Re: Distributing multicast groups to different RPs with AutoRP

From: polarccie@yahoo.co.uk
Date: Thu Jul 31 2003 - 12:17:38 GMT-3


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:52:59 GMT-3