Netgear XSM4348CS Product Data Sheet - Page 9

ProSAFE® Intelligent Edge Managed Switches Data Sheet M4300 series Distance Vector Multicast Routing Protocol (DVMRP) is a dense mode multicast protocol also called Broadcast and Prune Multicasting protocol • DVMRP uses a distributed routing algorithm to build per-source-group multicast trees • DVMRP assumes that all hosts are part of a multicast group until it is informed of multicast group changes • It dynamically generates per-source-group multicast trees using Reverse Path Multicasting • Trees are calculated and updated dynamically to track membership of individual groups Multicast routing (PIM-SM and PIM-DM, both IPv4 and IPv6) ensure multicast streams can reach receivers in different L3 subnets • Multicast static routes allowed in Reverse Path Forwarding (RPF) selection • Multicast dynamic routing (PIM associated with OSPF) including PIM multi-hop RP support for routing around damage advanced capabilities • Full support of PIM (S,G,Rpt) state machine events as described in RFC 4601 • Improved Multicast PIM timer accuracy with hardware abstraction layer (HAPI) polling hit status for multicast entries in real time (without caching) PoE power management and schedule enablement Power redundancy for higher availability when mission critical convergent installation, including hot-swap main PSU replacement without interruption Layer 3 routing package Static Routes/ECMP Static Routes for IPv4 and IPv6 • Static and default routes are configurable with next IP address hops to any given destination • Permitting additional routes creates several options for the network administrator • The admin can configure multiple next hops to a given destination, intending for the router to load share across the next hops • The admin distinguishes static routes by specifying a route preference value: a lower preference value is a more preferred static route • A less preferred static route is used if the more preferred static route is unusable (down link, or next hop cannot be resolved to a MAC address) • Preference option allows admin to control the preference of individual static routes relative to routes learned from other sources (such as OSPF) since a static route will be preferred over a dynamic route when routes from different sources have the same preference Advanced Static Routing functions for administrative traffic control • Static Reject Routes are configurable to control the traffic destined to a particular network so that it is not forwarded through the router • Such traffic is discarded and the ICMP destination unreachable message is sent back to the source • Static reject routes can be typically used to prevent routing loops • Default routes are configurable as a preference option In order to facilitate VLAN creation and VLAN routing using Web GUI, a VLAN Routing Wizard offers following automated capabilities: • Create a VLAN and generate a unique name for VLAN • Add selected ports to the newly created VLAN and remove selected ports from the default VLAN • Create a LAG, add selected ports to a LAG, then add this LAG to the newly created VLAN • Enable tagging on selected ports if the port is in another VLAN • Disable tagging if a selected port does not exist in another VLAN • Exclude ports that are not selected from the VLAN • Enable routing on the VLAN using the IP address and subnet mask entered as logical routing interface DHCP Relay Agents relay DHCP requests from any routed interface, including VLANs, when DHCP server doesn't reside on the same IP network or subnet • The agent relays requests from a subnet without a DHCP server to a server or next-hop agent on another subnet • Unlike a router which switches IP packets transparently, a DHCP relay agent processes DHCP messages and generates new DHCP messages • Supports DHCP Relay Option 82 circuit-id and remote-id for VLANs • Multiple Helper IPs feature allows to configure a DHCP relay agent with multiple DHCP server addresses per routing interface and to use different server addresses for client packets arriving on different interfaces on the relay agent server addresses for client packets arriving on different interfaces on the relay agent Page 9 of 49