3.4.0 Matrix Server Administration Guide

Appendix B: Error and Event Log Messages 241

Operational Problems

When fabric fencing is configured on the matrix, errors such as the

following can appear in the Alert panel on the PolyServe Management

Console.

FenceAgent <ip_address>: disabled status

The error indicates that there is an operational problem with the specified

FibreChannel switch (192.168.10.74 in the following example).

192.168.10.100 [Critical ] [2006-03-13 15:22:59] ClusterPulse

SERVERS Alert - FenceAgent 192.168.10.74: disabled status

being reported on 192.168.10.100

To resolve the problem, check the switch for faulting or failed

components such as GBICs and/or faulting slots.

Loss of Network Access or Unresponsive Switch

Errors such as the following can occur when a matrix node reacts to the

loss of network access or to an unresponsive FibreChannel switch.

FenceAgent 172.23.186.174: no response to queries from 172.23.186.30

172.23.186.29 [Error ] [2006-03-13 10:42:48] SCLD SERVERS Mon Mar 13

10:42:48 2006::scld(9858): CRITICAL ERROR: Unable to fence

host 172.23.186.27 uid[0]

21:00:00:e0:8b:03:29:b0::172.23.186.174: Error trying to

communicate with fenceagent.

These types of errors can be caused by the following:

• The server has experienced a total loss of network access to the

FibreChannel switch(es).

• A FibreChannel switch has become unresponsive to snmp requests.

• The dependent r/w community string has been changed or deleted.

The following utility is useful for determining whether a matrix node can

communicate with the FibreChannel switch. The command displays the

name service entries of the WWPN and the Fabric IDs of the switch. It

may take approximately five or six seconds for the output to be

displayed.

PSANinfo -c <snmp community string> <IP address of FC switch>