HP 5920 User manual

HP 5920 & 5900 Switch Series
SPB
Configuration Guide
Part number: 5998-4678a
Software version: Release 23xx
Document version: 6W101-20150320

Legal and notice information
© Copyright 2015 Hewlett-Packard Development Company, L.P.
No part of this documentation may be reproduced or transmitted in any form or by any means without
prior written consent of Hewlett-Packard Development Company, L.P.
The information contained herein is subject to change without notice.
HEWLETT-PACKARD COMPANY MAKES NO WARRANTY OF ANY KIND WITH REGARD TO THIS
MATERIAL, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY
AND FITNESS FOR A PARTICULAR PURPOSE. Hewlett-Packard shall not be liable for errors contained
herein or for incidental or consequential damages in connection with the furnishing, performance, or
use of this material.
The only warranties for HP products and services are set forth in the express warranty statements
accompanying such products and services. Nothing herein should be construed as constituting an
additional warranty. HP shall not be liable for technical or editorial errors or omissions contained
herein.

i
Contents
SPBM overview ···························································································································································· 1
SPBM network model························································································································································1
Terminology ·······································································································································································1
Area···········································································································································································1
BCB ············································································································································································2
BEB·············································································································································································2
B-MAC, B-VLAN························································································································································2
Customer network port, provider network port ·····································································································2
Ethernet service instance··········································································································································2
I-SID············································································································································································2
ISIS-SPB······································································································································································2
LSDB···········································································································································································3
MAC-in-MAC ····························································································································································3
PW ·············································································································································································3
SPB VSI ······································································································································································3
SPBM packet types····························································································································································3
ISIS-SPB control packets···········································································································································3
SPBM data packet····················································································································································4
Working mechanisms ·······················································································································································4
Formation and maintenance of ISIS-SPB adjacencies ··························································································5
MAC address learning ············································································································································5
Data paths·································································································································································5
SPBM multicast address···········································································································································8
Multiple SPB VSIs ······························································································································································9
Load balancing ······························································································································································ 10
B-VLAN to ECT algorithm mapping····················································································································· 10
ECT migration ························································································································································ 11
Loop prevention······························································································································································ 12
Multicast B-VLAN···························································································································································· 12
Fast channel for quick spread of LSPs·························································································································· 12
Protocols and standards ················································································································································ 12
Configuring SPBM······················································································································································13
Configuration restrictions and guidelines···················································································································· 13
SPBM configuration task list·········································································································································· 13
Configuring basic SPBM settings on BEBs and BCBs································································································· 14
Configuring MST region parameters··················································································································· 14
Enabling SPBM ······················································································································································ 15
Configuring customer-side settings on BEBs ················································································································ 16
Enabling L2VPN ···················································································································································· 16
Creating an SPB VSI ············································································································································· 16
Assigning a B-VLAN to an SPB VSI ····················································································································· 17
Configuring Ethernet service instances on BEBs································································································· 17
Configuring the SPBM multicast replication mode on BEBs and BCBs ···································································· 18
Optimizing the SPB network ········································································································································· 18
Configuring the SPSource ID································································································································ 19
Configuring the bridge priority···························································································································· 19
Configuring a link metric value for a provider network port············································································ 19
Mapping B-VLANs to an ECT algorithm ············································································································· 20

ii
Performing ECT migration for an SPB VSI ·········································································································· 21
Enabling dynamic hostname exchange ·············································································································· 22
Configuring Graceful Restart for ISIS-SPB··········································································································· 23
Configuring NSR for ISIS-SPB······························································································································· 23
Tuning ISIS-SPB adjacency maintenance settings ······························································································ 24
Tuning ISIS-SPB LSP timers ···································································································································· 25
Tuning the SPF calculation timer ·························································································································· 27
Setting the LSDB overload bit······························································································································· 28
Enabling outputting ISIS-SPB adjacency changes to the configuration terminal············································· 28
Configuring the group MAC address for ISIS-SPB····························································································· 29
Configuring ISIS-SPB authentication ···················································································································· 29
Enabling SNMP notifications for SPBM ·············································································································· 31
Configuring the AP mode·············································································································································· 31
Enabling the multicast B-VLAN feature························································································································· 31
Displaying and maintaining SPBM ······························································································································ 32
SPBM configuration examples······································································································································ 34
Basic SPBM configuration example····················································································································· 34
ECT migration example ········································································································································ 39
Support and other resources ·····································································································································44
Contacting HP ································································································································································ 44
Subscription service ·············································································································································· 44
Related information························································································································································ 44
Documents······························································································································································ 44
Websites································································································································································· 44
Conventions ···································································································································································· 45
Index ···········································································································································································47

