From: jfaure@sztele.com
Date: Thu Jul 31 2003 - 14:49:30 GMT-3
And more:
I'm seing this feature explained on page 555 of Doyle II and i'm suspecting
that you can only include as mask of the first octect for this acl any of
these values:
1--------00000001
3--------00000011
7--------00000111
15------00001111
because the multicast range is from 224 to 239 in this octect, this is you
have the 4 most significative ever set to 1110 and the last 4 can be 0 or
1. It seems this is treated like a range.
Please, anybody with knoleadge & experience about this can confirm? If this
is so, what does the system if your access list to control the rp
announcement is the form:
access-list 33 permit 224.0.0.0 10.255.255.255 ?
Some help would be highly apreciated.
Regards
access-list
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