Use > Monitor with the NNM iSPI Performance for QA > Access QA Probe Details

Access QA Probe Details

This topic includes the following sections:

The QA Probes view displays all the QA probes configured in the network elements. The QA probes are discovered by the NNMi polling process.

To launch the QA Probes view:

  1. Log on to NNMi console using your user name and password.
  2. Click the Quality Assurance workspace. The Quality Assurance tab expands to display the views.
  3. Click the QA Probes view. The view displays all the QA probes discovered in your network along with some key attributes for each QA probe.
    By default, this information is refreshed every 300 seconds, or 5 minutes.

The NNM iSPI Performance for QA supports Multi-Tenancy architecture configured in NNMi. The security group defined for a node in NNMi is also applicable for the probes of the node in NNM iSPI Performance for QA. This implies that all QA probes cannot be viewed by all users. For example, if a user has access to a set of nodes, the user can view only the QA probes configured on those nodes.

To manage large number of QA probes, use the QA Groups list to filter the QA probes based on various QA groups. As you type, the auto-complete feature lists the matching QA Groups. You can select a QA Group name from the list.

You can also perform a few other actions on probes by following the steps given below:

  1. Right-click a probe and select Quality Assurancefrom the sub-menu.
  2. Choose an option from the sub-menu to perform an action you want on the probe.

Key Attributes of the QA Probes View

The QA Probes view displays the following key attributes for each QA probe:

Attribute Name Description
Status

The status of the QA probe. NNM iSPI Performance for QA calculates the status based on the polling status of the nodes and the threshold states. A QA probe can have one of the following statuses :

  • Normal
  • Warning
  • Major
  • Critical
  • Unknown
  • Disabled
  • Not Polled
  • No Status
Name The name of the discovered QA probe configured on the network device.
Owner The name of the discovered QA probe's owner.
Service

The type of the discovered QA probe.

Some of the QA probe types that the NNM iSPI Performance for QA recognizes are:

  • UDP Echo
  • ICMP Echo
  • UDP
  • TCP Connect
  • VoIP
  • HTTP
  • DNS
  • DHCP
  • Oracle
  • HTTPS
Device Model The device model name (as discovered by NNMi) of the probe's source node.
Source The source device on which the probe is configured.
Destination The destination device on which the probe is configured.
Source Site

The source site to which the configured probe is associated.
Destination Site The destination site to which the configured probe is associated.
RTT

The round-trip time used by the selected QA probe.

Displays one of the following threshold states for the metric:

High

Nominal

Low

Not Polled

Unavailable

Threshold Not Set

None
Jitter

The delay variance for a data packet to reach the destination device or site.

Displays one of the following threshold states for the metric:

High

Nominal

Low

Not Polled

Unavailable

Threshold Not Set

None
PL (Packet Loss)

The percentage of packets that failed to arrive at the destination.

Displays one of the following threshold states for the metric:

High

Nominal

Low

Not Polled

Unavailable

Threshold Not Set

None
Manager Specifies whether the NNMi management server is Local or specifies the name of the Regional Manager.
Tenant Specifies the NNMi tenant selected for the QA probe.

The RTT, Jitter, and PL columns display the most recent network performance states. Apart from this, MOS metric is also considered for change in the network performance state.

The following table describes the threshold state or network performance state values:

Threshold States
State Description
High

For Count-Based Threshold Configuration:

Indicates that the measured value of the metric is above the configured High Value and recurs for the consecutive number of times specified in the Trigger Count.

For Time-Based Threshold Configuration:

Indicates that the measured value of the metric is above the configured High Value and this high value persists for the specified High Duration within the High Duration Window.
Nominal

Indicates that the measured value of the metric is within the normal healthy range.
Low

For Count-Based Threshold Configuration:

Indicates that the measured value of the metric is below the configured Low Value for the consecutive number of times specified in the Trigger Count.

For Time-Based Threshold Configuration:

Indicates that the measured value of the metric is below the configured Low Value and this low value persists for the specified Low Duration within the Low Duration Window.

Typically, this threshold state is applicable for metrics such as Mean Opinion Score (MOS).
Not Polled

Indicates that the metric is intentionally not polled.

Some of the possible reasons are:

  • The parent Node or Interface is set to Not Managed or Out of Service.

  • The metric is not supported for the particular entity.

    For example, for an ICMP probe, Jitter and Packet Loss metrics are not supported and so the threshold states for these metrics are displayed as "Not Polled".
Unavailable Unable to compute the metric, or the computed value is outside the valid range.
Threshold Not Set Indicates that the threshold is not set for the metric.
None

For Count-Based Threshold Configuration:

Indicates that the measured value of the metric is zero, and recurs for the consecutive number of times specified in the Trigger Count.

For Time-Based Threshold Configuration:

