[j-nsp] VPLS q-in-q
Mark Tees
marktees at gmail.com
Wed May 20 09:04:49 EDT 2020
Assuming 00:22:07:4d:7b:0d is the MAC behind the Juniper and the PCAP
is on NIC of the host connected to the ZTE.
At a guess the ZTE doing something different on ingress than what I am
thinking here.
If you can verify by PCAP on MPLS interface it would be handy to see
what each side is doing in each direction. Juniper MX operations in
this regards have usually been pretty explicit.
On Wed, 20 May 2020 at 22:49, Baldur Norddahl <baldur at gigabit.dk> wrote:
>
> I tried this and we got closer but it is replacing both inner and outer
> tags now:
>
> 12:48:27.320821 00:22:07:4d:7b:0d > ff:ff:ff:ff:ff:ff, ethertype 802.1Q
> (0x8100), length 350: vlan 424, p 0, ethertype 802.1Q, vlan 424, p 0,
> ethertype IPv4, 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request
> from 00:22:07:4d:7b:0d, length 300
>
> That should have been outer 424 inner 201.
>
> The config:
>
> baldur at formervangen-edge1# show interfaces xe-0/1/7
> flexible-vlan-tagging;
> native-vlan-id 424;
> encapsulation flexible-ethernet-services;
> unit 424 {
> encapsulation vlan-vpls;
> vlan-id 424;
> input-vlan-map pop;
> output-vlan-map push;
> }
>
> [edit]
> baldur at formervangen-edge1# commit
> commit complete
>
> [edit]
> baldur at formervangen-edge1# show routing-instances poi-formervangen |
> display inheritance brief
> protocols {
> vpls {
> ## 'ethernet-vlan' was inherited from group 'POI-VPLS'
> encapsulation-type ethernet-vlan;
> ## 'no-control-word' was inherited from group 'POI-VPLS'
> no-control-word;
> ## 'mac-statistics' was inherited from group 'POI-VPLS'
> mac-statistics;
> mesh-group 1 {
> vpls-id 424;
> neighbor 10.9.124.0;
> }
> }
> }
> ## 'vpls' was inherited from group 'POI-VPLS'
> instance-type vpls;
> interface xe-0/1/7.424;
>
> Regards,
>
> Baldur
>
> On 20.05.2020 14.25, Mark Tees wrote:
> > You need to get rid of the vlan-id off the routing-instance.
> >
> > End result I think should be similar to this:
> >
> > Logical interface ge-1/0/6.888 (Index 650) (SNMP ifIndex 830)
> > Flags: Up SNMP-Traps 0x0 VLAN-Tag [ 0x8100.888 ] In(pop) Out(push
> > 0x8100.888) Encapsulation: VLAN-VPLS
> >
> > Yours is pushing 424 on ingress. Unless, you want to be matching on
> > both tags all you need is this:
> >
> > set routing-instances VPLS instance-type vpls
> > set routing-instances VPLS interface ge-1/0/6.888
> > </snip>
> >
> > set interfaces ge-1/0/6 unit 888 encapsulation vlan-vpls
> > set interfaces ge-1/0/6 unit 888 vlan-id 888
> > set interfaces ge-1/0/6 unit 888 input-vlan-map pop
> > set interfaces ge-1/0/6 unit 888 output-vlan-map push
> >
> > You don't need to say anything about inner tags unless you are wanting
> > to do an operation on them? It sound like your remote side/ZTE does
> > the same as what I have mentioned above.
> >
> > On Wed, 20 May 2020 at 22:13, Baldur Norddahl <baldur at gigabit.dk> wrote:
> >> Hello
> >>
> >> I am trying the suggestion received so far and now have this configuration:
> >>
> >> baldur at formervangen-edge1# show interfaces xe-0/1/7
> >> flexible-vlan-tagging;
> >> native-vlan-id 424;
> >> encapsulation flexible-ethernet-services;
> >> unit 424 {
> >> encapsulation vlan-vpls;
> >> vlan-tags outer 424;
> >> input-vlan-map {
> >> push;
> >> vlan-id 424;
> >> }
> >> output-vlan-map pop;
> >> }
> >>
> >> baldur at formervangen-edge1# show routing-instances poi-formervangen |
> >> display inheritance brief
> >> protocols {
> >> vpls {
> >> ## 'ethernet-vlan' was inherited from group 'POI-VPLS'
> >> encapsulation-type ethernet-vlan;
> >> ## 'no-control-word' was inherited from group 'POI-VPLS'
> >> no-control-word;
> >> ## 'mac-statistics' was inherited from group 'POI-VPLS'
> >> mac-statistics;
> >> mesh-group 1 {
> >> vpls-id 424;
> >> neighbor 10.9.124.0;
> >> }
> >> }
> >> }
> >> ## 'vpls' was inherited from group 'POI-VPLS'
> >> instance-type vpls;
> >> ## 'inner-all' was inherited from group 'POI-VPLS'
> >> vlan-id inner-all;
> >> interface xe-0/1/7.424;
> >>
> >> baldur at formervangen-edge1# run show interfaces xe-0/1/7
> >> Physical interface: xe-0/1/7, Enabled, Physical link is Up
> >> Interface index: 176, SNMP ifIndex: 541
> >> Link-level type: Flexible-Ethernet, MTU: 1522, MRU: 1530, LAN-PHY
> >> mode, Speed: 10Gbps, BPDU Error: None, Loop Detect PDU Error: None,
> >> MAC-REWRITE Error: None, Loopback: None, Source filtering: Disabled,
> >> Flow control: Enabled, Speed Configuration: Auto
> >> Pad to minimum frame size: Disabled
> >> Device flags : Present Running
> >> Interface flags: SNMP-Traps Internal: 0x4000
> >> CoS queues : 8 supported, 8 maximum usable queues
> >> Schedulers : 0
> >> Current address: e4:5d:37:8f:dc:7a, Hardware address: e4:5d:37:8f:dc:7a
> >> Last flapped : 2020-05-20 11:14:05 CEST (02:54:05 ago)
> >> Input rate : 0 bps (0 pps)
> >> Output rate : 1384 bps (0 pps)
> >> Active alarms : None
> >> Active defects : None
> >> PCS statistics Seconds
> >> Bit errors 3
> >> Errored blocks 3
> >> Interface transmit statistics: Disabled
> >>
> >> Logical interface xe-0/1/7.424 (Index 82) (SNMP ifIndex 607)
> >> Flags: Up SNMP-Traps 0x4000 VLAN-Tag [ 0x8100.424 ] Native-vlan-id:
> >> 424 In(push .424) Out(pop) Encapsulation: VLAN-VPLS
> >> Input packets : 14
> >> Output packets: 66
> >> Protocol vpls, MTU: 1522
> >> Flags: Is-Primary
> >>
> >> Logical interface xe-0/1/7.32767 (Index 111) (SNMP ifIndex 605)
> >> Flags: Up SNMP-Traps 0x4004000 VLAN-Tag [ 0x0000.0 ] Encapsulation:
> >> ENET2
> >> Input packets : 426
> >> Output packets: 456
> >> Protocol multiservice, MTU: Unlimited
> >> Flags: None
> >>
> >>
> >>
> >> However the behaviour did not change. I am stilling receiving only
> >> single tagged frames:
> >>
> >> 12:11:09.996863 00:22:07:4d:7b:0d > ff:ff:ff:ff:ff:ff, ethertype 802.1Q
> >> (0x8100), length 346: vlan 201, p 0, ethertype IPv4, 0.0.0.0.68 >
> >> 255.255.255.255.67: BOOTP/DHCP, Request from 00:22:07:4d:7b:0d, length 300
> >>
> >> It appears the vlan map is completely ignored.
> >>
> >> Regards,
> >>
> >> Baldur
> >>
> >>
> >>
> >> _______________________________________________
> >> juniper-nsp mailing list juniper-nsp at puck.nether.net
> >> https://puck.nether.net/mailman/listinfo/juniper-nsp
> >
> >
>
--
Regards,
Mark Tees
More information about the juniper-nsp
mailing list