IP Multicast

This chapter provides information about multicast for IPv4 and IPv6, including Internet Group Management Protocol (IGMP), Multicast Listener Discovery (MLD), Protocol Independent Multicast source-specific multicast (PIM-SSM), Protocol Independent Multicast sparse mode (PIM-SM), and Multicast Source Discovery Protocol (MSDP).

Topics in this chapter include:

Overview of IP Multicast

IP multicast is a method of sending a single stream of traffic (or a single copy of data) to multiple recipients. IP multicast provides an effective method of one-to-many and many-to-many communication.

In the case of unicast delivery, IP packets are sent from a single source to a single host receiver. The source inserts the address of the target receiver in the IP header destination field of an IP datagram, and intermediate routers (if present) forward the datagram towards the target in accordance with their respective routing tables.

However, some applications, such as audio or video streaming broadcasts, require the delivery of individual IP packets to multiple destinations. In such applications, IP multicast is used to distribute datagrams from one or more source hosts to a set of receivers that may be distributed over different (sub) networks.

Multicast sources can send a single copy of data using a single address for the entire group of recipients. The routers between the source and recipients route the data using the group address route. Multicast packets are delivered to a multicast group. A multicast group specifies a set of recipients who are interested in a particular data stream and is represented by an IP address from a specified range. Data addressed to the IP address is forwarded to the members of the group. A source host sends data to a multicast group by specifying the multicast group address in the datagram’s destination IP address. A source does not have to register to a Rendezvous Point (RP) in order to send data to a group nor do they need to be a member of the group.

Routers and Layer 3 switches use the Internet Group Management Protocol (IGMP) to manage group membership for IPv4 multicast, and Multicast Listener Discovery (MLD) to manage group membership for IPv6 multicast. When a host receiver wants to receive one or more multicast sessions, it signals its local router by sending a join message to each multicast group it wants to join. When a host wants to leave a multicast group, it sends a Leave message. The local router forwards its group membership information to the core routers to inform the core routers about which multicast flows are needed.

To extend multicast from the receivers’ local router to the Internet, the 7705 SAR uses Protocol Independent Multicast (PIM), which employs both unicast and multicast routing tables to keep track of route information. As more routers in the Internet become multicast-capable, using both unicast and multicast routing tables becomes more and more important.

The 7705 SAR also uses the Multicast Source Discovery Protocol (MSDP) as a mechanism to connect multiple IPv4 PIM-SM domains together. Each PIM-SM domain uses its own independent Rendezvous Point (RP) and does not have to depend on RPs in other domains.

To summarize, host receivers connect to a local router (7705 SAR) via IGMP or MLD access or network interfaces. The 7705 SAR connects to the network—and eventually to the multicast source device at the far end—via PIM network interfaces. At the multicast source end, the 7705 SAR connects to the source via a PIM access or network interface.

Multicast in IP-VPN Networks

Multicast can be deployed as part of IP-VPN networks using VPRN. For details, see the ‟Multicast VPN (MVPN)” section in the 7705 SAR Services Guide.

Mobile Backhaul IP Multicast Example

A typical mobile backhaul infrastructure designed for Multimedia Broadcast Multicast Service (MBMS) is shown in IP Multicast for MBMS.

Figure 1. IP Multicast for MBMS

The 7705 SAR listens for IGMP and MLD receiver requests from the eNB and relays the requested group information back to the requester in one of two ways:

  • via local replication, if the stream for the given group is already available (that is, one or more receivers have already joined the group), or

  • via first relaying the request to the upstream router and then replicating the stream to the new receiver once the stream is available

IP Multicast for MBMS illustrates this as follows.

  • The 7705 SAR listens to IGMPv3 on an eNB IPv4 interface, or to MLDv2 on an eNB IPv6 interface.

  • The 7705 SAR uses PIM-SSM to send multicast traffic upstream and communicate with the 7750 SR at the MTSO. Similarly, the 7750 SR runs PIM-SSM towards the 7705 SAR.

  • The 7750 SR can then run a wide variety of different multicast protocols (such as point-to-multipoint LSPs, and multicast IP-VPN) towards the network core where the source (video head end) is located.

Multicast Models (ASM and SSM)

ASM provides network layer support for many-to-many delivery. SSM supports one-to-many delivery.

This section provides information about the following topics:

Any-Source Multicast (ASM)

ASM is the IP multicast service model defined in RFC 1112, Host extensions for IP Multicasting. An IP datagram is transmitted to a host group, which is a set of zero or more end-hosts identified by a single IP destination address (224.0.0.0 through 239.255.255.255 for IPv4). End-hosts can join and leave the group at any time and there is no restriction on their location or number. This model supports multicast groups with an arbitrary number of senders. Any end-host can transmit to a host group even if it is not a member of that group.

The ASM service model identifies a group by a (*, G) pair, where ‟*” (star) represents one or more sources.

Source-Specific Multicast (SSM)

The SSM service model defines a channel identified by an (S,G) pair, where S is a source address and G is an SSM destination address. In contrast to the ASM model, SSM only provides network-layer support for one-to-many delivery.

The SSM service model attempts to alleviate the following deployment problems that ASM has presented:

  • address allocation — SSM defines channels on a per-source basis. For example, the channel (S1,G) is distinct from the channel (S2,G), where S1 and S2 are source addresses. This avoids the problem of global allocation of SSM destination addresses and makes each source independently responsible for resolving address collisions for the various channels it creates.

  • access control — SSM provides an efficient solution to the access control problem. When a receiver subscribes to an (S,G) channel, it receives data sent only by the source, S. In contrast, any host can transmit to an ASM host group. At the same time, when a sender picks a channel (S,G) to transmit on, it is automatically ensured that no other sender will be transmitting on the same channel (except in the case of malicious acts such as address spoofing). This makes it harder to spam an SSM channel than it is to spam an ASM multicast group.

  • handling of well-known sources — SSM requires only source-based forwarding trees. This eliminates the need for a shared tree infrastructure. Thus the complexity of the multicast routing infrastructure for SSM is low, making it viable for immediate deployment.

IGMP Snooping and MLD Snooping For VPLS and Routed VPLS

The 7705 SAR supports IGMP snooping and MLD snooping for VPLS and routed VPLS (r-VPLS) services. IGMP and MLD snooping is enabled or disabled at the VPLS and r-VPLS service level. Further configurations are available at that level, as well as at the SAP and SDP (spoke and mesh) level of the service.

For details on IGMP and MLD snooping, see the ‟Multicast for VPLS and Routed VPLS (IGMP and MLD Snooping)” section in the 7705 SAR Services Guide.

Multicast Over Layer 3 Spoke SDP

The 7705 SAR supports PIM on Layer 3 spoke SDP interfaces. PIM-SM and PIM-SSM are supported for IPv4 in VPRN and IES. PIM-SSM is supported for IPv6 in IES.

A Layer 3 spoke SDP interface can be configured in the same way existing interfaces to be part of PIM IPv4 or PIM IPv6, which allows the interface to be used for multicast signaling and to transport multicast PDUs. GRE, MPLS, LDP, and SR transport tunnels are supported.

When signaling, PIM is tunneled through the Layer 3 spoke SDP interface multihop. Multicast PDUs are tunneled in the reverse direction through the Layer 3 spoke SDP interface. In both cases, packets are encapsulated with the Layer 3 spoke SDP header.

For more information about PIM functionality, see PIM.

IGMP

Internet Group Management Protocol (IGMP) enables multicast applications over native IPv4 networks. This section contains information about the following topics:

IGMP Overview

Internet Group Management Protocol (IGMP) is used by IPv4 hosts and routers to report their IP multicast group memberships to neighboring multicast routers. A multicast router keeps a list of multicast group memberships for each attached network, and a timer for each membership.

Multicast group memberships include at least one member of a multicast group on an attached network. In each of its attached networks, a multicast router can assume one of two roles, querier or non-querier. There is normally only one querier per physical network. The querier is the router elected as the router that issues queries for all routers on a LAN segment. Non-queriers listen for reports.

The querier issues two types of queries, a general query and a group-specific query. General queries are issued to solicit membership information with regard to any multicast group. Group-specific queries are issued when a router receives a Leave message from the node it perceives as being the last remaining group member on that network segment. See Query Messages for more information.

SSM translation allows an IGMPv1 or IGMPv2 device to join an SSM multicast network through the router that provides such a translation capability. SSM translation can done at the node (IGMP protocol) level, and at the interface level, which offers the ability to have the same (*,G) mapped to two different (S,G)s on two different interfaces to provide flexibility. Since PIM-SSM does not support (*,G), SSM translation is required to support IGMPv1 and IGMPv2.

Hosts wanting to receive a multicast session issue a multicast group membership report. These reports must be sent to all multicast-enabled routers.

IGMP Versions and Interoperability Requirements

If routers run different versions of IGMP, they will negotiate to run the lowest common version of IGMP that is supported on their subnet and operate in that version. The 7705 SAR supports three versions of IGMP:

  • version 1 — specified in RFC 1112, Host extensions for IP Multicasting, IGMPv1 was the first widely deployed version and the first version to become an Internet standard

  • version 2 — specified in RFC 2236, Internet Group Management Protocol, IGMPv2 added support for ‟low leave latency”; that is, a reduction in the time it takes for a multicast router to learn that there are no longer any members of a particular group present on an attached network

  • version 3 — specified in RFC 3376, Internet Group Management Protocol, IGMPv3 added support for source filtering; that is, the ability for a system to report interest in receiving packets only from specific source addresses, as required to support Source-Specific Multicast or from all but specific source addresses, sent to a particular multicast address (see Multicast Models (ASM and SSM))

IGMPv3 must keep track of each group’s state for each attached network. The group state consists of a filter-mode, a list of sources, and various timers. For each attached network running IGMP, a multicast router records the desired reception state for that network.

IGMP Version Transition

Nokia 7705 SAR routers are capable of interoperating with routers and hosts running IGMPv1, IGMPv2, and/or IGMPv3. RFC 5186, Internet Group Management Protocol version 3 (IGMPv3)/Multicast Listener Discovery version 2 (MLDv2) and Multicast Routing Protocol Interaction explores some of the interoperability issues and how they affect the various routing protocols.

IGMPv3 specifies that, if at any time a router receives an older IGMP version query message on an interface, it must immediately switch to a mode that is compatible with that earlier version. Since the previous versions of IGMP are source-aware, should this occur and the interface switch to version 1 or version 2 compatibility mode, any previously learned group memberships with specific sources (learned via the IGMPv3 specific INCLUDE or EXCLUDE mechanisms) must be converted to non-source-specific group memberships. The routing protocol will then treat this as if there is no EXCLUDE definition present.

Query Messages

The IGMP query source address is configurable at two hierarchical levels. It can be configured globally at each router instance IGMP level and can be configured individually at the group interface level. The group interface level overrides the source IP address configured at the router instance level.

By default, subscribers with IGMP policies send IGMP queries with an all-zero source IP address (0.0.0.0). However, some systems only accept and process IGMP query messages with non-zero source IP addresses. The query messages feature allows the Broadband Network Gateway (BNG) to interoperate with such systems.

Source-Specific Multicast Groups (IPv4)

IGMPv3 allows a receiver to join a group and specify that it only wants to receive traffic for a multicast group if that traffic comes from a particular source. If a receiver does this, and no other receiver on the LAN requires all the traffic for the group, the designated router (DR) can omit performing a (*,G) join to set up the shared tree, and instead issue a source-specific (S,G) join only.

The range of multicast addresses from 232.0.0.0 to 232.255.255.255 is currently set aside for source-specific multicast in IPv4. For groups in this range, receivers should only issue source-specific IGMPv3 joins. If a PIM router receives a non-source-specific join message for a group in this range, it should ignore it.

A 7705 SAR PIM router must silently ignore a received (*,G) PIM join message when ‟G” is a multicast group address from the multicast address group range that has been explicitly configured for SSM. This occurrence should generate an event. If configured, the IGMPv2 request can be translated into IGMPv3. The 7705 SAR allows for the conversion of an IGMPv2 (*,G) request into a IGMPv3 (S,G) request based on manual entries. A maximum of 32 SSM ranges is supported.

IGMPv3 also permits a receiver to join a group and specify that it only wants to receive traffic for a group if that traffic does not come from a specific source or sources. In this case, the designated router (DR) will perform a (*,G) join as normal, but can combine this with a prune for each of the sources the receiver does not wish to receive.

MLD

Multicast Listener Discovery (MLD) enables multicast applications over native IPv6 networks. This section contains information about the following topics:

MLD Overview

MLD is the IPv6 version of IGMP. The purpose of MLD is to allow each IPv6 router to discover the presence of multicast listeners on its directly attached links, and to discover specifically which multicast groups are of interest to those neighboring nodes.

MLD is a sub-protocol of ICMPv6. MLD message types are a subset of the set of ICMPv6 messages, and MLD messages are identified in IPv6 packets by a preceding Next Header value of 58. All MLD messages are sent with a link-local IPv6 source address, a Hop Limit of 1, and an IPv6 Router Alert option in the Hop-by-Hop Options header.

MLDv1

Similar to IGMPv2, MLDv1 reports include only the multicast group addresses that listeners are interested in, and do not include the source addresses. In order to work with the PIM-SSM model, an SSM translation function similar to that used for IGMPv1 and IGMPv2 is required when MLDv1 is used.

SSM translation allows an MLDv1 device to join an SSM multicast network through the router that provides such a translation capability. SSM translation can done at the node (MLD protocol) level, and at the interface level, which offers the ability to have the same (*,G) mapped to two different (S,G)s on two different interfaces to provide flexibility. Since PIM-SSM does not support (*,G), SSM translation is required to support MLDv1.

MLDv2

MLDv2 is backwards-compatible with MLDv1 and adds the ability for a node to report interest in listening to packets with a particular multicast group only from specific source addresses or from all sources except for specific source addresses.

PIM

The 7705 SAR supports PIM-SM according to RFC 4601, Protocol Independent Multicast - Sparse Mode (PIM-SM): Protocol Specification (Revised), and PIM-SSM according to RFC 4607, Source-Specific Multicast for IP, as described in this section.

For information about PIM-SSM support for IPv4 and IPv6, see Source-Specific Multicast Groups (IPv4) and IPv6 PIM Models.

This section contains information about the following topics:

PIM-SM Overview

PIM-SM leverages the unicast routing protocols that are used to create the unicast routing table: OSPF, IS-IS, BGP, and static routes. Because PIM uses this unicast routing information to perform the multicast forwarding function, it is effectively IP protocol-independent. Unlike the distance vector multicast routing protocol (DVMRP), PIM does not send multicast routing table updates to its neighbors.

PIM-SM uses the unicast routing table to perform the Reverse Path Forwarding (RPF) check function instead of building up a completely independent multicast routing table.

PIM-SM only forwards data to network segments with active receivers that have explicitly requested the multicast group. Initially, PIM-SM in the ASM model uses a shared tree to distribute information about active sources. Depending on the configuration options, the traffic can remain on the shared tree or switch over to an optimized source distribution tree. As multicast traffic starts to flow down the shared tree, routers along the path determine if there is a better path to the source. If a more direct path exists, the router closest to the receiver sends a join message toward the source and reroutes the traffic along this path.

PIM-SM relies on an underlying topology-gathering protocol to populate a routing table with routes. This routing table is called the multicast routing information base (MRIB). The routes in this table can be taken directly from the unicast routing table or they can be different and provided by a separate routing protocol such as multicast BGP (MBGP). The primary role of the MRIB in the PIM-SM protocol is to provide the next-hop router along a multicast-capable path to each destination subnet. The MRIB is used to determine the next-hop neighbor to whom any PIM join/prune message is sent. Data flows along the reverse path of the join messages. Therefore, in contrast to the unicast RIB that specifies the next hop that a data packet would take to get to a subnet, the MRIB gives reverse-path information and indicates the path that a multicast data packet would take from its origin subnet to the router that has the MRIB.

Note:

  • For proper functioning of the PIM protocol, multicast data packets must be received by the CSM CPU. Therefore, CSM filters and management access filters must be configured to allow forwarding of multicast data packets. For details on CSM filters and management access filters, see the ‟Security” chapter in the 7705 SAR System Management Guide.

  • Although the Control and Switching module on the 7705 SAR is called a CSM, the CSM filters are referred to as CPM filters in the CLI in order to maintain consistency with other SR routers.

PIM-SM Functions

PIM-SM functions in three phases:

Phase One

In this phase, a multicast receiver expresses its interest in receiving traffic destined for a multicast group. Typically it does this using IGMP or MLD, but other mechanisms might also serve this purpose. One of the receiver’s local routers is elected as the designated router (DR) for that subnet. When the expression of interest is received, the DR sends a PIM join message towards the RP for that multicast group. This join message is known as a (*,G) join because it joins group G for all sources to that group. The (*,G) join travels hop-by-hop towards the RP for the group, and in each router it passes through, the multicast tree state for group G is instantiated. Eventually, the (*,G) join either reaches the RP or reaches a router that already has the (*,G) join state for that group. When many receivers join the group, their join messages converge on the RP and form a distribution tree for group G that is rooted at the RP. The distribution tree is called the RP tree or the shared tree (because it is shared by all sources sending to that group). Join messages are re-sent periodically as long as the receiver remains in the group. When all receivers on a leaf network leave the group, the DR will send a PIM (*,G) prune message towards the RP for that multicast group. However, if the prune message is not sent for any reason, the state will eventually time out.

A multicast data sender starts sending data destined for a multicast group. The sender’s local router (the DR) takes these data packets, unicast-encapsulates them, and sends them directly to the RP. The RP receives these encapsulated data packets, removes the encapsulation, and forwards them to the shared tree. The packets then follow the (*,G) multicast tree state in the routers on the RP tree, are replicated wherever the RP tree branches, and eventually reach all the receivers for that multicast group. The process of encapsulating data packets to the RP is called registering, and the encapsulation packets are known as PIM register packets.

At the end of phase one, multicast traffic is flowing encapsulated to the RP, and then natively over the RP tree to the multicast receivers.

Phase Two

In this phase, register-encapsulation of data packets is performed. However, register-encapsulation of data packets is inefficient for the following reasons.

  • Encapsulation and de-encapsulation can be resource-intensive operations for a router to perform depending on whether the router has appropriate hardware for the tasks.

  • Traveling to the RP and then back down the shared tree can cause the packets to travel a relatively long distance to reach receivers that are close to the sender. For some applications, increased latency is unwanted.

Although register-encapsulation can continue indefinitely, for the reasons above, the RP will normally switch to native forwarding. To do this, when the RP receives a register-encapsulated data packet from source S on group G, it will normally initiate an (S,G) source-specific join towards S. This join message travels hop-by-hop towards S, instantiating an (S,G) multicast tree state in the routers along the path. The (S,G) multicast tree state is used only to forward packets for group G if those packets come from source S. Eventually, the join message reaches S’s subnet or a router that already has the (S,G) multicast tree state, and packets from S the start to flow following the (S,G) tree state towards the RP. These data packets can also reach routers with a (*,G) state along the path towards the RP, and if this occurs, they take a shortcut to the RP tree at this point.

While the RP is in the process of joining the source-specific tree for S, the data packets continue being encapsulated to the RP. When packets from S also start to arrive natively at the RP, the RP receives two copies of each of these packets. At this point, the RP starts to discard the encapsulated copy of these packets and sends a register-stop message back to S’s DR to prevent the DR from unnecessarily encapsulating the packets. At the end of phase two, traffic is flowing natively from S along a source-specific tree to the RP and from there along the shared tree to the receivers. Where the two trees intersect, traffic can transfer from the shared RP tree to the shorter source tree.

Note: A sender can start sending before or after a receiver joins the group, and thus phase two may occur before the shared tree to the receiver is built.

Phase Three

In this phase, the RP joins back towards the source using the shortest path tree (SPT). Although having the RP join back towards the source removes the encapsulation overhead, it does not completely optimize the forwarding paths. For many receivers, the route via the RP can involve a significant detour when compared with the shortest path from the source to the receiver.

To obtain lower latencies, a router on the receiver’s LAN, typically the DR, may optionally initiate a transfer from the shared tree to a source-specific SPT. To do this, it issues an (S,G) join towards S. This instantiates the (S,G) state in the routers along the path to S. Eventually, this join either reaches S’s subnet or reaches a router that already has the (S,G) state. When this happens, data packets from S start to flow following the (S,G) state until they reach the receiver.

At this point, the receiver (or a router upstream of the receiver) is receiving two copies of the data—one from the SPT and one from the RP tree. When the first traffic starts to arrive from the SPT, the DR or upstream router starts to drop the packets for G from S that arrive via the RP tree. In addition, it sends an (S,G) prune message towards the RP. The prune message travels hop-by-hop, instantiating an (S,G) state along the path towards the RP indicating that traffic from S for G should not be forwarded in this direction. The prune message is propagated until it reaches the RP or a router that still needs the traffic from S for other receivers.

By now, the receiver is receiving traffic from S along the SPT between the receiver and S. In addition, the RP is receiving the traffic from S, but this traffic is no longer reaching the receiver along the RP tree. As far as the receiver is concerned, this is the final distribution tree.

Encapsulating Data Packets in the Register Tunnel

Conceptually, the register tunnel is an interface with a smaller MTU than the underlying IP interface towards the RP. IP fragmentation on packets forwarded on the register tunnel is performed based on this smaller MTU. The encapsulating DR can perform path-MTU discovery to the RP to determine the effective MTU of the tunnel. This smaller MTU takes both the outer IP header and the PIM register header overhead into consideration.

PIM Bootstrap Router Mechanism

For proper operation, every PIM-SM router within a PIM domain must be able to map a particular global-scope multicast group address to the same RP. If this is not possible, black holes can appear (this is where some receivers in the domain cannot receive some groups). A domain in this context is a contiguous set of routers that all implement PIM and are configured to operate within a common boundary.

The Bootstrap Router (BSR) mechanism provides a way in which viable group-to-RP mappings can be created and distributed to all the PIM-SM routers in a domain. Each candidate BSR originates bootstrap messages (BSMs). Every BSM contains a BSR priority field. Routers within the domain flood the BSMs throughout the domain. A candidate BSR that hears about a higher-priority candidate BSR suppresses sending more BSMs for a period of time. The single remaining candidate BSR becomes the elected BSR and its BSMs inform the other routers in the domain that it is the elected BSR.

The PIM bootstrap routing mechanism is adaptive, meaning that if an RP becomes unreachable, the event will be detected and the mapping tables will be modified so that the unreachable RP is no longer used and the new tables are rapidly distributed throughout the domain.

PIM-SM Routing Policies

Multicast traffic can be restricted from certain source addresses by creating routing policies. Join messages can be filtered using import filters. PIM join policies can be used to reduce denial of service attacks and subsequent PIM state explosion in the router and to remove unwanted multicast streams at the edge of the network before they are carried across the core. Route policies are created in the config>router>policy-options context. Join and register route policy match criteria for PIM-SM can specify the following:

  • router interfaces specified by name or IP address

  • neighbor address (the source address in the IP header of the join and prune message)

  • multicast group address embedded in the join and prune message

  • multicast source address embedded in the join and prune message

Join policies can be used to filter PIM join messages so that no (*,G) or (S,G) state is created on the router. Join Filter Policy Match Conditions describes the match conditions.

Table 1. Join Filter Policy Match Conditions

Match Condition

Matches:

Interface

The router interface by name

Neighbor

The neighbor source address in the IP header

Group address

The multicast group address in the join/prune message

Source address

The source address in the join/prune message

PIM register messages are sent by the first-hop designated router that has a direct connection to the source. This serves a dual purpose:

  • notifies the RP that a source has active data for the group

  • delivers the multicast stream in register encapsulation to the RP and its potential receivers. If no routers have joined the group at the RP, the RP ignores the register requests.

In an environment where the sources to particular multicast groups are always known, register filters can be applied at the RP to prevent any unwanted sources from transmitting a multicast stream. These filters can also be applied at the edge so that register data does not travel unnecessarily over the network towards the RP. Register Filter Policy Match Conditions describes the match conditions.

Table 2. Register Filter Policy Match Conditions

Match Condition

Matches:

Interface

The router interface by name

Group address

The multicast group address in the join/prune message

Source address

The source address in the join/prune message

Reverse Path Forwarding Checks

Multicast implements a reverse path forwarding (RPF) check. RPF checks the path that multicast packets take between their sources and the destinations to prevent loops. Multicast requires that an incoming interface be the outgoing interface used by unicast routing to reach the source of the multicast packet. RPF forwards a multicast packet only if it is received on an interface that is used by the router to route to the source.

If the forwarding paths are modified due to routing topology changes, any dynamic filters that may have been applied must be re-evaluated. If filters are removed, the associated alarms are also cleared.

Anycast RP for PIM-SM

The implementation of anycast Rendezvous Point (RP) for PIM-SM environments enables fast convergence if a PIM RP router fails by allowing receivers and sources to rendezvous at the closest RP. It allows an arbitrary number of RPs per group in a single shared tree PIM-SM domain. This is particularly important for triple play configurations that choose to distribute multicast traffic using PIM-SM, not SSM. In this case, RP convergence must be fast enough to avoid the loss of multicast streams that could cause loss-of-TV delivery to the end customer.

Anycast RP for PIM-SM environments is supported in the base routing PIM-SM instance of the service router. This feature is also supported in Layer 3 VPRN instances that are configured with PIM.

Implementation

The anycast RP for PIM-SM implementation is defined in RFC 4610, Anycast-RP Using Protocol Independent Multicast (PIM), and is similar to that described in RFC 3446, Anycast Rendevous Point (RP) mechanism using Protocol Independent Multicast (PIM) and Multicast Source Discovery Protocol (MSDP). The implementation extends the register mechanism in PIM so that anycast RP functionality can be retained without using MSDP. For details, refer to the ‟Multicast VPN (MVPN)” section in the 7705 SAR Services Guide.

The mechanism works as follows:

  • An IP address is chosen as the RP address. This address is statically configured or distributed using a dynamic protocol to all PIM routers throughout the domain.

  • A set of routers in the domain are chosen to act as RPs for this RP address. These routers are called the anycast-RP set.

  • Each router in the anycast-RP set is configured with a loopback interface using the RP address.

  • Each router in the anycast-RP set also needs a separate IP address to be used for communication between the RPs.

  • The RP address, or a prefix that covers the RP address, is injected into the unicast routing system inside the domain.

  • Each router in the anycast-RP set is configured with the addresses of all other routers in the anycast-RP set. This must be consistently configured for all RPs in the set.

Figure 2. Anycast RP for PIM-SM Implementation

Anycast RP for PIM-SM Implementation shows a scenario where all routers connected, and where R1A, R1B, and R2 are receivers for a group, and S1 and S2 send to that group. In the example, RP1, RP2, and RP3 are all assigned the same IP address that is used as the anycast-RP address (RPA).

Note: The address used for the RP address in the domain (the RPA address) must be different from the addresses used by the anycast-RP routers to communicate with each other.

