Guest

Preview Tool

Cisco Bug: CSCuq38354 - EGTPCPathFailure: PGW not sending Echo Request after 180sec interval

Last Modified

Feb 08, 2017

Products (1)

  • Cisco ASR 5000 Series

Known Affected Releases

16.0(1)

Description (partial)

Symptom:
We're seeing EGTPPathFailure traps on the chassis for various SGW peers. There doesn't seem to be any correlation between the SGWs having the traps either.

Based on the wall_pgw_15min.pcap, we observe the following:

- Packet 6: PGW sends Echo Request at  19:47:32 and gets response from SGW
- PGW fails to send Echo Request at 19:47.32 + 180secs (19:50:32).
- PGW fails to send 6 Echo Request retries at 15 second interval (105 secs).
- 19:50:32 + 105 secs = 19:52:17 which is when the trap is generated (see below) and PGW resets the path dropping ~1M subs.

Tue Aug 12 19:52:18 2014 Internal trap notification 1112 (EGTPCPathFail) context XGWin, service EGTP1, interface type pgw-ingress, self address 66.174.120.229,  peer address 199.223.96.98, peer old restart counter 10,  peer new restart counter 10,  peer session count  1030466, failure reason no-response-from-peer

NPUMGR shows exceptions Transmit_error/Missing_results, reflecting that some traffic is being discarded in NPU.

Conditions:
Normal use
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.