Specifications

54
High Performance Trading/Algo Speed with Wombat Design and Implementation Guide
OL-15617-01
Appendix B—Building and Configuring Switches
Look at Port Errors
Monitor the port counters in the network. Expect to find numerous problems during bring-up.
Error Course of Action
Configuration caused by some ports in INIT state 1. Look for Failed discover node test, node
00:05:ad:00:00:02:22:d0, port_num= 14, error code
1 in the log.
Note that the message provides you with the device
GUID (in this case, 00:05:ad:00:00:02:22:d0) and port
number (14).
2. Match the GUID to its SFS chassis and identify the
chassis type.
Note If the chassis type is a Cisco 7000, the external port
number is the same as the port number reported in
the ts_log. If the chassis is a Cisco 7008, refer to
“Appendix C: Cisco SFS 7008 Port Mapping” to
map the port listed in the log to the external port
number of the chassis.
3. Disable the offending port(s) and check the error log to
verify that the log entries have stopped.
SM OUT_OF_SERVICE trap for
GID=0xfe800000000000000005ad00000348e1
Note This message is not a problem when changes have
occurred in the network. It is just a problem if there
are ports which are bouncing between in-service and
out-of-service, causing the SM to continuously
sweep.
1. Identify the subnet prefix in the log entry. As of the
release of this document, the subnet prefix is always
fe:80:00:00:00:00:00:00.
2. Identify the GUID. The GUID immediately follows the
subnet prefix. In our example, the GUID is
00:05:ad:00:00:03:48:e1.
3. Find the port. For these log entries, the GUID usually
represents a channel adapter port. If the GUID is odd
the Node GUID will be the Port GUID - 1. In the case
above, the Node GUID is: 00:05:ad:00:00:03:48:e0.
You use the GUID in the message (the port GUID) to
find the node guid (minus 1, possibly 2), and then find
the switch port to which the node connects and take
down the port.
4. Run neighbor_to_cal.
5. Shut down the port.