ASA failover issue

Syed Khaja Afzal Hussain — Tue, 12 Mar 2019 02:18:08 GMT

Dears all,

I have some issue on ASA active and standby devices. the below behaviour is normal or abnormal, because we are facing slow network. Can you tell me about below errors.

Monitored Interfaces 11 of 1025 maximum

Version: Ours 8.4(4)1, Mate 8.4(4)1

Last Failover at: 18:56:49 UTC Oct 24 2012

This host: Secondary - Active

Active time: 23936387 (sec)

slot 0: ASA5585-SSP-20 hw/sw rev (1.0/8.4(4)1) status (Up Sys)

Interface voice (192.168.9.1): Normal (Monitored)

Interface ServersZone (192.168.10.1): Normal (Monitored)

Interface serv_dev (192.168.12.1): Normal (Monitored)

Interface serve_quality (192.168.13.1): Normal (Monitored)

Interface ERPZone (192.168.14.1): Normal (Not-Monitored)

Interface vmware (192.168.17.1): Normal (Monitored)

Interface Storage_Blade (192.168.18.1): Normal (Monitored)

Interface VM_KERNEL (192.168.19.1): Normal (Not-Monitored)

Interface access_control (192.168.30.1): Normal (Monitored)

Interface security_device (192.168.33.1): Normal (Not-Monitored)

Interface net_mgmt (192.168.34.1): Normal (Monitored)

Interface cam_mgmt (192.168.35.1): Normal (Not-Monitored)

Interface OUTSIDE (192.168.32.18): Normal (Monitored)

slot 1: empty

Other host: Primary - Standby Ready

Active time: 837 (sec)

slot 0: ASA5585-SSP-20 hw/sw rev (1.0/8.4(4)1) status (Up Sys)

Interface voice (192.168.9.2): Normal (Monitored)

Interface ServersZone (192.168.10.1): Normal (Monitored)

Interface serv_dev (192.168.12.2): Normal (Monitored)

Interface serve_quality (192.168.13.2): Normal (Monitored)

Interface ERPZone (192.168.14.2): Normal (Not-Monitored)

Interface vmware (192.168.17.2): Normal (Monitored)

Interface Storage_Blade (192.168.18.2): Normal (Monitored)

Interface VM_KERNEL (192.168.19.2): Normal (Not-Monitored)

Interface access_control (192.168.30.2): Normal (Monitored)

Interface security_device (192.168.33.2): Normal (Not-Monitored)

Interface net_mgmt (192.168.34.2): Normal (Monitored)

Interface cam_mgmt (192.168.35.2): Normal (Not-Monitored) ------> this behaviour is normall or not?

Interface OUTSIDE (192.168.32.18): Normal (Monitored)

slot 1: empty

-------------------------------

show failover state

State Last Failure Reason Date/Time

This host - Secondary

Active Ifc Failure 18:56:45 UTC Oct 24 2012

Other host - Primary

Standby Ready Ifc Failure 18:56:49 UTC Oct 24 2012

access_control: Failed ----> This is normal behavoiur

net_mgmt: Failed

====Configuration State===

Sync Done - STANDBY

====Communication State===

Mac set

which i was highlighted in bold not monitored is normal or any issue.

ASA failover issue

Marvin Rhoads — Sun, 28 Jul 2013 14:56:15 GMT

The not-monitored / monitored state is just telling you how failover is configured. We typically setup ASA to monitor all active interfaces so that if any one goes down a failover event is triggered. (Reference)

Your "show failover state" output explains that the last failover event was due to loss of connectivity on two interfaces on the Primary unit.

Since the current state is "Secondary - Active" and "Primary - Standby Ready", all is well with respect to the ASA failover pair.

ASA failover issue

mvsheik123 — Sun, 28 Jul 2013 15:02:33 GMT

To add to Marvin's explanation, refer to the below link...

http://www.cisco.com/en/US/docs/security/asa/asa72/command/reference/s3_72.html#wp1285409

Thx

topic ASA failover issue in Network Security

ASA failover issue

ASA failover issue

ASA failover issue