Re: [j-nsp] l2circuit down one side/up another

[Caio]

Hi Rafael,

Thanks for your help.
I have tried using explicit-null as it's a point-to-point (PE-to-PE) and as
there is no need for PHP, and it has worked as expected (the l2circuits
came up) but afterwards I have replaced the whole router to a better one
and the tunnels came up even without explicit-null set.
The physical path still the same, passing through LS SW (1) and LS SW (2).

So I could not know what went wrong with the previous router and as it's a
production environment, I don't think I could obtain permission test this
circuit ever again. So I think my doubt will last..

Cheers,
Caio


On Sat, Oct 21, 2017 at 7:53 AM, Rafael Ganascim 
wrote:

> Just more checks:
>
> How is the MPLS forwarding table for the negotiated Labels for loopback
> and l2circuit?
> Are you using label PHP? Can you switch It off?
> Is the LDP adjacency up and exchanging labels?
> Are the l2circuit neighbors configured between loopback interfaces?
>
> Regards,
>
>
>
>
> Em 20 de out de 2017 8:26 AM, "Caio"  escreveu:
>
>> Hello people,
>>
>> There's a weird problem I would like to share with you.
>> I have the following scenario:
>>
>> MX104 -> L2 SW (1) -> L2 SW (2) -> MX80
>>
>> Both L2 SW are Extreme X460 and they're doing nothing except forwarding
>> frames at layer 2.
>>
>> In order to simplify our topology, we have changed the MX104 uplink to L2
>> SW (2) so the topology went to MX104 -> L2 SW (2) -> MX80.
>>
>> After that, the BGP sessions went up and all the traffic has returned as
>> expected, however I have three l2circuit connections (vlan-ccc mode) and
>> they went to "Down (OL)" status at one side and Up at another. In order to
>> reestablish them we had to do a rollback of the physical changes we did.
>>
>> As it just don't make any sense to me, I summon you experts to help me
>> with
>> that, so we can try to figure out what went wrong.
>>
>> Additional details: I'm using LDP signaling at both sides. It' a point to
>> point L3 connection, so I have the loopback interfaces configured at both
>> sides and a /30 between them, also I have static routes to reach their
>> loopback interface's addresses.
>>
>> Any help will be appreciated.
>>
>> Cheers,
>> Caio
>> ___
>> 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] l2circuit down one side/up another

[Alexandre Guimaraes]

Caio,

Have you check something?

Are these extremes let the signaling pass thru?

att
Alexandre

Em 21 de out de 2017, à(s) 07:54, Rafael Ganascim 
> escreveu:

Just more checks:

How is the MPLS forwarding table for the negotiated Labels for loopback and
l2circuit?
Are you using label PHP? Can you switch It off?
Is the LDP adjacency up and exchanging labels?
Are the l2circuit neighbors configured between loopback interfaces?

Regards,




Em 20 de out de 2017 8:26 AM, "Caio" 
> escreveu:

Hello people,

There's a weird problem I would like to share with you.
I have the following scenario:

MX104 -> L2 SW (1) -> L2 SW (2) -> MX80

Both L2 SW are Extreme X460 and they're doing nothing except forwarding
frames at layer 2.

In order to simplify our topology, we have changed the MX104 uplink to L2
SW (2) so the topology went to MX104 -> L2 SW (2) -> MX80.

After that, the BGP sessions went up and all the traffic has returned as
expected, however I have three l2circuit connections (vlan-ccc mode) and
they went to "Down (OL)" status at one side and Up at another. In order to
reestablish them we had to do a rollback of the physical changes we did.

As it just don't make any sense to me, I summon you experts to help me with
that, so we can try to figure out what went wrong.

Additional details: I'm using LDP signaling at both sides. It' a point to
point L3 connection, so I have the loopback interfaces configured at both
sides and a /30 between them, also I have static routes to reach their
loopback interface's addresses.

Any help will be appreciated.

Cheers,
Caio
___
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
___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp

Re: [j-nsp] l2circuit down one side/up another

[Rafael Ganascim]

Just more checks:

How is the MPLS forwarding table for the negotiated Labels for loopback and
l2circuit?
Are you using label PHP? Can you switch It off?
Is the LDP adjacency up and exchanging labels?
Are the l2circuit neighbors configured between loopback interfaces?

Regards,




Em 20 de out de 2017 8:26 AM, "Caio"  escreveu:

