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: Spanning tree
- Chapter 10: Layer 3 network design
- Chapter 11: SPBM design guidelines
- Chapter 12: 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 13: System and network stability and security
- Chapter 14: QoS design guidelines
- Chapter 15: Layer 1, 2, and 3 design examples
- Chapter 16: Software scaling capabilities
- Chapter 17: Supported standards, RFCs, and MIBs
- Glossary
- If you do manually change the system ID, take the necessary steps to ensure no
duplication exists in the network.
• Create two B-VLANs to allow load distribution over both B-VLANs. This configuration is
required if you use SMLT. Even if you do not use SMLT in the network, this is still good
practice as adding a second B-VLAN to an existing configuration allows SPBM to load
balance traffic across two equal cost multipaths if the physical topology grants it.
• In a ring topology with OSPF and IS-IS configured in the core, a core link break causes
slow convergence that can lead to SPBM Layer 2 traffic loss. If the last member link of
an OSPF VLAN fails, it takes down the IP interface and OSPF reconverges. While OSPF
reconverges, SPBM does not have access to the CPU, which causes traffic loss.
SPBM
The following list identifies best practices for SPBM:
• Use a different, easily recognizable IS-IS nickname on each switch.
• If you enable IP shortcuts, you must configure an IS-IS IP source address on the
switch.
Physical or MLT links between IS-IS switches
Virtual Services Platform supports only a single port or single MLT between a pair of IS-IS
switches. For example, if two individual ports exist between a pair of IS-IS switches, you can
configure IS-IS on both the ports but an IS-IS adjacency only forms on one of the links.
If you configure a single MLT between a pair of IS-IS switches, all ports in the MLT are used.
You must configure the MLT before you enable IS-IS on the MLT.
CFM using manual mode configuration
Important:
Avaya recommends auto-configuration of CFM, which is simpler than the manual mode of
configuration.
For more information on these commands, see Avaya Command Line Reference,
NN46251–104.
The following list identifies best practices for manual configuration of Connectivity Fault
Management (CFM):
• The CFM domain name must be the same on all switches in an IS-IS area.
• The maintenance association must be the same on all switches in an IS-IS area.
• To use CFM testing over both B-VLANs, create two maintenance associations — one for
each B-VLAN.
• You can configure the same maintenance domain intermediate points (MIP) on all
switches in an IS-IS area or uniquely defined per switch.
SPBM design guidelines
102 Network Design Reference for Avaya VSP 4000 February 2014
Comments? infodev@avaya.com