|
|
Due to the real-time nature of voice and video, more configuration and planning is required for voice traffic than is required for traditional data traffic. Because voice and video streams are real-time and continuous, the information is normally generated by the source device and received by the destination device at a synchronized fixed rate. If the source and destination clocking is not synchronized, meaning the devices generate information at different rates, there will be a loss of information as one side overruns and the other side underruns.
As a result, for voice and video configurations a single master clock source must be configured to make the network synchronous. The master clock must be used as the clock source for all devices on the network, even when the voice traffic is compressed.
Clocking mismatches can be caused by a variety of configuration problems. The following situations can cause problems:
To ensure a synchronized system, you must configure a master clock somewhere within the network, and distribute and recover the clock throughout the network. This will allow end devices at opposite ends of the network to reference a common clock source. If you cannot configure a synchronized system, then you can configure multiple clock sources on your network as long as they are accurate enough that the clocking on both clock sources will match.
You can statically configure the Cisco MC3810 to receive or generate clocking using one of the following scenarios:
![]() |
Note Configuring a clock source from the digital voice module (DVM) is supported if the installed DVM is either hardware version 4.50 or later, and the system control board (SCB) is version 6.05 or later. To verify the hardware version of the SCB, enter the show version command and check the entry for the Cisco MC3810 processor revision. To verify the hardware version of the DVM, enter the show controller T1/E1 command and check the HWVersion entry. |
For more information on how to configure clocking for these scenarios, see the "Configuring the Clock Source for the Cisco MC3810" section later in this chapter.
In addition, you can define a hierarchy of potential clock sources so that when the primary clock source goes down, the Cisco MC3810 can automatically switch to a backup clock source. For more information, see the "Configuring a Hierarchy of Clock Sources for Backup Purposes" section later in this chapter.
Because of the different ways that PSTNs provide clocking and how data networks provide clocking, there may be incompatibilities when the Cisco MC3810 is used to integrate voice and data networks. As a result, the Cisco MC3810 must synchronize the disparate clocking, and you must be careful in how you configure your clock sources. The clocking can be derived from one of the following sources:
Depending on the configuration, you must determine how to configure the appropriate interface on the Cisco MC3810 for the clocking configuration. Each interface provides different clocking support, and depending on the interface used, the commands required to configure the clocking are different. You must also determine whether the Cisco MC3810 interface will be the DCE or the DTE in the configuration.
The following sections provide configuration tasks:
![]() |
Note The procedures in this section statically configure the clock source for the interfaces. If the clock source fails, these procedures do not configure a backup clock source. For information on configuring a hierarchy of backup clock sources, see the "Configuring a Hierarchy of Clock Sources for Backup Purposes" section later in this chapter. |
When the Cisco MC3810 recovers clocking from a network device attached to a T1 or E1 controller, the clock recovery circuit on the controller will place a recovered 2 MHz clock on the common circuit toward the network clock phase-lock-loop (PLL). Once the network-clock PLL circuit receives the valid 2 MHz clock from the controller, the network clock PLL synchronizes to the recovered clock and redistributes the clock to the rest of the system. The other T1/E1 controller and the serial ports on the Cisco MC3810 then derive their clocking from the network clock PLL.
When you configure a T1/E1 controller to recover clocking from a network device, configure the clock-source controller configuration command to the line setting.
![]() |
Note Do not configure both T1/E1 controllers to the line setting. Doing so will cause both controllers to attempt to drive the network clock PLL at the same time. If you configure both T1/E1 controllers to line, there will be clocking conflicts. You will not receive an error message if you misconfigure the clocking in this way. Instead, configure one controller for line timing and the other controller for internal or loop timing. The one exception to this rule is if you configure backup clocks to dynamically activate if the primary clock fails. For more information, see the "Configuring a Hierarchy of Clock Sources for Backup Purposes" section later in this chapter. |
Figure 117 shows an example in which the Cisco MC3810 obtains its clock source from a network device attached to controller T1/E1 0 (the MFT).

