53-1003085-02 17 February 2014 FastIron Ethernet Switch IP Multicast Configuration Guide Supporting FastIron Software Release 08.0.
© 2014, Brocade Communications Systems, Inc. All Rights Reserved. Brocade, the B-wing symbol, Brocade Assurance, ADX, AnyIO, DCX, Fabric OS, FastIron, HyperEdge, ICX, MLX, MyBrocade, NetIron, OpenScript, VCS, VDX, and Vyatta are registered trademarks, and The Effortless Network and the On-Demand Data Center are trademarks of Brocade Communications Systems, Inc., in the United States and in other countries. Other brands and product names mentioned may be trademarks of others.
Contents Preface..................................................................................................................................... 7 Document conventions......................................................................................7 Text formatting conventions.................................................................. 7 Command syntax conventions.............................................................. 7 Notes, cautions, and warnings....................................
Enabling IGMP V3 membership tracking and fast leave for the VLAN........................................................................................... 24 Enabling fast leave for IGMP V2....................................................... 25 Enabling fast convergence ...............................................................25 IGMP snooping show commands................................................................. 26 Displaying the IGMP snooping configuration.................................
Configuring the MLD version for individual ports................................ 53 Configuring static groups.................................................................... 53 Configuring static router ports............................................................. 53 Disabling static group proxy................................................................ 53 Enabling MLDv2 membership tracking and fast leave for the VLAN.............................................................................
Initiating PIM multicasts on a network...............................................82 Pruning a multicast tree.................................................................... 82 Grafts to a multicast tree................................................................... 84 PIM DM versions...............................................................................85 Configuring PIM DM .........................................................................85 Failover time in a multi-path topology.
IGMP proxy limitations...................................................................... 144 Configuring IGMP Proxy................................................................... 144 Filtering groups in proxy report messages........................................ 145 Displaying IGMP Proxy information.................................................. 145 IGMP V3........................................................................................................147 Default IGMP version............
Clearing IPv6 MLD traffic................................................................ 206 Clearing the IPv6 MLD group membership table cache................. 206 IPv6 Multicast Boundaries...........................................................................206 Configuration considerations...........................................................207 Configuring multicast boundaries....................................................207 Displaying multicast boundaries................................
Preface ● Document conventions......................................................................................................7 ● Brocade resources............................................................................................................ 9 ● Getting technical help........................................................................................................9 ● Document feedback...................................................................................................
Notes, cautions, and warnings Convention Description value In Fibre Channel products, a fixed value provided as input to a command option is printed in plain text, for example, --show WWN. [] Syntax components displayed within square brackets are optional. Default responses to system prompts are enclosed in square brackets. {x|y|z} A choice of required parameters is enclosed in curly brackets separated by vertical bars. You must select one of the options.
Brocade resources Brocade resources Visit the Brocade website to locate related documentation for your product and additional Brocade resources. You can download additional publications supporting your product at www.brocade.com. • • Adapter documentation is available on the Downloads and Documentation for Brocade Adapters page. Select your platform and scroll down to the Documentation section.
Document feedback Document feedback To send feedback and report errors in the documentation you can use the feedback form posted with the document or you can e-mail the documentation team. Quality is our first concern at Brocade and we have made every effort to ensure the accuracy and completeness of this document. However, if you find an error or an omission, or you think that a topic needs further development, we want to hear from you.
About This Guide ● Introduction..................................................................................................................... 11 ● What’s new in this document.......................................................................................... 11 ● How command information is presented in this guide.....................................................12 Introduction This guide includes procedures for configuring the software.
How command information is presented in this guide How command information is presented in this guide For all new content, command syntax and parameters are documented in a separate command reference section at the end of the publication. In an effort to provide consistent command line interface (CLI) documentation for all products, Brocade is in the process of preparing standalone Command References for the IP platforms.
IPv4 Multicast Traffic Reduction ● Supported IPv4 Multicast Traffic Reduction.................................................................... 13 ● IGMP snooping overview................................................................................................ 13 ● IGMP snooping configuration..........................................................................................17 ● IGMP snooping show commands...................................................................................
Queriers and non-queriers membership information by processing the IGMP reports and leave messages, so traffic can be forwarded to ports receiving IGMP reports. An IPv4 multicast address is a destination address in the range of 224.0.0.0 to 239.255.255.255. Addresses of 224.0.0.X are reserved. Because packets destined for these addresses may require VLAN flooding, devices do not snoop in the reserved range.
VLAN-specific configuration multiple devices are configured as queriers, Brocade recommends that only one device (preferably the one with the traffic source) is configured as a querier. The non-queriers always forward multicast data traffic and IGMP messages to router ports which receive IGMP queries or PIM hellos. Brocade recommends that you configure the device with the data traffic source (server) as a querier.
MAC-based forwarding implementation on FastIron X Series devices On both switch and router software images, IGMP snooping is either *,G based or S,G based. The hardware can either match the group address only (* G), or both the source and group (S, G) of the data stream. This is 32-bit IP address matching, not 23-bit multicast MAC address 01-00-5e-xx-xx-xx matching. When any port in a VLAN is configured for IGMP v3, the VLAN matches both source and group (S, G) in hardware switching.
IGMP snooping configuration • • • • • • • • • A user can configure static router ports to force all multicast traffic to these specific ports. If a VLAN has a connection to a PIM-enabled port on another router, the VLAN must be configured as a non-querier (passive). When multiple snooping devices connect together and there is no connection to PIM ports, one device must be configured as a querier (active).
IGMP snooping mcache entries and group addresses • • • • • • • • Configuring the IGMP mode for a VLAN (active or passive) Disabling IGMP snooping on a VLAN Configuring the IGMP version for a VLAN Configuring static router ports Turning off static group proxy Enabling IGMP V3 membership tracking and fast leave for the VLAN Enabling fast leave for IGMP Enabling fast convergence Perform the following port-specific IGMP snooping task: • Configuring the IGMP version for individual ports in a VLAN IGMP snoop
Setting the maximum number of IGMP group addresses Setting the maximum number of IGMP group addresses The configured number of IGMP group addresses is the upper limit of an expandable database. Client memberships exceeding the group limit are not processed. Configure the system-max igmp-snoopgroup-addr command to define the maximum number of IGMP group addresses.
Configuring the global IGMP mode this case, enable the active IGMP mode on only one of the devices and leave the other devices configured for passive IGMP mode. • Passive - When passive IGMP mode is enabled, it forwards reports to the router ports which receive queries. IGMP snooping in the passive mode does not send queries. However, it forwards queries to the entire VLAN. Configuring the global IGMP mode To globally set the IGMP mode to active, enter the following command.
Configuring the IGMP version for individual ports in a VLAN Configuring the IGMP version for individual ports in a VLAN You can specify the IGMP version for individual ports in a VLAN. For example, the following commands configure ports 4, 5, and 6 to use IGMP V3. The other ports either use the IGMP version specified with the multicast version command, or the globally-configured IGMP version.
Disabling IGMP snooping on a VLAN Disabling IGMP snooping on a VLAN When IGMP snooping is enabled globally, you can still disable it for a specific VLAN. For example, the following commands cause IGMP snooping to be disabled for VLAN 20. This setting overrides the global setting.
Configuring report control Configuring report control A device in passive mode forwards reports and leave messages from clients to the upstream router ports that are receiving queries. You can configure report control to rate-limit report forwarding within the same group to no more than once every 10 seconds. This rate-limiting does not apply to the first report answering a group-specific query. NOTE This feature applies to IGMP V2 only. The leave messages are not rate limited.
Enabling or disabling error and warning messages Enabling or disabling error and warning messages The device prints error or warning messages when it runs out of software resources or when it receives packets with the wrong checksum or groups. These messages are rate-limited. You can turn off these messages by entering the following command.
Enabling fast leave for IGMP V2 device immediately stops forwarding traffic to the interface. This feature requires the entire VLAN be configured for IGMP V3 with no IGMP V2 clients. If a client does not send a report during the specified group membership time (the default is 260 seconds), that client is removed from the tracking list. Every group on a physical port keeps its own tracking record. However, it can only track group membership; it cannot track by (source, group).
IGMP snooping show commands Syntax: multicast fast-convergence IGMP snooping show commands This section describes the show commands for IGMP snooping. Displaying the IGMP snooping configuration To display the global IGMP snooping configuration, enter the show ip multicast command at any level of the CLI. device#show ip multicast Summary of all vlans.
Displaying IGMP snooping errors Field Description rtr port The router ports, which are the ports receiving queries. Displaying IGMP snooping errors To display information about possible IGMP errors, enter the show ip multicast error command. device#show ip multicast error snoop SW processed pkt: 173, up-time 160 sec Syntax: show ip multicast error The following table describes the output from the show ip multicast error command.
Displaying IGMP snooping mcache information group: 226.1.1.1, EX, permit 0 (source, life): life=120, deny 0: If the tracking and fast leave features are enabled, you can display the list of clients that belong to a particular group by entering the following command. device#show ip multicast group 224.1.1.1 tracking Display group 224.1.1.1 in all interfaces with tracking enabled.
Displaying software resource usage for VLANs System Parameters igmp-snoop-mcache Default 512 Maximum 8192 Current 300 Configured 300 The IGMP snooping mcache contains multicast forwarding information for VLANs. To display information in the multicast forwarding mcache, enter the show ip multicast mcache command. device#show ip multicast mcache Example: (S G) cnt=: cnt is number of SW processed packets OIF: e1/22 TR(1/32,1/33), TR is trunk, e1/32 primary, e1/33 output vlan 10, 1 caches.
Displaying the status of IGMP snooping traffic Field Description alloc The allocated number of units. in-use The number of units which are currently being used. avail The number of available units. get-fail This displays the number of resource failures. NOTE It is important to pay attention to this field. limit The upper limit of this expandable field. The limit of multicast group is configured by the system-max igmp-snoop-group-addr command.
Displaying querier information Field Description Qry General Query QryV2 Number of general IGMP V2 queries received or sent. QryV3 Number of general IGMP V3 queries received or sent. G-Qry Number of group-specific queries received or sent. GSQry Number of group source-specific queries received or sent. Mbr The membership report. MbrV2 The IGMP V2 membership report. MbrV3 The IGMP V3 membership report. IsIN Number of source addresses that were included in the traffic.
Displaying the active interface with no other querier present Displaying the active interface with no other querier present The following example shows the output in which the VLAN interface is active and no other querier is present with the lowest IP address.
Displaying the passive interface with other querier present 1/1/16 has 4 groups, This interface is Querier default V2 group: 226.6.6.6, life = 240 group: 228.8.8.8, life = 240 group: 230.0.0.0, life = 240 group: 224.4.4.4, life = 240 1/1/24 has 1 groups, This interface is Querier default V2 group: 228.8.8.8, life = 240 2/1/16 has 4 groups, This interface is Querier default V2 group: 226.6.6.6, life = 240 group: 228.8.8.8, life = 240 group: 230.0.0.0, life = 240 group: 224.4.4.
Clear commands for IGMP snooping default V2 **** Warning! has V3 (age=0) nbrs group: 234.4.4.4, life = 260 group: 226.6.6.6, life = 260 3/1/1 has 4 groups, This interface is non-Querier (passive) default V2 group: 238.8.8.8, life = 260 group: 228.8.8.8, life = 260 group: 230.0.0.0, life = 260 group: 224.4.4.4, life = 260 3/1/4 has 1 groups, This interface is non-Querier (passive) Querier is 10.8.8.8 Age is 0 Max response time is 100 default V2 **** Warning! has V3 (age=0) nbrs group: 236.6.6.
Clearing IGMP counters on VLANs Clearing IGMP counters on VLANs To clear IGMP snooping on error and traffic counters for all VLANs, enter the clear ip multicast counters command. device#clear ip multicast counters Syntax: clear ip multicast counters Disabling the flooding of unregistered IPv4 multicast frames in an IGMP-snooping-enabled VLAN NOTE Disabling the flooding of unregistered IPv4 multicast frames in an IGMP-snooping-enabled VLAN is supported only on ICX 6650 devices.
IPv4 Multicast Traffic Reduction device receives a join message or group membership report for a group, the device forwards subsequent traffic for that group only on the ports from which the join messages or IGMP reports were received. In this example, the router connected to the receiver for group 239.255.162.1 sends a join message toward the group source.
Configuration notes and limitations for PIM SM snooping NOTE This example assumes that the devices are actually Brocade devices running Layer 2 Switch software. FIGURE 1 PIM SM traffic reduction in Global Ethernet environment The devices on the edge of the Global Ethernet cloud are configured for IGMP snooping and PIM SM traffic snooping. Although this application uses multiple devices, the feature has the same requirements and works the same way as it does on a single device.
PIM SM snooping configuration NOTE Use the passive mode of IGMP snooping instead of the active mode. The passive mode assumes that a router is sending group membership queries as well as join and prune messages on behalf of receivers. The active mode configures the device to send group membership queries. • • All the device ports connected to the source and receivers or routers must be in the same portbased VLAN.
Enabling PIM SM snooping on a VLAN This command enables PIM SM traffic snooping. The PIM SM traffic snooping feature assumes that the network has routers that are running PIM SM. NOTE The device must be in passive mode before it can be configured for PIM SM snooping. To disable the feature, enter the no ip pimsm-snooping command. device(config)#no ip pimsm-snooping If you also want to disable IP multicast traffic reduction, enter the no ip multicast command.
Displaying PIM SM snooping information on a Layer 2 switch 2 1 (age=60) 1 has 1 src: 10.20.20.66(60) (* 230.2.2.2) has 1 pim join ports out of 1 OIF 1 (age=60) 1 has 1 src: 10.20.20.66(60) This output shows the number of PIM join OIF out of the total OIF. The join or prune messages are source-specific. In this case, If the mcache is in (* G), the display function will also print the traffic source information.
Displaying PIM SM snooping information for a specific group or source group pair Field Description Multicast Group The IP address of the multicast group. NOTE The fid and camindex values are used by Brocade Technical Support for troubleshooting. Forwarding Port The ports attached to the group receivers. A port is listed here when it receives a join message for the group, an IGMP membership report for the group, or both.
IPv4 Multicast Traffic Reduction Field Description 42 age The age of the port, in seconds. src The source address and age. The age (number of seconds) is indicated in brackets immediately following the source.
IPv6 Multicast Traffic Reduction ● IPv6 Multicast Traffic Reduction......................................................................................43 ● MLD snooping overview..................................................................................................43 ● MLD snooping configuration........................................................................................... 48 ● Displaying MLD snooping information........................................................................
Support for MLD snooping and Layer 3 IPv6 multicast routing together on the same device ports without going through the CPU. If there is no client report, the hardware resource drops the data stream. MLD protocols provide a way for clients and a device to exchange messages, and allow the device to build a database indicating which port wants what traffic.
Forwarding mechanism in hardware Forwarding mechanism in hardware IP-based forwarding implementation on FCX and ICX devices The following information about *,G or S,G fdb-based implementation is specific to FCX, ICX 6610, ICX 6430, ICX 6450, and ICX 6650 devices. On both switch and router software images, MLD snooping is either *,G based or S,G based. The hardware can either match the group address only (* G), or both the source and group (S, G) of the data stream.
MLD snooping configuration notes and feature limitations is unable to install resources for a specific matching address due to hashing collision. The hardware hashes addresses into available entries, with some addresses hashed into the same entry. If the collision number in an entry is more than the hardware chain length, the resource cannot be installed.
MLD snooping-enabled queriers and non-queriers Because Brocade does not support MRD, this can lead to stream loss when non-Querier router ports age out on the Querier after the initial Query election. To avoid such stream loss, configure a static router port on the querier on each interface that connects to a non-querier snooping device.
MLD and VLAN configuration MLD and VLAN configuration You can configure MLD snooping on some VLANs or all VLANs. Each VLAN can be independently enabled or disabled for MLD snooping, or can be configured with MLDv1 or MLDv2. In general, the IPv6 MLD snooping commands apply globally to all VLANs except those configured with VLANspecific MLD snooping commands. VLAN-specific MLD snooping commands supersede global IPv6 MLD snooping commands.
Configuring the hardware and software resource limits Configuring the hardware and software resource limits The system supports up to 8K of hardware-switched multicast streams. The following are the resource limits: • • • • • The default is 512 for most devices; for ICX 6430 devices the default is 256. FCX, FSX, ICX 6610, ICX 6450 and ICX 6650 devices support up to 8192 MLD snooping mcache entries. ICX 6430 devices support up to 2048 MLD snooping mcache entries.
Modifying the age interval Omitting both the active and passive keywords is the same as entering ipv6 multicast passive . NOTE The ipv6 mld-snooping command is replaced by the ipv6 multicast command; the mld-snooping command is replaced by the multicast6 command. Modifying the age interval When the device receives a group membership report, it makes an entry in the MLD group table for the group in the report.
Configuring report control Configuring report control When a device is in passive mode, it forwards reports and leave messages from clients to the upstream router ports that are receiving queries. You can configure report control to rate-limit report forwarding for the same group to no more than once per 10 seconds. This rate limiting does not apply to the first report answering a group-specific query. NOTE This feature applies to MLDv1 only. The leave messages are not rate limited.
Disabling error and warning messages Disabling error and warning messages Error or warning messages are printed when the device runs out of software resources or when it receives packets with the wrong checksum or groups. These messages are rate limited. You can turn off these messages by entering the ipv6 multicast verbose-off command.
Configuring the MLD version for individual ports Configuring the MLD version for individual ports You can specify the MLD version for individual ports in a VLAN. For example, the following commands configure ports 1/4, 1/5, 1/6 and 2/1 to use MLDv2. The other ports use the MLD version specified with the multicast6 version command, or the globally configured MLD version.
Enabling MLDv2 membership tracking and fast leave for the VLAN Syntax: [no] multicast6 proxy-off By default, MLD snooping proxy is enabled. Enabling MLDv2 membership tracking and fast leave for the VLAN MLDv2 provides membership tracking and fast leave services to clients. In MLDv1, only one client per interface must respond to a router queries; leaving some clients invisible to the router, which makes it impossible for the device to track the membership of all clients in a group.
Enabling fast convergence Enabling fast convergence In addition to periodically sending general queries, an active (querier) device sends out general queries when it detects a new port. However, since it does not recognize the other device port-up event, the multicast traffic might still use the query-interval time to resume after a topology change.
Displaying MLD group information Displaying MLD group information To display default, maximum, current, and configured values for system maximum parameters, use the show default values command. The following output example does not show complete output; it shows only MLD group values. Device(config)#show default values System Parameters Default Maximum MLD-snoop-group-addr 4096 8192 Current 5000 Configured 5000 To display MLD group information, enter the show ipv6 multicast group command.
Displaying MLD snooping mcache information Field Description ST Yes indicates that the MLD group was configured as a static group; No means it was learned from reports. QR Yes means the port is a querier port; No means it is not. A port becomes a non-querier port when it receives a query from a source with a lower source IP address than the port. life The number of seconds the group can remain in EXCLUDE mode.
IPv6 Multicast Traffic Reduction Field Description (abcd:ef50 0:100): The lowest 32 bits of source and group. It is displayed in XXXX:XXXX hex format. Here XXXX is a 16-bit hex number. cnt The number of packets processed in software. OIF Output interfaces. age The mcache age in seconds. The mcache is reset to 0 if traffic continues to arrive, otherwise it is aged out when it reaches the time defined by ipv6 multicast mcache-age. uptime The up time of this mcache in seconds.
Displaying status of MLD snooping traffic Field Displays get-mem The current memory allocation. This number should continue to increase. size The size of a unit (in bytes). init The initial allocated amount of memory. NOTE This number can be increased. (More memory can be allocated if necessary.) Available vidx The output interface (OIF) port mask used by mcache. The entire device has a maximum of 4096 vidx. Different mcaches with the same OIF share the same vidx.
Displaying MLD snooping information by VLAN Field Description MbrV2 The MLDv2 membership report. IsIN Number of source addresses that were included in the traffic. IsEX Number of source addresses that were excluded in the traffic. ToIN Number of times the interface mode changed from EXCLUDE to INCLUDE. ToEX Number of times the interface mode changed from INCLUDE to EXCLUDE. ALLO Number of times additional source addresses were allowed on the interface.
Clearing MLD snooping counters and mcache Field Description QR Indicates that the port is a querier. Clearing MLD snooping counters and mcache The clear commands for MLD snooping should only be used in troubleshooting situations or when recovering from error conditions. Clearing MLD counters on all VLANs To clear MLD snooping error and traffic counters on all VLANs, enter the clear ipv6 multicast counters command.
Disabling the flooding of unregistered IPv6 multicast frames in an MLD-snooping-enabled VLAN Disabling the flooding of unregistered IPv6 multicast frames in an MLD-snooping-enabled VLAN NOTE Disabling the flooding of unregistered IPv6 multicast frames in an MLD-snooping-enabled VLAN is supported only on ICX 6650 devices. To disable the flooding of unregistered IPv6 multicast frames in an MLD-snooping-enabled VLAN, use the ipv6 multicast disable-flooding command in global configuration mode.
IPv6 Multicast Traffic Reduction Notice that the receiver for group ff1e::3:4 is directly connected to the device. As a result, the device does not see a join message on behalf of the client. However, because MLD snooping also is enabled, the device uses the MLD group membership report from the client to select the port for forwarding traffic to group ff1e::3:4 receivers. The MLD snooping feature and the PIM6 SM traffic snooping feature together build a list of groups and forwarding ports for the VLAN.
Configuration notes and limitations for PIM6 SM snooping NOTE This example assumes that the devices are actually Brocade devices running Layer 2 Switch software. FIGURE 2 PIM6 SM traffic reduction in Global Ethernet environment The devices on the edge of the Global Ethernet cloud are configured for MLD snooping and PIM6 SM traffic snooping. Although this application uses multiple devices, the feature has the same requirements and works the same way as it does on a single device.
PIM6 SM snooping configuration • • All the device ports connected to the source and receivers or routers must be in the same portbased VLAN. The PIM6 SM snooping feature assumes that the group source and the device are in different subnets and communicate through a router. The source must be in a different IP subnet than the receivers. A PIM6 SM router sends PIM join and prune messages on behalf of a multicast group receiver only when the router and the source are in different subnet.
Enabling PIM6 SM snooping on a VLAN To disable PIM6 SM snooping, enter the no ipv6 pimsm-snooping command. device(config)#no ipv6 pimsm-snooping If you also want to disable IP multicast traffic reduction, enter the no ipv6 multicast command. device(config)#no ipv6 multicast Syntax: [no] ipv6 pimsm-snooping Enabling PIM6 SM snooping on a VLAN Perform the following steps to enable PIM6 SM snooping on a VLAN. 1.
Displaying PIM6 SM snooping for a VLAN 2 1/1/2 2/1/3 (0:16 2/1/3 1/1/2 has 1 src: 15::11(0), has 1 src: 15::11(0), 1:3) has 2 pim join ports out of 2 OIF (age=0), 1/1/2 (age=0), has 1 src: 15::16(0), This output shows the number of PIM join OIF out of the total OIF. The join or prune messages are source-specific. In this case, If the mcache is in (* G), the display function will also print the traffic source information.
Displaying PIM6 SM snooping for a VLAN 68 FastIron Ethernet Switch IP Multicast Configuration Guide 53-1003085-02
IPv4 Multicast Protocols ● Supported IPv4 Multicast Protocols features.................................................................. 69 ● Overview of IP multicasting.............................................................................................71 ● Support for Multicast Multi-VRF...................................................................................... 71 ● Changing global IP multicast parameters.......................................................................
IPv4 Multicast Protocols Feature ICX 6430 ICX 6450 FCX ICX 6610 ICX 6650 FSX 800 FSX 1600 ICX 7750 PMRI No 08.0.011 08.0.01 08.0.01 08.0.01 08.0.01 08.0.10 PIM-SSM No 08.0.011 08.0.01 08.0.01 08.0.01 08.0.01 08.0.10 Multi-VRF support No 08.0.011 08.0.01 08.0.01 08.0.01 08.0.01 08.0.10 IP Multicast Boundaries No 08.0.011 08.0.01 08.0.01 08.0.01 08.0.01 08.0.10 PIM Dense No 08.0.011 08.0.01 08.0.01 08.0.01 08.0.01 08.0.10 PIM Sparse No 08.0.011 08.0.01 08.
Overview of IP multicasting Overview of IP multicasting Multicast protocols allow a group or channel to be accessed over different networks by multiple stations (clients) for the receipt and transmission of multicast data. Distribution of stock quotes, video transmissions such as news services and remote classrooms, and video conferencing are all examples of applications that use multicast routing.
Show and clear command support The following new runtime commands have been introduced: max-mcache This command is described in the “Defining the maximum number of PIM cache entries” section. ip igmp max-group-address This command, which is described in the “Defining the maximum number of IGMP group ” section, addresses replaces the system-max igmp-max-group-address command.
Defining the maximum number of PIM cache entries Defining the maximum number of PIM cache entries You can use the following run-time command to define the maximum number of repeated PIM traffic being sent from the same source address and being received by the same destination address. To define this maximum for the default VRF, enter the following commands.
Changing IGMP V1 and V2 parameters Changing IGMP V1 and V2 parameters IGMP allows Brocade devices to limit the multicast of IGMP packets to only those ports on the device that are identified as IP Multicast members. The device actively sends out host queries to identify IP Multicast groups on the network, inserts the group information in an IGMP packet, and forwards the packet to IP Multicast neighbors.
Security enhancement for IGMP Syntax:[no] ip igmp max-response-time num The num variable specifies the number of seconds and can be a value from 1 to 25. The default is 10. Security enhancement for IGMP A security enhancement was made to IGMPv2 to comply with the following recommendation of RFC 2236: “Ignore the Report if you cannot identify the source address of the packet as belonging to a subnet assigned to the interface on which the packet was received.
Multicast non-stop routing To display static multicast groups in the default VRF, enter the following command. device#show ip igmp static Group Address Interface Port List ---------------------------------224.2.2.2 v1 ethe 5/2 Syntax: show ip igmp [ vrf vrf_name ] static The vrf parameter allows you to display static IGMP groups for the VRF instance specified by the vrf_name variable.
Displaying the multicast NSR status Syntax: ip multicast-nonstop-routing During a hitless upgrade and switchover, this syslog message is generated on the CLI. The message displayed depends on which version of PIM is configured.
Passive multicast route insertion The vrf parameter allows you to display IP PIM counters for the VRF instance specified by the vrfname variable. The following table displays the output from the show ip pim counter nsr command. This field... Displays... Mcache sync The mcache NSR sync queue that carries the NSR sync message for mcache updates. pack The number of NSR sync messages that are packed from the active module to the standby module.
Configuring PMRI Configuring PMRI PMRI is enabled by default. To disable PMRI, enter commands such as the following. device(config)# router pim device(config-pim-router)# hardware-drop-disable Syntax: [no] hardware-drop-disable Displaying hardware-drop Use the show ip pim sparse command to display if the hardware-drop feature has been enabled or disabled.
Configuring multicast boundaries • • When a boundary is applied to an ingress interface, all packets destined to a multicast group that is filtered out will be dropped by software. Currently, there is no support to drop such packets in hardware. The ip multicast-boundary command may not stop clients from receiving multicast traffic if the filter is applied on the egress interface up-stream from RP.
PIM Dense |Address | | |Address Port|Thr|Boundary | | Prio | Interval ---------+---------------+----+---+-----------------------+---+---------+------+------+---------+ e1/1/7 30.0.0.1 SM Ena Itself 1 None default 1 3000ms Total Number of Interfaces : 1 Syntax: show ip pim [vrf vrf-name ] interface [ethernet port-number | loopback num | ve num | tunnel num ] The vrf keyword allows you to display multicast boundary information for the VRF instance identified by the vrf-name variable.
Initiating PIM multicasts on a network PIM was introduced to simplify some of the complexity of the routing protocol at the cost of additional overhead tied with a greater replication of forwarded multicast packets. PIM builds source-routed multicast delivery trees and employs reverse path check when forwarding multicast packets. There are two modes in which PIM operates: Dense and Sparse. The Dense Mode is suitable for densely populated multicast groups, primarily in the LAN environment.
IPv4 Multicast Protocols sends a prune message to R1. With R4 in a prune state, the resulting multicast delivery tree would consist only of leaf nodes R2 and R3.
Grafts to a multicast tree Grafts to a multicast tree A PIM device restores pruned branches to a multicast tree by sending graft messages towards the upstream device. Graft messages start at the leaf node and travel up the tree, first sending the message to its neighbor upstream device. In the preceding example, if a new 229.255.0.1 group member joins on device R6, which was previously pruned, a graft is sent upstream to R4.
PIM DM versions PIM DM versions The Brocade device supports only PIM V2. PIM DM V2 sends messages to the multicast address 224.0.0.13 (ALL-PIM-ROUTERS) with protocol number 103. Configuring PIM DM NOTE This section describes how to configure the "dense" mode of PIM, described in RFC 1075. Refer to Configuring PIM Sparse on page 96 for information about configuring PIM Sparse. Enabling PIM on the device and an interface By default, PIM is disabled. To enable PIM: • • • Enable the feature globally.
Modifying PIM global parameters The [no] router pim vrf command behaves in the following manner: • • Entering the router pim vrf command to enable PIM does not require a software reload. Entering a no router pim vrf command removes all configuration for PIM multicast on the specified VRF. Enabling a PIM version To enable PIM on an interface, globally enable PIM, then enable PIM on interface 3, enter the following commands.
IPv4 Multicast Protocols The default is 105 seconds. The range is 3 to 65535 seconds. Modifying hello timer This parameter defines the interval at which periodic hellos are sent out PIM interfaces. Devices use hello messages to inform neighboring devices of their presence. The interval can be set between 10 and 3600 seconds, and the default rate is 30 seconds. To apply a PIM hello timer of 120 seconds to all ports on the device operating with PIM, enter the following.
Failover time in a multi-path topology Modifying graft retransmit timer The graft retransmit timer defines the interval between the transmission of graft messages. A graft message is sent by a device to cancel a prune state. When a device receives a graft message, the device responds with a Graft Ack (acknowledge) message. If this Graft Ack message is lost, the device that sent the graft message will resend it. To change the graft retransmit timer from the default of 180 to 90 seconds, enter the following.
Configuring a DR priority Configuring a DR priority The DR priority option lets you give preference to a particular device in the DR election process by assigning it a numerically higher DR priority. This value can be set for IPv4 interfaces.
Displaying all multicast cache entries in a pruned state Field Description Inactivity interval How long a forwarding entry can remain unused before the device deletes it. Hardware Drop Enabled Displays Yes if the Passive Multicast Route Insertion feature is enabled and No if it is not. Prune Wait Interval The amount of time a PIM device waits before stopping traffic to neighbor devices that do not want the traffic. The value can be from zero to three seconds. The default is three seconds.
IPv4 Multicast Protocols IP Multicast Mcache Table Entry Flags : SM - Sparse Mode, SSM - Source Specific Multicast, DM - Dense Mode RPT - RPT Bit, SPT - SPT Bit, LSRC - Local Source, LRCV - Local Receiver HW - HW Forwarding Enabled, FAST - Resource Allocated, TAG - Need For Replication Entry REGPROB - Register In Progress, REGSUPP - Register Suppression Timer MSDPADV - Advertise MSDP, NEEDRTE - Route Required for Src/RP, PRUN - DM Prune Upstream Interface Flags: IM - Immediate, IH - Inherited, WA - Won Ass
IPv4 Multicast Protocols TABLE 1 Output fields from the show ip pim mcache command (Continued) Field Description BF Blocked Filter BI Blocked IIF Uptime Shows the software entry uptime. Rate Shows the total number of packets per second that have been forwarded using the hardware programmed forwarding entry (the (S,G) entry programmed in hardware or (*,G) entries if (*,G) based forwarding is enabled). The rate is displayed for all entries when the fwd_fast flag is set on the active module.
IPv4 Multicast Protocols TABLE 1 Output fields from the show ip pim mcache command (Continued) Field Description AgeSltMsk Shows the slot number on which active module expects ingress traffic. This value is 1 if the entry is programmed in hardware and is 0 if the entry is not programmed in hardware. L2 FID Hardware Resource allocated for the traffic switched to receivers in the ingress VLAN. DIT Hardware Resource allocated for router receivers.
Displaying information across VRFs TABLE 1 Output fields from the show ip pim mcache command (Continued) Field Description Flags (explanation of flags in the OIF section) Shows the flags set in each of the Outgoing interface in abbreviated string format whose explanations are as follows.
PIM Sparse bsr Bootstrap router flow-count Show flowcache counters hw-resource PIM hw resources interface PIM interface neighbor PIM neighbor states resource PIM resources rp-set List of rendezvous point (RP) candidates traffic Active multicast traffic PIM Sparse Brocade devices support Protocol Independent Multicast (PIM) Sparse version 2. PIM Sparse provides multicasting that is especially suitable for widely distributed multicast environments. The Brocade implementation is based on RFC 2362.
RP paths and SPT paths • • • PMBR - A PIM device that has some interfaces within the PIM domain and other interface outside the PIM domain. PBMRs connect the PIM domain to the Internet. BSR - The Bootstrap Router (BSR) distributes RP information to the other PIM Sparse devices within the domain. Each PIM Sparse domain has one active BSR. For redundancy, you can configure ports on multiple devices as candidate BSRs.
Current limitations ‐ ‐ ‐ Identify the Brocade device as a candidate PIM Sparse Bootstrap Router (BSR), if applicable. Identify the Brocade device as a candidate PIM Sparse Rendezvous Point (RP), if applicable. Specify the IP address of the RP (if you want to statically select the RP). NOTE It is recommended that you configure the same Brocade device as both the BSR and the RP.
Configuring PIM interface parameters • • Entering the router pim vrf command to enable PIM does not require a software reload. Entering a no router pim vrf command removes all configuration for PIM multicast on the specified VRF. Configuring PIM interface parameters After you enable IP multicast routing and PIM Sparse at the global level, you must enable it on the individual interfaces connected to the PIM Sparse network. To enable PIM Sparse mode on an interface, enter commands such as the following.
Configuring RPs The numhash-mask-length variable specifies the number of bits in a group address that are significant when calculating the group-to-RP mapping. You can specify a value from 1 to 32. NOTE it is recommended that you specify 30 for IP version 4 (IPv4) networks. The priority variable specifies the BSR priority. You can specify a value from 0 to 255. When the election process for BSR takes place, the candidate BSR with the highest priority becomes the BSR. The default is 0.
IPv4 Multicast Protocols add a range, you override the default. The device then becomes a candidate RP only for the group address ranges you add. You also can delete the configured rp-candidate group ranges by entering the following command. device(config-pim-router)# rp-candidate delete 224.126.22.0 24 Syntax: [no] rp-candidate delete group-addr mask-bits The usage of the group-addrmask-bits parameter is the same as for the rp-candidate add command.
ACL based RP assignment ACL based RP assignment The rp-address command allows multiple static rendezvous point (RP) configurations. For each static RP, an ACL can be given as an option to define the multicast address ranges that the static RP permit or deny to serve. A static RP by default serves the range of 224.0.0.0/4 if the RP is configured without an ACL name. If an ACL name is given but the ACL is not defined, the static RP is set to inactive mode and it will not cover any multicast group ranges.
PIM Passive ------------------------------------------1 225.1.1.1 25.0.0.25 2 225.1.1.2 25.0.0.25 3 225.1.1.3 25.0.0.25 4 225.1.1.4 25.0.0.25 5 225.1.1.5 25.0.0.25 PIM Passive PIM Passive is used to reduce and minimize unnecessary PIM Hello and other PIM control messages. PIM Passive allows you to specify that the interface is "passive" in regards to PIM.
Displaying system values NOTE IPv4 multicast routes do not share hardware replication table entries with IPv6 multicast routes even if they share the same OIF lists. Displaying system values To display default, maximum, current, and configured values for system maximum parameters, use the show default values command. The following output example does not show complete output; it shows only PIM hardware mcache values.
IPv4 Multicast Protocols Total hw w/Tag MVID entries 0 Total hw w/Tag invalid MVID entries 0 Syntax: show ip pim [all-vrf | [ vrf vrf-name ] ] resource The vrf parameter allows you to display hardware resource information for the VRF instance identified by the vrf-name variable. The following table displays the output from the show ip pim resource command. TABLE 2 Output from the show ip pim resource command Field Description Num alloc Number of VRF instances allocated.
Displaying PIM Sparse configuration information and statistics TABLE 3 Output from the show ip pim all-vrf hw-resource command Field Description VRF Name of the VRF. Usage Number of allocated SG entries in this VRF. Fail Number of failures while allocating SG entries in this VRF (due to the system-max limit. Total usage Total number of SG entries in the system (all VRFs). System-max limit for SG entries Configured system limit for pim-hw-mcache.
IPv4 Multicast Protocols The vrf keyword allows you to display PIM sparse configuration information for the VRF instance identified by the vrf-name variable. This example shows the PIM Sparse configuration information on PIM Sparse device A in Figure 5 on page 95. The following table shows the information displayed by the show ip pim sparse command. TABLE 4 Output of the show ip pim sparse command This field... Displays...
Displaying a list of multicast groups TABLE 4 Output of the show ip pim sparse command (Continued) This field... Displays... Bootstrap Msg interval How frequently the BSR configured on the device sends the RP set to the RPs within the PIM Sparse domain. The RP set is a list of candidate RPs and their group prefixes. The group prefix of a candidate RP indicates the range of PIM Sparse group numbers for which it can be an RP.
Displaying BSR information Group member at e2/9: v59 Group member at e1/16: v57 3 Group 226.0.120.0 Group member at e2/9: v59 Group member at e1/16: v57 4 Group 226.0.163.0 Group member at e2/9: v59 Group member at e1/16: v57 5 Group 226.0.206.0 Group member at e2/9: v59 Group member at e1/16: v57 6 Group 226.0.249.0 Group member at e2/9: v59 Group member at e1/16: v57 7 Group 226.0.30.
IPv4 Multicast Protocols This example shows information displayed on a device that has been elected as the BSR. The next example shows information displayed on a device that is not the BSR. Notice that some fields shown in the example above do not appear in the example below device(config)#show ip pim bsr PIMv2 Bootstrap information for Vrf Instance : default-vrf ---------------------------------------------------------------------------BSR address: 1.51.51.1. Hash Mask Length 32. Priority 255.
Displaying candidate RP information TABLE 6 Output from the show ip pim bsr command (Continued) This field... Displays... RP Indicates the IP address of the Rendezvous Point (RP). NOTE This field appears only if this device is a candidate BSR. group prefixes Indicates the multicast groups for which the RP listed by the previous field is a candidate RP. NOTE This field appears only if this device is a candidate BSR.
Displaying RP-to-group mappings TABLE 7 Output from the show ip pim rp-candidate command This field... Displays... Candidate-RP-advertisement Indicates how time will pass before the BSR sends the next RP message. The time in is displayed in "hh:mm:ss" format. NOTE This field appears only if this device is a candidate RP. RP Indicates the IP address of the Rendezvous Point (RP). NOTE This field appears only if this device is a candidate RP.
Displaying RP Information for a PIM Sparse group TABLE 8 Output of the show ip pim rp-map command This field... Displays... Group address Indicates the PIM Sparse multicast group address using the listed RP. RP address Indicates the IP address of the Rendezvous Point (RP) for the listed PIM Sparse group. Displaying RP Information for a PIM Sparse group To display RP information for a PIM Sparse group, enter the following command at any CLI level. device# show ip pim rp-hash 239.255.162.1 RP: 207.95.
Displaying multicast neighbor information Number of group prefixes Learnt from BSR: 1 Group prefix = 224.0.0.0/4 # RPs expected: 2 # RPs received: 2 RP 1: 1.51.51.1 priority=0 age=60 holdtime=150 RP 2: 1.51.51.3 priority=0 age=30 holdtime=150 Syntax: show ip pim [ vrf vrf-name ] rp-set The vrf option allows you to display the RP set list for the VRF instance identified by the vrf-name variable. The following table describes the output from this command.
Displaying the PIM multicast cache The vrf option allows you to display information about the PIM neighbors for the VRF instance identified by the vrf-name variable. The following table describes the output from this command. TABLE 11 Output from the show ip pim vrf neighbor command This field... Displays... Port The interface through which the device is connected to the neighbor. Phyport When there is a virtual interface, this is the physical port to which the neighbor is connected.
IPv4 Multicast Protocols e4/29(VL13), 00:03:12/0, Flags: MJ e5/2(VL1004), 00:03:12/0, Flags: MJ L2 (HW) 1: e5/2, 00:00:07/0, Flags: MJ L2 MASK: ethe 5/2 Src-Vlan: 1001 Syntax: show ip pim [vrf vrf-name ] mcache [source-address | group-address | counts | dense | ditidx dit-idx | g_entries | receiver | sg_entries | sparse | ssm] The vrf option allows you to display the PIM multicast cache for the VRF instance identified by the vrfname variable.
IPv4 Multicast Protocols TABLE 12 Output fields from the show ip pim mcache command (Continued) Field Description upstream neighbor Shows the upstream neighbor for the Source/RP based on the type of entry. For (*,G) it shows the upstream neighbor towards the RP. For (S,G) entries it shows the upstream neighbor towards the source. Flags Flags Represent Entry flags in hex format in the braces. And indicates the meaning of the flags set in abbreviated string whose explanations are as below.
Displaying the PIM multicast cache for DIT TABLE 12 Output fields from the show ip pim mcache command (Continued) Field Description Profile Shows the Profile ID associated with the Stream. Number of matching entries Shows the total number of mcache entries matching a particular multicast filter specified. Outgoing interfaces Section This section consists of three parts. L3 OIFs, L2OIFs and Blocked OIFs.
Clearing the PIM forwarding cache HW - HW Forwarding Enabled, FAST - Resource Allocated, TAG - Need For Replication Entry REGPROB - Register In Progress, REGSUPP - Register Suppression Timer MSDPADV - Advertise MSDP, NEEDRTE - Route Required for Src/RP, PRUN - DM Prune Upstream Interface Flags: IM - Immediate, IH - Inherited, WA - Won Assert MJ - Membership Join, MI - Membership Include, ME - Membership Exclude BR - Blocked RPT, BA - Blocked Assert, BF - Blocked Filter, BI Blocked IIF Total entries in mcac
IPv4 Multicast Protocols ------+---------+-----------+---------+---------+---------+---------+---------+--v30 0 0 0 0 0 0 0 0 v50 2526 1260 0 0 0 1263 0 0 v150 2531 0 0 0 0 1263 0 0 v200 2531 0 0 0 0 1 0 0 Port HELLO JOIN-PRUNE ASSERT REGISTER REGISTER BOOTSTRAP CAND. RP Err GRAFT(DM) STOP(SM) MSGS (SM) ADV.
Clearing the PIM message counters NOTE If you have configured interfaces for standard PIM (dense mode) on the device, statistics for these interfaces are listed first by the display. The following table describes the output for this show command. TABLE 13 Output from the show ip pim vrf traffic command This field... Displays... Port The port or virtual interface on which the PIM interface is configured. Hello The number of PIM Hello messages sent or received on the interface.
Displaying PIM RPF Displaying PIM RPF The show ip pim rfp command displays what PIM sees as the reverse path to the source as shown in the following. While there may be multiple routes back to the source, the one displayed by this command is the one that PIM thinks is best. device# show ip pim vrf eng rpf 130.50.11.10 Source 130.50.11.10 directly connected on e4/1 Syntax: show ip pim [vrf vrf-name ] rpf ip-address The ip-address variable specifies the source address for RPF check.
Peer Reverse Path Forwarding (RPF) flooding information with other PIM Sparse domains by communicating with RPs in other domains that are running MSDP. The RP sends the source information to each peer through a Source Active message. The message contains the IP address of the source, the group address to which the source is sending, and the IP address of the RP. In this example, the Source Active message contains the following information: • • • Source address: 206.251.14.22 Group address: 232.1.0.
Configuring MSDP Configuring MSDP To configure MSDP, perform the following tasks: • • Enable MSDP. Configure the MSDP peers. NOTE The PIM Sparse Rendezvous Point (RP) is also an MSDP peer. NOTE Devices that run MSDP usually also run BGP. The source address used by the MSDP device is normally configured to be the same source address used by BGP. Enabling MSDP To enable MSDP, enter the following command.
Disabling an MSDP peer The connect-source loopbacknum parameter specifies the loopback interface you want to use as the source for sessions with the neighbor and must be reachable within the VRF. NOTE It is strongly recommended that you use the connect-source loopback num parameter when issuing the msdp-peer command. If you do not use this parameter, the device uses the IP address of the outgoing interface.
Filtering MSDP source-group pairs device(config)# router msdp vrf blue device(config-msdp-router-vrf blue)# originator-id loopback 2 device(config-msdp-router-vrf blue)# exit Syntax: [no] originator-id type number The originator-id command instructs MSDP to use the specified interface IP address as the IP address of the RP in an SA message. This address must be the address of the interface used to connect the RP to the source. The default address used is the RP IP address.
IPv4 Multicast Protocols device(config)# route-map msdp2_map permit 1 device(config-routemap msdp2_map)# match ip address 125 device(config-routemap msdp2_map)# exit device(config)# route-map msdp2_rp_map deny 1 device(config-routemap msdp2_rp_map)# match ip route-source 124 device(config-routemap msdp2_rp_map)# exit device(config)# route-map msdp2_rp_map permit 2 device(config-routemap msdp2_rp_map)# match ip route-source 125 device(config-routemap msdp2_rp_map)# exit The following commands configure the
Filtering advertised Source-Active messages Filtering advertised Source-Active messages The following example configures the device to advertise all source-group pairs except the ones that have source address 10.x.x.x. The following commands configure extended ACLs to be used in the route map definition. device(config)# access-list 123 permit ip 10.0.0.0 0.255.255.
IPv4 Multicast Protocols KA: Keepalive SA:Source-Active NOT: Notification Peer Address Peer As State KA In Out 40.40.40.1 1001 ESTABLISH 59 59 40.40.40.3 1001 ESTABLISH 59 59 47.1.1.2 N/A ESTABLISH 59 59 Brocade(config)# In 0 0 0 SA Out 0 0 0 In 0 0 0 NOT Out 0 0 0 Age 6 47 47 Syntax: show ip msdp summary The following table describes the output from this command. TABLE 14 MSDP summary information This field... Displays...
IPv4 Multicast Protocols TotalRcv: 49 RcvQue: Input SA Filter:Not Applicable Input (S,G) route-map:None Input RP route-map:None Output SA Filter:Not Applicable Output (S,G) route-map:None Output RP route-map:None 0 SendQue: 0 Syntax: show ip msdp [vrf vrf-name ] peer The following table describes the output from this command. TABLE 15 MSDP peer information This field... Displays...
IPv4 Multicast Protocols TABLE 15 MSDP peer information (Continued) This field... Displays... Notification Message Error Code Received The MSDP device has received a notification message from the neighbor that contains an error code corresponding to one of the following errors. Some errors have subcodes that clarify the reason for the error.
IPv4 Multicast Protocols TABLE 15 MSDP peer information (Continued) This field... Displays... TCP connection state The state of the connection with the neighbor. Can be one of the following: • LISTEN - Waiting for a connection request. • SYN-SENT - Waiting for a matching connection request after having sent a connection request. • SYN-RECEIVED - Waiting for a confirming connection request acknowledgment after having both received and sent a connection request.
IPv4 Multicast Protocols TABLE 15 MSDP peer information (Continued) This field... Displays... TotalRcv The number of sequence numbers received from the neighbor. RcvQue The number of sequence numbers in the receive queue. SendQue The number of sequence numbers in the send queue. Displaying Source Active cache information To display the Source Actives in the MSDP cache, use the following command.
Displaying MSDP RPF-Peer TABLE 16 MSDP source active cache (Continued) This field... Displays... Orig Peer The peer from which this source-active entry was received. Age The number of seconds the entry has been in the cache You can use the following command to filter the output to display only the entries matching a specific source. device#show ip msdp sa-cache 1.1.1.1 You can use the following command to filter the output to display only the entries matching a specific group.
Displaying MSDP Peer Displaying MSDP Peer To display MSDP peer information, enter the following command. Brocade# show ip msdp peer 40.40.40.3 MSDP Peer Status Summary KA: Keepalive SA:Source-Active NOT: Notification Peer Address Peer As State KA SA NOT Age In Out In Out In Out 40.40.40.3 1001 ESTABLISH 62 62 0 0 0 0 7 Brocade# Syntax: show ip msdp peer peer-addr Displaying MSDP VRF RPF-Peer To display MSDP peer information for a specific VRF, enter the following command.
Configuring MSDP mesh groups Clearing the source active cache To clear the source active cache, enter the following command at the Privileged EXEC level of the CLI. device# clear ip msdp sa-cache Syntax: clear ip msdp sa-cache [ ip-addr ] The command in this example clears all the cache entries. Use the ip-addr variable to clear only the entries matching either a source or a group.
Configuring MSDP mesh group mesh group. An RP can forward an SA message to any MSDP router as long as that peer is farther away from the originating RP than the current MSDP router. The following figure shows an example of an MSDP mesh group. In a PIM-SM mesh group the RPs are configured to be peers of each other. They can also be peers of RPs in other domains. FIGURE 7 Example of MSDP mesh group PIM Sparse Domain 1 in Figure 7 contains a mesh group with four RPs. When the first RP, for example, RP 206.
MSDP Anycast RP Syntax: [no] mesh-group group-name peer-address The sample configuration above reflects the configuration in Figure 7 on page 136. On RP 206.251.21.31 you specify its peers within the same domain (206.251.18.31, 206.251.19.31, and 206.251.20.31). You first configure the MSDP peers using the msdp-peer command to assign their IP addresses and the loopback interfaces. Next, place the MSDP peers within a domain into a mesh group. Use the mesh-group command. There are no default mesh groups.
Example NOTE The anycast RP address *must* not be the IGP router-id. • • • • Enable PIM-SM on all interfaces on which multicast routing is desired. Enable an IGP on each of the loopback interfaces and physical interfaces configured for PIM-SM. Configure loopback interfaces with unique IP addresses on each of the RPs for MSDP peering. This loopback interface is also used as the MSDP originator-id.
IPv4 Multicast Protocols The configuration examples demonstrate the commands required to enable this application. FIGURE 8 Example of a MDSP Anycast RP network RP 1 configuration The following commands provide the configuration for the RP 1 router in Figure 8 . RP1(config)#router ospf RP1(config-ospf-router)# area 0 RP1(config-ospf-router)# exit RP1(config)# interface loopback 1 RP1(config-lbif-1)# ip ospf area 0 RP1(config-lbif-1)# ip ospf passive RP1(config-lbif-1)# ip address 10.0.0.
IPv4 Multicast Protocols RP1(config)# router pim RP1(config-pim-router)# rp-candidate loopback 1 RP1(config-pim-router)# exit RP1(config)# router msdp RP1(config-msdp-router)# msdp-peer 10.1.1.2 connect-source loopback 2 RP1(config-msdp-router)# originator-id loopback 2 RP 2 configuration The following commands provide the configuration for the RP 2 router in Figure 8 .
PIM Anycast RP PIMR2 configuration The following commands provide the configuration for the PIMR2 router in Figure 8 . PIMR2(config)#router ospf PIMR2(config-ospf-router)# area 0 PIMR2(config-ospf-router)# exit PIMR2(config)# interface ethernet 1/2 PIMR2(config-if-e1000-1/2)# ip ospf area 0 PIMR2(config-if-e1000-1/2)# ip ospf cost 5 PIMR2(config-if-e1000-1/2)# ip address 192.5.2.
Displaying information for a PIM Anycast RP interface as a router-id. A PIM First Hop router will register the source with the closest RP. The first RP that receives the register will re-encapsulate the register to all other Anycast RP peers. Please refer to Figure 9 as described in the configuration of PIM Anycast RP 100.1.1.1. device(config)#interface loopback 2 device(config-lbif-2)#ip address 100.1.1.
Static multicast routes The following table describes the parameters of the show ip pim anycast-rp command: TABLE 17 Display of show ip pim anycast-rp This field... Displays... Number of Anycast RP: The Number of Anycast RP specifies the number of Anycast RP sets in the multicast domain. Anycast RP: The Anycast RP address specifies a shared RP address used among multiple PIM routers. ACL ID: The ACL ID specifies the ACL ID assigned. ACL Name The ACL Name specifies the name of the Anycast RP set.
IGMP Proxy Configure the route-precedence command to specify a precedence table that dictates how routes are selected for multicast. IGMP Proxy IGMP Proxy provides a means for routers to receive any or all multicast traffic from an upstream device if the router is not able to run PIM and runs only IGMP. IGMP Proxy supports IGMP v1, v2, and v3. IGMP Proxy enables the router to issue IGMP host messages on behalf of hosts that the router discovered through standard PIM interfaces.
Filtering groups in proxy report messages 1. Configure router PIM globally. 2. Configure an IP address on the interface (physical, virtual routing, or tunnel interface) that will serve as the IGMP proxy for an upstream device by entering commands such as the following. device(config)#router pim device(config)#int e 1/3 device(config-if-e1000-1/3)#ip address 10.95.5.1/24 3. Enable PIM passive on the interface. device(config-if-e1000-1/3)#ip pim passive 4. Enable IGMP Proxy on the interface.
IPv4 Multicast Protocols TABLE 18 Output of show ip igmp proxy Field Description Address Group address. Mode Multicast group mode. Can be "exclude" or "include." Source count Number sources in the given mode. A group in IGMP v2 has exclude mode with zero sources. ref count Number of proxy interfaces where the responses (query, state, change, etc) are scheduled. flags Can be "0" or "1." "1" indicates that the group state has changed and it needs to be reevaluated before a response is generated.
IGMP V3 The report shows the following information. TABLE 20 Output of show ip igmp proxy stats Field Description Intf Interface genQv1 RX IGMP v1 general query received on proxy interface. genQv2 RX IGMP v2 general query received on proxy interface. genQv3 RX IGMP v3 general query received on proxy interface. GrpQ RX Group query received. SrcQ RX Source query received. Rprtv1 TX IGMP v1 report generated. Rprtv2 TX IGMP 2 report generated. Rprtv3 TX IGMP v3 report generated.
Default IGMP version • Address field contains the multicast address of interest, and the Number of Sources (N) field contains zero. A "Group-and-Source-Specific Query" is sent by a multicast router to learn if any neighboring interface desires reception of packets sent to a specified multicast address, from any of a specified list of sources.
Globally enabling the IGMP version An interface or router sends the queries and reports that include its IGMP version specified on it. It may recognize a query or report that has a different version. For example, an interface running IGMP V2 can recognize IGMP V3 packets, but cannot process them. Also, a router running IGMP V3 can recognize and process IGMP V2 packet, but when that router sends queries to an IGMP V2 interface, the downgraded version is supported, no the upgraded version.
Enabling membership tracking and fast leave In this example, the second line sets IGMP V2 on virtual routing interface 3. However, the third line set IGMP V3 on ports 1/3 through 1/7 and port e2/9. All other ports in this virtual routing interface are configured with IGMP V2. Syntax: [no] ip igmp port-version version-number ethernet port-number Enter 1, 2, or 3 for version-number . IGMP V2 is the default version.
Creating a static IGMP group Creating a static IGMP group You can configure one or more physical ports to be a permanent (static) member of an IGMP group based on the range or count. To configure two static groups starting from 226.0.0.1, enter either this command: Device(config)# interface ethernet 1/5 Device(config-if-e1000-1/5)# ip igmp static-group 226.0.0.1 count 2 Or this command: Device(config)# interface ethernet 1/5 Device(config-if-e1000-1/5)# ip igmp static-group 226.0.0.1 to 226.0.0.
Setting the group membership time Setting the group membership time Group membership time defines how long a group will remain active on an interface in the absence of a group report. Possible values are from 5 - 26000 seconds and the default value is 260 seconds. To define an IGMP membership time of 240 seconds, enter the following.
IPv4 Multicast Protocols If the tracking and fast leave feature is enabled, you can display the list of clients that belong to a particular group by entering commands such as the following. device# show ip igmp group 224.1.10.1 tracking Total 2 entries ----------------------------------------------------Idx Group Address Port Intf Mode Timer Srcs ---+----------------+------+------+-------+-----+---1 226.0.0.1 e6/2 v30 exclude 253 3 S: 40.40.40.12 S: 40.40.40.11 S: 40.40.40.10 S: 40.40.40.
Clearing the IGMP group membership table Clearing the IGMP group membership table To clear the IGMP group membership table, enter the following command. device# clear ip igmp cache Syntax: clear ip igmp [vrf vrf-name ] cache This command clears the IGMP membership for the default router instance or for a specified VRF. Use the vrf option to clear the traffic information for a VRF instance specified by the vrf-name variable.
IPv4 Multicast Protocols Enter ve and its number , or ethernet and its port-address to display information for a specific virtual routing interface, or ethernet interface. The tunnelnum parameter specifies a GRE tunnel interface that is being configured. The GRE tunnel interface is enabled under the router PIM configuration. Entering an address for group-address displays information for a specified group on the specified interface.
Clearing IGMP traffic statistics Displaying IGMP traffic status To display the traffic status on each virtual routing interface, enter the following command.
IPv4 Multicast Protocols Syntax: clear ip igmp [ vrf vrf-name] traffic This command clears all the multicast traffic information on all interfaces on the device. Use the vrf option to clear the traffic information for a VRF instance specified by the vrf-name variable. T Displaying IGMP settings To display global IGMP settings or IGMP settings for a specified VRF. To display global IGMP settings, enter the following command.
Source-specific multicast TABLE 25 Output of show ip igmp settings (Continued) This field Displays Last Member Query Interval The Last Member Query Interval is the Max Response Time used to calculate the Max Resp Code inserted into Group-Specific Queries sent in response to Leave Group messages. It is also the Max Response Time used in calculating the Max Resp Code for Group-and-Source-Specific Query messages.
Displaying source-specific multicast configuration information To configure a single SSM group address, enter the following command under the router pim configuration: device(config)#router pim device(config-pim-router)#ssm-enable range 232.1.1.1/8 Syntax: [no] ssm-enable range group-address address-mask The group-address parameter specifies the multicast address for the SSM address range.
Displaying information for PIM SSM range ACL The acl-id/acl-name parameter specifies the ACL id or name used to configure multiple SSM group ranges. To disable the SSM mapping range ACL, use the [no] form of this command. NOTE The ssm-enable rangeacl-id acl-name or command also supports IPv6 traffic. The ssm-enable rangeacl-id acl-name or command must be configured under the IPv6 router pim configuration to support IPv6.
Configuring an ACL for IGMPv2 SSM mapping Configuring an ACL for IGMPv2 SSM mapping You can use either a standard or extended ACL to identify the group multicast address you want to add source addresses to when creating a IGMPv3 report. For standard ACLs, you must create an ACL with a permit clause and the ip-source-address variable must contain the group multicast address. This can be configured directly with a subnet mask or with the host keyword in which case a subnet mask of all zeros (0.0.0.
Displaying an IGMP SSM mapping information Theacl-id variable specifies the ACL ID that contains the group multicast address. The source-address variable specifies the source address that you want to map to the group multicast address specified in the ACL. The no option is used to delete a previously configured SSM map. Example configuration In the following example configuration, one extended ACL and two standard ACLs are defined with group multicast addresses.
IPv6 Multicast Protocols ● Supported IPv6 Multicast Features............................................................................... 163 ● IPv6 PIM Sparse .......................................................................................................... 164 ● PIM Anycast RP............................................................................................................ 194 ● Multicast Listener Discovery and source-specific multicast protocols...........................
IPv6 PIM Sparse IPv6 PIM Sparse IPv6 Protocol Independent Multicast (PIM) Sparse is supported. IPv6 PIM Sparse provides multicasting that is especially suitable for widely distributed multicast environments. In an IPv6 PIM Sparse network, an IPv6 PIM Sparse router that is connected to a host that wants to receive information for a multicast group must explicitly send a join request on behalf of the receiver (host).
RP paths and SPT paths between the receiver and the source (the Shortest Path Tree, or SPT) and uses the SPT for subsequent packets from the source to the receiver. The device calculates a separate SPT for each source-receiver pair. NOTE It is recommended that you configure the same ports as candidate BSRs and RPs. RP paths and SPT paths Figure 10 on page 164 shows two paths for packets from the source for group fec0:1111::1 and a receiver for the group.
IPv6 PIM-Sparse mode NOTE It is recommended that you configure the same device as both the BSR and the RP. IPv6 PIM-Sparse mode To configure a device for IPv6 PIM Sparse, perform the following tasks: • • Identify the Layer 3 switch as a candidate sparse Rendezvous Point (RP), if applicable. Specify the IPv6 address of the RP (to configure statically). The following example enables IPv6 PIM-SM routing. Enter the following command at the configuration level to enable IPv6 PIM-SM globally.
Configuring BSRs Configuring BSRs In addition to the global and interface parameters configured in the prior sections, you must identify an interface on at least one device as a candidate PIM Sparse Bootstrap Router (BSR) and a candidate PIM Sparse Rendezvous Point (RP). NOTE It is possible to configure the device as only a candidate BSR or an RP, but it is recommended that you configure the same interface on the same device as both a BSR and an RP.
Configuring candidate RP The num parameter specifies the number of seconds and can be from 10 - 65535. The default is 60. Use the no option to disable a timer that has been configured. Configuring candidate RP Enter a command such as the following to configure the device as a candidate RP. device(config)# ipv6 router pim device(config-ipv6-pim-router)# rp-candidate ethernet 2/2 To configure the device as a candidate RP for a specified VRF, enter the commands as shown in the following example.
Updating IPv6 PIM Sparse forwarding entries with a new RP configuration If you explicitly specify the RP, the device uses the specified RP for all group-to-RP mappings and overrides the set of candidate RPs supplied by the BSR. NOTE Specify the same IP address as the RP on all IPv6 PIM Sparse routers within the IPv6 PIM Sparse domain. Make sure the device is on the backbone or is otherwise well-connected to the rest of the network.
Changing the Shortest Path Tree threshold To disable embedded RP support for a specified VRF, enter the following commands.
Changing the PIM Join and Prune message interval To specify how frequently the candidate RP configured on the device sends candidate RP advertisement messages to the BSR for a specified VRF, enter commands such as the following. device(config)# ipv6 router pim vrf blue device(config-ipv6-pim-router-vrf-blue)# rp-adv-interval 180 Syntax: rp-adv-interval seconds The seconds parameter specifies the number of seconds in a range from 10 through 65535. The default is 60 seconds.
Setting the prune wait interval Setting the prune wait interval The prune-wait command allows you to set the amount of time the PIM router should wait for a join override before pruning an Outgoing Interface List Optimization (OIF) from the entry. To change the default join override time to 2 seconds, enter commands such as the following.
Setting the inactivity timer To change the default register probe time to 20 seconds, enter commands such as following. device(config)# ipv6 router pim device(config-ipv6-pim-router)# register-probe-time 20 To change the default register probe time to 20 seconds for a specified VRF, enter commands such as the following.
Enabling Source-specific Multicast Enabling Source-specific Multicast Using the Any-Source Multicast (ASM) service model, sources and receivers register with a multicast address. The protocol uses regular messages to maintain a correctly configured broadcast network where all sources can send data to all receivers and all receivers get broadcasts from all sources.
Passive Multicast Route Insertion • • If more than one router has the same DR priority on a subnet (as in the case of default DR priority on all), the router with the numerically highest IP address on that subnet will get elected as the DR. The DR priority information is used in the DR election only if all the PIM routers connected to the subnet support the DR priority option.
Displaying system values Join/Prune interval Hardware Drop Enabled Bootstrap Msg interval Register Suppress Time Register Stop Delay SSM Enabled SSM Group Range Route Precedence Embedded RP Enabled : : : : : : : : : 60 Inactivity interval : Yes Prune Wait Interval : 60 Candidate-RP Msg interval : 60 Register Probe Time : 10 Register Suppress interval : Yes SPT Threshold : ff30::/32 mc-non-default mc-default uc-non-default Yes 180 3 60 10 60 1 uc-default Displaying system values To display default, maxi
IPv6 Multicast Protocols Syntax: show ipv6 pim [ vrf vrf-name ] sparse The vrf parameter allows you to configure IPv6 PIM on the virtual routing instance (VRF) specified by the vrf-name variable. The following table displays the output from the show ipv6 pim sparse command. TABLE 26 Output from the show ipv6 pim sparse command Field Description Global PIM Sparse mode settings Maximum mcache Maximum number of multicast cache entries. Current Count Number of multicast cache entries used.
Displaying IPv6 PIM interface information TABLE 26 Output from the show ipv6 pim sparse command (Continued) Field Description Candidate-RP Msg interval Number of seconds the candidate RP configured on the Layer 3 switch sends candidate RP advertisement messages to the BSR. Default is 60 seconds. Register Suppress Time This is the mean interval between receiving a Register-Stop and allowing registers to be sent again.
Displaying a list of multicast groups Syntax: show ipv6 pim [ vrfvrf-name ] interface [ ethernetslot/portnum | loopbacknum | venum ] The vrf option allows you to display multicast boundary information for the VRF instance identified by the vrf-name variable. The ethernet port-number parameter specifies the physical port. The loopback num parameter specifies the loopback port. The ve num parameter specifies a virtual interface.
Displaying BSR information TABLE 28 Output from the show ipv6 pim group command Field Description Total number of Groups Lists the total number of IPv6 multicast groups the device is forwarding. Group The multicast group address. Group member at Interface name and number. Displaying BSR information To display information on a device that has been elected as the BSR, enter the show ipv6 pim bsr command at the CLI level.
Displaying candidate RP information TABLE 29 Output from the show ipv6 pim bsr command (Continued) Field Description Hash mask length The number of significant bits in the IPv6 multicast group comparison mask. This mask determines the IPv6 multicast group numbers for which the device can be a BSR. The default is 32 bits, which allows the device to be a BSR for any valid IPv6 multicast group number. NOTE This field appears only if this device is a candidate BSR.
Displaying RP-to-group mappings RP: 1be::11:21 group prefixes: ff00:: / 8 Candidate-RP-advertisement period: 60 This example shows information displayed on a device that is a candidate RP. The following example shows the message displayed on a device that is not a candidate RP. device# show ipv6 pim rp-candidate This system is not a Candidate-RP.
Displaying RP information for an IPv6 PIM Sparse group ------------------------------------------------------------------------------1 ff07::c:1 3200:12::32 2 ff07::c:2 3200:12::32 3 ff07::c:3 3200:12::32 Number of group-to-RP mappings: 3 Brocade# Syntax: show ipv6 pim [ vrf vrf-name ] rp-map The vrf parameter allows you to display IPv6 RP-to-group-mappings for the VRF instance identified by the vrf-name variable. The following table displays the output from the show ipv6 rp-map command.
Displaying multicast neighbor information --------Static RP count: 1 100::1 Number of group prefixes Learnt from BSR: 0 No RP-Set present Syntax: show ipv6 pim [ vrf vrf-name ] rp-set The vrf parameter allows you to display the RP set for the VRF instance identified by the vrf-name variable. The following table displays the output from the show ipv6 pim rp-set command.
Displaying the IPv6 PIM multicast cache The vrf parameter allows you to display the IPv6 PIM neighbors for the VRF instance identified by the vrf-name variable. The following table displays the output from the show ipv6 pim neighbor command. TABLE 34 Output from the show ipv6 pim neighbor command Field Description Port The routing interface through which the device is connected to the neighbor. Phyport The physical interface through which the device is connected to the neighbor.
IPv6 Multicast Protocols For Replication Entry REGPROB - Register In Progress, REGSUPP - Register Suppression Timer MSDPADV - Advertise MSDP, NEEDRTE - Route Required for Src/RP, PRUN - DM Prune Upstream Interface Flags: IM - Immediate, IH - Inherited, WA - Won Assert MJ - Membership Join, MI - Membership Include, ME - Membership Exclude BR - Blocked RPT, BA - Blocked Assert, BF - Blocked Filter, BI Blocked IIF Total entries in mcache: 4 1 (*, ff05::4422) RP 2006:1001::1, in v503 (tag e2/1/11), Uptime 1d 0
Displaying IPv6 PIM RPF TABLE 35 Output parameters of the show ipv6 pim mcache command (Continued) Field Description Flags Show the flags associated with the forward entry. slow ports ethe Shows the forwarding port ID of the mcache entry which is in the software forwarding path. AgeSltMsk Shows the slot number on which MP expects ingress traffic. L2 FID Shows the hardware resource allocated for the traffic switched to receivers in the ingress VLAN.
Displaying the IPv6 PIM resources Brocade#show ipv pim vrf eng counter Event Callback: DFTVlanChange : 0 VlanPort : 0 LP to MP IPCs: SM_REGISTER : 8315 MCAST_CREATE : S_G_AGEOUT : 3 WRONG_IF : ABOVE_THRESHOLD: 0 MCAST_FIRST_DATA : SET KAT : 3 SET KAT INFINITY : MP to LP IPCs: INIT : 25 INSERT_VPORT : 30 DELETE_VPORT : 186 DELETE_VIF : 162 MOVE_VPORT : 0 DEL_ENTRY : 16 INSERT_SOURCE : 0 DELETE_SOURCE : 0 RESET_SRC_LIST : 0 MOVE_TNNL_PORT : 0 FLAG_CHANGE : 6 FDB_VIDX_CHANGE: 0 OIF_FLAG_CHANGE :0 Error Counte
IPv6 Multicast Protocols pim/dvm intf.
Displaying PIM traffic statistics System-max limit for SG entries: 6144 Syntax: show ipv6 pim [ all-vrf | [ vrf vrf-name ] ] hw-resource The vrf parameter allows you to display hardware resource information for the VRF instance identified by the vrf-name variable. The following table displays the output from the show ipv6 pim all-vrf hw-resource command. TABLE 38 Output from the show ipv6 pim all-vrf hw-resource command Field Description VRF Name of the VRF.
Clearing the IPv6 PIM forwarding cache TABLE 39 Output from the show ipv6 pim traffic command (Continued) Field Description Join-Prune The number of Join or Prune messages sent or received on the interface. NOTE Unlike PIM dense, PIM Sparse uses the same messages for Joins and Prunes. Assert The number of Assert messages sent or received on the interface. Register Graft (DM) The number of Register messages sent or received on the interface.
Clearing the IPv6 PIM traffic The clear IPv6 pim rp-map command allows you to update the entries in the static multicast forwarding table immediately after making RP configuration changes. This command is meant to be used with rp-address command. To update the entries in an IPv6 PIM Sparse static multicast forwarding table with a new RP configuration, enter the clear ipv6 pim rp-map command at the privileged EXEC level of the CLI.
Configuring a static multicast route within a VRF The system-max pim6-hw-mcache command sets the maximum number of SG entries that are allowed in the hardware. Configuring a static multicast route within a VRF You can configure a static multicast route within a virtual routing instance (VRF). 1. 2. 3. Configure a VRF. Device(config)# vrf vpn1 Configure the VRF address family for IPv6 and enter IPv6 address family configuration mode.
PIM Anycast RP The following examples show how to configure the route precedence and display the route-precedence setting.
IPv6 Multicast Protocols device(config-ipv6-pim-router)# rp-address 1001::1 device(config-ipv6-pim-router)# anycast-rp 1001::1 my-anycast-rp-set-acl To configure PIM Anycast RP for a specified VRF, enter the commands as shown in the following example.
Displaying information for an IPv6 PIM Anycast RP interface Displaying information for an IPv6 PIM Anycast RP interface To display information for an IPv6 PIM Anycast RP interface, enter the show ipv6 pim anycast-rp command.
Enabling MLDv2 The source list and filter mode are created when the IPv6 querier router sends a query. The querier router is the one with the lowest source IPv6 address. It sends out any of the following queries: • • • General query - The querier sends this query to learn all multicast addresses that need to be listened to on an interface. Address specific query - The querier sends this query to determine if a specific multicast address has any listeners.
Defining the maximum number of MLD group addresses To define an MLD group membership time of 2000 seconds for a specified VRF, enter the following commands. device(config)# ipv6 router pim vrf blue device(config-ipv6-pim-router-vrf-blue)# ipv6 mld group-membership-time 2000 Syntax: [no] ipv6 router pim [ vrf vrf-name ] The vrf parameter specifies the virtual routing instance (VRF) specified by the variable vrf-name .
Setting the query interval Setting the query interval You can define the frequency at which MLD query messages are sent. For example, if you want queries to be sent every 50 seconds, enter a command such as the following. device(config)# ipv6 mld query-interval 50 Syntax: [no] ipv6 mld query-interval seconds The seconds variable specifies the MLD query interval in seconds. You can specify from 2 through 3600 seconds. The default value is 125 seconds.
Setting the version To set the robustness for a specified VRF, enter the following commands. device(config)# ipv6 router pim vrf blue device(config-ipv6-pim-router-vrf-blue)# ipv6 mld robustness 3 Syntax: [no] ipv6 router pim [ vrf vrf-name ] The vrf parameter specifies the virtual routing instance (VRF) specified by the variable vrf-name . Setting the version You can use this command to set the MLD version (1 or 2) globally. You can select the version of MLD by entering a command such as the following.
Enabling MLD tracking on an interface To configure two static groups, starting from ff0d::1, without having to receive an MLDv1 report on a virtual Ethernet interface, enter either this command: Device(config-if-e1000-1/5)# ipv6 mld static-group ff0d::1 count 2 Or this command: Device(config-if-e1000-1/5)# ipv6 mld static-group ff0d::1 to ff0d::2 To configure two static groups on virtual ports starting from ff0d::1, enter either this command: Device(config)# interface ve 10 Device(config-vif-10)# ipv6 ml
Displaying MLD group information Displaying MLD group information To display the list of multicast groups, enter a command such as the following.
Displaying MLD settings e1/1/2 v220 e1/1/1 0 0 3 2 2 2 - Self - Self 0 0 No 0 12 No Disabled Syntax: show ipv6 mld [ vrf vrf-name ] interface [ ethernet port-number | ve num ] The vrf parameter allows you to display MLD parameters on an interface for the VRF instance identified by the vrf-name variable. Enter ve and its number, or ethernet and its port address to display MLD information for a specific virtual routing interface or an Ethernet interface.
Displaying static MLD groups Max Response Time : Group Membership Time : Operating Version : Robustness Variable : Last Member Query Interval: Older Host Present Timer : 10s 260s 2 2 1s 260s Configured Version : 0 Last Member Query Count: 2 Syntax: show ipv6 mld [ vrf vrf-name ] settings The vrf parameter specifies that you want to display information for MLD settings for the VRF specified by the vrf-name variable.
Displaying MLD traffic TABLE 44 Output from the show ipv6 mld vrf cs static command Field Description Group Address The address of the multicast group. Interface Port List The physical ports on which the multicast groups are received. Displaying MLD traffic To display information on MLD traffic, enter a command such as the following.
Clearing IPv6 MLD traffic TABLE 45 Output from the show ipv6 mld traffic command (Continued) Field Description Is_EX Number of source addresses that were excluded in the traffic. ToIN Number of times the interface mode changed from exclude to include. ToEX Number of times the interface mode changed from include to exclude. ALLOW Number of times that additional source addresses were allowed or denied on the interface. BLK Number of times that sources were removed from an interface.
Configuration considerations Configuration considerations • • • • • • Only one ACL can be bound to any interface. Normal ACL restrictions apply as to how many software ACLs can be created, but there is no hardware restrictions on ACLs with this feature. Creation of a static MLD client is allowed for a group on a port that may be prevented from participation in the group on account of an ACL bound to the port’s interface.
Displaying multicast boundaries Displaying multicast boundaries To display multicast boundary information, use the show ipv6 pim interface command. In this example, abc is the name of the access list.
IP Multicast Commands ● clear ip mroute.............................................................................................................. 209 ● clear ipv6 mroute...........................................................................................................210 ● ip max-mroute............................................................................................................... 211 ● ip mroute......................................................................................
clear ipv6 mroute Modes Usage Guidelines Examples Privileged EXEC mode After mroutes are cleared from an IP multicast routing table, the best static mroutes are added back to it. This example removes all mroutes from the IP multicast routing table: Device(config)# clear ip mroute This example removes all mroutes from the vrf green IP multicast routing table: Device(config)# clear ip mroute vrf green This example removes mroute 10.0.0.
ip max-mroute ip max-mroute Configures a limit to the number of multicast routes supported. Syntax ip max-mroute num no ip max-mroute Command Default Parameters The default is no limit. num Configures the maximum number of multicast routes supported. Modes Usage Guidelines Examples VRF configuration mode The no form of this command restores the limit to the default value. This example limits the number of multicast routes supported on the VRF named my_vrf to 20.
ip mroute (next hop) Configures a virtual interface as the route path. tunnel num Configures a tunnel interface as the route path. cost Configures a metric for comparing the route to other static routes in the static route table that have the same destination. The range is 1-16; the default is 1. distance distance-value Configures the route's administrative distance. The range is 1-255; the default is 1. name name Name for this static route.
ip mroute next-hop-enable-default Configures a metric for comparing the route to other static routes in the static route table that have the same destination. The range is 1-16; the default is 1. distance distance-value Configures the route's administrative distance. The range is 1-255; the default is 1. name name Name for this static route. Modes Usage Guidelines Examples VRF configuration mode The no form of this command deletes a previously configured next-hop static multicast route.
ip mroute next-hop-recursion ip mroute next-hop-recursion Configures the recursion level while using static mroutes to resolve a static mroute next hop. Syntax ip mroute [ vrf vrf-name ] next-hop-recursion 1-10 no ip mroute [ vrf vrf-name ] next-hop-recursion 1-10 Command Default Parameters The recursion level for resolving a static mroute next hop is 3. vrf vrf-name Configures a static mroute for this virtual routing and forwarding (VRF) route.
ipv6 max-mroute After the hardware forwarding database (FDB) entry is made, the multicast traffic is switched only to the VLAN hosts that are members of the multicast group. This can avoid congestion and loss of traffic on the ports that have not subscribed to this IPv4 multicast traffic. Examples The following example shows the disabling of flooding of unregistered IPv4 multicast frames. Brocade(config)# ip multicast disable-flooding History Release version Command history 08.0.
ipv6 mroute (next hop) Parameters vrf vrf-name Configures a static mroute for this virtual routing and forwarding (VRF) route. ipv6-address-prefix/prefix-length Configures the destination IPv6 address and prefix for which the route should be added. ethernet Configures an Ethernet interface as the route path. ve Configures a virtual interface as the route path. cost Configures a metric for comparing the route to other static routes in the IPv6 static route table that have the same destination.
ipv6 mroute next-hop-enable-default Configures a static mroute for this virtual routing and forwarding (VRF) route. ipv6-address-prefix/prefix-length Configures the destination IPv6 address and prefix for which the route should be added. next-hop address Configures a next-hop address as the route path. cost Configures a metric for comparing the route to other static routes in the static route table that have the same destination. The range is 1-16; the default is 1.
ipv6 mroute next-hop-recursion History Release version Command history 8.0.10a This command was introduced. ipv6 mroute next-hop-recursion Configures the recursion level while using static mroutes to resolve a static mroute next hop. Syntax ipv6 mroute [ vrf vrf-name ] next-hop-recursion 1-10 no ipv6 mroute [ vrf vrf-name ] next-hop-recursion 1-10 Command Default Parameters The recursion level for resolving a static mroute next hop is 3.
route-precedence Usage Guidelines NOTE This command is supported only on ICX 6650 devices. The no form of this command enables the flooding of unregistered IPv6 multicast frames in an MLDsnooping-enabled VLAN. After the hardware forwarding database (FDB) entry is made, the multicast traffic is switched only to the VLAN hosts that are members of the multicast group. This can avoid congestion and loss of traffic on the ports that have not subscribed to this IPv6 multicast traffic.
route-precedence admin-distance You must configure four parameters indicating the four different route types. If you want to specify that a particular route type not be used, configure the none keyword to fill the precedence table. Examples This command specifies a non-default route from the mRTM, then a non-default route from the uRTM, then a default route from the mRTM, and then a default route from the uRTM.
IP Multicast Commands Specifies a VRF route. static Specifies a static multicast route. connected Specifies a directly attached (connected) multicast route. ip-subnet [ mask ] Specifies an IP address. Modes Examples Privileged EXEC mode This example displays information for IP multicast routes: Device(config)# show ip mroute Total number of IP routes: 5 Type Codes - B:BGP D:Connected S:Static; Cost - Dist/Metric Destination Gateway Port Type Uptime 1 20.20.20.0/24 220.220.220.1 ve 220 S 8m54s 2 50.50.
show ip multicast optimization show ip multicast optimization Displays Internet Group Management Protocol (IGMP) snooping hardware resource-sharing information. You can configure it to display the availability of IP multicast (IPMC) group indexes in the hardware and how it is been used and shared. Syntax Parameters show ip multicast optimization [ ipmc ] ipmc Specifies the IPMC group index.
show ipv6 mroute Examples This example displays information for configured multicast routes: Device(config)# show ip static mroute IP Static Routing Table - 2 entries: IP Prefix Next Hop Interface *20.20.20.0/24 220.220.220.1 20.20.20.0/24 50.50.50.2 21.21.21.0/24 1.2.3.4 - History Dis/Metric/Tag 1/1/0 1/2/0 1/1/0 Release version Command history 8.0.10a This command was introduced. Name show ipv6 mroute Displays information on IPv6 multicast routes.
show ipv6 multicast optimization This example displays information for static IPv6 multicast routes: Device(config)# show ipv6 mroute static Type Codes - B:BGP C:Connected S:Static Type IPv6 Prefix Next Hop Router S 1:1::1:0/120 :: Interface ve 90 Dis/Metric 1/1 Uptime 2d16h This example displays information for directly attached (connected) IPv6 multicast routes: Device(config)#show ipv6 mroute connect Type Codes - B:BGP C:Connected S:Static Type IPv6 Prefix Next Hop Router C 2090::/64 :: C 2100::/64
show ipv6 static mroute History Release version Command history 8.0.10 This command was introduced. show ipv6 static mroute Displays information for configured IPv6 multicast routes. Syntax Parameters show ipv6 static mroute [ vrf vrf-name ] ipv6-address-prefix/prefix-length vrf vrf-name Specifies a VRF route. ipv6-address-prefix/prefix-length Specifies an IPv6 address. Modes Usage Guidelines Examples Privileged EXEC mode Only resolved and best static mroutes are added to the mRTM table.
show ipv6 static mroute 226 FastIron Ethernet Switch IP Multicast Configuration Guide 53-1003085-02
Index C clear commands 34 clearing IGMP counters on VLANs 35 clearing the IGMP mcache 34 clearing the mcache on a specific VLAN 34 clearing traffic on a specific VLAN 34 configuration 17 configuring report control 23 disabling on a VLAN 22 displaying mcache information 28 displaying querier information 31 displaying software resource usage for VLANs 29 displaying the status 30 MAC-based implementation on FastIron X series 16 modifying the maximum response time 22 modifying the query interval 22 overview 13
configuration 38, 65 disabling on a VLAN 39, 66 displaying errors 27 displaying information 39, 66 displaying information for a specific group or source group pair 41 displaying information on a Layer 2 switch 40, 67 enabling on a VLAN 39 enabling or disabling 38, 65 show commands show command show ip multicast 26 PIM SM traffic snooping application examples 35, 62 configuration notes and limitations 37, 64 enabling globally on the device 19 global tasks 17 overview 35, 62 port-specific tasks 17 VLAN-spec
