Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
slots for serial transmission of data. Therefore at any instant only two ports can be
communicating.
With the addition of Switch fabric, the switchs backplane changes from serially-accessed
bus to crossbar fabric. By using crossbar fabric, many ports can be simultaneously
transmitting and receiving data, providing a much higher throughput.
The crossbar fabric consists of 18 fabric channels, providing each linecard two fabric
channels into the crossbar fabric. These channels can run at 8Gbps or 20Gbps
depending upon the line card used. The CEF256 and dCEF256 series modules connect
to fabric using 8 Gbps per channel and CEF720 series modules connect to it using 20
Gbps per channel.
Requirements
For a module to use switch fabric, it should be a fabric enabled module
Troubleshooting Tips
1. If the Fabric Switch Module does not work as expected, check the following:
2
a) Check if the Fabric Switch Status is Active. To do this, use the show fabric active
command. This command will display the current status of the Fabric Switch. Here is an
example.
b) Check the fabric status of switching modules in the device. To do this use the show
fabric status [slot_number | all] command. This command will display the fabric status
of one or all switching modules. Here is an example,
Switch# show fabric status
slot
channel
speed
module
status
status
fabric
8G
OK
OK
8G
OK
Up- Timeout
20G
OK
Up- BufError
8G
OK
OK
8G
OK
OK
8G
Down- DDRsync
Switch#
OK
c) Check the fabric utilization of switching modules. To do this use the show fabric
utilization [slot_number | all] command. This command will display the fabric utilization
of one or all modules.
Here is an example,
channel
speed
Ingress %
20G
20G
20G
24
20G
24
20G
48
20G
20G
Egress %
2. In certain rare condi tions out put of 'show fabric channel-counters' may show
incrementing number of rxErrors.
Switch#show fabric channel-counters
Slot channel rxErrors txErrors
txDrops lbusDrops
39
a) RxRrror indicates that the module received corrupted packet(s) and dropped.
b) The Fabric do NOT check CRC when forwarding frames between different fabric
ports/channels.
c) This could be due to the receiving module corrupting the frames or receiving
corrupted frames from any fabric-enabled module in the switch.
0 20G
OK
1 20G
OK
OK Y(not-hot)
0 20G
OK
OK Y(not-hot)
1 20G
OK
OK Y(not-hot)
0 20G
OK
OK
N/A
1 20G
OK
OK
N/A
0 20G
OK
OK
N/A
1 20G
OK
OK
N/A
0 20G
OK
OK Y(not-hot)
1 20G
OK
OK Y(not-hot)
0 20G
OK
OK Y(not-hot)
1 20G
OK
OK Y(not-hot)
0 20G
OK
OK Y(not-hot)
1 20G
OK
OK Y(not-hot)
Reason: The standby fabric hot sync feature is only supported on the E version of the
6500 chassis, and this system has a non-E version.
3. If you see the error message as, SP: Linecard endpoint of Channel 7 lost
Sync.
To Lower fabric and trying to recover now!.
Reason: The message caused by a line card not being fully or properly seated. To
identify this line card - the capture of show fabric fpoe map command need to be
analyzed. Here is an example,
10
11
12
14
15
16
17
Workaround: The fpoe will be mapped to a specific line card slot. Once the suspect line
card is identified From the output of show fabric fpoe map, fpoe 7 points to the line
7
card in slot 8 and that is card that is causing the error messages.your next action
should be to schedule a removal and re-insert of that card to try to eliminate this
message from re-occurring.
4. If the system switching performance drops from 30Mpps to 15Mpps.
Reason: When classic and fabric enabled modules are mixed in a chassis, the system
switching performance drops from 30Mpps to 15Mpps.
Older "Classic" modules in the 6500, models 61xx, 62xx, 63xx, 64xx, send all traffic over
the switch BUS backplane, to be forwarded by the supervisor. Fabric enabled modules
only send the packet headers over the bus and the switch fabric can be utilized for
forwarding the data portion of the packet.
Workaround: Consider replacing any "Classic" modules with fabric enabled modules, in
order to increase system performance.
5. To troubleshoot further, collect the following show command output before
opening a TAC case.
step 1. turn on service internal.
switch# configure terminal
switch(config)# service internal
Troubleshooting Example
1. Fabric Time out Error Message:
%FABRIC-SP-[module-number]-TIMEOUT_ERR: Fabric in slot [dec] reported timeout
error for channel [dec] (Module [dec], fabric connection [dec])
Description
The error message indicates that firmware code on the fabric detected that the input or
output buffer was not moving. To recover from this condition, the system will
automatically
resynchronize the fabric channel.
Troubleshooting Steps
1. Issue the command hw-module reset to soft-reset the module. After the module
is up again,
2. capture the output of the command show module and the command show
diagnostic module all.
Sample Output Of show module
Show Module
Mod Ports
Card Type
Model
Serial No.
24
WS-X6724-SFP
SAL0AAAAAAA
24
WS-X6724-SFP
SAD0AAAAAAA
(Hot)
WS-SUP720-3B
SAD0AAAAAAA
(Active)
WS-SUP720-3B
SAD0AAAAAAA
10
1 2
---------U
4) TestActiveToStandbyLoopback:
Port
1 2
---------U
5) TestLoopback:
11
Port
1 2
12
1 2
---------U
In case the output doesnt come as expected, physically pull out and reseat the module
firmly in the chassis to hard-reset the module. After the module is up again, capture the
output of the command show module and show diagnostic module all
Here is an example of failed diagnostic test for module 1
Module 1: Catalyst 6000 supervisor 2 (Active) SerialNo :
Overall Diagnostic Result for Module 1 : MINOR ERROR
Diagnostic level at card bootup: minimal
Test results: (. = Pass, F = Fail, U = Untested)
1) TestSPRPInbandPing --------------> F
2) TestTransceiverIntegrity:
13
Solution:
Enabling switch fabric will not rectify overruns because after the installation of a Switch
Fabric Module in a Cisco Catalyst 6500 series switch, the traffic is forwarded to and from
modules in different modes which doesn't necessarily facilitate resolution for overruns.
The traffic is forwarded in one of these of these modes:
14
a) Flow-through mode: In this mode, data passes between the local bus and the
supervisor engine bus. This mode is used for traffic to or from modules that are not
fabric-enabled.
b) Truncated mode: Only truncated data (the first 64 bytes of the frame) goes over the
switch fabric channel if both the destination and the source are fabric-enabled modules. If
either the source or destination is not a fabric-enabled module, the data goes through the
switch fabric channel and the data bus. The Switch Fabric Module does not get involved
when traffic is forwarded between modules that are not fabric-enabled.
c) Compact mode: A compact version of the DBus header is forwarded over the switch
fabric channel, which delivers the best possible switching rate. Modules that are not
fabric-enabled do not support the compact mode and generate cyclic redundancy check
(CRC) errors upon receipt of frames in compact mode. This mode is used only when no
such modules are installed in the chassis.
Lets understand what overrun is:Overrun - The number of times the receiver hardware was unable to hand received data
to a hardware buffer
Common Cause - The input rate of traffic exceeded the ability of the receiver to handle
the data.
From the given example, the module used is WS-X6548-GE-TX:
This module is 8:1 oversubscribed. The ports on this module go to servers. On these
modules there is a single 1-Gigabit Ethernet uplink from the port ASIC that supports eight
ports. These cards share a 1 Mb buffer between a group of ports (1-8, 9-16, 17-24, 2532, 33-40, and 41-48) since each block of eight ports is 8:1 oversubscribed. The
aggregate throughput of each block of eight ports cannot exceed 1 Gbps. These line
cards are oversubscription cards that are designed to extend gigabit to the desktop and
might not be ideal for server farm connectivity. For more information refer to:-
More related:
The Differences of XFP, SFP and SFP+
How to Identify the Genuine Cisco SFP?
Basic Knowledge on Cisco SFP Modules
Technical Specifications for Cisco SFP Modules
16