1
SPBM overview
IEEE 802.1aq Shortest Path Bridging (SPB) enables multipath routing in an Ethernet mesh network by
using IS-IS as the control protocol. The technology allows all paths to be active, supports equal cost paths,
and provides shortest path forwarding in an Ethernet mesh network. IEEE 802.1aq SPB provides faster
convergence, higher link efficiency, and larger Layer 2 topologies than conventional spanning tree
protocols such as MSTP.
Shortest path bridging MAC mode (SPBM) is one bridging method of IEEE 802.1aq SPB. This method
encapsulates Ethernet frames into MAC-in-MAC frames in compliance with IEEE 802.1ah PBB.
SPBM network model
As shown in Figure 1, the SPBM network includes backbone edge bridges and backbone core bridges.
Backbone edge bridges connect customer sites to the SPBM network.
The nodes in the SPBM network run ISIS-SPB to prevent loops and calculate the shortest path for a frame.
Figure 1 SPBM network model
Terminology
Area
An SPBM area is a subdomain of a routing domain. Each address has an area address. Routing within
one area is called Level-1 routing. The device supports only one area.
Customer
site Customer site
Customer
site
Customer
site
SPBM
network
BCB BCB
BCBBCB
BEB BEB
BEB BEB

2
BCB
Backbone core bridges (BCBs) are core nodes of an SPB network. They are identical to the P devices in
an MPLS VPN network. BCBs forward MAC-in-MAC frames based on the B-MAC and B-VLAN. They do
not learn customer MAC (C-MAC) addresses.
BEB
Backbone edge bridges (BEBs) are edge nodes of the SPBM network. They are identical to PEs in an
MPLS VPN network. BEBs encapsulate customer frames into MAC-in-MAC frames before forwarding
them to the SPBM network. BEBs also decapsulate MAC-in-MAC frames before sending them to a
customer site.
B-MAC, B-VLAN
Backbone MAC addresses (B-MACs) are bridge MAC addresses associated with SPBM bridges.
Backbone VLANs (B-VLANs) are VLANs assigned by the service provider for transmitting customer traffic
on the SPBM network.
For customer frames to be transmitted across an SPBM network, 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 SPBM network forward the
MAC-in-MAC frames based on the destination B-MAC and B-VLAN.
Customer network port, provider network port
On a BEB, a customer network port (CNP) connects to a customer site and a provider network port (PNP)
connects to the SPBM network.
Ethernet service instance
An Ethernet service instance provides forwarding service for a set of C-VLANs. To extend C-VLANs across
customer sites over an SPBM network, you must configure Ethernet service instances on BEBs' customer
edge ports and map them to SPB VSIs.
For more information about Ethernet service instances, see VPLS in MPLS Configuration Guide.
I-SID
A backbone services instance identifier (I-SID) uniquely identifies a MAC-in-MAC service instance (also
called an "SPB VSI") provided by the service provider.
ISIS-SPB
ISIS-SPB is the control protocol for an SPB network to calculate shortest path trees (SPTs) and maintain
adjacencies between neighbors.

