Go to APC Homepage PowerChute Network Shutdown
Online Help
 
Help Topics
Note: After clicking on a link directly below, press the Back button on your Web browser to return to these Help Topics. Alternatively, press the Ctrl + Home keys.

Server Information

 
UPS Information

List of Events

APC Customer Support

 
Event Log

This log displays, in chronological order, the UPS events that PowerChute Network Shutdown has recognized. The log is for the individual computer on which it resides only.

PowerChute Network Shutdown logs only those events that may affect the operation of the equipment powered by the UPS (not, for example, events related to UPS self-tests and runtime calibrations). Use the Network Management Card user interface to see all of the events that have occurred at the UPS.

See the List of Events for descriptions of the events that are recognized by PowerChute Network Shutdown and can be recorded in the Event Log. Not all events are supported by every UPS model.

By default, event logging is enabled for all events. To disable logging of an event, use the Configuring Events to Take Actions function.

The EventLog.txt file is in the PowerChute directory. When this file size reaches 1000 events, the oldest third of the file is deleted. To completely clear the Event Log, you must stop the PowerChute process, delete the EventLog.txt file, then restart the PowerChute process. PowerChute Network Shutdown creates a new file the next time it records an event.

 
Configuring Events to Take Actions

Using the Configure Events page, you can configure PowerChute Network Shutdown to take certain actions when a UPS event occurs. Here are the possible actions (some are not available depending on your configuration):

The Configure Events page summarizes which actions are configured for each event. For more details on a configured action, select the check box for that action.

Below are the events that can be configured. This table specifies the text for events listed on the Configure Events page. Note that this text is sometimes a little different from that which displays for the same event in the Event Log. Click on an event below to see the Event Log descriptions and further explanatory text listing causes and resolutions.

 
Account Locked Out for xxx.xxx.xxx.xxx Battery: Discharged Battery: Installed
Battery: Recharged Battery: Removed Battery: Replaced
Battery: Replacement Needed Bypass: Ended Bypass: For Maintenance
Bypass Switch: Failed Bypass Switch: Replaced Bypass: Overload Bypass
Communication: Established Communication: Lost while on Battery Communication: Management Card cannot communicate with the UPS
Communication: PowerChute cannot communicate with the Management Card Environment: Contact Zone X Alarm Environment: Contact Zone X Normal
Environment: Humidity Probe X In Range Environment: Humidity Probe X Out Of Range Environment: Temperature Probe X In Range
Environment: Temperature Probe X Out Of Range Environmental Monitoring Card: Communication Established Environmental Monitoring Card: Communication Lost
Input Power: Restored Manual Bypass has been started Minimum Load Capability: Lost
Minimum Load Capability: Restored Minimum Redundancy: Lost Minimum Redundancy: Restored
Runtime: Exceeded Runtime: Normal Again SmartBoost: Activated
SmartTrim: Activated System-Level Fan: Failed System-Level Fan: Replaced
UPS Module: Failed UPS Module: Installed UPS Module: Removed
UPS Module: Repaired UPS: On Battery UPS: Overloaded
UPS Overload: Corrected UPS Temperature: Overheated UPS Temperature: Normal Again

 

Log Event Action

By default, PowerChute Network Shutdown records a supported event in the PowerChute Event Log when that event occurs. Disable logging for events that you do not want recorded.

 
Notify Users Action

PowerChute Network Shutdown can send a broadcast message to one user or all users when an event occurs. (This is not available under Windows Vista as it does not support the messenger service).

Use the following parameters to configure how broadcast messages are sent:

Send notification only when the event(s) last this long (seconds): The time, in seconds, that the event must persist before the first message is sent. For example, if short power failures occur frequently, you may not want to receive messages about each one. If you set this notification delay time to 10 seconds for the UPS On Battery event, you receive a message only if a power failure lasts at least ten seconds.

Send notification again this often (seconds): The time interval, in seconds, at which the message will be repeated while the event condition exists. If this field is blank or zero, the message will not be repeated.

Notify all users: The message will be sent to all users who are on the same domain (Windows) or who are logged into the server (Linux, VMware, Solaris, NetWare).

