From: Erick B. (erickbe@xxxxxxxxx)
Date: Fri Aug 23 2002 - 02:23:04 GMT-3
   
Jim,
Virtual Links are associated with the neighbors router
ID - not IP address of adjancent interface. The router
id by default is the highest IP address of any
physical interface, or the highest IP of a loopback if
there is a loopback interface configured. You can
manually configure the router-id as well. It doesn't
have to be a valid IP address on the router, just
needs to be a unique number in the OSPF domain.
HTH, Erick
--- jim.phillipo@guardent.com wrote:
> Take a look at these configs. How is router 3 using
> the Ethernet of router 4
> 137.20.40.1 as the virtual link end point ?
>
> The only way I have been able to make things work is
> to add a loopback to
> rtr 4 and use that as rtr3's link neighbor.
>
> Any thoughts ?   I am losing my mind on this one.
>
> R4
> interface Ethernet0
>  ip address 137.20.40.1 255.255.255.0
> area0---r3---area1-----r4---area40
>  ipx network 400
>  ipx type-20-propagation
>  bridge-group 1
> !
> interface Serial0
>  no ip address
>  shutdown
>  no fair-queue
> !
> interface Serial1
>  ip address 137.20.103.2 255.255.255.0
>  clockrate 2000000
> !
> router ospf 1
>  log-adjacency-changes
>  area 1 virtual-link 137.20.3.65
>  network 137.20.40.1 0.0.0.0 area 40
>  network 137.20.103.2 0.0.0.0 area 1
>
>
> r3
> interface Loopback0
>  ip address 137.20.3.33 255.255.255.224
>  ipx network 30000
> !
> interface Loopback1
>  ip address 137.20.3.65 255.255.255.224
>  ipx network 30001
> !
> !
> interface Serial0
>  ip address 137.20.103.1 255.255.255.0
> !
> interface Serial1
>  ip address 137.20.101.3 255.255.255.0
>  encapsulation frame-relay
>  ip ospf network point-to-multipoint
>  ipx network 3150
>  custom-queue-list 1
>  clockrate 64000
>  frame-relay map ip 137.20.101.1 301 broadcast
>  frame-relay lmi-type ansi
> !
> interface TokenRing0
>  ip address 137.20.30.1 255.255.255.0
>  ipx network 300
>  ipx type-20-propagation
>  ring-speed 16
>  source-bridge 1 1 10
>  source-bridge spanning
> !
> router ospf 1
>  log-adjacency-changes
>  area 1 virtual-link 137.20.40.1
>  area 31 range 137.20.3.0 255.255.255.0
>  network 137.20.3.0 0.0.0.255 area 31
>  network 137.20.30.1 0.0.0.0 area 30
>  network 137.20.101.3 0.0.0.0 area 0
>  network 137.20.103.1 0.0.0.0 area 1
> !
> !
>
> -----Original Message-----
> From: Jim Phillipo
> Sent: Thursday, August 22, 2002 8:07 PM
> To: ccielab@groupstudy.com
> Subject: OSPF Issue
>
>
> I  am working on lab 3 of CCIE boot camp.
>
> I have a area that needs a virtual link to connect
> to the back
> bone.Everything appears ok, but the interface that
> is in the area that needs
> the virtual link is not in the routing table of the
> ABR connected to the
> Backbone. But the LSA is in its Database ?
>
>
> Any thoughts ?
>
> Here is the Database and route table:  137.20.40.0
> is the missing network
>
>
>        OSPF Router with ID (137.20.3.65) (Process ID
> 64)
>
>
>                 Router Link States (Area 0)
>
> Link ID         ADV Router      Age         Seq#
>   Checksum Link count
> 137.20.3.65     137.20.3.65     603
> 0x80000005 0xA30A   3
> 137.20.101.1    137.20.101.1    1089
> 0x80000011 0x1B53   5
> 137.20.103.2    137.20.103.2    604
> 0x80000021 0x8022   2
> 172.168.32.1    172.168.32.1    894
> 0x80000004 0xEBBF   2
>
>                 Summary Net Link States (Area 0)
>
> Link ID         ADV Router      Age         Seq#
>   Checksum
> 137.20.30.0     137.20.3.65     1050
> 0x80000001 0x7A1F
> 137.20.30.0     137.20.103.1    2603
> 0x80000001 0x3D38
> 137.20.103.0    137.20.3.65     1107
> 0x80000001 0x9A7B
>
>                 Router Link States (Area 1)
>
> Link ID         ADV Router      Age         Seq#
>   Checksum Link count
> 137.20.3.65     137.20.3.65     617
> 0x80000004 0x1AB0   2
> 137.20.103.2    137.20.103.2    607
> 0x8000000E 0xE9B0   2
>
>                 Summary Net Link States (Area 1)
>
> Link ID         ADV Router      Age         Seq#
>   Checksum
> 1.0.0.0         137.20.103.2    30
> 0x80000001 0x8AA0
> 137.20.30.0     137.20.3.65     1053
> 0x80000001 0x7A1F
> 137.20.30.0     137.20.103.2    603
> 0x80000001 0xB97A
> 137.20.40.0     137.20.103.2    607
> 0x80000006 0xE67A
> 137.20.100.0    137.20.3.65     1080
> 0x80000001 0x3E9A
> 137.20.100.0    137.20.103.2    603
> 0x80000001 0x7DF5
> 137.20.101.1    137.20.3.65     1080
> 0x80000001 0xA670
> 137.20.101.1    137.20.103.2    603
> 0x80000001 0xE5CB
> 137.20.101.3    137.20.3.65     1110
> 0x80000001 0x1045
> 137.20.101.3    137.20.103.2    603
> 0x80000001 0x4FA0
> 137.20.101.5    137.20.3.65     593
> 0x80000001 0x1D1
> 137.20.101.5    137.20.103.1    1982
> 0x80000001 0xC3EA
>
>                 Router Link States (Area 30)
>
> Link ID         ADV Router      Age         Seq#
>   Checksum Link count
> 137.20.3.65     137.20.3.65     1058
> 0x80000002 0x1B90   1
>
>                 Summary Net Link States (Area 30)
>
> Link ID         ADV Router      Age         Seq#
>   Checksum
> 137.20.100.0    137.20.3.65     1081
> 0x80000001 0x3E9A
> 137.20.101.1    137.20.3.65     1632
> 0x80000001 0xA670
> 137.20.101.3    137.20.3.65     1662
> 0x80000001 0x1045
> 137.20.101.5    137.20.3.65     1145
> 0x80000001 0x1D1
> 137.20.103.0    137.20.3.65     1662
> 0x80000001 0x9A7B
> r3>
>
>
> r3>sho ip rou
> Codes: C - connected, S - static, I - IGRP, R - RIP,
> M - mobile, B - BGP
>        D - EIGRP, EX - EIGRP external, O - OSPF, IA
> - OSPF inter area
>        N1 - OSPF NSSA external type 1, N2 - OSPF
> NSSA external type 2
>        E1 - OSPF external type 1, E2 - OSPF external
> type 2, E - EGP
>        i - IS-IS, L1 - IS-IS level-1, L2 - IS-IS
> level-2, ia - IS-IS inter
> area
>        * - candidate default, U - per-user static
> route, o - ODR
>        P - periodic downloaded static route
>
> Gateway of last resort is not set
>
>      137.20.0.0/16 is variably subnetted, 8 subnets,
> 3 masks
> C       137.20.30.0/24 is directly connected,
> TokenRing0
> C       137.20.3.32/27 is directly connected,
> Loopback0
> C       137.20.3.64/27 is directly connected,
> Loopback1
> C       137.20.101.0/24 is directly connected,
> Serial1
> O       137.20.101.1/32 [110/64] via 137.20.101.1,
> 00:19:46, Serial1
> O       137.20.100.0/24 [110/128] via 137.20.101.1,
> 00:19:46, Serial1
> C       137.20.103.0/24 is directly connected,
> Serial0
> O       137.20.101.5/32 [110/128] via 137.20.101.1,
> 00:19:47, Serial1
> r3>
>
This archive was generated by hypermail 2.1.4 : Sat Sep 07 2002 - 19:48:35 GMT-3