Usage Guidelines

For the interface-path-id argument, use the following guidelines:

• If specifying a physical interface, the naming notation is rack/slot/module/port. The slash between values is required as part of the notation. An explanation of each component of the naming notation is as follows:

  • rack : Chassis number of the rack.

  • slot : Physical slot number of the line card.

  • module : Module number. A physical layer interface module (PLIM) is always 0.

  • port : Physical port number of the interface.

• If specifying a virtual interface, the number range varies, depending on interface type.

Note

Before you can start a BERT on an E1 controller or channel group, you must configure a BERT pattern using the bert pattern command. If desired, you can also adjust the default setting (1 minute) of the BERT interval using the bert interval command. Both of these commands are available in E1 configuration mode and channel group configuration mode.

To view the BERT results, use the show controllers e1 command in EXEC mode . The BERT results include the following information:

• Type of test pattern selected
• Status of the test
• Interval selected
• Time remaining on the BERT
• Total bit errors
• Total bits received

BERT is data intrusive. Regular data cannot flow on a line while the test is in progress. The line is put in an alarm state when a BERT is in progress and restored to a normal state after a BERT has been terminated.

Usage Guidelines

For the interface-path-id argument, use the following guidelines:

• If specifying a physical interface, the naming notation is rack/slot/module/port. The slash between values is required as part of the notation. An explanation of each component of the naming notation is as follows:

  • rack : Chassis number of the rack.

  • slot : Physical slot number of the line card.

  • module : Module number. A physical layer interface module (PLIM) is always 0.

  • port : Physical port number of the interface.

• If specifying a virtual interface, the number range varies, depending on interface type.

Note	Before you can start a BERT on an E3 controller, you must configure a BERT pattern using the bert pattern command. If desired, you can also adjust the default setting (1 minute) of the BERT interval using the bert interval command. Both of these commands are available in E3 configuration mode.

To view the BERT results, use the show controllers e3 command in EXEC mode . The BERT results include the following information:

• Type of test pattern selected
• Status of the test
• Interval selected
• Time remaining on the BERT
• Total bit errors
• Total bits received

BERT is data intrusive. Regular data cannot flow on a line while the test is in progress. The line is put in an alarm state when a BERT is in progress and restored to a normal state after a BERT has been terminated.

Usage Guidelines

Use the bert error command with the bert pattern command.

Usage Guidelines

Use the bert interval command with the bert pattern command. If the bert interval command is not used, then the BERT runs for a default of 1 minute.

Usage Guidelines

BERT is supported on each of the T3/E3 or T1/E1 links. It is done only over an unframed T3/E3 or T1/E1 signal and is run on only one port at a time. It is also supported on an individual channel group.

To begin a BERT, commit the configuration and use the bert t1 , bert e1 , bert t3 , or bert e3 command in EXEC mode.

To view the BERT results, use the show controllers t1 or show controllers t3 command in EXEC mode. The BERT results include the following information:

• Type of test pattern selected
• Status of the test
• Interval selected
• Time remaining on the BERT
• Total bit errors
• Total bits received

BERT is data intrusive. Regular data cannot flow on a line while the test is in progress. The line is put in an alarm state when a BERT is in progress and restored to a normal state after a BERT has been terminated.

Usage Guidelines

For the interface-path-id argument, use the following guidelines:

• If specifying a physical interface, the naming notation is rack/slot/module/port. The slash between values is required as part of the notation. An explanation of each component of the naming notation is as follows:

  • rack : Chassis number of the rack.

  • slot : Physical slot number of the line card.

  • module : Module number. A physical layer interface module (PLIM) is always 0.

  • port : Physical port number of the interface.

• If specifying a virtual interface, the number range varies, depending on interface type.

Note

Before you can start a BERT on a T1 controller or channel group, you must configure a BERT pattern using the bert pattern command. If desired, you can also adjust the default setting (1 minute) of the BERT interval using the bert interval command. Both of these commands are available in T1 configuration mode and channel group configuration mode.

