HP Insight Control for Linux 6.2 User Guide

1.5 Insight Control for Linux command environment
Table 1-2 lists the Insight Control for Linux commands that you can run from the command line
on the CMS or on any management hub, with the exception of the pdsh command.
Table 1-2 Insight Control for Linux commands
ManpageDescriptionCommand
console(8)Enables access to the serial consoles of managed systems.
console
headnode(1)Returns the name of the CMS.
headnode
nodename(1)Displays the Insight Control for Linux internal name for the
CMS or managed system on which it is run.
nodename
nrg(8)Uses data that Nagios collects to generate reports, including an
analysis of the state of Insight Control for Linux collections.
nrg
pdsh(1)Runs a command or commands on the CMS across multiple
managed systems in parallel.
pdsh
shownode(1)This command has a variety of subcommands that provide
information about managed systems. Enter shownode --help
for a list of the subcommands.
shownode
For more information about an individual command, see the corresponding manpage, if one is
available. Use the man command to view manpages from the command line, as follows:
# man command_name
1.6 Internal task queuing and management
Because some Insight Control for Linux tasks, especially OS installation tasks, might take a long
time to complete, Insight Control for Linux uses an internal task engine for task queueing and
load balancing. The task engine provides the following benefits:
• Only one Insight Control for Linux task is run against a given target managed system at any
one time.
• Insight Control for Linux tasks are run against a given target managed system in the order
in which you started them.
• Regardless of the number of selected target managed systems, the load that the Insight
Control for Linux tasks imposes on the CMS is controlled so that performance and usability
of the CMS is unaffected.
You might notice that when you run an Insight Control for Linux tool against multiple target
managed systems, the task is completed on some managed systems before the task is started on
other managed systems. You might also notice that tasks proceed at a faster or slower rate on
some target managed systems. This is considered normal behavior.
All output, logging, and control of Insight Control for Linux tasks is integrated into the Tasks
& Logs→View Task Results… screen.
A time out of five days is in effect for an OS installation using Kickstart or AutoYaST files so that
tasks do not hang indefinitely.
You can change the number of Insight Control for Linux tasks that can be run concurrently. For
information, see Section 23.8 (page 210)
1.7 Synchronized system clocks
When using Insight Control for Linux, and especially when using Insight Control for Linux tools
to install operating systems on managed systems, to capture and deploy Linux images, HP
recommends that you keep system clocks up to date and synchronized.
18 Using Insight Control for Linux