Transcription

PowerNetManagementInformation Base(MIB)Version 3.4.4Reference Guide

REFERENCE GUIDE: POWERNET MANAGEMENT INFORMATION BASE (MIB), VERSION 3.4.4AMERICAN POWER CONVERSION CORPORATION - SOFTWARE LICENSE AGREEMENTThis software license agreement (the “agreement”) is a legal agreement between American Power ConversionCorporation as the “licensor” (hereafter referred to as APC) and you (hereafter referred to as the “customer”) forthe APC software accompanying this agreement.By downloading, installing, loading, copying, or otherwise using the software, you represent that one of thefollowing is true: You have been authorized to accept these terms on behalf of the customer (the entity on whose behalf yourepresent that you are authorized to act). You intend to be personally bound to the terms of this agreement as the customer.If you accept these terms as a representative of an entity on whose behalf you are authorized to act, you may usethe software only on behalf of such entity. If you intend to be personally bound, use of the software is limited to yourpersonal use.If you are not authorized to accept these terms on behalf of a company or other entity, and you do not intend to bepersonally bound, APC will not license the software.Installation or use of the software in violation of the terms of this agreement is a violation of U.S. and internationalcopyright laws and conventions.If third-party software is provided with the APC software, that third-party software is not subject to the terms of thislicense agreement. The license agreement of that third-party software defines the responsibilities of the customerand licensor with regard to that software.1. GRANTOFLICENSEAPC hereby agrees to grant and customer agrees to accept a non-exclusive and non-transferable license to usethe software, subject to the terms and conditions of this agreement. The software is owned and copyrighted byAmerican Power Conversion Corporation or its suppliers. As a customer, your license confers no ownership of ortitle to the software and does not constitute a sale of any right in the software. APC retains all proprietary rights andtitle to the software and any modifications.The customer is not permitted to rent, lease, grant a security interest in, or otherwise transfer rights to the software,or remove or alter any trademark, logo, copyright or other proprietary notices, legends, symbols or labels in thesoftware.2. RIGHTTOUSEThe software is licensed for use only by the number of users and/or on the number of servers or workstationsdescribed in this “Right to Use” section of this agreement or in any related invoice.The customer may use this software in one of the following ways, whichever is applicable to this software: On a single file server powered by an APC UPS for serving any computer and related peripheral devicesconnected with that single file server On one or more computers powered by the same APC UPS To support a web server, which may be connected to a varying but unlimited number of workstations orcomputers on one or more networks. To support any licensed copy of the PowerNet Agent.3. RIGHTTOCOPYThe customer may make copies of the software for the following purposes only: The customer may make one copy of the software for archival or backup purposes. The customer may make additional copies of the software and documentation only when essential for theauthorized and intended use of the software as described in this agreement and/or in the documentationaccompanying the software.Any and all copies, including any archival copy, must include the APC copyright notice and any other proprietarynotices that are included with the licensed software, and are fully subject to the terms of this agreement.The customer may not redistribute the software or make copies with the intent to redistribute.PowerNet MIB Reference Guideii