To make sure the network is synchronized, configure the attached network device that obtains its clocking from the Cisco MC3810 (from the T1/E1 controller clock source set to internal) to derive its clock from the T1/E1 signal sent by the Cisco MC3810. If the T1/E1 signal received from the attached network device is not synchronous with the Cisco MC3810 network clock, then frame and clock slips will occur at the T1/E1 controller, causing loss of data.
To configure the Cisco MC3810 to obtain its clock source from a network device attached to controller T1/E1 0, use the following commands beginning in global configuration mode:
| Command | Purpose | |
|---|---|---|
Step 1 | Router(config)# controller {T1 | E1} 0
| Enters controller configuration mode for controller T1/E10. |
Step2 | Router(config-controller)# clock source line | Configures controller T1/E1 0 to obtain the CiscoMC3810 clock source from an attached network device. |
Step3 | Router(config)# controller {T1 | E1} 1
| Enters controller configuration mode for controller T1/E11. |
Step4 | Router(config-controller)# clock source internal | Configures controller T1/E1 1 to obtain its clocking from the internal network clock PLL. |
Step5 | Router(config-controller)# network-clock base-rate
{56k | 64k}
| Sets the network clock base rate for the serial ports. The default is 56k. |
Step6 | Router(config)# interface serial 0 | Enters interface configuration mode for serial 0. |
Step7 | Router(config-if)# clock rate network-clock rate |
Repeat Steps 6 and 7 for serial port 1. |
Step8 | Router(config)# exit | Exits configuration mode. |
Step9 | Router# show network-clocks | Displays the network clock configuration. |
Figure 118 shows an example in which the Cisco MC3810 obtains its clock source from a network device attached to controller T1/E1 1 (the DVM).

To configure the Cisco MC3810 to obtain its clock source from a network device attached to controller T1/E1 1, use the following commands beginning in global configuration mode:
| Command | Purpose | |
|---|---|---|
Step1 | Router(config)# controller {T1 | E1} 1
| Enters controller configuration mode for controller T1/E11. |
Step2 | Router(config-controller)# clock source line | |
Step3 | Router(config)# controller {T1 | E1} 0
| Enters controller configuration mode for T1/E1 0 to configure the clock source for the MFT. |
Step4 | Router(config-controller)# clock source internal | Configures controller T1/E1 1 to obtain its clocking from the internal network clock PLL. |
Step5 | Router(config-controller)# network-clock base-rate
{56k | 64k}
| Sets the network clock base-rate for the serial ports. The default is 56k. |
Step6 | Router(config)# interface serial 0 | Enters interface configuration mode for serial 0. |
Step7 | Router(config-if)# clock rate network-clock rate |
Repeat Steps 6 and 7 for serial port 1. |
Step8 | Router(config)# exit | Exits configuration mode. |
Step9 | Router# show network-clocks | Displays the network clock configuration. |
When you configure a T1/E1 controller to loop-time the clocking back to a network device, you configure the clock-source controller command to the loop-timed setting. The clock-source command on the other T1/E1 controller should in most cases be set to the internal setting.
When a controller's clock source is set to loop-timed, the internal network clock PLL is placed into free-running mode.
![]() |
NoteUse caution when configuring the controller clock source to loop-timed. This setting should only be used in certain cases, such as when there are two master clocks but you can only obtain clocking from one master clock at a time. Using the functionality to configure a hierarchy of clock sources, you can configure a controller set to loop-timed clock source to become the CiscoMC3810 clock source if the primary clock source fails. For more information about configuring a hierarchy of clock sources, see the "Configuring a Hierarchy of Clock Sources for Backup Purposes" section later in this chapter. |
Figure 119 shows an example of a configuration in which the input clock source on the MFT is loop-timed back to the clock source device.

