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

2017-10-22 Thread Caio 
Thanks guys,
I have successfully installed the new router using Lsys and it has worked
as expected (running a LOT of l2circuits through Lsys now).

However, there's a lot of bugs in my JunOS version (16.1R4.7) regarding
Lsys.
The most annoying bug that I've found is the logical tunnel interfaces (LT)
going down after a massive configuration changes (costumer groups, physical
interfaces configurations... nothing related to the LT).

I heard about Node Slicing and that it's a 'less buggy' implementation of
pretty much for the same purpose.
What do you guys think of that ? Is it better than logical systems?
What about flow exporting, do you know if may it accept different addresses
as sources for flow exporting (like real routers) ?

Cheers,
Caio

On Sat, Oct 21, 2017 at 2:12 PM, Aaron Gould  wrote:

>
> 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] Logical systems plus ldp/l2circuit

2017-10-21 Thread 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] Logical systems plus ldp/l2circuit

2017-10-20 Thread Eduardo Schoedler 
Em sáb, 21 de out de 2017 às 01:51, Caio  escreveu:

> Hi again everyone,
> Another question I would like to ask for whoever worked with Lsys:
>
> Is ldp neighborhood supposed to work with Lsys?



Yes, working here.
Ending a vpls into a IRB interface for main instance.

Lsys is a completly another router, it has his own rpd process

You have to create all the interfaces (including loopback) for the
instance, and specify his addresses into it.

—
Eduardo Schoedler

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

[j-nsp] Logical systems plus ldp/l2circuit

2017-10-20 Thread Caio 
Hi again everyone,
Another question I would like to ask for whoever worked with Lsys:

Is ldp neighborhood supposed to work with Lsys?
I have a scenario in which there is a physical MX104 router and I need to
create an adjacency with a Lsys at a MX480 router, however after I enabled
family mpls, protocols LDP and protocols mpls for both the subinterface and
the loopback, there's still no neighborhood between them.
The physical topology is:
MX104 -> L2 SW (1) -> L2 SW (2) -> MX480
The L2 SW (1) is an Extreme X460 and L2 SW (2) is a Cisco Nexus 3064pq and
they are both just forwarding L2 frames.

Once again, any help would be appreciated.

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