Contents

Configuring VLAN mapping· 1

About VLAN mapping· 1

VLAN mapping types· 1

VLAN mapping application scenarios· 1

VLAN mapping implementations· 3

Restrictions and guidelines: VLAN mapping configuration· 4

VLAN mapping tasks at a glance· 5

Prerequisites· 5

Configuring one-to-one VLAN mapping· 5

Configuring one-to-two VLAN mapping· 6

Display and maintenance commands for VLAN mapping· 6

VLAN mapping configuration examples· 7

Example: Configuring one-to-one VLAN mapping· 7

Example: Configuring one-to-two VLAN mapping· 9

 

Configuring VLAN mapping

About VLAN mapping

VLAN mapping re-marks VLAN traffic with new VLAN IDs.

VLAN mapping types

H3C provides the following types of VLAN mapping:

·     One-to-one VLAN mapping—Replaces one VLAN tag with another.

·     One-to-two VLAN mapping—Tags single-tagged packets with an outer VLAN tag.

VLAN mapping application scenarios

One-to-one VLAN mapping

One-to-one VLAN mapping are typically used by a community for broadband Internet access, as shown in Figure 1.

Figure 1 Application scenario of one-to-one VLAN mapping

‌

As shown in Figure 1, the network is implemented as follows:

·     Each home gateway uses different VLANs to transmit the PC, VoD, and VoIP services.

·     To further subclassify each type of traffic by customer, configure one-to-one VLAN mapping on the wiring-closet switches. This feature assigns a separate VLAN to each type of traffic from each customer. The required total number of VLANs in the network can be very large.

One-to-two VLAN mapping

As shown in Figure 2, one-to-two VLAN mapping is used to transmit different types of CVLAN packets with different SVLAN tags over the service provider network.

Figure 2 Application scenario of one-to-two VLAN mapping

 

As shown in Figure 2, users of Site 1 and Site 2 are in VLAN 10 and VLAN 20. The service provider assigns VLAN 100 and VLAN 200 to the customer network. When packets from Site 1 arrive at PE 1, PE 1 adds an SVLAN tag to the packets based on the packet type.

One-to-two VLAN mapping enables the customer to plan CVLANs without conflicting with SVLANs. The service provider can distinguish traffic of the customer network with different SVLANs, and apply transmission policies to the customer traffic.

VLAN mapping implementations

Figure 3 shows a simplified network that illustrates basic VLAN mapping terms.

Basic VLAN mapping terms include the following:

·     Uplink traffic—Traffic transmitted from the customer network to the service provider network.

·     Downlink traffic—Traffic transmitted from the service provider network to the customer network.

·     Network-side port—A port connected to or closer to the service provider network.

·     Customer-side port—A port connected to or closer to the customer network.

Figure 3 Basic VLAN mapping terms

‌

One-to-one VLAN mapping

As shown in Figure 4, one-to-one VLAN mapping is implemented on the customer-side port and replaces VLAN tags as follows:

·     Replaces the CVLAN with the SVLAN for the uplink traffic.

·     Replaces the SVLAN with the CVLAN for the downlink traffic.

Figure 4 One-to-one VLAN mapping implementation

‌

One-to-two VLAN mapping

As shown in Figure 5, one-to-two VLAN mapping is implemented on the customer-side port to add the SVLAN tag for the uplink traffic.

For the downlink traffic to be correctly sent to the customer network, make sure the SVLAN tag is removed on the customer-side port before transmission. Use one of the following methods to remove the SVLAN tag from the downlink traffic:

·     Configure the customer-side port as a hybrid port and assign the port to the SVLAN as an untagged member.

·     Configure the customer-side port as a trunk port and set the port PVID to the SVLAN.

Figure 5 One-to-two VLAN mapping implementation

‌

Restrictions and guidelines: VLAN mapping configuration

To add VLAN tags to packets, you can configure both VLAN mapping and QinQ. VLAN mapping takes effect if a configuration conflict occurs. For more information about QinQ, see "Configuring QinQ."

To add or replace VLAN tags for packets, you can configure both VLAN mapping and a QoS policy. VLAN mapping takes effect if a configuration conflict occurs. For information about QoS policies, see ACL and QoS Configuration Guide.

VLAN mapping tasks at a glance

Use the appropriate VLAN mapping methods for the devices in the network.

To configure VLAN mapping, perform the following tasks:

·     Configuring one-to-one VLAN mapping

Configure one-to-one VLAN mapping on the wiring-closet switch, as shown in Figure 1.

·     Configuring one-to-two VLAN mapping

Configure one-to-two VLAN mapping on PE 1 and PE 4, as shown in Figure 2, through which traffic from customer networks enters the service provider networks.

Prerequisites

Before you configure VLAN mapping, create original and translated VLANs.

Configuring one-to-one VLAN mapping

About one-to-one VLAN mapping

