Application Notes for Extreme Networks Alpine, BlackDiamond, and Summit Series Switches with Avaya Communication Manager - Issue 1.

Transcription

1 Avaya Solution & Interoperability Test Lab Application Notes for Extreme Networks Alpine, BlackDiamond, and Summit Series Switches with Avaya Communication Manager - Issue 1.0 Abstract These Application Notes present a sample configuration for running Avaya Communication Manager in a network comprised of Extreme Networks Alpine 3808, BlackDiamond 10808, Summit 200, Summit , and Summit 400 switches. The Avaya Media Servers and Media Gateways used in the compliance-tested configuration include the Avaya S8500 Media Server, Avaya G650 Media Gateway, and Avaya G350 Media Gateway. During compliance testing, phone calls were successfully completed with good voice quality over the Extreme Networks infrastructure under various network conditions, including the presence of competing low priority data traffic. Information in these Application Notes has been obtained through compliance testing and additional technical discussions. Testing was conducted via the DeveloperConnection Program at the Avaya Solution and Interoperability Test Lab. 1 of 25

2 1. Introduction These Application Notes describe a compliance-tested configuration comprised of Avaya IP telephony products operating in a Layer 2/3 infrastructure formed mainly by Extreme Networks switches. Virtual LANs (VLANs) and Quality of Service (QoS) techniques were implemented to optimize Voice over IP (VoIP) performance over the Layer 2/3 infrastructure. Figure 1 shows a sample network configuration consisting of an Avaya S8500 Media Server, two Avaya G650 Media Gateways, an Avaya G350 Media Gateway, Avaya IP and Digital Telephones, Avaya IP Softphones, an Extreme Networks Alpine 3808 Switch, an Extreme Networks BlackDiamond Switch, an Extreme Networks Summit 200 Switch, an Extreme Networks Summit Switch, an Extreme Networks Summit 400 Switch, and PCs. Note that the solution described herein is also extensible to other Avaya Media Servers and Media Gateways. The campus network illustrated is divided into three sites with a 10 Gbps link connecting Site A and Site B, and a 1 Gbps link connecting Site A and Site C. The Extreme Networks switches and the Avaya G350 provide the Layer 2 and Layer 3 switching and routing infrastructure. The Alpine 3808, Summit 300, and G350 perform Layer 2 switching in Site A, Site B, and Site C, respectively. The BlackDiamond 10808, Summit 400, and Summit 200 perform intra-site routing within Site A, Site B, and Site C, respectively, as well as inter-site routing. The two G650 Media Gateways and the G350 Media Gateway are controlled by the S8500 Media Server and provide the TDM-IP conversion necessary for transporting calls between non- IP devices over an IP network. The Avaya IP Telephones in all three sites obtain IP configuration from the DHCP/TFTP server and register with Avaya Communication Manager (running on the Avaya S8500 Media Server) via the C-LAN boards in the Avaya G650 Media Gateways. The Avaya IP Softphones utilize the IP configuration of the computers on which they reside and register with Avaya Communication Manager in the same manner. 2 of 25

3 CAMPUS SITE A: MAIN SITE SITE B PC VLAN 11 VLANs 11: /24 12: /24 13: /24 Avaya IP Softphone Ext VLAN 11 Avaya G650 Media Gateway IPSI IP Addr: C-LAN IP Addr: MEDPRO IP Addr: VLAN 22 VLANs 21: /24 22: /24 23: /24 Avaya 6424D+M Digital Phone Ext G Avaya 4630SW IP Phone Ext VLAN 13 Extreme Networks Summit 400 Extreme Networks Summit Avaya 4620SW IP Phone Ext VLAN 13 Extreme Networks Alpine G 10 G PC VLAN 21 SITE C Avaya 4610SW IP Phone Ext VLAN 23 Avaya IP Softphone Ext VLAN 21 VLANs 31: /24 32: /24 33: /24 DHCP/FTP Server IP Addr: VLAN 11 PC VLAN 31 Avaya S8500 Media Server IP Addr: VLAN 12 Extreme Networks BlackDiamond Avaya IP Softphone Ext VLAN 31 Avaya 6408D+ Digital Phone Ext G Avaya 4602SW IP Phone Ext VLAN 33 Avaya 6424D+M Digital Phone Ext Avaya G650 Media Gateway IPSI IP Addr: C-LAN IP Addr: MEDPRO IP Addr: VLAN 12 Extreme Networks Summit M Avaya G350 Media Gateway IP Addr: VLAN 32 Figure 1: Sample Network Configuration 3 of 25

