Re: Node Manager does not receive any snmp trap ! (59 Views)
Reply
Frequent Advisor
ASSIST
Posts: 93
Registered: ‎02-17-2000
Message 1 of 3 (59 Views)

Node Manager does not receive any snmp trap !

Hi!,,
I'm trying to test the trap reception capability of node manager with:

snmpnotify -v2c -A -c isnetmgr netserver5 .1.3.6.1.4.1.2427.6.1

And nothing appears in the alarm browser,,
any trap from any node , router ,etc. I can only see the polls nodes and Node Nanager pings,(I have a NM 6.1 with NT), all the 4 snmp services are started,, and ovstatus shows that all the proceses are running ,
What Happens?

Like Anthony Goh , sometimes I have the ovtrapd died with the message 'ovtrapd Not Running WinSNMP SnmpRegister() failed: 100 Exit(1)'

Well , maybe is an incompatible version of the wsnmp32 dynamic library,,,,BUT what is the compatible version??,,,
how can I obtain it?,,,,

can I solve anything with the latest patch,? the NNM_00483 ???

Best regards,, and Thank you very much,,

Daniel Vila.
Abast Systems.
Honored Contributor
Berlene Herren
Posts: 1,514
Registered: ‎10-11-1999
Message 2 of 3 (59 Views)

Re: Node Manager does not receive any snmp trap !

If the snmp master agent
service has not started by the time netmon and ovtopmd start, then this
situation will occur. Without any control NT will simply start all the
services at the same time and it will be a free for all as to who starts
first.

NT does provide 3 registry entries per service in order to control the
boot order. The registry entries are documented as :-

Under HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServices
you will see all the service names. Under each service the 3 variables
of interest are :

Group REG_DWORD Group name
specifies the name of the group of which the particular service is a
member
DependOnGroup REG_DWORD Group
name
Specifies zero or more group names. If one or more groups is listed,
at least one service from the named group must be loaded before this
service is loaded.

DependOnService REG_DWORD Service name
Specifies zero or more Services subkey names. If a service is listed
here, that named service must be loaded before this service is loaded.


-- In fact the REG_DWORDs should be REG_MULTI_SZ since they need to be
ascii.

This can be resolved by simply updating the "HP Openview
Process Manager" by adding the DependOnService variable and setting it
to "EMANATE" the master agent service name.






The temporary workaround is to simply add the variable

DependOnService REG_MULTI_SZ EMANATE

to the HP Openview Process Manager under the

HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServicesHP Openview Pr..

Berlene
http://www.mindspring.com/~bkherren/dobes/index.htm
Honored Contributor
Berlene Herren
Posts: 1,514
Registered: ‎10-11-1999
Message 3 of 3 (59 Views)

Re: Node Manager does not receive any snmp trap !

If the snmp master agent
service has not started by the time netmon and ovtopmd start, then this
situation will occur. Without any control NT will simply start all the
services at the same time and it will be a free for all as to who starts
first.

NT does provide 3 registry entries per service in order to control the
boot order. The registry entries are documented as :-

Under HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServices
you will see all the service names. Under each service the 3 variables
of interest are :

Group REG_DWORD Group name
specifies the name of the group of which the particular service is a
member
DependOnGroup REG_DWORD Group
name
Specifies zero or more group names. If one or more groups is listed,
at least one service from the named group must be loaded before this
service is loaded.

DependOnService REG_DWORD Service name
Specifies zero or more Services subkey names. If a service is listed
here, that named service must be loaded before this service is loaded.


-- In fact the REG_DWORDs should be REG_MULTI_SZ since they need to be
ascii.

This can be resolved by simply updating the "HP Openview
Process Manager" by adding the DependOnService variable and setting it
to "EMANATE" the master agent service name.






The temporary workaround is to simply add the variable

DependOnService REG_MULTI_SZ EMANATE

to the HP Openview Process Manager under the

HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServicesHP Openview Pr..

Berlene
http://www.mindspring.com/~bkherren/dobes/index.htm
The opinions expressed above are the personal opinions of the authors, not of HP. By using this site, you accept the Terms of Use and Rules of Participation.