Router Multicast Source Discovery Protocol (MSDP) Commands

msdp

Syntax

[no] msdp

Context

config>router

Description

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.

The no form of the command deletes the MSDP protocol instance removing all associated configuration parameters.

Default

no msdp

Interactions:

In order 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.

active-source-limit

Syntax

active-source-limit number

no active-source-limit

Context

config>router>msdp

config>router>msdp>group

config>router>msdp>group>peer

Description

This option controls the maximum number of active source messages that will be accepted by Multicast Source Discovery Protocol (MSDP). This effectively controls the number of active sources that can be stored on the system.

The no form of this command reverts the number of source message limit to default operation

Default

No limit is placed on the number of source active records

Parameters

number

This parameter defines how many active sources can be maintained by MSDP.

Values 0 — 1000000

receive-msdp-msg-rate

Syntax

receive-msg-rate number interval seconds [threshold number]

no receive-msg-rate

Context

config>router>msdp

config>router>msdp>peer

config>router>msdp>group

config>router>msdp>source

Description

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.

The no form of this command reverts this active-source limit to default operation

Default

No limit is placed on the number of MSDP and source active limit messages will be accepted.

Parameters

number

Defines the number of MSDP messages (including source active messages) that are read from the TCP session per the number of seconds.

Values 10 — 10000

Default

0

interval seconds

This defines the time that together with the number parameter defines the number of MSDP messages (including source active messages) that are read from the TCP session within the configured number of seconds.

Values 1 — 600

Default

0

threshold number

This number reflects the number of MSDP messages can be processed before the MSDP message rate limiting function described above is activated; this is of use in particular during at system startup and initialization.

Values 1 — 1000000

Default

0

Interactions:

Once 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.

authentication-key

Syntax

authentication-key [authentication-key|hash-key] [hash|hash2]

no authentication-key

Context

config>router>msdp>peer

config>router>msdp>group>peer

Description

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.

Default

Authentication-key. All MSDP messages are accepted and the MD5 signature option authentication key is disabled.

Parameters

authentication-key