3
LSDB
A link state database (LSDB) contains the states of all links in an SPBM network.
MAC-in-MAC
SPBM encapsulates Ethernet frames into MAC-in-MAC frames by using 802.1ah PBB encapsulation. For
more information about PBB, see Layer 2—LAN Switching Configuration Guide.
Customer frames are encapsulated in MAC-in-MAC format at edges of the SPBM network before they are
forwarded from one customer site to another.
PW
Pseudo wires (PWs) are MAC-in-MAC tunnels established over the SPBM network for transmitting
customer traffic.
PWs are established between BEBs. BCBs do not set up PWs.
SPB VSI
An SPB virtual service instance (SPB VSI) provides MAC-in-MAC tunnel service for Ethernet service
instances. Each SPB VSI is uniquely identified by an I-SID. For more information about VSIs, see VPLS in
MPLS Configuration Guide.
SPBM packet types
SPBM packets include ISIS-SPB control packets and SPBM data packets.
ISIS-SPB control packets
ISIS-SPB control packets include hello, LSPs, and SNP. All SPBM control packets are encapsulated in
802.1q.
Hello
SPBM neighbors send IS-IS hello (IIH) PDUs to establish and maintain adjacencies.
LSP
Adjacent SPBM neighbors send link state PDUs (LSPs) to advertise topology data.
SNP
Adjacent SPBM neighbors exchange sequence number PDUs (SNPs) for LSDB synchronization.
SNPs include complete SNP (CSNP) and partial SNP (PSNP).
•CSNP—Contains the digest of each LSP in the LSDB. Adjacent routers exchange CSNPs to maintain
LSDB synchronization.
•PSNP—Contains the sequence numbers of recently received LSPs. An SPBM node uses a PSNP to
acknowledge LSPs or request needed LSPs from a neighbor.

4
SPBM data packet
SPBM data packets use the IEEE 802.1ah MAC-in-MAC frame format, as shown in Figure 2.
Figure 2 IEEE 802.1ah-compliant MAC-in-MAC frame format
Table 1 IEEE 802.1ah encapsulated frame header fields
Field Descri
p
tion
B-DA Destination B-MAC that identifies the destination BEB.
B-SA Source B-MAC. It is a known MAC address of the BEB that encapsulates the MAC-in-MAC
frame.
B-Tag B-VLAN tag identifies the VLAN ID and priority of the frame in the SPBM network. The TPID
in the tag is fixed at 0x8100.
I-Tag
Backbone service instance tag contains the following subfields:
•TPID—A value fixed at 0x88E7 to identify the frame as an 802.1ah encapsulated frame.
•I-PCP—Transmission priority of the frame on the BEB.
•I-DEI—Drop priority of the frame on the BEB.
•I-SID—Backbone service instance identifier.
•C-DA—Customer destination MAC address.
•C-SA—Customer source MAC address.
S-Tag This field contains the outer customer VLAN ID and priority.
C-Tag This field contains the inner customer VLAN ID and priority.
Working mechanisms
To forward Layer 2 traffic between customer sites across an SPBM network, you must configure Ethernet
service instances on BEBs' customer network ports, and map Ethernet service instances to SPB VSIs.
SPBM uses ISIS-SPB in the control plane to calculate shortest path trees. It uses IEEE 802.1ah PBB
encapsulation in the data plane to encapsulate and forward traffic.
SPBM uses the following generic process to calculate SPTs and forward traffic:
1. BEBs and BCBs send ISIS-SPB P2P hellos to establish and maintain adjacencies.
2. Adjacent nodes send LSPs to advertise their respective topology data. Eventually, the LSDBs of all
nodes are synchronized.
3. Each node selects the forwarding path:

5
a. Each node runs SPF to calculate the shortest path from itself to each of the other nodes.
b. If equal-cost paths are available, each node runs ECT to choose the best forwarding path.
c. The nodes populate their respective FDB and FIB tables with the forwarding path.
4. BEBs establish PWs over the SPBM network for transmitting customer traffic.
Formation and maintenance of ISIS-SPB adjacencies
ISIS-SPB only supports point-to-point links within an IS-IS level 1. It sends P2P hellos between directly
connected nodes to form and maintain adjacencies. To forward traffic on an adjacency, two SPBM
neighbors must meet the following requirements:
•The neighbors have the same configuration digest for MSTI 4092.
•The neighbors have the same B-VLAN to ECT algorithm mapping.
•Their link metric values are valid.
MAC address learning
In an SPBM network, BEBs perform typical source MAC learning in the data plane to learn C-MACs, but
BCBs do not learn C-MACs.
BCBs forward MAC-in-MAC traffic by destination B-MAC and B-VLAN, which are advertised through
ISIS-SPB in the control plane. As a result, BCBs do not need to maintain a large MAC address table.
Data paths
For the forwarding process for known unicast frames, see "Unicast."
To avoid loops, SPBM does not support broadcast. BEBs flood broadcast, unknown unicast, and
unknown multicast frames to the SPBM network as multicast frames. For the flooding process, see
"Multicast."
Unicast
For an intra-site known unicast frame, the ingress BEB performs typical MAC address table lookup.
For a known inter-site unicast frame, the following forwarding process (see Figure 3) takes place:
1. The ingress BEB does the following:
a. Assigns the frame to the correct Ethernet service instance based on the outer VLAN.
b. Learns the source MAC address.
c. Looks up the destination MAC address in the Ethernet service instance's Ethernet address table.
2. If the outgoing interface is a provider network port, the ingress BEB does the following:
a. Encapsulates the frame as shown in Figure 2.
b. Sends the frame out of the unicast PW to the egress BEB.
The B-DA field in the outer frame header is the B-MAC of the egress BEB.
3. Each BCB on the unicast PW forwards the frame based on the B-MAC and B-VLAN in the outer
frame header until it reaches the egress BEB.
4. The egress BEB removes the outer frame header and forwards the frame to the destination
customer MAC address.

