From: FATHALLAH (sfathallah@mail.cbi.net.ma)
Date: Wed May 07 2003 - 06:06:17 GMT-3
sorry there is large time shift betwen our contries.
yes it is a solution. I have tried it, but in pim dense mode.
Said FATHALLAH.
-----Message d'origine-----
De : frank.yu@japan.bnpparibas.com
[mailto:frank.yu@japan.bnpparibas.com]
Envoyi : mercredi 7 mai 2003 02:41
@ : sfathallah@mail.cbi.net.ma
Objet : RE: atuo-rp question
Hi Said,
I think GRE tunnel might be a solution,but I haven't tried yet, what do
you think?
Frank
Internet
sfathallah@mail.cbi.net.ma@groupstudy.com - 05/06/2003 11:59 PM
Please respond to sfathallah@mail.cbi.net.ma
Sent by: nobody@groupstudy.com
To: zjxjgo, ccielab
cc:
Subject: RE: atuo-rp question
Zhou,
the problem here is that in PIM dense, sparse ou sparse-dense and for any
multicast group, if an interface exist in multicast "input list interfaces"
it can never exist in the multicast "output list interface (olist)" for the
same group. so the solution is to use differents subinterface and it may
work. don't care, I belive this scenarion can never be in LAB exam.
Said FATHALLAH.
-----Message d'origine-----
De?: nobody@groupstudy.com [mailto:nobody@groupstudy.com]De la part de zhou
jun
Envoy(&?: dimanche 11 mai 2003 02:24
($?: ccielab@groupstudy.com
Objet?: atuo-rp question
group:
I do a lab for auto-rp and sparse-dense over frame multipoint question.
according TCP/IP volume 2 ,r1,r2,r3 in same subnet,r2 is hub,r1 and r3 is
spoke ,the question is r1 and r3 cann't each other ping it's group
address,r1 and r3 can ping r2's group address.thank you for any advice!
r1:
ip multicast-routing
int lo0
ip add 10.5.1.1 255.255.255.0
int e0
ip add ...
ip pim sparse-dense
ip igmp join-group 225.1.1.1
int s0
encacp frame
frame map ip 10.5.123.2 102 broad
frame map ip 10.5.123.3 103 broad
ip add 10.5.123.1
ip ospf net point-to-multipoint
ip pim spares-dense-mode
ip pim nbma
ip pim send-rp-announce lo0 scope 5
router ospf 1
net 0.0.0.0 255.255.255.255 area 0
r2:
ip multicast-routing
int lo0
ip add 10.5.2.2 255.255.255.0
ip pim sparse-mode
int e0
ip add ...
ip pim sparse-dense
ip igmp join-group 225.2.2.2
int s0
encacp frame
frame map ip 10.5.123.1 201 broad
frame map ip 10.5.123.3 203 broad
ip add 10.5.123.2
ip ospf net point-to-multipoint
ip pim spares-dense-mode
ip pim nbma
ip pim send-rp-discovery lo0 scope 5
router ospf 1
net 0.0.0.0 255.255.255.255 area 0
r3:
ip multicast-routing
int lo0
ip add 10.5.3.3 255.255.255.0
int e0
ip add ...
ip pim sparse-dense
ip igmp join-group 225.3.3.3
int s0
encacp frame
frame map ip 10.5.123.1 301 broad
frame map ip 10.5.123.2 302 broad
ip add 10.5.123.3
ip ospf net point-to-multipoint
ip pim spares-dense-mode
ip pim nbma
ip pim send-rp-announce lo0 scope 5
router ospf 1
net 0.0.0.0 255.255.255.255 area 0
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 : Mon Jun 02 2003 - 15:13:38 GMT-3