Design Reference
Table Of Contents
- Contents
- Chapter 1: Introduction
- Chapter 2: New in Release 4.0.50
- Chapter 3: New in Release 4.0.40
- Chapter 4: New in Release 4.0
- Chapter 5: Network design fundamentals
- Chapter 6: Hardware fundamentals and guidelines
- Chapter 7: Optical routing design
- Chapter 8: Platform redundancy
- Chapter 9: Link redundancy
- Chapter 10: Layer 2 loop prevention
- Chapter 11: Spanning tree
- Chapter 12: Layer 3 network design
- Chapter 13: SPBM design guidelines
- Chapter 14: 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
- Multicast for multimedia
- Chapter 15: System and network stability and security
- Chapter 16: QoS design guidelines
- Chapter 17: Layer 1, 2, and 3 design examples
- Chapter 18: Software scaling capabilities
- Chapter 19: Supported standards, RFCs, and MIBs
- Glossary
nick-name : b:b0:<node-id>
MEP-id : md.ma.<node-id>
BMAC : 00:bb:00:00:<node-id>:00
VirtBMAC : 00:bb:00:00:<node-id>:ff
MD : spbm (level 4)
MA : 4040 & 4041
mep : <node-id>
mip : (level 4)
isis manual area : 49.0001
Related Links
SPBM design guidelines on page 71
SPBM restrictions and limitations
This section describes the restrictions and limitations associated with SPBM on VSP 4000.
RSTP and MSTP
The following list identifies restrictions and limitations associated with RSTP and MSTP:
• RSTP mode does not support SPBM.
• Because Avaya supports non-SPBM C-VLANs to also span the SPBM network, MSTP can be
provisioned in the network to provide loop-free connectivity for these non-SPBM C-VLANs.
Because all ports on the VSP 4000 system including IS-IS enabled NNI ports belong to MSTP
instance 0, Avaya recommends provisioning the non-SPBM C-VLANs in an MSTP instance
other than 0.
• SPBM NNI ports are not part of the Layer 2 VSN C-VLAN, and BPDUs are not transmitted over
the SPBM tunnel. SPBM can only guarantee loop-free topologies consisting of the NNI ports.
Avaya recommends that you always use Simple Loop Prevention Protocol (SLPP) for loop
prevention.
Note:
Avaya recommends that you deploy SLPP on C-VLANs to detect loops created by
customers in their access networks. However, SLPP is not required on B-VLANs, and it is
not supported. The B-VLAN active topology is controlled by IS-IS that has loop mitigation
and prevention capabilities built into the protocol.
• SPB internally uses spanning tree group (STG) 63 or Multiple Spanning Tree Instance (MSTI)
62. STG 63 or MSTI 62 cannot be used by another VLAN or MSTI. For non-SPB customer
networks, if you use STG 63 or MSTI 62 in the configuration, you must delete STG 63 or MSTI
62 before you can configure SPBM.
• You must configure SPBM B-VLANs on all devices in the same MSTP region. MSTP requires
this configuration to generate the correct digest.
SPBM IS-IS
The following list identifies restrictions and limitations associated with SPBM IS-IS:
• The current release does not support IP over IS-IS as defined by RFC1195. IS-IS protocol is
only to facilitate SPBM.
SPBM restrictions and limitations
December 2014 Network Design Reference for Avaya VSP 4000 Series 101
Comments? infodev@avaya.com