ASA multi-context failover (Active/Active)

-

 















1. Change both ASA to multi-context mode

ciscoasa(config)# mode multiple 


2. Configure failover 

2.1 on the primary unit

failover lan unit primary
failover lan interface FO Ethernet2
failover link FO Ethernet2
failover interface ip FO 172.16.1.1 255.255.255.0 standby 172.16.1.2

2.2 On the secondary unit:

failover lan unit secondary
failover lan interface FO Ethernet2
failover link FO Ethernet2
failover interface ip FO 172.16.1.1 255.255.255.0 standby 172.16.1.2

3. Configure failover group on the primary unit
Specify group 1 active one primary unit and group2 active on secondary unit, specify active delay to 1 minute.

failover group 1
  primary
  preempt 60
failover group 2
  secondary
  preempt 60

4. enabled failover on both units

ciscoasa(config)#failover

from now on, failover is up, configuration continue on the active ASA:

5. create resource class:

class gold
  limit-resource VPN Other 3
  limit-resource ASDM 5
  limit-resource SSH 5
  limit-resource Telnet 5
  limit-resource Mac-addresses 10000

6. Configure port channel and sub interfaces will be used for inside interfaces

  interface Ethernet1
 channel-group 1 mode on
interface Ethernet3
 channel-group 1 mode on

interface Port-channel1.100
 vlan 100
!
interface Port-channel1.200
 vlan 200

7. E0 will be used as shared outside interface for all contexts

8.Create contexts:
context admin
  config-url disk0:/admin.cfg
!

context c1
  member gold
  allocate-interface Ethernet0
  allocate-interface Port-channel1.100
  config-url disk0:/c1.cfg
  join-failover-group 1
!

context c2
  member gold
  allocate-interface Ethernet0
  allocate-interface Port-channel1.200
  config-url disk0:/c2.cfg
  join-failover-group 2
!

9. Configure context c1
interface Ethernet0
 nameif outside
 security-level 0
 ip address 192.168.2.120 255.255.255.0 standby 192.168.2.121
!
interface Port-channel1.100
 nameif inside
 security-level 100
 ip address 10.0.100.1 255.255.255.0 standby 10.0.100.2

10. Configure context c2:
interface Ethernet0
 nameif outside
 security-level 0
 ip address 192.168.2.122 255.255.255.0 standby 192.168.2.123
!
interface Port-channel1.200
 nameif inside
 security-level 100
 ip address 10.0.200.1 255.255.255.0 standby 10.0.200.2




Comments

Post a Comment

Popular posts from this blog

Firepower FMC and FTD troubleshooting

-
 1. Display real time log on FMC or FTD: pigtail for example: pigtail | grep 192.168.2.20                      pigtail | grep sftunnel 2. Restart communication channel manage_procs.pl run it from  the sensor only, run it from FMC will reset all sensors' channel. This scripts are nice to be used when the FMC and FTD have communication problems like heartbeats are not received, policy deployment is failing or events are not received > expert ************************************************************** NOTICE - Shell access will be deprecated in future releases          and will be replaced with a separate expert mode CLI. ************************************************************** admin@FTD:~$ sudo su Password: root@FTD:/home/admin# manage_procs.pl ****************  Configuration Utility  **************  1   Reconfigure Correlator  2   Reconfigure and flush Correlator  3    Restart Comm. channel  4   Update routes  5   Reset all routes  6   Validate Network  0   Exit *****
Read more

ASA IKEv1 VPN troubleshooting Steps and Tips

-
  1. Phase I proposal mismatch  Run show crypto isakmp sa  Initiator: MM_WAIT_MSG2 Responder: No info  Most likely this is phase1 proposal mismatch, verify IKEv1 policy, other symptoms:   Initiator log: Information Exchange processing failed All configured IKE versions failed to establish the tunnel Initiator debug: Received an un-encrypted NO_PROPOSAL_CHOSEN notify message, dropping Responder log: Error processing payload: Payload ID Responder debug:  All SA proposals found unacceptable 2. IKE version mismatch:  Run  show crypto isakmp sa  no info at both initiator and responder Initiator log: Removing peer from correlator table failed, no match! Reason: User Requested  All configured IKE versions failed to establish the tunnel Initiator debug: Oakley begin quick mode PHASE 1 COMPLETED IKE Initiator sending 1st QM pkt Removing peer from correlator table failed, no match! Session is being torn down. Reason: User Requested Responder log: Tunnel Rejected: Conflicting protocols specified
Read more

Firepower 2100/1100 FTD/ASA initial setup, reimage, upgrade.

-
  Chassis FXOS and FTD share same management IP (default 192.168.45.45) Chassis FXOS (192.168.45.45) and ASA ()use different management IP although on same physical interface. SSH to FXOS/FTD are on FTD CLI prompt, go to FXOS using the  connect fxos  command Console to Chassis is on FXOS CLI prompt, go to FTD using the  connect ftd  command The Firepower 1100 does not support the FXOS Firepower Chassis Manager; only a limited CLI is supported for troubleshooting purposes. The Firepower 2100 runs an underlying operating system called the Firepower eXtensible Operating System (FXOS).  If you run ASA on Firepower 2100, ASA can be in the following modes: Appliance mode (the default after ASA 9.13)—Appliance mode lets you configure all settings in the ASA. Only advanced troubleshooting commands are available from the FXOS CLI. See the  FXOS troubleshooting guide  for more information. Firepower Chassis Manager is not supported . ciscoasa# connect fxos [admin] Connecting to fxos. Connected
Read more