RE: stupid question about ip ospf network point-to-multipoint

From: Michael Snyder (msnyder@revolutioncomputer.com)
Date: Sun Feb 22 2004 - 00:17:18 GMT-3


I always do frame-relay non-broadcast multi-point interfaces when given
a choice. I'm behind the curve with this stuff.

Ok, new update. My asbr router's have the /27 routes and don't have the
/32, but my plain abr router's have the /32 and not the /27. It's
136.10.100.0 I'm trying to figure out.

I don't get it. Can someone point me to a url? Why would my asbr
behave in a manner that I would prefer, and my abr only shows the host
routes.

I'm very perplexed.

---------------------------

Here's a plain abr with area 2,3 and 0.

O E1 136.10.78.0/25 [110/1001] via 136.10.56.7, 00:30:08, Vlan904
O 136.10.100.6/32 [110/121] via 136.10.56.5, 00:30:08, Vlan904
O 136.10.100.5/32 [110/1] via 136.10.56.5, 00:30:08, Vlan904
O 136.10.100.2/32 [110/65] via 136.10.56.5, 00:30:08, Vlan904
     205.1.1.0/27 is subnetted, 3 subnets

     
3550#show ip ospf data router

       OSPF Router with ID (136.10.10.10) (Process ID 36)

                Router Link States (Area 0)

  Routing Bit Set on this LSA
  LS age: 21 (DoNotAge)
  Options: (No TOS-capability, DC)
  LS Type: Router Links
  Link State ID: 136.10.2.2
  Advertising Router: 136.10.2.2
  LS Seq Number: 80000011
  Checksum: 0x4E74
  Length: 84
  AS Boundary Router
   Number of Links: 5

    Link connected to: another Router (point-to-point)
     (Link ID) Neighboring Router ID: 136.10.6.6
     (Link Data) Router Interface address: 136.10.100.2
      Number of TOS metrics: 0
       TOS 0 Metrics: 56

    Link connected to: another Router (point-to-point)
     (Link ID) Neighboring Router ID: 136.10.5.5
     (Link Data) Router Interface address: 136.10.100.2
      Number of TOS metrics: 0
       TOS 0 Metrics: 56

    Link connected to: a Stub Network
     (Link ID) Network/subnet number: 136.10.100.2
     (Link Data) Network Mask: 255.255.255.255
      Number of TOS metrics: 0
       TOS 0 Metrics: 0

    Link connected to: a Stub Network
     (Link ID) Network/subnet number: 136.10.25.0
     (Link Data) Network Mask: 255.255.255.252
      Number of TOS metrics: 0
       TOS 0 Metrics: 1562

    Link connected to: a Stub Network
     (Link ID) Network/subnet number: 136.10.2.0
     (Link Data) Network Mask: 255.255.255.0
      Number of TOS metrics: 0
       TOS 0 Metrics: 1

  Routing Bit Set on this LSA
  LS age: 5 (DoNotAge)
  Options: (No TOS-capability, DC)
  LS Type: Router Links
  Link State ID: 136.10.5.5
  Advertising Router: 136.10.5.5
  LS Seq Number: 80000070
  Checksum: 0xA9EF
  Length: 84
  Area Border Router
   Number of Links: 5

    Link connected to: a Virtual Link
     (Link ID) Neighboring Router ID: 136.10.10.10
     (Link Data) Router Interface address: 136.10.56.5
      Number of TOS metrics: 0
       TOS 0 Metrics: 10

    Link connected to: a Stub Network
     (Link ID) Network/subnet number: 136.10.5.0
     (Link Data) Network Mask: 255.255.255.0
      Number of TOS metrics: 0
       TOS 0 Metrics: 1

    Link connected to: another Router (point-to-point)
     (Link ID) Neighboring Router ID: 136.10.2.2
     (Link Data) Router Interface address: 136.10.100.5
      Number of TOS metrics: 0
       TOS 0 Metrics: 64

    Link connected to: a Stub Network
     (Link ID) Network/subnet number: 136.10.100.5
     (Link Data) Network Mask: 255.255.255.255
      Number of TOS metrics: 0
       TOS 0 Metrics: 0

    Link connected to: a Stub Network
     (Link ID) Network/subnet number: 136.10.25.0
     (Link Data) Network Mask: 255.255.255.252
      Number of TOS metrics: 0
       TOS 0 Metrics: 1562

  Routing Bit Set on this LSA
  LS age: 23 (DoNotAge)
  Options: (No TOS-capability, DC)
  LS Type: Router Links
  Link State ID: 136.10.6.6
  Advertising Router: 136.10.6.6
  LS Seq Number: 80000065
  Checksum: 0xE81D
  Length: 60
  Area Border Router
  AS Boundary Router
   Number of Links: 3

    Link connected to: a Stub Network
     (Link ID) Network/subnet number: 136.10.6.0
     (Link Data) Network Mask: 255.255.255.0
      Number of TOS metrics: 0
       TOS 0 Metrics: 1

    Link connected to: another Router (point-to-point)
     (Link ID) Neighboring Router ID: 136.10.2.2
     (Link Data) Router Interface address: 136.10.100.6
      Number of TOS metrics: 0
       TOS 0 Metrics: 64

    Link connected to: a Stub Network
     (Link ID) Network/subnet number: 136.10.100.6
     (Link Data) Network Mask: 255.255.255.255
      Number of TOS metrics: 0
       TOS 0 Metrics: 0

  Options: (No TOS-capability, DC)
  LS Type: Router Links
  Link State ID: 136.10.10.10
  Advertising Router: 136.10.10.10
  LS Seq Number: 80000008
  Checksum: 0x9923
  Length: 48
  Area Border Router
   Number of Links: 2

    Link connected to: a Virtual Link
     (Link ID) Neighboring Router ID: 136.10.5.5
     (Link Data) Router Interface address: 136.10.56.10
      Number of TOS metrics: 0
       TOS 0 Metrics: 1

    Link connected to: a Stub Network
     (Link ID) Network/subnet number: 136.10.10.0
     (Link Data) Network Mask: 255.255.255.0
      Number of TOS metrics: 0
       TOS 0 Metrics: 1

                Router Link States (Area 2)

  LS age: 1083
  Options: (No TOS-capability, DC)
  LS Type: Router Links
  Link State ID: 136.10.10.10
  Advertising Router: 136.10.10.10
  LS Seq Number: 80000005
  Checksum: 0x7FCB
  Length: 60
  Area Border Router
   Number of Links: 3

    Link connected to: a Stub Network
     (Link ID) Network/subnet number: 205.1.1.64
     (Link Data) Network Mask: 255.255.255.224
      Number of TOS metrics: 0
       TOS 0 Metrics: 1

    Link connected to: a Stub Network
     (Link ID) Network/subnet number: 205.1.1.32
     (Link Data) Network Mask: 255.255.255.224
      Number of TOS metrics: 0
       TOS 0 Metrics: 1

    Link connected to: a Stub Network
     (Link ID) Network/subnet number: 205.1.1.0
     (Link Data) Network Mask: 255.255.255.224
      Number of TOS metrics: 0
       TOS 0 Metrics: 1

                Router Link States (Area 3)

  Routing Bit Set on this LSA
  LS age: 1993
  Options: (No TOS-capability, DC)
  LS Type: Router Links
  Link State ID: 136.10.5.5
  Advertising Router: 136.10.5.5
  LS Seq Number: 80000002
  Checksum: 0x2429
  Length: 36
  Area Border Router
   Number of Links: 1

    Link connected to: a Transit Network
     (Link ID) Designated Router address: 136.10.56.7
     (Link Data) Router Interface address: 136.10.56.5
      Number of TOS metrics: 0
       TOS 0 Metrics: 10

  Routing Bit Set on this LSA
  LS age: 55
  Options: (No TOS-capability, DC)
  LS Type: Router Links
  Link State ID: 136.10.6.6
  Advertising Router: 136.10.6.6
  LS Seq Number: 80000003
  Checksum: 0x1431
  Length: 36
  Area Border Router
  AS Boundary Router
   Number of Links: 1

    Link connected to: a Transit Network
     (Link ID) Designated Router address: 136.10.56.7
     (Link Data) Router Interface address: 136.10.56.6
      Number of TOS metrics: 0
       TOS 0 Metrics: 10

  Routing Bit Set on this LSA
  LS age: 1197
  Options: (No TOS-capability, DC)
  LS Type: Router Links
  Link State ID: 136.10.7.7
  Advertising Router: 136.10.7.7
  LS Seq Number: 80000015
  Checksum: 0xE49F
  Length: 48
  AS Boundary Router
   Number of Links: 2

    Link connected to: a Transit Network
     (Link ID) Designated Router address: 136.10.56.7
     (Link Data) Router Interface address: 136.10.56.7
      Number of TOS metrics: 0
       TOS 0 Metrics: 10

    Link connected to: a Stub Network
     (Link ID) Network/subnet number: 136.10.7.0
     (Link Data) Network Mask: 255.255.255.0
      Number of TOS metrics: 0
       TOS 0 Metrics: 1

  LS age: 1085
  Options: (No TOS-capability, DC)
  LS Type: Router Links
  Link State ID: 136.10.10.10
  Advertising Router: 136.10.10.10
  LS Seq Number: 80000006
  Checksum: 0x1524
  Length: 36
  Area Border Router
   Number of Links: 1

    Link connected to: a Transit Network
     (Link ID) Designated Router address: 136.10.56.7
     (Link Data) Router Interface address: 136.10.56.10
      Number of TOS metrics: 0
       TOS 0 Metrics: 1

