Hi guys
If you have the following setup
RIP----- (R5&R6)---- AREA 0----(R2)----AREA 27-----(R1)----- EIGRP
3.5 The task says area-27 should be configured as a stub. Type 7 LSA's
should be permitted.
A - easy enough, just area 27 nssa.
Later on when getting to the redistribution,:
3.9 - Redistribute as needed, on R1, R5, R6, confirm full-reachability to
from Area27 to the RIP domain.
The question I have is regarding generating of a default into area 27, while
not voilating
the DO's, and DONT's that say "do not create a static/default unless stated
otherwise"
Area 27 needs full reachability to reach the RIP domain, and since being a
NSSA area,
it does by default NOT get a Default route (0/0).
I configured on R2 : " area 27 nssa no-summary"
So without violating the DO's and DONT's, changed the area type to
Total-NSSA,
thereby creating a default route automatically. This is also not breaking
task 3.5, as
Type-7 LSA are still permitted, nor any other task.
But, the solution in the MOCK lab, used the following command or R2:
" area 27 nssa default-information-originate"
Mine was marked wrong, while it did not break any reachability while
meeting task requirements
I did not opt to use the default-information-originate as I assumed that
would count as creating a default
route manually, which is a beeeg NO-NO
Am I taken this wrong, I feel my solution is correct and technically more
correct than the lab solution?
Is using the command " area 27 nssa default-information-originate" not
count for manually creating
a default route, even when not explicitly told?
Please share you views on this
-- <ruhann> Blogs and organic groups at http://www.ccie.netReceived on Wed Apr 08 2009 - 18:14:07 ART
This archive was generated by hypermail 2.2.0 : Mon May 04 2009 - 07:39:11 ART