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.
Link copied. Please paste this link to share this article on your social media post.
Posted: 2024-12-26 01:27 AM
Hi,
Since I upgraded an AP4423 network to 7.1.4, I get this alarm on my supervision.
Every other entities are OK and I have no error on the device web interface.
Do you know what VoltageOutStatus is and do you know if this is an error or a real problem on the device ?
Thank you for your help !
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: 2024-12-27 01:47 PM
What NMS are you using via SNMP?!? What does the verbose logs show as to the original vs new OID?!?
Confirm the OID in 7.1.4 hasn’t changed from the previous firmware’s version. From personal experience if the NMS hasn’t been programmed to identify new or changed OID’s errors will be seen / declared.
Given the PDU continues to operate fine and the web interface hasn’t declared any errors / faults indicates this is a NMS software error.
The voltage out is exactly what it sounds as indicating the voltage output from the PDU.
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: 2025-01-02 01:02 AM
Thank you for your answer.
We use Centreon.
Nothing changed but the device firmware.
I'll try to delete and create it again.
I'm not sure what you mean by verbose here.
This is the complete output for this device:
CRITICAL: Entity 'VoltageOutStatus' status is 'fail'
Checking entities
entity '1Dot0VPowerSupply' status is 'atsPowerSupplyOK' [instance = 1Dot0VPowerSupply]
entity '24VPowerSupply' status is 'atsPowerSupplyOK' [instance = 24VPowerSupply]
entity '24VSourceBPowerSupply' status is 'atsPowerSupplyOK' [instance = 24VSourceBPowerSupply]
entity '3dot3VPowerSupply' status is 'atsPowerSupplyOK' [instance = 3dot3VPowerSupply]
entity '5VPowerSupply' status is 'n/a' [instance = 5VPowerSupply]
entity 'CommStatus' status is 'atsCommEstablished' [instance = CommStatus]
entity 'HardwareStatus' status is 'ok' [instance = HardwareStatus]
entity 'Minus12VPowerSupply' status is 'n/a' [instance = Minus12VPowerSupply]
entity 'OverCurrentState' status is 'atsCurrentOK' [instance = OverCurrentState]
skipping entity section PhaseSyncStatus instance.
entity 'Plus12VPowerSupply' status is 'n/a' [instance = Plus12VPowerSupply]
entity 'RedundancyState' status is 'atsFullyRedundant' [instance = RedundancyState]
entity 'SourceAStatus' status is 'ok' [instance = SourceAStatus]
entity 'SourceBStatus' status is 'ok' [instance = SourceBStatus]
entity 'SwitchStatus' status is 'ok' [instance = SwitchStatus]
entity 'VBoostSourceA' status is 'atsPowerSupplyOK' [instance = VBoostSourceA]
entity 'VBoostSourceB' status is 'atsPowerSupplyOK' [instance = VBoostSourceB]
entity 'VoltageOutStatus' status is 'fail' [instance = VoltageOutStatus]
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: 2025-01-02 03:25 AM
The NMC should be able to provide verbose (extended detailed) logs. Specifically it should have captured any changes to the OID’s / MIB’s since the firmware update.
If you revert back to the original firmware what are the results seen on the PDU?!? My expectation is the error / fault goes away let me know.
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.