Tripp SNMPWEBCARD User Manual

WARRANTY

User’s Guide

REGISTRATION:

chance to win a FREE Tripp Lite

product—www.tripplite.com/warranty

Table of Contents

1. Introduction 2

1.1 System Requirements 2

2. Installation and Conﬁguration 2

2.1 Saving Conﬁguration Changes 2

2.2 Default UPS System Shutdown Settings 2

2.3 Other Default Settings 3

2.4 SNMP Conﬁguration 3

3. Web Console 4

3.1 Opening the Web Console 4

3.2 Web Console Interface 4

3.3 Device Summary 5

3.4 Status Menu 5

3.4.1 Status > Overview 5

3.4.2 Status > Details 6

3.4.3 Status > Alarms 7

3.5 Device Menu 7

3.5.1 Device > Controls 7

3.5.2 Device > Loads 8

3.5.3 Device > Load Groups 8

3.5.4 Device > Events 9

3.5.5 Device > Device Discovery

3.6 Actions Menu 10

3.6.1 Actions 10

3.6.1.1 Actions > Event Actions >

Device Actions 10

3.6.1.2 Actions > Event Actions > General Actions 13

3.6.2 Actions > Address Book 14

3.7 Logs 15

3.7.1 Logs > Event Logs 15

3.7.2 Logs > Data 15

3.8 Preferences 16

3.8.1 Preferences > Network 16

3.8.2 Preferences > Security 18

3.8.3 Preferences > System 22

3.8.4 Preferences > Restart 24

3.9 Help 24

SNMPWEBCARD

Firmware Version 12.06.0061

Revision 2

4. Telnet/SSH Console 25

4.1 Device Menu 27

4.1.1 Status 28

4.1.2 Identiﬁcation 29

4.1.3 Controls 30

4.1.3.1 Control Data 31

4.1.4 Events 32

4.1.5 Loads 35

4.1.5.1 Load Conﬁguration 35

4.1.5.2 Load Groups 36

4.1.5.3 Ramp/Shed Settings 37

4.1.6 Preferences and Thresholds 38

4.1.7 Device Alarms 39

4.1.8 Logs 39

4.2 System Conﬁguration 39

4.2.1 Address Book 39

4.2.1.1 Email Contacts 40

4.2.1.2 SNMP Contacts 41

4.2.1.3 HTTP Contacts 42

4.2.2 Global Actions 43

4.2.2.1 Action Proﬁles 43

4.2.2.2 Schedules 55

4.2.3 Security 59

4.2.3.1 Authentication Method 59

4.2.3.2 Local Users 60

4.2.3.3 RADIUS Servers 63

4.2.3.4 Change Password 64

4.2.4 Date/Time 64

4.2.4.1 Time Source Data

Entry Menu 64

4.2.4.2 Time Settings 65

4.2.4.3 SNTP Settings 66

4.2.4.4 RTC Settings 66

4.2.5 Local Device Discovery 67

4.2.6 Restart PowerAlert 68

4.3 Network Conﬁguration 69

4.3.1 Remote Services 69

4.3.1.1 Email Settings 69

4.3.1.2 Remote Syslog 71

4.3.1.3 Watchdog Settings 74

4.3.2 User Interfaces 75

4.3.2.1 Telnet/SSH 75

4.3.2.2 Web Console 75

4.3.2.3 SNMP Settings 76

4.3.2.4 FTP 76

4.3.2.5 Remote View Access Port 76

4.3.3 IP Conﬁguration 77

4.3.3.1 Host Name 78

4.3.3.2 Domain Data Entry Menu 78

4.3.3.3 IPV4 Settings 78

4.3.3.4 IPV6 Settings 79

4.4 Alarms and Logging 81

4.4.1 Alarms 81

4.4.1.1 Alarm Details 82

4.4.2 View Logs 82

4.4.2.1 Data Log 83

4.4.2.2 Event Log 85

4.4.3 Logging Settings 88

4.4.3.1 Individual Log Settings 88

4.4.3.2 Data Log Settings 89

4.4.3.3 Event Log Settings 90

4.5 About 92

5. Command Line Interface 93

5.1 Syntax Conventions 93

5.2 Manual Pages 94

5.3 Output Conventions 94

5.4

Getting Started with the PowerAlert CLI

6. Troubleshooting 96

7. Technical Support 96

8. Appendix 97

Documentation Notice: This User’s Guide is a supplement to the printed manual that came with your SNMPWEBCARD or network-enabled PDU. Refer to the printed manual for instructions on hardware installation and basic conﬁguration, including IP address assignment. If you have misplaced your printed manual, refer to the electronic version included on the bundled CD-ROM or download it at www.tripplite.com/support/manuals/.

1111 W. 35th Street, Chicago, IL 60609 USA • www.tripplite.com/support

1. Introduction

SNMPWEBCARD is an optional network card that you can install in the accessory slot of a compatible UPS system or PDU*. SNMPWEBCARD connects your UPS system or PDU to your Ethernet network as a manageable device that supports remote monitoring, remote control and remote condition reporting. You can manage the device from PowerAlert Network Management System, an SNMP Network Management Station, a Web browser or telnet. Remote access capability allows you to reboot, control outlets, shed nonessential loads, monitor load levels and more. The SNMPWEBCARD can also send SNMP traps or e-mail messages to the addresses you specify, alerting you automatically to events such as power failures.

* SNMPWE BCARD is p reinsta lled in Tripp Li te Monitor ed and Swit ched PDUs , which can b e identiﬁe d by the pre sence of “M N” or “NET ” in the mode l name.

1.1 System Requirements

• Tripp Lite UPS system or PDU with compatible accessory slot

• Ethernet network that supports the TCP/IP protocol

• One of the following options for remote monitoring and control:

• PowerAlert Network Management System

• SNMP-based Network Management Station (such as HP® OpenView®)

• Web browser that supports frames, forms and Java™ (such as Microsoft® Internet Explorer® 7.0 or later)

• VT-100 Telnet and/or SSH Client

• For “Terminal Mode” conﬁguration only:

• Terminal emulation software program (such as TeraTerm Pro by Ayera Technologies)

• Computer with available DB9 serial port

Warning : Use of this eq uipmen t in life sup port ap plicati ons wher e failur e of this equ ipment c an reason ably be ex pecte d to cause th e failur e of the life s uppor t equipm ent or to sig niﬁcant ly affe ct its safet y or effe ctiveness is not re comme nded. Do n ot use this eq uipmen t in the pre sence of a ﬂ ammable a nesthe tic mixt ure with a ir, oxygen or n itrous oxide.

2. Installation and Conﬁguration

For instructions on hardware installation and basic conﬁguration, refer to the printed manual that came with your SNMPWEBCARD or PDU. For instructions on loading a ﬁrmware or device driver upgrade on the SNMPWEBCARD, refer to the PowerAlert software release notes. The manual and release notes can be found on the bundled CD-ROM or downloaded from www.tripplite.com/manuals/.

2.1 Saving Conﬁguration Changes

