From: Jongsoo.Kim@Intelsat.com
Date: Mon Mar 21 2005 - 23:33:07 GMT-3
Guys
Here is one lab result I did a long time ago about this topic.
Regarding multicasr over NBMA, it is very imporatnt where you have the
source, MA, RP.
Rule of thumb is to have them on HUB side. But no matter what auto-rp MA
should be in hub as it uses dense mode.
ip pim nbma-mode should be on in hub
See below my lab I sent Aug 2004.
I still believe something may be wrong in my lab.
Because ip pim nbma-mode is only supposed to be used for sparse-mode...
I was focused on finding out the effect of "ip pim nbma-mode" on Hub router
in mroute table entry.
This command basically enable multicast capability over NBMA medium.
Wihtout this command, Hub seems to send mulicast stream only to one spoke
even though you config IGMP join groups on both spoke. For that aspect,
this command is needed for SM, SD, DM.
----- Original Message -----
From: <jongsoo.kim@intelsat.com>
To: <ccielab@groupstudy.com>
Sent: Thursday, August 12, 2004 8:41 PM
Subject: My Lab result on "pim nbma-mode" using SM, SD, DM
> Guys
>
> I set up a lab using R2,R4,and R5.
> R2,4,5 are F/R multipoint and R2 is hub and R4& R5 are spoke.
> I created R4 and R5 igmp join-group 235.0.0.1
> R2 is MA as well as RP.
>
> I focused on the affect of pim nbma-mode on F/R multipoint uinsg SM, SD,
DM.
> I validate based on ping result from R1 to 235.0.0.1 and mroute from R2.
>
> My result showes pim nbma-mode is always needed regardless of SM, SD, DM.
> This is the only way R1 can get ping reply-back from R4 and R5
>
> I know cisco doesn't recommend pim nbma-mode on DM or SD but it is
necessray based on my lab unless I am doing something wrong.
>
> Here is config and result
>
> Lab #1 pim sparse-mode on serial 0 of R2,4,5
>
> r2#show run int s0
> Building configuration...
>
> Current configuration : 221 bytes
> !
> interface Serial0
> ip address 10.0.0.2 255.255.255.0
> ip pim sparse-mode
> encapsulation frame-relay
> frame-relay map ip 10.0.0.4 104 broadcast
> frame-relay map ip 10.0.0.5 105 broadcast
> frame-relay lmi-type cisco
> end
>
> r2#show ip mroute 235.0.0.1
>
> (*, 235.0.0.1), 00:00:28/00:02:59, RP 20.0.0.1, flags: SJC
> Incoming interface: Null, RPF nbr 0.0.0.0
> Outgoing interface list:
> Serial0, Forward/Sparse, 00:00:28/00:03:01
>
> (30.0.0.1, 235.0.0.1), 00:00:20/00:02:59, flags: CTA
> Incoming interface: Ethernet0, RPF nbr 0.0.0.0
> Outgoing interface list:
> Serial0, Forward/Sparse, 00:00:20/00:02:39
>
> r1#
> Reply to request 16 from 10.0.0.5, 64 ms
> Reply to request 17 from 10.0.0.5, 64 ms
> Reply to request 18 from 10.0.0.5, 64 ms
>
############################################################################
####
> Lab #2 pim sparse-mode on serial 0 of R2,4,5 and R2 has ip pim nbma-mode
>
> r2#show run int s0
> Building configuration...
>
> Current configuration : 239 bytes
> !
> interface Serial0
> ip address 10.0.0.2 255.255.255.0
> ip pim nbma-mode
> ip pim sparse-mode
> encapsulation frame-relay
> frame-relay map ip 10.0.0.4 104 broadcast
> frame-relay map ip 10.0.0.5 105 broadcast
> frame-relay lmi-type cisco
> end
>
> r2#show ip mroute 235.0.0.1
>
> (*, 235.0.0.1), 00:00:17/00:02:59, RP 20.0.0.1, flags: SJC
> Incoming interface: Null, RPF nbr 0.0.0.0
> Outgoing interface list:
> Serial0, 10.0.0.5, Forward/Sparse, 00:00:03/00:03:26
> Serial0, 10.0.0.4, Forward/Sparse, 00:00:08/00:03:21
>
> (30.0.0.1, 235.0.0.1), 00:00:17/00:02:52, flags: CTA
> Incoming interface: Ethernet0, RPF nbr 0.0.0.0
> Outgoing interface list:
> Serial0, 10.0.0.5, Forward/Sparse, 00:00:03/00:03:26
> Serial0, 10.0.0.4, Forward/Sparse, 00:00:08/00:03:22
> r1#
> Reply to request 36 from 10.0.0.5, 60 ms
> Reply to request 36 from 10.0.0.4, 76 ms
> Reply to request 37 from 10.0.0.5, 60 ms
> Reply to request 37 from 10.0.0.4, 76 ms
>
> ########################################################################
> Lab #3 pim sparse-dense-mode on serial 0 of R2,4,5
>
> r5#show run int s0
> interface Serial0
> ip address 10.0.0.5 255.255.255.0
> ip pim sparse-dense-mode
> encapsulation frame-relay
> ip igmp join-group 235.0.0.1
> frame-relay map ip 10.0.0.2 501 broadcast
> frame-relay map ip 10.0.0.4 501 broadcast
> frame-relay lmi-type cisco
> end
>
> r4#show run int s0
> interface Serial0
> ip address 10.0.0.4 255.255.255.0
> ip pim sparse-dense-mode
> encapsulation frame-relay
> frame-relay map ip 10.0.0.2 401 broadcast
> frame-relay map ip 10.0.0.5 401 broadcast
> frame-relay lmi-type cisco
> end
>
> r2#show run int s0
> interface Serial0
> ip address 10.0.0.2 255.255.255.0
> ip pim sparse-dense-mode
> encapsulation frame-relay
> frame-relay map ip 10.0.0.4 104 broadcast
> frame-relay map ip 10.0.0.5 105 broadcast
> frame-relay lmi-type cisco
> end
>
>
> r2#show ip mroute 235.0.0.1
> (*, 235.0.0.1), 00:01:45/00:02:59, RP 20.0.0.1, flags: SJC
> Incoming interface: Null, RPF nbr 0.0.0.0
> Outgoing interface list:
> Serial0, Forward/Sparse-Dense, 00:01:45/00:03:02
>
> (30.0.0.1, 235.0.0.1), 00:01:42/00:03:27, flags: CTA
> Incoming interface: Ethernet0, RPF nbr 0.0.0.0
> Outgoing interface list:
> Serial0, Forward/Sparse-Dense, 00:01:42/00:03:02
>
> r1#
> Reply to request 8 from 10.0.0.5, 64 ms
> Reply to request 9 from 10.0.0.5, 64 ms
>
############################################################################
#####
> Lab #4 pim sparse-dense-mode on serial 0 of R2,4,5 and R2 has pim
nbma-mode
> r2#show run int s0
> interface Serial0
> ip address 10.0.0.2 255.255.255.0
> ip pim nbma-mode
> ip pim sparse-dense-mode
> encapsulation frame-relay
> frame-relay map ip 10.0.0.4 104 broadcast
> frame-relay map ip 10.0.0.5 105 broadcast
> frame-relay lmi-type cisco
> end
>
> r2#show ip mroute 235.0.0.1
> (*, 235.0.0.1), 00:00:27/00:03:24, RP 20.0.0.1, flags: SJC
> Incoming interface: Null, RPF nbr 0.0.0.0
> Outgoing interface list:
> Serial0, 10.0.0.4, Forward/Sparse-Dense, 00:00:05/00:03:24
> Serial0, 10.0.0.5, Forward/Sparse-Dense, 00:00:25/00:03:04
>
> (30.0.0.1, 235.0.0.1), 00:00:27/00:03:08, flags: CTA
> Incoming interface: Ethernet0, RPF nbr 0.0.0.0
> Outgoing interface list:
> Serial0, 10.0.0.4, Forward/Sparse-Dense, 00:00:05/00:03:28
> Serial0, 10.0.0.5, Forward/Sparse-Dense, 00:00:25/00:03:04
>
> r1#
> Reply to request 24 from 10.0.0.4, 60 ms
> Reply to request 24 from 10.0.0.5, 76 ms
> Reply to request 25 from 10.0.0.4, 60 ms
> Reply to request 25 from 10.0.0.5, 76 ms
>
>
############################################################################
#######
> Lab #5 pim dense-mode on serial 0 of R2,4,5
> r2#show run int s0
> Building configuration...
>
> Current configuration : 220 bytes
> !
> interface Serial0
> ip address 10.0.0.2 255.255.255.0
> ip pim dense-mode
> encapsulation frame-relay
> frame-relay map ip 10.0.0.4 104 broadcast
> frame-relay map ip 10.0.0.5 105 broadcast
> frame-relay lmi-type cisco
> end
>
> r2#
> r2#show ip mroute 235.0.0.1
>
> (*, 235.0.0.1), 00:01:53/00:03:08, RP 20.0.0.1, flags: SJC
> Incoming interface: Null, RPF nbr 0.0.0.0
> Outgoing interface list:
> Serial0, Forward/Dense, 00:01:53/00:00:00
>
> (30.0.0.1, 235.0.0.1), 00:01:52/00:03:25, flags: CTA
> Incoming interface: Ethernet0, RPF nbr 0.0.0.0
> Outgoing interface list:
> Serial0, Forward/Dense, 00:01:52/00:00:00
> r1#
> Reply to request 74 from 10.0.0.5, 64 ms
> Reply to request 75 from 10.0.0.5, 64 ms
> Reply to request 76 from 10.0.0.5, 64 ms
> Reply to request 77 from 10.0.0.5, 64 ms
>
>
############################################################################
#############
> Lab #6 pim dense-mode on serial 0 of R2,4,5 and R2 has pim nbma-mode
>
> r2#show run int s0
> Building configuration...
>
> Current configuration : 238 bytes
> !
> interface Serial0
> ip address 10.0.0.2 255.255.255.0
> ip pim nbma-mode
> ip pim dense-mode
> encapsulation frame-relay
> frame-relay map ip 10.0.0.4 104 broadcast
> frame-relay map ip 10.0.0.5 105 broadcast
> frame-relay lmi-type cisco
> end
> r2#show ip mroute 235.0.0.1
>
> (*, 235.0.0.1), 00:00:27/00:03:23, RP 20.0.0.1, flags: SJC
> Incoming interface: Null, RPF nbr 0.0.0.0
> Outgoing interface list:
> Serial0, Forward/Dense, 00:00:06/00:00:00
> Serial0, Forward/Dense, 00:00:26/00:00:00
>
> (30.0.0.1, 235.0.0.1), 00:00:27/00:02:56, flags: CTA
> Incoming interface: Ethernet0, RPF nbr 0.0.0.0
> Outgoing interface list:
> Serial0, Forward/Dense, 00:00:06/00:00:00
> Serial0, Forward/Dense, 00:00:26/00:00:00
> r1#
> Reply to request 86 from 10.0.0.4, 60 ms
> Reply to request 86 from 10.0.0.5, 76 ms
> Reply to request 87 from 10.0.0.4, 60 ms
> Reply to request 87 from 10.0.0.5, 76 ms
> Reply to request 88 from 10.0.0.4, 60 ms
> Reply to request 88 from 10.0.0.5, 76 ms
-----Original Message-----
From: mani poopal [mailto:mani_ccie@yahoo.com]
Sent: Saturday, 19 March, 2005 10:10 PM
To: ccielab@groupstudy.com
Subject: multicast over NBMA
Hi Guys,
Assume you have multicast over frame relay NBMA network where R1 is hub and
R2 and R3 are spokes. I joined the R2 e0 to multicast group
224.24.24.24(-if)#ip igmp join-group 224.24.24.24).
My Question: I thought you cannot ping this address from other spoke(R3)
becase R1 hub will not send and receive multicast over same interface. My
assumption is we need GRE tunnel interface between both spokes to overcome
this situation, but to my surprise I was able to ping the 224.24.24.24 from
other spoke, R3. Any explanation is appreciated.
thanks
Mani
B.ENG,A+,CCNA,CCNP,CCNP-VOICE, CSS1,CNA,MCSE
(416)431 9929
MANI_CCIE@YAHOO.COM
---------------------------------
Do you Yahoo!?
Yahoo! Small Business - Try our new resources site!
This archive was generated by hypermail 2.1.4 : Sun Apr 03 2005 - 17:56:49 GMT-3