TmSingleTransQueuePeak

Measurement Group: Transport Performance

Measurement Type: Max

Measurement Dimension: Arrayed (per Transport)

Description: The peak single Transport Writer Queue utilization (0-100%) measured during the collection interval (averaged over 2 sec).

Collection Interval: 5 min

Peg Condition Transport's Queue is registered as a Stack Resource, StackResourceManager thread monitors and updates the maximum Transport Queue utilization sample taken during the collection interval for affected Transport.

Measurement Scope: NE, Server

Recovery:

Transport single queue utilization depicts the SCTP or UDP Transport Writer Queues utilization. This is a measure of how fast the Transport queue is being processed. It indicates the maximum depth of queue over the monitored interval. It is primarily intended to assist in evaluating the need for additional MP processing capacity at a Network Element.
If both the peak and average measurement for multiple MPs within a Network Element are consistently near the recommended maximum engineered capacity of an MP over several collection intervals, then the number of MPs in the Network Element may need to be increased.
If the peak and average for an individual MP is significantly different than other MPs in the same Network Element then an MP-specific hardware, software, or configuration problem may exist.
The percent utilization of the MP's Transport Writer Queue is approaching its maximum capacity. If this problem persists and the queue reaches 100% utilization, all new egress messages from the Transport will be discarded.
1. An IP network or Adjacent node problem may exist preventing SCTP from transmitting messages into the network at the same pace that messages are being received form the network.
2. The SCTP Association Writer process may be experiencing a problem preventing it from processing events from its event queue. The alarm log should be examined from Main Menu > Alarms & Events.
3. If one or more MPs in a server site have failed, the traffic will be distributed amongst the remaining Mps in the server site. MP server status can be monitored from Main Menu > Status & Control > Server Status.
4. The mis-configuration of Adjacent Node IP routing may result in too much traffic being distributed to the MP. Each MP in the server site should be receiving approximately the same ingress transaction per second.
5. There may be an insufficient number of MPs configured to handle the network traffic load. The ingress traffic rate of each MP can be monitored from Main Menu > Status & Control > KPI Display. If all MPs are in a congestion state then the offered load to the server site is exceeding its capacity.
Contact My Oracle Support (MOS) for assistance if needed.