SNMP MIB Search

Configuration values for a virtual ring. 

Configuration and status information of a remote RSRB peer. 

A ring described by a unique ring number within the
bridged token ring network, and the virtual ring
which it is associated with.

The configured number of the virtual ring in which this peer is
participating.

The IP address configured for this RSRB local peer.

The maximum number of packets that can be held in any single
outbound TCP queue to a remote peer before packets are discarded.
This value indicates the configured or default value.

An arbitrary index that uniquely identifies a remote peer
within a virtual ring.

How traffic is encapsulated for RSRB:
tcp = IP datagrams over a TCP connection
serial = point-to-point (serial) direct encapsulation
lan = direct encapsulation over a LAN
fst = IP datagrams over a Fast Sequenced Transport connection
frameRelay = direct encapsulation over frame relay

The IP address used by the RSRB remote peer.
This field is meaningful only for TCP and FST encapsulation.
For other encapsulation types 0.0.0.0 is returned.

Local interface index value to the RSRB remote peer.  Same value
as used for accessing the Interface MIB for the same interface.
This field is meaningful only for serial, LAN and
frame relay encapsulation.  For other encapsulation types 0
is returned.

Current state of the RSRB session with the remote peer.

Number of packets received from remote peer.

Number of packets transmitted to remote peer.

Number of bytes received from remote peer.

Number of bytes transmitted to remote peer.

Number of explorer packets received from the remote peer.

Number of packets being held by the local router
in the TCP output queue to the remote peer.

Number of received packets discarded by the local router.
The reasons for packets being dropped include, but are not
limited to, problems with the configuration, queue overflow,
and protocol errors.

Indicates if local acknowledgment is used for the sessions
going to the remote peer.
TRUE -> local acknowledgment is used
FALSE -> local acknowledgment is not used

The version of RSRB used between local and remote peer.
Generally peers can communicate if they are within one version
of each other.  The value returned is the lower version
of the two peers.

The configured ring number that uniquely identifies this network
segment or ring within the bridged token ring network.

The configured number of the bridge that connects this entry's
ring to the virtual ring.

Indicates if the entry represents a local or remote ring.
TRUE indicates a local ring.
FALSE indicates a remote ring.

The ring type.

The mac address of either the local router's interface to the ring
for local ring entries, or the remote peer's interface to the ring
for remote ring entries.  Not valid for entry types
remote SDLLC and QLLC; for these type '00 00 00 00 00 00' will be
returned.

For local ring entries, the local interface into the ring.  This is
the same value as used for accessing the Interface MIB for the
same interface.
Not meaningful for remote ring entries; for these types
0 will be returned.

For remote ring entries, the IP address of the remote RSRB peer.
Not meaningful for local ring entries, and so 0.0.0.0 will be
returned.

The number of packets forwarded by the local router onto this ring.

Table of virtual rings in the router.

Table of RSRB remote peers for a virtual ring.

Table of local and remote rings associated with a
virtual ring.

This trap indicates that the state of an RSRB remote peer
has transitioned to active (psConnected) or inactive
(psDead or psClosed).

This is the MIB module for objects used to manage RSRB.
Overview of remote source-route bridging (RSRB) management and MIB
MIB description
The RSRB MIB will include the following managed entities:
1) Virtual Rings
2) Remote Peers
3) Associated Token Rings
The goal of this MIB to to allow a management stations to
display the attributes of the local-remote RSRB peer relationship.
The following example configuration will show how the RSRB MIB can
be used to manage RSRB.
== Token Ring == CISCO A == IP Network/ == CISCO B == Token Ring
Virtual Ring
Both CISCO A and CISCO B are RSRB peers, having the same virtual ring
number.  In this example information will be gatherered from CISCO A
(the local peer), and CISCO B is considered to be CISCO A's remote peer.
The first table is the virtual ring table.  There is one entry for
each RSRB virtual ring the router is defined on.  The fields included
in this table include
* the virtual ring number, or index
* the IP address used by the router
* the maximum outbound queue size for each RSRB remote peer
In this example the table has a single entry since CISCO A only belongs
to one RSRB virtual ring.
The next table is for each remote peer in the virtual ring.  There
can be multiple RSRB remote peers.  The remote peer information includes:
* an internally generated (not configured) index into the table
* the type of data encapsulation with the remote peer
* identification of how to get to the remote peer; either an IP address
or an interface index, depending upon the encapsulation type
* the state of the remote peer
* various statistics (bytes and packets sent and received, explorers
generated, outbound queue size, and packets dropped
* whether local acknowledgment is used with the remote peer
* the RSRB version of the peer
In this example there would be just one remote peer table entry,
for CISCO B.
The last table is for the real local and remote token rings associated
with the RSRB virtual ring, that this router has either had configured
or learned about dynamically.  The ring information includes:
* the token ring number (index)
* the bridge number connecting the real ring to the virtual ring
* the ring entry type
* the local or remote routers mac address on the interface to the ring
* the local router's interface index, or the remote router's IP address,
depending on if this is a local or remote ring
* number of packets forwarded by the local router onto this ring
In this example CISCO A would have two ring entries:  one for the local
ring it is connected to, and one for the ring CISCO B is a part of.
A management application can construct a virtual ring view either by
collecting MIB information from all routers and grouping those in the
same virtual ring together, or beginning with a particular router or
routers, and collecting MIB information about other peer routers.

A collection of objects providing configuration capability.

A collection of objects providing operational control
capability.

A collection of objects providing operational control
capability.