The following procedure is used when S1 starts sourcing traffic:

  1. S1 sends a multicast packet.

  2. The DR directly attached to S1 forms a PIM register message to send to the RPA. The unicast routing system delivers the PIM register message to the nearest RP, in this case RP1.

  3. RP1 receives the PIM register message, de-encapsulates it, and sends the packet down the shared tree to receivers R1A and R1B.

  4. RP1 is configured with the IP addresses of RP2 and RP3. Because the register message did not come from one of the RPs in the anycast-RP set, RP1 assumes the packet came from a DR. If the register message is not addressed to the RPA, an error has occurred and it should be rate-limited logged.

  5. RP1 sends a copy of the register message from S1’s DR to both RP2 and RP3. RP1 uses its own IP address as the source address for the PIM register message.

  6. RP1 may join back to the source tree by triggering an (S1,G) join message toward S1; however, RP1 must create an (S1,G) state.

  7. RP2 receives the register message from RP1, de-encapsulates it, and also sends the packet down the shared tree to receiver R2.

  8. RP2 sends a register-stop message back to RP1. RP2 may wait to send the register-stop message if it decides to join the source tree. RP2 should wait until it has received data from the source on the source tree before sending the register-stop message. If RP2 decides to wait, the register-stop message will be sent when the next register is received. If RP2 decides not to wait, the register-stop message is sent immediately.

  9. RP2 may join back to the source tree by triggering an (S1,G) join message toward S1; however, RP2 must create an (S1,G) state.

  10. RP3 receives the register message from RP1 and de-encapsulates it, but since there are no receivers joined for the group, it discards the packet.

  11. RP3 sends a register-stop message back to RP1.

  12. RP3 creates an (S1,G) state so when a receiver joins after S1 starts sending, RP3 can join quickly to the source tree for S1.

  13. RP1 processes the register-stop messages from RP2 and RP3. RP1 may cache–on a per-RP/per-(S,G) basis—the receipt of register-stop messages from the RPs in the anycast-RP set. This option is performed to increase the reliability of register message delivery to each RP. When this option is used, subsequent register messages received by RP1 are sent only to the RPs in the anycast-RP set that have not previously sent register-stop messages for the (S,G) entry.

  14. RP1 sends a register-stop message back to the DR the next time a register message is received from the DR and, when the option in step 13 is in use, if all RPs in the anycast-RP set have returned register-stop messages for a particular (S,G) route.

The procedure for S2 sending follows the same steps as above, but it is RP3 that sends a copy of the register originated by S2’s DR to RP1 and RP2. Therefore, this example shows how sources anywhere in the domain, associated with different RPs, can reach all receivers, also associated with different RPs, in the same domain.

Multicast-only Fast Reroute (MoFRR)

The 7705 SAR supports multicast-only fast reroute (MoFRR) in the context of GRT for mLDP, where the multicast traffic is duplicated on a primary mLDP multicast tree and on a secondary mLDP multicast tree. These are two separate mLDP LSPs, and therefore they are set up separately. The root node transmits multicast PDUs on both active and inactive LSPs. The PDUs are duplicated using the multicast tree and sent through the network to the leaf node on both the active and the inactive LSPs. The leaf listens only to the active LSP and drops PDUs from the secondary, inactive LSP.

The MoFRR functionality relies on detecting failures on the primary path and switching to forwarding the traffic to the standby path. The traffic failure can happen with or without physical links or nodes going down. Various mechanisms for link or node failure detections are supported. However, for best performance and resilience, enable MoFRR on every node in the network and use hop-by-hop BFD for detection of fast link failure or data plane failure on each upstream link. If BFD is not used, PIM adjacency loss or a route change can be used to detect traffic failure.

MoFRR in Steady State with No Failure and MoFRR in Failure State illustrate MoFRR with no failure and with a failure. MoFRR is enabled on P1, P2, P3, P4, PE2, and PE3. Primary streams (solid gray lines) are active; one stream is from PE1 to PE2 and another is from PE1 to PE3. Secondary streams (gray-black lines) are blocked (circles with ‟X” inside). In MoFRR in Failure State, PE3 detects a link failure between P4 and PE3, and switches to the standby (secondary) stream from P2.

Figure 3. MoFRR in Steady State with No Failure
Figure 4. MoFRR in Failure State

Automatic Discovery of Group-to-RP Mappings (Auto-RP)

Auto-RP is a proprietary group discovery and mapping mechanism for IPv4 PIM that is described in cisco-ipmulticast/pim-autorp-spec, Auto-RP: Automatic discovery of Group-to-RP mappings for IP multicast. The functionality is similar to the IETF standard BSR mechanism that is described in RFC 5059, Bootstrap Router (BSR) Mechanism for Protocol Independent Multicast (PIM), to dynamically learn about the availability of RPs in a network.

When a router is configured as an RP mapping agent with the pim>rp>auto-rp-discovery command, it listens to the CISCO-RP-ANNOUNCE (224.0.1.39) group and caches the announced mappings. The RP mapping agent then periodically sends out RP mapping packets to the CISCO-RP-DISCOVERY (224.0.1.40) group. PIM dense mode (PIM-DM) as described in RFC 3973, Protocol Independent Multicast - Dense Mode (PIM-DM): Protocol Specification (Revised), is used for the auto-RP groups to support multihoming and redundancy. The RP mapping agent supports announcing, mapping, and discovery functions; candidate RP functionality is not supported.

Auto-RP is supported for IPv4 in multicast VPNs and in the global routing instance. Either BSR or auto-RP for IPv4 can be configured; the two mechanisms cannot be enabled together. In a multicast VPN, auto-RP cannot be enabled together with sender-only or receiver-only multicast distribution trees (MDTs), or wildcard S-PMSI configurations that could block flooding.

IPv6 PIM Models

IPv6 multicast enables multicast applications over native IPv6 networks. There are two service models: Any Source Multicast (ASM) and Source Specific Multicast (SSM) which includes PIM-SSM and MLD. SSM does not require source discovery and only supports a single source for a specific multicast stream. As a result, SSM is easier to operate in a large-scale deployment that uses the one-to-many service model.

PIM-SSM

The IPv6 address family for the SSM model is supported. OSPFv3 and static routing have extensions to support submission of routes into the IPv6 multicast RTM.

PIM-ASM

IPv4 PIM-ASM is supported. All PIM-ASM related functions—such as bootstrap router and RP—support the IPv4 address family.

IP Multicast Debugging Tools

This section describes multicast debugging tools for the 7705 SAR. The debugging tools for multicast consist of three elements, which are accessed from the CLI <global> level:

Mtrace

Assessing problems in the distribution of IP multicast traffic can be difficult. The multicast traceroute (mtrace) feature uses a tracing feature implemented in multicast routers that is accessed via an extension to the IGMP protocol. The mtrace feature is used to print the path from the source to a receiver; it does this 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 requester.

Data added by each hop includes:

  • query arrival time

  • incoming interface

  • outgoing interface

  • previous hop router address

  • input packet count

  • output packet count

  • total packets for this source/group

  • routing protocol

  • TTL threshold

  • forwarding/error code

The information enables the network administrator to determine:

  • the flow of the multicast stream

  • where multicast flows stop

When the trace response packet reaches the first-hop router (the router that is directly connected to the source’s network interface), that router sends the completed response to the response destination (receiver) address specified in the trace query.

If a multicast router along the path does not implement the mtrace feature or if there is an outage, then no response is returned. To solve this problem, the trace query includes a maximum hop count field to limit the number of hops traced before the response is returned. This allows a partial path to be traced.

The reports inserted by each router contain not only the address of the hop, but also the TTL required to forward the packets and flags to indicate routing errors, plus counts of the total number of packets on the incoming and outgoing interfaces and those forwarded for the specified group. Examining the differences in these counts for two separate traces and comparing the output packet counts from one hop with the input packet counts of the next hop allows the calculation of packet rate and packet loss statistics for each hop to isolate congestion problems.

Finding the Last-hop Router

The trace query must be sent to the multicast router that is the last hop on the path from the source to the receiver. If the receiver is on the local subnet (as determined by the subnet mask), then the default method is to send the trace query to all-routers.mcast.net (224.0.0.2) with a TTL of 1. Otherwise, the trace query is sent to the group address since the last-hop router will be a member of that group if the receiver is. Therefore, it is necessary to specify a group that the intended receiver has joined. This multicast query is sent with a default TTL of 64, which may not be sufficient for all cases.

When tracing from a multihomed host or router, the default receiver address may not be the desired interface for the path from the source. In that case, the desired interface should be specified explicitly as the receiver.

Directing the Response

By default, mtrace first attempts to trace the full reverse path, unless the number of hops to trace is explicitly set with the hop option. If there is no response within a 3-s timeout interval, a ‟*” is displayed and the probing switches to hop-by-hop mode. Trace queries are issued starting with a maximum hop count of one and increasing by one until the full path is traced or no response is received. At each hop, multiple probes are sent. The first attempt is made with the unicast address of the host running mtrace as the destination for the response. Since the unicast route may be blocked, the remainder of attempts request that the response be sent to mtrace.mcast.net (224.0.1.32) with the TTL set to 32 more than what is needed to pass the thresholds seen so far along the path to the receiver. For the last attempts, the TTL is increased by another 32.

Alternatively, the TTL may be set explicitly with the TTL option.

For each attempt, if no response is received within the timeout, a ‟*” is displayed. After the specified number of attempts have failed, mtrace will try to query the next-hop router with a DVMRP_ASK_NEIGHBORS2 request (as used by the mrinfo feature) to determine the router type.

The output of mtrace is a short listing of the hops in the order they are queried, that is, in the reverse of the order from the source to the receiver. For each hop, a line is displayed showing:

  • the hop number (counted negatively to indicate that this is the reverse path)

  • the multicast routing protocol

  • the threshold required to forward data (to the previous hop in the listing as indicated by the up-arrow character)

  • the cumulative delay for the query to reach that hop (valid only if the clocks are synchronized)

The response ends with a line showing the round-trip time which measures the interval from when the query is issued until the response is received, both derived from the local system clock.

Mtrace/mstat packets use special IGMP packets with IGMP type codes of 0x1E and 0x1F.

Mstat

The mstat feature adds the capability to show the multicast path in a limited graphic display and indicates drops, duplicates, TTLs, and delays at each node. This information is useful to the network operator because it identifies nodes with high drop and duplicate counts. Duplicate counts are shown as negative drops.

The output of mstat provides a limited pictorial view of the path in the forward direction with data flow indicated by arrows pointing downward and the query path indicated by arrows pointing upward. For each hop, both the entry and exit addresses of the router are shown if different, along with the initial TTL required on the packet in order to be forwarded at this hop and the propagation delay across the hop assuming that the routers at both ends have synchronized clocks. The output consists of two columns, one for the overall multicast packet rate that does not contain lost/sent packets and the other for the (S,G)-specific case. The (S,G) statistics also do not contain lost/sent packets.

Mrinfo

The mrinfo feature is a simple mechanism to display the configuration information from the target multicast router. The type of information displayed includes the multicast capabilities of the router, code version, metrics, TTL thresholds, protocols, and status. This information can be used by network operators, for example, to verify if bidirectional adjacencies exist. Once the specified multicast router responds, the configuration is displayed.

MSDP

Multicast Source Discovery Protocol (MSDP) is a mechanism that allows rendezvous points (RPs) to share information about active sources. When RPs in remote domains hear about the active sources, they can pass on that information to the local receivers and multicast data can be forwarded between the domains. MSDP allows each domain to maintain an independent RP that does not rely on other domains, but it also enables RPs to forward traffic between domains. PIM-SM is used to forward the traffic between the multicast domains.

Using PIM-SM, multicast sources and receivers register with their local RP via the closest multicast router. The RP maintains information about the sources and receivers for any particular group. RPs in other domains do not have any knowledge about sources located in other domains.

MSDP-speaking routers in a PIM-SM domain have an MSDP peering relationship with MSDP peers in another PIM-SM domain. The peering relationship is made up of a TCP connection in which control information is exchanged. Each domain has one or more connections to this virtual topology.

When a PIM-SM RP learns about a new multicast source within its own domain from a standard PIM register mechanism, it encapsulates the first data packet in an MSDP source-active (SA) message and sends it to all MSDP peers.

After an RPF check, the SA message is flooded by each peer to its MSDP peers until the SA message reaches every MSDP router in the interconnected networks. If the receiving MSDP peer is an RP, and the RP has a (*,G) entry (receiver) for the group, the RP creates a (*,G) state for the source and joins the shortest path tree for the source. The encapsulated data is de-encapsulated and forwarded down the shared tree of that RP. When the packet is received by the last-hop router of the receiver, the last-hop router can also join the shortest path tree to the source.

The MSDP speaker periodically sends SA messages that include all sources.

This section contains information about the following topics:

The 7705 SAR supports MSDP in the base router context and on MVPNs in the VPRN service context. For information about MSDP on MVPNs, see ‟Multicast Source Discovery Protocol” in the Multicast VPN (MVPN) section of the 7705 SAR Services Guide.

MSDP and Anycast RP

MSDP is required to provide inter-domain multicast services using Any Source Multicast (ASM). Anycast RP for MSDP enables fast convergence when an MSDP PIM RP router fails by allowing receivers and sources to rendezvous at the closest RP.

MSDP Procedure

When an RP in a PIM-SM domain first learns of a new sender—for example, by PIM register messages—it constructs an SA message and sends it to its MSDP peers. The SA message contains the following fields:

  • source address of the data source

  • group address the data source sends to

  • IP address of the RP

Note: An RP that is not a designated router on a shared network does not originate SAs for directly connected sources on that shared network. An RP only originates SAs in response to receiving register messages from the designated router.

Each MSDP peer receives and then forwards the SA message away from the RP address in a peer-RPF flooding fashion. The RPF multicast routing information base (MRIB) is examined to determine which peer towards the originating RP of the SA message is selected. This peer is called an RPF peer. The MSDP peer performs peer-RPF forwarding by comparing the RP address carried in the SA message against the MSDP peer from which the message was received.

If the MSDP peer receives the SA from a non-RPF peer towards the originating RP, it will drop the message. Otherwise, it forwards the message to all its MSDP peers (except the one from which it received the SA message).

When an MSDP peer that is also an RP for its own domain receives a new SA message, it determines if there are any group members within the domain interested in any group described by an (S,G) entry within the SA message. That is, the RP checks for a (*,G) entry with a non-empty outgoing interface list. This implies that some router in the domain is interested in the group. In this case, the RP triggers an (S,G) join event toward the data source as if a join/prune message was received addressed to the RP. This sets up a branch of the source tree to this domain. Subsequent data packets arrive at the RP by this tree branch and are forwarded down the shared tree inside the domain. If leaf routers choose to join the source tree, they have the option to do so according to existing PIM-SM conventions. If an RP in a domain receives a PIM join message for a new group G, the RP must trigger an (S,G) join event for each active (S,G) for that group in its cache.

This procedure is called flood-and-join because if any RP is not interested in the group, the SA message can be ignored; otherwise, the RPs join a distribution tree.

MSDP Peering Scenarios

The 7705 SAR conforms to draft-ietf-mboned-msdp-deploy-nn.txt, Multicast Source Discovery Protocol (MSDP) Deployment Scenarios, which describes how PIM-SM and MP-BGP work together to provide intra- and inter-domain ASM service.

The 7705 SAR supports the following intra-domain MSDP peering deployment options:

  • peering between routers configured for both MSDP and MBGP

  • MSDP peer is not a BGP peer (or no BGP peer)

The 7705 SAR supports the following inter-domain MSDP peering deployment options:

  • peering between PIM border routers (single-hop peering)

  • peering between non-border routers (multi-hop peering)

  • MSDP peering without BGP

  • MSDP peering between mesh groups

  • MSDP peering at a multicast exchange

MSDP Peer Groups

MSDP peer groups are typically created when multiple peers have a set of common operational parameters. Group parameters that are not specifically configured are inherited from the global level.

MSDP Mesh Groups

MSDP mesh groups are used to reduce SA flooding primarily in intra-domain configurations. When multiple speakers in an MSDP domain are fully meshed, they can be configured as a mesh group. The originator of the SA message forwards the message to all members of the mesh group; therefore, forwarding the SA message between non-originating members of the mesh group is not necessary.

MSDP Routing Policies

MSDP routing policies allow for filtering of inbound and outbound SA messages. Policies can be configured at different levels:

  • global level — applies to all peers

  • group level — applies to all peers in a peer group

  • neighbor level — applies only to a specified peer

The most specific level is used. If multiple policy names are specified, the policies are evaluated in the order they are specified. The first policy that matches is applied. If no policy is applied, SA messages are passed.

Match conditions include:

  • neighbor — the policy matches on a neighbor address that is the source address in the IP header of the SA message

  • route filter — the policy matches on a multicast group address embedded in the SA message

  • source address filter — the policy matches on a multicast source address embedded in the SA message

Auto-RP (Discovery Mode Only) in Multicast VPN

Auto-RP is a vendor proprietary protocol used to dynamically learn about the availability of RPs in a network. The Auto-RP protocol consists of announcing, mapping, and discovery functions. The 7705 SAR supports the discovery mode of Auto-RP, which includes mapping and forwarding of RP-mapping messages and RP-candidate messages. Discovery mode also includes receiving RP-mapping messages locally in order to learn and maintain the RP-candidate database.

The Auto-RP protocol is supported for multicast VPN and in the global routing instance. Either BSR or Auto-RP can be configured per routing instance. Both mechanisms cannot be enabled together.

Inter-AS Non-segmented mLDP

This feature allows multicast services to use segmented protocols and span them over multiple autonomous systems (ASs) in the same way as unicast services. Because IP VPN or GRT services span multiple IGP areas or multiple ASs, either for a network designed to deal with scale or as a result of commercial acquisitions, operators may require inter-AS VPN (unicast) connectivity. For example, an inter-AS VPN can break the IGP, MPLS, and BGP protocols into access segments and core segments, allowing higher scaling of protocols by segmenting them into their own islands. The 7705 SAR allows for a similar provisioning of multicast services and for spanning these services over multiple IGP areas or multiple ASs.

Multicast LDP (mLDP) supports non-segmented mLDP trees for inter-AS solutions that are applicable for NG-MVPN services. Refer to the 7705 SAR Services Guide, ‟NG-MVPN Non-segmented Inter-AS Solution” for information.

For information about ECMP behavior for inter-AS non-segmented mLDP, refer to the 7705 SAR MPLS Guide, ‟ECMP Support” under ‟Inter-AS Non-segmented mLDP”.

ASBR Support of PE Functionality

Remote and Local ASBRs displays remote and local ASBRs.

Figure 5. Remote and Local ASBRs

ASBRs can also act as PE nodes, but the 7705 SAR does not support all PE functionalities in the ASBR node. PE Features on ASBRs lists supported PE features on ASBRs.

Table 3. PE Features on ASBRs

Inter-AS Multicast Context

ASBR Node

Leaf or Bud

Root or Source

GRT

X

X

VPN

✓

X

Hashing for Inter-AS

At each leaf or ASBR, there are two FECs: a lower FEC and an upper FEC. The lower FEC is used for hashing to multiple ASBRs and the upper FEC is used to choose the next hop that connects the leaf node to the ASBR. Hashing is performed based on the opaque value of the FEC. See the 7705 SAR MPLS Guide, ‟Supported Recursive Opaque Values”, for more information.

In Hashing for Inter-AS, the leaf generates a lower FEC of <0.0.0.0, opaque <10.0.0.14, 8010>>. The lower FEC opaque <10.0.0.14, 8010> and number of ASBRs (three) is used to decide which ASBR will be used based on hashing. After hashing produces ASBR-5 as the result, the upper FEC of <10.0.0.23, opaque <10.0.0.14, 8010>> is created. This upper FEC is used to resolve the ASBR-5 next hop between the three interfaces that connect the leaf node to ASBR-5.

Figure 6. Hashing for Inter-AS

Hashing at the ASBR

Hashing at the ASBR illustrates hashing at the ASBR.

Figure 7. Hashing at the ASBR

In Hashing at the ASBR, the leaf node will have ROOT-1 in the RTM for Inter-AS Option C; therefore, the leaf will not generate a recursive type 7 opaque and will only generate a type 1 opaque. When the FEC arrives at ASBR-3, it will have a basic type 1 FEC of <ROOT: 10.0.0.14, opaque <8010>>.

If the ASBR also has a host that will generate an mLDP LSP toward the root, this FEC will look up <ROOT: 0.0.0.0, opaque <10.0.0.14, 8010>>.

Hashing is performed based on the opaque value of the FEC. Refer to the 7705 SAR MPLS Guide, ‟Supported Recursive Opaque Values” for more information.

The opaque of the leaf node is not the same as the opaque of the ASBR bud node. In this scenario, the two LSPs will generate a different ASBR as the next hop, inefficiently duplicating multicast traffic. In order to prevent this problem, the 7705 SAR converts the opaque type 1 lower FEC, that arrives from the leaf node, into a recursive type 7 FEC, so that the bud FEC generated by the ASBR and the FEC arriving from the leaf node will result in the same upper ASBR.

Unicast and Multicast Address Translation

The 7705 SAR supports unicast-to-multicast address translation and multicast-to-multicast address translation.

For unicast-to-multicast translation, the 7705 SAR translates the destination IP address of the unicast flow to a multicast group.

For multicast-to-multicast translation, the 7705 SAR acts as a host to upstream (S,G)s and performs address translation to the downstream (S,G).

Unicast and multicast address translation is supported on the following adapter cards and platforms:

  • on the 7705 SAR-8 Shelf V2 and the 7705 SAR-18:

    • 2-port 10GigE (Ethernet) Adapter card

    • 6-port Ethernet 10Gbps Adapter card

    • 8-port Gigabit Ethernet Adapter card, version 3

    • 10-port 1GigE/1-port 10GigE X-Adapter card, version 2 (supported on the 7705 SAR-18 only)

  • 7705 SAR-Ax

  • 7705 SAR-H

  • 7705 SAR-Hc

  • 7705 SAR-Wx

  • 7705 SAR-X

Unicast-to-Multicast Address Translation

With unicast-to-multicast address translation, unicast packets destined for a local loopback interface on the 7705 SAR are translated to a multicast (S,G).

Unicast-to-multicast translation is supported in the global routing table (GRT) and in VPRNs. Both IPv4 and IPv6 address families are supported for the GRT, while IPv4 addressing on SAP-to-SAP connections is supported for VPRNs.

For the 7705 SAR to perform unicast-to-multicast address translation, the following is required.

  • The unicast traffic must be destined for a loopback IP address on the translator router (7705 SAR).

  • The multicast source must be a loopback IP address on the 7705 SAR that is also configured under a PIM, IGMP, or MLD interface.

  • The 7705 SAR only forwards multicast traffic on the outgoing interfaces that receive the (S,G) join.

  • The unicast domain must support resilience functionality such as LFA, ECMP, or LAG.

  • All hosts in the multicast domain must join a loopback IP on the 7705 SAR that is doing unicast-to-multicast translation.

Note:

  • For IES and VPRN services, the normal operation of unicast-to-multicast translation does not require an ingress IES or VPRN physical interface to be added under the PIM context. However, if separate QoS treatment is required for the unicast traffic that is translated to multicast traffic, the multicast traffic must be mapped to a multicast queue in a SAP ingress QoS policy assigned to the SAP for the IES or VPRN ingress interface. In order for this multicast queue to be created, the physical IES or VPRN interface must also be added under the PIM context.

  • To prevent PIM Hello messages from being sent from the IES or VPRN interface back to the unicast domain, the interface should be shut down under PIM.

Unicast-to-Multicast Translation on the 7705 SAR shows an example of the 7705 SAR acting as a translator router for unicast-to-multicast address translation.

Figure 8. Unicast-to-Multicast Translation on the 7705 SAR

In Unicast-to-Multicast Translation on the 7705 SAR, the host (leaf) nodes in a multicast group are connected to a local router via an interface configured for IGMP or MLD; however, the hosts can also be connected to the translator directly via an IGMP or MLD interface. The local router is connected to the translator router via a PIM interface. To receive a multicast session, the local router must send a PIM join message to the translator router. After translating the traffic from unicast to multicast, the 7705 SAR forwards multicast traffic on the outgoing interfaces that receive the (S,G) join.

The following CLI example shows the configuration to enable multicast translation on three loopback interfaces on the 7705 SAR translator router based on the scenario shown in Unicast-to-Multicast Translation on the 7705 SAR. The loopback interfaces are the destination for the unicast traffic.

Example:
config>router# interface loop1
config>router>if# multicast-translation
config>router>if# exit
config>router# interface loop2
config>router>if# multicast-translation
config>router>if# exit
config>router# interface loop3
config>router>if# multicast-translation
config>router>if# exit

The following CLI example shows the configuration to translate the unicast source addresses to a destination multicast group based on the scenario shown in Unicast-to-Multicast Translation on the 7705 SAR.

Example:
config>router# pim 
config>router>pim# interface loop1
config>router>pim>if# unicast-to-multicast unicast-start 1.1.1.1 unicast-end 1.1.1.1 destination 100.1.1.1 to-multicast 230.0.0.1
config>router>pim>if# no shutdown
config>router>pim>if# exit
config>router>pim# interface loop2
config>router>pim>if# unicast-to-multicast unicast-start 1.1.1.3 unicast-end 1.1.1.3 destination 200.1.1.1 to-multicast 230.0.0.2
config>router>pim>if# no shutdown
config>router>pim>if# exit 
config>router>pim# interface loop2 
config>router>pim>if# unicast-to-multicast unicast-start 2.1.1.1 unicast-end 2.1.1.2 destination 200.1.1.1 to-multicast 230.1.0.1
config>router>pim>if# no shutdown
config>router>pim>if# exit

The outcome of the configuration is as follows:

  • unicast source (1.1.1.1, 100.1.1.1) translates to multicast destination (100.1.1.1, 230.0.0.1) for interface loop1

  • unicast source (1.1.1.3, 200.1.1.1) translates to multicast destination (200.1.1.1, 230.0.0.2) for interface loop2

  • unicast source (2.1.1.1 to 2.1.1.2, 200.1.1.1) translates to multicast destination (200.1.1.1, 230.1.0.1 to 230.1.0.2) for interface loop2

The 7705 SAR supports both single-source multicast (SSM) and any-source multicast (ASM) models for unicast-to-multicast address translation.

With SSM, when hosts join a loopback address on the 7705 SAR that is doing the translation, IGP routes the PIM joins to this router. The PIM joins are routed to the 7705 SAR because the 7705 SAR translator router is configured as the source of the multicast traffic on the hosts. All multicast functionality is valid in the multicast domain, except that the multicast source is the 7705 SAR loopback IP address rather than a source that is connected to the 7705 SAR. Reverse Path Forwarding (RPF) is performed against the loopback address of the translated (S,G), so if the multicast traffic (S,G) arrives on a non-loopback interface, it will be dropped.

