When I started doing the labs I tried not to peek at the workbook’s solutions nor the videos but as I advanced I realized it was the whole point of it, at the starting line I couldn’t be just demanding myself to know how to do stuff out of my head without having practiced for almost a month after the bootcamp was done. So after going through labs 1-8 in my first 4 hours of practice and finding myself lost by in the last two labs (7 and 8) what I decided to do was make notes on everything I wasn’t very familiar with as way to help me burn it to my brain permanently, it’s how it works for me.
FailOver
On the first ASA/PIX:
int e0/2
no sh
exit
failover lan interface FailOverLink e0/2
failover interface ip FailOverLink 192.168.15.1 255.255.255.0 standby 192.168.15.2
failover key 4ny1UL1k3
failover lan unit primary
failover

On the second ASA/PIX:

int e0/2
no sh
exit
failover lan interface FailOverLink e0/2
failover interface ip FailOverLink 192.168.15.1 255.255.255.0 standby 192.168.15.2
failover key 4ny1UL1k3
failover lan unit secondary (this is the command that makes a difference)
failover

After you are done on both firewalls you will see a note saying it synched the configs, one last thing is left to make it work the way it’s supposed to, go to each interface and configure the standby ip on it, if you are using multiple contexts make sure you do the same for each one too:

ip address 15.15.15.1 255.255.255.0 standby 15.15.15.2

Also, if you have enough interfaces you can use the stateful failover feature, what this does is that keeps sessions, translations synched between the two boxes and when there’s a failure you don’t loose all the connections opened, so on both boxes you got to do:

int e0/3
no sh
exit
failover link StateFulFOLink e0/3
failover interface ip StateFulFOLink 192.168.16.1 255.255.255.0 standby 192.168.16.2

More later, got to do some BBQ…