A.15 Workaround to Fix cmsoapa Restart

When the upgrade path is from 7.x, 8.0 to 8.1, the cmsoapa process continuously restarts on the lower-level node after the higher-level node has been upgraded, that is, on SOAM after NOAM was upgraded and on DP server after SOAM has been upgraded.

1. Log in to the NOAM VIP GUI. If not already done, establish a GUI session on the NOAM server the VIP IP address of the NOAM server. Open the web browser and enter a URL of:
   http://<Primary_NOAM_VIP_IP_Address>
2. Log into the NOAM GUI as the guiadmin user.

   Figure A-119 NOAM VIP GUI Log in

   
   

   

   
   
3. In the NOAM VIP GUI, identify the servers with the 31201 alarm for the cmsoapa process not running.
   1. Navigate to current alarm details and identify the server on which 31201 - Process Not Running alarm is getting raised for Instance as cmsoapa.
   2. Expand Alarms & Events click View Active.
   3. Look for "31201" alarm instances and make a list of servers with the cmsoapa alarm instance.
4. Login into Server using CLI on which cmsoapa is restarting. Use the SSH command (on UNIX systems – or putty if running on windows) to log into the server identified.

   ssh admusr@<SERVER_XMI>
   password: <enter password>

   Answer yes if you are asked to confirm the identity of the server.

5. In the server CLI, run the workaround.
   1. Enter the command $ sudo prod.dbdown.
   2. After few minutes, when processes are down. Run prod.start. Enter the command $ sudo prod.start.
   3. Repeat the steps on all server(s) where the alarm is, that is, where the cmsoapa process is restarting.