Description:
|
rmonMibModule MODULE-IDENTITY
LAST-UPDATED "200005110000Z" -- 11 May, 2000
ORGANIZATION "IETF RMON MIB Working Group"
CONTACT-INFO
"Steve Waldbusser
Phone: +1-650-948-6500
Fax: +1-650-745-0671
Email: waldbusser@nextbeacon.com"
DESCRIPTION
"Remote network monitoring devices, often called
monitors or probes, are instruments that exist for
the purpose of managing a network. This MIB defines
objects for managing remote network monitoring devices."
REVISION "200005110000Z" -- 11 May, 2000
DESCRIPTION
"Reformatted into SMIv2 format.
This version published as RFC 2819."
REVISION "199502010000Z" -- 1 Feb, 1995
DESCRIPTION
"Bug fixes, clarifications and minor changes based on
implementation experience, published as RFC1757 [18].
Two changes were made to object definitions:
1) A new status bit has been defined for the
captureBufferPacketStatus object, indicating that the
packet order within the capture buffer may not be identical to
the packet order as received off the wire. This bit may only
be used for packets transmitted by the probe. Older NMS
applications can safely ignore this status bit, which might be
used by newer agents.
2) The packetMatch trap has been removed. This trap was never
actually 'approved' and was not added to this document along
with the risingAlarm and fallingAlarm traps. The packetMatch
trap could not be throttled, which could cause disruption of
normal network traffic under some circumstances. An NMS should
configure a risingAlarm threshold on the appropriate
channelMatches instance if a trap is desired for a packetMatch
event. Note that logging of packetMatch events is still
supported--only trap generation for such events has been
removed.
In addition, several clarifications to individual object
definitions have been added to assist agent and NMS
implementors:
- global definition of 'good packets' and 'bad packets'
- more detailed text governing conceptual row creation and
modification
- instructions for probes relating to interface changes and
disruptions
- clarification of some ethernet counter definitions
- recommended formula for calculating network utilization
- clarification of channel and captureBuffer behavior for some
unusual conditions
- examples of proper instance naming for each table"
REVISION "199111010000Z" -- 1 Nov, 1991
DESCRIPTION
"The original version of this MIB, published as RFC1271."
|
|
iso(1)
