mirror of
https://github.com/librenms/librenms.git
synced 2024-10-07 16:52:45 +00:00
Remove Duplicate Mibs
This commit is contained in:
Rosiak
File diff suppressed because it is too large
Load Diff
@@ -1,772 +0,0 @@
|
||||
SNMPv2-TC DEFINITIONS ::= BEGIN
|
||||
|
||||
IMPORTS
|
||||
TimeTicks FROM SNMPv2-SMI;
|
||||
|
||||
-- definition of textual conventions
|
||||
|
||||
TEXTUAL-CONVENTION MACRO ::=
|
||||
|
||||
BEGIN
|
||||
TYPE NOTATION ::=
|
||||
DisplayPart
|
||||
"STATUS" Status
|
||||
"DESCRIPTION" Text
|
||||
ReferPart
|
||||
"SYNTAX" Syntax
|
||||
|
||||
VALUE NOTATION ::=
|
||||
value(VALUE Syntax) -- adapted ASN.1
|
||||
|
||||
DisplayPart ::=
|
||||
"DISPLAY-HINT" Text
|
||||
| empty
|
||||
|
||||
Status ::=
|
||||
"current"
|
||||
| "deprecated"
|
||||
| "obsolete"
|
||||
|
||||
ReferPart ::=
|
||||
"REFERENCE" Text
|
||||
| empty
|
||||
|
||||
-- a character string as defined in [2]
|
||||
Text ::= value(IA5String)
|
||||
|
||||
Syntax ::= -- Must be one of the following:
|
||||
-- a base type (or its refinement), or
|
||||
-- a BITS pseudo-type
|
||||
type
|
||||
| "BITS" "{" NamedBits "}"
|
||||
|
||||
NamedBits ::= NamedBit
|
||||
| NamedBits "," NamedBit
|
||||
|
||||
NamedBit ::= identifier "(" number ")" -- number is nonnegative
|
||||
|
||||
END
|
||||
|
||||
DisplayString ::= TEXTUAL-CONVENTION
|
||||
DISPLAY-HINT "255a"
|
||||
STATUS current
|
||||
DESCRIPTION
|
||||
"Represents textual information taken from the NVT ASCII
|
||||
|
||||
character set, as defined in pages 4, 10-11 of RFC 854.
|
||||
|
||||
To summarize RFC 854, the NVT ASCII repertoire specifies:
|
||||
|
||||
- the use of character codes 0-127 (decimal)
|
||||
|
||||
- the graphics characters (32-126) are interpreted as
|
||||
US ASCII
|
||||
|
||||
- NUL, LF, CR, BEL, BS, HT, VT and FF have the special
|
||||
meanings specified in RFC 854
|
||||
|
||||
- the other 25 codes have no standard interpretation
|
||||
|
||||
- the sequence 'CR LF' means newline
|
||||
|
||||
- the sequence 'CR NUL' means carriage-return
|
||||
|
||||
- an 'LF' not preceded by a 'CR' means moving to the
|
||||
same column on the next line.
|
||||
|
||||
- the sequence 'CR x' for any x other than LF or NUL is
|
||||
illegal. (Note that this also means that a string may
|
||||
end with either 'CR LF' or 'CR NUL', but not with CR.)
|
||||
|
||||
Any object defined using this syntax may not exceed 255
|
||||
characters in length."
|
||||
SYNTAX OCTET STRING (SIZE (0..255))
|
||||
|
||||
PhysAddress ::= TEXTUAL-CONVENTION
|
||||
DISPLAY-HINT "1x:"
|
||||
STATUS current
|
||||
DESCRIPTION
|
||||
"Represents media- or physical-level addresses."
|
||||
SYNTAX OCTET STRING
|
||||
|
||||
MacAddress ::= TEXTUAL-CONVENTION
|
||||
DISPLAY-HINT "1x:"
|
||||
STATUS current
|
||||
DESCRIPTION
|
||||
"Represents an 802 MAC address represented in the
|
||||
`canonical' order defined by IEEE 802.1a, i.e., as if it
|
||||
were transmitted least significant bit first, even though
|
||||
802.5 (in contrast to other 802.x protocols) requires MAC
|
||||
addresses to be transmitted most significant bit first."
|
||||
SYNTAX OCTET STRING (SIZE (6))
|
||||
|
||||
TruthValue ::= TEXTUAL-CONVENTION
|
||||
STATUS current
|
||||
DESCRIPTION
|
||||
"Represents a boolean value."
|
||||
SYNTAX INTEGER { true(1), false(2) }
|
||||
|
||||
TestAndIncr ::= TEXTUAL-CONVENTION
|
||||
STATUS current
|
||||
DESCRIPTION
|
||||
"Represents integer-valued information used for atomic
|
||||
operations. When the management protocol is used to specify
|
||||
that an object instance having this syntax is to be
|
||||
modified, the new value supplied via the management protocol
|
||||
must precisely match the value presently held by the
|
||||
instance. If not, the management protocol set operation
|
||||
fails with an error of `inconsistentValue'. Otherwise, if
|
||||
the current value is the maximum value of 2^31-1 (2147483647
|
||||
decimal), then the value held by the instance is wrapped to
|
||||
zero; otherwise, the value held by the instance is
|
||||
incremented by one. (Note that regardless of whether the
|
||||
management protocol set operation succeeds, the variable-
|
||||
binding in the request and response PDUs are identical.)
|
||||
|
||||
The value of the ACCESS clause for objects having this
|
||||
syntax is either `read-write' or `read-create'. When an
|
||||
instance of a columnar object having this syntax is created,
|
||||
any value may be supplied via the management protocol.
|
||||
|
||||
When the network management portion of the system is re-
|
||||
initialized, the value of every object instance having this
|
||||
syntax must either be incremented from its value prior to
|
||||
the re-initialization, or (if the value prior to the re-
|
||||
initialization is unknown) be set to a pseudo-randomly
|
||||
generated value."
|
||||
SYNTAX INTEGER (0..2147483647)
|
||||
|
||||
AutonomousType ::= TEXTUAL-CONVENTION
|
||||
STATUS current
|
||||
DESCRIPTION
|
||||
"Represents an independently extensible type identification
|
||||
value. It may, for example, indicate a particular sub-tree
|
||||
with further MIB definitions, or define a particular type of
|
||||
protocol or hardware."
|
||||
SYNTAX OBJECT IDENTIFIER
|
||||
|
||||
InstancePointer ::= TEXTUAL-CONVENTION
|
||||
STATUS obsolete
|
||||
DESCRIPTION
|
||||
"A pointer to either a specific instance of a MIB object or
|
||||
a conceptual row of a MIB table in the managed device. In
|
||||
the latter case, by convention, it is the name of the
|
||||
particular instance of the first accessible columnar object
|
||||
in the conceptual row.
|
||||
|
||||
The two uses of this textual convention are replaced by
|
||||
VariablePointer and RowPointer, respectively."
|
||||
SYNTAX OBJECT IDENTIFIER
|
||||
|
||||
VariablePointer ::= TEXTUAL-CONVENTION
|
||||
STATUS current
|
||||
DESCRIPTION
|
||||
"A pointer to a specific object instance. For example,
|
||||
sysContact.0 or ifInOctets.3."
|
||||
SYNTAX OBJECT IDENTIFIER
|
||||
|
||||
RowPointer ::= TEXTUAL-CONVENTION
|
||||
STATUS current
|
||||
DESCRIPTION
|
||||
"Represents a pointer to a conceptual row. The value is the
|
||||
name of the instance of the first accessible columnar object
|
||||
in the conceptual row.
|
||||
|
||||
For example, ifIndex.3 would point to the 3rd row in the
|
||||
ifTable (note that if ifIndex were not-accessible, then
|
||||
ifDescr.3 would be used instead)."
|
||||
SYNTAX OBJECT IDENTIFIER
|
||||
|
||||
RowStatus ::= TEXTUAL-CONVENTION
|
||||
STATUS current
|
||||
DESCRIPTION
|
||||
"The RowStatus textual convention is used to manage the
|
||||
creation and deletion of conceptual rows, and is used as the
|
||||
value of the SYNTAX clause for the status column of a
|
||||
conceptual row (as described in Section 7.7.1 of [2].)
|
||||
|
||||
The status column has six defined values:
|
||||
|
||||
- `active', which indicates that the conceptual row is
|
||||
available for use by the managed device;
|
||||
|
||||
- `notInService', which indicates that the conceptual
|
||||
row exists in the agent, but is unavailable for use by
|
||||
the managed device (see NOTE below); 'notInService' has
|
||||
no implication regarding the internal consistency of
|
||||
the row, availability of resources, or consistency with
|
||||
the current state of the managed device;
|
||||
|
||||
- `notReady', which indicates that the conceptual row
|
||||
exists in the agent, but is missing information
|
||||
necessary in order to be available for use by the
|
||||
managed device (i.e., one or more required columns in
|
||||
the conceptual row have not been instanciated);
|
||||
|
||||
- `createAndGo', which is supplied by a management
|
||||
station wishing to create a new instance of a
|
||||
conceptual row and to have its status automatically set
|
||||
to active, making it available for use by the managed
|
||||
device;
|
||||
|
||||
- `createAndWait', which is supplied by a management
|
||||
station wishing to create a new instance of a
|
||||
conceptual row (but not make it available for use by
|
||||
the managed device); and,
|
||||
- `destroy', which is supplied by a management station
|
||||
wishing to delete all of the instances associated with
|
||||
an existing conceptual row.
|
||||
|
||||
Whereas five of the six values (all except `notReady') may
|
||||
be specified in a management protocol set operation, only
|
||||
three values will be returned in response to a management
|
||||
protocol retrieval operation: `notReady', `notInService' or
|
||||
`active'. That is, when queried, an existing conceptual row
|
||||
has only three states: it is either available for use by
|
||||
the managed device (the status column has value `active');
|
||||
it is not available for use by the managed device, though
|
||||
the agent has sufficient information to attempt to make it
|
||||
so (the status column has value `notInService'); or, it is
|
||||
not available for use by the managed device, and an attempt
|
||||
to make it so would fail because the agent has insufficient
|
||||
information (the state column has value `notReady').
|
||||
|
||||
NOTE WELL
|
||||
|
||||
This textual convention may be used for a MIB table,
|
||||
irrespective of whether the values of that table's
|
||||
conceptual rows are able to be modified while it is
|
||||
active, or whether its conceptual rows must be taken
|
||||
out of service in order to be modified. That is, it is
|
||||
the responsibility of the DESCRIPTION clause of the
|
||||
status column to specify whether the status column must
|
||||
not be `active' in order for the value of some other
|
||||
column of the same conceptual row to be modified. If
|
||||
such a specification is made, affected columns may be
|
||||
changed by an SNMP set PDU if the RowStatus would not
|
||||
be equal to `active' either immediately before or after
|
||||
processing the PDU. In other words, if the PDU also
|
||||
contained a varbind that would change the RowStatus
|
||||
value, the column in question may be changed if the
|
||||
RowStatus was not equal to `active' as the PDU was
|
||||
received, or if the varbind sets the status to a value
|
||||
other than 'active'.
|
||||
|
||||
Also note that whenever any elements of a row exist, the
|
||||
RowStatus column must also exist.
|
||||
|
||||
To summarize the effect of having a conceptual row with a
|
||||
status column having a SYNTAX clause value of RowStatus,
|
||||
consider the following state diagram:
|
||||
|
||||
STATE
|
||||
+--------------+-----------+-------------+-------------
|
||||
| A | B | C | D
|
||||
| |status col.|status column|
|
||||
|status column | is | is |status column
|
||||
ACTION |does not exist| notReady | notInService| is active
|
||||
--------------+--------------+-----------+-------------+-------------
|
||||
set status |noError ->D|inconsist- |inconsistent-|inconsistent-
|
||||
column to | or | entValue| Value| Value
|
||||
createAndGo |inconsistent- | | |
|
||||
| Value| | |
|
||||
--------------+--------------+-----------+-------------+-------------
|
||||
set status |noError see 1|inconsist- |inconsistent-|inconsistent-
|
||||
column to | or | entValue| Value| Value
|
||||
createAndWait |wrongValue | | |
|
||||
--------------+--------------+-----------+-------------+-------------
|
||||
set status |inconsistent- |inconsist- |noError |noError
|
||||
column to | Value| entValue| |
|
||||
active | | | |
|
||||
| | or | |
|
||||
| | | |
|
||||
| |see 2 ->D|see 8 ->D| ->D
|
||||
--------------+--------------+-----------+-------------+-------------
|
||||
set status |inconsistent- |inconsist- |noError |noError ->C
|
||||
column to | Value| entValue| |
|
||||
notInService | | | |
|
||||
| | or | | or
|
||||
| | | |
|
||||
| |see 3 ->C| ->C|see 6
|
||||
--------------+--------------+-----------+-------------+-------------
|
||||
set status |noError |noError |noError |noError ->A
|
||||
column to | | | | or
|
||||
destroy | ->A| ->A| ->A|see 7
|
||||
--------------+--------------+-----------+-------------+-------------
|
||||
set any other |see 4 |noError |noError |see 5
|
||||
column to some| | | |
|
||||
value | | see 1| ->C| ->D
|
||||
--------------+--------------+-----------+-------------+-------------
|
||||
|
||||
(1) goto B or C, depending on information available to the
|
||||
agent.
|
||||
|
||||
(2) if other variable bindings included in the same PDU,
|
||||
provide values for all columns which are missing but
|
||||
required, and all columns have acceptable values, then
|
||||
return noError and goto D.
|
||||
|
||||
(3) if other variable bindings included in the same PDU,
|
||||
provide legal values for all columns which are missing but
|
||||
required, then return noError and goto C.
|
||||
|
||||
(4) at the discretion of the agent, the return value may be
|
||||
either:
|
||||
|
||||
inconsistentName: because the agent does not choose to
|
||||
create such an instance when the corresponding
|
||||
RowStatus instance does not exist, or
|
||||
|
||||
inconsistentValue: if the supplied value is
|
||||
inconsistent with the state of some other MIB object's
|
||||
value, or
|
||||
|
||||
noError: because the agent chooses to create the
|
||||
instance.
|
||||
|
||||
If noError is returned, then the instance of the status
|
||||
column must also be created, and the new state is B or C,
|
||||
depending on the information available to the agent. If
|
||||
inconsistentName or inconsistentValue is returned, the row
|
||||
remains in state A.
|
||||
|
||||
(5) depending on the MIB definition for the column/table,
|
||||
either noError or inconsistentValue may be returned.
|
||||
|
||||
(6) the return value can indicate one of the following
|
||||
errors:
|
||||
|
||||
wrongValue: because the agent does not support
|
||||
notInService (e.g., an agent which does not support
|
||||
createAndWait), or
|
||||
|
||||
inconsistentValue: because the agent is unable to take
|
||||
the row out of service at this time, perhaps because it
|
||||
is in use and cannot be de-activated.
|
||||
|
||||
(7) the return value can indicate the following error:
|
||||
|
||||
inconsistentValue: because the agent is unable to
|
||||
remove the row at this time, perhaps because it is in
|
||||
use and cannot be de-activated.
|
||||
|
||||
(8) the transition to D can fail, e.g., if the values of the
|
||||
conceptual row are inconsistent, then the error code would
|
||||
be inconsistentValue.
|
||||
|
||||
NOTE: Other processing of (this and other varbinds of) the
|
||||
set request may result in a response other than noError
|
||||
being returned, e.g., wrongValue, noCreation, etc.
|
||||
|
||||
Conceptual Row Creation
|
||||
|
||||
There are four potential interactions when creating a
|
||||
conceptual row: selecting an instance-identifier which is
|
||||
not in use; creating the conceptual row; initializing any
|
||||
objects for which the agent does not supply a default; and,
|
||||
making the conceptual row available for use by the managed
|
||||
device.
|
||||
|
||||
Interaction 1: Selecting an Instance-Identifier
|
||||
|
||||
The algorithm used to select an instance-identifier varies
|
||||
for each conceptual row. In some cases, the instance-
|
||||
identifier is semantically significant, e.g., the
|
||||
destination address of a route, and a management station
|
||||
selects the instance-identifier according to the semantics.
|
||||
|
||||
In other cases, the instance-identifier is used solely to
|
||||
distinguish conceptual rows, and a management station
|
||||
without specific knowledge of the conceptual row might
|
||||
examine the instances present in order to determine an
|
||||
unused instance-identifier. (This approach may be used, but
|
||||
it is often highly sub-optimal; however, it is also a
|
||||
questionable practice for a naive management station to
|
||||
attempt conceptual row creation.)
|
||||
|
||||
Alternately, the MIB module which defines the conceptual row
|
||||
might provide one or more objects which provide assistance
|
||||
in determining an unused instance-identifier. For example,
|
||||
if the conceptual row is indexed by an integer-value, then
|
||||
an object having an integer-valued SYNTAX clause might be
|
||||
defined for such a purpose, allowing a management station to
|
||||
issue a management protocol retrieval operation. In order
|
||||
to avoid unnecessary collisions between competing management
|
||||
stations, `adjacent' retrievals of this object should be
|
||||
different.
|
||||
|
||||
Finally, the management station could select a pseudo-random
|
||||
number to use as the index. In the event that this index
|
||||
|
||||
was already in use and an inconsistentValue was returned in
|
||||
response to the management protocol set operation, the
|
||||
management station should simply select a new pseudo-random
|
||||
number and retry the operation.
|
||||
|
||||
A MIB designer should choose between the two latter
|
||||
algorithms based on the size of the table (and therefore the
|
||||
efficiency of each algorithm). For tables in which a large
|
||||
number of entries are expected, it is recommended that a MIB
|
||||
object be defined that returns an acceptable index for
|
||||
creation. For tables with small numbers of entries, it is
|
||||
recommended that the latter pseudo-random index mechanism be
|
||||
used.
|
||||
|
||||
Interaction 2: Creating the Conceptual Row
|
||||
|
||||
Once an unused instance-identifier has been selected, the
|
||||
management station determines if it wishes to create and
|
||||
activate the conceptual row in one transaction or in a
|
||||
negotiated set of interactions.
|
||||
|
||||
Interaction 2a: Creating and Activating the Conceptual Row
|
||||
|
||||
The management station must first determine the column
|
||||
requirements, i.e., it must determine those columns for
|
||||
which it must or must not provide values. Depending on the
|
||||
complexity of the table and the management station's
|
||||
knowledge of the agent's capabilities, this determination
|
||||
can be made locally by the management station. Alternately,
|
||||
the management station issues a management protocol get
|
||||
operation to examine all columns in the conceptual row that
|
||||
it wishes to create. In response, for each column, there
|
||||
are three possible outcomes:
|
||||
|
||||
- a value is returned, indicating that some other
|
||||
management station has already created this conceptual
|
||||
row. We return to interaction 1.
|
||||
|
||||
- the exception `noSuchInstance' is returned,
|
||||
indicating that the agent implements the object-type
|
||||
associated with this column, and that this column in at
|
||||
least one conceptual row would be accessible in the MIB
|
||||
view used by the retrieval were it to exist. For those
|
||||
columns to which the agent provides read-create access,
|
||||
the `noSuchInstance' exception tells the management
|
||||
station that it should supply a value for this column
|
||||
when the conceptual row is to be created.
|
||||
|
||||
- the exception `noSuchObject' is returned, indicating
|
||||
that the agent does not implement the object-type
|
||||
associated with this column or that there is no
|
||||
conceptual row for which this column would be
|
||||
accessible in the MIB view used by the retrieval. As
|
||||
such, the management station can not issue any
|
||||
management protocol set operations to create an
|
||||
instance of this column.
|
||||
|
||||
Once the column requirements have been determined, a
|
||||
management protocol set operation is accordingly issued.
|
||||
This operation also sets the new instance of the status
|
||||
column to `createAndGo'.
|
||||
|
||||
When the agent processes the set operation, it verifies that
|
||||
it has sufficient information to make the conceptual row
|
||||
available for use by the managed device. The information
|
||||
available to the agent is provided by two sources: the
|
||||
management protocol set operation which creates the
|
||||
conceptual row, and, implementation-specific defaults
|
||||
supplied by the agent (note that an agent must provide
|
||||
implementation-specific defaults for at least those objects
|
||||
which it implements as read-only). If there is sufficient
|
||||
information available, then the conceptual row is created, a
|
||||
`noError' response is returned, the status column is set to
|
||||
`active', and no further interactions are necessary (i.e.,
|
||||
interactions 3 and 4 are skipped). If there is insufficient
|
||||
information, then the conceptual row is not created, and the
|
||||
set operation fails with an error of `inconsistentValue'.
|
||||
On this error, the management station can issue a management
|
||||
protocol retrieval operation to determine if this was
|
||||
because it failed to specify a value for a required column,
|
||||
or, because the selected instance of the status column
|
||||
already existed. In the latter case, we return to
|
||||
interaction 1. In the former case, the management station
|
||||
can re-issue the set operation with the additional
|
||||
information, or begin interaction 2 again using
|
||||
`createAndWait' in order to negotiate creation of the
|
||||
conceptual row.
|
||||
|
||||
NOTE WELL
|
||||
|
||||
Regardless of the method used to determine the column
|
||||
requirements, it is possible that the management
|
||||
station might deem a column necessary when, in fact,
|
||||
the agent will not allow that particular columnar
|
||||
instance to be created or written. In this case, the
|
||||
management protocol set operation will fail with an
|
||||
error such as `noCreation' or `notWritable'. In this
|
||||
case, the management station decides whether it needs
|
||||
to be able to set a value for that particular columnar
|
||||
instance. If not, the management station re-issues the
|
||||
management protocol set operation, but without setting
|
||||
a value for that particular columnar instance;
|
||||
otherwise, the management station aborts the row
|
||||
creation algorithm.
|
||||
|
||||
Interaction 2b: Negotiating the Creation of the Conceptual
|
||||
Row
|
||||
|
||||
The management station issues a management protocol set
|
||||
operation which sets the desired instance of the status
|
||||
column to `createAndWait'. If the agent is unwilling to
|
||||
process a request of this sort, the set operation fails with
|
||||
an error of `wrongValue'. (As a consequence, such an agent
|
||||
must be prepared to accept a single management protocol set
|
||||
operation, i.e., interaction 2a above, containing all of the
|
||||
columns indicated by its column requirements.) Otherwise,
|
||||
the conceptual row is created, a `noError' response is
|
||||
returned, and the status column is immediately set to either
|
||||
`notInService' or `notReady', depending on whether it has
|
||||
sufficient information to (attempt to) make the conceptual
|
||||
row available for use by the managed device. If there is
|
||||
sufficient information available, then the status column is
|
||||
set to `notInService'; otherwise, if there is insufficient
|
||||
information, then the status column is set to `notReady'.
|
||||
Regardless, we proceed to interaction 3.
|
||||
|
||||
Interaction 3: Initializing non-defaulted Objects
|
||||
|
||||
The management station must now determine the column
|
||||
requirements. It issues a management protocol get operation
|
||||
to examine all columns in the created conceptual row. In
|
||||
the response, for each column, there are three possible
|
||||
outcomes:
|
||||
|
||||
- a value is returned, indicating that the agent
|
||||
implements the object-type associated with this column
|
||||
and had sufficient information to provide a value. For
|
||||
those columns to which the agent provides read-create
|
||||
access (and for which the agent allows their values to
|
||||
be changed after their creation), a value return tells
|
||||
the management station that it may issue additional
|
||||
management protocol set operations, if it desires, in
|
||||
order to change the value associated with this column.
|
||||
|
||||
- the exception `noSuchInstance' is returned,
|
||||
indicating that the agent implements the object-type
|
||||
associated with this column, and that this column in at
|
||||
least one conceptual row would be accessible in the MIB
|
||||
view used by the retrieval were it to exist. However,
|
||||
the agent does not have sufficient information to
|
||||
provide a value, and until a value is provided, the
|
||||
conceptual row may not be made available for use by the
|
||||
managed device. For those columns to which the agent
|
||||
provides read-create access, the `noSuchInstance'
|
||||
exception tells the management station that it must
|
||||
issue additional management protocol set operations, in
|
||||
order to provide a value associated with this column.
|
||||
|
||||
- the exception `noSuchObject' is returned, indicating
|
||||
that the agent does not implement the object-type
|
||||
associated with this column or that there is no
|
||||
conceptual row for which this column would be
|
||||
accessible in the MIB view used by the retrieval. As
|
||||
such, the management station can not issue any
|
||||
management protocol set operations to create an
|
||||
instance of this column.
|
||||
|
||||
If the value associated with the status column is
|
||||
`notReady', then the management station must first deal with
|
||||
all `noSuchInstance' columns, if any. Having done so, the
|
||||
value of the status column becomes `notInService', and we
|
||||
proceed to interaction 4.
|
||||
|
||||
Interaction 4: Making the Conceptual Row Available
|
||||
|
||||
Once the management station is satisfied with the values
|
||||
associated with the columns of the conceptual row, it issues
|
||||
a management protocol set operation to set the status column
|
||||
to `active'. If the agent has sufficient information to
|
||||
make the conceptual row available for use by the managed
|
||||
device, the management protocol set operation succeeds (a
|
||||
`noError' response is returned). Otherwise, the management
|
||||
protocol set operation fails with an error of
|
||||
`inconsistentValue'.
|
||||
|
||||
NOTE WELL
|
||||
|
||||
A conceptual row having a status column with value
|
||||
`notInService' or `notReady' is unavailable to the
|
||||
managed device. As such, it is possible for the
|
||||
managed device to create its own instances during the
|
||||
time between the management protocol set operation
|
||||
which sets the status column to `createAndWait' and the
|
||||
management protocol set operation which sets the status
|
||||
column to `active'. In this case, when the management
|
||||
protocol set operation is issued to set the status
|
||||
column to `active', the values held in the agent
|
||||
supersede those used by the managed device.
|
||||
|
||||
If the management station is prevented from setting the
|
||||
status column to `active' (e.g., due to management station
|
||||
or network failure) the conceptual row will be left in the
|
||||
`notInService' or `notReady' state, consuming resources
|
||||
indefinitely. The agent must detect conceptual rows that
|
||||
have been in either state for an abnormally long period of
|
||||
time and remove them. It is the responsibility of the
|
||||
DESCRIPTION clause of the status column to indicate what an
|
||||
abnormally long period of time would be. This period of
|
||||
time should be long enough to allow for human response time
|
||||
(including `think time') between the creation of the
|
||||
conceptual row and the setting of the status to `active'.
|
||||
In the absence of such information in the DESCRIPTION
|
||||
clause, it is suggested that this period be approximately 5
|
||||
minutes in length. This removal action applies not only to
|
||||
newly-created rows, but also to previously active rows which
|
||||
are set to, and left in, the notInService state for a
|
||||
prolonged period exceeding that which is considered normal
|
||||
for such a conceptual row.
|
||||
|
||||
Conceptual Row Suspension
|
||||
|
||||
When a conceptual row is `active', the management station
|
||||
may issue a management protocol set operation which sets the
|
||||
instance of the status column to `notInService'. If the
|
||||
agent is unwilling to do so, the set operation fails with an
|
||||
error of `wrongValue' or `inconsistentValue'. Otherwise,
|
||||
the conceptual row is taken out of service, and a `noError'
|
||||
response is returned. It is the responsibility of the
|
||||
DESCRIPTION clause of the status column to indicate under
|
||||
what circumstances the status column should be taken out of
|
||||
service (e.g., in order for the value of some other column
|
||||
of the same conceptual row to be modified).
|
||||
|
||||
Conceptual Row Deletion
|
||||
|
||||
For deletion of conceptual rows, a management protocol set
|
||||
operation is issued which sets the instance of the status
|
||||
column to `destroy'. This request may be made regardless of
|
||||
the current value of the status column (e.g., it is possible
|
||||
to delete conceptual rows which are either `notReady',
|
||||
`notInService' or `active'.) If the operation succeeds,
|
||||
then all instances associated with the conceptual row are
|
||||
immediately removed."
|
||||
SYNTAX INTEGER {
|
||||
-- the following two values are states:
|
||||
-- these values may be read or written
|
||||
active(1),
|
||||
notInService(2),
|
||||
-- the following value is a state:
|
||||
-- this value may be read, but not written
|
||||
notReady(3),
|
||||
-- the following three values are
|
||||
-- actions: these values may be written,
|
||||
-- but are never read
|
||||
createAndGo(4),
|
||||
createAndWait(5),
|
||||
destroy(6)
|
||||
}
|
||||
|
||||
TimeStamp ::= TEXTUAL-CONVENTION
|
||||
STATUS current
|
||||
DESCRIPTION
|
||||
"The value of the sysUpTime object at which a specific
|
||||
occurrence happened. The specific occurrence must be
|
||||
|
||||
defined in the description of any object defined using this
|
||||
type.
|
||||
|
||||
If sysUpTime is reset to zero as a result of a re-
|
||||
initialization of the network management (sub)system, then
|
||||
the values of all TimeStamp objects are also reset.
|
||||
However, after approximately 497 days without a re-
|
||||
initialization, the sysUpTime object will reach 2^^32-1 and
|
||||
then increment around to zero; in this case, existing values
|
||||
of TimeStamp objects do not change. This can lead to
|
||||
ambiguities in the value of TimeStamp objects."
|
||||
SYNTAX TimeTicks
|
||||
|
||||
TimeInterval ::= TEXTUAL-CONVENTION
|
||||
STATUS current
|
||||
DESCRIPTION
|
||||
"A period of time, measured in units of 0.01 seconds."
|
||||
SYNTAX INTEGER (0..2147483647)
|
||||
|
||||
DateAndTime ::= TEXTUAL-CONVENTION
|
||||
DISPLAY-HINT "2d-1d-1d,1d:1d:1d.1d,1a1d:1d"
|
||||
STATUS current
|
||||
DESCRIPTION
|
||||
"A date-time specification.
|
||||
|
||||
field octets contents range
|
||||
----- ------ -------- -----
|
||||
1 1-2 year* 0..65536
|
||||
2 3 month 1..12
|
||||
3 4 day 1..31
|
||||
4 5 hour 0..23
|
||||
5 6 minutes 0..59
|
||||
6 7 seconds 0..60
|
||||
(use 60 for leap-second)
|
||||
7 8 deci-seconds 0..9
|
||||
8 9 direction from UTC '+' / '-'
|
||||
9 10 hours from UTC* 0..13
|
||||
10 11 minutes from UTC 0..59
|
||||
|
||||
* Notes:
|
||||
- the value of year is in network-byte order
|
||||
- daylight saving time in New Zealand is +13
|
||||
|
||||
For example, Tuesday May 26, 1992 at 1:30:15 PM EDT would be
|
||||
displayed as:
|
||||
|
||||
1992-5-26,13:30:15.0,-4:0
|
||||
|
||||
Note that if only local time is known, then timezone
|
||||
information (fields 8-10) is not present."
|
||||
SYNTAX OCTET STRING (SIZE (8 | 11))
|
||||
|
||||
StorageType ::= TEXTUAL-CONVENTION
|
||||
STATUS current
|
||||
DESCRIPTION
|
||||
"Describes the memory realization of a conceptual row. A
|
||||
row which is volatile(2) is lost upon reboot. A row which
|
||||
is either nonVolatile(3), permanent(4) or readOnly(5), is
|
||||
backed up by stable storage. A row which is permanent(4)
|
||||
can be changed but not deleted. A row which is readOnly(5)
|
||||
cannot be changed nor deleted.
|
||||
|
||||
If the value of an object with this syntax is either
|
||||
permanent(4) or readOnly(5), it cannot be written.
|
||||
Conversely, if the value is either other(1), volatile(2) or
|
||||
nonVolatile(3), it cannot be modified to be permanent(4) or
|
||||
readOnly(5). (All illegal modifications result in a
|
||||
'wrongValue' error.)
|
||||
|
||||
Every usage of this textual convention is required to
|
||||
specify the columnar objects which a permanent(4) row must
|
||||
at a minimum allow to be writable."
|
||||
SYNTAX INTEGER {
|
||||
other(1), -- eh?
|
||||
volatile(2), -- e.g., in RAM
|
||||
nonVolatile(3), -- e.g., in NVRAM
|
||||
permanent(4), -- e.g., partially in ROM
|
||||
readOnly(5) -- e.g., completely in ROM
|
||||
}
|
||||
|
||||
TDomain ::= TEXTUAL-CONVENTION
|
||||
STATUS current
|
||||
DESCRIPTION
|
||||
"Denotes a kind of transport service.
|
||||
|
||||
Some possible values, such as snmpUDPDomain, are defined in
|
||||
the SNMPv2-TM MIB module. Other possible values are defined
|
||||
in other MIB modules."
|
||||
REFERENCE "The SNMPv2-TM MIB module is defined in RFC 1906."
|
||||
SYNTAX OBJECT IDENTIFIER
|
||||
|
||||
TAddress ::= TEXTUAL-CONVENTION
|
||||
STATUS current
|
||||
DESCRIPTION
|
||||
"Denotes a transport service address.
|
||||
|
||||
A TAddress value is always interpreted within the context of a
|
||||
TDomain value. Thus, each definition of a TDomain value must
|
||||
be accompanied by a definition of a textual convention for use
|
||||
with that TDomain. Some possible textual conventions, such as
|
||||
SnmpUDPAddress for snmpUDPDomain, are defined in the SNMPv2-TM
|
||||
MIB module. Other possible textual conventions are defined in
|
||||
other MIB modules."
|
||||
REFERENCE "The SNMPv2-TM MIB module is defined in RFC 1906."
|
||||
SYNTAX OCTET STRING (SIZE (1..255))
|
||||
|
||||
END
|
||||
File diff suppressed because it is too large
Load Diff
@@ -1,772 +0,0 @@
|
||||
SNMPv2-TC DEFINITIONS ::= BEGIN
|
||||
|
||||
IMPORTS
|
||||
TimeTicks FROM SNMPv2-SMI;
|
||||
|
||||
-- definition of textual conventions
|
||||
|
||||
TEXTUAL-CONVENTION MACRO ::=
|
||||
|
||||
BEGIN
|
||||
TYPE NOTATION ::=
|
||||
DisplayPart
|
||||
"STATUS" Status
|
||||
"DESCRIPTION" Text
|
||||
ReferPart
|
||||
"SYNTAX" Syntax
|
||||
|
||||
VALUE NOTATION ::=
|
||||
value(VALUE Syntax) -- adapted ASN.1
|
||||
|
||||
DisplayPart ::=
|
||||
"DISPLAY-HINT" Text
|
||||
| empty
|
||||
|
||||
Status ::=
|
||||
"current"
|
||||
| "deprecated"
|
||||
| "obsolete"
|
||||
|
||||
ReferPart ::=
|
||||
"REFERENCE" Text
|
||||
| empty
|
||||
|
||||
-- a character string as defined in [2]
|
||||
Text ::= value(IA5String)
|
||||
|
||||
Syntax ::= -- Must be one of the following:
|
||||
-- a base type (or its refinement), or
|
||||
-- a BITS pseudo-type
|
||||
type
|
||||
| "BITS" "{" NamedBits "}"
|
||||
|
||||
NamedBits ::= NamedBit
|
||||
| NamedBits "," NamedBit
|
||||
|
||||
NamedBit ::= identifier "(" number ")" -- number is nonnegative
|
||||
|
||||
END
|
||||
|
||||
DisplayString ::= TEXTUAL-CONVENTION
|
||||
DISPLAY-HINT "255a"
|
||||
STATUS current
|
||||
DESCRIPTION
|
||||
"Represents textual information taken from the NVT ASCII
|
||||
|
||||
character set, as defined in pages 4, 10-11 of RFC 854.
|
||||
|
||||
To summarize RFC 854, the NVT ASCII repertoire specifies:
|
||||
|
||||
- the use of character codes 0-127 (decimal)
|
||||
|
||||
- the graphics characters (32-126) are interpreted as
|
||||
US ASCII
|
||||
|
||||
- NUL, LF, CR, BEL, BS, HT, VT and FF have the special
|
||||
meanings specified in RFC 854
|
||||
|
||||
- the other 25 codes have no standard interpretation
|
||||
|
||||
- the sequence 'CR LF' means newline
|
||||
|
||||
- the sequence 'CR NUL' means carriage-return
|
||||
|
||||
- an 'LF' not preceded by a 'CR' means moving to the
|
||||
same column on the next line.
|
||||
|
||||
- the sequence 'CR x' for any x other than LF or NUL is
|
||||
illegal. (Note that this also means that a string may
|
||||
end with either 'CR LF' or 'CR NUL', but not with CR.)
|
||||
|
||||
Any object defined using this syntax may not exceed 255
|
||||
characters in length."
|
||||
SYNTAX OCTET STRING (SIZE (0..255))
|
||||
|
||||
PhysAddress ::= TEXTUAL-CONVENTION
|
||||
DISPLAY-HINT "1x:"
|
||||
STATUS current
|
||||
DESCRIPTION
|
||||
"Represents media- or physical-level addresses."
|
||||
SYNTAX OCTET STRING
|
||||
|
||||
MacAddress ::= TEXTUAL-CONVENTION
|
||||
DISPLAY-HINT "1x:"
|
||||
STATUS current
|
||||
DESCRIPTION
|
||||
"Represents an 802 MAC address represented in the
|
||||
`canonical' order defined by IEEE 802.1a, i.e., as if it
|
||||
were transmitted least significant bit first, even though
|
||||
802.5 (in contrast to other 802.x protocols) requires MAC
|
||||
addresses to be transmitted most significant bit first."
|
||||
SYNTAX OCTET STRING (SIZE (6))
|
||||
|
||||
TruthValue ::= TEXTUAL-CONVENTION
|
||||
STATUS current
|
||||
DESCRIPTION
|
||||
"Represents a boolean value."
|
||||
SYNTAX INTEGER { true(1), false(2) }
|
||||
|
||||
TestAndIncr ::= TEXTUAL-CONVENTION
|
||||
STATUS current
|
||||
DESCRIPTION
|
||||
"Represents integer-valued information used for atomic
|
||||
operations. When the management protocol is used to specify
|
||||
that an object instance having this syntax is to be
|
||||
modified, the new value supplied via the management protocol
|
||||
must precisely match the value presently held by the
|
||||
instance. If not, the management protocol set operation
|
||||
fails with an error of `inconsistentValue'. Otherwise, if
|
||||
the current value is the maximum value of 2^31-1 (2147483647
|
||||
decimal), then the value held by the instance is wrapped to
|
||||
zero; otherwise, the value held by the instance is
|
||||
incremented by one. (Note that regardless of whether the
|
||||
management protocol set operation succeeds, the variable-
|
||||
binding in the request and response PDUs are identical.)
|
||||
|
||||
The value of the ACCESS clause for objects having this
|
||||
syntax is either `read-write' or `read-create'. When an
|
||||
instance of a columnar object having this syntax is created,
|
||||
any value may be supplied via the management protocol.
|
||||
|
||||
When the network management portion of the system is re-
|
||||
initialized, the value of every object instance having this
|
||||
syntax must either be incremented from its value prior to
|
||||
the re-initialization, or (if the value prior to the re-
|
||||
initialization is unknown) be set to a pseudo-randomly
|
||||
generated value."
|
||||
SYNTAX INTEGER (0..2147483647)
|
||||
|
||||
AutonomousType ::= TEXTUAL-CONVENTION
|
||||
STATUS current
|
||||
DESCRIPTION
|
||||
"Represents an independently extensible type identification
|
||||
value. It may, for example, indicate a particular sub-tree
|
||||
with further MIB definitions, or define a particular type of
|
||||
protocol or hardware."
|
||||
SYNTAX OBJECT IDENTIFIER
|
||||
|
||||
InstancePointer ::= TEXTUAL-CONVENTION
|
||||
STATUS obsolete
|
||||
DESCRIPTION
|
||||
"A pointer to either a specific instance of a MIB object or
|
||||
a conceptual row of a MIB table in the managed device. In
|
||||
the latter case, by convention, it is the name of the
|
||||
particular instance of the first accessible columnar object
|
||||
in the conceptual row.
|
||||
|
||||
The two uses of this textual convention are replaced by
|
||||
VariablePointer and RowPointer, respectively."
|
||||
SYNTAX OBJECT IDENTIFIER
|
||||
|
||||
VariablePointer ::= TEXTUAL-CONVENTION
|
||||
STATUS current
|
||||
DESCRIPTION
|
||||
"A pointer to a specific object instance. For example,
|
||||
sysContact.0 or ifInOctets.3."
|
||||
SYNTAX OBJECT IDENTIFIER
|
||||
|
||||
RowPointer ::= TEXTUAL-CONVENTION
|
||||
STATUS current
|
||||
DESCRIPTION
|
||||
"Represents a pointer to a conceptual row. The value is the
|
||||
name of the instance of the first accessible columnar object
|
||||
in the conceptual row.
|
||||
|
||||
For example, ifIndex.3 would point to the 3rd row in the
|
||||
ifTable (note that if ifIndex were not-accessible, then
|
||||
ifDescr.3 would be used instead)."
|
||||
SYNTAX OBJECT IDENTIFIER
|
||||
|
||||
RowStatus ::= TEXTUAL-CONVENTION
|
||||
STATUS current
|
||||
DESCRIPTION
|
||||
"The RowStatus textual convention is used to manage the
|
||||
creation and deletion of conceptual rows, and is used as the
|
||||
value of the SYNTAX clause for the status column of a
|
||||
conceptual row (as described in Section 7.7.1 of [2].)
|
||||
|
||||
The status column has six defined values:
|
||||
|
||||
- `active', which indicates that the conceptual row is
|
||||
available for use by the managed device;
|
||||
|
||||
- `notInService', which indicates that the conceptual
|
||||
row exists in the agent, but is unavailable for use by
|
||||
the managed device (see NOTE below); 'notInService' has
|
||||
no implication regarding the internal consistency of
|
||||
the row, availability of resources, or consistency with
|
||||
the current state of the managed device;
|
||||
|
||||
- `notReady', which indicates that the conceptual row
|
||||
exists in the agent, but is missing information
|
||||
necessary in order to be available for use by the
|
||||
managed device (i.e., one or more required columns in
|
||||
the conceptual row have not been instanciated);
|
||||
|
||||
- `createAndGo', which is supplied by a management
|
||||
station wishing to create a new instance of a
|
||||
conceptual row and to have its status automatically set
|
||||
to active, making it available for use by the managed
|
||||
device;
|
||||
|
||||
- `createAndWait', which is supplied by a management
|
||||
station wishing to create a new instance of a
|
||||
conceptual row (but not make it available for use by
|
||||
the managed device); and,
|
||||
- `destroy', which is supplied by a management station
|
||||
wishing to delete all of the instances associated with
|
||||
an existing conceptual row.
|
||||
|
||||
Whereas five of the six values (all except `notReady') may
|
||||
be specified in a management protocol set operation, only
|
||||
three values will be returned in response to a management
|
||||
protocol retrieval operation: `notReady', `notInService' or
|
||||
`active'. That is, when queried, an existing conceptual row
|
||||
has only three states: it is either available for use by
|
||||
the managed device (the status column has value `active');
|
||||
it is not available for use by the managed device, though
|
||||
the agent has sufficient information to attempt to make it
|
||||
so (the status column has value `notInService'); or, it is
|
||||
not available for use by the managed device, and an attempt
|
||||
to make it so would fail because the agent has insufficient
|
||||
information (the state column has value `notReady').
|
||||
|
||||
NOTE WELL
|
||||
|
||||
This textual convention may be used for a MIB table,
|
||||
irrespective of whether the values of that table's
|
||||
conceptual rows are able to be modified while it is
|
||||
active, or whether its conceptual rows must be taken
|
||||
out of service in order to be modified. That is, it is
|
||||
the responsibility of the DESCRIPTION clause of the
|
||||
status column to specify whether the status column must
|
||||
not be `active' in order for the value of some other
|
||||
column of the same conceptual row to be modified. If
|
||||
such a specification is made, affected columns may be
|
||||
changed by an SNMP set PDU if the RowStatus would not
|
||||
be equal to `active' either immediately before or after
|
||||
processing the PDU. In other words, if the PDU also
|
||||
contained a varbind that would change the RowStatus
|
||||
value, the column in question may be changed if the
|
||||
RowStatus was not equal to `active' as the PDU was
|
||||
received, or if the varbind sets the status to a value
|
||||
other than 'active'.
|
||||
|
||||
Also note that whenever any elements of a row exist, the
|
||||
RowStatus column must also exist.
|
||||
|
||||
To summarize the effect of having a conceptual row with a
|
||||
status column having a SYNTAX clause value of RowStatus,
|
||||
consider the following state diagram:
|
||||
|
||||
STATE
|
||||
+--------------+-----------+-------------+-------------
|
||||
| A | B | C | D
|
||||
| |status col.|status column|
|
||||
|status column | is | is |status column
|
||||
ACTION |does not exist| notReady | notInService| is active
|
||||
--------------+--------------+-----------+-------------+-------------
|
||||
set status |noError ->D|inconsist- |inconsistent-|inconsistent-
|
||||
column to | or | entValue| Value| Value
|
||||
createAndGo |inconsistent- | | |
|
||||
| Value| | |
|
||||
--------------+--------------+-----------+-------------+-------------
|
||||
set status |noError see 1|inconsist- |inconsistent-|inconsistent-
|
||||
column to | or | entValue| Value| Value
|
||||
createAndWait |wrongValue | | |
|
||||
--------------+--------------+-----------+-------------+-------------
|
||||
set status |inconsistent- |inconsist- |noError |noError
|
||||
column to | Value| entValue| |
|
||||
active | | | |
|
||||
| | or | |
|
||||
| | | |
|
||||
| |see 2 ->D|see 8 ->D| ->D
|
||||
--------------+--------------+-----------+-------------+-------------
|
||||
set status |inconsistent- |inconsist- |noError |noError ->C
|
||||
column to | Value| entValue| |
|
||||
notInService | | | |
|
||||
| | or | | or
|
||||
| | | |
|
||||
| |see 3 ->C| ->C|see 6
|
||||
--------------+--------------+-----------+-------------+-------------
|
||||
set status |noError |noError |noError |noError ->A
|
||||
column to | | | | or
|
||||
destroy | ->A| ->A| ->A|see 7
|
||||
--------------+--------------+-----------+-------------+-------------
|
||||
set any other |see 4 |noError |noError |see 5
|
||||
column to some| | | |
|
||||
value | | see 1| ->C| ->D
|
||||
--------------+--------------+-----------+-------------+-------------
|
||||
|
||||
(1) goto B or C, depending on information available to the
|
||||
agent.
|
||||
|
||||
(2) if other variable bindings included in the same PDU,
|
||||
provide values for all columns which are missing but
|
||||
required, and all columns have acceptable values, then
|
||||
return noError and goto D.
|
||||
|
||||
(3) if other variable bindings included in the same PDU,
|
||||
provide legal values for all columns which are missing but
|
||||
required, then return noError and goto C.
|
||||
|
||||
(4) at the discretion of the agent, the return value may be
|
||||
either:
|
||||
|
||||
inconsistentName: because the agent does not choose to
|
||||
create such an instance when the corresponding
|
||||
RowStatus instance does not exist, or
|
||||
|
||||
inconsistentValue: if the supplied value is
|
||||
inconsistent with the state of some other MIB object's
|
||||
value, or
|
||||
|
||||
noError: because the agent chooses to create the
|
||||
instance.
|
||||
|
||||
If noError is returned, then the instance of the status
|
||||
column must also be created, and the new state is B or C,
|
||||
depending on the information available to the agent. If
|
||||
inconsistentName or inconsistentValue is returned, the row
|
||||
remains in state A.
|
||||
|
||||
(5) depending on the MIB definition for the column/table,
|
||||
either noError or inconsistentValue may be returned.
|
||||
|
||||
(6) the return value can indicate one of the following
|
||||
errors:
|
||||
|
||||
wrongValue: because the agent does not support
|
||||
notInService (e.g., an agent which does not support
|
||||
createAndWait), or
|
||||
|
||||
inconsistentValue: because the agent is unable to take
|
||||
the row out of service at this time, perhaps because it
|
||||
is in use and cannot be de-activated.
|
||||
|
||||
(7) the return value can indicate the following error:
|
||||
|
||||
inconsistentValue: because the agent is unable to
|
||||
remove the row at this time, perhaps because it is in
|
||||
use and cannot be de-activated.
|
||||
|
||||
(8) the transition to D can fail, e.g., if the values of the
|
||||
conceptual row are inconsistent, then the error code would
|
||||
be inconsistentValue.
|
||||
|
||||
NOTE: Other processing of (this and other varbinds of) the
|
||||
set request may result in a response other than noError
|
||||
being returned, e.g., wrongValue, noCreation, etc.
|
||||
|
||||
Conceptual Row Creation
|
||||
|
||||
There are four potential interactions when creating a
|
||||
conceptual row: selecting an instance-identifier which is
|
||||
not in use; creating the conceptual row; initializing any
|
||||
objects for which the agent does not supply a default; and,
|
||||
making the conceptual row available for use by the managed
|
||||
device.
|
||||
|
||||
Interaction 1: Selecting an Instance-Identifier
|
||||
|
||||
The algorithm used to select an instance-identifier varies
|
||||
for each conceptual row. In some cases, the instance-
|
||||
identifier is semantically significant, e.g., the
|
||||
destination address of a route, and a management station
|
||||
selects the instance-identifier according to the semantics.
|
||||
|
||||
In other cases, the instance-identifier is used solely to
|
||||
distinguish conceptual rows, and a management station
|
||||
without specific knowledge of the conceptual row might
|
||||
examine the instances present in order to determine an
|
||||
unused instance-identifier. (This approach may be used, but
|
||||
it is often highly sub-optimal; however, it is also a
|
||||
questionable practice for a naive management station to
|
||||
attempt conceptual row creation.)
|
||||
|
||||
Alternately, the MIB module which defines the conceptual row
|
||||
might provide one or more objects which provide assistance
|
||||
in determining an unused instance-identifier. For example,
|
||||
if the conceptual row is indexed by an integer-value, then
|
||||
an object having an integer-valued SYNTAX clause might be
|
||||
defined for such a purpose, allowing a management station to
|
||||
issue a management protocol retrieval operation. In order
|
||||
to avoid unnecessary collisions between competing management
|
||||
stations, `adjacent' retrievals of this object should be
|
||||
different.
|
||||
|
||||
Finally, the management station could select a pseudo-random
|
||||
number to use as the index. In the event that this index
|
||||
|
||||
was already in use and an inconsistentValue was returned in
|
||||
response to the management protocol set operation, the
|
||||
management station should simply select a new pseudo-random
|
||||
number and retry the operation.
|
||||
|
||||
A MIB designer should choose between the two latter
|
||||
algorithms based on the size of the table (and therefore the
|
||||
efficiency of each algorithm). For tables in which a large
|
||||
number of entries are expected, it is recommended that a MIB
|
||||
object be defined that returns an acceptable index for
|
||||
creation. For tables with small numbers of entries, it is
|
||||
recommended that the latter pseudo-random index mechanism be
|
||||
used.
|
||||
|
||||
Interaction 2: Creating the Conceptual Row
|
||||
|
||||
Once an unused instance-identifier has been selected, the
|
||||
management station determines if it wishes to create and
|
||||
activate the conceptual row in one transaction or in a
|
||||
negotiated set of interactions.
|
||||
|
||||
Interaction 2a: Creating and Activating the Conceptual Row
|
||||
|
||||
The management station must first determine the column
|
||||
requirements, i.e., it must determine those columns for
|
||||
which it must or must not provide values. Depending on the
|
||||
complexity of the table and the management station's
|
||||
knowledge of the agent's capabilities, this determination
|
||||
can be made locally by the management station. Alternately,
|
||||
the management station issues a management protocol get
|
||||
operation to examine all columns in the conceptual row that
|
||||
it wishes to create. In response, for each column, there
|
||||
are three possible outcomes:
|
||||
|
||||
- a value is returned, indicating that some other
|
||||
management station has already created this conceptual
|
||||
row. We return to interaction 1.
|
||||
|
||||
- the exception `noSuchInstance' is returned,
|
||||
indicating that the agent implements the object-type
|
||||
associated with this column, and that this column in at
|
||||
least one conceptual row would be accessible in the MIB
|
||||
view used by the retrieval were it to exist. For those
|
||||
columns to which the agent provides read-create access,
|
||||
the `noSuchInstance' exception tells the management
|
||||
station that it should supply a value for this column
|
||||
when the conceptual row is to be created.
|
||||
|
||||
- the exception `noSuchObject' is returned, indicating
|
||||
that the agent does not implement the object-type
|
||||
associated with this column or that there is no
|
||||
conceptual row for which this column would be
|
||||
accessible in the MIB view used by the retrieval. As
|
||||
such, the management station can not issue any
|
||||
management protocol set operations to create an
|
||||
instance of this column.
|
||||
|
||||
Once the column requirements have been determined, a
|
||||
management protocol set operation is accordingly issued.
|
||||
This operation also sets the new instance of the status
|
||||
column to `createAndGo'.
|
||||
|
||||
When the agent processes the set operation, it verifies that
|
||||
it has sufficient information to make the conceptual row
|
||||
available for use by the managed device. The information
|
||||
available to the agent is provided by two sources: the
|
||||
management protocol set operation which creates the
|
||||
conceptual row, and, implementation-specific defaults
|
||||
supplied by the agent (note that an agent must provide
|
||||
implementation-specific defaults for at least those objects
|
||||
which it implements as read-only). If there is sufficient
|
||||
information available, then the conceptual row is created, a
|
||||
`noError' response is returned, the status column is set to
|
||||
`active', and no further interactions are necessary (i.e.,
|
||||
interactions 3 and 4 are skipped). If there is insufficient
|
||||
information, then the conceptual row is not created, and the
|
||||
set operation fails with an error of `inconsistentValue'.
|
||||
On this error, the management station can issue a management
|
||||
protocol retrieval operation to determine if this was
|
||||
because it failed to specify a value for a required column,
|
||||
or, because the selected instance of the status column
|
||||
already existed. In the latter case, we return to
|
||||
interaction 1. In the former case, the management station
|
||||
can re-issue the set operation with the additional
|
||||
information, or begin interaction 2 again using
|
||||
`createAndWait' in order to negotiate creation of the
|
||||
conceptual row.
|
||||
|
||||
NOTE WELL
|
||||
|
||||
Regardless of the method used to determine the column
|
||||
requirements, it is possible that the management
|
||||
station might deem a column necessary when, in fact,
|
||||
the agent will not allow that particular columnar
|
||||
instance to be created or written. In this case, the
|
||||
management protocol set operation will fail with an
|
||||
error such as `noCreation' or `notWritable'. In this
|
||||
case, the management station decides whether it needs
|
||||
to be able to set a value for that particular columnar
|
||||
instance. If not, the management station re-issues the
|
||||
management protocol set operation, but without setting
|
||||
a value for that particular columnar instance;
|
||||
otherwise, the management station aborts the row
|
||||
creation algorithm.
|
||||
|
||||
Interaction 2b: Negotiating the Creation of the Conceptual
|
||||
Row
|
||||
|
||||
The management station issues a management protocol set
|
||||
operation which sets the desired instance of the status
|
||||
column to `createAndWait'. If the agent is unwilling to
|
||||
process a request of this sort, the set operation fails with
|
||||
an error of `wrongValue'. (As a consequence, such an agent
|
||||
must be prepared to accept a single management protocol set
|
||||
operation, i.e., interaction 2a above, containing all of the
|
||||
columns indicated by its column requirements.) Otherwise,
|
||||
the conceptual row is created, a `noError' response is
|
||||
returned, and the status column is immediately set to either
|
||||
`notInService' or `notReady', depending on whether it has
|
||||
sufficient information to (attempt to) make the conceptual
|
||||
row available for use by the managed device. If there is
|
||||
sufficient information available, then the status column is
|
||||
set to `notInService'; otherwise, if there is insufficient
|
||||
information, then the status column is set to `notReady'.
|
||||
Regardless, we proceed to interaction 3.
|
||||
|
||||
Interaction 3: Initializing non-defaulted Objects
|
||||
|
||||
The management station must now determine the column
|
||||
requirements. It issues a management protocol get operation
|
||||
to examine all columns in the created conceptual row. In
|
||||
the response, for each column, there are three possible
|
||||
outcomes:
|
||||
|
||||
- a value is returned, indicating that the agent
|
||||
implements the object-type associated with this column
|
||||
and had sufficient information to provide a value. For
|
||||
those columns to which the agent provides read-create
|
||||
access (and for which the agent allows their values to
|
||||
be changed after their creation), a value return tells
|
||||
the management station that it may issue additional
|
||||
management protocol set operations, if it desires, in
|
||||
order to change the value associated with this column.
|
||||
|
||||
- the exception `noSuchInstance' is returned,
|
||||
indicating that the agent implements the object-type
|
||||
associated with this column, and that this column in at
|
||||
least one conceptual row would be accessible in the MIB
|
||||
view used by the retrieval were it to exist. However,
|
||||
the agent does not have sufficient information to
|
||||
provide a value, and until a value is provided, the
|
||||
conceptual row may not be made available for use by the
|
||||
managed device. For those columns to which the agent
|
||||
provides read-create access, the `noSuchInstance'
|
||||
exception tells the management station that it must
|
||||
issue additional management protocol set operations, in
|
||||
order to provide a value associated with this column.
|
||||
|
||||
- the exception `noSuchObject' is returned, indicating
|
||||
that the agent does not implement the object-type
|
||||
associated with this column or that there is no
|
||||
conceptual row for which this column would be
|
||||
accessible in the MIB view used by the retrieval. As
|
||||
such, the management station can not issue any
|
||||
management protocol set operations to create an
|
||||
instance of this column.
|
||||
|
||||
If the value associated with the status column is
|
||||
`notReady', then the management station must first deal with
|
||||
all `noSuchInstance' columns, if any. Having done so, the
|
||||
value of the status column becomes `notInService', and we
|
||||
proceed to interaction 4.
|
||||
|
||||
Interaction 4: Making the Conceptual Row Available
|
||||
|
||||
Once the management station is satisfied with the values
|
||||
associated with the columns of the conceptual row, it issues
|
||||
a management protocol set operation to set the status column
|
||||
to `active'. If the agent has sufficient information to
|
||||
make the conceptual row available for use by the managed
|
||||
device, the management protocol set operation succeeds (a
|
||||
`noError' response is returned). Otherwise, the management
|
||||
protocol set operation fails with an error of
|
||||
`inconsistentValue'.
|
||||
|
||||
NOTE WELL
|
||||
|
||||
A conceptual row having a status column with value
|
||||
`notInService' or `notReady' is unavailable to the
|
||||
managed device. As such, it is possible for the
|
||||
managed device to create its own instances during the
|
||||
time between the management protocol set operation
|
||||
which sets the status column to `createAndWait' and the
|
||||
management protocol set operation which sets the status
|
||||
column to `active'. In this case, when the management
|
||||
protocol set operation is issued to set the status
|
||||
column to `active', the values held in the agent
|
||||
supersede those used by the managed device.
|
||||
|
||||
If the management station is prevented from setting the
|
||||
status column to `active' (e.g., due to management station
|
||||
or network failure) the conceptual row will be left in the
|
||||
`notInService' or `notReady' state, consuming resources
|
||||
indefinitely. The agent must detect conceptual rows that
|
||||
have been in either state for an abnormally long period of
|
||||
time and remove them. It is the responsibility of the
|
||||
DESCRIPTION clause of the status column to indicate what an
|
||||
abnormally long period of time would be. This period of
|
||||
time should be long enough to allow for human response time
|
||||
(including `think time') between the creation of the
|
||||
conceptual row and the setting of the status to `active'.
|
||||
In the absence of such information in the DESCRIPTION
|
||||
clause, it is suggested that this period be approximately 5
|
||||
minutes in length. This removal action applies not only to
|
||||
newly-created rows, but also to previously active rows which
|
||||
are set to, and left in, the notInService state for a
|
||||
prolonged period exceeding that which is considered normal
|
||||
for such a conceptual row.
|
||||
|
||||
Conceptual Row Suspension
|
||||
|
||||
When a conceptual row is `active', the management station
|
||||
may issue a management protocol set operation which sets the
|
||||
instance of the status column to `notInService'. If the
|
||||
agent is unwilling to do so, the set operation fails with an
|
||||
error of `wrongValue' or `inconsistentValue'. Otherwise,
|
||||
the conceptual row is taken out of service, and a `noError'
|
||||
response is returned. It is the responsibility of the
|
||||
DESCRIPTION clause of the status column to indicate under
|
||||
what circumstances the status column should be taken out of
|
||||
service (e.g., in order for the value of some other column
|
||||
of the same conceptual row to be modified).
|
||||
|
||||
Conceptual Row Deletion
|
||||
|
||||
For deletion of conceptual rows, a management protocol set
|
||||
operation is issued which sets the instance of the status
|
||||
column to `destroy'. This request may be made regardless of
|
||||
the current value of the status column (e.g., it is possible
|
||||
to delete conceptual rows which are either `notReady',
|
||||
`notInService' or `active'.) If the operation succeeds,
|
||||
then all instances associated with the conceptual row are
|
||||
immediately removed."
|
||||
SYNTAX INTEGER {
|
||||
-- the following two values are states:
|
||||
-- these values may be read or written
|
||||
active(1),
|
||||
notInService(2),
|
||||
-- the following value is a state:
|
||||
-- this value may be read, but not written
|
||||
notReady(3),
|
||||
-- the following three values are
|
||||
-- actions: these values may be written,
|
||||
-- but are never read
|
||||
createAndGo(4),
|
||||
createAndWait(5),
|
||||
destroy(6)
|
||||
}
|
||||
|
||||
TimeStamp ::= TEXTUAL-CONVENTION
|
||||
STATUS current
|
||||
DESCRIPTION
|
||||
"The value of the sysUpTime object at which a specific
|
||||
occurrence happened. The specific occurrence must be
|
||||
|
||||
defined in the description of any object defined using this
|
||||
type.
|
||||
|
||||
If sysUpTime is reset to zero as a result of a re-
|
||||
initialization of the network management (sub)system, then
|
||||
the values of all TimeStamp objects are also reset.
|
||||
However, after approximately 497 days without a re-
|
||||
initialization, the sysUpTime object will reach 2^^32-1 and
|
||||
then increment around to zero; in this case, existing values
|
||||
of TimeStamp objects do not change. This can lead to
|
||||
ambiguities in the value of TimeStamp objects."
|
||||
SYNTAX TimeTicks
|
||||
|
||||
TimeInterval ::= TEXTUAL-CONVENTION
|
||||
STATUS current
|
||||
DESCRIPTION
|
||||
"A period of time, measured in units of 0.01 seconds."
|
||||
SYNTAX INTEGER (0..2147483647)
|
||||
|
||||
DateAndTime ::= TEXTUAL-CONVENTION
|
||||
DISPLAY-HINT "2d-1d-1d,1d:1d:1d.1d,1a1d:1d"
|
||||
STATUS current
|
||||
DESCRIPTION
|
||||
"A date-time specification.
|
||||
|
||||
field octets contents range
|
||||
----- ------ -------- -----
|
||||
1 1-2 year* 0..65536
|
||||
2 3 month 1..12
|
||||
3 4 day 1..31
|
||||
4 5 hour 0..23
|
||||
5 6 minutes 0..59
|
||||
6 7 seconds 0..60
|
||||
(use 60 for leap-second)
|
||||
7 8 deci-seconds 0..9
|
||||
8 9 direction from UTC '+' / '-'
|
||||
9 10 hours from UTC* 0..13
|
||||
10 11 minutes from UTC 0..59
|
||||
|
||||
* Notes:
|
||||
- the value of year is in network-byte order
|
||||
- daylight saving time in New Zealand is +13
|
||||
|
||||
For example, Tuesday May 26, 1992 at 1:30:15 PM EDT would be
|
||||
displayed as:
|
||||
|
||||
1992-5-26,13:30:15.0,-4:0
|
||||
|
||||
Note that if only local time is known, then timezone
|
||||
information (fields 8-10) is not present."
|
||||
SYNTAX OCTET STRING (SIZE (8 | 11))
|
||||
|
||||
StorageType ::= TEXTUAL-CONVENTION
|
||||
STATUS current
|
||||
DESCRIPTION
|
||||
"Describes the memory realization of a conceptual row. A
|
||||
row which is volatile(2) is lost upon reboot. A row which
|
||||
is either nonVolatile(3), permanent(4) or readOnly(5), is
|
||||
backed up by stable storage. A row which is permanent(4)
|
||||
can be changed but not deleted. A row which is readOnly(5)
|
||||
cannot be changed nor deleted.
|
||||
|
||||
If the value of an object with this syntax is either
|
||||
permanent(4) or readOnly(5), it cannot be written.
|
||||
Conversely, if the value is either other(1), volatile(2) or
|
||||
nonVolatile(3), it cannot be modified to be permanent(4) or
|
||||
readOnly(5). (All illegal modifications result in a
|
||||
'wrongValue' error.)
|
||||
|
||||
Every usage of this textual convention is required to
|
||||
specify the columnar objects which a permanent(4) row must
|
||||
at a minimum allow to be writable."
|
||||
SYNTAX INTEGER {
|
||||
other(1), -- eh?
|
||||
volatile(2), -- e.g., in RAM
|
||||
nonVolatile(3), -- e.g., in NVRAM
|
||||
permanent(4), -- e.g., partially in ROM
|
||||
readOnly(5) -- e.g., completely in ROM
|
||||
}
|
||||
|
||||
TDomain ::= TEXTUAL-CONVENTION
|
||||
STATUS current
|
||||
DESCRIPTION
|
||||
"Denotes a kind of transport service.
|
||||
|
||||
Some possible values, such as snmpUDPDomain, are defined in
|
||||
the SNMPv2-TM MIB module. Other possible values are defined
|
||||
in other MIB modules."
|
||||
REFERENCE "The SNMPv2-TM MIB module is defined in RFC 1906."
|
||||
SYNTAX OBJECT IDENTIFIER
|
||||
|
||||
TAddress ::= TEXTUAL-CONVENTION
|
||||
STATUS current
|
||||
DESCRIPTION
|
||||
"Denotes a transport service address.
|
||||
|
||||
A TAddress value is always interpreted within the context of a
|
||||
TDomain value. Thus, each definition of a TDomain value must
|
||||
be accompanied by a definition of a textual convention for use
|
||||
with that TDomain. Some possible textual conventions, such as
|
||||
SnmpUDPAddress for snmpUDPDomain, are defined in the SNMPv2-TM
|
||||
MIB module. Other possible textual conventions are defined in
|
||||
other MIB modules."
|
||||
REFERENCE "The SNMPv2-TM MIB module is defined in RFC 1906."
|
||||
SYNTAX OCTET STRING (SIZE (1..255))
|
||||
|
||||
END
|
||||
File diff suppressed because it is too large
Load Diff
File diff suppressed because it is too large
Load Diff
@@ -1,951 +0,0 @@
|
||||
--
|
||||
-- This MIB document has been modified to avoid a name conflict
|
||||
-- with the standard version (RFC 2932) of this MIB. All occurances
|
||||
-- of ipMRoute have been changed to ipMRoute1. This will not have
|
||||
-- any impact on users. M. Davison, July, 2001.
|
||||
--
|
||||
IPMROUTE-MIB DEFINITIONS ::= BEGIN
|
||||
|
||||
IMPORTS
|
||||
-- NOTE TO RFC EDITOR: When this document is published as
|
||||
-- an RFC, change 'experimental' to 'mib-2' in the
|
||||
-- following import, and delete this comment
|
||||
MODULE-IDENTITY, OBJECT-TYPE, experimental,
|
||||
Integer32, Counter32, Counter64, Gauge32,
|
||||
IpAddress, TimeTicks FROM SNMPv2-SMI
|
||||
RowStatus, TEXTUAL-CONVENTION,
|
||||
TruthValue, DisplayString FROM SNMPv2-TC
|
||||
MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF
|
||||
SnmpAdminString FROM SNMP-FRAMEWORK-MIB
|
||||
InterfaceIndexOrZero,
|
||||
InterfaceIndex FROM IF-MIB;
|
||||
|
||||
ipMRoute1MIB MODULE-IDENTITY
|
||||
LAST-UPDATED "9907221200Z" -- July 22, 1999
|
||||
ORGANIZATION "IETF IDMR Working Group"
|
||||
CONTACT-INFO
|
||||
" Dave Thaler
|
||||
Microsoft Corporation
|
||||
One Microsoft Way
|
||||
Redmond, WA 98052-6399
|
||||
US
|
||||
|
||||
Phone: +1 425 703 8835
|
||||
EMail: dthaler@dthaler.microsoft.com"
|
||||
DESCRIPTION
|
||||
"The MIB module for management of IP Multicast routing, but
|
||||
independent of the specific multicast routing protocol in
|
||||
use."
|
||||
REVISION "9907221200Z" -- July 22, 1999
|
||||
DESCRIPTION
|
||||
"Initial version, published as RFC xxxx (to be filled in by
|
||||
RFC-Editor)."
|
||||
::= { experimental 60 }
|
||||
-- NOTE TO RFC EDITOR: When this document is published as
|
||||
-- an RFC, change '{ experimental 60 }' to '{ mib-2 XX }'
|
||||
-- where XX is assigned by IANA, and delete this comment.
|
||||
|
||||
-- Textual Conventions
|
||||
|
||||
|
||||
IpMRoute1Protocol ::= TEXTUAL-CONVENTION
|
||||
STATUS current
|
||||
DESCRIPTION
|
||||
"The multicast routing protocol. Inclusion of values for
|
||||
multicast routing protocols is not intended to imply that
|
||||
those protocols need be supported."
|
||||
SYNTAX INTEGER {
|
||||
other(1), -- none of the following
|
||||
local(2), -- e.g., manually configured
|
||||
netmgmt(3), -- set via net.mgmt protocol
|
||||
dvmrp(4),
|
||||
mospf(5),
|
||||
pimSparseDense(6), -- PIMv1, both DM and SM
|
||||
cbt(7),
|
||||
pimSparseMode(8), -- PIM-SM
|
||||
pimDenseMode(9), -- PIM-DM
|
||||
igmpOnly(10),
|
||||
bgmp(11),
|
||||
msdp(12)
|
||||
}
|
||||
|
||||
-- Top-level structure of the MIB
|
||||
|
||||
ipMRoute1MIBObjects OBJECT IDENTIFIER ::= { ipMRoute1MIB 1 }
|
||||
|
||||
ipMRoute1 OBJECT IDENTIFIER ::= { ipMRoute1MIBObjects 1 }
|
||||
|
||||
|
||||
-- the IP Multicast Routing MIB-Group
|
||||
--
|
||||
-- a collection of objects providing information about
|
||||
-- IP Multicast Groups
|
||||
|
||||
ipMRoute1Enable OBJECT-TYPE
|
||||
SYNTAX INTEGER { enabled(1), disabled(2) }
|
||||
MAX-ACCESS read-only
|
||||
STATUS current
|
||||
DESCRIPTION
|
||||
"The enabled status of IP Multicast routing on this router."
|
||||
::= { ipMRoute1 1 }
|
||||
|
||||
ipMRoute1EntryCount OBJECT-TYPE
|
||||
SYNTAX Gauge32
|
||||
MAX-ACCESS read-only
|
||||
STATUS current
|
||||
DESCRIPTION
|
||||
"The number of rows in the ipMRoute1Table. This can be used
|
||||
to monitor the multicast routing table size."
|
||||
::= { ipMRoute1 7 }
|
||||
|
||||
ipMRoute1Table OBJECT-TYPE
|
||||
SYNTAX SEQUENCE OF IpMRoute1Entry
|
||||
MAX-ACCESS not-accessible
|
||||
STATUS current
|
||||
DESCRIPTION
|
||||
"The (conceptual) table containing multicast routing
|
||||
information for IP datagrams sent by particular sources to
|
||||
the IP multicast groups known to this router."
|
||||
|
||||
|
||||
::= { ipMRoute1 2 }
|
||||
|
||||
|
||||
ipMRoute1Entry OBJECT-TYPE
|
||||
SYNTAX IpMRoute1Entry
|
||||
MAX-ACCESS not-accessible
|
||||
STATUS current
|
||||
DESCRIPTION
|
||||
"An entry (conceptual row) containing the multicast routing
|
||||
information for IP datagrams from a particular source and
|
||||
addressed to a particular IP multicast group address.
|
||||
Discontinuities in counters in this entry can be detected by
|
||||
observing the value of ipMRoute1UpTime."
|
||||
INDEX { ipMRoute1Group,
|
||||
ipMRoute1Source,
|
||||
ipMRoute1SourceMask }
|
||||
::= { ipMRoute1Table 1 }
|
||||
|
||||
IpMRoute1Entry ::= SEQUENCE {
|
||||
ipMRoute1Group IpAddress,
|
||||
ipMRoute1Source IpAddress,
|
||||
ipMRoute1SourceMask IpAddress,
|
||||
ipMRoute1UpstreamNeighbor IpAddress,
|
||||
ipMRoute1InIfIndex InterfaceIndexOrZero,
|
||||
ipMRoute1UpTime TimeTicks,
|
||||
ipMRoute1ExpiryTime TimeTicks,
|
||||
ipMRoute1Pkts Counter32,
|
||||
ipMRoute1DifferentInIfPackets Counter32,
|
||||
ipMRoute1Octets Counter32,
|
||||
ipMRoute1Protocol IpMRoute1Protocol,
|
||||
ipMRoute1RtProto INTEGER,
|
||||
ipMRoute1RtAddress IpAddress,
|
||||
ipMRoute1RtMask IpAddress,
|
||||
ipMRoute1RtType INTEGER,
|
||||
ipMRoute1HCOctets Counter64
|
||||
}
|
||||
|
||||
ipMRoute1Group OBJECT-TYPE
|
||||
SYNTAX IpAddress
|
||||
MAX-ACCESS not-accessible
|
||||
STATUS current
|
||||
DESCRIPTION
|
||||
"The IP multicast group address for which this entry
|
||||
contains multicast routing information."
|
||||
::= { ipMRoute1Entry 1 }
|
||||
|
||||
ipMRoute1Source OBJECT-TYPE
|
||||
SYNTAX IpAddress
|
||||
|
||||
|
||||
MAX-ACCESS not-accessible
|
||||
STATUS current
|
||||
DESCRIPTION
|
||||
"The network address which when combined with the
|
||||
corresponding value of ipMRoute1SourceMask identifies the
|
||||
sources for which this entry contains multicast routing
|
||||
information."
|
||||
::= { ipMRoute1Entry 2 }
|
||||
|
||||
ipMRoute1SourceMask OBJECT-TYPE
|
||||
SYNTAX IpAddress
|
||||
MAX-ACCESS not-accessible
|
||||
STATUS current
|
||||
DESCRIPTION
|
||||
"The network mask which when combined with the corresponding
|
||||
value of ipMRoute1Source identifies the sources for which
|
||||
this entry contains multicast routing information."
|
||||
::= { ipMRoute1Entry 3 }
|
||||
|
||||
ipMRoute1UpstreamNeighbor OBJECT-TYPE
|
||||
SYNTAX IpAddress
|
||||
MAX-ACCESS read-only
|
||||
STATUS current
|
||||
DESCRIPTION
|
||||
"The address of the upstream neighbor (e.g., RPF neighbor)
|
||||
from which IP datagrams from these sources to this multicast
|
||||
address are received, or 0.0.0.0 if the upstream neighbor is
|
||||
unknown (e.g., in CBT)."
|
||||
::= { ipMRoute1Entry 4 }
|
||||
|
||||
ipMRoute1InIfIndex OBJECT-TYPE
|
||||
SYNTAX InterfaceIndexOrZero
|
||||
MAX-ACCESS read-only
|
||||
STATUS current
|
||||
DESCRIPTION
|
||||
"The value of ifIndex for the interface on which IP
|
||||
datagrams sent by these sources to this multicast address
|
||||
are received. A value of 0 indicates that datagrams are not
|
||||
subject to an incoming interface check, but may be accepted
|
||||
on multiple interfaces (e.g., in CBT)."
|
||||
::= { ipMRoute1Entry 5 }
|
||||
|
||||
ipMRoute1UpTime OBJECT-TYPE
|
||||
SYNTAX TimeTicks
|
||||
MAX-ACCESS read-only
|
||||
|
||||
|
||||
STATUS current
|
||||
DESCRIPTION
|
||||
"The time since the multicast routing information
|
||||
represented by this entry was learned by the router."
|
||||
::= { ipMRoute1Entry 6 }
|
||||
|
||||
ipMRoute1ExpiryTime OBJECT-TYPE
|
||||
SYNTAX TimeTicks
|
||||
MAX-ACCESS read-only
|
||||
STATUS current
|
||||
DESCRIPTION
|
||||
"The minimum amount of time remaining before this entry will
|
||||
be aged out. The value 0 indicates that the entry is not
|
||||
subject to aging."
|
||||
::= { ipMRoute1Entry 7 }
|
||||
|
||||
ipMRoute1Pkts OBJECT-TYPE
|
||||
SYNTAX Counter32
|
||||
MAX-ACCESS read-only
|
||||
STATUS current
|
||||
DESCRIPTION
|
||||
"The number of packets which this router has received from
|
||||
these sources and addressed to this multicast group
|
||||
address."
|
||||
::= { ipMRoute1Entry 8 }
|
||||
|
||||
ipMRoute1DifferentInIfPackets OBJECT-TYPE
|
||||
SYNTAX Counter32
|
||||
MAX-ACCESS read-only
|
||||
STATUS current
|
||||
DESCRIPTION
|
||||
"The number of packets which this router has received from
|
||||
these sources and addressed to this multicast group address,
|
||||
which were dropped because they were not received on the
|
||||
interface indicated by ipMRoute1InIfIndex. Packets which are
|
||||
not subject to an incoming interface check (e.g., using CBT)
|
||||
are not counted."
|
||||
::= { ipMRoute1Entry 9 }
|
||||
|
||||
ipMRoute1Octets OBJECT-TYPE
|
||||
SYNTAX Counter32
|
||||
MAX-ACCESS read-only
|
||||
STATUS current
|
||||
DESCRIPTION
|
||||
"The number of octets contained in IP datagrams which were
|
||||
|
||||
|
||||
received from these sources and addressed to this multicast
|
||||
group address, and which were forwarded by this router."
|
||||
::= { ipMRoute1Entry 10 }
|
||||
|
||||
ipMRoute1Protocol OBJECT-TYPE
|
||||
SYNTAX IpMRoute1Protocol
|
||||
MAX-ACCESS read-only
|
||||
STATUS current
|
||||
DESCRIPTION
|
||||
"The multicast routing protocol via which this multicast
|
||||
forwarding entry was learned."
|
||||
::= { ipMRoute1Entry 11 }
|
||||
|
||||
ipMRoute1RtProto OBJECT-TYPE
|
||||
SYNTAX INTEGER {
|
||||
other (1), -- not specified
|
||||
local (2), -- local interface
|
||||
netmgmt (3), -- static route
|
||||
icmp (4), -- result of ICMP Redirect
|
||||
-- the following are all dynamic
|
||||
-- routing protocols
|
||||
egp (5), -- Exterior Gateway Protocol
|
||||
ggp (6), -- Gateway-Gateway Protocol
|
||||
hello (7), -- FuzzBall HelloSpeak
|
||||
rip (8), -- Berkeley RIP or RIP-II
|
||||
isIs (9), -- Dual IS-IS
|
||||
esIs (10), -- ISO 9542
|
||||
ciscoIgrp (11), -- Cisco IGRP
|
||||
bbnSpfIgp (12), -- BBN SPF IGP
|
||||
ospf (13), -- Open Shortest Path First
|
||||
bgp (14), -- Border Gateway Protocol
|
||||
idpr (15), -- InterDomain Policy Routing
|
||||
ciscoEigrp (16), -- Cisco EIGRP
|
||||
dvmrp (17) -- DVMRP
|
||||
}
|
||||
MAX-ACCESS read-only
|
||||
STATUS current
|
||||
DESCRIPTION
|
||||
"The routing mechanism via which the route used to find the
|
||||
upstream or parent interface for this multicast forwarding
|
||||
entry was learned. Inclusion of values for routing
|
||||
protocols is not intended to imply that those protocols need
|
||||
be supported."
|
||||
::= { ipMRoute1Entry 12 }
|
||||
|
||||
|
||||
ipMRoute1RtAddress OBJECT-TYPE
|
||||
SYNTAX IpAddress
|
||||
MAX-ACCESS read-only
|
||||
STATUS current
|
||||
DESCRIPTION
|
||||
"The address portion of the route used to find the upstream
|
||||
or parent interface for this multicast forwarding entry."
|
||||
::= { ipMRoute1Entry 13 }
|
||||
|
||||
ipMRoute1RtMask OBJECT-TYPE
|
||||
SYNTAX IpAddress
|
||||
MAX-ACCESS read-only
|
||||
STATUS current
|
||||
DESCRIPTION
|
||||
"The mask associated with the route used to find the upstream
|
||||
or parent interface for this multicast forwarding entry."
|
||||
::= { ipMRoute1Entry 14 }
|
||||
|
||||
ipMRoute1RtType OBJECT-TYPE
|
||||
SYNTAX INTEGER {
|
||||
unicast (1), -- Unicast route used in multicast RIB
|
||||
multicast (2) -- Multicast route
|
||||
}
|
||||
MAX-ACCESS read-only
|
||||
STATUS current
|
||||
DESCRIPTION
|
||||
"The reason the given route was placed in the (logical)
|
||||
multicast Routing Information Base (RIB). A value of
|
||||
unicast means that the route would normally be placed only
|
||||
in the unicast RIB, but was placed in the multicast RIB
|
||||
(instead or in addition) due to local configuration, such as
|
||||
when running PIM over RIP. A value of multicast means that
|
||||
the route was explicitly added to the multicast RIB by the
|
||||
routing protocol, such as DVMRP or Multiprotocol BGP."
|
||||
::= { ipMRoute1Entry 15 }
|
||||
|
||||
ipMRoute1HCOctets OBJECT-TYPE
|
||||
SYNTAX Counter64
|
||||
MAX-ACCESS read-only
|
||||
STATUS current
|
||||
DESCRIPTION
|
||||
"The number of octets contained in IP datagrams which were
|
||||
received from these sources and addressed to this multicast
|
||||
group address, and which were forwarded by this router.
|
||||
This object is a 64-bit version of ipMRoute1Octets."
|
||||
|
||||
|
||||
::= { ipMRoute1Entry 16 }
|
||||
|
||||
--
|
||||
-- The IP Multicast Routing Next Hop Table
|
||||
--
|
||||
|
||||
ipMRoute1NextHopTable OBJECT-TYPE
|
||||
SYNTAX SEQUENCE OF IpMRoute1NextHopEntry
|
||||
MAX-ACCESS not-accessible
|
||||
STATUS current
|
||||
DESCRIPTION
|
||||
"The (conceptual) table containing information on the next-
|
||||
hops on outgoing interfaces for routing IP multicast
|
||||
datagrams. Each entry is one of a list of next-hops on
|
||||
outgoing interfaces for particular sources sending to a
|
||||
particular multicast group address."
|
||||
|
||||
|
||||
::= { ipMRoute1 3 }
|
||||
|
||||
ipMRoute1NextHopEntry OBJECT-TYPE
|
||||
SYNTAX IpMRoute1NextHopEntry
|
||||
MAX-ACCESS not-accessible
|
||||
STATUS current
|
||||
DESCRIPTION
|
||||
"An entry (conceptual row) in the list of next-hops on
|
||||
outgoing interfaces to which IP multicast datagrams from
|
||||
particular sources to a IP multicast group address are
|
||||
routed. Discontinuities in counters in this entry can be
|
||||
detected by observing the value of ipMRoute1UpTime."
|
||||
INDEX { ipMRoute1NextHopGroup, ipMRoute1NextHopSource,
|
||||
ipMRoute1NextHopSourceMask, ipMRoute1NextHopIfIndex,
|
||||
ipMRoute1NextHopAddress }
|
||||
::= { ipMRoute1NextHopTable 1 }
|
||||
|
||||
|
||||
IpMRoute1NextHopEntry ::= SEQUENCE {
|
||||
ipMRoute1NextHopGroup IpAddress,
|
||||
ipMRoute1NextHopSource IpAddress,
|
||||
ipMRoute1NextHopSourceMask IpAddress,
|
||||
ipMRoute1NextHopIfIndex InterfaceIndex,
|
||||
ipMRoute1NextHopAddress IpAddress,
|
||||
ipMRoute1NextHopState INTEGER,
|
||||
ipMRoute1NextHopUpTime TimeTicks,
|
||||
ipMRoute1NextHopExpiryTime TimeTicks,
|
||||
ipMRoute1NextHopClosestMemberHops Integer32,
|
||||
ipMRoute1NextHopProtocol IpMRoute1Protocol,
|
||||
ipMRoute1NextHopPkts Counter32
|
||||
}
|
||||
|
||||
ipMRoute1NextHopGroup OBJECT-TYPE
|
||||
SYNTAX IpAddress
|
||||
MAX-ACCESS not-accessible
|
||||
STATUS current
|
||||
DESCRIPTION
|
||||
"The IP multicast group for which this entry specifies a
|
||||
next-hop on an outgoing interface."
|
||||
::= { ipMRoute1NextHopEntry 1 }
|
||||
|
||||
ipMRoute1NextHopSource OBJECT-TYPE
|
||||
SYNTAX IpAddress
|
||||
MAX-ACCESS not-accessible
|
||||
STATUS current
|
||||
DESCRIPTION
|
||||
"The network address which when combined with the
|
||||
corresponding value of ipMRoute1NextHopSourceMask identifies
|
||||
the sources for which this entry specifies a next-hop on an
|
||||
outgoing interface."
|
||||
::= { ipMRoute1NextHopEntry 2 }
|
||||
|
||||
ipMRoute1NextHopSourceMask OBJECT-TYPE
|
||||
SYNTAX IpAddress
|
||||
MAX-ACCESS not-accessible
|
||||
STATUS current
|
||||
DESCRIPTION
|
||||
"The network mask which when combined with the corresponding
|
||||
value of ipMRoute1NextHopSource identifies the sources for
|
||||
which this entry specifies a next-hop on an outgoing
|
||||
interface."
|
||||
::= { ipMRoute1NextHopEntry 3 }
|
||||
|
||||
|
||||
ipMRoute1NextHopIfIndex OBJECT-TYPE
|
||||
SYNTAX InterfaceIndex
|
||||
MAX-ACCESS not-accessible
|
||||
STATUS current
|
||||
DESCRIPTION
|
||||
"The ifIndex value of the interface for the outgoing
|
||||
interface for this next-hop."
|
||||
::= { ipMRoute1NextHopEntry 4 }
|
||||
|
||||
ipMRoute1NextHopAddress OBJECT-TYPE
|
||||
SYNTAX IpAddress
|
||||
MAX-ACCESS not-accessible
|
||||
STATUS current
|
||||
DESCRIPTION
|
||||
"The address of the next-hop specific to this entry. For
|
||||
most interfaces, this is identical to ipMRoute1NextHopGroup.
|
||||
NBMA interfaces, however, may have multiple next-hop
|
||||
addresses out a single outgoing interface."
|
||||
::= { ipMRoute1NextHopEntry 5 }
|
||||
|
||||
ipMRoute1NextHopState OBJECT-TYPE
|
||||
SYNTAX INTEGER { pruned(1), forwarding(2) }
|
||||
MAX-ACCESS read-only
|
||||
STATUS current
|
||||
DESCRIPTION
|
||||
"An indication of whether the outgoing interface and next-
|
||||
hop represented by this entry is currently being used to
|
||||
forward IP datagrams. The value 'forwarding' indicates it
|
||||
is currently being used; the value 'pruned' indicates it is
|
||||
not."
|
||||
::= { ipMRoute1NextHopEntry 6 }
|
||||
|
||||
ipMRoute1NextHopUpTime OBJECT-TYPE
|
||||
SYNTAX TimeTicks
|
||||
MAX-ACCESS read-only
|
||||
STATUS current
|
||||
DESCRIPTION
|
||||
"The time since the multicast routing information
|
||||
represented by this entry was learned by the router."
|
||||
::= { ipMRoute1NextHopEntry 7 }
|
||||
|
||||
ipMRoute1NextHopExpiryTime OBJECT-TYPE
|
||||
SYNTAX TimeTicks
|
||||
MAX-ACCESS read-only
|
||||
STATUS current
|
||||
|
||||
|
||||
DESCRIPTION
|
||||
"The minimum amount of time remaining before this entry will
|
||||
be aged out. If ipMRoute1NextHopState is pruned(1), the
|
||||
remaining time until the prune expires and the state reverts
|
||||
to forwarding(2). Otherwise, the remaining time until this
|
||||
entry is removed from the table. The time remaining may be
|
||||
copied from ipMRoute1ExpiryTime if the protocol in use for
|
||||
this entry dos not specify next-hop timers. The value 0
|
||||
indicates that the entry is not subject to aging."
|
||||
::= { ipMRoute1NextHopEntry 8 }
|
||||
|
||||
ipMRoute1NextHopClosestMemberHops OBJECT-TYPE
|
||||
SYNTAX Integer32
|
||||
MAX-ACCESS read-only
|
||||
STATUS current
|
||||
DESCRIPTION
|
||||
"The minimum number of hops between this router and any
|
||||
member of this IP multicast group reached via this next-hop
|
||||
on this outgoing interface. Any IP multicast datagrams for
|
||||
the group which have a TTL less than this number of hops
|
||||
will not be forwarded to this next-hop."
|
||||
::= { ipMRoute1NextHopEntry 9 }
|
||||
|
||||
ipMRoute1NextHopProtocol OBJECT-TYPE
|
||||
SYNTAX IpMRoute1Protocol
|
||||
MAX-ACCESS read-only
|
||||
STATUS current
|
||||
DESCRIPTION
|
||||
"The routing mechanism via which this next-hop was learned."
|
||||
::= { ipMRoute1NextHopEntry 10 }
|
||||
|
||||
ipMRoute1NextHopPkts OBJECT-TYPE
|
||||
SYNTAX Counter32
|
||||
MAX-ACCESS read-only
|
||||
STATUS current
|
||||
DESCRIPTION
|
||||
"The number of packets which have been forwarded using this
|
||||
route."
|
||||
::= { ipMRoute1NextHopEntry 11 }
|
||||
|
||||
|
||||
--
|
||||
-- The Multicast Routing Interface Table
|
||||
--
|
||||
|
||||
ipMRoute1InterfaceTable OBJECT-TYPE
|
||||
SYNTAX SEQUENCE OF IpMRoute1InterfaceEntry
|
||||
MAX-ACCESS not-accessible
|
||||
STATUS current
|
||||
DESCRIPTION
|
||||
"The (conceptual) table containg multicast routing
|
||||
information specific to interfaces."
|
||||
|
||||
|
||||
::= { ipMRoute1 4 }
|
||||
|
||||
ipMRoute1InterfaceEntry OBJECT-TYPE
|
||||
SYNTAX IpMRoute1InterfaceEntry
|
||||
MAX-ACCESS not-accessible
|
||||
STATUS current
|
||||
DESCRIPTION
|
||||
"An entry (conceptual row) containing the multicast routing
|
||||
information for a particular interface."
|
||||
INDEX { ipMRoute1InterfaceIfIndex }
|
||||
::= { ipMRoute1InterfaceTable 1 }
|
||||
|
||||
IpMRoute1InterfaceEntry ::= SEQUENCE {
|
||||
ipMRoute1InterfaceIfIndex InterfaceIndex,
|
||||
ipMRoute1InterfaceTtl Integer32,
|
||||
ipMRoute1InterfaceProtocol IpMRoute1Protocol,
|
||||
ipMRoute1InterfaceRateLimit Integer32,
|
||||
ipMRoute1InterfaceInMcastOctets Counter32,
|
||||
ipMRoute1InterfaceOutMcastOctets Counter32,
|
||||
ipMRoute1InterfaceHCInMcastOctets Counter64,
|
||||
ipMRoute1InterfaceHCOutMcastOctets Counter64
|
||||
}
|
||||
|
||||
ipMRoute1InterfaceIfIndex OBJECT-TYPE
|
||||
SYNTAX InterfaceIndex
|
||||
MAX-ACCESS not-accessible
|
||||
STATUS current
|
||||
DESCRIPTION
|
||||
"The ifIndex value of the interface for which this entry
|
||||
contains information."
|
||||
::= { ipMRoute1InterfaceEntry 1 }
|
||||
|
||||
ipMRoute1InterfaceTtl OBJECT-TYPE
|
||||
SYNTAX Integer32 (0..255)
|
||||
|
||||
|
||||
MAX-ACCESS read-only
|
||||
STATUS current
|
||||
DESCRIPTION
|
||||
"The datagram TTL threshold for the interface. Any IP
|
||||
multicast datagrams with a TTL less than this threshold will
|
||||
not be forwarded out the interface. The default value of 0
|
||||
means all multicast packets are forwarded out the
|
||||
interface."
|
||||
::= { ipMRoute1InterfaceEntry 2 }
|
||||
|
||||
ipMRoute1InterfaceProtocol OBJECT-TYPE
|
||||
SYNTAX IpMRoute1Protocol
|
||||
MAX-ACCESS read-only
|
||||
STATUS current
|
||||
DESCRIPTION
|
||||
"The routing protocol running on this interface."
|
||||
::= { ipMRoute1InterfaceEntry 3 }
|
||||
|
||||
ipMRoute1InterfaceRateLimit OBJECT-TYPE
|
||||
SYNTAX Integer32
|
||||
MAX-ACCESS read-only
|
||||
STATUS current
|
||||
DESCRIPTION
|
||||
"The rate-limit, in kilobits per second, of forwarded
|
||||
multicast traffic on the interface. A rate-limit of 0
|
||||
indicates that no rate limiting is done."
|
||||
DEFVAL { 0 }
|
||||
::= { ipMRoute1InterfaceEntry 4 }
|
||||
|
||||
ipMRoute1InterfaceInMcastOctets OBJECT-TYPE
|
||||
SYNTAX Counter32
|
||||
MAX-ACCESS read-only
|
||||
STATUS current
|
||||
DESCRIPTION
|
||||
"The number of octets of multicast packets that have arrived
|
||||
on the interface, including framing characters. This object
|
||||
is similar to ifInOctets in the Interfaces MIB, except that
|
||||
only multicast packets are counted."
|
||||
::= { ipMRoute1InterfaceEntry 5 }
|
||||
|
||||
ipMRoute1InterfaceOutMcastOctets OBJECT-TYPE
|
||||
SYNTAX Counter32
|
||||
MAX-ACCESS read-only
|
||||
STATUS current
|
||||
DESCRIPTION
|
||||
|
||||
|
||||
"The number of octets of multicast packets that have been
|
||||
sent on the interface."
|
||||
::= { ipMRoute1InterfaceEntry 6 }
|
||||
|
||||
ipMRoute1InterfaceHCInMcastOctets OBJECT-TYPE
|
||||
SYNTAX Counter64
|
||||
MAX-ACCESS read-only
|
||||
STATUS current
|
||||
DESCRIPTION
|
||||
"The number of octets of multicast packets that have arrived
|
||||
on the interface, including framing characters. This object
|
||||
is a 64-bit version of ipMRoute1InterfaceInMcastOctets. It
|
||||
is similar to ifHCInOctets in the Interfaces MIB, except
|
||||
that only multicast packets are counted."
|
||||
::= { ipMRoute1InterfaceEntry 7 }
|
||||
|
||||
ipMRoute1InterfaceHCOutMcastOctets OBJECT-TYPE
|
||||
SYNTAX Counter64
|
||||
MAX-ACCESS read-only
|
||||
STATUS current
|
||||
DESCRIPTION
|
||||
"The number of octets of multicast packets that have been
|
||||
sent on the interface. This object is a 64-bit version of
|
||||
ipMRoute1InterfaceOutMcastOctets."
|
||||
::= { ipMRoute1InterfaceEntry 8 }
|
||||
|
||||
|
||||
--
|
||||
-- The IP Multicast Scope Boundary Table
|
||||
--
|
||||
|
||||
ipMRoute1BoundaryTable OBJECT-TYPE
|
||||
SYNTAX SEQUENCE OF IpMRoute1BoundaryEntry
|
||||
MAX-ACCESS not-accessible
|
||||
STATUS current
|
||||
DESCRIPTION
|
||||
"The (conceptual) table listing the router's scoped
|
||||
multicast address boundaries."
|
||||
|
||||
|
||||
::= { ipMRoute1 5 }
|
||||
|
||||
ipMRoute1BoundaryEntry OBJECT-TYPE
|
||||
SYNTAX IpMRoute1BoundaryEntry
|
||||
MAX-ACCESS not-accessible
|
||||
STATUS current
|
||||
DESCRIPTION
|
||||
"An entry (conceptual row) in the ipMRoute1BoundaryTable
|
||||
representing a scoped boundary."
|
||||
INDEX { ipMRoute1BoundaryIfIndex, ipMRoute1BoundaryAddress,
|
||||
ipMRoute1BoundaryAddressMask }
|
||||
::= { ipMRoute1BoundaryTable 1 }
|
||||
|
||||
IpMRoute1BoundaryEntry ::= SEQUENCE {
|
||||
ipMRoute1BoundaryIfIndex InterfaceIndex,
|
||||
ipMRoute1BoundaryAddress IpAddress,
|
||||
ipMRoute1BoundaryAddressMask IpAddress,
|
||||
ipMRoute1BoundaryStatus RowStatus
|
||||
}
|
||||
|
||||
ipMRoute1BoundaryIfIndex OBJECT-TYPE
|
||||
SYNTAX InterfaceIndex
|
||||
MAX-ACCESS not-accessible
|
||||
STATUS current
|
||||
DESCRIPTION
|
||||
"The IfIndex value for the interface to which this boundary
|
||||
applies. Packets with a destination address in the
|
||||
associated address/mask range will not be forwarded out this
|
||||
interface."
|
||||
::= { ipMRoute1BoundaryEntry 1 }
|
||||
|
||||
ipMRoute1BoundaryAddress OBJECT-TYPE
|
||||
SYNTAX IpAddress
|
||||
MAX-ACCESS not-accessible
|
||||
|
||||
|
||||
STATUS current
|
||||
DESCRIPTION
|
||||
"The group address which when combined with the
|
||||
corresponding value of ipMRoute1BoundaryAddressMask
|
||||
identifies the group range for which the scoped boundary
|
||||
exists. Scoped addresses must come from the range 239.x.x.x
|
||||
as specified in RFC 2365."
|
||||
::= { ipMRoute1BoundaryEntry 2 }
|
||||
|
||||
ipMRoute1BoundaryAddressMask OBJECT-TYPE
|
||||
SYNTAX IpAddress
|
||||
MAX-ACCESS not-accessible
|
||||
STATUS current
|
||||
DESCRIPTION
|
||||
"The group address mask which when combined with the
|
||||
corresponding value of ipMRoute1BoundaryAddress identifies
|
||||
the group range for which the scoped boundary exists."
|
||||
::= { ipMRoute1BoundaryEntry 3 }
|
||||
|
||||
ipMRoute1BoundaryStatus OBJECT-TYPE
|
||||
SYNTAX RowStatus
|
||||
MAX-ACCESS read-only
|
||||
STATUS current
|
||||
DESCRIPTION
|
||||
"The status of this row, by which new entries may be
|
||||
created, or old entries deleted from this table."
|
||||
::= { ipMRoute1BoundaryEntry 4 }
|
||||
|
||||
--
|
||||
-- The IP Multicast Scope Name Table
|
||||
--
|
||||
|
||||
ipMRoute1ScopeNameTable OBJECT-TYPE
|
||||
SYNTAX SEQUENCE OF IpMRoute1ScopeNameEntry
|
||||
MAX-ACCESS not-accessible
|
||||
STATUS current
|
||||
DESCRIPTION
|
||||
"The (conceptual) table listing the multicast scope names."
|
||||
|
||||
|
||||
::= { ipMRoute1 6 }
|
||||
|
||||
ipMRoute1ScopeNameEntry OBJECT-TYPE
|
||||
SYNTAX IpMRoute1ScopeNameEntry
|
||||
MAX-ACCESS not-accessible
|
||||
STATUS current
|
||||
|
||||
|
||||
DESCRIPTION
|
||||
"An entry (conceptual row) in the ipMRoute1ScopeNameTable
|
||||
representing a multicast scope name."
|
||||
INDEX { ipMRoute1ScopeNameAddress,
|
||||
ipMRoute1ScopeNameAddressMask,
|
||||
IMPLIED ipMRoute1ScopeNameLanguage }
|
||||
::= { ipMRoute1ScopeNameTable 1 }
|
||||
|
||||
IpMRoute1ScopeNameEntry ::= SEQUENCE {
|
||||
ipMRoute1ScopeNameAddress IpAddress,
|
||||
ipMRoute1ScopeNameAddressMask IpAddress,
|
||||
ipMRoute1ScopeNameLanguage DisplayString,
|
||||
ipMRoute1ScopeNameString SnmpAdminString,
|
||||
ipMRoute1ScopeNameDefault TruthValue,
|
||||
ipMRoute1ScopeNameStatus RowStatus
|
||||
}
|
||||
|
||||
ipMRoute1ScopeNameAddress OBJECT-TYPE
|
||||
SYNTAX IpAddress
|
||||
MAX-ACCESS not-accessible
|
||||
STATUS current
|
||||
DESCRIPTION
|
||||
"The group address which when combined with the
|
||||
corresponding value of ipMRoute1ScopeNameAddressMask
|
||||
identifies the group range associated with the multicast
|
||||
scope. Scoped addresses must come from the range
|
||||
239.x.x.x."
|
||||
::= { ipMRoute1ScopeNameEntry 1 }
|
||||
|
||||
ipMRoute1ScopeNameAddressMask OBJECT-TYPE
|
||||
SYNTAX IpAddress
|
||||
MAX-ACCESS not-accessible
|
||||
STATUS current
|
||||
DESCRIPTION
|
||||
"The group address mask which when combined with the
|
||||
corresponding value of ipMRoute1ScopeNameAddress identifies
|
||||
the group range associated with the multicast scope."
|
||||
::= { ipMRoute1ScopeNameEntry 2 }
|
||||
|
||||
ipMRoute1ScopeNameLanguage OBJECT-TYPE
|
||||
SYNTAX DisplayString (SIZE (1..8))
|
||||
MAX-ACCESS not-accessible
|
||||
STATUS current
|
||||
DESCRIPTION
|
||||
"An RFC 1766-style language tag, with all alphabetic
|
||||
|
||||
|
||||
characters converted to lowercase. This restriction is
|
||||
intended to make the lexical ordering imposed by SNMP useful
|
||||
when applied to language tags. Note that it is
|
||||
theoretically possible for a valid language tag to exceed
|
||||
the allowed length of this object, and thus be impossible to
|
||||
represent in this table. Sampling of language tags in
|
||||
current use on the Internet suggests that this limit does
|
||||
not pose a serious problem in practice."
|
||||
::= { ipMRoute1ScopeNameEntry 3 }
|
||||
|
||||
ipMRoute1ScopeNameString OBJECT-TYPE
|
||||
SYNTAX SnmpAdminString
|
||||
MAX-ACCESS read-only
|
||||
STATUS current
|
||||
DESCRIPTION
|
||||
"The textual name associated with the multicast scope. The
|
||||
value of this object should be suitable for displaying to
|
||||
end-users, such as when allocating a multicast address in
|
||||
this scope. When no name is specified, the default value of
|
||||
this object should be the string 239.x.x.x/y with x and y
|
||||
replaced appropriately to describe the address and mask
|
||||
length associated with the scope."
|
||||
::= { ipMRoute1ScopeNameEntry 4 }
|
||||
|
||||
ipMRoute1ScopeNameDefault OBJECT-TYPE
|
||||
SYNTAX TruthValue
|
||||
MAX-ACCESS read-only
|
||||
STATUS current
|
||||
DESCRIPTION
|
||||
"If true, indicates a preference that the name in the
|
||||
following language should be used by applications if no name
|
||||
is available in a desired language."
|
||||
DEFVAL { false }
|
||||
::= { ipMRoute1ScopeNameEntry 5 }
|
||||
|
||||
ipMRoute1ScopeNameStatus OBJECT-TYPE
|
||||
SYNTAX RowStatus
|
||||
MAX-ACCESS read-only
|
||||
STATUS current
|
||||
DESCRIPTION
|
||||
"The status of this row, by which new entries may be
|
||||
created, or old entries deleted from this table."
|
||||
::= { ipMRoute1ScopeNameEntry 6 }
|
||||
|
||||
|
||||
-- conformance information
|
||||
|
||||
ipMRoute1MIBConformance
|
||||
OBJECT IDENTIFIER ::= { ipMRoute1MIB 2 }
|
||||
ipMRoute1MIBCompliances
|
||||
OBJECT IDENTIFIER ::= { ipMRoute1MIBConformance 1 }
|
||||
ipMRoute1MIBGroups OBJECT IDENTIFIER ::= { ipMRoute1MIBConformance 2 }
|
||||
|
||||
-- compliance statements
|
||||
|
||||
ipMRoute1MIBCompliance MODULE-COMPLIANCE
|
||||
STATUS current
|
||||
DESCRIPTION
|
||||
"The compliance statement for the IP Multicast MIB."
|
||||
MODULE -- this module
|
||||
MANDATORY-GROUPS { ipMRoute1MIBBasicGroup,
|
||||
ipMRoute1MIBRouteGroup}
|
||||
|
||||
GROUP ipMRoute1MIBBoundaryGroup
|
||||
DESCRIPTION
|
||||
"This group is mandatory if the router supports
|
||||
administratively-scoped multicast address boundaries."
|
||||
|
||||
OBJECT ipMRoute1BoundaryStatus
|
||||
MIN-ACCESS read-only
|
||||
DESCRIPTION
|
||||
"Write access is not required."
|
||||
|
||||
OBJECT ipMRoute1ScopeNameStatus
|
||||
MIN-ACCESS read-only
|
||||
DESCRIPTION
|
||||
"Write access is not required."
|
||||
|
||||
GROUP ipMRoute1MIBHCInterfaceGroup
|
||||
DESCRIPTION
|
||||
"This group is mandatory only for those network interfaces
|
||||
for which the value of the corresponding instance of ifSpeed
|
||||
is greater than 20,000,000 bits/second."
|
||||
|
||||
::= { ipMRoute1MIBCompliances 1 }
|
||||
|
||||
-- units of conformance
|
||||
|
||||
|
||||
ipMRoute1MIBBasicGroup OBJECT-GROUP
|
||||
OBJECTS { ipMRoute1Enable, ipMRoute1EntryCount,
|
||||
ipMRoute1UpstreamNeighbor, ipMRoute1InIfIndex,
|
||||
ipMRoute1UpTime, ipMRoute1ExpiryTime,
|
||||
ipMRoute1NextHopState,
|
||||
ipMRoute1NextHopUpTime,
|
||||
ipMRoute1NextHopExpiryTime,
|
||||
ipMRoute1NextHopProtocol,
|
||||
ipMRoute1NextHopPkts,
|
||||
ipMRoute1InterfaceTtl,
|
||||
ipMRoute1InterfaceProtocol, ipMRoute1InterfaceRateLimit,
|
||||
ipMRoute1InterfaceInMcastOctets,
|
||||
ipMRoute1InterfaceOutMcastOctets,
|
||||
ipMRoute1Protocol
|
||||
}
|
||||
STATUS current
|
||||
DESCRIPTION
|
||||
"A collection of objects to support basic management of IP
|
||||
Multicast routing."
|
||||
::= { ipMRoute1MIBGroups 1 }
|
||||
|
||||
ipMRoute1MIBHopCountGroup OBJECT-GROUP
|
||||
OBJECTS { ipMRoute1NextHopClosestMemberHops }
|
||||
STATUS current
|
||||
DESCRIPTION
|
||||
"A collection of objects to support management of the use of
|
||||
hop counts in IP Multicast routing."
|
||||
::= { ipMRoute1MIBGroups 2 }
|
||||
|
||||
ipMRoute1MIBBoundaryGroup OBJECT-GROUP
|
||||
OBJECTS { ipMRoute1BoundaryStatus, ipMRoute1ScopeNameString,
|
||||
ipMRoute1ScopeNameDefault, ipMRoute1ScopeNameStatus }
|
||||
STATUS current
|
||||
DESCRIPTION
|
||||
"A collection of objects to support management of scoped
|
||||
multicast address boundaries."
|
||||
::= { ipMRoute1MIBGroups 3 }
|
||||
|
||||
ipMRoute1MIBPktsOutGroup OBJECT-GROUP
|
||||
OBJECTS { ipMRoute1NextHopPkts }
|
||||
STATUS current
|
||||
DESCRIPTION
|
||||
"A collection of objects to support management of packet
|
||||
counters for each outgoing interface entry of a route."
|
||||
::= { ipMRoute1MIBGroups 4 }
|
||||
|
||||
|
||||
ipMRoute1MIBHCInterfaceGroup OBJECT-GROUP
|
||||
OBJECTS { ipMRoute1InterfaceHCInMcastOctets,
|
||||
ipMRoute1InterfaceHCOutMcastOctets,
|
||||
ipMRoute1HCOctets }
|
||||
STATUS current
|
||||
DESCRIPTION
|
||||
"A collection of objects providing information specific to
|
||||
high speed (greater than 20,000,000 bits/second) network
|
||||
interfaces."
|
||||
::= { ipMRoute1MIBGroups 5 }
|
||||
|
||||
ipMRoute1MIBRouteGroup OBJECT-GROUP
|
||||
OBJECTS { ipMRoute1RtProto, ipMRoute1RtAddress,
|
||||
ipMRoute1RtMask, ipMRoute1RtType }
|
||||
STATUS current
|
||||
DESCRIPTION
|
||||
"A collection of objects providing information on the
|
||||
relationship between multicast routing information, and the
|
||||
IP Forwarding Table."
|
||||
::= { ipMRoute1MIBGroups 6 }
|
||||
|
||||
ipMRoute1MIBPktsGroup OBJECT-GROUP
|
||||
OBJECTS { ipMRoute1Pkts, ipMRoute1DifferentInIfPackets,
|
||||
ipMRoute1Octets }
|
||||
STATUS current
|
||||
DESCRIPTION
|
||||
"A collection of objects to support management of packet
|
||||
counters for each forwarding entry."
|
||||
::= { ipMRoute1MIBGroups 7 }
|
||||
|
||||
END
|
||||
File diff suppressed because it is too large
Load Diff
File diff suppressed because it is too large
Load Diff
File diff suppressed because it is too large
Load Diff
File diff suppressed because it is too large
Load Diff
File diff suppressed because it is too large
Load Diff
File diff suppressed because it is too large
Load Diff
File diff suppressed because it is too large
Load Diff
File diff suppressed because it is too large
Load Diff
@@ -1,876 +0,0 @@
|
||||
--
|
||||
-- All read-write/read-create objects have been changed to read-only
|
||||
-- since this implmentation does not support write/create access.
|
||||
-- M. Davison, Juniper.
|
||||
--
|
||||
IPMROUTE-STD-MIB DEFINITIONS ::= BEGIN
|
||||
|
||||
IMPORTS
|
||||
MODULE-IDENTITY, OBJECT-TYPE, mib-2,
|
||||
Integer32, Counter32, Counter64, Gauge32,
|
||||
IpAddress, TimeTicks FROM SNMPv2-SMI
|
||||
RowStatus, TEXTUAL-CONVENTION,
|
||||
TruthValue FROM SNMPv2-TC
|
||||
MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF
|
||||
SnmpAdminString FROM SNMP-FRAMEWORK-MIB
|
||||
InterfaceIndexOrZero,
|
||||
InterfaceIndex FROM IF-MIB
|
||||
IANAipRouteProtocol,
|
||||
IANAipMRouteProtocol FROM IANA-RTPROTO-MIB;
|
||||
|
||||
ipMRouteStdMIB MODULE-IDENTITY
|
||||
LAST-UPDATED "200009220000Z" -- September 22, 2000
|
||||
ORGANIZATION "IETF IDMR Working Group"
|
||||
CONTACT-INFO
|
||||
" Dave Thaler
|
||||
Microsoft Corporation
|
||||
One Microsoft Way
|
||||
Redmond, WA 98052-6399
|
||||
US
|
||||
|
||||
Phone: +1 425 703 8835
|
||||
EMail: dthaler@microsoft.com"
|
||||
DESCRIPTION
|
||||
"The MIB module for management of IP Multicast routing, but
|
||||
independent of the specific multicast routing protocol in
|
||||
use."
|
||||
REVISION "200009220000Z" -- September 22, 2000
|
||||
DESCRIPTION
|
||||
"Initial version, published as RFC 2932."
|
||||
::= { mib-2 83 }
|
||||
|
||||
-- Textual Conventions
|
||||
|
||||
LanguageTag ::= TEXTUAL-CONVENTION
|
||||
|
||||
DISPLAY-HINT "100a"
|
||||
STATUS current
|
||||
DESCRIPTION
|
||||
"An RFC 1766-style language tag, with all alphabetic
|
||||
characters converted to lowercase. This restriction is
|
||||
intended to make the lexical ordering imposed by SNMP useful
|
||||
when applied to language tags. Note that it is
|
||||
theoretically possible for a valid language tag to exceed
|
||||
the allowed length of this syntax, and thus be impossible to
|
||||
represent with this syntax. Sampling of language tags in
|
||||
current use on the Internet suggests that this limit does
|
||||
not pose a serious problem in practice."
|
||||
SYNTAX OCTET STRING (SIZE (1..100))
|
||||
|
||||
|
||||
-- Top-level structure of the MIB
|
||||
|
||||
ipMRouteMIBObjects OBJECT IDENTIFIER ::= { ipMRouteStdMIB 1 }
|
||||
|
||||
ipMRoute OBJECT IDENTIFIER ::= { ipMRouteMIBObjects 1 }
|
||||
|
||||
-- the IP Multicast Routing MIB-Group
|
||||
--
|
||||
-- a collection of objects providing information about
|
||||
-- IP Multicast Groups
|
||||
|
||||
|
||||
ipMRouteEnable OBJECT-TYPE
|
||||
SYNTAX INTEGER { enabled(1), disabled(2) }
|
||||
MAX-ACCESS read-write
|
||||
STATUS current
|
||||
DESCRIPTION
|
||||
"The enabled status of IP Multicast routing on this router."
|
||||
::= { ipMRoute 1 }
|
||||
|
||||
ipMRouteEntryCount OBJECT-TYPE
|
||||
SYNTAX Gauge32
|
||||
MAX-ACCESS read-only
|
||||
STATUS current
|
||||
DESCRIPTION
|
||||
"The number of rows in the ipMRouteTable. This can be used
|
||||
to monitor the multicast routing table size."
|
||||
::= { ipMRoute 7 }
|
||||
|
||||
ipMRouteTable OBJECT-TYPE
|
||||
SYNTAX SEQUENCE OF IpMRouteEntry
|
||||
MAX-ACCESS not-accessible
|
||||
STATUS current
|
||||
DESCRIPTION
|
||||
"The (conceptual) table containing multicast routing
|
||||
information for IP datagrams sent by particular sources to
|
||||
the IP multicast groups known to this router."
|
||||
::= { ipMRoute 2 }
|
||||
|
||||
ipMRouteEntry OBJECT-TYPE
|
||||
SYNTAX IpMRouteEntry
|
||||
MAX-ACCESS not-accessible
|
||||
STATUS current
|
||||
DESCRIPTION
|
||||
"An entry (conceptual row) containing the multicast routing
|
||||
information for IP datagrams from a particular source and
|
||||
addressed to a particular IP multicast group address.
|
||||
Discontinuities in counters in this entry can be detected by
|
||||
observing the value of ipMRouteUpTime."
|
||||
INDEX { ipMRouteGroup,
|
||||
ipMRouteSource,
|
||||
ipMRouteSourceMask }
|
||||
::= { ipMRouteTable 1 }
|
||||
|
||||
IpMRouteEntry ::= SEQUENCE {
|
||||
ipMRouteGroup IpAddress,
|
||||
ipMRouteSource IpAddress,
|
||||
ipMRouteSourceMask IpAddress,
|
||||
ipMRouteUpstreamNeighbor IpAddress,
|
||||
ipMRouteInIfIndex InterfaceIndexOrZero,
|
||||
ipMRouteUpTime TimeTicks,
|
||||
ipMRouteExpiryTime TimeTicks,
|
||||
ipMRoutePkts Counter32,
|
||||
ipMRouteDifferentInIfPackets Counter32,
|
||||
ipMRouteOctets Counter32,
|
||||
ipMRouteProtocol IANAipMRouteProtocol,
|
||||
ipMRouteRtProto IANAipRouteProtocol,
|
||||
ipMRouteRtAddress IpAddress,
|
||||
ipMRouteRtMask IpAddress,
|
||||
ipMRouteRtType INTEGER,
|
||||
ipMRouteHCOctets Counter64
|
||||
}
|
||||
|
||||
ipMRouteGroup OBJECT-TYPE
|
||||
SYNTAX IpAddress
|
||||
MAX-ACCESS not-accessible
|
||||
STATUS current
|
||||
DESCRIPTION
|
||||
"The IP multicast group address for which this entry
|
||||
contains multicast routing information."
|
||||
::= { ipMRouteEntry 1 }
|
||||
|
||||
ipMRouteSource OBJECT-TYPE
|
||||
SYNTAX IpAddress
|
||||
MAX-ACCESS not-accessible
|
||||
STATUS current
|
||||
DESCRIPTION
|
||||
"The network address which when combined with the
|
||||
corresponding value of ipMRouteSourceMask identifies the
|
||||
sources for which this entry contains multicast routing
|
||||
information."
|
||||
::= { ipMRouteEntry 2 }
|
||||
|
||||
ipMRouteSourceMask OBJECT-TYPE
|
||||
SYNTAX IpAddress
|
||||
MAX-ACCESS not-accessible
|
||||
STATUS current
|
||||
DESCRIPTION
|
||||
"The network mask which when combined with the corresponding
|
||||
value of ipMRouteSource identifies the sources for which
|
||||
this entry contains multicast routing information."
|
||||
::= { ipMRouteEntry 3 }
|
||||
|
||||
ipMRouteUpstreamNeighbor OBJECT-TYPE
|
||||
SYNTAX IpAddress
|
||||
MAX-ACCESS read-only
|
||||
STATUS current
|
||||
DESCRIPTION
|
||||
"The address of the upstream neighbor (e.g., RPF neighbor)
|
||||
from which IP datagrams from these sources to this multicast
|
||||
address are received, or 0.0.0.0 if the upstream neighbor is
|
||||
unknown (e.g., in CBT)."
|
||||
::= { ipMRouteEntry 4 }
|
||||
|
||||
ipMRouteInIfIndex OBJECT-TYPE
|
||||
SYNTAX InterfaceIndexOrZero
|
||||
MAX-ACCESS read-only
|
||||
STATUS current
|
||||
DESCRIPTION
|
||||
"The value of ifIndex for the interface on which IP
|
||||
datagrams sent by these sources to this multicast address
|
||||
are received. A value of 0 indicates that datagrams are not
|
||||
subject to an incoming interface check, but may be accepted
|
||||
on multiple interfaces (e.g., in CBT)."
|
||||
::= { ipMRouteEntry 5 }
|
||||
|
||||
ipMRouteUpTime OBJECT-TYPE
|
||||
SYNTAX TimeTicks
|
||||
MAX-ACCESS read-only
|
||||
STATUS current
|
||||
DESCRIPTION
|
||||
"The time since the multicast routing information
|
||||
represented by this entry was learned by the router."
|
||||
::= { ipMRouteEntry 6 }
|
||||
|
||||
ipMRouteExpiryTime OBJECT-TYPE
|
||||
SYNTAX TimeTicks
|
||||
MAX-ACCESS read-only
|
||||
STATUS current
|
||||
DESCRIPTION
|
||||
"The minimum amount of time remaining before this entry will
|
||||
be aged out. The value 0 indicates that the entry is not
|
||||
subject to aging."
|
||||
::= { ipMRouteEntry 7 }
|
||||
|
||||
ipMRoutePkts OBJECT-TYPE
|
||||
SYNTAX Counter32
|
||||
MAX-ACCESS read-only
|
||||
STATUS current
|
||||
DESCRIPTION
|
||||
"The number of packets which this router has received from
|
||||
these sources and addressed to this multicast group
|
||||
address."
|
||||
::= { ipMRouteEntry 8 }
|
||||
|
||||
ipMRouteDifferentInIfPackets OBJECT-TYPE
|
||||
SYNTAX Counter32
|
||||
MAX-ACCESS read-only
|
||||
STATUS current
|
||||
DESCRIPTION
|
||||
"The number of packets which this router has received from
|
||||
these sources and addressed to this multicast group address,
|
||||
which were dropped because they were not received on the
|
||||
interface indicated by ipMRouteInIfIndex. Packets which are
|
||||
not subject to an incoming interface check (e.g., using CBT)
|
||||
are not counted."
|
||||
::= { ipMRouteEntry 9 }
|
||||
|
||||
ipMRouteOctets OBJECT-TYPE
|
||||
SYNTAX Counter32
|
||||
MAX-ACCESS read-only
|
||||
STATUS current
|
||||
DESCRIPTION
|
||||
"The number of octets contained in IP datagrams which were
|
||||
received from these sources and addressed to this multicast
|
||||
group address, and which were forwarded by this router."
|
||||
::= { ipMRouteEntry 10 }
|
||||
|
||||
ipMRouteProtocol OBJECT-TYPE
|
||||
SYNTAX IANAipMRouteProtocol
|
||||
MAX-ACCESS read-only
|
||||
STATUS current
|
||||
DESCRIPTION
|
||||
"The multicast routing protocol via which this multicast
|
||||
forwarding entry was learned."
|
||||
::= { ipMRouteEntry 11 }
|
||||
|
||||
ipMRouteRtProto OBJECT-TYPE
|
||||
SYNTAX IANAipRouteProtocol
|
||||
MAX-ACCESS read-only
|
||||
STATUS current
|
||||
DESCRIPTION
|
||||
"The routing mechanism via which the route used to find the
|
||||
upstream or parent interface for this multicast forwarding
|
||||
entry was learned. Inclusion of values for routing
|
||||
protocols is not intended to imply that those protocols need
|
||||
be supported."
|
||||
::= { ipMRouteEntry 12 }
|
||||
|
||||
ipMRouteRtAddress OBJECT-TYPE
|
||||
SYNTAX IpAddress
|
||||
MAX-ACCESS read-only
|
||||
STATUS current
|
||||
DESCRIPTION
|
||||
"The address portion of the route used to find the upstream
|
||||
or parent interface for this multicast forwarding entry."
|
||||
::= { ipMRouteEntry 13 }
|
||||
|
||||
ipMRouteRtMask OBJECT-TYPE
|
||||
SYNTAX IpAddress
|
||||
MAX-ACCESS read-only
|
||||
STATUS current
|
||||
DESCRIPTION
|
||||
"The mask associated with the route used to find the upstream
|
||||
or parent interface for this multicast forwarding entry."
|
||||
::= { ipMRouteEntry 14 }
|
||||
|
||||
ipMRouteRtType OBJECT-TYPE
|
||||
SYNTAX INTEGER {
|
||||
unicast (1), -- Unicast route used in multicast RIB
|
||||
multicast (2) -- Multicast route
|
||||
}
|
||||
MAX-ACCESS read-only
|
||||
STATUS current
|
||||
DESCRIPTION
|
||||
"The reason the given route was placed in the (logical)
|
||||
multicast Routing Information Base (RIB). A value of
|
||||
unicast means that the route would normally be placed only
|
||||
in the unicast RIB, but was placed in the multicast RIB
|
||||
(instead or in addition) due to local configuration, such as
|
||||
when running PIM over RIP. A value of multicast means that
|
||||
the route was explicitly added to the multicast RIB by the
|
||||
routing protocol, such as DVMRP or Multiprotocol BGP."
|
||||
::= { ipMRouteEntry 15 }
|
||||
|
||||
ipMRouteHCOctets OBJECT-TYPE
|
||||
SYNTAX Counter64
|
||||
MAX-ACCESS read-only
|
||||
STATUS current
|
||||
DESCRIPTION
|
||||
"The number of octets contained in IP datagrams which were
|
||||
received from these sources and addressed to this multicast
|
||||
group address, and which were forwarded by this router.
|
||||
This object is a 64-bit version of ipMRouteOctets."
|
||||
::= { ipMRouteEntry 16 }
|
||||
|
||||
--
|
||||
-- The IP Multicast Routing Next Hop Table
|
||||
--
|
||||
|
||||
ipMRouteNextHopTable OBJECT-TYPE
|
||||
SYNTAX SEQUENCE OF IpMRouteNextHopEntry
|
||||
MAX-ACCESS not-accessible
|
||||
STATUS current
|
||||
DESCRIPTION
|
||||
"The (conceptual) table containing information on the next-
|
||||
hops on outgoing interfaces for routing IP multicast
|
||||
|
||||
datagrams. Each entry is one of a list of next-hops on
|
||||
outgoing interfaces for particular sources sending to a
|
||||
particular multicast group address."
|
||||
::= { ipMRoute 3 }
|
||||
|
||||
ipMRouteNextHopEntry OBJECT-TYPE
|
||||
SYNTAX IpMRouteNextHopEntry
|
||||
MAX-ACCESS not-accessible
|
||||
STATUS current
|
||||
DESCRIPTION
|
||||
"An entry (conceptual row) in the list of next-hops on
|
||||
outgoing interfaces to which IP multicast datagrams from
|
||||
particular sources to a IP multicast group address are
|
||||
routed. Discontinuities in counters in this entry can be
|
||||
detected by observing the value of ipMRouteUpTime."
|
||||
INDEX { ipMRouteNextHopGroup, ipMRouteNextHopSource,
|
||||
ipMRouteNextHopSourceMask, ipMRouteNextHopIfIndex,
|
||||
ipMRouteNextHopAddress }
|
||||
::= { ipMRouteNextHopTable 1 }
|
||||
|
||||
IpMRouteNextHopEntry ::= SEQUENCE {
|
||||
ipMRouteNextHopGroup IpAddress,
|
||||
ipMRouteNextHopSource IpAddress,
|
||||
ipMRouteNextHopSourceMask IpAddress,
|
||||
ipMRouteNextHopIfIndex InterfaceIndex,
|
||||
ipMRouteNextHopAddress IpAddress,
|
||||
ipMRouteNextHopState INTEGER,
|
||||
ipMRouteNextHopUpTime TimeTicks,
|
||||
ipMRouteNextHopExpiryTime TimeTicks,
|
||||
ipMRouteNextHopClosestMemberHops Integer32,
|
||||
ipMRouteNextHopProtocol IANAipMRouteProtocol,
|
||||
ipMRouteNextHopPkts Counter32
|
||||
}
|
||||
|
||||
ipMRouteNextHopGroup OBJECT-TYPE
|
||||
SYNTAX IpAddress
|
||||
MAX-ACCESS not-accessible
|
||||
STATUS current
|
||||
DESCRIPTION
|
||||
"The IP multicast group for which this entry specifies a
|
||||
next-hop on an outgoing interface."
|
||||
::= { ipMRouteNextHopEntry 1 }
|
||||
|
||||
ipMRouteNextHopSource OBJECT-TYPE
|
||||
SYNTAX IpAddress
|
||||
MAX-ACCESS not-accessible
|
||||
STATUS current
|
||||
DESCRIPTION
|
||||
"The network address which when combined with the
|
||||
corresponding value of ipMRouteNextHopSourceMask identifies
|
||||
the sources for which this entry specifies a next-hop on an
|
||||
outgoing interface."
|
||||
::= { ipMRouteNextHopEntry 2 }
|
||||
|
||||
ipMRouteNextHopSourceMask OBJECT-TYPE
|
||||
SYNTAX IpAddress
|
||||
MAX-ACCESS not-accessible
|
||||
STATUS current
|
||||
DESCRIPTION
|
||||
"The network mask which when combined with the corresponding
|
||||
value of ipMRouteNextHopSource identifies the sources for
|
||||
which this entry specifies a next-hop on an outgoing
|
||||
interface."
|
||||
::= { ipMRouteNextHopEntry 3 }
|
||||
|
||||
ipMRouteNextHopIfIndex OBJECT-TYPE
|
||||
SYNTAX InterfaceIndex
|
||||
MAX-ACCESS not-accessible
|
||||
STATUS current
|
||||
DESCRIPTION
|
||||
"The ifIndex value of the interface for the outgoing
|
||||
interface for this next-hop."
|
||||
::= { ipMRouteNextHopEntry 4 }
|
||||
|
||||
ipMRouteNextHopAddress OBJECT-TYPE
|
||||
SYNTAX IpAddress
|
||||
MAX-ACCESS not-accessible
|
||||
STATUS current
|
||||
DESCRIPTION
|
||||
"The address of the next-hop specific to this entry. For
|
||||
most interfaces, this is identical to ipMRouteNextHopGroup.
|
||||
NBMA interfaces, however, may have multiple next-hop
|
||||
addresses out a single outgoing interface."
|
||||
::= { ipMRouteNextHopEntry 5 }
|
||||
|
||||
ipMRouteNextHopState OBJECT-TYPE
|
||||
SYNTAX INTEGER { pruned(1), forwarding(2) }
|
||||
MAX-ACCESS read-only
|
||||
STATUS current
|
||||
DESCRIPTION
|
||||
"An indication of whether the outgoing interface and next-
|
||||
hop represented by this entry is currently being used to
|
||||
forward IP datagrams. The value 'forwarding' indicates it
|
||||
is currently being used; the value 'pruned' indicates it is
|
||||
not."
|
||||
::= { ipMRouteNextHopEntry 6 }
|
||||
|
||||
ipMRouteNextHopUpTime OBJECT-TYPE
|
||||
SYNTAX TimeTicks
|
||||
MAX-ACCESS read-only
|
||||
STATUS current
|
||||
DESCRIPTION
|
||||
"The time since the multicast routing information
|
||||
represented by this entry was learned by the router."
|
||||
::= { ipMRouteNextHopEntry 7 }
|
||||
|
||||
ipMRouteNextHopExpiryTime OBJECT-TYPE
|
||||
SYNTAX TimeTicks
|
||||
MAX-ACCESS read-only
|
||||
STATUS current
|
||||
DESCRIPTION
|
||||
"The minimum amount of time remaining before this entry will
|
||||
be aged out. If ipMRouteNextHopState is pruned(1), the
|
||||
remaining time until the prune expires and the state reverts
|
||||
to forwarding(2). Otherwise, the remaining time until this
|
||||
entry is removed from the table. The time remaining may be
|
||||
copied from ipMRouteExpiryTime if the protocol in use for
|
||||
this entry does not specify next-hop timers. The value 0
|
||||
indicates that the entry is not subject to aging."
|
||||
::= { ipMRouteNextHopEntry 8 }
|
||||
|
||||
ipMRouteNextHopClosestMemberHops OBJECT-TYPE
|
||||
SYNTAX Integer32
|
||||
MAX-ACCESS read-only
|
||||
STATUS current
|
||||
DESCRIPTION
|
||||
"The minimum number of hops between this router and any
|
||||
member of this IP multicast group reached via this next-hop
|
||||
on this outgoing interface. Any IP multicast datagrams for
|
||||
the group which have a TTL less than this number of hops
|
||||
will not be forwarded to this next-hop."
|
||||
::= { ipMRouteNextHopEntry 9 }
|
||||
|
||||
ipMRouteNextHopProtocol OBJECT-TYPE
|
||||
SYNTAX IANAipMRouteProtocol
|
||||
MAX-ACCESS read-only
|
||||
STATUS current
|
||||
DESCRIPTION
|
||||
"The routing mechanism via which this next-hop was learned."
|
||||
::= { ipMRouteNextHopEntry 10 }
|
||||
|
||||
ipMRouteNextHopPkts OBJECT-TYPE
|
||||
SYNTAX Counter32
|
||||
MAX-ACCESS read-only
|
||||
STATUS current
|
||||
DESCRIPTION
|
||||
"The number of packets which have been forwarded using this
|
||||
route."
|
||||
::= { ipMRouteNextHopEntry 11 }
|
||||
|
||||
--
|
||||
-- The Multicast Routing Interface Table
|
||||
--
|
||||
|
||||
ipMRouteInterfaceTable OBJECT-TYPE
|
||||
SYNTAX SEQUENCE OF IpMRouteInterfaceEntry
|
||||
MAX-ACCESS not-accessible
|
||||
STATUS current
|
||||
DESCRIPTION
|
||||
"The (conceptual) table containing multicast routing
|
||||
information specific to interfaces."
|
||||
::= { ipMRoute 4 }
|
||||
|
||||
ipMRouteInterfaceEntry OBJECT-TYPE
|
||||
SYNTAX IpMRouteInterfaceEntry
|
||||
MAX-ACCESS not-accessible
|
||||
STATUS current
|
||||
DESCRIPTION
|
||||
"An entry (conceptual row) containing the multicast routing
|
||||
information for a particular interface."
|
||||
INDEX { ipMRouteInterfaceIfIndex }
|
||||
::= { ipMRouteInterfaceTable 1 }
|
||||
|
||||
IpMRouteInterfaceEntry ::= SEQUENCE {
|
||||
ipMRouteInterfaceIfIndex InterfaceIndex,
|
||||
ipMRouteInterfaceTtl Integer32,
|
||||
ipMRouteInterfaceProtocol IANAipMRouteProtocol,
|
||||
ipMRouteInterfaceRateLimit Integer32,
|
||||
ipMRouteInterfaceInMcastOctets Counter32,
|
||||
ipMRouteInterfaceOutMcastOctets Counter32,
|
||||
ipMRouteInterfaceHCInMcastOctets Counter64,
|
||||
ipMRouteInterfaceHCOutMcastOctets Counter64
|
||||
}
|
||||
|
||||
ipMRouteInterfaceIfIndex OBJECT-TYPE
|
||||
SYNTAX InterfaceIndex
|
||||
MAX-ACCESS not-accessible
|
||||
STATUS current
|
||||
DESCRIPTION
|
||||
"The ifIndex value of the interface for which this entry
|
||||
contains information."
|
||||
::= { ipMRouteInterfaceEntry 1 }
|
||||
|
||||
ipMRouteInterfaceTtl OBJECT-TYPE
|
||||
SYNTAX Integer32 (0..255)
|
||||
MAX-ACCESS read-write
|
||||
STATUS current
|
||||
DESCRIPTION
|
||||
"The datagram TTL threshold for the interface. Any IP
|
||||
multicast datagrams with a TTL less than this threshold will
|
||||
not be forwarded out the interface. The default value of 0
|
||||
means all multicast packets are forwarded out the
|
||||
interface."
|
||||
::= { ipMRouteInterfaceEntry 2 }
|
||||
|
||||
ipMRouteInterfaceProtocol OBJECT-TYPE
|
||||
SYNTAX IANAipMRouteProtocol
|
||||
MAX-ACCESS read-only
|
||||
STATUS current
|
||||
DESCRIPTION
|
||||
"The routing protocol running on this interface."
|
||||
::= { ipMRouteInterfaceEntry 3 }
|
||||
|
||||
ipMRouteInterfaceRateLimit OBJECT-TYPE
|
||||
SYNTAX Integer32
|
||||
MAX-ACCESS read-write
|
||||
STATUS current
|
||||
DESCRIPTION
|
||||
"The rate-limit, in kilobits per second, of forwarded
|
||||
multicast traffic on the interface. A rate-limit of 0
|
||||
indicates that no rate limiting is done."
|
||||
DEFVAL { 0 }
|
||||
::= { ipMRouteInterfaceEntry 4 }
|
||||
|
||||
ipMRouteInterfaceInMcastOctets OBJECT-TYPE
|
||||
SYNTAX Counter32
|
||||
MAX-ACCESS read-only
|
||||
STATUS current
|
||||
DESCRIPTION
|
||||
"The number of octets of multicast packets that have arrived
|
||||
on the interface, including framing characters. This object
|
||||
is similar to ifInOctets in the Interfaces MIB, except that
|
||||
only multicast packets are counted."
|
||||
::= { ipMRouteInterfaceEntry 5 }
|
||||
|
||||
ipMRouteInterfaceOutMcastOctets OBJECT-TYPE
|
||||
SYNTAX Counter32
|
||||
MAX-ACCESS read-only
|
||||
STATUS current
|
||||
DESCRIPTION
|
||||
"The number of octets of multicast packets that have been
|
||||
sent on the interface."
|
||||
::= { ipMRouteInterfaceEntry 6 }
|
||||
|
||||
ipMRouteInterfaceHCInMcastOctets OBJECT-TYPE
|
||||
SYNTAX Counter64
|
||||
MAX-ACCESS read-only
|
||||
STATUS current
|
||||
DESCRIPTION
|
||||
"The number of octets of multicast packets that have arrived
|
||||
on the interface, including framing characters. This object
|
||||
is a 64-bit version of ipMRouteInterfaceInMcastOctets. It
|
||||
is similar to ifHCInOctets in the Interfaces MIB, except
|
||||
that only multicast packets are counted."
|
||||
::= { ipMRouteInterfaceEntry 7 }
|
||||
|
||||
ipMRouteInterfaceHCOutMcastOctets OBJECT-TYPE
|
||||
SYNTAX Counter64
|
||||
MAX-ACCESS read-only
|
||||
STATUS current
|
||||
DESCRIPTION
|
||||
"The number of octets of multicast packets that have been
|
||||
sent on the interface. This object is a 64-bit version of
|
||||
ipMRouteInterfaceOutMcastOctets."
|
||||
::= { ipMRouteInterfaceEntry 8 }
|
||||
|
||||
--
|
||||
-- The IP Multicast Scope Boundary Table
|
||||
--
|
||||
|
||||
ipMRouteBoundaryTable OBJECT-TYPE
|
||||
SYNTAX SEQUENCE OF IpMRouteBoundaryEntry
|
||||
MAX-ACCESS not-accessible
|
||||
STATUS current
|
||||
DESCRIPTION
|
||||
"The (conceptual) table listing the router's scoped
|
||||
multicast address boundaries."
|
||||
::= { ipMRoute 5 }
|
||||
|
||||
ipMRouteBoundaryEntry OBJECT-TYPE
|
||||
SYNTAX IpMRouteBoundaryEntry
|
||||
MAX-ACCESS not-accessible
|
||||
STATUS current
|
||||
DESCRIPTION
|
||||
"An entry (conceptual row) in the ipMRouteBoundaryTable
|
||||
representing a scoped boundary."
|
||||
INDEX { ipMRouteBoundaryIfIndex, ipMRouteBoundaryAddress,
|
||||
ipMRouteBoundaryAddressMask }
|
||||
::= { ipMRouteBoundaryTable 1 }
|
||||
|
||||
IpMRouteBoundaryEntry ::= SEQUENCE {
|
||||
ipMRouteBoundaryIfIndex InterfaceIndex,
|
||||
ipMRouteBoundaryAddress IpAddress,
|
||||
ipMRouteBoundaryAddressMask IpAddress,
|
||||
ipMRouteBoundaryStatus RowStatus
|
||||
}
|
||||
|
||||
ipMRouteBoundaryIfIndex OBJECT-TYPE
|
||||
SYNTAX InterfaceIndex
|
||||
MAX-ACCESS not-accessible
|
||||
STATUS current
|
||||
DESCRIPTION
|
||||
"The IfIndex value for the interface to which this boundary
|
||||
applies. Packets with a destination address in the
|
||||
associated address/mask range will not be forwarded out this
|
||||
interface."
|
||||
::= { ipMRouteBoundaryEntry 1 }
|
||||
|
||||
ipMRouteBoundaryAddress OBJECT-TYPE
|
||||
SYNTAX IpAddress
|
||||
MAX-ACCESS not-accessible
|
||||
STATUS current
|
||||
DESCRIPTION
|
||||
"The group address which when combined with the
|
||||
corresponding value of ipMRouteBoundaryAddressMask
|
||||
identifies the group range for which the scoped boundary
|
||||
exists. Scoped addresses must come from the range 239.x.x.x
|
||||
as specified in RFC 2365."
|
||||
::= { ipMRouteBoundaryEntry 2 }
|
||||
|
||||
ipMRouteBoundaryAddressMask OBJECT-TYPE
|
||||
SYNTAX IpAddress
|
||||
MAX-ACCESS not-accessible
|
||||
STATUS current
|
||||
DESCRIPTION
|
||||
"The group address mask which when combined with the
|
||||
corresponding value of ipMRouteBoundaryAddress identifies
|
||||
the group range for which the scoped boundary exists."
|
||||
::= { ipMRouteBoundaryEntry 3 }
|
||||
|
||||
ipMRouteBoundaryStatus OBJECT-TYPE
|
||||
SYNTAX RowStatus
|
||||
MAX-ACCESS read-create
|
||||
STATUS current
|
||||
DESCRIPTION
|
||||
"The status of this row, by which new entries may be
|
||||
created, or old entries deleted from this table."
|
||||
::= { ipMRouteBoundaryEntry 4 }
|
||||
|
||||
--
|
||||
-- The IP Multicast Scope Name Table
|
||||
--
|
||||
|
||||
ipMRouteScopeNameTable OBJECT-TYPE
|
||||
SYNTAX SEQUENCE OF IpMRouteScopeNameEntry
|
||||
MAX-ACCESS not-accessible
|
||||
STATUS current
|
||||
DESCRIPTION
|
||||
"The (conceptual) table listing the multicast scope names."
|
||||
::= { ipMRoute 6 }
|
||||
|
||||
ipMRouteScopeNameEntry OBJECT-TYPE
|
||||
SYNTAX IpMRouteScopeNameEntry
|
||||
MAX-ACCESS not-accessible
|
||||
STATUS current
|
||||
DESCRIPTION
|
||||
"An entry (conceptual row) in the ipMRouteScopeNameTable
|
||||
representing a multicast scope name."
|
||||
INDEX { ipMRouteScopeNameAddress,
|
||||
ipMRouteScopeNameAddressMask,
|
||||
IMPLIED ipMRouteScopeNameLanguage }
|
||||
::= { ipMRouteScopeNameTable 1 }
|
||||
|
||||
IpMRouteScopeNameEntry ::= SEQUENCE {
|
||||
ipMRouteScopeNameAddress IpAddress,
|
||||
ipMRouteScopeNameAddressMask IpAddress,
|
||||
ipMRouteScopeNameLanguage LanguageTag,
|
||||
ipMRouteScopeNameString SnmpAdminString,
|
||||
ipMRouteScopeNameDefault TruthValue,
|
||||
ipMRouteScopeNameStatus RowStatus
|
||||
}
|
||||
|
||||
ipMRouteScopeNameAddress OBJECT-TYPE
|
||||
SYNTAX IpAddress
|
||||
MAX-ACCESS not-accessible
|
||||
STATUS current
|
||||
DESCRIPTION
|
||||
"The group address which when combined with the
|
||||
corresponding value of ipMRouteScopeNameAddressMask
|
||||
identifies the group range associated with the multicast
|
||||
scope. Scoped addresses must come from the range
|
||||
239.x.x.x."
|
||||
::= { ipMRouteScopeNameEntry 1 }
|
||||
|
||||
ipMRouteScopeNameAddressMask OBJECT-TYPE
|
||||
SYNTAX IpAddress
|
||||
MAX-ACCESS not-accessible
|
||||
STATUS current
|
||||
DESCRIPTION
|
||||
"The group address mask which when combined with the
|
||||
corresponding value of ipMRouteScopeNameAddress identifies
|
||||
the group range associated with the multicast scope."
|
||||
::= { ipMRouteScopeNameEntry 2 }
|
||||
|
||||
ipMRouteScopeNameLanguage OBJECT-TYPE
|
||||
SYNTAX LanguageTag
|
||||
MAX-ACCESS not-accessible
|
||||
STATUS current
|
||||
DESCRIPTION
|
||||
"The RFC 1766-style language tag associated with the scope
|
||||
name."
|
||||
::= { ipMRouteScopeNameEntry 3 }
|
||||
|
||||
ipMRouteScopeNameString OBJECT-TYPE
|
||||
SYNTAX SnmpAdminString
|
||||
MAX-ACCESS read-create
|
||||
STATUS current
|
||||
DESCRIPTION
|
||||
"The textual name associated with the multicast scope. The
|
||||
value of this object should be suitable for displaying to
|
||||
end-users, such as when allocating a multicast address in
|
||||
this scope. When no name is specified, the default value of
|
||||
this object should be the string 239.x.x.x/y with x and y
|
||||
replaced appropriately to describe the address and mask
|
||||
length associated with the scope."
|
||||
::= { ipMRouteScopeNameEntry 4 }
|
||||
|
||||
ipMRouteScopeNameDefault OBJECT-TYPE
|
||||
SYNTAX TruthValue
|
||||
MAX-ACCESS read-create
|
||||
STATUS current
|
||||
DESCRIPTION
|
||||
"If true, indicates a preference that the name in the
|
||||
following language should be used by applications if no name
|
||||
is available in a desired language."
|
||||
DEFVAL { false }
|
||||
::= { ipMRouteScopeNameEntry 5 }
|
||||
|
||||
ipMRouteScopeNameStatus OBJECT-TYPE
|
||||
SYNTAX RowStatus
|
||||
MAX-ACCESS read-create
|
||||
STATUS current
|
||||
DESCRIPTION
|
||||
"The status of this row, by which new entries may be
|
||||
created, or old entries deleted from this table."
|
||||
::= { ipMRouteScopeNameEntry 6 }
|
||||
|
||||
|
||||
-- conformance information
|
||||
|
||||
ipMRouteMIBConformance
|
||||
OBJECT IDENTIFIER ::= { ipMRouteStdMIB 2 }
|
||||
ipMRouteMIBCompliances
|
||||
OBJECT IDENTIFIER ::= { ipMRouteMIBConformance 1 }
|
||||
ipMRouteMIBGroups OBJECT IDENTIFIER ::= { ipMRouteMIBConformance 2 }
|
||||
|
||||
-- compliance statements
|
||||
|
||||
ipMRouteMIBCompliance MODULE-COMPLIANCE
|
||||
STATUS current
|
||||
DESCRIPTION
|
||||
"The compliance statement for the IP Multicast MIB."
|
||||
MODULE -- this module
|
||||
MANDATORY-GROUPS { ipMRouteMIBBasicGroup,
|
||||
ipMRouteMIBRouteGroup}
|
||||
|
||||
GROUP ipMRouteMIBBoundaryGroup
|
||||
DESCRIPTION
|
||||
"This group is mandatory if the router supports
|
||||
administratively-scoped multicast address boundaries."
|
||||
|
||||
OBJECT ipMRouteBoundaryStatus
|
||||
MIN-ACCESS read-only
|
||||
DESCRIPTION
|
||||
"Write access is not required."
|
||||
|
||||
OBJECT ipMRouteScopeNameStatus
|
||||
MIN-ACCESS read-only
|
||||
DESCRIPTION
|
||||
"Write access is not required."
|
||||
|
||||
GROUP ipMRouteMIBHCInterfaceGroup
|
||||
DESCRIPTION
|
||||
"This group is mandatory only for those network interfaces
|
||||
for which the value of the corresponding instance of ifSpeed
|
||||
is greater than 20,000,000 bits/second."
|
||||
|
||||
::= { ipMRouteMIBCompliances 1 }
|
||||
|
||||
-- units of conformance
|
||||
|
||||
ipMRouteMIBBasicGroup OBJECT-GROUP
|
||||
OBJECTS { ipMRouteEnable, ipMRouteEntryCount,
|
||||
ipMRouteUpstreamNeighbor, ipMRouteInIfIndex,
|
||||
ipMRouteUpTime, ipMRouteExpiryTime,
|
||||
ipMRouteNextHopState,
|
||||
ipMRouteNextHopUpTime,
|
||||
ipMRouteNextHopExpiryTime,
|
||||
ipMRouteNextHopProtocol,
|
||||
ipMRouteNextHopPkts,
|
||||
ipMRouteInterfaceTtl,
|
||||
ipMRouteInterfaceProtocol, ipMRouteInterfaceRateLimit,
|
||||
ipMRouteInterfaceInMcastOctets,
|
||||
ipMRouteInterfaceOutMcastOctets,
|
||||
ipMRouteProtocol
|
||||
}
|
||||
STATUS current
|
||||
DESCRIPTION
|
||||
"A collection of objects to support basic management of IP
|
||||
Multicast routing."
|
||||
::= { ipMRouteMIBGroups 1 }
|
||||
|
||||
ipMRouteMIBHopCountGroup OBJECT-GROUP
|
||||
OBJECTS { ipMRouteNextHopClosestMemberHops }
|
||||
STATUS current
|
||||
DESCRIPTION
|
||||
"A collection of objects to support management of the use of
|
||||
hop counts in IP Multicast routing."
|
||||
::= { ipMRouteMIBGroups 2 }
|
||||
|
||||
ipMRouteMIBBoundaryGroup OBJECT-GROUP
|
||||
OBJECTS { ipMRouteBoundaryStatus, ipMRouteScopeNameString,
|
||||
ipMRouteScopeNameDefault, ipMRouteScopeNameStatus }
|
||||
STATUS current
|
||||
DESCRIPTION
|
||||
"A collection of objects to support management of scoped
|
||||
multicast address boundaries."
|
||||
::= { ipMRouteMIBGroups 3 }
|
||||
|
||||
ipMRouteMIBPktsOutGroup OBJECT-GROUP
|
||||
OBJECTS { ipMRouteNextHopPkts }
|
||||
STATUS current
|
||||
DESCRIPTION
|
||||
"A collection of objects to support management of packet
|
||||
counters for each outgoing interface entry of a route."
|
||||
::= { ipMRouteMIBGroups 4 }
|
||||
|
||||
ipMRouteMIBHCInterfaceGroup OBJECT-GROUP
|
||||
OBJECTS { ipMRouteInterfaceHCInMcastOctets,
|
||||
ipMRouteInterfaceHCOutMcastOctets,
|
||||
ipMRouteHCOctets }
|
||||
STATUS current
|
||||
DESCRIPTION
|
||||
"A collection of objects providing information specific to
|
||||
high speed (greater than 20,000,000 bits/second) network
|
||||
interfaces."
|
||||
::= { ipMRouteMIBGroups 5 }
|
||||
|
||||
ipMRouteMIBRouteGroup OBJECT-GROUP
|
||||
OBJECTS { ipMRouteRtProto, ipMRouteRtAddress,
|
||||
ipMRouteRtMask, ipMRouteRtType }
|
||||
STATUS current
|
||||
DESCRIPTION
|
||||
"A collection of objects providing information on the
|
||||
relationship between multicast routing information, and the
|
||||
IP Forwarding Table."
|
||||
::= { ipMRouteMIBGroups 6 }
|
||||
|
||||
ipMRouteMIBPktsGroup OBJECT-GROUP
|
||||
OBJECTS { ipMRoutePkts, ipMRouteDifferentInIfPackets,
|
||||
ipMRouteOctets }
|
||||
STATUS current
|
||||
DESCRIPTION
|
||||
"A collection of objects to support management of packet
|
||||
counters for each forwarding entry."
|
||||
::= { ipMRouteMIBGroups 7 }
|
||||
|
||||
END
|
||||
File diff suppressed because it is too large
Load Diff
File diff suppressed because it is too large
Load Diff
File diff suppressed because it is too large
Load Diff
File diff suppressed because it is too large
Load Diff
File diff suppressed because it is too large
Load Diff
File diff suppressed because it is too large
Load Diff
File diff suppressed because it is too large
Load Diff
File diff suppressed because it is too large
Load Diff
File diff suppressed because it is too large
Load Diff
File diff suppressed because it is too large
Load Diff
Reference in New Issue
Block a user