CLAB-ANI-DEV-MIB

All MIBs › CLAB-ANI-DEV-MIB

Organization: Cable Television Laboratories, Inc.

Last Updated: 2017-04-27

Category: DOCSIS and Cable

Description: Manages CableLabs Access Network Interface (ANI) device configuration and status for DOCSIS networks.

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 CLAB-ANI-DEV-MIB?

CLAB-ANI-DEV-MIB is a CableLabs (DOCSIS ecosystem) MIB defining management objects for sRouter devices under the Access Network Independent (ANI) project, used by cable-modem/gateway devices sitting behind a DOCSIS cable modem. It exposes device-level control (a remote reset action) and a logging subsystem covering log buffer size, per-severity and per-group logging controls, and a table of individual logged events. Its monitoring emphasis is software/fault status: an operator can trigger or track a device reset, control how much and what kind of event logging occurs, and inspect the event log table to diagnose device or service problems on the residential/business gateway. As a CableLabs specification MIB, it is designed to be used alongside other DOCSIS-related MIBs (such as DOCS-CABLE-DEVICE-MIB) that describe the cable-modem side of the same device. It is deployed on cable-operator-provisioned residential and small-business gateway/sRouter devices in DOCSIS access networks. Engineers can download the CLAB-ANI-DEV-MIB file directly to load it into their MIB browser.

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

DOCSIS cable gateway/sRouter devices

Monitoring Examples

An operator would poll aniDevSysLoggingEventTable/aniDevSysLoggingEventEntry, indexed by aniDevSysLoggingEventIndex, to review recent logged events when a subscriber reports connectivity problems, and could adjust aniDevSysLoggingLevelCtrl or aniDevSysLoggingGroupCtrl to increase logging detail for a specific subsystem during troubleshooting. If aniDevSysLoggingSize is near its limit, older events may be getting overwritten before they can be reviewed. Setting aniDevResetNow lets a technician remotely reboot a misbehaving gateway without a truck roll, and aniDevLoggingCtrlReset lets them clear accumulated log noise afterward.

What Can Be Monitored

device reset trigger
logging buffer size/utilization
per-severity logging level
per-group logging control
logged event history

Imported Objects

From CLAB-DEF-MIB

clabCommonMibs

OBJECT-IDENTITY

From SNMP-FRAMEWORK-MIB

SnmpAdminString

From SNMPv2-CONF

MODULE-COMPLIANCE
OBJECT-GROUP

From SNMPv2-SMI

Integer32
MODULE-IDENTITY
OBJECT-TYPE

From SNMPv2-TC

DateAndTime
TruthValue

OIDs

OID symbolic	OID numeric	Type	Access	Description
clabAniDevMib	1.3.6.1.4.1.4491.4.7			This MIB module contains the management objects for sRouter devices under the CableLabs Access Network Independent (ANI) project. Copyright 1999-2017 Cable Television Laboratories, Inc. All rights reserved.
clabAniDevObjects	1.3.6.1.4.1.4491.4.7.1
T/F aniDevResetNow	1.3.6.1.4.1.4491.4.7.1.1	TruthValue	read-write	Setting this object to true(1) causes the device to reset. Reading this object always returns false(2).
clabAniDevSysLoggingObjects	1.3.6.1.4.1.4491.4.7.1.2
INT aniDevLoggingCtrlReset	1.3.6.1.4.1.4491.4.7.1.2.1	INTEGER	read-write	Setting this object to resetLog(1) empties the logging table. Setting this object to pauseLog(2) causes the ANI device to stop writing events to the logging table. Setting this object to startLog(3) causes the ANI device to start writing events to the logging table. Reading this object returns either pauseLog(2) or startLog(3). The default is startLog(3). Log event pausing is independent of any other log filtering mechanisms, e.g., levels. Setting it to useDefaultReporting(4) resets the log (i.e., empties) and returns all event levels to the factory-default reporting.
U32 aniDevSysLoggingSize	1.3.6.1.4.1.4491.4.7.1.2.2	Unsigned32	read-write	Setting this object modifies the size of the system logging table. When set to zero, all entries are removed and new entries are not allowed to be added. When set less than the current size, the oldest entries are removed until the new size is reached.
INT aniDevSysLoggingLevelCtrl	1.3.6.1.4.1.4491.4.7.1.2.3	INTEGER	read-write	The current logging priority level for system messages. Setting a level sets all levels from the level specified to the highest severity level except for �off�. The level �all� indicates all levels. The log levels are derived from the log4j class. all(1) The all level has the lowest possible rank and is intended to turn on all logging. trace(2) The trace level designates finer-grained informational events than the DEBUG (see log4j class for further definition). debug(3) The debug level designates fine-grained informational events that are most useful to debug an application. info(4) The info level designates informational messages that highlight the progress of the application at coarse-grained level. warn(5) The warn level designates potentially harmful situations. error(6) The error level designates error events that might still allow the application to continue running. fatal(7) The fatal level designates very severe error events that will presumably lead the application to abort. off(8) The off has the highest possible rank and is intended to turn off logging.
BIT aniDevSysLoggingGroupCtrl	1.3.6.1.4.1.4491.4.7.1.2.4	Bits	read-write	The system 'group' or 'groups' to be logged. If all(1) is set, then other bits are ignored. If set to 'none(0)', messages that do not include a 'group' are candidates to be logged. Logging Groups for Event Logs are defined in the controlling Access Network Independent device specification for equipment implementing this MIB. Returns WrongValue error if an attempt is made to set the bit for a Logging Group not supported by the device.
aniDevSysLoggingEventTable	1.3.6.1.4.1.4491.4.7.1.2.5		not-accessible	This table is a cyclic table of events.
aniDevSysLoggingEventEntry	1.3.6.1.4.1.4491.4.7.1.2.5.1		not-accessible	A logging event entry.
U32 aniDevSysLoggingEventIndex	1.3.6.1.4.1.4491.4.7.1.2.5.1.1	Unsigned32	not-accessible	Provides relative ordering of the objects in the event log. This object will always increase except when (a) the log is reset via aniDevSysLoggingEventCtrlReset or (b) the device reboots and does not implement non-volatile storage for this log. The next entry for all the above cases is 1.
DAT aniDevSysLoggingEventTimeStamp	1.3.6.1.4.1.4491.4.7.1.2.5.1.2	DateAndTime	read-only	The time stamp of this event logging entry. The timestamp is established when the event occurs.
STR aniDevSysLoggingEventMessage	1.3.6.1.4.1.4491.4.7.1.2.5.1.3	SnmpAdminString	read-only	The event message.
clabAniDevConformance	1.3.6.1.4.1.4491.4.7.2
clabAniDevCompliances	1.3.6.1.4.1.4491.4.7.2.1
clabAniDevCompliance	1.3.6.1.4.1.4491.4.7.2.1.1			The compliance statement for CableLabs ANI devices.
clabAniDevGroups	1.3.6.1.4.1.4491.4.7.2.2
clabAniDevGroup	1.3.6.1.4.1.4491.4.7.2.2.1			Object(s) implemented for the management of ANI devices.

RFC description

Vendor-private MIB for CableLabs ANI (Access Network Interface) devices; defines management objects for cable access equipment.

Start monitoring DOCSIS cable gateway/sRouter devices 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 CLAB-ANI-DEV-MIB

What Is CLAB-ANI-DEV-MIB?

Supported Devices

Monitoring Examples

What Can Be Monitored

This MIB depends on

Related MIBs

RFC description