All MIBs › URI-TC-MIB
Organization: IETF Operations and Management (OPS) Area
Last Updated: 2007-09-10
Category: Textual Conventions and Registries
Description: Defines textual conventions for representing Uniform Resource Identifiers (URIs) in SNMP MIB modules.
IPNetwork Monitor uses several OIDs from this MIB in network discovery and polling the applicable devices. Start monitoring URI-TC-MIB with a free 30-day trial of IPNetwork Monitor.
What Is URI-TC-MIB?
URI-TC-MIB is a vendor-neutral IETF standards-track MIB (defined per RFC 3986/STD 66) that defines textual conventions for representing Uniform Resource Identifiers within other SNMP MIB modules, rather than exposing any device data of its own. It contains no object instances, tables, or notifications; its sole content is type definitions (e.g., a Uri textual convention) that other MIBs import to declare URI-valued objects in a standard, size-bounded string format. As a result it has no direct role in monitoring hardware or software status itself, since it is purely a shared data-type definition module used by other MIBs. Its entire purpose is dependency: it exists to be imported by other MIB modules (such as those for HTTP servers, printers, or web-management interfaces) that need to represent a URI-typed object consistently. It is deployed implicitly, wherever a compliant SNMP agent implements another MIB that imports and uses the Uri textual convention, as standardized in the URI-TC-MIB RFC (RFC 3986/STD 66).
IPNetwork Monitor allows you to monitor SNMP objects defined in URI-TC-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; supports any SNMP-managed device whose other MIBs need a URI-typed object
Monitoring Examples
This module defines no runtime data objects or tables of its own, and no sample_objects were provided, so there is no monitoring scenario to describe; it is a conformance/textual-convention support module. Its practical use is entirely indirect: any MIB (e.g., one exposing a device's configuration or management web-page URL) that imports the Uri textual convention from this module will render that URI-valued object using the octet-string format standardized here.
Imported Objects
From SNMPv2-SMI
| MODULE-IDENTITY | |
| mib-2 |
From SNMPv2-TC
| TEXTUAL-CONVENTION |
OIDs
RFC description
Textual conventions for representing Uniform Resource Identifiers (URIs) as defined by RFC 3986 and RFC 5017.
Start monitoring vendor-neutral, standards-based MIB, any SNMP-managed device whose other MIBs need a URI-typed object (shared textual conventions, no data objects) 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.