pix 501 issue

sautertech · ‎08-07-2005

I had Cisco configure this device. I needed to go in and open up a few more ports and map them to a new internal IP. This is the first time I have been in the unit since Cisco configured it. When I log in I can only access HOME and MONITORING modes. I cannot get into CONFIGURATION menu. The message below is what I get.

PDM has encountered a firewall configuration command statement that PDM does not support. Configuration parsing has stopped. PDM access is now limited to the home and monitoring views during the current session. To regain access to rest of PDM use the command line interface window to fix the unsupported command statement and then refresh PDM with the modified firewall configuration.

PDM does not support the "alias" command in your configuration.

Cisco recommends that you consider migrating from the "alias" command to the newer "Outside Nat feature" ( also known as Bi-Directional NAT ), which provides functionally equivalent to the alias command.

Any help would be appreciated.

Dave

nkhawaja · ‎08-09-2005

Cisco must have configured it using CLI. if there is "alias" command in the config, then you will not be able to configure the firewall via PDM. You need to use CLI to configure it. There may be a reason for alias command to be there in the config in the first place.

Either you login via CLI and change the alias command to static command, or remove this command if you are not using it.

or you can temprarily remove the alias command, loging via PDM, make your changes, and put the alis command back in

sautertech · ‎08-09-2005

I appreciate the response, however I haven't figured out how to modify from the CLI. The alias command is as follows:

alias (inside) 192.168.1.3 xxx.xxx.xxx.xxx 255.255.255.255

( I xxx'd out the actual public IP )

This is my first purchase of a Cisco product. The PIX is awesome - but I am somewhat disappointed that I am having these issues. Since Cisco configured it initially I would expect to be able to get into the normal configuration screens in PDM. But instead I have to deal with this error message. They told me that it would cost $400 for them to correct it. Heck, that's about what I paid for the unit! That kind of money to fix something they did is insane. Oh well...if the alias command is not supported, why would they have put it in there?