The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
This document describes the procedure required to configure multicast within Unified Computing Systems (UCS). Multicast (MCAST) is the ability to send data across a network to multiple users at the same time (one-to-many or many-many group communication). Internet Group Management Protocol (IGMP) is a crucial component of Multicast. The Primary purpose of IGMP is to permit hosts to communicate their desire to receive multicast traffic, to the IP Multicast router(s) on the local network. This in return, permits the IP Multicast router(s) to “Join” the specified multicast group and to begin to forward the multicast traffic onto the network segment towards the host.
Cisco recommends that you have knowledge of these topics:
The information in this document is based on these software and hardware versions:
The information in this document was created from the devices in a specific lab environment. All of the devices used in this document started with a cleared (default) configuration. If your network is live, ensure that you understand the potential impact of any command.
Prior to Unified Computing System Manager (UCS-M) Version 2.1:
Del Mar 2.1 Notes:
Fabric Interconnect Specifics:
Approved Configurations:
Either configure IGMP querier on the upstream switch with IGMP snooping enabled or Disable IGMP snooping on the upstream switch to flood multicast traffic. Alternatively, change the FIs to switch mode.
Approved Configurations:
The upstream switch can have IGMP snooping enabled or have it disabled on the upstream switch to flood multicast traffic.
IGMP snooping is available on a VLAN basis and not on the interface level. From UCSM, this can be configured with a Multicast Policy on a named VLAN.
1. Add a new Multicast Policies node under LAN> LAN > Policies> root.
2. There is support for the creation, modification, and deletion of Multicast Policies.
3. There is an option for selecting existing Multicast Policy when a VLAN is created.
4. And support for attaching an existing Multicast Policy with a VLAN that is already created.
Note: Multicast Policies are only under the root policies tree and you cannot create individual policies under a sub-organization.
Default Multicast Policy keeps in line with Fabric Interconnect behavior prior to 2.1 Del Mar release:
IGMP Snooping- Enabled
IGMP Querier- Disabled
Step 1. Add a new Multicast Policies node under LAN > LAN > Policies > root.
Step 2. Right Click on Multicast Policies, then Create Multicast Policy.
Step 3. You are then presented with this:
Provide a Name and configure the IGMP Snooping and Snooping Querier states.
Step 4. If you attempt to disable IGMP Snooping while the IGMP Snooping Querier is enabled, this throws an error, as this isn’t a valid configuration.
Step 5. During the creation of a new VLAN, now there is an e option to specify Multicast Policy Name.
Examples with different policies set on the VLAN. Multicast Policy Name is what you configure where Multicast Policy Instance is actually being used by the Fabric Interconnects.
If you create multiple VLAN objects, which point to the same VLAN ID, then, when you apply a Multicast policy, it is applied to all VLAN objects with the same VLAN ID. The latest Multicast Policy applied is applied to all. Eg: QMulticast changed to Snoop_off_qu_off (Vlan 38).
MiniMe-B# scope org
MiniMe-B /org # create mcast-policy <name>
MiniMe-B /org/mcast-policy #set querier <enable/disable>
MiniMe-B /org/mcast-policy #set snooping <enable/disable>
MiniMe-B # scope org
MiniMe-B /org # show mcast-policy
MiniMe-B # scope org
MiniMe-B /org # delete mcast-policy <name>
MiniMe-B# scope eth-uplink
MiniMe-B /eth-uplink # scope vlan <vlan>
MiniMe-B /eth-uplink/vlan # set mcastpolicy <name>
AGR012-5K-A(config)# vlan 38
AGR012-5K-A(config-vlan)# vlan configuration 38
AGR012-5K-A(config-vlan-config)# ip igmp snooping querier 172.16.38.124( IP is likely to be different)
(UCS snooping command output for VLAN 38 verifies that the querier is configured on the UCSM and the N5k, and it shows that only the querier on the N5k is currently active (as expected). While VLAN 39 is not configured.
Legend: - primary entry, G - Gateway MAC, (R) - Routed MAC, O - Overlay MAC age - seconds since last seen,+ - primary entry using vPC Peer-Link VLAN MAC Address Type age Secure NTFY Ports ---------+-----------------+--------+---------+------+----+------------------ 38 0100.5e10.2604 igmp 0 F F Eth1/2 Router 38 0100.5e7f.fffd igmp 0 F F Eth1/2 Router 0100.5e7f.2604 = 224.127.38.4 (Multicast Group Address) 0100.5e7f.fffd = 224.127.255.253 (Multicast Group Address)
This does not capture actual video stream data, just IGMP data. This tool captures control traffic. (EX; it shows when a host joins or leaves the group.)
Capturing on inband 2009-12-02 02:11:34.435559 172.16.38.5 -> 224.0.0.22 IGMP V3 Membership Report / Join group 224.0.0.252 for any sources 2009-12-02 02:11:55.416507 172.16.38.6 -> 224.0.0.22 IGMP V3 Membership Report / Leave group 236.16.38.4 2009-12-02 02:11:55.802408 172.16.38.6 -> 224.0.0.22 IGMP V3 Membership Report / Leave group 236.16.38.4 2009-12-02 02:11:59.378576 172.16.38.6 -> 224.0.0.22 IGMP V3 Membership Report / Join group 236.16.38.4 for any sources
(Here are the images that show how to stream on VLC. There is quite a bit of information regarding how to do this process online.)
Multicast sender CLI.
# iperf -c 239.1.1.1 -i 1 -u -t 600 -b 10M iperf sender options: -c 239.1.1.1 : send traffic to multicast IP address 239.1.1.1 -i 1 : update interval is 1 second -u : UDP traffic, multicast is based on UDP -t 600 : send traffic for 600 seconds -b 10M: UDP traffic bandwidth is10Mbps
Multicast receiver CLI.
# iperf -s -B 239.1.1.1 -i 1 -u iperf receiver options: -s : server mode -B 239.1.1.1 : listening to IP address 239.1.1.1, as it is a multicast IP address, so this is a multicast receiver. -i 1 : update interval is 1 second -u : UDP traffic, multicast is based on UDP