[f-nsp] Packet loss on MLXe-4

Frank Bulk frnkblk at iname.com
Tue Sep 17 17:50:47 EDT 2013


Thanks for the suggestions. I believe I checked the sfm utilization during
the maintenance window, and there were no sfm errors.  But we did not try
powering off one at a time.  We'll have to try that.

 

TM's didn't throw errors and appeared clean.

 

Regards,

 

Frank Bulk

 

From: Mike Tindle [mailto:mtindle at he.net] 
Sent: Tuesday, September 17, 2013 4:43 PM
To: Frank Bulk
Cc: foundry-nsp at puck.nether.net
Subject: Re: [f-nsp] Packet loss on MLXe-4

 

If you're getting loss between cards but not while traffic stays on a card,
check your (h)SFMs.  You can usually take one out of service without impact.
You can see their load with "sh sfm-ut all" and then walk them off one at a
time ("power-off snm [#]") to see if the packet loss goes away.   You can
also see if they're having issues with "sh sfm-link all err" but I believe
that would have shown up in logs. 

 

We've found a couple bad ones this way and they can be an absolute nightmare
to discover since they'll report everything fine. 

 

The other option could be a bad TM on a card but those usually throw errors
as well. 

 

Regards,

Mike

  

 

On Sep 17, 2013, at 1:17 PM, Frank Bulk <frnkblk at iname.com
<mailto:frnkblk at iname.com> > wrote:





We inserted an MLXe-4 into a Brocade ring this morning and it didn't go so
well.  We saw most IP video traffic (1.3 Gbps) not flow through, and when we
moved an inter-border router link from eth 1/2 to eth 2/2 we saw significant
packet loss on other Internet VLANs (all on eth 1/x).  Moving it back
resolved the issue.

We have two SFMs and have two four-port 10G cards, one is a NI-XMR-10Gx4 and
the other is a BR-MLX-10Gx4-X.  We also have a BR-MLX-1GCx24-X in slot 3
that we're not using, yet.  We're running 5.4.0d and the FPGAs are at the
correct releases.

The ring goes in one 10G port on the one 10G card and through another 10G
port on the other 10G card.

Are there any compatibility issues between the two cards?  Placement
requirements?  Any obvious reasons why we experienced all that traffic loss?

Regards,

Frank



_______________________________________________
foundry-nsp mailing list
foundry-nsp at puck.nether.net <mailto:foundry-nsp at puck.nether.net> 
http://puck.nether.net/mailman/listinfo/foundry-nsp

 

*----------- H U R R I C A N E - E L E C T R I C ---------->>
| Mike Tindle | Senior Network Engineer | mtindle at he.net
<mailto:mtindle at he.net> 
| ASN 6939 | http://www.he.net | 510-580-4126
*--------------------------------------------------->>

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/foundry-nsp/attachments/20130917/956afea2/attachment.html>


More information about the foundry-nsp mailing list