From: Alavalapati, Abhimanyu V. (aalavala@xxxxxxxxx)
Date: Wed Feb 06 2002 - 20:37:04 GMT-3
Since it s NON-Broadcast type on each side(default OSPF type for interface
in your config) specify neighbor with
"neighbor r2"
"neighbor r3"
under router ospf on R1(hub)
-----Original Message-----
From: Emmanuel Oppong [mailto:e-oppong@attbi.com]
Sent: Wednesday, February 06, 2002 5:57 PM
To: Carl Phelan; ccielab@groupstudy.com
Cc: e-oppong@attbi.com
Subject: RE: Solie and Skynet - Practice Lab 1
You must use a multipoint interface on r2 or use "ip ospf netwwork
point-to-multipoint" on both interfaces. BUT the lab states that you cannot
use any "ip ospf network .." statement, so you have to use a multipoint
interface. This will make the interface timers the same. If you do "sh ip
ospf int s0" on r2 and "sh ip ospf int s0.2" on r1, you see that they have
different timer values. For adjacency you need the same timer values.
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com]On Behalf Of
Carl Phelan
Sent: Wednesday, February 06, 2002 2:27 PM
To: ccielab@groupstudy.com
Subject: Solie and Skynet - Practice Lab 1
Hi All,
I am having problems with this lab trying to get R2 and R3 to OSPF peer over
hub and spoke Frame Relay . R1 is the hub and both R2 and R3 the spokes. I
include the relevant config excerpts. Both R2 and R3 can ping each other -
R1
is in a full state with both R2 and R3 so where am I going wrong?
Many thanks for your help.
R1
interface Serial0
no ip address
no ip directed-broadcast
encapsulation frame-relay
ip ospf priority 200
no ip mroute-cache
logging event subif-link-status
logging event dlci-status-change
no arp frame-relay
no frame-relay inverse-arp
frame-relay lmi-type ansi
....
interface Serial0.2 multipoint
ip address 140.100.4.1 255.255.255.0
no ip directed-broadcast
ip ospf hello-interval 60
frame-relay map ip 140.100.4.2 110 broadcast
frame-relay map ip 140.100.4.3 120 broadcast
....
router ospf 1
network 140.100.4.0 0.0.0.255 area 0
neighbor 140.100.4.3
neighbor 140.100.4.2
R1#sh ip ospf ne
Neighbor ID Pri State Dead Time Address Interface
140.100.4.2 0 FULL/DROTHER 00:03:43 140.100.4.2 Serial0.2
140.100.4.3 0 FULL/DROTHER 00:03:55 140.100.4.3 Serial0.2
R2
interface Serial1
bandwidth 64
ip address 140.100.4.2 255.255.255.0
no ip directed-broadcast
encapsulation frame-relay
ip ospf hello-interval 60
ip ospf priority 0
logging event subif-link-status
logging event dlci-status-change
frame-relay map ip 140.100.4.1 111 broadcast
frame-relay map ip 140.100.4.3 111 broadcast
frame-relay lmi-type ansi
....
router ospf 1
network 140.100.4.0 0.0.0.255 area 0
...
R2#sh ip ospf ne
Neighbor ID Pri State Dead Time Address Interface
140.100.4.1 1 FULL/DR 00:03:25 140.100.4.1 Serial1
N/A 0 ATTEMPT/DROTHER - 140.100.4.3 Serial1
R3
interface Serial0
ip address 140.100.4.3 255.255.255.0
no ip directed-broadcast
encapsulation frame-relay
ip ospf hello-interval 60
ip ospf priority 0
no ip mroute-cache
logging event subif-link-status
logging event dlci-status-change
frame-relay map ip 140.100.4.1 121 broadcast
frame-relay map ip 140.100.4.2 121 broadcast
frame-relay lmi-type ansi
....
router ospf 1
network 140.100.4.0 0.0.0.255 area 0
....
R3#sh ip ospf ne
Neighbor ID Pri State Dead Time Address Interface
140.100.4.1 1 FULL/DR 00:03:49 140.100.4.1 Serial0
N/A 0 ATTEMPT/DROTHER - 140.100.4.2 Serial0
R3#ping 140.100.4.2
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 140.100.4.2, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 112/117/128 ms
This archive was generated by hypermail 2.1.4 : Thu Jun 20 2002 - 13:46:14 GMT-3