4. RESTRICTIONSThe customer is not permitted to do any of the following: Reverse assemble, reverse compile, or otherwise attempt to create the source code from the software. Create derivative works of the software or any portion thereof. Localize or translate the software or its documentation, without the prior written consent of APC. Publish or provide any results of benchmark tests run on the software to a third party without the prior writtenconsent of APC.5. DURATIONANDTERMINATIONOFTHIS AGREEMENTThis license shall continue so long as the customer uses the software in compliance with the agreement. If thecustomer breaches any of its obligations, this license shall terminate, and the customer agrees to destroy or returnall copies of the software and all materials provided for or with the software upon notification and demand by APC.The customer can terminate the agreement at any time by destroying or returning to APC all copies of the softwareand documentation.6. LIMITED WARRANTYThe APC limited warranty is for a period of ninety (90) days from the time the customer receives the software.APC warrants during the limited warranty period that the software will function materially as described in theaccompanying software user documentation and that any medium upon which the software is delivered will be freefrom defects in material and workmanship when given normal, proper and intended usage.This warranty does not apply in any of the following circumstances: If the software is used on a machine or operating system other than the machines and versions of operatingsystems specified in the documentation. If the software is subjected to misuse, neglect, accident, or exposure to environmental conditions beyondthose specified in the documentation. If a version of the software is used that does not include all updates available from APC. If the software has been modified.APC does not warrant that use of the software will be uninterrupted or error free, nor that program errors will becorrected.APC’s sole responsibility and customer’s sole remedy under this warranty is, at APC’s option, to repair or replaceall or any portions of the software, or to refund any license fee paid. This limited warranty is valid only if APCreceives written notice within the ninety-day warranty period.7. LIMITATIONOFWARRANTIESANDLIABILITYEXCEPT AS EXPRESSLY SET FORTH IN SECTION 6 HEREIN ENTITLED “LIMITED WARRANTY”, (i) APCSHALL HAVE NO LIABILITY TO THE CUSTOMER OR ANY THIRD PARTY FOR THE SOFTWARE, INCLUDINGANY LIABILITY FOR NEGLIGENCE; (ii) APC MAKES AND THE CUSTOMER RECEIVES NO WARRANTIES,EXPRESS, IMPLIED, STATUTORY, OR IN ANY OTHER PROVISION OF THIS AGREEMENT OR ANY OTHERCOMMUNICATION; AND (iii) APC SPECIFICALLY DISCLAIMS ANY WARRANTY OF MERCHANTABILITY,FITNESS FOR A PARTICULAR PURPOSE, TITLE AND NON-INFRINGEMENT.IN NO EVENT SHALL APC BE LIABLE TO THE CUSTOMER FOR ANY CONSEQUENTIAL, INDIRECT,SPECIAL, MULTIPLE OR INCIDENTAL DAMAGES, EVEN IF APC HAS BEEN ADVISED OF THE POSSIBILITYOF SUCH POTENTIAL LOSS OR DAMAGE.SOME STATES OR JURISDICTIONS DO NOT ALLOW THE EXCLUSION OF IMPLIED WARRANTIES ORLIMITATION OF INCIDENTAL OR CONSEQUENTIAL DAMAGES, SO THE ABOVE LIMITATION OREXCLUSION MIGHT NOT APPLY TO YOU. HOWEVER, TO THE FULL EXTENT PERMITTED BY APPLICABLELAW, THE DURATION OF STATUTORILY REQUIRED WARRANTIES, IF ANY, SHALL BE LIMITED TO THEWARRANTY PERIOD OF 90 DAYS.NO DEALER, AGENT, EMPLOYEE, OR CUSTOMER OF APC IS AUTHORIZED TO MAKE ANYMODIFICATIONS, EXTENSIONS, OR ADDITIONS TO THIS LIMITED WARRANTY. The cumulative liability ofAPC to the customer for all claims relating to the software shall not exceed the total amount of any and all licensefees paid to APC by the customer for the software or, if no license fee was required, the replacement of thesoftware.PowerNet MIB Reference Guideiii

8. NO WARRANTY UNDER HAZARDOUS, HIGH-RISK,ORLIFE-THREATENING CONDITIONSThe software is not fault-tolerant and is not designed, manufactured or intended for use or resale as controlequipment in hazardous environments requiring fail-safe performance, such as in the operation of nuclear facilities,aircraft navigation or communication systems, air traffic control, direct life support machines, or weapons systems,in which the failure of the software could lead directly to death, personal injury, or severe physical or environmentaldamage. Accordingly, APC and its suppliers specifically disclaim any express or implied warranty of fitness for suchhazardous, high-risk, or life-threatening activities.9. USEOFTECHNICAL INFORMATION RELATEDTOCUSTOMER SUPPORTThe customer agrees that APC may use technical information that the customer provides while receiving technical/customer support services. APC may use such information for its own business purposes, including productsupport and development, but agrees not to use such information in any form that might identify the customer.10. TRANSFER RESTRICTIONSThis agreement, the license granted hereunder, the software and any modifications thereto may not be assignedor in any way transferred without the prior written consent of APC.11. LANGUAGEAND JURISDICTION OF THEAGREEMENTThe original of this agreement has been written in English. The parties hereto waive any statute, law, or regulationthat might provide an alternative law or forum or to have this agreement written in any language other than English.Any translation of this agreement to a language other than English is provided only for the convenience of thecustomer and is not the legally binding version of the agreement.The terms of this agreement shall be construed in accordance with the substantive laws of the Commonwealth ofMassachusetts, United States of America, without giving effect to the principles of conflict or choice of law of suchcommonwealth. APC and Customer exclude the United Nations Convention on Contracts for the International Saleof Goods from this agreement.12. U.S. GOVERNMENT RESTRICTED RIGHTS LEGENDThe software and documentation are “commercial items” as that term is defined in 48 C.F.R. 2.101 (October 1995)consisting of “commercial computer software” and “commercial computer software documentation” as such termsare used in 48 C.F.R. 227.7202-1, 227.7202-3 and 227.7202-4 (June 1995). If the customer is the U.S.Government or any agency or department thereof, the software and documentation are licensed only as acommercial item, and with only those rights as are granted to all other end users pursuant to the terms andconditions of this agreement. Licensor is American Power Conversion Corporation, P.0. Box 278, 132 FairgroundsRd., West Kingston, RI 02892, U.S.A.13. EXPORT CONTROLSNone of the software or underlying information or technology may be downloaded or otherwise exported or reexported to any of the following: Into (or to a national or resident of) any country to which the U.S. has embargoed goods. To anyone on the U.S. Treasury Department’s list of Specially Designated Nationals. To anyone on the U.S. Commerce Department’s Table of Denial Orders.By downloading or using the software, the customer agrees to the foregoing and represents and warrants that it isnot located in, under the control of, or a national or resident of any such country or on any such list.The customer is responsible for complying with any local laws in its jurisdiction that might impact its right to import,export or use the software, and represents that it has complied with any regulations or registration proceduresrequired by applicable law to make this license --------------AMERICAN POWER CONVERSION CORPORATIONCORPORATE HEADQUARTERS:132 Fairgrounds RoadP.O. Box 278West Kingston, RI 02892United States of AmericaTelephone: 401-789-5735Toll Free (US and Canada): 800-800-4272PowerNet MIB Reference Guideiv

ContentsAbout This Guide1Guide Purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Guide Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Related Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Terms Used in This Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Chapter 1: PowerNet MIB Structure11223PowerNet MIB Traps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3PowerNet MIB OIDs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3SNMP Access Controls 4SNMP Browser Structure 4PowerNet MIB OIDs Structure 4Tabled OIDs 5Chapter 2: How to Manage Agents and Management Cards6How to Monitor a PowerNet Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6[powerNetSoftwareSystem] 7[powerNetSoftwareConfig] 7How to Manage the SNMP Agent at a Hardware Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7[mcontrol] 8[mconfig] 8[mtrapargs] 9[mfiletransfer] 9[mfiletransferStatus] 9[mfiletransferConfig] 10[mfiletransferControl] 10Chapter 3: How to Manage a UPS11How to Monitor a UPS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12[upsIdent] UPS Identification OIDs 12[upsBasicIdent] 12[upsAdvIdent] 13[upsBattery] UPS Battery OIDs 13[upsBasicBattery] 13[upsAdvBattery] 14[upsComm] UPS Communication OID 14[upsInput] UPS Input OIDs 14[upsBasicInput] 14[upsAdvInput] 15[upsOutput] UPS Output OIDS 16[upsBasicOutput] 16[upsAdvOutput] 17PowerNet MIB Reference Guidev

How to Control a UPS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .[upsControl] OIDs 17[upsBasicControl] 17[upsAdvControl] 18How to Configure a UPS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .[upsConfig] 20[upsBasicConfig] 20[upsAdvConfig] 21How to Test a UPS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .[upsTest] 23[upsAdvTest] 23How to Use OIDs for 3-Phase UPS Models . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .[upsPhaseResetValues] 25[upsPhaseInput] 26[upsPhaseOutput] 27Chapter 4: How to Manage an Environmental Monitor1720232528External Environmental Monitor (em) OIDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28[emIdent] OID 28[emConfig] OIDs 29[emConfigProbes] OIDs 29[emConfigContacts] OIDs 30[emStatus] OIDs 30[emStatusCommStatus] OID 30[emStatusProbes] OIDs 31[emStatusContacts] OIDs 31Integrated Environmental Monitor (iem) OIDs (AP9618 or AP9619 Network Management CardOnly) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32[iemIdent] OID 32[iemConfig] OIDs 32[iemConfigProbes] OIDs 33[iemConfigContacts] OIDs 33[iemStatus] OIDs 34[iemStatusProbes] OIDs 34[iemStatusContacts] OIDs 35[iemStatusRelays] OIDs 35Measure-UPS (mUps) OIDs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35[mUpsEnviron] Environment OIDs 36[mUpsContact] Contact OIDS 36Chapter 5: How to Manage a MasterSwitch Unit37[sPDUIdent] Identification OIDS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .[sPDUMasterControl] Master Control OIDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .[sPDUMasterConfig] Master Configuration OIDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .[sPDUOutletControl] Outlet Control OIDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .[sPDUOutletConfig] Outlet Configuration OIDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .PowerNet MIB Reference Guidevi3839404142

