Performance Intelligence Center (PIC) - User Password Reset & New User Creation Does Not Work and NSP Access Unstable

Asset ID:	1-72-2106041.1
Update Date:	2016-03-31
Keywords:

Solution Type Problem Resolution Sure

Solution 2106041.1 : Performance Intelligence Center (PIC) - User Password Reset & New User Creation Does Not Work and NSP Access Unstable

Applies to:

Oracle Communications Performance Intelligence Center (PIC) Software - Version 9.0.4 and later
Information in this document applies to any platform.

Symptoms

No possibility to create new users from "Security" Configuration application or to change users' passwords. On other hand, the NSP is unstable and there are frequent issues to access it or to use various applications.

Check in Weblogic Console, whether there are a lot of SNMP alarms in the JMS queue (all servers) for "Message Current". It can be blocked to 50000.

On other hand, verify the following alarm in the nspadmin log:

#### <ExecuteThread: '2' for queue: 'weblogic.socket.Muxer'> <> <> <> 4.137.76,port=7001,localport=28267]
weblogic.socket.MaxMessageSizeExceededException: Incoming message of size: '10000080' bytes exceeds the configured maximum of: '10000000' bytes for protocol: 't3'.
weblogic.socket.MaxMessageSizeExceededException: Incoming message of size: '10000080' bytes exceeds the configured maximum of: '10000000' bytes for protocol: 't3'
at weblogic.socket.BaseAbstractMuxableSocket.incrementBufferOffset(BaseAbstractMuxableSocket.java:174)

Cause

The alarms flow might be not well managed by JMS Queues on Weblogic and this causes various instability at Weblogic level.

Check on platcfg whether there is an SNMP destination configured on NSP side (placfg menu: NSP Configuration --> SNMP Agent Configuration).

Simultaneously, all instances (nsp1a, 1b and nspadmin) must be set to manage up to 20 millions bytes. In case of different values in various instances, it may occur issues in alarms management.

Solution

For SNMP alarms management, open an ssh connection on NSP server. Open "platcfg" and configure the NSP by defining in "SNMP Agent Configuration" the destination server for SNMP traps. NSP server can be itself the destination in case of no dedicated server on customer side.

For the error in nspadmin log about message size issue, open the Weblogic Console (Web GUI) and set a correct value for "Maximum Message Size":

Open WebLogic Administration Console (GUI)
Click on Lock & Edit
Go to Servers -> {server-name} -> Protocols -> General
Set a bigger value for Maximum Message Size (e.g. set it as 20000000 bytes)
Click on "Save and Activate Changes"

Repeat this procedure on all servers (including the admin server) by setting the same value.

It is useless to restart the NSP.

System should be kept under surveillance for several days to verify the NSP stability.

Attachments

This solution has no attachment