This alarm should not normally occur when no other
congestion alarms are asserted. This may occur for a variety of reasons:
- 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.
- 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
.
- 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
.
- 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.
- 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
. If all MPs are in a congestion state then
the offered load to the server site is exceeding its capacity.