Cisco Bug: CSCus09809 - [SaMOG-R18] Mag-service "Tot Dis/Fail" & PBA counters pegged incorrectly
Dec 24, 2016
- Cisco ASR 5000 Series
Known Affected Releases
Symptom: Issue 1: ---------------- 1) Trigger a S2A-PMIP call with PMIP Access Type. 2) Trigger PBA from PGW with time stamp mismatch. SaMOG starts clean up of the session and triggers PBU with Life time Zero towards PGW. 3) PGW does not respond to PBU with Life time zero. SaMOG cleans up session on dis-connect timer expiry. 4) Check the mag counters and observe the below anomaly: Total Disconnects/Failures: 2 <<< should be 1 Lifetime expiry: 0 Access Initiated Term: 0 Admin Drops: 0 Other Reasons: 2 <<< should be 1 LMA Revocations: Issue 2: -------------- Trigger a S2APMIP call with, PGW responds with the "IPv4 Default Router Address" = "IPv4 Home Address" in PBA. The call is aborted with reason - samog-mandatory-ie-incorrect. Check the mag-service stats and observe that this error condition is not pegged in the below stats. Home Address Conflict should have been pegged Conditions: Issue 1: ------------ Scenario. 1. On dis-connect timer expiry when session deletion is in progress. In Current testing retransmission timeout is very high so we encountered the dis-connect timer expiry this is will not happen normally. Retransmission expiry will occur before dis-connect timer expiry and we will not observe the issue. Issue 2: ----------- Expected Behavior. This check is performed at Application so, MAG Driver Counters are not pegged.
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