From: Chua, Parry (Parry.Chua@xxxxxxxxxx)
Date: Thu Feb 07 2002 - 04:01:03 GMT-3
AS you are using NBMA in a Hub/spoke configuration, you should configure
neigh in the hub router instead of the spoke routers. Set spoke router
ip ospf interface priority to 0.
You should see 2 neigh at hub ( assume that two spoke) and see 1 neigh
per spoke(to hub),
this is what suppose to work on ospf in a multiple access network( ie DR
neigh with other routers, other router only neigh with DR(hub)).
You should ensure that the spoke can communicate to other spoke as it is
in the same subnet.
Parry Chua
-----Original Message-----
From: haluk [mailto:haluk@sprint.ca]
Sent: Thursday, February 07, 2002 2:25 PM
To: Carl Phelan; ccielab@groupstudy.com
Subject: Re: Solie and Skynet - Practice Lab 1
Hi Carl,
When you use multipoint interface type, it means that OSPF is running
NBMA
and in that Access mode, All routers have a neighbor relationship with
designated router and they exchange all LSAs via Designated router.
Since
you set OSPF priority 200 on r1 router ( which is hub router and it
should
be like that) R1 is elected as a designated router and it is sending all
LSAs to all spoke routers. You don't need to put second neighbor on r2
and
r3 for each other. I hope that helps.
Haluk
----- Original Message -----
From: "Carl Phelan" <carlphelan@hotmail.com>
To: "Emmanuel Oppong" <e-oppong@attbi.com>; <ccielab@groupstudy.com>
Sent: Wednesday, February 06, 2002 3:12 PM
Subject: Re: Solie and Skynet - Practice Lab 1
> As you can see below, the timers are the same for all 3 routers as the
hello
> interval on R3 must be 60 secs. - so must the other 2 routers in the
frame
> in order to peer. Many thanks for your reply. I did put a neighbor
> statement on both R2 and
> R3 in OSPF config mode - weird thing is it doesn't show up in 'sh run'
but
> changes the OSPF neighbor state from nothing to ATTEMPT. I am using
the
> following IOS:
>
> System image file is "flash:c2500-ins-l.120-15.bin" on all 3 routers.
>
>
>
>
> R2#sh ip ospf int
> Serial1 is up, line protocol is up
> Internet Address 140.100.4.2/24, Area 0
> Process ID 1, Router ID 140.100.4.2, Network Type NON_BROADCAST,
Cost:
64
> Transmit Delay is 1 sec, State DROTHER, Priority 0
> Designated Router (ID) 140.100.4.1, Interface address 140.100.4.1
> No backup designated router on this network
> Timer intervals configured, Hello 60, Dead 240, Wait 240, Retransmit
5
> Hello due in 00:00:39
> Neighbor Count is 1, Adjacent neighbor count is 1
> Adjacent with neighbor 140.100.4.1 (Designated Router)
> Suppress hello for 0 neighbor(s)
>
> R1#sh ip ospf int s0.2
> Serial0.2 is up, line protocol is up
> Internet Address 140.100.4.1/24, Area 0
> Process ID 1, Router ID 140.100.4.1, Network Type NON_BROADCAST,
Cost:
64
> Transmit Delay is 1 sec, State DR, Priority 1
> Designated Router (ID) 140.100.4.1, Interface address 140.100.4.1
> No backup designated router on this network
> Timer intervals configured, Hello 60, Dead 240, Wait 240, Retransmit
5
> Hello due in 00:00:23
> Neighbor Count is 2, Adjacent neighbor count is 2
> Adjacent with neighbor 140.100.4.2
> Adjacent with neighbor 140.100.4.3
> Suppress hello for 0 neighbor(s)
>
> R3#sh ip ospf int
> Serial0 is up, line protocol is up
> Internet Address 140.100.4.3/24, Area 0
> Process ID 1, Router ID 140.100.4.3, Network Type NON_BROADCAST,
Cost:
64
> Transmit Delay is 1 sec, State DROTHER, Priority 0
> Designated Router (ID) 140.100.4.1, Interface address 140.100.4.1
> No backup designated router on this network
> Timer intervals configured, Hello 60, Dead 240, Wait 240, Retransmit
5
> Hello due in 00:00:14
> Neighbor Count is 1, Adjacent neighbor count is 1
> Adjacent with neighbor 140.100.4.1 (Designated Router)
> Suppress hello for 0 neighbor(s)
>
> ----- Original Message -----
> From: "Emmanuel Oppong" <e-oppong@attbi.com>
> To: "Carl Phelan" <carlphelan@hotmail.com>; <ccielab@groupstudy.com>
> Cc: <e-oppong@attbi.com>
> Sent: Wednesday, February 06, 2002 10:56 PM
> 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