Page 1 Avaya Ethernet Routing Switch 8800/8600 Planning and Engineering — Network Design Release 7.2.10 NN46205-200 Issue 07.05 June 2016...
Page 2 RESERVES THE RIGHT TO TAKE LEGAL ACTION AGAINST YOU the express behalf of Avaya. End User agrees to indemnify and hold AND ANYONE ELSE USING OR SELLING THE SOFTWARE harmless Avaya, Avaya's agents, servants and employees against all WITHOUT A LICENSE.
Page 3 LICENSED TO PROVIDE AVC VIDEO. NO LICENSE IS GRANTED written consent of Avaya can be a criminal, as well as a civil offense OR SHALL BE IMPLIED FOR ANY OTHER USE. ADDITIONAL under the applicable law.
Page 4: Table Of Contents
.................. 20 Power supply circuit requirements ....................... 21 Chassis cooling .......................... 22 Modules ...................... 22 SF/CPU modules .................... 23 8800 series I/O modules ........................ 24 RS modules ........................ 26 R modules ....................... 29 Features and scaling ....................... 32 Optical device guidelines .................... 32...
Page 5 SLPP, Loop Detect, and Extended CP-Limit ................ 102 Simple Loop Prevention Protocol (SLPP) ...................... 106 Extended CP-Limit ........................ 107 Loop Detect ......................... 107 VLACP ................. 107 Loop prevention recommendations June 2016 Planning and Engineering — Network Design Comments on this document? infodev@avaya.com...
Page 6 ...................... 142 SPBM provisioning .................... 143 SPBM implementation options .................... 148 SPBM reference architectures .................... 150 SPBM campus architecture ................... 153 SPBM multicast architecture .................. 153 Large data center architecture June 2016 Planning and Engineering — Network Design Comments on this document? infodev@avaya.com...
Page 7 PIM-SM receivers and VLANs ................ 212 PIM network with non-PIM interfaces ........ 213 Protocol Independent Multicast-Source Specific Multicast guidelines .................. 213 IGMPv3 and PIM-SSM operation ................ 213 RP Set configuration considerations June 2016 Planning and Engineering — Network Design Comments on this document? infodev@avaya.com...
Page 8 IP VPN Lite .................. 247 IP VPN Lite deployment scenarios ........................ 248 SMLT design ...................... 249 Layer 2 VPN design .................... 250 Inter-site IGP routing design ...................... 250 Layer 3 VPN design June 2016 Planning and Engineering — Network Design Comments on this document? infodev@avaya.com...
Page 9 Encryption of control plane traffic .................. 286 SNMP header network address ...................... 286 SNMPv3 support .................... 286 Other security equipment ...................... 288 For more information Chapter 16: QoS design guidelines.................. 289 June 2016 Planning and Engineering — Network Design Comments on this document? infodev@avaya.com...
Page 10 IPv4 Layer 3/Layer 4 Intelligence ....................... 312 IPv4 Multicast .......................... 312 IPv6 ........................ 313 Platform .................... 313 Quality of Service (QoS) .................... 314 Network Management .................. 315 Supported network management MIBs June 2016 Planning and Engineering — Network Design Comments on this document? infodev@avaya.com...
Page 11: Chapter 1: Safety Messages
Chapter 1: Safety messages This section describes the different precautionary notices used in this document. This section also contains precautionary notices that you must read for safe operation of the Avaya Ethernet Routing Switch 8800/8600. Notices Notice paragraphs alert you about issues that require your attention. The following sections describe the types of notices.
Page 12: Caution Notice
Electrostatic alert: PRECAUCIÓN ESD (Descarga electrostática) El aviso de ESD brinda información acerca de cómo evitar una descarga de electricidad estática y el daño posterior a los productos Avaya. Electrostatic alert: CUIDADO ESD Os avisos do ESD oferecem informações sobre como evitar descarga de eletricidade estática e os conseqüentes danos aos produtos da Avaya.
Page 13 Notices Caution: CUIDADO Os avisos de cuidado oferecem informações sobre como evitar possíveis interrupções do serviço ou danos aos produtos da Avaya. Caution: ATTENZIONE Le indicazioni di attenzione forniscono informazioni per evitare possibili interruzioni del servizio o danni ai prodotti Avaya.
Page 14: Chapter 2: Introduction
Avaya Mentor videos provide technical content on how to install, configure, and troubleshoot Avaya products. About this task Videos are available on the Avaya Support website, listed under the video document type, and on the Avaya-run channel on YouTube. June 2016 Planning and Engineering —...
Page 15: Support
- In Search, type Avaya Mentor Videos to see a list of the available videos. - In Search, type the product name. On the Search Results page, select Video in the Content Type column on the left.
Page 16: Chapter 3: New In This Release
• Control operations such as managing APs are still performed by the WLAN 8100 Controller, which is referred to as the Wireless Control Point (WCP) • Data forwarding functions are now implemented in the ERS 8800/8600, which is referred to as the Wireless Switching Point (WSP).
Page 17: Other Changes
Other changes the ERS 8800/8600 builds on the simplicity introduced with Avaya VENA using SPBM for the control plane with support for Bridged and Routed IP Multicast traffic without the inefficiencies or complexities that exist today. This new functionality now extends the SPBM IS-IS control plane to additionally exchange IP...
Page 18: Chapter 4: Network Design Fundamentals
Chapter 4: Network design fundamentals To efficiently and cost-effectively use your Avaya 8000 Series routing switch, you must properly design your network. Use the information in this section to help you properly design your network. When you design networks, you must consider the following: •...
Page 19 Based on this model, one goal of network design is to off-load the interacting software level as much as possible to the other levels, especially to the hardware level. Therefore, Avaya recommends that you follow these generic rules when you design networks: •...
Page 20: Chapter 5: Hardware Fundamentals And Guidelines
Supply Calculator for Avaya ERS 8800/8600, NN48500-519. This is available at www.avaya.com/ support with the rest of the ERS 8800/8600 documentation.To support a full configuration of RS modules, you require an 8004 or 8005 power supply. Do not mix 8004 and 8005 power supplies in the same chassis.
Page 21: Chassis Cooling
Chassis cooling You can use two basic methods to determine the cooling capacity required to cool the switch. You can use the Avaya Power Supply Calculator Tool to determine power draw in watts, or you can use a worse-case power draw.
Page 22: Modules
You must also consider the type of module installed on the chassis. If you install an RS or 8800 module in the chassis, you must install the high speed cooling modules. If you do not install the high speed cooling modules, the software cannot operate on the module.
Page 23: 8800 Series I/O Modules
Ensure that you are running software release 7.1 or later for the 8800 modules to operate properly. R and RS modules continue to be supported and you can install a mix of R/RS and 8800 modules in the same chassis.
Page 24: Rs Modules
For module specifications and installation procedures, see Avaya Ethernet Routing Switch 8800/8600 Installation — Modules, (NN46205–304). For optical transceiver specifications and installation procedures, see Avaya Ethernet Routing Switch 8800/8600 Installation — SFP, SFP+, XFP, and OADM Hardware Components, (NN46205– 320). 8812XL information and recommendations The 8812XL SFP+ I/O module supports 12 SFP+ ports at 10Gbps.
Page 25 QoS capabilities—RS modules do so. Table 1: RS module lane oversubscription Module Lane oversubscription 8612XLRS 4:1 (each group of ports [1–4, 5–8, and 9–12] share a 10GE lane) Table continues… June 2016 Planning and Engineering — Network Design Comments on this document? infodev@avaya.com...
Page 26: R Modules
R modules provide support for a variety of technologies, interfaces, and feature sets and provide 1 and 10 Gbit/s port rates. The Avaya Ethernet Routing Switch 8800/8600 supports the following R modules, which require the use of the 8895 SF/CPU or 8692 SF/CPU with SuperMezz: •...
Page 27 8634XGRS 16 Gbit/s 60 Gbit/s For maximum switch performance, Avaya recommends that you place R modules in chassis slots 2 to 4 or 7 to 9, as available. A chassis revision with an upgraded High-performance Backplane (HPB) compatible with R modules and supporting high-performance in all slots is available.
Page 28 • 10GBASE-ER/EW • 10GBASE-ZR/ZW • 10GBASE DWDM For more information about XFP specifications, see Avaya Ethernet Routing Switch 8800/8600 Installation — SFP, SFP+, XFP, and OADM Hardware Components (NN46205-320). 10 GbE clocking Whether you use internal or line clocking depends on the application and configuration. Typically, the default internal clocking is sufficient.
Page 29: Features And Scaling
Features and scaling The following tables show scaling information and features available on the Avaya Ethernet Routing Switch 8800/8600. For the most recent scaling information, always consult the latest version of the Release Notes. Table 5: Supported scaling capabilities...
Page 30 OSPF LSA packet maximum size 3000 bytes RIP instances RIP interfaces RIP routes 2500 in a VRF 10 000 in the system Multiprotocol Label Switching MPLS LDP sessions Table continues… June 2016 Planning and Engineering — Network Design Comments on this document? infodev@avaya.com...
Page 31 RMON Ethernet statistics with 4000K memory 4590 Avaya supports only 25 spanning tree groups (STG). Although you can configure up to 64 STGs, configurations of more than 25 STGs are not supported. If you need to configure more than 25 STGs, contact your Avaya Customer Support representative for more information.
Page 32: Optical Device Guidelines
Haul 1600G, have transmitters that allow you to change the transmitter power level. By default, they are typically set to –10 dBm, thus requiring no additional receiver attenuation for the 10GE WAN module. For specifications for the 10 GbE modules, see Avaya Ethernet Routing Switch 8800/8600 Installation — Ethernet Modules, NN46205-304.
Page 33 Optical device guidelines For more information about these devices, including compatible fiber type, see Avaya Ethernet Routing Switch 8800/8600 Installation — SFP, SFP+, XFP, and OADM Hardware Components (NN46205-320). Table 6: Optical devices and maximum reach Optical device (SFP/SFP+/ Maximum reach...
Page 34: Xfps And Dispersion Considerations
57 km. To show how link length, dispersion, and spectral width are related, see the following tables. Table 7: Spectral width and link lengths assuming the maximum of 3.5 ps/(nm-km) Spectral width (nm) Maximum link length (km) 28.5 June 2016 Planning and Engineering — Network Design Comments on this document? infodev@avaya.com...
Page 35: 10/100Base-X And 1000Base-Tx Reach
If no PMD compensating devices are available and the proposed fiber is over the PMD limit, use a different optical fiber. 10/100BASE-X and 1000BASE-TX reach The following tables list maximum transmission distances for 10/100BASE-X and 1000BASE-TX Ethernet cables. June 2016 Planning and Engineering — Network Design Comments on this document? infodev@avaya.com...
Page 36: 10/100Base-Tx Autonegotiation Recommendations
10BASE-T, 100BASE-TX, and 100BASE-T4 compatible devices to be recognized, even if they do not support autonegotiation. In this case, only the link speed is sensed; not the duplex mode. Avaya recommends the autonegotiation settings as shown in the following table, where A and B are two Ethernet devices.
Page 37: Cana
The CP-Limit default settings are as follows: • default state is enabled on all ports • when creating the IST, CP-Limit is disabled automatically on the IST ports June 2016 Planning and Engineering — Network Design Comments on this document? infodev@avaya.com...
Page 38: Extended Cp-Limit
SMLT configurations. Avaya recommends that an IST MLT contain at least two physical ports, although this is not a requirement. Avaya also recommends that you disable CP-Limit on all physical ports that are members of an IST MLT. This is the default configuration. Disabling CP-Limit on IST MLT ports forces another, less critical port to be disabled if the defined CP-Limits are exceeded.
Page 39 PortCongTime—this parameter is only used by SoftDown. The following figures detail the flow logic of the HardDown and SoftDown operation of Extended CP- Limit. Figure 4: Extended CP-Limit HardDown operation June 2016 Planning and Engineering — Network Design Comments on this document? infodev@avaya.com...
Page 40 For information about using CP-Limit and Extended CP-Limit with SLPP and VLACP, see SLPP, Loop Detect, and Extended CP-Limit on page 102. For more information about CP-Limit and Extended CP-Limit, see Avaya Ethernet Routing Switch 8800/8600 Administration, NN46205-605. June 2016 Planning and Engineering — Network Design...
Page 41: Chapter 6: Optical Routing Design
Chapter 6: Optical routing design Use the Avaya optical routing system to maximize bandwidth on a single optical fiber. This section provides optical routing system information that you can use to help design your network. Optical routing system components The Avaya optical routing system uses coarse wavelength division multiplexing (CWDM) in a grid of eight optical wavelengths.
Page 42 Optical routing design Figure 6: Wavelength division multiplexing The Avaya optical routing system supports both ring and point-to-point configurations. The optical routing system includes the following parts: • CWDM SFPs • CWDM SFP+s • Optical add/drop multiplexers (OADM) • Optical multiplexer/demultiplexers (OMUX) •...
Page 43 AA1419059-E6, up to 40 km DDI AA1419067-E6, up to 70 km DDI 1610 nm AA1419032-E5, up to 40 km SFP AA1402011-E5 AA1402009-E5 Brown AA1419040-E5, up to 70 km SFP Table continues… June 2016 Planning and Engineering — Network Design Comments on this document? infodev@avaya.com...
Page 44: Multiplexer Applications
AA1419060-E6, up to 40 km DDI AA1419068-E6, up to 70 km DDI For more information about multiplexers, SFPs and SFP+s, including technical specifications and installation instructions, see Avaya Ethernet Routing Switch 8800/8600 Installation — SFP, SFP+, XFP, and OADM Hardware Components, NN46205-320. Multiplexer applications Use OADMs to add and drop wavelengths to and from an optical fiber.
Page 45: Optical Multiplexer In A Point-To-Point Application
(SFPs/SFP+s). Typically, two OMUXs are installed in a chassis. The OMUX on the left is called the east path, and the OMUX on the right is called the west path. June 2016 Planning and Engineering — Network Design Comments on this document? infodev@avaya.com...
Page 46: Omux In A Ring
Transmission distance To ensure proper network operation, given your link characteristics, calculate the maximum transmission distance for your fiber link. June 2016 Planning and Engineering — Network Design Comments on this document? infodev@avaya.com...
Page 47: Reach And Optical Link Budget
The examples assume the use of the values and information listed in the following table. Use the expected repair margin specified by your organization. For SFP, SFP+, XFP, and multiplexer specifications, see Avaya Ethernet Routing Switch 8800/8600 Installation — SFP, SFP+, XFP, and OADM Hardware Components (NN46205-320). Multiplexer loss values include connector loss.
Page 48 The following factors affect signal strength and determine the point-to-point link budget and the maximum transmission distance for the network shown in the following figure. • OMUX multiplexer (mux) loss • OMUX demultiplexer (demux) loss • Fiber attenuation June 2016 Planning and Engineering — Network Design Comments on this document? infodev@avaya.com...
Page 49 The transmission distance calculation for the mesh ring configuration shown in the following figure is similar to that of the point-to-point configuration, with some additional loss generated in the passthrough of intermediate OADM nodes. June 2016 Planning and Engineering — Network Design Comments on this document? infodev@avaya.com...
Page 50 The number of OADMs that can be supported is based on loss budget calculations. The following table shows the typical loss values used to calculate the transmission distance for the mesh ring network example. June 2016 Planning and Engineering — Network Design Comments on this document? infodev@avaya.com...
Page 51 • OADM insertion loss for Add port • OADM insertion loss for Drop port • OADM insertion loss for Through port for intermediate nodes • Fiber attenuation of 0.25 dB/km June 2016 Planning and Engineering — Network Design Comments on this document? infodev@avaya.com...
Page 52 OMUX-8 demux loss 4.5 dB System margin 3.0 dB Fiber attenuation 0.25 dB/km The equations and calculations used to determine maximum transmission distance for the network example are: June 2016 Planning and Engineering — Network Design Comments on this document? infodev@avaya.com...
Page 53 Passthrough nodes = 7 nodes Passive loss = 1.9 + 4.5 + (67*2.0)= 20.4 dB Implied fiber loss = 30 – 20.4 – 3 = 6.6 dB Maximum reach = (6.6 dB) / (0.25 dB/km) = 26.4 km June 2016 Planning and Engineering — Network Design Comments on this document? infodev@avaya.com...
Page 54: Chapter 7: Software Considerations
Operational modes With Release 7.0 and later, the Avaya Ethernet Routing Switch 8800/8600 operates in R mode only. You cannot configure the switch to run in M mode. Similarly, enhanced operational mode configuration is not applicable as the system always operates in enhanced mode.
Page 55: Chapter 8: Redundant Network Design
57 100BASE-FX FEFI recommendations The Avaya Ethernet Routing Switch 8800/8600 supports Far End Fault Indication (FEFI). FEFI ensures that link failures are reported to the switch. FEFI is enabled when the autonegotiation function is enabled. However, not all 100BASE-FX drivers support FEFI. Without FEFI support, if...
Page 56: Gigabit Ethernet And Remote Fault Indication
Redundant network design Figure 12: 100BASE-FX FEFI With Avaya-to-Avaya connections, to avoid loss of connectivity for devices that do not support FEFI, you can use VLACP as an alternative failure detection method. For more information, see End-to- end fault detection and VLACP on page 57.
Page 57: End-To-End Fault Detection And Vlacp
A major limitation of the RFI and FEFI functions is that they terminate at the next Ethernet hop. Therefore, failures cannot be determined on an end-to-end basis over multiple hops. To mitigate this limitation, Avaya has developed a feature called Virtual LACP (VLACP), which provides an end-to-end failure detection mechanism. With VLACP, far-end failures can be detected.
Page 58 By using VLACP over SLT, enhanced failure detection is extended beyond the limits of the number of SMLT or LACP instances that can be created on an Avaya switch. VLACP trap messages are sent to the management stations if the VLACP state changes. If the failure is local, the only traps that are generated are port linkdown or port linkup.
Page 59 This functionality is only supported between two Ethernet Routing Switch 8800/8600 switches, generally across the core of a square of a full-mesh multiple cluster design. As an environment is scaled, sub-100 millisecond failover may not be stable. Therefore, if you enable this feature, minimize the number of links running sub-100 millisecond operation.
Page 60 Availability (HA) mode, and may not be stable in scaled networks. • For interswitch trunk (IST) links, Avaya recommends using a time-out scale of 5, long timers, and slow-periodic-time of 10000. For IST MLTs, Avaya recommends that you do not set the VLACP long periodic timer to less than 30 seconds.
Page 61: Platform Redundancy
• Switch fabric redundancy Avaya recommends that you use two SF/CPUs to protect against switch fabric failures. The two SF/CPUs load share and provide backup for each other. Using the 8006 or 8010 chassis, full switching capacity is available with both SF/CPU modules.
Page 62: High Availability Mode
International Association (PCMCIA) storage. If you enable the system flag called save to standby, it ensures that configuration changes are always saved to both CPUs. When you use SMLT, Avaya recommends that you use VLACP to avoid packet forwarding to a failed switch that cannot process them.
Page 63 Table 19: Synchronization capabilities in HA mode Synchronization of: Release 7.0 Layer 1 Port configuration parameters Layer 2 VLAN parameters STP parameters RSTP/MSTP parameters SMLT parameters QoS parameters Layer 3 Table continues… June 2016 Planning and Engineering — Network Design Comments on this document? infodev@avaya.com...
Page 64 CPUs, or the synchronization may take a long time. Error messages can appear on the console. In HA mode, Avaya recommends that you do not configure the OSPF hello timers for less than one second, and the dead router interval for less for than 15 seconds.
Page 65: Link Redundancy
66 • Switch-to-switch MLT link recommendations on page 66 • Brouter ports and MLT on page 66 • MLT and spanning tree protocols on page 67 June 2016 Planning and Engineering — Network Design Comments on this document? infodev@avaya.com...
Page 66 • Connect port 3/1 on switch A to port 8/1 on switch B. Brouter ports and MLT In the Avaya Ethernet Routing Switch 8800/8600, brouter ports do not support MLT. Thus, you cannot use brouter ports to connect two switches with a MLT. An alternative is to use a VLAN. This configuration option provides a routed VLAN with a single logical port (MLT).
Page 67 Mbit/s link is 1. Because the root selection algorithm chooses the link with the lowest port ID as its root port (ignoring the aggregate rate of the links), Avaya recommends that the following methods be used when you define path costs: •...
Page 68: Ad-Based Link Aggregation
LACP and SMLT: Interoperability with servers (and potentially third-party switches) To better serve interoperability with servers (and potentially certain third-party switches) in SMLT designs, the Avaya Ethernet Routing Switch 8800/8600 provides a system ID configuration option for Split MultiLink Trunk (SMLT). June 2016 Planning and Engineering —...
Page 69 The actor system priority of LACP_DEFAULT_SYS_PRIO, the actor system ID configured by the user, and an actor key equal to the SMLT-ID or SLT-ID are sent to the wiring closet switch. Avaya recommends that you configure the system ID to be the base MAC address of one of the aggregate switches along with its SMLT-ID.
Page 70: Bidirectional Forwarding Detection
If the number of active links in the LAG becomes less than the MinLink setting, the Avaya Ethernet Routing Switch 8800/8600 marks the LAG as down, and informs the remote end of the LAG state by using a Link Aggregation Protocol Data Unit (LACPDU). The switch continues to send LACPDUs to neighbors on each available link based on the configured timers.
Page 71 Operation The Avaya Ethernet Routing Switch 8800/8600 uses one BFD session for all protocols with the same destination. For example, if a network runs OSPF and BGP across the same link with the same peer, only one BFD session is established, and BFD shares session information with both routing protocols.
Page 72: Multihoming
Multihomed hosts can be connected to port-based, policy-based, and IP subnet-based VLANs. The IP addresses that you associate with a single MAC address on a host must be located in the same IP subnet. The Ethernet Routing Switch 8800/8600 supports multihomed hosts with up to 16 IP addresses per MAC address.
Page 73 Important: Avaya recommends that you do not directly connect servers and clients in core switches. If one IST switch fails, connectivity to the server is lost. Data center architecture The tiered network architecture also applies to a data center architecture.
Page 74 Figure 17: Two-tiered architecture with four-switch core plus data center Thefollowing figure shows a two-tiered architecture with a two-switchcore. June 2016 Planning and Engineering — Network Design Comments on this document? infodev@avaya.com...
Page 75: Network Edge Redundancy
If one edge layer switch fails, the other can maintain user services. Figure 19: Redundant network edge diagram Avaya recommends the network edge design shown in Figure 20: Recommended network edge design on page 76. This setup is simple to implement and maintain, yet still provides redundancy if one of the edge or distribution layer switches fails.
Page 76: Split Multi-Link Trunking
This permits the scaling of the number of split multilink trunks on a switch to the maximum number of available ports. For configuration procedures for the Avaya Split Multi-Link Trunking feature for the Ethernet Routing Switch 8800/8600, see Switch Clustering using Split-Multilink Trunking (SMLT) Technical Configuration Guide, NN48500-518 or Switch Clustering (SMLT/SLT) Configuration Tool , NN48500-536.
Page 77 Source/Destination address (SA/DA) pair (regardless of whether or not the DA is known by B or C). Packet over SONET (POS), and Ethernet interfaces are supported as operational SMLT links. June 2016 Planning and Engineering — Network Design Comments on this document? infodev@avaya.com...
Page 78 SMLT failures occur, the interswitch trunk traffic volume may be significant. To ensure that no single point of failure exists in the interswitch trunk, Avaya recommends that the interswitch trunk be a multigigabit multilink trunk with connections across different modules on both aggregation switches.
Page 79 Network redundancy Avaya also recommends that you use low slot number ports for the IST, for example ports 1/1 and 2/1, because the low number slots boot up first. Avaya recommends that you use an independent Virtual Local Area Network (VLAN) for the IST peer session.
Page 80 On the edge switch, SMLT achieves load sharing by using the MLT path selection algorithm (for a description of the algorithm, see Avaya Ethernet Routing Switch 8800/8600 Configuration — Link Aggregation, MLT, and SMLT, NN46205-518. Usually, the algorithm operates on a source/ destination MAC address basis or a source/destination IP address basis.
Page 81 (the critical IP) fail. Avaya recommends that you do not configure VRRP critical IPs within SMLT or R-SMLT environments because SMLT operation automatically provides the same level of redundancy.
Page 82 SMLT and IEEE 802.3ad interaction The Avaya Ethernet Routing Switch 8800/8600 switch fully supports the IEEE 802.3adLink Aggregation Control Protocol (LACP) on MLT and distributed MLTlinks, and on a pair of SMLT switches.
Page 83 Prior to Release 4.1.1, if the SMLT core aggregation switches did not know and were unable to negotiate the LACP system ID, data could be lost. Avaya recommends that you configure the LACP SMLT system ID to be the base MAC address of one of the aggregate switches, and that you include the SMLT-ID.
Page 84: Smlt Topologies
For more information about SMLT scalability and multicast routing, see Multicast network design page 172. For more information about VLAN scalability, see Avaya Ethernet Routing Switch 8800/8600 Configuration — VLANs and Spanning Tree, NN46205-517. SMLT topologies Several common network topologies are used in SMLT networks. These include the SMLT triangle, the SMLT square, and the SMLT full-mesh.
Page 85 You can scale SMLT groups to achieve hierarchical network designs by connecting SMLT groups together. This allows redundant loop-free Layer 2 domains that fully use all network links without using an additional protocol. June 2016 Planning and Engineering — Network Design Comments on this document? infodev@avaya.com...
Page 86: Smlt Full-Mesh Recommendations With Ospf
In a full-mesh SMLT configuration between two clusters running OSPF (typically an RSMLT configuration), Avaya recommends that you place the MLT ports that form the square leg of the mesh (rather than the cross connect) on lower numbered slots/ports. This configuration is recommended because CP-generated traffic is always sent out on the lower numbered MLT ports when active.
Page 87 To minimize the creation of many IP subnets, one VLAN (VLAN 1, IP subnet A) spans all wiring closets. SMLT provides loop prevention and enables all links to forward to VLAN 1, IP Subnet A. June 2016 Planning and Engineering — Network Design Comments on this document? infodev@avaya.com...
Page 88 RSMLT. Routers R1 and R2 forward traffic for IP subnet A. RSMLT provides both router failover and link failover. For example, if the SMLT link in between R2 and R4 are broken, the traffic fails over to R1. June 2016 Planning and Engineering — Network Design Comments on this document? infodev@avaya.com...
Page 89 (that is, the pair always routes for each other). Avaya recommends that you set the hold up and hold down timer to 1.5 times the convergence time of the network.
Page 90 If you use a Layer 3 SMLT client switch without a routing protocol, configure two static routes to point to both RSMLT switches or configure one static route. Set the RSMLT hold-up timer to 9999 (infinity). Avaya also recommends that you set the RSMLT hold-up timer to 9999 (infinity) for RSMLT Edge (Layer 2 RSMLT).
Page 91 While Avaya’s Routed Split MultiLink Trunk (RSMLT) functionality originally provided sub-second failover for IPv4 forwarding only, the Avaya Ethernet Routing Switch 8800/8600 extends RSMLT functionality to IPv6. The overall model for IPv6 RSMLT is essentially identical to that of IPv4 RSMLT.
Page 92 • IPv6 Static Routes • OSPFv3 IPv4 IST with IPv6 RSMLT The Avaya Ethernet Routing Switch 8800/8600 does not support the configuration of an IST over IPv6. IST is supported over IPv4 only. Example network The following figure shows a sample IPv6 RSMLT topology. It shows a typical redundant network example with user aggregation, core, and server access layers.
Page 93 R1. At startup, R1 and R2 use the IST link to exchange full configuration information including MAC address for the IPv6 interfaces residing on SMLT VLAN 3. June 2016 Planning and Engineering — Network Design Comments on this document? infodev@avaya.com...
Page 94 For a given SMLT VLAN RSMLT is supported for any of the following scenarios: • IPv4 Only: IPv4 is configured on the VLAN and IPv6 is not. RSMLT operation and logic remains unchanged from the current implementation. June 2016 Planning and Engineering — Network Design Comments on this document? infodev@avaya.com...
Page 95: Switch Clustering Topologies And Interoperability With Other Products
Switch clustering topologies and interoperability with other products When the Avaya Ethernet Routing Switch 8800/8600 is used with other Avaya Ethernet Routing Switch products, the switch clustering bridging, unicast routing, and multicast routing configurations vary with switch type. Avaya recommends that you use the supported topologies and features when you perform inter-product switch clustering.
Page 96: Chapter 9: Layer 2 Loop Prevention
Spanning tree Spanning Tree prevents loops in switched networks. The Avaya Ethernet Routing Switch 8800/8600 supports several spanning tree protocols and implementations. These include the Spanning Tree Protocol (STP), Per-VLAN Spanning Tree Plus (PVST+), Rapid Spanning Tree Protocol (RSTP), and Multiple Spanning Tree Protocol (MSTP).
Page 97 Avaya provides multiple spanning tree group (STG) interoperability with single STG devices. When you connect the Avaya Ethernet Routing Switch 8800/8600 with Layer 2 switches, be aware of the differences in STG support between the two types of devices. Some switches support only one STG, whereas the Avaya Ethernet Routing Switch 8800/8600 supports 25 STGs.
Page 98 Switch 8100. To create this configuration, you must configure STGs on the two Ethernet Routing Switch 8800/8600s, assign specific MAC addresses to the BPDUs created by the two new STGs, create VLANs 4002 and 4003 on the Layer 2 device, and create two new VLANs (VLAN 2 and VLAN 3) on all three devices.
Page 99 In the ACLI, the command is spanning-tree stp <1-64> create. On the Ethernet Routing Switch 8800/8600s (A8600 and B8600), configure A8600 as the root of STG2 and B8600 as the root of STG3. On the Ethernet Switch 8100 (Layer 2), configure A8600 as the root of STG1.
Page 100: Per-Vlan Spanning Tree Plus
Configure the four VLANs on the Layer 2 switch to include the tagged ports connected to the Ethernet Routing Switch 8800/8600. To ensure that the BPDUs from STG2 and STG3 are seen by the Layer 2 switch as traffic for the two VLANs, and not as BPDUs, give two of the VLANs the IDs 4002 and 4003.
Page 101: Mstp And Rstp Considerations
Use to configure multiple instances of RSTP on the same switch. Each RSTP instance can include one or more VLANs. The operation of the MSTP is similar to the current Avaya proprietary MSTP, except that the Avaya version has faster recovery time.
Page 102: Slpp, Loop Detect, And Extended Cp-Limit
The CP-Limit functionality only protects the switch from broadcast and control traffic with a QoS value of 7. Do not use only the CP-Limit for loop prevention. Avaya recommends the following loop prevention and recovery features in order of preference: •...
Page 103 • In case of a network failure, to avoid edge isolation, the SLPP rx-threshold is set to 50 on SMLT switch B. This configuration detects loops and avoids edge isolation. For tagged data, consider the following configuration: June 2016 Planning and Engineering — Network Design Comments on this document? infodev@avaya.com...
Page 104 • On SMLT switch B, the SLPP Rx threshold is set to 50 to avoid edge isolation in case of a network failure. In this scenario, Avaya recommends that you enable the untagged-frames-discard parameter on the SMLT uplink ports. SLPP configuration considerations and recommendations SLPP uses a per-VLAN hello packet mechanism to detect network loops.
Page 105 • Enable SLPP-Rx only on SMLT edge ports, and never on core ports. Do not enable SLPP-Rx on SMLT IST ports or SMLT square or full-mesh core ports. • In an SMLT Cluster, Avaya recommends an SLPP Packet-RX Threshold of 5 on the primary switch and 50 on the secondary switch.
Page 106: Extended Cp-Limit
Primary (P) – primary target for convergence Secondary (S) – secondary target for convergence Tertiary (T) – third target for convergence Quarternary (Q) – fourth target for convergence Avaya does not recommend the Ext CP-Limit HardDown option for software Release 4.1 or later. Only use this option if SLPP is not available.
Page 107: Loop Detect
Loop prevention recommendations The following table describes the loop prevention features available for release 4.1.x and later. For best loop prevention, Avaya recommends that you use SLPP. Table 23: Loop prevention by release Software release...
Page 108: Sf/Cpu Protection And Loop Prevention Compatibility
SLPP Note 1: SF/CPU protection mechanism; do not enable on IST links. Note 2: With Release 4.1.1.0 and later, Avaya recommends that you use the Soft Down option versus Hard Down. Note 3: Do not enable SLPP on IST links.
Page 109: Chapter 10: Layer 3 Network Design
— IP Routing, NN46205-523. VRF Lite route redistribution Using VRF Lite, the Avaya Ethernet Routing Switch 8800/8600 can function as many routers; each Virtual Router and Forwarder (VRF) autonomous routing engine works independently. Normally, no route leak occurs between different VRFs. Sometimes users may have to redistribute OSPF or RIP routes from one VRF to another.
Page 110: Vrf Lite Architecture Examples
Figure 35: VRF Lite example The following figure shows how VRF Lite can be used in an SMLT topology. VRRP is used between the two bottom routers. June 2016 Planning and Engineering — Network Design Comments on this document? infodev@avaya.com...
Page 111 The following figure shows how VRF Lite can be used in an RSMLT topology. Figure 37: Router redundancy for multiple routing instances (using RSMLT) The following figure shows how VRFs can interconnect through an external firewall. June 2016 Planning and Engineering — Network Design Comments on this document? infodev@avaya.com...
Page 112 IP subnets from one VRF to another. Filters can be used to restrict access to certain protocols. This enables hub-and-spoke network designs for, for example, VoIP gateways. Figure 39: Inter VRF communication, internal inter-VRF forwarding June 2016 Planning and Engineering — Network Design Comments on this document? infodev@avaya.com...
Page 113: Virtual Router Redundancy Protocol
Instead, the backup router employs Layer 2 switching on the IST to deliver traffic to the VRRP master for routing. To allow both VRRP switches to route traffic, Avaya has created an extension to VRRP, BackupMaster, that creates an active-active environment for routing. With BackupMaster enabled on the backup router, the backup router no longer switches traffic to the VRRP Master.
Page 114 In some cases, setting the VRRP hold down timer to a minimum of 1.5 times the IGP convergence time is sufficient. For OSPF, Avaya recommends that you use a value of 90 seconds if using the default OSPF timers.
Page 115: Vrrp And Stg
• Do not use VRRP BackupMaster and critical IP at the same time. Use one or the other. • When implementing VRRP on multiple VLANs between the same switches, Avaya recommends that you configure a unique VRID on each VLAN.
Page 116: Vrrp And Icmp Redirect Messages
45 seconds. After spanning tree reconvergence, VRRP can take a few more seconds to failover. Rather than configuring STG with VRRP, Avaya recommends that you enable SMLT with VRRP to simplify the network configuration and reduce the failover time. For more information about VRRP...
Page 117: Ipv6 Vrrp
To avoid excessive ICMP redirect messages if network clients do not recognize ICMP redirect messages, Avaya recommends the network design shown in the following figure. Ensure that the routing path to the destination through both routing switches has the same metric to the destination.
Page 118 ND traffic. This is especially so when there are many hosts all trying to determine the reachability of one of more routers. To provide fast failover of a default router for IPv6 LAN hosts, the Avaya Ethernet Routing Switch 8800/8600 supports the Virtual Router Redundancy Protocol (VRRP v3) for IPv6 (defined in draft- ietf-vrrp-ipv6-spec-08.txt).
Page 119: Vrrp Versus Rsmlt For Default Gateway Resiliency
A better alternative than VRRP with BackupMaster is to use RSMLT L2 Edge. For Release 5.0 and later, Avaya recommends that you use an RSMLT L2 Edge configuration, rather than VRRP with BackupMaster, for those products that support RSMLT L2 Edge.
Page 120: Subnet-Based Vlan Guidelines
After the DHCP response is forwarded to the DHCP client and it learns its source IP address, the end-user traffic is appropriately classified into the subnet-based VLAN. The switch supports a maximum number of 200 subnet-based VLANs. June 2016 Planning and Engineering — Network Design Comments on this document? infodev@avaya.com...
Page 121: Pppoe-Based Vlan Design Example
8800/8600). • Each user is assigned their own VLAN. • Each user has two VLANs when directly connected to the Avaya Ethernet Routing Switch 8800/8600: one for IP traffic and the other for PPPoE traffic. • PPPoE bridged traffic preserves user VLANs.
Page 122: Indirect Connections
• The connection between the Layer 2 switch and the Ethernet Routing Switch 8800/8600 can be a single port connection or a MultiLink Trunk (MLT) connection. • Ethernet Routing Switch 8800/8600 ports connected to the user side (Users 1, 2, and 3) and the routed network are routed ports.
Page 123: Direct Connections
Figure 46: Indirect PPPoE and IP configuration Direct connections To directly connect to the Avaya Ethernet Routing Switch 8800/8600, a user must create two protocol-based VLANs on the port: one for PPPoE traffic and one for IP traffic (see the following figure).
Page 124: Border Gateway Protocol
Exterior BGP (EBGP), which refers to the protocol that BGP routers use across two different autonomous systems. BGP information is redistributed to Interior Gateway Protocols (IGP) running in the autonomous system. June 2016 Planning and Engineering — Network Design Comments on this document? infodev@avaya.com...
Page 125: Bgp Scaling
BGP to operate with are in forwarding mode. If you are using BGP for a multi-homed AS (one that contains more than a single exit point), Avaya recommends that you use OSPF for your IGP, and BGP for your sole exterior gateway protocol.
Page 126: Bgp And Other Vendor Interoperability
By using BGP, you can perform Internet peering directly between the Avaya Ethernet Routing Switch 8800/8600 and another edge router. In such a scenario, you can use each Avaya Ethernet Routing Switch 8800/8600 for aggregation and peer it with a Layer 3 edge router, as shown in the following figure.
Page 127 Figure 48: BGP and Internet peering In cases where the Internet connection is single-homed, to reduce the size of the routing table, Avaya recommends that you advertise Internet routes as the default route to the IGP. Routing domain interconnection with BGP You can implement BGP so that autonomous routing domains, such as OSPF routing domains, are connected.
Page 128 Figure 51: Multiple regions separated by IBGP In this figure, consider the following: • The AS is divided into three regions that each run different and independent IGPs. June 2016 Planning and Engineering — Network Design Comments on this document? infodev@avaya.com...
Page 129 AS numbers to prevent them from leaking to providers. The following figure illustrates a design scenario in which you use multiple OSPF regions to peer with the Internet. June 2016 Planning and Engineering — Network Design Comments on this document? infodev@avaya.com...
Page 130: Ipv6 Bgp
IPv6 routes using BGPv4 peering. BGP+ is an extension of BGPv4 for IPV6. Note that the Ethernet Routing Switch 8800/8600 BGP+ support is not an implementation of BGPv6. Native BGPv6 peering uses the IPv6 Transport layer (TCPv6 ) for establishing the BGPv6 peering, route exchanges, and data traffic.
Page 131: Open Shortest Path First
This section describes some general design considerations and presents a number of design scenarios for OSPF. For more information about OSPF and a list of OSPF commands see Avaya Ethernet Routing Switch 8800/8600 Configuration — OSPF and RIP, NN46205-522.
Page 132: Ospf Design Guidelines
The enabling of ICMP unreachable message generation on the switch may result in a high CPU utilization rate. To avoid high CPU utilization, Avaya recommends that you use a black hole static route configuration. The black hole static route is a route (equal to the OSPF summary route) with a next- hop of 255.255.255.255.
Page 133 S3 directly connects to S2, but any traffic between S1 and S3 is indirect, and passes through S2. Figure 55: Example 2: OSPF on two subnets in one area June 2016 Planning and Engineering — Network Design Comments on this document? infodev@avaya.com...
Page 134 192.168.20.2 which is in OSPF area 2. The general method used to configure OSPF for this three-switch network is: 1. On all three switches, enable OSPF globally. June 2016 Planning and Engineering — Network Design Comments on this document? infodev@avaya.com...
Page 135: Ip Routed Interface Scaling
VLAN ID for the OSPF port, and enable OSPF on the port. The three switches exchange Hello packets. In an environment with a mix of Cisco and Avaya switches/routers, you may need to manually modify the OSPF parameter RtrDeadInterval to 40 seconds.
Page 136: Ipv6 Requirements
29. Transition mechanisms for IPv6 The Avaya Ethernet Routing Switch 8800/8600 helps networks transition from IPv4 to IPv6 by using three primary mechanisms: • Dual Stack mechanism, where the IPv4 and IPv6 stacks can communicate with both IPv6 and IPv4 devices •...
Page 137 Your ISP also provides you with the required destination IPv4 address for the exit point of the tunnel. The following figure shows a manually-configured tunnel. For more information, see Avaya Ethernet Routing Switch 8800/8600 Configuration — IPv6 Routing Operations, NN46205-504. Figure 57: IPv6 tunnels Because each tunnel exists between only two routing switches and is independently managed, additional tunnels are required whenever you add new routing switches.
Page 138: Chapter 11: Spbm Design Guidelines
• For information on advanced configurations, see Shortest Path Bridging (802.1aq) for ERS 8800/8600 Technical Configuration Guide (NN48500-617). Note: For information on IP multicast over SPBM, see Avaya Ethernet Routing Switch 8800/8600 Configuration — Shortest Path Bridging (NN46205–525). Related links SPBM IEEE 802.1aq standards compliance...
Page 139: Spbm Ieee 802.1Aq Standards Compliance
Path Bridging MAC (SPBM) because the standard was not yet ratified. The standard is now ratified and Release 7.1.3 supports it. Avaya continues to support the pre-standard (or draft) SPBM for previous releases, but all future releases will support standard SPBM only. Release 7.1.3 is a bridge release that supports both draft and standard SPBM.
Page 140 Backbone VLAN IDs (B-VIDs) provisioned (with a maximum of 16 B-VIDs allowed by the standard and 2 allowed in ERS 8800 release 7.1) per IS-IS instance. IS-IS interfaces operate in point-to-point mode only, which means that for any given Ethernet or MLT interface where IS-IS has been enabled, there can be only one IS-IS adjacency across that interface.
Page 141: Vlans Without Member Ports
Ethernet Routing Switch 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.
Page 142: Spbm Provisioning
138 SPBM provisioning This section summarizes how to provision SPBM. For information on specific configuration commands, see Avaya Ethernet Routing Switch 8800/8600 Configuration — Shortest Path Bridging MAC (SPBM) (NN46205–525). Infrastructure provisioning Provisioning an SPBM core is as simple as enabling SPBM and IS-IS globally and on all the IS-IS core Ethernet links on all the BCB and BEB nodes.
Page 143: Spbm Implementation Options
Figure 59: SPBM support for campus and data center architecture Within the SPBM architecture, you can implement multiple options. The following figure shows all the options that SPBM supports. June 2016 Planning and Engineering — Network Design Comments on this document? infodev@avaya.com...
Page 144 IS-IS source address is configured to matched a circuitless/loopback IP address. In the figure above, node 8600G is acting as a BCB for the service, and has no IP configuration whatsoever. June 2016 Planning and Engineering — Network Design Comments on this document? infodev@avaya.com...
Page 145 IP routes and install IP routes learnt from IS-IS. Suitable IP redistribution policies need to be defined to determine what IP routes a BEB will advertise to IS-IS. June 2016 Planning and Engineering — Network Design Comments on this document? infodev@avaya.com...
Page 146 In this network, you can use some or all of the SPBM implementation options to meet the needs of the community while maintaining the security of information within VLAN members. June 2016 Planning and Engineering — Network Design Comments on this document? infodev@avaya.com...
Page 147 L3 VSNs. In all three domains, they can share data center resources across the SPBM network. Figure 62: SPBM ring topology with shared data centers June 2016 Planning and Engineering — Network Design Comments on this document? infodev@avaya.com...
Page 148: Spbm Reference Architectures
SPBM backbone (on the BEBs). There is no provisioning needed on the core SPBM nodes. The following figure illustrates an existing Edge connecting to an SPBM Core. June 2016 Planning and Engineering — Network Design Comments on this document? infodev@avaya.com...
Page 149 Related links SPBM design guidelines on page 138 SPBM campus architecture on page 150 SPBM multicast architecture on page 153 Large data center architecture on page 153 June 2016 Planning and Engineering — Network Design Comments on this document? infodev@avaya.com...
Page 150: Spbm Campus Architecture
OSPF, you can leave them in place too. SPBM uses IS-IS, and operates independently from other protocols. However, Avaya recommends that you eventually eliminate SMLT in the core and other unnecessary protocols. This reduces the complexity of the network and makes it much simpler to maintain and troubleshoot.
Page 151 The first figure below uses IP Shortcuts that route VLANs in the GRT. There is no I-SID configuration and no Layer 3 virtualization between the Edge Distribution and the Core. This is normal IP forwarding to the BEB. June 2016 Planning and Engineering — Network Design Comments on this document? infodev@avaya.com...
Page 152 VRFs are attached to I-SIDs and use Layer 3 virtualization. Figure 67: VRF scenario to move traffic between data centers Related links SPBM reference architectures on page 148 June 2016 Planning and Engineering — Network Design Comments on this document? infodev@avaya.com...
Page 153: Spbm Multicast Architecture
Release 7.2 of the ERS 8800/8600 builds on the simplicity introduced with Avaya VENA using SPBM for the control plane with support for Bridged and Routed IP Multicast traffic without the inefficiencies or complexities that exist today.
Page 154 Ethernet. This topology is optimized for storage transport because traffic never travels more than two hops. Note: Avaya recommends a two-tier, full-mesh topology for large data centers. Figure 68: SPBM data center — full-mesh Traditional data center routing of VMs In a traditional data center configuration, the traffic flows into the network to a VM and out of the network in almost a direct path.
Page 155 As you can see in the figure below, one VM move results in a convoluted traffic path. Multiply this with many moves and soon the network look like a tangled mess that is very inefficient, difficult to maintain, and almost impossible to troubleshoot. June 2016 Planning and Engineering — Network Design Comments on this document? infodev@avaya.com...
Page 156 Inter-VSN routing interfaces on the SPBM BCB nodes. This makes the IP routed paths top- down less optimal, but the BCBs will remain pure BCBs, thus simplifying core switch configurations. June 2016 Planning and Engineering — Network Design Comments on this document? infodev@avaya.com...
Page 157 With VRRP Backup Master, the traffic no longer goes through the default gateway; it takes the most direct route in and out of the network. June 2016 Planning and Engineering — Network Design Comments on this document? infodev@avaya.com...
Page 158: Spbm Scaling And Performance Capabilities
The test scenarios in this section simulate deployments of SPBM in Enterprise networks. Each figure represents an actual configuration that was tested in the Avaya Data Solutions Test Lab. The table accompanying each figure shows the scaling results of the tests performed in that test bed.
Page 159 Maximum number tested in this Maximum number supported in scenario all test scenarios Multicast streams on non-SPBM 1500 VLANs when SPBM is enabled on the switch Table continues… June 2016 Planning and Engineering — Network Design Comments on this document? infodev@avaya.com...
Page 160 IS-IS advertises a unique Virtual MAC to support SMLT-UNI so that LSP re-advertising and remote C-MAC re-learning is unnecessary when SMLT-UNI link failures occur. IS-IS also supports two B- MAC instances. June 2016 Planning and Engineering — Network Design Comments on this document? infodev@avaya.com...
Page 161 SPBM scaling and performance capabilities Figure 74: Test bed for upgrading a network to STP/SPBM The following table shows how SPBM scales in a smaller configuration with SMLT. June 2016 Planning and Engineering — Network Design Comments on this document? infodev@avaya.com...
Page 162 163 figure tests a square topology in the core and the red-dashed line outlines all the devices included in the SPBM network. This figure shows a network with an MSTP/SPBM configuration June 2016 Planning and Engineering — Network Design Comments on this document? infodev@avaya.com...
Page 163 VLANs when SPBM is enabled on the switch ARP entries with SPBM enabled 2000 6000 on the switch VLAN entries with SPBM enabled on the switch Table continues… June 2016 Planning and Engineering — Network Design Comments on this document? infodev@avaya.com...
Page 164 1,500 multicast groups streaming data across the SPBM network. Figure 76: Test bed for a greenfield MSTP/SPBM ring configuration The following table shows how SPBM scales in a ring with MSTP. June 2016 Planning and Engineering — Network Design Comments on this document? infodev@avaya.com...
Page 165: Spbm Best Practices
This section describes best practices when setting up SPBM networks. IS-IS • Avaya recommends that you change the IS-IS system ID from the default B-MAC value to a recognizable address to easily identify a switch. This helps to recognize source and destination addresses for troubleshooting purposes.
Page 166 The MIP must be configured at the same level as the MEP on all switches in the SPBM network. Example of a configuration using best practices - spbm-id - BVID #1 & BVID #2 : 4040, 4041 (ignore warning message when configuring) June 2016 Planning and Engineering — Network Design Comments on this document? infodev@avaya.com...
Page 167: Migration Best Practices
BEB in the SPBM network. • If you do not want to use Multicast over SPBM, disable both Multicast over SPBM and IGMP Snoop on each BEB in the SPBM network. June 2016 Planning and Engineering — Network Design Comments on this document? infodev@avaya.com...
Page 168 - If an IGP (OSPF) is being used on the VLAN, the impact on traffic during the migration can be reduced by using two VLANs in each routed segment and configuring the interface cost June 2016 Planning and Engineering — Network Design Comments on this document? infodev@avaya.com...
Page 169: Restrictions And Limitations
The B-VLAN active topology is controlled by IS-IS that has loop mitigation and prevention capabilities built into the protocol. • SPBM uses STG 63 (with Avaya STP enabled) or MSTI 62 (with MSTP enabled) for internal use. So STG 63 or MSTI 62 cannot be used by other VLAN/MSTI.
Page 170 VLACP is generally used when a repeater or switch exists between connected Ethernet Routing Switch 8800/8600 switches to detect when a connection is down even when the link light is up. If you have VLACP configured on an SPBM link that is also an IST link, during a connection fail over (where the link lights stay up) the IS-IS hellos time out first (after 27 seconds, using default values) and take down the IS-IS adjacency.
Page 171 • Filters are not supported on the B-VLAN NNI port. • Filters are not supported on the C-VLAN port for egress traffic. Related links SPBM design guidelines on page 138 June 2016 Planning and Engineering — Network Design Comments on this document? infodev@avaya.com...
Page 172: Chapter 12: Multicast Network Design
For more information about multicast routing, see Avaya Ethernet Routing Switch 8800/8600 Configuration — IP Multicast Routing Protocols (NN46205-501). Note: For information on IP multicast over SPBM, see Avaya Ethernet Routing Switch 8800/8600 Configuration — Shortest Path Bridging (NN46205–525). General multicast considerations Use the following general rules and considerations when planning and configuring IP multicast.
Page 173 7. For faster convergence, configure the Bootstrap and Rendezvous Point routers on a circuitless IP. For more information, see Circuitless IP for PIM-SM on page 205. 8. For faster convergence, Avaya recommends using a static Rendezvous Point (RP) router. June 2016 Planning and Engineering — Network Design Comments on this document? infodev@avaya.com...
Page 174: Multicast And Unified Access
ERS 8800/8600 switches support multicast with Avaya VENA Unified Access enabled. However, the number of IP multicast streams that the switch supports depends on the Unified Access configuration. In an ERS 8800/8600 switch, each IP multicast stream has a corresponding IpmcPep record that indicates the following information: • multicast stream incoming VLAN •...
Page 175 As a result, two IpmcPep records are required to handle each of these multicast streams. In this scenario, ERS 8800/8600 switches enabled with Unified Access support up to 3000 IP multicast streams. If this scenario is also in an SMLT setup, four IpmcPep records are required and the ERS 8800/8600 switches support up to 1500 IP multicast streams.
Page 176: Multicast And Vrf-Lite
• SMLT/RSMLT support for Multicast VRFs • 64 instances of PIM-SM/SSM • Total of 4000 multicast routes Requirements To support multicast virtualization, the Avaya Ethernet Routing Switch 8800/8600 must be equipped with the following: • Release 5.1 (or later) software • Premier Software License •...
Page 177 The following figure shows an example of multicast virtualization in an RSMLT topology. Figure 78: Multicast virtualization in RSMLT topology The following figure shows an example of multicast virtualization in an Enterprise/Metro network. June 2016 Planning and Engineering — Network Design Comments on this document? infodev@avaya.com...
Page 178 Multicast network design Figure 79: Multicast virtualization for Enterprise/Metro network The following figure shows an example of multicast virtualization supporting an end-to-end triple play solution for an MSO/Large Enterprise. June 2016 Planning and Engineering — Network Design Comments on this document? infodev@avaya.com...
Page 179 Figure 80: End-to-end triple play solution for MSO/Large Enterprise The following figure shows an example of multicast virtualization in a data center. Figure 81: Data center solution with multicast virtualization June 2016 Planning and Engineering — Network Design Comments on this document? infodev@avaya.com...
Page 180: Multicast And Multi-Link Trunking Considerations
Multicast traffic distribution is important because the bandwidth requirements can be substantial when a large number of streams are employed. The Avaya Ethernet Routing Switch 8800/8600 can distribute IP multicast streams over links of a multilink trunk. If you need to use several links to share the load of several multicast streams between two switches, use one of the following: •...
Page 181: Ip Multicast Address Range Restrictions
Authority for link-local network applications. Packets with an address in this range are not forwarded by multicast-capable routers. For example, OSPF uses 224.0.0.5 and 224.0.0.6, and VRRP uses 224.0.0.18 to communicate across local broadcast network segments. June 2016 Planning and Engineering — Network Design Comments on this document? infodev@avaya.com...
Page 182: Multicast Mac Address Mapping Considerations
Ethernet address (see the following figure). For example, all 32 addresses 224.1.1.1, 224.129.1.1, 225.1.1.1, 225.129.1.1, 239.1.1.1, 239.129.1.1 map to the same 01:00:5E:01:01:01 multicast MAC address. June 2016 Planning and Engineering — Network Design Comments on this document? infodev@avaya.com...
Page 183 When an IP multicast packet is received, the lookup is based on the IP group address, regardless of whether the VLAN is bridged or routed. Be aware that while the Avaya Ethernet Routing Switch 8800/8600 does not suffer from the problem described in the previous example, other switches in the network, particularly pure Layer 2 switches, can.
Page 184: Dynamic Multicast Configuration Changes
IP address, or the subnet mask for an interface until multicast traffic ceases. For such changes, Avaya recommends that you temporarily stop all multicast traffic. If the changes are necessary and you have no control over the applications that send multicast data, it may be necessary for you to disable the multicast routing protocols before performing the change.
Page 185: Ttl In Ip Multicast Packets
Ethernet Routing Switch 8800/8600 (Switch 1) to drop multicast traffic with a TTL of less than 2 (see Figure 85: IP multicast traffic with low TTL on page 185).
Page 186: Guidelines For Multicast Access Policies
At a minimum, map the multicast MAC address to a set of ports within the VLAN. In addition, if traffic is routed on the local Avaya Ethernet Routing Switch 8800/8600, you must configure an Address Resolution Protocol (ARP) entry to map the shared unicast IP address to the shared multicast MAC address.
Page 187: Split-Subnet And Multicast
RP on a split-subnet can impact the whole multicast traffic flow. Traffic can be affected even for receivers and senders that are not part of the split-subnet. Layer 2 multicast features On Layer 2 VLANs, the Avaya Ethernet Routing Switch 8800/8600 provides the following features to support multicast traffic. •...
Page 188: Igmp Snoop And Proxy
Configuration — IP Multicast Routing Protocols (NN46205-501). Multicast VLAN Registration (MVR) On Layer 2 VLANs, the Avaya Ethernet Routing Switch 8800/8600 uses IGMP Snoop to listen for report, leave and query packets, and then creates or deletes multicast groups for receiver ports to receive multicast data streams.
Page 189: Igmp Layer 2 Querier
Layer 2 querier is supported in the same Layer 2 multicast domain. No querier election is available. You cannot enable MVR and Layer 2 querier on the same VLAN. For more information about IGMP Layer 2 querier, see Avaya Ethernet Routing Switch 8800/8600 Configuration — IP Multicast Routing Protocols (NN46205-501). Pragmatic General Multicast guidelines Pragmatic General Multicast (PGM) is a reliable multicast transport protocol for applications that require ordered, duplicate free, multicast data delivery from multiple sources to multiple receivers.
Page 190: Distance Vector Multicast Routing Protocol Guidelines
Multicast network design The Avaya Ethernet Routing Switch 8800/8600 implements the Network Element part of PGM. Hosts running PGM implement the other PGM features. PGM operates on a session basis, so every session requires state information. Therefore, control both the number of sessions that the switch allows and the window size of these sessions.
Page 191: Dvmrp Scalability
The recommended maximum number of active multicast source/group pairs (S,G) is 2000. Avaya recommends that the number of source subnets multiplied by the number of receiver groups not exceed 500. If you need more than 500 active streams, group senders into the same subnets to achieve higher scalability.
Page 192: Dvmrp Design Guidelines
For faster network convergence in the case of failures or route changes, you may need to change the default values of these timers. If so, Avaya recommends that you follow these rules: • Ensure that all timer values match on all switches in the same DVMRP network. Failure to do so may result in unpredictable network behavior and troubleshooting difficulties.
Page 193: Dvmrp Policies
The following figure illustrates a similar scenario. As before, the goal is to receive and distribute public multicast streams on the private network, while not forwarding private multicast streams to the June 2016 Planning and Engineering — Network Design Comments on this document? infodev@avaya.com...
Page 194 To make the path between Routers B and D more preferable, use announce policies on Router A to increase the advertised metric of certain routes. Thus, traffic that originates from those subnets takes the alternate route between B and D. June 2016 Planning and Engineering — Network Design Comments on this document? infodev@avaya.com...
Page 195 (that do not contain sources) should not be advertised, you can selectively enable do not advertise self policies on a per-interface basis or you can configure announce policies. June 2016 Planning and Engineering — Network Design Comments on this document? infodev@avaya.com...
Page 196 Router A. Figure 91: Default route Avaya recommends that you configure announce policies on Routers A and B to suppress the advertisement of all other routes to Router C. Alternatively, you can configure accept policies on Router C to prevent all routes from Router A and Router B, other than the default, from installation in the routing table.
Page 197: Protocol Independent Multicast-Sparse Mode Guidelines
Protocol Independent Multicast-Sparse Mode guidelines Configure passive interfaces only on interfaces that contain potential sources of multicast traffic. If the interfaces are connected to networks that only have receivers, Avaya recommends that you use a do not advertise self policy on those interfaces.
Page 198: Pim General Requirements
196. Important: Avaya does not support more than 80 interfaces and recommends the use of not more than 10 PIM active interfaces in a large-scale configuration of more than 500 VLANs. If you configure more interfaces, they must be passive.
Page 199 Static RP cannot be enabled or configured on a switch in a mixed mode of candidate RP and static RP switches. For examples, see the following two figures. Figure 92: Example 1 June 2016 Planning and Engineering — Network Design Comments on this document? infodev@avaya.com...
Page 200: Pim And Shortest Path Tree Switchover
Regardless of their implementation, no interoperability issues with the Avaya Ethernet Routing Switch 8800/8600 result. Switching to and from the shared and shortest path trees is independently controlled by each downstream router. Upstream routers relay Joins and Prunes upstream hop-by-hop, building the desired tree as they go.
Page 201: Pim Traffic Delay And Smlt Peer Reboot
DVMRP domain, although you can use redundant switches for this purpose. You can use more than one interface on the switch to link the domains together. The following figure illustrates this basic scenario. June 2016 Planning and Engineering — Network Design Comments on this document? infodev@avaya.com...
Page 202 Multicast network design Figure 94: MBR configuration With the Avaya Ethernet Routing Switch 8800/8600 implementation you can place the RP anywhere in the network. The following figure shows a redundant MBR configuration, where two MBR switches connect a PIM to a DVMRP domain. This configuration is not a supported configuration; MBRs that connect two domains should not span the same VLAN on the links connected to the same domain.
Page 203 For a proper redundant configuration, ensure that the links use two separate VLANs (see the following figure). Ensure that the unicast routes and DVMRP routes always point to the same path. June 2016 Planning and Engineering — Network Design Comments on this document? infodev@avaya.com...
Page 204 To resolve this issue, stop the affected streams until DVMRP ages out the entries. Another alternative is to reinitialize DVMRP (disable and reenable) and then restart the multicast streams. June 2016 Planning and Engineering — Network Design Comments on this document? infodev@avaya.com...
Page 205: Circuitless Ip For Pim-Sm
DVMRP learns its routes before PIM learns the new unicast routes and reroutes the stream. If DVMRP and unicast routes diverge while traffic flows, the same problem may occur. As a result, for safe MBR network operation, Avaya recommends that you use the simple design proposed in PIM-SM to DVMRP connection: MBR.
Page 206 Avaya Ethernet Routing Switch 8800/8600 PIM-SM RP and BSR. You can use the static RP feature to interoperate in this environment. For example, in a mixed-vendor network, you can use auto-RP among routers that support the protocol, while other routers use static RP.
Page 207 IGP convergence and, more specifically, on the removal of the route to the RP from the routing table. With the route to the failed RP removed, the Avaya Ethernet Routing Switch 8800/8600 can fail over to an alternate static RP.
Page 208: Rendezvous Point Router Considerations
You can place an RP on any switch when VLANs extend over several switches. Indeed, you can place your RP on any switch in the network. However, when using PIM-SM, Avaya recommends that you not span VLANs on more than two switches.
Page 209 RP is not obvious. In this case, use the hash algorithm to reveal which of the remaining CRPs take over for a particular group address in the event of primary RP failure. June 2016 Planning and Engineering — Network Design Comments on this document? infodev@avaya.com...
Page 210 The group range 238.1.1.40 to 238.1.1.51 (12 consecutive groups) maps to 128.10.0.56. The group range 238.1.1.52 to 238.1.1.55 (4 consecutive groups) maps to 128.10.0.54. The group range 238.1.1.56 to 238.1.1.63 (8 consecutive groups) maps to 128.10.0.56. June 2016 Planning and Engineering — Network Design Comments on this document? infodev@avaya.com...
Page 211: Pim-Sm Receivers And Vlans
Switch A discards the data on the second path (assuming the upstream source is A to C). To avoid this waste of resources, Avaya recommends that you do not place receivers on V1. This guarantees that no traffic flows between B and A for receivers attached to A. In this case, the existence of the receivers is only learned through PIM Join messages to the RP [for (*,G)] and of the source through SPT Joins.
Page 212: Pim Network With Non-Pim Interfaces
(that is, through A). The simple workaround is to enable PIM on VLAN1 between C and B. Figure 101: PIM network with non-PIM interfaces June 2016 Planning and Engineering — Network Design Comments on this document? infodev@avaya.com...
Page 213: Protocol Independent Multicast-Source Specific Multicast Guidelines
RP Set configuration considerations When you configure RP sets (C-RPs or static RPs), Avaya recommends as best practice not to configure multiple entries that each specify a unique group, but instead specify a range of groups when possible, thereby decreasing the number of entries required.
Page 214: Msdp
SSM range, or use PIM-SM. Note: On the ERS 8800/8600 with IGMPv3, note that receivers on the same switch cannot join flows from different sources in the same group since the IGMPv3 channel table currently allows only one entry per group. It does not matter whether the sources are on different switches or not because the PIM state machine can manage multiple sources per group.
Page 215: Peers
If you configure a default peer, the switch accepts all SA messages from that peer. MSDP configuration considerations Avaya recommends that you configure MSDP on RPs for sources that send to global groups to announce to the Internet. You cannot configure the MSDP feature for use with the Virtual Router Forwarding (VRF) feature.
Page 216: Static Mroute
RFC 4624. Static mroute The Avaya Ethernet Routing Switch 8800/8600 supports a static IP route table to separate the paths for unicast and multicast streams. Only multicast protocols use this table. Adding a route to this table does not affect the switching or routing of unicast packets.
Page 217: Dvmrp And Pim Comparison
DVMRP uses flood and prune operations whereas PIM-SM uses shared and shortest-path trees. DVMRP is suitable for use in a dense environment where receivers are present in most parts of the June 2016 Planning and Engineering — Network Design Comments on this document? infodev@avaya.com...
Page 218: Unicast Routes For Pim Versus Dmvrp Own Routes
RP-set message to all PIM-enabled interfaces. In turn, this can cause a PIM-enabled switch to receive RP-set from multiple PIM neighbors towards the BSR. A PIM-enabled switch only accepts the BSR message from the RPF neighbor towards the BSR. June 2016 Planning and Engineering — Network Design Comments on this document? infodev@avaya.com...
Page 219: Igmp And Routing Protocol Interactions
VLAN. Source S is attached to switch A on a VLAN different than the one that connects A to C. A receiver (R) is attached to switch B on another VLAN. June 2016 Planning and Engineering — Network Design Comments on this document? infodev@avaya.com...
Page 220: Igmp And Pim-Sm Interaction
IGMP reports are forwarded only to A on the mrouter port P1. A does not create a leaf because reports are received on the interface towards the DR. June 2016 Planning and Engineering — Network Design Comments on this document? infodev@avaya.com...
Page 221: Multicast And Smlt Guidelines
To avoid using an external querier to provide correct handling and routing of multicast traffic to the rest of the network, Avaya recommends that you use the triangle design with IGMP Snoop at the client switches. Then use multicast routing (DVMRP or PIM) at the aggregation switches as shown in the following figure.
Page 222: Square And Full-Mesh Topology Multicast Guidelines
(RSMLT) configuration. The Avaya Ethernet Routing Switch 8800/8600 does not support DVMRP in SMLT full-mesh designs. In a square design, you must configure all switches with PIM-SM. Avaya recommends that you place the BSR and RP in one of the four core switches. For both full-mesh and square topologies that use multicast, you must set the multicast square-smlt flag.
Page 223: Smlt And Multicast Traffic Issues
IST. Although, in general, routing protocols should not run over an IST, multicast routing protocols are an exception. In a single PIM domain with an MBR (Multicast Border Router), Avaya does not support a configuration of DVMRP in a triangle SMLT and PIM-SM in a square SMLT.
Page 224 Because both A and B have a local receiver on the SMLT port, the IGMP switch receives data from both the routers, causing R to receive duplicate traffic. June 2016 Planning and Engineering — Network Design Comments on this document? infodev@avaya.com...
Page 225: Pim-Ssm Over Smlt/Rsmlt
The following figures show some examples of the supported topologies of PIM-SSM over SMLT. The following figure shows a triangle topology in which all the Ethernet Routing Switch 8800/8600s are running PIM-SSM at the core, and the Ethernet Routing Switch 8300 and the stackable Ethernet Routing Switches (5xxx/4500/2500) are also running PIM-SSM at the edge.
Page 226 Ethernet Routing Switches (5xxx/4500/2500) running PIM-SSM at the edge. In this case, however, the Ethernet Routing Switch 8800/8600s are running PIM-SM in the core. With the extended VLANs from the SSM edge to the SM core, the operating version of the interfaces in the core must be IGMPv2.
Page 227 The following figure shows a square or full mesh topology in which one Ethernet Routing Switch 8800/8600 IST pair is running PIM-SSM in the core, and the other IST pair is running Layer 2 IGMP. The Ethernet Routing Switch 8300 and the stackable Ethernet Routing Switches (5xxx/4500/2500) are also running Layer 2 IGMP at the edge.
Page 228 The following figure shows a square or full mesh topology in which both Ethernet Routing Switch 8800/8600 IST pairs are running PIM-SSM and RSMLT in the core. The Ethernet Routing Switch 8300 and the stackable Ethernet Routing Switches (5xxx/4500/2500) are running Layer 2 IGMP at the edge.
Page 229 The following figure shows a square or full mesh topology in which both Ethernet Routing Switch 8800/8600 IST pairs are running PIM-SSM and RSMLT in the core. The Ethernet Routing Switch 8300 and the stackable Ethernet Routing Switches (5xxx/4500/2500) are running PIM-SSM at the edge.
Page 230: Static-Rp In Smlt Using The Same Clip Address
RP using the same CLIP address, as shown in the following figure. In this case, (S,G) entries are not flushed out in the event of a failed RP, and therefore this configuration provides faster failover. June 2016 Planning and Engineering — Network Design Comments on this document? infodev@avaya.com...
Page 231 7. If the SW_D (RP) fails, SW_B changes only the next-hop interface towards SW_E, and since the RP address is the same, it does not flush any (S,G) entries. In this way, this configuration achieves faster failover. June 2016 Planning and Engineering — Network Design Comments on this document? infodev@avaya.com...
Page 232: Multicast For Multimedia
TV applications. Important: For IGMPv3, Avaya recommends that you ensure a Join rate of 250 per second or less. If the Avaya Ethernet Routing Switch 8800/8600 must process more than 250 Joins per second, users may have to resend Joins.
Page 233: Fast Leave
Conversely, if streams frequently start and stop in short intervals, as in a TV delivery network, assigning a value of ten may lead to frequent congestion in the core network. June 2016 Planning and Engineering — Network Design Comments on this document? infodev@avaya.com...
Page 234: Internet Group Membership Authentication Protocol
Test that value to ensure that it provides the best performance. Important: In networks that have only one user connected to each port, Avaya recommends that you use the Fast Leave feature instead of LMQI, since no wait is required before the stream stops.
Page 235 The following figure shows an IGAP member connected to an Avaya Ethernet Routing Switch 8800/8600 edge switch (R1) that has two MLT links. The MLT links provide alternative routes to the RADIUS authentication server and the Content Delivery Network (CDN) server.
Page 236 • Set the route preference (path cost) of the alternative link (MLT2) to equal or higher than MLT1. With this workaround, the switchover is immediate. Traffic is not interrupted and accounting does not have to be stopped and restarted. June 2016 Planning and Engineering — Network Design Comments on this document? infodev@avaya.com...
Page 237: Chapter 13: Mpls Ip Vpn And Ip Vpn Lite
Chapter 13: MPLS IP VPN and IP VPN Lite The Avaya Ethernet Routing Switch 8800/8600 supports Multiprotocol Label Switching (MPLS) and IP Virtual Private Networks (VPN) to provide fast and efficient data communications. In addition, to support IP VPN capabilities without the complexities associated with MPLS deployments, the Ethernet Routing Switch 8800/8600 supports IP VPN Lite.
Page 238: Operation Of Mpls Ip Vpn
(that is, each label corresponds to a FEC). Operation of MPLS IP VPN MPLS IP-VPN enabled routers use two labels as shown in the following figure. The Avaya Ethernet Routing Switch 8800/8600 uses LDP for IP VPN. LDP generates and distributes an outer label referred as a tunnel label, which is in fact the LSP.
Page 239 To support this capability, the PE router must maintain separate forwarding routing tables. To provide multiple independent IPv4 routing and forwarding tables, the Ethernet Routing Switch 8800/8600 supports a default routing instance (VRF0) and up to 255 Virtual Routing and Forwarding (VRF) instances (VRF1 to VRF255).
Page 240: Route Distinguishers
IPv4 address globally unique. As a result, each VPN can be distinguished by its own RD, and the same IPv4 address space can be used over multiple VPNs. The following figure shows the VPN-IPv4 address. June 2016 Planning and Engineering — Network Design Comments on this document? infodev@avaya.com...
Page 241: Route Targets
PE router export policy. Any PE router in the network configured with a matching route target in its import policy imports the route for that particular VRF. June 2016 Planning and Engineering — Network Design Comments on this document? infodev@avaya.com...
Page 242: Ip Vpn Requirements And Recommendations
To use IP VPN, you require R or RS modules, as well as the 8692 SF/CPU with SuperMezz or 8895 SF/CPU. You also require the appropriate license. The Avaya Ethernet Routing Switch 8800/8600 supports IP VPN over 802.3ad (MLT) Partial-HA (P-HA) is supported by IP VPN. P-HA means that a module can be enabled and configured when the system is running in the HA mode.
Page 243: Ip Vpn Prerequisites
IP VPN deployment scenarios When the Avaya Ethernet Routing Switch 8800/8600 is used as a PE device, the following are the means by which a CE device can connect to PE device: •...
Page 244: Mpls Interoperability
CE device works with EBGP running in the context of a VRF in the PE device. This suits carrier deployments. When the Ethernet Routing Switch 8800/8600 is used as a PE device, the following are the means by which a PE device can connect to a provider core device: •...
Page 245: Ip Vpn Lite
IP VPN services. With Avaya IP VPN-Lite, the RD is now used to convey one extra piece of information over and above its intended use within the RFC 4364 framework. In the RFC, the only purpose of the RD is to ensure that identical IPv4 routes from different customers are rendered unique so that BGP can treat them as separate VPN-IPv4 routes.
Page 246 While MPLS struggles to achieve these goals and only does so by bringing in exponential complexity, Avaya IP VPN-Lite can simply leverage these capabilities from either a pure IP OSPF routed core where ECMP is enabled or a network core designed with Avaya SMLT/RSMLT clustering.
Page 247: Ip Vpn Lite Deployment Scenarios
• the forwarding plane to encapsulate the customer IP packet into the revise IP header IP VPN Lite deployment scenarios The following sections describe how you can use the IP VPN Lite capability on the Avaya Ethernet Routing Switch 8800/8600 to design a sample network interconnecting five separate sites while meeting the following requirements: •...
Page 248: Smlt Design
MPLS IP VPN and IP VPN Lite SMLT design To meet the design requirements, an Avaya Ethernet Routing Switch 8800/8600 is deployed at each site. As shown in the following figure, the five Ethernet Routing Switch 8800/8600s are interconnected using 10 gigabit Ethernet links in an SMLT cluster configuration. The Ethernet...
Page 249: Layer 2 Vpn Design
Layer 2 VLANs that are added to this design must always be configured on both main sites 1 and 2 (the SMLT IST cluster) but only on the Avaya Ethernet Routing Switch 8800/8600 SMLT edge switches that require the VLANs. In this example, VLAN 12 is added to the SMLT IST cluster switches at sites 1 and 2 and then added at Sites 3 and 5.
Page 250: Inter-Site Igp Routing Design
To support a larger number of sites, Avaya recommends the use of BGP Route-Reflectors. This can be accomplished by making the Ethernet Routing Switch 8800/8600 at site 1 and site 2 redundant Route-Reflectors and every other site a Route-Reflector client.
Page 251: Internet Layer 3 Vpn Design
Internet Layer 3 VPN design The two Avaya Ethernet Routing Switch 8800/8600s in the main sites 1 and 2 also have a third CLIP address (also a Service IP) which is made the same at both sites. This CLIP address also uses a 24-bit mask and is only used for IPinIP encapsulated Layer 3 VPN traffic destined for the Internet.
Page 252 MPLS IP VPN and IP VPN Lite This allows both the site 1 and site 2 Ethernet Routing Switch 8800/8600s to handle Internet bound traffic from Site 3, 4 or 5 regardless of the MLT hash used by these SMLT edge sites (this eliminates the need for site 1 to forward some Internet bound traffic to site 2 over the IST and vice versa).
Page 253: Chapter 14: Layer 1, 2, And 3 Design Examples
This section provides examples to help you design your network. Layer 1 examples deal with the physical network layouts; Layer 2 examples map Virtual Local Area Networks (VLAN) on top of the physical layouts; and Layer 3 examples show the routing instances that Avaya recommends to optimize IP for network redundancy.
Page 254 Layer 1, 2, and 3 design examples Figure 128: Layer 1 design example 2 June 2016 Planning and Engineering — Network Design Comments on this document? infodev@avaya.com...
Page 255: Layer 2 Examples
Example 1 shows a redundant device network that uses one VLAN for all switches. To support multiple VLANs, 802.1Q tagging is required on the links with trunks. June 2016 Planning and Engineering — Network Design Comments on this document? infodev@avaya.com...
Page 256 Spanning Tree Protocol: SMLT prevents loops and ensures that all paths are actively used. Each wiring closet (WC) can have up to 8 Gbit/s access to the core. This SMLT configuration example is based on a three-stage network. June 2016 Planning and Engineering — Network Design Comments on this document? infodev@avaya.com...
Page 257 Layer 2 examples Figure 131: Layer 2 design example 2 June 2016 Planning and Engineering — Network Design Comments on this document? infodev@avaya.com...
Page 258 Because SMLT is part of MLT, all SMLT links have an MLT ID. The SMLT and MLT ID can be the same, but this is not necessary. June 2016 Planning and Engineering — Network Design Comments on this document? infodev@avaya.com...
Page 259: Layer 3 Examples
Figure 133: Layer 2 design example 4 Layer 3 examples The following figures are a series of Layer 3 network design examples that show the routing instances that Avaya recommends you use to optimize IP for network redundancy. June 2016 Planning and Engineering — Network Design...
Page 260 Layer 1, 2, and 3 design examples Figure 134: Layer 3 design example 1 June 2016 Planning and Engineering — Network Design Comments on this document? infodev@avaya.com...
Page 261 Layer 3 examples Figure 135: Layer 3 design example 2 In the following figures, DGW denotes Data GateWay. June 2016 Planning and Engineering — Network Design Comments on this document? infodev@avaya.com...
Page 262 Layer 1, 2, and 3 design examples Figure 136: Layer 3 design example 3 June 2016 Planning and Engineering — Network Design Comments on this document? infodev@avaya.com...
Page 263 Layer 3 examples Figure 137: Layer 3 design example 4 June 2016 Planning and Engineering — Network Design Comments on this document? infodev@avaya.com...
Page 264: Rsmlt Redundant Network With Bridged And Routed Vlans In The Core
Routing Information Protocol (RIP), Open Shortest Path First (OSPF) or Border Gateway Protocol (BGP) to exchange routing information. RSMLT and its protection mechanisms prevent the routing protocol convergence time from impacting network convergence time. June 2016 Planning and Engineering — Network Design Comments on this document? infodev@avaya.com...
Page 265 To reduce network convergence time in case of a failure in a network with multiple IP client stations, Avaya recommends that you distribute the ARP request/second load to multiple IP routers/switches. Enabling routing at the access layer distributes the ARP load, which reduces the IP subnet sizes.
Page 266: Chapter 15: Network Security
Redundant network design page 55. Without redundancy, all services can be brought down. To provide additional network security, you can use the Avaya Contivity VPN product suite or the Ethernet Routing Switch Firewall and Intrusion Sensor. They offer differing levels of protection against Denial of Service (DoS) attacks through either third party IDS partners, or through their own high-performance stateful firewalls.
Page 267: Broadcast And Multicast Rate Limiting
Directed broadcast suppression protects hosts from possible DoS attacks. To prevent the flooding of other networks with DoS attacks, such as the Smurf attack, the Avaya Ethernet Routing Switch 8800/8600 is protected by directed broadcast suppression. This feature is enabled by default.
Page 268: Arp Request Threshold Recommendations
The Address Resolution Protocol (ARP) request threshold limits the ability of the Avaya Ethernet Routing Switch 8800/8600 to source ARP requests for workstation IP addresses it has not learned within its ARP table. The default setting for this function is 500 ARP requests per second. To avoid excessive amounts of subnet scanning caused by a virus (like Welchia), Avaya recommends that you change the ARP request threshold to a value between 100 to 50.
Page 269: Multicast Learning Limitation
CPU through a port during a sampling interval, the port is shut down until the user or administrator takes the appropriate action. For more information and configuration instructions, see Avaya Ethernet Routing Switch 8800/8600 Configuration — IP Multicast Routing Protocols, NN46205-501.
Page 270: Packet Spoofing
255.255.255.255/32 Broadcast1 You can also enable the spoof-detect feature on a port. For more information about the spoof-detect feature, see Avaya Ethernet Routing Switch 8800/8600 Configuration — VLANs and Spanning Tree, NN46205-517. June 2016 Planning and Engineering — Network Design...
Page 271: High Secure Mode
IP Filtering for R and RS Modules, NN46205-507. High Secure mode To ensure that the Avaya Ethernet Routing Switch 8800/8600 does not route packets with an illegal source address of 255.255.255.255 (in accordance with RFC 1812 Section 4.2.2.11 and RFC 971 Section 3.2), you can enable High Secure mode.
Page 272: Security And Redundancy
Network security Security and redundancy Redundancy in hardware and software is one of the key security features of the Avaya Ethernet Routing Switch 8800/8600. High availability is achieved by eliminating single points of failure in the network and by using the unique features of the Avaya Ethernet Routing Switch 8800/8600 including: •...
Page 273: Eap
Figure 139: 802.1x and OPS interaction Software support is included for the Preside (Funk) and Microsoft IAS RADIUS servers. Additional RADIUS servers that support the EAP standard should also be compatible with the Avaya Ethernet Routing Switch 8800/8600. For more information, contact your Avaya representative.
Page 274: Vlans And Traffic Isolation
The Sygate LAN Enforcer or the Avaya VPN TunnelGuard enables the Avaya Ethernet Routing Switch 8800/8600 to use the 802.1x standard to ensure that a user connecting from inside a corporate network is legitimate. The LAN Enforcer/TunnelGuard also checks the endpoint security posture, including anti-virus, firewall definitions, Windows registry content, and specific file content (plus date and size).
Page 275: Dynamic Arp Inspection (Dai)
• VLAN ID • port You can also configure static DHCP binding entries. Dynamic binding entries are lost after a restart. For more information about DHCP snooping, see Avaya Ethernet Routing Switch 8800/8600 Security (NN46205-601). Dynamic ARP Inspection (DAI) Dynamic ARP Inspection (DAI) is a security feature that validates ARP packets in the network. It intercepts, discards, and logs ARP packets with invalid IP-to-MAC address bindings.
Page 276: Ip Source Guard
DHCP snooping and untrusted for Dynamic ARP Inspection. IP Source Guard cannot be enabled on MLT/SMLT ports. For more information about IP Source Guard, see Avaya Ethernet Routing Switch 8800/8600 Security (NN46205-601). Security at layer 2...
Page 277: Security At Layer 3: Filtering
At Layer 3 and above, the Avaya Ethernet Routing Switch 8800/8600 provides enhanced filtering capabilities as part of its security strategy to protect the network from different attacks. You can configure two types of Classic filters on the Avaya Ethernet Routing Switch 8800/8600: global filters and source/destination address filters.
Page 278: Security At Layer 3: Announce And Accept Policies
MD5 keys per interface. You can also use multiple MD5 key configurations for MD5 transitions without bringing down an interface. For more information, see Avaya Ethernet Routing Switch 8800/8600 Configuration — OSPF and RIP, NN46205-522 and Avaya Ethernet Routing Switch 8800/8600 Configuration — BGP Services, NN46205-510.
Page 279: Management Port
286 Management port The Avaya Ethernet Routing Switch 8800/8600 provides an isolated management port on the switch fabric/CPU. This separates user traffic from management traffic in highly sensitive environments, such as brokerages and insurance agencies. By using this dedicated network (see the following figure) to manage the switches, and by configuring access policies (when routing is enabled), you can manage the switch in a secure fashion.
Page 280: Management Access Control
Network security Figure 142: Terminal servers/modem access When it is an absolute necessity for you to access the switch, Avaya recommends that you use this configuration. The switch is always reachable, even if an issue occurs with the in-band network management interface.
Page 281: High Secure Mode
High Secure mode Use High Secure to disable all unsecured application and daemons, such as FTP, TFTP, and rlogin. Avaya recommends that you not use any unsecured protocols. For more information, see High Secure mode. Use Secure Copy (SCP) rather than FTP or TFTP. For more information, see SSHv1/v2 page 286.
Page 282: Radius Authentication
You can configure a list of up to 10 RADIUS servers on the client. If the first server is unavailable, the Avaya Ethernet Routing Switch 8800/8600 tries the second, and then attempts each server in sequence until it establishes a successful connection.
Page 283: Radius Over Ipv6
Avaya recommends that you use the default value in the attribute-identifier field. If you change the set default value, you must alter the dictionary on the RADIUS server with the new value. To configure the RADIUS feature, you require Read-Write-All access to the switch.
Page 284: Tacacs
Network security For more information about RADIUS over IPv6, see Avaya Ethernet Routing Switch 8800/8600 Security, NN46205-601. TACACS+ Terminal Access Controller Access Control System (TACACS+) is a security application implemented as a client/server-based protocol that provides centralized validation of users attempting to gain access to a router or network access server.
Page 285: Encryption Of Control Plane Traffic
AV pairs. The accounting records are stored on the security server. The accounting data can then be analyzed for network management and auditing. The Avaya Ethernet Routing Switch 8800/8600 supports eight users logged in to the chassis simultaneously with TACACS+.
Page 286: Snmp Header Network Address
SNMPv3 support SNMP version 1 and version 2 are not secure because communities are not encrypted. Avaya recommends that you use SNMP version 3. SNMPv3 provides stronger authentication services and the encryption of data traffic for network management. Other security equipment Avaya offers other devices that increase the security of your network.
Page 287 VPN technology employs IP Security (IPSec) and Secure Sockets Layer (SSL) services. Several Avaya products support IPSec and SSL. Contivity and the Services Edge Router support IPSEC. Contivity supports up to 5000 IPSEC tunnels, and scales easily to support operational requirements.
Page 288: For More Information
• The Center of Internet Security Expertise (CERT) • The Research and Education Organization for Network Administrators and Security Professionals (SANS) • The Computer Security Institute (CSI) June 2016 Planning and Engineering — Network Design Comments on this document? infodev@avaya.com...
Page 289: Chapter 16: Qos Design Guidelines
(latency), and packet delay variation (jitter). For more information about fundamental QoS mechanisms, and how to configure QoS, see Avaya Ethernet Routing Switch 8800/8600 Configuration — QoS and IP Filtering for R and RS Modules, NN46205-507.
Page 290 802.1p field is not trusted to be correct. An internal QoS level is assigned to each packet that enters an Ethernet Routing Switch 8800/8600 port. Once the QoS level is set, the egress queue is determined and the packet is transmitted. The mapping of QoS levels to queue is a hard-coded 1-to-1 mapping.
Page 291: Qos And Queues
The egress priority and discard priority are commonly referred to as latency and drop precedence, respectively. Each port on the Avaya Ethernet Routing Switch 8800/8600 has eight (or 64, depending on the module) egress queues. Each queue is associated with an egress priority. Some queues are designated as Strict Priority queues, which means that they are guaranteed service, and some are designated as Weighted Round Robin (WRR) queues.
Page 292: Qos And Filters
QoS level at both Layer 2 (802.1p) and Layer 3 (DSCP). Traffic filtering is a key QoS feature. The Avaya Ethernet Routing Switch 8800/8600, by default, determines incoming packet 802.1p or DiffServ markings, and forwards traffic based on their assigned QoS levels.
Page 293 This strategy reduces the number of ACEs. You can configure a maximum of 1000 ACEsper port for ingress and egress. The Avaya Ethernet Routing Switch 8800/8600 supports a maximum of 4000 ACEs. For each ACL, a maximum of 500 ACEsare supported.
Page 294: Policing And Shaping
Rate metering can only be performed on a Layer 3 basis. Traffic shapers buffer and delay violating traffic. These operations occur at the egress queue set level. The Ethernet Routing Switch 8800/8600 supports traffic shaping at the port level and at the per-transmit-queue level for outgoing traffic.
Page 295: Qos Interface Considerations
QoS level to the packets and sends the packets to the appropriate egress queues for servicing. The following figure illustrates how packets are processed through a core port. Figure 148: Core port QoS actions June 2016 Planning and Engineering — Network Design Comments on this document? infodev@avaya.com...
Page 296: Bridged And Routed Traffic
QoS features are unavailable in the bridging mode of operation. If the Ethernet Routing Switch 8800/8600 is configured for bridging, ingress traffic is mapped from IEEE 802.1p-bits to the appropriate QoS level, and egress traffic is mapped from the QoS level to the appropriate IEEE 802.1p-bits.
Page 297: 802.1P And 802.1Q Recommendations
If 802.1Q-tagged encapsulation is not used to connect to the Ethernet Routing Switch 8800/8600, traffic can only be classified based on VLAN membership, port, or MAC address. To ensure consistent Layer 2 QoS boundaries within the service provider network, you must use 802.1Q encapsulation to connect a CPE directly to an Ethernet Routing Switch 8800/8600 access...
Page 298: Qos Examples And Recommendations
When severe congestion is detected, the Ethernet Routing Switch 8800/8600 discards traffic based on drop precedence values. This mode of operation ensures that high-priority traffic is not discarded before lower-priority traffic.
Page 299 QoS examples and recommendations Figure 150: Trusted bridged traffic The following figure shows what happens inside an Ethernet Routing Switch 8800/8600 access node. Packets enter through a tagged or untagged access port, and exit through a tagged or untagged core port.
Page 300 QoS design guidelines The following figure shows what happens inside an Ethernet Routing Switch 8800/8600 core node. Packets enter through a tagged or untagged core port, and exit through a tagged or untagged core port. Figure 152: QoS actions on bridged or routed core ports Bridged untrusted traffic When you set the port to access, mark and prioritize traffic on the access node using global filters.
Page 301: Routed Traffic
When you route traffic over the core network, VLANs are not kept separate. The following case describes QoS design guidelines you can use to provide and maintain high service quality in an Avaya Ethernet Routing Switch 8800/8600 network. Routed trusted traffic When you set the port to core, you assumethat, for all incoming traffic, the QoS setting is properly marked.All core switch ports simply read and forward packets.
Page 302 Figure 154: Trusted routed traffic Routed untrusted traffic The following figure shows what happens inside an Avaya Ethernet Routing Switch 8800/8600 access node. Packets enter through a tagged or untagged access port and exit through a tagged or untagged core port.
Page 303: Appendix A: Hardware And Supporting Software Compatibility
Appendix A: Hardware and supporting software compatibility The following table describes Avaya Ethernet Routing Switch 8800/8600 hardware and the minimum software version required to support the hardware. EUED RoHS compliancy: Beginning July 1, 2006, products can be ordered with European Union Environmental Directive (EUED) Restriction of Hazardous Substances (RoHS) (EUED RoHS) compliancy.
Page 304 DS1405018-E6 8005DI DC 1462 W Dual input DC DS1405017-E5 8005DC 1462 W DC 4.0.x DS1405011 Table 36: Ethernet Routing Switch 8800/8600 modules and components Minimum software Part number Module or component version Ethernet R modules 8630GBR 30-port Gigabit Ethernet SFP 4.0.0...
Page 305 • 82 m using 50 µm, 500 MHz- km MMF. • 300 m using 50 µm, 2000 MHz-km MMF. • 400 m using OM4 MMF 10GBASE-LRM 1310 nm. 7.1.3 AA1403017–E6 Table continues… June 2016 Planning and Engineering — Network Design Comments on this document? infodev@avaya.com...
Page 306 NTK587AYE5 10GBASE DWDM 1538.19 nm (194.9 THz) 5.1.0 NTK587BAE5 10GBASE DWDM 1538.98 nm (194.8 THz) 5.1.0 NTK587BCE5 10GBASE DWDM 1539.77 nm (194.7 THz) 5.1.0 NTK587BEE5 Table continues… June 2016 Planning and Engineering — Network Design Comments on this document? infodev@avaya.com...
Page 307 1542.94 nm (194.3 THz) 5.1.0 NTK587BNE5 10GBASE DWDM 1543.73 nm (194.2 THz) 5.1.0 NTK587BQE5 10GBASE DWDM 1544.53 nm (194.1 THz) 5.1.0 NTK587BSE5 10GBASE DWDM 1545.32 nm (194.0 THz) 5.1.0 NTK587BUE5 June 2016 Planning and Engineering — Network Design Comments on this document? infodev@avaya.com...
Page 308: Appendix B: Supported Standards, Rfcs, And Mibs
IEEE 802.1X Extensible Authentication Protocol IEEE 802.3 CSMA/CD Ethernet(ISO/IEC 8802-3) IEEE 802.3ab 1000BASE-T Ethernet IEEE 802.3ab 1000BASE-LX Ethernet IEEE 802.3ab 1000BASE-ZX Ethernet IEEE 802.3ab 1000BASE-CWDM Ethernet Table continues… June 2016 Planning and Engineering — Network Design Comments on this document? infodev@avaya.com...
Page 309: Ietf Rfcs
RFC 894 A standard for the Transmission of IP Datagrams over Ethernet Networks RFC 896 Congestion control in IP/TCP internetworks RFC 903 Reverse ARP Protocol Table continues… June 2016 Planning and Engineering — Network Design Comments on this document? infodev@avaya.com...
Page 310 RFC 906 Bootstrap loading using TFTP RFC 950 Internet Standard Subnetting Procedure RFC 951 / RFC 2131 BootP/DHCP RFC 1027 Using ARP to implement transparent subnet gateways/ Avaya Subnet based VLAN RFC 1058 RIPv1 Protocol RFC 1112 IGMPv1 RFC 1253...
Page 311 RFC 3569 An overview of Source-Specific Multicast (SSM) RFC 3917 Requirements for IP Flow Information Export (IPFIX) RFC 4364 BGP/MPLS IP Virtual Private Networks (VPNs) Table continues… June 2016 Planning and Engineering — Network Design Comments on this document? infodev@avaya.com...
Page 312: Ipv4 Multicast
RFC 1981 Path MTU Discovery for IP v6 RFC 2030 Simple Network Time Protocol (SNTP) v4 for IPv4, IPv6 & OSI RFC 2373 IPv6 Addressing Architecture Table continues… June 2016 Planning and Engineering — Network Design Comments on this document? infodev@avaya.com...
Page 313: Platform
RFC 1340 Assigned Numbers RFC 1350 The TFTP Protocol (Revision 2) Quality of Service (QoS) The following table describes the supported IETF RFCs for Quality of Service (QoS). June 2016 Planning and Engineering — Network Design Comments on this document? infodev@avaya.com...
Page 314: Network Management
RFC 2575 View-based Access Control Model (VACM) for the Simple Network Management Protocol (SNMP) RFC 2576 Coexistence between v1, v2, & v3 of the Internetstandard Network Management Framework June 2016 Planning and Engineering — Network Design Comments on this document? infodev@avaya.com...
Page 315: Supported Network Management Mibs
Standard MIBs, as well as private MIB extensions, which ensure compatibility with existing network management tools. All these MIBs are included with any software version that supports them. Consult the Avaya Web site for a file called mib.zip, which contains all MIBs, and a special file called manifest.
Page 316 (SNMP) RFC 3635 Definitions of Managed Objects for the Ethernet-like Interface Types RFC 3636 Definitions of Managed Objects for IEEE 802.3 Medium Attachment Units (MAUs) Table continues… June 2016 Planning and Engineering — Network Design Comments on this document? infodev@avaya.com...
Page 317 Network Control Protocol of the Point-to-Point Protocol – Avaya Proprietary The Definitions of Managed Objects for the Bridge rfc1474rcc.mib Network Control Protocol of the Point-to-Point Protocol Table continues… June 2016 Planning and Engineering — Network Design Comments on this document? infodev@avaya.com...
Page 318 Supported standards, RFCs, and MIBs Proprietary MIB name File name Definitions of Managed Objects for the SONET/SDH rfc1595rcc.mib Interface Type – Avaya Proprietary OSPF Version 2 Management Information Base – rfc1850t_rcc.mib Avaya proprietary extensions Avaya IPv6 proprietary MIB definitions rfc_ipv6_tc.mib, inet_address_tc.mib, ipv6_flow_label.mib...
Page 319 (ADM) A network element in which facilities are added, dropped, or passed directly through for transmission to other network elements. June 2016 Planning and Engineering — Network Design Comments on this document? infodev@avaya.com...
Page 320 (BER) The ratio of the number of bit errors to the total number of bits transmitted in a given time interval. June 2016 Planning and Engineering — Network Design Comments on this document? infodev@avaya.com...
Page 321 A technology that uses multiple optical signals with different wavelengths to simultaneously transmit in the same direction over one fiber, and then separates by wavelength at the distant end. June 2016 Planning and Engineering — Network Design Comments on this document? infodev@avaya.com...
Page 322 Custom AutoNegotiation Advertisement can advertise a user-defined subset of the capabilities that settle on a lower or particular capability. June 2016 Planning and Engineering — Network Design Comments on this document? infodev@avaya.com...
Page 323 A database that maps a port for every MAC address. If a packet is sent to a specific MAC address, the switch refers to the forwarding database for the corresponding port number and sends the data packet through that port. June 2016 Planning and Engineering — Network Design Comments on this document? infodev@avaya.com...
Page 324 A method of link aggregation that uses multiple Ethernet trunks aggregated to provide a single logical trunk. A multilink trunk provides the combined bandwidth of multiple links and the physical layer protection against the failure of a single link. June 2016 Planning and Engineering — Network Design Comments on this document? infodev@avaya.com...
Page 325 Open Shortest Path First (OSPF) A link-state routing protocol used as an Interior Gateway Protocol (IGP). June 2016 Planning and Engineering — Network Design Comments on this document? infodev@avaya.com...
Page 326 (SFP) A hot-swappable input and output enhancement component used with Avaya products to allow gigabit Ethernet ports to link with other gigabit Ethernet ports over various media types. June 2016 Planning and Engineering — Network Design...
Page 327 Split MultiLink Trunking (SMLT) An Avaya extension to IEEE 802.1AX (link aggregation), provides nodal and link failure protection and flexible bandwidth scaling to improve on the level of Layer 2 resiliency. June 2016 Planning and Engineering — Network Design Comments on this document? infodev@avaya.com...

This manual is also suitable for:

8600

Avaya 8800 Planning And Engineering, Network Design

Chapter 1: Safety Messages

Chapter 2: Introduction

Chapter 3: New in this Release

Chapter 4: Network Design Fundamentals

Chapter 5: Hardware Fundamentals and Guidelines

Chapter 6: Optical Routing Design

Chapter 7: Software Considerations

Chapter 8: Redundant Network Design

Chapter 9: Layer 2 Loop Prevention

Chapter 10: Layer 3 Network Design

Chapter 11: SPBM Design Guidelines

Chapter 12: Multicast Network Design

Chapter 13: MPLS IP VPN and IP VPN Lite

Chapter 14: Layer 1, 2, and 3 Design Examples

Chapter 15: Network Security

Chapter 16: Qos Design Guidelines

Appendix A: Hardware and Supporting Software Compatibility

Appendix B: Supported Standards, Rfcs, and Mibs

Quick Links

Related Manuals for Avaya 8800

Summary of Contents for Avaya 8800