telemetry-snmp 0.1.0

Sign up to get free protection for your applications and to get access to all the features.
Files changed (131) hide show
  1. checksums.yaml +7 -0
  2. data/.github/workflows/rspec.yml +44 -0
  3. data/.github/workflows/rubocop.yml +28 -0
  4. data/.github/workflows/sourcehawk-scan.yml +20 -0
  5. data/.gitignore +14 -0
  6. data/.rspec +4 -0
  7. data/.rubocop.yml +26 -0
  8. data/CHANGELOG.md +4 -0
  9. data/CODE_OF_CONDUCT.md +75 -0
  10. data/CONTRIBUTING.md +54 -0
  11. data/Gemfile +10 -0
  12. data/INDIVIDUAL_CONTRIBUTOR_LICENSE.md +30 -0
  13. data/LICENSE +201 -0
  14. data/NOTICE.txt +9 -0
  15. data/README.md +54 -0
  16. data/attribution.txt +1 -0
  17. data/config.ru +15 -0
  18. data/exe/snmp_collector +55 -0
  19. data/lib/telemetry/snmp.rb +23 -0
  20. data/lib/telemetry/snmp/api.rb +55 -0
  21. data/lib/telemetry/snmp/auth.rb +54 -0
  22. data/lib/telemetry/snmp/auth/defaults.rb +41 -0
  23. data/lib/telemetry/snmp/client.rb +104 -0
  24. data/lib/telemetry/snmp/controllers/device_creds.rb +105 -0
  25. data/lib/telemetry/snmp/controllers/devices.rb +94 -0
  26. data/lib/telemetry/snmp/controllers/oid_groups.rb +71 -0
  27. data/lib/telemetry/snmp/controllers/oids.rb +80 -0
  28. data/lib/telemetry/snmp/controllers/users.rb +81 -0
  29. data/lib/telemetry/snmp/controllers/walks.rb +89 -0
  30. data/lib/telemetry/snmp/data.rb +69 -0
  31. data/lib/telemetry/snmp/data/default_opts.rb +73 -0
  32. data/lib/telemetry/snmp/data/migrations/001_device_creds.rb +19 -0
  33. data/lib/telemetry/snmp/data/migrations/002_create_devices_table.rb +31 -0
  34. data/lib/telemetry/snmp/data/migrations/003_create_oids_tables.rb +16 -0
  35. data/lib/telemetry/snmp/data/migrations/004_create_oid_groups.rb +15 -0
  36. data/lib/telemetry/snmp/data/migrations/005_create_oids_oid_groups.rb +17 -0
  37. data/lib/telemetry/snmp/data/migrations/006_device_to_oid_group.rb +15 -0
  38. data/lib/telemetry/snmp/data/migrations/007_create_users.rb +20 -0
  39. data/lib/telemetry/snmp/data/migrations/008_create_walks_table.rb +14 -0
  40. data/lib/telemetry/snmp/data/migrations/009_create_tag_name_column.rb +7 -0
  41. data/lib/telemetry/snmp/data/migrations/010_create_user_audit_table.rb +18 -0
  42. data/lib/telemetry/snmp/data/models/device.rb +11 -0
  43. data/lib/telemetry/snmp/data/models/device_cred.rb +11 -0
  44. data/lib/telemetry/snmp/data/models/oid.rb +10 -0
  45. data/lib/telemetry/snmp/data/models/oid_group.rb +10 -0
  46. data/lib/telemetry/snmp/data/models/oid_oid_groups.rb +10 -0
  47. data/lib/telemetry/snmp/data/models/oid_walk.rb +10 -0
  48. data/lib/telemetry/snmp/data/models/user.rb +10 -0
  49. data/lib/telemetry/snmp/data/models/user_audit_log.rb +19 -0
  50. data/lib/telemetry/snmp/mibs/AGENTX-MIB.txt +527 -0
  51. data/lib/telemetry/snmp/mibs/AIRPORT-BASESTATION-3-MIB.txt +461 -0
  52. data/lib/telemetry/snmp/mibs/BRIDGE-MIB.txt +1472 -0
  53. data/lib/telemetry/snmp/mibs/DISMAN-EVENT-MIB.txt +1882 -0
  54. data/lib/telemetry/snmp/mibs/DISMAN-SCHEDULE-MIB.txt +699 -0
  55. data/lib/telemetry/snmp/mibs/DISMAN-SCRIPT-MIB.txt +1764 -0
  56. data/lib/telemetry/snmp/mibs/EtherLike-MIB.txt +1862 -0
  57. data/lib/telemetry/snmp/mibs/HCNUM-TC.txt +118 -0
  58. data/lib/telemetry/snmp/mibs/HOST-RESOURCES-MIB.txt +1540 -0
  59. data/lib/telemetry/snmp/mibs/HOST-RESOURCES-TYPES.txt +389 -0
  60. data/lib/telemetry/snmp/mibs/IANA-ADDRESS-FAMILY-NUMBERS-MIB.txt +123 -0
  61. data/lib/telemetry/snmp/mibs/IANA-LANGUAGE-MIB.txt +123 -0
  62. data/lib/telemetry/snmp/mibs/IANA-RTPROTO-MIB.txt +91 -0
  63. data/lib/telemetry/snmp/mibs/IANAifType-MIB.txt +619 -0
  64. data/lib/telemetry/snmp/mibs/IF-INVERTED-STACK-MIB.txt +149 -0
  65. data/lib/telemetry/snmp/mibs/IF-MIB.txt +1814 -0
  66. data/lib/telemetry/snmp/mibs/INET-ADDRESS-MIB.txt +402 -0
  67. data/lib/telemetry/snmp/mibs/IP-FORWARD-MIB.txt +1277 -0
  68. data/lib/telemetry/snmp/mibs/IP-MIB.txt +4993 -0
  69. data/lib/telemetry/snmp/mibs/IPV6-FLOW-LABEL-MIB.txt +58 -0
  70. data/lib/telemetry/snmp/mibs/IPV6-ICMP-MIB.txt +529 -0
  71. data/lib/telemetry/snmp/mibs/IPV6-MIB.txt +1443 -0
  72. data/lib/telemetry/snmp/mibs/IPV6-TC.txt +67 -0
  73. data/lib/telemetry/snmp/mibs/IPV6-TCP-MIB.txt +211 -0
  74. data/lib/telemetry/snmp/mibs/IPV6-UDP-MIB.txt +141 -0
  75. data/lib/telemetry/snmp/mibs/NET-SNMP-AGENT-MIB.txt +554 -0
  76. data/lib/telemetry/snmp/mibs/NET-SNMP-EXAMPLES-MIB.txt +285 -0
  77. data/lib/telemetry/snmp/mibs/NET-SNMP-EXTEND-MIB.txt +325 -0
  78. data/lib/telemetry/snmp/mibs/NET-SNMP-MIB.txt +67 -0
  79. data/lib/telemetry/snmp/mibs/NET-SNMP-PASS-MIB.txt +124 -0
  80. data/lib/telemetry/snmp/mibs/NET-SNMP-TC.txt +128 -0
  81. data/lib/telemetry/snmp/mibs/NET-SNMP-VACM-MIB.txt +154 -0
  82. data/lib/telemetry/snmp/mibs/NOTIFICATION-LOG-MIB.txt +753 -0
  83. data/lib/telemetry/snmp/mibs/PAN-COMMON-MIB.md5 +1 -0
  84. data/lib/telemetry/snmp/mibs/PAN-COMMON-MIB.my +2293 -0
  85. data/lib/telemetry/snmp/mibs/PAN-ENTITY-EXT-MIB.md5 +1 -0
  86. data/lib/telemetry/snmp/mibs/PAN-ENTITY-EXT-MIB.my +293 -0
  87. data/lib/telemetry/snmp/mibs/PAN-GLOBAL-REG-MIB.md5 +1 -0
  88. data/lib/telemetry/snmp/mibs/PAN-GLOBAL-REG-MIB.my +84 -0
  89. data/lib/telemetry/snmp/mibs/PAN-GLOBAL-TC-MIB.md5 +1 -0
  90. data/lib/telemetry/snmp/mibs/PAN-GLOBAL-TC-MIB.my +68 -0
  91. data/lib/telemetry/snmp/mibs/PAN-LC-MIB.md5 +1 -0
  92. data/lib/telemetry/snmp/mibs/PAN-LC-MIB.my +204 -0
  93. data/lib/telemetry/snmp/mibs/PAN-PRODUCT-MIB.md5 +1 -0
  94. data/lib/telemetry/snmp/mibs/PAN-PRODUCT-MIB.my +305 -0
  95. data/lib/telemetry/snmp/mibs/PAN-TRAPS.md5 +1 -0
  96. data/lib/telemetry/snmp/mibs/PAN-TRAPS.my +7809 -0
  97. data/lib/telemetry/snmp/mibs/RFC-1215.txt +38 -0
  98. data/lib/telemetry/snmp/mibs/RFC1155-SMI.txt +119 -0
  99. data/lib/telemetry/snmp/mibs/RFC1213-MIB.txt +2613 -0
  100. data/lib/telemetry/snmp/mibs/RMON-MIB.txt +3980 -0
  101. data/lib/telemetry/snmp/mibs/SCTP-MIB.txt +1342 -0
  102. data/lib/telemetry/snmp/mibs/SMUX-MIB.txt +160 -0
  103. data/lib/telemetry/snmp/mibs/SNMP-COMMUNITY-MIB.txt +429 -0
  104. data/lib/telemetry/snmp/mibs/SNMP-FRAMEWORK-MIB.txt +526 -0
  105. data/lib/telemetry/snmp/mibs/SNMP-MPD-MIB.txt +145 -0
  106. data/lib/telemetry/snmp/mibs/SNMP-NOTIFICATION-MIB.txt +589 -0
  107. data/lib/telemetry/snmp/mibs/SNMP-PROXY-MIB.txt +294 -0
  108. data/lib/telemetry/snmp/mibs/SNMP-TARGET-MIB.txt +660 -0
  109. data/lib/telemetry/snmp/mibs/SNMP-USER-BASED-SM-MIB.txt +912 -0
  110. data/lib/telemetry/snmp/mibs/SNMP-USM-AES-MIB.txt +62 -0
  111. data/lib/telemetry/snmp/mibs/SNMP-USM-DH-OBJECTS-MIB.txt +532 -0
  112. data/lib/telemetry/snmp/mibs/SNMP-VIEW-BASED-ACM-MIB.txt +830 -0
  113. data/lib/telemetry/snmp/mibs/SNMPv2-CONF.txt +322 -0
  114. data/lib/telemetry/snmp/mibs/SNMPv2-MIB.txt +854 -0
  115. data/lib/telemetry/snmp/mibs/SNMPv2-SMI.txt +344 -0
  116. data/lib/telemetry/snmp/mibs/SNMPv2-TC.txt +772 -0
  117. data/lib/telemetry/snmp/mibs/SNMPv2-TM.txt +176 -0
  118. data/lib/telemetry/snmp/mibs/TCP-MIB.txt +785 -0
  119. data/lib/telemetry/snmp/mibs/TRANSPORT-ADDRESS-MIB.txt +421 -0
  120. data/lib/telemetry/snmp/mibs/TUNNEL-MIB.txt +738 -0
  121. data/lib/telemetry/snmp/mibs/UCD-DEMO-MIB.txt +74 -0
  122. data/lib/telemetry/snmp/mibs/UCD-DISKIO-MIB.txt +171 -0
  123. data/lib/telemetry/snmp/mibs/UCD-DLMOD-MIB.txt +124 -0
  124. data/lib/telemetry/snmp/mibs/UCD-IPFWACC-MIB.txt +327 -0
  125. data/lib/telemetry/snmp/mibs/UCD-SNMP-MIB.txt +1712 -0
  126. data/lib/telemetry/snmp/mibs/UDP-MIB.txt +549 -0
  127. data/lib/telemetry/snmp/publisher.rb +130 -0
  128. data/lib/telemetry/snmp/version.rb +7 -0
  129. data/sourcehawk.yml +4 -0
  130. data/telemetry-snmp.gemspec +48 -0
  131. metadata +456 -0
@@ -0,0 +1,38 @@
1
+
2
+ RFC-1215 DEFINITIONS ::= BEGIN
3
+
4
+ -- This module is a empty module. It has been created solely for the
5
+ -- purpose of allowing other modules to correctly import the TRAP-TYPE
6
+ -- clause from RFC-1215 where it should be imported from. It's a
7
+ -- built in type in the UCD-SNMP code, and in fact RFC-1215 doesn't
8
+ -- actually define a mib at all; it only defines macros. However,
9
+ -- importing the TRAP-TYPE is conventionally done from an import
10
+ -- clause pointing to RFC-1215.
11
+ --
12
+ -- Wes 7/17/98
13
+
14
+ TRAP-TYPE MACRO ::=
15
+ BEGIN
16
+ TYPE NOTATION ::= "ENTERPRISE" value
17
+ (enterprise OBJECT IDENTIFIER)
18
+ VarPart
19
+ DescrPart
20
+ ReferPart
21
+ VALUE NOTATION ::= value (VALUE INTEGER)
22
+ VarPart ::=
23
+ "VARIABLES" "{" VarTypes "}"
24
+ | empty
25
+ VarTypes ::=
26
+ VarType | VarTypes "," VarType
27
+ VarType ::=
28
+ value (vartype ObjectName)
29
+ DescrPart ::=
30
+ "DESCRIPTION" value (description DisplayString)
31
+ | empty
32
+ ReferPart ::=
33
+ "REFERENCE" value (reference DisplayString)
34
+ | empty
35
+ END
36
+
37
+
38
+ END
@@ -0,0 +1,119 @@
1
+ RFC1155-SMI DEFINITIONS ::= BEGIN
2
+
3
+ EXPORTS -- EVERYTHING
4
+ internet, directory, mgmt,
5
+ experimental, private, enterprises,
6
+ OBJECT-TYPE, ObjectName, ObjectSyntax, SimpleSyntax,
7
+ ApplicationSyntax, NetworkAddress, IpAddress,
8
+ Counter, Gauge, TimeTicks, Opaque;
9
+
10
+ -- the path to the root
11
+
12
+ internet OBJECT IDENTIFIER ::= { iso org(3) dod(6) 1 }
13
+
14
+ directory OBJECT IDENTIFIER ::= { internet 1 }
15
+
16
+ mgmt OBJECT IDENTIFIER ::= { internet 2 }
17
+
18
+ experimental OBJECT IDENTIFIER ::= { internet 3 }
19
+
20
+ private OBJECT IDENTIFIER ::= { internet 4 }
21
+ enterprises OBJECT IDENTIFIER ::= { private 1 }
22
+
23
+ -- definition of object types
24
+
25
+ OBJECT-TYPE MACRO ::=
26
+ BEGIN
27
+ TYPE NOTATION ::= "SYNTAX" type (TYPE ObjectSyntax)
28
+ "ACCESS" Access
29
+ "STATUS" Status
30
+ VALUE NOTATION ::= value (VALUE ObjectName)
31
+
32
+ Access ::= "read-only"
33
+ | "read-write"
34
+ | "write-only"
35
+ | "not-accessible"
36
+ Status ::= "mandatory"
37
+ | "optional"
38
+ | "obsolete"
39
+ END
40
+
41
+ -- names of objects in the MIB
42
+
43
+ ObjectName ::=
44
+ OBJECT IDENTIFIER
45
+
46
+ -- syntax of objects in the MIB
47
+
48
+ ObjectSyntax ::=
49
+ CHOICE {
50
+ simple
51
+ SimpleSyntax,
52
+ -- note that simple SEQUENCEs are not directly
53
+ -- mentioned here to keep things simple (i.e.,
54
+ -- prevent mis-use). However, application-wide
55
+ -- types which are IMPLICITly encoded simple
56
+ -- SEQUENCEs may appear in the following CHOICE
57
+
58
+ application-wide
59
+ ApplicationSyntax
60
+ }
61
+
62
+ SimpleSyntax ::=
63
+ CHOICE {
64
+ number
65
+ INTEGER,
66
+ string
67
+ OCTET STRING,
68
+ object
69
+ OBJECT IDENTIFIER,
70
+ empty
71
+ NULL
72
+ }
73
+
74
+ ApplicationSyntax ::=
75
+ CHOICE {
76
+ address
77
+ NetworkAddress,
78
+ counter
79
+ Counter,
80
+ gauge
81
+ Gauge,
82
+ ticks
83
+ TimeTicks,
84
+ arbitrary
85
+ Opaque
86
+
87
+ -- other application-wide types, as they are
88
+ -- defined, will be added here
89
+ }
90
+
91
+ -- application-wide types
92
+
93
+ NetworkAddress ::=
94
+ CHOICE {
95
+ internet
96
+ IpAddress
97
+ }
98
+
99
+ IpAddress ::=
100
+ [APPLICATION 0] -- in network-byte order
101
+ IMPLICIT OCTET STRING (SIZE (4))
102
+
103
+ Counter ::=
104
+ [APPLICATION 1]
105
+ IMPLICIT INTEGER (0..4294967295)
106
+
107
+ Gauge ::=
108
+ [APPLICATION 2]
109
+ IMPLICIT INTEGER (0..4294967295)
110
+
111
+ TimeTicks ::=
112
+ [APPLICATION 3]
113
+ IMPLICIT INTEGER (0..4294967295)
114
+
115
+ Opaque ::=
116
+ [APPLICATION 4] -- arbitrary ASN.1 value,
117
+ IMPLICIT OCTET STRING -- "double-wrapped"
118
+
119
+ END
@@ -0,0 +1,2613 @@
1
+ RFC1213-MIB DEFINITIONS ::= BEGIN
2
+
3
+ IMPORTS
4
+ mgmt, NetworkAddress, IpAddress, Counter, Gauge,
5
+ TimeTicks
6
+ FROM RFC1155-SMI
7
+ OBJECT-TYPE
8
+ FROM RFC-1212;
9
+
10
+ -- This MIB module uses the extended OBJECT-TYPE macro as
11
+ -- defined in [14];
12
+
13
+ -- MIB-II (same prefix as MIB-I)
14
+
15
+ mib-2 OBJECT IDENTIFIER ::= { mgmt 1 }
16
+
17
+ -- textual conventions
18
+
19
+ DisplayString ::=
20
+ OCTET STRING
21
+ -- This data type is used to model textual information taken
22
+ -- from the NVT ASCII character set. By convention, objects
23
+ -- with this syntax are declared as having
24
+
25
+ --
26
+ -- SIZE (0..255)
27
+
28
+ PhysAddress ::=
29
+ OCTET STRING
30
+ -- This data type is used to model media addresses. For many
31
+ -- types of media, this will be in a binary representation.
32
+ -- For example, an ethernet address would be represented as
33
+ -- a string of 6 octets.
34
+
35
+ -- groups in MIB-II
36
+
37
+ system OBJECT IDENTIFIER ::= { mib-2 1 }
38
+
39
+ interfaces OBJECT IDENTIFIER ::= { mib-2 2 }
40
+
41
+ at OBJECT IDENTIFIER ::= { mib-2 3 }
42
+
43
+ ip OBJECT IDENTIFIER ::= { mib-2 4 }
44
+
45
+ icmp OBJECT IDENTIFIER ::= { mib-2 5 }
46
+
47
+ tcp OBJECT IDENTIFIER ::= { mib-2 6 }
48
+
49
+ udp OBJECT IDENTIFIER ::= { mib-2 7 }
50
+
51
+ egp OBJECT IDENTIFIER ::= { mib-2 8 }
52
+
53
+ -- historical (some say hysterical)
54
+ -- cmot OBJECT IDENTIFIER ::= { mib-2 9 }
55
+
56
+ transmission OBJECT IDENTIFIER ::= { mib-2 10 }
57
+
58
+ snmp OBJECT IDENTIFIER ::= { mib-2 11 }
59
+
60
+ -- the System group
61
+
62
+ -- Implementation of the System group is mandatory for all
63
+ -- systems. If an agent is not configured to have a value
64
+ -- for any of these variables, a string of length 0 is
65
+ -- returned.
66
+
67
+ sysDescr OBJECT-TYPE
68
+ SYNTAX DisplayString (SIZE (0..255))
69
+ ACCESS read-only
70
+ STATUS mandatory
71
+ DESCRIPTION
72
+ "A textual description of the entity. This value
73
+ should include the full name and version
74
+ identification of the system's hardware type,
75
+ software operating-system, and networking
76
+ software. It is mandatory that this only contain
77
+ printable ASCII characters."
78
+ ::= { system 1 }
79
+
80
+ sysObjectID OBJECT-TYPE
81
+ SYNTAX OBJECT IDENTIFIER
82
+ ACCESS read-only
83
+ STATUS mandatory
84
+ DESCRIPTION
85
+ "The vendor's authoritative identification of the
86
+ network management subsystem contained in the
87
+ entity. This value is allocated within the SMI
88
+ enterprises subtree (1.3.6.1.4.1) and provides an
89
+ easy and unambiguous means for determining `what
90
+ kind of box' is being managed. For example, if
91
+ vendor `Flintstones, Inc.' was assigned the
92
+ subtree 1.3.6.1.4.1.4242, it could assign the
93
+ identifier 1.3.6.1.4.1.4242.1.1 to its `Fred
94
+ Router'."
95
+ ::= { system 2 }
96
+
97
+ sysUpTime OBJECT-TYPE
98
+ SYNTAX TimeTicks
99
+ ACCESS read-only
100
+ STATUS mandatory
101
+ DESCRIPTION
102
+ "The time (in hundredths of a second) since the
103
+ network management portion of the system was last
104
+ re-initialized."
105
+ ::= { system 3 }
106
+
107
+ sysContact OBJECT-TYPE
108
+ SYNTAX DisplayString (SIZE (0..255))
109
+ ACCESS read-write
110
+ STATUS mandatory
111
+ DESCRIPTION
112
+ "The textual identification of the contact person
113
+ for this managed node, together with information
114
+ on how to contact this person."
115
+ ::= { system 4 }
116
+
117
+ sysName OBJECT-TYPE
118
+ SYNTAX DisplayString (SIZE (0..255))
119
+ ACCESS read-write
120
+ STATUS mandatory
121
+ DESCRIPTION
122
+ "An administratively-assigned name for this
123
+ managed node. By convention, this is the node's
124
+ fully-qualified domain name."
125
+ ::= { system 5 }
126
+
127
+ sysLocation OBJECT-TYPE
128
+ SYNTAX DisplayString (SIZE (0..255))
129
+ ACCESS read-write
130
+ STATUS mandatory
131
+ DESCRIPTION
132
+ "The physical location of this node (e.g.,
133
+ `telephone closet, 3rd floor')."
134
+ ::= { system 6 }
135
+
136
+ sysServices OBJECT-TYPE
137
+ SYNTAX INTEGER (0..127)
138
+ ACCESS read-only
139
+ STATUS mandatory
140
+ DESCRIPTION
141
+ "A value which indicates the set of services that
142
+ this entity primarily offers.
143
+
144
+ The value is a sum. This sum initially takes the
145
+ value zero, Then, for each layer, L, in the range
146
+ 1 through 7, that this node performs transactions
147
+ for, 2 raised to (L - 1) is added to the sum. For
148
+ example, a node which performs primarily routing
149
+ functions would have a value of 4 (2^(3-1)). In
150
+ contrast, a node which is a host offering
151
+ application services would have a value of 72
152
+ (2^(4-1) + 2^(7-1)). Note that in the context of
153
+ the Internet suite of protocols, values should be
154
+ calculated accordingly:
155
+
156
+ layer functionality
157
+ 1 physical (e.g., repeaters)
158
+ 2 datalink/subnetwork (e.g., bridges)
159
+ 3 internet (e.g., IP gateways)
160
+ 4 end-to-end (e.g., IP hosts)
161
+ 7 applications (e.g., mail relays)
162
+
163
+ For systems including OSI protocols, layers 5 and
164
+ 6 may also be counted."
165
+ ::= { system 7 }
166
+
167
+ -- the Interfaces group
168
+
169
+ -- Implementation of the Interfaces group is mandatory for
170
+ -- all systems.
171
+
172
+ ifNumber OBJECT-TYPE
173
+ SYNTAX INTEGER
174
+ ACCESS read-only
175
+ STATUS mandatory
176
+ DESCRIPTION
177
+ "The number of network interfaces (regardless of
178
+ their current state) present on this system."
179
+ ::= { interfaces 1 }
180
+
181
+ -- the Interfaces table
182
+
183
+ -- The Interfaces table contains information on the entity's
184
+ -- interfaces. Each interface is thought of as being
185
+ -- attached to a `subnetwork'. Note that this term should
186
+ -- not be confused with `subnet' which refers to an
187
+ -- addressing partitioning scheme used in the Internet suite
188
+ -- of protocols.
189
+
190
+ ifTable OBJECT-TYPE
191
+ SYNTAX SEQUENCE OF IfEntry
192
+ ACCESS not-accessible
193
+ STATUS mandatory
194
+ DESCRIPTION
195
+ "A list of interface entries. The number of
196
+ entries is given by the value of ifNumber."
197
+ ::= { interfaces 2 }
198
+
199
+ ifEntry OBJECT-TYPE
200
+ SYNTAX IfEntry
201
+ ACCESS not-accessible
202
+ STATUS mandatory
203
+ DESCRIPTION
204
+ "An interface entry containing objects at the
205
+ subnetwork layer and below for a particular
206
+ interface."
207
+ INDEX { ifIndex }
208
+ ::= { ifTable 1 }
209
+
210
+ IfEntry ::=
211
+ SEQUENCE {
212
+ ifIndex
213
+ INTEGER,
214
+ ifDescr
215
+ DisplayString,
216
+ ifType
217
+ INTEGER,
218
+ ifMtu
219
+ INTEGER,
220
+ ifSpeed
221
+ Gauge,
222
+ ifPhysAddress
223
+ PhysAddress,
224
+ ifAdminStatus
225
+ INTEGER,
226
+ ifOperStatus
227
+ INTEGER,
228
+ ifLastChange
229
+ TimeTicks,
230
+ ifInOctets
231
+ Counter,
232
+ ifInUcastPkts
233
+ Counter,
234
+ ifInNUcastPkts
235
+ Counter,
236
+ ifInDiscards
237
+ Counter,
238
+ ifInErrors
239
+ Counter,
240
+ ifInUnknownProtos
241
+ Counter,
242
+ ifOutOctets
243
+ Counter,
244
+ ifOutUcastPkts
245
+ Counter,
246
+ ifOutNUcastPkts
247
+ Counter,
248
+ ifOutDiscards
249
+ Counter,
250
+ ifOutErrors
251
+ Counter,
252
+ ifOutQLen
253
+ Gauge,
254
+ ifSpecific
255
+ OBJECT IDENTIFIER
256
+ }
257
+
258
+ ifIndex OBJECT-TYPE
259
+ SYNTAX INTEGER
260
+ ACCESS read-only
261
+ STATUS mandatory
262
+ DESCRIPTION
263
+ "A unique value for each interface. Its value
264
+ ranges between 1 and the value of ifNumber. The
265
+ value for each interface must remain constant at
266
+ least from one re-initialization of the entity's
267
+ network management system to the next re-
268
+ initialization."
269
+ ::= { ifEntry 1 }
270
+
271
+ ifDescr OBJECT-TYPE
272
+ SYNTAX DisplayString (SIZE (0..255))
273
+ ACCESS read-only
274
+ STATUS mandatory
275
+ DESCRIPTION
276
+ "A textual string containing information about the
277
+ interface. This string should include the name of
278
+ the manufacturer, the product name and the version
279
+ of the hardware interface."
280
+ ::= { ifEntry 2 }
281
+
282
+ ifType OBJECT-TYPE
283
+ SYNTAX INTEGER {
284
+ other(1), -- none of the following
285
+ regular1822(2),
286
+ hdh1822(3),
287
+ ddn-x25(4),
288
+ rfc877-x25(5),
289
+ ethernet-csmacd(6),
290
+ iso88023-csmacd(7),
291
+ iso88024-tokenBus(8),
292
+ iso88025-tokenRing(9),
293
+ iso88026-man(10),
294
+ starLan(11),
295
+ proteon-10Mbit(12),
296
+ proteon-80Mbit(13),
297
+ hyperchannel(14),
298
+ fddi(15),
299
+ lapb(16),
300
+ sdlc(17),
301
+ ds1(18), -- T-1
302
+ e1(19), -- european equiv. of T-1
303
+ basicISDN(20),
304
+ primaryISDN(21), -- proprietary serial
305
+ propPointToPointSerial(22),
306
+ ppp(23),
307
+ softwareLoopback(24),
308
+ eon(25), -- CLNP over IP [11]
309
+ ethernet-3Mbit(26),
310
+ nsip(27), -- XNS over IP
311
+ slip(28), -- generic SLIP
312
+ ultra(29), -- ULTRA technologies
313
+ ds3(30), -- T-3
314
+ sip(31), -- SMDS
315
+ frame-relay(32)
316
+ }
317
+ ACCESS read-only
318
+ STATUS mandatory
319
+ DESCRIPTION
320
+ "The type of interface, distinguished according to
321
+ the physical/link protocol(s) immediately `below'
322
+ the network layer in the protocol stack."
323
+ ::= { ifEntry 3 }
324
+
325
+ ifMtu OBJECT-TYPE
326
+ SYNTAX INTEGER
327
+ ACCESS read-only
328
+ STATUS mandatory
329
+ DESCRIPTION
330
+ "The size of the largest datagram which can be
331
+ sent/received on the interface, specified in
332
+ octets. For interfaces that are used for
333
+ transmitting network datagrams, this is the size
334
+ of the largest network datagram that can be sent
335
+ on the interface."
336
+ ::= { ifEntry 4 }
337
+
338
+ ifSpeed OBJECT-TYPE
339
+ SYNTAX Gauge
340
+ ACCESS read-only
341
+ STATUS mandatory
342
+ DESCRIPTION
343
+ "An estimate of the interface's current bandwidth
344
+ in bits per second. For interfaces which do not
345
+ vary in bandwidth or for those where no accurate
346
+ estimation can be made, this object should contain
347
+ the nominal bandwidth."
348
+ ::= { ifEntry 5 }
349
+
350
+ ifPhysAddress OBJECT-TYPE
351
+ SYNTAX PhysAddress
352
+ ACCESS read-only
353
+ STATUS mandatory
354
+ DESCRIPTION
355
+ "The interface's address at the protocol layer
356
+ immediately `below' the network layer in the
357
+ protocol stack. For interfaces which do not have
358
+
359
+ such an address (e.g., a serial line), this object
360
+ should contain an octet string of zero length."
361
+ ::= { ifEntry 6 }
362
+
363
+ ifAdminStatus OBJECT-TYPE
364
+ SYNTAX INTEGER {
365
+ up(1), -- ready to pass packets
366
+ down(2),
367
+ testing(3) -- in some test mode
368
+ }
369
+ ACCESS read-write
370
+ STATUS mandatory
371
+ DESCRIPTION
372
+ "The desired state of the interface. The
373
+ testing(3) state indicates that no operational
374
+ packets can be passed."
375
+ ::= { ifEntry 7 }
376
+
377
+ ifOperStatus OBJECT-TYPE
378
+ SYNTAX INTEGER {
379
+ up(1), -- ready to pass packets
380
+ down(2),
381
+ testing(3) -- in some test mode
382
+ }
383
+ ACCESS read-only
384
+ STATUS mandatory
385
+ DESCRIPTION
386
+ "The current operational state of the interface.
387
+ The testing(3) state indicates that no operational
388
+ packets can be passed."
389
+ ::= { ifEntry 8 }
390
+
391
+ ifLastChange OBJECT-TYPE
392
+ SYNTAX TimeTicks
393
+ ACCESS read-only
394
+ STATUS mandatory
395
+ DESCRIPTION
396
+ "The value of sysUpTime at the time the interface
397
+ entered its current operational state. If the
398
+ current state was entered prior to the last re-
399
+ initialization of the local network management
400
+ subsystem, then this object contains a zero
401
+ value."
402
+ ::= { ifEntry 9 }
403
+
404
+ ifInOctets OBJECT-TYPE
405
+ SYNTAX Counter
406
+ ACCESS read-only
407
+ STATUS mandatory
408
+ DESCRIPTION
409
+ "The total number of octets received on the
410
+ interface, including framing characters."
411
+ ::= { ifEntry 10 }
412
+
413
+ ifInUcastPkts OBJECT-TYPE
414
+ SYNTAX Counter
415
+ ACCESS read-only
416
+ STATUS mandatory
417
+ DESCRIPTION
418
+ "The number of subnetwork-unicast packets
419
+ delivered to a higher-layer protocol."
420
+ ::= { ifEntry 11 }
421
+
422
+ ifInNUcastPkts OBJECT-TYPE
423
+ SYNTAX Counter
424
+ ACCESS read-only
425
+ STATUS mandatory
426
+ DESCRIPTION
427
+ "The number of non-unicast (i.e., subnetwork-
428
+ broadcast or subnetwork-multicast) packets
429
+ delivered to a higher-layer protocol."
430
+ ::= { ifEntry 12 }
431
+
432
+ ifInDiscards OBJECT-TYPE
433
+ SYNTAX Counter
434
+ ACCESS read-only
435
+ STATUS mandatory
436
+ DESCRIPTION
437
+ "The number of inbound packets which were chosen
438
+ to be discarded even though no errors had been
439
+ detected to prevent their being deliverable to a
440
+ higher-layer protocol. One possible reason for
441
+ discarding such a packet could be to free up
442
+ buffer space."
443
+ ::= { ifEntry 13 }
444
+
445
+ ifInErrors OBJECT-TYPE
446
+ SYNTAX Counter
447
+ ACCESS read-only
448
+ STATUS mandatory
449
+ DESCRIPTION
450
+ "The number of inbound packets that contained
451
+ errors preventing them from being deliverable to a
452
+ higher-layer protocol."
453
+ ::= { ifEntry 14 }
454
+
455
+ ifInUnknownProtos OBJECT-TYPE
456
+ SYNTAX Counter
457
+ ACCESS read-only
458
+ STATUS mandatory
459
+ DESCRIPTION
460
+ "The number of packets received via the interface
461
+ which were discarded because of an unknown or
462
+ unsupported protocol."
463
+ ::= { ifEntry 15 }
464
+
465
+ ifOutOctets OBJECT-TYPE
466
+ SYNTAX Counter
467
+ ACCESS read-only
468
+ STATUS mandatory
469
+ DESCRIPTION
470
+ "The total number of octets transmitted out of the
471
+ interface, including framing characters."
472
+ ::= { ifEntry 16 }
473
+
474
+ ifOutUcastPkts OBJECT-TYPE
475
+ SYNTAX Counter
476
+ ACCESS read-only
477
+ STATUS mandatory
478
+ DESCRIPTION
479
+ "The total number of packets that higher-level
480
+ protocols requested be transmitted to a
481
+ subnetwork-unicast address, including those that
482
+ were discarded or not sent."
483
+ ::= { ifEntry 17 }
484
+
485
+ ifOutNUcastPkts OBJECT-TYPE
486
+ SYNTAX Counter
487
+ ACCESS read-only
488
+ STATUS mandatory
489
+ DESCRIPTION
490
+ "The total number of packets that higher-level
491
+ protocols requested be transmitted to a non-
492
+ unicast (i.e., a subnetwork-broadcast or
493
+ subnetwork-multicast) address, including those
494
+ that were discarded or not sent."
495
+ ::= { ifEntry 18 }
496
+
497
+ ifOutDiscards OBJECT-TYPE
498
+ SYNTAX Counter
499
+ ACCESS read-only
500
+ STATUS mandatory
501
+ DESCRIPTION
502
+ "The number of outbound packets which were chosen
503
+
504
+ to be discarded even though no errors had been
505
+ detected to prevent their being transmitted. One
506
+ possible reason for discarding such a packet could
507
+ be to free up buffer space."
508
+ ::= { ifEntry 19 }
509
+
510
+ ifOutErrors OBJECT-TYPE
511
+ SYNTAX Counter
512
+ ACCESS read-only
513
+ STATUS mandatory
514
+ DESCRIPTION
515
+ "The number of outbound packets that could not be
516
+ transmitted because of errors."
517
+ ::= { ifEntry 20 }
518
+
519
+ ifOutQLen OBJECT-TYPE
520
+ SYNTAX Gauge
521
+ ACCESS read-only
522
+ STATUS mandatory
523
+ DESCRIPTION
524
+ "The length of the output packet queue (in
525
+ packets)."
526
+ ::= { ifEntry 21 }
527
+
528
+ ifSpecific OBJECT-TYPE
529
+ SYNTAX OBJECT IDENTIFIER
530
+ ACCESS read-only
531
+ STATUS mandatory
532
+ DESCRIPTION
533
+ "A reference to MIB definitions specific to the
534
+ particular media being used to realize the
535
+ interface. For example, if the interface is
536
+ realized by an ethernet, then the value of this
537
+ object refers to a document defining objects
538
+ specific to ethernet. If this information is not
539
+ present, its value should be set to the OBJECT
540
+ IDENTIFIER { 0 0 }, which is a syntatically valid
541
+ object identifier, and any conformant
542
+ implementation of ASN.1 and BER must be able to
543
+ generate and recognize this value."
544
+ ::= { ifEntry 22 }
545
+
546
+ -- the Address Translation group
547
+
548
+ -- Implementation of the Address Translation group is
549
+ -- mandatory for all systems. Note however that this group
550
+ -- is deprecated by MIB-II. That is, it is being included
551
+
552
+ -- solely for compatibility with MIB-I nodes, and will most
553
+ -- likely be excluded from MIB-III nodes. From MIB-II and
554
+ -- onwards, each network protocol group contains its own
555
+ -- address translation tables.
556
+
557
+ -- The Address Translation group contains one table which is
558
+ -- the union across all interfaces of the translation tables
559
+ -- for converting a NetworkAddress (e.g., an IP address) into
560
+ -- a subnetwork-specific address. For lack of a better term,
561
+ -- this document refers to such a subnetwork-specific address
562
+ -- as a `physical' address.
563
+
564
+ -- Examples of such translation tables are: for broadcast
565
+ -- media where ARP is in use, the translation table is
566
+ -- equivalent to the ARP cache; or, on an X.25 network where
567
+ -- non-algorithmic translation to X.121 addresses is
568
+ -- required, the translation table contains the
569
+ -- NetworkAddress to X.121 address equivalences.
570
+
571
+ atTable OBJECT-TYPE
572
+ SYNTAX SEQUENCE OF AtEntry
573
+ ACCESS not-accessible
574
+ STATUS deprecated
575
+ DESCRIPTION
576
+ "The Address Translation tables contain the
577
+ NetworkAddress to `physical' address equivalences.
578
+ Some interfaces do not use translation tables for
579
+ determining address equivalences (e.g., DDN-X.25
580
+ has an algorithmic method); if all interfaces are
581
+ of this type, then the Address Translation table
582
+ is empty, i.e., has zero entries."
583
+ ::= { at 1 }
584
+
585
+ atEntry OBJECT-TYPE
586
+ SYNTAX AtEntry
587
+ ACCESS not-accessible
588
+ STATUS deprecated
589
+ DESCRIPTION
590
+ "Each entry contains one NetworkAddress to
591
+ `physical' address equivalence."
592
+ INDEX { atIfIndex,
593
+ atNetAddress }
594
+ ::= { atTable 1 }
595
+
596
+ AtEntry ::=
597
+ SEQUENCE {
598
+ atIfIndex
599
+ INTEGER,
600
+ atPhysAddress
601
+ PhysAddress,
602
+ atNetAddress
603
+ NetworkAddress
604
+ }
605
+
606
+ atIfIndex OBJECT-TYPE
607
+ SYNTAX INTEGER
608
+ ACCESS read-write
609
+ STATUS deprecated
610
+ DESCRIPTION
611
+ "The interface on which this entry's equivalence
612
+ is effective. The interface identified by a
613
+ particular value of this index is the same
614
+ interface as identified by the same value of
615
+ ifIndex."
616
+ ::= { atEntry 1 }
617
+
618
+ atPhysAddress OBJECT-TYPE
619
+ SYNTAX PhysAddress
620
+ ACCESS read-write
621
+ STATUS deprecated
622
+ DESCRIPTION
623
+ "The media-dependent `physical' address.
624
+
625
+ Setting this object to a null string (one of zero
626
+ length) has the effect of invaliding the
627
+ corresponding entry in the atTable object. That
628
+ is, it effectively dissasociates the interface
629
+ identified with said entry from the mapping
630
+ identified with said entry. It is an
631
+ implementation-specific matter as to whether the
632
+ agent removes an invalidated entry from the table.
633
+ Accordingly, management stations must be prepared
634
+ to receive tabular information from agents that
635
+ corresponds to entries not currently in use.
636
+ Proper interpretation of such entries requires
637
+ examination of the relevant atPhysAddress object."
638
+ ::= { atEntry 2 }
639
+
640
+ atNetAddress OBJECT-TYPE
641
+ SYNTAX NetworkAddress
642
+ ACCESS read-write
643
+ STATUS deprecated
644
+ DESCRIPTION
645
+ "The NetworkAddress (e.g., the IP address)
646
+ corresponding to the media-dependent `physical'
647
+ address."
648
+ ::= { atEntry 3 }
649
+
650
+ -- the IP group
651
+
652
+ -- Implementation of the IP group is mandatory for all
653
+ -- systems.
654
+
655
+ ipForwarding OBJECT-TYPE
656
+ SYNTAX INTEGER {
657
+ forwarding(1), -- acting as a gateway
658
+ not-forwarding(2) -- NOT acting as a gateway
659
+ }
660
+ ACCESS read-write
661
+ STATUS mandatory
662
+ DESCRIPTION
663
+ "The indication of whether this entity is acting
664
+ as an IP gateway in respect to the forwarding of
665
+ datagrams received by, but not addressed to, this
666
+ entity. IP gateways forward datagrams. IP hosts
667
+ do not (except those source-routed via the host).
668
+
669
+ Note that for some managed nodes, this object may
670
+ take on only a subset of the values possible.
671
+ Accordingly, it is appropriate for an agent to
672
+ return a `badValue' response if a management
673
+ station attempts to change this object to an
674
+ inappropriate value."
675
+ ::= { ip 1 }
676
+
677
+ ipDefaultTTL OBJECT-TYPE
678
+ SYNTAX INTEGER
679
+ ACCESS read-write
680
+ STATUS mandatory
681
+ DESCRIPTION
682
+ "The default value inserted into the Time-To-Live
683
+ field of the IP header of datagrams originated at
684
+ this entity, whenever a TTL value is not supplied
685
+ by the transport layer protocol."
686
+ ::= { ip 2 }
687
+
688
+ ipInReceives OBJECT-TYPE
689
+ SYNTAX Counter
690
+ ACCESS read-only
691
+ STATUS mandatory
692
+ DESCRIPTION
693
+ "The total number of input datagrams received from
694
+ interfaces, including those received in error."
695
+ ::= { ip 3 }
696
+
697
+ ipInHdrErrors OBJECT-TYPE
698
+ SYNTAX Counter
699
+ ACCESS read-only
700
+ STATUS mandatory
701
+ DESCRIPTION
702
+ "The number of input datagrams discarded due to
703
+ errors in their IP headers, including bad
704
+ checksums, version number mismatch, other format
705
+ errors, time-to-live exceeded, errors discovered
706
+ in processing their IP options, etc."
707
+ ::= { ip 4 }
708
+
709
+ ipInAddrErrors OBJECT-TYPE
710
+ SYNTAX Counter
711
+ ACCESS read-only
712
+ STATUS mandatory
713
+ DESCRIPTION
714
+ "The number of input datagrams discarded because
715
+ the IP address in their IP header's destination
716
+ field was not a valid address to be received at
717
+ this entity. This count includes invalid
718
+ addresses (e.g., 0.0.0.0) and addresses of
719
+ unsupported Classes (e.g., Class E). For entities
720
+ which are not IP Gateways and therefore do not
721
+ forward datagrams, this counter includes datagrams
722
+ discarded because the destination address was not
723
+ a local address."
724
+ ::= { ip 5 }
725
+
726
+ ipForwDatagrams OBJECT-TYPE
727
+ SYNTAX Counter
728
+ ACCESS read-only
729
+ STATUS mandatory
730
+ DESCRIPTION
731
+ "The number of input datagrams for which this
732
+ entity was not their final IP destination, as a
733
+ result of which an attempt was made to find a
734
+ route to forward them to that final destination.
735
+ In entities which do not act as IP Gateways, this
736
+ counter will include only those packets which were
737
+ Source-Routed via this entity, and the Source-
738
+ Route option processing was successful."
739
+ ::= { ip 6 }
740
+
741
+ ipInUnknownProtos OBJECT-TYPE
742
+ SYNTAX Counter
743
+ ACCESS read-only
744
+ STATUS mandatory
745
+ DESCRIPTION
746
+ "The number of locally-addressed datagrams
747
+ received successfully but discarded because of an
748
+ unknown or unsupported protocol."
749
+ ::= { ip 7 }
750
+
751
+ ipInDiscards OBJECT-TYPE
752
+ SYNTAX Counter
753
+ ACCESS read-only
754
+ STATUS mandatory
755
+ DESCRIPTION
756
+ "The number of input IP datagrams for which no
757
+ problems were encountered to prevent their
758
+ continued processing, but which were discarded
759
+ (e.g., for lack of buffer space). Note that this
760
+ counter does not include any datagrams discarded
761
+ while awaiting re-assembly."
762
+ ::= { ip 8 }
763
+
764
+ ipInDelivers OBJECT-TYPE
765
+ SYNTAX Counter
766
+ ACCESS read-only
767
+ STATUS mandatory
768
+ DESCRIPTION
769
+ "The total number of input datagrams successfully
770
+ delivered to IP user-protocols (including ICMP)."
771
+ ::= { ip 9 }
772
+
773
+ ipOutRequests OBJECT-TYPE
774
+ SYNTAX Counter
775
+ ACCESS read-only
776
+ STATUS mandatory
777
+ DESCRIPTION
778
+ "The total number of IP datagrams which local IP
779
+ user-protocols (including ICMP) supplied to IP in
780
+ requests for transmission. Note that this counter
781
+ does not include any datagrams counted in
782
+ ipForwDatagrams."
783
+ ::= { ip 10 }
784
+
785
+ ipOutDiscards OBJECT-TYPE
786
+ SYNTAX Counter
787
+ ACCESS read-only
788
+ STATUS mandatory
789
+ DESCRIPTION
790
+ "The number of output IP datagrams for which no
791
+
792
+ problem was encountered to prevent their
793
+ transmission to their destination, but which were
794
+ discarded (e.g., for lack of buffer space). Note
795
+ that this counter would include datagrams counted
796
+ in ipForwDatagrams if any such packets met this
797
+ (discretionary) discard criterion."
798
+ ::= { ip 11 }
799
+
800
+ ipOutNoRoutes OBJECT-TYPE
801
+ SYNTAX Counter
802
+ ACCESS read-only
803
+ STATUS mandatory
804
+ DESCRIPTION
805
+ "The number of IP datagrams discarded because no
806
+ route could be found to transmit them to their
807
+ destination. Note that this counter includes any
808
+ packets counted in ipForwDatagrams which meet this
809
+ `no-route' criterion. Note that this includes any
810
+ datagarms which a host cannot route because all of
811
+ its default gateways are down."
812
+ ::= { ip 12 }
813
+
814
+ ipReasmTimeout OBJECT-TYPE
815
+ SYNTAX INTEGER
816
+ ACCESS read-only
817
+ STATUS mandatory
818
+ DESCRIPTION
819
+ "The maximum number of seconds which received
820
+ fragments are held while they are awaiting
821
+ reassembly at this entity."
822
+ ::= { ip 13 }
823
+
824
+ ipReasmReqds OBJECT-TYPE
825
+ SYNTAX Counter
826
+ ACCESS read-only
827
+ STATUS mandatory
828
+ DESCRIPTION
829
+ "The number of IP fragments received which needed
830
+ to be reassembled at this entity."
831
+ ::= { ip 14 }
832
+
833
+ ipReasmOKs OBJECT-TYPE
834
+ SYNTAX Counter
835
+ ACCESS read-only
836
+ STATUS mandatory
837
+ DESCRIPTION
838
+ "The number of IP datagrams successfully re-
839
+ assembled."
840
+ ::= { ip 15 }
841
+
842
+ ipReasmFails OBJECT-TYPE
843
+ SYNTAX Counter
844
+ ACCESS read-only
845
+ STATUS mandatory
846
+ DESCRIPTION
847
+ "The number of failures detected by the IP re-
848
+ assembly algorithm (for whatever reason: timed
849
+ out, errors, etc). Note that this is not
850
+ necessarily a count of discarded IP fragments
851
+ since some algorithms (notably the algorithm in
852
+ RFC 815) can lose track of the number of fragments
853
+ by combining them as they are received."
854
+ ::= { ip 16 }
855
+
856
+ ipFragOKs OBJECT-TYPE
857
+ SYNTAX Counter
858
+ ACCESS read-only
859
+ STATUS mandatory
860
+ DESCRIPTION
861
+ "The number of IP datagrams that have been
862
+ successfully fragmented at this entity."
863
+ ::= { ip 17 }
864
+
865
+ ipFragFails OBJECT-TYPE
866
+ SYNTAX Counter
867
+ ACCESS read-only
868
+ STATUS mandatory
869
+ DESCRIPTION
870
+ "The number of IP datagrams that have been
871
+ discarded because they needed to be fragmented at
872
+ this entity but could not be, e.g., because their
873
+ Don't Fragment flag was set."
874
+ ::= { ip 18 }
875
+
876
+ ipFragCreates OBJECT-TYPE
877
+ SYNTAX Counter
878
+ ACCESS read-only
879
+ STATUS mandatory
880
+ DESCRIPTION
881
+ "The number of IP datagram fragments that have
882
+ been generated as a result of fragmentation at
883
+ this entity."
884
+ ::= { ip 19 }
885
+
886
+ -- the IP address table
887
+
888
+ -- The IP address table contains this entity's IP addressing
889
+ -- information.
890
+
891
+ ipAddrTable OBJECT-TYPE
892
+ SYNTAX SEQUENCE OF IpAddrEntry
893
+ ACCESS not-accessible
894
+ STATUS mandatory
895
+ DESCRIPTION
896
+ "The table of addressing information relevant to
897
+ this entity's IP addresses."
898
+ ::= { ip 20 }
899
+
900
+ ipAddrEntry OBJECT-TYPE
901
+ SYNTAX IpAddrEntry
902
+ ACCESS not-accessible
903
+ STATUS mandatory
904
+ DESCRIPTION
905
+ "The addressing information for one of this
906
+ entity's IP addresses."
907
+ INDEX { ipAdEntAddr }
908
+ ::= { ipAddrTable 1 }
909
+
910
+ IpAddrEntry ::=
911
+ SEQUENCE {
912
+ ipAdEntAddr
913
+ IpAddress,
914
+ ipAdEntIfIndex
915
+ INTEGER,
916
+ ipAdEntNetMask
917
+ IpAddress,
918
+ ipAdEntBcastAddr
919
+ INTEGER,
920
+ ipAdEntReasmMaxSize
921
+ INTEGER (0..65535)
922
+ }
923
+
924
+ ipAdEntAddr OBJECT-TYPE
925
+ SYNTAX IpAddress
926
+ ACCESS read-only
927
+ STATUS mandatory
928
+ DESCRIPTION
929
+ "The IP address to which this entry's addressing
930
+ information pertains."
931
+ ::= { ipAddrEntry 1 }
932
+
933
+ ipAdEntIfIndex OBJECT-TYPE
934
+ SYNTAX INTEGER
935
+ ACCESS read-only
936
+ STATUS mandatory
937
+ DESCRIPTION
938
+ "The index value which uniquely identifies the
939
+ interface to which this entry is applicable. The
940
+ interface identified by a particular value of this
941
+ index is the same interface as identified by the
942
+ same value of ifIndex."
943
+ ::= { ipAddrEntry 2 }
944
+
945
+ ipAdEntNetMask OBJECT-TYPE
946
+ SYNTAX IpAddress
947
+ ACCESS read-only
948
+ STATUS mandatory
949
+ DESCRIPTION
950
+ "The subnet mask associated with the IP address of
951
+ this entry. The value of the mask is an IP
952
+ address with all the network bits set to 1 and all
953
+ the hosts bits set to 0."
954
+ ::= { ipAddrEntry 3 }
955
+
956
+ ipAdEntBcastAddr OBJECT-TYPE
957
+ SYNTAX INTEGER
958
+ ACCESS read-only
959
+ STATUS mandatory
960
+ DESCRIPTION
961
+ "The value of the least-significant bit in the IP
962
+ broadcast address used for sending datagrams on
963
+ the (logical) interface associated with the IP
964
+ address of this entry. For example, when the
965
+ Internet standard all-ones broadcast address is
966
+ used, the value will be 1. This value applies to
967
+ both the subnet and network broadcasts addresses
968
+ used by the entity on this (logical) interface."
969
+ ::= { ipAddrEntry 4 }
970
+
971
+ ipAdEntReasmMaxSize OBJECT-TYPE
972
+ SYNTAX INTEGER (0..65535)
973
+ ACCESS read-only
974
+ STATUS mandatory
975
+ DESCRIPTION
976
+ "The size of the largest IP datagram which this
977
+ entity can re-assemble from incoming IP fragmented
978
+ datagrams received on this interface."
979
+ ::= { ipAddrEntry 5 }
980
+
981
+ -- the IP routing table
982
+
983
+ -- The IP routing table contains an entry for each route
984
+ -- presently known to this entity.
985
+
986
+ ipRouteTable OBJECT-TYPE
987
+ SYNTAX SEQUENCE OF IpRouteEntry
988
+ ACCESS not-accessible
989
+ STATUS mandatory
990
+ DESCRIPTION
991
+ "This entity's IP Routing table."
992
+ ::= { ip 21 }
993
+
994
+ ipRouteEntry OBJECT-TYPE
995
+ SYNTAX IpRouteEntry
996
+ ACCESS not-accessible
997
+ STATUS mandatory
998
+ DESCRIPTION
999
+ "A route to a particular destination."
1000
+ INDEX { ipRouteDest }
1001
+ ::= { ipRouteTable 1 }
1002
+
1003
+ IpRouteEntry ::=
1004
+ SEQUENCE {
1005
+ ipRouteDest
1006
+ IpAddress,
1007
+ ipRouteIfIndex
1008
+ INTEGER,
1009
+ ipRouteMetric1
1010
+ INTEGER,
1011
+ ipRouteMetric2
1012
+ INTEGER,
1013
+ ipRouteMetric3
1014
+ INTEGER,
1015
+ ipRouteMetric4
1016
+ INTEGER,
1017
+ ipRouteNextHop
1018
+ IpAddress,
1019
+ ipRouteType
1020
+ INTEGER,
1021
+ ipRouteProto
1022
+ INTEGER,
1023
+ ipRouteAge
1024
+ INTEGER,
1025
+ ipRouteMask
1026
+ IpAddress,
1027
+ ipRouteMetric5
1028
+ INTEGER,
1029
+ ipRouteInfo
1030
+ OBJECT IDENTIFIER
1031
+ }
1032
+
1033
+ ipRouteDest OBJECT-TYPE
1034
+ SYNTAX IpAddress
1035
+ ACCESS read-write
1036
+ STATUS mandatory
1037
+ DESCRIPTION
1038
+ "The destination IP address of this route. An
1039
+ entry with a value of 0.0.0.0 is considered a
1040
+ default route. Multiple routes to a single
1041
+ destination can appear in the table, but access to
1042
+ such multiple entries is dependent on the table-
1043
+ access mechanisms defined by the network
1044
+ management protocol in use."
1045
+ ::= { ipRouteEntry 1 }
1046
+
1047
+ ipRouteIfIndex OBJECT-TYPE
1048
+ SYNTAX INTEGER
1049
+ ACCESS read-write
1050
+ STATUS mandatory
1051
+ DESCRIPTION
1052
+ "The index value which uniquely identifies the
1053
+ local interface through which the next hop of this
1054
+ route should be reached. The interface identified
1055
+ by a particular value of this index is the same
1056
+ interface as identified by the same value of
1057
+ ifIndex."
1058
+ ::= { ipRouteEntry 2 }
1059
+
1060
+ ipRouteMetric1 OBJECT-TYPE
1061
+ SYNTAX INTEGER
1062
+ ACCESS read-write
1063
+ STATUS mandatory
1064
+ DESCRIPTION
1065
+ "The primary routing metric for this route. The
1066
+ semantics of this metric are determined by the
1067
+ routing-protocol specified in the route's
1068
+ ipRouteProto value. If this metric is not used,
1069
+ its value should be set to -1."
1070
+ ::= { ipRouteEntry 3 }
1071
+
1072
+ ipRouteMetric2 OBJECT-TYPE
1073
+ SYNTAX INTEGER
1074
+ ACCESS read-write
1075
+ STATUS mandatory
1076
+ DESCRIPTION
1077
+ "An alternate routing metric for this route. The
1078
+ semantics of this metric are determined by the
1079
+ routing-protocol specified in the route's
1080
+ ipRouteProto value. If this metric is not used,
1081
+ its value should be set to -1."
1082
+ ::= { ipRouteEntry 4 }
1083
+
1084
+ ipRouteMetric3 OBJECT-TYPE
1085
+ SYNTAX INTEGER
1086
+ ACCESS read-write
1087
+ STATUS mandatory
1088
+ DESCRIPTION
1089
+ "An alternate routing metric for this route. The
1090
+ semantics of this metric are determined by the
1091
+ routing-protocol specified in the route's
1092
+ ipRouteProto value. If this metric is not used,
1093
+ its value should be set to -1."
1094
+ ::= { ipRouteEntry 5 }
1095
+
1096
+ ipRouteMetric4 OBJECT-TYPE
1097
+ SYNTAX INTEGER
1098
+ ACCESS read-write
1099
+ STATUS mandatory
1100
+ DESCRIPTION
1101
+ "An alternate routing metric for this route. The
1102
+ semantics of this metric are determined by the
1103
+ routing-protocol specified in the route's
1104
+ ipRouteProto value. If this metric is not used,
1105
+ its value should be set to -1."
1106
+ ::= { ipRouteEntry 6 }
1107
+
1108
+ ipRouteNextHop OBJECT-TYPE
1109
+ SYNTAX IpAddress
1110
+ ACCESS read-write
1111
+ STATUS mandatory
1112
+ DESCRIPTION
1113
+ "The IP address of the next hop of this route.
1114
+ (In the case of a route bound to an interface
1115
+ which is realized via a broadcast media, the value
1116
+ of this field is the agent's IP address on that
1117
+ interface.)"
1118
+ ::= { ipRouteEntry 7 }
1119
+
1120
+ ipRouteType OBJECT-TYPE
1121
+ SYNTAX INTEGER {
1122
+ other(1), -- none of the following
1123
+
1124
+ invalid(2), -- an invalidated route
1125
+
1126
+ -- route to directly
1127
+ direct(3), -- connected (sub-)network
1128
+
1129
+ -- route to a non-local
1130
+ indirect(4) -- host/network/sub-network
1131
+ }
1132
+ ACCESS read-write
1133
+ STATUS mandatory
1134
+ DESCRIPTION
1135
+ "The type of route. Note that the values
1136
+ direct(3) and indirect(4) refer to the notion of
1137
+ direct and indirect routing in the IP
1138
+ architecture.
1139
+
1140
+ Setting this object to the value invalid(2) has
1141
+ the effect of invalidating the corresponding entry
1142
+ in the ipRouteTable object. That is, it
1143
+ effectively dissasociates the destination
1144
+ identified with said entry from the route
1145
+ identified with said entry. It is an
1146
+ implementation-specific matter as to whether the
1147
+ agent removes an invalidated entry from the table.
1148
+ Accordingly, management stations must be prepared
1149
+ to receive tabular information from agents that
1150
+ corresponds to entries not currently in use.
1151
+ Proper interpretation of such entries requires
1152
+ examination of the relevant ipRouteType object."
1153
+ ::= { ipRouteEntry 8 }
1154
+
1155
+ ipRouteProto OBJECT-TYPE
1156
+ SYNTAX INTEGER {
1157
+ other(1), -- none of the following
1158
+
1159
+ -- non-protocol information,
1160
+ -- e.g., manually configured
1161
+ local(2), -- entries
1162
+
1163
+ -- set via a network
1164
+ netmgmt(3), -- management protocol
1165
+
1166
+ -- obtained via ICMP,
1167
+ icmp(4), -- e.g., Redirect
1168
+
1169
+ -- the remaining values are
1170
+ -- all gateway routing
1171
+ -- protocols
1172
+ egp(5),
1173
+ ggp(6),
1174
+ hello(7),
1175
+ rip(8),
1176
+ is-is(9),
1177
+ es-is(10),
1178
+ ciscoIgrp(11),
1179
+ bbnSpfIgp(12),
1180
+ ospf(13),
1181
+ bgp(14)
1182
+ }
1183
+ ACCESS read-only
1184
+ STATUS mandatory
1185
+ DESCRIPTION
1186
+ "The routing mechanism via which this route was
1187
+ learned. Inclusion of values for gateway routing
1188
+ protocols is not intended to imply that hosts
1189
+ should support those protocols."
1190
+ ::= { ipRouteEntry 9 }
1191
+
1192
+ ipRouteAge OBJECT-TYPE
1193
+ SYNTAX INTEGER
1194
+ ACCESS read-write
1195
+ STATUS mandatory
1196
+ DESCRIPTION
1197
+ "The number of seconds since this route was last
1198
+ updated or otherwise determined to be correct.
1199
+ Note that no semantics of `too old' can be implied
1200
+ except through knowledge of the routing protocol
1201
+ by which the route was learned."
1202
+ ::= { ipRouteEntry 10 }
1203
+
1204
+ ipRouteMask OBJECT-TYPE
1205
+ SYNTAX IpAddress
1206
+ ACCESS read-write
1207
+ STATUS mandatory
1208
+ DESCRIPTION
1209
+ "Indicate the mask to be logical-ANDed with the
1210
+ destination address before being compared to the
1211
+ value in the ipRouteDest field. For those systems
1212
+ that do not support arbitrary subnet masks, an
1213
+ agent constructs the value of the ipRouteMask by
1214
+ determining whether the value of the correspondent
1215
+ ipRouteDest field belong to a class-A, B, or C
1216
+ network, and then using one of:
1217
+
1218
+ mask network
1219
+ 255.0.0.0 class-A
1220
+ 255.255.0.0 class-B
1221
+ 255.255.255.0 class-C
1222
+
1223
+ If the value of the ipRouteDest is 0.0.0.0 (a
1224
+ default route), then the mask value is also
1225
+ 0.0.0.0. It should be noted that all IP routing
1226
+ subsystems implicitly use this mechanism."
1227
+ ::= { ipRouteEntry 11 }
1228
+
1229
+ ipRouteMetric5 OBJECT-TYPE
1230
+ SYNTAX INTEGER
1231
+ ACCESS read-write
1232
+ STATUS mandatory
1233
+ DESCRIPTION
1234
+ "An alternate routing metric for this route. The
1235
+ semantics of this metric are determined by the
1236
+ routing-protocol specified in the route's
1237
+ ipRouteProto value. If this metric is not used,
1238
+ its value should be set to -1."
1239
+ ::= { ipRouteEntry 12 }
1240
+
1241
+ ipRouteInfo OBJECT-TYPE
1242
+ SYNTAX OBJECT IDENTIFIER
1243
+ ACCESS read-only
1244
+ STATUS mandatory
1245
+ DESCRIPTION
1246
+ "A reference to MIB definitions specific to the
1247
+ particular routing protocol which is responsible
1248
+ for this route, as determined by the value
1249
+ specified in the route's ipRouteProto value. If
1250
+ this information is not present, its value should
1251
+ be set to the OBJECT IDENTIFIER { 0 0 }, which is
1252
+ a syntatically valid object identifier, and any
1253
+ conformant implementation of ASN.1 and BER must be
1254
+ able to generate and recognize this value."
1255
+ ::= { ipRouteEntry 13 }
1256
+
1257
+ -- the IP Address Translation table
1258
+
1259
+ -- The IP address translation table contain the IpAddress to
1260
+ -- `physical' address equivalences. Some interfaces do not
1261
+ -- use translation tables for determining address
1262
+ -- equivalences (e.g., DDN-X.25 has an algorithmic method);
1263
+ -- if all interfaces are of this type, then the Address
1264
+ -- Translation table is empty, i.e., has zero entries.
1265
+
1266
+ ipNetToMediaTable OBJECT-TYPE
1267
+ SYNTAX SEQUENCE OF IpNetToMediaEntry
1268
+ ACCESS not-accessible
1269
+ STATUS mandatory
1270
+ DESCRIPTION
1271
+ "The IP Address Translation table used for mapping
1272
+ from IP addresses to physical addresses."
1273
+ ::= { ip 22 }
1274
+
1275
+ ipNetToMediaEntry OBJECT-TYPE
1276
+ SYNTAX IpNetToMediaEntry
1277
+ ACCESS not-accessible
1278
+ STATUS mandatory
1279
+ DESCRIPTION
1280
+ "Each entry contains one IpAddress to `physical'
1281
+ address equivalence."
1282
+ INDEX { ipNetToMediaIfIndex,
1283
+ ipNetToMediaNetAddress }
1284
+ ::= { ipNetToMediaTable 1 }
1285
+
1286
+ IpNetToMediaEntry ::=
1287
+ SEQUENCE {
1288
+ ipNetToMediaIfIndex
1289
+ INTEGER,
1290
+ ipNetToMediaPhysAddress
1291
+ PhysAddress,
1292
+ ipNetToMediaNetAddress
1293
+ IpAddress,
1294
+ ipNetToMediaType
1295
+ INTEGER
1296
+ }
1297
+
1298
+ ipNetToMediaIfIndex OBJECT-TYPE
1299
+ SYNTAX INTEGER
1300
+ ACCESS read-write
1301
+ STATUS mandatory
1302
+ DESCRIPTION
1303
+ "The interface on which this entry's equivalence
1304
+ is effective. The interface identified by a
1305
+ particular value of this index is the same
1306
+ interface as identified by the same value of
1307
+ ifIndex."
1308
+ ::= { ipNetToMediaEntry 1 }
1309
+
1310
+ ipNetToMediaPhysAddress OBJECT-TYPE
1311
+ SYNTAX PhysAddress
1312
+ ACCESS read-write
1313
+ STATUS mandatory
1314
+ DESCRIPTION
1315
+ "The media-dependent `physical' address."
1316
+ ::= { ipNetToMediaEntry 2 }
1317
+
1318
+ ipNetToMediaNetAddress OBJECT-TYPE
1319
+ SYNTAX IpAddress
1320
+ ACCESS read-write
1321
+ STATUS mandatory
1322
+ DESCRIPTION
1323
+ "The IpAddress corresponding to the media-
1324
+ dependent `physical' address."
1325
+ ::= { ipNetToMediaEntry 3 }
1326
+
1327
+ ipNetToMediaType OBJECT-TYPE
1328
+ SYNTAX INTEGER {
1329
+ other(1), -- none of the following
1330
+ invalid(2), -- an invalidated mapping
1331
+ dynamic(3),
1332
+ static(4)
1333
+ }
1334
+ ACCESS read-write
1335
+ STATUS mandatory
1336
+ DESCRIPTION
1337
+ "The type of mapping.
1338
+
1339
+ Setting this object to the value invalid(2) has
1340
+ the effect of invalidating the corresponding entry
1341
+ in the ipNetToMediaTable. That is, it effectively
1342
+ dissasociates the interface identified with said
1343
+ entry from the mapping identified with said entry.
1344
+ It is an implementation-specific matter as to
1345
+ whether the agent removes an invalidated entry
1346
+ from the table. Accordingly, management stations
1347
+ must be prepared to receive tabular information
1348
+ from agents that corresponds to entries not
1349
+ currently in use. Proper interpretation of such
1350
+ entries requires examination of the relevant
1351
+ ipNetToMediaType object."
1352
+ ::= { ipNetToMediaEntry 4 }
1353
+
1354
+ -- additional IP objects
1355
+
1356
+ ipRoutingDiscards OBJECT-TYPE
1357
+ SYNTAX Counter
1358
+ ACCESS read-only
1359
+ STATUS mandatory
1360
+ DESCRIPTION
1361
+ "The number of routing entries which were chosen
1362
+ to be discarded even though they are valid. One
1363
+ possible reason for discarding such an entry could
1364
+ be to free-up buffer space for other routing
1365
+
1366
+ entries."
1367
+ ::= { ip 23 }
1368
+
1369
+ -- the ICMP group
1370
+
1371
+ -- Implementation of the ICMP group is mandatory for all
1372
+ -- systems.
1373
+
1374
+ icmpInMsgs OBJECT-TYPE
1375
+ SYNTAX Counter
1376
+ ACCESS read-only
1377
+ STATUS mandatory
1378
+ DESCRIPTION
1379
+ "The total number of ICMP messages which the
1380
+ entity received. Note that this counter includes
1381
+ all those counted by icmpInErrors."
1382
+ ::= { icmp 1 }
1383
+
1384
+ icmpInErrors OBJECT-TYPE
1385
+ SYNTAX Counter
1386
+ ACCESS read-only
1387
+ STATUS mandatory
1388
+ DESCRIPTION
1389
+ "The number of ICMP messages which the entity
1390
+ received but determined as having ICMP-specific
1391
+ errors (bad ICMP checksums, bad length, etc.)."
1392
+ ::= { icmp 2 }
1393
+
1394
+ icmpInDestUnreachs OBJECT-TYPE
1395
+ SYNTAX Counter
1396
+ ACCESS read-only
1397
+ STATUS mandatory
1398
+ DESCRIPTION
1399
+ "The number of ICMP Destination Unreachable
1400
+ messages received."
1401
+ ::= { icmp 3 }
1402
+
1403
+ icmpInTimeExcds OBJECT-TYPE
1404
+ SYNTAX Counter
1405
+ ACCESS read-only
1406
+ STATUS mandatory
1407
+ DESCRIPTION
1408
+ "The number of ICMP Time Exceeded messages
1409
+ received."
1410
+ ::= { icmp 4 }
1411
+
1412
+ icmpInParmProbs OBJECT-TYPE
1413
+ SYNTAX Counter
1414
+ ACCESS read-only
1415
+ STATUS mandatory
1416
+ DESCRIPTION
1417
+ "The number of ICMP Parameter Problem messages
1418
+ received."
1419
+ ::= { icmp 5 }
1420
+
1421
+ icmpInSrcQuenchs OBJECT-TYPE
1422
+ SYNTAX Counter
1423
+ ACCESS read-only
1424
+ STATUS mandatory
1425
+ DESCRIPTION
1426
+ "The number of ICMP Source Quench messages
1427
+ received."
1428
+ ::= { icmp 6 }
1429
+
1430
+ icmpInRedirects OBJECT-TYPE
1431
+ SYNTAX Counter
1432
+ ACCESS read-only
1433
+ STATUS mandatory
1434
+ DESCRIPTION
1435
+ "The number of ICMP Redirect messages received."
1436
+ ::= { icmp 7 }
1437
+
1438
+ icmpInEchos OBJECT-TYPE
1439
+ SYNTAX Counter
1440
+ ACCESS read-only
1441
+ STATUS mandatory
1442
+ DESCRIPTION
1443
+ "The number of ICMP Echo (request) messages
1444
+ received."
1445
+ ::= { icmp 8 }
1446
+
1447
+ icmpInEchoReps OBJECT-TYPE
1448
+ SYNTAX Counter
1449
+ ACCESS read-only
1450
+ STATUS mandatory
1451
+ DESCRIPTION
1452
+ "The number of ICMP Echo Reply messages received."
1453
+ ::= { icmp 9 }
1454
+
1455
+ icmpInTimestamps OBJECT-TYPE
1456
+ SYNTAX Counter
1457
+ ACCESS read-only
1458
+ STATUS mandatory
1459
+ DESCRIPTION
1460
+ "The number of ICMP Timestamp (request) messages
1461
+ received."
1462
+ ::= { icmp 10 }
1463
+
1464
+ icmpInTimestampReps OBJECT-TYPE
1465
+ SYNTAX Counter
1466
+ ACCESS read-only
1467
+ STATUS mandatory
1468
+ DESCRIPTION
1469
+ "The number of ICMP Timestamp Reply messages
1470
+ received."
1471
+ ::= { icmp 11 }
1472
+
1473
+ icmpInAddrMasks OBJECT-TYPE
1474
+ SYNTAX Counter
1475
+ ACCESS read-only
1476
+ STATUS mandatory
1477
+ DESCRIPTION
1478
+ "The number of ICMP Address Mask Request messages
1479
+ received."
1480
+ ::= { icmp 12 }
1481
+
1482
+ icmpInAddrMaskReps OBJECT-TYPE
1483
+ SYNTAX Counter
1484
+ ACCESS read-only
1485
+ STATUS mandatory
1486
+ DESCRIPTION
1487
+ "The number of ICMP Address Mask Reply messages
1488
+ received."
1489
+ ::= { icmp 13 }
1490
+
1491
+ icmpOutMsgs OBJECT-TYPE
1492
+ SYNTAX Counter
1493
+ ACCESS read-only
1494
+ STATUS mandatory
1495
+ DESCRIPTION
1496
+ "The total number of ICMP messages which this
1497
+ entity attempted to send. Note that this counter
1498
+ includes all those counted by icmpOutErrors."
1499
+ ::= { icmp 14 }
1500
+
1501
+ icmpOutErrors OBJECT-TYPE
1502
+ SYNTAX Counter
1503
+ ACCESS read-only
1504
+ STATUS mandatory
1505
+ DESCRIPTION
1506
+ "The number of ICMP messages which this entity did
1507
+ not send due to problems discovered within ICMP
1508
+
1509
+ such as a lack of buffers. This value should not
1510
+ include errors discovered outside the ICMP layer
1511
+ such as the inability of IP to route the resultant
1512
+ datagram. In some implementations there may be no
1513
+ types of error which contribute to this counter's
1514
+ value."
1515
+ ::= { icmp 15 }
1516
+
1517
+ icmpOutDestUnreachs OBJECT-TYPE
1518
+ SYNTAX Counter
1519
+ ACCESS read-only
1520
+ STATUS mandatory
1521
+ DESCRIPTION
1522
+ "The number of ICMP Destination Unreachable
1523
+ messages sent."
1524
+ ::= { icmp 16 }
1525
+
1526
+ icmpOutTimeExcds OBJECT-TYPE
1527
+ SYNTAX Counter
1528
+ ACCESS read-only
1529
+ STATUS mandatory
1530
+ DESCRIPTION
1531
+ "The number of ICMP Time Exceeded messages sent."
1532
+ ::= { icmp 17 }
1533
+
1534
+ icmpOutParmProbs OBJECT-TYPE
1535
+ SYNTAX Counter
1536
+ ACCESS read-only
1537
+ STATUS mandatory
1538
+ DESCRIPTION
1539
+ "The number of ICMP Parameter Problem messages
1540
+ sent."
1541
+ ::= { icmp 18 }
1542
+
1543
+ icmpOutSrcQuenchs OBJECT-TYPE
1544
+ SYNTAX Counter
1545
+ ACCESS read-only
1546
+ STATUS mandatory
1547
+ DESCRIPTION
1548
+ "The number of ICMP Source Quench messages sent."
1549
+ ::= { icmp 19 }
1550
+
1551
+ icmpOutRedirects OBJECT-TYPE
1552
+ SYNTAX Counter
1553
+ ACCESS read-only
1554
+ STATUS mandatory
1555
+ DESCRIPTION
1556
+ "The number of ICMP Redirect messages sent. For a
1557
+
1558
+ host, this object will always be zero, since hosts
1559
+ do not send redirects."
1560
+ ::= { icmp 20 }
1561
+
1562
+ icmpOutEchos OBJECT-TYPE
1563
+ SYNTAX Counter
1564
+ ACCESS read-only
1565
+ STATUS mandatory
1566
+ DESCRIPTION
1567
+ "The number of ICMP Echo (request) messages sent."
1568
+ ::= { icmp 21 }
1569
+
1570
+ icmpOutEchoReps OBJECT-TYPE
1571
+ SYNTAX Counter
1572
+ ACCESS read-only
1573
+ STATUS mandatory
1574
+ DESCRIPTION
1575
+ "The number of ICMP Echo Reply messages sent."
1576
+ ::= { icmp 22 }
1577
+
1578
+ icmpOutTimestamps OBJECT-TYPE
1579
+ SYNTAX Counter
1580
+ ACCESS read-only
1581
+ STATUS mandatory
1582
+ DESCRIPTION
1583
+ "The number of ICMP Timestamp (request) messages
1584
+ sent."
1585
+ ::= { icmp 23 }
1586
+
1587
+ icmpOutTimestampReps OBJECT-TYPE
1588
+ SYNTAX Counter
1589
+ ACCESS read-only
1590
+ STATUS mandatory
1591
+ DESCRIPTION
1592
+ "The number of ICMP Timestamp Reply messages
1593
+ sent."
1594
+ ::= { icmp 24 }
1595
+
1596
+ icmpOutAddrMasks OBJECT-TYPE
1597
+ SYNTAX Counter
1598
+ ACCESS read-only
1599
+ STATUS mandatory
1600
+ DESCRIPTION
1601
+ "The number of ICMP Address Mask Request messages
1602
+ sent."
1603
+ ::= { icmp 25 }
1604
+
1605
+ icmpOutAddrMaskReps OBJECT-TYPE
1606
+ SYNTAX Counter
1607
+ ACCESS read-only
1608
+ STATUS mandatory
1609
+ DESCRIPTION
1610
+ "The number of ICMP Address Mask Reply messages
1611
+ sent."
1612
+ ::= { icmp 26 }
1613
+
1614
+ -- the TCP group
1615
+
1616
+ -- Implementation of the TCP group is mandatory for all
1617
+ -- systems that implement the TCP.
1618
+
1619
+ -- Note that instances of object types that represent
1620
+ -- information about a particular TCP connection are
1621
+ -- transient; they persist only as long as the connection
1622
+ -- in question.
1623
+
1624
+ tcpRtoAlgorithm OBJECT-TYPE
1625
+ SYNTAX INTEGER {
1626
+ other(1), -- none of the following
1627
+
1628
+ constant(2), -- a constant rto
1629
+ rsre(3), -- MIL-STD-1778, Appendix B
1630
+ vanj(4) -- Van Jacobson's algorithm [10]
1631
+ }
1632
+ ACCESS read-only
1633
+ STATUS mandatory
1634
+ DESCRIPTION
1635
+ "The algorithm used to determine the timeout value
1636
+ used for retransmitting unacknowledged octets."
1637
+ ::= { tcp 1 }
1638
+
1639
+ tcpRtoMin OBJECT-TYPE
1640
+ SYNTAX INTEGER
1641
+ ACCESS read-only
1642
+ STATUS mandatory
1643
+ DESCRIPTION
1644
+ "The minimum value permitted by a TCP
1645
+ implementation for the retransmission timeout,
1646
+ measured in milliseconds. More refined semantics
1647
+ for objects of this type depend upon the algorithm
1648
+ used to determine the retransmission timeout. In
1649
+ particular, when the timeout algorithm is rsre(3),
1650
+ an object of this type has the semantics of the
1651
+ LBOUND quantity described in RFC 793."
1652
+ ::= { tcp 2 }
1653
+
1654
+ tcpRtoMax OBJECT-TYPE
1655
+ SYNTAX INTEGER
1656
+ ACCESS read-only
1657
+ STATUS mandatory
1658
+ DESCRIPTION
1659
+ "The maximum value permitted by a TCP
1660
+ implementation for the retransmission timeout,
1661
+ measured in milliseconds. More refined semantics
1662
+ for objects of this type depend upon the algorithm
1663
+ used to determine the retransmission timeout. In
1664
+ particular, when the timeout algorithm is rsre(3),
1665
+ an object of this type has the semantics of the
1666
+ UBOUND quantity described in RFC 793."
1667
+ ::= { tcp 3 }
1668
+
1669
+ tcpMaxConn OBJECT-TYPE
1670
+ SYNTAX INTEGER
1671
+ ACCESS read-only
1672
+ STATUS mandatory
1673
+ DESCRIPTION
1674
+ "The limit on the total number of TCP connections
1675
+ the entity can support. In entities where the
1676
+ maximum number of connections is dynamic, this
1677
+ object should contain the value -1."
1678
+ ::= { tcp 4 }
1679
+
1680
+ tcpActiveOpens OBJECT-TYPE
1681
+ SYNTAX Counter
1682
+ ACCESS read-only
1683
+ STATUS mandatory
1684
+ DESCRIPTION
1685
+ "The number of times TCP connections have made a
1686
+ direct transition to the SYN-SENT state from the
1687
+ CLOSED state."
1688
+ ::= { tcp 5 }
1689
+
1690
+ tcpPassiveOpens OBJECT-TYPE
1691
+ SYNTAX Counter
1692
+ ACCESS read-only
1693
+ STATUS mandatory
1694
+ DESCRIPTION
1695
+ "The number of times TCP connections have made a
1696
+ direct transition to the SYN-RCVD state from the
1697
+ LISTEN state."
1698
+ ::= { tcp 6 }
1699
+
1700
+ tcpAttemptFails OBJECT-TYPE
1701
+ SYNTAX Counter
1702
+ ACCESS read-only
1703
+ STATUS mandatory
1704
+ DESCRIPTION
1705
+ "The number of times TCP connections have made a
1706
+ direct transition to the CLOSED state from either
1707
+ the SYN-SENT state or the SYN-RCVD state, plus the
1708
+ number of times TCP connections have made a direct
1709
+ transition to the LISTEN state from the SYN-RCVD
1710
+ state."
1711
+ ::= { tcp 7 }
1712
+
1713
+ tcpEstabResets OBJECT-TYPE
1714
+ SYNTAX Counter
1715
+ ACCESS read-only
1716
+ STATUS mandatory
1717
+ DESCRIPTION
1718
+ "The number of times TCP connections have made a
1719
+ direct transition to the CLOSED state from either
1720
+ the ESTABLISHED state or the CLOSE-WAIT state."
1721
+ ::= { tcp 8 }
1722
+
1723
+ tcpCurrEstab OBJECT-TYPE
1724
+ SYNTAX Gauge
1725
+ ACCESS read-only
1726
+ STATUS mandatory
1727
+ DESCRIPTION
1728
+ "The number of TCP connections for which the
1729
+ current state is either ESTABLISHED or CLOSE-
1730
+ WAIT."
1731
+ ::= { tcp 9 }
1732
+
1733
+ tcpInSegs OBJECT-TYPE
1734
+ SYNTAX Counter
1735
+ ACCESS read-only
1736
+ STATUS mandatory
1737
+ DESCRIPTION
1738
+ "The total number of segments received, including
1739
+ those received in error. This count includes
1740
+ segments received on currently established
1741
+ connections."
1742
+ ::= { tcp 10 }
1743
+
1744
+ tcpOutSegs OBJECT-TYPE
1745
+ SYNTAX Counter
1746
+ ACCESS read-only
1747
+ STATUS mandatory
1748
+ DESCRIPTION
1749
+ "The total number of segments sent, including
1750
+ those on current connections but excluding those
1751
+ containing only retransmitted octets."
1752
+ ::= { tcp 11 }
1753
+
1754
+ tcpRetransSegs OBJECT-TYPE
1755
+ SYNTAX Counter
1756
+ ACCESS read-only
1757
+ STATUS mandatory
1758
+ DESCRIPTION
1759
+ "The total number of segments retransmitted - that
1760
+ is, the number of TCP segments transmitted
1761
+ containing one or more previously transmitted
1762
+ octets."
1763
+ ::= { tcp 12 }
1764
+
1765
+ -- the TCP Connection table
1766
+
1767
+ -- The TCP connection table contains information about this
1768
+ -- entity's existing TCP connections.
1769
+
1770
+ tcpConnTable OBJECT-TYPE
1771
+ SYNTAX SEQUENCE OF TcpConnEntry
1772
+ ACCESS not-accessible
1773
+ STATUS mandatory
1774
+ DESCRIPTION
1775
+ "A table containing TCP connection-specific
1776
+ information."
1777
+ ::= { tcp 13 }
1778
+
1779
+ tcpConnEntry OBJECT-TYPE
1780
+ SYNTAX TcpConnEntry
1781
+ ACCESS not-accessible
1782
+ STATUS mandatory
1783
+ DESCRIPTION
1784
+ "Information about a particular current TCP
1785
+ connection. An object of this type is transient,
1786
+ in that it ceases to exist when (or soon after)
1787
+ the connection makes the transition to the CLOSED
1788
+ state."
1789
+ INDEX { tcpConnLocalAddress,
1790
+ tcpConnLocalPort,
1791
+ tcpConnRemAddress,
1792
+ tcpConnRemPort }
1793
+ ::= { tcpConnTable 1 }
1794
+
1795
+ TcpConnEntry ::=
1796
+ SEQUENCE {
1797
+ tcpConnState
1798
+ INTEGER,
1799
+ tcpConnLocalAddress
1800
+ IpAddress,
1801
+ tcpConnLocalPort
1802
+ INTEGER (0..65535),
1803
+ tcpConnRemAddress
1804
+ IpAddress,
1805
+ tcpConnRemPort
1806
+ INTEGER (0..65535)
1807
+ }
1808
+
1809
+ tcpConnState OBJECT-TYPE
1810
+ SYNTAX INTEGER {
1811
+ closed(1),
1812
+ listen(2),
1813
+ synSent(3),
1814
+ synReceived(4),
1815
+ established(5),
1816
+ finWait1(6),
1817
+ finWait2(7),
1818
+ closeWait(8),
1819
+ lastAck(9),
1820
+ closing(10),
1821
+ timeWait(11),
1822
+ deleteTCB(12)
1823
+ }
1824
+ ACCESS read-write
1825
+ STATUS mandatory
1826
+ DESCRIPTION
1827
+ "The state of this TCP connection.
1828
+
1829
+ The only value which may be set by a management
1830
+ station is deleteTCB(12). Accordingly, it is
1831
+ appropriate for an agent to return a `badValue'
1832
+ response if a management station attempts to set
1833
+ this object to any other value.
1834
+
1835
+ If a management station sets this object to the
1836
+ value deleteTCB(12), then this has the effect of
1837
+ deleting the TCB (as defined in RFC 793) of the
1838
+ corresponding connection on the managed node,
1839
+ resulting in immediate termination of the
1840
+ connection.
1841
+
1842
+ As an implementation-specific option, a RST
1843
+
1844
+ segment may be sent from the managed node to the
1845
+ other TCP endpoint (note however that RST segments
1846
+ are not sent reliably)."
1847
+ ::= { tcpConnEntry 1 }
1848
+
1849
+ tcpConnLocalAddress OBJECT-TYPE
1850
+ SYNTAX IpAddress
1851
+ ACCESS read-only
1852
+ STATUS mandatory
1853
+ DESCRIPTION
1854
+ "The local IP address for this TCP connection. In
1855
+ the case of a connection in the listen state which
1856
+ is willing to accept connections for any IP
1857
+ interface associated with the node, the value
1858
+ 0.0.0.0 is used."
1859
+ ::= { tcpConnEntry 2 }
1860
+
1861
+ tcpConnLocalPort OBJECT-TYPE
1862
+ SYNTAX INTEGER (0..65535)
1863
+ ACCESS read-only
1864
+ STATUS mandatory
1865
+ DESCRIPTION
1866
+ "The local port number for this TCP connection."
1867
+ ::= { tcpConnEntry 3 }
1868
+
1869
+ tcpConnRemAddress OBJECT-TYPE
1870
+ SYNTAX IpAddress
1871
+ ACCESS read-only
1872
+ STATUS mandatory
1873
+ DESCRIPTION
1874
+ "The remote IP address for this TCP connection."
1875
+ ::= { tcpConnEntry 4 }
1876
+
1877
+ tcpConnRemPort OBJECT-TYPE
1878
+ SYNTAX INTEGER (0..65535)
1879
+ ACCESS read-only
1880
+ STATUS mandatory
1881
+ DESCRIPTION
1882
+ "The remote port number for this TCP connection."
1883
+ ::= { tcpConnEntry 5 }
1884
+
1885
+ -- additional TCP objects
1886
+
1887
+ tcpInErrs OBJECT-TYPE
1888
+ SYNTAX Counter
1889
+ ACCESS read-only
1890
+ STATUS mandatory
1891
+ DESCRIPTION
1892
+ "The total number of segments received in error
1893
+ (e.g., bad TCP checksums)."
1894
+ ::= { tcp 14 }
1895
+
1896
+ tcpOutRsts OBJECT-TYPE
1897
+ SYNTAX Counter
1898
+ ACCESS read-only
1899
+ STATUS mandatory
1900
+ DESCRIPTION
1901
+ "The number of TCP segments sent containing the
1902
+ RST flag."
1903
+ ::= { tcp 15 }
1904
+
1905
+ -- the UDP group
1906
+
1907
+ -- Implementation of the UDP group is mandatory for all
1908
+ -- systems which implement the UDP.
1909
+
1910
+ udpInDatagrams OBJECT-TYPE
1911
+ SYNTAX Counter
1912
+ ACCESS read-only
1913
+ STATUS mandatory
1914
+ DESCRIPTION
1915
+ "The total number of UDP datagrams delivered to
1916
+ UDP users."
1917
+ ::= { udp 1 }
1918
+
1919
+ udpNoPorts OBJECT-TYPE
1920
+ SYNTAX Counter
1921
+ ACCESS read-only
1922
+ STATUS mandatory
1923
+ DESCRIPTION
1924
+ "The total number of received UDP datagrams for
1925
+ which there was no application at the destination
1926
+ port."
1927
+ ::= { udp 2 }
1928
+
1929
+ udpInErrors OBJECT-TYPE
1930
+ SYNTAX Counter
1931
+ ACCESS read-only
1932
+ STATUS mandatory
1933
+ DESCRIPTION
1934
+ "The number of received UDP datagrams that could
1935
+ not be delivered for reasons other than the lack
1936
+ of an application at the destination port."
1937
+ ::= { udp 3 }
1938
+
1939
+ udpOutDatagrams OBJECT-TYPE
1940
+ SYNTAX Counter
1941
+ ACCESS read-only
1942
+ STATUS mandatory
1943
+ DESCRIPTION
1944
+ "The total number of UDP datagrams sent from this
1945
+ entity."
1946
+ ::= { udp 4 }
1947
+
1948
+ -- the UDP Listener table
1949
+
1950
+ -- The UDP listener table contains information about this
1951
+ -- entity's UDP end-points on which a local application is
1952
+ -- currently accepting datagrams.
1953
+
1954
+ udpTable OBJECT-TYPE
1955
+ SYNTAX SEQUENCE OF UdpEntry
1956
+ ACCESS not-accessible
1957
+ STATUS mandatory
1958
+ DESCRIPTION
1959
+ "A table containing UDP listener information."
1960
+ ::= { udp 5 }
1961
+
1962
+ udpEntry OBJECT-TYPE
1963
+ SYNTAX UdpEntry
1964
+ ACCESS not-accessible
1965
+ STATUS mandatory
1966
+ DESCRIPTION
1967
+ "Information about a particular current UDP
1968
+ listener."
1969
+ INDEX { udpLocalAddress, udpLocalPort }
1970
+ ::= { udpTable 1 }
1971
+
1972
+ UdpEntry ::=
1973
+ SEQUENCE {
1974
+ udpLocalAddress
1975
+ IpAddress,
1976
+ udpLocalPort
1977
+ INTEGER (0..65535)
1978
+ }
1979
+
1980
+ udpLocalAddress OBJECT-TYPE
1981
+ SYNTAX IpAddress
1982
+ ACCESS read-only
1983
+ STATUS mandatory
1984
+ DESCRIPTION
1985
+ "The local IP address for this UDP listener. In
1986
+
1987
+ the case of a UDP listener which is willing to
1988
+ accept datagrams for any IP interface associated
1989
+ with the node, the value 0.0.0.0 is used."
1990
+ ::= { udpEntry 1 }
1991
+
1992
+ udpLocalPort OBJECT-TYPE
1993
+ SYNTAX INTEGER (0..65535)
1994
+ ACCESS read-only
1995
+ STATUS mandatory
1996
+ DESCRIPTION
1997
+ "The local port number for this UDP listener."
1998
+ ::= { udpEntry 2 }
1999
+
2000
+ -- the EGP group
2001
+
2002
+ -- Implementation of the EGP group is mandatory for all
2003
+ -- systems which implement the EGP.
2004
+
2005
+ egpInMsgs OBJECT-TYPE
2006
+ SYNTAX Counter
2007
+ ACCESS read-only
2008
+ STATUS mandatory
2009
+ DESCRIPTION
2010
+ "The number of EGP messages received without
2011
+ error."
2012
+ ::= { egp 1 }
2013
+
2014
+ egpInErrors OBJECT-TYPE
2015
+ SYNTAX Counter
2016
+ ACCESS read-only
2017
+ STATUS mandatory
2018
+ DESCRIPTION
2019
+ "The number of EGP messages received that proved
2020
+ to be in error."
2021
+ ::= { egp 2 }
2022
+
2023
+ egpOutMsgs OBJECT-TYPE
2024
+ SYNTAX Counter
2025
+ ACCESS read-only
2026
+ STATUS mandatory
2027
+ DESCRIPTION
2028
+ "The total number of locally generated EGP
2029
+ messages."
2030
+ ::= { egp 3 }
2031
+
2032
+ egpOutErrors OBJECT-TYPE
2033
+ SYNTAX Counter
2034
+ ACCESS read-only
2035
+ STATUS mandatory
2036
+ DESCRIPTION
2037
+ "The number of locally generated EGP messages not
2038
+ sent due to resource limitations within an EGP
2039
+ entity."
2040
+ ::= { egp 4 }
2041
+
2042
+ -- the EGP Neighbor table
2043
+
2044
+ -- The EGP neighbor table contains information about this
2045
+ -- entity's EGP neighbors.
2046
+
2047
+ egpNeighTable OBJECT-TYPE
2048
+ SYNTAX SEQUENCE OF EgpNeighEntry
2049
+ ACCESS not-accessible
2050
+ STATUS mandatory
2051
+ DESCRIPTION
2052
+ "The EGP neighbor table."
2053
+ ::= { egp 5 }
2054
+
2055
+ egpNeighEntry OBJECT-TYPE
2056
+ SYNTAX EgpNeighEntry
2057
+ ACCESS not-accessible
2058
+ STATUS mandatory
2059
+ DESCRIPTION
2060
+ "Information about this entity's relationship with
2061
+ a particular EGP neighbor."
2062
+ INDEX { egpNeighAddr }
2063
+ ::= { egpNeighTable 1 }
2064
+
2065
+ EgpNeighEntry ::=
2066
+ SEQUENCE {
2067
+ egpNeighState
2068
+ INTEGER,
2069
+ egpNeighAddr
2070
+ IpAddress,
2071
+ egpNeighAs
2072
+ INTEGER,
2073
+ egpNeighInMsgs
2074
+ Counter,
2075
+ egpNeighInErrs
2076
+ Counter,
2077
+ egpNeighOutMsgs
2078
+ Counter,
2079
+ egpNeighOutErrs
2080
+ Counter,
2081
+ egpNeighInErrMsgs
2082
+ Counter,
2083
+ egpNeighOutErrMsgs
2084
+ Counter,
2085
+ egpNeighStateUps
2086
+ Counter,
2087
+ egpNeighStateDowns
2088
+ Counter,
2089
+ egpNeighIntervalHello
2090
+ INTEGER,
2091
+ egpNeighIntervalPoll
2092
+ INTEGER,
2093
+ egpNeighMode
2094
+ INTEGER,
2095
+ egpNeighEventTrigger
2096
+ INTEGER
2097
+ }
2098
+
2099
+ egpNeighState OBJECT-TYPE
2100
+ SYNTAX INTEGER {
2101
+ idle(1),
2102
+ acquisition(2),
2103
+ down(3),
2104
+ up(4),
2105
+ cease(5)
2106
+ }
2107
+ ACCESS read-only
2108
+ STATUS mandatory
2109
+ DESCRIPTION
2110
+ "The EGP state of the local system with respect to
2111
+ this entry's EGP neighbor. Each EGP state is
2112
+ represented by a value that is one greater than
2113
+ the numerical value associated with said state in
2114
+ RFC 904."
2115
+ ::= { egpNeighEntry 1 }
2116
+
2117
+ egpNeighAddr OBJECT-TYPE
2118
+ SYNTAX IpAddress
2119
+ ACCESS read-only
2120
+ STATUS mandatory
2121
+ DESCRIPTION
2122
+ "The IP address of this entry's EGP neighbor."
2123
+ ::= { egpNeighEntry 2 }
2124
+
2125
+ egpNeighAs OBJECT-TYPE
2126
+ SYNTAX INTEGER
2127
+ ACCESS read-only
2128
+ STATUS mandatory
2129
+ DESCRIPTION
2130
+ "The autonomous system of this EGP peer. Zero
2131
+ should be specified if the autonomous system
2132
+ number of the neighbor is not yet known."
2133
+ ::= { egpNeighEntry 3 }
2134
+
2135
+ egpNeighInMsgs OBJECT-TYPE
2136
+ SYNTAX Counter
2137
+ ACCESS read-only
2138
+ STATUS mandatory
2139
+ DESCRIPTION
2140
+ "The number of EGP messages received without error
2141
+ from this EGP peer."
2142
+ ::= { egpNeighEntry 4 }
2143
+
2144
+ egpNeighInErrs OBJECT-TYPE
2145
+ SYNTAX Counter
2146
+ ACCESS read-only
2147
+ STATUS mandatory
2148
+ DESCRIPTION
2149
+ "The number of EGP messages received from this EGP
2150
+ peer that proved to be in error (e.g., bad EGP
2151
+ checksum)."
2152
+ ::= { egpNeighEntry 5 }
2153
+
2154
+ egpNeighOutMsgs OBJECT-TYPE
2155
+ SYNTAX Counter
2156
+ ACCESS read-only
2157
+ STATUS mandatory
2158
+ DESCRIPTION
2159
+ "The number of locally generated EGP messages to
2160
+ this EGP peer."
2161
+ ::= { egpNeighEntry 6 }
2162
+
2163
+ egpNeighOutErrs OBJECT-TYPE
2164
+ SYNTAX Counter
2165
+ ACCESS read-only
2166
+ STATUS mandatory
2167
+ DESCRIPTION
2168
+ "The number of locally generated EGP messages not
2169
+ sent to this EGP peer due to resource limitations
2170
+ within an EGP entity."
2171
+ ::= { egpNeighEntry 7 }
2172
+
2173
+ egpNeighInErrMsgs OBJECT-TYPE
2174
+ SYNTAX Counter
2175
+ ACCESS read-only
2176
+ STATUS mandatory
2177
+ DESCRIPTION
2178
+ "The number of EGP-defined error messages received
2179
+ from this EGP peer."
2180
+ ::= { egpNeighEntry 8 }
2181
+
2182
+ egpNeighOutErrMsgs OBJECT-TYPE
2183
+ SYNTAX Counter
2184
+ ACCESS read-only
2185
+ STATUS mandatory
2186
+ DESCRIPTION
2187
+ "The number of EGP-defined error messages sent to
2188
+ this EGP peer."
2189
+ ::= { egpNeighEntry 9 }
2190
+
2191
+ egpNeighStateUps OBJECT-TYPE
2192
+ SYNTAX Counter
2193
+ ACCESS read-only
2194
+ STATUS mandatory
2195
+ DESCRIPTION
2196
+ "The number of EGP state transitions to the UP
2197
+ state with this EGP peer."
2198
+ ::= { egpNeighEntry 10 }
2199
+
2200
+ egpNeighStateDowns OBJECT-TYPE
2201
+ SYNTAX Counter
2202
+ ACCESS read-only
2203
+ STATUS mandatory
2204
+ DESCRIPTION
2205
+ "The number of EGP state transitions from the UP
2206
+ state to any other state with this EGP peer."
2207
+ ::= { egpNeighEntry 11 }
2208
+
2209
+ egpNeighIntervalHello OBJECT-TYPE
2210
+ SYNTAX INTEGER
2211
+ ACCESS read-only
2212
+ STATUS mandatory
2213
+ DESCRIPTION
2214
+ "The interval between EGP Hello command
2215
+ retransmissions (in hundredths of a second). This
2216
+ represents the t1 timer as defined in RFC 904."
2217
+ ::= { egpNeighEntry 12 }
2218
+
2219
+ egpNeighIntervalPoll OBJECT-TYPE
2220
+ SYNTAX INTEGER
2221
+ ACCESS read-only
2222
+ STATUS mandatory
2223
+ DESCRIPTION
2224
+ "The interval between EGP poll command
2225
+
2226
+ retransmissions (in hundredths of a second). This
2227
+ represents the t3 timer as defined in RFC 904."
2228
+ ::= { egpNeighEntry 13 }
2229
+
2230
+ egpNeighMode OBJECT-TYPE
2231
+ SYNTAX INTEGER { active(1), passive(2) }
2232
+ ACCESS read-only
2233
+ STATUS mandatory
2234
+ DESCRIPTION
2235
+ "The polling mode of this EGP entity, either
2236
+ passive or active."
2237
+ ::= { egpNeighEntry 14 }
2238
+
2239
+ egpNeighEventTrigger OBJECT-TYPE
2240
+ SYNTAX INTEGER { start(1), stop(2) }
2241
+ ACCESS read-write
2242
+ STATUS mandatory
2243
+ DESCRIPTION
2244
+ "A control variable used to trigger operator-
2245
+ initiated Start and Stop events. When read, this
2246
+ variable always returns the most recent value that
2247
+ egpNeighEventTrigger was set to. If it has not
2248
+ been set since the last initialization of the
2249
+ network management subsystem on the node, it
2250
+ returns a value of `stop'.
2251
+
2252
+ When set, this variable causes a Start or Stop
2253
+ event on the specified neighbor, as specified on
2254
+ pages 8-10 of RFC 904. Briefly, a Start event
2255
+ causes an Idle peer to begin neighbor acquisition
2256
+ and a non-Idle peer to reinitiate neighbor
2257
+ acquisition. A stop event causes a non-Idle peer
2258
+ to return to the Idle state until a Start event
2259
+ occurs, either via egpNeighEventTrigger or
2260
+ otherwise."
2261
+ ::= { egpNeighEntry 15 }
2262
+
2263
+ -- additional EGP objects
2264
+
2265
+ egpAs OBJECT-TYPE
2266
+ SYNTAX INTEGER
2267
+ ACCESS read-only
2268
+ STATUS mandatory
2269
+ DESCRIPTION
2270
+ "The autonomous system number of this EGP entity."
2271
+ ::= { egp 6 }
2272
+
2273
+ -- the Transmission group
2274
+
2275
+ -- Based on the transmission media underlying each interface
2276
+ -- on a system, the corresponding portion of the Transmission
2277
+ -- group is mandatory for that system.
2278
+
2279
+ -- When Internet-standard definitions for managing
2280
+ -- transmission media are defined, the transmission group is
2281
+ -- used to provide a prefix for the names of those objects.
2282
+
2283
+ -- Typically, such definitions reside in the experimental
2284
+ -- portion of the MIB until they are "proven", then as a
2285
+ -- part of the Internet standardization process, the
2286
+ -- definitions are accordingly elevated and a new object
2287
+ -- identifier, under the transmission group is defined. By
2288
+ -- convention, the name assigned is:
2289
+ --
2290
+ -- type OBJECT IDENTIFIER ::= { transmission number }
2291
+ --
2292
+ -- where "type" is the symbolic value used for the media in
2293
+ -- the ifType column of the ifTable object, and "number" is
2294
+ -- the actual integer value corresponding to the symbol.
2295
+
2296
+ -- the SNMP group
2297
+
2298
+ -- Implementation of the SNMP group is mandatory for all
2299
+ -- systems which support an SNMP protocol entity. Some of
2300
+ -- the objects defined below will be zero-valued in those
2301
+ -- SNMP implementations that are optimized to support only
2302
+ -- those functions specific to either a management agent or
2303
+ -- a management station. In particular, it should be
2304
+ -- observed that the objects below refer to an SNMP entity,
2305
+ -- and there may be several SNMP entities residing on a
2306
+ -- managed node (e.g., if the node is hosting acting as
2307
+ -- a management station).
2308
+
2309
+ snmpInPkts OBJECT-TYPE
2310
+ SYNTAX Counter
2311
+ ACCESS read-only
2312
+ STATUS mandatory
2313
+ DESCRIPTION
2314
+ "The total number of Messages delivered to the
2315
+ SNMP entity from the transport service."
2316
+ ::= { snmp 1 }
2317
+
2318
+ snmpOutPkts OBJECT-TYPE
2319
+ SYNTAX Counter
2320
+ ACCESS read-only
2321
+ STATUS mandatory
2322
+ DESCRIPTION
2323
+ "The total number of SNMP Messages which were
2324
+ passed from the SNMP protocol entity to the
2325
+ transport service."
2326
+ ::= { snmp 2 }
2327
+
2328
+ snmpInBadVersions OBJECT-TYPE
2329
+ SYNTAX Counter
2330
+ ACCESS read-only
2331
+ STATUS mandatory
2332
+ DESCRIPTION
2333
+ "The total number of SNMP Messages which were
2334
+ delivered to the SNMP protocol entity and were for
2335
+ an unsupported SNMP version."
2336
+ ::= { snmp 3 }
2337
+
2338
+ snmpInBadCommunityNames OBJECT-TYPE
2339
+ SYNTAX Counter
2340
+ ACCESS read-only
2341
+ STATUS mandatory
2342
+ DESCRIPTION
2343
+ "The total number of SNMP Messages delivered to
2344
+ the SNMP protocol entity which used a SNMP
2345
+ community name not known to said entity."
2346
+ ::= { snmp 4 }
2347
+
2348
+ snmpInBadCommunityUses OBJECT-TYPE
2349
+ SYNTAX Counter
2350
+ ACCESS read-only
2351
+ STATUS mandatory
2352
+ DESCRIPTION
2353
+ "The total number of SNMP Messages delivered to
2354
+ the SNMP protocol entity which represented an SNMP
2355
+ operation which was not allowed by the SNMP
2356
+ community named in the Message."
2357
+ ::= { snmp 5 }
2358
+
2359
+ snmpInASNParseErrs OBJECT-TYPE
2360
+ SYNTAX Counter
2361
+ ACCESS read-only
2362
+ STATUS mandatory
2363
+ DESCRIPTION
2364
+ "The total number of ASN.1 or BER errors
2365
+ encountered by the SNMP protocol entity when
2366
+ decoding received SNMP Messages."
2367
+ ::= { snmp 6 }
2368
+
2369
+ -- { snmp 7 } is not used
2370
+
2371
+ snmpInTooBigs OBJECT-TYPE
2372
+ SYNTAX Counter
2373
+ ACCESS read-only
2374
+ STATUS mandatory
2375
+ DESCRIPTION
2376
+ "The total number of SNMP PDUs which were
2377
+ delivered to the SNMP protocol entity and for
2378
+ which the value of the error-status field is
2379
+ `tooBig'."
2380
+ ::= { snmp 8 }
2381
+
2382
+ snmpInNoSuchNames OBJECT-TYPE
2383
+ SYNTAX Counter
2384
+ ACCESS read-only
2385
+ STATUS mandatory
2386
+ DESCRIPTION
2387
+ "The total number of SNMP PDUs which were
2388
+ delivered to the SNMP protocol entity and for
2389
+ which the value of the error-status field is
2390
+ `noSuchName'."
2391
+ ::= { snmp 9 }
2392
+
2393
+ snmpInBadValues OBJECT-TYPE
2394
+ SYNTAX Counter
2395
+ ACCESS read-only
2396
+ STATUS mandatory
2397
+ DESCRIPTION
2398
+ "The total number of SNMP PDUs which were
2399
+ delivered to the SNMP protocol entity and for
2400
+ which the value of the error-status field is
2401
+ `badValue'."
2402
+ ::= { snmp 10 }
2403
+
2404
+ snmpInReadOnlys OBJECT-TYPE
2405
+ SYNTAX Counter
2406
+ ACCESS read-only
2407
+ STATUS mandatory
2408
+ DESCRIPTION
2409
+ "The total number valid SNMP PDUs which were
2410
+ delivered to the SNMP protocol entity and for
2411
+ which the value of the error-status field is
2412
+ `readOnly'. It should be noted that it is a
2413
+ protocol error to generate an SNMP PDU which
2414
+ contains the value `readOnly' in the error-status
2415
+ field, as such this object is provided as a means
2416
+ of detecting incorrect implementations of the
2417
+
2418
+ SNMP."
2419
+ ::= { snmp 11 }
2420
+
2421
+ snmpInGenErrs OBJECT-TYPE
2422
+ SYNTAX Counter
2423
+ ACCESS read-only
2424
+ STATUS mandatory
2425
+ DESCRIPTION
2426
+ "The total number of SNMP PDUs which were
2427
+ delivered to the SNMP protocol entity and for
2428
+ which the value of the error-status field is
2429
+ `genErr'."
2430
+ ::= { snmp 12 }
2431
+
2432
+ snmpInTotalReqVars OBJECT-TYPE
2433
+ SYNTAX Counter
2434
+ ACCESS read-only
2435
+ STATUS mandatory
2436
+ DESCRIPTION
2437
+ "The total number of MIB objects which have been
2438
+ retrieved successfully by the SNMP protocol entity
2439
+ as the result of receiving valid SNMP Get-Request
2440
+ and Get-Next PDUs."
2441
+ ::= { snmp 13 }
2442
+
2443
+ snmpInTotalSetVars OBJECT-TYPE
2444
+ SYNTAX Counter
2445
+ ACCESS read-only
2446
+ STATUS mandatory
2447
+ DESCRIPTION
2448
+ "The total number of MIB objects which have been
2449
+ altered successfully by the SNMP protocol entity
2450
+ as the result of receiving valid SNMP Set-Request
2451
+ PDUs."
2452
+ ::= { snmp 14 }
2453
+
2454
+ snmpInGetRequests OBJECT-TYPE
2455
+ SYNTAX Counter
2456
+ ACCESS read-only
2457
+ STATUS mandatory
2458
+ DESCRIPTION
2459
+ "The total number of SNMP Get-Request PDUs which
2460
+ have been accepted and processed by the SNMP
2461
+ protocol entity."
2462
+ ::= { snmp 15 }
2463
+
2464
+ snmpInGetNexts OBJECT-TYPE
2465
+ SYNTAX Counter
2466
+ ACCESS read-only
2467
+ STATUS mandatory
2468
+ DESCRIPTION
2469
+ "The total number of SNMP Get-Next PDUs which have
2470
+ been accepted and processed by the SNMP protocol
2471
+ entity."
2472
+ ::= { snmp 16 }
2473
+
2474
+ snmpInSetRequests OBJECT-TYPE
2475
+ SYNTAX Counter
2476
+ ACCESS read-only
2477
+ STATUS mandatory
2478
+ DESCRIPTION
2479
+ "The total number of SNMP Set-Request PDUs which
2480
+ have been accepted and processed by the SNMP
2481
+ protocol entity."
2482
+ ::= { snmp 17 }
2483
+
2484
+ snmpInGetResponses OBJECT-TYPE
2485
+ SYNTAX Counter
2486
+ ACCESS read-only
2487
+ STATUS mandatory
2488
+ DESCRIPTION
2489
+ "The total number of SNMP Get-Response PDUs which
2490
+ have been accepted and processed by the SNMP
2491
+ protocol entity."
2492
+ ::= { snmp 18 }
2493
+
2494
+ snmpInTraps OBJECT-TYPE
2495
+ SYNTAX Counter
2496
+ ACCESS read-only
2497
+ STATUS mandatory
2498
+ DESCRIPTION
2499
+ "The total number of SNMP Trap PDUs which have
2500
+ been accepted and processed by the SNMP protocol
2501
+ entity."
2502
+ ::= { snmp 19 }
2503
+
2504
+ snmpOutTooBigs OBJECT-TYPE
2505
+ SYNTAX Counter
2506
+ ACCESS read-only
2507
+ STATUS mandatory
2508
+ DESCRIPTION
2509
+ "The total number of SNMP PDUs which were
2510
+ generated by the SNMP protocol entity and for
2511
+ which the value of the error-status field is
2512
+ `tooBig.'"
2513
+ ::= { snmp 20 }
2514
+
2515
+ snmpOutNoSuchNames OBJECT-TYPE
2516
+ SYNTAX Counter
2517
+ ACCESS read-only
2518
+ STATUS mandatory
2519
+ DESCRIPTION
2520
+ "The total number of SNMP PDUs which were
2521
+ generated by the SNMP protocol entity and for
2522
+ which the value of the error-status is
2523
+ `noSuchName'."
2524
+ ::= { snmp 21 }
2525
+
2526
+ snmpOutBadValues OBJECT-TYPE
2527
+ SYNTAX Counter
2528
+ ACCESS read-only
2529
+ STATUS mandatory
2530
+ DESCRIPTION
2531
+ "The total number of SNMP PDUs which were
2532
+ generated by the SNMP protocol entity and for
2533
+ which the value of the error-status field is
2534
+ `badValue'."
2535
+ ::= { snmp 22 }
2536
+
2537
+ -- { snmp 23 } is not used
2538
+
2539
+ snmpOutGenErrs OBJECT-TYPE
2540
+ SYNTAX Counter
2541
+ ACCESS read-only
2542
+ STATUS mandatory
2543
+ DESCRIPTION
2544
+ "The total number of SNMP PDUs which were
2545
+ generated by the SNMP protocol entity and for
2546
+ which the value of the error-status field is
2547
+ `genErr'."
2548
+ ::= { snmp 24 }
2549
+
2550
+ snmpOutGetRequests OBJECT-TYPE
2551
+ SYNTAX Counter
2552
+ ACCESS read-only
2553
+ STATUS mandatory
2554
+ DESCRIPTION
2555
+ "The total number of SNMP Get-Request PDUs which
2556
+ have been generated by the SNMP protocol entity."
2557
+ ::= { snmp 25 }
2558
+
2559
+ snmpOutGetNexts OBJECT-TYPE
2560
+ SYNTAX Counter
2561
+ ACCESS read-only
2562
+ STATUS mandatory
2563
+ DESCRIPTION
2564
+ "The total number of SNMP Get-Next PDUs which have
2565
+ been generated by the SNMP protocol entity."
2566
+ ::= { snmp 26 }
2567
+
2568
+ snmpOutSetRequests OBJECT-TYPE
2569
+ SYNTAX Counter
2570
+ ACCESS read-only
2571
+ STATUS mandatory
2572
+ DESCRIPTION
2573
+ "The total number of SNMP Set-Request PDUs which
2574
+ have been generated by the SNMP protocol entity."
2575
+ ::= { snmp 27 }
2576
+
2577
+ snmpOutGetResponses OBJECT-TYPE
2578
+ SYNTAX Counter
2579
+ ACCESS read-only
2580
+ STATUS mandatory
2581
+ DESCRIPTION
2582
+ "The total number of SNMP Get-Response PDUs which
2583
+ have been generated by the SNMP protocol entity."
2584
+ ::= { snmp 28 }
2585
+
2586
+ snmpOutTraps OBJECT-TYPE
2587
+ SYNTAX Counter
2588
+ ACCESS read-only
2589
+ STATUS mandatory
2590
+ DESCRIPTION
2591
+ "The total number of SNMP Trap PDUs which have
2592
+ been generated by the SNMP protocol entity."
2593
+ ::= { snmp 29 }
2594
+
2595
+ snmpEnableAuthenTraps OBJECT-TYPE
2596
+ SYNTAX INTEGER { enabled(1), disabled(2) }
2597
+ ACCESS read-write
2598
+ STATUS mandatory
2599
+ DESCRIPTION
2600
+ "Indicates whether the SNMP agent process is
2601
+ permitted to generate authentication-failure
2602
+ traps. The value of this object overrides any
2603
+ configuration information; as such, it provides a
2604
+ means whereby all authentication-failure traps may
2605
+ be disabled.
2606
+
2607
+ Note that it is strongly recommended that this
2608
+ object be stored in non-volatile memory so that it
2609
+ remains constant between re-initializations of the
2610
+ network management system."
2611
+ ::= { snmp 30 }
2612
+
2613
+ END