The authentication key. Allowed values are any string up to 16 characters long composed of printable, 7-bit ASCII characters. If the string contains special characters (#, $, spaces, etc.), the entire string must be enclosed within double quotes.

hash-key

The hash key. The key can be any combination of ASCII characters up to 33 characters in length (encrypted). If spaces are used in the string, enclose the entire string in quotation marks
(“ ”).

This is useful when a user must configure the parameter, but, for security purposes, the actual unencrypted key value is not provided.

hash

Specifies the key is entered in an encrypted form. If the hash parameter is not used, the key is assumed to be in a non-encrypted, clear text form. For security, all keys are stored in encrypted form in the configuration file with the hash parameter specified.

hash2

Specifies the key is entered in a more complex encrypted form. If the hash2 parameter is not used, the less encrypted hash form is assumed.

data-encapsulation

Syntax

[no] data-encapsulation

Context

config>router>msdp

Description

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.

Default

data-encapsulation

default-peer

Syntax

default-peer

no default-peer

Context

config>router>msdp>peer

config>router>msdp>group>peer

Description

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:

•	If Router N and router S are one and the same, then the message is originated by a direct peer-RPF neighbor and will be accepted.

•	If Router N is a configured peer, or a member of the Router R mesh group then its source-active messages are accepted.

•	If Router N is the Border Gateway Protocol (BGP) next hop of the active multicast RPF route toward Router S then Router N is the peer-RPF neighbor and its source-active messages are accepted.

•	If Router N is an external BGP peer of Router R and the last autonomous system (AS) number in the BGP AS-path to Router S is the same as Router N’s AS number, then Router N is the peer-RPF neighbor, and its source-active messages are accepted.

•	If Router N uses the same next hop as the next hop to Router S, then Router N is the peer-RPF neighbor, and its source-active messages are accepted.

•	If Router N fits none of the above rules, then Router N is not a peer-RPF neighbor, and its source-active messages are rejected.

Default

No default peer is established and all active source messages must be RPF checked.

export

Syntax

export policy-name [policy-name...(up to 5 max)]

no export

Context

config>router>msdp

config>router>msdp>peer

config>router>msdp>group

config>router>msdp>group>peer

Description

This command specifies the policies to export source active state from the source active list into Multicast Source Discovery Protocol (MSDP).

The no form of the command removes all policies from the configuration.

Default

No export policies are applied and all SA entries are announced.

Parameters

policy-name

Specifies the export policy name. Up to five policy-name arguments can be specified.

Interactions:

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.

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.

group

Syntax

[no] group group-name

Context

config>router>msdp

Description

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.

In order for a group to be of use at least one peer must be configured.

Default

no group

Parameters

group-name

Species a unique name for the MSDP group.

Interactions:

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.

import

Syntax

import policy-name [policy-name...(up to 5 max)]

no import

Context

config>router>msdp

config>router>msdp>peer

config>router>msdp>group

config>router>msdp>group>peer

Description

This command specifies the policies to import source active state from Multicast Source Discovery Protocol (MSDP) into source active list.

The no form of the command removes all policies from the configuration.

Default

No import policies are applied and all source active messages are allowed.

Parameters

policy-name

Specifies the import policy name. Up to five policy-name arguments can be specified.

Interactions:

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.

local-address

Syntax

local-address address

no local-address

Context

config>router>msdp

config>router>msdp>peer

config>router>msdp>group

config>router>msdp>group>peer

Description

This command configures the local end of a Multicast Source Discovery Protocol (MSDP) session. In order 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.

The no local address format of this command removes the local-address from the configuration.

Default

No local address is configured.

Parameters

address

Specifies an existing address on the node.

Interactions:

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 session(s) 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 session(s) will be terminated.

Whenever a session is terminated all information pertaining to and learned from that peer and will be removed.

Whenever a new peering session is created or a peering session is lost an event message should be generated.

mode

Syntax

mode {mesh-group | standard}

Context

config>router>msdp>group

Description

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.

Default

standard (non-meshed)

Parameters

mesh-group

Specifies that source-active message received from a mesh group member are always accepted but are not flooded to other members of the same mesh group. These source-active messages are only flooded to non-mesh group peers or members of other mesh groups.

standard

Specifies a non-meshed mode.

Interactions:

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.

peer

Syntax

[no] peer peer-address

Context

config>router>msdp

config>router>msdp>group

Description

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.

At least one peer must be configured for MSDP to function.

Default

none

Parameters

peer-address

The address configured in this statement must identify the remote MSDP router that the peering session must be established with.

Interactions:

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 assuming it is valid it 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 and will be removed. Whenever a new peering session is created or a peering session is lost an event message should be generated.

source

Syntax

[no] source ip-prefix/mask

Context

config>router>msdp

Description

This command limits the number of active source messages the router accepts from sources in the specified address range.

The no form of this message removes the source active rate limiter for this source address range.

Default

None. The source active msdp messages are not rate limited based on the source address range.

Interactions:

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.

Parameters

ip-prefix

The IP prefix in dotted decimal notation for the range used by the ABR to advertise that summarizes the area into another area.

Values

ip-prefix/mask: ip-prefix a.b.c.d (host bits must be 0)

mask

The subnet mask for the range expressed as a decimal integer mask length or in dotted decimal notation.

Values

0 — 32 (mask length), 0.0.0.0 — 255.255.255.255 (dotted decimal)

 

Multicast CAC Policy Configuration Commands

mcac

Parameters

mcac

Context

config>router

config>router>pim>if

config>router>mld>group-interface

Description

This command enables the context to configure multicast CAC parameters.

Default 

none

policy

Syntax

policy mcac-policy-name

no policy mcac-policy-name

Context

configure>router>igmp>interface>mcac

configure>service>vprn>igmp>interface >mcac

Description

This command references the global channel bandwidth definition policy that is used for (H)mcac and HQoS Adjust.

HQoS Adjustment is supported only with redirection enabled. In other words, the policy from the redirected interface is used for HQoS Adjustment.

Hierarchical mcac (Hmcac) is supported only with redirection enabled. In Hmcac, the subscriber is checked first against its bandwidth limits followed by the check on the redirected interface against the bandwidth limits defined under the redirected interface. In the Hmcac case the channel definition policy must be referenced under the redirected interface level.

Parameters

mcac-policy-name

Specifies the name of the global mcac channel definition policy defined under the hierarchy configure>router>mcac>policy.

Default

No policy is referenced.

bundle

Parameters

[no] bundle bundle-name

Context

config>router>mcac>policy

Description

This command creates the context that enables the grouping of MCAC group addresses into bundles.

When a number of multicast groups or BTV channels are grouped into a single bundle, then policing, if a join for a particular MC-group (BTV channel), can depend on whether:

1. There is enough physical bandwidth on the egress interface.

2. The given channel is a mandatory or optional channel.

– If optional, is there sufficient bandwidth according to the policy settings for the relevant interface.

– If optional, is there sufficient bandwidth within the bundle.

The no form of the command removes the named bundle from the configuration.

Default

none

Parameters

bundle-name

Specifies the multicast bundle name. Allowed values are any string up to 32 characters long composed of printable, 7-bit ASCII characters. If the string contains special characters (#, $, spaces, etc.), the entire string must be enclosed within double quotes.

bandwidth

Syntax

bandwidth bandwidth

no bandwidth

Context

config>router>mcac>policy>bundle

Description

This command configures the MCAC policy bundle maximum bandwidth.

Parameters

bandwidth

Specifies the MCAC policy bandwidth.

channel

Syntax

channel start-address end-address bw bandwidth [class {high | low}] [type {mandatory | optional}] [source source-prefix]

no channel start-address end-address [source source-prefix]

Context

config>router>mcac>policy>bundle

Description

This command creates a multicast channel within the bundle where it is configured. A join for a particular multicast channel can be accepted if:

1) Mandatory channels:

A sufficient bandwidth exists on the interface according to the policy settings for the interface. Note, there is always sufficient BW available on the bundle level, as mandatory channels get BW pre-reserved.

2) Optional channels:

A sufficient BW exists on both interface and bundle level.

A channel definition can be either IPv4 (start-address, end-address, source-address are IPv4 addresses) or IPv6. A single bundle can have either IPv4 or IPv6 or IPv6 and IPv4 channel definitions. A single policy can mix any of those bundles.

Overlapping channels are not allowed. Two channels overlap if they contain same groups and the same source address prefix (or both do not specify source address prefix). Two channels with same groups and different source prefixes (including one of the channels having no source configured or one of the channels having more specific prefix than the other) do not overlap and are treated as separate channels.

When joining a group from multiple sources, MCAC accounts for that only once when no source address is specified or a prefix for channel covers both sources. Channel BW should be adjusted accordingly or source-aware channel definition should be used if that is not desired.

If a bundle is removed, the channels associated are also removed and every multicast group that was previously policed (because it was in the bundle that contained the policy) becomes free of constraints.

When a new bundle is added to a MCAC policy, the bundle’s established groups on a given interfaces are accounted by the policy. Even if this action results in exceeding the bundle’s constrain, no active multicast groups are removed. When a leave message is received for an existing optional channel, then the multicast stream is pruned and subsequent new joins may be denied in accordance with the policy. It is possible that momentarily there may be insufficient bandwidth, even for mandatory channels, in this bundle.

Default

No channels are specified as part of a bundle on default.

Parameters

start-address end-address

Specifies the beginning and ending multicast IP addresses that identifies a multicast stream (BTV channel). Both addresses have to be either IPv4 or IPv6.

Values

This must be a valid IPv4 or IPv6 multicast group address

source source-prefix

Specifies the source of the multicast IP stream. This must be a valid IPv4 or IPv6 multicast source address prefix.

Values

address-prefix/prefix-length

address-prefix is valid IPv4/IPv6 multicast source IP address prefix (local scope excluded)

prefix-length [0..32] for IPv4 [0..128] for IPv6

bw bandwidth

Specifies the bandwidth required by this channel in kbps. If this bandwidth is configured for a mandatory channel then this bandwidth is reserved by subtracting the amount from the total available bandwidth for all potential egress interfaces and the bundle.

If this bandwidth is configured as an optional channel then this bandwidth must be available for both the bundle and the egress interface requesting the channel to be added. Once the channel has been added the available bandwidth for the bundle and the interface must be reduced by the configured bandwidth of channel.

Values

10 — 10000 kbps

class {high | low}

Provides deeper classification of channels used in the algorithm when LAG ports change state.

Default

low

type {mandatory | optional}

Specifies the channel to be either mandatory or optional.

mandatory — When the mandatory keyword is specified, then the bandwidth is reserved by subtracting it from the total available for all the potential egress interfaces and the bundle.

optional — When the optional keyword is specified then the bandwidth must be available on both the bundle and the egress interface that requests the channel to be added. Once the channel has been added the available bandwidth for the bundle and the interface must be reduced by the configured bandwidth of channel.

