Supported Pim Modes And Features - Lenovo ThinkSystem NE2552E Application Manual

Supported PIM Modes and Features

420
NE2552E Application Guide for ENOS 8.4
Receiver join requests as well as sender multicast content initially converge at the
RP, which generates and distributes multicast routing data for the DRs along the
delivery path. As the multicast content flows, DRs use the routing tree information
obtained from the RP to optimize the paths both to and from send and receive
stations, bypassing the RP for the remainder of content transactions if a more
efficient route is available.
DRs continue to share routing information with the RP, modifying the multicast
routing tree when new receivers join, or pruning the tree when all the receivers in
any particular domain are no longer part of the multicast group.
For each interface attached to a PIM network component, PIM can be configured to
operate either in PIM Sparse Mode (PIM‐SM) or PIM Dense Mode (PIM‐DM).
 PIM‐SM is used in networks where multicast senders and receivers comprise a
relatively small (sparse) portion of the overall network. PIM‐SM uses a more
complex process than PIM‐DM for collecting and optimizing multicast routes,
but minimizes impact on other IP services and is more commonly used.
 PIM‐DM is used where multicast devices are a relatively large (dense) portion of
the network, with very frequent (or constant) multicast traffic. PIM‐DM requires
less configuration on the switch than PIM‐SM, but uses broadcasts that can
consume more bandwidth in establishing and optimizing routes.
The following PIM modes and features are not currently supported in Lenovo
ENOS 8.4:
Hybrid Sparse‐Dense Mode (PIM‐SM/DM). Sparse Mode and Dense Mode may

be configured on separate IP interfaces on the switch, but are not currently
supported simultaneously on the same IP interface.
 PIM Source‐Specific Multicast (PIM‐SSM)
 Anycast RP
 PIM RP filters
 Only configuration via the switch ISCLI is supported. PIM configuration is
currently not available using the menu‐based CLI, the BBI, or via SNMP.