RE: OSPF demand-circuit does not work [7:74954]
It will say multicast. Martijn -Oorspronkelijk bericht- Van: Devrim Yener KUCUK [mailto:[EMAIL PROTECTED] Verzonden: maandag 8 september 2003 16:38 Aan: [EMAIL PROTECTED] Onderwerp: Re: OSPF demand-circuit does not work [7:74954] what do you see when you do "sh dialer" on the calling router, as a dial reason? or debug dialer, debug isdn q931 will be telling you regards De - Original Message - From: "Lesly Verdier" To: Sent: Monday, September 08, 2003 2:25 PM Subject: OSPF demand-circuit does not work [7:74954] > Hello All, > > I've configured "ip ospf demand-circuit" on an ISDN connection and this > statement is supposed to supress the calls initiated by the Hello Packets. > Still my router keeps on dialing. > > Does anybody know what the reason might be? > > Thanks, > > Lesly Verdier > **Please support GroupStudy by purchasing from the GroupStudy Store: > http://shop.groupstudy.com > FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html **Please support GroupStudy by purchasing from the GroupStudy Store: http://shop.groupstudy.com FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Message Posted at: http://www.groupstudy.com/form/read.php?f=7&i=75250&t=74954 -- **Please support GroupStudy by purchasing from the GroupStudy Store: http://shop.groupstudy.com FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Re: OSPF demand-circuit does not work [7:74954]
Devrim Yener KUCUK wrote: > what do you see when you do "sh dialer" on the calling router, as a dial > reason? > or debug dialer, debug isdn q931 will be telling you And "sh ip ospf stat" will show you activity of OSPF - remember that every change in OSPF topology can trigger dialer. -- EC Message Posted at: http://www.groupstudy.com/form/read.php?f=7&i=75038&t=74954 -- **Please support GroupStudy by purchasing from the GroupStudy Store: http://shop.groupstudy.com FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Re: OSPF demand-circuit does not work [7:74954]
what do you see when you do "sh dialer" on the calling router, as a dial reason? or debug dialer, debug isdn q931 will be telling you regards De - Original Message - From: "Lesly Verdier" To: Sent: Monday, September 08, 2003 2:25 PM Subject: OSPF demand-circuit does not work [7:74954] > Hello All, > > I've configured "ip ospf demand-circuit" on an ISDN connection and this > statement is supposed to supress the calls initiated by the Hello Packets. > Still my router keeps on dialing. > > Does anybody know what the reason might be? > > Thanks, > > Lesly Verdier > **Please support GroupStudy by purchasing from the GroupStudy Store: > http://shop.groupstudy.com > FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Message Posted at: http://www.groupstudy.com/form/read.php?f=7&i=74967&t=74954 -- **Please support GroupStudy by purchasing from the GroupStudy Store: http://shop.groupstudy.com FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
OSPF demand-circuit does not work [7:74954]
Hello All, I've configured "ip ospf demand-circuit" on an ISDN connection and this statement is supposed to supress the calls initiated by the Hello Packets. Still my router keeps on dialing. Does anybody know what the reason might be? Thanks, Lesly Verdier Message Posted at: http://www.groupstudy.com/form/read.php?f=7&i=74954&t=74954 -- **Please support GroupStudy by purchasing from the GroupStudy Store: http://shop.groupstudy.com FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Re: OSPF Demand Circuit - interesting and frustrating [7:65509]
an interesting evening, all things considered. where's that woman from Australia been lately? Jen - your insight and experience would be most welcome here :-> Got an OSPF demand circuit to work as advertised: R2#o data OSPF Router with ID (10.7.7.7) (Process ID 2) Router Link States (Area 1) Link ID ADV Router Age Seq# Checksum Link count 10.7.7.710.7.7.727 0x8022 0xEEC3 5 10.9.9.910.9.9.97 (DNA) 0x80BE 0x940D 2 10.111.111.110.111.111.1103 0x8039 0xE4F3 5 Net Link States (Area 1) Link ID ADV Router Age Seq# Checksum 10.1.2.110.111.111.1103 0x800B 0x2C03 Summary Net Link States (Area 1) Link ID ADV Router Age Seq# Checksum 10.4.1.110.9.9.9318 (DNA) 0x8003 0x14E6 10.4.2.110.9.9.9318 (DNA) 0x8003 0x9F0 10.8.8.010.9.9.9318 (DNA) 0x8003 0x3CBE 10.9.9.010.9.9.9318 (DNA) 0x8003 0x25D3 10.34.34.0 10.9.9.918780x8030 0xE3AC 10.44.1.0 10.9.9.9860 0x8002 0x3E96 172.16.1.1 10.9.9.966(DNA) 0x8002 0x430A R2# HOWEVER: it only worked for a little while. Note the time stamps. R2#sh di 01:26:47: %ISDN-6-DISCONNECT: Interface BRI0:1 disconnected from 2221 R3, call lasted 120 secondsaler 01:26:47: %LINK-3-UPDOWN: Interface BRI0:1, changed state to down 01:26:48: %LINEPROTO-5-UPDOWN: Line protocol on Interface BRI0:1, changed state to down 01:26:48: %LINEPROTO-5-UPDOWN: Line protocol on Interface Virtual-Access1, changed state to down Link goes down at 1:26 and change. BRI0 - dialer type = ISDN Dial String Successes FailuresLast DNIS Last status 222138 100:02:04 successful 0 incoming call(s) have been screened. 0 incoming call(s) rejected for callback. BRI0:1 - dialer type = ISDN Idle timer (120 secs), Fast idle timer (20 secs) Wait for carrier (30 secs), Re-enable (15 secs) Dialer state is idle BRI0:2 - dialer type = ISDN Idle timer (120 secs), Fast idle timer (20 secs) Wait for carrier (30 secs), Re-enable (15 secs) Dialer state is idle R2# 01:48:19: %OSPF-5-ADJCHG: Process 2, Nbr 10.9.9.9 on BRI0 from FULL to DOWN, Neighbor Down: Dead timer expired R2# NOTE - the time stamp indicates the adjacency dies at 1:48 and change - roughly 22 minutes later. This is the best result I've had so far, but still a bit short of expectation. IMHO the demand situation SHOULD last FOREVER!! Note that the OSPF database still shows the DNA's for the routes in question. R2#o data OSPF Router with ID (10.7.7.7) (Process ID 2) Router Link States (Area 1) Link ID ADV Router Age Seq# Checksum Link count 10.7.7.710.7.7.7713 0x8025 0xE3F3 10.9.9.910.9.9.97 (DNA) 0x80BE 0x940D 2 10.111.111.110.111.111.1763 0x803B 0xE0F5 5 Net Link States (Area 1) Link ID ADV Router Age Seq# Checksum 10.1.2.110.111.111.1763 0x800D 0x2805 Summary Net Link States (Area 1) Link ID ADV Router Age Seq# Checksum 10.4.1.110.9.9.9318 (DNA) 0x8003 0x14E6 10.4.2.110.9.9.9318 (DNA) 0x8003 0x9F0 10.8.8.010.9.9.9318 (DNA) 0x8003 0x3CBE 10.9.9.010.9.9.9318 (DNA) 0x8003 0x25D3 172.16.1.1 10.9.9.966(DNA) 0x8002 0x430A R2# Anyone with real world experience got any thoughts? Recall that this is done with IOS 12.1.5T10 and an ISDN simulator, which has proven interesting, to say the least. TAC docs indicate that lots of things ISDN related have been "fixed" in 12.2 releases. Good night, all. Chuck -- TANSTAAFL "there ain't no such thing as a free lunch" Message Posted at: http://www.groupstudy.com/form/read.php?f=7&i=65509&t=65509 -- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
RE: ISDN - OSPF DEMAND CIRCUIT [7:61310]
Its got something to do with the cost. try setting the ip opsf cost on the bri to . I had simular issues and I read this somewhere. Message Posted at: http://www.groupstudy.com/form/read.php?f=7&i=61528&t=61310 -- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
ISDN - OSPF DEMAND CIRCUIT [7:61310]
When using IP OSPF DEMAND-CIRCUIT are there any restrictions with using PPP MULTLINK as well ? Noticed that when PPP MULTILINK is configured on either the BRI or the DIALER interface, when the Serial interface is shutdown between the two routers and then brought back up, the ISDN continues to dial the second router. Checking the Dialer interface using "sh ip ospf int" it shows that Hellos are suppressed. When PPP MULTILINK is NOT configured, performing the same steps, i.e. shutdown Serial, bring it back up, the ISDN will disconnect and stay disconnected. Which makes me believe it is configured corrcetly. Any thoughts appreciated. Thank you. Message Posted at: http://www.groupstudy.com/form/read.php?f=7&i=61310&t=61310 -- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
Re: OSPF DEMAND-CIRCUIT, not stopping the link UPDOWN [7:60719]
Ya, redistribution of RIP into ospf but bri is on passive int. neil ""Scott"" wrote in message [EMAIL PROTECTED]">news:[EMAIL PROTECTED]... > Are you doing any type of redistribution on these routers? > > ""neil K."" wrote in message > [EMAIL PROTECTED]">news:[EMAIL PROTECTED]... > > I have configured the peer neighbor, also checked the ospf cost which is > > more than the Ethernet and also point to point configured on BRi. > > > > I checked the ospf database but it was not showing the DNA bit was set. > > Any suggestions. > > > > Thanks, > > > > neil > > > > ""Eisert, James A (Jad) %"" wrote in message > > [EMAIL PROTECTED]">news:[EMAIL PROTECTED]... > > > Have you done a "debug interesting packets" to see exactly what is > causing > > > your dialer to dial? > > > > > > James A Eisert (Jad) > > > HP Managed Services at Agere Systems > > > Agere Operations Center > > > 610-712-5700 > > > [EMAIL PROTECTED] > > > > > > -Original Message- > > > From: neil K. [mailto:[EMAIL PROTECTED]] > > > Sent: Thursday, January 09, 2003 12:25 PM > > > To: [EMAIL PROTECTED] > > > Subject: OSPF DEMAND-CIRCUIT, not stopping the link UPDOWN [7:60719] > > > > > > Guys, > > > > > > The ISDN back between two of my routers keeps on dialling. I am running > > ospf > > > over the ISDN which is a backup for frame relay link. I have configured > > the > > > ISDN bri with ip ospf demand-circuit and still it keeps dialling.I have > > even > > > used no peer-neighbor command on the interface. > > > Please help. > > > > > > Thanks in Advance. > > > > > > neil k. Message Posted at: http://www.groupstudy.com/form/read.php?f=7&i=60860&t=60719 -- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
Re: OSPF DEMAND-CIRCUIT, not stopping the link UPDOWN [7:60719]
Are you doing any type of redistribution on these routers? ""neil K."" wrote in message [EMAIL PROTECTED]">news:[EMAIL PROTECTED]... > I have configured the peer neighbor, also checked the ospf cost which is > more than the Ethernet and also point to point configured on BRi. > > I checked the ospf database but it was not showing the DNA bit was set. > Any suggestions. > > Thanks, > > neil > > ""Eisert, James A (Jad) %"" wrote in message > [EMAIL PROTECTED]">news:[EMAIL PROTECTED]... > > Have you done a "debug interesting packets" to see exactly what is causing > > your dialer to dial? > > > > James A Eisert (Jad) > > HP Managed Services at Agere Systems > > Agere Operations Center > > 610-712-5700 > > [EMAIL PROTECTED] > > > > -Original Message- > > From: neil K. [mailto:[EMAIL PROTECTED]] > > Sent: Thursday, January 09, 2003 12:25 PM > > To: [EMAIL PROTECTED] > > Subject: OSPF DEMAND-CIRCUIT, not stopping the link UPDOWN [7:60719] > > > > Guys, > > > > The ISDN back between two of my routers keeps on dialling. I am running > ospf > > over the ISDN which is a backup for frame relay link. I have configured > the > > ISDN bri with ip ospf demand-circuit and still it keeps dialling.I have > even > > used no peer-neighbor command on the interface. > > Please help. > > > > Thanks in Advance. > > > > neil k. Message Posted at: http://www.groupstudy.com/form/read.php?f=7&i=60849&t=60719 -- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
Re: OSPF DEMAND-CIRCUIT, not stopping the link UPDOWN [7:60719]
I have configured the peer neighbor, also checked the ospf cost which is more than the Ethernet and also point to point configured on BRi. I checked the ospf database but it was not showing the DNA bit was set. Any suggestions. Thanks, neil ""Eisert, James A (Jad) %"" wrote in message [EMAIL PROTECTED]">news:[EMAIL PROTECTED]... > Have you done a "debug interesting packets" to see exactly what is causing > your dialer to dial? > > James A Eisert (Jad) > HP Managed Services at Agere Systems > Agere Operations Center > 610-712-5700 > [EMAIL PROTECTED] > > -Original Message- > From: neil K. [mailto:[EMAIL PROTECTED]] > Sent: Thursday, January 09, 2003 12:25 PM > To: [EMAIL PROTECTED] > Subject: OSPF DEMAND-CIRCUIT, not stopping the link UPDOWN [7:60719] > > Guys, > > The ISDN back between two of my routers keeps on dialling. I am running ospf > over the ISDN which is a backup for frame relay link. I have configured the > ISDN bri with ip ospf demand-circuit and still it keeps dialling.I have even > used no peer-neighbor command on the interface. > Please help. > > Thanks in Advance. > > neil k. Message Posted at: http://www.groupstudy.com/form/read.php?f=7&i=60847&t=60719 -- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
RE: OSPF DEMAND-CIRCUIT, not stopping the link UPDOWN [7:60719]
Your interesting traffic needs to deny ospf -Original Message- From: neil K. [mailto:[EMAIL PROTECTED]] Sent: 09 January 2003 19:25 To: [EMAIL PROTECTED] Subject: OSPF DEMAND-CIRCUIT, not stopping the link UPDOWN [7:60719] Guys, The ISDN back between two of my routers keeps on dialling. I am running ospf over the ISDN which is a backup for frame relay link. I have configured the ISDN bri with ip ospf demand-circuit and still it keeps dialling.I have even used no peer-neighbor command on the interface. Please help. Thanks in Advance. neil k. Message Posted at: http://www.groupstudy.com/form/read.php?f=7&i=60792&t=60719 -- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
Re: OSPF DEMAND-CIRCUIT, not stopping the link UPDOWN [7:60719]
I mean sh dialer. PPP multilink is enabled on the circuit. also no peer neighbor-route is defined. Still having problems. neil ""neil K."" wrote in message [EMAIL PROTECTED]">news:[EMAIL PROTECTED]... > Guys, > > The ISDN back between two of my routers keeps on dialling. I am running ospf > over the ISDN which is a backup for frame relay link. I have configured the > ISDN bri with ip ospf demand-circuit and still it keeps dialling.I have even > used no peer-neighbor command on the interface. > Please help. > > Thanks in Advance. > > neil k. Message Posted at: http://www.groupstudy.com/form/read.php?f=7&i=60791&t=60719 -- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
Re: OSPF DEMAND-CIRCUIT, not stopping the link UPDOWN [7:60719]
I just found on this URL on the cisco's web site and as many of us suggested the following could be one of the reasons : http://www.cisco.com/warp/public/104/dcprob.html On the bri interfaces 1. Encapsulation should be ppp and " no peer neighbor-route" should be configured. 2. " ip ospf network point-point "or multipoint should be configured and several more. HTH, Rajesh Cisco Nuts wrote: > Guess, what!! > > I had the exact same problem till this morning. I found out that if I > have HDLC encap, then it would keep bringing up the line.Cofigured > ppp encap with the no peer neighbor-routehad the ip ospf > demand-circuit on both sides and now it works fine > > But not really sure if ppp encap or the no peer neighbor route had > anything to do with this but > > >From: "Eisert, James A (Jad) %" >Reply-To: "Eisert, James A (Jad) %" > >To: [EMAIL PROTECTED] >Subject: RE: OSPF DEMAND-CIRCUIT, not stopping > the link UPDOWN [7:60719] >Date: Thu, 9 Jan 2003 18:41:18 GMT > >Have you > done a "debug interesting packets" to see exactly what is causing >your > dialer to dial? > >James A Eisert (Jad) >HP Managed Services at Agere > Systems >Agere Operations Center >610-712-5700 >[EMAIL PROTECTED] > > > -Original Message- >From: neil K. [mailto:[EMAIL PROTECTED]] > >Sent: Thursday, January 09, 2003 12:25 PM >To: [EMAIL PROTECTED] > >Subject: OSPF DEMAND-CIRCUIT, not stopping the link UPDOWN [7:60719] > > >Guys, > >The ISDN back between two of my routers keeps on dialling. I am > running ospf >over the ISDN which is a backup for frame relay link. I > have configured the >ISDN bri with ip ospf demand-circuit and still it > keeps dialling.I have even >used no peer-neighbor command on the > interface. >Please help. > >Thanks in Advance. > >neil k. > > > > > misconduct and Nondisclosure violations to [EMAIL PROTECTED] > > > > MSN 8: advanced junk mail protection and 2 months FREE* Message Posted at: http://www.groupstudy.com/form/read.php?f=7&i=60779&t=60719 -- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
Re: OSPF DEMAND-CIRCUIT, not stopping the link UPDOWN [7:60719]
Hi, please check you route table and OSPF database. Have you route via ISDN link less cost then originaly link? Wojtek Message Posted at: http://www.groupstudy.com/form/read.php?f=7&i=60746&t=60719 -- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
Re: OSPF DEMAND-CIRCUIT, not stopping the link UPDOWN [7:60719]
I ASSume you mean debug dialer!?! Dave Eisert, James A (Jad) % wrote: > Have you done a "debug interesting packets" to see exactly what is causing > your dialer to dial? > > James A Eisert (Jad) > HP Managed Services at Agere Systems > Agere Operations Center > 610-712-5700 > [EMAIL PROTECTED] > > -Original Message- > From: neil K. [mailto:[EMAIL PROTECTED]] > Sent: Thursday, January 09, 2003 12:25 PM > To: [EMAIL PROTECTED] > Subject: OSPF DEMAND-CIRCUIT, not stopping the link UPDOWN [7:60719] > > Guys, > > The ISDN back between two of my routers keeps on dialling. I am running ospf > over the ISDN which is a backup for frame relay link. I have configured the > ISDN bri with ip ospf demand-circuit and still it keeps dialling.I have even > used no peer-neighbor command on the interface. > Please help. > > Thanks in Advance. > > neil k. -- David Madland CCIE# 2016 Sr. Network Engineer Qwest Communications 612-664-3367 "You don't make the poor richer by making the rich poorer." --Winston Churchill Message Posted at: http://www.groupstudy.com/form/read.php?f=7&i=60730&t=60719 -- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
RE: OSPF DEMAND-CIRCUIT, not stopping the link UPDOWN [7:60719]
Guess, what!! I had the exact same problem till this morning. I found out that if I have HDLC encap, then it would keep bringing up the line.Cofigured ppp encap with the no peer neighbor-routehad the ip ospf demand-circuit on both sides and now it works fine But not really sure if ppp encap or the no peer neighbor route had anything to do with this but >From: "Eisert, James A (Jad) %" >Reply-To: "Eisert, James A (Jad) %" >To: [EMAIL PROTECTED] >Subject: RE: OSPF DEMAND-CIRCUIT, not stopping the link UPDOWN [7:60719] >Date: Thu, 9 Jan 2003 18:41:18 GMT > >Have you done a "debug interesting packets" to see exactly what is causing >your dialer to dial? > >James A Eisert (Jad) >HP Managed Services at Agere Systems >Agere Operations Center >610-712-5700 >[EMAIL PROTECTED] > > -Original Message- >From: neil K. [mailto:[EMAIL PROTECTED]] >Sent: Thursday, January 09, 2003 12:25 PM >To: [EMAIL PROTECTED] >Subject: OSPF DEMAND-CIRCUIT, not stopping the link UPDOWN [7:60719] > >Guys, > >The ISDN back between two of my routers keeps on dialling. I am running ospf >over the ISDN which is a backup for frame relay link. I have configured the >ISDN bri with ip ospf demand-circuit and still it keeps dialling.I have even >used no peer-neighbor command on the interface. >Please help. > >Thanks in Advance. > >neil k. > > > > misconduct and Nondisclosure violations to [EMAIL PROTECTED] MSN 8: advanced junk mail protection and 2 months FREE* Message Posted at: http://www.groupstudy.com/form/read.php?f=7&i=60729&t=60719 -- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
RE: OSPF DEMAND-CIRCUIT, not stopping the link UPDOWN [7:60719]
Have you done a "debug interesting packets" to see exactly what is causing your dialer to dial? James A Eisert (Jad) HP Managed Services at Agere Systems Agere Operations Center 610-712-5700 [EMAIL PROTECTED] -Original Message- From: neil K. [mailto:[EMAIL PROTECTED]] Sent: Thursday, January 09, 2003 12:25 PM To: [EMAIL PROTECTED] Subject: OSPF DEMAND-CIRCUIT, not stopping the link UPDOWN [7:60719] Guys, The ISDN back between two of my routers keeps on dialling. I am running ospf over the ISDN which is a backup for frame relay link. I have configured the ISDN bri with ip ospf demand-circuit and still it keeps dialling.I have even used no peer-neighbor command on the interface. Please help. Thanks in Advance. neil k. Message Posted at: http://www.groupstudy.com/form/read.php?f=7&i=60725&t=60719 -- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
OSPF DEMAND-CIRCUIT, not stopping the link UPDOWN [7:60719]
Guys, The ISDN back between two of my routers keeps on dialling. I am running ospf over the ISDN which is a backup for frame relay link. I have configured the ISDN bri with ip ospf demand-circuit and still it keeps dialling.I have even used no peer-neighbor command on the interface. Please help. Thanks in Advance. neil k. Message Posted at: http://www.groupstudy.com/form/read.php?f=7&i=60719&t=60719 -- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
RE: ip ospf demand-circuit?? [7:55501]
Hi, The answer is NO, you don't need to deny ospf as interesting traffic in the ACL. In fact , having read rfc 1793 (http://www.ietf.org/rfc/rfc1793.txt)which explains demand ccts and I think that by doing this you will break the demand cct feature. OSPF requires that initially the database should be synchronised and only brings the link up when various LSA changes occur. HTH :) Richard Message Posted at: http://www.groupstudy.com/form/read.php?f=7&i=55544&t=55501 -- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
ip ospf demand-circuit?? [7:55501]
Hello, Had a question on ip ospf demand-circuit? For an isdn bri backup for 2 sites running ospf, in addition to the ip ospf demand-circuit command on both the interfaces, is it necessary to configure: #dialer-list 1 prot ip list 101 ! #access-list 101 deny ospf any any #access-list 101 permit ip any any Should this be configured on one router or both routers? Are static routes with a high AD also necessary if all the networks are configured under OSPF?? I wouldn't think so but Please advise. Thank you. Sincerely. _ Chat with friends online, try MSN Messenger: http://messenger.msn.com Message Posted at: http://www.groupstudy.com/form/read.php?f=7&i=55501&t=55501 -- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
RE: FW: OSPF Demand Circuit issues [7:46864]
The OSPF demand circuit command only needs to be placed on the router that is dialing, unless the ISDN is active, r5 is not receiving hellos, or an LSA refresh every 30 minutes so the dead timer on the LSAs would expire. This is overcome with the OSPF demand circuit command. From the output of your dedug dialer, OSPF Hellos are what is causing the link to come every 10 seconds, the default for OSPF point-to-point. Just remove the command from r3's interface. To examine the Do Not Age, you can do an ip ospf neighbor command and you will see a '-' as the value in the dead timer. I don't see your OSPF config, but the adjacency issue, if you're doing stub areas make sure both routers are negotiating the same area type. Hope this helps. Message Posted at: http://www.groupstudy.com/form/read.php?f=7&i=46898&t=46864 -- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
Re: OSPF Demand Circuit Mystery [7:34732]
Okay, nevermind! I discovered what was occurring. I was misunderstanding my own configuration. On a remote router I was redistributing IS-IS into OSPF. So, when my local interface--running IS-IS--went down, this triggered an LSA update remotely, which in turn caused the OSPF demand circuit to come up. The scenario is setup as if the local side will be doing the dialing, but in practice that's just not going to happen because of the topology. With this setup, the remote side will always be the side to bring up the demand circuit even if the triggering event occurs locally. Maybe I should quit for the night and get some sleep. ;-) John Get your own "800" number Voicemail, fax, email, and a lot more http://www.ureach.com/reg/tag On Thu, 7 Feb 2002, John Neiberger ([EMAIL PROTECTED]) wrote: > Okay, maybe it doesn't quite qualify as a mystery but it just > occurred to me that I don't know what actually triggers a > demand circuit to come up. I *thought* I did until I ran into > a new scenario tonight that confused me. > > In this scenario, IS-IS and OSPF are running on a router, but > only one interface is participating in OSPF and that is the one > configured as a demand circuit. So, under normal operations > there are no OSPF routes in the routing table, only IS-IS > routes. > > In the usual situation where OSPF is running on multiple > interfaces, I assumed it was some function of OSPF that > triggered the demand circuit to come up. In that situation > there is an interface running OSPF that is aware that the > adjacency went down and that could trigger the demand circuit. > > However, in this case, only IS-IS is running on the main > interface. What is it that actually causes the OSPF demand > circuit to come up? I don't see how it could simply be a > topology change since OSPF isn't aware of the IS-IS topology. > > So, specifically, what is occurring? Perhaps I'm being dense > but I just don't see which mechanism is responsible for this. > > Someone, please put me out of my misery. :-) > > Thanks, > John > > > Get your own "800" number > Voicemail, fax, email, and a lot more > http://www.ureach.com/reg/tag [EMAIL PROTECTED] Message Posted at: http://www.groupstudy.com/form/read.php?f=7&i=34733&t=34732 -- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
OSPF Demand Circuit Mystery [7:34732]
Okay, maybe it doesn't quite qualify as a mystery but it just occurred to me that I don't know what actually triggers a demand circuit to come up. I *thought* I did until I ran into a new scenario tonight that confused me. In this scenario, IS-IS and OSPF are running on a router, but only one interface is participating in OSPF and that is the one configured as a demand circuit. So, under normal operations there are no OSPF routes in the routing table, only IS-IS routes. In the usual situation where OSPF is running on multiple interfaces, I assumed it was some function of OSPF that triggered the demand circuit to come up. In that situation there is an interface running OSPF that is aware that the adjacency went down and that could trigger the demand circuit. However, in this case, only IS-IS is running on the main interface. What is it that actually causes the OSPF demand circuit to come up? I don't see how it could simply be a topology change since OSPF isn't aware of the IS-IS topology. So, specifically, what is occurring? Perhaps I'm being dense but I just don't see which mechanism is responsible for this. Someone, please put me out of my misery. :-) Thanks, John Get your own "800" number Voicemail, fax, email, and a lot more http://www.ureach.com/reg/tag Message Posted at: http://www.groupstudy.com/form/read.php?f=7&i=34732&t=34732 -- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
Question on route loop when using OSPF demand circuit [7:22076]
Hi Group, When viewing CCIE power session presentation of Networkers 2000, I could not understand why you could form route loop when using ospf demand circuit. Here is the example given there: interface BRI0 ip ospf 1.1.1.1 255.255.255.0 ip ospf demand-circiut ! router ospf 10 redistribute rip subnets network 1.1.1.1 0.0.0.0 area 5 ! router rip redistribute connected network 3.0.0.0 default-metric 3 The power session could be found at http://www.ieng.com/networkers/nw00/pres/3304/3304_c1_sec7.pdf thanks, J _ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com Message Posted at: http://www.groupstudy.com/form/read.php?f=7&i=22076&t=22076 -- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
OSPF demand-circuit over dialer profile [7:20741]
Does anyone have a successful config for ospf demand-circuit over ISDN, where the dialer profile is used ? My config is as follows, but whenever I put "ip ospf demand-circuit" on dialer interface 1 (of RA), the "show ip ospf" command will show it not a ABR anymore and OSPF stop to work right away! Thanks Andy RA config -- ! version 11.3 no service password-encryption ! hostname RA ! enable secret 5 $1$z3DF$3JKut/S8iklU.C/OFGKIZ0 ! username RB password 0 abc123 memory-size iomem 15 isdn switch-type basic-5ess ! interface Loopback0 ip address 1.1.1.13 255.255.255.0 ! interface Ethernet 0 ip address 172.16.1.1 255.255.255.0 ! interface BRI3/0 no ip address encapsulation ppp ip ospf demand-circuit dialer pool-member 1 ppp authentication chap ! interface BRI3/1 no ip address shutdown ! interface BRI3/2 no ip address shutdown ! interface BRI3/3 no ip address shutdown ! interface Dialer1 ip address 10.1.1.2 255.255.255.0 encapsulation ppp ip ospf demand-circuit dialer remote-name RB dialer string 4125993507 dialer pool 1 dialer-group 1 no peer neighbor-route ppp authentication chap ! router ospf 100 network 10.1.1.0 0.0.0.255 area 0 network 172.16.1.0 0.0.0.255 area 5 ! ip classless dialer-list 1 protocol ip permit ! line con 0 exec-timeout 0 0 logging synchronous line aux 0 line vty 0 4 login ! end --- RB config ! version 11.3 no service password-encryption ! hostname RB ! enable secret 5 $1$z3DF$3JKut/S8iklU.C/OFGKIZ0 ! username RA password 0 abc123 memory-size iomem 15 isdn switch-type basic-5ess ! interface Loopback0 ip address 1.1.1.12 255.255.255.0 ! interface Ethernet 0 ip address 192.168.1.1 255.255.255.0 ! interface BRI3/0 no ip address encapsulation ppp ip ospf demand-circuit dialer pool-member 1 ppp authentication chap ! interface BRI3/1 no ip address shutdown ! interface BRI3/2 no ip address shutdown ! interface BRI3/3 no ip address shutdown ! interface Dialer1 ip address 10.1.1.1 255.255.255.0 encapsulation ppp ip ospf demand-circuit dialer remote-name RB dialer string 4125993508 dialer pool 1 dialer-group 1 no peer neighbor-route ppp authentication chap ! router ospf 100 network 10.1.1.0 0.0.0.255 area 0 network 192.168.1.0 0.0.0.255 area 5 ! ip classless dialer-list 1 protocol ip permit ! line con 0 exec-timeout 0 0 logging synchronous line aux 0 line vty 0 4 login ! end _ Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp Message Posted at: http://www.groupstudy.com/form/read.php?f=7&i=20741&t=20741 -- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
Re: OSPF demand Circuit [7:20228]
Lance, You should be able to use this command on typically any router that at mimimum has an "aux" port. A quick look on CCO for the command "ip ospf demand-circuit" showed that the command was supported from version 11.2. HTH Nigel Chuck.. maybe when you talk to your ISP the word "rebate" should make it's way into the conversation. ;-> - Original Message - From: "Chuck Larrieu" To: Sent: Tuesday, September 18, 2001 10:35 PM Subject: RE: OSPF demand Circuit [7:20228] > I don't know the answer, so I will ask: > > isn't demand circuit a part of the OSPF specification, per RFC 1793? ( and > please don't rag on me if I misremembered the RFC #. My ISP has apparently > been crippled by the nambia worm, and I can't get to any web sites tonight ) > > Chuck > > -Original Message- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of > Lance > Sent: Tuesday, September 18, 2001 10:06 AM > To: [EMAIL PROTECTED] > Subject: Re: OSPF demand Circuit [7:20228] > > > Is there any way I can find which routers do not support it, I assume that > each router must run IOS 11.3 or later? > > Thanks, > Lance > > > ""Sasa Milic"" wrote in message > [EMAIL PROTECTED]">news:[EMAIL PROTECTED]... > > Lance, > > > > DNA LSAs are not allowed because router received LSAs (ten different > > LSAa) without DC bit set in options field from other routers in the > > area. That means that there are routers in the area which doesn't > > support demand circuit. As you remember, in order to support DNAs, > > all routers in the area must support it, which is not the case in > > your network. > > > > Sasa > > > > > > Lance wrote: > > > > > > I have R6 connected to R5 via an ethernet and a ISDN link. The ISDN > link > > is > > > configured as an OSPF demand circuit however when I do a show ip ospf > int I > > > get the following output. Notice that it says "DoNotAge LSA not allowed > > > (Number of DCbitless LSA is 10)". Why is this, I need for the DoNotAge > LSA > > > to be allowed and I thought this is what ospf demand-circuit is for. > BTW > > > this is CCbootcamp lab 8a. Please help? > > > > > > R6#sho ip ospf int bri0 > > > BRI0 is up, line protocol is up (spoofing) > > > Internet Address 137.20.224.6/20, Area 0 > > > Process ID 64, Router ID 137.20.60.1, Network Type POINT_TO_POINT, > Cost: > > > 1562 > > > Configured as demand circuit. > > > Run as demand circuit. > > > DoNotAge LSA not allowed (Number of DCbitless LSA is 10). > > > Transmit Delay is 1 sec, State POINT_TO_POINT, > > > Timer intervals configured, Hello 10, Dead 40, Wait 40, Retransmit 5 > > > Hello due in 00:00:06 > > > Neighbor Count is 1, Adjacent neighbor count is 1 > > > Adjacent with neighbor 137.20.240.1 (Hello suppressed) > > > Suppress hello for 1 neighbor(s) Message Posted at: http://www.groupstudy.com/form/read.php?f=7&i=20355&t=20228 -- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
RE: OSPF demand Circuit [7:20228]
I don't know the answer, so I will ask: isn't demand circuit a part of the OSPF specification, per RFC 1793? ( and please don't rag on me if I misremembered the RFC #. My ISP has apparently been crippled by the nambia worm, and I can't get to any web sites tonight ) Chuck -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Lance Sent: Tuesday, September 18, 2001 10:06 AM To: [EMAIL PROTECTED] Subject: Re: OSPF demand Circuit [7:20228] Is there any way I can find which routers do not support it, I assume that each router must run IOS 11.3 or later? Thanks, Lance ""Sasa Milic"" wrote in message [EMAIL PROTECTED]">news:[EMAIL PROTECTED]... > Lance, > > DNA LSAs are not allowed because router received LSAs (ten different > LSAa) without DC bit set in options field from other routers in the > area. That means that there are routers in the area which doesn't > support demand circuit. As you remember, in order to support DNAs, > all routers in the area must support it, which is not the case in > your network. > > Sasa > > > Lance wrote: > > > > I have R6 connected to R5 via an ethernet and a ISDN link. The ISDN link > is > > configured as an OSPF demand circuit however when I do a show ip ospf int I > > get the following output. Notice that it says "DoNotAge LSA not allowed > > (Number of DCbitless LSA is 10)". Why is this, I need for the DoNotAge LSA > > to be allowed and I thought this is what ospf demand-circuit is for. BTW > > this is CCbootcamp lab 8a. Please help? > > > > R6#sho ip ospf int bri0 > > BRI0 is up, line protocol is up (spoofing) > > Internet Address 137.20.224.6/20, Area 0 > > Process ID 64, Router ID 137.20.60.1, Network Type POINT_TO_POINT, Cost: > > 1562 > > Configured as demand circuit. > > Run as demand circuit. > > DoNotAge LSA not allowed (Number of DCbitless LSA is 10). > > Transmit Delay is 1 sec, State POINT_TO_POINT, > > Timer intervals configured, Hello 10, Dead 40, Wait 40, Retransmit 5 > > Hello due in 00:00:06 > > Neighbor Count is 1, Adjacent neighbor count is 1 > > Adjacent with neighbor 137.20.240.1 (Hello suppressed) > > Suppress hello for 1 neighbor(s) Message Posted at: http://www.groupstudy.com/form/read.php?f=7&i=20346&t=20228 -- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
Re: OSPF demand Circuit [7:20228]
"show ip ospf database router", look at LSAs without DC in options field. Sasa Lance wrote: > > Is there any way I can find which routers do not support it, I assume that > each router must run IOS 11.3 or later? > > Thanks, > Lance > > ""Sasa Milic"" wrote in message > [EMAIL PROTECTED]">news:[EMAIL PROTECTED]... > > Lance, > > > > DNA LSAs are not allowed because router received LSAs (ten different > > LSAa) without DC bit set in options field from other routers in the > > area. That means that there are routers in the area which doesn't > > support demand circuit. As you remember, in order to support DNAs, > > all routers in the area must support it, which is not the case in > > your network. > > > > Sasa > > > > > > Lance wrote: > > > > > > I have R6 connected to R5 via an ethernet and a ISDN link. The ISDN > link > > is > > > configured as an OSPF demand circuit however when I do a show ip ospf > int I > > > get the following output. Notice that it says "DoNotAge LSA not allowed > > > (Number of DCbitless LSA is 10)". Why is this, I need for the DoNotAge > LSA > > > to be allowed and I thought this is what ospf demand-circuit is for. > BTW > > > this is CCbootcamp lab 8a. Please help? > > > > > > R6#sho ip ospf int bri0 > > > BRI0 is up, line protocol is up (spoofing) > > > Internet Address 137.20.224.6/20, Area 0 > > > Process ID 64, Router ID 137.20.60.1, Network Type POINT_TO_POINT, > Cost: > > > 1562 > > > Configured as demand circuit. > > > Run as demand circuit. > > > DoNotAge LSA not allowed (Number of DCbitless LSA is 10). > > > Transmit Delay is 1 sec, State POINT_TO_POINT, > > > Timer intervals configured, Hello 10, Dead 40, Wait 40, Retransmit 5 > > > Hello due in 00:00:06 > > > Neighbor Count is 1, Adjacent neighbor count is 1 > > > Adjacent with neighbor 137.20.240.1 (Hello suppressed) > > > Suppress hello for 1 neighbor(s) Message Posted at: http://www.groupstudy.com/form/read.php?f=7&i=20307&t=20228 -- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
Re: OSPF demand Circuit [7:20228]
Is there any way I can find which routers do not support it, I assume that each router must run IOS 11.3 or later? Thanks, Lance ""Sasa Milic"" wrote in message [EMAIL PROTECTED]">news:[EMAIL PROTECTED]... > Lance, > > DNA LSAs are not allowed because router received LSAs (ten different > LSAa) without DC bit set in options field from other routers in the > area. That means that there are routers in the area which doesn't > support demand circuit. As you remember, in order to support DNAs, > all routers in the area must support it, which is not the case in > your network. > > Sasa > > > Lance wrote: > > > > I have R6 connected to R5 via an ethernet and a ISDN link. The ISDN link > is > > configured as an OSPF demand circuit however when I do a show ip ospf int I > > get the following output. Notice that it says "DoNotAge LSA not allowed > > (Number of DCbitless LSA is 10)". Why is this, I need for the DoNotAge LSA > > to be allowed and I thought this is what ospf demand-circuit is for. BTW > > this is CCbootcamp lab 8a. Please help? > > > > R6#sho ip ospf int bri0 > > BRI0 is up, line protocol is up (spoofing) > > Internet Address 137.20.224.6/20, Area 0 > > Process ID 64, Router ID 137.20.60.1, Network Type POINT_TO_POINT, Cost: > > 1562 > > Configured as demand circuit. > > Run as demand circuit. > > DoNotAge LSA not allowed (Number of DCbitless LSA is 10). > > Transmit Delay is 1 sec, State POINT_TO_POINT, > > Timer intervals configured, Hello 10, Dead 40, Wait 40, Retransmit 5 > > Hello due in 00:00:06 > > Neighbor Count is 1, Adjacent neighbor count is 1 > > Adjacent with neighbor 137.20.240.1 (Hello suppressed) > > Suppress hello for 1 neighbor(s) Message Posted at: http://www.groupstudy.com/form/read.php?f=7&i=20303&t=20228 -- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
Re: OSPF demand Circuit [7:20228]
Lance, DNA LSAs are not allowed because router received LSAs (ten different LSAa) without DC bit set in options field from other routers in the area. That means that there are routers in the area which doesn't support demand circuit. As you remember, in order to support DNAs, all routers in the area must support it, which is not the case in your network. Sasa Lance wrote: > > I have R6 connected to R5 via an ethernet and a ISDN link. The ISDN link is > configured as an OSPF demand circuit however when I do a show ip ospf int I > get the following output. Notice that it says "DoNotAge LSA not allowed > (Number of DCbitless LSA is 10)". Why is this, I need for the DoNotAge LSA > to be allowed and I thought this is what ospf demand-circuit is for. BTW > this is CCbootcamp lab 8a. Please help? > > R6#sho ip ospf int bri0 > BRI0 is up, line protocol is up (spoofing) > Internet Address 137.20.224.6/20, Area 0 > Process ID 64, Router ID 137.20.60.1, Network Type POINT_TO_POINT, Cost: > 1562 > Configured as demand circuit. > Run as demand circuit. > DoNotAge LSA not allowed (Number of DCbitless LSA is 10). > Transmit Delay is 1 sec, State POINT_TO_POINT, > Timer intervals configured, Hello 10, Dead 40, Wait 40, Retransmit 5 > Hello due in 00:00:06 > Neighbor Count is 1, Adjacent neighbor count is 1 > Adjacent with neighbor 137.20.240.1 (Hello suppressed) > Suppress hello for 1 neighbor(s) Message Posted at: http://www.groupstudy.com/form/read.php?f=7&i=20231&t=20228 -- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
OSPF demand Circuit [7:20228]
I have R6 connected to R5 via an ethernet and a ISDN link. The ISDN link is configured as an OSPF demand circuit however when I do a show ip ospf int I get the following output. Notice that it says "DoNotAge LSA not allowed (Number of DCbitless LSA is 10)". Why is this, I need for the DoNotAge LSA to be allowed and I thought this is what ospf demand-circuit is for. BTW this is CCbootcamp lab 8a. Please help? R6#sho ip ospf int bri0 BRI0 is up, line protocol is up (spoofing) Internet Address 137.20.224.6/20, Area 0 Process ID 64, Router ID 137.20.60.1, Network Type POINT_TO_POINT, Cost: 1562 Configured as demand circuit. Run as demand circuit. DoNotAge LSA not allowed (Number of DCbitless LSA is 10). Transmit Delay is 1 sec, State POINT_TO_POINT, Timer intervals configured, Hello 10, Dead 40, Wait 40, Retransmit 5 Hello due in 00:00:06 Neighbor Count is 1, Adjacent neighbor count is 1 Adjacent with neighbor 137.20.240.1 (Hello suppressed) Suppress hello for 1 neighbor(s) Message Posted at: http://www.groupstudy.com/form/read.php?f=7&i=20228&t=20228 -- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
ISDN Dialer Watch / IP OSPF Demand Circuit
Hi all, I am in the process of configuration a bunch of routers to do ISDN dial backup. Has any body worked with Dialer Watch on a router running OSPF? I know that some Cisco document says that Dialer Watch is only supported in EIGRP and IGRP. But others say any Dynamic routing protocols. Also, has any one used the IP OSPF Demand Circuit? This option is suppose to control the types of LSAs that are sent across the dial line. It reduces the amount of Access-list that is needed to monitor the traffic. Basically, I am using 4 BRIs in a Dialer Interface with ip unnumbered Loopback0. Then, I will be using Dialer Watch to trigger the ISDN calls and run OSPF Demand Circuit to control packed over the dial link. Defaulting back to the serial link will be done based on OSPF cost statement once the link comes back. Does this sound like it's feasible or is it too much to handle? Any help will be greatly appreciated! Evan You - CCNA / Soon to be CCNP interface BRI1/0 description connected into a rotary group no ip address encapsulation ppp dialer rotary-group 0 isdn switch-type basic-net3 isdn T310 1 no fair-queue no cdp enable ! interface BRI1/1 no ip address encapsulation ppp dialer rotary-group 0 isdn switch-type basic-net3 isdn T310 1 no fair-queue no cdp enable ! interface BRI1/2 no ip address encapsulation ppp dialer rotary-group 0 isdn switch-type basic-net3 isdn T310 1 no fair-queue no cdp enable ! interface BRI1/3 no ip address encapsulation ppp dialer rotary-group 0 isdn switch-type basic-net3 isdn T310 1 no fair-queue no cdp enable ! interface Dialer0 description Dialer group controlling the BRIs ip unnumbered Loopback0 encapsulation ppp ip ospf cost 1500 ip ospf demand-circuit dialer in-band dialer idle-timeout 500 dialer map ip 53.29.248.2 name hostname broadcast 000 dialer load-threshold 30 either dialer watch-group 1 no fair-queue no cdp enable ppp authentication chap ppp multilink hold-queue 100 in ! dialer watch-list 1 ip 10.10.10.10 255.255.255.252 dialer watch-list 1 ip 10.1.2.12 255.255.255.252 Evan You - CCNA / Soon CCNP _ FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
ISDN Dialer Watch / IP OSPF Demand Circuit
Hi all, I am in the process of configuration a bunch of routers to do ISDN dial backup. Has any body worked with Dialer Watch on a router running OSPF? I know that some Cisco document says that Dialer Watch is only supported in EIGRP and IGRP. But others say any Dynamic routing protocols. Also, has any one used the IP OSPF Demand Circuit? This option is suppose to control the types of LSAs that are sent across the dial line. It reduces the amount of Access-list that is needed to monitor the traffic. Basically, I am using 4 BRIs in a Dialer Interface with ip unnumbered Loopback0. Then, I will be using Dialer Watch to trigger the ISDN calls and run OSPF Demand Circuit to control packed over the dial link. Defaulting back to the serial link will be done based on OSPF cost statement once the link comes back. Does this sound like it's feasible or is it too much to handle? Any help will be greatly appreciated! Evan You - CCNA / Soon to be CCNP interface BRI1/0 description connected into a rotary group no ip address encapsulation ppp dialer rotary-group 0 isdn switch-type basic-net3 isdn T310 1 no fair-queue no cdp enable ! interface BRI1/1 no ip address encapsulation ppp dialer rotary-group 0 isdn switch-type basic-net3 isdn T310 1 no fair-queue no cdp enable ! interface BRI1/2 no ip address encapsulation ppp dialer rotary-group 0 isdn switch-type basic-net3 isdn T310 1 no fair-queue no cdp enable ! interface BRI1/3 no ip address encapsulation ppp dialer rotary-group 0 isdn switch-type basic-net3 isdn T310 1 no fair-queue no cdp enable ! interface Dialer0 description Dialer group controlling the BRIs ip unnumbered Loopback0 encapsulation ppp ip ospf cost 1500 ip ospf demand-circuit dialer in-band dialer idle-timeout 500 dialer map ip 53.29.248.2 name hostname broadcast XX dialer load-threshold 30 either dialer watch-group 1 no fair-queue no cdp enable ppp authentication chap ppp multilink hold-queue 100 in ! dialer watch-list 1 ip 10.10.10.10 255.255.255.252 dialer watch-list 1 ip 10.1.2.12 255.255.255.252 Evan You - CCNA / Soon CCNP _ FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
ISDN Dialer Watch / OSPF Demand Circuit
Hi all, I am in the process of configuration a bunch of routers to do ISDN dial backup. Has any body worked with Dialer Watch on a router running OSPF? I know that some Cisco document says that Dialer Watch is only supported in EIGRP and IGRP. But others say any Dynamic routing protocols. Also, has any one used the IP OSPF Demand Circuit? This option is suppose to control the types of LSAs that are sent across the dial line. It reduces the amount of Access-list that is needed to monitor the traffic. Basically, I am using 4 BRIs in a Dialer Interface with ip unnumbered Loopback0. Then, I will be using Dialer Watch to trigger the ISDN calls and run OSPF Demand Circuit to control packed over the dial link. Defaulting back to the serial link will be done based on OSPF cost statement once the link comes back. Does this sound like it's feasible or is it too much to handle? Any help will be greatly appreciated! Evan You - CCNA / Soon to be CCNP interface BRI1/0 description connected into a rotary group no ip address encapsulation ppp dialer rotary-group 0 isdn switch-type basic-net3 isdn T310 1 no fair-queue no cdp enable ! interface BRI1/1 no ip address encapsulation ppp dialer rotary-group 0 isdn switch-type basic-net3 isdn T310 1 no fair-queue no cdp enable ! interface BRI1/2 no ip address encapsulation ppp dialer rotary-group 0 isdn switch-type basic-net3 isdn T310 1 no fair-queue no cdp enable ! interface BRI1/3 no ip address encapsulation ppp dialer rotary-group 0 isdn switch-type basic-net3 isdn T310 1 no fair-queue no cdp enable ! interface Dialer0 description Dialer group controlling the BRIs ip unnumbered Loopback0 encapsulation ppp ip ospf cost 1500 ip ospf demand-circuit dialer in-band dialer idle-timeout 500 dialer map ip 53.29.248.2 name hostname broadcast XX dialer load-threshold 30 either dialer watch-group 1 no fair-queue no cdp enable ppp authentication chap ppp multilink hold-queue 100 in ! dialer watch-list 1 ip 10.10.10.10 255.255.255.252 dialer watch-list 1 ip 10.1.2.12 255.255.255.252 _ FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
RE: OSPF Demand-Circuit External Routes
Either build an access-list to filter the route advertisements or if you are running 12.0 or newer code use the "no peer neighbor-route" statement on both ends at the interface level. When I disagree with a rational man, I let reality be our final arbiter; If I am right, he will learn, If I am wrong, I will; one of us will win, but both of us will profit. - John Galt -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Brian Sent: Wednesday, November 29, 2000 10:40 PM To: Bob Henry Cc: [EMAIL PROTECTED] Subject: Re: OSPF Demand-Circuit External Routes On Wed, 29 Nov 2000, Bob Henry wrote: > All, > > I have a question in regardds to using the > ospf demand-circuit. > > If you are using ospf demand circuit across an ISDN > line and do not want it to dial when external routes > that were redistributed into OSPF flap how is this > done? one way would be to enable summarization > > Thanks, > Jack > > __ > Do You Yahoo!? > Yahoo! Shopping - Thousands of Stores. Millions of Products. > http://shopping.yahoo.com/ > > _ > FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html > Report misconduct and Nondisclosure violations to [EMAIL PROTECTED] > --- Brian Feeny, CCNP, CCDP [EMAIL PROTECTED] Network Administrator ShreveNet Inc. (ASN 11881) _ FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED] _ FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
Re: OSPF Demand-Circuit External Routes
On Wed, 29 Nov 2000, Bob Henry wrote: > All, > > I have a question in regardds to using the > ospf demand-circuit. > > If you are using ospf demand circuit across an ISDN > line and do not want it to dial when external routes > that were redistributed into OSPF flap how is this > done? one way would be to enable summarization > > Thanks, > Jack > > __ > Do You Yahoo!? > Yahoo! Shopping - Thousands of Stores. Millions of Products. > http://shopping.yahoo.com/ > > _ > FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html > Report misconduct and Nondisclosure violations to [EMAIL PROTECTED] > --- Brian Feeny, CCNP, CCDP [EMAIL PROTECTED] Network Administrator ShreveNet Inc. (ASN 11881) _ FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
OSPF Demand-Circuit External Routes
All, I have a question in regardds to using the ospf demand-circuit. If you are using ospf demand circuit across an ISDN line and do not want it to dial when external routes that were redistributed into OSPF flap how is this done? Thanks, Jack __ Do You Yahoo!? Yahoo! Shopping - Thousands of Stores. Millions of Products. http://shopping.yahoo.com/ _ FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
Re: OSPF Demand Circuit...
Louie, I just wonder have you tried to put the "no dialer hold-queue"? I never tested, but I would imagine this should prevent the router from holding the packets while waiting for the call to come up. Please let us know any progress. Good Luck Jack > > ""Louie Belt"" <[EMAIL PROTECTED]> wrote in message > 000201c03e40$f4fbb6e0$[EMAIL PROTECTED]">news:000201c03e40$f4fbb6e0$[EMAIL PROTECTED]... > > While configuring and OSPF demand circuit over ISDN, I noticed that the > ISDN > > link would disconnected and immediately reconnect - because the change in > > ospf topology was triggering and LSA flood - forcing the ISDN line to > > reconnect. However, the dialer enable-timeout setting was at it's default > > of 15 seconds so the ISDN link should have been forced to wait 15 seconds > > before attempting to reconnect (and thereby giving the LSA flood time to > > pass). However, this did not happen. No matter what I set the dialer > > enable-timeout to, the redial happened immediately. > > > > Question: What am I missing? (or mis-understanding) > > > > Thanks in advance! > > > > Louie > > > > > > > > > > > > > > _ > > FAQ, list archives, and subscription info: > http://www.groupstudy.com/list/cisco.html > > Report misconduct and Nondisclosure violations to [EMAIL PROTECTED] > > > > > _ > FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html > Report misconduct and Nondisclosure violations to [EMAIL PROTECTED] > _ FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
Re: OSPF Demand Circuit...
Louie, Ok, here's the scoop. First, this is normal behaviour for a demand circuit and there is no provision in OSPF to handle it. BUT, Cisco has a relatively undocumented command to take care of the flapping. "no peer neighbor-route" I only found out about it's existance by calling TAC. This works great as long as you don't have any virtual links that traverse the ISDN link. You'll need to filter the virtual link traffic in the dialer list also, so the multicast traffic isn't interesting to the dialer. I'm going to be playing with this in my lab in the next week or two. I was thinking of trying to change the link type to non-broadcast, point-to-point, etc. to see if this would be a better/easier setup. I'll let you know if I dig up any more good info. Rodgers Moore ""Louie Belt"" <[EMAIL PROTECTED]> wrote in message 000201c03e40$f4fbb6e0$[EMAIL PROTECTED]">news:000201c03e40$f4fbb6e0$[EMAIL PROTECTED]... > While configuring and OSPF demand circuit over ISDN, I noticed that the ISDN > link would disconnected and immediately reconnect - because the change in > ospf topology was triggering and LSA flood - forcing the ISDN line to > reconnect. However, the dialer enable-timeout setting was at it's default > of 15 seconds so the ISDN link should have been forced to wait 15 seconds > before attempting to reconnect (and thereby giving the LSA flood time to > pass). However, this did not happen. No matter what I set the dialer > enable-timeout to, the redial happened immediately. > > Question: What am I missing? (or mis-understanding) > > Thanks in advance! > > Louie > > > > > > > _ > FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html > Report misconduct and Nondisclosure violations to [EMAIL PROTECTED] > _ FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
RE: OSPF Demand Circuit...
Hi Louie I like to make sure if I understand your solution. The reason why it didn't make difference is that you didn't configure in the interface configuration mode. is that your reason? I will appreciate your reply. jeongwoo --- Louie Belt <[EMAIL PROTECTED]> wrote: > Thanks! That would explain why it never made a > difference. Cisco's info on > it is a bit vague. I got this from the Cisco CD: > > dialer enable-timeout > To set the length of time an interface stays down > after a call has completed > or failed and before it is available to dial again, > use the dialer > enable-timeout interface configuration command. To > return to the default > value, use the no form of this command. > > dialer enable-timeout seconds > no dialer enable-timeout > > Syntax Description > seconds > Time in seconds that the Cisco IOS software waits > before the next call can > occur on the specific interface. Acceptable values > are positive, nonzero > integers. > > This value must be greater than the serial pulse > interval for this > interface, set via the pulse-time command. > > Default > 15 seconds > > Command Mode > Interface configuration > > Usage Guidelines > This command first appeared in Cisco IOS Release > 10.0. > > This command applies to inbound and outbound calls. > > If your phone lines are often busy or down, you > might want to enforce a > certain period of time before the system repeats an > attempt to make a > connection with a remote site. Configuring this > timeout can prevent outgoing > lines and switching equipment from being needlessly > overloaded. > > > Louie > > > > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED]]On Behalf Of > Mark Vicuna > Sent: Wednesday, October 25, 2000 3:09 AM > To: Louie Belt; [EMAIL PROTECTED] > Subject: Re: OSPF Demand Circuit... > > > Louie, > > dialer enable-timeout is used for callback. > > > hth, > Mark. > > At 12:03 AM 10/25/00 -0500, Louie Belt wrote: > >While configuring and OSPF demand circuit over > ISDN, I noticed that the > ISDN > >link would disconnected and immediately reconnect - > because the change in > >ospf topology was triggering and LSA flood - > forcing the ISDN line to > >reconnect. However, the dialer enable-timeout > setting was at it's default > >of 15 seconds so the ISDN link should have been > forced to wait 15 seconds > >before attempting to reconnect (and thereby giving > the LSA flood time to > >pass). However, this did not happen. No matter > what I set the dialer > >enable-timeout to, the redial happened immediately. > > > >Question: What am I missing? (or > mis-understanding) > > > >Thanks in advance! > > > >Louie > > > > > > > > > > > > > >_ > >FAQ, list archives, and subscription info: > >http://www.groupstudy.com/list/cisco.html > >Report misconduct and Nondisclosure violations to > [EMAIL PROTECTED] > > _ > FAQ, list archives, and subscription info: > http://www.groupstudy.com/list/cisco.html > Report misconduct and Nondisclosure violations to > [EMAIL PROTECTED] > > _ > FAQ, list archives, and subscription info: > http://www.groupstudy.com/list/cisco.html > Report misconduct and Nondisclosure violations to [EMAIL PROTECTED] __ Do You Yahoo!? Yahoo! Messenger - Talk while you surf! It's FREE. http://im.yahoo.com/ _ FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
Re: OSPF Demand Circuit...
Can you send output of "show ip ospf inte bri" command ,of your router + the running config o/p Thanks Thangavel - Original Message - From: Sam LI <[EMAIL PROTECTED]> To: Louie Belt <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> Sent: Wednesday, October 25, 2000 5:07 AM Subject: Re: OSPF Demand Circuit... > Louie > > what is missing, your configuration > > Sam Li > - Original Message - > From: Louie Belt <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Sent: Wednesday, October 25, 2000 1:03 PM > Subject: OSPF Demand Circuit... > > > > While configuring and OSPF demand circuit over ISDN, I noticed that the > ISDN > > link would disconnected and immediately reconnect - because the change in > > ospf topology was triggering and LSA flood - forcing the ISDN line to > > reconnect. However, the dialer enable-timeout setting was at it's default > > of 15 seconds so the ISDN link should have been forced to wait 15 seconds > > before attempting to reconnect (and thereby giving the LSA flood time to > > pass). However, this did not happen. No matter what I set the dialer > > enable-timeout to, the redial happened immediately. > > > > Question: What am I missing? (or mis-understanding) > > > > Thanks in advance! > > > > Louie > > > > > > > > > > > > > > _ > > FAQ, list archives, and subscription info: > http://www.groupstudy.com/list/cisco.html > > Report misconduct and Nondisclosure violations to [EMAIL PROTECTED] > > > > _ > FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html > Report misconduct and Nondisclosure violations to [EMAIL PROTECTED] > _ FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
Re: OSPF Demand Circuit...
Louie what is missing, your configuration Sam Li - Original Message - From: Louie Belt <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Wednesday, October 25, 2000 1:03 PM Subject: OSPF Demand Circuit... > While configuring and OSPF demand circuit over ISDN, I noticed that the ISDN > link would disconnected and immediately reconnect - because the change in > ospf topology was triggering and LSA flood - forcing the ISDN line to > reconnect. However, the dialer enable-timeout setting was at it's default > of 15 seconds so the ISDN link should have been forced to wait 15 seconds > before attempting to reconnect (and thereby giving the LSA flood time to > pass). However, this did not happen. No matter what I set the dialer > enable-timeout to, the redial happened immediately. > > Question: What am I missing? (or mis-understanding) > > Thanks in advance! > > Louie > > > > > > > _ > FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html > Report misconduct and Nondisclosure violations to [EMAIL PROTECTED] > _ FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
RE: OSPF Demand Circuit...
Thanks! That would explain why it never made a difference. Cisco's info on it is a bit vague. I got this from the Cisco CD: dialer enable-timeout To set the length of time an interface stays down after a call has completed or failed and before it is available to dial again, use the dialer enable-timeout interface configuration command. To return to the default value, use the no form of this command. dialer enable-timeout seconds no dialer enable-timeout Syntax Description seconds Time in seconds that the Cisco IOS software waits before the next call can occur on the specific interface. Acceptable values are positive, nonzero integers. This value must be greater than the serial pulse interval for this interface, set via the pulse-time command. Default 15 seconds Command Mode Interface configuration Usage Guidelines This command first appeared in Cisco IOS Release 10.0. This command applies to inbound and outbound calls. If your phone lines are often busy or down, you might want to enforce a certain period of time before the system repeats an attempt to make a connection with a remote site. Configuring this timeout can prevent outgoing lines and switching equipment from being needlessly overloaded. Louie -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Mark Vicuna Sent: Wednesday, October 25, 2000 3:09 AM To: Louie Belt; [EMAIL PROTECTED] Subject: Re: OSPF Demand Circuit... Louie, dialer enable-timeout is used for callback. hth, Mark. At 12:03 AM 10/25/00 -0500, Louie Belt wrote: >While configuring and OSPF demand circuit over ISDN, I noticed that the ISDN >link would disconnected and immediately reconnect - because the change in >ospf topology was triggering and LSA flood - forcing the ISDN line to >reconnect. However, the dialer enable-timeout setting was at it's default >of 15 seconds so the ISDN link should have been forced to wait 15 seconds >before attempting to reconnect (and thereby giving the LSA flood time to >pass). However, this did not happen. No matter what I set the dialer >enable-timeout to, the redial happened immediately. > >Question: What am I missing? (or mis-understanding) > >Thanks in advance! > >Louie > > > > > > >_ >FAQ, list archives, and subscription info: >http://www.groupstudy.com/list/cisco.html >Report misconduct and Nondisclosure violations to [EMAIL PROTECTED] _ FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED] _ FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
Re: OSPF Demand Circuit...
Hi. You need use dialer interface or dialer profile. Ls4577 ""Louie Belt"" <[EMAIL PROTECTED]> wrote in message 000201c03e40$f4fbb6e0$[EMAIL PROTECTED]">news:000201c03e40$f4fbb6e0$[EMAIL PROTECTED]... > While configuring and OSPF demand circuit over ISDN, I noticed that the ISDN > link would disconnected and immediately reconnect - because the change in > ospf topology was triggering and LSA flood - forcing the ISDN line to > reconnect. However, the dialer enable-timeout setting was at it's default > of 15 seconds so the ISDN link should have been forced to wait 15 seconds > before attempting to reconnect (and thereby giving the LSA flood time to > pass). However, this did not happen. No matter what I set the dialer > enable-timeout to, the redial happened immediately. > > Question: What am I missing? (or mis-understanding) > > Thanks in advance! > > Louie > > > > > > > _ > FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html > Report misconduct and Nondisclosure violations to [EMAIL PROTECTED] > _ FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
Re: OSPF Demand Circuit...
Louie, dialer enable-timeout is used for callback. hth, Mark. At 12:03 AM 10/25/00 -0500, Louie Belt wrote: >While configuring and OSPF demand circuit over ISDN, I noticed that the ISDN >link would disconnected and immediately reconnect - because the change in >ospf topology was triggering and LSA flood - forcing the ISDN line to >reconnect. However, the dialer enable-timeout setting was at it's default >of 15 seconds so the ISDN link should have been forced to wait 15 seconds >before attempting to reconnect (and thereby giving the LSA flood time to >pass). However, this did not happen. No matter what I set the dialer >enable-timeout to, the redial happened immediately. > >Question: What am I missing? (or mis-understanding) > >Thanks in advance! > >Louie > > > > > > >_ >FAQ, list archives, and subscription info: >http://www.groupstudy.com/list/cisco.html >Report misconduct and Nondisclosure violations to [EMAIL PROTECTED] _ FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
OSPF Demand Circuit...
While configuring and OSPF demand circuit over ISDN, I noticed that the ISDN link would disconnected and immediately reconnect - because the change in ospf topology was triggering and LSA flood - forcing the ISDN line to reconnect. However, the dialer enable-timeout setting was at it's default of 15 seconds so the ISDN link should have been forced to wait 15 seconds before attempting to reconnect (and thereby giving the LSA flood time to pass). However, this did not happen. No matter what I set the dialer enable-timeout to, the redial happened immediately. Question: What am I missing? (or mis-understanding) Thanks in advance! Louie _ FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
Re: OSPF Demand Circuit - About to go crazy! :-)
If you don't specify the < broadcast > in the dialer map statement then the # that the router is supposed to dial won't be broadcasted to the isdn interface.The only way to bring it up would be to ping the ip address in the dialer map ip X.X.X.X and this would broadcast the # in the statement to the dialing device whether it be the router interface or an external device. -jek "Ryan Moffett" <[EMAIL PROTECTED]> wrote in message 8lvv16$m67$[EMAIL PROTECTED]">news:8lvv16$m67$[EMAIL PROTECTED]... > I am beating myself to death with the following: > > I am working through the following scenario in which R1 has a Frame Relay > connection to R2 via Frame-Relay and ISDN. R1 is configured with ip ospf > demand-circuit on the ISDN interface as well as OSPF on the Frame Relay > interface. R1 forms an ajacency with R2 over the Frame Relay link, and > they sucessfully exchange databases. R2 is configured the same as R1 with > the exception of the ip ospf demand-circuit, it does not have that > configured.R1 does not show 2 entries in the show ip ospf neighbor > output. R1 and R2 are not forming adjacencies over the OSPF > demand-circuit.I can ping between R1 and R2's BRI interfaces to bring up > the ISDN link, and it works properly, however, if I shut the Frame Relay > interface down, shouldn't the ISDN link come up as both links are in area 0? > > R1 has the following relavent configuration: > > ! > int s0.102 point-to-point > encapsulation frame-relay > ip address 10.36.18.5 255.255.255.252 > frame-relay interface-dlci 102 > ! > int bri0 > encapsulation ppp > dialer map ip 10.36.19.5 > ip ospf demand-circuit > dialer-group 1 > ! > router ospf 100 > network 10.36.18.5 0.0.0.0 area 0 > network 10.36.19.5 0.0.0.0 area 0 > ! > dialer-list 1 protocol ip permit > > > R2 has the following relavent configuration > > ! > int S0.201 point-to-point > encapsulation frame-relay > ip address 10.36.18.6 255.255.255.252 > frame-relay interface-dlci 201 > ! > int bri0 > encapsulation ppp > dialer map ip 10.36.19.6 > ip ospf demand-circuit > dialer-group 1 > ! > router ospf 100 > network 10.39.18.6 0.0.0.0 area 0 > network 10.39.19.6 0.0.0.0 area 0 > ! > dialer-list 1 protocol ip permit > > Thanks, > Ryan Moffett > > > ___ > UPDATED Posting Guidelines: http://www.groupstudy.com/list/guide.html > FAQ, list archives, and subscription info: http://www.groupstudy.com > Report misconduct and Nondisclosure violations to [EMAIL PROTECTED] > --- ___ UPDATED Posting Guidelines: http://www.groupstudy.com/list/guide.html FAQ, list archives, and subscription info: http://www.groupstudy.com Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
Re: OSPF Demand Circuit - About to go crazy! :-)
Well, that nailed up the ISDN connection for good, but OSPF adjacencies still did not form I had to change my dialer map statements to dialer string statements... dialer string on R1 dialer string on R3 ...and it magically worked.now, why? Why did it have a problem with the dialer map ip statements? I will try to figure that out, but at least I know now what I need to do in this scenario. ""Aaron K. Dixon"" <[EMAIL PROTECTED]> wrote in message [EMAIL PROTECTED]">news:[EMAIL PROTECTED]... > Try using the broadcast command in your dialer map commands. > > ie. > > dialer map ip 10.36.19.6 broadcast > > Regards, > Aaron K. Dixon > > -Original Message- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of > Ryan Moffett > Sent: Saturday, July 29, 2000 8:51 PM > To: [EMAIL PROTECTED] > Subject: Re: OSPF Demand Circuit - About to go crazy! :-) > > > I apologize, the ip ospf network statements in my routers are correct: > > network 10.36.18.6 0.0.0.0 area 0 > network 10.36.19.6 0.0.0.0 area 0 > ! > > I attempted to write down the config from memory and my previous post was > erraneous. > > In any case, sh ip ospf int on both routers shows that OSPF is running on > both the Frame Relay and ISDN interfaces and on R1 the ISDN interface shows > that it is running as a demand circuit. The problem is that it will never > establish an adjacency over the frame-relay link, nor attempt to. If I > shut the Frame Relay interface down, the ISDN interface doesn't come up, and > even if I attempt to "nail-up" the ISDN connection so that it is always up, > adjacencies will not form. I debug ip ospf adjacency, and nothing happens. > Both routers can ping each other over the ISDN link, I can make RIP, IGRP, > EIGRP and BGP talk over the ISDN connection, however OSPF still fails... > > Ryan > > ""Aaron K. Dixon"" <[EMAIL PROTECTED]> wrote in message > [EMAIL PROTECTED]">news:[EMAIL PROTECTED]... > > It looks like you mistyped the ospf statements in router 2. Under the > ospf > > process you specify addresses that have the 2nd octet of .39 when the > > interfaces have a second octet of .36. A good way to verify that your > > interfaces coincide with your ospf configuration is to do a 'sh ip ospf > > int'. This will allow you to verify that the interfaces are configured > for > > opsf and then you can go into troubleshooting neighbor relationships. > > > > Regards, > > Aaron K. Dixon > > > > -Original Message- > > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of > > Ryan Moffett > > Sent: Saturday, July 29, 2000 8:06 PM > > To: [EMAIL PROTECTED] > > Subject: OSPF Demand Circuit - About to go crazy! :-) > > > > > > I am beating myself to death with the following: > > > > I am working through the following scenario in which R1 has a Frame Relay > > connection to R2 via Frame-Relay and ISDN. R1 is configured with ip ospf > > demand-circuit on the ISDN interface as well as OSPF on the Frame Relay > > interface. R1 forms an ajacency with R2 over the Frame Relay link, and > > they sucessfully exchange databases. R2 is configured the same as R1 > with > > the exception of the ip ospf demand-circuit, it does not have that > > configured.R1 does not show 2 entries in the show ip ospf neighbor > > output. R1 and R2 are not forming adjacencies over the OSPF > > demand-circuit.I can ping between R1 and R2's BRI interfaces to bring > up > > the ISDN link, and it works properly, however, if I shut the Frame Relay > > interface down, shouldn't the ISDN link come up as both links are in area > 0? > > > > R1 has the following relavent configuration: > > > > ! > > int s0.102 point-to-point > > encapsulation frame-relay > > ip address 10.36.18.5 255.255.255.252 > > frame-relay interface-dlci 102 > > ! > > int bri0 > > encapsulation ppp > > dialer map ip 10.36.19.5 > > ip ospf demand-circuit > > dialer-group 1 > > ! > > router ospf 100 > > network 10.36.18.5 0.0.0.0 area 0 > > network 10.36.19.5 0.0.0.0 area 0 > > ! > > dialer-list 1 protocol ip permit > > > > > > R2 has the following relavent configuration > > > > ! > > int S0.201 point-to-point > > encapsulation frame-relay > > ip address 10.36.18.6 255.255.255.252 > > frame-relay interface-dlci 201 > > ! > > int bri0 > > encapsulation ppp > > dialer map ip 10.36.19.6 > >
RE: OSPF Demand Circuit - About to go crazy! :-)
Try using the broadcast command in your dialer map commands. ie. dialer map ip 10.36.19.6 broadcast Regards, Aaron K. Dixon -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Ryan Moffett Sent: Saturday, July 29, 2000 8:51 PM To: [EMAIL PROTECTED] Subject: Re: OSPF Demand Circuit - About to go crazy! :-) I apologize, the ip ospf network statements in my routers are correct: network 10.36.18.6 0.0.0.0 area 0 network 10.36.19.6 0.0.0.0 area 0 ! I attempted to write down the config from memory and my previous post was erraneous. In any case, sh ip ospf int on both routers shows that OSPF is running on both the Frame Relay and ISDN interfaces and on R1 the ISDN interface shows that it is running as a demand circuit. The problem is that it will never establish an adjacency over the frame-relay link, nor attempt to. If I shut the Frame Relay interface down, the ISDN interface doesn't come up, and even if I attempt to "nail-up" the ISDN connection so that it is always up, adjacencies will not form. I debug ip ospf adjacency, and nothing happens. Both routers can ping each other over the ISDN link, I can make RIP, IGRP, EIGRP and BGP talk over the ISDN connection, however OSPF still fails... Ryan ""Aaron K. Dixon"" <[EMAIL PROTECTED]> wrote in message [EMAIL PROTECTED]">news:[EMAIL PROTECTED]... > It looks like you mistyped the ospf statements in router 2. Under the ospf > process you specify addresses that have the 2nd octet of .39 when the > interfaces have a second octet of .36. A good way to verify that your > interfaces coincide with your ospf configuration is to do a 'sh ip ospf > int'. This will allow you to verify that the interfaces are configured for > opsf and then you can go into troubleshooting neighbor relationships. > > Regards, > Aaron K. Dixon > > -Original Message- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of > Ryan Moffett > Sent: Saturday, July 29, 2000 8:06 PM > To: [EMAIL PROTECTED] > Subject: OSPF Demand Circuit - About to go crazy! :-) > > > I am beating myself to death with the following: > > I am working through the following scenario in which R1 has a Frame Relay > connection to R2 via Frame-Relay and ISDN. R1 is configured with ip ospf > demand-circuit on the ISDN interface as well as OSPF on the Frame Relay > interface. R1 forms an ajacency with R2 over the Frame Relay link, and > they sucessfully exchange databases. R2 is configured the same as R1 with > the exception of the ip ospf demand-circuit, it does not have that > configured.R1 does not show 2 entries in the show ip ospf neighbor > output. R1 and R2 are not forming adjacencies over the OSPF > demand-circuit.I can ping between R1 and R2's BRI interfaces to bring up > the ISDN link, and it works properly, however, if I shut the Frame Relay > interface down, shouldn't the ISDN link come up as both links are in area 0? > > R1 has the following relavent configuration: > > ! > int s0.102 point-to-point > encapsulation frame-relay > ip address 10.36.18.5 255.255.255.252 > frame-relay interface-dlci 102 > ! > int bri0 > encapsulation ppp > dialer map ip 10.36.19.5 > ip ospf demand-circuit > dialer-group 1 > ! > router ospf 100 > network 10.36.18.5 0.0.0.0 area 0 > network 10.36.19.5 0.0.0.0 area 0 > ! > dialer-list 1 protocol ip permit > > > R2 has the following relavent configuration > > ! > int S0.201 point-to-point > encapsulation frame-relay > ip address 10.36.18.6 255.255.255.252 > frame-relay interface-dlci 201 > ! > int bri0 > encapsulation ppp > dialer map ip 10.36.19.6 > ip ospf demand-circuit > dialer-group 1 > ! > router ospf 100 > network 10.39.18.6 0.0.0.0 area 0 > network 10.39.19.6 0.0.0.0 area 0 > ! > dialer-list 1 protocol ip permit > > Thanks, > Ryan Moffett > > > ___ > UPDATED Posting Guidelines: http://www.groupstudy.com/list/guide.html > FAQ, list archives, and subscription info: http://www.groupstudy.com > Report misconduct and Nondisclosure violations to [EMAIL PROTECTED] > > ___ > UPDATED Posting Guidelines: http://www.groupstudy.com/list/guide.html > FAQ, list archives, and subscription info: http://www.groupstudy.com > Report misconduct and Nondisclosure violations to [EMAIL PROTECTED] > --- ___ UPDATED Posting Guidelines: http://www.groupstudy.com/list/guide.html FAQ, list archives, and subscription info: http://www.groupstudy.com Report misconduct and Nondisclosure violations to [EMAIL PROTECTED] ___ UPDATED Posting Guidelines: http://www.groupstudy.com/list/guide.html FAQ, list archives, and subscription info: http://www.groupstudy.com Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
Re: OSPF Demand Circuit - About to go crazy! :-)
I apologize, the ip ospf network statements in my routers are correct: network 10.36.18.6 0.0.0.0 area 0 network 10.36.19.6 0.0.0.0 area 0 ! I attempted to write down the config from memory and my previous post was erraneous. In any case, sh ip ospf int on both routers shows that OSPF is running on both the Frame Relay and ISDN interfaces and on R1 the ISDN interface shows that it is running as a demand circuit. The problem is that it will never establish an adjacency over the frame-relay link, nor attempt to. If I shut the Frame Relay interface down, the ISDN interface doesn't come up, and even if I attempt to "nail-up" the ISDN connection so that it is always up, adjacencies will not form. I debug ip ospf adjacency, and nothing happens. Both routers can ping each other over the ISDN link, I can make RIP, IGRP, EIGRP and BGP talk over the ISDN connection, however OSPF still fails... Ryan ""Aaron K. Dixon"" <[EMAIL PROTECTED]> wrote in message [EMAIL PROTECTED]">news:[EMAIL PROTECTED]... > It looks like you mistyped the ospf statements in router 2. Under the ospf > process you specify addresses that have the 2nd octet of .39 when the > interfaces have a second octet of .36. A good way to verify that your > interfaces coincide with your ospf configuration is to do a 'sh ip ospf > int'. This will allow you to verify that the interfaces are configured for > opsf and then you can go into troubleshooting neighbor relationships. > > Regards, > Aaron K. Dixon > > -Original Message- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of > Ryan Moffett > Sent: Saturday, July 29, 2000 8:06 PM > To: [EMAIL PROTECTED] > Subject: OSPF Demand Circuit - About to go crazy! :-) > > > I am beating myself to death with the following: > > I am working through the following scenario in which R1 has a Frame Relay > connection to R2 via Frame-Relay and ISDN. R1 is configured with ip ospf > demand-circuit on the ISDN interface as well as OSPF on the Frame Relay > interface. R1 forms an ajacency with R2 over the Frame Relay link, and > they sucessfully exchange databases. R2 is configured the same as R1 with > the exception of the ip ospf demand-circuit, it does not have that > configured.R1 does not show 2 entries in the show ip ospf neighbor > output. R1 and R2 are not forming adjacencies over the OSPF > demand-circuit.I can ping between R1 and R2's BRI interfaces to bring up > the ISDN link, and it works properly, however, if I shut the Frame Relay > interface down, shouldn't the ISDN link come up as both links are in area 0? > > R1 has the following relavent configuration: > > ! > int s0.102 point-to-point > encapsulation frame-relay > ip address 10.36.18.5 255.255.255.252 > frame-relay interface-dlci 102 > ! > int bri0 > encapsulation ppp > dialer map ip 10.36.19.5 > ip ospf demand-circuit > dialer-group 1 > ! > router ospf 100 > network 10.36.18.5 0.0.0.0 area 0 > network 10.36.19.5 0.0.0.0 area 0 > ! > dialer-list 1 protocol ip permit > > > R2 has the following relavent configuration > > ! > int S0.201 point-to-point > encapsulation frame-relay > ip address 10.36.18.6 255.255.255.252 > frame-relay interface-dlci 201 > ! > int bri0 > encapsulation ppp > dialer map ip 10.36.19.6 > ip ospf demand-circuit > dialer-group 1 > ! > router ospf 100 > network 10.39.18.6 0.0.0.0 area 0 > network 10.39.19.6 0.0.0.0 area 0 > ! > dialer-list 1 protocol ip permit > > Thanks, > Ryan Moffett > > > ___ > UPDATED Posting Guidelines: http://www.groupstudy.com/list/guide.html > FAQ, list archives, and subscription info: http://www.groupstudy.com > Report misconduct and Nondisclosure violations to [EMAIL PROTECTED] > > ___ > UPDATED Posting Guidelines: http://www.groupstudy.com/list/guide.html > FAQ, list archives, and subscription info: http://www.groupstudy.com > Report misconduct and Nondisclosure violations to [EMAIL PROTECTED] > --- ___ UPDATED Posting Guidelines: http://www.groupstudy.com/list/guide.html FAQ, list archives, and subscription info: http://www.groupstudy.com Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
RE: OSPF Demand Circuit - About to go crazy! :-)
It looks like you mistyped the ospf statements in router 2. Under the ospf process you specify addresses that have the 2nd octet of .39 when the interfaces have a second octet of .36. A good way to verify that your interfaces coincide with your ospf configuration is to do a 'sh ip ospf int'. This will allow you to verify that the interfaces are configured for opsf and then you can go into troubleshooting neighbor relationships. Regards, Aaron K. Dixon -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Ryan Moffett Sent: Saturday, July 29, 2000 8:06 PM To: [EMAIL PROTECTED] Subject: OSPF Demand Circuit - About to go crazy! :-) I am beating myself to death with the following: I am working through the following scenario in which R1 has a Frame Relay connection to R2 via Frame-Relay and ISDN. R1 is configured with ip ospf demand-circuit on the ISDN interface as well as OSPF on the Frame Relay interface. R1 forms an ajacency with R2 over the Frame Relay link, and they sucessfully exchange databases. R2 is configured the same as R1 with the exception of the ip ospf demand-circuit, it does not have that configured.R1 does not show 2 entries in the show ip ospf neighbor output. R1 and R2 are not forming adjacencies over the OSPF demand-circuit.I can ping between R1 and R2's BRI interfaces to bring up the ISDN link, and it works properly, however, if I shut the Frame Relay interface down, shouldn't the ISDN link come up as both links are in area 0? R1 has the following relavent configuration: ! int s0.102 point-to-point encapsulation frame-relay ip address 10.36.18.5 255.255.255.252 frame-relay interface-dlci 102 ! int bri0 encapsulation ppp dialer map ip 10.36.19.5 ip ospf demand-circuit dialer-group 1 ! router ospf 100 network 10.36.18.5 0.0.0.0 area 0 network 10.36.19.5 0.0.0.0 area 0 ! dialer-list 1 protocol ip permit R2 has the following relavent configuration ! int S0.201 point-to-point encapsulation frame-relay ip address 10.36.18.6 255.255.255.252 frame-relay interface-dlci 201 ! int bri0 encapsulation ppp dialer map ip 10.36.19.6 ip ospf demand-circuit dialer-group 1 ! router ospf 100 network 10.39.18.6 0.0.0.0 area 0 network 10.39.19.6 0.0.0.0 area 0 ! dialer-list 1 protocol ip permit Thanks, Ryan Moffett ___ UPDATED Posting Guidelines: http://www.groupstudy.com/list/guide.html FAQ, list archives, and subscription info: http://www.groupstudy.com Report misconduct and Nondisclosure violations to [EMAIL PROTECTED] ___ UPDATED Posting Guidelines: http://www.groupstudy.com/list/guide.html FAQ, list archives, and subscription info: http://www.groupstudy.com Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
OSPF Demand Circuit - About to go crazy! :-)
I am beating myself to death with the following: I am working through the following scenario in which R1 has a Frame Relay connection to R2 via Frame-Relay and ISDN. R1 is configured with ip ospf demand-circuit on the ISDN interface as well as OSPF on the Frame Relay interface. R1 forms an ajacency with R2 over the Frame Relay link, and they sucessfully exchange databases. R2 is configured the same as R1 with the exception of the ip ospf demand-circuit, it does not have that configured.R1 does not show 2 entries in the show ip ospf neighbor output. R1 and R2 are not forming adjacencies over the OSPF demand-circuit.I can ping between R1 and R2's BRI interfaces to bring up the ISDN link, and it works properly, however, if I shut the Frame Relay interface down, shouldn't the ISDN link come up as both links are in area 0? R1 has the following relavent configuration: ! int s0.102 point-to-point encapsulation frame-relay ip address 10.36.18.5 255.255.255.252 frame-relay interface-dlci 102 ! int bri0 encapsulation ppp dialer map ip 10.36.19.5 2222 ip ospf demand-circuit dialer-group 1 ! router ospf 100 network 10.36.18.5 0.0.0.0 area 0 network 10.36.19.5 0.0.0.0 area 0 ! dialer-list 1 protocol ip permit R2 has the following relavent configuration ! int S0.201 point-to-point encapsulation frame-relay ip address 10.36.18.6 255.255.255.252 frame-relay interface-dlci 201 ! int bri0 encapsulation ppp dialer map ip 10.36.19.6 1111 ip ospf demand-circuit dialer-group 1 ! router ospf 100 network 10.39.18.6 0.0.0.0 area 0 network 10.39.19.6 0.0.0.0 area 0 ! dialer-list 1 protocol ip permit Thanks, Ryan Moffett ___ UPDATED Posting Guidelines: http://www.groupstudy.com/list/guide.html FAQ, list archives, and subscription info: http://www.groupstudy.com Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
