Reading/writing startup configuration

[excusememeister]

I am trying to programmatically automate the reading/writing of the startup and running configurations of a Cisco PIX 501 using software version 6.3.

I have been able to successfully read/write the running configuration (using write net and configure net) but have not determined the best way to read/write the startup configuration.

At present, I'm thinking that the best techniques for working with the startup configuration are:

* Read it by running 'show startup-config' and capturing the output. I don't like this solution a lot because it feels like I could lose data doing this (although in practice it might be okay.)

* Write it by making changes to the running configuration and then making the changes permanent. But this isn't ideal in that if I want to preserve the running configuration, I need to make a backup of it first and then restore it after setting the startup configuration.

I've found that doing this is easier on other Cisco devices (just copy tftp://[ipaddr]/startup-config startup-config and vice versa), but the copy command works differently on at least this version of the PIX.

Any suggestions for how I can read/write the startup configuration would be appreciated.

 

[brianinms]

Are you really making that many changes to the firewall on a daily basis, or is this in a lab environment?

 

[excusememeister]

This is a lab environment (i.e. I'm creating distributable software.)

 

[brianinms]

As in you are trying to create software for this task?

 

[excusememeister]

Correct.

I am creating software that (among other things) will allow a user to download and upload the startup and running configurations for a Cisco PIX 501.

 

[brianinms]

I wouldn't bother as the Pix's are approaching end of sale. However, to answer your question I don't know of any other way to gather the startup configuration of the device.

http://www.cisco.com/en/US/prod/collateral/vpndevc/ps5708/ps5709/ps2030/pix_eos.html

 

[excusememeister]

Thanks for your responses.

Unfortunately, I need to support Pix simply because some of our customers are using (and will continue to use) older equipment.