From: Jongsoo.Kim@Intelsat.com
Date: Fri Aug 13 2004 - 10:56:33 GMT-3
R1 is directly connected to R2 via FE.
I tried spoke to spoke ( R4 to R5).
I have very unstable result. Sometimes never worked but sometimes it works
with duplicate response.
But it never work in a way supposed to be.
Later today, I will show you the result on this.
JK
-----Original Message-----
From: ccie2be [mailto:ccie2be@nyc.rr.com]
Sent: Friday, 13 August, 2004 6:01 AM
To: Kim, Jongsoo; ccielab@groupstudy.com
Subject: Re: My Lab result on "pim nbma-mode" using SM, SD, DM
Hi,
Good going.
I read your post carefully but I'm not clear on a couple of points.
Where is R1 in your network?
Also, what happens when you make just R5 a mcast member and ping from R4?
Does the ping get forwarded by R2 under all conditions?
Thanks again. Tim
----- 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 R1,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
>
> _______________________________________________________________________
> Please help support GroupStudy by purchasing your study materials from:
> http://shop.groupstudy.com
>
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
############################################################
Building on 40 Years of Leadership - As a global communications leader with 40 years of experience, Intelsat helps service providers,
broadcasters, corporations and governments deliver information and entertainment anywhere in the world, instantly, securely and reliably.
############################################################
This email message is for the sole use of the intended
recipient(s) and may contain confidential and privileged
information. Any unauthorized review, use, disclosure or
distribution is prohibited. If you are not the intended
recipient, please contact the sender by reply email and
destroy all copies of the original message. Any views
expressed in this message are those of the individual
sender, except where the sender specifically states them
to be the views of Intelsat, Ltd. and its subsidiaries.
############################################################
This archive was generated by hypermail 2.1.4 : Fri Sep 03 2004 - 07:02:43 GMT-3