Loading ...
Home » Spaces » UPS Management Devices & PowerChute Software » discussion » General » PowerChute Network Shutdown 4.2.0 Build 6729 Shuts Down Host OS following Reboot?

PowerChute Network Shutdown 4.2.0 Build 6729 Shuts Down Host OS following Reboot?

Discussion in UPS Management Devices & PowerChute Software started by Martin , 20 days ago
Login to follow, share, and participate in this space.
Not a member?Join now
  • schultzy
    Martin
    New Member New Member
    Martin 20 days ago

    We have an HP Proliant Server that is used to host a Hyper-V Virtualised System.

    I have just installed updates on 4 Windows Guests and successfully rebooted each in turn to complete the upgrade process.  BUT I had a problem with the Host OS (Windows 2008 R2) - following the upgrade I got the following events in the event log followed by a shutdown;

    09/29/2017 22:50:56 Available runtime has been exceeded.
    09/29/2017 22:50:56 Communication has been established.

    There are no events on the UPS Network Management Card 2?

    This is the third system I have had this problem with.

    Does anyone have a solution to this problem other than to disable the "Available runtime has been exceeded" event?
     

  • wpasquil
    Bill
    =S= Representative
    Bill 18 days ago (in response to Martin)

    Hi,

    Sorry for the inconvenience. Available runtime has been exceeded is discussed on page 78 of the PowerChute Network Shutdown Hyper-V User's Guide. http://www.apc.com/salestools/PMAR-9E5LP4/PMAR-9E5LP4_R3_EN.pdf?sdirect=true

    In Schneider Electric FAQ FA241713 "PowerChute Network Shutdown reports "Available runtime has been exceeded" and by clicking on help in the PowerChute web interface.

    I cannot be sure with out seeing he pcnsconfig.ini and the NMC config.ini however in 99% of cases you need to increase the low battery threshold in the NMC to be 2 minutes greater that need needed time for PowerChute to shutdown the OS. The NMC ships with the low battery threshold default of 2 minutes PowerChute needs a minimum of 4 minutes (greater when powering down VMs) so by increasing the low battery threshold in the NMC to 4 minutes the error will be resolved. 

    Below is the text from the FAQ

    Issue:
    PowerChute Network Shutdown reports "Available runtime has been exceeded". and or PowerChute shuts down OS due to "Available runtime has been exceeded"

    Product:
    PowerChute Network Shutdown versions 3.1, 4.x

    Environment:
    All supported OS

    Cause:
    Condition 1 for all configurations except VMware and Hyper-V:
    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.

    Condition 2 for all configurations except VMware and Hyper-V:
    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.

    For  conditions 3 and 4 below, the "total shutdown time" includes the following durations:

    • VM migration duration
    • VM shutdown and startup duration
    • vApp shutdown and startup duration
    • Shutdown command file 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)

    The event occurs with either of the following conditions:

    Condition 3 for VMware:
    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.

    Condition 4 for VMware:
    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.

    For conditions 5 and 6 below, the "total shutdown time" includes the following durations:

    • VM migration duration - Hyper-V only
    • VM shutdown and startup duration- Hyper-V only
    • Host Maintenance duration - SCVMM only
    • Shutdown command file 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)

    The event occurs with either of the following conditions:

    Condition 5 for Hyper-V:
    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.

    Condition 6 for Hyper-V:
    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.

    Solution:

    Condition 1 for all configurations except VMware and Hyper-V:
    Increase the Low Battery Duration value on the NMC using Configure - Shutdown or decrease the shutdown durations being used by PowerChute.

    Condition 2 for all configurations except VMware and Hyper-V:

    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.

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

    Condition 4 for VMware:

    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.

    Condition 5 for Hyper-V:
    Increase the Low Battery Duration value on the NMC using Configure - Shutdown or decrease the shutdown durations being used by PowerChute.

    Condition 6 for Hyper-V:

    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.

  • Page 1 of 1 (2 items)
Choose your language:  
powered by Communifire
Version 5.2.6420.11692