Design Reference

ManualsBrandsExtreme Networks ManualsComputers & AccessoriesFabric-enabled multi-service edge switches

Table Of Contents

Contents
Chapter 1: Introduction
- Purpose
- Related resources
- Support
Chapter 2: New in this release
- VOSS 4.2.1
  - Features
  - Other changes
- VOSS 4.2
  - Features
  - Other changes
Chapter 3: Network design fundamentals
Chapter 4: Hardware fundamentals and guidelines
- Supported hardware
- Platform considerations
- Hardware compatibility for VSP 4000
- Supported optical devices
- Dispersion considerations for long reach
- 10/100BASE-X and 1000BASE-TX reach
- 10/100/1000BASE-TX Auto-Negotiation recommendations
- Auto MDIX
- CANA
Chapter 5: Optical routing design
- Optical routing system components
Chapter 6: Platform redundancy
- Power redundancy
- Input/output port redundancy
- Configuration redundancy
- Link redundancy
Chapter 7: Link redundancy
- Physical layer redundancy
- MultiLink Trunking
- 802.3ad-based link aggregation
Chapter 8: Layer 2 loop prevention
- Loop prevention and detection
- SLPP example scenarios
Chapter 9: Layer 2 switch clustering and SMLT
- Split MultiLink Trunk configuration
Chapter 10: Layer 3 switch clustering and RSMLT
- Routed SMLT
- Switch clustering topologies and interoperability with other products
Chapter 11: Layer 3 switch clustering and multicast SMLT
- General guidelines
- Multicast triangle topology
- Square and full-mesh topology multicast guidelines
- SMLT and multicast traffic issues
Chapter 12: Spanning tree
- Spanning tree and protection against isolated VLANs
- MSTP and RSTP considerations
Chapter 13: Layer 3 network design
- VRF Lite
- Virtual Router Redundancy Protocol
- Open Shortest Path First
- Border Gateway Protocol
- IP routed interface scaling
- IPv6
Chapter 14: SPBM design guidelines
- 802.1aq standard
- VLANs without member ports
- Provisioning
- Implementation options
- Reference architectures
- Solution-specific reference architectures
- Best practices
- SPBM restrictions and limitations
- IP multicast over Fabric Connect restrictions
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
- DoS protection mechanisms
- Damage prevention
- Data plane security
- Control plane security
- Additional information
Chapter 17: QoS design guidelines
- QoS mechanisms
- QoS interface considerations
- Network congestion and QoS design
- QoS examples and recommendations
Chapter 18: Layer 1, 2, and 3 design examples
- Layer 1 example
- Layer 2 example
- Layer 3 example
Glossary

SMLT aggregation switches detect that aggregation is disabled on the SMLT client, thus no

automatic link aggregation establishes until the configuration is resolved.

• Single CPU failure

In this case, LACP on other switches detects the remote failure, and all links that connect to the

failed system are removed from the link aggregation group. This process allows failure

recovery to a different network path.

• LACP and VLACP cannot run on the same interfaces simultaneously.

SMLT and LACP System ID

The LACP SMLT System ID used by SMLT core aggregation switches is configurable. Configure the

LACP SMLT system ID to be the base MAC address of one of the aggregate switches and include

the SMLT-ID. Ensure that the same System ID is configured on both of the SMLT core aggregation

switches.

The LACP System ID is the base MAC address of the switch, which is carried in Link Aggregation

Control Protocol Data Units (LACPDU). When two links interconnect two switches running LACP,

each switch is aware both links connect to the same remote device because the LACPDUs originate

from the same System ID. If the links are enabled for aggregation using the same key, LACP can

dynamically aggregate them into a LAG (MLT).

When SMLT is used between the two switches, they act as one logical device. Both aggregation

switches must use the same LACP System ID over the SMLT links. This ensures the edge switch

sees one logical LACP peer, and can aggregate uplinks towards the SMLT aggregation switches.

This process automatically occurs over the vIST connection, where the base MAC address of one of

the SMLT aggregation switches is chosen and used by both SMLT aggregation switches.

If the switch that owns that Base MAC address reboots, the vIST is no longer operational and the

other switch reverts to using its own Base MAC address as the LACP System ID. This action causes

all edge switches that run LACP to think their links are connected to a different switch. The edge

switches stop forwarding traffic on their remaining uplinks until the aggregation can reform.

Aggregation reformation can take several seconds. When the rebooted switch comes back online,

the same actions occur and disrupt traffic twice. The solution to this situation is to statically configure

the same SMLT System ID MAC address on both aggregation switches.

For more information about how to configure the LACP SMLT system ID, see Configuring Link

Aggregation, MLT, and SMLT on Avaya Virtual Services Platform 9000, NN46250-503.