Support Support Downloads Knowledge Base Case Manager My Juniper Community

Knowledge Base

Search our Knowledge Base sites to find answers to your questions.

Ask All Knowledge Base Sites All Knowledge Base Sites JunosE Defect (KA)Knowledge BaseSecurity AdvisoriesTechnical BulletinsTechnotes Sign in to display secure content and recently viewed articles

[MX] VLAN pop/push operation

0

0

Article ID: KB24398 KB Last Updated: 21 Nov 2019Version: 3.0
Summary:

This article provides information about the support extended by the MX Series platform for the Pop without Push and Push without Pop of VLAN tags.

Symptoms:
  • If you pop VLAN in an interface, you must also push some VLAN and vice versa. You also must do it for the same amount of VLANs; that is it needs to be 100% symmetric.

  • There are realistic scenarios, in which you might want to pop but not push or push but not pop, or pop a different amount, than the push amount.

  • So, if the remote end is in such a device and is asymmetric, you must also be able to interoperate (maybe you cannot convince the remote end to change the configuration or the remote end has another device, which is hardware limited).
Solution:

As of Junos 11.2R1, it is not supported; it may be added in future releases as an Enhancement Request.

Possible configuration for both scenarios:

Pop without push:

VLAN 42 comes in on the trunk port (or one with vlan-bridge encap); take it off and send it out of an access port (or one with ethernet-bridge encap). Both IFL's are in the same Bridge Domain. The configuration is as follows:

[edit interfaces]
ge-0/2/5 {
    vlan-tagging;
    encapsulation flexible-ethernet-services;
    unit 0 {
        encapsulation vlan-bridge;
        vlan-id 42;
    }
}
ge-0/2/6 {
    encapsulation ethernet-bridge;
    unit 0;
}
[edit]
bridge-domains {
    vlan42 {
    vlan-id 42;
    interface ge-0/2/5.0;
    interface ge-0/2/6.0;
    }
}

Push without pop:

VLAN 42 comes in on the trunk port (or one with vlan-bridge encap); add VLAN 43 on top of it. The configuration is as follows:

[edit interfaces]
ge-0/0/0 {
    flexible-vlan-tagging;
    encapsulation flexible-ethernet-services;
    unit 0 {
        encapsulation vlan-bridge;
        vlan-id 42;
        input-vlan-map {
            push;
            vlan-id 43;
        }
    output-vlan-map pop;
    }
}
[edit]
bridge-domains {
    vlan43 {
        vlan-id 43;
        interface ge-0/0/0.0;
    }
}

You can use any 3D hardware and logical systems to test pings. For example:

MX80(logical-system A)---ge-0/0/0-ge-0/0/1---MX80(doing the BD tasks)---0/0/2-ge-0/0/3---MX80(logical-system B)

Modification History:
2019-11-21: Updated Symptoms field of article.
Comment on this article > Affected Products Browse the Knowledge Base for more articles related to these product categories. Select a category to begin.

Getting Up and Running with Junos

Getting Up and Running with Junos Security Alerts and Vulnerabilities Product Alerts and Software Release Notices Problem Report (PR) Search Tool EOL Notices and Bulletins JTAC User Guide Customer Care User Guide Pathfinder SRX High Availability Configurator SRX VPN Configurator Training Courses and Videos End User Licence Agreement Global Search