Sample Configuration with Avaya Ethernet Routing Switch

WDC; Reviewed: SPOC 12/10/2010

Solution & Interoperability Test Lab Application Notes ©2010 Avaya Inc. All Rights Reserved.

1 of 32 sample_lab_core

Avaya Solution & Interoperability Test Lab

Sample Configuration with Avaya Ethernet Routing Switch Supporting Switch Clustering Using Split Multi-Link Trunking in an Avaya Aura Infrastructure - Issue 1.0

Abstract These Application Notes describe a sample configuration using Avaya Ethernet Routing Switch (ERS) 8600’s clustered in a core network and connecting to the distribution layer in a triangle topology using Avaya ERS 5698 edge switches. The core is built using two like ERS 8600’s connected together by an Inter-Switch Trunk (IST). The IST consists of two physical Ethernet connections configured together as a MultiLink Trunk (MLT) to provide added resiliency and throughput. The core and distribution layer switches use the Split MultiLink Trunks (SMLT) between them to provide redundant connections which can be scaled as the network demand increases.




1. Introduction These Application Notes describe a sample configuration using Avaya Ethernet Routing Switch (ERS) 8600’s clustered in a core network and connecting to the distribution layer in a triangle topology using Avaya ERS 5698 edge switches as shown in Figure 1. The core is built using two like ERS 8600’s connected together by an Inter-Switch Trunk (IST). The IST consists of two physical Ethernet connections configured together as a MultiLink Trunk (MLT) to provide added resiliency and throughput. The core and distribution layer switches use the Split MultiLink Trunks (SMLT) between them to provide redundant connections which can be scaled as the network demand increases. Each of these SMLT pairs from the ERS 5698 edge switches to the two ERS 8600 core switches represent a single MultiLink Trunk. This configuration builds a four triangle topology within the provider’s network.

Figure 1: Sample Core Network




1.1. Layer 2 Edge This topology represents different VLAN(s) spanning from each edge device(s) and those VLANs being routed at the Switch Cluster Core. Multiple VLANs are configured on the edge devices and 802.1Q tagged to the Switch Cluster Core via the SMLT connections. Ethernet or Fiber-Channel connections are in this sample configuration to extend VLAN connectivity from the provider edge to the customer edge. The customer edge is represented as devices outside the dotted circle in Figure 1. VLAN tagging must be enabled on the Ethernet or Fiber-Channel ports used for trunking to the customer’s edge device and the customer’s edge device must support VLAN tagging.

1.2. Layer 3 Core All MLTs connect to the core ERS8600 switches via SMLTs connections, each connecting from a provider edge switch (ERS5698) to each of the core ERS8600 switches. These SMLT ports on the ERS5698s are VLAN tagged and have been added to the VLANs supported on each of the provider edge switches. The core ERS8600 switches have also been configured with all the VLANs supported by the connected ERS5698 switches and the SMLT port members have been enabled for VLAN tagging. Open Shortest Path First (OSPF) routing has been enabled on the VLANs configured on the core ERS8600 switches allowing routing between VLANs at the core of the network configuration.

1.3. VLANS The sample configuration uses four VLANs:

VLAN 1 Default Management VLAN, VLAN 588 will be the new management VLAN. IST VLAN between core ERS8600 switches.

VLAN 588 Devices having IP Address Range 135.9.88.xxx / 24 bit mask. New Management VLAN.

VLAN 728 Devices having IP Address Range 135.9.288.xxx / 24 bit mask.

VLAN 20 Data devices (HTTP, FTP, DHCP, DNS, SNMP, etc.) having IP Address Range 20.20.20.xxx / 24 bit mask. Note: VLAN 20 will only be added between the core switches (SIL-8600-1, SIL-8600-2) and the provider edge switch (SIL-5698-1) to support trunking to the customer edge switch (SIL-5520-1).

VLAN 1 is created by default on all the switch devices and has been originally assigned as the management VLAN. VLAN 588 is created on the core ERS8600 switches and on the provider edge ERS5698 switches. The port members assigned to VLAN 588 on the ERS5698 switches are grouped into the lower port region of ports 1/1 – 1/50. VLAN 728 is created on the core ERS8600 switches and on the provider edge ERS5698 switches. The port members assigned to VLAN 728 on the ERS5698 switches are grouped into the upper port region of ports 1/51 – 1/98. Ports 1/91 – 1/98 may be reassigned when used as trunk connections to the customer’s edge