To configure the Cisco MC3810 to use loop-timed clock mode on controller T1/E1 0, use the following commands beginning in global configuration mode:
| Command | Purpose | |||
|---|---|---|---|---|
Step1 | Router(config)# controller {T1 | E1} 0
| Enters controller configuration mode for T1/E1 0. | ||
Step2 | Router(config-controller)# clock source loop-timed | Configures controller T1/E1 0 to take the clock from the receive line and send it back to the source. | ||
Step3 | Router(config)# controller {T1 | E1} 1
| Enters controller configuration mode for T1/E1 1. | ||
Step4 | Router(config-controller)# clock source internal | Configures controller T1/E1 1 to obtain its clocking from the internal network clock PLL.
| ||
Step5 | Router(config-controller)# network-clock base-rate
{56k|64k}
| Sets the network clock base rate for the serial ports. The default is 56k. | ||
Step6 | Router(config)# interface serial 0 | Enters interface configuration mode for serial 0. | ||
Step7 | Router(config-if)# clock rate network-clock rate | Configures the serial 0 network clock speed for DCE mode. The rate must be a multiple of the value set with the network-clock base-rate command in Step5. Repeat Steps 6 and 7 for serial port 1. | ||
Step8 | Router(config)# exit | Exits configuration mode. | ||
Step9 | Router# show network-clocks | Displays the network clock configuration. |
If serial interface 0 is configured as a DTE, it can accept clocking from the attached DCE and use the clocking to drive the network-clock PLL on the Cisco MC3810. The clocking is then distributed to the T1/E1 controllers and to serial interface1.
Because the input to the network clock PLL must be 2 MHz, a clock multiplier circuit is used to multiply the incoming clock on serial 0 to 2 MHz in 8 Hz increments. This multiplier is configured using the clock-rate line serial interface command. This command is valid only when serial 0 is configured as the DTE device.
![]() |
NoteTo recover clocking over serial interfaces, the Cisco MC3810 can recover clocking only from a device attached to serial 0 in DTE mode. It cannot recover clocking from a device attached to serial 1, or to serial 0 in DCE mode. |
![]() |
NoteWhen Q.SIG, ISDN, or the BRI Voice Module (BVM) is enabled, Serial 1 is normally configured for DCE. If Serial 1 is configured as a DTE, you need to make sure that the clock driving serial 1 comes from the same source as the clock driving the system. When Q.SIG, ISDN, or the BVM is enabled, the CPU takes the serial 1 data in time-slot mode that is driven by the system clock. If this clock is different from the clock driving the data into Serial 1, there will be cyclic redundancy check (CRC) errors and the line will not come up. |
Figure 120 shows an example of the Cisco MC3810 obtaining clocking from a network device attached to Serial 0.

To configure the Cisco MC3810 to use a network device attached to serial port 0 as the clock source, use the following commands beginning in global configuration mode:
| Command | Purpose | |
|---|---|---|
Step1 | Router(config)# network-clock base-rate {56k|64k}
| Sets the network clock base rate for the serial ports. The default is 56k. |
Step2 | Router(config)# network-clock-select 1 serial 0 | Configures the network clock PLL to use the multiplied 2Hz. clock from serial 0. |
Step3 | Router(config)# interface serial 0 | Enters interface configuration mode for serial 0. |
Step4 | Router(config-if)# clock rate line rate | |
Step5 | Router(config)# interface serial 1 | Enters interface configuration mode for serial 1. |
Step6 | Router(config-if)# clock rate network-clock rate | Configures the network clock line rate for serial 1 acting in DCE mode. The rate must be a multiple of the value set with the network-clock base-rate command and must match the value set in Step 1. |
Step7 | Router(config)# controller {T1 | E1} 0
| Enters controller configuration mode for T1/E1 0. |
Step8 | Router(config-controller)# clock source internal | Configures controller T1/E1 0 to obtain its clocking from the internal network clock PLL. |
Step9 | Router(config)# controller {T1 | E1} 1
| Enters controller configuration mode for T1/E1 1. |
Step10 | Router(config-controller)# clock source internal | Configures controller T1/E1 1 to obtain its clocking from the internal network clock PLL. |
Step11 | Router(config)# exit | Exits configuration mode. |
Step12 | Router# show network-clocks | Displays the network clock configuration. |
Figure 121 shows an example of the Cisco MC3810 using its internal clock source and propagating it outward onto the associated networks.