While using PowerAlert, most of your conﬁguration changes will take effect immediately so you can try out your conﬁguration before committing to it. The Web and Telnet Menu user interfaces will typically advise you if your conﬁguration requires a restart to take effect.

In general, the conﬁguration is not persisted permanently until you restart PowerAlert (or ‘reboot’ the SNMPWEBCARD). You should restart PowerAlert when your conﬁguration is complete and before testing conﬁgurations that simulate or nearly simulate a power outage. For your convenience, most changes will auto-save after about 30 minutes of idle time. Changes to the network settings will not.

Restarting PowerAlert cannot cause equipment powered through your UPS or PDU to experience an outage and has no affect on the general operation of your Tripp Lite device.

2.2 Default UPS System Shutdown Settings

During a power failure, SNMPWEBCARD is pre-conﬁgured to shut down the UPS system two minutes after receiving a low battery signal. This allows the UPS system to provide the maximum available runtime to connected equipment. If you want to change the default setting, follow these instructions and refer to Figure 2-1 and Figure 2-2:

1. Use a Web browser to open the PowerAlert console window for your SNMPWEBCARD (see 3.1 Opening the Web Console for instructions).

2. Click the Actions menu A and access the Event Actions submenu B.

3. Select Device Shutdown in the Device Actions C section.

4. Click the button on the bottom of the screen D to add a new action.

5. In the Name ﬁeld E, type a name for the new action.

Figure 2-1: UPS System Shutdown Settings

2. Installation and Conﬁguration continued

6. Click the Actions ﬁeld F to access its submenu. Select the device to shut down in the Select Trigger Device section G.

7. Set how long the delay should be before the action will take place H.

8. Select the Event(s) that will trigger the action I.

9. Click the Save button on the bottom of the screen J.

Note: Whenever changes are made, the save button must be pressed to submit the changes before moving off of the page. This also includes deleting ﬁelds using the button. After selecting an item and clicking the button press the button to commit the change.

2.3 Other Default Settings

Setting Default Value Additional Information

IP address Telnet Access

SSH Access HTTP Access HTTP Access SNMPv1 Access SNMPv2 Access SNMPv3 Access

Default users and passwords

Radius Email Notiﬁcation

SNMP Trap Notiﬁcation

Event Logging Data Logging

Obtain from DHCP Enabled

Enabled Enabled Enabled Enabled—Read-Only Community—public Enabled—Read-Write Community—tripplite Enabled

localadmin localmanager localguest

See table below localadmin/localadmin

localmanager/localmanger localguest/localguest

Disabled Default email action proﬁle setup to trigger 30 seconds after an alarm. Add email destinations to

the address book. Default SNMP Trap action proﬁle setup to trigger 30 seconds after an alarm. Add trap destinations

to the address book. Enabled Enabled

G H I

Figure 2-2: UPS System Shutdown Settings

Section 3.8.1 Section 3.8.1

Section 3.8.1 Section 3.8.1 Section 3.8.1 Section 3.8.2 Section 3.8.2 Section 3.8.2

Section 3.8.2

Section 3.8.2 Section 3.6

Section 3.6

Section 3.7 Section 3.7

2.4 SNMP Conﬁguration

SNMPWEBCARD allows a compatible UPS system or PDU to function as an SNMP-managed device on your network, using the SNMP agent and Management Information Base (MIB). The SNMP agent resides in the SNMPWEBCARD ﬁrmware and responds to standard SNMP commands (Get, Get Next and Set). It can also generate SNMP traps (messages). The MIB determines which parameters can be monitored and controlled. Two MIB ﬁles—Tripplite.mib and RFC1628.mib—must be loaded on each Network Management Station that will monitor the managed device. (The ﬁles are provided on the CD-ROM included with the SNMPWEBCARD or network-enabled PDU. Consult your Network Management Station software documentation for instructions on how to import MIB ﬁles.)

SNMPv3 Deﬁnitions

User Name The identiﬁer of the user proﬁle. SNMP version 3 maps Gets, Sets and Traps to a user proﬁle by matching the user name

of the proﬁle to the user name in the data packet being transmitted. A user name can have up to 32 ASCII characters.

Authentication Passphrase A phrase of 8 to 32 ASCII characters that veriﬁes that the Network Management System (NMS) communicating

with this device through SNMPv3 is the NMS it claims to be, that the message has not been changed during transmission, and that the message was communicated in a timely manner, indicating that it was not delayed and that it was not copied and sent again later at an inappropriate time.

Privacy Passphrase A phrase of 8 to 32 ASCII characters that ensures the privacy of the data (by means of encryption) that a Network

Management System (NMS) is sending to this device or receiving from this device through SNMPv3.

Authentication Protocol The Tripp Lite implementation of SNMPv3 supports only MD5 authentication.

Privacy Protocol The Tripp Lite implementation of SNMPv3 supports only DES as the protocol for encrypting and decrypting data.

Public Value A ﬁeld provided to enter a username/password hint for SNMPv3 Admin users. This SNMPv3 value is part of the SNMPv3

3. Web Console

The Web console is the primary graphical user interface for the SNMPWEBCARD.

3.1 Opening the Web Console

Figure 3-1: Web Console Login

1. Open a Web browser that supports frames, forms and Java. PowerAlert versions 12.06.0061+ are compatible with Java 1.7. Older versions may require Java 1.6.

2. Type the IP address assigned to the SNMPWEBCARD or PDU into the address ﬁeld and press the enter key to download the Java applet. (Refer to the printed manual for IP address assignment instructions.)

3. After the applet is downloaded and connected, you should be prompted for a user name and password (Figure 3-1). The default administrator user name is localadmin and the default password is localadmin.

The application screen includes a communication status message A that indicates the progress of the application in ﬁnding a device, making a connection and completing the login attempt successfully.

3.2 Web Console Interface

Figure 3-3: Status Page

The header B contains the menu buttons, which are the main navigational icons of the console.

After clicking a menu button, the submenu options for the menu C will appear below the header.

The Device Summary D is always displayed at the top of the screen, while the bottom portion of the screen changes as different options are chosen.

Figure 3-2: Communications Status

4. After you log in, the device status page (Figure 3-3) will load in the browser window.

3. Web Console continued

3.3 Device Summary

Figure 3-4: Devices

The Device Summary displays the current Alarm Status, Model Name, Device Type and user-deﬁned location of a device.

Valid Alarm Status values include:

•NORMAL

•INFORMATION

• WARNING

• STATUS

•CRITICAL

•OFFLINE

Model Name is detected automatically and is not editable by the user.

Valid Device Type values include

• UPS

•PDU

• ENVIROSENSE

•AC

3.4 Status Menu

3.4.1 Status > Overview

Figure 3-5: Status Page

This is the default screen of information and will the ﬁrst screen to be displayed. It is a pictorial representation of the state of the system. The values on this screen are not editable.

Note: The graphic symbols used are not intended to be a representation of the actual equipment connected.

Location is user-deﬁned. There is no default value for location.

3. Web Console continued

3.4 Status Menu continued

3.4.2 Status > Details

Figure 3-6: Device Status

