HP XC System Software Administration Guide Version 3.0

This command flushes each client node's IP routing cache and generates traffic on its primary default gateway
(its preferred server) in an attempt to influence the selected default gateway.
NOTE: This implementation of NAT prevents the use of NFS locking.
The GATEWAY= field of the /etc/sysconfig/network file, which provided network configuration in
previous releases of the HP XC System Software, is no longer used. Use the ip route show command to
display a node's routing information. The following command line example continues the example from
Figure 7-1. and shows the routing information for NAT client nodes n6 and n7:
# pdsh -w n[6-7] ip route show
.
.
.
n6: default via 172.20.0.4 dev eth1
n6: default via 172.20.0.8 dev eth1
.
.
.
n7: default via 172.20.0.8 dev eth1
n7: default via 172.20.0.4 dev eth1
.
.
.
where 172.20.0.4 refers to n4 and 172.20.0.8 refers to n8.
For further information, see ip(8).
Network Time Protocol Service
By default, the head node acts as the primary Network Time Protocol (NTP) internal server for all other nodes
in an HP XC system. Other nodes are NTP clients of the head node.
You can specify where the NTP server obtains its time reference during the initial configuration of the HP XC
system; up to three external time servers are accepted if the internal server is connected to an external
network. You can also specify the internal server's clock as the time reference instead.
If you encounter a clock synchronization problem, examine the /etc/ntp.conf file on the internal server
and the /etc/ntp.conf file on the node that is experiencing the problem.
You can restart the NTP service (ntpd) with the following command:
# service ntpd restart
Other tools (ntpq and ntpdc) are also available. For more information on NTP, see ntpd(1), ntpdc(1),
and ntpq(1).
78 Network Administration