Few years ago I wrote article about how to setup CISCO ASA in GNS3. You can use one of below activation key. Feb 11, 2009  plzzz i run pix with image 7.2.2 and i have activation key an eveything is work with cli but i need to run asdm and config the pix with gns3 i have im.

If they would tear your world apart,
Would you intervene?
Music is a weapon;
Sounds like a threat.
Let the bass terrorize;
There’s no turning back!

Hey! Activate! Hey!
Hey! Activate! Hey!

Activate!
Atari Teenage Riot

Lazy Saturday with my pet ASA, trying different file systems on the internal Compact Flash card. Atari Teenage Riot sings in the background; the new album is really quite good. Back after 10 years with a different lineup, they sound the same, but different. Old school synthetic. Still pissed about the same shit.

Bands that break up and disappear from view; they’re never really gone. The philosophical drummer, the narcissistic lead singer, the flaky guitarist; they are still somewhere out there in the world, doing designer drugs in their luxury penthouses, or shopping for Maalox at Safeway in their flip flops. Latent, in potentia. Waiting to be reassembled.

The second time I play the album, I sing along with Activate! and it not-so-subliminally makes me think to look for the missing activation key on my Cisco ASA.

A Cisco ASA with a Base license, compared with an ASA with a Security Plus license: They can boot with identical image files, use identical hardware and identical config. They just have different features enabled. Like that old myth about humans using only 10 percent of their brains, the advanced features for the Cisco ASA are there in the boot image, they just need to be unlocked via license keys. (Well, you need to unlock your wallet too.)

Just do a show version or a show activation-key to see the type of license that is installed.

When you use the ERASE command in ROMMON mode, you completely wipe the Compact Flash card on a Cisco ASA. All the files and directories, even the hidden ones, are gone. Gone, baby, gone. The license files are located in the .private hidden directory, so if you wipe the Compact Flash card, the existing license information is lost. Even after you load a new boot image, the ASA will report that the license key is not valid during boot up (you can also check with a show version.) Some of the original features will be disabled until you install the correct license key.

The activation keys are all tied to the serial number of the ASA, so you can’t just cut and paste a key from another ASA. So, what do you do? You go to see the wizard; ask him to give you a new key. Go to:

Late 2012 models with a Nvidia 675MX or Nvidia 680MX graphics cards are also supported. Please note for your computer to meet the minimum requirements it must match or better all elements of the listed system requirements. • * All 13' MacBook Pros released since 2016 • * All 15” Retina MacBook Pros released since Mid 2012 • * All 15' MacBook Pros released since Mid 2012 with a 1GB Graphics Card • * All 21.5” iMacs released since Late 2013 with a 1.8GHz i3 processor or better • * All 27” iMacs released since Late 2013 (1) • * All 27' iMac Pros • * All Mac Pros released since Late 2013 • 1. For more detailed specifications check the Feral website. Lego marvel superheroes cheat codes.

Log in with a cisco.com ID and you will be presented with the Product License Registration page.

You don’t need a PAK. Click the link for available licenses.

Select Cisco ASA 3DES/AES License.

Enter the serial number of the Cisco ASA. You can get this by looking on the chassis, or doing a show version or a show activation-key. The license key will be emailed to you, and then all you have to do is enter it into the ASA with the activation-key command.

Then do a show version to ensure that the new key has been applied.

Additional Information:

Contents

Introduction

The failover configuration requires two identical security appliances connected to each other through a dedicated failover link and, optionally, a stateful failover link. The health of the active interfaces and units is monitored to determine if specific failover conditions are met. If those conditions are met, failover occurs.

The security appliance supports two failover configurations, Active/Active Failover and Active/Standby Failover. Each failover configuration has its own method to determine and perform failover. With Active/Active Failover, both units can pass network traffic. This lets you configure load balancing on your network. Active/Active Failover is only available on units that run in multiple context mode. With Active/Standby Failover, only one unit passes traffic while the other unit waits in a standby state. Active/Standby Failover is available on units that run in either single or multiple context mode. Both failover configurations support stateful or stateless (regular) failover.

