SNMPv3 + Dual NIC Network Collector

Question

So I am having issues validating my SNMPv3 when trying to add nodes to the SaaS. I have verified the configurations on the switches I want to add, but it fails validation every time. I am using SHA1 and AES-128 for my authentication and encryption. Is there additional configurations needs for the Network Collector?

I am also using an HP Elite Mini as my network collector using the physical NIC, and a USB to NIC adapter to connect our secondary network. I have added and deleted routes to use one interface as the ingress and egress. When I add nodes using ICMP since SNMPv3 is not working for me, it can discover and gives the syslog that telemetry will show shortly, but the Node never comes up nor shows in the inventory of added Nodes. How I can I resolve both issues?

lcolehower · Answer

I am using version 3.0.102 on my Network Collector.

Pathway leaves and comes back the same pathway.

It shows no Nodes that have been added when I check Discovered under both Other and Network Device.

Still no success

PJC · Answer

SHA-1/AES-128 is supported by the Network Collector, so there shouldn’t be any additional SNMPv3 setting required on the collector. I’d test from the Network Collector host itself and verify that the SNMPv3 user has read access to the system OIDs, especially sysDescr, sysObjectID, and sysUpTime, with the correct context if the device uses one. Also check UDP/161 and any device ACLs, making sure they allow the collector’s actual source IP.

Because the collector has two NICs, confirm with a packet capture that the request leaves through the intended interface and that the reply returns through the same path. ICMP discovery only provides limited status data, so check Network > Discovered, filter for Found, and import the device as a Network Device. If it appears as Other, it can still be imported as a network device. The collector version and exact validation error would help narrow down the SNMP issue.