From: Brian Dennis (bdennis@internetworkexpert.com)
Date: Wed May 04 2005 - 00:27:12 GMT-3
What good is it for someone to say to configure it on both sides
and not explain the reasoning behind the statement? As a CCIE you need
to understand the reasoning and not just blindly apply commands. Also
the problem you mentioned below doesn't make must sense without posting
more information (show commands, debugs, etc).
As far as the CCIE lab goes, if it works with using the neighbor
command only on one side, they will not take off points just because
some document on CCO said it was "good practice" to configure it on both
sides. Do what you need to make things work in the lab. Do not try to
apply any sort of best practices configuration. As stated by Cisco,
"the Routing and Switching exam tests your ability to apply
configuration knowledge and skill to new situations. It is not a design
test, nor is it always a test of "best practices" for use in the field".
Brian Dennis, CCIE #2210 (R&S/ISP-Dial/Security)
bdennis@internetworkexpert.com
Internetwork Expert, Inc.
http://www.InternetworkExpert.com
Toll Free: 877-224-8987
Direct: 775-745-6404 (Outside the US and Canada)
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
gladston@br.ibm.com
Sent: Tuesday, May 03, 2005 1:32 PM
To: ccielab@groupstudy.com
Subject: Neighbor Statement on Both Sides
Hi,
This Cisco Doc says it is good practice configuring neighbor statement
on both sides.
I though it was I good idea to configure it on just on side on the real
lab, just to be sure they will not take out points because configuring
it on just one side is enough.
What are your thoughts?
In fact I am reserching this topic because a scenario that worked fine
until now is not going up today. It seems there is some problem on R2
(the hub with neighbor commands)
==========
quoted
Though configuring the neighbor statement on one end is sufficient to
form adjacency, it is a good practice to have it configured on both the
ends as shown.
http://www.cisco.com/warp/public/104/18.html
==========
This archive was generated by hypermail 2.1.4 : Fri Jun 03 2005 - 10:11:56 GMT-3