To configure the Cisco MC3810 to use its internal 2 MHz clock as the clock source, use the following commands beginning in global configuration mode:
| Command | Purpose | |
|---|---|---|
Step1 | Router(config)# network-clock base-rate {56k|64k}
| Sets the network clock base rate for the serial ports. The default is 56k. |
Step2 | Router(config)# interface serial 0 | Enters interface configuration mode for serial 0. |
Step3 | Router(config-if)# clock rate network-clock rate | Configures the network clock line rate on serial 0 acting in DCE mode. The rate must be a multiple of the value set with the network-clock base-rate command and must match the value set in Step 1. |
Step4 | Router(config)# interface serial 1 | Enters interface configuration mode for serial 1. |
Step5 | Router(config-if)# clock rate network-clock rate | Configures the network clock line rate on serial 1 acting in DCE mode. The rate must be a multiple of the value set with the network-clock base-rate command and must match the value set in Step 1. |
Step6 | Router(config)# controller {T1 | E1} 0
| Enters controller configuration mode for T1/E1 0. |
Step7 | Router(config-controller)# clock source internal | Configures controller T1/E1 0 to obtain its clocking from the internal network clock PLL. |
Step8 | Router(config)# controller {T1 | E1} 1
| Enters controller configuration mode for T1/E1 1. |
Step9 | Router(config-controller)# clock source internal | Configures controller T1/E1 1 to obtain its clocking from the internal network clock PLL. |
Step10 | Router(config)# exit | Exits configuration mode. |
Step11 | Router# show network-clocks | Displays the network clock configuration. |
![]() |
NoteWhen using the internal Cisco MC3810 clock source as the master clock, make sure to configure any other network devices directly attached to the Cisco MC3810 T1/E1 controllers and serial ports to obtain their clocking from the Cisco MC3810. |
Using the network-clock-select command, you can configure a dynamic hierarchy of clock sources that are used if the primary clock source fails. Each clock source is assigned a priority. A higher priority number of a clock source places that source higher in the clocking hierarchy. The highest clock source priority is used as the default.
When a clock source fails, the Cisco MC3810 switches to the clock source in the hierarchy with the next highest priority. For example, if the clock source with priority 1 (the highest priority) fails, the Cisco MC3810 switches to the clock source with priority 2. Then, if the clock source with priority2 fails, the Cisco MC3810 then switches to the clock source with priority 3 (assuming that the clock source with priority 1 has not become active in the meantime.)
If the module providing the clock experiences a failure (for example, if the T1/E1 controller experiences a Loss-of-Signal or Loss-of-Frame), then the clock source will be switched.
![]() |
NoteIf you shut down a controller that is the current clock source, the shutdown will not cause the clock source to be switched. |
To configure a hierarchy of clock sources for backup purposes, use the following commands beginning in global configuration mode:
| Command | Purpose | |||
|---|---|---|---|---|
Step1 | Router(config)# network-clock-select 1-4 [serial0 | system | controller] |
Repeat Step 1, specifying each clock source with a lower priority. If the clock source with the highest priority fails, the clock source with the next priority is used. You can configure four clock sources: one primary clock source and up to three backup clock sources. For example, if serial 0 is priority 1 and controller T1 0 is priority2, when serial 0 goes down the system will switch to controller T1 0 as the clock source. | ||
Step2 | Router(config)# network-clock-switch [switch-delay | never] [restore-delay | never] | |||
Step3 | Router(config)# controller {T1 | E1} {0|1}
| If one of the controllers will be used as a clock source in the hierarchy, enter controller configuration mode for the T1/E1 controller. | ||
Step4 | Router(config-controller)# clock source line | Configures the controller to obtain the Cisco MC3810 clock source from an attached network device. If the other controller will be used as a potential clock source in the hierarchy, repeat Steps 3 and 4.
| ||
Step5 | Router(config)# interface serial 0 | If serial interface 0 will be used as a potential clock source in the hierarchy, enter interface configuration mode for serial 0. | ||
Step6 | Router(config-if)# clock rate line rate | Configures the network clock line rate on serial 0 acting in DTE mode. The rate must be a multiple of the value set with the network-clock base-rate command. | ||
Step7 | Router(config)# exit | Exits configuration mode. | ||
Step8 | Router# show network-clocks | Displays the network clock configuration. |
When you configure a hierarchy of clock sources, each potential clock source must be preconfigured to a mode that enables the Cisco MC3810 to derive the clock from that source. For example, if a controller will be a potential clock source, the controller clock source must be configured to line. If the controller clock source is configured to internal, the controller cannot be configured as a potential backup clock source using the network-clock-select command.
In the normal configuration, configuring both controllers to clock source line causes clocking conflicts. However, when configuring a hierarchy of clock sources, because only one controller is used as the primary clock source at one time, the conflict is prevented.
The following rules apply to configuring the clock source hierarchy:
The following is a configuration example showing a hierarchy of clock sources:
network-clock-select 1 t1 0 network-clock-select 2 t1 1 network-clock-select 3 serial0 network-clock-select 4 system network-clock-switch 10 10 controller t1 0 clock source line controller t1 1 clock source line interface serial0 clock rate line 64000
In this configuration, controller T1 0 is the primary clock source, and the clock source is configured to line. Controller T1 1 is a backup clock source and although the clock source is configured to line, the system temporarily sets the clock source to the loop-timed state.
If the controller T1 0 clock source fails, the system switches to use controller T1 1 as the clock source. The clock source loop-timed "set state" on controller T1 1 is switched to the preconfigured line state.
![]()
![]()
![]()
![]()
![]()
![]()
![]()
Posted: Thu Jul 27 00:00:59 PDT 2000
Copyright 1989-2000©Cisco Systems Inc.