Although it appears you have it enabled, not having the network-clock
participation set correctly will render the network-clock synchronization
ineffective for the NIM with the port your trying to clock source on.
Yeah, but I can't enable it:
ILNOVOIPISR01(config)#network-clock participate 0
G.781 based clock selection process is enabled Please unconfigure G.781
based configuration before configuring network-clock participate config
command
ILNOVOIPISR01(config)#network-clock participate 1
G.781 based
What is the output of show platform hardware subslot 0/1 module device
networkclock
assuming the slot/subslot of the desired line clock is on 0/1
Sent from my iPad
> On Oct 11, 2015, at 12:42 PM, Jonathan Charles wrote:
>
> Yeah, but I can't enable it:
>
>
>
ILNOVOIPISR01#show platform hardware subslot 0/1 module device networkclock
primary clock 0, secondary clock 255, ntwk_clk_selected Yes,
ntwk_clk_participate Yes, current clock = 0
PLL status= 1, and cntl = 17
ILNOVOIPISR01#
ILNOVOIPISR01#show platform hardware subslot 0/2 module device
I think the automatic already handles that
ILNOVOIPISR01(config)#network-clock synchronization participate 0/1
Slot 0 subslot 1 is already enabled for network clocking. Command Aborted.
ILNOVOIPISR01(config)#
Jonathan
On Sun, Oct 11, 2015 at 12:41 PM, Ryan Huff
If there are no calls active (and haven't been for awhile) the slips will
usually clear. However, it will likely start slipping again once calls start
signaling (assuming there is still an underlying issue with network clock
synchronization).
Sent from my iPad
> On Oct 11, 2015, at 5:02 PM,
Here is the relevant portion of a isr4k humming along as we speak, with no
clock slippage (excuse the scrunchiness of the output, SSHTerm on my iPad is
limited and there is a Rocky marathon on TV ... so I ain't moving ;) ).
Granted, this is one PRI and not 10 in two different modules but the