[prev in list] [next in list] [prev in thread] [next in thread] 

List:       juniper-nsp
Subject:    Re: [j-nsp] routing vpls
From:       Cydon Satyr <cydonsatyr () gmail ! com>
Date:       2018-01-04 9:00:44
Message-ID: CAF0PUwcoVEDajKMk=nGvpGe=rNT9cb54a-tyB1Eh1RADbeaZxw () mail ! gmail ! com
[Download RAW message or body]

Hi all,

Anyone have some experience with this; what might be wrong with the
configuration?

Thanks



On Thu, Dec 28, 2017 at 4:41 PM, Cydon Satyr <cydonsatyr@gmail.com> wrote:

> Hi.
> The way I understood IRB in VPLS is like this - if you have CE interface
> down, then VPLS should be down, unless you have connectivity-type irb
> configured inside VPLS instance.
>
> This is the config:
>
> instance-type vpls;
> vlan-id 123;
> interface ge-1/2/3.123;
> routing-interface irb.123;
> protocols {
>     vpls {
>         no-tunnel-services;
>         vpls-id 123;
>         neighbor a.b.c.d;
>     }
> }
>
> By default, if my ge-1/2/3.0 is physically down, VPLS instance should be
> down.
> Except it isn't.
>
> # run show interfaces ge-1/2/3.123
>   Logical interface...
>     Description: ...
>     Flags: *Device-Down *SNMP-Traps 0x4000 VLAN-Tag [ 0x8100.123 ]
> Encapsulation: VLAN-VPLS
>     Input packets : 0
>     Output packets: 0
>
>
> Instance: vpls-123
>   VPLS-id: 123
>     Neighbor...
>     a.b.c.d(vpls-id 123)
>
>
> *rmt Up  ...*
> I want instance to be signaled down if my only subinterface is down, is
> this possible?
>
> thanks all
>
_______________________________________________
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp
[prev in list] [next in list] [prev in thread] [next in thread]