4 2. Equipment and Software Validated The following equipment and software/firmware were used for the sample configuration provided: Equipment Software/Firmware Avaya S8500 Media Server ACM 2.1 (R012x ) Avaya G650 Media Gateway - TN2312BP IPSI 9 TN799DP C-LAN 11 TN2302AP MedPro 92 Avaya G350 Media Gateway Avaya 4602SW IP Telephone Avaya 4610SW IP Telephone 2.1 Avaya 4620SW IP Telephone 2.1 Avaya 4630SW IP Telephone Avaya 6408D+ Digital Telephone - Avaya 6416D+M Digital Telephone - Avaya 6424D+M Digital Telephone - Avaya IP Softphone running on Windows XP SP1 5.1 laptop computer Extreme Networks BlackDiamond ExtremeWare XOS Inserted modules: - MSM (2 modules) - 10G6X G60T G60X G1010 Extreme Networks Alpine 3808 ExtremeWare Build 33 Inserted modules: - SMMi GM-4Xi GM-4Ti FM-32Ti FM-32Pi Extreme Networks Summit 200 ExtremeWare 7.1e.1 Build 5 Extreme Networks Summit ExtremeWare 6.2a Build 422 Extreme Networks Summit 400 ExtremeWare 7.2e.1 Build 10 Microsoft DHCP Server running on Windows Advanced Server SP4 computer SolarWinds.Net TFTP Server running on Windows 2000 Advanced Server SP4 computer PC Windows 2000 Professional SP4 4 of 25

5 3. QoS Overview 3.1. Avaya QoS All Avaya VoIP components (Media Servers, Media Gateways, IP telephones, and IP Softphones) support 802.1p/Q priority tagging and DiffServ. When 802.1p/Q priority tagging is enabled, the S8500 Media Server and IPSI boards of the G650 Media Gateways transmit priority tagged frames on VLAN 0. However, Extreme Networks switches treat VLAN 0 frames as clear traffic and thus ignore the priority values in the VLAN 0 frames. Therefore, the Extreme Networks switches must be configured to classify and queue packets based on the packets DiffServ values (enable diffserv examination in Extreme Networks terminology) on the ports connected to the S8500 Media Server and the IPSI boards of the G650 Media Gateways Extreme Networks QoS Extreme Networks switches can classify and forward ingress traffic based on 802.1p or DiffServ. By default, Extreme Networks switches examine the 802.1p priorities of ingress packets and place them in corresponding hardware queues on the egress port. The Alpine 3808 and BlackDiamond have eight hardware queues on each physical port, whereas the Summit 200, , and 400 have four hardware queues on each physical port. If DiffServ examination is enabled, then the ingress packets DiffServ values determine which hardware queues the packets are placed in. For example, by default the DiffServ values 0 through 7 equate to 802.1p priority 0, so a packet with a DiffServ value of 5 would be placed in the same hardware queue as a packet with 802.1p priority 0. Similarly, DiffServ values 8 through 15 equate to 802.1p priority 1, DiffServ values 16 through 23 equate to 802.1p priority 2, and so on p and DiffServ examination is configurable on a per port basis. Extreme Networks switches can also classify ingress traffic according to user-defined traffic groupings, which are defined by any combination of parameters such as IP-based information, MAC information, physical source port, and VLAN. QoS profiles may be assigned to traffic groupings to determine their forwarding treatment. For example, an Extreme Networks switch can identify all ingress packets that match a particular traffic grouping s parameters and forward them according to the behavior defined in a QoS profile rather than the packets 802.1p priorities or DiffServ values. Extreme Networks switches have eight default QoS profiles, numbered QP1 through QP8, and each QoS profile includes a priority and minimum and maximum bandwidth utilizations (by default 0% and 100% respectively). QP1 has a default priority of 0, QP2 has a default priority of 1, and so on. On egress, the Alpine 3808 and BlackDiamond can preserve or replace 802.1p priorities and Differentiated Services Code Point (DSCP) values. If 802.1p replacement is enabled, the transmitted 802.1p priority is determined by the hardware queue used to transmit the packet. Thus, on a tagged link, 802.1p replacement provides a convenient way to request the same priority treatment from the next switch, independent of the classification method used in the transmitting switch. The Alpine 3808 and BlackDiamond can also be configured to remark the DSCP value prior to transmission. The remarked DSCP value is determined by the 802.1p priority, which in turn is determined by the hardware queue used to transmit the packet. 5 of 25

