Spbm Provisioning - Avaya 8800 Planning And Engineering, Network Design

Ethernet routing switch
Hide thumbs Also See for 8800:
Table of Contents

Advertisement

SPBM design guidelines
• If no matching instance of the I-SID exists in the SPBM network, then that VLAN has no
reachable members and does not act as an NNI interface.
The VLAN does not act as a UNI interface because it does not have a member port.
Therefore, the device does not designate the VLAN as operationally up because the VLAN
does not act as a UNI or an NNI interface.
If the device acts as a BCB with two VLANs configured and two I-SIDs, there must be a UNI side
with the corresponding I-SID existing in the network.
If the device acts as both BEB and BCB, then there must be a member port in that VLAN to push
out the UNI traffic.
Related links
SPBM design guidelines

SPBM provisioning

This section summarizes how to provision SPBM. For information on specific configuration
commands, see Avaya Ethernet Routing Switch 8800/8600 Configuration — Shortest Path Bridging
MAC (SPBM) (NN46205–525).
Infrastructure provisioning
Provisioning an SPBM core is as simple as enabling SPBM and IS-IS globally and on all the IS-IS
core Ethernet links on all the BCB and BEB nodes. The IS-IS protocol operates at layer 2 so it does
not need IP addresses configured on the links to form IS-IS adjacencies with neighboring switches
(like OSPF does). Hence there is no need to configure any IP addresses on any of the core links.
The encapsulation of customer MAC addresses in backbone MAC addresses greatly improves
network scalability.
There is no flooding and learning of end-user MACs in the backbone. This SPBM provisioning
significantly improves network robustness, as customer-introduced network loops have no effect on
the backbone infrastructure.
Service provisioning
Provision I-SIDs on a BEB to associate that BEB with a particular service instance. After you map
the customer VLAN or VRF into an I-SID, any BEB that has the same I-SID configured can
participate in the same L2 or L3 virtual services network (VSN). This same simplicity extends to
provisioning the services to run above the SPBM backbone.
• To create an L2 VSN, associate an I-SID number with an edge VLAN.
• To create an L3 VSN, associate an I-SID number with a VRF and configure the desired IS-IS
IP route redistribution within the newly created L3 VSN.
Note:
There is no service provisioning needed on the core BCB SPBM switches. This provides a
robust carrier grade architecture where configuration on the core switches never needs to be
touched when adding new services.
June 2016
on page 138
Planning and Engineering — Network Design
Comments on this document? infodev@avaya.com
142

Advertisement

Table of Contents
loading

This manual is also suitable for:

8600

Table of Contents