Ambient Temperature In Range Probe X

Transcription

1 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 Non-Configurable Events. 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. The events occur for all configurations. The Event Log text (on left) is almost identical for both configurations but for Redundant- and Parallel-UPS configurations, the text will in many instances use the plural form, e.g. UPSs instead of UPS. Event Text Ambient Temperature In Range Probe X Event Description 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. Ambient Temperature Out Of One of the temperature probes on the Range Probe X 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. 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.

2 (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 Redundant- 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 recharged Battery is discharged 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. 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. Bypass ended: UPS has switched to On Line operation Bypass has been started The UPS has returned from bypass. See 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

3 this event occurs when the UPS was not deliberately put into bypass, contact APC Customer Support. Bypass switch has been replaced Bypass switch has failed Communication established with Environmental Monitoring Card Communication has been established Communication has been lost while on battery Communication lost with Environmental Monitoring Card Contact X Alarm The bypass contactor is operating properly. 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. PowerChute Network Shutdown is receiving data from the Environmental Monitoring Card. Communication between PowerChute Network Shutdown and the UPS has been established. 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. 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. 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.

4 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. Parallel-UPSconfiguration. 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. Parallel-UPSconfiguration. Humidity Out Of Range Probe X Input Power has been restored: UPS has switched to On Line operation Management Card cannot communicate with the UPS 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. one Network Management Card on a Redundant-UPS or The UPS is no longer running on battery power. 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 NMC is always logged. Load (kva) Alarm Violation The load on your UPS has violated the maximum load threshold, set in the Network Management Card user interface. Reduce the load on the UPS to a safe level or upgrade to a device that can support the

5 existing load. Load (kva) Alarm Violation: OK Minimum redundancy has been lost Minimum redundancy has been restored Network Communication with address xxx has been lost PowerChute cannot communicate with the Management Card The load on your UPS is no longer above the load threshold. This event occurs only after a Load (kva) Alarm Violation event. The UPS 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. The UPS can now support the desired redundancy. This event occurs only after a Minimum Redundancy: Lost event. 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. 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

6 UPS has switched to battery power site, or contact APC Customer Support. This event is logged with a single occurrence and the IP address of the battery is always logged. 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 output overload UPS overload condition has been corrected 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. 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. All configurations Redundant- and Parallel-UPS configurations

7 Errors when running an INI file These events occur for all configurations. GUI: Account locked out. Your attempt to log on to PowerChute Network Shutdown has failed three times. Your PowerChute Network Shutdown account for the IP address xxx.xxx.xxx.xxx is locked out for 2 minutes. Low-Battery Condition: 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 Redundant-UPS and Parallel-UPS 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-UPS installations are not supported at address xxx.xxx.xxx.xxx One of the UPS devices in a Parallel-UPS configuration has been taken out of the configuration. Multiple Critical Events occurred: Event name, Event name This could be called multiple different critical events occurred. See Critical Events in Redundant or Parallel Configurations. UPS xxx.xxx.xxx.xxx is running on battery power.

8 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. All the events/ message below are errors that can happen when running an INI file. See INI files in PowerChute Network Shutdown in the Installation guide. ERROR: The ini file is missing the required [xx] section. WARNING: The ini file has entries defined outside of a section. WARNING: The invalid section [xx] should be removed from the ini file. ERROR: The ini file is missing [xx] key from section [xx]. ERROR: The ini file could not find IP address information in section [xx]. WARNING: The ini file has detected duplicate values for [xx] in section [xx]. WARNING: The invalid key [xx] should be deleted from section [xx] in the ini file. ERROR: The ini contains an invalid value for [xx] in section [xx]. ERROR: The ini contains an invalid value for [xx] in section [xx]. Using {2} instead. Please validate the configuration. FATAL ERROR: PCNS cannot find the configuration file ([xx]) or the backup configuration file ([xx]). Shutting down. ERROR: The key [xx] in section [xx], failed to match the supplied regular expression. ERROR: Could not convert the value of [xx] in section [xx] to its expected type. ERROR: Event [xx] is enabled for command file execution, but an invalid value for [xx] is specified. WARNING: Disabling command file execution for event [xx] due to bad parameters. Please validate the configuration.