- Subscriber Data Server Cloud Installation Guide
- Configuration Procedures
- OAM Installation for DP-SOAM Sites (All DP-SOAM Sites)
3.6 OAM Installation for DP-SOAM Sites (All DP-SOAM Sites)
- Ensure the DP-SOAM Network Element XML file for the DP-SOAM site is created as described in Creating an XML file for Installing SDS Network Elements.
- All the Network Element XML files are on the laptop’s hard drive.
- To launch a web browser, in Active SDS VIP, connect to the XMI virtual
IP address assigned to active SDS site using https://xx.xxx.xx.xxx/If the Security Certificate Warning screen displays, click Continue to this website (not recommended).
- To login to Active SDS VIP, establish a GUI session as the
guiadmin user on the NOAM-A server.
- To configure the DP SOAM network element, in Active SDS VIP, perform the
following steps:
- Navigate to Configuration, select
Networking and click
Networks.
- Click Browse and enter the pathname
of the NOAM network XML file.
Note:
This step assumes that the XML files were previously prepared as described in Creating an XML file for Installing SDS Network Elements. - Select the location of the XML file and click
Open.
- Click Upload File to upload the XML
file.
If the values in the XML file pass and the upload is successful, an information banner displays.Note:
Left-click mouse on the Info banner to display the banner.
- Navigate to Configuration, select
Networking and click
Networks.
- To configure the SOAM server, in Active SDS VIP, perform the following
steps:
- Navigate to Configuration, and
select Servers.
- Click Insert to insert the new SOAM
server into server’s table.
- Fill in the fields as follows:
- Hostname: Assigned Hostname
- Role: SYSTEM OAM
- System ID: Assigned Hostname
- Hardware Profile: SDS Cloud Guest
- Network Element Name: [Select NE from list]
- Location: Optional
- Navigate to Configuration, and
select Servers.
- The network interface fields are now available with selection choices based on
the chosen hardware profile and the network element. To insert the network
element in Active SDS VIP, perform the following steps:The network interface fields are now available with selection choices based on the chosen hardware profile and network element.
- Enter the server IP addresses for the XMI network, select ethX for the interface, and retain the VLAN checkbox unchecked.
- Enter the server IP addresses for the IMI network, select
ethX for the interface, and retain the VLAN checkbox
unchecked.
Note:
For OpenStack, use the IP addresses used during instance booting and network. - Add the following NTP servers:
NTP Server Preferred? Valid NTP Server Yes Valid NTP Server (Optional) No Valid NTP Server (Optional) No - Optionally, mark the Prefer checkbox to prefer one server over the other.
- Click OK, once all the server data is entered.
- To export the initial configuration, in Active SDS VIP, perform the
following steps:
- Navigate to Configuration, and then
select Servers.
- From the GUI screen, select the SDS server.
- Click Export, to generate the initial configuration data for that server.
- Navigate to the Info tab to confirm
the file has been created.
- Navigate to Configuration, and then
select Servers.
- To copy server configuration file to
/var/tmp
directory, in Active SDS VIP, perform the following steps:- Obtain a terminal window to the SDS NOAM-A server, loggin as the admusr user.
- Copy the configuration file created in the previous step
from the
/var/TKLC/db/filemgmt
directory on the SDS NOAM-A to the/var/tmp
directory. The configuration file has a filename likeTKLCConfigData.<hostname>.sh
.For example:$ cp /var/TKLC/db/filemgmt/TKLCConfigData.<NOAM-A_hostname>.sh /var/tmp/TKLCConfigData.sh
Note:
The server polls the/var/tmp
directory for the configuration file and automatically runs it.For the NOAM-B server, the command is:$ scp \ /var/TKLC/db/filemgmt/TKLCConfigData.<NOAM-B_hostname>.sh \ <NOAM-B_ipaddr>:/var/tmp/TKLCConfigData.sh
Note:
The IPADDR is the IP address of NOAM-B associated with the XMI network.Wait for configuration to complete.
The automatic configuration daemon looks for the file named
TKLCConfigData.sh
in the/var/tmp
directory, implements the configuration in the file, and prompts the user to reboot the server.A broadcast message is sent to the terminal. This process can take between 3 to 20 minutes to complete.
If you are on the console, wait to be prompted to reboot the server. Do not reboot the server. It is rebooted later in this procedure.
- Verify if the script is completed successfully, in SDS SOAM Server, by
checking the following file:
$ sudo cat /var/TKLC/appw/logs/Process/install.log
Note:
Ignore the warning about removing the USB key since no USB key is present. No response occurs until the reboot prompt is issued. - Optionally, to set the time zone and reboot the server, in SDS SOAM
Server, perform the following steps:
- To change the system time zone, from the command line prompt, run
set_ini_tz.pl
. The following command example uses the America/New_York time zone.$ sudo /usr/TKLC/appworks/bin/set_ini_tz.pl "America/New_York" >/dev/null 2>&1 $ sudo init 6
- Replace, as appropriate, with the time zone selected for this installation. See List of Frequently Used Time Zones for a complete list of valid time zones.
Wait for server to reboot.
- To change the system time zone, from the command line prompt, run
- To verify server health, in SDS NOAM-A, perform the following
steps:
- Log into the NOAM1 as the admusr user.
- Run the following command on the first NOAM server and
ensure no errors are
returned:
$ 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
- To configure DR SDS NOAM-B, repeat the above steps from Step 4 to Step 10 of this procedure on SDS NOAM-B.