6
Figure 3 MAC-in-MAC unicast traffic over an SPBM network
Multicast
SPBM floods unknown customer unicast, unknown customer multicast, and broadcast as multicast traffic.
SPBM supports the following replication methods for multicast:
•Head-end replication—Replicates frames at the ingress BEB for frames to enter the SPBM network.
This method is suitable for SPB VSIs that have sparse multicast traffic. It does not require BCBs to
maintain multicast FDB entries.
•Tandem replication—Replicates frames only at the node where the shortest path tree forks. This
method is suitable for SPB VSIs that have dense multicast traffic. It requires BCBs to maintain
multicast FDB entries.
In head-end replication, the ingress BEB does the following, as shown in Figure 4:
1. Replicates the customer frame for each destination BEB.
2. Encapsulates each replica in one unicast frame.
3. Sends the unicast frames to the destination BEBs.

7
Figure 4 Head-end replication
In tandem replication, the source BEB encapsulates a frame with a B-DA multicast address that uniquely
identifies itself and the SPBM service. When this frame arrives at the BCB where the shortest path tree
forks, the BCB replicates one frame for each destination BEB, as shown in Figure 5.
B-DA
BEB2Data
B-SA
BEB1B-VLAN
100I-SID
300
B-DA
BEB3Data
B-SA
BEB1B-VLAN
100I-SID
300
XGE1/0/2
XGE1/0/3XGE1/0/1
XGE1/0/1

8
Figure 5 Tandem replication
SPBM multicast address
Each SPBM node has a multicast address for each SPB VSI. This multicast address consists of one shortest
path source identifier (SPSource ID) and one I-SID. The I-SID identifies an SPB VSI, and the SPSource ID
identifies the node as a multicast source in the SPB VSI.
By default, ISIS-SPB generates the SPSource ID automatically. You may choose to configure the SPSource
ID manually, but the SPSource ID must be unique throughout the SPBM network.
Figure 6 SPBM multicast address format

9
Table 2 SPBM multicast address fields
Field Descri
p
tion
M 1-bit multicast flag. Its value is fixed at 1.
L 1-bit local flag bit. Its value is fixed at 1.
TYP 2-bit SPSource ID type. Its value is fixed at 0.
SPSource ID 20-bit SPSource ID.
I-SID 24-bit SPB VSI identifier.
In the figure, LSB represents the lower 4 bits of a byte, and MSB represents the higher 4 bits of a byte. The
first byte of an SPBM multicast address is identical to the combination of the first 4 bits of the SPSource
ID field, the TYP field, the L field, and the M field. For example, in the SPBM multicast address
E386070006E9, the first byte 11100011 (E3 in hexadecimal format) consists of 1110 (first 4 bits of
SPSource ID), 00 (TYP), 1 (L), and 1 (M).
Multiple SPB VSIs
You can use multiple SPB VSIs to transmit traffic for different Ethernet services that span different customer
sites. Each SPB VSI is identified by a unique I-SID.
For example, the network in Figure 7 has three SPB VSIs:
•I-SID 300 extends traffic to customer sites B, C, and D.
•I-SID 400 extends traffic to all customer sites.
•I-SID 500 extends traffic to customer sites A and D.
All traffic in one SPB VSI is transmitted in one B-VLAN. Different SPB VSIs can use the same B-VLAN to
transmit traffic. Traffic of different SPB VSIs is isolated by I-SID.

