cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1881
Views
0
Helpful
10
Replies

One to One NAT Issue

ahsan1
Level 1
Level 1

i All,

can anyone face similar issue that after reboot the firepower 2110, static NAT (one to one) from one interface is not working but from another interface it is working.

10 Replies 10

Hello,

 

I checked for bugs, nothing there. Are these interfaces in the same or in different interface groups ?

ahsan1
Level 1
Level 1

Thanks for the response.

Physical interfaces are from 2 different ISP's. Can you please more elaborate? 

Hello,

 

what I mean is that interfaces can belong to different interface groups (same security group obviously).

 

After the reboot, when you send traffic over the one-to-one NAT entry, does anything show up in:

 

show xlate

show asp table classify domain nat

show asp table classify domain nat-reverse

 

?

No entry showing from that public nat public IP, which has been checked from your shared commands.

Hello


@ahsan1 wrote:

, static NAT (one to one) from one interface is not working but from another interface it is working.


Can you elaborate,
Can you ping from the hidden address (natted) to the outside network?

 


Please rate and mark as an accepted solution if you have found any of the information provided useful.
This then could assist others on these forums to find a valuable answer and broadens the community’s global network.

Kind Regards
Paul

No i am unable to ping from outside to the natted public ip.

So internally from that natted host you have no connection externally, Have you checked to see if  the ASA has lost its nat configuration after the reload?


Please rate and mark as an accepted solution if you have found any of the information provided useful.
This then could assist others on these forums to find a valuable answer and broadens the community’s global network.

Kind Regards
Paul

No it has not removed because configuration was saved.

Hello,

 

post the full running config of the 2110...

Hello

 


@ahsan1 wrote:

No it has not removed because configuration was saved.


Well if it was working before a reload and it isn’t now, something has changed and if your positive no cfg has been lost, Have you DIIF examined the pre-/post  running config and make sure all objects groups, access-lists and NAT statements have parity?

What about physical issue are all ports in a up/up state that was before reload?


Please rate and mark as an accepted solution if you have found any of the information provided useful.
This then could assist others on these forums to find a valuable answer and broadens the community’s global network.

Kind Regards
Paul
Review Cisco Networking for a $25 gift card