Highlighted
Absent Member.. Clarence Lee Absent Member..
Absent Member..
286 views

snmp trap configurations content being being over written.

Dear All,

We are using nnmi version 9.20.9.23.004. 

While working on enabling the snmp object id thru menu path Incident > snmp trap configuration,  seem that when  navigate to  load incident configuration, it over rides the previous value in the snmp trap cofiguration.

Is there any way to recover this situation ?

Your advise please.

 

Regards,

Clarence

 

 

 

 

0 Likes
2 Replies
Micro Focus Expert
Micro Focus Expert

Re: snmp trap configurations content being being over written.

Hi, Clarence.

If only I understand the problem correctly you need to check browser supportability against product Support Matrix and also make sure you hit Save and Close all the open configuration windows. Changes will not take effect until all configuration windows are Save and Closed.

If that is not what you were asking about, please share few more details on what happens, may be screen-shot or copy or an error message will help. What are privileges of the user that makes those changes: L2, admin or system user? Is there no other user that makes changes to SNMP Trap configuration at the sane time?

Mikayel Grigoryan
HPE Software

If you find that this or any post resolves your issue, please be sure to mark it as an accepted solution.
0 Likes
Absent Member.. Clarence Lee Absent Member..
Absent Member..

Re: snmp trap configurations content being being over written.

Hello  Mikayel,

This is concerning of loading mibs and snmp trap configuration.

When navigating,thru menu path MIBs>Tools>Load/Unload Mibs,
on the right hand "action" choose display, rather then Load Mib,
if the MIB already being loaded and snmp trap configuration being done,
otherwise it will override the "checkmark" and the status of the
snmp trap configuration. There isn't any warning about overriding.
This is what's happend to us.

To resolve the issues, we base on the exported policy file which we exported
earlier on, grep the record "# from EVENT".
example of the grep record.
# from EVENT lgpEventLowBatteryWarning .1.3.6.1.4.1.476.1.42.3.3.0.3 "Status" Critical

Base this record we update back the snmp trap configuration, on the checkmark and the status.

Initially, what's we asking for, is there a tool available to revert back the situation,
rather then do manually.

Thanks and Regards,
Clarence

 

 

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.