10
Figure 7 Multiple SPB VSIs
Load balancing
To balance traffic between forwarding paths, you can map B-VLANs to different ECT algorithms. When
a path is approaching congestion, you can move part of traffic on one path to another by moving an
I-SID from one ECT algorithm to another.
B-VLAN to ECT algorithm mapping
For balanced traffic distribution, SPBM supports calculating one SPT for a set of B-VLANs by using
different ECT algorithms. IEEE 802.1aq SPB provides 16 ECT algorithms. Each algorithm represents a set
of tie-break rules. As a result, you can have up to 16 forwarding paths in an SPBM network.
Figure 8 shows two SPTs that are calculated by using two ECT algorithms.
Customer site B
Customer site A
Customer site E
Customer site D
Customer site C
VSI 3
VSI 2
BEB
I-SID 400
I-SID 500
BEB
I-SID 300
I-SID 400
BEB
I-SID 400
BEB
I-SID 300
I-SID 400
I-SID 500
BEB
I-SID 300
I-SID 400
VSI 1
SPBM
network

11
Figure 8 Multiple SPTs in an SPBM network
ECT migration
ECT migration enables an I-SID to migrate from one ECT algorithm to another with minimum traffic loss.
To prevent traffic loss, ECT migration was designed based on the idea of make-before-break. All nodes
in the SPBM network maintain the old path for the I-SID before a new path is set up. The SPBM nodes
remove the old path only after all affected traffic has been moved from the old path to the new path for
the I-SID.
As shown in Figure 9, two paths (path A and path B) are available between BEB 1 and BEB 2. B-VLAN
300 has been using path A. As path A is getting congested, you can perform ECT migration to move part
of B-VLAN traffic (for example, traffic in I-SID 400) to path B.
Figure 9 ECT migration
Customer site B
Customer site A
Customer site F
Customer site E
Customer site C
BEB
BEB
BEB
BEB
BEB
Customer site D
BEB
BCB BCB
SPBM
network
ECT 1 B-VLANs 100-200
ECT 2 B-VLANs 300-400
BCB 1
BCB 2
Customer
network
Customer
network
BEB 1 BEB 2
SPBM network
Path A (ECT 1)
Path B (ECT 2)
I-SID 400 B-VLAN 300
B-VLAN 300 ECT 1
B-VLAN 300 ECT 2
B-VLAN 300 ECT 1
B-VLAN 300 ECT 2
CNP
I-SID 400 B-VLAN 300
B-VLAN 300 ECT 1
B-VLAN 300 ECT 2
CNP

12
Loop prevention
SPBM nodes collect topology data independently to calculate forwarding paths. Transient loops might
occur during SPT recalculation caused by a network flapping because the latency varies for an LSP to
reach the SPBM nodes. SPBM uses the Agreement Protocol (AP) to prevent transient loops. AP introduces
a delay for ISIS-SPB to issue forwarding entries to the data plane. After a topology recalculation, ISIS-SPB
issues new forwarding entries to the data plane only if topology data is synchronized between the SPBM
node and its adjacent neighbors.
NOTE:
Do not confuse the "AP" in this document with access points, which are wireless access devices.
Multicast B-VLAN
By default, the device uses one B-VLAN to transmit both unicast and multicast traffic.
If the multicast B-VLAN feature is enabled, you must assign an odd B-VLAN ID to an I-SID for SPBM to
transmit unicast traffic. SPBM automatically chooses the next higher even B-VLAN ID (odd B-VLAN ID plus
1) for multicast traffic.
ISIS-SPB only advertises the odd B-VLAN IDs. It uses the odd B-VLAN IDs when populating the unicast
FDB table with routes. When populating the multicast FDB table with routes, it uses the even B-VLAN IDs.
Fast channel for quick spread of LSPs
The fast-channel feature provides a quicker LSP propagation method than conventional LSP propagation.
This feature spreads ISIS-SPB LSPs in the SPBM network by forwarding LSPs as data packets along the SPT
in a dedicated SPB VSI. An SPBM node does not need to complete updating its LSDB before it
propagates the topology change to the next node.
The I-SID for the fast-channel VSI is 255. To use the fast-channel feature, you must create a VSI and assign
I-SID 255 to the VSI.
You cannot associate any Ethernet service instance with the VSI that uses I-SID 255 for data transmission.
Protocols and standards
•IEEE 802.1aq, Shortest Path Bridging
•IEEE 802.1ah, Virtual Bridged Local Area Networks Amendment 7: Provider Backbone Bridges
•ISO 10589, ISO IS-IS Routing Protocol
•RFC 6329, IS-IS Extensions Supporting IEEE 802.1aq Shortest Path Bridging

