From: Richard Dumoulin (Richard.Dumoulin@vanco.fr)
Date: Wed Sep 08 2004 - 16:01:14 GMT-3
The requirement is "...when R5 fast0/0 goes down...".
R3 is connected to the same Ethernet segment as R5 so R3 won't be able to
know if R5 Fast is down because it can learn R5's routes via another frame
relay interface.
I still don't like watching a connected interface but I don't see any reason
to not use it ! Is there any one ? If not then we only need the equivalent
commands of backup delay to fulfill the same requirements as the backup
command and even more !!!
--Richard
-----Message d'origine-----
De : Kenneth Wygand [mailto:KWygand@customonline.com]
Envoyi : Wednesday, September 08, 2004 8:54 PM
@ : Richard Dumoulin; James
Cc : john matijevic; ccielab@groupstudy.com
Objet : RE: RE : RE : Lab6 Cisco r&s Prac Labs ISDN wording
Since I don't have the lab in front of me (but I did buy the book and
studied from it and liked it), does it say which side has to do the dialing?
Otherwise, you could have the other side watch the network so you don't have
to watch a directly-connected network.
Kenneth E. Wygand
Systems Engineer, Project Services
CCIE #13720, CISSP #37102, CCNP/DP, ACSP,
Cisco IPT Design Specialist, MCP, CNA, Network+, A+
Custom Computer Specialists, Inc.
"Failure only occurs at the point in which one stops trying."
-Anonymous
Custom Computer Specialists, Inc.
"Celebrating 25 Years of Excellence"
-----Original Message-----
From: Richard Dumoulin [mailto:Richard.Dumoulin@vanco.fr]
Sent: Wednesday, September 08, 2004 2:51 PM
To: Kenneth Wygand; James
Cc: john matijevic; ccielab@groupstudy.com
Subject: RE : RE : Lab6 Cisco r&s Prac Labs ISDN wording
Kenneth, you passed before the book was edited I think :)
"CCIE Routing and Switching Practice Labs".
James,
it does not say "must" but "should only pass a routing protocol if fast0/0
is down".
But yes, I think you are right and dialer watch should do the job. Although
I find it weird to watch a directly connected interface. Is this good
practice ?
--Richard
-----Message d'origine-----
De : Kenneth Wygand [mailto:KWygand@customonline.com
<mailto:KWygand@customonline.com> ]
Envoyi : Wednesday, September 08, 2004 8:44 PM
@ : James; Richard Dumoulin
Cc : john matijevic; ccielab@groupstudy.com
Objet : RE: RE : Lab6 Cisco r&s Prac Labs ISDN wording
James,
Which practice lab workbook is this from? I've purchased almost all of
them so I should be able to reference the diagram to answer your
question.
Thanks! :)
Kenneth E. Wygand
Systems Engineer, Project Services
CCIE #13720, CISSP #37102, CCNP/DP, ACSP,
Cisco IPT Design Specialist, MCP, CNA, Network+, A+
Custom Computer Specialists, Inc.
"Failure only occurs at the point in which one stops trying."
-Anonymous
Custom Computer Specialists, Inc.
"Celebrating 25 Years of Excellence"
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com
<mailto:nobody@groupstudy.com> ] On Behalf Of
James
Sent: Wednesday, September 08, 2004 2:38 PM
To: Richard Dumoulin
Cc: john matijevic; ccielab@groupstudy.com
Subject: Re: RE : Lab6 Cisco r&s Prac Labs ISDN wording
On Wed, Sep 08, 2004 at 07:32:17PM +0100, Richard Dumoulin wrote:
> Hi John, the problem with using the backup command is you are breaking
the
> requirement "...R3 and R5 should be able to ping each other..."
>
> After reading his explanation I have come to the conclusion that it is
not
> really a backup solution the author is asking for, nor is there a
> requirement for it. We can see in the breakdown solution that ISIS
only goes
> through the isdn line once he pings through the bri interfaces so he
is
> effectively fulfilling all his requirements.
But ISIS must activate when fa0/0 goes down? :P
I am pretty new in the ISDN field as my experience never used it in the
past. So I ask -- would using dialer-watch also prevent pinging accross
the
ISDN circuit when fa0/0 is up and running, like backup command does?
Thanks for all the good replies!
-J
>
> --Richard
>
> -----Message d'origine-----
> De : john matijevic [mailto:matijevi@bellsouth.net
<mailto:matijevi@bellsouth.net> ]
> Envoyi : Wednesday, September 08, 2004 6:00 PM
> @ : 'James'; ccielab@groupstudy.com
> Objet : RE: Lab6 Cisco r&s Prac Labs ISDN wording
>
> 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
<http://home.bellsouth.net/p/PWP-CCIE>
>
>
> -----Original Message-----
> From: nobody@groupstudy.com [mailto: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
<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