This document focuses on how to configure an Active/Active Failover in Cisco PIX/ASA Security Appliance.

Refer to PIX/ASA 7.x Active/Standby Failover Configuration Example in order to learn more information about the Active/Standby Failover configurations.

Note: VPN failover is not supported on units that run in multiple context mode as VPN is not supported in multiple context. VPN failover is available only for Active/Standby Failover configurations in single context configurations.

This configuration guide provides a sample configuration to include a brief introduction to the PIX/ASA 7.x Active/Active technology. Refer to the Cisco Security Appliance Command Reference, Version 7.2 for a more in-depth sense of the theory based behind this technology.

Prerequisites

Requirements

Hardware Requirement

The two units in a failover configuration must have the same hardware configuration. They must be the same model, have the same number and types of interfaces, and the same amount of RAM.

Note: The two units do not need to have the same size Flash memory. If you use units with different Flash memory sizes in your failover configuration, make sure the unit with the smaller Flash memory has enough space to accommodate the software image files and the configuration files. If it does not, configuration synchronization from the unit with the larger Flash memory to the unit with the smaller Flash memory fails.

Software Requirement

The two units in a failover configuration must be in the operational modes (routed or transparent, single or multiple context). They must have the same major (first number) and minor (second number) software version, but you can use different versions of the software within an upgrade process; for example, you can upgrade one unit from Version 7.0(1) to Version 7.0(2) and have failover remain active. Cisco recommends that you upgrade both units to the same version to ensure long-term compatibility.

Refer to Performing Zero Downtime Upgrades for Failover Pairs for more information about upgrading the software on a failover pair.

License Requirements

On the PIX/ASA Security appliance platform, at least one of the units must have an unrestricted (UR) license. The other unit can have a Failover Only Active-Active (FO_AA) license, or another UR license. Units with a Restricted license cannot be used for failover, and two units with FO_AA licenses cannot be used together as a failover pair.

Note: You might need to upgrade the licenses on a failover pair in order to obtain additional features and benefits. For more information on upgrade, refer to License Key Upgrade on a Failover Pair

Note: The licensed features, such as SSL VPN peers or security contexts, on both security appliances that participate in failover must be identical.

Note: The FO license does not support Active/Active Failover.

Components Used

The information in this document is based on these software and hardware versions:

• PIX Security Appliance with 7.x version and later

The information in this document was created from the devices in a specific lab environment. All of the devices used in this document started with a cleared (default) configuration. If your network is live, make sure that you understand the potential impact of any command.

Related Products

This configuration can also be used with these hardware and software versions:

• ASA with 7.x version and later

Note: Active/Active failover is not available on the ASA 5505 series adaptive security appliance.

Conventions

Refer to the Cisco Technical Tips Conventions for more information document conventions.

Active/Active Failover

This section describes Active/Standby Failover and includes these topics:

Active/Active Failover Overview

Active/Active failover is only available to security appliances in multiple context mode. In an Active/Active failover configuration, both security appliances can pass network traffic.

In Active/Active failover, you divide the security contexts on the security appliance into failover groups. A failover group is simply a logical group of one or more security contexts. You can create a maximum of two failover groups on the security appliance. The admin context is always a member of failover group 1. Any unassigned security contexts are also members of failover group 1 by default.

The failover group forms the base unit for failover in Active/Active failover. Interface failure monitoring, failover, and active/standby status are all attributes of a failover group rather than the unit. When an active failover group fails, it changes to the standby state while the standby failover group becomes active. The interfaces in the failover group that becomes active assume the MAC and IP addresses of the interfaces in the failover group that failed. The interfaces in the failover group that is now in the standby state take over the standby MAC and IP addresses.

Note: A failover group failing on a unit does not mean that the unit has failed. The unit may still have another failover group passing traffic on it.

Primary/Secondary Status and Active/Standby Status

As in Active/Standby failover, one unit in an Active/Active failover pair is designated the primary unit, and the other unit the secondary unit. Unlike Active/Standby failover, this designation does not indicate which unit becomes active when both units start simultaneously. Instead, the primary/secondary designation does two things:

• Determines which unit provides the running configuration to the pair when they boot simultaneously.

