Abstract. Avaya Solution & Interoperability Test Lab

Transcription

1 Avaya Solution & Interoperability Test Lab Application Notes for Configuring Multiple EAPS Domains with Shared Port using Extreme Networks BlackDiamond 12804, BlackDiamond and Avaya Communication Manager - Issue 1.0 Abstract These Application Notes describe the steps for configuring Multiple Ethernet Automatic Protection Switching (EAPS) Domains using a shared port in a network environment with Avaya Communication Manager and Avaya IP Telephones. A partial mesh four-node network using various Extreme Networks Switches was used in the configuration. Avaya IP Telephony was implemented in this configuration to demonstrate link resiliency through the use of EAPS to maintain VoIP traffic without interruption of service in the event of link failure. 1 of 15

2 1. Introduction Resiliency and fast recovery time is often key in network infrastructure design. This is especially true in real-time applications such as VoIP. These Application Notes describe a solution using EAPS (Ethernet Automatic Protection Switching) to expedite convergence time in the case of link failure in an infrastructure supporting Avaya Communication Manager and Avaya IP Telephones. The sample network in Figure 1 shows four Extreme Networks switches interconnected in a partial mesh topology. Two EAPS Domains, userfloor1 and userfloor2, are configured. Each EAPS Domain supports users on a different Extreme Networks Alpine 3804 switch accessing Avaya Communication Manager, connected to the BlackDiamond core switch. This BlackDiamond switch is the default gateway for the network. Unlike 802.1D (Spanning Tree Protocol), EAPS convergence time is typically less than 50 milliseconds for a link failure. A common port is configured between the BlackDiamond and the BlackDiamond This port will be shared between the two EAPS rings. Since a link between the BlackDiamond and the BlackDiamond core switches is shared between two different EAPS Domains, these core switches cannot be configured as the Master of either EAPS Domain. The BlackDiamond is configured as the Controller and the BlackDiamond is configured as the Partner for the shared link. The role of the EAPS Domain Master will fall to each of the respective Alpine The BlackDiamond is configured to be the default gateway for the V172 VLAN. The following is a brief summary of considerations for configuring an EAPS Domain. Please refer to [5] for more complete information, including the configuration of Shared Port and Shared Link in EAPS. Every EAPS Domain must have one switch designated as the Master. The EAPS Domain Master tracks the status of the EAPS Domain, including link up and link down conditions. Each switch will need to designate a primary port and a secondary port for the EAPS Domain. Under normal operation, the Master will block the port designated as secondary to maintain a loop free environment. In EAPS version 2, a port can be designated as a Shared Port and Shared Link. This allows for multiple EAPS Domains to be configured on one port. A switch with a Shared Port must be configured as Transit for the EAPS Domain. One of the switches terminating the shared link is designated as a Controller while the other switch terminating the shared link is designated as a Partner. 2 of 15

3 2. Configuration Figure 1 illustrates the configuration used in these Application Notes. Avaya S8500 Media Server Avaya G650 Media Gateway C-LAN MedPro :4 2:3 2:2 Extreme Networks BlackDiamond VLAN V EAPS Controller 2:17 2:15 EAPS: Userfloor2 Master Extreme Networks Alpine 3804 Alpine-2 2:20 2:27 2:28 EAPS Domain userfloor2 Control VLAN c2 Protect VLAN V172 Shared EAPS Link 2:16 8:5 EAPS Domain userfloor1 Control VLAN c1 Protect VLAN V172 1:6 1:5 Extreme Networks Alpine 3804 Alpine-1 EAPS: Userfloor1 Master 1:1 8:17 8:6 Avaya 4620SW H.323 phone Ext EAPS Partner Avaya 4620SW H.323 phone Ext Extreme Networks BlackDiamond Figure 1: Sample Network Configuration 3 of 15

4 3. Equipment and Software Validated The following equipment and software/firmware were used for the sample configuration: Equipment Avaya S8500 Media Server with Avaya G650 Media Gateway Software/Firmware Avaya Communication Manager 3.1 (R ) Service Pack Avaya 4620SW IP Telephone 2.3 Extreme Networks BlackDiamond XOS Extreme Networks BlackDiamond XOS Extreme Networks Alpine 3804 Alpine-1 ExtremeWare Extreme Networks Alpine 3804 Alpine-2 ExtremeWare of 15