devices. The management VLAN on both core and edge devices has been changed to use VLAN 588. All SMLT connections on both the core and edge switches have been enabled to use VLAN tagging (802.1Q) allowing multiple VLANs across a single trunk connection. If VLAN tagging were not enabled on the trunks connecting the switches, then a physical trunk connection would have to exist for each VLAN between switches and the port membership assigned to the VLAN it supports. No routing is enabled at the provider edge switches between the VLANs and all VLAN broadcast domains are isolated from one another on each switch. The core switches have routing turned on and is the central location where routing occurs. This means that devices at a customer site connecting through a provider edge switch on one VLAN will always have to pass through the core to communicate with another device, anywhere on the network, that is on a different VLAN. Also, customer devices connecting through different provider edge switches are able to communicate with one another as the VLAN has been extended through the core and edge switches allowing traffic to pass through the core to the other edge switch. It is important to note that customer devices on the same VLAN and connected to the same provider edge switch will only have traffic switched between ports on that edge switch and will not need to pass through the core switches. These traffic routing scenarios will need to be considered in designing test cases where expected traffic may need to be routed by the core switches.

2. Equipment and Software Validated The following equipment and software were used for the sample configuration provided:

Equipment Software Avaya™ ERS 8600 Image: p80a7000.img Slot 1: 8630GBR -- Slot 2: Empty -- Slot 3: 8648GTR -- Slot 4: 8683XLR -- Slot 5: 8692SF Version: 7.0.0.0/094

Image: PMC280-A-MV-A0-MPC7447A (1.1) Slot 6: 8692SF Version: 7.0.0.0/094

Image: PMC280-A-MV-A0-MPC7447A (1.1) Slot 7: 8648GTR -- Slot 8: 8683XLR -- Slot 9: 8630GBR -- Slot 10: Empty Avaya™ ERS 5698 HW: 03

FW: 6.0.0.10 SW: 6.2.0.009

Avaya™ ERS 5520 HW: 33 FW: 5.0.0.4 SW: 5.1.1.017

Avaya™ ERS 4548 -- Avaya™ ERS 2526 --




3. Configure Core ERS8600 Switches

3.1. Configure IST between Core ERS8600s

Figure 2: ERS8600 Core IST The first step of building the clustered switched core of the network is to connect the ERS8600 switches via an Inter-Switch Trunk using VLAN 1. A serial console cable is connected from the serial port on a laptop computer to the serial connection on the front of the management card on the ERS8600s. In this configuration sample these management cards are in slot 5 and 6 of the ERS860s. HyperTerminal can be used on the serial port configured for 9600 bits per second, 8 data bits, No Parity, 1 Stop bit, and flow control set to Xon/Xoff. The ERS8600 can support two user command interfaces, the NNCLI and the Passport command interface. Each of these command interfaces supports similar configuration functionality, but use different command syntax to accomplish configuration tasks. For this configuration example both ERS8600’s will be configured from the console using the Passport command interface.

3.1.1. Name Each ERS8600 SIL-8600-1: Step 1 – Configure CLI Prompt with Name

SIL-8600-1:6# cli prompt "SIL-8600-1"

SIL-8600-2: Step 1 – Configure CLI Prompt with Name

SIL-8600-2:6# cli prompt “SIL-8600-2”

3.1.2. Create IST VLAN SIL-8600-1: Step 1 – Create VLAN 1

SIL-8600-1:6# config vlan 1 create byport 1 name IST

SIL-8600-1:6# config vlan 1 ip create 10.10.10.1/30

SIL-8600-2: Step 1 – Create VLAN 1

SIL-8600-2:6# config vlan 1 create byport 1 name IST





3.1.3. Create IST Multilink Trunking 1 (MLT 1) will be used for the IST with port members 7/1 and 7/2. 802.1Q tagging will be enabled on all IST port members and Spanning Tree will be disabled on all IST port members by default. SIL-8600-1: Step 1 – Create MLT 1 for IST

SIL-8600-1:6# config mlt 1 create

SIL-8600-1:6# config mlt 1 name IST

SIL-8600-1:6# config mlt 1 add port 7/1,7/2

SIL-8600-1:6# config vlan 1 add-mlt 1

SIL-8600-2: Step 1 – Create MLT 1 for IST


SIL-8600-2:6# config mlt 1 name IST

SIL-8600-2:6# config mlt 1 add port 7/1,7.2


SIL-8600-1: Step 2 – Create IST

SIL-8600-1:6# config mlt 1 ist create ip 10.10.10.2 vlan-id 1

SIL-8600-1:6# config mlt 1 ist enable

SIL-8600-2: Step 2 – Create IST

SIL-8600-2:6# config mlt 1 ist create ip 10.10.10.1 vlan-id 1