6 Thus, to remark egress DSCP values on a port, 802.1p replacement and DSCP replacement must both be enabled on the port. With this approach, DSCP remarking results in hardware queue 0 transmitting DSCP 0, hardware queue 1 transmitting DSCP 8, and so on. DSCP replacement thus provides a convenient way to request the same priority treatment from a next hop that observes DiffServ, independent of the classification scheme used by the transmitting switch. None of the foregoing QoS operations impact switch performance QoS Configuration Employed In order to simplify QoS configuration, DiffServ examination was enabled on all ports on the Extreme Networks switches. This means that the QoS applied in forwarding packets was based only on DSCP values. Table 1 below summarizes the QoS configuration used for the Avaya equipment and the Extreme Networks switch ports connected to them during compliance testing. The detailed commands to implement this configuration, as well as QoS for switch ports connected to other switch ports, are provided in the forthcoming sections. Avaya Equipment 802.1p/Q and DiffServ configuration IP Telephone - tagged with VLAN ID received from the DHCP server p priority and DiffServ value obtained from IP network region configured on Avaya Communication Manager, though 802.1p priority not relevant due to enabling of DiffServ examination. PC running IP Softphone - no 802.1p/Q tagging. - DiffServ value obtained from IP network region configured on Avaya Communication Manager. IPSI on Avaya G650 Media - DiffServ value set to 48 Gateway via IPSI administration (no 802.1p/Q tagging) Extreme Networks Switch Configuration - tagged VLAN and DiffServ examination enabled on port connected to IP phone; also untagged VLAN on port if PC is attached to phone. - untagged VLAN and DiffServ examination enabled on port connected to PC. - untagged VLAN and DiffServ examination enabled on port connected to IPSI. 6 of 25

7 Avaya Equipment 802.1p/Q and DiffServ configuration C-LAN and MedPro on Avaya p priority and G650 Media Gateway DiffServ value obtained from IP network region configured on Avaya Communication Manager. Avaya S8500 Media Server p priority and DiffServ value set in ipserver-interface form. Avaya G350 Media Gateway p priority and DiffServ value obtained from IP network region configured on Avaya Communication Manager. Extreme Networks Switch Configuration - untagged VLAN and DiffServ examination enabled on ports connected to C-LAN and MedPro. - untagged VLAN and DiffServ examination enabled on port connected to S8500 Media Server. - tagged VLAN and DiffServ examination enabled on port connected to G350 Media Gateway. Table 1: QoS and Port Configuration Summary for Avaya-Extreme Connections 4. Configure the Avaya S8500 Media Server 4.1. Ethernet Interfaces The S8500 Media Server contains at least two Ethernet interfaces: a Services port solely for configuring the Media Server and a Control Network port for communications between the S8500 Media Server and IPSI circuit packs in Avaya Media Gateways. The Control Network port may also be used for connection to the network. The IP address and subnet mask of the Services port is fixed at and , respectively, while those of the Control Network port are configurable. To configure the S8500 Media Server, connect a computer to the Services port with a crossover Ethernet cable. Configure the computer with an IP address of and subnet mask of Launch a web browser, with proxies turned off, and connect to the URL Log in with the appropriate credentials and click on Launch Maintenance Web Interface to invoke the Maintenance Web Pages. In the left panel of the Maintenance Web Pages, click on Configure Server and follow the instructions to configure the Ethernet interfaces. In Figure 2 below, Ethernet 0: Control Network A is assigned an IP address of , default gateway of , and subnet mask of of 25

8 4.2. Add Avaya G650 Media Gateways Using the System Access Terminal (SAT), globally enable IPSI control by entering the command change system-parameters ipserver-interface and setting IPSI Control of Port Networks to enabled. change system-parameters ipserver-interface Page 1 of 1 IP SERVER INTERFACE (IPSI) SYSTEM PARAMETERS SERVER INFORMATION OPTIONS IPSI Host Name Prefix: Primary Control Subnet Address:... Secondary Control Subnet Address:... Switch Identifier: A IPSI Control of Port Networks: enabled 8 of 25

9 Enter the command add cabinet N (where N is a number between 1 and 64) for each G650 Media Gateway to be controlled by the S8500 Media Server. In the add cabinet form, set Cabinet Layout to G650-rack-mount-stack. add cabinet 1 Page 1 of 1 CABINET CABINET DESCRIPTION Cabinet: 1 Cabinet Layout: G650-rack-mount-stack Cabinet Type: expansion-portnetwork Location: 1 Rack: Room: Floor: Building: CARRIER DESCRIPTION Carrier Carrier Type Number E D C B A not-used not-used not-used not-used G650-port add cabinet 2 Page 1 of 1 CABINET CABINET DESCRIPTION Cabinet: 2 Cabinet Layout: G650-rack-mount-stack Cabinet Type: expansion-portnetwork Location: 1 Rack: Room: Floor: Building: CARRIER DESCRIPTION Carrier Carrier Type Number E D C B A not-used not-used not-used not-used G650-port 9 of 25