5 4. Avaya Communication Manager There is no unique configuration required in Avaya Communication Manager to support EAPS or any feature(s) mentioned in this document. For detailed information on the Installation, Maintenance, and Configuration of Avaya Communication Manager, please consult reference [1] and [2]. 5. Configure the Extreme Networks Switches The following sections describe the configuration for the different Extreme Networks Switches in the sample configuration Configure the Extreme Networks BlackDiamond This section shows the necessary steps in configuring the BlackDiamond as shown in the sample network. The BlackDiamond is configured as an EAPS Controller. Step 1. Connect to the BlackDiamond Log in using the appropriate Login ID and Password. login: password: BD # 2. Make sure the ports are not already configured. Use the show port <port> info detail command to check the current configuration for the port. BD # show port 2:15-2:17 info detail 3. Disable the uplink ports that will be used to prevent accidental broadcast storms from occurring (optional). BD # disable port 2:15-2:17 4. Create the control VLAN c1 and c2 for the two EAPS Domains, userfloor1 and userfloor2. There is no need to assign an IP address for the control VLAN. The control VLANs should also be assigned with qosprofile of QP8. This ensures that the control messages are given the highest priority through the network. Assign these control VLANs to the appropriate ports. BD # create vlan "c1" BD # configure vlan c1 tag 1172 BD # configure vlan c1 qosprofile QP8 BD # configure vlan c1 add ports 2:15-16 tagged BD # create vlan "c2" BD # configure vlan c2 tag 2172 BD # configure vlan c2 qosprofile QP8 BD # configure vlan c2 add ports 2:16-17 tagged 5 of 15

6 Step 5. Create the user VLAN. The sample configuration has only one user VLAN that is used for both EAPS Domains. BD # create vlan "V172" BD # configure vlan V172 tag 172 BD # configure vlan V172 ipaddress /24 BD # configure vlan V172 add ports 2:15-17 tagged BD # enable ipforwarding 6. Create the EAPS Domain userfloor1 and userfloor2. BD # create eaps userfloor1 BD # configure eaps userfloor1 mode transit BD # configure eaps userfloor1 primary port 2:15 BD # configure eaps userfloor1 secondary port 2:16 BD # create eaps userfloor2 BD # configure eaps userfloor2 mode transit BD # configure eaps userfloor2 primary port 2:17 BD # configure eaps userfloor2 secondary port 2:16 Note: BlackDiamond must be in transit mode because a Shared Link is configured to support multiple EAPS Domains. 7. Assign the control and protected VLAN to each EAPS Domain. BD # configure eaps userfloor1 add control vlan c1 BD # configure eaps userfloor1 add protected vlan V172 BD # configure eaps userfloor2 add control vlan c2 BD # configure eaps userfloor2 add protected vlan V Configure the shared port. BD # create eaps shared port 2:16 BD # configure eaps shared-port 2:16 mode controller BD # configure eaps shared-port 2:16 link-id 1 9. Enable EAPS and enable ports. BD # enable eaps BD # enable eaps userfloor1 BD # enable eaps userfloor2 BD # enable port 2:15-2: Save the configuration. BD # save 6 of 15

7 5.2. Configure the Extreme Networks BlackDiamond This section shows the necessary steps in configuring the BlackDiamond as shown in the sample network. The BlackDiamond is configured as an EAPS Partner. Step 1. Connect to the BlackDiamond Log in using the appropriate Login ID and Password. login: password: BD # 2. Make sure the ports are not already configured. Use the show port <port> info detail command to check the current configuration for the port. BD # show port 8:5,8:6,8:17 info detail 3. Disable the uplink ports that will be used to prevent accidental broadcast storms from occurring (optional). BD # disable port 8:5,8:6,8:17 4. Create the control VLAN c1 and c2 for the two EAPS Domains, userfloor1 and userfloor2. There is no need to assign an IP address for the control VLAN. The control VLANs should also be assigned with qosprofile of QP8. This ensures that the control messages are given the highest priority through the network. Assign these control VLANs to the appropriate ports. BD # create vlan "c1" BD # configure vlan c1 tag 1172 BD # configure vlan c1 qosprofile QP8 BD # configure vlan c1 add ports 8:5-8:6 tagged BD # create vlan "c2" BD # configure vlan c2 tag 2172 BD # configure vlan c2 qosprofile QP8 BD # configure vlan c2 add ports 8:5,8:17 tagged 5. Create the user VLAN. The sample configuration has only one user VLAN that is used for both EAPS Domains. BD # create vlan "V172" BD # configure vlan V172 tag 172 BD # configure vlan V172 add ports 8:5-8:6,8:17 tagged 7 of 15

