CISCO-XDSL-LINE-MIB
The CISCO-XDSL-LINE-MIB provides vendor-specific, technology-agnostic managed objects for monitoring and configuring the physical layer parameters of Cisco xDSL modems (including ADSL, SDSL, and IDSL) across both Central Office (XTU-C) and Remote (XTU-R) transceivers. This module extends standard line MIBs by exposing generic configuration profiles and performance metrics such as Bit Error Ratio (BER) and Digital Signal Processor (DSP) status that are not covered by vendor-specific or technology-specific MIBs.
Imported Objects
Objects
34 total| Object Name |
|---|
ciscoXdslLineMIB OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.204 |
RFC1155-SMI Unknown .1.3.6.1.4.1.9.9.204 |
ciscoXdslLineMIBObjects OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.204.1 |
cXdslLineTableThis table contains enterprise-specific line parameters
for XTU-C class xDSL devices supported by the system. SEQUENCE OF CXdslLineEntry .1.3.6.1.4.1.9.9.204.1.1 |
cXdslLineEntryA set of enterprise-specific xDSL line parameters for an
XTU-C class device.
There exists an entry for each ifEntry with an ifType of
xDSL such as adsl, sdsl, idsl, etc. that are supported by
the system. CXdslLineEntry .1.3.6.1.4.1.9.9.204.1.1.1 |
cXdslLineTimeSinceLastChangeRepresents the time elapsed since the status of this
interface was last changed.ro TimeTicks (SNMPv2-SMI) .1.3.6.1.4.1.9.9.204.1.1.1.1 |
cXdslLineNoOfChangesRepresents the number of changes of the interface status
since last reset of the agent or since a XTU-C modem was
installed.ro Counter .1.3.6.1.4.1.9.9.204.1.1.1.2 |
cXdslTestTableThis table contains enterprise-specific test
parameters initiated by the XTU-C class devices
supported by the system. SEQUENCE OF CXdslTestEntry .1.3.6.1.4.1.9.9.204.1.2 |
cXdslTestEntryA set of enterprise-specific test parameters for an
XTU-C class xDSL device.
There exists an entry for each ifEntry with an ifType of
xDSL such as adsl, sdsl, idsl, etc. that are supported by
the system. CXdslTestEntry .1.3.6.1.4.1.9.9.204.1.2.1 |
cXdslTestStatusRepresents status of the test per port. Once a test is
completed or aborted, the status remains at passed, failed,
or aborted until user clears it by setting cXdslTestTrigger
to clear or starts a new test.
This object will return 'passed' if there are no
cXdslTestBertErrors and no cXdslTestBertBitErrorsro Enumeration .1.3.6.1.4.1.9.9.204.1.2.1.1 |
cXdslTestTypeThe type of test to be performed. The test duration is
determined by cXdslTestTime.
All the test types inhibit the service on that line.
The agent will only change cXdslTestType, if no test is
active on the targeted port.
The XTU-C may support other test types that are not defined
in this mib, if such test is running this object will have
a value of 'other'.
cXdslTestTrigger will start the test when set to start.rw Enumeration .1.3.6.1.4.1.9.9.204.1.2.1.2 |
cXdslTestTriggerStarts, stops (aborts) a test in progress or clears the
test results. The agent will only start a new test, if no
test is active on the targeted port. The value of this
object returns 'ready' when read, the value cannot be set
to 'ready'.
The cXdslTestTrigger value affects cXdslTestStatus as
following:
value current TestStatus
-
start inactive/pass/fail/ active
aborted
stop active aborted
clear pass/fail/aborted inactive
All other combinations will result in error, for instance,
starting a test may fail due to a test already in progress.
Likewise, stopping a test NOT in progress will result in an
error.
The value of cXdslTestType, cXdslTestStatus and cXdslTestTime
will remain in the system until cleared or until the the agent
is reset.
When this object is set to 'clear' the test results are cleared,
cXdslTestType is set to none and cXdslTestStatus is set to
inactive. The 'old' test results will remain until completion
of a 'new' test if test results are not clearedrw Enumeration .1.3.6.1.4.1.9.9.204.1.2.1.3 |
cXdslTestTimeTest duration. Time interval between 1 - 30 minutes.rw INTEGER .1.3.6.1.4.1.9.9.204.1.2.1.4 |
cXdslTestBertErrorsErrors during BERT test.
The test will abort if any BERT errors occur.
Note: that even if there are no BERT errors the test can
still fail due to BertBitErrors.
Bit Description
-
0 No BERT errors
1 XTU-R BERT aborted
2 XTU-R lost sync during BERT
3 XTU-R never got in sync
4 No XTU-R BERT results
5 XTU-C BERT aborted
6 XTU-C lost sync during BERT
7 XTU-C never got in syncro OCTET STRING .1.3.6.1.4.1.9.9.204.1.2.1.5 |
cXdslTestBertBitErrorsThis value represents the number of BERT bit errors accumulated
during the test duration, the value may not be available
until completion of the test. The test will fail if this value
is greater than 0.ro Gauge .1.3.6.1.4.1.9.9.204.1.2.1.6 |
cXdslTestBertRunTimeThis value represents the BERT run time in seconds, the
value may not be available until completion of the test.ro INTEGER .1.3.6.1.4.1.9.9.204.1.2.1.7 |
cXdslTestBertBitRateThis value represents the BERT bitrate in bps that was
detected during the BERT test, the value may not be
available until completion of the test.ro INTEGER .1.3.6.1.4.1.9.9.204.1.2.1.8 |
cXdslModeTableThis table contains enterprise-specific mode
parameters initiated by the XTU-C class devices
supported by the system. SEQUENCE OF CXdslModeEntry .1.3.6.1.4.1.9.9.204.1.3 |
cXdslModeEntryA set of enterprise-specific mode parameters for an
XTU-C class xDSL device.
There exists an entry for each ifEntry with an ifType of
xDSL such as adsl, sdsl, idsl, etc. that are supported by
the system. CXdslModeEntry .1.3.6.1.4.1.9.9.204.1.3.1 |
cXdslModeLoopbackThe value of this object specifies the loopback mode of
this interface. The interface will stay in loopback mode
until this object is set to disabled.
The XTU-C may support other mode types that are not defined
in this mib, if such mode is running, this object will have
a value of 'other'.
The loopback modes will inhibit the service on that line.rw Enumeration .1.3.6.1.4.1.9.9.204.1.3.1.1 |
cXdslModeSpectrumThe value of this object specifies the spectrum mode of
this interface. The interface will stay in spectrum mode
until this object is set to disabled.
The modes will inhibit the service on that line.
Not all spectrum modes are avaiable for all types of modems.
The modes translate as follows:
sdsl & shdsl
spectrum1 = tx-1 spectrum2 = tx-3
spectrum3 = tx+1 spectrum4 = tx+3
spectrum5 = spec2PT spectrum6 = spec4PT
dmt
spectrum1 = reverb spectrum2 = medley
spectrum3 = pilot spectrum4 = not supported
spectrum5 = not supported spectrum6 = not supported
cap
spectrum1 = 136k spectrum2 = 340k
spectrum3 = 680k spectrum4 = 952k
spectrum5 = not supported spectrum6 = not supportedrw Enumeration .1.3.6.1.4.1.9.9.204.1.3.1.2 |
cXdslLineConfProfileTableThis table extends the adslLineConfProfileTable and contains
enterprise-specific xDSL configuration information. Entries in
this table apply to more than one type of DSL modems SEQUENCE OF CXdslLineConfProfileEntry .1.3.6.1.4.1.9.9.204.1.4 |
cXdslLineConfProfileEntryA configuration profile containing enterprise-specific xDSL
line configuration information.
An entry exist in this table for every profile created by
adslLineConfProfileRowStatus which will also modify or
delete an existing row in this table. CXdslLineConfProfileEntry .1.3.6.1.4.1.9.9.204.1.4.1 |
cXdslLineConfPayloadScrambledThis object specifies whether ATM Payload Scrambling
is enabled for this profile.rw TruthValue -- Rsyntax INTEGER { -- true(1), -- false(2) -- } .1.3.6.1.4.1.9.9.204.1.4.1.1 |
cXdslLineConfAlarmsEnabledThis object specifies whether Alarms are enabled for
this profile.rw TruthValue -- Rsyntax INTEGER { -- true(1), -- false(2) -- } .1.3.6.1.4.1.9.9.204.1.4.1.2 |
cXdslLineConfLinkUpDownTrapThis object specifies whether Link Up/Down traps
are enabled for this profile.rw TruthValue -- Rsyntax INTEGER { -- true(1), -- false(2) -- } .1.3.6.1.4.1.9.9.204.1.4.1.3 |
ciscoXdslLineMIBConformance OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.204.3 |
ciscoXdslLineMIBCompliances OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.204.3.1 |
ciscoXdslLineMIBCompliance OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.204.3.1.1 |
ciscoXdslLineMIBGroups OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.204.3.2 |
cXdslLineGroup OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.204.3.2.1 |
cXdslLineConfProfileGroup OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.204.3.2.2 |
cXdslTestGroup OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.204.3.2.3 |
cXdslModeGroup OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.204.3.2.4 |
More MIBs from Cisco
Browse all CiscoMIBs →The CISCO-ENTITY-VENDORTYPE-OID-MIB maps Cisco-specific hardware component identifiers to the ENTITY-MIB's entPhysicalTable, enabling precise differentiation of physical device types such as line cards, power supplies, and fans within Cisco infrastructure. This mapping ensures that SNMP management systems can accurately correlate physical inventory entries with vendor-specific component definitions for accurate device discovery and monitoring.
The CISCO-UNIFIED-COMPUTING-EQUIPMENT-MIB provides SNMP-based monitoring and management of Cisco Unified Computing System (UCS) hardware components, including chassis, blades, fabric interconnects, and power supplies. It exposes critical operational metrics such as device status, port states, temperature readings, fan speeds, and power consumption data for infrastructure health assessment.
The CISCO-UNIFIED-COMPUTING-ADAPTOR-MIB enables SNMP-based monitoring and management of physical and virtual network adapter interfaces, including link status, traffic counters, error statistics, and port configuration parameters, within the Cisco Unified Computing System (UCS) fabric interconnects and blade servers.
The CISCO-UNIFIED-COMPUTING-TC-MIB module defines standard textual conventions and data type definitions required for monitoring Cisco Unified Computing System (UCS) hardware components, including server blades, fabric interconnects, and chassis resources. These definitions enable consistent interpretation of specific UCS metrics such as power supply status, fan speeds, thermal readings, and port utilization across SNMP management applications.
The CISCO-UNIFIED-COMPUTING-FABRIC-MIB enables SNMP-based monitoring and management of the Cisco UCS Fabric Interconnects and associated fabric switching infrastructure, exposing metrics for port states, link utilization, error counters, and fabric topology status. It facilitates granular visibility into the physical and logical fabric layers, including uplink/downlink interfaces, VLAN configurations, and fabric failover conditions within the unified computing environment.
The STARENT-MIB module provides SNMP management and monitoring capabilities for Cisco ASR 5000 and ASR 5500 multimedia core platforms, specifically exposing metrics related to 2G/3G/4G and WiFi subscriber sessions, inline service states, and carrier-class high-availability status.