From: Joseph Brunner (joe@affirmedsystems.com)
Date: Sat Sep 22 2007 - 22:39:31 ART
You do not need to test reachability to the BB routes to get the points in
the real lab!!!
You do need to make sure all routes appear in your topology as stated by the
test booklet.
Believe me, doing it the way they want it is hard enough a challenge. I have
seen the config of Brian&Brian's BB's and I have made some interesting
config's for the BB's in my rack.
We often inject routes into bgp via loopbacks, and other methods such as
redistributing static, with those statics to null, etc..
I would say when in doubt ask the proctor. But you're more likely to get out
of a ticket doing 110 Mph on I-95 at 2am in Rural Georgia with NY license
plates and rap music playing than to get meaningful help in the lab from the
proctors to help you get points.
Just remember what I said, and that I honestly got 100% of the BGP points
last attempt and the IGP points from other BB tasks.
-Joe
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of Toh
Soon, Lim
Sent: Saturday, September 22, 2007 9:29 PM
To: Antonio Soares
Cc: Bit Gossip; ccielab@groupstudy.com
Subject: Re: how to identify host ip from routes comming from Backbone
Hi Antonio,
I share the same concern. Are we supposed to test reachability to the routes
injected by BB routers? If we redistribute our routes into the IGP the BB
routers are running, theorectically we know the BBs will have full
reachability to our pod. However since we are not allowed to view the BBs'
config, we are not sure if they have any filtering, etc. configured.
Secondly, how are we supposed to know the IP address of the routes injected
by BBs in order to set up our TCL script to ping those IP addresses? Only
thing I can think of is to ping the directed broadcast address of the
routes, e.g. if we receive 100.10.2.0/24 from BB, we can ping to
100.10.2.255.
Appreciate further comments from the Group.
Thank you.
B.Rgds,
Lim TS
On 9/6/07, Antonio Soares <amsoares@netcabo.pt> wrote:
>
> That will be true if the backbone routers have not been configured to
> avoid
> it. For example, try to add this config to you BB router:
>
> ++++++++++++++++++++++++
> !
> interface Ethernet0
> ip address xxx.xxx.xxx.xxx 255.255.255.0
> ip access-group 101 in
> no ip unreachables
> no ip proxy-arp
> no cdp enable
> !
> access-list 101 deny icmp any 0.0.0.255 255.255.255.0
> access-list 101 deny icmp any 0.0.0.0 255.255.255.0
>
> access-list 101 deny icmp any 0.0.255.255 255.255.0.0
> access-list 101 deny icmp any 0.0.0.0 255.255.0.0
>
> access-list 101 deny icmp any 0.255.255.255 255.0.0.0
> access-list 101 deny icmp any 0.0.0.0 255.0.0.0
>
> access-list 101 permit ip any any
> !
> ++++++++++++++++++++++++
>
> I had this question in the past and the only solution i know is via tcl
> scripts. Of course, it will be feasible for /24 or less networks.
>
>
>
> Regards,
>
> Antonio Soares
> CCIE #18473, CCNP, CCIP
>
> -----Original Message-----
> From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
> Bit
> Gossip
> Sent: quarta-feira, 5 de Setembro de 2007 13:03
> To: ccielab@groupstudy.com
> Subject: Re: how to identify host ip from routes comming from Backbone
>
> Usually I ping the network address, usually the router with an interface
> configured for this network replies.
> Bit.
>
> R6#show ip bgp
> BGP table version is 11, local router ID is 54.1.2.6 Status codes: s
> suppressed, d damped, h history, * valid, > best, i - internal,
> r RIB-failure, S Stale
> Origin codes: i - IGP, e - EGP, ? - incomplete
>
> Network Next Hop Metric LocPrf Weight Path
> *> 28.119.16.0/24 54.1.2.254 0 54 i
> *> 28.119.17.0/24 54.1.2.254 0 54 i
> *> 112.0.0.0 54.1.2.254 0 0 54 50 60 i
> *> 113.0.0.0 54.1.2.254 0 0 54 50 60 i
> *> 114.0.0.0 54.1.2.254 0 0 54 i
> *> 115.0.0.0 54.1.2.254 0 0 54 i
> *> 116.0.0.0 54.1.2.254 0 0 54 i
> *> 117.0.0.0 54.1.2.254 0 0 54 i
> *> 118.0.0.0 54.1.2.254 0 0 54 i
> *> 119.0.0.0 54.1.2.254 0 0 54 i
> R6#debug ip icmp
> ICMP packet debugging is on
> R6#ping 28.119.16.0
>
> Type escape sequence to abort.
> Sending 5, 100-byte ICMP Echos to 28.119.16.0, timeout is 2 seconds:
> !!!!!
> Success rate is 100 percent (5/5), round-trip min/avg/max = 76/76/77 ms
> R6#
> *Mar 2 06:58:14.923: ICMP: echo reply rcvd, src 172.16.4.3, dst 54.1.2.6
> *Mar 2 06:58:15.003: ICMP: echo reply rcvd, src 172.16.4.3, dst 54.1.2.6
>
> R6#ping 112.0.0.0
>
> Type escape sequence to abort.
> Sending 5, 100-byte ICMP Echos to 112.0.0.0, timeout is 2 seconds:
> !!!!!
> Success rate is 100 percent (5/5), round-trip min/avg/max = 16/16/16 ms
> R6#
> *Mar 2 07:00:50.293: ICMP: echo reply rcvd, src 54.1.2.254, dst 54.1.2.6
>
> ----- Original Message -----
> From: "NITIN NITIN" <ccie_study_123@yahoo.com>
> To: <ccielab@groupstudy.com>
> Sent: Friday, August 31, 2007 8:01 PM
> Subject: how to identify host ip from routes comming from Backbone
>
>
> > Hi Experts ,
> >
> > please suggest -----
> >
> > IF in lab I have routes comming from BB routers --- Now to check
> > connectivity to those ips
> > like 1.1.1.0/24
> >
> > Which host ip to ping ???? how to identify that ???
> >
> >
> >
> >
> > ---------------------------------
> > Moody friends. Drama queens. Your life? Nope! - their life, your story.
> > Play Sims Stories at Yahoo! Games.
> >
> > ---------------------------------
> > Yahoo! oneSearch: Finally, mobile search that gives answers, not web
> > links.
> >
> > _______________________________________________________________________
> > Subscription information may be found at:
> > http://www.groupstudy.com/list/CCIELab.html
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
This archive was generated by hypermail 2.1.4 : Sat Oct 06 2007 - 12:01:15 ART