SONOMASYSTEMS-SONOMA-SRTB-MIB

All MIBs › SONOMASYSTEMS-SONOMA-SRTB-MIB

Category: SNA and Legacy WAN Protocols, SonomaSystems ATM WAN Management

Description: Manages SonomaSystems Sonoma SRTB protocol interface configuration and operational statistics.

Start monitoring vendor-neutral, standards-based MIB, any SNMPv3-capable network device (SNMP engine identity/boot/clock status) with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.

What Is SONOMASYSTEMS-SONOMA-SRTB-MIB?

SONOMASYSTEMS-SONOMA-SRTB-MIB is a vendor-specific MIB from Sonoma Systems (later acquired into the Cabletron/Riverstone lineage) that models Source Routing and Translational Bridging (SRTB) for the Sonoma product line of LAN switches, sitting under the sonomaBridging subtree. It exposes per-port source-routing configuration and counters in srtPortTable (srtPortHopCount, srtPortLocalSegment, srtPortLargestFrame, srtPortSTESpanMode, and frame counters for specifically-routed, all-routes-explorer, and spanning-tree-explorer traffic, plus discard counters for segment mismatches, duplicate segments, and hop-count-exceeded events), and a learned source-route cache in srtSourceRouteTable (indexed by VLAN and MAC address, holding the routing information field, entry type, and direction). This is a legacy Token Ring-era bridging MIB rather than a modern Ethernet MIB, so it's primarily relevant to environments still running IBM Token Ring/source-routing bridged segments. It depends on the base SONOMASYSTEMS-SONOMA-MIB for its OID placement and on the underlying bridge/VLAN configuration for context. It is deployed on Sonoma Systems switches providing source-routing bridging services, and administrators can download the SONOMASYSTEMS-SONOMA-SRTB-MIB file to load it into their MIB browser.

IPNetwork Monitor allows you to monitor SNMP objects defined in SONOMASYSTEMS-SONOMA-SRTB-MIB. Use the built-in SNMP Monitoring Browser to explore available variables, view their current values and descriptions, and select the objects you want to monitor. You can then create SNMP monitors, configure thresholds, and receive alerts when monitored values change.

Supported Devices

Sonoma Systems switch product line (source-routing/translational bridging capable)

Monitoring Examples

An operator polls srtPortTable for a given port (srtPortIfIndex) to review srtPortSegmentMismatchDiscards and srtPortDuplicateSegmentDiscards alongside srtPortHopCountExceededDiscards; a rising count of segment-mismatch or duplicate-segment discards on one port would point to a misconfigured ring segment number or a source-routing loop on that Token Ring segment.

What Can Be Monitored

per-port source-route hop count and segment settings
specifically-routed and explorer frame counters (ARE/STE)
segment-mismatch and duplicate-segment discard counters
hop-count-exceeded discard counter
learned source-route table entries by VLAN/MAC

Imported Objects

From RFC-1212

OBJECT-TYPE

From RFC1155-SMI

Counter

From SONOMASYSTEMS-SONOMA-MIB

sonomaBridging

OBJECT-IDENTITY

OIDs

