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

FWSM - No Nat Control

When using no nat control on a FWSM, I would assume that the xlate table (sh xlate) should be empty.

Is this correct as I am seeing some one to one entries in the xlate. I am not seeing every single host, only approx 200 out of 5000 potential hosts.

Can someone confirm this ?

Thanks,

Jon

1 ACCEPTED SOLUTION

Accepted Solutions

Re: FWSM - No Nat Control

By default, the FWSM creates NAT sessions for all connections even if you do not use NAT. To avoid running into the maximum NAT session limit, you can disable NAT sessions for untranslated traffic (called xlate bypass).

To enable xlate bypass, enter the following command:

hostname(config)# xlate-bypass

Syed

4 REPLIES
Bronze

Re: FWSM - No Nat Control

No , using no nat control onlt disables strict nat to be applied on the traffic traversing through the firewall. If a nat policy is there it will still be applied and there will be entries in sh xlate.

New Member

Re: FWSM - No Nat Control

I am not using any nat in the config. All references have been removed. In my opinion I shouldn't be seeing xlates if there is no nat policies configured.

Re: FWSM - No Nat Control

By default, the FWSM creates NAT sessions for all connections even if you do not use NAT. To avoid running into the maximum NAT session limit, you can disable NAT sessions for untranslated traffic (called xlate bypass).

To enable xlate bypass, enter the following command:

hostname(config)# xlate-bypass

Syed

New Member

Re: FWSM - No Nat Control

Thanks Syed,

I found out this command the last time I was on site, but your explanation confirms my actions.

Thanks,

Jon

424
Views
0
Helpful
4
Replies