Introduction
The IPSI Peg Count report measures the amount of errors encountered between the IPSI and the PCD (Processor). This network is often referred to as the Control Network. The IPSI is effectively a NIC for the Port Network.
| Info |
|---|
...
The data flowing over this network is used for control purposes. Even though the bandwidth consumed is relatively small, it is very important that QoS policy is applied |
...
| Note |
|---|
If the Control Network does not meet Avaya’s recommended performance standards, parts or all of the solution can restart, causing major business interruption. |
See below for more information of what measures this report tracks.
Uses
Use this report to:
- Identify, over an extended time period, the performance of the Control Network.
- Use as an indicator of Indicate potential problems when there are peg counts present.
- Detect and resolve issues before they become business-impacting.
- Use for Root Cause Analysis(RCA) to prevent a recurrence of the incident.
Example 1
This is a good example. There are no issues with the Control Network.
Example 2
In this example there are frequent issues with the Control Network and Port Network 3 is in danger of restarting. The UC team need to work in conjunction with the data team to resolve this issue prior to there being an outage. If the IPSI misses 3 sequential Heart Beat messages it will restart, causing major disruption to the business.
Additional Information
Description of the measures that this report tracks.
...
Field | Description |
|---|---|
RTT > 300 | Network Delay Count of how many times within an hour the sample delay was greater than 300 milliseconds. |
HB Missed | Network Indicator Heart Beats Missed measures how many once per second “heartbeats” between the IPSI and PCD were missed. |
Network Outage > 1 | Network Indicator Network Outage measures the number of times there was at least a one second outage. |
Network Outage > 3 | Network Indicator Network Outage > 3 seconds (subset of number above) measures the number of times there was an outage of greater than 3 seconds’ duration. |
Sanity Timer | Network Indicator Sanity Timeout (subset of number above) measures the number of times there was an outage greater than the value administered for the “IPSI Socket Sanity Timeout” (4 – 15 sec). If a value is not administered, this number will be the same as the preceding column. |
Example 1
This is a good example. There are no issues with the Control Network.
Example 2
In this example there are frequent issues with the Control Network and Port Network 3 is in danger of restarting. The UC team need to work in conjunction with the data team to resolve this issue prior to there being an outage. If the IPSI misses 3 sequential Heart Beat messages it will restart, causing major disruption to the business.