• Determines on which unit each failover group appears in the active state when the units boot simultaneously. Each failover group in the configuration is configured with a primary or secondary unit preference. You can configure both failover groups be in the active state on a single unit in the pair, with the other unit containing the failover groups in the standby state. However, a more typical configuration is to assign each failover group a different role preference to make each one active on a different unit, distributing the traffic across the devices.

  Note: The security appliance does not provide load balancing services. Load balancing must be handled by a router passing traffic to the security appliance.

Which unit each failover group becomes active on is determined as shown

• When a unit boots while the peer unit is not available, both failover groups become active on the unit.

• When a unit boots while the peer unit is active (with both failover groups in the active state), the failover groups remain in the active state on the active unit regardless of the primary or secondary preference of the failover group until one of the following:

  • A failover occurs.

  • You manually force the failover group to the other unit with the no failover active command

  • You configured the failover group with the preempt command, which causes the failover group to automatically become active on the preferred unit when the unit becomes available.

• When both units boot at the same time, each failover group becomes active on its preferred unit after the configurations have been synchronized.

Device Initialization and Configuration Synchronization

Configuration synchronization occurs when one or both units in a failover pair boot. The configurations are synchronized as shown:

• When a unit boots while the peer unit is active (with both failover groups active on it), the booting unit contacts the active unit to obtain the running configuration regardless of the primary or secondary designation of the booting unit.

• When both units boot simultaneously, the secondary unit obtains the running configuration from the primary unit.

When the replication starts, the security appliance console on the unit sending the configuration displays the message 'Beginning configuration replication: Sending to mate,' and when it is complete, the security appliance displays the message 'End Configuration Replication to mate.' During replication, commands entered on the unit sending the configuration may not replicate properly to the peer unit, and commands entered on the unit receiving the configuration may be overwritten by the configuration being received. Avoid entering commands on either unit in the failover pair during the configuration replication process. Depending upon the size of the configuration, replication can take from a few seconds to several minutes.

On the unit receiving the configuration, the configuration exists only in running memory. To save the configuration to Flash memory after synchronization enter the write memory all command in the system execution space on the unit that has failover group 1 in the active state. The command is replicated to the peer unit, which proceeds to write its configuration to Flash memory. Using the all keyword with this command causes the system and all context configurations to be saved.

Note: Startup configurations saved on external servers are accessible from either unit over the network and do not need to be saved separately for each unit. Alternatively, you can copy the contexts configuration files from the disk on the primary unit to an external server, and then copy them to disk on the secondary unit, where they become available when the unit reloads.

Command Replication

After both units are running, commands are replicated from one unit to the other as shown:

• Commands entered within a security context are replicated from the unit on which the security context appears in the active state to the peer unit.

  Note: context is considered in the active state on a unit if the failover group to which it belongs is in the active state on that unit.

• Commands entered in the system execution space are replicated from the unit on which failover group 1 is in the active state to the unit on which failover group 1 is in the standby state.

• Commands entered in the admin context are replicated from the unit on which failover group 1 is in the active state to the unit on which failover group 1 is in the standby state.

All configuration and file commands (copy, rename, delete, mkdir, rmdir, and so on) are replicated, with the following exceptions. The show, debug, mode, firewall, and failover lan unit commands are not replicated.

Failure to enter the commands on the appropriate unit for command replication to occur causes the configurations to be out of synchronization. Those changes may be lost the next time the initial configuration synchronization occurs.

You can use the write standby command to resynchronize configurations that have become out of sync. For Active/Active failover, the write standby command behaves as shown:

• If you enter the write standby command in the system execution space, the system configuration and the configurations for all of the security contexts on the security appliance is written to the peer unit. This includes configuration information for security contexts that are in the standby state. You must enter the command in the system execution space on the unit that has failover group 1 in the active state.

  Note: If there are security contexts in the active state on the peer unit, the write standby command causes active connections through those contexts to be terminated. Use the failover active command on the unit providing the configuration to make sure all contexts are active on that unit before entering the write standby command.

• If you enter the write standby command in a security context, only the configuration for the security context is written to the peer unit. You must enter the command in the security context on the unit where the security context appears in the active state.

