If you are saying that port 161, 162 are not in the listening state. So, yes this could be the issue. These ports used for Communication between the NNMi Management Server and SNMP agent, they should be in open state.
You could ask your network team to check it. ( As suggested above, you can use the WireShark to verify the communication issue)
For the second request " How to configure snmp on agen?" --> You should contact with your network team in order to configure SNMP on agents and configure a devices to send SNMP traps. Because it depend on the kind of device vendors, each vendors have its own way to enable SNMP and configure to send SNMP traps.
For example, the following is using on the cisco router:
Use this command in order to enable the Read-only (RO) community string:
Router(config)#snmp-server community public RO where "public" is the Read-only community string.
Use this command in order to enable the Read-write (RW) community string:
Router(config)#snmp-server community private RW
where "private" is the Read-write community string.
The following example shows how to enable the router to send all traps to the host specified by the name myhost.cisco.com, using the community string defined as public: Router(config)# snmp-server enable traps Router(config)# snmp-server host myhost.cisco.com public
And the last question: "are the services SNMP Service and SNMP Traps required for NNMi to function properly?"
Answer: You don't need to adjust the SNMP service and SNMP Traps on the NNMi management server (Windows server), both should be in default setting.
Best Regards, Dong HP Support IF this or any post resolves your issue, Plz be sure to mark it as an accepted solution. To show your appreciation, click KUDOS !!!
We’ve made some progress. Last night, we ran the following command “nnmbackup.ovpl –type online –scope all –force –archive –target D:\HPNNM_backup” to archive the logs/traps. Once this was executed, we began receiving SNMP traps. However, we are still not receiving SNMP traps from some of our devices such as our Cisco IPS.
As such, I’d like to know how to check on what port is the NNM listening for SNMP traps? Please see below HPOM agent integration configuration.
The screenshot illustrated a port 5162 and destination being the NNM itself.
"As such, I’d like to know how to check on what port is the NNM listening for SNMP traps? "
"netstat -ano | findstr 162" (on Windows)
" netstat -anp | grep 162" (on Linux)
...look for the entry "UDP 0.0.0.0:162".The PID associated with that netstat entry should be ovjBoss's PID (select the PID column in task manager,or use the ps command in Linux). This is the default port on which NNMi receives SNMP Traps.
Suppose a non default configuration was done (for whatever reason), a simple method is to use the following command:
"nnmtrapconfig.ovpl -showProp | findstr trapPort" (works even without the findstr part, I filtered it just to show relevant info).
trapPort : 162 trapPort : UDP port on which server listens for traps
Or simply execute "nnmtrapconfig.ovpl -showProp" to see all trap configuration parameters, along with their current values.
"Please see below HPOM agent integration configuration. The screenshot illustrated a port 5162 and destination being the NNM itself."
The screenshot is the NNMi HPOM Integration Form.
One can integrate HP OM with HP NNMi (check the deployment guide on this topic to see the business value in doing this).
In such a situation, the OM Agent is installed on the NNMi server.
The mechanism is as follows (crude explanation):
>>Monitored device (switch/router) sends traps to NNMi Server on UDP 162.
>>NNMi 'listens'/'receives' these traps, processes them, and then, when such an integration is configured, forwards these traps (with additional info) to the OM Agent (which is installed and listening on the same NNMi server, BUT using port UDP 5162).
>>The OM Agent receives this info from NNMi, and then forwards the info to the OM Server (mother ship for this agent).
Such integrations are called NorthBound Integrations, because NNMi receives info, and transmits it 'upwards' (north like the way directions are shown on a map, North South East West) to an entity (in this case the OM Agent).
All this info is mentioned in the NNMi Deployment Guide, and the Admin Guide.
I am facing a problem that in all my Switch Nodes the State is showing 'Not Polled' and all the interface of Switches are not responding. On the other hand in MSS Nodes, State is being polled timely and all the interface are responding. All the service of NNMi 8.10 are running. SNMP services of Server are disabled and of NNMi are running.