All - We moved our demark on Saturday, and had to drop all of our existing PRI and MPLS circuits for the cut-over. Post cut-over, Call Manager came back on-line. Call's were coming in and everything seemed fine. This morning, I'm getting the following error message from my subscribers unable to reach my publisher...
7/13/2015 5:11 User.Critical ablcucmsub01 136461: : ntpRunningStatus.sh: Primary node NTP server, ablcucmpub01, is currently inaccessible or down. Verify the network between the primary and secondary nodes. Check the status of NTP on both the primary and secondary nodes via CLI 'utils ntp status'. If the network is fine, try restarting NTP using CLI 'utils ntp restart'.
7/13/2015 5:11 User.Critical ablcucmsub02 934: : ntpRunningStatus.sh: Primary node NTP server, ablcucmpub01, is currently inaccessible or down. Verify the network between the primary and secondary nodes. Check the status of NTP on both the primary and secondary nodes via CLI 'utils ntp status'. If the network is fine, try restarting NTP using CLI 'utils ntp restart'.
When I ran "utils ntp status", I received this output...
ntpd (pid 28514) is running...
remote refid st t when poll reach delay offset jitter
==============================================================================
x172.17.1.1 CHU_AUDIO(1) 8 u 742 1024 377 0.791 -841.74 5.586
x172.19.1.1 CHU_AUDIO(1) 8 u 324 1024 377 2.233 -373.03 3.683
synchronised to unspecified at stratum 9
time correct to within 2379 ms
polling server every 1024 s
Current time in UTC is : Mon Jul 13 15:04:22 UTC 2015
Current time in America/Chicago is : Mon Jul 13 10:04:22 CDT 2015
I am noticing a little "static" on or PRI's when I make calls, so this could be a clocking issue. Here is my question: Do I dare run 'utils ntp restart' in the middle of the day, or will this drop calls? What other caveats will I experience? Since this is our clocking, I'm thinking that this will drop calls. I read of problems with Unity after restarting this service.
Any advice would be helpful
7/13/2015 5:11 User.Critical ablcucmsub01 136461: : ntpRunningStatus.sh: Primary node NTP server, ablcucmpub01, is currently inaccessible or down. Verify the network between the primary and secondary nodes. Check the status of NTP on both the primary and secondary nodes via CLI 'utils ntp status'. If the network is fine, try restarting NTP using CLI 'utils ntp restart'.
7/13/2015 5:11 User.Critical ablcucmsub02 934: : ntpRunningStatus.sh: Primary node NTP server, ablcucmpub01, is currently inaccessible or down. Verify the network between the primary and secondary nodes. Check the status of NTP on both the primary and secondary nodes via CLI 'utils ntp status'. If the network is fine, try restarting NTP using CLI 'utils ntp restart'.
When I ran "utils ntp status", I received this output...
ntpd (pid 28514) is running...
remote refid st t when poll reach delay offset jitter
==============================================================================
x172.17.1.1 CHU_AUDIO(1) 8 u 742 1024 377 0.791 -841.74 5.586
x172.19.1.1 CHU_AUDIO(1) 8 u 324 1024 377 2.233 -373.03 3.683
synchronised to unspecified at stratum 9
time correct to within 2379 ms
polling server every 1024 s
Current time in UTC is : Mon Jul 13 15:04:22 UTC 2015
Current time in America/Chicago is : Mon Jul 13 10:04:22 CDT 2015
I am noticing a little "static" on or PRI's when I make calls, so this could be a clocking issue. Here is my question: Do I dare run 'utils ntp restart' in the middle of the day, or will this drop calls? What other caveats will I experience? Since this is our clocking, I'm thinking that this will drop calls. I read of problems with Unity after restarting this service.
Any advice would be helpful