From: anthony ohanusi (ohanusi@lagos.sns.slb.com)
Date: Mon Nov 11 2002 - 17:19:05 GMT-3
The multicast source should always be at the hub, for hub and spoke design
,if the source is at the remote ,the hub will not replicate this not like
in unicast routing
Put the ip igmp join command at the hub
Regards
At 11:32 AM 11/11/2002, frank.yu@japan.bnpparibas.com wrote:
>Donny,
>
> oh yeah, I wonder why that though? Is this because something similar like
>split horizon, 239.1.6.1 and 2 incoming interface on R4 are s0.1, and s0.1
>won't be the outgoing interface?
> I tried to turned off split horizon under s0.1 on R4, did not help. Any
>one help?
> Thanks.
>
>Frank
>
>
>
>Internet
>donny.mateo@sg.ca-indosuez.com - 11/11/2002 07:23 PM
>
>To: Frank Yu
>
>cc: ccielab, nobody
>
>
>Subject: Re: multicast over FR
>
>
>
>Hi Frank,
>
>just wondering, if you take a look at the mroute table, all the multicast
>route for your group
>(except the RP announce and RP discovery ( * , G ) entry) are prunned.
>so...
>
>Best Regards
>Donny
>
>
>
> frank.yu@japan.bnp
> paribas.com To:
>ccielab@groupstudy.com
> Sent by: cc:
> nobody@groupstudy. Subject: multicast over FR
> com
>
>
> 11-11-2002 16:02
> Please respond to
> frank.yu
>
>
>
>
>
>
>Group,
>
> Woking with multicast over FR with no luck. I need some help here.
> Hub and spoke topology, where R4 is the hub router serving as both RP
>and map agent (note: frame relay is configured under multipoint
>subinterface). R3 and R6 are spoke routers configuration are all under
>physical interfaces. IP connectivity is fine, R6 is configured with "ip
>igmp join-group 239.1.6.1"and "ip igmp join-group 239.1.6.2", I can ping
>the multicast addresses from R4, no problem.
> Here comes the problem, on R3 which is another spoke router, I tried to
>ping the mulitcast addresses several times, no response :-(
> From the following output on R3, I can tell R3 got the correct RP and
>group-to-rp which is R4. R3 also has the route (239.1.6.1and 239.1.6.2) in
>his multicast routing table. I searched archive tried some suggestion such
>as put "ip pim nbma-mode" under the subinterface of R4, did not work. Why I
>can't ping the multicast address on R6 from R3? Am I missing something
>here?
>
>R3#
>R3#sh ip pim rp
>Group: 239.1.6.1, RP: 135.1.34.4, v2, v1, uptime 00:01:47, expires 00:02:38
>Group: 239.1.6.2, RP: 135.1.34.4, v2, v1, uptime 00:01:34, expires 00:02:39
>R3#sh ip pim rp ma
>PIM Group-to-RP Mappings
>
>Group(s) 239.1.6.1/32
> RP 135.1.34.4 (?), v2v1
> Info source: 135.1.34.4 (?), via Auto-RP
> Uptime: 00:06:01, expires: 00:02:33
>Group(s) 239.1.6.2/32
> RP 135.1.34.4 (?), v2v1
> Info source: 135.1.34.4 (?), via Auto-RP
> Uptime: 00:06:01, expires: 00:02:33
>R3#ping 239.1.6.1
>
>Type escape sequence to abort.
>Sending 1, 100-byte ICMP Echos to 239.1.6.1, timeout is 2 seconds:
>.
>R3#sh ip mro
>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 - Advertised via MSDP, U - URD,
> I - Received Source Specific Host Report
>Outgoing interface flags: H - Hardware switched
>Timers: Uptime/Expires
>Interface state: Interface, Next-Hop or VCD, State/Mode
>
>(*, 224.0.1.39), 00:12:47/00:02:59, RP 0.0.0.0, flags: DJC
> Incoming interface: Null, RPF nbr 0.0.0.0
> Outgoing interface list:
> Serial0, Forward/Sparse-Dense, 00:12:47/00:00:00
>
>(135.1.34.4, 224.0.1.39), 00:02:24/00:00:35, flags: PCTA
> Incoming interface: Serial0, RPF nbr 0.0.0.0
> Outgoing interface list: Null
>
>(*, 224.0.1.40), 00:13:47/00:00:00, RP 0.0.0.0, flags: DJCL
> Incoming interface: Null, RPF nbr 0.0.0.0
> Outgoing interface list:
> Serial0, Forward/Sparse-Dense, 00:13:47/00:00:00
>
>(135.1.34.4, 224.0.1.40), 00:05:25/00:02:14, flags: PCLTA
> Incoming interface: Serial0, RPF nbr 0.0.0.0
> Outgoing interface list: Null
>
>(*, 239.1.6.1), 00:02:17/00:02:59, RP 135.1.34.4, flags: SP
> Incoming interface: Serial0, RPF nbr 135.1.34.4
> Outgoing interface list: Null
>
>(135.1.34.4, 239.1.6.1), 00:02:17/00:00:42, flags: PT
> Incoming interface: Serial0, RPF nbr 0.0.0.0
> Outgoing interface list: Null
>
>(*, 239.1.6.2), 00:02:04/00:02:59, RP 135.1.34.4, flags: SP
> Incoming interface: Serial0, RPF nbr 135.1.34.4
> Outgoing interface list: Null
>
>(135.1.34.4, 239.1.6.2), 00:02:04/00:00:55, flags: PT
> Incoming interface: Serial0, RPF nbr 0.0.0.0
> Outgoing interface list: Null
>
>R3#ping 239.1.6.1
>
>Type escape sequence to abort.
>Sending 1, 100-byte ICMP Echos to 239.1.6.1, timeout is 2 seconds:
>.
>R3#ping 239.1.6.2
>
>Type escape sequence to abort.
>Sending 1, 100-byte ICMP Echos to 239.1.6.2, timeout is 2 seconds:
>.
>R3#
>
>
>
>This message and any attachments (the "message") is
>intended solely for the addressees and is confidential.
>If you receive this message in error, please delete it and
>immediately notify the sender. Any use not in accord with
>its purpose, any dissemination or disclosure, either whole
>or partial, is prohibited except formal approval. The internet
>can not guarantee the integrity of this message.
>BNP PARIBAS (and its subsidiaries) shall (will) not
>therefore be liable for the message if modified.
>
> ---------------------------------------------
>
>Ce message et toutes les pieces jointes (ci-apres le
>"message") sont etablis a l'intention exclusive de ses
>destinataires et sont confidentiels. Si vous recevez ce
>message par erreur, merci de le detruire et d'en avertir
>immediatement l'expediteur. Toute utilisation de ce
>message non conforme a sa destination, toute diffusion
>ou toute publication, totale ou partielle, est interdite, sauf
>autorisation expresse. L'internet ne permettant pas
>d'assurer l'integrite de ce message, BNP PARIBAS (et ses
>filiales) decline(nt) toute responsabilite au titre de ce
>message, dans l'hypothese ou il aurait ete modifie.
>
>
>
>
>
>This message is for information purposes only and its content
>should not be construed as an offer, or solicitation of an offer,
>to buy or sell any banking or financial instruments or services
>and no representation or warranty is given in respect of its
>accuracy, completeness or fairness. The material is subject
>to change without notice. You should take your own independent
>tax, legal and other professional advice in respect of the content
>of this message. This message may contain confidential or
>legally privileged material and may not be copied, redistributed
>or published (in whole or in part) without our prior written consent.
>This email may have been intercepted, partially destroyed,
>arrive late, incomplete or contain viruses and no liability is
>accepted by any member of the Credit Agricole Indosuez group
>as a result. If you are not the intended recipient of this message,
>please immediately notify the sender and delete this message
>from your computer.
>
>
>
>
>
>
>This message and any attachments (the "message") is
>intended solely for the addressees and is confidential.
>If you receive this message in error, please delete it and
>immediately notify the sender. Any use not in accord with
>its purpose, any dissemination or disclosure, either whole
>or partial, is prohibited except formal approval. The internet
>can not guarantee the integrity of this message.
>BNP PARIBAS (and its subsidiaries) shall (will) not
>therefore be liable for the message if modified.
>
> ---------------------------------------------
>
>Ce message et toutes les pieces jointes (ci-apres le
>"message") sont etablis a l'intention exclusive de ses
>destinataires et sont confidentiels. Si vous recevez ce
>message par erreur, merci de le detruire et d'en avertir
>immediatement l'expediteur. Toute utilisation de ce
>message non conforme a sa destination, toute diffusion
>ou toute publication, totale ou partielle, est interdite, sauf
>autorisation expresse. L'internet ne permettant pas
>d'assurer l'integrite de ce message, BNP PARIBAS (et ses
>filiales) decline(nt) toute responsabilite au titre de ce
>message, dans l'hypothese ou il aurait ete modifie.
This archive was generated by hypermail 2.1.4 : Tue Dec 03 2002 - 07:22:56 GMT-3