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
In Release 3.1, CFM also extends the debugging of Layer 2 networks to Customer VLANs (C-
VLANs).
• For SPBM B-VLANs, you can use either autogenerated or explicitly-configured CFM
MEPs.
• For C-VLANs, you can only use autogenerated CFM MEPs.
Important:
Previous explicit CFM configurations of MDs, MAs, and MEPs on SPBM B-VLANs continue
to function in this release. However, if you want to enable the new autogenerated
commands, you must first remove the existing MEP and MIP on the SPBM B-VLANs. VSP
4000 only supports one type of MEP or MIP for each SPBM B-VLAN.
If you choose to explicitly configure CFM, you must configure an MD, MA, and MEP ID. You
do not have to configure an MD, MA, MIPs and MEPs if you configured autogenerated CFM,
which enables the device to create default MD, MA, MEPs, and MIPs.
For more information on CFM, see Configuring Avaya VENA Fabric Connect on Avaya Virtual
Services Platform 4000, NN46251–510.
IGMP Layer 2 querier
Beginning with Release 3.1, you can use Virtual Services Platform 4000 as a Layer 2 querier
for a Layer 2 multicast network that does not have a multicast router. For more information,
see
IGMP Layer 2 querier on page 113.
IGMP virtualization
From Release 3.1 onward you can configure IGMP with the Virtual Routing and Forwarding
(VRF) Lite feature. For more information, see
Multicast and VRF-lite on page 107.
Layer 2 ping output
Release 3.1 updates the output for the l2 ping ip-address. The l2 ping ip-
address command output now displays path attempted, which refers to the number of
Layer 2 ping attempts.
Layer 2 ping and Layer 2 traceroute
In Release 3.1, you can use the l2 ping and l2 traceroute commands with C-VLANs.
These commands provide a simpler command syntax than the standard Loopback Message
and Linktrace Messages.
Trace commands
Release 3.1 adds new trace commands to provide additional troubleshooting procedures.
The following trace commands provide trace information for SPBM IS-IS:
•
trace spbm isis level <0–4>
•
show trace spbm isis
The following trace commands provide trace information form CFM:
•
trace cfm level <0–4>
•
show trace cfm
New in this release
14 Network Design Reference for Avaya VSP 4000 February 2014
Comments? infodev@avaya.com