Got it. Thanks! ________________________________
From: Joe Astorino [mailto:[email protected]] Sent: Saturday, July 04, 2009 11:07 AM To: Meraz, Richard Cc: [email protected]; CCIE OSL Subject: Re: [OSL | CCIE_RS] Vol2 Sect8 Task6.4 Basically it is using it's own clock as the source. So, on R1 the "client" 127.127.7.1 is querying itself. If you don't have that in there, it won't sync properly On Sat, Jul 4, 2009 at 2:00 PM, Meraz, Richard <[email protected]> wrote: Hi Joe, I see the 127.127.7.1 ref id on R1, the NTP server, but in the task we are asked only R2 to query for time. Why do we have to permit our own internal time source? ________________________________ From: Joe Astorino [mailto:[email protected]] Sent: Saturday, July 04, 2009 10:56 AM To: Meraz, Richard; [email protected]; CCIE OSL Subject: Re: [OSL | CCIE_RS] Vol2 Sect8 Task6.4 Hey Richard, It is basically the internal NTP address. Regards, Joe Astorino CCIE #24347 (R&S) Sr. Support Engineer - IPexpert, Inc. URL: http://www.IPexpert.com ________________________________ From: "Meraz, Richard" Date: Sat, 4 Jul 2009 10:49:39 -0700 To: <[email protected]> Subject: [OSL | CCIE_RS] Vol2 Sect8 Task6.4 The solution requires configuring: ntp access-group serve-only 2 access-list 2 permit 10.0.0.2 access-list 2 permit 127.127.7.1 What is the 127.127.7.1 permitting? Thanks, Rich -- Regards, Joe Astorino CCIE #24347 (R&S) Sr. Support Engineer - IPexpert, Inc. URL: http://www.IPexpert.com