To view the BERT results, use the show controllers t1 command in EXEC mode mode. The BERT results include the following information:

• Type of test pattern selected
• Status of the test
• Interval selected
• Time remaining on the BERT
• Total bit errors
• Total bits received

BERT is data intrusive. Regular data cannot flow on a line while the test is in progress. The line is put in an alarm state when a BERT is in progress and restored to a normal state after a BERT has been terminated.

Usage Guidelines

For the interface-path-id argument, use the following guidelines:

• If specifying a physical interface, the naming notation is rack/slot/module/port. The slash between values is required as part of the notation. An explanation of each component of the naming notation is as follows:

  • rack : Chassis number of the rack.

  • slot : Physical slot number of the line card.

  • module : Module number. A physical layer interface module (PLIM) is always 0.

  • port : Physical port number of the interface.

• If specifying a virtual interface, the number range varies, depending on interface type.

Note	Before you can start a BERT on a T3 controller, you must configure a BERT pattern using the bert pattern command. If desired, you can also adjust the default setting (1 minute) of the BERT interval using the bert interval command. Both of these commands are available in T3 configuration mode.

To view the BERT results, use the show controllers t3 command in EXEC mode . The BERT results include the following information:

• Type of test pattern selected
• Status of the test
• Interval selected
• Time remaining on the BERT
• Total bit errors
• Total bits received

BERT is data intrusive. Regular data cannot flow on a line while the test is in progress. The line is put in an alarm state when a BERT is in progress and restored to a normal state after a BERT has been terminated.

Usage Guidelines

You can specify a cable length from 0 to 450 feet; however, the hardware recognizes only two ranges: 0 to 49 and 50 to 450. For example, entering 35 feet uses the 0 to 49 range. If you later change the cable length to 40 feet, there is no change because 40 is still within the 0 to 49 range. However, if you change the cable length to 50, the 50 to 450 range is used. The actual number you enter is stored in the configuration file.

Usage Guidelines

The channel-group command is available only on channelized SPAs.

Use the channel-group command in configurations in which the router must communicate with a T1 or an E1 fractional data line. The channel group number may be arbitrarily assigned and must be unique for the controller. An associated serial interface is created with each defined channel group.

Before the channel group configuration is valid, you must define the associated DS0 time slots using the timeslots command.

Use the no channel group command to delete a channel group.

Usage Guidelines

When specifying a channelized T1 controller, use the following guidelines for the interface-path-id :

• The naming notation is rack/slot/module/port/T3Num/T1num.
• The slash between values is required as part of the notation.
• The following list describes the components of the notation:

  • rack —Chassis number of the rack.

  • slot —Physical slot number of the line card.

  • module —Module number or subslot (for a SPA). A physical layer interface module (PLIM) is always 0.

  • port —Physical port number of the interface.

  • T3num —T3 controller number.

  • T1num —T1 controller number.

  There should not normally be any need to clear the LNM controller states. The state option resets the LNM configuration which causes an update of the current LNM states in the system. Therefore, under normal conditions, if the controller is in alarm state, the reset should continue to report the alarm state; alternatively, if the controller is clear of any alarms, the reset will show the stable state. The use of the clear controller lnm state command does not actually clear any alarms, but causes a refresh of their values in the system. Therefore, this command can be used if the reported controller state should happen to be out of synchronization with the actual controller state.

  To view the status of the controllers, use the show controllers t1 command.

Usage Guidelines

When specifying a channelized T1 controller, use the following guidelines for the interface-path-id :

• The naming notation is rack/slot/module/port/T3Num/T1num.
• The slash between values is required as part of the notation.
• The following list describes the components of the notation:

  • rack —Chassis number of the rack.

  • slot —Physical slot number of the line card.

  • module —Module number or subslot (for a SPA). A physical layer interface module (PLIM) is always 0.

  • port —Physical port number of the interface.

  • T3num —T3 controller number.

  • T1num —T1 controller number.

