HPE FlexFabric 12900E User manual

HPE FlexFabric 12900E & 12900
SPB
Configuration Guide
Part number: 5998-8715R
Software version: Release 1135 and later
Document version: 6W102-20151124

© Copyright 2015 Hewlett Packard Enterprise Development LP
The information contained herein is subject to change without notice. The only warranties for Hewlett Packard
Enterprise 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. Hewlett
Packard Enterprise shall not be liable for technical or editorial errors or omissions contained herein.
Confidential computer software. Valid license from Hewlett Packard Enterprise required for possession, use, or
copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software
Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor’s
standard commercial license.
Links to third-party websites take you outside the Hewlett Packard Enterprise website. Hewlett Packard
Enterprise has no control over and is not responsible for information outside the Hewlett Packard Enterprise
website.
Acknowledgments
Intel®, Itanium®, Pentium®, Intel Inside®, and the Intel Inside logo are trademarks of Intel Corporation in the
United States and other countries.
Microsoft® and Windows® are trademarks of the Microsoft group of companies.
Adobe® andAcrobat® are trademarks ofAdobe Systems Incorporated.
Java and Oracle are registered trademarks of Oracle and/or its affiliates.
UNIX® is a registered trademark of The Open Group.

i
Contents
SPBM overview·······························································································1
SPBM network model ········································································································································1
Terminology ·······················································································································································1
AC······························································································································································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··························································································································································2
MAC-in-MAC··············································································································································2
PW ·····························································································································································3
SPB VSI·····················································································································································3
SPBM packet types············································································································································3
ISIS-SPB control packets···························································································································3
SPBM data packet ·····································································································································3
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··········································································································································10
Loop prevention ···············································································································································11
Fast channel for quick spread of LSPs ············································································································11
Protocols and standards ··································································································································11
Configuring SPBM ························································································12
Feature and software version compatibility······································································································12
Configuration restrictions and guidelines·········································································································12
SPBM configuration task list ····························································································································12
Configuring basic SPBM settings on BEBs and BCBs ····················································································14
Configuring MST region parameters········································································································14
Enabling SPBM········································································································································14
Configuring customer-side settings on BEBs···································································································15
Enabling L2VPN·······································································································································15
Creating an SPB VSI································································································································15
Assigning a B-VLAN to an SPB VSI·········································································································16
Configuring Ethernet service instances on BEBs·····················································································16
Configuring SPBM multicast settings···············································································································17
Configuring the SPBM multicast replication mode on BEBs····································································17
Setting the SPSource ID··························································································································17
Optimizing traffic distribution····························································································································18
Setting the bridge priority·························································································································18
Setting a link metric value for a provider network port·············································································18
Mapping B-VLANs to an ECT algorithm···································································································19
Performing ECT migration for an SPB VSI ······························································································19
Configuring the AP mode·································································································································21
Optimizing the SPBM network ·························································································································21
Enabling dynamic hostname exchange ···································································································21
Tuning ISIS-SPB adjacency maintenance settings··················································································22
Tuning ISIS-SPB LSP timers ···················································································································23

ii
Tuning the SPF calculation timer·············································································································25
Setting the LSDB overload bit··················································································································26
Configuring the control MAC address for ISIS-SPB·················································································26
Configuring ISIS-SPB authentication···············································································································27
Configuring ISIS-SPB adjacency authentication······················································································27
Configuring ISIS-SPB area authentication·······························································································27
Configuring Graceful Restart for ISIS-SPB······································································································28
Configuring SNMP notifications for SPBM·······································································································29
Enabling ISIS-SPB adjacency change logging ································································································29
Displaying and maintaining SPBM···················································································································30
SPBM configuration examples·························································································································32
Basic SPBM configuration example·········································································································32
SPBM with head-end replication configuration example··········································································36
SPBM with tandem replication configuration example·············································································39
ECT migration by changing B-VLAN example·························································································42
ECT migration by changing ECT algorithm example···············································································46
Document conventions and icons·································································51
Conventions·····················································································································································51
Network topology icons····································································································································52
Support and other resources ········································································53
Accessing Hewlett Packard Enterprise Support ······························································································53
Accessing updates···········································································································································53
Websites ··················································································································································54
Customer self repair·································································································································54
Remote support········································································································································54
Documentation feedback ·························································································································54
Index·············································································································55

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.
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
AC
An attachment circuit (AC) is a physical or virtual link that connects a customer site to a backbone
edge bridge.
Area
An SPBM area is a subdomain of an SPBM network. 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 SPBM 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. 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.
I-SID
A backbone service 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 SPBM network to calculate shortest path trees (SPTs) and
maintain adjacencies between neighbors.
LSDB
A link state database (LSDB) contains the states of all links in an SPBM network.
MAC-in-MAC
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.