Indicates that the measured value of the metric is zero and this zero value persists for the specified duration within the High or Low Duration Window (depending on the metric).

If you launch the Status Poll command from NNMi, it also triggers a corresponding status poll for

NNM iSPI Performance for QA

.

Analysis Pane

To view the Analysis pane, click a QA probe in the QA Probes View. The Analysis pane of the selected QA Probe appears.

In the Analysis pane, you can view the summary, Threshold State, Baseline State, Latest Polled Values, and Performance panels.

The Threshold State panel displays whether the threshold is configured for the selected probe or not. It also indicates whether the threshold is configured for a site or a probe. If a threshold is configured, you can view the summary of the threshold configuration details. The configured threshold value and rearm value are displayed in either milliseconds or microseconds based on the probe configuration. The Threshold State pane enables you to check the configured values and the threshold violations, if any.

If the threshold is not configured, you can use the Configure Threshold link provided in this pane to configure the threshold.

The Baseline State panel displays whether Baseline Monitoring is configured for the selected probe or not. If baseline monitoring is configured, you can view the metric, baseline state, upper norm deviation, and lower norm deviation.

The Latest Polled Values panel displays the last five polled values for the relevant metrics, which may be RTT (ms or µs), two-way jitter (ms or µs), two-way packet loss, and MOS metric. You can also view the last polled time. If the last polled time is not available, it displays the message—Polling Not Complete.

The Performance panel enables you to analyze the performance faults for the selected probe, in the form of graphs. The graph shows the following information:

  • RTT value of the selected probe
  • Reachability of the selected probe

You can easily monitor and analyze the performance of the probe, from the color of the status. Whenever any problem arises, you can view the status in the Performance panel. The status of the probe enables you to easily determine the root cause of the fault.

The following table indicates the status information:

Probe Status Color in the graph
Normal Normal
High, Low Major
Critical Critical
No Status No Status
Unavailable, Unknown Unknown
Not Polled, Threshold not set, Not defined Disabled

View Probe Status

The QA Probe Form displays the details for the selected QA probe and the configurations associated with it.

QA Probe Form: Left Panel

The left panel of the QA Probe form displays the following:

QA Probe Details

This section displays the following:

Basic Attributes: QA Probe Details
Attribute Description
Status

Status of the QA probe.

A QA probe can have one of the following statuses:

  • No Status
  • Normal
  • Disabled
  • Unknown
  • Warning
  • Major
  • Critical
Name

Name of the selected QA probe.

For QA probes, the QA probe name is derived from the 'TAG' field of the QA probe definition.

If the tag field is not present, the QA probe name is derived by appending the source node name, the target IP address, and the admin index.

For RFC QA probes, the name is derived from the RFC MIB.

The QA probe names cannot be blank.
Owner Name of the QA probe owner.
Service

Type of the QA probe.

Possible service types are:

  • UDP Echo
  • ICMP Echo
  • UDP
  • TCP Connect
  • VoIP
  • HTTP
  • DNS
  • HTTPS
  • Oracle
  • DHCP
Device Model The device model name (as discovered by NNMi) of the probe's source node.
Admin Index

The unique index ID given for each QA probe.

Available only for QA probes.
Manager Specifies whether the NNMi management server is Local or not. The name of the Regional Manager is displayed if the NNMi management server is not local.
One Way HW Time Stamp Enabled Specifies whether the one way hardware time stamp is enabled or not for the QA probe.

Source/Destination Info 

This section displays the following:

Basic Attributes: Source/Destination Info
Attribute Description
Source

Name of the starting device from which the QA probe is configured.

Click and select Show Analysis or Open to display the Node Form.

The Node: <Node Name> form opens. Select the QA Probes tab to display the QA probes initiated from this node.
Source IP Address IP address of the starting device from which the QA probe is configured.
Source Interface

Interface name to which the QA probe is configured.

For information on configuring source interfaces, see Configuring Source Interface for a QA Probe.
Source Site Name of the site where the source device resides.
Source Port Port number of the starting device from which the QA probe is configured.
Destination Name of the end point on which the QA probe is configured.
Destination IP Address IP address of the device at the end point on which the QA probe is configured.
Destination Site Name of the site where the destination device resides.
Destination Port Port number of the device at the end point on which the QA probe is configured.
Measurement Precision

Whether the QA probe retrieves the network performance in microseconds or in milliseconds.
Timeout Maximum time the source node waits for a response from the destination node before stopping the request.
Frequency Frequency of the QA probe in seconds.
TOS Type of Service specified in an IP packet header that indicates the service level required for the packet.
VRF

Virtual Routing and Forwarding (VRFs) tables defined on the source node.

This field is populated only if the test is configured with VRF(s).
Discovery State

Discovered state of the source node.

Possible values are as follows:

Completed - All the analysis are completed and the QA probes are discovered.

