This command enables a Multicast Source Discovery Protocol (MSDP) instance. When an MSDP instance is created, the protocol is enabled. To start or suspend execution of the MSDP protocol without affecting the configuration, use the [no] shutdown command.
For the MSDP protocol to function, at least one peer must be configured.
When MSDP is configured and started an appropriate event message should be generated.
When the no form of the command is executed, all sessions must be terminated and an appropriate event message should be generated.
When all peering sessions are terminated, an event message per peer is not required.
The no form of the command deletes the MSDP protocol instance, removing all associated configuration parameters.
no msdp
This option controls the maximum number of active source messages that will be accepted by Multicast Source Discovery Protocol (MSDP), effectively controlling the number of active sources that can be stored on the system.
The no form of this command sets no limit on the number of source active records.
no active-source-limit
This command limits the number of Multicast Source Discovery Protocol (MSDP) messages that are read from the TCP session. It is possible that an MSDP/ RP router may receive a large number of MSDP protocol message packets in a particular source active message.
After the number of MSDP packets (including source active messages) defined in the threshold have been processed, the rate of all other MSDP packets is rate limited by no longer accepting messages from the TCP session until the time (seconds) has elapsed.
The no form of this command sets no limit on the number of MSDP and source active limit messages that will be accepted.
no receive-msdp-msg-rate
The shutdown command administratively disables the entity. When disabled, an entity does not change, reset, or remove any configuration settings or statistics. Many entities must be explicitly enabled using the no shutdown command and must be shut down before they may be deleted.
Unlike other commands and parameters where the default state is not indicated in the configuration file, shutdown and no shutdown are always indicated in system generated configuration files.
The no form of the command puts an entity into the administratively enabled state.
no shutdown
This command configures a Message Digest 5 (MD5) authentication key to be used with a specific Multicast Source Discovery Protocol (MSDP) peering session. The authentication key must be configured per peer as such no global or group configuration is possible.
The no form of the command configures acceptance of all MSDP messages and disables the MD5 signature option authentication key.
no authentication-key
This is useful when a user must configure the parameter, but, for security purposes, the actual unencrypted key value is not provided.
This command configures a rendezvous point (RP) using Multicast Source Discovery Protocol (MSDP) to encapsulate multicast data received in MSDP register messages inside forwarded MSDP source-active messages.
data-encapsulation
Using the default peer mechanism, a peer can be selected as the default Multicast Source Discovery Protocol (MSDP) peer. As a result, all source-active messages from the peer will be accepted without the usual peer-reverse-path-forwarding (RPF) check.
The MSDP peer-RPF check is different from the normal multicast RPF checks. The peer-RPF check is used to stop source-active messages from looping. A router validates source-active messages originated from other routers in a deterministic fashion.
A set of rules is applied in order to validate received source-active messages, and the first rule that applies determines the peer-RPF neighbor. All source-active messages from other routers are rejected. The rules applied to source-active messages originating at Router S received at Router R from Router N are as follows:
No default peer is established and all active source messages must be RPF checked.
This command specifies the policies to export source active state from the source active list into Multicast Source Discovery Protocol (MSDP).
If multiple policy names are specified, the policies are evaluated in the order they are specified. The first policy that matches is applied. If multiple export commands are issued, the last command entered will override the previous command. A maximum of five policy names can be specified.
The no form of the command applies no export policies and all SA entries are announced.
no export
If you configure an export policy at the global level, each individual peer inherits the global policy. If you configure an export policy at the group level, each individual peer in a group inherits the group’s policy. If you configure an export policy at the peer level, then policy only applies to the peer where it is configured.
This command enables access to the context to create or modify a Multicast Source Discovery Protocol (MSDP) group. To configure multiple MSDP groups, include multiple group statements.
By default, the group’s options are inherited from the global MSDP options. To override these global options, group-specific options within the group statement can be configured.
If the group name provided is already configured then this command only provides the context to configure the options pertaining to this group.
If the group name provided is not already configured, then the group name must be created and the context to configure the parameters pertaining to the group should be provided. In this case, the $ prompt to indicate that a new entity (group) is being created should be used.
For a group to be of use, at least one peer must be configured.
no group
This command specifies the policies to import source active state from Multicast Source Discovery Protocol (MSDP) into source active list.
If multiple policy names are specified, the policies are evaluated in the order they are specified. The first policy that matches is applied. If multiple import commands are issued, the last command entered will override the previous command. A maximum of five policy names can be specified.
If you configure an import policy at the global level, each individual peer inherits the global policy.
If you configure an import policy at the group level, each individual peer in a group inherits the group’s policy.
If you configure an import policy at the peer level, then policy only applies to the peer where it is configured.
The no form of the command applies no import policies and all source active messages are allowed.
no import
This command configures the local end of a Multicast Source Discovery Protocol (MSDP) session. For MSDP to function, at least one peer must be configured. When configuring a peer, you must include this local-address command to configure the local end of the MSDP session. This address must be present on the node and is used to validate incoming connections to the peer and to establish connections to the remote peer.
If the user enters this command, then the address provided is validated and will be used as the local address for MSDP peers from that point. If a subsequent local-address command is entered, it will replace the existing configuration and existing sessions will be terminated.
Similarly, when the no form of this command is entered, the existing local-address will be removed from the configuration and the existing sessions will be terminated.
Whenever a session is terminated, all information pertaining to and learned from that peer will be removed.
Whenever a new peering session is created or a peering session is lost, an event message should be generated.
The no form of this command removes the local-address from the configuration.
No local address is configured.
This command configures groups of peers in a full mesh topology to limit excessive flooding of source-active messages to neighboring peers.
Multicast Source Discovery Protocol (MSDP) peers can be configured grouped in a full-mesh topology that prevents excessive flooding of source-active messages to neighboring peers.
In a meshed configuration, all members of the group must have a peer connection with every other mesh group member. If this rule is not adhered to, then unpredictable results may occur.
mode standard
This command configures peer parameters. Multicast Source Discovery Protocol (MSDP) must have at least one peer configured. A peer is defined by configuring a local-address that can be used by this node to set up a peering session and the address of a remote MSDP router, It is the address of this remote peer that is configured in this command and it identifies the remote MSDP router address.
After peer relationships are established, the MSDP peers exchange messages to advertise active multicast sources. It may be required to have multiple peering sessions in which case multiple peer statements should be included in the configurations.
By default, the options applied to a peer are inherited from the global or group-level. To override these inherited options, include peer-specific options within the peer statement.
If the peer address provided is already a configured peer, then this command only provides the context to configure the parameters pertaining to this peer.
If the peer address provided is not already a configured peer, then the peer instance must be created and the context to configure the parameters pertaining to this peer should be provided. In this case, the $ prompt to indicate that a new entity (peer) is being created should be used.
The peer address provided will be validated and, if valid, will be used as the remote address for an MSDP peering session.
When the no form of this command is entered, the existing peering address will be removed from the configuration and the existing session will be terminated. Whenever a session is terminated, all source active information pertaining to and learned from that peer will be removed. Whenever a new peering session is created or a peering session is lost, an event message should be generated.
At least one peer must be configured for MSDP to function.
none
This command configures the sequence of route tables used to find a Reverse Path Forwarding (RPF) interface for a particular multicast route.
By default, only the unicast route table is looked up to calculate RPF interface towards the source/rendezvous point. However, the operator can specify one of the following options:
rpf-table rtable-u
This command configures the value for the SA entries in the cache. If these entries are not refreshed within the timeout value, they are removed from the cache. Normally, the entries are refreshed at least once a minute. But under high load with many of MSDP peers, the refresh cycle could be incomplete. A higher timeout value (more than 90) could be useful to prevent instabilities in the MSDP cache.
90
This command limits the number of active source messages the router accepts from sources in the specified address range.
If the prefix and mask provided is already a configured then this command only provides the context to configure the parameters pertaining to this active source-message filter.
If the prefix and mask provided is not already a configured, then the source node instance must be created and the context to configure the parameters pertaining to this node should be provided. In this case, the $ prompt to indicate that a new entity (source) is being created should be used.
The no form of this message removes the source active rate limiter for this source address range.
None. The source active msdp messages are not rate limited based on the source address range.