From: louie kouncar (lkouncar@xxxxxx)
Date: Thu May 31 2001 - 19:23:29 GMT-3
It does not matter if the sopkes can ping the hub because.........
EXAMPLE...
Spoke one has Ip add 1.1.1.1
Spoke two has 2.2.2.2
hub 10.10.10.10
When you ping the hub from the spoke the destination ip is 10.10.10.10 which
has a frame map to a dlci
when you ping spoke 2 from spoke 1 the destination ip is 2.2.2.2 not
(10.10.10.10) and there is no layer two info to how the packet should be
encapsulated....
That is why you need to have a Map statment on the spokes.
Hope that helps
Louie J. Kouncar
TCO3 Senior Data Center Engineer
UUNET
W-703-343-6645
C-703-304-2460
-----Original Message-----
From: . .. [mailto:subinterface@yahoo.com]
Sent: Thursday, May 31, 2001 6:08 PM
To: lkouncar@UU.NET; ccielab@groupstudy.com
Subject: RE: OSPF & ip ospf net non-bro
Well, you might have a point but...
both spokes can ping the hub and the hub can ping each
spoke. Also, I didn't include in the example but
there is a p-to-p sub-if off of the hub. It can ping
everything and everything can ping it.
--- louie kouncar <lkouncar@UU.NET> wrote:
> OSI Model......
>
> I will let you figure this out.....
>
> Layer 3 OK
> layer 2 ??????
> Ping .....
>
>
>
> Louie J. Kouncar
> TCO3 Senior Data Center Engineer
> UUNET
> W-703-343-6645
> C-703-304-2460
>
>
>
> -----Original Message-----
> From: nobody@groupstudy.com
> [mailto:nobody@groupstudy.com]On Behalf Of .
> ..
> Sent: Thursday, May 31, 2001 5:18 PM
> To: ccielab@groupstudy.com
> Subject: OSPF & ip ospf net non-bro
>
>
> ok, there have been several of these posts and
> instances in the archives but I've yet to see a
> comprehensive answer. I understand the
> characteristics of ospf non-bro nets and forming
> adjaciencies but I still don't know why the spokes
> can't ping each other. The routes are in the table.
>
> Scenario...
> r3
> /
> r5--fr
> \
> r4
>
> ===> r5 (hub) <===
> interface Serial0.3 multipoint
> ip address 140.11.51.5 255.255.255.0
> ip ospf network non-broadcast
> ip ospf hello-interval 10
> ip ospf priority 10
> frame-relay map ip 140.11.51.3 103 broadcast
> frame-relay map ip 140.11.51.4 104 broadcast
>
> router ospf 1
> network 140.11.51.0 0.0.0.255 area 0
> neighbor 140.11.51.3 priority 1 poll-interval 30
> neighbor 140.11.51.4 priority 1 poll-interval 30
>
> r5# sh ip ro
> O 140.11.33.1/32 [110/1786] via 140.11.51.3,
> 00:17:23, Serial0.3
> O 140.11.44.1/32 [110/1786] via 140.11.51.4,
> 00:17:23, Serial0.3
> C 140.11.51.0/24 is directly connected,
> Serial0.3
>
> =====> r3 & r4 (basically the same, except the
> obvious) <===
>
> interface loopback 0
> ip address 140.11.33.1 255.255.255.0
> (r4's loop is 140.11.44.1/24)
>
> interface Serial0
> ip address 140.11.51.3 255.255.255.0
> encapsulation frame-relay
> ip ospf network non-broadcast
> ip ospf hello-interval 10
> frame-relay map ip 140.11.51.5 301 broadcast
>
> router ospf 1
> network 140.11.33.0 0.0.0.255 area 0
> network 140.11.51.0 0.0.0.255 area 0
> neighbor 140.11.51.5 priority 10 poll-interval 30
>
> r3# sh ip ro
> C 140.11.33.0/24 is directly connected,
> Loopback0
> O 140.11.44.1/32 [110/65] via 140.11.51.4,
> 00:20:58, Serial0
> C 140.11.51.0/24 is directly connected,
> Serial0
>
> as you can see, both loopbacks show up in the
> spoke's
> routing tables but the spokes can't ping each other.
> the DR is the hub already.
>
> Please help.
> Thanks in advance.
>
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 10:30:58 GMT-3