telemetry-snmp 0.1.0
Sign up to get free protection for your applications and to get access to all the features.
- checksums.yaml +7 -0
- data/.github/workflows/rspec.yml +44 -0
- data/.github/workflows/rubocop.yml +28 -0
- data/.github/workflows/sourcehawk-scan.yml +20 -0
- data/.gitignore +14 -0
- data/.rspec +4 -0
- data/.rubocop.yml +26 -0
- data/CHANGELOG.md +4 -0
- data/CODE_OF_CONDUCT.md +75 -0
- data/CONTRIBUTING.md +54 -0
- data/Gemfile +10 -0
- data/INDIVIDUAL_CONTRIBUTOR_LICENSE.md +30 -0
- data/LICENSE +201 -0
- data/NOTICE.txt +9 -0
- data/README.md +54 -0
- data/attribution.txt +1 -0
- data/config.ru +15 -0
- data/exe/snmp_collector +55 -0
- data/lib/telemetry/snmp.rb +23 -0
- data/lib/telemetry/snmp/api.rb +55 -0
- data/lib/telemetry/snmp/auth.rb +54 -0
- data/lib/telemetry/snmp/auth/defaults.rb +41 -0
- data/lib/telemetry/snmp/client.rb +104 -0
- data/lib/telemetry/snmp/controllers/device_creds.rb +105 -0
- data/lib/telemetry/snmp/controllers/devices.rb +94 -0
- data/lib/telemetry/snmp/controllers/oid_groups.rb +71 -0
- data/lib/telemetry/snmp/controllers/oids.rb +80 -0
- data/lib/telemetry/snmp/controllers/users.rb +81 -0
- data/lib/telemetry/snmp/controllers/walks.rb +89 -0
- data/lib/telemetry/snmp/data.rb +69 -0
- data/lib/telemetry/snmp/data/default_opts.rb +73 -0
- data/lib/telemetry/snmp/data/migrations/001_device_creds.rb +19 -0
- data/lib/telemetry/snmp/data/migrations/002_create_devices_table.rb +31 -0
- data/lib/telemetry/snmp/data/migrations/003_create_oids_tables.rb +16 -0
- data/lib/telemetry/snmp/data/migrations/004_create_oid_groups.rb +15 -0
- data/lib/telemetry/snmp/data/migrations/005_create_oids_oid_groups.rb +17 -0
- data/lib/telemetry/snmp/data/migrations/006_device_to_oid_group.rb +15 -0
- data/lib/telemetry/snmp/data/migrations/007_create_users.rb +20 -0
- data/lib/telemetry/snmp/data/migrations/008_create_walks_table.rb +14 -0
- data/lib/telemetry/snmp/data/migrations/009_create_tag_name_column.rb +7 -0
- data/lib/telemetry/snmp/data/migrations/010_create_user_audit_table.rb +18 -0
- data/lib/telemetry/snmp/data/models/device.rb +11 -0
- data/lib/telemetry/snmp/data/models/device_cred.rb +11 -0
- data/lib/telemetry/snmp/data/models/oid.rb +10 -0
- data/lib/telemetry/snmp/data/models/oid_group.rb +10 -0
- data/lib/telemetry/snmp/data/models/oid_oid_groups.rb +10 -0
- data/lib/telemetry/snmp/data/models/oid_walk.rb +10 -0
- data/lib/telemetry/snmp/data/models/user.rb +10 -0
- data/lib/telemetry/snmp/data/models/user_audit_log.rb +19 -0
- data/lib/telemetry/snmp/mibs/AGENTX-MIB.txt +527 -0
- data/lib/telemetry/snmp/mibs/AIRPORT-BASESTATION-3-MIB.txt +461 -0
- data/lib/telemetry/snmp/mibs/BRIDGE-MIB.txt +1472 -0
- data/lib/telemetry/snmp/mibs/DISMAN-EVENT-MIB.txt +1882 -0
- data/lib/telemetry/snmp/mibs/DISMAN-SCHEDULE-MIB.txt +699 -0
- data/lib/telemetry/snmp/mibs/DISMAN-SCRIPT-MIB.txt +1764 -0
- data/lib/telemetry/snmp/mibs/EtherLike-MIB.txt +1862 -0
- data/lib/telemetry/snmp/mibs/HCNUM-TC.txt +118 -0
- data/lib/telemetry/snmp/mibs/HOST-RESOURCES-MIB.txt +1540 -0
- data/lib/telemetry/snmp/mibs/HOST-RESOURCES-TYPES.txt +389 -0
- data/lib/telemetry/snmp/mibs/IANA-ADDRESS-FAMILY-NUMBERS-MIB.txt +123 -0
- data/lib/telemetry/snmp/mibs/IANA-LANGUAGE-MIB.txt +123 -0
- data/lib/telemetry/snmp/mibs/IANA-RTPROTO-MIB.txt +91 -0
- data/lib/telemetry/snmp/mibs/IANAifType-MIB.txt +619 -0
- data/lib/telemetry/snmp/mibs/IF-INVERTED-STACK-MIB.txt +149 -0
- data/lib/telemetry/snmp/mibs/IF-MIB.txt +1814 -0
- data/lib/telemetry/snmp/mibs/INET-ADDRESS-MIB.txt +402 -0
- data/lib/telemetry/snmp/mibs/IP-FORWARD-MIB.txt +1277 -0
- data/lib/telemetry/snmp/mibs/IP-MIB.txt +4993 -0
- data/lib/telemetry/snmp/mibs/IPV6-FLOW-LABEL-MIB.txt +58 -0
- data/lib/telemetry/snmp/mibs/IPV6-ICMP-MIB.txt +529 -0
- data/lib/telemetry/snmp/mibs/IPV6-MIB.txt +1443 -0
- data/lib/telemetry/snmp/mibs/IPV6-TC.txt +67 -0
- data/lib/telemetry/snmp/mibs/IPV6-TCP-MIB.txt +211 -0
- data/lib/telemetry/snmp/mibs/IPV6-UDP-MIB.txt +141 -0
- data/lib/telemetry/snmp/mibs/NET-SNMP-AGENT-MIB.txt +554 -0
- data/lib/telemetry/snmp/mibs/NET-SNMP-EXAMPLES-MIB.txt +285 -0
- data/lib/telemetry/snmp/mibs/NET-SNMP-EXTEND-MIB.txt +325 -0
- data/lib/telemetry/snmp/mibs/NET-SNMP-MIB.txt +67 -0
- data/lib/telemetry/snmp/mibs/NET-SNMP-PASS-MIB.txt +124 -0
- data/lib/telemetry/snmp/mibs/NET-SNMP-TC.txt +128 -0
- data/lib/telemetry/snmp/mibs/NET-SNMP-VACM-MIB.txt +154 -0
- data/lib/telemetry/snmp/mibs/NOTIFICATION-LOG-MIB.txt +753 -0
- data/lib/telemetry/snmp/mibs/PAN-COMMON-MIB.md5 +1 -0
- data/lib/telemetry/snmp/mibs/PAN-COMMON-MIB.my +2293 -0
- data/lib/telemetry/snmp/mibs/PAN-ENTITY-EXT-MIB.md5 +1 -0
- data/lib/telemetry/snmp/mibs/PAN-ENTITY-EXT-MIB.my +293 -0
- data/lib/telemetry/snmp/mibs/PAN-GLOBAL-REG-MIB.md5 +1 -0
- data/lib/telemetry/snmp/mibs/PAN-GLOBAL-REG-MIB.my +84 -0
- data/lib/telemetry/snmp/mibs/PAN-GLOBAL-TC-MIB.md5 +1 -0
- data/lib/telemetry/snmp/mibs/PAN-GLOBAL-TC-MIB.my +68 -0
- data/lib/telemetry/snmp/mibs/PAN-LC-MIB.md5 +1 -0
- data/lib/telemetry/snmp/mibs/PAN-LC-MIB.my +204 -0
- data/lib/telemetry/snmp/mibs/PAN-PRODUCT-MIB.md5 +1 -0
- data/lib/telemetry/snmp/mibs/PAN-PRODUCT-MIB.my +305 -0
- data/lib/telemetry/snmp/mibs/PAN-TRAPS.md5 +1 -0
- data/lib/telemetry/snmp/mibs/PAN-TRAPS.my +7809 -0
- data/lib/telemetry/snmp/mibs/RFC-1215.txt +38 -0
- data/lib/telemetry/snmp/mibs/RFC1155-SMI.txt +119 -0
- data/lib/telemetry/snmp/mibs/RFC1213-MIB.txt +2613 -0
- data/lib/telemetry/snmp/mibs/RMON-MIB.txt +3980 -0
- data/lib/telemetry/snmp/mibs/SCTP-MIB.txt +1342 -0
- data/lib/telemetry/snmp/mibs/SMUX-MIB.txt +160 -0
- data/lib/telemetry/snmp/mibs/SNMP-COMMUNITY-MIB.txt +429 -0
- data/lib/telemetry/snmp/mibs/SNMP-FRAMEWORK-MIB.txt +526 -0
- data/lib/telemetry/snmp/mibs/SNMP-MPD-MIB.txt +145 -0
- data/lib/telemetry/snmp/mibs/SNMP-NOTIFICATION-MIB.txt +589 -0
- data/lib/telemetry/snmp/mibs/SNMP-PROXY-MIB.txt +294 -0
- data/lib/telemetry/snmp/mibs/SNMP-TARGET-MIB.txt +660 -0
- data/lib/telemetry/snmp/mibs/SNMP-USER-BASED-SM-MIB.txt +912 -0
- data/lib/telemetry/snmp/mibs/SNMP-USM-AES-MIB.txt +62 -0
- data/lib/telemetry/snmp/mibs/SNMP-USM-DH-OBJECTS-MIB.txt +532 -0
- data/lib/telemetry/snmp/mibs/SNMP-VIEW-BASED-ACM-MIB.txt +830 -0
- data/lib/telemetry/snmp/mibs/SNMPv2-CONF.txt +322 -0
- data/lib/telemetry/snmp/mibs/SNMPv2-MIB.txt +854 -0
- data/lib/telemetry/snmp/mibs/SNMPv2-SMI.txt +344 -0
- data/lib/telemetry/snmp/mibs/SNMPv2-TC.txt +772 -0
- data/lib/telemetry/snmp/mibs/SNMPv2-TM.txt +176 -0
- data/lib/telemetry/snmp/mibs/TCP-MIB.txt +785 -0
- data/lib/telemetry/snmp/mibs/TRANSPORT-ADDRESS-MIB.txt +421 -0
- data/lib/telemetry/snmp/mibs/TUNNEL-MIB.txt +738 -0
- data/lib/telemetry/snmp/mibs/UCD-DEMO-MIB.txt +74 -0
- data/lib/telemetry/snmp/mibs/UCD-DISKIO-MIB.txt +171 -0
- data/lib/telemetry/snmp/mibs/UCD-DLMOD-MIB.txt +124 -0
- data/lib/telemetry/snmp/mibs/UCD-IPFWACC-MIB.txt +327 -0
- data/lib/telemetry/snmp/mibs/UCD-SNMP-MIB.txt +1712 -0
- data/lib/telemetry/snmp/mibs/UDP-MIB.txt +549 -0
- data/lib/telemetry/snmp/publisher.rb +130 -0
- data/lib/telemetry/snmp/version.rb +7 -0
- data/sourcehawk.yml +4 -0
- data/telemetry-snmp.gemspec +48 -0
- metadata +456 -0
@@ -0,0 +1,118 @@
|
|
1
|
+
HCNUM-TC DEFINITIONS ::= BEGIN
|
2
|
+
|
3
|
+
IMPORTS
|
4
|
+
MODULE-IDENTITY, mib-2, Counter64
|
5
|
+
FROM SNMPv2-SMI
|
6
|
+
TEXTUAL-CONVENTION
|
7
|
+
FROM SNMPv2-TC;
|
8
|
+
|
9
|
+
hcnumTC MODULE-IDENTITY
|
10
|
+
LAST-UPDATED "200006080000Z"
|
11
|
+
|
12
|
+
ORGANIZATION "IETF OPS Area"
|
13
|
+
CONTACT-INFO
|
14
|
+
" E-mail: mibs@ops.ietf.org
|
15
|
+
Subscribe: majordomo@psg.com
|
16
|
+
with msg body: subscribe mibs
|
17
|
+
|
18
|
+
Andy Bierman
|
19
|
+
Cisco Systems Inc.
|
20
|
+
170 West Tasman Drive
|
21
|
+
San Jose, CA 95134 USA
|
22
|
+
+1 408-527-3711
|
23
|
+
abierman@cisco.com
|
24
|
+
|
25
|
+
Keith McCloghrie
|
26
|
+
Cisco Systems Inc.
|
27
|
+
170 West Tasman Drive
|
28
|
+
San Jose, CA 95134 USA
|
29
|
+
+1 408-526-5260
|
30
|
+
kzm@cisco.com
|
31
|
+
|
32
|
+
Randy Presuhn
|
33
|
+
BMC Software, Inc.
|
34
|
+
Office 1-3141
|
35
|
+
2141 North First Street
|
36
|
+
San Jose, California 95131 USA
|
37
|
+
+1 408 546-1006
|
38
|
+
rpresuhn@bmc.com"
|
39
|
+
DESCRIPTION
|
40
|
+
"A MIB module containing textual conventions
|
41
|
+
for high capacity data types. This module
|
42
|
+
addresses an immediate need for data types not directly
|
43
|
+
supported in the SMIv2. This short-term solution
|
44
|
+
is meant to be deprecated as a long-term solution
|
45
|
+
is deployed."
|
46
|
+
REVISION "200006080000Z"
|
47
|
+
DESCRIPTION
|
48
|
+
"Initial Version of the High Capacity Numbers
|
49
|
+
MIB module, published as RFC 2856."
|
50
|
+
::= { mib-2 78 }
|
51
|
+
|
52
|
+
CounterBasedGauge64 ::= TEXTUAL-CONVENTION
|
53
|
+
STATUS current
|
54
|
+
DESCRIPTION
|
55
|
+
"The CounterBasedGauge64 type represents a non-negative
|
56
|
+
integer, which may increase or decrease, but shall never
|
57
|
+
exceed a maximum value, nor fall below a minimum value. The
|
58
|
+
maximum value can not be greater than 2^64-1
|
59
|
+
(18446744073709551615 decimal), and the minimum value can
|
60
|
+
|
61
|
+
not be smaller than 0. The value of a CounterBasedGauge64
|
62
|
+
has its maximum value whenever the information being modeled
|
63
|
+
is greater than or equal to its maximum value, and has its
|
64
|
+
minimum value whenever the information being modeled is
|
65
|
+
smaller than or equal to its minimum value. If the
|
66
|
+
information being modeled subsequently decreases below
|
67
|
+
(increases above) the maximum (minimum) value, the
|
68
|
+
CounterBasedGauge64 also decreases (increases).
|
69
|
+
|
70
|
+
Note that this TC is not strictly supported in SMIv2,
|
71
|
+
because the 'always increasing' and 'counter wrap' semantics
|
72
|
+
associated with the Counter64 base type are not preserved.
|
73
|
+
It is possible that management applications which rely
|
74
|
+
solely upon the (Counter64) ASN.1 tag to determine object
|
75
|
+
semantics will mistakenly operate upon objects of this type
|
76
|
+
as they would for Counter64 objects.
|
77
|
+
|
78
|
+
This textual convention represents a limited and short-term
|
79
|
+
solution, and may be deprecated as a long term solution is
|
80
|
+
defined and deployed to replace it."
|
81
|
+
SYNTAX Counter64
|
82
|
+
|
83
|
+
ZeroBasedCounter64 ::= TEXTUAL-CONVENTION
|
84
|
+
STATUS current
|
85
|
+
DESCRIPTION
|
86
|
+
"This TC describes an object which counts events with the
|
87
|
+
following semantics: objects of this type will be set to
|
88
|
+
zero(0) on creation and will thereafter count appropriate
|
89
|
+
events, wrapping back to zero(0) when the value 2^64 is
|
90
|
+
reached.
|
91
|
+
|
92
|
+
Provided that an application discovers the new object within
|
93
|
+
the minimum time to wrap it can use the initial value as a
|
94
|
+
delta since it last polled the table of which this object is
|
95
|
+
part. It is important for a management station to be aware
|
96
|
+
of this minimum time and the actual time between polls, and
|
97
|
+
to discard data if the actual time is too long or there is
|
98
|
+
no defined minimum time.
|
99
|
+
|
100
|
+
Typically this TC is used in tables where the INDEX space is
|
101
|
+
constantly changing and/or the TimeFilter mechanism is in
|
102
|
+
use.
|
103
|
+
|
104
|
+
Note that this textual convention does not retain all the
|
105
|
+
semantics of the Counter64 base type. Specifically, a
|
106
|
+
Counter64 has an arbitrary initial value, but objects
|
107
|
+
defined with this TC are required to start at the value
|
108
|
+
|
109
|
+
zero. This behavior is not likely to have any adverse
|
110
|
+
effects on management applications which are expecting
|
111
|
+
Counter64 semantics.
|
112
|
+
|
113
|
+
This textual convention represents a limited and short-term
|
114
|
+
solution, and may be deprecated as a long term solution is
|
115
|
+
defined and deployed to replace it."
|
116
|
+
SYNTAX Counter64
|
117
|
+
|
118
|
+
END
|
@@ -0,0 +1,1540 @@
|
|
1
|
+
HOST-RESOURCES-MIB DEFINITIONS ::= BEGIN
|
2
|
+
|
3
|
+
IMPORTS
|
4
|
+
MODULE-IDENTITY, OBJECT-TYPE, mib-2,
|
5
|
+
Integer32, Counter32, Gauge32, TimeTicks FROM SNMPv2-SMI
|
6
|
+
|
7
|
+
TEXTUAL-CONVENTION, DisplayString,
|
8
|
+
TruthValue, DateAndTime, AutonomousType FROM SNMPv2-TC
|
9
|
+
|
10
|
+
MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF
|
11
|
+
|
12
|
+
InterfaceIndexOrZero FROM IF-MIB;
|
13
|
+
|
14
|
+
hostResourcesMibModule MODULE-IDENTITY
|
15
|
+
LAST-UPDATED "200003060000Z" -- 6 March 2000
|
16
|
+
ORGANIZATION "IETF Host Resources MIB Working Group"
|
17
|
+
CONTACT-INFO
|
18
|
+
"Steve Waldbusser
|
19
|
+
Postal: Lucent Technologies, Inc.
|
20
|
+
1213 Innsbruck Dr.
|
21
|
+
Sunnyvale, CA 94089
|
22
|
+
USA
|
23
|
+
Phone: 650-318-1251
|
24
|
+
Fax: 650-318-1633
|
25
|
+
Email: waldbusser@lucent.com
|
26
|
+
|
27
|
+
In addition, the Host Resources MIB mailing list is
|
28
|
+
dedicated to discussion of this MIB. To join the
|
29
|
+
mailing list, send a request message to
|
30
|
+
hostmib-request@andrew.cmu.edu. The mailing list
|
31
|
+
address is hostmib@andrew.cmu.edu."
|
32
|
+
DESCRIPTION
|
33
|
+
"This MIB is for use in managing host systems. The term
|
34
|
+
`host' is construed to mean any computer that communicates
|
35
|
+
with other similar computers attached to the internet and
|
36
|
+
that is directly used by one or more human beings. Although
|
37
|
+
this MIB does not necessarily apply to devices whose primary
|
38
|
+
function is communications services (e.g., terminal servers,
|
39
|
+
routers, bridges, monitoring equipment), such relevance is
|
40
|
+
not explicitly precluded. This MIB instruments attributes
|
41
|
+
common to all internet hosts including, for example, both
|
42
|
+
personal computers and systems that run variants of Unix."
|
43
|
+
|
44
|
+
REVISION "200003060000Z" -- 6 March 2000
|
45
|
+
DESCRIPTION
|
46
|
+
"Clarifications and bug fixes based on implementation
|
47
|
+
experience. This revision was also reformatted in the SMIv2
|
48
|
+
format. The revisions made were:
|
49
|
+
|
50
|
+
New RFC document standards:
|
51
|
+
Added Copyright notice, updated introduction to SNMP
|
52
|
+
Framework, updated references section, added reference to
|
53
|
+
RFC 2119, and added a meaningful Security Considerations
|
54
|
+
section.
|
55
|
+
|
56
|
+
New IANA considerations section for registration of new types
|
57
|
+
|
58
|
+
Conversion to new SMIv2 syntax for the following types and
|
59
|
+
macros:
|
60
|
+
Counter32, Integer32, Gauge32, MODULE-IDENTITY,
|
61
|
+
OBJECT-TYPE, TEXTUAL-CONVENTION, OBJECT-IDENTITY,
|
62
|
+
MODULE-COMPLIANCE, OBJECT-GROUP
|
63
|
+
|
64
|
+
Used new Textual Conventions:
|
65
|
+
TruthValue, DateAndTime, AutonomousType,
|
66
|
+
InterfaceIndexOrZero
|
67
|
+
|
68
|
+
Fixed typo in hrPrinterStatus.
|
69
|
+
|
70
|
+
Added missing error bits to hrPrinterDetectedErrorState and
|
71
|
+
clarified confusion resulting from suggested mappings to
|
72
|
+
hrPrinterStatus.
|
73
|
+
|
74
|
+
Clarified that size of objects of type
|
75
|
+
InternationalDisplayString is number of octets, not number
|
76
|
+
of encoded symbols.
|
77
|
+
|
78
|
+
Clarified the use of the following objects based on
|
79
|
+
implementation experience:
|
80
|
+
hrSystemInitialLoadDevice, hrSystemInitialLoadParameters,
|
81
|
+
hrMemorySize, hrStorageSize, hrStorageAllocationFailures,
|
82
|
+
hrDeviceErrors, hrProcessorLoad, hrNetworkIfIndex,
|
83
|
+
hrDiskStorageCapacity, hrSWRunStatus, hrSWRunPerfCPU,
|
84
|
+
and hrSWInstalledDate.
|
85
|
+
|
86
|
+
Clarified implementation technique for hrSWInstalledTable.
|
87
|
+
|
88
|
+
Used new AUGMENTS clause for hrSWRunPerfTable.
|
89
|
+
|
90
|
+
Added Internationalization Considerations section.
|
91
|
+
|
92
|
+
This revision published as RFC2790."
|
93
|
+
|
94
|
+
REVISION "9910202200Z" -- 20 October, 1999
|
95
|
+
DESCRIPTION
|
96
|
+
"The original version of this MIB, published as
|
97
|
+
RFC1514."
|
98
|
+
::= { hrMIBAdminInfo 1 }
|
99
|
+
|
100
|
+
host OBJECT IDENTIFIER ::= { mib-2 25 }
|
101
|
+
|
102
|
+
hrSystem OBJECT IDENTIFIER ::= { host 1 }
|
103
|
+
hrStorage OBJECT IDENTIFIER ::= { host 2 }
|
104
|
+
hrDevice OBJECT IDENTIFIER ::= { host 3 }
|
105
|
+
hrSWRun OBJECT IDENTIFIER ::= { host 4 }
|
106
|
+
hrSWRunPerf OBJECT IDENTIFIER ::= { host 5 }
|
107
|
+
hrSWInstalled OBJECT IDENTIFIER ::= { host 6 }
|
108
|
+
hrMIBAdminInfo OBJECT IDENTIFIER ::= { host 7 }
|
109
|
+
|
110
|
+
-- textual conventions
|
111
|
+
|
112
|
+
KBytes ::= TEXTUAL-CONVENTION
|
113
|
+
STATUS current
|
114
|
+
DESCRIPTION
|
115
|
+
"Storage size, expressed in units of 1024 bytes."
|
116
|
+
SYNTAX Integer32 (0..2147483647)
|
117
|
+
|
118
|
+
ProductID ::= TEXTUAL-CONVENTION
|
119
|
+
STATUS current
|
120
|
+
DESCRIPTION
|
121
|
+
"This textual convention is intended to identify the
|
122
|
+
|
123
|
+
manufacturer, model, and version of a specific
|
124
|
+
hardware or software product. It is suggested that
|
125
|
+
these OBJECT IDENTIFIERs are allocated such that all
|
126
|
+
products from a particular manufacturer are registered
|
127
|
+
under a subtree distinct to that manufacturer. In
|
128
|
+
addition, all versions of a product should be
|
129
|
+
registered under a subtree distinct to that product.
|
130
|
+
With this strategy, a management station may uniquely
|
131
|
+
determine the manufacturer and/or model of a product
|
132
|
+
whose productID is unknown to the management station.
|
133
|
+
Objects of this type may be useful for inventory
|
134
|
+
purposes or for automatically detecting
|
135
|
+
incompatibilities or version mismatches between
|
136
|
+
various hardware and software components on a system.
|
137
|
+
|
138
|
+
For example, the product ID for the ACME 4860 66MHz
|
139
|
+
clock doubled processor might be:
|
140
|
+
enterprises.acme.acmeProcessors.a4860DX2.MHz66
|
141
|
+
|
142
|
+
A software product might be registered as:
|
143
|
+
enterprises.acme.acmeOperatingSystems.acmeDOS.six(6).one(1)
|
144
|
+
"
|
145
|
+
SYNTAX OBJECT IDENTIFIER
|
146
|
+
|
147
|
+
-- unknownProduct will be used for any unknown ProductID
|
148
|
+
-- unknownProduct OBJECT IDENTIFIER ::= { 0 0 }
|
149
|
+
|
150
|
+
InternationalDisplayString ::= TEXTUAL-CONVENTION
|
151
|
+
STATUS current
|
152
|
+
DESCRIPTION
|
153
|
+
"This data type is used to model textual information
|
154
|
+
in some character set. A network management station
|
155
|
+
should use a local algorithm to determine which
|
156
|
+
character set is in use and how it should be
|
157
|
+
displayed. Note that this character set may be
|
158
|
+
encoded with more than one octet per symbol, but will
|
159
|
+
most often be NVT ASCII. When a size clause is
|
160
|
+
specified for an object of this type, the size refers
|
161
|
+
to the length in octets, not the number of symbols."
|
162
|
+
SYNTAX OCTET STRING
|
163
|
+
|
164
|
+
-- The Host Resources System Group
|
165
|
+
|
166
|
+
hrSystemUptime OBJECT-TYPE
|
167
|
+
SYNTAX TimeTicks
|
168
|
+
MAX-ACCESS read-only
|
169
|
+
STATUS current
|
170
|
+
DESCRIPTION
|
171
|
+
"The amount of time since this host was last
|
172
|
+
initialized. Note that this is different from
|
173
|
+
sysUpTime in the SNMPv2-MIB [RFC1907] because
|
174
|
+
sysUpTime is the uptime of the network management
|
175
|
+
portion of the system."
|
176
|
+
::= { hrSystem 1 }
|
177
|
+
|
178
|
+
hrSystemDate OBJECT-TYPE
|
179
|
+
SYNTAX DateAndTime
|
180
|
+
MAX-ACCESS read-write
|
181
|
+
STATUS current
|
182
|
+
DESCRIPTION
|
183
|
+
"The host's notion of the local date and time of day."
|
184
|
+
::= { hrSystem 2 }
|
185
|
+
|
186
|
+
hrSystemInitialLoadDevice OBJECT-TYPE
|
187
|
+
SYNTAX Integer32 (1..2147483647)
|
188
|
+
MAX-ACCESS read-write
|
189
|
+
STATUS current
|
190
|
+
DESCRIPTION
|
191
|
+
"The index of the hrDeviceEntry for the device from
|
192
|
+
which this host is configured to load its initial
|
193
|
+
operating system configuration (i.e., which operating
|
194
|
+
system code and/or boot parameters).
|
195
|
+
|
196
|
+
Note that writing to this object just changes the
|
197
|
+
configuration that will be used the next time the
|
198
|
+
operating system is loaded and does not actually cause
|
199
|
+
the reload to occur."
|
200
|
+
::= { hrSystem 3 }
|
201
|
+
|
202
|
+
hrSystemInitialLoadParameters OBJECT-TYPE
|
203
|
+
SYNTAX InternationalDisplayString (SIZE (0..128))
|
204
|
+
MAX-ACCESS read-write
|
205
|
+
STATUS current
|
206
|
+
DESCRIPTION
|
207
|
+
"This object contains the parameters (e.g. a pathname
|
208
|
+
and parameter) supplied to the load device when
|
209
|
+
requesting the initial operating system configuration
|
210
|
+
from that device.
|
211
|
+
|
212
|
+
Note that writing to this object just changes the
|
213
|
+
configuration that will be used the next time the
|
214
|
+
operating system is loaded and does not actually cause
|
215
|
+
the reload to occur."
|
216
|
+
::= { hrSystem 4 }
|
217
|
+
|
218
|
+
hrSystemNumUsers OBJECT-TYPE
|
219
|
+
SYNTAX Gauge32
|
220
|
+
MAX-ACCESS read-only
|
221
|
+
STATUS current
|
222
|
+
DESCRIPTION
|
223
|
+
"The number of user sessions for which this host is
|
224
|
+
storing state information. A session is a collection
|
225
|
+
of processes requiring a single act of user
|
226
|
+
authentication and possibly subject to collective job
|
227
|
+
control."
|
228
|
+
::= { hrSystem 5 }
|
229
|
+
|
230
|
+
hrSystemProcesses OBJECT-TYPE
|
231
|
+
SYNTAX Gauge32
|
232
|
+
MAX-ACCESS read-only
|
233
|
+
STATUS current
|
234
|
+
DESCRIPTION
|
235
|
+
"The number of process contexts currently loaded or
|
236
|
+
running on this system."
|
237
|
+
::= { hrSystem 6 }
|
238
|
+
|
239
|
+
hrSystemMaxProcesses OBJECT-TYPE
|
240
|
+
SYNTAX Integer32 (0..2147483647)
|
241
|
+
MAX-ACCESS read-only
|
242
|
+
STATUS current
|
243
|
+
DESCRIPTION
|
244
|
+
"The maximum number of process contexts this system
|
245
|
+
can support. If there is no fixed maximum, the value
|
246
|
+
should be zero. On systems that have a fixed maximum,
|
247
|
+
this object can help diagnose failures that occur when
|
248
|
+
this maximum is reached."
|
249
|
+
::= { hrSystem 7 }
|
250
|
+
|
251
|
+
-- The Host Resources Storage Group
|
252
|
+
|
253
|
+
-- Registration point for storage types, for use with hrStorageType.
|
254
|
+
-- These are defined in the HOST-RESOURCES-TYPES module.
|
255
|
+
hrStorageTypes OBJECT IDENTIFIER ::= { hrStorage 1 }
|
256
|
+
|
257
|
+
hrMemorySize OBJECT-TYPE
|
258
|
+
SYNTAX KBytes
|
259
|
+
UNITS "KBytes"
|
260
|
+
MAX-ACCESS read-only
|
261
|
+
STATUS current
|
262
|
+
DESCRIPTION
|
263
|
+
"The amount of physical read-write main memory,
|
264
|
+
typically RAM, contained by the host."
|
265
|
+
::= { hrStorage 2 }
|
266
|
+
|
267
|
+
hrStorageTable OBJECT-TYPE
|
268
|
+
SYNTAX SEQUENCE OF HrStorageEntry
|
269
|
+
MAX-ACCESS not-accessible
|
270
|
+
STATUS current
|
271
|
+
DESCRIPTION
|
272
|
+
"The (conceptual) table of logical storage areas on
|
273
|
+
the host.
|
274
|
+
|
275
|
+
An entry shall be placed in the storage table for each
|
276
|
+
logical area of storage that is allocated and has
|
277
|
+
fixed resource limits. The amount of storage
|
278
|
+
represented in an entity is the amount actually usable
|
279
|
+
by the requesting entity, and excludes loss due to
|
280
|
+
formatting or file system reference information.
|
281
|
+
|
282
|
+
These entries are associated with logical storage
|
283
|
+
areas, as might be seen by an application, rather than
|
284
|
+
physical storage entities which are typically seen by
|
285
|
+
an operating system. Storage such as tapes and
|
286
|
+
floppies without file systems on them are typically
|
287
|
+
not allocated in chunks by the operating system to
|
288
|
+
requesting applications, and therefore shouldn't
|
289
|
+
appear in this table. Examples of valid storage for
|
290
|
+
this table include disk partitions, file systems, ram
|
291
|
+
(for some architectures this is further segmented into
|
292
|
+
regular memory, extended memory, and so on), backing
|
293
|
+
store for virtual memory (`swap space').
|
294
|
+
|
295
|
+
This table is intended to be a useful diagnostic for
|
296
|
+
`out of memory' and `out of buffers' types of
|
297
|
+
failures. In addition, it can be a useful performance
|
298
|
+
monitoring tool for tracking memory, disk, or buffer
|
299
|
+
usage."
|
300
|
+
::= { hrStorage 3 }
|
301
|
+
|
302
|
+
hrStorageEntry OBJECT-TYPE
|
303
|
+
SYNTAX HrStorageEntry
|
304
|
+
MAX-ACCESS not-accessible
|
305
|
+
STATUS current
|
306
|
+
DESCRIPTION
|
307
|
+
"A (conceptual) entry for one logical storage area on
|
308
|
+
the host. As an example, an instance of the
|
309
|
+
hrStorageType object might be named hrStorageType.3"
|
310
|
+
INDEX { hrStorageIndex }
|
311
|
+
::= { hrStorageTable 1 }
|
312
|
+
|
313
|
+
HrStorageEntry ::= SEQUENCE {
|
314
|
+
hrStorageIndex Integer32,
|
315
|
+
hrStorageType AutonomousType,
|
316
|
+
hrStorageDescr DisplayString,
|
317
|
+
hrStorageAllocationUnits Integer32,
|
318
|
+
hrStorageSize Integer32,
|
319
|
+
hrStorageUsed Integer32,
|
320
|
+
hrStorageAllocationFailures Counter32
|
321
|
+
}
|
322
|
+
|
323
|
+
hrStorageIndex OBJECT-TYPE
|
324
|
+
SYNTAX Integer32 (1..2147483647)
|
325
|
+
MAX-ACCESS read-only
|
326
|
+
STATUS current
|
327
|
+
DESCRIPTION
|
328
|
+
"A unique value for each logical storage area
|
329
|
+
contained by the host."
|
330
|
+
::= { hrStorageEntry 1 }
|
331
|
+
|
332
|
+
hrStorageType OBJECT-TYPE
|
333
|
+
SYNTAX AutonomousType
|
334
|
+
MAX-ACCESS read-only
|
335
|
+
STATUS current
|
336
|
+
DESCRIPTION
|
337
|
+
"The type of storage represented by this entry."
|
338
|
+
::= { hrStorageEntry 2 }
|
339
|
+
|
340
|
+
hrStorageDescr OBJECT-TYPE
|
341
|
+
SYNTAX DisplayString
|
342
|
+
MAX-ACCESS read-only
|
343
|
+
STATUS current
|
344
|
+
DESCRIPTION
|
345
|
+
"A description of the type and instance of the storage
|
346
|
+
described by this entry."
|
347
|
+
::= { hrStorageEntry 3 }
|
348
|
+
|
349
|
+
hrStorageAllocationUnits OBJECT-TYPE
|
350
|
+
SYNTAX Integer32 (1..2147483647)
|
351
|
+
UNITS "Bytes"
|
352
|
+
MAX-ACCESS read-only
|
353
|
+
STATUS current
|
354
|
+
DESCRIPTION
|
355
|
+
"The size, in bytes, of the data objects allocated
|
356
|
+
from this pool. If this entry is monitoring sectors,
|
357
|
+
blocks, buffers, or packets, for example, this number
|
358
|
+
will commonly be greater than one. Otherwise this
|
359
|
+
number will typically be one."
|
360
|
+
::= { hrStorageEntry 4 }
|
361
|
+
|
362
|
+
hrStorageSize OBJECT-TYPE
|
363
|
+
SYNTAX Integer32 (0..2147483647)
|
364
|
+
MAX-ACCESS read-write
|
365
|
+
STATUS current
|
366
|
+
DESCRIPTION
|
367
|
+
"The size of the storage represented by this entry, in
|
368
|
+
units of hrStorageAllocationUnits. This object is
|
369
|
+
writable to allow remote configuration of the size of
|
370
|
+
the storage area in those cases where such an
|
371
|
+
operation makes sense and is possible on the
|
372
|
+
underlying system. For example, the amount of main
|
373
|
+
memory allocated to a buffer pool might be modified or
|
374
|
+
the amount of disk space allocated to virtual memory
|
375
|
+
might be modified."
|
376
|
+
::= { hrStorageEntry 5 }
|
377
|
+
|
378
|
+
hrStorageUsed OBJECT-TYPE
|
379
|
+
SYNTAX Integer32 (0..2147483647)
|
380
|
+
MAX-ACCESS read-only
|
381
|
+
STATUS current
|
382
|
+
DESCRIPTION
|
383
|
+
"The amount of the storage represented by this entry
|
384
|
+
that is allocated, in units of
|
385
|
+
hrStorageAllocationUnits."
|
386
|
+
::= { hrStorageEntry 6 }
|
387
|
+
|
388
|
+
hrStorageAllocationFailures OBJECT-TYPE
|
389
|
+
SYNTAX Counter32
|
390
|
+
MAX-ACCESS read-only
|
391
|
+
STATUS current
|
392
|
+
DESCRIPTION
|
393
|
+
"The number of requests for storage represented by
|
394
|
+
this entry that could not be honored due to not enough
|
395
|
+
storage. It should be noted that as this object has a
|
396
|
+
SYNTAX of Counter32, that it does not have a defined
|
397
|
+
initial value. However, it is recommended that this
|
398
|
+
object be initialized to zero, even though management
|
399
|
+
stations must not depend on such an initialization."
|
400
|
+
::= { hrStorageEntry 7 }
|
401
|
+
|
402
|
+
-- The Host Resources Device Group
|
403
|
+
--
|
404
|
+
-- The device group is useful for identifying and diagnosing the
|
405
|
+
-- devices on a system. The hrDeviceTable contains common
|
406
|
+
-- information for any type of device. In addition, some devices
|
407
|
+
-- have device-specific tables for more detailed information. More
|
408
|
+
-- such tables may be defined in the future for other device types.
|
409
|
+
|
410
|
+
-- Registration point for device types, for use with hrDeviceType.
|
411
|
+
|
412
|
+
-- These are defined in the HOST-RESOURCES-TYPES module.
|
413
|
+
hrDeviceTypes OBJECT IDENTIFIER ::= { hrDevice 1 }
|
414
|
+
|
415
|
+
hrDeviceTable OBJECT-TYPE
|
416
|
+
SYNTAX SEQUENCE OF HrDeviceEntry
|
417
|
+
MAX-ACCESS not-accessible
|
418
|
+
STATUS current
|
419
|
+
DESCRIPTION
|
420
|
+
"The (conceptual) table of devices contained by the
|
421
|
+
host."
|
422
|
+
::= { hrDevice 2 }
|
423
|
+
|
424
|
+
hrDeviceEntry OBJECT-TYPE
|
425
|
+
SYNTAX HrDeviceEntry
|
426
|
+
MAX-ACCESS not-accessible
|
427
|
+
STATUS current
|
428
|
+
DESCRIPTION
|
429
|
+
"A (conceptual) entry for one device contained by the
|
430
|
+
host. As an example, an instance of the hrDeviceType
|
431
|
+
object might be named hrDeviceType.3"
|
432
|
+
INDEX { hrDeviceIndex }
|
433
|
+
::= { hrDeviceTable 1 }
|
434
|
+
|
435
|
+
HrDeviceEntry ::= SEQUENCE {
|
436
|
+
hrDeviceIndex Integer32,
|
437
|
+
hrDeviceType AutonomousType,
|
438
|
+
hrDeviceDescr DisplayString,
|
439
|
+
hrDeviceID ProductID,
|
440
|
+
hrDeviceStatus INTEGER,
|
441
|
+
hrDeviceErrors Counter32
|
442
|
+
}
|
443
|
+
|
444
|
+
hrDeviceIndex OBJECT-TYPE
|
445
|
+
SYNTAX Integer32 (1..2147483647)
|
446
|
+
MAX-ACCESS read-only
|
447
|
+
STATUS current
|
448
|
+
DESCRIPTION
|
449
|
+
"A unique value for each device contained by the host.
|
450
|
+
The value for each device must remain constant at
|
451
|
+
least from one re-initialization of the agent to the
|
452
|
+
next re-initialization."
|
453
|
+
::= { hrDeviceEntry 1 }
|
454
|
+
|
455
|
+
hrDeviceType OBJECT-TYPE
|
456
|
+
SYNTAX AutonomousType
|
457
|
+
MAX-ACCESS read-only
|
458
|
+
STATUS current
|
459
|
+
DESCRIPTION
|
460
|
+
"An indication of the type of device.
|
461
|
+
|
462
|
+
If this value is
|
463
|
+
`hrDeviceProcessor { hrDeviceTypes 3 }' then an entry
|
464
|
+
exists in the hrProcessorTable which corresponds to
|
465
|
+
this device.
|
466
|
+
|
467
|
+
If this value is
|
468
|
+
`hrDeviceNetwork { hrDeviceTypes 4 }', then an entry
|
469
|
+
exists in the hrNetworkTable which corresponds to this
|
470
|
+
device.
|
471
|
+
|
472
|
+
If this value is
|
473
|
+
`hrDevicePrinter { hrDeviceTypes 5 }', then an entry
|
474
|
+
exists in the hrPrinterTable which corresponds to this
|
475
|
+
device.
|
476
|
+
|
477
|
+
If this value is
|
478
|
+
`hrDeviceDiskStorage { hrDeviceTypes 6 }', then an
|
479
|
+
entry exists in the hrDiskStorageTable which
|
480
|
+
corresponds to this device."
|
481
|
+
::= { hrDeviceEntry 2 }
|
482
|
+
|
483
|
+
hrDeviceDescr OBJECT-TYPE
|
484
|
+
SYNTAX DisplayString (SIZE (0..64))
|
485
|
+
MAX-ACCESS read-only
|
486
|
+
STATUS current
|
487
|
+
DESCRIPTION
|
488
|
+
"A textual description of this device, including the
|
489
|
+
device's manufacturer and revision, and optionally,
|
490
|
+
its serial number."
|
491
|
+
::= { hrDeviceEntry 3 }
|
492
|
+
|
493
|
+
hrDeviceID OBJECT-TYPE
|
494
|
+
SYNTAX ProductID
|
495
|
+
MAX-ACCESS read-only
|
496
|
+
STATUS current
|
497
|
+
DESCRIPTION
|
498
|
+
"The product ID for this device."
|
499
|
+
::= { hrDeviceEntry 4 }
|
500
|
+
|
501
|
+
hrDeviceStatus OBJECT-TYPE
|
502
|
+
SYNTAX INTEGER {
|
503
|
+
unknown(1),
|
504
|
+
running(2),
|
505
|
+
warning(3),
|
506
|
+
testing(4),
|
507
|
+
down(5)
|
508
|
+
|
509
|
+
}
|
510
|
+
MAX-ACCESS read-only
|
511
|
+
STATUS current
|
512
|
+
DESCRIPTION
|
513
|
+
"The current operational state of the device described
|
514
|
+
by this row of the table. A value unknown(1)
|
515
|
+
indicates that the current state of the device is
|
516
|
+
unknown. running(2) indicates that the device is up
|
517
|
+
and running and that no unusual error conditions are
|
518
|
+
known. The warning(3) state indicates that agent has
|
519
|
+
been informed of an unusual error condition by the
|
520
|
+
operational software (e.g., a disk device driver) but
|
521
|
+
that the device is still 'operational'. An example
|
522
|
+
would be a high number of soft errors on a disk. A
|
523
|
+
value of testing(4), indicates that the device is not
|
524
|
+
available for use because it is in the testing state.
|
525
|
+
The state of down(5) is used only when the agent has
|
526
|
+
been informed that the device is not available for any
|
527
|
+
use."
|
528
|
+
::= { hrDeviceEntry 5 }
|
529
|
+
|
530
|
+
hrDeviceErrors OBJECT-TYPE
|
531
|
+
SYNTAX Counter32
|
532
|
+
MAX-ACCESS read-only
|
533
|
+
STATUS current
|
534
|
+
DESCRIPTION
|
535
|
+
"The number of errors detected on this device. It
|
536
|
+
should be noted that as this object has a SYNTAX of
|
537
|
+
Counter32, that it does not have a defined initial
|
538
|
+
value. However, it is recommended that this object be
|
539
|
+
initialized to zero, even though management stations
|
540
|
+
must not depend on such an initialization."
|
541
|
+
::= { hrDeviceEntry 6 }
|
542
|
+
|
543
|
+
hrProcessorTable OBJECT-TYPE
|
544
|
+
SYNTAX SEQUENCE OF HrProcessorEntry
|
545
|
+
MAX-ACCESS not-accessible
|
546
|
+
STATUS current
|
547
|
+
DESCRIPTION
|
548
|
+
"The (conceptual) table of processors contained by the
|
549
|
+
host.
|
550
|
+
|
551
|
+
Note that this table is potentially sparse: a
|
552
|
+
(conceptual) entry exists only if the correspondent
|
553
|
+
value of the hrDeviceType object is
|
554
|
+
`hrDeviceProcessor'."
|
555
|
+
::= { hrDevice 3 }
|
556
|
+
|
557
|
+
hrProcessorEntry OBJECT-TYPE
|
558
|
+
SYNTAX HrProcessorEntry
|
559
|
+
MAX-ACCESS not-accessible
|
560
|
+
STATUS current
|
561
|
+
DESCRIPTION
|
562
|
+
"A (conceptual) entry for one processor contained by
|
563
|
+
the host. The hrDeviceIndex in the index represents
|
564
|
+
the entry in the hrDeviceTable that corresponds to the
|
565
|
+
hrProcessorEntry.
|
566
|
+
|
567
|
+
As an example of how objects in this table are named,
|
568
|
+
an instance of the hrProcessorFrwID object might be
|
569
|
+
named hrProcessorFrwID.3"
|
570
|
+
INDEX { hrDeviceIndex }
|
571
|
+
::= { hrProcessorTable 1 }
|
572
|
+
|
573
|
+
HrProcessorEntry ::= SEQUENCE {
|
574
|
+
hrProcessorFrwID ProductID,
|
575
|
+
hrProcessorLoad Integer32
|
576
|
+
}
|
577
|
+
|
578
|
+
hrProcessorFrwID OBJECT-TYPE
|
579
|
+
SYNTAX ProductID
|
580
|
+
MAX-ACCESS read-only
|
581
|
+
STATUS current
|
582
|
+
DESCRIPTION
|
583
|
+
"The product ID of the firmware associated with the
|
584
|
+
processor."
|
585
|
+
::= { hrProcessorEntry 1 }
|
586
|
+
|
587
|
+
hrProcessorLoad OBJECT-TYPE
|
588
|
+
SYNTAX Integer32 (0..100)
|
589
|
+
MAX-ACCESS read-only
|
590
|
+
STATUS current
|
591
|
+
DESCRIPTION
|
592
|
+
"The average, over the last minute, of the percentage
|
593
|
+
of time that this processor was not idle.
|
594
|
+
Implementations may approximate this one minute
|
595
|
+
smoothing period if necessary."
|
596
|
+
::= { hrProcessorEntry 2 }
|
597
|
+
|
598
|
+
hrNetworkTable OBJECT-TYPE
|
599
|
+
SYNTAX SEQUENCE OF HrNetworkEntry
|
600
|
+
MAX-ACCESS not-accessible
|
601
|
+
STATUS current
|
602
|
+
DESCRIPTION
|
603
|
+
"The (conceptual) table of network devices contained
|
604
|
+
by the host.
|
605
|
+
|
606
|
+
Note that this table is potentially sparse: a
|
607
|
+
(conceptual) entry exists only if the correspondent
|
608
|
+
value of the hrDeviceType object is
|
609
|
+
`hrDeviceNetwork'."
|
610
|
+
::= { hrDevice 4 }
|
611
|
+
|
612
|
+
hrNetworkEntry OBJECT-TYPE
|
613
|
+
SYNTAX HrNetworkEntry
|
614
|
+
MAX-ACCESS not-accessible
|
615
|
+
STATUS current
|
616
|
+
DESCRIPTION
|
617
|
+
"A (conceptual) entry for one network device contained
|
618
|
+
by the host. The hrDeviceIndex in the index
|
619
|
+
represents the entry in the hrDeviceTable that
|
620
|
+
corresponds to the hrNetworkEntry.
|
621
|
+
|
622
|
+
As an example of how objects in this table are named,
|
623
|
+
an instance of the hrNetworkIfIndex object might be
|
624
|
+
named hrNetworkIfIndex.3"
|
625
|
+
INDEX { hrDeviceIndex }
|
626
|
+
::= { hrNetworkTable 1 }
|
627
|
+
|
628
|
+
HrNetworkEntry ::= SEQUENCE {
|
629
|
+
hrNetworkIfIndex InterfaceIndexOrZero
|
630
|
+
}
|
631
|
+
|
632
|
+
hrNetworkIfIndex OBJECT-TYPE
|
633
|
+
SYNTAX InterfaceIndexOrZero
|
634
|
+
MAX-ACCESS read-only
|
635
|
+
STATUS current
|
636
|
+
DESCRIPTION
|
637
|
+
"The value of ifIndex which corresponds to this
|
638
|
+
network device. If this device is not represented in
|
639
|
+
the ifTable, then this value shall be zero."
|
640
|
+
::= { hrNetworkEntry 1 }
|
641
|
+
|
642
|
+
hrPrinterTable OBJECT-TYPE
|
643
|
+
SYNTAX SEQUENCE OF HrPrinterEntry
|
644
|
+
MAX-ACCESS not-accessible
|
645
|
+
STATUS current
|
646
|
+
DESCRIPTION
|
647
|
+
"The (conceptual) table of printers local to the host.
|
648
|
+
|
649
|
+
Note that this table is potentially sparse: a
|
650
|
+
(conceptual) entry exists only if the correspondent
|
651
|
+
value of the hrDeviceType object is
|
652
|
+
`hrDevicePrinter'."
|
653
|
+
::= { hrDevice 5 }
|
654
|
+
|
655
|
+
hrPrinterEntry OBJECT-TYPE
|
656
|
+
SYNTAX HrPrinterEntry
|
657
|
+
MAX-ACCESS not-accessible
|
658
|
+
STATUS current
|
659
|
+
DESCRIPTION
|
660
|
+
"A (conceptual) entry for one printer local to the
|
661
|
+
host. The hrDeviceIndex in the index represents the
|
662
|
+
entry in the hrDeviceTable that corresponds to the
|
663
|
+
hrPrinterEntry.
|
664
|
+
|
665
|
+
As an example of how objects in this table are named,
|
666
|
+
an instance of the hrPrinterStatus object might be
|
667
|
+
named hrPrinterStatus.3"
|
668
|
+
INDEX { hrDeviceIndex }
|
669
|
+
::= { hrPrinterTable 1 }
|
670
|
+
|
671
|
+
HrPrinterEntry ::= SEQUENCE {
|
672
|
+
hrPrinterStatus INTEGER,
|
673
|
+
hrPrinterDetectedErrorState OCTET STRING
|
674
|
+
}
|
675
|
+
|
676
|
+
hrPrinterStatus OBJECT-TYPE
|
677
|
+
SYNTAX INTEGER {
|
678
|
+
other(1),
|
679
|
+
unknown(2),
|
680
|
+
idle(3),
|
681
|
+
printing(4),
|
682
|
+
warmup(5)
|
683
|
+
}
|
684
|
+
MAX-ACCESS read-only
|
685
|
+
STATUS current
|
686
|
+
DESCRIPTION
|
687
|
+
"The current status of this printer device."
|
688
|
+
::= { hrPrinterEntry 1 }
|
689
|
+
|
690
|
+
hrPrinterDetectedErrorState OBJECT-TYPE
|
691
|
+
SYNTAX OCTET STRING
|
692
|
+
MAX-ACCESS read-only
|
693
|
+
STATUS current
|
694
|
+
DESCRIPTION
|
695
|
+
"This object represents any error conditions detected
|
696
|
+
by the printer. The error conditions are encoded as
|
697
|
+
bits in an octet string, with the following
|
698
|
+
definitions:
|
699
|
+
|
700
|
+
Condition Bit #
|
701
|
+
|
702
|
+
lowPaper 0
|
703
|
+
|
704
|
+
noPaper 1
|
705
|
+
lowToner 2
|
706
|
+
noToner 3
|
707
|
+
doorOpen 4
|
708
|
+
jammed 5
|
709
|
+
offline 6
|
710
|
+
serviceRequested 7
|
711
|
+
inputTrayMissing 8
|
712
|
+
outputTrayMissing 9
|
713
|
+
markerSupplyMissing 10
|
714
|
+
outputNearFull 11
|
715
|
+
outputFull 12
|
716
|
+
inputTrayEmpty 13
|
717
|
+
overduePreventMaint 14
|
718
|
+
|
719
|
+
Bits are numbered starting with the most significant
|
720
|
+
bit of the first byte being bit 0, the least
|
721
|
+
significant bit of the first byte being bit 7, the
|
722
|
+
most significant bit of the second byte being bit 8,
|
723
|
+
and so on. A one bit encodes that the condition was
|
724
|
+
detected, while a zero bit encodes that the condition
|
725
|
+
was not detected.
|
726
|
+
|
727
|
+
This object is useful for alerting an operator to
|
728
|
+
specific warning or error conditions that may occur,
|
729
|
+
especially those requiring human intervention."
|
730
|
+
::= { hrPrinterEntry 2 }
|
731
|
+
|
732
|
+
hrDiskStorageTable OBJECT-TYPE
|
733
|
+
SYNTAX SEQUENCE OF HrDiskStorageEntry
|
734
|
+
MAX-ACCESS not-accessible
|
735
|
+
STATUS current
|
736
|
+
DESCRIPTION
|
737
|
+
"The (conceptual) table of long-term storage devices
|
738
|
+
contained by the host. In particular, disk devices
|
739
|
+
accessed remotely over a network are not included
|
740
|
+
here.
|
741
|
+
|
742
|
+
Note that this table is potentially sparse: a
|
743
|
+
(conceptual) entry exists only if the correspondent
|
744
|
+
value of the hrDeviceType object is
|
745
|
+
`hrDeviceDiskStorage'."
|
746
|
+
::= { hrDevice 6 }
|
747
|
+
|
748
|
+
hrDiskStorageEntry OBJECT-TYPE
|
749
|
+
SYNTAX HrDiskStorageEntry
|
750
|
+
MAX-ACCESS not-accessible
|
751
|
+
STATUS current
|
752
|
+
DESCRIPTION
|
753
|
+
"A (conceptual) entry for one long-term storage device
|
754
|
+
contained by the host. The hrDeviceIndex in the index
|
755
|
+
represents the entry in the hrDeviceTable that
|
756
|
+
corresponds to the hrDiskStorageEntry. As an example,
|
757
|
+
an instance of the hrDiskStorageCapacity object might
|
758
|
+
be named hrDiskStorageCapacity.3"
|
759
|
+
INDEX { hrDeviceIndex }
|
760
|
+
::= { hrDiskStorageTable 1 }
|
761
|
+
|
762
|
+
HrDiskStorageEntry ::= SEQUENCE {
|
763
|
+
hrDiskStorageAccess INTEGER,
|
764
|
+
hrDiskStorageMedia INTEGER,
|
765
|
+
hrDiskStorageRemoveble TruthValue,
|
766
|
+
hrDiskStorageCapacity KBytes
|
767
|
+
}
|
768
|
+
|
769
|
+
hrDiskStorageAccess OBJECT-TYPE
|
770
|
+
SYNTAX INTEGER {
|
771
|
+
readWrite(1),
|
772
|
+
readOnly(2)
|
773
|
+
}
|
774
|
+
MAX-ACCESS read-only
|
775
|
+
STATUS current
|
776
|
+
DESCRIPTION
|
777
|
+
"An indication if this long-term storage device is
|
778
|
+
readable and writable or only readable. This should
|
779
|
+
reflect the media type, any write-protect mechanism,
|
780
|
+
and any device configuration that affects the entire
|
781
|
+
device."
|
782
|
+
::= { hrDiskStorageEntry 1 }
|
783
|
+
|
784
|
+
hrDiskStorageMedia OBJECT-TYPE
|
785
|
+
SYNTAX INTEGER {
|
786
|
+
other(1),
|
787
|
+
unknown(2),
|
788
|
+
hardDisk(3),
|
789
|
+
floppyDisk(4),
|
790
|
+
opticalDiskROM(5),
|
791
|
+
opticalDiskWORM(6), -- Write Once Read Many
|
792
|
+
opticalDiskRW(7),
|
793
|
+
ramDisk(8)
|
794
|
+
}
|
795
|
+
MAX-ACCESS read-only
|
796
|
+
STATUS current
|
797
|
+
DESCRIPTION
|
798
|
+
"An indication of the type of media used in this long-
|
799
|
+
term storage device."
|
800
|
+
::= { hrDiskStorageEntry 2 }
|
801
|
+
|
802
|
+
hrDiskStorageRemoveble OBJECT-TYPE
|
803
|
+
SYNTAX TruthValue
|
804
|
+
MAX-ACCESS read-only
|
805
|
+
STATUS current
|
806
|
+
DESCRIPTION
|
807
|
+
"Denotes whether or not the disk media may be removed
|
808
|
+
from the drive."
|
809
|
+
::= { hrDiskStorageEntry 3 }
|
810
|
+
|
811
|
+
hrDiskStorageCapacity OBJECT-TYPE
|
812
|
+
SYNTAX KBytes
|
813
|
+
UNITS "KBytes"
|
814
|
+
MAX-ACCESS read-only
|
815
|
+
STATUS current
|
816
|
+
DESCRIPTION
|
817
|
+
"The total size for this long-term storage device. If
|
818
|
+
the media is removable and is currently removed, this
|
819
|
+
value should be zero."
|
820
|
+
::= { hrDiskStorageEntry 4 }
|
821
|
+
|
822
|
+
hrPartitionTable OBJECT-TYPE
|
823
|
+
SYNTAX SEQUENCE OF HrPartitionEntry
|
824
|
+
MAX-ACCESS not-accessible
|
825
|
+
STATUS current
|
826
|
+
DESCRIPTION
|
827
|
+
"The (conceptual) table of partitions for long-term
|
828
|
+
storage devices contained by the host. In particular,
|
829
|
+
partitions accessed remotely over a network are not
|
830
|
+
included here."
|
831
|
+
::= { hrDevice 7 }
|
832
|
+
|
833
|
+
hrPartitionEntry OBJECT-TYPE
|
834
|
+
SYNTAX HrPartitionEntry
|
835
|
+
MAX-ACCESS not-accessible
|
836
|
+
STATUS current
|
837
|
+
DESCRIPTION
|
838
|
+
"A (conceptual) entry for one partition. The
|
839
|
+
hrDeviceIndex in the index represents the entry in the
|
840
|
+
hrDeviceTable that corresponds to the
|
841
|
+
hrPartitionEntry.
|
842
|
+
|
843
|
+
As an example of how objects in this table are named,
|
844
|
+
an instance of the hrPartitionSize object might be
|
845
|
+
named hrPartitionSize.3.1"
|
846
|
+
INDEX { hrDeviceIndex, hrPartitionIndex }
|
847
|
+
::= { hrPartitionTable 1 }
|
848
|
+
|
849
|
+
HrPartitionEntry ::= SEQUENCE {
|
850
|
+
hrPartitionIndex Integer32,
|
851
|
+
hrPartitionLabel InternationalDisplayString,
|
852
|
+
hrPartitionID OCTET STRING,
|
853
|
+
hrPartitionSize KBytes,
|
854
|
+
hrPartitionFSIndex Integer32
|
855
|
+
}
|
856
|
+
|
857
|
+
hrPartitionIndex OBJECT-TYPE
|
858
|
+
SYNTAX Integer32 (1..2147483647)
|
859
|
+
MAX-ACCESS read-only
|
860
|
+
STATUS current
|
861
|
+
DESCRIPTION
|
862
|
+
"A unique value for each partition on this long-term
|
863
|
+
storage device. The value for each long-term storage
|
864
|
+
device must remain constant at least from one re-
|
865
|
+
initialization of the agent to the next re-
|
866
|
+
initialization."
|
867
|
+
::= { hrPartitionEntry 1 }
|
868
|
+
|
869
|
+
hrPartitionLabel OBJECT-TYPE
|
870
|
+
SYNTAX InternationalDisplayString (SIZE (0..128))
|
871
|
+
MAX-ACCESS read-only
|
872
|
+
STATUS current
|
873
|
+
DESCRIPTION
|
874
|
+
"A textual description of this partition."
|
875
|
+
::= { hrPartitionEntry 2 }
|
876
|
+
|
877
|
+
hrPartitionID OBJECT-TYPE
|
878
|
+
SYNTAX OCTET STRING
|
879
|
+
MAX-ACCESS read-only
|
880
|
+
STATUS current
|
881
|
+
DESCRIPTION
|
882
|
+
"A descriptor which uniquely represents this partition
|
883
|
+
to the responsible operating system. On some systems,
|
884
|
+
this might take on a binary representation."
|
885
|
+
::= { hrPartitionEntry 3 }
|
886
|
+
|
887
|
+
hrPartitionSize OBJECT-TYPE
|
888
|
+
SYNTAX KBytes
|
889
|
+
UNITS "KBytes"
|
890
|
+
MAX-ACCESS read-only
|
891
|
+
STATUS current
|
892
|
+
DESCRIPTION
|
893
|
+
"The size of this partition."
|
894
|
+
::= { hrPartitionEntry 4 }
|
895
|
+
|
896
|
+
hrPartitionFSIndex OBJECT-TYPE
|
897
|
+
SYNTAX Integer32 (0..2147483647)
|
898
|
+
MAX-ACCESS read-only
|
899
|
+
STATUS current
|
900
|
+
DESCRIPTION
|
901
|
+
"The index of the file system mounted on this
|
902
|
+
partition. If no file system is mounted on this
|
903
|
+
partition, then this value shall be zero. Note that
|
904
|
+
multiple partitions may point to one file system,
|
905
|
+
denoting that that file system resides on those
|
906
|
+
partitions. Multiple file systems may not reside on
|
907
|
+
one partition."
|
908
|
+
::= { hrPartitionEntry 5 }
|
909
|
+
|
910
|
+
-- The File System Table
|
911
|
+
|
912
|
+
-- Registration point for popular File System types,
|
913
|
+
-- for use with hrFSType. These are defined in the
|
914
|
+
-- HOST-RESOURCES-TYPES module.
|
915
|
+
hrFSTypes OBJECT IDENTIFIER ::= { hrDevice 9 }
|
916
|
+
|
917
|
+
hrFSTable OBJECT-TYPE
|
918
|
+
SYNTAX SEQUENCE OF HrFSEntry
|
919
|
+
MAX-ACCESS not-accessible
|
920
|
+
STATUS current
|
921
|
+
DESCRIPTION
|
922
|
+
"The (conceptual) table of file systems local to this
|
923
|
+
host or remotely mounted from a file server. File
|
924
|
+
systems that are in only one user's environment on a
|
925
|
+
multi-user system will not be included in this table."
|
926
|
+
::= { hrDevice 8 }
|
927
|
+
|
928
|
+
hrFSEntry OBJECT-TYPE
|
929
|
+
SYNTAX HrFSEntry
|
930
|
+
MAX-ACCESS not-accessible
|
931
|
+
STATUS current
|
932
|
+
DESCRIPTION
|
933
|
+
"A (conceptual) entry for one file system local to
|
934
|
+
this host or remotely mounted from a file server.
|
935
|
+
File systems that are in only one user's environment
|
936
|
+
on a multi-user system will not be included in this
|
937
|
+
table.
|
938
|
+
|
939
|
+
As an example of how objects in this table are named,
|
940
|
+
an instance of the hrFSMountPoint object might be
|
941
|
+
named hrFSMountPoint.3"
|
942
|
+
INDEX { hrFSIndex }
|
943
|
+
::= { hrFSTable 1 }
|
944
|
+
|
945
|
+
HrFSEntry ::= SEQUENCE {
|
946
|
+
hrFSIndex Integer32,
|
947
|
+
hrFSMountPoint InternationalDisplayString,
|
948
|
+
hrFSRemoteMountPoint InternationalDisplayString,
|
949
|
+
hrFSType AutonomousType,
|
950
|
+
hrFSAccess INTEGER,
|
951
|
+
hrFSBootable TruthValue,
|
952
|
+
hrFSStorageIndex Integer32,
|
953
|
+
hrFSLastFullBackupDate DateAndTime,
|
954
|
+
hrFSLastPartialBackupDate DateAndTime
|
955
|
+
}
|
956
|
+
|
957
|
+
hrFSIndex OBJECT-TYPE
|
958
|
+
SYNTAX Integer32 (1..2147483647)
|
959
|
+
MAX-ACCESS read-only
|
960
|
+
STATUS current
|
961
|
+
DESCRIPTION
|
962
|
+
"A unique value for each file system local to this
|
963
|
+
host. The value for each file system must remain
|
964
|
+
constant at least from one re-initialization of the
|
965
|
+
agent to the next re-initialization."
|
966
|
+
::= { hrFSEntry 1 }
|
967
|
+
|
968
|
+
hrFSMountPoint OBJECT-TYPE
|
969
|
+
SYNTAX InternationalDisplayString (SIZE(0..128))
|
970
|
+
MAX-ACCESS read-only
|
971
|
+
STATUS current
|
972
|
+
DESCRIPTION
|
973
|
+
"The path name of the root of this file system."
|
974
|
+
::= { hrFSEntry 2 }
|
975
|
+
|
976
|
+
hrFSRemoteMountPoint OBJECT-TYPE
|
977
|
+
SYNTAX InternationalDisplayString (SIZE(0..128))
|
978
|
+
MAX-ACCESS read-only
|
979
|
+
STATUS current
|
980
|
+
DESCRIPTION
|
981
|
+
"A description of the name and/or address of the
|
982
|
+
server that this file system is mounted from. This
|
983
|
+
may also include parameters such as the mount point on
|
984
|
+
the remote file system. If this is not a remote file
|
985
|
+
system, this string should have a length of zero."
|
986
|
+
::= { hrFSEntry 3 }
|
987
|
+
|
988
|
+
hrFSType OBJECT-TYPE
|
989
|
+
SYNTAX AutonomousType
|
990
|
+
MAX-ACCESS read-only
|
991
|
+
STATUS current
|
992
|
+
DESCRIPTION
|
993
|
+
"The value of this object identifies the type of this
|
994
|
+
file system."
|
995
|
+
::= { hrFSEntry 4 }
|
996
|
+
|
997
|
+
hrFSAccess OBJECT-TYPE
|
998
|
+
SYNTAX INTEGER {
|
999
|
+
readWrite(1),
|
1000
|
+
readOnly(2)
|
1001
|
+
}
|
1002
|
+
MAX-ACCESS read-only
|
1003
|
+
STATUS current
|
1004
|
+
DESCRIPTION
|
1005
|
+
"An indication if this file system is logically
|
1006
|
+
configured by the operating system to be readable and
|
1007
|
+
writable or only readable. This does not represent
|
1008
|
+
any local access-control policy, except one that is
|
1009
|
+
applied to the file system as a whole."
|
1010
|
+
::= { hrFSEntry 5 }
|
1011
|
+
|
1012
|
+
hrFSBootable OBJECT-TYPE
|
1013
|
+
SYNTAX TruthValue
|
1014
|
+
MAX-ACCESS read-only
|
1015
|
+
STATUS current
|
1016
|
+
DESCRIPTION
|
1017
|
+
"A flag indicating whether this file system is
|
1018
|
+
bootable."
|
1019
|
+
::= { hrFSEntry 6 }
|
1020
|
+
|
1021
|
+
hrFSStorageIndex OBJECT-TYPE
|
1022
|
+
SYNTAX Integer32 (0..2147483647)
|
1023
|
+
MAX-ACCESS read-only
|
1024
|
+
STATUS current
|
1025
|
+
DESCRIPTION
|
1026
|
+
"The index of the hrStorageEntry that represents
|
1027
|
+
information about this file system. If there is no
|
1028
|
+
such information available, then this value shall be
|
1029
|
+
zero. The relevant storage entry will be useful in
|
1030
|
+
tracking the percent usage of this file system and
|
1031
|
+
diagnosing errors that may occur when it runs out of
|
1032
|
+
space."
|
1033
|
+
::= { hrFSEntry 7 }
|
1034
|
+
|
1035
|
+
hrFSLastFullBackupDate OBJECT-TYPE
|
1036
|
+
SYNTAX DateAndTime
|
1037
|
+
MAX-ACCESS read-write
|
1038
|
+
STATUS current
|
1039
|
+
DESCRIPTION
|
1040
|
+
"The last date at which this complete file system was
|
1041
|
+
|
1042
|
+
copied to another storage device for backup. This
|
1043
|
+
information is useful for ensuring that backups are
|
1044
|
+
being performed regularly.
|
1045
|
+
|
1046
|
+
If this information is not known, then this variable
|
1047
|
+
shall have the value corresponding to January 1, year
|
1048
|
+
0000, 00:00:00.0, which is encoded as
|
1049
|
+
(hex)'00 00 01 01 00 00 00 00'."
|
1050
|
+
::= { hrFSEntry 8 }
|
1051
|
+
|
1052
|
+
hrFSLastPartialBackupDate OBJECT-TYPE
|
1053
|
+
SYNTAX DateAndTime
|
1054
|
+
MAX-ACCESS read-write
|
1055
|
+
STATUS current
|
1056
|
+
DESCRIPTION
|
1057
|
+
"The last date at which a portion of this file system
|
1058
|
+
was copied to another storage device for backup. This
|
1059
|
+
information is useful for ensuring that backups are
|
1060
|
+
being performed regularly.
|
1061
|
+
|
1062
|
+
If this information is not known, then this variable
|
1063
|
+
shall have the value corresponding to January 1, year
|
1064
|
+
0000, 00:00:00.0, which is encoded as
|
1065
|
+
(hex)'00 00 01 01 00 00 00 00'."
|
1066
|
+
::= { hrFSEntry 9 }
|
1067
|
+
|
1068
|
+
-- The Host Resources Running Software Group
|
1069
|
+
--
|
1070
|
+
-- The hrSWRunTable contains an entry for each distinct piece of
|
1071
|
+
-- software that is running or loaded into physical or virtual
|
1072
|
+
-- memory in preparation for running. This includes the host's
|
1073
|
+
-- operating system, device drivers, and applications.
|
1074
|
+
|
1075
|
+
hrSWOSIndex OBJECT-TYPE
|
1076
|
+
SYNTAX Integer32 (1..2147483647)
|
1077
|
+
MAX-ACCESS read-only
|
1078
|
+
STATUS current
|
1079
|
+
DESCRIPTION
|
1080
|
+
"The value of the hrSWRunIndex for the hrSWRunEntry
|
1081
|
+
that represents the primary operating system running
|
1082
|
+
on this host. This object is useful for quickly and
|
1083
|
+
uniquely identifying that primary operating system."
|
1084
|
+
::= { hrSWRun 1 }
|
1085
|
+
|
1086
|
+
hrSWRunTable OBJECT-TYPE
|
1087
|
+
SYNTAX SEQUENCE OF HrSWRunEntry
|
1088
|
+
MAX-ACCESS not-accessible
|
1089
|
+
STATUS current
|
1090
|
+
DESCRIPTION
|
1091
|
+
"The (conceptual) table of software running on the
|
1092
|
+
host."
|
1093
|
+
::= { hrSWRun 2 }
|
1094
|
+
|
1095
|
+
hrSWRunEntry OBJECT-TYPE
|
1096
|
+
SYNTAX HrSWRunEntry
|
1097
|
+
MAX-ACCESS not-accessible
|
1098
|
+
STATUS current
|
1099
|
+
DESCRIPTION
|
1100
|
+
"A (conceptual) entry for one piece of software
|
1101
|
+
running on the host Note that because the installed
|
1102
|
+
software table only contains information for software
|
1103
|
+
stored locally on this host, not every piece of
|
1104
|
+
running software will be found in the installed
|
1105
|
+
software table. This is true of software that was
|
1106
|
+
loaded and run from a non-local source, such as a
|
1107
|
+
network-mounted file system.
|
1108
|
+
|
1109
|
+
As an example of how objects in this table are named,
|
1110
|
+
an instance of the hrSWRunName object might be named
|
1111
|
+
hrSWRunName.1287"
|
1112
|
+
INDEX { hrSWRunIndex }
|
1113
|
+
::= { hrSWRunTable 1 }
|
1114
|
+
|
1115
|
+
HrSWRunEntry ::= SEQUENCE {
|
1116
|
+
hrSWRunIndex Integer32,
|
1117
|
+
hrSWRunName InternationalDisplayString,
|
1118
|
+
hrSWRunID ProductID,
|
1119
|
+
hrSWRunPath InternationalDisplayString,
|
1120
|
+
hrSWRunParameters InternationalDisplayString,
|
1121
|
+
hrSWRunType INTEGER,
|
1122
|
+
hrSWRunStatus INTEGER
|
1123
|
+
}
|
1124
|
+
|
1125
|
+
hrSWRunIndex OBJECT-TYPE
|
1126
|
+
SYNTAX Integer32 (1..2147483647)
|
1127
|
+
MAX-ACCESS read-only
|
1128
|
+
STATUS current
|
1129
|
+
DESCRIPTION
|
1130
|
+
"A unique value for each piece of software running on
|
1131
|
+
the host. Wherever possible, this should be the
|
1132
|
+
system's native, unique identification number."
|
1133
|
+
::= { hrSWRunEntry 1 }
|
1134
|
+
|
1135
|
+
hrSWRunName OBJECT-TYPE
|
1136
|
+
SYNTAX InternationalDisplayString (SIZE (0..64))
|
1137
|
+
MAX-ACCESS read-only
|
1138
|
+
STATUS current
|
1139
|
+
DESCRIPTION
|
1140
|
+
"A textual description of this running piece of
|
1141
|
+
software, including the manufacturer, revision, and
|
1142
|
+
the name by which it is commonly known. If this
|
1143
|
+
software was installed locally, this should be the
|
1144
|
+
same string as used in the corresponding
|
1145
|
+
hrSWInstalledName."
|
1146
|
+
::= { hrSWRunEntry 2 }
|
1147
|
+
|
1148
|
+
hrSWRunID OBJECT-TYPE
|
1149
|
+
SYNTAX ProductID
|
1150
|
+
MAX-ACCESS read-only
|
1151
|
+
STATUS current
|
1152
|
+
DESCRIPTION
|
1153
|
+
"The product ID of this running piece of software."
|
1154
|
+
::= { hrSWRunEntry 3 }
|
1155
|
+
|
1156
|
+
hrSWRunPath OBJECT-TYPE
|
1157
|
+
SYNTAX InternationalDisplayString (SIZE(0..128))
|
1158
|
+
MAX-ACCESS read-only
|
1159
|
+
STATUS current
|
1160
|
+
DESCRIPTION
|
1161
|
+
"A description of the location on long-term storage
|
1162
|
+
(e.g. a disk drive) from which this software was
|
1163
|
+
loaded."
|
1164
|
+
::= { hrSWRunEntry 4 }
|
1165
|
+
|
1166
|
+
hrSWRunParameters OBJECT-TYPE
|
1167
|
+
SYNTAX InternationalDisplayString (SIZE(0..128))
|
1168
|
+
MAX-ACCESS read-only
|
1169
|
+
STATUS current
|
1170
|
+
DESCRIPTION
|
1171
|
+
"A description of the parameters supplied to this
|
1172
|
+
software when it was initially loaded."
|
1173
|
+
::= { hrSWRunEntry 5 }
|
1174
|
+
|
1175
|
+
hrSWRunType OBJECT-TYPE
|
1176
|
+
SYNTAX INTEGER {
|
1177
|
+
unknown(1),
|
1178
|
+
operatingSystem(2),
|
1179
|
+
deviceDriver(3),
|
1180
|
+
application(4)
|
1181
|
+
}
|
1182
|
+
MAX-ACCESS read-only
|
1183
|
+
STATUS current
|
1184
|
+
DESCRIPTION
|
1185
|
+
"The type of this software."
|
1186
|
+
::= { hrSWRunEntry 6 }
|
1187
|
+
|
1188
|
+
hrSWRunStatus OBJECT-TYPE
|
1189
|
+
SYNTAX INTEGER {
|
1190
|
+
running(1),
|
1191
|
+
runnable(2), -- waiting for resource
|
1192
|
+
-- (i.e., CPU, memory, IO)
|
1193
|
+
notRunnable(3), -- loaded but waiting for event
|
1194
|
+
invalid(4) -- not loaded
|
1195
|
+
}
|
1196
|
+
MAX-ACCESS read-write
|
1197
|
+
STATUS current
|
1198
|
+
DESCRIPTION
|
1199
|
+
"The status of this running piece of software.
|
1200
|
+
Setting this value to invalid(4) shall cause this
|
1201
|
+
software to stop running and to be unloaded. Sets to
|
1202
|
+
other values are not valid."
|
1203
|
+
::= { hrSWRunEntry 7 }
|
1204
|
+
|
1205
|
+
-- The Host Resources Running Software Performance Group
|
1206
|
+
--
|
1207
|
+
-- The hrSWRunPerfTable contains an entry corresponding to
|
1208
|
+
-- each entry in the hrSWRunTable.
|
1209
|
+
|
1210
|
+
hrSWRunPerfTable OBJECT-TYPE
|
1211
|
+
SYNTAX SEQUENCE OF HrSWRunPerfEntry
|
1212
|
+
MAX-ACCESS not-accessible
|
1213
|
+
STATUS current
|
1214
|
+
DESCRIPTION
|
1215
|
+
"The (conceptual) table of running software
|
1216
|
+
performance metrics."
|
1217
|
+
::= { hrSWRunPerf 1 }
|
1218
|
+
|
1219
|
+
hrSWRunPerfEntry OBJECT-TYPE
|
1220
|
+
SYNTAX HrSWRunPerfEntry
|
1221
|
+
MAX-ACCESS not-accessible
|
1222
|
+
STATUS current
|
1223
|
+
DESCRIPTION
|
1224
|
+
"A (conceptual) entry containing software performance
|
1225
|
+
metrics. As an example, an instance of the
|
1226
|
+
hrSWRunPerfCPU object might be named
|
1227
|
+
hrSWRunPerfCPU.1287"
|
1228
|
+
AUGMENTS { hrSWRunEntry } -- This table augments information in
|
1229
|
+
-- the hrSWRunTable.
|
1230
|
+
::= { hrSWRunPerfTable 1 }
|
1231
|
+
|
1232
|
+
HrSWRunPerfEntry ::= SEQUENCE {
|
1233
|
+
hrSWRunPerfCPU Integer32,
|
1234
|
+
hrSWRunPerfMem KBytes
|
1235
|
+
}
|
1236
|
+
|
1237
|
+
hrSWRunPerfCPU OBJECT-TYPE
|
1238
|
+
SYNTAX Integer32 (0..2147483647)
|
1239
|
+
MAX-ACCESS read-only
|
1240
|
+
STATUS current
|
1241
|
+
DESCRIPTION
|
1242
|
+
"The number of centi-seconds of the total system's CPU
|
1243
|
+
resources consumed by this process. Note that on a
|
1244
|
+
multi-processor system, this value may increment by
|
1245
|
+
more than one centi-second in one centi-second of real
|
1246
|
+
(wall clock) time."
|
1247
|
+
::= { hrSWRunPerfEntry 1 }
|
1248
|
+
|
1249
|
+
hrSWRunPerfMem OBJECT-TYPE
|
1250
|
+
SYNTAX KBytes
|
1251
|
+
UNITS "KBytes"
|
1252
|
+
MAX-ACCESS read-only
|
1253
|
+
STATUS current
|
1254
|
+
DESCRIPTION
|
1255
|
+
"The total amount of real system memory allocated to
|
1256
|
+
this process."
|
1257
|
+
::= { hrSWRunPerfEntry 2 }
|
1258
|
+
|
1259
|
+
-- The Host Resources Installed Software Group
|
1260
|
+
--
|
1261
|
+
-- The hrSWInstalledTable contains an entry for each piece
|
1262
|
+
-- of software installed in long-term storage (e.g. a disk
|
1263
|
+
-- drive) locally on this host. Note that this does not
|
1264
|
+
-- include software loadable remotely from a network
|
1265
|
+
-- server.
|
1266
|
+
--
|
1267
|
+
-- Different implementations may track software in varying
|
1268
|
+
-- ways. For example, while some implementations may track
|
1269
|
+
-- executable files as distinct pieces of software, other
|
1270
|
+
-- implementations may use other strategies such as keeping
|
1271
|
+
-- track of software "packages" (e.g., related groups of files)
|
1272
|
+
-- or keeping track of system or application "patches".
|
1273
|
+
--
|
1274
|
+
-- This table is useful for identifying and inventorying
|
1275
|
+
-- software on a host and for diagnosing incompatibility
|
1276
|
+
-- and version mismatch problems between various pieces
|
1277
|
+
-- of hardware and software.
|
1278
|
+
|
1279
|
+
hrSWInstalledLastChange OBJECT-TYPE
|
1280
|
+
SYNTAX TimeTicks
|
1281
|
+
MAX-ACCESS read-only
|
1282
|
+
STATUS current
|
1283
|
+
DESCRIPTION
|
1284
|
+
"The value of sysUpTime when an entry in the
|
1285
|
+
hrSWInstalledTable was last added, renamed, or
|
1286
|
+
deleted. Because this table is likely to contain many
|
1287
|
+
entries, polling of this object allows a management
|
1288
|
+
station to determine when re-downloading of the table
|
1289
|
+
might be useful."
|
1290
|
+
::= { hrSWInstalled 1 }
|
1291
|
+
|
1292
|
+
hrSWInstalledLastUpdateTime OBJECT-TYPE
|
1293
|
+
SYNTAX TimeTicks
|
1294
|
+
MAX-ACCESS read-only
|
1295
|
+
STATUS current
|
1296
|
+
DESCRIPTION
|
1297
|
+
"The value of sysUpTime when the hrSWInstalledTable
|
1298
|
+
was last completely updated. Because caching of this
|
1299
|
+
data will be a popular implementation strategy,
|
1300
|
+
retrieval of this object allows a management station
|
1301
|
+
to obtain a guarantee that no data in this table is
|
1302
|
+
older than the indicated time."
|
1303
|
+
::= { hrSWInstalled 2 }
|
1304
|
+
|
1305
|
+
hrSWInstalledTable OBJECT-TYPE
|
1306
|
+
SYNTAX SEQUENCE OF HrSWInstalledEntry
|
1307
|
+
MAX-ACCESS not-accessible
|
1308
|
+
STATUS current
|
1309
|
+
DESCRIPTION
|
1310
|
+
"The (conceptual) table of software installed on this
|
1311
|
+
host."
|
1312
|
+
::= { hrSWInstalled 3 }
|
1313
|
+
|
1314
|
+
hrSWInstalledEntry OBJECT-TYPE
|
1315
|
+
SYNTAX HrSWInstalledEntry
|
1316
|
+
MAX-ACCESS not-accessible
|
1317
|
+
STATUS current
|
1318
|
+
DESCRIPTION
|
1319
|
+
"A (conceptual) entry for a piece of software
|
1320
|
+
installed on this host.
|
1321
|
+
|
1322
|
+
As an example of how objects in this table are named,
|
1323
|
+
an instance of the hrSWInstalledName object might be
|
1324
|
+
named hrSWInstalledName.96"
|
1325
|
+
INDEX { hrSWInstalledIndex }
|
1326
|
+
::= { hrSWInstalledTable 1 }
|
1327
|
+
|
1328
|
+
HrSWInstalledEntry ::= SEQUENCE {
|
1329
|
+
hrSWInstalledIndex Integer32,
|
1330
|
+
hrSWInstalledName InternationalDisplayString,
|
1331
|
+
hrSWInstalledID ProductID,
|
1332
|
+
hrSWInstalledType INTEGER,
|
1333
|
+
hrSWInstalledDate DateAndTime
|
1334
|
+
}
|
1335
|
+
|
1336
|
+
hrSWInstalledIndex OBJECT-TYPE
|
1337
|
+
SYNTAX Integer32 (1..2147483647)
|
1338
|
+
MAX-ACCESS read-only
|
1339
|
+
STATUS current
|
1340
|
+
DESCRIPTION
|
1341
|
+
"A unique value for each piece of software installed
|
1342
|
+
on the host. This value shall be in the range from 1
|
1343
|
+
to the number of pieces of software installed on the
|
1344
|
+
host."
|
1345
|
+
::= { hrSWInstalledEntry 1 }
|
1346
|
+
|
1347
|
+
hrSWInstalledName OBJECT-TYPE
|
1348
|
+
SYNTAX InternationalDisplayString (SIZE (0..64))
|
1349
|
+
MAX-ACCESS read-only
|
1350
|
+
STATUS current
|
1351
|
+
DESCRIPTION
|
1352
|
+
"A textual description of this installed piece of
|
1353
|
+
software, including the manufacturer, revision, the
|
1354
|
+
name by which it is commonly known, and optionally,
|
1355
|
+
its serial number."
|
1356
|
+
::= { hrSWInstalledEntry 2 }
|
1357
|
+
|
1358
|
+
hrSWInstalledID OBJECT-TYPE
|
1359
|
+
SYNTAX ProductID
|
1360
|
+
MAX-ACCESS read-only
|
1361
|
+
STATUS current
|
1362
|
+
DESCRIPTION
|
1363
|
+
"The product ID of this installed piece of software."
|
1364
|
+
::= { hrSWInstalledEntry 3 }
|
1365
|
+
|
1366
|
+
hrSWInstalledType OBJECT-TYPE
|
1367
|
+
SYNTAX INTEGER {
|
1368
|
+
unknown(1),
|
1369
|
+
operatingSystem(2),
|
1370
|
+
deviceDriver(3),
|
1371
|
+
application(4)
|
1372
|
+
}
|
1373
|
+
MAX-ACCESS read-only
|
1374
|
+
STATUS current
|
1375
|
+
DESCRIPTION
|
1376
|
+
"The type of this software."
|
1377
|
+
::= { hrSWInstalledEntry 4 }
|
1378
|
+
|
1379
|
+
hrSWInstalledDate OBJECT-TYPE
|
1380
|
+
SYNTAX DateAndTime
|
1381
|
+
MAX-ACCESS read-only
|
1382
|
+
STATUS current
|
1383
|
+
DESCRIPTION
|
1384
|
+
"The last-modification date of this application as it
|
1385
|
+
would appear in a directory listing.
|
1386
|
+
|
1387
|
+
If this information is not known, then this variable
|
1388
|
+
shall have the value corresponding to January 1, year
|
1389
|
+
0000, 00:00:00.0, which is encoded as
|
1390
|
+
(hex)'00 00 01 01 00 00 00 00'."
|
1391
|
+
::= { hrSWInstalledEntry 5 }
|
1392
|
+
|
1393
|
+
-- Conformance information
|
1394
|
+
|
1395
|
+
hrMIBCompliances OBJECT IDENTIFIER ::= { hrMIBAdminInfo 2 }
|
1396
|
+
hrMIBGroups OBJECT IDENTIFIER ::= { hrMIBAdminInfo 3 }
|
1397
|
+
|
1398
|
+
-- Compliance Statements
|
1399
|
+
hrMIBCompliance MODULE-COMPLIANCE
|
1400
|
+
STATUS current
|
1401
|
+
DESCRIPTION
|
1402
|
+
"The requirements for conformance to the Host Resources MIB."
|
1403
|
+
MODULE -- this module
|
1404
|
+
MANDATORY-GROUPS { hrSystemGroup, hrStorageGroup,
|
1405
|
+
hrDeviceGroup }
|
1406
|
+
|
1407
|
+
OBJECT hrSystemDate
|
1408
|
+
MIN-ACCESS read-only
|
1409
|
+
DESCRIPTION
|
1410
|
+
"Write access is not required."
|
1411
|
+
|
1412
|
+
OBJECT hrSystemInitialLoadDevice
|
1413
|
+
MIN-ACCESS read-only
|
1414
|
+
DESCRIPTION
|
1415
|
+
"Write access is not required."
|
1416
|
+
|
1417
|
+
OBJECT hrSystemInitialLoadParameters
|
1418
|
+
MIN-ACCESS read-only
|
1419
|
+
DESCRIPTION
|
1420
|
+
"Write access is not required."
|
1421
|
+
|
1422
|
+
OBJECT hrStorageSize
|
1423
|
+
MIN-ACCESS read-only
|
1424
|
+
DESCRIPTION
|
1425
|
+
"Write access is not required."
|
1426
|
+
|
1427
|
+
OBJECT hrFSLastFullBackupDate
|
1428
|
+
MIN-ACCESS read-only
|
1429
|
+
DESCRIPTION
|
1430
|
+
"Write access is not required."
|
1431
|
+
|
1432
|
+
OBJECT hrFSLastPartialBackupDate
|
1433
|
+
MIN-ACCESS read-only
|
1434
|
+
DESCRIPTION
|
1435
|
+
"Write access is not required."
|
1436
|
+
|
1437
|
+
GROUP hrSWRunGroup
|
1438
|
+
DESCRIPTION
|
1439
|
+
"The Running Software Group. Implementation
|
1440
|
+
of this group is mandatory only when the
|
1441
|
+
hrSWRunPerfGroup is implemented."
|
1442
|
+
|
1443
|
+
OBJECT hrSWRunStatus
|
1444
|
+
MIN-ACCESS read-only
|
1445
|
+
DESCRIPTION
|
1446
|
+
"Write access is not required."
|
1447
|
+
|
1448
|
+
GROUP hrSWRunPerfGroup
|
1449
|
+
DESCRIPTION
|
1450
|
+
"The Running Software Performance Group.
|
1451
|
+
Implementation of this group is at the discretion
|
1452
|
+
of the implementor."
|
1453
|
+
|
1454
|
+
GROUP hrSWInstalledGroup
|
1455
|
+
DESCRIPTION
|
1456
|
+
"The Installed Software Group.
|
1457
|
+
Implementation of this group is at the discretion
|
1458
|
+
of the implementor."
|
1459
|
+
::= { hrMIBCompliances 1 }
|
1460
|
+
|
1461
|
+
hrSystemGroup OBJECT-GROUP
|
1462
|
+
OBJECTS {
|
1463
|
+
hrSystemUptime, hrSystemDate,
|
1464
|
+
hrSystemInitialLoadDevice,
|
1465
|
+
hrSystemInitialLoadParameters,
|
1466
|
+
hrSystemNumUsers, hrSystemProcesses,
|
1467
|
+
hrSystemMaxProcesses
|
1468
|
+
}
|
1469
|
+
STATUS current
|
1470
|
+
DESCRIPTION
|
1471
|
+
"The Host Resources System Group."
|
1472
|
+
::= { hrMIBGroups 1 }
|
1473
|
+
|
1474
|
+
hrStorageGroup OBJECT-GROUP
|
1475
|
+
OBJECTS {
|
1476
|
+
hrMemorySize, hrStorageIndex, hrStorageType,
|
1477
|
+
hrStorageDescr, hrStorageAllocationUnits,
|
1478
|
+
hrStorageSize, hrStorageUsed,
|
1479
|
+
hrStorageAllocationFailures
|
1480
|
+
}
|
1481
|
+
STATUS current
|
1482
|
+
DESCRIPTION
|
1483
|
+
"The Host Resources Storage Group."
|
1484
|
+
::= { hrMIBGroups 2 }
|
1485
|
+
|
1486
|
+
hrDeviceGroup OBJECT-GROUP
|
1487
|
+
OBJECTS {
|
1488
|
+
hrDeviceIndex, hrDeviceType, hrDeviceDescr,
|
1489
|
+
hrDeviceID, hrDeviceStatus, hrDeviceErrors,
|
1490
|
+
hrProcessorFrwID, hrProcessorLoad,
|
1491
|
+
hrNetworkIfIndex, hrPrinterStatus,
|
1492
|
+
hrPrinterDetectedErrorState,
|
1493
|
+
hrDiskStorageAccess, hrDiskStorageMedia,
|
1494
|
+
hrDiskStorageRemoveble, hrDiskStorageCapacity,
|
1495
|
+
hrPartitionIndex, hrPartitionLabel,
|
1496
|
+
hrPartitionID, hrPartitionSize,
|
1497
|
+
hrPartitionFSIndex, hrFSIndex, hrFSMountPoint,
|
1498
|
+
hrFSRemoteMountPoint, hrFSType, hrFSAccess,
|
1499
|
+
hrFSBootable, hrFSStorageIndex,
|
1500
|
+
hrFSLastFullBackupDate,
|
1501
|
+
hrFSLastPartialBackupDate
|
1502
|
+
}
|
1503
|
+
STATUS current
|
1504
|
+
DESCRIPTION
|
1505
|
+
"The Host Resources Device Group."
|
1506
|
+
::= { hrMIBGroups 3 }
|
1507
|
+
|
1508
|
+
hrSWRunGroup OBJECT-GROUP
|
1509
|
+
OBJECTS {
|
1510
|
+
hrSWOSIndex, hrSWRunIndex, hrSWRunName,
|
1511
|
+
hrSWRunID, hrSWRunPath, hrSWRunParameters,
|
1512
|
+
hrSWRunType, hrSWRunStatus
|
1513
|
+
}
|
1514
|
+
STATUS current
|
1515
|
+
DESCRIPTION
|
1516
|
+
"The Host Resources Running Software Group."
|
1517
|
+
::= { hrMIBGroups 4 }
|
1518
|
+
|
1519
|
+
hrSWRunPerfGroup OBJECT-GROUP
|
1520
|
+
OBJECTS { hrSWRunPerfCPU, hrSWRunPerfMem }
|
1521
|
+
STATUS current
|
1522
|
+
DESCRIPTION
|
1523
|
+
"The Host Resources Running Software
|
1524
|
+
Performance Group."
|
1525
|
+
::= { hrMIBGroups 5 }
|
1526
|
+
|
1527
|
+
hrSWInstalledGroup OBJECT-GROUP
|
1528
|
+
OBJECTS {
|
1529
|
+
hrSWInstalledLastChange,
|
1530
|
+
hrSWInstalledLastUpdateTime,
|
1531
|
+
hrSWInstalledIndex, hrSWInstalledName,
|
1532
|
+
hrSWInstalledID, hrSWInstalledType,
|
1533
|
+
hrSWInstalledDate
|
1534
|
+
}
|
1535
|
+
STATUS current
|
1536
|
+
DESCRIPTION
|
1537
|
+
"The Host Resources Installed Software Group."
|
1538
|
+
::= { hrMIBGroups 6 }
|
1539
|
+
|
1540
|
+
END
|