User Manual

Protocol Independent Multicast (PIM)
284 Enterasys X-Pedition User Reference Manual
Reconfiguration
This release does not support the use of GenIDs, a mechanism used to let neighboring routers know
that the router rebooted. Upon receiving a new GenID, a router should retransmit certain
information related to its current state and RP-set. Future releases will support GenID.
Static RPs
Using static RPs can simplify the convergence of a PIM-SM domain by eliminating the need for
BSR support; however, static RPs are difficult to maintain in a large domains and are similar to
static routes in advantages and limitations.
Examples
Every PIM-SM enabled network needs to know which routers are selected as the RP and RP
candidates for the network. This information is distributed through configuration (static RPs) or via
a Bootstrap Router (BSR) mechanism. PIM-SM uses the underlying Unicast routing protocol to
determine the best path back to the RP or to the source.
Configuration
Before configuring PIM-SM on your network, you will need to create a sparse component for each
router on which PIM-SM will be enabled. The sparse component allows the router to combine all
PIM-SM configuration commands and place them together at a single location. To create a sparse
component, use the pim sparse create component <name> command. With the sparse component
created, you may add interfaces to the component to indicate to the router the interfaces on which
PIM-SM will be enabled. To add interfaces to the sparse component, use the pim sparse add
interface <name> to-component <component> command where <component> is the name used
in the create component command.
If the router on which you configure PIM-SM will act as a candidate RP or candidate BSR, you
must enable this capability with the pim sparse set component <component> crp-on or pim
sparse set component <component> bsr-on command. Once the configuration is complete, enter
the pim global start command to begin running the protocol.
Note: Clients connected directly to the router must run IGMP in order to request multicast
traffic. However, the IGMP configuration options in the configuration are used for
DVMRP only and will not work for PIM-SM—all PIM IGMP configuration must use the
pim igmp commands.
To configure PIM IGMP on a specific interface(s), use the pim igmp enable interface <name>
command. After configuring the interface(s), enter the pim igmp global start command from the
CLI to launch IGMP.