1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 295 296 297 298 299 300 301 302 303 304 305 306 307 308 309 310 311 312 313 314 315 316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 331 332 333 334 335 336 337 338 339 340 341 342 343 344 345 346 347 348 349 350 351 352 353 354 355 356 357 358 359 360 361 362 363 364 365 366 367 368 369 370 371 372 373 374 375 376 377 378 379 380 381 382 383 384 385 386 387 388 389 390 391 392 393 394 395 396 397 398 399 400 401 402 403 404 405 406 407 408 409 410 411 412 413 414 415 416 417 418 419 420 421 422 423 424 425 426 427 428 429 430 431 432 433 434 435 436 437 438 439 440 441 442 443 444 445 446 447 448 449 450 451 452 453 454 455 456 457 458 459 460 461 462 463 464 465 466 467 468 469 470 471 472 473 474 475 476 477 478 479 480 481 482 483 484 485 486 487 488 489 490 491 492 493 494 495 496 497 498 499 500 501 502 503 504 505 506 507 508 509 510 511 512 513 514 515 516 517 518 519 520 521 522 523 524 525 526 527 528 529 530 531 532 533 534 535 536 537 538 539 540 541 542 543 544 545 546 547 548 549 550 551 552 553 554 555 556 557 558 559 560 561 562 563 564 565 566 567 568 569 570 571 572 573 574 575 576 577 578 579 580 581 582 583 584 585 586 587 588 589 590 591 592 593 594 595 596 597 598 599 600 601 602 603 604 605 606 607 608 609 610 611 612 613 614 615 616 617 618 619 620 621 622 623 624 625 626 627 628 629 630 631 632 633 634 635 636 637 638 639 640 641 642 643 644 645 646 647 648 649 650 651 652 653 654 655 656 657 658 659 660 661 662 663 664 665 666 667 668 669 670 671 672 673 674 675 676 677 678 679 680 681 682 683 684 685 686 687 688 689 690 691 692 693 694 695 696 697 698 699 700 701 702 703 704 705 706 707 708 709 710 711 712 713 714 715 716 717 718 719 720 721 722 723 724 725 726 727 728 729 730 731 732 733 734 735 736 737 738 739 740 741 742 743 744 745 746 747 748 749 750 751 752 753 754 755 756 757 758 759 760 761 762 763 764 765 766 767 768 769 770 771 772 773 774 775 776 777 778 779 780 781 782 783 784 785 786 787 788 789 790 791 792 793 794 795 796 797 798 799 800 801 802 803 804 805 806 807 808 809 810 811 812 813 814 815 816 817 818 819 820 821 822 823 824 825 826 827 828 829 830 831 832 833 834 835 836 837 838 839 840 841 842 843 844 845 846 847 848 849 850 851 852 853 854 855 856 857 858 859 860 861 862 863 864 865 866 867 868 869 870 871 872 873 874 875 876 877 878 879 880 881 882 883 884 885 886 887 888 889 890 891 892 893 894 895 896 897 898 899 900 901 902 903 904 905 906 907 908 909 910 911 912 913 914 915 916 917 918 919 920 921 922 923 924 925 926 927 928 929 930 931 932 933 934 935 936 937 938 939 940 941 942 943 944 945 946 947 948 949 950 951 952 953 954 955 956 957 958 959 960 961 962 963 964 965 966 967 968 969 970 971 972 973 974 975 976 977 978 979 980 981 982 983 984 985 986 987 988 989 990 991 992 993 994 995 996 997 998 999 1000 1001 1002 1003 1004 1005 1006 1007 1008 1009 1010 1011 1012 1013 1014 1015 1016 1017 1018 1019 1020 1021 1022 1023 1024 1025 1026 1027 1028 1029 1030 1031 1032 1033 1034 1035 1036 1037 1038 1039 1040 1041 1042 1043 1044 1045 1046 1047 1048 1049 1050 1051 1052 1053 1054 1055 1056 1057 1058 1059 1060 1061 1062 1063 1064 1065 1066 1067 1068 1069 1070 1071 1072 1073 1074 1075 1076 1077 1078 1079 1080 1081 1082 1083 1084 1085 1086 1087 1088 1089 1090 1091 1092 1093 1094 1095 1096 1097 1098 1099 1100 1101 1102 1103 1104 1105 1106 1107 1108 1109 1110 1111 1112 1113 1114 1115 1116 1117 1118 1119 1120 1121 1122 1123 1124 1125 1126 1127 1128 1129 1130 1131 1132 1133 1134 1135 1136 1137 1138 1139 1140 1141 1142 1143 1144 1145 1146 1147 1148 1149 1150 1151 1152 1153 1154 1155 1156 1157 1158 1159 1160 1161 1162 1163 1164 1165 1166 1167 1168 1169 1170 1171 1172 1173 1174 1175 1176 1177 1178 1179 1180 1181 1182 1183 1184 1185 1186 1187 1188 1189 1190 1191 1192 1193 1194 1195 1196 1197 1198 1199 1200 1201 1202 1203 1204 1205 1206 1207 1208 1209 1210 1211 1212 1213 1214 1215 1216 1217 1218 1219 1220 1221 1222 1223 1224 1225 1226 1227 1228 1229 1230 1231 1232 1233 1234 1235 1236 1237 1238 1239 1240 1241 1242 1243 1244 1245 1246 1247 1248 1249 1250 1251 1252 1253 1254 1255 1256 1257 1258 1259 1260 1261 1262 1263 1264 1265 1266 1267 1268 1269 1270 1271 1272 1273 1274 1275 1276 1277 1278 1279 1280 1281 1282 1283 1284 1285 1286 1287 1288 1289 1290 1291 1292 1293 1294 1295 1296 1297 1298 1299 1300 1301 1302 1303 1304 1305 1306 1307 1308 1309 1310 1311 1312 1313 1314 1315 1316 1317 1318 1319 1320 1321 1322 1323 1324 1325 1326 1327 1328 1329 1330 1331 1332 1333 1334 1335 1336 1337 1338 1339 1340 1341 1342 1343 1344 1345 1346 1347 1348 1349 1350 1351 1352 1353 1354 1355 1356 1357 1358 1359 1360 1361 1362 1363 1364 1365 1366 1367 1368 1369 1370 1371 1372 1373 1374 1375 1376 1377 1378 1379 1380 1381 1382 1383 1384 1385 1386 1387 1388 1389 1390 1391 1392 1393 1394 1395 1396 1397 1398 1399 1400 1401 1402 1403 1404 1405 1406 1407 1408 1409 1410 1411 1412 1413 1414 1415 1416 1417 1418 1419 1420 1421 1422 1423 1424 1425 1426 1427 1428 1429 1430 1431 1432 1433 1434 1435 1436 1437 1438 1439 1440 1441 1442 1443 1444 1445 1446 1447 1448 1449 1450 1451 1452 1453 1454 1455 1456 1457 1458 1459 1460 1461 1462 1463 1464 1465 1466 1467 1468 1469 1470 1471 1472 1473 1474 1475 1476 1477 1478 1479 1480 1481 1482 1483 1484 1485 1486 1487 1488 1489 1490 1491 1492 1493 1494 1495 1496 1497 1498 1499 1500 1501 1502 1503 1504 1505 1506 1507 1508 1509 1510 1511 1512 1513 1514 1515 1516 1517 1518 1519 1520 1521 1522 1523 1524 1525 1526 1527 1528 1529 1530 1531 1532 1533 1534 1535 1536 1537 1538 1539 1540 1541 1542 1543 1544 1545 1546 1547 1548 1549 1550 1551 1552 1553 1554 1555 1556 1557 1558 1559 1560 1561 1562 1563 1564 1565 1566 1567 1568 1569 1570 1571 1572 1573 1574 1575 1576 1577 1578 1579 1580 1581 1582 1583 1584 1585 1586 1587 1588 1589 1590 1591 1592 1593 1594 1595 1596 1597 1598 1599 1600 1601 1602 1603 1604 1605 1606 1607 1608 1609 1610 1611 1612 1613 1614 1615 1616 1617 1618 1619 1620 1621 1622 1623 1624 1625 1626 1627 1628 1629 1630 1631 1632 1633 1634 1635 1636 1637 1638 1639 1640 1641 1642 1643 1644 1645 1646 1647 1648 1649 1650 1651 1652 1653 1654 1655 1656 1657 1658 1659 1660 1661 1662 1663 1664 1665 1666 1667 1668 1669 1670 1671 1672 1673 1674 1675 1676 1677 1678 1679 1680 1681 1682 1683 1684 1685 1686 1687 1688 1689 1690 1691 1692 1693 1694 1695 1696 1697 1698 1699 1700 1701 1702 1703 1704 1705 1706 1707 1708 1709 1710 1711 1712 1713 1714 1715 1716 1717 1718 1719 1720 1721 1722 1723 1724 1725 1726 1727 1728 1729 1730 1731 1732 1733 1734 1735 1736 1737 1738 1739 1740 1741 1742 1743 1744 1745 1746 1747 1748 1749 1750 1751 1752 1753 1754 1755 1756 1757 1758 1759 1760 1761 1762 1763 1764 1765 1766 1767 1768 1769 1770 1771 1772 1773 1774 1775 1776 1777 1778 1779 1780 1781 1782 1783 1784 1785 1786 1787 1788 1789 1790 1791 1792 1793 1794 1795 1796 1797 1798 1799 1800 1801 1802 1803 1804 1805 1806 1807 1808 1809 1810 1811 1812 1813 1814 1815 1816 1817 1818 1819 1820 1821 1822 1823 1824 1825 1826 1827 1828 1829 1830 1831 1832 1833 1834 1835 1836 1837 1838 1839 1840 1841 1842 1843 1844 1845 1846 1847 1848 1849 1850 1851 1852 1853 1854 1855 1856 1857 1858 1859 1860 1861 1862 1863 1864 1865 1866 1867 1868 1869 1870 1871 1872 1873 1874 1875 1876 1877 1878 1879 1880 1881 1882 1883 1884 1885 1886 1887 1888 1889 1890 1891 1892 1893 1894 1895 1896 1897 1898 1899 1900 1901 1902 1903 1904 1905 1906 1907 1908 1909 1910 1911 1912 1913 1914 1915 1916 1917 1918 1919 1920 1921 1922 1923 1924 1925 1926 1927 1928 1929 1930 1931 1932 1933 1934 1935 1936 1937 1938 1939 1940 1941 1942 1943 1944 1945 1946 1947 1948 1949 1950 1951 1952 1953 1954 1955 1956 1957 1958 1959 1960 1961 1962 1963 1964 1965 1966 1967 1968 1969 1970 1971 1972 1973 1974 1975 1976 1977 1978 1979 1980 1981 1982 1983 1984 1985 1986 1987 1988 1989 1990 1991 1992 1993 1994 1995 1996 1997 1998 1999 2000 2001 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 2018 2019 2020 2021 2022 2023 2024 2025 2026 2027 2028 2029 2030 2031 2032 2033 2034 2035 2036 2037 2038 2039 2040 2041 2042 2043 2044 2045 2046 2047 2048 2049 2050 2051 2052 2053 2054 2055 2056 2057 2058 2059 2060 2061 2062 2063 2064 2065 2066 2067 2068 2069 2070 2071 2072 2073 2074 2075 2076 2077 2078 2079 2080 2081 2082 2083 2084 2085 2086 2087 2088 2089 2090 2091 2092 2093 2094 2095 2096 2097 2098 2099 2100 2101 2102 2103 2104 2105 2106 2107 2108 2109 2110 2111 2112 2113 2114 2115 2116 2117 2118 2119 2120 2121 2122 2123 2124 2125 2126 2127 2128 2129 2130 2131 2132 2133 2134 2135 2136 2137 2138 2139 2140 2141 2142 2143 2144 2145 2146 2147 2148 2149 2150 2151 2152 2153 2154 2155 2156 2157 2158 2159 2160 2161 2162 2163 2164 2165 2166 2167 2168 2169 2170 2171 2172 2173 2174 2175 2176 2177 2178 2179 2180 2181 2182 2183 2184 2185 2186 2187 2188 2189 2190 2191 2192 2193 2194 2195 2196 2197 2198 2199 2200 2201 2202 2203 2204 2205 2206 2207 2208 2209 2210 2211 2212 2213 2214 2215 2216 2217 2218 2219 2220 2221 2222 2223 2224 2225 2226 2227 2228 2229 2230 2231 2232 2233 2234 2235 2236 2237 2238 2239 2240 2241 2242 2243 2244 2245 2246 2247 2248 2249 2250 2251 2252 2253 2254 2255 2256 2257 2258 2259 2260 2261 2262 2263 2264 2265 2266 2267 2268 2269 2270 2271 2272 2273 2274 2275 2276 2277 2278 2279 2280 2281 2282 2283 2284 2285 2286 2287 2288 2289 2290 2291 2292 2293 2294 2295 2296 2297 2298 2299 2300 2301 2302 2303 2304 2305 2306 2307 2308 2309 2310 2311 2312 2313 2314 2315 2316 2317 2318 2319 2320 2321 2322 2323 2324 2325 2326 2327 2328 2329 2330 2331 2332 2333 2334 2335 2336 2337 2338 2339 2340 2341 2342 2343 2344 2345 2346 2347 2348 2349 2350 2351 2352 2353 2354 2355 2356 2357 2358 2359 2360 2361 2362 2363 2364 2365 2366 2367 2368 2369 2370 2371 2372 2373 2374 2375 2376 2377 2378 2379 2380 2381 2382 2383 2384 2385 2386 2387 2388 2389 2390 2391 2392 2393 2394 2395 2396 2397 2398 2399 2400 2401 2402 2403 2404 2405 2406 2407 2408 2409 2410 2411 2412 2413 2414 2415 2416 2417 2418 2419 2420 2421 2422 2423 2424 2425 2426 2427 2428 2429 2430 2431 2432 2433 2434 2435 2436 2437 2438 2439 2440 2441 2442 2443 2444 2445 2446 2447 2448 2449 2450 2451 2452 2453 2454 2455 2456 2457 2458 2459 2460 2461 2462 2463 2464 2465 2466 2467 2468 2469 2470 2471 2472 2473 2474 2475 2476 2477 2478 2479 2480 2481 2482 2483 2484 2485 2486 2487 2488 2489 2490 2491 2492 2493 2494 2495 2496 2497 2498 2499 2500 2501 2502 2503 2504 2505 2506 2507 2508 2509 2510 2511 2512 2513 2514 2515 2516 2517 2518 2519 2520 2521 2522 2523
|
Network Working Group J. Case, Editor
Request for Comments: 1628 SNMP Research, Incorporated
Category: Standards Track May 1994
UPS Management Information Base
Status of this Memo
This document specifies an Internet standards track protocol for the
Internet community, and requests discussion and suggestions for
improvements. Please refer to the current edition of the "Internet
Official Protocol Standards" (STD 1) for the standardization state
and status of this protocol. Distribution of this memo is unlimited.
Table of Contents
1. Introduction .............................................. 1
2. The SNMPv2 Network Management Framework ................... 2
2.1 Object Definitions ....................................... 2
3. Overview .................................................. 2
4. Definitions ............................................... 3
4.1 The Device Identification Group........................... 4
4.2 The Battery Group ........................................ 5
4.3 The Input Group .......................................... 7
4.4 The Output Group ......................................... 9
4.5 The Bypass Group ......................................... 12
4.6 The Alarm Group .......................................... 13
4.7 The Test Group ........................................... 19
4.8 The Control Group ........................................ 23
4.9 The Configuration Group .................................. 26
5. Acknowledgements .......................................... 43
6. References ................................................ 44
7. Security Considerations ................................... 45
8. Author's Address .......................................... 45
1. Introduction
This memo defines a portion of the Management Information Base (MIB)
for use with network management protocols in the Internet community.
In particular, it defines objects for managing uninterruptible power
supply (UPS) systems.
Case [Page 1]
RFC 1628 UPS MIB May 1994
2. The SNMPv2 Network Management Framework
The SNMPv2 Network Management Framework consists of four major
components. They are:
o RFC 1442 which defines the SMI, the mechanisms used for
describing and naming objects for the purpose of management.
o STD 17, RFC 1213 defines MIB-II, the core set of managed
objects for the Internet suite of protocols.
o RFC 1445 which defines the administrative and other
architectural aspects of the framework.
o RFC 1448 which defines the protocol used for network access
to managed objects.
The Framework permits new objects to be defined for the purpose of
experimentation and evaluation.
2.1. Object Definitions
Managed objects are accessed via a virtual information store, termed
the Management Information Base or MIB. Objects in the MIB are
defined using the subset of Abstract Syntax Notation One (ASN.1)
defined in the SMI. In particular, each object type is named by an
OBJECT IDENTIFIER, an administratively assigned name. The object
type together with an object instance serves to uniquely identify a
specific instantiation of the object. For human convenience, we
often use a textual string, termed the descriptor, to refer to the
object type.
3. Overview
This document defines the managed objects for Uninterruptible Power
Supplies which are to be manageable via the Simple Network Management
Protocol (SNMP).
Case [Page 2]
RFC 1628 UPS MIB May 1994
4. Definitions
UPS-MIB DEFINITIONS ::= BEGIN
IMPORTS
MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE,
OBJECT-IDENTITY, Counter32, Gauge32, Integer32
FROM SNMPv2-SMI
DisplayString, TimeStamp, TimeInterval, TestAndIncr,
AutonomousType
FROM SNMPv2-TC
MODULE-COMPLIANCE, OBJECT-GROUP
FROM SNMPv2-CONF;
upsMIB MODULE-IDENTITY
LAST-UPDATED "9402230000Z"
ORGANIZATION "IETF UPS MIB Working Group"
CONTACT-INFO
" Jeffrey D. Case
Postal: SNMP Research, Incorporated
3001 Kimberlin Heights Road
Knoxville, TN 37920
US
Tel: +1 615 573 1434
Fax: +1 615 573 9197
E-mail: case@snmp.com"
DESCRIPTION
"The MIB module to describe Uninterruptible Power
Supplies."
::= { mib-2 33 }
PositiveInteger ::= TEXTUAL-CONVENTION
DISPLAY-HINT "d"
STATUS current
DESCRIPTION
"This data type is a non-zero and non-negative value."
SYNTAX INTEGER (1..2147483647)
NonNegativeInteger ::= TEXTUAL-CONVENTION
DISPLAY-HINT "d"
STATUS current
DESCRIPTION
"This data type is a non-negative value."
SYNTAX INTEGER (0..2147483647)
Case [Page 3]
RFC 1628 UPS MIB May 1994
upsObjects OBJECT IDENTIFIER ::= { upsMIB 1 }
--
-- The Device Identification group.
-- All objects in this group except for upsIdentName and
-- upsIdentAttachedDevices are set at device initialization
-- and remain static.
--
upsIdent OBJECT IDENTIFIER ::= { upsObjects 1 }
upsIdentManufacturer OBJECT-TYPE
SYNTAX DisplayString (SIZE (0..31))
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The name of the UPS manufacturer."
::= { upsIdent 1 }
upsIdentModel OBJECT-TYPE
SYNTAX DisplayString (SIZE (0..63))
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The UPS Model designation."
::= { upsIdent 2 }
upsIdentUPSSoftwareVersion OBJECT-TYPE
SYNTAX DisplayString (SIZE (0..63))
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The UPS firmware/software version(s). This variable
may or may not have the same value as
upsIdentAgentSoftwareVersion in some implementations."
::= { upsIdent 3 }
upsIdentAgentSoftwareVersion OBJECT-TYPE
SYNTAX DisplayString (SIZE (0..63))
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The UPS agent software version. This variable may or
may not have the same value as
upsIdentUPSSoftwareVersion in some implementations."
::= { upsIdent 4 }
Case [Page 4]
RFC 1628 UPS MIB May 1994
upsIdentName OBJECT-TYPE
SYNTAX DisplayString (SIZE(0..63))
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"A string identifying the UPS. This object should be
set by the administrator."
::= { upsIdent 5 }
upsIdentAttachedDevices OBJECT-TYPE
SYNTAX DisplayString (SIZE(0..63))
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"A string identifying the devices attached to the
output(s) of the UPS. This object should be set by
the administrator."
::= { upsIdent 6 }
--
-- Battery Group
--
upsBattery OBJECT IDENTIFIER ::= { upsObjects 2 }
upsBatteryStatus OBJECT-TYPE
SYNTAX INTEGER {
unknown(1),
batteryNormal(2),
batteryLow(3),
batteryDepleted(4)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The indication of the capacity remaining in the UPS
system's batteries. A value of batteryNormal
indicates that the remaining run-time is greater than
upsConfigLowBattTime. A value of batteryLow indicates
that the remaining battery run-time is less than or
equal to upsConfigLowBattTime. A value of
batteryDepleted indicates that the UPS will be unable
to sustain the present load when and if the utility
power is lost (including the possibility that the
utility power is currently absent and the UPS is
unable to sustain the output)."
::= { upsBattery 1 }
Case [Page 5]
RFC 1628 UPS MIB May 1994
upsSecondsOnBattery OBJECT-TYPE
SYNTAX NonNegativeInteger
UNITS "seconds"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"If the unit is on battery power, the elapsed time
since the UPS last switched to battery power, or the
time since the network management subsystem was last
restarted, whichever is less. Zero shall be returned
if the unit is not on battery power."
::= { upsBattery 2 }
upsEstimatedMinutesRemaining OBJECT-TYPE
SYNTAX PositiveInteger
UNITS "minutes"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"An estimate of the time to battery charge depletion
under the present load conditions if the utility power
is off and remains off, or if it were to be lost and
remain off."
::= { upsBattery 3 }
upsEstimatedChargeRemaining OBJECT-TYPE
SYNTAX INTEGER (0..100)
UNITS "percent"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"An estimate of the battery charge remaining expressed
as a percent of full charge."
::= { upsBattery 4 }
upsBatteryVoltage OBJECT-TYPE
SYNTAX NonNegativeInteger
UNITS "0.1 Volt DC"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The magnitude of the present battery voltage."
::= { upsBattery 5 }
upsBatteryCurrent OBJECT-TYPE
SYNTAX Integer32
UNITS "0.1 Amp DC"
MAX-ACCESS read-only
Case [Page 6]
RFC 1628 UPS MIB May 1994
STATUS current
DESCRIPTION
"The present battery current."
::= { upsBattery 6 }
upsBatteryTemperature OBJECT-TYPE
SYNTAX Integer32
UNITS "degrees Centigrade"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The ambient temperature at or near the UPS Battery
casing."
::= { upsBattery 7 }
--
-- Input Group
--
upsInput OBJECT IDENTIFIER ::= { upsObjects 3 }
upsInputLineBads OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"A count of the number of times the input entered an
out-of-tolerance condition as defined by the
manufacturer. This count is incremented by one each
time the input transitions from zero out-of-tolerance
lines to one or more input lines out-of-tolerance."
::= { upsInput 1 }
upsInputNumLines OBJECT-TYPE
SYNTAX NonNegativeInteger
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of input lines utilized in this device.
This variable indicates the number of rows in the
input table."
::= { upsInput 2 }
upsInputTable OBJECT-TYPE
SYNTAX SEQUENCE OF UpsInputEntry
MAX-ACCESS not-accessible
Case [Page 7]
RFC 1628 UPS MIB May 1994
STATUS current
DESCRIPTION
"A list of input table entries. The number of entries
is given by the value of upsInputNumLines."
::= { upsInput 3 }
upsInputEntry OBJECT-TYPE
SYNTAX UpsInputEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry containing information applicable to a
particular input line."
INDEX { upsInputLineIndex }
::= { upsInputTable 1 }
UpsInputEntry ::= SEQUENCE {
upsInputLineIndex PositiveInteger,
upsInputFrequency NonNegativeInteger,
upsInputVoltage NonNegativeInteger,
upsInputCurrent NonNegativeInteger,
upsInputTruePower NonNegativeInteger
}
upsInputLineIndex OBJECT-TYPE
SYNTAX PositiveInteger
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The input line identifier."
::= { upsInputEntry 1 }
upsInputFrequency OBJECT-TYPE
SYNTAX NonNegativeInteger
UNITS "0.1 Hertz"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The present input frequency."
::= { upsInputEntry 2 }
upsInputVoltage OBJECT-TYPE
SYNTAX NonNegativeInteger
UNITS "RMS Volts"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The magnitude of the present input voltage."
Case [Page 8]
RFC 1628 UPS MIB May 1994
::= { upsInputEntry 3 }
upsInputCurrent OBJECT-TYPE
SYNTAX NonNegativeInteger
UNITS "0.1 RMS Amp"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The magnitude of the present input current."
::= { upsInputEntry 4 }
upsInputTruePower OBJECT-TYPE
SYNTAX NonNegativeInteger
UNITS "Watts"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The magnitude of the present input true power."
::= { upsInputEntry 5 }
--
-- The Output group.
--
upsOutput OBJECT IDENTIFIER ::= { upsObjects 4 }
upsOutputSource OBJECT-TYPE
SYNTAX INTEGER {
other(1),
none(2),
normal(3),
bypass(4),
battery(5),
booster(6),
reducer(7)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The present source of output power. The enumeration
none(2) indicates that there is no source of output
power (and therefore no output power), for example,
the system has opened the output breaker."
::= { upsOutput 1 }
upsOutputFrequency OBJECT-TYPE
SYNTAX NonNegativeInteger
Case [Page 9]
RFC 1628 UPS MIB May 1994
UNITS "0.1 Hertz"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The present output frequency."
::= { upsOutput 2 }
upsOutputNumLines OBJECT-TYPE
SYNTAX NonNegativeInteger
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of output lines utilized in this device.
This variable indicates the number of rows in the
output table."
::= { upsOutput 3 }
upsOutputTable OBJECT-TYPE
SYNTAX SEQUENCE OF UpsOutputEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A list of output table entries. The number of
entries is given by the value of upsOutputNumLines."
::= { upsOutput 4 }
upsOutputEntry OBJECT-TYPE
SYNTAX UpsOutputEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry containing information applicable to a
particular output line."
INDEX { upsOutputLineIndex }
::= { upsOutputTable 1 }
UpsOutputEntry ::= SEQUENCE {
upsOutputLineIndex PositiveInteger,
upsOutputVoltage NonNegativeInteger,
upsOutputCurrent NonNegativeInteger,
upsOutputPower NonNegativeInteger,
upsOutputPercentLoad INTEGER
}
upsOutputLineIndex OBJECT-TYPE
SYNTAX PositiveInteger
MAX-ACCESS not-accessible
STATUS current
Case [Page 10]
RFC 1628 UPS MIB May 1994
DESCRIPTION
"The output line identifier."
::= { upsOutputEntry 1 }
upsOutputVoltage OBJECT-TYPE
SYNTAX NonNegativeInteger
UNITS "RMS Volts"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The present output voltage."
::= { upsOutputEntry 2 }
upsOutputCurrent OBJECT-TYPE
SYNTAX NonNegativeInteger
UNITS "0.1 RMS Amp"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The present output current."
::= { upsOutputEntry 3 }
upsOutputPower OBJECT-TYPE
SYNTAX NonNegativeInteger
UNITS "Watts"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The present output true power."
::= { upsOutputEntry 4 }
upsOutputPercentLoad OBJECT-TYPE
SYNTAX INTEGER (0..200)
UNITS "percent"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The percentage of the UPS power capacity presently
being used on this output line, i.e., the greater of
the percent load of true power capacity and the
percent load of VA."
::= { upsOutputEntry 5 }
Case [Page 11]
RFC 1628 UPS MIB May 1994
--
-- The Bypass group.
--
upsBypass OBJECT IDENTIFIER ::= { upsObjects 5 }
upsBypassFrequency OBJECT-TYPE
SYNTAX NonNegativeInteger
UNITS "0.1 Hertz"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The present bypass frequency."
::= { upsBypass 1 }
upsBypassNumLines OBJECT-TYPE
SYNTAX NonNegativeInteger
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of bypass lines utilized in this device.
This entry indicates the number of rows in the bypass
table."
::= { upsBypass 2 }
upsBypassTable OBJECT-TYPE
SYNTAX SEQUENCE OF UpsBypassEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A list of bypass table entries. The number of
entries is given by the value of upsBypassNumLines."
::= { upsBypass 3 }
upsBypassEntry OBJECT-TYPE
SYNTAX UpsBypassEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry containing information applicable to a
particular bypass input."
INDEX { upsBypassLineIndex }
::= { upsBypassTable 1 }
UpsBypassEntry ::= SEQUENCE {
upsBypassLineIndex PositiveInteger,
upsBypassVoltage NonNegativeInteger,
upsBypassCurrent NonNegativeInteger,
Case [Page 12]
RFC 1628 UPS MIB May 1994
upsBypassPower NonNegativeInteger
}
upsBypassLineIndex OBJECT-TYPE
SYNTAX PositiveInteger
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The bypass line identifier."
::= { upsBypassEntry 1 }
upsBypassVoltage OBJECT-TYPE
SYNTAX NonNegativeInteger
UNITS "RMS Volts"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The present bypass voltage."
::= { upsBypassEntry 2 }
upsBypassCurrent OBJECT-TYPE
SYNTAX NonNegativeInteger
UNITS "0.1 RMS Amp"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The present bypass current."
::= { upsBypassEntry 3 }
upsBypassPower OBJECT-TYPE
SYNTAX NonNegativeInteger
UNITS "Watts"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The present true power conveyed by the bypass."
::= { upsBypassEntry 4 }
--
-- The Alarm group.
--
upsAlarm OBJECT IDENTIFIER ::= { upsObjects 6 }
upsAlarmsPresent OBJECT-TYPE
SYNTAX Gauge32
MAX-ACCESS read-only
Case [Page 13]
RFC 1628 UPS MIB May 1994
STATUS current
DESCRIPTION
"The present number of active alarm conditions."
::= { upsAlarm 1 }
upsAlarmTable OBJECT-TYPE
SYNTAX SEQUENCE OF UpsAlarmEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A list of alarm table entries. The table contains
zero, one, or many rows at any moment, depending upon
the number of alarm conditions in effect. The table
is initially empty at agent startup. The agent
creates a row in the table each time a condition is
detected and deletes that row when that condition no
longer pertains. The agent creates the first row with
upsAlarmId equal to 1, and increments the value of
upsAlarmId each time a new row is created, wrapping to
the first free value greater than or equal to 1 when
the maximum value of upsAlarmId would otherwise be
exceeded. Consequently, after multiple operations,
the table may become sparse, e.g., containing entries
for rows 95, 100, 101, and 203 and the entries should
not be assumed to be in chronological order because
upsAlarmId might have wrapped.
Alarms are named by an AutonomousType (OBJECT
IDENTIFIER), upsAlarmDescr, to allow a single table to
reflect well known alarms plus alarms defined by a
particular implementation, i.e., as documented in the
private enterprise MIB definition for the device. No
two rows will have the same value of upsAlarmDescr,
since alarms define conditions. In order to meet this
requirement, care should be taken in the definition of
alarm conditions to insure that a system cannot enter
the same condition multiple times simultaneously.
The number of rows in the table at any given time is
reflected by the value of upsAlarmsPresent."
::= { upsAlarm 2 }
upsAlarmEntry OBJECT-TYPE
SYNTAX UpsAlarmEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry containing information applicable to a
Case [Page 14]
RFC 1628 UPS MIB May 1994
particular alarm."
INDEX { upsAlarmId }
::= { upsAlarmTable 1 }
UpsAlarmEntry ::= SEQUENCE {
upsAlarmId PositiveInteger,
upsAlarmDescr AutonomousType,
upsAlarmTime TimeStamp
}
upsAlarmId OBJECT-TYPE
SYNTAX PositiveInteger
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A unique identifier for an alarm condition. This
value must remain constant."
::= { upsAlarmEntry 1 }
upsAlarmDescr OBJECT-TYPE
SYNTAX AutonomousType
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"A reference to an alarm description object. The
object referenced should not be accessible, but rather
be used to provide a unique description of the alarm
condition."
::= { upsAlarmEntry 2 }
upsAlarmTime OBJECT-TYPE
SYNTAX TimeStamp
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The value of sysUpTime when the alarm condition was
detected. If the alarm condition was detected at the
time of agent startup and presumably existed before
agent startup, the value of upsAlarmTime shall equal
0."
::= { upsAlarmEntry 3 }
--
-- Well known alarm conditions.
--
upsWellKnownAlarms OBJECT IDENTIFIER ::= { upsAlarm 3 }
Case [Page 15]
RFC 1628 UPS MIB May 1994
upsAlarmBatteryBad OBJECT-IDENTITY
STATUS current
DESCRIPTION
"One or more batteries have been determined to require
replacement."
::= { upsWellKnownAlarms 1 }
upsAlarmOnBattery OBJECT-IDENTITY
STATUS current
DESCRIPTION
"The UPS is drawing power from the batteries."
::= { upsWellKnownAlarms 2 }
upsAlarmLowBattery OBJECT-IDENTITY
STATUS current
DESCRIPTION
"The remaining battery run-time is less than or equal
to upsConfigLowBattTime."
::= { upsWellKnownAlarms 3 }
upsAlarmDepletedBattery OBJECT-IDENTITY
STATUS current
DESCRIPTION
"The UPS will be unable to sustain the present load
when and if the utility power is lost."
::= { upsWellKnownAlarms 4 }
upsAlarmTempBad OBJECT-IDENTITY
STATUS current
DESCRIPTION
"A temperature is out of tolerance."
::= { upsWellKnownAlarms 5 }
upsAlarmInputBad OBJECT-IDENTITY
STATUS current
DESCRIPTION
"An input condition is out of tolerance."
::= { upsWellKnownAlarms 6 }
upsAlarmOutputBad OBJECT-IDENTITY
STATUS current
DESCRIPTION
"An output condition (other than OutputOverload) is
out of tolerance."
::= { upsWellKnownAlarms 7 }
upsAlarmOutputOverload OBJECT-IDENTITY
Case [Page 16]
RFC 1628 UPS MIB May 1994
STATUS current
DESCRIPTION
"The output load exceeds the UPS output capacity."
::= { upsWellKnownAlarms 8 }
upsAlarmOnBypass OBJECT-IDENTITY
STATUS current
DESCRIPTION
"The Bypass is presently engaged on the UPS."
::= { upsWellKnownAlarms 9 }
upsAlarmBypassBad OBJECT-IDENTITY
STATUS current
DESCRIPTION
"The Bypass is out of tolerance."
::= { upsWellKnownAlarms 10 }
upsAlarmOutputOffAsRequested OBJECT-IDENTITY
STATUS current
DESCRIPTION
"The UPS has shutdown as requested, i.e., the output
is off."
::= { upsWellKnownAlarms 11 }
upsAlarmUpsOffAsRequested OBJECT-IDENTITY
STATUS current
DESCRIPTION
"The entire UPS has shutdown as commanded."
::= { upsWellKnownAlarms 12 }
upsAlarmChargerFailed OBJECT-IDENTITY
STATUS current
DESCRIPTION
"An uncorrected problem has been detected within the
UPS charger subsystem."
::= { upsWellKnownAlarms 13 }
upsAlarmUpsOutputOff OBJECT-IDENTITY
STATUS current
DESCRIPTION
"The output of the UPS is in the off state."
::= { upsWellKnownAlarms 14 }
upsAlarmUpsSystemOff OBJECT-IDENTITY
STATUS current
DESCRIPTION
"The UPS system is in the off state."
::= { upsWellKnownAlarms 15 }
Case [Page 17]
RFC 1628 UPS MIB May 1994
upsAlarmFanFailure OBJECT-IDENTITY
STATUS current
DESCRIPTION
"The failure of one or more fans in the UPS has been
detected."
::= { upsWellKnownAlarms 16 }
upsAlarmFuseFailure OBJECT-IDENTITY
STATUS current
DESCRIPTION
"The failure of one or more fuses has been detected."
::= { upsWellKnownAlarms 17 }
upsAlarmGeneralFault OBJECT-IDENTITY
STATUS current
DESCRIPTION
"A general fault in the UPS has been detected."
::= { upsWellKnownAlarms 18 }
upsAlarmDiagnosticTestFailed OBJECT-IDENTITY
STATUS current
DESCRIPTION
"The result of the last diagnostic test indicates a
failure."
::= { upsWellKnownAlarms 19 }
upsAlarmCommunicationsLost OBJECT-IDENTITY
STATUS current
DESCRIPTION
"A problem has been encountered in the communications
between the agent and the UPS."
::= { upsWellKnownAlarms 20 }
upsAlarmAwaitingPower OBJECT-IDENTITY
STATUS current
DESCRIPTION
"The UPS output is off and the UPS is awaiting the
return of input power."
::= { upsWellKnownAlarms 21 }
upsAlarmShutdownPending OBJECT-IDENTITY
STATUS current
DESCRIPTION
"A upsShutdownAfterDelay countdown is underway."
::= { upsWellKnownAlarms 22 }
upsAlarmShutdownImminent OBJECT-IDENTITY
STATUS current
Case [Page 18]
RFC 1628 UPS MIB May 1994
DESCRIPTION
"The UPS will turn off power to the load in less than
5 seconds; this may be either a timed shutdown or a
low battery shutdown."
::= { upsWellKnownAlarms 23 }
upsAlarmTestInProgress OBJECT-IDENTITY
STATUS current
DESCRIPTION
"A test is in progress, as initiated and indicated by
the Test Group. Tests initiated via other
implementation-specific mechanisms can indicate the
presence of the testing in the alarm table, if
desired, via a OBJECT-IDENTITY macro in the MIB
document specific to that implementation and are
outside the scope of this OBJECT-IDENTITY."
::= { upsWellKnownAlarms 24 }
--
-- The Test Group
--
upsTest OBJECT IDENTIFIER ::= { upsObjects 7 }
upsTestId OBJECT-TYPE
SYNTAX OBJECT IDENTIFIER
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"The test is named by an OBJECT IDENTIFIER which
allows a standard mechanism for the initiation of
tests, including the well known tests identified in
this document as well as those introduced by a
particular implementation, i.e., as documented in the
private enterprise MIB definition for the device.
Setting this variable initiates the named test. Sets
to this variable require the presence of
upsTestSpinLock in the same SNMP message.
The set request will be rejected with an appropriate
error message if the requested test cannot be
performed, including attempts to start a test when
another test is already in progress. The status of
the current or last test is maintained in
upsTestResultsSummary. Tests in progress may be
aborted by setting the upsTestId variable to
Case [Page 19]
RFC 1628 UPS MIB May 1994
upsTestAbortTestInProgress.
Read operations return the value of the name of the
test in progress if a test is in progress or the name
of the last test performed if no test is in progress,
unless no test has been run, in which case the well
known value upsTestNoTestsInitiated is returned."
::= { upsTest 1 }
-- see [6] for more information on the semantics of objects with
-- syntax of TestAndIncr
upsTestSpinLock OBJECT-TYPE
SYNTAX TestAndIncr
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"A spin lock on the test subsystem. The spinlock is
used as follows.
Before starting a test, a manager-station should make
sure that a test is not in progress as follows:
try_again:
get (upsTestSpinLock)
while (upsTestResultsSummary == inProgress) {
/* loop while a test is running for another
manager */
short delay
get (upsTestSpinLock)
}
lock_value = upsTestSpinLock
/* no test in progress, start the test */
set (upsTestSpinLock = lock_value, upsTestId =
requested_test)
if (error_index == 1) { /* (upsTestSpinLock
failed) */
/* if problem is not access control, then
some other manager slipped in ahead of us
*/
goto try_again
}
if (error_index == 2) { /* (upsTestId) */
/* cannot perform the test */
give up
}
/* test started ok */
/* wait for test completion by polling
Case [Page 20]
RFC 1628 UPS MIB May 1994
upsTestResultsSummary */
get (upsTestSpinLock, upsTestResultsSummary,
upsTestResultsDetail)
while (upsTestResultsSummary == inProgress) {
short delay
get (upsTestSpinLock, upsTestResultsSummary,
upsTestResultsDetail)
}
/* when test completes, retrieve any additional
test results */
/* if upsTestSpinLock == lock_value + 1, then
these are our test */
/* results (as opposed to another manager's */
The initial value of upsTestSpinLock at agent
initialization shall
be 1."
::= { upsTest 2 }
upsTestResultsSummary OBJECT-TYPE
SYNTAX INTEGER {
donePass(1),
doneWarning(2),
doneError(3),
aborted(4),
inProgress(5),
noTestsInitiated(6)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The results of the current or last UPS diagnostics
test performed. The values for donePass(1),
doneWarning(2), and doneError(3) indicate that the
test completed either successfully, with a warning, or
with an error, respectively. The value aborted(4) is
returned for tests which are aborted by setting the
value of upsTestId to upsTestAbortTestInProgress.
Tests which have not yet concluded are indicated by
inProgress(5). The value noTestsInitiated(6)
indicates that no previous test results are available,
such as is the case when no tests have been run since
the last reinitialization of the network management
subsystem and the system has no provision for non-
volatile storage of test results."
::= { upsTest 3 }
upsTestResultsDetail OBJECT-TYPE
SYNTAX DisplayString (SIZE (0..255))
Case [Page 21]
RFC 1628 UPS MIB May 1994
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Additional information about upsTestResultsSummary.
If no additional information available, a zero length
string is returned."
::= { upsTest 4 }
upsTestStartTime OBJECT-TYPE
SYNTAX TimeStamp
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The value of sysUpTime at the time the test in
progress was initiated, or, if no test is in progress,
the time the previous test was initiated. If the
value of upsTestResultsSummary is noTestsInitiated(6),
upsTestStartTime has the value 0."
::= { upsTest 5 }
upsTestElapsedTime OBJECT-TYPE
SYNTAX TimeInterval
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The amount of time, in TimeTicks, since the test in
progress was initiated, or, if no test is in progress,
the previous test took to complete. If the value of
upsTestResultsSummary is noTestsInitiated(6),
upsTestElapsedTime has the value 0."
::= { upsTest 6 }
--
-- Well known tests.
--
upsWellKnownTests OBJECT IDENTIFIER ::= { upsTest 7 }
upsTestNoTestsInitiated OBJECT-IDENTITY
STATUS current
DESCRIPTION
"No tests have been initiated and no test is in
progress."
::= { upsWellKnownTests 1 }
upsTestAbortTestInProgress OBJECT-IDENTITY
STATUS current
Case [Page 22]
RFC 1628 UPS MIB May 1994
DESCRIPTION
"The test in progress is to be aborted / the test in
progress was aborted."
::= { upsWellKnownTests 2 }
upsTestGeneralSystemsTest OBJECT-IDENTITY
STATUS current
DESCRIPTION
"The manufacturer's standard test of UPS device
systems."
::= { upsWellKnownTests 3 }
upsTestQuickBatteryTest OBJECT-IDENTITY
STATUS current
DESCRIPTION
"A test that is sufficient to determine if the battery
needs replacement."
::= { upsWellKnownTests 4 }
upsTestDeepBatteryCalibration OBJECT-IDENTITY
STATUS current
DESCRIPTION
"The system is placed on battery to a discharge level,
set by the manufacturer, sufficient to determine
battery replacement and battery run-time with a high
degree of confidence. WARNING: this test will leave
the battery in a low charge state and will require
time for recharging to a level sufficient to provide
normal battery duration for the protected load."
::= { upsWellKnownTests 5 }
--
-- The Control group.
--
upsControl OBJECT IDENTIFIER ::= { upsObjects 8 }
upsShutdownType OBJECT-TYPE
SYNTAX INTEGER {
output(1),
system(2)
}
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"This object determines the nature of the action to be
taken at the time when the countdown of the
Case [Page 23]
RFC 1628 UPS MIB May 1994
upsShutdownAfterDelay and upsRebootWithDuration
objects reaches zero.
Setting this object to output(1) indicates that
shutdown requests should cause only the output of the
UPS to turn off. Setting this object to system(2)
indicates that shutdown requests will cause the entire
UPS system to turn off."
::= { upsControl 1 }
upsShutdownAfterDelay OBJECT-TYPE
SYNTAX INTEGER (-1..2147483648)
UNITS "seconds"
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"Setting this object will shutdown (i.e., turn off)
either the UPS output or the UPS system (as determined
by the value of upsShutdownType at the time of
shutdown) after the indicated number of seconds, or
less if the UPS batteries become depleted. Setting
this object to 0 will cause the shutdown to occur
immediately. Setting this object to -1 will abort the
countdown. If the system is already in the desired
state at the time the countdown reaches 0, then
nothing will happen. That is, there is no additional
action at that time if upsShutdownType = system and
the system is already off. Similarly, there is no
additional action at that time if upsShutdownType =
output and the output is already off. When read,
upsShutdownAfterDelay will return the number of
seconds remaining until shutdown, or -1 if no shutdown
countdown is in effect. On some systems, if the agent
is restarted while a shutdown countdown is in effect,
the countdown may be aborted. Sets to this object
override any upsShutdownAfterDelay already in effect."
::= { upsControl 2 }
upsStartupAfterDelay OBJECT-TYPE
SYNTAX INTEGER (-1..2147483648)
UNITS "seconds"
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"Setting this object will start the output after the
indicated number of seconds, including starting the
UPS, if necessary. Setting this object to 0 will
cause the startup to occur immediately. Setting this
Case [Page 24]
RFC 1628 UPS MIB May 1994
object to -1 will abort the countdown. If the output
is already on at the time the countdown reaches 0,
then nothing will happen. Sets to this object
override the effect of any upsStartupAfterDelay
countdown or upsRebootWithDuration countdown in
progress. When read, upsStartupAfterDelay will return
the number of seconds until startup, or -1 if no
startup countdown is in effect. If the countdown
expires during a utility failure, the startup shall
not occur until the utility power is restored. On
some systems, if the agent is restarted while a
startup countdown is in effect, the countdown is
aborted."
::= { upsControl 3 }
upsRebootWithDuration OBJECT-TYPE
SYNTAX INTEGER (-1..300)
UNITS "seconds"
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"Setting this object will immediately shutdown (i.e.,
turn off) either the UPS output or the UPS system (as
determined by the value of upsShutdownType at the time
of shutdown) for a period equal to the indicated
number of seconds, after which time the output will be
started, including starting the UPS, if necessary. If
the number of seconds required to perform the request
is greater than the requested duration, then the
requested shutdown and startup cycle shall be
performed in the minimum time possible, but in no case
shall this require more than the requested duration
plus 60 seconds. When read, upsRebootWithDuration
shall return the number of seconds remaining in the
countdown, or -1 if no countdown is in progress. If
the startup should occur during a utility failure, the
startup shall not occur until the utility power is
restored."
::= { upsControl 4 }
upsAutoRestart OBJECT-TYPE
SYNTAX INTEGER {
on(1),
off(2)
}
MAX-ACCESS read-write
STATUS current
DESCRIPTION
Case [Page 25]
RFC 1628 UPS MIB May 1994
"Setting this object to 'on' will cause the UPS system
to restart after a shutdown if the shutdown occurred
during a power loss as a result of either a
upsShutdownAfterDelay or an internal battery depleted
condition. Setting this object to 'off' will prevent
the UPS system from restarting after a shutdown until
an operator manually or remotely explicitly restarts
it. If the UPS is in a startup or reboot countdown,
then the UPS will not restart until that delay has
been satisfied."
::= { upsControl 5 }
--
-- The Configuration group.
--
upsConfig OBJECT IDENTIFIER ::= { upsObjects 9 }
upsConfigInputVoltage OBJECT-TYPE
SYNTAX NonNegativeInteger
UNITS "RMS Volts"
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"The magnitude of the nominal input voltage. On those
systems which support read-write access to this
object, if there is an attempt to set this variable to
a value that is not supported, the request must be
rejected and the agent shall respond with an
appropriate error message, i.e., badValue for SNMPv1,
or inconsistentValue for SNMPv2."
::= { upsConfig 1 }
upsConfigInputFreq OBJECT-TYPE
SYNTAX NonNegativeInteger
UNITS "0.1 Hertz"
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"The nominal input frequency. On those systems which
support read-write access to this object, if there is
an attempt to set this variable to a value that is not
supported, the request must be rejected and the agent
shall respond with an appropriate error message, i.e.,
badValue for SNMPv1, or inconsistentValue for SNMPv2."
::= { upsConfig 2 }
Case [Page 26]
RFC 1628 UPS MIB May 1994
upsConfigOutputVoltage OBJECT-TYPE
SYNTAX NonNegativeInteger
UNITS "RMS Volts"
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"The magnitude of the nominal output voltage. On
those systems which support read-write access to this
object, if there is an attempt to set this variable to
a value that is not supported, the request must be
rejected and the agent shall respond with an
appropriate error message, i.e., badValue for SNMPv1,
or inconsistentValue for SNMPv2."
::= { upsConfig 3 }
upsConfigOutputFreq OBJECT-TYPE
SYNTAX NonNegativeInteger
UNITS "0.1 Hertz"
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"The nominal output frequency. On those systems which
support read-write access to this object, if there is
an attempt to set this variable to a value that is not
supported, the request must be rejected and the agent
shall respond with an appropriate error message, i.e.,
badValue for SNMPv1, or inconsistentValue for SNMPv2."
::= { upsConfig 4 }
upsConfigOutputVA OBJECT-TYPE
SYNTAX NonNegativeInteger
UNITS "Volt-Amps"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The magnitude of the nominal Volt-Amp rating."
::= { upsConfig 5 }
upsConfigOutputPower OBJECT-TYPE
SYNTAX NonNegativeInteger
UNITS "Watts"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The magnitude of the nominal true power rating."
::= { upsConfig 6 }
upsConfigLowBattTime OBJECT-TYPE
Case [Page 27]
RFC 1628 UPS MIB May 1994
SYNTAX NonNegativeInteger
UNITS "minutes"
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"The value of upsEstimatedMinutesRemaining at which a
lowBattery condition is declared. For agents which
support only discrete (discontinuous) values, then the
agent shall round up to the next supported value. If
the requested value is larger than the largest
supported value, then the largest supported value
shall be selected."
::= { upsConfig 7 }
upsConfigAudibleStatus OBJECT-TYPE
SYNTAX INTEGER {
disabled(1),
enabled(2),
muted(3)
}
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"The requested state of the audible alarm. When in
the disabled state, the audible alarm should never
sound. The enabled state is self-describing. Setting
this object to muted(3) when the audible alarm is
sounding shall temporarily silence the alarm. It will
remain muted until it would normally stop sounding and
the value returned for read operations during this
period shall equal muted(3). At the end of this
period, the value shall revert to enabled(2). Writes
of the value muted(3) when the audible alarm is not
sounding shall be accepted but otherwise shall have no
effect."
::= { upsConfig 8 }
upsConfigLowVoltageTransferPoint OBJECT-TYPE
SYNTAX NonNegativeInteger
UNITS "RMS Volts"
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"The minimum input line voltage allowed before the UPS
system transfers to battery backup."
::= { upsConfig 9 }
upsConfigHighVoltageTransferPoint OBJECT-TYPE
Case [Page 28]
RFC 1628 UPS MIB May 1994
SYNTAX NonNegativeInteger
UNITS "RMS Volts"
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"The maximum line voltage allowed before the UPS
system transfers to battery backup."
::= { upsConfig 10 }
--
-- notifications, i.e., traps
--
upsTraps OBJECT IDENTIFIER ::= { upsMIB 2 }
-- This section defines the well-known notifications sent by
-- UPS agents.
-- Care must be taken to insure that no particular notification
-- is sent to a single receiving entity more often than once
-- every five seconds.
upsTrapOnBattery NOTIFICATION-TYPE
OBJECTS { upsEstimatedMinutesRemaining, upsSecondsOnBattery,
upsConfigLowBattTime }
STATUS current
DESCRIPTION
"The UPS is operating on battery power. This trap is
persistent and is resent at one minute intervals until
the UPS either turns off or is no longer running on
battery."
::= { upsTraps 1 }
upsTrapTestCompleted NOTIFICATION-TYPE
OBJECTS { upsTestId, upsTestSpinLock,
upsTestResultsSummary, upsTestResultsDetail,
upsTestStartTime, upsTestElapsedTime }
STATUS current
DESCRIPTION
"This trap is sent upon completion of a UPS diagnostic
test."
::= { upsTraps 2 }
upsTrapAlarmEntryAdded NOTIFICATION-TYPE
OBJECTS { upsAlarmId, upsAlarmDescr }
STATUS current
DESCRIPTION
"This trap is sent each time an alarm is inserted into
to the alarm table. It is sent on the insertion of
Case [Page 29]
RFC 1628 UPS MIB May 1994
all alarms except for upsAlarmOnBattery and
upsAlarmTestInProgress."
::= { upsTraps 3 }
upsTrapAlarmEntryRemoved NOTIFICATION-TYPE
OBJECTS { upsAlarmId, upsAlarmDescr }
STATUS current
DESCRIPTION
"This trap is sent each time an alarm is removed from
the alarm table. It is sent on the removal of all
alarms except for upsAlarmTestInProgress."
::= { upsTraps 4 }
--
-- conformance information
--
upsConformance OBJECT IDENTIFIER ::= { upsMIB 3 }
upsCompliances OBJECT IDENTIFIER ::= { upsConformance 1 }
--
-- compliance statements
--
upsSubsetCompliance MODULE-COMPLIANCE
STATUS current
DESCRIPTION
"The compliance statement for UPSs that only support
the two-contact communication protocol."
MODULE -- this module
MANDATORY-GROUPS { upsSubsetIdentGroup,
upsSubsetBatteryGroup, upsSubsetInputGroup,
upsSubsetOutputGroup, upsSubsetAlarmGroup,
upsSubsetControlGroup, upsSubsetConfigGroup }
OBJECT upsBatteryStatus
SYNTAX INTEGER {
batteryNormal(2),
batteryLow(3)
}
DESCRIPTION
"Support of the values unknown(1) and
batteryDepleted(4) is not required."
OBJECT upsAlarmDescr
Case [Page 30]
RFC 1628 UPS MIB May 1994
DESCRIPTION
"Support of all `well known' alarm types is not
required. The well known alarm types which must be
supported are: upsAlarmOnBattery, upsAlarmLowBattery,
upsAlarmInputBad, upsAlarmUpsOutputOff,
upsAlarmUpsSystemOff, and upsAlarmTestInProgress."
OBJECT upsOutputSource
SYNTAX INTEGER {
normal(2),
battery(4)
}
DESCRIPTION
"Support of the values other(1), none(2), bypass(4),
booster(6) and reducer(7) is not required."
OBJECT upsShutdownType
MIN-ACCESS read-only
DESCRIPTION
"Read-write access is not required, i.e., compliant
systems need not support more than one shutdown type."
OBJECT upsAutoRestart
MIN-ACCESS read-only
DESCRIPTION
"Read-write access is not required, i.e., compliant
systems need not support more than one restart type."
OBJECT upsConfigInputVoltage
MIN-ACCESS read-only
DESCRIPTION
"Read-write access is not required."
OBJECT upsConfigInputFreq
MIN-ACCESS read-only
DESCRIPTION
"Read-write access is not required."
OBJECT upsConfigOutputVoltage
MIN-ACCESS read-only
DESCRIPTION
"Read-write access is not required."
OBJECT upsConfigOutputFreq
MIN-ACCESS read-only
DESCRIPTION
"Read-write access is not required."
Case [Page 31]
RFC 1628 UPS MIB May 1994
::= { upsCompliances 1 }
upsBasicCompliance MODULE-COMPLIANCE
STATUS current
DESCRIPTION
"The compliance statement for UPSs that support
full-featured functions, such as control."
MODULE -- this module
MANDATORY-GROUPS { upsBasicIdentGroup,
upsBasicBatteryGroup, upsBasicInputGroup,
upsBasicOutputGroup, upsBasicAlarmGroup,
upsBasicTestGroup, upsBasicControlGroup,
upsBasicConfigGroup }
OBJECT upsAlarmDescr
DESCRIPTION
"Support of all `well known' alarm types is not
required. The well known alarm types which must be
supported are: upsAlarmOnBattery, upsAlarmLowBattery,
upsAlarmDepletedBattery, upsAlarmTempBad,
upsAlarmInputBad, upsAlarmOutputOverload,
upsAlarmOnBypass, upsAlarmBypassBad,
upsAlarmOutputOffAsRequested,
upsAlarmUpsOffAsRequested, upsAlarmUpsOutputOff,
upsAlarmUpsSystemOff, upsAlarmGeneralFault,
upsAlarmDiagnosticTestFailed,
upsAlarmCommunicationsLost, upsAlarmShutdownPending,
and upsAlarmTestInProgress."
OBJECT upsTestId
DESCRIPTION
"Support of all `well known' test types is not
required. If no tests are supported, then the only
well known test type which must be supported is
upsTestNoTestsInitiated."
OBJECT upsOutputSource
SYNTAX INTEGER {
normal(2),
battery(4)
}
DESCRIPTION
"Support of the values other(1), none(2), bypass(4),
booster(6) and reducer(7) is not required."
GROUP upsBasicBypassGroup
Case [Page 32]
RFC 1628 UPS MIB May 1994
DESCRIPTION
"The upsBasicBypassGroup is only required for UPSs
that have a Bypass present."
OBJECT upsShutdownType
MIN-ACCESS read-only
DESCRIPTION
"Read-write access is not required, i.e., compliant
systems need not support more than one shutdown type."
OBJECT upsAutoRestart
MIN-ACCESS read-only
DESCRIPTION
"Read-write access is not required, i.e., compliant
systems need not support more than one restart type."
OBJECT upsConfigInputVoltage
MIN-ACCESS read-only
DESCRIPTION
"Read-write access is not required."
OBJECT upsConfigInputFreq
MIN-ACCESS read-only
DESCRIPTION
"Read-write access is not required."
OBJECT upsConfigOutputVoltage
MIN-ACCESS read-only
DESCRIPTION
"Read-write access is not required."
OBJECT upsConfigOutputFreq
MIN-ACCESS read-only
DESCRIPTION
"Read-write access is not required."
OBJECT upsConfigLowBattTime
DESCRIPTION
"Implementation of all possible values may be onerous
for some systems. Consequently, not all possible
values must be supported. However, at least two
different manufacturer-selected values must be
supported."
::= { upsCompliances 2 }
upsFullCompliance MODULE-COMPLIANCE
STATUS current
DESCRIPTION
Case [Page 33]
RFC 1628 UPS MIB May 1994
"The compliance statement for UPSs that support
advanced full-featured functions."
MODULE -- this module
MANDATORY-GROUPS { upsFullIdentGroup, upsFullBatteryGroup,
upsFullInputGroup, upsFullOutputGroup,
upsFullAlarmGroup, upsFullTestGroup,
upsFullControlGroup, upsFullConfigGroup }
OBJECT upsAlarmDescr
DESCRIPTION
"Support of all `well known' alarm types is not
required. The well known alarm types which must be
supported are: upsAlarmBatteryBad, upsAlarmOnBattery,
upsAlarmLowBattery, upsAlarmDepletedBattery,
upsAlarmTempBad, upsAlarmInputBad, upsAlarmOnBypass,
upsAlarmBypassBad, upsAlarmOutputOffAsRequested,
upsAlarmUpsOffAsRequested, upsAlarmUpsOutputOff,
upsAlarmUpsSystemOff, upsAlarmGeneralFault,
upsAlarmDiagnosticTestFailed,
upsAlarmCommunicationsLost, upsAlarmShutdownPending,
and upsAlarmTestInProgress."
OBJECT upsTestId
DESCRIPTION
"Support of all `well known' test types is not
required. The well known test types which must be
supported are: upsTestNoTestsInitiated,
upsTestGeneralSystemsTest, and
upsTestQuickBatteryTest."
OBJECT upsOutputSource
SYNTAX INTEGER {
normal(2),
battery(4)
}
DESCRIPTION
"Support of the values other(1), none(2), bypass(4),
booster(6) and reducer(7) is not required."
GROUP upsFullBypassGroup
DESCRIPTION
"The upsFullBypassGroup is only required for UPSs that
have a Bypass present."
OBJECT upsShutdownType
MIN-ACCESS read-only
DESCRIPTION
"Read-write access is not required, i.e., compliant
Case [Page 34]
RFC 1628 UPS MIB May 1994
systems need not support more than one shutdown type."
OBJECT upsAutoRestart
MIN-ACCESS read-only
DESCRIPTION
"Read-write access is not required, i.e., compliant
systems need not support more than one restart type."
OBJECT upsConfigInputVoltage
MIN-ACCESS read-only
DESCRIPTION
"Read-write access is not required."
OBJECT upsConfigInputFreq
MIN-ACCESS read-only
DESCRIPTION
"Read-write access is not required."
OBJECT upsConfigOutputVoltage
MIN-ACCESS read-only
DESCRIPTION
"Read-write access is not required."
OBJECT upsConfigOutputFreq
MIN-ACCESS read-only
DESCRIPTION
"Read-write access is not required."
OBJECT upsConfigLowBattTime
DESCRIPTION
"Implementation of all possible values may be onerous
for some systems. Consequently, not all possible
values must be supported. However, at least two
different manufacturer-selected values must be
supported."
::= { upsCompliances 3 }
--
-- units of conformance
--
-- summary at a glance:
-- subset basic adv
--upsIdentManufacturer x x x
--upsIdentModel x x x
Case [Page 35]
RFC 1628 UPS MIB May 1994
--upsIdentUPSSoftwareVersion x x
--upsIdentAgentSoftwareVersion x x x
--upsIdentName x x x
--upsIdentAttachedDevices x x
--
--upsBatteryStatus x x x notes
--upsSecondsOnBattery x x x
--upsEstimatedMinutesRemaining x
--upsEstimatedChargeRemaining x
--upsBatteryVoltage
--upsBatteryCurrent
--upsBatteryTemperature
--
--upsInputLineBads x x x
--upsInputNumLines x x
--upsInputFrequency x x
--upsInputVoltage x x
--upsInputCurrent
--upsInputTruePower
--
--upsOutputSource x x x notes
--upsOutputFrequency x x
--upsOutputNumLines x x
--upsOutputVoltage x x
--upsOutputCurrent x
--upsOutputPower x
--upsOutputPercentLoad x
--
--
--upsBypassFrequency x x notes
--upsBypassNumLines x x
--upsBypassVoltage x x
--upsBypassCurrent
--upsBypassPower
--
--
--upsAlarmsPresent x x x
--upsAlarmDescr x x x notes
--upsAlarmTime x x x
--
--upsTestId x x notes
--upsTestSpinLock x x
--upsTestResultsSummary x x
--upsTestResultsDetail x x
--upsTestStartTime x x
--upsTestElapsedTime x x
--
--upsShutdownType x x x notes
Case [Page 36]
RFC 1628 UPS MIB May 1994
--upsShutdownAfterDelay x x x
--upsStartupAfterDelay x x
--upsRebootWithDuration x x
--upsAutoRestart x x x notes
--
--upsConfigInputVoltage x x x notes
--upsConfigInputFreq x x x notes
--upsConfigOutputVoltage x x x notes
--upsConfigOutputFreq x x x notes
--upsConfigOutputVA x x x
--upsConfigOutputPower x x x
--upsConfigLowBattTime x x notes
--upsConfigAudibleStatus x x
--upsConfigLowVoltageTransferPoint
--upsConfigHighVoltageTransferPoint
-- units of conformance
upsGroups OBJECT IDENTIFIER ::= { upsConformance 2 }
upsSubsetGroups OBJECT IDENTIFIER ::= { upsGroups 1 }
upsSubsetIdentGroup OBJECT-GROUP
OBJECTS { upsIdentManufacturer, upsIdentModel,
upsIdentAgentSoftwareVersion, upsIdentName,
upsIdentAttachedDevices }
STATUS current
DESCRIPTION
"The upsSubsetIdentGroup defines objects which are
common across all UPSs which meet subset compliance.
Most devices which conform to the upsSubsetIdentGroup
will provide access to these objects via a proxy
agent. If the proxy agent is compatible with multiple
UPS types, configuration of the proxy agent will
require specifying some of these values, either
individually, or as a group (perhaps through a table
lookup mechanism based on the UPS model number)."
::= { upsSubsetGroups 1 }
upsSubsetBatteryGroup OBJECT-GROUP
OBJECTS { upsBatteryStatus, upsSecondsOnBattery }
STATUS current
DESCRIPTION
"The upsSubsetBatteryGroup defines the objects that
are common to battery groups of two-contact UPSs."
::= { upsSubsetGroups 2 }
upsSubsetInputGroup OBJECT-GROUP
Case [Page 37]
RFC 1628 UPS MIB May 1994
OBJECTS { upsInputLineBads }
STATUS current
DESCRIPTION
"The upsSubsetInputGroup defines the objects that are
common to the Input groups of two-contact UPSs."
::= { upsSubsetGroups 3 }
upsSubsetOutputGroup OBJECT-GROUP
OBJECTS { upsOutputSource }
STATUS current
DESCRIPTION
"The upsSubsetOutputGroup defines the objects that are
common to the Output groups of two-contact UPSs."
::= { upsSubsetGroups 4 }
-- { upsSubsetGroups 5 } is reserved for
-- future use (upsSubsetBypassGroup)
upsSubsetAlarmGroup OBJECT-GROUP
OBJECTS { upsAlarmsPresent, upsAlarmDescr, upsAlarmTime }
STATUS current
DESCRIPTION
"The upsSubsetAlarmGroup defines the objects that are
common to the Alarm groups of two-contact UPSs."
::= { upsSubsetGroups 6 }
-- { upsSubsetGroups 7 } is reserved for
-- future use (upsSubsetTestGroup)
upsSubsetControlGroup OBJECT-GROUP
OBJECTS { upsShutdownType, upsShutdownAfterDelay,
upsAutoRestart }
STATUS current
DESCRIPTION
"The upsSubsetControlGroup defines the objects that
are common to the Control groups of two-contact UPSs."
::= { upsSubsetGroups 8 }
upsSubsetConfigGroup OBJECT-GROUP
OBJECTS { upsConfigInputVoltage, upsConfigInputFreq,
upsConfigOutputVoltage, upsConfigOutputFreq,
upsConfigOutputVA, upsConfigOutputPower }
STATUS current
DESCRIPTION
"The upsSubsetConfigGroup defines the objects that are
common to the Config groups of two-contact UPSs."
::= { upsSubsetGroups 9 }
Case [Page 38]
RFC 1628 UPS MIB May 1994
upsBasicGroups OBJECT IDENTIFIER ::= { upsGroups 2 }
upsBasicIdentGroup OBJECT-GROUP
OBJECTS { upsIdentManufacturer, upsIdentModel,
upsIdentUPSSoftwareVersion,
upsIdentAgentSoftwareVersion, upsIdentName }
STATUS current
DESCRIPTION
"The upsBasicIdentGroup defines objects which are
common to the Ident group of compliant UPSs which
support basic functions."
::= { upsBasicGroups 1 }
upsBasicBatteryGroup OBJECT-GROUP
OBJECTS { upsBatteryStatus, upsSecondsOnBattery }
STATUS current
DESCRIPTION
"The upsBasicBatteryGroup defines the objects that are
common to the battery groups of compliant UPSs which
support basic functions."
::= { upsBasicGroups 2 }
upsBasicInputGroup OBJECT-GROUP
OBJECTS { upsInputLineBads, upsInputNumLines,
upsInputFrequency, upsInputVoltage }
STATUS current
DESCRIPTION
"The upsBasicInputGroup defines the objects that are
common to the Input groups of compliant UPSs which
support basic functions."
::= { upsBasicGroups 3 }
upsBasicOutputGroup OBJECT-GROUP
OBJECTS { upsOutputSource, upsOutputFrequency,
upsOutputNumLines, upsOutputVoltage }
STATUS current
DESCRIPTION
"The upsBasicOutputGroup defines the objects that are
common to the Output groups of compliant UPSs which
support basic functions."
::= { upsBasicGroups 4 }
upsBasicBypassGroup OBJECT-GROUP
OBJECTS { upsBypassFrequency, upsBypassNumLines,
upsBypassVoltage }
STATUS current
DESCRIPTION
"The upsBasicBypassGroup defines the objects that are
Case [Page 39]
RFC 1628 UPS MIB May 1994
common to the Bypass groups of compliant UPSs which
support basic functions."
::= { upsBasicGroups 5 }
upsBasicAlarmGroup OBJECT-GROUP
OBJECTS { upsAlarmsPresent, upsAlarmDescr, upsAlarmTime }
STATUS current
DESCRIPTION
"The upsBasicAlarmGroup defines the objects that are
common to the Alarm groups of compliant UPSs which
support basic functions."
::= { upsBasicGroups 6 }
upsBasicTestGroup OBJECT-GROUP
OBJECTS { upsTestId, upsTestSpinLock,
upsTestResultsSummary, upsTestResultsDetail,
upsTestStartTime, upsTestElapsedTime }
STATUS current
DESCRIPTION
"The upsBasicTestGroup defines the objects that are
common to the Test groups of compliant UPSs which
support basic functions."
::= { upsBasicGroups 7 }
upsBasicControlGroup OBJECT-GROUP
OBJECTS { upsShutdownType, upsShutdownAfterDelay,
upsStartupAfterDelay, upsRebootWithDuration,
upsAutoRestart }
STATUS current
DESCRIPTION
"The upsBasicControlGroup defines the objects that are
common to the Control groups of compliant UPSs which
support basic functions."
::= { upsBasicGroups 8 }
upsBasicConfigGroup OBJECT-GROUP
OBJECTS { upsConfigInputVoltage, upsConfigInputFreq,
upsConfigOutputVoltage, upsConfigOutputFreq,
upsConfigOutputVA, upsConfigOutputPower,
upsConfigLowBattTime, upsConfigAudibleStatus }
STATUS current
DESCRIPTION
"The upsBasicConfigGroup defines the objects that are
common to the Config groups of UPSs which support
basic functions."
::= { upsBasicGroups 9 }
Case [Page 40]
RFC 1628 UPS MIB May 1994
upsFullGroups OBJECT IDENTIFIER ::= { upsGroups 3 }
upsFullIdentGroup OBJECT-GROUP
OBJECTS { upsIdentManufacturer, upsIdentModel,
upsIdentUPSSoftwareVersion,
upsIdentAgentSoftwareVersion, upsIdentName,
upsIdentAttachedDevices }
STATUS current
DESCRIPTION
"The upsFullIdentGroup defines objects which are
common to the Ident group of fully compliant UPSs."
::= { upsFullGroups 1 }
upsFullBatteryGroup OBJECT-GROUP
OBJECTS { upsBatteryStatus, upsSecondsOnBattery,
upsEstimatedMinutesRemaining,
upsEstimatedChargeRemaining }
STATUS current
DESCRIPTION
"The upsFullBatteryGroup defines the objects that are
common to the battery groups of fully compliant UPSs."
::= { upsFullGroups 2 }
upsFullInputGroup OBJECT-GROUP
OBJECTS { upsInputLineBads, upsInputNumLines,
upsInputFrequency, upsInputVoltage }
STATUS current
DESCRIPTION
"The upsFullInputGroup defines the objects that are
common to the Input groups of fully compliant UPSs."
::= { upsFullGroups 3 }
upsFullOutputGroup OBJECT-GROUP
OBJECTS { upsOutputSource, upsOutputFrequency,
upsOutputNumLines, upsOutputVoltage,
upsOutputCurrent, upsOutputPower,
upsOutputPercentLoad }
STATUS current
DESCRIPTION
"The upsFullOutputGroup defines the objects that are
common to the Output groups of fully compliant UPSs."
::= { upsFullGroups 4 }
upsFullBypassGroup OBJECT-GROUP
OBJECTS { upsBypassFrequency, upsBypassNumLines,
upsBypassVoltage }
STATUS current
DESCRIPTION
Case [Page 41]
RFC 1628 UPS MIB May 1994
"The upsFullBypassGroup defines the objects that are
common to the Bypass groups of fully compliant UPSs."
::= { upsFullGroups 5 }
upsFullAlarmGroup OBJECT-GROUP
OBJECTS { upsAlarmsPresent, upsAlarmDescr, upsAlarmTime }
STATUS current
DESCRIPTION
"The upsFullAlarmGroup defines the objects that are
common to the Alarm groups of fully compliant UPSs."
::= { upsFullGroups 6 }
upsFullTestGroup OBJECT-GROUP
OBJECTS { upsTestId, upsTestSpinLock,
upsTestResultsSummary, upsTestResultsDetail,
upsTestStartTime, upsTestElapsedTime }
STATUS current
DESCRIPTION
"The upsFullTestGroup defines the objects that are
common to the Test groups of fully compliant UPSs."
::= { upsFullGroups 7 }
upsFullControlGroup OBJECT-GROUP
OBJECTS { upsShutdownType, upsShutdownAfterDelay,
upsStartupAfterDelay, upsRebootWithDuration,
upsAutoRestart }
STATUS current
DESCRIPTION
"The upsFullControlGroup defines the objects that are
common to the Control groups of fully compliant UPSs."
::= { upsFullGroups 8 }
upsFullConfigGroup OBJECT-GROUP
OBJECTS { upsConfigInputVoltage, upsConfigInputFreq,
upsConfigOutputVoltage, upsConfigOutputFreq,
upsConfigOutputVA, upsConfigOutputPower,
upsConfigLowBattTime, upsConfigAudibleStatus }
STATUS current
DESCRIPTION
"The upsFullConfigGroup defines the objects that are
common to the Config groups of fully compliant UPSs."
::= { upsFullGroups 9 }
END
Case [Page 42]
RFC 1628 UPS MIB May 1994
5. Acknowledgements
The UPS MIB represents the combined work of the IETF UPS MIB Working
Group, with particular, substantial authorship contributions from:
Mike Davison
Fibercom, Inc.
Ray Wasson
Consultant
Roger Draper
Liebert Corporation
Ken Key
SNMP Research, Incorporated
Pete Yoest
American Power Conversion
Doug Rademacher
American Power Conversion
Ron Pitt
Network Security Systems, Inc
Terry Zumwalt
International Power Machines
Lawren Markle
Tripp Lite
Bill Elliot
ONEAC
Tom Brennan
Exide Electronics
Brian Young
Best Power Technology
Case [Page 43]
RFC 1628 UPS MIB May 1994
6. References
[1] Case, J., Fedor, M., Schoffstall, M., and J. Davin, "Simple
Network Management Protocol", STD 15, RFC 1157, SNMP Research,
Inc., Performance Systems International, Performance Systems
International, MIT Laboratory for Computer Science, May 1990.
[2] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Protocol
Operations for Version 2 of the Simple Network Management
Protocol (SNMPv2)", RFC 1448, SNMP Research, Inc., Hughes LAN
Systems, Dover Beach Consulting, Inc., Carnegie Mellon
University, April 1993.
[3] McCloghrie, K., and M. Rose, Editors, "Management Information
Base for Network Management of TCP/IP-based internets: MIB-II",
STD 17, RFC 1213, Hughes LAN Systems, Performance Systems
International, March 1991.
[4] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Structure
of Management Information for Version 2 of the Simple Network
Management Protocol (SNMPv2)", RFC 1442, SNMP Research, Inc.,
Hughes LAN Systems, Dover Beach Consulting, Inc., Carnegie Mellon
University, April 1993.
[5] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser,
"Conformance Statements for Version 2 of the Simple Network
Management Protocol (SNMPv2)", RFC 1444, SNMP Research, Inc.,
Hughes LAN Systems, Dover Beach Consulting, Inc., Carnegie Mellon
University, April, 1993.
[6] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Textual
Conventions for Version 2 of the Simple Network Management
Protocol (SNMPv2)", RFC 1443, SNMP Research, Inc., Hughes LAN
Systems, Dover Beach Consulting, Inc., Carnegie Mellon
University, April 1993.
Case [Page 44]
RFC 1628 UPS MIB May 1994
7. Security Considerations
Security issues are not discussed in this memo.
8. Author's Address
Jeffrey D. Case, Ph.D.
SNMP Research, Incorporated
3001 Kimberlin Heights Road
Knoxville, Tennessee 37920
Phone: (615) 573-1434
EMail: case@SNMP.COM
Case [Page 45]
|