> Hello people,
>
> There's a weird problem I would like to share with you.
> I have the following scenario:
>
> MX104 -> L2 SW (1) -> L2 SW (2) -> MX80
>
> Both L2 SW are Extreme X460 and they're doing nothing except forwarding
> frames at layer 2.
>
> In order to simplify our topology, we have changed the MX104 uplink to L2
> SW (2) so the topology went to MX104 -> L2 SW (2) -> MX80.
>
> After that, the BGP sessions went up and all the traffic has returned as
> expected, however I have three l2circuit connections (vlan-ccc mode) and
> they went to "Down (OL)" status at one side and Up at another. In order to
> reestablish them we had to do a rollback of the physical changes we did.
>
> As it just don't make any sense to me, I summon you experts to help me with
> that, so we can try to figure out what went wrong.
>
> Additional details: I'm using LDP signaling at both sides. It' a point to
> point L3 connection, so I have the loopback interfaces configured at both
> sides and a /30 between them, also I have static routes to reach their
> loopback interface's addresses.
>
> Any help will be appreciated.
>
> Cheers,
> Caio
> ___
> 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] l2circuit down one side/up another

[Caio]

*> Also, after your physical change, was ospf/isis  up on both sides?*

No OSPF/ISIS just static routes pointing to their loopbacks.

Cheers,
Caio

Em 20 de out de 2017 11:48 AM, "Daniel Rohan"  escreveu:

Also, after your physical change, was ospf/isis  up on both sides?

On Fri, Oct 20, 2017 at 6:12 AM Daniel Rohan  wrote:

> Did you change any of the physical interfaces as part of your topology
> change? And if so, is family mpls configured on that new port? Is that new
> port configured under protocols ldp and protocols mpls along with the
> loopback used for signaling?
>
> Do your control plane filters still permit ldp on both ends?
>
>
>
> Dan
>
> On Fri, Oct 20, 2017 at 3:26 AM Caio  wrote:
>
>> Hello people,
>>
>> There's a weird problem I would like to share with you.
>> I have the following scenario:
>>
>> MX104 -> L2 SW (1) -> L2 SW (2) -> MX80
>>
>> Both L2 SW are Extreme X460 and they're doing nothing except forwarding
>> frames at layer 2.
>>
>> In order to simplify our topology, we have changed the MX104 uplink to L2
>> SW (2) so the topology went to MX104 -> L2 SW (2) -> MX80.
>>
>> After that, the BGP sessions went up and all the traffic has returned as
>> expected, however I have three l2circuit connections (vlan-ccc mode) and
>> they went to "Down (OL)" status at one side and Up at another. In order to
>> reestablish them we had to do a rollback of the physical changes we did.
>>
>> As it just don't make any sense to me, I summon you experts to help me
>> with
>> that, so we can try to figure out what went wrong.
>>
>> Additional details: I'm using LDP signaling at both sides. It' a point to
>> point L3 connection, so I have the loopback interfaces configured at both
>> sides and a /30 between them, also I have static routes to reach their
>> loopback interface's addresses.
>>
>> Any help will be appreciated.
>>
>> Cheers,
>> Caio
>> ___
>> juniper-nsp mailing list juniper-nsp@puck.nether.net
>> https://puck.nether.net/mailman/listinfo/juniper-nsp
>>
> --
> Thanks, Dan
>
-- 
Thanks, Dan
___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp

Re: [j-nsp] l2circuit down one side/up another

[Saku Ytti]

On 20 October 2017 at 19:39,   wrote:

Hey,

>>  I had a hard time passing IS-IS thru Extreme Switch, give up after
>> 5m and used OSPF for that segment of our Pre-Prod Lab.
>
> There's nothing magic about IS-IS. We've had IS-IS running through
> Extreme switches many times (still have one such adjacency in our lab,
> running through one X460 and one X480). No problem.

Not proposing that 802.3 is magic, but I can imagine and have
experienced devices sensitive to ethertype value. Technically IS-IS
does not have ethertype, as that field is frame length. So switch
implementing ethernetII wouldn't even work incorrectly dropping IS-IS.
Hopefully we'll get IS-IS over ethernetII+IP some day.

-- 
  ++ytti
___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp

Re: [j-nsp] l2circuit down one side/up another

[Pavel Lunin]

No TE, no problem. Extreme knows how to do it reeeally wrong :) At least,
last time I checked.

But yes, at the basic level it works. Adjacency, LSAs etc.

