5.4.3 How to Check Errors

Check the messages output to the system log (/var/log/messages) if there is an error in the master server (primary) that causes a switch to the master server (secondary) or if an error in one side of a duplicated network causes a switch to the other side.

The status of the HA cluster and network repliation can be checked with the following commands.

Checking the status of the master server HA cluster

The status can be checked by running the hvdisp command on both the master server (primary) and the master server (secondary).

Refer to "hvdisp" in "5.3.5 Displaying object states" of the "PRIMECLUSTER Reliant Monitor Services (RMS) with Wizard Tools Configuration and Administration Guide" and Online help (man hvdisp) for information on the hvdisp command.

The following example shows the status in the master server (secondary) after switching due to an error in the master server (primary).

Display the status of the HA cluster of the master server (primary) (example)

# hvdisp -a

Local System:  master1RMS
Configuration: /opt/SMAW/SMAWRrms/build/bdpp.us

Resource            Type    HostName            State        StateDetails
-----------------------------------------------------------------------------
master1RMS          SysNode                     Online
master2RMS          SysNode                     Online
app1                userApp                     Faulted      Failed Over
Machine001_app1     andOp   master1RMS
Machine000_app1     andOp   master2RMS          Offline
ManageProgram000_Cmd_APP1 gRes                  Offline
Ipaddress000_Gls_APP1 gRes                      Offline

Display the status of the HA cluster of the master server (secondary) (example)

# hvdisp -a

Local System:  master2RMS
Configuration: /opt/SMAW/SMAWRrms/build/bdpp.us

Resource            Type    HostName            State        StateDetails
-----------------------------------------------------------------------------
master1RMS            SysNode                   Online
master2RMS            SysNode                   Online
app1                userApp                     Online
app1                userApp kawa4RMS            Online
Machine001_app1     andOp   kawa5RMS            Online
Machine000_app1     andOp   kawa4RMS
ManageProgram000_Cmd_APP1 gRes                  Online
Ipaddress000_Gls_APP1 gRes                      Online

Checking Network Repliation Status

Check the status using the dsphanet command. The status can be checked on the master server and slave servers.

Refer to "7.4 dsphanet Command" in "Chapter 7 Command references", in the "PRIMECLUSTER Global Link Services Configuration and Administration Guide 4.3 Redundant Line Control Function" for information on the dsphanet command.

Display the status of the network repliation of the master server (primary) (example)

# /opt/FJSVhanet/usr/sbin/dsphanet
[IPv4,Patrol / Virtual NIC]
 Name       Status   Mode CL  Device
+----------+--------+----+----+------------------------------------------------+
 sha0       Active    d   ON   eth5(ON),eth9(OFF)
 sha1       Active    p   OFF  sha0(ON)
[IPv6]
 Name       Status   Mode CL  Device
+----------+--------+----+----+------------------------------------------------+

Display the status of the network repliation of the slave server (example)

# /opt/FJSVhanet/usr/sbin/dsphanet
[IPv4,Patrol / Virtual NIC]
 Name       Status   Mode CL  Device
+----------+--------+----+----+------------------------------------------------+
 sha0       Active    e   OFF  eth5(ON),eth9(OFF)
 sha1       Active    p   OFF  sha0(ON)
[IPv6]
 Name       Status   Mode CL  Device
+----------+--------+----+----+------------------------------------------------+