Table Of Contents
T3 Maintenance Data Link Messages on the Cisco 7304 Router
Related Features and Technologies
Supported Standards, MIBs, and RFCs
Enabling and Configuring MDL Messaging
Verifying Local and Remote MDL Message Information
Enabling and Configuring MDL Messaging Example
Verifying Local and Remote MDL Information Example
T3 Maintenance Data Link Messages on the Cisco 7304 Router
Feature History
Release Modification12.1(13)EX
This feature was introduced on the Cisco 7304 router.
12.2(18)S
This feature was introduced on Cisco 7304 routers running Cisco IOS Release 12.2 S.
This document describes the T3 Maintenance Data Link Messages on the Cisco 7304 Router feature and includes information on the benefits of the new feature, supported platforms, configuration tasks and a command reference.
This document includes the following sections:
•
Supported Standards, MIBs, and RFCs
Feature Overview
This feature introduces the ability to send and receive MDL messages on Cisco 7304 T3 interfaces.
MDL messages are used to communicate identification information between local and remote ports. The type of information included in MDL messages includes the equipment identification code (EIC), location identification code (LIC), frame identification code (FIC), unit, Path Facility Identification (PFI), port number, and Generator Identification numbers. The values for each piece of MDL message identification can be defined only by a network administrator and are discussed in ANSI T1.107.
Related Features and Technologies
Clear Channel 6-port T3 (DS3) line card
Related Documents
•
Clear Channel 6-Port T3 (DS3) Line Card Installation and Configuration document for the Cisco 7304 router
•
"Configuring Serial Interfaces" chapter of Cisco IOS Interface Configuration Guide, Release 12.1
•
Cisco IOS Interface Command Reference, Release 12.1
Supported Platforms
Although implementation of MDL on the Cisco 7304 router is similar across most Cisco platforms, this documentation only covers MDL on the Cisco 7304 router.
Determining Platform Support Through Cisco Feature Navigator
Cisco IOS software is packaged in feature sets that support specific platforms. To get updated information regarding platform support for this feature, access Cisco Feature Navigator. Cisco Feature Navigator dynamically updates the list of supported platforms as new platform support is added for the feature.
Cisco Feature Navigator is a web-based tool that enables you to quickly determine which Cisco IOS software images support a specific set of features and which features are supported in a specific Cisco IOS image. You can search by feature or release. Under the release section, you can compare releases side by side to display both the features unique to each software release and the features in common.
Cisco Feature Navigator is updated regularly when major Cisco IOS software releases and technology releases occur. For the most current information, go to the Cisco Feature Navigator home page at the following URL:
Supported Standards, MIBs, and RFCs
Standards
MDL messaging is defined in ANSI T1.107.
MIBs
No new or modified MIBs are supported by this feature.
RFCs
No new or modified RFCs are supported by this feature.
Prerequisites
C-bit framing has to be enabled in order to transport MDL messages between source and destination T3 ports.
This specific feature only works on Cisco 7304 interfaces using a T3 line card. For information on MDL messaging on another platform, check the IOS and line card documentation for that platform.
Configuration Tasks
See the following sections for configuration tasks for the MDL Messages on the Cisco 7304 feature:
•
Enabling and Configuring MDL Messaging
•
Verifying Local and Remote MDL Message Information, page 5
Enabling and Configuring MDL Messaging
All information that is transmitted using MDL messages is user-configurable. The same command used to configure the information in MDL messages is also used to enable MDL messaging.
To enable MDL messaging or to configure the information contained in the MDL messages, enter the following commands:
Verifying Local and Remote MDL Message Information
The following command can be used to verify MDL information on the local router and to view incoming MDL information from devices transmitting to the local router:
Command PurposeRouter#show controllers serial slot/interface-numberShows the status of the controller, including local and remote MDL information.
Configuration Example
This section provides the following configuration examples:
•
Enabling and Configuring MDL Messaging Example
•
Verifying Local and Remote MDL Information Example
Enabling and Configuring MDL Messaging Example
In the following example, the local MDL information for idle signal and test signal MDL messages is configured and MDL messaging is enabled.
interface Serial4/2ip address 60.0.0.1 255.0.0.0no keepaliveclock source internalmdl string eic EIC_4_2mdl string lic LIC_4_2mdl string fic FIC_4_2mdl string unit U_4_20mdl string pfi PFI_4_2mdl string port PORT_4_2mdl string generator GEN_4_2mdl transmit pathmdl transmit idle-signalmdl transmit test-signalVerifying Local and Remote MDL Information Example
In the following example, the local and remote MDL information is gathered using the show controllers command. In this particular example, the MDL information includes information related to path signals, idle signals, and test signals.
Router# show controllers serial 4/2Interface Serial4/2 (DS3 port 2)Line state is uprxLOS inactive, rxLOF inactive, rxAIS inactivetxAIS inactive, rxRAI inactive, txRAI inactiveCurrent configurable parameter settings:Loopback is none, Framing is c-bitClock source is internal, Cable length is 50DSU mode is cisco, DSU bandwidth limit is 44210Payload scrambling is disabled, CRC is 16Bert pattern is disabled, Bert interval is 0 minutesTransmitter delay is 0, Encapsulation is HDLCIdle character is flags, Invert data is disabledRemote fullrate has no request outstandingRemote accept is enabled, MTU is 4470MIB information:Data in current interval (86 seconds elapsed):0 Line Code Violations, 0 P-bit Coding Violations0 C-bit Coding Violations0 P-bit Err Secs, 0 P-bit Sev Err Secs0 Sev Err Framing Secs, 0 Unavailable Secs0 Line Errored Secs, 0 C-bit Errored Secs, 0 C-bit Sev Err SecsNo alarms detected.0 Sev Err Line Secs, 0 Far-End Err Secs, 0 Far-End Sev Err Secs0 P-bit Unavailable Secs, 0 CP-bit Unavailable Secs0 CP-bit Far-end Unavailable Secs0 Near-end path failures, 0 Far-end path failures0 Far-end code violationsMDL transmission is enabledLocal MDL Information:EIC:EIC_4_2, LIC:LIC_4_2, FIC:FIC_4_2, UNIT:U_4_20Path FI:PFI_4_2Idle Signal PORT_NO:PORT_4_2Test Signal GEN_NO:GEN_4_2Far-End MDL Information:EIC:EIC_4_3, LIC:LIC_4_3, FIC:FIC_4_3, UNIT:U_4_3Path FI:PFI_4_3Idle Signal PORT_NO:PORT_4_3Test Signal GEN_NO:GEN_4_3...Command Reference
This section documents the modified commands in this feature. All other commands used with this feature are documented in the Cisco IOS Release 12.1 configuration guide and command reference publications.
•
mdl
mdl
To configure the Maintenance Data Link (MDL) message defined in the ANSI T1.107a-1990 specification, use the mdl command in interface configuration mode. To remove the message, use the no form of this command.
mdl {transmit {path | idle-signal | test-signal} | string {eic | lic | fic | unit | pfi | port | generator} string}
no mdl {transmit {path | idle-signal | test-signal} | string {eic | lic | fic | unit | pfi | port | generator} string}
Syntax Description
Defaults
No MDL message is configured unless the mdl command is entered.
Command Modes
Interface configuration
Command History
Examples
In the following example, the local MDL information for idle signal and test signal MDL messages is configured and MDL messaging is enabled.
interface Serial4/2ip address 60.0.0.1 255.0.0.0no keepaliveclock source internalmdl string eic EIC_4_2mdl string lic LIC_4_2mdl string fic FIC_4_2mdl string unit U_4_20mdl string pfi PFI_4_2mdl string port PORT_4_2mdl string generator GEN_4_2mdl transmit pathmdl transmit idle-signalmdl transmit test-signal
In the following example, the local and remote MDL information is gathered using the show controllers command.
Router# show controllers serial 4/2Interface Serial4/2 (DS3 port 2)Line state is uprxLOS inactive, rxLOF inactive, rxAIS inactivetxAIS inactive, rxRAI inactive, txRAI inactiveCurrent configurable parameter settings:Loopback is none, Framing is c-bitClock source is internal, Cable length is 50DSU mode is cisco, DSU bandwidth limit is 44210Payload scrambling is disabled, CRC is 16Bert pattern is disabled, Bert interval is 0 minutesTransmitter delay is 0, Encapsulation is HDLCIdle character is flags, Invert data is disabledRemote fullrate has no request outstandingRemote accept is enabled, MTU is 4470MIB information:Data in current interval (86 seconds elapsed):0 Line Code Violations, 0 P-bit Coding Violations0 C-bit Coding Violations0 P-bit Err Secs, 0 P-bit Sev Err Secs0 Sev Err Framing Secs, 0 Unavailable Secs0 Line Errored Secs, 0 C-bit Errored Secs, 0 C-bit Sev Err SecsNo alarms detected.0 Sev Err Line Secs, 0 Far-End Err Secs, 0 Far-End Sev Err Secs0 P-bit Unavailable Secs, 0 CP-bit Unavailable Secs0 CP-bit Far-end Unavailable Secs0 Near-end path failures, 0 Far-end path failures0 Far-end code violationsMDL transmission is enabledLocal MDL Information:EIC:EIC_4_2, LIC:LIC_4_2, FIC:FIC_4_2, UNIT:U_4_20Path FI:PFI_4_2Idle Signal PORT_NO:PORT_4_2Test Signal GEN_NO:GEN_4_2Far-End MDL Information:EIC:EIC_4_3, LIC:LIC_4_3, FIC:FIC_4_3, UNIT:U_4_3Path FI:PFI_4_3Idle Signal PORT_NO:PORT_4_3Test Signal GEN_NO:GEN_4_3....
