Multicast
This chapter provides information about Protocol Independent Multicast (PIM).
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 will be transmitting on the same channel (except in the case of malicious acts such as address spoofing). This makes it harder to spam an SSM channel than 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 contains information about the multicast protocols required to support a Nokia router in the 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. Three 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 desired 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 will then treat the query as if there is no EXCLUDE definition present.
SSM groups
IGMPv3 permits 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 permits 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 will perform a (*,G) join as normal, but can combine this with a prune for each of the sources the receiver does not wish to receive.
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's 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 will eventually time out.
A multicast data sender starts sending data destined for a multicast group. The sender's 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 or not 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 will switch to native forwarding. To do this, when the RP receives a register-encapsulated data packet from source S on group G, it will initiate 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'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 will continue being encapsulated to the RP. When packets from S also start to arrive natively at the RP, the RP receives two copies of each of these packets. At this point, the RP starts to discard the encapsulated copy of these packets and sends a register-stop message back to S's DR to prevent the DR unnecessarily encapsulating the packets. At the end of phase 2, traffic will be flowing natively from S along a source-specific tree to the RP and from there along the shared tree to the receivers. Where the two trees intersect, traffic can transfer from the shared RP tree to the shorter source tree.
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's 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'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 proper operation, every PIM-SM router within a PIM domain must be able to map a particular global-scope multicast group address to the same RP. If this is not possible, black holes can appear (this is where some receivers in the domain cannot receive some groups). A domain in this context is a contiguous set of routers that all implement PIM and are configured to operate within a common boundary.
The bootstrap router (BSR) mechanism provides a way in which viable group-to-RP mappings can be created and distributed to all the PIM-SM routers in a domain. Each candidate BSR originates bootstrap messages (BSMs). 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 will be detected and the mapping tables will be modified so that the unreachable RP is no longer used and the new tables will be rapidly distributed throughout the domain.
PIM-SM routing policies
Multicast traffic can be restricted from certain source addresses by creating routing policies. Join messages can be filtered using import filters. PIM join policies can be used to reduce denial of service attacks and subsequent PIM state explosion in the router and to remove unwanted multicast streams at the edge of the network before 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.
Match condition |
Matches |
|---|---|
Interface |
The RTR interface by name |
Neighbor |
The neighbors source address in the IP header |
Group Address |
The multicast group address in the join/prune message |
Source Address |
The source address in the join/prune message |
PIM register messages are sent by the first hop designated router that has a direct connection to the source. This serves a dual purpose:
It notifies the RP that a source has active data for the group.
It 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 will ignore 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.
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 due to 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).
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:
S1 sends a multicast packet.
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.
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.
RP1 is configured with RP2 and RP3’s 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.
RP1 sends a copy of the register message from S1’s DR to both RP2 and RP3. RP1 uses its own IP address as the source address for the PIM register message.
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.
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.
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 will be sent when the next register is received. If RP2 decides not to wait, the register-stop message is sent now.
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.
RP3 receives the register message from RP1 and de-encapsulates it, but, since there are no receivers joined for the group, it can discard the packet.
RP3 sends a register-stop message back to RP1.
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.
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.
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 preceding steps, but it is RP3 that sends a copy of the register originated by S2’s 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 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:
For a specific S, G get all possible nHops.
Sort these nHops based on nHop addresses.
xor S and G addresses.
Hash the xor address over a number of PIM next hops.
Use the hash value obtained in step 4, and get that element, in the sorted list obtained in step 2, as the preferred nHop.
If this element is not available or it is not a PIM nHop (PIM neighbor), the next available next hop is chosen.
PIM status
The following is a sample PIM status indicating ECMP hashing is disabled.
*B:BB# 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 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
PIM joins over multiple ECMP paths
The following is a sample distribution of PIM joins over multiple ECMP paths.
*A:BA# show router 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
===============================================================================
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’s network interface), that router sends the completed response to the response destination (receiver) address specified in the trace query.
If a multicast router along the path does not implement the 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 desired interface for the path from the source. In such cases, the desired 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.
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 the 7210 SAS:
7210 SAS platforms can be used as RPs.
Static RP configuration using PIM BSR messages is supported.
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 shared tree. However, the traffic rate threshold cannot be configured to trigger the switch over.
RFP checks 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, and PIM.
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 wishes 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)
Enabled IGMP and PIM configuration output
A:LAX>config>router>igmp# info
----------------------------------------------
interface "lax-vls"
exit
interface "p1-ix"
exit
----------------------------------------------
*A:Dut-B>config>router>igmp# info detail
----------------------------------------------
interface "C_Rx"
no import
version 3
subnet-check
no max-groups
no max-sources
no max-grp-sources
no disable-router-alert-check
no query-interval
no query-last-listener-interval
no query-response-interval
no shutdown
exit
no grp-if-query-src-ip
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#
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
Enabled IGMP detailed output
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
IGMP interface configuration command usage
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
Command usage
Use the following syntax 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
Command usage
Use the following syntax 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 CLI syntax to configure IGMP parameters.
config>router# igmp
ssm-translate
grp-range start end
source ip-address
Command usage to configure IGMP parameters
config>router# igmp
config>router>igmp# ssm-translate
config>router>igmp>ssm# grp-range 239.255.0.1 231.2.2.2
config>router>igmp>ssm>grp-range# source 10.1.1.1
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 might 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
The following examples show the command usage to configure PIM interface parameters and the resulting configuration outputs.
Command usage 1
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
Configuration output 1
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#
Command usage 2
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#
Configuration output 2
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#
Command usage 3
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#
Configuration output 3
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#
Command usage 4
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#
Configuration output 4
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#
Command usage 5
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#
Configuration output 5
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.
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]
Applying the policy statement
The following example 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#
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 231.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#
Multicast command reference
Command hierarchies
Configuration commands
config
- router
- mc-maximum-routes number [log-only] [threshold threshold]
- no mc-maximum-routes
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 [value]
- no max-sources
- query-interval seconds
- no query-interval
- query-last-listener-interval seconds
- no query-last-listener-interval
- query-response-interval seconds
- no query-response-interval
- [no] shutdown
- 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]
- [no] bsm-check-rtr-alert
- 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
- no spt-switchover-threshold {grp-ipv4-prefix/ipv4-prefix-length | grp-ipv4-prefix netmask}
- 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}
Operational commands
Show commands
show
- router
- igmp
- group [grp-ip-address] [host | interface | saps]
- group summary [host | interface | saps]
- 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
- statistics [ip-int-name | int-ip-address | mpls-if-name] [family]
- status [detail] [family]
Clear commands
clear
- router
- igmp
- database [group grp-ip-address [source src-ip-address]]
- database interface {ip-int-name | ip-address} [group grp-ip-address [source src-ip-address]]
- database host ip-address [group grp-ip-address [source src-ip-address]]
- database host all [group grp-ip-address [source src-ip-address]]
- database group-interface all
- statistics group-interface [fwd-service service-id] ip-int-name
- statistics group-interface all
- statistics host ip-address
- statistics host all
- statistics [interface ip-int-name | ip-address]
- version group-interface [fwd-service service-id] ip-int-name
- version group-interface all
- version host ip-address
- version host all
- 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]
- statistics [{[interface ip-int-name | int-ip-address]} {[group grp-ip-address [source ip-address]]}] [family]]
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] group-interface [fwd-service service-id] [ip-int-name]
- [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
- 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
- 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
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.
Unlike other commands and parameters where the default state is not indicated in the configuration file, shutdown and no shutdown are always indicated in system-generated configuration files.
The no form of 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 |
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.
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.
- end
Specifies the multicast group range end address.
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 will be 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 shutdown.
Default
no mc-maximum-routes
Parameters
- number
Specifies the maximum number of routes to be held in a VRF context.
- 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
Specifies the percentage at which a warning log message and SNMP trap are sent.
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, IGMP 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 it 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
Commands in this context configure an IGMP interface. The interface is a local identifier of the network interface on which reception of the specified multicast address is to be enabled or disabled.
The no form of 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 the 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 will be 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 it 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>policyoptions 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 specifies 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 will not be allowed. When the value is 0, there is no limit to the number of groups. This command is applicable for IPv4 only.
Default
max-groups 0
Parameters
- value
Specifies the maximum number of groups for this interface.
max-sources
Syntax
max-sources [value]
no max-sources
Context
config>router>igmp>if
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 that can be configured.
query-last-listener-interval
Syntax
query-last-listener-interval seconds
no query-last-listener-interval
Context
config>router>igmp>if
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
no query-last-listener-interval
Parameters
- seconds
Specifies the frequency, in seconds, at which the router transmits group-specific host-query messages.
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 an IPv4 unicast address that sends data on an interface. This enables a multicast receiver host to signal to a router the group from which to receive multicast traffic, and the sources from which the traffic is expected.
The source command is mutually exclusive with the specification of individual sources for the same group.
The source command in combination with the group is used to create a specific (S,G) static group entry.
The no form of 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 only be enabled if no existing source addresses for this group are specified.
The no form of this command is used to remove 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.
The no form of this command disables subnet checking.
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. If routers run different versions of IGMP, they will negotiate the lowest common version of IGMP that is supported by hosts on their subnet and operate in that version. For IGMP to function correctly, all routers on a LAN 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.
query-interval
Syntax
query-interval seconds
no query-interval
Context
config>router>igmp
config>router>igmp>if
Platforms
Supported on all 7210 SAS platforms as described in this document
Description
This command specifies the frequency at which 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.
query-last-member-interval
Syntax
query-last-member-interval seconds
Context
config>router>igmp
config>router>igmp>if
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.
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 length of time to wait to receive a response to the host-query message from the host.
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.
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, which are translated to source-specific multicast (SSM) (S,G) entries. If the static entry needs to be created, it has to be translated from an IGMPv1 or IGMPv2 request to an 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 is used to configure group ranges, which are translated to SSM (S,G) entries.
Parameters
- start
Specifies an IP address that indicates the start of the group range.
- end
Specifies an IP address that indicates 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 specifies the source IP address for the group range. Whenever a (*,G) report is received in the range specified by grp-range start and end parameters, it is translated to an (S,G) report with the value of this object as the source address.
Parameters
- ip-address
Specifies the IP address that will be sending data.
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).
Default
no pim
enable-mdt-spt
Syntax
[no] enable-mdt-spt
Context
config>router>pim
Platforms
Supported on all 7210 SAS platforms as described in this document
Description
This command is used to enable SPT switchover for default MDT.
The no form of this command disables SPT switchover for default MDT. If 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]]
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 prevents 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.
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 creates a logical IP routing interface.
Interface names are case-sensitive and must be unique within the group of IP interfaces defined for config>router>interface and config>service>ies>interface. 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, up to 32 characters. Interface names must be unique within the group of defined IP interfaces for the config router interface and config service ies interface commands. An interface name cannot be in the form of an IP address. 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 periodic refreshes of PIM Assert messages on an interface.
The no form of this command removes the configuration.
Default
no assert-period
Parameters
- assert-period
Specifies the period for periodic refreshes of PIM Assert messages on an interface.
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.
The no form of this command removes BFD from the associated IGP protocol adjacency.
For information about the protocols and platforms that support BFD, see the 7210 SAS-D, Dxp, K 2F1C2T, K 2F6C4T, K 3SFP+ 8C Router Configuration Guide.
Default
no bfd-enable
bsm-check-rtr-alert
Syntax
[no] bsm-check-rtr-alert
Context
config>router>pim>interface
Platforms
Supported on all 7210 SAS platforms as described in this document
Description
This command enables the checking of the router alert option in the bootstrap messages received on this interface.
The no form of this command enables accepting of BSM packets without the router alert option.
Default
no bsm-check-rtr-alert
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 this command is enabled, each multicast stream that needs to be forwarded over an ECMP link is reevaluated for the total multicast bandwidth utilization. Reevaluation occurs on the ECMP interface in question.
The no form of this command disables 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.
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 IPv4 only.
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 will never timeout the adjacency).
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.
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 advantages are that it eliminates duplicate traffic forwarding to the LAN. It also improves performance because it removes the required interaction between the control and data planes.
The improved-assert command is still fully interoperable with the 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), implementations. However, there may be conformance tests that may 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
enabled
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 a 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: 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
auto
Parameters
- auto
Specifies that, on broadcast interfaces, the forwarding plane performs subnet-match checks on multicast packets received on the interface to determine whether the packet is from a directly-attached source. On unnumbered/point-to-point interfaces, all traffic is implicitly treated as coming from a remote source.
- always
Specifies that all traffic received on the interface be treated as coming from a directly-attached multicast source.
- never
Specifies 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/point-to-point interfaces, 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 sets 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 restores the default values.
Default
priority 1
Parameters
- priority
Specifies the priority to become the designated router. The higher the value, the higher the priority.
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 the sticky-dr operation on this interface. When the operation is 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 an interface, it will continue to act as the DR for the LAN even after the old DR comes back up.
The no form of this command disables the sticky-dr operation on this interface.
Default
no sticky-dr
Parameters
- 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.
three-way-hello
Syntax
three-way-hello [compatibility-mode]
no three-way-hello
Context
config>router>pim>interface
Platforms
Supported on all 7210 SAS platforms as described in this document
Description
This command configures the compatibility mode to enable three-way hello. By default, the value is disabled on all interfaces, which specifies that the standard two-way hello is supported. When enabled, the three-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 that the router is capable of enabling 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 disabled, 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 RP being configured. Anycast enables fast convergence when a PIM RP router fails by allowing receivers and sources to rendezvous at the closest RP.
The no form of 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.
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 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.
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.
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 control the flow of bootstrap messages from the RP and apply them to the PIM configuration. 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...(5 maximum)]
no bootstrap-import
Context
config>router>pim>rp
Platforms
Supported on all 7210 SAS platforms as described in this document
Description
This command applies import policies to control the flow of bootstrap messages to the RP, and apply them to the PIM configuration. 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.
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 will be used by the IP interface within the subnet. This address must be unique within the subnet and specified in dotted-decimal notation.
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 is used to configure 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 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.
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 0 value means the router is not eligible to be the bootstrap router. A value of 1 means the router is the least likely to become the designated router.
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 the candidate RP parameters.
Routers use a set of available rendezvous points distributed in bootstrap messages to get the proper group-to-RP mapping. A set of routers within a domain are also configured as candidate RPs (C-RPs); typically, these will be the same routers that are configured as candidate BSRs.
Every multicast group has a shared tree through which receivers learn about new multicast sources and new receivers learn about all multicast sources. The rendezvous point (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.
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.
- 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.
- netmask
Specifies the subnet mask in dotted-decimal notation.
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.
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 a rendezvous point (RP). This value is used to elect an RP for a group range.
Default
priority 192
Parameters
- priority
Specifies the priority to become a rendezvous point (RP). A value of 0 is considered as the highest priority.
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 rendezvous point (RP) addresses for a multicast group range.
Entries can be created or destroyed. If no IP addresses are configured in the config>router>pim>rp>static>address context, 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 indicates the RP address that should be used by the router for the range of multicast groups configured by the group-range command.
Parameters
- ip-address
Specifies the static IP address of the RP. This address must be unique within the subnet and specified in dotted-decimal notation.
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 SSM multicast group address ranges for this router.
Parameters
- ip-prefix/mask
Specifies the IP prefix in dotted-decimal notation and the associated mask.
- netmask
Specifies the subnet mask in dotted-decimal notation.
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 that should be used by the router as the RP. The config router pim rp static address 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 configuration.
Parameters
- grp-ip-address
Specifies the multicast group IP address expressed in dotted-decimal notation.
- 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.
- netmask
Specifies the subnet mask in dotted-decimal notation.
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 this command is 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 interfaces) 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, the non-dr-attract-trafffic flag can be used in the PIM context to have the router ignore the DR state and attract traffic when not DR. While using this flag, the router may not send the stream down to the DSLAM while not DR.
When this command is enabled, the designated router state is ignored.
The no form of this command causes the router to honor the designated router value.
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 the RPF interface toward the source/rendezvous point. However, the operator can specify the use of the unicast route table (rtable-u).
Default
rpf-table rtable-u
Parameters
- rtable-u
Specifies only that the unicast route table will be used by the multicast protocol (PIM) for IPv4 RPF checks. This route table will contain routes submitted by all the unicast routing protocols.
spt-switchover-threshold
Syntax
spt-switchover-threshold {grp-ipv4-prefix/ipv4-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 should switch over from the shared tree to the source-specific tree. The switchover is attempted only if the traffic rate on the shared tree for the group exceeds the configured threshold.
On the 7210 SAS, this command is used to enable or disable switch over to the SPT tree. To disable switch over to SPT, a threshold value of infinity must be configured (that is, to continue using the shared tree forever, configure the IP multicast prefix with this command and set the threshold to infinity). To use the SPT tree, do not configure the IP multicast address prefix using this command and the default behavior will apply 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-ipv4-prefix
Specifies the multicast group IP address expressed in dotted-decimal notation.
- ipv4-prefix-length
Specifies the length of the IPv4 prefix.
- netmask
Specifies the netmask associated with the IPv4 prefix expressed in dotted-decimal notation.
- spt-threshold
Specifies the configured threshold in kilobits per second (kbps) for a group prefix. A switchover is attempted only if the traffic rate on the shared tree for the group exceeds this configured threshold.
- infinity
Keyword to specify that no switchover will occur at any time, regardless of the traffic level is detected. The threshold value, in kilobits per second (KBPS), is 4294967295.
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 this command is enabled, packets are treated as if SPT bit was set regardless of whether it is set or not.
Default
ssm-assert-compatible-mode disable
Parameters
- enable
Enables SSM assert in compatibility mode for this PIM protocol instance.
- disable
Disables SSM assert in compatibility mode for this PIM protocol instance.
ssm-default-range-disable
Syntax
[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 allows the user to disable 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
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 SSM group ranges.
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 relevant multicast information from the target multicast router. Information displayed includes adjacency information, protocol, metrics, thresholds, and flags from the target multicast router. This information can be used by network operators to determine whether bidirectional adjacencies exist.
Parameters
- ip-address
Specifies the IP address of the multicast capable target router.
- dns-name
Specifies the DNS name, up to 63 characters.
- router-instance
Specifies the router instance.
- service-name
Specifies the service name, up to 64 characters
Output
The following output is an example of multicast information, and Output fields: mrinfo describes the output fields.
Sample outputA:dut-f# mrinfo 10.1.1.2
10.1.1.2 [version 3.0,prune,genid,mtrace]:
10.1.1.2 -> 10.1.1.1 [1/0/pim]
16.1.1.1 -> 0.0.0.0 [1/0/pim/down/disabled]
17.1.1.1 -> 0.0.0.0 [1/0/pim/querier/leaf]
200.200.200.3 -> 200.200.200.5 [1/0/tunnel/pim]...
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]
? 12.1.1.1 -> ? 12.1.1.2 [1/0/pim]
? 19.1.1.1 -> ? 19.1.1.9 [1/0/pim]
? 11.1.1.1 -> ? 0.0.0.0 [1/0/pim/leaf]
? 17.1.1.1 -> ? 17.1.1.7 [1/0/pim]
? 17.1.2.1 -> ? 17.1.2.7 [1/0/pim]
Label |
Description |
|---|---|
General flags |
|
version |
Displays the software version on queried router |
prune |
Indicates that router understands pruning |
genid |
Indicates that router sends generation IDs |
mtrace |
Indicates that the router handles mtrace requests |
Neighbors flags |
|
1 |
Metric |
0 |
Threshold (multicast time-to-live) |
pim |
PIM enabled on interface |
down |
Operational status of interface |
disabled |
Administrative status of interface |
leaf |
No downstream neighbors on interface |
querier |
Interface is IGMP querier |
tunnel |
Neighbor reached via tunnel |
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, up to 63 characters.
- 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.
- hop
Specifies the maximum number of hops that will be traced from the receiver back toward the source.
- router-instance
Specifies the router name or service ID used to identify the router instance.
- service-name
Specifies the service name, up to 64 characters.
- wait-time
Specifies the number of seconds to wait for the response.
Output
The following output is an example of mtrace information, and Output fields: mtrace describes the output fields.
Sample outputA: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.
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 will be 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] [host | interface | saps]
group summary [host | interface | saps]
Context
show>router>igmp
Platforms
Supported on all 7210 SAS platforms as described in this document
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.
- host
Displays hosts for the multicast group addresses.
- interface
Displays interfaces for the multicast group addresses.
- saps
Displays SAPs for the multicast group addresses.
Output
The following output is an example of IGMP 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
===============================================================================
(*,225.0.0.1)
Fwd List : 112.112.1.2 Up Time : 0d 00:00:21
(11.11.0.1,225.0.0.1)
Fwd List : 112.112.1.1 Up Time : 0d 00:00:30
Blk List : 112.112.1.2 Up Time : 0d 00:00:21
(11.11.0.2,225.0.0.1)
Fwd List : 112.112.1.1 Up Time : 0d 00:00:30
(*,225.0.0.2)
Fwd List : 112.112.1.2 Up Time : 0d 00:00:21
(11.11.0.1,225.0.0.2)
Blk List : 112.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
===============================================================================
(*,225.0.0.1) 1 0
(11.11.0.1,225.0.0.1) 1 1
(11.11.0.2,225.0.0.1) 1 0
(*,225.0.0.2) 1 0
(11.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
===============================================================================
(*,224.24.24.24) Up Time : 0d 05:23:23
Fwd List : nyc-vlc
-------------------------------------------------------------------------------
(*,G)/(S,G) Entries : 1
===============================================================================
A:NYC#
Label |
Description |
|---|---|
IGMP Groups |
Displays the IP multicast sources corresponding to the IP multicast groups which are statically configured |
Fwd List |
Displays the list of interfaces in the forward list |
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 the specified IP interface name up to 32 characters.
- ip-address
Displays the information associated with the specified IP address.
- grp-address
Displays 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 output fields.
Sample outputA:Dut-C# show router igmp interface
===============================================================================
IGMP Interfaces
===============================================================================
Interface Adm Oper Querier Cfg/Opr Num Policy
Version Groups
-------------------------------------------------------------------------------
C_Rx_net1 Up Up 10.2.1.3 3/3 900 none
C_Rx_acc1 Up Up 10.1.1.3 3/3 900 none
C_Rx_acc2 Up Up 10.1.2.3 3/3 900 none
C_Rx_net2 Up Up 10.2.2.3 3/3 900 none
-------------------------------------------------------------------------------
Interfaces : 4
===============================================================================
*A:Dut-C# show router igmp interface detail
===============================================================================
IGMP Interface C_Rx_net1
===============================================================================
Interface : C_Rx_net1
Admin Status : Up Oper Status : Up
Querier : 10.2.1.3 Querier Up Time : 0d 00:00:55
Querier Expiry Time: N/A Time for next query: 0d 00:01:51
Admin/Oper version : 3/3 Num Groups : 900
Policy : none Subnet Check : Enabled
Max Groups Allowed : No Limit Max Groups Till Now: 900
Use LAG port weight: no
Router Alert Check : Enabled Max Sources Allowed: No Limit
Max GrpSrcs Allowed: No Limit
Redundant Multicast: no Red. Multicast Fwd : N/A
-------------------------------------------------------------------------------
IGMP Group
-------------------------------------------------------------------------------
Group Address : 239.225.1.1 Up Time : 0d 00:00:51
Interface : C_Rx_net1 Expires : N/A
Last Reporter : 10.2.1.1 Mode : include
V1 Host Timer : Not running Type : dynamic
V2 Host Timer : Not running Compat Mode : IGMP Version 3
-----------------------------------------------
Source Address Expires Type Fwd/Blk
-----------------------------------------------
10.1.1.2 0d 00:04:07 dynamic Fwd
-------------------------------------------------------------------------------
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 will be zero. |
Cfg/Opr Version Admin/Oper version |
Cfg — The configured version of IGMP running on this interface. For IGMP to function correctly, all routers on a LAN must be configured to run the same version of IGMP on that LAN. Opr — The operational version of IGMP running on this interface. If the cfg value is 3 but all of the routers in the local subnet of this interface use IGMP version v1 or v2, the operational version will be v1 or v2. |
Num Groups |
Displays the number of multicast groups which 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 got 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 report(s) 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 |
The time remaining until the local router will assume that there are no longer any IGMP version 1 members on the IP subnet attached to this interface. Upon hearing any IGMPv1 Membership Report, this value is reset to the group membership timer. While this time remaining is non-zero, the local router ignores any IGMPv2 Leave messages for this group that it receives on this interface. |
V2 Host Timer |
The time remaining until the local router will assume that there are no longer any IGMP version 2 members on the IP subnet attached to this interface. Upon hearing any IGMPv2 Membership Report, this value is reset to the group membership timer. While this time remaining is non-zero, the local router ignores any IGMPv3 Leave messages for this group that it receives on this interface. |
Type |
Indicates how this group entry was learned. If this group entry was learned by IGMP, it will be set to ‟dynamic”. For statically configured groups, the value will be set to 'static'. |
Compat Mode |
Used in order for routers to be compatible with earlier version routers. IGMPv3 hosts MUST operate in version 1 and version 2 compatibility modes. IGMPv3 hosts MUST keep state per local interface regarding the compatibility mode of each attached network. A host's compatibility mode is determined from the Host Compatibility Mode variable which can be in one of three states: IGMPv1, IGMPv2 or IGMPv3. This variable is kept per interface and is dependent on the version of General Queries heard on that interface as well as the Earlier Version Querier Present timers for the interface. |
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.
Parameters
- interface-name
Displays information associated with the specified interface name up to 32 characters.
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
-----------------------------------------------------------------
<234.1.1.1 - 234.1.1.2> 10.1.1.1
<232.1.1.1 - 232.1.1.5> 10.1.1.2 ies-abc
-----------------------------------------------------------------
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 |
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 the specified IP interface name up to 32 characters.
- ip-addr
Displays the information associated with the specified IP address.
Output
The following output is an example of static IGMP information, and Output fields: IGMP static describes the output fields.
Sample output*A:Dut-C# show router igmp static
===================================================================
IGMP Static Group Source
===================================================================
Source Group Interface
-------------------------------------------------------------------
* 239.1.2.1 C_Rx_acc1
10.2.1.1 239.12.1.1 C_Rx_acc1
* 239.1.1.1 C_Rx_net2
-------------------------------------------------------------------
Static (*,G)/(S,G) Entries : 3
===================================================================
Label |
Description |
|---|---|
Source |
Displays entries which represent a source address from which receivers are interested/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]
statistics group-interface [fwd-service service-id] [ip-int-name]
statistics host [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 the specified IP interface name up to 32 characters.
- ip-address
Displays the information associated with the specified IP address.
- service-id
Displays the information associated with the specified service ID.
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#
Label |
Description |
|---|---|
IGMP Interface Statistics |
Displays the IGMP statistics for a particular interface |
Message Type |
Queries — The number of IGMP general queries transmitted or received on this interface Report — The total number of IGMP V1, V2, or V3 reports transmitted or received on this interface Leaves — The total number of IGMP leaves transmitted on this interface |
Received |
Displays the total number of IGMP packets received on this interface |
Transmitted |
Column that 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 which did 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#
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 will retry a query |
Show router PIM commands
anycast
Syntax
anycast [detail] [family]
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
- detail
Displays detailed information.
- family
Displays IPv4 information.
Output
The following output displays an example of a PIM anycast information, and Output fields: PIM anycast describes the output fields.
Sample outputA: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
===================================================
Label |
Description |
|---|---|
Anycast Address |
Displays the candidate anycast address |
Anycast RP Peer |
Displays the candidate anycast RP peer address |
crp
Syntax
crp [family|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.
- family
Displays IPv4 information.
Output
The following output is an example of a PIM CRP configuration, and Output fields: PIM CRP describes the output fields.
Sample outputA:7210SAS# show router pim crp
============================================================================
PIM Candidate RPs
============================================================================
RP Address Group Address Priority Holdtime Expiry Time
----------------------------------------------------------------------------
239.22.187.236 239.0.0.0/4 192 150 0d 00:02:19
239.22.187.239 239.0.0.0/4 192 150 0d 00:02:19
239.22.187.240 239.0.0.0/4 192 150 0d 00:02:09
----------------------------------------------------------------------------
Candidate RPs : 3
============================================================================
A:7210SAS#
Label |
Description |
|---|---|
RP Address |
Displays the Candidate RP address |
Group Address |
Displays the range of multicast group addresses for which the CRP is the Candidate RP |
Priority |
Displays the candidate RP priority for becoming a rendezvous point (RP). This value is used to elect RP for a group range. A value of 0 is considered as the highest priority. |
Holdtime |
Displays the hold time of the candidate RP. 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 will be 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 be displayed.
- type starg
Specifies that only (*,G) entries be displayed.
- type sg
Specifies that only (S,G) entries be displayed.
- detail
Displays detailed group information.
- family
Displays IPv4 information.
Output
The following output is an example of PIM group information, and Output fields: PIM group describes the output fields.
Sample output*A:Dut-C# show router pim group
===============================================================================
Legend: A = Active S = Standby
===============================================================================
PIM Groups ipv4
===============================================================================
Group Address Type Spt Bit Inc Intf No.Oifs
Source Address RP State Inc Intf(S)
-------------------------------------------------------------------------------
239.225.1.1 (S,G) spt C_A 4
10.1.1.2 10.4.4.4
239.225.1.2 (S,G) spt C_A 4
10.1.1.2 10.4.4.4
239.225.1.3 (S,G) spt C_A 4
10.1.1.2 10.4.4.4
239.225.1.4 (S,G) spt C_A 4
10.1.1.2 10.4.4.4
239.225.1.5 (S,G) spt C_A 4
10.1.1.2 10.4.4.4
239.225.1.6 (S,G) spt C_A 4
10.1.1.2 10.4.4.4
239.225.1.7 (S,G) spt C_A 4
10.1.1.2 10.4.4.4
-------------------------------------------------------------------------------
Groups : 7
===============================================================================
*A:Dut-C# show router pim group detail
===============================================================================
PIM Source Group ipv4
===============================================================================
Group Address : 239.225.1.1
Source Address : 10.1.1.2
RP Address : 10.4.4.4
Advt Router : 10.1.1.1
Flags : spt Type : (S,G)
MRIB Next Hop : 13.1.1.1
MRIB Src Flags : remote
Keepalive Timer Exp: 0d 00:03:16
Up Time : 0d 00:21:44 Resolved By : rtable-u
Up JP State : Joined Up JP Expiry : 0d 00:00:43
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 : 13.1.1.1
Incoming Intf : C_A
Outgoing Intf List : C_Rx_net1, C_Rx_acc1, C_Rx_acc2, C_Rx_net2
Spt threshold : 0 kbps ECMP opt threshold : 7
===============================================================================
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. It will be 0 if the type is configured as starg. It will be the address of the Rendezvous Point (RP) if the type is configured as starRP. |
RP Address |
Displays the RP address |
Type |
Displays the type of entry: (*,*, rp)/(*,G) or (S,G) |
Spt Bit |
Specifies whether to forward on (*,*, rp)/(*,G) or on (S,G) state. It is updated when the (S,G) data comes on the RPF interface 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 will contain 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 will be 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 '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 it does not see a join (S,G, rpt) message, then on expiry of the override timer, it sends it's 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 |
Specifies 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 happen based on the register stop timer and the response received from the RP. |
Register Stop Exp |
Displays the time remaining before the register state might transition to a different state |
Register from Anycast RP |
Displays if 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 with the specified IP interface name.
- ip-address
Displays the interface information associated with 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 will be zero.
If the type is starstarrp, the value of this object will be address of the RP.
- type
Specifies the type of this entry.
- detail
Displays detailed interface information.
- family
Displays IPv4 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#
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, 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 address parameter is not defined in this example, then the show command output would display two adjacencies.
Parameters
- neighbor ip-int-name
Displays the interface information associated with the specified IP interface name.
- neighbor ip-address
Displays the interface information associated 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 IPv4 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 outputALA-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#
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 neighbor address |
Expiry Time |
Displays the minimum time remaining before this PIM neighbor will be aged out 0 — Means that this neighbor will never be aged out. This happens when the PIM neighbor sends a Hello message with holdtime 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 was 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, any old hello information about that neighbor is discarded and superseded 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 rendezvous point (RP) set information built by the router.
Parameters
- family
Displays IPv4 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 outputA: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#
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 |
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 RP hash information, and Output fields: PIM RP hash describes the output fields.
Sample outputA: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 239.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#
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 |
statistics
Syntax
statistics [ip-int-name | int-ip-address | mpls-ip-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
Displays the interface information associated with the specified IP interface name.
- int-ip-address
Displays the interface information associated with the specified IP address.
- mpls-ip-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 IPv4 information.
Output
The following output is an example of PIM statistics information, and Output fields: PIM statistics describes the output fields.
Sample outputA: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#
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 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 which 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 which 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 groups contained in the message |
Register Policy Drops |
Displays the number of times the register policy match resulted in dropping PIM Register messages |
Bootstrap Import Policy Drops |
Displays the number of Bootstrap messages received on this interface that were dropped because of the bootstrap import policy |
Bootstrap Export Policy Drops |
Displays the number of Bootstrap messages that were not transmitted on this interface because of the bootstrap export policy |
Source Group Statistics |
Displays 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 the PIM status. The oper status reflects the combined operational status of the IPv4 PIM protocol status. If both are down, the oper status will be reflected as down. If IPv4 reflects up, the oper status will reflect 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 IPv4 information.
Output
The following output is an example of PIM status information, and Output fields: PIM status describes the output fields.
Sample outputA: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 toward 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#
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 toward |
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 CRP mechanism |
Address |
Displays the local RP address |
Priority |
Displays the CRP's priority for becoming a rendezvous point (RP). A 0 value 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 if hash-based multicast balancing of traffic over ECMP links is enabled or disabled |
Clear commands
database
Syntax
database [group grp-ip-address [source src-ip-address]]
database interface {ip-int-name|ip-address} [group grp-ip-address [source src-ip-address]]
database host ip-address [group grp-ip-address [source src-ip-address]]
database host all [group grp-ip-address [source src-ip-address]]
database group-interface all
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 grp-ip-address
Clears the multicast group address or zero in the specified address group.
- source src-ip-address
Clears the IGMP or PIM database from the specified source IP address.
- group-interface all
Clears the IGMP database on all group interfaces.
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 group-interface [fwd-service service-id] ip-int-name
statistics group-interface all
statistics host ip-address
statistics host all
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 a group or source cannot be specified at the same time.
Parameters
- group-interface interface-name
Clears the IGMP statistics on the specifies group interface.
- group-interface all
Clears the IGMP statistics on all group interfaces.
- fwd-service service-id
Clears the IGMP statistics on the specified service ID.
- host ip-address
Clears the IGMP statistics on the specified host.
- host all
Clears the IGMP statistics on all hosts.
- 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, then the (S,G) statistics are reset to zero.
- source ip-address
When the source address is specified along with the group address, then the (S,G) statistics are reset to zero.
- family
Clears IPv4 information.
version
Syntax
version group-interface [fwd-service service-id] ip-int-name
version group-interface all
version host ip-address
version host all
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
- group-interface interface-name
Clears the IGMP version on the specifies group interface.
- group-interface all
Clears the IGMP version on all group interfaces.
- fwd-service service-id
Clears the IGMP version on the specified service ID.
- host ip-address
Clears the IGMP version on the specified host.
- host all
Clears the IGMP version on all hosts.
- interface ip-int-name
Clears IGMP version on the specified interface.
- interface ip-address
Clears IGMP version 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.
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 about 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
The encapsulation value on the specified port ID.
- 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.
- vc-id
The virtual circuit ID on the SDP ID for which to clear information.
- 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 about 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
The encapsulation value on the specified port ID.
- sdp sdp-id
Displays the IGMP snooping statistics for a specific spoke or mesh SDP.
- vc-id
The virtual circuit ID on the SDP ID for which to display information.
Debug commands
Debug IGMP commands
group-interface
Syntax
[no] group-interface [fwd-service service-id] [ip-int-name]
Context
debug>router>igmp
Platforms
Supported on all 7210 SAS platforms as described in this document
Description
This command enables debugging for IGMP group interfaces.
Parameters
- service-id
Displays information associated with the specified service ID.
- ip-int-name
Displays information associated with the specified IP interface name, up to 32 characters.
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 specifies interface name or IP address.
Parameters
- ip-int-name
Displays the information associated with the specified IP interface name.
- ip-address
Displays the information associated with the specified IP address.
misc
Syntax
[no] misc
Context
debug>router>igmp
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 the debugging.
Output
The following output is an example of IGMP miscellaneous information.
Sample outputA: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/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 the specified IP interface name.
- ip-address
Displays the information associated with 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 or 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 or disables debugging for all the PIM modules.
Parameters
- group grp-ip-address
Debugs information associated with all PIM modules.
- source ip-address
Debugs information associated with all PIM modules.
- detail
Debugs detailed information about 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 or disables debugging for PIM assert mechanism.
Parameters
- group grp-ip-address
Debugs information associated with the PIM assert mechanism.
- source ip-address
Debugs information associated with the PIM assert mechanism.
- detail
Debugs detailed information about 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 or disables debugging for PIM/BGP specific interoperation.
Parameters
- ip-address
Debugs BGP information associated with the specified source.
- group-ip-address
Debugs BGP information associated with the specified group.
- peer-ip-address
Debugs BGP information associated with the specified peer.
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 the PIM bootstrap mechanism.
The no form of this command disables debugging.
Parameters
- detail
Debugs detailed information about the PIM assert 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 or disables debugging for PIM data exception.
Parameters
- group grp-ip-address
Debugs information associated with the specified data exception.
- source ip-address
Debugs information associated with the specified data exception.
- 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 or disables debugging for the PIM database.
Parameters
- group grp-ip-address
Debugs information associated with the specified database.
- source ip-address
Debugs information associated with the specified database.
- detail
Debugs detailed IP database 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 or disables debugging for the PIM interface.
Parameters
- ip-int-name
Debugs the information associated with the specified IP interface name.
- 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 or disables debugging for the PIM join-prune mechanism.
Parameters
- group grp-ip-address
Debugs information associated with the specified join-prune mechanism.
- source ip-address
Debugs information associated with the specified join-prune mechanism.
- 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 or disables debugging for PIM MRIB.
Parameters
- group grp-ip-address
Debugs information associated with the specified PIM MRIB.
- source ip-address
Debugs information associated with the specified PIM MRIB.
- 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 or disables debugging for PIM messaging.
Parameters
- detail
Debugs detailed messaging information.
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 or 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.
- 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 or 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 or disables debugging for the PIM register mechanism.
Parameters
- group grp-ip-address
Debugs information associated with the specified PIM register.
- source ip-address
Debugs information associated with the specified PIM register.
- 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 or disables debugging for PIM RTM.
Parameters
- detail
Debugs detailed RTM information.