Replicated commands are not saved to the Flash memory when replicated to the peer unit. They are added to the running configuration. To save replicated commands to Flash memory on both units, use the write memory or copy running-config startup-config command on the unit that you made the changes on. The command is replicated to the peer unit and cause the configuration to be saved to Flash memory on the peer unit.

Failover Triggers

In Active/Active failover, failover can be triggered at the unit level if one of the following events occurs:

• The unit has a hardware failure.

• The unit has a power failure.

• The unit has a software failure.

• The no failover active or the failover active command is entered in the system execution space.

Failover is triggered at the failover group level when one of these events occurs:

• Too many monitored interfaces in the group fail.

• The no failover active group group_id or failover active group group_id command is entered.

Failover Actions

In an Active/Active failover configuration, failover occurs on a failover group basis, not a system basis. For example, if you designate both failover groups as active on the primary unit, and failover group 1 fails, then failover group 2 remains active on the primary unit while failover group 1 becomes active on the secondary unit.

Note: When configuring Active/Active failover, make sure that the combined traffic for both units is within the capacity of each unit.

This table shows the failover action for each failure event. For each failure event, the policy (whether or not failover occurs), actions for the active failover group, and actions for the standby failover group are given.

Regular and Stateful Failover

The security appliance supports two types of failover, regular and stateful. This section includes these topics:

Regular Failover

When a failover occurs, all active connections are dropped. Clients need to re-establish connections when the new active unit takes over.

Stateful Failover

When stateful failover is enabled, the active unit continually passes per-connection state information to the standby unit. After a failover occurs, the same connection information is available at the new active unit. Supported end-user applications are not required to reconnect to keep the same communication session.

The state information passed to the standby unit includes these:

• The NAT translation table

• The TCP connection states

• The UDP connection states

• The ARP table

• The Layer 2 bridge table (when it runs in the transparent firewall mode)

• The HTTP connection states (if HTTP replication is enabled)

• The ISAKMP and IPSec SA table

• The GTP PDP connection database

The information that is not passed to the standby unit when stateful failover is enabled includes these:

• The HTTP connection table (unless HTTP replication is enabled)

• The user authentication (uauth) table

• The routing tables

• State information for security service modules

Note: If failover occurs within an active Cisco IP SoftPhone session, the call remains active because the call session state information is replicated to the standby unit. When the call is terminated, the IP SoftPhone client loses connection with the Call Manager. This occurs because there is no session information for the CTIQBE hang-up message on the standby unit. When the IP SoftPhone client does not receive a response back from the Call Manager within a certain time period, it considers the Call Manager unreachable and unregisters itself.

Failover Configuration Limitations

You cannot configure failover with these types of IP addresses:

• IP addresses obtained through DHCP

• IP addresses obtained through PPPoE

• IPv6 addresses

Additionally, these restrictions apply:

• Stateful Failover is not supported on the ASA 5505 adaptive security appliance.

• Active/Active failover is not supported on the ASA 5505 adaptive security appliance.

• You cannot configure failover when Easy VPN Remote is enabled on the ASA 5505 adaptive security appliance.

• VPN failover is not supported in multiple context mode.

Unsupported Features

Multiple context mode does not support these features:

• Dynamic routing protocols

  Security contexts support only static routes. The ultimate best of shalamar. You cannot enable OSPF or RIP in multiple context mode.

• VPN

• Multicast

Cable-Based Active/Active Failover Configuration

Prerequisites

Before you begin, verify the following:

• Both units have the same hardware, software configuration, and proper license.

• Both units are in the same mode (single or multiple, transparent or routed).

Network Diagram

This document uses this network setup:

Follow these steps in order to configure Active/Active failover using a serial cable as the failover link. The commands in this task are entered on the primary unit in the failover pair. The primary unit is the unit that has the end of the cable labeled 'Primary' plugged into it. For devices in multiple context mode, the commands are entered in the system execution space unless otherwise noted.

You do not need to bootstrap the secondary unit in the failover pair when you use cable-based failover. Leave the secondary unit powered off until instructed to power it on.

