- Table of Contents
-
- 03-Layer 2—LAN Switching Configuration Guide
- 00-Preface
- 01-Ethernet interface configuration
- 02-Loopback, null, and inloopback interface configuration
- 03-Bulk interface configuration
- 04-MAC address table configuration
- 05-Ethernet link aggregation configuration
- 06-Port isolation configuration
- 07-Spanning tree configuration
- 08-Loop detection configuration
- 09-VLAN configuration
- 10-MVRP configuration
- 11-QinQ configuration
- 12-VLAN mapping configuration
- 13-PBB configuration
- 14-LLDP configuration
- 15-L2PT configuration
- 16-Service loopback group configuration
- 17-Cut-through forwarding configuration
- 18-DRNI configuration
- Related Documents
-
Title | Size | Download |
---|---|---|
13-PBB configuration | 170.92 KB |
Configuration restrictions and guidelines
Configuring a B-VLAN for a PBB VSI
Configuring the data encapsulation type
Displaying and maintaining PBB
Failed to transmit customer frames to peer
Configuring PBB
Overview
PBB has the following advantages over QinQ:
· Reduces the MAC address table size. In a PBB-enabled service provider network, only the edge devices maintain entries for customer MAC addresses. In a QinQ-enabled service provider network, all devices must maintain entries for customer MAC addresses.
· Supports more than 16 million service instances. QinQ supports only a maximum of 4094 outer VLANs (service instances).
For more information about QinQ, see "Configuring QinQ."
PBB network model
As shown in Figure 1, the PBB network includes backbone edge bridges and backbone core bridges.
Backbone edge bridges connect customer sites or provider bridge networks to the PBB network. They encapsulate the customer MAC in the service provider MAC. Backbone core bridges forward traffic based on the service provider MAC.
Terminology
PBBN
A network using PBB is a provider backbone bridge network (PBBN). A PBBN is a Layer 2 switching network where Layer 2 connections are established between different nodes.
PBN
A provider bridge network (PBN) connects a PBBN to a customer network. A customer network can connect to a PBBN directly or through a PBN.
BEB
A backbone edge bridge (BEB) is an edge device in a PBBN. A BEB encapsulates frames from a customer network by using PBB. It decapsulates PBB frames from a PBBN and forwards them to a customer network. The BEB learns customer MAC addresses.
BCB
A backbone core bridge (BCB) is a core device in a PBBN. It forwards a PBB frame according to its B-MAC and B-VLAN. A BCB only forwards frames and learns MAC addresses within the PBBN. It does not learn a large number of customer MAC addresses. This reduces network deployment costs, and the PBBN is more expandable.
CE
Customer edges (CEs) are edge devices that connect customer sites or PBNs to the BEBs of the PBBN.
B-MAC and B-VLAN
A backbone MAC address (B-MAC) is a MAC address associated with a PBB bridge. A backbone VLAN (B-VLAN) is a VLAN assigned by the service provider for transmitting customer traffic on the PBBN.
For customer frames to be transmitted across a PBBN, the ingress BEB encapsulates them in MAC-in-MAC format. In the outer frame header, the source MAC address is a B-MAC of the ingress BEB, and the destination MAC is a B-MAC of the egress BEB. All devices in the PBBN forward the PBB frames based on the destination B-MAC and B-VLAN.
Uplink port and downlink port
A port that connects a BEB to a PBBN is an uplink port, and a port that connects a BEB to a customer network is a downlink port. After frames from the customer network are encapsulated in PBB frames, they are forwarded out of the corresponding uplink ports on the BEB. After PBB frames from the PBBN are decapsulated, they are forwarded out of the corresponding downlink ports on the BEB according to the customer MAC addresses.
PBB VSI and I-SID
AC
An attachment circuit (AC) is a physical or virtual link that connects a CE to a BEB.
PBB frame format
Figure 2 shows the format of a PBB frame.
Table 1 describes key fields in the frame.
Table 1 PBB frame fields
Field |
Full name |
Description |
B-DA |
Backbone destination MAC address |
Destination B-MAC, outer destination MAC address in a PBB frame. It is the MAC address of the BEB at the destination end of the PBBN tunnel. The combination of B-DA and B-SA is B-MAC. |
B-SA |
Backbone source MAC address |
Source B-MAC, outer source MAC address in a PBB frame. It is the MAC address of the BEB at the source end of the PBBN tunnel. The combination of B-DA and B-SA is B-MAC. |
B-Tag |
Backbone VLAN tag |
B-VLAN tag, outer VLAN tag in a PBB frame. It indicates the VLAN information and priority information of the frame within the PBBN. The TPID in a B-Tag is 0x8100. |
I-Tag |
Backbone service instance tag |
Service identifier of a PBB frame. The I-Tag contains the following fields: · TPID—The TPID in an I-Tag is 0x88E7. · I-PCP—Backbone service instance priority code point. · I-DEI—Backbone service instance drop eligibility indicator. · I-SID—Backbone service instance identifier. · C-DA—Destination MAC address of the customer frame. · C-SA—Source MAC address of the customer frame. |
S-Tag |
Service provider VLAN tag |
Outer VLAN tag of the frame in the PBN, which indicates the VLAN and priority information of the frame within the PBN. |
C-Tag |
Customer VLAN tag |
Inner VLAN tag of the frame in the PBN, which indicates the VLAN and priority information of the frame within the customer network. |
For more information about TPID, see "Configuring VLANs."
PBB frame forwarding
On a PBBN, the BEBs encapsulate customer traffic in PBB, and learn their C-MAC reachability information in the data plane. To forward traffic across the PBBN, the BEBs learn unicast forwarding entries for reaching each other. Each entry contains a B-MAC address, B-VLAN, I-SID, and outgoing interface.
The following describes how a unicast forwarding entry is created:
1. When BEB 1 receives a frame with an unknown destination C-MAC (for example, MAC A) from the customer network, BEB 1 performs the following operations:
a. Assign the frame to a PBB VSI based on the configured match criteria.
b. Encapsulates the frame in MAC-in-MAC format. The source B-MAC is the MAC address of BEB 1. The destination B-MAC is the multicast B-MAC configured for the matching PBB VSI.
c. Multicasts the PBB frame out of the VSI's all uplink ports.
2. When BEB 2 receives the PBB frame, it performs the following operations:
a. Creates a unicast forwarding entry for MAC A. In the entry, the destination B-MAC is the B-MAC of BEB 1, the outgoing interface is the interface on which the frame was received.
b. Removes the PBB encapsulation, and then forwards the frame to the customer network.
Figure 3 shows how the PBBN forwards a frame between BEBs if a unicast forwarding entry exists for the frame:
1. BEB 1 encapsulates a customer frame with the matching source and destination B-MACs, B-VLAN, and I-SID. Then it forwards the frame to the BCB through its uplink port.
2. BCB forwards the PBB frame from BEB 1 to BEB 2 according to the frame's destination B-MAC and B-VLAN.
3. BEB 2 removes the PBB encapsulation, and then forwards the original Ethernet frame out of the downlink port to the customer network.
Protocols and standards
IEEE 802.1ah, Virtual Bridged Local Area Networks Amendment 7: Provider Backbone Bridges
Configuration restrictions and guidelines
When you configure PBB, follow these restrictions and guidelines:
· You need to configure PBB only on BEBs.
· On BCBs, you must create VLANs that are the same as the B-VLANs used on the BEBs.
PBB configuration task list
Tasks at a glance |
(Required.) Enabling L2VPN |
(Required.) Creating a PBB VSI |
(Required.) Configuring a B-VLAN for a PBB VSI |
(Required.) Configuring an uplink port |
(Required.) Configuring a downlink port |
(Optional.) Configuring the data encapsulation type |
Enabling L2VPN
Step |
Command |
Remarks |
1. Enter system view. |
system-view |
N/A |
2. Enable L2VPN. |
l2vpn enable |
By default, L2VPN is disabled. |
Creating a PBB VSI
When you create a PBB VSI, follow these guidelines:
· You can configure one PBB I-SID and one SPB I-SID for a VSI, but the two I-SIDs must be different. For more information about SPB, see SPB Configuration Guide.
· You must assign a unique I-SID to each PBB VSI.
· The name of a PBB VSI can be different on different PBB nodes, but its I-SID must be the same across the PBBN.
To create a PBB VSI:
Step |
Command |
Remarks |
1. Enter system view. |
system-view |
N/A |
2. Create a VSI and enter VSI view. |
vsi vsi-name |
By default, no VSIs exist. |
3. Configure the VSI as a PBB VSI, specify a PBB I-SID for the PBB VSI, and enter PBB VSI view. |
pbb i-sid i-sid |
By default, no PBB VSIs exist. |
Configuring a B-VLAN for a PBB VSI
You can assign only one B-VLAN to a PBB VSI, but different PBB VSIs can use the same B-VLAN.
For a PBB VSI, you must specify the same I-SID and B-VLAN across all BEBs.
To configure a B-VLAN for a PBB VSI:
Step |
Command |
Remarks |
1. Enter system view. |
system-view |
N/A |
2. Enter VSI view. |
vsi vsi-name |
N/A |
3. Configure the VSI as a PBB VSI, specify a PBB I-SID for the PBB VSI, and enter PBB VSI view. |
pbb i-sid i-sid |
N/A |
4. Specify a B-VLAN for the PBB VSI. |
bvlan vlan-id |
By default, no B-VLAN is specified for a PBB VSI. |
Configuring an uplink port
On the BEB, you must specify uplink ports for a PBB VSI to forward frames from the customer network to the service provider network.
You can specify multiple uplink ports for one PBB VSI. The device automatically selects uplink ports for packets. The uplink ports cannot be member ports in a link aggregation group.
For the uplink port configuration to take effect, perform the following tasks before uplink port assignment:
· Assign a B-VLAN to the PBB VSI.
· Verify that the port is in up state and is not a link aggregation group member.
· Assign the port to the B-VLAN.
To configure an uplink port:
Step |
Command |
Remarks |
1. Enter system view. |
system-view |
N/A |
2. Enter Layer 2 Ethernet interface view or Layer 2 aggregate interface view. |
interface interface-type interface-number |
N/A |
3. Specify the port as the uplink port for the specified or all PBB VSIs. |
pbb uplink { all | vsi vsi-name-list } |
By default, a port is not configured as the uplink port of any PBB VSI. |
Configuring a downlink port
You can specify one or multiple downlink ports for a PBB VSI.
Do not assign a downlink port to a B-VLAN.
To configure a downlink port:
Step |
Command |
Remarks |
1. Enter system view. |
system-view |
N/A |
2. Enter Layer 2 Ethernet interface view or Layer 2 aggregate interface view. |
interface interface-type interface-number |
N/A |
3. Create an Ethernet service instance and enter Ethernet service instance view. |
service-instance instance-id |
By default, no Ethernet service instances exist. |
4. Configure a match criterion. |
· encapsulation s-vid vlan-id [ c-vid { vlan-id-list | all } | only-tagged ] · encapsulation s-vid vlan-id-list [ c-vid vlan-id-list ] · encapsulation { default | tagged | untagged } |
By default, no match criterion is configured. |
5. Map the Ethernet service instance to a PBB VSI. |
xconnect vsi vsi-name [ access-mode { ethernet | vlan } ] |
By default, an Ethernet service instance is not mapped to any PBB VSI. |
For more information about the service-instance, encapsulation, and xconnect vsi commands, see MPLS Command Reference.
Configuring the data encapsulation type
A PBB VSI supports Ethernet and VLAN data encapsulation types.
Data encapsulation type decides how the BEB handles the P-tag on a PBB VSI, as shown in Table 2. P-tags are unique VLAN tags that the service provider assigns to users for differentiation.
Traffic direction |
Ethernet encapsulation |
VLAN encapsulation |
CE to PBBN |
The traffic must not contain a P-tag. · VLAN access mode—The BEB removes the P-tag before it encapsulates the traffic in PBB. · Ethernet access mode—The BEB directly encapsulates the traffic in PBB. The VLAN tag in the received traffic is considered a U-tag. |
The traffic must contain a P-tag. · VLAN access mode—The BEB retains the P-tag or changes the P-tag to the value assigned by the peer BEB. · Ethernet access mode—The BEB adds the P-tag assigned by the peer BEB. The original VLAN tag in the received traffic is considered a U-tag. The P-tag assigned by the peer BEB might be a null tag (tag 0). |
PBBN to CE |
· VLAN access mode—The BEB adds a P-tag before it forwards the traffic. · Ethernet access mode—The BEB forwards the traffic without adding a P-tag. The BEB cannot modify or remove any tags already in the traffic from PBBN to CE. |
· VLAN access mode—The BEB forwards the traffic with the P-tag modified or intact. · Ethernet access mode—The BEB removes the P-tag before it forwards the traffic. |
|
NOTE: To configure the access mode, use the xconnect vsi command (see MPLS Command Reference). |
To configure the data encapsulation type for a PBB VSI:
Step |
Command |
Remarks |
1. Enter system view. |
system-view |
N/A |
2. Enter VSI view. |
vsi vsi-name |
N/A |
3. Enter PBB VSI view. |
pbb i-sid i-sid |
N/A |
4. Specify an encapsulation type for the PBB VSI. |
encapsulation { ethernet | vlan } |
By default, VLAN encapsulation applies. |
Displaying and maintaining PBB
Execute display commands in any view and reset commands in user view.
Task |
Command |
Display PBB VSI connections. |
display pbb connection |
Display MAC-in-MAC connections. |
display l2vpn minm connection [ vsi vsi-name ] |
Display MAC-in-MAC forwarding entries. |
display l2vpn minm forwarding [ vsi vsi-name ] [ slot slot-number ] |
Display VSI information. |
display l2vpn vsi [ name vsi-name ] [ verbose ] |
Clear PBB VSI connections. |
reset pbb connection [ bvlan vlan-id | interface interface-type interface-number ] * |
PBB configuration example
Network requirements
As shown in Figure 4, configure PBB to provide connectivity between network A and network B of a customer.
Configuration procedure
1. Configure BEB 1:
# Create VLAN 20.
<BEB1> system-view
[BEB1] vlan 20
[BEB1-vlan20] quit
# Enable L2VPN.
[BEB1] l2vpn enable
# Create a VSI of the PBB type.
[BEB1] vsi aaa
# Specify the I-SID as 1.
[BEB1-vsi-aaa] pbb i-sid 1
# Specify B-VLAN 20 for the PBB VSI.
[BEB1-vsi-aaa-1] bvlan 20
[BEB1-vsi-aaa-1] quit
[BEB1-vsi-aaa] quit
# Configure Ten-GigabitEthernet 1/0/1 as a trunk port, assign it to VLAN 20, and configure it as an uplink port of the PBB VSI.
[BEB1] interface ten-gigabitethernet 1/0/1
[BEB1-Ten-GigabitEthernet1/0/1] port link-type trunk
[BEB1-Ten-GigabitEthernet1/0/1] port trunk permit vlan 20
[BEB1-Ten-GigabitEthernet1/0/1] pbb uplink vsi aaa
[BEB1-Ten-GigabitEthernet1/0/1] quit
# Create Ethernet service instance 1 on Ten-GigabitEthernet 1/0/2.
[BEB1] interface ten-gigabitethernet 1/0/2
[BEB1-Ten-GigabitEthernet1/0/2] service-instance 1
# Configure the Ethernet service instance to match all 802.1Q tagged frames. Map the service instance to the PBB VSI, and set the access mode to Ethernet.
[BEB1-Ten-GigabitEthernet1/0/2-srv1] encapsulation tagged
[BEB1-Ten-GigabitEthernet1/0/2-srv1] xconnect vsi aaa access-mode ethernet
[BEB1-Ten-GigabitEthernet1/0/2-srv1] quit
[BEB1-Ten-GigabitEthernet1/0/2] quit
# Configure Ethernet encapsulation for the PBB VSI.
[BEB1] vsi aaa
[BEB1-vsi-aaa] pbb i-sid 1
[BEB1-vsi-aaa-1] encapsulation ethernet
[BEB1-vsi-aaa-1] quit
2. Configure BEB 2 in the same way BEB 1 is configured. (Details not shown.)
Verifying the configuration
# Display PBB VSI connections on BEB 1.
[BEB1] display pbb connection
BMAC BVLAN Port Type Aging
011e-8300-0001 20 XGE1/0/1 MC N
000f-e200-0001 20 XGE1/0/1 UC Y
# Verify that Device A and Device B can ping each other. (Details not shown.)
Troubleshooting PBB
Failed to transmit customer frames to peer
Symptom
Customer frames cannot be transmitted to the peer network by using PBB.
Solution
To resolve the problem:
1. Use the display l2vpn vsi verbose command to display the PBB configuration of the VSI.
¡ If the VSI is not configured as a PBB VSI, configure the VSI as a PBB VSI.
¡ If the VSI is down, use the undo shutdown command to bring the VSI up.
2. Use the display l2vpn vsi verbose command to verify that the VSI's PBB settings are consistent across BEBs, especially the I-SID and B-VLAN settings.
3. Use the display vlan all command to verify that the following settings are configured on all BCBs:
¡ The B-VLAN is created on each BCB.
¡ All ports on the path between the BEBs are assigned to the B-VLAN.
4. If the problem persists, contact H3C Support.