From: john matijevic (matijevi@bellsouth.net)
Date: Wed Sep 08 2004 - 12:59:45 GMT-3
Hello James,
Yes this is an error in the book, please visit my forum, as there are
many errors already pointed out there, already. Backup interface is the
solution I used as well.
Sincerely,
John Matijevic, CCIE #13254, MCSE, CNE, CCEA
CEO
IgorTek Inc.
151 Crandon Blvd. #402
Key Biscayne, FL 33149
Hablo Espanol
305-321-6232
http://home.bellsouth.net/p/PWP-CCIE
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
James
Sent: Wednesday, September 08, 2004 3:23 AM
To: ccielab@groupstudy.com
Subject: Lab6 Cisco r&s Prac Labs ISDN wording
In Lab 6 on practice labs , under ISDN, we see the following:
"Make sure that yourrouting proto is passed accross the isdn link only
when
the connectivity is established"
In order to accomplish the above, we simply make sure 'dialer-list 1
proto
clns permit', and ensure that "clns_is" is not included -- thereby
making
ISIS establish adjacency only when ISDN circuit is already up and
running.
So far so good. (well also ensuring dialer map clns yadda yadda..)
"The ISDN link should only pass a routing protocol if R5-fa0/0 is down."
Now.. it says ISDN should pass routing protocol when fa0/0 on R5 is
down.
That is good and all when FA0/0 sudden goes down while ISDN is already
dialed
and running. But what happens when ISDN is NOT dialed and turned off
(due to
idle traffic)?? The previous requirement says that isdn must only
establish
ISIS protocol when the circuit is already dialed and running.
So the thought process here in my head is to use 'backup interface' on
fa0/0
or another mechanism that will trigger ISDN to dial itself during fa0/0
outage.
This will ensure ISIS will establish adjacency then, after fa0/0 outage,
since backup interface brought up the ISDN circuit physically.
But the solution in the book made no configuration changes for this
requirement.
Well, not making any config changes for this requirement works well when
the
isdn is already dialed and up and running, but guarantees nothing when
proctor
reboots your routers and isdn is shut down at boot time :(
Any ideas, clues?
Thanks,
-J
-- James Jun TowardEX Technologies, Inc. Technical Lead Network Design, Consulting, IT Outsourcing james@towardex.com Boston-based Colocation & Bandwidth Services cell: 1(978)-394-2867 web: http://www.towardex.com , noc: www.twdx.net
This archive was generated by hypermail 2.1.4 : Fri Oct 01 2004 - 15:00:39 GMT-3