Multicast

This chapter provides information about Protocol Independent Multicast (PIM).

Note:

Multicast is supported on all 7210 SAS platforms as described in this document, except those operating in access-uplink mode.

Overview of multicast

IP multicast is a method of many-to-many communication that simplifies the delivery of unicast datagrams. In the case of unicast delivery, IP packets are sent from a single source to a single recipient. The source inserts the address of the target host in the IP header destination field of an IP datagram, and intermediate routers (if present) forward the datagram toward 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, multicast is used to distribute datagrams sourced from one or more hosts to a set of receivers that may be distributed over different (sub) networks. The delivery of multicast datagrams is significantly more complex.

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 destination IP address. A source does not have to register to send data to a group, nor does it need to be a member of the group.

Routers and Layer 3 (L3) switches use the Internet Group Management Protocol (IGMP) to manage membership for a multicast session. When a host needs to receive one or more multicast sessions, it signals its local router by sending a join message to each multicast group it needs to join. When a host needs to leave a multicast group, it sends a leave message.

To extend multicast to the Internet, the multicast backbone (Mbone) is used. The Mbone is layered on top of portions of the Internet. These portions, or islands, are interconnected using tunnels. The tunnels allow multicast traffic to pass between the multicast-capable portions of the Internet. As more and more routers in the Internet are multicast-capable (and scalable), the unicast and multicast routing table will converge.

The original Mbone was based on the Distance Vector Multicast Routing Protocol (DVMRP) and was very limited. The Mbone is, however, converging around the following protocol set:

  • IGMP

  • Protocol Independent Multicast (Sparse Mode) (PIM-SM)

Multicast models (SSM)

This section provides information about the Source-Specific Multicast (SSM) model.

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.

  • 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, and G is an SSM destination address. This averts 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 is 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 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. In terms of the IGMP and PIM-SM, this implies that neither the RP-based shared tree infrastructure of PIM-SM nor the MSDP protocol is required. Therefore, the complexity of the multicast routing infrastructure for SSM is low, making it viable for immediate deployment.

  • handling point-to-point applications

    Anticipating that point-to-multipoint applications such as Internet TV will be significant in the future; the SSM model is better suited for such applications.

Multicast features

This section describes the multicast requirements when a Nokia router is deployed as part of the user core network.

IGMP

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 typically only one querier per physical network.

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.

If the host needs to receive a multicast session issue and a multicast group membership report, the reports must be sent to all multicast-enabled routers.

IGMP versions and interoperability requirements

If routers run different versions of IGMP, they negotiate the lowest common version of IGMP that is supported on their subnet and operate in that version. The following versions of IGMP are supported:

  • Version 1

    Specified in RFC-1112, Host extensions for IP Multicasting 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 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 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 SSM, or from all but specific source addresses, sent to a particular multicast address.

IGMPv3 must keep track of the state of each group 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 needed reception state for that network.

IGMP version transition

Nokia 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 the interoperability issues and how they affect the routing protocols.

IGMPv3 specifies that if a router receives an earlier version query message on an interface, it must immediately switch to a mode that is compatible with the earlier version. Because the previous versions of IGMP are not source-aware, should this occur and the interface switches to version 1 or 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 then treats the query as if there is no EXCLUDE definition present.

SSM groups

IGMPv3 allows a receiver to join a group and specify that it only needs to receive traffic for a 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 for a group in this range, it should ignore it.

A Nokia PIM router must silently ignore a received (*,G) PIM join message where 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 router 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 allows a receiver to join a group and specify that it only needs to receive traffic for a group if that traffic does not come from a specific source or sources. In this case, the DR performs a (*,G) join as normal, but can combine this with a prune for each of the sources the receiver does not want to receive.

PIM-SM

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 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. PIM-SM in the ASM model initially 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 whether 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. The 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 MBGP. Regardless of how it is created, 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. 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.

PIM-SM functions

This section provides information about the three phases of PIM-SM functions.

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 can also serve this purpose. One of the receiver local routers is elected as the DR for that subnet. When the expression of interest is received, the DR sends a PIM join message toward 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 toward 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. This is known as the RP tree and is also known as the shared tree because it is shared by all sources sending to that group. Join messages are resent periodically as long as the receiver remains in the group. When all receivers on a leaf-network leave the group, the DR sends a PIM (*,G) prune message toward the RP for that multicast group. However, if the prune message is not sent for any reason, the state eventually times out.

A multicast data sender starts sending data destined for a multicast group. The sender local router (the DR) takes those data packets, unicast-encapsulates them, and sends them directly to the RP. The RP receives these encapsulated data packets, de-encapsulates them, and forwards them to the shared tree. The packets then follow the (*,G) multicast tree state in the routers on the RP tree, being replicated wherever the RP tree branches, and eventually reaching 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 flows 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 unsuitable 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 these reasons, the RP switches to native forwarding. To do this, when the RP receives a register-encapsulated data packet from source S on group G, it initiates an (S,G) source-specific join toward S. This join message travels hop-by-hop toward S, instantiating the (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 subnet or a router that already has the (S,G) multicast tree state, and packets from S start to flow following the (S,G) tree state toward the RP. These data packets can also reach routers with the (*,G) state along the path toward the RP, and if this occurs, they can 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 the S DR to prevent the DR unnecessarily encapsulating the packets. At the end of phase 2, traffic flows 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 therefore, phase two may occur before the shared tree to the receiver is built.

Phase three

In this phase, the RP joins back toward the source using the shortest path tree. Although having the RP join back toward 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 LAN, typically the DR, may optionally initiate a transfer from the shared tree to a source-specific shortest-path tree (SPT). To do this, it issues an (S,G) Join toward S. This instantiates the state in the routers along the path to S. Eventually, this join either reaches 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) receives two copies of the data — one from the SPT and one from the RPT. 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 toward the RP. The prune message travels hop-by-hop instantiating the state along the path toward 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 toward 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 correct 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). Each 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 its sending of further 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, it is detected and the mapping tables are 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 specific 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 it is 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 interface or 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. The following table describes the match conditions.

Table 1. Join filter policy match conditions

Match condition

Matches the:

Interface

RTR interface by name

Neighbor

The neighbors source address in the IP header

Group Address

Multicast Group address in the join/prune message

Source Address

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 one has joined the group at the RP, the RP ignores the registers

In an environment where the sources to particular multicast groups are always known, it is possible to apply register filters at the RP to prevent any unwanted sources from transmitting a multicast stream. You can apply these filters at the edge so that register data does not travel unnecessarily over the network toward the RP.

The following table describes the match conditions.

Table 2. Register filter policy match conditions

Match condition

Matches

Interface

The RTR 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 check (RPF). An 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 because of routing topology changes, any dynamic filters that may have been applied must be reevaluated. If filters are removed, the associated alarms are also cleared.

Anycast RP for PIM-SM