10 For each G650 Media Gateway to be controlled by the S8500 Media Server, enter the command add ipserver-interface N (where N identifies the cabinet number). In the add ipserverinterface form, set Host to the IPSI IP address and configure QoS parameters for the IPSI board as desired. add ipserver-interface 1 IP SERVER INTERFACE (IPSI) ADMINISTRATION - PORT NETWORK 1 IP Control? y Socket Encryption? y Enable QoS? y Primary IPSI QoS Parameters Loca tion: 1A01 Call Control 802.1p: 6 Host: Call Control DiffServ: 48 DHCP ID: ipsi-a01a add ipserver-interface 2 IP SERVER INTERFACE (IPSI) ADMINISTRATION - PORT NETWORK 2 IP Control? y Socket Encryption? y Enable QoS? y Primary IPSI QoS Parameters Location: 2A01 Call Control 802.1p: 6 Host: Call Control DiffServ: 48 DHCP ID: ipsi-a02a Enter the command change node-names ip and enter names and IP addresses for the C-LAN and MedPro boards of the G650 media gateways. The node names entered in the change nodenames ip form will be used as aliases in other forms. change node-names ip Page 1 of 1 IP NODE NAMES Name IP Address Name IP Address CLAN-1A CLAN-2A MEDPRO-1A MEDPRO-2A default procr For each C-LAN and MedPro board, enter the command add ip-interface UUCSS (where UUCSS is a board location). In the add ip-interface form, specify the Node Name, Subnet Mask, and Gateway Address, and set Enable Ethernet Port to y. The board locations of the C-LAN and MedPro boards can be obtained from the list configuration all form. 10 of 25

11 add ip-interface 01A02 Page 1 of 1 IP INTERFACES Type: C-LAN Slot: 01A02 Code/Suffix: TN799 D Node Name: CLAN-1A02 IP Address: Subnet Mask: Gateway Address: Enable Ethernet Port? y Network Region: 1 VLAN: n ETHERNET OPTIONS Auto? y Number of CLAN Sockets Before Warning: 400 add ip-interface 02A02 Page 1 of 1 IP INTERFACES Type: C-LAN Slot: 01A02 Code/Suffix: TN799 D Node Name: CLAN-2A02 IP Address: Subnet Mask: Gateway Address: Enable Ethernet Port? y Network Region: 1 VLAN: n ETHERNET OPTIONS Auto? y Number of CLAN Sockets Before Warning: 400 add ip-interface 01A03 Page 1 of 1 IP INTERFACES Type: MEDPRO Slot: 01A03 Code/Suffix: TN2302 Node Name: MEDPRO-1A03 IP Address: Subnet Mask: Gateway Address: Enable Ethernet Port? y Network Region: 1 VLAN: n ETHERNET OPTIONS Auto? y 11 of 25

12 add ip-interface 02A03 Page 1 of 1 IP INTERFACES Type: MEDPRO Slot: 02A03 Code/Suffix: TN2302 Node Name: MEDPRO-2A03 IP Address: Subnet Mask: Gateway Address: Enable Ethernet Port? y Network Region: 1 VLAN: n ETHERNET OPTIONS Auto? y For each C-LAN board, enter the command add data-module nnnnn (where nnnnn is an extension whose length and value depends on the provisioned dial plan; a sample dial plan is provided on the next page). In the add data-module form, set Type to ethernet, Port to the C- LAN board number appended with 17, and Link to a number between 1 and 99. add data-module Page 1 of 1 DATA MODULE Data Extension: Type: ethernet Port: 01A0217 Link: 1 Name: CLAN-1A02 Network uses 1's for Broadcast Addresses? y add data-module Page 1 of 1 DATA MODULE Data Extension: Type: ethernet Port: 02A0217 Link: 2 Name: CLAN-2A02 Network uses 1's for Broadcast Addresses? y 12 of 25