Notify only this user: Specify the network broadcast address of the user to notify. This name must be an individual user name, not a group name.
  • On Windows, enter the machine name.
  • On Linux, VMware, UNIX, and Mac OS X, enter the user name (that is, the login name, for example, tomw).
  • On NetWare, enter the fully-resolved NDS name (for example .don.sales.myc). The leading period is required for NDS user names only. For a user connected via the bindery instead of NDS, use only the user’s common name (for example don).
 
Run Command File Action

PowerChute Network Shutdown can execute a command file when an event occurs. (On Windows, the file must be a .cmd or .bat file; on NetWare it must be a .nlm file.) You must specify the full path name of the command file, including the disk drive or volume name. If any element of the path name contains spaces, enclose the full path name in quotation marks.

Use the following parameters to configure when the command file runs and to ensure that sufficient time is available for it to run:

Run the command file only when the event lasts this long (seconds): The time, in seconds, that the event must persist before the command file is started. For example, you may want the command file to execute only if a power failure lasts for at least 60 seconds. If you set the Command Execution Delay time to 60 seconds for the UPS On Battery event, the command file will not run if the power failure is shorter than 60 seconds.
The command file needs this much time to complete (seconds): The time, in seconds, that the command file requires to complete its execution. If you are running a command file for the UPS: On Battery event, PowerChute Network Shutdown periodically checks the amount of runtime that is available from the UPS. If the delay time for your command file, plus the time configured to shut down the server, exceeds the amount of runtime that the UPS has available, the Run Time Exceeded event occurs.

Note: On Windows, the command file must use the @START command to run executable programs, and use the full path name of the program. Path names that include spaces must be enclosed in quotation marks. Any arguments for the executable must be outside the quotation marks.  For example, if you run HyperTerminal and Backup in your command file, use the syntax:

@START "c:\Program Files\Windows NT\hypertrm.exe" arguments
@START c:\Winnt\system32\backup  arguments

 

Shutting Down Utilities in Windows

For Windows, utilities are provided to shut down some common applications. They are located in the Shutdown utilities sub-directory of the installation directory. By default, that location is:

C:\Program Files\APC\PowerChute\group1\Shutdown utilities
 
Note: group1 becomes group2 and group3 in non-primary installations of a Multiple-PCNS instance configuration. See Multiple-UPS configuration in the Installation help.

The Shutdown utilities directory contains the following DLLs:

  • ShutdownIIS.dll - To shut down Microsoft® Internet Information Services (IIS®)
  • ShutdownNotes.dll - To shut down IBM® Lotus® Notes®/ DominoTM
  • ShutdownSiebel.dll - To shut down SiebelTM eBusiness Applications
  • ShutdownSQL.dll - To shut down Microsoft® SQL ServerTM
  • ShutdownExchange.dll - To shut down Microsoft® Exchange Server

To use the shutdown DLL utilities, do the following:

  1. Include the following line (using the full path name) in a command file with any other commands that you want PowerChute Network Shutdown to execute before shutting down the operating system.
    @START /D"installation dir\Shutdown utilities" appshut DLL name

    So, for example to shut down Microsoft IIS from the default installation directory:

    @START /D"C:\Program Files\APC\PowerChute\group1\Shutdown utilities" appshut ShutdownIIS.dll
  2. Select an event, select run command file, and enter the path to the command file you created with the above line.
 
Shut Down System Action

If this action is enabled for an event, PowerChute Network Shutdown (PCNS) causes the server operating system to shut down when the event occurs. That is, the event is treated as critical. (This action cannot be enabled for every event.)

Delay Time (in seconds) before starting shutdown: Enter the time, in seconds, that the event must persist before the shutdown is started. For example, you may want to shut down the operating system only if a power failure lasts for at least ten minutes. If you set the Delay Time to 600 seconds for the UPS On Battery event, the shutdown will not start if the power failure is less than 600 seconds (10 minutes) in duration.

Use the Configure Shutdown page to specify details about how the system will shut down.

Critical Events and Multiple-UPS or Parallel Silcon UPS configurations
For Multiple-UPS or Parallel Silcon UPS configurations, PCNS always considers the following as critical events: a) a low battery condition, or b) a UPS off condition, or c) any event with the Shut Down System action enabled on the Configure Events page.

