01-07-2016 06:45 PM - last edited on 03-25-2019 05:57 PM by ciscomoderator
1. do "hw-module 1 reload" to reload IPS cause failover that make ASA02 become active if ASA01 originally is active?
2. is this command "hw-module 1 reload" only can apply to active unit ? in another words, if i type this command in secondary unit ASA02 which is not active, this command can not reload IPS02, do i need to do failover first to make ASA02 active first in order to reload IPS02 ?
Solved! Go to Solution.
01-08-2016 09:39 AM
Hi,
Ans1: Yes, 'hw-module 1 reload' would cause failover and would make ASA02 as Active. This is because the reload of the module on ASA02 would make the ASA unit as Unhealthy.
Ans2: 'hw-module 1 reload' command is independent of active/standby status. It is a Unit based command. It could be implemented on Standby Unit as well.
If you are generally reloading the module or upgrading the module, then it is always recommended to reload the module on Standby Unit so that Active Unit would remain healthy and continue to pass traffic. Once you reload the Standby Unit, it would go in failed state first and then when the module comes up fine, it would comes back in standby status.
Then change unit from Standby to Active and then reload the newly made standby unit.
Hope it answers your queries.
Regards,
Akshay Rastogi
Remember to rate helpful posts.
01-08-2016 10:17 AM
You can send the command to the secondary unit if you are logged into the primary unit:
failover exec standby hw-module 1 reload
Also, as of ASA 9.5, we can disable hardware module monitoring for the fialover cluster:
no health-check monitor-interface service-module
01-08-2016 09:39 AM
Hi,
Ans1: Yes, 'hw-module 1 reload' would cause failover and would make ASA02 as Active. This is because the reload of the module on ASA02 would make the ASA unit as Unhealthy.
Ans2: 'hw-module 1 reload' command is independent of active/standby status. It is a Unit based command. It could be implemented on Standby Unit as well.
If you are generally reloading the module or upgrading the module, then it is always recommended to reload the module on Standby Unit so that Active Unit would remain healthy and continue to pass traffic. Once you reload the Standby Unit, it would go in failed state first and then when the module comes up fine, it would comes back in standby status.
Then change unit from Standby to Active and then reload the newly made standby unit.
Hope it answers your queries.
Regards,
Akshay Rastogi
Remember to rate helpful posts.
01-08-2016 10:17 AM
You can send the command to the secondary unit if you are logged into the primary unit:
failover exec standby hw-module 1 reload
Also, as of ASA 9.5, we can disable hardware module monitoring for the fialover cluster:
no health-check monitor-interface service-module
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide