« back to all changes in this revision
Viewing changes to mibs/RMON-MIB.txt
- browse files at revision 44
- compare with another revision
- download diff
- download tarball
- view history from revision 44
- Committer: Bazaar Package Importer
- Author(s): Chuck Short
- Date: 2010-06-28 14:59:36 UTC
- mfrom: (1.2.3 upstream) (1.1.12 sid)
- Revision ID: james.westby@ubuntu.com-20100628145936-cbiallic69pn044g
Tags: 5.4.3~dfsg-1ubuntu1
* Merge from debian unstable. Remaining changes:
- Set Ubuntu maintainer address.
- net-snmp-config: Use bash. (LP: #104738)
- Removed multiuser option when calling update-rc.d. (LP: #254261)
- debian/snmpd.init: LSBify the init script.
- debian/patches/52_fix_snmpcmd_1_typo.patch: Adjust a typo in snmpcmd.1
(LP: #250459)
- debian/snmpd.postinst: source debconf before doing work, LP: #589056
- debian/snmp.preinst, debian/snmp.prerm: kill any/all processes owned by
snmp user before install/uninstall, LP: #573391
- Add apport hook (LP: #533603):
- debian/{snmp,snmpd}.apport: Added.
- debian/control: Build-depends on dh-apport.
- debian/rules:
+ Add --with apport.
+ override_dh_apport to install hook on snmpd package only.
* Dropped patches:
- debian/patches/99-fix-ubuntu-div0.patch: Fix dvision by zero..
- Set Ubuntu maintainer address.
- net-snmp-config: Use bash. (LP: #104738)
- Removed multiuser option when calling update-rc.d. (LP: #254261)
- debian/snmpd.init: LSBify the init script.
- debian/patches/52_fix_snmpcmd_1_typo.patch: Adjust a typo in snmpcmd.1
(LP: #250459)
- debian/snmpd.postinst: source debconf before doing work, LP: #589056
- debian/snmp.preinst, debian/snmp.prerm: kill any/all processes owned by
snmp user before install/uninstall, LP: #573391
- Add apport hook (LP: #533603):
- debian/{snmp,snmpd}.apport: Added.
- debian/control: Build-depends on dh-apport.
- debian/rules:
+ Add --with apport.
+ override_dh_apport to install hook on snmpd package only.
* Dropped patches:
- debian/patches/99-fix-ubuntu-div0.patch: Fix dvision by zero..
- files added:
- .pc
- .pc/02_statistics.patch
- .pc/02_statistics.patch/agent
- .pc/02_statistics.patch/agent/mibgroup
- .pc/02_statistics.patch/agent/mibgroup/mibII
- .pc/03_makefiles.patch
- .pc/03_makefiles.patch/local
- .pc/03_makefiles.patch/mibs
- .pc/05_searchdirs.patch
- .pc/05_searchdirs.patch/local
- .pc/06_extramibs.patch
- .pc/06_extramibs.patch/mibs
- .pc/07_docfiles.patch
- .pc/08_defaultconfig.patch
- .pc/25_duplicate_iftable.patch
- .pc/25_duplicate_iftable.patch/agent
- .pc/25_duplicate_iftable.patch/agent/mibgroup
- .pc/25_duplicate_iftable.patch/agent/mibgroup/if-mib
- .pc/25_duplicate_iftable.patch/agent/mibgroup/if-mib/data_access
- .pc/25_duplicate_iftable.patch/agent/mibgroup/if-mib/ifTable
- .pc/25_duplicate_iftable.patch/snmplib
- .pc/26_kfreebsd.patch
- .pc/26_kfreebsd.patch/agent
- .pc/26_kfreebsd.patch/agent/mibgroup
- .pc/26_kfreebsd.patch/agent/mibgroup/hardware
- .pc/26_kfreebsd.patch/agent/mibgroup/hardware/cpu
- .pc/26_kfreebsd.patch/include
- .pc/26_kfreebsd.patch/include/net-snmp
- .pc/26_kfreebsd.patch/include/net-snmp/system
- .pc/32_mnttab_path.patch
- .pc/44_nlist_kvm.patch
- .pc/56_manpage.patch
- .pc/56_manpage.patch/man
- .pc/60_libsensors_api.patch
- .pc/60_libsensors_api.patch/agent
- .pc/60_libsensors_api.patch/agent/mibgroup
- .pc/60_libsensors_api.patch/agent/mibgroup/ucd-snmp
- .pc/61_vacm_missing_dependency_check.patch
- .pc/61_vacm_missing_dependency_check.patch/agent
- .pc/61_vacm_missing_dependency_check.patch/apps
- .pc/62_add_lib_cflags.patch
- debian/source
- files removed:
- debian/README.source
- files modified:
- CHANGES
- dist/extractnews *
added
removed
mibs/RMON-MIB.txt
1
RMON-MIB DEFINITIONS ::= BEGIN
2
3
IMPORTS
4
MODULE-IDENTITY, OBJECT-TYPE, OBJECT-IDENTITY,
5
NOTIFICATION-TYPE, mib-2, Counter32,
6
Integer32, TimeTicks FROM SNMPv2-SMI
7
8
TEXTUAL-CONVENTION, DisplayString FROM SNMPv2-TC
9
10
MODULE-COMPLIANCE, OBJECT-GROUP,
11
NOTIFICATION-GROUP FROM SNMPv2-CONF;
12
13
14
rmonMibModule MODULE-IDENTITY
15
LAST-UPDATED "200005110000Z" -- 11 May, 2000
16
ORGANIZATION "IETF RMON MIB Working Group"
17
CONTACT-INFO
18
"Steve Waldbusser
19
Phone: +1-650-948-6500
20
Fax: +1-650-745-0671
21
Email: waldbusser@nextbeacon.com"
22
DESCRIPTION
23
"Remote network monitoring devices, often called
24
monitors or probes, are instruments that exist for
25
the purpose of managing a network. This MIB defines
26
objects for managing remote network monitoring devices."
27
28
REVISION "200005110000Z" -- 11 May, 2000
29
DESCRIPTION
30
"Reformatted into SMIv2 format.
31
32
This version published as RFC 2819."
33
34
REVISION "199502010000Z" -- 1 Feb, 1995
35
DESCRIPTION
36
"Bug fixes, clarifications and minor changes based on
37
implementation experience, published as RFC1757 [18].
38
39
Two changes were made to object definitions:
40
41
1) A new status bit has been defined for the
42
captureBufferPacketStatus object, indicating that the
43
packet order within the capture buffer may not be identical to
44
the packet order as received off the wire. This bit may only
45
46
be used for packets transmitted by the probe. Older NMS
47
applications can safely ignore this status bit, which might be
48
used by newer agents.
49
50
2) The packetMatch trap has been removed. This trap was never
51
actually 'approved' and was not added to this document along
52
with the risingAlarm and fallingAlarm traps. The packetMatch
53
trap could not be throttled, which could cause disruption of
54
normal network traffic under some circumstances. An NMS should
55
configure a risingAlarm threshold on the appropriate
56
channelMatches instance if a trap is desired for a packetMatch
57
event. Note that logging of packetMatch events is still
58
supported--only trap generation for such events has been
59
removed.
60
61
In addition, several clarifications to individual object
62
definitions have been added to assist agent and NMS
63
implementors:
64
65
- global definition of 'good packets' and 'bad packets'
66
67
- more detailed text governing conceptual row creation and
68
modification
69
70
- instructions for probes relating to interface changes and
71
disruptions
72
73
- clarification of some ethernet counter definitions
74
75
- recommended formula for calculating network utilization
76
77
- clarification of channel and captureBuffer behavior for some
78
unusual conditions
79
80
- examples of proper instance naming for each table"
81
82
REVISION "199111010000Z" -- 1 Nov, 1991
83
DESCRIPTION
84
"The original version of this MIB, published as RFC1271."
85
::= { rmonConformance 8 }
86
87
rmon OBJECT IDENTIFIER ::= { mib-2 16 }
88
89
-- textual conventions
90
91
OwnerString ::= TEXTUAL-CONVENTION
92
STATUS current
93
DESCRIPTION
94
"This data type is used to model an administratively
95
assigned name of the owner of a resource. Implementations
96
must accept values composed of well-formed NVT ASCII
97
sequences. In addition, implementations should accept
98
values composed of well-formed UTF-8 sequences.
99
100
It is suggested that this name contain one or more of
101
the following: IP address, management station name,
102
network manager's name, location, or phone number.
103
In some cases the agent itself will be the owner of
104
an entry. In these cases, this string shall be set
105
to a string starting with 'monitor'.
106
107
SNMP access control is articulated entirely in terms
108
of the contents of MIB views; access to a particular
109
SNMP object instance depends only upon its presence
110
or absence in a particular MIB view and never upon
111
its value or the value of related object instances.
112
Thus, objects of this type afford resolution of
113
resource contention only among cooperating
114
managers; they realize no access control function
115
with respect to uncooperative parties."
116
SYNTAX OCTET STRING (SIZE (0..127))
117
118
EntryStatus ::= TEXTUAL-CONVENTION
119
STATUS current
120
DESCRIPTION
121
"The status of a table entry.
122
123
Setting this object to the value invalid(4) has the
124
effect of invalidating the corresponding entry.
125
That is, it effectively disassociates the mapping
126
identified with said entry.
127
It is an implementation-specific matter as to whether
128
the agent removes an invalidated entry from the table.
129
Accordingly, management stations must be prepared to
130
receive tabular information from agents that corresponds
131
to entries currently not in use. Proper
132
interpretation of such entries requires examination
133
of the relevant EntryStatus object.
134
135
An existing instance of this object cannot be set to
136
createRequest(2). This object may only be set to
137
createRequest(2) when this instance is created. When
138
this object is created, the agent may wish to create
139
supplemental object instances with default values
140
to complete a conceptual row in this table. Because the
141
142
creation of these default objects is entirely at the option
143
of the agent, the manager must not assume that any will be
144
created, but may make use of any that are created.
145
Immediately after completing the create operation, the agent
146
must set this object to underCreation(3).
147
148
When in the underCreation(3) state, an entry is allowed to
149
exist in a possibly incomplete, possibly inconsistent state,
150
usually to allow it to be modified in multiple PDUs. When in
151
this state, an entry is not fully active.
152
Entries shall exist in the underCreation(3) state until
153
the management station is finished configuring the entry
154
and sets this object to valid(1) or aborts, setting this
155
object to invalid(4). If the agent determines that an
156
entry has been in the underCreation(3) state for an
157
abnormally long time, it may decide that the management
158
station has crashed. If the agent makes this decision,
159
it may set this object to invalid(4) to reclaim the
160
entry. A prudent agent will understand that the
161
management station may need to wait for human input
162
and will allow for that possibility in its
163
determination of this abnormally long period.
164
165
An entry in the valid(1) state is fully configured and
166
consistent and fully represents the configuration or
167
operation such a row is intended to represent. For
168
example, it could be a statistical function that is
169
configured and active, or a filter that is available
170
in the list of filters processed by the packet capture
171
process.
172
173
A manager is restricted to changing the state of an entry in
174
the following ways:
175
176
To: valid createRequest underCreation invalid
177
From:
178
valid OK NO OK OK
179
createRequest N/A N/A N/A N/A
180
underCreation OK NO OK OK
181
invalid NO NO NO OK
182
nonExistent NO OK NO OK
183
184
In the table above, it is not applicable to move the state
185
from the createRequest state to any other state because the
186
manager will never find the variable in that state. The
187
nonExistent state is not a value of the enumeration, rather
188
it means that the entryStatus variable does not exist at all.
189
190
An agent may allow an entryStatus variable to change state in
191
additional ways, so long as the semantics of the states are
192
followed. This allowance is made to ease the implementation of
193
the agent and is made despite the fact that managers should
194
never exercise these additional state transitions."
195
SYNTAX INTEGER {
196
valid(1),
197
createRequest(2),
198
underCreation(3),
199
invalid(4)
200
}
201
202
statistics OBJECT IDENTIFIER ::= { rmon 1 }
203
history OBJECT IDENTIFIER ::= { rmon 2 }
204
alarm OBJECT IDENTIFIER ::= { rmon 3 }
205
hosts OBJECT IDENTIFIER ::= { rmon 4 }
206
hostTopN OBJECT IDENTIFIER ::= { rmon 5 }
207
matrix OBJECT IDENTIFIER ::= { rmon 6 }
208
filter OBJECT IDENTIFIER ::= { rmon 7 }
209
capture OBJECT IDENTIFIER ::= { rmon 8 }
210
event OBJECT IDENTIFIER ::= { rmon 9 }
211
rmonConformance OBJECT IDENTIFIER ::= { rmon 20 }
212
213
--
214
--
215
--
216
217
etherStatsTable OBJECT-TYPE
218
SYNTAX SEQUENCE OF EtherStatsEntry
219
MAX-ACCESS not-accessible
220
STATUS current
221
DESCRIPTION
222
"A list of Ethernet statistics entries."
223
::= { statistics 1 }
224
225
etherStatsEntry OBJECT-TYPE
226
SYNTAX EtherStatsEntry
227
MAX-ACCESS not-accessible
228
STATUS current
229
DESCRIPTION
230
"A collection of statistics kept for a particular
231
Ethernet interface. As an example, an instance of the
232
etherStatsPkts object might be named etherStatsPkts.1"
233
INDEX { etherStatsIndex }
234
::= { etherStatsTable 1 }
235
236
EtherStatsEntry ::= SEQUENCE {
237
etherStatsIndex Integer32,
238
etherStatsDataSource OBJECT IDENTIFIER,
239
etherStatsDropEvents Counter32,
240
etherStatsOctets Counter32,
241
etherStatsPkts Counter32,
242
etherStatsBroadcastPkts Counter32,
243
etherStatsMulticastPkts Counter32,
244
etherStatsCRCAlignErrors Counter32,
245
etherStatsUndersizePkts Counter32,
246
etherStatsOversizePkts Counter32,
247
etherStatsFragments Counter32,
248
etherStatsJabbers Counter32,
249
etherStatsCollisions Counter32,
250
etherStatsPkts64Octets Counter32,
251
etherStatsPkts65to127Octets Counter32,
252
etherStatsPkts128to255Octets Counter32,
253
etherStatsPkts256to511Octets Counter32,
254
etherStatsPkts512to1023Octets Counter32,
255
etherStatsPkts1024to1518Octets Counter32,
256
etherStatsOwner OwnerString,
257
etherStatsStatus EntryStatus
258
}
259
260
etherStatsIndex OBJECT-TYPE
261
SYNTAX Integer32 (1..65535)
262
MAX-ACCESS read-only
263
STATUS current
264
DESCRIPTION
265
"The value of this object uniquely identifies this
266
etherStats entry."
267
::= { etherStatsEntry 1 }
268
269
etherStatsDataSource OBJECT-TYPE
270
SYNTAX OBJECT IDENTIFIER
271
MAX-ACCESS read-create
272
STATUS current
273
DESCRIPTION
274
"This object identifies the source of the data that
275
this etherStats entry is configured to analyze. This
276
source can be any ethernet interface on this device.
277
In order to identify a particular interface, this object
278
shall identify the instance of the ifIndex object,
279
defined in RFC 2233 [17], for the desired interface.
280
For example, if an entry were to receive data from
281
interface #1, this object would be set to ifIndex.1.
282
283
The statistics in this group reflect all packets
284
on the local network segment attached to the identified
285
interface.
286
287
An agent may or may not be able to tell if fundamental
288
changes to the media of the interface have occurred and
289
necessitate an invalidation of this entry. For example, a
290
hot-pluggable ethernet card could be pulled out and replaced
291
by a token-ring card. In such a case, if the agent has such
292
knowledge of the change, it is recommended that it
293
invalidate this entry.
294
295
This object may not be modified if the associated
296
etherStatsStatus object is equal to valid(1)."
297
::= { etherStatsEntry 2 }
298
299
etherStatsDropEvents OBJECT-TYPE
300
SYNTAX Counter32
301
MAX-ACCESS read-only
302
STATUS current
303
DESCRIPTION
304
"The total number of events in which packets
305
were dropped by the probe due to lack of resources.
306
Note that this number is not necessarily the number of
307
packets dropped; it is just the number of times this
308
condition has been detected."
309
::= { etherStatsEntry 3 }
310
311
etherStatsOctets OBJECT-TYPE
312
SYNTAX Counter32
313
UNITS "Octets"
314
MAX-ACCESS read-only
315
STATUS current
316
DESCRIPTION
317
"The total number of octets of data (including
318
those in bad packets) received on the
319
network (excluding framing bits but including
320
FCS octets).
321
322
This object can be used as a reasonable estimate of
323
10-Megabit ethernet utilization. If greater precision is
324
desired, the etherStatsPkts and etherStatsOctets objects
325
should be sampled before and after a common interval. The
326
differences in the sampled values are Pkts and Octets,
327
respectively, and the number of seconds in the interval is
328
Interval. These values are used to calculate the Utilization
329
as follows:
330
331
Pkts * (9.6 + 6.4) + (Octets * .8)
332
Utilization = -------------------------------------
333
Interval * 10,000
334
335
The result of this equation is the value Utilization which
336
is the percent utilization of the ethernet segment on a
337
scale of 0 to 100 percent."
338
::= { etherStatsEntry 4 }
339
340
etherStatsPkts OBJECT-TYPE
341
SYNTAX Counter32
342
UNITS "Packets"
343
MAX-ACCESS read-only
344
STATUS current
345
DESCRIPTION
346
"The total number of packets (including bad packets,
347
broadcast packets, and multicast packets) received."
348
::= { etherStatsEntry 5 }
349
350
etherStatsBroadcastPkts OBJECT-TYPE
351
SYNTAX Counter32
352
UNITS "Packets"
353
MAX-ACCESS read-only
354
STATUS current
355
DESCRIPTION
356
"The total number of good packets received that were
357
directed to the broadcast address. Note that this
358
does not include multicast packets."
359
::= { etherStatsEntry 6 }
360
361
etherStatsMulticastPkts OBJECT-TYPE
362
SYNTAX Counter32
363
UNITS "Packets"
364
MAX-ACCESS read-only
365
STATUS current
366
DESCRIPTION
367
"The total number of good packets received that were
368
directed to a multicast address. Note that this number
369
does not include packets directed to the broadcast
370
371
address."
372
::= { etherStatsEntry 7 }
373
374
etherStatsCRCAlignErrors OBJECT-TYPE
375
SYNTAX Counter32
376
UNITS "Packets"
377
MAX-ACCESS read-only
378
STATUS current
379
DESCRIPTION
380
"The total number of packets received that
381
had a length (excluding framing bits, but
382
including FCS octets) of between 64 and 1518
383
octets, inclusive, but had either a bad
384
Frame Check Sequence (FCS) with an integral
385
number of octets (FCS Error) or a bad FCS with
386
a non-integral number of octets (Alignment Error)."
387
::= { etherStatsEntry 8 }
388
389
etherStatsUndersizePkts OBJECT-TYPE
390
SYNTAX Counter32
391
UNITS "Packets"
392
MAX-ACCESS read-only
393
STATUS current
394
DESCRIPTION
395
"The total number of packets received that were
396
less than 64 octets long (excluding framing bits,
397
but including FCS octets) and were otherwise well
398
formed."
399
::= { etherStatsEntry 9 }
400
401
etherStatsOversizePkts OBJECT-TYPE
402
SYNTAX Counter32
403
UNITS "Packets"
404
MAX-ACCESS read-only
405
STATUS current
406
DESCRIPTION
407
"The total number of packets received that were
408
longer than 1518 octets (excluding framing bits,
409
but including FCS octets) and were otherwise
410
well formed."
411
::= { etherStatsEntry 10 }
412
413
etherStatsFragments OBJECT-TYPE
414
SYNTAX Counter32
415
UNITS "Packets"
416
MAX-ACCESS read-only
417
STATUS current
418
DESCRIPTION
419
"The total number of packets received that were less than
420
64 octets in length (excluding framing bits but including
421
FCS octets) and had either a bad Frame Check Sequence
422
(FCS) with an integral number of octets (FCS Error) or a
423
bad FCS with a non-integral number of octets (Alignment
424
Error).
425
426
Note that it is entirely normal for etherStatsFragments to
427
increment. This is because it counts both runts (which are
428
normal occurrences due to collisions) and noise hits."
429
::= { etherStatsEntry 11 }
430
431
etherStatsJabbers OBJECT-TYPE
432
SYNTAX Counter32
433
UNITS "Packets"
434
MAX-ACCESS read-only
435
STATUS current
436
DESCRIPTION
437
"The total number of packets received that were
438
longer than 1518 octets (excluding framing bits,
439
but including FCS octets), and had either a bad
440
Frame Check Sequence (FCS) with an integral number
441
of octets (FCS Error) or a bad FCS with a non-integral
442
number of octets (Alignment Error).
443
444
Note that this definition of jabber is different
445
than the definition in IEEE-802.3 section 8.2.1.5
446
(10BASE5) and section 10.3.1.4 (10BASE2). These
447
documents define jabber as the condition where any
448
packet exceeds 20 ms. The allowed range to detect
449
jabber is between 20 ms and 150 ms."
450
::= { etherStatsEntry 12 }
451
452
etherStatsCollisions OBJECT-TYPE
453
SYNTAX Counter32
454
UNITS "Collisions"
455
MAX-ACCESS read-only
456
STATUS current
457
DESCRIPTION
458
"The best estimate of the total number of collisions
459
on this Ethernet segment.
460
461
The value returned will depend on the location of the
462
RMON probe. Section 8.2.1.3 (10BASE-5) and section
463
10.3.1.3 (10BASE-2) of IEEE standard 802.3 states that a
464
station must detect a collision, in the receive mode, if
465
three or more stations are transmitting simultaneously. A
466
repeater port must detect a collision when two or more
467
468
stations are transmitting simultaneously. Thus a probe
469
placed on a repeater port could record more collisions
470
than a probe connected to a station on the same segment
471
would.
472
473
Probe location plays a much smaller role when considering
474
10BASE-T. 14.2.1.4 (10BASE-T) of IEEE standard 802.3
475
defines a collision as the simultaneous presence of signals
476
on the DO and RD circuits (transmitting and receiving
477
at the same time). A 10BASE-T station can only detect
478
collisions when it is transmitting. Thus probes placed on
479
a station and a repeater, should report the same number of
480
collisions.
481
482
Note also that an RMON probe inside a repeater should
483
ideally report collisions between the repeater and one or
484
more other hosts (transmit collisions as defined by IEEE
485
802.3k) plus receiver collisions observed on any coax
486
segments to which the repeater is connected."
487
::= { etherStatsEntry 13 }
488
489
etherStatsPkts64Octets OBJECT-TYPE
490
SYNTAX Counter32
491
UNITS "Packets"
492
MAX-ACCESS read-only
493
STATUS current
494
DESCRIPTION
495
"The total number of packets (including bad
496
packets) received that were 64 octets in length
497
(excluding framing bits but including FCS octets)."
498
::= { etherStatsEntry 14 }
499
500
etherStatsPkts65to127Octets OBJECT-TYPE
501
SYNTAX Counter32
502
UNITS "Packets"
503
MAX-ACCESS read-only
504
STATUS current
505
DESCRIPTION
506
"The total number of packets (including bad
507
packets) received that were between
508
65 and 127 octets in length inclusive
509
(excluding framing bits but including FCS octets)."
510
::= { etherStatsEntry 15 }
511
512
etherStatsPkts128to255Octets OBJECT-TYPE
513
SYNTAX Counter32
514
UNITS "Packets"
515
MAX-ACCESS read-only
516
STATUS current
517
DESCRIPTION
518
"The total number of packets (including bad
519
packets) received that were between
520
128 and 255 octets in length inclusive
521
(excluding framing bits but including FCS octets)."
522
::= { etherStatsEntry 16 }
523
524
etherStatsPkts256to511Octets OBJECT-TYPE
525
SYNTAX Counter32
526
UNITS "Packets"
527
MAX-ACCESS read-only
528
STATUS current
529
DESCRIPTION
530
"The total number of packets (including bad
531
packets) received that were between
532
256 and 511 octets in length inclusive
533
(excluding framing bits but including FCS octets)."
534
::= { etherStatsEntry 17 }
535
536
etherStatsPkts512to1023Octets OBJECT-TYPE
537
SYNTAX Counter32
538
UNITS "Packets"
539
MAX-ACCESS read-only
540
STATUS current
541
DESCRIPTION
542
"The total number of packets (including bad
543
packets) received that were between
544
512 and 1023 octets in length inclusive
545
(excluding framing bits but including FCS octets)."
546
::= { etherStatsEntry 18 }
547
548
etherStatsPkts1024to1518Octets OBJECT-TYPE
549
SYNTAX Counter32
550
UNITS "Packets"
551
MAX-ACCESS read-only
552
STATUS current
553
DESCRIPTION
554
"The total number of packets (including bad
555
packets) received that were between
556
1024 and 1518 octets in length inclusive
557
(excluding framing bits but including FCS octets)."
558
::= { etherStatsEntry 19 }
559
560
etherStatsOwner OBJECT-TYPE
561
SYNTAX OwnerString
562
MAX-ACCESS read-create
563
STATUS current
564
DESCRIPTION
565
"The entity that configured this entry and is therefore
566
using the resources assigned to it."
567
::= { etherStatsEntry 20 }
568
569
etherStatsStatus OBJECT-TYPE
570
SYNTAX EntryStatus
571
MAX-ACCESS read-create
572
STATUS current
573
DESCRIPTION
574
"The status of this etherStats entry."
575
::= { etherStatsEntry 21 }
576
577
578
--
579
--
580
--
581
582
historyControlTable OBJECT-TYPE
583
SYNTAX SEQUENCE OF HistoryControlEntry
584
MAX-ACCESS not-accessible
585
STATUS current
586
DESCRIPTION
587
"A list of history control entries."
588
::= { history 1 }
589
590
historyControlEntry OBJECT-TYPE
591
SYNTAX HistoryControlEntry
592
MAX-ACCESS not-accessible
593
STATUS current
594
DESCRIPTION
595
"A list of parameters that set up a periodic sampling of
596
statistics. As an example, an instance of the
597
historyControlInterval object might be named
598
historyControlInterval.2"
599
INDEX { historyControlIndex }
600
::= { historyControlTable 1 }
601
602
HistoryControlEntry ::= SEQUENCE {
603
historyControlIndex Integer32,
604
historyControlDataSource OBJECT IDENTIFIER,
605
historyControlBucketsRequested Integer32,
606
historyControlBucketsGranted Integer32,
607
historyControlInterval Integer32,
608
historyControlOwner OwnerString,
609
historyControlStatus EntryStatus
610
}
611
612
historyControlIndex OBJECT-TYPE
613
SYNTAX Integer32 (1..65535)
614
MAX-ACCESS read-only
615
STATUS current
616
DESCRIPTION
617
"An index that uniquely identifies an entry in the
618
historyControl table. Each such entry defines a
619
set of samples at a particular interval for an
620
interface on the device."
621
::= { historyControlEntry 1 }
622
623
historyControlDataSource OBJECT-TYPE
624
SYNTAX OBJECT IDENTIFIER
625
MAX-ACCESS read-create
626
STATUS current
627
DESCRIPTION
628
"This object identifies the source of the data for
629
which historical data was collected and
630
placed in a media-specific table on behalf of this
631
historyControlEntry. This source can be any
632
interface on this device. In order to identify
633
634
a particular interface, this object shall identify
635
the instance of the ifIndex object, defined
636
in RFC 2233 [17], for the desired interface.
637
For example, if an entry were to receive data from
638
interface #1, this object would be set to ifIndex.1.
639
640
The statistics in this group reflect all packets
641
on the local network segment attached to the identified
642
interface.
643
644
An agent may or may not be able to tell if fundamental
645
changes to the media of the interface have occurred and
646
necessitate an invalidation of this entry. For example, a
647
hot-pluggable ethernet card could be pulled out and replaced
648
by a token-ring card. In such a case, if the agent has such
649
knowledge of the change, it is recommended that it
650
invalidate this entry.
651
652
This object may not be modified if the associated
653
historyControlStatus object is equal to valid(1)."
654
::= { historyControlEntry 2 }
655
656
historyControlBucketsRequested OBJECT-TYPE
657
SYNTAX Integer32 (1..65535)
658
MAX-ACCESS read-create
659
STATUS current
660
DESCRIPTION
661
"The requested number of discrete time intervals
662
over which data is to be saved in the part of the
663
media-specific table associated with this
664
historyControlEntry.
665
666
When this object is created or modified, the probe
667
should set historyControlBucketsGranted as closely to
668
this object as is possible for the particular probe
669
implementation and available resources."
670
DEFVAL { 50 }
671
::= { historyControlEntry 3 }
672
673
historyControlBucketsGranted OBJECT-TYPE
674
SYNTAX Integer32 (1..65535)
675
MAX-ACCESS read-only
676
STATUS current
677
DESCRIPTION
678
"The number of discrete sampling intervals
679
over which data shall be saved in the part of
680
the media-specific table associated with this
681
historyControlEntry.
682
683
When the associated historyControlBucketsRequested
684
object is created or modified, the probe
685
should set this object as closely to the requested
686
value as is possible for the particular
687
probe implementation and available resources. The
688
probe must not lower this value except as a result
689
of a modification to the associated
690
historyControlBucketsRequested object.
691
692
There will be times when the actual number of
693
buckets associated with this entry is less than
694
the value of this object. In this case, at the
695
end of each sampling interval, a new bucket will
696
be added to the media-specific table.
697
698
When the number of buckets reaches the value of
699
this object and a new bucket is to be added to the
700
media-specific table, the oldest bucket associated
701
with this historyControlEntry shall be deleted by
702
the agent so that the new bucket can be added.
703
704
When the value of this object changes to a value less
705
than the current value, entries are deleted
706
from the media-specific table associated with this
707
historyControlEntry. Enough of the oldest of these
708
entries shall be deleted by the agent so that their
709
number remains less than or equal to the new value of
710
this object.
711
712
When the value of this object changes to a value greater
713
than the current value, the number of associated media-
714
specific entries may be allowed to grow."
715
::= { historyControlEntry 4 }
716
717
historyControlInterval OBJECT-TYPE
718
SYNTAX Integer32 (1..3600)
719
UNITS "Seconds"
720
MAX-ACCESS read-create
721
STATUS current
722
DESCRIPTION
723
"The interval in seconds over which the data is
724
sampled for each bucket in the part of the
725
media-specific table associated with this
726
historyControlEntry. This interval can
727
be set to any number of seconds between 1 and
728
3600 (1 hour).
729
730
Because the counters in a bucket may overflow at their
731
732
maximum value with no indication, a prudent manager will
733
take into account the possibility of overflow in any of
734
the associated counters. It is important to consider the
735
minimum time in which any counter could overflow on a
736
particular media type and set the historyControlInterval
737
object to a value less than this interval. This is
738
typically most important for the 'octets' counter in any
739
media-specific table. For example, on an Ethernet
740
network, the etherHistoryOctets counter could overflow
741
in about one hour at the Ethernet's maximum
742
utilization.
743
744
This object may not be modified if the associated
745
historyControlStatus object is equal to valid(1)."
746
DEFVAL { 1800 }
747
::= { historyControlEntry 5 }
748
749
historyControlOwner OBJECT-TYPE
750
SYNTAX OwnerString
751
MAX-ACCESS read-create
752
STATUS current
753
DESCRIPTION
754
"The entity that configured this entry and is therefore
755
using the resources assigned to it."
756
::= { historyControlEntry 6 }
757
758
historyControlStatus OBJECT-TYPE
759
SYNTAX EntryStatus
760
MAX-ACCESS read-create
761
STATUS current
762
DESCRIPTION
763
"The status of this historyControl entry.
764
765
Each instance of the media-specific table associated
766
with this historyControlEntry will be deleted by the agent
767
if this historyControlEntry is not equal to valid(1)."
768
::= { historyControlEntry 7 }
769
770
771
--
772
773
--
774
775
etherHistoryTable OBJECT-TYPE
776
SYNTAX SEQUENCE OF EtherHistoryEntry
777
MAX-ACCESS not-accessible
778
STATUS current
779
DESCRIPTION
780
"A list of Ethernet history entries."
781
::= { history 2 }
782
783
etherHistoryEntry OBJECT-TYPE
784
SYNTAX EtherHistoryEntry
785
MAX-ACCESS not-accessible
786
STATUS current
787
DESCRIPTION
788
"An historical sample of Ethernet statistics on a particular
789
Ethernet interface. This sample is associated with the
790
historyControlEntry which set up the parameters for
791
a regular collection of these samples. As an example, an
792
instance of the etherHistoryPkts object might be named
793
etherHistoryPkts.2.89"
794
INDEX { etherHistoryIndex , etherHistorySampleIndex }
795
::= { etherHistoryTable 1 }
796
797
EtherHistoryEntry ::= SEQUENCE {
798
etherHistoryIndex Integer32,
799
etherHistorySampleIndex Integer32,
800
etherHistoryIntervalStart TimeTicks,
801
etherHistoryDropEvents Counter32,
802
etherHistoryOctets Counter32,
803
etherHistoryPkts Counter32,
804
etherHistoryBroadcastPkts Counter32,
805
etherHistoryMulticastPkts Counter32,
806
etherHistoryCRCAlignErrors Counter32,
807
etherHistoryUndersizePkts Counter32,
808
etherHistoryOversizePkts Counter32,
809
etherHistoryFragments Counter32,
810
etherHistoryJabbers Counter32,
811
etherHistoryCollisions Counter32,
812
etherHistoryUtilization Integer32
813
}
814
815
etherHistoryIndex OBJECT-TYPE
816
SYNTAX Integer32 (1..65535)
817
MAX-ACCESS read-only
818
STATUS current
819
DESCRIPTION
820
"The history of which this entry is a part. The
821
history identified by a particular value of this
822
index is the same history as identified
823
by the same value of historyControlIndex."
824
::= { etherHistoryEntry 1 }
825
826
etherHistorySampleIndex OBJECT-TYPE
827
SYNTAX Integer32 (1..2147483647)
828
MAX-ACCESS read-only
829
STATUS current
830
DESCRIPTION
831
"An index that uniquely identifies the particular
832
sample this entry represents among all samples
833
associated with the same historyControlEntry.
834
This index starts at 1 and increases by one
835
as each new sample is taken."
836
::= { etherHistoryEntry 2 }
837
838
etherHistoryIntervalStart OBJECT-TYPE
839
SYNTAX TimeTicks
840
MAX-ACCESS read-only
841
STATUS current
842
DESCRIPTION
843
"The value of sysUpTime at the start of the interval
844
over which this sample was measured. If the probe
845
keeps track of the time of day, it should start
846
the first sample of the history at a time such that
847
when the next hour of the day begins, a sample is
848
started at that instant. Note that following this
849
rule may require the probe to delay collecting the
850
first sample of the history, as each sample must be
851
of the same interval. Also note that the sample which
852
is currently being collected is not accessible in this
853
table until the end of its interval."
854
::= { etherHistoryEntry 3 }
855
856
etherHistoryDropEvents OBJECT-TYPE
857
SYNTAX Counter32
858
MAX-ACCESS read-only
859
STATUS current
860
DESCRIPTION
861
"The total number of events in which packets
862
were dropped by the probe due to lack of resources
863
during this sampling interval. Note that this number
864
is not necessarily the number of packets dropped, it
865
is just the number of times this condition has been
866
867
detected."
868
::= { etherHistoryEntry 4 }
869
870
etherHistoryOctets OBJECT-TYPE
871
SYNTAX Counter32
872
UNITS "Octets"
873
MAX-ACCESS read-only
874
STATUS current
875
DESCRIPTION
876
"The total number of octets of data (including
877
those in bad packets) received on the
878
network (excluding framing bits but including
879
FCS octets)."
880
::= { etherHistoryEntry 5 }
881
882
etherHistoryPkts OBJECT-TYPE
883
SYNTAX Counter32
884
UNITS "Packets"
885
MAX-ACCESS read-only
886
STATUS current
887
DESCRIPTION
888
"The number of packets (including bad packets)
889
received during this sampling interval."
890
::= { etherHistoryEntry 6 }
891
892
etherHistoryBroadcastPkts OBJECT-TYPE
893
SYNTAX Counter32
894
UNITS "Packets"
895
MAX-ACCESS read-only
896
STATUS current
897
DESCRIPTION
898
"The number of good packets received during this
899
sampling interval that were directed to the
900
broadcast address."
901
::= { etherHistoryEntry 7 }
902
903
etherHistoryMulticastPkts OBJECT-TYPE
904
SYNTAX Counter32
905
UNITS "Packets"
906
MAX-ACCESS read-only
907
STATUS current
908
DESCRIPTION
909
"The number of good packets received during this
910
sampling interval that were directed to a
911
multicast address. Note that this number does not
912
include packets addressed to the broadcast address."
913
::= { etherHistoryEntry 8 }
914
915
etherHistoryCRCAlignErrors OBJECT-TYPE
916
SYNTAX Counter32
917
UNITS "Packets"
918
MAX-ACCESS read-only
919
STATUS current
920
DESCRIPTION
921
"The number of packets received during this
922
sampling interval that had a length (excluding
923
framing bits but including FCS octets) between
924
64 and 1518 octets, inclusive, but had either a bad Frame
925
Check Sequence (FCS) with an integral number of octets
926
(FCS Error) or a bad FCS with a non-integral number
927
of octets (Alignment Error)."
928
::= { etherHistoryEntry 9 }
929
930
etherHistoryUndersizePkts OBJECT-TYPE
931
SYNTAX Counter32
932
UNITS "Packets"
933
MAX-ACCESS read-only
934
STATUS current
935
DESCRIPTION
936
"The number of packets received during this
937
sampling interval that were less than 64 octets
938
long (excluding framing bits but including FCS
939
octets) and were otherwise well formed."
940
::= { etherHistoryEntry 10 }
941
942
etherHistoryOversizePkts OBJECT-TYPE
943
SYNTAX Counter32
944
UNITS "Packets"
945
MAX-ACCESS read-only
946
STATUS current
947
DESCRIPTION
948
"The number of packets received during this
949
sampling interval that were longer than 1518
950
octets (excluding framing bits but including
951
FCS octets) but were otherwise well formed."
952
::= { etherHistoryEntry 11 }
953
954
etherHistoryFragments OBJECT-TYPE
955
SYNTAX Counter32
956
UNITS "Packets"
957
MAX-ACCESS read-only
958
STATUS current
959
DESCRIPTION
960
"The total number of packets received during this
961
sampling interval that were less than 64 octets in
962
length (excluding framing bits but including FCS
963
964
octets) had either a bad Frame Check Sequence (FCS)
965
with an integral number of octets (FCS Error) or a bad
966
FCS with a non-integral number of octets (Alignment
967
Error).
968
969
Note that it is entirely normal for etherHistoryFragments to
970
increment. This is because it counts both runts (which are
971
normal occurrences due to collisions) and noise hits."
972
::= { etherHistoryEntry 12 }
973
974
etherHistoryJabbers OBJECT-TYPE
975
SYNTAX Counter32
976
UNITS "Packets"
977
MAX-ACCESS read-only
978
STATUS current
979
DESCRIPTION
980
"The number of packets received during this
981
sampling interval that were longer than 1518 octets
982
(excluding framing bits but including FCS octets),
983
and had either a bad Frame Check Sequence (FCS)
984
with an integral number of octets (FCS Error) or
985
a bad FCS with a non-integral number of octets
986
(Alignment Error).
987
988
Note that this definition of jabber is different
989
than the definition in IEEE-802.3 section 8.2.1.5
990
(10BASE5) and section 10.3.1.4 (10BASE2). These
991
documents define jabber as the condition where any
992
packet exceeds 20 ms. The allowed range to detect
993
jabber is between 20 ms and 150 ms."
994
::= { etherHistoryEntry 13 }
995
996
etherHistoryCollisions OBJECT-TYPE
997
SYNTAX Counter32
998
UNITS "Collisions"
999
MAX-ACCESS read-only
1000
STATUS current
1001
DESCRIPTION
1002
"The best estimate of the total number of collisions
1003
on this Ethernet segment during this sampling
1004
interval.
1005
1006
The value returned will depend on the location of the
1007
RMON probe. Section 8.2.1.3 (10BASE-5) and section
1008
10.3.1.3 (10BASE-2) of IEEE standard 802.3 states that a
1009
station must detect a collision, in the receive mode, if
1010
three or more stations are transmitting simultaneously. A
1011
repeater port must detect a collision when two or more
1012
1013
stations are transmitting simultaneously. Thus a probe
1014
placed on a repeater port could record more collisions
1015
than a probe connected to a station on the same segment
1016
would.
1017
1018
Probe location plays a much smaller role when considering
1019
10BASE-T. 14.2.1.4 (10BASE-T) of IEEE standard 802.3
1020
defines a collision as the simultaneous presence of signals
1021
on the DO and RD circuits (transmitting and receiving
1022
at the same time). A 10BASE-T station can only detect
1023
collisions when it is transmitting. Thus probes placed on
1024
a station and a repeater, should report the same number of
1025
collisions.
1026
1027
Note also that an RMON probe inside a repeater should
1028
ideally report collisions between the repeater and one or
1029
more other hosts (transmit collisions as defined by IEEE
1030
802.3k) plus receiver collisions observed on any coax
1031
segments to which the repeater is connected."
1032
::= { etherHistoryEntry 14 }
1033
1034
etherHistoryUtilization OBJECT-TYPE
1035
SYNTAX Integer32 (0..10000)
1036
MAX-ACCESS read-only
1037
STATUS current
1038
DESCRIPTION
1039
"The best estimate of the mean physical layer
1040
network utilization on this interface during this
1041
sampling interval, in hundredths of a percent."
1042
::= { etherHistoryEntry 15 }
1043
1044
1045
--
1046
--
1047
1048
--
1049
1050
alarmTable OBJECT-TYPE
1051
SYNTAX SEQUENCE OF AlarmEntry
1052
MAX-ACCESS not-accessible
1053
STATUS current
1054
DESCRIPTION
1055
"A list of alarm entries."
1056
::= { alarm 1 }
1057
1058
alarmEntry OBJECT-TYPE
1059
SYNTAX AlarmEntry
1060
MAX-ACCESS not-accessible
1061
STATUS current
1062
DESCRIPTION
1063
"A list of parameters that set up a periodic checking
1064
for alarm conditions. For example, an instance of the
1065
alarmValue object might be named alarmValue.8"
1066
INDEX { alarmIndex }
1067
::= { alarmTable 1 }
1068
1069
AlarmEntry ::= SEQUENCE {
1070
alarmIndex Integer32,
1071
alarmInterval Integer32,
1072
alarmVariable OBJECT IDENTIFIER,
1073
alarmSampleType INTEGER,
1074
alarmValue Integer32,
1075
alarmStartupAlarm INTEGER,
1076
alarmRisingThreshold Integer32,
1077
alarmFallingThreshold Integer32,
1078
alarmRisingEventIndex Integer32,
1079
alarmFallingEventIndex Integer32,
1080
alarmOwner OwnerString,
1081
alarmStatus EntryStatus
1082
}
1083
1084
alarmIndex OBJECT-TYPE
1085
SYNTAX Integer32 (1..65535)
1086
MAX-ACCESS read-only
1087
STATUS current
1088
DESCRIPTION
1089
"An index that uniquely identifies an entry in the
1090
alarm table. Each such entry defines a
1091
diagnostic sample at a particular interval
1092
for an object on the device."
1093
::= { alarmEntry 1 }
1094
1095
alarmInterval OBJECT-TYPE
1096
SYNTAX Integer32
1097
UNITS "Seconds"
1098
MAX-ACCESS read-create
1099
STATUS current
1100
DESCRIPTION
1101
"The interval in seconds over which the data is
1102
sampled and compared with the rising and falling
1103
thresholds. When setting this variable, care
1104
should be taken in the case of deltaValue
1105
sampling - the interval should be set short enough
1106
that the sampled variable is very unlikely to
1107
increase or decrease by more than 2^31 - 1 during
1108
a single sampling interval.
1109
1110
This object may not be modified if the associated
1111
alarmStatus object is equal to valid(1)."
1112
::= { alarmEntry 2 }
1113
1114
alarmVariable OBJECT-TYPE
1115
SYNTAX OBJECT IDENTIFIER
1116
MAX-ACCESS read-create
1117
STATUS current
1118
DESCRIPTION
1119
"The object identifier of the particular variable to be
1120
sampled. Only variables that resolve to an ASN.1 primitive
1121
type of INTEGER (INTEGER, Integer32, Counter32, Counter64,
1122
Gauge, or TimeTicks) may be sampled.
1123
1124
Because SNMP access control is articulated entirely
1125
in terms of the contents of MIB views, no access
1126
control mechanism exists that can restrict the value of
1127
this object to identify only those objects that exist
1128
in a particular MIB view. Because there is thus no
1129
acceptable means of restricting the read access that
1130
could be obtained through the alarm mechanism, the
1131
probe must only grant write access to this object in
1132
1133
those views that have read access to all objects on
1134
the probe.
1135
1136
During a set operation, if the supplied variable name is
1137
not available in the selected MIB view, a badValue error
1138
must be returned. If at any time the variable name of
1139
an established alarmEntry is no longer available in the
1140
selected MIB view, the probe must change the status of
1141
this alarmEntry to invalid(4).
1142
1143
This object may not be modified if the associated
1144
alarmStatus object is equal to valid(1)."
1145
::= { alarmEntry 3 }
1146
1147
alarmSampleType OBJECT-TYPE
1148
SYNTAX INTEGER {
1149
absoluteValue(1),
1150
deltaValue(2)
1151
}
1152
MAX-ACCESS read-create
1153
STATUS current
1154
DESCRIPTION
1155
"The method of sampling the selected variable and
1156
calculating the value to be compared against the
1157
thresholds. If the value of this object is
1158
absoluteValue(1), the value of the selected variable
1159
will be compared directly with the thresholds at the
1160
end of the sampling interval. If the value of this
1161
object is deltaValue(2), the value of the selected
1162
variable at the last sample will be subtracted from
1163
the current value, and the difference compared with
1164
the thresholds.
1165
1166
This object may not be modified if the associated
1167
alarmStatus object is equal to valid(1)."
1168
::= { alarmEntry 4 }
1169
1170
alarmValue OBJECT-TYPE
1171
SYNTAX Integer32
1172
MAX-ACCESS read-only
1173
STATUS current
1174
DESCRIPTION
1175
"The value of the statistic during the last sampling
1176
period. For example, if the sample type is deltaValue,
1177
this value will be the difference between the samples
1178
at the beginning and end of the period. If the sample
1179
type is absoluteValue, this value will be the sampled
1180
value at the end of the period.
1181
1182
This is the value that is compared with the rising and
1183
falling thresholds.
1184
1185
The value during the current sampling period is not
1186
made available until the period is completed and will
1187
remain available until the next period completes."
1188
::= { alarmEntry 5 }
1189
1190
alarmStartupAlarm OBJECT-TYPE
1191
SYNTAX INTEGER {
1192
risingAlarm(1),
1193
fallingAlarm(2),
1194
risingOrFallingAlarm(3)
1195
}
1196
MAX-ACCESS read-create
1197
STATUS current
1198
DESCRIPTION
1199
"The alarm that may be sent when this entry is first
1200
set to valid. If the first sample after this entry
1201
becomes valid is greater than or equal to the
1202
risingThreshold and alarmStartupAlarm is equal to
1203
risingAlarm(1) or risingOrFallingAlarm(3), then a single
1204
rising alarm will be generated. If the first sample
1205
after this entry becomes valid is less than or equal
1206
to the fallingThreshold and alarmStartupAlarm is equal
1207
to fallingAlarm(2) or risingOrFallingAlarm(3), then a
1208
single falling alarm will be generated.
1209
1210
This object may not be modified if the associated
1211
alarmStatus object is equal to valid(1)."
1212
::= { alarmEntry 6 }
1213
1214
alarmRisingThreshold OBJECT-TYPE
1215
SYNTAX Integer32
1216
MAX-ACCESS read-create
1217
STATUS current
1218
DESCRIPTION
1219
"A threshold for the sampled statistic. When the current
1220
sampled value is greater than or equal to this threshold,
1221
and the value at the last sampling interval was less than
1222
this threshold, a single event will be generated.
1223
A single event will also be generated if the first
1224
sample after this entry becomes valid is greater than or
1225
equal to this threshold and the associated
1226
alarmStartupAlarm is equal to risingAlarm(1) or
1227
risingOrFallingAlarm(3).
1228
1229
After a rising event is generated, another such event
1230
1231
will not be generated until the sampled value
1232
falls below this threshold and reaches the
1233
alarmFallingThreshold.
1234
1235
This object may not be modified if the associated
1236
alarmStatus object is equal to valid(1)."
1237
::= { alarmEntry 7 }
1238
1239
alarmFallingThreshold OBJECT-TYPE
1240
SYNTAX Integer32
1241
MAX-ACCESS read-create
1242
STATUS current
1243
DESCRIPTION
1244
"A threshold for the sampled statistic. When the current
1245
sampled value is less than or equal to this threshold,
1246
and the value at the last sampling interval was greater than
1247
this threshold, a single event will be generated.
1248
A single event will also be generated if the first
1249
sample after this entry becomes valid is less than or
1250
equal to this threshold and the associated
1251
alarmStartupAlarm is equal to fallingAlarm(2) or
1252
risingOrFallingAlarm(3).
1253
1254
After a falling event is generated, another such event
1255
will not be generated until the sampled value
1256
rises above this threshold and reaches the
1257
alarmRisingThreshold.
1258
1259
This object may not be modified if the associated
1260
alarmStatus object is equal to valid(1)."
1261
::= { alarmEntry 8 }
1262
1263
alarmRisingEventIndex OBJECT-TYPE
1264
SYNTAX Integer32 (0..65535)
1265
MAX-ACCESS read-create
1266
STATUS current
1267
DESCRIPTION
1268
"The index of the eventEntry that is
1269
used when a rising threshold is crossed. The
1270
eventEntry identified by a particular value of
1271
this index is the same as identified by the same value
1272
of the eventIndex object. If there is no
1273
corresponding entry in the eventTable, then
1274
no association exists. In particular, if this value
1275
is zero, no associated event will be generated, as
1276
zero is not a valid event index.
1277
1278
This object may not be modified if the associated
1279
1280
alarmStatus object is equal to valid(1)."
1281
::= { alarmEntry 9 }
1282
1283
alarmFallingEventIndex OBJECT-TYPE
1284
SYNTAX Integer32 (0..65535)
1285
MAX-ACCESS read-create
1286
STATUS current
1287
DESCRIPTION
1288
"The index of the eventEntry that is
1289
used when a falling threshold is crossed. The
1290
eventEntry identified by a particular value of
1291
this index is the same as identified by the same value
1292
of the eventIndex object. If there is no
1293
corresponding entry in the eventTable, then
1294
no association exists. In particular, if this value
1295
is zero, no associated event will be generated, as
1296
zero is not a valid event index.
1297
1298
This object may not be modified if the associated
1299
alarmStatus object is equal to valid(1)."
1300
::= { alarmEntry 10 }
1301
1302
alarmOwner OBJECT-TYPE
1303
SYNTAX OwnerString
1304
MAX-ACCESS read-create
1305
STATUS current
1306
DESCRIPTION
1307
"The entity that configured this entry and is therefore
1308
using the resources assigned to it."
1309
::= { alarmEntry 11 }
1310
1311
alarmStatus OBJECT-TYPE
1312
SYNTAX EntryStatus
1313
MAX-ACCESS read-create
1314
STATUS current
1315
DESCRIPTION
1316
"The status of this alarm entry."
1317
::= { alarmEntry 12 }
1318
1319
1320
--
1321
1322
1323
1324
1325
1326
1327
1328
1329
hostControlTable OBJECT-TYPE
1330
SYNTAX SEQUENCE OF HostControlEntry
1331
MAX-ACCESS not-accessible
1332
STATUS current
1333
DESCRIPTION
1334
"A list of host table control entries."
1335
::= { hosts 1 }
1336
1337
hostControlEntry OBJECT-TYPE
1338
SYNTAX HostControlEntry
1339
MAX-ACCESS not-accessible
1340
STATUS current
1341
DESCRIPTION
1342
"A list of parameters that set up the discovery of hosts
1343
on a particular interface and the collection of statistics
1344
about these hosts. For example, an instance of the
1345
hostControlTableSize object might be named
1346
hostControlTableSize.1"
1347
INDEX { hostControlIndex }
1348
::= { hostControlTable 1 }
1349
1350
HostControlEntry ::= SEQUENCE {
1351
1352
hostControlIndex Integer32,
1353
hostControlDataSource OBJECT IDENTIFIER,
1354
hostControlTableSize Integer32,
1355
hostControlLastDeleteTime TimeTicks,
1356
hostControlOwner OwnerString,
1357
hostControlStatus EntryStatus
1358
}
1359
1360
hostControlIndex OBJECT-TYPE
1361
SYNTAX Integer32 (1..65535)
1362
MAX-ACCESS read-only
1363
STATUS current
1364
DESCRIPTION
1365
"An index that uniquely identifies an entry in the
1366
1367
hostControl table. Each such entry defines
1368
a function that discovers hosts on a particular interface
1369
and places statistics about them in the hostTable and
1370
the hostTimeTable on behalf of this hostControlEntry."
1371
::= { hostControlEntry 1 }
1372
1373
hostControlDataSource OBJECT-TYPE
1374
SYNTAX OBJECT IDENTIFIER
1375
MAX-ACCESS read-create
1376
STATUS current
1377
DESCRIPTION
1378
"This object identifies the source of the data for
1379
this instance of the host function. This source
1380
can be any interface on this device. In order
1381
to identify a particular interface, this object shall
1382
identify the instance of the ifIndex object, defined
1383
in RFC 2233 [17], for the desired interface.
1384
For example, if an entry were to receive data from
1385
interface #1, this object would be set to ifIndex.1.
1386
1387
The statistics in this group reflect all packets
1388
on the local network segment attached to the identified
1389
interface.
1390
1391
An agent may or may not be able to tell if fundamental
1392
changes to the media of the interface have occurred and
1393
necessitate an invalidation of this entry. For example, a
1394
hot-pluggable ethernet card could be pulled out and replaced
1395
by a token-ring card. In such a case, if the agent has such
1396
knowledge of the change, it is recommended that it
1397
invalidate this entry.
1398
1399
This object may not be modified if the associated
1400
hostControlStatus object is equal to valid(1)."
1401
::= { hostControlEntry 2 }
1402
1403
hostControlTableSize OBJECT-TYPE
1404
SYNTAX Integer32
1405
MAX-ACCESS read-only
1406
STATUS current
1407
DESCRIPTION
1408
"The number of hostEntries in the hostTable and the
1409
hostTimeTable associated with this hostControlEntry."
1410
::= { hostControlEntry 3 }
1411
1412
hostControlLastDeleteTime OBJECT-TYPE
1413
SYNTAX TimeTicks
1414
MAX-ACCESS read-only
1415
STATUS current
1416
DESCRIPTION
1417
"The value of sysUpTime when the last entry
1418
was deleted from the portion of the hostTable
1419
associated with this hostControlEntry. If no
1420
deletions have occurred, this value shall be zero."
1421
::= { hostControlEntry 4 }
1422
1423
hostControlOwner OBJECT-TYPE
1424
SYNTAX OwnerString
1425
MAX-ACCESS read-create
1426
STATUS current
1427
DESCRIPTION
1428
"The entity that configured this entry and is therefore
1429
using the resources assigned to it."
1430
::= { hostControlEntry 5 }
1431
1432
hostControlStatus OBJECT-TYPE
1433
SYNTAX EntryStatus
1434
MAX-ACCESS read-create
1435
STATUS current
1436
DESCRIPTION
1437
"The status of this hostControl entry.
1438
1439
If this object is not equal to valid(1), all associated
1440
entries in the hostTable, hostTimeTable, and the
1441
hostTopNTable shall be deleted by the agent."
1442
::= { hostControlEntry 6 }
1443
1444
hostTable OBJECT-TYPE
1445
SYNTAX SEQUENCE OF HostEntry
1446
MAX-ACCESS not-accessible
1447
STATUS current
1448
DESCRIPTION
1449
"A list of host entries."
1450
::= { hosts 2 }
1451
1452
hostEntry OBJECT-TYPE
1453
SYNTAX HostEntry
1454
MAX-ACCESS not-accessible
1455
STATUS current
1456
DESCRIPTION
1457
"A collection of statistics for a particular host that has
1458
been discovered on an interface of this device. For example,
1459
an instance of the hostOutBroadcastPkts object might be
1460
named hostOutBroadcastPkts.1.6.8.0.32.27.3.176"
1461
INDEX { hostIndex, hostAddress }
1462
::= { hostTable 1 }
1463
1464
HostEntry ::= SEQUENCE {
1465
hostAddress OCTET STRING,
1466
hostCreationOrder Integer32,
1467
hostIndex Integer32,
1468
hostInPkts Counter32,
1469
hostOutPkts Counter32,
1470
hostInOctets Counter32,
1471
hostOutOctets Counter32,
1472
hostOutErrors Counter32,
1473
hostOutBroadcastPkts Counter32,
1474
hostOutMulticastPkts Counter32
1475
}
1476
1477
hostAddress OBJECT-TYPE
1478
SYNTAX OCTET STRING
1479
MAX-ACCESS read-only
1480
STATUS current
1481
DESCRIPTION
1482
"The physical address of this host."
1483
::= { hostEntry 1 }
1484
1485
hostCreationOrder OBJECT-TYPE
1486
SYNTAX Integer32 (1..65535)
1487
MAX-ACCESS read-only
1488
STATUS current
1489
DESCRIPTION
1490
"An index that defines the relative ordering of
1491
the creation time of hosts captured for a
1492
particular hostControlEntry. This index shall
1493
be between 1 and N, where N is the value of
1494
the associated hostControlTableSize. The ordering
1495
of the indexes is based on the order of each entry's
1496
insertion into the table, in which entries added earlier
1497
have a lower index value than entries added later.
1498
1499
It is important to note that the order for a
1500
particular entry may change as an (earlier) entry
1501
is deleted from the table. Because this order may
1502
change, management stations should make use of the
1503
hostControlLastDeleteTime variable in the
1504
hostControlEntry associated with the relevant
1505
portion of the hostTable. By observing
1506
this variable, the management station may detect
1507
the circumstances where a previous association
1508
between a value of hostCreationOrder
1509
and a hostEntry may no longer hold."
1510
::= { hostEntry 2 }
1511
1512
hostIndex OBJECT-TYPE
1513
SYNTAX Integer32 (1..65535)
1514
MAX-ACCESS read-only
1515
STATUS current
1516
DESCRIPTION
1517
"The set of collected host statistics of which
1518
this entry is a part. The set of hosts
1519
identified by a particular value of this
1520
index is associated with the hostControlEntry
1521
as identified by the same value of hostControlIndex."
1522
::= { hostEntry 3 }
1523
1524
hostInPkts OBJECT-TYPE
1525
SYNTAX Counter32
1526
UNITS "Packets"
1527
MAX-ACCESS read-only
1528
STATUS current
1529
DESCRIPTION
1530
"The number of good packets transmitted to this
1531
address since it was added to the hostTable."
1532
::= { hostEntry 4 }
1533
1534
hostOutPkts OBJECT-TYPE
1535
SYNTAX Counter32
1536
UNITS "Packets"
1537
MAX-ACCESS read-only
1538
STATUS current
1539
DESCRIPTION
1540
"The number of packets, including bad packets, transmitted
1541
by this address since it was added to the hostTable."
1542
::= { hostEntry 5 }
1543
1544
hostInOctets OBJECT-TYPE
1545
SYNTAX Counter32
1546
UNITS "Octets"
1547
MAX-ACCESS read-only
1548
STATUS current
1549
DESCRIPTION
1550
"The number of octets transmitted to this address since
1551
it was added to the hostTable (excluding framing
1552
bits but including FCS octets), except for those
1553
octets in bad packets."
1554
::= { hostEntry 6 }
1555
1556
hostOutOctets OBJECT-TYPE
1557
SYNTAX Counter32
1558
UNITS "Octets"
1559
MAX-ACCESS read-only
1560
STATUS current
1561
DESCRIPTION
1562
"The number of octets transmitted by this address since
1563
it was added to the hostTable (excluding framing
1564
bits but including FCS octets), including those
1565
octets in bad packets."
1566
::= { hostEntry 7 }
1567
1568
hostOutErrors OBJECT-TYPE
1569
SYNTAX Counter32
1570
UNITS "Packets"
1571
MAX-ACCESS read-only
1572
STATUS current
1573
DESCRIPTION
1574
"The number of bad packets transmitted by this address
1575
since this host was added to the hostTable."
1576
::= { hostEntry 8 }
1577
1578
hostOutBroadcastPkts OBJECT-TYPE
1579
SYNTAX Counter32
1580
UNITS "Packets"
1581
MAX-ACCESS read-only
1582
STATUS current
1583
DESCRIPTION
1584
"The number of good packets transmitted by this
1585
address that were directed to the broadcast address
1586
since this host was added to the hostTable."
1587
::= { hostEntry 9 }
1588
1589
hostOutMulticastPkts OBJECT-TYPE
1590
SYNTAX Counter32
1591
UNITS "Packets"
1592
MAX-ACCESS read-only
1593
STATUS current
1594
DESCRIPTION
1595
"The number of good packets transmitted by this
1596
address that were directed to a multicast address
1597
since this host was added to the hostTable.
1598
Note that this number does not include packets
1599
directed to the broadcast address."
1600
::= { hostEntry 10 }
1601
1602
1603
hostTimeTable OBJECT-TYPE
1604
SYNTAX SEQUENCE OF HostTimeEntry
1605
MAX-ACCESS not-accessible
1606
STATUS current
1607
DESCRIPTION
1608
"A list of time-ordered host table entries."
1609
::= { hosts 3 }
1610
1611
hostTimeEntry OBJECT-TYPE
1612
SYNTAX HostTimeEntry
1613
MAX-ACCESS not-accessible
1614
STATUS current
1615
DESCRIPTION
1616
"A collection of statistics for a particular host that has
1617
been discovered on an interface of this device. This
1618
collection includes the relative ordering of the creation
1619
time of this object. For example, an instance of the
1620
hostTimeOutBroadcastPkts object might be named
1621
hostTimeOutBroadcastPkts.1.687"
1622
INDEX { hostTimeIndex, hostTimeCreationOrder }
1623
::= { hostTimeTable 1 }
1624
1625
HostTimeEntry ::= SEQUENCE {
1626
hostTimeAddress OCTET STRING,
1627
hostTimeCreationOrder Integer32,
1628
hostTimeIndex Integer32,
1629
hostTimeInPkts Counter32,
1630
hostTimeOutPkts Counter32,
1631
hostTimeInOctets Counter32,
1632
hostTimeOutOctets Counter32,
1633
hostTimeOutErrors Counter32,
1634
hostTimeOutBroadcastPkts Counter32,
1635
hostTimeOutMulticastPkts Counter32
1636
}
1637
1638
hostTimeAddress OBJECT-TYPE
1639
SYNTAX OCTET STRING
1640
MAX-ACCESS read-only
1641
STATUS current
1642
DESCRIPTION
1643
"The physical address of this host."
1644
::= { hostTimeEntry 1 }
1645
1646
hostTimeCreationOrder OBJECT-TYPE
1647
SYNTAX Integer32 (1..65535)
1648
MAX-ACCESS read-only
1649
STATUS current
1650
DESCRIPTION
1651
"An index that uniquely identifies an entry in
1652
the hostTime table among those entries associated
1653
with the same hostControlEntry. This index shall
1654
be between 1 and N, where N is the value of
1655
1656
the associated hostControlTableSize. The ordering
1657
of the indexes is based on the order of each entry's
1658
insertion into the table, in which entries added earlier
1659
have a lower index value than entries added later.
1660
Thus the management station has the ability to
1661
learn of new entries added to this table without
1662
downloading the entire table.
1663
1664
It is important to note that the index for a
1665
particular entry may change as an (earlier) entry
1666
is deleted from the table. Because this order may
1667
change, management stations should make use of the
1668
hostControlLastDeleteTime variable in the
1669
hostControlEntry associated with the relevant
1670
portion of the hostTimeTable. By observing
1671
this variable, the management station may detect
1672
the circumstances where a download of the table
1673
may have missed entries, and where a previous
1674
association between a value of hostTimeCreationOrder
1675
and a hostTimeEntry may no longer hold."
1676
::= { hostTimeEntry 2 }
1677
1678
hostTimeIndex OBJECT-TYPE
1679
SYNTAX Integer32 (1..65535)
1680
MAX-ACCESS read-only
1681
STATUS current
1682
DESCRIPTION
1683
"The set of collected host statistics of which
1684
this entry is a part. The set of hosts
1685
identified by a particular value of this
1686
index is associated with the hostControlEntry
1687
as identified by the same value of hostControlIndex."
1688
::= { hostTimeEntry 3 }
1689
1690
hostTimeInPkts OBJECT-TYPE
1691
SYNTAX Counter32
1692
UNITS "Packets"
1693
MAX-ACCESS read-only
1694
STATUS current
1695
DESCRIPTION
1696
"The number of good packets transmitted to this
1697
address since it was added to the hostTimeTable."
1698
::= { hostTimeEntry 4 }
1699
1700
hostTimeOutPkts OBJECT-TYPE
1701
SYNTAX Counter32
1702
UNITS "Packets"
1703
MAX-ACCESS read-only
1704
STATUS current
1705
DESCRIPTION
1706
"The number of packets, including bad packets, transmitted
1707
by this address since it was added to the hostTimeTable."
1708
::= { hostTimeEntry 5 }
1709
1710
hostTimeInOctets OBJECT-TYPE
1711
SYNTAX Counter32
1712
UNITS "Octets"
1713
MAX-ACCESS read-only
1714
STATUS current
1715
DESCRIPTION
1716
"The number of octets transmitted to this address since
1717
it was added to the hostTimeTable (excluding framing
1718
bits but including FCS octets), except for those
1719
octets in bad packets."
1720
::= { hostTimeEntry 6 }
1721
1722
hostTimeOutOctets OBJECT-TYPE
1723
SYNTAX Counter32
1724
UNITS "Octets"
1725
MAX-ACCESS read-only
1726
STATUS current
1727
DESCRIPTION
1728
"The number of octets transmitted by this address since
1729
it was added to the hostTimeTable (excluding framing
1730
bits but including FCS octets), including those
1731
octets in bad packets."
1732
::= { hostTimeEntry 7 }
1733
1734
hostTimeOutErrors OBJECT-TYPE
1735
SYNTAX Counter32
1736
UNITS "Packets"
1737
MAX-ACCESS read-only
1738
STATUS current
1739
DESCRIPTION
1740
"The number of bad packets transmitted by this address
1741
since this host was added to the hostTimeTable."
1742
::= { hostTimeEntry 8 }
1743
1744
hostTimeOutBroadcastPkts OBJECT-TYPE
1745
SYNTAX Counter32
1746
UNITS "Packets"
1747
MAX-ACCESS read-only
1748
STATUS current
1749
DESCRIPTION
1750
"The number of good packets transmitted by this
1751
address that were directed to the broadcast address
1752
1753
since this host was added to the hostTimeTable."
1754
::= { hostTimeEntry 9 }
1755
1756
hostTimeOutMulticastPkts OBJECT-TYPE
1757
SYNTAX Counter32
1758
UNITS "Packets"
1759
MAX-ACCESS read-only
1760
STATUS current
1761
DESCRIPTION
1762
"The number of good packets transmitted by this
1763
address that were directed to a multicast address
1764
since this host was added to the hostTimeTable.
1765
Note that this number does not include packets directed
1766
to the broadcast address."
1767
::= { hostTimeEntry 10 }
1768
1769
1770
--
1771
1772
1773
hostTopNControlTable OBJECT-TYPE
1774
SYNTAX SEQUENCE OF HostTopNControlEntry
1775
MAX-ACCESS not-accessible
1776
STATUS current
1777
DESCRIPTION
1778
"A list of top N host control entries."
1779
::= { hostTopN 1 }
1780
1781
hostTopNControlEntry OBJECT-TYPE
1782
SYNTAX HostTopNControlEntry
1783
MAX-ACCESS not-accessible
1784
STATUS current
1785
DESCRIPTION
1786
"A set of parameters that control the creation of a report
1787
of the top N hosts according to several metrics. For
1788
example, an instance of the hostTopNDuration object might
1789
be named hostTopNDuration.3"
1790
INDEX { hostTopNControlIndex }
1791
::= { hostTopNControlTable 1 }
1792
1793
HostTopNControlEntry ::= SEQUENCE {
1794
hostTopNControlIndex Integer32,
1795
hostTopNHostIndex Integer32,
1796
hostTopNRateBase INTEGER,
1797
hostTopNTimeRemaining Integer32,
1798
hostTopNDuration Integer32,
1799
hostTopNRequestedSize Integer32,
1800
hostTopNGrantedSize Integer32,
1801
hostTopNStartTime TimeTicks,
1802
hostTopNOwner OwnerString,
1803
hostTopNStatus EntryStatus
1804
}
1805
1806
hostTopNControlIndex OBJECT-TYPE
1807
SYNTAX Integer32 (1..65535)
1808
MAX-ACCESS read-only
1809
STATUS current
1810
DESCRIPTION
1811
"An index that uniquely identifies an entry
1812
in the hostTopNControl table. Each such
1813
entry defines one top N report prepared for
1814
one interface."
1815
::= { hostTopNControlEntry 1 }
1816
1817
hostTopNHostIndex OBJECT-TYPE
1818
SYNTAX Integer32 (1..65535)
1819
MAX-ACCESS read-create
1820
STATUS current
1821
DESCRIPTION
1822
"The host table for which a top N report will be prepared
1823
on behalf of this entry. The host table identified by a
1824
particular value of this index is associated with the same
1825
host table as identified by the same value of
1826
hostIndex.
1827
1828
This object may not be modified if the associated
1829
hostTopNStatus object is equal to valid(1)."
1830
::= { hostTopNControlEntry 2 }
1831
1832
hostTopNRateBase OBJECT-TYPE
1833
SYNTAX INTEGER {
1834
hostTopNInPkts(1),
1835
hostTopNOutPkts(2),
1836
hostTopNInOctets(3),
1837
hostTopNOutOctets(4),
1838
hostTopNOutErrors(5),
1839
hostTopNOutBroadcastPkts(6),
1840
hostTopNOutMulticastPkts(7)
1841
}
1842
MAX-ACCESS read-create
1843
STATUS current
1844
DESCRIPTION
1845
"The variable for each host that the hostTopNRate
1846
variable is based upon.
1847
1848
This object may not be modified if the associated
1849
hostTopNStatus object is equal to valid(1)."
1850
::= { hostTopNControlEntry 3 }
1851
1852
hostTopNTimeRemaining OBJECT-TYPE
1853
SYNTAX Integer32
1854
UNITS "Seconds"
1855
MAX-ACCESS read-create
1856
STATUS current
1857
DESCRIPTION
1858
"The number of seconds left in the report currently being
1859
collected. When this object is modified by the management
1860
station, a new collection is started, possibly aborting
1861
a currently running report. The new value is used
1862
as the requested duration of this report, which is
1863
loaded into the associated hostTopNDuration object.
1864
1865
When this object is set to a non-zero value, any
1866
associated hostTopNEntries shall be made
1867
inaccessible by the monitor. While the value of this
1868
object is non-zero, it decrements by one per second until
1869
it reaches zero. During this time, all associated
1870
hostTopNEntries shall remain inaccessible. At the time
1871
that this object decrements to zero, the report is made
1872
accessible in the hostTopNTable. Thus, the hostTopN
1873
table needs to be created only at the end of the collection
1874
interval."
1875
DEFVAL { 0 }
1876
::= { hostTopNControlEntry 4 }
1877
1878
hostTopNDuration OBJECT-TYPE
1879
SYNTAX Integer32
1880
UNITS "Seconds"
1881
MAX-ACCESS read-only
1882
STATUS current
1883
DESCRIPTION
1884
"The number of seconds that this report has collected
1885
during the last sampling interval, or if this
1886
report is currently being collected, the number
1887
of seconds that this report is being collected
1888
during this sampling interval.
1889
1890
When the associated hostTopNTimeRemaining object is set,
1891
this object shall be set by the probe to the same value
1892
and shall not be modified until the next time
1893
the hostTopNTimeRemaining is set.
1894
1895
This value shall be zero if no reports have been
1896
requested for this hostTopNControlEntry."
1897
DEFVAL { 0 }
1898
::= { hostTopNControlEntry 5 }
1899
1900
hostTopNRequestedSize OBJECT-TYPE
1901
SYNTAX Integer32
1902
MAX-ACCESS read-create
1903
STATUS current
1904
DESCRIPTION
1905
"The maximum number of hosts requested for the top N
1906
table.
1907
1908
When this object is created or modified, the probe
1909
should set hostTopNGrantedSize as closely to this
1910
object as is possible for the particular probe
1911
implementation and available resources."
1912
DEFVAL { 10 }
1913
::= { hostTopNControlEntry 6 }
1914
1915
hostTopNGrantedSize OBJECT-TYPE
1916
SYNTAX Integer32
1917
MAX-ACCESS read-only
1918
STATUS current
1919
DESCRIPTION
1920
"The maximum number of hosts in the top N table.
1921
1922
When the associated hostTopNRequestedSize object is
1923
created or modified, the probe should set this
1924
object as closely to the requested value as is possible
1925
for the particular implementation and available
1926
1927
resources. The probe must not lower this value except
1928
as a result of a set to the associated
1929
hostTopNRequestedSize object.
1930
1931
Hosts with the highest value of hostTopNRate shall be
1932
placed in this table in decreasing order of this rate
1933
until there is no more room or until there are no more
1934
hosts."
1935
::= { hostTopNControlEntry 7 }
1936
1937
hostTopNStartTime OBJECT-TYPE
1938
SYNTAX TimeTicks
1939
MAX-ACCESS read-only
1940
STATUS current
1941
DESCRIPTION
1942
"The value of sysUpTime when this top N report was
1943
last started. In other words, this is the time that
1944
the associated hostTopNTimeRemaining object was
1945
modified to start the requested report."
1946
::= { hostTopNControlEntry 8 }
1947
1948
hostTopNOwner OBJECT-TYPE
1949
SYNTAX OwnerString
1950
MAX-ACCESS read-create
1951
STATUS current
1952
DESCRIPTION
1953
"The entity that configured this entry and is therefore
1954
using the resources assigned to it."
1955
::= { hostTopNControlEntry 9 }
1956
1957
hostTopNStatus OBJECT-TYPE
1958
SYNTAX EntryStatus
1959
MAX-ACCESS read-create
1960
STATUS current
1961
DESCRIPTION
1962
"The status of this hostTopNControl entry.
1963
1964
If this object is not equal to valid(1), all associated
1965
hostTopNEntries shall be deleted by the agent."
1966
::= { hostTopNControlEntry 10 }
1967
1968
hostTopNTable OBJECT-TYPE
1969
SYNTAX SEQUENCE OF HostTopNEntry
1970
MAX-ACCESS not-accessible
1971
STATUS current
1972
DESCRIPTION
1973
"A list of top N host entries."
1974
::= { hostTopN 2 }
1975
1976
hostTopNEntry OBJECT-TYPE
1977
SYNTAX HostTopNEntry
1978
MAX-ACCESS not-accessible
1979
STATUS current
1980
DESCRIPTION
1981
"A set of statistics for a host that is part of a top N
1982
report. For example, an instance of the hostTopNRate
1983
object might be named hostTopNRate.3.10"
1984
INDEX { hostTopNReport, hostTopNIndex }
1985
::= { hostTopNTable 1 }
1986
1987
HostTopNEntry ::= SEQUENCE {
1988
hostTopNReport Integer32,
1989
hostTopNIndex Integer32,
1990
hostTopNAddress OCTET STRING,
1991
hostTopNRate Integer32
1992
}
1993
1994
hostTopNReport OBJECT-TYPE
1995
SYNTAX Integer32 (1..65535)
1996
MAX-ACCESS read-only
1997
STATUS current
1998
DESCRIPTION
1999
"This object identifies the top N report of which
2000
this entry is a part. The set of hosts
2001
identified by a particular value of this
2002
object is part of the same report as identified
2003
by the same value of the hostTopNControlIndex object."
2004
::= { hostTopNEntry 1 }
2005
2006
hostTopNIndex OBJECT-TYPE
2007
SYNTAX Integer32 (1..65535)
2008
MAX-ACCESS read-only
2009
STATUS current
2010
DESCRIPTION
2011
"An index that uniquely identifies an entry in
2012
the hostTopN table among those in the same report.
2013
This index is between 1 and N, where N is the
2014
number of entries in this table. Increasing values
2015
of hostTopNIndex shall be assigned to entries with
2016
decreasing values of hostTopNRate until index N
2017
is assigned to the entry with the lowest value of
2018
hostTopNRate or there are no more hostTopNEntries."
2019
::= { hostTopNEntry 2 }
2020
2021
hostTopNAddress OBJECT-TYPE
2022
SYNTAX OCTET STRING
2023
MAX-ACCESS read-only
2024
STATUS current
2025
DESCRIPTION
2026
"The physical address of this host."
2027
::= { hostTopNEntry 3 }
2028
2029
hostTopNRate OBJECT-TYPE
2030
SYNTAX Integer32
2031
MAX-ACCESS read-only
2032
STATUS current
2033
DESCRIPTION
2034
"The amount of change in the selected variable
2035
during this sampling interval. The selected
2036
variable is this host's instance of the object
2037
selected by hostTopNRateBase."
2038
::= { hostTopNEntry 4 }
2039
2040
2041
--
2042
2043
matrixControlTable OBJECT-TYPE
2044
SYNTAX SEQUENCE OF MatrixControlEntry
2045
MAX-ACCESS not-accessible
2046
STATUS current
2047
DESCRIPTION
2048
"A list of information entries for the
2049
traffic matrix on each interface."
2050
::= { matrix 1 }
2051
2052
matrixControlEntry OBJECT-TYPE
2053
SYNTAX MatrixControlEntry
2054
MAX-ACCESS not-accessible
2055
STATUS current
2056
DESCRIPTION
2057
"Information about a traffic matrix on a particular
2058
2059
interface. For example, an instance of the
2060
matrixControlLastDeleteTime object might be named
2061
matrixControlLastDeleteTime.1"
2062
INDEX { matrixControlIndex }
2063
::= { matrixControlTable 1 }
2064
2065
MatrixControlEntry ::= SEQUENCE {
2066
matrixControlIndex Integer32,
2067
matrixControlDataSource OBJECT IDENTIFIER,
2068
matrixControlTableSize Integer32,
2069
matrixControlLastDeleteTime TimeTicks,
2070
matrixControlOwner OwnerString,
2071
matrixControlStatus EntryStatus
2072
}
2073
2074
matrixControlIndex OBJECT-TYPE
2075
SYNTAX Integer32 (1..65535)
2076
MAX-ACCESS read-only
2077
STATUS current
2078
DESCRIPTION
2079
"An index that uniquely identifies an entry in the
2080
matrixControl table. Each such entry defines
2081
a function that discovers conversations on a particular
2082
interface and places statistics about them in the
2083
matrixSDTable and the matrixDSTable on behalf of this
2084
matrixControlEntry."
2085
::= { matrixControlEntry 1 }
2086
2087
matrixControlDataSource OBJECT-TYPE
2088
SYNTAX OBJECT IDENTIFIER
2089
MAX-ACCESS read-create
2090
STATUS current
2091
DESCRIPTION
2092
"This object identifies the source of
2093
the data from which this entry creates a traffic matrix.
2094
This source can be any interface on this device. In
2095
order to identify a particular interface, this object
2096
shall identify the instance of the ifIndex object,
2097
defined in RFC 2233 [17], for the desired
2098
interface. For example, if an entry were to receive data
2099
from interface #1, this object would be set to ifIndex.1.
2100
2101
The statistics in this group reflect all packets
2102
on the local network segment attached to the identified
2103
interface.
2104
2105
An agent may or may not be able to tell if fundamental
2106
changes to the media of the interface have occurred and
2107
2108
necessitate an invalidation of this entry. For example, a
2109
hot-pluggable ethernet card could be pulled out and replaced
2110
by a token-ring card. In such a case, if the agent has such
2111
knowledge of the change, it is recommended that it
2112
invalidate this entry.
2113
2114
This object may not be modified if the associated
2115
matrixControlStatus object is equal to valid(1)."
2116
::= { matrixControlEntry 2 }
2117
2118
matrixControlTableSize OBJECT-TYPE
2119
SYNTAX Integer32
2120
MAX-ACCESS read-only
2121
STATUS current
2122
DESCRIPTION
2123
"The number of matrixSDEntries in the matrixSDTable
2124
for this interface. This must also be the value of
2125
the number of entries in the matrixDSTable for this
2126
interface."
2127
::= { matrixControlEntry 3 }
2128
2129
matrixControlLastDeleteTime OBJECT-TYPE
2130
SYNTAX TimeTicks
2131
MAX-ACCESS read-only
2132
STATUS current
2133
DESCRIPTION
2134
"The value of sysUpTime when the last entry
2135
was deleted from the portion of the matrixSDTable
2136
or matrixDSTable associated with this matrixControlEntry.
2137
If no deletions have occurred, this value shall be
2138
zero."
2139
::= { matrixControlEntry 4 }
2140
2141
matrixControlOwner OBJECT-TYPE
2142
SYNTAX OwnerString
2143
MAX-ACCESS read-create
2144
STATUS current
2145
DESCRIPTION
2146
"The entity that configured this entry and is therefore
2147
using the resources assigned to it."
2148
::= { matrixControlEntry 5 }
2149
2150
matrixControlStatus OBJECT-TYPE
2151
SYNTAX EntryStatus
2152
MAX-ACCESS read-create
2153
STATUS current
2154
DESCRIPTION
2155
"The status of this matrixControl entry.
2156
2157
If this object is not equal to valid(1), all associated
2158
entries in the matrixSDTable and the matrixDSTable
2159
shall be deleted by the agent."
2160
::= { matrixControlEntry 6 }
2161
2162
matrixSDTable OBJECT-TYPE
2163
SYNTAX SEQUENCE OF MatrixSDEntry
2164
MAX-ACCESS not-accessible
2165
STATUS current
2166
DESCRIPTION
2167
"A list of traffic matrix entries indexed by
2168
source and destination MAC address."
2169
::= { matrix 2 }
2170
2171
matrixSDEntry OBJECT-TYPE
2172
SYNTAX MatrixSDEntry
2173
MAX-ACCESS not-accessible
2174
STATUS current
2175
DESCRIPTION
2176
"A collection of statistics for communications between
2177
two addresses on a particular interface. For example,
2178
an instance of the matrixSDPkts object might be named
2179
matrixSDPkts.1.6.8.0.32.27.3.176.6.8.0.32.10.8.113"
2180
INDEX { matrixSDIndex,
2181
matrixSDSourceAddress, matrixSDDestAddress }
2182
::= { matrixSDTable 1 }
2183
2184
MatrixSDEntry ::= SEQUENCE {
2185
matrixSDSourceAddress OCTET STRING,
2186
matrixSDDestAddress OCTET STRING,
2187
matrixSDIndex Integer32,
2188
matrixSDPkts Counter32,
2189
matrixSDOctets Counter32,
2190
matrixSDErrors Counter32
2191
}
2192
2193
matrixSDSourceAddress OBJECT-TYPE
2194
SYNTAX OCTET STRING
2195
MAX-ACCESS read-only
2196
STATUS current
2197
DESCRIPTION
2198
"The source physical address."
2199
::= { matrixSDEntry 1 }
2200
2201
matrixSDDestAddress OBJECT-TYPE
2202
SYNTAX OCTET STRING
2203
MAX-ACCESS read-only
2204
STATUS current
2205
DESCRIPTION
2206
"The destination physical address."
2207
::= { matrixSDEntry 2 }
2208
2209
matrixSDIndex OBJECT-TYPE
2210
SYNTAX Integer32 (1..65535)
2211
MAX-ACCESS read-only
2212
STATUS current
2213
DESCRIPTION
2214
"The set of collected matrix statistics of which
2215
this entry is a part. The set of matrix statistics
2216
identified by a particular value of this index
2217
is associated with the same matrixControlEntry
2218
as identified by the same value of matrixControlIndex."
2219
::= { matrixSDEntry 3 }
2220
2221
matrixSDPkts OBJECT-TYPE
2222
SYNTAX Counter32
2223
UNITS "Packets"
2224
MAX-ACCESS read-only
2225
STATUS current
2226
DESCRIPTION
2227
"The number of packets transmitted from the source
2228
address to the destination address (this number includes
2229
bad packets)."
2230
::= { matrixSDEntry 4 }
2231
2232
matrixSDOctets OBJECT-TYPE
2233
SYNTAX Counter32
2234
UNITS "Octets"
2235
MAX-ACCESS read-only
2236
STATUS current
2237
DESCRIPTION
2238
"The number of octets (excluding framing bits but
2239
including FCS octets) contained in all packets
2240
transmitted from the source address to the
2241
destination address."
2242
::= { matrixSDEntry 5 }
2243
2244
matrixSDErrors OBJECT-TYPE
2245
SYNTAX Counter32
2246
UNITS "Packets"
2247
MAX-ACCESS read-only
2248
STATUS current
2249
DESCRIPTION
2250
"The number of bad packets transmitted from
2251
the source address to the destination address."
2252
::= { matrixSDEntry 6 }
2253
2254
2255
matrixDSTable OBJECT-TYPE
2256
SYNTAX SEQUENCE OF MatrixDSEntry
2257
MAX-ACCESS not-accessible
2258
STATUS current
2259
DESCRIPTION
2260
"A list of traffic matrix entries indexed by
2261
destination and source MAC address."
2262
::= { matrix 3 }
2263
2264
matrixDSEntry OBJECT-TYPE
2265
SYNTAX MatrixDSEntry
2266
MAX-ACCESS not-accessible
2267
STATUS current
2268
DESCRIPTION
2269
"A collection of statistics for communications between
2270
two addresses on a particular interface. For example,
2271
an instance of the matrixSDPkts object might be named
2272
matrixSDPkts.1.6.8.0.32.10.8.113.6.8.0.32.27.3.176"
2273
INDEX { matrixDSIndex,
2274
matrixDSDestAddress, matrixDSSourceAddress }
2275
::= { matrixDSTable 1 }
2276
2277
MatrixDSEntry ::= SEQUENCE {
2278
matrixDSSourceAddress OCTET STRING,
2279
matrixDSDestAddress OCTET STRING,
2280
matrixDSIndex Integer32,
2281
matrixDSPkts Counter32,
2282
matrixDSOctets Counter32,
2283
matrixDSErrors Counter32
2284
}
2285
2286
matrixDSSourceAddress OBJECT-TYPE
2287
SYNTAX OCTET STRING
2288
MAX-ACCESS read-only
2289
STATUS current
2290
DESCRIPTION
2291
"The source physical address."
2292
::= { matrixDSEntry 1 }
2293
2294
matrixDSDestAddress OBJECT-TYPE
2295
SYNTAX OCTET STRING
2296
MAX-ACCESS read-only
2297
STATUS current
2298
DESCRIPTION
2299
"The destination physical address."
2300
::= { matrixDSEntry 2 }
2301
2302
matrixDSIndex OBJECT-TYPE
2303
SYNTAX Integer32 (1..65535)
2304
MAX-ACCESS read-only
2305
STATUS current
2306
DESCRIPTION
2307
"The set of collected matrix statistics of which
2308
this entry is a part. The set of matrix statistics
2309
identified by a particular value of this index
2310
is associated with the same matrixControlEntry
2311
as identified by the same value of matrixControlIndex."
2312
::= { matrixDSEntry 3 }
2313
2314
matrixDSPkts OBJECT-TYPE
2315
SYNTAX Counter32
2316
UNITS "Packets"
2317
MAX-ACCESS read-only
2318
STATUS current
2319
DESCRIPTION
2320
"The number of packets transmitted from the source
2321
address to the destination address (this number includes
2322
bad packets)."
2323
::= { matrixDSEntry 4 }
2324
2325
matrixDSOctets OBJECT-TYPE
2326
SYNTAX Counter32
2327
UNITS "Octets"
2328
MAX-ACCESS read-only
2329
STATUS current
2330
DESCRIPTION
2331
"The number of octets (excluding framing bits
2332
but including FCS octets) contained in all packets
2333
transmitted from the source address to the
2334
destination address."
2335
::= { matrixDSEntry 5 }
2336
2337
matrixDSErrors OBJECT-TYPE
2338
SYNTAX Counter32
2339
UNITS "Packets"
2340
MAX-ACCESS read-only
2341
STATUS current
2342
DESCRIPTION
2343
"The number of bad packets transmitted from
2344
the source address to the destination address."
2345
::= { matrixDSEntry 6 }
2346
2347
2348
2349
--
2350
--
2351
--
2352
--
2353
2354
filterTable OBJECT-TYPE
2355
SYNTAX SEQUENCE OF FilterEntry
2356
MAX-ACCESS not-accessible
2357
STATUS current
2358
DESCRIPTION
2359
"A list of packet filter entries."
2360
::= { filter 1 }
2361
2362
filterEntry OBJECT-TYPE
2363
SYNTAX FilterEntry
2364
MAX-ACCESS not-accessible
2365
STATUS current
2366
DESCRIPTION
2367
"A set of parameters for a packet filter applied on a
2368
particular interface. As an example, an instance of the
2369
filterPktData object might be named filterPktData.12"
2370
INDEX { filterIndex }
2371
::= { filterTable 1 }
2372
2373
FilterEntry ::= SEQUENCE {
2374
filterIndex Integer32,
2375
filterChannelIndex Integer32,
2376
filterPktDataOffset Integer32,
2377
filterPktData OCTET STRING,
2378
filterPktDataMask OCTET STRING,
2379
filterPktDataNotMask OCTET STRING,
2380
filterPktStatus Integer32,
2381
filterPktStatusMask Integer32,
2382
filterPktStatusNotMask Integer32,
2383
filterOwner OwnerString,
2384
filterStatus EntryStatus
2385
}
2386
2387
filterIndex OBJECT-TYPE
2388
SYNTAX Integer32 (1..65535)
2389
MAX-ACCESS read-only
2390
STATUS current
2391
DESCRIPTION
2392
"An index that uniquely identifies an entry
2393
in the filter table. Each such entry defines
2394
one filter that is to be applied to every packet
2395
received on an interface."
2396
::= { filterEntry 1 }
2397
2398
filterChannelIndex OBJECT-TYPE
2399
SYNTAX Integer32 (1..65535)
2400
MAX-ACCESS read-create
2401
STATUS current
2402
DESCRIPTION
2403
"This object identifies the channel of which this filter
2404
is a part. The filters identified by a particular value
2405
of this object are associated with the same channel as
2406
identified by the same value of the channelIndex object."
2407
::= { filterEntry 2 }
2408
2409
filterPktDataOffset OBJECT-TYPE
2410
SYNTAX Integer32
2411
UNITS "Octets"
2412
MAX-ACCESS read-create
2413
STATUS current
2414
DESCRIPTION
2415
"The offset from the beginning of each packet where
2416
a match of packet data will be attempted. This offset
2417
is measured from the point in the physical layer
2418
packet after the framing bits, if any. For example,
2419
in an Ethernet frame, this point is at the beginning of
2420
the destination MAC address.
2421
2422
This object may not be modified if the associated
2423
filterStatus object is equal to valid(1)."
2424
DEFVAL { 0 }
2425
::= { filterEntry 3 }
2426
2427
filterPktData OBJECT-TYPE
2428
SYNTAX OCTET STRING
2429
MAX-ACCESS read-create
2430
STATUS current
2431
DESCRIPTION
2432
"The data that is to be matched with the input packet.
2433
For each packet received, this filter and the accompanying
2434
filterPktDataMask and filterPktDataNotMask will be
2435
adjusted for the offset. The only bits relevant to this
2436
match algorithm are those that have the corresponding
2437
filterPktDataMask bit equal to one. The following three
2438
rules are then applied to every packet:
2439
2440
(1) If the packet is too short and does not have data
2441
corresponding to part of the filterPktData, the packet
2442
will fail this data match.
2443
2444
(2) For each relevant bit from the packet with the
2445
corresponding filterPktDataNotMask bit set to zero, if
2446
the bit from the packet is not equal to the corresponding
2447
bit from the filterPktData, then the packet will fail
2448
this data match.
2449
2450
(3) If for every relevant bit from the packet with the
2451
corresponding filterPktDataNotMask bit set to one, the
2452
bit from the packet is equal to the corresponding bit
2453
from the filterPktData, then the packet will fail this
2454
data match.
2455
2456
Any packets that have not failed any of the three matches
2457
above have passed this data match. In particular, a zero
2458
length filter will match any packet.
2459
2460
This object may not be modified if the associated
2461
filterStatus object is equal to valid(1)."
2462
::= { filterEntry 4 }
2463
2464
filterPktDataMask OBJECT-TYPE
2465
SYNTAX OCTET STRING
2466
MAX-ACCESS read-create
2467
STATUS current
2468
DESCRIPTION
2469
"The mask that is applied to the match process.
2470
After adjusting this mask for the offset, only those
2471
bits in the received packet that correspond to bits set
2472
in this mask are relevant for further processing by the
2473
2474
match algorithm. The offset is applied to filterPktDataMask
2475
in the same way it is applied to the filter. For the
2476
purposes of the matching algorithm, if the associated
2477
filterPktData object is longer than this mask, this mask is
2478
conceptually extended with '1' bits until it reaches the
2479
length of the filterPktData object.
2480
2481
This object may not be modified if the associated
2482
filterStatus object is equal to valid(1)."
2483
::= { filterEntry 5 }
2484
2485
filterPktDataNotMask OBJECT-TYPE
2486
SYNTAX OCTET STRING
2487
MAX-ACCESS read-create
2488
STATUS current
2489
DESCRIPTION
2490
"The inversion mask that is applied to the match
2491
process. After adjusting this mask for the offset,
2492
those relevant bits in the received packet that correspond
2493
to bits cleared in this mask must all be equal to their
2494
corresponding bits in the filterPktData object for the packet
2495
to be accepted. In addition, at least one of those relevant
2496
bits in the received packet that correspond to bits set in
2497
this mask must be different to its corresponding bit in the
2498
filterPktData object.
2499
2500
For the purposes of the matching algorithm, if the associated
2501
filterPktData object is longer than this mask, this mask is
2502
conceptually extended with '0' bits until it reaches the
2503
length of the filterPktData object.
2504
2505
This object may not be modified if the associated
2506
filterStatus object is equal to valid(1)."
2507
::= { filterEntry 6 }
2508
2509
filterPktStatus OBJECT-TYPE
2510
SYNTAX Integer32
2511
MAX-ACCESS read-create
2512
STATUS current
2513
DESCRIPTION
2514
"The status that is to be matched with the input packet.
2515
The only bits relevant to this match algorithm are those that
2516
have the corresponding filterPktStatusMask bit equal to one.
2517
The following two rules are then applied to every packet:
2518
2519
(1) For each relevant bit from the packet status with the
2520
corresponding filterPktStatusNotMask bit set to zero, if
2521
the bit from the packet status is not equal to the
2522
2523
corresponding bit from the filterPktStatus, then the
2524
packet will fail this status match.
2525
2526
(2) If for every relevant bit from the packet status with the
2527
corresponding filterPktStatusNotMask bit set to one, the
2528
bit from the packet status is equal to the corresponding
2529
bit from the filterPktStatus, then the packet will fail
2530
this status match.
2531
2532
Any packets that have not failed either of the two matches
2533
above have passed this status match. In particular, a zero
2534
length status filter will match any packet's status.
2535
2536
The value of the packet status is a sum. This sum
2537
initially takes the value zero. Then, for each
2538
error, E, that has been discovered in this packet,
2539
2 raised to a value representing E is added to the sum.
2540
The errors and the bits that represent them are dependent
2541
on the media type of the interface that this channel
2542
is receiving packets from.
2543
2544
The errors defined for a packet captured off of an
2545
Ethernet interface are as follows:
2546
2547
bit # Error
2548
0 Packet is longer than 1518 octets
2549
1 Packet is shorter than 64 octets
2550
2 Packet experienced a CRC or Alignment error
2551
2552
For example, an Ethernet fragment would have a
2553
value of 6 (2^1 + 2^2).
2554
2555
As this MIB is expanded to new media types, this object
2556
will have other media-specific errors defined.
2557
2558
For the purposes of this status matching algorithm, if the
2559
packet status is longer than this filterPktStatus object,
2560
this object is conceptually extended with '0' bits until it
2561
reaches the size of the packet status.
2562
2563
This object may not be modified if the associated
2564
filterStatus object is equal to valid(1)."
2565
::= { filterEntry 7 }
2566
2567
filterPktStatusMask OBJECT-TYPE
2568
SYNTAX Integer32
2569
MAX-ACCESS read-create
2570
STATUS current
2571
DESCRIPTION
2572
"The mask that is applied to the status match process.
2573
Only those bits in the received packet that correspond to
2574
bits set in this mask are relevant for further processing
2575
by the status match algorithm. For the purposes
2576
of the matching algorithm, if the associated filterPktStatus
2577
object is longer than this mask, this mask is conceptually
2578
extended with '1' bits until it reaches the size of the
2579
filterPktStatus. In addition, if a packet status is longer
2580
than this mask, this mask is conceptually extended with '0'
2581
bits until it reaches the size of the packet status.
2582
2583
This object may not be modified if the associated
2584
filterStatus object is equal to valid(1)."
2585
::= { filterEntry 8 }
2586
2587
filterPktStatusNotMask OBJECT-TYPE
2588
SYNTAX Integer32
2589
MAX-ACCESS read-create
2590
STATUS current
2591
DESCRIPTION
2592
"The inversion mask that is applied to the status match
2593
process. Those relevant bits in the received packet status
2594
that correspond to bits cleared in this mask must all be
2595
equal to their corresponding bits in the filterPktStatus
2596
object for the packet to be accepted. In addition, at least
2597
one of those relevant bits in the received packet status
2598
that correspond to bits set in this mask must be different
2599
to its corresponding bit in the filterPktStatus object for
2600
the packet to be accepted.
2601
2602
For the purposes of the matching algorithm, if the associated
2603
filterPktStatus object or a packet status is longer than this
2604
mask, this mask is conceptually extended with '0' bits until
2605
it reaches the longer of the lengths of the filterPktStatus
2606
object and the packet status.
2607
2608
This object may not be modified if the associated
2609
filterStatus object is equal to valid(1)."
2610
::= { filterEntry 9 }
2611
2612
filterOwner OBJECT-TYPE
2613
SYNTAX OwnerString
2614
MAX-ACCESS read-create
2615
STATUS current
2616
DESCRIPTION
2617
"The entity that configured this entry and is therefore
2618
using the resources assigned to it."
2619
::= { filterEntry 10 }
2620
2621
filterStatus OBJECT-TYPE
2622
SYNTAX EntryStatus
2623
MAX-ACCESS read-create
2624
STATUS current
2625
DESCRIPTION
2626
"The status of this filter entry."
2627
::= { filterEntry 11 }
2628
2629
channelTable OBJECT-TYPE
2630
SYNTAX SEQUENCE OF ChannelEntry
2631
MAX-ACCESS not-accessible
2632
STATUS current
2633
DESCRIPTION
2634
"A list of packet channel entries."
2635
::= { filter 2 }
2636
2637
channelEntry OBJECT-TYPE
2638
SYNTAX ChannelEntry
2639
MAX-ACCESS not-accessible
2640
STATUS current
2641
DESCRIPTION
2642
"A set of parameters for a packet channel applied on a
2643
particular interface. As an example, an instance of the
2644
channelMatches object might be named channelMatches.3"
2645
INDEX { channelIndex }
2646
::= { channelTable 1 }
2647
2648
ChannelEntry ::= SEQUENCE {
2649
channelIndex Integer32,
2650
channelIfIndex Integer32,
2651
channelAcceptType INTEGER,
2652
channelDataControl INTEGER,
2653
channelTurnOnEventIndex Integer32,
2654
channelTurnOffEventIndex Integer32,
2655
channelEventIndex Integer32,
2656
channelEventStatus INTEGER,
2657
channelMatches Counter32,
2658
channelDescription DisplayString,
2659
channelOwner OwnerString,
2660
channelStatus EntryStatus
2661
}
2662
2663
channelIndex OBJECT-TYPE
2664
SYNTAX Integer32 (1..65535)
2665
MAX-ACCESS read-only
2666
STATUS current
2667
DESCRIPTION
2668
"An index that uniquely identifies an entry in the channel
2669
table. Each such entry defines one channel, a logical
2670
data and event stream.
2671
2672
It is suggested that before creating a channel, an
2673
application should scan all instances of the
2674
filterChannelIndex object to make sure that there are no
2675
pre-existing filters that would be inadvertently be linked
2676
to the channel."
2677
::= { channelEntry 1 }
2678
2679
channelIfIndex OBJECT-TYPE
2680
SYNTAX Integer32 (1..65535)
2681
MAX-ACCESS read-create
2682
STATUS current
2683
DESCRIPTION
2684
"The value of this object uniquely identifies the
2685
interface on this remote network monitoring device to which
2686
the associated filters are applied to allow data into this
2687
channel. The interface identified by a particular value
2688
of this object is the same interface as identified by the
2689
same value of the ifIndex object, defined in RFC 2233 [17].
2690
2691
The filters in this group are applied to all packets on
2692
the local network segment attached to the identified
2693
interface.
2694
2695
An agent may or may not be able to tell if fundamental
2696
changes to the media of the interface have occurred and
2697
necessitate an invalidation of this entry. For example, a
2698
hot-pluggable ethernet card could be pulled out and replaced
2699
by a token-ring card. In such a case, if the agent has such
2700
knowledge of the change, it is recommended that it
2701
invalidate this entry.
2702
2703
This object may not be modified if the associated
2704
channelStatus object is equal to valid(1)."
2705
::= { channelEntry 2 }
2706
2707
channelAcceptType OBJECT-TYPE
2708
SYNTAX INTEGER {
2709
acceptMatched(1),
2710
acceptFailed(2)
2711
}
2712
MAX-ACCESS read-create
2713
STATUS current
2714
DESCRIPTION
2715
"This object controls the action of the filters
2716
associated with this channel. If this object is equal
2717
to acceptMatched(1), packets will be accepted to this
2718
channel if they are accepted by both the packet data and
2719
packet status matches of an associated filter. If
2720
this object is equal to acceptFailed(2), packets will
2721
be accepted to this channel only if they fail either
2722
the packet data match or the packet status match of
2723
each of the associated filters.
2724
2725
In particular, a channel with no associated filters will
2726
match no packets if set to acceptMatched(1) case and will
2727
match all packets in the acceptFailed(2) case.
2728
2729
This object may not be modified if the associated
2730
channelStatus object is equal to valid(1)."
2731
::= { channelEntry 3 }
2732
2733
channelDataControl OBJECT-TYPE
2734
SYNTAX INTEGER {
2735
on(1),
2736
off(2)
2737
}
2738
MAX-ACCESS read-create
2739
STATUS current
2740
DESCRIPTION
2741
"This object controls the flow of data through this channel.
2742
If this object is on(1), data, status and events flow
2743
through this channel. If this object is off(2), data,
2744
status and events will not flow through this channel."
2745
DEFVAL { off }
2746
::= { channelEntry 4 }
2747
2748
channelTurnOnEventIndex OBJECT-TYPE
2749
SYNTAX Integer32 (0..65535)
2750
MAX-ACCESS read-create
2751
STATUS current
2752
DESCRIPTION
2753
"The value of this object identifies the event
2754
that is configured to turn the associated
2755
channelDataControl from off to on when the event is
2756
generated. The event identified by a particular value
2757
of this object is the same event as identified by the
2758
same value of the eventIndex object. If there is no
2759
corresponding entry in the eventTable, then no
2760
association exists. In fact, if no event is intended
2761
for this channel, channelTurnOnEventIndex must be
2762
set to zero, a non-existent event index.
2763
2764
This object may not be modified if the associated
2765
channelStatus object is equal to valid(1)."
2766
::= { channelEntry 5 }
2767
2768
channelTurnOffEventIndex OBJECT-TYPE
2769
SYNTAX Integer32 (0..65535)
2770
MAX-ACCESS read-create
2771
STATUS current
2772
DESCRIPTION
2773
"The value of this object identifies the event
2774
that is configured to turn the associated
2775
channelDataControl from on to off when the event is
2776
generated. The event identified by a particular value
2777
of this object is the same event as identified by the
2778
same value of the eventIndex object. If there is no
2779
corresponding entry in the eventTable, then no
2780
association exists. In fact, if no event is intended
2781
for this channel, channelTurnOffEventIndex must be
2782
set to zero, a non-existent event index.
2783
2784
This object may not be modified if the associated
2785
channelStatus object is equal to valid(1)."
2786
::= { channelEntry 6 }
2787
2788
channelEventIndex OBJECT-TYPE
2789
SYNTAX Integer32 (0..65535)
2790
MAX-ACCESS read-create
2791
STATUS current
2792
DESCRIPTION
2793
"The value of this object identifies the event
2794
that is configured to be generated when the
2795
associated channelDataControl is on and a packet
2796
is matched. The event identified by a particular value
2797
of this object is the same event as identified by the
2798
same value of the eventIndex object. If there is no
2799
corresponding entry in the eventTable, then no
2800
association exists. In fact, if no event is intended
2801
for this channel, channelEventIndex must be
2802
set to zero, a non-existent event index.
2803
2804
This object may not be modified if the associated
2805
channelStatus object is equal to valid(1)."
2806
::= { channelEntry 7 }
2807
2808
channelEventStatus OBJECT-TYPE
2809
SYNTAX INTEGER {
2810
eventReady(1),
2811
eventFired(2),
2812
eventAlwaysReady(3)
2813
}
2814
MAX-ACCESS read-create
2815
STATUS current
2816
DESCRIPTION
2817
"The event status of this channel.
2818
2819
If this channel is configured to generate events
2820
when packets are matched, a means of controlling
2821
the flow of those events is often needed. When
2822
this object is equal to eventReady(1), a single
2823
event may be generated, after which this object
2824
will be set by the probe to eventFired(2). While
2825
in the eventFired(2) state, no events will be
2826
generated until the object is modified to
2827
eventReady(1) (or eventAlwaysReady(3)). The
2828
management station can thus easily respond to a
2829
notification of an event by re-enabling this object.
2830
2831
If the management station wishes to disable this
2832
flow control and allow events to be generated
2833
at will, this object may be set to
2834
eventAlwaysReady(3). Disabling the flow control
2835
is discouraged as it can result in high network
2836
traffic or other performance problems."
2837
DEFVAL { eventReady }
2838
::= { channelEntry 8 }
2839
2840
channelMatches OBJECT-TYPE
2841
SYNTAX Counter32
2842
UNITS "Packets"
2843
MAX-ACCESS read-only
2844
STATUS current
2845
DESCRIPTION
2846
"The number of times this channel has matched a packet.
2847
Note that this object is updated even when
2848
channelDataControl is set to off."
2849
::= { channelEntry 9 }
2850
2851
channelDescription OBJECT-TYPE
2852
SYNTAX DisplayString (SIZE (0..127))
2853
MAX-ACCESS read-create
2854
STATUS current
2855
DESCRIPTION
2856
"A comment describing this channel."
2857
::= { channelEntry 10 }
2858
2859
channelOwner OBJECT-TYPE
2860
SYNTAX OwnerString
2861
MAX-ACCESS read-create
2862
STATUS current
2863
DESCRIPTION
2864
"The entity that configured this entry and is therefore
2865
using the resources assigned to it."
2866
::= { channelEntry 11 }
2867
2868
channelStatus OBJECT-TYPE
2869
SYNTAX EntryStatus
2870
MAX-ACCESS read-create
2871
STATUS current
2872
DESCRIPTION
2873
"The status of this channel entry."
2874
::= { channelEntry 12 }
2875
2876
2877
--
2878
2879
bufferControlTable OBJECT-TYPE
2880
SYNTAX SEQUENCE OF BufferControlEntry
2881
MAX-ACCESS not-accessible
2882
STATUS current
2883
DESCRIPTION
2884
"A list of buffers control entries."
2885
::= { capture 1 }
2886
2887
bufferControlEntry OBJECT-TYPE
2888
SYNTAX BufferControlEntry
2889
MAX-ACCESS not-accessible
2890
STATUS current
2891
DESCRIPTION
2892
"A set of parameters that control the collection of a stream
2893
of packets that have matched filters. As an example, an
2894
instance of the bufferControlCaptureSliceSize object might
2895
be named bufferControlCaptureSliceSize.3"
2896
INDEX { bufferControlIndex }
2897
::= { bufferControlTable 1 }
2898
2899
BufferControlEntry ::= SEQUENCE {
2900
bufferControlIndex Integer32,
2901
bufferControlChannelIndex Integer32,
2902
bufferControlFullStatus INTEGER,
2903
bufferControlFullAction INTEGER,
2904
bufferControlCaptureSliceSize Integer32,
2905
bufferControlDownloadSliceSize Integer32,
2906
bufferControlDownloadOffset Integer32,
2907
bufferControlMaxOctetsRequested Integer32,
2908
bufferControlMaxOctetsGranted Integer32,
2909
bufferControlCapturedPackets Integer32,
2910
bufferControlTurnOnTime TimeTicks,
2911
bufferControlOwner OwnerString,
2912
bufferControlStatus EntryStatus
2913
}
2914
2915
bufferControlIndex OBJECT-TYPE
2916
SYNTAX Integer32 (1..65535)
2917
MAX-ACCESS read-only
2918
STATUS current
2919
DESCRIPTION
2920
"An index that uniquely identifies an entry
2921
in the bufferControl table. The value of this
2922
index shall never be zero. Each such
2923
entry defines one set of packets that is
2924
captured and controlled by one or more filters."
2925
::= { bufferControlEntry 1 }
2926
2927
bufferControlChannelIndex OBJECT-TYPE
2928
SYNTAX Integer32 (1..65535)
2929
MAX-ACCESS read-create
2930
STATUS current
2931
DESCRIPTION
2932
"An index that identifies the channel that is the
2933
source of packets for this bufferControl table.
2934
The channel identified by a particular value of this
2935
index is the same as identified by the same value of
2936
the channelIndex object.
2937
2938
This object may not be modified if the associated
2939
bufferControlStatus object is equal to valid(1)."
2940
::= { bufferControlEntry 2 }
2941
2942
bufferControlFullStatus OBJECT-TYPE
2943
SYNTAX INTEGER {
2944
2945
spaceAvailable(1),
2946
full(2)
2947
}
2948
MAX-ACCESS read-only
2949
STATUS current
2950
DESCRIPTION
2951
"This object shows whether the buffer has room to
2952
accept new packets or if it is full.
2953
2954
If the status is spaceAvailable(1), the buffer is
2955
accepting new packets normally. If the status is
2956
full(2) and the associated bufferControlFullAction
2957
object is wrapWhenFull, the buffer is accepting new
2958
packets by deleting enough of the oldest packets
2959
to make room for new ones as they arrive. Otherwise,
2960
if the status is full(2) and the
2961
bufferControlFullAction object is lockWhenFull,
2962
then the buffer has stopped collecting packets.
2963
2964
When this object is set to full(2) the probe must
2965
not later set it to spaceAvailable(1) except in the
2966
case of a significant gain in resources such as
2967
an increase of bufferControlOctetsGranted. In
2968
particular, the wrap-mode action of deleting old
2969
packets to make room for newly arrived packets
2970
must not affect the value of this object."
2971
::= { bufferControlEntry 3 }
2972
2973
bufferControlFullAction OBJECT-TYPE
2974
SYNTAX INTEGER {
2975
lockWhenFull(1),
2976
wrapWhenFull(2) -- FIFO
2977
}
2978
MAX-ACCESS read-create
2979
STATUS current
2980
DESCRIPTION
2981
"Controls the action of the buffer when it
2982
reaches the full status. When in the lockWhenFull(1)
2983
state and a packet is added to the buffer that
2984
fills the buffer, the bufferControlFullStatus will
2985
be set to full(2) and this buffer will stop capturing
2986
packets."
2987
::= { bufferControlEntry 4 }
2988
2989
bufferControlCaptureSliceSize OBJECT-TYPE
2990
SYNTAX Integer32
2991
UNITS "Octets"
2992
MAX-ACCESS read-create
2993
STATUS current
2994
DESCRIPTION
2995
"The maximum number of octets of each packet
2996
that will be saved in this capture buffer.
2997
For example, if a 1500 octet packet is received by
2998
the probe and this object is set to 500, then only
2999
500 octets of the packet will be stored in the
3000
associated capture buffer. If this variable is set
3001
to 0, the capture buffer will save as many octets
3002
as is possible.
3003
3004
This object may not be modified if the associated
3005
bufferControlStatus object is equal to valid(1)."
3006
DEFVAL { 100 }
3007
::= { bufferControlEntry 5 }
3008
3009
bufferControlDownloadSliceSize OBJECT-TYPE
3010
SYNTAX Integer32
3011
UNITS "Octets"
3012
MAX-ACCESS read-create
3013
STATUS current
3014
DESCRIPTION
3015
"The maximum number of octets of each packet
3016
in this capture buffer that will be returned in
3017
an SNMP retrieval of that packet. For example,
3018
if 500 octets of a packet have been stored in the
3019
associated capture buffer, the associated
3020
bufferControlDownloadOffset is 0, and this
3021
object is set to 100, then the captureBufferPacket
3022
object that contains the packet will contain only
3023
the first 100 octets of the packet.
3024
3025
A prudent manager will take into account possible
3026
interoperability or fragmentation problems that may
3027
occur if the download slice size is set too large.
3028
In particular, conformant SNMP implementations are not
3029
required to accept messages whose length exceeds 484
3030
octets, although they are encouraged to support larger
3031
datagrams whenever feasible."
3032
DEFVAL { 100 }
3033
::= { bufferControlEntry 6 }
3034
3035
bufferControlDownloadOffset OBJECT-TYPE
3036
SYNTAX Integer32
3037
UNITS "Octets"
3038
MAX-ACCESS read-create
3039
STATUS current
3040
DESCRIPTION
3041
"The offset of the first octet of each packet
3042
in this capture buffer that will be returned in
3043
an SNMP retrieval of that packet. For example,
3044
if 500 octets of a packet have been stored in the
3045
associated capture buffer and this object is set to
3046
100, then the captureBufferPacket object that
3047
contains the packet will contain bytes starting
3048
100 octets into the packet."
3049
DEFVAL { 0 }
3050
::= { bufferControlEntry 7 }
3051
3052
bufferControlMaxOctetsRequested OBJECT-TYPE
3053
SYNTAX Integer32
3054
UNITS "Octets"
3055
MAX-ACCESS read-create
3056
STATUS current
3057
DESCRIPTION
3058
"The requested maximum number of octets to be
3059
saved in this captureBuffer, including any
3060
implementation-specific overhead. If this variable
3061
is set to -1, the capture buffer will save as many
3062
octets as is possible.
3063
3064
When this object is created or modified, the probe
3065
should set bufferControlMaxOctetsGranted as closely
3066
to this object as is possible for the particular probe
3067
implementation and available resources. However, if
3068
the object has the special value of -1, the probe
3069
must set bufferControlMaxOctetsGranted to -1."
3070
DEFVAL { -1 }
3071
::= { bufferControlEntry 8 }
3072
3073
bufferControlMaxOctetsGranted OBJECT-TYPE
3074
SYNTAX Integer32
3075
UNITS "Octets"
3076
MAX-ACCESS read-only
3077
STATUS current
3078
DESCRIPTION
3079
"The maximum number of octets that can be
3080
saved in this captureBuffer, including overhead.
3081
If this variable is -1, the capture buffer will save
3082
as many octets as possible.
3083
3084
When the bufferControlMaxOctetsRequested object is
3085
created or modified, the probe should set this object
3086
as closely to the requested value as is possible for the
3087
particular probe implementation and available resources.
3088
However, if the request object has the special value
3089
3090
of -1, the probe must set this object to -1.
3091
3092
The probe must not lower this value except as a result of
3093
a modification to the associated
3094
bufferControlMaxOctetsRequested object.
3095
3096
When this maximum number of octets is reached
3097
and a new packet is to be added to this
3098
capture buffer and the corresponding
3099
bufferControlFullAction is set to wrapWhenFull(2),
3100
enough of the oldest packets associated with this
3101
capture buffer shall be deleted by the agent so
3102
that the new packet can be added. If the corresponding
3103
bufferControlFullAction is set to lockWhenFull(1),
3104
the new packet shall be discarded. In either case,
3105
the probe must set bufferControlFullStatus to
3106
full(2).
3107
3108
When the value of this object changes to a value less
3109
than the current value, entries are deleted from
3110
the captureBufferTable associated with this
3111
bufferControlEntry. Enough of the
3112
oldest of these captureBufferEntries shall be
3113
deleted by the agent so that the number of octets
3114
used remains less than or equal to the new value of
3115
this object.
3116
3117
When the value of this object changes to a value greater
3118
than the current value, the number of associated
3119
captureBufferEntries may be allowed to grow."
3120
::= { bufferControlEntry 9 }
3121
3122
bufferControlCapturedPackets OBJECT-TYPE
3123
SYNTAX Integer32
3124
UNITS "Packets"
3125
MAX-ACCESS read-only
3126
STATUS current
3127
DESCRIPTION
3128
"The number of packets currently in this captureBuffer."
3129
::= { bufferControlEntry 10 }
3130
3131
bufferControlTurnOnTime OBJECT-TYPE
3132
SYNTAX TimeTicks
3133
MAX-ACCESS read-only
3134
STATUS current
3135
DESCRIPTION
3136
"The value of sysUpTime when this capture buffer was
3137
first turned on."
3138
::= { bufferControlEntry 11 }
3139
3140
bufferControlOwner OBJECT-TYPE
3141
SYNTAX OwnerString
3142
MAX-ACCESS read-create
3143
STATUS current
3144
DESCRIPTION
3145
"The entity that configured this entry and is therefore
3146
using the resources assigned to it."
3147
::= { bufferControlEntry 12 }
3148
3149
bufferControlStatus OBJECT-TYPE
3150
SYNTAX EntryStatus
3151
MAX-ACCESS read-create
3152
STATUS current
3153
DESCRIPTION
3154
"The status of this buffer Control Entry."
3155
::= { bufferControlEntry 13 }
3156
3157
captureBufferTable OBJECT-TYPE
3158
SYNTAX SEQUENCE OF CaptureBufferEntry
3159
MAX-ACCESS not-accessible
3160
STATUS current
3161
DESCRIPTION
3162
"A list of packets captured off of a channel."
3163
::= { capture 2 }
3164
3165
captureBufferEntry OBJECT-TYPE
3166
SYNTAX CaptureBufferEntry
3167
MAX-ACCESS not-accessible
3168
STATUS current
3169
DESCRIPTION
3170
"A packet captured off of an attached network. As an
3171
example, an instance of the captureBufferPacketData
3172
object might be named captureBufferPacketData.3.1783"
3173
INDEX { captureBufferControlIndex, captureBufferIndex }
3174
::= { captureBufferTable 1 }
3175
3176
CaptureBufferEntry ::= SEQUENCE {
3177
captureBufferControlIndex Integer32,
3178
captureBufferIndex Integer32,
3179
captureBufferPacketID Integer32,
3180
captureBufferPacketData OCTET STRING,
3181
captureBufferPacketLength Integer32,
3182
captureBufferPacketTime Integer32,
3183
captureBufferPacketStatus Integer32
3184
}
3185
3186
captureBufferControlIndex OBJECT-TYPE
3187
SYNTAX Integer32 (1..65535)
3188
MAX-ACCESS read-only
3189
STATUS current
3190
DESCRIPTION
3191
"The index of the bufferControlEntry with which
3192
this packet is associated."
3193
::= { captureBufferEntry 1 }
3194
3195
captureBufferIndex OBJECT-TYPE
3196
SYNTAX Integer32 (1..2147483647)
3197
MAX-ACCESS read-only
3198
STATUS current
3199
DESCRIPTION
3200
"An index that uniquely identifies an entry
3201
in the captureBuffer table associated with a
3202
particular bufferControlEntry. This index will
3203
start at 1 and increase by one for each new packet
3204
added with the same captureBufferControlIndex.
3205
3206
Should this value reach 2147483647, the next packet
3207
added with the same captureBufferControlIndex shall
3208
cause this value to wrap around to 1."
3209
::= { captureBufferEntry 2 }
3210
3211
captureBufferPacketID OBJECT-TYPE
3212
SYNTAX Integer32
3213
MAX-ACCESS read-only
3214
STATUS current
3215
DESCRIPTION
3216
"An index that describes the order of packets
3217
that are received on a particular interface.
3218
The packetID of a packet captured on an
3219
interface is defined to be greater than the
3220
packetID's of all packets captured previously on
3221
the same interface. As the captureBufferPacketID
3222
object has a maximum positive value of 2^31 - 1,
3223
any captureBufferPacketID object shall have the
3224
value of the associated packet's packetID mod 2^31."
3225
::= { captureBufferEntry 3 }
3226
3227
captureBufferPacketData OBJECT-TYPE
3228
SYNTAX OCTET STRING
3229
MAX-ACCESS read-only
3230
STATUS current
3231
DESCRIPTION
3232
"The data inside the packet, starting at the beginning
3233
of the packet plus any offset specified in the
3234
3235
associated bufferControlDownloadOffset, including any
3236
link level headers. The length of the data in this object
3237
is the minimum of the length of the captured packet minus
3238
the offset, the length of the associated
3239
bufferControlCaptureSliceSize minus the offset, and the
3240
associated bufferControlDownloadSliceSize. If this minimum
3241
is less than zero, this object shall have a length of zero."
3242
::= { captureBufferEntry 4 }
3243
3244
captureBufferPacketLength OBJECT-TYPE
3245
SYNTAX Integer32
3246
UNITS "Octets"
3247
MAX-ACCESS read-only
3248
STATUS current
3249
DESCRIPTION
3250
"The actual length (off the wire) of the packet stored
3251
in this entry, including FCS octets."
3252
::= { captureBufferEntry 5 }
3253
3254
captureBufferPacketTime OBJECT-TYPE
3255
SYNTAX Integer32
3256
UNITS "Milliseconds"
3257
MAX-ACCESS read-only
3258
STATUS current
3259
DESCRIPTION
3260
"The number of milliseconds that had passed since
3261
this capture buffer was first turned on when this
3262
packet was captured."
3263
::= { captureBufferEntry 6 }
3264
3265
captureBufferPacketStatus OBJECT-TYPE
3266
SYNTAX Integer32
3267
MAX-ACCESS read-only
3268
STATUS current
3269
DESCRIPTION
3270
"A value which indicates the error status of this packet.
3271
3272
The value of this object is defined in the same way as
3273
filterPktStatus. The value is a sum. This sum
3274
initially takes the value zero. Then, for each
3275
error, E, that has been discovered in this packet,
3276
2 raised to a value representing E is added to the sum.
3277
3278
The errors defined for a packet captured off of an
3279
Ethernet interface are as follows:
3280
3281
bit # Error
3282
0 Packet is longer than 1518 octets
3283
3284
1 Packet is shorter than 64 octets
3285
2 Packet experienced a CRC or Alignment error
3286
3 First packet in this capture buffer after
3287
it was detected that some packets were
3288
not processed correctly.
3289
4 Packet's order in buffer is only approximate
3290
(May only be set for packets sent from
3291
the probe)
3292
3293
For example, an Ethernet fragment would have a
3294
value of 6 (2^1 + 2^2).
3295
3296
As this MIB is expanded to new media types, this object
3297
will have other media-specific errors defined."
3298
::= { captureBufferEntry 7 }
3299
3300
3301
--
3302
--
3303
3304
eventTable OBJECT-TYPE
3305
SYNTAX SEQUENCE OF EventEntry
3306
MAX-ACCESS not-accessible
3307
STATUS current
3308
DESCRIPTION
3309
"A list of events to be generated."
3310
::= { event 1 }
3311
3312
eventEntry OBJECT-TYPE
3313
SYNTAX EventEntry
3314
MAX-ACCESS not-accessible
3315
STATUS current
3316
DESCRIPTION
3317
"A set of parameters that describe an event to be generated
3318
when certain conditions are met. As an example, an instance
3319
of the eventLastTimeSent object might be named
3320
eventLastTimeSent.6"
3321
INDEX { eventIndex }
3322
::= { eventTable 1 }
3323
3324
EventEntry ::= SEQUENCE {
3325
eventIndex Integer32,
3326
eventDescription DisplayString,
3327
eventType INTEGER,
3328
eventCommunity OCTET STRING,
3329
eventLastTimeSent TimeTicks,
3330
eventOwner OwnerString,
3331
eventStatus EntryStatus
3332
}
3333
3334
eventIndex OBJECT-TYPE
3335
SYNTAX Integer32 (1..65535)
3336
MAX-ACCESS read-only
3337
STATUS current
3338
DESCRIPTION
3339
"An index that uniquely identifies an entry in the
3340
event table. Each such entry defines one event that
3341
is to be generated when the appropriate conditions
3342
occur."
3343
::= { eventEntry 1 }
3344
3345
eventDescription OBJECT-TYPE
3346
SYNTAX DisplayString (SIZE (0..127))
3347
MAX-ACCESS read-create
3348
STATUS current
3349
DESCRIPTION
3350
"A comment describing this event entry."
3351
::= { eventEntry 2 }
3352
3353
eventType OBJECT-TYPE
3354
SYNTAX INTEGER {
3355
none(1),
3356
log(2),
3357
snmptrap(3), -- send an SNMP trap
3358
logandtrap(4)
3359
}
3360
MAX-ACCESS read-create
3361
STATUS current
3362
DESCRIPTION
3363
"The type of notification that the probe will make
3364
about this event. In the case of log, an entry is
3365
made in the log table for each event. In the case of
3366
snmp-trap, an SNMP trap is sent to one or more
3367
management stations."
3368
::= { eventEntry 3 }
3369
3370
eventCommunity OBJECT-TYPE
3371
SYNTAX OCTET STRING (SIZE (0..127))
3372
MAX-ACCESS read-create
3373
STATUS current
3374
DESCRIPTION
3375
"If an SNMP trap is to be sent, it will be sent to
3376
the SNMP community specified by this octet string."
3377
::= { eventEntry 4 }
3378
3379
eventLastTimeSent OBJECT-TYPE
3380
SYNTAX TimeTicks
3381
MAX-ACCESS read-only
3382
STATUS current
3383
DESCRIPTION
3384
"The value of sysUpTime at the time this event
3385
entry last generated an event. If this entry has
3386
not generated any events, this value will be
3387
zero."
3388
::= { eventEntry 5 }
3389
3390
eventOwner OBJECT-TYPE
3391
SYNTAX OwnerString
3392
MAX-ACCESS read-create
3393
STATUS current
3394
DESCRIPTION
3395
"The entity that configured this entry and is therefore
3396
using the resources assigned to it.
3397
3398
If this object contains a string starting with 'monitor'
3399
and has associated entries in the log table, all connected
3400
management stations should retrieve those log entries,
3401
as they may have significance to all management stations
3402
connected to this device"
3403
::= { eventEntry 6 }
3404
3405
eventStatus OBJECT-TYPE
3406
SYNTAX EntryStatus
3407
MAX-ACCESS read-create
3408
STATUS current
3409
DESCRIPTION
3410
"The status of this event entry.
3411
3412
If this object is not equal to valid(1), all associated
3413
log entries shall be deleted by the agent."
3414
::= { eventEntry 7 }
3415
3416
--
3417
logTable OBJECT-TYPE
3418
SYNTAX SEQUENCE OF LogEntry
3419
MAX-ACCESS not-accessible
3420
STATUS current
3421
DESCRIPTION
3422
"A list of events that have been logged."
3423
::= { event 2 }
3424
3425
logEntry OBJECT-TYPE
3426
SYNTAX LogEntry
3427
MAX-ACCESS not-accessible
3428
STATUS current
3429
DESCRIPTION
3430
"A set of data describing an event that has been
3431
logged. For example, an instance of the logDescription
3432
object might be named logDescription.6.47"
3433
INDEX { logEventIndex, logIndex }
3434
::= { logTable 1 }
3435
3436
LogEntry ::= SEQUENCE {
3437
logEventIndex Integer32,
3438
logIndex Integer32,
3439
logTime TimeTicks,
3440
logDescription DisplayString
3441
}
3442
3443
logEventIndex OBJECT-TYPE
3444
SYNTAX Integer32 (1..65535)
3445
MAX-ACCESS read-only
3446
STATUS current
3447
DESCRIPTION
3448
"The event entry that generated this log
3449
entry. The log identified by a particular
3450
value of this index is associated with the same
3451
eventEntry as identified by the same value
3452
of eventIndex."
3453
::= { logEntry 1 }
3454
3455
logIndex OBJECT-TYPE
3456
SYNTAX Integer32 (1..2147483647)
3457
MAX-ACCESS read-only
3458
STATUS current
3459
DESCRIPTION
3460
"An index that uniquely identifies an entry
3461
in the log table amongst those generated by the
3462
same eventEntries. These indexes are
3463
assigned beginning with 1 and increase by one
3464
with each new log entry. The association
3465
between values of logIndex and logEntries
3466
is fixed for the lifetime of each logEntry.
3467
The agent may choose to delete the oldest
3468
instances of logEntry as required because of
3469
lack of memory. It is an implementation-specific
3470
matter as to when this deletion may occur."
3471
::= { logEntry 2 }
3472
3473
logTime OBJECT-TYPE
3474
SYNTAX TimeTicks
3475
MAX-ACCESS read-only
3476
STATUS current
3477
DESCRIPTION
3478
"The value of sysUpTime when this log entry was created."
3479
::= { logEntry 3 }
3480
3481
logDescription OBJECT-TYPE
3482
SYNTAX DisplayString (SIZE (0..255))
3483
MAX-ACCESS read-only
3484
STATUS current
3485
DESCRIPTION
3486
"An implementation dependent description of the
3487
event that activated this log entry."
3488
::= { logEntry 4 }
3489
3490
3491
rmonEventsV2 OBJECT-IDENTITY
3492
STATUS current
3493
DESCRIPTION "Definition point for RMON notifications."
3494
::= { rmon 0 }
3495
3496
risingAlarm NOTIFICATION-TYPE
3497
OBJECTS { alarmIndex, alarmVariable, alarmSampleType,
3498
alarmValue, alarmRisingThreshold }
3499
STATUS current
3500
DESCRIPTION
3501
"The SNMP trap that is generated when an alarm
3502
entry crosses its rising threshold and generates
3503
an event that is configured for sending SNMP
3504
traps."
3505
::= { rmonEventsV2 1 }
3506
3507
fallingAlarm NOTIFICATION-TYPE
3508
OBJECTS { alarmIndex, alarmVariable, alarmSampleType,
3509
alarmValue, alarmFallingThreshold }
3510
STATUS current
3511
DESCRIPTION
3512
"The SNMP trap that is generated when an alarm
3513
entry crosses its falling threshold and generates
3514
an event that is configured for sending SNMP
3515
traps."
3516
::= { rmonEventsV2 2 }
3517
3518
3519
rmonCompliances OBJECT IDENTIFIER ::= { rmonConformance 9 }
3520
rmonGroups OBJECT IDENTIFIER ::= { rmonConformance 10 }
3521
3522
rmonCompliance MODULE-COMPLIANCE
3523
STATUS current
3524
DESCRIPTION
3525
"The requirements for conformance to the RMON MIB. At least
3526
one of the groups in this module must be implemented to
3527
conform to the RMON MIB. Implementations of this MIB
3528
must also implement the system group of MIB-II [16] and the
3529
IF-MIB [17]."
3530
MODULE -- this module
3531
3532
GROUP rmonEtherStatsGroup
3533
DESCRIPTION
3534
"The RMON Ethernet Statistics Group is optional."
3535
3536
GROUP rmonHistoryControlGroup
3537
DESCRIPTION
3538
"The RMON History Control Group is optional."
3539
3540
GROUP rmonEthernetHistoryGroup
3541
DESCRIPTION
3542
"The RMON Ethernet History Group is optional."
3543
3544
GROUP rmonAlarmGroup
3545
DESCRIPTION
3546
"The RMON Alarm Group is optional."
3547
3548
GROUP rmonHostGroup
3549
DESCRIPTION
3550
"The RMON Host Group is mandatory when the
3551
rmonHostTopNGroup is implemented."
3552
3553
GROUP rmonHostTopNGroup
3554
DESCRIPTION
3555
"The RMON Host Top N Group is optional."
3556
3557
GROUP rmonMatrixGroup
3558
DESCRIPTION
3559
"The RMON Matrix Group is optional."
3560
3561
GROUP rmonFilterGroup
3562
DESCRIPTION
3563
"The RMON Filter Group is mandatory when the
3564
rmonPacketCaptureGroup is implemented."
3565
3566
GROUP rmonPacketCaptureGroup
3567
DESCRIPTION
3568
"The RMON Packet Capture Group is optional."
3569
3570
GROUP rmonEventGroup
3571
DESCRIPTION
3572
"The RMON Event Group is mandatory when the
3573
rmonAlarmGroup is implemented."
3574
::= { rmonCompliances 1 }
3575
3576
rmonEtherStatsGroup OBJECT-GROUP
3577
OBJECTS {
3578
etherStatsIndex, etherStatsDataSource,
3579
etherStatsDropEvents, etherStatsOctets, etherStatsPkts,
3580
etherStatsBroadcastPkts, etherStatsMulticastPkts,
3581
etherStatsCRCAlignErrors, etherStatsUndersizePkts,
3582
etherStatsOversizePkts, etherStatsFragments,
3583
etherStatsJabbers, etherStatsCollisions,
3584
etherStatsPkts64Octets, etherStatsPkts65to127Octets,
3585
etherStatsPkts128to255Octets,
3586
etherStatsPkts256to511Octets,
3587
etherStatsPkts512to1023Octets,
3588
etherStatsPkts1024to1518Octets,
3589
etherStatsOwner, etherStatsStatus
3590
}
3591
STATUS current
3592
DESCRIPTION
3593
"The RMON Ethernet Statistics Group."
3594
::= { rmonGroups 1 }
3595
3596
rmonHistoryControlGroup OBJECT-GROUP
3597
OBJECTS {
3598
historyControlIndex, historyControlDataSource,
3599
historyControlBucketsRequested,
3600
historyControlBucketsGranted, historyControlInterval,
3601
historyControlOwner, historyControlStatus
3602
}
3603
STATUS current
3604
DESCRIPTION
3605
"The RMON History Control Group."
3606
::= { rmonGroups 2 }
3607
3608
rmonEthernetHistoryGroup OBJECT-GROUP
3609
OBJECTS {
3610
etherHistoryIndex, etherHistorySampleIndex,
3611
etherHistoryIntervalStart, etherHistoryDropEvents,
3612
etherHistoryOctets, etherHistoryPkts,
3613
etherHistoryBroadcastPkts, etherHistoryMulticastPkts,
3614
etherHistoryCRCAlignErrors, etherHistoryUndersizePkts,
3615
etherHistoryOversizePkts, etherHistoryFragments,
3616
etherHistoryJabbers, etherHistoryCollisions,
3617
etherHistoryUtilization
3618
}
3619
STATUS current
3620
DESCRIPTION
3621
"The RMON Ethernet History Group."
3622
::= { rmonGroups 3 }
3623
3624
rmonAlarmGroup OBJECT-GROUP
3625
OBJECTS {
3626
alarmIndex, alarmInterval, alarmVariable,
3627
alarmSampleType, alarmValue, alarmStartupAlarm,
3628
alarmRisingThreshold, alarmFallingThreshold,
3629
alarmRisingEventIndex, alarmFallingEventIndex,
3630
alarmOwner, alarmStatus
3631
}
3632
STATUS current
3633
DESCRIPTION
3634
"The RMON Alarm Group."
3635
::= { rmonGroups 4 }
3636
3637
rmonHostGroup OBJECT-GROUP
3638
OBJECTS {
3639
hostControlIndex, hostControlDataSource,
3640
hostControlTableSize, hostControlLastDeleteTime,
3641
hostControlOwner, hostControlStatus,
3642
hostAddress, hostCreationOrder, hostIndex,
3643
hostInPkts, hostOutPkts, hostInOctets,
3644
hostOutOctets, hostOutErrors, hostOutBroadcastPkts,
3645
hostOutMulticastPkts, hostTimeAddress,
3646
hostTimeCreationOrder, hostTimeIndex,
3647
hostTimeInPkts, hostTimeOutPkts, hostTimeInOctets,
3648
hostTimeOutOctets, hostTimeOutErrors,
3649
hostTimeOutBroadcastPkts, hostTimeOutMulticastPkts
3650
}
3651
STATUS current
3652
DESCRIPTION
3653
"The RMON Host Group."
3654
::= { rmonGroups 5 }
3655
3656
rmonHostTopNGroup OBJECT-GROUP
3657
OBJECTS {
3658
hostTopNControlIndex, hostTopNHostIndex,
3659
hostTopNRateBase, hostTopNTimeRemaining,
3660
hostTopNDuration, hostTopNRequestedSize,
3661
hostTopNGrantedSize, hostTopNStartTime,
3662
hostTopNOwner, hostTopNStatus,
3663
hostTopNReport, hostTopNIndex,
3664
hostTopNAddress, hostTopNRate
3665
}
3666
STATUS current
3667
DESCRIPTION
3668
"The RMON Host Top 'N' Group."
3669
::= { rmonGroups 6 }
3670
3671
rmonMatrixGroup OBJECT-GROUP
3672
OBJECTS {
3673
matrixControlIndex, matrixControlDataSource,
3674
matrixControlTableSize, matrixControlLastDeleteTime,
3675
matrixControlOwner, matrixControlStatus,
3676
matrixSDSourceAddress, matrixSDDestAddress,
3677
matrixSDIndex, matrixSDPkts,
3678
matrixSDOctets, matrixSDErrors,
3679
matrixDSSourceAddress, matrixDSDestAddress,
3680
matrixDSIndex, matrixDSPkts,
3681
matrixDSOctets, matrixDSErrors
3682
}
3683
STATUS current
3684
DESCRIPTION
3685
"The RMON Matrix Group."
3686
::= { rmonGroups 7 }
3687
3688
rmonFilterGroup OBJECT-GROUP
3689
OBJECTS {
3690
3691
filterIndex, filterChannelIndex, filterPktDataOffset,
3692
filterPktData, filterPktDataMask,
3693
filterPktDataNotMask, filterPktStatus,
3694
filterPktStatusMask, filterPktStatusNotMask,
3695
filterOwner, filterStatus,
3696
channelIndex, channelIfIndex, channelAcceptType,
3697
channelDataControl, channelTurnOnEventIndex,
3698
channelTurnOffEventIndex, channelEventIndex,
3699
channelEventStatus, channelMatches,
3700
channelDescription, channelOwner, channelStatus
3701
}
3702
STATUS current
3703
DESCRIPTION
3704
"The RMON Filter Group."
3705
::= { rmonGroups 8 }
3706
3707
rmonPacketCaptureGroup OBJECT-GROUP
3708
OBJECTS {
3709
bufferControlIndex, bufferControlChannelIndex,
3710
bufferControlFullStatus, bufferControlFullAction,
3711
bufferControlCaptureSliceSize,
3712
bufferControlDownloadSliceSize,
3713
bufferControlDownloadOffset,
3714
bufferControlMaxOctetsRequested,
3715
bufferControlMaxOctetsGranted,
3716
bufferControlCapturedPackets,
3717
bufferControlTurnOnTime,
3718
bufferControlOwner, bufferControlStatus,
3719
captureBufferControlIndex, captureBufferIndex,
3720
captureBufferPacketID, captureBufferPacketData,
3721
captureBufferPacketLength, captureBufferPacketTime,
3722
captureBufferPacketStatus
3723
}
3724
STATUS current
3725
DESCRIPTION
3726
"The RMON Packet Capture Group."
3727
::= { rmonGroups 9 }
3728
3729
rmonEventGroup OBJECT-GROUP
3730
OBJECTS {
3731
eventIndex, eventDescription, eventType,
3732
eventCommunity, eventLastTimeSent,
3733
eventOwner, eventStatus,
3734
logEventIndex, logIndex, logTime,
3735
logDescription
3736
}
3737
STATUS current
3738
DESCRIPTION
3739
"The RMON Event Group."
3740
::= { rmonGroups 10 }
3741
3742
rmonNotificationGroup NOTIFICATION-GROUP
3743
NOTIFICATIONS { risingAlarm, fallingAlarm }
3744
STATUS current
3745
DESCRIPTION
3746
"The RMON Notification Group."
3747
::= { rmonGroups 11 }
3748
END
Loggerhead is a web-based interface for Breezy
Version: 2.0.1