The implementation of anycast RP for PIM-SM environments enables fast convergence when a PIM rendezvous point (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 protocol Independent Multicast-Sparse Mode (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, which could cause loss-of-TV delivery to the end customer.

Anycast RP for PIM-SM environments are supported in the base routing/PIM-SM instance of the service router. This feature is 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 Rendezvous 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 Multicast Source Discovery Protocol (MSDP).

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 of 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 in all RPs in the set.

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

Figure 1. Anycast RP for PIM-SM implementation example
Note:

The address used for the RP address in the domain (the anycast-RP 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 anycast-RP address (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 get the packet to receivers R1A and R1B.

  4. RP1 is configured with RP2 and RP3 IP address. 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 anycast-RP address, an error has occurred and it should be rate-limited logged.

  5. RP1 sends a copy of the register message from S1 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 a (S1,G) Join message toward S1; however, RP1 must create the (S1,G) state.

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

  8. RP2 sends a register-stop message back to the 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 is sent when the next register is received. If RP2 decides not to wait, the register-stop message is sent now.

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

  10. RP3 receives the register message from RP1 and de-encapsulates it, but, because no receivers are joined for the group, it can discard the packet.

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

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

  13. RP1 processes the register-stop message 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, if all RPs in the anycast-RP set have returned register-stop messages for a particular (S,G) route when RP1 caches on a per-RP/per-(S,G) basis the receipt of register-stop messages from the RPs in the anycast-RP set.

The procedure for S2 sending follows the same previous steps, but it is RP3 that sends a copy of the register originated by S2 DR to RP1 and RP2. 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.

Distributing PIM joins over multiple ECMP paths

The per bandwidth/round robin method is commonly used in multicast load balancing. However, the interface in an ECMP set can also be used for a channel to be predictable without any knowledge of the other channels using the ECMP set.

The mc-ecmp-hashing-enabled command enables PIM joins to be distributed over multiple ECMP paths based on a hash of S and G. When a link in the ECMP set is removed, the multicast streams using the link are redistributed over the remaining ECMP links using the same hash algorithm. When a link is added to the ECMP set, new joins may be allocated to the new link based on the hash algorithm, but existing multicast streams using the other ECMP links stay on those links until they are pruned.

The default is no mc-ecmp-hashing-enabled, which means that the use of multiple ECMP paths (if enabled in the config>service>vprn context) is controlled by the existing implementation and CLI commands, that is, mc-ecmp-balance.

The mc-ecmp-hashing-enabled command and the mc-ecmp-balance command are mutually exclusive in the same context.

The following procedure is used to achieve distribution of streams across the ECMP links.

  1. For a specific S, G get all possible nHops.

  2. Sort these nHops based on nHop addresses.

  3. xor S and G addresses.

  4. Hash the xor address over a number of PIM next hops.

  5. Use the hash value obtained in step 4, and get that element, in the sorted list obtained in step 2, as the preferred nHop.

  6. If this element is not available or it is not a PIM nHop (PIM neighbor), the next available next hop is chosen.

PIM status output indicating ECMP hashing is disabled
*B:BB# show router 100 pim status

===============================================================================
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 toward E-BSR        : N/A

Candidate BSR
    Admin State                   : Down
    Oper State                    : Down
    Address                       : None
    Priority                      : 0
    Hash Mask Length              : 30

Candidate RP
    Admin State                   : Down
    Oper State                    : Down
    Address                       : 0.0.0.0
    Priority                      : 192
    Holdtime                      : 150

SSM-Default-Range                 : Enabled
SSM-Group-Range
    None

MC-ECMP-Hashing                   : Disabled

Policy                            : None

RPF Table                         : rtable-u

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

----------------------------------------------
*B:BB>config>service>vprn>pim# no mc-ecmp-balance mc-ecmp-balance mc-ecmp-balance-
hold
*B:BB>config>service>vprn>pim# no mc-ecmp-balance 
*B:BB>config>service>vprn>pim# mc-ecmp-mc-ecmp-balance mc-ecmp-balance-hold mc-ecmp-
hashing-enabled
*B:BB>config>service>vprn>pim# mc-ecmp-hashing-enabled
*B:BB>config>service>vprn>pim# info
----------------------------------------------
                apply-to all
                rp
                    static
                        address 10.3.3.3
                            group-prefix 224.0.0.0/4
                        exit
                    exit
                    bsr-candidate
                        shutdown
                    exit
                    rp-candidate
                        shutdown
                    exit
                exit
                no mc-ecmp-balance
                mc-ecmp-hashing-enabled
----------------------------------------------
*B:BB>config>service>vprn>pim#
apply-to        - Create/remove interfaces in PIM
 [no] import          - Configure import policies
 [no] interface       + Configure PIM interface
 [no] mc-ecmp-balance - Enable/
Disable multicast balancing of traffic over ECMP links
 [no] mc-ecmp-balanc* - Configure hold time for multicast balancing over ECMP links
 [no] mc-ecmp-hashin* - Enable/
Disable hash based multicast balancing of traffic over ECMP links
 [no] non-dr-attract* - Enable/disable attracting traffic when not DR
      rp              + Configure the router as static or Candidate-RP
 [no] shutdown        - Administratively enable or disable the operation of PIM 
 [no] spt-switchover* -
 Configure shortest path tree (spt tree) switchover threshold for a group prefix
 [no] ssm-default-ra* - Enable the disabling of SSM Default Range
 [no] ssm-groups      + Configure the SSM group ranges
Distribution output of PIM joins over multiple ECMP paths
*A:BA# show router 100 pim group

===============================================================================
PIM Groups ipv4
===============================================================================
Group Address                           Type     Spt Bit Inc Intf       No.Oifs
   Source Address                          RP
-------------------------------------------------------------------------------
239.1.1.1                               (S,G)    spt     to_C0          1
   172.0.100.33                            10.20.1.6
239.1.1.2                               (S,G)    spt     to_C3          1
   172.0.100.33                            10.20.1.6
239.1.1.3                               (S,G)    spt     to_C2          1
   172.0.100.33                            10.20.1.6
239.1.1.4                               (S,G)    spt     to_C1          1
   172.0.100.33                            10.20.1.6
239.1.1.5                               (S,G)    spt     to_C0          1
   172.0.100.33                            10.20.1.6
239.1.1.6                               (S,G)    spt     to_C3          1
   172.0.100.33                            10.20.1.6

239.2.1.1                               (S,G)    spt     to_C0          1
   172.0.100.33                            10.20.1.6
239.2.1.2                               (S,G)    spt     to_C3          1
   172.0.100.33                            10.20.1.6
239.2.1.3                               (S,G)    spt     to_C2          1
   172.0.100.33                            10.20.1.6
239.2.1.4                               (S,G)    spt     to_C1          1
   172.0.100.33                            10.20.1.6
239.2.1.5                               (S,G)    spt     to_C0          1
   172.0.100.33                            10.20.1.6
239.2.1.6                               (S,G)    spt     to_C3          1
   172.0.100.33                            10.20.1.6

239.3.1.1                               (S,G)    spt     to_C0          1
   172.0.100.33                            10.20.1.6
239.3.1.2                               (S,G)    spt     to_C3          1
   172.0.100.33                            10.20.1.6
239.3.1.3                               (S,G)    spt     to_C2          1
   172.0.100.33                            10.20.1.6
239.3.1.4                               (S,G)    spt     to_C1          1
   172.0.100.33                            10.20.1.6
239.3.1.5                               (S,G)    spt     to_C0          1
   172.0.100.33                            10.20.1.6
239.3.1.6                               (S,G)    spt     to_C3          1
   172.0.100.33                            10.20.1.6

239.4.1.1                               (S,G)    spt     to_C0          1
   172.0.100.33                            10.20.1.6
239.4.1.2                               (S,G)    spt     to_C3          1
   172.0.100.33                            10.20.1.6
239.4.1.3                               (S,G)    spt     to_C2          1
   172.0.100.33                            10.20.1.6
239.4.1.4                               (S,G)    spt     to_C1          1
   172.0.100.33                            10.20.1.6
239.4.1.5                               (S,G)    spt     to_C0          1
   172.0.100.33                            10.20.1.6
239.4.1.6                               (S,G)    spt     to_C3          1
   172.0.100.33                            10.20.1.6
-------------------------------------------------------------------------------
Groups : 24
===============================================================================

MSDP

Multicast Source Discovery Protocol (MSDP) defines a protocol to exchange information about multicast sources across multiple PIM-SM domains. MSDP-speaking routers in a PIM-SM domain have an MSDP peering relationship with the MSDP-speaking peer in another 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 rendezvous point (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.

The SA message is flooded (after a reverse path forwarding (RPF) check) 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 state for the source and joins to 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 may also join the shortest path tree to the source.

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

Anycast RPs for MSDP

MSDP provides a mechanism that allows RPs to share information about active sources. When RPs in remote domains learn about the active sources, they pass on that information to the local receivers and multicast data is forwarded between the domains. MSDP allows each domain to maintain an independent RP that does not rely on other domains but 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 themselves with their local RP and this registration is performed by the closest multicast router to which the source and receiver are connected. The RP maintains information about the sources and receivers for a specific group. RPs in other domains do not have any knowledge about sources located in other domains.

MSDP is required to provide inter-domain multicast services using Any Source Multicast (ASM). Anycast RP for MSDP enables fast convergence when should an MSDP/PIM PR router fail 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 SA messages for directly-connected sources on that shared network. It only originates SA messages in response to a register message received from the designated router.

Each MSDP peer receives and forwards the message away from the RP address in a peer-RPF flooding fashion. The notion of peer-RPF flooding is with respect to forwarding SA messages. The Multicast RPF Routing Information Base (MRIB) is examined to determine which peer toward the originating RP of the SA message is selected. Such a peer is called an RPF peer.

If the MSDP peer receives the SA message from a non-RPF peer toward the originating RP, it drops the message. Otherwise, it forwards the message to all its MSDP peers (except the peer 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 in 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 a system 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 and 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 SA cache.

This procedure is called flood-and-join because if an RP in the domain is not interested in the group, the SA message can be ignored when there are no receivers or members interested in that domain; otherwise, the RP joins a distribution tree.

MSDP peering scenarios

The draft-ietf-mboned-msdp-deploy-nn.txt, Multicast Source Discovery Protocol (MSDP) Deployment Scenarios describes how protocols work together to provide intra- and inter-domain ASM service.

The following inter-domain peering scenarios are supported for ASM services:

  • 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

The following intra-domain peering scenarios are supported for ASM services:

  • peering between routers configured for both MSDP and MBGP

  • MSDP peer is not BGP peer (meaning, no BGP peer)

MSDP peer groups

MSDP peer groups are typically created when multiple peers have a set of common operational parameters. Group parameters 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 several 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. Because of this, forwarding the SA 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 the following levels:

  • global level

    This level applies to all peers.

  • group level

    This level applies to all peers in a peer group.

  • neighbor level

    This level applies only to 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, source active messages are passed.

Match conditions include:

  • neighbor

    This condition matches on a neighbor address is the source address in the IP header of the source active message.

  • route filter

    This condition matches on a multicast group address embedded in the source active message.

  • source address filter

    This condition matches on a multicast source address embedded in the source active message.

Draft-Rosen multicast in VPNs

RFC 4364, BGP/MPLS IP Virtual Private Networks (VPNs), describes a method of providing a VPN service, which secures connections to the network, allowing more efficient service to remote users without compromising the security of firewalls. The Rosen draft specifies the protocols and procedures that must be implemented for a service provider to provide a unicast VPN. The draft extends that specification by describing the protocols and procedures that a service provider must implement to support multicast traffic in a VPN.

See the ‟Virtual Private Routed Network Service” section of the 7210 SAS-Mxp, S, Sx, T Services Guide for more information.

Dynamic multicast signaling over P2MP LDP

This feature provides a flexible multicast signaling solution to connect native IP multicast source and receivers that are running PIM multicast protocol via an intermediate MPLS (P2MP LDP LSP) network. It allows each native IP multicast flow to be connected via an intermediate P2MP LSP by dynamically mapping each PIM multicast flow to a P2MP LDP LSP.

It is not required to manually configure a mapping of (S,G) to a P2MP LSP on the edge node of MPLS network. A signaling method is defined that allows dynamic mapping of PIM signaling to P2MP LDP tree setup on the leaf node of P2MP LSP and also P2MP LDP signaling to be handed back to PIM on root node of P2MP LSP. Because of dynamic mapping of multicast IP flow to P2MP LSP, provisioning and maintenance overhead is eliminated as multicast distribution services are added and removed from the network.

P2MP LDP LSP signaling is initiated from node that receives PIM JOIN from a downstream node. The p2mp-ldp-tree-join command must be configured on PIM outgoing interface that received PIM JOIN to enable handover of multicast tree signaling from PIM to P2MP LDP LSP.

Leaf node of P2MP LDP LSP selects the upstream-hop as the root node of LDP FEC based on route table lookup. On the root node of P2MP LDP LSP, multicast tree signaling is handed back to PIM and propagated upstream as native-IP PIM JOIN.

Only PIM-SSM is supported with this feature. A single instance of P2MP LDP LSP is supported between the root and leaf nodes per multicast flow, that is, no stitching of dynamic trees.

If multiple criteria exist to set up a multicast flow, the following priorities are:

  1. Multicast (statically provisioned) over P2MP LSP (RSVP-TE or LDP)

  2. Dynamic multicast signaling over P2MP LDP

  3. PIM native-IP multicast

Multicast debugging tools

This section describes multicast debugging tools for the 7210 SAS.

The debugging tools for multicast consist of two elements: mtrace and mrinfo.

Mtrace

Assessing problems in the distribution of IP multicast traffic can be difficult. The 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

  • Fowarding/error code

The information enables the network administrator to determine the following:

  • Where multicast flows stop

  • The flow of the multicast stream

When the trace response packet reaches the first-hop router (the router that is directly connected to the source 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 traceroute feature or if there is an outage, 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, flags to indicate routing errors, and 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, which is the last hop on the path from the source to the receiver. If the receiver is on the local subnet (as determined using the subnet mask), the default method is to multicast 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 because 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 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 wanted interface for the path from the source. In such cases, the wanted interface should be specified explicitly as the receiver.

Directing the response

Unless the number of hops to trace is explicitly set with the hop option, mtrace first attempts to trace the full reverse path by default. If there is no response within a 3 second 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 multicast 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 final 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 printed. After the specified number of attempts have failed, mtrace tries to query the next hop router with a DVMRP_ASK_NEIGHBORS2 request (as used by the mrinfo program) to determined 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 the time the query is issued until the response is received, both derived from the local system clock.

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

Mrinfo

The mrinfo feature is a simple mechanism to display 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 to verify if bidirectional adjacencies exist. When the specified multicast router responds, the configuration is displayed.

Configuration guidelines for 7210 SAS

The following are the configuration guidelines for 7210 SAS:

  • On 7210 SAS devices, on ingress of a port, multicast traffic can be processed in the context of either igmp-snooping (Layer 2 Ethernet multicast) or l3-multicast (Layer 3 multicast), but not both. It is not possible to configure SAPs on the port such that one SAP is a receiver for multicast traffic that is processed by IGMP snooping, and the other is the receiver for multicast traffic that is processed by IP multicast in the context of Layer 3 service or RVPLS. An option per port (using the configure>port>ethernet>multicast-ingress {l2-mc | ip-mc} command) is available to enable one or the other. By default, backward compatibility is enabled for IGMP snooping. To allow processing of received multicast traffic as IP multicast in the context of Layer 3 service or RVPLS, the user must explicitly change the default by using the configure>port>ethernet>multicast-ingress command. For more information about the command, see the 7210 SAS-Mxp, R6, R12, S, Sx, T Interface Configuration Guide.

  • On 7210 SAS devices in network mode, on egress of a port, users have an option to configure Layer 2 or Layer 3 multicast replication. That is, with RVPLS IGMPv3 snooping-based multicast, a port on which receivers are present can be configured to do either Layer 2 multicast replication—where IP TTL is not decremented and the source MAC address is not replaced with the 7210 SAS chassis MAC or IP interface MAC address—or Layer 3 multicast replication—where IP TTL is decremented and the source MAC address is replaced. Users have an option to modify this with the configure>port>ethernet>multicast-egress command. For more information about the command, see the 7210 SAS-Mxp, R6, R12, S, Sx, T Interface Configuration Guide.

  • If a VPLS SAP is configured on the port that has IP multicast enabled, then multicast traffic received on the SAP is dropped. Unicast, Broadcast and unknown-unicast packets received on the SAP are forwarded appropriately. This behavior is true only for VPLS SAPs and does not apply to VPLS SDPs, Epipe SAPs, and Epipe SDPs.

  • 7210 SAS platforms can be used as RPs.

  • Static RP configuration and automatic RP discovery using PIM BSR messages is supported. 7210 SAS-R6 or 7210 SAS-R12 platforms can be configured as candidate RP (or candidate BSR).

  • It is possible to configure the 7210 SAS as a First Hop Multicast router (FHR) from the source in a PIM-SM network.

  • 7210 SAS devices provide an option to either switch over to the SPT or continue to use the share tree. However, the traffic rate threshold cannot be configured to trigger the switch over.

  • There is no hardware support for LAG hashing of replicated multicast traffic on 7210 SAS-R6 and 7210 SAS-R12 for IES access interfaces configured on a LAG. On these platforms, to egress on IES access interfaces, software assigns multicast traffic to the member ports of the LAG based on system-defined hash logic. LAG hashing is supported by hardware for multicast traffic on 7210 SAS-T, 7210 SAS-Mxp, 7210 SAS-Sx/S 1/10GE, 7210 SAS-Sx 10/100GE, and on network port interfaces for 7210 SAS-R6 and 7210 SAS-R12.

  • RFP check are performed using the unicast routing table. Multicast BGP and multicast routing table are not supported.

Configuring multicast parameters with CLI

This section provides information to configure multicast, IGMP, PIM, and MSDP.

Multicast configuration overview

7210 SAS routers use IGMP to manage membership for a specific multicast session. IGMP is not enabled by default. The IGMP context is not operational until at least one IGMP interface is specified in the context, at which time the interface is enabled for IGMP.

Traffic can only flow away from the router to an IGMP interface, and to and from a PIM interface. A router directly connected to a source must have PIM enabled on the interface to that source. In a network, traffic travels from PIM interface to PIM interface, and arrives on an IGMP-enabled interface.

The IGMP CLI context allows you to specify an existing IP interface, and modify the interface-specific parameters. Static IGMP group memberships can be configured to test multicast forwarding without a receiver host. When IGMP static group membership is enabled, data is forwarded to an interface without receiving membership reports from host members.

When static IGMP group entries on point-to-point links that connect routers to a rendezvous point (RP) are configured, the static IGMP group entries do not generate join messages toward the RP. When a host needs to receive multicast sessions, it sends a join message for each multicast group it needs to join. Then, a leave message may be sent for each multicast group it no longer wants to participate with.

A multicast router keeps a list of multicast group memberships for each attached network, and an interval timer for each membership. Hosts issue a Multicast Group Membership Report when they want to receive a multicast session. The reports are sent to all multicast routers.

PIM is not enabled by default. Because it is an interface function, PIM is not operational until at least one interface is specified in the PIM context, at which time the interface is enabled for PIM. When PIM is enabled, data is forwarded to network segments with active receivers that have explicitly requested the multicast group.

Basic configuration

Perform the following basic multicast configuration tasks:

  • For IGMP:

    • enable IGMP (required)

    • configure IGMP interfaces (required)

    • specify the IGMP version on the interface (optional)

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

    • configure SSM translation (optional)

  • For PIM:

    • enable PIM (required)

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

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

      • using static group-to-RP mapping

      • enabling the candidate RP/bootstrap mechanism on some routers

    • enable unicast routing protocols to learn routes toward the RP/source for reverse path forwarding (required)

    • add SSM ranges (optional)

    • enable Candidate BSR (optional)

    • enable Candidate RP (optional)

    • change the hello interval (optional)

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

  • For MSDP:

    • enable MSDP (required)

    • configure peer

    • configure local address

Enabled IGMP, PIM, and MSDP configuration output

A:LAX>config>router>igmp# info
----------------------------------------------
interface "lax-vls"
exit
interface "p1-ix"
exit
----------------------------------------------
A:7210SAS>config>router>igmp# info detail
----------------------------------------------
        interface "lax-vls"
            no import
            version 3
            no shutdown
        exit
        interface "p1-ix"
            no import
            version 3
            no shutdown
        exit
        query-interval 125
        query-last-member-interval 1
        query-response-interval 10
        robust-count 2
        no shutdown
----------------------------------------------
A:7210SAS>config>router>igmp# exit
A:7210SAS>config>router# pim
A:7210SAS>config>router>pim# info
----------------------------------------------
            interface "lax-vls"
            exit
            interface "lax-vls"
            exit
            interface "lax-sjc"
            exit
            interface "p1-ix"
            exit
            rp
                static
                    address 239.22.187.237
                        group-prefix 239.24.24.24/32
                    exit
                exit
                    shutdown
bsr-candidate
                exit
                rp-candidate
                    shutdown
                exit
            exit
----------------------------------------------
A:7210SAS>config>router>pim# info detail
----------------------------------------------
            no import join-policy
            no import register-policy
            interface "system"
                priority 1
                hello-interval 30
                multicast-senders auto
                no tracking-support
                no shutdown
            exit
            interface "lax-vls"
                priority 1
                hello-interval 30
                multicast-senders auto
                no tracking-support
                no shutdown
            exit
            interface "lax-sjc"
                priority 1
                hello-interval 30
                multicast-senders auto
                no tracking-support
                no shutdown
            exit
            interface "p1-ix"
                priority 1
                hello-interval 30
                multicast-senders auto
                no tracking-support
                no shutdown
            exit
            apply-to none
            rp
                no bootstrap-import
                no bootstrap-export
                static
                    address 239.22.187.237
                        no override
                        group-prefix 239.24.24.24/32
                    exit
                exit
                    shutdown
                    priority 0
                    hash-mask-len 30
                    no address
                exit
                rp-candidate
                    shutdown
bsr-candidate
                    no address
                    holdtime 150
                    priority 192
                exit
            exit
            no shutdown
----------------------------------------------
A:7210SAS>config>router>pim#
*A:Dut-B>config>router>msdp# info 
----------------------------------------------
            peer 10.20.1.6
                local-address 10.20.1.1
            exit
            group "msdpgroup"
                peer 10.20.1.4
                    local-address 10.20.1.1
                exit
                peer 10.20.1.5
                    local-address 10.20.1.1
                exit
            exit
----------------------------------------------
*A:Dut-B>config>router>msdp# info detail 
----------------------------------------------
            no active-source-limit
            no receive-msdp-msg-rate
            data-encapsulation
            no export
            no import
            no local-address
            no rpf-table
            no sa-timeout
            no shutdown
            peer 10.20.1.6
                no active-source-limit
                no receive-msdp-msg-rate
                no authentication-key
                no default-peer
                no export
                no import
                local-address 10.20.1.1
                no shutdown
            exit
            group "msdpgroup"
                no active-source-limit
                no receive-msdp-msg-rate
                no export
                no import
                no local-address
                mode standard
                no shutdown
                peer 10.20.1.4
                    no active-source-limit
                    no receive-msdp-msg-rate
                    no authentication-key
                    no default-peer
                    no export
                    no import
                    local-address 10.20.1.1
                    no shutdown
                exit
                peer 10.20.1.5
                    no active-source-limit
                    no receive-msdp-msg-rate
                    no authentication-key
                    no default-peer
                    no export
                    no import
                    local-address 10.20.1.1
                    no shutdown
                exit
            exit
----------------------------------------------

Common configuration tasks

The following sections describe basic multicast configuration tasks.

Configuring IGMP parameters

This section provides information to configure IGMP parameters.

Enabling IGMP

Use the following syntax to enable IGMP. 

config>router# igmp
Detailed output for an enabled IGMP
A:7210SAS>>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:7210SAS>>config>system#

Configuring an IGMP interface

Use the following syntax to configure an IGMP interface.

config>router# igmp
    interface ip-int-name
    max-groups value
    import policy-name
    version version
    no shutdown

Use the following syntax to configure IGMP interfaces.

config>router#
    config>router>igmp# interface "lax-vls" 
    config>router>igmp>if? no shutdown
    config>router>igmp>if# exit
    config>router>igmp# interface "p1-ix" 
    config>router>igmp>if? no shutdown
    config>router>igmp>if# exit
    config>router>igmp# interface "lax-sjc" 
    config>router>igmp>if? no shutdown
    config>router>igmp>if# exit
IGMP configuration output
A:7210SAS>config>router>igmp# info
----------------------------------------------
        interface "lax-sjc"
        exit
        interface "lax-vls"
        exit
        interface "p1-ix"
        exit
----------------------------------------------
A:7210SAS>config>router>igmp# exit

Configuring static parameters

Use the following syntax to add an IGMP static multicast source.

 config>router# igmp
    interface ip-int-name
    no shutdown
    static
        group grp-ip-address
            source ip-address

The following shows the command usage to configure static group addresses and source addresses for the SSM translate group ranges. 

config>router>igmp# interface lax-vls
    config>router>igmp>if# static
    config>router>igmp>if>static# group 239.255.0.2
    config>router>igmp>if>static>group#  source 172.22.184.197
    config>router>igmp>if>static>group# exit
    config>router>igmp>if>static# exit
    config>router>igmp>if# exit
Configuration output
A:LAX>config>router>igmp# info
----------------------------------------------
        interface "lax-sjc"
        exit
        interface "lax-vls"
            static
                group 239.255.0.2
                    source 172.22.184.197
                exit
            exit
        exit
        interface "p1-ix"
        exit
----------------------------------------------
A:LAX>config>router>igmp#

Use the following syntax to add an IGMP static starg entry.

config>router# igmp
    interface ip-int-name
    no shutdown
    static
        group grp-ip-address
            starg

The following shows the command usage to configure static group addresses and add a static (*,G) entry.

config>router>igmp# interface lax-sjc
    config>router>igmp>if# static
    config>router>igmp>if>static# group 239.1.1.1
    config>router>igmp>if>static>group# starg
    config>router>igmp>if>static>group# exit
    config>router>igmp>if>static# exit
    config>router>igmp>if# exit
    config>router>igmp#
Configuration output
A:LAX>config>router>igmp# info
----------------------------------------------
        interface "lax-sjc"
            static
                group 239.1.1.1
                    starg
                exit
            exit
        exit
        interface "lax-vls"
            static
                group 239.255.0.2
                    source 172.22.184.197
                exit
            exit
        exit
        interface "p1-ix"
        exit
----------------------------------------------
A:LAX>config>router>igmp#

Configuring SSM translation

Use the following syntax to configure IGMP parameters.

config>router# igmp
    ssm-translate
    grp-range start end
        source ip-address

The following shows the command usage to configure IGMP parameters.

config>router# igmp
    config>router>igmp# ssm-translate
    config>router>igmp>ssm# grp-range 239.255.0.1 239.2.2.2
    config>router>igmp>ssm>grp-range# source 10.1.1.1
SSM translation configuration output
A:LAX>config>router>igmp# info
----------------------------------------------
        ssm-translate
            grp-range 239.255.0.1 239.2.2.2
                source 10.1.1.1
            exit
        exit
        interface "lax-sjc"
            static
                group 239.1.1.1
                    starg
                exit
            exit
        exit
        interface "lax-vls"
            static
                group 239.255.0.2
                    source 172.22.184.197
                exit
            exit
        exit
        interface "p1-ix"
        exit
----------------------------------------------
A:LAX>config>router>igmp# exit

Configuring PIM parameters

The following section describes the syntax used to configure the PIM parameters.

Enabling PIM

PIM must be enabled on all interfaces for the routing instance; failure to do so may result in multicast routing errors.

Use the following syntax to enable PIM. 

config>router# pim
Detailed output of an enabled PIM
A:LAX>>config>router# info detail
...
#------------------------------------------
echo "PIM Configuration"
#------------------------------------------
        pim
            no import join-policy
            no import register-policy
            apply-to none
            rp
                no bootstrap-import
                no bootstrap-export
                static
                exit
                    shutdown
                    priority 0
                    hash-mask-len 30
                    no address
                exit
                rp-candidate
                    shutdown
                    no address
                    holdtime 150
                    priority 192
                exit
            exit
            no shutdown
        exit
#------------------------------------------
...
A:LAX>>config>system#

Configuring PIM interface parameters

Command usage to configure PIM interface parameters
A:LAX>config>router# pim
    A:LAX>config>router>pim# interface "system" 
    A:LAX>config>router>pim>if# exit
    A:LAX>config>router>pim# interface "lax-vls" 
    A:LAX>config>router>pim>if# exit
    A:LAX>config>router>pim# interface "lax-sjc" 
    A:LAX>config>router>pim>if# exit
    A:LAX>config>router>pim# interface "p1-ix" 
    A:LAX>config>router>pim>if# exit
    A:LAX>config>router>pim# rp
    A:LAX>config>router>pim>rp# static
    A:LAX>config>router>pim>rp>static# address 239.22.187.237
    A:LAX>config>router>..>address# group-prefix 239.24.24.24/32
    A:LAX>config>router>pim>rp>static>address# exit
    A:LAX>config>router>pim>rp>static# exit
    A:LAX>config>router>pim>rp# exit
PIM configuration output
A:LAX>config>router>pim# info
----------------------------------------------
            interface "system"
            exit
            interface "lax-vls"
            exit
            interface "lax-sjc"
            exit
            interface "p1-ix"
            exit
            rp
                static
                    address 239.22.187.237
                        group-prefix 239.24.24.24/32
                    exit
                    address 10.10.10.10
                    exit
                exit
                    shutdown
bsr-candidate
                exit
                rp-candidate
                    shutdown
                exit
            exit
----------------------------------------------
A:LAX>config>router>pim#


A:SJC>config>router# pim
    A:SJC>config>router>pim# interface "system" 
    A:SJC>config>router>pim>if# exit
    A:SJC>config>router>pim# interface "sjc-lax" 
    A:SJC>config>router>pim>if# exit
    A:SJC>config>router>pim# interface "sjc-nyc" 
    A:SJC>config>router>pim>if# exit
    A:SJC>config>router>pim# interface "sjc-sfo" 
    A:SJC>config>router>pim>if# exit
    A:SJC>config>router>pim# rp
    A:SJC>config>router>pim>rp# static
    A:SJC>config>router>pim>rp>static# address 239.22.187.237
    A:SJC>config>router>pim>rp>static>address# group-prefix 239.24.24.24/32
    A:SJC>config>router>pim>rp>static>address# exit
    A:SJC>config>router>pim>rp>static# exit
    A:SJC>config>router>pim>rp# exit
    A:SJC>config>router>pim# 

A:SJC>config>router>pim# info
----------------------------------------------
            interface "system"
            exit
            interface "sjc-lax"
            exit
            interface "sjc-nyc"
            exit
            interface "sjc-sfo"
            exit
            rp
                static
                    address 239.22.187.237
                        group-prefix 239.24.24.24/32
                    exit
                exit
                    shutdown
bsr-candidate
                exit
                rp-candidate
                    shutdown
                exit
            exit
----------------------------------------------
A:SJC>config>router>pim#

A:MV>config>router# pim
    A:MV>config>router>pim# interface "system" 
    A:MV>config>router>pim>if# exit
    A:MV>config>router>pim# interface "mv-sfo" 
    A:MV>config>router>pim>if# exit
    A:MV>config>router>pim# interface "mv-v1c" 
    A:MV>config>router>pim>if# exit
    A:MV>config>router>pim# interface "p3-ix" 
    A:MV>config>router>pim>if# exit
    A:MV>config>router>pim# rp
    A:MV>config>router>pim>rp# static
    A:MV>config>router>pim>rp>static# address 239.22.187.237
    A:MV>config>router>pim>rp>static>address# group-prefix 239.24.24.24/32
    A:MV>config>router>pim>rp>static>address# exit
    A:MV>config>router>pim>rp>static#
    A:MV>config>router>pim>rp# exit
    A:MV>config>router>pim# 

A:MV>config>router>pim# info
----------------------------------------------
            interface "system"
            exit
            interface "mv-sfo"
            exit
            interface "mv-vlc"
            exit
            interface "p3-ix"
            exit
            rp
                static
                    address 239.22.187.237
                        group-prefix 239.24.24.24/32
                    exit
                exit
                    address 239.22.187.236
                    no shutdown
                exit
                rp-candidate
                    address 239.22.187.236
                    no shutdown
bsr-candidate
                exit
            exit
----------------------------------------------
A:MV>config>router>pim#

A:SFO>config>router# pim
    A:SFO>config>router>pim# interface "system" 
    A:SFO>config>router>pim>if# exit
    A:SFO>config>router>pim# interface "sfo-sfc" 
    A:SFO>config>router>pim>if# exit
    A:SFO>config>router>pim# interface "sfo-was" 
    A:SFO>config>router>pim>if# exit
    A:SFO>config>router>pim# interface "sfo-mv" 
    A:SFO>config>router>pim>if# exit
    A:SFO>config>router>pim# rp
    A:SFO>config>router>pim>rp# static
    A:SFO>config>router>pim>rp>static# address 239.22.187.237
    A:SFO>config>router>pim>rp>static>address# group-prefix 239.24.24.24/32
    A:SFO>config>router>pim>rp>static>address# exit
    A:SFO>config>router>pim>rp>static# exit
    A:SFO>config>router>pim>rp # exit
    A:SFO>config>router>pim# 
A:SFO>config>router>pim# info
----------------------------------------------
            interface "system"
            exit
            interface "sfo-sjc"
            exit
            interface "sfo-was"
            exit
            interface "sfo-mv"
            exit
            rp
                static
                    address 239.22.187.237
                        group-prefix 239.24.24.24/32
                    exit
                exit
                    address 239.22.187.239
                    no shutdown
                exit
                rp-candidate
                    address 239.22.187.239
                    no shutdown
bsr-candidate
                exit
            exit
----------------------------------------------
A:SFO>config>router>pim#

A:WAS>config>router# pim
    A:WAS>config>router>pim# interface "system" 
    A:WAS>config>router>pim>if# exit
    A:WAS>config>router>pim# interface "was-sfo" 
    A:WAS>config>router>pim>if# exit
    A:WAS>config>router>pim# interface "was-vlc" 
    A:WAS>config>router>pim>if# exit
    A:WAS>config>router>pim# interface "p4-ix" 
    A:WAS>config>router>pim>if# exit
    A:WAS>config>router>pim# rp
    A:WAS>config>router>pim>rp# static
    A:WAS>config>router>pim>rp>static# address 239.22.187.237
    A:WAS>config>router>pim>rp>static>address# group-prefix 239.24.24.24/32
    A:WAS>config>router>pim>rp>static>address# exit
    A:WAS>config>router>pim>rp>static# exit
    A:WAS>config>router>pim>rp# exit
    A:WAS>config>router>pim#

A:WAS>config>router>pim# info
----------------------------------------------
            interface "system"
            exit
            interface "was-sfo"
            exit
            interface "was-vlc"
            exit
            interface "p4-ix"
            exit
            rp
                static
                    address 239.22.187.237
                        group-prefix 239.24.24.24/32
                    exit
                exit
                    address 239.22.187.240
                    no shutdown
                exit
                rp-candidate
                    address 239.22.187.240
                    no shutdown
bsr-candidate
                exit
            exit
----------------------------------------------
A:WAS>config>router>pim#

Importing PIM join or register policies

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

Note:

In the import policy, if a policy action is not specified in the entry, the default-action takes precedence. In the same way, 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 syntax to configure PIM parameters.

config>router# pim 
    import {join-policy|register-policy} [policy-name 
[.. policy-name]

The following shows the command usage to apply the policy statement, which does not allow join messages for group 229.50.50.208/32 and source 192.168.0.0/16, but allows join messages for 192.168.0.0/16, 229.50.50.208 (see Configuring route policy components).

config>router# pim
    config>router>pim# import join-policy "foo"
    config>router>pim# no shutdown
PIM configuration output
A:LAX>config>router>pim# info
----------------------------------------------
            import join-policy "foo"
            interface "system"
            exit
            interface "lax-vls"
            exit
            interface "lax-sjc"
            exit
            interface "p1-ix"
            exit
            rp
                static
                    address 239.22.187.237
                        group-prefix 239.24.24.24/3
                    exit
                    address 10.10.10.10
                    exit
                exit
                    shutdown
                exit
                rp-candidate
                    shutdown
                exit
            exit
----------------------------------------------
A:LAX>config>router>pim#

Configuring MSDP parameters

Use the following commands to configure basic MSDP parameters. 

config>router# msdp 
        peer ip-address 
            active-source-limit number 
            authentication-key [authentication-key | hash-key]  [hash | hash2 | custom] 
            default-peer 
            export policy-name [policy-name] 
            import policy-name [policy-name] 
            local-address ip-address 
            receive-msdp-msg-rate number interval seconds [threshold threshold] 
            no shutdown 
        no shutdown

Use the following CLI syntax to configure MSDP parameters. 

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#

Displaying the MSDP configuration

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

Disabling IGMP or PIM

Use the following syntax to disable IGMP and PIM.

config>router# 
    igmp
    shutdown
    pim
    shutdown

Command usage to disable multicast

config>router# igmp
    config>router>igmp# shutdown
    config>router>igmp# exit
    config>router#
    config>router# pim
    config>router>pim# shutdown
    config>router>pim# exit

Configuration output

A:LAX>config>router# info
----------------------------------------------
...
#------------------------------------------
echo "IGMP Configuration"
#------------------------------------------
        igmp
            shutdown
            ssm-translate
                grp-range 239.255.0.1 239.2.2.2
                    source 10.1.1.1
                exit
            exit
            interface "lax-sjc"
                static
                    group 239.1.1.1
                        starg
                    exit
                exit
            exit
            interface "lax-vls"
                static
                    group 239.255.0.2
                        source 172.22.184.197
                    exit
                exit
            exit
            interface "p1-ix"
            exit
        exit
#------------------------------------------

echo "PIM Configuration"
#------------------------------------------
        pim
            shutdown
            import join-policy "foo"
            interface "system"
            exit
            interface "lax-sjc"
            exit
            interface "lax-vls"
            exit
            interface "p1-ix"
            exit
            rp
                static
                    address 239.22.187.237
                        group-prefix 239.24.24.24/32
                    exit
                    address 10.10.10.10
                    exit
                exit
                    shutdown
                exit
                rp-candidate
                    shutdown
bsr-candidate
                exit
            exit
        exit
#------------------------------------------
....
------------------------------------------
A:LAX>config>router#

Disabling MSDP

Use the following CLI syntax to disable MSDP. 

config>router# 
        msdp 
            shutdown

Command usage to disable multicast

config>router# 
    config>router>msdp# shutdown 
    config>router>msdp# exit

Configuration output

A:LAX>config>router# info
----------------------------------------------
...
#------------------------------------------
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
#--------------------------------------------------

Multicast command reference

Command hierarchies

IGMP commands

config
    - 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-sources [1..1000]
                - no max-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] starg
                - [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

PIM commands

config
    - router
        - [no] pim
            - [no] enable-mdt-spt
            - 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]
                - hello-interval hello-interval
                - no hello-interval
                - hello-multiplier deci-units
                - no hello-multiplier
                - [no] improved-assert
                - [no] instant-prune-echo
                - max-groups value
                - no max-groups
                - multicast-senders {auto | always | never}
                - no multicast-senders
                - priority dr-priority
                - no priority
                - [no] shutdown
                - sticky-dr [priority dr-priority]
                - no sticky-dr
                - three-way-hello [compatibility-mode]
                - no three-way-hello
                - [no] tracking-support
            - [no] mc-ecmp-balance
            - mc-ecmp-balance-hold minutes
            - no mc-ecmp-balance-hold
            - [no] mc-ecmp-hashing-enabled
        - [no] non-dr-attract-traffic
            - rp
                - [no] anycast rp-ip-address
                    - [no] rp-set-peer ip-address
                - 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 ip-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
            - no] rpf-table {rtable-u}
            - [no] shutdown
            - spt-switchover-threshold {grp-ipv4-prefix/ipv4-prefix-length | grp-ipv4-prefix netmask} spt-threshold
            - ssm-assert-compatible-mode [enable | disable]
            - ssm-default-range-disable ipv4
            - no ssm-default-range-disable ipv4
            - [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 ip-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 ip-address 
                    - no local-address 
                    - receive-msdp-msg-rate number interval seconds [threshold threshold]  
                    - no receive-msdp-msg-rate 
                    - [no] shutdown 
                - receive-msdp-msg-rate number interval seconds [threshold threshold]  
                - no receive-msdp-msg-rate 
                - [no] shutdown 
            - import policy-name [policy-name...(up to 5 max)] 
            - no import 
            - local-address ip-address 
            - no local-address 
            - [no] peer ip-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] 
                - no export 
                - import policy-name [policy-name] 
                - no import 
                - local-address ip-address 
                - no local-address 
                - receive-msdp-msg-rate number interval seconds [threshold threshold]  
                - no receive-msdp-msg-rate 
                - [no] shutdown 
            - receive-msdp-msg-rate number interval seconds [threshold threshold] 
            - 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 prefix/mask  
                - active-source-limit number 
                - no active-source-limit

Operational commands

<GLOBAL>

    - mrinfo ip-address | dns-name [router router-instance | service-name service-name] 
    - mtrace source ip-address | dns-name [group ip-address | dns-name] [destination ip-address | dns-name] [hop hop] [router router-instance> | service-name service-name] [wait-time wait-time]

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-addr]
            - statistics [ip-int-name | ip-address]
            - status
show
    - router
        - pim
            - anycast [family] [detail]
            - crp [family | ip-address]
            - group [grp-ip-address] [source ip-address] [type {starstarrp | starg | sg}] [detail] [family]
            - interface [ip-int-name | int-ip-address] [group [group-ip-address] source ip-address] [type {starstarrp | starg | sg}] [detail] [family] 
            - mc-ecmp-balance
            - neighbor [ip-address | ip-int-name [address neighbor-ip-address]] [detail] [family]
            - rp [family | ip-address]
            - rp-hash ip-address
            - s-pmsi [group-ip group-ip]source-ip source- ip] [detail]
            - s-pmsi [mdSrcAddr [mdGrpAddr]] [group-ip group-ip] [source-ip source- ip] [detail]
            - s-pmsi ext-tunnel-id ext-tunnel-id [tunnel-id tunnel-id [group-ip group-ip] [source-ip source- ip] [detail]
            - s-pmsi root-addr root-addr [lsp-idlsp-id] [group-ip group-ip] [source-ip source- ip] [detail]
            - statistics [ip-int-name | int-ip-address | mpls-if-name] [family]
            - status [detail] [family]
            - tunnel-interface [ip-int-name | mt-int-name | int-ip-address] [group [group-ip-address] source ip-address] [type {starstarrp | starg | sg}] [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
show
    - router {router-instance}
        - mvpn
        - mvpn-list
show
    - router
        - tunnel-table [ip-address [/mask]] [protocol | sdp sdp-id]
        - tunnel-table [summary]

Clear commands

clear
    - router
        - igmp
            - database [interface ip-int-name|ip-address] group grp-ip-address [source src-ip-address]
            - database [group grp-ip-address [source src-ip-address]]
            - statistics [interface ip-int-name | ip-address]
            - version [interface ip-int-name | ip-address]
        - pim
            - database [interface ip-int-name | int-ip-address] [group grp-ip-address [source ip-address]][family]]
            - neighbor [interface ip-int-name] [family]
            - s-pmsi [mdSrcAddr] [mdGrpAddr] [vprnSrcAddr vprnGrpAddr]
            - statistics [{[interface ip-int-name | int-ip-address]} {[group grp-ip-address [source ip-address]]}][family]]
        - msdp
            - cache [peer ip-address] [group ip-address] [source ip-address] [originrp ip-address]
            - statistics [peer ip-address]
clear
    - service
        - id
            - igmp-snooping
                - port-db sap sap-id [group grp-ip-address [source src-ip-address]]
                - port-db sdp sdp-id:vc-id [group grp-ip-address [source src-ip-address]]
                - querier
                - statistics [all | sap sap-id | sdp sdp-id:vc-id

Debug commands

debug
    - router
        - igmp
            - [no] interface [ip-int-name | ip-address]
            - [no] misc
            - no packet [query | v1-report | v2-report | v3-report | v2-leave] group-interface ip-int-name
            - no packet [query | v1-report | v2-report | v3-report | v2-leave] host ip-int-name
            - packet [query | v1-report | v2-report | v3-report | v2-leave] [ip-int-name|ip-int-name] [mode {dropped-only | ingr-and-dropped | egr-ingr-and-dropped}]
            - packet [query | v1-report | v2-report | v3-report | v2-leave] [mode {dropped-only | ingr-and-dropped | egr-ingr-and-dropped}] group-interface ip-int-name
            - packet [query | v1-report | v2-report | v3-report | v2-leave] host ip-address [mode {dropped-only | ingr-and-dropped | egr-ingr-and-dropped}]
debug
    - router
        - 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
            - bgp [source ip-address] [group group-ip-address] [peer peer-ip-address]
            - 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
            - dynmldp [detail]
            - no dynmldp
            - interface [ip-int-name | mt-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
            - mvpn-rtcache [group grp-ip-address] [peer ip-address]
            - no mvpn-rtcache
            - packet [hello | register | register-stop| jp | bsr | assert] [ip-int-name | int-ip-address]
            - no packet
            - red [detail]
            - no red
            - register [group grp-ip-address] [source ip-address] [detail]
            - no register
            - rtm [detail]
            - no rtm
            - s-pmsi [{vpnSrcAddr [vpnGrpAddr]} [mdSrcAddr]] [detail]
            - no s-pmsi
            - tunnel-interface [ldp-p2mp p2mp-id] [sender ip-address] [detail]
            - no tunnel-interface [ldp-p2mp p2mp-id] [sender ip-address]
            - tunnel-interface [rsvp-p2mp lsp-name] [sender ip-address] [detail]
            - no tunnel-interface [rsvp-p2mp lsp-name] [sender ip-address]
debug
    - router
        - [no] msdp
            - packet [pkt-type] [peer ip-address]
            - pim [grp-address]
            - no pim
            - rtm [rp-address]
            - no rtm
            - sa-db [group grpAddr] [source srcAddr] [rp rpAddr]
            - no sa-db

Command descriptions

Configuration commands

Generic commands
shutdown
Syntax

[no] shutdown

Context

config>router>igmp

config>router>igmp>interface

config>router>pim

config>router>pim>interface

Platforms

Supported on all 7210 SAS platforms as described in this document.

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 shutdown command administratively disables an entity. 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 may be deleted.

Unlike other commands and parameters where the default state is not indicated in the configuration file, shutdownand no shutdown are always indicated in system-generated configuration files.

The no form of this command puts an entity into the administratively enabled state.

Default

no shutdown:

config>router>igmp

config>router>igmp>interface ip-int-name

config>router>pim
Special Cases
IGMP Protocol Handling

On all 7210 SAS platforms, IGMP is created in the no shutdown state.

On the 7210 SAS-Mxp, the protocol is handled as follows.

The configure router igmp command instantiates the protocol in the no shutdown state, and resources are allocated to enable the node to process the protocol.

To deallocate resources, you must issue the configure router igmp shutdown and configure router no igmp commands to allow the node to boot up correctly after the reboot. It is not sufficient to issue only a configure router igmp shutdown command.

The resources for IGMP are allocated when the IGMP context is enabled either in the base routing instance or the VPRN service instance. Resources are deallocated when the configuration of the last IGMP context under either base routing instances or VPRN service is removed or shut down.

PIM Protocol Handling

On all 7210 SAS platforms, PIM is created in the no shutdown state.

On the 7210 SAS-Mxp, the protocol is handled as follows.

The configure router pim command instantiates the protocol in the no shutdown state, and resources are allocated to enable the node to process the protocol.

To deallocate resources, you must issue the configure router pim shutdown and configure router no pim commands to allow the node to boot up correctly after the reboot. It is not sufficient to issue only a configure router pim shutdown command.

The resources for PIM are allocated when the PIM context is enabled either in the base routing instance or the VPRN service instance. Resources are deallocated when the configuration of the last PIM context under either base routing instances or VPRN service is removed or shut down.

Multicast commands
ssm-translate
Syntax

ssm-translate

Context

config>router>igmp>interface

Platforms

Supported on all 7210 SAS platforms as described in this document.

Description

This command adds or removes ssm-translate group ranges.

source
Syntax

[no] source ip-address

Context

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

Platforms

Supported on all 7210 SAS platforms as described in this document.

Description

This command adds or removes source addresses for the SSM translate group range.

Parameters
ip-address

Specifies the unicast source address.

Values

a.b.c.d

grp-range
Syntax

[no] grp-range start end

Context

config>router>igmp>interface>shutdown>ssm-translate

Platforms

Supported on all 7210 SAS platforms as described in this document.

Description

This command adds or removes SSM translate group range entries.

Parameters
start

Specifies the multicast group range start address.

Values

a.b.c.d

end

Specifies the multicast group range end address.

Values

a.b.c.d

mc-maximum-routes
Syntax

mc-maximum-routes number [log-only] [threshold threshold]

no mc-maximum-routes

Context

config>router

Platforms

Supported on all 7210 SAS platforms as described in this document.

Description

This command specifies the maximum number of multicast routes that can be held within a VPN routing/forwarding (VRF) context. When this limit is reached, a log and SNMP trap are sent. If the log-only parameter is not specified and the maximum routes value is set below the existing number of routes in a VRF, no new joins are processed.

The no form of this command disables the limit of multicast routes within a VRF context. Issue the no form of this command only when the VPRN instance is shut down.

Default

no mc-maximum-routes

Parameters
number

Specifies the maximum number of routes held in a VRF context.

Values

1 to 2147483647

log-only

Keyword to specify that if the maximum limit is reached, only log the event. This keyword does not disable the learning of new routes.

threshold threshold

Specifies the percentage at which a warning log message and SNMP trap should be sent.

Values

0 to 100

Router IGMP commands
igmp
Syntax

[no] igmp

Context

config>router

Platforms

Supported on all 7210 SAS platforms as described in this document.

Description

This command enables the Internet Group Management Protocol (IGMP) context. When the context is created, the IGMP protocol is enabled.

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 this command disables the IGMP instance. To start or suspend execution of IGMP without affecting the configuration, use the no shutdown command.

interface
Syntax

[no] interface ip-int-name

Context

config>router>igmp

Platforms

Supported on all 7210 SAS platforms as described in this document.

Description

This command configures an IGMP interface. The interface is a local identifier of the network interface on which reception of the specified multicast address is enabled or disabled.

The no form of this 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

Parameters
ip-int-name

Specifies 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 composed of printable, 7-bit ASCII characters. If the string contains special characters (#, $, spaces, and so on), the entire string must be enclosed within double quotes.

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

If the IP interface exists in a different area, it is moved to this area.

disable-router-alert-check
Syntax

[no] disable-router-alert-check

Context

config>router>igmp>if

Platforms

Supported on all 7210 SAS platforms as described in this document.

Description

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

The no form of this command disables the IGMP router alert check option.

import
Syntax

import policy-name

no import

Context

configure>router>igmp>interface

Platforms

Supported on all 7210 SAS platforms as described in this document.

Description

This command applies the referenced IGMP policy (filter) to an interface subscriber or a group interface. An IGMP filter is also known as an allowlist/denylist and is defined under the configure>router>policy-options context.

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

Default

no import

Parameters
policy-name

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

max-groups
Syntax

max-groups [value]

no max-groups

Context

config>router>igmp>if

config>router>pim>if

Platforms

Supported on all 7210 SAS platforms as described in this document.

Description

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

Default

max-group 0

Parameters
value

Specifies the maximum number of groups for this interface.

Values

1 to 1024

max-sources
Syntax

max-sources [value]

no max-sources

Context

config>router>igmp>group-interface

Platforms

Supported on all 7210 SAS platforms as described in this document.

Description

This command configures the maximum number of group sources for this interface.

Parameters
value

Specifies the maximum number of group sources for this interface.

Values

1 to 1000

static
Syntax

static

Context

config>router>igmp>if

Platforms

Supported on all 7210 SAS platforms as described in this document.

Description

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

group
Syntax

[no] group grp-ip-address

Context

config>router>igmp>if>static

Platforms

Supported on all 7210 SAS platforms as described in this document.

Description

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

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

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.

source
Syntax

[no] source ip-address

Context

config>router>igmp>if>static>group

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

Platforms

Supported on all 7210 SAS platforms as described in this document.

Description

This command specifies the source IPv4 address (S) for the static IGMP group being configured. Multicast traffic to the group (G) is 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 is mutually exclusive with the specification of individual sources for the same group.

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

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

Parameters
ip-address

Specifies the IPv4 unicast address.

starg
Syntax

[no] starg

Context

config>router>igmp>if>static>group

Platforms

Supported on all 7210 SAS platforms as described in this document.

Description

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

The no form of this command removes the starg entry from the configuration.

subnet-check
Syntax

[no] subnet-check

Context

config>router>igmp>interface

Platforms

Supported on all 7210 SAS platforms as described in this document.

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

subnet-check

version
Syntax

version version

no version

Context

config>router>igmp>if

Platforms

Supported on all 7210 SAS platforms as described in this document.

Description

This command specifies the IGMP version. Routers that run different versions of IGMP 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 should 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

version 3

Parameters
version

Specifies the IGMP version number.

Values

1, 2, 3

Values

>= 1000

query-interval
Syntax

query-interval seconds

no query-interval

Context

config>router>igmp

Platforms

Supported on all 7210 SAS platforms as described in this document.

Description

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

Default

query-interval 125

Parameters
seconds

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

Values

2 to 1024

query-last-member-interval
Syntax

query-last-member-interval seconds

Context

config>router>igmp

Platforms

Supported on all 7210 SAS platforms as described in this document.

Description

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

Default

query-last-member-interval 1

Parameters
seconds

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

Values

1 to 1024

query-response-interval
Syntax

query-response-interval seconds

Context

config>router>igmp

Platforms

Supported on all 7210 SAS platforms as described in this document.

Description

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

Default

query-response-interval 10

Parameters
seconds

Specifies the number of seconds 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

Platforms

Supported on all 7210 SAS platforms as described in this document.

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

robust-count 2

Parameters
robust-count

Specifies the robust count value.

Values

2 to 10

ssm-translate
Syntax

ssm-translate

Context

config>router>igmp

Platforms

Supported on all 7210 SAS platforms as described in this document.

Description

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

grp-range
Syntax

[no] grp-range start end

Context

config>router>igmp>ssm-translate

Platforms

Supported on all 7210 SAS platforms as described in this document.

Description

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

Parameters
start

Specifies an IP address for the start of the group range.

end

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

source
Syntax

[no] source ip-address

Context

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

Platforms

Supported on all 7210 SAS platforms as described in this document.

Description

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

Parameters
ip-address

Specifies the IP address that will be sending data.

Router PIM commands
pim
Syntax

[no] pim

Context

config>router

Platforms

Supported on all 7210 SAS platforms as described in this document.

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 router OS supports PIM sparse mode (PIM-SM). By default, this command is not enabled.

interface
Syntax

[no] interface ip-int-name

Context

config>router>pim

Platforms

Supported on all 7210 SAS platforms as described in this document.

Description

This command configures a logical IP routing interface.

Interface names are case-sensitive and must be unique within the group of IP interfaces defined for the config router interface and config service ies interface commands. Interface names must not be in the dotted decimal notation of an IP address. For example, the name ‟1.1.1.1” is not allowed, but ‟int-1.1.1.1” is allowed. Show commands for router interfaces use either the interface names or the IP addresses. Ambiguity can exist if an IP address is used as an IP address and an interface name. Duplicate interface names can exist in different router instances, although this is not recommended because it is confusing.

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

Parameters
ip-int-name

Specifies the name of the IP interface. An interface name cannot be in the form of an IP address. Interface names can be any string of up to 32 alphanumeric characters. If the string contains special characters (#, $, spaces, and so on), 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.

assert-period
Syntax

assert-period assert-period

no assert-period

Context

config>router>pim>if

Platforms

Supported on all 7210 SAS platforms as described in this document.

Description

This command configures the period for refreshes of PIM Assert messages on an interface.

The no form of this command removes the assert period from the configuration.

Default

no assert-period

Parameters
assert-period

Specifies the period for refreshes of PIM Assert messages on an interface.

Values

1 to 300 seconds

bfd-enable
Syntax

[no] bfd-enable {ipv4}

Context

config>router>pim>interface

Platforms

Supported on all 7210 SAS platforms as described in this document.

Description

This command enables the use of IPv4 bidirectional forwarding (BFD) to control the state of the associated protocol interface. By enabling BFD on a specific 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 the BFD are set using the BFD command under the IP interface.

For information about the protocols and platforms that support BFD, see the 7210 SAS-Mxp, R6, R12, S, Sx, T Router Configuration Guide.

The no form of this command removes BFD from the associated IGP protocol adjacency.

Default

no bfd-enable

enable-mdt-spt
Syntax

[no] enable-mdt-spt

Context

config>router>pim

Platforms

7210 SAS-T, 7210 SAS-Mxp, 7210 SAS-R6, and 7210 SAS-R12

Description

This command enables SPT switchover for default MDT. When enabled, the PIM instance resets all MDTs and reinitiates setup.

The no form of this command disables SPT switchover for default MDT. When disabled, the PIM instance resets all MDTs and reinitiates setup.

Default

no enable-mdt-spt

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

Platforms

Supported on all 7210 SAS platforms as described in this document.

Description

This command specifies the import route policy to be used. Route policies are configured in the config>router>policy-options context.

When an import policy is not specified, BGP routes are accepted by default. Up to five import policy names can be specified.

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

Default

no import join-policy

no import register-policy

Parameters
join-policy

Keyword to filter PIM join messages, which prevent unwanted multicast streams from traversing the network.

register-policy

Keyword to filter 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

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

mc-ecmp-balance
Syntax

[no] mc-ecmp-balance

Context

configure>router>pim

Platforms

Supported on all 7210 SAS platforms as described in this document.

Description

This command enables multicast balancing of traffic over ECMP links. When enabled, each multicast stream that needs to be forwarded over an ECMP link is re-evaluated for the total multicast bandwidth utilization. Re-evaluation occurs on the specified ECMP interface.

The no form of this command disables the multicast balancing.

mc-ecmp-balance-hold
Syntax

mc-ecmp-balance-hold minutes

no mc-ecmp-balance-hold

Context

configure>router>pim

Platforms

Supported on all 7210 SAS platforms as described in this document.

Description

This command configures the hold time for multicast balancing over ECMP links.

Parameters
minutes

Specifies the hold time, in minutes, that applies after an interface has been added to the ECMP link.

Values

2 to 600

mc-ecmp-hashing-enabled
Syntax

[no] mc-ecmp-hashing-enabled

Context

configure>router>pim

Platforms

Supported on all 7210 SAS platforms as described in this document.

Description

This command enables hash-based multicast balancing of traffic over ECMP links and causes PIM joins to be distributed over the multiple ECMP paths based on a hash of S and G (and possibly next-hop IP). When a link in the ECMP set is removed, the multicast streams that were using that link are redistributed over the remaining ECMP links using the same hash algorithm. When a link is added to the ECMP set, new joins may be allocated to the new link based on the hash algorithm, but existing multicast streams using the other ECMP links stay on those links until they are pruned.

Hash-based multicast balancing is supported for both IPv4 and IPv6.

This command is mutually exclusive with the mc-ecmp-balance command in the same context.

The no form of this command disables the hash-based multicast balancing of traffic over ECMP links.

Default

no mc-ecmp-hashing-enabled

hello-interval
Syntax

hello-interval hello-interval

no hello-interval

Context

config>router>pim>interface

Platforms

Supported on all 7210 SAS platforms as described in this document.

Description

This command configures the frequency at which PIM Hello messages are transmitted on this interface.

The no form of this command reverts to the default value.

Default

hello-interval 30

Parameters
hello-interval

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

Values

0 to 255 seconds

hello-multiplier
Syntax

hello-multiplier deci-units

no hello-multiplier

Context

config>router>pim>interface

Platforms

Supported on all 7210 SAS platforms as described in this document.

Description

This command configures the multiplier 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.

Parameters
deci-units

Specifies the value, in multiples of 0.1, for the formula used to calculate the hello-hold time based on the hello-multiplier:

(hello-interval * hello-multiplier) / 10

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

Values

20 to 100

Default

35

improved-assert
Syntax

[no] improved-assert

Context

config>router>pim>interface

Platforms

Supported on all 7210 SAS platforms as described in this document.

Description

The PIM assert process establishes a forwarder for a LAN and requires interaction between the control and forwarding planes. The assert process is started when data is received on an outgoing interface, meaning that duplicate traffic is forwarded to the LAN until the forwarder is negotiated among the routers.

When the improved-assert command is enabled, the PIM assert process is done entirely in the control plane. The advantage is that it eliminates duplicate traffic forwarding to the LAN. It also improves performance by removing the required interaction between the control and data planes.

Note:

This command is still fully interoperable with the implementations described in draft-ietf-pim-sm-v2-new-xx, Protocol Independent Multicast - Sparse Mode (PIM-SM): Revised, and RFC 2362, Protocol Independent Multicast-Sparse Mode (PIM-SM). However, there may be conformance tests that fail if the tests expect control-data plane interaction in determining the assert winner. Nokia recommends disabling the improved-assert command when performing conformance tests.

Default

improved-assert

instant-prune-echo
Syntax

[no] instant-prune-echo

Context

config>router>pim>interface

Platforms

Supported on all 7210 SAS platforms as described in this document.

Description

This command enables the PIM router to echo the PIM prune message received from a downstream router. It is typically used in a multi-access broadcast network, for example in an Ethernet LAN, to reduce the probability of loss of PIM prune messages.

Default

no instant-prune-echo

multicast-senders
Syntax

multicast-senders {auto | always | never}

no multicast-senders

Context

config>router>pim>interface

Platforms

Supported on all 7210 SAS platforms as described in this document.

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

multicast-senders auto

Parameters
auto

Keyword to specify that, on broadcast interfaces, the forwarding plane performs a subnet-match check on multicast packets received on the interface to determine whether 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

Keyword that treats all traffic received on the interface as coming from a directly-attached multicast source.

never

Keyword to specify that, on broadcast interfaces, traffic from directly-attached multicast sources is not forwarded. Traffic from a remote source is still 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.

priority
Syntax

priority dr-priority

no priority

Context

config>router>pim>interface

Platforms

Supported on all 7210 SAS platforms as described in this document.

Description

This command configures the priority value to elect the designated router (DR). The DR election priority is a 32-bit unsigned number, and the numerically larger priority is always preferred.

The no form of this command reverts to the default values.

Default

priority 1

Parameters
priority

Specifies the priority to become the designated router. 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

Platforms

Supported on all 7210 SAS platforms as described in this document.

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) are 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 continues to act as the DR for the LAN even after the old DR comes back up.

The no form of this command disables sticky-dr operation on this interface.

Default

no sticky-dr

Parameters
priority dr-priority

Specifies 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

three-way-hello

no three-way-hello

Context

config>router>pim>interface

Platforms

Supported on all 7210 SAS platforms as described in this document.

Description

This command enables three-way hello. By default, the three-way-hello command 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

Platforms

Supported on all 7210 SAS platforms as described in this document.

Description

This command sets the T bit in the LAN Prune Delay option of the Hello Message. This indicates the capability of the router to enable join message suppression. This capability allows for upstream routers to explicitly track join membership.

Default

no tracking-support

rp
Syntax

rp

Context

config>router>pim

Platforms

Supported on all 7210 SAS platforms as described in this document.

Description

Commands in this context configure rendezvous point (RP) parameters. The address of the root of the group shared multicast distribution tree is known as its RP. Packets received from a source upstream, and join messages from downstream routers, rendezvous at this router.

If this command is not enabled, the router cannot become the RP.

anycast
Syntax

[no] anycast rp-ip-address

Context

config>router>pim>rp

Platforms

Supported on all 7210 SAS platforms as described in this document.

Description

This command configures a PIM anycast protocol instance for the configured RP. 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 this command removes the anycast instance from the configuration.

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

Platforms

Supported on all 7210 SAS platforms as described in this document.

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 specific 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, up to 15 IP addresses is recommended.

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

Parameters
ip-address

Specifies a peer in the anycast RP set.

Values

Any valid IP address within the scope described previously.

bootstrap-export
Syntax

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

no bootstrap-export

Context

config>router>pim>rp

Platforms

Supported on all 7210 SAS platforms as described in this document.

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.

Default

no bootstrap-export

Parameters
policy-name

Specifies the export policy name up to 32 characters.

bootstrap-import
Syntax

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

no bootstrap-import

Context

config>router>pim>rp

Platforms

Supported on all 7210 SAS platforms as described in this document.

Description

This command to applies import policies to the PIM configuration. The policies control the flow of bootstrap messages to the RP. Up to 5 policy names can be specified.

Default

no bootstrap-import

Parameters
policy-name

Specifies the import policy name up to 32 characters.

bsr-candidate
Syntax

bsr-candidate

Context

config>router>pim>rp

Platforms

Supported on all 7210 SAS platforms as described in this document.

Description

Commands in this context configure Candidate Bootstrap (BSR) parameters.

Default

bsr-candidate shutdown

address
Syntax

address ip-address

Context

config>router>pim>rp>bsr-candidate

Platforms

Supported on all 7210 SAS platforms as described in this document.

Description

This command configures the candidate BSR IP address. This address is for bootstrap router election.

Parameters
ip-address

Specifies the IP host address that is used by the IP interface within the subnet. This address must be unique within the subnet and specified in dotted decimal notation.

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

Platforms

Supported on all 7210 SAS platforms as described in this document.

Description

This command configures the length of a mask that is to be combined with the group address before the hash function is called. All groups with the same hash result 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.

Default

hash-mask-len 30

Parameters
hash-mask-length

Specifies the hash mask length.

Values

0 to 32 (v4)

priority
Syntax

priority bootstrap-priority

no priority

Context

config>router>pim>rp>bsr-candidate

Platforms

Supported on all 7210 SAS platforms as described in this document.

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

priority 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

Platforms

Supported on all 7210 SAS platforms as described in this document.

Description

Commands in this context configure candidate RP parameters.

Routers use a set of available rendezvous points distributed in bootstrap messages to get the correct group-to-RP mapping. A set of routers within a domain are also configured as candidate RPs (C-RPs); typically, these are 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

rp-candidate shutdown

address
Syntax

[no] address ip-address

Context

config>router>pim>rp>rp-candidate

Platforms

Supported on all 7210 SAS platforms as described in this document.

Description

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

Parameters
ip-address

Specifies the ip-address.

Values

a.b.c.d

group-range
Syntax

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

Context

config>router>pim>rp>rp-candidate

Platforms

Supported on all 7210 SAS platforms as described in this document.

Description

This command configures the address ranges of the multicast groups for which this router can be an RP.

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

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

Platforms

Supported on all 7210 SAS platforms as described in this document.

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.

Values

5 to 255

priority
Syntax

priority priority

no priority

Context

config>router>pim>rp>rp-candidate

Platforms

Supported on all 7210 SAS platforms as described in this document.

Description

This command configures the candidate RP priority for becoming an RP. This value is used to elect RP for a group range.

Default

priority 192

Parameters
priority

Specifies the priority to become an RP. A value of 0 is considered the highest priority.

Values

0 to 255

static
Syntax

static

Context

config>router>pim>rp

Platforms

Supported on all 7210 SAS platforms as described in this document.

Description

Commands in this context configure static 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, 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

Platforms

Supported on all 7210 SAS platforms as described in this document.

Description

This command configures the RP address used by the router for the range of multicast groups configured by the range command.

Parameters
ip-address

Specifies the static IP address of the RP. The ip-address value of the address command specifies the IP host address that is used by the IP interface within the subnet. This address must be unique within the subnet and specified in dotted decimal notation.

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

Platforms

Supported on all 7210 SAS platforms as described in this document.

Description

This command specifies the range of multicast group addresses to be used by the router as the RP. The config>router>pim>rp>static>address a.b.c.d command implicitly defaults to deny all for all multicast groups (224.0.0.0/4). A group-prefix must be specified for that static address. This command does not apply to the whole group range.

The no form of this command removes the group-prefix from the configuration.

Parameters
grp-ip-address

Specifies the multicast group IP address expressed in dotted decimal notation.

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.

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

Platforms

Supported on all 7210 SAS platforms as described in this document.

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

non-dr-attract-traffic
Syntax

[no] non-dr-attract-traffic

Context

config>router>pim

Platforms

Supported on all 7210 SAS platforms as described in this document.

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, IES, or VPRN) to IGMP and PIM. The interface state is synchronized to the backup node if it is associated with the redundant peer port. The interface can be configured to use PIM, which causes multicast streams to be sent to the elected DR only. The DR is also the router sending traffic to the DSLAM. Because 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 when it is not the DR. When 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

rpf-table
Syntax

rpf-table {rtable-u}

no rpf-table

Context

config>router>pim

Platforms

Supported on all 7210 SAS platforms as described in this document.

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 RPF interface toward the source/rendezvous point. However, the user can specify use of the unicast route table (rtable-u).

The no form of this command reverts to the default value.

Default

rpf-table rtable-u

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

spt-switchover-threshold
Syntax

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

Context

config>router>pim

Platforms

Supported on all 7210 SAS platforms as described in this document

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

Note:

On 7210 SAS, this command enables or disables switchover to the SPT. To disable switchover to SPT, a threshold value of infinity must be configured (that is, to continue using the shared tree for ever, configure the IP multicast prefix with this command and set the threshold to infinity). To use the SPT, do not configure the IP multicast address prefix using this command, and the default behavior applies to the multicast group. The default behavior is to switch over to SPT when the first packet is received.

In the absence of any matching prefix in the table, the default behavior is to switch over when the first packet is seen. In the presence of multiple prefixes matching a specific group, the most specific entry is used.

Parameters
grp-ip-address

Specifies the multicast group IP address expressed in dotted decimal notation.

Values

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

ip-prefix-length

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

spt-threshold

Specifies the 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 threshold. When the infinity keyword is specified, no switchover occurs at any time, regardless of the traffic level detected

Values

1 to 4294967294 | infinity (threshold in kbps)

ssm-assert-compatible-mode
Syntax

ssm-assert-compatible-mode [enable | disable]

Context

config>router>pim

Platforms

Supported on all 7210 SAS platforms as described in this document.

Description

When enabled, this command treats packets as if the SPT bit is set, regardless of whether it is set.

Default

ssm-assert-compatible-mode disable

ssm-default-range-disable
Syntax

ssm-default-range-disable ipv4

no ssm-default-range-disable ipv4

Context

config>router>pim

Platforms

Supported on all 7210 SAS platforms as described in this document.

Description

This command enables and disables the reservation and allows PIM to accept and create (*,G) entries for addresses in this range on receiving IGMPv2 reports. PIM SSM has a default range of 232/8 (232.0.0.0 to 232.255.255.255) reserved by IANA. These addresses are not used by PIM ASM.

Default

ssm-default-range-disable ipv4

Parameters
ipv4

Keyword to specify IPv4 as the SSM default range.

ipv6

Keyword to specify IPv6 as the SSM default range.

ssm-groups
Syntax

[no] ssm-groups

Context

config>router>pim

Platforms

Supported on all 7210 SAS platforms as described in this document.

Description

Commands in this context configure an SSM group instance.

group-range
Syntax

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

Context

config>router>pim>ssm-groups

Platforms

Supported on all 7210 SAS platforms as described in this document.

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.

Parameters
ip-prefix/mask

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

Values

ipv4-prefix:

a.b.c.d

ipv4-prefix-le:

0 to 32

ipv6-prefix:

x:x:x:x:x:x:x:x (eight 16-bit pieces)

x:x:x:x:x:x:d.d.d.d

x:

[0 to FFFF]H

d:

[0 to 255]D

ipv6-prefix-le:

0 to 128
Values

Specifies the to 32 (mask length), 0.0.0.0 to 255.255.255.255 (dotted decimal)

netmask

Specifies the subnet mask in dotted decimal notation.

Values

0.0.0.0 to 255.255.255.255 (network bits all 1 and host bits all 0)

MSDP commands
msdp
Syntax

[no] msdp

Context

config>router

Platforms

7210 SAS-Sx/S 1/10GE (standalone)

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 without affecting the configuration, use the [no] shutdown command.

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

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

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

When all peering sessions are terminated, an event message per peer is not generated.

The no form of this 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

Platforms

7210 SAS-Sx/S 1/10GE (standalone)

Description

This command configures the maximum number of active source messages that are accepted by MSDP, effectively controlling the number of active sources that can be stored on the system.

The no form of this command removes the user-configured limit on the number of source-active (SA) records.

Default

no active-source-limit

Parameters
number

Specifies the number of active sources that can be maintained by MSDP stored on the system.

Values

0 to 1000000

data-encapsulation
Syntax

[no] data-encapsulation

Context

config>router>msdp

Platforms

7210 SAS-Sx/S 1/10GE (standalone)

Description

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

The no form of this command disables the encapsulation of multicast data in SA register messages.The system sends only multicast (S,G) sender information to the remote MSDP peer.

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

Platforms

7210 SAS-Sx/S 1/10GE (standalone)

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. The first policy that matches is applied. If multiple export commands are issued, the last command entered overrides the previous command. The user can specify a maximum of five policy names.

The no form of this command applies no export policies and all SA entries are announced.

Default

no export

Parameters
policy-name

Specifies the export policy name, up to 32 characters. Up to five policy-name arguments can be specified.

If you configure an export policy at the global level, each individual peer inherits the global policy. If you configure an export policy at the group level, each individual peer in a group inherits the group policy. If you configure an export policy at the peer level, the policy only applies to the peer where it is configured.

group
Syntax

[no] group group-name

Context

config>router>msdp

Platforms

7210 SAS-Sx/S 1/10GE (standalone)

Description

This command creates or modifies an MSDP group. To configure multiple MSDP groups, include multiple group statements.

By default, the group options are inherited from the global MSDP options. To override these global options, group-specific options within the group statement can be configured.

If the specified group name is already configured, this command only provides the context to configure the options pertaining to this group.

If the group name provided is not already configured, the group name must be created and the commands in the config>router>msdp>group context, which configure parameters for the group, become available.

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

The no form of this command removes the group name from the MSDP configuration.

Default

no group

Parameters
group-name

Species a MSDP group name, up to 32 characters.

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

Platforms

7210 SAS-Sx/S 1/10GE (standalone)

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. The first policy that matches is applied. If multiple import commands are issued, the last command entered overrides the previous command. A maximum of five policy names can be specified.

If an import policy is configured at the global level, each individual peer inherits the global policy.

If an import policy is configured at the group level, each individual peer in a group inherits the group policy.

If an import policy is configured at the peer level, the policy only applies to the peer where it is configured.

The no form of this command applies no import policies and all source active messages are allowed.

Default

no import

Parameters
policy-name

Specifies the import policy name, up to 32 characters. Up to five policy-name arguments can be specified.

local-address
Syntax

local-address ip-address

no local-address

Context

config>router>msdp

config>router>msdp>peer

config>router>msdp>group

config>router>msdp>group>peer

Platforms

7210 SAS-Sx/S 1/10GE (standalone)

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 to configure the local end of the MSDP session. This address must be present on the node and is used to validate incoming connections to the peer and to establish connections to the remote peer.

If the user enters this command, the specified address is validated and used as the local address for MSDP peers from that point. If a subsequent local-address command is entered, it replaces the existing configuration and the existing sessions are terminated.

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

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

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

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

Default

no local-address

Parameters
ip-address

Specifies an existing address on the node.

Values

a.b.c.d

peer
Syntax

[no] peer ip-address

Context

config>router>msdp

config>router>msdp>group

Platforms

7210 SAS-Sx/S 1/10GE (standalone)

Description

This command configures peer parameters. MSDP must have at least one peer configured. A peer is defined by configuring a local address that can be used by the node to set up a peering session and the address of a remote MSDP router. It is the address of this remote peer that is configured in this command and it identifies the remote MSDP router address.

After peer relationships are established, the MSDP peers exchange messages to advertise active multicast sources. Multiple peering sessions may be required, in which case multiple peer statements should be included in the configurations.

By default, the options applied to a peer are inherited from the global or group level. To override these inherited options, include peer-specific options within the peer statement.

If the peer address provided is already a configured peer, this command only provides the context to configure the parameters pertaining to this peer.

If the peer address provided is not already a configured peer, the peer instance must be created and the commands in the config>router>msdp>peer or config>router>msdp>group>peer contexts, which configure parameters for the peer instance, become available.

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

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

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

Parameters
ip-address

Specifies the peer IP address. The address configured in this statement must identify the remote MSDP router with which the peering session must be established.

authentication-key
Syntax

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

no authentication-key

Context

config>router>msdp>peer

config>router>msdp>group>peer

Platforms

7210 SAS-Sx/S 1/10GE (standalone)

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.

The no form of this command configures acceptance of all MSDP messages and disables the MD5 signature option authentication key.

Default

no authentication-key

Parameters
authentication-key

Specifies the authentication key. The key can be any combination of printable, 7-bit ASCII characters, up to 255 characters in the config>router>msdp>peer context, or up to 127 characters in the config>router>msdp>group>peer context. If the string contains special characters (#, $, spaces, and so on), enclose the entire string in quotation marks (‟ ”).

hash-key

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

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

hash

Keyword to specify 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

Keyword to specify 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

Platforms

7210 SAS-Sx/S 1/10GE (standalone)

Description

This command enables the use of a default peer. Using the default peer mechanism, a peer can be selected as the default MSDP peer. As a result, all SA messages from the peer are 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 rules applied to SA messages originating at Router S received at Router R from Router N are as follows:

  • 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 Border Gateway Protocol (BGP) next hop of the active multicast RPF route toward Router S, 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, 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, Router N is the peer-RPF neighbor, and its SA messages are accepted.

  • If Router N does not fit any of the preceding rules, Router N is not a peer-RPF neighbor, and its SA messages are rejected.

The no form of this command removes the default peer configuration.

Default

no default-peer

receive-msdp-msg-rate
Syntax

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

no receive-msg-rate

Context

config>router>msdp

config>router>msdp>peer

config>router>msdp>group

config>router>msdp>group>peer

Platforms

7210 SAS-Sx/S 1/10GE (standalone)

Description

This command limits the number of MSDP messages that are read from the TCP session. An MSDP/ RP router may receive a large number of MSDP protocol message packets in a particular SA message.

After the number of MSDP packets (including SA messages) defined in the threshold have been processed, the rate of all other MSDP packets is rate limited by no longer accepting messages from the TCP session until the time (seconds) has elapsed.

The no form of this command sets no limit on the number of MSDP and SA limit messages that are accepted.

Default

no receive-msdp-msg-rate

Parameters
number

Specifies the number of MSDP messages (including SA messages) that are read from the TCP session per the specified number of seconds.

Values

10 to 10000

Default

0

seconds

Specifies the time that, together with the number parameter, defines the number of MSDP messages (including SA messages) that are read from the TCP session within the configured number of seconds.

Values

1 to 600

Default

0

threshold

Specifies the number of MSDP messages that can be processed before the MSDP message rate limiting function is activated; this is particularly useful during system startup and initialization.

Values

1 to 1000000

Default

0

shutdown
Syntax

[no] shutdown

Context

config>router>msdp

config>router>msdp>peer

config>router>msdp>group

Platforms

7210 SAS-Sx/S 1/10GE (standalone)

Description

This command administratively enables or disables an entity. When disabled, an entity does not change, reset, or remove any configuration settings or statistics. Many entities must be explicitly enabled using the no shutdown command and must be shut down before they may be deleted.

Unlike other commands and parameters where the default state is not indicated in the configuration file, shutdownand no shutdownare always indicated in system generated configuration files.

The no form of this command puts an entity into the administratively enabled state.

Default

no shutdown

mode
Syntax

mode {mesh-group | standard}

Context

config>router>msdp>group

Platforms

7210 SAS-Sx/S 1/10GE (standalone)

Description

This command configures groups of peers in a full mesh topology to limit excessive flooding of SA messages to neighboring peers.

MSDP peers can be configured and grouped in a full-mesh topology that prevents excessive flooding of SA messages to neighboring peers.

In a meshed configuration, all members of the group must have a peer connection with every other mesh group member. If this rule is not followed, unpredictable results may occur.

Default

mode standard

Parameters
mesh-group

Keyword to specify that 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.

standard

Keyword to specify a non-meshed mode.

rpf-table
Syntax

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

no rpf-table

Context

config>router>msdp

Platforms

7210 SAS-Sx/S 1/10GE (standalone)

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 the RPF interface toward the source or RP. However, the user can specify one of the following options:

  • use the unicast route table only

  • use the multicast route table only

  • use both route tables

The no form of this command reverts to the default value.

Default

rpf-table rtable-u

Parameters
rtable-m

Specifies that only the multicast route table is used by the multicast protocol (MSDP) for IPv4 RPF checks. This route table contains routes submitted by static routes, IS-IS, and OSPF.

rtable-u

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

both

Specifies that the multicast route table is always looked up first and, if there is a route, use it. If MSDP does not find a route in the first lookup, it tries to find it in the unicast route table. The multicast route table (rtable-m) is checked before the unicast route table (rtable-u).

sa-timeout
Syntax

sa-timeout seconds

no sa-timeout

Context

config>router>msdp

Platforms

7210 SAS-Sx/S 1/10GE (standalone)

Description

This command configures the value for the SA entries in the cache. If these entries are not refreshed within the timeout value, they are removed from the cache. Normally, entries are refreshed at least once a minute. But under a 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.

The no form of this command reverts to the default value.

Default

sa-timeout 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

Platforms

7210 SAS-Sx/S 1/10GE (standalone)

Description

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

If the specified prefix and mask are already configured, this command only provides the context to configure the parameters pertaining to this active source message filter.

If the prefix and mask provided are not already configured, the source node instance must be created and the commands in the config>router>msdp>source context, which configure parameters for the source node instance, become available.

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

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

Parameters
ip-prefix

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

Values

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

mask

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)

Operational commands
mrinfo
Syntax

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

Context

<GLOBAL>

Platforms

Supported on all 7210 SAS platforms as described in this document.

Description

This command displays multicast information from the target multicast router. Information displayed includes adjacency information, protocol, metrics, thresholds, and flags from the target multicast router. This information can be used to determine whether bidirectional adjacencies exist.

Parameters
ip-address

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

dns-name

Specifies the DNS name, if the DNS name resolution is configured.

Values

ip-address: ipv4 unicast address (a.b.c.d)

dns-name: [max 63 chars]

router router-instance

Specifies the router instance that this command applies to.

Default

router-name — "Base" | "management", Default — Base

service-name

Specifies the service instance that this command applies to, up to 64 characters.

Output

The following output is an example of mrinfo, and Output fields: mrinfo describes the output fields.

Sample output 
A:dut-f# mrinfo 10.1.1.2

10.1.1.2  [version 3.0,prune,genid,mtrace]:
  10.1.1.2 -> 10.1.1.1 [1/0/pim]
  16.1.1.1 -> 0.0.0.0 [1/0/pim/down/disabled]
  17.1.1.1 -> 0.0.0.0 [1/0/pim/querier/leaf]
  200.200.200.3 -> 239.200.200.5 [1/0/tunnel/pim]... 

A:dut-g# mrinfo 1.1.1.1

1.1.1.1  [version 7.0,prune,genid,mtrace]:
? 1.1.1.1 -> ? 0.0.0.0 [1/0/pim/leaf]
? 10.1.1.1 -> ? 10.1.1.2 [1/0/pim]
? 10.1.1.1 -> ? 10.1.1.9 [1/0/pim]
? 10.1.1.1 -> ? 0.0.0.0 [1/0/pim/leaf]
? 10.1.1.1 -> ? 10.1.1.7 [1/0/pim]
? 10.1.2.1 -> ? 10.1.2.7 [1/0/pim]
Table 3. Output fields: mrinfo

Label

Description

General flags

version

Indicates software version on queried router

prune

Indicates the router understands pruning

genid

Indicates the router sends generation IDs

mtrace

Indicates the router handles mtrace requests

Neighbors flags

1

Metric

0

Threshold (multicast time-to-live)

pim

PIM enabled on the interface

down

Operational status of the interface

disabled

Administrative status of the interface

leaf

No downstream neighbors on the interface

querier

Interface is IGMP querier

tunnel

Neighbor reached via tunnel
mtrace
Syntax

mtrace source ip-address | dns-name [group ip-address | dns-name] [destination ip-address | dns-name] [hop hop] [router router-instance> | service-name service-name] [wait-time wait-time]

Context

<GLOBAL>

Platforms

Supported on all 7210 SAS platforms as described in this document.

Description

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

Parameters
source ip-address

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

dns-name

Specifies the DNS name if DNS name resolution is configured.

Values

ip-address: ipv4 unicast address (a.b.c.d)

dns-name: [max 63 chars]

group ip-address

Specifies the multicast address.

destination ip-address

Specifies the IP address of the unicast destination. If this parameter is omitted, the IP address of the system where the command is entered is used. The destination parameter can also be used to specify a local interface address as the destination address to send the trace query. The default address for the destination address is the incoming IETF format for that (S,G)

hop hop

Specifies the maximum number of hops that are traced from the receiver back toward the source.

Values

1 to 255

Default

32 hops (infinity for the DVMRP routing protocol).

router router-instance

Specifies the router instance that this command applies to.

Default

router-name — "Base" | "management", Default — Base

service-name service-name

Specifies the service instance that this command applies to, up to 64 characters.

wait-time wait-time

Specifies the number of seconds to wait for the response.

Values

1 to 60

Default

10

Output

The following output is an example of multicast path tracing information, and Output fields: mtrace describes the output fields.

Sample output 
A:Dut-F# mtrace source 10.10.16.9 group 224.5.6.7
 
Mtrace from 10.10.16.9 via group 224.5.6.7
Querying full reverse path...
 
  0  ? (10.10.10.6)
 -1  ? (10.10.10.5)  PIM  thresh^ 1  No Error
 -2  ? (10.10.6.4)  PIM  thresh^ 1  No Error
 -3  ? (10.10.4.2)  PIM  thresh^ 1  Reached RP/Core
 -4  ? (10.10.1.1)  PIM  thresh^ 1  No Error
 -5  ? (10.10.2.3)  PIM  thresh^ 1  No Error
 -6  ? (10.10.16.9)
Round trip time 29 ms; total ttl of 5 required.
Table 4. Output fields: mtrace

Label

Description

hop

Displays the number of hops from the source to the listed router

router name

Displays the name of the router for this hop. If a DNS name query is not successful a ‟?” displays.

address

Displays the address of the router for this hop

protocol

Displays the protocol used

ttl

Displays the forward TTL threshold. TTL that a packet is required to have before it is forwarded over the outgoing interface.

forwarding code

Displays the forwarding information or error code for this hop

Show commands

IGMP commands
group
Syntax

group [grp-ip-address]

group summary

Context

show>router>igmp

Platforms

Supported on all 7210 SAS platforms as described in this document, except those operating in access-uplink mode

Description

This command displays the multicast group and (S,G) addresses. If no grp-ip-address parameters are specified, 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 multicast group information, and Output fields: IGMP group describes the output fields.

Sample output 
*B:Dut-C# show router igmp group 
===============================================================================
IGMP Interface Groups
===============================================================================
===============================================================================
IGMP Host Groups
===============================================================================
(*,224.0.0.1)
    Fwd List  : 239.112.1.2            Up Time : 0d 00:00:21
(10.11.0.1,224.0.0.1)
    Fwd List  : 239.112.1.1            Up Time : 0d 00:00:30
    Blk List  : 239.112.1.2            Up Time : 0d 00:00:21
(10.11.0.2,224.0.0.1)
    Fwd List  : 239.112.1.1            Up Time : 0d 00:00:30
(*,224.0.0.2)
    Fwd List  : 239.112.1.2            Up Time : 0d 00:00:21
(10.11.0.1,224.0.0.2)
    Blk List  : 239.112.1.2            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   Nbr Blk 
===============================================================================
(*,224.0.0.1)                     1                      0
(10.11.0.1,224.0.0.1)             1                      1
(10.11.0.2,224.0.0.1)             1                      0
(*,224.0.0.2)                     1                      0
(10.11.0.1,225.0.0.2)             0                      1
-------------------------------------------------------------------------------
(*,G)/(S,G) Entries : 5
===============================================================================
*B:Dut-C# 

A:NYC# show router igmp group 224.24.24.24
===============================================================================
IGMP Groups
===============================================================================
(*,239.24.24.24)                       Up Time : 0d 05:23:23
    Fwd List  : nyc-vlc
-------------------------------------------------------------------------------
(*,G)/(S,G) Entries : 1
===============================================================================
A:NYC#
Table 5. Output fields: IGMP group

Label

Description

IGMP Groups

Displays the IP multicast sources corresponding to the IP multicast groups that4 are statically configured

Fwd List

Displays the list of interfaces in the forward list

Blk List

Displays the list of interfaces in the blocked list
ssm-translate
Syntax

ssm-translate

ssm-translate interface interface-name

Context

show>router>igmp

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command displays IGMP SSM translate configuration information.

Output

The following output is an example of IGMP SSM translate information, and Output fields: IGMP SSM-translate describes the output fields.

Sample output 
================================================================= 
IGMP SSM Translate Entries
=================================================================
Group Range               Source                     Interface
-----------------------------------------------------------------
<239.1.1.1 - 239.1.1.2>   10.1.1.1                     
                             
<239.1.1.1 - 239.1.1.5>   10.1.1.2                     ies-abc
-----------------------------------------------------------------
Table 6. Output fields: IGMP SSM-translate

Label

Description

Group Range

Displays the address ranges of the multicast groups for which this router can be an RP

Source

Displays the unicast address that sends data on an interface

SSM Translate Entries

Displays the total number of SSM translate entries
interface
Syntax

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

Context

show>router>igmp

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command displays IGMP interface information.

Parameters
ip-int-name

Displays the information associated with only the specified IP interface name.

ip-address

Displays the information associated with only the specified IP address.

group grp-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 Output fields: IGMP interface describes the fields.

Sample output 
show router igmp interface output

*A:ALA-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 none
-------------------------------------------------------------------------------
Interfaces : 1
===============================================================================
*A:ALA-BA#


*A:7210SAS>show>router# interface

===============================================================================
Interface Table (Router: Base)
===============================================================================
Interface-Name                   Adm         Opr(v4/v6)  Mode    Port/SapId
   IP-Address                                                    PfxState
-------------------------------------------------------------------------------
system                           Up          Up/Down     Network system
   10.3.3.3/32                                                    n/a
toD_1                            Up          Up/Down     Network 1/1/6
   10.1.3.3/24                                                   n/a
toE_1                            Up          Up/Down     Network 1/1/5
   10.1.2.3/24                                                   n/a
toIxia_1                         Up          Up/Down     IES     1/1/16:1
   10.2.1.3/24                                                   n/a
-------------------------------------------------------------------------------
Interfaces : 4
===============================================================================
*A:7210SAS>show>router#
Table 7. Output fields: IGMP interface

Label

Description

Interface

Specifies the interfaces that participate in the IGMP protocol

Adm

Admin Status

Displays the administrative state for the IGMP protocol on this interface

Oper

Oper Status

Displays the current operational state of IGMP protocol on the interface

Querier

Displays the address of the IGMP querier on the IP subnet to which the interface is attached

Querier Up Time

Displays the time since the querier was last elected as querier

Querier Expiry Timer

Displays the time remaining before the querier ages out. If the querier is the local interface address, the value is zero.

Cfg/Opr Version

Admin/Oper version

Cfg — 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 — operational version of IGMP running on this interface. For example, if the cfg value is 3 but all the routers in the local subnet of this interface use IGMP version v1 or v2, the operational version is v1 or v2

Num Groups

Displays the number of multicast groups that have been learned by the router on the interface

Policy

Displays the policy that is to be applied on the interface

Group Address

Displays the IP multicast group address for which this entry contains information

Up Time

Displays the time since this source group entry was created

Last Reporter

Displays 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. In the ‟include” mode, 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. In ‟exclude” mode, reception of packets sent to the specific multicast address is requested from all IP source addresses except those listed in the source-list parameter.

V1 Host Timer

Displays the time remaining until the local router assumes there are no longer any IGMP version 1 members on the IP subnet attached to this interface. Upon hearing an IGMPv1 Membership Report, this value is reset to the group membership timer. While this time remaining is non-zero, the local router ignores an IGMPv2 Leave messages for this group that it receives on this interface.

V2 Host Timer

Displays the time remaining until the local router assumes there are no longer IGMP version 2 members on the IP subnet attached to this interface. Upon hearing an IGMPv2 Membership Report, this value is reset to the group membership timer. While this time remaining is non-zero, the local router ignores 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 is set to ‟dynamic.” For statically configured groups, the value is set to ‟static.”

Compat Mode

Used 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 state per local interface about the compatibility mode of each attached network. A host compatibility mode is determined by the Host Compatibility Mode variable, which can be in one of the following 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.
static
Syntax

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

Context

show>router>igmp

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

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

Parameters
ip-int-name

Displays the information associated with only the specified IP interface name.

ip-addr

Displays the information associated with only the specified IP address.

Output

The following output is an example of static IGMP information, and Output fields: IGMP static describes the fields.

Sample output 
*A:ALA-BA# show router 100 igmp static 
==================================================================
IGMP Static Group Source
==================================================================
Source           Group            Interface                                    
------------------------------------------------------------------
10.11.11.11      239.136.22.3     IGMP_to_CE                      
*                239.1.1.1        IGMP_to_CE                      
10.22.22.22      239.255.255.255  IGMP_to_CE                      
------------------------------------------------------------------
Static (*,G)/(S,G) Entries : 3
==================================================================
*A:ALA-BA#
Table 8. Output fields: IGMP static

Label

Description

Source

Displays entries that represent a source address from which receivers are interested or not interested in receiving multicast traffic

Group

Displays the IP multicast group address for which this entry contains information

Interface

Displays the interface name
statistics
Syntax

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

Context

show>router>igmp

Platforms

Supported on all 7210 SAS platforms as described in this document.

Description

This command displays IGMP statistics information.

Parameters
ip-int-name

Displays the information associated with only the specified IP interface name.

ip-address

Displays the information associated with only the specified IP address.

Output

The following output is an example of IGMP statistics information, and Output fields: IGMP statistics describes the output fields.

Sample output 
*A:dut-e>show>router# igmp statistics

==================================================
IGMP Interface Statistics
==================================================
Message Type        Received       Transmitted
--------------------------------------------------
Queries             0              57
Report V1           0              0
Report V2           0              0
Report V3           0              0
Leaves              0              0
--------------------------------------------------
Global General Statistics
--------------------------------------------------
Bad Length        : 0
Bad Checksum      : 0
Unknown Type      : 0
Drops             : 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
--------------------------------------------------
Global Source Group Statistics
--------------------------------------------------
(S,G)             : 0
(*,G)             : 75
==================================================
*A:dut-e>show>router#
Table 9. Output fields: IGMP statistics

Label

Description

IGMP Interface Statistics

Displays the IGMP statistics for a particular interface

Message Type

Queries — number of IGMP general queries transmitted or received on this interface

Report — total number of IGMP V1, V2, or V3 reports transmitted or received on this interface

Leaves — total number of IGMP leaves transmitted on this interface

Received

Displays the total number of IGMP packets received on this interface

Transmitted

Displays the total number of IGMP packets transmitted from this interface

General Interface Statistics

Displays the general IGMP statistics

Bad Length

Displays the total number of IGMP packets with bad length received on this interface

Bad Checksum

Displays the total number of IGMP packets with bad checksum received on this interface.

Unknown Type

Displays the total number of IGMP packets with unknown type received on this interface

Bad Receive If

Displays the total number of IGMP packets incorrectly received on this interface

Rx Non Local

Displays the total number of IGMP packets received from a non-local sender

Rx Wrong Version

Displays the total number of IGMP packets with wrong versions received on this interface

Policy Drops

Displays the total number of times IGMP protocol instance matched the host IP address or group/source addresses specified in the import policy

No Router Alert

Displays the total number of IGMPv3 packets received on this interface that do not have the router alert flag set
status
Syntax

status

Context

show>router>igmp

Platforms

Supported on all 7210 SAS platforms as described in this document.

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 Output fields: IGMP status describes the output fields.

Sample output 
*A:ALA-BA# show>router# igmp status

===============================================================================
IGMP Status
===============================================================================
Admin State                       : Up
Oper State                        : Up
Query Interval                    : 125
Last Member Query Interval        : 1
Query Response Interval           : 10
Robust Count                      : 2
===============================================================================
*A:ALA-BA#
Table 10. Output fields: IGMP status

Label

Description

Admin State

Displays the administrative status of IGMP

Oper State

Displays the current operating state of this IGMP protocol instance on this router

Query Interval

Displays the frequency at which IGMP query packets are transmitted

Last Member Query Interval

Displays the maximum response time inserted into group-specific queries sent in response to leave group messages, and is also the amount of time between group-specific query messages

Query Response Interval

Displays the maximum query response time advertised in IGMPv2 queries

Robust Count

Displays the number of times the router retries a query
Router PIM commands
anycast
Syntax

anycast [family] [detail]

Context

show>router>pim

Platforms

Supported on all 7210 SAS platforms as described in this document.

Description

This command displays PIM anycast rp-set information.

Parameters
family

Indicates an IPv4 address.

detail

Displays detailed information.

Output

The following output is an example of a PIM anycast configuration information, and Output fields: PIM anycast describes the output fields.

Sample output 
A:7210SAS# show router pim anycast 
===================================================
PIM Anycast RP Entries
===================================================
Anycast RP               Anycast RP Peer                                       
---------------------------------------------------
100.100.100.1            10.102.1.1                 
                         10.103.1.1                 
                         10.104.1.1                 
---------------------------------------------------
PIM Anycast RP Entries : 3
===================================================
Table 11. Output fields: PIM anycast

Label

Description

Anycast Address

Displays the candidate anycast address

Anycast RP Peer

Displays the candidate anycast RP peer address
crp
Syntax

crp [ip-address]

Context

show>router>pim

Platforms

Supported on all 7210 SAS platforms as described in this document.

Description

This command displays PIM candidate RP (CRP) information received at the elected Bootstrap router (BSR).

Parameters
ip-address

Specifies the candidate RP IP address.

Output

The following output is an example of PIM CRP information, and Output fields: PIM CRP describes the output fields.

Sample output 
A:7210SAS# show router pim crp
============================================================================
PIM Candidate RPs
============================================================================
RP Address      Group Address      Priority    Holdtime  Expiry Time
----------------------------------------------------------------------------
239.22.187.236    224.0.0.0/4        192         150       0d 00:02:19
239.22.187.239    224.0.0.0/4        192         150       0d 00:02:19
239.22.187.240    224.0.0.0/4        192         150       0d 00:02:09
----------------------------------------------------------------------------
Candidate RPs : 3
============================================================================
A:7210SAS#
Table 12. Output fields: PIM CRP

Label

Description

RP Address

Displays the CRP address

Group Address

Displays the range of multicast group addresses for which the CRP is the Candidate RP

Priority

Displays the CRP priority for becoming an RP. This value is used to elect RP for a group range. A value of 0 is considered the highest priority.

Holdtime

Displays the hold time of the CRP. It is used by the Bootstrap router to time out the RP entries if it does not listen to another CRP advertisement within the hold time period.

Expiry

Displays the minimum time remaining before the CRP is declared down. If the local router is not the BSR, this value is 0.

Candidate RPs

Displays the number of CRP entries
group
Syntax

group [group-ip-address] [source ip-address] [type {starstarrp | starg | sg}] [detail] [family]

Context

show>router>pim

Platforms

Supported on all 7210 SAS platforms as described in this document.

Description

This command displays PIM source group database information.

Parameters
group-ip-address

Specifies the IP multicast group address for which this entry contains information.

source ip-address

Specifies the source address for which this entry contains information.

type starstarrp

Specifies that only (*, *, rp) entries are displayed.

type starg

Specifies that only (*,G) entries are displayed.

type sg

Specifies that only (S,G) entries are displayed.

detail

Displays detailed group information.

family

Displays either IPv4 or IPv6 information.

Output

The following output is an example of PIM source group database information, and Output fields: PIM group describes the output fields.

Sample output 
*A:7210SAS# show router 1 pim group 

===============================================================================
PIM Groups ipv4
===============================================================================
Group Address                           Type     Spt Bit Inc Intf       No.Oifs
   Source Address                          RP                           
-------------------------------------------------------------------------------
239.1.1.1                               (S,G)            mpls-if-74734  1
   10.1.1.2                                
239.1.1.2                               (S,G)            mpls-if-74734  1
   10.1.1.2                                
239.1.1.3                               (S,G)            mpls-if-74734  1
   10.1.1.2                                
239.1.1.4                               (S,G)            mpls-if-74734  1
   10.1.1.2                                
239.1.1.5                               (S,G)            mpls-if-74734  1
   10.1.1.2                                
239.1.1.6                               (S,G)            mpls-if-74734  1
   10.1.1.2                                
239.1.1.7                               (S,G)            mpls-if-74734  1
   10.1.1.2                                
239.1.1.8                               (S,G)            mpls-if-74734  1
   10.1.1.2                                
239.1.1.9                               (S,G)            mpls-if-74734  1
   10.1.1.2                                

*A:7210SAS# 


*A:7210SAS#show router 1 pim group detail 

===============================================================================
PIM Source Group ipv4
===============================================================================
Group Address      : 239.1.1.1
Source Address     : 10.1.1.2
RP Address         : 0
Advt Router        : 10.17.17.17
Flags              :                    Type               : (S,G)
MRIB Next Hop      : 10.17.17.17
MRIB Src Flags     : remote             Keepalive Timer    : Not Running
Up Time            : 5d 21:12:47        Resolved By        : rtable-u

Up JP State        : Joined             Up JP Expiry       : 0d 00:00:52
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.17.17.17
Incoming Intf      : mpls-if-74734
Outgoing Intf List : vprn1_1
                                      
ECMP opt threshold : 7
Table 13. Output fields: PIM group

Label

Description

Group Address

Displays the IP multicast group address for which this entry contains information

Source Address

Displays the source address of the multicast sender

The source address is 0 if the type is configured as starg.

The source address is the address of the RP if the type is configured as starstarrp.

RP Address

Displays the RP address

Type

Specifies the type of entry, (*,*, rp)/(*,G) or (S,G)

Spt Bit

Specifies whether to forward on (*,*, rp)/(*,G) or on (S,G) state. This is updated when the (S,G) data comes on the RPF interface toward the source.

Incoming Intf

Displays the interface on which the traffic comes in. It can be the RPF interface to the RP (if starg) or the source (if sg).

Num Oifs

Displays the number of interfaces in the inherited outgoing interface list. An inherited list inherits the state from other types.

Flags

Displays the different lists that this interface belongs to

Keepalive Timer Exp

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 (S,G) state alive in the absence of explicit (S,G) joins.

MRIB Next Hop

Displays the next-hop address toward the RP

MRIB Src Flags

Displays the MRIB information about the source. If the entry is of type starg or starstarrp, it contains information about the RP for the group.

Up Time

Displays the time since this source group entry was created

Resolved By

Displays the route table used for RPF check

Up JP State

Displays the upstream join prune state for this entry on the interface. PIM join prune messages are sent by the downstream routers toward the RPF neighbor.

Up JP Expiry

Displays the minimum amount of time remaining before this entry is aged out

Up JP Rpt

Displays the join prune Rpt state for this entry on the interface. PIM join/prune messages are sent by the downstream routers toward the RPF neighbor. (S,G, rpt) state is a result of receiving (S,G, rpt) JP message from the downstream router on the RP tree.

Up JP Rpt Override

Displays 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 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 cancels the override timer. If the router does not see a join (S,G, rpt) message, on expiry of the override timer, it sends its own join (S,G, rpt) message to RPF (S,G, rpt). A similar scenario exists when RPF (S,G, rpt) changes to become equal to RPF (*,G).

Register State

Displays the register state. The register state is kept at the source DR. When the host starts sending multicast packets, and if there are no entries programmed for that group, the source DR sends a register packet to the RP (g). Register state transition occurs based on the register stop timer and the response received from the RP.

Register Stop Exp

Displays the time remaining before the register state may transition to a different state

Register from Anycast RP

Displays whether the register packet for that group has been received from one of the RP from the anycast-RP set

RPF Neighbor

Displays the address of the RPF neighbor

Outgoing Intf List

Displays a list of interfaces on which data is forwarded

interface
Syntax

interface [ip-int-name | int-ip-address] [group [group-ip-address] source ip-address] [type {starstarrp | starg | sg}] [detail] [family]

Context

show>router>pim

Platforms

Supported on all 7210 SAS platforms as described in this document.

Description

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

Parameters
ip-int-name

Displays the interface information associated only with the specified IP interface name.

ip-address

Displays the interface information associated with only the specified IP address.

group group-ip-address

Specifies the IP multicast group address for which this entry contains information.

source ip-address

Specifies the source address for which this entry contains information.

If the type is starg, the value of this object is zero.

If the type is starstarrp, the value of this object is the address of the RP.

type

Specifies the type of this entry.

Values

starstarrp, starg, sg

detail

Displays detailed interface information.

family

Displays IPv4 or IPv6 information for the interface.

Output

The following output is an example of PIM interface information, and Output fields: PIM interface describes the output fields.

Sample output 
*7210 SAS>show>router>pim# interface

===============================================================================
PIM Interfaces ipv4
===============================================================================
Interface                   Adm  Opr  DR Prty         Hello Intvl  Mcast Send
   DR
-------------------------------------------------------------------------------
system                      Up   Up   1               30           auto
   10.5.5.5
loopback1                   Up   Up   1               30           auto
   10.1.1.5
toG_1                       Up   Down 1               30           auto
toIxia_Ntw_1                Up   Up   1               30           auto
   10.2.1.5
toIxia_Ntw_2                Up   Up   1               30           auto
   10.2.2.5
toR_1                       Up   Down 1               30           auto
   N/A
toIxia_1                    Up   Down 1               30           auto
   N/A
toLAN_1                     Up   Up   1               30           auto
   10.1.1.5

-------------------------------------------------------------------------------
Interfaces : 124
===============================================================================
*7210 SAS>show>router>pim#
Table 14. Output fields: PIM interface

Label

Description

Admin State

Displays the administrative state for PIM protocol on this interface

Oper State

Displays the current operational state of PIM protocol on this interface

DR

Displays the designated router on this PIM interface

DR Priority

Displays the priority value sent in PIM Hello messages and that is used by routers to elect the designated router (DR)

Hello Intvl

Indicates the frequency at which PIM Hello messages are transmitted on this interface
mc-ecmp-balance
Syntax

mc-ecmp-balance

Context

show>router>pim

Platforms

Supported on all 7210 SAS platforms as described in this document.

Description

This command displays multicast balance information.

neighbor
Syntax

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

Context

show>router>pim

Platforms

Supported on all 7210 SAS platforms as described in this document.

Description

This command displays PIM neighbor information.

This can be important if an interface has more than one adjacency. For example, consider a LAN-interface configuration with three routers connected and all are running PIM on their LAN interfaces. These routers then have two adjacencies on their LAN interface, each with different neighbors. If the address parameter is not defined in this example, the show command output would display two adjacencies.

Parameters
neighbor ip-int-name

Displays the interface information associated only with the specified IP interface name.

neighbor ip-address

Displays the interface information associated only with the specified IP address.

address ip-address

Specifies the IP address of the neighbor on the other side of the interface.

detail

Displays detailed neighbor information.

family

Displays either IPv4 or IPv6 information for the specified neighbor.

Output

The following output is an example of PIM neighbor information, and Output fields: PIM neighbor describes the output fields.

Sample output 
ALA-1>show>router>pim# neighbor

===============================================================================
PIM Neighbor ipv4
===============================================================================
Interface               Nbr DR Prty     Up Time       Expiry Time     Hold Time
   Nbr Address
-------------------------------------------------------------------------------
toB_1                   1               0d 00:31:36   0d 00:01:40     105
   10.1.1.2
toE_1                   1               0d 00:32:04   0d 00:01:42     105
   10.1.1.5
toE_10                  1               0d 00:32:04   0d 00:01:42     105
   10.1.10.5
toE_11                  1               0d 00:32:04   0d 00:01:42     105
   10.1.11.5
toE_12                  1               0d 00:32:04   0d 00:01:42     105
   10.1.12.5
toE_13                  1               0d 00:32:04   0d 00:01:42     105
   10.1.13.5
toE_14                  1               0d 00:32:04   0d 00:01:42     105
   10.1.14.5
toE_15                  1               0d 00:32:05   0d 00:01:41     105
   10.1.15.5
ALA-1#
Table 15. Output fields: PIM neighbor

Label

Description

Interface

Displays the neighbor interface name

Nbr DR Priority

Displays the value of the neighbor DR priority, which is received in the Hello message

Nbr Address

Displays the neighbors address

Up Time

Displays the time since this PIM neighbor (last) became a neighbor of the local router

Expiry Time

Displays the minimum time remaining before this PIM neighbor is aged out

0 — Means that this neighbor is never be aged out. This happens when the PIM neighbor sends a Hello message with a hold-time set to ‟0xffff.”

Hold Time

Displays the value of the hold time present in the hello message

DR Priority

Displays the value of the neighbor DR priority, which is received in the Hello message

Tracking Support

Displays whether the T bit in the LAN prune delay option is present in the Hello message. This indicates the neighbor capability to disable join message suppression.

LAN Delay

Displays the value of the LAN delay field present in the hello message received from the neighbor

Gen Id

Displays a randomly generated 32-bit value that is regenerated each time PIM forwarding is started or restarted on the interface, including when the router restarts. When a Hello message with a new GenID is received from a neighbor, old Hello information about that neighbor is discarded and replaced by the information from the new hello message.

Override Intvl (ms)

Displays the value of the override interval present in the Hello message
rp
Syntax

rp [family | ip-address]

Context

show>router>pim

Platforms

Supported on all 7210 SAS platforms as described in this document.

Description

This command displays the RP set information built by the router.

Parameters
family

Displays either IPv4 or IPv6 information.

ip-address

Specifies the IP address of the RP.

Output

The following output is an example of PIM RP information, and Output fields: PIM RP describes the output fields.

Sample output 
A:ALA-1# show router pim rp
==================================================================
PIM RP Set ipv4
==================================================================
Group Address      RP Address      Type        Priority  Holdtime Expirytime
------------------------------------------------------------------
224.0.0.0/4        239.200.200.4   Dynamic     192       150
                   10.1.7.1        Static      1         N/A
------------------------------------------------------------------
Group Prefixes : 1
==================================================================
A:ALA-1#
Table 16. Output fields: PIM RP

Label

Description

Group Address

Displays the multicast group address of the entry

RP Address

Displays the address of the RP

Type

Specifies whether the entry was learned through the Bootstrap mechanism or if it was statically configured

Priority

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

Holdtime

Displays the value of the hold time present in the BSM message
rp-hash
Syntax

rp-hash ip-address

Context

show>router>pim

Platforms

Supported on all 7210 SAS platforms as described in this document.

Description

This command hashes the RP for the specified group from the RP set.

Parameters
ip-address

Displays specific multicast group addresses.

Output

The following output is an example of PIM RP hashing information, and Output fields: PIM RP-hash describes the output fields.

Sample output 
A:ALA-1# show router pim rp-hash 239.101.0.0
==============================================
PIM Group-To-RP mapping
==============================================
Group Address      RP Address      Type
----------------------------------------------
239.101.0.0        229.200.200.4   Bootstrap
==============================================
A:ALA-1#


A:ALA-1# show router pim rp-hash 239.101.0.6
==============================================
PIM Group-To-RP mapping
==============================================
Group Address      RP Address      Type
----------------------------------------------
239.101.0.6        239.200.200.4   Bootstrap
==============================================
A:ALA-1#
Table 17. Output fields: PIM RP-hash

Label

Description

Group Address

Displays the multicast group address of the entry

RP Address

Displays the address of the Rendezvous Point (RP)

Type

Specifies whether the entry was learned through the Bootstrap mechanism or if it was statically configured
s-pmsi
Syntax

s-pmsi [group-ip group-ip] [source-ip source-ip] [detail]

s-pmsi [mdSrcAddr [mdGrpAddr]] [group-ip group-ip] [source-ip source-ip] [detail]

s-pmsi ext-tunnel-id ext-tunnel-id [tunnel-id tunnel-id] [group-ip group-ip] [source-ip source-ip] [detail]

s-pmsi root-addr root-addr [lsp-id lsp-id] [group-ip group-ip] [source-ip source-ip] [detail]

Context

show>router>pim

Platforms

7210 SAS-T (network mode only), 7210 SAS-R6, 7210 SAS-R12, 7210 SAS-Mxp, and 7210 SAS-Sx/S 1/10GE (in standalone mode)

Description

Displays the list of selective provider multicast service interfaces that are currently active.

Parameters
group-ip

Specifies the group IP address.

source-ip

Specifies the source IP address.

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.

lsp-id

Displays PIM S-PMSI information associated with the specified LSP.

detail

Displays detailed output.

Output

The following outputs are examples of S-PMSI information, and Output fields: S-PMSI describes the output fields.

Sample output PIM selective provider tunnel 
*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.200.200.7         239.0.89.72           24603         1                   
239.200.200.7         239.0.89.73           24604         1                   
239.200.200.7         239.0.89.74           24605         1                   
239.200.200.7         239.0.89.75           24606         1                   
239.200.200.7         239.0.89.76           24607         1                   
239.200.200.7         239.0.89.77           24608         1                   
239.200.200.7         239.0.89.78           24609         1                   
239.200.200.7         239.0.89.79           24610         1                   
239.200.200.7         239.0.89.80           24611         1                   
239.200.200.7         239.0.89.81           24612         1                   
239.200.200.7         239.0.89.82           24613         1                   
239.200.200.7         239.0.89.83           24614         1                   
239.200.200.7         239.0.89.84           24615         1                   
239.200.200.7         239.0.89.85           24616         1                   
239.200.200.7         239.0.89.86           24617         1                   
239.200.200.7         239.0.89.87           24618         1
...
===============================================================================
*B:node-6#
Sample output PIM selective provider tunnel detail 
*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.200.200.7         239.0.89.72           24603         1                   
239.200.200.7         239.0.89.73           24604         1                   
239.200.200.7         239.0.89.74           24605         1                   
239.200.200.7         239.0.89.75           24606         1                   
239.200.200.7         239.0.89.76           24607         1                   
239.200.200.7         239.0.89.77           24608         1                   
239.200.200.7         239.0.89.78           24609         1                   
239.200.200.7         239.0.89.79           24610         1                   
239.200.200.7         239.0.89.80           24611         1                   
239.200.200.7         239.0.89.81           24612         1                   
239.200.200.7         239.0.89.82           24613         1                   
239.200.200.7         239.0.89.83           24614         1                   
239.200.200.7         239.0.89.84           24615         1                   
239.200.200.7         239.0.89.85           24616         1                   
239.200.200.7         239.0.89.86           24617         1                   
239.200.200.7         239.0.89.87           24618         1
...
===============================================================================
*B:node-6#
Sample output RX tracking for RSVP S-PMSI tunnel 
*A:Dut-C# show router 1 pim s-pmsi
===============================================================================
PIM RSVP Spmsi tunnels
===============================================================================
P2mp ID   Tunnel ID   Ext Tunnel Adrs       SPMSI Index   Num VPN   State
                                                          SGs
-------------------------------------------------------------------------------
0         0           10.20.1.4             1030144       1         RX Tracking
0         0           10.20.1.4             1030144       1         RX Tracking
===============================================================================
PIM RSVP Spmsi Interfaces : 2
===============================================================================
*A:Dut-C# show router 21 pim s-pmsi
====================================================================
PIM LDP Spmsi tunnels
====================================================================
Lsp ID    Root Addr             SPMSI Index   Num VPN   State
                                              SGs
--------------------------------------------------------------------
0         10.20.1.4             1030144       1         RX Tracking
0         10.20.1.4             1030144       1         RX Tracking
====================================================================
PIM LDP Spmsi Interfaces : 2
====================================================================
*A:Dut-C#
Sample output RX tracking for RSVP S-PMSI tunnel detail 
*A:Dut-C# show router 1 pim s-pmsi detail
===============================================================================
PIM RSVP Spmsi tunnels
===============================================================================
P2MP ID            : 0                  Tunnel ID          : 0
Ext Tunnnel Addrs  : 10.20.1.4          Spmsi IfIndex      : 1030144
Number of VPN SGs  : 1                  Uptime             : 0d 00:02:48
VPN Group Address  : 239.100.0.0
VPN Source Address : 10.1.101.2
State              : RX Tracking        Mdt Threshold      : 0
===============================================================================
PIM RSVP Spmsi tunnels
===============================================================================
P2MP ID            : 0                  Tunnel ID          : 0
Ext Tunnnel Addrs  : 10.20.1.4          Spmsi IfIndex      : 1030144
Number of VPN SGs  : 1                  Uptime             : 0d 00:02:47
VPN Group Address  : ff0e:db8:225:100::
VPN Source Address : 2001:db8:1:101::2
State              : RX Tracking        Mdt Threshold      : 0
===============================================================================
PIM RSVP Spmsi Interfaces : 2
===============================================================================
*A:Dut-C#
*A:Dut-C# show router 21 pim s-pmsi detail
===============================================================================
PIM LDP Spmsi tunnels
===============================================================================
LSP ID             : 0
Root Addr          : 10.20.1.4          Spmsi IfIndex      : 1030144
Number of VPN SGs  : 1                  Uptime             : 0d 00:03:35
VPN Group Address  : 239.100.0.0
VPN Source Address : 10.1.101.2
State              : RX Tracking        Mdt Threshold      : 0
===============================================================================
PIM LDP Spmsi tunnels
===============================================================================
LSP ID             : 0
Root Addr          : 10.20.1.4          Spmsi IfIndex      : 1030144
Number of VPN SGs  : 1                  Uptime             : 0d 00:03:34
VPN Group Address  : ff0e:db8:225:100::
VPN Source Address : 2001:db8:1:101::2
State              : RX Tracking        Mdt Threshold      : 0
===============================================================================
PIM LDP Spmsi Interfaces : 2
===============================================================================
*A:Dut-C#
Sample output TX tracking for RSVP S-PMSI tunnel detail 
*A:Dut-C# show router 1 pim s-pmsi detail
===============================================================================
PIM RSVP Spmsi tunnels
===============================================================================
P2MP ID            : 1                  Tunnel ID          : 61442
Ext Tunnnel Addrs  : 10.20.1.4          Spmsi IfIndex      : 74230
Number of VPN SGs  : 1                  Uptime             : 0d 00:05:11
VPN Group Address  : 239.100.0.0
VPN Source Address : 10.1.101.2
State              : TX Join Pending    Mdt Threshold      : 1
Join Timer         : N/A                Holddown Timer     : 0d 00:00:47
Receiver Count     : 4
===============================================================================
PIM RSVP Spmsi tunnels
===============================================================================
P2MP ID            : 1                  Tunnel ID          : 61443
Ext Tunnnel Addrs  : 10.20.1.4          Spmsi IfIndex      : 74231
Number of VPN SGs  : 1                  Uptime             : 0d 00:05:10
VPN Group Address  : ff0e:225:100::
VPN Source Address : 2001:db8:1:101::2
State              : TX Join Pending    Mdt Threshold      : 1
Join Timer         : N/A                Holddown Timer     : 0d 00:00:50
Receiver Count     : 4
===============================================================================
PIM RSVP Spmsi Interfaces : 2
===============================================================================
*A:Dut-C#
*A:Dut-D# show router 21 pim s-pmsi detail
===============================================================================
PIM LDP Spmsi tunnels
===============================================================================
LSP ID             : 8194
Root Addr          : 10.20.1.4          Spmsi IfIndex      : 74228
Number of VPN SGs  : 1                  Uptime             : 0d 00:05:56
VPN Group Address  : 239.100.0.0
VPN Source Address : 10.1.101.2
State              : TX Join Pending    Mdt Threshold      : 1
Join Timer         : N/A                Holddown Timer     : 0d 00:00:02
Receiver Count     : 4
===============================================================================
PIM LDP Spmsi tunnels
===============================================================================
LSP ID             : 8195
Root Addr          : 10.20.1.4          Spmsi IfIndex      : 74229
Number of VPN SGs  : 1                  Uptime             : 0d 00:05:55
VPN Group Address  : ff0e:db8:225:100::
VPN Source Address : 2001:db8:1:101::2
State              : TX Join Pending    Mdt Threshold      : 1
Join Timer         : N/A                Holddown Timer     : 0d 00:00:05
Receiver Count     : 4
===============================================================================
PIM LDP Spmsi Interfaces : 2
===============================================================================
*A:Dut-D#
Table 18. Output fields: S-PMSI

Label

Description

MD Grp Address

Displays the IP multicast group address for which this entry contains information

MD Src Address

Displays the source address of the multicast sender

A value of 0 (zero) indicates 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

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

Egress Fwding Rate

Displays the egress forwarding rate for the S-PMSI

VPN Group Address

Displays the VPN group address for the S-PMSI

VPN Source Address

Displays the VPN source address for the S-PMSI

Expiry Timer

Displays the minimum time remaining before this S_PMSI is aged out

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

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

Context

show>router>pim

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command displays statistics for a particular PIM instance.

Parameters
ip-int-name

Only displays the interface information associated with the specified IP interface name.

int-ip-address

Only displays the interface information associated with the specified IP address.

mpls-if-name

Identifies the system created IP-MPLS tunnel interfaces, when using NG-MVPN with BGP based signaling and using P2MP LSPs setup using RSVP or mLDP.

family

Displays either IPv4 or IPv6 information.

Output

The following output is an example of PIM statistics information, and Output fields: PIM statistics describes the output fields.

Sample output 
A:dut-g>show>router>pim# statistics

=================================================================
PIM Statistics ipv4
=================================================================
Message Type        Received       Transmitted    Rx Errors
-----------------------------------------------------------------
Hello               9690           9735           0
Join Prune          2441           6855           0
Asserts             589            0              0
Register            0              0              0
Null Register       0              0              0
Register Stop       0              0              0
BSM                 0              0              0
Total Packets       12720          16590
-------------------------------------------------------------------------------
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 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
PDU Drops on Non-PIM/Down Intf    : 0
-------------------------------------------------------------------------------
Source Group Statistics
-------------------------------------------------------------------------------
(S,G)                             : 435
(*,G)                             : 251
(*,*,RP)                          : 0
=================================================================
A:dut-g>show>router>pim#
Table 19. Output fields: PIM statistics

Label

Description

PIM Statistics

Displays the PIM statistics for a particular interface

Message Type

Displays the type of message

Hello — displays the number of PIM Hello messages received or transmitted on this interface

Join Prune — displays the number of PIM join prune messages received or transmitted on this interface

Asserts — displays the number of PIM assert messages received or transmitted on this interface

Register — displays the number of register messages received or transmitted on this interface

Null Register — displays the number of PIM null register messages received or transmitted on this interface

Register Stop — displays the number of PIM register stop messages received or transmitted on this interface

BSM — displays the number of PIM Bootstrap messages (BSM) received or transmitted on this interface

Candidate RP Adv — displays the number of candidate RP advertisements

Total Packets — displays the total number of packets transmitted and received on this interface

Received

Displays the number of messages received on this interface

Transmitted

Displays the number of multicast data packets transmitted on this interface

Rx Errors

Displays the total number of receive errors

General Interface Statistics

Displays the general PIM interface statistics

Register TTL Drop

Displays the number of multicast data packets that could not be encapsulated in Register messages because the time to live (TTL) was zero

Tx Register MTU Drop

Displays the number of Bootstrap messages received on this interface but were dropped

Rx Invalid Register

Displays the number of invalid PIM register messages received on this interface

Rx Neighbor Unknown

Displays 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

Displays the number of PIM messages received on this interface that were discarded because of bad checksum

Rx Bad Encoding

Displays the number of PIM messages with bad encodings received on this interface

Rx Bad Version Discard

Displays the number of PIM messages with bad versions received on this interface

Rx CRP No Router Alert

Displays the number of candidate RP advertisements (C-RP-Adv) received on this interface that had no router alert option set

Rx Invalid Join Prune

Displays the number of invalid PIM join prune messages received on this interface

Rx Unknown PDU Type

Displays the number of packets received with an unsupported PIM type

Join Policy Drops

Displays the number of times the join policy match resulted in dropping PIM join-prune message or one of the source group contained in the message

Register Policy Drops

Displays the number of times the register policy match resulted in dropping PIM register message

Bootstrap Import Policy Drops

Displays the number of Bootstrap messages received on this interface but were dropped because of Bootstrap import policy

Bootstrap Export Policy Drops

Displays the number of Bootstrap messages that were not transmitted on this interface because of Bootstrap export policy

Source Group Statistics

Displays the source group statistics

(S,G)

Displays the number of entries in which the type is (S,G)

(*,G)

Displays the number of entries in which the type is (*,G)

(*,*,RP)

Displays the number of entries in which the type is (*, *, rp)
status
Syntax

status [detail] [family]

Context

show>router>pim

Platforms

Supported on all 7210 SAS platforms as described in this document.

Description

This command displays PIM status. The Oper Status reflects the combined operational status of IPv4 or IPv6 PIM protocol status. If both are down, Oper Status is reflected as down. If IPv4 or IPv6 reflects up, the Oper Status reflects 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
detail

Displays detailed status information.

family

Displays either IPv4 or IPv6 information.

Output

The following output is an example of PIM status information, and Output fields: PIM status describes the output fields.

Sample output 
A:dut-g>show>router>pim# status

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

Candidate BSR
    Admin State                   : Down
    Oper State                    : Down
    Address                       : None
    Priority                      : 0
    Hash Mask Length              : 30

SSM-Default-Range                 : Enabled
SSM-Assert-Comp-Mode              : Disabled
SSM-Group-Range
    None

MC-ECMP-Hashing                   : Disabled

Policy                            : None

RPF Table                         : rtable-u

Non-DR-Attract-Traffic            : Disabled
===============================================================================
A:dut-g>show>router>pim#
Table 20. Output fields: PIM status

Label

Description

Admin State

Displays the administrative status of PIM

Oper State

Displays the current operating state of this PIM protocol instance

BSR State

Displays the state of the router with respect to the Bootstrap mechanism

Address

Displays the address of the elected Bootstrap router

Expiry Time

Displays the time remaining before the router sends the next Bootstrap message

Priority

Displays the priority of the elected Bootstrap router. The higher the value, the higher the priority.

Hash Mask Length

Displays the hash mask length of the Bootstrap router

Up Time

Displays the time since the current E-BSR became the Bootstrap router

RPF Intf towards

Displays the RPF interface toward the elected BSR. The value is zero if there is no elected BSR in the network.

Address

Displays the address of the candidate BSR router

Expiry Time

Displays the time remaining before the router sends the next Bootstrap message.

Priority

Displays the priority of the Bootstrap router. The higher the value, the higher the priority.

Hash Mask Length

Displays the hash mask length of the candidate Bootstrap router

Up Time

Displays the time since becoming the Bootstrap router

Admin State

Displays the administrative status of CRP

Oper State

Displays the current operating state of the C-RP mechanism

Address

Displays the local RP address

Priority

Displays the CRP priority for becoming an RP. A value of 0 is the highest priority

Holdtime

Displays the hold time of the candidate RP. It is used by the Bootstrap router to timeout the RP entries if it does not listen to another CRP advertisement within the hold-time period.

Policy

Displays the PIM policies for a particular PIM instance

Default Group

Displays the default core group address

RPF Table

Displays the route table used for RPF check

MC-ECMP-Hashing

Displays whether hash-based multicast balancing of traffic over ECMP links is enabled
tunnel-interface
Syntax

tunnel-interface [ip-int-name | mt-int-name | int-ip-address] [group [group-ip-address] source ip-address] [type {starstarrp | starg | sg}] [detail] [family]

Context

show>router>pim

Platforms

7210 SAS-T (network mode only), 7210 SAS-R6, 7210 SAS-R12, and 7210 SAS-Mxp.

Description

This command displays PIM tunnel interface information.

Parameters
ip-int-name

Specifies the IP interface name. A string up to 32 characters.

mt-int-name

Specifies the Multicast Tunnel (MT) interface for a VPRN.

int-ip-address

Specifies the interface IPv4 or IPv6 address.

group-ip-address

Specifies the IP multicast group address, or 0.

ip-address

Specifies the source or RP IPv4 or IPv6 address.

type

Specifies the type of entry.

Values

starstarrp, starg, sg

detail

Displays detailed interface information.

family

Specifies the IPv4 or IPv6 address family.

Output

The following output is an example of PIM tunnel interface information.

Sample output 
*A:Dut-C# show router pim tunnel-interface 
==================================================================================
PIM Interfaces ipv4
===============================================================================
Interface                        Originator Address   Adm  Opr  Transport Type
-------------------------------------------------------------------------------
mpls-if-73728                    N/A                  Up   Up   Tx-IPMSI
mpls-if-73729                    N/A                  Up   Up   Tx-IPMSI
mpls-if-73730                    N/A                  Up   Up   Tx-IPMSI
mpls-if-73731                    N/A                  Up   Up   Tx-IPMSI
mpls-if-73732                    N/A                  Up   Up   Tx-IPMSI
-------------------------------------------------------------------------------
Interfaces : 5
===============================================================================
mvpn
Syntax

mvpn

Context

show>router

Platforms

7210 SAS-T (network mode only), 7210 SAS-R6, 7210 SAS-R12, 7210 SAS-Mxp, and 7210 SAS-Sx/S 1/10GE (in standalone mode)

Description

This command displays multicast VPN information for the specified router instance.

Output

The following output is an example of PIM MVPN information.

Sample output 
*A:7210SAS# show router 10 mvpn 

===============================================================================
MVPN 10 configuration data
===============================================================================
signaling : Bgp auto-discovery : Default
UMH Selection : Highest-Ip intersite-shared : Enabled
vrf-import : N/A
vrf-export : N/A
vrf-target : unicast
C-Mcast Import RT : target:10.16.16.16:3
 
ipmsi : ldp
i-pmsi P2MP AdmSt : Up 
 
spmsi : ldp
s-pmsi P2MP AdmSt : Up 
max-p2mp-spmsi : 251 
data-delay-interval: 3 seconds 
enable-asm-mdt : N/A 
data-threshold : 224.0.0.0/4 --> 1 kbps
 
===============================================================================
*A:7210SAS# 
mvpn-list
Syntax

mvpn-list

Context

show>router

Platforms

7210 SAS-T (network mode only), 7210 SAS-R6, 7210 SAS-R12, 7210 SAS-Mxp, and 7210 SAS-Sx/S 1/10GE (in standalone mode)

Description

This command displays multicast VPN list information for the specified router instance.

Output

The following output is an example of PIM MVPN list information.

Sample output 
A:7210SAS# show router mvpn-list 

===============================================================================
MVPN List
===============================================================================
VprnID Sig A-D iPmsi/sPmsi GroupAddr/Lsp-Template (S,G)/(*,G)
-------------------------------------------------------------------------------
10 Bgp Default Mldp/Mldp N/A 512/0
20 Bgp Default Mldp/Mldp N/A 512/0
30 Bgp Default None/None N/A 0/0
-------------------------------------------------------------------------------
Total PIM I-PMSI tunnels : 0
Total RSVP I-PMSI tunnels : 0
Total MLDP I-PMSI tunnels : 2
Total PIM TX S-PMSI tunnels : 0
Total RSVP TX S-PMSI tunnels : 0
Total MLDP TX S-PMSI tunnels : 502
Total PIM RX S-PMSI tunnels : 0
Total RSVP RX S-PMSI tunnels : 0
Total MLDP RX S-PMSI tunnels : 0
Total (S,G) : 1024
Total (*,G) : 0
Total Mvpns : 3
Sig = Signal Pim-a = pim-asm Pim-s = pim-ssm A-D = Auto-Discovery
===============================================================================
*A:7210SAS# 
tunnel-table
Syntax

tunnel-table [ip-address [/mask]] [protocol | sdp sdp-id]

tunnel-table [summary]

Context

show>router

Platforms

Supported on all 7210 SAS platforms as described in this document.

Description

This command displays tunnel table information.

Parameters
protocol

Specifies the protocol.

Values

bgp, ldp, rsvp, sdp

sdp-id

Specifies the SDP ID.

Values

1 to 17407

Output

The following output is an example of PIM tunnel table information.

Sample output 
*A:Dut-C# show router pim tunnel-interface 
==================================================================================
PIM Interfaces ipv4
===============================================================================
Interface                        Originator Address   Adm  Opr  Transport Type
-------------------------------------------------------------------------------
mpls-if-73728                    N/A                  Up   Up   Tx-IPMSI
mpls-if-73729                    N/A                  Up   Up   Tx-IPMSI
mpls-if-73730                    N/A                  Up   Up   Tx-IPMSI
mpls-if-73731                    N/A                  Up   Up   Tx-IPMSI
mpls-if-73732                    N/A                  Up   Up   Tx-IPMSI
-------------------------------------------------------------------------------
Interfaces : 5
===============================================================================
MSDP commands
group
Syntax

group [group-name] [detail]

Context

show>router>msdp

Platforms

7210 SAS-Sx/S 1/10GE (standalone)

Description

This command displays information about MSDP groups.

Parameters
group-name

Displays information about the specified group name, up to 32 characters. If no group-name is specified, information about all group names displays.

detail

Displays detailed MSDP group information.

Output

The following output is an example of MSDP group information, and Output fields: MSDP group describes the output fields.

Sample output 
*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 21. Output fields: MSDP group

Label

Description

Group Name

Displays the MSDP group name.

Mode

Displays the groups of peers in a full mesh topology to limit excessive flooding of SA messages to neighboring peers.

Act Srcs

Displays the configured maximum number of active source messages that are 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 at which the messages are read from the TCP session.

Receive Msg Time

Displays the time of MSDP messages that are read from the TCP session within the configured number of seconds.

Receive Msg Thd

Displays the configured threshold number of MSDP messages that can be processed before the MSDP message rate limiting function.

SA Limit

Displays the SA limit.
peer
Syntax

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

Context

show>router>msdp

Platforms

7210 SAS-Sx/S 1/10GE (standalone)

Description

This command displays information about MSDP peers.

Parameters
ip-address

Displays information about the specified IP address. If no IP address is specified, information about all MSDP IP addresses displays.

group-name

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

detail

Displays detailed MSDP peer information.

Output

The following output is an example of MSDP peer information, and Output fields: MSDPpeer describes the output fields.

Sample output 
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:131008    
-----------------------------------------------------------------------------
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 22. Output fields: MSDPpeer

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 Learn

Displays the number of SA messages learned through a peer.
source
Syntax

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

Context

show>router>msdp

Platforms

7210 SAS-Sx/S 1/10GE (standalone)

Description

This command displays the discovery method for this multicast source.

Parameters
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 Output fields: MSDP source describes the output fields.

Sample output 
*A:Dut-G>config>router>msdp>source# /show  router  msdp source 
===============================================================================
MSDP Sources
===============================================================================
Source             Type         SA Limit   Num Excd   Last Exceeded
-------------------------------------------------------------------------------
100.112.1.2/32     Configured   10         0          N/A
-------------------------------------------------------------------------------
Sources : 1
===============================================================================
Table 23. Output fields: MSDP source

Label

Description

Source

Displays the source address.

Type

Displays the source type.

SA Limit

Displays the limit of SA messages allowed.

Num Excd

Displays the number of SA messages that have exceeded the limit.

Last Exceeded

Displays the date and time that the limit was last exceeded.

Sources

Displays the number of sources.
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

Platforms

7210 SAS-Sx/S 1/10GE (standalone)

Description

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

group ip-address

Displays information about the specified group IP address.

detail

Displays detailed MSDP SA information.

Output

The following output is an example of MSDP SA information, and Output fields: MSDP source-active describes the output fields.

Sample output 
A:ALA-48# show router msdp source-active
===============================================================================
MSDP Source Active Info
===============================================================================
Grp Address      Src Address      Origin RP        Peer Address State Timer
-------------------------------------------------------------------------------
239.100.0.0      10.112.1.2      10.20.1.1        10.20.1.1 69        
239.100.0.1      10.112.1.2      10.20.1.1        10.20.1.1 69        
239.100.0.2      10.112.1.2      10.20.1.1        10.20.1.1 69        
239.100.0.3      10.112.1.2      10.20.1.1        10.20.1.1 69        
239.100.0.4      10.112.1.2      10.20.1.1        10.20.1.1 69        
239.100.0.5      10.112.1.2      10.20.1.1        10.20.1.1 69        
239.100.0.6      10.112.1.2      10.20.1.1        10.20.1.1 69        
239.100.0.7      10.112.1.2      10.20.1.1        10.20.1.1 69        
239.100.0.8      10.112.1.2      10.20.1.1        10.20.1.1 69        
239.100.0.9      10.112.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.100.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.100.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.100.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.100.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.100.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.100.0.5        Source Address     : 10.112.1.2      
Origin RP          : 10.20.1.1          Peer Address       : 10.20.1.1        
Origin RP          : 10.20.1.1          Peer Address       : 10.20.1.1        
State Timer        : 64                 Up Time            : 48d 18:22:29     
Group Address      : 239.100.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.100.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.100.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 24. Output fields: MSDP source-active

Label

Description

Grp Address

Displays the IP address of the group.

Src Address

Displays the IP address of the source.

Origin RP

Displays the origination RP address.

Peer Address

Displays the address of the peer.

State Timer

Displays the time-out value. If the value reaches zero, the SA 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

Platforms

7210 SAS-Sx/S 1/10GE (standalone)

Description

This command displays SA messages rejected by MSDP.

Parameters
peer-group 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 SA 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 SA entry was last received.

Output

The following output is an example of MSDP rejected SA information, and Output fields: MSDP source-active rejected describes the output fields.

Sample output 
*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.100.0.1     10.0.0.1       10.20.0.1       239.0.0.1        Import Policy
239.100.0.2     10.0.0.2       10.20.0.2       239.0.0.2        Export Policy
239.100.0.3     10.0.0.3       10.20.0.3       239.0.0.3        RPF Failure
239.100.0.4     10.0.0.4       10.20.0.4       239.0.0.4        Limit Exceeded
239.100.0.5     10.0.0.5       10.20.0.5       239.0.0.5        Limit Exceeded
239.100.0.6     10.0.0.6       10.20.0.6       239.0.0.6        Limit Exceeded
239.100.0.7     10.0.0.7       10.20.0.7       239.0.0.7        Limit Exceeded
-------------------------------------------------------------------------------
SA Rejected Entries : 7
===============================================================================
*A:ALA-48#
Table 25. Output fields: MSDP source-active rejected

Label

Description

Grp Address

Displays the IP address of the group.

Src Address

Displays the IP address of the source.

Origin RP

Displays the origination rendezvous point (RP) address.

Peer Address

Displays the address of the peer.

Reject Reason

Displays the reason why this source active entry is rejected.
statistics
Syntax

statistics [peer ip-address]

Context

show>router>msdp

Platforms

7210 SAS-Sx/S 1/10GE (standalone)

Description

This command displays statistics information related to an MSDP peer.

Parameters
ip-address

Displays information about the specified peer IP address.

Output

The following output is an example of MSDP statistics information, and Output fields: MSDP statistics describes the output fields.

Sample output 
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 26. Output fields: MSDP statistics

Label

Description

Last State Change

Displays the date and time the peer state changed.

RPF Failures

Displays the number of RPF failures.

SA Msgs Sent

Displays the number of SA messages sent.

SA req. Msgs Sent

Displays the number of SA request messages sent.

SA res. Msgs Sent

Displays the number of SA response messages sent.

KeepAlive Msgs Sent

Displays the number of keepalive messages sent.

Unknown Msgs Sent

Displays the number of unknown messages received.

Last message Peer

Displays the time the last message was received from the peer.

Remote Closes

Displays the number of times the remote peer close.

SA Msgs Recvd

Displays the number of SA messages received.

SA req. Msgs Recvd

Displays the number of SA request messages received.

SA res. Msgs Recvd

Displays the number of SA response messages received.

KeepAlive Msgs Recd

Displays the number of keepalive messages received.

Error Msgs Recvd

Displays the number of unknown messages received.
status
Syntax

status

Context

show>router>msdp

Platforms

7210 SAS-Sx/S 1/10GE (standalone)

Description

This command displays MSDP status information.

Output

The following output is an example of MSDP status information, and Output fields: MSDP status describes the output fields.

Sample output 
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 27. Output fields: MSDP status

Label

Description

Admin State

Displays the administrative state.

Local Address

Displays the local IP address.

Active Src Limit

Displays the active source limit.

Act Src Lim Excd

Displays the active source limit which has been 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

Displays the policy to export the SA state from the SA list into MSDP.

Data Encapsulation

Displays the RP using MSDP to encapsulate multicast data received in MSDP register messages inside forwarded MSDP SA messages.

Rate

Displays the receive message rate.

Time

Displays the receive message time.

Threshold

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

RPF Table

Displays the name of the reverse path forwarding table.

Last msdp Enabled

Displays the time the last MSDP was triggered.

Clear commands

database
Syntax

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

database grp-interface interface-name [fwd-service service-id]

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

database host [ip-address]

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

Context

clear>router>igmp

Platforms

Supported on all 7210 SAS platforms as described in this document.

Description

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

Parameters
interface ip-int-name

Clears the IGMP or PIM database on the specified interface.

interface ip-address

Clears the IGMP or PIM database on the specified IP address.

group group-ip-address

Clears the multicast group address (ipv4 or ipv6) or zero in the specified address group.

source ip-address

Clears the IGMP or PIM database from the specified source IP address.

database
Syntax

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

Context

clear>router>pim

Platforms

Supported on all 7210 SAS platforms as described in this document.

Description

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

Parameters
interface ip-int-name

Clears the IGMP or PIM database on the specified interface.

interface ip-address

Clears the IGMP or PIM database on the specified IP address.

group group-ip-address

Clears the multicast group address (ipv4) or zero in the specified address group.

source ip-address

Clears the IGMP or PIM database from the specified source IP address.

family

Clears IPv4 information.

statistics
Syntax

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

Context

clear>router>igmp

Platforms

Supported on all 7210 SAS platforms as described in this document.

Description

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

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

Parameters
interface ip-int-name

Clears IGMP statistics on the specified interface.

interface ip-address

Clears IGMP statistics on the specified IP address.

statistics
Syntax

statistics [{[interface ip-int-name | ip-address | mt-int-name]} {[group grp-ip-address [source ip-address]]}] [family]]

Context

clear>router>pim

Platforms

Supported on all 7210 SAS platforms as described in this document.

Description

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

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

Parameters
interface ip-int-name

Clears PIM statistics on the specified interface.

interface ip-address

Clears PIM statistics on the specified IP address.

group grp-ip-address

When only the group address is specified and no source is specified, (*,G) statistics are cleared. When the group address is specified along with the source address, the (S,G) statistics are reset to zero.

source ip-address

When the source address is specified along with the group address, the (S,G) statistics are reset to zero.

family

Clears IPv4 information.

version
Syntax

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

Context

clear>router>igmp

Platforms

Supported on all 7210 SAS platforms as described in this document.

Description

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

Parameters
ip-int-name

Clears IGMP or PIM statistics on the specified interface.

ip-address

Clears IGMP or PIM statistics on the specified IP address.

neighbor
Syntax

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

Context

clear>router>pim

Platforms

Supported on all 7210 SAS platforms as described in this document.

Description

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

Parameters
ip-int-name

Clears PIM neighbor on the specified interface.

ip-address

Clears PIM neighbor on the specified IP address.

family

Clears IPv4 information.

s-pmsi
Syntax

s-pmsi [mdSrcAddr] [mdGrpAddr] [vprnSrcAddr vprnGrpAddr]

Context

clear>router>pim

Platforms

7210 SAS-T (network mode only), 7210 SAS-R6, 7210 SAS-R12, 7210 SAS-Mxp, and 7210 SAS-Sx/S 1/10GE (in standalone mode)

Description

This command clears the PIM selective provider multicast service interface cache.

Parameters
mdSrcAddr

Clears the specified source address used for Multicast Distribution Tree (MDT).

mdGrpAddr

Clears the specified group address used for Multicast Distribution Tree (MDT).

vprnSrcAddr

Clears the specified source address of the multicast sender.

vprnGrpAddr

Clears the specified multicast group address.

msdp
Syntax

msdp

Context

clear>router

Platforms

7210 SAS-Sx/S 1/10GE (standalone)

Description

Commands in this context clear and reset MSDP entities and statistics.

cache
Syntax

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

Context

clear>router>msdp

Platforms

7210 SAS-Sx/S 1/10GE (standalone)

Description

This command clears the MSDP cache.

Parameters
peer ip-address

Clears the cache of the IP address of the peer to which MSDP SA requests for groups matching this entry's group range were sent.

group ip-address

Clears the group IP address of the SA entry.

source ip-address

Clears the source IP address of the SA entry.

originrp ip-address

Clears the origin RP address type of the SA entry.

statistics
Syntax

statistics [peer ip-address]

Context

clear>router>msdp

Platforms

7210 SAS-Sx/S 1/10GE (standalone)

Description

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

Parameters
ip-address

Clears the statistics of the specified IP address.

igmp-snooping
Syntax

igmp-snooping

Context

clear>service>id

Platforms

Supported on all 7210 SAS platforms as described in this document.

Description

Commands in this context clear IGMP snooping-related data.

port-db
Syntax

port-db {sap sap-id | sdp sdp-id:vc-id} [group grp-address [source ip-address]]

Context

clear>service>id>igmp-snooping

Platforms

Supported on all 7210 SAS platforms as described in this document.

Description

This command clears the information from the IGMP snooping port database.

Parameters
sap sap-id

Clears IGMP snooping statistics matching the specified SAP ID and optional encapsulation value. The sap-id can be in one of the following formats:

Encapsulation type

Syntax

Example

null

port-id

1/1/3

dot1q

port-id :qtag1

1/1/3:100

qinq

port-id :qtag1.qtag2

1/1/3:100.200

qtag1, qtag2

Specifies the encapsulation value on the specified port ID.

Values

0 to 4094

sdp sdp-id

Clears only IGMP snooping entries associated with the specified mesh SDP or spoke-SDP. For a spoke-SDP, the VC ID must be specified; for a mesh SDP, the VC ID is optional.

Values

1 to 17407

vc-id

Specifies the virtual circuit ID on the SDP ID for which to clear information.

Values

1 to 4294967295

Default

For mesh SDPs only, all VC IDs

group grp-address

Clears IGMP snooping statistics matching the specified group address.

source ip-address

Clears IGMP snooping statistics matching one particular source within the multicast group.

querier
Syntax

querier

Context

clear>service>id>igmp-snooping

Platforms

Supported on all 7210 SAS platforms as described in this document.

Description

This command clears information from the IGMP snooping queriers for the VPLS service.

statistics
Syntax

statistics [sap sap-id | sdp sdp-id:vc-id]

Context

clear>service>id>igmp-snooping

Platforms

Supported on all 7210 SAS platforms as described in this document.

Description

This command clears IGMP snooping statistics for the VPLS service.

Parameters
sap sap-id

Displays IGMP snooping statistics for a specific SAP. The sap-id can be in one of the following formats:

Encapsulation type

Syntax

Example

null

port-id

1/1/3

dot1q

port-id :qtag1

1/1/3:100

qinq

port-id :qtag1.qtag2

1/1/3:100.200
qtag1, qtag2

Specifies the encapsulation value on the specified port ID.

Values

0 to 4094

sdp sdp-id

Displays the IGMP snooping statistics for a specific spoke or mesh SDP.

Values

1 to 17407

vc-id

Specifies the virtual circuit ID on the SDP ID for which to display information.

Values

1 to 4294967295

Default

For mesh SDPs only, all VC IDs

Debug commands

Debug IGMP commands
interface
Syntax

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

Context

debug>router>igmp

Platforms

Supported on all 7210 SAS platforms as described in this document.

Description

This command enables debugging for IGMP interfaces.

The no form of this command disables the IGMP interface debugging for the specified interface name or IP address.

Parameters
ip-int-name

Displays the information associated with only the specified IP interface name.

ip-address

Displays the information associated with only the specified IP address.

misc
Syntax

[no] misc

Context

debug>router>igmp

Platforms

Supported on all 7210 SAS platforms as described in this document.

Description

This command enables debugging for IGMP miscellaneous.

The no form of this command disables debugging.

Output
Sample output 
A:ALA-CA# debug router igmp misc 
*A:ALA-CA# show debug 
debug
    router 
        igmp
            misc
        exit
    exit
exit
*A:ALA-CA#
packet
Syntax

packet [query | v1-report | v2-report | v3-report | v2-leave] host ip-address

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

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

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

Context

debug>router>igmp

Platforms

Supported on all 7210 SAS platforms as described in this document.

Description

This command enables and disables debugging for IGMP packets.

Parameters
query

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

v1-report

Specifies to log IGMP V1 reports transmitted and received on this interface.

v2-report

Specifies to log IGMP V2 reports transmitted and received on this interface.

v3-report

Specifies to log IGMP V3 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 only the specified IP interface name.

ip-address

Displays the information associated with only the specified IP address.

Debug PIM commands
adjacency
Syntax

[no] adjacency

Context

debug>router>pim

Platforms

Supported on all 7210 SAS platforms as described in this document.

Description

This command enables and disables debugging for PIM adjacencies.

all
Syntax

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

no all

Context

debug>router>pim

Platforms

Supported on all 7210 SAS platforms as described in this document.

Description

This command enables and disables debugging for all the PIM modules.

Parameters
group grp-ip-address

Debugs information associated with all PIM modules.

Values

IPv4 address

source ip-address

Debugs information associated with all PIM modules.

Values

IPv4 address

detail

Debugs detailed information on all PIM modules.

assert
Syntax

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

no assert

Context

debug>router>pim

Platforms

Supported on all 7210 SAS platforms as described in this document.

Description

This command enables and disables debugging for PIM assert mechanism.

Parameters
group grp-ip-address

Debugs information associated with the PIM assert mechanism.

Values

multicast group address (ipv4)

source ip-address

Debugs information associated with the PIM assert mechanism.

Values

source address (ipv4)

detail

Debugs detailed information on the PIM assert mechanism.

bgp
Syntax

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

no bgp

Context

debug>router>pim

Platforms

Supported on all 7210 SAS platforms as described in this document.

Description

This command enables and disables debugging for PIM/BGP specific interoperation.

Parameters
ip-address

Debugs BGP information associated with the specified source.

Values

source address (ipv4)

group-ip-address

Debugs BGP information associated with the specified group.

Values

group address (ipv4)

peer-ip-address

Debugs BGP information associated with the specified peer.

Values

peer address (ipv4)

bsr
Syntax

bsr [detail]

no bsr

Context

debug>router>pim

Platforms

Supported on all 7210 SAS platforms as described in this document.

Description

This command enables debugging for PIM bootstrap mechanism.

The no form of this command disables debugging.

Parameters
detail

Debugs detailed information on the PIM bootstrap mechanism.

data
Syntax

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

no data

Context

debug>router>pim

Platforms

Supported on all 7210 SAS platforms as described in this document.

Description

This command enables and disables debugging for PIM data exception.

Parameters
group grp-ip-address

Debugs information associated with the specified data exception.

Values

multicast group address (ipv4)

source ip-address

Debugs information associated with the specified data exception.

Values

source address (ipv4)

detail

Debugs detailed IP data exception information.

db
Syntax

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

no db

Context

debug>router>pim

Platforms

Supported on all 7210 SAS platforms as described in this document.

Description

This command enables and disables debugging for PIM database.

Parameters
group grp-ip-address

Debugs information associated with the specified database.

Values

multicast group address (ipv4 or ipv6) or zero

source ip-address

Debugs information associated with the specified database.

Values

source address (ipv4 or ipv6)

detail

Debugs detailed IP database information.

dynmldp
Syntax

dynmldp [detail]

no dynmldp

Context

debug>router>pim

Platforms

7210 SAS-T (network mode only), 7210 SAS-R6, 7210 SAS-R12, and 7210 SAS-Mxp.

Description

This command enables and disables debugging for dynamic MLDP.

Parameters
detail

Debugs detailed dynamic MLDP information.

interface
Syntax

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

no interface

Context

debug>router>pim

Platforms

Supported on all 7210 SAS platforms as described in this document.

Description

This command enables and disables debugging for PIM interface.

Parameters
ip-int-name

Debugs the information associated with the specified IP interface name.

Values

IPv4 interface address

ip-address

Debugs the information associated with the specified IP address.

detail

Debugs detailed IP interface information.

jp
Syntax

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

no jp

Context

debug>router>pim

Platforms

Supported on all 7210 SAS platforms as described in this document.

Description

This command enables and disables debugging for PIM Join-Prune mechanism.

Parameters
group grp-ip-address

Debugs information associated with the specified Join-Prune mechanism.

Values

multicast group address (ipv4) or zero

source ip-address

Debugs information associated with the specified Join-Prune mechanism.

Values

source address (ipv4)

detail

Debugs detailed Join-Prune mechanism information.

mrib
Syntax

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

no mrib

Context

debug>router>pim

Platforms

Supported on all 7210 SAS platforms as described in this document.

Description

This command enables and disables debugging for PIM MRIB.

Parameters
group grp-ip-address

Debugs information associated with the specified PIM MRIB.

Values

multicast group address (ipv4)

source ip-address

Debugs information associated with the specified PIM MRIB.

Values

source address (ipv4)

detail

Debugs detailed MRIB information.

msg
Syntax

msg [detail]

no msg

Context

debug>router>pim

Platforms

Supported on all 7210 SAS platforms as described in this document.

Description

This command enables and disables debugging for PIM messaging.

Parameters
detail

Debugs detailed messaging information.

mvpn-rtcache
Syntax

mvpn-rtcache [group grp-ip-address] [peer ip-address]

no mvpn-rtcache

Context

debug>router>pim

Platforms

7210 SAS-T (network mode only), 7210 SAS-R6, 7210 SAS-R12, 7210 SAS-Mxp, and 7210 SAS-Sx/S 1/10GE (in standalone mode)

Description

This command enables and disables debugging for the PIM MVPN route cache.

Parameters
grp-ip-address

Debugs information associated with the specified group.

Values

multicast group address (ipv4) or zero

peer-ip-address

Debugs information associated with the specified peer.

Values

peer address (ipv4)

packet
Syntax

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

no packet

Context

debug>router>pim

Platforms

Supported on all 7210 SAS platforms as described in this document.

Description

This command enables and disables debugging for PIM packets.

Parameters
hello | register | register-stop | jp | bsr | assert | crp

PIM packet types.

ip-int-name

Debugs the information associated with the specified IP interface name.

Values

IPv4 interface address

ip-address

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

red
Syntax

red [detail]

no red

Context

debug>router>pim

Platforms

Supported on all 7210 SAS platforms as described in this document.

Description

This command enables and disables debugging for PIM redundancy messages to the standby CPM.

Parameters
detail

Displays detailed redundancy information.

register
Syntax

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

no register

Context

debug>router>pim

Platforms

Supported on all 7210 SAS platforms as described in this document.

Description

This command enables and disables debugging for PIM register mechanism.

Parameters
group grp-ip-address

Debugs information associated with the specified PIM register.

Values

multicast group address (ipv4)

source ip-address

Debugs information associated with the specified PIM register.

Values

source address (ipv4)

detail

Debugs detailed register information.

rtm
Syntax

rtm [detail]

no rtm

Context

debug>router>pim

Platforms

Supported on all 7210 SAS platforms as described in this document.

Description

This command enables the disables debugging for PIM RTM.

Parameters
detail

Debugs detailed RTM information.

s-pmsi
Syntax

s-pmsi [{vpnSrcAddr [vpnGrpAddr]} [mdSrcAddr]] [detail]

no s-pmsi

Context

debug>router>pim

Platforms

7210 SAS-T (network mode only), 7210 SAS-R6, 7210 SAS-R12, 7210 SAS-Mxp, and 7210 SAS-Sx/S 1/10GE (in standalone mode)

Description

This command enables debugging for PIM selective provider multicast service interface.

The no form of this command disables the debugging.

Parameters
vpnSrcAddr

Specifies the VPN source address.

vpnGrpAddr

Specifies the VPN group address

mdSrcAddr

Specifies the source address of the multicast domain.

detail

Displays detailed information for selective PMSI.

tunnel-interface
Syntax

tunnel-interface [rsvp-p2mp lsp-name] [sender ip-address] [detail]

tunnel-interface [ldp-p2mp p2mp-id] [sender ip-address] [detail]

no tunnel-interface [rsvp-p2mp lsp-name] [sender ip-address]

no tunnel-interface [ldp-p2mp p2mp-id] [sender ip-address]

Context

debug>router>pim

Platforms

7210 SAS-T (network mode only), 7210 SAS-R6, 7210 SAS-R12, and 7210 SAS-Mxp.

Description

This command enables and disables the debugging for PIM tunnel interfaces.

Parameters
lsp-name

Specifies the LSP for RSVP P2MP.

ip-address

Specifies the IP address of the sender.

p2mp-id

Specifies the P2MP ID for LDP P2MP.

detail

Displays detailed information for PIM tunnel interfaces.

Debug MSDP commands
msdp
Syntax

[no] msdp

Context

debug>router

Platforms

7210 SAS-Sx/S 1/10GE (standalone)

Description

This command enables debugging for MSDP.

The no form of the command disables MSDP debugging.

packet
Syntax

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

Context

debug>router>msdp

Platforms

7210 SAS-Sx/S 1/10GE (standalone)

Description

This command enables debugging for MSDP packets.

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

Platforms

7210 SAS-Sx/S 1/10GE (standalone)

Description

This command enables debugging for MSDP PIM.

The no form of this 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

Platforms

7210 SAS-Sx/S 1/10GE (standalone)

Description

This command enables debugging for the MSDP route table manager (RTM).

The no form of this 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 sadb

Context

debug>router>msdp

Platforms

7210 SAS-Sx/S 1/10GE (standalone)

Description

This command enables debugging for MSDP SA requests.

The no form of this 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 RP address.