Application Notes for the Packeteer PacketShaper with Avaya Communication Manager - Issue 1.0

Transcription

1 Avaya Solution & Interoperability Test Lab Application Notes for the Packeteer PacketShaper with Avaya Communication Manager - Issue 1.0 Abstract These Application Notes describe the procedure for configuring the Packeteer PacketShaper to guarantee WAN link bandwidth to Voice over IP (VoIP) traffic generated by Avaya Media Servers, Avaya Media Gateways, and Avaya IP Telephones. During compliance testing, telephone calls traversing the WAN link were successfully established and maintained, regardless of the amount of non-voip traffic sharing the WAN link. 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 30

2 1. Introduction These Application Notes describe a compliance-tested configuration comprised of Avaya IP telephony products, such as Avaya Media Servers, Avaya Media Gateways, and Avaya IP Telephones, and the Packeteer PacketShaper. PacketShaper is a traffic management appliance that monitors and controls IP network traffic going over WAN links. Typically placed in between a site s WAN router and LAN, PacketShaper identifies and analyzes inbound/outbound WAN traffic up to and including the OSI Application Layer (Layer 7). In addition, PacketShaper manages WAN link utilization and throughput based on the bandwidth guarantees and policies applied to the identified traffic classes. PacketShaper can thus ensure that Voice over IP (VoIP) packets generated by Avaya Media Servers, Avaya Media Gateways, and Avaya IP telephones always receive their guaranteed share of the WAN link capacity and do not encroach upon the guarantees provided to other traffic classes and applications sharing the WAN link. Figure 1 and Figure 2 show sample network configurations consisting of Avaya S8500 Media Servers, Avaya G650 Media Gateways, Avaya G350 Media Gateways, Avaya IP and Digital telephones, a pair of Packeteer PacketShaper 6500 appliances, PCs, DHCP/FTP servers, and other Avaya infrastructure components. Note that the solution described herein is also extensible to other Avaya Media Servers and Media Gateways. The other infrastructure components, namely the Avaya P333T-PWR Layer 2 Switches, Avaya P333R Layer 2/3 Switches, and Avaya SG203 and SG208 Security Gateways (Figure 2 only) support the verification and illustration of the Avaya/Packeteer solution. The configuration of the infrastructure components are not the focus of these Application Notes and are thus not described here. In Figure 1, both the Avaya G650 Media Gateway and Avaya G350 Media Gateway are controlled by the Avaya 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 both sites obtain IP configuration information from the DHCP/FTP server and register with the Avaya S8500 Media Server via the C-LAN board in the Avaya G650 Media Gateway. The P333R Layer 2/3 Switches route packets between VLANs within their respective sites and route all inter-site packets towards their respective X330W-2DS1 WAN Access Router Modules. The Packeteer PacketShaper 6500 appliances reside between the P333R Layer 2/3 Switches and X330W-2DS1 WAN Access Router Modules in order to manage the traffic leaving and entering their respective sites. Finally, a T1 PPP link between the two X330W-2DS1 WAN Access Router Modules connects the two sites. Figure 2 is essentially the same as Figure 1 with the addition of Avaya SG203 and SG208 Security Gateways to provide a site-to-site VPN tunnel between the two sites. 2 of 30

3 G650 Media Gateway IPSI IP Addr: C-LAN IP Addr: MEDPRO IP Addr: VLAN 2 Main Site VLANs VLAN 1: /24 VLAN 2: /24 VLAN 100: /24 P333R Layer 2/3 Switch with X330W-2DS1 WAN Access Router Module P333R IP Addr: VLAN 1, Q Trunk S8500 Media Server IP Addr: VLAN 2 P333T-PWR Layer 2 Switch IP Addr: D+ DCP Phone Ext DHCP/FTP Server IP Addr: VLAN /24.2 VLAN 100 PacketShaper 6500 PC VLAN IP Phone Ext VLAN IP Phone Ext VLAN 2 T1 PPP /24 Main Site Branch Site Branch Site VLANs VLAN 1: /24 VLAN 2: /24 VLAN 100: /24 G350 Media Gateway IP Addr: VLAN 2 P333R Layer 2/3 Switch with X330W-2DS1 WAN Access Router Module P333R IP Addr: VLAN 1, Q Trunk P333T-PWR Layer 2 Switch IP Addr: T1 6408D+ DCP Phone Ext /24 VLAN 100 PacketShaper 6500 PC VLAN IP Phone Ext VLAN IP Phone Ext VLAN 2 Figure 1: Sample Network Configuration 3 of 30

4 G650 Media Gateway IPSI IP Addr: C-LAN IP Addr: MEDPRO IP Addr: VLAN 2 P333R Layer 2/3 Switch with X330W-2DS1 WAN Access Router Module P333R IP Addr: Main Site VLANs VLAN 1: /24 VLAN 2: /24 VLAN 100: / VLAN 100 VLAN 1, Q Trunk S8500 Media Server IP Addr: VLAN 2 P333T-PWR Layer 2 Switch IP Addr: D+ DCP Phone Ext DHCP/FTP Server IP Addr: VLAN 1 PacketShaper PC VLAN IP Phone Ext VLAN IP Phone Ext VLAN 2 T1 PPP SG208 Security Gateway Main Site /24 Branch Site Branch Site VLANs VLAN 1: /24 VLAN 2: /24 VLAN 100: /24 G350 Media Gateway IP Addr: VLAN 2 P333R Layer 2/3 Switch with X330W-2DS1 WAN Access Router Module P333R IP Addr: VLAN 100 VLAN 1, Q Trunk P333T-PWR Layer 2 Switch IP Addr: T1 6408D+ DCP Phone Ext PacketShaper PC VLAN IP Phone Ext VLAN IP Phone Ext VLAN 2 SG203 Security Gateway Figure 2: Sample Network Configuration with Site-to-Site VPN Tunnel Between Sites 4 of 30

5 2. Equipment and Software Validated The following equipment and software/firmware were used for the sample configurations provided: Equipment Software/Firmware Avaya S8500 Media Server (R012x ) Avaya G650 Media Gateway - TN2312BP IPSI 9 TN799DP C-LAN 11 TN2302AP MedPro 77 TN2224CP Digital Line 2 Avaya G350 Media Gateway - Media Gateway Processor MM712AP DCP Media Module 5 Avaya 4602SW IP Telephone Avaya 4610SW IP Telephone Avaya 4620SW IP Telephone Avaya 6400 Series Digital Phones - Avaya P333T-PWR Power over Ethernet Stackable Ethernet Switch Avaya P333R Multilayer Stackable Switch Avaya X330W-2DS1 WAN Access Router Module 3.12 Avaya SG203 Security Gateway Avaya SG208 Security Gateway Packeteer PacketShaper 6500 PacketWise PCs Windows 2000 Professional SP4 Microsoft DHCP Server Windows 2000 Advanced Server SP4 GuildFTPd FTP Server Configure the Packeteer PacketShaper This section describes the steps for creating traffic classes for VoIP protocols such as RTP, RTCP, H.323, H.248, and encrypted H.248, and configuring policies and partitions for those VoIP traffic classes on PacketShaper. The steps are applicable to both PacketShapers in the main and branch sites of Figure 1 and Figure Create Outbound VoIP Traffic Classes A traffic class identifies the traffic flows of specific IP addresses, protocols, or applications. Traffic classes may be either discovered or created. This section discusses the creation of traffic classes relevant to VoIP. 5 of 30

6 1. Open a browser, enter PacketShaper s IP address in the URL and log in with the appropriate password. 6 of 30

7 2. Click on the Setup tab. Enter the capacity of the WAN link in the Inbound Rate and Outbound Rate textboxes and click on apply changes. In the example below, a rate of 1.5M is used to approximate the T1 link rate. Note: For VPN configurations, the effective inbound/outbound rates may be significantly lower depending on the encryption algorithm used and processing power of the VPN devices. The calculation of the effective rates is beyond the scope of this document. Use the effective rates if they can be determined. 3. Click on the Manage tab and then the Outbound folder in the left panel. 7 of 30

8 4. Select class->add folder to create a folder for outbound VoIP traffic classes. 5. Enter a name for the folder and click on OK. 8 of 30

9 6. Click on the newly created folder in the left panel. Then select class->add to create an outbound traffic class. 9 of 30

10 7. Enter a Name for the traffic class and select the Service corresponding to the traffic class. The example below shows the creation of an RTP traffic class. Click on add class. 10 of 30

11 8. Repeat Steps 6 7 for the following traffic classes: RTCP: Select RTCP-I for the Service field. H.323: Select H.323 for the Service field. H.248 (unencrypted)*: Select Megaco for the Service field. H.248 (encrypted)*: Select any for the Service field, and enter 1039 for the Outside Port(s) textbox. * The H.248 traffic classes need to be created if one or more media gateways are registered to the media server via a C-LAN board. Check the display media-gateway form using the SAT to see if the H.248 link is encrypted. If encrypted H.248 links are not used, then skip the last bullet above and Steps MEDIA GATEWAY Number: 1 IP Address: Type: g350 FW Version/HW Vintage: /49 Name: G350 MAC Address: 00:04:0d:29:cb:d9 Serial No: 03IS Encrypt Link? y Network Region: 2 Location: 1 Registered? y Controller IP Address: Site Data: 11 of 30

12 9. Click on the traffic class for encrypted H.248 in the left panel, and then select class->add matching rule. 12 of 30

13 10. Enter 1039 for the Inside Port(s) textbox and click on add rule Assign Priority Policies to Outbound Call Control Traffic Classes A priority policy applied to a traffic class specifies the precedence that packets within the traffic class should have relative to packets within other traffic classes. For example, a priority policy may be applied to each call control traffic class so that call control traffic takes precedence over less real-time sensitive data traffic. 13 of 30

14 1. Click on an outbound call control traffic class (RTCP, H.323, H.248 unencrypted, H.248 encrypted) in the left panel and select policy->add. 14 of 30

15 2. For the Type field, select Priority and specify 5 (or higher) for the Priority value. The Priority value corresponds to a strict priority queue, though traffic classes with rate guarantees (see rate policies in Section 3.3) are always allocated bandwidth first. 15 of 30

16 3. [Optional] To force all packets of the traffic class going through PacketShaper in a particular direction (outbound in the example below) to have the same DSCP value for QoS purposes, click on diffserv. In the invoked IP Diffserv window, select Code Point for the Diffserv Type field, enter a DSCP value for Code Point Substitution field, and click on OK. Note that this step is not necessary if the DSCP values are set in Avaya Communication Manager (see Section 4.1). 4. Click on add policy. 5. Repeat steps 1-4 for the other outbound call control traffic classes. 16 of 30

17 3.3. Assign a Rate Policy to Individual RTP Flows and a Partition to the Outbound RTP Traffic Class Since the audio portion of a VoIP connection requires a constant bit rate, a rate policy should be applied to individual RTP flows within the RTP traffic class. A rate policy specifies the amount of bandwidth guaranteed to each RTP flow, i.e. each telephone call, and when properly defined, ensures that each telephone call going over the WAN link always receives enough bandwidth. A partition specifies the total bandwidth guaranteed to all traffic within a traffic class. A partition applied to the RTP traffic class thus reserves a portion of the WAN link capacity for all RTP traffic. When combined with a rate policy on individual RTP flows, the partition effectively sets a maximum on the number of concurrent telephone calls going across the WAN link. Bandwidth above the reserved partition amount cannot be guaranteed, even with burstable limits defined. Therefore, telephone calls beyond the maximum also cannot be guaranteed and should be prevented from using the WAN link by the Avaya Communication Manager Call Admission Control (CAC) feature (see Section 4.1). Step 1. Click on the outbound RTP traffic class in the left panel and select policy->add. 17 of 30

18 2. For Type, select Rate and enter in Guaranteed rate field the amount of bandwidth to be guaranteed to each outbound RTP flow (i.e., each phone call). The per-call bandwidth depends on the codec, packet size, and number of frames per packet. For example, for G.729 codec, 20 ms packet size, and 2 frames per packet, the calculated per-call bandwidth including overhead is approximately 25 kbps. Uncheck the Burstable at Priority checkbox. 18 of 30

19 3. [Optional] To force all RTP packets going through PacketShaper in a particular direction (outbound in the example below) to have the same DSCP value for QoS purposes, click on diffserv. In the invoked IP Diffserv window, select Code Point for the Diffserv Type field, enter a DSCP value for Code Point Substitution field, and click on OK. Note that this step is not necessary if the DSCP values are set in Avaya Communication Manager (see Section 4.1). 4. Click on add policy. 19 of 30

20 5. Select partition->add. 20 of 30

21 6. Enter the total amount of bandwidth (in bit rate or percentage) to be guaranteed to outbound RTP traffic, uncheck the Burstable checkbox and click on add partition. A rough guideline for sizing the partition is as follows: N = number of calls to be guaranteed R = per call bandwidth Size = (N * R) + (0.1 * R) For example, if twenty G.729 calls are to be guaranteed, then N = 20, R = 25 kbps (recall Step 3 of this section), and Size = (20 * 25 kbps) + (0.1 * 2.5 kbps) = kbps, or approximately 503 kbps. Note that the extra sizing (0.1 * R) is suggested merely for illustrative purposes. Packeteer documentation recommends oversizing by as much as 15 to 20 percent. 21 of 30

