Oracle Communications Diameter Signaling Router (DSR)
 

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

PM&C (also called PMAC) Server Software Inventory screen does not populate details for all servers.

In this Document

Symptoms

Changes

Cause

Solution

Created from <SR 3-17251217957>

Applies to:

Symptoms

Platform Management & Configuration (PM&C) server GUI (Graphical User Interface) Software Inventory screen does not populate all server rows.  Often it may only show the PM&C server itself and TVOE host servers whereas some or all application servers (NOAM/SOAM/MP/IPFE/etc) fail to resolve hostname, IP address, and other information.  
Another symptom that may or may not be present is that 'snmpget' commands directed at the server using known SNMP Community String (CS) may fail, or may succeed only when using a previous Community String.

Changes

The SNMP Community String settings for some or all servers has been manually changed.

Cause

PM&C uses SNMP to get certain data from managed servers in order to assemble part of the Software Inventory screen. If the SNMP Community Strings do not match, parts of the screen may fail to populate correctly.

The CS settings for PM&C and all TVOE servers in the managed site are set using the PM&C GUI.
All application servers have their CS values set through the NOAM GUI.
[Individual servers can have their SNMP CS values changed individually using platcfg or other means, though after initial installation this method is not supported].

Despite warnings thrown when making changes at either location, it is possible for mismatches to arise among servers within a single DSR Site because the platform servers (PM&C and TVOE) have SNMP CS values changed through a different interface than the application servers.

Servers for DSR are initially [automatically] configured with known default values for the SNMP Community Strings when the software is first installed.  These default settings allow the server information to populate correctly in the PM&C Software Inventory screen even if the PM&C has had its own Community String values changed.  However if after the DSR application servers have their CS values changed from defaults to a value that does not match customized Community String values on the PM&C, the PM&C may not be able to successfully interrogate the servers when populating the Software Inventory screen (and certain other PM&C elements).  This mismatch is the cause of the observed condition.

[Note:  in some cases, values may visibly match but have not taken effect after a recent change; see Solution Addendum for steps to finalize the change].
 

Solution

The solution is to set the SNMP Community Strings for Read Only (RO) and Read/Write (RW) to uniform values for all platform and application servers in the site.
The procedures for setting the SNMP Community String values for both platform (through PM&C) servers and application (through active NOAM) servers can be found in the document "DSR Software Installation and Configuration Procedure 2/2" in the procedure entitled "Configure SNMP Trap Receiver(s)" [Procedure number changes depending on software release document set].   The document set is available on docs.oracle.com at the URL:

  https://docs.oracle.com/en/industries/communications/diameter-signaling-router/index.html

Addendum:

In some cases, after making changes to the SNMP Community String it may be necessary to perform Restart Sentry action on the PM&C server, and/or to restart the TKLCsnmp daemon on the target server or servers if PM&C Software Inventory screen still fails to resolve or user snmpget actions don't succeed with the new Community String.  Neither of these actions affects normal operation of the application servers.

To restart the PM&C sentry, (1) Log into the PM&C GUI, (2) Select Administration / PM&C Application (3) Select Restart Sentry from the pulldown menu and click Go to execute.

To restart the TKLCsnmp daemon on an individual server, (1) Log into the server as admusr, (2) execute--without quotes--the command "sudo initctl restart TKLCsnmp" (3) The TKLCsnmp service will restart; log out of the server.

This solution has no attachment