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 Release 4.0.50
- Features
- Other changes
Chapter 3: New in Release 4.0.40
- Features
- Other changes
Chapter 4: New in Release 4.0
- Features
- Other changes
Chapter 5: Network design fundamentals
Chapter 6: Hardware fundamentals and guidelines
- Supported hardware
- Platform considerations
- Hardware compatibility
- 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 7: Optical routing design
- Optical routing system components
Chapter 8: Platform redundancy
- Power redundancy
- Input/output port redundancy
- Configuration redundancy
- Link redundancy
Chapter 9: Link redundancy
- Physical layer redundancy
- MultiLink Trunking
- 802.3ad-based link aggregation
Chapter 10: Layer 2 loop prevention
- Loop prevention and detection
- SLPP example scenarios
Chapter 11: Spanning tree
- Spanning tree and protection against isolated VLANs
- MSTP and RSTP considerations
Chapter 12: Layer 3 network design
- VRF Lite
- Virtual Router Redundancy Protocol
- Open Shortest Path First
- Border Gateway Protocol
- IP routed interface scaling
Chapter 13: 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 SPBM restrictions
Chapter 14: 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 15: System and network stability and security
- DoS protection mechanisms
- Damage prevention
- Data plane security
- Control plane security
- Additional information
Chapter 16: QoS design guidelines
- QoS mechanisms
- QoS interface considerations
- Network congestion and QoS design
- QoS examples and recommendations
Chapter 17: Layer 1, 2, and 3 design examples
- Layer 1 example
- Layer 2 example
- Layer 3 example
Chapter 18: Software scaling capabilities
Chapter 19: Supported standards, RFCs, and MIBs
- Supported IEEE standards
- Supported RFCs
- Quality of service
- Network management
- MIBs
- Standard MIBs
- Proprietary MIBs
Glossary

ERS 8800 implementation

If a VLAN has an IP address and is attached to an I-SID, the ERS 8800 designates that VLAN as

operationally up whether it has a member port or not. When the VLAN is operationally up, the IP

address of the VLAN will be in the routing table.

The ERS 8800 design behaves this way because the VLAN might be acting as an NNI in cases of

Layer 2 Inter-VSN routing. If the VLAN was acting as a UNI interface, it would require a member

port.

VSP 9000 and VSP 4000 implementation

If a VLAN is attached to an I-SID there must be another instance of that same I-SID in the SPBM

network.

• If there is another instance of that I-SID, the device designates that VLAN as operationally up

regardless of whether it has a member port or not.

When the VLAN is operationally up, the IP address of the VLAN will be in the routing table.

• If there is NO matching instance of the I-SID in the SPBM network, then that VLAN does not

have any reachable members so it is not acting as an NNI interface.

The VLAN is also not acting as a UNI interface because it does not have a member port.

Therefore, the device does not designate the VLAN as operationally up because the VLAN is

not acting as a UNI or an NNI interface.

If the device is just acting as a BCB with two VLANs configured and two I-SIDs, there must be a UNI

side with the corresponding I-SID existing in the network.

If the device is acting as both BEB and BCB, then there must be a member port in that VLAN in

order to push out the UNI traffic.