G450_QOS_MPLS

JF; Reviewed: SPOC 4/17/2008

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

1 of 22 G450_QOS_MPLS

Avaya Solution & Interoperability Test Lab

Configuring Quality of Service (QOS) Over a Cisco MPLS Network Between Avaya Communication Manager and an Avaya G450 Media Gateway. - Issue 1.0

Abstract These Application Notes present configuring Quality of Service (QOS) over a Cisco MPLS core network that connects Avaya Communication Manager in a Main Office to an Avaya G450 Media Gateway in a Branch Office. Should network congestion occur, QOS settings will give priority to the Avaya VoIP traffic across the MPLS core network.




1. INTRODUCTION .................................................................................................................. 3

2. EQUIPMENT AND SOFTWARE VALIDATED ............................................................... 4

3. CONFIGURE AVAYA G450 MEDIA GATEWAY ........................................................... 5

4. CONFIGURE AVAYA COMMUNICATION MANAGER................................................ 6

5. CISCO CONFIGURATIONS .............................................................................................. 8

6. VERIFICATION .................................................................................................................. 17

7. CONCLUSION.................................................................................................................... 20

8. REFERENCES ................................................................................................................... 21

4.1 Add the Avaya G450 Media Gateway ............................................................................................................6

4.2 Configure IP Network Regions .......................................................................................................................7

4.3 Save Translations ..............................................................................................................................................8

5.1 Configure Cisco 3825 Router ..........................................................................................................................8

5.2 Configure Cisco “2811- One” Router..........................................................................................................14

5.3 Cisco “2811-Two” Router Configuration ...................................................................................................15

8.1 Avaya Product Documentation.....................................................................................................................21

8.2 Avaya Application Notes................................................................................................................................21

8.3 Cisco Documentation......................................................................................................................................21




1. Introduction Figure 1 shows the reference network used for the verification of these Application Notes. The reference network is comprised of a “Main Office” and a “Branch Office” connected via a Multi-Protocol Label Switching (MPLS) core network. The Main Office contains an Avaya S8500 Server, an Avaya G650 Media Gateway (containing IPSI, CLAN, and MedPro cards) and Avaya 4621 IP telephones. The Branch Office contains an Avaya G450 Media Gateway and Avaya 4621 IP telephones. In the reference configuration, the Avaya equipment in the Main Office is provisioned on Avaya Communication Manager in Network Region one. The Avaya equipment in the Branch Office is provisioned in Network Region 2. The MPLS core is comprised of one Cisco 3825 router and two Cisco 2811 routers (designated “2811-One” and 2811-Two”). These routers function as MPLS Provider Edges (PEs) and share network routing information between each other via Border Gateway Protocol (BGP). In addition, Cisco’s Enhanced Interior Gateway Routing Protocol (EIGRP) is used between the core routers to determine adjacency states. Each core router has a loopback IP address defined. These loopback addresses are used by EIGRP. Avaya Communication Manager supports both Differentiated Services Code Point (DSCP) values (sometimes referred to as Diffserv) for IP QoS and 802.1p for MAC level QoS. DSCP and 802.1p are provisioned via the Avaya Communication Manager Network Region forms. Avaya VoIP components including Avaya Servers, Avaya Media Gateways and Avaya IP telephones obtain their QoS values from the Network Region settings. In the reference configuration, all Avaya components are configured with a DSCP value of 46 and 802.1p value of 5. QoS is also enabled on the Cisco routers connected to the Main and Branch Offices as well as the inter-MPLS core connections. Refer to [1] and [2] for detailed QoS configuration on the Avaya VoIP components. A Smartbits load generator was connected to the 3825 and 2811-Two core routers. It was provisioned to generate random length UDP packets at 80-90% utilization. Under normal circumstances the MPLS core would route the Smartbits traffic between the 3825 and 2811-Two core routers. The MPLS core routes the Avaya VoIP traffic directly between the 3825 and 2811-One core routers. In this manner the Avaya VoIP traffic is unaffected by the Smartbits load. However if the link between the 3825 and 2811-Two core routers is failed, the MPLS core will re-direct the Smartbits traffic from the 3825 router to the 2811-Two router via the 2811-One router. In this situation the Avaya VoIP traffic will be competing against the Smartbits traffic for bandwidth. Therefore QoS tagging of the Avaya VoIP traffic is necessary.




2. Equipment and Software Validated

Figure 1 – Reference Configuration

The following equipment and software were used to test the sample configuration.

Network Component Hardware/Firmware

Version Software Version

Avaya S8500 Server - Avaya Communication Manager 5.0 R015x.00.0.825.4

Avaya G650 Media Gateway IPSI – TN2312BP CLAN – TN799DP MedPro – TN2302AP

- HW15 FW040 HW01 FW024 HW20 FW117

- - -

Avaya G450 Media Gateway 27.26.0 - Avaya 4621SW H.323 Telephones a20d01b3_8.bin - Smartbits Load Generator - 7.10.40 Wireshark Protocol Analyzer - V 0.99.5 Cisco 3825 Router - c3825-spservicesk9-mz 12.3(11)T Cisco 2811 Routers - c2800nm-adventerprisek9-mz 12.4(10a)

Table 1: Test Equipment List




3. Configure Avaya G450 Media Gateway The QoS values for the Avaya G450 Media Gateway are obtained by means of the Network Region provisioning in Avaya Communication Manager (see Section 4.2). Therefore no QoS specific provisioning is required in the Avaya G450 Media Gateway. The Avaya G450 Media Gateway IP provisioning is shown below. For more information see [1].

1. Configure an IP interface for the Avaya G450 Media Gateway. a. interface vlan 2

Creates the interface Vlan2 b. ip address 73.73.73.2 255.255.255.0

Sets the network IP address and mask for the Avaya G450 Media Gateway c. pmi

Sets the Primary Management Interface. d. exit

2. Configure the default gateway for the Avaya G450 Media Gateway.

a. ip default-gateway 73.73.73.1 73.73.73.1 is the IP address of the Cisco “2811-One” router.

interface Vlan 2 ip address 73.73.73.2 255.255.255.0 pmi exit ! ip default-gateway 73.73.73.1

Figure 2 – Avaya G450 Media Gateway Configuration

3. After the provisioning is completed, enter the command copy run start to save the configuration on the Avaya G450 Media Gateway.

4. Enter the command show system and copy down the serial number. This is required when

the Avaya G450 Media Gateway is provisioned on Avaya Communication Manager in Section 4.1.

G450-001(super)# show system System Name : Branch_G450 System Location : System Contact : Uptime (d,h:m:s) : 7,02:56:35 MV Time : 08:04:49 29 FEB 2008 Serial No : 07IS13107508 Model No : G450

Figure 3 – Avaya G450 Media Gateway Serial Number




4. Configure Avaya Communication Manager In the sample configuration, there are two Network Regions. The Avaya equipment in the Main Office is defined in Network Region 1 and the Avaya equipment in the Branch Office is defined in Network Region 2. The following commands were entered during an Avaya Communication Manager SAT session. Parameter values shown are specific to the reference configuration. For information on these commands see [2].

4.1 Add the Avaya G450 Media Gateway 1. add media-gateway 1

a. Type = g450 b. Name = <text>

c. Serial No: <serial number>

Enter the Avaya G450 Media Gateway serial number taken from the show system command in Section 3 Step 4.

d. Network Region: 2

As described previously, the Avaya G450 Media Gateway resides in Network Region 2.

e. All other vales are default or will auto-populate.

add media-gateway 1 Page 1 of 1 MEDIA GATEWAY Number: 1 Registered? y Type: g450 FW Version/HW Vintage: 27 .26 .0 /0 Name: G450_Branch MGP IP Address: 73 .73 .73 .2 Serial No: 07IS13107508 Controller IP Address: 50 .50 .50 .100 Encrypt Link? y MAC Address: 00:04:0d:ea:ab:b8 Network Region: 2 Location: 1 Site Data: Recovery Rule: 1 Slot Module Type Name DSP Type FW/HW version V1: V2: MM710 DS1 MM V3: MM342 USP WAN MM V4: MP80 8 1 V5: MM711 ANA MM V6: MM712 DCP MM V7: MM716 ANA MM Max Survivable IP Ext: 8 V8: MM340 DS1 WAN MM V9:

Figure 4 – Avaya Communication Manager – Add G450 Media Gateway




4.2 Configure IP Network Regions In the reference configuration, the default DSCP value (46) was used. Therefore no QoS provisioning was required for Network Regions 1 or 2. Default values are shown in Figures 5 and 6.

display ip-network-region 1 Page 1 of 19 IP NETWORK REGION Region: 1 Location: 1 Authoritative Domain: do.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: 26 802.1P/Q PARAMETERS Call Control 802.1p Priority: 5 Audio 802.1p Priority: 5 Video 802.1p Priority: 5 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

Figure 5 – Avaya Communication Manager – IP-Network-Region 1

display ip-network-region 2 Page 1 of 19 IP NETWORK REGION Region: 2 Location: 1 Authoritative Domain: do.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: 26 802.1P/Q PARAMETERS Call Control 802.1p Priority: 5 Audio 802.1p Priority: 5 Video 802.1p Priority: 5 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

Figure 6 – Avaya Communication Manager – IP-Network-Region 2




4.3 Save Translations After the provisioning is completed, enter the command save trans to save the configuration on Avaya Communication Manager.

5. Cisco Configurations As described in Section 1, an MPLS core comprised of one Cisco 3825 router and two Cisco 2811 routers (designated “2811-One” and 2811-Two”) connect the Main Office and the Branch Office. These routers function as MPLS Provider Edges (PEs) and share network routing information between each other via Border Gateway Protocol (BGP). In addition, Cisco’s Enhanced Interior Gateway Routing Protocol (EIGRP) is used between the core routers to determine adjacency states. Each core router has a loopback IP address defined. These loopback addresses are used by EIGRP. Virtual Routing and Forwarding (VRF) is defined on the core routers. VRF routing tables are generated that contain routing information specific to (and only available to) members of a particular VRF. In the reference configuration, the defined VRF is called “VRFMPLS”. Routing Information Protocol (RIP) is used by the Cisco 3825 router to advertise the Main Office IP addressing to VRFMPLS. The Cisco router 2811-One uses RIP to advertise the IP addressing of the Branch to VRFMPLS. The default routing tables in the core routers will contain the loopback IP addresses of the adjacent routers but not the addresses of the Main or Branch Offices. However the VRF routing tables of the core routers will contain the IP addressing of the Main and Branch Offices. In this manner, unless a network device is part of VRFMPLS, routing to the Main and Branch Offices is not possible. QoS is provisioned on each MPLS core interface but not on the interfaces directly connected to the Main or Branch Offices. 5.1 Configure Cisco 3825 Router The 3825 router connects the Main Office to the MPLS core. It provides RIP routing information to the core regarding the Main Office IP addressing (50.50.50.x). This routing information is only available to members of VRFMPLS. The following commands were entered via Cisco CLI from the enable/config t access prompt. See Section 6.3 for more information.

1. Enter ip cef to enable Cisco Express Forwarding (CEF).

ip cef

Figure 7 – Cisco 3825 Router – Enable CEF




2. Configure the QoS policy.

a. Enter class-map match-any voip This command creates a class that matches on any VoIP packet.

i. Enter match mpls experimental topmost 5 By default, Cisco copies the three most significant bits of the DiffServ code point (DSCP) or the IP precedence of the IP packet to the EXP field in the MPLS header. A value of decimal value 46 is 101110 in binary. The first three binary bits (101) equals 5 (4+1).

ii. Enter exit b. Enter policy-map mpls-qos

This command creates a policy map called mpls-qos. This will be used in Step 4. i. Enter class voip

Specifies VoIP traffic. ii. Enter priority 50

Specifies 50 kbps. iii. Enter class class-default

Specifies a non-VoIP class.

class-map match-any voip match mpls experimental topmost 5 ! policy-map mpls-qos class voip priority 50 class class-default

Figure 8 – Cisco 3825 Router – Configure QOS

3. Configuring the IP interface to the Main Office. a. Enter interface fastethernet 1/1

i. Enter description To_Main ii. Enter ip vrf forwarding VRFMPLS

This defines the interface to VRFMPLS. iii. Enter ip address 50.50.50.1 255.255.255.0

This defines the IP address of the interface iv. Enter duplex full

This command sets the interface to full duplex. v. Enter speed 100

This command sets the interface to 100mbps.

FastEthernet1/1 description To_Main ip vrf forwarding VRFMPLS ip address 50.50.50.1 255.255.255.0 duplex full speed 100

Figure 9 – Cisco 3825 Router – Configure Interface




4. Configuring the MPLS interface to core router “2811-One”

a. Enter interface gigabitethernet 0/0 i. Enter description To_2811_One

ii. Enter ip address 10.1.1.2 255.255.255.0 This defines the IP address of the interface

iii. Enter service-policy output mpls-qos This command specifies the QOS policy defined in Step 2.

iv. Enter media-type rj45 This command defines the interface as type rj45.

v. Enter mpls label switching ldp This command sets enables Label Distribution Protocol (LDP).

vi. Enter tag-switching ip This command sets enables tag-switching on the interface.

interface GigabitEthernet0/0 description To_2811_One ip address 10.1.1.2 255.255.255.0 service-policy output mpls-qos duplex auto speed auto media-type rj45 mpls label protocol ldp tag-switching ip

Figure 10 – Cisco 3825 Router – Configure MPLS to Router 2811-One

5. Configuring the MPLS interface to core router “2811-Two” The commands are similar to Step 4.

interface GigabitEthernet0/1 description To_2811_Two ip address 10.1.2.2 255.255.255.0 service-policy output mpls-qos duplex auto speed auto media-type rj45 mpls label protocol ldp tag-switching ip

Figure 11 – Cisco 3825 Router – Configure MPLS to Router 2811-Two

6. Configuring the loopback interface. a. Enter interface loopback 0

i. Enter ip address 10.10.10.2 255.255.255.0 This defines the IP address of the interface.

interface Loopback0 ip address 10.10.10.2 255.255.255.255

Figure 12 – Cisco 3825 Router – Configure Loopback Interface




7. Enable EIGRP routing for the core router loopback addresses.

a. Enter router eigrp 10 This command enables EIGRP with a network ID of 10.

i. Enter network 10.0.0.0 This command defines the IP domain.

ii. Enter no auto-summary This command allows disconnected subnets to be advertised in RIP.

router eigrp 10 network 10.0.0.0 no auto-summary

Figure 13 – Cisco 3825 Router – Configure EIGRP

8. Create the VRF “VRFMPLS” a. Enter ip vrf VRFMPLS

i. Enter rd 1:10 Create a route distinguisher ID

ii. Enter route-target export 1:10 This defines the export routing to BGP.

iii. Enter route-target import 1:10 This defines the import routing from BGP.

iv. Enter ip vrf forwarding Enables vrf forwarding.

ip vrf VRFMPLS rd 1:10 route-target export 1:10 route-target import 1:10 ip vrf forwarding

Figure 14 – Cisco 3825 Router – Create VRFMPLS

9. Enable BGP routing for the core routers including RIP and “VRFMPLS”. a. Enter router bgp 65001

This command enables BGPP with an autonomous system ID of 65001. i. Enter no synchronization

This command allows GP to update network routes without waiting for IGP updates.

ii. Enter bgp log-neighbor changes This command enables logging of Border Gateway Protocol (BGP) neighbor resets.

iii. Enter neighbor 10.10.10.1 remote-as 65001 Adds an entry to the BGP neighbor table for network 10.10.10.1 (loopback address of core router 2811-Two).

iv. Enter neighbor 10.10.10.1 update-source Loopback0 Allows BGP sessions to use interface Loopback 0 for TCP connections to core router 2811-Two.




v. Enter neighbor 10.10.10.3 remote-as 65001 Adds an entry to the BGP neighbor table for network 10.10.10.3 (loopback address of core router 2811-One).

vi. Enter neighbor 10.10.10.3 update-source Loopback0 Allows BGP sessions to use interface Loopback 0 for TCP connections to core router 2811-Two.

b. Enter address-family vpnv4 Enter address family configuration mode for configuring routing sessions.

i. Enter neighbor 10.10.10.1 activate Enable the exchange of information with BGP neighbor router 2811-Two.

ii. Enter neighbor 10.10.10.1 next-hop-self Configure the router as the next hop for a BGP neighbor router 2811-Two.

iii. Enter neighbor 10.10.10.1 send-community both Specify that this communities attributes should be sent to BGP neighbor router 2811-Two.

iv. Enter neighbor 10.10.10.3 activate Enable the exchange of information with BGP neighbor router 2811-One.

v. Enter neighbor 10.10.10.3 next-hop-self Configure the router as the next hop for a BGP neighbor router 2811-TOne.

vi. Enter neighbor 10.10.10.3 send-community both Specify that this communities attributes should be sent to BGP neighbor router 2811-One.

vii. Enter exit-address-family

c. Enter address-family ipv4 vrf VRFMPLS Configure an BGP family for VRFMPLS.

i. Enter redistribute rip Specify the BGP will redistribute RIP routing updates.

ii. Enter no auto-summary To advertise and carry subnet routes in BGP.

iii. Enter no synchronization Allows the Cisco IOS software to advertise a network route without waiting for the IGP.

iv. Enter exit-address-family




router bgp 65001 no synchronization bgp log-neighbor-changes neighbor 10.10.10.1 remote-as 65001 neighbor 10.10.10.1 update-source Loopback0 neighbor 10.10.10.3 remote-as 65001 neighbor 10.10.10.3 update-source Loopback0 no auto-summary address-family vpnv4 neighbor 10.10.10.1 activate neighbor 10.10.10.1 next-hop-self neighbor 10.10.10.1 send-community both neighbor 10.10.10.3 activate neighbor 10.10.10.3 next-hop-self neighbor 10.10.10.3 send-community both exit-address-family address-family ipv4 vrf VRFMPLS redistribute rip no auto-summary no synchronization exit-address-family

Figure 15 – Cisco 3825 Router – Configure BGP

10. Enable the RIP advertisement of the Main Office IP network to “VRFMPLS” and BGP.

i. Enter router rip Enables RIP protocol.

ii. Enter version 2 Specifies RIP version 2 to be used.

iii. Enter address-family ipv4 vrf VRFMPLS Enter address family configuration mode for configuring routing sessions for VRFMPLS.

iv. Enter redistribute bgp 65001 metric transparent Redistributes routes with BGP autonomous system ID 65001.

v. Enter network 50.0.0.0 Specifies the network that RIP will advertise to BGP.

vi. Enter no auto-summary Disable automatic summarization to perform routing between disconnected subnets.

vii. Enter exit-address-family

router rip version 2 address-family ipv4 vrf VRFMPLS redistribute bgp 65001 metric transparent network 50.0.0.0 no auto-summary exit-address-family

Figure 16 – Cisco 3825 Router – Configure RIP




5.2 Configure Cisco “2811- One” Router Cisco 2811 router “2811-One” connects the Branch Office to the MPLS core. It provides RIP routing information to the core regarding the Branch Office IP addressing (73.73.73.x). This routing information is only available to members of VRFMPLS. It is configured in a similar fashion as the 3825 router (Section 5.1).

