[Xorp-users] OSPF Areas and Linux Route table
Sukrit Dasgupta
sd88 at drexel.edu
Mon Mar 3 10:47:00 PST 2008
Hi Atanu,
Just wanted to update you that the issue got resolved. I was trying
to do SNMP based automated configurations and for some reason, the
Cisco routers werent liking the order in which OSPF configurations
were taking place.
Thanks for your time!
Sukrit
Begin forwarded message:
> From: Sukrit Dasgupta <sd88 at drexel.edu>
> Date: March 1, 2008 10:13:02 PM EST
> To: atanu at icsi.berkeley.edu
> Subject: Re: [Xorp-users] OSPF Areas and Linux Route table
>
> Hi Atanu,
>
> Here are the show ospf database output:
>
> ----------------------------------------------------------------------
> -------- XORP/Linux/Area1/RouterID:12.0.11.2
>
> show ospf4 database
> OSPF link state database, Area 0.0.0.1
> Type ID Adv Rtr Seq Age Opt
> Cksum Len
> Router *12.0.11.3 12.0.11.3 0x80000002 86 0x2
> 0xdf0a 36
> Network *12.0.11.3 12.0.11.3 0x80000001 86 0x2
> 0xe9b1 32
> Router 192.168.0.7 192.168.0.7 0x80000002 86 0x22
> 0x64b0 36
>
>
> ----------------------------------------------------------------------
> ---------Cisco7200/Area0/RouterID:192.168.0.7
>
>
> show ip ospf database
>
> OSPF Router with ID (192.168.0.7) (Process ID 12)
>
> Router Link States (Area 1)
>
> Link ID ADV Router Age Seq# Checksum
> Link count
> 12.0.11.3 12.0.11.3 305 0x80000002 0xDF0A 1
> 192.168.0.7 192.168.0.7 304 0x80000002 0x64B0 1
>
> Net Link States (Area 1)
>
> Link ID ADV Router Age Seq# Checksum
> 12.0.11.3 12.0.11.3 305 0x80000001 0xE9B1
>
> OSPF Router with ID (192.168.1.7) (Process ID 14)
>
> Router Link States (Area 0)
>
> Link ID ADV Router Age Seq# Checksum
> Link count
> 192.168.0.1 192.168.0.1 309 0x800006CD 0x33C 4
> 192.168.0.2 192.168.0.2 157 0x800006D1 0xE0C 2
> 192.168.0.3 192.168.0.3 2172 0x800006C8 0xAF82 2
> 192.168.0.4 192.168.0.4 1787 0x800006CB 0x282C 1
> 192.168.1.7 192.168.1.7 146 0x80000006 0xF784 2
> 192.168.1.8 192.168.1.8 270 0x80000002 0x95F8 1
> 192.168.1.10 192.168.1.10 270 0x80000002 0x98AE 1
>
> Net Link States (Area 0)
>
> Link ID ADV Router Age Seq# Checksum
> 14.0.13.111 192.168.0.1 537 0x800006C5 0x4063
> 14.0.23.115 192.168.0.3 383 0x8000013E 0xC15D
> 14.0.24.115 192.168.0.4 1855 0x8000013D 0xBC60
> 14.1.78.2 192.168.1.8 339 0x80000001 0xABD8
> 14.1.107.2 192.168.1.10 338 0x80000001 0x73EF
>
>
>
> --------------------------------------------- Cisco7200/Area0/
> RouterID:192.168.0.10
>
>
> show ip ospf database
>
> OSPF Router with ID (192.168.0.10) (Process ID 16)
>
> Router Link States (Area 2)
>
> Link ID ADV Router Age Seq# Checksum
> Link count
> 16.0.43.2 16.0.43.2 791 0x8000002F 0xEA83 1
> 192.168.0.10 192.168.0.10 222 0x80000003 0x30D4 1
>
> Net Link States (Area 2)
>
> Link ID ADV Router Age Seq# Checksum
> 16.0.43.2 16.0.43.2 228 0x80000001 0x9B95
>
> OSPF Router with ID (192.168.1.10) (Process ID 14)
>
> Router Link States (Area 0)
>
> Link ID ADV Router Age Seq# Checksum
> Link count
> 192.168.0.1 192.168.0.1 268 0x800006CD 0x33C 4
> 192.168.0.2 192.168.0.2 115 0x800006D1 0xE0C 2
> 192.168.0.3 192.168.0.3 2131 0x800006C8 0xAF82 2
> 192.168.0.4 192.168.0.4 1746 0x800006CB 0x282C 1
> 192.168.1.7 192.168.1.7 104 0x80000006 0xF784 2
> 192.168.1.8 192.168.1.8 229 0x80000002 0x95F8 1
> 192.168.1.10 192.168.1.10 227 0x80000002 0x98AE 1
>
> Net Link States (Area 0)
>
> Link ID ADV Router Age Seq# Checksum
> 14.0.13.111 192.168.0.1 496 0x800006C5 0x4063
> 14.0.23.115 192.168.0.3 342 0x8000013E 0xC15D
> 14.0.24.115 192.168.0.4 1769 0x8000013D 0xBC60
> 14.1.78.2 192.168.1.8 253 0x80000001 0xABD8
> 14.1.107.2 192.168.1.10 251 0x80000001 0x73EF
>
>
> -------------------------------------------------------------XORP/
> Linux/Area1/RouterID:16.0.43.2
>
>
> show ospf4 database
> OSPF link state database, Area 0.0.0.2
> Type ID Adv Rtr Seq Age Opt
> Cksum Len
> Router *16.0.43.2 16.0.43.2 0x80000030 492 0x2
> 0xeb43 36
> Network *16.0.43.2 16.0.43.2 0x80000001 492 0x2
> 0x9b95 32
> Router 192.168.0.10 192.168.0.10 0x80000002 493 0x22
> 0x2338 36
>
>
>
> Thanks,
> Sukrit
>
>
>
>
> On Mar 1, 2008, at 2:19 PM, Atanu Ghosh wrote:
>
>> Hi,
>>
>> The next step is the output of "show ospf4 database" so we can see
>> what
>> is actually in the database.
>>
>> Atanu.
>>
>>>>>>> "Sukrit" == Sukrit Dasgupta <sd88 at drexel.edu> writes:
>>
>> Sukrit> Hi Atanu,
>> Sukrit> Here are the neighbor tables, the adjacencies are
>> correctly formed as
>> Sukrit> follows:
>>
>> Sukrit> On XORP/Linux 12.0.11.3, show ospf4 neighbor shows:
>> Sukrit> Address Interface State ID
>> Sukrit> Pri Dead
>> Sukrit> 12.0.11.2 eth0/eth0 Full
>> 192.168.1.7
>> Sukrit> 1 32
>>
>> Sukrit> On Cisco 7200 (Router id 192.168.1.7 )connected to
>> 12.0.11.3 and to
>> Sukrit> 14.1.107.2, sho ip ospf neighbor shows:
>> Sukrit> Neighbor ID Pri State Dead Time Address
>> Sukrit> Interface
>> Sukrit> 12.0.11.3 128 FULL/BDR 00:00:38
>> 12.0.11.3
>> Sukrit> Ethernet2/0
>> Sukrit> 192.168.1.10 1 FULL/DR 00:00:37
>> 14.1.107.2
>> Sukrit> Ethernet2/1
>>
>> Sukrit> On Cisco 7200 (Router id 192.168.1.10) connected to
>> 14.1.107.1 and to
>> Sukrit> 16.0.43.2, sho ip ospf neighbor shows:
>> Sukrit> Neighbor ID Pri State Dead Time Address
>> Sukrit> Interface
>> Sukrit> 16.0.43.2 128 FULL/BDR 00:00:38
>> 16.0.43.2
>> Sukrit> Ethernet1/0
>> Sukrit> 192.168.1.7 1 FULL/BDR 00:00:31
>> 14.1.107.1
>> Sukrit> Ethernet1/1
>>
>> Sukrit> On XORP/Linux 16.0.43.2, show ospf4 neighbor shows:
>> Sukrit> Address Interface State ID
>> Sukrit> Pri Dead
>> Sukrit> 16.0.43.110 eth1/eth1 Full
>> 192.168.1.10
>> Sukrit> 1 39
>>
>>
>> Sukrit> So you see, the routers can see each other however,
>> the correct area
>> Sukrit> information is not propagating through for some
>> reason. A similar
>> Sukrit> setup used to work earlier before a power failure
>> knocked out the
>> Sukrit> machines running XORP. I used to validate the reach-
>> ability through
>> Sukrit> "route -e" on the linux machines.
>> Sukrit> I was wondering if its a linux issue and I forgot
>> something about
>> Sukrit> some flags since its been a long time I played with
>> XORP. The
>> Sukrit> ip_forward flag is set to 1.
>>
>> Sukrit> Thanks,
>> Sukrit> Sukrit
>>
>> Sukrit> On Mar 1, 2008, at 2:52 AM, Atanu Ghosh wrote:
>>
>>>> Hi,
>>>>
>>>> The output of "show ospf4 neighbor" would be a useful starting
>>>> point
>>>> to verify that the adjacencies have been correctly formed.
>>>>
>>>> Atanu.
>>>>
>>>>>>>>> "Sukrit" == Sukrit Dasgupta <sd88 at drexel.edu> writes:
>>>>
>> Sukrit> Hi list, I have a pretty simple setup of 3 areas using
>>>> OSPF:
>>>>
>>>>
>> Sukrit> 12.0.0.0 (Area1: XORP on Linux)<---------->14.0.0.0
>>>> (Area 0:
>> Sukrit> Cisco 7200 Testbed) <-----------------> 16.0.0.0 (Area 2:
>> Sukrit> XORP on linux)
>>>>
>> Sukrit> The XORP border routers in Area 1 and Area 2 can ping the
>> Sukrit> Cisco ABR routers, but thats about it. The linux route
>>>> table
>> Sukrit> shows that only an entry for the corresponding area. So
>>>> for
>> Sukrit> example, $route -e on the XORP with router with IP
>>>> 12.0.11.2
>> Sukrit> connected to the Cisco 7200 with IP 12.0.11.3 only shows
>>>>
>> Sukrit> Destination Gateway Genmask Flags MSS Window irtt Iface
>> Sukrit> 12.0.11.0 * 255.255.255.0 U 0 0 0 eth1
>>>>
>> Sukrit> No OSPF area information is being shared amongst the
>> Sukrit> routers.
>>>>
>> Sukrit> Any ideas?
>>>>
>> Sukrit> Thanks in advance Sukrit
>>>>
>> Sukrit> _______________________________________________ Xorp-
>> users
>> Sukrit> mailing list Xorp-users at xorp.org
>> Sukrit> http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-
>>>> users
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20080303/376d2446/attachment-0001.html
More information about the Xorp-users
mailing list