Please note the following for critical events for these configurations.

  1. Two different critical events (such as UPS: On Battery and PowerChute cannot communicate with the Management Card) occurring in succession on two UPSs cause a shutdown. The shutdown is initiated after the critical event state expires in 10 seconds; that is, no configured delay time is counted down.
     
  2. Two identical critical events (such as UPS: On Battery) occurring in succession on two UPSs also cause a shutdown but any configured delay time is counted down first.
     
  3. However, two Low Battery OR two UPS off events occurring in succession on two UPSs cause an immediate shutdown initiation (after the critical event state expires in 10 seconds). This is because no configured delay is possible with these events.
 
Turn Off UPS Action

If this action is enabled for an event, PowerChute Network Shutdown causes each UPS in a Multiple-UPS configuration to turn off when the event occurs. (This action cannot be enabled for every event.) You can also configure the turn off to occur only when the event lasts a specified time span.

For background information, see Multiple-UPS configuration and Multiple-PCNS Instances in a Multiple-UPS configuration in the Installation help.

 

Configure Shutdown

If you configure any PowerChute events to shut down your system, use the Configure Shutdown page to customize how your operating system will shut down. You can configure PowerChute Network Shutdown a) to notify users, b) to run a command file before shutting down the operating system and c) to signal the UPS to turn off after the operating system shutdown. (See Configuring Events to Take Actions for details on configuring an event to shut down your system.)

Note: In a Multiple-UPS configuration, this page displays with the server name and only the notifying users and running command file functionalities are available. See also Turn Off UPS Action and for background information, see Multiple-UPS configuration in the Installation help.

Notifying Users: PowerChute Network Shutdown can send a broadcast message to one or all users when a shutdown occurs. Use the following parameters to configure how broadcast messages are sent:

  • Notify all users: The message will be sent to all users who are on the same domain (Windows) or who are logged into the server (Linux, VMware, Solaris, NetWare).
     
  • Notify only this user: Specify the network broadcast address of the user to notify. This name must be an individual user name, not a group name.
     
  • Send notification again this often (seconds): The time interval, in seconds, at which the message will be repeated while the event condition exists. If this field is blank or zero, the message will not be repeated.
     
    • On Windows, enter the machine name.
    • On Linux, VMware, UNIX, or Mac OS X, enter the user name (that is, the login name, for example, tomw).
    • On NetWare, enter the fully-resolved NDS name (for example .don.sales.myc). The leading period is required for NDS user names only. For a user connected via the bindery instead of NDS, use only the user’s common name (for example don).

Run this command file (full name): You must specify the full path name of the command file, including the disk drive or volume name. See Run Command File Action and Shutdown Utilities Action for information on using command files to shut down applications that are running on your system.

The command file needs this much time to complete (seconds): Enter the number of seconds that the command file requires to complete its execution. PowerChute Network Shutdown will wait this much time before ordering the operating system to shut down, even if no command file is specified. The time you specify is in addition to the delay used by the event that causes the shutdown. If the system is shutting down due to a power failure, PowerChute Network Shutdown periodically checks the amount of runtime that is available from the UPS. If the UPS cannot support its attached equipment for the amount of time that you have configured, the Run Time Exceeded event occurs.

Note: You must determine the time required for your command file to execute. PowerChute Network Shutdown cannot determine whether the command file has completed, so it will wait only the amount of time that is entered on this page before ordering the operating system to shut down.

Turn off the UPS when the shutdown finishes: If you have more than one server connected to your UPS, you might not want PowerChute Network Shutdown to turn off the UPS after the operating system is shut down. Clear the check box to prevent this server from ordering the UPS to turn off. This feature is disabled for a Parallel Silcon series UPS; a Parallel Silcon series UPS cannot be turned off through PowerChute.

Note: The Network Management Card will not allow the UPS to turn off until all of the servers running PowerChute Network Shutdown have completed their shutdown activities.

