My client is running DCE 7.4.3 on a physical Enterprise server. They server is a bit old but still functional.
We have an issue where some of the devices have communication issues (communication lost alarms) but physical connectivity is there and we are able to launch to the said devices through DCE. We have confirmed that the SNMP community strings have not changed. And the device credentials are still the same.
There is no firewall in between the server and the devices. All are sitting in one LAN segment. Any ideas what the issue could be?
The first thing I'd recommend is to go to:
And confirm that the devices are providing the correct answers to the DCE.
Hi @GavanOB ,
Is the utility available on 7.4.3 from the web client? I have tried this on my test server and all i get is "The requested URL /nbc/status/SnmpWalk was not found on this server."
Any other suggestions?
Sorry, it's not available in 7.4.3, can you try to do an SNMP walk from a different computer?
snmp walk from the DCE web client is only available in DCE 7.6 and above. However you still use the device walk utility found here https://dcimsupport.ecostruxureit.com/hc/en-us/articles/360006388878-How-to-create-a-device-walk-fil...
this will also allow you to walk modbus devices.
out of curiosity, are they snmpv3 devices? If so, are they APC devices? If they are, I would recommend making sure they are running the latest firmware. You may need to reboot the web interface for snmpv3 communication to come back
Thank you @ATrabert
All devices are APC. Ranging from Inrows, rack PDUs and UPS units.
Nothing changed in the environment. They were reporting and they just happened to have lost communication.
A firmware update of the NMCs could assist the issue. I know the firmware has not been getting upgraded.
I would definitely recommend upgrading the firmware regardless then. Do you know DCE is polling them via snmpV1 or snmpV3? snmpV1 devices should be fine, but older nmc1 devices running 3.5.x have been known to have issues with snmpv3.
ok then, if firmware update/nmc reboot does not correct the issue, you may want to check the nmc event logs to see if there are any specific snmp events.
Discuss challenges in energy and automation with 30,000+ experts and peers.
Find answers in 10,000+ support articles to help solve your product and business challenges.
Find peer based solutions to your questions. Provide answers for fellow community members!