HPOV UPS NMS Release 2 This README FILE is about installing and using OV UPS PACK. First section about installing Second section about using Third section about internals Fourth section gives overview of applications 1. Installing this software =========================== This UPS management software requires the HP OpenView application Network Node Manager version 6.1 and HP-UX 10 or 11. The platform should be up and running. If neccesary run /opt/OV/bin/ovstart to start the platform. It's no problem if one or more ovw sessions are active. Menuchanges however will only be seen when ovw is restarted. To install this UPS management software, log in as root and change directory to /opt/OV/contrib/NNM/ cd /opt/OV/contrib/NNM/ if you don't have the /opt/OV/contrib directory, you probably don't have OpenView installed. Update to this version first. Load the software from tape using the tar command: tar xvf where is the device file of your tapeunit (probably /dev/rmt/0m ) Next run the install command to configure the software in the OpenView platform. cd mg; ./install As the messages flash by, you will see the product configuring itself. The product can be installed using the install script ./install The product can be removed withe -remove option to the install script: ./install -remove 2. Using the UPS Management software ==================================== This software provides the following functionality: a. MGE UPS Devices will be automatically discovered by OpenView and drawn on the OpenView windows graphical map with a special symbol. (if this does not seem to work, try use the Fault->Poll Node menu. If the UPS have already been discvered use the following cookbook to get the right symbols: Stop ovw ovstop netmon ovtopofix -a ovtsrta netmon b. The status of the UPS device can be seen on the OpenView map. As long as the symbol is green, the UPS can be managed from OpenView. This doesn't mean that the UPS is functioning correctly! Checking the UPS functionality and status will be described below c. Several Monitoring applications are available through the monitor->UPS menu options. (These choice are only available if a UPS symbol is selected on the graphical map). These applications are for checking status and power levels. An overview of the available UPS applications can be found on the help->help on application menu choice. The ups applications all start with the letters mg. See section 4 for an overview of application in the menu. d. Two administer applications have been made for checking the SNMP configuration. See section 4 for an overview of application in the menu. e. Traps sent by the UPS will be picked up by the OpenView event system and can be seen on a special category on the event-browser: UPS events. Depending on the severity of the trap a additional action will be performed. The severity of the traps and the message that will appear in the event- browser can be customized through the event configurator located beyond the options menu. Be carefull not to change the executed command because the command shown will take care of the acknowledgement of the traps. The only actions currently implemented are a message window and a status change when a power failure/restoration occur. However user defined actions can be added in the file $OV_CONTRIB/NNM/mg/actions/trap.action. Please refer to the Addendum section to see which actions are already implemented in the trap.action file. Whenever a "UPS on battery trap" is received, a special bell-signal and a voice saying "UPS on battery" can be heard. (Works only if audio is configured) 3. Internals ============= The install script performs the following actions: a. copy Mib into place The MG mib will be copied to the OpenView standard MIB directory: $OV_SNMP_MIBS b. register fields for MGE UPS The following fields are inserted in the following config files: file field inserted atribute $OV_FIELDS/C/snmp_fields SNMPAgent UPS Agent $OV_FIELDS/C/ovw_fields vendor MGE-UPS c. register symbol The symbol registration file $OV_SYMBOLS/C/Device will be extended with the definition of a special device called UPS. d. copy bitmaps into place The bitmaps for the UPS device will be copied into place. ( a picture of a car-battery is made as a symbol for the UPS) Next to this OpenView will compile the new definitions into binary format. e. Updating SNMP tables Several OpenView tables will be updated so OpenView knows that the object id that it receives, belongs to a UPS device from the Vendor MGE. f. Installing applications. The SNMP applications will be copied into place and will be in the OpenView menu system the next time ovw is started. See section 4 for an overview of applications g. Trap definitions will be installed The new trap definitions will be installed to the OpenView event system. Every time a trap is received, the command $OV_CONTRIB/NNM/actions/trap.action is executed. This script takes care of the acknoledgement of the trap by executing the command $OV_CONTRIB/NNM/actions/acknowledge. For this to work correctly the set community name of the UPS device has to be configured using the options->snmp configuration menu choice. h. Loading the Mib Finally the Mib will be loaded into the OpenView system. i. Logfiles There are two new logfiles in the $OV_CONTRIB/NNM/mg/log directory: action.log logs all actions snmpset.log logs all acknowledgements 4. Overview of applications in menu ==================================== Monitor->UPS->General General information about the UPS (version etc) Monitor->UPS->OutputLoad Graphical information about output-load Monitor->UPS->Battery Level Graphical information about battery level and remaining time. Monitor->UPS-Analysis->Input Input voltage and frequency Monitor->UPS-Analysis->Output Output voltage and frequency Monitor->UPS->Status->Battery Status screen of battery Monitor->UPS->Status->EnvironmenStatus screen of environment Monitor->UPS->Status->Input Status screen of input Monitor->UPS->Status->Output Status screen of output Administer->UPS->Agent Conf Configuration of SNMP Agent (adresses etc) Administer->UPS->Managers Table of managers Please note that you may need to use a chmod so that these files can be executed by HPOV.