HP XC System Software Release Notes for Version 3.0

# pdsh -a -x n122,n126,n129 cp /etc/init.d/default_gateway \
/etc/init.d/default_gatewaySAVE
3. Use the dbsysparams command to modify the value of NAT_GATEWAYS from multiple
to single:
# /opt/hptc/sbin/dbsysparams "NAT_GATEWAYS"
NAT_GATEWAYS: multiple
# /opt/hptc/sbin/dbsysparams -s "NAT_GATEWAYS" "single"
# /opt/hptc/sbin/dbsysparams "NAT_GATEWAYS"
NAT_GATEWAYS: single
4. Rerun nconfig and cconfig to rewrite the /etc/init.d/default_gateway file on
each node so that the file contains one default gateway definition:
# pdsh -a service nconfig nconfigure
# pdsh -a service nconfig nrestart
7.5 Re-edit the /etc/dhcpd.conf File Any Time cluster_config or discover
is Rerun
This task applies only to systems using a Myricom interconnect or QsNet
II
interconnect with
DHCP.
Any time the cluster_config utility and discover commands are rerun, the contents of the
/etc/dhcpd.conf file are overwritten. If your system is using a Myricom or QsNet
II
interconnect, you customized this file to configure the interconnect switch line monitoring cards,
and therefore, your customizations are lost.
“Save the Contents of the /etc/dhcpd.conf File” (page 33) in this document instructed you to
save a backup copy of the /etc/dhcpd.conf file, so you should have a backup copy available.
Follow this procedure to restore the contents of the file:
1. Use the text editor of you choice to open the /etc/dhcpd.conf file.
2. Use the text editor of your choice to open the /etc/dhcpd.conf.ORIG file.
3. Merge the customizations you made to the backup copy of the file when you configured the
switch monitoring line cards into the /etc/dhcpd.conf file.
Important:
Do not replace the newly-created /etc/dhcpd.conf file with the entire contents of the
.ORIG backup copy because the new version of the /etc/dhcpd.conf file may contain
new or additional information that is not present in the backup copy.
4. Save your changes to the /etc/dhcpd.conf file.
5. Restart the dhcpd service:
# service dhcpd restart
7.6 pdsh Prints Out Non-Zero Return Status
In this release, the pdsh command prints out the return status of the remote command if it is
non-zero. In previous releases it did not. Some existing XC utilities (for example, sys_check)
rely on the previous pdsh behavior.
Therefore, you might see pdsh return status failure messages during the execution of some XC
utilities. These messages can be safely ignored. For example,
# sys_check -debug -nohtml nfs syslogng -output=/tmp/n3.txt
1 uname Mon Sep 26 15:49:58 EDT 2005
2 nfs Mon Sep 26 15:49:58 EDT 2005
pdsh@n3: n3: ssh exited with exit code 1
3 syslogng Mon Sep 26 15:49:58 EDT 2005
44 System Administration and Management Notes