From: Hogo, Trust (trust.hogo@sarcom.com)
Date: Thu Feb 26 2004 - 01:55:59 GMT-3
You need to change you distance on R3 but be careful to change distance only
for routes learned for ISIS. You need a distance command with an access-list.
Also stick within the guide lines, this is not a best practice exam and your
main interest is the summary route 51.0.0.0 255.248.0.0.
Good Luck
Trust Hogo
________________________________
From: nobody@groupstudy.com on behalf of Ahmed Mustafa
Sent: Wed 2/25/2004 7:52 PM
To: ccielab@groupstudy.com
Subject: Lab 2 Verification tasks 5.30 - 5.34
Hello Brian and Group,
Couple of things I noticed while finishing my Lab2.
1) I also configured the summary address 51.0.0.0 255.248.0.0 on R4 even not
mentioned in Solution guide. The reason if the connection between r2 and r1
fails then r1 will inject routes either from r4 or r3. R4 has also becom
ASBR
because of redistribution, and will take care of the summary route.
2) In order to have full reachbility I redistributed Ethernet 0/0
(132.1.5.0/24) of R5, and 132.1.6.0 on R6 in ISIS domain. The Soultion Guide
only mentioned of redistributing Ethernet 0/1 (192.10.1.0/24). The only
thing
comes in my mind is can we do thing like that on our own in a real lab or
better talk to Proctor.
3) In solution guide, why it wouldn't alter the distance of native ISIS
routes on R3. The routes such as 54.1.2.0, 54.1.4.0, 132.1.26.0 on r3 are
learned through r2 via ospf, instead via HDLC over ISIS. Is not it
recommended that the native routes must always learn through the routing
protocol assigned to it.
Please advise !
Regards,
Ahmed
This archive was generated by hypermail 2.1.4 : Fri Mar 05 2004 - 07:13:57 GMT-3