SIL-8600-2:6# config mlt 1 ist enable

3.2. Configure MLT 2 on Core ERS8600 Switches

Figure 3: ERS8600 MLT 2




MLT 2 connects the ERS5698 (SIL-5698-1) to the core using two Split Multilink Trunks (SMLTs) each connecting to one of the ERS8600 switches (SIL-8600-1 and SIL-8600-2). See Figure 3. To allow for future expansion, two ports (Ports 3/3, 3/4) on each ERS8600 will be configured for SMLT 2. However, only one Ethernet port will be connected from each of the ERS8600s back to SIL-5698-1 in this example. Three VLANs (588, 728, and 20) will be configured and assigned IP addresses on each of the ERS8600s to allow for routing at the core of these VLANS. SMLT 2 will be added to each of these VLANs. IP OSPF routing will be enabled on the core switches for each of the VLANs. This will allow the provider edge switch (SIL-5698-1) access to the specified VLAN by port assignment. Also, the data network (VLAN 20) will be accessible via trunk connection from the customer edge (SIL-5520-1) to the provider edge (SIL-5698-1).

3.2.1. Create VLANs 588, 728, and 20 SIL-8600-1: Step 1 – Create VLAN 588

SIL-8600-1:6# config vlan 588 create byport 1 name “VLAN #588”




















3.2.2. Enable IP OSPF Routing on VLANs SIL-8600-1: Step 1 – Enable IP OSPF Routing on VLANs

SIL-8600-1:6# config vlan 588 ip ospf enable



SIL-8600-1:6# config ip ospf enable

SIL-8600-2: Step 3 – Enable IP OSPF Routing on VLANs




SIL-8600-2:6# config ip ospf enable

3.2.3. SMLT-2 to SIL-5698-1 SIL-8600-1: Step 1 – Create SMLT-2


SIL-8600-1:6# config mlt 2 name SIL-5698-1

SIL-8600-1:6# config mlt 2 add ports 3/3,3/4

SIL-8600-1:6# config mlt 2 perform-tagging enable

SIL-8600-1:6# config mlt 2 smlt create smlt-id 2

SIL-8600-2: Step 1 – Create SMLT-2






SIL-8600-1: Step 2 – Add SMLT-2 to VLANs












Figure 4: ERS8600 MLT 3 MLT 3 connects the ERS5698 (SIL-5698-2) to the core using two Split Multilink Trunks (SMLTs) each connecting to one of the ERS8600 switches (SIL-8600-1 and SIL-8600-2). See Figure 4. To allow for future expansion, two ports (Ports 3/5, 3/6) on each ERS8600 will be configured for SMLT 3. However, only one Ethernet port will be connected from each of the ERS8600s back to SIL-5698-2 in this example. SIL-5698-2 only supports VLANs 588 and 728. Therefore, SMLT 3 will only be added to the 588 and 728 VLAN configurations.










































































4. Configure Edge ERS5698 Switches This section covers the necessary steps to configure the provider edge ERS5698 switches connecting back to the core ERS8600 switches via Multilink Trunks using a Split-Multilink Trunk configuration. The MLT on each of the ERS5698s will have two SMLT physical connections, each connecting to one of the ERS8600 switches. VLANs supported over the MLTs will be created and configured with assigned port members as described in Table 1. Ethernet and Fiber-Channel ports will be configured as trunking ports extending the ERS5698s VLAN connectivity beyond the provider edge to the customer edge. Any SMLT trunks or VLAN trunks will have spanning-tree turned off and all other ports will have spanning-tree set to "Fast Learning".

Edge Switch

IP Mask

Gateway

MLT MLT Port

Members

VLANs

* = Mgt. VLAN

VLAN Port Members

SIL-5698-1 IP: 135.9.88.85 Mask: 255.255.255.0 GW: 135.9.88.254

2 3,4 1 None 588 * 1/1-1/50 728 1/3-1/4, 1/51-1/93, 1/95-1/98 20 1/3-1/4, 1/94

SIL-5698-2 IP: 135.9.88.86 Mask: 255.255.255.0 GW: 135.9.88.254

3 5,6 1 None 588 * 1/1-1/50, 1/91 728 1/5-1/6, 1/51-1/90,1/92-1/98

SIL-5698-3 IP: 135.9.88.87 Mask: 255.255.255.0 GW: 135.9.88.254

4 13,14 1 None 588 * 1/1-1/50 728 1/13-1/14, 1/51-1/98

SIL-5698-4 IP: 135.9.88.88 Mask: 255.255.255.0 GW: 135.9.88.254

