From: Michael Zuo (mzuo@ixiacom.com)
Date: Fri Dec 01 2006 - 19:48:51 ART
Thank you for the replies.
to summarize (so that it is clear in my head :) ):
Dense mode/sparse-dense mode: will not work in H&S natively, tunneling
is needed
Sparse mode: "ip pim nbma-mode" is needed on HUB.
I did some experiments with the sparse-mode with "ip pim nbma-mode"
configured and rp-add configured statically and found out:
1. when RP is the hub, everything is peachy
2. when RP is on the spoke, multicast traffic does not go thru
Is item 2 expected or I missed something (config and debug below just in
case)?
Thanks in advance...
HUB
interface Serial1/0
ip address 150.1.134.1 255.255.255.0
ip pim nbma-mode
ip pim sparse-mode
encapsulation frame-relay
no ip split-horizon eigrp 100
no ip mroute-cache
serial restart-delay 0
no dce-terminal-timing-enable
frame-relay map ip 150.1.134.3 103 broadcast
frame-relay map ip 150.1.134.4 104 broadcast
no frame-relay inverse-arp
end
ip pim rp-address 150.1.134.3
Spoke 1
interface Serial1/0
ip address 150.1.134.4 255.255.255.0
ip pim sparse-mode
encapsulation frame-relay
ip igmp join-group 239.2.2.2
no ip mroute-cache
serial restart-delay 0
no dce-terminal-timing-enable
frame-relay map ip 150.1.134.1 401 broadcast
frame-relay map ip 150.1.134.3 401 broadcast
no frame-relay inverse-arp
end
ip pim rp-address 150.1.134.3
Spoke 2
interface Serial1/0
ip address 150.1.134.3 255.255.255.0
ip pim sparse-mode
encapsulation frame-relay
ip igmp join-group 239.1.1.1
no ip mroute-cache
serial restart-delay 0
no dce-terminal-timing-enable
frame-relay map ip 150.1.134.1 301 broadcast
frame-relay map ip 150.1.134.3 301 broadcast
frame-relay map ip 150.1.134.4 301 broadcast
no frame-relay inverse-arp
end
ip pim rp-address 150.1.134.3
Spoke1#ping 239.1.1.1
Type escape sequence to abort.
Sending 1, 100-byte ICMP Echos to 239.1.1.1, timeout is 2 seconds:
.
Spoke1#
Hub#sh ip mr
IP Multicast Routing Table
Flags: D - Dense, S - Sparse, B - Bidir Group, s - SSM Group, C -
Connected,
L - Local, P - Pruned, R - RP-bit set, F - Register flag,
T - SPT-bit set, J - Join SPT, M - MSDP created entry,
X - Proxy Join Timer Running, A - Candidate for MSDP
Advertisement,
U - URD, I - Received Source Specific Host Report,
Z - Multicast Tunnel, z - MDT-data group sender,
Y - Joined MDT-data group, y - Sending to MDT-data group
Outgoing interface flags: H - Hardware switched, A - Assert winner
Timers: Uptime/Expires
Interface state: Interface, Next-Hop or VCD, State/Mode
(*, 239.1.1.1), 00:01:08/stopped, RP 150.1.134.3, flags: SP
Incoming interface: Serial1/0, RPF nbr 150.1.134.3
Outgoing interface list: Null
(150.1.134.4, 239.1.1.1), 00:00:57/00:02:07, flags: PT
Incoming interface: Serial1/0, RPF nbr 0.0.0.0
Outgoing interface list: Null
(*, 239.2.2.2), 00:01:10/00:02:02, RP 150.1.134.3, flags: SP
Incoming interface: Serial1/0, RPF nbr 150.1.134.3
Outgoing interface list: Null
(*, 224.0.1.40), 00:01:23/00:02:07, RP 150.1.134.3, flags: SJPL
Incoming interface: Serial1/0, RPF nbr 150.1.134.3
Outgoing interface list: Null
Hub#
-----Original Message-----
From: Ivan [mailto:ivan@iip.net]
Sent: Friday, December 01, 2006 12:44 PM
To: ccielab@groupstudy.com; Michael Zuo
Subject: Re: PIM dense mode with Frame-relay hub and spoke
In H&S topology with dense mode you have RPF-failure on HUB-router such
as
input interface the same as output interfase. This problem can be solved
with
Tunnel from spoke-to-spoke.
> Hi group,
>
>
>
> I ran into a problem configuring pim dense mode in the frame-relay hub
> and spoke environment. I configured "ip pim dense" on hub and spoke
and
> "ip igmp join 239.1.1.1" on one spoke. But when i do ping test, it
> fails. Since "ip pim nbma-mode" is not meant for dense mode, is there
> something I missed? Thanks
>
>
>
> R1 (the HUB)
>
> ip multicast-routing
>
> interface Serial1/0
>
> ip address 150.1.134.1 255.255.255.0
>
> ip pim dense-mode
>
> encapsulation frame-relay
>
> no ip split-horizon eigrp 100
>
> serial restart-delay 0
>
> no dce-terminal-timing-enable
>
> frame-relay map ip 150.1.134.3 103 broadcast
>
> frame-relay map ip 150.1.134.4 104 broadcast
>
> no frame-relay inverse-arp
>
> end
>
>
>
>
>
> R3 (Spoke)
>
> ip multicast-routing
>
> interface Serial1/0
>
> ip address 150.1.134.3 255.255.255.0
>
> ip pim dense-mode
>
> encapsulation frame-relay
>
> ip igmp join-group 239.1.1.1
>
> serial restart-delay 0
>
> no dce-terminal-timing-enable
>
> frame-relay map ip 150.1.134.1 301 broadcast
>
> frame-relay map ip 150.1.134.4 301 broadcast
>
> no frame-relay inverse-arp
>
> end
>
>
>
> R4 (Spoke)
>
> ip multicast-routing
>
> interface Serial1/0
>
> ip address 150.1.134.4 255.255.255.0
>
> ip pim dense-mode
>
> encapsulation frame-relay
>
> serial restart-delay 0
>
> no dce-terminal-timing-enable
>
> frame-relay map ip 150.1.134.1 401 broadcast
>
> frame-relay map ip 150.1.134.3 401 broadcast
>
> no frame-relay inverse-arp
>
>
>
>
>
> Rack1R4(config-if)#do ping 150.1.134.3
>
>
>
> Type escape sequence to abort.
>
> Sending 5, 100-byte ICMP Echos to 150.1.134.3, timeout is 2 seconds:
>
> !!!!!
>
> Success rate is 100 percent (5/5), round-trip min/avg/max = 60/119/200
> ms
>
> Rack1R4(config-if)#do ping 239.1.1.1
>
>
>
> Type escape sequence to abort.
>
> Sending 1, 100-byte ICMP Echos to 239.1.1.1, timeout is 2 seconds:
>
> .
>
> Rack1R4(config-if)#
>
>
>
> Rack1R1(config-if)#
>
> *Mar 1 01:14:33.851: IP(0): s=150.1.134.4 (Serial1/0) d=239.1.1.1
> id=48, ttl=25
>
> 4, prot=1, len=104(100), mroute olist null
>
> *Mar 1 01:14:33.859: IP(0): s=150.1.134.4 (Serial1/0) d=239.1.1.1
> id=48, ttl=25
>
> 4, prot=1, len=104(100), mroute olist null
>
> Rack1R1(config-if)#
>
>
This archive was generated by hypermail 2.1.4 : Tue Jan 02 2007 - 07:50:36 ART