Users Guide

putting it first into maintenance mode, then performing the firmware update and rebooting the
server, and finally bringing the server out of maintenance mode before moving on to the next
server.
Apply Updates on Next Reboot — Select the option to update the firmware at the next server
reboot. ASM stages the firmware update to each server selected until reboot.
SM stages the firmware update to each server selected. The update will take effect at the next
server reboot.
Schedule Update — Select this option and then select the date and time to update the firmware.
ASM applies the firmware updates at a selected date and time and then reboot to all servers
within this service. For servers belonging to a VMware vSphere cluster, servers will be updated
one at a time by putting it first into maintenance mode, then performing the firmware update and
rebooting the server, and finally bringing the server out of maintenance mode before moving on
to the next server.
2. Click Save.
NOTE: Firmware update on a server that is part of a cluster is successful only if the server is set
in maintenance mode. ASM sets servers in a cluster in maintenance mode before updating
firmware. To ensure that the server remains in maintenance mode, ensure that there are other
servers available in the cluster to host the virtual machines of the server that will be updated.
Removing resources
NOTE: On the user with Administrator role can remove the resource from ASM.
To remove any particular resource from ASM, perform the following steps:
1. On the home page, click Resources.
2. On the Resources page, click the All Resources tab.
3. From the list of resources, select one or more resources, and click Remove.
4. Click OK when the confirmation message is displayed.
If you remove a Chassis, the Chassis and associated servers and I/O modules are removed from ASM. The
removal process shuts down the servers and erases identity information to prevent potential corruption,
and identity information returns to the associated pool. Associated targets (for example, storage volume)
are not affected.
NOTE: You cannot remove a chassis that is in any Pending state.
If you remove a server, the server state changes to Pending. The server powers off, ASM erases network
identity information from the server to prevent potential corruption, and network identity information
returns to the associated pool.
Viewing firmware compliance report
To view the compliance report of any resource:
1. On the Resources page, select a resource to view the firmware compliance report.
2. In the right pane, under Firmware Status, click View Compliance Report.
101