3
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.
On an interface, incoming frames are assigned to the same PW if they match the frame match
criterion of the same Ethernet service instance.
SPB VSI
An SPB virtual switch instance (SPB VSI) provides MAC-in-MAC tunnel service for Ethernet service
instances. Each SPB VSI is uniquely identified by an I-SID.
SPBM packet types
SPBM packets include ISIS-SPB control packets and SPBM data packets.
ISIS-SPB control packets
ISIS-SPB control packets include hello, LSP, 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 to request needed LSPs from a neighbor.
SPBM data packet
SPBM data packets use the IEEE 802.1ah MAC-in-MAC frame format, as shown in Figure 2.

4
Figure 2 IEEE 802.1ah-compliant MAC-in-MAC frame format
Table 1 IEEE 802.1ah encapsulated frame header fields
Field Description
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.
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:
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.

5
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.
•The neighbors have valid link metric values.
NOTE:
In SPBM, you must map all B-VLANs to MSTI 4092.
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, multicast, and unknown
unicast 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 takes place, as shown
in Figure 3:
1. The ingress BEB performs the following tasks:
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 performs the following
tasks:
a. Encapsulates the frame in IEEE 802.1ah format.
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 broadcast, customer multicast, and unknown customer unicast 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 performs the following tasks, 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.
Customer
network
Customer
network
BEB 1
BEB 2
SPBM
network
BCB
FGE1/0/1 FGE1/0/1
FGE1/0/2FGE1/0/1
CNP
CNP
B-DA
BEB2Data
B-SA
BEB1B-VLAN
100I-SID
300
Data
Data
Customer
network
B-DA
BEB2 Data
B-SA
BEB1 B-VLAN 100 I-SID 300
BEB 3
CNP
Data
B-DA
BEB3 Data
B-SA
BEB1 B-VLAN 100 I-SID 300
FGE1/0/3
B-DA
BEB3Data
B-SA
BEB1B-VLAN
100I-SID
300
FGE1/0/1
B-MAC
BEB2
B-VLAN
100 FGE1/0/1
Port
BEB3 100 FGE1/0/1
BEB2
BEB1 100
100
FGE1/0/1
FGE1/0/2
B-MAC B-VLAN Port
BEB3 100 FGE1/0/3
B-MAC
BEB1
B-VLAN
100 FGE1/0/1
Port
BEB2 100 FGE1/0/1
B-MAC
BEB1
B-VLAN
100 FGE1/0/1
Port
BEB3 100 FGE1/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.
Figure 6 SPBM multicast address format
Table 2 SPBM multicast address fields
Field Description
M 1-bit multicast flag. Its value is fixed at 1.
Customer
network
Customer
network
BEB 1
BEB 2
SPBM network
BCB
CNP
CNP
B-DA
M-BEB1Data
B-SA
BEB1B-VLAN
100I-SID
300
Data
Data
Customer
network
BEB 3
CNP
Data
B-DA
M-BEB1 Data
B-SA
BEB1 B-VLAN 100 I-SID 300
B-DA
M-BEB1Data
B-SA
BEB1B-VLAN
100I-SID
300
B-MAC
M-BEB1
B-VLAN
100
Port
M-BEB2
M-BEB1 100
100
B-MAC B-VLAN Port
M-BEB3 100
B-MAC
M-BEB3
B-VLAN
100
Port
B-MAC
M-BEB2
B-VLAN
100
Port
FGE 1/0/1 FGE 1/0/1
FGE1/0/1
FGE 1/0/3
FGE 1/0/2
FGE1/0/1
FGE1/0/1
FGE1/0/2，FGE1/0/3
FGE1/0/1，FGE1/0/3
FGE1/0/1，FGE1/0/2
FGE1/0/1
FGE1/0/1

9
Field Description
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 Figure 6, 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, the hexadecimal form of
the first byte (E3) in the SPBM multicast address E386070006E9 is 11100011. This byte 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 the following 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 sitesAand 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.
Figure 7 Multiple SPB VSIs
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

10
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.
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 pathAis getting congested, you can perform ECT migration
to move part of B-VLAN traffic (for example, traffic in I-SID 400) to path B.
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

11
Figure 9 ECT migration
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. To prevent transient loops, SPBM uses the Agreement Protocol (AP)
to exchange LSDB synchronization status. 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:
In this document, "AP" refers to agreement protocol. In other documents, "AP" can also refer to
access points.
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
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
Configuring SPBM
Feature and software version compatibility
The SPBM feature is available in Release 1137 and later versions.
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 guidelines
IRF
You must configure the irf mac-address persistent always command to
prevent the IRF bridge MAC address from changing after the address owner
leaves. 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.
Spanning tree
The spanning tree mode must be set to MSTP.
For SPBM neighbors to establish adjacencies, you must map all B-VLANs to
MSTI 4092, and make sure their in-between links have connectivity.
To forward traffic on an SPBM network, you must assign all SPBM nodes to the
same MST region.
Static MAC If a B-MAC is the same as a static MAC in the MAC address table, remove the static MAC entry. The device can forward SPBM packets to the B-MAC only
after the conflict is removed.
System operating mode
Before you can configure SPBM, you must perform the following tasks:
1. Set the system operating mode to enhanced Layer 2 by using the
system-working-mode bridgee command.
2. Save the configuration.
3. Delete the binary .mdb next-startup configuration file.
4. Reboot the device.
For more information about setting the system operating mode, see device
management in Fundamentals Configuration Guide.
VLAN Do not use B-VLANs for other purposes. Before specifying a VLAN as a
B-VLAN, you must remove all features that have been configured on the VLAN.
SPBM configuration task list
Tasks at a glance 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.

