Netgear CSM4532 Product Data Sheet - Page 13

Layer 3 Multicast Features, Datacenter Features

Page 13 highlights

100GE-Enabled Managed Switches Data Sheet M4500 series VRF Lite Operation and Configuration Layer 3 Multicast Features Internet Group Management Protocol PIM Sparse Mode (PIM-SM) PIM Source Specific Multicast (PIM-SSM) PIM IPv6 MLD/MLDv2 (RFC 2710 / RFC 3810) Datacenter Features Priority-Based Flow Control Data Center Bridging Exchange Protocol CoS Queuing and Enhanced Transmission Selection VXLAN Gateway • The Virtual Routing and Forwarding feature enables a router to function as multiple routers. Each virtual router manages its own routing domain, with its own IP routes, routing interfaces, and host entries. Each virtual router makes its own routing decisions, independent of other virtual routers. More than one virtual routing table may contain a route to a given destination. The network administrator can configure a subset of the router's interfaces to be associated with each virtual router. The router routes packets according to the virtual routing table associated with the packet's ingress interface. Each interface can be associated with at most one virtual router. • The Internet Group Management Protocol (IGMP) is used by IPv4 systems (hosts and routers) to report their IP multicast group memberships to any neighboring multicast routers. The switch performs the "multicast router part" of the IGMP protocol, which means it collects the membership information needed by the active multicast router. • Protocol Independent Multicast-Sparse Mode (PIM-SM) is used to efficiently route multicast traffic to multicast groups that may span wide area networks, and where bandwidth is a constraint. PIM-SM uses shared trees by default and implements source-based trees for efficiency. This data threshold rate is used to toggle between trees. • Protocol Independent Multicast-Source Specific Multicast (PIM-SSM) is a subset of PIM-SM and is used for one-to-many multicast routing applications, such as audio or video broadcasts. PIM-SSM does not use shared trees. • PIM-SM support IPv6 routes. • MLD is used by IPv6 systems (listeners and routers) to report their IP multicast addresses memberships to any neighboring multicast routers. The implementation of MLD v2 is backward compatible with MLD v1. • MLD protocol enables the IPv6 router to discover the presence of multicast listeners, the nodes that want to receive the multicast data packets, on its directly attached interfaces. The protocol specifically discovers which multicast addresses are of interest to its neighboring nodes and provides this information to the multicast routing protocol that make the decision on the flow of the multicast data packets. • The Priority-Based Flow Control (PFC) feature allows the user to pause or inhibit transmission of individual priorities within a single physical link. By configuring PFC to pause a congested priority (priorities) independently, protocols that are highly loss sensitive can share the same link with traffic that has different loss tolerances. Priorities are differentiated by the priority field of the 802.1Q VLAN header. An interface that is configured for PFC is automatically disabled for 802.3x flow control. • The Data Center Bridging Exchange Protocol (DCBX) is used by data center bridge devices to exchange configuration information with directly-connected peers. The protocol is also used to detect misconfiguration of the peer DCBX devices and optionally, for configuration of peer DCBX devices. • The CoS Queuing feature allows the switch administrator to directly configure certain aspects of the device hardware queuing to provide the desired QoS behavior for different types of network traffic. The priority of a packet arriving at an interface can be used to steer the packet to the appropriate outbound CoS queue through a mapping table. CoS queue characteristics such as minimum guaranteed bandwidth, transmission rate shaping, etc. are user configurable at the queue (or port) level. Enhanced Transmission Selection (ETS) allows Class of Service (CoS) configuration settings to be advertised to other devices in a data center network through DCBX ETS TLVs. CoS information is exchanged with peer DCBX devices using ETS TLVs. • Logically segregated virtual networks in a data center are sometimes referred to as data center VPNs. The VXLAN Gateway is a solution that allows VXLAN to communicate with another network, particularly a VLAN. It offers VXLAN Tunnel Endpoint (VTEP) functionality for VXLAN tunnels on the switch. VXLAN is a layer-3 function, IP-based technologies that prepend an existing layer-2 frame with a new IP header, providing layer-3 based tunneling capabilities for layer-2 frames. This essentially enables a layer-2 domain to extend across a layer-3 boundary. For the traffic from a VXLAN to use services on physical devices in a distant network, the traffic must pass through a VXLAN Gateway.The VXLAN Gateway feature is configurable through the CLI. It also offers an Overlay API to facilitate programming from external agents. Page 13 of 29

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29

