User Manual

Insight Managed 8-Port Gigabit (Hi-Power) PoE+ Smart Cloud Switch with NETGEAR FlexPoE Power
Configure Switching User Manual167
4. Enter one of the following passwords:
• After registration, enter your customized local device password.
• If you previously added the switch to an Insight network location, enter the Insight
network password.
For more information about the local device password and the Insight network password,
see
Credentials for the local browser UI on page 28.
5. Click the Login button.
The System Information page displays.
6. Select Switching> Multicast > Auto-Video.
The Auto-Video Configuration page displays.
7. Select one of the following radio buttons:
• Select the Disable radio button to globally disable the Auto-Video mode for the
switch.
• Select the Enable radio button to globally enable the Auto-Video mode for the switch.
The Auto-Video VLAN field shows the ID for the Auto-Video VLAN. By default, the VLAN
ID is 4089.
8. Click the Apply button.
Your settings are saved.
Configure IGMP snooping
Internet Group Management Protocol (IGMP) snooping is a feature that allows a switch to
forward multicast traffic intelligently. Multicast IP traffic is traffic that is destined to a host
group. Host groups are identified by class
D IP addresses, which range from 224.0.0.0 to
239.255.255.255. Based on the IGMP query and report messages, the switch forwards traffic
only to the ports that request the multicast traffic. This prevents the switch from broadcasting
the traffic to all ports and possibly affecting network performance.
IGMP snooping overview
A traditional Ethernet network can be separated into different network segments to prevent
placing too many devices onto the same shared media. Bridges and switches connect these
segments. When a packet with a broadcast or multicast destination address is received, the
switch forwards a copy to each of the remaining network segments in accordance with the
IEEE MAC Bridge standard. Eventually, the packet is made accessible to all nodes
connected to the network.
This approach works well for broadcast packets that are intended to be seen or processed by
all connected nodes. In the case of multicast packets, however, this approach could lead to
less efficient use of network bandwidth, particularly when the packet is intended for only a
small number of nodes. Packets are flooded into network segments where no node is
receptive to the packet. While nodes rarely incur any processing overhead to filter packets