Routing

Hello!

Please help me to configure passing native VLAN #1 traffic throuth VPLS. My scheme CE1--PE1--PE2--CE2.

CE1 and CE2 send unntaged traffic in VLAN 1 and tagged in vlan 99. In Vlan 99 everything is working.

My config from CE1 (CE2 is the same):

# show interfaces ge-1/2/1
flexible-vlan-tagging;
native-vlan-id 1;
encapsulation flexible-ethernet-services;

interfaces {

 ge-1/2/1 {
        unit 20 {
            encapsulation vlan-vpls;
            vlan-id 1;
            family vpls;
        }
        unit 99 {
            encapsulation vlan-vpls;
            vlan-id 99;
            family vpls;
        }

routing-instances {
    VPLS {
        instance-type vpls;
        vlan-id all;
        interface ge-1/2/1.20;
        interface ge-1/2/1.99;
        route-distinguisher 7.7.7.7:150;
        vrf-target target:65000:150;
        protocols {
            vpls {
                no-tunnel-services;
                site CE1 {
                    site-identifier 1;
                }
                      }
        }
    }

I'd tried to configure VLAN rewrite rule on the interface like this:

interfaces {
        unit 20 {

    vlan-tags outer 1 inner 2;
            native-inner-vlan-id 2;

}

Native traffic puted to VLAN2 in VPLS, but i couldn't ping CE2.

Please help me with correct configuration.

Thank you!

Hello,

http://www.juniper.net/techpubs/en_US/junos/topics/example/layer-2-vlans-multiple-for-one-vpls-instance-example-mx-solutions.html

You cannot use the native vlan- id statement when the vlan-id all statement is included in the configuration.

Please use the following VPLS instance configuration:

routing-instances {
    VPLS {
        instance-type vpls;
        vlan-id 99;

 This way, the untagged frames coming from ge-1/2/1.20 will get vlan-tag 99 pushed before being forwarded to MPLS core, and packets coming from MPLS core and destined for ge-1/2/1.20 will get vlan-tag 99 removed. This is called "VLAN tag normalization".

HTH

Thanks
Alex

Thank you for reply!

Is VLAN tag normalization working for dot1q frames? If i configure another IFL with vlan-id 100 vlan normalization will it rewrite vlan to 99? 

Am i think rigth that i should create another VPLS instance for property configuration? One instance would be for vlan normalization for native vlan, another- without normalization for my dot1q VLANs?

Hello,

---

akvasov@nvg.ru wrote:

Thank you for reply!

Is VLAN tag normalization working for dot1q frames?

---

VPLS VLAN normalization works for both 802.1Q tagged and untagged frames.

---

akvasov@nvg.ru wrote:

 

if i configure another IFL with vlan-id 100 vlan normalization will it rewrite vlan to 99? 

 

---

Yes it will.

---

akvasov@nvg.ru wrote:

Am i think rigth that i should create another VPLS instance for property configuration?

---

If You don't want Your ge-1/2/1.20 talking to ge-1/2/1.99 and also CE2' interface with vlan-id 99, then yes. Separate VPLS instance will create a second "data plane" for untagged frames only.

---

akvasov@nvg.ru wrote:

One instance would be for vlan normalization for native vlan, another- without normalization for my dot1q VLANs?

---

You can do it that way but it will prevent ge-1/2/1.20 talking to ge-1/2/1.99 and CE2' interface wil vlan-id 99.

This may be good or bad, depending on Your circumstances and client' requirements.

HTH

Thanks
Alex