Your operating system shutdown follows this sequence:

  1. The On Battery Event initiates the Event Delay Time. Before initiating a shutdown, PowerChute Network Shutdown will wait the amount of time configured by the user for the Shut Down Server action, on the Configure Events page.
  2. The Command File Starts. When the Run Command File action has been configured by the user on the Configure Events page and the Configure Shutdown page, the specified command file executes.
  3. The operating system shuts down. The operating system will begin a graceful shutdown when the Event Delay Time and the Command File Runtime have expired.

  4. UPS Shutdown Begins. The UPS initiates its shutdown. It waits the amount of time indicated by one of the following, whichever is greater:

    • Low battery duration: Configure this value in the Network Management Card Web user interface.
      UPS tab —> Configuration-shutdown —> Low Battery Duration value (in minutes).
    • Shutdown Command File Runtime: Configure this value in PCNS at the Configure Shutdown page. The command file needs this much time to complete (seconds).
  5. A 2-minute delay. This is built-in and cannot be changed by the user.
  6. UPS Reboot sequence starts. The reboot sequence starts before the UPS shuts down. This prepares the UPS to continue the reboot sequence when power is restored.
  7. Shutdown Delay. Configure this value at the Network Management Card user interface.
    UPS tab —> Configuration-shutdown —> Shutdown Delay.
  8. Turn Off. Power is turned off.

You can configure the UPS to automatically turn on or to require a manual turn-on when power returns after a power failure. (An automatic turn-on will restart the equipment that the UPS is supporting). Set this parameter in the Network Management Card user interface by using the On-Battery Shutdown Behavior field under the UPS tab in PowerChute - configuration.

 
Configuring a Silcon to Turn Off

Some events like a low battery are set up to automatically shut down the system turn off the UPS. However, with a single Silcon, you must perform the following steps to facilitate the Silcon turning off.

  1. Use a serial cable to connect your computer to the Network Management Card.
  2. Start a terminal emulator, such as HyperTerminal, on your computer.
  3. Log on to the Network Management card.
  4. Select Device Manager on the terminal window.
  5. Select a device listed in Device Manager, for example, Silcon DP310E.
  6. Type yes to accept remote turn off commands.
Set Up Communications
The following two sections, Web/ SSL and Network Management Card deal with the fields on this page and relate to the server whose name displays on the menu and in the top right corner of the page.
 
Web/ SSL
The Protocol Mode field value can toggle between HTTP and HTTPS (SSL) for your Web user interface. If you change the value, it comes into effect after you restart PowerChute Network Shutdown (PCNS).

The following lists the six possible communication "ports" used by the PCNS Web user interface when using a Multiple-UPS configuration with Multiple-PCNS instances functionality (see Multiple-UPS configuration in the Installation help). In the list, host represents the IP address of the Network Management Card.

    The usage with http is:
     
  • Instance 1:  http://host:3052
  • Instance 2:  http://host:2161
  • Instance 3:  http://host:2260

  •  
    The usage with https is:
     
  • Instance 1:  https://host:6547
  • Instance 2:  https://host:6548
  • Instance 3:  https://host:6549
 
Network Management Card

Network Management Card IP Address: the network address of the APC Network Management Card (NMC) in your UPS. To change this setting, use the Configuration Utility. If you are using a Multiple-UPS configuration, the IP addresses of the NMC cards entered during installation display; for a Parallel Silcon UPS configuration, only the address of the first NMC displays.

Administrator User Name: this name is used when you log on to the PowerChute Network Shutdown (PCNS) user interface; it is also used to authenticate communications between the NMC and PCNS. The User Name must be no more than ten characters long. If you change this user name, you must also change it for the NMC, otherwise, PCNS and the NMC will not be able to communicate. If you are using a Multiple-UPS or a Parallel Silcon UPS configuration, all of the NMC user names in the UPS system must be the same.

Note: If you try to log on without success three times, then the system locks out the account and you will have to wait two minutes to try again.

Administrator Password: used when you log on to the PowerChute Network Shutdown user interface, the Password must be no more than ten characters.

Administrator Authentication Phrase: used by PCNS to communicate with the NMC, the Authentication Phrase must be at least 15, but no more than 32, characters. If you change this Authentication Phrase, you must also change it for the NMC, otherwise, PCNS and the NMC will not be able to communicate. If you are using a Multiple-UPS or a Parallel Silcon UPS configuration, all of the NMC authentication phrases must be the same.

Note: You must set the administrator user name and authentication phrase for the Network Management Card to be the same as those used by PowerChute Network Shutdown. Set these parameters in the Network Management Card user interface:
a) For user name: Administrator tab - Security - Local Users - administrator - Administrator page
b) For authentication phrase: UPS tab - PowerChute - configuration - PowerChute Shutdown Parameters page.

