Restarting the application

If the Application State displays Disabled, Restart starts the software. If the Application State displays Enabled, Restart stops and then starts the software. Restarting the software places it in the enabled state.

A Restart can be used:

• To restart a newly created server, which has software in the disabled state.
• When a server is removed and re-added to topology and has software in the disabled state.

GUI sessions are not affected by the restart application software action. You may continue to use the GUI as these actions progress. You may use GUI sessions connected to servers with application software being restarted. GUI provisioning may be affected if the server is the active NOAMP server. Stopping and starting application software may cause a switchover as well; you can observe changes in the status of these servers from the Server Status page.

Caution:

Do not click Restart for an application until you have assessed the impact on the system. Restarting the application on a server can adversely affect processes on this server and/or other servers in the network element.

Use this procedure to restart the application on a server:

1. Click Status & Manage > Server.
   The Server Status page appears.
2. Click to select the server you want to restart.
   Alternately, you can select multiple servers to restart. To select multiple rows, press and hold Ctrl as you click to select specific rows.
3. Click Restart
   A warning message appears:

   Are you sure you wish to restart application software on the following server(s)? <server name>

4. Click OK to continue.

Application processes are restarted on this server. Restarting running software influences the High Availability subsystem by raising an alarm. If the software is running when the Restart is selected, the stopping of the software affects server processing in the following ways:

• Servers continue to emit alarms and collect measurements.
• NOAMP and SOAM servers continue to publish replicated data and accept GUI connections.
• SOAM and Message processing servers continue to subscribe to replicated data.
• NOAMP servers do not accept provisioning/configuration changes.
• Message Processing servers do not maintain signaling connections nor process messages.