Unable to connect Austin Hughes IPM Dongles to DCE Version 7.7.0
EcoStruxure IT forum
Schneider Electric support forum about installation and configuration for DCIM including EcoStruxure IT Expert, IT Advisor, Data Center Expert, and NetBotz
Send a co-worker an invite to the portal.Just enter their email address and we'll connect them to register. After joining, they will belong to the same company.
You have entered an invalid email address. Please re-enter the email address.
This co-worker has already been invited to the Exchange portal. Please invite another co-worker.
Please enter email address
Send InviteCancel
Invitation Sent
Your invitation was sent.Thanks for sharing Exchange with your co-worker.
Link copied. Please paste this link to share this article on your social media post.
Posted: 2023-04-0602:16 AM
Unable to connect Austin Hughes IPM Dongles to DCE Version 7.7.0
Dear Team
Good day. We are trying to add new Austin Hughes IPM dongles to an existing system which already has previous dongles configured successfully but we are facing some issues.
Primary issue is that we are trying to fix new 6 AH IP dongles to the system . 3 Dongles are working fine but the remaining 3 go into failure mode soon after discovery even though SNMPV3 walk and ping is successful for all dongles. Also from the 3 dongles that we are able to connect,the DCE will only allow 2 connections and the 3rd one will be connected only if any of the other 2 is disconnected.
Please advice as to what might be the issue that is causing this. We have even replaced the switch and checked but same issue. We have enough DCE node licenses also.
If you are still experiencing an issue with this, I recommend reaching out to technical support for investigation.
Each of these should not affect one another if they are separate devices on the network. If you didn't have enough licensing they would not show up in DCE at all as you would run out of licensing.
If SNMPv3 is giving issues, I always recommend briefly trying SNMPv1 to see if it works successfully or not and then it would tie it to an SNMPv3 configuration/issue.