Configuring an IGMP over GRE Tunnel
The information system contains different services involving multicast packets. These services are isolated through GRE tunnels. Devices' GRE interfaces are required to have IGMP capabilities.
Context
Usage Scenario
If the information system contains two types of services involving multicast packets, for example, both the closed-circuit monitoring system and passenger information system in the urban rail signal system involve multicast packets, these services need to be isolated through GRE tunnels and the information system needs to access devices through GRE tunnels. To meet these needs, devices' GRE interfaces must have multicast capabilities. Currently, GRE interfaces support PIM. GRE interfaces must also have IGMP capabilities.
Pre-configuration Tasks
Before configuring IGMP over GRE, complete the following tasks:
Configure a unicast routing protocol to ensure that devices are reachable.
Procedure
- Run system-view
The system view is displayed.
- Run interface tunnelinterface-number
The tunnel interface view is displayed.
- Run tunnel-protocolgre
The tunnel encapsulation type is set to GRE.
- Run source ip-address
A source IP address or source interface is set for the tunnel interface.
Run the binding tunnel gre command to bind GRE to the source interface or the interface where the source address resides. After the binding, a GRE tunnel can use the interface to forward packets encapsulated by GRE.
- Run destination [ vpn-instancevpn-instance-name ] ip-address
A destination IP address is set for the tunnel interface.
After a tunnel interface is created, specify the source address or source interface and destination address of the tunnel.
- Run pim sm
PIM-SM is enabled.
Running the undo pim sm command deletes PIM neighbor relationships on the interface and interrupt the multicast service running on the interface.
- Run igmp enable
IGMP is enabled.
- Run commit
The configuration is committed.