3550#
---------------------------

Here's an ASBR with just area 3

E1 136.10.69.0/28 [110/1010] via 136.10.56.6, 00:34:19, Ethernet0
C 136.10.78.0/25 is directly connected, Serial0
O IA 136.10.100.0/27 [110/10] via 136.10.56.5, 00:34:19, Ethernet0
                        [110/10] via 136.10.56.6, 00:34:19, Ethernet0
O IA 205.1.1.0 [110/11] via 136.10.56.10, 00:34:14, Ethernet0
R 208.10.89.0/24 [120/2] via 136.10.78.8, 00:00:10, Serial0
O E1 100.10.14.0 [110/1074] via 136.10.56.5, 00:34:20, Ethernet0

R7#show ip ospf data router

            OSPF Router with ID (136.10.7.7) (Process ID 36)

                Router Link States (Area 3)

  Routing Bit Set on this LSA
  LS age: 224
  Options: (No TOS-capability, DC)
  LS Type: Router Links
  Link State ID: 136.10.5.5
  Advertising Router: 136.10.5.5
  LS Seq Number: 80000003
  Checksum: 0x222A
  Length: 36
  Area Border Router
  Number of Links: 1

    Link connected to: a Transit Network
     (Link ID) Designated Router address: 136.10.56.7
     (Link Data) Router Interface address: 136.10.56.5
      Number of TOS metrics: 0
       TOS 0 Metrics: 10

  Routing Bit Set on this LSA
  LS age: 329
  Options: (No TOS-capability, DC)
  LS Type: Router Links
  Link State ID: 136.10.6.6
  Advertising Router: 136.10.6.6
  LS Seq Number: 80000003
  Checksum: 0x1431
  Length: 36
  Area Border Router
  AS Boundary Router
  Number of Links: 1

    Link connected to: a Transit Network
     (Link ID) Designated Router address: 136.10.56.7
     (Link Data) Router Interface address: 136.10.56.6
      Number of TOS metrics: 0
       TOS 0 Metrics: 10

  LS age: 1471
  Options: (No TOS-capability, DC)
  LS Type: Router Links
  Link State ID: 136.10.7.7
  Advertising Router: 136.10.7.7
  LS Seq Number: 80000015
  Checksum: 0xE49F
  Length: 48
  AS Boundary Router
  Number of Links: 2

    Link connected to: a Transit Network
     (Link ID) Designated Router address: 136.10.56.7
     (Link Data) Router Interface address: 136.10.56.7
      Number of TOS metrics: 0
       TOS 0 Metrics: 10

    Link connected to: a Stub Network
     (Link ID) Network/subnet number: 136.10.7.0
     (Link Data) Network Mask: 255.255.255.0
      Number of TOS metrics: 0
       TOS 0 Metrics: 1

  Routing Bit Set on this LSA
  LS age: 1360
  Options: (No TOS-capability, DC)
  LS Type: Router Links
  Link State ID: 136.10.10.10
  Advertising Router: 136.10.10.10
  LS Seq Number: 80000006
  Checksum: 0x1524
  Length: 36
  Area Border Router
  Number of Links: 1

    Link connected to: a Transit Network
     (Link ID) Designated Router address: 136.10.56.7
     (Link Data) Router Interface address: 136.10.56.10
      Number of TOS metrics: 0
       TOS 0 Metrics: 1

