- SDS BareMetal to Cloud Migration Guide
- Migration
- Reuse of the Existing Hardware and Existing IP Addresses
- Configuring Network Element
4.1.4 Configuring Network Element
Perform the following procedure to configuring network
element:
- Log in to SDS 8.6.x Active NOAM GUI using VIP.
- Export the network element configurations.
- Navigate to Configuration from Main Menu, then select Networking and click Networks.
- Select the required NOAM Network Element for configuration.
- Click Export and save the configuration.
- Log in to newly created 9.0.X vSDS GUI using XMI IP.
- Configure Network Element for NOAM server on the vSDS 9.0.1.
- Navigate to Configuration from Main Menu, then select Networking and click Networks.
- Click Browse and select the file exported from the SDS 8.6.X server, to import the Network element configuration.
- Click Upload File.
- Configure server details on vSDS 9.0.1.
- Log in to newly created vSDS 9.0.X GUI using XMI IP.
- Navigate to Configuration from Main Menu, then select Servers.
- Click Insert.
- On Insert page, update the following
server details:
- Enter the standby NOAM hostname
- Role as Network OAM&P
- Hardware Profile as SDS Cloud guest
- Select the Noam Network element name
- Configure XMI and IMI IP's and NTP server IP
- Click Ok.
- Export and run
TKLCConfigData.sh
file on vSDS 9.0.1 NOAM.- Log in to NOAM vSDS 9.0.X GUI using XMI IP.
- Navigate to Configuration from Main Menu, then select Servers.
- Select the required NOAM server, which was added in the previous step.
- Click Export, to export server configuration file to the file management folder on the NOAM.
- Perform
ssh
to XMI IP of the newly created vSDS 9.0.X VM. - Run the
cd $FILE_MGMT_AREA/
command to access the file management area. - Copy the
TKLCConfigData.sh
file to/var/tmp
folder, by running the following command:cp TKLCConfigData.<hostname>.sh /var/tmp/TKLCConfigData.sh
- 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! '
- Use following command to update the
/etc/resolv.conf
file:sudo vim /etc/resolv.conf
- Add IMI IP of the Active 8.6.X SDS NOAM at the
end of file. Select Save and then click
Close.
Sample
/etc/resolv.conf
file:[admusr@901noam00 ~]$ cat /etc/resolv.conf domain platform.cgbu.us.oracle.com nameserver 127.0.0.1 nameserver 192.168.0.20 ; IMI IP of NOAM
- Copy the
/var/named/db.platform.cgbu.us.oracle.com
from Active NOAM to Standby NOAM, by running the following commands on SDS 9.0.1 VM.cd $FILE_MGMT_AREA/
sudo ssh admusr@<XMI ip of Active 8.6.X SDS NOAM> "sudo cat /var/named/db.platform.cgbu.us.oracle.com " > db.platform.cgbu.us.oracle.com
sudo mv db.platform.cgbu.us.oracle.com /var/named/
sudo chown root:named /var/named/db.platform.cgbu.us.oracle.com
sudo chmod 640 /var/named/db.platform.cgbu.us.oracle.com
- Wait for 10 minutes for server to configure with the IP configuration, then
reboot the VM using
sudo init 6
command on CLI.