New config for Pix525 and Failover unit 1

[yowza]

I need to replace my entire configuration on our pix 525 and failover pix and have 3 questions.

1. I connect my laptop to the console port and use Hyperterminal to configure the pix. I have the config in a Notepad file and just cut and paste to make changes. When I paste, it is EXTREMELY slow. I really think I can type faster than what is being pasted. Is there any way to speed this up? The settings I use for the Hyperterminal session is: bps=9600, data bits=8, parity = 1, stop bits =1, flow control = none. I have played with the flow control, but it does not make any difference.

2. If I do a write erase on the primary pix, will it also erase the failover unit?

3. To replace my entire configuration, I am assuming that the answer to my second question is No and here is what I think I need to do. I would appreciate any help on this.

Remove failover cable from the failover unit.
Using the console port & hyperterminal, do a write erase.
Power down the failover unit and reconnect failover cable.
On the primary unit do:

write erase
reload
config term
Paste new configuration in
write mem
Power up failover unit

Will this work?
Thanks,
yowza

 

[baddos]

Pasting a bunch of text over your serial port will always be slow. If you want it fast, do it over telnet or ssh.

After you do a write erase on the active pix, you need to write standby.

 

[bell1996]

I agree, to overcome the slow console connection, just set the inside interface to accept a telnet connection, this will speed things up significantly.

Secondly, by doing a erase on the primary, it'll definitely affect the failover unit. The primary PIX is where all the changes to the configuration should take place. So, if you erase the config on the primary the failover will no longer function(well at least not properly).

Third, do the steps you've outlined. This will allow you to make changes to the primary PIX. There will be some down time involved (minimal as it seems, but it should be planned for). You'll have to be careful when you configure the INSIDE interface with an IP address (this is the downtime I was mentioning).