RE: [nsp] OSPF problems

From: Erik L. Montemer (montemer@more.net)
Date: Wed Jun 28 2000 - 20:04:15 EDT


 If you do a show ip ospf stat it will show you what LSAs are being flooded,
and how many
times SPF has run

--erik

-----Original Message-----
From: Martin, Christian
To: 'srg@2alpha.net'; cisco-nsp@puck.nether.net
Sent: 6/28/00 9:44 AM
Subject: RE: [nsp] OSPF problems

Is the forward address known to OSPF internally (as either an O, IA, or
E1/2
route)? Note that the routing bit is not set on this LSA, so it is
likely
that OSPF does not have a directed path on the SPT to get there.

chris

-----Original Message-----
From: srg@2alpha.net [mailto:srg@2alpha.net]
Sent: Wednesday, June 28, 2000 10:29 AM
To: cisco-nsp@puck.nether.net
Subject: [nsp] OSPF problems

I'm having no luck understanding why some OSPF routes make it into
the routing table and some don't. Here are two routes, both of which
are being generated by static route commands on another router. (ie -
they are at the other end of a frame relay or ISDN link, respectively.)
The first one (209.189.209.0/26) shows up in this router's route table
as an ospf type 2 external route. The other one doesn't. The
only difference I can see is the metric. The only other difference
that I know of is that the first one is advertised by another Cisco
router, and the second is advertised by a Portmaster 2ei. Both routes
show up in the OSPF database of all routers in the area. (We're small -
I use only area 0 for everything.)

Can anyone help me figure out why they are treated differently?

thanks,

Spencer

Output from "show ip ospf database external" on a Cisco 2621 (sea1):

(this one shows up in the routing table. It's being generated by
  ip route 209.100.203.240 255.255.255.240 209.100.192.142
 on another Cisco 2621 (sea2).)

  Routing Bit Set on this LSA
  LS age: 1843
  Options: (No TOS-capability, DC)
  LS Type: AS External Link
  Link State ID: 209.100.203.240 (External Network Number )
  Advertising Router: 209.189.223.242
  LS Seq Number: 8000007D
  Checksum: 0xEDEF
  Length: 36
  Network Mask: /28
        Metric Type: 2 (Larger than any link state path)
        TOS: 0
        Metric: 20
        Forward Address: 0.0.0.0
        External Route Tag: 0

(this one doesn't show up in the routing table. It's being generated
 by a RADIUS "Framed-Route" entry, but I get the same results when I
 put in a static route. The route shows up in the routing table
 of other portmasters, but not any of the ciscos.)

  LS age: 533
  Options: (No TOS-capability, No DC)
  LS Type: AS External Link
  Link State ID: 209.189.209.128 (External Network Number )
  Advertising Router: 209.189.192.252
  LS Seq Number: 8000000F
  Checksum: 0x95E1
  Length: 36
  Network Mask: /26
        Metric Type: 2 (Larger than any link state path)
        TOS: 0
        Metric: 2
        Forward Address: 209.189.192.11
        External Route Tag: 0



This archive was generated by hypermail 2b29 : Sun Aug 04 2002 - 04:12:13 EDT