Note: The Synchronization option in the NMC should be disabled.

 
PowerChute Network Shutdown Configuration Utility

The PowerChute Network Shutdown Configuration Utility is a stand-alone utility and is not part of the main user interface. The Configuration Utility allows you to change various PowerChute Network Shutdown settings, including the IP address and port number of the Card, the Administrator user account and password, and the security phrase.

For information on the command line to use for your operating system to run the Configuration Utility and on how to use the utility for silent installations, see the section Using the PowerChute Network Shutdown Configuration Utility in the Installation help.

 

Advanced Configuration of Multiple-UPS Configurations

If PowerChute Network Shutdown monitors a Multiple-UPS configuration (that is, configurations of multiple Smart-UPS devices or multiple Symmetras), the Advanced Configuration page displays under the server name in the user interface.

Using this page, you can tell the system to turn off a UPS that has gone on battery and you can specify a delay time before this occurs.

When the UPS switches to battery power, this is logged, together with the IP address of the UPS, and the specified delay time starts to count down. Next, the UPS counts down its own turn-off delay, and then actually turns off (to go into sleep mode). For a graphic representation of the UPS shutdown, see shutdown timeline, specifically the bottom bar. Explanatory text precedes the graphic. When the AC utility power is restored, the UPS reboots automatically.

Before enabling this setting, make sure that the server and any network devices (like a HUB, or a router) are not connected to the UPS or they will be turned off also.

Note: When two UPSs in a Multiple-UPS configuration go on battery simultaneously, or even if one goes on battery while another is counting down its specified delay time, then neither UPS is turned off.

Note: The operating system does not shut down with Multiple-UPS configuration functionality. For background information, see Multiple-UPS configuration in the Installation help.

 
UPS Model Name (link to Network Management Card user interface)

Access the Management Card user interface by selecting the model name of your UPS in the UPS Information section. This will open a new Web browser window. You must enter your Network Management Card Administrator User Name and Password to access the user interface.

Note: If your Network Management Card has firmware revision 1.2.0 or later, be sure that the Synchronization option is disabled.

If you have Multiple-UPS or a Parallel Silcon UPS configuration, all the Network Management Card IP addresses registered during the installation are listed in the Multiple UPS menu command under UPS information. Selecting one will launch the user interface.

 
Connected Servers

The Connected Servers page provides a list of the servers that have IP addresses registered with the Network Management Card. This list can contain up to 50 servers.

The server name and the IP address are displayed for each server. Select the IP address of a server to open the PowerChute Network Shutdown user interface for that server (in either a new window or a new tab in your Web browser). You must enter the Administrator User Name and Password for this server to access the user interface.

 
Interactive Assistance
Use the Interactive Assistance link to the APC support page to search the Knowledge Base or submit a question via email.
 
System Problem Report
You will receive a System Problem Report message in response to a menu selection if PowerChute Network Shutdown is not able to get information from the Network Management Card. During normal operation, an error of this type may occur occasionally due to network traffic or to other processing by the Network Management Card. Try the menu selection again.

If the problem continues, perform the same troubleshooting steps described for the PowerChute cannot communicate with the Management Card event.

 
List of Events
This section lists all events that are written to the Event Log. Some of these events can be configured through the Configuring Events to Take Actions page, and these are listed in the first section directly below, Configurable Events. Others cannot be configured and are listed in a second section.
 
Configurable Events
The column at left specifies the actual text used in the Event Log. Note that this is sometimes a little different from the text on the Configuring Events to Take Actions page.

All events occur for both single and Multiple-UPS and Parallel Silcon configurations. The Event Log text (on left) is almost identical for both configurations but for Multiple-UPS and Parallel Silcon configurations, the text will in many instances use the plural form, e.g. UPSs instead of UPS.
 

Event Text Event Description

Account is locked out for xxx.xxx.xxx.xxx. On the Web page, this displays as GUI: Account is locked out for xxx.xxx.xxx.xxx.
 
