PowerAlert Device Manager 20.0.0 (Build 2526) 9-FEB-2021 SHA1 hash: 6094f445d2e4cfc481b7ee4a757216d9e267cee1 Copyright (c) 2021 by Tripp Lite All Rights Reserved IMPORTANT NOTES * Devices must be running firmware version of 15.5.2 or higher in order to upgrade to PADM20. If devices are running firmware versions 15.5.1 or earlier, they must be upgraded to 15.5.7 prior to the PADM20 upgrade. * This version of PowerAlert Device Manager (PADM20) applies the following security policies: - On initial login with any of the pre-configured Local Users – localadmin, localmanager or localguest – PADM will force the user to change the default password. - The default passwords localadmin, localmanager and localguest are restricted and cannot be used for any user. - The preconfigured SNMPv1 and SNMPv2 users – public and tripplite, respectively – are disabled, by default. Note that PowerAlert Network Management System (PANMS) and PowerAlert Network Shutdown Agent (PANSA) will not discover devices until SNMPv2 user tripplite is enabled. - The default password of the pre-configured SNMPv3 users – localadmin, localmanager or localguest – must be changed prior to use. Note that the new entry will be saved as both the authentication and privacy passwords. - If the Administrator (with new password) navigates to Configuration > Security > User and saves any edits on the page, a warning message will appear about changing the Password and Auth Password for localmanager and localguest. * Beginning with PADM version 20.0.0, LX Platform devices do not include a textual menu interface. The menu interface is superseded by a full-featured Command Line Interface (CLI), capable of the same functionality as the web interface. A maximum of two concurrent CLI sessions are supported. If a third session is attempted, a warning message will appear that the session limit has been reached. The exception to this is if the third session is logging in with the default localdmin/localadmin credentials in which case the oldest active session will be terminated. * With firmware version 15.x.x, certain device protocols reported the device temperature under the incorrect label, "upsBatteryTemperature.0". In PADM20 this was corrected; the new labels are " tlpUpsDeviceTemperatureC" and "tlpUpsDeviceTemperatureF". * When performing a "Reset to Factory Defaults" using Command Line Interface (CLI), the observed LED sequence on the LX card/device differs from the one observed when executing the Reset from the web interface or long-pressing the Reset button. In all cases, the outcome of the Reset is identical. * Beginning with PADM version 20.0.0, the following features available in PADM version 15.5.x are not supported: HTTP/HTTPS Contacts, EnergyWise, IP filtering (Access Control ) of inbound SNMPv3 users. * Use PowerAlert Element Manager (PAEM) to perform Mass Firmware update on LX Platform Devices running firmware version 15.5.1 or later. See PAEM Release Notes for more information. * If UPS systems operating on 15.5.x are being monitored by PowerAlert Network Shutdown Agent (PANSA) software, upgrading those devices to PADM20 will require them to be deleted and then then re-discovered in PANSA. REQUIREMENTS DEFECT FIXES ENHANCEMENTS KNOWN ISSUES * External Battery Pack configuration using CLI is not supported in this release. Use the web GUI to execute this function.  * Language selection is not supported in this release; the default language is English. * SNMP does not report the same battery voltage parameters as does the web interface. [4201] * On certain devices, configuration SNMP OIDs (e.g. tlpUpsConfigInputVoltage) incorrectly appear to be supported. [5 4006 4100] * SNMP OIDs tlpUpsLowTransferVoltage and tlpUpsHighTransferVoltage do not map to corresponding UPS MIB OIDS [3021] * Output Voltage is not selectable in any interface, other than on the device's LCD [4004] * Changing installation date via SNMP OID tlpDeviceIdentDateInstalled does not propagate the change to all other interfaces [3005 3026] * When viewed on a mobile device, the 'Cleared' field in Alerts does not display status [3005] * On certain devices, the Low Critical Threshold is ignored, resulting in the Battery Low state being triggered when the value falls below the Low Warning Threshold [3014 4007] * Battery Status and Battery Capacity are incorrectly reported when the device is in a Low Battery condition [5] * Input Voltage Thresholds do not appear for 380/400/415 VAC devices [4200] * Bypass, Economy, Standby & Converter Modes are not correctly reported on some devices. [4000 4001 4002 4003 4004 4006 4100 4200 4201] * After undergoing a state change on all loads, certain PDU models may not correctly report the outlet state on a subset of those loads [5005] * Certain UPSs support adding an external battery [configuring a new runtime] using its front display. For this battery to appear in PADM, the LX card must first be rebooted, after which the battery model will be appear as 'unknown'. To update the model, edit the line item and select the appropriate model from the pulldown menu. To avoid the reboot+model procedure, add external battery packs using PADM instead of the UPS display. [4006] * The Recorded High/Low Output Current values may not be accurate [4006] * Under certain conditions, a firmware update from 15.5.x to PADM20 may experience issues uploading the file. To ensure there is enough memory to support the update, reset the LX Card to factory defaults. [ALL] * The terminology for E2 sensor Contact Input Alarm Level options (e.g. "Normally Closed") does not align with the condition, i.e. "Alarm" is not "Normal" [9003] * On certain devices, a tripped breaker will not trigger an "Output Off" event or alarm. [4100] * A newly created Auto-Probe may appear not to work. Ensure that the Auto-Probe is tied to an Action. Refer to the User Guide for instructions on assigning Auto-Probes to actions. [ALL] * Executing "Reboot PowerAlert" via the GUI appears differently than when executed via CLI. [5018] * After updating a device to PADM20, the initial launch of CLI make take a longer time than with 15.5.x. Please be patient. [ALL] * Reported values for tlpAtsOutputActivePower and 'Output Power (W)' may not be accurate; the calculation is subject to the accuracy of the hardware's sensors and truncation of the actual reading. * Temperature set points entered via SNMP (tlpCoolingSetPointDegF) are subject to rounding during conversion and so may not exactly match values entered using GUI or CLI [9002] * Changes to the unit of measure in PADM20 may result in rounded-up/down settings. For example, Low Battery Seconds Remaining Warning in 15.5.x converts to Runtime Remaining Low Warning (measured in minutes) in PADM20. * A pin Reset does not automatically close web and CLI sessions even though the sessions become inactive; a screen refresh is required to return the user to the login screen [ALL] * The Backup of Power Alert Settings function omits runtime configuration. If the Restore from Saved Backup is performed, delete all external batteries then run the “Add Battery” function again. [ALL] * Load selection for certain privileges will not automatically update related privileges. For example, changes to "switch-loads" will not be applied to "view-loads". [3015 5018] * Watchdog is incorrectly reported (as supported) in Device details [5018] * The names for Output Power(W) variables – KVA and KW – are displayed twice [3015 5018] * Variable "Auto Shed on Transition" may be displayed in GUI for devices that do not support the features [5018] * When performing the “Restore LX Card to Factory Defaults” function using the “maintain current network settings” option, the following occurs: -- Internet - Domain, IPv4, IPv6 and DNS settings do NOT change -- Services - The enabled/disabled status of SNMPv1, SNMPv2 and SNMPv3 revert to defaults; the port values for SNMP Get/Set and Trap do NOT change; HTTP/HTTPS and Telnet settings do NOT change; SFTP/SCP revert to defaults if SSH is enabled -- SMTP - Server, Authentication and Email Format all change; settings revert to defaults * In CLI, SNMP Set OID Delay, Count, or Interval do not display the minimum value when a value below that minimum is entered [PADM-21012] [4008] * In the “Device” menu item, The Bypass Limit settings are displayed without units of measure. The unit of measure for these settings is percentage (%). [4007] * In CLI, the IP Filter format does not match the format in documentation [4008] * CLI command "show security-mode" does not display the set parameter [3015 5018] * Firmware updates of SRCOOL products may cause certain data variables to disappear; restoring PowerAlert to Factory Defaults should resolve the issue [9002] * Data variable "Remote Temperature Sensor Setting " should re-named "Remote Temperature Sensor" [9002] * The Battery Age (Years) variable is not correctly displayed when viewed on a Galaxy mobile device [3015] * For SRCOOL devices, the Operating Mode "Idle" should be re-named "Defrosting" when the device is defrosting [9003] * The GUI allows the main Load to be cycled a second time, before the first one has completed [3015] * In CLI, the "on" command accepts a value greater than the maximum [4008] * Actions set to trigger on Clear events may not execute the number of times set by the count value. [5018] * The Battery Transition Count quantity displayed in SNMP does not match the one displayed in GUI and CLI [4008] * The Battery Transition Count quantity displayed in SNMP value does not reset when Reset Transition Count is executed in GUI or CLI [4008] * In CLI, error messages associated with the 'action' command lack details [All] * The SNMP Get/Set Port and SNMP Trap Port can be set to the same value [3014] * Changes made to Alert Contacts in CLI do not automatically update in GUI; a screen refresh is required to view the changes in GUI [9003] * In the Event Log, date-based filters may not display all relevant event entries [5018] * The Syslog Application log contains misspelled words [4008] * CLI allows load actions to be configured with both "on-set" and "on-clear" triggers whereas in GUI, it is either "on-set" or "on-clear" [5018] * The tlpUpsOutletGroup OID can be set to a value of zero [4008] * On changing the Device / Sensor name, it may take a long time to reflect the updated name(s) in other screens [3015 5018] * On logging in, it may take a long time for the "Current User", "PADM Firmware:" "PADM Uptime" values to be displayed at the bottom of the Main Menu [3015 5018 5023] * If an event is switched from disabled to enabled while the event is taking place (active alert), it does not get logged or appear as an active alert in the Alert table. [5023] * Certain Battery configuration details presented in SNMP are not displayed in GUI or CLI [3015] * After deleting then creating load groups, the Load selection page may display a text artifact in the load Name [3015 5018] * Sometimes the CLI command 'show trigger' doesn't display the "On Set/Clear" columns [3015 5018] * In CLI, setting the frequency of a scheduled action to 'once' will automatically- and without informing the user – reset (overwrite) the recurrence count to one (1). * In SNMP, the tlpUpsConfigBypassLowerLimitPercent variable can be set to a value outside the allowed range [4007] * For Scheduled Actions, the "run-on" parameter will automatically update to a different value if it is set too close to current time [3015 5018] * In SNMP, the tlpUpsConfigHigh/LowVoltageTransfer OIDs cannot be set; use CLI or GUI to set these parameters [3027] * In CLI, the action delay variable can be set to a value outside the allowed range [PADM-21012] [9002, 9003] * The Sensor metrics selected to be recorded (in Data Log Settings) are not correctly reflected in CLI [9003 9300] * If two or three E2 sensors are exchanged on an active device (e.g. disconnect two E2MTs and connect two E2MTDOs), the "Device Properties" page will not immediately reflect the change; eventually it will. A reboot of PowerAlert will immediately resolve the issue. * Log exports will be recorded as successful even if the recipient email is invalid (e.g. fails Send Test) [3015 5018] * The Event Log may not record failed SNMP Traps, i.e. sent to an invalid SNMP trap recipient [3015 5018] * If a UPS Power Module is disconnected from one detachable PDU and connected to a different one, it will not detect the difference until "Restore LX to Factory Defaults" is performed on the Power Module. * On certain device models, the displayed Nominal Input Voltage value is incorrect [4100] * In CLI, the following error message may appear: "Connection lost or request timed out. Unable to process command. Please try again". This can occur if a command is entered while a previously executed one is still in process. Wait a few moments before attempting the command again. * When logging out as a sysadmin user, the word 'logged' is misspelled [4008] * When performing a "Send Test" of an Alert Contact, the "Cancel" function may not work; the test will continue [3015 5018] * Under certain conditions the 'Loads Not All On' alert may not clear at the same time as the alert for the corresponding individual load(s). [4008] * Unselecting device variables to be (Data) logged may cause the displayed data not to align with the column headers [3015 5018] * If a log export is performed to an invalid email address, the progress indication box may get stuck after reaching 100%; perform a screen refresh to recover [3015 5018] * CLI allows enabling an action with no added contacts; GUI requires a contact when enabling an action. [4008] * Standard external battery packs that are added in the Batteries page are numerically represented on the Device Details page under "Number of External Batteries". Smart external battery packs can be added in the Batteries page, but are not be accounted for in "Number of External Batteries". * When Ramp/Shed is being edited in GUI, attempting to make edits via SNMP (tlpUpsControlRamp/Shed) will incorrectly return "Set Succeeded" [4008] * In CLI, if the load ramp state is changed, but not applied, Begin Ramp and Shed in GUI should be disabled [4008] * After adding an external battery pack via the "Batteries" page, the displayed runtime does not update to reflect the new configuration. Navigate away from, then back to the page in order to display the updated runtime. * If two or three E2 sensors are exchanged on an active device it may take a while for the "Device Properties" page to reflect the change. A reboot of PowerAlert will immediately resolve the issue. * In CLI, performing the 'restore' command with no backup file present will display an unformatted message [4008] * After changing the Input Frequency in GUI, it may take a very long time for the change to be reflected in SNMP (tlpUpsInputPhaseFrequency) [4007] * For certain UPS models, the Events page may display duplicate or similar-sounding events. For example “Emergency Power Off Active” may appear alongside “Emergency Power Off”. This occurs because the event displayed on the LCD of the device does not exactly match the event reported to PADM. As a result, if the event occurs, it will be recorded in the PADM Event Log under each name. * Battery Replacement Dates are overwritten during a Restore action [4006] * For certain UPS models, the Events page may display duplicate or similar-sounding events. For example “Emergency Power Off Active” may appear alongside “Emergency Power Off”. This occurs because the event displayed on the LCD of the device does not exactly match the event reported to PADM. As a result, if the event occurs, it will be recorded in the PADM Event Log under each name. * Active alerts related to sensors get cleared if the sensor is disconnected [3015] * For devices that support both controllable and non-controllable loads, Alert/Email/SMS/Traps will get generated for controllable loads, but not the non-controllable loads [3015] * The Email Alarm ID for certain event types (stateless) is shared; it should be unique for each such event [4008] * For certain UPS models, the Battery Status > Fully Discharged variable does not display a value [4004] * Events triggered via HID (ERRCODE) are not mapped to PADM20 Events [4008] * When Seconds on Battery > Timed Shutdown Status is enabled, a power event will trigger a fault condition instead of executing the timed shutdown. [4008] * LCD orientation and brightness do not return to default values when a Reset to Factory Default is performed [5017] * In CLI, changing the Data Log interval does not generate a Purge Warning Message, as it does in the web interface [9003] * Trap port parameter removed but still exist in "man" command in [4008 5023] * During a firmware upgrade using CLI, the screen may display 'failed to add accounting log record' though the upgrade is successful [4004] * At the start of a firmware upgrade using CLI, the Accounting Log displays the loopback address as the origin. [5022] * The polling interval difference between SNMP and CLI is significantly greater in PADM20 than it was with 15.5.x. [4006] * When editing the linked actions of a stateless event (e.g. Device Startup), PADM20 erroneously allows selection of an On Clear trigger. [4008] * SNMP OID tlpUpsConfigHighVoltageResetTolerance fails to write a valid value [3027] * SNMP OID tlpUpsConfigLowVoltageResetTolerance fails to write a valid value [3027] * SNMP OID tlpUpsBatteryPackDetailLastReplaceDate is not writable until the Battery Installed Date is updated in the web interface [3015 3021] * SNMP OID tlpUpsControlResetAllParameters is not available, though the equivalent is available in CLI and the web interface [3027] * Data Log Rollups erroneously display parameter categories that are not supported (e.g. input voltage line to neutral L1-N) [5023] * For scheduled actions, no warning is provided that the set time must be at least ten minutes beyond current time [9003] * The high and low transfer voltage ranges shown in the web interface are incorrect [4004] * When setting a false value for TruthValue OIDs during an SNMP SET, PADM20 should not respond with an error [4008] * The set values for load ramp and shed delays do not align with the corresponding,observed delays when ramp and shed are executed [3003] * In CLI, it should not be possible to set a value of zero for output current threshold High [5023] * Under certain conditions, the shed start command will not work [4008] * The date and time values of the Real Time Clock are affected by a firmware upgrade [9002 9003] * After disabling an Autoprobe, the CLI and web interface report status as 'unknown' whereas in SNMP (tlpAgentAutoProbeStatus) it is reported as "OK" [5023] * On configuring Battery Installed Date via CLI or web interface, the SNMP response for tlpUpsBatteryPackDetailLastReplaceDate is intermittent [4008] * Configuring the Battery Installed Date value via CLI or web interface does not get reflected in SNMP (tlpUpsBatteryPackDetailLastReplaceDate) [4008] * A Bypass Out Of Range condition is intermittently reported [4007] * When the (AC) device is operating in Metric Mode, its status is reported slowly / incorrectly in the software interfaces [9002 9003] * Disabling 'on-battery-shutdown-seconds' causes the time value to revert to the default value [4006 4007 4008] * The 'AC Fail and Restore Auto-Reboot' command is available in SNMP and the web interface, but not in CLI [4006] * Performing a MIB WALK takes longer than expected [5023] * The Bypass Voltage Low Limit and High Limit ranges reported in SNMP differ from those reported in CLI and the web interface [4000] * Intermittently, a "Temperature Beyond Limits" Alert may persist after the threshold is changed to be in range [5018] * An anomaly was observed in which a scheduled load action incorrectly affected other loads [5001] * When the UPS is on battery, the Buzzer Status variable reports 'silent', i.e. does not reflect the current state [3005] * Fan speed is not reported correctly when the device is powered off [9003] * After AC is restored, Loads set to remain off are turned on during Ramp [4007] * After AC is restored, Loads set to turn on after a long delay never turn on [4007] END RELEASE NOTES