Interfaces are important in ASAv failover on VIRL
One reader asked me few days ago following question when he had problem establishing the failover in his lab: “I’ve tried to create ASA failover pair on VIRL and it was not working. I’ve looked through manual and VIRL forum for the solution. I believe that failover is supported configuration on VIRL. I think my configuration is correct, nodes can ping each other but I still cannot establish failover relationship”. Configuration he made was correct except he forgot about one thing – interfaces numbers are important when you setup failover using ASAv.
Cisco VIRL uses ASAv image for virtual firewalls. This is same image that you use in production on ESXi. That means all restrictions applies also to virtual firewall if you run it on VIRL. In this image we must configure failover link using interfaces GigabitEthernet0/8. It’s clearly stated in documentation. If we use any other interface the configuration will be accepted but failover never established.
failover lan unit primary failover lan interface Fail-link GigabitEthernet0/8 failover replication http failover link State-link GigabitEthernet0/7 failover interface ip Fail-link 192.168.255.253 255.255.255.252 standby 192.168.255.254 failover interface ip State-link 192.168.254.253 255.255.255.252 standby 192.168.254.254 failover ipsec pre-shared-key 0 FailoverKey failover
We also need to remember we can’t configure Active-Active failover. This mode is not supported so we have to stick to Active-Standby model. It’s direct result of lack of support for virtual contexts so remember about it as well.