In Progress - The discovery process is still gathering network information or the QA probe data.
Last Discovery Completed

Date, time, and time zone of the last discovery.
Management Mode

Whether the source node is managed or not.

Possible states are as follows:

  • Managed: Indicates that the node is managed.
  • Not Managed: Indicates that the node is not managed on purpose.
  • Out of Service: Indicates that a node is unavailable because it is out of service.

Probes Form: Right Panel

The right panel of the QA Probes form displays information about the selected QA probe. The panel consists of the following tabs:

Analysis Pane

The Analysis pane enables you to view the Summary, Threshold State, and Latest Polled Values panels.

The Threshold State panel displays whether the threshold is configured for the selected probe or not. It also indicates whether the threshold is configured for a site or a probe. If a threshold is configured, you can view the summary of the threshold configuration details. The configured threshold value and rearm value are displayed in either milliseconds or microseconds based on the probe configuration. The Threshold State pane enables you to check the configured values and the threshold violations, if any.

If the threshold is not configured, you can use the Configure Threshold link provided in this pane to configure the threshold.

The Latest Polled Values panel displays the last five polled values for the relevant metrics, which may be RTT, two-way jitter, or two-way packet loss metric. If the last polled time is not available, it displays the message "Polling Not Complete".

Probe State

The State tab in the QA Probes Form displays information about the last run of the QA probe.

Attributes: State Tab
Attribute Description
Administrative State

Administrative State condition returned by the QA probe.

The QA probe status is derived from the SNMP polling results for Administrative State, as well as from any conclusions.
Operational State

Operational State condition returned by the QA probe.

The QA probe status is derived from the SNMP polling results for Operational State, as well as from any conclusions.
State Last Modified The date, time, and time zone when the QA probe state was last modified.

Threshold State

The Threshold State tab in the QA Probes Form displays a quick summary of the most recent performance of the network element on which the QA probe runs.

This tab displays only those metrics on which the administrator has configured a threshold.

When the network performance breaches a threshold depending on the count-based, or time-based threshold configuration, the Status tab displays the network element status as Major and the Incident tab displays a Critical incident raised on the network element.

This tab displays the following details:

Field Name Description
State

The threshold state of the probe. The valid threshold states are listed below:

High 

Nominal

Low

Not Polled

Unavailable

Threshold Not Set

None

For more information about the threshold states, see Threshold States.
Metric Name The name of the metric.
Type The type of threshold configured. It can be Count-Based or Time-Based.
Value This value indicates the high threshold value, measured in milliseconds or microseconds.
Rearm Value The Rearm Value is used to indicate the end of the threshold state and NNM iSPI Performance for QA clears the incident once it reaches below this value, measured in milliseconds or microseconds.
Trigger Count

Indicates after how many consecutive threshold violations NNM iSPI Performance for QA alerts the operator by transitioning the threshold state to High. This field value appears for Count-based threshold configuration.
Duration

Indicates the minimum duration for which the value must persist in a high value range for the threshold state to change to High. This field value appears for Time-based threshold configuration.
Duration Window Indicates the duration of the window within which the high duration criteria must be met. This field value appears for Time-based threshold violations.

Threshold States

The following table describes the threshold states:

Threshold States
State Description
High

For Count-Based Threshold Configuration:

Indicates that the measured value of the metric is above the configured High Value and recurs for the consecutive number of times specified in the Trigger Count.

For Time-Based Threshold Configuration:

Indicates that the measured value of the metric is above the configured High Value and this high value persists for the specified High Duration within the High Duration Window.
Nominal

Indicates that the measured value of the metric is within the normal healthy range.
Low

For Count-Based Threshold Configuration:

Indicates that the measured value of the metric is below the configured Low Value for the consecutive number of times specified in the Trigger Count.

For Time-Based Threshold Configuration:

Indicates that the measured value of the metric is below the configured Low Value and this low value persists for the specified Low Duration within the Low Duration Window.

Typically, this threshold state is applicable for metrics such as Mean Opinion Score (MOS).
Not Polled

Indicates that the metric is intentionally not polled.

Some of the possible reasons are:

  • The parent Node or Interface is set to Not Managed or Out of Service.

  • The metric is not supported for the particular entity.

    For example, for an ICMP probe, Jitter and Packet Loss metrics are not supported and so the threshold states for these metrics are displayed as "Not Polled".
Unavailable Unable to compute the metric, or the computed value is outside the valid range.
Threshold Not Set Indicates that the threshold is not set for the metric.
None

For Count-Based Threshold Configuration:

Indicates that the measured value of the metric is zero, and recurs for the consecutive number of times specified in the Trigger Count.

For Time-Based Threshold Configuration:

Indicates that the measured value of the metric is zero and this zero value persists for the specified duration within the High or Low Duration Window (depending on the metric).
  • Click Open to view more information about a specific threshold state.
  • Click Refresh to refresh the Threshold State table.
  • Click Show View in New Window to open the Threshold State table in an independent window.