2811_One# ! ip cef ! class-map match-any voip match mpls experimental topmost 5 ! ! policy-map mpls-qos class voip priority 50 class class-default ! ip vrf VRFMPLS rd 1:10 route-target export 1:10 route-target import 1:10 ! ip vrf forwarding ! interface Loopback0 ip address 10.10.10.3 255.255.255.255 ! interface FastEthernet0/0 description To_2811_Two ip address 10.1.3.1 255.255.255.0 service-policy output mpls-qos duplex full speed 100 mpls label protocol ldp mpls ip ! interface FastEthernet0/1 description To_G450_Media_gateway ip vrf forwarding VRFMPLS ip address 73.73.73.1 255.255.255.0 duplex auto speed auto ! interface GigabitEthernet1/0 description MPLS_To_3825 ip address 10.1.1.1 255.255.255.0 service-policy output mpls-qos mpls label protocol ldp mpls ip !




router eigrp 10 network 10.0.0.0 no auto-summary ! router rip version 2 ! address-family ipv4 vrf VRFMPLS redistribute bgp 65001 metric transparent network 73.0.0.0 no auto-summary exit-address-family ! router bgp 65001 no synchronization bgp log-neighbor-changes neighbor 10.10.10.1 remote-as 65001 neighbor 10.10.10.1 update-source Loopback0 neighbor 10.10.10.2 remote-as 65001 neighbor 10.10.10.2 update-source Loopback0 no auto-summary ! address-family vpnv4 neighbor 10.10.10.1 activate neighbor 10.10.10.1 send-community both neighbor 10.10.10.1 next-hop-self neighbor 10.10.10.2 activate neighbor 10.10.10.2 send-community both neighbor 10.10.10.2 next-hop-self exit-address-family ! address-family ipv4 vrf VRFMPLS redistribute rip no synchronization exit-address-family !

Figure 17 – Cisco 2811-One Configuration 5.3 Cisco “2811-Two” Router Configuration Cisco 2811 router “2811-Two” is the third router in the MPLS core. Although it does not directly connect to either the Main or Branch Offices, it does forward routing information for VRFMPLS. If the direct link between the 3825 router and router “2811-One” fails, connectivity between the Main and Branch Offices would be maintained via router “2811-Two”. It is configured in a similar fashion as the “2811-One” router (Section 5.2).




2811-Two# ! ip cef ! class-map match-any voip match mpls experimental topmost 5 ! ! policy-map mpls-qos class voip priority 50 class class-default ! ip vrf VRFMPLS rd 1:10 route-target export 1:10 route-target import 1:10 ! ip vrf forwarding ! interface Loopback0 ip address 10.10.10.1 255.255.255.255 ! interface FastEthernet0/1 description To_2811_One ip address 10.1.3.2 255.255.255.0 service-policy output mpls-qos duplex full speed 100 mpls label protocol ldp mpls ip ! interface GigabitEthernet1/0 description To_3825 ip address 10.1.2.1 255.255.255.0 service-policy output mpls-qos mpls label protocol ldp mpls ip ! router eigrp 10 network 10.0.0.0 no auto-summary ! router bgp 65001 no synchronization bgp log-neighbor-changes neighbor 10.10.10.2 remote-as 65001 neighbor 10.10.10.2 update-source Loopback0 neighbor 10.10.10.3 remote-as 65001 neighbor 10.10.10.3 update-source Loopback0 no auto-summary !




address-family vpnv4 neighbor 10.10.10.2 activate neighbor 10.10.10.2 send-community both neighbor 10.10.10.2 next-hop-self neighbor 10.10.10.3 activate neighbor 10.10.10.3 send-community both neighbor 10.10.10.3 next-hop-self exit-address-family ! address-family ipv4 vrf VRFMPLS redistribute rip no synchronization exit-address-family !

Figure 18 – Cisco 2811-Two Configuration

6. Verification 1. Verify that the Avaya G450 Media Gateway in the Branch Office is registered to

Avaya Communication Manager in the Main Office. 2. Place a call from the Main to Branch Office. Verify good audio quality. 3. Start Smartbits traffic and verify that the Avaya VoIP call is unaffected. 4. Fail the link between the 3825 and 2811-two core routers. Verify with Wireshark that

the Smartbits traffic now uses the 3811 to 2811-One link to get to the 2811-Two router.

5. Verify that the Avaya VoIP call still has good quality. 6. Verify that the Avaya G450 Media Gateway remains registered to Avaya

