I Change SOAM VM Profile for Increased MP Capacity on a VMware system

This procedure describes how to change the SOAM VM profile on a VMware system.

Log in to Active NOAM

1. Log in to the Active NOAM GUI using the VIP.
2. Navigate to Main Menu, then Status & Manage, and then HA.
3. Confirm that at least one SOAM has OAM HA Role of Active.
4. Identify the Active and Standby SOAM server based upon the OAM HA Role column.

Check System Alarms

1. Navigate to Main Menu, then Alarms & Events , and then View Active.
2. Confirm that there are no alarms related to Replication, Merging, system health, or SOAMs.
3. In case of any alarms, stop the activity, identify the cause of alarms, and resolve them, and then continue to the next steps when the alarms are cleared.

Take Standby SOAM Out of Service in HA

1. Navigate to Main Menu, then Status & Manage, and then HA.
2. Press the Edit button in lower-left corner of the page.
3. Take the SOAM identified as Standby in Step 1 to Max Allowed HA Role of OOS.
4. Click OK.

   Information displays information banner Pre-Validation passed-Data Not Committed.

5. Press OK.

   The system goes back to the previous screen with the Standby SOAM now Showing OOS in Max Allowed HA Role and OAM HA Role. At this point, the server is ready to be turned off for any change.

Stop/Shut Down the VM

1. Log in to Command Line Interface of the SOAM taken out of service.
2. Run the sudo init 0 command.

Modify the vCPU and Memory

1. Confirm that the virtual machine is powered off.
2. Click the virtual machine.
3. Go to Settings.
4. Edit System Settings to change:

   vCPU: 8

   RAM/Base Memory: 14,336 (14GB, 14 x 1024)

   Note:

   The exact steps may be different depending on the VM Manager. Contact your VM Manager for any help on the exact steps.

Start the VM

1. Set Power State of VM to Power ON in the VM Manager and wait for a few minutes.

Log in to SOAM using CLI

1. Use the SSH command to log in to the respective SOAM identified.

   ssh admusr@<SERVER_XMI>

   password: <enter password>

2. Answer yes when prompted to confirm the identity of the server.

Confirm that the SOAM is Sowing 8 vCPU

1. On the SOAM CLI, run the mpstat -P ALL command.

   The output should be one line for each vCPU. Confirm that for vCPU=8, the output shows 8 lines.

Check Memory (RAM) Size is 14 GB

1. On the SOAM CLI, run the following command:

   cat /proc/meminfo

   vmstat -s

   Sample output:

   admusr@labNOAM ini]$ cat /proc/meminfo

   MemTotal: 14007172 kB

   [admusr@labNOAM ini]$ vmstat -s

   14007172 total memory

Increase Measurement Memory and Queue Size

1. Run the following command:

   sudo sh /usr/TKLC/dsr/prod/maint/loaders/install/load.AppwMeasMem

2. Verify if the MeasMem.inifile is created for measurement memory size of 3072 MB:

   cat /var/TKLC/appworks/ini/MeasMem.ini

   Note:

   INI entry should be aw.measure.maxmem = 3072.
3. Verify that the measurement queue size is set to 2 in LongParam table where the parameter name "measurementMaxQueues" is 2:

   iqt -pE LongParam | grep measurementMaxQueues

Bring Back SOAM in to Service

1. Log in to the Active NOAM GUI using the VIP.
2. Navigate to Main Menu, then Status & Manage , and then HA.
3. Press Edit in the lower-left corner of the page.
4. Take the modified SOAM to Max Allowed HA Role of ACTIVE.
5. Press OK.

   Information displays information banner Pre-Validation passed-Data Not Committed.

6. Press OK.

   The system goes back to the previous screen with the Standby SOAM now showing Active in Max Allowed HA Role.

7. Wait for the time till this SOAM shows Standby in the OAM HA Role.

   At this point, the server is back to the normal operating status.

Take Active SOAM Out of Service in HA

1. Navigate to Main Menu, then Status & Manage, and then HA.
2. Press Edit in the lower-left corner of the page.
3. Take the SOAM identified as Active in Step 1 to Max Allowed HA Role of OOS.
4. Press OK.

   Information displays the information banner Pre-Validation passed-Dat Not Committed.

5. Press OK.

   The system goes back to the previous screen with the Active SOAM showing OOS in Max Allowed HA Role and OAM HA Role.

6. Confirm that the SOAM that was Standby earlier is now Active in Max Allowed HA Role and OAM HA Role.

   At this point, the server is ready to be turned off for any change.

   Note:

   Repeat all the tasks from Stop/Shut down the VM to Bring Back SOAM into service.