Default

optional

mc-constraints

Syntax

mc-constraints

Context

config>router>mcac>policy>bundle

config>router>igmp>group-interface>mcac

config>router>mld>group-interface

Description

This command enables the context to configure the level and its associated bandwidth for a bundle or a logical interface.

Default

none

policy

Syntax

policy policy-name

no policy

Context

configure>router>igmp>interface>mcac

configure>router>igmp>group-interface>mcac

configure>service>vprn>igmp>interface>mcac

config>router>mld>group-interface

configure>service>vprn>igmp>group-interface>mcac

Description

This command references the global channel bandwidth definition policy that is used for (H)mcac and HQoS Adjust.

Within the scope of HQoS Adjustment, the channel definition policy under the group-interface is used if redirection is disabled. In such case HQoS Adjustment can be applied to IPoE subscribers in per-sap replication mode.

In case that redirection is enabled, the channel bandwidth definition policy applied under the Layer 3 redirected interface is in effect.

Hierarchical mcac (Hmcac) is supported on two levels simultaneously:

subscriber level and redirected interface in case that redirection is enabled

subscriber level and group-interface level in case that redirection is disabled.

In Hmcac, the subscriber is first checked against its bandwidth limits followed by the check on the redirected interface (or group-interface) against the bandwidth limits there.

In the case that the redirection is enabled but the policy is referenced ONLY under the group-interface, no admission control will be executed (Hmcac or Mcac).

Default

No policy is referenced.

Parameters

policy-name

Specifies the name of the global mcac channel definition policy defined under the hierarchy configure>router>mcac>policy.

 

lag-port-down

Syntax

lag-port-down lag-id number-down number-lag-port-down level level-id

no lag-port-down lag-id number-down number-lag-port-down

Context

config>router>mcac>policy>bundle>mc-constraints

Description

This command configures the bandwidth available both at the interface and bundle level when a specific number of ports in a LAG group fail.

Default

none

Parameters

lag-id

When the number of ports available in the LAG link is reduced by the number of ports configured in this context then the level-id specified here must be applied.

number-down number-lag-port-down

If the number of ports available in the LAG is reduced by the number of ports configured in this command here then bandwidth allowed for bundle and/or interface will be as per the levels configured in this context.

Values

1 — 64 (for 64-link LAG) 1 — 32 (for other LAGs)

level level-id

Specifies the amount of bandwidth available within a given bundle for MC traffic for a specified level.

number-down

Syntax

number-down number-lag-port-down level level-id

no number-down number-lag-port-down

Context

config>router>pim>if>mcac>mc-constraints

Description

This command configures the number of ports down along with level for multicast cac policy on this interface.

Default

none

Parameters

number-down number-lag-port-down

If the number of ports available in the LAG is reduced by the number of ports configured in this command here then bandwidth allowed for bundle and/or interface will be as per the levels configured in this context.

Values

1 — 64 (for 64-link LAG) 1 — 32 (for other LAGs)

level level-id

Specifies the amount of bandwidth available within a given bundle for MC traffic for a specified level.

level

Syntax

level level bw bandwidth

no level level

Context

config>router>mcac>policy>bundle>mc-constraints

Description

This command configures the amount of bandwidth available within a given bundle for MC traffic for a specified level. The amount of allowable BW for the specified level is expressed in kbps and this can be defined for up to eight different levels.

The no form of the command removes the level from the configuration.

Default

none (If no bandwidth is defined for a given level then no limit is applied.)

Parameters

level

Specifies the bandwidth for a given level. Level 1 has the highest priority. Level 8 has the lowest priority.

Values

1 — 8

bw bandwidth

Specifies the bandwidth, in kbps, for the level.

Values

1 — 2147483647 kbps

Default

1

number-down

Syntax

number-down number-lag-port-down level level-id

no number-down number-lag-port-down

Context

config>router>igmp>mcac>mc-constraints

Description

This command configures the number of ports down along with level for the MCAC policy.

Parameters

number-lag-port-down

Specifies the number of ports down along with level for the MCAC policy.

Values

1 — 64

level level-id

Specifies the bandwidth for a given level. Level 1 has the highest priority. Level 8 has the lowest priority.

Values

1 — 8

unconstrained-bw

Syntax

unconstrained-bw bandwidth mandatory-bw mandatory-bw