20 окт. 2017 г. 6:39 ПП пользователь  написал:

>  I had a hard time passing IS-IS thru Extreme Switch, give up after
> 5m and used OSPF for that segment of our Pre-Prod Lab.

There's nothing magic about IS-IS. We've had IS-IS running through
Extreme switches many times (still have one such adjacency in our lab,
running through one X460 and one X480). No problem.

Steinar Haug, Nethelp consulting, sth...@nethelp.no
___
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] l2circuit down one side/up another

[sthaug]

>      I had a hard time passing IS-IS thru Extreme Switch, give up after 
> 5m and used OSPF for that segment of our Pre-Prod Lab.

There's nothing magic about IS-IS. We've had IS-IS running through
Extreme switches many times (still have one such adjacency in our lab,
running through one X460 and one X480). No problem.

Steinar Haug, Nethelp consulting, sth...@nethelp.no
___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp

Re: [j-nsp] l2circuit down one side/up another

[Alain Hebert]

    Alphabet soup mistake =D.  I never had a need for LDP alone.

-
Alain Hebertaheb...@pubnix.net
PubNIX Inc.
50 boul. St-Charles
P.O. Box 26770 Beaconsfield, Quebec H9W 6G7
Tel: 514-990-5911  http://www.pubnix.netFax: 514-990-9443

On 10/20/17 11:17, Aaron Gould wrote:

Why would you need rsvp for ldp ?  I don't think they have dependency on each 
other... As I understand it, you can use RSVP for label advertisement, OR, you 
can use LDP for label advertisement.  They are alternatives to each other.

-Aaron





___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp

Re: [j-nsp] l2circuit down one side/up another

[Aaron Gould]

Why would you need rsvp for ldp ?  I don't think they have dependency on each 
other... As I understand it, you can use RSVP for label advertisement, OR, you 
can use LDP for label advertisement.  They are alternatives to each other.

-Aaron


___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp

Re: [j-nsp] l2circuit down one side/up another

[Alain Hebert]

    Well,

    IS-IS or OSPF?

    Q: And don't you need at least RSVP for the LDP signaling? But 
since he didn't change nothing beside the L2 switches...  Not relevant 
(maybe).


    I had a hard time passing IS-IS thru Extreme Switch, give up after 
5m and used OSPF for that segment of our Pre-Prod Lab.


    ( Since its only for a redundant MX it don't matter much to 
perfectly match Prod for that part )


-
Alain Hebertaheb...@pubnix.net
PubNIX Inc.
50 boul. St-Charles
P.O. Box 26770 Beaconsfield, Quebec H9W 6G7
Tel: 514-990-5911  http://www.pubnix.netFax: 514-990-9443

On 10/20/17 10:39, Caio wrote:

*Did you change any of the physical interfaces as part of your topology

change? And if so, is family mpls configured on that new port? Is that new
port configured under protocols ldp and protocols mpls along with the
loopback used for signaling? *

No. Both of the MX routers are using the same interfaces.
The only thing that has changed was the switches  (l2 path) between them.

*Do your control plane filters still permit ldp on both ends*?

Yes

Cheers,
Caio


Em 20 de out de 2017 11:12 AM, "Daniel Rohan"  escreveu:

Did you change any of the physical interfaces as part of your topology
change? And if so, is family mpls configured on that new port? Is that new
port configured under protocols ldp and protocols mpls along with the
loopback used for signaling?

Do your control plane filters still permit ldp on both ends?



Dan

On Fri, Oct 20, 2017 at 3:26 AM Caio  wrote:


Hello people,

There's a weird problem I would like to share with you.
I have the following scenario:

MX104 -> L2 SW (1) -> L2 SW (2) -> MX80

Both L2 SW are Extreme X460 and they're doing nothing except forwarding
frames at layer 2.

In order to simplify our topology, we have changed the MX104 uplink to L2
SW (2) so the topology went to MX104 -> L2 SW (2) -> MX80.

After that, the BGP sessions went up and all the traffic has returned as
expected, however I have three l2circuit connections (vlan-ccc mode) and
they went to "Down (OL)" status at one side and Up at another. In order to
reestablish them we had to do a rollback of the physical changes we did.

As it just don't make any sense to me, I summon you experts to help me with
that, so we can try to figure out what went wrong.

Additional details: I'm using LDP signaling at both sides. It' a point to
point L3 connection, so I have the loopback interfaces configured at both
sides and a /30 between them, also I have static routes to reach their
loopback interface's addresses.

Any help will be appreciated.

Cheers,
Caio
___
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] l2circuit down one side/up another

[Caio]

> *Did you change any of the physical interfaces as part of your topology
change? And if so, is family mpls configured on that new port? Is that new
port configured under protocols ldp and protocols mpls along with the
loopback used for signaling? *

No. Both of the MX routers are using the same interfaces.
The only thing that has changed was the switches  (l2 path) between them.

*Do your control plane filters still permit ldp on both ends*?

Yes

Cheers,
Caio


Em 20 de out de 2017 11:12 AM, "Daniel Rohan"  escreveu:

Did you change any of the physical interfaces as part of your topology
change? And if so, is family mpls configured on that new port? Is that new
port configured under protocols ldp and protocols mpls along with the
loopback used for signaling?

Do your control plane filters still permit ldp on both ends?



Dan

On Fri, Oct 20, 2017 at 3:26 AM Caio  wrote:

> Hello people,
>
> There's a weird problem I would like to share with you.
> I have the following scenario:
>
> MX104 -> L2 SW (1) -> L2 SW (2) -> MX80
>
> Both L2 SW are Extreme X460 and they're doing nothing except forwarding
> frames at layer 2.
>
> In order to simplify our topology, we have changed the MX104 uplink to L2
> SW (2) so the topology went to MX104 -> L2 SW (2) -> MX80.
>
> After that, the BGP sessions went up and all the traffic has returned as
> expected, however I have three l2circuit connections (vlan-ccc mode) and
> they went to "Down (OL)" status at one side and Up at another. In order to
> reestablish them we had to do a rollback of the physical changes we did.
>
> As it just don't make any sense to me, I summon you experts to help me with
> that, so we can try to figure out what went wrong.
>
> Additional details: I'm using LDP signaling at both sides. It' a point to
> point L3 connection, so I have the loopback interfaces configured at both
> sides and a /30 between them, also I have static routes to reach their
> loopback interface's addresses.
>
> Any help will be appreciated.
>
> Cheers,
> Caio
> ___
> juniper-nsp mailing list juniper-nsp@puck.nether.net
> https://puck.nether.net/mailman/listinfo/juniper-nsp
>
-- 
Thanks, Dan
___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp

Re: [j-nsp] l2circuit down one side/up another

[Caio]

Same MTU 9216.
LDP neighborhood ok
Same loopback filters, the only change was the L2 path.

Cheers,
Caio

Em 20 de out de 2017 9:57 AM, "Alexandre Guimaraes" <
alexandre.guimar...@ascenty.com> escreveu:

MTU?

RSVP ISIS/OSPF LDP neighborhood are ok?

Loopback filters?

att
Alexandre

Em 20 de out de 2017, à(s) 08:26, Caio  escreveu:

Hello people,

There's a weird problem I would like to share with you.
I have the following scenario:

MX104 -> L2 SW (1) -> L2 SW (2) -> MX80

Both L2 SW are Extreme X460 and they're doing nothing except forwarding
frames at layer 2.

In order to simplify our topology, we have changed the MX104 uplink to L2
SW (2) so the topology went to MX104 -> L2 SW (2) -> MX80.

After that, the BGP sessions went up and all the traffic has returned as
expected, however I have three l2circuit connections (vlan-ccc mode) and
they went to "Down (OL)" status at one side and Up at another. In order to
reestablish them we had to do a rollback of the physical changes we did.

As it just don't make any sense to me, I summon you experts to help me with
that, so we can try to figure out what went wrong.

Additional details: I'm using LDP signaling at both sides. It' a point to
point L3 connection, so I have the loopback interfaces configured at both
sides and a /30 between them, also I have static routes to reach their
loopback interface's addresses.

Any help will be appreciated.

Cheers,
Caio
___
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] l2circuit down one side/up another

[Daniel Rohan]

Also, after your physical change, was ospf/isis  up on both sides?

On Fri, Oct 20, 2017 at 6:12 AM Daniel Rohan  wrote:

> Did you change any of the physical interfaces as part of your topology
> change? And if so, is family mpls configured on that new port? Is that new
> port configured under protocols ldp and protocols mpls along with the
> loopback used for signaling?
>
> Do your control plane filters still permit ldp on both ends?
>
>
>
> Dan
>
> On Fri, Oct 20, 2017 at 3:26 AM Caio  wrote:
>
>> Hello people,
>>
>> There's a weird problem I would like to share with you.
>> I have the following scenario:
>>
>> MX104 -> L2 SW (1) -> L2 SW (2) -> MX80
>>
>> Both L2 SW are Extreme X460 and they're doing nothing except forwarding
>> frames at layer 2.
>>
>> In order to simplify our topology, we have changed the MX104 uplink to L2
>> SW (2) so the topology went to MX104 -> L2 SW (2) -> MX80.
>>
>> After that, the BGP sessions went up and all the traffic has returned as
>> expected, however I have three l2circuit connections (vlan-ccc mode) and
>> they went to "Down (OL)" status at one side and Up at another. In order to
>> reestablish them we had to do a rollback of the physical changes we did.
>>
>> As it just don't make any sense to me, I summon you experts to help me
>> with
>> that, so we can try to figure out what went wrong.
>>
>> Additional details: I'm using LDP signaling at both sides. It' a point to
>> point L3 connection, so I have the loopback interfaces configured at both
>> sides and a /30 between them, also I have static routes to reach their
>> loopback interface's addresses.
>>
>> Any help will be appreciated.
>>
>> Cheers,
>> Caio
>> ___
>> juniper-nsp mailing list juniper-nsp@puck.nether.net
>> https://puck.nether.net/mailman/listinfo/juniper-nsp
>>
> --
> Thanks, Dan
>
-- 
Thanks, Dan
___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp

Re: [j-nsp] l2circuit down one side/up another

[Daniel Rohan]

Did you change any of the physical interfaces as part of your topology
change? And if so, is family mpls configured on that new port? Is that new
port configured under protocols ldp and protocols mpls along with the
loopback used for signaling?

Do your control plane filters still permit ldp on both ends?



Dan

On Fri, Oct 20, 2017 at 3:26 AM Caio  wrote:

> Hello people,
>
> There's a weird problem I would like to share with you.
> I have the following scenario:
>
> MX104 -> L2 SW (1) -> L2 SW (2) -> MX80
>
> Both L2 SW are Extreme X460 and they're doing nothing except forwarding
> frames at layer 2.
>
> In order to simplify our topology, we have changed the MX104 uplink to L2
> SW (2) so the topology went to MX104 -> L2 SW (2) -> MX80.
>
> After that, the BGP sessions went up and all the traffic has returned as
> expected, however I have three l2circuit connections (vlan-ccc mode) and
> they went to "Down (OL)" status at one side and Up at another. In order to
> reestablish them we had to do a rollback of the physical changes we did.
>
> As it just don't make any sense to me, I summon you experts to help me with
> that, so we can try to figure out what went wrong.
>
> Additional details: I'm using LDP signaling at both sides. It' a point to
> point L3 connection, so I have the loopback interfaces configured at both
> sides and a /30 between them, also I have static routes to reach their
> loopback interface's addresses.
>
> Any help will be appreciated.
>
> Cheers,
> Caio
> ___
> juniper-nsp mailing list juniper-nsp@puck.nether.net
> https://puck.nether.net/mailman/listinfo/juniper-nsp
>
-- 
Thanks, Dan
___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp

Re: [j-nsp] l2circuit down one side/up another

[Alexandre Guimaraes]

MTU?

RSVP ISIS/OSPF LDP neighborhood are ok?

Loopback filters?

att
Alexandre

Em 20 de out de 2017, à(s) 08:26, Caio 
> escreveu:

Hello people,

There's a weird problem I would like to share with you.
I have the following scenario:

MX104 -> L2 SW (1) -> L2 SW (2) -> MX80

Both L2 SW are Extreme X460 and they're doing nothing except forwarding
frames at layer 2.

In order to simplify our topology, we have changed the MX104 uplink to L2
SW (2) so the topology went to MX104 -> L2 SW (2) -> MX80.

After that, the BGP sessions went up and all the traffic has returned as
expected, however I have three l2circuit connections (vlan-ccc mode) and
they went to "Down (OL)" status at one side and Up at another. In order to
reestablish them we had to do a rollback of the physical changes we did.

As it just don't make any sense to me, I summon you experts to help me with
that, so we can try to figure out what went wrong.

Additional details: I'm using LDP signaling at both sides. It' a point to
point L3 connection, so I have the loopback interfaces configured at both
sides and a /30 between them, also I have static routes to reach their
loopback interface's addresses.

Any help will be appreciated.

Cheers,
Caio
___
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