[c-nsp] Multicast over VRF possible?

[Ben Basler (bbasler)]

Jeff,

At this point multicast on VRF interfaces is only supported with Sup6-E
and 4900M.
http://www.cisco.com/en/US/docs/switches/lan/catalyst4500/12.2/52sg/conf
iguration/guide/vrf.html#wp1064137 

6500 does it on any PFC3 based sup since SXE.

Cheers,
Ben

> -----Original Message-----
> From: cisco-nsp-bounces at puck.nether.net [mailto:cisco-nsp-
> bounces at puck.nether.net] On Behalf Of Douglas C. Stephens
> Sent: Wednesday, May 27, 2009 7:48 PM
> To: Jeff Kell
> Cc: 'NSP List'
> Subject: Re: [c-nsp] Multicast over VRF possible?
> 
> Jeff,
> 
> I've successfully used "ip pim sparse-mode" on SVIs assigned to
VRF-lite
> contexts on all my 6500s.  This was on Sup720+MSFC3+PFC3B blades
running
> both ADVENTERPRISEK9_WAN-M and ADVIPSERVICESK9_WAN-M feature sets of
the
> 12.2(18)SXF release.
> 
> I've not run into this problem on my 4500 switches, but then I'm
running
> them with SupV blades, and I've not yet had much call for VRF-lite
there.
> 
> 
> 
> At 07:54 PM 5/27/2009, Jeff Kell wrote:
> >In the process of an upgrade/reconfiguration today, I discovered
> >that PIM multicast routing and VRF-lite are apparently mutually
> >exclusive on a 4506.  In this case, specifically IOS
> >cat4500-entservicesk9-mz.122-50.SG1 on a Sup-IV  WS-X4515.
> >
> >With an "ip vrf forwarding ..." directive, there is no "ip pim"
> >option available, it disappears from the configuration options.
> >
> >OK, that was the "old school" fix to make some limited multicast
> >work in this situation (Symantec Ghost for imaging remote labs).
> >
> >Is there another way to achieve routed multicasting in a VRF
> >environment?  Specifically, the imaging server resides in a "public
> >services" VRF, while the target labs are in other VRFs.
> >
> >Is this a platform-specific restriction?  Or is it
> >Catalyst-wide?  Can the 6500 handle it (on a 'ip vrf forward'ed
> >interface or SVI)?
> >
> >There are some imaging alternatives (just relocate a suitable
> >"master" copy to the local subnet), but there are some other
> >multicast "plans" on the table that aren't so easily bypassed.
> >
> >Thanks in advance,
> >
> >Jeff
> >_______________________________________________
> >cisco-nsp mailing list  cisco-nsp at puck.nether.net
> >https://puck.nether.net/mailman/listinfo/cisco-nsp
> >archive at http://puck.nether.net/pipermail/cisco-nsp/
> 
> --
> Douglas C. Stephens             | UNIX/Windows/Email Admin
> System Support Specialist       | Network/DNS Admin
> Information Systems             | Phone: (515) 294-6102
> Ames Laboratory, US DOE         | Email: stephens at ameslab.gov
> 
> _______________________________________________
> cisco-nsp mailing list  cisco-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/