ST2-MIB

MIB Reference — IPNetwork Monitor · Updated October 06, 2026

All MIBs › ST2-MIB

Category: Generic / Unclassified

Description: Manages ST2 device configuration, interface parameters, and operational status objects.

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 ST2-MIB?

ST2-MIB is a Wellfleet (Bay Networks) vendor MIB — its OID root, stii, hangs off wfSt2Group imported from Wellfleet-ST2-MIB — that configures and reports on a router's implementation of ST-II, the Stream Protocol (RFC 1190), a resource-reservation protocol for real-time data streams. It exposes identification objects (st2AgentCopyright, st2ProtoVersion, st2FlowSpecVersion, st2AgentType indicating end-system/intermediate-system role, st2RoutingDerived), and a family of matched timeout/retry-count pairs governing each ST-II control message type — st2ToAccept/st2NAccept, st2ToConnect/st2NConnect, st2ToDisconnect/st2NDisconnect, st2ToHidAck/st2NHidAck, st2ToHidChange/st2NHidChange, st2ToNotify/st2NNotify, and st2ToRefuse/st2NRefuse. These objects reveal how aggressively the router retries ST-II control handshakes (ACCEPT, CONNECT, DISCONNECT, HID-CHANGE, NOTIFY, REFUSE) before giving up, which is central to diagnosing failed or flapping ST-II stream setups. It depends on RFC1155-SMI, RFC-1212, and RFC1213-MIB base types plus Wellfleet's own ST2 group definition. Network engineers troubleshooting ST-II reservations on Wellfleet routers can consult ST2-MIB RFC background (RFC 1190) alongside this MIB to tune its retry timers correctly.

IPNetwork Monitor allows you to monitor SNMP objects defined in ST2-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

  • Wellfleet (Bay Networks) routers implementing ST-II (Stream Protocol, RFC 1190)

Monitoring Examples

An operator polls st2ToConnect and st2NConnect to see the current hop-by-hop CONNECT timeout and retry count, then correlates repeated timeouts with failed stream setups; a high number of CONNECT retries with no successful stream establishment would point to a downstream router failing to acknowledge ST-II CONNECT messages.

What Can Be Monitored

  • ST-II agent type and protocol/flow-spec version
  • CONNECT/ACCEPT/DISCONNECT timeout and retry counters
  • HID-CHANGE and HID-CHANGE-REQUEST timeout and retry counters
  • NOTIFY and REFUSE timeout and retry counters
  • routing-source configuration for ST-II
Imported Objects

From RFC-1212

OBJECT-TYPE

From RFC1155-SMI

Counter
Gauge
IpAddress
TimeTicks

From RFC1213-MIB

DisplayString

From Wellfleet-ST2-MIB

wfSt2GroupOBJECT-IDENTITY
OIDs

RFC description

RFC 1190 ST-II (Stream Protocol II) MIB for managing stream protocol configuration, flow specifications, and agent information on ST-II capable systems.

Start monitoring Wellfleet (Bay Networks) router implementing ST-II Stream Protocol (RFC 1190) 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 ST2-MIB