13
Configuring SPBM
Configuration restrictions and guidelines
When you use SPBM in conjunction with other features, follow the restrictions and guidelines in Table 3.
Table 3 SPBM and other features compatibility
Feature Restrictions and
g
uidelines
IRF
You must configure the irf mac-address persistent always command to prevent the
IRF bridge MAC address from changing after a master re-election. For more
information about IRF bridge MAC persistence, see IRF Command Reference.
IS-IS Provider network ports on BEBs and BCBs cannot be used for setting up standard
IS-IS adjacencies.
Static MAC
If a B-MAC is the same as a static MAC in the MAC address table, remove the
static MAC. The device can forward SPBM packets to the B-MAC only after the
conflict is removed.
Spanning tree
The spanning tree mode must be set to MSTP.
SPBM runs on MSTI 4092. For SPBM to run correctly, make sure MSTI 4092 is not
used by Smart Link. For more information about Smart Link, see High Availability
Configuration Guide.
VLAN
Do not use B-VLANs for other purposes such as VLAN interfaces. Before specifying
a VLAN as a B-VLAN, you must remove all features that have been configured on
the VLAN.
You must configure the provider network ports on BEBs and BCBs as trunk or
hybrid ports, and assign them to all B-VLANs as tagged VLAN members.
SPBM configuration task list
Tasks at a
g
lance Remarks
(Required.) Configuring basic SPBM settings on BEBs and
BCBs:
•Configuring MST region parameters
•Enabling SPBM
You must map B-VLANs to MSTI 4092, and
enable SPBM both globally and on the provider
network ports in the SPBM network.
(Required.) Configuring customer-side settings on BEBs:
•Enabling L2VPN
•Creating an SPB VSI
•Assigning a B-VLAN to an SPB VSI
•Configuring Ethernet service instances on BEBs
Configure customer-side settings to map Ethernet
service instances to SPB VSIs for extending
C-VLANs across different sites.
Each Ethernet service instance represents a set of
C-VLANs.

