Guest

Preview Tool

Cisco Bug: CSCus10366 - Traffic meant to be NAT'ed is *not* being NAT'ed

Last Modified

Oct 13, 2016

Products (1)

  • Cisco ASR 1000 Series Aggregation Services Routers

Known Affected Releases

15.2(4)S5.1

Description (partial)

Symptom:
Traffic meant to be NAT'ed is *not* being NAT'ed - seeming inconsistency. Can be identified after getting packet capture on ingress and egress on the Router (e,g, ASR1001)

Conditions:
The scenarios where the Gatekeeper causes issues is the following: 
1) customer has a route-map configuration with a match next hop, 
2) customer has inside mapping plus traffic initiated out2in traffic were the source addresses is a PAT address provided by a previous box. 

The key to these scenarios is that a single source sometimes requires NAT and sometimes does not; this causes issues with the gatekeeper.
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.