2023年6月26日发(作者：)

PowerNet

Management

Information 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 Conversion

Corporation as the “licensor” (hereafter referred to as APC) and you (hereafter referred to as the “customer”) for

the APC software accompanying this agreement.

By downloading, installing, loading, copying, or otherwise using the software, you represent that one of the

following is true:••You have been authorized to accept these terms on behalf of the customer (the entity on whose behalf you

represent 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 use

the software only on behalf of such entity. If you intend to be personally bound, use of the software is limited to your

personal you are not authorized to accept these terms on behalf of a company or other entity, and you do not intend to be

personally 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 international

copyright laws and third-party software is provided with the APC software, that third-party software is not subject to the terms of this

license agreement. The license agreement of that third-party software defines the responsibilities of the customer

and licensor with regard to that software.1. GRANT

OF LICENSEAPC hereby agrees to grant and customer agrees to accept a non-exclusive and non-transferable license to use

the software, subject to the terms and conditions of this agreement. The software is owned and copyrighted by

American Power Conversion Corporation or its suppliers. As a customer, your license confers no ownership of or

title to the software and does not constitute a sale of any right in the software. APC retains all proprietary rights and

title to the software and any 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 the

software.2. RIGHT

TO USEThe software is licensed for use only by the number of users and/or on the number of servers or workstations

described 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 devices

connected with that single file server

On one or more computers powered by the same APC UPSTo support a web server, which may be connected to a varying but unlimited number of workstations or

computers on one or more networks.

To support any licensed copy of the PowerNet Agent.3. RIGHT

TO COPYThe 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 customer may make additional copies of the software and documentation only when essential for the

authorized and intended use of the software as described in this agreement and/or in the documentation

accompanying the and all copies, including any archival copy, must include the APC copyright notice and any other proprietary

notices that are included with the licensed software, and are fully subject to the terms of this customer may not redistribute the software or make copies with the intent to et MIB Reference Guideii4. 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 derivative works of the software or any portion ze or translate the software or its documentation, without the prior written consent of h or provide any results of benchmark tests run on the software to a third party without the prior written

consent of APC.5. DURATION

AND TERMINATION

OF THIS AGREEMENTThis license shall continue so long as the customer uses the software in compliance with the agreement. If the

customer breaches any of its obligations, this license shall terminate, and the customer agrees to destroy or return

all 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 software

and documentation.6. LIMITED WARRANTYThe APC limited warranty is for a period of ninety (90) days from the time the customer receives the warrants during the limited warranty period that the software will function materially as described in the

accompanying software user documentation and that any medium upon which the software is delivered will be free

from defects in material and workmanship when given normal, proper and intended 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 operating

systems specified in the the software is subjected to misuse, neglect, accident, or exposure to environmental conditions beyond

those specified in the a version of the software is used that does not include all updates available from the software has been does not warrant that use of the software will be uninterrupted or error free, nor that program errors will be

’s sole responsibility and customer’s sole remedy under this warranty is, at APC’s option, to repair or replace

all or any portions of the software, or to refund any license fee paid. This limited warranty is valid only if APC

receives written notice within the ninety-day warranty period.7. LIMITATION

OF WARRANTIES

AND LIABILITYEXCEPT AS EXPRESSLY SET FORTH IN SECTION 6 HEREIN ENTITLED “LIMITED WARRANTY”, (i) APC

SHALL HAVE NO LIABILITY TO THE CUSTOMER OR ANY THIRD PARTY FOR THE SOFTWARE, INCLUDING

ANY 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 OTHER

COMMUNICATION; 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 POSSIBILITY

OF SUCH POTENTIAL LOSS OR STATES OR JURISDICTIONS DO NOT ALLOW THE EXCLUSION OF IMPLIED WARRANTIES OR

LIMITATION OF INCIDENTAL OR CONSEQUENTIAL DAMAGES, SO THE ABOVE LIMITATION OR

EXCLUSION MIGHT NOT APPLY TO YOU. HOWEVER, TO THE FULL EXTENT PERMITTED BY APPLICABLE

LAW, THE DURATION OF STATUTORILY REQUIRED WARRANTIES, IF ANY, SHALL BE LIMITED TO THE

WARRANTY PERIOD OF 90 DEALER, AGENT, EMPLOYEE, OR CUSTOMER OF APC IS AUTHORIZED TO MAKE ANY

MODIFICATIONS, EXTENSIONS, OR ADDITIONS TO THIS LIMITED WARRANTY. The cumulative liability of

APC to the customer for all claims relating to the software shall not exceed the total amount of any and all license

fees paid to APC by the customer for the software or, if no license fee was required, the replacement of the

et MIB Reference Guideiii8. NO WARRANTY UNDER HAZARDOUS, HIGH-RISK,

OR LIFE-THREATENING CONDITIONS

The software is not fault-tolerant and is not designed, manufactured or intended for use or resale as control

equipment 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 environmental

damage. Accordingly, APC and its suppliers specifically disclaim any express or implied warranty of fitness for such

hazardous, high-risk, or life-threatening activities.9. USE

OF TECHNICAL INFORMATION RELATED

TO CUSTOMER 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 product

support 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 assigned

or in any way transferred without the prior written consent of APC.11. LANGUAGE

AND JURISDICTION

OF

THE AGREEMENTThe original of this agreement has been written in English. The parties hereto waive any statute, law, or regulation

that 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 the

customer and is not the legally binding version of the terms of this agreement shall be construed in accordance with the substantive laws of the Commonwealth of

Massachusetts, United States of America, without giving effect to the principles of conflict or choice of law of such

commonwealth. APC and Customer exclude the United Nations Convention on Contracts for the International Sale

of Goods from this agreement.12. U.S. GOVERNMENT RESTRICTED RIGHTS LEGENDThe software and documentation are “commercial items” as that term is defined in 48C.F.R. 2.101 (October 1995)

consisting of “commercial computer software” and “commercial computer software documentation” as such terms

are used in 48C.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 a

commercial item, and with only those rights as are granted to all other end users pursuant to the terms and

conditions of this agreement. Licensor is American Power Conversion Corporation, P.0. Box 278, 132 Fairgrounds

Rd., West Kingston, RI 02892, U.S.A.13. EXPORT CONTROLS None of the software or underlying information or technology may be downloaded or otherwise exported or re-exported to any of the following:•••Into (or to a national or resident of) any country to which the U.S. has embargoed anyone on the U.S. Treasury Department’s list of Specially Designated anyone on the U.S. Commerce Department’s Table of Denial downloading or using the software, the customer agrees to the foregoing and represents and warrants that it is

not located in, under the control of, or a national or resident of any such country or on any such 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 procedures

required by applicable law to make this license enforceable.---------------------------------------------------------------------------------------------------------------------------------------------------------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 GuideivContentsAbout This Guide 1Guide Purpose. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1Guide Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1Related Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2Terms Used in This Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2Chapter 1:PowerNet MIB Structure 3PowerNet 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 Cards 6How 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 UPS

11How 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 GuidevHow to Control a UPS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17[upsControl] OIDs 17[upsBasicControl] 17[upsAdvControl] 18How to Configure a UPS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20[upsConfig] 20[upsBasicConfig] 20[upsAdvConfig] 21How to Test a UPS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23[upsTest] 23[upsAdvTest] 23How to Use OIDs for 3-Phase UPS Models. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25[upsPhaseResetValues] 25[upsPhaseInput] 26[upsPhaseOutput] 27Chapter 4:How to Manage an Environmental Monitor 28External 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 Card

Only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 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 Unit

37[sPDUIdent] Identification OIDS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38[sPDUMasterControl] Master Control OIDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39[sPDUMasterConfig] Master Configuration OIDs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40[sPDUOutletControl] Outlet Control OIDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41[sPDUOutletConfig] Outlet Configuration OIDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42PowerNet MIB Reference GuideviChapter 6:How to Manage a MasterSwitch VM Unit 43[sPDUIdentVM] Identification OIDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44[sPDUMasterControlVM] Master Control OIDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45[sPDUMasterConfigVM] Master Configuration OIDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45[sPDUMasterStatusVM] Master Status OIDs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47[sPDUOutletControlVM] Outlet Control OIDs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48[sPDUOutletConfigVM] Outlet Configuration OIDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49[sPDUOutletStatusVM] Outlet Status OIDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50Chapter 7:How to Manage a MasterSwitch Plus Unit 51[sPDUIdentMSP] Identification OIDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52[sPDUMasterControlMSP] Master Control OIDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53[sPDUMasterConfigMSP] Master Configuration OIDs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54[sPDUMasterStatusMSP] Master Status OIDs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54[sPDUOutletControlMSP] Outlet Control OIDs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55[sPDUOutletConfigMSPall] Outlet Configuration OIDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56[sPDUOutConfigMSPgs] Outlet Configuration OIDS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56Example of a “Load-Shedding” Configuration 58[sPDUOutConfigMSPannun] Outlet Configuration OIDS. . . . . . . . . . . . . . . . . . . . . . . . . . . . 60[sPDUOutConfigMSPmups] Outlet Configuration OIDs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61[sPDUOutletStatusMSP] Outlet Status OIDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63Chapter 8:How to Manage an Automatic Transfer Switch 64[atsIdent] Identification OIDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65[atsCalibration] Calibration OIDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66[atsControl] Control OIDs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67[atsConfig] Configuration OIDs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67[atsStatus] Status OIDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68[atsStatusInput] Input OIDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70[atsStatusOutput] Output OIDs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72Chapter 9:PowerNet MIB Traps 74Trap Severity Levels. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75How To Define Trap Receivers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75PowerNet MIB Trap Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76Symmetra UPS Subtraps. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85PowerNet MIB Reference GuideviiAbout This GuideThis introduction provides the following information to help you use this guide.••••Guide PurposeGuide StructureRelated DocumentsTerms Used in This GuideFor assistance with this or any other APC product, contact APC Worldwide Customer Support as

described at the end of this PurposeThis guide describes how to use the PowerNet management information base (MIB), version 3.4.4, to

manage APC products that allow or enable using simple network management protocol (SNMP) for

management:••••MIB version 3.4.4 management of a Management Card, UPS, and an Environmental MonitorMIB version 2.2-compatible management of a version 2.2 Agent, its UPS, and an

Environmental MonitorMIB version 3.4.4 management of an APC MasterSwitch™ AC Power Controller, a

MasterSwitch VM AC remote control PDU, or a MasterSwitch Plus AC remote control PDUMIB version 3.4.4 management of an APC Automatic Transfer Switch and its embedded

Network Management StructureThis guide’s chapters describe how to use the PowerNet MIB:•Chapter1, 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:------Chapter2, How to Manage Agents and Management CardsChapter3, How to Manage a UPSChapter4, How to Manage an Environmental MonitorChapter5, How to Manage a MasterSwitch UnitChapter6, How to Manage a MasterSwitch VM UnitChapter7, How to Manage a MasterSwitch Plus UnitPowerNet MIB Reference Guide1 About This GuideRelated Documents- Chapter 8, How to Manage an Automatic Transfer Switch• Chapter 9, PowerNet MIB TrapsDescribes the PowerNet MIB traps and how to define which NMSs can receive those d DocumentsThis guide describes how to use the PowerNet MIB only. For information about an APC product that

you manage using the PowerNet MIB, see the user’s guide or owner’s manual for that product. See

your 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 to

any of the following devices:•Any PowerNet Adapter with model number

AP9205, AP9605, or AP9603

•Any Web/SNMP Management Card•Any Network Management CardPowerNet Agent, or AgentEnvironmental MonitorAny PowerNet AgentUnless otherwise stated, Environmental Monitor

refers to any of the following devices:•Measure-UPS•Measure-UPS II•Environmental Monitoring Card•Environmental Monitoring Device•Integrated Environmental Monitor (AP9618 and

AP9619 Network Management Cards only)MasterSwitch unitIn Chapter5, How to Manage a MasterSwitch

Unit, MasterSwitch unit refers to model numbers

AP9210(i), AP9211, and AP9212. In the rest of this

guide, MasterSwitch unit is used collectively to refer

to any MasterSwitch unit, MasterSwitch VM unit, or

MasterSwitch Plus network component capable of using the

PowerNet MIBNetwork management station or NMSPowerNet MIB Reference Guide2Chapter 1:PowerNet MIB

StructureThis chapter categorizes the PowerNet MIB into its major OID and trap components as follows:••PowerNet MIB TrapsPowerNet MIB OIDsPowerNet MIB TrapsAny Management Card, PowerNet Agent, or MasterSwitch unit can send traps to an NMS when

specific events occur. The NMS does not need the PowerNet MIB to receive the trap, but it does need

the MIB to interpret the trap’s meaning. Also, the trap receiver definitions that a particular device or

Agent uses determines which NMSs can receive more information on traps, see Chapter 9, PowerNet MIB et 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 MonitorA PowerNet Agent, its UPS and Environmental MonitorA MasterSwitch unitHowever, the NMS can manage a device only if the SNMP access controls of that device allow the

NMS to have SNMP access. (A PowerNet Agent, which has limited control over a UPS, does not use

SNMP access controls.)The following sections further explain how to use OIDs:••••SNMP Access ControlsSNMP Browser StructurePowerNet MIB OIDs StructureTabled OIDsPowerNet MIB Reference Guide3Chapter 1:PowerNet MIB OIDsSNMP Access ControlsA Management Card or MasterSwitch unit has a console programs that you can use to define specific

SNMP access values for up to four SNMP ResultDisable SNMP access completelyUse an NMS IP Address as a SNMP channel

valueDefine a non-default password for an SNMP

channelSelect the type of access used by an SNMP

channelPrevent SNMP access by any channel access to only the defined channel access to an NMS that knows the

an NMS to have write access, read access, or

no more information on SNMP access controls, see the User’s Guide for your Management Browser StructureThe PowerNet MIB fits into a hierarchical structure within the SNMP browser’s categories. For

example, when you use an HP OpenView for Windows SNMP browser, PowerNet MIB OIDs fit into

the 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 and

individual OIDs under specific OID categories or within specific OID tables. (See Tabled OIDs.) For

example, under [apc] there are two categories: [products], which provides the OIDs that you use to

manage specific products, and [apcmgmt], which provides OIDs that you use to affect the operation

of hardware-based SNMP agents (Management Cards and MasterSwitch units). For more information

on how to use the [apcmgmt] OIDs, see Chapter 2, How to Manage Agents and Management

et MIB Reference Guide4Chapter 1:PowerNet MIB OIDsUnder [products], there are three categories, two of which ([hardware] and [software]) provide OIDs

that you use to manage specific products.[hardware][software]This category contains sub-categories for each type of

hardware product that you can manage using PowerNet

MIB OIDs. The following chapters describe how to use

the OIDs in those sub-categories:• For [ups], see Chapter 3, How to Manage a UPS.• For [measureUps], see Chapter 4, How to Manage

an Environmental Monitor.• For [miniSNMP adapter], see Chapter 2, How to

Manage Agents and Management Cards.• For [masterswitch], see Chapter 5, How to Manage

a MasterSwitch Unit.• For [masterswitchVM], see Chapter 6, How to

Manage a MasterSwitch VM Unit.• For [masterswitchMSP], see Chapter 7, How to

Manage a MasterSwitch Plus Unit.

This category includes read-only OIDs that

you can use to monitor a software

PowerNet Agent only (as described in

Chapter 2, How to Manage Agents and

Management Cards) and contains the one

sub-category [powerNetSubAgent]The third listing, [system], does not provide OIDs that you can use for SNMP management. The read-only OIDs that this category contains identify models of UPSs, Environmental Monitors, and

MasterSwitch units by unique numbers that other OIDs can reference. For example, the MIB-II system

OIDs (listed under [internet], [mgmt], [mib-2], and [system]) use a PowerNet MIB [system] OID

number for the MIB-II’s [sysObjectID] OIDsFor any PowerNet MIB OID category listed in the SNMP browser, you can access a list of the current

values 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 current

values for all PowerNet MIB UPS OIDs. However, OIDs grouped together in a table will not appear

in such a list. You can access an OID table’s values only by selecting that OID table in the SNMP

browser. (An OID table appears enclosed in braces {}.) For example, to access the OIDs that define all

four trap receivers for a device, select {mconfigTrapReceiverTable} in the SNMP more information on how to define trap receivers, see Chapter 9, PowerNet MIB et MIB Reference Guide5Chapter 2:How to

Manage Agents and

Management CardsThis chapter describes how to use PowerNet MIB OIDs to manage a Management Card, or to view

software data for a PowerNet Agent. It also includes information on managing the SNMP agent of a

MasterSwitch unit or Automatic Transfer the following cases, the network connection allows an NMS to use an SNMP browser and PowerNet

MIB OIDs to manage the UPS, Environmental Monitor, MasterSwitch unit, or Automatic Transfer

Switch.•A Web/SNMP Management Card or Network Management Card enables Web-based or SNMP-based monitoring of a UPS, Environmental Monitor, MasterSwitch unit, or Automatic Transfer

Switch (which has an embedded Network Management Card).A PowerNet Management Card allows SNMP-based monitoring of a UPS and Environmental

Monitor.A PowerNet Agent indirectly connects a UPS and an Environmental Monitor to the network by

communicating with a PowerChute plus application, which, in turn, communicates with the

UPS and Environmental Monitor.••In addition to using SNMP to manage a device connected to the network by a Management Card or

PowerNet 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 software

values for the PowerNet sks[powerNetSubAgent] read-only

OIDs[apcmgmt] OIDsView information about a PowerNet Agent. (See How to

Monitor a PowerNet Agent.)Manage the internal SNMP Agent at a hardware device. (See

How 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 by

performing the following steps: [products] under [apc].Select [software].Select [powerNetSubAgent].The SNMP browser lists two OID categories: [powerNetSoftwareSystem] and

[powerNetSoftwareConfig].PowerNet MIB Reference Guide6Chapter 2:How to Manage the SNMP Agent at a Hardware Device[powerNetSoftwareSystem]The following table describes the [powerNetSoftwareSystem] ormation ProvidedpowerNetSoftwareSystemDescriptionpowerNetSoftwareOidpowerNetSoftwareSystemUpTimeInformation about an Agent, including its version technology that the Agent uses to implement the

PowerNet length of time that the Agent has been continuously

running on the network.[powerNetSoftwareConfig]The following table describes the [powerNetSoftwareConfig] ormation ReportedpowerNetSoftwareTableSize{powerNetSoftwareTable}

{powerNetSoftwareEntry}

moduleNumbermoduleNamemoduleVersionmoduleDateThe number of distinct software modules that an Agent has.A tabled set of OIDs that define each module by these module

characteristics:•Table row number•Name•Version number•Installation date, in the format mm-dd-yyHow to Manage the SNMP Agent at a Hardware DeviceWhen you select [apcmgmt] under [apc], the SNMP browser lists four OID categories: [mcontrol],

[mconfig], [mtrapargs], and [mfiletransfer]. In these categories, you can use the OIDs documented

in this guide to manage the SNMP Agent at a hardware device (ManagementCard, Environmental

Monitor, MasterSwitch unit, or Automatic Transfer Switch).PowerNet MIB Reference Guide7Chapter 2:How to Manage the SNMP Agent at a Hardware Device[mcontrol]The following table describes the one OID in the [mcontrol] category. Value (3), not documented, is

ues You Can SETmcontrolRestartAgentrestartCurrentAgent (1): Reboots the SNMP ueCurrentAgent (2): Continues the Agent without tWithoutAgent (4): Restarts the system without starting the Agent.

The next time the system restarts, the Agent also restarts.[mconfig]The following table describes the [mconfig] Task

mconfigBOOTPEnabled Identify the current BOOTP setting. A GET to this OID returns

one of the following:•yes (1): Enable BOOTP. The hardware device will obtain its IP

configuration parameters from a BOOTP server.•no (2): Disable BOOTP. The hardware device will use the IP

configuration parameters stored in its EPROM.

mconfigNumTrapReceivers

{mconfigTrapReceiverTable}

Identify how many NMSs can receive traps from the Agent. A

GET to this OID returns a value from 0 to this tabled set of OIDs to define up to four NMSs as trap

{mconfigTrapReceiverEntry}

receivers. See How To Define Trap Receivers in Chapter 9,

PowerNet MIB Traps for information on the OIDs in this dex

receiverAddr

communityString

severity

acceptThisReceiver

receiveTrapType

mconfigClockConfigure the date and time on a Web/SNMP Management Card,

Network Management Card, or MasterSwitch unit.•mconfigClockDate in mm/dd/yyyy format•mconfigClockTime in hh:mm:ss am/pm formatSee How To Define Trap Receivers in Chapter 9, PowerNet MIB Traps for information on how to

define trap et MIB Reference Guide8Chapter 2:How to Manage the SNMP Agent at a Hardware Device[mtrapargs]The following table describes the [mtrapargs] OIDs, which enable APC traps to use a specific type of

argument, which, in each case, may not be defined as part of the APC ument That APC Traps Are Alowed to UsemtrapsapargsIntegermtrapsapargsIpAddressmtrapsapargsStringmtrapsapargsGaugemtrapsapargsTimeTicksAn integer IP address octet string argument.A Gauge argument.A TimeTicks argument.[mfiletransfer]The [mfiletransfer] OIDs, which are supported only by a PowerNet Management Card, allow transfers

of any type of file that the card can recognize. For more information, see the User’s Guide for your

PowerNet Management OID categories under the [mfiletransfer] category are [mfiletransferStatus],

[mfiletransferConfig], and [mfiletransferControl].

[mfiletransferStatus]The following table describes the one OID in the [mfiletransferStatus] letransferStatusLastFileTransferResultInformation ProvidedOne of the following results of the last attempted file

transfer:lastFileTransferResultSuccessful (1)

lastFileTransferResultNotAvailable (2): If this value is

returned, there have been no previous file leTransferResultFailureUnknown (3)

lastFileTransferResultFailureServerInaccessible (4)

lastFileTransferResultFailureServerAccessDenied (5)

lastFileTransferResultFailureFileNotFound (6)

lastFileTransferResultFailureFileTypeUnknown (7)

lastFileTransferResultFailureFileCorrupted (8)

PowerNet MIB Reference Guide9Chapter 2:How to Manage the SNMP Agent at a Hardware Device[mfiletransferConfig]The following table describes the three sub-categories in the [mfiletransferConfig] category and the

OIDs in each of those Sub-categoryOIDs in Each Sub-category[mfiletransferConfigSettings] mfiletransferConfigSettingsFileName: The name and path of the

file to be transferred.

[mfiletransferConfigTFTP] mfiletransferConfigTFTPServerAddress: The IP Address of the

remote TFTP Server.[mfiletransferConfigFTP]mfiletransferConfigFTPServerAddress: The IP Address, in

decimal notation, of the remote FTP Server involved in the file

ransferConfigFTPServerUser: The FTP Server User

ransferConfigFTPServerPassword: The FTP Server

Password.[mfiletransferControl]The following table describes the one OID in the [mfiletransferControl] kmfiletransferControlInitiateFileTransferdoNotInitiateFileTransfer (1): Do teFileTransferDownloadViaTFTP (2):

Download file from the TFTP teFileTransferDownloadViaFTP (3):

Download file from the FTP et MIB Reference Guide10Chapter 3:How to Manage a UPSThis chapter describes how to use PowerNet MIB OIDs to manage a UPS through its Management

Card or its PowerNet erNet MIB OIDs that you can use to manage (monitor, configure, control and test) a UPS are

in nine categories under the heading [ups]. To list the nine categories, perform the following steps: [products] under [apc].Select [hardware].Select [ups].TasksOID Categories[upsIdent][upsBattery][upsInput][upsOutput][upsComm][upsConfig][upsControl][upsTest][upsPhase]View information about the UPS and its overall operation. (See How to

Monitor a UPS.)Modify parameters that affect the overall operation of the UPS. (See

How to Configure a UPS.)Directly affect the current operation of the UPS. (See How to Control a

UPS.)Verify that the UPS can operate correctly during a power failure. (See

How to Test a UPS.)Provide OIDs directly related to 3-phase UPS models. (See How to Use

OIDs for 3-Phase UPS Models.)The following factors determine which OIDs in the [ups] categories can be used to manage a UPS:

••The manner in which the UPS connects to the a PowerNet Agent, the type of signalling used for the connection between the Agent and the

UPS: basic (simple-signalling) and advanced (smart-signalling). Management CardPowerNet AgentYou can use all OIDs listed under the

[ups] category of the PowerNet cannot use the following:•Any [ups] OIDs not originally supported for PowerNet

Agents in PowerNet MIB version 2.2.•Smart-signalling (advanced) OIDs, if the Agent- to-UPS

communication uses et MIB Reference Guide11Chapter 3:How to Monitor a UPSHow to Monitor a UPSYou use GETs (SNMP read commands) to PowerNet MIB OIDs to monitor (view information about)

the PowerNet MIB categories have OIDs that you can use to view information about the operation

of the UPS. With few exceptions, these OIDs respond to GETs, but not to SETs: You can view (GET)

information about UPS operation, but you cannot affect (SET) that CategoriesInformation Reported[upsIdent][upsBattery][upsComm][upsInput][upsOutput]The UPS identification parameters. See [upsIdent] UPS Identification UPS battery status. See [upsBattery] UPS Battery UPS-to-SNMP agent communication link. See [upsComm] UPS

Communication voltage input to the UPS. See [upsInput] UPS Input voltage output by the UPS. See [upsOutput] UPS Output every PowerNet MIB OID responds to a GET with useful information. For example:•••A GET to any [upsControl] OID receives a response indicating that the UPS did not perform

the related control action.A GET to [upsAdvControlFlashAndBeep] receives a noFlashAndBeep (1) response.A GET to [upsAdvControlRebootUps] receives a noRebootUps (1) response.[upsIdent] UPS Identification OIDsThe [upsIdent] category has five OIDs in two sub-categories, [upsBasicIdent] and [upsAdvIdent]

that report UPS identification parameter values. Four read-only OIDs report values pre-set at the

factory, and one OID reports the name used for the UPS, a name that you can define using a SET.

You can access all five OIDs through any Management Card or PowerNet Agent that connects to the

UPS through a smart-signalling cable. For a PowerNet Agent that connects to the UPS through a

simple-signalling cable, you can use only the two [upsBasicIdent] OIDs.[upsBasicIdent]OID Information ReportedupsBasicIdentModel

upsBasicIdentName

The UPS model 8-character name for the UPS. You can use a SET to change this et MIB Reference Guide12Chapter 3:How to Monitor a UPS[upsAdvIdent]OIDInformation ReportedupsAdvIdentFirmwareRevision

upsAdvIdentDateOfManufacture

upsAdvIdentSerialNumber

The UPS firmware version.

The date on which the UPS completed the

manufacturing UPS serial number.[upsBattery] UPS Battery OIDsThe [upsBattery] category has nine OIDs in two sub-categories, [upsBasicBattery] and

[upsAdvBattery] that provide UPS battery status information. Eight are read-only OIDs, and one OID

reports when the battery was replaced last, a value that you can define by using a can access all nine OIDs through any Management Card or through a PowerNet Agent that

connects to the UPS through a smart-signalling cable. For a PowerNet Agent that connects to the UPS

through a simple-signalling cable, you can use only the three [upsBasicBattery] OIDs.[upsBasicBattery]OIDInformation Reported

upsBasicBatteryStatusThe current UPS battery status:•unknown (1): The Management Card or PowerNet Agent

cannot report the status.•batteryNormal (2): Within normal operating parameters.•batteryLow (3): Insufficient battery capacity to support the

UPS equipment icTimeOnBatteryThe amount of time since the UPS switched to battery icBatteryLastReplaceDateThe date on which the battery was last replaced, a value you can

change by using a SET. The format is mm/dd/yy or mm/dd/et MIB Reference Guide13Chapter 3:How to Monitor a UPS[upsAdvBattery]OIDInformation ReportedupsAdvBatteryCapacityupsAdvBatteryTemperatureupsAdvBatteryRunTimeRemainingupsAdvBatteryReplaceIndicatorThe battery’s remaining capacity as a percentage of full

battery internal temperature of the UPS, in long the UPS battery can provide output r a UPS battery needs replacement:•noBatteryNeedsReplacing (1)

•batteryNeedsReplacing (2)

upsAdvBatteryNumOfBattPacksupsAdvBatteryNumOfBadBattPacksThe number of external battery packs a Matrix-UPS or

Smart-UPS XL number of defective external battery packs that a

Matrix-UPS or Smart-UPS XL has.[upsComm] UPS Communication OIDThis category has a single read-only OID that you can access through any Management Card but not

through a PowerNet ormation ReportedupsCommStatusThe status of the Management Card’s SNMP agent-to-UPS

communication link:•ok (1)

•noComm (2)

[upsInput] UPS Input OIDsThe [upsInput] category has six read-only OIDs in two sub-categories, [upsBasicInput] and

[upsAdvInput], that provide information about the UPS input (utility line) can access all six OIDs through any Management Card or through a PowerNet Agent that connects

to the UPS through a smart-signalling cable. For a PowerNet Agent that connects to the UPS through

a simple-signalling cable, you can use only the upsBasicInputPhase OID.[upsBasicInput]OIDInformation Reported

upsBasicInputPhaseThe current AC input voltage et MIB Reference Guide14Chapter 3:How to Monitor a UPS[upsAdvInput]OIDInformation Reported

upsAdvInputLineVoltageupsAdvInputMaxLineVoltageupsAdvInputMinLineVoltageupsAdvInputFrequencyupsAdvLineFailCauseThe current input voltage in maximum input voltage, in VAC, sensed by the UPS during

the last minimum input voltage, in VAC, sensed by the UPS during

the last current input voltage frequency in reason for the most recent transfer to battery.•Any Management Card or smart-signalling PowerNet Agent can

report the following:-noTransfer (1): No transfer has occurred.-highLineVoltage (2): Voltage exceeded the high-transfer

voltage value.-brownout (3): For more than 5 seconds, the voltage level was

between 40% of the UPS rated output voltage and the low-transfer voltage value.-blackout (4): For more than 5 seconds, the voltage level was

between 40% of the UPS rated output voltage and ground [0

volts].-smallMomentarySag (5): A brownout existed for 5 seconds

or less.-deepMomentarySag (6): A blackout existed for 5 seconds or

less.-smallMomentarySpike (7): Less than 10 volts per cycle

voltage increase.-largeMomentarySpike (8): More than 10 volts per cycle

voltage increase.•A Management Card can also report the occurrence of a UPS

self-test, self-test (9), and the rate of changes in the line voltage

level, rateOfVoltageChange (10).See How to Configure a UPS for information about the following values mentioned in the

descriptions of [upsAdvLineFailCause] OID values in the preceding table:•••Rated output of the UPSThe high-transfer voltage valueThe low-transfer voltage valuePowerNet MIB Reference Guide15Chapter 3:How to Monitor a UPS[upsOutput] UPS Output OIDSThe [upsOutput] category has six read-only OIDs in two subcategories, [upsBasicOutput] and

[upsAdvOutput], that provide information about the UPS output can access all six OIDs through any Management Card. A PowerNet Agent that connects to the

UPS through a smart-signalling cable can use all the OIDs except upsAdvOutputCurrent. A

PowerNet Agent that connects to the UPS through a simple-signalling cable can use only the two

[upsBasicOutput] OIDs.[upsBasicOutput]OIDInformation Reported

upsBasicOutputStatus The current UPS operational status:•unknown (1): The Management Card or PowerNet Agent cannot

determine the state of the UPS.•onLine (2): The UPS is using acceptable input voltage to provide

output voltage.•onBattery (3): The UPS is using battery power to provide output

voltage.•onSmartBoost (4): The UPS is using

its AVR Boost feature with a low

input voltage to provide sufficient output voltage without switching to

battery operation.•timedSleeping (5): The UPS is waiting a defined period of time

before supplying output power to its supported equipment.•softwareBypass (6): The Matrix-UPS or Symmetra UPS was placed

into bypass mode using SNMP, PowerChute plus or PowerNet

Manager.•off (7): The UPS is turned off.•rebooting (8): The UPS is resetting its supported equipment by

turning off its output power and then turning it back on.

•switchedBypass (9): The Matrix-UPS or Symmetra UPS was placed

into bypass mode using the switch at the UPS.•hardwareFailureBypass (10): The Matrix-UPS or Symmetra UPS

placed itself into bypass mode in response to a hardware problem.•sleepingUntilPowerReturn (11): The UPS is waiting for input power

to return to an acceptable level before it provides output power to its

supported equipment.•onSmartTrim (12): The UPS is using

its AVR Trim feature with a high

input voltage to provide output voltage without switching to battery

icOutputPhase The current output et MIB Reference Guide16Chapter 3:How to Control a UPS[upsAdvOutput]OIDInformation Reported

upsAdvOutputVoltageupsAdvOutputFrequencyupsAdvOutputLoadupsAdvOutputCurrentThe output voltage of the UPS in VAC.

The output voltage frequency of the UPS in equipment load placed on the UPS by its supported equipment as a

percentage of rated load output voltage current in AmperesHow to Control a UPSYou can use SETs (SNMP write commands) to the [upsControl] OIDs to directly affect the current

operation of the UPS[upsControl] OIDsWhich [upsControl] OIDs you can use depends on how the UPS connects to the network. The

[upsControl] category has two subcategories••[upsBasicControl] for simple-signalling connections.[upsAdvControl] for smart-signalling connections.[upsBasicControl]The [upsBasicControl] category has one OID, which any Management Card or PowerNet Agent can

use to put a UPS that is running on battery into “sleep mode.”OIDTaskupsBasicControlConserveBatteryCause a UPS running on battery to turn off its outlets to

conserve battery runtime and then wait in “sleep mode” until

acceptable input power returns.•noTurnOffUps (1): The value always returned for a GET.

Setting this value has no effect.•turnOffUpsToConserveBattery (2): The UPS, if running

on battery, waits in “sleep mode” until acceptable input

power returns. If the UPS is not on battery, a badValue error

is et MIB Reference Guide17Chapter 3:How to Control a UPS[upsAdvControl]Management Cards and PowerNet Agents that use smart-signalling to connect with the UPS can use

SETs to the OIDs in the [upsAdvControl] category, with the following exceptions:•Three OIDs each have a value that you can use only with a Management Card.

---OIDThe upsAdvControlUpsOff OID’s value of turnUpsOffGracefully (3).The upsAdvControlRebootUps OID’s value of rebootUpsGracefully (3).The upsAdvControlUpsSleep OID’s value of putUpsToSleepGracefully (3).Task (page 1 of 2)upsAdvControlUpsOffCause the UPS to turn off. How the UPS turns off depends on

what SET value is used and how the UPS connects to the

network:•noTurnUpsOff (1): The value always returned for a GET.

Setting this value has no effect.•turnUpsOff (2): All Management Cards turn off the UPS

immediately.•turnUpsOffGracefully (3):

-A PowerNet Agent performs an orderly shutdown of the

UPS server, then turns off the UPS.-A Management Card turns off a UPS after the delay

defined by upsAdvConfigShutoffDelay, a UPS

configuration OID. (See How to Configure a UPS.)Note:

When you use the upsAdvControlUpsOff OID with a

PowerNet Agent, you can turn on the UPS again only by

using the UPS on/off switch. For all Management Cards,

you can turn on the UPS again by using a SET value of

turnOnUPS (2) for the upsAdvControlTurnOnUPS ControlRebootUpsCause the UPS to reset its supported equipment by turning

power off and then back on:•noRebootUps (1): The value always returned for a GET.

Setting this value has no effect.•rebootUps (2): All Management Cards reboot the UPS

immediately.•rebootUpsGracefully (3): A Management Card reboots a

UPS, using a delay before it turns off the UPS. The UPS uses

the delay value defined by upsAdvConfigShutoffDelay, a

UPS configuration OID. (See How to Configure a UPS.)PowerNet MIB Reference Guide18Chapter 3:How to Control a UPSOIDTask (page 2 of 2)upsAdvControlUpsSleepCause the UPS to turn off its outlets and wait in “sleep mode”

for the period of time defined by

upsAdvConfigUpsSleepTime, a UPS configuration OID (See

How to Configure a UPS.)

•noPutUpsToSleep (1): The value always returned for a

GET. Setting this value has no effect.•putUpsToSleep (2): All Management Cards turn off UPS

power immediately.

•putUpsToSleepGracefully (3): A Management Card turns

off UPS power after a delay defined by

upsAdvConfigShutoffDelay, a UPS configuration OID.

(See How to Configure a UPS.)upsAdvControlSimulatePowerFailCause the UPS to test its ability to switch to battery operation

as it would in a power failure:•noSimulatePowerFailure (1): The value always returned

for a GET. Setting this value has no effect.•simulatePowerFailure (2): The UPS performs this ControlFlashAndBeepCause the UPS to test its front panel lights (if any) and its

audible alarm:•noFlashAnd Beep (1): The value always returned for a

GET. Setting this value has no effect.•flashAndBeep (2): The UPS performs this ControlTurnOnUPSCause a Management Card’s UPS to turn on:•noTurnOnUPS (1): The value always returned for a GET.

Setting this value has no effect.•turnOnUPS (2): The UPS turns on, if that UPS was turned

off using the upsAdvControlUpsOff ControlBypassSwitchSwitch a Matrix-UPS or Symmetra UPS to or from software

bypass mode:•noBypassSwitch (1): The value always returned for a GET.

Setting this value has no effect.•switchToBypass (2): The UPS switches to bypass mode.•switchOutOfBypass (3): The UPS switches from bypass

mode to normal et MIB Reference Guide19Chapter 3:How to Configure a UPSHow to Configure a UPSYou can use the OIDS in the [upsConfig] category to define how the UPS responds to specific

operating conditions.[upsConfig]Which [upsConfig] OIDs you can use depends on how the Management Card or PowerNet Agent

connects to the UPS. The [upsConfig] category has two subcategories:•[upsBasicConfig] for simple-signalling connections, which provide basic power management

and protection but offer few additional configuration and monitoring options. (A Back-UPS

supports only simple-signalling.)[upsAdvConfig] for smart-signalling connections, which provide full support for the advanced

configuration and monitoring options available on all APC UPSs except Back-UPS.•[upsBasicConfig]The [upsBasicConfig] category has one read-only OID and a tabled set of OIDs that you can use to

view or define information about the equipment supported by the k

upsBasicConfigNumDevices Identify the number of devices specified in the tabled set of

OIDS {upsBasicConfigDeviceTable}, i.e. the number of

devices plugged into the or define information about the equipment supported

by each UPS outlet:•View read-only value that identifies the specific outlet.•Define a 16-character name for the device at this outlet.•Define the VA rating of the device this outlet supportsAdd a device entry to the table or delete and existing device

entry:•yes (1): Add an entry.•no (2): Delete an entry.{upsBasicConfigDeviceTable}

{upsBasicConfigDeviceEntry}

deviceIndex

deviceName

vaRating

acceptThisDevice

PowerNet MIB Reference Guide20Chapter 3:How to Configure a UPS[upsAdvConfig]The OIDs in the [upsAdvConfig] category enable you to view or configure operating and shutdown

parameters for a UPS connected in smart-signalling mode. A Management Card can use all the OIDS

in this category. A PowerNet Agent can use all but four of the OIDs, as noted in the following k (page 1 of 3)upsAdvConfigRatedOutputVoltage1upsAdvConfigHighTransferVolt1Define the UPS nominal VAC output voltage. This value is

read-only for most 120 VAC the input voltage at which the UPS will switch to

its

AVR Boost feature. If the UPS does not support AVR Boost,

it switches to battery operation instead. (A Matrix-UPS, for

example, does not support AVR Boost.)Define the input voltage at which the UPS will switch to

its

AVR Trim feature. If the UPS does not support AVR Trim, it

switches to battery operation instead. (A Matrix-UPS, for

example, does not support AVR Trim.)Define when the UPS will generate an audible alarm for a

line-fail condition:•timed (1): After the UPS switches to battery operation and

waits the delay defined by the

upsAdvConfigAlarmTimer OID.•atLowBattery (2): When a low-battery condition occurs.•never (3): No alarm occursupsAdvConfigLowTransferVolt2upsAdvConfigAlarmupsAdvConfigAlarmTimer Define how long in seconds the UPS must wait after

switching to battery operation before it can generate an

alarm when timed (1) is the value for the

upsAdvConfigAlarm OID. The only allowed values are 0

and 30. If you use any value of 1 second or more, the value

is set to 30. If you use any value less than 1 second, the

value is set to the battery capacity (as a percentage of full capacity)

required before the UPS can return from a low-battery

ConfigMinReturnCapacity21 If a SET specifies an unsupported value, the UPS interprets the value as the next lower allowed

value, as defined by the apcUpsConfigFieldValueRange OID in the tabled set of OIDs

{upsAdvConfigAllowedSetTable}. If the value is less than the lowest allowable value, the lowest

allowed value is used. If a SET specifies an unsupported value, the UPS interprets the value as the next higher allowed

value, as defined by the apcUpsConfigFieldValueRange OID in the tabled set of OIDs

{upsAdvConfigAllowedSetTable}. If the value is higher than the highest allowable value, the

highest allowed value is used.2PowerNet MIB Reference Guide21Chapter 3:How to Configure a UPSOIDTask (page 2 of 3)upsAdvConfigSensitivityDefine the sensitivity of the UPS to input line abnormalities

or “noise.”

•auto (1): The only setting recognized by UPSs with

automatic voltage regulators, e.g Matrix-UPS and

Symmetra UPS.•low (2)

•medium (3)

•high (4)

upsAdvConfigLowBatteryRunTime2Define when a low-battery condition will occur, based on

how much battery runtime remains, in the time in seconds that a UPS in sleep mode will

wait after input power returns before turning on its power

outlets. (In sleep mode, a UPS waits, with its power outlets

turned off, for input power to return.)Define the delay time, in seconds, used for graceful turn-off, reboot, and sleep-control options. (See How to Control

a UPS.) Only Management Cards can use this how long the UPS will remain in timed sleep,

specified as a multiple of 360 seconds (6 minutes). If a SET

provides a value that is not a multiple of 360, the UPS

rounds the value to the nearest multiple of 360, except that

any value from 1 through 540 is rounded to 360. Only

Management Cards can use this OID.

Reset the UPS configuration values to the values set at the

factory. Only Management Cards can use this OID.•noSetEEPROMDefaults (1): The value always returned

by a GET. Setting this value has no effect.•setEEPROMDefaults (2): Resets the ConfigReturnDelay2upsAdvConfigShutoffDelay2upsAdvConfigUpsSleepTime

upsAdvConfigSetEEPROMDefaults

upsAdvConfigPassword Define the 4-byte password used for front-panel access to a

Matrix-UPS or Symmetra UPS. Only Management Cards

can use this OID.1 If a SET specifies an unsupported value, the UPS interprets the value as the next lower allowed

value, as defined by the apcUpsConfigFieldValueRange OID in the tabled set of OIDs

{upsAdvConfigAllowedSetTable}. If the value is less than the lowest allowable value, the lowest

allowed value is used. If a SET specifies an unsupported value, the UPS interprets the value as the next higher allowed

value, as defined by the apcUpsConfigFieldValueRange OID in the tabled set of OIDs

{upsAdvConfigAllowedSetTable}. If the value is higher than the highest allowable value, the

highest allowed value is used.2PowerNet MIB Reference Guide22Chapter 3:How to Test a UPSOIDTask (page 3 of 3){upsAdvConfigAllowedSetTable} {apcUpsConfigEntry}

apcUpsConfigFieldIndex

apcUpsConfigFieldOID

apcUpsConfigFieldValueRange

Obtain the allowed values for all settable OIDs in the

[upsAdvConfig] group.

•The index to an EEPROM field entry.•The OID of the current configurable value.•A comma-delimited list of allowed values for the OID1 If a SET specifies an unsupported value, the UPS interprets the value as the next lower allowed

value, as defined by the apcUpsConfigFieldValueRange OID in the tabled set of OIDs

{upsAdvConfigAllowedSetTable}. If the value is less than the lowest allowable value, the lowest

allowed value is used.2 If a SET specifies an unsupported value, the UPS interprets the value as the next higher allowed

value, as defined by the apcUpsConfigFieldValueRange OID in the tabled set of OIDs

{upsAdvConfigAllowedSetTable}. If the value is higher than the highest allowable value, the

highest allowed value is to Test a UPSThis section contains information on using OIDs to perform UPS self-tests and runtime calibrations.[upsTest]The [upsTest] category contains the [upsAdvTest] sub-category for use by smart-signalling

Management Cards or PowerNet Agents. There are no OIDs in the [upsTest] category for performing

self-tests and calibrations for UPSs connected in simple-signalling mode because simple-signalling

does not support those functions.

[upsAdvTest]You can use the OIDS in the [upsAdvTest] sub-category to schedule or initiate UPS self-tests and

runtime calibrations and to view the results of UPS OIDs in this sub-category have the following limitations on their use:

••A Management Card can use all these OIDS except upsAdvTestLastDiagnosticsDate, which

can be used only by a PowerNet Agent.A PowerNet Agent can use all these OIDs except upsAdvTestRuntimeCalibration, which can

be used only by a Management CardPowerNet MIB Reference Guide23Chapter 3:How to Test a UPSOIDTaskupsAdvTestDiagnosticScheduleDefine the self-test schedule for the UPS:•unknown (1): The Management Card or Agent cannot

determine the setting.•biweekly (2): Self-tests will occur bi-weekly.•weekly (3): A self-test will occur once every week.•atTurnOn (4): A self-test will occur whenever the UPS turns

on.•never (5): No self-test will be TestDiagnosticsCause the UPS to perform an immediate self-test.

•noTestDiagnostics (1): The value always returned by a GET.

Setting this value has no effect.•testDiagnostics (2): Perform the TestDiagnosticsResultsView the result of the last self-test:•ok (1):•failed (2):

•invalidTest (3):•testInProgress (4):

upsAdvTestLastDiagnosticDateupsAdvTestRuntimeCalibrationView the date (in dd/mm/yy format) of the last UPS self-test.

Only smart-signalling PowerNet Agents use this l a runtime calibration:•noPerformCalibration (1): The value always returned by a

GET. Setting this value has no effect.•performCalibration (2): Starts a runtime calibration, if the

UPS battery is at 100% capacity. If the battery capacity is not

at 100%, a SET of this value results in an invalidCalibration

setting for the upsAdvTestCalibrationResults OID.•cancelCurrentCalibration (3): Cancels a runtime a Management Card can use this OID.

upsAdvTestCalibrationResultsView the result of the last runtime calibration:•ok (1): The runtime calibration was successful.•invalidCalibration (2): The last calibration requested did not

take place because battery capacity was less than 100%.•calibrationInProgress (3): A calibration is occurring TestCalibrationDateView the date (in dd/mm/yy format) of the last runtime

calibration. Only smart-signalling PowerNet Agents use this

et MIB Reference Guide24Chapter 3:How to Use OIDs for 3-Phase UPS ModelsHow to Use OIDs for 3-Phase UPS ModelsThe [upsPhase] category has OIDs in three subcategories•[upsPhaseResetValues]: Set of OIDs you use to reset the counters for the corresponding OID

in the [upsPhaseInput] and [upsPhaseOutput] groups that report minimum and maximum

values.[upsPhaseInput]: Set of OIDs you use to obtain information about the input phases.[upsPhaseOutput]: Set of OIDs you use to obtain information about the ouput phases.••To access the values of OIDs in a table, select the OID table in the SNMP browser. (An OID table

appears enclosed in braces {}.) For example, to access the OIDs that provide information on all input

phases for a device, select {upsPhaseInputPhaseTable} in the SNMP browser, and then select

[upsPhaseInputEntry] to see each OID in the table.[upsPhaseResetValues]Use an OID in the [upsPhaseReset Values] group to reset the counters for the corresponding OID in

the [upsPhaseInput] and [upsPhaseOutput] groups that report minimum and maximum kupsBasicControlConserveBatteryupsPhaseInputMaxVoltageupsPhaseInputMinVoltageupsPhaseInputMaxCurrentupsPhaseInputMinCurrentupsPhaseInputMaxPowerupsPhaseInputMinPowerupsPhaseOutputMaxCurrentupsPhaseOutputMinCurrentupsPhaseOutputMaxLoadupsPhaseOutputMinLoadupsPhaseOutputMaxPercentLoadupsPhaseOutputMinPercentLoadupsPhaseOutputMaxPowerupsPhaseOutputMinPowerupsPhaseOutputMaxPercentPowerupsPhaseOutputMinPercentPowerResets the counter for the corresponding OID in the

[upsPhaseInput] and [upsPhaseOutput] groups. For

example, to reset the counter for the OID in the

[upsPhaseInput] category that reports the maximum input

current (upsPhaseInputMaxCurrent), SET to the OID with

that name in this [upsPhaseResetValues] et MIB Reference Guide25Chapter 3:How to Use OIDs for 3-Phase UPS Models[upsPhaseInput]All of the OIDs in this category are read-only except for the upsPhaseInputName OID, a

{upsPhaseInputEntry} in the {upsPhaseInputTable}.OIDTaskupsPhaseNumInputs{upsPhaseInputTable}{upsPhaseInputEntry}upsPhaseInputTableIndexupsPhaseNumInputPhasesupsPhaseInputVoltageOrientationupsPhaseInputFrequencyupsPhaseInputTypeupsPhaseInputName(upsPhaseInputPhaseTable){upsPhaseInputPhaseEntry}upsPhaseInputPhaseTableIndexupsPhaseInputPhaseIndexupsPhaseInputVoltageupsPhaseInputMaxVoltageupsPhaseInputMinVoltageupsPhaseInputCurrentupsPhaseInputMaxCurrentupsPhaseInputMinCurrentupsPhaseInputPowerupsPhaseInputMaxPowerupsPhaseInputMinPowerUse these read-only OIDs to obtain information about the

number of input feeds to the UPS, and information about

each of those the read-only OIDs to obtain the following

information for each input phase:•The input voltage, input current, and input power now.•The minimum and maximum value recorded for the

input voltage, input current, and input power since the

corresponding counters were reset by the OIDs in the

[upsPhaseResetValues] number of entries in the table depends on the sum of

the values reported for upsPhaseNumInputPhases in the

{upsPhaseInputTable} described et MIB Reference Guide26Chapter 3:How to Use OIDs for 3-Phase UPS Models[upsPhaseOutput]All of the OIDs in this category are read-only except for the upsPhaseOutputName OID, a

{upsPhaseOutputEntry} in the {upsPhaseOutputTable}.OIDTaskupsPhaseNumOutputs{upsPhaseOutputTable}{upsPhaseOutputEntry}upsPhaseOutputTableIndexupsPhaseNumOutputPhasesupsPhaseOutputVoltageOrientationupsPhaseOutputFrequencyupsPhaseOutputName(upsPhaseInputPhaseTable){upsPhaseInputPhaseEntry}upsPhaseInputPhaseTableIndexupsPhaseInputPhaseIndexupsPhaseInputVoltageupsPhaseInputMaxVoltageupsPhaseInputMinVoltageupsPhaseInputCurrentupsPhaseInputMaxCurrentupsPhaseInputMinCurrentupsPhaseInputPowerupsPhaseInputMaxPowerupsPhaseInputMinPowerUse these read-only OIDs to obtain information about

the number of output feeds to the UPS, and information

about each of those the read-only OIDs to obtain the following

information for each input phase:•The output voltage, output current, output load and

output power now.•The minimum and maximum value recorded for the

output voltage, output current, output load and output

power since the corresponding counters were reset by

the OIDs in the [upsPhaseResetValues] number of entries in the table depends on the sum of

the values reported for upsPhaseNumOutputPhases in

the {upsPhaseOutputTable} et MIB Reference Guide27Chapter 4:How to Manage an

Environmental MonitorThis chapter describes how to use the following PowerNet MIB OIDs to manage (monitor, configure,

and control) an Environmental Monitor through its Management Card or PowerNet Agent.

•••External Environmental Monitor (em) OIDsIntegrated Environmental Monitor (iem) OIDs (AP9618 or AP9619 Network

Management Card Only)Measure-UPS (mUps) OIDsNote:The external Environmental Monitor (em) OIDs expand on the management

capabilities provided by the mUps OIDs. The mUps OIDS have been kept in the MIB

for compatability with previous versions of the PowerNet al Environmental Monitor (em) OIDsThree categories of em OIDs provide for managing external Environmental Monitors.•••[emIdent] OID[emConfig] OIDs

[emStatus] OIDsTo access these em OIDs in the PowerNet MIB, do the following: [products] under [apc].Select [hardware].Select [environmentalMonitor].Select [external].[emIdent] OIDA single [emIdent] OID, emIdentFirmwareRevision, identifes the firmware used by the

Environmental Monitor.

PowerNet MIB Reference Guide28Chapter 4:External Environmental Monitor (em) OIDs[emConfig] OIDsTwo sets of [emConfig] OIDs are available to configure an external Environmental Monitor:••[emConfigProbes] OIDs[emConfigContacts] OIDs[emConfigProbes] OIDsYou use the following [emConfigProbes] OIDs to view and change values used by the temperature

and humidity probes at an external Environmental kemConfigProbesNumProbes{emConfigProbesTable}

{emConfigProbesEntry}

emConfigProbeNumber

emConfigProbeNameemConfigProbeHighTempThresholdemConfigProbeLowTempThresholdemConfigProbeTempUnitsView how many probes are available (read-only).Access the set of OIDs for each probe and perform the

following:•View the number of the probe to which this set of

OIDs applies (read-only).•Define a descriptive name for the probe.•Set the high-temperature threshold.•Set the low-temperature threshold.•View whether the probe uses Celsius (1) or

Fahrenheit (2) temperature values (read-only).Note:The temperature unit is defined by a system

preferences setting at the igProbeHighHumidThresholdemConfigProbeLowHumidThresholdemConfigProbeHighTempEnableemConfigProbeLowTempEnableemConfigProbeHighHumidEnableemConfigProbeLowHumidEnable•Set the high-humidity threshold.•Set the low-humidity threshold.•Enable or disable the following alarms:-High-temperature threshold alarm-Low-temperature threshold alarm-High-humidity threshold alarm-Low-humidity threshold alarmPowerNet MIB Reference Guide29Chapter 4:External Environmental Monitor (em) OIDs[emConfigContacts] OIDsYou use the following [emConfigContacts] OIDs to view and change values used by the input

contacts at an external Environmental kemConfigContactsNumContacts{emConfigContactsTable}

{emConfigContactsEntry}

emConfigContactNumber

emConfigContactNameemConfigContactEnableView how many contacts are available (read-only).Access the set of OIDs for each input contact and

perform the following:•Identify the contact to which this set of OIDs applies

(read-only).•Define a descriptive name for the contact.•Enable or disable the contact alarm.[emStatus] OIDsThree types of [emStatus] read-only OIDs are available to view the status at an external

Environmental Monitor:•••[emStatusCommStatus] OID[emStatusProbes] OIDs[emStatusProbes] OIDs[emStatusCommStatus] OIDYou use this read-only OID to view the status of the communication between the agent and the external

Environmental DescriptionnoComm (1)comm (2)commLost (3)Communication has not been ication has been ication was lost after it had been et MIB Reference Guide30Chapter 4:External Environmental Monitor (em) OIDs[emStatusProbes] OIDsYou use the following [emStatusProbes] read-only OIDs to view information about the temperature

and humidity probes at an external Environmental ormation ReportedemStatusProbesNumProbes{emStatusProbesTable}

{emStatusProbesEntry}

emStatusProbeNumberemStatusProbeNameemStatusProbeStatusemStatusProbeCurrentTempemStatusProbeTempUnitsThe number of available probesAccess the set of OIDs for each input contact and view

the following information:•The number of the probe•The name of the probe•The disconnected (1) or connected (2) status of the

probe•The current temperature reading at the probe•Whether Celsius (1) or Fahrenheit (2) temperature

values are used by the probeNote:The temperature unit is defined by a system

preferences setting at the usProbeCurrentHumidemStatusProbeHighTempViolationemStatusProbeLowTempViolationemStatusProbeHighHumidViolationemStatusProbeLowHumidViolation•The current humidity reading at the probe•The noViolation (1), highTempViolation (2), or

disabled (3) status of the high-temperature alarm•The noViolation (1), lowTempViolation (2), or

disabled (3) status of the low-temperature alarm•The noViolation (1), highHumidViolation (2), or

disabled (3) status of the high-humidity alarm•The noViolation (1), lowHumidViolation (2), or

disabled (3) status of the low-humidity alarm[emStatusContacts] OIDsYou use the following [emStatusContacts] read-only OIDs to view information about the input

contacts at an external Environmental ormation ReportedemStatusContactsNumContacts{emStatusContactsTable}

{emStatusContactsEntry}

emStatusContactNumber

emStatusContactNameemStatusContactStatusThe number of available contactsAccess the set of OIDs for each input contact and view

the following information:•The number of the contact•The name of the contact•The noFault (1), fault (2), or disabled (3) status of

the contact alarmPowerNet MIB Reference Guide31Chapter 4:Integrated Environmental Monitor (iem) OIDs (AP9618 or AP9619 Network Management Card Only)Integrated Environmental Monitor (iem) OIDs

(AP9618 or AP9619 Network Management Card

Only)Three categories of iem OIDs provide for managing the Integrated Environmental Monitor at an

AP9618 or AP9619 Network Management Card.•••[iemIdent] OID[iemConfig] OIDs

[iemStatus] OIDsNote:The Integrated Environmental Monitor has one probe, two input contacts, and an

output relay access these iem OIDs in the PowerNet MIB, do the following: [products] under [apc].Select [hardware].Select [environmentalMonitor].Select [integrated].[iemIdent] OIDA single [iemIdent] OID, iemIdentHardwareRevision, identifes the hardware version for the

Integrated Environmental Monitor.

[iemConfig] OIDsTwo sets of [iemConfig] OIDs are available to configure an Integrated Environmental Monitor:••[emConfigProbes] OIDs[emConfigContacts] OIDsPowerNet MIB Reference Guide32Chapter 4:Integrated Environmental Monitor (iem) OIDs (AP9618 or AP9619 Network Management Card Only)[iemConfigProbes] OIDsYou use the following [iemConfigProbes] OIDs to view and change values used by the temperature

and humidity probe at an Integrated Environmental kiemConfigProbesNumProbes{iemConfigProbesTable}

{iemConfigProbesEntry}

iemConfigProbeNumber

iemConfigProbeNameiemConfigProbeHighTempThresholdiemConfigProbeLowTempThresholdiemConfigProbeTempUnitsView whether the single probe is available (read-only).Access the set of OIDs for the probe and perform the

following:•View the number of the probe (read only).•Define a descriptive name for the probe.•Set the high-temperature threshold.•Set the low-temperature threshold.•View whether the probe uses Celsius (1) or

Fahrenheit (2) temperature values (read-only).Note:The temperature unit is defined by a system

preferences setting at the figProbeHighHumidThresholdiemConfigProbeLowHumidThresholdiemConfigProbeHighTempEnableiemConfigProbeLowTempEnableiemConfigProbeHighHumidEnableiemConfigProbeLowHumidEnable•Set the high-humidity threshold.•Set the low-humidity threshold.•Enable or disable the following alarms:-High-temperature threshold alarm-Low-temperature threshold alarm-High-humidity threshold alarm-Low-humidity threshold alarm[iemConfigContacts] OIDsYou use the following [iemConfigContacts] OIDs to view and change values used by the input

contacts at an Integrated Environmental kiemConfigContactsNumContacts{iemConfigContactsTable}

{iemConfigContactsEntry}

iemConfigContactNumber

iemConfigContactNameiemConfigContactEnableView how many contacts are available (read-only).Access the set of OIDs for each input contact and

perform the following:•Identify the contact to which this set of OIDs applies

(read-only).•Define a descriptive name for the contact.•Enable or disable the contact et MIB Reference Guide33Chapter 4:Integrated Environmental Monitor (iem) OIDs (AP9618 or AP9619 Network Management Card Only)[iemStatus] OIDsThree types of [iemStatus] read-only OIDs are available to view the status at an external

Environmental Monitor:•••[iemStatusProbes] OIDs[iemStatusContacts] OIDs[iemStatusRelays] OIDs[iemStatusProbes] OIDsYou use the following [iemStatusProbes] read-only OIDs to view information about the temperature

and humidity probes at an Integrated Environmental ormation ReportediemStatusProbesNumProbes{iemStatusProbesTable}{iemStatusProbesEntry}iemStatusProbeNumberiemStatusProbeNameiemStatusProbeStatusiemStatusProbeCurrentTempiemStatusProbeTempUnitsThe number of available probesAccess the set of OIDs for each input contact and view

the following information:•The number of the probe•The name of the probe•The disconnected (1) or connected (2) status of the

probe•The current temperature reading at the probe•Whether Celsius (1) or Fahrenheit (2) temperature

values are used by the probeNote:The temperature unit used is defined by a

system preferences setting at the tusProbeCurrentHumidiemStatusProbeHighTempViolationiemStatusProbeLowTempViolationiemStatusProbeHighHumidViolationiemStatusProbeLowHumidViolation•The current humidity reading at the probe•The noViolation (1), highTempViolation (2), or

disabled (3) status of the high-temperature alarm•The noViolation (1), lowTempViolation (2), or

disabled (3) status of the low-temperature alarm•The noViolation (1), highHumidViolation (2), or

disabled (3) status of the high-humidity alarm•The noViolation (1), lowHumidViolation (2), or

disabled (3) status of the low-humidity alarmPowerNet MIB Reference Guide34Chapter 4:Measure-UPS (mUps) OIDs[iemStatusContacts] OIDsYou use the following [iemStatusContacts] read-only OIDs to view information about the input

contacts at an Integrated Environmental ormation ReportediemStatusContactsNumContacts{iemStatusContactsTable}

{iemStatusContactsEntry}

iemStatusContactNumber

iemStatusContactNameiemStatusContactStatusThe number of available contactsAccess the set of OIDs for each input contact and view

the following information:•The number of the contact•The name of the contact•The noFault (1), fault (2), or disabled (3) status[iemStatusRelays] OIDsYou use the following [iemStatusRelays] read-only OIDs to view information about the output relay

associated with the Integrated Environmental ormation ReportediemStatusRelaysNumRelays{iemStatusRelaysTable}

{iemStatusRelaysEntry}

iemStatusRelayNumber

iemStatusRelayNameiemStatusRelaytStatusThe number of available output relaysAccess the set of OIDs for each output relay and view

the following information:•The number of the output relay•The name of the output relay•The faultState (1) or normalState (2) statusMeasure-UPS (mUps) OIDsTwo categories of mUps OIDs provide for managing external Environmental Monitors through a

Management Card or PowerNet Agent that uses a previous version of the PowerNet MIB.••[mUpsEnviron] Environment OIDs[mUpsContact] Contact OIDS

To access these mUps OIDs in the PowerNet MIB, do the following: [products] under [apc].Select [hardware].Select [measureUps].PowerNet MIB Reference Guide35Chapter 4:Measure-UPS (mUps) OIDs[mUpsEnviron] Environment OIDsAn Environmental Monitor can monitor an environment’s ambient temperature and relative humidity.

You use two read-only [mUpsEnviron] OIDs to view those temperature and humidity ormation ReportedmUpsEnvironAmbientTemperature The ambient temperature, in Celsius or Farrenheit,

depending on the configuration, sensed by the

Environmental vironRelativeHumidity The relative humidity (as a percentage) sensed by the

Environmental Monitor.[mUpsContact] Contact OIDSAn Environmental Monitor or Measure-UPS can have up to four input contacts in use. Each sensor

provides an open contact condition and a closed contact use the following [mUpsContact] OIDs to view and change input contact values for a an

Environmental Monitor or Measure-UPS. However, with an Environmental Monitor you cannot use

an OID to set or view the normal status of the sContactNumContactsTaskDetermine how may input contacts the Environmental Monitor or

Measure-UPS is the set of OIDs for each input contact and perform the

following:•Identify the input contact to which this set of OIDs applies.•Define the input contact’s normal condition for a Measure-UPS: open

(2) or closed (3).

Caution:An Environmental Monitor always report unknown (1) because

the normal condition is not detectable via software.{mUpsContactTable}

{mUpsContactEntry}

contactNumber

normalState

description

monitoringStatus

currentStatus

•Define a brief description of the input contact’s purpose.•Define whether the Measure-UPS will monitor the input contact.-unknown (1): The monitoring status cannot be determined.-enabled (2): The input contact will be monitored.-disabled (3): The input contact will not be monitored.•Identify the current condition of the input contact: unknown (1),

noFault (2) or fault (3).

PowerNet MIB Reference Guide36Chapter 5:How to Manage a

MasterSwitchUnit

This chapter describes how to use PowerNet MIB OIDs to manage a MasterSwitch unit, MasterSwitch VM unit, or

MasterSwitch Plus unit. For information on how to manage the Agent that these units use, see How to Manage the

SNMP Agent at a Hardware Device in Chapter list the five OID categories that you use to manage a MasterSwitch unit, perform the following steps:

[products] under [apc].Select [hardware].Select [masterswitch].TasksOID Categories[sPDUIdent]

[sPDUMasterControl]

[sPDUMasterConfig]

[sPDUOutletControl]

[sPDUOutletConfig]

Identify the MasterSwitch unit by its identification parameter values. See [sPDUIdent]

Identification ly affect the overall operation of the MasterSwitch unit. See [sPDUMasterControl]

Master Control parameters that affect the overall operation of the MasterSwitch unit. See

[sPDUMasterConfig] Master Configuration ly affect the current operation of an outlet at a MasterSwitch unit. See

[sPDUOutletControl] Outlet Control parameters that affect the operation of an outlet at a MasterSwitch unit. See

[sPDUOutletConfig] Outlet Configuration et MIB Reference Guide37Chapter 5:[sPDUIdent] Identification OIDS[sPDUIdent] Identification OIDSThe [sPDUIdent] category has five read-only OIDs that report MasterSwitch unit identification parameter :MasterSwitch unit version 2.x identification parameters reflect the values of the Web/SNMP Management

Card (AP9606)OIDsPDUIdentHardwareRev

sPDUIdentFirmwareRev

sPDUIdentDateOfManufacture

sPDUIdentModelNumber

sPDUIdentSerialNumber

Information ReportedThe MasterSwitch unit’s hardware versionThe MasterSwitch unit’s firmware versionThe date on which the MasterSwitch unit completed the manufacturing process, in

mm/dd/yyyy formatThe MasterSwitch unit’s model numberThe MasterSwitch unit’s serial numberPowerNet MIB Reference Guide38Chapter 5:[sPDUMasterControl] Master Control OIDs[sPDUMasterControl] Master Control OIDsThe [sPDUMasterControl] category has two OIDs that respond to GETs with information about all eight outlets and a

third OID that uses SETs to directly affect the operation of all outlets UMasterControlSwitch

Task

Affect the operation of all outlets.

•turnAllOnNow (1): Immediately turn on all outlets.•turnAllOnSequence (2): Turn on all outlets by using the

sPDUOutletPowerOnTime OID value for each outlet.•turnAllOffNow (3): Immediately turn off all outlets.•rebootAllNow (4): Immediately reboot all outlets by turning off power and then

turning on power based on the master power’s sPDUMasterConfigReboot

configuration OID value.•rebootAllSequence (5):-For firmware version 2.x: Turn off all outlets as described for

turnAllOffSequence, wait the delay time specified as

sPDUMasterConfigReboot, and then turn on all outlets as described for

turnAllOnSequence.-For firmware version 1.x: Reboot all outlets as described for

turnAllOnSequence.

•noCommand (6): The value returned for a GET.•turnAllOffSequence (7): Turn off all outlets by using each outlet’s

sPDUOutletPowerOffTime configuration OID : The turnAllOffSequence (7) setting has no effect when used with

firmware

sPDUMasterState

sPDUMasterPending

Identify the on or off status of the eight fy whether any outlet has a command pending (yes or no).For information on [sPDUMasterConfigReboot] and [sPDUMasterConfigPowerOn], see [sPDUMasterConfig] Master

Configuration OIDs; for information on [sPDUMasterConfigReboot] and [sPDUOutletPowerOnTime] OIDs, see

[sPDUOutletConfig] Outlet Configuration et MIB Reference Guide39Chapter 5:[sPDUMasterConfig] Master Configuration OIDs[sPDUMasterConfig] Master Configuration OIDsThe [sPDUMasterConfig] category has three OIDs that allow you to use SETs to define two overall operational values

and a name for the MasterSwitch unit. If the MasterSwitch unit uses firmware version 2.x, the

sPDUMasterConfigReboot OID is UMasterConfigPowerOn

Task

Define how long a delay will occur after power is applied to the MasterSwitch unit

until it supplies power to the outlets.•-1: Never apply power automatically; you must turn on outlets manually.

•0: Apply power immediately, with no delay.•15: 15-second delay.•30: 30-second delay.•45: 45-second delay.•60: 1-minute delay.•120: 2-minute delay.•300: 5-minute :

Each outlet's sPDUOutletConfigPowerOn Time configuration OID also

affects the time it takes for an outlet to provide power. See [sPDUOutletConfig]

Outlet Configuration sterConfigReboot

Define how long a delay after master power is turned off during a reboot sequence

until master power is turned on again. This OID checks the delay that is set for each

outlet and reports the longest of these delays. This OID is read-only for firmware

•5: 5-second delay.•10: 10-second delay.•15: 15-second delay.•20: 20-second delay.•30: 30-second delay.•45: 45-second delay.•60: 1-minute :

Each outlet's sPDUOutletConfigPowerOnTime configuration OID also affects

the time it takes for an outlet to provide power. See [sPDUOutletConfig] Outlet

Configuration sterConfigPDUName

Define a name (of up to 20 characters) for the MasterSwitch unit.

PowerNet MIB Reference Guide40Chapter 5:[sPDUOutletControl] Outlet Control OIDs[sPDUOutletControl] Outlet Control OIDsThe [sPDUOutletControl] category has a read-only OID and a tabled set of UOutletControlTableSize

{sPDUOutletControlTable} {sPDUOutletControlEntry}

sPDUOutletControlIndex

sPDUOutletPending

TaskIdentify the number of MasterSwitch unit outlets (always 8)View and control each outlet individually:•The outlet number (read-only).•Identify whether the outlet has a command pending:-commandPending (1): A command is pending.-noCommandPending (2): There is no pending command.-commandPendingUnknown (3): This is an error condition. To clear the

condition, shut down all devices powered by the MasterSwitch unit, and turn

power off and then on to the MasterSwitch tletCtl

•Affect the outlet’s current operation.

-outletOn (1): Turn on the outlet’s power.-outletOff (2): Turn off the outlet’s power.-outletReboot (3): Turn off and then turn on the outlet’s power.-outletUnknown (4): This is an error condition. Shut down all devices powered

by the MasterSwitch unit, then turn power off and on to the MasterSwitch unit

to clear the condition.-outletOnWithDelay (5): Not valid for firmware Turn on the

outlet’s power after the delay specified as sPDUOutletPowerOnTime.-outletOffWithDelay (6): Not valid for firmware Turn off the

outlet’s power after the delay specified as sPDUOutletPowerOffTime.-outletRebootWithDelay (7): Not valid for firmware After the

delay specified as sPDUOutletPowerOffTime, turn off the outlet’s power,

wait the time specified as sPDUOutletRebootDuration, and turn on the

outlet’s tletCtlName

•Identify the outlet’s name (20 characters or less) as defined by

sPDUOutletName. See [sPDUOutletConfig] Outlet Configuration et MIB Reference Guide41Chapter 5:[sPDUOutletConfig] Outlet Configuration OIDs[sPDUOutletConfig] Outlet Configuration OIDsThe [sPDUOutletConfig] category has a read-only OID and a tabled set of UOutletConfigTableSize

{sPDUOutletConfigTable} {sPDUOutletConfigEntry}

sPDUOutletConfigIndex

sPDUOutletPowerOnTime

TaskIdentify the number of MasterSwitch unit outlets (always 8).View and configure each outlet individually.•The outlet number (read-only).•Define how long the outlet will wait to provide output power after the

MasterSwitch unit is turned on.

--1: Never start providing output power automatically.-0: Begin providing output power immediately.-15: 15-second delay-30: 30-second delay-45: 45-second delay-60: 1-minute delay-120: 2-minute delay-300: 5-minute delay•Define a name of up to 20 characters for the outlet.

•Not valid for Firmware Define the time that the outlet will wait

after being commanded to turn off its output power until it does turn off its

output power--1: Never stop providing output power automatically-0: Stop providing output power immediately.-15: 15-second delay-30: 30-second delay-45: 45-second delay-60: 1-minute delay-120: 2-minute delay-300: 5-minute delay•Not valid for Firmware Define how long a delay will occur after

power is turned off during a reboot sequence until power is turned on again.-5: 5-second delay-10: 10-second delay-15: 15-second delay-20: 20-second delay-30: 30-second delay-45: 45-second delay-60: 1-minute delaysPDUOutletName

sPDUOutletPowerOffTime

sPDUOutletRebootDuration

PowerNet MIB Reference Guide42