Highlighted
Vice Admiral
Vice Admiral
192 views

Suppressing Trap Incidents

Jump to solution

I have a switch that has a bad fan and power supply. The switch keeps sending traps regarding fan and power supply failures. When I go into Incident Configuration and enable trap suppression it supresses this  trap OID  for all devices.

How do I get granular and specify suppression of these traps for just a specific device.

 

Thanks

 

John

0 Likes
1 Solution

Accepted Solutions
Highlighted
Micro Focus Expert
Micro Focus Expert

Hello John,

 

 

To handle the unwanted traps you have few possibilities:

 

1. The best way is to change configuration on the sending device. This will reduce also the network traffic and will free resources on NNMi servers as memory and CPU.

 

2. As Nick mentioned above, you can filter the unwanted incoming traps with one of the next two configuration files:

    • <NNMDataDir>/shared/nnm/conf/nnmtrapd.conf
    • <NNMDataDir>/shared/nnm/conf/trapFilter.conf

        Format is common for both files:

                        <IP_Address,Event Oids>

            The difference between two is that the traps blocked by trapFilter.conf do not get stored in the trap binary store nor do they take part in analysis of incoming trap rates.

 

3. With “enrichment” of the SNMP Trap configuration – but this is common for all monitored devices in the network.  

 

 

Best Regards,

Svetoslav

View solution in original post

5 Replies
Highlighted
Absent Member.. Absent Member..
Absent Member..

If you set the node as either "not managed" or "out of service" then traps wil be ignored for the device.  To do this, within the gui, select the node then from the "actions" drop down, select "management mode" then select the desired setting.

 

 

HP Support
If you find that this or any 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 and show your appreciation.
0 Likes
Highlighted
Absent Member.. Absent Member..
Absent Member..

Another option would be to use the suppression you tried previously and add a payload filter to control what is suppressed.

HP Support
If you find that this or any 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 and show your appreciation.
0 Likes
Highlighted
Absent Member.. Absent Member..
Absent Member..

Hey,

 

we can filter the specific trap using trapfilter.conf  file using node ip and specific OID.

 

 

Just try this option and let me know.

 

 

 

with regards,

Nick

0 Likes
Highlighted
Micro Focus Expert
Micro Focus Expert

Hello John,

 

 

To handle the unwanted traps you have few possibilities:

 

1. The best way is to change configuration on the sending device. This will reduce also the network traffic and will free resources on NNMi servers as memory and CPU.

 

2. As Nick mentioned above, you can filter the unwanted incoming traps with one of the next two configuration files:

    • <NNMDataDir>/shared/nnm/conf/nnmtrapd.conf
    • <NNMDataDir>/shared/nnm/conf/trapFilter.conf

        Format is common for both files:

                        <IP_Address,Event Oids>

            The difference between two is that the traps blocked by trapFilter.conf do not get stored in the trap binary store nor do they take part in analysis of incoming trap rates.

 

3. With “enrichment” of the SNMP Trap configuration – but this is common for all monitored devices in the network.  

 

 

Best Regards,

Svetoslav

View solution in original post

Highlighted
Vice Admiral
Vice Admiral

That helps. Looks like the filter files is the way to go. I tried to to do it in the tool with adding the node IP enrichment but it did not work.

 

Thanks Again - 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.