It is important that the secondary unit is running a current version of the configuration that exists on the primary PIX Firewall. Issue the following command on the primary, if possible, to copy the current configuration to the standby unit:
The configuration will be copied over to the standby unit. Once this is completed, remove the primary PIX from the setup by shutting down the primary unit. Make sure that the secondary PIX has taken over before physically removing the primary PIX. This can done by issuing the following command on the secondary unit:
secondarypix# configure terminal
secondarypix (config t)# show failover
The output should look like the following:
pixfirewall (config)# show failover
Reconnect timeout 0:00:00
Poll frequency 15 seconds
failover replication http
This host:Secondary - Active
Active time:30 (sec)
Interface FailLink (172.16.31.2):Normal
Interface 4th (172.16.16.1):Normal
Interface int5 (192.168.168.1):Normal
Interface intf2 (192.168.1.1):Normal
Interface outside (184.108.40.206):Normal
Interface inside (10.1.1.4):Normal
At this point, the secondary PIX should show up as active in the above command output. Now it is possible to safely remove the primary PIX physically.
Note: If the secondary unit is not active at this point, troubleshooting will be necessary.
Once the old primary unit has been removed, you will need to physically install the new primary unit. The hardware and software must match the secondary unit. Be sure that the new primary PIX is running the same PIX operating system version and has the same hardware configuration as the secondary. If these requirement are not met, the new primary PIX will not perform properly in a failover environment.
Once the new primary PIX has been attached properly and is running, you will need the existing configuration on the new unit. This can be done through TFTP or entered manually. The entire configuration is not necessary at this time, but the interfaces must be set up properly and failover commands must be in place. Issue the show failover command again on the secondary unit. The above information from the previous show failover command will appear along with the following:
Other host: Secondary - Standby
Active time:0 (sec)
Interface FailLink (172.16.31.2) : Normal
This will verify that the primary PIX is properly attached using failover. Issue the copy standby command on the secondary unit. This will copy the full configuration from the secondary PIX to the new primary PIX.
Issue the failover active command on the primary PIX so that it will resume the active role for the failover connection. Issue the show active command on the new primary to make sure that it is identified as the primary failover device. On the new primary PIX, issue the write memory command to save the configuration to memory.
Not sure if there is a solution out there yet. We recently purchased 2110 for VPN S2S and RA. We don't have ISE as it is out of our budget to house this. We are trying to see how we can control the RA computers that access our VPN. Has anyone found a work...
I am looking for a way to allow a custom user role to only have access to Blacklist Emails. Is this possible without allowing full access to Mail Policies and Content Filters.For example we have a Mail Policy that blacklists emails based on sender. W...
Guys, help, I have two ISE in operation with version 2.3 in a SNS3415 and I have a new SNS-3655 and I need migrate the ISE from 2.3 to 2.4 patch 5 in a this new nodes. Whats it's the procedure for this? I think export the certificate, the show r...
I have a Site-to-site tunnel built between Virginia (VA) and California (CA). He has a Juniper Firewall, and I have a FirePower running ASA. I define interesting traffic as VA-to-CA for all IP (one direction). Because of the Junipe...