Spbm Best Practices - Avaya 8800 Planning And Engineering, Network Design

Table 28: Greenfield MSTP/SPBM ring scaling capability
Service
Multicast groups on non-SPBM
VLANs when SPBM is enabled
on the switch
ARP entries with SPBM enabled
on the switch
VLAN entries with SPBM enabled
on the switch
VRF instances
GRT routes
VRF routes total
L2 VPNs
Number of MACs on VPNs
Related links
SPBM design guidelines

SPBM best practices

This section describes best practices when setting up SPBM networks.
IS-IS
• Avaya recommends that you change the IS-IS system ID from the default B-MAC value to a
recognizable address to easily identify a switch. This helps to recognize source and destination
addresses for troubleshooting purposes.
- If you leave the system ID as the default value (safe practice as it ensures no duplication in
the network), it can be difficult to recognize the source and destination B-MAC for
troubleshooting purposes.
- If you do manually change the system ID, take the necessary steps to ensure there is no
duplication in the network.
• Create two B-VLANs to allow load distribution over both B-VLANs. This is required when using
SMLT. Even if SMLT is not used 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.
SPBM
• Use a different, easily recognizable IS-IS nickname on each switch.
• If IP Shortcuts is enabled, you must configure an IS-IS IP source address on the switch.
June 2016
Maximum number tested in this
scenario
100
2000
20
10
500
500
1000
10 000
on page 138
Planning and Engineering — Network Design
Comments on this document? infodev@avaya.com
SPBM best practices
Maximum number supported in
all test scenarios
1500
6000
100
256 (including GRT)
8000
8000
1000
30 000
165