HP XC System Software Administration Guide Version 3.0

Example A-5. As a User on the HP XC Node Launching to an HP XC Resource As a User on the HP XC
Node Launching to an HP XC Resource
$ bsub -I -n6 -R type=SLINUX64 srun hostname
Job <416> is submitted to default queue <normal>.
<<Waiting for dispatch ...>>
<<Starting on xclsf>>
xc3
xc3
xc2
xc2
xc1
xc1
Troubleshooting
• Use the following commands to check your configuration changes:
iptables -L and other options to confirm the firewall settings•
• pdsh -a 'ls -l /etc/init.d/lsf' to confirm startup script
• pdsh -a 'ls -ld /shared/lsf/' (using our running example) to confirm that the LSF tree
was properly mounted
• pdsh -a 'ls -l /etc/profile.d/lsf.sh' to confirm the LSF environment scripts
• Monitor the LSF log files when problems arise for communication complaints, unresolved host name
issues, or configuration problems.
• Ensure that the HP XC firewall has been disabled properly. Having this enabled will prevent the non-XC
LSF nodes from communicating with the HP XC LSF node.
• Ensure that the controllsf command has been properly configured with alias. Run the controllsf
show command to confirm proper settings.
• Check the output of the ifconfig command on the HP XC LSF node to ensure that the LSF alias was
properly established.
If eth0 is the external network device, the LSF alias entry is eth0:lsf.
• Use the appropriate LSF commands to restart daemons when network communications have been
adjusted:
• lsadmin reconfig to restart the Load Information manager (LIM)
• badmin mbdrestart to restart the Master Batch Daemon (mbatchd)
• badmin reconfig to reset the batch settings for the Slave Batch Daemon (sbatchd).
See the Platform LSF documentation for more information on these commands and Standard LSF.
Troubleshooting 181