" Unlike the ip igmp static interface command, when a router issues an IGMP ?join?, the CPU must actually process the multicast group. Therefore, a router configured with an IGMP join statement will respond to ICMP echo requests sent to the group that is has joined. In order to prevent looping of multicast feeds the router performs a reverse-path ".
What is the difference between the ip igmp join-group and the ip igmp static-group?
The join-group command forces the router to respond as a host on its own interface. This is processswitched. The static-group command causes the router to put the interface permanently in the OIF (output interface) list. This is not process-switched.
Informs the router to join group on the interface. IP packets that are addressed to this group address will be passed up to the IP client process in the router as well forwarded out the interface. If you do not want packets forwarded out the interface, join the group on a loopback interface. Packets are not sent on the loopback interface.
ip igmp static-group
Configures a static connected member for the group on the interface. Packets to the group will get fastswitched, unlike the ?ip igmp join-group? command. If ?ip igmp join-group? command is used for the same group address, it will take precedence and the group will behave like a locally joined group.
When the Cisco configuration command "ip igmp static-group" is used to force a router interface to join a multicast group, that self-subscription of the router is not reflected properly in the IGMP MIB.
A workaround is to use the command "ip igmp join-group", which properly shows self-subscription in the IGMP MIB
This command (ip igmp static-group) enrolls the router in the multicast group specified by the group-address. Unlike the ip igmp join-group command, this command allows packets to the group to be fast-switched out the interface
1- Is the processswitch same as fastswitched ?
2- Is quote #2 authenticated ?
3- I could not find where it has been mentioned that :"the static as the router would not respond"
.Use the ip igmp join-group interface configuration command. With this method, the router accepts the multicast packets in addition to forwarding them. Accepting the multicast packets prevents the router from fast switching.
?Use the ip igmp static-group interface configuration command. With this method, the router does not accept the packets itself, but only forwards them. Hence, this method allows fast switching. The outgoing interface appears in the IGMP cache, but the router itself is not a member, as evidenced by lack of an "L" (local) flag in the multicast route entry.
>>3- I could not find where it has been mentioned that :"the static as the router would not respond"<<
Question We run asr9001 with XR 6.1.3, and we have a very long delay to
login w/ SSH 1 or 2 to the device compare to IOS device. After
investigation, the there is 1s delay between the client KEXDH_INIT and
the server (XR) KEXDH_REPLY. After debug ssh serv...
Introduction The purpose of this document is to demonstrate the Open
Shortest Path First (OSPF) behavior when the V-bit (Virtual-link bit) is
present in a non-backbone area. The V-bit is signaled in Type-1 LSA only
if the router is the endpoint of one or ...
Hi, I am seeing quite a few issues with patch install and wanted to
share my experience and workaround to this. Login to admin via CLI, then
access root with the “shell” command Issue “df –h” and you’ll probably
see the following directory full or nearly ...