• If specifying a virtual interface, the number range varies, depending on interface type.
• When specifying a virtual tributary group, the naming notation is rack/slot/module/port/vtg/vt. The slash between values is required as part of the notation. An explanation of each component of the naming notation is as follows:

  • rack —Chassis number of the rack.

  • slot —Physical slot number of the line card.

  • module —Module number or subslot (for a SPA). A physical layer interface module (PLIM) is always 0.

  • port —Physical port number of the interface.

  • vtg —Virtual tributary group.

  • vt —Virtual tributary instance.

  To view the status of the controllers, use the show controllers t1 command.

Usage Guidelines

For the interface-path-id argument, use the following guidelines:

• When specifying a T3 controller, the naming notation is rack/slot/module/port/T3num. The slash between values is required as part of the notation. An explanation of each component of the naming notation is as follows:

  • rack —Chassis number of the rack.

  • slot —Physical slot number of the line card or SIP.

  • module —Module number or subslot (for a SPA). A physical layer interface module (PLIM) is always 0.

  • port —Physical port number of the interface.

  • T3num —T3 controller number.

  To view the status of the controllers, use the show controllers t3 command.

Usage Guidelines

No specific guidelines impact the use of this command.

Usage Guidelines

If you do not specify the clock source command, the default clock source is used.

Configure the clock source line command if your telephone company or the remote data service unit provides the reference clock of the T3 or E3 connection.

Configure the clock source internal command if your router provides the reference clock of the T3 or E3 connection.

Note	For a back-to-back connection between two T3 network modules, one controller must be configured for internal clocking while the other controller must be configured for line clocking.

Usage Guidelines

For the interface-path-id argument, use the following guidelines:

• If specifying a physical interface, the naming notation is rack/slot/module/port. The slash between values is required as part of the notation. An explanation of each component of the naming notation is as follows:

  • rack : Chassis number of the rack.

  • slot : Physical slot number of the line card.

  • module : Module number. A physical layer interface module (PLIM) is always 0.

  • port : Physical port number of the interface.

• If specifying a virtual interface, the number range varies, depending on interface type.

The controller e1 command is used in configurations in which the router is intended to communicate with an E1 fractional data line. The controller e1 command is available only on channelized interfaces.

Use the mode command in T3 configuration mode to specify the mode for the port. The default mode for 2-Port and 4-Port Channelized T3 SPAs is T1.

Note	If you do not use the mode command to define the port to be E1, you cannot configure the E1 controller.

To view the status of the controllers, use the show controllers e1 command.

Usage Guidelines

For the interface-path-id argument, use the following guidelines:

• If specifying a physical interface, the naming notation is rack/slot/module/port. The slash between values is required as part of the notation. An explanation of each component of the naming notation is as follows:

  • rack : Chassis number of the rack.

  • slot : Physical slot number of the line card.

  • module : Module number. A physical layer interface module (PLIM) is always 0.

  • port : Physical port number of the interface.

• If specifying a virtual interface, the number range varies, depending on interface type.

To view the status of the controllers, use the show controllers e3 command.

Usage Guidelines

When specifying a channelized T1 controller, use the following guidelines for the interface-path-id :

• The naming notation is rack/slot/module/port/T3Num/T1num.
• The slash between values is required as part of the notation.
• The following list describes the components of the notation:

  • rack —Chassis number of the rack.

  • slot —Physical slot number of the line card.

  • module —Module number or subslot (for a SPA). A physical layer interface module (PLIM) is always 0.

  • port —Physical port number of the interface.

  • T3num —T3 controller number.

  • T1num —T1 controller number.

