Recreate the SDS SOAM VM with the 1B Subscriber Profile

Log into the Platform Management and Configuration application, open an approved Web browser (Internet Explorer 8.0, 9.0, or 10.0) and connect to the management IP address assigned to the PMAC server associated with the SDS SOAM NE. If a certificate error is received, click on the Continue to this website (not recommended) link.

Figure 49-21 Website Security

Log in to the PMAC server using the default user name and password.

Figure 49-22 PMAC Server Login

In the PMAC Server GUI, access VM Management screen. Navigate to VM Management.

Figure 49-23 VM Management

In the PMAC Server GUI, select the 1B subscriber profile. In the VM Entities box, click the plus sign (+) to expand the folder for the OAM blade containing the SOAM VM to be converted to the 1B Subscriber profile. Click on the SOAM VM to be converted to the 1B Subscriber profile.

Figure 49-24 Virtual Machine Management

Note:

Verify the correct SDS SOAM VM is selected since the next step deletes the VM from the OAM blade. It is imperative that only the SDS SOAM VM removed from the server group (Remove the SDS SOAM VM from the SOAM Server Group) is selected for deletion.

In the PMAC Server GUI, delete the VM. Click Delete.

Figure 49-25 Delete

Click OK to confirm.

Figure 49-26 OK

Wait for the Delete Guest succeeded confirmation banner (up to a minute).

Figure 49-27 Delete Successful Message

In the PMAC Server GUI, create the profile on the server. Select the OAM blade containing the SOAM VM to be converted to the 1B Subscriber profile. Click Create Guest.

Figure 49-28 Create Guest

Click Import Profile.

Figure 49-29 Import Profile

In the PMAC Server GUI, select the ISO/Profile value. Select the ISO/Profile option that matches the hardware your SOAM VM TVOE server is running.

Figure 49-30 ISO/Profile

Click Select Profile.

Figure 49-31 Select Profile

In the PMAC Server GUI, create VM host. Type the server host Name (for example, so-mrsvnc-a). Click Create

Figure 49-32 Create Guest

Note:

If the VM guest creation fails due to a Host resources are oversubscribed error, contact My Oracle Support. Verify the task successfully completes by watching the Progress value change to 100%.

In the PMAC Server GUI, install the operating system. Click Install OS.

Figure 49-33 Install OS

In the PMAC Server GUI, start the installation of the TPD image. Select the TPD image and click Start Install.

Figure 49-34 Start Install

Click OK to confirm.

Figure 49-35 OK

Monitor the installation task by navigating to Task Monitoring. It should take about 11 minutes until you see the Progress value change to 100%.

Figure 49-36 Task Monitoring

In the PMAC Server GUI, verify installation. Navigate to VM Management. From the Tasks tab, verify the operating system has been installed. The Application Details section is blank.

Figure 49-37 Application Details

In the PMAC Server GUI, upgrade the network. From the Network tab, record the control IP address for this SOAM VM (to be used later). Click Upgrade.

Figure 49-38 Upgrade

In the PMAC Server GUI, start the software upgrade. Select the SDS version from the Image Name column and click Start Software Upgrade.

Figure 49-39 Select Image

Start Software Upgrade, click OK to confirm.

Figure 49-40 Software Upgrade

Figure 49-41 OK

Navigate to Task Monitoring to monitor the upgrade.

Figure 49-42 Task Monitoring

In the Primary SDS VIP, export the recreated SOAM server. Expand Configuration click Servers.

Figure 49-43 Servers

Select the recreated SOAM server from the list.

Figure 49-44 SOAM Server List

Click Export.

Figure 49-45 Export

In the SDS VIP CLI, access the active NOAM server CLI. Connect to the active SDS NOAM CLI using SSH terminal session to the NOAM VIP address.

Log into the server as the admusr user.

login: admusr

Password: <admusr_password>

Change directory into the file management location.

$ cd /var/TKLC/db/filemgmt

Get a directory listing and find the configuration file containing the SOAM server name.

$ ls –ltr TKLCConfigData*.sh

*** TRUNCATED OUTPUT ***

-rw-rw-rw- 1 root root 2208 Dec 19 16:50

TKLCConfigData.so-carync-b.sh

Copy the configuration files found in the previous step to the PMAC.

$ scp -p <configuration_file> admusr@<PMAC_Mgmt_IP>:/tmp/

