Provision: multi vlan tagging on interfaces

Probably one of the most frustrating “features” of provision was the fact that you could not add multiple tagged vlans at once on a port.

On the provision asic switches (5400/3500/3800/8200) with a rather current release (K15.12 or later), this major 😉 new feature has been added.

From global config, specify the interface and the tagged vlan list or range:

int 1 tagged vlan 10-20

Configuration example

Verify current vlans on the port:

edge1(config)# sh vlan port 1 detail

 Status and Counters - VLAN Information - for ports 2

 VLAN ID Name | Status Voice Jumbo Mode
 ------- -------------------- + ---------- ----- ----- --------
 1 DEFAULT_VLAN | Port-based No No Untagged

Verify the vlans you want to add exist on the switch (there is still no command to add a a global vlan range)

edge1(config)# show vlan

 Status and Counters - VLAN Information

 Maximum VLANs to support : 256
 Primary VLAN : DEFAULT_VLAN
 Management VLAN :

 VLAN ID Name | Status Voice Jumbo
 ------- -------------------------------- + ---------- ----- -----
 1 DEFAULT_VLAN | Port-based No No
 2 VLAN2 | Port-based No No
 3 VLAN3 | Port-based No No
 4 VLAN4 | Port-based No No
 5 VLAN5 | Port-based No No
 6 VLAN6 | Port-based No No
 8 VLAN8 | Port-based No No
 9 VLAN9 | Port-based No No
 10 VLAN10 | Port-based No No

Add the interface 1 tagged to a vlan range, with “-” separator for a range and “,” separator for multiple ranges:

edge1(config)# int 1 tagged vlan 2-3,5-6

Verify the updated vlan list on the port:

edge1(config)# sh vlan port 1 detail

 Status and Counters - VLAN Information - for ports 1

 VLAN ID Name | Status Voice Jumbo Mode
 ------- -------------------- + ---------- ----- ----- --------
 1 DEFAULT_VLAN | Port-based No No Untagged
 2 VLAN2 | Port-based No No Tagged
 3 VLAN3 | Port-based No No Tagged
 5 VLAN5 | Port-based No No Tagged
 6 VLAN6 | Port-based No No Tagged

You can also add vlans to existing tagged interfaces:

edge1(config)# int 1 tag vlan 8-10
edge1(config)# sh vlan port 1 detail

 Status and Counters - VLAN Information - for ports 1

 VLAN ID Name | Status Voice Jumbo Mode
 ------- -------------------- + ---------- ----- ----- --------
 1 DEFAULT_VLAN | Port-based No No Untagged
 2 VLAN2 | Port-based No No Tagged
 3 VLAN3 | Port-based No No Tagged
 5 VLAN5 | Port-based No No Tagged
 6 VLAN6 | Port-based No No Tagged
 8 VLAN8 | Port-based No No Tagged
 9 VLAN9 | Port-based No No Tagged
 10 VLAN10 | Port-based No No Tagged

And multiple interfaces can be configured at once:

edge1(config)# int 1,2,3,4 tag vlan 2-6,8-10
edge1(config)# sh vlan 10

 Status and Counters - VLAN Information - VLAN 10

 VLAN ID : 10
 Name : VLAN10
 Status : Port-based
 Voice : No
 Jumbo : No

 Port Information Mode Unknown VLAN Status
 ---------------- -------- ------------ ----------
 1 Tagged Learn Down
 2 Tagged Learn Down
 3 Tagged Learn Down
 4 Tagged Learn Down


edge1(config)#

Restrictions

Vlans must exist at global level for the command to work !

This also means that you cannot perform interface vlan tag provisioning (enable the vlan on the port even when the VLAN does not exist yet).

 

 

This entry was posted in Provision and tagged , , . Bookmark the permalink.

One Response to Provision: multi vlan tagging on interfaces

  1. Gaetan says:

    Do you have experience in vlan mapping ? I am working on comware 7, and need to map several trunked vlans on a connection between two switches. It looks like something like that on the switch where the vlan are mapped:

    vlan 2130
    name XXX

    interface Bridge-Aggregation1
    port link-type trunk
    undo port trunk permit vlan 1
    port trunk permit vlan 2130 to 2140
    vlan mapping 5 translated-vlan 2130
    vlan mapping 10 translated-vlan 2131
    vlan mapping 15 translated-vlan 2132
    vlan mapping 20 translated-vlan 2133

    Basically, I have 2 questions when it comes to the implementation:
    1. should only the translated vlan be created on the switch or also the original one ?
    2. should only the translated vlan be permitted in the trunk on the interface or also the original one ?

    If you have any hints, I’ll be glad that you share 🙂
    Thank you.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s