Avaya 2330/4134 - Network Clock Misconfigured, Does Not Lock, or Displays as Bad Clock

Network clock misconfigured, does not lock, or displays as bad
clock
In
some cases, the remote end of the link reports clock slip errors or frame drop errors on the
physical link. In other cases, the clock source configured on the Secure Router 2330/4134
does not lock to the peer, or the clock state displays a bad clock.
To troubleshoot these problems, verify the clock configuration on the Secure Router
2330/4134.
Make sure that the Secure Router 2330/4134 is configured as the clock slave to the remote
end and the remote end is configured as the clock master. If both the Secure Router 2330/4134
and the peer are configured as slaves, neither end of the link can lock to the external clock.
To display the clock configuration, enter the show network-clocks command.
Figure 52: show network-clocks sample output for clock source
In
the preceding figure, there is no clock configured and the Secure Router 2330/4134 is free-
running as the clock master.
The following figure shows an example of a bad clock source.
Troubleshooting a SIP Media Gateway problem
320 Troubleshooting August 2013
Comments? infodev@avaya.com