Honored Contributor.. connection Honored Contributor..
Honored Contributor..
262 views

NNMi not receving the alerts from RNNM

Hi Team,

 

We have Rnnm and Gnnm running, The alerts are not recevied by Gnnm becuase the load in DB, Tried the archiving and getting the below error, please help us to resovle the issue.error.JPGerror1.JPGerror2.JPGhelp.JPG

 

0 Likes
3 Replies
Highlighted
Vincent_M_NNM Acclaimed Contributor.
Acclaimed Contributor.

Re: NNMi not receving the alerts from RNNM

Hello Connection

Thanks for posting,

May I know if the cmd was executed as administrator? If not please open a cmd as administrator and execute the command as you did.

I tested in my local box the way you ran the trimincidents and it worked normally. If running the cmd as administrator the command fails, would like to recommend the following>

- Set the nnm logging level to FINEST: nnmsetlogginglevel.ovpl com.hp.ov.nms.events FINEST

- Trim the incidents using the command nnmtrimincidents.

- If the command fails collect: nnm-trace.log and pg_log files

- Set the nnm logging level to FINEST: nnmsetlogginglevel.ovpl com.hp.ov.nms.events INFO


Once you get those files, you can share them with me or open a support case.

Hope this helps,

Regards,



Vincent Montenegro Mena
Customer Support Engineer

If you find that this or any other post resolves your issue, please be sure to mark it as an accepted solution.
If you are satisfied with anyone’s response please remember to give them a KUDOS by clicking on the STAR at the bottom left of the post and show your appreciation.
0 Likes
Honored Contributor.. connection Honored Contributor..
Honored Contributor..

Re: NNMi not receving the alerts from RNNM

I have opened support case and the team is working and still not able to find out issue, it s been more than 3 days. 

0 Likes
AndyKemp Acclaimed Contributor.
Acclaimed Contributor.

Re: NNMi not receving the alerts from RNNM

I dont think there's going to be a way to resolve this issue without taking down the GNM for a little offline database maintenance as its transaction load is too high.

 

I'd recommend  halting the system or cluster,  clearing out the three evil cache file locations:

hornetq/paging

hornetq/journal

tx-object-store

bring up just the nmsdbmgr process and do an offline vaccum. with /opt/OV/nonOV/Postgres/bin/vacuumdb -d nnm -U postgres -z -f

after it completes you just stop the nmsdbmanager and start the system as usual. Immediately start trimming when the system comes up before the regionals try to  fill the transaction queues. 

 

 

 

Have a nice day 🙂

Andy Kemp
I've lasted longer in the technology industry than most certifications.
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.