• If specifying a virtual interface, the number range varies, depending on interface type.
• When specifying a virtual tributary group, the naming notation is rack/slot/module/port/vtg/vt. The slash between values is required as part of the notation. An explanation of each component of the naming notation is as follows:

  • rack —Chassis number of the rack.

  • slot —Physical slot number of the line card.

  • module —Module number or subslot (for a SPA). A physical layer interface module (PLIM) is always 0.

  • port —Physical port number of the interface.

  • vtg —Virtual tributary group.

  • vt —Virtual tributary instance.

  The controller t1 command is used in configurations in which the router is intended to communicate with a T1 fractional data line. The controller t1 command is available only on channelized SPAs.

  Use the mode command in T3 configuration mode to specify the mode for each T3 port.

  To view the status of the controllers, use the show controllers t1 command.

  If the T1 framing type is super frame (SF), you should consider disabling yellow alarm detection as the yellow alarm can be incorrectly detected with SF framing.

  Serial interface may flap and eventually, go down if yellow alarm detection is not disabled on its T1 controller configured with SF framing.

Usage Guidelines

For the interface-path-id argument, use the following guidelines:

• When specifying a T3 controller, the naming notation is rack/slot/module/port/T3num. The slash between values is required as part of the notation. An explanation of each component of the naming notation is as follows:

  • rack —Chassis number of the rack.

  • slot —Physical slot number of the line card or SIP.

  • module —Module number or subslot (for a SPA). A physical layer interface module (PLIM) is always 0.

  • port —Physical port number of the interface.

  • T3num —T3 controller number.

• If specifying a virtual interface, the number range varies, depending on interface type.

To view the status of the controllers, use the show controllers t3 command.

Usage Guidelines

No specific guidelines impact the use of this command.

Usage Guidelines

No specific guidelines impact the use of this command.

Usage Guidelines

If the timer for the T1 or E1 path delay trigger expires, an alarm is declared.

Usage Guidelines

If the timer for the T3 or E3 path delay trigger expires, an alarm is declared.

Usage Guidelines

No specific guidelines impact the use of this command.

Usage Guidelines

No specific guidelines impact the use of this command.

Usage Guidelines

This command does not have a no form.

Usage Guidelines

This command does not have a no form.

Usage Guidelines

The local interface configuration must match the remote interface configuration. For example, if you reduce the maximum bandwidth to 16,000 on the local port, you must also do the same on the remote port.

The dsu bandwidth command reduces the bandwidth by padding the E3 and T3 frame.

To verify the data service unit (DSU) bandwidth configured on the interface, use the show controllers t3 or show controllers e3 command in EXEC mode.

When G.751 framing is used on E3 links, DSU bandwidth can be used to select a payload subrate from 34,010 kbps down to 22 kbps. Before framing bypass can be used, a DSU bandwidth of 34,010 kbps must be configured.

Although software allows the user to configure a continuous range of bandwidths in subrate modes, vendors support bandwidths only in quantums (for example, in a ADC Kentrox T3 link, bandwidth must be in multiples of 500 kbps). Therefore, the software sets the user-configured bandwidth to the closest vendor-supported bandwidth. Use the show controllers t3 or show controllers e3 command to display the actual bandwidth that is configured.

The following table shows DSU modes and vendor-supported bandwidths.

Usage Guidelines

The default DSU mode Cisco is equivalent to Digilink Mode with Scrambling Enabled. This mode was added to enable scrambling along with Digilink mode on E3 Controllers.

Digilink Mode, by definition does not support scrambling for E3 Controllers though it supports the same for T3 Controllers. For T3 controllers, there is no functional default DSU mode. The DSU Mode Cisco is not applicable for T3 Controller.

For interoperability, it is recommended to always configure the DSU mode command under T3/E3 Controller by matching the DSU type of the remote port.

To enable Scrambling, configure Scramble under the respective Serial Interface for the T3/E3 Controller.

Refer to Table 1 for more information regarding the modes.

The local interface configuration must match the remote interface configuration. For example, if you define the data service unit (DSU) interoperability mode as digital-link on the local port, you must also do the same on the remote port.

