Notification - Cannot change default interval on battery replacement warning

[nt4workstation]

Where can I find the data point to change the SNMP Trap Interval from 10 minute default to 720 minutes?

Cannot find under

Configuration > Notifications > Event Action > By Event > Battery > Warning

There's a long list under Critical, but no matches.  

Under Warning there are only

Warning	Event Log	E-mail	Trap
UPS: Battery near end of life. Order replacement battery.	•		•
UPS: Battery measured life near end. Order replacement battery.	•		•

The event log text is:

Date	Time	Event
2025-09-02	18:10:55	UPS: Battery needs replacement. Order replacement battery, APCRBC140, for the internal pack, cartridge 1.

SNMP manager is forwarding this text with the trap:

Any Trap PassiveMonitor.Payload.TrapName=enterpriseSpecific PassiveMonitor.Payload.TrapMajor=6 PassiveMonitor.Payload.TrapMinor=17 PassiveMonitor.Payload.mtrapargsString.0=UPS: Battery needs replacement. Order replacement battery, APCRBC140, for the internal pack, cartridge 1. PassiveMonitor.Payload.ObjectLong=1.3.6.1.4.1.318 (apc) PassiveMonitor.Payload.Object=apc PassiveMonitor.Payload.Timetick=-91days -20:-54:-22.-31 PassiveMonitor.Payload.Packet Type=Trap PassiveMonitor.Payload.1.3.6.1.4.1.318.2.3.3.0=UPS: Battery needs replacement. Order replacement battery, APCRBC140, for the internal pack, cartridge 1. PassiveMonitor.Payload.Protocol Version=SNMPv1 PassiveMonitor.Payload.CommunityName=x Device.Address=10.x.x.x PassiveMonitor.DisplayName=Any Trap PassiveMonitor.Payload.TrapName=enterpriseSpecific PassiveMonitor.Payload.TrapMajor=6 PassiveMonitor.Payload.TrapMinor=17 PassiveMonitor.Payload.mtrapargsString.0=UPS: Battery needs replacement. Order replacement battery, APCRBC140, for the internal pack, cartridge 1. PassiveMonitor.Payload.ObjectLong=1.3.6.1.4.1.318 (apc) PassiveMonitor.Payload.Object=apc PassiveMonitor.Payload.Timetick=-91days -20:-54:-22.-31 PassiveMonitor.Payload.Packet Type=Trap PassiveMonitor.Payload.1.3.6.1.4.1.318.2.3.3.0=UPS: Battery needs replacement. Order replacement battery, APCRBC140, for the internal pack, cartridge 1. PassiveMonitor.Payload.Protocol Version=SNMPv1 PassiveMonitor.Payload.CommunityName=

[nt4workstation]

The workaround I found was to set ALL battery notifications to 12 hours.  But then I have to go back and change the critical battery notifications to 2 minutes, 10 minutes, etc.  Not really a solution since I need to know if the unit is going on battery, batteries getting low and so on, more frequently than every 12 hours.  

[Teken]

Given you haven’t provided any real specific information as to the APC UPS besides the RBC.

I’m going to assume this is a SRT / SAU / SURT?!? If this is a SRT you can change the battery health / sleep alarm in (days) from the defaults of 183 / 14 to whatever within the defined limits.

Once that has been set you can define an alert interval that suits your needs in most NMS. 

All I want to know is how long the RBC has been in place (installed date) and when it’s coming due. Than, I / We can place an order with enough lead time for a RBC replacement to arrive.

This balances cost, storage, and having fresh cells for the longest service life. Regardless of any notification any serious Enterprise installation would be following well defined SOP for monthly / annual maintenance and inspection of the system and RBC.

The NMS would provide at a glance, live, and historical state of health regardless of any notification. The same data would be pushed / pulled to a SysLog Server for fail over and verbose logging if available.

Questions Ask . . . 👍

[nt4workstation]

Thanks for your response ...

Sorry about that, I forgot to give specifics.  The current case is an SRT5KXLT with the built-in 0N-1557 NMC.  However I've had this issue with any of the "newer" UPSs with 9640 cards as well.  There must be a good reason they default a battery replacement to 10 minutes but it's beyond me.  

