All MIBs › Transport-Subsystem-MIB
Organization: ISMS Working Group
Last Updated: 2006-10-06
Description: Defines SNMP Transport Subsystem MIB objects for managing secure transport model sessions and parameters between SNMP engines
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 Transport-Subsystem-MIB?
The Transport Subsystem MIB is an IETF standards-track module (drafted alongside RFC work on SNMP security, related to the Transport Security Model) that defines managed objects for the SNMP engine's transport subsystem rather than for any physical device. It exposes configuration and session data about secure transport sessions and parameters used between cooperating SNMP engines, such as transport model identifiers and session counters. It is not a hardware/software device-health MIB in the traditional sense; instead it is used to monitor and manage the SNMP protocol stack's own transport-security state, such as active/failed secure sessions, which indirectly reflects the health of the management channel itself. It is explicitly dependent on companion SNMPv3 security architecture RFCs (the Transport Security Model and related USM/session MIBs) referenced in its copyright header. It is deployed wherever SNMPv3 with a secure transport model (e.g., SSH or TLS transport) is used to manage devices, primarily on the managing/managed SNMP engines themselves rather than on end-user hardware. Engineers implementing or auditing this functionality typically reference the Transport-Subsystem-MIB RFC/standard documentation for the authoritative specification.
IPNetwork Monitor allows you to monitor SNMP objects defined in Transport-Subsystem-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
- vendor-neutral, standards-based MIB, not tied to a specific manufacturer; applies to SNMP engines/agents supporting secure transport models
Monitoring Examples
No sample objects were supplied for this module, so concrete object names cannot be cited; based on its stated purpose, an operator would expect tables tracking secure transport sessions and per-session parameters between SNMP engines. Monitoring would focus on session establishment/failure counts to detect misconfigured or failing secure transport channels. Because the MIB text itself notes it is a draft tied to an RFC placeholder, exact object names should be confirmed against the finalized RFC/MIB source.
Imported Objects
From SNMP-FRAMEWORK-MIB
| SnmpAdminString | |
| SnmpEngineID | |
| SnmpSecurityLevel | |
| SnmpSecurityModel |
From SNMPv2-CONF
| MODULE-COMPLIANCE | |
| OBJECT-GROUP |
From SNMPv2-SMI
| Gauge32 | |
| Integer32 | |
| MODULE-IDENTITY | |
| OBJECT-TYPE | |
| Unsigned32 | |
| mib-2 |
From SNMPv2-TC
| RowStatus | |
| StorageType | |
| TestAndIncr |
| TransportAddress | |
| TransportAddressType |
OIDs
RFC description
Manages SNMP transport subsystem configuration including security models and transport addresses.
Start monitoring vendor-neutral, standards-based MIB, SNMP engines/agents supporting secure transport models (secure-session count/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.