[Contents] [Prev] [Next] [Index] [Report an Error]

Configuring a Multicast Network with a Configuration Editor

To configure the Services Router as a node in a multicast network, you must perform the following tasks marked (Required).

Configuring SAP and SDP (Optional)

Multicast session announcements are handled by two protocols, the Session Announcement Protocol (SAP) and Session Description Protocol (SDP). These two protocols display multicast session names and correlate the names with multicast traffic. Enabling SDP and SAP allows the router to receive announcements about multimedia and other multicast sessions from sources. Enabling SAP automatically enables SDP.

For more information on SAP and SDP, see the JUNOS Multicast Protocols Configuration Guide.

The Services Router listens for session announcements on one or more addresses and ports. By default, the router listens to address and port 224.2.127.254:9875.

To configure SAP and SDP for the Services Router:

  1. Navigate to the top of the configuration hierarchy in either the J-Web or CLI configuration editor.
  2. Perform the configuration tasks described in Table 177.
  3. Go on to Configuring IGMP (Required).

Table 177: Configuring SAP and SDP

Task

J-Web Configuration Editor

CLI Configuration Editor

Navigate to the Listen level in the configuration hierarchy.

  1. In the J-Web interface, select Configure>CLI Tools>Point and Click CLI.
  2. Next to Protocols, click Configure or Edit.
  3. Next to Sap, click Configure or Edit.
  4. Click Add new entry next to Listen.

From the [edit] hierarchy level, enter

edit protocols sap

(Optional) Enter one or more addresses and ports for the Services Router to listen to session announcements on. By default, the Services Router listens to address and port 224.2.127.254:9875.

  1. In the Address box, type the multicast address the Services Router can listen to session announcements on, in dotted decimal notation.
  2. In the Port box, type the port number in decimal notation.
  3. Click OK.
  1. Set the address value to the IP address that the Services Router can listen to session announcements on, in dotted decimal notation. For example:

    set listen 224.2.127.254

  2. Set the port value to the number of the port that the Services Router can listen to session announcements on, in decimal notation. For example:

    set listen 224.2.127.254 port 9875.

Configuring IGMP (Required)

The Internet Group Management Protocol (IGMP) manages the membership of hosts and routers in multicast groups. IGMP is an integral part of IP and must be enabled on all routers and hosts that need to receive IP mulitcasts. IGMP is automatically enabled on all broadcast interfaces when you configure PIM or DVMRP.

For more information on IGMP, see JUNOS Multicast Protocols Configuration Guide.

By default, the Services Router runs IGMPv2. However, you might still want to set the IGMP version explicitly on an interface, or all interfaces. Routers running different versions of IGMP negotiate the lowest common version of IGMP supported by hosts on their subnet. One host running IGMPv1 forces the Services Router to use that version and lose features important to other hosts.

To explicitly configure the IGMP version, perform these steps on each Services Router in the network:

  1. Navigate to the top of the configuration hierarchy in either the J-Web or CLI configuration editor.
  2. Perform the configuration tasks described in Table 178.
  3. If you are finished configuring the router, commit the configuration.
  4. Go on to one of the following procedures:

Table 178: Explicitly Configuring the IGMP version

Task

J-Web Configuration Editor

CLI Configuration Editor

Navigate to the Interface level in the configuration hierarchy.

  1. In the J-Web interface, select Configure>CLI Tools>Point and Click CLI.
  2. Next to Protocols, click Configure or Edit.
  3. Next to Igmp, click Configure or Edit.
  4. Next to Interface, click Add new entry.

From the [edit] hierarchy level, enter

edit protocols igmp

Set the IGMP version. By default, the Services Router uses IGMPv2, but this version can be changed through negotiation with hosts unless explicitly configured.

  1. In the Interface name box, type the name of the interface, or all.
  2. In the Version box, type the version number: 1, 2, or 3.
  3. Click OK.
  1. Set the interface value to the interface name, or all. For example:

    set igmp interface all

  2. Set the version value to 1, 2, or 3. For example:

    set igmp interface all version 2

