A
server should not be rebooted until you have assessed the full impact on the system. This list describes what happens when
servers of different roles are rebooted:
- OAM Server controlling GUI session: Reboot of OAM Servers ends all GUI sessions controlled by that server. Note that the reboot may reboot the server controlling your GUI session. After the reboot sequence completes, you can re-establish a GUI session with the rebooted server. You are presented with a login screen and need to re-authenticate to create a new session.
- Active OAM Server: Stopping and starting application software may cause a switchover. You have different capabilities on Active vs. Standby OAM servers, depending on the feature. For example, provisioning is only allowed from the Active NOAMP server.
- Other Servers: Rebooting Message Processing servers and Standby OAM servers without GUI sessions has no direct GUI impact. You can observe changes in the status of these servers. A BR tag was used here in the original source.
Caution:
Do not click
Reboot for a
server until you have assessed the impact on the system.
Reboot temporarily halts all services on the designated
server; do not perform a Reboot unless other
servers within the network element can take over the traffic load.
Use this procedure to reboot a server:
