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.
The operational state of the entity is disabled as well as the operational state of any entities contained within. Many objects must be shut down before they can 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 enables the Internet Group Management Protocol (IGMP) context. When the context is created, the IGMP protocol is enabled.
The Internet Group Management Protocol (IGMP) is used by IPv4 systems (hosts and routers) to report their IP multicast group memberships to neighboring multicast routers. An IP multicast router can be a member of one or more multicast groups, in which case it performs both the “multicast router” part of the protocol, which collects the membership information needed by its multicast routing protocol, and the “group member” part of the protocol, which informs itself and other neighboring multicast routers of its memberships.
The no form of the command disables the IGMP instance. To start or suspend execution of IGMP without affecting the configuration, use the no shutdown command.
n/a
This command enables the context to configure an IGMP 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 IGMP interface. The shutdown command in the config>router>igmp>interface context can be used to disable an interface without removing the configuration for the interface.
no interface (no interfaces are defined)
If the IP interface name does not exist or does not have an IP address configured, an error message will be returned.
This command disables or enables router alert checking for IGMP messages received on the interface.
The no form of the command enables the IGMP router alert check option.
no disable-router-alert-check
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 (see the “Route Policies” section in the 7705 SAR OS Router Configuration Guide).
If an import policy is not specified, all the IGMP reports are accepted.
The no form of the command removes the policy association from the IGMP instance.
no import (no import policy specified)
This command specifies the maximum number of groups for which IGMP can have local receiver information based on received IGMP reports on this interface. If 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.
The no version of the command removes the configured value and the maximum number of groups is not defined.
no max-groups
This command enables the context to configure group ranges that are translated to SSM (S,G) entries. If the static entry needs to be created, it has to be translated from an IGMPv1 or IGMPv2 request to a Source-Specific Multicast (SSM) Join message.
This command adds or removes SSM translate group range entries. The group range is not created until the grp-range>source command is used to configure the source address.
n/a
This command specifies the source IP address for the group range. Whenever a (*,G) report is received in the range specified by the grp-range start and end parameters, it is translated to an (S,G) report with the value of this object as the source address.
n/a
This command allows multicast forwarding out an interface without having received a dynamic join report on that interface. The specific multicast traffic to be forwarded is configured using the static>group and static>group>source commands.
n/a
This command adds a static multicast (S,G) group membership to an IPv4 interface. When IGMP static groups are enabled, data is forwarded to an interface without receiving membership reports from host members. A possible use for IGMP static groups is to test multicast forwarding in the absence of an IGMP host receiver.
The group command, in combination with the source command, is used to create a specific (S,G) static group entry.
n/a
This command specifies the source IPv4 address (S) for the static IGMP group being configured. Multicast traffic to the group (G) will be forwarded out the interface on which this static group is configured if the source address in the IPv4 header of the multicast packets matches S.
The source command, in combination with the group command, is used to create a specific (S,G) static group entry.
The no form of the command removes the source from the configuration.
n/a
This command enables subnet checking for IGMP messages received on this interface. All IGMP packets with a source address that is not in the local subnet are dropped.
enabled
This command specifies the IGMP version. If routers run different versions of IGMP, they will negotiate the lowest common version of IGMP that is supported by hosts on their subnet and operate in that version. For IGMP to function correctly, all routers on a LAN must be configured to run the same version of IGMP on that LAN.
For IGMPv3, a multicast router that is also a group member performs both parts of IGMPv3, receiving and responding to its own IGMP message transmissions as well as those of its neighbors.
3
This command specifies the frequency at which the querying router transmits general host-query messages. Host-query messages solicit group membership information and are sent to the all-systems multicast group address, 224.0.0.1.
125
This command configures the frequency at which the querying router sends group-specific query messages, including messages sent in response to leave-group messages. The shorter the interval, the faster the detection of the loss of the last member of a group.
1
This command specifies how long the querying router waits to receive a response to a host-query message from a host.
10
This command configures the robust count, which is the number of times the router will retry a query. 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.
2
This command enables the context to configure Multicast Listener Discovery (MLD) parameters.
The no form of the command disables MLD.
no mld
This command enables the context to configure an 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.
no interface (no interfaces are defined)
If the IP interface name does not exist or does not have an IP address configured, an error message will be returned.
This command enables or disables the router alert checking for MLD messages received on this interface.
The no form of the command enables the MLD router alert check option.
no disable-router-alert-check (enabled)
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.
If 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.
no import (no import policy specified)
This command specifies the maximum number of groups for which MLD can have local receiver information based on received MLD reports on this interface. If 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.
The no version of the command removes the configured value and the maximum number of groups is not defined.
no max-groups
This command specifies the frequency at which the querying router transmits general host-query messages. Host-query messages solicit group membership information and are sent to the all-systems multicast group address, 224.0.0.1.
125
This command configures the frequency at which the querying router sends group-specific query messages, including messages sent in response to leave-group messages. The shorter the interval, the faster the detection of the loss of the last member of a group.
1
This command specifies how long the querying router waits to receive a response to a host-query message from a host.
10
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.
2
This command enables the context to configure group ranges that are translated to SSM (S,G) entries. If the static entry needs to be created, it has to be translated from an MLDv1 request to a Source-Specific Multicast (SSM) Join message.
This command is used to configure group ranges that are translated to SSM (S,G) entries.
n/a
This command specifies the source IPv6 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.
n/a
This command allows multicast forwarding out an interface without having received a dynamic join report on that interface. The specific multicast traffic to be forwarded is configured using the static>group and static>group>source commands.
n/a
This command adds a static multicast (S,G) group membership to an IPv6 interface. When MLD static groups are enabled, data is forwarded to an interface without receiving membership reports from host members. A possible use for MLD static groups is to test multicast forwarding in the absence of an MLD host receiver.
The no form of the command removes the IPv6 address from the configuration.
n/a
This command specifies the source IPv6 address (S) for the static MLD group being configured. Multicast traffic to the group (G) will be forwarded out the interface on which this static group is configured if the source address in the IPv6 header of the multicast packets matches S.
The source command, in combination with the group command, is used to create a specific (S,G) static group entry.
The no form of the command removes the source from the configuration.
n/a
This command specifies the MLD version. If routers run different versions of MLD, 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 must be configured to run the same version of MLD on that LAN.
2
This command configures a Protocol Independent Multicast (PIM) instance.
PIM is used for multicast routing within the network. Devices in the network can receive the multicast feed requested and non-participating routers can be pruned. The 7705 SAR supports PIM Source-Specific Multicast (SSM).
The no form of the command deletes the PIM instance and removes all configuration parameters.
no pim
This command automatically creates or removes PIM interfaces. The ies, non-ies, and all options create a PIM interface with default PIM parameters when a new IP or IES interface is created manually. The none option removes any automatically created PIM interfaces that have not been modified manually in the PIM context. Existing manually created or modified PIM interfaces are not affected.
The default option for the apply-to command is none, so to activate its automatic behavior it must first be saved in the PIM configuration structure. Then, all subsequent commands either create new structures (in the case of IP or IES interface commands) or modify the default values created by the apply-to command (in the case of PIM interface commands).
For example, assume that the apply-to setting is none and that two manually created PIM interfaces already exist. If the apply-to setting is changed to ies, then the two manually created PIM interfaces remain unchanged but any newly created or modified IES interfaces will automatically create a corresponding PIM interface with default PIM values. Subsequently, if the apply-to command is changed back to none, then all PIM interfaces that were not manually created or modified are removed.
If a manually created or modified PIM interface is deleted, the interface will be recreated when (re)processing the apply-to command. If PIM is not required on a specific interface, then a config>router>pim>if>shutdown command should be executed.
none (keyword)
This command specifies the import route policy to be used by PIM. Route policies are configured in the config>router>policy-options context.
If an import policy is not specified, IGP routes are accepted by default. Up to five import policy names can be specified.
The no form of the command removes the policy association from the instance.
no import join-policy
This command creates a logical IP routing interface.
The no form of the command removes the IP interface and all the associated configurations.
no interfaces or names are defined within PIM
If the ip-int-name already exists, the context is changed to maintain that IP interface. If ip-int-name does not exist, the interface is created and the context is changed to that interface for further command processing.
This command configures the period for refreshes of PIM Assert messages on an interface.
The no form of the command removes the assert period from the configuration.
no assert-period
This command enables the use of IPv4 or IPv6 Bidirectional Forwarding Detection (BFD) to control the state of the associated protocol interface. By enabling BFD on a given protocol interface, the state of the protocol interface is tied to the state of the BFD session between the local node and the remote node. The parameters used for BFD are set via the BFD command under the IP interface.
The no form of this command removes BFD from the associated IGP protocol adjacency.
no bfd-enable
This command configures the time interval between PIM Hello messages transmitted on this interface.
The no form of this command reverts to the default value of the hello-interval.
30
This command configures the multiplier used to determine the hold time for a PIM neighbor on this interface.
The hello-multiplier in conjunction with the hello-interval determines the hold time for a PIM neighbor.
The multiplier value is expressed in deci-units, so that (for example) 10 deci-units represents a multiplier of 1 and 35 deci-units represents a multiplier of 3.5. For example, if the hello-interval is 1 s and the hello-multiplier is 35 deci-units, then the calculated hold time (in seconds) is:
hold time = (hello-interval * hello-multiplier) / 10 = (1 s * 35 deci-units) / 10 = 3.5 s
This allows the PIM default timeout of 3.5 seconds to be supported.
This command enables or disables instant PruneEcho for a PIM interface.
no instant-prune-echo
This command administratively disables or enables PIM operation for IPv4.
no ipv4-multicast-disable
This command administratively disables or enables PIM operation for IPv6.
no ipv6-multicast-disable
This command specifies the maximum number of groups for which PIM can have local receiver information based on received PIM reports on this interface. If 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. This command is applicable for IPv4 and IPv6.
The no version of the command removes the configured value and the maximum number of groups is not defined.
no max-groups
This command sets the priority value that is used to elect the designated router (DR). The DR election priority is a 32-bit unsigned number and the router with numerically largest dr-priority value is always the preferred DR.
The no form of the command restores the default values.
1
This command enables sticky-dr operation on this interface. When enabled, the priority in PIM Hello messages sent on this interface when elected as the designated router (DR) will be modified to the value configured in dr-priority. This is done to avoid the delays in forwarding caused by DR recovery, when switching back to the old DR on a LAN when it comes back up.
By enabling sticky-dr on this interface, it will continue to act as the DR for the LAN even after the old DR comes back up.
The no form of the command disables sticky-dr operation on this interface.
no sticky-dr (disabled)
This command enables three-way hello. By default, three-way hello is disabled on all interfaces and the standard two-way hello is supported.
no three-way-hello
This command sets the T-bit in the LAN Prune Delay option of the Hello Message. This indicates the router’s capability to enable Join message suppression. This capability allows for upstream routers to explicitly track Join memberships.
no tracking-support
This command specifies whether the router should ignore the designated router state and attract traffic even when it is not the designated router.
An operator can configure an interface (router or IES) to IGMP for PIM. The interface IGMP state will be synchronized to the backup node if it is associated with the redundant peer port. The interface can be configured to use PIM, which will cause multicast streams to be sent to the elected DR only. The DR will also be the router sending traffic to the DSLAM. Since it may be required to attract traffic to both routers, a non-dr-attract-traffic flag can be used in the PIM context to have the router ignore the DR state and attract traffic if it is not the DR. Note that while using this flag, the router may not send the stream down to the DSLAM while it is not the DR.
When enabled, the designated router state is ignored. When disabled, the designated router value is honored.
no non-dr-attract-traffic
This command provides access to the bootstrap import and export policy commands.
The 7705 SAR cannot become a Rendezvous Point (RP); however, it may be present in a network that has one or more RPs. The 7705 SAR handles Register messages by allowing the configuration of policies that will drop incoming Register messages silently, or send Register-Stop messages if the policy action is set to “accept” or if no policy action is assigned.
This command applies export policies to the PIM configuration. The policies control the flow of bootstrap messages from the RP. Up to five policy names can be specified.
Bootstrap export policies are created using the config>router>policy-options>policy-statement command. For more information on configuring bootstrap policies, refer to the “Configuring PIM Join Policies” section of the 7705 SAR OS Router Configuration Guide.
no bootstrap-export
This command applies import policies to the PIM configuration. The policies control the flow of bootstrap messages to the RP. Up to five policy names can be specified.
Bootstrap import policies are created using the config>router>policy-options>policy-statement command. For more information on configuring bootstrap policies, refer to the “Configuring PIM Join Policies” section of the 7705 SAR OS Router Configuration Guide.
no bootstrap-import
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 the RPF interface towards the source/rendezvous point. However the operator can specify the following:
rtable-u
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 the RPF interface towards the source/rendezvous point. However the operator can specify the following:
rtable6-u
This command enables the context to display IGMP information.
This command displays the multicast group and (S,G) addresses. If no grp-ip-address parameters are specified, then all IGMP group, (*,G) and (S,G) addresses are displayed.
The following output is an example of IGMP group information, and Table 2 describes the fields.
Label | Description |
IGMP Host Groups Summary | The IP multicast sources corresponding to the IP multicast groups that are statically configured |
Nbr Fwd Hosts | The number of forwarding hosts |
Nbr Blk Hosts | The number of blocking hosts |
This command displays IGMP interface information.
The following output is an example of IGMP interface information, and Table 3 describes the fields.
Label | Description |
Interface | The interface that participates in the IGMP protocol |
Adm Admin Status | The administrative state for the IGMP protocol on this interface |
Querier | The address of the IGMP querier on the IP subnet to which the interface is attached |
Oper Oper Status | The current operational state of the IGMP protocol on the interface |
Querier Up Time | The time since the querier was last elected as querier |
Querier Expiry Time | The time remaining before the querier ages out. If the querier is the local interface address, the value will be zero. |
Cfg/Opr Version Admin/Oper version | Cfg — the configured version of IGMP running on this interface. For IGMP to function correctly, all routers on a LAN must be configured to run the same version of IGMP on that LAN. Opr — the operational version of IGMP running on this interface. If the cfg value is 3 but all of the routers in the local subnet of this interface use IGMPv1 or IGMPv2, the operational version will be v1 or v2 (as appropriate). |
Num Groups | The number of multicast groups that have been learned by the router on the interface |
Policy | The policy that is to be applied on the interface |
Group Address | The IP multicast group address for which this entry contains information |
Up Time | The time since this source group entry got created |
Last Reporter | The IP address of the source of the last membership report received for this IP multicast group address on this interface. If no membership report has been received, this object has the value 0.0.0.0. |
Mode | The mode is based on the type of membership report(s) received on the interface for the group. Include — reception of packets sent to the specified multicast address is requested only from those IP source addresses listed in the source-list parameter of the IGMP membership report Exclude — reception of packets sent to the given multicast address is requested from all IP source addresses except those listed in the source-list parameter |
V1 Host Timer | The time remaining until the local router assumes that there are no longer any IGMPv1 members on the IP subnet attached to this interface. Upon hearing any IGMPv1 membership report, this value is reset to the group membership timer. While this time remaining is non-zero, the local router ignores any IGMPv2 Leave messages for this group that it receives on this interface. |
V2 Host Timer | The time remaining until the local router assumes that there are no longer any IGMPv2 members on the IP subnet attached to this interface. Upon hearing any IGMPv2 membership report, this value is reset to the group membership timer. While this time remaining is non-zero, the local router ignores any IGMPv3 Leave messages for this group that it receives on this interface. |
Type | Indicates how this group entry was learned. If this group entry was learned by IGMP, it will be set to “dynamic”. For statically configured groups, the value will be set to “static”. |
Compat Mode | Used in order for routers to be compatible with older version routers. IGMPv3 hosts must operate in version 1 and version 2 compatibility modes. IGMPv3 hosts must keep track of the state per local interface regarding the compatibility mode of each attached network. A host’s compatibility mode is determined from the Host Compatibility Mode variable, which can be in one of three states: IGMPv1, IGMPv2 or IGMPv3. This variable is kept per interface and is dependent on the version of General Queries heard on that interface as well as the Older Version Querier Present timers for the interface. |
This command displays IGMP SSM translate configuration information.
The following output is an example of IGMP ssm-translate configuration information, and Table 4 describes the fields.
Label | Description |
Group Range | The address ranges of the multicast groups to which this router can belong |
Source | The unicast address that sends data on an interface |
Interface | The name of the interface |
SSM Translate Entries | The total number of SSM translate entries |
This command displays static IGMP, (*,G), and (S,G) information.
The following output is an example of static IGMP information, and Table 5 describes the fields.
Label | Description |
Source | The entries that represent a source address from which receivers are interested or not interested in receiving multicast traffic |
Group | The IP multicast group address for which this entry contains information |
Interface | The interface name |
This command displays IGMP statistics information.
The following output is an example of IGMP statistic information, and Table 6 describes the fields.
Label | Description |
IGMP Interface Statistics | |
Message Type | Queries — The number of IGMP general queries transmitted or received on this interface |
Report — The total number of IGMPv1, IGMPv2, or IGMPv3 reports transmitted or received on this interface | |
Leaves — The total number of IGMP leaves transmitted on this interface | |
Received | The total number of IGMP packets received on this interface |
Transmitted | The total number of IGMP packets transmitted from this interface |
General Interface Statistics | |
Bad Length | The total number of IGMP packets with bad length received on this interface |
Bad Checksum | The total number of IGMP packets with bad checksum received on this interface |
Unknown Type | The total number of IGMP packets with unknown type received on this interface |
Bad Receive If | The total number of IGMP packets incorrectly received on this interface |
Rx Non Local | The total number of IGMP packets received from a non-local sender |
Rx Wrong Version | The total number of IGMP packets with wrong versions received on this interface |
Policy Drops | The total number of times that the IGMP protocol instance matched the host IP address or group/source addresses specified in the import policy |
No Router Alert | The total number of IGMPv3 packets received on this interface that did not have the router alert flag set |
Rx Bad Encodings | The total number of IGMP packets with bad encoding received on this interface |
Local Scope Pkts | The total number of IGMP packets received with scope field of node-local on this interface |
Resvd Scope Pkts | The total number of IGMP packets with reserved scope on this interface |
Source Group Statistics | |
(S,G) | The total number of (S,G)s for IGMP |
(*,G) | The total number of (*,G)s for IGMP |
This command displays IGMP status information. If IGMP is not enabled, the following message appears:
The following output is an example of IGMP status information, and Table 7 describes the fields.
Label | Description |
Admin State | The administrative status of IGMP |
Oper State | The current operating state of this IGMP protocol instance on this router |
Query Interval | The frequency at which IGMP query packets are transmitted |
Last Member Query Interval | The maximum response time inserted into group-specific queries sent in response to leave group messages Also, the amount of time between group-specific query messages |
Query Response Interval | The maximum query response time advertised in IGMPv2 queries |
Robust Count | The number of times the router will retry a query |
This command enables the context to display MLD information.
This command displays MLD group information.
The following output is an example of MLD group information, and Table 8 describes the fields.
Label | Description |
Up Time | The length of time that the interface has been part of the MLD group |
Fwd List | The forwarding list associated with the MLD group |
This command displays MLD interface information.
The following output is an example of MLD interface information, and Table 9 describes the fields.
Label | Description |
MLD Interface | |
Interface | The interface that participates in the MLD protocol |
Admin Status | The administrative state for the MLD protocol on this interface |
Oper Status | The current operational state of the MLD protocol on the interface |
Querier | The address of the MLD querier on the IP subnet to which the interface is attached |
Querier Up Time | The time since the querier was last elected as querier |
Querier Expiry Time | The time remaining before the querier ages out. If the querier is the local interface address, the value will be zero. |
Time for next query | The time until the next query is sent |
Admin/Oper version | The operational version of MLD running on this interface. If the cfg value is 2 but all of the routers in the local subnet of this interface use MLDv1, the operational version will be v1. |
Num Groups | The number of multicast groups that have been learned by the router on the interface |
Policy | The policy that is to be applied on the interface |
Max Groups Allowed | The maximum number of groups allowed for this interface |
Max Groups Till Now | The maximum number of groups joined for this interface up until the present time |
Query Interval | The frequency at which MLD query packets are transmitted |
Query Resp Interval | The length of time that the interface will wait for a query response |
Last List Qry Interval | The maximum response time inserted into group-specific queries sent in response to leave group messages Also, the amount of time between group-specific query messages |
Router Alert Check | The status of the MLD message router alert check: enabled or disabled. When enabled (default), messages without the hop-by-hop router alert extension header in the IPv6 header will be rejected. |
MLD Group | |
Group Address | The IPv6 multicast group address for which this entry contains information |
Last Reporter | The IPv6 address of the source of the last membership report received for this IP multicast group address on this interface. If no membership report has been received, this object has the value 0.0.0.0. |
Interface | The interface that participates in the MLD protocol |
Expires | The length of time until the interface leaves the MLD group |
Up Time | The time since this source group entry got created |
Mode | The mode is based on the type of membership report(s) received on the interface for the group. Include — reception of packets sent to the specified multicast address is requested only from those IP source addresses listed in the source-list parameter of the IGMP membership report Exclude — reception of packets sent to the given multicast address is requested from all IP source addresses except those listed in the source-list parameter |
V1 Host Timer | The time remaining until the local router assumes that there are no longer any MLDv1 members on the IP subnet attached to this interface. Upon hearing any MLDv1 membership report, this value is reset to the group membership timer. While this time remaining is non-zero, the local router ignores any MLDv2 Leave messages for this group that it receives on this interface. |
Type | Indicates how this group entry was learned. If this group entry was learned by MLD, it will be set to “dynamic”. For statically configured groups, the value will be set to “static”. |
Compat Mode | Used in order for routers to be compatible with older version routers. MLDv2 hosts must operate in version 1 compatibility mode. MLDv2 hosts must keep track of the state per local interface regarding the compatibility mode of each attached network. A host’s compatibility mode is determined from the Host Compatibility Mode variable, which can be in one of two states: MLDv1 or MLDv2. This variable is kept per interface and is dependent on the version of General Queries heard on that interface as well as the Older Version Querier Present timers for the interface. |
Source | |
Expires | The length of time until the source leaves the MLD group |
Type | The type of message that was used to join the source: dynamic or static |
Fwd/Blk | The state of the source: forwarding or blocking |
This command displays the MLD SSM translate configuration.
The following output is an example of MLD ssm-translate information, and Table 10 describes the fields.
Label | Description |
Group Range | The address range of the multicast group for this interface |
Source | The unicast address that sends data on an interface |
Interface | The name of the interface |
SSM Translate Entries | The total number of SSM translate entries |
This command displays MLD static group and source configuration.
The following output is an example of MLD static group and source configuration information, and Table 11 describes the fields.
Label | Description |
Source | The entries that represent a source address from which receivers are interested or not interested in receiving multicast traffic |
Group | The IP multicast group address for which this entry contains information |
Interface | The IPv6 interface name |
This command displays MLD statistics.
The following output is an example of MLD statistics information, and Table 12 describes the fields.
Label | Description |
MLD Interface Statistics | |
Message Type | Queries — the number of MLD general queries transmitted or received on this interface |
Reports — the total number of MLDv1 or MLDv2 reports transmitted or received on this interface | |
Dones — the total number of MLD dones transmitted on this interface | |
Received | The total number of MLD packets received on this interface |
Transmitted | The total number of MLD packets transmitted from this interface |
General Interface Statistics | |
Bad Length | The total number of MLD packets with bad length received on this interface |
Bad Checksum | The total number of MLD packets with bad checksum received on this interface |
Unknown Type | The total number of MLD packets with unknown type received on this interface |
Bad Receive If | The total number of MLD packets incorrectly received on this interface |
Rx Non Local | The total number of MLD packets received from a non-local sender |
Rx Wrong Version | The total number of MLD packets with wrong versions received on this interface |
Policy Drops | The total number of times that the MLD protocol instance matched the host IP address or group/source addresses specified in the import policy |
No Router Alert | The total number of MLDv2 packets received on this interface that did not have the router alert flag set |
Rx Bad Encodings | The total number of MLD packets with bad encoding received on this interface |
Rx Pkt Drops | The number of receive packets dropped by this interface |
Local Scope Pkts | The total number of MLD packets received with scope field of node-local on this interface |
Resvd Scope Pkts | The total number of MLD packets with reserved scope on this interface |
Source Group Statistics | |
(S,G) | The total number of (S,G)s for MLD |
(*,G) | The total number of (*,G)s for MLD |
This command displays the MLD status.
The following output is an example of MLD status information, and Table 13 describes the fields.
Label | Description |
Admin State | The administrative status of MLD |
Oper State | The current operating state of this MLD protocol instance on this router |
Query Interval | The frequency at which MLD query packets are transmitted |
Last Listener Query Interval | The maximum response time inserted into group-specific queries sent in response to leave group messages Also, the amount of time between group-specific query messages |
Query Response Interval | The maximum query response time advertised in MLDv2 queries |
Robust Count | The number of times the router will retry a query |
This command enables the context to display PIM information.
This command displays PIM source group database information.
The following output is an example of PIM group information, and Table 14 describes the fields.
Label | Description |
Group Address | The IP multicast group address for which this entry contains information |
Source Address | The source address of the multicast sender |
RP Address | Always set to 0 (zero) |
Flags | The lists to which this interface belongs |
Type | The type of entry: (*,*, rp)/(*,G) or (S,G) The 7705 SAR only supports and will only indicate (S,G) |
Spt Bit | Specifies whether to forward on (*,*, rp)/(*,G) or on (S,G) state. It is updated when the (S,G) data comes on the RPF interface towards the source. The 7705 SAR only supports and will only indicate (S,G) |
Inc Intf | The incoming interface on which the traffic arrives (that is, the RPF interface to the source) |
No. Oifs | The number of interfaces in the inherited outgoing interface list, where an inherited list inherits the state from other types |
MRIB Next Hop | The next-hop address towards the source |
MRIB Src Flags | The MRIB information about the source |
Keepalive Timer | The keepalive timer is applicable only for (S,G) entries The (S,G) keepalive timer is updated by data being forwarded using this (S,G) Forwarding state. It is used to keep the (S,G) state alive in the absence of explicit (S,G) joins. |
Up Time | The length of time since this source group entry was created |
Resolved By | The route table used for the RPF check |
Up JP State | The upstream Join Prune state for this entry on the interface. PIM Join Prune messages are sent by the downstream routers towards the RPF neighbor. |
Up JP Expiry | The minimum amount of time remaining before this entry will be aged out |
Up JP Rpt | The Join Prune Rpt state for this entry on the interface. PIM Join Prune messages are sent by the downstream routers towards the RPF neighbor. The (S,G, rpt) state is a result of receiving an (S,G, rpt) JP message from the downstream router on the source tree. |
Up JP Rpt Override | The value used to delay triggered Join (S,G, rpt) messages to prevent implosions of triggered messages If this has a non-zero value, it means that the router was in a “notPruned”state and it saw a prune (S,G, rpt) message being sent to the RPF (S,G, rpt). If the router sees a join (S,G, rpt) override message being sent by some other router on the LAN while the timer is still non-zero, it simply cancels the override timer. If it does not see a join (S,G, rpt) message, then on expiry of the override timer, it sends its own join (S,G, rpt) message to the RPF (S,G, rpt). |
Register State | The register state: always displays “No info” |
Register Stop Exp | The time remaining before the register state might transition to a different state |
Reg from Anycast RP | The receive status of the Register packet for that group from one of the RPs from the anycast-RP set: always displays “No” |
RPF Neighbor | The address of the Reverse Path Forwarding (RPF) neighbor |
Outgoing Intf List | A list of interfaces on which data is forwarded |
Curr Fwding Rate | The current forwarding rate of the multicast data for this group and source |
Forwarded Packets | The number of multicast packets that were forwarded to the interfaces in the outgoing interface list |
Discarded Packets | The number of multicast packets that matched this source group entry but were discarded For (S,G) entries, if the traffic is getting forwarded on the SPT (Shortest Path Tree), the packets arriving from the RPT will be discarded |
Forwarded Octets | The number of octets forwarded |
RPF Mismatches | The number of multicast packets that matched this source group entry but they did not arrive on the interface |
Spt threshold | The value of the SPT threshold configured for that group: 0 kbps means that the switch to the SP tree will happen immediately |
This command displays PIM interface information and the (S,G) state of the interface.
The following output is an example of PIM interface information, and Table 15 describes the fields.
Label | Description |
PIM Interface | |
Admin Status | The administrative state for the PIM protocol on this interface |
Oper Status | The current operational state of the PIM protocol on this interface |
IPv4 Admin Status | The administrative state for the PIM protocol on this interface |
IPv4 Oper Status | The current operational state of the PIM protocol on this interface |
DR | The designated router on this PIM interface |
Oper DR Priority | The priority of the operational designated router |
BSM RA Check | Not applicable |
Cfg DR Priority | The priority value sent in PIM Hello messages that is used by routers to elect the designated router (DR) |
Hello Interval | The time interval at which PIM Hello messages are transmitted on this interface |
Time for next hello | The time when the next PIM Hello message will be transmitted |
Hello Multiplier | The value of the hello multiplier |
J/P Tracking Admin | The administrative state for Join Prune message tracking: Enabled or Disabled |
J/P Tracking Oper | The operational state for Join Prune message tracking: Enabled or Disabled |
Auto-created | Specifies whether the PIM interface was auto-created: Yes or No |
Improved Assert | Specifies whether the improved assert processing on this interface is Enabled or Disabled. The 7705 SAR supports only Enabled (that is, the PIM assert process is done entirely on the control plane with no interaction between the control and forwarding planes). |
Sticky-DR | The configured state of sticky-DR: Enabled or Disabled |
Sticky-DR Priority | Not applicable |
Max Groups Allowed | The maximum number of groups allowed for this interface |
Max Groups Till Now | The maximum number of groups joined for this interface up until the present time |
Num Groups | The current number of groups joined for this interface |
Bfd enabled | Specifies whether BFD is enabled: Yes or No |
Three-way Hello | The state of the three-way hello parameter: Enabled or Disabled |
Assert-Period | The period for refreshes of PIM Assert messages on an interface |
Instant Prune Echo | The state of the instant prune echo: Enabled or Disabled |
PIM Group Source | |
Group Address | The group IP address for this PIM group |
Source Address | The unicast source IP address for this PIM group |
Interface | The PIM IP address for this PIM interface |
Type | The type of multicast group |
RP Address | The IP address of the Rendezvous Point for this PIM interface |
Up Time | The time since this PIM interface joined the multicast group |
Join Prune State | The Join Prune state for this PIM interface and multicast group |
Expires | The length of time until this PIM interface leaves the multicast group |
Prune Pend Expires | Not applicable |
Assert State | The PIM assert message state |
This command displays PIM neighbor information.
This information can be important if an interface has more than one adjacency. For example, assume a LAN interface configuration has three routers connected and all the routers are running PIM on their LAN interfaces. These routers have two adjacencies on their LAN interface, each with different neighbors. If the address neighbor-ip-address parameter is not defined in this example, then the show command output would display two adjacencies instead of only the one adjacency of the neighbor whose IP address is specified.
The following output is an example of PIM neighbor information, and Table 16 describes the fields.
Label | Description |
Interface | The interface name of the neighbor |
Nbr DR Priority | The value of the DR priority of the neighbor, which is received in the Hello message |
Nbr Address | The IP address of the neighbor |
Up Time | The time since this PIM neighbor (last) became a neighbor of the local router |
Expiry Time | The minimum time remaining before this PIM neighbor will be aged out A value of 0 (zero) means that this neighbor will never be aged out, which occurs when the PIM neighbor sends a Hello message with hold time set to 0xffff |
Hold Time | The value of the hold time present in the Hello message |
DR Priority | The value of the DR priority of the neighbor, which is received in the Hello message |
Tracking Support | Indicates the presence of the T-bit in the LAN prune delay option in the Hello message: Yes or No, which indicates the neighbor's capability to disable Join message suppression |
LAN Delay (ms) | The value of the LAN delay field present in the Hello message received from the neighbor |
Gen Id | A randomly generated 32-bit value that is regenerated each time PIM forwarding is started or restarted on the interface, including when the router itself restarts. When a Hello message with a new GenID is received from a neighbor, any old Hello information about that neighbor is discarded and superseded by the information from the new Hello message. |
Override Intvl (ms) | The value of the override interval present in the Hello message |
This command displays statistics for a particular PIM instance.
The following output is an example of PIM statistics output information, and Table 17 describes the fields.
Label | Description |
PIM Statistics | |
Message Type | Hello — the number of PIM Hello messages received or transmitted on this interface Join Prune — the number of PIM Join Prune messages received or transmitted on this interface Asserts — the number of PIM Assert messages received or transmitted on this interface Register — the number of Register messages received or transmitted on this interface Null Register — the number of PIM Null Register messages received or transmitted on this interface Register Stop — the number of PIM Register Stop messages received or transmitted on this interface BSM — the number of PIM Bootstrap messages (BSM) received or transmitted on this interface Candidate RP Adv — the number of candidate RP advertisements Total Packets — the total number of packets transmitted and received on this interface |
Received | The number of messages received on this interface |
Transmitted | The number of multicast data packets transmitted on this interface |
Rx Errors | The total number of receive errors |
General Statistics | |
Rx Invalid Register | The number of invalid PIM Register messages received on this interface |
Rx Neighbor Unknown | The number of PIM messages (other than Hello messages) that were received on this interface and were rejected because the adjacency with the neighbor router was not already established |
Rx Bad Checksum Discard | The number of PIM messages received on this interface that were discarded because of a bad checksum |
Rx Bad Encoding | The number of PIM messages with bad encodings received on this interface |
Rx Bad Version Discard | The number of PIM messages with bad versions received on this interface |
Rx CRP No Router Alert | The number of candidate-rp advertisements (C-RP-Adv) received on this interface that had no router alert option set |
Rx BSM Router Alert Drops | The number of router alert bootstrap message alerts that have been dropped on this interface |
Rx BSM Wrong If Drops | The number of bootstrap messages not meant to be received on this interface |
Rx Invalid Join Prune | The number of invalid PIM Join Prune messages received on this interface |
Rx Unknown PDU Type | The number of packets received with an unsupported PIM type |
Join Policy Drops | The number of times the join policy match resulted in dropping a PIM Join Prune message or one of the source groups contained in the message |
Register Policy Drops | The number of times the register policy match resulted in dropping a PIM Register message |
Bootstrap Import Policy Drops | The number of Bootstrap messages received on this interface that were dropped because of Bootstrap import policy |
Bootstrap Export Policy Drops | The number of Bootstrap messages that were not transmitted on this interface because of Bootstrap export policy |
Fwd Candidate RP Adv | The number of candidate RP advertisements that were forwarded by the router |
Fwd Candidate RP Adv Drops | The number of candidate RP advertisements that were dropped by the router |
Source Group Statistics | |
(S,G) | The number of entries in which the type is (S,G) |
(*,G) | The number of entries in which the type is (*,G) |
(*,*,RP) | The number of entries in which the type is (*, *, rp) |
This command displays the PIM status. The Oper Status indicates the combined operational status of IPv4/IPv6 PIM protocol status. If both are down, then Oper Status will be shown as down. If IPv4 or IPv6 is up, the Oper Status will indicate up.
If PIM is not enabled, the following message appears:
The following output is an example of PIM status information, and Table 18 describes the fields.
Label | Description |
Admin State | The administrative status of PIM |
Oper State | The current operating state of this PIM protocol instance |
IPv4 Admin State IPv6 Admin State | The administrative status of PIM |
IPv4 Oper State IPv6 Oper State | The current operating state of this PIM protocol instance |
BSR State | The state of the router with respect to the Bootstrap mechanism |
Elected BSR | Address — the address of the elected Bootstrap router Expiry Time — the time remaining before the router sends the next Bootstrap message Priority — the priority of the elected Bootstrap router. The higher the value, the higher the priority. Hash Mask Length — the hash mask length of the Bootstrap router Up Time — the time since the current E-BSR became the Bootstrap router RPF Intf towards E-BSR — the RPF interface towards the elected BSR. The value is zero if there is no elected BSR in the network. |
Policy | The PIM policies for a particular PIM instance |
RPF Table | The route table used for the RPF check |
Non-DR-Attract-Traffic | Indicates whether the router ignores the designated router state and attracts traffic even when it is not the designated router |
This command enables the context to clear and reset IGMP entities.
This command clears IGMP database statistics on a specified interface or IP address.
This command clears IGMP statistics on a specified interface or IP address.
Note that interface and group/source cannot be specified at the same time.
This command clears IGMP version parameters.
This command enables the context to clear and reset MLD entities.
This command clears MLD database parameters.
This command clears MLD statistics parameters.
This command clears MLD version parameters.
This command enables the context to clear and reset PIM entities.
This command clears PIM database statistics on a specified interface or IP address.
This command clears PIM neighbor data on a specified interface or IP address.
This command clears PIM statistics.
This command enables access to the IGMP debug commands.
This command enables debugging for IGMP interfaces.
The no form of the command disables the IGMP interface debugging for the specified interface name or IP address.
This command enables debugging for IGMP miscellaneous information.
The no form of the command disables the debugging.
This command enables debugging for IGMP packets.
The no form of the command disables the debugging.
This command enables access to the MLD debug commands.
This command enables debugging for MLD interfaces.
The no form of the command disables the MLD interface debugging for the specified interface name or IP address.
This command enables debugging for MLD miscellaneous information.
The no form of the command disables the debugging.
This command enables debugging for MLD packets.
The no form of the command disables the debugging.
This command enables access to the PIM debug commands.
This command enables debugging for PIM adjacencies.
The no form of the command disables debugging.
This command enables debugging for all the PIM groups.
The no form of the command disables debugging.
This command enables debugging for the PIM assert mechanism.
The no form of the command disables debugging.
This command enables debugging for the PIM BGP mechanism.
The no form of the command disables debugging.
This command enables debugging for the PIM Bootstrap mechanism.
The no form of the command disables debugging.
This command enables debugging for the PIM data exception.
The no form of the command disables debugging.
This command enables debugging for the PIM database.
The no form of the command disables debugging.
This command enables debugging for the PIM interface.
The no form of the command disables debugging.
This command enables debugging for the PIM Join-Prune mechanism.
The no form of the command disables debugging.
This command enables debugging for the PIM MRIB.
The no form of the command disables debugging.
This command enables debugging for PIM messaging.
The no form of the command disables debugging.
This command enables debugging for PIM packets.
The no form of the command disables debugging.
This command enables debugging for the PIM redundancy mechanism.
The no form of the command disables debugging.
This command enables debugging for the PIM register mechanism.
The no form of the command disables debugging.
This command enables debugging for the PIM RTM.
The no form of the command disables debugging.
This command enables access to the mtrace debug commands.
The no form of the command disables the debugging.
This command enables debugging for mtrace miscellaneous events.
The no form of the command disables the debugging.
This command enables debugging for mtrace packets.
The no form of the command disables the debugging.
This command monitors statistics for a PIM source group.