Комментарии:
Hi Ally, When you issue the write standby command on the primary unit, it copies the running configuration to the secondary unit. All your configuration, outside of the failover config, should be carried out on the primary unit. Hope this helps. Laurence
ОтветитьReally good movie. Thank you mate! I think it is worth to mentioned about "prompt hostname state" command which tells you what is the current state.
ОтветитьI don't think so, you can always tell what unit your currently working on by using: show failover. Unfortunately because the hostname command is part of the running config it gets copied over.
ОтветитьHi Djbsd, Yes you can configure a separate interface for the second ISP, use the SLA monitor and route tracking features to implement this. Laurence
ОтветитьSee my video on Redundant ISPs to configure this.
ОтветитьCan this procedure work when there is already a configuration on the active one?
ОтветитьI just tried this in a lab enviroment and the one that was configured as secondary pushed his configuration to the primary. Is there a way to prevent this. Doing this on my live system would loose everything.
ОтветитьHi Steve, this is unusual behavior - are you sure you weren't entering commands on the secondary unit? You can always tell by entering 'show failover'. Thanks
ОтветитьHi Laurence, I am replacing pix with NEW ASA, can i copy and paste the existing configuration from the pix and paste on to ASA and tweak little bite or between the two devices it is complete different animal? thanks
ОтветитьIt worked fine when I just did it on the live firewall. Thank you for the great vid!! A problem that I still have is that cisco anyconnect will close the session when the asa's do a failover. Is this normal or should sessions failover be possible?
ОтветитьLaurence ur German right?
ОтветитьThank you for the kick start man!
ОтветитьNice vid man. Do you need to manually swap the ISP connection to the new ASA?
ОтветитьThank you sir.
ОтветитьI had to enable failover today on a new ASA5515. This video helped me more than sorting through mounds of Cisco documentation. Thanks.
ОтветитьNice Job...straight to the point.
ОтветитьIt also does work with 5505s.
ОтветитьCan you help me configure Failover using Ipv6 on Firewall Asa?
ОтветитьGreat video! So precise and clear!
Ответитьjust getting around to migrate pix to asa.....on failover config is the secret key optional?
ОтветитьCame here because although failover was occuring, nothing on my sub-interfaces of the inside int would respond when secondary ASA took over.
'Sh failover' only listed 1 monitored interface (OUTSIDE). Entering command 'monitor-interface *NAME*' has caused 'sh failover' to list 7 monitored interfaces.
Looks like now it's back to the office at half-past midnight to simulate a failure and see if this has fixed my issue!
Thanks, was hoping you'll show us how to force failover and we can see it in action
Ответить