ASCEND-MIBDEBUG-MIB

All MIBs › ASCEND-MIBDEBUG-MIB

Category: Device Management, Vendor: Ascend/Lucent

Description: Provides debug and diagnostic control objects for troubleshooting Ascend access equipment.

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 ASCEND-MIBDEBUG-MIB?

This proprietary Ascend Communications MIB provides debug and diagnostic control objects used for troubleshooting Ascend access equipment in the field or lab. It exposes configuration-style data for enabling diagnostic tracing, debug logging levels, and related troubleshooting controls rather than steady-state operational counters. Its role in monitoring is indirect but software-status related — enabling or checking debug settings helps an engineer confirm what level of diagnostic logging is active on the device while investigating an existing hardware or software fault, rather than being a source of ongoing health metrics itself. It is a vendor-proprietary utility MIB with no dependency on IETF standards, intended purely as an Ascend engineering/support tool. It was deployed on legacy Ascend/Lucent access equipment, primarily by vendor support or field engineers troubleshooting device issues, who could download the ASCEND-MIBDEBUG-MIB file to load into a MIB browser when needed.

IPNetwork Monitor allows you to monitor SNMP objects defined in ASCEND-MIBDEBUG-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

legacy Ascend access equipment

Monitoring Examples

No specific object or table names were included in the sampled instrumentation for this module, so a concrete polling example can't be tied to real OIDs; in general, a support engineer would check or set debug/diagnostic trace-level objects to increase logging detail while investigating an active fault on the device, then verify the debug configuration reverted to normal afterward.

What Can Be Monitored

diagnostic/debug trace level
troubleshooting control flags

Imported Objects

From ASCEND-MIB

configuration

OBJECT-IDENTITY

From RFC-1212

OBJECT-TYPE

From RFC1155-SMI

IpAddress

OIDs

OID symbolic	OID numeric	Type	Access	Description
mibdebugProfile	1.3.6.1.4.1.529.23.72
mibdebugProfileTable	1.3.6.1.4.1.529.23.72.1		not-accessible	A list of mibdebugProfile profile entries.
mibdebugProfileEntry	1.3.6.1.4.1.529.23.72.1.1		not-accessible	A mibdebugProfile entry containing objects that maps to the parameters of mibdebugProfile profile.
INT debugProfile_Shelf_o	1.3.6.1.4.1.529.23.72.1.1.1	INTEGER	read-only
INT debugProfile_Slot_o	1.3.6.1.4.1.529.23.72.1.1.2	INTEGER	read-only
INT debugProfile_Item_o	1.3.6.1.4.1.529.23.72.1.1.3	INTEGER	read-only
INT debugProfile_PhysicalAddress_Shelf	1.3.6.1.4.1.529.23.72.1.1.4	INTEGER	read-write	The number of the shelf that the addressed physical device resides on.
INT debugProfile_PhysicalAddress_Slot	1.3.6.1.4.1.529.23.72.1.1.5	INTEGER	read-write	The number of the slot that the addressed physical device resides on.
INT debugProfile_PhysicalAddress_ItemNumber	1.3.6.1.4.1.529.23.72.1.1.6	INTEGER	read-write	A number that specifies an addressable entity within the context of shelf and slot.
INT debugProfile_Active	1.3.6.1.4.1.529.23.72.1.1.7	INTEGER	read-write	Setting this field to Yes enables this profile. Setting this field to No disables this entire profile.
INT debugProfile_EnableCoreDump	1.3.6.1.4.1.529.23.72.1.1.8	INTEGER	read-write	Core dump on system failure can be enabled by setting this field to Yes. Core dumps are disabled if this field is No.
STR debugProfile_CoreDumpServer	1.3.6.1.4.1.529.23.72.1.1.9	DisplayString	read-write	The name (or IP address) of the host setup to receive our core dumps.
INT debugProfile_EnableGdb	1.3.6.1.4.1.529.23.72.1.1.10	INTEGER	read-write	GDB can be enabled by setting this field to Yes. GDB is disabled if this field is No.
STR debugProfile_GdbHost	1.3.6.1.4.1.529.23.72.1.1.11	DisplayString	read-write	The name (or IP address) of the host running GDB.
INT debugProfile_CsTracking	1.3.6.1.4.1.529.23.72.1.1.12	INTEGER	read-write	csTracking can be enabled by setting this field to Yes. csTracking is disabled if this field is No.
INT debugProfile_GenericField	1.3.6.1.4.1.529.23.72.1.1.13	INTEGER	read-write	This field can be used as a generic bitmask stored in nonvolatile memory and thus preserved over resets and powerdowns
INT debugProfile_MinWarningCoreDump	1.3.6.1.4.1.529.23.72.1.1.14	INTEGER	read-write	Minimum value for a range of warning numbers that will generate a core dump (a core dump is taken for warnings between the minimum and maximum warning numbers inclusive) if coredumps are enabled. The default value of 0 in the minimum and maximum fields mean that only warnings from 101 to 121 will cause a core dump.
INT debugProfile_MaxWarningCoreDump	1.3.6.1.4.1.529.23.72.1.1.15	INTEGER	read-write	Maximum value for a range of warning numbers that will generate a core dump (a core dump is taken for warnings between the minimum and maximum warning numbers inclusive) if coredumps are enabled. The default value of 0 in the minimum and maximum fields mean that only warnings from 101 to 121 will cause a core dump.
INT debugProfile_CoreDumpLocation	1.3.6.1.4.1.529.23.72.1.1.16	INTEGER	read-write	Core dumps will go to the specified location if enabled.
INT debugProfile_FlashCoreOverwrite	1.3.6.1.4.1.529.23.72.1.1.17	INTEGER	read-write	A previous flash dump will be overwritten by a new dump if this field to Yes, but will be preserved if this field is No.
INT debugProfile_Action_o	1.3.6.1.4.1.529.23.72.1.1.18	INTEGER	read-write
INT debugProfile_CoreDumpRipUpdate	1.3.6.1.4.1.529.23.72.1.1.19	INTEGER	read-write	RIP updates will be sent accordingly based on the setting here during coredump.
IP debugProfile_CoredumpSourceAddress	1.3.6.1.4.1.529.23.72.1.1.20	IpAddress	read-write	The coredump source ip address for the shelf card. It is usually set only if the system-ip-address and the coredump server ip address belong to different networks.

RFC description

Ascend mibdebug MIB for managing debug profiles and core dump configuration on network devices.

Start monitoring Ascend Communications (Lucent) MAX/Pipeline/TNT WAN access equipment (legacy) 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 ASCEND-MIBDEBUG-MIB

What Is ASCEND-MIBDEBUG-MIB?

Supported Devices

Monitoring Examples

What Can Be Monitored

This MIB depends on

Related MIBs

RFC description