You must know what type of DSU is connected to the remote port to determine if it interoperates with a T3 or an E3 controller. The dsu mode command enables and improves interoperability with other DSUs.

To verify the DSU mode configured on the interface, use the show controllers t3 command in EXEC mode.

Usage Guidelines

To verify the DSU remote settings configured on the interface, use the show controllers t3 command in EXEC mode.

Usage Guidelines

The fdl command applies only to T1 lines and can be used only if the T1 framing type is Extended Super Frame (ESF).

To display the performance report information, use the show controllers t1 command.

Usage Guidelines

Use the framing command in configurations in which the router or access server is intended to communicate with E1 fractional data lines. The service provider determines the framing type required for your E1 circuit.

Usage Guidelines

If you do not use the framing command, the default is used by the E3 controllers to automatically determine the framing type received from the far-end equipment. You can also set the framing for each T1/E1 channel by using the framing command in T1 or E1 configuration mode.

Usage Guidelines

Use the framing command in configurations in which the router or access server is intended to communicate with T1 fractional data lines. The service provider determines the framing type required for your T1 circuit.

Usage Guidelines

If you do not use the framing command, the default is used by the T3 controllers to automatically determine the framing type received from the far-end equipment. You can also set the framing for each T1 or E1 channel by using the framing command in T1 or E1 configuration mode.

Usage Guidelines

Use this command in configurations where the router must communicate with T1 or E1 fractional data lines. The T1 or E1 service provider determines which line-code type is required for your T1 or E1 circuit.

Usage Guidelines

This command can only be configured on full T1 or E1 channel groups; it is not supported on fractional, or DS0 links.

The lnm major-warning command cannot be configured with the lnm remove command—they are mutually exclusive.

The major threshold values must be greater than the values configured in the lnm minor-warning command.

LNM supports hierarchical level alarm reporting as defined in the Telcordia (Bellcore) GR-253 standard. Hierarchical alarm reporting means that whenever a higher alarm is asserted, the lower alarm state is suppressed. When the high alarm is cleared, the lower alarm will re-assert if the condition still exists.

For LNM, this means that if a major warning threshold is exceeded resulting in a crossed event and alarm state reached, then a minor warning alarm state is suppressed and placed in stable state. The minor crossed event also is removed from the bistate log. Only a single crossed event for major warnings will appear in the bistate log for the controller. When the major warning is cleared, the minor warning alarm is asserted if the condition still exists.

Usage Guidelines

This command can only be configured on full T1 or E1 channel groups; it is not supported on fractional, or DS0 links.

The minor threshold values cannot be greater than the values configured in the lnm major-warning command.

LNM supports hierarchical level alarm reporting as defined in the Telcordia (Bellcore) GR-253 standard. Hierarchical alarm reporting means that whenever a higher alarm is asserted, the lower alarm state is suppressed. When the high alarm is cleared, the lower alarm will re-assert if the condition still exists.

For LNM, this means that if a major warning threshold is exceeded resulting in a crossed event and alarm state reached, then a minor warning alarm state is suppressed and placed in stable state. The minor crossed event also is removed from the bistate log. Only a single crossed event for major warnings will appear in the bistate log for the controller. When the major warning is cleared, the minor warning alarm is asserted if the condition still exists.

Usage Guidelines

This command can only be configured on full T1 or E1 channel groups; it is not supported on fractional, or DS0 links.

The lnm remove command cannot be configured with the lnm major-warning command—they are mutually exclusive.

The remove threshold values must be greater than the values configured in the lnm minor-warning command.

LNM supports hierarchical level alarm reporting as defined in the Telcordia (Bellcore) GR-253 standard. Hierarchical alarm reporting means that whenever a higher alarm is asserted, the lower alarm state is suppressed. When the high alarm is cleared, the lower alarm will re-assert if the condition still exists.

