Re: Ospf Point-to-point to multipoint

From: Brian Dennis <bdennis_at_ine.com>
Date: Fri, 8 Mar 2013 16:18:14 -0600

It appears that he has restrictions with using point-to-multipoint on the
spokes and is using physical interfaces on them also.

I have to ask. Why are you disabling inverse-ARP on the physical interface
when you don't have an IP address assigned to the physical interface?

--
Brian Dennis, CCIEx5 #2210 (R&S/ISP-Dial/Security/SP/Voice)
bdennis_at_ine.com<mailto:bdennis_at_ine.com>
INE, Inc.
http://www.INE.com<http://www.ine.com/>
From: Sunil Modi <sunil.s.modi_at_gmail.com<mailto:sunil.s.modi_at_gmail.com>>
Date: Friday, March 8, 2013 5:07 PM
To: Brian Dennis <bdennis_at_ine.com<mailto:bdennis_at_ine.com>>
Cc: Daniel Barney Briseqo
<daniel.barney.b_at_hotmail.com<mailto:daniel.barney.b_at_hotmail.com>>, Cisco
certification <ccielab_at_groupstudy.com<mailto:ccielab_at_groupstudy.com>>
Subject: Re: Ospf Point-to-point to multipoint
Maybe I'm missing something, but wouldn't the following work:
R1
int ser0/0
enc fram
no fram inv
interface Serial0/0.124 multipoint
 ip address 172.16.124.1 255.255.255.0
 ip ospf network point-to-multipoint
 frame-relay interface-dlci 102
 frame-relay interface-dlci 105
end
R1(config-router)#do sh ip ospf nei | i 124
172.16.124.5      0   FULL/  -        00:01:59    172.16.124.5
Serial0/0.124
172.16.124.2      0   FULL/  -        00:01:50    172.16.124.2
Serial0/0.124
R2 &R5
int ser0/0
enc frame rel
no fram inv
interface Serial0/0/0.124 point-to-point
 ip address 172.16.124.5 255.255.255.0
 ip ospf network point-to-multipoint
 frame-relay interface-dlci 501
end
R5(config-if)#do sh ip ospf nei
Neighbor ID     Pri   State           Dead Time   Address         Interface
172.16.124.1      0   FULL/  -        00:01:39    172.16.124.1
Serial0/0/0.124
R5(config-router)#do sh ip route os
     172.16.0.0/16<http://172.16.0.0/16> is variably subnetted, 3 subnets, 2
masks
O       172.16.124.1/32<http://172.16.124.1/32> [110/64] via 172.16.124.1,
00:00:59, Serial0/0/0.124
O       172.16.124.2/32<http://172.16.124.2/32> [110/128] via 172.16.124.1,
00:00:59, Serial0/0/0.124
On Fri, Mar 8, 2013 at 12:50 PM, Brian Dennis
<bdennis_at_ine.com<mailto:bdennis_at_ine.com>> wrote:
Could you just use PPPoFR?
In your current configuration if you enter a "show ip route <remote spoke's
FR
INT IP>" from a spoke and it points directly to the interface and not the
hub,
then you'll need some sort of L3 to L2 mapping to reach the remote spoke.  If
you used OSPF Point-to-Multipoint on the spokes the route to reach the other
spoke (/32 host route) would be via the hub as opposed to the directly
connected interface as it is with the OSPF Point-to-Point network type.  This
is the reason you need a "mapping" on the spoke to reach the other spoke.
Technically speaking OSPF Point-to-Multipoint is making the L3 topology in
sync with the L2 topology by routing the spoke to spoke communication through
the hub.  OSPF Point-to-Multipoint is a "proper" solution by putting the L3
topology in sync with the L2 topology as opposed to a "hack" solution of
PPPoFR or mapping the spoke's L3 address to the L2 address of the hub.
--
Brian Dennis, CCIEx5 #2210 (R&S/ISP-Dial/Security/SP/Voice)
bdennis_at_ine.com<mailto:bdennis_at_ine.com><mailto:bdennis_at_ine.com<mailto:bdennis
@ine.com>>
INE, Inc.
http://www.INE.com<http://www.ine.com/>
From: Daniel Barney Briseqo
<daniel.barney.b_at_hotmail.com<mailto:daniel.barney.b_at_hotmail.com><mailto:danie
l.barney.b_at_hotmail.com<mailto:daniel.barney.b_at_hotmail.com>>>
Date: Friday, March 8, 2013 11:29 AM
To: Brian Dennis
<bdennis_at_ine.com<mailto:bdennis_at_ine.com><mailto:bdennis_at_ine.com<mailto:bdenni
s_at_ine.com>>>
Cc: Cisco certification
<ccielab_at_groupstudy.com<mailto:ccielab_at_groupstudy.com><mailto:ccielab_at_groupst
udy.com<mailto:ccielab_at_groupstudy.com>>>
Subject: Re: Ospf Point-to-point to multipoint
The lab I am doing is asking for that:
- No frame relay maps between the spokes.
- Spokes should be point to point using the physical interface, so i change
the network type with ip ospf network and  i set the timers to be equal with
ip ospf hello-timers
-hub must be multipoint.
Ping with the hub works fine. From spoke to spoke, it is.
Daniel Barney Briseqo
"El zltimo minuto tambiin tiene 60 segundos"
daniel.barney.b_at_hotmail.com<mailto:daniel.barney.b_at_hotmail.com><mailto:daniel
.barney.b_at_hotmail.com<mailto:daniel.barney.b_at_hotmail.com>>
On Mar 7, 2013, at 7:23 PM, Brian Dennis wrote:
I'm assuming that your spokes are also multipoint (physical Frame Relay or
multipoint subinterface) since you mentioned the spokes are not allowed
the communicated directly.  Is there a reason you don't have the spokes
set to point-to-multipoint?  Point-to-multipoint is designed to allow for
reachability between the spokes without the need for mappings between
spokes in the event the spokes are multipoint interfaces.
--
Brian Dennis, CCIEx5 #2210 (R&S/ISP-Dial/Security/SP/Voice)
bdennis_at_ine.com<mailto:bdennis_at_ine.com><mailto:bdennis_at_ine.com<mailto:bdennis
@ine.com>>
INE, Inc.
http://www.INE.com
On 3/7/13 4:53 PM, "Daniel Barney Briseqo"
<daniel.barney.b_at_hotmail.com<mailto:daniel.barney.b_at_hotmail.com><mailto:danie
l.barney.b_at_hotmail.com<mailto:daniel.barney.b_at_hotmail.com>>>
wrote:
Hello there.
In this topology, over frame relay:
R1-----------R2
|
|
R3
-I only have frame relay maps from, R1 to R2 and from R1 to R3.
-Frame relay between the spokes is not allowed
-The spokes must be ospf network type point-to-point and the hub
multipoint.
-I have changed the hello timers, so neighbors are UP.
I have connectivity from hub to both spokes, but I dont have from spoke to
spoke.
Is this a split horizon issue?
Rutes are being propagated well, I have announced the loopbacks on ospf
and I
can see all of them on each router.
Daniel Barney Briseqo
"El zltimo minuto tambiin tiene 60 segundos"
daniel.barney.b_at_hotmail.com<mailto:daniel.barney.b_at_hotmail.com><mailto:daniel
.barney.b_at_hotmail.com<mailto:daniel.barney.b_at_hotmail.com>>
Blogs and organic groups at http://www.ccie.net
Received on Fri Mar 08 2013 - 16:18:14 ART

This archive was generated by hypermail 2.2.0 : Wed Apr 03 2013 - 19:06:19 ART