RE: Should you be able to ping backbone routers on the LAB?

From: Mike Ollington (Mike.Ollington@uk.didata.com)
Date: Tue Jan 31 2006 - 05:27:10 GMT-3


If you have a BGP peer with the BB then send in an aggregate address (ensuring
you don't break other requirements).

-----Original Message-----
From: Mitchell, TJ [mailto:tmitchell@allianttech.com]
Sent: Mon 1/30/2006 7:02 PM
To: Mike Ollington; Scott Morris; CCIEin2006
Cc: ccie lab
Subject: RE: Should you be able to ping backbone routers on the LAB?

Scott --
You could do NAT or what about a summary loopback sent to the BB.
Technically your not redistributing your routes back to the BB.

Thanks

T.J. Mitchell

-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
Mike Ollington
Sent: Monday, January 30, 2006 6:53 AM
To: Scott Morris; CCIEin2006
Cc: ccie lab
Subject: RE: Should you be able to ping backbone routers on the LAB?

If you're not clear from the lab requirements (which I wasn't) - check
with the proctor. The proctor assigned to my lab was happy to
differentiate what should and should not be reachable/pingable.

Regards,
Mike

-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
Scott Morris
Sent: 29 January 2006 15:47
To: 'CCIEin2006'
Cc: 'ccie lab'
Subject: RE: Should you be able to ping backbone routers on the LAB?

In vague theory that would be right, but I'd just watch the wording on
the
lab. IMHO, if you get a route, it's likely on a loopback which means
either
.1 or .254 is the likely IP address reachable. But how far that BB
router
is supposed to see into YOUR network is a different story. If you are
not
told to send your routes to the BB, then obviously pinging would be
difficult without NAT involved!

Don't give yourself extra work though when it's not asked for! Do what
you'd told to do!

Scott

  _____

From: CCIEin2006 [mailto:ciscocciein2006@gmail.com]
Sent: Sunday, January 29, 2006 10:23 AM
To: swm@emanon.com
Cc: ccie lab
Subject: Re: Should you be able to ping backbone routers on the LAB?

So basically if I receive a RIP route such as 10.1.1.0 from a BB router
and
there is nothing on the lab saying you must be able to ping a host on
this
network, I should not even bother, correct?

On 1/28/06, Scott Morris <swm@emanon.com> wrote:

That's a pretty vague concept... Basically, you're supposed to do
whatever
the lab tells you to do!

Some may tell you to reach all the ethernets, others perhaps a loopback
only. I don't think there'd be any pat answer.

As for the TCL script, if it makes sense based on your lab requirements
to
do that, then the answer is sure. But IMHO there isn't any "standard"
answer to that question. Read your lab! It'll mention what is
reachable
and what isn't. Some routes you may send out, others you may not. Each
lab
may be different

Scott

-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
CCIEin2006
Sent: Saturday, January 28, 2006 8:05 PM
To: ccie lab
Subject: Should you be able to ping backbone routers on the LAB?

Hello once again list,

Can someone tell me if you're supposed be able to all the interfaces on
the
backbone routers?
If that is the case then how are you supposed to know all the IP
addresses
on the routers when you have no access to them?
For example, do you assume that any route received from the BB routers
you
should be able to ping the .1 address?

And finally, as a best practice should you include in your TCL script
the
aforementioned IP addresses?

Thanks again.



This archive was generated by hypermail 2.1.4 : Wed Feb 01 2006 - 07:45:50 GMT-3