For LNM, this means that if a remove threshold is exceeded resulting in a crossed event and alarm state reached, then a minor warning alarm state is suppressed and placed in stable state. The minor crossed event also is removed from the bistate log. Only a single crossed event for major warnings will appear in the bistate log for the controller. When the major warning is cleared, the minor warning alarm is asserted if the condition still exists.

Usage Guidelines

Caution

Enabling LNM syslog messages can produce large amounts of console messages. If you want to avoid this and disable the LNM syslog, you can use the show controllers lnm command to view the most recent event messages and current LNM states.

When you enable syslog messages for LNM events using the lnm syslog command, LNM messages will appear in both the system log and in the log events buffer. You can display LNM events in the log events buffer using the show logging events buffer bistate-alarms-set command, and also using the show logging command, which are described in the System Monitoring Command Reference for Cisco ASR 9000 Series Routers

LNM supports hierarchical level alarm reporting as defined in the Telcordia (Bellcore) GR-253 standard. Hierarchical alarm reporting means that whenever a higher alarm is asserted, the lower alarm state is suppressed. When the high alarm is cleared, the lower alarm will re-assert if the condition still exists.

For LNM, this means that if a major warning threshold is continuously met or exceeded resulting in a crossed event and alarm state, then a minor warning alarm state is suppressed and returned to stable state. The minor crossed event also is removed from the bistate log. When the major warning is cleared, the minor warning alarm is asserted if the condition still exists.

Only a single crossed event for major warnings will appear in the bistate log for the controller. Therefore, you will see only a single log message for a controller if noise exists above configured threshold values.

Usage Guidelines

Use the loopback command for troubleshooting purposes. To verify that a loopback is configured on the interface, use the show controllers t1 or show controllers e1 command in EXEC mode .

For E1 lines, only the local and network options are valid. For T1 lines, all listed options are valid.

Usage Guidelines

Use the loopback command for troubleshooting purposes. To verify that a loopback is configured on the interface, use the show controllers t3 or show controllers e3 command in EXEC mode. Note that remote loopback is valid only in C-bit parity mode.

You can also loopback each T1 or E1 channel by using the loopback command in T1 or E1 configuration mode.

Usage Guidelines

Use the show controllers t3 command to display MDL information (received strings). MDL information is displayed only when framing is set to C-bit.

Note	MDL is supported only when the DS3 framing is C-bit parity.

Usage Guidelines

You can change the mode of a controller only when there are no subinterfaces defined for the controller. For example, if you previously defined channelized T1 subinterfaces on a T3 interface and now you want to change this to E1 subinterfaces or a clear channel interface, you must first clear the subinterfaces. To do this, use the no controller t1 command for all defined T1/E1 subinterfaces. If you have defined serial parameters, you also need to use the no interface serial command.

For channelized SPAs, you must use the mode command before you can configure any channelized controllers.

Usage Guidelines

No specific guidelines impact the use of this command.

Usage Guidelines

No specific guidelines impact the use of this command.

Usage Guidelines

For the interface-path-id argument, use the following guidelines:

• If specifying a physical interface, the naming notation is rack/slot/module/port. The slash between values is required as part of the notation. An explanation of each component of the naming notation is as follows:

  • rack : Chassis number of the rack.

  • slot : Physical slot number of the line card.

  • module : Module number. A physical layer interface module (PLIM) is always 0.

  • port : Physical port number of the interface.

• If specifying a virtual interface, the number range varies, depending on interface type.

Usage Guidelines

For the interface-path-id argument, use the following guidelines:

• If specifying a physical interface, the naming notation is rack/slot/module/port. The slash between values is required as part of the notation. An explanation of each component of the naming notation is as follows:

  • rack : Chassis number of the rack.

  • slot : Physical slot number of the line card.

  • module : Module number. A physical layer interface module (PLIM) is always 0.

  • port : Physical port number of the interface.

• If specifying a virtual interface, the number range varies, depending on interface type.