Chapter 6: How to Manage a MasterSwitch VM Unit43[sPDUIdentVM] Identification OIDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .[sPDUMasterControlVM] Master Control OIDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .[sPDUMasterConfigVM] Master Configuration OIDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .[sPDUMasterStatusVM] Master Status OIDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .[sPDUOutletControlVM] Outlet Control OIDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .[sPDUOutletConfigVM] Outlet Configuration OIDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .[sPDUOutletStatusVM] Outlet Status OIDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Chapter 7: How to Manage a MasterSwitch Plus Unit51[sPDUIdentMSP] Identification OIDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .[sPDUMasterControlMSP] Master Control OIDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .[sPDUMasterConfigMSP] Master Configuration OIDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .[sPDUMasterStatusMSP] Master Status OIDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .[sPDUOutletControlMSP] Outlet Control OIDs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .[sPDUOutletConfigMSPall] Outlet Configuration OIDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . .[sPDUOutConfigMSPgs] Outlet Configuration OIDS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Example of a “Load-Shedding” Configuration 58[sPDUOutConfigMSPannun] Outlet Configuration OIDS . . . . . . . . . . . . . . . . . . . . . . . . . . . .[sPDUOutConfigMSPmups] Outlet Configuration OIDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . .[sPDUOutletStatusMSP] Outlet Status OIDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Chapter 8: How to Manage an Automatic Transfer Switch5253545455565660616364[atsIdent] Identification OIDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .[atsCalibration] Calibration OIDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .[atsControl] Control OIDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .[atsConfig] Configuration OIDs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .[atsStatus] Status OIDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .[atsStatusInput] Input OIDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .[atsStatusOutput] Output OIDs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Chapter 9: PowerNet MIB Traps444545474849506566676768707274Trap Severity Levels. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .How To Define Trap Receivers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .PowerNet MIB Trap Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Symmetra UPS Subtraps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .PowerNet MIB Reference Guidevii75757685

About This GuideThis introduction provides the following information to help you use this guide. Guide Purpose Guide Structure Related Documents Terms Used in This GuideFor assistance with this or any other APC product, contact APC Worldwide Customer Support asdescribed at the end of this manual.Guide PurposeThis guide describes how to use the PowerNet management information base (MIB), version 3.4.4, tomanage APC products that allow or enable using simple network management protocol (SNMP) formanagement: MIB version 3.4.4 management of a Management Card, UPS, and an Environmental Monitor MIB version 2.2-compatible management of a version 2.2 Agent, its UPS, and anEnvironmental Monitor MIB version 3.4.4 management of an APC MasterSwitch AC Power Controller, aMasterSwitch VM AC remote control PDU, or a MasterSwitch Plus AC remote control PDU MIB version 3.4.4 management of an APC Automatic Transfer Switch and its embeddedNetwork Management Card.Guide StructureThis guide’s chapters describe how to use the PowerNet MIB: Chapter 1, PowerNet MIB StructureProvides an overview of the PowerNet MIB, its Object Identifications (OIDs) and its traps(messages that alert a network management station [NMS] about specific conditions). Chapter 2 through Chapter 8Describe how to use PowerNet MIB OIDs to manage specific products:-Chapter 2, How to Manage Agents and Management Cards-Chapter 3, How to Manage a UPS-Chapter 4, How to Manage an Environmental Monitor-Chapter 5, How to Manage a MasterSwitch Unit-Chapter 6, How to Manage a MasterSwitch VM Unit-Chapter 7, How to Manage a MasterSwitch Plus UnitPowerNet MIB Reference Guide1

