Cisco Bug: CSCur04175 - 17.0 - MME/SGSN snmp trap "Congestion" with max sessions wrongly hit
Feb 08, 2017
- Cisco ASR 5000 Series
Known Affected Releases
Symptom: 17.0 - MME/SGSN snmp trap "Congestion" with max sessions wrongly hit On a mme/sgsn combo chassis under load conditions of 2 million subscribers, when MME congestion control is enabled, below trap is generated continuously with statistics counter incremented rapidly at high rate. Fri Sep 26 04:28:07 2014 Internal trap notification 81 (Congestion) service type sgsn congestion policy none, resource type maxsessions Below stats counter increases and toggles with applied and cleared continuously. [local]F43# show congestion-control statistics imsimgr Current congestion status: Applied Current congestion Type : Critical Congestion applied: 703329 times Critical Congestion Control Resource Limits system cpu use exceeded: No service cpu use exceeded: No system memory use exceeded: No port rx use exceeded: No port tx use exceeded: No port specific rx use exceeded: No port specific tx use exceeded: No max sess use exceeded: Yes license use exceeded: No msg queue size use exceeded: No msg queue wait time exceeded: No license threshold exceeded: No SGSN Congestion Control: MM Congestion Level: None Congestion Resource: None SM Congestion Level: None O&M Congestion Level: None [local]F43# show snmp trap statistics | grep Conges Congestion 721507 0 720527 2014:09:26:04:43:30 Conditions: MME Congestion policy enabled and under load conditions.
Bug details contain sensitive information and therefore require a Cisco.com account to be viewed.
Bug Details Include
- Full Description (including symptoms, conditions and workarounds)
- Known Fixed Releases
- Related Community Discussions
- Number of Related Support Cases