Design Reference

• IPv4 multicast routed traffic on the Global Router (IP shortcuts with IP multicast over
SPBM)
• IPv4 multicast routed traffic using a VRF (Layer 3 VSN with IP multicast over SPBM)
Campus architecture
For migration purposes, you can add SPBM to an existing network that has SMLT configured.
In fact, if there are other protocols already running in the network such as Open Shortest Path
First (OSPF), you can leave them in place too. SPBM uses IS-IS, and operates independently
from other protocols. However, Avaya recommends that you eventually eliminate SMLT in the
core and other unnecessary protocols. This reduces the complexity of the network and makes
it much simpler to maintain and troubleshoot.
Whether you configure SMLT in the core or not, the main point to remember is that SPBM
separates services from the infrastructure. For example, in a large campus, a user may need
access to other sites or data centers. SPBM enables you to grant that access by associating
the user to a specific I-SID. This mechanism enables the user to work without getting access
to confidential information of another department.
The following figure depicts a topology where the BEBs in the edge and data center distribution
nodes are configured in SMLT clusters. Prior to implementing SPBM, the core nodes would
also have been configured as SMLT clusters. When migrating SPBM onto this network design,
it is important to note that you can deploy SPBM over the existing SMLT topology without
network interruption. After the SPBM infrastructure is in place, you can create VSN services
over SPBM or migrate them from the previous end-to-end SMLT-based design.
Figure 38: SPBM campus without SMLT
After migrating all services to SPBM, the customer VLANs (C-VLANs) will exist only on the
BEB SMLT clusters at the edge of the SPBM network. The C-VLANs will be assigned to an I-
SPBM design guidelines
86 Network Design Reference for Avaya VSP 4000 February 2014
Comments? [e-mail]