Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. If you'd prefer to explore, try our test area to get started. And see here for current known issues.

New Member

clear xlate - PIX vs ASA

I'm finding a discrepancy between PIX (version 6.3(3)) and ASA (version 7.0(5)):

I use a static NAT statement to map a public IP address to an internal IP address:

static (inside,outside) 67.67.67.67 10.0.0.1 netmask 255.255.255.255

In the event of a server failure (i.e. 10.0.0.1), another server changes this NAT statement to:

static (inside,outside) 67.67.67.67 10.0.0.2 netmask 255.255.255.255

and performs a 'clear xlate' to immedidately start routing traffic from 10.0.0.1 to 10.0.0.2. I am finding the PIX (version 6.3(3)) is dropping all other connections immediately after the 'clear xlate' is ran, whereas the ASA (version 7.0(5)) maintains existing connections, but begins mapping all new connections to the new server. I prefer the ASA behavior for my application (since sometimes I perform simulated failover and I want the existing connections to remain in place) and am wondering if there is a setting within the PIX to achieve the same results.

1 REPLY
New Member

Re: clear xlate - PIX vs ASA

Check your configuration ,below command is configured or not, if so remove this cmd

timeout xlate 0:05:00

(eg)this line is doing a clear xlate every 5 minutes

try this command to change MSS:

sysopt connection tcpmss

Force TCP proxy connection to have a maximum segment size no greater than bytes. The default value for bytes is 1380, so lets try something like 1200.

Try this link:

http://www.cisco.com/en/US/products/sw/secursw/ps2120/products_command_reference_chapter09186a00801cd841.html#wp1084248

278
Views
0
Helpful
1
Replies