Professional Documents
Culture Documents
Fabric Drops
Fabric Drops
Fabric Drops
Added by Yannick Le Teigner, last edited by Yannick Le Teigner on Apr 07, 2011 (view change)
This counter indicate some drops sending the packets across the fabric.
Collect the 'show class-of-service fabric statistics' command, and see if any FPC has drops towards
another FPC.
timeden@re0-bx01.lax04> show class-of-service fabric statistics
[...SNIP...]
Destination FPC Index: 8, Source FPC Index: 7
Total statistics: High priority Low priority
Packets: 289633053685 735213313900
Bytes : 93612800544377 554762954469973
Pps : 535679 958963
Bps : 181043816 541669832
Tx statistics: High priority Low priority
Packets: 289633053685 735200362884
Bytes : 93612800544377 554750982278504
Pps : 535679 958963
Bps : 181043816 541669832
Drop statistics: High priority Low priority
Packets: 0 12951016 <<<
Bytes : 0 11972191469 <<<
Pps : 0 0
Bps : 0 0
In the above output, you can see drops from FPC7 and FPC8 to FPC8. This command doesn't tell you
which PFE is actually having the drops. So you'll need to dig deeper to find out the problematic set of
interfaces. And depending on the type of FPC, you'll have to use different commands.
Trinity
The bandwidth for the Trinity based PFE on an MX960 is about ~29G. So it's possible to overload the
fabric before the interfaces.
If you suspect fabric overloading from the PFE, You first need to identify each stream that is going from
the FPCs dropping packets (as identified above).
There's one fabric stream for each MqChip going to every other PFE in the chassis.
There are 4 stream IDs per FPC, so FPC 7 will have stream IDs 28, 29, 30 and 31, whereas FPC 8 will
have stream IDs 32, 33, 34 and 35.
FO Counters: