Quality of Experience. Mike Fitzgerald. # AvayaATF. Quality of Experience. QoS , Avaya Diagnostic Server, SLAMon ™ and tools for a better user experience. Problem Scenario. New Hires Report Degraded Video Quality to IT During Recent V ideo T raining S essions. New Hires. HQ. - PowerPoint PPT Presentation
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Problem ScenarioNew Hires Report Degraded Video Quality to IT During Recent Video Training
Sessions
HQ
Paul
New Hires
New Hires
1. An Insurance company regularly conducts remote PC-based video training exercise for their new hires across multiple sites that don’t require the use of Avaya IP phones.
2. The company streams video from a central training system at HQ to New Hires at each of the remote sites.
Problem ScenarioNew Hires Report Degraded Video Quality to IT During Recent Video Training
Sessions
Paul
1. The New Hires have complained that in the past training sessions, some sites (but not all) have experienced degraded video quality during the sessions. 2. Now what?.
Avaya Diagnostic Server with SLAMon™Empowers customers with proactive tools
Intelligent, proactive agents embedded in Avaya equipment Local Interface delivers end to end network visibility for voice, video and data
traffic Identifies and isolates QoS problems across each network hop using synthetic
sessions and defined traffic priority levels Provides graphical reporting of latency, delay, jitter, and estimated MOS Proactive Alarms based on thresholds sent to multiple destinations – enterprise
NMS, Avaya
Provides Customers with Early Warning Signs for Preventative Actions
Avaya Diagnostic Server 2.0 Install ADS 2.0 can be delivered in 3 ways
New install Standalone server ADS 2.0 OVA similar to the VE 1.0 SAL OVA
Upgrade of an existing SAL GW Assumes server meets hard drive, processing and memory needs of the
applications Migration would be required if the above is not met
Standalone Server Hardware recommendations
Application RAM CPU Hard Drive Free space Minimum Recommended Minimum Recommended Minimum RecommendedOnly SAL GW 2 GB 4 GB single core dual core 10 GB 40 GBOnly SLA Mon 4 GB 8 GB dual core quad core 40 GB 180 GBBoth SAL GW and SLA Mon 4 GB 8 GB dual core quad core 50 GB 220 GB
The disk space requirements that will be checked by the ADS R2 Installer
If /opt and /var are located in same partition then check “free” space as follows:Partition Minimum Recommended"/" 50 GB 220 GBIf /opt and /var are located in two different partitions then check “free” space as follows:/opt/ 10 GB 20 GB/var/ 40 GB 200 GB
To configure SLA Mon agent:enableconfigure terminalapplicationslamon agent ip address {A.B.C.D}slamon oper-mode enable <enable the agent>slamon server ip address {A.B.C.D}
See this deck’s appendix and networking product documentation for full listing of SLA Mon-related commands.
The ultimate objective is to create a logical topology within SLA Mon that matches the physical network topology. This requires knowing the network topology and where the agents are located in that topology.
Santa Clara’s IP address range is large enough that it requires 4 discovery entries. The other cities only require a single entry.
Creating zones for the cities puts the individual IP subnets into a display grouping, explained in coming slides.
Warning: Zone assignments made here overwrite the zone assignments on the Zone Management page.
/21 is the smallest mask permitted. This particular entry scans 10.1.0.1 thru 10.1.7.255 to discover agents. This is nothing more than an IP address range. It implies nothing about how this range is subnetted in the network. The individual subnet information (subnet mask and default gateway) is received from the agents.
3. Maximize these unless you’re concerned about too much test traffic on the network.1. Add new pattern name.
Test runs for 1sec, data is compiled and sent to SLA Mon server (takes up to 2sec), and test runs again. This cycle may vary depending on how many total tests the SLA Mon server is managing.
2. Select test pattern for editing.
4. Select G.729 or G.711 (G.729 recommended for most cases).
For each test pair, the G.729 pattern puts roughly one G.729 call’s worth of traffic (<30kbps) onto the network. Likewise the G.711 pattern puts <100kbps onto the network.
1. Select the default pattern, which is a full-mesh pattern.
2. Export the full-mesh pattern to a spreadsheet.3. Manually prune the spreadsheet.
4. Import the pruned spreadsheet test pattern into a new pattern and save the pattern.
The default test pattern is 1) all zones to all zones (full mesh of zones); 2) full mesh of subnets within a zone; 3) full mesh of subnets not assigned to a zone; 4) full mesh of unassigned subnets to zones (subnet to zone tests).
Black means no agents on that subnet could be reached to execute the test – agent(s) or network down.
Select the “Failed” traffic parameter.
Red means the agent could be reached, but test execution failed – agent is malfunctioning or overloaded with tests. In this case SLA Mon will attempt to find another agent to execute the test.
Detailed Matrix for a Specific Test Pair For the past hour, all of the traffic type and traffic parameter combinations from the summary matrix are shown here for this specific test pair. Color codes are the same as the summary matrix.
DetailedGraphsSelect time period to view, up to 5 days and down to 5min (default last hour).
Select traffic parameter and traffic type.
administered thresholds
To view a specific time window within the graph, zoom in and out with a mouse click-drag-release motion. Double-click to return to full graph view for selected date/time period.
Mouse over a spot on the graph (cross hairs will appear) to see specific data on that point.
Hop-by-Hop QoS MonitoringAudio traffic left marked as DSCP 46. Changed to 0 at first hop. No more QoS treatment from that point on.
Temporarily changed to match the service provider’s class of service markings while in the MPLS cloud. This is a common practice.
both directions charted Traceroute is the underlying utility used to monitor hop-by-hop QoS, and it is possible for the router or destination endpoint to not respond to the traceroute.
Important: When executing the script using EDM, do not run other commands while the script is in progress, because this slows down the execution. EDM can time-out while waiting for a response and even when a time-out occurs, the script execution continues on EDM.
Problem ScenarioNew Hires Report Degraded Video Quality to IT During Recent Video Training
Sessions
HQ
Paul
New Hires
New Hires
1. An Insurance company regularly conducts remote PC-based video training exercise for their new hires across multiple sites that don’t require the use of Avaya IP phones.
2. The company streams video from a central training system at HQ to New Hires at each of the remote sites.
Use Case SLAMon™New Hires Report Degraded Video Quality to IT During Recent Video Training
Sessions
HQ
Paul
New Hires
New Hires
SLA MonTM Server
Network Monitoring
Endpoint Diagnostics
Ethernet RoutingSwitch
Agent
1. An Insurance company regularly conducts remote PC-based video training exercise for their new hires across multiple sites that don’t require the use of Avaya IP phones.
2. The company streams video from a central training system at HQ to New Hires at each of the remote sites.
Use Case SLAMon™New Hires Report Degraded Video Quality to IT During Recent Video Training
Sessions
Paul
SLA MonTM Server
Network Monitoring
Endpoint Diagnostics
1. The New Hires have complained that in the past training sessions, some sites (but not all) have experienced degraded video quality during the sessions. 2. Each of the remote sites and their HQ have Avaya Ethernet switches and they have an SLA Mon server at HQ.
Use Case SLAMon™New Hires Report Degraded Video Quality to IT During Recent Video Training
Sessions
Paul
SLA MonTM Server
Network Monitoring
Endpoint Diagnostics
1. Paul uses Network Monitoring feature of SLA MonTM Server to review historical data and sees that there is some delay between the HQ and Branch site link. 2. He looks at the Hop by Hop QoS reports and sees that the DSCP of the video traffic is being remarked at some point. 3. He knows that he has configured the video traffic to DSCP 26 but somehow it’s being remarked to 0 and therefore not getting preferential treatment.
Use Case SLAMon™New Hires Report Degraded Video Quality to IT During Recent Video Training
Sessions
Paul
Ethernet RoutingSwitch
Agent
Ethernet RoutingSwitch
Agent
HQ
1. He calls the SP to ask what is happening. After the SP investigates, they realize that they had not configured the network to give preferential treatment to video traffic and fixed the error. Problem solved! 2. The next training session goes off without any problems.
Intelligent, proactive agents embedded in Avaya equipment Local Interface delivers end to end network visibility for voice, video and data
traffic Identifies and isolates QoS problems across each network hop using
synthetic sessions and defined traffic priority levels Provides graphical reporting of latency, delay, jitter, and estimated MOS Proactive Alarms based on thresholds sent to multiple destinations –
enterprise NMS, Avaya
Provides Customers with Early Warning Signs for Preventative Actions
3. Assign all IP subnets in the city of Sacramento to zone “Sacramento.”
5. The selected IP subnets will appear in the Sacramento zone and be grouped for display.
2. Select zone to add subnets to.
4. Or add individual IP subnets in the city of Sacramento to zone “Sacramento.”
If agents were discovered on the Discovery tab w/o a zone designation, they can be assigned to a zone after discovery. Likewise, a zone assigned at discovery time can be changed after discovery.
Warning: Any zone changes made here do not transfer to the Discovery tab. If agents are re-discovered on the Discovery tab using the previous discovery entries, they will overwrite the zone assignments on this page.
Note: SLA Mon identifies IP subnets by the default gateway reported by the agent, instead of the familiar network/mask designation. This may change in the future, but for now this is how IP subnets are identified.
Zones Explained A zone is a way to group IP subnets for display purposes, to more easily see inter-
zone test results and intra-zone test results. We can create a zone of one city. The IP subnets in the Santa Clara office can be
grouped into a zone called “SantaClara_Zone.” We can also create a zone of multiple cities.
We can create a California zone and a Texas zone and put select cities into each zone. Or we can create a USA zone and an Australia zone and put select cities into each zone.
We can create zones within the same city. Within a college campus in one city, we can create an “Engineering” zone and a “Fine
Arts” zone and a “Sociology” zone. Within a corporate campus we can create a “Bldg A” zone and “Bldg B” zone. Within a large building we can create a “Floor 1” zone and a “Floor 2” zone.
An administrator can create zones to suit the purposes of the enterprise, to make the network performance displays more manageable. We want to see at a high level the tests between the zones. We want to see separately the tests between subnets within a zone. To do that we drill
down into that zone. This grouping is only for display purposes. All tests are between IP subnets, not
5x5 summary matrix of a network that contains 5 locations, 2 of which are zones:- Europe zone- North America zone- Bangalore subnet- London subnet- Sydney subnet
There is a full mesh of network tests running, from every location to every location. (These tests will be explained in more detail later.)
Zone Limitations The zone hierarchy is limited to one level.
We cannot create a zone consisting of multiple zones. Right now we don’t anticipate a need for this.
Only one test can be created between a zone pair. This is an intentional limitation. Suppose we try to create these two tests:
10.1.1.1 (SantaClara_Zone) to 10.10.1.1 (Toronto_Zone) 10.1.2.1 (SantaClara_Zone) to 10.10.2.1 (Toronto_Zone) The second test will be blocked by SLA Mon.
Because we segregated the display into zones, we cannot show multiple test results for the same zone pair.
If there were no zones, these tests would be permitted as individual subnet tests. The zones need to be created such that only one test is required for any zone pair.
Note- Bypass mode is used to run tests between two switches without an SLA Mon Server. This operation is not covered in the ADS R2 KTK. Refer to ERS3500 5.1.1 or ERS5600 6.6 Troubleshooting Technical Transfer for guidance to running Bypass mode