This is lab environment, I'm just testing basic multicast features with nexus.
The command reference says the following: "When you enter this command, the traffic generated is handled by the device CPU, not the hardware." http://www.cisco.com/en/US/docs/switches/datacenter/sw/5_x/nx-os/multicast/c ommand/reference/mcr_cmds_i.html#wp1230243 The "ip igmp static-group" was replaced by the command: ip igmp static-oif http://www.cisco.com/en/US/docs/switches/datacenter/sw/5_x/nx-os/multicast/c ommand/reference/mcr_cmds_i.html#wp1034808 When I have the igmp joing on the physical interface, the (*,G) entry is created then it disappears. But I see the (*,G) entry on the RP and I verified that the traffic is actually sent to the nexus. Thanks. Regards, Antonio Soares, CCIE #18473 (R&S/SP) [email protected] http://www.ccie18473.net -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Phil Mayers Sent: sábado, 1 de Outubro de 2011 10:49 To: [email protected] Subject: Re: [c-nsp] Nexus 7K - Multicast Question On 10/01/2011 01:31 AM, Antonio Soares wrote: > Hello group, > > Anyone knows why the "ip igmp join-group" does not work on a physical > interface but it works fine on a loopback interface ? "ip igmp join-group" is a CPU command; it makes the CPU join the group and receive the packets. I imagine this might not work on a hardware platform, with an interface which will be processed in hardware. Are you sure you don't want "ip igmp static-group"? What's your use case? _______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/ _______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