Configuring the PIM Static RP (Optional)

Protocol Independent Multicast (PIM) sparse mode is the most common multicast protocol used on the Internet. PIM sparse mode is the default mode whenever PIM is configured on any interface of the Services Router. However, because PIM must not be configured on the network management interface of the Services Router, you must disable it on that interface.

Each any-source multicast (ASM) group has a shared tree through which receivers learn about new multicast sources and new receivers learn about all multicast sources. The rendezvous point (RP) router is the root of this shared tree and receives the multicast traffic from the source. To receive multicast traffic from the groups served by the RP, the Services Router must determine the IP address of the RP for the source.

One common way for the Services Router to locate RPs is by static configuration of the IP address of the RP. For information about alternate methods of locating RPs, see the JUNOS Multicast Protocols Configuration Guide.

To configure PIM sparse mode, disable PIM on ge-0/0/0, and configure the IP address of the RP perform these steps on each Services Router in the network:

  1. Navigate to the top of the configuration hierarchy in either the J-Web or CLI configuration editor.
  2. Perform the configuration tasks described in Table 179.
  3. Go on to Configuring a PIM RPF Routing Table (Optional).

Table 179: Configuring PIM Sparse Mode and the RP

Task

J-Web Configuration Editor

CLI Configuration Editor

Navigate to the Interface level in the configuration hierarchy.

  1. In the J-Web interface, select Configure>CLI Tools>Point and Click CLI.
  2. Next to Protocols, click Configure or Edit.
  3. Next to Pim, click Configure or Edit.
  4. Next to Interface, click Add new entry.

From the [edit] hierarchy level, enter

edit protocols pim

Enable PIM on all network interfaces.

In the Interface name box, type all.

Set the interface value to all. For example:

set pim interface all

Apply your configuration changes.

Click OK to apply your entries to the configuration.

Changes in the CLI are applied automatically when you execute the set command.

Remain at the Interface level in the configuration hierarchy.

Click Add new entry next to Interface.

Remain at the [edit protocols pim interface] hierarchy level.

Disable PIM on the network management interface.

  1. In the Interface name box, type ge-0/0/0.
  2. Select the check box next to Disable.

Disable the ge-0/0/0 interface:

set pim interface ge-0/0/0 unit 0 disable

Apply your configuration changes.

Click OK to apply your entries to the configuration.

Changes in the CLI are applied automatically when you execute the set command.

Navigate to the Rp level in the configuration hierarchy.

  1. On the main Configuration page next to Protocols, click Configuring BGP Confederations.
  2. Next to Pim, click Configure or Edit.
  3. Next to Rp, click Configure or Edit.

From the [edit] hierarchy level, enter

edit protocols pim rp

Configure the IP address of the RP—for example, 192.168.14.27.

  1. Click Configure next to Static.
  2. Click Add new entry next to Address.
  3. In the Addr box, type 192.168.14.27.
  4. Click OK.

Set the address value to the IP address of the RP:

set static address 192.168.14.27

Filtering PIM Register Messages from Unauthorized Groups and Sources (Optional)

When a source in a multicast network becomes active, the source’s designated router (DR) encapsulates multicast data packets into a PIM register message and sends them by means of unicast to the rendezvous point (RP) router.

To prevent unauthorized groups and sources from registering with an RP router, you can define a routing policy to reject PIM register messages from specific groups and sources and configure the policy on the designated router or the RP router. For information about routing policies, see the JUNOS Policy Framework Configuration Guide

Note: If you have configured the reject policy on an RP router, we recommend that you configure the same policy on all the RP routers in your multicast network.

Note: If you delete a group and source address from the reject policy configured on an RP router and commit the configuration, the RP router will register the group and source only when the designated router sends a null register message.

This section contains the following topics:

Rejecting Incoming PIM Register Messages on an RP Router

To reject incoming PIM register messages on an RP router:

  1. Navigate to the top of the configuration hierarchy in either the J-Web or CLI configuration editor.
  2. Perform the configuration tasks described in Table 180.
  3. If you are finished configuring the router, commit the configuration.
  4. To check the configuration, see Verifying a Multicast Configuration.

