All MIBs › AE-TC
Category: Textual Conventions and Registries
Description: Defines textual conventions and common data types for a network equipment vendor MIB module suite.
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 AE-TC?
AE-TC is a textual-conventions-only support MIB for a network-equipment vendor's MIB suite, defining shared data types, enumerations, and formatting conventions rather than any managed objects of its own. It exposes no tables or scalars for direct monitoring — its purpose is purely to standardize types like status enumerations, string formats, or index conventions that other MIBs in the vendor's suite import and reuse. Because it has no managed objects, it plays no direct role in monitoring hardware or software status; its value is in enabling consistent representation of status/severity/state values used by the vendor's other operational MIBs. Every other module in the same vendor's suite that imports from AE-TC has a hard dependency on it, meaning AE-TC must be loaded first for those MIBs to compile or be understood correctly. It is deployed wherever the vendor's other functional MIBs are deployed, purely as a prerequisite support module, never polled on its own. Engineers implementing or auditing this functionality typically reference the AE-TC RFC/standard documentation for the authoritative specification.
IPNetwork Monitor allows you to monitor SNMP objects defined in AE-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 support module — not directly applicable to any device; used only as a dependency by other MIBs from the same equipment vendor
Monitoring Examples
A MIB compiler or NMS discovery tool loading any other MIB in this vendor's suite that references a shared severity or admin-state TEXTUAL-CONVENTION must first load AE-TC to resolve those imported type definitions. Since no sample objects or module description text were available, this MIB has no pollable OIDs of its own — an admin would never query AE-TC directly via SNMP GET. Instead, seeing a load/compile error referencing an unresolved type from AE-TC in another vendor MIB indicates this dependency file is missing from the MIB search path.
What Can Be Monitored
- no directly pollable objects (type-definition support module only)
Imported Objects
From SNMPv2-SMI
| Gauge32 |
From SNMPv2-TC
| TEXTUAL-CONVENTION |
RFC description
Defines textual conventions for CALIX Active Ethernet ONT equipment types and alarm classifications.
Start monitoring vendor support modules 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.