Specifications

High Performance Trading/Algo Speed with Wombat Design and Implementation Guide

OL-15617-01

Appendix B—Building and Configuring Switches

Troubleshoot “Bring Up” Pod

Embedded SM

High-Performance SM

• config trace 2 0x1000

• tail –f var syslog messages or tail –f <syslog-server>

Isolate Problems and Prune Ports

It is important to constantly monitor the ts_log on the switch where the SM is running or on the

High-Performance Subnet Manager. As every piece of equipment is added to the subnet, you must make

sure the SM is able to complete its sweep of the subnet, and that there are no errors.

As you add each component to the subnet, watch the ts_log with the show logging end command

(embedded) or tail –f var syslog messages command (HSM). When a new component is added, there

should be a number of messages about “in service traps” and changes to the topology. However, they

should quickly settle down, and after a few sweeps, the SM should stop logging. If new log entries

continue to appear, there is a problem with the subnet. If you see continuous messages starting with

“Configuration caused by,” then the SM has not been able to completely sweep the subnet, and is

constantly retrying. You should address these errors before you add any additional components to the

fabric.

Step 1

Password: xxxxx

Step 2

R2S101> enable Enter Privileged Exec mode.

Step 3

R2S101# terminal length 0 Configure unlimited output from show commands.

Step 4

R2S101# configure terminal Enter Global Configuration mode.

Step 5

R2S101(config)# trace app 26 mod 10 level terse flow

0x1000

Configure trace level for log tracking.

Step 6

R2S101(config)# exit Returns to Privileged Exec mode.

Step 7

R2S101# show logging end Displays the Subnet Manager log.