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: Layer 2 switch clustering and SMLT
- Chapter 10: Layer 3 switch clustering and RSMLT
- Chapter 11: Layer 3 switch clustering and multicast SMLT
- Chapter 12: Spanning tree
- Chapter 13: Layer 3 network design
- Chapter 14: SPBM design guidelines
- Chapter 15: 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
- Split-subnet and multicast
- Protocol Independent Multicast-Sparse Mode guidelines
- Protocol Independent Multicast-Source Specific Multicast guidelines
- Multicast for multimedia
- Chapter 16: System and network stability and security
- Chapter 17: QoS design guidelines
- Chapter 18: Layer 1, 2, and 3 design examples
- Glossary
Figure 74: 802.1x and OPS interaction
Virtual Services Platform 4000 includes software support for the Preside (Funk) and Microsoft IAS
RADIUS servers. Additional RADIUS servers that support the EAP standard are also compatible
with Virtual Services Platform 4000. For more information, contact your Avaya representative.
802.1x and the LAN Enforcer or Avaya Health Agent
The Sygate LAN Enforcer or the Avaya Health Agent enables Virtual Services Platform 4000 to use
the 802.1x standard to ensure that a user who connects from inside a corporate network is
legitimate. The LAN Enforcer or Health Agent also checks the endpoint security posture, including
anti-virus, firewall definitions, Windows registry content, and specific file content (plus date and
size). Noncompliant systems that attempt to obtain switch authentication can be placed in a
remediation VLAN, where updates can be pushed to the internal user, and users can subsequently
attempt to join the network again.
VLANs and traffic isolation
You can use Avaya Virtual Services Platform 4000 Series to build secure VLANs. If you configure
port-based VLANs, each VLAN is completely separate from the others. VSP 4000 supports the
IEEE 802.1Q specification for tagging frames and coordinating VLANs across multiple switches.
VSP 4000 analyzes each packet independently of preceding packets. This mode, as opposed to the
cache mode that other vendors use, allows complete traffic isolation.
For more information about VLANs, see Configuring VLANs and Spanning Tree on Avaya Virtual
Services Platform 4000 Series, NN46251-500.
Management of access policies
At Layer 2, VSP 4000 provides the following security mechanisms:
• Access policies
If you enable access policies globally, the system creates a default policy (1) that allows File
Transfer Protocol (FTP), Hypertext Transfer Protocol (HTTP), Telnet, and Secure Shell (SSH).
If you enable access policies globally but disable the default policy, the system denies FTP,
HTTP, rlogin, SSH, Simple Network Management Protocol (SNMP), Telnet, and Trivial FTP
(TFTP).
System and network stability and security
152 Network Design Reference for Avaya VSP 4000 Series June 2015
Comments on this document? infodev@avaya.com










