Specifications

57
High Performance Trading/Algo Speed with Wombat Design and Implementation Guide
OL-15617-01
Appendix B—Building and Configuring Switches
5. Internal link
problem (Cisco
7008; similar steps
apply to the Cisco
7012 and 7024)
Try to identify the bad fru:
• node card
• core card
• backplane (almost never)
Figure out failed ports. (Use the show diag fru error command at the switch CLI.) Identify the
cards that create the failed connection. Begin by swapping out the relevant node card with
another node card (do not introduce an outside card). Check and see if the location of the error
follows the swapped card. If so, you have identified a faulty node card. If the error has not
moved, the problem is with the core card or the backplane.
Leave the swapped node cards in their new state and swap the relevant core card with another
fabric module in the chassis. (Choose the module that will cause you the least amount of effort
or overhead.) Check and see if the problem follows the module. If it does, you have identified
a faulty SFM.
If the problem has not moved at all, you have identified a faulty backplane. If the problem
disappeared altogether during any of these steps, you probably had a seating problem.
6. Internal link
problem (Cisco
3504)
These steps are similar to the steps for the Cisco 7008 but the blanking panels in the 360 cause
links between the switch cards. In addition to looking for connections between switch cards and
gateway cards and between fabric controller cards and switch cards, look for issues between
switch cards and blanking panels.
The switch cards on the Cisco 3504 are symmetric, so you cannot swap the cards with one
another to determine which has a problem, because the problem will appear in the same location.
Instead, you must swap one of the existing cards with a third card to diagnose problems.