I have a multicast server cluster in a VLAN behind a pair of 6509s with MSFC2s. The pair of MSFCs is running HSRP. The default gateway for the mcast cluster controller is the HSRP address. Everything works fine. It dawned on me today that I might be able to reference the HSRP address as the RP on all other routers that will be sending mcast joins. As it is now, for test and turn-up, I have a only two audio/video pairs being sourced by VCRs which are attached to mcast servers. So I have:
'ip pim rp-address a.b.c.d 1' 'ip pim rp-address e.f.g.h 2' 'access-list 1 permit 239.1.1.1' 'access-list 1 permit 239.1.1.2' 'access-list 2 permit 239.1.2.1' 'access-list 2 permit 239.1.2.2' where a.b.c.d and e.f.g.h are loopback addresses of the two HSRP-speaking routers. The first access list specifies that one audio/video pair have router A as an RP and the other pair the router B as an RP. Not very scalable for the long term. I initially though about splitting the 239.0.0.0 network between the two RPs. That would be psuedo load balancing. However, I don't seem to be able to influence how the cluster controller assigns mcast IPs (nor do I want the administrator that this will ultimately be turned over to to have to statically assign mcast IPs to every channel's audio and video). I can only specify a range (e.g. 239.0.0.0 - 239.255.255.255) from which the cluster controller randomly (apparently) grabs addresses. So the audio and video might end up in different halves of the 239.0.0.0 network, making the RP different between the two. Not really a big deal, but not really clean either. So what if I: 'ip pim rp-address i.j.k.l' where i.j.k.l is the HSRP virtual IP? Will it work or will it break? I can't get to the client site until next week to find out for myself. What do ya'll think? Thanks much and happy weekend! Scott Message Posted at: http://www.groupstudy.com/form/read.php?f=7&i=62289&t=62289 -------------------------------------------------- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]