Introduction
Tracks throughput at a NIC level for each Media Resource IP Interface over a selected period of time. Measures datagrams transmitted and received on the network for the selected Media Resource.
Uses
The report can be used:
- To identify over an extended time period normal Media Resource throughput.
- As an indicator of potential problems.
Identifying sudden changes away from established traffic trends can provide an early warning and a chance to mitigate otherwise unseen issues.
Use this report in conjunction with Availability Management to identify potential issues.
Examples
Example 1
To cater for high levels of traffic, the customer below has multiple Media Resource resources in the same Port Network (and same Network Region).
Given this configuration, and the load sharing algorithms inherent in Avaya Aura Communication Manager, the traffic loading should be very even between resources. Any differences in the resulting load are indicative of potential problems.
The graphs below indicates at a glance that the design is working as expected.
Example 2
This graph depicts a common issue experienced by voice applications running on an IP network with one-way speech. There is a visible difference in transmitted datagrams compared to received datagrams, which is clearly representative of a fault.
As VSM is measuring the data flow on the NIC and the same codec is used for transmit and receive, the data patterns should be symmetrical. Symmetrical data rates represent normal performance with a Media Resource; asymmetrical data represents a problem.
In these situations there will be no alarm generated at the SNMP or alarm log level, meaning this sort of incident will normally be reported by the End User Customer - with all of the inherent delays this brings about.
With VSM the problem is immediately apparent to the people that matter. This is one of the key strengths that managing platforms at an application level brings, as the human latency is removed.
