 context : admin : (001/003 Contexts saved) Cryptochecksum: f69086ec aa68219f d3ef18ff 391fe121 1780 bytes copied in 0.260 secs Saving context : GAD-Tech : (002/003 Contexts saved) Cryptochecksum: 156bed5f 17788005 9fb9d182 231910ab 1503 bytes copied in 0.160 secs Saving context : Test : (003/003 Contexts saved) Cryptochecksum: f39b8a45 e1b47f79 22f4b4e6 95b0cc8d 1499 bytes copied in 0.220 secs Failover Most ASA appliances can be configured in high-availability pairs, provided that both ASAs in the pair have identical hardware specs. There are two ways to configure ASAs for failover: active/standby and active/active. In active/standby configuration, should the primary ASA fail, the secondary will take over. In an active/active standby config- uration, both ASAs can forward traffic, but, as you'll see, that's not necessarily as ex- citing as it sounds. To use this feature, the ASA must be licensed for it, though currently all models 5520 and higher come with the feature. To determine whether an ASA is capable of sup- porting failover, use the show version command: ASA-5540# sho version I begin Licensed Licensed features for this platform: Maximum Physical Interfaces : Unlimited Chapter 28: ASA Firewall Configuration Maximum VLANs : 200 Inside Hosts : Unlimited Failover : Active/Active VPN-DES : Enabled VPN-3DES-AES : Enabled Security Contexts GTP/GPRS : Disabled VPN Peers : 5000 WebVPN Peers AnyConnect for Mobile : Disabled AnyConnect for Linksys phone : Disabled Advanced Endpoint Assessment : Disabled UC Proxy Sessions To be installed as a failover pair, each ASA must have the same software release instal- led, though minor differences are tolerated and will be indicated with a warning such as this: WARNING WARNING WARNING Mate version 8.0(3) is not identical with ours 8.0(4) WARNING WARNING WARNING Beginning configuration replication: Sending to mate. Each ASA in a failover pair must also have the exact same configuration. As a result, the hostname will be the same on both firewalls in the pair. If we attempt to