A ServerNet Switch failed neighbor validation on one of its ports. The offending node will not be able to receive or transmit ServerNet data packets until the situation is corrected. Possible Cause / Solution: Ports not configured: If a port is not configured or disabled, this event is generated whenever the topology is changed, or firmware is updated. The snetSwitchNeighborID will indicate that the link is down with LD. If the snetSwitchNeighborID is AF, this indicates the specified port is disabled and assumed failed. If the specified port is not configured, this event may be ignored. Bad Node: Run diagnostics to validate offending nodes. Incorrect cabling: verify cabling and correct if necessary. Incorrect configuration: switch configruation may be incorrect. Reconfigure switch. Node not added to SAN: Offending node may not have been added to the SAN. Run ServerNet II Administrative Utility to add node. Incorrect SAN installation: Offending node may not have been correctly added to SAN. Run Administrator GUI to verify status and add if necessary. To force the switch to rerun neighbor checks, the user may have to manually cycle the power on the offending node.