Oracle Communications Diameter Signaling Router (DSR)
 

PLA-Support>Sun Systems>CommsGBU>Global Signaling Solutions>SN-SND: Tekelec DSR
 

In this Document

Symptoms

Changes

Cause

Solution

References

Created from <SR 3-12650945097>

Applies to:

Symptoms

awpushcfg script fails showing following on the target server:

Error:

Changes

Customer was upgrading Gen6 to Gen8 hardware

Cause

This is related to Bug 23243569 - The bug will address the fact that when the ‘Export’ button is clicked (Configuration -> Servers GUI screen), an alias device (e.g. bond0.7:1) can be added before the actual device (e.g. bond0.7). This is what is causing the ‘awpushcfg’ script to fail.

The ‘Export’ button calls for a AppWorks to create a server’s configuration file (i.e. TKLCConfigData..sh). This file is used by the 'awpushcfg' script to configure the server. The bug will analyze and put a check in place to make sure that the 'TKLCConfigData.sh' file is created with the correct sequence.

Solution

 Following workaround can be applied on active NOAM VIP:

1.  Export the Server Configuration file.
   
   1. Configuration -> Servers
   2. Click on 'Export'
2.  Download the Server Configuration file
   1. Status & Manage -> Files
   2. Click on the active NOAM Tab
   3. Highlight the Server Configuration file
   4. Click on 'Download'
   5. Save the ‘TKLCConfigData.<hostname>.sh’ locally to your PC/Laptop.
3.  Inspect the ‘TKLCConfigData.<hostname>.sh’ file from your PC/Laptop
   1. Make sure all the devices (e.g. bond0.7, bond0.5, etc… ) are added before the alias device (e.g. bond0.7:1, bond0.5:1, etc…).
   2. If you see that any alias device is being added before the actual device, then go to step #4.
   3. If you see that the actual device being added before the alias device, then there’s not need to make any changes, and this procedure is complete.
4.  Edit and Apply all alias devices which are being added before the actual device.
   1. From the Blade/Server being replaced CLI as admusr, check for the following file:
      $ sudo ls -l /var/TKLC/appw/TKLCinitcfg
   2. If present, then continue to move the file. If the file is not present, skip the ‘$ sudo mv’ commands that follow.
   3. From the Blade/Server being replaced CLI, as admusr:
      $ sudo mv /var/TKLC/appw/TKLCinitcfg /var/TKLC/appw/TKLCinitcfgHold
   4. Configuration -> Network -> Devices
   5. Select the TAB for the server being configured
   6. Highlight the alias device (e.g. bond0.7:1)
   7. Click on Edit
   8. From the edit screen, do not make any changes, just click on ‘Apply’
   9. From the Blade/Server being replaced CLI, as admusr:
      $ sudo mv /var/TKLC/appw/TKLCinitcfgHold /var/TKLC/appw/TKLCinitcfg
   10. If this step fails, then proceed to step #6 below.
5.  Execute steps 1 through 3 to export, download, and inspect the new file.
   
   1. ‘TKLCConfigData.<hostname>.sh’ file, if OK, then continue with the ‘awpushcfg’ script. If the server configuration file did not change, then proceed to step #6 below
6.  If Step #4 above fails to change the order in which the devices are configured, then login to the active NOAM (as ‘admusr’) and manually edit the server config file.
   1. Change directory
      $ cd /var/TKLC/db/filemgmt
   2. List files:
      $ ls –l
   3. The sever config file should have the properties: rw-rw-rw- 1 root root 8.4K Month date time TKLCConfigData.<hostname>.sh
   4. Edit file:
      $ vi TKLCConfigData.<hostname>.sh
   5. Once in edit mode, edit the file so that the actual devices (e.g. bond0.7) are added before the alias devices (e.g. bond0.7:1)
   6. Once edited, save the file.
   7. List files:
      $ ls –l (to confirm the file properties)
   8. Continue with the ‘awpushcfg’ script.

References

This solution has no attachment