13 display dialplan analysis Page 1 of 12 DIAL PLAN ANALYSIS TABLE Percent Full: 1 Dialed Total Call Dialed Total Call Dialed Total Call String Length Type String Length Type String Length Type 1 3 dac 2 5 ext 5 5 ext 6 5 ext 7 5 aar 4.3. Add the Avaya G350 Media Gateway To add a G350 Media Gateway, enter the command add media-gateway M (where M is a number between 1 and 250). In the add media-gateway form, set Type to g350, enter the Serial No of the G350 Media Gateway, and specify the Network Region (to be defined in section 7.1). add media-gateway 1 Page 1 of 1 MEDIA GATEWAY Number: 1 IP Address: Type: g350 FW Version/HW Vintage: Name: G350 MAC Address: Serial No: 03IS Encrypt Link? y Network Region: 1 Location: 1 Registered? n Controller IP Address: Site Data: Slot Module Type Name V1: V2: V3: V4: V5: V6: V7: V8: V9: 5. Configure the Avaya G650 and G350 Media Gateways 5.1. Avaya G650 Media Gateways The S8500 Media Server controls the G650 Media Gateways through their respective IPSI boards. To configure the IPSI board on a G650 Media Gateway, connect a computer with an IP address of and subnet mask of to the Services port of the IPSI board and telnet to Log in with the appropriate credentials and configure the IP address, subnet mask, default gateway, and QoS parameters for the IPSI board, as illustrated in the commands that follow. 13 of 25

14 TN2312 IPSI IP Admin Utility Copyright Avaya Inc, 2003, All Rights Reserved [IPSI]: ipsilogin Login: craft Password: [IPADMIN]: set control interface WARNING! The control network interface IP operating parameters will be updated upon exiting IPADMIN! See the "set control interface" command help and the "show route" command output (and command help) before AND after changing any IP operating parameters. It is highly recommended that you reset the IPSI when done, and run the "show route" command again to insure the routing table is exactly as you expect it to be. [IPADMIN]: set control gateway WARNING! The control network interface IP operating parameters will be updated upon exiting IPADMIN! See the "set control interface" command help and the "show route" command output (and command help) before AND after changing any IP operating parameters. It is highly recommended that you reset the IPSI when done, and run the "show route" command again to insure the routing table is exactly as you expect it to be. [IPADMIN]: set vlan tag off [IPADMIN]: set diffserv 48 Note: The above IPSI commands take effect after the user logs out. 14 of 25

15 TN2312 IPSI IP Admin Utility Copyright Avaya Inc, 2003, All Rights Reserved [IPSI]: ipsilogin Login: craft Password: [IPADMIN]: set control interface WARNING! The control network interface IP operating parameters will be updated upon exiting IPADMIN! See the "set control interface" command help and the "show route" command output (and command help) before AND after changing any IP operating parameters. It is highly recommended that you reset the IPSI when done, and run the "show route" command again to insure the routing table is exactly as you expect it to be. [IPADMIN]: set control gateway WARNING! The control network interface IP operating parameters will be updated upon exiting IPADMIN! See the "set control interface" command help and the "show route" command output (and command help) before AND after changing any IP operating parameters. It is highly recommended that you reset the IPSI when done, and run the "show route" command again to insure the routing table is exactly as you expect it to be. [IPADMIN]: set vlan tag off [IPADMIN]: set diffserv 48 Note: The above IPSI commands take effect after the user logs out Avaya G350 Media Gateway The S8500 Media Server controls the G350 Media Gateway through its Primary Management Interface (PMI). The following commands create and configure VLAN 32 and assign it as the PMI on the G350 Media Gateway. Note that the??? appears in the command prompt until the G350 Media Gateway registers with an Avaya Media Server. G350-???(super)# set vlan 32 G350-???(super)# interface Vlan 32 G350-???(super-if:Vlan 32)# ip address G350-???(super-if:Vlan 32)# pmi G350-???(super-if:Vlan 32)# exit G350-???(super)# ip default-gateway of 25

16 The G350 Media Gateway maintains a statically provisioned list of media gateway controllers (media servers). The following command provisions the IP address of the G650 Media Gateway C-LAN board in Site A as the controller: G350-???(super)# set mgc list Configure the Layer 2 and Layer 3 Infrastructure In the sample configuration of Figure 1, Extreme Networks switches and the Avaya G350 Media Gateway provide the Layer 2 and Layer 3 switching and routing infrastructure. The Alpine 3808, Summit , and G350 Media Gateway perform Layer 2 switching in Site A, Site B, and Site C, respectively. The BlackDiamond 10808, Summit 400, and Summit 200 perform intra-site routing within Site A, Site B, and Site C, respectively, as well as inter-site routing. Note: This section contains examples where ports are configured with untagged VLANs. It is assumed that the Default VLAN has been previously removed from the ports. To remove the Default VLAN from one or more ports, use the command configure vlan Default delete ports <portlist> Extreme Networks Alpine 3808 As mentioned above, the Alpine 3808 is used for Layer 2 switching only in Site A. The following commands create and configure two VLANs on the Alpine 3808: vlan11 for the PCs, including the PC running the IP Softphone application, and vlan13 for the IP telephones. vlan11 is configured as an untagged VLAN on the ports (5:1-5:3) that may connect to PCs while vlan13 is configured as a tagged VLAN on the ports (5:1-5:2) that may connect to IP telephones. Note that in this example, ports 5:1 and 5:2 are both configured with vlan11 and vlan13 ; this enables the option of attaching a PC directly to an IP telephone that is connected to those ports. create vlan vlan11 configure vlan vlan11 tag 11 configure vlan vlan11 add ports 5:1-5:3 untagged create vlan vlan13 configure vlan vlan13 tag 13 configure vlan vlan13 add ports 5:1-5:2 tagged The following commands configure vlan11 and vlan13 as tagged VLANs on the port (2:1) connected to the BlackDiamond configure vlan vlan11 add ports 2:1 tagged configure vlan vlan13 add ports 2:1 tagged 16 of 25