The content of this screen will vary based upon the protocol of the device. This screen contains the device variable data. Any editable variables will be displayed at the top of the list. The editable variables have a white value box. This section of variables is sorted by purpose and within each purpose, by variable name.

Customizing the device functionality can be done through Behavior, Personal, and Threshold menus on the left side of the screen. These menus allow settings and threshold information to be change to meet individual needs. Some options are modiﬁed by clicking on a cell and the then selecting the appropriate value, and some will require a typed value in the cell. Click Save when you have ﬁnished making changes.

Device Name

Purpose

• ThevalidvaluesforPurposeare:

o Behavior – the variable contains conﬁguration information that

deﬁnes device behavior

o Equipment – the variable contains information describing the

device

o Personal – the variable contains conﬁgurable identifying

information

o Status – the variable contains device status information

o Threshold – the variable contains a threshold for a device

event

Figure 3-7: Device Behavior

Group

• Each device has a group to categorize the variable. Devices in

general will not have variables in all groups, but will have variables in multiple groups. The following are the valid group values:

o Battery – the variable is associated with the devices battery

o Bypass – the variable is associated with bypass

o Contact – the variable is associated with a contact closure

sensor

o Device

o Environment

o Input

o Load

o Output

o System

o Watchdog

Value

• This is the current value of the variable. Values include Enabled,

Disabled and numeric values depending on the device.

3. Web Console continued

3.4 Status Menu continued

3.4.3 Status > Alarms

Figure 3-8: Alarms

This submenu provides a listing of all active and/or unacknowledged alarms.

By default, only active alarms will be displayed on this page, as the software will automatically mark the alarm acknowledged upon receipt of the matching clear alarm. To change this, deselect the option to auto acknowledge alarms. Upon de-selection of this option, alarms will remain in this list until they are acknowledged individually by clicking on the ‘Ack’ column for the alarm, or clicking the “Acknowledge all” button.

Note: An alarm must be inactive in order for it to be acknowledged and disappear from the alarm list.

3.5 Device Menu

The device menu is used to enact different commands or conﬁgurations for individual devices.

3.5.1 Device > Controls

Figure 3-9: Controls

Controls available on the selected device in the device list appear in the ‘Select One’ section of the page.

Click on a control and, if parameters are necessary to execute the control, the parameters required will appear to right of the selected control. Enter the data in the value ﬁeld and the click the ‘Execute’ button on the bottom of the page.

Available commands include “Reboot Device,” “Initiate Self-Test,” “Operating System Restart,” “Start Ramp Sequence,” “Start Shed Sequence,” etc. For a complete list of commands available for your device, refer to the ‘Select One’ menu.

3. Web Console continued

3.5 Device Menu continued

3.5.2 Device > Loads

Figure 3-10: Loads

The Loads menu option will only appear if the device supports loads. The description ﬁeld is an editable value. In order to save any changes made on this page, you must click the ‘Save’ button at the bottom of the page.

You can control the outlets of the managed device by selecting the load and then clicking the appropriate “On,” “Off” or “Cycle” button.

The load of connected equipment is displayed in amps, allowing you to see whether additional equipment can be added safely. (Load ﬂuctuates with the power demands of connected equipment. It is prudent to limit the load to approximately 80% of maximum capacity in order to accommodate higher startup power demands and other increased power needs.)

If your device has controllable load banks, additional buttons allow you to control each load bank. (Each load bank consists of one or more outlets.) You can use the “Description” ﬁeld to label the banks for easy reference. The main control buttons affect all outlets at once. Note:

If the control buttons remain grayed out when a load is selected, this condition indicates the outlet is non-controllable.

3.5.3 Device > Load Groups

Figure 3-11: Load Groups

The Load Groups menu option will only appear if the device has two (2) or more controllable loads.

To create a load group click the (+) button on the bottom of the screen to add a group row to the table. Then, enter a name and description and click on the loads cell to expose available loads that can be added to a group. Click on the select loads and then click the save button on the bottom of the screen

The description is an editable ﬁeld. Once change are made to any, or all, descriptions, click the Save button to save the changes.

To delete a load group, click on the load group row to delete, click the [-] button and conﬁrm the delete.

3. Web Console continued

3.5 Device Menu continued

3.5.4 Device > Events

Figure 3-12: Events

The ‘Events’ page displays all of the available events associated with a device.

Event Category

This speciﬁes the severity level for the event. The user may choose to give the event a different severity level. The valid values for category are:

•CRITICAL

• WARNING

•INFORMATION

3.5.5 Device > Device Discovery

Figure 3-13: Device Discovery

To search for additional devices, click ‘Execute’ at the bottom of the page. This feature can be used when adding a Tripp Lite ENVIROSENSE temperature and humidity probe. Once the probe is connected to the SNMPWEBCARD, press the execute button and the probe will appear as a device in the device list.

Enable/Disable Event

This allows the user to no longer consider this event an alarm event. Disabling the event will cause this event to no longer create an alarm and the actions will no longer ﬁre when this event occurs. The default is for all events to be enabled.

Enable/Disable Logging

The user may enable and disable logging for the event. The default is that all events are logged.

3. Web Console continued

3.6 Actions Menu

The Actions menu allows for detailed conﬁguration of event responses, scheduled actions, and the contact information in the address book. At this time, the Web interface does not support scheduled actions. Please refer to the Telnet or SSH menu interface to create scheduled actions

(Section 4.2.2.2).

Note: The Actions menu in the Web interface was formerly called the Conﬁguration menu. A few of the screen shots in this manual still depict the content under the former name.

3.6.1 Actions

3.6.1.1 Actions > Event Actions > Device Actions

Control Execution Actions

A control action is a device speciﬁc action that can be executed when an alarm trigger is crossed. An example of a control action could be that when the battery age crosses the user deﬁned threshold, a self test is automatically executed to see if the battery in a UPS is still in good condition. Since these are device speciﬁc, the control actions available on devices will vary from UPS to UPS and from UPS to PDUs.

To add an action, click the [+] button to activate a row and enter the appropriate data. To delete an action, click on the action that is to be deleted and then click the [-] button and conﬁrm the deletion and then the [save] button to commit the changes.

Figure 3-14: Actions

Action proﬁles deﬁne responses to events and alarm conditions. The action proﬁle allows the response to be deﬁned once and applied to multiple alarm events. An action may be a response to the alarm condition or a response to the condition clearing. Where appropriate, the two actions may be the same.

You can conﬁgure action settings for several event types, including “On Battery” and “Battery Low.” (Events vary by device.) You can conﬁgure several settings categories that specify actions to be executed when the selected event takes place.

Figure 3-15: Device Actions

3. Web Console continued

3.6 Actions Menu continued

3.6.1.1 Actions > Event Actions > Device Actions continued

Device Shutdown Actions

Device shutdown actions allow you to shutdown a device when a user-deﬁned trigger occurs. Triggers include various alarms and even ENVIROSENSE readings. Device shutdown also includes the option to be put on a delay.

Load Actions