admusr@xxx.xxx.xxx.xxx's password: <admusr_password>

TKLCConfigData.so-carync-b.sh 100% 1741 1.7KB/s 00:00

In the SDS VIP CLI, log out of the active NOAM CLI.

$ exit

In the PMAC Server CLI, use SSH to log into the PMAC guest VM server as the admusr user.

login: admusr

Password: <admusr_password>

In the PMAC Guest VM, copy the server configuration file to the control IP for the SDS SOAM VM.

$ scp -p /tmp/<configuration_file>

admusr@<SDS_SOAM_VM_Control_IP>:/tmp/

admusr@xxx.xxx.xxx.xxx's password:

TKLCConfigData.so-carync-a.sh 100% 1741 1.7KB/s 00:00

Note:

The control IP for each the SOAM VM was recorded in step 17 of this procedure.

Connect to the SOAM server CLI from the PMAC server console.

$ ssh <SDS_SOAM_VM_Control_IP>

admusr@xxx.xxx.xxx.xxx's password: <admusr_password>

In the SOAM Guest VM, copy the configuration file. Copy the server configuration file to the /var/tmp directory on the server, making sure to rename the file by omitting the server host name from the file name.

Example: TKLCConfigData.<server_hostname>.sh translates to TKLCConfigData.sh

$ cp –p /tmp/TKLCConfigData.so-carync-b.sh

/var/tmp/TKLCConfigData.sh

Note:

The server polls the /var/tmp directory for the presence of the configuration file and automatically executes it when found.

Monitor for broadcast message sent to the terminal

Note:

The time to complete this step varies by server and may take from 3‑5 minutes to complete.

*** NO OUTPUT FOR ≈ 3-5 MINUTES ***
Broadcast message from root (Mon Dec 14 15:47:33 2009):
Server configuration completed successfully!
See /var/TKLC/appw/logs/Process/install.log for details.
Remove the USB flash drive if connected and reboot the server.
<ENTER>

Accept upgrade to the application software.

$ sudo /var/TKLC/backout/accept
Called with options: --accept
Loading Upgrade::Backout::RPM
Accepting Upgrade
Setting POST_UPGRADE_ACTION to ACCEPT in upgrade info.
Cleaning backout directory.
Clearing Upgrade Accept/Reject alarm.
Cleaning message from MOTD.
Cleaning up RPM config backup files...
Checking /
Checking /boot
Checking /tmp
Checking /usr
Checking /var
Checking /var/TKLC
Checking /tmp/appworks_temp
Checking /var/TKLC/appw/logs/Process
Checking /var/TKLC/appw/logs/Security
Checking /var/TKLC/db/filemgmt
Checking /var/TKLC/rundb
Starting cleanup of RCS repository.
 INFO: Removing '/var/lib/prelink/force' from RCS repository
 INFO: Removing '/etc/my.cnf' from RCS repository

Verify the desired time zone is currently in use.

$ date

Mon Aug 10 19:34:51 UTC 2015

Configure the time zone (optional).

$ sudo set_ini_tz.pl <time_zone>

Note:

The following command example sets the time to the UTC (aka GMT) time zone, which is recommended for all sites. Replace, as appropriate, with the customer requested time zone for this site installation. See Add the SDS ISO to the PMAC Software Repository for a list of valid time zones.

$ sudo set_ini_tz.pl “Etc/UTC”

Reboot the SOAM server.

$ sudo init 6

Sample output:

Connection to xxx.xxx.xxx.xxx closed by remote host.
         Connection to xxx.xxx.xxx.xxx closed.

In the PMAC Guest VM, reboot the SOAM server console. Reboot and reconnect to the SOAM server console from the PMAC server console.

$ ssh <SDS_SOAM_VM_Control_IP>
         admusr@xxx.xxx.xxx.xxx's password: <admusr_password>

In the SOAM Guest VM, verify if the IMI and XMI addresses have been applied.

$ ifconfig |grep in
control  Link encap:Ethernet  HWaddr 52:54:00:23:DC:32
         inet addr:192.168.1.199  Bcast:192.168.1.255  Mask:255.255.255.0
imi      Link encap:Ethernet  HWaddr 52:54:00:33:DC:DC
         inet addr:10.240.38.78  Bcast:10.240.38.127  Mask:255.255.255.192
lo       Link encap:Local Loopback
         inet addr:127.0.0.1  Mask:255.0.0.0