17 6.2. Extreme Networks BlackDiamond The following commands create and configure VLANs vlan11 and vlan13 as tagged VLANs on the port (3:31) connected to the Alpine Note that vlan11 and vlan13 correspond to the VLANs with tags 11 and 13, respectively, configured on the Alpine The last command configures vlan11 as an untagged VLAN on the port (3:7) connected to the DHCP server. create vlan vlan11 create vlan vlan13 configure vlan vlan11 tag 11 configure vlan vlan13 tag 13 configure vlan vlan11 ipaddress configure vlan vlan13 ipaddress configure vlan vlan11 add ports 3:31 tagged configure vlan vlan13 add ports 3:31 tagged configure vlan vlan11 add ports 3:7 untagged The following commands create and configure an untagged VLAN vlan12 on the ports (3:1-3:4) connected to the S8500 Media Server and the G650 Media Gateway s IPSI, C-LAN, and MedPro boards in Site A. create vlan vlan12 configure vlan vlan12 tag 12 configure vlan vlan12 ipaddress configure vlan vlan12 add ports 3:1-3:4 untagged The following commands create and configure a tagged VLAN vlan122 on the port (1:1) connected to the Summit 400. create vlan vlan122 configure vlan vlan122 tag 122 configure vlan vlan122 ipaddress configure vlan vlan122 add ports 1:1 tagged The following commands create and configure a tagged VLAN vlan123 on the port (3:60) connected to the Summit 200. create vlan vlan123 configure vlan vlan123 tag 123 configure vlan vlan123 ipaddress configure vlan vlan123 add ports 3:60 tagged The following commands create static routes to Site B and Site C with the Summit 400 and Summit 200 as the next hops, respectively. configure iproute add configure iproute add of 25

18 The following commands enable IP forwarding on the VLANs. IP forwarding allows packets to be routed to/from the VLANs. enable ipforwarding vlan11 enable ipforwarding vlan12 enable ipforwarding vlan13 enable ipforwarding vlan122 enable ipforwarding vlan Extreme Networks Summit As mentioned above, the Summit is used for Layer 2 switching only in Site B. The following commands create and configure two VLANs on the Summit : vlan21 for the PCs, including the PC running the IP Softphone application, and vlan23 for the IP telephones. vlan21 is configured as an untagged VLAN on the ports (1:1 and 1:3) that may connect to PCs while vlan23 is configured as a tagged VLAN on the port (1:1) that may connect to an IP telephone. Note that in this example, port 1:1 is configured with both vlan21 and vlan23 ; this enables the option of attaching a PC directly to an IP telephone that is physically connected to that port. create vlan vlan21 configure vlan vlan21 tag 21 configure vlan vlan21 add ports 1:1,1:3 untagged create vlan vlan23 configure vlan vlan23 tag 23 configure vlan vlan23 add ports 1:1 tagged The following commands configure vlan21 and vlan23 as tagged VLANs on the port (1:49) connected to the Summit 400. configure vlan vlan21 add ports 1:49 tagged configure vlan vlan23 add ports 1:49 tagged 6.4. Extreme Networks Summit 400 The following commands create and configure VLANs vlan21 and vlan23 as tagged VLANs on the port (48) connected to the Summit Note that vlan21 and vlan23 correspond to the VLANs with tags 21 and 23, respectively, configured on the Summit create vlan vlan21 create vlan vlan23 configure vlan vlan21 tag 21 configure vlan vlan23 tag 23 configure vlan vlan21 ipaddress configure vlan vlan23 ipaddress configure vlan vlan21 add ports 48 tagged configure vlan vlan23 add ports 48 tagged 18 of 25