A load action is a device speciﬁc action that can be executed when an alarm trigger is crossed. An example of a load action could be that when the device load goes above the user deﬁned threshold and triggers a ‘Load Level Above Threshold Event,’ that a speciﬁc load is turned off to reduce the load. The amount of controllable loads available on devices will vary from UPS to UPS and from UPS to PDUs.

Figure 3-16: Device Shutdown

Figure 3-17: Load Actions

3. Web Console continued

3.6 Actions Menu continued

3.6.1.1 Actions > Event Actions > Device Actions continued

Ramp Actions

A ramp action is a device speciﬁc action that can be executed when an alarm trigger is crossed. An example of a ramp action could be that when a UPS returns from an on battery event, the event trigger would be ‘On Utility Power,’ to execute the ramp settings set on the controllable loads. Ramp settings are deﬁned on the Device-Loads page. The amount of controllable loads available on devices will vary from UPS to UPS and from UPS to PDUs.

Shed Actions

A shed action is a device speciﬁc action that can be executed when an alarm trigger is crossed. An example of a ramp action could be that when a UPS goes to battery, the event trigger would be ‘UPS on Battery,’ to execute the shed settings set on the controllable loads. Shed settings are deﬁned on the Device-Loads page. The amount of controllable loads available on devices will vary from UPS to UPS and from UPS to PDUs.

Figure 3-18: Ramp Actions

Figure 3-19: Shed Actions

3. Web Console continued

3.6 Actions Menu continued

3.6.1.2 Actions > Event Actions > General Actions

Email Actions

An Email action is an action that will send emails to selected people in the address book when user-deﬁned events are detected. It is possible to deﬁne multiple email actions so that different people are notiﬁed when different alarms are detected or different people are notiﬁed if the triggering event lasts longer than expected.

By default, an email action is set up to notify all email contacts in the address book 30 seconds after an event trigger.

The delay setting deﬁnes when the ﬁrst email should be sent, while the count deﬁnes the number of emails to be sent. The interval is the delay between the sending of additional emails. If the count is set to 1, the interval time is ignored as only one email will be sent.

SNMP Set OID Actions

A SNMP Set OID action allows for the SNMPWEBCARD to set an SNMP value on another device on the network that will do something or set a value that the other network device will recognize and take some action based upon that SNMP value being set. An example of an application of this action is to have an SNMPWEBCARD in a UPS notify the network PDU that the UPS is power that the PDU is running on battery power. If utilizing a Tripp Lite PDU it is possible to execute the shed setting stored on the PDU to shed (turn off) equipment that is not necessary to extend the runtime of the UPS.

The OID to set on Tripp Lite PDU for shedding is

OID .1.3.6.1.4.1.850.100.1.8.3.3.0 – type integer and a value of 1

The OID to set on Tripp Lite PDU for ramping is

Clear OID .1.3.6.1.4.1.850.100.1.8.3.2.0 –type integer value of 1

Figure 3-20: Email Actions

Figure 3-21: Set Actions

3. Web Console continued

3.6 Actions Menu continued

3.6.1.2 Actions > Event Actions > General Actions

continued

SNMP Trap Actions

An SNMP Trap action is an action that will send SNMPv1 traps to selected destinations in the address book when selected events are detected. It is possible to deﬁne multiple email actions so that different people are notiﬁed when different alarms are detected or if the requirement is notify different people if the triggering event last longer then expected.

By default there is a default SNMP Trap action setup to notify all SNMP contacts in the address book after 30 seconds.

The delay settings deﬁnes when the ﬁrst email should be sent, the count the number of emails to be sent, if set to 1 the interval time is ignored as it will only send one email, and the interval is the delay between additional emails being sent out.

3.6.2 Actions > Address Book

Figure 3-23: Address Book

To modify Address Book settings for each type of notiﬁcation method, locate it in the ‘Contacts’ box on the left side of the page and edit the variable ﬁelds.

The “Email” tab shows a table of e-mail contacts. Before your SNMPWEBCARD can send e-mail notiﬁcations, you must add at least one e-mail contact.

If you do not know the correct settings, contact your network administrator. To add an email contact, click the [+] button on the bottom of the screen to activate the next available row.

The “SNMP” tab shows a table of SNMP contacts. Before your SNMPWEBCARD can send an SNMP trap or SNMP set to an IP address, you must add at least one SNMP contact. To add an email contact, click the [+] button on the bottom of the screen to activate the next available row. (The standard port for SNMP set destinations is port 161. The standard port for SNMP trap recipients is port 162.)

Note: If adding an SNMP contact to be used with a SNMP Set Notiﬁcation, use port 161 or the port number that the remote SNMP device can be accessed on. After adding Email and SNMP contacts, the user must set contacts for trap sending during events.

Note: You also need to conﬁgure and enable each event setting through the Conﬁguration>Actions window before notiﬁcations can be sent to your contacts.

Figure 3-22: Trap Actions

3. Web Console continued

3.7 Logs

This menu allows for in-dept h viewing, conﬁguration and ackn owledgement of logs that come across the system.

3.7.1 Logs > Event Logs

Figure 3-24: Event Logs

This menu allows the user to view the event log entries for the entire system.

Events are listed in order of the time and date they occurred. Information on the type of event that occurred, the device it occurred on, the severity category and a description of the event is also displayed. To view more events, simply continue scrolling down through the log.

Logs can be ﬁltered by using the menus at the bottom of the page. Logs can be ﬁltered and viewed by time frame, type of event, device on which it occurred, severity category and description. In order to apply ﬁlters to the event log, click the ‘Apply’ button at the bottom of the page.

3.7.2 Logs > Data

Figure 3-25: Data Logs

This menu allows the user to view the data log entries for the entire system.

Data points are listed in order of the time and date they occurred. Information on the type of data point that occurred, the device it occurred on, which variable it occurred on and the numeric value is also displayed. To view more data points, simply continue scrolling down through the log.

Logs can be ﬁltered by using the menus at the bottom of the page. Logs can be ﬁltered and viewed by time frame, reporting device, device variables and variable value. Device variable ﬁlters can either be all of the variables for all devices (default), all variables on one device or up to three speciﬁc variables across all devices. In order to apply ﬁlters to the event log, click the ‘Apply’ button at the bottom of the page.

Filters can be cleared within a session by clicking the ‘Reset Filters’ button at the bottom of the page. Filters do not persist from session to session.

3. Web Console continued

3.8 Preferences

This menu is used to alter user-deﬁned preferences for the network, security and overall system settings.

3.8.1 Preferences > Network

Figure 3-26: Services

This menu is used to deﬁne the network preferences for remote service interfaces, SMTP and Internet.

Services

This menu is available in the ‘Network Preferences’ box at the left side of the page in the Preferences > Network submenu. Any changes to these settings will require a system restart.

Automatically Start SNMP

This indicates if SNMP should automatically be started when the system is initialized.

SNMP Port

This is the port to use when starting SNMP during system initialization. This is the same port to use for set and get requests. The default is 161.

Automatically Start HT TP

This indicates if HT TP should be automatically started as part of system initialization.

HTTP Port

If the application is to be started, then this is the listening port to use. The default is 80

Automatically Start Telnet Menu

This indicates if the Telnet Menu application be automatically started as part of system initialization.

Telnet Menu Port

This is the listening port to user for the Telnet Menu application. The default is 23.

Automatically Start Telnet CLI

This indicates if the Command Line Interface application should be automatically started as part of system initialization.

Telnet CLI Port

This is the listening port to use for the Telnet CLI Application. The default is 5214.

Automatically Start SSH Menu

This indicates if the SSH Menu application should be automatically started as part of system initialization. The default is Yes.

SSH Menu Port

This is the listening port to use when starting the SSH Menu application. The default is 22.

Automatically Start SSH CLI

This indicates if the SSH Command Line Interface application should be automatically started as part of system initialization. The default value is Yes.

SSH CLI Por t

This is the listening port to use when starting the SSH CLI application. The default is 2112.

Enable SNMP V1

This indicates if SNMPv1 should be enabled on startup. The default is that SNMP V1 is enabled.

Enable SNMP V2c

This indicates if SNMPV2c should be enabled on startup. The default is that SNMP V2c is enabled.

Enable SNMP V3

This indicates if SNMPV3 should be enabled on startup. The default is that SNMPV3 is enabled. Note: The SNMP enable ﬂags will not change

the default local users created.

Automatically Start HT TPS

This indicates if HT TPS should be automatically started as part of system initialization.

HTTPS Port

If the application is to be started, then this is the listening port to use. The default is 443.

3. Web Console continued

3.8 Preferences continued

3.8.1 Preferences > Network continued

SMTP

The email settings are used to deﬁne a remote email relay server to use to send emails from the system. These settings also indicate what items to include in email notiﬁcations.

Figure 3-27: SMTP Preferences

Server Name

This deﬁnes the email relay server address information used for sending out email messages. If this is blank, email messages can still be sent, but will use a direct connection to the recipients email server.

If using direct connection, there must be a valid DNS server deﬁned and the DNS server must have a valid entry that points back to the card and is visible from the contacts destination server.

Port

This deﬁnes the port of the email relay server. This only is user if the Server Name is also speciﬁed. The default is 25.

Authentication Login Name

This is the login to use if authentication is required by the email relay server. It is not used if direct email is being used.

Authentication Password

If authentication is required by the email relay server, this is the password for the authentication login name. If an Authentication Login Name is speciﬁed, then the Authentication Password must also be provided.

From Address

This is the address that the email will be sent from. The default is poweralert@tripplite.com.

Subject

This is the information to be used as the “Subject” line in the message. The default is “PowerAlert Notiﬁcation”.

Include Triggering Event

This is a ﬂag to indicate if information about the triggering event should be included in the email message if it is available. Values are:

• Yes

Include the data in the email message.

• No

Do not include the data in the email message.

Include Device

This is a ﬂag to indicate if the device that the event occurred on should be included in the email message if it is available. Values are:

• Yes

Include the data in the email message.

• No

Do not include the data in the email message.

Include Host

This is a ﬂag to indicate if the host address for the event that occurred should be included in the email if it is available. Values are:

• Yes

Include the data in the email message.

• No

Do not include the data in the email message.

Include Location

This is a ﬂag to indicate if the device location for the event that occurred should be included in the email if it is available. Values are:

• Yes

Include the data in the email message.

• No

Do not include the data in the email message.

Digest MD5 Authentication Supported

This indicates if PowerAlert should authenticate with the email relay server using Digest MD5 Authentication.

CRAM MD5 Authentication Supported

This indicates if PowerAlert should authenticate with the email relay server using CRAM MD5 Authentication.

This indicates if PowerAlert should authenticate with the email relay server using Login Authentication.

Plain Authentication Supported

This indicates if PowerAlert should authenticate with the email relay server using Plain Authentication.

3. Web Console continued

3.8 Preferences continued

3.8.1 Preferences > Network continued

Internet

This menu can be used to monitor and alter IP v4 and IP v6 settings such as the addresses in use and the settings on system restart.

Changes made in this menu will require a system reboot.

Figure 3-28: Internet Preferences

3.8.2 Preferences > Security

This menu is used to deﬁne user-supplied Security preferences for individual log-ins, authentication methods, Radius servers, SSL and more.

Change Password

This menu allows individual users to change their password for security reasons. The user must enter their user name, current password, new password and then conﬁrm the new password.

You must press ‘Save’ in order for the changes to take effect.

Users

This menu allows for the deﬁnition and management of various users allowed to access various aspects of the network. There are a total of 12 available user slots.

Figure 3-30: User Menu

There are three levels of user access

•ReadOnly-Theusermayreadthedatabutmakenochanges.

•ReadWrite-Theusermaynotonlyreadthedatabutmakechanges

as well.

•None-Theuserhasnoaccesstothedatainthefacility

There are ﬁve pre-deﬁned users on the SNMPWEBCARD:

localadmin

This is the administrator account and has Read/Write access to all program areas. This user cannot be deleted or its facility access permission be modiﬁed, but the username and password may be changed from its default settings. The default password is same as the username. This user has SNMPv3 access.

Figure 3-29: Change Password

localmanager

This account has default access as Read/Write to all areas except to the security area of the program. The default password is same as the username. This user has SNMPv3 access.

localguest This account has only read access to Device Status, Logging, and Info areas of the program. The default password is same as the username. This user has SNMPv3 access.

public

This account is not a program user. It is only a SNMPv1 Read-Only community

tripplite

This account is not a program user; it is only a SNMPv2c Read/ Write community. This is the default community string that Tripp Lite’s PowerAlert Network Shutdown Agent uses to discover Tripp Lite SNMP devices on the network.

Users 6-12 are not deﬁned.

3. Web Console continued

3.8 Preferences continued

3.8.2 Preferences > Security continued

User Deﬁnition Menu Data

The following is the data that is used to deﬁne the local users. Not all data applies to all user types and will be identiﬁed accordingly.

SNMP Protocol

The SNMP Protocol is the ﬁrst attribute to be deﬁned for a user since it will needed to determine what data items will be populated for the user. The valid values are:

•None

This user does not have any SNMP access.

•SNMPv1

This user is a SNMPv1 community deﬁnition. Only access through SNMP is allowed for this user.

•SNMPv2c

This user is a SNMPv2c community deﬁnition. Only access through SNMP is allowed for this user.

•SNMPV3

This user has SNMPv3 access as well as access through any of the other view interfaces.

User Name

For users with no SNMP and SNMPv3 access, the user name is a string value 8 to 32 characters in length with no spaces.

Community

For SNMPv1 and SNMPv2 users, the community name is a string value 8 to 32 characters in length with no spaces. The only exception to the minimum length rule is the default community name “public.” If the public community is deleted, it can be re-added and will not need to follow the 8 character minimum rule.

Facility permissions

This deﬁnes the access permissions for the user. A pop-up box will be presented to choose the facilities. The facilities are ways of grouping permission for related pieces of data. A user may have access to all or only a subset of the data.

Default- This is used to provide the default access for program access for each user. When adding a new user the default, permissions are set to No Access.

The individual areas listed below override the default setting for that program area