14
Tasks at a
g
lance Remarks
(Required.) Configuring the SPBM multicast replication
mode on BEBs and BCBs
Make sure the multicast replication mode for an
SPB VSI is the same across all SPBM nodes.
(Optional.) Optimizing the SPB network:
•Configuring the SPSource ID
•Optimizing traffic distribution:
{Configuring the bridge priority
{Configuring a link metric value for a provider network
port
{Mapping B-VLANs to an ECT algorithm
{Performing ECT migration for an SPB VSI
•Enabling dynamic hostname exchange
•Configuring Graceful Restart for ISIS-SPB
•Configuring NSR for ISIS-SPB
•Configuring ISIS-SPB throttling timers:
{Tuning ISIS-SPB adjacency maintenance settings
{Tuning ISIS-SPB LSP timers
{Tuning the SPF calculation timer
{Setting the LSDB overload bit
•Enabling outputting ISIS-SPB adjacency changes to the
configuration terminal
•Configuring the group MAC address for ISIS-SPB
•Configuring ISIS-SPB authentication:
{Configuring ISIS-SPB adjacency authentication
{Configuring ISIS-SPB area authentication
•Enabling SNMP notifications for SPBM
IMPORTANT:
To ensure correct path selection and traffic
forwarding, make sure B-VLAN to ECT algorithm
mappings and ISIS-SPB timer settings are
consistent across the network.
By default, all B-VLANs are mapped to ECT
algorithm 1. To optimize traffic distribution, map
B-VLANs to different ECT algorithms. To affect
the path selection result, you could change the
bridge priority and link metric values.
The following features help you manage the
network with ease:
•Dynamic hostname exchange—Enables you
to identify SPBM nodes with symbolic
hostnames.
•Adjacency change logging—Enables you to
track all adjacency changes. To suppress
frequent adjacency change messages,
disable this function.
•SNMP notifications for SPBM—Enables you
to send SPBM event notifications to an NMS.
(Optional.) Configuring the AP mode
Perform this task to prevent temporary loops that
might occur when the topologies of SPBM
neighbors do not match.
(Optional.) Enabling the multicast B-VLAN feature Perform this task if tandem multicast replication is
used.
Configuring basic SPBM settings on BEBs and BCBs
For SPBM to run, you must configure all settings in this section on all BEBs and BCBs.
Configuring MST region parameters
CAUTION:
Changing MST region settings causes spanning tree recalculation. Make sure you understand the impac
t
of this task on your network before you activate the MST region settings.

15
SPBM runs on MSTI 4092. For two SPBM neighbors to establish an adjacency, you must activate MSTI
4092 on both of them and make sure their in-between link has connectivity. To forward traffic on the link,
you must also configure the same MST region parameters on the devices, including:
•Format selector. The value for this parameter is fixed at 0.
•Region name.
•Revision level.
•VLAN-to-MSTI mapping table.
To configure MST region parameters on a BEB or BCB:
Step Command Remarks
1. Enter system view. system-view N/A
2. Enter MST region view. stp region-configuration N/A
3. Configure the MST
region name. region-name name The default MST region name is the MAC
address of the device.
4. Configure the MSTP
revision level. revision-level level The default MSTP revision level is 0.
5. Map B-VLANs to MSTI
4092.
instance instance-id vlan
vlan-id-list
The value for the instance-id argument must
be 4092.
By default, all VLANs are mapped to the
CIST (MSTI 0).
6. Activate the MST region
configuration. active region-configuration N/A
Enabling SPBM
You must enable SPBM both globally and on the provider network ports on all BEBs and BCBs in the
SPBM network.
To enable SPBM:
Step Command Remarks
1. Enter system view. system-view N/A
2. Enable SPBM globally. spbm By default, SPBM is disabled
globally.
3. Return to system view. quit N/A
4. Enter Layer 2 Ethernet
interface view or Layer 2
aggregate interface view.
interface interface-type
interface-number N/A
5. Enable SPBM on the
interface. spbm enable By default, SPBM is disabled on
interfaces.
6. Configure the port link
type. port link-type { trunk |hybrid } By default, a port is an access port.

16
Step Command Remarks
7. Assign the interface to the
port VLAN (PVID) as an
untagged member, and
assign the interface to all
B-VLANs as a tagged
member.
•Trunk link type:
port trunk permit vlan
{ vlan-id-list | all }
•Hybrid link type:
port hybrid vlan vlan-id-list
{ tagged | untagged }
ISIS-SPB protocol frames are
transmitted untagged on links. An
SPBM-enabled interface will drop
these frames if it is not assigned to the
port VLAN as an untagged member.
Configuring customer-side settings on BEBs
All tasks in this section are required.
Enabling L2VPN
Ste
p
Command Remarks
1. Enter system view. system-view N/A
2. Enable L2VPN. l2vpn enable
By default, L2VPN is disabled.
For more information about this command, see
VPLS commands in MPLS Command Reference.
Creating an SPB VSI
SPBM uses a unique I-SID to identify an SPB VSI. An SPB VSI's I-SID must be the same across the SPBM
network.
I-SID 255 is reserved for the fast channel. You cannot associate any Ethernet service instance with the VSI
that uses I-SID 255.
To use the fast-channel feature, you must create a VSI and assign I-SID 255 to the VSI.
To create an SPB VSI:
Step Command Remarks
1. Enter system view. system-view N/A
2. Create a VSI. vsi vsi-name
By default, no VSIs exist.
For more information about this command, see VPLS
commands in MPLS Command Reference.
3. Assign an SPB I-SID to
the VSI. spb i-sid i-sid
By default, a VSI does not have an SPB I-SID. You
can configure one SPB I-SID and one PBB I-SID for
one VSI, but the two I-SIDs cannot be the same.
For more information about PBB, see Layer 2—LAN
Switching Configuration Guide.