VRF Lite Operation and Configuration
The Virtual Routing and Forwarding feature enables a router to function as multiple routers. Each virtual
router manages its own routing domain, with its own IP routes, routing interfaces, and host entries. Each
virtual router makes its own routing decisions, independent of other virtual routers. More than one virtual
routing table may contain a route to a given destination. The network administrator can configure a subset
of the router’s interfaces to be associated with each virtual router. The router routes packets according to
the virtual routing table associated with the packet’s ingress interface. Each interface can be associated
with at most one virtual router.
Layer 3 Multicast Features
Internet Group Management Protocol
The Internet Group Management Protocol (IGMP) is used by IPv4 systems (hosts and routers) to report
their IP multicast group memberships to any neighboring multicast routers. The switch performs the
“multicast router part” of the IGMP protocol, which means it collects the membership information needed
by the active multicast router.
PIM Sparse Mode (PIM-SM)
Protocol Independent Multicast-Sparse Mode (PIM-SM) is used to efficiently route multicast traffic to
multicast groups that may span wide area networks, and where bandwidth is a constraint. PIM-SM uses
shared trees by default and implements source-based trees for efficiency. This data threshold rate is used
to toggle between trees.
PIM Source Specific Multicast (PIM-SSM)
Protocol Independent Multicast—Source Specific Multicast (PIM-SSM) is a subset of PIM-SM and is used
for one-to-many multicast routing applications, such as audio or video broadcasts. PIM-SSM does not use
shared trees.
PIM IPv6
PIM-SM support IPv6 routes.
MLD/MLDv2 (RFC 2710 / RFC 3810)
MLD is used by IPv6 systems (listeners and routers) to report their IP multicast addresses memberships
to any neighboring multicast routers. The implementation of MLD v2 is backward compatible with MLD
v1.
MLD protocol enables the IPv6 router to discover the presence of multicast listeners, the nodes that want
to receive the multicast data packets, on its directly attached interfaces. The protocol specifically discovers
which multicast addresses are of interest to its neighboring nodes and provides this information to the
multicast routing protocol that make the decision on the flow of the multicast data packets.
Datacenter Features
Priority-Based Flow Control
The Priority-Based Flow Control (PFC) feature allows the user to pause or inhibit transmission of individual
priorities within a single physical link. By configuring PFC to pause a congested priority (priorities)
independently, protocols that are highly loss sensitive can share the same link with traffic that has different
loss tolerances. Priorities are differentiated by the priority field of the 802.1Q VLAN header. An interface
that is configured for PFC is automatically disabled for 802.3x flow control.
Data Center Bridging Exchange Protocol
The Data Center Bridging Exchange Protocol (DCBX) is used by data center bridge devices to
exchange configuration information with directly-connected peers. The protocol is also used to detect
misconfiguration of the peer DCBX devices and optionally, for configuration of peer DCBX devices.
CoS Queuing and Enhanced Transmission Selection
The CoS Queuing feature allows the switch administrator to directly configure certain aspects of the
device hardware queuing to provide the desired QoS behavior for different types of network traffic. The
priority of a packet arriving at an interface can be used to steer the packet to the appropriate outbound
CoS queue through a mapping table. CoS queue characteristics such as minimum guaranteed bandwidth,
transmission rate shaping, etc. are user configurable at the queue (or port) level. Enhanced Transmission
Selection (ETS) allows Class of Service (CoS) configuration settings to be advertised to other devices in a
data center network through DCBX ETS TLVs. CoS information is exchanged with peer DCBX devices using
ETS TLVs.
VXLAN Gateway
Logically segregated virtual networks in a data center are sometimes referred to as data center VPNs.
The VXLAN Gateway is a solution that allows VXLAN to communicate with another network, particularly
a VLAN. It offers VXLAN Tunnel Endpoint (VTEP) functionality for VXLAN tunnels on the switch. VXLAN
is a layer-3 function, IP-based technologies that prepend an existing layer-2 frame with a new IP header,
providing layer-3 based tunneling capabilities for layer-2 frames. This essentially enables a layer-2 domain
to extend across a layer-3 boundary. For the traffic from a VXLAN to use services on physical devices
in a distant network, the traffic must pass through a VXLAN Gateway.The VXLAN Gateway feature
is configurable through the CLI. It also offers an Overlay API to facilitate programming from external
agents.
100GE-Enabled Managed Switches
Data Sheet
M4500 series
Page 13 of 29