Table 180: Rejecting Incoming PIM Register Messages on an RP Router

Task

J-Web Configuration Editor

CLI Configuration Editor

Navigate to the Policy options level in the configuration hierarchy.

  1. In the J-Web interface, select Configure>CLI Tools>Point and Click CLI.
  2. Next to Policy options, click Configure or Edit.

From the [edit] hierarchy level, enter

edit policy-options

Define a policy to reject PIM register messages from a group and source address.

  1. Next to Policy statement, click Add new entry.
  2. In the Policy name box, type the name of the policy statement—for example, reject-pim-register-msg-rp.
  3. Next to From, click Configure.
  4. Next to Route filter, click Add new entry.
  5. In the Address box, type the address of the group—for example, 224.1.1.1/32.
  6. From the Modifier list, select Exact.
  7. Click OK.
  8. Next to Source address filter, click Add new entry.
  9. In the Address box, type the address of the source—for example, 10.10.10.1/32.
  10. From the Modifier list, select Exact.
  11. Click OK until you return to the Policy statement page.
  12. Next to Then, click Configure.
  13. From the Accept reject list, select Reject.
  14. Click OK.
  1. Set the match condition for the group address:

    set policy statement reject-pim-register-msg-rp from route-filter 224.1.1.1/32 exact

  2. Set the match condition for the address of a source in the group:

    set policy statement reject-pim-register-msg-rp from source-address-filter 10.10.10.1/32 exact

  3. Set the match action to reject PIM register messages from the group and source address:

    set policy statement reject-pim-register-msg-rp then reject

Configure the reject-pim-register-msg-rp policy on the RP router.

  1. On the main Configuration page next to Protocols, click Configure or Edit.
  2. Next to Pim, click Configure.
  3. Next to Rp, click Configure.
  4. Next to Rp register policy, click Add new entry.
  5. In the Value box, type the name of the policy—reject-pim-register-msg-rp.
  6. Click OK.
  1. From the [edit] hierarchy level, enter

    edit protocols pim rp

  2. Assign the policy on the RP:

    set rp-register-policy reject-pim-register-msg-rp

Stopping Outgoing PIM Register Messages on a Designated Router

To stop outgoing PIM register messages on a designated router:

  1. Navigate to the top of the configuration hierarchy in either the J-Web or CLI configuration editor.
  2. Perform the configuration tasks described in Table 181.
  3. If you are finished configuring the router, commit the configuration.
  4. To check the configuration, see Verifying a Multicast Configuration.

Table 181: Stopping Outgoing PIM Register Messages on a Designated Router

Task

J-Web Configuration Editor

CLI Configuration Editor

Navigate to the Policy options level in the configuration hierarchy.

  1. In the J-Web interface, select Configure>CLI Tools>Point and Click CLI.
  2. Next to Policy options, click Configure or Edit.

From the [edit] hierarchy level, enter

edit policy-options

Define a policy to not send PIM register messages for a group and source address.

  1. Next to Policy statement, click Add new entry.
  2. In the Policy name box, type the name of the policy statement—for example, stop-pim-register-msg-dr.
  3. Next to From, click Configure.
  4. Next to Route filter, click Add new entry.
  5. In the Address box, type the address of the group—for example, 224.2.2.2/32.
  6. From the Modifier list, select Exact.
  7. Click OK.
  8. Next to Source address filter, click Add new entry.
  9. In the Address box, type the address of the source—for example, 20.20.20.1/32.
  10. From the Modifier list, select Exact.
  11. Click OK until you return to the Policy statement page.
  12. Next to Then, click Configure.
  13. From the Accept reject list, select Reject.
  14. Click OK.
  1. Set the match condition for the group address:

    set policy statement stop-pim-register-msg-dr from route-filter 224.2.2.2/32 exact

  2. Set the match condition for the address of a source in the group:

    set policy statement stop-pim-register-msg-dr from source-address-filter 20.20.20.1/32 exact

  3. Set the match action to not send PIM register messages for the group and source address:

    set policy statement stop-pim-register-msg-dr then reject

