Risky Operations
Risky operations are classified into the following levels:
- Minor: Operation that does not modify the feature configurations but may result in the loss of user-defined key data.
- Major: Operation that may cause managed resources to be unreachable or interrupt some services running on a node.
- Critical: Operation that may cause interruption of a large number of services on the entire network.
For details about risky operations on server hardware, see Table 1. For details about risky operations on software, see Table 2.
No. |
Operation |
Impact |
Risk Level |
Operation Requirements in Production Environment |
Operation Requirements in Test Environment |
|---|---|---|---|---|---|
1 |
Replacing server parts |
Perform this operation in strict accordance with the operation instructions to avoid function failures and hardware damages. |
Critical |
|
This operation must be performed by maintenance personnel or with their consent. |
2 |
Powering off unexpectedly during the CPLD upgrade |
This failure may damage the CPLD file, affecting the functions. Re-upgrading is required. |
|||
3 |
Powering off unexpectedly during the BIOS upgrade |
This failure may damage the BIOS and affect its functions. Re-upgrading is required. |
|||
4 |
Powering off unexpectedly during the iBMC upgrade |
This failure may damage the iBMC hardware and the server management page cannot be logged in. In this case, you need to replace the iBMC hardware. |
|||
5 |
Installing/Removing a server in/from a cabinet |
Perform this operation in strict accordance with the service and maintenance guide to avoid hardware damage and personnel injury. |
No. |
Operation |
Operation Entry |
Impact |
Risk Level |
Workaround |
Operation Requirements in Production Environment |
Operation Requirements in Test Environment |
|---|---|---|---|---|---|---|---|
1 |
Running the service network restart command during the normal operation of the system |
Log in to the host and run the service network restart command. |
The host, service provisioning, and VM startup may fail. |
Critical |
None |
|
This operation must be performed by maintenance personnel or with their consent. |
2 |
Running the ping -I command on the host to specify a network adapter |
Log in to the host and run the ping -I command. |
Host network communication may be interrupted. Running the ping command to check the network is recommended. |
||||
3 |
Manually deleting or modifying the message log files |
Log in to the host and run the rm command to delete message logs from /var/log. |
Logs cannot be displayed. |
||||
4 |
Clearing the user-defined information in the BIOS flash memory |
Log in to the iBMC CLI and run the ipmcset -d clearcmos command. |
Deleted information cannot be recovered. |
||||
5 |
Restoring the iBMC factory settings |
Log in to the iBMC CLI and run the ipmcset -d restore command. |
User data cannot be recovered once factory settings are restored. |
||||
6 |
Changing the IP address of a server |
Log in to the host and run the ifconfig command to change the IP address. |
This operation may affect service processes on the host and current service operations. |
||||
7 |
Running the rm -rf command to delete files |
Log in to the host and delete files on the host or files required by the commercial release package. |
This operation may affect service processes on the host and the video stream cloud phone service. |