About This GuideRelated Documents Chapter 8, How to Manage an Automatic Transfer SwitchChapter 9, PowerNet MIB TrapsDescribes the PowerNet MIB traps and how to define which NMSs can receive those traps.Related DocumentsThis guide describes how to use the PowerNet MIB only. For information about an APC product thatyou manage using the PowerNet MIB, see the user’s guide or owner’s manual for that product. Seeyour network management system (NMS) documentation for information about your NMS.Terms Used in This GuideTerms used in this guide have the following definitions:Term Used in This GuideManagement CardDefinitionUnless otherwise stated, Management Card refers toany of the following devices: Any PowerNet Adapter with model numberAP9205, AP9605, or AP9603 Any Web/SNMP Management Card Any Network Management CardPowerNet Agent, or AgentAny PowerNet AgentEnvironmental MonitorUnless otherwise stated, Environmental Monitorrefers to any of the following devices: Measure-UPS Measure-UPS II Environmental Monitoring Card Environmental Monitoring Device Integrated Environmental Monitor (AP9618 andAP9619 Network Management Cards only)MasterSwitch unitIn Chapter 5, How to Manage a MasterSwitchUnit, MasterSwitch unit refers to model numbersAP9210(i), AP9211, and AP9212. In the rest of thisguide, MasterSwitch unit is used collectively to referto any MasterSwitch unit, MasterSwitch VM unit, orMasterSwitch Plus unit.Network management station or NMSAny network component capable of using thePowerNet MIBPowerNet MIB Reference Guide2

Chapter 1: PowerNet MIBStructureThis chapter categorizes the PowerNet MIB into its major OID and trap components as follows: PowerNet MIB Traps PowerNet MIB OIDsPowerNet MIB TrapsAny Management Card, PowerNet Agent, or MasterSwitch unit can send traps to an NMS whenspecific events occur. The NMS does not need the PowerNet MIB to receive the trap, but it does needthe MIB to interpret the trap’s meaning. Also, the trap receiver definitions that a particular device orAgent uses determines which NMSs can receive traps.For more information on traps, see Chapter 9, PowerNet MIB Traps.PowerNet MIB OIDsThe PowerNet MIB OIDs allow an NMS to use its SNMP browser to manage any of the following: A Management Card, its UPS and an Environmental Monitor A PowerNet Agent, its UPS and Environmental Monitor A MasterSwitch unitHowever, the NMS can manage a device only if the SNMP access controls of that device allow theNMS to have SNMP access. (A PowerNet Agent, which has limited control over a UPS, does not useSNMP access controls.)The following sections further explain how to use OIDs: SNMP Access Controls SNMP Browser Structure PowerNet MIB OIDs Structure Tabled OIDsPowerNet MIB Reference Guide3

Chapter 1:PowerNet MIB OIDsSNMP Access ControlsA Management Card or MasterSwitch unit has a console programs that you can use to define specificSNMP access values for up to four SNMP channels.ActionResultDisable SNMP access completelyPrevent SNMP access by any NMS.Use an NMS IP Address as a SNMP channelvalueLimit channel access to only the defined NMS.Define a non-default password for an SNMPchannelLimit channel access to an NMS that knows thepassword.Select the type of access used by an SNMPchannelAllow an NMS to have write access, read access, orno access.For more information on SNMP access controls, see the User’s Guide for your Management Card.SNMP Browser StructureThe PowerNet MIB fits into a hierarchical structure within the SNMP browser’s categories. Forexample, when you use an HP OpenView for Windows SNMP browser, PowerNet MIB OIDs fit intothe browser’s structure, as follows: [iso] (for International Standards Organization) at the top [org] (for organization) under [iso] [dod] (for Department of Defense) under [org] [internet] under [dod] [private] under [internet] [enterprises] under [private] [apc] (for American Power Conversion) under [enterprises]PowerNet MIB OIDs StructureThe PowerNet MIB OIDs also are categorized into a hierarchical structure, with [apc] at the top andindividual OIDs under specific OID categories or within specific OID tables. (See Tabled OIDs.) Forexample, under [apc] there are two categories: [products], which provides the OIDs that you use tomanage specific products, and [apcmgmt], which provides OIDs that you use to affect the operationof hardware-based SNMP agents (Management Cards and MasterSwitch units). For more informationon how to use the [apcmgmt] OIDs, see Chapter 2, How to Manage Agents and ManagementCards.PowerNet MIB Reference Guide4