Configure one-to-one VLAN mapping on the customer-side ports of wiring-closet switches (see Figure 1) to isolate traffic of the same service type from different homes.

Procedure

1.     Enter system view.

system-view

2.     Enter interface view.

¡     Enter Layer 2 Ethernet interface view.

interface interface-type interface-number

¡     Enter Layer 2 aggregate interface view.

interface bridge-aggregation interface-number

3.     Set the link type of the port.

port link-type { hybrid | trunk }

By default, the link type of a port is access.

4.     Assign the port to the original VLAN and the translated VLAN.

¡     Assign the trunk port to the original VLAN and the translated VLAN.

port trunk permit vlan vlan-id-list

By default, a trunk port is assigned to VLAN 1.

¡     Assign the hybrid port to the original VLAN and the translated VLAN as a tagged member.

port hybrid vlan vlan-id-list tagged

By default, a hybrid port is an untagged member of the VLAN to which the port belongs when its link type is access.

5.     Configure a one-to-one VLAN mapping.

vlan mapping vlan-id translated-vlan vlan-id

By default, no VLAN mapping is configured on an interface.

Configuring one-to-two VLAN mapping

About one-to-two VLAN mapping

Configure one-to-two VLAN mapping on the customer-side ports of edge devices from which customer traffic enters SP networks, for example, on PEs 1 and 4 in Figure 2. One-to-two VLAN mapping enables the edge devices to add an SVLAN tag to each incoming packet.

Restrictions and guidelines

Only one SVLAN tag can be added to packets from the same CVLAN. To add different SVLAN tags to different CVLAN packets on a port, set the port link type to hybrid and configure multiple one-to-two VLAN mappings.

The MTU of an interface is 1500 bytes by default. After a VLAN tag is added to a packet, the packet length is added by 4 bytes. As a best practice, set the MTU to a minimum of 1504 bytes for ports on the forwarding path of the packet in the service provider network.

Procedure

1.     Enter system view.

system-view

2.     Enter interface view.

¡     Enter Layer 2 Ethernet interface view.

interface interface-type interface-number

¡     Enter Layer 2 aggregate interface view.

interface bridge-aggregation interface-number

3.     Set the link type of the port.

port link-type { hybrid | trunk }

By default, the link type of a port is access.

4.     Configure the port to allow packets from the SVLAN to pass through untagged.

¡     Configure the SVLAN as the PVID of the trunk port and assign the trunk port to the SVLAN.

port trunk pvid vlan vlan-id

port trunk permit vlan { vlan-id-list | all }

¡     Assign the hybrid port to the SVLAN as an untagged member.

port hybrid vlan vlan-id-list untagged

5.     Configure a one-to-two VLAN mapping.

vlan mapping nest { range vlan-range-list | single vlan-id-list } nested-vlan vlan-id

By default, no VLAN mapping is configured on an interface.

Display and maintenance commands for VLAN mapping

Execute display commands in any view.

 

Task	Command
Display VLAN mapping information.	display vlan mapping [ interface interface-type interface-number ]

‌

VLAN mapping configuration examples

Example: Configuring one-to-one VLAN mapping

Network configuration

As shown in Figure 6:

·     Each household subscribes to PC, VoD, and VoIP services.

·     On the home gateways, VLANs 1, 2, and 3 are assigned to PC, VoD, and VoIP traffic, respectively.

To isolate traffic of the same service type from different households, configure one-to-one VLAN mappings on the wiring-closet switches. This feature assigns one VLAN to each type of traffic from each household.

Figure 6 Network diagram

 

‌

Procedure

1.     Configure Switch A:

# Create the original VLANs.

<SwitchA> system-view

[SwitchA] vlan 2 to 3

# Create the translated VLANs.

[SwitchA] vlan 101 to 102

[SwitchA] vlan 201 to 202

[SwitchA] vlan 301 to 302

# Configure customer-side port GigabitEthernet 1/0/1 as a trunk port.

<SwitchA> system-view

[SwitchA] interface gigabitethernet 1/0/1

[SwitchA-GigabitEthernet1/0/1] port link-type trunk

# Assign GigabitEthernet 1/0/1 to all original VLANs and translated VLANs.

[SwitchA-GigabitEthernet1/0/1] port trunk permit vlan 1 2 3 101 201 301

# Configure one-to-one VLAN mappings on GigabitEthernet 1/0/1 to map VLANs 1, 2, and 3 to VLANs 101, 201, and 301, respectively.

[SwitchA-GigabitEthernet1/0/1] vlan mapping 1 translated-vlan 101

[SwitchA-GigabitEthernet1/0/1] vlan mapping 2 translated-vlan 201

[SwitchA-GigabitEthernet1/0/1] vlan mapping 3 translated-vlan 301

[SwitchA-GigabitEthernet1/0/1] quit

# Configure customer-side port GigabitEthernet 1/0/2 as a trunk port.