Ambient Temperature In Range Probe X One of the temperature probes on the Environmental Monitoring Card has detected a return from abnormal to normal temperature. You can change the temperature thresholds for this probe using the Network Management Card user interface.
This event is logged and event actions are carried out with a single occurrence even if it occurs on only one Network Management Card on a Multiple-UPS or Parallel Silcon configuration.

 
Ambient Temperature Out Of Range Probe X One of the temperature probes on the Environmental Monitoring Card is detecting an abnormal temperature. Check for a problem in the location monitored by this probe. You can change the temperature thresholds for this probe using the Network Management Card user interface.
This event is logged and event actions are carried out with a single occurrence even if it occurs on only one Network Management Card on a Multiple-UPS or Parallel Silcon configuration.

 
Available runtime has been exceeded The UPS does not have the runtime available that is configured in PowerChute Network Shutdown. Two configuration conditions can cause this event:
  • When the command file time on the Configure Shutdown page plus 10 seconds is greater than the Low Battery Duration field value. (A low battery condition always causes a shutdown, so when it occurs the UPS must have enough time available to complete shutdown activities). To fix this, either decrease the command file time, or increase the Low Battery Duration value. (To change the Low Battery Duration, on the Network Management Card user interface select the UPS tab and Configuration - shutdown).
  • When the UPS runtime is less than the sum of the shutdown delay time configured for the UPS: On Battery event plus the command file time on the Configure Shutdown page, minus two minutes. This condition can be caused by having too much load on the UPS, or by the UPS batteries not being fully charged. If the UPS batteries are fully charged, to fix this a) remove some equipment from the UPS, or b) decrease the shutdown delay time for the UPS: On Battery event, or c) decrease the command file execution time on the Configure Shutdown page.

This event is always logged and, on a Multiple-UPS configuration, event actions are carried out even if it occurs on only one Network Management Card.
 

Available runtime is sufficient The available UPS runtime will support the PowerChute Network Shutdown configuration. This event occurs only after a Run Time Exceeded event.
 
Battery has been installed A battery module has been added to your Symmetra, or an external battery pack has been added to the Smart-UPS or Matrix-UPS.
 
Battery has been removed A battery module has been removed from the Symmetra, or an external battery pack has been removed from the Smart-UPS or Matrix-UPS.
 
Battery has been replaced A UPS battery has been replaced. This event occurs only if the Battery Replacement Needed event has occurred and the battery has been replaced.
 
Battery has recharged The battery charge of the UPS is within an acceptable range. This event occurs when a Battery Discharged or a Low Battery event has occurred.
 
Battery is discharged The UPS batteries are discharged. If power fails, a low battery condition will exist immediately. Sufficient runtime cannot be guaranteed. This event can occur if the UPS has recently been operating on battery power for a long time. If a Battery Recharged event does not occur within four hours, the UPS may not be charging properly; contact APC Customer Support.
 
Battery replacement is needed A UPS battery needs to be replaced. See the APC Web site for information on ordering a replacement battery, or contact APC Customer Support.
Note: This condition means that the battery should be replaced as soon as possible. However, the battery has not yet failed and can still provide backup power.
 
Bypass ended: UPS has switched to On Line operation The UPS has returned from bypass. See Bypass has been started.
 
Bypass has been started The UPS has switched to bypass and will not support its load in a power failure. 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, contact APC Customer Support.
 
Bypass switch has been replaced The bypass contactor is operating properly.
 
Bypass switch has failed The bypass contactor is not operating properly. The UPS will not be able to support its load in a power failure if the UPS is in bypass. Contact APC Customer Support.
 
UPS output overload
Bypass has been started
The load on the UPS is too great and has caused it to go into bypass mode. Reduce the load.
 
Communication established with Environmental Monitoring Card PowerChute Network Shutdown is receiving data from the Environmental Monitoring Card.
This event is logged and event actions are carried out with a single occurrence even if it occurs on only one Network Management Card on a Multiple-UPS or Parallel Silcon configuration.

 
Communication has been established Communication between PowerChute Network Shutdown and the UPS has been established.
 
