Downloads |
Table Of Contents
T1/E1 Multiflex VWIC Enhancements
Related Features and Technologies
Supported Standards, MIBs, and RFCs
Configuring BERT on Cisco 2600 and Cisco 3600 VWICs
T1/E1 Multiflex VWIC Enhancements
This feature module contains the following sections:
•
Supported Standards, MIBs, and RFCs
Feature Overview
Cisco T1/E1 Multiflex Voice/WAN interface cards (VWICs) support voice and data applications in Cisco 2600 and 3600 series routers. The VWICs offer WAN interface card (WIC) and voice interface card (VIC) functionality in a variety of applications for enterprises and service providers who supply customer premises equipment.
The single- or dual-port T1 or E1 trunk interface in a VWIC:
•
•
•
–
–
–
At the physical layer, the one or two network interfaces provided use RJ-48C jacks with on-card TDM drop and insert capability in the VWIC with the drop and insert option. The card supports uninterrupted drop and insert operation during Cisco IOS software upgrades. The TDM drop and insert connection is maintained independent of the Cisco IOS, including router reload operations, in order to minimize service interruptions.
There are four versions of the VWIC:
•
•
•
•
Transition cables support the different T1/E1 line configurations.
This feature's design provides for high T1/E1 port density with integrated support for voice and data applications on lines provisioned for a combination of PCM voice and either Frame Relay or Asychronous Transfer Mode (ATM) data. Bit-error rate testing (BERT) and V.54 capability are also supported.
When the card is initialized, the Cisco IOS software reads the VWIC's cookie ID to determine whether the card is to be used as an E1 or T1 card; then the firmware loads the proper configuration onto the card. The cookie also indicates whether the card is single or dual port and whether drop and insert is supported if it is a dual-port card. The card does not support "mixed-mode" operation, such as when one interface is E1 and the other interface is T1. Cisco IOS software recognizes the G.703 cookie ID indicating the card has hardware support for the E1 interface.
Each two-port model has an internal TDM bus, which can be used to handle pass-through of individual timeslots between Port 1 and Port 2 on the same card.
To support TDM switching, TDM Manager and Connection Manager modules provide the infrastructure to control the switching hardware in the system.
The reset system on the card is only activated when the card is initially powered up. From that point on, the host software determines whether the card's firmware is already running. If so, the host software initializes its own data structures and SCC hardware and resumes operation. During this sequence, the card continues to allow any timeslots designated as pass-throughs to be transferred between the ports.
Benefits
Extended Availability Drop and Insert (EADI)
Extended Availability Drop and Insert (EADI) allows on-card TDM drop-and-insert (D&I) connections to survive an instance of IOS unavailability or reload. EADI is supported on 2-port T1/E1 D&I cards only. EADI will support TDM connections between the two ports on the same card only. These connections are drop and inserted on the TDM bus on the T1/E1 card itself.
Note
This enhancement has no associated CLI commands.
Time Division Multiplexing (TDM)
Time-division multiplexing (TDM) allows switching of channels between ports 1 and 2. The card accomodates TDM groups, which are groups of timeslots that may be sent from one E1/T1 trunk to another without being terminated. This allows you to allocate some timeslots (TDM groups) for pass-through while other timeslots (channel groups) are terminated as a serial link. By using these two abilities, you can connect traffic from any TDM-based device to any other TDM-based device in the system, as long as there is a path and enough bandwidth between the devices.
CLI Reset, Microcode Reload Functionality
You can reload the firmware and FPGA on the VWIC from the CLI without reloading the IOS image by using the new microcode reload controller command.
Bit Error Rate Testing (BERT)
Bit-error-rate testing and loopbacks are used by carriers and ISPs to help resolve problems as well as test the quality of T1/E1 links. By early detection of poor quality links and quick problem isolation, network operators can improve their network's quality of service and increase their revenues:
•
•
•
•
Note
Restrictions
For this Cisco IOS software release and Cisco 2600 and Cisco 3600 routers, only one BERT-related operation per physical port is supported. For example, if there are two channel groups on a T1, and you run a BERT test on one channel group, the other channel group cannot detect incoming V.54 loopback activation requests until the BERT test terminates.
Support for 2 channel groups is available only on the Cisco 2600 WIC slot and on the FE network module for the Cisco 3600. It is not supported on the Combo network module for the Cisco 3600.
Related Features and Technologies
Digital T1 Packet Voice Trunk Network Modules require the 2-port T1 Multiflex VWIC for operation. For more information about these modules, see the online 12.0(7)T document, Configuring Digital T1 Packet Voice Trunk Network Modules on Cisco 2600 and 3600 Routers.
Related Documents
The following documents provide additional information about installing and configuring T1/E1 Multiflex VWICs:
•
•
•
The following Cisco IOS Release 12.1 documents provide information that can help you use T1/E1 Multiflex VWICs and the BERT/TDM features:
•
•
•
•
•
•
Supported Platforms
•
EADI will work when the 2-port D&I T1/E1 is plugged in to a standalone WIC slot on the 2600 platform.
•
Supported Standards, MIBs, and RFCs
Standards
•
MIBs
•
For descriptions of supported MIBs and how to use MIBs, see the Cisco MIB web site on CCO at http://www.cisco.com/public/sw-center/netmgmt/cmtk/mibs.shtml.
RFCs
•
–
–
–
–
A host process updates the T1/E1 MIB information for network performance monitoring. In addition to periodic updates for reporting MIB data, some line state changes cause the processor to send information to the host driver asynchronously. These events require the host driver to take action with the associated multi-channel controller (if available).
Prerequisites
For this feature to respond to a V.54 loopback activation from a far end, the feature must have V.54 request detection enabled.
Configuration Tasks
See the following section for configuration tasks for the V.54 and BERT features. Each task in the list indicates if the task is optional or required.
•
Configuring BERT on Cisco 2600 and Cisco 3600 VWICs
Verifying BERT
To verify BERT parameters, enter the show controllers user EXEC command:
Router> show controllers e1 0/0 bertE1 0/0 is down.BERT is done. The result of last time isDSX1 BERT status : doneDSX1 BERT pattern : unknownDSX1 BERT sync count : 0DSX1 BERT interval : 0 minDSX1 BERT time remain : 0 min 0 secDSX1 BERT total errs : 0DSX1 BERT total k bits: 0DSX1 BERT errors (last): 0DSX1 BERT k bits (last): 0Command Reference
This section documents new or modified commands. All other commands used with this feature are documented in the Cisco IOS Release 12.1 command reference publications.
•
bert abort
To stop BERT pattern generation for a particular port, use the bert abort controller EXEC command. There is no no form of this command.
bert abort controller type-controller slot/port
Syntax Description
type-controller
Use either T1 or E1 depending on the type of facility.
slot/port
Enter the slot number and port number for the BERT pattern being stopped.
Defaults
No default behavior or values.
Command Modes
EXEC mode
Command History
12.0(1)T
This command was introduced in this release.
12.1(1)T
This command was applied to VWICs for Cisco 2600 and Cisco 3600 series routers in this release.
Usage Guidelines
This command enables you to end a BERT test early—rather than waiting for the BERT interval specified in the bert controller command to elapse.
Examples
The following example shows a BERT test on T1 ports 0/0 being stopped prematurely:
Router# bert abort controller t1 0/0Related Commands
bert controller
To start a bit-error rate test for a particular port, use the bert controller EXEC command. There is no no form of this command.
bert controller type-controller slot/port [channel-group channel-number] [pattern pattern-name] [interval 1-14400]
Syntax Description
Defaults
Bit error rate testing (BERT) is disabled.
Command Modes
EXEC mode
Command History
Usage Guidelines
The argument channel-group channel-group-number to specify a channel-group is optional. If the channel-group is specified, BERT will be run only on the timeslots associated with the channel group. If the channel-group keyword and argument are not used, the BERT will run on all timeslots of the specified controller.
Examples
The following example shows a BERT test started on a T1 port 0/0 and channel group 0 with a QRSS signaling pattern for a duration of 5 minutes:
Router# bert controller t1 0/0 channel-group 0 pattern qrss interval 5Related Commands
channel-group
To assign a channel group, use the channel-group controller configuration mode command. To unassign a channel group, use the no form of this command.
channel-group range timeslot range speed [48 | 56 | 64]
no channel-group range timeslot range speed [48 | 56 | 64]
Syntax Description
Defaults
No default behavior or values.
Command Modes
Controller configuration mode
Command History
Usage Guidelines
The channel-group command allows you to combine timeslots to create high-bandwidth pipes, which are treated as serial interfaces (a serial interface is created automatically when you create a channel group). You must enter controller command in configuration mode before the channel-group command can be used. The channel-group command accomodates two channel groups with a range of 0 to 1.
You can configure two channel groups on a one-port WAN/VICs and the first port of a two-port WAN/VIC. If you configure two channel groups on the first port of a two-port WAN/VIC card, then you can only use the second port for drop and insert applications. You can't have channel groups and TDM groups with the same number on the same T1/E1 controller.
Note
Examples
The following example shows the setting of channel-group 0 on timeslot 5 with a speed of 48 bps:
Router(config-controller)# channel-group 0 timeslot 5 speed 48Related Commands
connect
To start passing data between ports of a VWIC on Cisco 2600 and Cisco 3600 series routers, use the connect controller configuration mode command. To break this connection, use the no form of this command.
connect connection-name {t1 | e1} slot/port 1 {t1 | e1} slot/port 2
no connect connection-name {t1 | e1} slot/port 1 {t1 | e1} slot/port 2
Syntax Description
connection-name
Enter the name you have chosen for this connection.
t1/e1
Choose the type of line.
slot/port
Choose the slot and port number to be connected.
Defaults
Connections are not made.
Command Modes
Controller configuration mode
Command History
Usage Guidelines
Once TDM groups are created on two different physical ports, you can use the connect command to start the passage of data between the ports. If a crosspoint switch is provided in the AIM slot, the connections can extend between ports on different cards. Otherwise, the connection will be restricted to ports on the same VWIC card.
The VWIC card can make a connection only if the number of timeslots at the source and destination are the same. For the connection to be error-free, the two ports must be driven by the same clock source, otherwise, "slips" will occur.
Examples
The following example shows a fractional T1 terminated on port 0 using timeslots 1 through 8; a fractional T1 is terminated on port 1 using timeslots 2 through 12; and timeslots 13 through 20 from port 0 are connected to timeslots 14 through 21 on port 1 by using the connect command:
Router# configure terminalRouter(config)# controller t1 0/0Router(config-controller)# channel-group 1 timeslots 1-8Router(config-controller)# tdm-group 1 timeslots 13-20Router(config-controller)# exitRouter(config)# controller t1 0/1Router(config-controller)# channel-group 1 timeslots 2-12Router(config-controller)# tdm-group 2 timeslot 14-21Router(config-controller)# exitRouter(config)# connect exampleconnection t1 0/0 1 t1 0/1 2Related Commands
tdm-group
Configures lists of timeslots for creating clear-channel groups (pass-through) for time-division multiplexing (TDM) cross-connect.
detect v54 channel-group
To enable V.54 loopback detection for the command sent from the remote device, use the detect v54 channel-group controller configuration mode command. To disable the v.54 loopback detection, use the no form of this command.
detect v54 channel-group channel-number
no detect v54 channel-group channel-number
Syntax Description
Defaults
V.54 loopback detection is disabled.
Command Modes
Controller configuration mode
Command History
Usage Guidelines
Use the detect v54 channel-group controller configuration mode command to enable v.54 loopback detection. The remote device will send a loopup inband payload command sequence in fractional T1 (FT1).
Examples
The following example shows the loopback detection being set for channel-group 1; then the loopback detection is disabled for channel-group 1:
Router(config-controller)# detect v54 channel-group 1Router(config-controller)# no detect v54 channel-group 1Related Commands
loopback remote v54 channel-group
Activates a remote V.54 loopback for the channel-group on the far end.
loopback remote
To activate a remote loopback, use the loopback remote controller-configuration mode command. To deactivate the remote loopback, use the no form of this command.
loopback remote {v54 channel-group channel-number | iboc | esf {payload | line}}
no loopback remote {v54 channel-group channel-number | iboc | esf {payload | line}}
Syntax Description
Defaults
Loopbacks are not activated.
Command Modes
Controller configuration mode
Command History
12.1(1)T
This command was introduced.
12.1(2)XH
This command was modified to include the iboc and esf options.
Usage Guidelines
The commands loopback remote esf payload and loopback remote esf line are only allowed when ESF is configured on the controller. The FDL mode for the T1 controllers should be either att, ansi, or both. The default is no fdl. To enable the FDL channel on the ESF for transmitting loopback codes, you need to configure an FDL type.
The IBOC loopback and the V.54 loopbacks will work without FDL enabled.
Examples
The following example shows a T1 IBOC remote loopback and BERT being set on controller 0/0. Then BERT is stopped and the remote loopback is cancelled:
Router(config-controller)# loopback remote iboc00:04:045: %E1T1_MODULE-3-IBOCREQOK: Controller T1 0/0 - Remote end is put in line loopbackconfig-controller>endRouter> bert controller t1 0/0 pattern 1s interval 60Router> sho controller t1 0/0 bert......Router> bert abort controller t1 0/0Router# configure terminalRouter(config)#controller t1 0/0Router(config-controller)#no loopback00:28:00: %E1T1_MODULE-3-T1REQCANCELLED: Controller T1 0/0 - T1 remote loopback has been cancelledThe following example shows a loopback for a remote V.54 being set for channel group 1:
Router(config-controller)# loopback remote v54 channel-group 1Related Commands
fdl
Configures the Facility Data Link capability for Extended Super Frame (ESF) signalling.
microcode reload controller
To reload the firmware and FPGA from the command line interface (CLI) without reloading the IOS image, use the microcode reload controller privileged EXEC command. There is no no version of this command.
microcode reload controller {t1 | e1} {x/y}
Syntax Description
Defaults
No microcode reload activity is initiated.
Command Modes
Privileged EXEC.
Command History
Usage Guidelines
Configurations such as channel-groups, TDM-connections, loopbacks and so on in the running configuration are restored after this command is issued. If either of the controller ports on the WIC is in a looped state before this command is issued, the looped condition is dropped. You have to re-initiate the loopbacks from the remote end by doing "no loop" and "loop remote" from the controller configuration. If the BERT test is running, that test will be aborted for the microcode reload.
show controllers t1 | e1 bert
To view the network loopback status and BERT results, use the show controllers t1/e1 bert EXEC command. To disable the network loopback status viewing option, use the no form of this command.
show controllers {t1 | e1} [slot/port] bert
no show controllers {t1 | e1} [slot/port] bert
Syntax Description
Defaults
The network status viewing option is disabled.
Command Modes
User EXEC
Command History
12.0(2)XD
This command was introduced.
12.1(1)T
This command was modified to include the Cisco 2600 and Cisco 3600 series routers.
Usage Guidelines
If BERT is running, this command shows the real-time results up to the last second. Otherwise, the command shows the results of the previous BERT test that was run. If you specify the controller number (s/p), only the BERT result of this controller will appear. Otherwise, the BERT results for all the T1 or E1 controllers will be displayed.
Examples
The following example shows the output for the show controllers command for a specific T1 controller:
Router#show controllers t1 1/0 bertT1 1/0 is up.BERT is in progress. A snapshot of current result isDSX1 BERT status :syncDSX1 BERT pattern :QRSSDSX1 BERT sync count :1DSX1 BERT interval :1 minDSX1 BERT time remain :0 min 38 secDSX1 BERT total errs :0DSX1 BERT total k bits:28616DSX1 BERT errors (last):0DSX1 BERT k bits (last):28616Sequence of starting a BERT test, querying the BERT test while it's running, and then examining output after it's completed:
Router#bert controller t1 1/1BERT will disrupt the existing TDM connection configuredon this controller. Proceed with BERT? [confirm]Router#show controllers t1 bertT1 1/0 is up.BERT counts not valid.T1 1/1 is up.BERT is in progress. A snapshot of current result isDSX1 BERT status :syncDSX1 BERT pattern :QRSSDSX1 BERT sync count :1DSX1 BERT interval :1 minDSX1 BERT time remain :0 min 57 secDSX1 BERT total errs :0DSX1 BERT total k bits:3684DSX1 BERT errors (last):0DSX1 BERT k bits (last):3683Router#show controllers t1 bertT1 1/0 is up.BERT counts not valid.T1 1/1 is up.BERT is done on the controller. The result of last time isDSX1 BERT status :doneDSX1 BERT pattern :QRSSDSX1 BERT sync count :1DSX1 BERT interval :1 minDSX1 BERT time remain :0 min 0 secDSX1 BERT total errs :0DSX1 BERT total k bits:77969DSX1 BERT errors (last):0DSX1 BERT k bits (last):77968tdm-group
To configure a list of time slots for creating clear channel groups (pass-through) for time-division multiplexing (TDM) cross-connect, use the tdm-group command in controller configuration mode. Use the no form of this command to delete a clear channel group.
tdm-group tdm-group-no timeslot timeslot-list [type {e&m | fxs [loop-start | ground-start] | fxo [loop-start | ground-start] | fxs-melcas | fxo-melcas | e&m-melcas}]
no tdm-group tdm-group-no timeslot timeslot-list [type {e&m | fxs [loop-start | ground-start] | fxo [loop-start | ground-start] | fxs-melcas | fxo-melcas | e&m-melcas}]
Syntax Description
Defaults
No TDM group is configured.
Command Modes
Controller configuration
Command History
11.3(1)MA
This command was introduced.
12.1(1)T
This command was modified to include VWICs for Cisco 2600 and Cisco 3600 series routers.
Usage Guidelines
The tdm-group command allows specific timeslots to switch from port 0 to port 1 and vice-versa. This command is similar to the channel-group command, but it does not create a serial interface to terminate the specified channels.
Examples
The following example shows a TDM group 1 being set up to include timeslots 13 through 20:
Router(config-controller)# tdm-group 1 timeslots 13-20Related Commands
Glossary
Channelized T1/E1—A configuration in which multiple groups of timeslots are interpreted as individual streams. Each group is sent to a separate HDLC controller.
BERT—Bit error rate testing. The DS2172 BERT chip is used to do BERT testing on T1, E1, and serial interfaces associated with channel groups. The BERT chip detects V.54 LoopUp and LoopDown activation codes. The bit-error-rate test (BERT) feature enables you to test the quality of the connected channel group on T1 links by comparing a pseudo-random or a repetitive test pattern with an identical locally generated test pattern.
Drop and Insert—Also known as time-division multiplexing (TDM) cross-connect. A configuration in which a T1/E1 is connected to each data port. Some of the DS0s are transferred from one T1/E1 to the other without modification. The remaining DS0s are interpreted as one or more HDLC channel groups. Allows DS0 channels from one T1 or E1 facility to be digitally cross-connected to DS0 channels on another T1 or E1. By using this method, channel traffic is sent between a PBX and CO PSTN switch or other telephony device, so that some PBX channels are directed for long-distance service through the PSTN while the router compresses others for interoffice VoIP calls. In addition, drop and insert can cross-connect a telephony switch (from the CO or PSTN) to a channel bank for external analog connectivity.
Fractional T1/E1—A configuration which uses from 1 or more timeslots as a single data stream. The resulting stream is sent to an HDLC controller to be interpreted. Any timeslots not included in the fractional stream are ignored.
Framer—A hardware device which converts between the raw E1 or T1 bitstream and 8-bit DS0 streams. The framer also extracts and inserts signalling information.
TDM—Time-division multiplexing.
