Re: [j-nsp] Uplink failure detection in EX series
Yes, it will come out in EX in 11.1 in Mar. On Wed, Mar 16, 2011 at 12:16 AM, Richard A Steenbergen r...@e-gerbil.netwrote: On Tue, Mar 15, 2011 at 12:25:59PM +0100, Tore Anderson wrote: Hi, I'm wondering if it possible to configure something equivalent to the EX2500's Uplink Failure Detection on the JUNOS-based EX series switches? I want to designate a couple of interfaces as uplink ports, and if they all go down, all the other ports on the switch should be disabled as well. I think uplink failure detection is on the roadmap for 11.1, though I'm not sure about the EX-specificness of it. -- Richard A Steenbergen r...@e-gerbil.net http://www.e-gerbil.net/ras GPG Key ID: 0xF8B12CBC (7535 7F59 8204 ED1F CC1C 53AF 4C41 5ECA F8B1 2CBC) ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp -- BR! James Chen ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
[j-nsp] Uplink failure detection in EX series
Hi, I'm wondering if it possible to configure something equivalent to the EX2500's Uplink Failure Detection on the JUNOS-based EX series switches? I want to designate a couple of interfaces as uplink ports, and if they all go down, all the other ports on the switch should be disabled as well. I want to avoid repeats of an interesting failure I just experienced: an EX top-of-rack switch lost both its uplinks simultaneously, most likely due to lacpd failing to do its job - both uplinks were 802.3ad LAGs, and rebooting the switch solved the problem in the end. In any case, since the downstream access ports stayed up, the servers didn't fail over to the other switch in the rack and therefore lost connectivity. So much for redundancy... :-/ Best regards, -- Tore Anderson Redpill Linpro AS - http://www.redpill-linpro.com Tel: +47 21 54 41 27 ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: [j-nsp] Uplink failure detection in EX series
On Tue, Mar 15, 2011 at 7:25 AM, Tore Anderson tore.ander...@redpill-linpro.com wrote: Hi, I'm wondering if it possible to configure something equivalent to the EX2500's Uplink Failure Detection on the JUNOS-based EX series switches? I want to designate a couple of interfaces as uplink ports, and if they all go down, all the other ports on the switch should be disabled as well. I'm not aware of a protocol that can shut down switchports. There's something in the optical world that will shut down a gig port if the sonet links it traverses flap, but that wouldn't help here. Op-scripts maybe? I want to avoid repeats of an interesting failure I just experienced: an EX top-of-rack switch lost both its uplinks simultaneously, most likely due to lacpd failing to do its job - both uplinks were 802.3ad LAGs, and rebooting the switch solved the problem in the end. That sounds like a bug of some sort. I'd probably fix it by upgrading to code where the bug was fixed. What code are you running? In any case, since the downstream access ports stayed up, the servers didn't fail over to the other switch in the rack and therefore lost connectivity. So much for redundancy... :-/ Maybe you can write a script that pings out periodically and fails over the bundles if the ping fails. Probably easier than opscripts. If not there's always spanning-tree. ;) Best regards, -- Tore Anderson Redpill Linpro AS - http://www.redpill-linpro.com Tel: +47 21 54 41 27 ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: [j-nsp] Uplink failure detection in EX series
Hi, * Keegan Holley I'm not aware of a protocol that can shut down switchports. There's something in the optical world that will shut down a gig port if the sonet links it traverses flap, but that wouldn't help here. Op-scripts maybe? The EX2500 has the required functionality, the Cisco Nexus fabric extenders too (or so I'm told). I want to avoid repeats of an interesting failure I just experienced: an EX top-of-rack switch lost both its uplinks simultaneously, most likely due to lacpd failing to do its job - both uplinks were 802.3ad LAGs, and rebooting the switch solved the problem in the end. That sounds like a bug of some sort. I'd probably fix it by upgrading to code where the bug was fixed. What code are you running? No doubt a bug, and probably fixable by upgrading - the switch in question was running 10.1R1.8... However, it would be nice to have such functionality in any case. I would not need to waste ports on dual uplinks, for example. Maybe you can write a script that pings out periodically and fails over the bundles if the ping fails. Probably easier than opscripts. If not there's always spanning-tree. ;) I think both those approaches would cause more problems than they solve. The Linux bonding driver actually has ping based probing functionality, but from experience, the ping target is more likely to go down than anything else happening (or, if it was found on the same switch, it wouldn't help at all). And STP just terrifies me - I try to rely on it as little as possible. Best regards, -- Tore Anderson Redpill Linpro AS - http://www.redpill-linpro.com Tel: +47 21 54 41 27 ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: [j-nsp] Uplink failure detection in EX series
On Tue, Mar 15, 2011 at 12:25:59PM +0100, Tore Anderson wrote: Hi, I'm wondering if it possible to configure something equivalent to the EX2500's Uplink Failure Detection on the JUNOS-based EX series switches? I want to designate a couple of interfaces as uplink ports, and if they all go down, all the other ports on the switch should be disabled as well. I think uplink failure detection is on the roadmap for 11.1, though I'm not sure about the EX-specificness of it. -- Richard A Steenbergen r...@e-gerbil.net http://www.e-gerbil.net/ras GPG Key ID: 0xF8B12CBC (7535 7F59 8204 ED1F CC1C 53AF 4C41 5ECA F8B1 2CBC) ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