8 Step 6. Create the EAPS Domain userfloor1 and userfloor2. BD # create eaps userfloor1 BD # configure eaps userfloor1 mode transit BD # configure eaps userfloor1 primary port 8:6 BD # configure eaps userfloor1 secondary port 8:5 BD # create eaps userfloor2 BD # configure eaps userfloor2 mode transit BD # configure eaps userfloor2 primary port 8:17 BD # configure eaps userfloor2 secondary port 8:5 Note: BlackDiamond must be in transit mode because a Shared Link is configured to support multiple EAPS Domains. 7. Assign the control and protected VLAN to each EAPS Domain. BD # configure eaps userfloor1 add control vlan c1 BD # configure eaps userfloor1 add protected vlan V172 BD # configure eaps userfloor2 add control vlan c2 BD # configure eaps userfloor2 add protected vlan V Configure the shared port. BD # create eaps shared port 8:5 BD # configure eaps shared-port 8:5 mode partner BD # configure eaps shared-port 8:5 link-id 1 9. Enable EAPS and enable ports. BD # enable eaps BD # enable eaps userfloor1 BD # enable eaps userfloor2 BD # enable port 8:5-8:6,8: Save the configuration. BD # save 5.3. Configure the Extreme Networks Alpine 3804 (Alpine-1) This section shows the necessary steps in configuring the Alpine 3804 Alpine-1 as shown in the sample network. Configure this Alpine as the Master for the userfloor1 EAPS Domain. Step 1. Connect to the Alpine Log in using the appropriate Login ID and Password. login: password: Alpine-1 # 8 of 15

9 Step 2. Make sure the ports are not already configured. Use the show port <port> info detail command to check the current configuration for the port. Alpine-1 # show port 1:5-1:6 info detail 3. Disable the uplink ports that will be used to prevent accidental broadcast storms from occurring (optional). Alpine-1 # disable port 1:5-1:6 4. Create the control VLAN c1 for the EAPS Domain userfloor1. There is no need to assign an IP address for the control VLAN. The control VLAN should also be assigned with qosprofile of QP8. This ensures that the control messages are given the highest priority through the network. Assign the control VLAN to the appropriate ports. Alpine-1 # create vlan "c1" Alpine-1 # configure vlan c1 tag 1172 Alpine-1 # configure vlan c1 qosprofile QP8 Alpine-1 # configure vlan c1 add ports 1:5-1:6 tagged 5. Create the user VLAN. The sample configuration has only one user VLAN used for both EAPS Domains. Alpine-1 # create vlan "V172" Alpine-1 # configure vlan V172 tag 172 Alpine-1 # configure vlan V172 add ports 1:5-1:6 tagged 6. Create the EAPS Domain userfloor1. Alpine-1 # create eaps userfloor1 Alpine-1 # configure eaps userfloor1 mode master Alpine-1 # configure eaps userfloor1 primary port 1:6 Alpine-1 # configure eaps userfloor1 secondary port 1:5 Note: The Alpine-1 will need to be the Master for EAPS Domain userfloor1. 7. Assign the control and protected VLAN to the EAPS Domain. Alpine-1 # configure eaps userfloor1 add control vlan c1 Alpine-1 # configure eaps userfloor1 add protected vlan V Enable EAPS and enable ports. Alpine-1 # enable eaps Alpine-1 # enable eaps userfloor1 Alpine-1 # enable port 1:5-1:6 9 of 15

10 Step 9. Save the configuration. Alpine-1 # save 5.4. Configure the Extreme Networks Alpine 3804 (Alpine-2) This section shows the necessary steps in configuring the Alpine 3804 Alpine-2 as shown in the sample network. Configure this Alpine as the Master for the userfloor2 EAPS Domain. Step 1. Connect to the Alpine Log in using the appropriate Login ID and Password. login: password: Alpine-2 # 2. Make sure the ports are not already configured. Use the show port <port> info detail command to check the current configuration for the port. Alpine-2 # show port 2:27-2:28 info detail 3. Disable the uplink ports to prevent accidental broadcast storms from occurring (optional). Alpine-2 # disable port 2:27-2:28 4. Create the control VLAN c2 for the EAPS Domain userfloor2. There is no need to assign an IP address for the control VLAN. The control VLAN should also be assigned with qosprofile of QP8. This ensures that the control messages are given the highest priority through the network. Assigned the control VLAN to the appropriate ports. Alpine-2 # create vlan "c2" Alpine-2 # configure vlan c2 tag 2172 Alpine-2 # configure vlan c2 qosprofile QP8 Alpine-2 # configure vlan c2 add ports 2:27-2:28 tagged 5. Create the user VLAN. The sample configuration has only one user VLAN used for both EAPS Domains. Alpine-2 # create vlan "V172" Alpine-2 # configure vlan V172 tag 172 Alpine-2 # configure vlan V172 add ports 2:27-2:28 tagged 10 of 15

11 Step 6. Create the EAPS Domain userfloor2. Alpine-2 # create eaps userfloor2 Alpine-2 # configure eaps userfloor2 mode master Alpine-2 # configure eaps userfloor2 primary port 2:27 Alpine-2 # configure eaps userfloor2 secondary port 2:28 Note: The Alpine-2 will need to be the Master for EAPS Domain userfloor2. 7. Assign the control and protected VLAN to the EAPS Domain. Alpine-2 # configure eaps userfloor2 add control vlan c2 Alpine-2 # configure eaps userfloor2 add protected vlan V Enable EAPS and enable ports. Alpine-2 # enable eaps Alpine-2 # enable eaps userfloor2 Alpine-2 # enable port 2:27-2:28 9. Save the configuration. Alpine-2 # save 11 of 15

12 6. Verification Steps The following steps may be used to verify the configuration. To verify that an EAPS Domain is operating correctly, use the show eaps <EAPS Domain> detail command. The following is an example command output from the Alpine-2 switch in the sample network. Make sue the following fields are as shown for the Extreme Networks switch configured as Master for the EAPS Domain. State: Complete A different state may indicate a link down condition. Enabled: Yes Ensure the EAPS Domain is enabled. Mode: Master Indicates the EAPS Domain role Primary Port: Up The Primary port should be in the Up state. Secondary Port: Blocked Secondary port is always set to Blocked under normal conditions. Alpine3804:4 # show eaps userfloor2 detail Name: "userfloor2" (instance=0) State: Complete [Running: Yes] Enabled: Yes Mode: Master Primary port: 2:27 Port status: Up Tag status: Tagged Secondary port: 2:28 Port status: Blocked Tag status: Tagged Hello Timer interval: 1 sec Fail Timer interval: 3 sec Fail timer expiry action: Send alert Last update: From Master Id 00:04:96:1A:E9:60, at Thu Apr 27 11:16: EAPS Domain has following Controller Vlan: Vlan Name VID QosProfile "c2" 2172 QP8 EAPS Domain has following Protected Vlan(s): Vlan Name VID QosProfile "v172" 0172 QP1 Number of Protected Vlans: 1 12 of 15

13 For Extreme Networks switches configured as EAPS Domain Transit, the same show eaps <EAPS Domain command should display the following information. Following is the show eaps output from the BlackDiamond switch in the sample network. Make sure the following fields are as shown for the Extreme Networks switch configured as Transit for the EAPS Domain. Enabled: Yes Ensure the EAPS Domain is enabled Mode: Transit Indicates the EAPS Domain role Primary Port: Up The Primary port should be in the Up state. Secondary Port: Up The secondary port should be in the Up state. BD # show eaps userfloor2 Name: userfloor2 State: Links-Up Running: Yes Enabled: Yes Mode: Transit Primary port: 2:17 Port status: Up Tag status: Tagged Secondary port: 2:16 Port status: Up Tag status: Tagged Hello timer interval: 1 sec Fail timer interval: 3 sec Preforwarding Timer interval: 6 sec Last update: From Master Id 00:04:96:1a:e9:60, at Thu Apr 27 18:06: EAPS Domain has following Controller Vlan: Vlan Name VID c EAPS Domain has following Protected Vlan(s): Vlan Name VID v Number of Protected Vlans: 1 7. Conclusion These Application Notes have described the administration steps required to configure multiple EAPS Domains with a shared link in a partial mesh topology to support Avaya Communication Manager and Avaya IP Telephones. Avaya IP Telephony was implemented in this configuration to demonstrate link resiliency through the use of EAPS to maintain VoIP traffic without interruption of service in the event of link failure. To gauge the effectiveness of EAPS rapid convergence on VoIP traffic, different links, including the Shared Link, were disconnected and reconnected after a call was established between Avaya IP Telephones attached to each Alpine switch. Interruption to an ongoing phone conversation was hardly noticeable, and of sub-second in duration. The rapid convergence using EAPS is a dramatic improvement compared with a network running Spanning Tree Protocol. 13 of 15

14 8. Additional References Product documentation for Avaya products may be found at Product documentation for Extreme Networks products may be found at [1] Administrator Guide for Avaya Communication Manager, Doc # , Issue 1, February 2006 [2] Avaya Communication Manager Advanced Administration Quick Reference, Doc # , Issue 2, June 2005 Release 3.0 [3] Administration for Network Connectivity for Avaya Communication Manager, Doc # , Issue 6, May 2003 [4] Avaya Application Solutions: IP Telephony Deployment Guide, Doc# , Issue 4.3, February 2006 [5] ExtremeWare XOS Concepts Guide, Software Version 11.4, Part Number: Rev 01, March 2006 [6] ExtremeWare XOS Command Reference Guide, Software Version 11.4, Part Number: Rev 01, March 2006 [7] ExtremeWare CommandReference Guide, Software Version 7.5, Part Number: Rev. 01, October of 15

15 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 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 15 of 15