Baseline State

The Baseline State tab in the QA Probes Form displays only those metrics on which the administrator has configured a baseline deviation setting.

The valid baseline states for the QA probes are listed below:

  • Normal Range - The metric is within the normal range of deviation.
  • Abnormal Range - The metric is either above or below the configured normal range of the deviation.
  • Unavailable - The computed value for the metric is not found in NNM iSPI Performance for Metrics Software.
  • Unset - No baseline is computed.
  • Not polled - The metric is not polled for baseline deviations.
  • No Policy - No polling policy exists for this metric.
  • Threshold Agent Error - Indicates an error was returned by the state poller when retrieving the data from NPS.

Status

The Status tab in the QA Probes Form displays a quick summary of the iSPI object status to better determine and monitor any significant patterns in behavior and activity.

Attribute: Status Tab
Attribute Description
Status

Overall status for the current QA probe

Possible values are:

  • No Status
  • Normal
  • Disabled
  • Unknown
  • Warning
  • Major
  • Critical

In the case of sub-minute polling, the QA probe status refreshes every 2 minutes. The QA probe status gets updated based on the average polling value obtained for the last 2 minutes.

For more information about how the current status was determined, see the following topics:
Status Last Modified

Current status is calculated and set by Causal Engine.

The Time Stamp data displays the time when the status of the QA probe is last updated.
Status History

List of up to the last 30 changes in status for the selected QA probe.

This view is useful for obtaining a summary of the QA probe status so that you can better determine any patterns in traffic between the source node or site and the destination node or site.

  • Click Refresh to refresh the Status History table.
  • Click Show View in New Window to open the Status History table in an independent window.

Conclusions

The Conclusions tab in the QA Probe Form displays the results of the overall derived status. You can get a quick summary of the status and problem description retrieved by the selected QA probe.

Attribute: Conclusions Tab
Attribute Description
Status

Status of the conclusion.

Possible values are:

  • No Status
  • Normal
  • Disabled
  • Unknown
  • Warning
  • Major
  • Critical

Status reflects the most serious outstanding conclusion.
Time Stamp

Displays the time when the status of the QA probe was last updated.
Conclusions

Dynamically generated list of summary statuses of the QA probe at points in time that contributed to the current overall status of the selected QA probe.

Status is set by the Causal Engine. This view is useful for obtaining a quick summary of the status and problem description for the QA probe's most current status.

Examples of conclusions that might appear together are listed below:

  • TestUp
  • RttThresholdStateHigh
  • TwoWayPktLossThresholdStateHigh

Following examples list some of the conclusions caused by Administrative and Operational states:

Conclusions caused by Administrative State

TestTransient

  • notready
  • createandwait
  • createandgo
  • destroy

TestDisabled

  • disabled
  • Notinservice

TestUnknown

Caused by an SNMP error.

TestUnpolled

Caused when the QA probe is not polled.

Conclusions caused by Operational State

TestFailed

  • OperStateTimeout on probe
  • OperStateDisconnected on probe
  • OperStateNotConnected on probe
  • OperStateApplicationSpecific on probe
  • OperStateDnsServerTimeout on probe
  • OperStateTcpConnectTimeout on probe
  • OperStateHttpTransactionTimeout on probe
  • OperStateDnsQueryError on probe
  • OperStateHttpError on probe
  • OperStateError on probe
  • OperStateDisabled on probe

TestError

OperStateOther on probe

OperStateSequenceError on probe

OperStateOverThreashold on probe

OperStateBusy on probe

OperStateVerifyError on probe

OperStateDropped on probe

For information about how conclusions are based on the QA probe states, see Probe State.

Incidents

The Incidents tab in the QA Probes Form displays a quick summary of the problem description retrieved by the QA probe.

You can view the incidents only if you have the permissions to access the source node.

Attribute: Incidents Tab
Attribute Description
Incidents Attributes

The attributes listed in the incidents tab are same as the ones available in the NNMi Incidents form.

For more information about the Incidents attributes, see the topic NNMi Incidents Form in the Network Node Manager i SoftwareOnline help.

NNM iSPI Performance for QA generates the following incidents:

TwoWayJitterHigh

Indicates a high two-way jitter value (which is the average of the following values):

  • Positive jitter from the source to the destination
  • Negative jitter from the source to the destination
  • Positive jitter from the destination to the source
  • Negative jitter from the destination to the source

SourceToDestinationPositiveJitterHigh

Indicates a high positive jitter from the source to the destination. The jitter value is collected from the MIB. The exact MIB values that are queried may vary based on whether the latest value is polled or cumulative value is polled.

DestinationToSourcePositiveJitterHigh

Indicates a high positive jitter from the destination to the source. The jitter value is collected from the MIB. The exact MIB values that are queried vary based on whether the latest value is polled or cumulative value is polled.

SourceToDestinationNegativeJitterHigh

Indicates a high negative jitter from the source to the destination. The jitter value is collected from the MIB. The exact MIB values that are queried vary based on whether the latest value is polled or cumulative value is polled.

DestinationToSourceNegativeJitterHigh

Indicates a high negative jitter from the destination to the source. The jitter value is collected from the MIB. The exact MIB values that are queried vary based on the whether the latest value is polled or cumulative value is polled.

TwoWayPacketLossHigh

Indicates a high percentage of two-way packet loss. This value is the average of the following values:

  • Packet loss percentage from the source to the destination
  • Packet loss percentage from the destination to the source

SourceToDestinationPacketLossHigh

Indicates a high percentage of packet loss from the source to the destination.

The packet loss percentage is calculated from the ratio of the total number of packets sent to the reported number of packets lost.

The exact MIB values that are queried vary based on whether the latest value is polled or cumulative value is polled.

DestinationToSourcePacketLossHigh

Indicates a high percentage of packet loss from the destination to the source.

The packet loss percentage is calculated from the ratio of the total number of packets sent to the reported number of packets lost.

The exact MIB values that are queried vary based on whether the latest value is polled or cumulative value is polled.

RoundTripTimeHigh

Indicates a high round trip time. The exact MIB values that are queried vary based on whether the latest value is polled or cumulative value is polled.

MeanOpinionScoreLow

Indicates a low mean opinion score. The exact MIB values that are queried vary based on whether the latest value is polled or cumulative value is polled.

RoundTripTimeAbnormal

Indicates that the round trip time is beyond the normal range. This implies that the round trip time is above the configured normal range of the deviation.

TwoWayPacketLossAbnormal

Indicates the two-way packet loss is beyond the normal range. This implies that the two-way packet loss is above the configured normal range of the deviation. This value is the average of the following values:

  • Packet loss percentage from the source to the destination
  • Packet loss percentage from the destination to the source

TwoWayJitterAbnormal

Indicates that the two-way jitter is beyond the normal range. This implies that the two-way jitter is above the configured normal range of the deviation. The two-way jitter value is the average of the following values:

  • Positive jitter from the source to the destination
  • Negative jitter from the source to the destination
  • Positive jitter from the destination to the source
  • Negative jitter from the destination to the source

MeanOpinionScoreAbnormal

Indicates that the Mean Opinion Score is beyond the normal range. This implies that the mean opinion score is either above or below the configured normal range of the deviation.

TestError

This incident indicates that the QA Probe has returned an error.

TestTransient

This incident indicates that the QA Probe is in a transient state.

TestFailed

This incident indicates that the QA Probe has failed to run.

TestDisabled

This incident indicates that the QA Probe is explicitly disabled by the device administrator.

 

Attributes: Incidents Tab
Attribute Description
Severity

Severity of the incident calculated by NNMi. Possible values are:

  • Normal
  • Warning
  • Minor
  • Major
  • Critical
  • Unknown
  • Disabled
  • Not Polled
  • No Status
Lifecycle State Identifies where the incident is in the incident lifecycle.
Last Occurrence

Used when suppressing duplicate incidents or specifying an incident rate.

Indicates the time when the duplicate or rate criteria were last met for a set of duplicate incidents or for a set of incidents that has a rate criteria that was met.

If there are no duplicate incidents or incidents that have a rate criteria that were met, then this date is same as the First Occurrence Time.
Correlation Nature This incident's contribution to a root-cause calculation, if any.
Source Node

The Name attribute value of the node associated with the incident.

For more information about the node, click the Lookup icon and select Show Analysis or Open to display the Node Form.
Source Object

Name used to indicate the configuration item that is malfunctioning on the source node.

For more information about the object, click the Lookup icon and select Show Analysis or Open to display the Node Form.
Message The incident message defined by NNMi.

The global manager raises incidents for the overall health of the configured QA Probe interfaces on the network based on the threshold states collected from all regional managers.

For detailed information on NNMi incidents, see the Incident Form topic in Network Node Manager i Software Help for Operators.

Registration

The Registration tab in the QA Probe Form displays the results of the overall derived status from the database.

 Registration
Attribute Description
Created The last date and time when any of the QA probes user interface attributes were created.
Status Last Modified The last date and time when any of the QA Probe user interface attributes were modified.
 Object Identifiers
Attribute Description
ID The Unique Object Identifier that is unique for probes.
UUID The Universally Unique Object Identifier that is unique across all databases.

HTTP(S)

The HTTP(S) tab displays the retrieved information about the protocol and proxy.

Protocol Details
Attribute Description
URL

The URL specified while configuring the probe.
User Name The user name required to access the URL.

 

Proxy Details
Attribute Description
Proxy

The host name of the proxy server.
User Name The user name for the proxy server.
Port The port number on which the proxy server is configured.

Identify Probes with Critical Status

The Critical Probes view is used to segregate and display only the QA probes whose status is critical. The critical QA probes view displays the operational state, and administrative state as well. These details and the details in the Conclusions tab of the QA probe enable you to drill-down to the root cause of the problem.

To launch the Critical Probes view:

  1. Log on to NNMi console using your user name and password.
  2. Click Quality Assurance in the Workspaces panel. The Quality Assurance tab expands.
  3. Click Critical Probes. The QA probes with Critical status that are discovered in your network appear in the content pane along with some key attributes for each QA probe. By default, this information is refreshed every 300 seconds, or 5 minutes.

The NNM iSPI Performance for QA supports Multi-Tenancy architecture configured in NNMi. The security group defined for a node in NNMi is also applicable for the critical probes of the node in NNM iSPI Performance for QA. This implies that all the critical QA probes cannot be viewed by all users. For example, if a user has access to a set of nodes, then that user can view only the critical QA probes configured on those nodes.

You can filter the critical QA probes based on the QA Groups and list only the critical QA probes that belong to a particular QA group. As you type, the auto-complete feature lists the matching QA Groups. You can select a QA Group name from the list.

Key Attributes of the Critical Probes View

The Critical Probes view displays the following key attributes:

Attribute Name Description
Operational State

Operational State condition returned by the critical QA probe.

The QA probe status is derived from the SNMP polling results for Operational State, as well as from any conclusion.
Administrative State

Administrative State condition returned by the critical QA probe.

The QA probe status is derived from the SNMP polling results for Administrative State, as well as from any conclusion.
Name The name of the discovered QA probe configured in the network device.
Owner The name of the discovered QA probe's owner.
Service

The type of the discovered QA probe.
Device Model The device model name (as discovered by NNMi) of the probe's source node.
Source The source device from which the data packet is sent.
Destination The network device to which the data packet is sent.
Source Site

The network site from which the data packet is sent.
Destination Site The network site to which the data packet is sent.
Manager Specifies whether the NNMi management server is Local or not. The name of the Regional Manager is displayed if the NNMi management server is not local.
Source Tenant Specifies the NNMi tenant selected for the source network device.

If you launch the Status Poll command from NNMi, it triggers a corresponding status poll for NNM iSPI Performance for QA as well.

Analysis Pane

Select the QA probe by clicking the QA probe in the Critical QA Probes View to view the Analysis pane. The Analysis pane of the selected Critical QA Probe appears below.

In the Analysis pane, you can view the summary, Threshold State, and Baseline State panels.

The Threshold State panel displays whether the threshold is configured for the selected probe or not. If a threshold is configured, you can view the summary of the threshold configuration details, and you can also view whether the threshold is configured based on site or a probe. The Threshold State panel enables you to check the configured values and the threshold violations, if any.

The Baseline State panel displays whether Baseline Monitoring is configured for the selected probe or not. If baseline monitoring is configured, you can view the metric, baseline state, upper norm deviation, and lower norm deviation.

Identify Probes with Threshold Exceptions

The Probes Threshold Exceptions view displays a set of probes that have violated the threshold for any one or more of the metrics of NNM iSPI Performance for QA. You can view the threshold states of all the metrics to quickly identify the metrics that have breached the threshold level.

The QA Probes view gives a quick overview of the threshold state violations for the metrics such as Jitter, RTT and so on. However, the Probes Threshold Exceptions view is very exhaustive, and displays intricate details of threshold state violations. This view is very useful for segregating the QA probes that have violated the threshold state and for arriving at a conclusion.

To launch the Probes Threshold Exceptions view:

  1. Log on to NNMi console using your user name and password.
  2. Click Quality Assurance in the Workspaces panel. The Quality Assurance tab expands.
  3. Click Probes Threshold Exceptions. The QA probes that have violated the threshold for Jitter, RTT, Packet Loss and Mean Opinion Score metrics appear in the content pane along with some key attributes for each QA probe.

By default, this information is refreshed every 300 seconds, or 5 minutes.

The NNM iSPI Performance for QA supports Multi-Tenancy architecture configured in NNMi. The security group defined for a node in NNMi is also applicable for the probes of the node in NNM iSPI Performance for QA. This implies that all threshold violated QA probes cannot be viewed by all users. For example, if a user has access to a set of nodes, the user can view the threshold violated QA probes configured on those nodes only.

You can filter the QA probes that violated the threshold, based on the various QA groups. As you type, the auto-complete feature lists the matching QA Groups. You can select a QA Group name from the list.

Key Attributes of the Probes Threshold Exceptions View

Attribute Name Description
Status

The status of the QA probes. It can be one of the following:

  • Warning
  • Major
  • Critical

