Guest

Preview Tool

Cisco Bug: CSCuj86237 - Inaccurate SGW session stats on standby ASR

Last Modified

Jan 30, 2017

Products (1)

  • Cisco ASR 5000 Series

Known Affected Releases

16.0(1) 16.1(0)

Description (partial)

Symptom:
AT&T has also raised concern on the following bulkstats that are inaccurate (no-zero value) on standby 
and triggered PRIME threshold alarm:

1) SGW active session stats
2) StarOS SAEGW Bearers Others 5 Minute/Setup
3) StarOS KPI CEPS Call Events Per Second on Whole System 5 Minute/CEPS Call Events Per Second on Whole System.

List of standby KPI to check:

SUMSGW_SCUR
SUMSGW_STOTCUR_BEARERS
SUMSGW_STOTCUR_PDN
SUMSGW_STOTCUR_PDN_IPV4
SUMSGW_STOTCUR_UEACTIVE
SUMSGW_STOTCUR_UEIDLE

Conditions:
ARTNVANZ22G standby node is sending inaccurate bulkstats data for SGW session stats to
 
Prime/Optima.  Active ASR ARTNVANZ21G SGW stats show correctly in Prime and Optima but ARTNVANZ22G
 
data doesn't match or closely match the acitve ASR.
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)
  • Status
  • Severity
  • Known Fixed Releases
  • Related Community Discussions
  • Number of Related Support Cases
Bug information is viewable for customers and partners who have a service contract. Registered users can view up to 200 bugs per month without a service contract.