With ASM, if the 7705 SAR is both the Rendezvous Point (RP) and the unicast-to-multicast translator router, it receives packets from the unicast domain and translates their destination address to a multicast source address based on the configuration of the unicast-to-multicast command. The hosts (leaves) send a (*,G) join message to the RP (which is the translator router), and the translator router forwards (loopback,G) traffic to the leaves. The leaves then send a join (loopback,G) message back to the RP.

If the 7705 SAR is not the RP but is the unicast-to-multicast translator router, it must be configured with RP parameters under the PIM interface. The 7705 SAR translates the unicast stream to (loopback,G), then encapsulates the (loopback,G) packets in a unicast packet and sends the unicast packet to the RP. This unicast packet is known as a ‟register” message in PIM. The RP removes the outer IP address and forwards the (loopback,G) packets to the leaves. The leaves then send a join (loopback,G) message back to the 7705 SAR translator router.

For ASM, only IPv4 addresses are supported.

Multicast-to-Multicast Address Translation

With multicast-to-multicast address translation, the 7705 SAR acts as a host to upstream (S,G)s. (S,G) packets arriving on the 7705 SAR are translated to a new downstream (S,G). Multiple upstream sources can be translated to a single downstream source. The overlapping groups between the two sources merge into one and are configured to a range of groups on the single downstream source.

Multicast-to-multicast configuration on the 7705 SAR is very similar to unicast-to-multicast configuration except that the 7705 SAR performing the address translation is configured with static IGMP join requests for interested (S,G)s toward the upstream source. For these (S,G)s, the 7705 SAR acts as the host and translates these streams based on the configuration of the multicast-to-multicast command. On the downstream (receiver domain), the 7705 SAR acts as the source of the translated streams to the hosts that want to join these (S,G)s.

Multicast-to-multicast translation is supported in the GRT and in VPRNs.

Multicast-to-Multicast Address Translation on the 7705 SAR shows an example of the 7705 SAR acting as a multicast-to-multicast address translator.

Figure 9. Multicast-to-Multicast Address Translation on the 7705 SAR

In Multicast-to-Multicast Address Translation on the 7705 SAR, the 7705 SAR router with system IP address 100.0.0.1 is performing the translation. The translator router sends a static IGMP join request to interested streams in the source domain. The translator router is the host for these streams. The example below shows the configuration for a static IGMP join request.

Example:
config>router#
config>router>igmp# interface ‟to-source-domain”
config>router>igmp>if# static
config>router>igmp>if>static# group 230.0.0.1
config>router>igmp>if>static>group# source 1.1.1.1
config>router>igmp>if>static>group>source# exit
config>router>igmp>if>static# group 230.0.0.2
config>router>igmp>if>static>group# source 1.1.1.1
config>router>igmp>if>static>group>source# exit
config>router>igmp>if>static# group 230.0.0.100
config>router>igmp>if>static>group# source 1.1.1.1
config>router>igmp>if>static>group>source# exit
config>router>igmp>if>static# group 230.0.0.10
config>router>igmp>if>static>group# source 2.1.1.1
config>router>igmp>if>static>group>source# exit
config>router>igmp>if>static# group 230.0.0.1
config>router>igmp>if>static>group# source 2.1.1.2
config>router>igmp>if>static>group>source# exit
config>router>igmp>if>static# group 230.0.0.10
config>router>igmp>if>static>group# source 2.1.1.2
config>router>igmp>if>static>group>source# exit

To translate these source domain streams to receiver domain streams, a loopback interface on the translator router must be enabled for multicast translation. The example below shows the configuration.

Example:
config>router# interface ‟to-source-domain”
config>router>if# multicast-translation
config>router>if# exit

Under the loopback IP address on the PIM interface, the 7705 SAR creates a mapping between the upstream (S,G) and the downstream (S,G). The example below shows the configuration.

Example:
config>router# pim 
config>router>pim# interface loop2
config>router>pim>if# multicast-to-multicast source 1.1.1.1 group-start 230.0.0.1 group-end 230.0.0.100 to-multicast 230.0.0.1
config>router>pim>if# multicast-to-multicast source 2.1.1.1 group-start 230.0.0.1 group-end 230.0.0.10 to-multicast 230.0.0.101
config>router>pim>if# no shutdown
config>router>pim>if# exit
config>router>pim# interface loop3
config>router>pim>if# multicast-to-multicast source 2.1.1.2 group-start 230.0.0.1 group-end 230.0.0.10 to-multicast 230.0.0.1
config>router>pim>if# no shutdown
config>router>pim>if# exit

The outcome of the configuration is as follows:

  • multicast (1.1.1.1, 230.0.0.1) translates to multicast (200.1.1.1, 230.0.0.1)

  • multicast (1.1.1.1, 230.0.0.100) translates to multicast (200.1.1.1, 230.0.0.100)

  • multicast (2.1.1.1, 230.0.0.1) translates to multicast (200.1.1.1, 230.0.0.101)

  • multicast (2.1.1.1, 230.0.0.10) translates to multicast (200.1.1.1, 230.0.0.110)

  • multicast (2.1.1.2, 230.0.0.1) translates to multicast (210.1.1.1, 230.0.0.1)

  • multicast (2.1.1.2, 230.0.0.10) translates to multicast (210.1.1.1, 230.0.0.10)

The configuration above also merges two different source domain sources, source 1.1.1.1 and 2.1.1.1, into a single receiver domain, 200.1.1.1. As well, overlapping groups are spread out into a group range of 230.0.0.1 to 230.0.0.110.

IP Multicast Configuration Process Overview

IP Multicast Configuration Process shows the process to configure multicast parameters.

Figure 10. IP Multicast Configuration Process

Configuration Notes

General

This section describes multicast configuration guidelines and caveats:

  • a multicast stream is required by one or more multicast clients

  • a multicast stream is offered by one or more multicast servers

  • unlike 7750 SR nodes, when the maximum number of groups per node limit is exceeded, the additional groups are not stored at the CSM layer and an alarm is raised immediately

IP Multicast Configuration Overview

Nokia 7705 SAR routers use IGMP and MLD to manage membership of host receivers for a given multicast session. The routers use PIM-SSM or PIM-SM to connect to the multicast source and to the network.

Traffic can only flow away from the router to an IGMP or MLD interface; it can flow both to and from a PIM interface. A router directly connected to a source of multicast traffic must have PIM enabled on the interface to that source. The traffic travels through a network from PIM interface to PIM interface, and arrives on an IGMP- or MLD-enabled interface.

IGMP and MLD

The IGMP and MLD CLI contexts are created when the config>router>igmp and config>router>mld commands are run. They are not operational until at least one interface is specified in the context, at which time the interface is enabled for IGMP or MLD and is called an IGMP or MLD interface. When enabled, the interface can be configured with IGMP or MLD parameters, which are in addition to the standard parameters for the interface when it is created.

You can filter traffic on an IGMP or MLD interface by defining and importing a routing policy. You can also define the maximum number of groups to which the interface can belong.

Note: Before an IP interface can be specified in an IGMP or MLD context, it must be created on the 7705 SAR (config>router>interface or config>service>ies>interface).

Static Groups

Static IGMP and MLD group memberships can be configured so that multicast forwarding can be set up without any host receivers in the group. When static IGMP or MLD group membership is enabled, data is forwarded to an interface even though membership reports from one or more host members have not been received.

When static IGMP or MLD group entries on point-to-point links that connect routers to a rendezvous point (RP) are configured, the static IGMP or MLD group entries do not generate join messages toward the RP. When a host wants to receive multicast sessions, it sends a join message to each multicast group it wants to join. When a host wants to leave a multicast session, it sends a Leave message to each multicast group it wants to leave.

A multicast router keeps a list of multicast group memberships for each attached network and an interval timer for each membership. Host receivers issue a Multicast Group Membership Report when they want to receive a multicast session. In MLDv2, Leaves and Joins are both sub-messages of Report messages. These reports are sent to all multicast routers.

SSM Translation

The 7705 SAR supports SSM translation at both the protocol level and the interface level for both IGMP and MLD. When configured at the protocol level, the specified group and source addresses apply to all newly created IGMP and MLD interfaces. Configuring ssm-translation at the interface level overrides any protocol-level values for the specified interface.

PIM

Use the config>router>pim command to enable the PIM CLI context. The PIM protocol is not operational until at least one interface is specified for it, at which time the interface is enabled for PIM and is called a PIM interface. Once enabled, a PIM interface can be configured with PIM parameters, which are in addition to the standard parameters for the interface when it is created. When PIM is operational, data is forwarded to network segments with active host receivers that have explicitly requested the multicast group.

Note:

  • Before an IP interface can be specified in the PIM context, it must be created on the 7705 SAR (config>router>interface or config>service>ies>interface).

  • PIM interfaces can be automatically created once an IP or IES interface has been created by using the apply-to command.

Hardware Support

IGMP and MLD are supported on the following:

  • all Ethernet adapter cards

  • 6-port SAR-M Ethernet module

  • 2-port 10GigE (Ethernet) module

  • 4-port SAR-H Fast Ethernet module

  • all datapath Ethernet ports on all fixed 7705 SAR platforms

PIM-SSM and PIM-SM are supported on the following:

  • all Ethernet adapter cards

  • 6-port SAR-M Ethernet module

  • 2-port 10GigE (Ethernet) module

  • 4-port SAR-H Fast Ethernet module

  • all T1/E1 adapter cards

  • all OC3/STM1 adapter cards

  • the 4-port DS3/E3 Adapter card

  • all datapath Ethernet ports on all fixed 7705 SAR platforms

Basic IP Multicast Configuration

Perform the following basic multicast configuration tasks:

Note: Interfaces are created using the config>router>interface or config>service>ies>interface command (IES only), and then enabled and configured for IGMP, MLD, or PIM using the config>router>igmp>interface or mld>interface or pim>interface command.

For IGMP:

  • enable IGMP (required)

  • configure IGMP interfaces (required)

  • specify IGMP version on the interface (optional)

  • configure static (S,G) or (*,G) (optional)

  • configure SSM translation (optional)

For MLD:

  • enable MLD (required)

  • configure MLD interfaces (required)

  • specify MLD version on the interface (optional)

  • configure static (S,G) or (*,G) (optional)

  • configure SSM translation (optional for (S,G), required for (*,G))

For PIM:

  • enable PIM (required)

  • add interfaces so the protocol establishes adjacencies with the neighboring routers (required)

  • configure a group-to-RP mapping (required) by either:

    • configuring static group-to-RP mapping

    • enabling candidate RP or bootstrap mechanism on some routers

  • enable unicast routing protocols to learn routes towards the RP (for (*,G)) and source (for (S,G)) for reverse path forwarding (required)

  • add SSM ranges (optional)

  • enable candidate BSR (optional)

  • enable candidate RP (optional)

  • change hello interval (optional)

  • configure route policies (bootstrap-export, bootstrap-import, and import join and register) (optional)

For MSDP:

  • enable MSDP (required)

  • configure a peer

  • configure the local address

The following examples show information displays for IGMP, MLD, PIM, and MSDP. For IGMP, MLD, and PIM, each protocol shows the following output:

  • without an interface specified (detailed information)

  • with an interface specified (detailed information)

IGMP

*A:7705custDoc:Sar18>config>router>igmp# info detail
#--------------------------------------------------
            query-interval 125
            query-last-member-interval 1
            query-response-interval 10
            robust-count 2
            no shutdown
#--------------------------------------------------

*A:7705custDoc:Sar18>config>router>igmp# info detail
----------------------------------------------
        interface "igmp_interface"
            no import
            version 3
            subnet-check
            no max-groups
            no max-grp-sources
            no disable-router-alert-check
            no shutdown
        exit
        query-interval 125
        query-last-member-interval 1
        query-response-interval 10
        robust-count 2
        no shutdown
----------------------------------------------
*A:7705custDoc:Sar18>config>router>igmp#

MLD

*A:7705custDoc:Sar18>config>router>mld$ info detail
----------------------------------------------
        query-interval 125
        query-last-listener-interval 1
        query-response-interval 10
        robust-count 2
        no shutdown
----------------------------------------------
*A:7705custDoc:Sar18>config>router>mld$

*A:7705custDoc:Sar18>config>router>mld# info detail
----------------------------------------------
        interface "mld_interface"
            no import
            version 2
            no max-groups
            no disable-router-alert-check
            no query-interval
            no query-response-interval
            no query-last-listener-interval
            no shutdown
        exit
        query-interval 125
        query-last-listener-interval 1
        query-response-interval 10
        robust-count 2
        no shutdown
----------------------------------------------
*A:7705custDoc:Sar18>config>router>mld#

PIM

*A:7705custDoc:Sar18>config>router>pim# info detail
----------------------------------------------
            rpf-table rtable-u
            rpf6-table rtable6-u
            no import join-policy
            no import register-policy
            apply-to none
            rp
                no bootstrap-import
                no bootstrap-export
                static
                exit
                bsr-candidate
                    shutdown
                    priority 0
                    hash-mask-len 30
                    no address
                exit
                rp-candidate
                    shutdown
                    no address
                    holdtime 150
                    priority 192
                exit
            exit
            no non-dr-attract-traffic
            no ssm-default-range-disable ipv4
            no ssm-default-range-disable ipv6
            no shutdown
            no ipv4-multicast-disable
            ipv6-multicast-disable
----------------------------------------------
*A:7705custDoc:Sar18>config>router>pim# 

*A:7705custDoc:Sar18>config>router>pim# info detail
----------------------------------------------
            rpf-table rtable-u
            rpf6-table rtable6-u
            no import join-policy
            interface "pim_interface"
                hello-interval 30
                hello-multiplier 35
                no tracking-support
                no improved-assert
                no bfd-enable
                no bfd-enable ipv6
                no three-way-hello
                priority 1
                multicast-senders auto
                no bsm-check-rtr-alert
                no sticky-dr
                no max-groups
                no assert-period
                no instant-prune-echo
                no shutdown
                no ipv4-multicast-disable
                no ipv6-multicast-disable
            exit
            apply-to none
            rp
                no bootstrap-import
                no bootstrap-export
                static
                exit
                bsr-candidate
                    shutdown
                    priority 0
                    hash-mask-len 30
                    no address
                exit
                rp-candidate
                    shutdown
                    no address
                    holdtime 150
                    priority 192
                exit
            exit
            no non-dr-attract-traffic
            no ssm-default-range-disable ipv4
            no ssm-default-range-disable ipv6
            no shutdown
            no ipv4-multicast-disable
            ipv6-multicast-disable
----------------------------------------------
*A:7705custDoc:Sar18>config>router>pim#

MSDP

*A:7705custDoc:Sar18>config>router>msdp# info detail
----------------------------------------------
        peer 10.20.1.1 
            local-address 10.20.1.6 
        exit 
----------------------------------------------
*A:7705custDoc:Sar18>config>router>pim# 

Common Configuration Tasks

The following sections show the CLI syntax and examples for:

Configuring IGMP and MLD Parameters

This section contains the following subsections:

Enabling IGMP or MLD

Use the following CLI syntax to enable IGMP or MLD.

CLI Syntax:
config>router# igmp
CLI Syntax:
config>router# mld

The following displays an enabled IGMP example. An MLD display would look similar.

*A:7705custDoc:Sar18>config>router# info detail
...
#------------------------------------------
echo "IGMP Configuration"
#------------------------------------------
     igmp
          query-interval 125
          query-last-member-interval 1
          query-response-interval 10
          robust-count 2
          no shutdown
     exit
#------------------------------------------
*A:7705custDoc:Sar18>config>system#

Configuring IGMP and MLD

Use the following CLI syntax to configure IGMP and MLD:

CLI Syntax:
config>router# igmp
    query-interval seconds
    query-last-member-interval seconds
    query-response-interval seconds
    robust-count robust-count 
    [no] shutdown
CLI Syntax:
config>router# mld
    query-interval seconds
    query-last-member-interval seconds
    query-response-interval seconds
    robust-count robust-count 
    [no] shutdown

The following displays an IGMP configuration example. An MLD example would look similar.

Example:
config>router# igmp
config>router>igmp# query-interval 150 
config>router>igmp>if# query-last-member-interval 3
config>router>igmp>if# query-response-interval 15
config>router>igmp>if# robust count 3
config>router>igmp>if# exit

*A:7705custDoc:Sar18>config>router>igmp# info detail
----------------------------------------------
        query-interval 150
        query-last-member-interval 3
        query-response-interval 15
        robust-count 3
        no shutdown
----------------------------------------------
*A:7705custDoc:Sar18>config>router>igmp#

Configuring IGMP and MLD Interfaces

IGMP and MLD are supported on both access and network interfaces.

Note: MLD ‟query” parameters can be configured at both the MLD protocol and interface levels. When configured at the protocol level, settings apply to all new interfaces added to the context. Configuring the ‟query” parameters at the interface level overrides the protocol-level configuration for the specified interface.

See Configuring IGMP and MLD for an example of query parameter configuration.

Use the following CLI syntax to configure an IGMP or MLD interface:

CLI Syntax:
config>router# igmp
    interface ip-int-name
        [no] disable-router-alert-check 
        [no] import policy-name
        [no] max-groups value
        [no] max-grp-sources value
        [no] subnet-check 
        [no] version version
        [no] shutdown
CLI Syntax:
config>router# mld
    interface ip-int-name
        [no] disable-router-alert-check 
        [no] import policy-name
        [no] max-groups value
        [no] query-interval seconds
        [no] query-last-member-interval seconds
        [no] query-response-interval seconds
        [no] version version
        [no] shutdown

The following example displays IGMP interface configuration command usage. An MLD interface example would look similar.

Example:
config>router#
config>router>igmp# interface "igmp_interface"
config>router>igmp>if# max-groups 3
config>router>igmp>if# max-grp-sources 2
config>router>igmp>if# import igmp_policy1
config>router>igmp>if# exit

The following example displays the IGMP interface configuration:

*A:7705custDoc:Sar18>config>router>igmp>interface# info detail
----------------------------------------------
        interface "igmp_interface"
            import igmp_policy1
            version 3
            subnet-check
            max-groups 3
            max-grp-sources 2
            no disable-router-alert-check
            no shutdown
        exit
----------------------------------------------
*A:7705custDoc:Sar18>config>router>igmp#

Configuring IGMP and MLD Interface Static Multicast

The maximum number of static groups and sources that can be configured on a group interface is controlled by the max-groups and max-grp-sources commands. A static (*,G) cannot be added to a group if an (S,G) exists. Similarly, a static (S,G) cannot be added to a group if a (*,G) exists.

A static group is not created until a source has been specified.

Use the following syntax to configure an IGMP or MLD static multicast group and source for a multicast interface:

CLI Syntax:
config>router# igmp
    interface ip-int-name
        static
            group grp-ip-address
                source ip-address
                starg
CLI Syntax:
config>router# mld
    interface ip-int-name
        static
            group grp-ipv6-address
                source ipv6-address
                starg

The following example displays an IGMP interface configuration for static multicast. An MLD interface example would look similar except that it would use IPv6 group and source addresses.

Example:
config>router>igmp# interface igmp_interface
config>router>igmp>if# static
config>router>igmp>if>static# group 239.255.1.3
config>router>igmp>if>static>group# source 10.0.2.8
config>router>igmp>if>static>group# source 10.0.2.9
config>router>igmp>if>static# group 239.255.0.3
config>router>igmp>if>static>group# exit
config>router>igmp>if>static>group# source 10.0.184.197
config>router>igmp>if>static>group# source 10.0.184.198
config>router>igmp>if>static>group# exit
config>router>igmp>if>static# exit
config>router>igmp>if# exit

The following example displays the configuration for IGMP. An MLD example would look similar except that it would use IPv6 group and source addresses.

A:7705custDoc:Sar18>config>router>igmp# info
----------------------------------------------
     interface "igmp_interface"
          static
               group 239.255.1.3
                    source 10.0.2.8
                    source 10.0.2.9
               exit
               group 239.255.0.3
                    source 10.0.184.197
                    source 10.0.184.198
               exit
          exit
     exit
----------------------------------------------
A:7705custDoc:Sar18>config>router>igmp#

Configuring IGMP and MLD SSM Translation

SSM translation can be configured for IGMP and MLD at the protocol and the interface levels. When configured at the protocol level, settings apply to all new interfaces added to the context. Configuring SSM translation at the interface level overrides the protocol-level configuration for the specified interface.

The group range is not created until a source has been specified.

Use the following syntax to configure IGMP and MLD SSM translation parameters at the protocol and interface levels:

CLI Syntax:
config>router# igmp
    ssm-translate
        grp-range start end
            source ip-address
CLI Syntax:
config>router# igmp
    interface ip-int-name
        ssm-translate
            grp-range start end
                source ip-address
CLI Syntax:
config>router# mld
    ssm-translate
        grp-range start end
            source ipv6-address
CLI Syntax:
config>router# mld
    interface ip-int-name
        ssm-translate
            grp-range start end
                source ipv6-address

The following example displays the command usage to configure IGMP SSM translation at the protocol and interface levels. Examples for MLD protocol and MLD interfaces would look similar. MLD would use IPv6 group and source addresses.

Example:
config>router# igmp
config>router>igmp# ssm-translate
config>router>igmp>ssm# grp-range 192.0.2.0 192.0.2.10
config>router>igmp>ssm>grp-range# source 10.10.10.100
config>router>igmp>ssm>grp-range# exit
config>router>igmp# interface igmp_if
config>router>igmp>interface>ssm# grp-range 192.0.2.20 192.0.2.30
config>router>igmp>interface>ssm>grp-range# source 10.10.10.110
config>router>igmp>interface>ssm>grp-range# source 10.10.10.111

The following example displays the SSM translation configuration at the IGMP protocol and interface levels: 

A:7705custDoc:Sar18>config>router>igmp# info
----------------------------------------------
     ssm-translate
          grp-range 192.0.2.0 192.0.2.10 
               source 10.10.10.100 
          exit
     interface "igmp_if"
         max-groups 2
         max-grp-sources 3
         ssm-translate
             grp-range 192.0.2.20 192.0.2.30
                 source 10.10.10.110
                 source 10.10.10.111
         exit
----------------------------------------------
A:7705custDoc:Sar18>config>router>igmp# exit

Configuring PIM Parameters

This section contains the following subsections:

Enabling PIM

When configuring PIM, make sure to enable PIM on all interfaces for the routing instance; otherwise, multicast routing errors can occur.

Use the following CLI syntax to enable PIM.

CLI Syntax:
config>router# pim

The following example displays the detailed output when PIM is enabled without a PIM interface configured. See Configuring PIM Interface Parameters for the additional configuration settings when a PIM interface is configured.

Without a PIM interface enabled

*A:7705custDoc:Sar18>config>router>pim# info detail
----------------------------------------------
            rpf-table rtable-u
            rpf6-table rtable6-u
            no import join-policy
            no import register-policy
            apply-to none
            rp
                no bootstrap-import
                no bootstrap-export
                static
                exit
                bsr-candidate
                    shutdown
                    priority 0
                    hash-mask-len 30
                    no address
                exit
                rp-candidate
                    shutdown
                    no address
                    holdtime 150
                    priority 192
                exit
            exit
            no non-dr-attract-traffic
            no ssm-default-range-disable ipv4
            no ssm-default-range-disable ipv6
            no shutdown
            no ipv4-multicast-disable
            ipv6-multicast-disable
----------------------------------------------
*A:7705custDoc:Sar18>config>router>pim#

With a PIM interface enabled

*A:7705custDoc:Sar18>config>router>pim# info detail
----------------------------------------------
            rpf-table rtable-u
            rpf6-table rtable6-u
            no import join-policy
            no import register-policy
            interface "pim_interface"
                hello-interval 30
                hello-multiplier 35
                no tracking-support
                no bfd-enable
                no bfd-enable ipv6
                no three-way-hello
                priority 1
                multicast-senders auto
                no bsm-check-rtr-alert
                no sticky-dr
                no max-groups
                no assert-period
                no instant-prune-echo
                no shutdown
                no ipv4-multicast-disable
                no ipv6-multicast-disable
            exit
            apply-to none
            rp
                no bootstrap-import
                no bootstrap-export
            exit
            no non-dr-attract-traffic
            no shutdown
            no ipv4-multicast-disable
            ipv6-multicast-disable
----------------------------------------------
*A:7705custDoc:Sar18>config>router>pim#

Configuring PIM Interface Parameters

To create a PIM interface, first create an IP interface using the config>router> interface or the config>service>ies>interface command (IES only). Then use the config>router>pim>interface command to configure PIM interface parameters.

The following example displays the command usage to configure PIM interface parameters:

Example:
config>router# pim 
config>router>pim# interface "pim_interface"
config>router>pim>if# assert-period assert-period 
config>router>pim>if# [no] bfd-enable [ipv4 | ipv6]
config>router>pim>if# [no] bsm-check-rtr-alert 
config>router>pim>if# hello-interval hello-interval 
config>router>pim>if# hello-multiplier deci-units 
config>router>pim>if# instant-prune-echo 
config>router>pim>if# [no] ipv4-multicast-disable 
config>router>pim>if# [no] ipv6-multicast-disable 
config>router>pim>if# max-groups value 
config>router>pim>if# multicast-senders auto 
config>router>pim>if# priority dr-priority 
config>router>pim>if# [no] shutdown 
config>router>pim>if# sticky-dr [priority dr-priority] 
config>router>pim>if# [no] three-way-hello 
config>router>pim>if# [no] tracking-support 
config>router>pim>if# exit

The following example displays the detailed PIM interface configuration:

*A:7705custDoc:Sar18>config>router>pim# info detail
----------------------------------------------
...
            interface "pim_interface"
                hello-interval 30
                hello-multiplier 35
                no tracking-support
                no bfd-enable
                no bfd-enable ipv6
                no three-way-hello
                multicast-senders auto
                no bsm-check-rtr-alert
                priority 1
                no sticky-dr
                no max-groups
                no assert-period
                no instant-prune-echo
                no shutdown
                no ipv4-multicast-disable
                no ipv6-multicast-disable
            exit
...

Configuring a Rendezvous Point (RP)

When configuring a Rendezvous Point (RP), you can configure parameters for an RP candidate, a BSR candidate, or a static RP.

The following example displays the command usage to configure an RP:

Example:
config>router# pim 
config>router>pim# rp 
config>router>pim>rp# anycast rp-ip-address
config>router>pim>rp>anycast# rp-set-peer ip-address 
config>router>pim>rp# auto-rp-discovery 
config>router>pim>rp# bootstrap-export policy-name 
config>router>pim>rp# bootstrap-import policy-name 
config>router>pim>rp# bsr-candidate 
config>router>pim>rp>bsr-candidate# address ip-address 
config>router>pim>rp# rp-candidate 
config>router>pim>rp>rp-candidate# address ip-address 
config>router>pim>rp>rp-candidate# group-range {grp-ip-address/mask | grp-ip-address netmask}
config>router>pim>rp# static 
config>router>pim>rp>static# address ip-address 
config>router>pim>rp>static# group-prefix {grp-ip-address/mask | grp-ip-address netmask} 
config>router>pim>rp>static# override

The following example displays the detailed RP configuration:

