quality of experience

© 2014 Avaya Inc. Avaya – Confidential & ProprietaryDo not duplicate, publish or distribute further without the express written permission of Avaya. #AvayaATF

March 25 – 27th, 2014 І Orlando, FL

#AvayaATF© 2014 Avaya Inc. Avaya – Confidential & ProprietaryDo not duplicate, publish or distribute further without the express written permission of Avaya.

Quality of ExperienceMike Fitzgerald

#AvayaATF

© 2014 Avaya Inc. Avaya – Confidential & ProprietaryDo not duplicate, publish or distribute further without the express written permission of Avaya. #AvayaATF#AvayaATF

Quality of ExperienceQoS, Avaya Diagnostic Server, SLAMon™ and tools for a better user experience

© 2014 Avaya Inc. Avaya – Confidential & ProprietaryDo not duplicate, publish or distribute further without the express written permission of Avaya. #AvayaATF 3

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.



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?.

HQ

New Hires

New Hires




Avaya Diagnostic Server and SLAMon™ Overview


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


Monitor network performance:Packet loss

Jitter

Delay

Monitor hop-by-hop QoS integrity:

Emulate three traffic types:

Voice

Video

Data

Keep a 60-day historyof the network performance

statistics to correlate product/solution disruptions

to network disruptions

Network Monitoring – Spring 2014

Is the DSCP marking preservedend-to-end?

At which hop is the markingbeing changed?

Using synthetic test patterns that do not load the network…


How SLA MonTM Technology Works

Intelligent agents embedded in Avaya products and controlledby the SLA Mon™ server to provide advanced capabilities

ERS switch

agent

ERS switch

agent


Network Monitoring – Summary Matrix

Holistic view of all network links being monitored


Network Monitoring – Detailed Graphs

View the details of a specific location pair Select the desired time period, traffic type,

and measured traffic parameter


Network Monitoring – Hop-by-Hop QoS

Is the DSCP marking preserved end-to-end? At which hop is the marking being changed?


Proactive AlarmingWhen Network Thresholds Are Breached

SNMP traps sent to multiple destinations – enterprise NMS, Avaya


Products w/ Embedded SLA Mon Agent




Avaya Diagnostic Server Installation Requirements


New Install Packages for Avaya Diagnostic Server

SoftwareTo install on customer’s server

or virtual server

We will have a download site linking to PLDS

VMware OVATo install on customer’s Vmware

environment

We will have a download site linking to PLDS

iON ServerFor customers who want

a low-cost appliance

Will be sold through Select Product Program, same as today

SVMOn System Platform product templates

that support the latest SVM TBD

Note: SVM does not support Network Monitoring


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




Network Monitoring and Endpoint Diagnostics




SLA Mon™ Agent Enablement


Enable the Agent in ERS and VSP Switches

Enable the agent and assign an IP address. By default the agent uses the switch/stack IP address if a specific agent

address is not configured. Note: Commands are common across ERS 3500, 4000, and 5000

families. To view current configuration:

enable <enter privileged exec mode>show application slamon agent

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.


Configuring SLA Mon via ACLI (continued)




Agent Discovery


Obtain Network Topology

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.


Discover the Agents

2. Add an IP address range to scan for agents. Add a zone designation (optional).

3. Select one or more ranges previously entered, and run discovery.

1. Populate location.

SLA Mon polls all the IP addresses in the range to discover agents. This is surprisingly quick.


Discover the Agents (zoom in)

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.


See Discovered Agents

All discovered agents are listed.In Beta2 & GA loads: Blank means discovered; icon means manually disabled.

Note: In ADS 2.5 we will add a heartbeat mechanism and return the colored icons to indicate the health & reachability of the agents.




Test Administration


Set DSCP Values

Check if enterprise uses video; uncheck otherwise.

Set the values used in the enterprise.


Set Alarm Thresholds

180ms is the commonly accepted value for one-way delay.

4.0 - 4.5 is considered PSTN toll quality. Down to 3.6 is considered business quality.

e-MOS is estimated mean opinion score, calculated using the ITU-T G.107 recommendation.

These are commonly accepted values for jitter and loss, though perhaps a bit low in practicality.

Set based on the enterprise’s tolerance levels.

An alarm is triggered if the threshold is breached this many times in an hour span.


Create a Test Pattern

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.


Add Tests Manually to the Pattern

All 3 traffic types are added.

Select subnet1 and subnet2 and add test pair. Repeat as necessary. Save pattern.


Add Tests Using Bulk Tool

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).


Execute Test Pattern

Stop the current test pattern, select a new pattern, and start.

View test pairs for selected test pattern.

Errors could be caused by:• Agent malfunction, or agent down.• Not enough agents in a subnet.• Communication path disrupted between