Communication Manager in the Main Office. 7. Stop the Smartbits load and disconnect the Avaya call but leave the link between the

3825 and 2811-two core routers down. 8. Remove the MPLS QoS service-policy from the Core Router interfaces using the

command: no service-policy output mpls-qos (see Section 5). 9. Place the Avaya VoIP call again and verify good audio. 10. Start the Smartbits traffic and verify that the Avaya audio quality degrades. 11. Verify that the Avaya G450 Media Gateway looses registration with Avaya

Communication Manager in the Main Office. 12. QoS tagging can be confirmed with a protocol analyzer. The following examples

show QoS tagging on the Avaya audio traffic and no QoS tagging on the Smartbits traffic.

a. Avaya 4621 IP Telephone UDP packet – DSCP = 2e hex, (46 decimal) which is the value defined in the Avaya Communication Manager Network Region form (see Section 4.2).




Frame 64 (214 bytes on wire, 214 bytes captured) Ethernet II, Src: Avaya_e9:75:52 (00:04:0d:e9:75:52), Dst: Cisco_68:84:42 (00:11:93:68:84:42) Internet Protocol, Src: 50.50.50.151 (50.50.50.151), Dst: 73.73.73.101 (73.73.73.101) Version: 4 Header length: 20 bytes Differentiated Services Field: 0xb8 (DSCP 0x2e: Expedited Forwarding; ECN: 0x00) 1011 10.. = Differentiated Services Codepoint: Expedited Forwarding (0x2e) .... ..0. = ECN-Capable Transport (ECT): 0 .... ...0 = ECN-CE: 0 Total Length: 200 Identification: 0x4fdb (20443) Flags: 0x00 0... = Reserved bit: Not set .0.. = Don't fragment: Not set ..0. = More fragments: Not set Fragment offset: 0 Time to live: 64 Protocol: UDP (0x11) Header checksum: 0x321b [correct] [Good: True] [Bad : False] Source: 50.50.50.151 (50.50.50.151) Destination: 73.73.73.101 (73.73.73.101) User Datagram Protocol, Src Port: 2182 (2182), Dst Port: 2534 (2534) Source port: 2182 (2182) Destination port: 2534 (2534) Length: 180 Checksum: 0x0176 [correct] [Good Checksum: True] [Bad Checksum: False] Real-Time Transport Protocol [Stream setup by H245 (frame 51)] [Setup frame: 51] [Setup Method: H245] 10.. .... = Version: RFC 1889 Version (2) ..0. .... = Padding: False ...0 .... = Extension: False .... 0000 = Contributing source identifiers count: 0 0... .... = Marker: False Payload type: ITU-T G.711 PCMU (0) Sequence number: 4062 Timestamp: 1758677976 Synchronization Source identifier: 1982797712 Payload: 6D7BFB7BF8F2FCFBFE6D71F67CFEF7FEEEF56F77FDFBEFF9...

Figure 19 – Protocol Trace – Avaya IP Telephone QOS Tagging




b. Avaya G450 Media Gateway packet - DSCP = 2e hex, (46 decimal) which is

the value defined in the Avaya Communication Manager Network Region form (see Section 4.2).