How does one acknowledge an alarm?  "Battery Health Alarm Sleep Time" is defaulted to 14 days as you correctly noted.  It says I can set -1 for " never remind Once acknowledged."  Not that I'd do that, but, the concept of acknowledgment is not something I'm familiar with for the UPSs we have.  

Sounds like you're saying there's no way to change that interval individually within the web GUI.  

I'd love to say that we are a "serious Enterprise installation" but we tend to be under-resourced in all aspects.  I would love to have somebody to go to who can properly manage our NMS but what I get is access and "Check the online help."

Typically I wait until I need a pallet-quantity of batteries, place an order, and install them all immediately on receipt.  I've tried ordering in advance but managing and charging stock is not something I can do well with the limited resources available.  

This notification is not a typical replacement interval due to high duty cycle & deep discharge related to power problems in a new building ... and effects of Covid 19 etc. on supply chain.  The "expected" replacement date is August 2027 but here we are.  

[Teken]

Based on your feedback it seems you’re working in the *A Typical* network environment where IT is at the bottom of resources, finances, and staffing.

As noted up above the two settings can be defined in days to be alerted of a pending EOL RBC.

The entire concept is local in your face alert notifications which needs to be physically acknowledged. In parallel to receive the same information via SNMP / email.

A properly setup NMS will empower and enable an individual / team to monitor, track, and recall historical events relating to power management in this case the UPS.

Im unclear what you mean you have access to the NMS but (Check online help) ?!?!

Regardless of all the above this is what a ISO certified enterprise does to insure compliance and reduce downtime.

RBC: All RBC upon receipt are fully inspected internally / externally. This encompasses all wiring, connectors, fuse, sensors, chips if applicable.

The production date of the RBC is documented.

Initial voltage is recorded and than allowed to be fully charged for 72 hours. The RBC is than measured for conductance and internal resistance and compared to the battery makers data sheet and recorded.

Upon RBC deployment and insertion the installation date is affixed to the front of the RBC. The UPS is updated with the month and year and validate the same information is received by the various NMS.

A self test is manually initiated and once complete allow the RBC to return to 100% SOC.

This is followed by manually initiating a battery calibration with at least 30% connected load. Once complete allow the RBC to return to 100% SOC.

This insures the displayed and calculated operational runtime is as accurate as possible and reflected on the LCD, NMC, and SNMP connected NMS.

All of the data listed up above is logged in physical binders at the UPS. The same data is entered into several online tools to allow local / global tracking.

Notification and reminders span simple calendars, spreadsheets, to global tracking systems that schedule maintenance windows for all the above.

Once these basic tasks have been completed both static & dynamic validation tests are performed on all power delivery systems during a Lights Out / Grid Down event.

All of the above are timed, tracked, and documented and compared to a minimum rolling 12 month life cycle.

During both lights out / grid down validation tests the power output is measured with calibrated and certified meters to affirm voltage, frequency, THD, sine wave are within expected range.

Especially during a transfer to generator power. All ATS & Manual Transfer (Maintenance) switches are timed and tracked for proper operation.

As part of the Lights Out validation on an annual inspection all ATS / UPS are subjected to both high / low input voltage using a 120 / 240 variacs.

This allows us to validate both ATS & UPS react and operate correctly in both AVR and battery only mode when a voltage sag (brown out) or voltage rise (surge) is present.

The same tests are conducted for frequency and THD. To validate and confirm both ATS / UPS are capable of operating within the grid vs generator power output provided.

All of the above is simply established process and conducting the same at defined intervals and documenting the data.

Action items are scheduled, completed, documented, and life goes on . . . 👍

All the above can be done by anyone at any scale whether it be a DIY Home Lab to fill on ISO Certified Enterprise. 

Everyone started off with a note pad and sticky note! In 2025 using available technology like simple Outlook / Google calendar for scheduling & reminders work.

If you or people want to get fancy there are dozens of options to use. Comes down to ease of use and willingness to execute these tasks on a consistent basis to ensure the most important part of the network infrastructure is always 100% operational!

Questions Ask . . . 👍