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
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 RFC 1195. IS-IS protocol
is only to facilitate SPBM.
• The current release uses level 1 IS-IS. The current release does not support level 2 IS-
IS. The ACLI command show isis int-l2-contl-pkts is not supported in the
current release because the IEEE 802.1aq standard currently only defines the use of one
hierarchy, Level 1.
• The IS-IS standard defines wide (32bit ) metrics and narrow (8 bits) metrics. The current
release supports the wide metric.
Pay special attention to the expected scaling of routes in the network when you select
configuration values for the isis l1-hello-interval and isis l1-hello-
multiplier commands on IS-IS interfaces. The default values for these commands work
well for most networks, including those using moderately-scaled routes. In highly-scaled
networks, you may need to configure higher values for these commands.
VLACP
VLACP is generally used when a repeater or switch exists between connected Virtual Services
Platform 4000 switches to detect when a connection is down even when the link LED is lit.
SNMP traps
On each SPBM peer, if you configure the SPBM B-VLANs to use different VLAN IDs, for
example, VLAN 10 and 20 on one switch, and VLAN 30 and 40 on the second, the system
does not generate a trap message to alert of the mismatch because the two switches cannot
receive control packets from one another. Configure the SPBM B-VLANs to use matching
VLAN IDs.
Other
The following identifies other restrictions and limitations:
• The current release does not support I-SID filters.
SPBM design guidelines
104 Network Design Reference for Avaya VSP 4000 February 2014
Comments? infodev@avaya.com