Avaya 8800 Planning And Engineering, Network Design page 168

SPBM design guidelines
Common Procedures and Exclusions on Migration
• Make sure that the SPBM infrastructure is enabled and functional in the network.
• If the VLAN has multicast enabled or has IPv6 routing configured, then it can only be migrated
to an SPBM L2 VSN and routed with an external router.
• Identify the UNI and NNI ports that are currently port members of the VLAN on all the switches
in the network. If STP/MSTP/RSTP is being used on the UNI, and the relevant domain touches
more than one SPBM-enabled switch in the network (without having to go through any NNI
ports), then the VLAN cannot be migrated to SPBM.
Migrating a VLAN to be an L2 VSN (C-VLAN)
The following procedure can be used to provide L2 connectivity for a VLAN across the SPBM core.
• Follow the pre-migration procedures checks described in the preceding section, "Common
Procedures and Exclusions on Migration".
• Identify the UNI and NNI ports that are currently port members of the VLAN on all the switches
in the network.
• On all the switches in the network that are currently connected by the VLAN, remove the NNI
ports from the membership list of the VLAN.
Warning:
This step will cause service interruption.
• Make the VLAN an L2 VSN using the config vlan vlanid i-sid <isidvalue> CLI
command or the vlan i-sid vlanid isidvalue ACLI command. Use the same value of
I-SID on all the switches. This step should restore service.
Migrating to Inter-ISID Routing
Inter-ISID routing provides the ability to route traffic between extended VLANs where the VLANs
have different I-SIDs. All of the traditional IPv4 unicast routing and gateway redundancy protocols
(including OSPF, RIP, VRRP, and RSMLT) are supported on top of any VLAN that is mapped to an
I-SID.
The high level procedure to migrate a configuration to use Inter-ISID routing is described below.
• Follow the pre-migration procedures checks described in the preceding section, "Common
Procedures and Exclusions on Migration".
• For each VLAN in the SPBM core:
- On all the switches where the VLAN is configured, remove all NNI ports
Warning:
This step will cause service interruption.
- On all the switches where the VLAN is configured, map the VLAN to an I-SID. This will
restore L2 connectivity (the l2tracetree command can be used to validate L2 connectivity
within the VLAN at this point). L3 will be restored once the routing protocols configured on
top of the VLAN converge.
- If an IGP (OSPF) is being used on the VLAN, the impact on traffic during the migration can
be reduced by using two VLANs in each routed segment and configuring the interface cost
June 2016 Planning and Engineering — Network Design
Comments on this document? infodev@avaya.com
168