Re: Distributing multicast groups to different RPs with AutoRP

From: jfaure@sztele.com
Date: Thu Jul 31 2003 - 13:03:14 GMT-3


Yes, i see. If you look the /n that appears in the announcement is the
number of zeros you have in the mask of the ACL:

Mask Binary /n
10------------ 00001010 6 zeros
0--------------00000000 8 zeros
16------------00010000 7 zeros

Then, this may be this the way the address ranges is determined? Anyone can
confirm & explain?
Juan Faure Ferrer
email: jfaure@sztele.com

Lmnea de Negocio de Telematica y CC
Ingeniero de Integracisn de Redes y Sistemas
----------------------------------------------------------------------------

SOLUZIONA TELECOMUNICACIONES
Servicios Profesionales de UNION FENOSA
Jerez, 3
28016 MADRID
tel 91 579 30 00 fax 91 350 72 83
---------------------------------------------------------------------------

                                                                                      
                    polarccie@yaho
                    o.co.uk Para: ccielab@groupstudy.com
                    Enviado por: cc:
                    nobody@groupst Asunto: Re: Distributing multicast groups to
                    udy.com different RPs with AutoRP
                                                                                      
                                                                                      
                    31/07/03 17:17
                    Por favor,
                    responda a
                    polarccie
                                                                                      
                                                                                      

with
access-list 33 permit 228.0.0.0 10.255.255.255
your rp announces
02:08:40: Auto-RP: Update (228.0.0.0/6, RP:192.168.3.3), PIMv2 v1
so here 229.6.6.6 is also included and you dont get
PIM-INVALID-RP-JOIN message...

with
access-list 33 permit 228.0.0.0 0.255.255.255 you get
02:10:50: Auto-RP: Update (228.0.0.0/8, RP:192.168.3.3), PIMv2 v1

access-list 33 permit 228.0.0.0 0.0.255.255
02:11:30: Auto-RP: Update (228.0.0.0/16, RP:192.168.3.3), PIMv2 v1

access-l 33 permit 228.0.0.0 1.255.255.255
02:16:40: Auto-RP: Update (228.0.0.0/7, RP:192.168.3.3), PIMv2 v1

access-l 33 permit 228.0.0.0 4.255.255.255
02:17:59: Auto-RP: Update (224.0.0.0/7, RP:192.168.3.3), PIMv2 v1

access-l 33 permit 228.0.0.0 8.255.255.255
02:21:40: Auto-RP: Update (228.0.0.0/7, RP:192.168.3.3), PIMv2 v1

access-l 33 permit 228.0.0.0 16.255.255.255
02:22:50: Auto-RP: Update (228.0.0.0/7, RP:192.168.3.3), PIMv2 v1

access-l 33 permit 228.0.0.0 9.255.255.255
02:22:50: Auto-RP: Update (228.0.0.0/6, RP:192.168.3.3), PIMv2 v1

access-l 33 permit 228.0.0.0 10.255.255.255
02:22:50: Auto-RP: Update (228.0.0.0/6, RP:192.168.3.3), PIMv2 v1

access-l 33 permit 228.0.0.0 12.255.255.255
02:22:50: Auto-RP: Update (228.0.0.0/6, RP:192.168.3.3), PIMv2 v1

i could not conclude anything with these results...
there should be sthg behind these...



This archive was generated by hypermail 2.1.4 : Wed Aug 06 2003 - 06:53:00 GMT-3