Hello Experts,
Firstly, a hello to eveyone.  I have been a reader of this for many months but 
am only now reaching the point where I can starting firing off meaningful 
questions to you guys.
 
I hope I'm not being stupid here....
 
Was doing IPExpert R&S, WB2, Lab 8 Task 7.4.  Topolgy is:
 
 
BB1 Eth 0/0 ->VLANA -> Fast0/0 R1 -> F0/1 R1 -> VLAN B -> G0/0 R2.
 
 
The task involves setting up R1 as an NTP master, R2 as NTP client, bit of 
authentication, bit of security to ensure only certain devices can obtain time. 
 That is all fine.  However, part of the Task was:
 
"Hosts on VLANA should receive time without asking.  Do not configure any 
commands under R1 Fast0/0."
 
My initial thought of:
 
R1
==
 
int fast0/0
ntp broadcast
 
was shot down in flames by not being able to configure under R1 F0/0.
 
 
The DSG uses:
 
R1
==
 
int fast0/1
ntp broadcast
 
Em....isn't this broadcasting time out onto Vlan B and not Vlan A??  Am I 
missing somthing?
 
If I am correct, and that the DSG would not actually satisfy the lab 
requirement, I then turn to how you would actually do this?
 
Several thoughts occurred to me, and I just wondered if anyone else, when doing 
this lab, tried any of these!!
 
OPTION 1
 
Set up BB1 to be an NTP client of R2, and use BB2 to do the broadcasting onto 
Vlan A, but from BB1 Eth0/0.  Fine for a practice lab, but no good in the real 
exam as you don't have access to BB1.
 
OPTION 2
 
Similar idea.  Use one of the Cat switches as an NTP client of R2, create SVI 
INT VLAN "A" on it, and use "ntp broadcast" under that interface.
 
OPTION 3 
 
Not so sure about this one.  Turn on ntp multicast on R2 G0/0 heading back 
towards R1 F0/1 and put an "ip multicast helper-address" on R1 F0/1 to convert 
the NTP multicast address into a directed broadcast for the hosts on VLAN A.
 
OPTION 4
 
Do what the DSG says, but add vlan bridging on a Cat switch between Vlan A and 
Vlan B.  Horrible, I know....
 
 
Am interested to hear your views!!
 
Oh and as another little interesting tidbit.  I think I've come across that 
very rare beast indeed....a mistake in "Routing TCP/IP Volume 2" by 
Doyle/Carroll.  P274 and I quote:
 
"A route with a LOCAL_AS (community) attribute can be advertsied to peers in 
other subautonomous systems within a confederation but cannot be advertised 
outside of the AS that forms the confederation".
 
Isn't this incorrect?  Doesn't that statement define "no-export" conmmunity 
within confederations, with LOCAL_AS meaning "don't advertise outside of my own 
sub-AS"?
 
Regards, George.
 
 
 
 
 
 
 
 
 
 
 
 
                                          
_______________________________________________
For more information regarding industry leading CCIE Lab training, please visit 
www.ipexpert.com

Are you a CCNP or CCIE and looking for a job? Check out 
www.PlatinumPlacement.com

http://onlinestudylist.com/mailman/listinfo/ccie_rs

Reply via email to