Of Course :)
On dynamips with 12.4(15)T14, saw the same behaviour during vrack lab
---------------------------------------------
BB1
interface FastEthernet0/0
ip address 166.12.21.21 255.255.255.224
duplex auto
speed auto
ntp multicast 239.21.21.21
ntp master
BB1(config)#do sh ip pim int
Address Interface Ver/ Nbr Query DR DR
Mode Count Intvl Prior
BB1(config)#do debu ntp pac
NTP packets debugging is on
BB1(config)#
Mar 1 00:11:33.951: NTP: xmit packet to 239.21.21.21:
Mar 1 00:11:33.951: leap 0, mode 5, version 3, stratum 1, ppoll 64
Mar 1 00:11:33.955: rtdel 0000 (0.000), rtdsp 0002 (0.031), refid 4C4F434C
(76
.79.67.76)
Mar 1 00:11:33.955: ref C029457D.F3B53AE2 (00:10:37.951 UTC Fri Mar 1
2002)
Mar 1 00:11:33.955: org 00000000.00000000 (00:00:00.000 UTC Mon Jan 1
1900)
Mar 1 00:11:33.955: rec 00000000.00000000 (00:00:00.000 UTC Mon Jan 1
1900)
Mar 1 00:11:33.959: xmt C02945B5.F3B4EF67 (00:11:33.951 UTC Fri Mar 1
2002)
---------------------------------------------
R1
interface FastEthernet0/0
ip address 166.12.21.1 255.255.255.224
duplex auto
speed auto
ntp multicast client 239.21.21.21
end
RR1#sh ip pim int
Address Interface Ver/ Nbr Query DR DR
Mode Count Intvl Prior
R1#debu ntp pac
NTP packets debugging is on
R1#
Mar 1 00:11:33.968: NTP: rcv packet from 166.12.21.21 to 239.21.21.21 on
FastEt
hernet0/0:
Mar 1 00:11:33.972: leap 0, mode 5, version 3, stratum 1, ppoll 64
Mar 1 00:11:33.972: rtdel 0000 (0.000), rtdsp 0002 (0.031), refid 4C4F434C
(76
.79.67.76)
Mar 1 00:11:33.972: ref C029457D.F3B53AE2 (00:10:37.951 UTC Fri Mar 1
2002)
Mar 1 00:11:33.972: org 00000000.00000000 (00:00:00.000 UTC Mon Jan 1
1900)
Mar 1 00:11:33.976: rec 00000000.00000000 (00:00:00.000 UTC Mon Jan 1
1900)
Mar 1 00:11:33.976: xmt C02945B5.F3B4EF67 (00:11:33.951 UTC Fri Mar 1
2002)
Mar 1 00:11:33.976: inp C02945B5.F7D9B82D (00:11:33.968 UTC Fri Mar 1
2002)
R1#sh ntp statu
Clock is synchronized, stratum 2, reference is 166.12.21.21
nominal freq is 250.0000 Hz, actual freq is 250.0000 Hz, precision is 2**18
reference time is C02945F5.FB244E0D (00:12:37.981 UTC Fri Mar 1 2002)
clock offset is 0.8290 msec, root delay is 103.94 msec
root dispersion is 7883.27 msec, peer dispersion is 7882.42 msec
Regards
Morgan Charpentier
2010/11/21 Marko Milivojevic <[email protected]>
> I had mixed success without having PIM enabled on the interface, hence
> the solution with PIM. Perhaps you are right. Do you have show/debug
> to prove it works otherwise? :-)
>
> --
> Marko Milivojevic - CCIE #18427
> Senior Technical Instructor - IPexpert
>
> FREE CCIE training: http://bit.ly/vLecture
>
> Mailto: [email protected]
> Telephone: +1.810.326.1444
> Web: http://www.ipexpert.com/
>
> On Sun, Nov 21, 2010 at 15:43, Morgan Charpentier
> <[email protected]> wrote:
> > Hello,
> >
> > When using ntp multicast on the same segment I think we don't need Pim
> nor
> > ip mulitcast-routing, are the sender is directly connected, and labing it
> > prove it.
> > On DSG it seems that each time ntp multicast is used pim and
> > multicast-routing is activated like in lab 2 volume 3 task 7.2 Is it only
> a
> > best practice ? does on real exam I will lose point if i don't use pim
> but
> > ntp is well sync by multicast ?
> >
> > thanks for your reply
> >
> > _______________________________________________
> > For more information regarding industry leading CCIE Lab training, please
> > visit www.ipexpert.com
> >
> >
>
_______________________________________________
For more information regarding industry leading CCIE Lab training, please visit
www.ipexpert.com