19 The following commands create and configure an untagged VLAN vlan22 on the ports (1,3, and 5) connected to the G650 Media Gateway s IPSI, C-LAN, and MedPro boards in Site B. create vlan vlan22 configure vlan vlan22 tag 22 configure vlan vlan22 ipaddress configure vlan vlan22 add ports 1,3,5 untagged The following commands create and configure a tagged VLAN vlan122 on the port (49) connected to the BlackDiamond create vlan vlan122 configure vlan vlan122 tag 122 configure vlan vlan122 ipaddress configure vlan vlan122 add port 49 tagged The following commands create static routes to Site A and Site C with the BlackDiamond as the next hop. configure iproute add configure iproute add The following commands enable IP forwarding on the VLANs. enable ipforwarding vlan21 enable ipforwarding vlan22 enable ipforwarding vlan23 enable ipforwarding vlan Avaya G350 Media Gateway As mentioned above, the G350 Media Gateway performs Layer 2 switching in Site C. The following commands create and configure two additional VLANs (VLAN 32 was created earlier in Section 5.2) on the G350 Media Gateway: VLAN 31 for the PCs, including the PC running the IP Softphone application, and VLAN 33 for the IP telephones. VLAN 31 is configured as an untagged VLAN on the ports (6/2 and 6/3) that may connect to PCs while VLAN 33 is configured as a tagged VLAN on the ports (6/2) that may connect to IP telephones. Note that in this example, port 6/2 is configured with both VLAN 31 and VLAN 33; this enables the option of attaching a PC directly to an IP telephone that is physically connected to that port. G (super)# set vlan 31 G (super)# set vlan 33 G (super)# set port vlan 31 6/2-3 G (super)# set port static-vlan 6/2 33 G (super)# set trunk 6/2 off G (super)# set trunk 6/3 off G (super)# set port vlan-binding-mode 6/2-3 static 19 of 25

20 The following commands configure the port (6/1) connected to the Summit 200 as an 802.1Q trunk on and bind VLANs 31, 32, and 33 to that port. G (super)# set trunk 6/1 dot1q G (super)# set port vlan 31 6/1 G (super)# set port static-vlan 6/1 32 G (super)# set port static-vlan 6/1 33 G (super)# set port vlan-binding-mode 6/1 static 6.6. Extreme Networks Summit 200 The following commands create and configure VLANs vlan31, vlan32, and vlan33 as tagged VLANs on the port (1) connected to the G350 Media Gateway. Note that vlan31, vlan32, and vlan33 correspond to the VLANs with tags 31, 32 and 33, respectively, configured on the G350 Media Gateway. create vlan vlan31 create vlan vlan32 create vlan vlan33 configure vlan vlan31 tag 31 configure vlan vlan32 tag 32 configure vlan vlan33 tag 33 configure vlan vlan31 ipaddress configure vlan vlan32 ipaddress configure vlan vlan33 ipaddress configure vlan vlan31 add ports 1 tagged configure vlan vlan32 add ports 1 tagged configure vlan vlan33 add ports 1 tagged The following commands create and configure a tagged VLAN vlan123 on the port (49) connected to the BlackDiamond create vlan vlan123 configure vlan vlan123 tag 123 configure vlan vlan122 ipaddress configure vlan vlan123 add ports 49 tagged The following commands create static routes to Site A and Site B with the BlackDiamond as the next hop. configure iproute add configure iproute add The following commands enable IP forwarding on the VLANs. enable ipforwarding vlan31 enable ipforwarding vlan32 enable ipforwarding vlan33 enable ipforwarding vlan of 25

21 7. QoS Configuration 7.1. Avaya Communication Manager Each Avaya VoIP component is assigned to an IP network region. An IP network region defines the IP and QoS parameters for the region, as well as the codecs used within the region and between region pairs. G.711 is typically used to optimize voice quality for calls on high bandwidth paths, i.e., within a LAN or region, while G.729 is typically used to conserve bandwidth for calls on low bandwidth paths, i.e. on WAN links or between region pairs. Since the bandwidths of the inter-site links in the compliance-tested configuration were large (at least 1 Gbps), all Avaya VoIP components were assigned to a single IP network region. However, both G.711 and G.729 codecs were employed and verified during compliance testing. Using the SAT, enter the command change ip-network-region M (where M is a number from 1 to 250) to configure an IP network region. The following two pages of the change ip-networkregion form illustrate the IP, QoS, and codec configuration on IP network region 1. Note that enabling IP-IP Direct Audio allows RTP audio paths to be established directly between IP telephones, thereby reducing consumption of MedPro resources. change ip-network-region 1 Page 1 of 19 IP NETWORK REGION Region: 1 Location: Home Domain: Name: Intra-region IP-IP Direct Audio: yes AUDIO PARAMETERS Inter-region IP-IP Direct Audio: yes Codec Set: 1 IP Audio Hairpinning? y UDP Port Min: 2048 UDP Port Max: 3028 RTCP Reporting Enabled? y RTCP MONITOR SERVER PARAMETERS DIFFSERV/TOS PARAMETERS Use Default Server Parameters? y Call Control PHB Value: 48 Audio PHB Value: P/Q PARAMETERS Call Control 802.1p Priority: 6 Audio 802.1p Priority: 6 AUDIO RESOURCE RESERVATION PARAMETERS H.323 IP ENDPOINTS RSVP Enabled? n H.323 Link Bounce Recovery? y Idle Traffic Interval (sec): 20 Keep-Alive Interval (sec): 5 Keep-Alive Count: 5 21 of 25

