cords from the server. Attach an antistatic strap to your wrist and to a metal area on the
chassis. Following this practice equalizes the electrical potentials between you and the
server.
Note:
Antistatic wrist straps might be included with options and components.
• Use an antistatic mat.
Place ESD-sensitive components such as the motherboard, DIMMS (memory modules),
and other printed circuit board (PCB) cards on an antistatic mat. You can use the following
items as an antistatic mat:
– An antistatic bag used to wrap an Oracle replacement part
– An Oracle ESD mat (orderable item)
– A disposable ESD mat (shipped with some replacement parts or optional system
components)
Powering Down the Server
Gracefully shut down the server host to prevent data from being corrupted. Performing a
graceful shutdown ensures that the system is ready for restart. If the server is not responding,
or you must shut down the server quickly, perform an immediate shutdown.
Note:
Components that are hot-pluggable do not require the server to be powered down.
For more information, see the component replacement procedures in this guide.
Before Powering Down a Node
Servers in a Private Cloud Appliance rack are integrated components of a multinode
environment. Unless a server experiences a sudden failure or must be shut down in an
emergency situation, powering down server nodes in the appliance should be planned and
performed carefully to minimize impact on the performance and availability of the appliance
services and resources.
When planning to power down server nodes, take these points into account:
System load
Powering down servers means system capacity is temporarily reduced. It makes sense to plan
maintenance operations at a time when system load is typically at its lowest; for example
during the night, over the weekend, and so on.
Instance availability
Many workloads need to remain available while a server is offline for maintenance. You can
live-migrate compute instances to other compute nodes in the same fault domain, or restart
them in another fault domain. The available compute capacity in the three fault domains
determines whether all workloads can remain operational or if some need to be scaled down
or even interrupted temporarily.
Chapter 5
Preparing the Server for Component Replacement
5-4
To Next Page
Loading...