5 15,16 1 None 588 * 1/1-1/50, 1/91 728 1/15-1/16, 1/51-1/90, 1/92-1/98

Table 1: Provider Edge Switch Info Figure 7 shows a graphical view of the front of an ERS5698. Pay special attention when connecting cables on these devices as numbering starts on the lower, left section with port 1 on top and port 2 below it. The port number continues in ascending order, alternating top bottom until port 49 which then is the top port on the left side of the upper port block section. In addition, Fiber-Channel ports 91-96 are the same as the Ethernet ports labeled 91-96.

Figure 7: ERS5698TFD-PWR Front View




4.1. Basic Configuration

4.1.1. Name Each ERS5698 Press CTRL-Y to begin. If this is the first time entering the ERS5698 system you may be prompted to enter some information to initially configure the switch such as in-band IP Address, sub-net mask, Default Gateway, Read-Only Community String, Read-Write Community String, Quick Start VLAN, in-band IPV6 Address/Prefix length, and in-band IPV6 Default Gateway. Accept the default values for each of these prompts. All of these values can be changed from inside the configuration menu. If the initial configuration has already been performed, then you will be presented with the ERS5698 Main Menu selection. Select “System Characteristics” and press Enter.

Ethernet Routing Switch 5698TFD‐PWR Main Menu IP Configuration/Setup... SNMP Configuration... System Characteristics... Switch Configuration... Console/Comm Port Configuration... Display Hardware Units... Spanning Tree Configuration... TELNET/SNMP/SSH/Web Access Configuration... Software Download... Configuration File... Display System Log... Reset... Reset to Default Settings... Shutdown Command... Command Line Interface... Logout... Use arrow keys to highlight option, press <Return> or <Enter> to select option.




On the “System Characteristics” menu, arrow down to the sysName field and enter the name of the switch. In the sample below the switch is named “SIL-5698-1”.

Repeat the above steps for each of the four ERS5698 switches:

SIL-5698-1 SIL-5698-2 SIL-5698-3 SIL-6598-4

Press CTRL-C to return to the Main Menu when finished.

System Characteristics Operation Mode: Switch MAC Address: E0‐26‐36‐F2‐7C‐00 Reset Count: 16 Last Reset Type: Management Factory Reset Power Supply: (1) AC‐DC‐48V‐1000W (2) Unavailable (3) Unavailable Power Status: (1) OK (2) Not Present (3) Not Present sysDescr: Ethernet Routing Switch 5698TFD‐PWR HW:03 FW:6.0.0.10 SW:v6.2.0.009 sysObjectID: 1.3.6.1.4.1.45.3.74.1 sysUpTime: 18 days, 22:14:59 sysNtpTime: SNTP not synchronized. sysRtcTime: Friday 2005/01/21 01:08:00 sysServices: 6 sysContact: [ ] sysName: [ SIL‐5698‐1 ] sysLocation: [ ] Press Ctrl‐N to display the next page of this form. Enter text, press <Return> or <Enter> when complete. Press Ctrl‐R to return to previous menu. Press Ctrl‐C to return to Main Menu.




4.1.2. Assign IP Address to ERS5698 Use the IP Address, Mask, and Gateway values in Table 1 to assign each of the edge ERS5698 switches their IP configuration for connectivity and remote management. Repeat these steps for each of the switches listed in Table 1. From the Main Menu, select "IP Configuration/Setup".

Enter the IP Address for the switch in "In-Band Switch IP Address." Press Enter. Enter the Subnet Mask for the switch in "In-Band Subnet Mask." Press Enter. Enter the Gateway for the switch in "Default Gateway." Press Enter. Press CTRL-C to return to the Main Menu.

IP Configuration/Setup BootP/DHCP Request Mode: [ BootP When Needed ] Configurable In Use Last BootP/DHCP ‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐ ‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐ ‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐ In‐Band Stack IP Address: [ 0.0.0.0 ] 0.0.0.0 0.0.0.0 In‐Band Switch IP Address: [ 135.9.88.85 ] 135.9.88.85 0.0.0.0 In‐Band Subnet Mask: [ 255.255.255.0 ] 255.255.255.0 0.0.0.0 Default Gateway: [ 135.9.88.83 ] 135.9.88.83 0.0.0.0 IP Address to Ping: [ 0.0.0.0 ] Start Ping: [ No ] Enter text, press <Return> or <Enter> when complete. Press Ctrl‐R to return to previous menu. Press Ctrl‐C to return to Main Menu.





4.2. Advanced Configuration

4.2.1. Configure VLANs Refer to Table 1 for the list of VLANs and Port Members to be configured on each of the provider edge switches in the sample configuration. From the Main Menu, select "Switch Configuration."

From the Switch Configuration Menu, select "VLAN Configuration."

Switch Configuration Menu MAC Address Table MAC Address Security Configuration... EAPOL Security Configuration... VLAN Configuration... Port Configuration... High Speed Flow Control Configuration... MultiLink Trunk Configuration... Port Mirroring Configuration... Rate Limiting Configuration... IGMP Configuration... Display Port Statistics Clear All Port Statistics Return to Main Menu Use arrow keys to highlight option, press <Return> or <Enter> to select option. Press Ctrl‐R to return to previous menu. Press Ctrl‐C to return to Main Menu.





From the VLAN Configuration Menu, select "VLAN Configuration."

4.2.1.1 VLAN 1 By default VLAN 1 is already created and active with all ports assigned to it under Port Membership. The management VLAN is currently assigned to VLAN 1. Referring to Table 1, VLAN 1 on edge switch SIL-5698-1 does not have any port members assigned. Ports are shown to be members of a VLAN when they are marked with a "+" and not port members when they are marked with a "-". To remove port members from a VLAN 1 navigate the cursor, using the arrow keys, to the port desired and use the space bar to toggle between "+" and "-"; selecting "-" for "Not a Member", then press Enter to confirm. The sample below shows port 1 removed from VLAN 1.

Repeat this for all ports removing them from VLAN 1.

VLAN Configuration Create VLAN: [ 1 ] VLAN Type: [ Port‐Based ] Delete VLAN: [ ] Protocol Id (PID): [ None ] VLAN Name: [ VLAN #1 ] User‐Defined PID: [ 0x0000 ] Management VLAN: [ Yes ] Now: 1 VLAN State: [ Active ] STP Group: 1 Port Membership 1‐6 7‐12 13‐18 19‐24 25‐30 31‐36 37‐42 43‐48 49‐50 51‐56 57‐62 63‐68 69‐74 75‐80 81‐86 87‐92 93‐98 Unit #1 ‐+++++ ++++++ ++++++ ++++++ ++++++ ++++++ ++++++ ++++++ ++ ++++++ ++++++ ++++++ ++++++ ++++++ ++++++ ++++++ ++++++ KEY: + = A Member of This VLAN, ‐ = Not a Member of This VLAN Use space bar to display choices, press <Return> or <Enter> to select choice. Press Ctrl‐R to return to previous menu. Press Ctrl‐C to return to Main Menu.

VLAN Configuration Menu VLAN Configuration... VLAN Port Configuration... VLAN Display by Port... Return to Switch Configuration Menu Use arrow keys to highlight option, press <Return> or <Enter> to select option. Press Ctrl‐R to return to previous menu. Press Ctrl‐C to return to Main Menu.




4.2.1.2 VLAN 588 To create VLAN 588, enter "588" in the Create VLAN field and press Enter. The VLAN Name will be automatically completed with "VLAN #588". Referring to Table 1, VLAN 588 is used as a management VLAN. Change the Management VLAN to "Yes" by moving the cursor to this field and pressing the space bar to change the value from "No" to "Yes" and press Enter. The "Management VLAN Now" should show 588 as the management VLAN. Change the VLAN State to "Active" and press Enter. Referring to Table 1, configure the port members for VLAN 588 as described in Section 4.2.1.1.

4.2.1.3 VLAN 728 To create VLAN 728, enter "728" in the Create VLAN field and press Enter. The VLAN Name will be automatically completed with "VLAN #728". Referring to Table 1, VLAN 728 is not

VLAN Configuration Create VLAN: [ 1 ] VLAN Type: [ Port‐Based ] Delete VLAN: [ ] Protocol Id (PID): [ None ] VLAN Name: [ VLAN #1 ] User‐Defined PID: [ 0x0000 ] Management VLAN: [ No ] Now: 588 VLAN State: [ Active ] STP Group: 1 Port Membership 1‐6 7‐12 13‐18 19‐24 25‐30 31‐36 37‐42 43‐48 49‐50 51‐56 57‐62 63‐68 69‐74 75‐80 81‐86 87‐92 93‐98 Unit #1 ‐‐‐‐‐‐ ‐‐‐‐‐‐ ‐‐‐‐‐‐ ‐‐‐‐‐‐ ‐‐‐‐‐‐ ‐‐‐‐‐‐ ‐‐‐‐‐‐ ‐‐‐‐‐‐ ‐‐ ‐‐‐‐‐‐ ‐‐‐‐‐‐ ‐‐‐‐‐‐ ‐‐‐‐‐‐ ‐‐‐‐‐‐ ‐‐‐‐‐‐ ‐‐‐‐‐‐ ‐‐‐‐‐‐ KEY: + = A Member of This VLAN, ‐ = Not a Member of This VLAN Use space bar to display choices, press <Return> or <Enter> to select choice. Press Ctrl‐R to return to previous menu. Press Ctrl‐C to return to Main Menu.

VLAN Configuration Create VLAN: [ 588 ] VLAN Type: [ Port‐Based ] Delete VLAN: [ ] Protocol Id (PID): [ None ] VLAN Name: [ VLAN #588 ] User‐Defined PID: [ 0x0000 ] Management VLAN: [ Yes ] Now: 588 VLAN State: [ Active ] STP Group: 1 Port Membership 1‐6 7‐12 13‐18 19‐24 25‐30 31‐36 37‐42 43‐48 49‐50 51‐56 57‐62 63‐68 69‐74 75‐80 81‐86 87‐92 93‐98 Unit #1 ++++++ ++++++ ++++++ ++++++ ++++++ ++++++ ++++++ ++++++ ++ ‐‐‐‐‐‐ ‐‐‐‐‐‐ ‐‐‐‐‐‐ ‐‐‐‐‐‐ ‐‐‐‐‐‐ ‐‐‐‐‐‐ ‐‐‐‐‐‐ ‐‐‐‐‐‐ KEY: + = A Member of This VLAN, ‐ = Not a Member of This VLAN Use space bar to display choices or enter text. Press Ctrl‐R to return to previous menu. Press Ctrl‐C to return to Main Menu.




the management VLAN. Check to see that the Management VLAN is set to "No". Check to see that the "Management VLAN Now" shows 588 as the management VLAN. Change the VLAN State to "Active" and press Enter. Referring to Table 1, configure the port members for VLAN 728 as described in Section 4.2.1.1.

VLAN Configuration Create VLAN: [ 728 ] VLAN Type: [ Port‐Based ] Delete VLAN: [ ] Protocol Id (PID): [ None ] VLAN Name: [ VLAN #728 ] User‐Defined PID: [ 0x0000 ] Management VLAN: [ No ] Now: 588 VLAN State: [ Active ] STP Group: 1 Port Membership 1‐6 7‐12 13‐18 19‐24 25‐30 31‐36 37‐42 43‐48 49‐50 51‐56 57‐62 63‐68 69‐74 75‐80 81‐86 87‐92 93‐98 Unit #1 ‐‐++‐‐ ‐‐‐‐‐‐ ‐‐‐‐‐‐ ‐‐‐‐‐‐ ‐‐‐‐‐‐ ‐‐‐‐‐‐ ‐‐‐‐‐‐ ‐‐‐‐‐‐ ‐‐ ++++++ ++++++ ++++++ ++++++ ++++++ ++++++ ++++++ +‐++++ KEY: + = A Member of This VLAN, ‐ = Not a Member of This VLAN Use space bar to display choices or enter text. Press Ctrl‐R to return to previous menu. Press Ctrl‐C to return to Main Menu.




4.2.1.4 VLAN 20 VLAN 20 is created on SIL-5968-1 and will have only port member 94 which will be used as a trunking port to the customer’s edge switch. See Figure 1. Port members 3 and 4 will be used by the SMLT for connectivity back to the core switches. To create VLAN 20, enter "20" in the Create VLAN field and press Enter. The VLAN Name will be automatically completed with "VLAN #20". Referring to Table 1, VLAN 20 is not the management VLAN. Check to see that the Management VLAN is set to "No". Check to see that the "Management VLAN Now" shows 588 as the management VLAN. Change the VLAN State to "Active" and press Enter. Referring to Table 1, configure the port members for VLAN 20 as described in Section 4.2.1.1.

Return to the Main Menu by pressing CTRL-C when finished.

VLAN Configuration Create VLAN: [ 20 ] VLAN Type: [ Port‐Based ] Delete VLAN: [ ] Protocol Id (PID): [ None ] VLAN Name: [ VLAN #20 ] User‐Defined PID: [ 0x0000 ] Management VLAN: [ No ] Now: 588 VLAN State: [ Active ] STP Group: 1 Port Membership 1‐6 7‐12 13‐18 19‐24 25‐30 31‐36 37‐42 43‐48 49‐50 51‐56 57‐62 63‐68 69‐74 75‐80 81‐86 87‐92 93‐98 Unit #1 ‐‐++‐‐ ‐‐‐‐‐‐ ‐‐‐‐‐‐ ‐‐‐‐‐‐ ‐‐‐‐‐‐ ‐‐‐‐‐‐ ‐‐‐‐‐‐ ‐‐‐‐‐‐ ‐‐ ‐‐‐‐‐‐ ‐‐‐‐‐‐ ‐‐‐‐‐‐ ‐‐‐‐‐‐ ‐‐‐‐‐‐ ‐‐‐‐‐‐ ‐‐‐‐‐‐ ‐+‐‐‐‐ KEY: + = A Member of This VLAN, ‐ = Not a Member of This VLAN Use space bar to display choices or enter text. Press Ctrl‐R to return to previous menu. Press Ctrl‐C to return to Main Menu.




4.2.2. Configure Multilink Trunk Configuration From the Main Menu, select “Switch Configuration.”

From the Switch Configuration Menu, select “MultiLink Trunk Configuration.”






From the MultiLink Trunk Configuration Menu, select “MultiLink Trunk Configuration.”

Referring to Table 1, select the trunk matching the MLT value for the switch being configured. In this sample configuration, SIL-5698-1 has an MLT value of 2, indicating Trunk 2 will be configured on the MultiLink Trunk Configuration screen. Enter the Port Members referenced in Table 1 and press Enter after each entry. Select “ALL” for STPG and press Enter. Select “Normal” for Learning and press Enter. Select “Enable” for Status to activate the MLT.

Press CTRL-C to return to the Main Menu.

MultiLink Trunk Configuration Trunk Members STPG Learning Mode Status ‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐ 1 [ / ][ / ][ / ][ / ] [ Trunk #1 ] [ / ][ / ][ / ][ / ][ALL ] [ Normal ] Basic [ Disabled ] 2 [ / 3][ / 4][ / ][ / ] [ Trunk #2 ] [ / ][ / ][ / ][ / ][ALL ] [ Normal ] Basic [ Enabled ] 3 [ / ][ / ][ / ][ / ] [ Trunk #3 ] [ / ][ / ][ / ][ / ][ALL ] [ Normal ] Basic [ Disabled ] 4 [ / ][ / ][ / ][ / ] [ Trunk #4 ] [ / ][ / ][ / ][ / ][ALL ] [ Normal ] Basic [ Disabled ] 5 [ / ][ / ][ / ][ / ] [ Trunk #5 ] [ / ][ / ][ / ][ / ][ALL ] [ Normal ] Basic [ Disabled ] 6 [ / ][ / ][ / ][ / ] [ Trunk #6 ] [ / ][ / ][ / ][ / ][ALL ] [ Normal ] Basic [ Disabled ] Enter Port Number: Use space bar to display choices or enter number. Enter 0 to delete. Press Ctrl‐R to return to previous menu. Press Ctrl‐C to return to Main Menu.

MultiLink Trunk Configuration Menu MultiLink Trunk Configuration... MultiLink Trunk Utilization... Return to Switch Configuration Menu Use arrow keys to highlight option, press <Return> or <Enter> to select option. Press Ctrl‐R to return to previous menu. Press Ctrl‐C to return to Main Menu.




4.2.3. Enable Tagging on the SMLT Ports From the Main Menu, select “Switch Configuration.”

From the Switch Configuration Menu, select "VLAN Configuration."






From the VLAN Configuration Menu, select “VLAN Port Configuration.”

Referring to Table 1, select the first port member for the MLT on the switch and press Enter. In the Tagging field, change tagging to “Tag All”. Repeat for the second MLT port member. This will configure each of the SMLT ports to support multiple VLANs using VLAN tagging back to the core switches. Note: The Port Vlan ID (PVID) must match the vlan-id that it is a member of when tagging is set to untagged. When tagging is set to Tag All, the PVID does not need to be configured as the system will automatically assign based on the vlan port it is a member of.

Press CTRL-C, to return to the Main Menu when finished.

VLAN Configuration Menu VLAN Configuration... VLAN Port Configuration... VLAN Display by Port... Return to Switch Configuration Menu Use arrow keys to highlight option, press <Return> or <Enter> to select option. Press Ctrl‐R to return to previous menu. Press Ctrl‐C to return to Main Menu.

VLAN Port Configuration Port: [ 3 ] Filter Untagged Frames: [ No ] Filter Unregistered Frames: [ Yes ] Port Name: [ Port 3 ] PVID: [ 1 ] Port Priority: [ 0 ] Tagging: [ Tag All ] ConfigControl (global): [ Strict ] Use space bar to display choices or enter text. Press Ctrl‐R to return to previous menu. Press Ctrl‐C to return to Main Menu.




4.2.4. Disable Spanning Tree on SMLT and Trunk Ports From the Main Menu, select “Spanning Tree Configuration.”

From the Spanning Tree Configuration Menu, select “Spanning Tree Port Configuration.”

Spanning Tree Configuration Menu Spanning Tree Group Configuration... Spanning Tree Port Configuration... Display Spanning Tree Switch Settings... Display Spanning Tree VLAN Membership... Return to Main Menu Use arrow keys to highlight option, press <Return> or <Enter> to select option. Press Ctrl‐R to return to previous menu. Press Ctrl‐C to return to Main Menu.





Change SMLT port members and trunk port members to have Participation as “Disabled.” The remaining ports should be set to “Fast Learning.” Use CTRL-N to move forward to additional ports.

Press CTRL-C to return to the Main Menu.

Spanning Tree Port Configuration STP Group: [ 1 ] STP Mode: STPG (Nortel MSTP) Port Trunk Participation Priority Path Cost State ‐‐‐‐ ‐‐‐‐‐ ‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐ ‐‐‐‐‐‐‐‐ ‐‐‐‐‐‐‐‐‐ ‐‐‐‐‐‐‐‐‐‐ 1 [ Fast Learning ] 128 1 Forwarding 2 [ Fast Learning ] 128 1 Forwarding 3 2 [ Disabled ] 4 2 [ Disabled ] 5 [ Fast Learning ] 128 1 Forwarding 6 [ Fast Learning ] 128 1 Forwarding 7 [ Fast Learning ] 128 1 Forwarding 8 [ Fast Learning ] 128 1 Forwarding 9 [ Fast Learning ] 128 1 Forwarding 10 [ Fast Learning ] 128 1 Forwarding 11 [ Fast Learning ] 128 1 Forwarding 12 [ Fast Learning ] 128 1 Forwarding 13 [ Fast Learning ] 128 1 Forwarding 14 [ Fast Learning ] 128 1 Forwarding More... Press Ctrl‐N to display next screen. Enter number, press <Return> or <Enter> when complete. Press Ctrl‐R to return to previous menu. Press Ctrl‐C to return to Main Menu.




5. Verification Steps The ping command should be used to verify connectivity across all network devices. The ERS8600 switches use the command line ping command and the ERS5698 switches can use the ping command from the System Characteristics Menu.




6. Conclusion These Application Notes describe a sample lab configuration using Avaya Ethernet Routing Switches ERS8600 clustered in a core network and connecting to Avaya Ethernet Routing Switches ERS5698 at the provider’s edge creating the distribution network layer in a triangle topology. These Application Notes also provide a step by step configuration guide of each of the devices used in making this network design.




7. References The following references are relevant to these Application Notes: Avaya Switch Clustering

[1] Switch Clustering (SMLT/SLT/RSMLT/MSMLT) Supported Topologies and Interoperability with ERS 8600 / 5000 / 8300 / 1600, Document Number: NN48500-555, Version: 1.2.0.0, January 26, 2009, available at http://support.nortel.com.

[2] Switch Clustering: Design Best Practices, Document Number: NN48500-584, Version: 2.2, July 2009, available at http://support.nortel.com.

Avaya ERS8600

[3] Avaya Switch Clustering using Split Multi-Link Trunking (SMLT) with ERS 8600, 8300, 5x00 and 1600 Series: Technical Configuration Guide, Document Number: NN48600-518, Version: 3.8, June 4, 2009, available at http://support.nortel.com.

Avaya ERS5000

[4] Avaya Ethernet Routing Switch 5000 Series: Configuration - System, Document Number: NN47200-500, Version: 05.02, Release 6.1, November 19, 2010, available at http://support.nortel.com.

[5] Avaya Ethernet Routing Switch 5000 Series: Configuration – VLANS, Spanning Tree, and Link Aggregation, Document Number: NN47200-502, Version: 06.01, Release 6.2, June 28, 2010, available at http://support.nortel.com.




©2010 Avaya Inc. All Rights Reserved. Avaya and the Avaya Logo are trademarks of Avaya Inc. All trademarks identified by ® and ™ are registered trademarks or trademarks, respectively, of Avaya Inc. All other trademarks are the property of their respective owners. The information provided in these Application Notes is subject to change without notice. The configurations, technical data, and recommendations provided in these Application Notes are believed to be accurate and dependable, but are presented without express or implied warranty. Users are responsible for their application of any products specified in these Application Notes. Please e-mail any questions or comments pertaining to these Application Notes along with the full title name and filename, located in the lower right corner, directly to the Avaya Solution & Interoperability Test Lab at [email protected]

Documents

Sample Configuration with Avaya Ethernet Routing Switch