From: Ryaboy Vadim (VRyaboy@xxxxxxxxxx)
Date: Thu Jan 10 2002 - 21:03:46 GMT-3
I was using ospf network type point-to-multipoint if not specified
otherwise.
Yes, it creates /32. But, can anybody tell me what is wrong with /32?
It is still pingable, it is still in routing table.
Thanks.
Vadim.
-----Original Message-----
From: Joseph Ezerski [mailto:jezerski@broadcom.com]
Sent: Thursday, January 10, 2002 3:35 PM
To: ccielab@groupstudy.com
Subject: RE: List of Gotcha's
I would like to add to the specific configuration "gotchas" or more "rules
of thumb" that I used when I was practicing for the exam.
#1. Before doing a "no shut" on your frame relay interfaces for the first
time, make sure you DISABLE frame-relay inverse arp. Just to be safe, I do
it on the major and sub-interfaces as well.
#2. Nail down your DRs! When doing OSPF over the frame cloud, and an
election is needed, make sure you set your ip ospf priority to "0" on the
spokes and again, because I am paranoid, I set my hub (the one that should
be DR) to something higher than "1".
#3. Nail down your OSPF neighbors. I like to nail down my OSPF neighbors,
using non-broadcast as my network type. This is good and bad. It is good
because you absolutely nail down who your neighbors are and cannot get
screwed by some hidden CCIE trick that you are unaware of. It is bad
because you need to remember to set your ip ospf priority as per #2.
#4. Don't forget to set your opsf network type "point-to-point" on your
loopback interfaces, else you will get the /32 host routes.
#5. Here is a big one that people often forget. Absolutely NEVER forget
about split-horizon and how it works. If you do, it can mess up your whole
day. Trust me, I know ;)
These are just a few of the basics that I used when studying. Hope they
help.
-Joe
CCIE#8588
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com]On Behalf Of
EA Louie
Sent: Thursday, January 10, 2002 1:15 PM
To: ccielab@groupstudy.com
Subject: Re: List of Gotcha's
> An important part of the lab is to be prepared for the gotcha's that may
> determine a pass/fail. I would like to start with this gotcha and invite
> others to respond and add to the list. These would be gotcha's that would
not
> be explicitly detailed in a lab:
>
> Routing loop when redistributing between protocols - can use distribute
lists
> to prevent loop.
>
Being restricted from using one particular method to solve a problem (no ip
ospf network statements, no distribute-lists, minimum number of
configuration commands, etc) which means you need to know multiple ways to
solve the same problem.
Seemingly ambiguous directions that aren't necessarily clarified by the
proctor because you should be able to interpret what they're asking for if
you know the technology.
Following the direction *incompletely* and missing some part of the detail.
Testing your configuration by reloading the routers to see if your config
stands up after restart.
Overlooking erroneous route sources (just looking at the routing table) and
not catching that the source of the route is wrong.
(Somewhere in the vast stretches of my very small mind, I vaguely remember
doing this before - call it deja vu - a search of the archives is in order)
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 10:56:23 GMT-3