From: Voss, David (dvoss@heidrick.com)
Date: Fri Mar 14 2003 - 11:56:20 GMT-3
Thanks for the info. It probably was 60 seconds.
-----Original Message-----
From: Brian Dennis [mailto:brian@labforge.com]
Sent: Thursday, March 13, 2003 11:56 PM
To: Voss, David; ccielab@groupstudy.com
Subject: RE: NAT Expire
Check to see if it's not happening about 60 seconds after the ping is
finished and not 30 seconds. The "expiring" message is NAT cleaning up
the translation table for inactive translations. The reason I asked
about the time is because ICMP defaults to 60 seconds. To change the
default ICMP timeout for NAT use the "ip nat translation icmp-timeout
<seconds>" global configuration command.
Brian Dennis, CCIE #2210 (R&S/ISP Dial/Security) CCSI# 98640
brian@labforge.com
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
Voss, David
Sent: Thursday, March 13, 2003 8:05 PM
To: ccielab@groupstudy.com
Subject: NAT Expire
30 seconds after I send a repeated ping which works correctly, I get
"NAT
expiring" messages. Anyone seen this before? Nothing on CCO that I
see.
2d00h: NAT*: s=6.6.6.6, d=6.6.6.2->2.2.2.5 [208]
2d00h: NAT: s=2.2.2.5->6.6.6.2, d=6.6.6.6 [209]
2d00h: NAT*: s=6.6.6.6, d=6.6.6.2->2.2.2.5 [209]
Rack08R2#
Rack08R2#
2d00h: NAT: expiring 6.6.6.2 (2.2.2.5) icmp 1680 (1680)
2d00h: NAT: expiring 6.6.6.2 (2.2.2.5) icmp 1681 (1681)
2d00h: NAT: expiring 6.6.6.2 (2.2.2.5) icmp 1682 (1682)
This archive was generated by hypermail 2.1.4 : Sat Apr 05 2003 - 08:51:39 GMT-3