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
Port on A Port on B Remarks Recommendations
Full-duplex Full-duplex Both sides require the
same mode.
Avaya recommends
that you use this
configuration if you
require full-duplex, but
the configuration does
not support Auto-
Negotiation.
Auto-Negotiation cannot detect the identities of neighbors or shut down misconnected ports.
Upper-layer protocols perform these functions.
Auto MDIX
Automatic medium dependent interface crossover (Auto-MDIX) automatically detects the need
for a straight-through or crossover cable connection and configures the connection
appropriately. This removes the need for crossover cables to interconnect switches and
ensures either type of cable can be used. The speed and duplex setting of an interface must
be set to auto for Auto-MDIX to operate correctly.
CANA
Use Custom Auto-Negotiation Advertisement (CANA) to control the speed and duplex settings
that the interface modules advertise during Auto-Negotiation sessions between Ethernet
devices. Modules can only establish links using these advertised settings, rather than at the
highest common supported operating mode and data rate.
Use CANA to provide smooth migration from 10/100 Mb/s to 1000 Mb/s on host and server
connections. Using Auto-Negotiation only, the switch always uses the fastest possible data
rates. In limited-uplink-bandwidth scenarios, CANA provides control over negotiated access
speeds, and improves control over traffic load patterns.
You can use CANA only on 10/100/1000 Mb/s RJ-45 ports. To use CANA, you must enable
Auto-Negotiation.
Important:
If a port belongs to a Multilink Trunking (MLT) group and you configure CANA on the port
(that is, you configure an advertisement other than the default), then you must apply the
same configuration to all other ports of the MLT group (if they support CANA).
Auto MDIX
Network Design Reference for Avaya VSP 4000 February 2014 29