This is the MIB module for objects used to manage RSRB.
Overview of remote source-route bridging (RSRB) management and MIB
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
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.