Configuring the Device as a Statically Connected Member (CLI)
At various times, either there is not a group member on a network segment or a host that cannot report its
group membership by using IGMP. However, you may want multicast traffic to be sent to that network
segment. The following commands are used to pull multicast traffic down to a network segment:
• ip igmp join-group—The device accepts the multicast packets in addition to forwarding them. Accepting
the multicast packets prevents the device from fast switching.
• ip igmp static-group—The device does not accept the packets itself, but only forwards them. This
method enables fast switching. The outgoing interface appears in the IGMP cache, but the device itself
is not a member, as evidenced by lack of an L (local) flag in the multicast route entry.
This procedure is optional.
SUMMARY STEPS
1.
enable
2.
configure terminal
3.
interface interface-id
4.
ip igmp static-group group-address
5.
end
6.
show ip igmp interface [interface-id]
7.
copy running-config startup-config
DETAILED STEPS
PurposeCommand or Action
Enables privileged EXEC mode.enable
Step 1
Example:
Device> enable
•
Enter your password if prompted.
Enters the global configuration mode.configure terminal
Example:
Device# configure terminal
Step 2
Specifies the Layer 3 interface on which you want to enable multicast
routing, and enters interface configuration mode.
interface interface-id
Example:
Device(config)# interface
Step 3
The specified interface must be one of the following:
• A routed port—A physical port that has been configured as a Layer
3 port by entering the no switchport interface configuration command.
gigabitethernet 1/0/1
You will also need to enable IP PIM sparse-dense-mode on the
interface, and join the interface as a statically connected member to
IP Multicast Routing Configuration Guide, Cisco IOS XE Release 3SE (Catalyst 3650 Switches)
44 OL-29890-01
Configuring IGMP
Configuring the Device as a Statically Connected Member (CLI)
To Next Page
Loading...
Need help?
General