IGMP settings on S series switch

25

When multiple switches connect to the same subnet, the requirements on IGMP settings on interfaces are as follows:
Ensure that IGMP parameters configured on the interfaces on the same subnet are consistent.
These IGMP parameters affect each other. If IGMP parameters configured on the interfaces on a subnet are inconsistent, the IGMP member relationships are unordered.
Checking method: Run the display igmp interface interface-type interface-number verbose command on all the devices on a subnet to check IGMP parameters. If the IGMP parameter configurations are inconsistent, modify the configurations. IGMP parameters:
- IGMP version
- Robustness
- Query interval
- Other querier timeout
- Maximum query response time
- Last member query count
- Last member query interval
- Startup query interval
- Startup query count

Other related questions:
IGMP snooping parameters of an S series switch
The following IGMP snooping parameters are provided: - Query-interval: specifies the interval for sending General Query messages. The system starts an aging timer for a member port when the port receives a Report message. The aging time is calculated using the following formula: Aging time = Robust variable x Query interval + Maximum response time for General Query messages On the S series modular switch, the default value is 60s. On S and E series fixed switches excluding the S1700, the default value is 125s. - Max-response-time: specifies the maximum response time for a Query message. After receiving a Query message, a device must send a response message within the specified time. The device may send the Report message at any time before the maximum response time expires. The default interval is 10s. - Robust-count: specifies the IGMP robustness variable. This parameter is set based on the link performance. If a link is unstable and many packets are discarded, increase the robustness variable. The default robustness variable is 2. - Last-member-query-interval: specifies the interval for sending Last Member Query messages. In IGMPv2 and IGMPv3, the system starts an aging timer for a member port when the port receives a Leave message. The aging time is calculated using the following formula: Aging time = Robust variable x Interval for sending Last Member Query messages The default interval is 1s. If the IGMP snooping querier is not configured, the parameter is used to calculate the aging time of member ports. - After a member port receives a Report message from the downstream host, the aging time is as follows: Aging time = Robust variable x Query interval + Maximum response time for General Query messages - After a member port receives a Leave message from the downstream host, the aging time is as follows: Aging time = Robust variable x Interval for sending Last Member Query messages Run the display igmp-snooping command to check parameter settings on an S series switch excluding the S1700.

How IGMP messages are transparently transmitted on an S series switch enabled with IGMP snooping
After global IGMP snooping is enabled on a switch, the switch sends all the IGMP messages received from a VLAN to the CPU for processing. If the multicast service is not configured in a VLAN and the switch needs to directly forward the IGMP messages of this VLAN without sending them to the CPU, run the protocol-transparent command in the VLAN view to enable transparent transmission of protocol packets. S series fixed switches support transparent transmission of protocol packets starting from V200R001, and only the S3700HI, S5710EI, S5720EI, S5700HI, S5710HI, S5720HI, S6700EI, andS6720EI support this function. S series modular switches support this function.

What is the difference between IGMP versions of S series switches
IGMP runs on the last-hop router to collect users' requests for programs. The requested multicast data is then sent from the multicast source to users through PIM. IGMP has three versions. 1. IGMPv1 IGMPv1 defines the General Query message and Report message. A user sends Report message to request a program. After the last-hop router receives the Report message, it adds the user to the specified multicast group and sends General Query messages at intervals to maintain the membership of the user. If the router does not receive any Report message from the user within two intervals, it considers that the user does not require the multicast data and deletes the user from the multicast group. 2. IGMPv2 In IGMPv1, if a user does not require data of a multicast group, it leaves the multicast group after two intervals for sending General Query messages. Multicast data is still sent to the user in this period, wasting bandwidth. IGMPv2 improves IGMPv1 by adding two types of messages: Leave message and Special Query message. When a user does not require data of a multicast group, the user sends a Leave message to the last-hop router. When a port of the router receives the Leave message, the router sends some Group-Specific Query messages (the quantity is specified by the robustness variable) to the interface to check whether other users in the broadcast domain on the interface require data of the multicast group. If another user requires data of the multicast group, the user replies with a Report message. When receiving the Report message, the router retains the interface. If no Report message is received, the router deletes the interface from the multicast forwarding entry. IGMPv2 is the most widely used one on networks. 3. IGMPv3 IGMPv1 and IGMPv2 messages contain only the multicast group addresses of the requested programs. If multiple multicast sources provide data with the same multicast group address, data of all the groups is transmitted to users. Users may not see the programs they request. IGMPv3 solves this problem. IGMPv3 adds a source list in the Report message and supports the following six types of source lists: -Include: accepts data provided by the multicast sources in the list. -Exclude: rejects the multicast group data provided by all sources in the list. -ChangeToInclude: starts to accept multicast group data provided by the multicast sources in the list (previously rejects the data). -ChangeToExclude: starts to reject multicast group data provided by the multicast sources in the list (previously accepts the data). -AllowNew: adds a source of which the data is accepted or rejected. -BlockOld: deletes previous sources of which the data is accepted or rejected. IGMPv3 replaces the Leave message with the Rep ort message and adds the Group-and-Source-Specific Query message.

How does an S series switch elect an IGMP querier
When a host subnet is connected to the interfaces on multiple devices, to avoid data conflict, only one interface is allowed to send Query messages. This interface is the querier. The other interfaces running IGMP can receive the IGMP messages in this subnet. In IGMPv1, the querier is elected by a multicast routing protocol such as PIM. In IGMPv2 and IGMPv3, the switch interface with the lowest IP address acts as the querier.

If you have more questions, you can seek help from following ways:
To iKnow To Live Chat
Scroll to top