OID symbolic	OID numeric	Type	Access	Description
srtBridging	1.3.6.1.4.1.2926.25.3.2
INT srtBridgeNumber	1.3.6.1.4.1.2926.25.3.2.1	INTEGER	read-write	Obsoleted by vlanConfigBrNumber. Was: A bridge number uniquely identifies a bridge when more than one bridge is used to span the same segments. This object can have values between 0..15 inclusive and also a value 65535. When set to 65535, source routing on the unit is DISABLED.
INT srtSourceRouteAgingTime	1.3.6.1.4.1.2926.25.3.2.2	INTEGER	read-write	If no frames from a source are received for this time, any associated routing information in the Source Route Table is purged. The granularity is seconds.
srtPortTable	1.3.6.1.4.1.2926.25.3.2.3		not-accessible	Table of Source Routing per Port parameters.
srtPortEntry	1.3.6.1.4.1.2926.25.3.2.3.1		not-accessible	An entry in the logical port instanced SRT Port Table.
INT srtPortIfIndex	1.3.6.1.4.1.2926.25.3.2.3.1.1	INTEGER	read-only	The port number of the port for which this entry contains Source Route management information.
INT srtPortHopCount	1.3.6.1.4.1.2926.25.3.2.3.1.2	INTEGER	read-write	The maximum number of routing descriptors allowed in an All Paths or Spanning Tree Explorer frames.
INT srtPortLocalSegment	1.3.6.1.4.1.2926.25.3.2.3.1.3	INTEGER	read-write	The segment number that uniquely identifies the segment to which this port is connected. Current source routing protocols limit this value to the range: 0 through 4095. A value of 65535 signifies that no segment number is assigned to this port.
INT srtPortLargestFrame	1.3.6.1.4.1.2926.25.3.2.3.1.4	INTEGER	read-write	The maximum size of the INFO field (LLC and above) that this port can send/receive. It does not include any MAC level (framing) octets. The value of this object is used by this bridge to determine whether a modification of the LargestFrame (LF, see [14]) field of the Routing Control field of the Routing Information Field is necessary. Valid values as defined by the 802.5 source routing bridging specification[14] are 516, 1500, 2052, 4472, 8144, 11407, 17800, and 65535 octets. Behavior of the port when an illegal value is written is implementation specific. It is recommended that a reasonable legal value be chosen.
INT srtPortSTESpanMode	1.3.6.1.4.1.2926.25.3.2.3.1.5	INTEGER	read-write	Determines how this port behaves when presented with a Spanning Tree Explorer frame. The value 'disabled(2)' indicates that the port will not accept or send Spanning Tree Explorer packets; any STE packets received will be silently discarded. The value 'forced(3)' indicates the port will always accept and propagate Spanning Tree Explorer frames. This allows a manually configured Spanning Tree for this class of packet to be configured. Note that unlike transparent bridging this is not catastrophic to the network if there are loops. The value 'auto-span(1)' can only be returned by a bridge that both implements the Spanning Tree Protocol and has use of the protocol enabled on this port. The behavior of the port for Spanning Tree Explorer frames is determined by the state of dot1dStpPortState. If the port is in the 'forwarding' state, the frame will be accepted or propagated. Otherwise it will be silently discarded.
CTR srtPortSpecInFrames	1.3.6.1.4.1.2926.25.3.2.3.1.6	Counter	read-only	The number of specifically routed frames that have been received from this port's segment.
CTR srtPortSpecOutFrames	1.3.6.1.4.1.2926.25.3.2.3.1.7	Counter	read-only	The number of specifically routed frames that this port has transmitted on its segment.
CTR srtPortAREInFrames	1.3.6.1.4.1.2926.25.3.2.3.1.8	Counter	read-only	The number of all paths explorer frames that have been received by this port from its segment.
CTR srtPortAREOutFrames	1.3.6.1.4.1.2926.25.3.2.3.1.9	Counter	read-only	The number of all paths explorer frames that have been transmitted by this port on its segment.
CTR srtPortSteInFrames	1.3.6.1.4.1.2926.25.3.2.3.1.10	Counter	read-only	The number of spanning tree explorer frames that have been received by this port from its segment.
CTR srtPortSteOutFrames	1.3.6.1.4.1.2926.25.3.2.3.1.11	Counter	read-only	The number of spanning tree explorer frames that have been transmitted by this port on its segment.
CTR srtPortSegmentMismatchDiscards	1.3.6.1.4.1.2926.25.3.2.3.1.12	Counter	read-only	The number of explorer frames that have been discarded by this port because the routing descriptor field contained an invalid adjacent segment value.
CTR srtPortDuplicateSegmentDiscards	1.3.6.1.4.1.2926.25.3.2.3.1.13	Counter	read-only	The number of frames that have been discarded by this port because the routing descriptor field contained a duplicate segment identifier.
CTR srtPortHopCountExceededDiscards	1.3.6.1.4.1.2926.25.3.2.3.1.14	Counter	read-only	The number of explorer frames that have been discarded by this port because the Routing Information Field has exceeded the maximum route descriptor length.
srtSourceRouteTable	1.3.6.1.4.1.2926.25.3.2.4		not-accessible	This table contains a list of stored destination address and the routing information fields which will be inserted in frames sent to those destinations.
srtSourceRouteEntry	1.3.6.1.4.1.2926.25.3.2.4.1		not-accessible	An source route entry.
INT srtSourceRouteVlanID	1.3.6.1.4.1.2926.25.3.2.4.1.1	INTEGER	read-only	This is the ID of the Vlan on which the address corresponding to this entry was learnt.
OCT srtSourceRouteAddress	1.3.6.1.4.1.2926.25.3.2.4.1.2	OCTET STRING	read-only	This is the source address which was stored when the Source Routing frame which contained it was processed by the SRTB. The address is in the form it was received from the ring network.
OCT srtSourceRouteRIF	1.3.6.1.4.1.2926.25.3.2.4.1.3	OCTET STRING	read-only	This object contains all the routing information which was extracted from the received Source Routed frame. The data is in the form it was received from the ring network
INT srtSourceRouteType	1.3.6.1.4.1.2926.25.3.2.4.1.4	INTEGER	read-only	This object represents the type of the entry. If the value returned is sameRing (1), then this indicates that the frame from which this entry was taken originated on our local ring. A value of locked (2) is used for entries which have been learned from ARE type frames. The value provisional(3)is used for frames which have been learned from STE frames and the responsWithARE (4) values is used to indicate that when a response is sent to this entry's address is should be sent as an ARE frame.
INT srtSourceRouteDirection	1.3.6.1.4.1.2926.25.3.2.4.1.5	INTEGER	read-only	If this object returns a value of inOrder(0), then this means that the D bit is zero and that the frame traverses the LANs in the order in which they are specified in the routing information field. Conversely, if the D bit is set to 1 the frame will traverse the LANs in the reverse order. The D bit is meaningful only or source routed frames (SRF). For STE and ARE frames the D bit is ignored and is not altered by the unit.

RFC description

Manages Source Routing and Translational bridging objects for Sonoma bridging products.

Start monitoring Sonoma Systems switch product line, source-routing/translational bridging capable (Token Ring source-route status) with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.

Download SONOMASYSTEMS-SONOMA-SRTB-MIB

What Is SONOMASYSTEMS-SONOMA-SRTB-MIB?

Supported Devices

Monitoring Examples

What Can Be Monitored

This MIB depends on

Related MIBs

RFC description