Configuring Avaya 9600 Series IP Telephones with Avaya Ethernet Routing Switches 4548GT-PWR and T- PWR for Quality of Service (QoS) Issue 1.

Transcription

1 Avaya Solution & Interoperability Test Lab Configuring Avaya 9600 Series IP s with Avaya Ethernet Routing Switches 4548GT-PWR and T- PWR for Quality of Service (QoS) Issue 1.0 Abstract These Application Notes describe the configuration of the Avaya 9600 Series IP s with Avaya Ethernet Routing Switches 4548GT-PWR and T-PWR for Quality of Service (QoS). The following 9600 Series IP s were included in the testing: 9608, 9611G, 9621G. 9641G, 9640G and 9670G. The configuration described here also applies to other 9600 Series IP s. 1 of 7

2 1. Introduction Quality of Service allows for the prioritization of voice traffic over data traffic, by tagging voice packets with priority tags that allow switches to differentiate the traffic and deliver it in a more expeditious manner. Two common methods are Diffserv (Layer 3), and 802.1p (Layer 2). Avaya IP s and Avaya Ethernet Routing Switches (ERS) support both, and a sample configuration is covered in these Application Notes. Figure 1 shows the configuration used for QoS. Figure 1: QoS Network Configuration 2 of 7

3 2. Equipment and Software Validated The following equipment and software were used for the configuration provided: Equipment Version Avaya S8800 Server running Avaya Aura Communication Manager as an Evolution 6.0 (R016x ) Server with Avaya G450 Media Gateway Avaya Aura Session Manager Avaya Aura System Manager Avaya one-x Deskphone 9611G IP SIP (96x1_SALBR6_0r78_V4r52B.tar) Avaya one-x Deskphone 9621G IP H.323 (S9621_41_HALBR6_0_V4r52.tar) Avaya one-x Deskphone 9641G IP SIP (96x1_SALBR6_0r78_V4r52B.tar) Avaya one-x Deskphone 9608 IP H.323 (S9608_11_HALBR6_0_V4r52.tar) Avaya one-x Deskphone 9640G IP V2.6 (SIP96xx_2_6_2_0.bin) Avaya one-x Deskphone 9670G IP H.323 V3.1.1(ha9670ua3_11.bin) Avaya ERS 4548GT-PWR Switch V Avaya ERS T-PWR Switch V Configuration of the Avaya 9600 Series Endpoints Avaya IP s can receive QoS tagging information in several ways. These Application Notes cover a configuration where SIP IP s received their QoS values from the 46xxsettings file, and H.323 IP s received their QoS values from Avaya Aura Communication Manager. When a SIP IP reboots, it uses the IP address assigned for the HTTP Server and seeks an upgrade file and a settings file. Certain fields in the settings file tell the SIP IP what values to use. The following fields in the 46xxsettings file were set to assign L p values for SIP IP telephones: SET L2QAUD 6 SET L2QSIG 6 The following fields in the 46xxsettings file were set to assign L3 Diffserv values for SIP IP telephones: SET DSCPAUD 46 SET DSCPSIG 46 3 of 7

4 When a H.323 IP telephone registers with Communication Manager, it is assigned to a network region based on the CLAN card, S8800 server processor-ethernet board that it registers with, or based on its IP Address if specified in the ip-network-map form. The values assigned on the ipnetwork-region form are sent to the phone upon registration and when the form is changed. The ip-network-map form below shows that endpoints with IP Addresses in the range will be associated with network region 1. change ip-network-map Page 1 of 63 IP ADDRESS MAPPING Subnet Network Emergency IP Address Bits Region VLAN Location Ext FROM: / 1 n TO: The network region 1 form below shows the L3 Diffserv and L p fields used to assign the QoS priorities to the H.323 IP s. In the example below, H.323 IP telephones registered in network region 1 will be told to use 46 as the Diffserv L3 value for both Call Control and Audio packets, and 6 as the L p value for both Call Control and Audio packets. change ip-network-region 1 Page 1 of 19 IP NETWORK REGION Region: 1 Location: Authoritative Domain: interop.com Name: MEDIA PARAMETERS Intra-region IP-IP Direct Audio: yes Codec Set: 1 Inter-region IP-IP Direct Audio: yes UDP Port Min: 2048 IP Audio Hairpinning? n UDP Port Max: 3329 DIFFSERV/TOS PARAMETERS RTCP Reporting Enabled? y Call Control PHB Value: 46 RTCP MONITOR SERVER PARAMETERS Audio PHB Value: 46 Use Default Server Parameters? y Video PHB Value: P/Q PARAMETERS Call Control 802.1p Priority: 6 Audio 802.1p Priority: 6 Video 802.1p Priority: 0 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 4 of 7