Note: Cable-based failover is only available on the PIX 500 series security appliance.

Complete these steps in order to configure cable-based, Active/Active failover:

1. Connect the failover cable to the PIX 500 series security appliances. Make sure that you attach the end of the cable marked 'Primary' to the unit you use as the primary unit, and that you attach the end of the cable marked 'Secondary' to the unit you use as the secondary unit.

2. Power on the primary unit.

3. If you have not done so already, configure the active and standby IP addresses for each data interface (routed mode), for the management IP address (transparent mode), or for the management-only interface. The standby IP address is used on the security appliance that is currently the standby unit. It must be in the same subnet as the active IP address.

   You must configure the interface addresses from within each context. Use the changeto context command to switch between contexts. The command prompt changes to hostname/context(config-if)#, where context is the name of the current context. You must enter a management IP address for each context in transparent firewall multiple context mode.

   Note: Do not configure an IP address for the Stateful Failover link if you are going to use a dedicated Stateful Failover interface. You use the failover interface ip command to configure a dedicated Stateful Failover interface in a later step.

   In the example, the outside interface for context1 of the primary PIX is configured this way:

   For Context2:

   In routed firewall mode and for the management-only interface, this command is entered in interface configuration mode for each interface. In transparent firewall mode, the command is entered in global configuration mode.

4. In order to enable Stateful Failover, configure the Stateful Failover link.

   1. Specify the interface to be used as Stateful Failover link:

      In this example, the Ethernet2 interface is used to exchange the stateful failover link state information.

      The if_name argument assigns a logical name to the interface specified by the phy_if argument. The phy_if argument can be the physical port name, such as Ethernet1, or a previously created subinterface, such as Ethernet0/2.3. This interface should not be used for any other purpose (except, optionally, the failover link).

   2. Assign an active and standby IP address to the Stateful Failover link:

      In this example , 10.0.0.1 is used as an active, and 10.0.0.2 is used as a standby IP address for the stateful failover link.

      Install dll files windows 7. Install Microsoft Practices Spg Ajaxsupport Dll. 2013 project and want to use UpdatePanel for which file Microsoft.Practices.SPG.AJAXSupport.dll is. I read many articles like this: But no where i can't find a Microsoft.Practices.SPG.AJAXSupport.dll I only find. Thanks for your reply,I did not find above mentioned. The SharePoint Guidance Library contains. The Microsoft.Practices.ServiceLocation.dll assembly into. SPG.Common, Microsoft.Practices.AJAXSupport.

      The standby IP address must be in the same subnet as the active IP address. You do not need to identify the standby IP address subnet mask.

      The Stateful Failover link IP address and MAC address do not change at failover except for when Stateful Failover uses a regular data interface. The active IP address always stays with the primary unit, while the standby IP address stays with the secondary unit.

   3. Enable the interface:

5. Configure the failover groups. You can have at most two failover groups. The failover group command creates the specified failover group if it does not exist and enters the failover group configuration mode.

   For each failover group, you need to specify whether the failover group has primary or secondary preference using the primary or secondary command. You can assign the same preference to both failover groups. For load balancing configurations, you should assign each failover group a different unit preference.

   The following example assigns failover group 1 a primary preference and failover group 2 a secondary preference:

6. Assign each user context to a failover group using the join-failover-group command in context configuration mode.

   Any unassigned contexts are automatically assigned to failover group 1. The admin context is always a member of failover group 1.

   Enter these commands to assign each context to a failover group:

7. Enable failover:

8. Power on the secondary unit and enable failover on the unit if it is not already enabled:

   The active unit sends the configuration in running memory to the standby unit. As the configuration synchronizes, the messages 'Beginning configuration replication: Sending to mate' and 'End Configuration Replication to mate' appear on the primary console.

   Note: Issue the failover command on the primary device first, and then issue it on the secondary device. After you issue the failover command on the secondary device, the secondary device immediately pulls the configuration from the primary device and sets itself as standby. The primary ASA stays up and passes traffic normally and marks itself as the active device. From that point on, whenever a failure occurs on the active device, the standby device comes up as active.

