Design Reference
Table Of Contents
- Contents
- Chapter 1: Introduction
- Chapter 2: New in this release
- Chapter 3: Network design fundamentals
- Chapter 4: Hardware fundamentals and guidelines
- Chapter 5: Optical routing design
- Chapter 6: Platform redundancy
- Chapter 7: Link redundancy
- Chapter 8: Layer 2 loop prevention
- Chapter 9: Layer 2 switch clustering and SMLT
- Chapter 10: Layer 3 switch clustering and RSMLT
- Chapter 11: Layer 3 switch clustering and multicast SMLT
- Chapter 12: Spanning tree
- Chapter 13: Layer 3 network design
- Chapter 14: SPBM design guidelines
- Chapter 15: IP multicast network design
- Multicast and VRF-Lite
- Multicast and MultiLink Trunking considerations
- Multicast scalability design rules
- IP multicast address range restrictions
- Multicast MAC address mapping considerations
- Dynamic multicast configuration changes
- IGMPv3 backward compatibility
- IGMP Layer 2 Querier
- TTL in IP multicast packets
- Multicast MAC filtering
- Guidelines for multicast access policies
- Split-subnet and multicast
- Protocol Independent Multicast-Sparse Mode guidelines
- Protocol Independent Multicast-Source Specific Multicast guidelines
- Multicast for multimedia
- Chapter 16: System and network stability and security
- Chapter 17: QoS design guidelines
- Chapter 18: Layer 1, 2, and 3 design examples
- Glossary
When the VLAN is operationally up, the IP address of the VLAN will be in the routing table.
• 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.
Provisioning
This section summarizes how to provision SPBM. For information about specific configuration
commands, see Configuring Avaya Fabric Connect on VSP Operating System Software,
NN47227-510.
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). You do not need to configure IP addresses on any of the core links. The
encapsulation of customer MAC addresses in backbone MAC addresses greatly improves network
scalability.
No flooding or learning of end-user MACs occurs 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 Layer 2 or Layer 3 VSN. This same simplicity extends to provisioning the
services to run above the SPBM backbone:
• To create a Layer 2 VSN, associate an I-SID number with an edge VLAN.
• To create a Layer 3 VSN, associate an I-SID number with a VRF and configure the desired IS-
IS IP route redistribution within the newly created Layer 3 VSN.
Note:
No service provisioning is needed on the core BCB SPBM switches. This provides a robust
carrier grade architecture where configuration on the core switches never needs to be updated
when adding new services.
SPBM design guidelines
96 Network Design Reference for Avaya VSP 4000 Series June 2015
Comments on this document? infodev@avaya.com










