Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Navigation
Guide That Contains This Content
[+] Expand All
[-] Collapse All
     

    Related Documentation

     

    Configuring VLAN Translation with a VLAN ID List

    In many cases, the VLAN identifiers on the frames of an interface’s packets are not correct. VLAN translation, or VLAN rewrite, allows you to configure bidirectional VLAN identifier translation with a list on frames arriving on and leaving from a logical interface. This lets you use unique VLAN identifiers internally and maintain legacy VLAN identifiers on logical interfaces.

    To perform VLAN translation on the packets on a trunk interface, insert the vlan-rewrite statement at the [edit interfaces interface-name unit unit-number] hierarchy level. You must also include the interface-mode trunk statement within the [edit interfaces interface-name unit unit-number family ethernet-switching] hierarchy because VLAN translation is only supported on trunk interfaces. The reverse translation takes place on traffic exiting the interface. In other words, if VLAN 200 is translated to 500 on traffic entering the interface, VLAN 500 is translated to VLAN 200 on traffic leaving the interface.

    The following example translates incoming trunk packets from VLAN identifier 200 to 500 and 201 to 501 (other valid VLAN identifiers are not affected):

    [edit interfaces ge-1/0/1]
    unit 0 {... # Other logical interface statementsfamily ethernet-switching {interface-mode trunk # Translation is only for trunksinner-vlan-id-list [ 100 500–600 ];vlan-rewrite {translate 200 500;translate 201 501;}... # Other ethernet-switching statements}}

    Note: This example also translates frame VLANs from 500 to 200 and 501 to 201 on egress.

     

    Related Documentation

     

    Published: 2013-04-03