Current IP Multicast Commands ----------------------------- Change history 10/06/01 - Added pointer to configuration note for "ip pim rp-announce-filter" 10/10/01 - Added description for IGMP immediate-leave (CSCdk29405, CSCdr27925) ip igmp immediate-leave (global, interface) 09/20/01 - Added description for CSCdm73649 commands: ip pim dense-mode proxy-register ip pim bsr-border 09/17/01 - Added description for "ip msdp sa-limit", updated documentation for "show ip msdp count", "show ip msdp peer", "show ip msdp count" [CSCdt19258]. 09/17/01 - Updated information on "ip msdp cache-sa-state" - mandatory now [CSCdr93446]. 08/29/01 - Added description about UDP/IGMPv3lite port number change 659 -> 465 due to CSCdr53615. 07/12/01 - Added documentation for "ip pim register-source", added notes 06/29/01 - Corrected documentation for ip multicast multipath 06/27/01 - Added documentation for ip pim bidir-enable 05/28/01 - Added documentation for ip pim dr-priority 05/28/01 - Added documentation for Bidir-PIM commands ip pim rp-address ... bidir ip pim send-rp-announce ... bidir ip pim rp-candidate ... bidir 05/17/01 - Added description for ip msdp sa-filter RP matching options 05/09/01 - Added documentation for source option to "ip igmp static-group" 05/09/01 - ip pim spt-threshold note added. 05/09/01 - Added SSM / IGMP version 3 feature documentation: ip igmp version 3, ip pim ssm, ip urd, ip igmp v3lite, show ip igmp group detail, debug ip urd Notes: The text in brackets after the description of a command details the releases and sometimes also the ddts number in which this command appeared. The versions shown are only those where a command was explicitly added to the code, but in addition to that, the command will also be available on all further IOS version that inherit from one one the shown IOS versions: 12.0S, 12.0T inherits from 12.0 12.1 inherits from 12.0T 12.1E, 12.1T inherits from 12.1 12.2 inherits from 12.1T 12.2S, 12.2T inherits from 12.2 Global commands: [no] ip multicast-routing [distributed] Enables IP multicast forwarding. If disabled, group addressed IP packets that the router is not a member will be discarded. The default value is IP multicast routing disabled. [10.2] The distributed keyword will enable distributed fastswitching for the router. The interface command described below will enable individual interfaces for distributed fastswitching. [11.1(20)CC]. [no] ip multicast cache-headers [rtp] [] Allocates a circular buffer to store IP multicast packet headers that are received by the router. This command will allocate approximately a 32 kilobyte buffer. If you are low on memory, this command should not be used. Use the "show ip mpacket" command to display this buffer. This feature is used to determine 1) who is sending to what groups, 2) what the inter-packet delay and 3) if there are any duplicates or multicast forwarding loops in your network. [11.1] When the keyword "rtp" is used, RTP headers will also be saved. This is used in conjuction with the "show ip mpacket quality" command. [11.1(20)CC] is the power-of-2 number of cache entries maintained in the circular buffer. Valid values are 10 through 20. Use caution when setting this value greater than 10 because you can use up all the memory in the router. The default value is 10, which means 1024 entry circular buffer is maintained. [11.1(22)CC, 12.0S] [no] ip multicast multipath By default, this command is not enabled, and the RPF neighbor for all (*,Gi) with a certain RP and all (Si,G) with a certain Si is the PIM neihgbor with the highest IP address if there are multiple equal-cost alternatives for RP or Si. If this command is enabled, then the RPF neighbor will be selected pseudo-randomnly from the available equal-cost RPF neighbors, resulting in load splitting of traffic from different sources amongst the available equal cost paths (or neighbors). All traffic from a single source is still received from a single neighbor [12.0, 12.0S, 12.0T] [no] ip pim bidir-enable This global configuration command enables support for Bidir PIM on the router. If not enabled, then The router will behave like a legacy IOS router that does not support Bidir-PIM: The PIM Hello messages will not contain the Bidir option, the bidir options to the rp configuration commands will not be allowed, no Bidir-PIM DF election messages will be sent and received messages will be ignored, CLI commands for bidir will not work. This command exists to avoid potential issues when upgrading routers to images supporting Bidir-PIM. The default for this command in 12.0ST is "no ip pim bidir-enable", the default for 12.2 and 12.2T is "ip pim bidir-enable". [CSCdu53264, 12.0(18)ST, 12.2(2), 12.2(3)T] [no] ip pim ssm [ default | range ] Configure the SSM-range. If the argument default is configured, then the range 232.0.0.0...232.255.255.255 will be used as the SSM-range. If range is configured than must be a numeric or named standard ip access list defining the SSM-range - all ip addresses permitted by will be considered to be within the SSM-range. The SSM-range is the range of addresses, in which the router will support Source Specific Multicast (SSM) operations: Receiver hosts use IGMP version 3, URD or IGMP v3lite to explicitly join to an (S,G) channel to receive traffic directly via the shortest path from the source. [12.1(5)T, 12.2, 12.0(15)S, 12.1(8)E] [no] ip pim register-source By default this command is not configured and routers who are DR and need to send PIM sparse mode register messages will use the ip address of the interface towards the RP as the source address for these register messages. If that interface address is one that the RP can not reach (scoped or anycast address), then the PIM sparse mode registration process will malfunction because the RPs register-stop messages will not reach the DR. Configure ip pim register-source in global configuration command to make this router use the ip address of as the source address of PIM sparse-mode register messages if you need to avoid such problem. [CSCdm95268, 12.1(1)] [no] ip pim rp-address [] [override] [bidir] Configures the PIM Rendezvous Point (RP) address for a particular group. The RP address is used by first-hop routers to send Register packets on behalf of source multicast hosts. The RP address is also used by routers on behalf of multicast hosts that want to become members of a group. These routers send Join and Prune messages toward the RP. A single RP can be configured for multiple groups described by the access-list pointer. [10.2] If keyword "bidir" is supplied, the group range will be used for bidirectional shared-tree forwarding otherwise it will be used for sparse mode forwarding. A single can only be configured to be RP for either bidir or sparse mode group ranges. [12.1(2)T, 12.2] If there is no RP configured for a group, the router will treat the group as dense using the dense-mode PIM techniques. If the RP for a group is learned through a dynamic mechanism, such as Auto-RP, then this command may not be required. If there is a conflict between the RP configured with this command and one learned by Auto-RP, the Auto-RP information is used. Unless, the "override" keyword is specified. [11.1] [no] ip pim accept-rp {
| auto-rp} [] When this command is entered, the router will only accept (*,G) Joins with an RP address of
if G is in the group range specified by . When this command is entered with an address equal to one of the system's addresses, the system will be the RP only for the specified group range specified in . When not in the group range, the RP will not accept Joins or Register messages and will respond immediately to Registers with Register-Stop messages. There is no default setting for this command. [10.2] When the keyword "auto-rp" is specified, Join and Register messages will only be accepted for RPs that are in the Auto-RP cache. [11.1] If
is 0.0.0.0, the filter will accept any RP for any group accepted by , and deny any RP rejected by . When multiple "ip pim accept-rp" filters are configured, they must be configured in the following order (in 11.3(4.5), 12.0(1) and newer images the following order is guaranteed by the IOS, irrespective of the configuration sequence): ip pim accept-rp ip pim accept-rp auto-rp ip pim accept-rp 0.0.0.0 The following example will accept 171.69.58.88 as the RP for groups in 239.0.0.0/8, and RPs for groups in the Auto-RP cache. If the RP and group don't match the first two filters, the 3rd filter is in effect, i.e. any RP is accepted for groups permitted by ACL 2, and no RP for 224.0.1.39 and 224.0.1.40 is accepted. ip pim accept-rp 171.69.58.88 1 ip pim accept-rp auto-rp ip pim accept-rp 0.0.0.0 2 access-list 1 permit 239.0.0.0 0.255.255.255 access-list 2 deny 224.0.1.39 access-list 2 deny 224.0.1.40 access-list 2 permit any [no] ip pim send-rp-announce scope group-list [interval ] [bidir] This command sends an Auto-RP RP annoucement message to the well known group CISCO-RP-ANNOUNCE (224.0.1.39). This command should be used in a router you want to be the RP. The RP address field inside the announcement message will contain the IP address from the . is the time-to-live in the IP header which is set. This allows for the announcements to stay inside a ttl scoped boundary. is an access-list describing the group ranges this system is willing to be the RP for. Note that the deny clauses in the are ignored. [11.1] If keyword "bidir" is supplied, the group range will be used for bidirectional shared-tree forwarding otherwise it will be used for sparse mode forwarding. In AutoRP, a single IP address can only be RP for one type of groups, bidir or sparse mode. Use different arguments if you want to use a single router as an RP for both bidir-PIM and sparse mode group ranges and want to use Auto-RP to announce these mappings. [12.1(2)T, 12.2] Starting with IOS versions [12.0(1.1)], if the access-list contains a "deny" entry, auto-rp will maintain a negative entry for those group ranges. This will make it easier to configure group ranges to be dense-mode only groups. An RP announcement with a denied group prefix overrides any positive announcements for the same prefix from other RPs. However, IOS versions prior to this required a deny clause. The access-list must be changed to remove these deny clauses to obtain the correct RP map. When "interval" is specified, the interval between RP announcements is set to . The total holdtime of the RP announcements is automaticly set to 3 times . The default interval is 60 seconds. Tuning this interval down can reduce the time required to fail over to a secondary RP, at the expense of generating more Auto-RP messages through the entire region covered by the ttl scope. [11.2(18), 11.3(8), 12.0(3.1)] [no] ip pim send-rp-discovery [] scope This command is entered in the PIM RP-mapping agent. The RP-mapping agent listens on well-known group address CISCO-RP-ANNOUNCE (224.0.1.39) that candidate RPs send to. The RP-mapping agent will send RP-to-group mappings in an Auto-RP RP discovery message to the well known group CISCO-RP-DISCOVERY (224.0.1.40). PIM DRs will listen to this group and use the RPs they learn from the RP discovery message. is the time-to-live in the IP header which is set. This allows for the discovery messages to stay inside a ttl scoped boundary. [11.1] When is specified, RP discovery messages will be sourced from the IP address assigned to . [12.0] [no] ip pim rp-announce-filter rp-list group-list This command is entered in the PIM RP-mapping agent. This command configures an incoming filter for RP announcement messages. Parameter "rp-list " configures an access-list of RP addresses that, if permitted, will be filtered for the group ranges denies by the parameter "group-list ". If this command is not configured, all RP announcements are accepted. If you are going to use more than one RP-mapping agent, the filters should be consistent among them so there is no conflicts between different mapping agents. [11.1] For more detailed explanations and examples see: ftp://ftpeng.cisco.com/ipmulticast/config-notes/rp-announce-filter.txt [no] ip pim spt-threshold | infinity [group-list ] Configures when a PIM leaf router should join the shortest path source-tree for the specified group. is the traffic rate in kilobits per second. If a source sends at a rate greater than or equal to , a PIM Join message is triggered towards the source to construct a source-tree. If "infinity" is used, all sources for the specified group will use the shared-tree. Specifying a "group-list" indicates what groups the spt-threshold applies to. is a reference to a simple IP access-list. When a value of 0 is specified or the group-list parameter is not used, the threshold applies to all groups. The default setting (when this command is not used), is to join the shortest path tree immediately after the first packet arrives from a new source. [11.1] The ability to define an spt threshold value other than 0 or infinity is deprecated. It should not be used and may not be supported in further releases [05/01]. [no] ip pim bsr-candidate [] Configures the router to send bootstrap messages with 's address as the bootstrap-router (BSR) address, if no better bootstrap router is found. must be a PIM enabled interface. is the mask length used by the PIMv2 hash function. This hash mask length is accepted by all routers within the same PIM domain when selecting an RP. is an integer whose value is between 0 and 255. It is 0 by default. BSRs with larger preference values are preferred over those with smaller values. This command should only be used in "backbone" routers with good connectivities to all parts of the PIM region. E.g. a stub router that relies on an on-demand dial-up link to connect to the rest of the PIM domain is not a good candidate BSR. [11.3T] [no] ip pim rp-candidate [group-list ] [bidir] Configures to send pim version 2 candidate RP advertisement to the bootstrap RP. The IP address associated with will be advertised as the candidate RP address. The group prefixes defined by simple access-list will also be advertised in association with the RP address. RP-candidates should also be placed in the well-connected "backbone" part of the PIM domain. [11.3T] If keyword "bidir" is supplied, the group range will be used for bidirectional shared-tree forwarding otherwise it will be used for sparse mode forwarding. A single interface can only be RP for one type of groups, bidir or sparse mode. Use different arguments if you want to use a single router as an RP for both bidir-PIM and sparse mode group ranges. [12.1(2)T, 12.2] [no] ip pim register-rate-limit Sets a limit on the maximum number of data registers/second sent for each (S,G). If this is configured on a PIM domain border, a recommended is 2. [11.3T, 11.1(20)CC] [no] ip pim accept-register list | route-map Configures where Register messages are accepted from. This command is used only in candidate RPs. If "list " is used, you can configure an extended access-list which determines which (source, group) pairs will be permitted or denied when seen in a Register message. If "route-map " is used, you can apply typical route-map operations on the route for the source address which appears in a Register message. Both keywords "list" and "route-map" are not allowed together. When a Register message is denied, an immediate Register-Stop is sent back to the originator of the Register. [12.0, 12.0S, 12.0T] [no] ip dvmrp routehog-notification This configures the number of routes allowed within an approximate one minute interval before a syslog message is isssued warning that there maybe a route surge going on in the MBONE. This is typically used to detect quickly when someone has misconfigured their routers to inject a large number of routes into the MBONE. The default value is 10,000. You can find a running count in the "show ip igmp interface" display. When the count is exceeded, you'll see an "*** ALERT ***" string appended to the line. [10.2] [no] ip dvmrp route-limit This command limits the number of DVMRP routes advertised over an interface enabled to run DVMRP. That is a DVMRP tunnel, an interface where a DVMRP neighbor has been discovered, or an interface configured to run "ip dvmrp unicast-routing". The default value is 7000. This command will be automatically generated to the configuration file when at least one interface is enabled for multicast routing. This command is necessary so misconfigured "ip dvmrp metric" commands don't cause massive route injection into the MBONE. The "no" version of the command configures no limit. [11.0] [no] ip dvmrp distance Configures the default adminstrative distance for received DVMRP routes. This command should be used so routes advertised from the unicast routing table that are reflected back through DVMRP cause the original unicast routes to continue to be advertised. The "ip dvmrp accept-filter" command may override this value when specified on an interface. [11.2] [no] ip mroute [] [route-map ] | [] Configures a multicast static route (called a "static mroute"). When a source range is specified, the mroute applies only to those sources. When is specified, the mroute applies to those sources that have been learned by the corresponding routing process. If route-map is specified, further classification can be accomplished by the match clauses from . If the mroute is selected, the address dictates the incoming interface for the source that matches the mroute. If the is a PIM neighbor, PIM Joins, Grafts, and Prunes will be sent to it. The can be a host address of a directly connected router or a route. When it is a route, a recursive lookup is done from the unicast routing table to find a directly connected neighbor. If is not specified, is used as the incoming interface. is used to decide if a unicast route, a DVMRP route, or a static mroute should be used for the RPF lookup. The lower distances have better preference. If the static mroute has the same distance as the other two RPF sources, the static mroute will take precedence. There are only two exceptions to this rule, directly connected routes and the default unicast route. Default is 0. Static mroutes are local to the router and are not redistributed by any dynamic routing protocol. [11.0] [no] ip sdr cache-timeout The amount of time an sdr cache entry stays active in the cache. A value a 0 indicates the entry will never timeout. The default value is 24 hours. [11.2] [no] ip pim state-refresh disable Disables PIM-DM State-Refresh message processing and forwarding. A router configured with this command will behave like a non-State Refresh capable router and will not advertise the SR-capability in PIM Hello messages. By default, State-Refresh processing and forwarding is enabled. [12.1(3)T] ip igmp immediate-leave group-list no ip igmp immediate-leave Use this command to reduce the leave latency of IGMP memberships to zero when IGMP version 2 is in use and only a single receiver host is connected to each interface: If this command is not configured, the router will operate the normal IGMP version 2 leave process: It will send out a group specific query upon receipt of an IGMP version 2 leave message to learn if more hosts are interested in receiving this group. The router can then only stop forwarding traffic for the group if no host replies within the timeout resulting in a leave latency of around 2 to 3 seconds. If this command is configured, then the router assumes that only one host was joined to the group and stops forwarding the groups traffic immediately. Forwarding for only those groups is affected by this commands which are allowed by the standard or named standard access list . Use to limit the effect of this command to group ranges known to be receivable by only one host on each interface even if there may be multiple hosts. This command does not change the leave latency if IGMP version 3 is in effect for the group. To reduce the the leave latency with IGMP version 3, use the explicit tracking support for IGMP version 3. This command will take no effect on interfaces where IGMPv1 hosts are present. The global version of the immediate-leave command can not be used together with the per-interface immediate-leave command. You must either use one global configuration command or per-interface commands. When the global command is configured, the per-interface immediate-leave commands will be removed from the configuration and newly entered interface immediate-leave commands will silently be ignored. [CSCdr27925, 12.2(4)] This command was available in pre-IOS 12.2 versions as a hidden command and is thus unsupported in those releases. [CSCdk29405, 12.0(4)] ------------------------------------------------------------------------ IS-IS and OSPF Router commands: [no] mpls traffic-eng multicast-intact MPLS TE (traffic engineering) tunnels can not be used to convey PIM protocol traffic because theses tunnels are unidirectional in nature. This command allows for coexistance of PIM and MPLS TE tunnels by using native hop-by-hop transport for PIM protocol packets, even though the unicast routing is using MPLS TE tunnels. Configure this command under router IS-IS or router OSPF to enable the MPLS TE and PIM interworking for routes of the appropriate routing protocol (OSPF and/or IS-IS). By default, this command is disabled. [12.0(7)S,12.1(2)T, 12.1(2) via CSCdm63234] ------------------------------------------------------------------------ Interface subcommands: ip igmp immediate-leave group-list no ip igmp immediate-leave Use this command to reduce the leave latency of IGMP memberships to zero when IGMP version 2 is in use and only a single receiver host is connected to each interface. Please refer to the documentation for the global configuration command "ip igmp immediate-leave" for more details [no] ip igmp join-group Informs the router to join group on the interface. IP packets that are addressed to this group address will be passed up to the IP client process in the router as well forwarded out the interface. If you do not want packets forwarded out the interface, join the group on a loopback interface. Packets are not sent on the loopback interface. [10.2] [no] ip igmp static-group [ source ] [no] ip igmp static-group | "*" Configures a static connected member for the group on the interface. Packets to the group will get fastswitched, unlike the "ip igmp join-group" command. If "ip igmp join-group" command is used for the same group address, it will take precedence and the group will behave like a locally joined group. [11.2] If the "*" keyword is present, then the interface will be placed by default into all newly created mroute entries. It will not create new state where there was none before. Note that this means that prunes will be ignored when received on the interface. [12.0T] The source option is in support of SSM. It allows to statically forward a (,) channel out of the interface. This option does not create mroute forwarding state for groups that are not within the SSM range. [12.0(15)S, 12.2(1)]. [no] ip igmp query-interval Configures the frequency of IGMP Host-Query packets transmitted. A designated router for a LAN is the only router that transmits queries. For IGMPv1, the designated router is elected according to the multicast routing protocol that runs on the LAN. For IGMPv2, the designated querier is the lowest IP addressed multicast router on the subnet. The default value is 60 seconds. [10.2] [no] ip igmp last-member-query-interval Configures the "last member query interval" to be , in milliseconds. The default value is 1000 ms, or 1 second. A value below 1 second can result in faster IGMP leave actions. [12.0] [no] ip igmp access-group Configures what groups are allowed on the interface. The default is all groups are allowed. [10.2] [no] ip igmp version 3 | 2 | 1 Interface subcommand to change IGMP version. Default is version 2. [11.1] IGMP version 3 enabled receiver applications to signal (S,G) channel membership in support of SSM. Enable IGMP version 3 on all interfaces connected to receivers, if SSM is needed [12.1(5)T, 12.0(15)S, 12.2] [no] ip igmp v3lite Configure this command on interfaces connected to receiver hosts if you are using SSM and users may run applications on older host operating systems that do not yet support IGMP version 3 directly. IGMP v3lite enables the router to accept UDP (port 659) encapsulated IGMP version 3 application specifically compiled to support older operating systems (like IP/TV 3.2 and later). [12.1(5)T, 12.0(15)S, 12.2]. See the following URL for library needed to compile applications for IGMPv3lite. This is called the HSIL (Host Side IGMP Library): http://www.talarian.com/products/multicastlite/index.shtml The port used by igmp v3lite was changed to UDP port 465 via CSCdt68756 (See Release Notes for the ddts on CCO for more explanations). The HSIL will default to this new port in version 1.1 and later [12.2(4)M/B/T, 12.0(19)S/ST, 12.1(8a)E02]. [no] ip urd [proxy] Configure this command on interfaces connected to receiver hosts if you are using SSM and users may run applications that by themselves do not support IGMP version 3 yet. URD is a mechanism that allows web-started applications (like typical streaming media players) to be SSM augmented from an appropriately written web page. With URD enabled, the router will intercept TCP connections to port 659, act like a HTTP server on that port and interpret URLs requested from the clients browser to contain SSM channel information: http://arbitrary:659/arbitrary?group=&source=& If the router intercepts such a URL, it will join to the (,) SSM channel as soon if or as soon as it also sees that the legacy application is simply trying to join to the group . In the URL, and can either be IP addresses or fully qualified domain names (you need to have domain name resolution enabled on the router to support domain names). [12.1(5)T, 12.0(15)S, 12.2(1)] If the proxy option is not given, intercepted TCP connections are only considered to be valid, if they originate from directly connected hosts. If the proxy option is given, requests will be honored from any TCP connection arriving on this interface. Never enable the proxy option on a backbone interface because this would allow people from the backbone to create URD state in your router. This option is meant to be used with unnumbered interfaces towards users or stub networks with IGMP proxy routers downstream of your router. [12.2(1), 12.0(16)S] The port used by URD was changed to TCP port 465 via CSCdt68756 (See Release Notes for the ddts on CCO for more explanations). [12.2(4)M/B/T, 12.0(19)S/ST, 12.1(8a)E02]. [no] ip igmp query-timeout [timeout value in secs] This command is valid when IGMP v2 is running. This command specifies the timeout for the router to take over as the querier for the interface, after the previous querier has stopped querying. The default value is 2 * query-interval. If the router hears no queries for the "timeout" period, it becomes the querier. [11.1] [no] ip igmp query-max-response-time [secs] This command is valid when IGMP v2 is running. This command specifies the maximum query response time advertised in the IGMP queries. Default value is 10 secs. Configuring a value less than 10 seconds enables the router to prune groups faster. [11.1] [no] ip igmp helper-address This command causes all IGMP host report and leave message received on the interface to be forwarded toward the given ip-address. The reports are resent out the next-hop interface towards the ip-address with that interface's source address. This command can enable a sort of "dense-mode" join, allowing stub sites not participating in PIM to indicate membership in multicast groups. [11.3] [no] ip cgmp Enables the Cisco Group Management Protocol (CGMP) for IP multicast on a LAN. The command triggers a CGMP Join message. This should only be enabled on 802 media (i.e. Ethernet, Fddi, and Token Ring) or ATM. When a "no" is issued, a triggered CGMP Leave message is sent for the router's MAC address on the interface for group 0000.0000.0000. CGMP can only run on an interface if PIM is configured on the same interface. [11.1] A cisco will send CGMP Join messages in response to receiving IGMP reports from multicast capable members. Only the IGMP querier cisco router sends these CGMP Join messages on behalf of hosts. [no] ip cgmp proxy Enables CGMP for IP multicast as well as a proxy function. Initially supported is DVMRP proxying. If a DVMRP Report is received from a router that is not a PIM router, a cisco IGMP querier will advertise the MAC address of the DVMRP router in a CGMP Join with group address 0000.0000.0000. [11.1] To perform CGMP proxy, a cisco must be the IGMP querier. An IGMPv2 querier is selected based on the lowest IP addressed router on the interface. An IGMPv1 querier is selected based on the multicast routing protocol used on the interface. When multiple cisco routers are connected to a switched network and "ip cgmp [proxy]" is needed, it is recommended that all of them are configured 1) with the same CGMP option and 2) to have precedence of becoming IGMP querier over non-cisco routers. [no] ip pim version [1 | 2] Configures PIM version for this interface. Default is 2. [11.3T] [no] ip pim dr-priority Configures the neighbor priority used for PIM Designated Router (DR) election. The router with the largest on an interface will become the PIM DR. If multiple routers have the same priority, then the largest IP addressed system on the interface becomes DR. If a router doesn't include the DR-Priority Option in it's Hello messages, the router is regarded highest priority router and will become DR. If multiple of such routers exist, the largest IP addressed router will become DR. This allows interoperation with older systems. [12.1(2)T, 12.2, feature available in IOS images with Bidir-PIM] [no] ip pim [dense-mode | sparse-mode] Enables the PIM multicast routing protocol on the interface. Configures the interface to operate in dense or sparse mode. The default mode is dense-mode. A dense-mode interface is subject to multicast flooding by default. A sparse-mode interface is only used for multicast forwarding if a join is received from a downstream router or their are directly connected members on the interface. When "no ip pim" is entered, it disables PIM on the interface. [10.2] [no] ip pim sparse-dense-mode Enables the PIM multicast routing protocol on the interface. In this mode, the interface will be treated as dense-mode if the group is in dense-mode. If the group is in sparse-mode, the interface will be treated in sparse-mode. When an interface is treated in dense-mode, it will be populated in a multicast routing table's outgoing interface list when 1) there are members or DVMRP neighbors on the interface, or 2) any of the PIM neighbors on the interface have not pruned for the group. When an interface is treated in sparse-mode, it will be populated in a multicast routing table's outgoing interface list when 1) there are members or DVMRP neighbors on the interface or 2) an explicit Join has been received by a PIM neighbor on the interface. [11.1] [no] ip pim dense-mode proxy-register [list | route-map ] Enable this command on an interface connecting to a dense-mode region to enable registering for sources in that dense-mode region. For multicast groups in PIM sparse mode, the router will normally do the PIM sparse mode registering if it is the first-hop DR, directly connected to the source. If the router receives a packet from a non-directly connected source on an interface it will only register for this if either a DVMRP neighbor is active on an interface, or if this command is configured. Configuring this command will thus allow to get traffic from a source in a PIM dense-mode region to be correctly received by a receiver in the sparse mode region. In addition to a dense mode border, this command also needs to be configured on interfaces connecting to a stub region with IGMP proxying routers to allow for sources from that region to be correctly registered for when sending to PIM sparse mode groups. Because the "proxy-register" option is only supported together with the "ip pim dense-mode" interface mode, one should avoid putting further PIM or DVMRP routers on that interface (only IGMP proxy routers) to avoid that the border router starts to flood traffic (as long as there is no DVMRP or PIM router connected, a dense-mode interface does not behave different from a sparse-mode or sparse-dense-mode interface). Use the "list " or "route-map " options to limit the (S,G) packets arriving at this interface for which the router will do registering. These filtering options will only affect (S,G) for which S is not directly connected. [12.0(7), CSCdm73649] [no] ip pim query-interval Configures the frequency of PIM Router-Query messages. Router Query messages are used to elect an PIM designated router (DR). The DR is responsible for sending IGMPv1 Host-Query messages, PIM Register messages on behalf of sender hosts, and Join messages on behalf of member hosts. The default value is 30 seconds. [10.2] [no] ip pim neighbor-filter This command filters all PIM control messages based on the given access-list. It can be used to administratively deny a misconfigured PIM neighbor from participating in PIM, or in conjunction with "ip igmp helper-address" to be the basis for a simple stub IP multicast setup. Note: this command does not filter Auto-RP announcents and is only intended to filter neighbor-to-neighbor packets. [11.3] [no] ip pim multipoint-signalling Enables PIM to open ATM multipoint VCs for each multicast group that is joined. This command is only accepted on an ATM interface. This command allows optimal multicast trees to be built down to ATM switch granularity. This can enhance router performance and link utilization since packets are not replicated and sent multiple times over the ATM interface. The default setting is disabled. That is, all multicast traffic goes to the static map multipoint VC as long as "atm multipoint-signalling" is configured. [11.3] [no] ip pim vc-count Configures the maximum number of VCs PIM opens. The default value is 200. When the router hits this maximum limit it will delete inactive VCs so it may open VCs for new groups that might have activity. [11.3] [no] ip pim minimum-vc-rate Configures the minimum traffic rate to keep VCs active. When the maximum number of VCs are opened and a new VC needs to be opened, the router will scan existing VCs. VCs that have a current 1 second rate less than or equal to are eligible for deletion. If a VC is deleted, it means that packets for its respective group do not have its own multipoint VC. However, packets will flow over a shared multipoint VC which delivers packets to all PIM neighbors. If all VCs have a 1 minute rate more than , the new group will use the shared multipoint VC. The default value is 0 packets per second. [11.3] [no] ip pim bsr-border Configures the interface to be the PIM domain border. Bootstrap messages will not be able to pass through this border in either directions. Thus effectively partitions the network into regions using different bootstrap routers. No other PIM messages are dropped by this domain border setup. Please also note that this command does not set up any multicast boundaries. [12.0(7), CSCdm73649] Prior to renaming in 12.0(7) and all later IOS releases, this command was called "ip pim border". This old syntax is still accepted on input but will be NV generated as "ip pim bsr-border". [no] ip pim border See "ip pim bsr-border". [11.3T, 11.1(20)CC] [no] ip dvmrp metric [list ] {[ ] | dvmrp] When PIM is configured on an interface and DVMRP neighbors are discovered, the router will, by default, send DVMRP Report messages. Under certain circumstances, it may be desirable to tailor the metric used for various unicast routes. This command allows one to configure the metric associated with a set of destinations for Reports sent out this interface. The acceptable value is between 0 and 32, where 0 means that the route will not be advertised and 32 means infinity and the route is advertised unreachable. If an is specified, only the destinations that match the access-list will be reported with the configured metric. can be a simple or extended access-list. When extended access-lists are used, you have both address and netmask granularity. Any destinations not advertised due to split horizon will not use the configured metric. If the is configured, only routes learned by the specified routing protocol will be advertised in DVMRP Report messages. This parameter can be used in conjunction with so a selective list of destinations learned from a given routing protocol may be reported. If this command is not used, only directly connected networks are advertised when DVMRP neighbors are discovered. If the "dvmrp" keyword is configured, only routes from the DVMRP routing table will be selected to be advertised with . This command can be used multiple times on an interface. [10.2] [no] ip dvmrp metric route-map This command has existed since release 10.2. What has been added is the route-map keyword. Now unicast routes can be subject to route-map conditions before being injected into DVMRP. Note, route-maps cannot be used for DVMRP routes. [11.1] [no] ip dvmrp metric [route-map ] mbgp Configures redistribution of MBGP routes into DVMRP. If you supply a route-map, you can specify various match criteria options for the MBGP routes. [11.1(20)CC] [no] ip dvmrp accept-filter [neighbor-list ] [] Configures an acceptance filter for incoming DVMRP Reports. Any destinations that match received in DVMRP reports from neighbors in the are stored in the DVMRP routing table with . The distance is used to compare with the same destination in the unicast routing table. The lower distance route (either from the unicast routing table or DVMRP routing table) will take precedence when computing the RPF interface for a source of a multicast packet. When no filters are configured on an interface, all destinations are accepted with distance configured from the "ip dvmrp distance" global command. An value of 0, accepts all destinations. can be a simple or extended access-list. If extended access-lists are used, you have both address and netmask granularity. An value of 0 means accept from all neighbors on interface. [10.2] [no] ip dvmrp default-information originate | only Indicates network 0.0.0.0 is advertised to DVMRP neighbors on this interface. By default, metric 1 will be used. This command can be used with the "ip dvmrp metric" command to tailor the metric used when advertising default. This command only takes effect when peering with mrouted 3.4 machines. When keyword "only" is used, no other DVMRP routes are reported. When keyword "originate" is used, other more specific routes may be advertised. Do not advertise the DVMRP default route into the MBONE. [10.2] [no] ip dvmrp metric-offset [in | out] This is the value added to the metric of a DVMRP route advertised in a Report message. When "in" (or no keyword is supplied, the applies (is added) to incoming DVMRP reports and is reported in mrinfo replies. When the "out" keyword is supplied, the applies (is added) to outgoing DVMRP reports for routes from the DVMRP routing table. This is similar to the metric keyword in mrouted configuration files. The default value for "in" is 1. The default value for "out" is 0. [11.0] [no] ip dvmrp unicast-routing Enables DVMRP unicast routing on the interface. This means that routes in DVMRP Report messages are cached by the cisco in a DVMRP routing table. When PIM is running, these routes get preference over routes in the unicast routing table. This allows PIM to run on the MBONE topology, when it is different (or deviates) from the unicast topology. The default setting is off. DVMRP unicast routing can run on all interfaces including GRE tunnels. On DVMRP tunnels, it runs by virtue of doing DVMRP multicast routing. This command does not enable DVMRP multicast routing among ciscos. However, if there is a DVMRP capable multicast router, the cisco will do PIM/DVMRP multicast routing interaction. [10.3] [no] ip dvmrp reject-non-pruners This command will cause the router not to peer with a DVMRP neighbor if the neighbor doesn't support DVMRP Pruning/Grafting. If a DVMRP Probe or Report message is received without the Prune-Capable flag set, a syslog message will be logged and the message will be discarded. The default setting of this command is that all DVMRP neighbors will be accepted, regardless of capability (or lack there of). This command only prevents peering with neighbors. If there are any non-pruning routers multiple hops away (downstream towards potential receivers) that are not rejected, then a non-pruning DVMRP network may still exist. [11.0] [no] ip dvmrp summary-address
metric Configures a summary address to be advertised out the interface. If there is at least one more specific route in the unicast routing table that matches the
/, the summary will be advertised. Routes in the DVMRP routing table are not candidates for summarization. When the metric keyword is supplied, the summary will be advertised with metric . The default metric is 1. Multiple summary addresses can be configured on an interface. When multiple overlapping summary addresses are configured on an interface, the one with the longest mask takes preference. [11.2] [no] ip dvmrp auto-summary Enables/disables DVMRP auto-summarization. DVMRP auto-summarization occurs when a unicast subnet route is collasped into a classful network number route. This occurs then the subnet is a different network number than the IP address of the interface (or tunnel) the advertisement is sent over. If the interface is unnumbered, the network number of the numbered interface the unnumbered interface points to is compared. The default setting for this command is enabled. [11.2] [no] ip dvmrp output-report-delay [] Configures an inter-packet delay between DVMRP reports. , in milliseconds, is the amount of time that elaspes between transmission of a set of number packets. For example, at the periodic DVMRP report interval, if 6 packets are built, and the is 200 with of 2, 2 packets will be sent, then a delay of 200 milliseconds occurs, then another 2 packets are sent, then another delay of 200 milliseconds, then the final 2 packets are sent. The default value for is 2. The default value for is 100 milliseconds. [11.2] [no] tunnel mode dvmrp Configures a cisco tunnel to encapsulate IP in IP using protocol number 4. This mode can be used when a cisco connects to a mrouted machine to run DVMRP over a tunnel. This is a popular way to connect to the MBONE. It is required to configure PIM and an IP address on a DVMRP tunnel. This mode is not used to construct a tunnel between a pair of cisco routers. [10.2] [no] ip multicast ttl-threshold Configures a packet TTL threshold for traffic going out the interface. Any multicast packets with a TTL less than the threshold are not forwarded out the interface. The default value is 0 which means all multicast packets are forwarded out interface. [10.2] [no] ip multicast rate-limit in | out [video] | [whiteboard] [group-list ] [source-list ] [] Controls the rate a sender from the source-list can send to a multicast group in group-list. Any packets greater than are silently discarded. The default value for is 0, meaning all packets are discarded. If "in" is used, only will be accepted on the interface. IF "out" is used, only a maximum of kilobits per second will transmitted on the interface. If keywords "video" or "whiteboard" are used, then rate-limiting is performed based on the UDP port number used for the respective media. For this to work, "ip sdr listen" must be enabled so the port number can be obtained from the sdr cache. If sdr is not enabled, or the group address is not in the sdr cache, no rate-limiting is done for the group. The default setting of this command is disabled, meaning there is no rate-limiting in effect. [11.0] [no] ip multicast boundary Configures an administratively scoped boundary on the interface for multicast group addresses in the range defined by the simple IP access-list . No multicast data packets will be allowed to flow across the boundary from either directions. This allows reuse of the same multicast group address in different administrative domains. The multicast address range 239.0.0.0 to 239.255.255.255 will be designated as the administratively scoped addresses by the IANA in the near future. For example, to configure a boundary for all administratively scoped address, do: access-list 1 deny 239.0.0.0 0.255.255.255 access-list 1 permit 224.0.0.0 15.255.255.255 interface ethernet 0 ip multicast boundary 1 If this interface is also a PIM interdomain link, the access-list that also stops unwanted Auto-RP packets would be: access-list 1 deny 224.0.1.40 access-list 1 deny 224.0.1.39 access-list 1 deny 239.0.0.0 0.255.255.255 access-list 1 permit 224.0.0.0 15.255.255.255 If the RPF interface for a multicast route has a multicast boundary configured for that group, its outgoing interfaces will not be populated. Joins received on other interfaces will be ignored as long as the boundary remains on the RPF interface. If the RPF interface changes and the boundary no longer applies to the new RPF interface, there will be join latency introduced because of the delay in populating outgoing interfaces. [11.1] [no] ip multicast helper-map { | broadcast} { | } When a multicast-capable cloud is between two broadcast-only clouds, this command helps to convert broadcast traffic to multicast at the first hop router, and convert it back to broadcast at the last hop router to deliver the packets to the broadcast clients. This command utilizes the multicast capability of the intermediate multicast cloud. It prevents unnecessary replication at the intermediate routers and can take advantage of multicast fastswitching in the multicast cloud. is an extended access-list, when specified you can selectively configure what broadcast packets are translated based on the UDP port number. [11.1] [no] ip mroute-cache [distributed] Configures IP multicast fast-switching. If fast-switching is disabled on an incoming interface for a multicast routing table entry, the packet will be sent at process level for all interfaces in the outgoing interface list. If fast-switching is disabled on an outgoing interface for a multicast routing table entry, the packet is process level switched for that interface but may be fast-switched for other interfaces in the outgoing interface list. The default setting is all interfaces are multicast fastswitched. [11.0] The "distributed" keyword will enable the interface to perform distributed fastswitching on incoming packets. This command applies to the configuration of the physical interface and not to subinterfaces. Once this command is configured on the interface, all packets coming in this interface will be distributed switched. The command "ip route-cache distributed" should be configured before this command is configured on a 7500 (and not on the 12000). [11.1(20)CC] [no] ip sdr listen Enables/disables accepting sdr Session Directory Protocol V2 packets. The router joins group 224.2.127.254 on the interface. If "ip multicast-routing" is configured, packets arriving on any interface will be accepted. In this case, it is sufficient to enable this command only on a single interface. Otherwise, you must use this command on all interfaces. [11.1] [no] ip pim nbma-mode This configures a multi-access WAN interface to be in Non-Broadcast Multi-Access mode. In this case, each PIM Join message is kept track of in the outgoing interface list of a multicast routing table entry. Therefore, only PIM WAN neighbors that have joined for the group will get packets sent to as data link unicasts. This command should only be used when "ip pim sparse-mode" is configured on the interface. This is not recommended for LANs that have natural multicast capabilities. The default setting is NBMA mode disabled. [11.0] [no] ip multicast use-functional Enables the use of the RFC 1469 mandated MAC-level address, 0xc000.0004.0000, for transmission and reception of IP Multicast traffic. Valid only on Token Ring interfaces. [11.1] [no] ip pim state-refresh origination-interval [] Configures the PIM-DM State-Refresh origination interval. By default a router will process and forward State-Refresh messages but will not originate them. This command is required on first-hop routers directly connected to multicast sources to originate State-Refresh messages. It is required that all routers attached to the same LAN have the same value for . The value for is in units of seconds. The default value is 60 seconds. [12.1(3)T] ------------------------------------------------------------------------ Debug commands: debug ip packet Logs IP packets received and transmitted. This generates lots of messages. Use with caution. [Since the beginning of day] debug ip mpacket [detail] [] [] Logs only IP multicast packets received and transmitted. This generates lots of messages. Use with caution. An optional group address is allowed to monitor a single group's packet activity. If is specified, only multicast packets from sources described by the access-list will be logged. When "detail" is used, the packet's IP header information as well as MAC address information will be display. [10.2] debug ip igmp Logs IGMP packets received and transmitted as well as IGMP host related events. Specifically IGMP protocol messages and mtrace messages. [10.2] When is specified, logging for the single group is performed. [11.3T] debug ip urd [ | ] Logs received and processed intercepted TCP connections to the URD port 659. The / options are currently ignored. [12.1(5)T, 12.2, 12.0(15)S] debug ip cgmp Logs CGMP packet/event activity. [11.1] debug ip dvmrp [detail [] [in|out]] [pruning] Logs DVMRP packets received and transmitted. Keyword "detail" will log packet contents. If is specified, only routes associated with the access-list are logged. Keywords "in" and "out" can be used to look at routes received in DVMRP reports or routes transmitted in DVMRP reports, respectively. If "pruning" is specified, only DVMRP pruning and grafting events are logged. [10.2] debug ip pim [] Logs PIM packet received and transmitted as well as PIM related events. An optional group address is allowed to monitor a single group's PIM activity. [10.2] debug ip pim auto-rp Displays Auto-RP packet activity. [11.1] debug ip pim atm Logs PIM ATM signalling activity. [11.3] debug ip mrouting [] Logs transaction events to and from the IP multicast routing table. An optional group address is allowed to monitor a single group's routing table activity. [10.2] debug ip mcache Enables debug logging for IP multicast fast-switching events. [11.0] debug ip sdr Enables logging of received sd and sdr announcements. [11.1] debug ip mds ipc [event | packet] Logs MDS IPC related activity. This command is used both on the RP and line-card consoles. [11.1(20)CC] debug ip mds process Logs MDS RP and line card events. This command is used both on the RP and line-card consoles. [11.1(20)CC] debug ip mds mevent Logs multicast FIB related events on the line card. Used to debug MFIB route creation, deletion, and update events. [11.1(20)CC] debug ip mds mpacket Logs MDS switching events. Used to debug packet drops, interface drops, and switching failures. [11.1(20)CC] debug ip mbgp updates Logs MBGP related information passed in BGP Update messages. [11.1(20)CC] debug ip mbgp dampening [] Logs route flap dampening activity. If is specified, logging occurs for the routes specified in the access-list only. [11.1(20)CC] ------------------------------------------------------------------------ Show commands: show ip igmp interface [] Displays learned groups for given interface. [10.2] show ip igmp groups [ | ] | [] [detail] Displays directly connected groups learn via IGMP. [10.2] If the detail option is given, the router will output information about SSM sources [12.1(5)T, 12.0(15)S, 12.2(1)] show ip pim neighbor [] Displays PIM neighbors discovered. [10.2] show ip pim rp [ | ] [mapping] Displays active RPs that are cached with associated multicast routing entries. If "mapping" is supplied, displays all group-to-RP mappings that are configured and/or learned from Auto-RP. [10.2] show ip pim interface [] count Displays PIM interface information. [10.2] show ip pim interface [] detail Displays detail PIM interface information. [12.1(3)T] show ip pim vc [] [] Displays ATM VC status information for multipoint VCs opened by PIM. When is specified, only the single group is displayed. When is specified, only the single ATM interface is displayed. [11.3] show ip pim bsr Displays the bootstrap router (BSR) information, including the elected BSR's IP address, priority, hash mask length etc. Information is shown if the local router is a candidate bootstrap router (BSR) but not an elected BSR. This commands also displays information about locally configured candidate RP advertisement. [11.3T] show ip pim rp-hash , shows which RP is being selected for the . It also shows whether this RP was learned via Auto-RP or v2 bootstrap mechanism. [11.3T] show ip pim joiners [] Sends a PIM Joiner-ID Request on interface . If two addresses are supplied, then the request is made for a (S,G). If just one address is supplied and it is a group address, a request is made for (*,G). Routers supporting Joiner-ID will respond indicating whether or not they are sending joins to the querying router for the specified multicast route. They will include their outgoing interface lists and several flags. [12.0S] show ip pim pruners [] Sends a PIM Pruner-ID Request on interface . If two addresses are supplied, then the request is made for a (S,G). If just one address is supplied and it is a group address, a request is made for (*,G). Routers supporting Pruner-ID will respond indicating whether or not they are sending prunes to the querying router. They will include their outgoing intreface lists (if applicable), and flags indicating the type of Prune being sent (RP-bit). [12.0S] show ip mroute [[ | ] []] [summary] Displays the IP multicast routing table. When "summary" is specified, a one line abbreviated display is provided. When "count" is specified, group count, source count, and packet count statistics are provided. [10.2] show ip mroute [[] []] count Displays packet count per (S,G) multicast routing table entry. Also includes average packet size and data rate in kilobits per second. [10.2] show ip mroute [] active [] This command shows you the rate active sources are sending to multicast groups. You can display for all groups or specify a single . will only display sources that are sending >= . The default setting shows all sources sending at a rate greater than or equal to 1 kilobit/second. If sd is running on the router, the sd session name is displayed. [11.0] show ip mroute [] [] pruned Displays (S,G) entries that have been pruned. [11.3] show ip mroute [] [] [] Display the multicast routing table entries that have in the outgoing interface list. [11.3] show ip mroute [] active [] []" Display the active multicast routing table entries that have in the outgoing interface list. [11.3] show ip mroute static Displays staticly configured multicast static routes. [11.2] show ip mpacket [detail] show ip mpacket [detail] show ip mpacket [detail] show ip mpacket [detail] show ip mpacket [read-only] Displays the contents of the circular cache-header buffer. Each time this command is entered, a new buffer is allocated. The summary display shows IP packet ident, ttl, source and destination IP addresses plus a local timestamp when the packet was received. The detail display shows the rest of the IP header fields on an additional line plus the first 8 bytes after the IP header (usually the UDP port numbers). This command is only applicable when the "ip multicast cache-headers" command is in effect. [11.1] When keyword "read-only" is specified, a new buffer is not allocated. The old buffer contineus to accumulate packet entries. Useful for repeating the display with more or less detail the second time. [11.1(22)CC, 12.0S] show ip mpacket [] quality Displays RTP loss statistics for each given source sending to group or the single source specified in . Packets received, packets lost, packets misordered, average loss gap, and loss percentage is provided. [11.1(20)CC] show ip dvmrp route [ | ] Displays the DVMRP routing table. The DVMRP routing table contains unicast destinations only when any DVMRP is running on an interface or tunnel. If is specified, a longest match lookup is performed and the entry that matches is displayed. If is specified, all routes with a next-hop interface of is displayed. [10.2] show ip dvmrp route [] poison Display interfaces where a DVMRP report with a poisoned-reversed metric has been received for the route. [11.3] show ip mcache [ []] Displays the IP fast-switching cache. If is specified, the fastswitching cache for the single group is displayed. can be either a Class D IP address or a DNS name. If is specified with , a single multicast cache entry is displayed. can be either a unicast IP address or a DNS name. [11.0] Displays "mds" if MDS is being used instead of the fastswiching. Displays the "last used time" if the fastswitching is being used. Displays "never" if the fastswitching entry is not used (process level switched). Note that if MDS is not enabled on an incoming interface which is capable of doing MDS, incoming packets wont be distributed fastswitched and will be fastswitched at the RP. Also, if the incoming interface is not MDS capable, the packet will get fastswitched or process-level switched at the RP. If the incoming interface is enabled for MDS but at least one of the outgoing interfaces is not fastswitch capable, packets will be process-level switched. So it is a good idea not to disable fastswitching on any interface when MDS is enabled. [11.1(20)CC] show ip sdr [ | "" | detail] Displays the sdr cache. If the router is configured to be a member of 224.2.127.254 (the default sd group), it will cache sdr announcements. If no parameters are used, a sorted list of session names are displayed. If is specified, the session(s) defining the multicast group will be displayed in detail format. If "" is specified, the single session is displayed in detail format. If the keyword "detail" is specified, all sessions are display detail format. [11.1] show ip rpf Displays how IP multicast routing does Reverse Path Forwarding. Since the cisco can RPF from multiple routing tables (i.e. unicast routing table, DVMRP routing table, or static mroutes), this command tells you where the information is retreived from. [11.0] show tech-support ipmulticast Provides output for a set of IP multicast related show commands. This is useful for a customer to use a single type-in to provide the necessary information so cisco can debug an IP multicast related problem. [11.2] show ip mds stats [switching | linecard] Displays distributed fastswitching stats and linecard stats. [11.1(20)CC] show ip mds interface Displays MDS related interface information. [11.1(20)CC] show ip mds forwarding [] [] Displays the MFIB table on the line-card. Displays forwarding information and related flags and counts for MDS. This command is used on the line cards via the line-card console. [11.1(20)CC] show ip mds summary Displays MDS summary information on the line-card. This command is used on the line cards via the line-card console. [11.1(20)CC] show ip mbgp can be any of the existing BGP commands supported by "show ip bgp ". The MBGP variants show multicast RIB related information. Use this command in conjunction with "show ip rpf" to determine if IP multicast routing is using MBGP routes. [11.1(20)CC] ------------------------------------------------------------------------ Clear commands: clear ip mroute [ | []] | [*] Deletes entries from the IP multicast routing table. [10.2] clear ip igmp group [ | ] | [] Deletes entries from the IGMP cache. [10.2] clear ip cgmp [] Sends a CGMP Leave message with a group address of 0000.0000.0000 and a unicast address of 0000.0000.0000. This instructs the switches to clear all group entries they have cached. If is specified, the Leave is sent only on . Otherwise, it is sent on all CGMP enabled interfaces. [11.1] clear ip dvmrp route * | Deletes routes from the DVMRP routing table. When "*" is used, all routes are deleted. When is used, the longest match route will be deleted. [10.2] clear ip sdr [ | ""] Deletes an sdr cache entry. No parameters delete the entire sdr cache. If is supplied, all sessions associated with the IP group address are deleted. If "" is specified, only the sdr cache entry with the supplied name is deleted. [11.1] clear ip pim interface [] count Clears the multicast packet counters for interface . Or clears for all interfaces when is not specified. [11.2] clear ip pim auto-rp Clears the Auto-RP cache. When is specified, only the entries related to RP are cleared. Otherwise, the entire Auto-RP cache is cleared. [11.2] clear ip mds forwarding * Clears this linecards MFIB table and resync with the RP. This command is used on the line cards via the line-card console. [11.1(20)CC] ------------------------------------------------------------------------ Exec commands: mrinfo [] [] mrinfo is the MBONE's original tool to determine what neighboring multicast routers are peering with a multicast router. cisco has supported responding to mrinfo requests since release 10.2. Now you can query a multicast router using the mrinfo exec command. If is not used, the router queries itself. Otherwise, the DNS name or IP address of the multicast router is queried. The output format is identical to the mrouted version. If is specified, that is the source address used on mrinfo requests. When it is omitted, the source address is based on the outbound interface for the destination. [11.0] mtrace [] [] mtrace is a multicast traceroute. It allows you to trace the path from a source to a destination branch for a multicast distribution tree for a given group. The trace traverses in the reverse direction from destination to source. This allows you to isolate multicast routing failures. When is not specified, 224.2.0.1 is used. This is the group used for "MBone Audio". When is not specified, the mtrace starts from the system that the command is typed from. is required and can be a DNS name or the IP address of a multicast capable source. and can also take DNS names. When no parameters are entered, the router will interactively ask you for the parameters. [11.0] mstat [] [] The form of Unix mtrace that reports packet rate/loss information. Takes the same input as mtrace. [11.0] ping You can send ICMP Echo Requests to a multicast group address. When you supply , a single Echo Request packet is sent. When you type ping with no arguments, you will be prompted. [10.2] ------------------------------------------------------------------------ MBGP Router subcommands: [All in 11.1(20)CC] [no] neighbor remote-as [nlri unicast | multicast] Configures a BGP peer and associated AS number. If the "multicast" keyword only is supplied, only multicast NLRI will be sent to the neighbor. Counterwise, if the "unicast" keyword only is supplied, only unicast NLRI will be sent to the neighbor. Both keywords may be supplied which indicates the neighbor will be sent both types of routes. Unicast NLRI will be sent in the conventional encoding and the multicast NLRI will be send in the MP_REACH and MP_UNREACH path attribute. The default is to send unicast NLRI only. This version of BGP will negotiate NLRI in the Capabilities Option of the Open message. Therefore, both sides of a BGP connection must be configured consistently with respect to NLRI or the TCP connection will not be established. [no] neighbor peer-group [nlri unicast | multicast] Configures the peer-group to support either unicast NLRI, multicast NLRI or both. Supplying the both keywords "unicast" and "multicast" indicates both NLRI are sent. The default value is unicast only. [no] neighbor description Configures a user supplied description string for the neighbor. [no] neighbor dont-capability-negotiate This hidden command configures whether Capability Parameter negotiation in BGP Open messages are used. By default, capability negotiation is performed. This command is used to interoperate with older MBGP implementations in which no Capability Parameters are used in Open messages between multicast peers. This command is not applicable when peering between two unicast-only BGP neighbors. This command will eventually go away. [no] distance mbgp For configuring adminstrative distance for MBGP routes. is the distance for external routes, is the distance for internal routes, and is the distance for local routes. The default values are the same as for BGP. [no] network
[mask ] [nlri unicast | multicast] Determines if network in the AS should be injected into the BGP unicast RIB or the MBGP multicast RIB. If both keywords "unicast" and "multicast" are specified, it is injected in both RIBs. If "multicast" is specified, it is injected in the multicast RIB only. The default is unicast only. [no] aggregate-address
[nlri unicast | multicast] This command, used with the keyword "multicast" indicates if the aggregate should be applied to the multicast RIB. If the keyword is not supplied, then it applies to the unicast RIB. If you want it to apply to both RIBs, enter the both keywords "unicast" and "multicast". [no] redistribute dvmrp [route-map ] Configures redistribution of DVMRP routes into MBGP. If you supply a route-map, you can specify various BGP attribute settings. ------------------------------------------------------------------------ MBGP route-map subcommands: [All in 11.1(20)CC] [no] match nlri unicast | multicast The route-map criteria can be based on the unicast or multicast RIB (or both). If the multicast RIB entry is being processed for a route-map with a "match nlri multicast", then the route-map condition will yield true, likewise for the unicast corrolary. If both keywords "unicast" and "multicast" are specified, then either RIB entry being processed will yield TRUE. The default value is both. This command can be used in conjunction with the "neighbor
route-map in" command so you can use one route-map reference to describe filtering policies for different NLRI types. [no] set nlri unicast | multicast If the route-map match criteria is met, decide if the route should be injected into the unicast or multicast RIB. If both keywords "unicast" and "multicast" are specified, the route is injected into both RIBs and advertised as separate NLRI in a BGP Update message. If "multicast" is specified, the route is injected only into the multicast RIB. The default value is unicast only in all cases accept when this route-map is referenced by a "neighbor route-map out" command. This route-map subcommand is used when referencing a route-map by various router subcommands (i.e. like "redistribute", "aggregate-address", and neighbor outbound route-map references). This command can be used in conjunction with the "neighbor
default-originate route-map ". If the "set nlri" is supplied in the route-map referenced by the neighbor command, the multicast default route can be generated independent of the unicast default route. ------------------------------------------------------------------------ MSDP commands: [All in 12.0S] Global Commands: [no] ip msdp peer [connect-source ] [remote-as ] Configures an MSDP peer. If you are also BGP peering with with this MSDP peer, you should use the same IP address for MSDP as you do for BGP. However, you are not required to run BGP/MBGP with the MSDP peer as long as there is a BGP/MBGP path between the MSDP peers. If there is not, you are required to use "ip msdp default-peer" command. The keyword "connect-source" is used to supply a source IP address for the TCP connection. The primary address configured on is used. When the "remote-as" keyword is used, you can specify the AS number of the MSDP peer. This is only used for display purposes. There are cases where a peer may appear to be in another AS (other than the one it really resides in) when you MSDP peer but don't BGP peer with it. In this case, if the prefix of the peer is injected by another AS, it is displayed as the peer's AS number (and is misleading). [no] ip msdp description This command adds a descriptive text string to the configuration for the peer . You can see this description when doing NV command generation or via the "show ip msdp peer" command. [no] ip msdp shutdown This command adminstratively shuts down a configured peer. This command is used when you want to configure many MSDP commands for the same peer and don't want the peer to go active. This command could also be used if a MSDP session needs to be shut down for a period of time without losing configuration information for the peer. [no] ip msdp sa-filter out [list ] [route-map ] [rp-list | rp-route-map ] Configures outgoing filter list for Source-Active messages sent to MSDP peer . The default setting is all SA messages received are forwarded to the peer. is an extended access-list that can describe source/group pairs to pass through the filter. If route-map is specified, you can filter based on match criteria in . If all match criteria is true, a permit from the route-map will pass routes through the filter. A deny will filter routes. If both keywords are used, all conditions must be true to pass/filter any (S,G) in outgoing SA messages. If neither are specified, all source/group pairs are filtered. [12.0S, 1.0T] With the rp-list and rp-route-map arguments it is possible to filter SA messages based on the announcing RP address contained in the SA message. This allows to filter messages based on their origin even after they may have already transited one or more other MSDP speakers. [12.0(11)S, 12.1(2)T, 12.1(2)E, CSCdp44032] [no] ip msdp sa-filter in [list ] [route-map ] [rp-list | rp-route-map ] Configures incoming filter list for Source-Active messages received from MSDP peer . The default setting is all SA messages are received. is an extended access-list that can describe source/group pairs to pass through the filter. If route-map is specified, you can filter based on match criteria in . If all match criteria is true, a permit from the route-map will pass routes through the filter. A deny will filter routes. If both keywords are used, all conditions must be true to pass/filter any (S,G) in incoming SA messages. If neither are specified, all source/group pairs are filtered. [12.0S, 1.0T] With the rp-list and rp-route-map arguments it is possible to filter SA messages based on the announcing RP address contained in the SA message. This allows to filter messages based on their origin even after they may have already transited one or more other MSDP speakers. [12.0(11)S, 12.1(2)T, 12.1(2)E, CSCdp44032] [no] ip msdp sa-limit Configure this command to limit the overall number of SA messages the router will accept from MSDP peer . The router keeps a per-peer count of MSDP SA messages in his SA cache and will ignore new messages from a peer if the configured limit for that peer is reached. If the router receives SA messages in excess of the configured limit from an MSDP peer, it generates a rate-limited (once a minute) syslog message: %MSDP-4-SA_LIMIT: SA from peer 172.12.0.1, RP 172.1.0.1 for (1 72.1.0.45, 234.1.1.1) exceeded sa-limit of 40 The "ip msdp sa-limit" command was introduced as a mean of protection against (distributed) denial of service attacks (DoS-attacks). It is recommended to configure "ip msdp sa-limit" on all peerings. An appropriately low SA limit should be configured on peerings with a stub MSDP region (eg: a peer that may have some further downstream peers but that will not transit SA messages from the rest of the Internet). A high SA limit should be configured with all transit MSDP peerings. The commands "show ip msdp summary" and "show ip msdp count" have been enhanced to show the number of SA learned from each peer, "show ip msdp peer" has been enhanced to show the count and the limit if configured [12.0(15)S, 12.1(7), 12.2(2)T, 12.2(3), 12.2S, CSCdt19258]. [no] ip msdp sa-request This informs the router to request SA messages from the peer when a new joiner for the group becomes active. The default setting if this command is not used, is to not send any SA-Request messages. [no] ip msdp filter-sa-request [list ] Configures if the router should honor SA request messages from the peer for groups described by simple access-list . The defalut setting if this command is not used, is that all SA-Request messages from peer are honored. If is not specified, all SA-Request messges are ignored. [no] ip msdp ttl-threshold Configures what multicast data packets are sent in data-encapsulated SA messages. When is configured, only multicast packets with IP header TTL greater than or equal to are sent to the peer . The default value is 0. [no] ip msdp redistribute [list ] [asn ] [route-map ] Configures what (S,G) entries from the multicast routing table are advertised in SA messages to MSDP peers. By default only local sources are advertised provided they send to groups this system is RP for or for all groups if "ip msdp border" command is used. If "list " is used, you can further filter what local sources are advertised (and to what groups they send to) by using the extended access-list where you can supply a source address, source mask, group address and group mask. If "asn " is used alone, you can advertise all sources sending to any group which match the reference to a "ip as-path access-list " command. If "asn 0" is used, sources from all ASes are advertised. This is useful when connecting dense-mode domains to a sparse-mode domain running MSDP. Or when you use MSDP in a router that isn't configured with BGP (and therefore you don't know if a source is local or not). If "route-map " is used, you advertise all sources that satisfy the match criteria from route-map . When all keywords are used, all conditions must be true before any multicast source is advertised in an SA message. When you specify "ip msdp redistribute", no multicast sources are advertised. This command is used for SA message origination and not for SA message forwarding. If you want to filter what SA messages are forwarded from one peer to another, use the "ip msdp sa-filter" command. [no] ip msdp cache-sa-state [list rp-list rp-route-map ] This command is obsolete. In all current and recommended IOS images, caching of MSDP SA messages is mandatory and can not be manually enabled or disabled. "ip msdp cache-sa-state" will automatically be NVgened if at least one MSDP peer is configured. It can not be unconfigured but will be removed automatically when the last MSDP peer is removed from the configuration [12.0(14)ST, 12.0(15)S, 12.1(7), 12.2, CSCdr93446]. If you need to run an older version of IOS and can not immediately upgrade, enable "ip msdp cache-sa-state" without further arguments to achieve best operations and interoperability of MSDP. [no] ip msdp default-peer [prefix-list ] Defines a previously configured peer from which MSDP SA messages may come from. This command is used when you are not MBGP/BGP peering with an MSDP peer. If "prefix-list " is not specified, all SA messages received from the configured default-peer are accepted. If "prefix-list " is specified, SA messages originated from RPs covered by prefix-list will be accepted from the configured default-peer. If is specified, and there is no prefix-list configured, the default-peer will be used for all prefixes. You can enter multiple commands with the either the "prefix-list" keyword or without the "prefix-list" keyword, however, all commands must either have the keyword or all must not have the keyword. When you use multiple "ip msdp default-peer" commands without the "prefix-list" keyword, you use a single active peer to accept all SA messages. If that peer goes down, then you move to the next configured default-peer to accept all SA messages. This is typically used at a stub site. When you use multiple "ip msdp default-peer" commands with the "prefix-list" keyword, you use all the default-peers at the same time for different RP prefixes. This is typically used inside at a service provider cloud which connects stub site clouds. When you have a single peer configured, you don't need to use a default-peer command since there is only a single place to accept SA messages from (and you can't cause an SA forwarding loop). [no] ip msdp border sa-address Configures a MSDP border function which is used in a router that borders a sparse-mode region with a dense-mode region. If you want the router to send SA messages for sources active in the dense-mode region, use this command. The IP address on is used as RP address in SA messages so MSDP peers can forward SA messages away from this border. [no] ip msdp originator-id Allows a MSDP speaker, which originates an SA message, to use the IP address associated with as the RP address in the SA message. If this command is used with the "ip msdp border" command, the originator-id address will be used. [no] ip msdp mesh-group Configures an MSDP peer to be a member of a mesh-group. A mesh group is a group of MSDP speakers which have fully meshed MSDP connectivity between one another. Any SA messages received from a peer in a mesh-group are not forwarded to other peers in the same mesh-group. Mesh groups are useful in two scenarios, 1) to reduce SA message flooding, and 2) to simplify peer-RPF flooding (no need to run MBGP/BGP amoung MSDP peers). Debug Commands: [un]debug ip msdp [] [detail] [routes] Enables debugging MSDP protocol activity. If is specified, debug events for that peer only are logged. When keyword "detail" is specified, more detail debugging is enabled. When keyword "routes" is specified, SA message contents are displayed. [un]debug ip msdp resets Enables debugging of MSDP peer reset reasons. This cannot be used with other forms of "debug ip msdp" parameters described above. Show Commands: show ip msdp summary Displays MSDP peer status. A "*" in front of the peer address column indicates a default peer. Example output: sjck-rp1>sh ip msdp summary MSDP Peer Status Summary Peer Address AS State Uptime/ Reset SA Peer Name Downtime Count Count 192.135.250.116 109 Up 1d10h 9 111 rtp5-rp1 *144.228.240.253 1239 Up 14:24:00 5 4010 sl-rp-stk 172.17.253.19 109 Up 12:36:17 5 10 shinjuku-rp1 172.17.170.110 109 Up 1d11h 9 12 ams-rp1 The "SA Count" column was introduced in IOS images supporting the "ip msdp sa-limit" command [12.0(15)S, 12.1(7), 12.2(2)T, 12.2(3), 12.2S, CSCdt19258]. show ip msdp peer [] Displays detail information about the MSDP peer. If is not supplied, all peers are displayed. In images supporting the "ip msdp sa-limit" command, the output will also display the number of SA messages learned from each peer and, if configured, the sa-limit for that peer [12.0(15)S, 12.1(7), 12.2(2)T, 12.2(3), 12.2S, CSCdt19258]. Example output: sjck-rp1>sh ip msdp peer MSDP Peer 192.135.250.116 (rtp5-rp1.cisco.com), AS 109 (configured AS) Description: Connection status: State: Up, Resets: 9, Connection source: Loopback2 (204.69.199.17) Uptime(Downtime): 1d10h, Messages sent/received: 436765/429062 Output messages discarded: 0 Connection and counters cleared 1w2d ago SA Filtering: Input (S,G) filter: none, route-map: none Input RP filter: none, route-map: none Output (S,G) filter: none, route-map: none Output RP filter: none, route-map: none SA-Requests: Input filter: none Sending SA-Requests to peer: disabled Peer ttl threshold: 0 SAs learned from this peer: 32, SAs limit: 500 Input queue size: 0, Output queue size: 0 show ip msdp sa-cache [] [] [] Displays (S,G) state learned from MSDP peers. State is cached only when "ip msdp cache-sa-state" is configured. When is specified, only state originated by AS number is displayed. When two addresses (or names) are specified, an (S,G) entry corresponding to those addresses is displayed. Otherwise, a single group address can be specified to display all sources for that group. show ip msdp count [] When SA caching is enabled, this command displays the number of sources and groups originated in SA messages from each AS. In images supporting the "ip msdp sa-limit" command, the output will also display the number of SA messages learned from each peer [12.0(15)S, 12.1(7), 12.2(2)T, 12.2(3), 12.2S, CSCdt19258]. Example output: sjck-rp1>show ip msdp count SA State per Peer Counters, : <# SA learned> 192.135.250.116: 24 144.228.240.253: 3964 172.17.253.19: 10 172.17.170.110: 11 SA State per ASN Counters, : <# sources>/<# groups> Total entries: 4009 ?: 198/98, 9: 1/1, 14: 107/57, 17: 7/5 18: 4/3, 25: 23/17, 26: 39/27, 27: 2/2 32: 19/7, 38: 2/1, 52: 4/4, 57: 1/1 68: 4/4, 73: 12/8, 81: 19/1, 87: 9/6 ... Clear Commands: clear ip msdp peer Clears TCP connection for peer . Also resets message counters. clear ip msdp sa-cache [] Clears SA cache entry (if SA caching is enabled) for 1) all entries, 2) all sources for a specific group, or 3) all a specific source/group pair. clear ip msdp statistics [] Clears statistics counters of one or all MSDP peers without reseting the sessions. The counters cleared include the reset count and the input/output packet count. ------------------------------------------------------------------------