xmi      Link encap:Ethernet  HWaddr 52:54:00:63:63:BD
         inet addr:10.240.39.150  Bcast:10.240.39.255  Mask:255.255.255.128

Check health of server, Syscheck the current health of the server.

$ sudo syscheck
Running modules in class hardware...
                                 OK
Running modules in class disk...
                                 OK
Running modules in class net...
                                 OK
Running modules in class system...
                                 OK
Running modules in class proc...
                                 OK
LOG LOCATION: /var/TKLC/log/syscheck/fail_log

Ping the XMI IP address, ping the IMI IP address of the mate SOAM VM Guest.

$ ping –c 5 10.240.38.78
PING 10.240.38.78 (10.240.38.78) 56(84) bytes of data.
64 bytes from 10.240.38.78: icmp_seq=1 ttl=64 time=0.031 ms
64 bytes from 10.240.38.78: icmp_seq=2 ttl=64 time=0.017 ms
64 bytes from 10.240.38.78: icmp_seq=3 ttl=64 time=0.031 ms
64 bytes from 10.240.38.78: icmp_seq=4 ttl=64 time=0.028 ms
64 bytes from 10.240.38.78: icmp_seq=5 ttl=64 time=0.030 ms
64 bytes from 10.240.38.78: icmp_seq=6 ttl=64 time=0.028 ms
--- 10.240.38.78 ping statistics ---
6 packets transmitted, 6 received, 0% packet loss, time 5000ms
rtt min/avg/max/mdev = 0.017/0.027/0.031/0.007 ms

From the SOAM Guest, ping the XMI IP address of the mate SOAM VM Guest.

$ ping –c 5 10.240.39.150
PING 10.240.39.150 (10.240.39.150) 56(84) bytes of data.
64 bytes from 10.240.39.150: icmp_seq=1 ttl=64 time=0.024 ms
64 bytes from 10.240.39.150: icmp_seq=2 ttl=64 time=0.033 ms
64 bytes from 10.240.39.150: icmp_seq=3 ttl=64 time=0.032 ms
64 bytes from 10.240.39.150: icmp_seq=4 ttl=64 time=0.026 ms
64 bytes from 10.240.39.150: icmp_seq=5 ttl=64 time=0.027 ms
64 bytes from 10.240.39.150: icmp_seq=6 ttl=64 time=0.026 ms
--- 10.240.39.150 ping statistics ---
6 packets transmitted, 6 received, 0% packet loss, time 5004ms
rtt min/avg/max/mdev = 0.024/0.028/0.033/0.003 ms

From the SOAM Guest, ping the local XMI gateway address associated with the SOAM NE.

$ ping –c 5 10.240.39.1
PING 10.240.39.1 (10.240.39.1) 56(84) bytes of data.
64 bytes from 10.240.39.1: icmp_seq=1 ttl=64 time=0.024 ms
64 bytes from 10.240.39.1: icmp_seq=2 ttl=64 time=0.033 ms
64 bytes from 10.240.39.1: icmp_seq=3 ttl=64 time=0.032 ms
64 bytes from 10.240.39.1: icmp_seq=4 ttl=64 time=0.026 ms
64 bytes from 10.240.39.1: icmp_seq=5 ttl=64 time=0.027 ms
64 bytes from 10.240.39.1: icmp_seq=6 ttl=64 time=0.026 ms
--- 10.240.39.1 ping statistics ---
6 packets transmitted, 6 received, 0% packet loss, time 5004ms
rtt min/avg/max/mdev = 0.024/0.028/0.033/0.003 ms

Verify server connectivity, use the ntpq command to verify the server has connectivity to at least one of the assigned NTP server(s).

Note:

NTP connectivity is denoted by the presence of an asterisk (*) to the left of one of the remote IP addresses.

$ ntpq -np
   remote         refid     st t when poll reach  delay  offset jitter
========================================================
+10.250.32.10  192.5.41.209  2 u  139 1024  377  2.008   1.006   1.049
*10.250.32.51  192.5.41.209  2 u  979 1024  377  0.507   1.664   0.702

Note:

If connectivity to the NTP server(s) cannot be established, stop and repeat the previous step until NTP connectivity is established before continuing to the next step.

Exit from the SOAM command line to return the PMAC server console prompt.

$ exit

Exit from the PMAC server.

$ exit