Frame 12 (168 bytes on wire, 168 bytes captured) Ethernet II, Src: Avaya_ea:ab:b8 (00:04:0d:ea:ab:b8), Dst: Cisco_83:3e:f9 (00:18:18:83:3e:f9) Internet Protocol, Src: 73.73.73.2 (73.73.73.2), Dst: 50.50.50.100 (50.50.50.100) Version: 4 Header length: 20 bytes Differentiated Services Field: 0xb8 (DSCP 0x2e: Expedited Forwarding; ECN: 0x00) 1011 10.. = Differentiated Services Codepoint: Expedited Forwarding (0x2e) .... ..0. = ECN-Capable Transport (ECT): 0 .... ...0 = ECN-CE: 0 Total Length: 154 Identification: 0x50d5 (20693) Flags: 0x00 0... = Reserved bit: Not set .0.. = Don't fragment: Not set ..0. = More fragments: Not set Fragment offset: 0 Time to live: 64 Protocol: TCP (0x06) Header checksum: 0x31f0 [correct] [Good: True] [Bad : False] Source: 73.73.73.2 (73.73.73.2) Destination: 50.50.50.100 (50.50.50.100) Transmission Control Protocol, Src Port: 1074 (1074), Dst Port: 1039 (1039), Seq: 0, Ack: 0, Len: 114 Source port: 1074 (1074) Destination port: 1039 (1039) Sequence number: 0 (relative sequence number) [Next sequence number: 114 (relative sequence number)] Acknowledgement number: 0 (relative ack number) Header length: 20 bytes Flags: 0x18 (PSH, ACK) 0... .... = Congestion Window Reduced (CWR): Not set .0.. .... = ECN-Echo: Not set ..0. .... = Urgent: Not set ...1 .... = Acknowledgment: Set .... 1... = Push: Set .... .0.. = Reset: Not set .... ..0. = Syn: Not set .... ...0 = Fin: Not set Window size: 8192 Checksum: 0x0577 [correct] [Good Checksum: True] [Bad Checksum: False] Data (114 bytes)

Figure 20 – Protocol Trace – Avaya G450 Media Gateway QOS Tagging




c. Smartbits UDP packet – DSCP value = 0.

Frame 13 (697 bytes on wire, 697 bytes captured) Ethernet II, Src: 00:00:00_00:00:0f (00:00:00:00:00:0f), Dst: Cisco_f4:d5:d0 (00:1a:6d:f4:d5:d0) Internet Protocol, Src: 63.63.63.63 (63.63.63.63), Dst: 90.90.90.90 (90.90.90.90) Version: 4 Header length: 20 bytes Differentiated Services Field: 0x00 (DSCP 0x00: Default; ECN: 0x00) 0000 00.. = Differentiated Services Codepoint: Default (0x00) .... ..0. = ECN-Capable Transport (ECT): 0 .... ...0 = ECN-CE: 0 Total Length: 186 Identification: 0x0000 (0) Flags: 0x00 0... = Reserved bit: Not set .0.. = Don't fragment: Not set ..0. = More fragments: Not set Fragment offset: 0 Time to live: 64 Protocol: UDP (0x11) Header checksum: 0x4701 [correct] [Good: True] [Bad : False] Source: 63.63.63.63 (63.63.63.63) Destination: 90.90.90.90 (90.90.90.90) User Datagram Protocol, Src Port: 65535 (65535), Dst Port: 65535 (65535) Source port: 65535 (65535) Destination port: 65535 (65535) Length: 166 Checksum: 0xcb6f [correct] [Good Checksum: True] [Bad Checksum: False] Data (158 bytes)

Figure 21 – Protocol Trace – Smartbits Untagged Traffic

7. Conclusion As illustrated by these Application Notes, Avaya QoS tagging, via Avaya Communication Manager administration, is processed correctly by a Cisco MPLS core network. This results in prioritizing of Avaya VoIP call traffic as well as Avaya G450 Media Gateway traffic.




8. References 8.1 Avaya Product Documentation The following documents can be found at http://support.avaya.com: [1] Administration for the Avaya G450 Media Gateway, 03-602055, Issue 1, January 2008. [2] Administrator Guide for Avaya Communication Manager, 03-300509, Issue 4.0, Release 5.0, January 2008. 8.2 Avaya Application Notes The following documents can be found at http://support.avaya.com: [3] Configuring Avaya Communication Manager with Avaya G350 Media Gateway in a Cisco MPLS Network - Issue 1.0 8.3 Cisco Documentation The following document can be found at http://www.cisco.com: [4] Cisco IOS Multiprotocol Label Switching Configuration Guide, Release 12.4. [5] Quality of Service for Multi-Protocol Label Switching Networks. [6] Cisco IOS Quality of Service Solutions Command Reference, Release 12.2




©2008 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]

G450_QOS_MPLS

Documents

Transcript of G450_QOS_MPLS