From: Mike Chase (mchase@xxxxxxxxxxxx)
Date: Sun Sep 24 2000 - 00:04:48 GMT-3
This command basically helps stop ISDN from flapping due to the router with ISD
N
creating this automatic static host route (in the background) to the far end
router's IP which is withdrawn when the line goes down thus causing a topology
change, which of course forces the line back up (isdn flapping, walla !)
peer neighbor-route
To reenable the creation of peer neighbor routes on an interface once this
default behavior has been disabled, use the peer neighbor-route interface
configuration command. To disable the default behavior of creating a neighbor
route for the peer on a point-to-point interface, use the no
form of this command.
peer neighbor-route
no peer neighbor-route
Syntax Description
This command has no keywords and arguments.
Default
Creation of a route to the peer address on any point-to-point interface when th
e
PPP IPCP negotiation is completed.
Command Mode
Interface configuration
Usage Guidelines
This command first appeared in Cisco IOS Release 11.2.
Use the no form of this command only if the default behavior creates problems i
n
your network environment.
If if you enter this command on a dialer interface or a async-group interface,
it affects all member interfaces.
Example
The following examples reenables the default behavior on an interface.
peer neighbor-route
Mike L. Chase
Sr. Network Architect
ISG: Information Services Group
Broadcom Corporation World Headquarters, BLDG A-1050
16215 Alton Parkway, Irvine, California 92618-3616
OFFICE:949-585-6057|CELL:949-283-4254|FAX:949-585-6227
"Courage is not the absence of fear, but rather the judgment
that something else is more important than fear."
-- Ambrose Redmoon
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com]On Behalf Of
Kevin Baumgartner
Sent: Saturday, September 23, 2000 7:48 PM
To: Feliz, Edgar
Cc: ccielab@groupstudy.com
Subject: Re: ISDN RIP/OSPF DDR
I have never used the "no peer neighbor-route" command. Not even sure what
it does. What I have found that works very well is to not redistribute the ISDN
IP route into OSPF. This will prevent the ISDN line from coming up.
Please don't ask me how this works! It's in the archives.
Something like (network 192.168.1.0 is the ISDN network)
router ospf 1
red rip route-map deny-ISDN-network
route-map deny-ISDN-network deny 10
match address 1
route-map 20 deny-ISDN-network deny 20
match address 2
access-list 1 permit 192.168.1.0 0.0.0.255
access-list 2 permit any
At 10:22 PM 9/23/00 -0400, you wrote:
>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