no unconstrained-bw

Context

configure>router>igmp>interface>mcac

configure>router>igmp>group-interface>mcac

configure>service>vprn>igmp>interface >mcac

config>router>mld>group-interace>mcac

configure>service>vprn>igmp>group-interface >mcac

configure>subscr-mgmt>sub-mcac-policy

Description

This command enables Mcac (or Hmcac) function on the corresponding level (subscriber, group-interface or redirected interface). When Mcac (or Hmcac) is enabled and a channel definition policy is referenced, admission control is performed. The allocated bandwidth for optional channels should not exceed the unconstrained-bw minus the mandatory-bw. The mandatory channels have to stay below the specified value for the mandatory-bw.

In Hmcac, the subscriber is checked first against its bandwidth limits followed by the check on the redirected interface or the group-interface against the bandwidth limits defined there.

In case that redirection is enabled and Hmcac enabled, the channel definition policy must be referenced under the redirected interface level. If it is referenced under the group-interface level, it will be ignored.

Subscriber Mcac (only subscriber is checked for available resources) is supported only with direct subscriber replication (no redirection). In this case the channel definition policy must be referenced under the group-interface.

In the case that the redirection is enabled but the policy is referenced ONLY under the group-interface, no admission control will be executed (Hmcac or Mcac).

Default

none

Parameters

bandwidth

Specifies the unconstrained bandwidth in kbps for the MCAC policy.

Values 0 — 2147483647

mandatory-bw mandatory-bw

Specifies the mandatory bandwidth in kbps for the MCAC policy.

Values 0 — 2147483647

use-lag-port-weight

Syntax

use-lag-port-weight

no use-lag-port-weight

Context

config>router>igmp>interface>mcac>mc-constraints

config>router>mld>interface>mcac>mc-constraints

config>router>pim>interface>mcac>mc-constraints

config>router>mcac>policy>bundle>mc-constraints

Description

This command enables port weight to be used when determining available bandwidth per level when LAG ports go down/come up. The command is required for proper operation on mixed port-speed LAGs and can be used for non-mixed port-speed LAGs as well.

Default

no use-lag-port-weight

port number is used when determining available BW per level when LAG ports go down/come up

default-action

Syntax

default-action {accept | discard}

Context

config>router>mcac>policy

Description

This command specifies the action to be applied to multicast streams (channels) when the streams do not match any of the multicast addresses defined in the MCAC policy.

When multiple default-action commands are entered, the last command will overwrite the previous command.

Default

discard (all multicast stream not defined in a MCAC policy will be discarded)

Parameters

accept

Specifies multicast streams (channels) not defined in the MCAC policy will be accepted.

discard

Specifies multicast streams (channels) not defined in the MCAC policy will be dropped.

shutdown

Syntax

[no] shutdown

Context

config>router>mcac>policy>bundle

Description

This 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.

When an entity is shutdown, the operational state of the entity is disabled as well as the operational state of any entities contained within. Many objects must be shutdown 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.

When a shutdown is performed then all constraints placed on either a bundle or an interface are removed and multicast can potentially take up the full bandwidth of the interface. Furthermore, when a no shutdown command is executed then policing of the policy must be in a gradual fashion. No active multicast groups may be removed. When a leave message is received for an optional channel then the multicast stream should be pruned and subsequent new joins can be denied in accordance with the policy. This may mean that for a period of time insufficient bandwidth is available even for mandatory channels.

 

MLD Commands

mld

Syntax

[no] mld

Context

config>router

Description

This command enables the context to configure Multicast Listener Discovery (MLD) parameters.

The no form of the command disables MLD.

Default

no mld

group-interface

Syntax

[no] group-interface ip-int-name

Context

config>router>mld

Description

This command creates and enables the context to configure MLD group interface parameters.

Parameters

ip-int-name

