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

Figure 33: SPBM implementation options

The following sections describe the options that are illustrated in the preceding figure.

A—IP shortcut

IP shortcuts forward standard IP packets over IS-IS. This option enables you to forward IP over the

SPBM core, which is a simpler method than traditional IP routing or MPLS. SPBM nodes propagate

Layer 3 reachability as leaf information in the IS-IS link-state packets (LSP) using Extended IP

reachability type-length-value (TLV) 135, which contains routing information such as neighbors and

locally configured subnets. SPBM nodes that receive the reachability information use this

information to populate the routes to the announcing nodes. All TLVs announced in the IS-IS LSPs

are grafted onto the shortest-path tree (SPT) as leaf nodes.

An IP route lookup is only required once where the source BEB uses the routing table to identify the

BEB closest to the destination subnet. All other nodes perform standard Ethernet switching based

on the existing SPT. This scenario allows for end to end IP-over-Ethernet forwarding without the

need for Address Resolution Protocol (ARP), flooding, or reverse learning. Because BCB SPBM

nodes only forward on the MAC addresses that comprise the B-MAC header, and because unknown

TLVs in IS-IS are relayed to the next hop but ignored locally, SPBM BCB nodes do not require

information about IP subnets to forward IP traffic. Only BEBs generate and receive Extended IP

reachability TLV to build the routing table; BCBs just relay the TLV to the next hop based on the

SPT. In fact, the Extended IP reachabilty TLV is ignored on BCBs.

With IP shortcuts there are only two IP routing hops (ingress BEB and egress BEB) as the SPBM

backbone acts as a virtualized switching backplane.

IP shortcuts do not require I-SID configuration. However, you must enable IP on IS-IS, and

configure the IS-IS source address to match a circuitless or loopback IP address.

Implementation options

December 2014 Network Design Reference for Avaya VSP 4000 Series 77

Comments? infodev@avaya.com