PIM-SM (Sparse Mode) > Configuration steps for PIM-SM

  

 next

Configuration steps for PIM-SM

This process assumes that the necessary VLANs and IP addressing have already been configured on the routing switch.
[NOTE: ]

NOTE: The switches described in this guide do not support PMBR operation in the current software release.

Planning considerations

  • Where multiple routers are available to operate as the DR for a given source, set the DR priority on each router according to how you want the router used.

  • Determine whether there are any bandwidth considerations that would call for disabling SPT operation. (If any routers in the domain have SPT operation disabled, it should be disabled on all RPs in the domain. See Operating rules for static RPs.)

  • Determine the routers to configure as C-BSRs. In many applications, the best choice may be to configure all routers in the domain as candidates for this function.

  • Determine the multicast group support you want on each C-RP and any static RPs in the domain. The easiest option is to enable C-RP to support all possible multicast groups on all routers in the domain. However, if there are traffic control considerations you want to apply, you can limit specific multicast groups to specific routers and/or set priorities so that default traffic routes support optimum bandwidth usage.

Per-router global configuration context

Use these steps to enable routing and PIM operation in the global configuration context of each PIM-SM router (HP(config)#_):

  1. Enable routing. (Use ip routing.)

  2. Enable multicast routing. (Use ip multicast-routing.)

  3. Enable PIM. (Use router pim.)

  4. Configure the routing method(s) needed to reach the interfaces (VLANs) on which you want multicast traffic available for multicast receivers in your network:

    • Enable RIP or OSPF. (Use routerrip|ospf )

    • If desired, configure static routes to the destination subnets. (Use ip route dest-ip-address/mask-bits next-hop-ip-addr.)

Per-VLAN PIM-SM configuration

These steps configure PIM-SM in the VLAN interface context for each VLAN configured on the router (HP Switch(vlan-vid)#_).

  1. Enable IGMP. (Use ip igmp.) Repeat this action on every router (and switch) having membership in the VLAN.

  2. For both the global and VLAN levels on the routers where there are connected multicast receivers that may issue joins or send multicast traffic, use the same routing method as Step 4 of this procedure.

  3. Enable PIM-SM on the VLAN interfaces where you want to allow routed multicast traffic. (Default: disabled)

    1. If these VLANs do not already have static IP addresses, then statically configure one or more IP addresses on each VLAN you want to support PIM-SM operation. (PIM-SM cannot be enabled on a VLAN that does not have a statically configured IP address. That is, PIM-SM cannot use an IP address acquired by DHCP/Bootp.)

    2. Use ip pim-sparse to enter the VLAN's pim-sparse context and do one of the following:

      • Enable PIM-SM on the VLAN and allow the default option (any) to dynamically determine the source IP address for the PIM-SM packets sent from this VLAN interface.

      • Enable PIM-SM on the VLAN and allow the default option (any) to dynamically determine the source IP address for the PIM-SM packets sent from this VLAN interface.

      • Enable PIM-SM on the VLAN and specify an IP address for the PIM-SM packets sent from this VLAN interface. (The specified IP address must already be statically configured on the VLAN.)
      [NOTE: ]

      NOTE: This step requires enabling Router PIM on the global configuration context. See Configuring global context commands.

    3. Option: Change the current DR priority, in the PIM Sparse context, to a value for the current router in the current VLAN by using Command dr-priority [0-4294967295].

      (DR Priority default = 1)
    [NOTE: ]

    NOTE: When you initially enable PIM-SM, Hewlett Packard Enterprise recommends that you leave the PIM-SM traffic control settings at their default settings. You can then assess performance and make configuration changes when needed.

  4. Option: Change one or more of the traffic control settings for the pim-sparse of a given VLAN on which PIM-SM is enabled. (Note that some VLAN context control settings apply to both PIM-SM and PIM-DM).

    Features accessed in VLAN- vid -pim-sparse context Operation
    ip-addr Sets or resets the source IP address for PIM-SM packets sent out on the interface. Also enables PIM-SM on the interface. (Default: any)
    hello-interval [a] Resets the interval between transmitted PIM Hello packets on the interface. (Default: 30 seconds)
    hello-delay [a] Resets the maximum delay for transmitting a triggered PIM Hello packet on the interface. (Default: 5 seconds)
    lan-prune-delay [a] Enables or disables the LAN prune delay feature on the interface. (Default: on)
    override-interval [a] Resets the override interval of the LAN prune delay configured on the interface. (Default: 2500 milliseconds)
    propagation-delay[a] Resets the delay interval for triggering LAN prune delay packets on the interface. (Default: 500 milliseconds)
    dr-priority Resets the priority of the interface in the Designated Router election process. (Default: 1)

    If you want one router on a given VLAN to have a higher priority for DR than other routers on the same VLAN, use the dr-priority command to reconfigure the DR priority setting as needed. Otherwise, the highest DR priority among multiple routers on the same VLAN interface is assigned to the router having the highest source IP address for PIM-SM packets on that interface.

    [a] Applies to both PIM-SM and PIM-DM operations.

Router Pim configuration

These steps configure the PIM-SM in the Router PIM context (HP Switch (pim)#_).

  1. Specify the VLAN interface to advertise as the BSR Candidate and enable the router to advertise itself as a candidate BSR in a PIM-SM domain. (Use bsr-candidate source-ip-vlan vid.)

  2. Option: To make NSR candidate selection occur quickly and predictably, set a different priority on each BSR candidate in the domain. (Use bsr-candidate priority.)

  3. Do one of the following to configure RP operation:

    • Recommended: Enable C-RP operation and configure the router to advertise itself as a C-RP to the BSR for the current domain. This step includes the option to allow the C-RP to be a candidate for either all possible multicast groups or for up to four multicast groups and/or ranges of groups. (Use rp-candidate source-ip-vlan vid [group-addr/group-mask].)

    • Option: Use rp-address ip-addr [group-addr/group-mask] to statically configure the router as the RP for a specific multicast group or range of multicast groups. (This must be configured on all RIM-SM routers in the domain.)

  4. Option: In the PIM router context, change one or more of the traffic control settings. See Options Accessed in Router PIM Context.

Options Accessed in Router PIM Context

Options Accessed in Router PIM Context Operation
rp-candidate group-prefix group-addr/group-mask Enter an address and mask to define an additional multicast group or a range of groups.
rp-candidate hold-time 30-255 Tells the BSR how long it should expect the sending C-RP router to be operative. (Default: 150; 0 if router is not a candidate.)
rp-candidate priority 0-255 Changes the priority for the C-RP router. When multiple C-RPs are configured for the same multicast group(s), the priority determines which router becomes the RP for such groups. A smaller value means a higher priority. (Default: 192)
[ no ] spt-threshold Disable or enable the router’s ability to switch multicast traffic flows to the shortest path tree. (Default: enabled)
join-prune-interval 5-65535 Option: Globally change the interval for the frequency at which join and prune messages are forwarded on the router’s VLAN interfaces. (Default: 60 seconds)
trap neighbor-loss | hardware-mrt-full | software-mrt-full | all Option: Enable or disable PIM traps. (Default: disabled)

prev

 

up

 next

Operating rules and recommendations 

home

 Operating notes

Copyright © 2016 Hewlett Packard Enterprise Development LP