There's a good clue in that output:

"Adv Router is not-reachable"

Seeing that it's a frame relay interface you might have network type
mismatch or misconfigured pvcs:

http://www.cisco.com/en/US/tech/tk365/technologies_tech_note09186a008009481a.shtml



On Sun, Jan 9, 2011 at 4:50 PM, Paul Kim <[email protected]> wrote:

> Hi Jay,
>
>  The output at r3, the adjacent router seems OK as follows.
>
> r3#sh ip ospf database router 1.1.1.1
>
>            OSPF Router with ID (3.3.3.3) (Process ID 1)
>
>                Router Link States (Area 0)
>
>   Adv Router is not-reachable
>  LS age: 48
>  Options: (No TOS-capability, DC)
>  LS Type: Router Links
>  Link State ID: 1.1.1.1
>  Advertising Router: 1.1.1.1
>  LS Seq Number: 8000000D
>  Checksum: 0xC78D
>  Length: 72
>  Number of Links: 4
>
>    Link connected to: a Stub Network
>     (Link ID) Network/subnet number: 43.34.32.0
>     (Link Data) Network Mask: 255.255.255.0
>      Number of TOS metrics: 0
>       TOS 0 Metrics: 1
>
>    Link connected to: a Stub Network
>     (Link ID) Network/subnet number: 66.66.66.0
>     (Link Data) Network Mask: 255.255.255.0
>      Number of TOS metrics: 0
>       TOS 0 Metrics: 1
>
>    Link connected to: a Stub Network
>     (Link ID) Network/subnet number: 55.55.55.0
>     (Link Data) Network Mask: 255.255.255.0
>      Number of TOS metrics: 0
>       TOS 0 Metrics: 1
>
>    Link connected to: a Transit Network
>     (Link ID) Designated Router address: 172.16.0.3
>     (Link Data) Router Interface address: 172.16.0.1
>      Number of TOS metrics: 0
>       TOS 0 Metrics: 64
>
>
> r3#sh ip route 66.66.66.0
> % Network not in table
> r3#sh ip route 55.55.55.0
> % Network not in table
> r3#sh ip route 43.34.32.0
> % Network not in table
> r3#sh ip ospf nei
>
> Neighbor ID     Pri   State           Dead Time   Address         Interface
> 1.1.1.1           0   FULL/  -        00:00:32    172.16.0.1
>  Serial0/1/0.26
>
> It seems that somehow r3 doesn't take the r1's LSA into its RIB.
>
> Thanks,
> Paul
> On Sun, Jan 9, 2011 at 1:30 PM, Jay Taylor <[email protected]> wrote:
> > What's the output of a 'show ip ospf database router 1.1.1.1' on R1?
> >
> >
> > On Sun, Jan 9, 2011 at 2:48 PM, Paul Kim <[email protected]> wrote:
> >>
> >> Hi experts,
> >>
> >>  Probably I have  miss-understand some piece of OSPF.
> >> Can you please let me know why  r1 doesn't adverrise networks defined
> >> under ospf statment.
> >>
> >> r1#sh run | s router ospf
> >> router ospf 1
> >>  router-id 1.1.1.1
> >>  log-adjacency-changes
> >>  network 43.34.32.1 0.0.0.0 area 0
> >>  network 55.55.55.4 0.0.0.0 area 0
> >>  network 66.66.66.1 0.0.0.0 area 0
> >>  network 172.16.0.1 0.0.0.0 area 0
> >>
> >> r1#sh ip int brief | ex una
> >> Interface                  IP-Address      OK? Method Status
> >>     Protocol
> >> FastEthernet0/0            3.3.3.1         YES NVRAM  up
> >>     up
> >> FastEthernet0/1            55.55.55.4      YES NVRAM  up
> >>     up
> >> Serial0/3/0                172.16.0.1      YES NVRAM  up
> >>     up
> >> Vlan10                     66.66.66.1      YES manual up
> >>     up
> >> Loopback87                 43.34.32.1      YES NVRAM  up
> >>     up
> >>
> >> r1#sh ip ospf nei
> >>
> >> Neighbor ID     Pri   State           Dead Time   Address
> >> Interface
> >> 3.3.3.3           1   FULL/DR         00:00:30    172.16.0.3
> >>  Serial0/3/0
> >>
> >> r1#sh ip ospf database self
> >>
> >>            OSPF Router with ID (1.1.1.1) (Process ID 1)
> >>
> >>                Router Link States (Area 0)
> >>
> >> Link ID         ADV Router      Age         Seq#       Checksum Link
> count
> >> 1.1.1.1         1.1.1.1         574         0x80000009 0x00CF89 4
> >> r1#
> >>
> >>
> >> Thanks,
> >> Paul
> >> _______________________________________________
> >> For more information regarding industry leading CCIE Lab training,
> please
> >> visit www.ipexpert.com
> >
> >
>
_______________________________________________
For more information regarding industry leading CCIE Lab training, please visit 
www.ipexpert.com

Reply via email to