All MIBs › HCNUM-TC
Organization: IETF OPS Area
Last Updated: 2000-06-08
Category: Textual Conventions and Registries
Description:
Defines textual conventions (CounterBasedGauge64 and ZeroBasedCounter64) for representing high-capacity 64-bit numeric data types not natively supported by SMIv2.
Imported Objects
From SNMPv2-SMI
| Counter64 | |
| MODULE-IDENTITY | |
| mib-2 |
From SNMPv2-TC
| TEXTUAL-CONVENTION |
What Is HCNUM-TC?
HCNUM-TC is an IETF standards module that defines textual conventions for high-capacity numeric types -- specifically CounterBasedGauge64 and ZeroBasedCounter64 -- needed to represent large 64-bit counters and gauges that were not natively available in SMIv2. It is a foundational, vendor-neutral definitions module rather than one tied to a technology area, and it is used across many other MIBs (particularly high-speed interface and performance MIBs) that need 64-bit counting semantics. The module itself exposes no polling targets -- no interfaces, environment sensors, or fault conditions -- so it cannot reveal hardware or software status on its own. Its explicit purpose is as a shared dependency: any MIB tracking high-speed interface octets, packet counts, or other high-capacity gauges imports these conventions to avoid 32-bit counter wraparound, which is why the HCNUM-TC OID list contains nothing but the two textual-convention definitions themselves. It is deployed implicitly wherever high-throughput interfaces (Gigabit Ethernet and above) are monitored via SNMP.
IPNetwork Monitor allows you to monitor SNMP objects defined in HCNUM-TC. 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
- high-speed network devices with gigabit-and-above interfaces
Monitoring Examples
No sample runtime objects exist because HCNUM-TC defines only the CounterBasedGauge64 and ZeroBasedCounter64 textual conventions used as data types by other MIBs. An administrator would not poll this module directly; rather, an interface MIB using a 64-bit high-capacity counter (for example a high-speed interface octet counter) would be typed as CounterBasedGauge64, letting management tools avoid the wraparound problems of 32-bit counters on multi-gigabit links. This module is a supporting type-definitions dependency, not a monitoring target itself.
OIDs
| OID symbolic | OID numeric | Type | Access | Description |
|---|---|---|---|---|
| hcnumTC | 1.3.6.1.2.1.78 | High Capacity Numbers TC MIB. |
RFC description
IETF MIB defining high-capacity (64-bit) textual conventions for counters and gauges (RFC 2856).
Start monitoring Vendor-neutral high-speed network device, any manufacturer (64-bit counter textual conventions) 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.