22 change ip-network-region 1 Page 3 of 19 Inter Network Region Connection Management src dst codec direct Dynamic CAC rgn rgn set WAN WAN-BW-limits Intervening-regions Gateway Extreme Networks Switches Enter the command enable diffserv examination ports all on the Alpine 3808, BlackDiamond 10808, Summit 200, Summit , and Summit 400 to enable DiffServ examination on their respective ports. 8. Interoperability Compliance Testing The interoperability compliance testing focused on verifying connectivity and infrastructure compatibility as well as QoS in a converged voice/data network comprised of Avaya and Extreme Networks products General Test Approach The general approach for connectivity and infrastructure compatibility testing was to place phone calls of various characteristics (i.e., different codecs, two and multi-party calls, different phone types, etc.) across the converged infrastructure and verify their voice quality. The general approach for QoS testing was to overload infrastructure links with competing data traffic and verify QoS classification and treatment when the data traffic was configured with lower 802.1p priorities and DiffServ values than the Avaya VoIP traffic Test Results All test cases completed successfully. For connectivity and infrastructure compatibility testing, the phone call characteristics exercised included: Codec (G.711 and G.729) Silence suppression (on and off) Calls between IP telephones, IP Softphones, and Digital phones Calls to/from IP telephones with and without attached PCs 4-party conference calls VLANs DHCP (IP telephones obtain IP address and call server information from a DHCP server) DTMF tone transport (in-band and out-of-band) 22 of 25

23 Gigabit Ethernet media (copper and fiber) For QoS testing, phone calls were successfully completed with good voice quality when competing low priority data traffic was transmitted over infrastructure links at rates equal and greater than the line rates. 9. Verification Steps The following steps may be used to verify the configuration: 1. From each subnet/vlan, ping IP interfaces (Avaya S8500 Media Server, IPSI, C-LAN and MedPro boards on the Avaya G650 Media Gateways, Avaya G350 Media Gateway, Avaya IP Telephones, PCs, etc.) and verify connectivity. 2. Verify that Avaya Communication Manager running on the Avaya S8500 Media Server recognizes the Avaya G650 Media Gateways (use the SAT command status portnetwork). 3. Verify that the Avaya G350 Media Gateway is registered with Avaya Communication Manager (use the SAT command display media-gateway). 4. Verify that all Avaya IP telephones and softphones are registered with Avaya Communication Manager. 5. Verify that calls can be completed to and from each Avaya IP telephone, IP softphone, and Digital telephone with acceptable voice quality. 6. Use a traffic generator to overload infrastructure links with low priority data traffic and verify that calls can still be completed over those links with good or acceptable voice quality. 10. Support For technical support on Extreme Networks products, consult the support pages at or contact the Extreme Networks Worldwide TAC at: Toll free: Phone: support@extremenetworks.com 11. Conclusion These Application Notes illustrate the procedure for configuring a converged voice/data network comprised of Avaya IP Telephony products and Extreme Networks switches. The Avaya IP Telephony products include the Avaya S8500 Media Server running Avaya Communication Manager software, Avaya G650 Media Gateway, Avaya G350 Media Gateway, Avaya IP Telephones, and Avaya IP Softphones. The Extreme Networks switches include the Alpine 3808, BlackDiamond 10808, Summit 200, Summit , and Summit 400 Switches. The joint solution was successfully compliance-tested as phone calls successfully completed with good 23 of 25

24 voice quality over the Extreme Networks Layer 2/3 infrastructure under various network conditions, including the presence of competing low priority data traffic. 12. Additional References Product documentation for Avaya products may be found at Product documentation for Extreme Networks products may be found at: 24 of 25

25 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 DeveloperConnection Program at 25 of 25