Support Center > Search Results > SecureKnowledge Details
Configuring PIM and IGMP Multicast Protocols on SecurePlatform Pro
Solution

Important: Please ensure that you are familiar with routing protocols before using this quick guide.

Multicast traffic is sent to a multicast group (defined in the Destination IP field). The IP is specified in the range between 224.0.0.0 and 239.255.255.255.

The following procedure provides step by step guidance on how to configure PIM (Protocol Independent Multicast) and IGMP (Internet Group Management Protocol) Multicast Protocols on SecurePlatform Pro:

  1. Login to the SecurePlatform Device.

  2. Enter Router Mode by running the command router or cligated.

    Note: You can display all the available commands by typing <?> and pressing the "Enter" key.

  3. Enter Privileged Execution mode by running the command enable. If this mode is password protected, you will be prompted for a password.

  4. You can type show run to display the current configuration.

  5. Enter Global Configuration mode by running the command config terminal or config t.

  6. PIM does not have router context. PIM is configured in interface context, rather than in router context. (You should configure PIM/interface.)

    PIM does not create unicast routes. Instead, it uses the unicast routing table to build a multicast cache, i.e. a multicast routing table.

    At the config prompt (config)#, run the command interface <name_of_interface>. This is the interface on which PIM will run.
    Note: The prompt changes to (config-[if_name])# in Router Configuration mode. When in this mode, the order of the commands run is not important. Changes are only performed on exiting the mode.
    To exit the Router Configuration mode and return one mode back, i.e. to the Global Configuration mode, run the exit command. To exit the Router Configuration mode and return to the Main mode, run the end command.

    Multicast traffic consists of two components:

    • Host-Router protocol (IGMP)

    • Router-Router protocol (PIM) (PIM has two different modes: Sparse and Dense)

    For correct multicast traffic management, you should configure IGMP on the interfaces leading to the hosts, and PIM on the interfaces leading to the routers. (You can define both protocols on the same interface, if you wish.)

  7. To enable IGMP, run ip igmp version <version_number>

    Note: Currently, Version 2 is most commonly used.

  8. To enable PIM, run ip pim sparse-mode or ip pim dense-mode

    • Sparse Mode: In Sparse Mode, by default, routers that are not explicitly registered for multicast traffic, do not receive such traffic. In Sparse Mode, for every multicast group, there must be a single Rendezvous Point (RP) router. The multicast traffic tree is built via this router. This router can be defined manually or automatically via PIM Bootstrap protocol.

    • Dense Mode: By default, each router receives multicast traffic, unless it sends an explicit message not to receive multicast traffic.


  9. You can now leave interface context by running the exit command and entering the Global Configuration mode.

  10. Now, specify the PIM configuration options.

  11. To manually assign an RP router for a specific multicast group, or range of multicast groups, run:

    ip pim rp-address <IP_Address_of_RP> group <group_or_range_identifier/length_of_netmask>

    For example: ip pim rp-address 10.1.1.1 group 224.1.2.0/24

    Note: If you do not specify the RP manually, you must verify that all the routers in the Autonomous System run the PIM Bootstrap protocol, which specifies the RP router automatically.

  12. For the case of automatic specification of an RP router, each router that is ready to be the RP for any multicast group, must run ip pim rp-candidate

  13. You can also include a priority parameter, i.e., ip pim rp-candidate priority <integer_between_0-255>

  14. Each router that is ready to be the RP for a specific multicast group, must run ip pim rp-candidate group <group_or_range identifier/length_of_netmask> priority <integer_between_0-255>

  15. After these values are entered, exit Router Configuration mode and then exit Global Configuration mode.

Once you return to the Privileged Execution mode, if you want these values to be saved through reboot or different gated sessions, you must store all the applied changes. Do so by running the command write memory.

Configuration will be saved in /etc/gated.ami file.

It is recommended to backup the file prior to any change.

 

Related Documentation:

Refer to SecurePlatform Pro Advanced Routing Suite CLI Reference Guide (R60, R61, R62, R65, R70, R71, R75, R75.20, R75.40, R75.40VS, R76, R77).

 

Related Solutions:

Applies To:
  • Dynamic Routing

Give us Feedback
Please rate this document
[1=Worst,5=Best]
Comment