Mailing List Archive: trying to add double tagged interface and getting errors

trying to add double tagged interface and getting errors

Nov 21, 2019, 12:13 PM

Post #1 of 3 (1303 views)

How would I accomplish this ? It's working fine, but when I try to add a
double tagged interface into the existing vpls bridging environment, I get
the following error.

me@ 204-1> show configuration routing-instances 100 | display set

set routing-instances 100 instance-type vpls

set routing-instances 100 vlan-id none

set routing-instances 100 interface xe-0/1/4.100

set routing-instances 100 routing-interface irb.100

set routing-instances 100 protocols vpls no-tunnel-services

set routing-instances 100 protocols vpls vpls-id 10000

set routing-instances 100 protocols vpls mtu 1500

set routing-instances 100 protocols vpls neighbor 10.102.255.7

me@ 204-1> show configuration interfaces xe-0/1/1 | display set

set interfaces xe-0/1/1 flexible-vlan-tagging

set interfaces xe-0/1/1 mtu 9216

set interfaces xe-0/1/1 encapsulation flexible-ethernet-services

set interfaces xe-0/1/1 unit 300 vlan-tags outer 300

set interfaces xe-0/1/1 unit 300 vlan-tags inner 100

set interfaces xe-0/1/1 unit 300 input-vlan-map pop-pop

set interfaces xe-0/1/1 unit 300 output-vlan-map push-push

me@204-1# set routing-instances 100 interface xe-0/1/1.300

[edit]

me@ 204-1# commit check

[edit routing-instances 100 interface]

'xe-0/1/1.300'

interface with input/output vlan-maps cannot be added to a
routing-instance with a vlan-id/vlan-tags configured

error: configuration check-out failed: (statements constraint check failed)

-Aaron

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

Re: trying to add double tagged interface and getting errors [ In reply to ]

ckawchuk at gmail

Nov 21, 2019, 1:51 PM

Post #2 of 3 (1302 views)

Permalink

Remove the pop-pop and push-push statements against unit xe-0/1/1.300.

JunOS will auto magically "remove" and "add" the VLAN tags to the VPLS attachment circuit; since you have declared "vlan-id none" in the VPLS definition. (no tags)

It's basically saying "don't try to do manual vlan tag manipulation on this attachment circuit (unit) - We will do it for you in order to "normalise" the tags to "nothing"

https://www.juniper.net/documentation/en_US/junos-space16.1/topics/concept/layer2-provisioning-vlan-manipulation-understanding.html <https://www.juniper.net/documentation/en_US/junos-space16.1/topics/concept/layer2-provisioning-vlan-manipulation-understanding.html>

Basically -- You can only do pop/push operations where you have not declared any vlan-id inside a VPLS; (i.e. the vlan <x> statement is completely absent -- meaning you want do your own normalisation), however you need a vlan-id <x> statement for an irb.x to work; hence you need to let JunOS "do it's thing" and do the pop-swap for you in your case....

- Ck.

> On 22 Nov 2019, at 7:13 am, Aaron Gould <aaron1@gvtc.com> wrote:
>
> How would I accomplish this ? It's working fine, but when I try to add a
> double tagged interface into the existing vpls bridging environment, I get
> the following error.
>
>
>
> me@ 204-1> show configuration routing-instances 100 | display set
>
> set routing-instances 100 instance-type vpls
>
> set routing-instances 100 vlan-id none
>
> set routing-instances 100 interface xe-0/1/4.100
>
> set routing-instances 100 routing-interface irb.100
>
> set routing-instances 100 protocols vpls no-tunnel-services
>
> set routing-instances 100 protocols vpls vpls-id 10000
>
> set routing-instances 100 protocols vpls mtu 1500
>
> set routing-instances 100 protocols vpls neighbor 10.102.255.7
>
>
>
> me@ 204-1> show configuration interfaces xe-0/1/1 | display set
>
> set interfaces xe-0/1/1 flexible-vlan-tagging
>
> set interfaces xe-0/1/1 mtu 9216
>
> set interfaces xe-0/1/1 encapsulation flexible-ethernet-services
>
> set interfaces xe-0/1/1 unit 300 vlan-tags outer 300
>
> set interfaces xe-0/1/1 unit 300 vlan-tags inner 100
>
> set interfaces xe-0/1/1 unit 300 input-vlan-map pop-pop
>
> set interfaces xe-0/1/1 unit 300 output-vlan-map push-push
>
>
>
> me@204-1# set routing-instances 100 interface xe-0/1/1.300
>
>
>
> [edit]
>
> me@ 204-1# commit check
>
> [edit routing-instances 100 interface]
>
> 'xe-0/1/1.300'
>
> interface with input/output vlan-maps cannot be added to a
> routing-instance with a vlan-id/vlan-tags configured
>
> error: configuration check-out failed: (statements constraint check failed)
>
>
>
>
> -Aaron
>
> _______________________________________________
> 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: trying to add double tagged interface and getting errors [ In reply to ]

aaron1 at gvtc

Nov 21, 2019, 2:58 PM

Post #3 of 3 (1300 views)

Permalink

Very nice, the config works now! (I had to add vpls encap to the subints of
course)

And I see the interface shows pop-pop push-push still

Thanks!

set routing-instances 100 interface xe-0/1/1.300

set routing-instances 100 interface xe-0/1/1.312

delete interfaces xe-0/1/1 unit 300 input-vlan-map pop-pop

delete interfaces xe-0/1/1 unit 300 output-vlan-map push-push

delete interfaces xe-0/1/1 unit 312 input-vlan-map pop-pop

delete interfaces xe-0/1/1 unit 312 output-vlan-map push-push

set interfaces xe-0/1/1 unit 300 encapsulation vlan-vpls

set interfaces xe-0/1/1 unit 312 encapsulation vlan-vpls

me@204-1> show interfaces xe-0/1/1.300

Logical interface xe-0/1/1.300 (Index 336) (SNMP ifIndex 534)

Flags: Up SNMP-Traps 0x4000 VLAN-Tag [ 0x8100.300 0x8100.100 ]
In(pop-pop) Out(push-push 0x8100.300 0x8100.100) Encapsulation: VLAN-VPLS

Input packets : 0

Output packets: 0

Protocol vpls, MTU: 9216

me@204-1> show interfaces xe-0/1/1.312

Logical interface xe-0/1/1.312 (Index 341) (SNMP ifIndex 535)

Flags: Up SNMP-Traps 0x4000 VLAN-Tag [ 0x8100.312 0x8100.100 ]
In(pop-pop) Out(push-push 0x8100.312 0x8100.100) Encapsulation: VLAN-VPLS

Input packets : 0

Output packets: 0

Protocol vpls, MTU: 9216

- Aaron

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