13
Tasks at a glance Remarks
(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.
Configuring SPBM multicast settings:
•(Required.) Configuring the SPBM multicast replication
mode on BEBs
•(Optional.) Setting the SPSource ID
Make sure the multicast replication mode
for an SPB VSI is the same across all
BEBs.
(Optional.) Optimizing traffic distribution:
•Setting the bridge priority
•Setting a link metric value for a provider network port
•Mapping B-VLANs to an ECT algorithm
•Performing ECT migration for an SPB VSI
To obtain a desirable path, you can
change the bridge priority and link metric
values.
By default, all B-VLANs are mapped to
ECT algorithm 1. To optimize traffic
distribution, map B-VLANs to different
ECT algorithms.
(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.) Optimizing the SPBM network:
•Enabling dynamic hostname exchange
•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
•Configuring the control MAC address for ISIS-SPB
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.
Dynamic hostname exchange enables
you to identify SPBM nodes with symbolic
hostnames.
(Optional.) Configuring ISIS-SPB authentication:
•Configuring ISIS-SPB adjacency authentication
•Configuring ISIS-SPB area authentication
Configure ISIS-SPB authentication to
improve security in an SPBM network.
(Optional.) Configuring Graceful Restart for ISIS-SPB
Enable this feature before you re-enable
SPBM or perform an active/standby
switchover. Graceful Restart ensures
nonstop forwarding while ISIS-SPB
processes are re-establishing their
adjacency.
(Optional.) Configuring SNMP notifications for SPBM Configure SNMP notifications for SPBM to send SPBM event notifications to an
NMS.
(Optional.) Enabling ISIS-SPB adjacency change logging Enable this feature to track all adjacency
changes. To suppress frequent adjacency
change messages, disable this feature.

14
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
impact on your network before you activate the MST region settings.
SPBM runs on MSTI 4092. For two SPBM neighbors to establish an adjacency, you must activate
MSTI 4092 on both neighbors 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.
For more information about MST region configuration commands, see spanning tree commands in
Layer 2—LAN Switching Command Reference.
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. Set 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
By default, all VLANs are mapped
to the CIST (MSTI 0).
The value for the instance-id
argument must be 4092.
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.
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.
ISIS-SPB protocol frames are transmitted untagged on links. To prevent SPBM-enabled interfaces
from dropping these frames, assign each SPBM-enabled interface to the port VLAN (PVID) as an
untagged member. Make sure the PVIDs have been created on the device.

15
To enable SPBM:
Step Command Remarks
1. Enter system view. system-view N/A
2. Enable SPBM globally and
enter SPBM view. 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 } The default link type of a port is
access.
7. Assign the interface to the
port VLAN (PVID) as an
untagged member.
•Trunk link type:
port trunk permit vlan
{ vlan-id-list | all }
•Hybrid link type:
port hybrid vlan vlan-id-list
untagged
N/A
8. 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
N/A
Configuring customer-side settings on BEBs
All tasks in this section are required.
Enabling L2VPN
For SPBM settings to take effect, you must enable L2VPN.
To enable L2VPN:
Step Command Remarks
1. Enter system view. system-view N/A
2. Enable L2VPN. l2vpn enable By default, L2VPN is disabled.
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.

16
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.
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.
Assigning a B-VLAN to an SPB VSI
For an SPB VSI, you must specify the same I-SID and B-VLAN across all BEBs and BCBs. You can
assign only one B-VLAN to an SPB VSI, but different SPB VSIs can use the same B-VLAN.
To assign a B-VLAN to an SPB VSI:
Step Command Remarks
1. Enter system view. system-view N/A
2. Enter VSI view. vsi vsi-name N/A
3. Enter SPB I-SID view. spb i-sid i-sid N/A
4. Assign a B-VLAN to the SPB
VSI. b-vlan vlan-id By default, an SPB VSI does not
have a B-VLAN.
Configuring Ethernet service instances on BEBs
For a BEB to identify C-VLANs that must be extended across sites, you must configure Ethernet
service instances on its customer network ports to map C-VLANs to SPB VSIs.
When you configure Ethernet service instances, follow these restrictions and guidelines:
•An SPB VSI can be mapped to multiple Ethernet service instances on the same port or different
ports.
•For correct traffic processing, do not use the outer VLAN specified with the encapsulation
command to provide any other services, including Layer 2 and Layer 3 services.
NOTE:
The outer VLAN refers to the C-VLAN for a single-tagged frame and the S-VLAN for a
double-tagged frame.
To configure an Ethernet service instance on a customer network 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. Configure the port link type. port link-type { access | trunk |
hybrid } The default port link type is
access.