APC UPS Data Center & Enterprise Solutions Forum
Schneider, APC support forum to share knowledge about installation and configuration for Data Center and Business Power UPSs, Accessories, Software, Services.
Posted: 2021-07-08 01:09 AM . Last Modified: 2024-02-29 10:51 PM
Link copied. Please paste this link to share this article on your social media post.
Posted: 2021-07-08 01:09 AM . Last Modified: 2024-02-29 10:51 PM
So we have used X3000 UPS's extensivly for a number of years. Up until about a year ago we were able to generate aq configuration and apply it via DHCP for every deployment. This would include user information. Now with the newer firmware it seems that this has been broken. The user configuration is now in a seperate file or has to be set manually and I don't see a way for these to be applied via DHCP which kind of negates any automatic configuration.
So does anyone have any best practices on applying the configuration both system and user, via DHCP to make this an automated process again?
Any help is appreciated, thanks!
Link copied. Please paste this link to share this article on your social media post.
Link copied. Please paste this link to share this article on your social media post.
Posted: 2021-07-08 01:09 AM . Last Modified: 2024-02-29 10:50 PM
Hi Nick,
Yes, the firmware on your UPS itself (7.4) doesn't matter for this NMC issue. I was referring to the firmware on the NMC that you eventually looked at. v6.1.1 is older FYI, AOS/sumx app is v6.2.1 is the latest and available for download @ http://www.apc.com/tools/download/index.cfm. And again, it does not fix this issue but has several other bug fixes in it if you wanted to upgrade.
The v6.3.X will be out later this year as I mentioned and be on our website I suspect around Nov/Dec but that can change.
Yes, it seems to have broken on v6 firmware. v5 and v6 are just completely different platforms under the hood so I have told the QA team to make sure we are actively testing this each release as we should've been anyway.
Lastly, users can/will not be configured through config.ini any longer unfortunately and is by design. Mass configuration of users is now handled via a separate .csf file and how to do it is explained here (and you can use that same INI utility to cascade the file out to NMCs)-> http://www.schneider-electric.us/support/index?page=content&country=US〈=en&locale=en_US&id=FA176542
Link copied. Please paste this link to share this article on your social media post.
Link copied. Please paste this link to share this article on your social media post.
Posted: 2021-07-08 01:09 AM . Last Modified: 2024-02-29 10:51 PM
Hi Nick,
Are you referring to the DHCP boot file name option mentioned here -> http://www.schneider-electric.us/support/index?page=content&country=US〈=en&locale=en_US&id=FA156110 ?
If so, yes, it broke (caused the NMC to go into a reboot loop) and someone else posted about it a little bit ago here. I believe it will be fixed in a version of v6.3.X firmware for AP9630/31 coming out later this year as I was the one who logged the bug.
We have other options of automating a push of a config.ini file after DHCP configuration for now as an option but that is about it until the issue gets fixed that I am aware of without using our StruxureWare product. (Information on that here with the utility available -> http://www.schneider-electric.us/support/index?page=content&country=US〈=en&locale=en_US&id=FA156117 )
Link copied. Please paste this link to share this article on your social media post.
Posted: 2021-07-08 01:09 AM . Last Modified: 2024-02-29 10:50 PM
Link copied. Please paste this link to share this article on your social media post.
Posted: 2021-07-08 01:09 AM . Last Modified: 2024-02-29 10:50 PM
Thanks for the reply. I can say for sure that it's been broke for me since the X3000's started to come with the Schneider Firmware. Right now it looks like I am running 7.4 (ID1003). So how can I have newer firmware than the version you just mentioned?
Link copied. Please paste this link to share this article on your social media post.
Posted: 2021-07-08 01:09 AM . Last Modified: 2024-02-29 10:50 PM
Link copied. Please paste this link to share this article on your social media post.
Posted: 2021-07-08 01:09 AM . Last Modified: 2024-02-29 10:50 PM
Never mind I see that my AOS version is 6.1.1. So with the update to 6.3.x later this year, I will be able to completly configure my UPS again with an INI file? This would include users as well?
Link copied. Please paste this link to share this article on your social media post.
Link copied. Please paste this link to share this article on your social media post.
Posted: 2021-07-08 01:09 AM . Last Modified: 2024-02-29 10:50 PM
Hi Nick,
Yes, the firmware on your UPS itself (7.4) doesn't matter for this NMC issue. I was referring to the firmware on the NMC that you eventually looked at. v6.1.1 is older FYI, AOS/sumx app is v6.2.1 is the latest and available for download @ http://www.apc.com/tools/download/index.cfm. And again, it does not fix this issue but has several other bug fixes in it if you wanted to upgrade.
The v6.3.X will be out later this year as I mentioned and be on our website I suspect around Nov/Dec but that can change.
Yes, it seems to have broken on v6 firmware. v5 and v6 are just completely different platforms under the hood so I have told the QA team to make sure we are actively testing this each release as we should've been anyway.
Lastly, users can/will not be configured through config.ini any longer unfortunately and is by design. Mass configuration of users is now handled via a separate .csf file and how to do it is explained here (and you can use that same INI utility to cascade the file out to NMCs)-> http://www.schneider-electric.us/support/index?page=content&country=US〈=en&locale=en_US&id=FA176542
Link copied. Please paste this link to share this article on your social media post.
Create your free account or log in to subscribe to the board - and gain access to more than 10,000+ support articles along with insights from experts and peers.