Contents
- show ip pim boundary through udp-port
- show ip pim boundary
- show ip pim bsr-router
- show ip pim interface
- show ip pim mdt bgp
- show ip pim mdt history
- show ip pim mdt receive
- show ip pim mdt send
- show ip pim neighbor
- show ip pim rp
- show ip pim rp mapping
- show ip pim rp-hash
- show ip pim rp-hash (BSR)
- show ip pim snooping
- show ip pim tunnel
- show ip pim vc
- show ip rpf
- show ip rpf events
- show ip rpf select
- show ip sap
- show ip sdr
- show mls ip multicast
- show mls ip multicast bidir
- show mls ip multicast rp-mapping
- show mls ip multicast sso
- show mpls mldp bindings
- show mpls mldp count
- show mpls mldp database
- show mpls mldp filter
- show mpls mldp ha count
- show mpls mldp ha database
- show mpls mldp ha neighbors
- show mpls mldp ha root
- show mpls mldp interface
- show mpls mldp label release
- show mpls mldp neighbors
- show mpls mldp root
- show platform software multicast ip bidir
- show platform software multicast ip capability
- show platform software multicast ip complete
- show platform software multicast ip connected
- show platform software multicast ip interface
- show platform software multicast ip partial
- show platform software multicast ip source
- show platform software multicast ip statistics
- show platform software multicast ip summary
- show platform software multicast ip vrf
- show router-guard
- snmp-server enable traps mvpn
- snmp-server enable traps pim
- tunnel udlr address-resolution
- tunnel udlr receive-only
- tunnel udlr send-only
- udp-port
show ip pim boundary through udp-port
show ip pim boundary
To display information about mroutes filtered by administratively scoped IPv4 multicast boundaries configured on an interface, use the show ip pim boundary command in user EXEC or privileged EXEC mode.
Syntax Description
|
interface-type |
Interface type. For more information, use the question mark (?) online help function. |
|
interface-number |
Interface or subinterface number. For more information about the numbering syntax for your networking device, use the question mark (?) online help function. |
|
source- address |
IP address or hostname of the source. |
|
group- address |
IP address or hostname of the group. |
|
in |
Displays whether an mroute is being filtered (blocked) by an incoming multicast boundary (a multicast boundary configured to filter source traffic coming into the interface). |
|
out |
Displays whether an mroute is being filtered (blocked) by an outgoing multicast boundary (a multicast boundary configured to prevent mroutes states from being created on an interface by filtering Protocol Independent Multicast (PIM) joins and Internet Group Management Protocol (IGMP) reports for groups or channels). |
Usage Guidelines
Use the the show ip pim boundary command to determine whether an mroute is being filtered by administratively scoped IPv4 multicast boundaries configured on an interface (using the ip multicast boundary command).
Examples
The following sample output from the show ip pim boundary command shows a blocked mroute entry. The field descriptions are self-explanatory.
Router# show ip pim boundary FastEthernet 0/0 10.1.1.1 239.159.1.1 in
(10.1.1.1,239.159.1.1) unblocked on FastEthernet0/0 for in option
The following sample output from the show ip pim boundary command shows an unblocked mroute entry. The field descriptions are self-explanatory.
Router# show ip pim boundary FastEthernet 1/1 10.1.1.2 239.159.1.2 out
(10.1.1.2,239.159.1.2) blocked on FastEthernet1/1 for out option
show ip pim bsr-router
To display information about a bootstrap router (BSR), use the show ip pim bsr-routercommand in user EXEC or privileged EXEC mode.
Command History
|
Release |
Modification |
|---|---|
|
11.3 T |
This command was introduced. |
|
12.0(23)S |
The vrf keyword and vrf-name argument were added. |
|
12.2(13)T |
The vrf keyword and vrf-name argument were added. |
|
12.2(14)S |
This command was integrated into Cisco IOS Release 12.2(14)S. |
|
12.2(18)SXE |
Support for this command was introduced on the Supervisor Engine 720. |
|
12.2(27)SBC |
This command was integrated into Cisco IOS Release 12.2(27)SBC. |
|
12.2(33)SRA |
This command was integrated into Cisco IOS Release 12.2(33)SRA. |
Usage Guidelines
The output includes elected BSR information and information about the locally configured candidate rendezvous point (RP) advertisement.
Examples
The following is sample output from the show ip pim bsr-router command:
Router# show ip pim bsr-router
PIMv2 Bootstrap information
This system is the Bootstrap Router (BSR)
BSR address: 172.16.143.28
Uptime: 04:37:59, BSR Priority: 4, Hash mask length: 30
Next bootstrap message in 00:00:03 seconds
Next Cand_RP_advertisement in 00:00:03 seconds.
RP: 172.16.143.28(Ethernet0), Group acl: 6
The table below describes the significant fields shown in the display.
| Table 1 | show ip pim bsr-router Field Descriptions |
|
Field |
Description |
|---|---|
|
BSR address |
IP address of the BSR. |
|
Uptime |
Length of time that this router has been up (in hours, minutes, and seconds). |
|
BSR Priority |
Priority as configured with the ip pim bsr-candidate command. |
|
Hash mask length |
Length of a mask (32 bits maximum) that is to be ANDed with the group address before the hash function is called. This value is configured with the ip pim bsr-candidate command. |
|
Next bootstrap message in |
Time (in hours, minutes, and seconds) in which the next bootstrap message is due from this BSR. |
|
Next Cand_RP_advertisement in |
Time (in hours, minutes, and seconds) in which the next candidate RP advertisement will be sent. |
|
RP |
List of RP IP addresses. |
|
Group acl |
Standard IP access list number that defines the group prefixes that are advertised in association with the RP address. This value is configured with the ip pim rp-candidate command. |
Related Commands
|
Command |
Description |
|---|---|
|
ip pim bsr-candidate |
Configures the router to announce its candidacy as a BSR. |
|
ip pim rp-candidate |
Configures the router to advertise itself as a PIM Version 2 candidate RP to the BSR. |
|
show ip pim rp |
Displays active RPs that are cached with associated multicast routing entries. |
|
show ip pim rp-hash |
Displays which RP is being selected for a specified group. |
show ip pim interface
To display information about interfaces configured for Protocol Independent Multicast (PIM), use the show ip pim interface command in user EXEC or privileged EXEC mode.
Syntax Description
|
vrf vrf-name |
(Optional) Displays information about PIM interfaces associated with the Multicast Virtual Private Network (MVPN) virtual routing and forwarding (MVRF) instance specified for the vrf-nameargument. |
|
type number |
(Optional) Interface type and number. |
|
df |
(Optional) When bidirectional PIM (bidir-PIM) is used, displays the IP address of the elected designated forwarder (DF) for each rendezvous point (RP) of an interface. |
|
count |
(Optional) Specifies the number of packets received and sent out the interface. |
|
rp-address |
(Optional) RP IP address. |
|
detail |
(Optional) Displays PIM details of each interface. |
|
stats |
(Optional) Displays multicast PIM interface octet counts. |
Command History
|
Release |
Modification |
|---|---|
|
10.0 |
This command was introduced. |
|
11.2(11)GS |
This command was integrated into Cisco IOS Release 11.2(11)GS. |
|
12.0(5)T |
This command was modified. The flag "H" was added in the output display to indicate that an outgoing interface is hardware-switched in the case of IP multicast Multilayer Switching (MMLS). |
|
12.0(18)ST |
This command was integrated into Cisco IOS Release 12.0(18)ST. |
|
12.1(2)T |
This command was modified. The df keyword and rp-address argument were added. |
|
12.1(5)T |
This command was modified. The detail keyword was added. |
|
12.0(22)S |
This command was modified. The command output changed to show when the query interval is set to milliseconds. |
|
12.0(23)S |
This command was modified. The vrf keyword and vrf-name argument were added. |
|
12.2(13)T |
This command was modified. The vrf keyword and vrf-name argument were added. |
|
12.2(14)S |
This command was integrated into Cisco IOS Release 12.2(14)S. |
|
12.2(31)S |
This command was modified. The stats keyword was added. |
|
12.2(33)SRA |
This command was integrated into Cisco IOS Release 12.2(33)SRA. |
|
12.3(17) |
This command was modified. The stats keyword was added. |
|
12.4(7) |
This command was modified. The stats keyword was added. |
|
12.4(6)T |
This command was modified. The stats keyword was added. |
|
12.2SX |
This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware. |
|
Cisco IOS XE Release 2.1 |
This command was modified. The "FS" column was removed from the output of the show ip pim interface count command due to the introduction of the IPv4 MFIB architecture. |
|
15.0(1)M |
This command was modified. The "FS" column was removed from the output of the show ip pim interface count command due to the introduction of the IPv4 MFIB architecture. |
|
12.2(33)SRE |
This command was modified. The "FS" column was removed from the output of the show ip pim interface count command due to the introduction of the IPv4 MFIB architecture. |
Usage Guidelines
Use the show ip pim interface count command to display switching counts for Multicast Distributed Switching (MDS) and other switching statistics.
Examples
The following is sample output from the show ip pim interface command:
Router# show ip pim interface
Address Interface Ver/ Nbr Query DR DR
Mode Count Intvl Prior
10.1.0.1 GigabitEthernet0/0 v2/SD 0 30 1 10.1.0.1
10.6.0.1 GigabitEthernet0/1 v2/SD 1 30 1 10.6.0.2
10.2.0.1 ATM1/0.1 v2/SD 1 30 1 0.0.0.0
The following is sample output from the show ip pim interface command when an interface is specified:
Router# show ip pim interface Ethernet1/0
Address Interface Ver/ Nbr Query DR DR
Mode Count Intvl Prior
172.16.1.4 Ethernet1/0 v2/S 1 100 ms 1 172.16.1.4
The following is sample output from the show ip pim interface command when the count keyword is specified:
Router# show ip pim interface count
Address Interface FS Mpackets In/Out
172.16.121.35 Ethernet0 * 548305239/13744856
172.16.121.35 Serial0.33 * 8256/67052912
192.168.12.73 Serial0.1719 * 219444/862191
The following is sample output from the show ip pim interface command when the countkeyword is specified and IP MMLS is enabled. The example lists the PIM interfaces that are fast switched and process switched, and the packet counts for these interfaces. The H flag is added to interfaces where IP MMLS is enabled.
Router# show ip pim interface count
States: FS - Fast Switched, H - Hardware Switched
Address Interface FS Mpackets In/Out
192.168.10.2 Vlan10 * H 40886/0
192.168.11.2 Vlan11 * H 0/40554
192.168.12.2 Vlan12 * H 0/40554
192.168.23.2 Vlan23 * 0/0
192.168.24.2 Vlan24 * 0/0
The following are two sample outputs from the show ip pim interface command when the df keyword is specified:
Router# show ip pim interface df Interface RP DF Winner Metric Uptime Ethernet3/3 10.10.0.2 10.4.0.2 0 00:03:49 10.10.0.3 10.4.0.3 0 00:01:49 10.10.0.5 10.4.0.4 409600 00:01:49 Ethernet3/4 10.10.0.2 10.5.0.2 0 00:03:49 10.10.0.3 10.5.0.2 409600 00:02:32 10.10.0.5 10.5.0.2 435200 00:02:16 Loopback0 10.10.0.2 10.10.0.2 0 00:03:49 10.10.0.3 10.10.0.2 409600 00:02:32 10.10.0.5 10.10.0.2 435200 00:02:16 Router# show ip pim interface Ethernet3/3 df 10.10.0.3 Designated Forwarder election for Ethernet3/3, 10.4.0.2, RP 10.10.0.3 State Non-DF Offer count is 0 Current DF ip address 10.4.0.3 DF winner up time 00:02:33 Last winner metric preference 0 Last winner metric 0
The table below describes the significant fields shown in the displays.
| Table 2 | show ip pim interface Field Descriptions |
The following is sample output from the show ip pim interface command with the detailkeyword for Fast Ethernet interface 0/1:
Router# show ip pim interface fastethernet 0/1 detail
FastEthernet0/1 is up, line protocol is up
Internet address is 172.16.8.1/24
Multicast switching:process
Multicast packets in/out:0/0
Multicast boundary:not set
Multicast TTL threshold:0
PIM:enabled
PIM version:2, mode:dense
PIM DR:172.16.8.1 (this system)
PIM neighbor count:0
PIM Hello/Query interval:30 seconds
PIM State-Refresh processing:enabled
PIM State-Refresh origination:enabled, interval:60 seconds
PIM NBMA mode:disabled
PIM ATM multipoint signalling:disabled
PIM domain border:disabled
Multicast Tagswitching:disabled
The table below describes the significant fields shown in the display.
| Table 3 | show ip pim interface detail Field Descriptions |
|
Field |
Description |
|---|---|
|
Internet address |
IP address of the specified interface. |
|
Multicast switching: |
The type of multicast switching enabled on the interface: process, fast, or distributed. |
|
Multicast boundary: |
Indicates whether an administratively scoped boundary is configured. |
|
Multicast TTL threshold: |
The time-to-live (TTL) threshold of multicast packets being forwarded out the interface. |
|
PIM: |
Indicates whether PIM is enabled or disabled. |
|
PIM version: |
Indicates whether PIM version 1 or version 2 is configured. |
|
mode: |
Indicates whether PIM sparse mode, dense mode, or sparse-dense mode is configured. |
|
PIM DR: |
The IP address of the DR. |
|
PIM State-Refresh processing: |
Indicates whether the processing of PIM state refresh control messages is enabled. |
|
PIM State-Refresh origination: |
Indicates whether the origination of the PIM state refresh control messages is enabled. |
|
interval: |
Indicates the configured interval for the origination of the PIM state refresh control messages. The available interval range is from 4 to 100 seconds. |
|
PIM NBMA mode: |
Indicates whether the interface is enabled for nonbroadcast multiaccess (NBMA) mode. |
|
PIM ATM multipoint signalling: |
Indicates whether the interface is enabled for ATM multipoint signaling. |
|
PIM domain border: |
Indicates whether the interface is enabled as a PIM domain border. |
|
Multicast Tagswitching: |
Indicates whether multicast tag switching is enabled. |
The following is sample output from the show ip pim interface command when the stats keyword is specified:
Router# show ip pim interface stats
Interface Mpackets In Mpackets Out Octets In Octets Out
Loopback0 0 0 0 0
Loopback1 0 0 0 0
Ethernet0/0 0 0 0 0
Ethernet0/3 0 0 0 0
Ethernet1/1 0 0 0 0
For all of the count descriptions, a packet is counted as a multicast packet if either of the following two conditions is met:
- The IP address contained in the IP header of the packet specifies a multicast (class D) IP address.
- The IP address contained in the IP header of the packet specifies an IP address located on this router and the packet contains an encapsulated packet for which the IP header of the encapsulated packet specifies a multicast (class D) IP address.
The table below describes the significant fields shown in the display.
| Table 4 | show ip pim interface stats Field Descriptions |
|
Field |
Description |
|---|---|
|
Mpackets In |
The number of multicast packets received on each interface listed in the output. |
|
Mpackets Out |
The number of multicast packets sent on each interface listed in the output. |
|
Octets In |
Cumulative byte count for data bytes (including IP header bytes) contained within multicast packets received on each interface listed in the output. |
|
Octets Out |
Cumulative byte count for data bytes (including IP header bytes) contained within multicast packets sent on each interface listed in the output. |
Related Commands
|
Command |
Description |
|---|---|
|
ip pim |
Enables PIM on an interface. |
|
ip pim query-interval |
Configures the frequency of PIM router query messages. |
|
ip pim state-refresh disable |
Disables the processing and forwarding of PIM dense mode state refresh control messages on a PIM router. |
|
ip pim state-refresh origination-interval |
Configures the origination of and the interval for PIM dense mode state refresh control messages on a PIM router. |
|
show ip mfib interface |
Displays MFIB-related information about interfaces and their forwarding status. |
|
show ip pim neighbor |
Displays information about PIM neighbors. |
show ip pim mdt bgp
To show details about the Border Gateway Protocol (BGP) advertisement of the route distinguisher (RD) for the multicast distribution tree (MDT) default group, use the show ip pim mdt bgp command in user EXEC or privileged EXEC mode.
Command History
|
Release |
Modification |
|---|---|
|
12.0(23)S |
This command was introduced. |
|
12.2(13)T |
This command was integrated into Cisco IOS Release 12.2(13)T. |
|
12.2(14)S |
This command was integrated into Cisco IOS Release 12.2(14)S. |
|
12.2(18)SXE |
Support for this command was introduced on the Supervisor Engine 720. |
|
12.2(27)SBC |
This command was integrated into Cisco IOS Release 12.2(27)SBC. |
|
12.2(33)SRA |
This command was integrated into Cisco IOS Release 12.2(33)SRA. |
Usage Guidelines
Use this command to show detailed BGP advertisement of the RD for the MDT default group.
show ip pim mdt history
To display information about the history of data multicast distribution tree (MDT) groups that have been reused, use the show ip pim mdt historycommand in privileged EXEC mode.
Syntax Description
|
vrf vrf-name |
Displays the history of data MDT groups that have been reused for the Multicast VPN (MVPN) routing and forwarding (MVRF) instance specified for the vrf-name argument. |
|
interval minutes |
Specifies the interval (in minutes) for which to display information about the history of data MDT groups that have been reused. The range is from 1 to 71512 minutes (7 weeks). |
Command History
|
Release |
Modification |
|---|---|
|
12.0(23)S |
This command was introduced. |
|
12.2(13)T |
This command was integrated into Cisco IOS Release 12.2(13)T. |
|
12.2(14)S |
This command was integrated into Cisco IOS Release 12.2(14)S. |
|
12.2(18)SXE |
Support for this command was introduced on the Supervisor Engine 720. |
|
12.2(27)SBC |
This command was integrated into Cisco IOS Release 12.2(27)SBC. |
|
12.2(33)SRA |
This command was integrated into Cisco IOS Release 12.2(33)SRA. |
Usage Guidelines
The output of the show ip pim mdt history command displays the history of reused MDT data groups for the interval specified with the interval keyword and minutes argument. The interval is from the past to the present, that is, from the time specified for the minutes argument to the time at which the command is issued.
Examples
The following is sample output from the show ip pim mdt historycommand:
Router# show ip pim vrf vrf1 mdt history interval 20
MDT-data send history for VRF - vrf1 for the past 20 minutes
MDT-data group Number of reuse
10.9.9.8 3
10.9.9.9 2
The table below describes the significant fields shown in the display.
show ip pim mdt receive
To display the data multicast distribution tree (MDT) group mappings received from other provider edge (PE) routers, use the show ip pim mdt receivecommand in privileged EXEC mode.
Command History
|
Release |
Modification |
|---|---|
|
12.0(23)S |
This command was introduced. |
|
12.2(13)T |
This command was integrated into Cisco IOS Release 12.2(13)T. |
|
12.2(14)S |
This command was integrated into Cisco IOS Release 12.2(14)S. |
|
12.2(18)SXE |
Support for this command was introduced on the Supervisor Engine 720. |
|
12.2(27)SBC |
This command was integrated into Cisco IOS Release 12.2(27)SBC. |
|
12.2(33)SRA |
This command was integrated into Cisco IOS Release 12.2(33)SRA. |
Usage Guidelines
When a router wants to switch over from the default MDT to a data MDT, it advertises the VRF source, the group pair, and the global multicast address over which the traffic will be sent. If the remote router wants to receive this data, then it will join this global address multicast group.
Examples
The following is sample output from the show ip pim mdt receivecommand using the detail keyword for further information:
Router# show ip pim vrf vpn8 mdt receive detail
Joined MDT-data groups for VRF:vpn8
group:172.16.8.0 source:10.0.0.100 ref_count:13
(10.101.8.10, 225.1.8.1), 1d13h/00:03:28/00:02:26, OIF count:1, flags:TY
(10.102.8.10, 225.1.8.1), 1d13h/00:03:28/00:02:27, OIF count:1, flags:TY
The table below describes the significant fields shown in the display.
| Table 7 | show ip pim mdt receive Field Descriptions |
|
Field |
Description |
|---|---|
|
group:172.16.8.0 |
Group that caused the data MDT to be built. |
|
source:10.0.0.100 |
VRF source that caused the data MDT to be built. |
|
ref_count:13 |
Number of (S, G) pairs that are reusing this data MDT. |
|
OIF count:1 |
Number of interfaces out of which this multicast data is being forwarded. |
|
flags: |
Information about the entry.
|
show ip pim mdt send
To display the data multicast distribution tree (MDT) groups in use, use the show ip pim mdt send command in privileged EXEC mode.
Command History
|
Release |
Modification |
|---|---|
|
12.0(23)S |
This command was introduced. |
|
12.2(13)T |
This command was integrated into Cisco IOS Release 12.2(13)T. |
|
12.2(14)S |
This command was integrated into Cisco IOS Releaes 12.2(14)S. |
|
12.2(18)SXE |
Support for this command was introduced on the Supervisor Engine 720. |
|
12.2(27)SBC |
This command was integrated into Cisco IOS Release 12.2(27)SBC. |
|
12.2(33)SRA |
This command was integrated into Cisco IOS Release 12.2(33)SRA. |
Examples
The following is sample output from the show ip pim mdt send command:
Router# show ip pim vrf vpn8 mdt send MDT-data send list for VRF:vpn8 (source, group) MDT-data group ref_count (10.100.8.10, 225.1.8.1) 232.2.8.0 1 (10.100.8.10, 225.1.8.2) 232.2.8.1 1 (10.100.8.10, 225.1.8.3) 232.2.8.2 1 (10.100.8.10, 225.1.8.4) 232.2.8.3 1 (10.100.8.10, 225.1.8.5) 232.2.8.4 1 (10.100.8.10, 225.1.8.6) 232.2.8.5 1 (10.100.8.10, 225.1.8.7) 232.2.8.6 1 (10.100.8.10, 225.1.8.8) 232.2.8.7 1 (10.100.8.10, 225.1.8.9) 232.2.8.8 1 (10.100.8.10, 225.1.8.10) 232.2.8.9 1
The table below describes the significant fields shown in the display.
show ip pim neighbor
To display information about Protocol Independent Multicast (PIM) neighbors discovered by PIMv1 router query messages or PIMv2 hello messages, use the show ip pim neighbor command in user EXEC or privileged EXEC mode.
Command History
|
Release |
Modification |
|---|---|
|
10.0 |
This command was introduced. |
|
12.0(22)S |
This command was modified. The command output was updated to display the PIM protocol version. |
|
12.0(23)S |
This command was modified. The vrf keyword and vrf-name argument were added. |
|
12.2(13)T |
This command was modified. The vrf keyword and vrf-name argument were added. |
|
12.2(14)S |
This command was integrated into Cisco IOS Release 12.2(14)S. |
|
12.2(18)SXE |
Support for this command was introduced on the Supervisor Engine 720. |
|
12.0(30)S |
This command was modified. The "P" flag was added. |
|
12.2(28)SB |
This command was integrated into Cisco IOS Release 12.2(28)SB. |
|
12.2(33)SRA |
This command was modified. The "P" flag was added. |
|
12.2(31)SB2 |
This command was modified. The "P" flag was added. |
|
12.2(33)SXH |
This command was modified. The "P" flag was added. |
|
12.4(20)T |
This command was modified. The "P" flag was added. |
|
12.2(33)SXI |
This command was modified. The "G" flag was added. |
|
12.2(33)SRE |
This command was modified. The "G" flag was added. |
|
Cisco IOS XE Release 2.6 |
This command was integrated into Cisco IOS XE Release 2.6. |
|
15.0(1)S |
This command was integrated into Cisco IOS Release 15.0(1)S. |
Usage Guidelines
Use this command to display PIM neighbors discovered by PIMv1 router query messages or PIMv2 hello messages.
Use the optional interface-type and interface-number arguments to restrict the output to display only information about the PIM neighbor reachable on the specified interface.
Examples
The following is sample output from the show ip pim neighbor command:
Router# show ip pim neighbor
PIM Neighbor Table
Mode: B - Bidir Capable, DR - Designated Router, N - Default DR Priority,
S - State Refresh Capable
Neighbor Interface Uptime/Expires Ver DR
Address Prio/Mode
10.0.0.1 GigabitEthernet10/2 00:01:29/00:01:15 v2 1 / S
10.0.0.3 GigabitEthernet10/3 00:01:15/00:01:28 v2 1 / DR S P
The table below describes the significant fields shown in the display.
| Table 9 | show ip pim neighbor Field Descriptions |
|
Field |
Description |
||
|---|---|---|---|
|
Neighbor Address |
IP address of the PIM neighbor. |
||
|
Interface |
Interface type and number on which the neighbor is reachable. |
||
|
Uptime |
The total uptime of the neighbor (in hours:minutes:seconds). |
||
|
Expires |
The time before a neighbor is timed out and until the next PIM hello is received (in hours:minutes:seconds). |
||
|
Ver |
The version of PIM running on the neighbor's interface. |
||
|
DR Prio |
The priority of the PIM interface for designated router (DR) election. The possible values that can be displayed under this column are as follows: a value from 0 to 4294967294 or the "N" flag. The default DR priority is set to 1.
When a DR is a candidate for election, the following conditions apply:
|
||
|
|||
|
Mode |
Information about the DR and other PIM capabilities:
|
Related Commands
|
Command |
Description |
|---|---|
|
ip pim state-refresh disable |
Disables the processing and forwarding of PIM dense mode state refresh control messages on a PIM router. |
|
ip pim state-refresh origination-interval |
Configures the origination of and the interval for the PIM dense mode state refresh control messages on a PIM router. |
|
show ip pim interface |
Displays information about interfaces configured for PIM. |
show ip pim rp
To display active rendezvous points ( RPs) that are cached with associated multicast routing entries, use the show ip pim rpcommand in user EXEC or privileged EXEC mode.
Syntax Description
|
vrf |
(Optional) Supports the multicast VPN routing and forwarding (VRF) instance. |
|
vrf-name |
(Optional) Name assigned to the VRF. |
|
mapping |
(Optional) Displays all group-to-RP mappings of which the router is aware (either configured or learned from Auto-RP). |
|
metric |
(Optional) Displays the unicast routing metric to the RPs configured statically or learned via Auto-RP or the bootstrap router (BSR). |
|
rp-address |
(Optional) RP IP address. |
Command History
|
Release |
Modification |
|---|---|
|
10.2 |
This command was introduced. |
|
12.1(2)T |
The metric keyword and rp-address argument were added. |
|
12.0(23)S |
The vrf keyword and vrf-name argument were added. |
|
12.2(13)T |
The vrf keyword and vrf-name argument were added. |
|
12.2(14)S |
This command was integrated into Cisco IOS Release 12.2(14)S. |
|
12.2(27)SBC |
This command was integrated into Cisco IOS Release 12.2(27)SBC. |
|
12.2(33)SRA |
This command was integrated into Cisco IOS Release 12.2(33)SRA. |
|
12.2SX |
This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware. |
Usage Guidelines
The Protocol Independent Multicast (PIM) version known for an RP influences the type of PIM register messages (Version 1 or Version 2) that the router sends when acting as the designated router (DR) for an active source. If an RP is statically configured, the PIM version of the RP is not set and the router, if required to send register packets, tries to send PIM Version 2 register packets. If sending PIM Version 2 packets fails, the router sends PIM Version 1 register packets.
The version of the RP displayed in the show ip pim rp command output can change according to the operations of the router. When the group is created, the version shown is for the RP in the RP mapping cache. Later, the version displayed by this command may change. If this router is acting as a DR for an active source, the router sends PIM register messages. The PIM register messages are answered by the RP with PIM register stop messages. The router learns from these PIM register stop messages the actual PIM version of the RP. Once the actual PIM version of the RP is learned, this command displays only this version. If the router is not acting as a DR for active sources on this group, then the version shown for the RP of the group does not change. In this case, the PIM version of the RP is irrelevant to the router because the version of the RP influences only the PIM register messages that this router must send.
When you enter the show ip pim rp mapping command, the version of the RP displayed in the output is determined only by the method through which an RP is learned. If the RP is learned from Auto-RP then the RP displayed is either "v1" or "v2, v1." If the RP is learned from a static RP definition, the RP version is undetermined and no RP version is displayed in the output. If the RP is learned from the BSR, the RP version displayed is "v2."
Examples
The following is sample output from the show ip pim rpcommand:
Router# show ip pim rp
Group:227.7.7.7, RP:10.10.0.2, v2, v1, next RP-reachable in 00:00:48
The following is sample output from the show ip pim rpcommand when the mapping keyword is specified:
Router# show ip pim rp mapping
PIM Group-to-RP Mappings
This system is an RP (Auto-RP)
This system is an RP-mapping agent
Group(s) 227.0.0.0/8
RP 10.10.0.2 (?), v2v1, bidir
Info source:10.10.0.2 (?), via Auto-RP
Uptime:00:01:42, expires:00:00:32
Group(s) 228.0.0.0/8
RP 10.10.0.3 (?), v2v1, bidir
Info source:10.10.0.3 (?), via Auto-RP
Uptime:00:01:26, expires:00:00:34
Group(s) 229.0.0.0/8
RP 10.10.0.5 (mcast1.cisco.com), v2v1, bidir
Info source:10.10.0.5 (mcast1.cisco.com), via Auto-RP
Uptime:00:00:52, expires:00:00:37
Group(s) (-)230.0.0.0/8
RP 10.10.0.5 (mcast1.cisco.com), v2v1, bidir
Info source:10.10.0.5 (mcast1.cisco.com), via Auto-RP
Uptime:00:00:52, expires:00:00:37
The following is sample output from the show ip pim rpcommand when the metric keyword is specified:
Router# show ip pim rp metric
RP Address Metric Pref Metric Flags RPF Type Interface
10.10.0.2 0 0 L unicast Loopback0
10.10.0.3 90 409600 L unicast Ethernet3/3
10.10.0.5 90 435200 L unicast Ethernet3/3
The table below describes the significant fields shown in the displays.
| Table 10 | show ip pim rp Field Descriptions |
|
Field |
Description |
|---|---|
|
Group |
Address of the multicast group about which to display RP information. |
|
RP |
Address of the RP for that group. |
|
v2 |
Indicates that the RP is running PIM version 2. |
|
v1 |
Indicates that the RP is running PIM version 1. |
|
bidir |
Indicates that the RP is operating in bidirectional mode. |
|
Info source |
RP mapping agent that advertised the mapping. |
|
(?) |
Indicates that no Domain Name System (DNS) name has been specified. |
|
via Auto-RP |
Indicates that RP was learned via Auto-RP. |
|
Uptime |
Length of time the RP has been up (in days and hours). If less than 1 day, time is shown in hours, minutes, and seconds. |
|
expires |
Time in (hours, minutes, and seconds) in which the entry will expire. |
|
Metric Pref |
The preference value used for selecting the unicast routing metric to the RP announced by the designated forwarder (DF). |
|
Metric |
Unicast routing metric to the RP announced by the DF. |
|
Flags |
Indicates the flags set for the specified RP. The following are descriptions of possible flags: |
|
RPF Type |
Routing table from which this route was obtained, either unicast, Distance Vector Multicast Routing Protocol (DVMRP), or static mroute. |
|
Interface |
Interface type and number that is configured to run PIM. |
show ip pim rp mapping
To display the mappings for the PIM group to the active rendezvous points, use the show ip pim rp mappingcommand in user EXEC or privileged EXEC mode.
Command Default
If you do not specify an rp-address, the mappings for all the active rendezvous points are displayed.
Command History
|
Release |
Modification |
|---|---|
|
12.2(14)SX |
Support for this command was introduced on the Supervisor Engine 720. |
|
12.2(18)SXE |
This command was changed to add the vrfvrf-name keyword and argument. |
|
12.2(33)SRA |
This command was integrated into Cisco IOS Release 12.2(33)SRA. |
|
15.2(1)S |
This command was integrated into Cisco IOS Release 15.2(1)S. The output was modified to add the values for auto-RP and BSR mapping count and limit. |
Usage Guidelines
This command is not supported on Cisco 7600 series routers that are configured with a Supervisor Engine 2.
Examples
In Cisco IOS Release 15.2(1)S and later releases, the output includes the values for auto-RP or BSR mapping count and limit:
Router# show ip pim rp mapping
PIM Group-to-RP Mappings
Group(s) 224.0.0.0/4
RP 192.168.255.101 (?), v2v1
Info source: 192.168.255.101 (?), elected via Auto-RP
Uptime: 00:01:38, expires: 00:02:52
Auto-RP mapping count 1, limit 2
This example shows how to display the mappings for the PIM group to the active rendezvous points:
Router# show ip pim rp mapping
PIM Group-to-RP Mappings
This system is an RP-mapping agent
Group(s) 172.16.0.0/16
RP 10.6.6.6 (?), v2v1
Info source: 10.6.6.6 (?), elected via Auto-RP ---> learned via Auto-RP
and the elected RP.
Uptime: 22:36:49, expires: 00:02:04
Group(s) 192.168.0.0/24
RP 10.9.9.9 (?), v2v1, bidir
Info source: 10.9.9.9 (?), elected via Auto-RP
Uptime: 22:36:20, expires: 00:02:37
Group(s) 172.16.0.0/24
RP 10.2.2.2 (?), v2v1, bidir
Info source: 10.2.2.2 (?), elected via Auto-RP
Uptime: 22:36:24, expires: 00:02:29
Group(s) 172.16.0.0/24
RP 10.9.9.9 (?), v2v1, bidir
Info source: 10.9.9.9 (?), elected via Auto-RP
Uptime: 22:36:21, expires: 00:02:35
The table below describes the fields that are shown in the example.
| Table 11 | show ip pim rp mapping Field Descriptions |
|
Field |
Description |
|---|---|
|
Info source |
ACL number. |
|
Static |
Group-to-mapping information from the static rendezvous-point configuration. |
|
Bidir Mode |
Status of whether the rendezvous point is operating in bidirectional mode. |
|
RP |
Address of the rendezvous point for that group. |
|
(?) |
Status that shows no Domain Name System (DNS) name has been specified. |
|
count |
Number of RP or BSR groups configured. |
|
limit |
Maximum number of PIM groups that can be created. |
show ip pim rp-hash
To display which rendezvous point (RP) is being selected for a specified group, use the show ip pim rp-hashcommand in user EXEC or privileged EXEC mode.
Command History
|
Release |
Modification |
|---|---|
|
11.3 T |
This command was introduced. |
|
12.0(23)S |
The vrf keyword and vrf-name argument were added. |
|
12.2(13)T |
This command was integrated into Cisco IOS Release 12.2(13)T. |
|
12.2(14)S |
This command was integrated into Cisco IOS Release 12.2(14)S. |
|
12.2(27)SBC |
This command was integrated into Cisco IOS Release 12.2(27)SBC. |
|
12.2(33)SRA |
This command was integrated into Cisco IOS Release 12.2(33)SRA. |
|
12.2SX |
This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware. |
Usage Guidelines
This command displays which RP was selected for the group specified. It also shows whether this RP was selected by Auto-RP or the PIM Version 2 bootstrap mechanism.
Examples
The following is sample output from the show ip pim rp-hash command with the group address 239.1.1.1 specified:
Router# show ip pim rp-hash 239.1.1.1
RP 172.16.24.12 (mt1-47a.cisco.com), v2
Info source: 172.16.24.12 (mt1-47a.cisco.com), via bootstrap
Uptime: 05:15:33, expires: 00:02:01
The table below describes the significant fields shown in the display.
| Table 12 | show ip pim rp-hash Field Descriptions |
|
Field |
Description |
|---|---|
|
RP 172.16.24.12 (mt1-47a.cisco.com), v2 |
Address of the RP for the group specified (239.1.1.1). Within parentheses is the DNS name of the RP. If the address of the RP is not registered in the DNS, a question mark (?) is displayed. PIM Version 2 configured. |
|
Info source: 172.16.24.12 (mt1-47a.cisco.com), via bootstrap |
Indicates from which system the router learned this RP information, along with the DNS name of the source. RP was selected by the bootstrap mechanism. In this case, the BSR is also the RP. |
|
Uptime |
Length of time (in hours, minutes, and seconds) that the router has known about this RP. |
|
expires |
Time (in hours, minutes, and seconds) after which the information about this RP expires. If the router does not receive any refresh messages in this time, it will discard information about this RP. |
show ip pim rp-hash (BSR)
To display which rendezvous point is being selected for a specified group, use the show ip pim rp-hashcommand in user EXEC or privileged EXEC mode.
Usage Guidelines
This command displays which rendezvous point was selected for the group specified. It also shows whether this rendezvous point was selected by Auto-RP or the PIM Version 2 bootstrap mechanism.
Examples
This example shows how to display which rendezvous point is being selected for a specified group:
Router# show ip pim rp-hash 239.1.1.1
RP 172.16.24.12 (mt1-47a.cisco.com), v2
Info source: 172.16.24.12 (mt1-47a.cisco.com), via bootstrap
Uptime: 05:15:33, expires: 00:02:01
The table below describes the fields shown in the display.
| Table 13 | show ip pim rp-hash Field Descriptions |
|
Field |
Description |
|---|---|
|
RP 172.16.24.12 (mt1-47a.cisco.com), v2 |
Address of the rendezvous point for the group specified (239.1.1.1). The DNS name of the rendezvous point within the parentheses. If the address of the rendezvous point is not registered in the DNS, a question mark (?) is displayed. PIM Version 2 is configured. |
|
Info source: 172.16.24.12 (mt1-47a.cisco.com), via bootstrap |
Which system the router learned this rendezvous-point information and the DNS name of the source. The rendezvous point was selected by the bootstrap mechanism. In this case, the BSR is also the rendezvous point. |
|
Uptime |
Length of time (in hours, minutes, and seconds) that the router has known about this rendezvous point. |
|
expires |
Time (in hours, minutes, and seconds) after which the information about this rendezvous point expires. If the router does not receive any refresh messages in this time, it discards information about this rendezvous point. |
show ip pim snooping
To display the information about IP PIM snooping, use the show ip pim snoopingcommand in user EXEC or privileged EXEC mode.
Global Status
VLAN Status
Syntax Description
|
vlan vlan-id |
Displays information for a specific VLAN; valid values are from 1 to 4094. |
|
neighbor |
(Optional) Displays information about the neighbor database. |
|
mac-group |
(Optional) Displays information about the GDA database in Layer 2. |
|
statistics |
(Optional) Displays information about the VLAN statistics. |
|
mroute |
(Optional) Displays information about the mroute database. |
|
source-ip |
(Optional) Source IP address. |
|
group-ip |
(Optional) Group IP address. |
Usage Guidelines
This command is not supported on Cisco 7600 series routers that are configured with a Supervisor Engine 2.
Examples
This example shows how to display the information about the global status:
Router# show ip pim snooping
Global runtime mode: Enabled
Global admin mode : Enabled
Number of user enabled VLANs: 1
User enabled VLANs: 10
This example shows how to display the information about a specific VLAN:
Router# show ip pim snooping vlan 10
3 neighbors (0 DR priority incapable, 0 Bi-dir incapable)
6 mroutes, 3 mac entries
DR is 10.10.10.4
RP DF Set
This example shows how to display the information about the neighbor database for a specific VLAN:
Router# show ip pim snooping vlan 10 neighbor
IP Address Mac address Port Uptime/Expires Flags
10.10.10.2 000a.f330.344a 3/13 00:09:57/00:01:22
10.10.10.1 000a.f330.334a 3/12 00:09:44/00:01:21
10.10.10.4 000a.f330.3c00 15/01 00:09:57/00:01:22 DR
Number of Neighbors = 3
This example shows how to display the information about the GDA database for a specific VLAN in Layer 2:
Router# show ip pim snooping vlan 10 mac-group
Mac address Group address Uptime/Expires Outgoing Ports
VLAN 10: 4 mac entries
0100.5e03.0101 225.3.1.1 4d01h/00:03:04 1/2 1/3 1/48 15/1
0100.5e02.0101 225.2.1.1 4d01h/00:03:13 1/2 1/3 1/48 15/1
0100.5e05.0101 225.5.1.1 4d01h/00:03:01 1/2 1/3 1/48 15/1
0100.5e04.0101 225.4.1.1 4d01h/00:03:19 1/2 1/3 1/48 15/1
PE.100#
PE.100#
PE.100#
PE.100#
This example shows how to display the detailed statistics for a specific VLAN:
Router# show ip pim snooping vlan 10 statistics
PIMv2 statistics for vlan 10:
Hello : 811
Join/Prunes : 1332
RP DF Election : 0
Asserts : 133
Other types : 0
Hello option holdtime [1] : 811
Hello option Generation ID[20] : 544
Hello option DR priority[19] : 544
Hello option Bi-dir capable[22] : 0
Hello option Fast Hold[65005] : 0
Hello option Lan Prune Delay[2] : 0
Hello option Tag switching [17] : 0
Hello option PIM-DM State Refresh[21] : 544
Hello option Deprecated Cisco DR priority[18] : 0
Error - Hello length too short : 0
Error - Hello hold option missing : 0
Error - Hello option length : 0
Error - Hello option unknown : 0
Error - Join/Prune Address Family : 0
Error - Join/Prune Parser malloc failure : 0
Error - Join/Prune Unknown up/down neighbor : 0
Error - Join/Prune Malformed packet discards : 0
Error - RPDF election Address Family : 0
Error - RPDF Unknown up/down neighbor : 0
Error - Generic packet input error : 0
This example shows how to display the information about the mroute database for all mrouters in a specific VLAN:
Router# show ip pim snooping vlan 10 mroute
Number of Mroutes = 6
Flags: J/P - (*,G) Join/Prune, j/p - (S,G) Join/Prune
SGR-P - (S,G,R) Prune
VLAN 10: 4 mroutes
(*, 225.3.1.1), 4d01h/00:03:06
10.10.10.120->10.10.10.105, 4d01h/00:03:06 , J
Downstream ports: 1/2
Upstream ports: 1/48
Outgoing ports: 1/2 1/48
(*, 225.2.1.1), 4d01h/00:03:11
10.10.10.130->10.10.10.120, 4d01h/00:03:11 , J
Downstream ports: 1/3
Upstream ports: 1/2
Outgoing ports: 1/2 1/3
(*, 225.5.1.1), 4d01h/00:02:57 10.10.10.120->
10.10.10.10, 4d01h/00:02:49 , J
10.10.10.130->10.10.10.10, 4d01h/00:02:57 , J
10.10.10.105->10.10.10.10, 4d01h/00:02:41 , J
Downstream ports: 1/2 1/3 1/48
Upstream ports: 15/1
Outgoing ports: 1/2 1/3 1/48 15/1
(*, 225.4.1.1), 4d01h/00:03:16
10.10.10.105->10.10.10.130, 4d01h/00:03:16 , J
Downstream ports: 1/48
Upstream ports: 1/3
Outgoing ports: 1/3 1/48
This example shows how to display the information about the PIM mroute for a specific source address:
Router# show ip pim snooping vlan 10 mroute 172.16.100.100
(*, 172.16.100.100), 00:16:36/00:02:36
10.10.10.1->10.10.10.2, 00:16:36/00:02:36, J
Downstream ports: 3/12
Upstream ports: 3/13
Outgoing ports: 3/12 3/13
This example shows how to display the information about the PIM mroute for a specific source and group address:
Router# show ip pim snooping vlan 10 mroute 192.168.0.0 172.16.10.10
(192.168.0.0, 172.16.10.10), 00:03:04/00:00:25
10.10.10.1->10.10.10.2, 00:03:04/00:00:25, j
Downstream ports: 3/12
Upstream ports: 3/13
Outgoing ports: 3/12 3/13
The table below describes the significant fields shown in the display.
show ip pim tunnel
To display information about Protocol Independent Multicast (PIM) tunnel interfaces, use the show ip pim tunnelcommand in user EXEC or privileged EXEC mode.
Syntax Description
|
all-vrfs |
(Optional) Displays information about PIM tunnel interfaces associated with Multicast Virtual Private Network (MVPN) routing and forwarding (MVRF) instances (including the global table). |
|
vrf vrf-name |
(Optional) Displays information about PIM tunnel interfaces associated with the MVRF instances associated with MVRF specified for the vrf-name argument. |
|
interface-number |
(Optional) PIM tunnel interface number. |
|
verbose |
(Optional) Displays detailed information about PIM tunnel interfaces. |
Usage Guidelines
Use the show ip pim tunnelcommand to display information about PIM tunnel interfaces.
PIM tunnel interfaces are used by the IPv4 Multicast Forwarding Information Base (MFIB) for the PIM sparse mode (PIM-SM) registration process. Two types of PIM tunnel interfaces are used by the the IPv4 MFIB:
- A PIM encapsulation tunnel (PIM Encap Tunnel)
- A PIM decapsulation tunnel (PIM Decap Tunnel).
The PIM Encap Tunnel is dynamically created whenever a group-to-Rendezvous Point (RP) mapping is learned (via Auto-RP, bootstrap router (BSR), or static RP configuration). The PIM Encap Tunnel is used to encapsulate multicast packets sent by first-hop Designated Routers (DRs) that have directly connected sources.
Similar to the PIM Encap Tunnel, the PIM Decap Tunnel interface is dynamically created--with the exception that it is created only on the RP whenever a group-to-RP mapping is learned. The PIM Decap Tunnel interface is used by the RP to decapsulate PIM register messages.
 Note | PIM tunnels will not appear in the running configuration. |
