Hello, everyone.
I am sligthly confused by these two sections:
Why is the term “L3-aware ASIC” specifically mentioned here? L3 means that the ASIC can also make routing decisions, correct? However, after viewing these two sections, I don’t see any routing mentioned at all, so what does the term “L3-aware ASIC” have to do with IGMP Snooping in this case? Regardless of whether the ASIC supports only L2 or both L2 and L3, it shouldn’t make much of a difference here if the switch isn’t going to perform routing, or?
One more thing. This explanation here (The first section)
From how I understand this, everything is being sent to the CPU and the CPU is being overloaded, and cannot handle all the multicast traffic, so it might drop some. This is normal since process-switching is way slower than hardware switching by using ASICs.
In the next section with an ASIC, my understanding is that IGMP traffic is sent to the control plane, to the CPU for processing. However, multicast traffic for the specific groups is forwarded by using an ASIC, correct?
So what’s up with the MAC address table? I don’t think I quite understand what it says.
Anything you learn via IGMP Snooping is represented by the specific entry - 0100:5e01:0101 in this case, right?
So if traffic is destined for that multicast group that the switch learned about, it will only forward it out of the ports with the interested listeners. However, why is it classified as “non-IGMP”? The hosts can still send IGMP traffic (membership reports) to their own multicast group and that will be matched by the second entry in the CAM table. So this isn’t exactly “non-IGMP”, or is it?
Thank you.
David