22 3.4. Configure Inbound Traffic Classes, Policies, and Partitions Traffic classes, policies, and partitions may be configured for inbound traffic in the same manner as described in Sections for outbound traffic. If the inbound configuration is to be the same as the outbound configuration, then perform the steps below. Step 1. Click on the outbound VoIP folder in the left panel and select class->copy. 22 of 30

23 2. In the To new parent field, select /Inbound and click on copy class and children Uncontrolled FTP Traffic In PacketWise software release 6.2.1, uncontrolled (i.e., no rate limit applied) FTP traffic may prevent the Nth call from completing, where N calls are guaranteed with the configured bandwidth reservation. To avoid this, enter the following command from the PacketShaper CLI: sys set strict Enabling Traffic Shaping To turn on traffic shaping, click on the Setup tab, select On for the Shaping field, and click on apply changes. 23 of 30

24 4. Configure Avaya Communication Manager 4.1. Configure IP Network Regions In the sample configurations described by these Application Notes, each site is considered to be a separate IP network region. To configure an IP network region, enter change ip-networkregion m using the SAT, where m is the number of the region. On Page 1 of the change ip-network-region form, configure the following: Codec Set Enter the codec set number to be used in this region. A codec set specifies the set of codecs that may be used for IP calls within the region. To specify the codecs in a codec set, enter change ip-codec-set p using the SAT, where p is the number of a codec set, and modify the ip-codec-set form accordingly. DiffServ/ToS Parameters and 802.1P/Q Parameters Enter DSCP and 802.1p values for call control and audio RTP packets originating from the region. Intra-region IP-IP Direct Audio if set to yes, RTP audio paths may be established directly between IP telephones within the region. 24 of 30

25 Inter-region IP-IP Direct Audio if set to yes, RTP audio paths may be established directly between an IP telephone within this region and another IP telephone in another region that also has this parameter set to yes. 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 UDP Port Min: 2048 IP Audio Hairpinning? y UDP Port Max: 3028 RTCP Reporting Enabled? y RTCP MONITOR SERVER PARAMETERS DIFFSERV/TOS PARAMETERS Call Control PHB Value: 34 Use Default Server Parameters? y Audio PHB Value: P/Q PARAMETERS Call Control 802.1p Priority: 7 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 On Page 3 of the form, specify the following for every pair of IP network regions: codec-set enter the number of the codec set that indicates which codecs may be used for calls between the two regions. direct-wan set to y to indicate that there is a direct WAN connection between the two regions. WAN-BW-limits specify the maximum number of calls allowed between the two regions. This number should be the maximum number of calls allowed with the bandwidth reservation made in the PacketShaper. If this parameter is not set, then even if bandwidth is reserved in the PacketShaper for N calls, the N+1 call may still complete, albeit without audio. If the WAN-BW-limits parameter is set to N calls, the Avaya Media Server will not allow the N+1 call to follow the same path. In the example below, the calls between IP network regions 1 and 2 may use the codecs defined in codec set 1 and the number of calls between the two regions is limited to 20. Recall that in the examples of Section 3.3, the bandwidth reservation made on the PacketShaper was based on a maximum of 20 G.729 calls. 25 of 30

26 change ip-network-region 1 Page 3 of 19 Inter Network Region Connection Management src dst rgn rgn codec-set direct-wan WAN-BW-limits Intervening-regions y 20:Calls 1 3 Note: For configurations where two sites are served by local Avaya Media Servers and an IP trunk is configured between the two Avaya Media Servers, then limit the number of calls on the IP trunk by limiting the number of trunk members in the change trunk-group form, i.e. one trunk member for every call Assign Media Gateways and IP Addresses to IP Network Regions To assign a media gateway to an IP network region, enter change media gateway q using the SAT, where q is the number of a media gateway. On the change media-gateway form, specify the IP network region for the media gateway. In the example below, a G350 Media Gateway is assigned to IP network region 2. change media-gateway 1 Page 1 of 1 MEDIA GATEWAY Number: 1 IP Address: Type: g350 FW Version/HW Vintage: /49 Name: G350 MAC Address: 00:04:0d:29:cb:d9 Serial No: 03IS Encrypt Link? y Network Region: 2 Location: 1 Registered? n Controller IP Address: Site Data: To assign a range of IP addresses to an IP network region, enter change ip-network-map using the SAT. On Page 1 of the change ip-network-map form, enter one or more IP address ranges and the associated IP network regions. In the example below, IP endpoints (i.e., IP telephones) in the /24 subnet are assigned to IP network region 2. change ip-network-map Page 1 of 32 IP ADDRESS MAPPING Emergency Subnet Location From IP Address (To IP Address or Mask) Region 24 2 VLAN n Extension n 26 of 30