Security- This is the security data such as local user, RADIUS hosts deﬁnitions and authentication method. By default, security access is given to only the localadmin us e r.

Network Settings- This is all the network data.

System Settings- This includes all of the system settings. By

default, access is given to localadmin and localmanager.

Info- Provides Read Only access to the about, help, and system IP address

Figure 3-31: Permissions

Logging- This facility allows access to logs and log rotation actions. Log rotation actions will only be available if the user has at least Read Only access to the Contacts facility.

Device Status- The facility provides access to all device variable information. These would include device status variables, personalization variables and threshold variables. By default, the localadmin and localmanager have ‘Read/Write’ access and localguest has only ‘Read Only’ access. Any user that will have any access to any other device data should have at least ‘Read Only’ permissions for this facility.

Device Control- This facility conﬁgures whether a user has access to device controls. Since this is a subset of devices, it is required that the user has ‘Read Only’ access to device status to either view or control loads. Conﬁguring this to no access will restrict a user from seeing the controls area of the program.

Device Events- This facility conﬁgures whether a user has access to device events. Since this is a subset of devices it is required that the user has ‘Read Only’ access to the device status and contacts facility to properly view or modify events. Conﬁguring this to No Access will restrict a user from seeing events program area.

Device Loads- This facility conﬁgures whether a user has access to device loads. Since this is a subset of devices it is required that the user has Read Only access to device status to either view or control loads. Conﬁguring this to No Access will restrict a user from seeing loads.

3. Web Console continued

3.8 Preferences continued

3.8.2 Preferences > Security continued

Actions- This facility is the program area that deﬁnes what will happen when an event/alarm is detected. Data used for actions is also included in this facility. This includes Email Recipients, SNMP Destinations and HT TP Contacts.

Schedules- To allow a user to add scheduled tasks requires that the user have Read/Write access to the device controls facilities.

Discovery- This facility is the program area that allows execution of a device discovery. This program area is most commonly used for detecting an Envirosense temp/humidity probe that has been connected to the SNMPWEBCARD after initial startup.

Any changes applied to a user or multiple users must be conﬁrmed by pressing the ‘Save’ button at the bottom of the page.

Facility Choice Examples

Administrative Permissions

The permissions for a user with administrator level clearance should have access to all of the data in the system. The only facility permission needed would be Default facility with Read/Write access. These are the permissions given to the “localadmin” user created upon initial startup.

Manager Permissions

The permissions for a user with manager level clearance should have access to all of the data except for the security related data. The permissions set for this should be Default facility with Read/Write access and Security facility with no access. These are the permissions given to the “localmanager” user created upon initial startup.

Guest Permissions

The permissions for a user with guest level permissions would be very limited. This type of user would only have read only access to Status and very basic system level information. The facility settings for this type of user would be:

•DefaultFacility–NoAccess

•InfoFacility–ReadOnly

•LoggingFacility–ReadOnly

•DeviceStatusFacility–ReadOnly

Outlet Realms

This is a comma separated list of integers, or range of integers, indicating which outlet realms this user may access. The access level to the realms indicated is Read Write. Each load may optionally be assigned to a realm. Whatever loads belong to the realms indicated here, the user may access. In order to correctly access the data, a user should have at least Read Only permission for Device Status and Device Loads to be able to user the realms.

ACL IP Address (Users with SNMP Access Only)

This deﬁnes from which IP Address (or Addresses when used with the ACL IP Mask) this user may access the data via SNMP.

ACL IP Mask (Users with SNMP Access Only)

This deﬁnes the Subnet Mask to use with the ACL IP Address to determine if an address is one from which the user is allowed to access the data via SNMP.

192.168.1.1 (single) 255.255.255.255

192.168.1.0 (range) 255.255.255.0

192.168.0.0 255.255.0.0

192.0.0.0 255.0.0.0 * (everyone) 0.0.0.0

Password (N/A for SNMPv1 or SNMPv2c)

This is the user password for logging in. For SNMPv3 users, this is also the Priv Password.

Auth Password (N/A for SNMPv1 or SNMPv2c)

For SNMPv3 Users only, this is the Auth Password.

Idle Timeout in Minutes (N/A for SNMPv1 or SNMPv2c)

This applies to data access other than SNMP which does not use the concept of a logged in session. This is the amount of time that the session can be idle before it will time out and no longer have access to the data. When the value is 0, an idle session will not time out.

Session Expiration Minutes (N/A for SNMPv1 or SNMPv2c)

This applies to data access other than SNMP which does not use the concept of a logged in session. This is the amount of total time that a session may last whether or not the session is idle or active. When the value is 0, the session will not expire.

These are the permissions given to the “localguest” user created upon initial startup.

Limited Outlet Access Permissions

A user may be given permission to read limited data and to be given update access to control only a subset of the outlets. The facility settings to give that kind of access would be the following permissions:

•DefaultFacility–NoAccess

•DeviceStatusFacility–ReadOnly

•DeviceLoadsFacility–ReadOnly

In addition to these facility settings, the user would need to assigned a set of outlet realms to specify the loads the user may control.

3. Web Console continued

3.8 Preferences continued

3.8.2 Preferences > Security continued

AAA Preferences

Authorization Scheme

The authorization scheme deﬁnes how user authentication will be done. The authorization can be done with locally deﬁned users only, RADIUS server deﬁned users only or a combination of the two. The valid values are:

•LocalOnly

The system only uses locally deﬁned user deﬁnitions.

•RADIUSOnly

The system uses RADIUS only for authentication.

•LocalThenRADIUS

The system uses locally deﬁned user deﬁnitions ﬁrst. If the user data is not found, it uses RADIUS for authentication.

•RADIUSThenLocal

The system uses RADIUS for authentication ﬁrst, if not authorized

via the RADIUS server, the locally deﬁned users will be used for authentication.

Accounting Scheme

This deﬁnes where the user session accounting data will be recorded. Like the authorization, the data can be recorded locally or on the RADIUS server or a combination of the two. The valid values are:

•LocalOnly

Use only the local system to record the session accounting data.

RADIUS Servers

Address

This deﬁnes the internet address of the RADIUS server.

Priority

This is a number that deﬁnes the priority of this RADIUS server

Shared Secret

This is the shared secret value to be used with this RADIUS server.

Authentication Port

This deﬁnes the port on the server to be used for authentication.

Accounting Port

This deﬁnes the port on the server to be used for accounting.

•RADIUSOnly

Uses only the RADIUS servers deﬁned to record the session accounting data.

•LocalThenRADIUS

Try to record the session accounting data locally and if not able to, then try to record to RADIUS.

•RADIUSThenLocal

Try to record the session accounting data on RADIUS ﬁrst and if fails, then record locally.

Figure 3-32: AAA Preferences

3. Web Console continued

3.8 Preferences continued

3.8.3 Preferences > System

This menu allows you to view and modify preferences throughout the system, including:

Accounting Logging

Figure 3-33: Accounting Logging

Application Logging

Data Logging

Figure 3-35: Data Logging

Event Logging

Figure 3-34: Application Logging

Figure 3-36: Event Logging

The Accounting, Data and Event log settings allow you to deﬁne the number of records to be stored and persisted across a reboot of the SNMPWEBCARD. Once the maximum number of records is reached, the data is cleared; however, logs can be either emailed or posted to an HTTP or HTTPS server when the log rotates (clears) so that an ongoing history of data can be kept.

The maximum number of entries that can be in the log before it is rotated is 2048. The valid values are integers between 64 and 2048. The default is 2048.

The action to take when the log is rotated can be speciﬁcally deﬁned via the menus. The log data may be archived to a single destination using email or HTTP.

3. Web Console continued

3.8 Preferences continued

3.8.3 Preferences > System continued

Remote Syslog

Figure 3-37: Remote Syslog

Date and Time

The SNMPWEBCARD supports a date and time conﬁguration via Simple Network Time Protocol (SNTP) or the on-board Real-Time Clock (RTC). Both the SNTP and RTC time are able to utilize the local time conﬁguration. Refer to Section 4.2.4.2 Time Settings for additional details on local time conﬁguration.

Changes on the Date and Time menus require a restart to take effect. Please use the Preferences > Restart menu if you are not prompted to restart after making changes. Refer to the Telnet or SSH Menu interface if you experience any issues conﬁguring date and time.

Watchdog

Figure 3-39: Watchdog

The Watchdog settings provide the user with the ability to set up timers that will reboot the card automatically if the Watchdog trigger is reached. This provides a mechanism to maximize the uptime/accessibility of the SNMPWEBCARD. The Watchdog tab allows enabling/disabling of either the Ping probe or NTP probe.

Primary Ping Target: Address/hostname (requires DNS settings to be conﬁgured).

Secondary Ping Target: Address/hostname (requires DNS settings to be conﬁgured) (optional).

Ping Probe Interval: Time in minutes before retry.

Probe Tries Before Fail: The number of attempts to ping the primary and

secondary IP addresses before the SNMPWEBCARD assumes there is a problem and reboots itself.

The SNMPWEBCARD will continue to reboot until it is successfully able to ping the primary or secondary IP address.

Primary NTP Target: Address/hostname (requires DNS settings to be conﬁgured).

Secondary NTP Target: Address/hostname (requires DNS settings to be conﬁgured) (optional).

Figure 3-38: Date and Time

NTP Probe Inter val: Time in minutes before retry.

Probe Tries Before Fail: The number of attempts to get time from the

primary and secondary NTP addresses before the SNMPWEBCARD assumes there is a problem and reboots itself.

3. Web Console continued

3.8 Preferences continued

3.8.3 Preferences > System continued

Miscellaneous

Figure 3-40: Miscellaneous

The Auto Ack setting allows for alarms that clear to be automatically removed from the Status-Alarms page. This is enabled by default. Disabling this feature will require that the alarms be manually acknowledged on the Status-Alarms page. This setting must be enabled if utilizing the PowerAlert Network Shutdown Agent.

3.8.4 Preferences > Restart

•Erasetheusercongurationandsystemlogdatabase

•ResettheRootpasswordbacktoTrippLite

Reset Users

Reset the default user settings, including clearing any RADIUS settings. The following are cleared by this option:

•AuthorizationSettings for authorizationandaccountingbothreset

to LOCAL ONLY

•RemovesallRADIUSServerdenitions

•Resets the local users to the 5 default users, localadmin,

localmanager, localguest, tripplite, and public.

•ResettheRootpasswordbacktoTrippLite

The restart menu provides the user with an interface to restart the SNMPWEBCARD.

If there has been a setting that requires a system restart, the message “Changes have been made that require a restart to take effect” will be displayed on this menu. This message can only be cleared with a restart. Changing the settings back to their original values cannot clear this condition.

A user can reset their PowerAlert (and SNMPWEBCARD) conﬁguration back to the factory defaults using this menu.

Press ‘Execute’ at the bottom of the page in order for the restart to take place.

Resets affect the following settings:

Factory Reset Settings

Reset all settings to the original factory defaults except for the SNMPWEBCARD network settings. Resetting those settings would potentially disable desired connections to the system. If necessary, the SNMPWEBCARD network settings can be reset by clearing the Advanced Settings following a factory reset using the serial CLI boot dialog, which is accessible as described in the SNMPWEBCARD Installation Manual.

The changes made for this request are:

•ResetNVRAMtohard-codeddefaults,resetsevery thingexcept

o - IPv4 choice of DHCP or Static

- IPv4 saved static Address, IPv4 Subnet Mask, IPv4 Gateway

- IPv6 DHCPv6 Enable / Disable setting

- IPv6 Static Enable / Disable setting

- IPv6 saved Static Address & Preﬁx Length

- User-conﬁgured DNS server.

Figure 3-41: Reset Users

3.9 Help

Figure 3-42: Help Menu

4. Telnet/SSH Console

Most of the monitoring and control features available in the Web console (see Section 3 – Web Console) are also available in the telnet and/or SSH console. Accessing the SNMPWEBCARD through the telnet console is ideal for mobile or resource-limited platforms.

Accessing the Telnet Console

Open a telnet client and connect to the IP number of the SNMPWEBCARD. At the login prompt, enter a valid user name and password. (A valid user is any user deﬁned locally via RADIUS server. Users deﬁned as SNMP communities with SNMP version V1 or V2 will not be allowed telnet access.) After a successful login, you’ll see the telnet console’s main menu (Figure 4-1).

The Telnet Console Interface

The telnet console uses a menu-driven, text-based interface. It has most of the same menus and submenus as the Web console, but they are arranged differently.

Each menu can be thought of as one of four types: navigation, summary, detail and data collection.

Navigation Menus

Navigational Menus allow a user to choose a path down the menu structure. Any data presented on these navigational menus are for information only and will require continuing down into a submenu to make any modiﬁcations.

Summary Menus

Data items that can have multiple instances will also have a summary menu. For example the Email Recipients will have a summary menu. The summary will display a row for each member with a subset of the data for that object.

From the summary, a user may enter an ID number from the list to view/ modify the detail menu for that item. If insert is allowed for the data, the user will be presented with the option to enter ‘0’ as well. When ‘0’ is chosen, the user is then automatically prompted to enter the individual detail menu items. Once all items have been entered, the user will be prompted to save the information, view the information, or abort the insert.

Detail Menus

The detail menus display the information about a collection of related individual data items. An example of a detail menu would the menu for a single Email Recipient. From the detail menu, a user will be given the option to choose to modify the individual data items. When allowed, deletes will be done from the detail menus.

Some detail menus will immediately update the data as entered and others will collect all the data changes and require the user to explicitly save the data in one operation. Those that require an explicit save will present an ‘A’ option to apply the changes. If a user has pending changes and attempts to leave the menu, an indication that the changes have not been saved will be presented and give the user the option to save or abort the changes.

Data Collection Menus

Data collection menus allow a user to enter values for an individual data item. For example, the menu to update an Email Recipient’s email address would be a data collection menu. These menus do not have any submenus.

Menu Permissions

