Hi Kevin,   The receivers are the only ones that will send an IGMP membership report, the source on the other side will just start sending the multicast traffic into the network and in case it needs to be routed the First Hop Router (FHR) or in other words the gateway of the source will register this multicast source with another entity which is the Rendezvous Point (RP).   When the multicast traffic enters the switch it will replicate the packets and will forward them within that same VLAN, given that you have IGMP Snooping enabled the packets should be forwarded onto the ports where the receivers are connected.   With IGMPv2 I believe there is no command to see the source of the multicast traffic as IGMP does not need to register it, only if you were running PIM within the multicast network a source and group entry (S,G) will be created in the "show ip mroute" table and that's where you will see the source registered.   HTH ... View more

Hi peterwarwick, Netflow on your platform is supported only on IP Base and Enterprise Services license, please see the following release notes as a reference: http://www.cisco.com/c/en/us/td/docs/switches/lan/catalyst4500/release/note/ol-37xe-4500e.html#pgfId-1298539 HTH ... View more

Hi aamirkiani, Unfortunately you cannot assign an IP address to that interface. ASR901 supports SVIs for routing, so you can configure an interface vlan and then assign an IP address. http://www.cisco.com/c/en/us/td/docs/wireless/asr_901/Configuration/Guide/b_asr901-scg/b_asr901-scg_chapter_010010.html HTH ... View more

Hi Kurt, That will not cause the stack to fail, you just need to make sure that the IOS version and the license level are the same between the stack members and make sure to power down the new switch before connecting it into the stack. HTH Julio ... View more

Hi Marc, Even if Gi1/0/41 is an access port it can generate a TCN if there is change in its forwarding state. It would be important to check what is connected to the port, perhaps it is just an end host disconnecting its pc from the network.  If these ports are destined only for your end users, you can enable the "portfast" feature on them in order to prevent the TCNs to be constantly generated when a user connects/disonnects its pc. Here is a very useful link which explains in more detail this behavior: http://www.cisco.com/c/en/us/support/docs/lan-switching/spanning-tree-protocol/12013-17.html#anc12 HTH Julio ... View more

Hi Phil, Here is some feedback regarding your queries.  At the Layer 2 side IGMP is responsible for registering the Multicast Receivers (hosts) in a multicast group. IGMP Snooping on the other hand is just a feature that will prevent the multicast packets to be forwarded over all the ports on a LAN segment, this feature helps to prevent the waste of resources by only sending the traffic to those specific hosts requesting the multicast feed. (These are included on your IP base license) Now, f you're planning to have the Multicast Source and Multicast Receivers at different VLANs then you need to enable PIM. Within your license only PIM stub routing is available, meaning that you will only be able to configure PIM passive on the SVI interfaces and full PIM on the routed uplinks. You should be able to configure PIM sparse mode on the uplinks between your stacks and PIM passive on the SVis where the source and receivers will be connected. The below links might be useful: http://www.cisco.com/c/en/us/td/docs/ios/solutions_docs/ip_multicast/White_papers/mcst_ovr.html#wp1012495 http://www.cisco.com/c/en/us/support/docs/switches/catalyst-3750-series-switches/98289-pim-stub.html http://www.cisco.com/c/en/us/td/docs/switches/lan/catalyst3750x_3560x/software/release/12-2_53_se/configuration/guide/3750xscg/swmcast.html HTH, Julio ... View more