9. Save the configuration to Flash memory on the Primary unit. Because the commands entered on the primary unit are replicated to the secondary unit, the secondary unit also saves its configuration to Flash memory.

10. If necessary, force any failover group that is active on the primary to the active state on the secondary. To force a failover group to become active on the secondary unit, issue this command in the system execution space on the primary unit:

    The group_id argument specifies the group you want to become active on the secondary unit.

Configurations

This document uses these configurations:

LAN-Based Active/Active Failover Configuration

Network Diagram

This document uses this network setup:

This section describes how to configure Active/Active failover using an Ethernet failover link. When configuring LAN-based failover, you must bootstrap the secondary device to recognize the failover link before the secondary device can obtain the running configuration from the primary device.

Note: Instead of using a crossover Ethernet cable to directly link the units, Cisco recommends that you use a dedicated switch between the primary and secondary units.

This section includes the topics as shown:

Primary Unit Configuration

Complete these steps in order to configure the primary unit in an Active/Active failover configuration:

1. If you have not done so already, configure the active and standby IP addresses for each data interface (routed mode), for the management IP address (transparent mode), or for the management-only interface. The standby IP address is used on the security appliance that is currently the standby unit. It must be in the same subnet as the active IP address.

   You must configure the interface addresses from within each context. Use the changeto context command to switch between contexts. The command prompt changes to hostname/context(config-if)#, where context is the name of the current context. In transparent firewall mode, you must enter a management IP address for each context.

   Note: Do not configure an IP address for the Stateful Failover link if you are going to use a dedicated Stateful Failover interface. You use the failover interface ip command to configure a dedicated Stateful Failover interface in a later step.

   In the example, the outside interface for context1 of the primary PIX is configured this way:

   For Context2:

   In routed firewall mode and for the management-only interface, this command is entered in interface configuration mode for each interface. In transparent firewall mode, the command is entered in global configuration mode.

2. Configure the basic failover parameters in the system execution space.

   1. (PIX security appliance only) Enable LAN-based failover:

   2. Designate the unit as the primary unit:

   3. Specify the failover link:

      In this example, we use the interface ethernet 3 as LAN based failover interface.

      The if_name argument assigns a logical name to the interface specified by the phy_if argument. The phy_if argument can be the physical port name, such as Ethernet1, or a previously created subinterface, such as Ethernet0/2.3. On the ASA 5505 adaptive security appliance, the phy_if specifies a VLAN. This interface should not be used for any other purpose (except, optionally, the Stateful Failover link).

   4. Specify the failover link active and standby IP addresses:

      For this example, we use 10.1.0.1 as active and 10.1.0.2 as standby IP addresses for failover interface.

      The standby IP address must be in the same subnet as the active IP address. You do not need to identify the standby IP address subnet mask. The failover link IP address and MAC address do not change at failover. The active IP address always stays with the primary unit, while the standby IP address stays with the secondary unit.

3. To enable Stateful Failover, configure the Stateful Failover link:

   1. Specify the interface to be used as Stateful Failover link:

      The if_name argument assigns a logical name to the interface specified by the phy_if argument. The phy_if argument can be the physical port name, such as Ethernet1, or a previously created subinterface, such as Ethernet0/2.3. This interface should not be used for any other purpose (except, optionally, the failover link).

      Note: If the Stateful Failover link uses the failover link or a regular data interface, then you only need to supply the if_name argument.

   2. Assign an active and standby IP address to the Stateful Failover link.

      Note: If the Stateful Failover link uses the failover link or a regular data interface, skip this step. You have already defined the active and standby IP addresses for the interface.

      The standby IP address must be in the same subnet as the active IP address. You do not need to identify the standby address subnet mask. The state link IP address and MAC address do not change at failover. The active IP address always stays with the primary unit, while the standby IP address stays with the secondary unit.

   3. Enable the interface.

      Note: If the Stateful Failover link uses the failover link or regular data interface, skip this step. You have already enabled the interface.

