Maintenance is complete- We've moved from the saas.hpe.com domain to softwaregrp.com click to read more
As part of our journey to complete our separation work and our future integration with Micro Focus, we've now updated our domain for the community. This is an interim step, which will be followed by a series of future update / improvements: - Piloting Idea boards - Refreshing the entire UI. (more to come later) - and more
Network Management / (OpenView-NNM) Practitioners Forum
cancel

NNMi Deduplication events

Highlighted
RobertoMarinoHP
Respected Contributor.

NNMi Deduplication events

Hi all,

I am currently using an NNMi 9.20 on cluster and I have the following problem.

The customer has configured the snmp traps sending, on the monitored device, to all the Cluster Manager Servers, both the physical one and the VIP one.

Doing so we are always receiving TWO traps for each events (one to the VIP IP and the other on the Active Server), I want to know how to eliminate one of this two traps from the appliccation side.

To be more precise I want to receive and show only one trap not two (duplicated), there is a way to "DROP" the trap directed to the physical IP and not the one directed to the VIP?

For example, I'm receiving 2 traps on my system, onne towards IP 10.10.10.1 (Active Node) and the other to IP 10.10.10.3 (VIP), I want only the one directed towards the 10.10.10.3 IP, how can I stop the other one?

I have tried also with the Deduplication tab on the SNMP Trap Configuration, but it doesn't seem to work like I want, it only increment a count of Deduplicadet traps but doesn't discard either of them.

Thank you for you kind attention, any help it's really appreciated.

Regards, Roberto.

4 REPLIES
Dan_Morhart
Trusted Contributor.

Re: NNMi Deduplication events

There is a file setting that may help in this situation, you can do some more reading in the help regarding it.

/opt/OV/bin/nnmtrapconfig.ovpl -setProp trapInterface <Virtual_IP_of_cluster> -persist

The situation I had was different, but the general idea is similar.

RobertoMarinoHP
Respected Contributor.

Re: NNMi Deduplication events

Hi Dan,

thanks for your answer.

Do you mean that by using the command you suggested I can convey the "IN/OUT" traps' flow both from and to the Server NNM on only one interface?

I have this Hypotethical situation:

NNMi Cluster:

Node1 10.10.10.1 (active one)

Node2 10.10.10.2 (passive one)

VIP 10.10.10.3

The device monitored by me are currently sending trap to all the three devices (that way I always receives a double trap for each kind of allarms), if i run the command you suggested, for example in this way "/opt/OV/bin/nnmtrapconfig.ovpl -setProp trapInterface 10.10.10.3 -persist", will I receive traps only on the VIP IP (so only one)?

Because I also have founded this information on the /var/opt/OV/shared/nnm/conf/ov.conf where it's said the following:

---------------------------------

# uncomment this line and change <nnn.nnn.nnn.nnn> to the IP Address of

# the interface you want NNM to use for communications.

# Note: if you are in an MC/ServiceGuard environment, the IP Address can

# be used to indicate the IP Address of a MC/ServiceGuard floating IP Address.

#NNM_INTERFACE=<nnn.nnn.nnn.nnn>

 

# If the NNM_INTERFACE is set and you do want SNMP communications

# to use that address, then set this value to OFF.

IGNORE_NNM_IF_FOR_SNMP=ON

---------------------------------

But I'm not sure if it will work.

Thanks and regards, Roberto.

Dan_Morhart
Trusted Contributor.

Re: NNMi Deduplication events

I believe that using this setting should work, because you are specifying which interface NNMi should use for listening.  From the man page:

trapInterface ip address
Set IP address on which the Trap Service listens for traps. By default it listens on all interfaces.

 

LindsayHill
Acclaimed Contributor.

Re: NNMi Deduplication events

Why not just fix the devices in question?

Or if you don't want to change NNMi, then use iptables on the server.

Or try making the change, and you'll see very quickly if it works, based upon the netstat output.