A10 Certified Professional System Administration 4: Reboot Command and its Impact on aVCS Chassis

Reboot Command and its Impact on aVCS Chassis


When you execute a reboot command on the vMaster, how is aVCS Chassis affected?



Click on the arrows to vote for the correct answer

A. B. C. D.


When the reboot command is executed on the vMaster, the behavior of the aVCS chassis depends on the version of the aVCS software.

If the aVCS software is version 2.7 or later, then the answer is (C) Reboot is performed on vMaster.

If the aVCS software is version 2.6 or earlier, then the answer is (B) All devices in the chassis are rebooted.

In aVCS version 2.7 or later, the vMaster is responsible for maintaining the configuration and state information for the entire chassis. When the vMaster is rebooted, it will come back online and continue to function as the master controller for the chassis, while the vBlades continue to operate uninterrupted. During the reboot process, the vMaster will be unavailable for a short period, but the rest of the chassis will remain functional.

In aVCS version 2.6 or earlier, the vMaster was responsible for managing the entire chassis, including the vBlades. When the vMaster was rebooted, all devices in the chassis were also rebooted, including the vBlades. This resulted in a longer downtime for the entire chassis.