Our vBulletin migration is complete.
Welcome vBulletin users! All content and user information from the Micro Focus Forums (vBulletin) site has been migrated to this site. READ MORE.
johnivon Honored Contributor.
Honored Contributor.
111 views

Blocking Traps

Jump to solution

Hello,

 

I added some OIDs to the Trapfilter.conf file but noticed that they are still showing up in the Top Trap Rate by OID I run in NNMi. Is the change dynamic or is their a command I need to run to make it active.

 

Thanks

 

 

John

0 Likes
1 Solution

Accepted Solutions
Vincent_M_NNM Acclaimed Contributor.
Acclaimed Contributor.

Re: Blocking Traps

Jump to solution

Hello Johnivon

 

Thanks for your question

 

Once that you add the OIDs and IP in this file you have run this command nnmtrapconfig.ovpl -readFilter to apply filter changes to the running configuration.

 

Also you have to make sure that the syntax that you are using is the appropriate for example:

 

<IP Address, OID[,OID]*>

 

Here are some examples taken from the "Reference Pages" document that you can find attached to this post.

 

The following example blocks all generic traps from all subnets in the range 10.2.120 to 10.2.127:

<10.2.120.0/21, .1.3.6.1.6.3.1.1.5.*>

 

The following example blocks link up traps from all devices in the 10.6.112/21 subnet whose enterprise OID

is .1.3.6.1.4.1.11.2.3.7.11.17:

<10.6.112.0/21, .1.3.6.1.6.3.1.1.5.4.1.3.6.1.4.1.11.2.3.7.11.17>

 

Hope this information helps you,

 

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
4 Replies
Vincent_M_NNM Acclaimed Contributor.
Acclaimed Contributor.

Re: Blocking Traps

Jump to solution

Hello Johnivon

 

Thanks for your question

 

Once that you add the OIDs and IP in this file you have run this command nnmtrapconfig.ovpl -readFilter to apply filter changes to the running configuration.

 

Also you have to make sure that the syntax that you are using is the appropriate for example:

 

<IP Address, OID[,OID]*>

 

Here are some examples taken from the "Reference Pages" document that you can find attached to this post.

 

The following example blocks all generic traps from all subnets in the range 10.2.120 to 10.2.127:

<10.2.120.0/21, .1.3.6.1.6.3.1.1.5.*>

 

The following example blocks link up traps from all devices in the 10.6.112/21 subnet whose enterprise OID

is .1.3.6.1.4.1.11.2.3.7.11.17:

<10.6.112.0/21, .1.3.6.1.6.3.1.1.5.4.1.3.6.1.4.1.11.2.3.7.11.17>

 

Hope this information helps you,

 

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
Highlighted
Absent Member.. Walinton Absent Member..
Absent Member..

Re: Blocking Traps

Jump to solution

John

 

Please run this command to validate that your configuration entries were taken from the file

 

The output may be large, but please go to the beginning of it and search for "Filter Configuration"

 

The output will be similar to below:

 

[root@~]# nnmtrapconfig.ovpl -dumpBlockList
Filter Configuration:
List of blocked source address and trap combinations by the early filter:
*: .1.3.6.1.6.3.1.1.5.3.*
*: .1.3.6.1.6.3.1.1.5.4.*

 

If the configuration hasn't been loaded, please load the config as per Vincent's recommendation and make sure that the file name is trapFilter.conf as this is case sensitive

 

Thanks

HP Support
If you find that this or any post resolves your issue, please be sure to mark it as an accepted solution.
0 Likes
AndyKemp Acclaimed Contributor.
Acclaimed Contributor.

Re: Blocking Traps

Jump to solution

I think this is the answer you're looking for:

 

The reference file trapFilter.conf is only loaded into working memory when the system starts OR the command /opt/OV/bin/nnmtrapconfig.ovpl -readFilter is executed.

 

 

So the trapfilter is not dynamic but statically loaded.

 

 

(edited to correct executable name to standard)

Have a nice day 🙂

Andy Kemp
I've lasted longer in the technology industry than most certifications.
0 Likes
johnivon Honored Contributor.
Honored Contributor.

Re: Blocking Traps

Jump to solution

Excellent. Thanks everyone for your help.

 

-John

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.