From: Chuck Larrieu (chuck@xxxxxxxxxxxxx)
Date: Mon Jan 22 2001 - 22:23:47 GMT-3
Spent much of today on ccbootcamp rack two struggling with lab 1.
Couple of thoughts:
I was wondering about the number of questions recently about clock rate and
frame relay switching. To reiterate, the clock rate command goes on the
interface where the DCE end of the cable is connected. This does not have to
be the interface of the frame switch itself.
Debug is your friend. I had layer two problems despite my awareness of the
DCE / clockrate issue/ Question - when debug frame lmi and debug frame
packet yield no output, what next? Hint - the output of the show interface
command can provide key information.
In my case, a couple of the problems were fat finger things. One other was a
missing keepalive on a serial interface - something I have not run into
before.
I don't know about anyone else, but I have a severe problem with literal
mindedness. I'm not sure that flexible thinking can be taught or learned
quickly. I am told that one key to success is to read the lab scenario
carefully, read it again, and only then do your diagram and configurations.
Note to myself. It is impossible to get layer three to work over frame relay
without one of the following: frame-relay map ip, frame-relay
interface-dlci, neighbor statements, or ip ospf network commands. Or some
combination. It doesn't hurt to keep in mind the ramifications of DR
elections in a hub and spoke setup. Route maps are great once there is some
layer two. Do not ever accept the premise that you can gain connectivity
without layer to up and solid.
Chuck
http://www.1112.net/lastpage.html
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 10:27:39 GMT-3