Cisco AS5350 - Universal Access Server - Page 79

3-35
Cisco AS5350 and Cisco AS5400 Universal Gateway Software Configuration Guide
OL-3418-02 B0
Chapter 3 Basic Configuration Using the Command-Line Interface
Configuring Clocking
CLOCK CHANGE HISTORY
CLOCK
Event Time
2/1 Controller shutdown 23:23:06 UTC Tue Nov 30 1999
2/0 Change in CLI configuration 23:27:25 UTC Tue Nov 30 1999
AS5400#
• Verify your free-running clock selection using the show tdm clocks command:
AS5400# show tdm clocks
Primary Clock:
System primary is FREE RUNNING with priority 2
TDM Bus Master Clock Generator State = FREERUN
Backup clocks for primary:
Source Slot Port DS3-Port Priority Status State
Trunk 2 0 NO 204 Good Default
Trunk 2 1 NO 205 Good Default
Trunk cards controllers clock health information
Slot Type 7 6 5 4 3 2 1 0
2 T1 B B B B G G G G
CLOCK CHANGE HISTORY
CLOCK
Event Time
Freerun Change in CLI configuration 23:27:25 UTC Tue Nov 30 1999
AS5400#
• Verify your BITS clock selection using the show tdm clocks command:
AS5400# show tdm clocks
Primary Clock:
System primary is external with priority 1
TDM Bus Master Clock Generator State = NORMAL
Backup clocks for primary:
Source Slot Port DS3-Port Priority Status State
Trunk 2 0 NO 204 Good Default
Trunk 2 1 NO 205 Good Default
Trunk cards controllers clock health information
Slot Type 7 6 5 4 3 2 1 0
2 T1 B B B B G G G G
CLOCK CHANGE HISTORY
CLOCK
Event Time
External Change in CLI configuration 23:27:25 UTC Tue Nov 30 1999
AS5400#
Tip The most common reason for clock slip problems is that the dial-tdm-clock priority parameter is set
improperly. Change the default setting for dial-tdm-clock priority from free-running clock to a setting
that matches your system requirements.