The IP interface name. Interface names must be unique within the group of defined IP interfaces for config router interface and config service ies interface commands. An interface name cannot be in the form of an IP address. Interface names can be any string up to 32 characters long composed of printable, 7-bit ASCII characters. If the string contains special characters (#, $, spaces, etc.), the entire string must be enclosed within double quotes.

grp-if-query-src-ip

Syntax

grp-if-query-src-ip ipv6-address

no grp-if-query-src-ip

Context

config>router>mld>group-interface

Description

This command configures the query source IPv6 address for all group interfaces.

The no form of the command removes the IP address.

Default

none

Parameters

ipv6-address

Sets the source IPv6 address for all group interfaces. The address can be up to 64 characters.

query-src-ip

Syntax

query-src-ip ipv6-address

no query-src-ip

Context

config>router>mld>group-interface

Description

This command configures the query source IPv6 address for the group interface. This IP address overrides the source IP address configured at the router level.

The no form of the command removes the IPv6 address.

Default

none

Parameters

ipv6-address

Sets the source IPv6 address for all subscriber’s IGMP queries.

interface

Syntax

[no] interface ip-int-name

Context

config>router>mld

Description

This command enables the context to configure an Multicast Listener Discovery (MLD) interface. The interface is a local identifier of the network interface on which reception of the specified multicast address is to be enabled or disabled.

The no form of the command deletes the MLD interface. The shutdown command in the config>router>mld>interface context can be used to disable an interface without removing the configuration for the interface.

Default

no interface — No interfaces are defined.

Parameters

ip-int-name

The IP interface name. Interface names must be unique within the group of defined IP interfaces for config router interface and config service ies interface commands. An interface name cannot be in the form of an IP address. Interface names can be any string up to 32 characters long composed of printable, 7-bit ASCII characters. If the string contains special characters (#, $, spaces, etc.), the entire string must be enclosed within double quotes.

If the IP interface name does not exist or does not have an IP address configured an error message will be returned.

If the IP interface exists in a different area it will be moved to this area.

disable-router-alert-check

Syntax

[no] disable-router-alert-check

Context

config>router>mld>if

Description

This command enables router alert checking for MLD messages received on this interface.

The no form of the command disables the router alert checking.

Default

none

import

Syntax

import policy-name

no import

Context

config>router>mld>if

Description

This command specifies the import route policy to be used for determining which membership reports are accepted by the router. Route policies are configured in the config>router>policy-options context.

When an import policy is not specified, all the MLD reports are accepted.

The no form of the command removes the policy association from the MLD instance.

Default

no import — No import policy specified.

Parameters

policy-name

The route policy name. Allowed values are any string up to 32 characters long composed of printable, 7-bit ASCII characters. If the string contains special characters (#, $, spaces, etc.), the entire string must be enclosed within double quotes. Route policies are configured in the config>router>policy-options context.

max-groups

Syntax

max-groups value

no max-groups

Context

config>router>mld>if

Description

This command specifies the maximum number of groups for which MLD can have local receiver information based on received MLD reports on this interface. When this configuration is changed dynamically to a value lower than the currently accepted number of groups, the groups that are already accepted are not deleted. Only new groups will not be allowed.

Default

0, no limit to the number of groups.

Parameters

value

Specifies the maximum number of groups for this interface.

Values 1 — 16000

 

query-interval

Syntax

query-interval seconds

no query-interval

Context

config>router>mld

config>router>mld>if

Description

This command specifies the frequency that the querier router transmits general host-query messages. The host-query messages solicit group membership information and are sent to the all-systems multicast group address, 224.0.0.1.

Default

125

Parameters

seconds

The time frequency, in seconds, that the router transmits general host-query messages.

Values 2 — 1024

query-last-member-interval

Syntax

query-last-member-interval seconds

Context

config>router>mld

config>router>mld>if

Description

This command configures the frequency at which the querier sends group-specific query messages including messages sent in response to leave-group messages. The lower the interval, the faster the detection of the loss of the last member of a group.

Default

1

Parameters

seconds

Specifies the frequency, in seconds, at which query messages are sent.

Values 1 — 1024

query-response-interval

Syntax

query-response-interval seconds

Context

config>router>mld

config>router>mld>if

Description

This command specifies how long the querier router waits to receive a response to a host-query message from a host.

Default

10

Parameters

seconds

Specifies the the length of time to wait to receive a response to the host-query message from the host.

Values 1 — 1023

static

Syntax

static

Context

config>router>mld>if

Description

This command tests multicast forwarding on an interface without a receiver host. When enabled, data is forwarded to an interface without receiving membership reports from host members.

Default

none

group

Syntax

[no] group ipv6-address

Context

config>router>mld>if>static

Description

This command enables the context to add a static multicast group either as a (*,G) or one or more (S,G) records. Use MLD static group memberships to test multicast forwarding without a receiver host. When MLD static groups are enabled, data is forwarded to an interface without receiving membership reports from host members.

When static MLD group entries on point-to-point links that connect routers to a rendezvous point (RP) are configured, the static MLD group entries do not generate join messages toward the RP.

The no form of the command removes the IPv6 address from the configuration.

Default

none

Parameters

ipv6-address

Specifies an MLD multicast group address that receives data on an interface. The IP address must be unique for each static group.

source

Syntax

[no] source ipv6-address

Context

config>router>mld>if>static>group

config>router>mld>ssm-translate>grp-range

Description

This command specifies an IPv6 unicast address that sends data on an interface. This enables a multicast receiver host to signal a router the group to receive multicast traffic from, and from the source(s) that the traffic is expected.

The source command is mutually exclusive with the specification of individual sources for the same group.

The source command, in combination with the group, is used to create a specific (S,G) static group entry.

The no form of the command removes the source from the configuration.

Default

none

Parameters

ip-address

Specifies the IPv6 unicast address.

starg

Syntax

[no] starg

Context

config>router>mld>if>static>group

Description

This command adds a static (*,G) entry. This command can only be enabled if no existing source addresses for this group are specified.

Use the no form of the command to remove the starg entry from the configuration.

Default

none

subnet-check

Syntax

[no] subnet-check

Context

config>router>mld>interface

Description

This command enables subnet checking for MLD messages received on this interface. All MLD packets with a source address that is not in the local subnet are dropped.

Default

enabled

version

Syntax

version version

no version

Context

config>router>mld>if

Description

This command specifies the MLD version. If routers run different versions, they will negotiate the lowest common version of MLD that is supported by hosts on their subnet and operate in that version. For MLD to function correctly, all routers on a LAN should be configured to run the same version of MLD on that LAN.

Default

1

Parameters

version

Specifies the MLD version number.

Values 1, 2

robust-count

Syntax

robust-count robust-count

no robust-count

Context

config>router>mld

Description

This command configures the robust count. The robust-count variable allows tuning for the expected packet loss on a subnet. If a subnet anticipates losses, the robust-count variable can be increased.

Default

2

Parameters

robust-count

Specify the robust count value.

Values 2 — 10

ssm-translate

Syntax

ssm-translate

Context

config>router>mld

Description

This command enables the context to configure group ranges which are translated to SSM (S,G) entries. If the static entry needs to be created, it has to be translated from a IGMPv1 IGMPv2 request to a Source Specific Multicast (SSM) join. An SSM translate source can only be added if the starg command is not enabled. An error message is generated if you try to configure the source command with starg command enabled.

grp-range

Syntax

[no] grp-range start end

Context

config>router>mld>ssm-translate

Description

This command is used to configure group ranges which are translated to SSM (S,G) entries.

Parameters

start

An IP address that specifies the start of the group range.

end

An IP address that specifies the end of the group range. This value should always be greater than or equal to the value of the start value.

 

 

source

Syntax

[no] source ip-address

Context

config>router>mld>ssm-translate>grp-range

Description

This command specifies the source IP address for the group range. Whenever a (*,G) report is received in the range specified by grp-range start and end parameters, it is translated to an (S,G) report with the value of this object as the source address.

Parameters

ip-address

Specifies the IP address that will be sending data.

 

 

Operational Commands

mrinfo

Syntax

mrinfo ip-address [router router-name|service]

Context

<GLOBAL>

Description

This command is used to display relevant multicast information from the target multicast router. Information displayed includes adjacency information, protocol, metrics, thresholds, and flags from the target multicast router. This information can be used by network operators to determine whether bi-directional adjacencies exist.

Parameters

ip-address

Specify the IP address of the multicast capable target router should be entered.

router router-name

Specify the router instance that this command applies to.

Default

management Base

service

Specify the service instance that this command applies to.

Values 1 — 2147483647

Mrinfo Output Fields

The following table describes the output fields:

Label	Description
General flags
version	Indicates software version on queried router.
prune	Indicates that router understands pruning.
genid	Indicates that router sends generation IDs.
mtrace	Indicates that the router handles mtrace requests.
Neighbors flags
1	Metric
0	Threshold (multicast time-to-live)
pim	PIM enabled on interface.
down	Operational status of interface.
disabled	Administrative status of interface.
leaf	No downstream neighbors on interface.
querier	Interface is IGMP querier.
tunnel	Neighbor reached via tunnel.

A:dut-f# mrinfo 10.1.1.2

10.1.1.2  [version 3.0,prune,genid,mtrace]:

  10.1.1.2 -> 10.1.1.1 [1/0/pim]

  16.1.1.1 -> 0.0.0.0 [1/0/pim/down/disabled]

  17.1.1.1 -> 0.0.0.0 [1/0/pim/querier/leaf]

  200.200.200.3 -> 200.200.200.5 [1/0/tunnel/pim]... 

mstat

Syntax

mstat source ip-address group grp-ip-address [destination dst-ip-address] [hop hop] [router router-name|service] [wait-time wait-time]

Context

<GLOBAL>

Description

This command traces a multicast path from a source to a receiver and displays multicast packet rate and loss information. The mstat command adds the capability to show the multicast path in a limited graphic display and provide drops, duplicates, TTLs, and delays at each node. This information is useful to network operators because it identifies nodes with high drop and duplicate counts. Duplicate counts are shown as negative drops.

Parameters

source ip-address

Specify the IP address of the multicast-capable source. This is a unicast address of the beginning of the path to be traced.

group group-ip-address

Specify the multicast address that will be used.

destination dst-ip-address

Specify the IP address of the unicast destination. If this parameter is omitted, the IP address of the system where the command is entered is used. The destination parameter can also be used to specify a local interface address as the destination address to send the trace query.

Default

The default address for the destination address is the incoming IETF format for that (S,G)

hop hop

Specify the maximum number of hops that will be traced from the receiver back toward the source.

Values 1 — 255

Default 32 (infinity for the DVMRP routing protocol).

router router-name

Specify the router instance that this command applies to.

service

Specify the service instance that this command applies to.

Values 1 — 2147483647

wait-time wait-time

Specify the number of seconds to wait for the response.

Values 1 — 60

Default

10

Mstat Output Fields

The following table describes the output fields:

Label	Description
hop	Number of hops from the source to the listed router.
router name	Name of the router for this hop or “?” when not reverse DNS translated.
address	Address of the router for this hop.
protocol	Protocol used.
ttl	Forward TTL threshold. TTL that a packet is required to have before it will be forwarded over the outgoing interface.
forwarding code	Forwarding information/error code for this hop.

 

For each interface between 2 nodes a line is printed, following the same layout as other routers with an implementation derived from mrouted. Note the following:

•	The forwarding information/error code is only displayed when different from “No Error”.

•	“?” means the there is no reverse DNS translation.

•	There is no “Overall Mcast Pkt Rate” available in the PE for the VPRN case.

 

mtrace

Syntax

mtrace source ip-address group grp-ip-address [destination dst-ip-address] [hop hop] [router router-name|service] [wait-time wait-time]

Context

<GLOBAL>

Description

This command traces the multicast path from a source to a receiver by passing a trace query hop-by-hop along the reverse path from the receiver to the source. At each hop, information such as the hop address, routing error conditions, and packet statistics are gathered and returned to the requestor. A network administrator can determine where multicast flows stop and verify the flow of the multicast stream.

Parameters

source ip-address

Specify the IP address of the multicast-capable source. This is a unicast address of the beginning of the path to be traced.

group group-ip-address

Specify the multicast address that will be used.

destination dst-ip-address

Specify the IP address of the unicast destination. If this parameter is omitted, the IP address of the system where the command is entered is used. The destination parameter can also be used to specify a local interface address as the destination address to send the trace query.

Default

The default address for the desination address is the incoming IETF format for that (S,G)

hop hop

Specify the maximum number of hops that will be traced from the receiver back toward the source.

Values 1 — 255

Default 32 hops (infinity for the DVMRP routing protocol).

router router-name

Specify the router instance that this command applies to.

service

Specify the service instance that this command applies to.

Values 1 — 2147483647

wait-time wait-time

Specify the number of seconds to wait for the response.

Values 1 — 60

Default

10

Mtrace Output Fields

The following table describes the output fields:

Label	Description
hop	Number of hops from the source to the listed router.
router name	Name of the router for this hop. If a DNS name query is not successful a “?” displays.
address	Address of the router for this hop.
protocol	Protocol used.
ttl	Forward TTL threshold. TTL that a packet is required to have before it will be forwarded over the outgoing interface.
forwarding code	Forwarding information/error code for this hop.