Chris, If you see the diagram carefully, you will find the R1 and R5 are interconnecting through the FastEthernet interfaces of each router, they can be considered LAN, but they are not acting as LAN in this scinario, they are just interconnecting with each other.
Always, a good practice is to just define the exact IP address of the interface when advertising a network that is on WAN side ( or i would say between two routers - A link - with the Wildcard 0.0.0.0 ). Defiantly when you are advertising a real LAN network, then do advertise it according to its actual mask ( do you wildcard calculations according to the network subnet mask ). HTH, Amer On Fri, Dec 3, 2010 at 4:30 AM, <[email protected]> wrote: > Send CCIE_RS mailing list submissions to > [email protected] > > To subscribe or unsubscribe via the World Wide Web, visit > http://onlinestudylist.com/mailman/listinfo/ccie_rs > or, via email, send a message with subject or body 'help' to > [email protected] > > You can reach the person managing the list at > [email protected] > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of CCIE_RS digest..." > > > Today's Topics: > > 1. Volume 1 Lab 12.5: Advertising Question (Lemish, Christopher) > 2. Re: Volume 1 Lab 12.5: Advertising Question (marc abel) > 3. Re: Volume 2 , Lab 3 , Qn4.3 (Ananthan) > 4. Re: WORKBOOK 1 - LAB 13 TAKS 1.2 (Jeferson Guardia) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Thu, 2 Dec 2010 16:10:27 -0500 > From: "Lemish, Christopher" <[email protected]> > To: <[email protected]> > Subject: [OSL | CCIE_RS] Volume 1 Lab 12.5: Advertising Question > Message-ID: > <[email protected]> > Content-Type: text/plain; charset="iso-8859-1" > > ? > Guys, > > I was just wondering what the standard practice should be when advertising > a network. The lab guide shows: > > router ospf 1 > network 150.100.35.5 0.0.0.0 area 15 > > ---NOT--- > > router ospf 1 > network 150.100.35.0 0.0.0.255 area 15 > > In 12.4 it says configure OSPF Area 0 on R4, R5, and R6's Frame-Relay > "interface" so do you advertise the specific interface address in this > sitatuation? > In 12.5, it doesn't mention the interface but the config says to advertise > the actual ip address, so I'm wondering when do we know the difference? > > Thank you, > Chris > > > > This email and any files transmitted with it are confidential and are > intended for the sole use of the individual(s) to whom they are properly > addressed. Any use, dissemination or forwarding of this email and any > files transmitted with it by anyone other than the intended recipient(s) > is strictly prohibited. If you have received this email in error, please > notify the sender by replying to this email. Black Box Corporation and > its affiliates reserve the right to scan and monitor all e-mail traffic. > > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: </archives/ccie_rs/attachments/20101202/004d1898/attachment-0001.html> > > ------------------------------ > > Message: 2 > Date: Thu, 2 Dec 2010 15:59:45 -0600 > From: marc abel <[email protected]> > To: "Lemish, Christopher" <[email protected]> > Cc: [email protected] > Subject: Re: [OSL | CCIE_RS] Volume 1 Lab 12.5: Advertising Question > Message-ID: > <[email protected]> > Content-Type: text/plain; charset="iso-8859-1" > > I think it's just a matter of how specific you want to be, obviously > network 150.100.35.0 0.0.0.255 area 15 is going to advertise more possible > interfaces than network 150.100.35.5 0.0.0.0 area 15. I think for the lab > you can do whichever you want including 0.0.0.0 0.0.0.0 area 15 if it meets > your requirements and doesn't advertise too much. > > On Thu, Dec 2, 2010 at 3:10 PM, Lemish, Christopher < > [email protected]> wrote: > > > ? > > Guys, > > > > I was just wondering what the standard practice should be when > advertising > > a network. The lab guide shows: > > > > router ospf 1 > > network 150.100.35.5 0.0.0.0 area 15 > > > > ---NOT--- > > > > router ospf 1 > > network 150.100.35.0 0.0.0.255 area 15 > > > > In 12.4 it says configure OSPF Area 0 on R4, R5, and R6's Frame-Relay > > "interface" so do you advertise the specific interface address in this > > sitatuation? > > In 12.5, it doesn't mention the interface but the config says to > advertise > > the actual ip address, so I'm wondering when do we know the difference? > > > > Thank you, > > Chris > > > > > > > > This email and any files transmitted with it are confidential and are > > intended for the sole use of the individual(s) to whom they are properly > > addressed. Any use, dissemination or forwarding of this email and any > > files transmitted with it by anyone other than the intended recipient(s) > > is strictly prohibited. If you have received this email in error, please > > notify the sender by replying to this email. Black Box Corporation and > > its affiliates reserve the right to scan and monitor all e-mail traffic. > > > > _______________________________________________ > > For more information regarding industry leading CCIE Lab training, please > > visit www.ipexpert.com > > > > > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: </archives/ccie_rs/attachments/20101202/ab68413e/attachment-0001.html> > > ------------------------------ > > Message: 3 > Date: Fri, 3 Dec 2010 07:13:28 +0800 > From: Ananthan <[email protected]> > To: [email protected] > Subject: Re: [OSL | CCIE_RS] Volume 2 , Lab 3 , Qn4.3 > Message-ID: > > <[email protected]<aanlktimwckc4mc791b42%[email protected]> > > > Content-Type: text/plain; charset="iso-8859-1" > > Hi All, > > The Volume 2, Lab 3 , Qn4.3 indicate that " BGP AS178 has 2 equal paths to > AS111 via R5 and R6. Configure R7 ,so R6 is the primary route for all route > originating from AS111 and backup for all other routes. Also R5 should be > the backup for routes coming from AS111 and primary routes for all > others.." > > But solution implies R6 is primary route for all routes including routes > originating from AS111 and all other routes (originating from AS112) .. > Could you please clarify this issue ?? This solution is ok, because its > receiving only one prefix from R5 and R6 (those subnets belongs to AS111) , > but if R7 receive any other prefix from AS112 or AS3550 do we need to > modify > the solution ?? > > Thanks.. > -Ananthan > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: </archives/ccie_rs/attachments/20101203/d945a6e1/attachment-0001.html> > > ------------------------------ > > Message: 4 > Date: Thu, 2 Dec 2010 23:30:48 -0200 > From: Jeferson Guardia <[email protected]> > To: Jason Maynard <[email protected]> > Cc: [email protected], [email protected], Emmanuel > Aramide <[email protected]> > Subject: Re: [OSL | CCIE_RS] WORKBOOK 1 - LAB 13 TAKS 1.2 > Message-ID: > <[email protected]> > Content-Type: text/plain; charset="iso-8859-1" > > Nothing, I am just sharing a rule that I always keep in mind whenever I am > labbing up BGP and need to get stuff up quickly without re-checking. > > 2010/11/30 Jason Maynard <[email protected]> > > > What makes you believe that he is peering using loopbacks? > > > > -----Original Message----- > > From: [email protected] > > [mailto:[email protected]] On Behalf Of Jeferson > Guardia > > Sent: November-30-10 3:15 PM > > To: [email protected]; Emmanuel Aramide; Tyson Scott; > > [email protected] > > Subject: Re: [OSL | CCIE_RS] WORKBOOK 1 - LAB 13 TAKS 1.2 > > > > And you will ALWAYS need the multihop command whenever you are peering > > to an ebgp neighbor thru a loopback. > > > > On 11/29/10, [email protected] <[email protected]> wrote: > > > Solved this one already, I had to add the multihop command on R5 since > > its > > > FR hub-n-spoke and the traffic to R6 from R5 goes throgh R2. So its one > > > extra hop. > > > Sent from my BlackBerryR smartphone provided by mobily > > > > > > -----Original Message----- > > > From: Emmanuel Aramide <[email protected]> > > > Date: Mon, 29 Nov 2010 17:51:43 > > > To: Tyson Scott<[email protected]> > > > Cc: Amer Mustafa<[email protected]>; <[email protected]> > > > Subject: Re: [OSL | CCIE_RS] WORKBOOK 1 - LAB 13 TAKS 1.2 > > > > > > Lets see your interface and igp configs. Not sure whats going on here. > > > > > > Regards > > > > > > Emmanuel > > > > > > On 29 November 2010 15:08, Tyson Scott <[email protected]> wrote: > > > > > >> I can see that you can reach the loopback from the physicals but did > you > > >> try sourced from the loopbacks. > > >> > > >> > > >> > > >> Regards, > > >> > > >> > > >> > > >> Tyson Scott - CCIE #13513 R&S, Security, and SP > > >> > > >> Managing Partner / Sr. Instructor - IPexpert, Inc. > > >> > > >> Mailto: [email protected] > > >> > > >> Telephone: +1.810.326.1444, ext. 208 > > >> > > >> Live Assistance, Please visit: www.ipexpert.com/chat > > >> > > >> eFax: +1.810.454.0130 > > >> > > >> > > >> > > >> IPexpert is a premier provider of Self-Study Workbooks, Video on > Demand, > > >> Audio Tools, Online Hardware Rental and Classroom Training for the > Cisco > > >> CCIE (R&S, Voice, Security & Service Provider) certification(s) with > > >> training locations throughout the United States, Europe, South Asia > and > > >> Australia. Be sure to visit our online communities at > > >> www.ipexpert.com/communities and our public website at > www.ipexpert.com > > >> > > >> > > >> > > >> *From:* [email protected] [mailto: > > >> [email protected]] *On Behalf Of *Amer Mustafa > > >> *Sent:* Sunday, November 28, 2010 7:36 PM > > >> *To:* [email protected] > > >> *Subject:* [OSL | CCIE_RS] WORKBOOK 1 - LAB 13 TAKS 1.2 > > >> > > >> > > >> > > >> *WORKBOOK 1 - LAB 13 TAKS 1.2 * > > >> > > >> > > >> > > >> *BGP PEERING BETWEEN R5 AND R6 ARE NOT COMING UP. * > > >> > > >> > > >> > > >> *R5 ===> * > > >> > > >> *R5(config)#do show ip bgp sum* > > >> > > >> *BGP router identifier 200.0.0.5, local AS number 64513* > > >> > > >> *BGP table version is 1, main routing table version 1* > > >> > > >> * * > > >> > > >> *Neighbor V AS MsgRcvd MsgSent TblVer InQ OutQ > > Up/Down > > >> State/PfxRcd* > > >> > > >> *150.100.100.2 4 64512 7 6 1 0 0 > > 00:04:25 > > >> 0* > > >> > > >> *150.100.100.6 4 64514 0 0 0 0 0 never > > >> Active*** > > >> > > >> * * > > >> > > >> *R6====>* > > >> > > >> *R6(config-router)#do show ip bgp sum* > > >> > > >> *BGP router identifier 200.0.0.6, local AS number 64514* > > >> > > >> *BGP table version is 1, main routing table version 1* > > >> > > >> * * > > >> > > >> *Neighbor V AS MsgRcvd MsgSent TblVer InQ OutQ > > Up/Down > > >> State/PfxRcd* > > >> > > >> *150.100.100.5 4 64513 0 0 0 0 0 never > > >> Active*** > > >> > > >> * * > > >> > > >> * * > > >> > > >> > > >> > > >> *R5====> * > > >> > > >> *R5(config)#do show run | sec router bgp* > > >> > > >> *router bgp 64513* > > >> > > >> * no synchronization* > > >> > > >> * bgp log-neighbor-changes* > > >> > > >> * bgp confederation identifier 109* > > >> > > >> * bgp confederation peers 64512 64514 * > > >> > > >> * neighbor 150.100.100.2 remote-as 64512* > > >> > > >> * neighbor 150.100.100.6 remote-as 64514* > > >> > > >> * no auto-summary* > > >> > > >> * * > > >> > > >> * * > > >> > > >> *R6====> * > > >> > > >> *R6(config-router)#do show run | sec router bgp * > > >> > > >> *router bgp 64514* > > >> > > >> * no synchronization* > > >> > > >> * bgp log-neighbor-changes* > > >> > > >> * bgp confederation identifier 109* > > >> > > >> * bgp confederation peers 64512 64513 * > > >> > > >> * neighbor 150.100.100.5 remote-as 64513* > > >> > > >> * no auto-summary* > > >> > > >> * * > > >> > > >> * * > > >> > > >> *R6(config-router)#do ping 150.100.100.5* > > >> > > >> * * > > >> > > >> *Type escape sequence to abort.* > > >> > > >> *Sending 5, 100-byte ICMP Echos to 150.100.100.5, timeout is 2 > seconds:* > > >> > > >> *!!!!!* > > >> > > >> * * > > >> > > >> * * > > >> > > >> *R5(config)#do ping 150.100.100.6* > > >> > > >> * * > > >> > > >> *Type escape sequence to abort.* > > >> > > >> *Sending 5, 100-byte ICMP Echos to 150.100.100.6, timeout is 2 > seconds:* > > >> > > >> *!!!!!* > > >> > > >> _______________________________________________ > > >> For more information regarding industry leading CCIE Lab training, > > please > > >> visit www.ipexpert.com > > >> > > >> > > > > > > > > > > -- > > Sent from my mobile device > > _______________________________________________ > > For more information regarding industry leading CCIE Lab training, please > > visit www.ipexpert.com > > > > > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: </archives/ccie_rs/attachments/20101202/da65f683/attachment.html> > > End of CCIE_RS Digest, Vol 59, Issue 4 > ************************************** >
_______________________________________________ For more information regarding industry leading CCIE Lab training, please visit www.ipexpert.com
