42
Step6 Return to privileged EXEC mode:
Gateway(config-controller)# Ctrl-Z
Gateway#
Tip To save the gateway configuration, save it to NVRAM. Refer to the “Saving Configuration Changes” section on
page 57.
Verify
To verify that your controller is up and running and that no alarms have been reported:
•Enter the show controller command and specify the controller type, slot, and port numbers:
Gateway# show controller t1 1/7
T1 1/7 is up.
No alarms detected.
Framing is ESF, Line Code is B8ZS, Clock Source is Line Primary.
Version info of slot 2: HW: 2, Firmware: 14, NEAT PLD: 13, NR Bus PLD: 19
Data in current interval (476 seconds elapsed):
0 Line Code Violations, 0 Path Code Violations
0 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins
0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 0 Unavail Secs
Total Data (last 24 hours)
0 Line Code Violations, 0 Path Code Violations,
0 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins,
0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 0 Unavail Secs
•Note the following:
–
The controller must report being up.
–
No errors should be reported.
If you are having trouble:
•First decide if the problem is because of 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.
•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 time slots 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.
Configuring a Channelized T3 DFC
Your CT3 card offers 28 individual T1 channels (bundled in the T3) for serial transmission of voice and 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.
Note The CT3 controller numbering convention is dfc-slot/port in CLI commands. DFC slot numbering starts from the
motherboard and works up from left to right. Slot 0 is reserved for the motherboard. The DFC 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.