Subscribing is a smart move!
You can subscribe to this board after you log in or create your free account.
Invite a Co-worker
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.
Send Invite Cancel
Solved
Go to Solution
Link copied. Please paste this link to share this article on your social media post.
I have some feedback and enhancement requests the AP9630 NMC and PCNS, based on my unsuccessful effort to configure my equipment (SMT1000 and AP9630) to work the way I would like it to work. My impression is that the AP9630 NMC and PCNS have a huge amount of capability, but at the same time, seem to be very complex while at the same time lacking flexibility in key areas. Considering APC is considered by most to a leader in UPS technology and APC UPS technology is considered high-end WRT price, this is disappointing.
By far the biggest issue I have is that there are no mechanisms to trigger events based on battery charge. Considering that battery charge is a fundamental variable, not a derived variable like runtime, in my opinion, this is a glaring omission. The two mechanisms available for triggering events (runtime and time) make it very difficult to manage remaining battery charge. I would like to be able to trigger events based on battery charge because with a varying load it's not possible to do it based on runtime. I would like to be able to shut down a computer, an outlet group or the ups based on battery charge. I would also like to be able to turn on outlet groups based on battery charge. APCUPSD supports battery charge. So should the APC9630 NMC and PCNS. In my case, the reason this is such an issue is because immediately when the UPS goes on battery, after computers are shut down to shed load, the runtime goes from ~15 minutes to ~35 minutes. I do not want to delay shutting down the last server until less than 10 minutes of runtime remains. I would rather shut the server down (and power off the UPS) at around 20-25 minutes, which is more runtime than the UPS has when the network is fully operational. The only fix for this is to allow shutdown based on battery charge.
The next issue is the use of fixed (non-configurable) timers. Examples are the "70 second delay" and the "2 minute delay". There are probably other examples.
Why are these timers fixed? Why can't they be adjusted? Possibly if there was an explanation what purpose the timers serve it and why they are set to the chosen durations they might make sense, but as it is, they appear to be set to arbitrary durations for no obvious reason.
One purpose for the 70 second delay might be to allow a user to save open files, but if no user is sitting at the computer, the time is wasted and if the intention was to shed load as soon as possible, the battery is drawn down needlessly during the delay. A second purpose for the delay could be in case the power restored, but currently, even if power is restored before end of the 70 second delay, the computer is still shut down! Are you kidding?!?
For the 2 minute delay, it's not obvious what it's for considering the reference to low battery duration, which implies the computer should be shut down within the low battery duration, before the 2 minute delay begins. If it is to allow an additional margin of time for computers to shut down upon receiving the shut down command, 2 minutes should be a default that can be over-ridden by the administrator, otherwise it only causes unnecessary battery discharge.
The next issue is the lack of capability to configure events.
UPS On Battery: It should be possible to delay this event from being immediately triggered by the NMC to allow for transient power interruptions. This would allow for users in areas where there are frequent short duration power failures to ride through such interruptions.
Input Power Restored: If PCNS can be configured to trigger a command file upon restoration of power, why can't it be configured to cancel a shutdown triggered by a UPS On Battery Event?
Battery Discharged: If the NMC can raise this event, why can't it raise an events based on a percentage of discharge?
Outlet Groups Configuration: If NMC can be configured with Min Return Runtime for outlets, why not battery charge? When the outlet group is turned off, the runtime is infinite. Runtime only makes sense with known loads.
Why can't the NMC send wake-on-lan events?
The next issue is the lack of simulation and testing capability. As it is, the only way to test that everything is working is to actually pull the plug from the UPS. It would be useful and preferable if testing could be done by simulating events. For example, the user could trigger events such as UPS On Battery or Battery Discharged events from the NMC user interface to cause the configured actions to occur, without needless wear and tear on the UPS battery. Ideally, a scenario could be tested using a script that would shut down computers and outlet groups as if the UPS was on battery, then turn outlet groups and computers back on as if the UPS input power was restored.
Accepted Solutions
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.