From: Quetta Walla (quetta_1@lycos.com)
Date: Sun Mar 12 2006 - 16:47:23 GMT-3
Hi,
The difference is that with ntp server command, the server only provides timing. With ntp peer command, the routers can provide timing for each other depening upon which one has better strtum configured.
> ----- Original Message -----
> From: xprtofnet <xprtofnet@yahoo.com>
> To: ccielab@groupstudy.com
> Subject: NTP Failover - server/peer - whats the difference ?
> Date: Fri, 10 Mar 2006 12:26:35 -0800 (PST)
> 
> 
> Folks,
> 
> any inputs are appreciated.
> 
> I have tested both cmds [server/peer] and in both
> cases ntp fails over to the other time source.
> 
> You may have to copy and paste the following output to
> a notepad to see it properly. I was expecting that ntp
> will not fail over if i use the following config
> [server/server]. But it did in ~510 secs. as it does
> with the peer cmd [server/peer]
> 
> what is the difference between the two cmds ? i know
> documentation say about using the peer cmd when
> configuring a symetric time source but why use it peer
> cmd when i can use the same result with server cmd ?
> 
> I tested clients (configured with server cmd) giving
> time to other clients and peers to peers. I do not see
> the difference here...as per my test.
> 
> requesting inputs.
> 
> 
> ntp server 130.1.1.1 prefer
> ntp server 130.1.3.3
> 
> 
> 
>        address         ref clock     st  when  poll
> reach  delay  offset    disp
> *~130.1.1.1        .LOCL.            1   510    64
> 200    40.0   -0.14  16000.
> +~130.1.3.3        .LOCL.            1    40    64
> 377    40.0  416102     4.0
>   * master (synced), # master (unsynced), + selected, -
> candidate, ~ configured
> R2(config)#do sho nt as
> 
>        address         ref clock     st  when  poll
> reach  delay  offset    disp
> *~130.1.1.1        .LOCL.            1   511    64
> 200    40.0   -0.14  16000.
> +~130.1.3.3        .LOCL.            1    41    64
> 377    40.0  416102     4.0
>   * master (synced), # master (unsynced), + selected, -
> candidate, ~ configured
> R2(config)#do sho nt as
> 
>        address         ref clock     st  when  poll
> reach  delay  offset    disp
>   ~130.1.1.1        .LOCL.            1   512    64
> 0    40.0   -0.14  16000.
> *~130.1.3.3        .LOCL.            1    42    64
> 377    40.0  416102     4.0
>   * master (synced), # master (unsynced), + selected, -
> candidate, ~ configured
> 
> 
> 
> R2(config)#do sho nt as de
> 130.1.1.1 configured, insane, invalid, stratum 1
> ref ID .LOCL., time AEEF21BE.ED424A80 (15:02:06.926
> EST Fri Jan 1 1993)
> our mode client, peer mode server, our poll intvl 64,
> peer poll intvl 64
> root delay 0.00 msec, root disp 0.03, reach 0, sync
> dist 6351134.750
> delay 39.99 msec, offset -0.1405 msec, dispersion
> 16000.00
> precision 2**18, version 3
> org time 00000000.00000000 (19:00:00.000 EST Thu Dec
> 31 1899)
> rcv time 00000000.00000000 (19:00:00.000 EST Thu Dec
> 31 1899)
> xmt time C7BC5E1B.27DBAB24 (15:20:43.155 EST Fri Mar
> 10 2006)
> filtdelay =     0.00    0.00    0.00    0.00    0.00
>   0.00    0.00    0.00
> filtoffset =    0.00    0.00    0.00    0.00    0.00
>   0.00    0.00    0.00
> filterror =  16000.0 16000.0 16000.0 16000.0 16000.0
> 16000.0 16000.0 16000.0
> 
> 130.1.3.3 configured, our_master, sane, valid, stratum
> 1
> ref ID .LOCL., time C7BC5E1F.1572E918 (15:20:47.083
> EST Fri Mar 10 2006)
> our mode client, peer mode server, our poll intvl 64,
> peer poll intvl 64
> root delay 0.00 msec, root disp 0.03, reach 7, sync
> dist 3898.010
> delay 39.99 msec, offset 0.0891 msec, dispersion
> 3877.99
> precision 2**18, version 3
> org time C7BC5E31.301292A0 (15:21:05.187 EST Fri Mar
> 10 2006)
> rcv time C7BC5E31.3424C227 (15:21:05.203 EST Fri Mar
> 10 2006)
> xmt time C7BC5E31.27DAFF86 (15:21:05.155 EST Fri Mar
> 10 2006)
> filtdelay =    47.99   39.99   39.99    0.00    0.00
>   0.00    0.00    0.00
> filtoffset =    8.10    0.09    0.07    0.00    0.00
>   0.00    0.00    0.00
> filterror =     0.02    0.99    1.97 16000.0 16000.0
> 16000.0 16000.0 16000.0
> 
> 
> __________________________________________________
> Do You Yahoo!?
> Tired of spam?  Yahoo! Mail has the best spam protection around
> http://mail.yahoo.com
> 
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
>
--
This archive was generated by hypermail 2.1.4 : Sat Apr 01 2006 - 10:07:38 GMT-3