- SDS BareMetal to Cloud Migration Guide
- Migration
- Reuse of the Existing Hardware and Existing IP Addresses
- Shutting Down 20% of DP Server
4.1.9 Shutting Down 20% of DP Server
Perform the following procedure to shutdown 20% of DP
Server.
- Remove DP from topology.
- Login to Active NOAM SDS GUI.
- Navigate to Status & Manage from Main Menu, then select HA.
- To change HA state of DP to Out of Service (OOS), perform
the following steps:
- To change DP HA state to OOS, perform the following
steps:
- Navigate to Status & Manage from Main Menu, then select HA.
- Click Edit and change Max Allowed HA Role of DP to OOS.
- To remove the DP from DP Server group, perform the
following steps:
- Navigate to Configuration from Main Menu, then select Server Groups.
- Select DP (Level C) Server Group and click Edit.
- Uncheck DP from Server Group and click OK.
- Navigate to Configuration from Main Menu, then select Servers and select DP. Click Delete.
- To change DP HA state to OOS, perform the following
steps:
- Shutdown DP by running the following command:
sudo shutdown -h now
- Install OL8 and KVM on the shutdown BM server.
- Create vSDS 9.0.X.
Note:
Create DP on the same host where NOAM, SOAM VM was created. - Assign XMI IP to new vSDS 9.0.X.To configure netmask and XMI IP address values, run the following command:
sudo /usr/TKLC/plat/bin/netAdm set --onboot=yes --netmask=<netmask> --device=eth0 --address=<IP address>
- Login to SDS Active vSDS 9.0.1 NOAM using XMI.
- Navigate to Configuration from Main Menu, then select Servers.
- Click Insert.
- Add the following details for DP server:
- Enter DP hostname
- Update Role as MP
- Hardware Profile as SDS Cloud Guest
- Configure XMI and IMI, XSI IP's and NTP server IP
- Click Ok.
- Select the required DP server (which was created in the previous step).
- Click Export, to export server configuration file to the file management folder on the Active NOAM.
- Now ssh to Active SDS 9.0.X NOAM and copy the
TKLCConfigData.<hostname>.sh
file to the newly created vSDS 9.0.X DP. After copying the file wait for 5 minutes.cd $FILE_MGMT_AREA
sudo scp TKLCConfigData.<hostname>.sh admusr@<XMI IP of newly created vSDS 9.0.X DP>:/var/tmp/TKLCConfigData.sh
- SSH to newly created vSDS 9.0.X DP XMI IP and verify the
/var/TKLC/appw/logs/Process/install.log
log file for successfully running ofTKLCConfigData.sh
file. You can run following command to check logs.sudo tail -f /var/TKLC/appw/logs/Process/install.log
Output:+ sed -i s/WALLET_KEY_TO_BE_REPLACED_DURING_SERVER_EXPORT/bc332acff044aa6bcc7871c0742b0b89abd658efc23549acc70d857279a1ee3bb31e04f2e85fcc50fe2fad0c6aa69d3596ecb68f84983b44d7805d98a994ad96/g/usr/TKLC/appworks/prod/maint/loaders/install/postInstall/load.AppworksSecConfig + /usr/sbin/chpasswd ++ aw.wallet credential get tpdProvd tpdProvd + /usr/TKLC/appworks/sbin/updateMylogincnf Imysql: [Warning] Using a password on the command line interface can be insecure. Imysql: [Warning] Using a password on the command line interface can be insecure. + pm.kill apwSoapServer cmsoapa + /bin/touch /var/TKLC/appw/TKLCinitcfg + /bin/sleep 1 [SUCCESS] script completed successfully!
- Wait for 10 minutes for server to configure with the IP configuration, then
reboot the VM using
sudo init 6
command on CLI. - Login to Active vSDS NOAM GUI.
- Navigate to Configuration from Main Menu, then select Server Groups.
- Select the DP (Level C) Server group and click Edit.
- Select the newly added vSDS 9.0.X DP to add to the DP Server group, then click Ok to save the changes and wait for 5 minutes.
- If the Max Allowed HA Role of new 9.0.X vSDS DP is not Active then navigate to Status & Manage from Main Menu, then select HA and change Max Allowed HA Role of that server to Active by clicking Edit.
- SSH to new vSDS 9.0.X DP.
- Run the following commands to disable the upgrade barrier feature:
iset -fvalue=1 IdbParamDef where "param='IdbDisableUpgBarrier'" sudo init 6
- Login to Active vSDS NOAM GUI.
- Navigate to Status & Manage from Main
Menu, then select Server and select the
newly added vSDS 9.0.X DP. Click Restart.
Note:
- To configure remaining DPs, repeat procedure Shutting Down 20% of DP Server for each 20% of DP until you reach 100% of DP server.
- DP leader must be migrated last.