Re: [j-nsp] Same configuration

[Hugo Slabbert]

On Thu 2017-Oct-19 17:38:43 +0500, sameer mughal  
wrote:



Hi All,

Can anyone update me that Is the same configuration on srx240h2 will work
on srx550 or need some modification?


Try it and see?

Depends on the extent of the config.  There are some things that are 
model-specific, such as which ports are used/hardcoded/available for 
chassis cluster links.  But, the 240 and 550 are both branch series, so I 
would not expect too much difference there, especially if you're just using 
a single unit rather than chassis cluster.


--
Hugo Slabbert   | email, xmpp/jabber: h...@slabnet.com
pgp key: B178313E   | also on Signal



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

Re: [j-nsp] juniper-nsp Digest, Vol 179, Issue 20

[Aaron Gould]

I just reread my response, or you might have 2 problems... one with the
filter and one elsewhere...

-Aaron


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

Re: [j-nsp] juniper-nsp Digest, Vol 179, Issue 20

[Aaron Gould]

Or remove the filter for a moment... if all works then you know there's an
issue with the filter... if it still doesn't work, then you know your
problem is elsewhere.

-Aaron


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

Re: [j-nsp] Logical systems plus ldp/l2circuit

[Aaron Gould]

My working lsys-based ldp l2circuit (aka martini) config...

r2@lab-mx104:r2> show configuration protocols l2circuit | display set
set logical-systems r2 protocols l2circuit neighbor 1.1.255.6 interface
lt-0/1/0.210 virtual-circuit-id 1

r2@lab-mx104:r2> show configuration interfaces lt-0/1/0.210 | display set
set logical-systems r2 interfaces lt-0/1/0 unit 210 encapsulation
ethernet-ccc
set logical-systems r2 interfaces lt-0/1/0 unit 210 peer-unit 102

r2@lab-mx104:r2> show route 1.1.255.6 protocol ldp

inet.3: 6 destinations, 6 routes (6 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both

1.1.255.6/32   *[LDP/9] 2w4d 14:46:32, metric 1
  to 1.1.7.2 via lt-0/1/0.27, Push 305152
> to 1.1.1.2 via lt-0/1/0.3, Push 304096

r2@lab-mx104:r2> show l2circuit connections brief | find Neigh
Neighbor: 1.1.255.6
Interface Type  St Time last up  # Up trans
lt-0/1/0.210(vc 1)rmt   Up Oct  2 23:16:46 2017   1


--


r6@lab-mx104:r6> show configuration protocols l2circuit | display set
set logical-systems r6 protocols l2circuit neighbor 1.1.255.2 interface
lt-1/1/0.611 virtual-circuit-id 1

r6@lab-mx104:r6> show configuration interfaces lt-1/1/0.611 | display set
set logical-systems r6 interfaces lt-1/1/0 unit 611 encapsulation
ethernet-ccc
set logical-systems r6 interfaces lt-1/1/0 unit 611 peer-unit 116

r6@lab-mx104:r6> show route 1.1.255.2 protocol ldp

inet.3: 6 destinations, 6 routes (6 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both

1.1.255.2/32   *[LDP/9] 2w4d 16:13:27, metric 1
> to 1.1.6.1 via lt-0/1/0.63, Push 304048
  to 1.1.11.1 via lt-0/1/0.67, Push 305136


r6@lab-mx104:r6> show l2circuit connections brief | find Neigh
Neighbor: 1.1.255.2
Interface Type  St Time last up  # Up trans
lt-1/1/0.611(vc 1)rmt   Up Oct  2 23:16:46 2017   1



-Aaron

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

Re: [j-nsp] juniper-nsp Digest, Vol 179, Issue 20

[Brijesh Patel]

Hi

Is MX router has firewall filter on loop back?

If so pleae make sure ldp related port and IP address allow

Thanks

Brijesh

On Saturday, October 21, 2017,  wrote:

> Send juniper-nsp mailing list submissions to
> juniper-nsp@puck.nether.net 
>
> To subscribe or unsubscribe via the World Wide Web, visit
> https://puck.nether.net/mailman/listinfo/juniper-nsp
> or, via email, send a message with subject or body 'help' to
> juniper-nsp-requ...@puck.nether.net 
>
> You can reach the person managing the list at
> juniper-nsp-ow...@puck.nether.net 
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of juniper-nsp digest..."
>
>
> Today's Topics:
>
>1. Re: l2circuit down one side/up another (Rafael Ganascim)
>2. Re: l2circuit down one side/up another (Alexandre Guimaraes)
>
>
> --
>
> Message: 1
> Date: Sat, 21 Oct 2017 07:53:16 -0200
> From: Rafael Ganascim >
> To: Caio >
> Cc: juniper-nsp >
> Subject: Re: [j-nsp] l2circuit down one side/up another
> Message-ID:
> <
> cad4zomx2nc0u78l5ortiwekwqi58tf2ch07z1q4iy505mtk...@mail.gmail.com
> >
> Content-Type: text/plain; charset="UTF-8"
>
> 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
> >
>
>
> --
>
> Message: 2
> Date: Sat, 21 Oct 2017 10:42:21 +
> From: Alexandre Guimaraes >
> To: Rafael Ganascim >
> Cc: Caio >, juniper-nsp <
> juniper-nsp@puck.nether.net >
> Subject: Re: [j-nsp] l2circuit down one side/up another
> Message-ID: <727f7b43-688c-4dbf-9a6d-c7b6b32c1...@ascenty.com
> >
> Content-Type: text/plain; charset="utf-8"
>
> 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 

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