OAM report overview

General information

OAM reports show aggregated latency and loss information based on results of OAM testing. Information in the report inputs is optimized to reflect the configuration of the test in the NFM-P GUI, for example, only configured forwarding classes appear in the inputs.

Forwarding classes are highlighted when latency or packet loss exceeds thresholds:

• Orange highlighting indicates that the maximum RTD is double or more the value of the average RTD

• Yellow highlighting indicates that the loss is greater than 0% but less than 5%.

• Red highlighting indicates that the loss is greater than 5%.

Note: Gaps may appear in line graphs: these indicate a time during which no data was available.

Both the NE name and its IP address display in the report.

Drill-down reports

All OAM reports can be run from the main OAM reports folder. Some reports can also be run as drill-downs by clicking on a data point in another report.

The following table shows the drill-downs available for OAM reports. Each level of indentation indicates a drill down. For example, OAM-PM Network Site Summary is a drill-down report from an OAM-PM Network Summary report. OAM-PM Latency and OAM-PM Loss reports are drill-downs from an OAM-PM Network Site Summary report.

Table 13-1: Available drill-downs for OAM reports

OAM-PM Network Summary
	OAM-PM Network Site Summary
		OAM-PM Latency OAM-PM Loss
OAM-PM Service Summary
	OAM-PM Service Site Summary
		OAM-PM Service Site
			OAM-PM Latency OAM-PM Loss
OAM-PM Multiple Session View
	OAM-PM Bins and Delay
OAM-PM Composite Service Summary
	OAM-PM Composite Service View
		OAM-PM Service Site Summary
OAM-PM Bin Groups
	OAM-PM Latency OAM-PM Loss
OAM-PM Top N Worst Sessions
	OAM-PM Latency OAM-PM Loss
Ping Network Summary
	Ping Network Site Summary
		Ping Latency Ping Jitter & Loss
Ping Service Summary
	Ping Service Site Summary
		Ping Service Site
			Ping Latency Ping Jitter & Loss
Ping Top N Worst Results
	Ping Latency Ping Jitter & Loss

Supported standards

The following table describes the test types supported by the reports, and alternate test names where they exist.

Table 13-2: Supported standards for OAM testing

Reports	Standards or alternate test names
OAM-PM Bins and Delay OAM-PM Composite Service Summary OAM-PM Latency OAM-PM Loss OAM-PM Multiple Session View OAM-PM Network Site Summary OAM-PM Network Summary OAM-PM Service Summary OAM-PM Service Site Summary OAM-PM Service Site	MEF35

Prerequisites

The following must be configured for OAM reports to be created:

• OAM testing can be configured in the NFM-P or the NSP.

  See the following in the NSP NFM-P Classic Management User Guide for information about the tests and policies that provide data for OAM reports:

  • PM bin group policies

  • Configuring a CFM two way delay OAM diagnostic test from the STM

  • Configuring a PM session OAM diagnostic test from the STM

  • Configuring a CFM DMM session OAM diagnostic test from the STM

  • Configuring a TWAMP-Light session OAM diagnostic test from the STM

  • Creating and running an ICMP ping OAM diagnostic test from the STM

  • Creating and running a VCCV ping OAM diagnostic test from the STM

• The OAM test results must be stored in the auxiliary database. To enable auxiliary database storage of OAM test results, you must enable the oam-test-results parameter in the samauxdb section of each NFM-P main server configuration. See the NSP Installation and Upgrade Guide for information about using the samconfig utility to modify the NFM-P configuration.

• OAM statistics must be collected using an accounting policy:

  • ETH-CFM Two-Way Delay, ICMP Ping, and VCCV Ping tests require an NE Schedulable Tests policy.

  • ETH-CFM Session and TWAMP-Light Session tests require a Complete-PM policy.

• To view the reports for granularities other than raw data, the OAM aggregation rules must be enabled; see How do I configure analytics aggregation?.