Device IP Configuration Utility does not find NMC when SNMPv1 doesn't have public community name

[JohnsIsland_apc]

I have been baffled trying to figure out why Device IP Configuration Utility stopped finding devices on the network.  I figured it was a routing change on the network.  Today, the Device IP Configuration Utility did find a device, so I compared the NMC configuration to a device which wasn't found.  I found the NMC which was found had a SNMPv1 community of public, and the device which wasn't found did not have public community.

Reading the help, readme file I didn't see where it needs a public community to work.  Perhaps this could be added to the readme file.  Another option is to allow the user to specify the community which Device IP Configuration Utility uses to search for NMC's.  

I think the public community was removed from the NMC's due to security concerns.

Jeff

[BillP]

Hi Jeff,

I will log a product change request about this. You're right that the utility does rely on SNMPv1 and I think the assumption is that the user is finding NMCs on the network for first setup using this tool - which we ship the NMC with SNMPv1 enabled with the default community string of public. Then, of course the user would find the NMC, assign IP settings, and configure it from there, likely never using the utility again after that.

Can I ask more about how you're using this? Are you finding NMCs on the network after first setup for a different reason? Just asking so I can help better explain your perspective and use case in my request so that we are all on the same page.

[JohnsIsland_apc]

I would like to know if Device IP Configuration Utility can utilize SNMPv3, so SNMPv1 can be disabled.

[BillP]

Unfortunately no, there is no SNMPv3 support in the utility.

The utility is just designed to find NMCs for first time setup. We don't ship the cards with SNMPv3 enabled by default, especially since SNMPv3 requires some configuration to get it working properly.

I would love to hear more about you're application and how you're using this tool though.

[JohnsIsland_apc]

Angela,

Sometimes I configure a UPS/NMC while it's on my desk, then someone takes the UPS/NMC to a different site (with a different subnet) and they don't assign a DHCP reservation or let me know what IP the NMC picked up.  When the aforementioned happens, I run the Device IP Configuration Utility to find the NMC IP.  I try to prevent this by requesting a DHCP reservation for the remote site ahead of time, however I have been know to make a mistake and forget to request a reservation ahead of time.  Sometimes I remember to check my e-mail to see if I received a startup e-mail from the NMC.  

I also have been know to run Device IP Configuration Utility when I want to ensure all NMC's are on the network--I compare the found list to my list of UPS's.  Ideally I would check my e-mail to see if I had received a self test notification from each NMC, however that's a bit of work.

Thanks,

Jeff

[BillP]

Hi Jeff,

OK, thanks for the background on this. As I said, I'll enter a product change request for the NMC group to review and consideration.

[JohnsIsland_apc]

Angela,

I also use Device Up Configuration Utility as a check after upgrading a number of NMC firmwares to determine if I recorded all the upgrades.

 Jeff

[BillP]

OK, understood. While I personally understand why you're using this utility and that it can provide a little shortcut for certain tasks, like checking firmware revs, I have a feeling some may argue that it is not the main intent of the utility - especially specific to the firmware rev checking.

The other use case I think is valid and makes sense (again - personal opinion) and I think it will become more important as laws like those being passed in California with non default credentials at least make a case for evaluating the ability to specify a non-default community name for scanning.

[JohnsIsland_apc · Accepted solution]

Angela,

Thanks for listening and requesting an update to the software!

Jeff