Welcome to the new Schneider Electric Community

It's your place to connect with experts and peers, get continuous support, and share knowledge.

Important Announcement: WELCOME to the new Schneider Electric Community! Community is now no longer part of Exchange, and is now rebranded under se.com. If you have any bookmarks and links saved, we request you to update them to ensure that you continue accessing our community from this new location. For any issues that you might encounter as part of this change, please reach out to SchneiderCommunity.Support@se.com, and the team will help to get your issues resolved.
Invite a Co-worker
Send a co-worker an invite to the Exchange portal.Just enter their email address and we’ll connect them to register. After joining, they will belong to the same company.
Send Invite Cancel

SSH bug in NMC2 running AOS/SUMX v7.0.4

APC UPS Data Center Backup Solutions Forum

Schneider Electric support forum for Data Center UPS, software and services including our APC offers designed to share knowledge, installation, configuration, and general product use.


SSH bug in NMC2 running AOS/SUMX v7.0.4

Hi Schneider Electric Exchange Community,


On June 2nd, 2022, I discovered a bug in AOS / SUMX v7.0.4. ( released Jul 26 2021 ) running on AP9630 NMC2.


I'm posting here, as I don't know what's Schneider's formal way of submitting firmware bug reports.


When a 'Host Name' is set to a value that's 3 characters or less, when I try to SSH to the AP9630, my connection is immediately closed with this error message:


kex_exchange_identification: read: Connection reset by peer
Connection reset by 192.168.blah.blah port 22


The 'Host Name' in question is the one in DNS Configuration, ie. in the web GUI:  Configuration / Network / DNS / Configuration.


Has anyone else seen this?   My work-around is to fake the 'Host Name' by adding the 4th character, so instead of 'Host Name' being 'blah', I made it 'blahh';  that immediately fixed the problem and SSH on the AP9630 started working again.




1 Reply 1
Ensign Ensign

Re: SSH bug in NMC2 running AOS/SUMX v7.0.4



You can raise a support ticket to the SE team that supports your country to report the issue that you are facing.  Please use the link below and you might need to change it to your country as it is set to USA.


See Contact SE Technical Support 


The Technical Support might require you for a screenshot of the issue as well as the NMC TAR/Debug file so I have included the FAQ below to assist you on how and where to get it.


See FA156131 - How can I download Event, Data, Configuration, and Debug files from my Network Management... 


Secure Power Team
Tags (1)