The following syslog message will appear when a PIM tunnel interface is created:
* %LINEPROTO-5-UPDOWN: Line protocol on Interface Tunnel<interface_number>, changed state to up
Examples
The following is sample output from the show ip pim tunnel command taken from a RP. The output is used to verify the PIM Encap and Decap Tunnel on the RP.
Router# show ip pim tunnel
Tunnel0
Type : PIM Encap
RP : 192.168.6.6*
Source: 192.168.6.6
Tunnel1
Type : PIM Decap
RP : 192.168.6.6*
Source: -
Note | The asterisk (*) indicates that the router is the RP. The RP will always have a PIM Encap and Decap Tunnel interface. |
The following is sample output from the show ip pim tunnel command taken from a non-RP. The output is used to confirm that a PIM Encap Tunnel has been created on a non-RP router.
Router# show ip pim tunnel
Tunnel0
Type : PIM Encap
RP : 192.168.6.6
Source: 192.168.67.7
show ip pim vc
To display ATM virtual circuit (VC) status information for multipoint VCs opened by Protocol Independent Multicast (PIM), use the show ip pim vccommand in user EXEC or privileged EXEC mode.
Command History
|
Release |
Modification |
|---|---|
|
11.3 |
This command was introduced. |
|
12.2(33)SRA |
This command was integrated into Cisco IOS Release 12.2(33)SRA. |
|
12.2SX |
This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware. |
Examples
The following is sample output from the show ip pim vc command:
Router# show ip pim vc
IP Multicast ATM VC Status
ATM0/0 VC count is 5, max is 200
Group VCD Interface Leaf Count Rate
224.2.2.2 26 ATM0/0 1 0 pps
224.1.1.1 28 ATM0/0 1 0 pps
224.4.4.4 32 ATM0/0 2 0 pps
224.5.5.5 35 ATM0/0 1 0 pps
The table below describes the significant fields shown in the display.
| Table 15 | show ip pim vc Field Descriptions |
|
Field |
Description |
|---|---|
|
ATM0/0 |
ATM slot and port number on the interface. |
|
VC count |
Number of VCs opened by PIM. |
|
max |
Maximum number of VCs that PIM is allowed to open, as configured by the ip pim vc-count command. |
|
Group |
IP address of the multicast group to which the router is multicasting. |
|
VCD |
Virtual circuit descriptor. |
|
Interface |
Outgoing interface. |
|
Leaf Count |
Number of routers that have joined the group and are members of that multipoint VC. |
|
Rate |
Rate (in packets per second) as configured by the ip pim minimum-vc-rate command. |
show ip rpf
To display the information that IP multicast routing uses to perform the Reverse Path Forwarding (RPF) check for a multicast source, use the show ip rpfcommand in user EXEC or privileged EXEC mode.
Cisco ASR 1000 Series
Syntax Description
|
vrf vrf-name |
(Optional) Displays the information that IP multicast routing uses to perform the RPF check for a multicast source associated with the Multicast Virtual Private Network (MVPN) routing and forwarding (MVRF) instance specified for the vrf-nameargument. |
|
route-distinguisher |
Route distinguisher (RD) of a VPNv4 prefix. Entering the route-distinguisher argument displays RPF information related to the specified VPN route. You can enter an RD in either of these formats: |
|
source-address |
IP address or name of a multicast source for which to display RPF information. |
|
group-address |
(Optional) IP address or name of a multicast group for which to display RPF information. |
|
rd route-distinguisher |
(Optional) Displays the Border Gateway Protocol (BGP) RPF next hop for the VPN route associated with the RD specified for the route-distinguisher argument. You can enter an RD in either of these formats: |
|
metric |
(Optional) Displays the unicast routing metric. |
Command History
|
Release |
Modification |
|---|---|
|
11.0 |
This command was introduced. |
|
12.1(2)T |
This command was modified. The metric keyword was added. |
|
12.0(23)S |
This command was modified. The vrf keyword and vrf-name argument were added. |
|
12.2(13)T |
This command was integrated into Cisco IOS Release 12.2(13)T. |
|
12.2(14)S |
This command was integrated into Cisco IOS Release 12.2(14)S. |
|
12.0(29)S |
This command was modified. The group-addressargument, rd keyword, and route-distinguisher argument were added for the Multicast VPN Inter-AS Support feature. |
|
12.2(27)SBC |
This command was integrated into Cisco IOS Release 12.2(27)SBC. |
|
12.2(33)SRA |
This command was integrated into Cisco IOS Release 12.2(33)SRA. The group-addressargument, rd keyword, and route-distinguisher argument were added for the Multicast VPN Inter-AS Support feature. |
|
12.2(31)SB2 |
This command was modified. The output was modified to indicate that the Multicast VPN Extranet VRF Select feature is being used to perform the RPF lookup based on the group address and the VRF where the RPF lookup is being performed. |
|
12.2(33)SXH |
This command was modified. The group-addressargument, rd keyword, and route-distinguisher argument were added for the Multicast VPN Inter-AS Support feature. |
|
12.4(20)T |
This command was modified. The group-addressargument, rd keyword, and route-distinguisher argument were added for the Multicast VPN Inter-AS Support feature. |
|
15.0(1)M |
This command was modified. The output was modified to indicate that the Multicast VPN Extranet VRF Select feature is being used to perform the RPF lookup based on the group address and the VRF where the RPF lookup is being performed. |
|
Cisco IOS XE Release 3.2S |
This command was implemented on Cisco ASR 1000 series routers. |
|
15.1(1)SG |
This command was integrated into Cisco IOS Release 15.1(1)SG. |
|
Cisco IOS XE Release 3.3SG |
This command was integrated into Cisco IOS XE Release 3.3SG. |
Usage Guidelines
Use the show ip rpf command to display the information that IP multicast routing uses to perform the Reverse Path Forwarding (RPF) check for a multicast source. When performing the RPF calculation, the router can use multiple routing tables (the unicast routing table, Multiprotocol Border Gateway Protocol (MBGP) table, Distance Vector Multicast Routing Protocol [DVMRP] routing table, or static multicast routes) to determine the interface on which traffic from a source should arrive (the RPF interface). Because the RPF check can be performed from multiple routing tables, the show ip rpfcommand can be used to identify the source of the retrieved information.
In a Multi-Topology Routing (MTR) routing environment, a router can perform RPF lookups from multiple unicast Routing Information Bases (RIBs)--instead of only looking at the original unique unicast RIB. By default, the Cisco IOS software supports the pre-MTR IP multicast behavior; that is, the RPF check is performed on routes in the unicast RIB (base unicast topology).
Note | MTR introduces a multicast topology (base multicast topology) that is completely independent from the unicast topology. MTR integration with multicast allows the path of multicast traffic to be controlled in the network. |
Examples
The following is sample output from the show ip rpfcommand:
Router# show ip rpf 172.16.10.13
RPF information for host1 (172.16.10.13)
RPF interface: BRI0
RPF neighbor: sj1.cisco.com (172.16.121.10)
RPF route/mask: 172.16.0.0/255.255.0.0
RPF type: unicast
RPF recursion count: 0
Doing distance-preferred lookups across tables
The following is sample output from the show ip rpf command with the optional vrf keyword, vrf-name argument, and group-address argument:
Router# show ip rpf vrf green 10.1.1.100 232.6.6.6
RPF information for ? (10.1.1.100)
RPF interface: Ethernet3/0
RPF neighbor: ? (10.1.1.5)
RPF route/mask: 10.1.1.0/24
RPF type: unicast (rip)
RPF recursion count: 0
Doing distance-preferred lookups across tables
Using Group Based VRF Select, RPF VRF: blue
The following is sample output from the show ip rpfcommand with the metric keyword:
Router# show ip rpf 172.16.10.13 metric
RPF information for host1.cisco.com (172.16.10.13)
RPF interface: BRI0
RPF neighbor: neighbor.cisco.com (172.16.121.10)
RPF route/mask: 172.16.0.0/255.255.0.0
RPF type: unicast
RPF recursion count: 0
Doing distance-preferred lookups across tables
Metric preference: 110
Metric: 11
The following is sample output from the show ip rpf command in an MTR routing environment. In Cisco IOS releases that support MTR, the "RPF topology" field was introduced to indicate which RIB topology is being used for the RPF lookup. For the "RPF topology" field in this example, the first topology listed (ipv4 multicast base) indicates where the nexthop of the RPF lookup is being conducted and the second topology listed (ipv4 unicast data) indicates where the route originated from.
Router# show ip rpf 10.30.30.32
RPF information for ? (10.30.30.32)
RPF interface: Ethernet1/0
RPF neighbor: ? (10.1.1.32)
RPF route/mask: 10.30.30.32/32
RPF type: unicast (ospf 100)
Doing distance-preferred lookups across tables
RPF topology: ipv4 multicast base, originated from ipv4 unicast data
The table below describes the fields shown in the displays.
| Table 16 | show ip rpf Field Descriptions |
|
Field |
Description |
|---|---|
|
RPF information for |
Hostname and source address for which RPF information is displayed. |
|
RPF interface |
For the given source, the interface from which the router expects to receive packets. |
|
RPF neighbor |
For the given source, the neighbor from which the router expects to receive packets. |
|
RPF route/mask |
Route number and mask that matched against this source. |
|
RPF type |
Routing table from which this route was obtained, either unicast, MBGP, DVMRP, or static mroutes. |
|
RPF recursion count |
The number of times the route is recursively resolved. |
|
Doing distance-preferred |
Whether RPF was determined based on distance or length of mask. |
|
Using Group Based VRF Select, RPF VRF: |
The RPF lookup was based on the group address and the VRF where the RPF lookup is being performed. |
|
Metric preference |
The preference value used for selecting the unicast routing metric to the RP announced by the designated forwarder (DF). |
|
Metric |
Unicast routing metric to the RP announced by the DF. |
|
RPF topology |
RIB topology being used for the RPF lookup, and, if originated from a different RIB topology, which RIB topology the route originated from. |
The following is sample output from the show ip rpf command in a Multicast only Fast Re-Route (MoFRR) enabled environment. The command output shows that MoFRR is enabled for the 209.165.200.226 multicast source IP address. The relevant command output is shown in bold.
Router# show ip rpf 209.165.200.226 RPF information for ? (209.165.200.226) MoFRR Enabled RPF interface: Ethernet1/4 RPF neighbor: ? (209.165.201.2) RPF route/mask: 255.255.255.225 RPF type: unicast (ospf 200) Doing distance-preferred lookups across tables RPF topology: ipv4 multicast base, originated from ipv4 unicast base Secondary RPF interface: Ethernet1/3 Secondary RPF neighbor: ? (209.165.202.128)
The table below describes the fields shown in the displays.
| Table 17 | show ip rpf Command Output in an MoFRR-Enabled Environment: Field Descriptions |
|
Field |
Description |
|---|---|
|
RPF information for |
Hostname and source address for which RPF information is displayed, including MoFRR status. |
|
RPF interface |
For the given source, the interface from which the router expects to receive packets. |
|
RPF neighbor |
For the given source, the neighbor from which the router expects to receive packets. |
|
RPF route/mask |
Route number and mask that matched against this source. |
|
RPF type |
Routing table from which this route was obtained, either unicast, MBGP, DVMRP, or static mroutes. |
|
Doing distance preferred |
Whether RPF was determined based on distance or length of mask. |
|
RPF topology |
RIB topology being used for the RPF lookup, and, if originated from a different RIB topology, which RIB topology the route originated from. |
|
Secondary RPF interface |
For the given source, the secondary interface from which the router expects to receive packets. |
|
Secondary RPF neighbor |
For the given source, the secondary neighbor from which the router expects to receive packets. |
show ip rpf events
To display the last 15 triggered multicast Reverse Path Forwarding (RPF) check events, use the show ip rpf eventscommand in user EXEC or privileged EXEC mode.
Command History
|
Release |
Modification |
|---|---|
|
12.0(22)S |
This command was introduced. |
|
12.0(23)S |
The vrf keyword and vrf-name argument were added. |
|
12.2(14)S |
The vrf keyword and vrf-name argument were added. |
|
12.2(15)T |
This command was integrated into Cisco IOS Release 12.2(15)T. |
|
12.2(33)SRA |
This command was integrated into Cisco IOS Release 12.2(33)SRA. |
|
12.2SX |
This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware. |
Usage Guidelines
Use this command to determine the most recent triggered multicast RPF check events.
Examples
The following is sample output from the show ip rpf eventscommand:
Router# show ip rpf events
Last 15 triggered multicast RPF check events
RPF backoff delay:500 msec
RPF maximum delay:5 sec
DATE/TIME BACKOFF PROTOCOL EVENT RPF CHANGES
Mar 7 03:24:10.505 500 msec Static Route UP 0
Mar 7 03:23:11.804 1000 sec BGP Route UP 3
Mar 7 03:23:10.796 500 msec ISIS Route UP 0
Mar 7 03:20:10.420 500 msec ISIS Route Down 3
Mar 7 03:19:51.072 500 msec Static Route Down 0
Mar 7 02:46:32.464 500 msec Connected Route UP 3
Mar 7 02:46:24.052 500 msec Static Route Down 0
Mar 7 02:46:10.200 1000 sec Connected Route UP 3
Mar 7 02:46:09.060 500 msec OSPF Route UP 3
Mar 7 02:46:07.416 500 msec OSPF Route Down 0
Mar 7 02:45:50.423 500 msec EIGRP Route UP 3
Mar 7 02:45:09.679 500 msec EIGRP Route Down 0
Mar 7 02:45:06.322 500 msec EIGRP Route Down 2
Mar 7 02:33:09.424 500 msec Connected Route UP 0
Mar 7 02:32:28.307 500 msec BGP Route UP 3
The following is sample output from the show ip rpf eventscommand when the ip multicast rpf backoff command is used with the disable keyword, disabling the triggered RPF check function:
Router# show ip rpf events
Last 15 triggered multicast RPF check events
Note:Triggered RPF disabled!
RPF backoff delay:50 msec
RPF maximum delay:2 sec
DATE/TIME BACKOFF PROTOCOL EVENT RPF CHANGES
Sep 4 06:25:31.707 500 msec Connected Route UP 0
Sep 4 06:25:30.099 500 msec Connected Route UP 0
The table below describes the significant fields shown in the display.
| Table 18 | show ip rpf events Field Descriptions |
|
Field |
Description |
|---|---|
|
RPF backoff delay |
The configured amount of time (in milliseconds) allowed for the initial backoff delay. |
|
RPF maximum delay |
The maximum configured amount of time (in seconds) allowed for a backoff delay. |
|
DATE/TIME |
The date and time (in hours:minutes:seconds) an RPF event occurred. |
|
BACKOFF |
The actual backoff delay (in milliseconds) after which the RPF check was done. |
|
PROTOCOL |
The protocol that triggered the RPF check. |
|
EVENT |
This RPF check was caused by a route that went up or down, or was modified. |
|
RPF CHANGES |
The number of multicast routes that were affected by the RPF change. |
show ip rpf select
To display group-to-VPN routing and forwarding (VRF) mappings, use the show ip rpf select command in user EXEC or privileged EXEC mode.
Command Default
If the optional vrf keyword and vrf-name argument are omitted, the show ip rpf select command displays all group-to-VRF mappings.
Usage Guidelines
Use the show ip rpf select command after configuring group-based VRF selection policies to display the configured group-to-VRF mappings. The output displays information about group-based VRF selection policies, including the group address, the VRF mapped to the group where the Reverse Path Forwarding (RPF) lookup is performed, and the name of the access control list (ACL) applied to the policy.
Use the ip multicast rpf select command to configure group-based VRF selection policies. By defining group-based VRF selection policies, you can configure RPF lookups originating in a receiver MVRF or in the global routing table to be resolved in a source MVRF or in the global routing table based on group address.
Examples
The following is sample output from the show ip rpf select command:
Router# show ip rpf select
Multicast Group-to-Vrf Mappings
Group(s): 227.7.1.1/32, RPF vrf: blue, Acl: 20
Group(s): 227.7.7.7/32, RPF vrf: blue, Acl: 20
Group(s): 239.1.1.1/32, RPF vrf: blue, Acl: 20
The table below describes the significant fields shown in the display.
show ip sap
To display the Session Announcement Protocol (SAP) cache, use the show ip sapcommand in user EXEC or privileged EXEC mode.
Command History
|
Release |
Modification |
|---|---|
|
11.1 |
The show ip sdr command was introduced. |
|
12.2 |
The show ip sdrcommand was replaced by the show ip sapcommand. |
|
12.2(33)SRA |
This command was integrated into Cisco IOS Release 12.2(33)SRA. |
|
12.2SX |
This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware. |
Usage Guidelines
If the router is configured to be a member of multicast group 224.2.127.254 (the default session directory group), it will cache SAP announcements.
If no arguments or keywords are used with this command, the system displays a sorted list of session names.
Examples
The following is sample output from the show ip sap command for a session using multicast group 224.2.197.250:
Router# show ip sap 224.2.197.250
SAP Cache - 198 entries
Session Name: Session1
Description: This broadcast is brought to you courtesy of Name1.
Group: 0.0.0.0, ttl: 0, Contiguous allocation: 1
Lifetime: from 10:00:00 PDT Jul 4 1999 until 10:00:00 PDT Aug 1 1999
Uptime: 4d05h, Last Heard: 00:01:40
Announcement source: 128.102.84.134
Created by: sample 3136541828 3139561476 IN IP4 128.102.84.134
Phone number: Sample Digital Video Lab (555) 555-5555
Email: email1 <name@email.com>
URL: http://url.com/
Media: audio 20890 RTP/AVP 0
Media group: 224.2.197.250, ttl: 127
Attribute: ptime:40
Media: video 62806 RTP/AVP 31
Media group: 224.2.190.243, ttl: 127
The table below describes the significant fields shown in the display.
| Table 20 | show ip sap Field Descriptions |
|
Field |
Description |
|---|---|
|
SAP Cache - 198 entries |
Number of entries (sessions) in the cache. |
|
Session Name: |
Name of session. |
|
Description: |
Description of the session. Individual media may have their own Description field. |
|
Group: |
IP multicast group addresses used for this session. The 0.0.0.0 IP address is displayed if individual media define separate multicast groups. |
|
ttl: |
The time-to-live (TTL) value associated with the multicast groups. |
|
Contiguous Allocation: |
Number of continuously ascending IP multicast group addresses allocated to this session. |
|
Lifetime: |
Period of time during which this session is presumed to carry traffic in the network. |
|
Uptime: |
How long (in hours, minutes, and seconds) this announcement has been stored. |
|
Last Heard: |
How long ago (in hours, minutes, and seconds) this announcement was last heard. This time is always less than the timeout value configured using the sap cache-timeout command. |
|
Announcement source: |
IP address of the host from which this session announcement was received. |
|
Created by: |
Information for identifying and tracking the session announcement. |
|
Phone number: |
Telephone number of the person or entity responsible for the session. |
|
Email: |
E-mail address of the person or entity responsible for the session. |
|
URL: |
URL for the location where further information about this session can be found. |
|
Media: |
Indicates the media type (audio, video, or data), transport port that the medium stream is sent to, transport protocol used for these media (common values are User Datagram Protocol [UDP] and Real-Time Transport Protocol [RTP]/attribute-value pair [AVP]), and list of media formats that each media instance can use. The first media format is the default format. Format identifiers are specific to the transport protocol used. |
|
Media group: |
Indicates the IP multicast group address over which the media instance is sent. |
|
Attribute: |
Indicates attributes specific to each media instance. |
show mls ip multicast
To display the MLS IP information, use the show mls ip multicast command in user EXEC or privileged EXEC mode.
Syntax Description
|
capability |
Displays information about the multicast-replication capabilities. |
|
module num |
(Optional) Specifies the module number. |
|
connected |
(Optional) Displays the installed interface or mask entries. |
|
group |
(Optional) Displays the entries for a specific multicast-group address. |
|
hostname |
Group IP hostname. |
|
ip-address |
Group IP address. |
|
ip-mask |
(Optional) IP mask for group IP address. |
|
interface |
(Optional) Specifies an interface. |
|
type |
Interface type; possible valid values are ethernet, fastethernet, gigabitethernet, tengigabitethernet, pos, atm, and ge-wan. |
|
number |
Module and port number; see the "Usage Guidelines" section for valid values. |
|
module number |
(Optional) Displays the entries that are downloaded on the specified module; see the "Usage Guidelines" section for valid values. |
|
mdt |
(Optional) Displays hardware-accelerated MDT information. |
|
source hostname |
(Optional) Displays the entries for a specific source address. |
|
source ip-address |
(Optional) Displays the entries for a specific source IP address. |
|
statistics |
(Optional) Displays the statistics from multicast entries. |
|
summary |
(Optional) Displays a summary of statistics from multicast entries. |
Command History
|
Release |
Modification |
|---|---|
|
12.2(14)SX |
Support for this command was introduced on the Supervisor Engine 720. |
|
12.2(17a)SX |
This command is supported on releases prior to Release 12.2(17a)SX only. |
|
12.2(17b)SXA |
On Cisco 7600 series routers that are configured with a Supervisor Engine 720, this command is replaced by the show mls netflow ip command. |
|
12.2(17d)SXB |
Support for this command on the Supervisor Engine 2 was extended to the 12.2 SX release. This command was changed to include the capability [module num] keywords. |
|
12.2(18)SXF |
The output of the show mls ip multicast capability command was changed to include egress information. |
|
12.2(33)SRA |
This command was integrated into Cisco IOS Release 12.2(33)SRA. |
Usage Guidelines
The output of the show mls ip multicast capability command on Cisco 6500 and Cisco 7600 series routers that are configured with a Supervisor Engine 32 does not include egress information.
The pos, atm, and ge-wankeywords are not supported on Cisco 7600 series routers that are configured with a Supervisor Engine 720.
The following syntax is supported on Cisco 6500 and Cisco 7600 series routers that are configured with a Supervisor Engine 2:
show mls ip multicast complete partial group hostname ip-address ip-mask interface interface interface-number source hostname ip-address
show mls ip multicast connected summary
show mls ip multicast statistics group hostname ip-address source hostname ip-address
The number argument designates the module and port number. Valid values for number depend on the specified interface type and the chassis and module that are used. For example, if you specify a Gigabit Ethernet interface and have a 48-port 10/100BASE-T Ethernet module that is installed in a 13-slot chassis, valid values for the module number are from 1 to 13 and valid values for the port number are from 1 to 48. These valid values also apply when entering the module number keyword and argument.
When you view the output, note that a colon (:) is used to separate the fields.
Examples
This example shows how to display general MLS IP-multicast information:
Router# show mls ip multicast
Multicast hardware switched flows:
(*, 224.1.1.1) Incoming interface: Vlan0, Packets switched: 0
Hardware switched outgoing interfaces: Vlan202
RPF-MFD installed
Total hardware switched flows : 1
This example shows how to display a summary of MLS information:
Router# show mls ip multicast summary 1 MMLS entries using 168 bytes of memory Number of partial hardware-switched flows: 0 Number of complete hardware-switched flows: 1 Directly connected subnet entry install is enabled Aggregation of routed oif is enabled Hardware shortcuts for mvpn mroutes supported Egress Mode of replication is enabled Maximum route support is enabled Router#
This example shows how to display MLS information on a specific interface:
Router#
show mls ip multicast interface fastethernet 5/9
DstIP SrcIP Dst i/f:DstMAC Pkts Bytes
-----------------------------------------------------------------------
SrcDstPorts SrcDstEncap Age LastSeen
----------------------------------------
172.20.52.37 0.0.0.0 100: 00d0.5870.a4ff 1 129
Fa5/9,----- ARPA,ARPA 107 06:10:02
172.20.52.36 0.0.0.0 100 : 0050.7312.0cff 50 6403
Fa5/9,----- ARPA,ARPA 107 06:10:04
Number of Entries Found = 2
This example shows how to display information about the multicast-replication capabilities:
Router#
show mls ip multicast capability
Current mode of replication is Ingress
auto replication mode detection is ON
Slot Multicast replication capability
2 Egress
5 Egress
6 Egress
8 Ingress
9 Ingress
show mls ip multicast bidir
To display the Bidir hardware-switched entries, use the show mls ip multicast bidir command in user EXEC or privileged EXEC mode..
Syntax Description
|
group |
(Optional) Displays the entries for a specific multicast-group address. |
|
hostname |
Group IP hostname. |
|
ip-address |
Group IP address. |
|
ip-mask |
(Optional) IP mask for group IP address. |
|
interface |
(Optional) Specifies an interface. |
|
type |
Interface type; possible valid values are ethernet, fastethernet, gigabitethernet, and tengigabitethernet. |
|
number |
Module and port number. |
|
source hostname |
(Optional) Displays the entries for a specific source address. |
|
source ip-address |
(Optional) Displays the entries for a specific source IP address. |
Command History
|
Release |
Modification |
|---|---|
|
12.2(14)SX |
Support for this command was introduced on the Supervisor Engine 720. |
|
12.2(17a)SX |
This command is supported on releases prior to Release 12.2(17a)SXonly. |
|
12.2(17b)SXA |
This command is replaced by the show mls netflow ip command. |
|
12.2(33)SRA |
This command was integrated into Cisco IOS Release 12.2(33)SRA. |
Usage Guidelines
This command is not supported on Cisco 7600 series routers that are configured with a Supervisor Engine 2.
Examples
This example shows how to display the Bidir hardware-switched entries:
Router# show mls ip multicast bidir
Multicast hardware switched flows:
(*, 226.1.4.0) Incoming interface: Vlan51, Packets switched: 0
Hardware switched outgoing interfaces: Vlan51 Vlan30
RPF-MFD installed
(*, 227.1.4.0) Incoming interface: Gi2/1, Packets switched: 0
Hardware switched outgoing interfaces: Gi2/1 Vlan30
RPF-MFD installed
show mls ip multicast rp-mapping
To display the mappings for the PIM-Bidir group to active rendezvous points, use the show mls ip multicast rp-mapping command in user EXEC or privileged EXEC mode.
Command History
|
Release |
Modification |
|---|---|
|
12.2(14)SX |
Support for this command was introduced on the Supervisor Engine 720. |
|
12.2(17a)SX |
This command is supported on releases prior to Release 12.2(17a)SX only. |
|
12.2(17b)SXA |
This command is replaced by the show mls netflow ip command. |
|
12.2(33)SRA |
This command was integrated into Cisco IOS Release 12.2(33)SRA. |
Usage Guidelines
This command is not supported on Cisco 7600 series routers that are configured with a Supervisor Engine 2.
Examples
This example shows how to display the mappings for the PIM group-to-active rendezvous points:
Router# show mls ip multicast rp-mapping
RP Address State DF-count GM-count
10.2.2.2 H 1 1
10.9.9.9 H 1 2
This example shows how to display information that is based on the DF list in the mapping cache of the route processor:
Router# show mls ip multicast rp-mapping df-cache
RP Address State DF State
10.9.9.9 H Vl30 H
This example shows how to display information that is based on the mapping cache of the route processor:
Router# show mls ip multicast rp-mapping gm-cache
State: H - Hardware Switched, I - Install Pending, D - Delete Pending,
Z - Zombie
RP Address State Group Mask State Packet/Byte-count
10.0.0.60 H 172.16.0.0 255.255.0.0 H 100/6400
show mls ip multicast sso
To display information about multicast high-availability SSO, use the show mls ip multicast sso command in user EXEC or privileged EXEC mode .
Usage Guidelines
This command is not supported on Cisco 7600 series routers that are configured with a Supervisor Engine 2.
Examples
This example shows how to display multicast high-availability SSO information:
Router# show mls ip multicast sso
Multicast SSO is enabled
Multicast HA Parameters
---------------------------------------------------+------+
protocol convergence timeout 120 secs
flow leak percent 10
flow leak interval 20 secs
heartquake#
This example shows how to display statistical information about multicast high-availability SSO:
Router# show mls ip multicast sso statistics Multicast HA Statistics: ACTIVE --------------------------------------------------+------+ CHKPT msgs sent 5 CHKPT msgs send failed 0 CHKPT msgs send aborted 0 CHKPT met add msg sent 5 CHKPT met del msg sent 1 CHKPT icroif msg sent 1 MET HA met add enqueued 5 MET HA met del enqueued 1 ICROIF HA add enqueued 1 ICROIF HA del enqueued 0 CHKPT buffer failure 0 MET HA Reconstruction Statistics --------------------------------------------------+------+ Number of met blks reconstructed 0 Number of normal sets reconstructed 0 Number of fixed sets reconstructed 0 Number of sets deleted 0 Number of blks not found 0 normal sets reconstruction failed 0 fixed set reconstruction failed 0 Multicast HA Statistics: STANDBY --------------------------------------------------+------+ CHKPT msgs rcvd 5 CHKPT met add msg rcvd 5 CHKPT met del msg rcvd 1 CHKPT icroif msg rcvd 1 CHKPT msg unknown 0 CHKPT buffer failure 0
show mpls mldp bindings
To display the bindings (the upstream and downstream label assignments) for Multicast Label Distribution Protocol (MLDP) traffic, use the show mpls mldp bindingscommand in user EXEC or privileged EXEC mode.
Syntax Description
|
id id |
(Optional) The Label Switched Multicast (LSM) ID whose MLDP entry is to be displayed. |
|
opaque_type type |
(Optional) The opaque type to be used for filtering. The following types are supported:
|
|
summary |
(Optional) The MLDP database summary. |
Usage Guidelines
This command displays the bindings (the upstream and downstream label assignments) for MLDP traffic. The bindings map Multicast Data Trees (MDTs) to Multicast Label Switch Paths (LSPs). LSPs are used to transmit multicast traffic within an MPLS core network.
Examples
The following is sample output from the show mpls mldp bindingscommand.
Router# show mpls mldp bindings
System ID: D3000001
Type: MP2MP, Root Node: 172.30.20.1, Opaque Len: 14
Opaque value: [mdt 1:1 0]
lsr: 172.30.20.1:0, remote binding[U]: 30, local binding[D]: 30 active
The table below describes the significant fields shown in the display.
| Table 21 | show mpls mldp bindings Field Descriptions |
|
Field |
Description |
|---|---|
|
System ID |
The LSM ID whose MLDP entry is displayed. |
|
Type |
The type of LSP used (can be point-to-multipoint (P2MP) or multipoint-to-multipoint (MP2MP)). |
|
Root Node |
The root of the MDT. |
|
Opaque value |
A value which is used to uniquely identify the MP LSP. |
|
lsr |
The Label Switched Router ID. |
|
remote binding |
The label used remotely to map MDTs to Multicast LSPs. |
|
local binding |
The label used locally to map MDTs to Multicast LSPs. |
show mpls mldp count
To display Multicast Label Distribution Protocol (MLDP) count information, use the show mpls mldp countcommand in user EXEC or privileged EXEC mode.
Usage Guidelines
This command displays the MLDP count information, which is the total number of MLDP entries in the MLDP database. An entry can be a point-to-multipoint (P2MP) Label Switched Path (LSP) or an multipoint-to-multipoint (MP2MP) LSP. These statistics provide a summary on the usage of MLDP. LSPs are used to transmit multicast traffic within an MPLS core network.
show mpls mldp database
To display Multicast Label Distribution Protocol (MLDP) information, use the show mpls mldp databasecommand in user EXEC or privileged EXEC mode.
Syntax Description
|
id id |
(Optional) The Label Switched Multicast (LSM) ID whose MLDP entry is to be displayed. |
|
opaque_type type |
(Optional) The opaque type to be used for filtering. The following types are supported:
|
|
summary |
(Optional) The MLDP database summary. |
Usage Guidelines
This command displays the contents for MLDP entries in the MLDP database. Each MLDP entry provides the configuration details associated with each point-to-multipoint (P2MP) and multipoint-to-multipoint (MP2MP) Label Switched Path (LSP) used to transmit multicast traffic within an MPLS core network.
Examples
The following is sample output from the show mpls mldp databasecommand.
Router# show mpls mldp database opaque_type mdt 100:2
* Indicates MLDP recursive forwarding is enabled
LSM ID : D3000001 (RNR LSM ID: 8A000002) Type: MP2MP Uptime : 00:04:54
FEC Root : 172.30.20.1
Opaque decoded : [mdt 100:2 0]
Opaque length : 11 bytes
Opaque value : 07 000B 0000010000000100000000
RNR active LSP : (this entry)
Upstream client(s) :
172.30.20.1:0 [Active]
Expires : Never Path Set ID : 99000001
Out Label (U) : 32 Interface : Ethernet1/0*
Local Label (D): 30 Next Hop : 10.0.1.7
Replication client(s):
MDT (VRF blue)
Uptime : 00:04:54 Path Set ID : 5000002
Interface : Lspvif0
The table below describes the significant fields shown in the display.
| Table 22 | show mpls mldp database Field Descriptions |
|
Field |
Description |
|---|---|
|
LSM ID |
The LSM ID whose MLDP entry is displayed. |
|
Type |
The type of LSP used. This can P2MP or MP2MP. |
|
FEC Root |
The root of the MDT. |
|
Opaque value |
A value which is used to uniquely identify the MP LSP. |
|
RNR active LSP |
The primary root for upstream forwarding. |
|
Upstream client(s) |
The upstream clients are the upstream nodes of the MP2MP LSP. |
|
Replication client(s) |
The Replication Clients are the downstream nodes of the MP2MP LSP. They receive multipoint replicated traffic. |
show mpls mldp filter
To display infromation about filters for the Cisco Multicast Label Distribution Protocol (MLDP) label-based Multicast Virtual Private Network (MVPN) solution, use the show mpls mldp filter command in user or privileged EXEC mode.
show mpls mldp ha count
To display the number of MDT trees for a Multicast Label Distribution Protocol (MLDP) label-based Multicast Virtual Private Network (MVPN), use the show mpls mldp ha count command in user EXEC or privileged EXEC mode.
This command displays the MLDP HA count information, which is the total number of MLDP entries in the MLDP database. An entry can be a point-to-multipoint (P2MP) Label Switched Path (LSP) or an multipoint-to-multipoint (MP2MP) LSP. These statistics provide a summary on the usage of MLDP. LSPs are used to transmit multicast traffic within an MPLS core network.
show mpls mldp ha database
To display check pointed database information for a Multicast Label Distribution Protocol (MLDP) label-based Multicast Virtual Private Network (MVPN), use the show mpls mldp ha database command in user EXEC or privileged EXEC mode.
Usage Guidelines
Use this command to display information to be used to determine the state of check pointed information on the standby router. This command displays the contents for MLDP entries in the check pointed MLDP database. Each MLDP entry provides the configuration details associated with each point-to-multipoint (P2MP) and multipoint-to-multipoint (MP2MP) Label Switched Path (LSP) used to transmit multicast traffic within an MPLS core network.
Examples
PE2# show mpls mldp ha database
LSM ID : 98000001 (RNR LSM ID: 8F000002) Type: MP2MP
FEC Root : 100.100.100.100
Opaque decoded : [mdt 1:1 0]
Opaque length : 11 bytes
Opaque value : 07 000B 0000010000000100000000
Upstream client(s) :
50.50.50.50:0 Path Set ID : EE000001
Replication client(s):
MDT Path Set ID : EA000002
PE2# show mpls mldp ha database summary LSM ID Type Root Decoded Opaque Value Client Cnt. 98000001 MP2MP 100.100.100.100 [mdt 1:1 0] 1
The table below describes the significant fields shown in the display.
| Table 24 | show mpls mldp ha database Field Descriptions |
|
Field |
Description |
|---|---|
|
LSM ID |
The LSM ID whose MLDP entry is displayed. |
|
Type |
The type of LSP used. This can P2MP or MP2MP. |
|
FEC Root |
The root of the MDT. |
|
Opaque value |
A value which is used to uniquely identify the MP LSP. |
|
Upstream client(s) |
The upstream clients are the upstream nodes of the MP2MP LSP. |
|
Replication client(s) |
The Replication Clients are the downstream nodes of the MP2MP LSP. They receive multipoint replicated traffic. |
show mpls mldp ha neighbors
To display synched peer information for a Multicast Label Distribution Protocol (MLDP) label-based Multicast Virtual Private Network (MVPN), use the show mpls mldp ha neighbors command in user EXEC or privileged EXEC mode.
Usage Guidelines
This command displays the MLDP HA peers (neighbors) known to the router. Use this command to display information to be used to determine the state of check pointed information on the standby router.
Examples
PE2# show mpls mldp ha neighbors
MLDP peer ID : 50.50.50.50:0,
Path count : 1
Path(s) : 10.0.4.5 Ethernet1/0
Nhop count : 1
Nhop list : 10.0.4.5
The table below describes the significant fields shown in the display.
| Table 25 | show mpls mldp ha neighbor Field Descriptions |
|
Field |
Description |
|---|---|
|
MLDP peer ID |
The MLDP identifier of the neighbor (peer). |
|
Path count |
The number of LSPs. |
|
Path(s) |
A value which is used to uniquely identify the MP LSP. |
|
Nhop count |
The number of configured next hops. |
|
Nhop list |
The addresses of the next hops. |
show mpls mldp ha root
To display synched root information for a Multicast Label Distribution Protocol (MLDP) label-based Multicast Virtual Private Network (MVPN), use the show mpls mldp ha root command in user EXEC or privileged EXEC mode.
Usage Guidelines
This command displays synched Multicast Label Distribution Protocol (MLDP) root information. The root is the common entry between multiple Label Switch Paths (LSPs). LSPs are used to transmit multicast traffic within an MPLS core network.
show mpls mldp interface
To display a list of interfaces for a device along with information about whether Cisco Multicast Label Distribution Protocol (MLDP) is enabled or disabled on each interface, use the show mpls mldp interface command in user EXEC or privileged EXEC mode.
show mpls mldp label release
To display Multicast Label Distribution Protocol (MLDP) labels that have been withdrawn and awaiting release, use the show mpls mldp label releasecommand in user EXEC or privileged EXEC mode.
Usage Guidelines
This command displays the MLDP labels that have been withdrawn and awaiting release. These are the labels that are no longer being used by point-to-multipoint (P2MP) Label Switched Paths (LSPs) or multipoint-to-multipoint (MP2MP) LSPs. LSPs are used to transmit multicast traffic within an MPLS core network.
show mpls mldp neighbors
To display Multicast Label Distribution Protocol (MLDP) neighbor information, use the show mpls mldp neighborscommand in user EXEC or privileged EXEC mode.
Usage Guidelines
This command displays the MLDP peers (neighbors) known to the router. It also displays the associated Label Switched Path (LSP). LSPs are used to transmit multicast traffic within an MPLS core network.
Examples
The following is sample output from the show mpls mldp neighborscommand:
Router# show mpls mldp neighbors
MLDP peer ID : 172.30.20.2:0, uptime 00:05:10 Up,
Target Adj : No
Session hndl : 1
Upstream count : 0
Branch count : 0
Path count : 1
Path(s) : 10.0.1.4 LDP Ethernet1/0
Nhop count : 0
Filter list : 2 1
MLDP peer ID : 172.30.20.2:0, uptime 00:05:09 Up,
Target Adj : No
Session hndl : 2
Upstream count : 1
Branch count : 0
Path count : 1
Path(s) : 10.0.1.7 LDP Ethernet1/0
Nhop count : 1
Nhop list : 10.0.1.7
Filter list : 2 1
The table below describes the significant fields shown in the display.
| Table 27 | show mpls mldp neighbors Field Descriptions |
|
Field |
Description |
|---|---|
|
MLDP peer ID |
The MLDP identifier of the neighbor (peer). |
|
Upstream count |
The number of nodes upstream of the LSP. |
|
Path count |
The number of LSPs. |
|
Path(s) |
A value which is used to uniquely identify the MP LSP. |
|
Nhop count |
The number of configured next hops. |
|
Nhop list |
The addresses of the next hops. |
|
Filter list |
Filter by which a peer list was filtered. |
show mpls mldp root
To display Multicast Label Distribution Protocol (MLDP) root information, use the show mpls mldp rootcommand in user EXEC or privileged EXEC mode.
Usage Guidelines
This command displays Multicast Label Distribution Protocol (MLDP) root information. The root is the common entry between multiple Label Switch Paths (LSPs). LSPs are used to transmit multicast traffic within an MPLS core network.
Examples
The following is sample output from the show mpls mldp label rootcommand:
Router# show mpls mldp label root 10.0.0.1
Root node : 172.30.20.1
Metric : 20
Distance : 115
Interface : Ethernet1/0 (via unicast RT)
FEC count : 1
Path count : 1
Path(s) : 10.0.1.7 LDP nbr: 100.100.100.100:0 Ethernet1/0
The table below describes the significant fields shown in the display.
show platform software multicast ip bidir
Todisplay bidirectional (Bidir) information, use the show platform software multicast ip bidircommand in privileged EXEC mode.
Syntax Description
|
group |
Displays entries for a specific multicast group address. |
|
group-name |
Hostname or group IP address. |
|
interface |
Displays entries for a specific interface. |
|
gigabitethernet 1-6 |
Specifies the GigabitEthernet interface number. The range is 1 through 6. |
|
port-channel 1-256 |
Specifies the port-channel interface number. The range is 1 through 256. |
|
tengigabitethernet 1-6 |
Specifies the TenGigabitEthernet interface number. The range is 1 through 6. |
|
vlan 1-4094 |
Specifies the VLAN interface number. The range is 1 through 4094. |
|
source |
Displays entries for a specific source. |
|
A.B.C.D. |
Specifies source IP address. |
Examples
This example shows how to display bidirectional (Bidir) information:
Router# show platform software multicast ip bidir Multicast hardware switched flows: Total hardware switched flows: 0
This example shows how to display bidirectional (Bidir) information for a specific multicast group address:
Router# show platform software multicast ip bidir group 232.0.1.4 Multicast hardware switched flows: Total hardware switched flows: 0 Router#
This example shows how to display bidirectional (Bidir) information for a specific interface:
Router# show platform software multicast ip bidir interface tengigabitethernet 4/2 Multicast hardware switched flows: Total hardware switched flows: 0 Router#
This example shows how to display bidirectional (Bidir) information for a specific source:
Router# show platform software multicast ip bidir source 40.0.0.2 Multicast hardware switched flows: Total hardware switched flows: 0 Router#
Related Commands
|
Command |
Description |
|---|---|
|
show platform software multicast ip bidir |
Displays bidirectional (Bidir) information. |
|
show platform software multicast ip capability |
Displays multicast replication capability. |
|
show platform software multicast ip complete |
Displays complete hardware switched entries. |
|
show platform software multicast ip connected |
Displays installed interface and mask entries. |
|
show platform software multicast ip group |
Displays entries for a specific multicast group address. |
|
show platform software multicast ip interface |
Displays entries for a specific interface. |
|
show platform software multicast ip partial |
Displays partially hardware switched entries for a specific interface. |
|
show platform software multicast ip source |
Displays partially hardware switched entries for a specific source. |
|
show platform software multicast ip statistics |
Displays partially hardware switched entries for a specific source. |
|
show platform software multicast ip summary |
Displays a summary of installed-hardware shortcuts. |
|
show platform software multicast ip vrf |
Displays entries for a specific VRF. |
show platform software multicast ip capability
To display multicast replication capability, use the show platform software multicast ip capabilitycommand in privileged EXEC mode.
Examples
This example shows how to display multicast replication capability:
Router# show platform software multicast ip capability Current System HW Replication Mode : Egress Auto-detection of Replication Mode : ON Slot Replication-Capability Replication-Mode 2 Egress Egress 3 Egress Egress 4 Egress Egress 6 Egress Egress Router#
Related Commands
|
Command |
Description |
|---|---|
|
show platform software multicast ip bidir |
Displays bidirectional (Bidir) information. |
|
show platform software multicast ip capability |
Displays multicast replication capability. |
|
show platform software multicast ip complete |
Displays complete hardware switched entries. |
|
show platform software multicast ip connected |
Displays installed interface and mask entries. |
|
show platform software multicast ip group |
Displays entries for a specific multicast group address. |
|
show platform software multicast ip interface |
Displays entries for a specific interface. |
|
show platform software multicast ip partial |
Displays partially hardware switched entries for a specific interface. |
|
show platform software multicast ip source |
Displays partially hardware switched entries for a specific source. |
|
show platform software multicast ip statistics |
Displays partially hardware switched entries for a specific source. |
|
show platform software multicast ip summary |
Displays a summary of installed-hardware shortcuts. |
|
show platform software multicast ip vrf |
Displays entries for a specific VRF. |
show platform software multicast ip complete
To display complete hardware switched entries, use the show platform software multicast ip completecommand in privileged EXEC mode.
Syntax Description
|
group |
Displays entries for a specific multicast group address. |
|
A.B.C.D |
Specifies the group IP address. |
|
interface |
Displays entries for a specific interface. |
|
gigabitethernet 1-6 |
Specifies the GigabitEthernet interface number. The range is 1 through 6. |
|
port-channel 1-256 |
Specifies the port-channel interface number. The range is 1 through 256. |
|
tengigabitethernet 1-6 |
Specifies the TenGigabitEthernet interface number. The range is 1 through 6. |
|
vlan 1-4094 |
Specifies the VLAN interface number. The range is 1 through 4094. |
|
source |
Displays entries for a specific source. |
|
A.B.C.D. |
Specifies source IP address. |
Examples
This example shows how to display complete hardware switched entries:
Router# show platform software multicast ip complete
Multicast hardware switched flows:
(40.0.0.2, 232.0.1.4) Incoming interface: GigabitEthernet3/2/1, Packets Switched: 6610137
Hardware switched outgoing interfaces:
Tunnel10
Total hardware switched flows: 1
Router
This example shows how to display entries for a specific multicast group address:
Router# show platform software multicast ip complete group 232.0.1.4
Multicast hardware switched flows:
(40.0.0.2, 232.0.1.4) Incoming interface: GigabitEthernet3/2/1, Packets Switched: 6799184
Hardware switched outgoing interfaces:
Tunnel10
Total hardware switched flows: 1
Router#
This example shows how to display complete hardware switched entries for a specific inteface:
Router# show platform software multicast ip complete interface gigabitethernet 3/2/1
Multicast hardware switched flows:
(40.0.0.2, 232.0.1.4) Incoming interface: GigabitEthernet3/2/1, Packets Switched: 7008473
Hardware switched outgoing interfaces:
Tunnel10
Total hardware switched flows: 1
Router#
This example shows how to display complete hardware switched entries for a specific group:
Router# show platform software multicast ip complete group 232.0.1.4
Multicast hardware switched flows:
(40.0.0.2, 232.0.1.4) Incoming interface: GigabitEthernet3/2/1, Packets Switched: 7163170
Hardware switched outgoing interfaces:
Tunnel10
Total hardware switched flows: 1
PE1-7600#
Related Commands
|
Command |
Description |
|---|---|
|
show platform software multicast ip bidir |
Displays bidirectional (Bidir) information. |
|
show platform software multicast ip capability |
Displays multicast replication capability. |
|
show platform software multicast ip complete |
Displays complete hardware switched entries. |
|
show platform software multicast ip connected |
Displays installed interface and mask entries. |
|
show platform software multicast ip group |
Displays entries for a specific multicast group address. |
|
show platform software multicast ip interface |
Displays entries for a specific interface. |
|
show platform software multicast ip partial |
Displays partially hardware switched entries for a specific interface. |
|
show platform software multicast ip source |
Displays partially hardware switched entries for a specific source. |
|
show platform software multicast ip statistics |
Displays partially hardware switched entries for a specific source. |
|
show platform software multicast ip summary |
Displays a summary of installed-hardware shortcuts. |
|
show platform software multicast ip vrf |
Displays entries for a specific VRF. |
show platform software multicast ip connected
To display installed interface and mask entries, use the show platform software multicast ip connectedcommand in privileged EXEC mode.
Examples
This example shows how to display installed interface and mask entries:
Router# show platform software multicast ip connected
Multicast CEF Entries for VPN#0
Flags: R - Control, S - Subnet, B - Bidir, C - Complete, P - Partial, E - Encapsulation, D - Decapsulation, M - MAC rewrite, T - Forwarding
c - Central Rewrite, p - Primary Input, r - Recirculation, h - Entry sitting on Encap/Decap VRF layer
Source/mask Destination/mask RPF/DF Flags #packets #bytes rwindex Output Vlans/Info
+-------------------+-------------------+-------+------+-------------+------------------+--------+------------------------------+
Found 0 entries. 0 are mfd entries
PE1-7600
Related Commands
|
Command |
Description |
|---|---|
|
show platform software multicast ip bidir |
Displays bidirectional (Bidir) information. |
|
show platform software multicast ip capability |
Displays multicast replication capability. |
|
show platform software multicast ip complete |
Displays complete hardware switched entries. |
|
show platform software multicast ip connected |
Displays installed interface and mask entries. |
|
show platform software multicast ip group |
Displays entries for a specific multicast group address. |
|
show platform software multicast ip interface |
Displays entries for a specific interface. |
|
show platform software multicast ip partial |
Displays partially hardware switched entries for a specific interface. |
|
show platform software multicast ip source |
Displays partially hardware switched entries for a specific source. |
|
show platform software multicast ip statistics |
Displays partially hardware switched entries for a specific source. |
|
show platform software multicast ip summary |
Displays a summary of installed-hardware shortcuts. |
|
show platform software multicast ip vrf |
Displays entries for a specific VRF. |
show platform software multicast ip interface
To display entries for a specific interface, use the show platform software multicast ip interfacecommand in privileged EXEC mode.
Syntax Description
|
gigabitethernet 1-6 |
Specifies the GigabitEthernet interface number. The range is 1 through 6. |
|
port-channel 1-256 |
Specifies the port-channel interface number. The range is 1 through 256. |
|
tengigabitethernet 1-6 |
Specifies the TenGigabitEthernet interface number. The range is 1 through 6. |
|
vlan 1-4094 |
Specifies the VLAN interface number. The range is 1 through 4094. |
Examples
This example shows how to display entries for a gigabitethernet interface:
Router# show platform software multicast ip interface gigabitethernet 3/2/1
Multicast hardware switched flows:
(40.0.0.2, 232.0.1.4) Incoming interface: GigabitEthernet3/2/1, Packets Switched: 8206582
Hardware switched outgoing interfaces:
Tunnel10
Total hardware switched flows: 1
PE1-7600#
Related Commands
|
Command |
Description |
|---|---|
|
show platform software multicast ip bidir |
Displays bidirectional (Bidir) information. |
|
show platform software multicast ip capability |
Displays multicast replication capability. |
|
show platform software multicast ip complete |
Displays complete hardware switched entries. |
|
show platform software multicast ip connected |
Displays installed interface and mask entries. |
|
show platform software multicast ip group |
Displays entries for a specific multicast group address. |
|
show platform software multicast ip interface |
Displays entries for a specific interface. |
|
show platform software multicast ip partial |
Displays partially hardware switched entries for a specific interface. |
|
show platform software multicast ip source |
Displays partially hardware switched entries for a specific source. |
|
show platform software multicast ip statistics |
Displays partially hardware switched entries for a specific source. |
|
show platform software multicast ip summary |
Displays a summary of installed-hardware shortcuts. |
|
show platform software multicast ip vrf |
Displays entries for a specific VRF. |
show platform software multicast ip partial
To display partially hardware switched entries, use the show platform software multicast ip partialcommand in privileged EXEC mode.
Syntax Description
|
group |
Displays entries for a specific multicast group address. |
|
group-name |
Hostname or group IP address. |
|
interface |
Displays entries for a specific interface. |
|
gigabitethernet 1-6 |
Specifies the GigabitEthernet interface number. The range is 1 through 6. |
|
port-channel 1-256 |
Specifies the port-channel interface number. The range is 1 through 256. |
|
tengigabitethernet 1-6 |
Specifies the TenGigabitEthernet interface number. The range is 1 through 6. |
|
vlan 1-4094 |
Specifies the VLAN interface number. The range is 1 through 4094. |
|
source |
Displays entries for a specific source. |
|
A.B.C.D. |
Specifies source IP address. |
Examples
This example shows how to display partially hardware switched entries for a specific group:
Router# show platform software multicast ip partial group 232.0.1.4 Multicast hardware switched flows: Total hardware switched flows: 0 PE1-7600#
This example shows how to display partially hardware switched entries for a specific interface:
Router# show platform multicast ip partial interface gigabitethernet 3/2/1 Multicast hardware switched flows: Total hardware switched flows: 0 PE1-7600
Related Commands
|
Command |
Description |
|---|---|
|
show platform software multicast ip bidir |
Displays bidirectional (Bidir) information. |
|
show platform software multicast ip capability |
Displays multicast replication capability. |
|
show platform software multicast ip complete |
Displays complete hardware switched entries. |
|
show platform software multicast ip connected |
Displays installed interface and mask entries. |
|
show platform software multicast ip group |
Displays entries for a specific multicast group address. |
|
show platform software multicast ip interface |
Displays entries for a specific interface. |
|
show platform software multicast ip partial |
Displays partially hardware switched entries for a specific interface. |
|
show platform software multicast ip source |
Displays partially hardware switched entries for a specific source. |
|
show platform software multicast ip statistics |
Displays partially hardware switched entries for a specific source. |
|
show platform software multicast ip summary |
Displays a summary of installed-hardware shortcuts. |
|
show platform software multicast ip vrf |
Displays entries for a specific VRF. |
show platform software multicast ip source
To display partially hardware switched entries for a specific source, use the show platform software multicast ip sourcecommand in privileged EXEC mode.
Examples
This example shows how to display partially hardware switched entries for a specific source:
PE1-7600# show platform software multicast ip source 40.0.0.2
Multicast hardware switched flows:
(40.0.0.2, 232.0.1.4) Incoming interface: GigabitEthernet3/2/1, Packets Switched: 8778143
Hardware switched outgoing interfaces:
Tunnel10
Total hardware switched flows: 1
PE1-7600#
Related Commands
|
Command |
Description |
|---|---|
|
show platform software multicast ip bidir |
Displays bidirectional (Bidir) information. |
|
show platform software multicast ip capability |
Displays multicast replication capability. |
|
show platform software multicast ip complete |
Displays complete hardware switched entries. |
|
show platform software multicast ip connected |
Displays installed interface and mask entries. |
|
show platform software multicast ip group |
Displays entries for a specific multicast group address. |
|
show platform software multicast ip interface |
Displays entries for a specific interface. |
|
show platform software multicast ip partial |
Displays partially hardware switched entries for a specific interface. |
|
show platform software multicast ip source |
Displays partially hardware switched entries for a specific source. |
|
show platform software multicast ip statistics |
Displays partially hardware switched entries for a specific source. |
|
show platform software multicast ip summary |
Displays a summary of installed-hardware shortcuts. |
|
show platform software multicast ip vrf |
Displays entries for a specific VRF. |
show platform software multicast ip statistics
To display partially hardware switched entries for a specific source, use the show platform software multicast ip statisticscommand in privileged EXEC mode.
Examples
This example shows how to display partially hardware switched entries for a specific source:
Router# show platform software multicast ip statistics group 232.0.1.4 Warning: No stats to be printed
Related Commands
|
Command |
Description |
|---|---|
|
show platform software multicast ip bidir |
Displays bidirectional (Bidir) information. |
|
show platform software multicast ip capability |
Displays multicast replication capability. |
|
show platform software multicast ip complete |
Displays complete hardware switched entries. |
|
show platform software multicast ip connected |
Displays installed interface and mask entries. |
|
show platform software multicast ip group |
Displays entries for a specific multicast group address. |
|
show platform software multicast ip interface |
Displays entries for a specific interface. |
|
show platform software multicast ip partial |
Displays partially hardware switched entries for a specific interface. |
|
show platform software multicast ip source |
Displays partially hardware switched entries for a specific source. |
|
show platform software multicast ip statistics |
Displays partially hardware switched entries for a specific source. |
|
show platform software multicast ip summary |
Displays a summary of installed-hardware shortcuts. |
|
show platform software multicast ip vrf |
Displays entries for a specific VRF. |
show platform software multicast ip summary
To display a summary of installed-hardware shortcuts, use the show platform software multicast ip summarycommand in privileged EXEC mode.
Examples
This example shows how to display a summary of installed-hardware shortcuts:
Router# show platform software multicast ip summary IPv6 Multicast Netflow SC summary on Slot[7]: Shortcut Type Shortcut count ---------------------------+-------------- (S, G) 0 IPv6 Multicast FIB SC summary on Slot[7]: Shortcut Type Shortcut count ---------------------------+-------------- (*, G/128) 0 (*, G/m) 0
Related Commands
|
Command |
Description |
|---|---|
|
show platform software multicast ip bidir |
Displays bidirectional (Bidir) information. |
|
show platform software multicast ip capability |
Displays multicast replication capability. |
|
show platform software multicast ip complete |
Displays complete hardware switched entries. |
|
show platform software multicast ip connected |
Displays installed interface and mask entries. |
|
show platform software multicast ip group |
Displays entries for a specific multicast group address. |
|
show platform software multicast ip interface |
Displays entries for a specific interface. |
|
show platform software multicast ip partial |
Displays partially hardware switched entries for a specific interface. |
|
show platform software multicast ip source |
Displays partially hardware switched entries for a specific source. |
|
show platform software multicast ip statistics |
Displays partially hardware switched entries for a specific source. |
|
show platform software multicast ip summary |
Displays a summary of installed-hardware shortcuts. |
|
show platform software multicast ip vrf |
Displays entries for a specific VRF. |
show platform software multicast ip vrf
To display entries for a specific VRF, use the show platform software multicast ip vrfcommand in privileged EXEC mode.
Examples
This example shows how to display entries for a specific VRF:
Router# show platform software multicast ip vrf vrfp-id SIP-600-3#sh platform software multicast ip cmfib vrf red 232.5.5.5 verbose Multicast CEF Entries for VPN#3 (10.0.0.1, 232.5.5.5) IOSVPN:258 (1) PI:1 (1) CR:0 (1) Recirc:0 (1) Vlan:1037 AdjPtr:131076 FibRpfNf:1 FibRpfDf:1 FibAddr:0x30056 rwvlans:1037 rwindex:0x7FFA adjmac:0008.e287.65c0 rdt:1 E:0 CAP1:0 fmt:Mcast l3rwvld:1 DM:0 mtu:1518 rwtype:L2&L3 met2:0xD met3:0x7 packets:0000001266681 bytes:000000000506672400 Starting Offset: 0x000D V E L0 C:1019 I:0x0200F ----------->index of egress multicast vlan of vrf Starting Offset: 0x0007 V E C:1041 MLSVPN:264 (1) PI:1 (1) CR:1 (1) Recirc:1 (1) Vlan:1037 AdjPtr:131078 FibRpfNf:1 FibRpfDf:1 FibAddr:0x3005A rwvlans:1037 rwindex:0x7FFF adjmac:0000.0000.0000 rdt:1 E:0 CAP1:0 fmt:Mcast l3rwvld:0 DM:0 mtu:1522 rwtype:- met2:0x0 met3:0x0 packets:0000000000000 bytes:000000000000000000 IOSVPN:258 (1) PI:0 (1) CR:1 (1) Recirc:0 (1) Vlan:1019 AdjPtr:131077 FibRpfNf:0 FibRpfDf:1 FibAddr:0x30058 rwvlans:1019 rwindex:0x7FFA adjmac:0008.e287.65c0 rdt:1 E:0 CAP1:0 fmt:Mcast l3rwvld:1 DM:0 mtu:1518 rwtype:L3 met2:0x0 met3:0x7 packets:0000000000000 bytes:000000000000000000 Starting Offset: 0x0007 V E C:1041 Annotation-data: [0x4E2B1B80] A-vlan: 1037 NS-vlan: 0 RP-rpf-vlan: 0 Anntn flags: [0x100010] H MT MTU: 1500 Retry-count: 65534 Sec-entries count: 2 Met-handle: 0x46C8E080 New-Met-handle: 0x0 Met2-handle: 0x56141BAC HAL L3-data : [0x56141E28] Flags: 0x4 FIB-index: 0x86C ADJ-index: 0x20004 NF-addr: 0x0 ML3 entry type: 0x0 [(S,G) shortcut] Flags: 0xA1000000 Vpn: 258 Rpf: 1037 Rw_index: 0x7FFA Adj_mtu: 1514 Met2: 0xD Met3: 0x7 V6-data: NULL ---Secondary entry [1]--- HAL L3-data : [0x56141EE4] Flags: 0x4 FIB-index: 0x86E ADJ-index: 0x20006 NF-addr: 0x0 ML3 entry type: 0x0 [(S,G) shortcut] Flags: 0xB9400000 Vpn: 264 Rpf: 1037 Rw_index: 0x7FFF Adj_mtu: 1514 Met2: 0x0 Met3: 0x0 V6-data: NULL ---Secondary entry [2]--- HAL L3-data : [0x46C8E37C] Flags: 0x4 FIB-index: 0x86D ADJ-index: 0x20005 NF-addr: 0x0 ML3 entry type: 0x0 [(S,G) shortcut] Flags: 0x90000000 Vpn: 258 Rpf: 1019 Rw_index: 0x7FFA Adj_mtu: 1514 Met2: 0x0 Met3: 0x7 V6-data: NULL ---TE entries---
Related Commands
|
Command |
Description |
|---|---|
|
show platform software multicast ip bidir |
Displays bidirectional (Bidir) information. |
|
show platform software multicast ip capability |
Displays multicast replication capability. |
|
show platform software multicast ip complete |
Displays complete hardware switched entries. |
|
show platform software multicast ip connected |
Displays installed interface and mask entries. |
|
show platform software multicast ip group |
Displays entries for a specific multicast group address. |
|
show platform software multicast ip interface |
Displays entries for a specific interface. |
|
show platform software multicast ip partial |
Displays partially hardware switched entries for a specific interface. |
|
show platform software multicast ip source |
Displays partially hardware switched entries for a specific source. |
|
show platform software multicast ip statistics |
Displays partially hardware switched entries for a specific source. |
|
show platform software multicast ip summary |
Displays a summary of installed-hardware shortcuts. |
|
ipv6 mfib hardware-switching |
Configures hardware switching for IPv6 multicast packets on a global basis. |
show router-guard
To display router guard status and configuration information, use the show router-guard command in privileged EXEC mode.
Usage Guidelines
If the port is in the shutdown state, the system cannot determine if the port is in trunk mode or access mode, and you will not be able to display the status by entering the show router-guard command. In this case, you can enter the show running-config interface command to display the configuration.
Examples
Note | This section does not contain output description tables as the output fields are self-explanatory. |
The following example shows how to display global router guard configuration information:
Router# show router-guard
Router Guard for IP Multicast:
Globally enabled for all switch ports
The following example shows how to display a list of all interfaces for which router guard is enabled:
Router# show router-guard interface
Router Guard for IP Multicast:
Globally enabled for all switchports
Interfaces:
Gi1/3/46: Disabled on this port for VLANS: ALL
The following example shows how to display router guard configuration and statistics for a specified interface:
Router# show router-guard interface gigabitethernet 1/3/48
Router Guard for IP Multicast:
Globally enabled for all switch ports
Enabled on this interface
Packets denied:
IGMP Queries: x
PIMv2 Messages: x
PIMv1 Messages: x
DVMRP Messages: x
RGMP Messages: x
CGMP Messages: x
Related Commands
|
Command |
Description |
|---|---|
|
clear router-guard ip multicast statistics |
Clears the router guard statistical information. |
|
router-guard ip multicast |
Enables or disables the router guard for switch ports that are connected to multicast routers. |
|
router-guard ip multicast switchports |
Enables or disables the router guard on all switch ports. |
|
show running-config interface |
snmp-server enable traps mvpn
To enable Multicast Virtual Private Network (MVPN) routing and forwarding (MVRF) trap notifications, use the snmp-server enable traps mvpn command in global configuration mode. To disable MVRF trap notifications, use the no form of this command.
Usage Guidelines
SNMP notifications can be sent as traps or informs. This command enables trap notification requests only.
This command controls (enables or disables) MVRF (ciscoMvpnMvrfChange) trap notifications. A ciscoMvpnMvrfChange trap notification signifies a change about a MVRF in the device. The change event can be the creation of an MVRF, the deletion of an MVRF, or an update on the default or data multicast distribution tree (MDT) configuration of an MVRF. The change event is indicated by the ciscoMvpnGenOperStatusChange object embedded in the trap notification.
MVRF trap notifications are defined by the ciscoMvpnMvrfChange object in the MVPN MIB. When this object is queried from a network management system (NMS) workstation, one of the following values is appended to the object to indicate the configuration state of MVRF trap notifications:
- true(1)--MVRF trap notifications are enabled.
- false(2)--MVRF trap notifications are disabled.
The following MVPN MIB tables can be queried to gather details about MVRF change events:
- ciscoMvpnGenericTable
- ciscoMvpnMdtDefaultTable
- ciscoMvpnMdtDataTable
Note | For a complete description of the ciscoMvpnMvrfChange trap notification and MVPN MIB tables, see the CISCO_MVPN_MIB.my file, available on Cisco.com at http://www.cisco.com/go/mibs . |
The snmp-server enable traps mvpn command is used in conjunction with the snmp-server host command. Use the snmp-server host command to specify which host or hosts receive SNMP notifications. To send SNMP notifications, you must configure at least one snmp-server host command.
snmp-server enable traps pim
To enable Protocol Independent Multicast (PIM) Simple Network Management Protocol (SNMP) notifications, use the snmp-server enable traps pimcommand in global configuration mode. To disable PIM-specific SNMP notifications, use the noform of this command.
Syntax Description
|
neighbor-change |
(Optional) Enables notifications indicating when a router's PIM interface is disabled or enabled, or when a router's PIM neighbor adjacency expires. |
|
rp-mapping-change |
(Optional) Enables notifications indicating a change in the rendezvous point (RP) mapping information due to either Auto-RP or bootstrap router (BSR) messages. |
|
invalid-pim-message |
(Optional) Enables invalid PIM message traps. For example, an invalid PIM message could result when a router receives a join or prune message for which the RP specified in the packet is not the RP for the multicast group. |
Command History
|
Release |
Modification |
|---|---|
|
12.2(4)T |
This command was introduced. |
|
12.2(14)S |
This command was integrated into Cisco IOS Release 12.2(14)S. |
|
12.2(33)SRA |
This command was integrated into Cisco IOS Release 12.2(33)SRA. |
|
12.2SX |
This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware. |
Usage Guidelines
SNMP notifications can be sent as traps or inform requests. This command enables both traps and inform requests for the specified notification types. PIM notifications are defined in the CISCO-PIM-MIB.my and PIM-MIB.my files, available from Cisco.com at http://www.cisco.com/public/sw-center/netmgmt/cmtk/mibs.shtml .
Examples
The following example shows how to configure a router to generate notifications indicating that a PIM interface on the router has been enabled:
! Configure PIM traps to be sent as SNMPv2c traps to host with IP address 10.0.0.1. Router(config)# snmp-server host 10.0.0.1 traps version 2c public pim ! Configure router to send the neighbor-change class of notifications to host. Router(config)# snmp-server enable traps pim neighbor-change ! Enable PIM sparse-dense mode on Ethernet interface 0/0. Router(config)# interface ethernet0/0 Router(config-if)# ip pim sparse-dense-mode
tunnel udlr address-resolution
To enable the forwarding of the Address Resolution Protocol (ARP) and Next Hop Resolution Protocol (NHRP) over a unidirectional link (UDL), use the tunnel udlr address-resolution command in interface configuration mode. To disable forwarding, use the no form of this command.
Usage Guidelines
This command is configured on the send-only tunnel interface of a downstream router.
Examples
The following example shows how to configure the tunnel udlr address-resolution command on an interface to enable ARP and NHRP over a send-only tunnel. An ARP address resolution request received from the upstream router on the UDL (Ethernet interface 0) will be replied to over the send-only tunnel of the receiver. Likewise, an ARP request may be sent by the downstream router over the send-only tunnel, and the response will be received over the UDL.
interface tunnel 0 tunnel udlr send-only ethernet 0 tunnel udlr address-resolution
tunnel udlr receive-only
To configure a unidirectional, generic routing encapsulation (GRE) tunnel to act as a back channel that can receive messages, when another interface is configured for unidirectional link routing (UDLR) to send messages, use the tunnel udlr receive-onlycommand in interface configuration mode. To remove the tunnel, use the no form of this command.
Syntax Description
|
interface-type interface-number |
Interface type and number. The interface-type and interface-number arguments must match the unidirectional send-only interface type and number specified by the interface command. Thus, when packets are received over the tunnel, the upper layer protocols will treat the packets as if they are received over the unidirectional send-only interface. |
Usage Guidelines
Use this command to configure a router that has a unidirectional interface with send-only capabilities. One example of when you might configure this command is if you have traffic traveling via a satellite.
The interface-type and interface-number arguments must match the send-only interface type and number specified by the interface command.
You must configure the tunnel udlr send-only command at the opposite end of the tunnel.
If you have a large number of receivers, you should configure UDLR by an alternative means: Internet Group Management Protocol (IGMP) UDLR. See the description of the ip igmp unidirectional-link command.
Examples
In the following example, Router A (the upstream router) is configured with Open Shortest Path First (OSPF) and Protocol Independent Multicast (PIM). Serial interface 0 has send-only capability. Therefore, the UDLR tunnel is configured as receive-only, and points to serial interface 0.
Router A Configuration
ip multicast-routing ! ! Serial0 has send-only capability ! interface serial 0 encapsulation hdlc ip address 10.1.0.1 255.255.0.0 ip pim sparse-dense-mode ! ! Configure tunnel as receive-only UDLR tunnel. ! interface tunnel 0 tunnel source ethernet 0 tunnel destination <downstream-router> tunnel udlr receive-only serial 0 ! ! Configure OSPF. ! router ospf <pid> network 10.0.0.0 0.255.255.255 area 0
Router B (the downstream router) is configured with OSPF and PIM. Serial interface 1 has receive-only capability. Therefore, the UDLR tunnel is configured as send-only, and points to serial interface 1.
Router B Configuration
ip multicast-routing
!
! Serial1 has receive-only capability
!
interface serial 1
encapsulation hdlc
ip address 10.1.0.2 255.255.0.0
ip pim sparse-dense-mode
!
! Configure tunnel as send-only UDLR tunnel.
!
interface tunnel 0
tunnel source ethernet 0
tunnel destination <upstream-router>
tunnel udlr send-only serial 1
!
! Configure OSPF.
!
router ospf <pid>
network 10.0.0.0 0.255.255.255 area 0
Related Commands
|
Command |
Description |
|---|---|
|
interface |
Defines the IP addresses of the server, configures an interface type, and enters interface configuration mode. |
|
interface tunnel |
Configures a tunnel interface. |
|
ip igmp unidirectional-link |
Configures an interface to be unidirectional and enables it for IGMP UDLR. |
|
tunnel udlr send-only |
Configures a unidirectional, GRE tunnel to act as a back channel that can send messages, when another interface is configured for UDLR to receive messages. |
tunnel udlr send-only
To configure a unidirectional, generic routing encapsulation (GRE) tunnel to act as a back channel that can send messages, when another interface is configured for unidirectional link routing (UDLR) to receive messages, use the tunnel udlr send-onlycommand in interface configuration mode. To remove the tunnel, use the no form of this command.
Syntax Description
|
interface-type interface-number |
Interface type and number. The interface-type and interface-number arguments must match the unidirectional receive-only interface type and number specified by the interface command. Thus, when packets are sent by upper layer protocols over the interface, they will be redirected and sent over this GRE tunnel. |
Usage Guidelines
Use this command to configure a router that has a unidirectional interface with receive-only capabilities. The UDLR tunnel will act as a back channel. One example of when you might configure this command is if you have traffic traveling via a satellite.
The interface-type and interface-number arguments must match the receive-only interface type and number specified by the interface command.
You must configure the tunnel udlr receive-only command at the opposite end of the tunnel.
Examples
In the following example, Router A (the upstream router) is configured with Open Shortest Path First (OSPF) and Protocol Independent Multicast (PIM). Serial interface 0 has send-only capability. Therefore, the UDLR tunnel is configured as receive-only, and points to serial interface 0.
Router A Configuration
ip multicast-routing ! ! Serial0 has send-only capability ! interface serial 0 encapsulation hdlc ip address 10.1.0.1 255.255.0.0 ip pim sparse-dense-mode ! ! Configure tunnel as receive-only UDLR tunnel. ! interface tunnel 0 tunnel source ethernet 0 tunnel destination <downstream-router> tunnel udlr receive-only serial 0
Router B (the downstream router) is configured with OSPF and PIM. Serial interface 1 has receive-only capability. Therefore, the UDLR tunnel is configured as send-only, and points to serial interface 1.
Router B Configuration
ip multicast-routing
!
! Serial1 has receive-only capability
!
interface serial 1
encapsulation hdlc
ip address 10.1.0.2 255.255.0.0
ip pim sparse-dense-mode
!
! Configure tunnel as send-only UDLR tunnel.
!
interface tunnel 0
tunnel source ethernet 0
tunnel destination <upstream-router>
tunnel udlr send-only serial 1
Related Commands
|
Command |
Description |
|---|---|
|
interface |
Defines the IP addresses of the server, configures an interface type, and enters interface configuration mode. |
|
interface tunnel |
Configures a tunnel interface. |
|
ip igmp unidirectional-link |
Configures an interface to be unidirectional and enables it for IGMP UDLR. |
|
tunnel udlr address-resolution |
Enables the forwarding of ARP and NHRP over a UDL. |
|
tunnel udlr receive-only |
Configures a unidirectional, GRE tunnel to act as a back channel that can receive messages, when another interface is configured for UDLR to send messages. |
udp-port
To change the User Datagram Protocol (UDP) port numbers to which a Test Sender sends test packets or a Test Receiver sends status reports during Multicast Routing Monitor (MRM) tests, use the udp-portcommand in MRM manager configuration mode. To restore the default settings, use the no form of this command.
Syntax Description
|
test-packet port-number |
(Optional) Specifies the UDP port number to which test packets are sent by a Test Sender. The port number must be even if the packets are Real-Time Transport Protocol (RTP)-encapsulated. The range is from 16384 to 65535. By default, the Test Sender uses UDP port number 16834 to send test packets. |
|
status-report port-number |
(Optional) Specifies the UDP port number to which status reports are sent by a Test Receiver. The port number must be odd if the packets are RTP Control Protocol (RTCP)-encapsulated. The range is from 16834 to 65535. By default, the Test Receiver uses UDP port number 65535 to send status reports. |
Command Default
Test Senders use UDP port number 16834 to send test packets, and Test Receivers use UDP port number 65535 to send status reports.
Command History
|
Release |
Modification |
|---|---|
|
12.0(5)S |
This command was introduced. |
|
12.0(5)T |
This command was integrated into Cisco IOS Release 12.0(5)T. |
|
12.2(33)SRA |
This command was integrated into Cisco IOS Release 12.2(33)SRA. |
|
12.2SX |
This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware. |