+ Reply to Thread
Results 1 to 5 of 5

Thread: I am unable to establish failover on my asa 5520

  1. #1
    Junior Member
    Join Date
    Mar 2008
    Posts
    1

    Default I am unable to establish failover on my asa 5520

    What could be possible wrong with my config?

    Primary
    failover
    failover lan unit primary
    failover lan interface ASA_Failover GigabitEthernet0/3
    failover link ASA_Failover GigabitEthernet0/3
    failover interface ip ASA_Failover 192.168.199.2 255.255.255.252 standby 192.168.199.3

    FW00# sh fail state

    State Last Failure Reason Date/Time
    This host - Primary
    Active None
    Other host - Secondary
    Not Detected Comm Failure 06:33:57 CST Mar 1 2007

    ====Configuration State===
    ====Communication State===

    Secondary:
    interface GigabitEthernet0/3
    description LAN/STATE Failover Interface

    failover
    failover lan unit secondary
    failover lan interface ASA_Failover GigabitEthernet0/3
    failover link ASA_Failover GigabitEthernet0/3
    failover interface ip ASA_Failover 192.168.199.2 255.255.255.252 standby 192.168.199.3

    FW01# sh fail state

    State Last Failure Reason Date/Time
    This host - Secondary
    Active None
    Other host - Primary
    Not Detected None

  2. #2
    Junior Member
    Join Date
    Aug 2008
    Posts
    4

    Default

    This appears to be a physical connectivity issue on the failover interface. Assuming the interface is turned up and has L2 and L3 connectivity, try creating a capture on that interface to see if you can see traffic from the other device.

    config t
    access-list cap-acl permit ip any any
    capture cap-failover interface ASA_Failover access-list cap-acl
    sh cap cap-failover

    If you do not see traffic from the other firewall, you have a physical connectivity issue. If you do see traffic, please post the results in this forum and we will figure it out.

    For more information on captures, check out the post on my forum:
    netleetsDOTcom
    www.netleets.com
    IT Security news and forums for security professionals

  3. #3
    Junior Member
    Join Date
    Aug 2008
    Posts
    4

    Default cont

    Was this able to help you?
    www.netleets.com
    IT Security news and forums for security professionals

  4. #4
    Administrator
    Join Date
    Aug 2008
    Posts
    39

    Default

    With a 5-month delay, I'm guessing no

  5. #5
    Junior Member
    Join Date
    Dec 2008
    Posts
    8

    Default

    I think the problem is on the IP addresses you use for the failover link. Since its a .252 subnet, its better to use 192.168.199.1 for the Active unit and 192.168.199.2 for the Failover unit. 199.3 is the broadcast address so this might be the problem.




    Quote Originally Posted by rionel View Post
    What could be possible wrong with my config?

    Primary
    failover
    failover lan unit primary
    failover lan interface ASA_Failover GigabitEthernet0/3
    failover link ASA_Failover GigabitEthernet0/3
    failover interface ip ASA_Failover 192.168.199.2 255.255.255.252 standby 192.168.199.3

    FW00# sh fail state

    State Last Failure Reason Date/Time
    This host - Primary
    Active None
    Other host - Secondary
    Not Detected Comm Failure 06:33:57 CST Mar 1 2007

    ====Configuration State===
    ====Communication State===

    Secondary:
    interface GigabitEthernet0/3
    description LAN/STATE Failover Interface

    failover
    failover lan unit secondary
    failover lan interface ASA_Failover GigabitEthernet0/3
    failover link ASA_Failover GigabitEthernet0/3
    failover interface ip ASA_Failover 192.168.199.2 255.255.255.252 standby 192.168.199.3

    FW01# sh fail state

    State Last Failure Reason Date/Time
    This host - Secondary
    Active None
    Other host - Primary
    Not Detected None

+ Reply to Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts