From: fwells12 (fwells12@xxxxxxxxxxx)
Date: Tue Jan 23 2001 - 05:33:08 GMT-3
As you are creating your network, note all the ip addresses you put on the
interfaces and enter the data into a text file like so:
alias exec r1s0 ping x.x.x.x
alias exec r3t1 ping x.x.x.x
alias exec r5e0 ping x.x.x.x
Once you have addresses all of your interfaces you can then easily test
pinging all over the place by simply typing r1s0 or r5e0 for example. I use
the R to represent router and the letters to represent the interface type.
r3t1 means router 3 token-ring 1 etc.
Paste the complete text file into each router and viola!
----- Original Message -----
From: Chuck Larrieu <chuck@cl.cncdsl.com>
To: CCIE_Lab Groupstudy List <ccielab@groupstudy.com>
Sent: Monday, January 22, 2001 10:10 PM
Subject: Validation Testing
> As most of you know, one condition for success that all of the practice
labs
> state is the ability to reach all parts of the network from all other
parts.
> I.e. ping from any interface to any interface
>
> In terms of a general practice, I use two techniques.
>
> 1) are all the routes in my tables that I expect to be in my tables. This
is
> actually done incrementally as part of my configuration routine
>
> 2) I check my map for what look like the two points furthest apart and
test
> from there. If that is good, I make the ASSumption that things are as they
> should be.
>
> Not that I want to be saying this someplace where Lab proctors might see
and
> make notes about me, but I find that testing from everywhere to everywhere
> might cost more time than I can afford.
>
> Any thoughts? Techniques? Shortcuts? ( recognizing that what you say may
be
> used against you :-> )
>
>
> Chuck
> http://www.1112.net/lastpage.html
>
>
>
>
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 10:27:40 GMT-3