Hey All,
So as is commonly talked about, I have seen a number of end user sites
with simple redundancy service using IOS routers.
Multiple lines, coulds be the same provider, could be different
providers, no dynamic routing, different source addresses, uRPF/SAV at
the provider(s) is to be
Whenever the NAT outside IP address changes, the session has to be killed and
restarted as the NAT device cannot signal to the remote end that the outside
source IP address has changed.
EEM clear ip nat trans * is probably the cleanest method. You might want to
get more specific and use clear
Anyone else have any other thoughts on this? Could it be a bug or a faulty
backplane on the 6500 chassis?
James G
-Original Message-
From: cisco-nsp-boun...@puck.nether.net
[mailto:cisco-nsp-boun...@puck.nether.net] On Behalf Of James Greig
Sent: 22 January 2010 21:18
To: 'Alan Buxey'
Thanks for the response.
The nat is inside nat of course.
After the routing and egress changes, the router should be well aware
that continued traffic no longer matches the
ip nat inside source route-map ISPA Di1 overload
and now matches the
ip nat inside source route-map ISPB Di2
After the routing and egress changes, the router should be well aware
that continued traffic no longer matches the
ip nat inside source route-map ISPA Di1 overload
and now matches the
ip nat inside source route-map ISPB Di2 overload
for a simplistic example.
So the old
James Greig wrote:
Anyone else have any other thoughts on this? Could it be a bug or a faulty
backplane on the 6500 chassis?
It looks similar to what I got when I toasted a chassis in November. I
didn't capture the console output, but basically the primary Sup was OK
but the rest were all
Ivan Pepelnjak wrote:
Obviously the router does NOT check the ip nat rules if it gets a match in
the NAT translation table. This behavior makes sense; if you'd change the NAT parameters
of a live session, you'd lose the session anyway.
The problem is that the session stays active. I want