Communication has been lost while on battery PowerChute Network Shutdown lost communication while the UPS was switched to battery operation. Without communication, PowerChute Network Shutdown cannot determine how much runtime the UPS has available before the UPS will turn off (if the power failure continues).
This event registers when a) the UPS is on battery and the Management Card cannot communicate with the UPS event occurs or b) when the UPS is on battery and the PowerChute cannot communicate with the Management Card event occurs.

 
Communication lost with Environmental Monitoring Card PowerChute Network Shutdown has stopped receiving data from the Environmental Monitoring Card. Check to see that the Environmental Monitoring Card is firmly seated in its slot and has power; check to see that Environmental Monitoring Card information is accessible through the Network Management Card user interface. If communication with the Network Management Card has also been lost, correct that problem first.
This event is logged and event actions are carried out with a single occurrence even if it occurs on only one Network Management Card on a Multiple-UPS or Parallel Silcon configuration.

 
Contact X Alarm One of the contacts on the Environmental Monitoring Card is faulted. Check for a problem in the location monitored by this contact. You can reset the Alarm and Normal positions for this contact using the Network Management Card user interface.
This event is logged and event actions are carried out with a single occurrence even if it occurs on only one Network Management Card on a Multiple-UPS or Parallel Silcon configuration.

 
Contact X Normal One of the contacts on the Environmental Monitoring Card has returned from a faulted to a normal condition. You can reset the Alarm and Normal positions for this contact using the Network Management Card user interface.
This event is logged and event actions are carried out with a single occurrence even if it occurs on only one Network Management Card on a Multiple-UPS or Parallel Silcon configuration.

 
Humidity In Range Probe X One of the humidity probes on the Environmental Monitoring Card has detected a return from abnormal to normal humidity. You can change the humidity thresholds for this probe using the Network Management Card user interface.
This event is logged and event actions are carried out with a single occurrence even if it occurs on only one Network Management Card on a Multiple-UPS or Parallel Silcon configuration.

 
Humidity Out Of Range Probe X One of the humidity probes on the Environmental Monitoring Card is detecting abnormal humidity. Check for a problem in the location monitored by this probe. You can change the humidity thresholds for this probe using the Network Management Card user interface.
This event is logged and event actions are carried out with a single occurrence even if it occurs on only one Network Management Card on a Multiple-UPS or Parallel Silcon configuration.

 
Input Power has been restored: UPS has switched to On Line operation
 
The UPS is no longer running on battery power.
 
Management Card cannot communicate with the UPS Communication between the Network Management Card and the UPS has been lost. Make sure that the serial cable is properly connected, and that the Network Management Card is firmly seated in its slot.
This event is logged with a single occurrence and the IP address of the battery is always logged.

 
Manual Bypass has been started A user put a UPS into bypass mode directly through the UPS hardware.
 
Minimum load capability has been lost The load on your Symmetra has violated the minimum load threshold, set in the Network Management Card user interface. Make sure all load equipment is connected properly.
 
Minimum load capability has been restored The load on your Symmetra is no longer below the load threshold. This event occurs only after a Minimum Load Capability Lost event.
 
Minimum redundancy has been lost The Symmetra has too great a load, or too few operational modules, to support the desired redundancy. Check to see that all of the modules are functioning properly and that the redundancy configuration is correct. If the condition persists, contact APC Customer Support.
 
Minimum redundancy has been restored The Symmetra can now support the desired redundancy. This event occurs only after a Minimum Redundancy: Lost event.
 
Network Communication with address xxx has been lost A Network Management Card in your UPS is not communicating with PowerChute network shutdown. The DNS name or the IP address of the Network Management Card will be given. Perform the troubleshooting steps listed for the PowerChute cannot communicate with the Network Management Card event.
This event is logged with a single occurrence and the IP address of the battery is always logged.

 
PowerChute cannot communicate with the Management Card Network communication between PowerChute Network Shutdown and the Network Management Card in the UPS has been lost. Perform the following troubleshooting steps:
  1. Log on to the Network Management Card User Interface, select the UPS tab, and then select the PowerChute - clients menu item. If the server's IP address is not on the list of Network Shutdown client IP addresses, add it.
  2. Make sure that the Administrator User Name and Authentication Phrase are the same for PowerChute Network Shutdown and the Network Management Card.
  3. If your Network Management Card does not have a PowerChute menu item under the UPS model name, it is an older card that does not support PowerChute Network Shutdown. Most Network Management Cards can be upgraded by installing new firmware to provide PowerChute Network Shutdown support. Obtain the latest firmware from the APC Web site, or contact APC Customer Support.

This event is logged with a single occurrence and the IP address of the battery is always logged.
 

System-level fan has been replaced The internal fan is operating normally. This event occurs only after a Fan Failure.
 
