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

From: Scott Morris (swm@emanon.com)
Date: Sun Jan 29 2006 - 01:29:17 GMT-3


This is a multi-part message in MIME format...

------------=_1138509020-1096-12
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit

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.

------------=_1138509020-1096-12
Content-Type: text/plain; name="message-footer.txt"
Content-Disposition: inline; filename="message-footer.txt"
Content-Transfer-Encoding: 8bit



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