Configuring A Channelized T3 Trunk Card; Controller Numbering - Cisco AS5350 - Universal Access Server Configuration Manual

Chapter 3 Basic Configuration Using the Command-Line Interface
Tip If you are having trouble:
•
•
•

Configuring a Channelized T3 Trunk Card

Your AS54-DFC-CT3 trunk card offers 28 individual T1 channels (bundled in the T3) for serial
transmission of data. The CT3 link supports the maintenance data link channel in C-Bit parity mode and
also payload and network loopbacks. The T1s multiplexed in the CT3 link support facilities data link
(FDL) in extended super frame (ESF) framing.
Additionally, you can allocate your CT1 channels as described in the
E1 Trunk Cards" section on page

Controller Numbering

The CT3 controller numbering convention is dfc-slot/port in CLI commands. Trunk-card slot numbering
starts from the motherboard and works up from left to right. Slot 0 is reserved for the motherboard.
Trunk-card slots are numbered sequentially from 1 to 7. Port number value is always 0.
Under the CT3, the CT1 controller numbering convention is dfc-slot/port:channel in CLI commands.
Port numbering values range from 1 to 28.
OL-3418-02 B0
First decide if the problem is due to the T1 or E1 line or with a particular channel group. If the
problem is with a single channel group, you have a potential interface problem. If the problem is
with the T1 or E1 line, or with all channel groups, you have a potential controller problem. (See the
"Configuring ISDN PRI" section on page
To troubleshoot your E1 or T1 controllers, first check that the configuration is correct. The framing
type and line code should match to what the service provider has specified. Then check channel
group and PRI-group configurations, especially to verify that the timeslots and speeds are what the
service provider has specified. At this point, the show controller t1 or show controller e1
commands should be used to check for T1 or E1 errors. Use the command several times to determine
if error counters are increasing, or if the line status is continually changing. If this is occurring, you
need to work with the service provider.
Another common reason for failure is the dial-tdm-clock priority setting. The default setting is a
free-running clock that causes clock slip problems if not set properly. (See the
Clocking" section on page
Cisco AS5350 and Cisco AS5400 Universal Gateway Software Configuration Guide
3-13.)
3-31.)
3-9.
Configuring a Channelized T3 Trunk Card
"Configuring
"Configuring Channelized T1 and
3-11