System-level fan has failed The internal fan has failed. Check the fan for obstructions. If this condition is not resolved immediately, damage may occur to your UPS.
 
UPS enabling SmartBoost The UPS has enabled SmartBoost in response to low input voltage. If this event occurs frequently, decrease the Low Transfer Voltage of your UPS using the Network Management Card user interface. If the condition persists, contact an electrician to analyze your utility power.
 
UPS enabling SmartTrim The UPS has enabled SmartTrim in response to high input voltage. If this event occurs frequently, increase the High Transfer Voltage of your UPS using the Network Management Card user interface. If the condition persists, contact an electrician to analyze your utility power.
 
UPS has switched to battery power The UPS has switched to battery operation due to a power failure. Restore power to the UPS. If there is not a general power failure (that is, if only this UPS has lost input power), check building wiring and circuit breakers. If the UPS: On Battery event occurs occasionally and briefly, check to see if equipment on the same electrical circuit as the UPS uses high power periodically.
The UPS: On Battery event can also be caused by poor power quality (i.e. power fluctuation). Decrease the sensitivity of the UPS through the Network Management Card user interface. If the condition persists, contact an electrician to analyze your utility power.
This event is logged with a single occurrence and the IP address of the battery is always logged.

 
UPS has overheated which can cause damage 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.
 
UPS is no longer overheated The UPS's internal temperature has returned to an acceptable level. This event occurs only after a UPS has overheated event.
 
UPS Module has been installed A power module has been added to the Symmetra.
 
UPS Module has been removed A power module has been removed from the Symmetra.
 
UPS Module has been repaired A power module in the Symmetra is operating normally. This event occurs only after a Power Module Failed event.
 
UPS Module has failed A power module has failed in the Symmetra. Replace the power module, and contact APC Customer Support for repair or replacement of the failed module.
 
UPS output overload The UPS has sensed a load greater than 100 percent 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; this is typical of equipment such as laser printers and photocopiers. If the condition persists, contact APC Customer Support.
 
UPS overload condition has been corrected A condition that caused the UPS: Overloaded event to occur has been corrected.
 
 
 
Non-Configurable Events
All the events listed below are not configurable but they do appear in the Event Log.
 

These events occur for BOTH single and Multiple-UPS (Smart-UPS, Symmetra), and Parallel Silcon configurations.

Low-battery condition has occurred.

UPS turn off has been initiated.

PowerChute Network Shutdown version x started.

Shutdown process started. ‹OS name› will shut down soon.
An event has occurred for which the Shut Down System action is enabled, and the system has started to shut down. See Configuring Events to Take Actions for information about the Shut Down System action.
 
 

 
All the events below occur ONLY for Multiple-UPS (Smart-UPS, Symmetra) and Parallel Silcon configurations.

Multiple UPS turn offs have been initiated.

Network Communication with address xxx.xxx.xxx.xxx has been lost.
This event is always logged even if it occurs on only one Network Management Card.

The On Battery UPS turn off process started. UPS will turn off soon.

Management Card xxx.xxx.xxx.xxx can not communicate with the UPS.
The Event Log also records the name of the event as per the Configuring Events to Take Actions page: Communication: PowerChute cannot communicate with the Management Card. This event is always logged even if it occurs on only one Network Management Card.

Management Card xxx.xxx.xxx.xxx communication has been established.
The Event Log also records the name of the event as per the Configuring Events to Take Actions page: Communication: Established. This event is always logged even if it occurs on only one Network Management Card.

Parallel Silcon installations are not supported at address xxx.xxx.xxx.xxx

Multiple Critical Event occurred: ‹Event name›, ‹Event name›

UPS xxx.xxx.xxx.xxx is running on battery power.
This event is always logged even if it occurs on only one Network Management Card.

The On Battery UPS has switched to On Line operation.

UPS xxx.xxx.xxx.xxx has turned off.

The turned off UPS has switched to On Line operation.

Multiple UPS have turned off.

APC Customer Support
Customer support is available in any of the following ways:

Contact the APC representative or other distributor from whom you purchased your APC product for information on how to obtain local customer support.




Entire contents copyright © 2007 by American Power Conversion Corporation. All rights reserved. Reproduction in whole or in part without permission is prohibited. All trademarks, product names, and corporate names are the property of their respective owners and are used for informational purposes only.

npn-00209