It's your place to connect with experts and peers, get continuous support, and share knowledge.
Contact SchneiderCommunity.Support@se.com if you have any questions.
A support forum for Data Center Operation, Data Center Expert, and EcoStruxure IT product users to share knowledge on installation, configuration, and general product use.
You can subscribe to this forum after you log in or create your free account..
Posted: 2020-10-21 06:31 AM
Hi, I have upgreaded DCE to 7.8.0 using the correct method but the SNMP V3 connections have broken and now i cant acess the devices within DCE and they are showing as faliure comunication lost. They can be reached by ping.. no settings have changed so how can this be? and they are HTTPS for web browsing!!
Posted: 2020-10-22 12:43 AM
I haven't seen this happen but the two things I recommend are to first re-scan the devices, you don't need to remove them just create a scanning job with the same IPs and settings that the devices are already added with.
If that doesn't work go to http(s)://DCE-IP/nbc/status/SnmpWalk and preform an SNMP walk of one of the devices and ensure it responds correctly. (note that the URL is case sensitive)
Posted: 2020-10-23 07:59 AM
Appologies missed your response. Correct i have not seen this either, I got to the bottom of the rack ATS's thats due to firmware so will upgade it and it will fix the issue there, but the Rack Access PX HID and rPDU's all run latest FW but mojority show connection failure i have ran the device search again to now joy, they are on the private network GB2 and DHCP, the logs show this is working correctly i will try and get someone to site to run a device walk.
Posted: 2020-10-23 08:16 AM
While you're there, would you be able to confirm the exact error message? We have a known problem on 7.8.0 where you may get the "DDF failed to transfer" errors if the devices don't respond to pings, which would also get you red lights across the board if affected.
(That's not to say I'm doubting your report, just an easy one to tick off while you're at it.)
Posted: 2020-10-27 11:51 PM
I know you mentioned that you didn't change any settings. But I'd like to confirm if you changed from SNMPv1 to SNMPv3? If yes, was it after the upgrade or before?
Posted: 2020-10-28 12:09 AM
Yes it was changed prior to upgrade the server has been rebooted numerous times no problem. The log files are with Rich (screen) tech support
Posted: 2020-10-28 11:16 PM
I would assume that you followed the guide on changing SNMPv1 to SNMPv3.
Can you go to SNMP Device Scan Settings then check one of the device if the protocol has changed to SNMPv3? If it did change to SNMPv3, check the Protocols if it's the correct ones you configured on the device.
Posted: 2020-10-29 01:15 AM
Without sounding rude i know you dont know me but I am a certified software engineer for DCE, DCO all modules!! everything has been checked and checked again. It was working fine before the upgrade as stated, the server has been rebooted many times with no issues kit all comes back on line no problems. after applying the upgrade some Rack Access PX HID kits come back along with some rPDU's but the majority show failure / unable to connect they are all on the same version of FW so it eliminates this cause. tried searching for devices again using last 2 as wild cards * just incase the devices have picked up a new IP (as they DHCP) and the log files show this search is carried out but no devices return. i am reluctant to rebuild the machine to 7.6 and restore from backup as this solves nothing just hides it.
Posted: 2020-10-30 08:08 AM
I want to mention I am also having a similar issue. I had two AP8930 PDUs communicating just fine (I have 164 offline but I can't confirm they are all because of this issue but they could be). And they were communicating with DCE 7.8. Then I rebooted the server after changing the CA Cert and tried to disable port 80 and now they won't communicate.
The strings didn't change or anything, I have discovered other PDU's with the same scan. These two specific ones are now only showing up as SNMP Device and will not communicate!