*A:7705custDoc:Sar18 Dut-B>config>router>pim>rp# info detail
----------------------------------------------
                    no bootstrap-import
                    no bootstrap-export
                    static
                    exit
                    bsr-candidate
                        shutdown
                        priority 0
                        hash-mask-len 30
                        no address
                    exit
                    rp-candidate
                        shutdown
                        no address
                        group-range 224.0.0.0/4 
                        group-range 224.0.0.0/8 
                        group-range 224.0.0.0/12 
                        holdtime 150
                        priority 192
                    exit
                    anycast 10.10.10.12
                        rp-set-peer 10.10.10.13
                    exit

Importing PIM Join or Register Policies

The import command provides a mechanism to control the (*,G) or (S,G) state that gets created on a router. Import policies are defined in the config>router>policy-options context.

Up to five join policies can be included in a single join-policy command and up to five register policies can be included in a single register-policy command. Each use of the join-policy or register-policy command overrides the previous use and resets the list of import policies.

Note: In the import policy, if a policy action is not specified in the entry, the default-action takes precedence. Similarly, if there are no entry matches, the default-action takes precedence. If no default-action is specified, the default default-action is executed.

Use the following commands to import PIM join policies:

CLI Syntax:
config>router# pim
    import {join-policy | register-policy} [policy-name [...up to 5 max]]

The following example displays the commands used to import a join policy statement named ‟pim_join”. The example also displays the commands used to import three register policies. For information about configuring a join or register policy, see the ‟Configuring PIM Join or Register Policies” section in the 7705 SAR Router Configuration Guide.

Example:
config>router# pim
config>router>pim# import join-policy ‟pim_join”
config>router>pim# import register-policy ‟register_join” ‟register_join2” ‟register_join3”
config>router>pim# no shutdown

The following example displays the PIM configuration:

A:7705custDoc:Sar18>config>router>pim# info
----------------------------------------------
...
     import join-policy "pim_join"
     import register-policy "register_join" "register_join2" "register_join3"
     interface "pim_interface"
     exit
...
----------------------------------------------
A:7705custDoc:Sar18>config>router>pim#

Configuring Multicast Source Discovery Protocol (MSDP) Parameters

Use the following CLI syntax to configure MSDP parameters:

CLI Syntax:
config>router# msdp
    peer peer-address
        active-source-limit number
        authentication-key [authentication-key|hash-key]
        [hash|hash2]
        default-peer
        export policy-name [policy-name...(up to 5 max)]
        import policy-name [policy-name...(up to 5 max)]
        local-address address
        receive-msdp-msg-rate number interval seconds [threshold number]
        no shutdown
    no shutdown

The following example displays the command usage to configure basic MSDP parameters.

Example:
config>router>msdp# peer 10.20.1.1
config>router>msdp>peer# local-address 10.20.1.6
config>router>msdp>peer# no shutdown
config>router>msdp>peer# exit
config>router>msdp# no shutdown
config>router>msdp#

The following example displays the basic MSDP for configuration. 

ALA-48>config>router>msdp# info
-------------------------------------------
        peer 10.20.1.1
            local-address 10.20.1.6
        exit
-------------------------------------------
ALA-48>config>router>msdp#

Service Management Tasks

This section discusses the following multicast configuration management tasks:

Disabling IGMP, MLD, PIM, and MSDP

To disable IP multicast, disable PIM and disable IGMP or MLD (or both).

Use the following CLI syntax to disable IGMP, MLD, PIM, and MSDP:

CLI Syntax:
config>router#
    igmp
    shutdown
    mld
    shutdown
    pim
    shutdown
    msdp
    shutdown

The following example displays the command usage to disable multicast:

Example:
config>router# igmp
config>router>igmp# shutdown
config>router>igmp# exit
config>router# mld
config>router>mld# shutdown
config>router>mld# exit
config>router# pim
config>router>pim# shutdown
config>router>pim# exit
config>router# msdp
config>router>msdp# shutdown
config>router>msdp# exit

The following example displays the configuration outputs:

*A:7705custDoc:Sar18>config>router>igmp# info detail
----------------------------------------------
        shutdown
        interface "igmp_interface"
            no import
            version 3
            subnet-check
            no max-groups
            no disable-router-alert-check
            ssm-translate
                grp-range 239.255.0.0  239.255.20.20 
                    source 10.10.10.10
                exit
                grp-range 239.255.50.50  239.255.70.70
                    source 10.10.10.11
                exit
            exit
            no shutdown
        exit
        query-interval 125
        query-last-member-interval 1
        query-response-interval 10
        robust-count 2
----------------------------------------------
*A:7705custDoc:Sar18>config>router>igmp#

*A:7705custDoc:Sar18>config>router>mld# info detail
----------------------------------------------
        shutdown
        interface "mld_interface"
            no import
            version 2
            no max-groups
            no disable-router-alert-check
            no query-interval
            no query-response-interval
            no query-last-listener-interval
            no shutdown
        exit
        query-interval 125
        query-last-listener-interval 1
        query-response-interval 10
        robust-count 2
----------------------------------------------
*A:7705custDoc:Sar18>config>router>mld#

*A:7705custDoc:Sar18>config>router>pim# info detail
----------------------------------------------
            shutdown
            rpf-table rtable-u
            rpf6-table rtable6-u
            no import join-policy
            interface "pim_interface"
                hello-interval 30
                hello-multiplier 35
                no tracking-support
                no bfd-enable
                no bfd-enable ipv6
                no three-way-hello
                priority 1
                no sticky-dr
                no max-groups
                no assert-period
                instant-prune-echo
                no shutdown
                no ipv4-multicast-disable
                no ipv6-multicast-disable
            exit
            apply-to all
            rp
                no bootstrap-import
                no bootstrap-export
            exit
            no non-dr-attract-traffic
            no ipv4-multicast-disable
            ipv6-multicast-disable
----------------------------------------------
*A:7705custDoc:Sar18>config>router>pim#

#--------------------------------------------------
echo "MSDP Configuration"
#--------------------------------------------------
    msdp
            shutdown
        peer 10.20.1.1
            local-address 10.20.1.6
        exit
        group "test"
            active-source-limit 50000
            receive-msdp-msg-rate 100 interval 300 threshold 5000
            export "LDP-export"
            import "LDP-import"
            local-address 10.10.10.103
            mode mesh-group
            peer 10.10.10.104
            exit
        exit
    exit
#--------------------------------------------------

IP Multicast Command Reference

Command Hierarchies

Configuration Commands

IGMP Commands
configure
    - router
        - [no] igmp 
            - [no] interface ip-int-name
                - [no] disable-router-alert-check 
                - import policy-name
                - no import 
                - max-groups value
                - no max-groups 
                - max-grp-sources value
                - no max-grp-sources 
                - [no] shutdown 
                - ssm-translate 
                    - [no] grp-range start end
                        - [no] source ip-address
                - static 
                    - [no] group grp-ip-address
                        - [no] source ip-address
                - [no] subnet-check 
                - version version
                - no version 
            - query-interval seconds
            - no query-interval 
            - query-last-member-interval seconds
            - no query-last-member-interval 
            - query-response-interval seconds
            - no query-response-interval 
            - robust-count robust-count
            - no robust-count 
            - [no] shutdown 
            - ssm-translate 
                - [no] grp-range start end
                    - [no] source ip-address
MLD Commands
configure
    - router
        - [no] mld 
            - [no] interface ip-int-name
                - [no] disable-router-alert-check 
                - import policy-name 
                - no import 
                - max-groups value 
                - no max-groups 
                - query-interval seconds 
                - no query-interval 
                - query-last-listener-interval seconds 
                - no query-last-listener-interval 
                - query-response-interval seconds 
                - no query-response-interval 
                - [no] shutdown 
                - no ssm-translate 
                    - [no] grp-range start end 
                        - [no] source ipv6-address 
                - static 
                    - [no] group grp-ipv6-address 
                        - [no] source src-ipv6-address 
                - version version 
                - no version 
            - query-interval seconds 
            - no query-interval 
            - query-last-listener-interval seconds 
            - no query-last-listener-interval 
            - query-response-interval seconds 
            - no query-response-interval 
            - robust-count seconds 
            - no robust-count 
            - [no] shutdown 
            - no ssm-translate 
                - [no] grp-range start end 
                    - [no] source src-ipv6-address
PIM Commands
configure
    - router
        - [no] pim 
            - apply-to {ies | non-ies | all | none} 
            - import {join-policy | register-policy} policy-name[.. policy-name (up to 5 max)] 
            - no import {join-policy | register-policy}
            - [no] interface ip-int-name
                - assert-period assert-period 
                - no assert-period 
                - [no] bfd-enable [ipv4 | ipv6] 
                - [no] bsm-check-rtr-alert
                - hello-interval hello-interval 
                - no hello-interval 
                - hello-multiplier deci-units 
                - no hello-multiplier 
                - [no] instant-prune-echo 
                - [no] ipv4-multicast-disable 
                - [no] ipv6-multicast-disable 
                - max-groups value 
                - no max-groups 
                - multicast-senders {auto | always | never}
                - no multicast-senders
                - multicast-to-multicast source ip-address group-start ip-address group-end ip-address to-multicast group-address
                - no multicast-to-multicast 
                - priority dr-priority 
                - no priority 
                - [no] shutdown 
                - sticky-dr [priority dr-priority]
                - no sticky-dr 
                - [no] three-way-hello 
                - [no] tracking-support 
                - unicast-to-multicast unicast-start ip-address unicast-end ip-address destination ip-address to-multicast ip-address
                - no unicast-to-multicast 
            - [no] ipv4-multicast-disable 
            - [no] ipv6-multicast-disable 
            - [no] non-dr-attract-traffic 
            - rp 
                - [no] anycast rp-ip-address
                    - [no] rp-set-peer ip-address
                - [no] auto-rp-discovery
                - bootstrap-export policy-name[...policy-name (up to 5 max)] 
                - no bootstrap-export 
                - bootstrap-import policy-name[...policy-name (up to 5 max)] 
                - no bootstrap-import 
                - bsr-candidate
                    - address ipv4-address
                    - no address
                    - hash-mask-len hash-mask-length
                    - no hash-mask-len
                    - priority bootstrap-priority
                    - no priority
                    - [no] shutdown
                - rp-candidate
                    - address ip-address
                    - no address
                    - [no] group-range {grp-ip-address/mask | grp-ip-address netmask}
                    - holdtime holdtime
                    - no holdtime
                    - priority priority
                    - no priority
                    - [no] shutdown
                - static
                    - [no] address ip-address
                        - [no] group-prefix {grp-ip-address/mask | grp-ip-address netmask} 
                        - [no] override
            - rpf-table {rtable-m | rtable-u | both} 
            - no rpf-table 
            - rpf6-table {rtable6-m | rtable6-u | both} 
            - no rpf6-table 
            - [no] shutdown 
            - spt-switchover-threshold {grp-ipv4-prefix/ipv4-prefix-length | grp-ipv4-prefix netmask | grp-ipv6-prefix/ipv6-prefix-length} spt-threshold
            - no spt-switchover-threshold {grp-ipv4-prefix/ipv4-prefix-length | grp-ipv4-prefix netmask | grp-ipv6-prefix/ipv6-prefix-length}
            - [no] ssm-default-range-disable ipv4 
            - [no] ssm-default-range-disable ipv6
            - [no] ssm-groups 
                - [no] group-range {ip-prefix/mask | ip-prefix netmask}
MSDP Commands
config
    - router
        - [no] msdp
            - [no] active-source-limit number 
            - [no] data-encapsulation 
            - export policy-name [policy-name...(up to 5 max)]
            - no export
            - [no] group group-name 
                - active-source-limit number 
                - no active-source-limit
                - export policy-name [policy-name...(up to 5 max)]
                - no export
                - import policy-name [policy-name...(up to 5 max)]
                - no import
                - local-address address
                - no local-address
                - mode {mesh-group | standard}
                - [no] peer peer-address
                    - active-source-limit number 
                    - no active-source-limit
                    - authentication-key [authentication-key | hash-key] [hash | hash2]
                    - no authentication-key
                    - [no] default-peer
                    - export policy-name [policy-name...(up to 5 max)]
                    - no export
                    - import policy-name [policy-name...(up to 5 max)]
                    - no import
                    - local-address address
                    - no local-address
                    - receive-msdp-msg-rate number interval seconds [threshold number] 
                    - no receive-msdp-msg-rate
                    - [no] shutdown 
                - receive-msdp-msg-rate number interval seconds [threshold number] 
                - no receive-msdp-msg-rate
                - [no] shutdown
            - import policy-name [policy-name...(up to 5 max)]
            - no import
            - local-address address
            - no local-address
            - [no] peer peer-address 
                - active-source-limit number 
                - no active-source-limit
                - authentication-key [authentication-key | hash-key] [hash | hash2]
                - no authentication-key
                - [no] default-peer
                - export policy-name [policy-name...(up to 5 max)]
                - no export
                - import policy-name [policy-name...(up to 5 max)]
                - no import
                - local-address address
                - no local-address
                - receive-msdp-msg-rate number interval seconds [threshold number] 
                - no receive-msdp-msg-rate
                - [no] shutdown
            - receive-msdp-msg-rate number interval seconds [threshold number] 
            - no receive-msdp-msg-rate
            - rpf-table {rtable-m | rtable-u | both}
            - no rpf-table
            - sa-timeout seconds
            - no sa-timeout
            - [no] shutdown
            - [no] source ip-prefix/mask 
                - active-source-limit number 
                - no active-source-limit

Show Commands

show
    - router
        - igmp 
            - group [grp-ip-address] 
            - group summary
            - interface [ip-int-name | ip-address] [group] [grp-ip-address] [detail] 
            - ssm-translate [interface-name] 
            - static [ip-int-name | ip-address] 
            - statistics [ip-int-name | ip-address] 
            - status 

show
    - router
        - mld 
            - group [grp-ipv6-address] 
            - interface [ip-int-name | ip-address] [group] [grp-ipv6-address] [detail] 
            - ssm-translate [ip-int-name] 
            - static [ip-int-name | ip-address] 
            - statistics [ip-int-name | ipv6-address] 
            - status 

show
    - router
        - pim 
            - group [grp-ip-address] [source ip-address] [detail] [family] 
            - interface [ip-int-name | ip-address] [group grp-ip-address] [source ip-address] [detail] [family]
            - interface ip-int-name 
                - multicast-translation type {unicast-to-multicast | multicast-to-multicast}
            - neighbor [ip-int-name | ip-address [address neighbor-ip-address]] [detail] [family]
            - rp [family | ip-address] 
            - rp-hash [family | ip-address] 
            - s-pmsi [family | ip-address] 
            - statistics [ip-int-name | ip-address] [family]
            - status [detail] [family] 

show
    - router
        - msdp
            - group [group-name] [detail]
            - peer [ip-address] [group group-name] [detail]
            - source [ip-address/mask] [type {configured | dynamic | both}] [detail]
            - source-active [{group ip-address | local | originator ip-address | peer ip-address | source ip-address | group ip-address source ip-address}] [detail]
            - source-active-rejected [peer-group name] [group ip-address] [source ip-address] [originator ip-address] [peer ip-address]
            - statistics [peer ip-address]
            - status

Clear Commands

clear
    - router 
        - igmp 
            - database [interface ip-int-name | ip-address] [group grp-ip-address [source src-ip-address]] 
            - statistics [ip-int-name | ip-address] 
            - version [ip-int-name | ip-address] 

clear
    - router 
        - mld 
            - database [interface ip-int-name | ipv6-address] [group grp-ipv6-address [source src-ipv6-address]] 
            - statistics [ip-int-name | ipv6-address] 
            - version [ip-int-name | ip-address] 

clear
    - router 
        - pim 
            - database [interface ip-int-name | ip-address] [group grp-ip-address [source ip-address]] [family] 
            - neighbor [ip-int-name] [family] 
            - statistics [family] 
            - statistics interface ip-int-name | ip-address [family] 
            - statistics group grp-ip-address [source ip-address] [family] 

clear
    - router 
        - msdp
            - cache [peer ip-address] [group ip-address] [source ip-address] [originrp ip-address]
            - statistics [peer ip-address]

Monitor Commands

monitor
    - router
        - pim
            - group grp-ip-address [source ip-address] [interval interval] [repeat repeat] [absolute | rate]

Debug Commands

debug
    - router
        - [no] igmp 
            - [no] interface [ip-int-name | ip-address]
            - [no] misc
            - packet [query | v1-report | v2-report | v3-report | v2-leave] [ip-int-name | ip-address] 
            - no packet

debug
    - router
        - [no] mld 
            - [no] interface [ip-int-name | ipv6-address]
            - [no] misc
            - packet [query | v1-report | v2-report | v1-done] [ip-int-name | ipv6-address] 
            - no packet

debug
    - router 
        - [no] msdp
            - packet [pkt-type] [peer ip-address]
            - no packet
            - pim [grp-address]
            - no pim
            - rtm [rp-address]
            - no rtm
            - sa-db [group grpAddr] [source srcAddr] [rp rpAddr]
            - no sa-db

debug
    - router
        - [no] mtrace 
            - [no] misc 
            - [no] packet [query | request | response]

debug
    - router
        - [no] pim 
            - [no] adjacency
            - all [group grp-ip-address] [source ip-address] [detail] 
            - no all
            - assert [group grp-ip-address] [source ip-address] [detail] 
            - no assert
            - auto-rp [detail] 
            - no auto-rp 
            - bgp [group grp-ip-address] [source ip-address] [peer peer-ip-address] [detail] 
            - no bgp
            - bsr [detail] 
            - no bsr 
            - data [group grp-ip-address] [source ip-address] [detail] 
            - no data 
            - db [group grp-ip-address] [source ip-address] [detail] 
            - no db 
            - interface [ip-int-name | ip-address] [detail] 
            - no interface 
            - jp [group grp-ip-address] [source ip-address] [detail] 
            - no jp 
            - mrib [group grp-ip-address] [source ip-address] [detail] 
            - no mrib 
            - msg [detail]
            - no msg 
            - packet [hello | register | register-stop | jp | bsr | assert | crp] [ip-int-name | ip-address] 
            - no packet 
            - [no] red [detail]
            - register [group grp-ip-address] [source ip-address] [detail] 
            - no register 
            - rtm [detail] 
            - no rtm

Command Descriptions

Configuration Commands

Generic Commands
shutdown
Syntax

[no] shutdown

Context

config>router>igmp

config>router>igmp>interface

config>router>mld

config>router>mld>interface

config>router>msdp

config>router>msdp>group

config>router>msdp>group>peer

config>router>msdp>peer

config>router>pim

config>router>pim>interface

config>router>pim>rp>bsr-candidate

config>router>pim>rp>rp-candidate

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.

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.

Default

no shutdown

IGMP Commands
igmp
Syntax

[no] igmp

Context

config>router

Description

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.

Default

n/a

interface
Syntax

[no] interface ip-int-name

Context

config>router>igmp

