Specifications

55
High Performance Trading/Algo Speed with Wombat Design and Implementation Guide
OL-15617-01
Appendix B—Building and Configuring Switches
In the event that the error counters indicate a problem, shut down the port(s).
Port Shut-down
Run Step Troubleshoot “Bring Up” Pod On All Pods
Refer to the material under step Troubleshoot “Bring Up” Pod, page 53. Create a checklist and cross off
each pod as you complete the step.
Connect “bring up” Pod to Core Switches One at a Time
For each core switch, repeat the steps under Step Troubleshoot “Bring Up” Pod, page 53.
Connect Pods to Core Switches
Connect each pod to all core switches. Connect 1 to 4 pods at a time to the core switches. Be sure to
connect each pod to all of the core switches at once. Debug as per steps in
Troubleshoot “Bring Up”
Pod, page 53.
Troubleshooting after Pruning
Move components around to determine the source of the problem:
• Cable
• Port
• Chassis (interior port)
• HCA
• TCA/gateway
SM The SM can monitor thresholds on the error counters and the SM can notify you. Refer to the
relevant SM documentation for details (Cisco SFS CLI guide or Cisco High-Performance SM
User Guide).
Manual We have get_counters script and reset_counters script. Reset counters clears the port counters
throughout the network. Get counters gets the counters throughout the network.
Counters_to_errs pulls the data from the get_counters script and identifies problems from the
data. Error counters will accumulate on the fabric even when jobs don’t run. Some errors,
however, will only appear when jobs run.
Step 1
Login: super
Password:
xxxxx
Log in to the switch.
Step 2
R2S101> enable
Enter Privileged Exec mode.
Step 3
R2S101# configure terminal
Enter Global Configuration mode.
Step 4
R2S101(config)# interface 1/5
Enter Interface Configuration submode.
Step 5
R2S101(config-int-1/5)# shutdown
Shut down the problematic port.