Routing problem - ASA

[cisco_lite]

hi,

I am not able to ping to management interface of ASA from one of the vlans on the inside. Reason is that the route back to my PC takes a different path due to route definition in the routing table of ASA. This route enables internet access. However, when I remove the route and add another route to my PC via different hop (management vlans gateway), ping goes through. But then internet access fails due to lack of related route.

In absence of Policy based routing how can I achieve both the connectivity.

Thanks.

[cisco_lite]

Thanks for returning on this.

There is only one static NAT entry

static (inside,outside) 5.0.0.99 2.0.0.99 netmask 255.255.255.255

The IP address I am coming from on the inside is 2.0.0.99

The relevant sh xlate is

Global 2.0.0.99 Local 2.0.0.99

(Pls excuse me for not posting complete 'sh xlate' output)

So it is not getting NAT'ed to 5.0.0.99

[Jon Marshall · Accepted solution]

Do you have any other NAT statements ie. not just static entries on the inside. Key thing is do you have any nat exemption rules on the inside interface.

It could be that a nat rule is being used before your static entry.

The other thing is have you tried clearing that specific xlate entry

clear xlate 2.0.0.99 (syntax may need changing for FWSM)

Jon