Hi,
The explanation for that can be found in the ASAs syslog messages document.
Here it is
103001
Error Message %ASA-1-103001: (Primary) No response from other firewall (reason
code = code).
Explanation This is a failover message, which is displayed if the primary unit is unable to communicate with the secondary unit over the failover cable. (Primary) can also be listed as (Secondary). for the secondary unit. Table 1-2 lists the reason codes and the descriptions to determine why the failover occurred.
Table 1-2 Reason Codes
|
Reason Code
|
Description
|
|
1
|
The local unit is not receiving the hello packet on the failover LAN interface when LAN failover occurs or on the serial failover cable when serial failover occurs, and declares that the peer is down.
|
|
2
|
An interface did not pass one of the four failover tests, which are as follows: 1) Link Up, 2) Monitor for Network Traffic, 3) ARP, and 4) Broadcast Ping.
|
|
3
|
No proper ACK for 15+ seconds after a command was sent on the serial cable.
|
|
4
|
The local unit is not receiving the hello packet on the failover LAN and other data interfaces and it is declaring that the peer is down.
|
|
5
|
The failover LAN interface is down, and other data interfaces are not responding to additional interface testing. In addition, the local unit is declaring that the peer is down.
|
Recommended Action Verify that the failover cable is connected correctly and both units have the same hardware, software, and configuration. If the problem persists, contact the Cisco TAC.
Are you saying that the Primary ASA loses all connectivity to the Secondary ASA (looking at the log messages). Judging by the above Cisco description it would mean the Primary ASA isnt getting Failover Hellos through any of the monitored interfaces which again would make it seem like the Secondary Firewall is expriencing some problems.
- Jouni