27 5. Interoperability Compliance Testing The interoperability compliance testing focused on assessing the impact that PacketShaper has on VoIP performance in a converged voice/data IP network comprising Avaya Media Servers, Avaya Media Gateways, Avaya IP phones, Avaya Digital phones, PCs, and file servers. The test network was divided into two simulated sites connected by a T1 PPP WAN link, and PacketShaper appliances were employed at each site to manage the bandwidth utilization on the WAN link. Bandwidth reservations were configured on PacketShaper appliances for each VoIP RTP flow and for total VoIP RTP traffic. For call control VoIP traffic (RTCP, H.323, H.248), bandwidth reservations were not made but higher priority policies were applied General Test Approach The general approach was to attempt calls between the two sites with varying levels of competing data traffic on the WAN link. The main objectives were to verify that: An Avaya Media Gateway and Avaya IP telephones are able to register with an Avaya Media Server across the WAN link. Calls between pairs of Avaya telephones (IP-IP, Digital-Digital, and IP-Digital) can be established across the WAN link. Multiple calls between the two sites up to the guaranteed (reserved) amount can be established and maintained with good voice quality, even with the presence of competing data traffic (including aggressive applications such as FTP). Calls above the guaranteed amount are not delivered to the WAN. Non-VoIP traffic does not encroach upon the bandwidth guaranteed to VoIP traffic. VoIP traffic does not encroach upon the bandwidth reserved for other traffic. PacketShaper is able to insert or overwrite DSCP values in VoIP packets. The joint solution is valid for different voice codecs (G.711 and G.729) as well as VPN and non-vpn configurations Test Results All test cases completed successfully. With the appropriate bandwidth reservations, PacketShaper was able to guarantee bandwidth for all calls up to the amount allowed on the WAN link, regardless of the amount of competing traffic sharing the WAN link. In addition, the solution was successfully tested with G.711 and G.729 codecs in VPN and non-vpn configurations. The following observations were made during the testing: 1. If no bandwidth reservations are made for call control VoIP traffic, then additional calls over the guaranteed amount may still complete, but no talk path will be available. To ensure that such additional calls are not directed to the WAN link, use Avaya Communication Manager CAC to limit the number of inter-region calls (see Section 4.1) 27 of 30

28 to the same number of calls that the bandwidth reservations made in PacketShaper can guarantee. 2. In PacketWise software release 6.2.1, uncontrolled FTP traffic may prevent the Nth call from completing, where N calls are guaranteed with the configured bandwidth reservation. A workaround for this issue was described earlier in Section 3.5. This issue is expected to be resolved in a future PacketWise release. 6. Verification Steps The following steps may be used to verify the configuration: On PacketShaper, verify that the partitions, rate policies, and priority policies are configured correctly. If VPN is used, verify that the tunnel is up and configured properly. From each side of the WAN link, ping IP endpoints (Avaya Media Servers, Avaya Media Gateways, Avaya IP phones, PCs, servers, etc.) on the other side of the link. Verify that basic calls can be completed across the WAN link with acceptable voice quality. Make and maintain a call that goes across the WAN link, then FTP a large file across the WAN link and verify that the call is maintained and voice quality is unaffected. 7. Support For technical support on the PacketShaper product line, consult or contact Packeteer Technical Support: Americas Monday Friday: 6:00 AM 6:00 PM (U.S. Pacific Time) Voice: Fax: Europe Monday Friday: 9:00 AM 6:00 PM (The Netherlands) Voice: Fax: Asia Pacific Monday Friday: 8:00 AM 7:00 PM (Hong Kong) Voice: Fax: Tokyo Monday Friday: 9:00 AM 6:00 PM (Tokyo) Voice: of 30

29 Fax: Australia/New Zealand Monday Friday: 7:00 AM 7:00 PM (Sydney) Support Hot Line: (In Australia) Support Hot Line: +61 (0) (Outside Australia) Fax: 61 (0) Conclusion These Application Notes illustrate the procedure for configuring the Packeteer PacketShaper to guarantee WAN link bandwidth to VoIP traffic generated by Avaya Media Servers, Avaya Media Gateways, and Avaya IP telephones. With the appropriate bandwidth reservations and rate and priority policies applied to VoIP traffic classes, telephone calls going across the WAN link were always provided with the configured guaranteed bandwidth, regardless of the amount of non-voip traffic sharing the WAN link. 9. Additional References Product documentation for Avaya products may be found at Product documentation for Packeteer products may be found at 29 of 30

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