SLA Mon server and agent.




Network Performance Monitoring


Summary Matrix for Multiple Test Pairs

Rows and columns are numbered, but only the rows are labeled with the subnet or zone.

Click on a cell to see the details of that test pair.

Select traffic type and measured traffic parameter.

Prune the matrix by selecting locations/zones to view.

Color Code:

• Green: all tests in past hour were below threshold.

• Amber: at least one test in past hour exceeded threshold, but not the latest test executed.

• Red: latest test executed exceeded threshold.

• Grey: no test administered.• Black: unable to execute

administered test; agent or network down, or agent in distress.

• Blue: zone, click to see intra-zone test results.

• White: location to same location test not applicable.


Agent/Network Down vs. Agent in Distress

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.

network performance plot

both

dire

ction

s gra

phed


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.




SWITCH Bypass Mode


EDM SLA Monitor Configuration Menu

Mandatory options

IPv4 only

If values are unchanged stack/ switch IP and default port will be used

Avaya Diagnostic ServerConfiguration options not required for bypass mode

Select NTR or RTP to setup of desired test

Navigate to Configuration Serviceability SLA Monitor


SLA Mon Bypass TestingEDM - NTR Testing

To Run Select desired test OwnerId and Results

Select NTR Insert to configure NTR test

Insert NTR test configuration


SLA Mon Bypass TestingEDM - NTR Test Results

NTR configuration displayed

Test results

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.


SLA Mon Bypass ModeACLI – NTR test configuration and results

Results displayed after ntr command issued:

3524GT-PWR+(config-app)#slamon ntr 47.17.25.119 46 attempts 2 period 200000 Default values will be used

if values not set




Alarming


ADS 2.0 – Alarming

Two administrable tabs are available in the SLA Mon server that are related to alarming. SNMP Traps tab – Used to define an SNMP trap destination,

alarm generation, and alarm severity. Alarming tab – Used to configure “Thresholds” and “Strike” rates

against network Delay, Jitter, Packet Loss, and e-MOS. The SNMP Traps tab is where you define which alarms

should be sent out as traps as well as where you assign severity to that category of alarm.

You can configure different alarm rules per NMS destination.


ADS 2.0 – Alarming Diagram


ADS 2.0 – Monitoring and Diagnostics (Continued)

SLA Mon – SNMP Traps Access the SNMP Traps tab via “Admin SNMP Traps”


ADS 2.0 – Monitoring and Diagnostics (Continued)

Enter the IP address of the NMS server or SAL gateway then click “Add New”

SLA Mon – SNMP Traps [Add New]


ADS 2.0 – Monitoring and Diagnostics (Continued).

Define your NMS and alarming details.

SLA Mon – SNMP Traps [Trap Details]

NMS server details [Blue]

Alarm generation and severity details [Red]




Problem Scenario Revisited



Sessions

HQ

Paul

New Hires

New Hires




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




Agent


Agent



Sessions

Paul

SLA MonTM Server

Network Monitoring


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.


Agent


Agent

HQ

New Hires

New Hires


Agent



Sessions

Paul

SLA MonTM Server

Network Monitoring


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.


Agent

DSCP 26


Agent

HQ

New Hires

New HiresDSCP 0


Agent



Sessions

Paul


Agent


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.

Service Provider

New Hires

New Hires

DSCP 26

DSCP 26


Agent


Network Monitoring – Release 2 (2014) 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

© 2014 Avaya Inc. Avaya – Confidential & ProprietaryDo not duplicate, publish or distribute further without the express written permission of Avaya. #AvayaATF#AvayaATF

Thank You!


BE SURE TO TWEET YOUR FEEDBACK ON THIS PRESENTATION

#AvayaATF

58

BEST OF ATF SPEAKER AND TEAM AWARD

Winners will be announced at closing of event

#AvayaATF




Zone Management(Optional)


Zone Management

1. Add new zone name.

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

between zones.


Summary View of Locations and Zones

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.)

Click on blue cell to drill into zone.


Drill into the Zones

When we drill into the North America zone we see that there are two subnets – Montreal and Sacramento.

When we drill into the Europe zone we see that there are two subnets – Munchen and Salzburg.


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.




Appendix: ERS Commands


Configuring switch-based SLA Mon agent via ACLI

Note- commands are common across ERS3500, 4000, 5000 families.


Configuring SLA Mon via ACLI cont.



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


Configuring SLA Mon via ACLI (Continued)


Summary of SLA Mon Agent commands via CLI

quality of experience

Documents

degraded video quality

video traffic

recent training sessions

company streams video

avaya diagnostic server

use of avaya ip phones

avaya ethernet switches

past training sessions