PRIMECLUSTER Global Link Services Configuration and Administration Guide: Redundant Line Control Function 4.1 (for Solaris(TM) Operating System)

6.1 Redundant Line Control function Troubleshooting Data to be Collected

In the event of a problem in Redundant Line Control function operation, Redundant Line Control function troubleshooting requires following information about the problem to be collected.
When collecting examination materials of a Redundant Line Control function all together, see "6.1.1 Command to collect materials".

1) Collecting materials common to each mode

Collect the following materials for examination when an error occurred in the workings of a Redundant Line Control function:

• The content of the detailed operation and error messages when a phenomenon occurred.
• A console log (/var/adm/messages) file
• A log file (/var/opt/FJSVhanet/log/*) of a Redundant Line Control function
• An environment setting file (/etc/opt/FJSVhanet/config/*) of a Redundant Line Control function
• The result of executing /opt/FJSVnet/usr/sbin/dsphanet
• The result of executing ifconfig -a
• The result of executing netstat -ni
• The result of executing netstat -nr
• The result of executing netstat -np

2) When an error occurred in Fast switching mode

When an error occurred in Fast switching mode, perform "1)Collecting materials common to each mode" and collect the following materials:

• The result of executing /opt/FJSVhanet/usr/sbin/dsphanet -o
• The result of outputting a driver trace of a Redundant Line Control function. (See "6.2 Trace" as to how to set, etc.)

3) When an error occurred in RIP switching mode

When an error occurred in RIP switching mode, perform "1) Collecting materials common to each mode" and collect the following materials:

• The result of executing ps -ef
• The result of executing /opt/FJSVhanet/usr/sbin/dsppoll (Only when using a router monitoring function.)

4) When an error occurred in Fast switching/RIP mode

When an error occurred in Fast switching/RIP mode, see "2) When an error occurred in Fast switching mode and 3) When an error occurred in RIP switching mode". Collect materials according to the operation state where an error occurred.

5) When an error occurred in NIC switching mode

When an error occurred in NIC switching mode, perform "1) Collecting materials common to each mode" and collect the following materials:

• The result of executing ps -ef
• The result of outputting a driver trace of a Redundant Line Control function when an error occurred in the workings of a using standby patrol function and in standby NIC. (See "6.2 Trace" as to how to set, etc.)

6) When an error occurred in GS/SURE linkage mode

When an error occurred in GS/SURE linkage mode, perform "1) Collecting materials common to each mode" and collect the following materials:

• The result of outputting a driver trace of a Redundant Line Control function. (See "6.2 Trace" as to how to collect, etc.)
• The result of executing /opt/FJSVhanet/usr/sbin/dsphanet -c
• The result of executing /opt/FJSVhanet/usr/sbin/dsppoll -c

---

6.1.1 Command to collect materials