ManageUPSNET User Manual ManageUPS™NET User Instruction Manual UPS Network Managment Adapter Offering complete remote managagability via WEB, SNMP, or Telnet IMPORTANT SAFETY INSTRUCTIONS SAVE THESE INSTRUCTIONS. Please read and save these instructions. This manual contains important instructions for the ManageUPSNET Adapter. Follow these instructions during the unpacking, installation and maintenance of the.
Contents Contents Introduction ....................................................................................... 1 What's New in Version 2.6 ........................................................... 1 Total Manageability ..................................................................... 2 Using This Manual ....................................................................... 3 Technical Support ............................................................................... 3 Specifications ...
Contents User Names, Passwords, and Community Names ........................36 Ports ..........................................................................................36 Security Summary Table .............................................................37 Appendix A: Configuration File Description .......................................38 Appendix B: Sample Configuration File .............................................42 Appendix C: File Descriptions ..............................................
Introduction Introduction Thank you for purchasing ManageUPSNET. The ManageUPSNET Network manageability adapter is designed for use with ONEAC’s ON Series UPS products. ManageUPSNET based on the current state of RFC 1628 and provides an open approach to management of network AC power. What's New in Version 2.
Introduction CONSOLE Session Support CONSOLE session support for remote access via modem or terminal server provides Out-Of-Band access to all adapter and UPS configuration options. Network shutdown ManageUPSNET supports the MopNET protocol which allows MopUPS® shutdown software to monitor the UPS over a TCP/IP network.
Technical Support Using This Manual This manual uses the following conventions: • Individual hard key names that appear on the keyboard are in Helvetica font, small capital letters, enclosed in brackets. For example: [ENTER], [TAB], [RIGHT ARROW], [LEFT ARROW] • Words, phrases, abbreviations, and computer commands typed into a type-in field on the monitor screen are shown in bold courier font.
Specifications Specifications Table 1. Specifications for the ManageUPSNET Adapter SNMP SNMP UPS Agent conforms with SNMPv1 RFCs. Core Agent — supplied under license from SNMP Research, Inc.
Installation Installation Overview This section will take you through the process of installing the ManageUPSNET in the interface slot of an ON Series UPS. NOTE: Shielded 10Base-T cable should be used for both internal and external versions of manageUPS. Physical Installation Internal Adapter To install an optional interface card in an ON Series UPS: 1. Shut down all UPS-powered systems. Turn the UPS OFF and unplug it.
Installation 4. Refer to specific instructions provided in the Accessory Kit. 5. Plug the UPS in and turn it ON. External Adapter For applications where the auxiliary communications slot is unavailable, an external chassis for the Adapter can be used. Installing the External ManageUPSNET adapter is easy. Connect the port labeled UPS to the communications port on your UPS. Connect the universal external power adapter to an AC source and connect it to the 5V DC port on the back of the chassis.
Rear Panel Description Insert the tabs of the brackets into the slots on the bottom of the chassis. Tighten the screws provided and your adapter is ready for a neat and secure installation. NOTE: Make sure all earth connections are made to a single earth reference. Multiple earth potentials can result in ground currents flowing through serial cables that will interfere with the unit operation or damage circuits within the unit. The figure shown below is a rear panel view of the ManageUPSNET Adapter.
Rear Panel Description Table 2. Rear Panel Description RXD Receive Data This LED flashes when Ethernet packets are detected by the ManageUPSNET TXD Transmit Data This LED flashes when ManageUPSNET transmits an Ethernet packet LNK Link Integrity When lit, this LED indicates that the link integrity test pulse from the 10Base-T hub/concentrator is good. Basically, a valid physical network connection has been established.
Quick Start Quick Start Features ManageUPSNET offers many features that ease network management tasks of ON Series UPS systems. These features include: • Extensive UPS Configuration and Control functions available from an integrated web interface. • Email messages sent via SMTP in response to UPS related events. • An RS232 based console interface. • A remote console available via Telnet. • BOOTP and TFTP support.
Quick Start ht=ethernet:ha=002082000179: gw=198.186.180.1:hd=/tftpboot: bf=adapter.cfg:vm=rfc1048 This configuration sets the SNMP adapter interface as follows: IP address: 198.186.180.63 Subnet mask: 255.255.255.0 Default gateway: 198.186.180.1 Configuration file: /tftpboot/ adapter.cfg NOTE: This configuration file is optional. See Appendix A for more details on the file format. 2. Connect the adapter to the network. 3. The BOOTP server will provide the network settings to the adapter upon bootup. 4.
Quick Start ON F OF Fig 4. Dip Switch Settings 2. Run a terminal program such as HyperTerminal supplied with Windows. Configure the serial port with settings: 9600 baud, no parity, 8 data bits, 1 stop bit and no flow control. 3. Configure the Terminal program to send line ends with line feeds. 4. Type CONSOLE and press [ENTER]. 5. You will be prompted for a user name and password. Type “admin” for the user name and “admin” for the password. 6. Once you are logged in you will be presented with a menu.
Using SNMP Using SNMP Overview The Simple Network Management Protocol (SNMP) provides a means for transferring data between two devices. A Management Information Base (MIB) and MIB Object Identifiers (OIDs) are used by the two devices as the means of communication. The MIBs supported by the ManageUPSNET are described in Appendix D: SNMP MIBS and Appendix E: RFC1213 and Generic Trap Support.
Configuring MopNET Server Configuring Your NMS This section describes the process for configuring your SNMP based NMS to see and communicate with your UPS over the network. NOTE: This section addresses basic network management software issues. Due to the variety of SNMP network management software available, detailed information (e.g., specific NMS platforms) is not included in this manual. In summary, the MIB supplied with this product is compatible with most current SNMPv1 management tools.
Configuring MopNET Server required) without degrading the performance of the other entities in ManageUPS (SNMP, WEB or Telnet agents). Fig 5. MopNET Configuration Page The MopNET server authorizes client access based on the unique license key offered by the client at login. This activity is transparent to the system administrator and is typically configured in the MopUPS entity installed on the target PC. To enable multiple MopUPS clients on a single MopNET host, you will need multiple valid license keys.
Configuring Email Settings Configuring Email Settings Overview The ManageUPSNET can send an email message to up to 5 recipients when it detects various UPS related events. These are the same events that trigger the ManageUPSNET to send an SNMP trap. This feature is particularly useful in systems that do not use SNMP and therefore will not receive traps. A typical message will look like this: The UPS @ Computer Lab #3 is running on battery power. Line Voltage: 0 VAC Time On Battery: 5 sec.
Web Interface NOTE: This is the IP address NOT the host name, the ManageUPSNET does NOT support DNS. • SMTP Port: The port that the SMTP server is listening on, this is usually port 25. • Message From: The from email address that the UPS unit will use when sending email messages in response to an event. • Domain: The name of the domain that the UPS unit belongs to. • Email Notification (Enabled/Disabled): Email notification is disabled by default.
Web Interface Accessing the ManageUPSNET Using a Web Browser You can access the ManageUPSNET by entering the IP address of the adapter on the address line of your browser. Press [ENTER]. Fig 6. Web Browser Address Bar If you have configured your ManageUPSNET to use a port other than 80 then you must enter a colon and the port number after the IP address. See below for an example using port 280 instead of 80. Fig 7.
Telnet and Terminal Console Custom Links The ManageUPSNET allows four different types of user-definable links for linking the ManageUPSNET to other UPSs, networked devices, internal support and graphics. The four types of links are: Table 3. Type of Links Chain Links Used to create a chain between multiple UPS’s in a system. For example, if you have 10 adapters and this adapter was the 5th, you can use the two links to connect to adapters 4 and 6. This chain can then be repeated on the other adapters.
Telnet and Terminal Console the UPS are in the following positions: Dip switch 1 is in the down (OFF) position and DIP switch 2 is in the up (ON) position. ON F OF Fig 8. Dip Switch Settings 3. Open a terminal program such as HyperTerminal. Configure the session to 9600 baud, no parity, 8 data bits, 1 stop bit and no flow control. Also, configure the session to convert all Carriage Returns (CR) to Carriage Return LineFeeds (CRLF). 4. Type CONSOLE and press [ENTER]. 5.
File Transfers 2. The ManageUPSNET will ask you for a user name and password. The default user name is “admin”, the default password is “admin.” You can change the password once you have logged in. 3. You will be presented with an option screen where you can configure and control the ManageUPSNET and the UPS. File Transfers Overview The ManageUPSNET allows for all of its files to be downloaded, except the firmware file, and a few key files to be uploaded (see Appendix C, page 45).
File Transfers Upgrading Firmware Firmware File Description Firmware is the software running inside the ManageUPSNET that allows it to monitor the UPS and perform all of the tasks described in this manual. The file that is uploaded to the adapter is actually a compressed file containing the firmware file. This file is then decompressed, validated and then written over the firmware currently running on the adapter.
File Transfers was not changed from the default of 21 then supplying the port in the command line is optional. 6. The ManageUPSNET will ask you for a user name and password. The default user name is “admin” the default password is “admin.” Yours may be different. 7. Type the command “ftp> bin” and the press [ENTER]. The ManageUPSNET should respond with “ftp> 200 Command okay.” 8. Type in the command “put gz firmware.gz,” where is the local name and firmware.
File Transfers 2. Ensure that the adapter is also attached to the network and has already been configured with an IP address, Subnet Mask and a Default Gateway. The FTP server must also be enabled. 3. Open your browser, point it to the adapter. 4. The ManageUPSNET will ask you for a user name and password. The default user name is “admin” the default password is “admin”. Yours may be different. 5. Click the Administration option on the left side of the web interface.
File Transfers 9. The Web server will provide status pages during the file transfer. When the update is complete the browser will be redirected back to the main web interface page. Upgrade Using the Console and TFTP The following steps should be followed when updating the ManageUPSNET using the Telnet or Serial Console and TFTP. 1. Obtain the latest firmware(firmware260x.gz) from ONEAC and place it in a directory on your TFTP server. 2.
File Transfers 9. Select the Administration option from the Main Menu. This will display the Administration Menu. 10.Select the File Transfer option. This will display the File Transfer Menu. 11.Use this screen to enter the IP address of the TFTP server and the full path and file name of the firmware file. 12.Select the Initiate File Transfer using TFTP option to begin the File Transfer. 13.The Console will provide status information during the file transfer.
File Transfers 6. Select the Administration option from the Main Menu. This will display the Administration Menu. 7. Select the File Transfer option. This will display the File Transfer Menu. 8. Select the Initiate File Transfer using XMODEM option to begin the File Transfer. 9. Using the terminal program, select the firmware file (the firmware.gz file you received from ONEAC) to transfer via XMODEM. 10.The Console will provide status information during the file transfer.
File Transfers NOTE: You may notice that the lines using the put command have two file names specified. The first is the file to be uploaded the second is the name it will be given on the server. The second name must be firmware.gz for this to work properly. open 198.186.180.1 21 #open FTP connection to ManageUPSnet at 198.186.180.1 port 21 admin #user name admin #password put firmware260x.gz firmware.gz #upload the firmware file to the adapter disconnect #disconnect from ManageUPS open 198.186.
File Transfers Uploading Files Some of the files listed in Appendix C, page 45, can be uploaded to the ManageUPSNET using several different methods. This section describes the four methods which can be used to perform file uploads. Upload Configuration File Using BOOTP and TFTP This is described in section 5.2.1 Using BOOTP & TFTP. Upload File Using FTP 1. Ensure that the adapter is attached to the network and has already been configured with an IP address, Subnet Mask and a Default Gateway.
File Transfers 8. Type in the command “put filename1 filename2”, where filename1 is the local name of the file and filename2 is the name of a file described in Appendix C, page 45, press [ENTER]. The ManageUPSNET should respond with the following: 200Command okay. 150File status okay; about to open data connection for /. 250Requested file action okay, completed 1406bytes sent in 0.
File Transfers 7. Enter the IP address of the TFTP server in the Host Address field located in the top half of this page. Press the Apply button to save the setting. Fig 11. TFTP Host Address 8. Enter the full path and file name in the File Name field located in the center section of this page. Select “TFTP” from the Start Transfer using field. Press the Apply button to begin the File Transfer. Fig 12. File Transfer Dialog 9. The web server will provide status pages during the file transfer.
File Transfers 2. Ensure that the adapter is attached to the network and has already been configured with an IP address, Subnet Mask and a Default Gateway. The FTP server must also be enabled. 3. If you are using Telnet go to step 4, if you are using serial communications then skip to step 5. 4. Open your Telnet client and connect to the IP address of the ManageUPSNET adapter you wish to update. Skip to step 9. 5.
File Transfers complete and your connection will be lost. You must wait about 30 seconds before reconnecting. Scripting mass file uploads using FTP This section describes how to script mass file uploads from a Windows NT/95/98 computer using FTP. 1. Place all of the files you wish to upload into a directory named \Manageupsnet on your PC. The PC must be connected to the network. 2.
File Transfers put adapter02.def adapter.def #upload a default settings file to the adapter disconnect #disconnect from adapter open 198.186.180.2 21 #open FTP connection to ManageUPS at 198.186.180.1 port 21 admin #user name admin #password put adapter01.cfg adapter.cfg #upload a generic config file to the adapter put adapter03.cfg adapter.cfg #upload an adapter specific config file to the adapter put adapter02.def adapter.
File Transfers Download Files Using Web Browser and HTTP 1. Ensure that the adapter is attached to the network and has already been configured with an IP address, Subnet Mask and a Default Gateway. The HTTP server must also be enabled. 2. Open your browser. 3. Type in the URL of the file you wish to download in the address line of the browser and press [ENTER]. For example, typing “http://198.186.180.11/ adapter.cfg” on the address line would download the ManageUPSNET configuration file to the browser.
Security 5. The ManageUPSNET will ask you for a user name and password. The default user name is “admin” the default password is “admin”. Yours may be different. 6. Type the command “ftp> bin” and the press the [ENTER] Key. The ManageUPSNET should respond with “ftp> 200 Command okay”. 7. Type in the command “get filename”, where filename is the name of a file described in Appendix C, page 45, press [ENTER]. The ManageUPSNET should respond with the following: 200 Command okay.
Security User Names, Passwords, and Community Names User names and passwords are used for logging into the serial console, Telnet server, FTP server and the web interface. This information, as well as SNMP community names, are transmitted in plain-text over the network. This means that network sniffers can potentially determine the user name and passwords by monitoring network traffic to the device. This, unfortunately, is a limitation of the internet protocols themselves.
Security Security Summary Table The following table summarizes the ManageUPSNET’s security options. Table 4. Security Summary Table NMS IP filters Access Communities Server Enable/Disable Changeable Server Port User Name/Password Interface Type Comments Serial console X NA NA NA NA this is always enabled, but can only be accessed by physically connecting the adapter to a terminal with a serial communications cable.
Appendix A: Configuration File Description Appendix A: Configuration File Description The ManageUPSNET configuration file is an ASCII text based file which uses a “parameter = value” format to describe each entity. This file can be uploaded to the adapter using TFTP or FTP. The table below describes each possible entity. If an entity is missing from an uploaded file then that entity will simply not be updated in any way. Table 5.
Appendix A: Configuration File Description Table 5. Configuration File Description (Continued) Parameter Name chainLink0 chainLink1 Description 2 sets of 2 tuples, separated by semi-colons, specifying the Chain Links which are displayed on the main web interface screen. These tuples are: • Descriptive Name • URL of the link. Inactive link entries should include only the parameter name and equal sign (i.e.
Appendix A: Configuration File Description Table 5. Configuration File Description (Continued) Parameter Name Description smtpInfo 7 tuples, separated by semi-colons, describing SMTP settings used for sending email messages. These tuples are: • SMTP Server Address • SMTP port. • Email address of who the message is from, usually this would be something like ManageUPSnet@yourcompany.com. • Domain • Email Notification. 0=Disabled, 1=Enabled • On Battery Message Delay in seconds.
Appendix A: Configuration File Description Table 5. Configuration File Description (Continued) Parameter Name adminPassword Description The Admin user Password. Must also include adminUserName entry. resetCard Set to 1 to cause the adapter to reset after the settings have all been applied. mopnetInfo 2 tuples, separated by a semi-colon, used to specify the MopNET server port and if the MopNET server should be enabled (1) or disabled (0). mopnetLicense The MopNET License to be used by ManageUPSNET.
Appendix B: Sample Configuration File Appendix B: Sample Configuration File ip = 198.186.180.2 sm = 255.255.255.0 gw = 198.186.180.252 bootp = 0 sysName = Your UPS sysLocation = Computer Room sysContact = Joe x545 identName = Web Server UPS identAttachedDevices = Web Server snmpCommunity0 = public;0.0.0.0;READ snmpCommunity1 = private;0.0.0.
Appendix B: Sample Configuration File snmpTrapDest3 = snmpTrapDest4 = snmpTrapDest5 = snmpTrapDest6 = snmpTrapDest7 = snmpTrapDest8 = snmpTrapDest9 = snmpAuthenticateTraps = 2 chainLink0 = UPS 1;198.186.180.1 chainLink1 = UPS 3;198.186.180.3 customLink0 = Hub1 supplied by this UPS;198.186.180.10 customLink1 = Router supplied by this UPS;198.186.180.11 customLink2 = Hub2 supplied by this UPS;198.186.180.12 customLink3 = Your Companies Home Page;www.yourcompany.
Appendix B: Sample Configuration File emailDest0 = Support Person 1;supportperson1@yourcompany.com emailDest1 = Support Person 2;supportperson2@yourcompany.com emailDest2 = UPS Event Log;upseventlog@yourcompany.com emailDest3 = emailDest4 = tftpAddr = 198.186.180.
Appendix C: File Descriptions Appendix C: File Descriptions The following table is a list of the files stored on the ManageUPSNET. Table 6. File Description Upload(U)/ Download (D) File Name Description firmware.gz The compressed file containing the firmware currently running on the ManageUPSNET. U adapter.cfg The configuration file for the ManageUPSNET. This file uses the format described in Appendix A and B. UD adapter.def The default settings file for the ManageUPSNET.
Appendix C: File Descriptions Table 6. File Description (Continued) Upload(U)/ Download (D) File Name Description adminlinks.html Configuration of Custom Links. D adminabout.html Displays information about the ManageUPSNET. D filexferstatus.html File transfer status. D help.html On-line help. D helpalarms.html Ups alarm descriptions. D logout.html Logout page. D arrowdown.gif Graphic image D arrowright.gif Graphic image D exclamation.jpg Graphic image D warning.
Appendix D: SNMP MIBS Appendix D: SNMP MIBS About UPS MIBS (RFC1628) In May 1994, RFC1628 was published. This Request For Comments (RFC) is an Internet Proposed Standard that defines a portion of the Management Information Base (MIB) for use with network protocols in the internet community. In particular, it defines objects for managing uninterruptible power supply (UPS) systems. This is significant in many ways.
Appendix D: SNMP MIBS chosen to name the SNMPv1 translation of RFC1628 — 1628_V1.MIB. This is the MIB you will find on the supplied disk in the MIBS directory and it is the MIB you should load into your NMS. A copy of RFC1628.TXT (the Internet distribution format) has been included on the disk for your information. This is a text file with the UPS MIB written in Abstract Syntax Notation One (ASN.1) format. One of the fundamental SNMP axioms is — extensibility.
Appendix D: SNMP MIBS Table 7. RFC1628 Support upsIdent Group upsIdentManufacturer US Manufacturer upsIdentModel The model designation of the UPS upsIdentUPSSoftwareVersion xx.x format (x = 0 to 9) upsIdentAgentSoftwareVersion xx.xx format (x = 0 to 9) upsIdentName. Default: Not set (upsIdentName) upsIdentAttachedDevices Default: Not set(upsIdentAttachedDevices) upsBattery Group upsBatteryStatus The status of the UPS battery upsSecondsOnBattery Normally 0.
Appendix D: SNMP MIBS Table 7. RFC1628 Support (Continued) upsOutput Group upsOutputSource Supported values: normal(2), battery(4), booster(5). upsOutputFrequency Measured average. upsOutputNumLines Number of phases. This is one for single phase UPS’s. upsOutputTable upsOutputVoltage True RMS voltage measurement. upsOutputCurrent The present output current. upsOutputPower Represents actual output watts. upsOutputPercentLoad Values from 0 to about 141% are supported.
Appendix D: SNMP MIBS Table 7. RFC1628 Support (Continued) upsAlarm Group (continued) upsAlarmBypassBad Not applicable. upsAlarmOutputOffAsRequested Confirmation. upsAlarmUpsOffAsRequested Confirmation. upsAlarmChargerFailed Battery charger has failed or its fuse has blown. upsAlarmUpsOutputOff Confirmation, persistent until output is turned on. upsAlarmUpsSystemOff UPS shutdown. upsAlarmFanFailure Not supported. upsAlarmFuseFailure Input circuit breaker is open or charger fuse has blown.
Appendix D: SNMP MIBS Table 7. RFC1628 Support (Continued) upsTest Group (continued) upsTestElapsedTime This object is updated while a test is in progress. Once a test is complete, this object will contain the total elapsed time of the test in 100ths of seconds. upsWellKnownTests The OID values for the following objects are what the upsTestID object is SET to in order to initiate a given test. upsTestNoTestsInitiated If no tests are currently being run, then the value of upsTestId will equal this OID.
Appendix D: SNMP MIBS Table 7. RFC1628 Support (Continued) upsConfig Group (continued) upsConfigOutputPower The following objects in the UPSConfig group are read-write. UpsConfigLowBattTime Valid settings for UPSConfigLowBattTime are between 0 and 99. This is the amount of time before battery exhaustion that the low battery alarm will begin to sound. upsConfigAudibleStatus Valid settings for UPSConfigAudibleStatus are disabled(1) and enabled(2).
Appendix D: SNMP MIBS Table 7. RFC1628 Support (Continued) upsTraps Group (continued) upsTrapAlarmEntryAdded When an alarm condition is detected in the UPS, this trap is sent. Some conditions may cause multiple traps to be sent. For example, when AC power goes out of rated limits and the UPS goes on battery, the upsTrapOnBattery trap and upsTrapAlarmEntryAdded trap (upsAlarmInputBad) will be sent. upsTrapAlarmEntryRemoved Sent after a given alarm condition is no longer detected.
Appendix D: SNMP MIBS ONEAC Private Extension MIB This section details information about ONEAC’s Private Extensions UPS MIB. This MIB is also provided in the SNMP Agent and use of it is optional. ONEACXT.MIB is the name of this MIB and it is found in the MIBS directory on the ONEAC SNMP Diskette. NOTE: This information is in addition to the descriptions provided in the MIB. Table 8.
Appendix D: SNMP MIBS Table 8. Private Extension MIB oneacUpsControl Group (continued) oneacUpsControlRemoteResetPassword This variable must be supplied with the SNMP adapter access password in order to permit the SNMP agent to be reset. This is the same password used for telnet access and local serial port access via the MENU command. Note that the remote access password must be changed from its default value to work; using the default remote access password is not permitted and will result in an error.
Appendix D: SNMP MIBS Table 8. Private Extension MIB oneacUpsStatus Group (continued) oneacUpsDipSwitches A hexadecimal representation of the current setting of the DIP switch located at the rear of the UPS. oneacUpsBattLastRun The number of seconds the UPS was run on inverter on its previous run. oneacUpsStatusIndicators A hexadecimal representation of the current state of the buzzer and the three LED’s located on the front panel of the UPS.
Appendix E: RFC1213 and Generic Trap Support Appendix E: RFC1213 and Generic Trap Support This section lists the groups and objects in RFC1213 (aka: MIB-II or MIB-2) that are supported by the ManageUPSNET. In all, 135 scalar objects and table entries are supported. Table 9.
Appendix E: RFC1213 and Generic Trap Support Table 9.
Appendix E: RFC1213 and Generic Trap Support Table 9.
Appendix E: RFC1213 and Generic Trap Support Table 9.
Appendix E: RFC1213 and Generic Trap Support Table 9.
Appendix E: RFC1213 and Generic Trap Support Generic Trap - PDU Support RFC1157 defines 7 Generic Trap-PDUs. The following are applicable and supported by the ONEAC SNMP Agent. NOTE: Traps of any type will not be sent unless a trap destination receiver(s) is configured Table 10. Generic Trap -PDU Support coldStart The following conditions cause this trap to be sent: When power is applied to the interface.
Appendix F: Pass-through Mode Appendix F: Pass-through Mode The pass-through mode can be used for Out-Of-Band access or local serial monitoring. Both internal and external versions of the ManageUPSnet adapter allow the re-use of the UPS serial port for other utilities that need to communicate serially with the UPS. In pass-through mode, ManageUPS suspends its conversation with the UPS and yields the port to the external entity.
