From: Kevin Baumgartner (kbaumgar@xxxxxxxxx)
Date: Sat Sep 23 2000 - 23:58:56 GMT-3
That maybe one of the reasons why the ISDN line can come up but that's not
the reason in this case. The redistribution from RIP into OSPF is the problem.
Kevin
At 10:44 PM 9/23/00 -0400, you wrote:
>int bri0
>no cdp enable
>
>
>-----Original Message-----
>From: nobody@groupstudy.com [mailto:nobody@groupstudy.com]On Behalf Of
>Feliz, Edgar
>Sent: Saturday, September 23, 2000 10:23 PM
>To: 'Ccielab
>Subject: ISDN RIP/OSPF DDR
>
>
>All,
>
>I have the following configuration. R3 runs OSPF, and has a connection to
>the rest of the network via F/R, which is in area 0. I have a serial
>connection to r4 as the every day line, and ISDN for backup using the
>"demand-circuit" command on r4. On r4 I am doing mutual redistribution
>between RIP, and OSPF. Initially like many on the list have commented my
>ISDN link kept coming up because of the redistribution, so I added the "no
>peer neighbor-route" to the BRI interfaces and now the ISDN line stays down,
>BUT I am getting the following message. Is this message common with this
>command added?
>
>*Mar 2 01:32:18: BRI0: cdp, 272 bytes, outgoing uninteresting (no list
>matched)
>*Mar 2 01:32:18: BRI0: sending broadcast to ip 10.43.1.1 -- failed, not
>connected
>
>How do I keep this from happening? is there a better way to keep the ISDN
>line down? I know I can add a access-list which has been mentioned on the
>list? What would be the preferred method?
>
><r3 OSPF area 3>------ISDN-------< area 3 r4
>OSPF/RIP>----------SERIAL-------<r6 RIP>
>l
>l-interface S/0
>l----F/R cloud area 0
>
>Thanks,
>
>Edgar Feliz
>
>Technical Consultant
>
>
>
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 08:25:01 GMT-3