Configure the stop-pim-register-msg-dr policy on the designated router.

  1. On the main Configuration page, next to Protocols, click Configure or Edit.
  2. Next to Pim, click Configure.
  3. Next to Rp, click Configure.
  4. Next to Dr register policy, click Add new entry.
  5. In the Value box, type the name of the policy—for example, stop-pim-register-msg-dr.
  6. Click OK.
  1. From the [edit] hierarchy level, enter

    edit protocols pim rp

  2. Assign the policy on the designated router:

    set dr-register-policy stop-pim-register-msg-dr

Configuring a PIM RPF Routing Table (Optional)

By default, PIM uses inet.0 as its reverse-path forwarding (RPF) routing table group. PIM uses an RPF routing table group to resolve its RPF neighbor for a particular multicast source address and for the RP address. PIM can optionally use inet.2 as its RPF routing table group. The inet.2 routing table is organized more efficiently for RPF checks.

Once configured, the RPF routing table must be applied to PIM as a routing table group.

To configure and apply a PIM RPF routing table, perform these steps on each Services Router in the network:

  1. Navigate to the top of the configuration hierarchy in either the J-Web or CLI configuration editor.
  2. Perform the configuration tasks described in Table 182.
  3. If you are finished configuring the router, commit the configuration.
  4. To check the configuration, see Verifying a Multicast Configuration.

Table 182: Configuring a PIM RPF Routing Table

Task

J-Web Configuration Editor

CLI Configuration Editor

Navigate to the Routing options level in the configuration hierarchy.

  1. In the J-Web interface, select Configure>CLI Tools>Point and Click CLI.
  2. Next to Routing options, click Configure or Edit.

From the [edit] hierarchy level, enter

edit routing-options

Configure a new group for the RPF routing table.

Next to Rib groups, click Add new entry.

Enter

edit rib-groups

Configure a name for the new RPF routing table group—for example, multicast-rfp-rib—and use inet.2 for its export routing table.

  1. In the Ribgroup name box, type multicast-rfp-rib.
  2. In the Export rib box, type inet.2.

Enter

set multicast-rpf-rib export-rib inet.2

Configure the new RPF routing table group to use inet.2 for its import routing table.

  1. Click Add new entry next to Import rib.
  2. In the Value box, type inet.2.
  3. Click OK three times.

Enter

set multicast-rpf-rib import-rib inet.2

Navigate to the Rib group level in the configuration hierarchy.

  1. On the main Configuration page next to Protocols, click Configure or Edit.
  2. Next to Pim, click Configure or Edit.
  3. Next to Rib group, click Configure or Edit.

From the [edit] hierarchy level, enter

edit protocols pim

Apply the new RPF routing table to PIM.

  1. In the Inet box, type the name of the RPF routing table group—multicast-rpf-rib.
  2. Click OK three times.

Enter

set rib-group multicast-rpf-rib

Create a routing table group for the interface routes.

  1. On the main Configuration page next to Routing options, click Configure or Edit.
  2. Next to Rib groups, click Add new entry.

From the [edit] hierarchy level, enter

edit routing-options rib-groups.

Configure a name for the RPF routing table group—for example, if-rib—and use inet.2 and inet.0 for its import routing tables.

  1. In the Ribgroup name box, type if-rib.
  2. Click Add new entry next to Import rib.
  3. In the Value box, type inet.2 inet.0.
  4. Click OK twice.

Enter

set if-rib import-rib inet.2

set if-rib import-rib inet.0

Add the new interface routing table group to the interface routes.

  1. On the Routing options page next to Interface routes, click Configure or Edit.
  2. Next to Rib group, click Configure or Edit.
  3. In the Inet box, type if-rib.
  4. Click OK.

From the [edit] hierarchy level, enter

edit routing-options interface-routes

set rib-group inet if-rib

[Contents] [Prev] [Next] [Index] [Report an Error]


[an error occurred while processing this directive]