[j-nsp] Double-tagging on EX

Chris Kawchuk juniperdude at gmail.com
Wed Feb 22 17:01:57 EST 2012


Dang.

No dice on the native-vlan-id option. Makes sense, as an "access port" (even though it's for a QinQ access port) isn't expecting tagged vs untagged(native) - It just grabs everything (tags or not)

configgy:

ge-0/0/11 {
    description "TEST Input of QinQ Tagging using native-vlan-id to somehow double-tag an incoming untagged packet as S:4000 C:100";
    mtu 9192;
    unit 0 {
        family ethernet-switching {
            port-mode access;
            vlan {
                members 4000;
            }
            native-vlan-id 100;
        }
    }
}
ge-0/0/12 {
    description "TEST - DoubleTagged output of QinQ test for V4000/V100";
    mtu 9192;
    unit 0 {
        family ethernet-switching {
            port-mode trunk;
            vlan {
                members 4000;
            }
        }
    }
}

vlans {
    V100 {
        vlan-id 100;
    }
    V4000 {
        vlan-id 4000;
        dot1q-tunneling;
    }
}

me at ex4200#commit check
[edit interfaces ge-0/0/11 unit 0 family]
  'ethernet-switching'
    Access interface ge-0/0/11.0 cannot have native-vlan-id
error: configuration check-out failed

show version 
fpc0:
--------------------------------------------------------------------------
Model: ex4200-24t
JUNOS Base OS Software Suite [10.4R8.5]








More information about the juniper-nsp mailing list