[SwitchA] interface gigabitethernet 1/0/2

[SwitchA-GigabitEthernet1/0/2] port link-type trunk

# Assign GigabitEthernet 1/0/2 to all original VLANs and translated VLANs.

[SwitchA-GigabitEthernet1/0/2] port trunk permit vlan 1 2 3 102 202 302

# Configure one-to-one VLAN mappings on GigabitEthernet 1/0/2 to map VLANs 1, 2, and 3 to VLANs 102, 202, and 302, respectively.

[SwitchA-GigabitEthernet1/0/2] vlan mapping 1 translated-vlan 102

[SwitchA-GigabitEthernet1/0/2] vlan mapping 2 translated-vlan 202

[SwitchA-GigabitEthernet1/0/2] vlan mapping 3 translated-vlan 302

[SwitchA-GigabitEthernet1/0/2] quit

# Configure the network-side port (GigabitEthernet 1/0/3) as a trunk port.

[SwitchA] interface gigabitethernet 1/0/3

[SwitchA-GigabitEthernet1/0/3] port link-type trunk

# Assign GigabitEthernet 1/0/3 to the translated VLANs.

[SwitchA-GigabitEthernet1/0/3] port trunk permit vlan 101 201 301 102 202 302

[SwitchA-GigabitEthernet1/0/3] quit

2.     Configure Switch B in the same way Switch A is configured. (Details not shown.)

Verifying the configuration

# Verify VLAN mapping information on the wiring-closet switches, for example, Switch A.

[SwitchA] display vlan mapping

Interface GigabitEthernet1/0/1:

  Outer VLAN    Inner VLAN    Translated Outer VLAN    Translated Inner VLAN

  1             N/A           101                      N/A

  2             N/A           201                      N/A

  3             N/A           301                      N/A

Interface GigabitEthernet1/0/2:

  Outer VLAN    Inner VLAN    Translated Outer VLAN    Translated Inner VLAN

  1             N/A           102                      N/A

  2             N/A           202                      N/A

  3             N/A           302                      N/A

Example: Configuring one-to-two VLAN mapping

Network configuration

As shown in Figure 7, Site 1 and Site 2 of a company use VLAN 10 and VLAN 20 to transmit VoIP and PC traffic, respectively. The service provider assigns VLAN 100 and VLAN 200 to the customer network.

Configure one-to-two VLAN mappings to enable the service provider network to transmit VoIP and PC traffic with SVLAN 100 and SVLAN 200, respectively.

Figure 7 Network diagram

 

Procedure

1.     Configure PE 1:

# Create VLANs 10, 20, 100, and 200.

<PE1> system-view

[PE1] vlan 10

[PE1-vlan10] quit

[PE1] vlan 20

[PE1-vlan20] quit

[PE1] vlan 100

[PE1-vlan100] quit

[PE1] vlan 200

[PE1-vlan200] quit

# Configure a one-to-two VLAN mapping on the customer-side port (GigabitEthernet 1/0/1) to add SVLAN tag 100 to packets from CVLAN 10.

[PE1] interface gigabitethernet 1/0/1

[PE1-GigabitEthernet1/0/1] vlan mapping nest single 10 nested-vlan 100

# Configure a one-to-two VLAN mapping on GigabitEthernet 1/0/1 to add SVLAN tag 200 to packets from CVLAN 20.

[PE1-GigabitEthernet1/0/1] vlan mapping nest single 20 nested-vlan 200

# Configure GigabitEthernet 1/0/1 as a hybrid port.

[PE1-GigabitEthernet1/0/1] port link-type hybrid

# Assign GigabitEthernet 1/0/1 to VLANs 100 and 200 as an untagged member.

[PE1-GigabitEthernet1/0/1] port hybrid vlan 100 200 untagged

[PE1-GigabitEthernet1/0/1] quit

# Configure the network-side port (GigabitEthernet 1/0/2) as a trunk port, and assign the port to VLANs 100 and 200.

[PE1] interface gigabitethernet 1/0/2

[PE1-GigabitEthernet1/0/2] port link-type trunk

[PE1-GigabitEthernet1/0/2] port trunk permit vlan 100 200

[PE1-GigabitEthernet1/0/2] quit

2.     Configure PE 2 in the same way PE 1 is configured. (Details not shown.)

Verifying the configuration

# Verify VLAN mapping information on PE 1.

[PE1] display vlan mapping

Interface GigabitEthernet1/0/1:

  Outer VLAN    Inner VLAN    Translated Outer VLAN    Translated Inner VLAN

  10             N/A           100                      10

  20             N/A           200                      20

# Verify VLAN mapping information on PE 2.

[PE2] display vlan mapping

Interface GigabitEthernet1/0/2:

  Outer VLAN    Inner VLAN    Translated Outer VLAN    Translated Inner VLAN

  10             N/A           100                      10

  20             N/A           200                      20