R7#

-----Original Message-----
From: Pete Yeargin (pyeargin) [mailto:pyeargin@cisco.com]
Sent: Saturday, February 21, 2004 7:38 PM
To: 'Michael Snyder'; ccielab@groupstudy.com
Cc: 'Bob Sinclair'
Subject: RE: stupid question about ip ospf network point-to-multipoint
non-broadcast

Michael,
        Do you have any other IP addresses on that common subnet other
than
the three p2p interfaces? I'm not sure I see the requirement for the
full
/27 subnet to be advertised to the other neighbors as long as the /32's
are
advertised for each of the 100.0/27 routers.

Pete

-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
Michael Snyder
Sent: Saturday, February 21, 2004 7:26 PM
To: ccielab@groupstudy.com
Cc: 'Bob Sinclair'
Subject: RE: stupid question about ip ospf network point-to-multipoint
non-broadcast

That puts me in the weird situation of having to put an external lsa in
for
the common network of my ospf backbone. Or I could try to summarize the
/32
routes at the each distribution point.

I can make either one work, but it's really an odd thing to do.

Thanks Bob

-----Original Message-----
From: Bob Sinclair [mailto:bsin@cox.net]
Sent: Saturday, February 21, 2004 6:10 PM
To: Michael Snyder; ccielab@groupstudy.com
Subject: Re: stupid question about ip ospf network point-to-multipoint
non-broadcast

Michael,

Since the point-to-multipoint network type does not treat the
frame-relay
network as mult-access, it does not generate a network LSA for it.
Instead,
you will see the network represented in the router LSAs as a collection
of
point-to-point networks in their respective router LSAs.

Try the command:

sh ip ospf database router

and you should see this. The command:

sh ip ospf database

lists LSAs, not networks, per se.

HTH,

Bob Sinclair
CCIE #10427, CISSP, MCSE
www.netmasterclass.net



This archive was generated by hypermail 2.1.4 : Fri Mar 05 2004 - 07:13:54 GMT-3