4. Configure the failover groups. You can have at most two failover groups. The failover group command creates the specified failover group if it does not exist and enters the failover group configuration mode.

   For each failover group, specify whether the failover group has primary or secondary preference using the primary or secondary command. You can assign the same preference to both failover groups. For load balancing configurations, you should assign each failover group a different unit preference.

   The following example assigns failover group 1 a primary preference and failover group 2 a secondary preference:

5. Assign each user context to a failover group using the join-failover-group command in context configuration mode.

   Any unassigned contexts are automatically assigned to failover group 1. The admin context is always a member of failover group 1.

   Enter these commands to assign each context to a failover group:

6. Enable failover.

Secondary Unit Configuration

When configuring LAN-based Active/Active failover, you need to bootstrap the secondary unit to recognize the failover link. This allows the secondary unit to communicate with and receive the running configuration from the primary unit.

Complete these steps in order to bootstrap the secondary unit in an Active/Active failover configuration:

1. (PIX security appliance only) Enable LAN-based failover.

2. Define the failover interface. Use the same settings as you used for the primary unit:

   1. Specify the interface to be used as the failover interface.

      The if_name argument assigns a logical name to the interface specified by the phy_if argument. The phy_if argument can be the physical port name, such as Ethernet1, or a previously created subinterface, such as Ethernet0/2.3. On the ASA 5505 adaptive security appliance, the phy_if specifies a VLAN.

   2. Assign the active and standby IP address to the failover link:

      Note: Enter this command exactly as you entered it on the primary unit when you configured the failover interface.

      The standby IP address must be in the same subnet as the active IP address. You do not need to identify the standby address subnet mask.

   3. Enable the interface.

3. Designate this unit as the secondary unit:

   Note: This step is optional because by default units are designated as secondary unless previously configured otherwise.

4. Enable failover.

   After you enable failover, the active unit sends the configuration in running memory to the standby unit. As the configuration synchronizes, the messages Beginning configuration replication: Sending to mate and End Configuration Replication to mate appear on the active unit console.

   Note: Issue the failover command on the primary device first, and then issue it on the secondary device. After you issue the failover command on the secondary device, the secondary device immediately pulls the configuration from the primary device and sets itself as standby. The primary ASA stays up and passes traffic normally and marks itself as the active device. From that point on, whenever a failure occurs on the active device, the standby device comes up as active.

5. After the running configuration has completed replication, enter this command to save the configuration to Flash memory:

6. If necessary, force any failover group that is active on the primary to the active state on the secondary unit. To force a failover group to become active on the secondary unit, enter this command in the system execution space on the primary unit:

   The group_id argument specifies the group you want to become active on the secondary unit.

Configurations

This document uses these configurations:

Note: Refer the Cable based Failover Configuration section, PIX1 - Context1 Configuration and PIX1 - Context2 Configuration for context configuration in LAN based failover scenario.

Verify

Use of the show failover Command

This section describes the show failover command output. On each unit, you can verify the failover status with the show failover command.

Primary PIX

Secondary PIX

Use the show failover state command to verify the state.

Primary PIX

Secondary unit

In order to verify the IP addresses of the failover unit, use the show failover interfacecommand.

Primary unit

Secondary unit

View of Monitored Interfaces

In order to view the status of monitored interfaces: In single context mode, enter the show monitor-interface command in global configuration mode. In multiple context mode, enter the show monitor-interface within a context.

Note: In order to enable health monitoring on a specific interface, use the monitor-interface command in global configuration mode:

Primary PIX

Secondary PIX

Note: If you do not enter a failover IP address, the show failover command displays 0.0.0.0 for the IP address, and monitoring of the interfaces remains in a 'waiting' state. You must set a failover IP address for failover to work. For more information about different states for failover, refer to show failover.

By default, monitoring of physical interfaces is enabled, and monitoring of subinterfaces is disabled.

Display of the Failover Commands in the Running Configuration

In order to view the failover commands in the running configuration, enter this command:

All of the failover commands are displayed. On units that run in multiple context mode, enter the show running-config failover command in the system execution space. Enter the show running-config all failover command to display the failover commands in the running configuration and include commands for which you have not changed the default value.

Failover Functionality Tests

In order to test failover functionality, perform these steps:

1. Test that your active unit or failover group passes traffic as expected with FTP (for example) to send a file between hosts on different interfaces.

2. Force a failover to the standby unit with this command:

   • For Active/Active failover, enter the following command on the unit where the failover group containing the interface connecting your hosts is active:

3. Use FTP to send another file between the same two hosts.

4. If the test was not successful, enter the show failover command to check the failover status.

5. When you are finished, you can restore the unit or failover group to active status with this command:

   • For Active/Active failover, enter the following command on the unit where the failover group containing the interface connecting your hosts is active:

Forced Failover

In order to force the standby unit to become active, enter one of these commands:

Enter this command in the system execution space of the unit where the failover group is in the standby state:

Or, enter this command in the system execution space of the unit where the failover group is in the active state:

Entering this command in the system execution space causes all failover groups to become active:

Disabled Failover

In order to disable failover, enter this command:

If you disable failover on an Active/Standby pair, it causes the active and standby state of each unit to be maintained until you restart. For example, the standby unit remains in standby mode so that both units do not start to pass traffic. In order to make the standby unit active (even with failover disabled), see the Forced Failover section.

If you disable failover on an Active/Active pair, it causes the failover groups to remain in the active state on whichever unit they are currently active on, no matter which unit they are configured to prefer. The no failover command can be entered in the system execution space.

Restoration of a Failed Unit

In order to restore a failed Active/Active failover group to an unfailed state, enter this command:

If you restore a failed unit to an unfailed state, it does not automatically make it active; restored units or groups remain in the standby state until made active by failover (forced or natural). An exception is a failover group configured with the preempt command. If previously active, a failover group becomes active if it is configured with the preempt command and if the unit on which it failed is its preferred unit.

Replace the Failed Unit with a New Unit

Complete these steps in order to replace a failed unit with a new unit:

1. Run the no failover command on the primary unit.

   The status of the secondary unit shows standby unit as not detected.

2. Unplug the primary unit, and connect the replacement primary unit.

3. Verify that the replacement unit runs the same software and ASDM version as the secondary unit.

4. Run these commands on the replacement unit:

5. Plug the replacement primary unit to the network, and run this command:

Troubleshoot

When a failover occurs, both security appliances send out system messages. This section includes these topics:

Failover System Messages

The security appliance issues a number of system messages related to failover at priority level 2, which indicates a critical condition. In order to view these messages, refer to the Cisco Security Appliance Logging Configuration and System Log Messages to enable logging and to see descriptions of the system messages.

Note: Within switchover, failover logically shuts down and then brings up interfaces, which generates syslog 411001 and 411002 messages. This is normal activity.

Primary Lost Failover communications with mate on interface interface_name

This failover message is displayed if one unit of the failover pair can no longer communicate with the other unit of the pair. Primary can also be listed as Secondary for the secondary unit.

(Primary) Lost Failover communications with mate on interface interface_name

Verify that the network that is connected to the specified interface is functioning correctly.

Debug Messages

In order to see debug messages, enter the debug fover command. Refer to the Cisco Security Appliance Command Reference, Version 7.2 for more information.

Note: Because debugging output is assigned high priority in the CPU process, it can drastically affect system performance. For this reason, use the debug fover commands only to troubleshoot specific problems or within troubleshooting sessions with Cisco technical support staff.

SNMP

In order to receive SNMP syslog traps for failover, configure the SNMP agent to send SNMP traps to SNMP management stations, define a syslog host, and compile the Cisco syslog MIB into your SNMP management station. Refer to the snmp-server and logging commands in the Cisco Security Appliance Command Reference, Version 7.2 for more information.

Failover Polltime

In order to specify the failover unit poll and hold times, issue the failover polltime command in global configuration mode.

The failover polltime unit msec [time] represents the time interval to check the existence of the standby unit by polling hello messages.

Similarly, the failover holdtime unit msec [time] represents the time period during which a unit must receive a hello message on the failover link, after which the peer unit is declared to have failed.

Refer to failover polltime for more information.

WARNING: Failover message decryption failure.

Error message:

This problem occurs due to failover key configuration. In order to resolve this issue, remove the failover key, and configure the new shared key.

Related Information