From: Patrick McKinnis (pmckinni@xxxxxxxxx)
Date: Wed Mar 01 2000 - 16:21:31 GMT-3
Rob -
I have been using these guidelines from the Docs CD with success for IP
OSPF Demand-Circuits:
If the router is part of a point-to-point topology, then only ONE END
of the demand circuit must be configured with this command. However, all
routers must have this FEATURE loaded.
If the router is part of a point-to-multipoint topology, only the
MULTIPOINT END must be configured with this command.
He'll bring up the link initially to exchange hellos and LSA's, but he
should then supress that traffic. You should see this within the OSPF
database (notice the "Do Not Age" information:
r1#sh ip ospf database
OSPF Router with ID (172.16.200.1) (Process ID 100)
Router Link States (Area 0)
Link ID ADV Router Age Seq# Checksum Link count
172.16.25.5 172.16.25.5 1354 0x8000006C 0xF7B5 2
172.16.100.2 172.16.100.2 1457 0x8000007A 0x9235 3
172.16.100.3 172.16.100.3 20 0x80000081 0xEDDA 3
172.16.200.1 172.16.200.1 1026 0x80000097 0xA74C 4
172.16.200.2 172.16.200.2 5 (DNA) 0x80000014 0xD5E8 1
Net Link States (Area 0)
Link ID ADV Router Age Seq# Checksum
172.16.100.1 172.16.200.1 1483 0x8000006F 0x84CC
Summary Net Link States (Area 0)
Link ID ADV Router Age Seq# Checksum
172.16.200.0 172.16.200.1 400 0x8000005E 0x157E
172.16.200.0 172.16.200.2 341 (DNA) 0x80000001 0xC926
180.180.180.180 172.16.200.2 341 (DNA) 0x80000001 0xFEE2
Summary ASB Link States (Area 0)
Link ID ADV Router Age Seq# Checksum
172.16.200.2 172.16.200.1 426 0x80000056 0x395
Router Link States (Area 10)
Link ID ADV Router Age Seq# Checksum Link count
172.16.200.1 172.16.200.1 427 0x80000077 0x6923 2
172.16.200.2 172.16.200.2 105 0x80000069 0x7F17 2
Summary Net Link States (Area 10)
Link ID ADV Router Age Seq# Checksum
13.0.0.0 172.16.200.1 426 0x80000004 0xFE87
13.0.0.0 172.16.200.2 1043 0x80000003 0x7DC8
172.16.25.0 172.16.200.1 427 0x80000057 0x32D7
172.16.25.0 172.16.200.2 105 0x8000004D 0xC210
172.16.100.0 172.16.200.1 427 0x80000059 0x6F8D
172.16.100.0 172.16.200.2 105 0x8000004D 0x4C3
180.180.180.180 172.16.200.1 427 0x80000056 0xDC70
180.180.180.180 172.16.200.2 106 0x8000004D 0x662F
Summary ASB Link States (Area 10)
Link ID ADV Router Age Seq# Checksum
172.16.25.5 172.16.200.1 436 0x80000057 0xF112
172.16.25.5 172.16.200.2 115 0x8000004D 0x824A
172.16.200.2 172.16.200.1 436 0x80000056 0x395
Type-5 AS External Link States
Link ID ADV Router Age Seq# Checksum Tag
144.144.144.0 172.16.200.2 1891 0x80000054 0x4D47 0
Hope this helps.
Patrick
> -----Original Message-----
> From: nobody@groupstudy.com [mailto:nobody@groupstudy.com]On Behalf Of
> Rob Barton
> Sent: Wednesday, March 01, 2000 10:43 AM
> To: ccielab@groupstudy.com
> Subject: IP OSPF Demand Circuit
>
>
> Hi all, I am new to this group and am already impressed with the high
> level of discussion that has been going on. I am scheduled to write the
> exam in San Jose on June 29,30
>
> I have an OSPF config problem maybe someone can help me with. OSPF is
> configured across my BRI line (not as a backup interface, but just with
> a higher cost than the serial interface). I have used the ip ospf
> demand-circuit command at both sides of the ISDN line, but the OSPF
> multicast traffic is still bringing up the line constantly. Any ideas
> of why this would be?
>
>
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 08:23:03 GMT-3