Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
 

Configuring Graceful Restart for Multicast Snooping

When graceful restart is enabled for multicast snooping, no data traffic is lost during a process restart or a graceful Routing Engine switchover (GRES). Graceful restart can be configured for multicast snooping either at the global level or at the level of individual routing instances.

At the global level, graceful restart is enabled by default for multicast snooping. To change this default setting, you can configure the disable statement at the [edit multicast-snooping-options graceful-restart] hierarchy level:

To configure graceful restart for multicast snooping on a global level:

  1. Configure the duration for graceful restart.

    The range for restart-duration is from 0 through 300 seconds. The default value is 180 seconds. After this period, the Routing Engine resumes normal multicast operation.

    You can also set the graceful-restart statement for an individual routing instance level at the [edit logical-systems logical-system-name routing-instances routing-instance-name multicast-snooping-options] hierarchy level.

  2. Verify your configuration by using the show multicast-snooping-options command.
  3. Commit the configuration.

To configure graceful restart for multicast snooping for an individual routing instance level:

  1. Configure the duration for graceful restart.

    The range for restart-duration is from 0 through 300 seconds. The default value is 180 seconds. After this period, the Routing Engine resumes normal multicast operation.

    Note:

    You can also set the graceful-restart statement for an individual routing instance level at the [edit logical-systems logical-system-name routing-instances routing-instance-name multicast-snooping-options] hierarchy level.

  2. Verify your configuration by using the show routing-instances routing-instance-name multicast-snooping-options command.

  3. Commit the configuration.