This question was originally posted on DCIM Support by Mate Fekete on 2018-03-09
I have the following NMC card with the latest firmware:
and I am using SNMPv3 in DCE for monitoring. If I change the authentication and privacy protocols to MD5 and DES I lose connection in DCE. Of course I change in sync the protocol in Device Scan Settings on this device.
So for some reason DCE can reach the device if I don't use any protocol:
But with this solution I "kill" the benefit of SNMPv3.
Can you help in that?
This answer was originally posted on DCIM Support by Steven Marchetti on 2018-03-09
The easiest way to get this working (and troubleshoot) is to delete the device and re-add it using SNMP version 3. If you have many devices, that can be cumbersome. IN this case, I would suggest following k-base FA158442 which walks you through how to change the configuration so that DCE sees it.
If that fails, you may want to verify that a computer in the same subnet as DCE can actually use those SNMP version 3 settings to access that card.
This comment was originally posted on DCIM Support by Mate Fekete on 2018-03-09
I already deleted the device and added back to DCE
I'm familiar with that k-base FA158442 because I changed all my devices from v1 to v3 two month before. But this particular device already used v3.
However I tested with v1 and v3 (with 'None' settings) and working fine so it is not a network/firewall issue. I assume your last sentence wanted to point to that.
What is happened: today I upgreded the firmware from 3.5.5 to the latest. Before the firmware upgrade SNMPv3 with DES and MD5 went smoothly.
This comment was originally posted on DCIM Support by Steven Marchetti on 2018-03-09
My last sentence was to test using a different computer. Using that computer, do an SNMP get to the device in question. Do this to verify the device itself is working using the SNMP version 3 protocol and the security setting you're using. This way you can figure out if it is a DCE issue or an NMC issue.
What version of DCE are you using?
This comment was originally posted on DCIM Support by Mate Fekete on 2018-03-18
The following command solved my problem: resetToDef -p keepip 😀
Discuss challenges and get support in energy and automation with 30,000+ experts and peers.
Over 10,000+ support articles are available to help you find answers to your product and business challenges.
Find peer based solutions to your questions. Provide answers for fellow community members!