Chapter 1:PowerNet MIB OIDsUnder [products], there are three categories, two of which ([hardware] and [software]) provide OIDsthat you use to manage specific products.[hardware][software]This category contains sub-categories for each type ofhardware product that you can manage using PowerNetMIB OIDs. The following chapters describe how to usethe OIDs in those sub-categories:This category includes read-only OIDs thatyou can use to monitor a softwarePowerNet Agent only (as described inChapter 2, How to Manage Agents andManagement Cards) and contains the onesub-category [powerNetSubAgent] For [ups], see Chapter 3, How to Manage a UPS. For [measureUps], see Chapter 4, How to Managean Environmental Monitor. For [miniSNMP adapter], see Chapter 2, How toManage Agents and Management Cards. For [masterswitch], see Chapter 5, How to Managea MasterSwitch Unit. For [masterswitchVM], see Chapter 6, How toManage a MasterSwitch VM Unit. For [masterswitchMSP], see Chapter 7, How toManage a MasterSwitch Plus Unit.The third listing, [system], does not provide OIDs that you can use for SNMP management. The readonly OIDs that this category contains identify models of UPSs, Environmental Monitors, andMasterSwitch units by unique numbers that other OIDs can reference. For example, the MIB-II systemOIDs (listed under [internet], [mgmt], [mib-2], and [system]) use a PowerNet MIB [system] OIDnumber for the MIB-II’s [sysObjectID] value.Tabled OIDsFor any PowerNet MIB OID category listed in the SNMP browser, you can access a list of the currentvalues for all OIDs in that category and in all sub-categories below it in the hierarchy. For example,you can select [apc] to list the current values for all PowerNet MIB OIDs, or [ups] to list the currentvalues for all PowerNet MIB UPS OIDs. However, OIDs grouped together in a table will not appearin such a list. You can access an OID table’s values only by selecting that OID table in the SNMPbrowser. (An OID table appears enclosed in braces {}.) For example, to access the OIDs that define allfour trap receivers for a device, select {mconfigTrapReceiverTable} in the SNMP browser.For more information on how to define trap receivers, see Chapter 9, PowerNet MIB Traps.PowerNet MIB Reference Guide5

Chapter 2: How toManage Agents andManagement CardsThis chapter describes how to use PowerNet MIB OIDs to manage a Management Card, or to viewsoftware data for a PowerNet Agent. It also includes information on managing the SNMP agent of aMasterSwitch unit or Automatic Transfer Switch.In the following cases, the network connection allows an NMS to use an SNMP browser and PowerNetMIB OIDs to manage the UPS, Environmental Monitor, MasterSwitch unit, or Automatic TransferSwitch. A Web/SNMP Management Card or Network Management Card enables Web-based or SNMPbased monitoring of a UPS, Environmental Monitor, MasterSwitch unit, or Automatic TransferSwitch (which has an embedded Network Management Card). A PowerNet Management Card allows SNMP-based monitoring of a UPS and EnvironmentalMonitor. A PowerNet Agent indirectly connects a UPS and an Environmental Monitor to the network bycommunicating with a PowerChute plus application, which, in turn, communicates with theUPS and Environmental Monitor.In addition to using SNMP to manage a device connected to the network by a Management Card orPowerNet Agent, the NMS can also use PowerNet MIB OIDs to manage any Management Card,Environmental Monitor, MasterSwitch unit, or Automatic Transfer Switch, or to monitor softwarevalues for the PowerNet Agent.OIDsTasks[powerNetSubAgent] read-onlyOIDsView information about a PowerNet Agent. (See How toMonitor a PowerNet Agent.)[apcmgmt] OIDsManage the internal SNMP Agent at a hardware device. (SeeHow to Manage the SNMP Agent at a Hardware Device.)How to Monitor a PowerNet AgentYou can use [powerNetSubAgent] read-only OIDs to view information about a PowerNet Agent byperforming the following steps:1.Select [products] under [apc].2.Select [software].3.Select [powerNetSubAgent].The SNMP browser lists two OID categories: [powerNetSoftwareSystem] and[powerNetSoftwareConfig].PowerNet MIB Refer

PowerNet MIB Reference Guide ii REFERENCE GUIDE: POWERNET MANAGEMENT INFORMATION BASE (MIB), VERSION 3.4.4 AMERICAN POWER CONVERSION CORPORATION - SOFTWARE LICENSE AGREEMENT This software license agreement (the “agreement”) is a legal agreement between American Power Conversion Corporation as the File Size: 997KBPage Count: 95