5 4. Configuration of the Avaya ERS T-PWR and ERS 4548GT-PWR Switch Avaya switches support prioritization based on both Diffserv and 802.1p. Configuration for both switches is done in a similar manner. In the ERS T-PWR switch, IP s were configured on VLAN 7 and the endpoints were set to send VLAN 7 tags. Ports were used for IP Endpoints, and Data VLAN 199 was used as default. In the ERS 4548GT-PWR switch, IP s were configured on VLAN 6 and the endpoints were set to send VLAN 6 tags. Ports were used for IP Endpoints, and Data VLAN 198 was used as default. The following commands show the VLAN configuration on the ERS T-PWR switch. Similar commands were used on the ERS 4548GT-PWR switch, with the respective VLAN, ports, and IP addresses used T-PWR(config)#vlan create 7 type port T-PWR(config)#vlan create 199 type port T-PWR(config)#vlan members T-PWR(config)#vlan members T-PWR(config)#vlan ports tagging untagpvidonly pvid T-PWR(config)#interface vlan T-PWR(config-if)#ip address T-PWR(config)#interface vlan T-PWR(config-if)#ip address A QoS if-group, named trustall was created with class unrestricted. Care should be taken when using unrestricted as an interface group class, current operating systems and ethernet cards can also mark data traffic, and therefore savvy users could prioritize their traffic on the network that honors the markings. In this configuration the ports connected to IP s were assigned to the trustall if-group. In doing so, the switch will trust the Diffserv and/or 802.1p tags originated by the phones. A data endpoint connected to one of those ports, or to the phone was set to not tag, and therefore defaults to the priority assigned to the Data VLAN, in this case 0. The following commands were used to create the if-group and assign ports to it T-PWR(config)#qos if-group name trustall class unrestricted T-PWR(config)#qos if-assign port name trustall 5 of 7

6 For additional information or different methods to implement QoS on ERS 5500 and ERS 4500 series switches see [1] and [2]. For additional details on configuring the ERS T-PWR and 4548GT-PWR switches see [3] and [4]. 5. Observations With the release used for this testing it was observed that Avaya IP s were not tagging traffic with 802.1p values according to the settings in the IP Network Region for the phones. Changes in the ip-network-region form did not change the 802.1p values on the IP s, they continually used a value of 6. Changing the Diffserv values on the ip-network-region did properly propagate to the IP s. 6. Verification Steps To verify QoS is working, place calls while there is a background load that exceeds the available bandwidth between the switches, and verify calls can complete and voice quality is good. 7. Conclusion These Application Notes described the configuration of the Avaya IP s with Avaya ERS T-PWR and ERS 4548GT-PWR switches. The switches were able to provide QoS for the Avaya IP s to work properly under background data load. 8. Additional References [1] Ethernet Routing Switch 5500 Series: Configuration- Quality of Service, NN , Revision 06.01, June 28, [2] Ethernet Routing Switch 4500 Series: Configuration- Quality of Service, NN , Revision 06.01, May 3, [3] Ethernet Routing Switch 5500 Series: Configuration- VLANs, Spanning Tree, and Link Aggregation, NN , Revision 06.01, June 28, [4] Ethernet Routing Switch 4500 Series: Configuration- VLANs, Spanning Tree, and Multi-Link Trunking, NN , Revision 06.01, May 3, of 7

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