|
|
Home | Introduction | Web Interface | TFT Display | Appendix | Glossary
From the top-level menu of the web interface to the switch
click on Sync Ports.
On this webpage, there will be a list of switch ports that are out-of-sync. An out-of-sync switch port is a switch port that is not able to communicate due to:
If the switch port did not initialize properly, the resync procedure will reset the switch port. There is a pull-down menu from which you can choose the ports to be re-synced. Your choices are:
all -- All switch ports will be resynchronized.
best -- Only out-of-sync ports are resynchronized.
sff -- All sff ports are resynchronized.
quad -- All quad ports are resynchronized.
xbar -- All crossbar ports are resynchronized.
The default is best. You then specify when (in seconds) the ports will be resynchronized. The default is 5 seconds. You then click on Sync.
If one or two iterations of Syncing does not reset the port (and the port is still listed as unsync), try checking the shutdown checkbox and then select Sync again. If the situation seems to get worse (the list of unsynchronized ports grows longer), these are false positives, and you can try increasing the timeout on the pull-down list (from its default of 5 seconds). Also follow the procedure outlined in the Appendix to help identify the cause of the failure.
According to this example, there are four quad ports reported as disconnected. These down ports are located on port 12 and port 13 on the M3-4SW32-16Q switch line card located in slot 8, and on port 6 and port 7 on the M3-4SW32-16Q switch line card in slot 9.
Click on each of these four quad port and determine if we see a non-zero local synch failure or a remote synch failure switch trap for each. A local synch failure and remote synch failure pair will be associated with the connection on the two ends of the fiber cable. I.e., a local synch failure will be reported at the switch port connected to one end of the fiber cable and a remote synch failure will be reported at the switch port connected to the other end of the fiber cable. The goal is to identify which local synch failure switch port is connected by a fiber cable to which remote synch failure port.
For example, if we click on the first reported down port (slot.8.contained.xbar32.1.xbar32_port.12), we will be taken to this webpage:
which reports non-zero values for the local synch failure and port down switch traps. (If we then click on the quad port hyperlink on this webpage, we will see the non-zero counters signal lost and signal lost count for this quad port. Further, we will see 4 xbar port, and these correspond to the four xbar ports to which this quad port is connected. Further, if we click on the second xbar port (corresponding to xbar32.1, we will see that this is the fiber connection reporting the local synch failure.)
Similarly, if we click on (slot.8.contained.xbar32.1.xbar32_port.13), we will be taken to this webpage:
which contains non-zero values for the remote synch failure and port down switch traps.
Examining the other two quad ports, we see that slot 9, port 6 reports a non-zero local synch failure and slot 9, port 7 reports a non-zero remote synch failure.
From this information, we know that slot 8, port 12 and slot 9, port 6 report local synch failure and slot 8, port 13 and slot 9, port 7 report remote synch failure. However, it is not possible to determine from the switch information which local synch failure corresponds to which remote synch failure. You must physically inspect the cabling on the two switch line cards to determine if slot 8, port 12 is connected to either slot 8, port 13 or slot 9, port 7. Likewise, we must determine whether slot 9, port 6 is connected to either slot 8, port 13 or slot 9, port 7.
Refer to "One of the connected switch ports is not illuminated." for further troubleshooting details.
Last updated: 27 August 2007