NNM iSPI Performance for QA calculates the status based on the polling status of the nodes and the threshold states.

Name The name of the discovered QA probe configured in the network device.
Service

The type of the discovered QA probe.
Device Model The device model name (as discovered by NNMi) of the probe's source node.
Manager Specifies whether the NNMi management server is local or not. The name of the Regional Manager is displayed if the NNMi management server is not local.
RTT

The round-trip time used by the selected QA probe.

Displays one of the following threshold states for the metric:

High

Nominal

Low

Not Polled

Unavailable

Threshold Not Set

None
Jitter

The delay variance for a data packet to reach the destination device or site.

Displays one of the following threshold states for the metric:

High

Nominal

Low

Not Polled

Unavailable

Threshold Not Set

None
+ve Jitter SD

Indicates the threshold state of the positive jitter from the source to the destination.

Displays one of the following threshold states for the metric:

High

Nominal

Low

Not Polled

Unavailable

Threshold Not Set

None
+ve Jitter DS

Indicates the threshold state of the positive jitter from the destination to the source.

Displays one of the following threshold states for the metric:

High

Nominal

Low

Not Polled

Unavailable

Threshold Not Set

None
-ve Jitter SD

Indicates the threshold state of the negative jitter from the source to the destination.

Displays one of the following threshold states for the metric:

High

Nominal

Low

Not Polled

Unavailable

Threshold Not Set

None
-ve Jitter DS

Indicates the threshold state of the negative jitter from the destination to the source.

Displays one of the following threshold states for the metric:

High

Nominal

Low

Not Polled

Unavailable

Threshold Not Set

None
PL (Packet Loss)

The percentage of packets that failed to arrive at the destination.

Displays one of the following threshold states for the metric:

High

Nominal

Low

Not Polled

Unavailable

Threshold Not Set

None
Packet Loss SD

Indicates the threshold state of the percentage of packet loss from the source to the destination.

Displays one of the following threshold states for the metric:

High

Nominal

Low

Not Polled

Unavailable

Threshold Not Set

None
Packet Loss DS

Indicates the threshold state of the percentage of packet loss from the destination to source.

Displays one of the following threshold states for the metric:

High

Nominal

Low

Not Polled

Unavailable

Threshold Not Set

 
MOS

Indicates the threshold state of Mean Opinion Score (MOS) of the jitter.
Source Tenant Specifies the NNMi tenant selected for the source network device.

The following table describes the threshold state values:

Threshold States
State Description
High

For Count-Based Threshold Configuration:

Indicates that the measured value of the metric is above the configured High Value and recurs for the consecutive number of times specified in the Trigger Count.

For Time-Based Threshold Configuration:

Indicates that the measured value of the metric is above the configured High Value and this high value persists for the specified High Duration within the High Duration Window.
Nominal

Indicates that the measured value of the metric is within the normal healthy range.
Low

For Count-Based Threshold Configuration:

Indicates that the measured value of the metric is below the configured Low Value for the consecutive number of times specified in the Trigger Count.

For Time-Based Threshold Configuration:

Indicates that the measured value of the metric is below the configured Low Value and this low value persists for the specified Low Duration within the Low Duration Window.

Typically, this threshold state is applicable for metrics such as Mean Opinion Score (MOS).
Not Polled

Indicates that the metric is intentionally not polled.

Some of the possible reasons are:

  • The parent Node or Interface is set to Not Managed or Out of Service.

  • The metric is not supported for the particular entity.

    For example, for an ICMP probe, Jitter and Packet Loss metrics are not supported and so the threshold states for these metrics are displayed as "Not Polled".
Unavailable Unable to compute the metric, or the computed value is outside the valid range.
Threshold Not Set Indicates that the threshold is not set for the metric.
None

For Count-Based Threshold Configuration:

Indicates that the measured value of the metric is zero, and recurs for the consecutive number of times specified in the Trigger Count.

For Time-Based Threshold Configuration:

Indicates that the measured value of the metric is zero and this zero value persists for the specified duration within the High or Low Duration Window (depending on the metric).

If you launch the Status Poll command from NNMi, it triggers a corresponding status poll for NNM iSPI Performance for QA as well.

Analysis Pane

Select the QA probe by clicking the QA probe in the Probes Threshold Exceptions View to view the Analysis pane. The Analysis pane of the selected QA Probe appears.

In the Analysis pane, you can view the summary, Threshold State, Baseline State, and Latest Polled Values panels.

The Threshold State panel displays the summary of the threshold violations. It also displays whether the threshold configuration is based on probe or site.

The Baseline State panel displays whether Baseline Monitoring is configured for the selected probe or not. If baseline monitoring is configured, you can view the metric, baseline state, upper norm deviation, and lower norm deviation.

