Mailing List Archive

W dniu 16.09.2012 15:55, Stephane Grosjean pisze:
> Hi,
>
> Your description of the issue seems to show a TCP problem. Both LDP and
> BGP have a problem. Not sure this is an Extreme problem though. No idea
> of what's between the two switches?
>
> Stef
>

Hello,

BGP sessions are handled by other hardware, not extremes - extremes are
only doing L2 for them. So problem is not TCP. We also have some other
VLANs, but not MPLS enabled ant they just work fine. So definitely
something is broken with LDP.

Thanks


--
Micha³ Margula, alchemyx@uznam.net.pl, http://alchemyx.uznam.net.pl/
"W ¿yciu piêkne s± tylko chwile" [Ryszard Riedel]
_______________________________________________
extreme-nsp mailing list
extreme-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/extreme-nsp

W dniu 18.09.2012 11:56, Stephane Grosjean pisze:
> Hi Michal,
>
> As I don't know your setup, I'm only speculating.
> Can you detail the layout of the network a bit? On what BGP is relying, etc.
>
>
> Regards,
>
> Stef

OK!

I have two 1gig optical links between Cisco 6500-SUP720-3bxl and Extreme
X480-24x.

172.16.250.1/24 - Cisco, Link 1
172.16.249.1/24 - Cisco, Link 2

172.16.250.2/24 - Extreme, Link 1
172.16.249.2/24 - Extreme, Link 2

172.16.251.1/32 - Loopback on Cisco
172.16.251.2/32 - Loopback on Extreme

OSPF running on both links and advertising loopbacks. OSPF is UP,
everything is pingable and so on. MPLS LDP running on both links just
fine, defined three VPWS (Extreme side):

create l2vpn vpws MPLS-Jambox fec-id-type pseudo-wire 10
configure l2vpn vpws MPLS-Jambox add service vman Jambox
configure l2vpn vpws MPLS-Jambox mtu 1504
configure l2vpn vpws MPLS-Jambox add peer 172.16.251.1

And so on... Everything works fine, passing by traffic to Cisco. Then
after one of following things:

- physical disconnect of both links
- port shutdown on Cisco of both ports
- port disable on Extreme of both ports

And then recovering (reconnecting a cable, no shutdown or enable) LDP
fails to come back up, altough OSPF works just fine, everything is
pingable and so on. Extreme doesn't see its neighbors, Cisco doesn't see
Extreme. I have to do "disable mpls ldp vlan X" and "enable mpls ldp
vlan X" to make it work again. There is nothing I can do on Cisco to fix
it, so it is clearly problem on Extreme.

Conclusion: LDP doesn't recover after link failure. Why? Probably
software bug?

--
Micha³ Margula, alchemyx@uznam.net.pl, http://alchemyx.uznam.net.pl/
"W ¿yciu piêkne s± tylko chwile" [Ryszard Riedel]
_______________________________________________
extreme-nsp mailing list
extreme-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/extreme-nsp

W dniu 18.09.2012 12:10, Micha³ Margula pisze:
> I have two 1gig optical links between Cisco 6500-SUP720-3bxl and Extreme
> X480-24x.

Another thing - yesterday we had fiber cut on one links and after fixing
that LDP came up properly. So it seems that problem starts when both
links die and Loopback address disappears from OSPF.


--
Micha³ Margula, alchemyx@uznam.net.pl, http://alchemyx.uznam.net.pl/
"W ¿yciu piêkne s± tylko chwile" [Ryszard Riedel]
_______________________________________________
extreme-nsp mailing list
extreme-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/extreme-nsp

W dniu 22.09.2012 20:50, Stephane Grosjean pisze:
> Did you open an SR with Extreme TAC?
>

Hello,

No I didn't because I can't. It seems that every issue I need to report
to my retailer and he then contacts Extreme.

--
Micha³ Margula, alchemyx@uznam.net.pl, http://alchemyx.uznam.net.pl/
"W ¿yciu piêkne s± tylko chwile" [Ryszard Riedel]
_______________________________________________
extreme-nsp mailing list
extreme-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/extreme-nsp

W dniu 26.09.2012 11:45, Stephane Grosjean pisze:
> Hi,
>
>
> if it's a bug, that's the only way, ask your retailer to open a case on
> that matter.
>
> When losing the loopback in ospf, sure LDP has an issue. It should work
> when they are reachable again, maybe after OSPF (depends on the timer)
> so it could lead to some issue for mpls (and so vpls) in the meantime,
> while pure IP is not affected (LDP has to resignal the labels for mpls
> traffic). Did you wait long enough to see if it's working back after the
> timers of LDP are hit? If so, that's weird, so open a case. If not,
> maybe that's the issue and some tuning of the timers could help.
>


Hello,

I even did a test that took 30 minutes, so every possible timer should
be OK. But as Marcin suggested I will try IS-IS and see if it happens also.

Thanks!

--
Micha³ Margula, alchemyx@uznam.net.pl, http://alchemyx.uznam.net.pl/
"W ¿yciu piêkne s± tylko chwile" [Ryszard Riedel]
_______________________________________________
extreme-nsp mailing list
extreme-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/extreme-nsp

W dniu 26.09.2012 21:40, Micha³ Margula pisze:
>
> Hello,
>
> I even did a test that took 30 minutes, so every possible timer should
> be OK. But as Marcin suggested I will try IS-IS and see if it happens also.
>
> Thanks!
>

Hello,

I have found source of all that trouble with MPLS. It was caused by
default gateway configured on switches. After removing it everything
comes back up fine in about 90 seconds (MPLS + LDP + EoMPLS).

So for me it is still a bug but somewhat solved.

Have a nice day!

--
Micha³ Margula, alchemyx@uznam.net.pl, http://alchemyx.uznam.net.pl/
"W ¿yciu piêkne s± tylko chwile" [Ryszard Riedel]
_______________________________________________
extreme-nsp mailing list
extreme-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/extreme-nsp