cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
454
Views
0
Helpful
6
Replies

Error message during setup second node for CUCM7.0.1

kevintang
Level 1
Level 1

Hi,

Any one see this error message during the second node setup for CUCM 7.0.1?

I use the same process and do not have this issue for CUCM6.X.

Regards

6 Replies 6

kevintang
Level 1
Level 1

see the screen dump!

The message explained itself - not able to sync with NTP.

The best practice is NOT to use NTP/DNS/SMTP during install. You'll have the chance to configure those after install.

sorry, didn't notice that you were installing 2nd node.

You'll have to wait until the 1st node synchronize up with NTP before installing 2nd node. If 1st node didn't sync to NTP, 2nd node won't sync to 1st node.

Workarounds:

1) Find out why 1st node didn't sync up to NTP.

or

2) Delete NTP server from 1st node.

My blog:

http://htluo.blogspot.com/

Hi, Mr. Luo

I can see the 1st node did sync up with NTP server 10.15.15.2

admin:utils ntp status

ntpd (pid 5505) is running...

remote refid st t when poll reach delay offset jitter

==============================================================================

127.127.1.0 LOCAL(0) 10 l 11 64 377 0.000 0.000 0.004

*10.15.15.2 128.250.36.2 2 u 267 1024 377 1.949 6.925 2.740

synchronised to NTP server (10.15.15.2) at stratum 3

time correct to within 78 ms

polling server every 1024 s

Current time in UTC is : Sun Jan 18 19:05:11 UTC 2009

Current time in Pacific/Auckland is : Mon Jan 19 08:05:11 NZDT 2009

admin:

Hi Kevin,

The second reference in the attached screen capture is asking about whether or not the second node was added to the Pub/1st node (server list) before starting to build.

Just checking,

Rob

Hi, Rob

I added the second node in the Pub server list before I start in stall the second node. This process is same as in CUCM 6.X.

I only have this NTP issue in CUCM7.X second node install. I do not meet this problem during CUCM 6.X installation.

It looks like I am the only person got this issue?

Regards

Kevin