The Latest Polled Values panel displays the last five polled values for the relevant metrics, which may be RTT (ms or µs), two-way jitter (ms or µs), two-way packet loss, and MOS metric. You can also view the last polled time. If the last polled time is not available, it displays the message—Polling Not Complete.

Identify Probes with Baseline Exceptions

The Probes Baseline Exceptions view displays the QA probes with the baseline state as Abnormal Range, Unavailable, No Policy, or Not Polled for any one or more of the following metrics:

  • RTT
  • Two Way Jitter
  • Two Way Packet Loss
  • MOS

For information about how baseline state is set, see Baseline Monitoring.

This view is very useful to segregate the QA probes with Baseline exceptions and to arrive at a conclusion.

To launch the Probes Baseline Exceptions view:

  1. Log on to NNMi console using your user name and password.
  2. Click Quality Assurance in the Workspaces panel. The Quality Assurance tab expands.
  3. Click Probes Baseline Exceptions. The QA probes with the baseline state as Abnormal Range, Unavailable, or Not Polled for any one or more of the metrics appear in the content pane along with some key attributes for each QA probe.

By default, this information is refreshed every 300 seconds, or 5 minutes.

The NNM iSPI Performance for QA supports Multi-Tenancy architecture configured in NNMi. This implies that all baseline exception QA probes cannot be viewed by all users. For example, if a user has access to a set of source nodes, then that user can view only the QA probes configured on those source nodes.

You can filter the QA probes with the baseline state as Abnormal Range, Unavailable, No Policy, or Not Polled, based on the various QA groups. As you type, the auto-complete feature lists the matching QA Groups. You can select a QA Group name from the list.

Key Attributes of the Probes Baseline Exceptions View

Attribute Name Description
Status

Displays the status of the QA probes. It can be one of the following:

  • Normal
  • Warning
  • Major
  • Critical
  • Unknown
  • Disabled
  • Not Polled
  • No Status

NNM iSPI Performance for QA calculates the status based on the polling status of the nodes and the threshold states.
Name The name of the discovered QA probe configured in the network device.
Service

The type of the discovered QA probe.
Device Model The device model name (as discovered by NNMi) of the probe's source node.
Manager Specifies whether the NNMi management server is local or not. The name of the Regional Manager is displayed if the NNMi management server is not local.
RTT

The round-trip time used by the selected QA probe.

Displays one of the following baseline states for the metric:

  • Normal Range - The metric is within the normal range of deviation.
  • Abnormal Range - The metric is above the configured normal range of the deviation.
  • Unavailable - The computed value for the metric is not found in NNM iSPI Performance for Metrics Software.
  • Unset - No baseline is computed.
  • Not polled - The metric is not polled for baseline deviations.
  • No Policy - No polling policy exists for this metric.
Two Way Jitter

Indicates two way jitter. This value is the average of the following values:

  • Positive jitter from the source to the destination
  • Negative jitter from the source to the destination
  • Positive jitter from the destination to the source
  • Negative jitter from the destination to the source

Displays one of the following baseline states for the metric:

  • Normal Range - The metric is within the normal range of deviation.
  • Abnormal Range - The metric is either above or below the configured normal range of the deviation.
  • Unavailable - The computed value for the metric is not found in NNM iSPI Performance for Metrics Software.
  • Unset - No baseline is computed.
  • Not polled - The metric is not polled for baseline deviations.
  • No Policy - No polling policy exists for this metric.
Two Way Packet Loss

The percentage of packets that failed to arrive from the source to destination and destination to source.

Displays one of the following baseline states for the metric:

  • Normal Range - The metric is within the normal range of deviation.
  • Abnormal Range - The metric is either above or below the configured normal range of the deviation.
  • Unavailable - The computed value for the metric is not found in NNM iSPI Performance for Metrics Software.
  • Unset - No baseline is computed.
  • Not polled - The metric is not polled for baseline deviations.
  • No Policy - No polling policy exists for this metric.
MOS

Indicates the baseline state of Mean Opinion Score (MOS) of the jitter.

Displays one of the following baseline states for the metric:

  • Normal Range - The metric is within the normal range of deviation.
  • Abnormal Range - The metric is either above or below the configured normal range of the deviation.
  • Unavailable - The computed value for the metric is not found in NNM iSPI Performance for Metrics Software.
  • Unset - No baseline is computed.
  • Not polled - The metric is not polled for baseline deviations.
  • No Policy - No polling policy exists for this metric.
Source Tenant Specifies the NNMi tenant selected for the source network device.

The default polling interval for the NNM iSPI Performance for Metrics Software data to detect the exception is 2 minutes.

Analysis Pane

Select the QA probe by clicking the QA probe in the Probes Baseline Exceptions view. The Analysis pane of the selected QA Probe appears. The Baseline State panel displays the metric, baseline state, upper norm deviation, and lower norm deviation.

Send Help Center feedback