The menu descriptions in this documentation will assume that the user has read/write permissions to all of the data. Not all users will have this level of authorization.

The data displayed and the options presented to a given user will be dependent upon that user’s permissions. A user will only be presented with data and options to the data that he or she is allowed to access. A more detailed discussion of user permissions can be found in the discussion on Local User deﬁnitions later in the document.

Note: The menu examples were generated using one speciﬁc device model. Because the content of many of the device speciﬁc menus will vary based upon the device and protocol, these are simply examples to give an idea of the type of data displayed here and how it is formatted. The contents on these menus should not necessarily be expected to be displayed unless it is explicitly stated that the setting apply for all device types.

Figure 4-1: Telnet Console Main Menu

Figure 4-2: Telnet Console Device Submenu

4. Telnet/SSH Console continued

Menus

Main Menu

The main menu is the starting menu when a user accesses the Telnet interface. It contains the entry point for all of the pieces of the system data. All other menus are accessible from the main menu.

To help keep the user informed about active alarms, the current list of active alarms is always displayed as part of the main menu.

------------------------------------------------------------------------------------------

-------- ALARMS --------------------------------------------------------------------

# Device Alarm Detail ACT ACK

--- --------- -------------------------------------- ------ ------

46 2 Temperature Beyond Limits Yes No 47 2 Humidity Beyond Limits Yes No 48 1 Output Off Yes No 49 1 Self Test Failed Yes No 50 1 Battery Age Above Threshold Yes No

-------- Main Menu -------------------------------------------------------------

1- Devices 2- System Configuration 3- Network Configuration 4- Alarms and Logging 5- About Q- Logout <ENTER> Refresh Menu

------------------------------------------------------------------------------------------

4. Telnet/SSH Console continued

4.1 Device Menu

If there is more than one device, the ﬁrst menu displayed for “Device” is a choice of which device's data you would like to present. The data on all of descendant menus will refer to the device chosen. If there is only one device, this choice is skipped and all descendant menus will obviously apply to the sole device.

In order to access the device menu structure the user must have at least read permission for the DEVICE STATUS facility. Any additional permissions needed in the submenus of this structure will be indicated for that menu.

Device List Menu

-------- Device List -----------------------------------------------------------

1- Device 1 (SMART750RM1U) 2- Probe (Envirosense) X/M- Return to Main Menu <ENTER> Refresh Menu -----------------------------------------------------------------

Device Main Menu

-------- Device 1 -------------------------------------------------------------

Device Name : Device 1 Location : Region : Vendor : TRIPPLITE Product : SMART750RM1U Protocol : 3003 Date Installed : 2011-07-31 State : CRITICAL Type : UPS Port Mode : RS232 Port Name : /com/1 Firmware Version : 2264 (Rev A) Serial Number : Device ID : 1280 Self Test Date : Self Test Status : Done and Pass

1- Status 2- Identification 3- Controls 4- Events 5- Loads 6- Preferences and Thresholds 7- Device Alarms 8- Logs X- Device List Menu M- Return to Main Menu <ENTER> Refresh Menu

4. Telnet/SSH Console continued

4.1 Device Menu continued

4.1.1 Status

This menu displays the status variables for the device. The values in this menu are not editable. The exact data shown on this menu will be device dependent.

Device Status Menu

-------- Device Status Menu ----------------------------------------------------

Device ====== Self Test Date : 2011-12-08 Self Test Status : Bad Battery - Replace

Battery ======= Battery Charge Remaining : 100 % Battery Voltage : 27.4 V Battery Temperature (C) : 33.9 C Battery Temperature (F) : 93.0 F Nominal Battery Voltage : 24 V Battery Age : 0.0 Years Battery Voltage Condition : OK

Input ===== Input Frequency : 59.9 Hz Input Voltage : 0.0 V Device Mode : Utility System Nominal Input Voltage : 0 V Tap State : Normal Minimum Input : Voltage : 0.0 V Maximum Input Voltage : 0.0 V Nominal Input Frequency : 60 Hz

Output ====== Output Source : Normal Output Load : 0 % Load State :

X- Device Main Menu M- Return to Main Menu <ENTER> Refresh Menu

4. Telnet/SSH Console continued

4.1 Device Menu continued

4.1.2 Identiﬁcation

This is the section of the device menus that will contain the information about the device. This information will be both user deﬁned settings such as device name or location and equipment speciﬁc information like vendor, product, and protocol. There are data items on this menu which will be displayed for all devices and some data displayed based upon the type and protocol for the device. Any data that is modiﬁable by the user will have a prompt option displayed on the menu.

Device Identiﬁcation Menu

-------- Identification --------------------------------------------------------

Device Name : Device 1 Location : Region : Vendor : TRIPPLITE Product : SMART750RM1U Protocol : 3003 Date Installed : 2011-07-31 State : CRITICAL Type : UPS Port Mode : RS232 Port Name : /com/1 VA Rating : 750 VA Firmware Version : 2264 (Rev A) Input Line Count : 1 Load Banks Total : 3 Load Banks Controllable : 2 Serial Number : Device ID : 1280

1- Name 2- Location 3- Region 4- Date Installed 5- Serial Number 6- Device ID X- Device Main Menu M- Return to Main Menu <ENTER> Refresh Menu

Menu Data

The following is the data that should be displayed for all devices.

Device Name

This is the user modiﬁable device name. The system will give the device a default name. The default for a UPS or PDU is “Device X” where X is the device id number. The default for an ENVIROSENSE is “Probe”.

Location The user deﬁned device location. There is no default for location.

Region The user deﬁned device region. There is no default for region

Vendor This is the manufacturer of the device.

Product This is the device model.

Protocol This is the protocol used by the device

Date Installed

This is the date that the device was installed. For UPS, this will be used for the battery installed date and is therefore modiﬁable.

State This is the current alarm state of the device. The valid values are:

• NORMAL

• INFORMATION

• WARNING

• STATUS

• CRITICAL

• OFFLINE

Typ e This is the device type. The valid values are:

• UPS

• PDU

• ENVIROSENSE

• AC

4. Telnet/SSH Console continued

4.1 Device Menu continued

4.1.2 Identiﬁcation continued

Port Mode

This is the connection mode of this device. The valid values are:

• RS232

• USB

• HID

Port Name

Name of the port this device is on.

4.1.3 Controls

This section of the menu is used to present the controls that are available for the device. When a control is chosen and it does not have any control data associated, the user will be prompted for veriﬁcation that they really wish to execute the control. Upon veriﬁcation, the control will be executed. If the control does have control data parameters associated with it, then that data will be presented when the control is chosen.

Note: To have access to the device control menus, the user must also have at least read permission for the DEVICE STATUS and DEVICE CONTROLS facilities.

Device Controls Menu

-------- Device Controls -------------------------------------------------------

1 Set Unit ID 2 Reboot SNMP Card 3 Shut Down Device 4 Reboot Device 5 Immediate Device Reboot 6 Initiate Self Test 7 Disable Watchdog 8 Enable Watchdog X- Device Main Menu M- Main Menu

+ 70 hidden pages