Snetswitchibcerror - Compaq ServerNet ServerNet II Installation Manual

snetSwitchIBCError

ServerNet II Switch has detected IBC errors, such as, bad length, corrupt packet, bad
control data, bad source route, bad command, or permission violation.
Bad length, control data, bad source route and command are likely related to an initiator
or target using an incompatible version of IBC.
Corrupt packet indicates that one or more symbols where dropped, and permission
violation is self-explanatory.
Specific Trap:
Severity:
Summary:
Enable:
Disable:
snetSwitchSnetID
snetSwitchName
snetSwitchPortErrorStatusIndex
snetSwitchLinkErrorCounter
snetSwitchPacketErrorCounter
snetSwitchIBCErrorCounter
Bad Node
Loose Cable
Bad Cable
Incompatible versions of the IBC protocol
Blabbering Node
Probing Node
Switch ownership may be incorrect
104
Major
Switch snetSwitchSnetID, (snetSwitchName), port snetSwitchPortErrorStatusIndex has
detected IBC level errors. Link level errors are snetSwitchLinkErrorCounter, IBC level errors
are snetSwitchIBCErrorCounter.
snetSwitchThresholdErrorTrapEnable = 1
snetSwitchThresholdErrorTrapEnable = 0
Returned Variable
Possible Cause
ServerNet II Switch SNMP Traps J-7
Indicates
Identifies the switch that detected the error
The switch name. If no name is defined, this field will be
blank.
Indicates the port that detected the error
Indicates the current value of the link error counter
Contain the packet errors on the same port
Contain the IBC errors on the same port
Possible Solution
Run diagnostics to validate offending nodes
Check cable connections
Replace cable
Ensure that compatible versions of software and firmware are
installed on the offending nodes.
Run diagnostics to ensure that nodes at both ends of the cable
or communicating properly. Replace if necessary.
A node may be trying to break into the network. Isolate the
node and verify SAN membership.
Check ownership; Cycle power on the offending switch to
cause ownership update.