For both conditions below, the “total shutdown time” includes the following durations:

• VM migration duration

• VM shutdown and startup duration

• vApp shutdown and startup duration

• vCenter Server VM shutdown duration

• Disable vCLS duration

• Disable HA duration

• VM migration duration - Hyper-V only

• VM shutdown and startup duration - Hyper-V only

• Host Maintenance duration - SCVMM only

• AFS shutdown and startup duration - Nutanix only

• Abort Active Replications duration - Nutanix only

• Cluster shutdown and startup duration - Nutanix, HyperFlex, and Dell VxRail only

• Controller VM shutdown and startup duration - Nutanix and HyperFlex only

• OVC shutdown and startup duration - SimpliVity only

• Maintenance mode duration for Dell VxRail stretched cluster

• Shutdown command file duration

• SSH action duration

• Built-in duration of 2 minutes (this consists of a 10 second OS shutdown duration and a 60 second OS shutdown duration; rounded up)

This event occurs with either of the following conditions:

Condition 1.

When the total shutdown time required by PowerChute is greater than the Low Battery Duration minus two minutes configured for the UPS. In the event of a low battery condition, PowerChute will not have enough time to complete the shutdown sequence before the UPS powers off. For example, if the total shutdown time required is 3 minutes and Low Battery Duration is 4 minutes, the Available Runtime has been Exceeded event will be triggered.

Resolution: Increase the Low Battery Duration value on the NMC using Configure - Shutdown or decrease the shutdown durations being used by PowerChute.

Condition 2.

When the shutdown duration configured for the UPS On Battery event plus the total shutdown time required by PowerChute is greater than the Runtime Remaining on the UPS minus two minutes. This condition can be caused by having too great a load on the UPS when the battery is fully charged.

Resolution:

1. Remove some equipment from the UPS to increase the available runtime.

2. Decrease the shutdown duration time for the UPS On Battery event.

3. Decrease the command file execution time using the Shutdown Settings screen.

This event is logged and event actions are carried out even if it occurs on a single UPS in a Redundant or Parallel UPS configuration.

The UPS battery runtime has fallen below an acceptable range. If there is a power outage, a low battery condition will occur. This can be caused if the UPS has been operating on battery for an extended time period.

If a Battery Recharged event does not occur within four hours, the UPS may not be charging properly, please contact Schneider Electric Customer Support.

The UPS has switched to bypass due to an internal hardware problem or because the UPS is overloaded.

The UPS has switched to bypass and cannot protect the load if a power outage occurs. This is a normal condition if maintenance is being performed on the UPS.

If this event occurs when the UPS was not deliberately put into bypass, please contact Customer Support.

The bypass contactor is not operating properly. This will prevent the UPS from being placed in bypass or returning from bypass. Please contact Customer Support.

PowerChute lost communication while the UPS was on battery and cannot detect a Low Battery condition if the power outage continues. Graceful shutdown cannot be guaranteed.

This occurs when the UPS is on battery and:

• The Management Card cannot communicate with the UPS
  or
• PowerChute cannot communicate with the Management Card.

Network communication between PowerChute and the NMC has been lost. See Network Management Card Troubleshooting. This can occur during a firmware upgrade of the NMC.

The UPS has switched to battery operation due to a power outage. If you can’t restore power to the UPS, do the following:

1. If there is no general power outage (i.e. if only this UPS has lost input power), check the building wiring and circuit breakers.

2. If this event occurs occasionally and briefly, check to see if equipment on the same electrical circuit as the UPS uses high power periodically.

3. This event can also be caused by poor power quality (i.e. power fluctuation). Decrease the sensitivity of the UPS through the NMC user interface.

4. If the condition persists, contact an electrician to analyze your utility power.

The load on your UPS has exceeded the maximum load threshold, set in the NMC user interface. Reduce the load on the UPS or upgrade to a device that can support the existing load.

The UPS has too great a load or there are not enough power modules operational to support the desired redundancy.

Check to see that all power modules are functioning properly and that the redundancy configuration is correct.

If the condition persists, contact Customer Support.

The system has too great a load or there are not enough operational UPS’s to support the desired redundancy level.

Check to see that all UPS’s are functioning properly and that the redundancy configuration is correct.

If the condition persists, contact Customer Support.

The runtime remaining has dropped below the configured threshold while on battery. You can configure this threshold using the shutdown action on the Configure Events page.

When the UPS in running on battery power and the runtime remaining on the UPS drops below the threshold, PowerChute will trigger a shutdown sequence. See “Sequenced Server Shutdown” for more information.

The UPS’s internal temperature is too high. Make sure that there is at least one inch of clearance around the UPS, and that the UPS ventilation ports are not blocked. If this condition is not resolved quickly, damage may occur to your UPS.

The UPS has sensed a load greater than 100 per cent of its rated capacity. Remove attached equipment from the UPS until the condition is corrected. If this condition happens occasionally and briefly, check to see if some equipment connected to the UPS is using high power periodically (e.g. connected laser printers or photocopiers). If the condition persists, contact Customer Support.