4.0.0 HP Polyserve Matrix Server Event Notification Guide (T5392-96053, March 2010)

Message and Corrective ActionID
FenceAgent <IP_address>: no response to queries from <server>.
Fabric fencing is configured and a node has lost network access or the
FibreChannel switch is unresponsive.
Action. Possible causes of the error are:
• 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.
For the Cisco MDS FibreChannel switch with firmware version 2.1 or later, the
default VSAN (VSAN 1) is likely disabled, which causes fcFeFabricName (FA-MIB
defined) to be unassigned (all zeros). Currently Matrix Server uses the OID
assignment for fcFeFabricName to probe connected FC switches and will return
the above error messages if it is unable to determine a value for fcFeFabricName.
The messages can be quiesced by enabling the default VSAN (VSAN 1).
The following utility specifies whether a server 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>
13933
FenceAgent <IP_address>: no response to queries from <server> resolved.
Action. None. Alert 13933 is resolved.
13934
FenceAgent: disabled status being reported on <IP_address>.
Fabric fencing is configured and there is an operational problem with the specified
FibreChannel switch.
Action. Check the switch for faulting or failed components such as GBICs and/or
faulting slots.
13935
FenceAgent: disabled status being reported on <IP_address> resolved.
Action. None. Alert 13935 is resolved.
13936
Singleton matrix unable to take control of SAN, because the matrix that includes
NN.NN.NN.NN currently controls the SAN. Possibly this server has not been added
to the matrix or has been deleted from the matrix, or possibly a networking failure
or misconfiguration has partitioned this server from the servers that control the
SAN.
Action. Check the matrix configuration and add the server if it is not currently a
member. Also check the network to ensure that the server can communicate with
the rest of the matrix.
17001
PolyServe Matrix Server event notification guide 35