Description

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.

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>igmp>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 (such as #, $, or spaces), the entire string must be enclosed within double quotes.

disable-router-alert-check
Syntax

[no] disable-router-alert-check

Context

config>router>igmp>interface

Description

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.

Default

no disable-router-alert-check

import
Syntax

import policy-name

no import

Context

config>router>igmp>interface

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 (see the ‟Route Policies” section in the 7705 SAR 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.

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 (such as #, $, or spaces), the entire string must be enclosed within double quotes.

max-groups
Syntax

max-groups value

no max-groups

Context

config>router>igmp>interface

Description

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.

Default

no max-groups

Parameters
value

the maximum number of groups for the interface

Values

1 to 256

max-grp-sources
Syntax

max-grp-sources value

no max-grp-sources

Context

config>router>igmp>interface

Description

This command specifies the maximum number of group sources 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 group sources, the group sources that are already accepted are not deleted. Only new group sources will not be allowed.

The no version of the command removes the configured value and the maximum number of group sources is not defined.

Default

no max-grp-sources

Parameters
value

the maximum number of group sources for the group interface

Values

1 to 256

ssm-translate
Syntax

ssm-translate

Context

config>router>igmp

config>router>igmp>interface

Description

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.

grp-range
Syntax

[no] grp-range start end

Context

config>router>igmp>ssm-translate

config>router>igmp>if>ssm-translate

Description

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.

Default

n/a

Parameters
start

an IP address that specifies the start of the group range

Values

a.b.c.d

end

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

Values

a.b.c.d

source
Syntax

[no] source ip-address

Context

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

config>router>igmp>if>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 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.

Default

n/a

Parameters
ip-address

the unicast IP source address

Values

a.b.c.d

static
Syntax

static

Context

config>router>igmp>interface

Description

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.

Default

n/a

group
Syntax

[no] group grp-ip-address

Context

config>router>igmp>if>static

Description

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.

Default

n/a

Parameters
grp-ip-address

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

Values

a.b.c.d

source
Syntax

[no] source ip-address

Context

config>router>igmp>if>static>group

Description

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.

Default

n/a

Parameters
ip-address

the IPv4 unicast address

Values

a.b.c.d

subnet-check
Syntax

[no] subnet-check

Context

config>router>igmp>interface

Description

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.

Default

enabled

version
Syntax

version version

no version

Context

config>router>igmp>interface

Description

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.

Default

3

Parameters
version

the IGMP version number

Values

1, 2, or 3

query-interval
Syntax

query-interval seconds

no query-interval

Context

config>router>igmp

Description

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.

Default

125

Parameters
seconds

the frequency, in seconds, at which the router transmits general host-query messages

Values

2 to 1024

query-last-member-interval
Syntax

query-last-member-interval seconds

no query-last-member-interval

Context

config>router>igmp

Description

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.

Default

1

Parameters
seconds

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

Values

1 to 1023

query-response-interval
Syntax

query-response-interval seconds

no query-response-interval

Context

config>router>igmp

Description

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

Default

10

Parameters
seconds

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

Values

1 to 1023

robust-count
Syntax

robust-count robust-count

no robust-count

Context

config>router>igmp

Description

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.

Default

2

Parameters
robust-count

the robust count value

Values

2 to 10

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

interface
Syntax

[no] interface ip-int-name

Context

config>router>mld

Description

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.

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 (such as #, $, or spaces), the entire string must be enclosed within double quotes.

disable-router-alert-check
Syntax

[no] disable-router-alert-check

Context

config>router>mld>interface

Description

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.

Default

no disable-router-alert-check (enabled)

import
Syntax

import policy-name

no import

Context

config>router>mld>interface

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.

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.

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 (such as #, $, or spaces), the entire string must be enclosed within double quotes.

max-groups
Syntax

max-groups value

no max-groups

Context

config>router>mld>interface

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

Default

no max-groups

Parameters
value

the maximum number of groups for this interface

Values

1 to 256

query-interval
Syntax

query-interval seconds

no query-interval

Context

config>router>mld

config>router>mld>interface

Description

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.

Default

125

Parameters
seconds

the frequency, in seconds, at which the router transmits general host-query messages

Values

2 to 1024

query-last-listener-interval
Syntax

query-last-listener-interval seconds

no query-last-listener-interval

Context

config>router>mld

config>router>mld>interface

Description

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.

Default

1

Parameters
seconds

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

Values

1 to 1023

query-response-interval
Syntax

query-response-interval seconds

no query-response-interval

Context

config>router>mld

config>router>mld>interface

Description

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

Default

10

Parameters
seconds

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

Values

1 to 1023

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

the robust count value

Values

2 to 10

ssm-translate
Syntax

ssm-translate

Context

config>router>mld

config>router>mld>interface

Description

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.

grp-range
Syntax

[no] grp-range start end

Context

config>router>mld>ssm-translate

config>router>mld>if>ssm-translate

Description

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

Default

n/a

Parameters
start

a valid multicast group IPv6 address that identifies the start of the group range

end

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

source
Syntax

[no] source src-ipv6-address

Context

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

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

Description

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.

Default

n/a

Parameters
src-ipv6-address

the IPv6 address that will be sending data

static
Syntax

static

Context

config>router>mld>interface

Description

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.

Default

n/a

group
Syntax

[no] group grp-ipv6-address

Context

config>router>mld>if>static

Description

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.

Default

n/a

Parameters
grp-ipv6-address

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

source
Syntax

[no] source src-ipv6-address

Context

config>router>mld>if>static>group

Description

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.

Default

n/a

Parameters
src-ipv6-address

the IPv6 unicast address

version
Syntax

version version

no version

Context

config>router>mld>interface

Description

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.

Default

2

Parameters
version

the MLD version number

Values

1 or 2

PIM Commands
pim
Syntax

[no] pim

Context

config>router

Description

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) and PIM sparse mode (SM).

The no form of the command deletes the PIM instance and removes all configuration parameters.

Default

no pim

apply-to
Syntax

apply-to {ies | non-ies | all | none}

Context

config>router>pim

Description

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.

Default

none (keyword)

Parameters
ies

automatically creates a PIM interface for all IES interfaces in PIM

non-ies

creates non-IES interfaces in PIM

all

creates all IES and non-IES interfaces in PIM

none

removes all PIM interfaces that have not been manually created or modified in the PIM context

import
Syntax

import {join-policy | register-policy} [policy-name [.. policy-name (up to 5 max)]

no import {join-policy | register-policy}

Context

config>router>pim

Description

This command specifies the import route policy to be used by PIM. Route policies are configured in the config>router>policy-options context. Up to five import policy names can be specified.

If an import policy is not specified, IGP routes are accepted by default.

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

Default

no import join-policy

no import register-policy

Parameters
join-policy

this keyword filters PIM join messages, which prevents unwanted multicast streams from traversing the network

register-policy

this keyword filters PIM register messages. PIM register filters prevent register messages from being processed by the RP. This filter can only be defined on an RP. When a match is found, the RP immediately sends back a register-stop message.

policy-name

the route policy name

interface
Syntax

[no] interface ip-int-name

Context

config>router>pim

Description

This command creates a logical IP routing interface.

The no form of the command removes the IP interface and all the associated configurations.

Default

no interfaces or names are defined within PIM

Parameters
ip-int-name

the name of the IP interface. If the string contains special characters (such as #, $, or spaces), the entire string must be enclosed within double quotes.

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.

Values

1 to 32 alphanumeric characters

assert-period
Syntax

assert-period assert-period

no assert-period

Context

config>router>pim>interface

Description

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.

Default

no assert-period

Parameters
assert-period

the period for refreshes of PIM Assert messages on an interface

Values

1 to 300 seconds

bfd-enable
Syntax

[no] bfd-enable [ipv4 | ipv6]

Context

config>router>pim>interface

Description

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.

Default

no bfd-enable

bsm-check-rtr-alert
Syntax

[no] bsm-check-rtr-alert

Context

config>router>pim>interface

Description

This command enables the checking of the router alert option in the bootstrap messages received on this interface.

Default

no bsm-check-rtr-alert

hello-interval
Syntax

hello-interval hello-interval

no hello-interval

Context

config>router>pim>interface

Description

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.

Default

30

Parameters
hello-interval

the hello interval in seconds. A 0 (zero) value disables the sending of Hello messages (the PIM neighbor will never time out the adjacency)

Values

0 to 255 seconds

hello-multiplier
Syntax

hello-multiplier deci-units

no hello-multiplier

Context

config>router>pim>interface

Description

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   

Parameters
deci-units

the value, specified in multiples of 0.1, for the formula (above) used to calculate the hold time based on the hello-multiplier

This allows the PIM default timeout of 3.5 seconds to be supported.

Values

20 to 100

Default

35

instant-prune-echo
Syntax

[no] instant-prune-echo

Context

config>router>pim>interface

Description

This command enables or disables instant PruneEcho for a PIM interface.

Default

no instant-prune-echo

ipv4-multicast-disable
Syntax

[no] ipv4-multicast-disable

Context

config>router>pim

config>router>pim>interface

Description

This command administratively disables or enables PIM operation for IPv4.

Default

no ipv4-multicast-disable

ipv6-multicast-disable
Syntax

[no] ipv6-multicast-disable

Context

config>router>pim

config>router>pim>interface

Description

This command administratively disables or enables PIM operation for IPv6.

Default

no ipv6-multicast-disable

max-groups
Syntax

max-groups value

no max-groups

Context

config>router>pim>interface

Description

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.

Default

no max-groups

Parameters
value

the maximum number of groups for this interface

Values

1 to 256

multicast-senders
Syntax

multicast-senders {auto | always | never}

no multicast-senders

Context

config>router>pim>interface

Description

This command configures how traffic from directly attached multicast sources should be treated on broadcast interfaces. It can also be used to treat all traffic received on an interface as traffic coming from a directly attached multicast source. This is particularly useful if a multicast source is connected to a point-to-point or unnumbered interface.

Default

auto

Parameters
auto

specifies that, on broadcast interfaces, the forwarding plane performs a subnet-match check on multicast packets received on the interface to determine if the packet is from a directly attached source. On unnumbered or point-to-point interfaces, all traffic is implicitly treated as coming from a remote source.

always

treats all traffic received on the interface as coming from a directly attached multicast source

never

specifies that, on broadcast interfaces, traffic from directly attached multicast sources will not be forwarded; however, traffic from a remote source will still be forwarded if there is a multicast state for it. On unnumbered or point-to-point interfaces, it means that all traffic received on that interface must not be forwarded.

multicast-to-multicast
Syntax

multicast-to-multicast source ip-address group-start ip-address group-end ip-address to-multicast group-address

no multicast-to-multicast

Context

config>router>pim>interface

Description

This command enables multicast-to-multicast address translation by mapping a range of source IP addresses to a range of multicast group addresses. The PIM interface on the 7705 SAR translator router is the source of the multicast address. Multiple (S,G)s (for example, s1,g1 / s2,g1 / s3,g1) can be mapped to a single PIM interface, using the same source IP address for the translated (S,G) but for a range of groups.

The PIM interface on the translator router must first be enabled for multicast translation with the config>router>interface>multicast-translation command.

Default

no multicast-to-multicast

Parameters
source ip-address

the source address of the (S,G) being translated

group-start ip-address

the starting group address of the (S,G) being translated

group-end ip-address

the ending group address of the (S,G) being translated

group-address

the multicast group address used for translation

priority
Syntax

priority dr-priority

no priority

Context

config>router>pim>interface

Description

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.

Default

1

Parameters
dr-priority

the priority value that is used to elect the DR. The higher the value, the higher the priority.

Values

1 to 4294967295

sticky-dr
Syntax

sticky-dr [priority dr-priority]

no sticky-dr

Context

config>router>pim>interface

Description

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.

Default

no sticky-dr (disabled)

Parameters
priority dr-priority

sets the DR priority to be sent in PIM Hello messages following the election of that interface as the DR, when sticky-dr operation is enabled

Values

1 to 4294967295

three-way-hello
Syntax

[no] three-way-hello

Context

config>router>pim>interface

Description

This command enables three-way hello. By default, three-way hello is disabled on all interfaces and the standard two-way hello is supported.

Default

no three-way-hello

tracking-support
Syntax

[no] tracking-support

Context

config>router>pim>interface

Description

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.

Default

no tracking-support

unicast-to-multicast
Syntax

unicast-to-multicast unicast-start ip-address unicast-end ip-address destination ip-address to-multicast ip-address

no unicast-to-multicast

Context

config>router>pim>interface

Description

This command enables unicast-to-multicast address translation by mapping a range of unicast source addresses and a unicast destination address to a multicast group address. The unicast destination address is a loopback IP address configured on the 7705 SAR that is performing the translation. This translator router becomes the source of the multicast packets. The multicast source address is a loopback interface IP address configured on the PIM interface of the translator router. The PIM interface on the 7705 SAR translator router must first be enabled for multicast translation with the config>router>interface>multicast-translation command.

The unicast destination and the multicast source can be the same loopback address or different loopback addresses.

The translation can map a range of unicast source addresses to a range of multicast group addresses. For example, if the unicast source address range is 1.1.1.1 to 1.1.1.4 and the multicast group address is 230.0.0.100, the following multicast destination address range is created:

Table 4. Multicast Destination Address Range

Unicast Source

Multicast Group

1.1.1.1

230.0.0.100

1.1.1.2

230.0.0.101

1.1.1.3

230.0.0.102

1.1.1.4

230.0.0.103
Default

no unicast-to-multicast

Parameters
unicast-start ip-address

the start of the range of unicast source addresses to be translated

unicast-end ip-address

the end of the range of unicast source addresses to be translated

destination ip-address

the destination address of the unicast stream being translated

multicast ip-address

the group and destination addresses for the multicast stream

non-dr-attract-traffic
Syntax

[no] non-dr-attract-traffic

Context

config>router>pim

Description

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

Default

no non-dr-attract-traffic

rp
Syntax

rp

Context

config>router>pim

Description

This command provides access to the bootstrap import and export policy commands.

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.

anycast
Syntax

[no] anycast rp-ip-address

Context

config>router>pim>rp

Description

This command configures a PIM anycast protocol instance for the RP being configured. Anycast enables fast convergence when a PIM RP router fails by allowing receivers and sources to rendezvous at the closest RP.

The no form of the command removes the anycast instance from the configuration.

Default

n/a

Parameters
rp-ip-address

specifies the loopback IP address shared by all routes that form the RP set for this anycast instance. Only a single address can be configured. If another anycast command is entered with an address, the old address is replaced with the new address. If no IP address is entered, the command is used to enter the anycast CLI level.

Values

any valid loopback address configured on the node

rp-set-peer
Syntax

[no] rp-set-peer ip-address

Context

config>router>pim>rp>anycast

Description

This command configures a peer in the anycast-RP set. The ip-address identifies the address used by the other node as the RP candidate address for the same multicast group address range as configured on this node.

Caution: This is a manual procedure. Caution should be taken to produce a consistent configuration of an RP set for a multicast group address range. The priority should be identical on each node and be a higher value than any other configured RP candidate that is not a member of this RP set.

Although there is no set maximum number of addresses that can be configured in an RP set, a maximum of 15 IP addresses is recommended.

The no form of the command removes an entry from the list.

Default

n/a

Parameters
ip-address

specifies a peer in the anycast-RP set

Values

any valid ip-address within the scope outlined above

auto-rp-discovery
Syntax

[no] auto-rp-discovery

Context

config>router>pim>rp

Description

This command enables auto-RP protocol in discovery mode. In discovery mode, RP-mapping and RP-candidate messages are received and forwarded to downstream nodes. RP-mapping messages are received locally to learn about the availability of RP nodes present in the network.

Either bsr-candidate for IPv4 or auto-rp-discovery can be configured; the two mechanisms cannot be enabled together.

The no form of the command disables auto-RP discovery.

Default

no auto-rp-discovery

bootstrap-export
Syntax

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

no bootstrap-export

Context

config>router>pim>rp

Description

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 about configuring bootstrap policies, see the ‟Configuring Bootstrap Message Import and Export Policies” section of the 7705 SAR Router Configuration Guide.

Default

no bootstrap-export

Parameters
policy-name

the export policy name up

bootstrap-import
Syntax

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

no bootstrap-import

Context

config>router>pim>rp

Description

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 about configuring bootstrap policies, see the ‟Configuring Bootstrap Message Import and Export Policies” section of the 7705 SAR Router Configuration Guide.

Default

no bootstrap-import

Parameters
policy-name

the import policy name

bsr-candidate
Syntax

bsr-candidate

Context

config>router>pim>rp

Description

This command enables the context to configure candidate bootstrap router (BSR) parameters.

Either bsr-candidate for IPv4 or auto-rp-discovery can be configured; the two mechanisms cannot be enabled together.

Default

bsr-candidate shutdown

address
Syntax

address ip-address

Context

config>router>pim>rp>bsr-candidate

Description

This command is used to configure the candidate BSR IP address. This address is for bootstrap router election.

Default

n/a

Parameters
ip-address

specifies the IP host address that will be used by the IP interface within the subnet. This address must be a unique unicast address within the subnet and specified in dotted decimal notation (1.0.0.0 to 223.255.255.255).

Values

a.b.c.d

hash-mask-len
Syntax

hash-mask-len hash-mask-length

no hash-mask-len

Context

config>router>pim>rp>bsr-candidate

Description

This command is used to configure the length of the mask that is combined with the group address before the hash function is called. All groups with the same hash result will map to the same RP. For example, if the hash-mask-length value is 24, only the first 24 bits of the group addresses matter. This mechanism is used to map one group or multiple groups to an RP.

Parameters
hash-mask-length

specifies the hash mask length

Values

0 to 32

priority
Syntax

priority bootstrap-priority

no priority

Context

config>router>pim>rp>bsr-candidate

Description

This command configures the bootstrap priority of the router. The RP is sometimes called the bootstrap router. The priority determines if the router is eligible to be a bootstrap router. In the case of a tie, the router with the highest IP address is elected to be the bootstrap router.

Default

0

Parameters
bootstrap-priority

specifies the priority to become the bootstrap router. The higher the value, the higher the priority. A value of 0 means the router is not eligible to be the bootstrap router. A value of 1 means router is the least likely to become the designated router.

Values

0 to 255

rp-candidate
Syntax

rp-candidate

Context

config>router>pim>rp

Description

This command enables the context to configure the candidate rendezvous point (RP) parameters.

Routers use a set of available rendezvous points distributed in bootstrap messages to get the proper group-to-RP mapping. A set of routers within a domain are also configured as candidate RPs; typically, these will be the same routers that are configured as candidate BSRs.

Every multicast group has a shared tree through which receivers learn about new multicast sources and new receivers learn about all multicast sources. The RP is the root of this shared tree.

Default

shutdown

address
Syntax

address ip-address

no address

Context

config>router>pim>rp>rp-candidate

Description

This command configures the local RP address. This address is sent in the RP candidate advertisements to the bootstrap router.

Default

n/a

Parameters
ip-address

specifies the ip-address of the RP

Values

1.0.0.0 to 223.255.255.255

group-range
Syntax

[no] group-range {grp-ip-address/mask | grp-ip-address netmask}

Context

config>router>pim>rp>rp-candidate

Description

This command configures a range of addresses for the RP candidate group.

Default

n/a

Parameters
grp-ip-address

specifies the multicast group IP address expressed in dotted decimal notation (224.0.0.0 to 239.255.255.255)

Values

a.b.c.d (multicast group address)

mask

specifies the mask associated with the IP prefix expressed as a mask length or in dotted decimal notation; for example /16 for a sixteen-bit mask. The mask can also be entered in dotted decimal notation (255.255.0.0).

Values

4 to 32

netmask

specifies the subnet mask in dotted decimal notation (0.0.0.0 to 255.255.255.255)

Values

a.b.c.d (network bits all 1 and host bits all 0)

holdtime
Syntax

holdtime holdtime

no holdtime

Context

config>router>pim>rp>rp-candidate

Description

This command configures the length of time, in seconds, that neighbors should consider the sending router to be operationally up. A local RP cannot be configured on a logical router.

Parameters
holdtime

specifies the hold time, in seconds

Default

150

Values

5 to 255

priority
Syntax

priority priority

no priority

Context

config>router>pim>rp>rp-candidate

Description

This command configures the candidate RP priority for becoming a rendezvous point (RP). This value is used to elect the RP for a group range.

Default

192

Parameters
priority

specifies the priority to become a rendezvous point (RP). A value of 0 is considered as the highest priority.

Default

192

Values

0 to 255

static
Syntax

static

Context

config>router>pim>rp

Description

This command enables the context to configure static rendezvous point (RP) addresses for a multicast group range.

Entries can be created or destroyed. If no IP addresses are configured in the config>router>pim>rp>static>address context, then the multicast group-to-RP mapping is derived from the RP-set messages received from the bootstrap router.

address
Syntax

address ip-address

no address

Context

config>router>pim>rp>static

Description

This command indicates the rendezvous point (RP) address that is used by the router for the range of multicast groups configured by the range command.

Default

n/a

Parameters
ip-address

specifies the IP host address that will be used by the IP interface within the subnet. This address must be a unique unicast address within the subnet and specified in dotted decimal notation (1.0.0.0 to 223.255.255.255).

Values

a.b.c.d

group-prefix
Syntax

[no] group-prefix {grp-ip-address/mask | grp-ip-address netmask}

Context

config>router>pim>rp>static>address

Description

The command defines a range of multicast IP addresses for which an RP is applicable.

The no form of the command removes the address range.

Default

n/a

Parameters
grp-ip-address

specifies the multicast IP address

Values

a.b.c.d (multicast group address)

mask

specifies the mask of the multicast IP address

Values

4 to 32

netmask

specifies the subnet mask in dotted decimal notation

Values

a.b.c.d (network bits all 1 and host bits all 0)

override
Syntax

[no] override

Context

config>router>pim>rp>static>address

Description

This command changes the precedence of static RP over dynamically learned RP.

When enabled, the static group-to-RP mappings take precedence over the dynamically learned mappings.

Default

no override

rpf-table
Syntax

rpf-table {rtable-m | rtable-u | both}

no rpf-table

Context

config>router>pim

Description

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:

  • use unicast route table only

  • use multicast route table only

  • use both route tables

Default

rtable-u

Parameters
rtable-m

specifies that only the multicast route table will be used by the multicast protocol (PIM) for IPv4 RPF checks. This route table will contain routes submitted by static routes, IS-IS and OSPF.

rtable-u

specifies that only the unicast route table will be used by the multicast protocol (PIM) for IPv4 RPF checks. This route table will contain routes submitted by all the unicast routing protocols.

both

specifies that PIM will always use the multicast route table first, and if there is a route, it will use it. If PIM does not find a route in the first lookup, it will try to find it in the unicast route table.

rpf6-table
Syntax

rpf6-table {rtable6-m | rtable6-u | both}

no rpf6-table

Context

config>router>pim

Description

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:

  • use unicast route table only

  • use multicast route table only

  • use both route tables

Default

rtable6-u

Parameters
rtable6-m

specifies that only the multicast route table will be used by the multicast protocol (PIM) for IPv6 RPF checks. This route table will contain routes submitted by static routes and OSPF.

rtable6-u

specifies that only the unicast route table will be used by the multicast protocol (PIM) for IPv6 RPF checks. This route table will contain routes submitted by all the unicast routing protocols.

both

specifies that PIM will always use the multicast route table first, and if there is a route, it will use it. If PIM does not find a route in the first lookup, it will try to find it in the unicast route table.

spt-switchover-threshold
Syntax

spt-switchover-threshold {grp-ipv4-prefix/ipv4-prefix-length | grp-ipv4-prefix netmask | grp-ipv6-prefix/ipv6-prefix-length} spt-threshold

no spt-switchover-threshold {grp-ipv4-prefix/ipv4-prefix-length | grp-ipv4-prefix netmask | grp-ipv6-prefix/ipv6-prefix-length}

Context

config>router>pim

Description

This command configures the shortest path tree (SPT) switchover thresholds for group prefixes.

PIM-SM routers with directly connected routers receive multicast traffic initially on a shared tree rooted at the RP. When the traffic arrives on the shared tree and the source of the traffic is known, a switchover to the SPT rooted at the source is attempted.

For a group that falls in the range of a prefix configured in the table, the corresponding threshold value determines when the router should switch over from the shared tree to the source-specific tree. The switchover is attempted only if the traffic rate on the shared tree for the group exceeds the configured threshold.

If there is no matching prefix in the table, the default behavior is to switch over when the first packet is seen. If there are multiple prefixes matching a group, the most specific entry is used.

Default

n/a

Parameters
grp-ipv4-prefix

specifies the group IPv4 multicast address in dotted-decimal notation

ipv4-prefix-length

specifies the length of the IPv4 prefix

netmask

specifies the netmask associated with the IPv4 prefix, expressed in dotted-decimal notation. Network bits must be 1, and host bits must be 0.

grp-ipv6-prefix

specifies the group IPv6 multicast address in hexadecimal notation

ipv6-prefix-length

specifies the length of the IPv6 prefix

spt-threshold

specifies the configured threshold in kilobits per second (kbps) for a group prefix. A switchover is attempted only if the traffic rate on the shared tree for the group exceeds this configured threshold. When the infinity keyword is specified, no switchover will occur at any time, regardless of the traffic level detected.

Values

1 to 4294967294 | infinity (threshold in kbps)

ssm-default-range-disable
Syntax

[no] ssm-default-range-disable ipv4

[no] ssm-default-range-disable ipv6

Context

config>router>pim

Description

This command enables and disables the IPv4 and IPv6 SSM default ranges.

Default

no ssm-default-range-disable ipv4 no ssm-default-range-disable ipv6

Parameters
ipv4

specifies IPv4 as the SSM default range

ipv6

specifies IPv6 as the SSM default range

ssm-groups
Syntax

[no] ssm-groups

Context

config>router>pim

Description

This command enables the context to configure an SSM group range.

group-range
Syntax

[no] group-range {ip-prefix/mask | ip-prefix netmask}

Context

config>router>pim>ssm-groups

Description

This command configures the address ranges of the multicast groups for this router. When there are parameters present, the command configures the SSM group ranges for IPv6 addresses and netmasks.

Default

n/a

Parameters
ip-prefix/mask

specifies the IP prefix for the range used by the ABR to advertise that summarizes the area into another area

netmask

specifies the subnet mask in dotted-decimal notation

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.

For MSDP to function, at least one peer must be configured.

When MSDP is configured and started, an event message is generated.

Before the no form of the command is executed, all sessions are terminated and an event message is generated.

When all peering sessions are terminated, event messages are not generated for each peer.

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

Default

no msdp

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

config>router>msdp>peer

config>router>msdp>source

Description

This command controls the maximum number of source-active (SA) messages that will be accepted by MSDP, which controls the number of active sources that can be stored on the system.

The no form of this command resets the SA message limit to its default operation.

Default

no active-source-limit

Parameters
number

defines how many active sources can be maintained by MSDP

Values

0 to 1000000

data-encapsulation
Syntax

[no] data-encapsulation

Context

config>router>msdp

Description

This command configures a rendezvous point (RP) that uses MSDP to encapsulate multicast data received in MSDP register messages inside forwarded MSDP SA messages.

Default

data-encapsulation

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 the SA state from the SA list into MSDP.

If multiple policy names are specified, the policies are evaluated in the order they are specified. A maximum of five policy names can be specified. The first policy that matches is applied. If multiple export commands are issued, the last command entered will override the previous command.

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, the policy only applies to the peer where it is configured.

The no form of the command removes all policies from the configuration and all SA entries are allowed.

Default

no export

Parameters
policy-name

specifies the export policy name. Up to five policy names can be specified.

group
Syntax

[no] group group-name

Context

config>router>msdp

Description

This command enables access to the context to create or modify an MSDP group. To configure multiple MSDP groups, multiple group statements must be included in the configuration.

By default, the group’s parameter settings are inherited from the global MSDP parameter settings. To override the global settings, group-specific settings within the group can be configured.

If the specified group name is already configured, this command enables the context to configure or modify group-specific parameters.

If the specified group name is not already configured, this command creates the group and enables the context to configure the group-specific parameters.

For a group to be functional, at least one peer must be configured.

Default

no group

Parameters
group-name

specifies a unique name for the MSDP group

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 the SA state from MSDP into the SA list.

If multiple policy names are specified, the policies are evaluated in the order they are specified. A maximum of five policy names can be specified. The first policy that matches is applied. If multiple import commands are issued, the last command entered will override the previous command.

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, the policy only applies to the peer where it is configured.

The no form of the command removes all policies from the configuration and all SA messages are allowed.

Default

no import

Parameters
policy-name

specifies the import policy name. Up to five policy names can be specified.

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 an MSDP session. For MSDP to function, at least one peer must be configured. When configuring a peer, you must include this local-address command. 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.

When the address is configured, it is validated and will be used as the local address for MSDP peers from that point. If a subsequent local-address command is entered, it will replace the existing configuration and existing sessions will be terminated.

Similarly, when the no form of this command is entered, the existing local-address will be removed from the configuration and the existing sessions will be terminated.

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

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

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

Default

no local-address

Parameters
address

specifies an existing address on the node

mode
Syntax

mode {mesh-group | standard}

Context

config>router>msdp>group

Description

This command configures groups of peers either in non-meshed mode or in a full mesh topology to limit excessive flooding of SA messages to neighboring peers. When the mode is specified as mesh-group, SA messages received from a mesh group member are always accepted but are not flooded to other members of the same mesh group. These SA messages are only flooded to non-mesh-group peers or members of other mesh groups

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, unpredictable results may occur.

Default

standard

Parameters
mesh-group

specifies that all members of the group have full mesh MSDP connectivity with each other

standard

specifies a non-meshed mode

peer
Syntax

[no] peer peer-address

Context

config>router>msdp

config>router>msdp>group

Description

This command configures an MSDP peer or MSDP group peer. MSDP must have at least one peer configured. A peer is defined by configuring a local-address that is used by the local node to set up a peering session and by configuring the address of a remote MSDP router. It is the address of this remote peer that is configured with this command.

After peer relationships are established, the MSDP peers exchange messages to advertise active multicast sources. If multiple peering sessions are required, multiple peer statements should be included in the configuration.

By default, the parameters applied to a peer are inherited from the global or group level. To override these inherited settings, the parameters must be configured at the peer level.

If the specified peer address is already a configured peer, this command enables the context to configure or modify the peer-specific parameters.

If the specified peer address is not already a configured peer, this command creates the peer instance and enables the context to configure the peer-specific parameters

The peer address is validated and, if valid, will be used as the remote address for an MSDP peering session.

When the no form of this command is entered, the existing peering address is removed from the configuration and the existing session is terminated. Whenever a session is terminated, all SA information pertaining to and learned from that peer is removed. Whenever a new peering session is created or a peering session is lost, an event message is generated.

Default

n/a

Parameters
peer-address

specifies the peer address that identifies the remote MSDP router with which the peering session will be established

authentication-key
Syntax

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

no authentication-key

Context

config>router>msdp>group>peer

config>router>msdp>peer

Description

This command configures a Message Digest 5 (MD5) authentication key to be used with a specific MSDP peering session. The authentication key must be configured per peer; therefore, no global or group configuration is possible.

Using the no form of the command accepts all MSDP messages and disables the MD5 signature option authentication key.

Default

no authentication-key

Parameters
authentication-key

specifies the authentication key. Allowed values are any string up to 256 characters long composed of printable, 7-bit ASCII characters. If the string contains special characters (such as #, $, or spaces), the entire string must be enclosed in quotation marks (‟ ”).

hash-key

specifies the hash key. The key can be any combination of ASCII characters up to 451 characters in length (encrypted). If spaces are used in the string, the entire string must be enclosed in quotation marks (‟ ”).

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

hash

specifies that the key is entered in an encrypted form. If the hash or hash2 parameter is not used, the key is assumed to be in an unencrypted, clear text form. For security, all keys are stored in encrypted form in the configuration file with the hash or hash2 parameter specified.

hash2

specifies that the key is entered in a more complex encrypted form that involves more variables than the key value alone, meaning that the hash2 encrypted variable cannot be copied and pasted. If the hash or hash2 parameter is not used, the key is assumed to be in an unencrypted, clear text form. For security, all keys are stored in encrypted form in the configuration file with the hash or hash2 parameter specified.

default-peer
Syntax

[no] default-peer

Context

config>router>msdp>peer

config>router>msdp>group>peer

Description

This command enables the default peer mechanism, where a peer can be selected as the default MSDP peer. As a result, all SA 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 SA messages from looping. A router validates SA messages originated from other routers in a deterministic fashion.

A set of rules is applied to validate received SA messages, and the first rule that applies determines the peer-RPF neighbor. All SA messages from other routers are rejected. The following rules are applied to SA messages originating at router_S and received at router_R from router_N.

  • If router_N and router_S are the same, the message is originated by a direct peer-RPF neighbor and is accepted.

  • If router_N is a configured peer or a member of the router_R mesh group, its SA messages are accepted.

  • If router_N is the BGP next hop of the active multicast RPF route toward router_S,then router_N is the peer-RPF neighbor and its SA 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 SA 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 SA messages are accepted.

  • If router_N fits none of the above rules, then router_N is not a peer-RPF neighbor and its SA messages are rejected.

When the no form the command is issued, no default peer is established and all SA messages are RPF checked.

Default

no default-peer

receive-msdp-msg-rate
Syntax

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

no receive-msdp-msg-rate

Context

config>router>msdp

config>router>msdp>group

config>router>msdp>group>peer

config>router>msdp>peer

Description

This command limits the number of MSDP messages that are read from the TCP session to prevent an MSDP RP router from receiving a large number of MSDP message packets in an SA message.

After the number of MSDP packets (including SA messages) defined by the threshold number have been processed, all other MSDP packets are rate-limited. Messages from the TCP session are no longer accepted until the configured interval seconds has elapsed. Setting the threshold is useful during at system startup and initialization. No limit is placed on the number of MSDP and SA messages that will be accepted

The no form of this command resets the message limit to its default operation.

Default

n/a

Parameters
receive-msdp-msg-rate number

specifies the number of MSDP messages (including SA messages) that are read from the TCP session per interval seconds

Values

10 to 10000

Default

0

seconds

specifies the interval of time in which the number of MSDP messages set by the receive-msdp-msg-rate number parameter are read from the TCP session

Values

1 to 600

Default

0

threshold number

specifies the number of MSDP messages that can be processed before the MSDP message rate-limiting function is activated

Values

1 to 1000000

Default

0

rpf-table
Syntax

rpf-table {rtable-m | rtable-u | both}

no rpf-table

Context

config>router>msdp

Description

This command configures the sequence of route tables used to find an RPF interface for a particular multicast route.

By default, only the unicast route table is looked up to calculate an RPF interface towards the source/rendezvous point. However, the operator can specify one of the following options:

  • use the unicast route table only

  • use the multicast route table only

  • use both route tables

Default

rtable-u

Parameters
rtable-m

specifies that only the multicast route table is used by the multicast protocol (PIM) for IPv4 RPF checks. This route table contains routes submitted by static routes, ISIS, and OSPF.

rtable-u

specifies that only the unicast route table is used by the multicast protocol (PIM) for IPv4 RPF checks. This route table contains routes submitted by all unicast routing protocols.

both

specifies that the first lookup is always in the multicast route table, and if there is a route, it will use it. If PIM does not find a route in the first lookup, it tries to find it in the unicast route table.

sa-timeout
Syntax

sa-timeout seconds

no sa-timeout

Context

config>router>msdp

Description

This command configures the timeout value for the SA entries in the cache. If these entries are not refreshed within the timeout value, they are removed from the cache. Normally, the entries are refreshed at least once a minute. However, under high load with many MSDP peers, the refresh cycle could be incomplete. A higher timeout value (more than 90 seconds) could be useful to prevent instabilities in the MSDP cache.

Default

90

Parameters
seconds

specifies the time, in seconds, to wait for a response from the peer before declaring the peer unavailable

Values

90 to 600

source
Syntax

[no] source ip-prefix/mask

Context

config>router>msdp

Description

This command configures an MSDP source.

If the specified prefix and mask is already configured, this command enables the context to configure or modify the source-specific parameters.

If the specified prefix and mask is not already configured, this command creates the source node instance and enables the context to configure the source-specific parameters.

The SA messages are not rate-limited based on the source address range.

The no form of this command removes the sources in the address range.

Default

n/a

Parameters
ip-prefix

specifies the IP prefix, in dotted-decimal notation, for the MSDP source

Values

a.b.c.d (host bits must be 0)

mask

specifies the subnet mask for the range, expressed as a decimal integer mask length or in dotted-decimal notation

Values

0 to 32 (mask length)

0.0.0.0 to 255.255.255.255 (dotted-decimal)

Show Commands

Note: The following command outputs are examples only; actual displays may differ depending on supported functionality and user configuration.
igmp
Syntax

igmp

Context

show>router

Description

This command enables the context to display IGMP information.

group
Syntax

group [grp-ip-address]

group summary

Context

show>router>igmp

Description

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.

Parameters
grp-ip-address

displays specific multicast group addresses

Output

The following output is an example of IGMP group information, and IGMP Group Field Descriptions describes the fields.

Output Example 
*B:Dut-C# show router igmp group 
===============================================================================
IGMP Interface Groups
===============================================================================
===============================================================================
IGMP Host Groups
===============================================================================
(*,239.255.0.1)
    Fwd List  : 239.255.1.2            Up Time : 0d 00:00:21
(10.11.0.1,239.255.0.1)
    Fwd List  : 239.255.1.1            Up Time : 0d 00:00:30
    Blk List  : 239.255.1.20           Up Time : 0d 00:00:21
(10.11.0.2,239.255.0.100)
    Fwd List  : 239.255.1.30           Up Time : 0d 00:00:30
(*,239.255.0.200)
    Fwd List  : 239.255.1.40           Up Time : 0d 00:00:21
(10.11.0.3,239.255.0.210)
    Blk List  : 239.255.1.50           Up Time : 0d 00:00:21
-------------------------------------------------------------------------------
(*,G)/(S,G) Entries : 5
===============================================================================
*B:Dut-C# 


*B:Dut-C# show router igmp group summary 
===============================================================================
IGMP Interface Groups
===============================================================================
===============================================================================
IGMP Host Groups Summary          Nbr Fwd Hosts          Nbr Blk Hosts
===============================================================================
(*,239.255.0.1)                   1                      0
(10.11.0.1,239.255.0.1)           1                      1
(10.11.0.2,239.255.0.100)         1                      0
(*,239.255.0.2)                   1                      0
(10.11.0.3,239.0.0.200)           0                      1
-------------------------------------------------------------------------------
(*,G)/(S,G) Entries : 5
===============================================================================
*B:Dut-C# 
Table 5. IGMP Group Field Descriptions

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

interface
Syntax

interface [ip-int-name | ip-address] [group] [grp-ip-address] [detail]

Context

show>router>igmp

Description

This command displays IGMP interface information.

Parameters
ip-int-name

displays only the information associated with the specified IP interface name

ip-address

displays only the information associated with the specified IP address

grp-ip-address

displays only the IP multicast group address for which this entry contains information

detail

displays detailed IP interface information along with the source group information learned on that interface

Output

The following output is an example of IGMP interface information, and IGMP Interface Field Descriptions describes the fields.

Output Example 
*A:ALU-BA# show router 100 interface
===============================================================================
Interface Table (Service: 100)
===============================================================================
Interface-Name           Adm          Opr(v4/v6)     Mode      Port/SapId
   IP-Address                                                  PfxState
-------------------------------------------------------------------------------
IGMP_to_CE               Up           Up             VPRN      1/1/7
   10.1.1.1/24 n/a
system                   Up           Up             VPRN      loopback
   10.20.1.2/32 n/a
-------------------------------------------------------------------------------
Interfaces : 2
===============================================================================
*A:ALU-BA#

*A:ALU-BA# show router 100 interface IGMP_to_CE
===============================================================================
Interface Table (Service: 100)
===============================================================================
Interface-Name           Adm          Opr(v4/v6)     Mode      Port/SapId
   IP-Address                                                  PfxState
-------------------------------------------------------------------------------
IGMP_to_CE               Up           Up             VPRN      1/1/7
   10.1.1.1/24                                                 n/a
-------------------------------------------------------------------------------
Interfaces : 1
===============================================================================
*A:ALU-BA#

*A:ALU-BA# show router 100 igmp interface 
===============================================================================
IGMP Interfaces
===============================================================================
Interface       Adm       Oper     Querier     Cfg/Opr   Num      Policy 
                                               Version   Groups 
-------------------------------------------------------------------------------
IGMP_to_CE      Up        Up       10.1.1.1    1/1        3       igmppol 
-------------------------------------------------------------------------------
Interfaces : 1
===============================================================================
*A:ALU-BA#

*A:ALU-BA# show router 100 igmp interface IGMP_to_CE
===============================================================================
IGMP Interface IGMP_to_CE
===============================================================================
Interface       Adm       Oper     Querier     Cfg/Opr   Num      Policy 
                                               Version   Groups 
-------------------------------------------------------------------------------
IGMP_to_CE      Up        Up       10.1.1.1    1/1        3       igmppol 
-------------------------------------------------------------------------------
Interfaces : 1
===============================================================================
*A:ALU-BA#

*A:ALU-BA# show router 100 igmp interface 10.1.1.1 
===============================================================================
IGMP Interface 10.1.1.1
===============================================================================
Interface       Adm       Oper     Querier     Cfg/Opr   Num      Policy 
                                               Version   Groups 
-------------------------------------------------------------------------------
IGMP_to_CE      Up        Up       10.1.1.1    1/1        3       igmppol 
-------------------------------------------------------------------------------
Interfaces : 1
===============================================================================
*A:ALU-BA#

*A:ALU-BA# show router 100 igmp interface IGMP_to_CE group 239.255.1.1 
===============================================================================
IGMP Interface IGMP_to_CE
===============================================================================
Interface       Adm       Oper     Querier     Cfg/Opr   Num      Policy 
                                               Version   Groups 
-------------------------------------------------------------------------------
IGMP_to_CE      Up        Up       10.1.1.1    1/1        3       igmppol 
-------------------------------------------------------------------------------
IGMP Group
-------------------------------------------------------------------------------
Group Address : 239.255.1.1            Up Time      : 0d 00:03:52 
Interface     : IGMP_to_CE             Expires      : never 
Last Reporter : 0.0.0.0                Mode         : exclude 
V1 Host Timer : Not running            Type         : static 
V2 Host Timer : Not running            Compat Mode  : IGMP Version 3 
-------------------------------------------------------------------------------
Interfaces : 1
===============================================================================
*A:ALU-BA#

*A:ALU-BA# show router 100 igmp interface IGMP_to_CE group 239.255.1.1 detail 
===============================================================================
IGMP Interface IGMP_to_CE
===============================================================================
Interface           : IGMP_to_CE 
Admin Status        : Up                Oper Status         : Up 
Querier             : 10.1.1.1          Querier Up Time     : 0d 00:04:01 
Querier Expiry Time : N/A               Time for next query : 0d 00:13:42 
Admin/Oper version  : 1/1               Num Groups          : 3 
Policy              : igmppol           Subnet Check        : Disabled 
Max Groups Allowed  : 16000             Max Groups Till Now : 3 
MCAC Policy Name    : MCAC              Const Adm St        : Enable 
MCAC Max Unconst BW : no limit          MCAC Max Mand BW    : no limit 
MCAC In use Mand BW : 0                 MCAC Avail Mand BW  : unlimited 
MCAC In use Opnl BW : 0                 MCAC Avail Opnl BW  : unlimited 
-------------------------------------------------------------------------------
IGMP Group
-------------------------------------------------------------------------------
Group Address       : 239.255.1.1       Up Time             : 0d 00:04:02 
Interface           : IGMP_to_CE        Expires             : never 
Last Reporter       : 0.0.0.0           Mode                : exclude 
V1 Host Timer       : Not running       Type                : static 
V2 Host Timer       : Not running       Compat Mode         : IGMP Version 3 
-------------------------------------------------------------------------------
Table 6. IGMP Interface Field Descriptions

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 reports 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.
ssm-translate
Syntax

ssm-translate [interface-name]

Context

show>router>igmp

Description

This command displays IGMP SSM translate configuration information.

Parameters
interface-name

displays the information associated with the specified IP interface name (the interface name can have up to 32 characters and must start with a letter)

Output

The following output is an example of IGMP ssm-translate configuration information, and IGMP SSM-Translate Field Descriptions describes the fields.

Output Example 
*A:7705custDoc:Sar18>show>router>igmp# ssm-translate
===============================================================================
IGMP SSM Translate Entries
===============================================================================
Group Range                        Source           Interface
-------------------------------------------------------------------------------
<239.255.10.0 - 239.255.10.10>     10.10.10.10      igmp_interface
-------------------------------------------------------------------------------
SSM Translate Entries : 1
===============================================================================
*A:7705custDoc:Sar18>show>router>igmp#
Table 7. IGMP SSM-Translate Field Descriptions

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
static
Syntax

static [ip-int-name | ip-address]

Context

show>router>igmp

Description

This command displays static IGMP, (*,G), and (S,G) information.

Parameters
ip-int-name

displays the information associated with the specified IP interface name

ip-address

displays the information associated with the specified IP address in the format a.b.c.d

Output

The following output is an example of static IGMP information, and Static IGMP Field Descriptions describes the fields.

Output Example 
*A:7705custDoc:Sar18>show>router>igmp# static
==================================================================
IGMP Static Group Source
==================================================================
Source           Group            Interface
------------------------------------------------------------------
10.11.11.11      239.255.22.3     IGMP_to_CE                      
------------------------------------------------------------------
Static (*,G)/(S,G) Entries : 1
==================================================================
Table 8. Static IGMP Field Descriptions

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

statistics
Syntax

statistics [ip-int-name | ip-address]

Context

show>router>igmp

Description

This command displays IGMP statistics information.

Parameters
ip-int-name

displays the information associated with the specified IP interface name

ip-address

displays the information associated with the specified IP address

Output

The following output is an example of IGMP statistic information, and IGMP Statistics Field Descriptions describes the fields.

Output Example 
*A:ALU-BA# show router igmp statistics
=================================================
IGMP Interface Statistics
=================================================
Message Type        Received     Transmitted 
--------------------------------------------------
Queries             0            5 
Report V1           0            0 
Report V2           0            0 
Report V3           10           0 
Leaves              0            0 
-------------------------------------------------
General Interface Statistics
-------------------------------------------------
Bad Length        : 0
Bad Checksum      : 0
Unknown Type      : 0
Bad Receive If    : 0
Rx Non Local      : 0
Rx Wrong Version  : 0
Policy Drops      : 0
No Router Alert   : 0
Rx Bad Encodings  : 0
Local Scope Pkts  : 0
Resvd Scope Pkts  : 0
-------------------------------------------------
Source Group Statistics
-------------------------------------------------
(S,G)             : 2
(*,G)             : 1
=================================================
*A:ALU-BA#
Table 9. IGMP Statistics Field Descriptions

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
status
Syntax

status

Context

show>router>igmp

Description

This command displays IGMP status information. If IGMP is not enabled, the following message appears:

A:NYC# show router igmp status
MINOR: CLI IGMP is not configured.
A:NYC#
Output

The following output is an example of IGMP status information, and IGMP Status Field Descriptions describes the fields.

Output Example 
*A:ALU-BA# show router 100 igmp status 
===============================================================================
IGMP Status
===============================================================================
Admin State                                : Up 
Oper State                                 : Up 
Query Interval                             : 1024 
Last Member Query Interval                 : 1024 
Query Response Interval                    : 1023 
Robust Count                               : 10 
===============================================================================
*A:ALU-BA#
Table 10. IGMP Status Field Descriptions

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
mld
Syntax

mld

Context

show>router

Description

This command enables the context to display MLD information.

group
Syntax

group [grp-ipv6-address]

Context

show>router>mld

Description

This command displays MLD group information.

Parameters
grp-ipv6-address

the IPv6 group address

Output

The following output is an example of MLD group information, and MLD Group Field Descriptions describes the fields.

Output Example 
*A:ALU# show router mld group 
===============================================================================
MLD Groups
===============================================================================
(3FFE:100::2:100,FF05::1:1) 
    Up Time    : 0d 00:00:31 
    Fwd List   : Host1 

(3FFE:100::2:100,FF05::1:2) 
    Up Time    : 0d 00:00:31 
    Fwd List   : Host1 

(3FFE:100::2:100,FF05::1:3) 
    Up Time    : 0d 00:00:31 
    Fwd List   : Host1 

(3FFE:100::2:100,FF05::1:4) 
    Up Time    : 0d 00:00:31 
    Fwd List   : Host1 

(3FFE:100::2:100,FF05::1:5)
===============================================================================
*A:ALU#

*A:ALU# show router mld group ff05::1:1 
===============================================================================
MLD Groups
===============================================================================
(3FFE:100::2:100,FF05::1:1) 
    Up Time    : 0d 00:00:40 
    Fwd List   : Host1 
-------------------------------------------------------------------------------
(*,G)/(S,G) Entries : 1
===============================================================================
*A:ALU#
Table 11. MLD Group Field Descriptions

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

interface
Syntax

interface [ip-int-name | ip-address] [group] [grp-ipv6-address] [detail]

Context

show>router>mld

Description

This command displays MLD interface information.

Parameters
ip-int-name

the IP interface name

ip-address

the IPv6 interface address (x:x:x:x:x:x:x:x)

grp-ipv6-address

the IPv6 multicast group address

detail

displays detailed information

Output

The following output is an example of MLD interface information, and MLD Interface Field Descriptions describes the fields.

Output Example 
*A:7705custDoc:Sar18>show>router>mld# interface mld_interface
===============================================================================
MLD Interface mld_interface
===============================================================================
Interface               Adm  Oper Cfg/Opr         Num             Policy
   Querier                        Version         Groups
-------------------------------------------------------------------------------
mld_interface           Up   Down 2/2             0               none
   ::
-------------------------------------------------------------------------------
Interfaces : 1
===============================================================================
*A:7705custDoc:Sar18>config>router>mld>if#

*A:7705custDoc:Sar18>show>router>mld# interface mld_interface detail
===============================================================================
MLD Interface mld_interface
===============================================================================
Interface              : mld_interface
Admin Status           : Up               Oper Status        : Down
Querier                : ::
Querier Up Time        : 0d 00:00:00
Querier Expiry Time    : N/A
Admin/Oper version     : 2/2              Num Groups         : 0
Policy                 : none
Max Groups Allowed     : No Limit         Max Groups Till Now: 0
Query Interval         : 0                Query Resp Interval: 0
Last List Qry Interval : 0                Router Alert Check : Enabled
-------------------------------------------------------------------------------
Interfaces : 1
===============================================================================

*A:ALU# show router mld interface 
===============================================================================
MLD Interfaces
===============================================================================
Interface                Adm     Oper    Cfg/Opr      Num        Policy 
   Querier                               Version      Groups 
-------------------------------------------------------------------------------
Host4_Srce1_IPv6         Up      Up        2/2         0          none 
   FE80::216:4DFF:FED4:4D5B
Host1                    Up      Up        2/2         0          none 
   FE80::216:4DFF:FED4:4D5B
Host2                    Up      Up        2/2         0          none 
   FE80::216:4DFF:FE51:3728
Host3_vlan1              Up      Up        2/2         0          none 
   FE80::216:4DFF:FE51:3729
Host3_vlan2              Up      Up        2/2         0          none 
   FE80::216:4DFF:FE51:3729
Host3_vlan3              Up      Up        2/2         0          none 
   FE80::216:4DFF:FE51:3729
Host3_vlan4              Up      Up        2/2         0          none 
   FE80::216:4DFF:FE51:3729
Host3_vlan5              Up      Up        2/2         0          none 
*A:ALU 

*A:ALU# show router mld interface Host1 detail 
===============================================================================
MLD Interface Host1
===============================================================================
Interface              : Host1 
Admin Status           : Up               Oper Status        : Up 
Querier                : FE80::216:4DFF:FED4:4D5B
Querier Up Time        : 0d 00:02:18 
Querier Expiry Time    : N/A              Time for next query: 0d 00:15:25 
Admin/Oper version     : 2/2              Num Groups         : 6000 
Policy                 : none 
Max Groups Allowed     : No Limit         Max Groups Till Now: 6000 
Query Interval         : 0                Query Resp Interval: 0 
Last List Qry Interval : 0                Router Alert Check : Enabled
-------------------------------------------------------------------------------
MLD Group
-------------------------------------------------------------------------------
Group Address          : FF05::1:1
Last Reporter          : FE80::1
Interface              : Host1            Expires : N/A
Up Time                : 0d 00:00:10      Mode : include
V1 Host Timer          : Not running      Type : dynamic
Compat Mode            : MLD Version 2
-------------------------------------------------------------------------------
Source
Expires                Type               Fwd/Blk
-------------------------------------------------------------------------------
3FFE:100::2:100
0d 00:34:07            dynamic            Fwd
-------------------------------------------------------------------------------
MLD Group
-------------------------------------------------------------------------------
Group Address         : FF05::1:2
Last Reporter         : FE80::1
Interface             : Host1            Expires           : N/A
Up Time               : 0d 00:00:11      Mode              : include
V1 Host Timer         : Not running      Type              : dynamic
Compat Mode           : MLD Version 2
-------------------------------------------------------------------------------
Source
Expires                Type               Fwd/Blk
-------------------------------------------------------------------------------
3FFE:100::2:100
0d 00:34:07            dynamic            Fwd
-------------------------------------------------------------------------------
MLD Group
-------------------------------------------------------------------------------
Group Address         : FF05::1:3
Last Reporter         : FE80::1
Interface             : Host1           Expires          : N/A
Up Time               : 0d 00:00:11     Mode             : include
V1 Host Timer         : Not running     Type             : dynamic
Compat Mode           : MLD Version 2
-------------------------------------------------------------------------------
Source
Expires                Type               Fwd/Blk
-------------------------------------------------------------------------------
3FFE:100::2:100
0d 00:34:07            dynamic            Fwd
-------------------------------------------------------------------------------
MLD Group
-------------------------------------------------------------------------------
Group Address         : FF05::1:4
Last Reporter         : FE80::1
Interface             : Host1             Expires         : N/A
Up Time               : 0d 00:00:12       Mode            : include
V1 Host Timer         : Not running       Type            : dynamic
Compat Mode           : MLD Version 2
-------------------------------------------------------------------------------
Source
Expires                Type               Fwd/Blk
-------------------------------------------------------------------------------
3FFE:100::2:100
0d 00:34:06            dynamic            Fwd
-------------------------------------------------------------------------------
MLD Group
-------------------------------------------------------------------------------
Group Address         : FF05::1:5
Last Reporter         : FE80::1
Interface             : Host1             Expires         : N/A
Up Time               : 0d 00:00:12       Mode            : include
V1 Host Timer         : Not running       Type            : dynamic
Compat Mode           : MLD Version 2
-------------------------------------------------------------------------------
Source
Expires                Type               Fwd/Blk
-------------------------------------------------------------------------------
3FFE:100::2:100
0d 00:34:06            dynamic            Fwd
-------------------------------------------------------------------------------
*A:ALU# show router mld interface Host1 detail 
Table 12. MLD Interface Field Descriptions

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 reports 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
ssm-translate
Syntax

ssm-translate [interface-name]

Context

show>router>mld

Description

This command displays the MLD SSM translate configuration.

Parameters
interface-name

displays the information associated with the specified IP interface name (the interface name can have up to 32 characters and must start with a letter)

Output

The following output is an example of MLD ssm-translate information, and MLD SSM-Translate Field Descriptions describes the fields.

Output Example 
*A:7705custDoc:Sar18>show>router>mld# ssm-translate mld_interface
===============================================================================
MLD SSM Translate Entries
===============================================================================
Group Range                        Source           Interface
-------------------------------------------------------------------------------
<239.255.10.0 - 239.255.10.10>     10.10.10.10      mld_interface
-------------------------------------------------------------------------------
SSM Translate Entries : 1
===============================================================================
*A:7705custDoc:Sar18>show>router>mld#
Table 13. MLD SSM-Translate Field Descriptions

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
static
Syntax

static [ip-int-name | ip-address]

Context

show>router>mld

Description

This command displays MLD static group and source configuration.

Parameters
ip-int-name

the IP interface name

ip-address

the IPv6 interface address in the format x:x:x:x:x:x:x:x

Output

The following output is an example of MLD static group and source configuration information, and MLD Static Group Field Descriptions describes the fields.

Output Example 
*A:7705custDoc:Sar18# show router mld static 
===============================================================================
MLD Static Group Source
===============================================================================
Source                                  Group                                  
    Interface
-------------------------------------------------------------------------------
No Matching Entries
===============================================================================
*A:7705custDoc:Sar18#
Table 14. MLD Static Group Field Descriptions

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

statistics
Syntax

statistics [ip-int-name | ipv6-address]

Context

show>router>mld

Description

This command displays MLD statistics.

Parameters
ip-int-name

displays the information associated with the specified IP interface name

ipv6-address

displays the information associated with the specified IPv6 address in the format x:x:x:x:x:x:x:x

Output

The following output is an example of MLD statistics information, and MLD Statistics Field Descriptions describes the fields.

Output Example 
*A:7705custDoc:Sar18>show>router>mld# statistics
=================================================
MLD Interface Statistics
=================================================
Message Type        Received       Transmitted
-------------------------------------------------
Queries             0              0
Report V1           0              0
Report V2           0              0
Dones               0              0
-------------------------------------------------------------------------------
General Interface Statistics
-------------------------------------------------------------------------------
Bad Length        : 0
Bad Checksum      : 0
Unknown Type      : 0
Bad Receive If    : 0
Rx Non Local      : 0
Rx Wrong Version  : 0
Policy Drops      : 0
No Router Alert   : 0
Rx Bad Encodings  : 0
Rx Pkt Drops      : 0
Local Scope Pkts  : 0
Resvd Scope Pkts  : 0
-------------------------------------------------------------------------------
Source Group Statistics
-------------------------------------------------------------------------------
(S,G)             : 0
(*,G)             : 0
=================================================
*A:7705custDoc:Sar18>show>router>mld#
Table 15. MLD Statistics Field Descriptions

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

status
Syntax

status

Context

show>router>mld

Description

This command displays the MLD status.

Output

The following output is an example of MLD status information, and MLD Status Field Descriptions describes the fields.

Output Example 
*A:7705Sar18>show>router>mld# status
===============================================================================
MLD Status
===============================================================================
Admin State                       : Up
Oper State                        : Up
Query Interval                    : 125
Last Listener Query Interval      : 1
Query Response Interval           : 10
Robust Count                      : 2
===============================================================================
*A:7705Sar18>show>router>mld#
Table 16. MLD Status Field Descriptions

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
pim
Syntax

pim

Context

show>router

Description

This command enables the context to display PIM information.

group
Syntax

group [grp-ip-address] [source ip-address] [detail] [family]

Context

show>router>pim

Description

This command displays PIM source group database information.

Parameters
grp-ip-address

the IP multicast group address for which this entry contains information

ip-address

the source address for which this entry contains information

detail

displays detailed group information

family

displays either IPv4 or IPv6 information

Values

ipv4 or ipv6

Output

The following output is an example of PIM group information, and PIM Group Field Descriptions describes the fields.

Output Example 
*A:7CSA:Dut-C# show router pim group 
===============================================================================
PIM Groups ipv4
===============================================================================
Group Address                           Type     Spt Bit Inc Intf       No.Oifs
   Source Address                          RP 
-------------------------------------------------------------------------------
239.255.0.0                             (S,G)            ip-10.1.7.7    16 
   10.111.1.2 
239.255.0.1                             (S,G)            ip-10.1.7.7    16 
   10.111.1.2 
239.255.0.2                             (S,G)            ip-10.1.7.7    16 
   10.111.1.2 
239.255.0.3                             (S,G)            ip-10.1.7.7    16 
   10.111.1.2 
239.255.0.4                             (S,G)            ip-10.1.7.7    16 
   10.111.1.2 
-------------------------------------------------------------------------------
Groups : 5
===============================================================================

*A:7CSA:Dut-C# show router pim group 239.255.0.0 
===============================================================================
PIM Groups ipv4
===============================================================================
Group Address                           Type     Spt Bit Inc Intf       No.Oifs
   Source Address                          RP 
-------------------------------------------------------------------------------
239.255.0.0                             (S,G)            ip-10.1.7.7    16     
   10.11.1.2                             
-------------------------------------------------------------------------------
Groups : 1
===============================================================================

*A:7CSA:Dut-C# show router pim group 239.255.0.0 detail 
===============================================================================
PIM Source Group ipv4
===============================================================================
Group Address      : 239.255.0.0
Source Address     : 10.111.1.2
RP Address         : 0
Flags              :                    Type               : (S,G)
MRIB Next Hop      : 10.1.7.1
MRIB Src Flags     : remote             Keepalive Timer    : Not Running
Up Time            : 0d 00:27:25        Resolved By        : rtable-u
Up JP State        : Joined             Up JP Expiry       : 0d 00:00:35
Up JP Rpt          : Not Joined StarG   Up JP Rpt Override : 0d 00:00:00
Register State     : No Info                                              
Reg From Anycast RP: No                 
 
Rpf Neighbor       : 10.1.7.1
Incoming Intf      : ip-10.1.7.7
Outgoing Intf List : ip-10.112.1.1, ip-10.112.2.1, ip-10.112.3.1
                     ip-10.112.4.1, ip-10.112.5.1, ip-10.112.6.1
                     ip-10.112.7.1, ip-10.112.8.1, ip-10.112.9.1
                     ip-10.112.10.1, ip-10.112.11.1, ip-10.112.12.1
                     ip-10.112.13.1, ip-10.112.14.1, ip-10.112.15.1
                     ip-10.112.16.1
Curr Fwding Rate   : 0.0 kbps           
Forwarded Packets  : 0                  Discarded Packets  : 0
Forwarded Octets   : 0                  RPF Mismatches     : 0
-------------------------------------------------------------------------------
Groups : 1
===============================================================================
Table 17. PIM Group Field Descriptions

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

interface
Syntax

interface [ip-int-name | mt-int-name | int-ip-address] [group grp-ip-address] [source ip-address] [detail] [family]

Context

show>router>pim

Description

This command displays PIM interface information and the (S,G) state of the interface.

Parameters
ip-int-name

displays the interface information associated with the specified IP interface name

mt-int-name

displays information on the multicast tunnel (MT) interface for a VPRN

Values

vprn-id-mt-grp-ip-address

ip-address

displays the interface information associated with the specified IP address

grp-ip-address

the IP multicast group address for which this entry contains information

source ip-address

specifies the source address for which this entry contains information

detail

displays detailed interface information

family

displays IPv4 or IPv6 information for the interface

Values

ipv4 or ipv6

Output

The following output is an example of PIM interface information, and PIM Interface Field Descriptions describes the fields.

Output Example 
*A:7705:Dut-A# show router pim interface    
==================================================================
PIM Interfaces ipv4
==================================================================
Interface                   Adm  Opr  DR Prty         Hello Intvl              
   DR                                                                          
------------------------------------------------------------------
ip-10.1.7.1                 Up   Up   1               30          
   10.1.7.7
ip-10.111.1.1              Up   Up   1               30          
   10.111.1.1
------------------------------------------------------------------
Interfaces : 2
==================================================================

*A:7705:Dut-A# show router pim interface detail  
===============================================================================
PIM Interface ipv4 ip-10.1.7.1
===============================================================================
Admin Status       : Up                 Oper Status        : Up
IPv4 Admin Status  : Up                 IPv4 Oper Status   : Up
DR                 : 10.1.7.7
Oper DR Priority   : 1                  
BSM RA Check       : Disabled           Cfg DR Priority    : 1
Hello Interval     : 30                 Time for next hello: 0d 00:00:16
Hello Multiplier   : 35                 
J/P Tracking Admin : Disabled           J/P Tracking Oper  : Disabled
Auto-created       : No                 Improved Assert    : Enabled
Sticky-DR          : Disabled           Sticky-DR Priority : N/A
Max Groups Allowed : 0                  Max Groups Till Now: 5
Num Groups         : 5                  Bfd enabled        : No
Three-way Hello    : Disabled           Assert-Period      : 60
Instant Prune Echo : Disabled           
-------------------------------------------------------------------------------
PIM Group Source
-------------------------------------------------------------------------------
Group Address      : 239.255.0.0        
Source Address     : 10.111.1.2
Interface          : ip-10.1.7.1        Type               : (S,G)
RP Address         : 10.0.0.0            
Up Time            : 0d 00:01:09        
 
Join Prune State   : Join               Expires            : 0d 00:03:21
Prune Pend Expires : N/A                
 
Assert State       : No Info            
-------------------------------------------------------------------------------
PIM Group Source
-------------------------------------------------------------------------------
Group Address      : 239.255.0.1
Source Address     : 10.111.1.2
Interface          : ip-10.1.7.1        Type               : (S,G)
RP Address         : 10.0.0.0            
Up Time            : 0d 00:01:10        
 
Join Prune State   : Join               Expires            : 0d 00:03:20
Prune Pend Expires : N/A                
 
Assert State       : No Info            
-------------------------------------------------------------------------------
PIM Group Source
-------------------------------------------------------------------------------
Group Address      : 239.255.0.2
Source Address     : 10.111.1.2
Interface          : ip-10.1.7.1        Type               : (S,G)
RP Address         : 10.0.0.0            
Up Time            : 0d 00:01:11        
 
Join Prune State   : Join               Expires            : 0d 00:03:19
Prune Pend Expires : N/A                
 
Assert State       : No Info            
-------------------------------------------------------------------------------
PIM Group Source
-------------------------------------------------------------------------------
Group Address      : 239.255.0.3
Source Address     : 10.111.1.2
Interface          : ip-10.1.7.1        Type               : (S,G)
RP Address         : 10.0.0.0            
Up Time            : 0d 00:01:11        
                                      
Join Prune State   : Join               Expires            : 0d 00:03:19
Prune Pend Expires : N/A                
 
Assert State       : No Info            
-------------------------------------------------------------------------------
PIM Group Source
-------------------------------------------------------------------------------
Group Address      : 239.255.0.4
Source Address     : 10.111.1.2
Interface          : ip-10.1.7.1        Type               : (S,G)
RP Address         : 10.0.0.0            
Up Time            : 0d 00:01:11        
 
Join Prune State   : Join               Expires            : 0d 00:03:18
Prune Pend Expires : N/A                
 
Assert State       : No Info            
===============================================================================
PIM Interface ipv4 ip-10.111.1.1
===============================================================================
Admin Status       : Up                 Oper Status        : Up
IPv4 Admin Status  : Up                 IPv4 Oper Status   : Up
DR                 : 10.111.1.1
Oper DR Priority   : 1                  
BSM RA Check       : Disabled           Cfg DR Priority    : 1
Hello Interval     : 30                 Time for next hello: 0d 00:00:29
Hello Multiplier   : 35                 
J/P Tracking Admin : Disabled           J/P Tracking Oper  : Disabled
Auto-created       : No                 Improved Assert    : Enabled
Sticky-DR          : Disabled           Sticky-DR Priority : N/A
Max Groups Allowed : 0                  Max Groups Till Now: 0
Num Groups         : 0                  Bfd enabled        : No
Three-way Hello    : Disabled           Assert-Period      : 60
Instant Prune Echo : Disabled           
-------------------------------------------------------------------------------
Interfaces : 2
===============================================================================

*A:7705:Dut-A# show router pim interface group 
==================================================================
PIM Interface ipv4 ip-10.1.7.1
==================================================================
Interface                   Adm  Opr  DR Prty         Hello Intvl              
   DR                                                                          
------------------------------------------------------------------
ip-10.1.7.1                 Up   Up   1               30          
   10.1.7.7
-------------------------------------------------------------------------------
Group Address                                Type     JP            Assert    
   Source Address                                                             
   RP Address                                                                 
-------------------------------------------------------------------------------
239.255.0.0                                  (S,G)    Join          No Info    
   10.111.1.2
   
239.255.0.1                                  (S,G)    Join          No Info    
   10.111.1.2
   
239.255.0.2                                  (S,G)    Join          No Info    
   10.111.1.2
   
239.255.0.3                                  (S,G)    Join          No Info    
   10.111.1.2
   
239.255.0.4                                  (S,G)    Join          No Info    
   10.111.1.2
------------------------------------------------------------------
Interfaces : 1
==================================================================

*A:7705:Dut-A# show router pim interface group 239.255.0.0 detail 
==================================================================
PIM Interface ipv4 ip-10.1.7.1
==================================================================
Interface                   Adm  Opr  DR Prty         Hello Intvl              
   DR                                                                          
------------------------------------------------------------------
ip-10.1.7.1                 Up   Up   1               30          
   10.1.7.7
-------------------------------------------------------------------------------
PIM Group Source
-------------------------------------------------------------------------------
Group Address      : 239.255.0.0
Source Address     : 10.111.1.2
Interface          : ip-10.1.7.1        Type               : (S,G)
RP Address         : 10.0.0.0            
Up Time            : 0d 00:11:09        
 
Join Prune State   : Join               Expires            : 0d 00:03:21
Prune Pend Expires : N/A                
 
Assert State       : No Info            
------------------------------------------------------------------
Interfaces : 1
==================================================================
Table 18. PIM Interface Field Descriptions

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

multicast-translation type
Syntax

multicast-translation type {unicast-to-multicast | multicast-to-multicast}

Context

show>router>pim>interface

Description

This command displays the translated addresses for either unicast-to-multicast translation or multicast-to-multicast translation.

neighbor
Syntax

neighbor [ip-int-name | ip-address [address neighbor-ip-address]] [detail] [family]

Context

show>router>pim

Description

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.

Parameters
ip-int-name

displays the interface information associated with the specified IP interface name

ip-address

displays the interface information associated with the specified IP address (IPv4 or IPv6)

neighbor-ip-address

the IP address of the PIM neighbor on the other side of the interface (IPv4 or IPv6)

detail

displays detailed interface information

family

displays IPv4 or IPv6 information for the interface

Values

ipv4 or ipv6

Output

The following output is an example of PIM neighbor information, and PIM Neighbor Field Descriptions describes the fields.

Output Example 
*A:7705custDoc:Sar18>show>router>pim# neighbor
===============================================================================
PIM Neighbor ipv4
===============================================================================
Interface               Nbr DR Prty     Up Time       Expiry Time     Hold Time
   Nbr Address
-------------------------------------------------------------------------------
ip-10.1.7.7             1               0d 00:29:49   0d 00:01:28     105      
   10.1.7.1
ip-10.112.1.1          0               0d 00:28:44   0d 00:00:05     5        
   10.112.1.2
ip-10.112.2.1          0               0d 00:28:44   0d 00:00:05     5        
   10.112.2.2
ip-10.112.3.1          0               0d 00:28:43   0d 00:00:04     5        
   10.112.3.2
ip-10.112.4.1          0               0d 00:28:43   0d 00:00:03     5        
   10.112.4.2
-------------------------------------------------------------------------------
Neighbors : 5
===============================================================================
*A:7705custDoc:Sar18>show>router>pim# neighbor

*A:7CSA:Dut-C# show router pim neighbor ip-10.1.7.7 
===============================================================================
PIM Neighbor ipv4
===============================================================================
Interface               Nbr DR Prty     Up Time       Expiry Time     Hold Time
   Nbr Address                                                                 
-------------------------------------------------------------------------------
ip-10.1.7.7             1               0d 00:58:15   0d 00:01:31     105      
   10.1.7.1
-------------------------------------------------------------------------------
Neighbors : 1
===============================================================================

*A:7CSA:Dut-C# show router pim neighbor ip-10.1.7.7 detail        
===============================================================================
PIM Neighbor ipv4
===============================================================================
Interface          : ip-10.1.7.7
Neighbor Addr      : 10.1.7.1
DR Priority        : 1                  
Tracking Support   : No                 LAN Delay(ms)      : 500
Gen Id             : 60143787           Override Intvl(ms) : 2500
Up Time            : 0d 01:00:13        Expiry Time        : 0d 00:01:34
Hold Time(sec)     : 105                
 
-------------------------------------------------------------------------------
Secondary Neighbor Addresses
-------------------------------------------------------------------------------
-------------------------------------------------------------------------------
Neighbors : 1
Table 19. PIM Neighbor Field Descriptions

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
rp
Syntax

rp [family | ip-address]

Context

show>router>pim

Description

This command displays RP information that is learned through PIM bootstrap or configured statically.

Parameters
family

displays either IPv4 or IPv6 information

Values

ipv4 or ipv6

Default

ipv4

ip-address

displays RP information associated with the specified IP address

Output

The following output is an example of RP output information, and RP Field Descriptions describes the fields.

Output Example 
*A:Sar18 Dut-B>show>router>pim# rp
===============================================================================
PIM RP Set ipv4
===============================================================================
Group Address                                                Hold Expiry
  RP Address                                   Type     Prio Time Time
-------------------------------------------------------------------------------
224.0.0.0/4                                                                   
  10.200.200.4                                Dynamic  192  150   N/A        
  10.1.7.1                                     Static   1    N/A   N/A        
===============================================================================
Table 20. RP Field Descriptions

Label

Description

Group Address

The multicast group address of the entry

RP Address

The IP address of the RP

Type

Indicates whether the entry was learned through the bootstrap mechanism or was statically configured

Prio

The priority for the specified group address. The higher the value, the higher the priority

Hold Time

The value of the hold time present in the BSM message

Expiry Time

The length of time until the entry expires

rp-hash
Syntax

rp-hash ip-address

Context

show>router>pim

Description

This command hashes the RP for the multicast group address associated with the specified IPv4 address.

Parameters
ip-address

displays RP information for the multicast group associated with the specified IPv4 address

Output

The following output is an example of RP hash output information, and RP Hash Field Descriptions describes the fields.

Output Example 
*A:Sar18 Dut-B# show router pim rp-hash 239.255.0.0
==============================================
PIM Group-To-RP mapping
==============================================
Group Address      RP Address      Type
----------------------------------------------
239.255.0.0        239.255.200.4   Bootstrap
==============================================
*A:Sar18 Dut-B#
Table 21. RP Hash Field Descriptions

Label

Description

Group Address

The multicast group address for the specified IP address

RP Address

The IP address of the RP

Type

Indicates whether the entry was learned through the bootstrap mechanism or was statically configured

s-pmsi
Syntax

s-pmsi [detail]

s-pmsi [mdSrcAddr [mdGrpAddr]] [detail]

s-pmsi ext-tunnel-id ext-tunnel-id [tunnel-id tunnel-id] [detail]

s-pmsi root-addr root-addr [lsp-id lsp-id] [detail]

Context

show>router>pim

Description

This command displays PIM S-PMSIs that are currently active.

Parameters
detail

displays detailed information

mdSrcAddr

displays PIM S-PMSI information associated with the specified source address of the multicast sender

mdGrpAddr

displays PIM S-PMSI information associated with the specified group address of the multicast sender

ext-tunnel-id

displays PIM S-PMSI information associated with the specified external tunnel ID

tunnel-id

displays PIM S-PMSI information associated with the specified tunnel ID

root-addr

displays PIM S-PMSI information associated with the specified root address

Output

The following output is an example of S-PMSI output information, and S-PMSI Field Descriptions describes the fields.

Output Example 
*B:node-6# show router 100 pim s-pmsi
===============================================================================
PIM Selective provider tunnels
===============================================================================
MD Src Address        MD Grp Address        MT Index      Num VPN SGs         
-------------------------------------------------------------------------------
239.255.0.1         239.255.89.72           24603         1                   
239.255.0.2         239.255.89.73           24604         1                   
239.255.0.3         239.255.89.74           24605         1                   
239.255.0.4         239.255.89.75           24606         1                   
239.255.0.5         239.255.89.76           24607         1                   
239.255.0.6         239.255.89.77           24608         1                   
239.255.0.7         239.255.89.78           24609         1                   
239.255.0.8         239.255.89.79           24610         1                   
239.255.0.9         239.255.89.80           24611         1                   
239.255.0.10        239.255.89.81           24612         1                   
239.255.0.11        239.255.89.82           24613         1                   
239.255.0.12        239.255.89.83           24614         1                   
239.255.0.13        239.255.89.84           24615         1                   
239.255.0.14        239.255.89.85           24616         1                   
239.255.0.15        239.255.89.86           24617         1                   
239.255.0.16        239.255.89.87           24618         1
...
===============================================================================
*B:node-6# 


*B:node-6# show router 100 pim s-pmsi detail
===============================================================================
PIM Selective provider tunnels
===============================================================================
Md Source Address  : 239.255.0.1      Md Group Address   : 239.255.89.72      
Number of VPN SGs  : 1                Uptime             : 0d 00:00:18      
MT IfIndex         : 24603            Egress Fwding Rate : 163.2 kbps       

VPN Group Address  : 239.255.0.0      VPN Source Address : 10.2.102.1       
State              : RX Joined                                                
Expiry Timer       : 0d 00:02:41 
===============================================================================
PIM Selective provider tunnels
===============================================================================
Md Source Address  : 239.255.0.2      Md Group Address   : 239.255.89.73      
Number of VPN SGs  : 1                Uptime             : 0d 00:00:18      
MT IfIndex         : 24604            Egress Fwding Rate : 163.2 kbps       

VPN Group Address  : 239.255.0.1      VPN Source Address : 10.2.102.1       
State              : RX Joined                                                
Expiry Timer       : 0d 00:02:41 
===============================================================================
PIM Selective provider tunnels
===============================================================================
Md Source Address  : 239.255.0.4     Md Group Address   : 239.255.89.74      
Number of VPN SGs  : 1               Uptime             : 0d 00:00:20      
MT IfIndex         : 24605           Egress Fwding Rate : 165.7 kbps       

VPN Group Address  : 239.255.0.2     VPN Source Address : 10.2.102.1       
State              : RX Joined                                                
Expiry Timer       : 0d 00:02:39 
===============================================================================
PIM Selective provider tunnels
===============================================================================
Md Source Address  : 239.255.0.5      Md Group Address   : 239.255.89.75      
Number of VPN SGs  : 1                Uptime             : 0d 00:00:20      
MT IfIndex         : 24606            Egress Fwding Rate : 165.7 kbps       

VPN Group Address  : 239.255.0.3      VPN Source Address : 10.2.102.1       
State              : RX Joined                                                
Expiry Timer       : 0d 00:02:39                                              
===============================================================================
*B:node-6# 
Table 22. S-PMSI Field Descriptions

Label

Description

MD Grp Address

The IP multicast group address for which this entry contains information

MD Src Address

The source address of the multicast sender

A value of 0 (zero) indicates that the type is configured as starg.

MT Index

MT IfIndex

Displays the index number

Num VP SGs

Displays the number of VPN (S,G)s

Uptime

The length of time that the S-PMSI has been up

Egress Fwding Rate

he egress forwarding rate for the S-PMSI

VPN Group Address

The VPN group address for the S-PMSI

VPN Source Address

The VPN source address for the S-PMSI

Expiry Timer

The minimum time remaining before this S_PMSI will be aged out

A value of 0 (zero) means that this S-PMSI will never be aged out, which occurs when the PIM neighbor sends a Hello message with hold time set to 0xffff

statistics
Syntax

statistics [ip-int-name | ip-address] [family]

Context

show>router>pim

Description

This command displays statistics for a particular PIM instance.

Parameters
ip-int-name

displays the interface information associated with the specified IP interface name

ip-address

displays the interface information associated with the specified IP address

family

displays either IPv4 or IPv6 information

Values

ipv4 or ipv6

Output

The following output is an example of PIM statistics output information, and PIM Statistics Field Descriptions describes the fields.

Output Example 
*A:7CSA:Dut-C# show router pim statistics 
================================================================
PIM Statistics ipv4
================================================================
Message Type        Received       Transmitted    Rx Errors                    
----------------------------------------------------------------
Hello               25435          2907           0             
Join Prune          75796          79             0             
Asserts             0              0              0             
Register            0              0              0             
Null Register       0              0              0             
Register Stop       0              0              0             
BSM                 0              0              0             
Candidate RP Adv    0              0              0             
Total Packets       101231         2986                         
-------------------------------------------------------------------------------
General Statistics
-------------------------------------------------------------------------------
Rx Invalid Register               : 0
Rx Neighbor Unknown               : 0
Rx Bad Checksum Discard           : 0
Rx Bad Encoding                   : 0
Rx Bad Version Discard            : 0
Rx CRP No Router Alert            : 0
Rx BSM Router Alert Drops         : 0
Rx BSM Wrong If Drops             : 0
Rx Invalid Join Prune             : 0
Rx Unknown PDU Type               : 0
Join Policy Drops                 : 0
Register Policy Drops             : 0
Bootstrap Import Policy Drops     : 0
Bootstrap Export Policy Drops     : 0
Fwd Candidate RP Adv              : 0
Fwd Candidate RP Adv Drops        : 0
-------------------------------------------------------------------------------
Source Group Statistics
-------------------------------------------------------------------------------
(S,G)                             : 64
(*,G)                             : 0
(*,*,RP)                          : 0
================================================================
Table 23. PIM Statistics Field Descriptions

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)
status
Syntax

status [detail] [family]

Context

show>router>pim

Description

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:

A:NYC# show router pim status
MINOR: CLI PIM is not configured.
A:NYC#
Parameters
family

displays either IPv4 or IPv6 information

Values

ipv4 or ipv6

detail

displays detailed status information

Output

The following output is an example of PIM status information, and PIM Status Field Descriptions describes the fields.

Output Example 
*A:7705:Dut-A# show router pim status detail ipv4 
===============================================================================
PIM Status ipv4
===============================================================================
Admin State                       : Up
Oper State                        : Up

IPv4 Admin State                  : Up
IPv4 Oper State                   : Up

BSR State                         : Accept Any

Elected BSR
    Address                       : None
    Expiry Time                   : N/A
    Priority                      : N/A
    Hash Mask Length              : 30
    Up Time                       : N/A
    RPF Intf towards E-BSR        : N/A

Policy                            : None
                                      
RPF Table                         : rtable-u

Non-DR-Attract-Traffic            : Disabled
===============================================================================

*A:7705:Dut-A# show router pim status detail ipv6 
===============================================================================
PIM Status ipv6
===============================================================================
Admin State                       : Up
Oper State                        : Up

IPv6 Admin State                  : Down
IPv6 Oper State                   : Down

BSR State                         : Accept Any

Elected BSR
    Address                       : None
    Expiry Time                   : N/A
    Priority                      : N/A
    Hash Mask Length              : 126
    Up Time                       : N/A
    RPF Intf towards E-BSR        : N/A

Policy                            : None
                                      
RPF Table                         : rtable6-u

Non-DR-Attract-Traffic            : Disabled
===============================================================================
Table 24. PIM Status Field Descriptions

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

msdp
Syntax

msdp

Context

show>router

Description

This command enables the context to display MSDP information.

group
Syntax

group [group-name] [detail]

Context

show>router>msdp

Description

This command displays information about MSDP groups.

Parameters
group-name

displays information about the specified group. If no group-name is specified, information about all groups is displayed.

detail

displays detailed MSDP group information

Output

The following output is an example of MSDP group information, and MSDP Group Field Descriptions describes the fields.

Output Example 
*A:ALA-48>show>router>msdp# group
===============================================================================
MSDP Groups
===============================================================================
Group Name                        Mode        Act Srcs  Local Address          
-------------------------------------------------------------------------------
main                              Mesh-group  None      None       
loop1                             Mesh-group  None      None                   
loop2                             Mesh-group  None      None                   
loop3                             Mesh-group  None      None                   
loop4                             Mesh-group  None      None                   
loop5                             Mesh-group  None      None                   
-------------------------------------------------------------------------------
Groups : 6
=======================
*A:ALA-48>show>router>msdp# 


*A:ALA-48>show>router>msdp# group test
===============================================================================
MSDP Groups
===============================================================================
Group Name                        Mode       Act Srcs  Local Address
-------------------------------------------------------------------------------
test                              Mesh-group 50000     10.10.10.103
-------------------------------------------------------------------------------
Groups : 1
===============================================================================
*A:ALA-48>show>router>msdp#


*A:ALA-48>show>router>msdp# group test detail
===============================================================================
MSDP Groups
===============================================================================
Group Name         : test
-------------------------------------------------------------------------------
Local Address      : 10.10.10.103
Admin State        : Up                 Receive Msg Rate   : None
Receive Msg Time   : None               Receive Msg Thd    : None
Mode               : Mesh-group         SA Limit           : 50000
Export Policy      : None Specified / Inherited
Import Policy      : None Specified / Inherited

-------------------------------------------------------------------------------
Groups : 1
===============================================================================
*A:ALA-48>show>router>msdp#
Table 25. MSDP Group Field Descriptions

Label

Description

Group Name

Displays the MSDP group name

Mode

Displays the mode of peers in the group, either Mesh-group or Standard

Act Srcs

Displays the configured maximum number of SA messages that will be accepted by MSDP

Local Address

Displays the local end of an MSDP session

Admin State

Displays the administrative state

Receive Msg Rate

Displays the rate that the messages are read from the TCP session

Receive Msg Time

Displays the time interval in which the number of MSDP messages set by the receive-msdp-msg-rate number parameter are read from the TCP session

Receive Msg Thd

Displays the configured threshold for the number of MSDP messages that can be processed before the MSDP message rate-limiting function is activated

SA Limit

Displays the SA message limit

Export Policy

Displays whether an export policy is configured or inherited

Import Policy

Displays whether an import policy is configured or inherited
peer
Syntax

peer [ip-address] [group group-name] [detail]

Context

show>router>msdp

Description

This command displays information about an MSDP peer.

Parameters
ip-address

displays information about the peer with the specified IP address. If no IP address is specified, information about all MSDP peers is displayed.

group-name

displays information about peers in the specified group. If no group-name is specified, information about all MSDP peers display is displayed.

detail

displays detailed MSDP peer information

Output

The following output is an example of MSDP peer information, and MSDP Peer Field Descriptions describes the fields.

Output Example 
A:ALA-48# show router msdp peer
=============================================================================
MSDP Peers
=============================================================================
Peer             Local Address    State       Last State Change     SA Learnt
-----------------------------------------------------------------------------
10.20.1.1        10.20.1.6        Established 08/30/2002 03:22:13   1008    
-----------------------------------------------------------------------------
Peers : 1
=============================================================================
A:ALA-48# 


A:ALA-48# show router msdp peer detail
===============================================================================
MSDP Peers
-------------------------------------------------------------------------------
Peer Address       : 10.20.1.1                                                
-------------------------------------------------------------------------------
Group Name         : None                                                     
Local Address      : 10.20.1.6                                                
Last State Change  : 08/30/2002 03:22:13 Last Act Src Limit : N/A
Peer Admin State   : Up                 Default Peer       : No               
Peer Connect Retry : 0                  State              : Established      
SA accepted        : 1008               SA received        : 709              
State timer expires: 18                 Peer time out      : 62               
Active Source Limit: None               Receive Msg Rate   : 0                
Receive Msg Time   : 0                  Receive Msg Thd    : 0                
Auth Status        : Disabled           Auth Key           : None             
Export Policy      : None Specified / Inherited
Import Policy      : None Specified / Inherited
-------------------------------------------------------------------------------
Peers : 1
===============================================================================
A:ALA-48#
Table 26. MSDP Peer Field Descriptions

Label

Description

Peer

Displays the IP address of the peer

Local Address

Displays the local IP address

State

Displays the current state of the peer

Last State Change

Displays the date and time of the peer’s last state change

SA Learnt

Displays the number of SAs learned through a peer

source
Syntax

source [ip-address/mask] [type {configured | dynamic | both}] [detail]

Context

show>router>msdp

Description

This command displays the discovery method for the specified multicast source. By default, all user-created sources are displayed.

Parameters
ip-address/mask

specifies the IP address and mask for a multicast source

Values

ip-address is in the format a.b.c.d

mask range is from 1 to 32

configured

displays user-created sources

dynamic

displays dynamically created sources

both

displays both user-configured and dynamically created sources

detail

displays detailed MSDP source information

Output

The following output is an example of MSDP source information and MSDP Source Field Descriptions describes the fields.

Output Example 
*A:7705:Dut-C# show  router msdp source 
===============================================================================
MSDP Sources
===============================================================================
Source             Type         SA Limit   Num Excd   Last Exceeded
-------------------------------------------------------------------------------
10.3.3.3/32         Configured   None       0          N/A
-------------------------------------------------------------------------------
Sources : 1
===============================================================================
*A:7705:Dut-C# 
Table 27. MSDP Source Field Descriptions

Label

Description

Source

Displays the IP address of the MSDP peer

Type

Displays the type of peer

SA Limit

Displays the local IP address

Num Excd

Displays the number of times the global active source limit has been exceeded

Last Exceeded

Displays the date and time of the last state change of the peer
source-active
Syntax

source-active [{group ip-address | local | originator ip-address | peer ip-address | source ip-address | group ip-address source ip-address}] [detail]

Context

show>router>msdp

Description

This command displays source-active (SA) messages accepted by MSDP.

Parameters
group ip-address

displays information about the specified group IP address

local

displays information about local SA messages

originator ip-address

displays information about the specified originator IP address

peer ip-address

displays information about the specified peer IP address

source ip-address

displays information about the specified source IP address

detail

displays detailed MSDP SA information

Output

The following output is an example of accepted MSDP SA messages information, and MSDP SA Field Descriptions describes the fields.

Output Example 
A:ALA-48# show router msdp source-active
===============================================================================
MSDP Source Active Info
===============================================================================
Grp Address      Src Address      Origin RP        Peer Address State Timer
-------------------------------------------------------------------------------
239.255.0.0      239.255.1.2      10.20.1.1        10.20.1.1    69        
239.255.0.1      239.255.1.2      10.20.1.1        10.20.1.1    69        
239.255.0.2      239.255.1.2      10.20.1.1        10.20.1.1    69        
239.255.0.3      239.255.1.2      10.20.1.1        10.20.1.1    69        
239.255.0.4      239.255.1.2      10.20.1.1        10.20.1.1    69        
239.255.0.5      239.255.1.2      10.20.1.1        10.20.1.1    69        
239.255.0.6      239.255.1.2      10.20.1.1        10.20.1.1    69        
239.255.0.7      239.255.1.2      10.20.1.1        10.20.1.1    69        
239.255.0.8      239.255.1.2      10.20.1.1        10.20.1.1    69        
239.255.0.9      239.255.1.2      10.20.1.1        10.20.1.1    69        
-------------------------------------------------------------------------------
MSDP Source Active : 10
===============================================================================
A:ALA-48# 


A:ALA-48# show router msdp source-active detail
===============================================================================
MSDP Source Active
===============================================================================
Group Address      : 239.255.0.0        Source Address     : 10.112.1.2      
Origin RP          : 10.20.1.1          Peer Address       : 10.20.1.1        
State Timer        : 64                 Up Time            : 3d 01:44:25      
Group Address      : 239.255.0.1        Source Address     : 10.112.1.2      
Origin RP          : 10.20.1.1          Peer Address       : 10.20.1.1        
State Timer        : 64                 Up Time            : 48d 18:22:29     
Group Address      : 239.255.0.2        Source Address     : 10.112.1.2      
Origin RP          : 10.20.1.1          Peer Address       : 10.20.1.1        
State Timer        : 64                 Up Time            : 48d 18:22:29     
Group Address      : 239.255.0.3        Source Address     : 10.112.1.2      
Origin RP          : 10.20.1.1          Peer Address       : 10.20.1.1        
State Timer        : 64                 Up Time            : 48d 18:22:29     
Group Address      : 239.255.0.4        Source Address     : 10.112.1.2      
Origin RP          : 10.20.1.1          Peer Address       : 10.20.1.1        
State Timer        : 64                 Up Time            : 48d 18:22:29     
Group Address      : 239.255.0.5        Source Address     : 10.112.1.2      
Origin RP          : 10.20.1.1          Peer Address       : 10.20.1.1        
State Timer        : 64                 Up Time            : 48d 18:22:29     
Group Address      : 239.255.0.6        Source Address     : 10.112.1.2      
Origin RP          : 10.20.1.1          Peer Address       : 10.20.1.1        
State Timer        : 64                 Up Time            : 48d 18:22:29     
Group Address      : 239.255.0.7        Source Address     : 10.112.1.2      
Origin RP          : 10.20.1.1          Peer Address       : 10.20.1.1        
State Timer        : 64                 Up Time            : 48d 18:22:29     
Group Address      : 239.255.0.8        Source Address     : 10.112.1.2      
Origin RP          : 10.20.1.1          Peer Address       : 10.20.1.1        
State Timer        : 64                 Up Time            : 48d 18:22:29     
Group Address      : 239.255.0.9        Source Address     : 10.112.1.2      
Origin RP          : 10.20.1.1          Peer Address       : 10.20.1.1        
State Timer        : 64                 Up Time            : 48d 18:22:29     
-------------------------------------------------------------------------------
MSDP Source Active : 10
===============================================================================
A:ALA-48# 
Table 28. MSDP SA Field Descriptions

Label

Description

Grp Address

Displays the IP address of the group

Src Address

Displays the IP address of the source

Origin RP

Displays the originating rendezvous point (RP) address

Peer Address

Displays the IP address of the peer

State Timer

Displays the state timeout value. If the value reaches 0, the SA entry is removed.
source-active-rejected
Syntax

source-active-rejected [peer-group name] [group ip-address] [source ip-address] [originator ip-address] [peer ip-address]

Context

show>router>msdp

Description

This command displays SA messages rejected by MSDP.

Parameters
name

displays information about rejected SA messages for the specified peer group

group ip-address

displays information about the specified group IP address

source ip-address

displays information about the source address of the source-active entry that is rejected

originator ip-address

displays information about the specified originator IP address

peer ip-address

displays information about the peer from which this rejected source-active entry was last received

Output

The following output is an example of rejected MSDP SA messages information, and MSDP Source-Active Field Descriptions describes the fields.

Output Example 
*A:ALA-48# show router msdp source-active-rejected
===============================================================================
MSDP Source Active Rejected Info
===============================================================================
Grp Address     Src Address     Origin RP       Peer Address    Reject Reason
-------------------------------------------------------------------------------
239.255.0.1     10.0.0.1       10.20.0.1       10.10.0.1        Import Policy
239.255.0.2     10.0.0.2       10.20.0.2       10.10.0.2        Export Policy
239.255.0.3     10.0.0.3       10.20.0.3       10.10.0.3        RPF Failure
239.255.0.4     10.0.0.4       10.20.0.4       10.10.0.4        Limit Exceeded
239.255.0.5     10.0.0.5       10.20.0.5       10.10.0.5        Limit Exceeded
239.255.0.6     10.0.0.6       10.20.0.6       10.10.0.6        Limit Exceeded
239.255.0.7     10.0.0.7       10.20.0.7       10.10.0.7        Limit Exceeded
-------------------------------------------------------------------------------
SA Rejected Entries : 7
===============================================================================
*A:ALA-48# 
Table 29. MSDP Source-Active Field Descriptions

Label

Description

Grp Address

Displays the IP address of the group

Src Address

Displays the IP address of the source

Origin RP

Displays the originating rendezvous point (RP) address

Peer Address

Displays the address of the peer

Reject Reason

Displays the reason why this SA entry is rejected

statistics
Syntax

statistics [peer ip-address]

Context

show>router>msdp

Description

This command displays statistics information related to an MSDP peer.

Parameters
ip-address

displays statistics for the peer with the specified IP address

Output

The following output is an example of MSDP statistics information, and MSDP Statistics Field Descriptions describes the fields.

Output Example 
A:ALA-48# show router msdp statistics
===============================================================================
MSDP Statistics
===============================================================================
Glo ActSrc Lim Excd: 0                                                        
-------------------------------------------------------------------------------
Peer Address       : 10.20.1.1                                                
-------------------------------------------------------------------------------
Last State Change  : 0d 11:33:16        Last message Peer  : 0d 00:00:17      
RPF Failures       : 0                  Remote Closes      : 0                
SA Msgs Sent       : 0                  SA Msgs Recvd      : 709              
SA req. Msgs Sent  : 0                  SA req. Msgs Recvd : 0                
SA res. Msgs Sent  : 0                  SA res. Msgs Recvd : 0                
KeepAlive Msgs Sent: 694                KeepAlive Msgs Recd: 694              
Unknown Msgs Sent  : 0                  Error Msgs Recvd   : 0                
-------------------------------------------------------------------------------
Peers : 1
===============================================================================
A:ALA-48#
Table 30. MSDP Statistics Field Descriptions

Label

Description

Glo ActSrc Lim Excd

Displays the number of global active source messages that exceed the configured limit

Peer Address

Displays the address of the MSDP peer

Last State Change

Displays the date and time the peer state changed

Last message Peer

Displays the time the last message was received from the peer

RPF Failures

Displays the number of reverse path forwarding (RPF) failures

Remote Closes

Displays the number of times the remote peer closed

SA Msgs Sent

Displays the number of SA messages sent

SA Msgs Recvd

Displays the number of SA messages received

SA req. Msgs Sent

Displays the number of SA request messages sent

SA req. Msgs Recvd

Displays the number of SA request messages received

SA res. Msgs Sent

Displays the number of SA response messages sent

SA res. Msgs Recvd

Displays the number of SA response messages received

KeepAlive Msgs Sent

Displays the number of keepalive messages sent

KeepAlive Msgs Recd

Displays the number of keepalive messages received

Unknown Msgs Sent

Displays the number of unknown messages sent

Error Msgs Recvd

Displays the number of error messages received

status
Syntax

status

Context

show>router>msdp

Description

This command displays MSDP status information.

Output

The following output is an example of MSDP status information, and MSDP Status Field Descriptions describes the fields.

Output Example 
A:ALA-48# show router msdp status 
===============================================================================
MSDP Status
===============================================================================
Admin State                       : Up 
Local Address                     : None 
Global Statistics
Active Src Limit                  : None                                      
Act Src Lim Excd                  : 0                                         
Num. Peers                        : 1                                         
Num. Peers Estab                  : 1                                         
Num. Source Active                : 10 
Policies                          : None
Data Encapsulation                : Enabled 
Receive Msg Rate
Rate                              : 0                                         
Time                              : 0                                         
Threshold                         : 0 
Last Msdp Enabled                 : 08/30/2002 03:21:43
===============================================================================
A:ALA-48#
Table 31. MSDP Status Field Descriptions

Label

Description

Admin State

Displays the administrative state

Local Address

Displays the local IP address

Global Statistics

Displays global MSDP statistics

Active Src Limit

Displays the active source limit

Act Src Lim Excd

Displays the number of times that the active source limit was exceeded

Num. Peers

Displays the number of peers

Num. Peers Estab

Displays the number of peers established

Num. Source Active

Displays the number of active sources

Policies

Specifies the policy used to export the SA state from the SA list into MSDP

Data Encapsulation

Specifies whether the rendezvous point (RP) encapsulates multicast data received in MSDP register messages inside forwarded MSDP SA messages

Rate

The receive message rate

Time

The receive message interval

Threshold

The number of MSDP messages that can be processed before the MSDP message rate-limiting function is activated

Last Msdp Enabled

The time the last MSDP was triggered

Clear Commands

igmp
Syntax

igmp

Context

clear>router

Description

This command enables the context to clear and reset IGMP entities.

database
Syntax

database [interface ip-int-name | ip-address] [group grp-ip-address [source src-ip-address]]

Context

clear>router>igmp

Description

This command clears IGMP database statistics on a specified interface or IP address.

Parameters
ip-int-name

clears the IGMP database on the specified interface

ip-address

clears the IGMP database on the specified IP address

grp-ip-address

clears the multicast group address (ipv4) or zero address in the specified address group

src-ip-address

clears the IGMP database from the specified source IP address

statistics
Syntax

statistics [ip-int-name | ip-address]

Context

clear>router>igmp

Description

This command clears IGMP statistics on a specified interface or IP address.

An interface and group/source cannot be specified at the same time.

Parameters
ip-int-name

clears IGMP statistics on the specified interface

ip-address

clears IGMP statistics on the specified IP address

version
Syntax

version [ip-int-name | ip-address]

Context

clear>router>igmp

Description

This command clears IGMP version parameters.

Parameters
ip-int-name

clears version information for the specified IGMP interface name

ip-address

clears version information for the specified IGMP IP address

mld
Syntax

mld

Context

clear>router

Description

This command enables the context to clear and reset MLD entities.

database
Syntax

database [interface ip-int-name | ipv6-address] [group grp-ipv6-address [source src-ipv6-address]]

Context

clear>router>mld

Description

This command clears MLD database parameters.

Parameters
ip-int-name

clears database information for the specified MLD interface name

ipv6-address

clears database information for the specified MLD interface IPv6 address

grp-ipv6-address

clears database information for the specified MLD group IPv6 address

src-ipv6-address

clears database information for the specified MLD source IP address

statistics
Syntax

statistics [ip-int-name | ipv6-address]

Context

clear>router>mld

Description

This command clears MLD statistics parameters.

Parameters
ip-int-name

clears statistics for the specified MLD interface name

ipv6-address

clears statistics for the specified MLD IPv6 address

version
Syntax

version [ip-int-name | ip-address]

Context

clear>router>mld

Description

This command clears MLD version parameters.

Parameters
ip-int-name

clears version information for the specified MLD interface name

ip-address

clears version information for the specified MLD IP address

pim
Syntax

pim

Context

clear>router

Description

This command enables the context to clear and reset PIM entities.

database
Syntax

database [interface ip-int-name | ip-address] [group grp-ip-address [source src-ip-address]] [family]

Context

clear>router>pim

Description

This command clears PIM database statistics on a specified interface or IP address.

Parameters
ip-int-name

clears the PIM database on the specified interface

ip-address

clears the PIM database on the specified IP address

grp-ip-address

clears the multicast group address (ipv4/ipv6) or zero address in the specified address group

src-ip-address

clears the PIM database from the specified source IP address

family

clears either IPv4 or IPv6 information

Values

ipv4 or ipv6

neighbor
Syntax

neighbor [ip-int-name] [family]

Context

clear>router>pim

Description

This command clears PIM neighbor data on a specified interface or IP address.

Parameters
ip-int-name

clears PIM neighbor data on the specified interface

family

clears either IPv4 or IPv6 information. If family is not specified, both IPv4 and IPv6 data are cleared.

Values

ipv4 or ipv6

statistics
Syntax

statistics [family]

statistics interface ip-int-name | ip-address [family]

statistics group grp-ip-address [source ip-address] [family]

Context

clear>router>pim

Description

This command clears PIM statistics.

Parameters
ip-int-name

clears PIM statistics on the specified interface

interface ip-address

clears PIM statistics on the specified IP address

grp-ip-address

specifies a multicast group address (IPv4 or IPv6 or zero address). When the group address is specified along with the source address, then the (S,G) statistics are reset to zero.

source ip-address

specifies a source or RP address (IPv4 or IPv6). When the source address is specified along with the group address, then the (S,G) statistics are reset to zero.

family

clears either IPv4 or IPv6 information. If family is not specified, both IPv4 and IPv6 data are cleared.

Values

ipv4 or ipv6

msdp
Syntax

msdp

Context

clear>router

Description

This command enables the context to clear and reset Multicast Source Discovery Protocol (MSDP) entities and statistics.

cache
Syntax

cache [peer ip-address] [group ip-address] [source ip-address] [originrp ip-address]

Context

clear>router>msdp

Description

This command clears IP addresses from the MSDP cache.

Parameters
peer ip-address

clears the specified peer address

group ip-address

clears the specified group address

source ip-address

clears the specified source address

originrp ip-address

clears the specified originating rendezvous point (RP) address

statistics
Syntax

statistics [peer ip-address]

Context

clear>router>msdp

Description

This command clears IP address statistics for the peer to which MSDP SA requests for groups matching this entry's group range were sent.

Parameters
ip-address

clears the MSDP statistics for the specified IP address

Monitor Commands

group
Syntax

group grp-ip-address [source ip-address] [interval interval] [repeat repeat] [absolute | rate]

Context

monitor>router>pim

Description

This command monitors statistics for a PIM source group.

Parameters
grp-ip-address

the IP address of a multicast group that identifies a set of recipients that are interested in a particular data stream

Values

IPv4 or IPv6 address | 0

ip-address

the source or RP IP address to use in the ping requests

Values

IPv4 or IPv6 address

Default

0.0.0.0 to 255.255.255.255

interval

specifies the interval for each display, in seconds

Values

10 | 20 | 30 | 40 | 50 | 60

Default

10

repeat

specifies the number of times the command is repeated

Values

1 to 999

Default

10

absolute

displays raw statistics, without processing. No calculations are performed on the delta or rate statistics.

rate

displays the rate per second for each statistic, instead of the delta

Debug Commands

Debug IGMP Commands
igmp
Syntax

igmp

Context

debug>router

Description

This command enables access to the IGMP debug commands.

interface
Syntax

[no] interface [ip-int-name | ip-address]

Context

debug>router>igmp

Description

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.

Parameters
ip-int-name

displays the information associated with the specified IP interface name

ip-address

displays the information associated with the specified IP address

misc
Syntax

[no] misc

Context

debug>router>igmp

Description

This command enables debugging for IGMP miscellaneous information.

The no form of the command disables the debugging.

packet
Syntax

[no] packet [query | v1-report | v2-report | v3-report | v2-leave] [ip-int-name | ip-address]

Context

debug>router>igmp

Description

This command enables debugging for IGMP packets.

The no form of the command disables the debugging.

Parameters
query

specifies to log the IGMP group- and source-specific queries transmitted and received on this interface

v1-report

specifies to log IGMPv1 reports transmitted and received on this interface

v2-report

specifies to log IGMPv2 reports transmitted and received on this interface

v3-report

specifies to log IGMPv3 reports transmitted and received on this interface

v2-leave

specifies to log the IGMP Leaves transmitted and received on this interface

ip-int-name

displays the information associated with the specified IP interface name

ip-address

displays the information associated with the specified IP address

Debug MLD Commands
mld
Syntax

mld

Context

debug>router

Description

This command enables access to the MLD debug commands.

interface
Syntax

[no] interface [ip-int-name | ipv6-address]

Context

debug>router>mld

Description

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.

Parameters
ip-int-name

displays the information associated with the specified IP interface name

ipv6-address

displays the information associated with the specified IP address

misc
Syntax

[no] misc

Context

debug>router>mld

Description

This command enables debugging for MLD miscellaneous information.

The no form of the command disables the debugging.

packet
Syntax

[no] packet [query | v1-report | v2-report | v1-done] [ip-int-name | ipv6-address]

Context

debug>router>mld

Description

This command enables debugging for MLD packets.

The no form of the command disables the debugging.

Parameters
query

specifies to log the MLD group- and source-specific queries transmitted and received on this interface

v1-report

specifies to log MLDv1 reports transmitted and received on this interface

v2-report

specifies to log MLDv2 reports transmitted and received on this interface

v1-done

specifies to log the MLDv1 Done transmitted and received on this interface

ip-int-name

displays the information associated with the specified IP interface name

ipv6-address

displays the information associated with the specified IPv6 address

Debug PIM Commands
pim
Syntax

pim

Context

debug>router

Description

This command enables access to the PIM debug commands.

adjacency
Syntax

[no] adjacency

Context

debug>router>pim

Description

This command enables debugging for PIM adjacencies. The no form of the command disables debugging.

all
Syntax

all [group grp-ip-address] [source ip-address] [detail]

no all

Context

debug>router>pim

Description

This command enables debugging for all the PIM groups. The no form of the command disables debugging.

Parameters
grp-ip-address

debugs information associated with all PIM groups for the specified multicast group address

Values

IPv4 or IPv6 address

ip-address

debugs information associated with all PIM groups for the specified source address

Values

IPv4 or IPv6 address

detail

debugs detailed information about all PIM groups

assert
Syntax

assert [group grp-ip-address] [source ip-address] [detail]

no assert

Context

debug>router>pim

Description

This command enables debugging for the PIM assert mechanism. The no form of the command disables debugging.

Parameters
grp-ip-address

debugs information associated with the PIM assert mechanism for the specified multicast group address

Values

IPv4 or IPv6 address

ip-address

debugs information associated with the PIM assert mechanism for the specified source address

Values

IPv4 or IPv6 address

detail

debugs detailed information about the PIM assert mechanism

auto-rp
Syntax

auto-rp [detail]

no auto-rp

Context

debug>router>pim

Description

This command enables debugging for PIM auto-RP. The no form of the command disables debugging.

Parameters
detail

debugs detailed information about the PIM auto-RP mechanism

bgp
Syntax

bgp [source src-ip-address] [group grp-ip-address] [peer peer-ip-address]

no bgp

Context

debug>router>pim

Description

This command enables debugging for the PIM BGP mechanism. The no form of the command disables debugging.

Parameters
grp-ip-address

debugs PIM BGP information associated with the specified group IP address

Values

IPv4 or IPv6 address

peer-ip-address

debugs PIM BGP information associated with the specified peer IP address

Values

IPv4 or IPv6 address

src-ip-address

debugs PIM BGP information associated with the specified source IP address

Values

IPv4 or IPv6 address

detail

debugs detailed PIM BGP information

bsr
Syntax

bsr [detail]

no bsr

Context

debug>router>pim

Description

This command enables debugging for the PIM Bootstrap mechanism. The no form of the command disables debugging.

Parameters
detail

debugs detailed information about the PIM Bootstrap mechanism

data
Syntax

data [group grp-ip-address] [source ip-address] [detail]

no data

Context

debug>router>pim

Description

This command enables debugging for the PIM data exception. The no form of the command disables debugging.

Parameters
grp-ip-address

debugs information associated with the PIM data exception for the specified multicast group address

Values

IPv4 or IPv6 address

ip-address

debugs information associated with the PIM data exception for the specified source address

Values

IPv4 or IPv6 address

detail

debugs detailed information about the PIM data exception

db
Syntax

db [group grp-ip-address] [source ip-address] [detail]

no db

Context

debug>router>pim

Description

This command enables debugging for the PIM database. The no form of the command disables debugging.

Parameters
grp-ip-address

debugs information associated with the PIM database for the specified multicast group address

Values

IPv4 or IPv6 address or zero address

ip-address

debugs information associated with the PIM database for the specified source address

Values

IPv4 or IPv6 address

detail

debugs detailed information about the PIM database

interface
Syntax

interface [ip-int-name | int-ip-address] [detail]

no interface

Context

debug>router>pim

Description

This command enables debugging for the PIM interface. The no form of the command disables debugging.

Parameters
ip-int-name

debugs information associated with the specified IP interface name

Values

IPv4 or IPv6 address

int-ip-address

debugs information associated with the specified IP address

Values

IPv4 or IPv6 address

detail

debugs detailed information about the IP interface

jp
Syntax

jp [group grp-ip-address] [source ip-address] [detail]

no jp

Context

debug>router>pim

Description

This command enables debugging for the PIM join-prune mechanism. The no form of the command disables debugging.

Parameters
grp-ip-address

debugs information associated with the specified PIM join-prune mechanism

Values

IPv4 or IPv6 address or zero address

ip-address

debugs information associated with the specified PIM join-prune mechanism

Values

IPv4 or IPv6 address

detail

debugs detailed information about the PIM join-prune mechanism

mrib
Syntax

mrib [group grp-ip-address] [source ip-address] [detail]

no mrib

Context

debug>router>pim

Description

This command enables debugging for the PIM MRIB. The no form of the command disables debugging.

Parameters
grp-ip-address

debugs information associated with the specified PIM MRIB

Values

IPv4 or IPv6 address

ip-address

debugs information associated with the specified PIM MRIB

Values

IPv4 or IPv6 address

detail

debugs detailed information about PIM MRIBs

msg
Syntax

msg [detail]

no msg

Context

debug>router>pim

Description

This command enables debugging for PIM messaging. The no form of the command disables debugging.

Parameters
detail

debugs detailed information about PIM messaging

packet
Syntax

packet [hello | register | register-stop | jp | bsr | assert | crp] [ip-int-name | int-ip-address]

no packet

Context

debug>router>pim

Description

This command enables debugging for PIM packets. The no form of the command disables debugging.

Parameters
ip-int-name

debugs information associated with the specified IP interface name

Values

IPv4 or IPv6 interface name

int-ip-address

debugs information associated with the specified IP address of a particular packet type

red
Syntax

[no] red [detail]

Context

debug>router>pim

Description

This command enables debugging for the PIM redundancy mechanism. The no form of the command disables debugging.

Parameters
detail

debugs detailed information about the PIM redundancy mechanism

register
Syntax

register [group grp-ip-address] [source ip-address] [detail]

no register

Context

debug>router>pim

Description

This command enables debugging for the PIM register mechanism. The no form of the command disables debugging.

Parameters
grp-ip-address

debugs information associated with the specified PIM register

Values

IPv4 or IPv6 address

ip-address

debugs information associated with the specified PIM register

Values

IPv4 or IPv6 address

detail

debugs detailed information about the PIM register mechanism

rtm
Syntax

rtm [detail]

no rtm

Context

debug>router>pim

Description

This command enables debugging for the PIM RTM. The no form of the command disables debugging.

Parameters
detail

debugs detailed information about the PIM RTM

Debug MSDP Commands
msdp
Syntax

[no] msdp

Context

debug>router

Description

This command enables debugging for Multicast Source Discovery Protocol (MSDP).

The no form of the command disables MSDP debugging.

packet
Syntax

packet [pkt-type] [peer ip-address]

Context

debug>router>msdp

Description

This command enables debugging for MSDP packets.

The no form of the command disables MSDP packet debugging.

Parameters
pkt-type

debugs information associated with the specified packet type

Values

keep-alive, source-active, sa-request, sa-response

ip-address

debugs information associated with the specified peer IP address

pim
Syntax

pim [grp-address]

no pim

Context

debug>router>msdp

Description

This command enables debugging for MSDP PIM.

The no form of the command disables MSDP PIM debugging.

Parameters
grp-address

debugs the IP multicast group address for which this entry contains information

rtm
Syntax

rtm [rp-address]

no rtm

Context

debug>router>msdp

Description

This command enables debugging for MSDP route table manager (RTM).

The no form of the command disables MSDP RTM debugging.

Parameters
rp-address

debugs the IP multicast address for which this entry contains information

sa-db
Syntax

sa-db [group grpAddr] [source srcAddr] [rp rpAddr]

no sa-db

Context

debug>router>msdp

Description

This command enables debugging for MSDP source-active (SA) requests.

The no form of the command disables the MSDP SA database debugging.

Parameters
grpAddr

debugs the IP address of the group

srcAddr

debugs the source IP address

rpAddr

debugs the specified rendezvous point RP address

Debug Mtrace Commands
mtrace
Syntax

[no] mtrace

Context

debug>router

Description

This command enables access to the mtrace debug commands.

The no form of the command disables the debugging.

misc
Syntax

[no] misc

Context

debug>router>mtrace

Description

This command enables debugging for mtrace miscellaneous events.

The no form of the command disables the debugging.

packet
Syntax

[no] packet [query | request | response]

Context

debug>router>mtrace

Description

This command enables debugging for mtrace packets.

The no form of the command disables the debugging.

Parameters
query

specifies to log the mtrace queries transmitted and received

request

specifies to log the mtrace requests transmitted and received

response

specifies to log the mtrace responses transmitted and received