HP Insight Cluster Management Utility manuals
Computer Equipment > Software
When we buy new device such as HP Insight Cluster Management Utility we often through away most of the documentation but the warranty.
Very often issues with HP Insight Cluster Management Utility begin only after the warranty period ends and you may want to find how to repair it or just do some service work.
Even oftener it is hard to remember what does each function in Software HP Insight Cluster Management Utility is responsible for and what options to choose for expected result.
Fortunately you can find all manuals for Software on our side using links below.
HP Insight Cluster Management Utility Manual
191 pages 4.69 Mb
1 User Guide3 Contents9 Figures10 TablesExamples 11 1 Overview13 2 Installing and upgrading HP Insight CMU14 2.1.2 Planning for compute node installationTwo IP addresses are required for each compute node •Determine the IP address for the NIC on the administration network 2.1.3 Disk space requirements 2.1.4 Firmware upgrade requirementsIMPORTANT: All compute nodes must have the same firmware version 2.1.5 Configuring the local smart array card 2.1.6 Configuring the management cardsTo configure the management cards such as iLO: 1.Power on the server 2.Access the management card 3.Assign the same username and password to all management cards 4.Assign a fixed IP address to each management card 15 2.1.7 Configuring the BIOS2.1.7.1DL3xx, DL5xx, DL7xx, Blades COM1 COM2 NIC 1 PXE boot or PXE enabled NIC 2 Disabled Com Speed 9600 Bd Auto 16 •16 addresses on the c7000 Enclosure•8 addresses on the c3000 Enclosure To configure the iLO cards: 1.Open a browser to the OA 2.In the right window, select Device Bays 3.Select Bay 5.Enter the IP address of the first iLO card 6.Click Auto Fill or the red arrow Each iLO is reset and assigned an IP address by the OA 7.From the HP Insight CMU management node, ping each iLO On each Blade server: 1.Access the iLO card 3.Select the Power Management tab 4.For Automatically Power On Server, select No 5.Select Submit Figure 2 iLO server power controls 2.1.7.2DL160 G5, DL165c G5, DL165c G6, and DL180 G5 Servers •IDE ◦ATA/IDE Enhanced ◦Configure SATA as IDE 17 SystemDirect ◦DHCP Disabled Enabled Always VT100 2.1.7.3DL160 G6 Servers ◦NIC1 PXE Enabled AHCI 18 2.1.7.4 SL2x170z G6 and DL170h G6 Servers BIOS settingLast state Delayed BMC Shared Dedicated Node 9600 8,n,1 19 2.2Preparing for installation2.2.1 HP Insight CMU kit delivery 2.2.2Preinstallation limitations 20 2.2.3 Operating system support2.2.3.1 RHEL 6 support HP Smart Array warning with RHEL6 and future Linux releases /dev/sd /dev/cciss/c*d /dev/sd As a result of support for RHEL6, HP Insight CMU v7.1 now supports: •The ext4 file system •UUID support in fstabs (replaced at backup by HP Insight CMU) •dhcpd.conf alternate path support •SHA512 password support for RHEL6 management nodes •hpsa/cciss support 2.2.4HP Insight CMU CD-ROMdirectory structureTable Table 1 Directory structure 21 2.2.5 HP Insight CMU installation checklistPreparing the management node: Preparing the compute nodes: Preparing the GUI client workstation: 2.2.6 Login privileges 2.2.7 SELinux and HP Insight CMU 22 2.3Installation procedures#chkconfig --addcmu Install HP Insight CMU on the GUI client workstation. For details, see “Installing HP Insight CMU on the GUI client workstation” (page 135) 23 2.4Installing HP Insight CMU with high availability“Defining a cluster with HP Insight CMU” (page 32) 25 2.4.1 HA hardware requirementsThe hardware requirements for HP Insight CMU under HA control are: •Two or more management servers •One shared storage accessed by both servers 2.4.2Software prerequisites“Preparing for installation” (page 19) 2.4.3 Installing HP Insight CMU under HA2.4.3.1 Overview “Glossary” (page 187) /opt/cmu/ tools/cmu_ha_postinstall 2.4.3.2 HP Insight CMU HA service requirements A shared file system. The mount point of this file system must /opt/cmu-store •A shared IP address The HP Insight CMU HA service must be able to invoke the start stop #/etc/init.d/cmu start #/etc/init.d/cmu stop 2.4.3.3Installing and testing Install the HP Insight CMU rpm as described in “Installation procedures” (page 22) 26 2.4.4 Configuring HA control of HP Insight CMUIf HP Insight CMU is running, set audit mode before you stop HP Insight CMU: cmuadmin1# /etc/init.d/cmu set_audit cmuadmin1# /etc/init.d/cmu stop , the CMU_CLUSTER_IP=X.X.X.X •The shared file system mounted on /opt/cmu-store •The cluster IP address 4.Run cmu_ha_postinstall: cmuadlmin1# /opt/cmu/tools/cmu_ha_postinstall cmuadlmin1# 27 5.Start cmuserver:Start # /etc/init.d/cmuserver start cmuadmin1# /etc/init.d/cmu start Correct possible errors and unset audit mode: cmuadmin1# /etc/init.d/cmu unset_audit 28 cmu ha:cmu service needs (re)start7.Run the appropriate command for your HA software to start HP Insight CMU 8.To verify that HP Insight CMU is still running correctly, review the /var/log/cmuservice_hostname.log file for errors file for errors #/etc/init.d/cmu set_audit d.Run the post installation procedure: cmuadmin2# /opt/cmu/tools/cmu_ha_postinstall cmuadmin2# e.Unset the audit mode on the new member: # /etc/init.d/cmu unset_audit f.Start HP Insight CMU under HA control g.Use your HA tool to migrate the HP Insight CMU HA service on the new member 29 2.4.5 HP Insight CMU configuration considerationscmu_ha_postinstall “Configuring HA control of HP Insight CMU” (page 26) cmuconf0-xxxx.sav cmuconf1-yyyy.sav •When cmu_ha_postinstall runs on the first HP Insight CMU management server cmu_ha: nothing to backup from the cmu HA share cmuconf2-zzzz.sav 2.4.6 Upgrading HP Insight CMU HA service2.Remove the previous HP Insight CMU rpm on server 3.Install the new HP Insight CMU rpm on server 4.Relocate the HP Insight CMU HA service to server 5.Set audit mode on server 6.Remove the previous HP Insight CMU rpm on server 7.Install the new HP Insight CMU rpm on server 8.Run cmu_ha_postinstall on server on server 9.Unset the audit mode on server 10.Relocate the HP Insight CMU HA service to server 11.Run cmu_ha_postinstall on server 30 tftp31 cmugui.jar32 3 Defining a cluster with HP Insight CMUFigure 4 (page 32) contains four main areas: •The top bar allows you to perform configuration commands •A filter allows you to show specific resources The central frame displays the global cluster view. In •The bottom frame shows log information 33 3.2.2X server requirements3.2.3 Administrator modeClick Options→Enter Admin Mode atime 3.2.4Quitting administrator modeClick Options→Unprivileged Mode 3.2.5 Changing X display addressTo change the X display address: 1.Click Options→Administrator Mode Login as root, and then confirm that your X Window display address is correct 3.Click Options→Change X-displayaddress Figure 5 Change X display address dialog box 34 3.3 High-levelchecklist for building an HP Insight CMU cluster3.4 Cluster administration 35 3.4.1 Node management36 3.4.1.1 Scanning nodesCluster Administration→Node Management→Scan Node Figure 8 Scan node dialog Figure 8 (page 36) To launch the scan node process: 1.Click OK 2.In the confirmation window, click OK 3.Enter the user name and password for the management card 37 3.4.1.2 Adding nodes38 3.4.1.3 Modifying nodesNOTE: The node name cannot be changed 3.4.1.4 Importing nodes Cluster Administration→Node Management→Import Node All the imported nodes belong to the default logical group 3.4.1.5 Deleting nodes IMPORTANT: After deleting a node, you cannot recover its attributes 3.4.1.6 Exporting nodes 3.4.1.7 Contextual menu The contextual menu options are: 39 3.4.2Network entity management41 4 Provisioning a cluster with HP Insight CMU42 4.1.1Modifying logical groups4.1.2 Deleting logical groups 4.1.3 Renaming logical groups 43 4.2 Autoinstall•Adds support for SLES and Debian 4.2.1Autoinstall requirementsAutoinstall Autoinstall template Red Hat—Aclassic Red Hat kickstart file SLES—Anautoyast xml file Debian—Apreseed file 4.2.2Autoinstall templatesnfs --server=16.16.184.115 --dir=/data/repositories/rh5u4_x86_64 nfs --server=CMU_MGT_IP --dir=CMU_REPOSITORY_PATH CMU_MGT_IP CMU_REPOSITORY_PATH “Creating an autoinstall logical group” (page 44) /opt/cmu/etc/cmuserver.conf 4.2.3 Autoinstall calling methods 44 4.2.4 Using autoinstall from GUI4.2.4.1 Enabling autoinstall # /etc/init.d/cmu restart 4.2.4.2Creating an autoinstall logical group 45 Figure 18 New autoinstall logical group•autoinst.tmpl.orig—Anexact copy of the autoinstall file •repository—Alogical link to the autoinstall repository For example: #ls -l /opt/cmu/image/rh5u5_autoinstall/ total total -rw-r--r--1 root root 1313 Oct 11 13:48 autoinst.tmpl-orig lrwxrwxrwx 1 root root 31 Oct 11 13:48 repository /data/repositories/rh5u5_x86_64 4.2.4.3Registering compute nodes 4.2.4.4Autoinstall compute nodes When you start autoinstall on a compute node, the following files are created: autoinst.tmpl-cmu autoinst-[compute_node_hostname] —The autoinstall template with hard-coded node-specific information pxelinux_template pxelinux compute_node_hostname] NOTE: pxelinux-node1 Figure 19 Autoinstall log 46 4.2.5 Using autoinstall from CLI4.2.5.1 Registering an autoinstall logical group cmucli 4.2.5.2Adding nodes to autoinstall logical group cmu> add_to_logical_group node to logical_group_name cmu> add_to_logical_group node1 to rh5u5_autoinst selected nodes: node1 selected nodes: node1 processing 1 node Or: 4.2.5.3Autoinstall compute nodes To autoinstall a node, enter the following command at the cmucli prompt: cmu> autoinstall "image" node1 cmu> autoinstall "rh5u5_autoinst" node1 /opt/cmu/bin/cmu_autoinstall_node -1rh5u5_autoinst -fnodes.txt Where nodes.txt is the list of nodes to autoinstall 47 4.2.6 Customizationcmuserver.conf autoinstall template files present, in autoinstall templates variables HP Insight CMU makes the substitution CMU_MGT_GW do not use the variable in your template. Instead, use the real value customized title bars to provide GUI and CLI title customization pxelinux parameters Change the pxelinux parameters by editing variables in this section For example, if your compute nodes use ttyS1 as the console port for a Red Hat pxelinux parameters for a single compute node, edit the The changes are permanent because this file is not overwritten by subsequent the pxelinux_template file in the autoinstall logical group directory timeout increase CMU_AUTOINST_INSTALL_TIMEOUT increase 48 4.2.7 RestrictionsThis implementation contains the following restrictions: •The repository must be on the local storage of the management node •The repository must be exported by NFS only. Do not use HTTP, Samba, or FTP •Updates must be applied through autoinstall post installation scripts •Only qualified distributions and updates are supported by HP 4.3Backing up 4.3.1 Backing up a disk from a compute node in a logical groupThe backup action is only available when one node is selected To perform a backup: 1.Expand the node list in the left-sideframe 2.Select a node 3.Right-clickthe selected node. The contextual menu appears 4.Select the backup option. Figure 20 Backup dialog box 5.Click OK to launch the backup of the selected node with the chosen options 49 /opt/cmu/image 50 4.4 CloningFigure 23 Cloning status When cloning is complete, a popup window displays the results The cloning procedure has the following limitations: “Cloning mechanisms” (page 120) Use the following conditions to determine if cloning was successful: The list of successfully cloned nodes is in the /opt/cmu/log/cmucerbere.log 51 4.4.1Preconfigurationpre_reconf.sh /opt/cmu/ etc/pre_reconf.sh /opt/cmu/image/myimage/pre_reconf.sh The default content of pre_reconf.sh is: 52 4.4.2 Reconfiguration/opt/cmu/etc/reconf.sh /opt/cmu/image/myimage/ reconf.sh The reconf.sh script expects the following parameters: CMU_RCFG_PATH •CMU_RCFG_HOSTNAME contains the hostname of the node •CMU_RCFG_DOMAIN contains the domain name of the node •CMU_RCFG_IP contains the IP address of the node •CMU_RCFG_NTMSK contains the netmask of the node IMPORTANT: “Execute” permission must be set for the reconf.sh file for users 53 4.5 Node static infoFigure 24 Node static info 4.6 Rescan MAC 54 4.7 HP Insight CMU image editor1.Use the cmu_image_open command to expand the image 2.Make changes 3.Use the cmu_image_commit command to save the image 4.7.1 Expanding an imageAfter editing the image, commit changes: #cmu_image_commit -irh5u4_x86_64 image_mountpoint 55 4.7.2 Modifying an imagechroot chroot mount /proc chroot mount /sys mount •grub-install—Replacesthe boot loader of the management node 4.7.3Saving a modified cloning imageTo update cloning image rh5u4_x86_64 with the modifications: #/opt/cmu/bin/cmu_image_commit -irh5u4_x86_64 #/opt/cmu/bin/cmu_image_commit -irh5u4_x86_64 -nrh5u4_mod 4.8 HP Insight CMU diskless environments 4.8.1 Overview 56 4.8.2 Operating systems supportedOn the management node Install the rpm file system-config-netboot-cmd-cmu-0.1.45.1_X-Y.noarch.rpm Install the rpm file python-xml On the golden node Install the following prerequisites on the golden node: NOTE: Package names may vary depending on the OS distribution •busybox •busybox-anaconda(RHEL5 only) •dhclient (dhcp-clienton SLES) •bind-utils(not required on SLES) 4.8.4Modifying the TFTP server configuration1.Install TFTP on the head node 2.Start TFTP on the head node 3.Modify /etc/xinetd.d/tftp as follows: Modify as follows: 4.Restart xinetd to reload the TFTP configuration #/etc/init.d/xinetd restart 57 4.8.5Activating the diskless feature1.Edit /opt/cmu/etc/cmuserver.conf to activate CMU_DISKLESS: Edit to activate 2.Restart the HP Insight CMU server: 4.8.6Populating the HP Insight CMU database“Scanning nodes” (page 36) 4.8.7Creating a diskless image1.Verify the golden node is running Verify you have enough space on your head node in /root/.ssh/authorizedKeys file on the golden node file on the golden node #/opt/cmu/tools/copy_ssh_keys.exp ip_golden_node Enter the root password (not echoed) To avoid “Installing and starting on compute nodes” (page 81) 4.8.8Creating a diskless logical groupFrom the GUI 1.In the Logical Group Management window, click the Add button 2.Add a new logical group From the CLI 1.Start the HP Insight CMU CLI: # /opt/cmu/cmucli cmu> probe_kernel cmu> add_logical_group <myTestImage> 16.16.185.192 "2.6.9-42.ELsmp 59 4.8.9 Adding nodes into the logical group1.Select nodes to add to the diskless image logical group 2.Click Add Figure 28 Adding nodes to logical groups Add the node into the logical group as follows: cmu> add_to_logical_group node1 – noden to <myTestImage 60 4.8.12.1files.custom61 4.8.12.2Using reconf-diskless-image.sh4.8.12.3Using reconf-diskless-snapshot.sh The script is invoked with the following four input parameters: •CMU_RCFG_PATH—Thepath to the snapshot directory of the node. /opt/cmu/image/<imageName>/snapshot/<nodeName node •CMU_RCFG_HOSTNAME—Thename of the node •CMU_RCFG_IP—TheIP address of the node •CMU_IMAGENAME—Thename of the diskless image 4.8.12.4Templates and image file /opt/cmu/image imageName reconf /opt/cmu etc/reconf-diskless-image.sh /opt/cmu/etc/reconf-diskless-snapshot.sh 62 4.8.13Best practices for diskless clusters•Do not update the /opt/cmu/image/<imageName>/root directory >/root Reasons for not updating this directory are: •You can make several diskless images •You can use the golden node as a diskless compute node normal 63 4.8.14Configuring additional NFS serversTo build a large-scalediskless cluster with HP Insight CMU: •Not more than 256 nodes per NFS server •4GB of (non-SATA)storage per compute node on each NFS server On Red Hat # chkconfig nfs on 64 On SLES# chkconfig nfsserver on RPCNFSDCOUNT /etc/sysconfig/nfs RPCNFSDCOUNT=8 Set in the /etc/ hosts /opt/cmu/etc/cmu_diskless_nfs_servers Sample file: Proceed with the diskless installation procedure in “Populating the HP Insight CMU database” (page 57) /opt/cmu/etc/cmu_diskless_nfs_servers When a diskless logical group is created /opt/cmu/image/ <logical_group_name root snapshot /opt/cmu/image/<logical_group_name When a node is added to the diskless logical group •A copy of the snapshot directory for this node is sent to the NFS server pxelinux.cfg 65 4.8.15 Comments on High Availability (HA)66 5 Monitoring a cluster with HP Insight CMU67 5.3 Monitoring the clusterLaunch the HP Insight CMU GUI Figure 31 Main window •By network entity •By logical group •By user group •By nodes definition Figure 31 (page 67) To change the classification, select a group from the drop-downmenu An icon represents the status of each node in the tree 68 5.3.1 Node and group status5.3.2Selecting the central frame display 69 5.3.3Global cluster view in the central frame70 5.3.4 Resource view in the central frameMonitoring values can be visualized by: •Global cluster •A specific logical group •A specific network entity •A specific user group /opt/cmu/bin/cmu_monstat cmu_monstat 5.3.4.1 Resource view overview Figure 34 Resource view overview Figure 35 Alert messages 5.3.4.2Detail mode in resource view 71 5.3.5 Gauge widget5.3.6 Node view in the central frame 72 5.3.7Using time view73 5.3.7.1 Getting startedTo launch HP Insight CMU with Time View: •From the web: Go to http: yourcluster •With Java: ◦Download required libraries: –Copy cmugui.jar to a chosen folder (/tmp in this example): scp root@yourcluster: /opt/cmu/bin/cmugui.jar /tmp scp root@yourcluster: –Copy required jars to the same folder: scp root@ yourcluster: /opt/cmu/www/jnlp/jogl-2.0-b44-20111202/jar/*.jar /tmp ◦Launch HP Insight CMU: java -cp"*" _GEN2.GUI.View.SplashScreen ◦Enter the IP address of your cluster when prompted In the HP Insight CMU GUI: •Select a group (in Network Entity, Logical Group, or User Group) •In the right panel, click the third tab labeled Time View 5.3.7.2 Tagging nodes 5.3.7.3 Adaptive stacking 74 5.3.7.4 Bindings and options75 5.3.7.4.3 Custom cameras•e – Set perspective view •z – Set history view •s – Set front view 5.3.7.4.4 Options The following options are also available in Options→Properties: Anti-aliasing Petal 5.3.7.5Technical dependencies “Troubleshooting” (page 75) 5.3.7.6 Troubleshooting –Detrunk=false “Getting started” (page 73) If Time View stops running, a restart button appears below the Time View panel 76 5.3.8 Archiving user groups1.Delete a user group Answer Yes to Do you want to archive this User Group? See Figure 40 (page 76) Figure 40 Archiving deleted user groups Figure 41 (page 76) Figure 41 Archived user groups cmu_del_user_group 5.3.8.1 Visualizing history data 5.3.8.2Limitations To display an archived user group, the following conditions must be satisfied: •Time must not exceed 24 hours •The number of nodes must not exceed •The number of metrics must not exceed •The product of the three parameters above must not exceed Table 2 (page 77) Table 2 Valid archived user group parameters 77 5.4 Stopping HP Insight CMU monitoring5.5 Tuning HP Insight CMU monitoring 5.5.1 Action and alert filesSensors, alerts, and alert reactions are described in the /opt/cmu/etc ActionAndAlertsFile.txt file file Following is an example of the contents of the file: collectl “Using for gathering monitoring data” (page 81) 78 5.5.2 ActionsEach action contains the following fields: Name Description Time multiple •A time multiple of 1 means the value is monitored every 5 seconds •A time multiple of 2 means the value is monitored every 10 seconds Data type Measurement method This can be either Instantaneous or MeanOverTime •Instantaneous returns the sensor value immediately 79 5.5.3 Alerts5.5.4 Alert reactions80 ConditionThe reaction is performed under this condition CMU_ALERT_NAME The name of the alert that caused the reaction CMU_ALERT_LEVEL The level of the alert CMU_REACT_MESSAGE The text of the “Description” for this reaction CMU_ALERT_NODES cmu_condense_nodes CMU_ALERT_NODES_EXPANDED CMU_ALERT_VALUES CMU_ALERT_NODES_EXPANDED CMU_ALERT_TIMES CMU_ALERT_SEQUENCE_FILE Several optional sensors, alerts, and alert reactions are commented out in the •Comment a sensor, alert, or alert reaction to stop monitoring it •Uncomment a sensor, alert, or alert reaction to start monitoring it •Modify a sensor, alert, or alert reaction line to change its parameters 81 collectl5.5.6.2Modifying the ActionAndAlerts.txt file 82 #collectl –c1 -s+C --exportlexprwaiting for 1 second sample Create the monitoring lines by using these variables Native HP Insight CMU lines and collectl lines can be mixed in the ActionAndAlertFile.txt file 83 colplot84 Import the common directory created on the administration server for#vi /etc/fstab X.X.X.X:/var/log/collectl /var/log/collectl nfs defaults where X.X.X.X is the address of your HP Insight CMU administration server #vi /etc/collectl.conf 11.Restart collectl: # /etc/init.d/collectl restart 5.5.6.3.1 Plotting data http://X.X.X.X/colplot Figure 42 ColPlot window Select plotting options, then click Generate Plot Figure 43 ColPlot results 85 5.5.7 Monitoring GPUs and coprocessors5.5.7.1 Monitoring NVIDIA GPUs Use the script /opt/cmu/contrib/install_nvidia.pl /opt/cmu/contrib/ install_nvidia.README /opt/ cmu/bin/cmu_config_nvidia ActionAndAlertsFile.txt 86 /opt/cmu/bin/cmu_config_nvidia“Action and alert files” (page 77) 5.5.7.2 Monitoring AMD GPUs /opt/cmu/contrib/cmu_install_amd /opt/cmu/contrib/ cmu_install_amd.README /opt/ cmu/bin/cmu_config_amd /opt/cmu/bin/cmu_config_amd 87 5.5.7.3 Monitoring Intel coprocessorsa.# cd /tmp b.# tar xvzf driver-file.tgz c.# cd created-driver-directory #sudo yum install --nogpgcheck --noplugins --disablerepo=**.rpm #sudo zypper --no-gpg-checksinstall *.rpm #sudo micctrl initdefaults #sudo micctrl –r #service mpss start #/opt/intel/mic/bin/micinfo k.Review the results and verify no errors are reported With the coprocessors working, enable coprocessor monitoring by updating the /opt/ cmu/etc/ActionAndAlertsFile.txt /opt/cmu/bin/cmu_config_intel “Global cluster view in the central frame” (page 69) 88 5.5.8 Monitoring HP Insight CMU alerts in HP Systems Insight ManagerActionAndAlertFile.txt “Alerts” (page 79) “Alert reactions” (page 79) Figure 44 (page 89) SNMP_util Figure 44 HP Insight CMU alert converted to SIM event HP Systems Insight Manager User Guide 89 5.5.9 Extended metric supportipmitool /opt/cmu/ contrib/cmu_IPMI_monitoring.README /opt/cmu/ contrib/cmu_IPMI_monitoring EXTENDED cmu_submit_extended_metrics /opt/cmu/bin Use the following three steps to configure an extended metric: . The following is an explanation of each field in the file as they pertain to extended metrics: The name of the extended metric. Description A brief description of the extended metric Time Multiple 91 6 Managing a cluster with HP Insight CMUTo select a terminal emulator other than the default: 1.Edit /opt/cmu/etc/cmuserver.conf Six blocks of variable names begin with CMU_REMOTE_TERMINAL 3.Verify all variables for other terminal emulators are commented out 4.Restart cmuserver: 92 6.4 Management card connection“SSH connection” (page 91) 6.5 Virtual serial port connection 6.6 Shutdown 6.7 Power offFigure 47 Power off dialog box 93 6.8 BootFigure 48 Boot dialog box 6.9 RebootFigure 49 Reboot dialog box 6.10 Change UID LED status 94 6.11 Multiple windows broadcastFigure 50 Multiple windows broadcast command 6.12 Single window pdshpdsh •cmudiff (default) •dshbak 95 6.12.1cmudiff examples97 6.13 Parallel distributed copy (pdcp)To copy the file: 1.Right-clickthe nodes you want to copy to 98 6.14User group management6.14.1Adding user groupsFigure 53 User group management 99 6.14.2Deleting user groups1.In the User Group Management window, select the user group to delete 2.Click Delete 6.14.3Renaming user groups1.In the User Group Management window, select the user group to rename 2.Click Rename 3.Enter the new name 6.15 HP Insight firmware management 6.15.1 Viewing and analyzing BIOS settingsconrep http://www.hp.com CMU_BIOS_SETTINGS_TOOL CMU_BIOS_SETTINGS_FILE cmu_dsh cmu_diff Located in /opt/cmu/tmp/conrep/ on each selected node: •A copy of the conrep binary •A copy of the conrep XML file •The file containing the BIOS settings 100 6.15.2Checking BIOS versionsVendor Version Release Date dsh_bak 6.15.3 Installing and upgrading firmware 6.16 Customizing the GUI menu/opt/cmu/etc/cmu_custom_menu /opt/ cmu/cmucli 1.In the /opt/cmu/etc/cmu_custom_menu file, uncomment the following line: 2.Run the CLI 3.cmu> custom_run The available custom commands are displayed Run the dmidecode cmu custom_run "audit|dmidecode" node10 101 6.16.1Saving user settings6.17 HP Insight CMU CLI 6.17.1 Starting a CLI interactive session#cmucli The following output appears: CMU - Cluster Management Utility (c)HP Competency Center Start of CMU CLI Session Wed Jan 4 17:30:49 CET 6.17.2 Basic commandsExiting an HP Insight CMU CLI interactive session cmu> exit Starting a noninteractive HP Insight CMU CLI session To start the CLI session and execute commands from a file: #cmucli my_path/my-file Management card naming iLO in HP Insight CMU GUI is ILO in HP Insight CMU CLI 102 Help commandshelp cmu> help Getting help for a command To get detailed information and the exact syntax of a command: #help command_name For example, to get more information about the halt command: cmu> help halt halt nodes of group_1 and group_2 Displaying logical groups of a cluster The groups command displays the list of the logical groups cmu> groups cmu> groups default Displaying nodes of a logical group To view nodes in a group and the attributes: cmu> groups <group_name groups Displaying nodes of the cluster The nodes command displays the list of nodes with the attribute name cmu> nodes 103 6.17.3 Specifying nodesUsing the HP Insight CMU CLI, you can execute a command on any number of nodes The nodes command: •Displays node information •Tests regular expressions for selecting nodes before executing a command Executing a command on one node cmu> node o185i222 active node list selected: o185i222 cmu 104 Executing a command on a list of nodesTo execute a command on multiple nodes, you must specify the names of nodes cmu> boot o185i222 o185i233 o185i243 active node list selected: o185i222 o185i233 o185i243 cmu Executing a command on a range of nodes cmu> boot o185i222 - o185i225 active node list selected: o185i222 o185i223 o185i224 o185i225 cmu IMPORTANT: Spaces between “-”and node names are mandatory Using wildcards cmu> nodes o185i22 Complex list of nodes To boot specific nodes: cmu> boot o185i209 o185i217 o185i22* o185i232 - o185i235 Executing a command on all nodes A command followed by the all option is executed on all nodes cmu> boot all Excluding specific nodes from a command allbut cmu> boot allbut o185i2 Executing a command on all nodes of a logical group cmu> boot all default Executing a command on specific nodes of a logical group but cmu> boot all default but o185i222 - o185i252 active node list selected: o185i194 o185i202 o185i216 o185i253 o185i254 cmu 105 6.17.4 Administration and cloning commandsBooting a set of nodes The boot modes are: •Normal mode boots nodes on the default device, generally the hard drive •Network mode fills the dhcpd.conf file to boot nodes over the network cmu> boot [net] cmu_nodes_regular_expression boot [net] Booting node o185i192 normal on the hard drive: cmu> boot o185i192 Booting node o185i192 with the network: cmu> boot net o185i192 Broadcasting commands to a set of nodes “Multiple windows broadcast” (page 94) cmu> broadcast cmu_nodes_regular_expression broadcast 106 To broadcast on all nodes of the cluster:cmu> broadcast all Rebooting a set of nodes cmu> reboot delay "message" cmu_nodes_regular_expression reboot where delay message A string that appears on every rebooted node cmu> reboot 1 "Reboot for maintenance" o185i192 active node list selected: o185i192 Rebooting the nodes ..Return-->Commandtoo long to execute<--:wait_for_command: .Please read /opt/cmu/log/Reboot.log to check errors cmu Halting a set of nodes cmu> halt delay "message" cmu_nodes_regular_expression halt A string that appears on every halted node cmu> halt now "Halt for maintenance" o185i192 Halting the nodes ..Please read /opt/cmu/log/Halt.log to check errors cmu Powering off a set of nodes cmu> power off cmu_nodes_regular_expression power off cmu> power off o185i192 107 Please read /opt/cmu/log/PowerOff.log for errors. cmuSetting the locator LED on or off cmu> Locate on|off cmu_nodes_regular_expression Locate on|off cmu> locate on o185i192 active node list selected: o185i192 cmu cmu> locate off o185i192 Cloning a set of nodes cmu> clone "image_name" cmu_nodes_regular_expression clone cmu> clone "cluster " o185i195 108 Adding a new logical groupadd_logical_group cmu> add_logical_group image_name "device cmu> add_logical_group my_logical_group "cciss/c0d0 processing 1 logical group Adding nodes to a logical group add_to_logical_group cmu> add_to_logical_group nodes to group_name cmu> add_to_logical_group o184i115 - o184i116 to my_logical_group selected nodes: o184i115 o184i116 processing 2 nodes Backing up a node backup cmu> backup or: cmu> backup "image_name" "root_partition,other_partition" node_name backup /boot The following example backs up three partitions on a hard disk of a node cmu> backup "test_julien" "sda1,sda5,sda9" o185i195 109 where:test_julien is the name of the logical group containing the node being backed up sda1,sda5,sda9 are the partitions on the hard drive o185i195 is the node name The following example is an interactive backup image name? > test_julien sda1,sda5,sda6,sda8,sda9 o185i195 110 Modifying a management card passwordModifies the management card password in the HP Insight CMU database cmu> modify_password ILO|ILOCM|lo100i cmu> modify_password lo100i login> hp password> service password successfully changed Discovering MAC address for new nodes scan_macs cmu> scan_macs Enter the number of nodes to scan: Enter the first nodename: node1 Enter the prefix of the node: node Enter the IP address of the first node: Enter the netmask of the first node: Enter the BMC type (ex. ILO, lo100i): ILO Enter the IP address of the first BMC: Scanning 2 nodes First nodename is 'node1'. The prefix is 'node The first IP address is '16.16.184.115'. The netmask is '255.255.248.0 The BMC type is 'ILO The first BMC IP address is '16.16.188.115'. Is this correct? ([y]/n): y Scanning. Please be patient. This process can take up to 10 minutes Scanning complete. 2 nodes added, 0 nodes updated. cmu 111 6.17.5 Administration utilities pdcp and pdshHP Insight CMU includes the open source software pdcp and pdsh Usage example of pdcp: #/opt/cmu/bin/pdcp -wcn0001,cn0002 source /tmp/dest is a file on the management node is the name of the destination file copied to compute nodes cn0001 and cn0002 Usage example of pdsh: #/opt/cmu/bin/pdsh -wcn0001,cn0002 ls The ls command is executed on compute nodes cn0001 and cn0002 6.17.6 HP Insight CMU Linux shell commands“HP Insight CMU manpages” (page 139) 112 7 Advanced topics113 sudoTable 4 HP Insight CMU GUI features and their corresponding commands 114 7.1.3 Examplesshutdown reboot ALL localhost jsmith ALL = NOPASSWD: /opt/cmu/tools/halt.exp /opt/cmu/tools/reboot.exp /etc/sudoers cjones ALL = CMU_POWER To let user 'bstevens' control power and provisioning without a password: bstevens ALL = NOPASSWD: CMU_POWER CMU_IMAGE sbarney ALL = NOPASSWD: CMU_POWER CMU_IMAGE CMU_ETC 7.2 HP Insight CMU diskless APIstateful stateless stateless ramdisk — The entire OS image is transferred during the /opt/cmu/diskless /opt/cmu/diskless/system-config-netboot The diskless API requires that the following programs exist The term <DISKLESS> here refers to the name of the implementation "toolkit 115 7.2.1 Build diskless imagebuild_image -l <CMU diskless logical group name The name of the new logical group -g <"golden node -k <"kernel version /opt/ cmu/image CMU diskless logical group name initrd 7.2.2 Delete diskless imagedelete_image The name of the logical group to delete 116 7.2.3 Configure diskless nodeThe name of the diskless logical group -s <NFS server IP The IP address of the NFS server -n <nodename The hostname of the target node to configure -i <IP address The IP address of the target node to configure -m <MAC address The MAC address of the target node to configure -e <eth device The active Ethernet device of the target node to configure 7.2.4 Unconfigure diskless nodeunconfigure_node The hostname of the target node to unconfigure The IP address of the target node to unconfigure /opt/cmu/tools/cmu_remove_node_from_dhcp 7.2.5 Boot diskless nodeboot_node The hostname of the target node to boot The IP address of the target node to boot The MAC address of the target node to boot The active Ethernet device of the target node to boot configure_node /opt/cmu/tools/cmu_add_node_to_dhcp 117 7.2.6 Diskless checkdiskless_check unconfigure_node boot_node After these programs are created, tested, and installed in the /opt/cmu diskless / directory CMU_VALID_DISKLESS_TOOLKITS 7.3 HP Insight CMU remote hardware control API/opt/cmu/bin/cmu_power As of CMU v7.1 the existing hardware APIs are: ILO The most common method of interacting with HP BL/DL/SL servers lo100i The legacy method of interacting with low-endHP servers None IPMI The industry standard method, useful with non-HP(or non-iLOHP) hardware 118 ILOCMThe method for integration with HP Moonshot 1500 Chassis /opt/cmu/ hardware HW_TYPE /opt/cmu/hardware/ILO cmu_<HW_TYPE>_power_<ACTION cmu _power Where <ACTION> is one of: off Remove power from the server Apply power to the server osoff Attempt a graceful shutdown of the OS before removing power uid_off Turn off the UID light uid_on Turn on the UID light These are the five basic actions required by HP Insight CMU status Provide a power status for the given node, either on or off press Simulate a "momentary press" of the power button FOO All of these programs are invoked with the following arguments: <PROGRAM> -n<NODENAME> -i<BMC_IP> -e<ERRFILE Where: <NODENAME The hostname of the target server <BMC_IP The IP address of the management card for the target server <ERRFILE The name of the file to log any errors CMU_VALID_HARDWARE_TYPES v7.1 this is the setting of this variable: CMU_VALID_HARDWARE_TYPES=ILO:lo100i:ILOCM To add the IPMI hardware API, add IPMI to the list of valid hardware types: CMU_VALID_HARDWARE_TYPES=ILO:lo100i:ILOCM:IPMI 119 7.4Customizing kernel arguments for the HP Insight CMU provisioning kerneldefault /opt/cmu/etc/bootopts /opt/cmu/etc/ bootopts/default /opt/cmu/etc/bootopts nodename hex-IP-address hex-ip-address •The /opt/cmu/etc/bootopts/default file is used. This is the default behavior For example, to create a node-specific PXE-bootfile: 1.Copy /opt/cmu/etc/bootopts/default to /opt/cmu/etc/bootopts/login1 Edit the new login1 ip=::::::bootp ip=:::::eth1:bootp /opt/cmu/etc/bootopts/ login1 /opt/cmu/etc/bootopts/login2 /opt/cmu/etc/bootopts/login3 etc/bootopts/AC14000. The hexadecimal IP address AC14000 covers IP addresses 120 7.5Support for ScaleMPCMU_vSMP_PREFIX=vSMP network boot For more details, see the ScaleMP documentation 7.6 Cloning mechanisms 123 8 Support and other resources•Installation and user guides for your specific operating system 124 8.3Typographic conventionsThis document uses the following typographical conventions: %, $, or # audit(5) (5) A manpage. The manpage name is audit, and it is located in Section Command A command name or qualified command phrase Computer output Text displayed by the computer Ctrl+x ENVIRONMENT VARIABLE The name of an environment variable, for example, PATH ERROR NAME The name of an error, usually returned in the errno variable Key The name of a keyboard key. Return and Enter both refer to the same key Term The defined use of an important word or phrase User input Commands and other text that you type Variable The preceding element can be repeated an arbitrary number of times Indicates the continuation of a code example Separates items in a list of choices WARNING 126 A Troubleshootingcmuserver •An incorrect MAC address in the HP Insight CMU database •The HP Insight CMU configuration on the management node is lost 127 Troubleshooting switch issues1.Verify that the management node pings the iLO and the nodes 2.Verify that broadcast is enabled and is redirected to the switch 3.Verify that the spanning tree is disabled on all ports connected to a node 4.Verify that « multicast IGMP snoop loop » is disabled on the switch 1.Boot one node in network mode 2.Login using cmuteam as the password 3.Verify that the node can ping the management card of other nodes 4.Verify that the node can ping other nodes 5.If the network boot image is damaged, reinstall the HP Insight CMU rpm A.2.1 Troubleshooting network boot1.Open a console to the management card of the node 2.Select the node in the HP Insight CMU main window and boot in network mode 3.Does the node receive a DHCP response from the server 4.Can the node download its kernel •If yes—Proceedto the next step •If no—Verifythe TFTP daemon configuration 5.Can the node mount / with NFS •If yes—Thenetwork image might be corrupted. Reinstall the HP Insight CMU rpm •If no—Verifythe NFS server is started 6.Verify that /opt/cmu/ntbt/rp is exported to all nodes with NFS A.3 Backup issuesIf you get the Could not get fstab message: 1.Verify that you can boot in network mode Verify that the device associated with the image in /opt/cmu/etc/cmu.conf •sda for SCSI or SATA disks cciss/c*d* for smart array. If you have RHEL6, see 3.Verify that the correct partition was chosen while launching the backup 4.Reboot the node and run « df » to check the root partition number If you get the Backup failure 128 A.4 Cloning issuesA.5 Administration command problems A.6 GUI problems 131 B Detailed installation instructions•On SLES: #chkconfig nfsserver on #/etc/init.d/nfsserver start 132 B.4 Verifying the DHCPD listen interface#grep DHCPD_INTERFACE= /etc/sysconfig/dhcpd In the example, DHCPD listens to the interface eth2 #chkconfig dhcpd on B.5 Firewall configuration On the HP Insight CMU management node:•External network interface ◦ RMI registry traffic (tcp ports 1099, 49150) Webserver port (tcp 80) ssh server (tcp 22) •Internal (Admin/Compute) network interface On the GUI client workstation:•X Window export (tcp ports 6000 to 6063) B.6 Java installation B.7 Installing HP Insight CMU1.On the management node, log in as root 2.Mount the CD-ROM: # cd /mnt/cdrom/Linux 3.Install the HP Insight CMU rpm: #rpm --import /mnt/cmuteam-rpm-key.asc #rpm -ivh /mnt/cmu-v7.1-1.i386.rpm cmuteam-rpm-key 133 B.8 Installing HP Insight CMU licensingCopy the content of all Flexlm license key files to /opt/cmu/etc/cmu.lic B.9 Setting the Java PATHCMU_JAVA_BIN #CMU_JAVA_BIN="/usr/java/jre1.6.0_31/bin/java B.10 Configuring the HP Insight CMU management server hostname Methodhosts /etc/hosts #Do not remove the following line, or various programs #that require network functionality will fail 127.0.0.1localhost.localdomain localhost 10.0.0.100 hptc481.gre.hp.com hptc481 2.Verify the setting # hostname 3.Verify the address # /opt/cmu/tools/cmu_mgt_net_info 134 B.11 Starting HP Insight CMUstarting cmu service cmu:core(standard) configured (audit mode) not running (audit mode) running (audit mode) configured ( subnet X.X.X.X netmask Y.Y.Y.Y {} ) cmu:high-availability unconfigured (audit mode) note: use '/etc/init.d/cmu unset_audit' to unset cmu 'audit mode #/etc/init.d/cmu unset_audit cmu service needs (re)start The output lists all the daemons started by cmuserver. java cmustatus Status of the utility checking the state of all the compute nodes 135 B.12 Configuring HP Insight CMU to start automaticallyB.13 Verifying the HP Insight CMU state B.14 Installing HP Insight CMU on the GUI client workstation 136 B.14.1 Configuring the GUI client on Linux workstationsUsing an ssh tunnel # /etc/init.d/sshd restart # ssh x.x.x.x -lroot # echo $DISPLAY Using an X Window server •Allow rmi connection and X display export in your firewall configuration 137 B.14.2 Activating the HP Insight CMU GUI•By copying the HP Insight CMU GUI Java file onto the client Launching the HP Insight CMU GUI using a web browser CMU_THTTPD_PORT To launch the HP Insight CMU GUI: Start a web browser on the HP Insight CMU client and then enter: cmu-management-node-ip-addr Launching the HP Insight CMU directly from the Java file /opt/cmu/bin To launch the client: On Windows operating systems: On Linux operating systems: Run the -jar 139 HP Insight CMU manpages140 cmu_show_nodes(8)NAME SYNOPSIS/opt/cmu/bin/cmu_show_nodes DESCRIPTION OPTIONS(ILOCM only) cartridge number (ILOCM only) node number 141 EXAMPLESDefault behavior: #/opt/cmu/bin/cmu_show_nodes cn0004 cn0005 cn0006 cn0008 cn0009 To show details for a specific node: #/opt/cmu/bin/cmu_show_nodes -nnode1 -o"%n %i %k %m default %b %t To show details for all nodes: #/opt/cmu/bin/cmu_show_nodes -a -o"%n %i %k %m default %b %t 142 cmu_show_logical_groups(8)#/opt/cmu/bin/cmu_show_logical_groups <-h | [logical_group_name] #/opt/cmu/bin/cmu_show_logical_groups #/opt/cmu/bin/cmu_show_logical_groups rhel6 143 cmu_show_network_entities(8)144 cmu_show_user_groups(8)145 cmu_show_archived_user_groups(8)cmu_show_archived_user_groups --Show archived user groups /opt/cmu/bin/cmu_show_archived_user_groups Show archived user groups pretty print (add blank lines for readability) print headers print in column mode change separator (not available in column mode) dumps all information, not just user group names column width for the displayed user group names #/opt/cmu/bin/cmu_show_archived_user_groups #/opt/cmu/bin/cmu_show_archived_user_groups -p -f #/opt/cmu/bin/cmu_show_archived_user_groups -f -s Return code is 0 if operation succeeds, or 1 if not successful 146 cmu_add_node(8)cmu_add_node --Add node(s) to the HP Insight CMU database #/opt/cmu/bin/cmu_add_node <-h | -s | -i | -f filename #/opt/cmu/bin/cmu_add_node -H|--hostname hostname -I|--ip ipaddress [-M| mask netmask] [-A| mac macaddress] [-L|--lg logicalgroup] [-G|--mgt-ip mgtcardip] [-T|--mgt-cardILO|lo100i|ILOCM] [-R|--arch architecture] [-C| cartridge num] [-N| node-number num] filename option option -h|--help show help -i|--interactive specify node(s) information is provided interactively -A|--macmacaddress compute node MAC address compute node MAC address -L|--lglogicalgroup compute node logical group compute node logical group -G|--mgt-ipmgtcardip compute node management card IP address -T|--mgt-cardILO|lo100i|ILOCM specifies the management card ilo type. ILO, LO100i, or ILOCM -R|--archarchitecture node architecture (e.g. "x86_64") -C|--cartridgenum (ILOCM only) cartridge number within chassis -N|--node-numbernum (ILOCM only) node number within the cartridge 147 Command-linemode:Interactive mode: In interactive mode, you are prompted for node parameters: #/opt/cmu/bin/cmu_add_node -i hostname> n10 hostname ip address> 16.16.184.116 netmask ip address netmask mac address> 00-1C-C4-79-35-83 architecture> x86_64 mgtcard> ILO mac address architecture mgtcard mgtcard ip address Adding multiple nodes using a file: The input file must have one line per node. Where one each line: #cat nodes.txt #/opt/cmu/bin/cmu_add_node -fnodes.txt processing 4 nodes 148 cmu_add_network_entity(8)#/opt/cmu/bin/cmu_add_network_entity <-f filename | -h #/opt/cmu/bin/cmu_add_network_entity rack1 rack2 #/opt/cmu/bin/cmu_add_network_entity -fnetwork_entity_list 149 cmu_add_logical_group(8)#/opt/cmu/bin/cmu_add_logical_group <-n | -i | -f filename | -s #/opt/cmu/bin/cmu_add_logical_group <-n name -d devicename #/opt/cmu/bin/cmu_add_logical_group -ntest -dcciss/c0d0 #/opt/cmu/bin/cmu_add_logical_group -flogical_group_file 150 cmu_add_to_logical_group_candidates(8)/opt/cmu/bin/cmu_add_to_logical_group_candidates #/opt/cmu/bin/cmu_add_to_logical_group_candidates -trh6u0_x86_64 node1 151 cmu_add_user_group(8)#/opt/cmu/bin/cmu_add_user_group <-f filename | -h #/opt/cmu/bin/cmu_add_user_group <user_group_name1, user_group_name2 #/opt/cmu/bin/cmu_add_user_group user1 user2 #/opt/cmu/bin/cmu_add_user_group -fuser_group_list 152 cmu_add_to_user_group(8)#/opt/cmu/bin/cmu_add_to_user_group <-h | -t user_group nodename #/opt/cmu/bin/cmu_add_to_user_group <-t user_group nodename -f nodenamefile #/opt/cmu/bin/cmu_add_to_user_group -tgroup1 cn0003 #/opt/cmu/bin/cmu_add_to_user_group -tgroup1 -fnodenamefile 153 cmu_change_active_logical_group(8)/opt/cmu/bin/cmu_change_active_logical_group #/opt/cmu/bin/cmu_change_active_logical_group -trh6u0_x86_64 cn0001 /opt/cmu/bin/cmu_change_active_logical_groups 154 cmu_change_network_entity(8)#/opt/cmu/bin/cmu_change_network_entity <-h | -t network_entity nodename1 #/opt/cmu/bin/cmu_change_network_entity -track1 cn0001 #/opt/cmu/bin/cmu_change_network_entity -track2 -fnodenamefile 155 cmu_del_from_logical_group_candidates(8)156 cmu_del_from_network_entity(8)#/opt/cmu/bin/cmu_del_from_network_entity <-h | -t network_entity nodename1 #/opt/cmu/bin/cmu_del_from_network_entity -track1 node1 #/opt/cmu/bin/cmu_del_from_network_entity -track2 -fnodenamefile 157 cmu_del_archived_user_group(8)#/opt/cmu/bin/cmu_del_archived_user_group [-h]| [-v] [-ttimeout] [-d] #/opt/cmu/bin/cmu_del_archived_user_group -njob1, job2, job[12–145] 158 cmu_del_from_user_group(8)#/opt/cmu/bin/cmu_del_from_user_group <-h | -t user_group nodename1 #/opt/cmu/bin/cmu_del_from_user_group <-t user_group nodename -f nodenamefile #/opt/cmu/bin/cmu_del_from_user_group -tuser1 node1 #/opt/cmu/bin/cmu_del_from_user_groups -tuser2 -fnodenamefile 159 cmu_del_logical_group(8)#/opt/cmu/bin/cmu_del_logical_group <-f filename | -h #/opt/cmu/bin/cmu_del_logical_group rh5u5_x86_64 sles11sp1_x86_64 #/opt/cmu/bin/cmu_del_logical_group -flogical_group_list 160 cmu_del_network_entity(8)#/opt/cmu/bin/cmu_del_network_entity <-f filename | -h #/opt/cmu/bin/cmu_del_network_entity rack1 rack2 #/opt/cmu/bin/cmu_del_network_entity -fnetwork_entity_list 161 cmu_del_node(8)#/opt/cmu/bin/cmu_del_node <-f filename | -h #/opt/cmu/bin/cmu_del_node <node_name1, node_name2 #/opt/cmu/bin/cmu_del_node node1 node2 #/opt/cmu/bin/cmu_del_node -fnode_list 162 cmu_del_snapshots(8)/opt/cmu/bin/cmu_del_snapshots 163 cmu_del_user_group(8)#/opt/cmu/bin/cmu_del_user_group <-f filename | -h> [-a] [-m] #/opt/cmu/bin/cmu_del_user_group <user_group1, user_group2 #/opt/cmu/bin/cmu_del_user_group user1 user2 #/opt/cmu/bin/cmu_del_user_group -fuser_group_list # /opt/cmu/bin/cmu_del_user_group -a -m60 -fuser_group_list 164 cmu_console(8)cmu_console --Connect to compute node management ports #/opt/cmu/bin/cmu_console <compute_node_hostname 165 cmu_power(8)cmu_power --Perform power actions on compute nodes -paction specifies the action to perform; valid actions are: OFF Power off. Depending on ACPI, it will be a shutdown, or a plain power off OS_OFF System shut down BOOT System shut down followed by power on STATUS Get power status PRESS Emulates pressing the power button UID_OFF Turn off the UID led UID_ON Turn on the UID led -nnodename specifies the host name(s) of the node(s) where the action will be performed -fnodefile specifies that the action well be performed on all nodes -llogical_group_name logical_group_name -uuser_group_name specifies that the action will be executed on nodes belonging to the user group user_group_name -eerror_log specifies the file name of an optional error log file 166 .cmu_power -pOFF -ncn0001.cmu_power -pOFF -uuser1 .cmu_power -pBOOT -lrh6u0_x86_64 ./cmu_power -pUID_ON -uuser2 167 cmu_custom_run(8)#/opt/cmu/bin/cmu_custom_run <-h | -l | -t command_title [-f nodefile] #/opt/cmu/bin/cmu_custom_run -l # /opt/cmu/bin/cmu_custom_run -taudit|lspci 168 cmu_clone(8)RETURN CODES 169 cmu_backup(8)#/opt/cmu/bin/cmu_backup <-h>| <-l logical_group -n compute_nodename-p ./cmu_backup -lmyimage -nnode20 -p"cciss/c0d0p3,cciss/c0d0p1 ./cmu_backup -lmyimage -nnode20 -r3 -e /tmp/err.log 170 cmu_scan_macs(8)OPTIONS (naming)-hhostname %xi %xL %xc %xn -sstart_val Start the integer value represented by %xi at start_val rather than -Sskip_val -phostname_prefix hostname_prefix 171 OPTIONS (general)-ifirst_ip_addr first_ip_addr -tBMC_type String specifying the BMC type. (e.g. ILO, ILOCM) -fBMC_ip_addr_file -bBMC_ip_addr BMC_ip_addr -nnum_to_discover num_to_discover BMC_ip_addr -mnetmask netmask -aarchitecture CMU_VALID_ARCHITECTURE_TYPES -NNIC_num NIC_num -ooutput_file output_file cmu_add_node 172 Example174 cmu_rescan_mac(8)#/opt/cmu/tools/cmu_rescan_mac -nnodename [N NIC_num] [-h] #/opt/cmu/tools/cmu_rescan_mac -no184i116 175 cmu_mod_node(8)#/opt/cmu/bin/cmu_mod_node <-h | -s | -i | -f filename #/opt/cmu/bin/cmu_mod_node -H|--hostname hostname [-I|--ip ipaddress] 176 /opt/cmu/bin/cmu_mod_node#/opt/cmu/bin/cmu_mod_node -i hostname> n10 Modifying multiple nodes using a file: #/opt/cmu/bin/cmu_mod_node -fnodes.txt 177 cmu_monstat(8)NODE AND GROUP OPTIONS178 #/opt/cmu/bin/cmu_monstat --nodes=n0001,n0002,n00[01-11]#/opt/cmu/bin/cmu_monstat --all-sensors --all-nodes #/opt/cmu/bin/cmu_monstat --all-alerts --prefix --lg=sles11_x86_64 #/opt/cmu/bin/cmu_monstat --sensors=cpuload,memory_used --nodes=n[1-2] #/opt/cmu/bin/cmu_monstat --sensors=cpuload --alerts=login_alert --nodes=n1 #/opt/cmu/bin/cmu_monstat --all-nodes --all-sensors --stats #/opt/cmu/bin/cmu_monstat --all-nodes --color 179 cmu_image_open(8)#/opt/cmu/bin/cmu_image_open <-h | -i imagename #/opt/cmu/bin/cmu_image_open -irh5u5_x86_64 180 cmu_image_commit(8)#/opt/cmu/bin/cmu_image_commit <-h | -i imagename [-n new_image_name] #/opt/cmu/bin/cmu_image_commit -irh5u5_x86_64 # /opt/cmu/bin/cmu_image_commit -irh5u5_x86_64 -nrh5u5_x86_64_new 181 cmu_config_nvidia(8)cmu_config_nvidia --Configure NVIDIA GPU monitoring /opt/cmu/ etc/ActionAndAlertsFile.txt print this help text replace earlier HP Insight CMU GPU monitoring with this monitoring install non-interactivelyby accepting defaults for all questions 182 cmu_config_amd(8)cmu_config_amd --Configure AMD GPU monitoring /opt/cmu/bin/cmu_config_amd 183 cmu_config_intel(8)#/opt/cmu/bin/cmu_config_intel <-h | -r | -n 184 cmu_mgt_config(8)MODE 186 cmu_firmware_mgmt(8)#/opt/cmu/bin/cmu_firmware_mgmt [-h] [-d -f <nodefile #/opt/cmu/bin/cmu_firmware_mgmt –v –fnodes.txt #/opt/cmu/bin/cmu_firmware_mgmt –d –fnodes.txt #/opt/cmu/bin/cmu_firmware_mgmt –uCP019061.scexe –fnodes.txt 187 Glossary189 Index
Also you can find more HP manuals or manuals for other Computer Equipment.