Check whether the "hanetobserv" command has been set correctly.
If GS's IP address moves between nodes as follows, execute the "hanetobserv create" command for each GS node.
# /opt/FJSVhanet/usr/sbin/hanetobserv create -n GS -i 192.168.120.20 -t 192.168.10.20,192.168.20.20
# /opt/FJSVhanet/usr/sbin/hanetobserv create -n GS -i 192.168.120.20 -t 192.168.10.30,192.168.20.30
# /opt/FJSVhanet/usr/sbin/hanetobserv print
Destination Host Virtual Address (Router Address+)NIC Address
+----------------+-------------------+--------------------------------+
GS 192.168.120.20 192.168.10.20,192.168.20.20
192.168.10.30,192.168.20.30 |
If you create the settings as follows, one node is set as the communication target. If you want to perform this in a cluster configuration, execute the command for each node one by one. Note that the difference between the settings mentioned above and the settings here is whether the IP addresses in the "NIC Address" field that are displayed by the "hanetobserv print" command are separated by commas.
# /opt/FJSVhanet/usr/sbin/hanetobserv create -n GS -i 192.168.120.20 -t 192.168.10.20,192.168.20.20,192.168.30.20,192.168.40.20
# /opt/FJSVhanet/usr/sbin/hanetobserv print
Destination Host Virtual Address (Router Address+)NIC Address
+----------------+-------------------+--------------------------------+
GS 192.168.120.20 192.168.10.20,192.168.20.20,
192.168.30.20,192.168.40.20 |
