Example: Configuring the Multicast Forwarding Cache

When a routing device receives multicast traffic, it places the (S,G) route information in the multicast forwarding cache, inet.1. This example shows how to configure multicast forwarding cache limits to prevent the cache from filling up with entries.

Requirements

Before you begin:

Overview

This example includes the following statements:

Configuration

CLI Quick Configuration

To quickly configure the multicast forwarding cache, copy the following commands and paste the commands into the CLI.

[edit]set routing-options multicast forwarding-cache threshold suppress 150000 set routing-options multicast forwarding-cache threshold reuse 34 set routing-options multicast forwarding-cache timeout 60

Step-by-Step Procedure

To configure the multicast forwarding cache:

  1. Configure the maximum size of the forwarding cache.

    [edit]user@host# edit routing-options multicast forwarding-cache[edit routing-options multicast forwarding-cache]user@host# set threshold suppress 150000
  2. Configure the amount of time (in minutes) entries can remain idle before being removed.

    [edit routing-options multicast forwarding-cache]user@host# set timeout 60
  3. Configure the size of the forwarding cache when suppression stops and new entries can be added.

    [edit routing-options multicast forwarding-cache]user@host# set threshold reuse 70000

Results

Confirm your configuration by entering the show routing-options command.

user@host# show routing-optionsmulticast {forwarding-cache {threshold {suppress 150000;reuse 70000;}timeout 60;}}

Verification

To verify the configuration, run the show multicast route extensive command.


user@host> show multicast route extensive
Family: INET
Group: 232.0.0.1
    Source: 11.11.11.11/32
    Upstream interface: fe-0/2/0.200
    Downstream interface list:
        fe-0/2/1.210
    Downstream interface list rejected by CAC:
        fe-0/2/1.220
    Session description: Source specific multicast
    Statistics: 0 kBps, 0 pps, 0 packets
    Next-hop ID: 337
    Upstream protocol: PIM
    Route state: Active
    Forwarding state: Forwarding
    Cache lifetime/timeout: 60 minutes
Wrong incoming interface notifications: 0

Related Topics