53-1003085-02
17 February 2014
FastIron Ethernet Switch IP
Multicast
Configuration Guide
Supporting FastIron Software Release 08.0.10a
Download from Www.Somanuals.com. All Manuals Search And Download.
Contents
Brocade resources............................................................................................9
FastIron Ethernet Switch IP Multicast Configuration Guide
53-1003085-02
1
Download from Www.Somanuals.com. All Manuals Search And Download.
PIM SM snooping configuration.................................................................... 38
2
FastIron Ethernet Switch IP Multicast Configuration Guide
53-1003085-02
Download from Www.Somanuals.com. All Manuals Search And Download.
VLAN............................................................................................. 54
PIM6 SM traffic snooping overview.................................................................62
Multicast terms....................................................................................71
Multicast non-stop routing...............................................................................76
FastIron Ethernet Switch IP Multicast Configuration Guide
53-1003085-02
3
Download from Www.Somanuals.com. All Manuals Search And Download.
Displaying PIM RPF....................................................................................121
MSDP Anycast RP......................................................................................137
PIM Anycast RP..........................................................................................141
Static multicast routes.................................................................................143
4
FastIron Ethernet Switch IP Multicast Configuration Guide
53-1003085-02
Download from Www.Somanuals.com. All Manuals Search And Download.
PIM Anycast RP............................................................................................194
FastIron Ethernet Switch IP Multicast Configuration Guide
53-1003085-02
5
Download from Www.Somanuals.com. All Manuals Search And Download.
ip mroute (next hop)....................................................................................212
ip multicast disable-flooding........................................................................214
ipv6 mroute next-hop-recursion.................................................................. 218
route-precedence........................................................................................219
show ipv6 mroute........................................................................................223
6
FastIron Ethernet Switch IP Multicast Configuration Guide
53-1003085-02
Download from Www.Somanuals.com. All Manuals Search And Download.
Preface
● Brocade resources............................................................................................................9
Document conventions
The document conventions describe text formatting conventions, command syntax conventions, and
important notice formats used in Brocade technical documentation.
Text formatting conventions
Text formatting conventions such as boldface, italic, or Courier font may be used in the flow of the text
to highlight specific words or phrases.
Format
Description
bold text
Identifies command names
Identifies keywords and operands
Identifies the names of user-manipulated GUI elements
Identifies text to enter at the GUI
italic text
Identifies emphasis
Identifies variables and modifiers
Identifies paths and Internet addresses
Identifies document titles
Courier font
Identifies CLI output
Identifies command syntax examples
Command syntax conventions
Bold and italic text identify command syntax components. Delimiters and operators define groupings of
parameters and their logical relationships.
Convention
bold text
Description
Identifies command names, keywords, and command options.
Identifies a variable.
italic text
FastIron Ethernet Switch IP Multicast Configuration Guide
53-1003085-02
7
Download from Www.Somanuals.com. All Manuals Search And Download.
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.
[ ]
A choice of required parameters is enclosed in curly brackets separated by
vertical bars. You must select one of the options.
{ x | y | z }
In Fibre Channel products, square brackets may be used instead for this
purpose.
A vertical bar separates mutually exclusive elements.
x | y
Nonprinting characters, for example, passwords, are enclosed in angle
brackets.
< >
...
\
Repeat the previous element, for example, member[member...].
Indicates a “soft” line break in command examples. If a backslash separates
two lines of a command input, enter the entire command at the prompt without
the backslash.
Notes, cautions, and warnings
Notes, cautions, and warning statements may be used in this document. They are listed in the order of
increasing severity of potential hazards.
NOTE
A note provides a tip, guidance, or advice, emphasizes important information, or provides a reference
to related information.
ATTENTION
An Attention statement indicates potential damage to hardware or data.
CAUTION
A Caution statement alerts you to situations that can be potentially hazardous to you or cause
damage to hardware, firmware, software, or data.
DANGER
A Danger statement indicates conditions or situations that can be potentially lethal or
extremely hazardous to you. Safety labels are also attached directly to products to warn of
these conditions or situations.
8
FastIron Ethernet Switch IP Multicast Configuration Guide
53-1003085-02
Download from Www.Somanuals.com. All Manuals Search And Download.
Brocade resources
Brocade resources
Visit the Brocade website to locate related documentation for your product and additional Brocade
resources.
•
•
Adapter documentation is available on the Downloads and Documentation for Brocade Adapters
page. Select your platform and scroll down to the Documentation section.
For all other products, select the Brocade Products tab to locate your product, then click the
Brocade product name or image to open the individual product page. The user manuals are
available in the resources module at the bottom of the page under the Documentation category.
register at no cost to obtain a user ID and password.
Getting technical help
You can contact Brocade Support 24x7 online, by telephone, or by e-mail.
For product support information and the latest information on contacting the Technical Assistance
Use one of the following methods to contact the Brocade Technical Assistance Center.
Online
Telephone
E-mail
Preferred method of contact for non- Required for Sev 1-Critical and Sev
urgent issues: 2-High issues:
Please include:
•
•
My Cases through MyBrocade
•
•
Continental US:
•
•
•
•
Problem summary
Serial number
1-800-752-8061
licensing tools
Europe, Middle East, Africa,
and Asia Pacific: +800-AT
FIBREE (+800 28 34 27 33)
Installation details
Environment description
•
•
•
For areas unable to access toll
free number: +1-408-333-6061
Toll-free numbers are available
in many countries.
FastIron Ethernet Switch IP Multicast Configuration Guide
53-1003085-02
9
Download from Www.Somanuals.com. All Manuals Search And Download.
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. You can provide feedback in two ways:
•
•
Provide the publication title, part number, and as much detail as possible, including the topic heading
and page number if applicable, as well as your suggestions for improvement.
10
FastIron Ethernet Switch IP Multicast Configuration Guide
53-1003085-02
Download from Www.Somanuals.com. All Manuals Search And Download.
About This Guide
Introduction
This guide includes procedures for configuring the software. The software procedures show how to
perform tasks using the CLI. This guide also describes how to monitor Brocade products using statistics
and summary screens.
Supported hardware
This guide supports the following product families from Brocade:
•
FastIron X Series devices (chassis models):
‐
‐
FastIron SX 800
FastIron SX 1600
Brocade FCX Series (FCX) Stackable Switch
•
•
•
•
•
•
™
Brocade ICX 6610 (ICX 6610) Stackable Switch
Brocade ICX 6430 Series (ICX 6430)
Brocade ICX 6450 Series (ICX 6450)
Brocade ICX 6650 Series (ICX 6650)
Brocade ICX7750 Series (ICX7750)
NOTE
The Brocade ICX 6430-C switch supports the same feature set as the Brocade ICX 6430 switch unless
otherwise noted.
NOTE
The Brocade ICX 6450-C12-PD switch supports the same feature set as the Brocade ICX 6450 switch
unless otherwise noted.
What’s new in this document
Support is added for static mroute.
FastIron Ethernet Switch IP Multicast Configuration Guide
53-1003085-02
11
Download from Www.Somanuals.com. All Manuals Search And Download.
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. This process
involves separating command syntax and parameter descriptions from configuration tasks. Until this
process is completed, command information is presented in two ways:
•
For all new content included in this guide, the CLI is documented in separate command pages.
The new command pages follow a standard format to present syntax, parameters, usage
guidelines, examples, and command history. Command pages are compiled in alphabetical order
in a separate command reference chapter at the end of the publication.
•
Legacy content continues to include command syntax and parameter descriptions in the chapters
where the features are documented.
If you do not find command syntax information embedded in a configuration task, refer to the
command reference section at the end of this publication for information on CLI syntax and usage.
12
FastIron Ethernet Switch IP Multicast Configuration Guide
53-1003085-02
Download from Www.Somanuals.com. All Manuals Search And Download.
IPv4 Multicast Traffic Reduction
● Supported IPv4 Multicast Traffic Reduction....................................................................13
● Clear commands for IGMP snooping..............................................................................34
● PIM SM traffic snooping overview...................................................................................35
● PIM SM snooping show commands................................................................................39
Supported IPv4 Multicast Traffic Reduction
The following table lists the individual Brocade FastIron switches and the IPv4 multicast traffic reduction
features they support. These features are supported in the Layer 2 and Layer 3 software images,
except where explicitly noted.
Feature
ICX 6430
ICX 6450
FCX
ICX 6610
ICX 6650
FSX 800
ICX 7750
FSX 1600
IGMP v1/v2/v3 snooping (global and
local)
08.0.01
08.0.01
08.0.01
08.0.01
08.0.01
08.0.01
08.0.10
IGMP fast leave for v2
08.0.01
08.0.01
08.0.01
08.0.01
08.0.01
08.0.01
08.0.01
08.0.01
08.0.01
08.0.01
08.0.01
08.0.01
08.0.10
08.0.10
IGMP membership tracking and fast
leave for v3
PIM-SM v2 Snooping
08.0.01
08.0.01
08.0.01
08.0.01
08.0.01
08.0.01
08.0.01
08.0.01
08.0.01
08.0.01
08.0.01
08.0.01
08.0.10
08.0.10
Static IGMP groups with support for
proxy
IGMP static group traffic filtering
08.0.01
08.0.01
08.0.01
08.0.01
08.0.01
No
No
IGMP snooping overview
When a device processes a multicast packet, by default, it broadcasts the packets to all ports except
the incoming port of a VLAN. Packets are flooded by hardware without going to the CPU. This behavior
causes some clients to receive unwanted traffic.
IGMP snooping provides multicast containment by forwarding traffic to only the ports that have IGMP
receivers for a specific multicast group (destination address). A device maintains the IGMP group
FastIron Ethernet Switch IP Multicast Configuration Guide
53-1003085-02
13
Download from Www.Somanuals.com. All Manuals Search And Download.
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. Data packets destined to addresses in the
reserved range are flooded to the entire VLAN by hardware, and mirrored to the CPU. Multicast data
packets destined for the non-reserved range of addresses are snooped. A client must send IGMP
reports in order to receive traffic.
An IGMP device's responsibility is to broadcast general queries periodically, and to send group queries
when receiving a leave message, to confirm that none of the clients on the port still want specific traffic
before removing the traffic from the port. IGMP V2 lets clients specify what group (destination address)
will receive the traffic but not to specify the source of the traffic. IGMP V3 is for source-specific
multicast traffic, adding the capability for clients to INCLUDE or EXCLUDE specific traffic sources. An
IGMP V3 device port state could be INCLUDE or EXCLUDE, and there are different types of group
records for client reports.
The interfaces respond to general or group queries by sending a membership report that contains one
or more of the following records associated with a specific group:
•
Current-state record that indicates from which sources the interface wants to receive and not
receive traffic. This record contains the source address of interfaces and whether or not traffic will
be included (IS_IN) or not excluded (IS_EX) from this source.
•
Filter-mode-change record. If the interface state changes from IS_IN to IS_EX, a TO_EX record is
included in the membership report. Likewise, if the interface state changes from IS_EX to IS_IN, a
TO_IN record appears in the membership report.
•
•
•
An IGMP V2 leave report is equivalent to a TO_IN (empty) record in IGMP V3. This record means
that no traffic from this group will be received regardless of the source.
An IGMP V2 group report is equivalent to an IS_EX (empty) record in IGMP V3. This record
means that all traffic from this group will be received regardless of source.
Source-list-change record. If the interface wants to add or remove traffic sources from its
membership report, the report can contain an ALLOW record, which includes a list of new sources
from which the interface wishes to receive traffic. It can also contain a BLOCK record, which lists
the current traffic sources from which the interface wants to stop receiving traffic.
IGMP protocols provide a method for clients and a device to exchange messages, and let the device
build a database indicating which port wants what traffic. The protocols do not specify forwarding
methods. They require IGMP snooping or multicast protocols such as PIM to handle packet
forwarding. PIM can route multicast packets within and outside a VLAN, while IGMP snooping can
switch packets only within a VLAN.
If a VLAN is not IGMP snooping-enabled, it floods multicast data and control packets to the entire
VLAN in hardware. When snooping is enabled, IGMP packets are trapped to the CPU. Data packets
are mirrored to the CPU in addition to being VLAN flooded. The CPU then installs hardware resources,
so that subsequent data packets can be switched to desired ports in hardware without going to the
CPU. If there is no client report or port to queriers for a data stream, the hardware resource drops it.
Queriers and non-queriers
An IGMP snooping-enabled Brocade device can be configured as a querier (active) or non-querier
(passive). An IGMP querier sends queries; a non-querier listens for IGMP queries and forwards them
to the entire VLAN. VLANs can be independently configured to be queriers or non-queriers. If a VLAN
has a connection to a PIM-enabled port on another router, the VLAN must be configured as a non-
querier. When multiple IGMP snooping devices are connected together, and there is no connection to
a PIM-enabled port, one of the devices must be configured as a querier. If multiple devices are
configured as queriers, after these devices exchange queries, then all except the winner stop sending
queries. The device with the lowest address becomes the querier. Although the system will work when
14
FastIron Ethernet Switch IP Multicast Configuration Guide
53-1003085-02
Download from Www.Somanuals.com. All Manuals Search And Download.
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. If a server is attached to a non-querier, the non-querier always
forwards traffic to the querier regardless of whether there are any clients on the querier.
NOTE
In a topology of one or more connecting devices, at least one device must be running PIM configured as
active. Otherwise, none of the devices can send out queries, and traffic cannot be forwarded to clients.
VLAN-specific configuration
IGMP snooping can be enabled on some VLANs or on all VLANs. Each VLAN can be independently
configured to be a querier or non-querier and can be configured for IGMP V2 or IGMP V3. In general,
the ip multicast commands apply globally to all VLANs except those configured with VLAN-specific
multicast commands. The VLAN-specific multicast commands supersede the global ip multicast
commands.
IGMP snooping can be configured for IGMP V2 or IGMP V3 on individual ports of a VLAN. An interface
or router sends the queries and reports that include its IGMP version specified on it. The version
configuration only applies to sending queries. The snooping device recognizes and processes IGMP V2
and IGMP V3 packets regardless of the version configuration.
To avoid version deadlock, an interface retains its version configuration even when it receives a report
with a lower version.
Tracking and fast leave
Brocade devices support fast leave for IGMP V2, and tracking and fast leave for IGMP V3. Fast leave
stops the traffic immediately when the port receives a leave message. Tracking traces all IGMP V3
Enabling fast leave for IGMP V2 on page 25.
Support for IGMP snooping and Layer 3 multicast routing together on
the same device
The Brocade device supports global Layer 2 IP multicast traffic reduction (IGMP snoopoing) and Layer
3 multicast routing (PIM-Sparse or PIM-Dense) together on the same device in the full Layer 3 software
image, as long as the Layer 2 feature configuration is at the VLAN level.
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, and ICX 6450 devices.
FastIron Ethernet Switch IP Multicast Configuration Guide
53-1003085-02
15
Download from Www.Somanuals.com. All Manuals Search And Download.
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. If no ports are configured for IGMP v3, the VLAN matches group only (* G).
Matching (S, G) requires more hardware resources than matching (* G) when there are multiple
servers sharing the same group. For example, two data streams from different sources to the same
group require two (S, G) entries in IGMP v3, but only one (* G) entry in IGMP v2.
To conserve resources, IGMP v3 must be used only in source-specific applications. When VLANs are
independently configured for versions, some VLANs can match (* G) while others match (S, G).
MAC-based forwarding implementation on FastIron X Series devices
On both switch and router software images, IGMP snooping is MAC-based. This differs from IGMP
snooping on the BigIron router images, which match on both IP source and group (S,G) entries
programmed in the Layer 4 CAM.
This differs from IGMP snooping on the FastIron FCX/ICX router images, which match on both IP
source and group (S,G) entries. In contrast, the FastIron X Series images match on Layer 2 23-bit
multicast MAC address i.e. 01-00-5e-xx-xx-xx (*,G) entries.
In addition, the lowest 23 bits of the group address are mapped to a MAC address. In this way,
multiple groups (for example, 224.1.1.1 and 225.1.1.1) have the same MAC address. Groups having
the same MAC address are switched to the same destination ports, which are the superset of
individual group output ports. Thus, the use of Layer 2 CAM might cause unwanted packets to be sent
to some ports. However, the switch generally needs far less layer 2 mac entries than it does for IP-
based forwarding, which is required for each stream with a different source and group.
Hardware resources for IGMP and PIM-SM snooping
Brocade devices allocate/program fdb/mac entries and application VLAN (vidx) to achieve multicast
snooping in hardware. If a data packet does not match any of these resources, it might be sent to the
CPU, which increases the CPU burden. This can happen if the device runs out of hardware resources,
or is unable to install resources for a specific matching address due to a hashing collision.
The hardware hashes addresses into available fdb/mac 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.
Configuration notes and feature limitations for IGMP snooping and
Layer 3 multicast routing
The following notes apply to all devices:
•
Layer 2 IGMP multicast is automatically enabled with Layer 3 multicast routing. If Layer 3
multicast routing is enabled on your system, do not attempt to enable Layer 2 IGMP snooping.
•
•
•
The default IGMP version is V2.
A user can configure the maximum numbers of group address entries.
An IGMP device can be configured to rate-limit the forwarding IGMP V2 membership reports to
queriers.
•
The device supports static groups. The device acts as a proxy to send IGMP reports for the static
groups when receiving queries.
16
FastIron Ethernet Switch IP Multicast Configuration Guide
53-1003085-02
Download from Www.Somanuals.com. All Manuals Search And Download.
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). If multiple devices
are configured as active (queriers), only one will keep sending queries after exchanging queries.
•
•
The querier must configure an IP address to send out queries.
IGMP snooping requires hardware resource. Hardware resource is installed only when there is data
traffic. If resource is inadequate, the data stream without a resource is mirrored to the CPU in
addition to being VLAN flooded, which can cause high CPU usage. Brocade recommends that you
avoid global enabling of snooping unless necessary.
•
IGMP snooping requires clients to send membership reports in order to receive data traffic. If a
client application does not send reports, you must configure static groups on the snooping VLAN to
force traffic to client ports. Note that servers (traffic sources) are not required to send IGMP
memberships.
•
•
Support for VSRP together with IGMP snooping on the same interface.
When VSRP or VSRP-aware is configured on a VLAN, only IGMP version 2 is recommended;
IGMP version 3 is not recommended.
•
•
Each VLAN can independently enable or disable IGMP, or configure IGMP v2 or IGMP v3.
IGMP/PIM-SM snooping over Multi-Chassis Trunking is supported on ICX 6650, ICX 7750, and X
series devices.
The following details apply to FCX, ICX 6610, ICX 6430, ICX 6450, and ICX 6650 devices:
•
Using the drop option, you can configure a static group that can discard multicast data packets to a
specified group in hardware, including addresses in the reserved range.
The following details apply to FastIron X Series devices:
•
High CPU utilization occurs when IGMP Snooping and PIM routing are enabled simultaneously,
and if the ingressing VLAN of the snooping traffic has "router-interface" configuration. With this
configuration, IP Multicast data packets received in the snooping VLANs are forwarded to client
ports via the hardware; however, copies of these packets are received and dropped by the CPU.
IGMP snooping configuration
Configuring IGMP snooping on a Brocade device consists of the following global, VLAN-specific, and
port-specific tasks:
Perform the following global IGMP snooping tasks:
•
•
•
•
•
•
•
•
•
•
•
Configuring the IGMP V3 snooping software resource limits
Enabling IGMP snooping globally on the device
Configuring the global IGMP mode
Configuring the global IGMP version
Modifying the age interval for group membership entries
Modifying the query interval (active IGMP snooping mode only)
Modifying the maximum response time
Configuring report control (rate limiting)
Modifying the wait time before stopping traffic when receiving a leave message
Modifying the multicast cache age time
Enabling or disabling error and warning messages
Perform the following VLAN-specific IGMP snooping tasks:
FastIron Ethernet Switch IP Multicast Configuration Guide
53-1003085-02
17
Download from Www.Somanuals.com. All Manuals Search And Download.
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 snooping mcache entries and group addresses
An IGMP snooping group address entry is created when an IGMP join message is received for a
group. An IGMP snooping mcache entry is created when data traffic is received for that group. Each
mcache entry represents one data stream, and multiple mcache entries (up to 32) can share the same
hardware (MAC) address entry. The egress port list for the mcache entry is obtained from the IGMP
group address entry. If there is no existing IGMP group address entry when an mcache entry is
created, data traffic for that multicast group is dropped in hardware. If there is an existing IGMP group
address entry when an mcache is created, data traffic for that multicast group is switched in hardware.
The following describes the IGMP snooping software resource limits for Brocade devices:
•
•
•
•
•
FCX, FSX, ICX 6610, and ICX 6450 devices support up to a maximum of 8192 IGMP snooping
multicast cache (mcache) entries and a maximum of 8192 IGMP group addresses.
ICX 6430 devices support up to 2048 IGMP snooping multicast cache (mcache) entries and a
maximum of 4096 IGMP group addresses.
ICX 6650 devices support 8192 IGMP snooping mcache entries and 8192 IGMP groups
addresses.
ICX 7750 switches support 8192 IGMP snooping mcache entries and 8192 IGMP group
addresses.
ICX 7750 routers support 6K IGMP snooping mcache entries and 8192 IGMP group addresses.
The default for IGMP snooping mcache entries is 512, with the exception of ICX 6430 devices where
the default is 256.
Changing the maximum number of supported IGMP snooping mcache
entries
You can configure the system-max igmp-snoop-mcache command to change the maximum number
of IGMP snooping cache entries supported on a device.
Device(config)#system-max igmp-snoop-mcache 2000
Syntax: [no] system-max igmp-snoop-mcache num
The num variable is a value from 256 through 8192. The default is 512.
18
FastIron Ethernet Switch IP Multicast Configuration Guide
53-1003085-02
Download from Www.Somanuals.com. All Manuals Search And Download.
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-snoop-
group-addr command to define the maximum number of IGMP group addresses.
Device(config)#system-max igmp-snoop-group-addr 1600
Syntax: [no] system-max igmp-snoop-group-addr num
The num variable is a value from 256 to 8192. The default for IGMP snooping group addresses is 4096,
except for ICX 6430 devices where the default is 1024.
Enabling IGMP snooping globally on the device
When you globally enable IGMP snooping, you can specify IGMP V2 or IGMP V3. The ip multicast
version command enables IGMP V3.
device(config)#ip multicast version 3
Syntax: [no] ip multicast version [2 | 3]
If you do not specify a version number, IGMP V2 is assumed.
Configuration notes for Layer 3 devices
•
•
•
If Layer 3 multicast routing is enabled on your system, do not attempt to enable Layer 2 IGMP
snooping. Layer 2 IGMP snooping is automatically enabled with Layer 3 multicast routing.
If the "route-only" feature is enabled on the Layer 3 Switch, then IP multicast traffic reduction will
not be supported.
IGMP snooping is not supported on the default VLAN of Layer 3 Switches.
Configuring the IGMP mode
You can configure active or passive IGMP modes on the Brocade device. The default mode is passive.
If you specify an IGMP mode for a VLAN, it overrides the global setting.
•
Active - When active IGMP mode is enabled, a Brocade device actively sends out IGMP queries to
identify multicast groups on the network, and makes entries in the IGMP table based on the group
membership reports it receives.
NOTE
Routers in the network generally handle this operation. Use the active IGMP mode only when the
device is in a stand-alone Layer 2 Switched network with no external IP multicast router attachments. In
FastIron Ethernet Switch IP Multicast Configuration Guide
53-1003085-02
19
Download from Www.Somanuals.com. All Manuals Search And Download.
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.
device(config)#ip multicast active
Syntax: [no] ip multicast [ active | passive ]
If you do not enter either active or passive, the passive mode is assumed.
Configuring the IGMP mode for a VLAN
If you specify an IGMP mode for a VLAN, it overrides the global setting.
To set the IGMP mode for VLAN 20 to active, enter the following commands.
device(config)#vlan 20
device(config-vlan-20)#multicast active
Syntax: [no] multicast [ active | passive]
Configuring the IGMP version
Use the procedures in this section to specify the IGMP version.
Configuring the global IGMP version
page 19.
Configuring the IGMP version for a VLAN
You can specify the IGMP version for a VLAN. For example, the following commands configure VLAN
20 to use IGMP V3.
device(config)#vlan 20
device(config-vlan-20)#multicast version 3
Syntax: [no] multicast version [2 | 3 ]
If no IGMP version is specified, then the globally-configured IGMP version is used. If an IGMP version
is specified for individual ports, those ports use that version, instead of the VLAN version.
20
FastIron Ethernet Switch IP Multicast Configuration Guide
53-1003085-02
Download from Www.Somanuals.com. All Manuals Search And Download.
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.
device(config)#vlan 20
device(config-vlan-20)#multicast port-version 3 ethernet 2/4 to 2/6
Syntax: [no] multicast port-version [2 | 3 ] ethernetport [ethernet port | toport ]
To specify a list of ports, enter each port as ethernetport followed by a space. For example, ethernet
1/24 ethernet 6/24 ethernet 8/17.
To specify a range of ports, enter the first port in the range as ethernetport followed by the last port in
the range. For example, ethernet 1/1 to 1/8 .
You can combine lists and ranges in the same command. For example: enable ethernet 1/1 to 1/8
ethernet 1/24 ethernet 6/24 ethernet 8/17.
Configuring static groups to specific ports
A snooping-enabled VLAN cannot forward multicast traffic to ports that do not receive IGMP
membership reports. If clients cannot send reports, you can configure a static group which applies to
specific ports. The static group allows packets to be forwarded to the static group ports even though
they have no client membership reports.
device(config)#vlan 20
device(config-vlan-20)#multicast static-group 224.1.1.1 count 2 ethernet 0/1/3
ethernet 0/1/5 to 0/1/7
Information specific to FCX and ICX devices
The following information about the drop option is specific to FCX, ICX 6610, ICX 6430, ICX 6450, and
ICX 6650 devices.
The static group drop option discards data traffic to a group in hardware. The group can be any
multicast group including groups in the reserved range of 224.0.0.X. The drop option does not apply to
IGMP packets, which are always trapped to CPU when snooping is enabled. The drop option applies to
the entire VLAN, and cannot be configured for a port list. When the drop option is not specified, the
group must exist outside the reserved range.
device(config-vlan-20)#multicast static-group 239.1.1.1 count 3 drop
Syntax: [no] multicast static-group ipv4-address [count num] [port-numbers | drop]
The ipv4-address parameter is the address of the multicast group.
The count is optional, which allows a contiguous range of groups. Omitting the count num is equivalent
to the count being 1.
FastIron Ethernet Switch IP Multicast Configuration Guide
53-1003085-02
21
Download from Www.Somanuals.com. All Manuals Search And Download.
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.
device(config)#vlan 20
device(config-vlan-20)#multicast disable-multicast-snoop
Syntax: [no] multicast disable-multicast-snoop
Modifying the age interval for group membership entries
When the device receives a group membership report, it makes an entry for that group in the IGMP
group table. The age interval specifies how long the entry can remain in the table before the device
receives another group membership report. When multiple devices connect together, all devices must
be configured for the same age interval, which must be at least twice the length of the query interval,
so that missing one report won't stop traffic. Non-querier age intervals must be the same as the age
interval of the querier.
To modify the age interval, enter the following command.
device(config)#ip multicast age-interval 280
Syntax: [no] ip multicast age-interval interval
The interval parameter specifies the aging time. You can specify a value from 20 through 26000
seconds. The default is 260 seconds.
Modifying the query interval (active IGMP snooping mode only)
If IP multicast traffic reduction is set to active mode, you can modify the query interval to specify how
often the device sends general queries. When multiple queriers connect together, they must all be
configured with the same query interval.
To modify the query interval, enter the following command.
device(config)#ip multicast query-interval 120
Syntax: [no] ip multicast query-intervalinterval
The interval parameter specifies the time between queries. You can specify a value from 10 through
3600 seconds. The default is 125 seconds.
Modifying the maximum response time
The maximum response time is the number of seconds that a client can wait before responding to a
query sent by the switch.
To change the maximum response time, enter the following command.
device(config)#ip multicast max-response-time 5
Syntax: [no] ip multicast max-response-time interval
For interval , enter a value from 1 through 10 seconds. The default is 10 seconds.
22
FastIron Ethernet Switch IP Multicast Configuration Guide
53-1003085-02
Download from Www.Somanuals.com. All Manuals Search And Download.
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.
IGMP V2 membership reports of the same group from different clients are considered to be the same
and are rate-limited.
Use the ip multicast report-control command to alleviate report storms from many clients answering
the upstream router query.
device(config)#ip multicast report-control
Syntax: [no] ip multicast-report-control
The original command, ip igmp-report-control , has been renamed to ip multicast report-control .
The original command is still accepted; however, it is renamed when you configure a show
configuration command.
Modifying the wait time before stopping traffic when receiving a leave
message
You can define the wait time before stopping traffic to a port when a leave message is received. The
device sends group-specific queries once per second to ask if any client in the same port still needs this
group. Due to internal timer granularity, the actual wait time is between n and (n+1) seconds (n is the
configured value).
device(config)#ip multicast leave-wait-time 1
Syntax: [no] ip multicast leave-wait-timenum
num is the number of seconds from 1 through 5. The default is 2 seconds.
Modifying the multicast cache age time
You can set the time for an mcache to age out when it does not receive traffic. The traffic is hardware
switched. One minute before aging out an mcache, the device mirrors a packet of this mcache to CPU
to reset the age. If no data traffic arrives within one minute, this mcache is deleted. A lower value
quickly removes resources consumed by idle streams, but it mirrors packets to CPU often. A higher
value is recommended only data streams are continually arriving.
device(config)#ip multicast mcache-age 180
Syntax: [no] ip multicast mcache-age num
num is the number of seconds from 60 through 3600. The default is 60 seconds.
FastIron Ethernet Switch IP Multicast Configuration Guide
53-1003085-02
23
Download from Www.Somanuals.com. All Manuals Search And Download.
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.
device(config)#ip multicast verbose-off
Syntax: [no] ip multicast verbose-off
Configuring static router ports
The Brocade device forwards all multicast control and data packets to router ports which receive
queries. Although router ports are learned, you can force multicast traffic to specified ports even
though these ports never receive queries. To configure static router ports, enter the following
commands.
device(config)#vlan 70
device(config-vlan-70)#multicast router-port ethernet 4 to 5 ethernet 8
Syntax: [no] multicast router-port ethernet port [ethernet port | to port]
To specify a list of ports, enter each port as ethernetport followed by a space. For example, ethernet
1/24 ethernet 6/24 ethernet 8/17.
To specify a range of ports, enter the first port in the range as ethernetport followed by the last port in
the range. For example, ethernet 1/1 to 1/8 .
You can combine lists and ranges in the same command. For example: enable ethernet 1/1 to 1/8
ethernet 1/24 ethernet 6/24 ethernet 8/17.
Turning off static group proxy
If a device has been configured for static groups, it acts as a proxy and sends membership reports for
the static groups when it receives general or group-specific queries. When a static group configuration
is removed, it is deleted from the active group table immediately. However, leave messages are not
sent to the querier, and the querier must age out the group. Proxy activity can be turned off. The
default is on. To turn proxy activity off for VLAN 20, enter the following commands.
device(config)#vlan 20
device(config-vlan-20)#multicast proxy-off
Syntax: [no] multicast proxy-off
Enabling IGMP V3 membership tracking and fast leave for the VLAN
IGMP V3 gives clients membership tracking and fast leave capability. In IGMP V2, only one client on
an interface needs to respond to a router's queries. This can leave some clients invisible to the router,
making it impossible to track the membership of all clients in a group. When a client leaves the group,
the device sends group-specific queries to the interface to see if other clients on that interface need
the data stream of the client who is leaving. If no client responds, the device waits a few seconds
before it stops the traffic. You can configure the wait time using the ip multicast leave-wait-time
command.
IGMP V3 requires every client to respond to queries, allowing the device to track all clients. When
tracking is enabled, and an IGMP V3 client sends a leave message and there is no other client, the
24
FastIron Ethernet Switch IP Multicast Configuration Guide
53-1003085-02
Download from Www.Somanuals.com. All Manuals Search And Download.
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). For example, Client A and Client B belong to group1
but each receives traffic streams from different sources. Client A receives a stream from (source_1,
group1) and Client B receives a stream from (source_2, group1). The device still waits for the
configured leave-wait-time before it stops the traffic because these two clients are in the same group. If
the clients are in different groups, then the waiting period is not applied and traffic is stopped
immediately.
To enable the tracking and fast leave feature for VLAN 20, enter the following commands.
device(config)#vlan 20
device(config-vlan-20)#multicast tracking
Syntax: [no] multicast tracking
The membership tracking and fast leave features are supported for IGMP V3 only. If any port or any
client is not configured for IGMP V3, then the multicast tracking command is ignored.
Enabling fast leave for IGMP V2
When a device receives an IGMP V2 leave message, it sends out multiple group-specific queries. If no
other client replies within the waiting period, the device stops forwarding traffic. When fast-leave-v2 is
configured, and when the device receives a leave message, it immediately stops forwarding to that port.
The device does not send group specific-queries. When fast-leave-v2 is configured on a VLAN, you
must not have multiple clients on any port that is part of the VLAN. In a scenario where two devices
connect, the querier device should not be configured for fast-leave-v2 because the port might have
multiple clients through the non-querier. The number of queries, and the waiting period (in seconds) can
be configured using the ip multicast leave-wait-time command. The default is 2 seconds.
To configure fast leave for IGMP V2, enter the following commands.
device(config)#vlan 20
device(config-vlan-20)#multicast fast-leave-v2
Syntax: [no] multicast fast-leave-v2
Enabling fast convergence
In addition to sending periodic general queries, an active device sends general queries when it detects
a new port. However, because the device does not recognize the other device's port up event, multicast
traffic might still require up to the query-interval time to resume after a topology change. Fast
convergence allows the device to listen to topology change events in Layer 2 protocols such as
spanning tree, and then send general queries to shorten the convergence time.
If the Layer 2 protocol cannot detect a topology change, fast convergence may not work in some cases.
For example, if the direct connection between two devices switches from one interface to another, the
rapid spanning tree protocol (802.1w) considers this optimization, rather than a topology change. In this
example, other devices will not receive topology change notifications, and will be unable to send queries
to speed up the convergence. Fast convergence works well with the regular spanning tree protocol in
this case.
To enable fast-convergency, enter the following commands.
device(config)#vlan 70
device(config-vlan-70)#multicast fast-convergence
FastIron Ethernet Switch IP Multicast Configuration Guide
53-1003085-02
25
Download from Www.Somanuals.com. All Manuals Search And Download.
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. Please use "sh ip mu vlan vlan-id" for details
Version=2, Intervals: Query=125, Group Age=260, Max Resp=10, Other Qr=260
VL10: cfg V3, vlan cfg passive, , pimsm (vlan cfg), 1 grp, 0 (SG) cache, no rtr port
To display the IGMP snooping information for a specific VLAN, enter the following command.
device#show ip multicast vlan 10
Version=3, Intervals: Query=10, Group Age=260, Max Resp=10, Other Qr=30
VL10: cfg V3, vlan cfg passive, , pimsm (vlan cfg), 3 grp, 1 (SG) cache, no rtr port,
e2
has
3 groups, non-QR (passive), default V3
**** Warning! has V2 client (life=240),
group: 239.0.0.3, life = 240
group: 224.1.1.2, life = 240
group: 224.1.1.1, life = 240
e4
has
0 groups, non-QR (passive), default V3
Syntax: show ip multicast vlan vlan-id
If you do not specify a vlan-id , information for all VLANs is displayed.
The following table describes the information displayed by the show ip multicast vlan command.
Field
Description
Version
Query
The global IGMP version. In this example, the device is configured for IGMP version 2.
How often a querier sends a general query on the interface. In this example, the general queries are
sent every 125 seconds.
Group Age The number of seconds membership groups can be members of this group before aging out.
Max Resp The maximum number of seconds a client waits before replying to a query.
Other Qr
cfg
How long it took a switch with a lower IP address to become a new querier. This value is 2 x Query +
Max Resp.
The IGMP version for the specified VLAN. In this example, VL10: cfg V3 indicates that VLAN 10 is
configured for IGMP V3.
vlan cfg
pimsm
The IGMP configuration mode, which is either passive or active.
Indicates that PIM SM is enabled on the VLAN.
26
FastIron Ethernet Switch IP Multicast Configuration Guide
53-1003085-02
Download from Www.Somanuals.com. All Manuals Search And Download.
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.
Field
Description
SW processed pkt
up-time
The number of multicast packets processed by IGMP snooping.
The time since the IGMP snooping is enabled.
Displaying IGMP 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 IGMP group values.
device(config)#show default values
System Parameters
Default
Maximum
8192
Current
5000
Configured
5000
igmp-snoop-group-add 4096
To display information about IGMP groups, enter the show ip multicast group command.
device#show ip multicast group
p-:physical, ST:static, QR:querier, EX:exclude, IN:include, Y:yes, N:no
VL70 : 3 groups, 4 group-port, tracking_enabled
group
p-port
1/33
1/33
1/35
1/33
ST
QR
life mode
120 EX
120 EX
100 EX
100 EX
source
1
2
3
4
224.1.1.2
224.1.1.1
226.1.1.1
226.1.1.1
no
yes
yes
yes
yes
0
0
0
0
no
yes
yes
In this example, an IGMP V2 group is in EXCLUDE mode with a source of 0. The group only excludes
traffic from the 0 (zero) source list, which actually means that all traffic sources are included.
To display detailed IGMP group information for a specific group, enter the show ip multicast group
detail command.
device#show ip multicast group 226.1.1.1 detail
Display group 226.1.1.1 in all interfaces in details.
p-:physical, ST:static, QR:querier, EX:exclude, IN:include, Y:yes, N:no
VL70 : 1 groups, 2 group-port, tracking_enabled
group
p-port
1/35
ST
QR
life mode
120 EX
source
0
1
226.1.1.1
yes
yes
group: 226.1.1.1, EX, permit 0 (source, life):
life=120, deny 0:
group
226.1.1.1
p-port
1/33
ST
yes
QR
yes
life mode
120 EX
source
0
2
FastIron Ethernet Switch IP Multicast Configuration Guide
53-1003085-02
27
Download from Www.Somanuals.com. All Manuals Search And Download.
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.
p-:physical, ST:static, QR:querier, EX:exclude, IN:include, Y:yes, N:no
VL70 : 1 groups, 1 group-port, tracking_enabled
group
p-port
ST
QR
life mode
source
*** Note: has 1 static groups to the entire vlan, not displayed here
1
224.1.1.1
1/33
no
yes
100 EX
0
receive reports from 1 clients: (age)
(10.2.100.2 60)
Syntax: show ip multicast group [group-address [detail] [tracking]]
If you want a report for a specific multicast group, enter that group's address for group-address .
Enter detail to display the source list of a specific VLAN.
Enter tracking for information on interfaces that have tracking enabled.
The following table describes the information displayed by the show ip multicast group command.
Field Description
group The address of the group (destination address in this case, 224.1.1.1)
p-port The physical port on which the group membership was received.
ST
QR
life
Yes indicates that the IGMP group was configured as a static group; No means the address was learned
from reports.
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 device.
The number of seconds the group can remain in EXCLUDE mode. An EXCLUDE mode changes to
INCLUDE mode if it does not receive an "IS_EX" or "TO_EX" message during a certain period of time.
The default is 260 seconds. There is no life displayed in INCLUDE mode.
mode Indicates current mode of the interface: INCLUDE or EXCLUDE. If the interface is in INCLUDE mode, it
admits traffic only from the source list. If an interface is in EXCLUDE mode, it denies traffic from the
source list and accepts the rest.
source Identifies the source list that will be included or excluded on the interface.
For example, if an IGMP V2 group is in EXCLUDE mode with a source of 0, the group excludes traffic
from the 0 (zero) source list, which actually means that all traffic sources are included.
Displaying IGMP snooping mcache 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 IGMP mcache values.
device(config)#show default values
28
FastIron Ethernet Switch IP Multicast Configuration Guide
53-1003085-02
Download from Www.Somanuals.com. All Manuals Search And Download.
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. use 1 VIDX
1
(10.10.10.2 239.0.0.3) cnt=0
OIF: tag e2
age=2s up-time=2s change=2s vidx=8191 (ref-cnt=1)
Syntax: show ip multicast mcache
The following table describes the output of the show ip multicast mcache command.
Field
Description
(source group) Source and group addresses of this data stream. (* group) means match group only; (source
group) means match both.
cnt
The number of packets processed in software. Packets are switched in hardware, which increases
this number slowly.
OIF
age
The output interfaces. If entire vlanis displayed, this indicates that static groups apply to the
entire VLAN.
The mcache age. The mcache will be reset to 0 if traffic continues to arrive, otherwise the mcache
will be aged out when it reaches the time defined by the ip multicast mcache-age command.
uptime
vidx
The up time of this mcache in seconds.
Vidx specifies output port list index. Range is from 4096 through 8191
ref-cnt
The vidx is shared among mcaches having the same output interfaces. Ref-cnt indicates the
number of mcaches using this vidx.
Displaying software resource usage for VLANs
To display information about the software resources used, enter the show ip multicast resource
command.
device#show ip multicast resource
alloc in-use avail get-fail
limit get-mem size init
igmp group
256
1
1
255
0
0
32000
1
1
16 256
22 1024
igmp phy port
1024
1023
200000
.... entries deleted ...
snoop mcache entry
128
2
126
0
8192
3
56 128
total pool memory 109056 bytes
has total 2 forwarding hash
VIDX sharing hash
: size=2
anchor=997 2nd-hash=no fast-trav=no
Available vidx: 4060. IGMP/MLD use 2
Syntax: show ip multicast resource
The following table describes the output displayed by the show ip multicast resource command.
FastIron Ethernet Switch IP Multicast Configuration Guide
53-1003085-02
29
Download from Www.Somanuals.com. All Manuals Search And Download.
Displaying the status of IGMP snooping traffic
Field
alloc
Description
The allocated number of units.
in-use
avail
The number of units which are currently being used.
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 groupis configured by the
system-max igmp-snoop-group-addr command. The limit of snoop mcache entry is
configured by the system-max igmp-snoop-mcache command.
get-mem
size
The number of memory allocation. This number must continue to increase.
The size of a unit (in bytes).
init
The initial allocated amount of memory. More memory may be allocated if resources run out.
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. If vidx is not available, the stream
cannot be hardware-switched.
Displaying the status of IGMP snooping traffic
To display status information for IGMP snooping traffic, enter the show ip multicast traffic command.
device#show ip multicast traffic
IGMP snooping: Total Recv: 22, Xmit: 26
Q: query, Qry: general Q, G-Qry: group Q, GSQry: group-source Q, Mbr: member
Recv
VL1
VL70
Recv
VL1
VL70
Send
VL1
VL70
VL70
QryV2
QryV3
G-Qry
GSQry
MbrV2
MbrV3
Leave
0
0
0
0
4
0
0
18
0
0
0
0
0
0
IsIN
IsEX
ToIN
ToEX
ALLOW
BLOCK
Pkt-Err
0
0
4
0
0
0
0
0
0
0
0
0
0
0
MbrV3
0
QryV2
QryV3
G-Qry
GSQry
MbrV2
0
0
0
0
8
0
0
0
0
0
9
18
pimsm-snooping, Hello:
12, Join/Prune:
Syntax: show ip multicast traffic
The following table describes the information displayed by the show ip multicast traffic command.
Field
Description
Q
Query
30
FastIron Ethernet Switch IP Multicast Configuration Guide
53-1003085-02
Download from Www.Somanuals.com. All Manuals Search And Download.
Displaying querier information
Field
Qry
Description
General Query
QryV2
QryV3
G-Qry
GSQry
Mbr
Number of general IGMP V2 queries received or sent.
Number of general IGMP V3 queries received or sent.
Number of group-specific queries received or sent.
Number of group source-specific queries received or sent.
The membership report.
MbrV2
MbrV3
IsIN
The IGMP V2 membership report.
The IGMP V3 membership report.
Number of source addresses that were included in the traffic.
Number of source addresses that were excluded in the traffic.
Number of times the interface mode changed from EXCLUDE to INCLUDE.
Number of times the interface mode changed from INCLUDE to EXCLUDE.
Number of times that additional source addresses were allowed on the interface.
Number of times that sources were removed from an interface.
Number of packets having errors, such as checksum.
Number of PIM sparse hello, join, and prune packets
IsEX
ToIN
ToEX
ALLO
BLK
Pkt-Err
Pimsm-snooping hello, join,
prune
Displaying querier information
You can use the show ip multicast vlan command to display the querier information for a VLAN. This
command displays the VLAN interface status and if there is any other querier present with the lowest IP
address. The following list provides the combinations of querier possibilities:
•
•
•
•
Active Interface with no other querier present
Passive Interface with no other querier present
Active Interface with other querier present
Passive Interface with other querier present
FastIron Ethernet Switch IP Multicast Configuration Guide
53-1003085-02
31
Download from Www.Somanuals.com. All Manuals Search And Download.
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.
device#show ip multicast vlan 10
Version=2, Intervals: Query=125, Group Age=260, Max Resp=10, Other Qr=260
VL10: dft
V2, vlan cfg active, 0 grp, 0 (*G) cache, no rtr port,
1/1/16 has
0 groups,
This interface is Querier
default V2
1/1/24 has
0 groups,
This interface is Querier
default V2
2/1/16 has
0 groups,
This interface is Querier
default V2
2/1/24 has
0 groups,
This interface is Querier
default V2
3/1/1
has
0 groups,
This interface is Querier
default V2
3/1/4
has
0 groups,
This interface is Querier
default V2
Syntax: show ip multicast vlan vlan-id
If you do not specify a vlan-id , information for all VLANs is displayed.
Displaying the passive interface with no other querier present
The following example shows the output in which the VLAN interface is passive and no other querier is
present with the lowest IP address.
device#show ip multicast vlan 10
Version=2, Intervals: Query=125, Group Age=260, Max Resp=10, Other Qr=260
VL10: dft V2, vlan cfg passive, 0 grp, 0 (*G) cache, no rtr port,
1/1/16 has
0 groups,
This interface is non-Querier (passive)
default V2
1/1/24 has
0 groups,
This interface is non-Querier (passive)
default V2
2/1/16 has
0 groups,
This interface is non-Querier (passive)
default V2
2/1/24 has
0 groups,
This interface is non-Querier (passive)
default V2
3/1/1
has
0 groups,
This interface is non-Querier (passive)
default V2
3/1/4
has
0 groups,
This interface is non-Querier (passive)
default V2
Displaying the active Interface with other querier present
The following example shows the output in which the VLAN interface is active and another querier is
present with the lowest IP address.
device#show ip multicast vlan 10
Version=2, Intervals: Query=125, Group Age=260, Max Resp=10, Other Qr=260
VL10: dft V2, vlan cfg active, 7 grp, 6 (*G) cache, rtr ports,
router ports: 2/1/24(260) 10.5.5.5, 3/1/4(260) 10.8.8.8,
32
FastIron Ethernet Switch IP Multicast Configuration Guide
53-1003085-02
Download from Www.Somanuals.com. All Manuals Search And Download.
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.4, life = 240
2/1/24 has
2 groups,
This interface is non-Querier
Querier is 10.5.5.5
Age is 0
Max response time is 100
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 Querier
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
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.6, life = 260
Displaying the passive interface with other querier present
The following example shows the output in which the VLAN interface is passive and another querier is
present with the lowest IP address.
device#show ip multicast vlan 10
Version=2, Intervals: Query=125, Group Age=260, Max Resp=10, Other Qr=260
VL10: dft V2, vlan cfg passive, 7 grp, 6 (*G) cache, rtr ports,
router ports: 2/1/24(260) 10.5.5.5, 3/1/4(260) 10.8.8.8,
1/1/16 has
4 groups,
This interface is non-Querier (passive)
default V2
group: 226.6.6.6, life = 260
group: 228.8.8.8, life = 260
group: 230.0.0.0, life = 260
group: 224.4.4.4, life = 260
1/1/24 has
1 groups,
This interface is non-Querier (passive)
default V2
group: 228.8.8.8, life = 260
2/1/16 has
4 groups,
This interface is non-Querier (passive)
default V2
group: 226.6.6.6, life = 260
group: 228.8.8.8, life = 260
group: 230.0.0.0, life = 260
group: 224.4.4.4, life = 260
2/1/24 has
2 groups,
This interface is non-Querier (passive)
Querier is 10.5.5.5
Age is 0
Max response time is 100
FastIron Ethernet Switch IP Multicast Configuration Guide
53-1003085-02
33
Download from Www.Somanuals.com. All Manuals Search And Download.
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.6, life = 260
Clear commands for IGMP snooping
The clear IGMP snooping commands must be used only in troubleshooting conditions, or to recover
from errors.
Clearing the IGMP mcache
To clear the mcache on all VLANs, enter the clear ip multicast mcache command.
device#clear ip multicast mcache
Syntax: clear ip multicast mcache
Clearing the mcache on a specific VLAN
To clear the mcache on a specific VLAN, enter the following command.
device#clear ip multicast vlan 10 mcache
Syntax: clear ip multicast vlan vlan-id mcache
The vlan-id parameter specifies the specific VLAN in which the mcache needs to be cleared.
Clearing traffic on a specific VLAN
To clear the traffic counters on a specific VLAN, enter the following command.
device#clear ip multicast vlan 10 traffic
Syntax: clear ip multicast vlanvlan-id traffic
The vlan-id parameter specifies the specific VLAN in which traffic counters needs to be cleared.
34
FastIron Ethernet Switch IP Multicast Configuration Guide
53-1003085-02
Download from Www.Somanuals.com. All Manuals Search And Download.
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.
To disable the flooding of unregistered IPv4 multicast frames in an IGMP-snooping-enabled VLAN,
use the ip multicast disable-flooding command in global configuration mode.
The following example shows the disabling of flooding of unregistered IPv4
multicast frames.
Brocade(config)# ip multicast disable-flooding
PIM SM traffic snooping overview
When multiple PIM sparse routers connect through a snooping-enabled device, the Brocade device
always forwards multicast traffic to these routers. For example, PIM sparse routers R1, R2, and R3
connect through a device. Assume R2 needs traffic, and R1 sends it to the device, which forwards it to
both R2 and R3, even though R3 does not need it. A PIM SM snooping-enabled device listens to join
and prune messages exchanged by PIM sparse routers, and stops traffic to the router that sends prune
messages. This allows the device to forward the data stream to R2 only.
PIM SM traffic snooping requires IGMP snooping to be enabled on the device. IGMP snooping
configures the device to listen for IGMP messages. PIM SM traffic snooping provides a finer level of
multicast traffic control by configuring the device to listen specifically for PIM SM join and prune
messages sent from one PIM SM router to another through the device.
Application examples of PIM SM traffic snooping
Figure 1 shows an example application of the PIM SM traffic snooping feature. In this example, a device
is connected through an IP router to a PIM SM group source that is sending traffic for two PIM SM
groups. The device also is connected to a receiver for each of the groups.
When PIM SM traffic snooping is enabled, the device starts listening for PIM SM join and prune
messages and IGMP group membership reports. Until the device receives a PIM SM join message or
an IGMP group membership report, the device forwards IP multicast traffic out all ports. Once the
FastIron Ethernet Switch IP Multicast Configuration Guide
53-1003085-02
35
Download from Www.Somanuals.com. All Manuals Search And Download.
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. Because PIM SM traffic snooping is enabled on the device, the device
examines the join message to learn the group ID, then makes a forwarding entry for the group ID and
the port connected to the receiver router. The next time the device receives traffic for 239.255.162.1
from the group source, the device forwards the traffic only on port 5/1, because that is the only port
connected to a receiver for the group.
Notice that the receiver for group 239.255.162.69 is directly connected to the device. As a result, the
device does not see a join message on behalf of the client. However, because IGMP snooping also is
enabled, the device uses the IGMP group membership report from the client to select the port for
forwarding traffic to group 239.255.162.69 receivers.
The IGMP snooping feature and the PIM SM traffic snooping feature together build a list of groups and
forwarding ports for the VLAN. The list includes PIM SM groups learned through join messages as well
as MAC addresses learned through IGMP group membership reports. In this case, even though the
device never sees a join message for the receiver for group 239.255.162.69, the device nonetheless
learns about the receiver and forwards group traffic to the receiver.
The device stops forwarding IP multicast traffic on a port for a group if the port receives a prune
message for the group.
Notice that the ports connected to the source and the receivers are all in the same port-based VLAN
on the device. This is required for the PIM SM snooping feature. 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.
The following figure shows another example application for PIM SM traffic snooping. This example
shows devices on the edge of a Global Ethernet cloud (a Layer 2 Packet over SONET cloud). Assume
that each device is attached to numerous other devices such as other Layer 2 Switches and Layer 3
Switches (routers).
36
FastIron Ethernet Switch IP Multicast Configuration Guide
53-1003085-02
Download from Www.Somanuals.com. All Manuals Search And Download.
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.
Configuration notes and limitations for PIM SM snooping
•
•
•
PIM SM snooping applies only to PIM SM version 2 (PIM SM V2).
PIM SM traffic snooping is supported in the Layer 2, base Layer 3, and full Layer 3 code.
IGMP snooping must be enabled on the device that will be running PIM SM snooping. The PIM SM
traffic snooping feature requires IGMP snooping.
FastIron Ethernet Switch IP Multicast Configuration Guide
53-1003085-02
37
Download from Www.Somanuals.com. All Manuals Search And Download.
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 port-
based VLAN.
The PIM 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 PIM 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. When the receiver and
source are in the same subnet, they do not need the router in order to find one another. They find
one another directly within the subnet.
The device forwards all IP multicast traffic by default. Once you enable IGMP snooping and PIM SM
traffic snooping, the device initially blocks all PIM SM traffic instead of forwarding it. The device
forwards PIM SM traffic to a receiver only when the device receives a join message from the receiver.
Consequently, if the source and the downstream router are in the same subnet, and PIM SM traffic
snooping is enabled, the device blocks the PIM SM traffic and never starts forwarding the traffic. This
is because the device never receives a join message from the downstream router for the group. The
downstream router and group find each other without a join message because they are in the same
subnet.
NOTE
If the "route-only" feature is enabled on a Layer 3 Switch, PIM SM traffic snooping will not be
supported.
PIM SM snooping configuration
Configuring PIM SM snooping on a Brocade device consists of the following global and VLAN-specific
tasks.
Perform the following global PIM SM snooping task:
•
Enabling or disabling PIM SM snooping
Perform the following VLAN-specific PIM SM snooping tasks:
•
•
Enabling PIM SM snooping on a VLAN
Disabling PIM SM snooping on a VLAN
Enabling or disabling PIM SM snooping
Use PIM SM snooping only in topologies where multiple PIM sparse routers connect through a device.
PIM SM snooping does not work on a PIM dense mode router which does not send join messages and
traffic to PIM dense ports is stopped. A PIM SM snooping-enabled device displays a warning if it
receives PIM dense join or prune messages.
To enable PIM sparse snooping globally, enter the ip pimsm-snooping command.
device(config)#ip pimsm-snooping
38
FastIron Ethernet Switch IP Multicast Configuration Guide
53-1003085-02
Download from Www.Somanuals.com. All Manuals Search And Download.
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.
device(config)#no ip multicast
Syntax: [no] ip pimsm-snooping
Enabling PIM SM snooping on a VLAN
You can enable PIM SM snooping for a specific VLAN. For example, the following commands enable
PIM SM snooping on VLAN 20.
device(config)#vlan 20
device(config-vlan-20)#multicast pimsm-snooping
Syntax: [no] multicast pimsm-snooping
Disabling PIM SM snooping on a VLAN
When PIM SM snooping is enabled globally, you can still disable it for a specific VLAN. For example,
the following commands disable PIM SM snooping for VLAN 20. This setting overrides the global
setting.
device(config)#vlan 20
device(config-vlan-20)#multicast disable-pimsm-snoop
Syntax: [no] multicast disable-pimsm-snoop
PIM SM snooping show commands
This section shows how to display information about PIM SM snooping, including:
•
•
•
Displaying PIM SM snooping information on page 39
Displaying PIM SM snooping information
To display PIM SM snooping information, enter the show ip multicast pimsm-snooping command.
device#show ip multicast pimsm-snooping
vlan 1, has 2 caches.
1
(* 230.1.1.1) has 1 pim join ports out of 1 OIF
FastIron Ethernet Switch IP Multicast Configuration Guide
53-1003085-02
39
Download from Www.Somanuals.com. All Manuals Search And Download.
Displaying PIM SM snooping information on a Layer 2 switch
1 (age=60)
1 has 1 src: 10.20.20.66(60)
2
(* 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.
Syntax: show ip multicast pimsm-snooping [vlan-id]
Use the vlan-id parameter to display PIM SM snooping information for a specific VLAN.
Displaying PIM SM snooping information on a Layer 2 switch
You can display PIM SM snooping information for all groups by entering the following command at any
level of the CLI on a Layer 2 Switch.
device#show ip multicast pimsm-snooping vlan 100
VLAN 100, has 2 caches
1(*230.1.1.1) has 1 pim join ports out of 1OIF
1(age=60)
1 has 1 src: 10.20.20.66(60)
2(* 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)
Syntax: show ip multicast pimsm-snooping vlan vlan-id
Enter the ID of the VLAN for the vlanvlan-id parameter.
If you want to display PIM SM snooping information for one source or one group, enter a command as
in the following example. The command also displays the (source, port) list of the group.
device#show ip multicst pimsm-snooping 230.1.1.1
Show pimsm snooping group 230.1.1.1 in all vlans
VLAN 10, has 2 caches
1(*230.1.1.1) has 1 pim join ports out of 1 OIF
1(age=120)
1 has 1 src:10.20.20.66(120)
Syntax: show ip multicast pimsm-snooping [group-address | source-address]
If the address you entered is within the range of source addresses, then the router treats it as the
source address. Likewise, if the address falls in the range of group addresses, then the router
assumes that you are requesting a report for that group.
The following table describes the information displayed by the show ip multicast pimsm-snooping
command.
Field
Description
VLAN ID
The port-based VLAN to which the following information applies and the number of
members in the VLAN.
PIM SM Neighbor list The PIM SM routers that are attached to the Layer 2 Switch ports.
The value following "expires" indicates how many seconds the Layer 2 Switch will wait for
a hello message from the neighbor before determining that the neighbor is no longer
present and removing the neighbor from the list.
40
FastIron Ethernet Switch IP Multicast Configuration Guide
53-1003085-02
Download from Www.Somanuals.com. All Manuals Search And Download.
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.
PIMv2 Group Port
Source, Port list
The ports on which the Layer 2 Switch has received PIM SM join messages for the group.
The IP address of each PIM SM source and the Layer 2 Switch ports connected to the
receivers of the source.
Displaying PIM SM snooping information for a specific group or source
group pair
To display PIM SM snooping information for a specific group, enter the following command at any level
of the CLI.
device#show ip multicast pimsm-snooping 230.1.1.1
Show pimsm snooping group 230.1.1.1 in all vlans
vlan 10,has 2 caches.
1 (*230.1.1.1) has 1 pim join ports out of 1 OIF
1(age=120)
1 has 1 src:10.20.20.66(120)
To display PIM SM snooping information for a specific (source, group) pair, enter the following
command at any level of the CLI.
device#show ip multicast pimsm-snooping 230.2.2.2 20.20.20.66
Show pimsm snooping source 10.20.20.66, group 230.2.2.2 in all vlans
vlan 10:(*230.2.2.2) has 1 pim join ports out of 2 OIF
1(age=0)
1 has 1 src:10.20.20.66(0)
Syntax: show ip multicast pimsm-snooping group-address [source-ip-address]
The Brocade device determines which address is the group address and which one is the source
address based on the ranges that the address fall into. If the address is within the range of source
addresses, then the router treats it as the source address. Likewise, if the address falls in the range of
group addresses, then the router assumes it is a group address.
The following table describes the information displayed by the show ip multicast pimsm-snooping
command.
Field Description
vlan The VLAN membership ID of the source.
port The port on which the source is sending traffic. In this example, the port number is 1.
FastIron Ethernet Switch IP Multicast Configuration Guide
53-1003085-02
41
Download from Www.Somanuals.com. All Manuals Search And Download.
IPv4 Multicast Traffic Reduction
Field Description
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.
42
FastIron Ethernet Switch IP Multicast Configuration Guide
53-1003085-02
Download from Www.Somanuals.com. All Manuals Search And Download.
IPv6 Multicast Traffic Reduction
● PIM6 SM traffic snooping overview.................................................................................62
● PIM6 SM snooping show commands..............................................................................66
IPv6 Multicast Traffic Reduction
Lists IPv6 Multicast Traffic Reduction features supported on FastIron devices.
The following table lists the individual Brocade FastIron switches and the IPv6 Multicast Traffic
Reduction features they support. These features are supported in the Layer 2 and Layer 3 software
images.
Feature
ICX 6430
ICX 6450
FCX
ICX 6610
ICX 6650
FSX 800
ICX 7750
FSX 1600
MLD v1/v2 snooping (global and local)
MLD fast leave for v1
08.0.01
08.0.01
08.0.01
08.0.01
08.0.01
08.0.01
08.0.01
08.0.01
08.0.01
08.0.01
08.0.01
08.0.01
08.0.01
08.0.01
08.0.01
08.0.01
08.0.01
08.0.01
08.0.01
08.0.01
08.0.01
08.0.01
08.0.01
08.0.01
08.0.01
08.0.01
08.0.01
08.0.01
08.0.01
08.0.01
08.0.01
08.0.01
08.0.01
08.0.10
08.0.10
08.0.10
08.0.10
08.0.10
08.0.10
MLD tracking and fast leave for v2
Static MLD groups with support for proxy 08.0.01
MLD v1/v2 snooping per VLAN
PIM6-SM snooping
08.0.01
08.0.01
MLD snooping overview
The default method a device uses to process an IPv6 multicast packet is to broadcast it to all ports
except the incoming port of a VLAN. Packets are flooded by hardware without going to the CPU, which
may result in some clients receiving unwanted traffic.
If a VLAN is not Multicast Listening Discovery (MLD) snooping-enabled, it floods IPv6 multicast data
and control packets to the entire VLAN in hardware. When snooping is enabled, MLD packets are
trapped to the CPU. Data packets are mirrored to the CPU and flooded to the entire VLAN. The CPU
then installs hardware resources so subsequent data packets can be hardware-switched to desired
FastIron Ethernet Switch IP Multicast Configuration Guide
53-1003085-02
43
Download from Www.Somanuals.com. All Manuals Search And Download.
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. Since the MLD protocols do not specify
forwarding methods, MLD snooping or multicast protocols such as IPv6 PIM-Sparse Mode (PIM6 SM)
are required to handle packet forwarding. PIM6 SM can route multicast packets within and outside a
VLAN, while MLD snooping can switch packets only within a VLAN.
MLD snooping provides multicast containment by forwarding traffic only to those clients that have MLD
receivers for a specific multicast group (destination address). The device maintains the MLD group
membership information by processing MLD reports and generating messages so traffic can be
forwarded to ports receiving MLD reports. This is analogous to IGMP Snooping on Brocade Layer 3
switches.
An IPv6 multicast address is a destination address in the range of FF00::/8. A limited number of
multicast addresses are reserved. Because packets destined for the reserved addresses may require
VLAN flooding, FSX devices do not snoop in the FF0X::00X range (where X is from 00 to FF) and
FFXX:XXXX:XXXX:XXXX:XXXX:XXXX:1:2. Data packets destined to these addresses are flooded to
the entire VLAN by hardware and mirrored to the CPU. Multicast data packets destined to addresses
outside the FF0X::00X range and FFXX:XXXX:XXXX:XXXX:XXXX:XXXX:1:2 are snooped. A client
must send MLD reports in order to receive traffic.
An MLD device periodically sends general queries and sends group queries upon receiving a leave
message, to ensure no other clients at the same port still want this specific traffic before removing it.
MLDv1 allows clients to specify which group (destination IPv6 address) will receive traffic. (MLDv1
cannot choose the source of the traffic.) MLDv2 deals with source-specific multicasts, adding the
capability for clients to INCLUDE or EXCLUDE specific traffic sources. An MLDv2 device's port state
can either be in INCLUDE or EXCLUDE mode.
There are different types of group records for client reports. Clients respond to general queries by
sending a membership report containing one or more of the following records associated with a
specific group:
•
Current-state record - Indicates the sources from which the client wants to receive or not receive
traffic. This record contains the addresses of the multicast sources and indicates whether or not
traffic will be included (IS_IN) or excluded (IS_EX) from that source address.
•
Filter-mode-change record - If the client changes its current state from IS_IN to IS_EX, a
TO_EX record is included in the membership report. Likewise, if a client current state changes
from IS_EX to IS_IN, a TO_IN record appears in the membership report.
•
•
•
MLDv1 leave report - Equivalent to a TO_IN (empty) record in MLDv2. This record means that
no traffic from this group will be received, regardless of the source.
An MLDv1 group report - Equivalent to an IS_EX (empty) record in MLDv2. This record means
that all traffic from this group will be received, regardless of the source.
Source-list-change record - If the client wants to add or remove traffic sources from its
membership report, the report can include an ALLOW record, which contains a list of new sources
from which the client wishes to receive traffic. The report can also contain a BLOCK record, which
lists current traffic sources from which the client wants to stop receiving traffic.
Support for MLD snooping and Layer 3 IPv6 multicast routing together
on the same device
The Brocade device supports global Layer 2 IPv6 multicast traffic reduction (MLD snooping) and Layer
3 IPv6 multicast routing (PIM-Sparse) together on the same device in the full Layer 3 software image,
as long as the Layer 2 feature configuration is at the VLAN level.
44
FastIron Ethernet Switch IP Multicast Configuration Guide
53-1003085-02
Download from Www.Somanuals.com. All Manuals Search And Download.
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. The hardware can match only the lowest 32 bits of a 128 bit IPv6 address. This is 32-bit IP
address matching, not 32-bit multicast MAC address 33-33-xx-xx-xx-xx matching.
If MLDv2 is configured in any port of a VLAN, the VLAN uses an (S, G) match, otherwise it uses (* G).
Because the hardware can match only the lowest 32 bits of a 128 bit IPv6 address, the output interfaces
(OIF) of a hardware resource are the superset of the OIF of all data streams sharing the same lowest
32 bits. For example, if groups ff10::1234:5678:abcd and ff20::5678:abcd share the same hardware
resource, then the OIF of the hardware matching (* 5678:abcd) is the superset of these two groups.
MAC-based forwarding implementation on FastIron X Series and ICX 7750 devices
Multicast Listening Discovery (MLD) snooping on Brocade devices is based on MAC address entries.
When an IPv6 multicast data packet is received, the packet destination MAC is matched with the MAC
address entries in the IPv6 multicast table. If a match is found, packets are sent to the ports associated
with the MAC address. If a match is not found, packets are flooded to the VLAN and copied to the CPU.
For IPv6 multicast, the destination MAC address is in the format 33-33-xx-yy-zz-kk, where xx-yy-zz-kk
are the 32 lowest bits of the IPv6 multicast group address. For example, the IPv6 group address
0xFF3E:40:2001:660:3007:123:0034:5678 maps to the IPv6 MAC address 33-33-00-34-56-78.
For two multicast traffic streams, Source_1 and Group1 (S1,G1) and Source_2 and Group2 (S2,G2),
with the same or different source addresses, if the lowest 32 bits of the 128-bit IPv6 group address are
the same, they would map to the same destination MAC. Because FSX devices support MAC-based
forwarding for MLD snooping, the final multicast MAC address entry would be a superset of all the IPv6
groups mapped to it. For example, consider the following three IPv6 multicast streams sent from port 5
of a Brocade device:
•
•
•
(S1,G1) = (2060::5, ff1e::12), client port 1, port 2
(S2,G2) = (2060::6, ff1e:13::12), client port 2, port 3
(S3,G1) = (2060::7, ff1e::12), client port 4
Because the lowest 32 bits of the group address for G1 and G2 are the same, all three streams would
use 33-33-00-00-00-12 as the destination MAC address. MLD snooping would build a MAC entry with
the MAC address 33-33-00-00-00-12 on egress ports 1, 2, 3, and 4. As a result, all three streams would
be sent to ports 1, 2, 3, and 4. Note that the above example assumes the following:
•
•
•
•
The Brocade device is running MLD snooping on VLAN 10 and all three streams are in VLAN 10
There are clients on port 1 and port 2 for (S1,G1)
There are clients on port 2 and port 3 for (S2,G2)
There are clients on port 4 for (S3,G1)
Hardware resources for MLD and PIMv6 SM snooping
Brocade devices allocate/program fdb/mac entries and application VLAN (vidx) to achieve multicast
snooping in hardware. If a data packet does not match any of these resources, it might be sent to the
CPU, which increases the CPU burden. This can happen if the device runs out of hardware resource, or
FastIron Ethernet Switch IP Multicast Configuration Guide
53-1003085-02
45
Download from Www.Somanuals.com. All Manuals Search And Download.
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 configuration notes and feature limitations
•
•
•
Servers (traffic sources) are not required to send Multicast Listening Discovery (MLD)
memberships.
The default MLD version is V1, where the source address is not sensitive. In this version, (S1,G1)
and (S2,G1) would be considered the same group as (*,G1).
If MLDv2 is configured on any port of a VLAN, you can check the source information, but because
MLD snooping is MAC based, (S,G) switching is not feasible.
•
•
•
Hardware resources are installed only when there is data traffic.
You can configure the maximum number of groups and the multicast cache (mcache) number.
The device supports static groups applying to specific ports. The device acts as a proxy to send
MLD reports for the static groups when receiving queries.
•
•
A user can configure static router ports, forcing all multicast traffic to be sent to these ports.
Brocade devices support fast leave for MLDv1, which stops traffic immediately to any port that
has received a leave message.
•
•
Brocade devices support tracking and fast leave for MLDv2, which tracks all MLDv2 clients. If the
only client on a port leaves, traffic is stopped immediately.
An MLD device can be configured as a querier (active) or non-querier (passive). Queriers send
queries. Non-queriers listen for queries and forward them to the entire VLAN.
•
•
Every VLAN can be independently configured as a querier or a non-querier.
A VLAN that has a connection to an IPv6 PIM-enabled port on another router should be
configured as a non-querier. When multiple snooping devices connect together and there is no
connection to IPv6 PIM ports, only one device should be configured as the querier. If multiple
devices are configured as active, only one will continue to send queries after the devices have
exchanged queries. Refer to the MLD snooping-enabled queriers and non-queriers section.
•
•
•
An MLD device can be configured to rate-limit the forwarding of MLDv1 membership reports to
queriers.
Because an IPv6 link-local address as the source address when sending queries, a global
address is not required.
The MLD implementation allows snooping on some VLANs or on all VLANs. MLD can be enabled
or disabled independently for each VLAN. In addition, individual ports of a VLAN can be
configured as MLDv1 and MLDv2. In general, global configuration commands such as ipv6
multicast.. apply to all VLANs except those with a local multicast6.. configuration, which
supersedes the global configuration. Configuring the version on a port or a VLAN only affects the
device sent query version. The device always processes all versions of client reports regardless
of the version configured.
•
MLD snooping requires hardware resources. If the device has insufficient resources, the data
stream without a resource is mirrored to the CPU in addition to being VLAN flooded, which can
cause high CPU usage. To avoid this situation, Brocade recommends that you avoid enabling
snooping globally unless necessary.
•
•
To receive data traffic, MLD snooping requires clients to send membership reports. If a client does
not send reports, you must configure a static group to force traffic to client ports.
Multicast Router Discovery (MRD) messages are useful for determining which nodes attached to
a switch have multicast routing enabled. This capability is useful in a Layer 2 bridge domain with
snooping switches. By utilizing MRD messages, Layer 2 switches can determine where to send
multicast source data and group membership messages. Multicast source data and group
membership reports must be received by all multicast routers on a segment. Using the group
membership protocol Query messages to discover multicast routers is insufficient due to query
suppression.
46
FastIron Ethernet Switch IP Multicast Configuration Guide
53-1003085-02
Download from Www.Somanuals.com. All Manuals Search And Download.
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.
The following details apply to FastIron X Series and ICX 7750 Series devices:
•
•
If MLDv2 is configured on any port of a VLAN, you can check the source information, but because
MLD snooping is MAC-based, (S,G) switching is not feasible.
High CPU utilization occurs when MLD Snooping and PIM6 routing are enabled simultaneously on
FastIron X Series devices, and if the ingressing VLAN of the snooping traffic has "router-interface"
configuration. With this configuration, IPv6 Multicast data packets received in the snooping VLANs
are forwarded to client ports via the hardware; however, copies of these packets are also received
and dropped by the CPU.
MLD/PIMv6 SM snooping over Multi-Chasis Trunking is supported on Fastiron X series, ICX 6610, and
ICX 7750 devices.
The following details apply to FCX, ICX 6610, ICX 6430, ICX 6450, and ICX 6650 devices:
•
•
If a VLAN is configured for MLDv2, the hardware matches (S G), otherwise it matches (* G).
When any port of a VLAN is configured for MLDv2, the VLAN matches both source and group (S,
G) in hardware switching. If no port is configured for MLDv2, the VLAN matches group only (* G).
Matching (S, G) requires more hardware resources than (* G) when there are multiple servers
sharing the same group. For example, two data streams from different sources to the same group
require two (S, G) entries in MLDv2, compared to only one (* G) in MLD v1.
Use MLD v2 only in a source-specific application. Because each VLAN can be configured for the
version independently, some VLANs might match (* G) while others match (S G)
MLD snooping-enabled queriers and non-queriers
An MLD snooping-enabled device can be configured as a querier (active) or non-querier (passive). An
MLD querier sends queries; a non-querier listens for MLD queries and forwards them to the entire
VLAN. When multiple MLD snooping devices are connected together, and there is no connection to an
IPv6 PIM-enabled port, one of the devices should be configured as a querier. If multiple devices are
configured as queriers, after multiple devices exchange queries, then all devices except the winner (the
device with the lowest address) stop sending queries. Although the system works when multiple devices
are configured as queriers, Brocade recommends that only one device, preferably the one with the
traffic source, is configured as the querier.
VLANs can also be independently configured as queriers or non-queriers. If a VLAN has a connection
to an IPv6 PIM-enabled port on another router, the VLAN should be configured as a non-querier.
Because non-queriers always forward multicast data traffic and MLD messages to router ports which
receive MLD queries or IPv6 PIM hellos, Brocade recommends that you configure the devices with the
data traffic source (server) as queriers. If a server is attached to a non-querier, the non-querier always
forwards traffic to the querier regardless of whether or not there are clients on the querier.
NOTE
In a topology with one or more connected devices, at least one device must be running PIM, or
configured as active. Otherwise, no devices can send queries, and traffic cannot be forwarded to
clients.
To configure the MLD mode (querier or non-querier) on an MLD snooping-enabled device, refer to
Configuring the global MLD mode on page 49. To configure the MLD mode on a VLAN, refer to
Configuring the MLD mode for a VLAN on page 52.
FastIron Ethernet Switch IP Multicast Configuration Guide
53-1003085-02
47
Download from Www.Somanuals.com. All Manuals Search And Download.
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 VLAN-
specific MLD snooping commands. VLAN-specific MLD snooping commands supersede global IPv6
MLD snooping commands.
MLDv1 with MLDv2
MLD snooping can be configured as MLDv1 or MLDv2 on individual ports on a VLAN. An interface or
router sends queries and reports that include the MLD version with which it has been configured. The
version configuration applies only to the sending of queries. The snooping device recognizes and
processes MLDv1 and MLDv2 packets regardless of the version configured.
NOTE
To avoid version deadlock, when an interface receives a report with a lower version than that for which
it has been configured, the interface does not automatically downgrade the running MLD version.
MLD snooping configuration
Configuring Multicast Listening Discovery (MLD) snooping on an IPv6 device consists of the following
global and VLAN-specific tasks.
MLD snooping global tasks
•
•
•
•
•
•
•
•
•
•
Configuring hardware and software resource limits
Disabling transmission and receipt of MLD packets on a port
Configuring the MLD mode: active or passive (must be enabled for MLD snooping)
Modifying the age interval
Modifying the interval for query messages (active MLD mode only)
Specifying the global MLD version
Enabling and disabling report control (rate limiting)
Modifying the leave wait time
Modifying the mcache age interval
Disabling error and warning messages
MLD snooping VLAN-specific tasks:
•
•
•
•
•
•
•
•
•
•
Configuring the MLD mode for the VLAN: active or passive
Enabling or disabling MLD snooping for the VLAN
Configuring the MLD version for the VLAN
Configuring the MLD version for individual ports
Configuring static groups
Configuring static router ports
Disabling proxy activity for a static group
Enabling client tracking and the fast leave feature for MLDv2
Configuring fast leave for MLDv1
Configuring fast-convergence
48
FastIron Ethernet Switch IP Multicast Configuration Guide
53-1003085-02
Download from Www.Somanuals.com. All Manuals Search And Download.
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.
ICX 7750 routers support 3072 MLD snooping mcache entries; ICX 7750 switches support 8192
MLD snooping mcache entries.
•
In Release 8.0.10a and later releases, ICX 7750 routers support 6144 MLD snooping mcache
entries; ICX 7750 switches support 8192 MLD snooping mcache entries.
To define the maximum number of MLD snooping mcache entries, enter the system-max mld-snoop-
mcache num command.
Device(config)#system-max mld-snoop-mcache 8000
Syntax:[no] system-max mld-snoop-mcache num
he num variable is a value from 256 to 8192. The default is 512.
The configured number is the upper limit of an expandable database. Client memberships exceeding
the group limits are not processed.
FCX, FSX, ICX 6610, ICX 6450, and ICX 6650 devices, ICX 7750 routers, and ICX 7750 switches
support up to 8192 MLD snooping group addresses. ICX 6430 devices support up to 4096 MLD
snooping group addresses.
To define the maximum number of multicast group addresses supported, enter the system-max mld-
snoop-group-addr num command.
The default for MLD snooping group addresses is 4096 for most devices; on ICX 6430 devices the
default is 1024.
Device(config)#system-max mld-snoop-group-addr 4000
Syntax:[no] system-max mld-snoop-group-addr num
For all devices except the ICX 6430, The num variable is a value from 256 to 8192. The default is 4096.
For the ICX 6430, the num variable is a value from 256 to 4096. The default is 1024.
Configuring the global MLD mode
You can configure a Brocade device for either active or passive (default) MLD mode. If you specify an
MLD mode for a VLAN, the MLD mode overrides the global setting.
•
•
Active - In active MLD mode, a device actively sends out MLD queries to identify IPv6 multicast
groups on the network, and makes entries in the MLD table based on the group membership
reports it receives from the network.
Passive - In passive MLD mode, the device forwards reports to the router ports which receive
queries. MLD snooping in passive mode does not send queries, but does forward queries to the
entire VLAN.
To globally set the MLD mode to active, enter the ipv6 multicast active command.
device(config)#ipv6 multicast active
Syntax: [no] ipv6 multicast [ active | passive ]
FastIron Ethernet Switch IP Multicast Configuration Guide
53-1003085-02
49
Download from Www.Somanuals.com. All Manuals Search And Download.
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. The age interval specifies how long the entry can remain in the table without
the device receiving another group membership report. When multiple devices connect together, all
devices should be configured with the same age interval. The age interval should be at least twice that
of the query interval, so that missing one report will not stop traffic. For a non-querier, the query
interval should equal that of the querier.
To modify the age interval, enter a command such as the following.
device(config)#ipv6 multicast age-interval 280
Syntax:[no] ipv6 multicast age-interval interval
The interval parameter specifies the aging time. You can specify a value from 20 to 7200 seconds.
The default is 260 seconds.
Modifying the query interval (active MLD snooping mode only)
If the MLD mode is set to active, you can modify the query interval, which specifies how often the
Brocade device sends group membership queries. By default, queries are sent every 60 seconds.
When multiple queriers connect together, all queriers should be configured with the same interval.
To modify the query interval, enter the ipv6 multicast query-interval interval command.
Device(config)#ipv6 multicast query-interval 120
Syntax: [no] ipv6 multicast query-interval interval
The interval parameter specifies the interval between queries. You can specify a value from 10 to
3600 seconds. The default is 125 seconds.
Configuring the global MLD version
The default version is MLDv1. You can specify the global MLD version on the device as either MLDv1
or MLDv2. For example, the following command configures the device to use MLDv2.
device(config)#ipv6 multicast version 2
Syntax: [no] ipv6 multicast version {1 | 2}
You can also specify the MLD version for individual VLANs, or individual ports within VLANs. If no
MLD version is specified for a VLAN, then the globally configured MLD version is used. If an MLD
version is specified for individual ports in a VLAN, those ports use that version instead of the version
specified for the VLAN or the globally specified version. The default is MLDv1.
50
FastIron Ethernet Switch IP Multicast Configuration Guide
53-1003085-02
Download from Www.Somanuals.com. All Manuals Search And Download.
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.
MLDv1 membership reports for the same group from different clients are considered to be the same,
and are rate-limited. This alleviates the report storm caused by multiple clients answering the upstream
router query.
To enable report-control, enter the ipv6 multicast report-control command.
device(config)#ipv6 multicast report-control
Syntax: [no] ipv6 multicast report-control
Modifying the wait time before stopping traffic when receiving a leave
message
You can define the wait time before stopping traffic to a port when the device receives a leave message
for that port. The device sends group-specific queries once per second to determine if any client on the
same port still needs the group.
Device(config)#ipv6 multicast leave-wait-time 1
Syntax: [no] ipv6 multicast leave-wait-time num
The num variable is a value from 1 to 5. The default is 2. Because of the internal timer accuracy, the
actual wait time is between n and (n+1) seconds, where n is the configured value.
Modifying the multicast cache aging time
You can set the time for a multicast cache (mcache) to age out when it does not receive traffic. Two
seconds before an mcache is aged out, the device mirrors a packet of the mcache to the CPU to reset
the age. If no data traffic arrives within two seconds, the mcache is deleted.
Note that in devices like FSX and ICX 7750 where MAC-based MLD snooping is supported, more than
one mcache can be mapped to the same destination MAC. Hence, when an mcache entry is deleted,
the MAC entry may not be deleted. If you configure a lower value, the resource consumed by idle
streams is quickly removed, but packets are mirrored to the CPU more frequently. Configure a higher
value only when data streams are arriving consistently.
You can use the show ipv6 multicast mcache command to view the currently configured mcache age.
See the Enabling or disabling PIM6 SM snooping section.
To modify the multicast cache age out time, enter the ipv6 multicast mcache-age num command.
device(config)#ipv6 multicast mcache-age 180
Syntax: [no] ipv6 multicast mcache-age num
The num variable is a value from 60 to 3600 seconds, and the default is 60 seconds.
FastIron Ethernet Switch IP Multicast Configuration Guide
53-1003085-02
51
Download from Www.Somanuals.com. All Manuals Search And Download.
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.
device(config)#ipv6 multicast verbose-off
Syntax: [no] ipv6 multicast verbose-off
Configuring the MLD mode for a VLAN
You can configure a VLAN for either the active or passive (default) MLD mode. The VLAN setting
overrides the global setting:
•
•
Active - In active MLD mode, the device actively sends out MLD queries to identify IPv6 multicast
groups on the network, and makes entries in the MLD table based on the group membership
reports it receives from the network.
Passive - In passive MLD mode, the device forwards reports to router ports that receive queries.
MLD snooping in the passive mode does not send queries. However, it does forward queries to
the entire VLAN.
To set the MLD mode for VLAN 20 to active, enter the following commands.
device(config)#vlan 20
device(config-vlan-20)#multicst6 active
Syntax: [no] multicast6 [active | passive]
The default mode is passive.
Disabling MLD snooping for the VLAN
When MLD snooping is enabled globally, you can disable it for a specific VLAN. For example, the
following commands disable MLD snooping for VLAN 20. This setting overrides the global setting for
VLAN 20.
device(config)#vlan 20
device(config-vlan-20)#multicast6 disable-mld-snoop
Syntax: [no] multicast6 disable-mld-snoop
Configuring the MLD version for the VLAN
You can specify the MLD version for a VLAN. For example, the following commands configure VLAN
20 to use MLDv2.
device(config)#vlan 20
device(config-vlan-20)#multicast6 version 2
Syntax: [no] multicast6 version [1 | 2]
When no MLD version is specified, the globally-configured MLD version is used. If an MLD version is
specified for individual ports, these ports use that version, instead of the version specified for the
VLAN.
52
FastIron Ethernet Switch IP Multicast Configuration Guide
53-1003085-02
Download from Www.Somanuals.com. All Manuals Search And Download.
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.
Device(config)#vlan 20
Device(config-vlan-20)#multicast6 port-version 2 ethernet 2/1 ethernet 1/4 to 1/6
Syntax: [no] multicast6 port-version [1 | 2 ] ethernet port-numbers
Configuring static groups
A snooping-enabled VLAN cannot forward multicast traffic to ports that do not receive MLD membership
reports. To allow clients to send reports, you can configure a static group that applies to individual ports
on the VLAN. You cannot configure a static group that applies to the entire VLAN.
The maximum number of supported static groups in a VLAN is 512, and the maximum number of
supported static groups for individual ports in a VLAN is 256. The static group forwards packets to the
static group ports even if they have no client membership reports. Configure a static group for specific
ports on VLAN 20 using commands similar to the following.
device(config)#vlan 20
device(config-vlan-20)#multicast6 static-group ff05::100 count 2 ethe 1/3 ethe 1/5 to
1/7
Syntax: [no] multicast6 static-group ipv6-address [ count num] [ port-numbers]
The ipv6-address parameter is the IPv6 address of the multicast group.
The count is optional, which allows a contiguous range of groups. Omitting the count num is equivalent
to the count being 1.
Configuring static router ports
All multicast control and data packets are forwarded to router ports that receive queries. Although router
ports are learned, you can configure static router ports to force multicast traffic to specific ports, even
though these ports never receive queries. To configure static router ports, enter commands such as the
following:
Device(config)#vlan 70
Device(config-vlan-70)#multicast6 router-port ethernet 1/4 to 1/5 ethernet 1/8
Syntax: [no] multicast6 router-port ethernet port-numbers
Disabling static group proxy
A device with statically configured groups acts as a proxy and sends membership reports for its static
groups when it receives general or group-specific queries. When a static group configuration is
removed, the group is immediately deleted from the active group table. However, the device does not
send leave messages to the querier. The querier should age out the group. The proxy activity can be
disabled (the default is enabled).
device(config)#vlan 20
device(config-vlan-20)#multicast6 proxy-off
FastIron Ethernet Switch IP Multicast Configuration Guide
53-1003085-02
53
Download from Www.Somanuals.com. All Manuals Search And Download.
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. In addition, when a client
leaves the group, the device sends group-specific queries to the interface to see if other clients on that
interface need the data stream of the client who is leaving. If no client responds, the device waits a few
seconds before stopping the traffic. You can configure the wait time with the ipv6 multicast6 leave-
wait-time command. See Enabling or disabling PIM6 SM snooping for more information.
MLDv2 requires that every client respond to queries, allowing the device to track every client. When
the tracking feature is enabled, the device immediately stops forwarding traffic to the interface if an
MLDv2 client sends a leave message, and there is no other client. This feature requires the entire
VLAN to be configured for MLDv2 and have no MLDv1 clients. If a client does not send a report during
the specified group membership time (the default is 140 seconds), that client is removed from the
tracking list.
Every group on a physical port keeps its own tracking record. However, it can track group membership
only; it cannot track by (source, group). For example, Client A and Client B belong to group1 but each
is receiving traffic from different sources. Client A receives a traffic stream from (source_1, group1)
and Client B receives a traffic stream from (source_2, group1). The device waits for the configured
leave-wait-time before it stops the traffic because the two clients are in the same group. If the clients
are in different groups, the waiting period is ignored and traffic is stopped immediately.
To enable tracking and fast leave for VLAN 20, enter the following commands.
device(config)#vlan 20
device(config-vlan-20)#multicast6 tracking
Syntax: [no] multicast6 tracking
The membership tracking and fast leave features are supported for MLDv2 only. If a port or client is
not configured for MLDv2, the multicast6 tracking command is ignored.
Configuring fast leave for MLDv1
When a device receives an MLDv1 leave message, it sends out multiple group-specific queries. If no
other client replies within the waiting period, the device stops forwarding traffic to this port. Configuring
fast-leave-v1 allows the device to stop forwarding traffic to a port immediately upon receiving a leave
message. The device does not send group-specific queries. When fast-leave-v1 is configured on a
VLAN, make sure you do not have multiple clients on any port that is part of the VLAN. In a scenario
where two devices connect, the querier device should not be configured for fast-leave-v1, because the
port might have multiple clients through the non-querier. The number of queries and the waiting period
(in seconds) can be configured using the ipv6 multicast leave-wait-time command. See Enabling or
disabling PIM6 SM snooping for more information.
To configure fast leave for MLDv1, use commands such as the following.
device(config)#vlan 20
device(config-vlan-20)#multicast6 fast-leave-v1
Syntax: [no] multicast6 fast-leave-v1
54
FastIron Ethernet Switch IP Multicast Configuration Guide
53-1003085-02
Download from Www.Somanuals.com. All Manuals Search And Download.
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. Configuring
fast-convergence allows the device to listen to topology change events in Layer 2 protocols, such as
spanning tree, and send general queries to shorten the convergence time.
If the Layer 2 protocol is unable to detect a topology change, the fast-convergence feature may not
work. For example, if the direct connection between two devices switches from one interface to another,
the rapid spanning tree protocol (802.1w) considers this an optimization action, rather than a topology
change. In this case, other devices will not receive topology change notifications and will be unable to
send queries to speed up the convergence. The original spanning tree protocol does not recognize
optimization actions, and fast-convergence works in all cases.
To enable fast-convergence, enter commands such as the following.
device(config)#vlan 70
device(config-vlan-70)#multicast6 fast-convergence
Syntax: [no] multicast6 fast-convergence
Displaying MLD snooping information
You can display the following MLD snooping information:
•
•
•
•
•
•
MLD snooping error information
Group and forwarding information for VLANs
Information about MLD snooping mcache
MLD memory pool usage
Status of MLD traffic
MLD information by VLAN
Displaying MLD snooping error information
To display information about possible MLD errors, enter the following command.
device#show ipv6 multicast error
snoop SW processed pkt: 173, up-time 160 sec
Syntax: show ipv6 multicast error
The following table describes the output from the show ipv6 multicast error command.
Field
Description
SW processed pkt
up-time
The number of IPv6 multicast packets processed by MLD snooping.
The MLD snooping up time.
FastIron Ethernet Switch IP Multicast Configuration Guide
53-1003085-02
55
Download from Www.Somanuals.com. All Manuals Search And Download.
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
8192
Current
5000
Configured
5000
MLD-snoop-group-addr 4096
To display MLD group information, enter the show ipv6 multicast group command.
Device#show ipv6 multicast group
p-:physical, ST:static, QR:querier, EX:exclude, IN:include, Y:yes, N:no
VL1 : 263 grp, 263 grp-port, tracking_enabled
group
ff0e::ef00:a0e3
ff01::1:f123:f567
p-port ST QR life mode source
1
2
1/7
1/9
N Y 120 EX
N Y IN
0
1
NOTE
In this example, an MLDv1 group is in EXCLUDE mode with a source of 0. The group excludes traffic
from the 0 (zero) source list, which actually means that all traffic sources are included.
To display detailed MLD group information, enter the following command.
Device#show ipv6 multicast group ff0e::ef00:a096 detail
Display group ff0e::ef00:a096 in all interfaces in details.
p-:physical, ST:static, QR:querier, EX:exclude, IN:include, Y:yes, N:no
VL1 : 1 grp, 1 grp-port, tracking_enabled
group
p-port ST QR life mode source
1/7 N Y 100 EX
1
ff0e::ef00:a096
0
group: ff0e::ef00:a096, EX, permit 0 (source, life):
life=100, deny 0:
If tracking and fast leave are enabled, you can display the list of clients for a particular group by
entering the following command.
Device#show ipv6 multicast group ff0e::ef00:a096 tracking
Display group ff0e::ef00:a096 in all interfaces with tracking enabled.
p-:physical, ST:static, QR:querier, EX:exclude, IN:include, Y:yes, N:no
VL1 : 1 grp, 1 grp-port, tracking_enabled
group
p-port ST QR life mode source
1/7 N Y 80 EX
1
ff0e::ef00:a096
0
receive reports from 1 clients: (age)
(2001:DB8::1011:1213:1415 60)
Syntax: show ipv6 multicast group [ group-address [ detail ] [ tracking ] ]
To receive a report for a specific multicast group, enter that group address for group-address.
Enter the detail keyword to display the source list of a specific VLAN.
Enter the tracking keyword for information on interfaces that are tracking-enabled.
The following table describes the information displayed by the show ipv6 multicast group command.
Field Description
group The address of the IPv6 group (destination IPv6 address).
p-port The physical port on which the group membership was received.
56
FastIron Ethernet Switch IP Multicast Configuration Guide
53-1003085-02
Download from Www.Somanuals.com. All Manuals Search And Download.
Displaying MLD snooping mcache information
Field Description
ST
QR
life
Yes indicates that the MLD group was configured as a static group; No means it was learned from
reports.
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.
The number of seconds the group can remain in EXCLUDE mode. An EXCLUDE mode changes to
INCLUDE if it does not receive an IS_EX or TO_EX message during a specified period of time. The
default is 140 seconds. There is no lifedisplayed in INCLUDE mode.
mode The current mode of the interface: INCLUDE or EXCLUDE. If the interface is in INCLUDE mode, it admits
traffic only from the source list. If the interface is in EXCLUDE mode, it denies traffic from the source list
and accepts the rest.
source Identifies the source list that will be included or excluded on the interface.
An MLDv1 group is in EXCLUDE mode with a source of 0. The group excludes traffic from 0 (zero)
source list, which actually means that all traffic sources are included.
group If you requested a detailed report, the following information is displayed:
•
•
•
•
The multicast group address
The mode of the group
Sources from which traffic will be admitted (INCLUDE) or denied (EXCLUDE) on the interface.
The life of each source list.
If you requested a tracking/fast leave report, the clients from which reports were received are identified.
Displaying MLD snooping mcache 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 mcache values.
device(config)#show default values
System Parameters
mld-snoop-mcache
Default
512
Maximum
8192
Current
512
Configured
512
The MLD snooping mcache contains multicast forwarding information for VLANs. To display information
in the multicast forwarding mcache, enter the show ipv6 multicast mcache command.
device#show ipv6 multicast mcache
Example: (S G) cnt=: (S G) are the lowest 32 bits, cnt: SW proc. count
OIF: 1/22 TR(1/32,1/33), TR is trunk, 1/32 primary, 1/33 output
vlan 1, has 2 cache
1
(abcd:ef50 0:100), cnt=121
OIF: 1/11 1/9
age=0s up-time=120s vidx=4130 (ref-cnt=1)
(abcd:ef50 0:101), cnt=0
2
OIF: entire vlan
age=0s up-time=0s vidx=8191 (ref-cnt=1)
vlan 70, has 0 cache
Syntax: show ipv6 multicast mcache
The following table describes the output from the show ipv6 multicast mcache command. Displaying
software resource usage for VLANs
FastIron Ethernet Switch IP Multicast Configuration Guide
53-1003085-02
57
Download from Www.Somanuals.com. All Manuals Search And Download.
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.
Output interfaces.
OIF
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
vidx
The up time of this mcache in seconds.
The vidx is shared among mcaches using the same output interfaces. The vidx specifies the
output port list, which shows the index. Valid range is from 4096 to 8191.
ref-cnt
The number of mcaches using this vidx.
To display information about the software resources used, enter the following command.
device#show ipv6 multicast resource
alloc in-use avail get-fail
limit get-mem size init
mld group
512
1024
512
9
16
9
503
1008
503
0
0
0
32000
200000
59392
272
279
272
28 256
21 1024
20 256
mld phy port
snoop group hash
.... Entries deleted
total pool memory 194432 bytes
has total 1 forwarding hash
Available vidx: 4061
Syntax: show ipv6 multicast resource
The following table describes the output from the show ipv6 multicast resource command.
Field
alloc
Displays
The allocated number of units.
The number of units which are currently used.
The number of available units.
The number of resource failures
in-use
avail
get-fail
NOTE
It is important to pay close attention to this field.
limit
The upper limit of this expandable field. The MLD group limit is configured using the system-
max mld-snoop-group-addr command. The snoop mcache entry limit is configured using the
system-max mld-snoop-mcache command.
58
FastIron Ethernet Switch IP Multicast Configuration Guide
53-1003085-02
Download from Www.Somanuals.com. All Manuals Search And Download.
Displaying status of MLD snooping traffic
Field
get-mem
size
Displays
The current memory allocation. This number should continue to increase.
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. If vidx is not available, the stream
cannot be hardware-switched.
Displaying status of MLD snooping traffic
To display status information for MLD snooping traffic, enter the show ipv6 multicast traffic command.
device#show ipv6 multicast traffic
MLD snooping: Total Recv: 32208, Xmit: 166
Q: query, Qry: general Q, G-Qry: group Q, GSQry: group-source Q, Mbr: member
Recv
VL1
VL70
Recv
VL1
QryV1
QryV2
G-Qry
GSQry
MbrV1
MbrV2
Leave
0
0
0
0
0
31744
208
256
0
IsEX
31784
0
0
ToIN
0
0
0
0
0
IsIN
1473
0
ToEX
ALLOW
BLOCK
Pkt-Err
1
0
1
0
7
0
0
0
VL70
Send
VL1
0
QryV1
0
QryV2
0
G-Qry
166
0
GSQry
MbrV1
MbrV2
0
0
0
0
0
0
VL70
0
0
Syntax: show ipv6 multicast traffic
The following table describes the information displayed by the show ipv6 multicast traffic command.
Field
Q
Description
Query
Qry
General Query
QryV1
QryV2
G-Qry
GSQry
MBR
MbrV1
Number of general MLDv1 queries received or sent.
Number of general MLDv2 snooping queries received or sent.
Number of group specific queries received or sent.
Number of group source specific queries received or sent.
The membership report.
The MLDv1 membership report.
FastIron Ethernet Switch IP Multicast Configuration Guide
53-1003085-02
59
Download from Www.Somanuals.com. All Manuals Search And Download.
Displaying MLD snooping information by VLAN
Field
MbrV2
IsIN
Description
The MLDv2 membership report.
Number of source addresses that were included in the traffic.
Number of source addresses that were excluded in the traffic.
Number of times the interface mode changed from EXCLUDE to INCLUDE.
Number of times the interface mode changed from INCLUDE to EXCLUDE.
Number of times additional source addresses were allowed on the interface.
Number of times sources were removed from an interface.
Number of packets having errors such as checksum errors.
IsEX
ToIN
ToEX
ALLO
BLK
Pkt-Err
Displaying MLD snooping information by VLAN
You can display MLD snooping information for all VLANs or for a specific VLAN. For example, to
display MLD snooping information for VLAN 70, enter the show ipv6 multicast vlan command.
device#show ipv6 multicast vlan 70
version=1, query-t=60, group-aging-t=140, max-resp-t=3, other-qr-present-t=123
VL70: cfg V2, vlan cfg passive, 2 grp, 0 (SG) cache, rtr ports,
router ports: 1/36(120) 2001:DB8::2e0:52ff:fe00:9900,
1/26 has 2 grp, non-QR (passive), cfg V1
1/26 has 2 grp, non-QR (passive), cfg V1
group: ff10:1234::5679, life = 100
group: ff10:1234::5678, life = 100
1/35 has 0 grp, non-QR (QR=2001:DB8::2e0:52ff:fe00:9900, age=20), dft V2 trunk
Syntax: show ipv6 multicast vlan [vlan-id]
If you do not specify the vlan-id variable, information for all VLANs is displayed.
The following table describes information displayed by the show ipv6 multicast vlan command.
Field
Description
version
query-t
The MLD version number.
How often a querier sends a general query on the interface.
group-aging-t Number of seconds membership groups can be members of this group before aging out.
rtr-port
The router ports which are the ports receiving queries. The display router ports:
1/36(120) 2001:DB8::2e0:52ff:fe00:9900means port 1/36 has a querier with
2001:DB8::2e0:52ff:fe00:9900 as the link-local address, and the remaining life is 120 seconds.
max-resp-t
non-QR
The maximum number of seconds a client can wait before it replies to the query.
Indicates that the port is a non-querier.
60
FastIron Ethernet Switch IP Multicast Configuration Guide
53-1003085-02
Download from Www.Somanuals.com. All Manuals Search And Download.
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.
device#clear ipv6 multicast counters
Syntax: clear ipv6 multicast counters
Clearing the mcache on all VLANs
To clear the mcache on all VLANs, enter the clear ipv6 multicast mcache command.
device#clear ipv6 multicast mcache
Syntax: clear ipv6 multicast mcache
Clearing the mcache on a specific VLAN
To clear the mcache on a specific VLAN, enter the clear ipv6 multicast vlan mcache command.
device#clear ipv6 multicast vlan 10 mcache
Syntax: clear ipv6 multicast vlan vlan-id mcache
The vlan-id parameter specifies the specific VLAN from which to clear the cache.
Clearing traffic counters on a specific VLAN
To clear the traffic counters on a specific VLAN, enter the clear ipv6 multicast vlan traffic command.
device#clear ipv6 multicast vlan 10 traffic
Syntax: clear ipv6 multicast vlan vlan-id traffic
The vlan-id parameter specifies the specific VLAN from which to clear the traffic counters.
FastIron Ethernet Switch IP Multicast Configuration Guide
53-1003085-02
61
Download from Www.Somanuals.com. All Manuals Search And Download.
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.
The following example shows the disabling of flooding of unregistered IPv6
multicast frames.
Brocade(config)# ipv6 multicast disable-flooding
PIM6 SM traffic snooping overview
When multiple PIM sparse routers connect through a snooping-enabled device, the Brocade device
always forwards multicast traffic to these routers. For example, PIM sparse routers R1, R2, and R3
connect through a device. Assume R2 needs traffic, and R1 sends it to the device, which forwards it to
both R2 and R3, even though R3 does not need it. A PIM6 SM snooping-enabled device listens to join
and prune messages exchanged by PIM sparse routers, and stops traffic to the router that sends
prune messages. This allows the device to forward the data stream to R2 only.
PIM6 SM traffic snooping requires MLD snooping to be enabled on the device. MLD snooping
configures the device to listen for MLD messages. PIM6 SM traffic snooping provides a finer level of
multicast traffic control by configuring the device to listen specifically for PIM6 SM join and prune
messages sent from one PIM6 SM router to another through the device.
Application examples of PIM6 SM traffic snooping
Figure 2 shows an example application of the PIM6 SM traffic snooping feature. In this example, a
device is connected through an IP router to a PIM6 SM group source that is sending traffic for two
PIM6 SM groups. The device also is connected to a receiver for each of the groups.
When PIM6 SM traffic snooping is enabled, the device starts listening for PIM6 SM join and prune
messages and MLD group membership reports. Until the device receives a PIM6 SM join message or
an MLD group membership report, the device forwards IP multicast traffic out all ports. Once the
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 MLD reports were
received.
In this example, the router connected to the receiver for group ff1e::1:2 sends a join message toward
the group source. Because PIM6 SM traffic snooping is enabled on the device, the device examines
the join message to learn the group ID, then makes a forwarding entry for the group ID and the port
connected to the receiver router. The next time the device receives traffic for ff1e::1:2 from the group
source, the device forwards the traffic only on port 5/1, because that is the only port connected to a
receiver for the group.
62
FastIron Ethernet Switch IP Multicast Configuration Guide
53-1003085-02
Download from Www.Somanuals.com. All Manuals Search And Download.
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. The list includes PIM6 SM groups learned through join messages as well
as MAC addresses learned through MLD group membership reports. In this case, even though the
device never sees a join message for the receiver for group ff1e::3:4, the device nonetheless learns
about the receiver and forwards group traffic to the receiver.
The device stops forwarding IP multicast traffic on a port for a group if the port receives a prune
message for the group.
Notice that the ports connected to the source and the receivers are all in the same port-based VLAN on
the device. This is required for the PIM6 SM snooping feature. 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.
The following figure shows another example application for PIM6 SM traffic snooping. This example
shows devices on the edge of a Global Ethernet cloud (a Layer 2 Packet over SONET cloud). Assume
that each device is attached to numerous other devices such as other Layer 2 Switches and Layer 3
Switches (routers).
FastIron Ethernet Switch IP Multicast Configuration Guide
53-1003085-02
63
Download from Www.Somanuals.com. All Manuals Search And Download.
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.
Configuration notes and limitations for PIM6 SM snooping
•
•
•
PIM6 SM snooping applies only to PIM6 SM version 2 (PIM6 SM V2).
PIM6 SM traffic snooping is supported in the Layer 2, base Layer 3, and full Layer 3 code.
MLD snooping must be enabled on the device that will be running PIM6 SM snooping. The PIM6
SM traffic snooping feature requires MLD snooping.
NOTE
Use the passive mode of MLD 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.
64
FastIron Ethernet Switch IP Multicast Configuration Guide
53-1003085-02
Download from Www.Somanuals.com. All Manuals Search And Download.
PIM6 SM snooping configuration
•
•
All the device ports connected to the source and receivers or routers must be in the same port-
based 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. When the receiver and source
are in the same subnet, they do not need the router in order to find one another. They find one
another directly within the subnet.
The device forwards all IP multicast traffic by default. Once you enable MLD snooping and PIM6 SM
traffic snooping, the device initially blocks all PIM6 SM traffic instead of forwarding it. The device
forwards PIM6 SM traffic to a receiver only when the device receives a join message from the receiver.
Consequently, if the source and the downstream router are in the same subnet, and PIM6 SM traffic
snooping is enabled, the device blocks the PIM6 SM traffic and never starts forwarding the traffic. This
is because the device never receives a join message from the downstream router for the group. The
downstream router and group find each other without a join message because they are in the same
subnet.
NOTE
If the "route-only" feature is enabled on a Layer 3 Switch, PIM6 SM traffic snooping will not be
supported.
PIM6 SM snooping configuration
Configuring PIM6 SM snooping on a Brocade device consists of the following global and VLAN-specific
tasks.
Perform the following global PIM6 SM snooping task:
•
Enabling or disabling PIM6 SM snooping
Perform the following VLAN-specific PIM6 SM snooping tasks:
•
•
Enabling PIM6 SM snooping on a VLAN
Disabling PIM6 SM snooping on a VLAN
Enabling or disabling PIM6 SM snooping
Use PIM6 SM snooping only in topologies where multiple PIM sparse routers connect through a device.
PIM6 SM snooping does not work on a PIM dense mode router which does not send join messages and
traffic to PIM dense ports is stopped. A PIM6 SM snooping-enabled device displays a warning if it
receives PIM dense join or prune messages.
Perform the following steps to enable PIM6 SM snooping globally.
1. Enable MLD snooping passive globally.
device(config)#ipv6 multicast passive
2. Enable PIM6 SM snooping globally.
device(config)#ipv6 pimsm-snooping
This command enables PIM6 SM traffic snooping. The PIM6 SM traffic snooping feature assumes
that the network has routers that are running PIM6 SM.
FastIron Ethernet Switch IP Multicast Configuration Guide
53-1003085-02
65
Download from Www.Somanuals.com. All Manuals Search And Download.
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. Configure a VLAN and add the ports that are connected to the device and host in the same port-
based VLAN.
device(config)#vlan 20
device(config-vlan-20)#untagged etherenet 1/1/5 ethernet 1/1/7 ethernet 1/1/11
2. Enable MLD snooping passive on the VLAN.
device(config-vlan-20)#multicast6 passive
3. Enable PIM6 SM snooping on the VLAN.
device(config-vlan-20)#multicast6 pimsm-snooping
Syntax: [no] multicast6 pimsm-snooping
Disabling PIM6 SM snooping on a VLAN
When PIM6 SM snooping is enabled globally, you can still disable it for a specific VLAN. For example,
the following commands disable PIM6 SM snooping for VLAN 20. This setting overrides the global
setting.
device(config)#vlan 20
device(config-vlan-20)#multicast6 disable-pimsm-snoop
Syntax: [no] multicast6 disable-pimsm-snoop
PIM6 SM snooping show commands
This section shows how to display information about PIM6 SM snooping, including:
•
•
Displaying PIM6 SM snooping information on page 66
Displaying PIM6 SM snooping for a VLAN on page 67
Displaying PIM6 SM snooping information
To display PIM6 SM snooping information, enter the show ipv6 multicast pimsm-snooping
command.
device#show ipv6 multicast pimsm-snooping
vlan 25, has 2 caches.
1
(0:11 1:3) has 2 pim join ports out of 2 OIF
1/1/2 (age=0), 2/1/3 (age=0),
66
FastIron Ethernet Switch IP Multicast Configuration Guide
53-1003085-02
Download from Www.Somanuals.com. All Manuals Search And Download.
Displaying PIM6 SM snooping for a VLAN
1/1/2 has 1 src: 15::11(0),
2/1/3 has 1 src: 15::11(0),
2
(0:16 1:3) has 2 pim join ports out of 2 OIF
2/1/3 (age=0), 1/1/2 (age=0),
1/1/2 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
You can display PIM6 SM snooping information for all groups by entering the following command at any
level of the CLI on a Layer 2 Switch.
device#show ipv6 multicast pimsm-snooping vlan 25
vlan 25, has 2 caches.
1
(0:11 1:3) has 2 pim join ports out of 2 OIF
1/1/2 (age=30), 2/1/3 (age=30),
1/1/2 has 1 src: 15::11(30),
2/1/3 has 1 src: 15::11(30),
2
(0:16 1:3) has 2 pim join ports out of 2 OIF
2/1/3 (age=90), 1/1/2 (age=10),
1/1/2 has 1 src: 15::16(10),
Syntax: show ipv6 multicast pimsm-snooping vlan vlan-id
Enter the ID of the VLAN for the vlan-id parameter.
The following table describes the information displayed by the show ipv6 multicast pimsm-snooping
command.
Field
Description
VLAN ID
The port-based VLAN to which the following information applies and the number of
members in the VLAN.
PIM6 SM Neighbor
list
The PIM6 SM routers that are attached to the Layer 2 Switch ports.
The value following "expires" indicates how many seconds the Layer 2 Switch will wait for a
hello message from the neighbor before determining that the neighbor is no longer present
and removing the neighbor from the list.
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 MLD membership report for the group, or both.
PIMv2 Group Port
Source, Port list
The ports on which the Layer 2 Switch has received PIM6 SM join messages for the group.
The IP address of each PIM6 SM source and the Layer 2 Switch ports connected to the
receivers of the source.
FastIron Ethernet Switch IP Multicast Configuration Guide
53-1003085-02
67
Download from Www.Somanuals.com. All Manuals Search And Download.
Displaying PIM6 SM snooping for a VLAN
68
FastIron Ethernet Switch IP Multicast Configuration Guide
53-1003085-02
Download from Www.Somanuals.com. All Manuals Search And Download.
IPv4 Multicast Protocols
● Overview of IP multicasting.............................................................................................71
● Multicast non-stop routing...............................................................................................76
● Displaying system values..............................................................................................103
● Clearing the PIM forwarding cache...............................................................................118
● Clearing the PIM message counters.............................................................................120
● Displaying PIM RPF......................................................................................................121
● MSDP Anycast RP........................................................................................................137
● PIM Anycast RP............................................................................................................141
● Static multicast routes...................................................................................................143
Supported IPv4 Multicast Protocols features
The following table displays the individual devices and the IPv4 Multicast Protocol features they
support.
Feature
ICX 6430
ICX 6450
FCX
ICX 6610
ICX 6650
FSX 800
ICX 7750
FSX 1600
IGMP (v1, v2, and v3)
No
08.0.011
08.0.011
08.0.01
08.0.01
08.0.01
08.0.01
08.0.01
08.0.01
08.0.01
08.0.01
08.0.10
08.0.10
IGMP membership tracking No
and fast leave for v3
1
In a mixed stack only.
FastIron Ethernet Switch IP Multicast Configuration Guide
53-1003085-02
69
Download from Www.Somanuals.com. All Manuals Search And Download.
IPv4 Multicast Protocols
Feature
ICX 6430
ICX 6450
FCX
ICX 6610
ICX 6650
FSX 800
ICX 7750
FSX 1600
PMRI
No
No
No
No
No
No
08.0.011
08.0.011
08.0.011
08.0.011
08.0.011
08.0.011
08.0.011
08.0.01
08.0.01
08.0.01
08.0.01
08.0.01
08.0.01
08.0.01
08.0.01
08.0.01
08.0.01
08.0.01
08.0.01
08.0.01
08.0.01
08.0.01
08.0.01
08.0.01
08.0.01
08.0.01
08.0.01
08.0.01
08.0.01
08.0.01
08.0.01
08.0.01
08.0.01
08.0.01
08.0.01
08.0.10
08.0.10
08.0.10
08.0.10
08.0.10
08.0.10
08.0.10
PIM-SSM
Multi-VRF support
IP Multicast Boundaries
PIM Dense
PIM Sparse
Multicast Source Discovery No
Protocol (MSDP)
MSDP Mesh Groups
MSDP Anycast RP
PIM Anycast RP
No
No
No
No
08.0.011
08.0.011
08.0.011
08.0.011
08.0.01
08.0.01
08.0.01
08.0.01
08.0.01
08.0.01
08.0.01
08.0.01
08.0.01
08.0.01
08.0.01
08.0.01
08.0.01
08.0.01
08.0.01
08.0.01
08.0.10
08.0.10
08.0.10
08.0.10
Concurrent support for
Multicast Routing and
Snooping
Modifying the Prune Wait
Timer
No
08.0.011
08.0.01
08.0.01
08.0.01
08.0.01
08.0.10
IGMP Proxy
No
No
08.0.01
08.0.01
08.0.01
08.0.01
08.0.01
08.0.01
08.0.01
08.0.01
08.0.01
08.0.10
08.0.10
Hardware replication
resource sharing
08.0.011
IPv4 ACLs for rendezvous No
points (RPs)
08.0.011
08.0.011
08.0.01
08.0.01
08.0.01
08.0.01
08.0.01
No
08.0.01
08.0.01
08.0.10
08.0.10
IPv4 Multicast Non-stop
routing (NSR) support for
PIM-SM,SSM, and Anycast
RP
No
No
08.0.10a1
08.0.10a
08.0.10a
08.0.10a
08.0.10a
08.0.10a
Static mroute support
This chapter describes how to configure devices for the following IP multicast protocol and versions:
•
•
Internet Group Management Protocol (IGMP) V1 and V2
Protocol Independent Multicast Dense mode (PIM DM) V1 (draft-ietf-pim-dm-05) and V2 (draft-
ietf-pim-v2-dm-03)
•
PIM Sparse mode (PIM SM) V2 (RFC 2362)
NOTE
Each multicast protocol uses IGMP. IGMP is automatically enabled on an interface when you
configure PIM, and is disabled on the interface if you disable PIM.
70
FastIron Ethernet Switch IP Multicast Configuration Guide
53-1003085-02
Download from Www.Somanuals.com. All Manuals Search And Download.
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.
Brocade devices support the Protocol-Independent Multicast (PIM) protocol, along with the Internet
Group Membership Protocol (IGMP).
PIM is a broadcast and pruning multicast protocol that delivers IP multicast datagrams. This protocol
employs reverse path lookup check and pruning to allow source-specific multicast delivery trees to
reach all group members. PIM builds a different multicast tree for each source and destination host
group.
Multicast terms
The following terms are commonly used in discussing multicast-capable devices. These terms are used
throughout this chapter:
Node: A device.
Root Node: The node that initiates the tree building process. It is also the device that sends the
multicast packets down the multicast delivery tree.
Upstream: The direction from which a device receives multicast data packets. An upstream device is a
node that sends multicast packets.
Downstream: The direction to which a device forwards multicast data packets. A downstream device
is a node that receives multicast packets from upstream transmissions.
Group Presence: A multicast group has been learned from one of the directly connected interfaces.
Members of the multicast group are present on the device.
Intermediate nodes: Devices that are in the path between source devices and leaf devices.
Leaf nodes: Devices that do not have any downstream devices.
Multicast Tree: A unique tree is built for each source group (S,G) pair. A multicast tree is comprised of
a root node and one or more nodes that are leaf or intermediate nodes.
Support for Multicast Multi-VRF
Multicast Multi-VRF support for the Brocade device includes the following:
•
PIM (PIM-SM and PIM-DM) The procedure for configuring PIM within a VRF instance is described
in the “Enabling PIM on the device and an interface” and the “Configuring global PIM Sparse
parameters” sections.
system-max command changes
Several changes have been made to thesystem-max commands in support of Multicast Multi-VRF.
The system-max pim-mcache command has been deprecated and replaced by the system max pim-
hw-mcache command.
FastIron Ethernet Switch IP Multicast Configuration Guide
53-1003085-02
71
Download from Www.Somanuals.com. All Manuals Search And Download.
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.
Show and clear command support
The following show and clear commands support Multicast Multi-VRF:
•
•
•
•
•
•
clear ip igmp [ vrf vrf-name ] cache
clear ip igmp [ vrf vrf-name ] traffic
show ip igmp [vrf vrf-name] group [group-address [detail] [tracking]]
show ip igmp [vrf vrf-name] interface [ve number | ethernet port-address | tunnel num]
show ip igmp [vrf vrf-name] settings
show ip igmp [vrf vrf-name] traffic
Changing global IP multicast parameters
The following sections apply to PIM-DM, PIM-SM, and IGMP.
Concurrent support for multicast routing and snooping
Multicast routing and multicast snooping instances work concurrently on the same device. For
example, you can configure PIM routing on certain VEs interfaces and snooping on other VEs or
VLANs. The limitation is that either multicast snooping or routing can be enabled on a VE interface or
VLAN, but not on both. This is because all of the multicast data and control packets (IGMP, PIM)
received on the snooping VLAN are handled by multicast snooping and do not reach the multicast
routing component. Similarly, any multicast data or control packets received on a VE interface enabled
with PIM routing are handled by the PIM routing component and are not seen by the IGMP or PIM
snooping component.
The following considerations apply when configuring concurrent operation of Multicast Routing and
Snooping.
1. Either multicast snooping or routing can be enabled on a VE or VLAN but not both.
2. Snooping can be enabled globally by configuring the ip multicast active | passive command.
3. The global snooping configuration is inherited by all current VLANs that are not enabled for
multicast routing.
4. The global snooping configuration is also inherited by all new VLANs. Enabling multicast routing
on a newly created VLAN or VE automatically disables snooping on the VLAN or VE.
5. When a VLAN-level snooping is configured, it is displayed.
72
FastIron Ethernet Switch IP Multicast Configuration Guide
53-1003085-02
Download from Www.Somanuals.com. All Manuals Search And Download.
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.
device(config)# router pim
device(config-pim-router)# max-mcache 999
Syntax: [no] max-cache num
The num variable specifies the maximum number of multicast cache entries for PIM in the default VRF.
If not defined by this command, the maximum value is determined by the system-max pim-hw-
mcache command or by available system resources.
To define the maximum number of PIM Cache entries for a specified VRF, use the following command.
device(config)# router pim vrf vpn1
device(config-pim-router-vrf-vpn1)# max-mcache 999
Syntax: [no] router pim [ vrf vrf-name ]
The vrf parameter specified with the router pim command allows you to configure the max-mcache
command for a virtual routing and forwarding (VRF) instance specified by the vrf-name variable.
The num variable specifies the maximum number of multicast cache entries for PIM in the specified
VRF. If not defined by this command, the maximum value is determined by the system-max command
option pim-hw-mcache or by available system resources.
Defining the maximum number of IGMP group addresses
You can use the ip igmp max-group-address run-time command to set the maximum number of IGMP
addresses for the default virtual routing and forwarding (VRF) instance or for a specified VRF. To define
this maximum for the default VRF, enter the following command.
device(config)# ip igmp max-group-address 1000
Syntax: [no] ip igmp max-group-address num
The num variable specifies the maximum number of IGMP group addresses for all VRFs, including the
default VRF. If not defined by this command, the maximum value is determined by available system
resources.
To define this maximum for a specified VRF, enter the following commands.
device(config)# vrf vpn1
device(config-vrf-vpn1)# address-family ipv4
device(config-vrf-vpn1-ipv4)# ip igmp max-group-address 1000
Syntax: [no] vrf vrf-name
Syntax: [no] address-family ipv4
Syntax: [no] ip igmp max-group-address num
The vrf parameter specifies the VRF instance specified by the vrf-name variable.
The num parameter specifies the number of IGMP group addresses that you want to make available for
the specified VRF. If not defined by this command, the maximum value is determined by available
system resources.
FastIron Ethernet Switch IP Multicast Configuration Guide
53-1003085-02
73
Download from Www.Somanuals.com. All Manuals Search And Download.
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.
The following IGMP V1 and V2 parameters apply to PIM:
•
•
IGMP query interval - Specifies how often the Brocade device queries an interface for group
membership. Possible values are 2 - 3600. The default is 125.
IGMP group membership time - Specifies how many seconds an IP Multicast group can remain
on a Brocade device interface in the absence of a group report. Possible values are 5 - 26000.
The default is 260.
•
IGMP maximum response time - Specifies how many seconds the Brocade device will wait for an
IGMP response from an interface before concluding that the group member on that interface is
down and removing the interface from the group. Possible values are 1 - 25. The default is 10.
Modifying IGMP (V1 and V2) query interval period
The IGMP query interval period defines how often a device will query an interface for group
membership. Possible values are 2 to 3600 seconds and the default value is 125 seconds.
To modify the default value for the IGMP (V1 and V2) query interval, enter the following:
Device(config)# ip igmp query-interval 120
Syntax: [no] ip igmp query-interval num
The num variable specifies the number of seconds and can be a value from 2 to 3600.
The default value is 125.
Modifying IGMP (V1 and V2) 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 to 26000 seconds and the default value is 260 seconds.
To define an IGMP (V1 and V2) membership time of 240 seconds, enter the following.
device(config)# ip igmp group-membership-time 240
Syntax: [no] ip igmp group-membership-time num
The num variable specifies the number of seconds and can be a value from 5 to 26000.
The default value is 260.
Modifying IGMP (V1 and V2) maximum response time
Maximum response time defines how long the Brocade device will wait for an IGMP (V1 and V2)
response from an interface before concluding that the group member on that interface is down and
removing the interface from the group. Possible values are 1 to 25. The default is 10.
To change the IGMP (V1 and V2) maximum response time, enter a command such as the following at
the global CONFIG level of the CLI.
Device(config)# ip igmp max-response-time 8
74
FastIron Ethernet Switch IP Multicast Configuration Guide
53-1003085-02
Download from Www.Somanuals.com. All Manuals Search And Download.
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.”
NOTE
When used in applications such as IP-TV (or any multicast application in general), the administrator
should ensure that the set-top box (or multicast client) is configured on the same subnet as the v.e.
configured on the device. This is typically the case but is emphasized here to ensure correct operation.
Without this configuration, IGMP messages received by the device are ignored, which causes an
interruption in any multicast traffic directed towards the set-top box (multicast client).
Adding an interface to a multicast group
You can manually add an interface to a multicast group. This is useful in the following cases:
•
•
Hosts attached to the interface are unable to add themselves as members of the group using
IGMP.
There are no members for the group attached to the interface.
When you manually add an interface to a multicast group, the device forwards multicast packets for the
group but does not itself accept packets for the group.
You can manually add a multicast group to individual ports only. If the port is a member of a virtual
routing and forwarding (VRF) interface, you must add the ports to the group individually.
To manually add a port to a multicast group, enter a command such as the following at the configuration
level for the port.
Device(config-if-e10000-1/1)# ip igmp static-group 224.2.2.2
This command adds port 1/1 to multicast group 224.2.2.2.
To add a port that is a member of a VRF interface to a multicast group, enter a command such as the
following at the configuration level for the virtual routing interface.
Device(config-vif-1)# ip igmp static-group 224.2.2.2 ethernet 5/2
This command adds port 5/2 in VRF interface 1 to multicast group 224.2.2.2.
Syntax: [no] ip igmp static-group ip-addr [ ethernet slot/portnum ]
The ip-addr variable specifies the group number.
The ethernet slot/portnum parameter specifies the port number. Use this parameter if the port is a
member of a VRF interface, and you are entering this command at the configuration level for the VRF
interface.
Manually added groups are included in the group information displayed by the following commands:
•
•
show ip igmp group
show ip pim group
FastIron Ethernet Switch IP Multicast Configuration Guide
53-1003085-02
75
Download from Www.Somanuals.com. All Manuals Search And Download.
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.
Multicast non-stop routing
Multicast non-stop routing (NSR) provides hitless-failover support on all platforms for IPv4 multicast
features (default and non-default VRFs): PIM-DM, PIM-SM, and PIM-SSM.
If multicast NSR is enabled, the software state is kept in sync between the active and standby
modules. The standby module is NSR ready when the software state of the standby and active
modules are in sync. When the standby module is NSR ready, a hitless-failover does not result in a
disruption to the multicast forwarding state or traffic
If Multicast NSR is not enabled, or if the standby module is not NSR ready, the software state of the
standby and active modules are not in sync. In this case, after a switchover or failover occurs, the new
active module enters protocol learning phase for a duration of 55 seconds. During this phase, it learns
the protocol state information from its PIM neighbors and local clients. During this period, new
multicast flows will not be forwarded, but the existing mutlicast flows (which existed prior to switchover
or failover) are forwarded in hardware without any disruption. At the end of the period, all the existing
flows are deleted from hardware and they are reprogrammed as per the newly learned state
information. Multicast traffic will incur a slight disturbance until the new active module reprograms the
hardware with new forwarding state information.
The following message is displayed on the console of the active and standby modules to indicate that
the standby module is NSR ready:
Mcastv4 is NSR ready
NOTE
During a hitless-upgrade on FSX platforms, the new active module will always perform the 55 second
deferred hardware cleanup even if the NSR is enabled.
Configuration considerations
•
•
Multicast NSR is not supported for IPv6 multicast.
When multicast NSR is turned on, unicast routing must be protected by NSR or graceful restart on
all multicast VRFs.
Configuring multicast non-stop routing
To globally enable multicast non-stop routing for all VRFs, enter the ip multicast-nonstop-routing
command on the CLI as shown in this example:
Device(config)#ip multicast-nonstop-routing
76
FastIron Ethernet Switch IP Multicast Configuration Guide
53-1003085-02
Download from Www.Somanuals.com. All Manuals Search And Download.
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.
PIM v4 is configured
MCASTv4 protocol receives switchover event
Mcastv4 protocol switchover done
PIM v6 is configured
MCASTv6 protocol receives switchover event
Mcastv6 protocol switchover done
The syslog message shows the state transition of multicast NSR as the standby module takes over as
the active module. The multicast data traffic will continue to flow during state transition.
Displaying the multicast NSR status
To display the multicast nonstop routing (NSR) status, enter the following command:
Device# show ip pim nsr
Global Mcast NSR Status
NSR: ON
Switchover In Progress Mode: FALSE
The following table displays the output from the show ip pim nsr command.
Field
Description
NSR
The NSR field indicates whether the ip multicast-nonstop-routing command is
enabled (ON) or disabled (OFF).
Switchover in Progress
Mode
The Switchover in Progress Mode field indicates whether the multicast traffic is in the
middle of a switchover (displaying a TRUE status), or not (displaying a FALSE status).
Displaying counter and statistic information for multicast NSR
To display multicast NSR counter and statistic information, enter the following command.
device#show ip pim counter nsr
Mcache sync (entity id: 203)
pack: 0
unpack: 0
ack: 0
RPset sync (entity id: 201)
pack: 0
unpack: 0
ack: 0
BSR status (entity id: 202)
pack: 1
unpack: 0
ack: 1
Syntax: show ip pim [vrf vrf_name ] counter nsr
FastIron Ethernet Switch IP Multicast Configuration Guide
53-1003085-02
77
Download from Www.Somanuals.com. All Manuals Search And Download.
Passive multicast route insertion
The vrf parameter allows you to display IP PIM counters for the VRF instance specified by the vrf-
name 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.
unpack
The number of NSR sync messages that are received and unpacked by the standby module.
The number of NSR sync acknowledgements received by the active module.
ack
RPset sync
BSR status
The RPset sync queue that carries the NSR sync message for RPset update.
The BSR status sync queue that carries the NSR sync message for BSR information update.
Passive multicast route insertion
To prevent unwanted multicast traffic from being sent to the CPU, PIM routing and passive multicast
route insertion (PMRI) can be used together to ensure that multicast streams are forwarded out only
ports with interested receivers and unwanted traffic is dropped in hardware on Layer 3 switches.
PMRI enables a Layer 3 switch running PIM Sparse to create an entry for a multicast route (for
example, (S,G)), with no directly attached clients or when connected to another PIM device (transit
network).
When a multicast stream has no output interfaces (OIF), the Layer 3 switch can drop packets in
hardware if the multicast traffic meets either of the following conditions:
In PIM-SM:
•
‐
‐
The route has no OIF and
If directly connected source passed source reverse-path forwarding (RPF) check and
completed data registration with reverse path (RP) or
‐
If non directly connected source passed source RPF check.
In PIM-DM:
•
‐
‐
‐
The route has no OIF and
passed source RPF check and
Device has no downstream PIM neighbor.
If the OIF is inserted after the hardware-drop entries are installed, the hardware entries will be updated
to include the OIFs.
NOTE
Disabling hardware-drop does not immediately take away existing hardware-drop entries, they will go
through the normal route aging processing when the traffic stops.
78
FastIron Ethernet Switch IP Multicast Configuration Guide
53-1003085-02
Download from Www.Somanuals.com. All Manuals Search And Download.
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.
device(config)#show ip pim sparse
Global PIM Sparse Mode Settings
Maximum Mcache
: 12992
: 30
Current Count
: 0
Hello interval
Join/Prune interval
Neighbor timeout
Inactivity interval
Prune Wait Interval
: 105
: 180
: 3
: 60
Hardware Drop Enabled : Yes
Bootstrap Msg interval : 60
Register Suppress Time : 60
Candidate-RP Msg interval : 60
Register Probe Time : 10
Register Suppress interval : 60
SPT Threshold : 1
Register Stop Delay
SSM Enabled
SSM Group Range
Route Precedence
: 10
: Yes
: 232.0.0.0/8
: mc-non-default mc-default uc-non-default uc-default
IP multicast boundaries
The IP multicast boundary feature is designed to selectively allow or disallow multicast flows to
configured interfaces.
The ip multicast-boundary command allows you to configure a boundary on a PIM enabled interface
by defining which multicast groups may not forward packets over a specified interface. This includes
incoming and outgoing packets. By default, all interfaces that are enabled for multicast are eligible to
participate in a multicast flow provided they meet the multicast routing protocol’s criteria for participating
in a flow.
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 IGMP 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. In such a situation,
the ACL would prevail and the port will not be added to the relevant entries.
Either standard or extended ACLs can be used with the multicast boundary feature. When a
standard ACL is used, the address specified is treated as a group address and NOT a source
address.
FastIron Ethernet Switch IP Multicast Configuration Guide
53-1003085-02
79
Download from Www.Somanuals.com. All Manuals Search And Download.
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.
Configuring multicast boundaries
To define boundaries for PIM enabled interfaces, enter a commands such as the following.
device(config)# interface ve 40
device(config-vif-40)#ip multicast-boundary MyBrocadeAccessList
Syntax: [no] ip multicast-boundary acl-spec
Use the acl-spec parameter to define the number or name identifying an access list that controls the
range of group addresses affected by the boundary.
Use the no ip multicast boundary command to remove the boundary on a PIM enabled interface.
The ACL, MyBrocadeAccessList can be configured using standard ACL syntax. Some examples of
how ACLs can be used to filter multicast traffic are as follows:
Standard ACL to permit multicast traffic
To permit multicast traffic for group 225.1.0.2 and deny all other traffic, enter the following command.
device(config)# access-list 10 permit host 225.1.0.2
device(config)# access-list 10 deny any
Extended ACL to deny multicast traffic
To deny multicast data traffic from group 225.1.0.1 and permit all other traffic, enter the following
command.
device(config)# access-list 101 deny ip any host 225.1.0.1
device(config)# access-list 101 permit ip any any
Extended ACL to permit multicast traffic
To permit multicast data traffic from source 97.1.1.50 for group 225.1.0.1 and deny all other traffic,
enter the following commands:
Device(config)# access-list 102 permit ip host 97.1.1.50 host 225.1.0.1
Device(config)# access-list 102 deny ip any any
Displaying multicast boundaries
To display multicast boundary information, enter the show ip pim interface command.
device# show ip pim interface ethernet 1/1/7
Flags
: SM - Sparse Mode v2, DM - Dense Mode v2, P - Passive Mode
---------+---------------+----+---+-----------------------+---+---------+-------
+------+---------+
Interface|Local
DR | Override
|Mode|St |
Designated Router
|TTL|Multicast| VRF |
80
FastIron Ethernet Switch IP Multicast Configuration Guide
53-1003085-02
Download from Www.Somanuals.com. All Manuals Search And Download.
PIM Dense
|Address
|
|
|Address
Port|Thr|Boundary |
|
Prio | Interval
---------+---------------+----+---+-----------------------+---+---------+-------
+------+---------+
e1/1/7 30.0.0.1
3000ms
SM
Ena Itself
1 None
default
1
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.
The ethernet parameter specifies the physical port.
The loopback parameter specifies the loopback port.
The veparameter specifies a virtual interface.
The tunnel parameter specifies a GRE tunnel interface that is being configured. The GRE tunnel
interface is enabled under the device PIM configuration.
The following table describes the output from the show ip pim interface ethernet command.
Field
Description
Interface
Local Address
Mode
Name of the interface.
IP address of the interface.
PIM mode, dense or sparse..
PIM status for this interface, enabled or disabled.
St
Designated Router Address, Port Address, port number of the designated router.
TTL Thr
Time to live threshold. Multicast packets with TTL less than this threshold value
are not be forwarded on this interface.
Multicast boundary ACL, if one exists.
Name of the VRF.
Multicast Boundary
VRF
DR Prio
Designated router priority assigned to this inerface.
Effective override interval in milliseconds.
Override Interval
PIM Dense
NOTE
95 for information about PIM Sparse.
FastIron Ethernet Switch IP Multicast Configuration Guide
53-1003085-02
81
Download from Www.Somanuals.com. All Manuals Search And Download.
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. The Sparse Mode is suitable
for sparsely populated multicast groups with the focus on WAN.
PIM uses the IP routing table instead of maintaining its own, thereby being routing protocol
independent.
Initiating PIM multicasts on a network
Once PIM is enabled on each device, a network user can begin a video conference multicast from the
capable device interface, the interface checks its IP routing table to determine whether the interface
that received the message provides the shortest path back to the source. If the interface does provide
the shortest path back to the source, the multicast packet is then forwarded to all neighboring PIM
devices. Otherwise, the multicast packet is discarded and a prune message is sent back upstream.
which it receives from the server, to its downstream nodes, R2, R3, and R4. Device R4 is an
intermediate device with R5 and R6 as its downstream devices. Because R5 and R6 have no
downstream interfaces, they are leaf nodes. The receivers in this example are those workstations that
are resident on devices R2, R3, and R6.
Pruning a multicast tree
As multicast packets reach these leaf devices, the devices check their IGMP databases for the group.
If the group is not in the IGMP database of the device, the device discards the packet and sends a
prune message to the upstream device. The device that discarded the packet also maintains the prune
state for the source, group (S,G) pair. The branch is then pruned (removed) from the multicast tree. No
further multicast packets for that specific (S,G) pair will be received from that upstream device until the
prune state expires. You can configure the PIM Prune Timer (the length of time that a prune state is
considered valid).
For example, in the “Transmission of multicast packets from the source to host group members” figure,
the sender with address 207.95.5.1 is sending multicast packets to the group 229.225.0.1. If a PIM
device receives any groups other than that group, the device discards the group and sends a prune
message to the upstream PIM device.
In the “Pruning leaf nodes from a multicast tree” figure, device R5 is a leaf node with no group
members in its IGMP database. Therefore, the device must be pruned from the multicast tree. R5
sends a prune message upstream to its neighbor device R4 to remove itself from the multicast delivery
tree and install a prune state, as seen in the “Pruning leaf nodes from a multicast tree” figure. Device 5
will not receive any further multicast traffic until the prune age interval expires.
When a node on the multicast delivery tree has all of its downstream branches (downstream
interfaces) in the prune state, a prune message is sent upstream. In the case of R4, if both R5 and R6
are in a prune state at the same time, R4 becomes a leaf node with no downstream interfaces and
82
FastIron Ethernet Switch IP Multicast Configuration Guide
53-1003085-02
Download from Www.Somanuals.com. All Manuals Search And Download.
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.
FIGURE 3 Transmission of multicast packets from the source to host group members
FIGURE 4 Pruning leaf nodes from a multicast tree
FastIron Ethernet Switch IP Multicast Configuration Guide
53-1003085-02
83
Download from Www.Somanuals.com. All Manuals Search And Download.
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. Since the forwarding state for this entry is in a prune
state, R4 sends a graft to R1. Once R4 has joined the tree, R4 along with R6 once again receive
multicast packets.
Prune and graft messages are continuously used to maintain the multicast delivery tree. You do not
need to configure anything.
84
FastIron Ethernet Switch IP Multicast Configuration Guide
53-1003085-02
Download from Www.Somanuals.com. All Manuals Search And Download.
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.
Configure the IP interfaces that will use PIM.
Enable PIM locally on the ports that have the IP interfaces you configured for PIM.
Suppose you want to initiate the use of desktop video for fellow users on a sprawling campus network.
All destination workstations have the appropriate hardware and software but the devices that connect
the various buildings need to be configured to support PIM multicasts from the designated video
conference server as shown in the “Pruning leaf nodes from a multicast tree” figure.
PIM is enabled on each of the devices shown in the “Pruning leaf nodes from a multicast tree” figure, on
which multicasts are expected. You can enable PIM on each device independently or remotely from one
of the devices with a Telnet connection. Follow the same steps for each device. All changes are
dynamic.
Globally enabling and disabling PIM
To globally enable PIM, enter the following command.
Device(config)# router pim
Syntax:[no] router pim
The [no] router pim command behaves in the following manner:
•
•
Entering a router pim command to enable PIM does not require a software reload.
Entering a no router pim command removes all configuration for PIM multicast on a device (router
pim level) only.
Enabling PIM for a specified VRF
To enable PIM for the VRF named "blue", use the following commands.
Device(config)# router pim vrf blue
Syntax: [no] router pim [ vrf vrf-name ]
The vrf parameter allows you to configure PIM (PIM-DM and PIM-SM) on the virtual routing and
forwarding instance (VRF) specified by the vrf-name variable. All PIM parameters available for the
default device instance are configurable for a VRF-based PIM instance.
FastIron Ethernet Switch IP Multicast Configuration Guide
53-1003085-02
85
Download from Www.Somanuals.com. All Manuals Search And Download.
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.
Device(config)# router pim
Device(config)# int e 1/3
Device(config-if-e10000-1/3)# ip address 207.95.5.1/24
Device(config-if-e10000-1/3)# ip pim
Device(config-if-e10000-1/3)# write memory
Device(config-if-e10000-1/3)# end
Syntax: [no] ip pim [version 1 | 2 ]
The version 1 | 2 parameter specifies the PIM DM version. The default version is 2.
If you have enabled PIM version 1 but need to enable version 2 instead, enter either of the following
commands at the configuration level for the interface.
Device(config-if-e10000-1/1)# ip pim version 2
Device(config-if-e10000-1/1)# no ip pim version 1
To disable PIM DM on the interface, enter the following command.
Device(config-if-e10000-1/1)# no ip pim
Modifying PIM global parameters
PIM global parameters come with preset values. The defaults work well in most networks, but you can
modify the following parameters if necessary:
•
•
•
•
•
•
Neighbor timeout
Hello timer
Prune timer
Prune wait timer
Graft retransmit timer
Inactivity timer
Modifying neighbor timeout
Neighbor timeout is the interval after which a PIM device will consider a neighbor to be absent.
Absence of PIM hello messages from a neighboring device indicates that a neighbor is not present.
The interval can be set between 3 and 65535 seconds, and it should not be less than 3.5 times the
hello timer value. The default value is 105 seconds.
To apply a PIM neighbor timeout value of 360 seconds to all ports on the device operating with PIM,
enter the following.
Device(config)# router pim
Device(config-pim-router)# nbr-timeout 360
Syntax: [no] nbr-timeout seconds
86
FastIron Ethernet Switch IP Multicast Configuration Guide
53-1003085-02
Download from Www.Somanuals.com. All Manuals Search And Download.
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.
Device(config)# router pim
Device(config-pim-router)# hello-timer 120
Syntax: [no] hello-timer 10-3600
The default is 30 seconds.
Modifying prune timer
This parameter defines how long a PIM device will maintain a prune state for a forwarding entry.
The first received multicast interface is forwarded to all other PIM interfaces on the device. If there is no
presence of groups on that interface, the leaf node sends a prune message upstream and stores a
prune state. This prune state travels up the tree and installs a prune state.
A prune state is maintained until the prune timer expires or a graft message is received for the
forwarding entry. The default value is 180 seconds.
To set the PIM prune timer to 90, enter the following.
Device(config)# router pim
Device(config-pim-router)# prune-timer 90
Syntax: [no] prune-timer seconds
The default is 180 seconds. The range is 60 to 3600 seconds.
Modifying the prune wait timer
The prune-wait command allows you to configure the amount of time a PIM device will wait before
stopping traffic to neighbor devices that do not want the traffic. The value can be from zero to 30
seconds. The default is three seconds. A smaller prune wait value reduces flooding of unwanted traffic.
A prune wait value of zero causes the PIM device to stop traffic immediately upon receiving a prune
message. If there are two or more neighbors on the physical port, then the prune-wait command
should not be used because one neighbor may send a prune message while the other sends a join
message at the same time, or within less than three seconds.
To set the prune wait time to zero, enter the following commands.
Device(config)#router pim
Device(config-pim-router)#prune-wait 0
Syntax: [no] prune-wait seconds
The seconds can be 0 - 30. A value of 0 causes the PIM device to stop traffic immediately upon
receiving a prune message. The default is 3 seconds.
To view the currently configured prune wait time, enter the show ip pim dense command as described
in the Displaying basic PIM Dense configuration information” section.
FastIron Ethernet Switch IP Multicast Configuration Guide
53-1003085-02
87
Download from Www.Somanuals.com. All Manuals Search And Download.
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.
Device(config)# router pim
Device(config-pim-router)# graft-retransmit-timer 90
Syntax: [no] graft-retransmit-timer seconds
The default is 180 seconds. The range is from 60 to 3600 seconds.
Modifying inactivity timer
The device deletes a forwarding entry if the entry is not used to send multicast packets. The PIM
inactivity timer defines how long a forwarding entry can remain unused before the device deletes it.
To apply a PIM inactivity timer of 90 seconds to all PIM interfaces, enter the following.
Device(config)# router pim
Device(config-pim-router)# inactivity-timer 90
Syntax: [no] inactivity-timer seconds
The default is 180 seconds. The range is from 60 to 3600 seconds.
Selection of shortest path back to source
By default, when a multicast packet is received on a PIM-capable interface in a multi-path topology,
the interface checks its IP routing table to determine the shortest path back to the source. If the
alternate paths have the same cost, the first alternate path in the table is picked as the path back to
the source. For example, in the following example, the first four routes have the same cost back to the
source. However, 137.80.127.3 is chosen as the path to the source since it is the first one on the list.
The device rejects traffic from any port other than Port V11 on which 137.80.127.3 resides
Total number of IP routes: 19
Type Codes - B:BGP D:Connected I:ISIS S:Static R:RIP O:OSPF Cost - Dist/Metric
Destination
..
172.17.41.4
172.17.41.4
172.17.41.4
172.17.41.4
172.17.41.8
Gateway
Port
Cost
Type
137.80.127.3
137.80.126.3
137.80.129.1
137.80.128.3
0.0.0.0
v11
v10
v13
v12
1/2
2
2
2
2
1
O
O
O
O
D
Failover time in a multi-path topology
When a port in a multi-path topology fails, multicast devices, depending on the routing protocol being
used, take a few seconds to establish a new path, if the failed port is the input port of the downstream
device.
88
FastIron Ethernet Switch IP Multicast Configuration Guide
53-1003085-02
Download from Www.Somanuals.com. All Manuals Search And Download.
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. To set a DR
priority higher than the default value of 1, use the ip pim dr-priority command as shown:
device(config-if-e10000-3/24)# ip pim dr-priority 50
Syntax: [no] ip pim dr-priority priority-value
The priority-value variable is the value that you want to set for the DR priority. Optional values are: 0 -
65535. The default value is 1.
The no option removes the command and sets the DR priority back to the default value of 1.
The following information may be useful for troubleshooting.
1. If more than one device has the same DR priority on a subnet (as in the case of default DR priority
on all), the device with the numerically highest IP address on that subnet is elected as the DR.
2. The DR priority information is used in the DR election ONLY IF ALL the PIM devices connected to
the subnet support the DR priority option. If there is at least one PIM device on the subnet that
does not support this option, then the DR election falls back to the backwards compatibility mode in
which the device with the numerically highest IP address on the subnet is declared the DR
regardless of the DR priority values.
Displaying basic PIM Dense configuration information
To display PIM Dense configuration information, enter the following command at any CLI level.
Device(config)# show ip pim dense
Global PIM Dense Mode Settings
Maximum Mcache
: 12992
: 30
Current Count
: 2
Hello interval
Neighbor timeout
Inactivity interval
Prune Wait Interval
Prune Age
: 105
: 180
: 3
Join/Prune interval
Hardware Drop Enabled
: 60
: Yes
Graft Retransmit interval : 180
Route Precedence
: 180
: mc-non-default mc-default uc-non-default uc-default
Syntax: show ip pim [ vrf vrf-name ] dense
The vrf keyword allows you to display PIM dense configuration information for the VRF instance
identified by the vrf-name variable.
This display shows the following information.
Field
Description
Maximum Mcache
Current Count
Hello interval
The maximum number multicast cache entries allowed on the device.
The number of multicast cache entries currently used.
How frequently the device sends hello messages out the PIM dense interfaces.
The interval after which a PIM device will consider a neighbor to be absent.
How long a PIM device will maintain a prune state for a forwarding entry.
Neighbor timeout
Join/Prune interval
FastIron Ethernet Switch IP Multicast Configuration Guide
53-1003085-02
89
Download from Www.Somanuals.com. All Manuals Search And Download.
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.
Graft Retransmit interval The interval between the transmission of graft messages.
Prune Age
The number of packets the device sends using the path through the RP before switching
to using the SPT path.
Route Precedence
The route precedence configured to control the selection of routes based on the four
route types:
•
•
•
•
Non-default route from the mRTM
Default route from the mRTM
Non-default route from the uRTM
Default route from the uRTM
Displaying all multicast cache entries in a pruned state
Use the following command to display all multicast cache entries that are currently in a pruned state
and have not yet aged out.
Device(config)# show ip pim prune
1 (104.1.1.2 231.0.1.1):
e2/2,2/2(150)
2 (108.1.1.100 231.0.1.1):
e2/2,2/2(150)
3 (104.1.1.2 231.0.1.2):
e2/2,2/2(150)
4 (108.1.1.100 231.0.1.2):
e2/2,2/2(150)
5 (108.1.1.100 231.0.1.3):
e2/2,2/2(150)
6 (104.1.1.2 231.0.1.4):
e2/2,2/2(150)
7 (108.1.1.100 231.0.1.4):
e2/2,2/2(150)
8 (104.1.1.2 231.0.1.5):
e2/2,2/2(150)
9 (108.1.1.100 231.0.1.5):
e2/2,2/2(150)
Total Prune entries: 9
Syntax: show ip pim [vrf vrf-name ] prune
Displaying all multicast cache entries
You can use the following command to display all multicast cache entries.
Brocade(config)# show ip pim mcache
90
FastIron Ethernet Switch IP Multicast Configuration Guide
53-1003085-02
Download from Www.Somanuals.com. All Manuals Search And Download.
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 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: 20
1 (140.140.140.3, 225.0.0.1) in v340 (tag e8/1), Uptime 00:00:02 Rate 0 (DM)
Source is directly connected
Flags (0x200004e1) DM HW FAST TAG
fast ports: ethe 4/6 ethe 8/26
AgeSltMsk: 1, L2 FID: 8188, DIT: 3 , AvgRate: 0, profile: none
Forwarding_oif: 2
L3 (HW) 2:
TR(e4/6,e4/6)(VL330), 00:00:02/0, Flags: IM
e8/26(VL310), 00:00:02/0, Flags: IM
Src-Vlan: 340
Syntax: show ip pim mcache [source-address | group-address | counts | dense | dit-idx | g_entries |
receiver | sg_entries | sparse | ssm ]
The source-address parameter selects the multicast cache source address.
The group-address parameter selects the multicast cache group address.
The counts keyword indicates the count of entries.
The dense keyword displays only the PIM Dense Mode entries.
The dit-idx variable allows you to display all entries that match a specified dit.
The g_entries keyword displays only the (*, G) entries.
The receiver keyword allows you to display all entries that egress a specified interface.
The sg_entries keyword displays only the (S, G) entries.
The sparse keyword displays only the PIM Sparse Mode entries.
The ssm keyword displays only the SSM entries.
TABLE 1 Output fields from the show ip pim mcache command
Field
Description
Total entries in
mcache
Shows the total number of PIM mcache entries
MJ
MI
Membership Join
Membership Include
ME
Membership Exclude - Legend for the mcache entry printed once per page, it gives the
explanation of each of the flags used in the entry.
BR
BA
Blocked RPT
Blocked Assert
FastIron Ethernet Switch IP Multicast Configuration Guide
53-1003085-02
91
Download from Www.Somanuals.com. All Manuals Search And Download.
IPv4 Multicast Protocols
TABLE 1 Output fields from the show ip pim mcache command (Continued)
Field
Description
BF
Blocked Filter
BI
Blocked IIF
Uptime
Rate
Shows the software entry uptime.
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.
upstream neighbor
Flags
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 Represent Entry flags in hex format in the braces. And indicates the meaning of the
flags set in abbreviated string whose explanations are as follows. Only shows the flags
which are set.
SM - Shows If the entry is created by PIM Sparse Mode
DM - Shows If DM mode entry is enabled
SSM - Shows If the SSM mode entry is enabled
RPT - Shows If the entry is on the Rendezvous Point (RP)
SPT - Shows If the entry is on the source tree
LSRC - Shows If the source is in a directly-connected interface
LRcv - Shows If the receiver is directly connected to the router
REG - if the data registration is in progress
L2REG - if the source is directly connected to the router
REGSUPP - if the register suppression timer is running
RegProbe
HW - Shows If the candidate for hardware forwarding is enabled
FAST - Shows If the resources are allocated for hardware forwarding
TAG - Shows If there is a need for allocating entries from the replication table
MSDPADV - Shows If RP is responsible for the source and must be advertised to its
peers.
NEEDRTE - Shows If there is no route to the source and RP is available
PRUNE - Shows If PIM DM Prune to upstream is required
RP
Show the IP address of the RP.
Shows forwarding port mask.
fast ports
92
FastIron Ethernet Switch IP Multicast Configuration Guide
53-1003085-02
Download from Www.Somanuals.com. All Manuals Search And Download.
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
DIT
Hardware Resource allocated for the traffic switched to receivers in the ingress VLAN.
Hardware Resource allocated for router receivers.
RegPkt
Shows the number of packets forwarded due to the Register decapsulation. This field is
displayed only on the active module. This field displays only those entries for which the
device is the RP. However, for a PIM DM entry the RegPkt field is not displayed for the
(S,G) entries on the active module.
AvgRate
Profile
Shows the average rate of packets ingressing for this entry over a 30 second period. This
field is displayed only on the active module for all entries that are hardware programmed
(the fwd_fast flag is set on the active module).
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. And each section
has Format of L3/L2/Blocked followed by (HW/SW) followed by count of the number of OIF
in each section.
Additionally, each section displays the OIFs one per line. And shows the OIF in the format
eth/Tr(Vlan) followed by uptime/expiry time, followed by the Flags associated with each
OIF.
L3
Shows whether the traffic is routed out of the interface.
Shows whether the traffic is switched out of the interface.
Shows whether the entry is hardware forwarded.
Shows whether the entry is software forwarded.
Shows the outgoing interface on the specified VLAN.
L2
HW
SW
Eth/Tr(VL1)
FastIron Ethernet Switch IP Multicast Configuration Guide
53-1003085-02
93
Download from Www.Somanuals.com. All Manuals Search And Download.
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. Legend of this shown at the top of each entry
IM - Immediate
IH - Inherited
MJ - Membership Join
MI - Membership Include
ME - Membership Exclude
BR - Blocked due to SG RPT
BA - Blocked due to Assert
BF - Blocked due to Filter
BI - Blocked IIF (Incoming interface) matches OIF
Src-VLAN
VLAN associated with the ingress interface.
You can use the following command to filter the output to display only entries that egress port ethernet
1/1.
device#show ip pim mcache receiver ethernet 1/1
You can use the following command to filter the output to display only the Source Specific Multicast
(SSM) routes in the mcache.
device#show ip pim mcache ssm
You can use the following command to filter the output to display only the Sparse Mode routes in the
mcache.
device#show ip pim mcache sparse
You can use the following command to filter the output to display only the Dense Mode routes in the
mcache.
device#show ip pim mcache dense
You can use the following command to filter the output to display only the entries matching a specific
source.
device#show ip pim mcache 1.1.1.1
You can use the following command to filter the output to display only the entries matching a specific
group.
device#show ip pim mcache 239.1.1.1
Displaying information across VRFs
Use the following command to display information across all active VRFs.
Brocade#show ip pim all-vrf
94
FastIron Ethernet Switch IP Multicast Configuration Guide
53-1003085-02
Download from Www.Somanuals.com. All Manuals Search And Download.
PIM Sparse
bsr
Bootstrap router
flow-count Show flowcache counters
hw-resource PIM hw resources
interface
neighbor
resource
rp-set
PIM interface
PIM neighbor states
PIM resources
List of rendezvous point (RP) candidates
Active multicast traffic
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.
In a PIM Sparse network, a PIM Sparse device 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).
PIM Sparse devices are organized into domains. A PIM Sparse domain is a contiguous set of devices
simple example of a PIM Sparse domain. This example shows three devices configured as PIM Sparse
devices. The configuration is described in detail following the figure.
FIGURE 5 Example PIM Sparse domain
PIM Sparse device types
Devices that are configured with PIM Sparse interfaces also can be configured to fill one or more of the
following roles:
FastIron Ethernet Switch IP Multicast Configuration Guide
53-1003085-02
95
Download from Www.Somanuals.com. All Manuals Search And Download.
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. The PIM Sparse protocol uses an election
process to select one of the candidate BSRs as the BSR for the domain. The BSR with the
highest BSR priority (a user-configurable parameter) is elected. If the priorities result in a tie, then
page 95, PIM Sparse device B is the BSR. Port 2/2 is configured as a candidate BSR.
•
RP - The RP is the meeting point for PIM Sparse sources and receivers. A PIM Sparse domain
can have multiple RPs, but each PIM Sparse multicast group address can have only one active
RP. PIM Sparse devices learn the addresses of RPs and the groups for which they are
responsible from messages that the BSR sends to each of the PIM Sparse devices. In the
candidate Rendezvous Point (RP). To enhance overall network performance, the Brocade device
uses the RP to forward only the first packet from a group source to the group’s receivers. After the
first packet, the Brocade device calculates the shortest path between the receiver and source (the
Shortest Path Tree, or SPT) and uses the SPT for subsequent packets from the source to the
receiver. The Brocade 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 5 on page 95 shows two paths for packets from the source for group 239.255.162.1 and a
receiver for the group. The source is attached to PIM Sparse device A and the recipient is attached to
PIM Sparse device C. PIM Sparse device B in is the RP for this multicast group. As a result, the
default path for packets from the source to the receiver is through the RP. However, the path through
the RP sometimes is not the shortest path. In this case, the shortest path between the source and the
receiver is over the direct link between device A and device C, which bypasses the RP (device B).
To optimize PIM traffic, the protocol contains a mechanism for calculating the Shortest Path Tree
(SPT) between a given source and receiver. PIM Sparse devices can use the SPT as an alternative to
using the RP for forwarding traffic from a source to a receiver. By default, the Brocade device forwards
the first packet they receive from a given source to a given receiver using the RP path, but forward
subsequent packets from that source to that receiver through the SPT. In Figure 5 on page 95, device
A forwards the first packet from group 239.255.162.1’s source to the destination by sending the packet
to device B, which is the RP. Device B then sends the packet to device C. For the second and all
future packets that device A receives from the source for the receiver, device A forwards them directly
to device C using the SPT path.
Configuring PIM Sparse
To configure a Brocade device for PIM Sparse, perform the following tasks:
•
•
Configure the following global parameter:
Enable the PIM Sparse mode of multicast routing.
Configure the following interface parameters:
‐
‐
‐
‐
Configure an IP address on the interface
Enable PIM Sparse.
Identify the interface as a PIM Sparse border, if applicable.
•
Configure the following PIM Sparse global parameters:
96
FastIron Ethernet Switch IP Multicast Configuration Guide
53-1003085-02
Download from Www.Somanuals.com. All Manuals Search And Download.
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.
Current limitations
The implementation of PIM Sparse in the current software release has the following limitations:
•
•
PIM Sparse and regular PIM (dense mode) cannot be used on the same interface.
You cannot configure or display PIM Sparse information using the Web Management Interface.
(You can display some general PIM information, but not specific PIM Sparse information.)
Configuring global PIM Sparse parameters
To configure basic global PIM Sparse parameters, enter commands such as the following on each
Brocade device within the PIM Sparse domain.
Device(config)# router pim
Syntax: [no] router pim
NOTE
You do not need to globally enable IP multicast routing when configuring PIM Sparse.
The command in this example enables IP multicast routing, and enables the PIM Sparse mode of IP
multicast routing. The command does not configure the Brocade device as a candidate PIM Sparse
Bootstrap Router (BSR) and candidate Rendezvous Point (RP). You can configure a device as a PIM
Sparse device without configuring the Brocade device as a candidate BSR and RP. However, if you do
configure the device as one of these, it is recommended that you configure the device as both of these.
Refer to the “Configuring BSRs” section.
Entering a no router pim command does the following:
•
•
Disables PIM.
Removes all configuration for PIM multicast on a Brocade device (router pim level) only.
Enabling PIM Sparse for a specified VRF
To enable PIM for the VRF named "blue", use the following commands.
Device(config)# router pim vrf blue
Syntax: [no] router pim [vrf vrf-name ]
The vrf parameter allows you to configure PIM (PIM-DM and PIM-SM) on the virtual routing instance
(VRF) specified by the vrf-name variable. All PIM parameters available for the default router instance
are configurable for a VRF-based PIM instance.
The no router pim vrf command behaves in the following manner:
FastIron Ethernet Switch IP Multicast Configuration Guide
53-1003085-02
97
Download from Www.Somanuals.com. All Manuals Search And Download.
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.
device(config)# interface ethernet 2/2
device(config-if-e10000-2/2)# ip address 207.95.7.1 255.255.255.0
device(config-if-e10000-2/2)# ip pim-sparse
Syntax: [no] ip pim-sparse
The commands in this example add an IP interface to port 2/2, then enable PIM Sparse on the
interface.
If the interface is on the border of the PIM Sparse domain, you also must enter the following
command.
device(config-if-e10000-2/2)# ip pim border
Syntax: [no] ip pim border
Configuring BSRs
In addition to the global and interface parameters described in the previous sections, you need to
identify an interface on at least one device as a candidate PIM Sparse Bootstrap router (BSR) and
candidate PIM Sparse Rendezvous Point (RP).
NOTE
It is possible to configure the device as only a candidate BSR or RP, but it is recommended that you
configure the same interface on the same device as both a BSR and an RP.
This section describes how to configure BSRs. Refer to the “Configuring RPs” section for instructions
on how to configure RPs.
To configure the device as a candidate BSR, enter commands such as the following.
Device(config)# router pim
Device(config-pim-router)# bsr-candidate ethernet 2/2 30 255
These commands configure the PIM Sparse interface on port 2/2 as a BSR candidate, with a hash
mask length of 30 and a priority of 255.
Syntax: [no] bsr-candidate ethernet slot / portnum | loopback num | ve numhash-mask-length [
priority ]
The ethernet slot / portnum, loopback num, and ve num parameters specify the interface. The device
will advertise the IP address of the specified interface as a candidate BSR.
•
•
•
Enter ethernet slot / portnum for a physical interface (port).
Enter ve num for a virtual interface.
Enter loopback num for a loopback interface.
98
FastIron Ethernet Switch IP Multicast Configuration Guide
53-1003085-02
Download from Www.Somanuals.com. All Manuals Search And Download.
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.
Configuring RPs
Enter a command such as the following to configure the device as a candidate RP.
device(config-pim-router)# rp-candidate ethernet 2/2
Syntax: [no] rp-candidate ethernet slot / portnum | loopback num | ve num
The ethernetslot /portnum | loopbacknum | venum parameters specify the interface. The device will
advertise the IP address of the specified interface as a candidate RP.
•
•
•
Enter ethernetslot /portnum for a physical interface (port).
Enter venum for a virtual interface.
Enter loopbacknum for a loopback interface.
By default, this command configures the device as a candidate RP for all group numbers beginning with
224. As a result, the device is a candidate RP for all valid PIM Sparse group numbers. You can change
this by adding or deleting specific address ranges. Consider the following when configuring the RP.
•
When the candidate RP is configured, before explicitly specifying the groups that it serves, the c-rp
does, by default, serve all the groups in the PIMSM multicast range, but this includes all groups
beginning with 224.x.x.x all the way up to 239.x.x.x. This is reflected in the "rp-candidate add
224.0.0.0 4" line displayed as part of the runtime configs. This entry will be referred to as the
DEFAULT PREFIX.
•
•
•
When any group prefix is explicitly added (and the 224.0.0.0/4 prefix itself can also be explicitly
added through CLI), the default prefix is implicitly removed. Now, the only groups served by the
candidate RP, are the groups that have been explicitly added.
All explicitly added groups can be removed using the "delete" option or "no ... add" option.
However, once all the explicitly added groups are deleted from the Candidate RP group prefix list,
the default prefix becomes active once more. This default group prefix CANNOT BE REMOVED.
It is not possible to punch holes in the group prefix range. For instance executing
rp-candidate add 228.0.0.0/16
and then,
rp-candidate delete 228.0.1.0/24
is not permissible. It cannot be used to ensure that the rp-candidate will serve all group prefixes in the
228.0.0.0/16 range except those in the 228.0.1.0/24 range.
The following example narrows the group number range for which the device is a candidate RP by
explicitly adding a range.
device(config-pim-router)# rp-candidate add 224.126.0.0 16
Syntax: [no] rp-candidate add group-addr mask-bits
The group-addrmask-bits specifies the group address and the number of significant bits in the subnet
mask. In this example, the device is a candidate RP for all groups that begin with 224.126. When you
FastIron Ethernet Switch IP Multicast Configuration Guide
53-1003085-02
99
Download from Www.Somanuals.com. All Manuals Search And Download.
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.
Updating PIM-Sparse forwarding entries with new RP configuration
If you make changes to your static RP configuration, the entries in the PIM-Sparse multicast
forwarding table continue to use the old RP configuration until they are aged out.
The clear 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 a PIM sparse static multicast forwarding table with new RP configuration,
enter the following command at the privileged EXEC level of the CLI.
device(config)# clear ip pim rp-map
Syntax: clear ip pim [ vrf vrf-name ] rp-map
Use the vrf option to clear the PIM sparse static multicast forwarding table for a VRF instance
specified by the vrf-name variable.
Statically specifying the RP
It is recommended that you use the PIM Sparse protocol’s RP election process so that a backup RP
can automatically take over if the active RP router becomes unavailable. However, if you do not want
the RP to be selected by the RP election process but instead you want to explicitly identify the RP by
P address, use the rp-address command.
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 PIM Sparse devices within the PIM Sparse domain.
Make sure the device is on the backbone or is otherwise well connected to the rest of the network.
To specify the IP address of the RP, enter commands such as the following.
device(config)# router pim
device(config-pim-router)# rp-address 207.95.7.1
Syntax: [no] rp-address ip-addr
The ip-addr parameter specifies the IP address of the RP.
The command in this example identifies the device interface at IP address 207.95.7.1 as the RP for
the PIM Sparse domain. The device uses the specified RP and ignore group-to-RP mappings received
from the BSR.
100
FastIron Ethernet Switch IP Multicast Configuration Guide
53-1003085-02
Download from Www.Somanuals.com. All Manuals Search And Download.
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.
The optional static RP ACL can be configured as a standard ACL or as an extended ACL. For an
extended ACL, the destination filter will be used to derive the multicast group range and all other filters
are ignored. The content of the ACL needs to be defined in the order of prefix length; the longest prefix
must be placed at the top of the ACL definition.
If there are overlapping group ranges among the static RPs, the static RP with the longest prefix match
is selected. If more than one static RP covers the exact same group range, the highest IP static RP will
be used.
Configuration considerations:
•
•
The Static RP has higher precedence over RP learnt from the BSR.
There is a limit of 64 static RPs in the systems.
Configuring an ACL based RP assignment
To configure an ACL based RP assignment, enter commands such as the following.
device(config)# router pim
device(config-pim-router)# rp-address 130.1.1.1 acl1
Syntax: [no] rp-address ip_address [acl_name_or_id ]
Use the ip address parameter to specify the IP address of the device you want to designate as an RP
device.
Use the acl name or id (optional) parameter to specify the name or ID of the ACL that specifies which
multicast groups use this RP.
Displaying the static RP
Use the show ip pim rp-set command to display static RP and the associated group ranges.
device(config)# show ip pim rp-set
Static RP and associated group ranges
-------------------------------------
Static RP count: 4
130.1.1.1
120.1.1.1
120.2.1.1
124.1.1.1
Number of group prefixes Learnt from BSR: 0
No RP-Set present.
Use the show ip pim rp-map command to display all current multicast group addresses to RP address
mapping.
device(config)# show ip pim rp-map
Number of group-to-RP mappings: 5
-------------------------------------------
S.No Group address
RP address
FastIron Ethernet Switch IP Multicast Configuration Guide
53-1003085-02
101
Download from Www.Somanuals.com. All Manuals Search And Download.
PIM Passive
-------------------------------------------
1
2
3
4
5
225.1.1.1
225.1.1.2
225.1.1.3
225.1.1.4
225.1.1.5
25.0.0.25
25.0.0.25
25.0.0.25
25.0.0.25
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. No PIM control
packets are sent or processed (if received), but hosts can still send and receive multicast traffic and
IGMP control traffic on that interface. Also, PIM Passive prevents any malicious router from taking
over as the designated router (DR), which can prevent all hosts on the LAN from joining multicast
traffic outside the LAN.
The following guidelines apply to PIM Passive:
1. This is a Layer 3 interface [Ethernet/Ve] level feature.
2. Since the loopback interfaces are never used to form PIM neighbors, this feature is not supported
on loopback interface.
3. Both PIM SM and PIM DM modes support this feature.
4. Applying the PIM Passive on an interface requires PIM to be enabled on that interface.
5. The sent and received statistics of a PIM Hello message are not changed for an interface, while it
is configured as PIM passive.
To enable PIM Passive on an interface, enter the following commands:
device# config term
device(config)#router pim
device(config-pim-router)#exit
device(config)#interface ethernet 2
device(config-if-e1000-2)#ip pim
device(config-if-e1000-2)#ip pim passive
device(config-if-e1000-2)#exit
device(config)#interface ve 2
device(config-vif-2)#ip pim-sparse
device(config-vif-2)#ip pim passive
device(config-vif-2)#exit
Syntax: [no] ip pim passive
Multicast Outgoing Interface (OIF) list optimization
Each multicast route entry maintains a list of outgoing interfaces (OIF List) to which an incoming
multicast data packet matching the route is replicated. In hardware-forwarded route entries, these OIF
lists are stored inside the hardware in replication tables which are limited in size. In many deployment
scenarios, more than one multicast route can have identical OIF lists and can optimize usage of the
replication table entries by sharing them across multiple multicast routes.
Multicast OIF list optimization keeps track of all the OIF lists in the system. It manages the hardware
replication resources optimally, in real time, by dynamically assigning or re-assigning resources to
multicast route entries to suit their current OIF list requirements, while maximizing resource sharing.
102
FastIron Ethernet Switch IP Multicast Configuration Guide
53-1003085-02
Download from Www.Somanuals.com. All Manuals Search And Download.
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.
device(config)#show default values
System Parameters
pim-hw-mcache
Default
1024
Maximum
6144
Current
1500
Configured
1500
Displaying PIM resources
To display the hardware resource information, such as hardware allocation, availability, and limit for
software data structure, enter the show ip pim resource command.
device# show ip pim resource
Global PIM Parameters :-
GLOBAL Ipv4 MULTICAST CLASS Size:16811 bytes
GLOBAL Ipv4 PIM CLASS Size:1065 bytes
MULTICAST IPV4 CLASS Num alloc:5, System max:129, Size:1228 bytes
PIM IPV4 CLASS Num alloc:5, System max:129, Size:50440
Vrf Instance : default-vrf
--------------------------------------
alloc in-use avail get-fail
limit get-mem size init
NBR list
256
256
64
3
4
0
0
0
0
0
0
1
0
2
0
3
3
0
2
0
253
252
64
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
512
1536
4
90 256
43 256
RP set list
5032
Static RP
64
0
36
64
LIF Entry
512
64
512
64
512
0
41 512
Anycast RP
64
0
190
64
64 256
34 128
29 1024
28 256
28 280
timer
256
128
1024
256
280
56
197
2000
1024
256
256
1024
256
128
1024
255
280
54
197
1997
1021
256
254
1024
59392
29696
48960
59392
64960
12992
45704
464000
237568
59392
59392
237568
4
prune
0
pimsm J/P elem
Timer Data
1258
2
20
2
mcache SLIB Sync
mcache
796
56
64 197
66 2000
78 1024
24 256
46 256
43 1024
graft if no mcache
HW replic vlan
HW replic port
pim/dvm intf. group
pim/dvm global group
repl entry(Global)
0
4
4
0
2
4
IGMP Resources(All Vrfs):
groups
256
2
2
1
0
0
0
254
254
55
0
0
0
0
0
0
4096
4096
2
2
210 256
142 256
group-memberships
sources
256
56
12992
12992
256
606
0
59
81
56
56
client sources
ssm-map
56
56
256
256
256
256
0
18 256
ssm-map-sources
59392
0 1024 256
Hardware-related Resources:
Total (S,G) entries 1
Total SW FWD entries 0
Total sw w/Tag MVID entries 0
Total sw w/Tag invalid MVID entries 0
Total HW FWD entries 1
FastIron Ethernet Switch IP Multicast Configuration Guide
53-1003085-02
103
Download from Www.Somanuals.com. All Manuals Search And Download.
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.
System max Maximum number of VRFs allowed in the system.
Size
Size of one instance of the resource in bytes.
Number of nodes of that data that are currently allocated in memory.
Number of allocated nodes in use.
alloc
in-use
avail
get-fail
limit
Number of allocated nodes are not in use.
Number of allocation failures for this node.
Maximum number of nodes that can be allocated for a data structure. This may or may not be
configurable, depending on the data structure
get-mem
size
Number of successful allocations for this node.
Size of the node in bytes.
init
Number of nodes that are allocated during initialization time.
To display usage and fail-count information for SG entries on each VRF, use the show ip pim all-vrf
hw-resource command.
device# show ip pim all-vrf hw-resource
VRF Usage
Fail
default-vrf
blue
3072
3072
8
0
-------------------------------
Total usage
6144
System-max limit for SG entries: 6144
Syntax: show ip 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 ip pim all-vrf hw-resource command.
104
FastIron Ethernet Switch IP Multicast Configuration Guide
53-1003085-02
Download from Www.Somanuals.com. All Manuals Search And Download.
Displaying PIM Sparse configuration information and statistics
TABLE 3 Output from the show ip pim all-vrf hw-resource command
Field
VRF
Description
Name of the VRF.
Usage
Fail
Number of allocated SG entries in this VRF.
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.
Displaying PIM Sparse configuration information and statistics
You can display the following PIM Sparse information:
•
•
•
•
•
•
•
•
•
•
•
•
Basic PIM Sparse configuration information
Group information
BSR information
Candidate RP information
RP-to-group mappings
RP information for a PIM Sparse group
RP set list
PIM neighbor information
The PIM flow cache
The PIM multicast cache
PIM traffic statistics
PIM counter statistics
Displaying basic PIM Sparse configuration information
To display PIM Sparse configuration information, enter the following command at any CLI level.
Device(config)# show ip pim sparse
Global PIM Sparse Mode Settings
Maximum Mcache
: 12992
: 30
Current Count
: 2
Hello interval
Join/Prune interval
Neighbor timeout
Inactivity interval
Prune Wait Interval
: 105
: 180
: 3
: 60
Hardware Drop Enabled : Yes
Bootstrap Msg interval : 60
Register Suppress Time : 60
Candidate-RP Msg interval : 60
Register Probe Time : 10
Register Suppress interval : 60
SPT Threshold : 1
Register Stop Delay
SSM Enabled
SSM Group Range
Route Precedence
: 10
: Yes
: 232.0.0.0/8
: mc-non-default mc-default uc-non-default uc-default
Syntax: show ip pim [vrf vrf-name ] sparse
FastIron Ethernet Switch IP Multicast Configuration Guide
53-1003085-02
105
Download from Www.Somanuals.com. All Manuals Search And Download.
IPv4 Multicast Protocols
The vrf keyword allows you to display PIM sparse configuration information for the VRF instance
identified by the vrf-name variable.
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...
Global PIM Sparse mode settings
Maximum mcache
Current Count
Hello interval
Maximum number of multicast cache entries.
Number of multicast cache entries used.
How frequently the device sends IPIM Sparse hello messages to its PIM Sparse
neighbors. This field shows the number of seconds between hello messages. PIM
Sparse routers use hello messages to discover one another.
Neighbor timeout
Number of seconds the device waits for a hello message from a neighbor before
determining that the neighbor is no longer present and is not removing cached PIM
Sparse forwarding entries for the neighbor. Default is 105 seconds.
Join or Prune interval How frequently the device sends IPv6 PIM Sparse Join or Prune messages for the
multicast groups it is forwarding. This field shows the number of seconds between Join or
Prune messages.
The device sends Join or Prune messages on behalf of multicast receivers that want to
join or leave an PIM Sparse group. When forwarding packets from PIM Sparse sources,
the device sends the packets only on the interfaces on which it has received join
requests in Join or Prune messages for the source group.
Inactivity interval
Number of seconds a forwarding entry can remain unused before the router deletes it.
Default is 180 sec.
Hardware Drop
Enabled
Indicates whether hardware drop is enabled or disabled.
To prevent unwanted multicast traffic from being sent to the CPU, PIM Routing and
Passive Multicast Route Insertion (PMRI) can be used together to ensure that multicast
streams are only forwarded out ports with interested receivers and unwanted traffic is
dropped in the hardware on Layer 3 Switches.
Prune Wait Interval
Number of seconds a PIM device waits before stopping traffic to neighbor devices that do
not want the traffic. Range is from zero to three seconds. Default is three seconds.
106
FastIron Ethernet Switch IP Multicast Configuration Guide
53-1003085-02
Download from Www.Somanuals.com. All Manuals Search And Download.
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.
NOTE
This field contains a value only if an interface on the device is elected to be the BSR.
Otherwise, the field is blank.
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. A lower value means more frequent register bursts at RP,
while a higher value means longer join latency for new receivers. Default: 60 seconds.
Register Probe Time
Register Stop Delay
Number of seconds the PIM router waits for a register-stop from an RP before it
generates another NULL register to the PIM RP. Default is 10 seconds.
Register stop message. Default is 10 seconds.
Register Suppress
interval
Number of seconds that it takes the designated router to send a Register-encapsulated
date to the RP after receiving a Register-Stop message. Default is 60 seconds.
SSM Enabled
SPT threshold
If yes, source-specific multicast is configured globally on this router.
Number of packets the device sends using the path through the RP before switching to
the SPT path. Default is 1 packet.
SSM Group Range
Route Precedence
Source-specific multicast group range.
The route precedence configured to control the selection of routes based on the four
route types:
•
•
•
•
Non-default route from the mRTM
Default route from the mRTM
Non-default route from the uRTM
Default route from the uRTM
Displaying a list of multicast groups
To display PIM group information, enter the following command at any CLI level.
Device(config)# show ip pim group
Total number of groups for VRF default-vrf: 7
1
Group 226.0.34.0
Group member at e2/9: v59
Group member at e1/16: v57
Group 226.0.77.0
2
FastIron Ethernet Switch IP Multicast Configuration Guide
53-1003085-02
107
Download from Www.Somanuals.com. All Manuals Search And Download.
Displaying BSR information
Group member at e2/9: v59
Group member at e1/16: v57
Group 226.0.120.0
Group member at e2/9: v59
Group member at e1/16: v57
Group 226.0.163.0
Group member at e2/9: v59
Group member at e1/16: v57
Group 226.0.206.0
Group member at e2/9: v59
Group member at e1/16: v57
Group 226.0.249.0
3
4
5
6
7
Group member at e2/9: v59
Group member at e1/16: v57
Group 226.0.30.0
Group member at e2/9: v59
Group member at e1/16: v57
device(config)#
Syntax: show ip pim [vrf vrf-name ] group
The vrf keyword allows you to display PIM group information for the VRF instance identified by the vrf-
name variable.
The following table describes the output from this command:
TABLE 5 Output from the show ip pim group command
This field...
Displays...
Total number of Groups Lists the total number of IP multicast groups the device is forwarding.
NOTE
This list can include groups that are not PIM Sparse groups. If interfaces on the device
are configured for regular PIM (dense mode), these groups are listed too.
Index
Group
Ports
The index number of the table entry in the display.
The multicast group address
The device ports connected to the receivers of the groups.
Displaying BSR information
To display BSR information, enter the following command at any CLI level.
device(config)# show ip pim bsr
PIMv2 Bootstrap information for Vrf Instance : default-vrf
------------------------------------------------------------------------------
This system is the Elected BSR
BSR address: 1.51.51.1. Hash Mask Length 32. Priority 255.
Next bootstrap message in 00:01:00
Configuration:
Candidate loopback 2 (Address 1.51.51.1). Hash Mask Length 32. Priority 255.
Next Candidate-RP-advertisment in 00:01:00
RP: 1.51.51.1
group prefixes:
224.0.0.0 / 4
Candidate-RP-advertisement period: 60
108
FastIron Ethernet Switch IP Multicast Configuration Guide
53-1003085-02
Download from Www.Somanuals.com. All Manuals Search And Download.
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.
Next Candidate-RP-advertisment in 00:00:30
RP: 1.51.51.3
group prefixes:
224.0.0.0 / 4
Candidate-RP-advertisement period: 60
device(config)#
Syntax: show ip pim [vrf vrf-name ] bsr
The vrf keyword allows you to display BSR information for the VRF instance identified by the vrf-
namevrf-name variable.
The following table describes the output from this command.
TABLE 6 Output from the show ip pim bsr command
This field...
BSR address
BSR priority
Displays...
The IP address of the interface configured as the PIM Sparse Bootstrap Router (BSR).
The priority assigned to the interface for use during the BSR election process. During
BSR election, the priorities of the candidate BSRs are compared and the interface with
the highest BSR priority becomes the BSR.
Hash mask length
The number of significant bits in the IP multicast group comparison mask. This mask
determines the IP 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 IP multicast group
number.
NOTE
This field appears only if this device is a candidate BSR.
Next bootstrap message Indicates how much time will pass before the BSR sends the next bootstrap message.
in
The time is displayed in "hh:mm:ss" format.
NOTE
This field appears only if this device is the BSR.
Next Candidate-RP-
advertisement message
in
Indicates how much time will pass before the BSR sends the next candidate PR
advertisement message. The time is displayed in "hh:mm:ss" format.
NOTE
This field appears only if this device is a candidate BSR.
FastIron Ethernet Switch IP Multicast Configuration Guide
53-1003085-02
109
Download from Www.Somanuals.com. All Manuals Search And Download.
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.
Candidate-RP-
Indicates how frequently the BSR sends candidate RP advertisement messages.
advertisement period
NOTE
This field appears only if this device is a candidate BSR.
Displaying candidate RP information
To display candidate RP information, enter the following command at any CLI level.
device# show ip pim rp-candidate
Next Candidate-RP-advertisement in 00:00:10
RP: 207.95.7.1
group prefixes:
224.0.0.0 / 4
Candidate-RP-advertisement period: 60
This example show information displayed on a device that is a candidate RP. The next example shows
the message displayed on a device that is not a candidate RP.
device# show ip pim rp-candidate
This system is not a Candidate-RP.
Syntax: show ip pim [vrf vrf-name ] rp-candidate
This command displays candidate RP information for the VRF instance identified by the vrf-name
variable.
The following table describes the output from this command.
110
FastIron Ethernet Switch IP Multicast Configuration Guide
53-1003085-02
Download from Www.Somanuals.com. All Manuals Search And Download.
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.
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 RP.
Candidate-RP-advertisement Indicates how frequently the BSR sends candidate RP advertisement messages.
period
NOTE
This field appears only if this device is a candidate RP.
Displaying RP-to-group mappings
To display RP-to-group-mappings, enter the following command at any CLI level.
device# show ip pim rp-map
Number of group-to-RP mappings: 6
Group address
RP address
-------------------------------
1 239.255.163.1 99.99.99.5
2 239.255.163.2 99.99.99.5
3 239.255.163.3 99.99.99.5
4 239.255.162.1 99.99.99.5
5 239.255.162.2 43.43.43.1
6 239.255.162.3 99.99.99.5
Syntax: show ip pim [vrf vrf-name ] rp-map
The vrf option allows you to display candidate RP-to-group mappings for the VRF instance identified by
the vrf-name variable.
The following table describes the output from this command.
FastIron Ethernet Switch IP Multicast Configuration Guide
53-1003085-02
111
Download from Www.Somanuals.com. All Manuals Search And Download.
Displaying RP Information for a PIM Sparse group
TABLE 8 Output of the show ip pim rp-map command
This field...
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.
Displays...
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.7.1, v2
Info source: 207.95.7.1, via bootstrap
Syntax: show ip pim [vrf vrf-name ] rp-hash group-addr
The vrf option allows you to display RP information for the VRF instance identified by the vrf-name
variable.
The group-addr parameter is the address of a PIM Sparse IP multicast group.
The following table describes the output from this command.
TABLE 9 Output from the show ip pim command
This field... Displays...
RP
Indicates the IP address of the Rendezvous Point (RP) for the specified PIM Sparse group.
Info source Indicates the source of the RP information. It can be a static-RP configuration or learned via the
bootstrap router. If RP information is learned from the boot strap, the BSR IP address is also
displayed.
Displaying the RP set list
To display the RP set list for the device elected as BSR, enter the following command at any CLI level.
device(config)# show ip pim rp-set
Static RP
---------
Static RP count: 2
1.51.51.4
1.51.51.5
Number of group prefixes Learnt from BSR: 1
Group prefix = 224.0.0.0/4
# RPs: 2
priority=0 age=60
priority=0 age=30
RP 1: 1.51.51.1
RP 2: 1.51.51.3
holdtime=150
holdtime=150
To display the RP set list for devices that are not elected as BSR, enter the following command at any
CLI level.
Brocade(config)# show ip pim rp-set
Static RP
---------
Static RP count: 2
1.51.51.4
1.51.51.5
112
FastIron Ethernet Switch IP Multicast Configuration Guide
53-1003085-02
Download from Www.Somanuals.com. All Manuals Search And Download.
Displaying multicast neighbor information
Number of group prefixes Learnt from BSR: 1
Group prefix = 224.0.0.0/4
# RPs received: 2
# RPs expected: 2
RP 1: 1.51.51.1
RP 2: 1.51.51.3
priority=0
priority=0
age=60
age=30
holdtime=150
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.
TABLE 10 Output from the show ip pim vrf rp-set command
This field...
Displays...
Number of group prefixes The number of PIM Sparse group prefixes for which the RP is responsible.
Group prefix
Indicates the multicast groups for which the RP listed by the previous field is a
candidate RP.
RPs expected or received Indicates how many RPs were expected and received in the latest bootstrap message.
RP num
Indicates the RP number. If there are multiple RPs in the PIM Sparse domain, a line of
information for each RP is listed, in ascending numerical order.
priority
The RP priority of the candidate RP. During the election process, the candidate RP with
the highest priority is elected as the RP.
age
The age (in seconds) of this RP-set.
holdtime
Indicates the time in seconds for which this rp-set information is valid.
If this rp-set information is not received from BSR within the holdtime period, the rp-set
information is aged out and deleted.
Displaying multicast neighbor information
To display information about PIM neighbors, enter the following command at any CLI level.
device(config)# show ip pim nbr
--------+--------+---------------+--------+---+---------+---------+-----
+----------------+-----------+----+
Port
|PhyPort |Neighbor
|VRF
|Holdtime|T |PropDelay|Override |Age |
UpTime
|Prio
|
|
|
|sec
|Bit|msec
|msec
|sec
|
|
--------+--------+---------------+--------+---+---------+---------+-----
+----------------+-----------+----+
v2
e1/1
e2/2
e1/4
e1/1
2.1.1.2
105
105
105
105
1
1
1
1
500
500
500
500
3000
3000
3000
3000
0
00:44:10
v4
default-vrf 1
4.1.1.2
10
0
00:42:50
v5
default-vrf 1
5.1.1.2
00:44:00
v22
default-vrf 1
22.1.1.1
0
00:44:10
default-vrf 1
Total Number of Neighbors : 4
device(config)#
Syntax: show ip pim [vrf vrf-name ] neighbor
FastIron Ethernet Switch IP Multicast Configuration Guide
53-1003085-02
113
Download from Www.Somanuals.com. All Manuals Search And Download.
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.
When there is a virtual interface, this is the physical port to which the neighbor is connected.
The IP interface of the PIM neighbor.
Phyport
Neighbor
Holdtime sec Indicates how many seconds the neighbor wants this device to hold the entry for this neighbor in
memory. The neighbor sends the Hold Time in Hello packets:
•
•
If the device receives a new Hello packet before the Hold Time received in the previous
packet expires, the device updates its table entry for the neighbor.
If the device does not receive a new Hello packet from the neighbor before the Hold time
expires, the device assumes the neighbor is no longer available and removes the entry for the
neighbor.
Age sec
The number of seconds since the device received the last hello message from the neighbor.
UpTime sec The number of seconds the PIM neighbor has been up. This timer starts when the device receives
the first Hello messages from the neighbor.
VRF
The VRF in which the interface is configured. This can be a VRF that the port was assigned to or
the default VRF of the device.
Priority
The DR priority that is used in the DR election process. This can be a configured value or the
default value of 1.
Displaying the PIM multicast cache
To display the PIM multicast cache, enter the following command at any CLI level.
Brocade(config)# show ip pim mcache 10.140.140.14 230.1.1.9
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 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: 20
1 (10.140.140.14, 230.1.1.9) in v1001 (tag e4/29), Uptime 00:03:12, Rate 0 (SM)
upstream neighbor 10.11.11.13
Flags (0x600680e1) SM SPT LRCV HW FAST TAG
fast ports: ethe 4/29 ethe 5/2
AgeSltMsk: 1, L2 FID: 8188, DIT: 8 , AvgRate: 0, profile: none
Forwarding_oif: 3, Immediate_oif: 0, Blocked_oif: 0
L3 (HW) 2:
114
FastIron Ethernet Switch IP Multicast Configuration Guide
53-1003085-02
Download from Www.Somanuals.com. All Manuals Search And Download.
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 | dit-
idx 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 vrf-
name variable.
The source-address parameter selects the multicast cache source address.
The group-address parameter selects the multicast cache group address.
The counts keyword indicates the count of entries.
The dense keyword displays only the PIM Dense Mode entries.
The dit-idx variable allows you to display all entries that match a specified dit.
The g_entries keyword displays only the (*, G) entries.
The receiver keyword allows you to display all entries that egress a specified interface.
The sg_entries keyword displays only the (S, G) entries.
The sparse keyword displays only the PIM Sparse Mode entries.
The ssm keyword displays only the SSM entries.
The following table describes the output from this command.
TABLE 12 Output fields from the show ip pim mcache command
Field
Description
Total entries in mcache Shows the total number of PIM mcache entries
MJ
MI
Membership Join
Membership Include
ME
Membership Exclude - Legend for the mcache entry printed once per page, it gives the
explanation of each of the flags used in the entry.
BR
Blocked RPT
BA
Blocked Assert
BF
Blocked Filter
BI
Blocked IIF
Uptime
Rate
Shows the entry uptime
Shows the Rate at which packets are ingressing for this entry
FastIron Ethernet Switch IP Multicast Configuration Guide
53-1003085-02
115
Download from Www.Somanuals.com. All Manuals Search And Download.
IPv4 Multicast Protocols
TABLE 12 Output fields from the show ip pim mcache command (Continued)
Field
Description
upstream neighbor
Flags
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 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. Only shows the
flags which are set.
SM - Shows If the entry is created by PIM Sparse Mode
DM - Shows If DM mode entry is enabled
SSM - Shows If the SSM mode entry is enabled
RPT - Shows If the entry is on the Rendezvous Point (RP)
SPT - Shows If the entry is on the source tree
LSRC - Shows If the source is in a directly-connected interface
LRcv - Shows If the receiver is directly connected to the router
REG - if the data registration is in progress
L2REG - if the source is directly connected to the router
REGSUPP - if the register suppression timer is running
RegProbe
HW - Shows If the candidate for hardware forwarding is enabled
FAST - Shows If the resources are allocated for hardware forwarding
TAG - Shows If there is a need for allocating entries from the replication table
MSDPADV - Shows If RP is responsible for the source and must be advertised to its
peers.
NEEDRTE - Shows If there is no route to the source and RP is available
PRUNE - Shows If PIM DM Prune to upstream is required
RP
Show the IP address of the RP.
fast ports
AgeSltMsk
L2 FID
Shows forwarding port mask.
Shows the slot number on which active module expects ingress traffic.
Shows the hardware resource allocated for the traffic switched to receivers in the
ingress VLAN.
DIT
Shows the hardware resource allocated for routed receivers.
RegPkt
AvgRate
Shows Count of Packets forwarded due to the Register decapsulation.
Shows the average Rate of packets ingressing for this entry over 30 seconds.
116
FastIron Ethernet Switch IP Multicast Configuration Guide
53-1003085-02
Download from Www.Somanuals.com. All Manuals Search And Download.
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. And each
section has Format of L3/L2/Blocked followed by (HW/SW) followed by count of the
number of OIF in each section.
Additionally, each section displays the OIFs one per line. And shows the OIF in the
format eth/Tr(Vlan) followed by uptime/expiry time, followed by the Flags associated with
each OIF.
L3
Shows whether the traffic is routed out of the interface.
Shows whether the traffic is switched out of the interface.
Shows whether the entry is hardware forwarded.
L2
HW
SW
Shows whether the entry is software forwarded
Eth/Tr(VL1)
Flags (explanation of
Shows the outgoing interface on the specified VLAN.
Shows the flags set in each of the Outgoing interface in abbreviated string format whose
flags in the OIF section) explanations are as below. Legend of this shown at the top of each entry
IM - Immediate
IH - Inherited
MJ - Membership Join
MI - Membership Include
ME - Membership Exclude
BR - Blocked due to SG RPT
BA - Blocked due to Assert
BF - Blocked due to Filter
BI - Blocked IIF (Incoming interface) matches OIF
Src-Vlan
Shows the VLAN associated with the ingress interface.
Displaying the PIM multicast cache for DIT
To display the PIM multicast cache for a specified dit, enter the following command at any CLI level.
Brocade#show ip pim mcache dit-idx 2
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
FastIron Ethernet Switch IP Multicast Configuration Guide
53-1003085-02
117
Download from Www.Somanuals.com. All Manuals Search And Download.
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 mcache: 30
1
2
3
(20.20.20.100, 225.1.1.1) in v220 (tag e1/1/13), Uptime 07:12:07, Rate 0 (SM)
upstream neighbor 220.220.220.1
Flags (0x200680e1) SM SPT LRCV HW FAST TAG
fast ports: ethe 1/1/11
AgeSltMsk: 1, L2 FID: 105c, DIT:
2 , AvgRate: 0, profile: none
Forwarding_oif: 1, Immediate_oif: 0, Blocked_oif: 0
L3 (HW) 1:
e1/1/11(VL40), 07:12:07/0, Flags: MJ
Src-Vlan: 220
(20.20.20.100, 225.1.1.2) in v220 (tag e1/1/13), Uptime 00:01:00, Rate 0 (SM)
upstream neighbor 220.220.220.1
Flags (0x200680e1) SM SPT LRCV HW FAST TAG
fast ports: ethe 1/1/11
AgeSltMsk: 1, L2 FID: 105c, DIT:
2 , AvgRate: 0, profile: none
Forwarding_oif: 1, Immediate_oif: 0, Blocked_oif: 0
L3 (HW) 1:
e1/1/11(VL40), 00:01:00/0, Flags: MJ
Src-Vlan: 220
(20.20.20.100, 225.1.1.3) in v220 (tag e1/1/13), Uptime 00:01:00, Rate 0 (SM)
upstream neighbor 220.220.220.1
Flags (0x200680e1) SM SPT LRCV HW FAST TAG
fast ports: ethe 1/1/11
AgeSltMsk: 1, L2 FID: 105c, DIT:
2 , AvgRate: 0, profile: none
Forwarding_oif: 1, Immediate_oif: 0, Blocked_oif: 0
L3 (HW) 1:
e1/1/11(VL40), 00:01:00/0, Flags: MJ
Src-Vlan: 220
Syntax: show ip pim [vrf vrf-name ] mcache dit-idx dit
The dit variable allows you to display an entry that matches a specified dit.
Clearing the PIM forwarding cache
You can clear the PIM forwarding cache using the following command.
device# clear ip pim cache
Syntax: clear ip pim [vrf vrf-name ] cache
Use the vrf option to clear the PIM forwarding cache for a VRF instance specified by the vrf-name
variable.
Displaying PIM traffic statistics
To display PIM traffic statistics, enter the following command at any CLI level.
device(config)# show ip pim traffic
Port
HELLO
JOIN-PRUNE ASSERT
REGISTER REGISTER BOOTSTRAP CAND. RP Err
GRAFT(DM) STOP(SM) MSGS (SM) ADV. (SM)
-------+---------+-----------+---------+---------+---------+---------+---------+---
Rx
Rx
Rx
Rx
Rx
Rx
Rx
Rx
118
FastIron Ethernet Switch IP Multicast Configuration Guide
53-1003085-02
Download from Www.Somanuals.com. All Manuals Search And Download.
IPv4 Multicast Protocols
------+---------+-----------+---------+---------+---------+---------+---------+---
v30
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
v50
2526
2531
2531
HELLO
1260
1263
1263
1
v150
v200
Port
0
0
JOIN-PRUNE ASSERT
REGISTER REGISTER BOOTSTRAP CAND. RP Err
GRAFT(DM) STOP(SM) MSGS (SM) ADV. (SM)
-------+---------+-----------+---------+---------+---------+---------+---------+---
Tx
Tx
Tx
Tx
Tx
Tx
Tx
------+---------+-----------+---------+---------+---------+---------+---------+---
v30
v50
v150
v200
2528
2540
2529
2529
0
0
0
0
0
0
0
0
0
0
0
0
0
0
2
1262
1262
0
0
0
0
1263
0
0
Brocade#show ip pim traffic rx
Port
HELLO
JOIN-PRUNE ASSERT
REGISTER REGISTER BOOTSTRAP CAND. RP Err
GRAFT(DM) STOP(SM) MSGS (SM) ADV. (SM)
-------+---------+-----------+---------+---------+---------+---------+---------+---
Rx
Rx
Rx
Rx
Rx
Rx
Rx
Rx
------+---------+-----------+---------+---------+---------+---------+---------+---
v30
v50
v150
v200
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
2526
2531
2531
1260
1263
1263
1
0
0
Brocade#show ip pim traffic tx
Port
HELLO
JOIN-PRUNE ASSERT
REGISTER REGISTER BOOTSTRAP CAND. RP Err
GRAFT(DM) STOP(SM) MSGS (SM) ADV. (SM)
-------+---------+-----------+---------+---------+---------+---------+---------+---
Tx
Tx
Tx
Tx
Tx
Tx
Tx
------+---------+-----------+---------+---------+---------+---------+---------+---
v30
v50
v150
v200
2528
2540
2529
2530
0
0
0
0
0
0
0
0
0
0
0
0
0
0
2
1262
1262
0
0
0
0
1263
0
0
Brocade#show ip pim traffic join-prune
Port Packet
-----+---------+---------+---------+---------+----------
Rx Rx Rx Rx Rx
Join
Prune
Avg Aggr Last Aggr
-----+---------+---------+---------+---------+----------
v30
v50
0
0
0
0
1
0
0
0
1
0
0
1260
1260
0
0
v150 0
0
0
v200 0
0
Port Packet
Join
Prune
Avg Aggr Last Aggr
-----+---------+---------+---------+---------+----------
Tx
Tx
Tx
Tx
Tx
-----+---------+---------+---------+---------+----------
v30
v50
v150 0
v200 0
0
0
0
1
0
0
0
1
0
0
0
1
0
0
1263
1262
0
0
Brocade#show ip pim traffic join-prune rx
Port Packet
-----+---------+---------+---------+---------+----------
Rx Rx Rx Rx Rx
Join
Prune
Avg Aggr Last Aggr
-----+---------+---------+---------+---------+----------
v30
v50
v150 0
v200 0
0
0
0
0
0
0
0
1
0
0
0
1
0
0
1260
1260
0
0
Brocade#show ip pim traffic join-prune tx
Port Packet
-----+---------+---------+---------+---------+----------
Tx Tx Tx Tx Tx
Join
Prune
Avg Aggr Last Aggr
-----+---------+---------+---------+---------+----------
v30
v50
v150 0
v200 0
0
0
0
1
0
0
0
1
0
0
0
1
0
0
1264
1263
0
0
Syntax: show ip pim [vrf vrf-name ] traffic [join-prune | rx | tx ]
•
•
•
•
vrf --PIM traffic statistics for the VRF instance identified by vrf-name
join-prune --Join/prune statistics.
rx --Received PIM traffic statistics.
tx --Transmitted PIM traffic statistics.
FastIron Ethernet Switch IP Multicast Configuration Guide
53-1003085-02
119
Download from Www.Somanuals.com. All Manuals Search And Download.
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...
Port
Displays...
The port or virtual interface on which the PIM interface is configured.
The number of PIM Hello messages sent or received on the interface.
The number of Join or Prune messages sent or received on the interface.
Hello
J or P
NOTE
Unlike PIM dense, PIM Sparse uses the same messages for Joins and Prunes.
Register
The number of Register messages sent or received on the interface.
The number of Register Stop messages sent or received on the interface.
The number of Assert messages sent or received on the interface.
The total number of IGMP messages sent and received by the device.
RegStop
Assert
Total Recv or Xmit
Total Discard or chksum The total number of IGMP messages discarded, including a separate counter for those
that failed the checksum comparison.
Clearing the PIM message counters
You can clear the PIM message counters using the following command.
device# clear ip pim traffic
Syntax: clear ip pim [vrf vrf-name ] traffic
Use the vrf option to clear the PIM message counters for a VRF instance specified by the vrf-name
variable.
120
FastIron Ethernet Switch IP Multicast Configuration Guide
53-1003085-02
Download from Www.Somanuals.com. All Manuals Search And Download.
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.
The vrf option to display what PIM sees as the reverse path to the source for a VRF instance specified
by the vrf-name variable.
Configuring Multicast Source Discovery Protocol (MSDP)
The Multicast Source Discovery Protocol (MSDP) is used by Protocol Independent Multicast (PIM)
Sparse devices to exchange source information across PIM Sparse domains. Devices running MSDP
can discover PIM Sparse sources in other PIM Sparse domains.
The following figure shows an example of some PIM Sparse domains. For simplicity, this example
shows one Designated Router (DR), one group source, and one receiver for the group. Only one PIM
Sparse device within each domain needs to run MSDP.
FIGURE 6 PIM Sparse domains joined by MSDP devices
In this example, the source for PIM Sparse multicast group 232.0.1.95 is in PIM Sparse domain 1. The
source sends a packet for the group to its directly attached DR. The DR sends a PIM register message
for this flow to the RPDR. The RP is configured for MSDP, which enables the RP to exchange source
FastIron Ethernet Switch IP Multicast Configuration Guide
53-1003085-02
121
Download from Www.Somanuals.com. All Manuals Search And Download.
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.95
RP address: 206.251.17.41
Figure 6 shows only one peer for the MSDP device (which is also the RP here) in domain 1, so the
Source Active message goes to only that peer. When an MSDP device has multiple peers, it sends a
Source Active message to each of those peers. Each peer sends the Source Advertisement to other
MSDP peers. The RP that receives the Source Active message also sends a Join message to the
source if the RP that received the message has receivers for the group and source.
Peer Reverse Path Forwarding (RPF) flooding
When the MSDP device (also the RP) in domain 2 receives the Source Active message from the peer
in domain 1, the MSDP device in domain 2 forwards the message to all other peers. This propagation
the MSDP device floods the Source Active message it receives from the peer in domain 1 to peers in
domains 3 and 4.
The MSDP device in domain 2 does not forward the Source Active back to the peer in domain 1,
because that is the peer from which the device received the message. An MSDP device never sends a
Source Active message back to the peer that sent it. The peer that sent the message is sometimes
called the "RPF peer". The MSDP device uses the unicast routing table for its Exterior Gateway
Protocol (EGP) to identify the RPF peer by looking for the route entry that is the next hop toward the
source. Often, the EGP protocol is Border Gateway Protocol (BGP) version 4.
NOTE
MSDP depends on BGP for inter-domain operations.
The MSDP routers in domains 3 and 4 also forward the Source Active message to all peers except the
Source Active caching
When an MSDP device that is also an RP receives a Source Active message, it checks the PIM
sparse multicast group table for receivers for that group. If there are receivers for that group being
advertised in the Source Active message, the RP sends a Join message towards the source.
In Figure 6 on page 121, if the MSDP device and RP in domain 4 has a table entry for the receiver, the
RP sends a Join message on behalf of the receiver back through the RPF tree to the source, in this
case the source in domain 1.
Source Active caching is enabled in MSDP on Brocade devices. The RP caches the Source Active
messages it receives even if the RP does not have a receiver for the group. Once a receiver arrives,
the RP can then send a Join to the cached source immediately.
The size of the cache used to store MSDP Source Active messages is 4K. MSDP SA cache size can
be configured using the system-max msdp-sa-cache command. The default value is 4K; the range is
1K to 8K.
122
FastIron Ethernet Switch IP Multicast Configuration Guide
53-1003085-02
Download from Www.Somanuals.com. All Manuals Search And Download.
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.
device(config)# router msdp
Syntax: [no] router msdp
Enabling MSDP for a specified VRF
The vrf parameter allows you to configure MSDP on the virtual routing instance (VRF) specified by the
vrf-name variable. All MSDP parameters available for the default router instance are configurable for a
VRF-based MSDP instance.
To enable MSDP for the VRF named "blue", enter the following commands.
device(config)# router msdp vrf blue
device(config-msdp-router-vrf-blue)
Syntax: [no] router msdp [vrf vrf-name ]
The vrf parameter allows you to configure MSDP on the virtual routing instance (VRF) specified by the
vrf-name variable.
Entering a no router msdp vrf command removes the MSDP configuration from the specified VRF
only.
Configuring MSDP peers
To configure an MSDP peer, enter a command such as the following at the MSDP configuration level.
device(config-msdp-router)# msdp-peer 205.216.162.1
To configure an MSDP peer on a VRF, enter the following commands at the MSDP VRF configuration
level.
device(config)# router msdp vrf blue
device(config-msdp-router-vrf-blue)# msdp-peer 205.216.162.1
Syntax: [no] msdp-peer ip-addr [connect-source loopback num ]
The ip-addr parameter specifies the IP address of the neighbor.
FastIron Ethernet Switch IP Multicast Configuration Guide
53-1003085-02
123
Download from Www.Somanuals.com. All Manuals Search And Download.
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. You should also make sure the IP address of the connect-source loopback is the
source IP address used by the PIM-RP, and the BGP device.
The commands in the following example add an MSDP neighbor and specify a loopback interface as
the source interface for sessions with the neighbor. By default, the device uses the subnet address
configured on the physical interface where you configure the neighbor as the source address for
sessions with the neighbor.
device(config)# interface loopback 1
device(config-lbif-1)# ip address 9.9.9.9/32
device(config)# router msdp
device(config-msdp-router)# msdp-peer 2.2.2.99 connect-source loopback 1
Disabling an MSDP peer
To disable an MSDP peer, enter the following command at the configure MSDP router level.
device(config-msdp-router)# msdp-peer 205.216.162.1 shutdown
To disable the MSDP VRF peer named "blue", enter the following commands.
device(config)# router msdp vrf blue
device(config-msdp-router-vrf-blue)# no msdp-peer 205.216.162.1
Syntax: [no] msdp-peer ip-addr shutdown
The ip-addr parameter specifies the IP address of the MSDP peer that you want to disable.
Designating the interface IP address as the RP IP address
When an RP receives a Source Active message, it checks its PIM Sparse multicast group table for
receivers for the group. If a receiver exists the RP sends a Join to the source.
By default, the IP address included in the RP address field of the SA message is the IP address of the
originating RP. An SA message can use the IP address of any interface on the originating RP. (The
interface is usually a loopback interface.)
To designate an interface IP address to be the IP address of the RP, enter commands such as the
following.
device(config)#
interface loopback 2
device(config-lbif-2)# ip address 2.2.1.99/32
device(config)# router msdp
device(config-msdp-router)# originator-id loopback 2
device(config-msdp-router)# exit
To specify VRF information, enter the following commands at the MSDP VRF configuration level.
device(config)#
interface loopback 2
device(config-lbif-2)# ip address 2.2.1.99/32
124
FastIron Ethernet Switch IP Multicast Configuration Guide
53-1003085-02
Download from Www.Somanuals.com. All Manuals Search And Download.
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.
The type parameter indicates the type of interface used by the RP. Ethernet, loopback and virtual
routing interfaces (ve) can be used.
The number parameter specifies the interface number (for example: loopback number, port number or
virtual routing interface number.)
Filtering MSDP source-group pairs
You can filter individual source-group pairs in MSDP Source-Active messages:
•
•
•
sa-filter in - Filters source-group pairs received in Source-Active messages from an MSDP
neighbor.
sa-filter originate - Filters self-originated source-group pairs in outbound Source-Active messages
sent to an MSDP neighbor
sa-filter out - Filters self-originated and forwarded source-group pairs in outbound Source-Active
messages sent to an MSDP neighbor
Filtering incoming and outgoing Source-Active messages
The following example configures filters for incoming Source-Active messages from three MSDP
neighbors:
•
•
•
For peer 2.2.2.99, all source-group pairs in Source-Active messages from the neighbor are filtered
(dropped).
For peer 2.2.2.97, all source-group pairs except those with source address matching 10.x.x.x and
group address of 235.10.10.1 are permitted.
For peer 2.2.2.96, all source-group pairs except those associated with RP 2.2.42.3 are permitted.
To configure filters for incoming Source-Active messages, enter commands at the MSDP VRF
configuration level.
To configure filters for outbound Source-Active messages, enter the optional out keyword.
Example
The following commands configure extended ACLs. The ACLs will be used in route maps, which will be
used by the Source-Active filters.
device(config)# access-list 123 permit ip 10.0.0.0 0.255.255.255 host 235.10.10.1
device(config)# access-list 124 permit ip host 2.2.42.3 any
device(config)# access-list 125 permit ip any any
The following commands configure the route maps.
device(config)# route-map msdp_map deny 1
device(config-routemap msdp_map)# match ip address 123
device(config-routemap msdp_map)# exit
device(config)# route-map msdp_map permit 2
device(config-routemap msdp_map)# match ip address 125
device(config-routemap msdp_map)# exit
FastIron Ethernet Switch IP Multicast Configuration Guide
53-1003085-02
125
Download from Www.Somanuals.com. All Manuals Search And Download.
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 Source-Active filters.
To specify VRF information, enter the following commands at the MSDP VRF configuration level.
device(config)# router msdp vrf blue
device(config-msdp-router-vrf blue)# sa-filter in 2.2.2.99
device(config-msdp-router-vrf blue)# sa-filter in 2.2.2.97 route-map msdp_map
device(config-msdp-router-vrf blue)# sa-filter in 2.2.2.96 route-map msdp2_map rp-
route-map msdp2_rp_map
The sa-filter commands configure the following filters:
•
sa-filter in 2.2.2.99 - This command drops all source-group pairs received from neighbor
2.2.2.99.
NOTE
The default action is to deny all source-group pairs from the specified neighbor. If you want to permit
some pairs, use route maps.
•
sa-filter in 2.2.2.97 route-map msdp_map - This command drops source-group pairs received
from neighbor 2.2.2.97 if the pairs have source addresses matching 10.x.x.x and group address
235.10.10.1.
•
sa-filter in 2.2.2.96 route-map msdp2_map rp-route-map msdp2_rp_map - This command
accepts all source-group pairs except those associated with RP 2.2.42.3.
Syntax: [no] sa-filter in | originate | out ip-addr [route-map map-tag ] [rp-route-map rp-map-tag]
Selecting the in option applies the filter to incoming Source-Active messages.
Selecting the originate option applies the filter to self-originated outbound Source-Active messages.
Selecting the out option applies the filter to self-originated and forwarded outbound Source-Active
messages.
The ip-addr parameter specifies the IP address of the MSDP neighbor. The filters apply to Source-
Active messages received from or sent to this neighbor.
The route-mapmap-tag parameter specifies a route map. The device applies the filter to source-group
pairs that match the route map. Use the match ip addressacl-id command in the route map to specify
an extended ACL that contains the source addresses.
The rp-route-maprp-map-tag parameter specifies a route map to use for filtering based on
Rendezvous Point (RP) address. Use this parameter if you want to filter Source-Active messages
based on their originating RP. Use the match ip route-sourceacl-id command in the route map to
specify an extended ACL that contains the RP address.
NOTE
The default filter action is deny. If you want to permit some source-group pairs, use a route map.
126
FastIron Ethernet Switch IP Multicast Configuration Guide
53-1003085-02
Download from Www.Somanuals.com. All Manuals Search And Download.
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.255 any
device(config)# access-list 125 permit ip any any
The following commands use the above ACLs to configure a route map which denies source-group with
source address 10.x.x.x and any group address, while permitting everything else.
device(config)# route-map msdp_map deny 1
device(config-routemap msdp_map)# match ip address 123
device(config-routemap msdp_map)# exit
device(config)# route-map msdp_map permit 2
device(config-routemap msdp_map)# match ip address 125
device(config-routemap msdp_map)# exit
The following commands configure the Source-Active filter.
device(config)# router msdp
device(config-msdp-router)# sa-filter originate route-map msdp_map
To specify VRF information, enter the following commands at the MSDP VRF configuration level.
device(config)# router msdp vrf blue
device(config-msdp-router-vrf blue)# sa-filter originate route-map msdp_map
Syntax: [no] sa-filter originate [route-map map-tag ]
The route-mapmap-tag parameter specifies a route map. The router applies the filter to source-group
pairs that match the route map. Use the match ip addressacl-id command in the route map to specify
an extended ACL that contains the source and group addresses.
NOTE
The default filter action is deny. If you want to permit some source-group pairs, use a route map. A
permit action in the route map allows the device to advertise the matching source-group pairs. A deny
action in the route map drops the source-group pairs from advertisements.
Displaying MSDP information
You can display the following MSDP information:
•
Summary information - the IP addresses of the peers, the state of the device MSDP session with
each peer, and statistics for keepalive, source active, and notification messages sent to and
received from each of the peers
•
•
•
VRF Information - Summary information for a specific VRF
Peer information - the IP address of the peer, along with detailed MSDP and TCP statistics
Source Active cache entries - the source active messages cached by the router.
Displaying summary information
To display summary MSDP information, enter the CLI command.
Brocade(config)#show ip msdp vrf blue summary
MSDP Peer Status Summary
FastIron Ethernet Switch IP Multicast Configuration Guide
53-1003085-02
127
Download from Www.Somanuals.com. All Manuals Search And Download.
IPv4 Multicast Protocols
KA: Keepalive SA:Source-Active NOT: Notification
Peer Address
Peer As
State
KA
SA
NOT
Age
In
Out
59
In
0
Out
0
In
0
Out
0
40.40.40.1
40.40.40.3
47.1.1.2
1001
1001
N/A
ESTABLISH 59
ESTABLISH 59
ESTABLISH 59
6
47
47
59
59
0
0
0
0
0
0
0
0
Brocade(config)#
Syntax: show ip msdp summary
The following table describes the output from this command.
TABLE 14 MSDP summary information
This field...
Displays...
Peer address The IP address of the peer interface with the device
State
The state of the MSDP device connection with the peer. The state can be one of the following:
•
•
•
•
CONNECTING - The session is in the active open state.
ESTABLISHED - The MSDP session is fully up.
INACTIVE - The session is idle.
LISTENING - The session is in the passive open state.
KA In
The number of MSDP keepalive messages the MSDP device has received from the peer
The number of MSDP keepalive messages the MSDP device has sent to the peer
The number of source active messages the MSDP device has received from the peer
The number of source active messages the MSDP device has sent to the peer
The number of notification messages the MSDP router has received from the peer
The number of notification messages the MSDP router has sent to the peer
KA Out
SA In
SA Out
NOT In
NOT Out
Displaying peer information
To display MSDP peer information, enter the following command.
Brocade#show ip msdp peer
IP Address
77.1.1.2
State
Mesh-group-name
1
ESTABLISH
Keep Alive Time Hold Time
Age
60
75
53
Message Sent
1240
0
0
0
Message Received
Keep Alive
1239
0
0
Notifications
Source-Active
Lack of Resource
Last Connection Reset Reason:Reason Unknown
Notification Message Error Code Received:Unspecified
Notification Message Error SubCode Received:Not Applicable
Notification Message Error Code Transmitted:Unspecified
Notification Message Error SubCode Transmitted:Not Applicable
Local IP Address: 55.1.1.2
TCP Connection state: ESTABLISHED
Local host: 55.1.1.2, Local Port: 8730
Remote host: 77.1.1.2, Remote Port: 639
ISentSeq: 1207132337 SendNext: 1207132386 TotUnAck:
0
0
SendWnd:
IRcvSeq:
16381 TotSent:
4000739 RcvNext:
49 ReTrans:
4000788 RcvWnd:
16384
128
FastIron Ethernet Switch IP Multicast Configuration Guide
53-1003085-02
Download from Www.Somanuals.com. All Manuals Search And Download.
IPv4 Multicast Protocols
TotalRcv:
49 RcvQue:
0 SendQue:
0
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
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...
Total number of MSDP The number of MSDP peers configured on the device
peers
IP Address
State
The IP address of the peer’s interface with the device
The state of the MSDP device connection with the peer. The state can be one of the
following:
•
•
•
•
CONNECTING - The session is in the active open state.
ESTABLISHED - The MSDP session is fully up.
INACTIVE - The session is idle.
LISTENING - The session is in the passive open state.
Keep Alive Time
Hold Time
The keepalive time, which specifies how often this MSDP device sends keep alive
messages to the neighbor. The keep alive time is 60 seconds and is not configurable.
The hold time, which specifies how many seconds the MSDP device will wait for a
KEEPALIVE or UPDATE message from an MSDP neighbor before deciding that the
neighbor is dead. The hold time is 90 seconds and is not configurable.
Keep Alive Message
Sent
The number of keepalive messages the MSDP device has sent to the peer.
The number of keepalive messages the MSDP device has received from the peer.
Keep Alive Message
Received
Notifications Sent
The number of notification messages the MSDP device has sent to the peer.
The number of notification messages the MSDP device has received from the peer.
The number of source active messages the MSDP device has sent to the peer.
Notifications Received
Source-Active Sent
Source-Active Received The number of source active messages the MSDP device has received from the peer.
Last Connection Reset The reason the previous session with this neighbor ended.
Reason
FastIron Ethernet Switch IP Multicast Configuration Guide
53-1003085-02
129
Download from Www.Somanuals.com. All Manuals Search And Download.
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. Where applicable, the subcode messages are listed
underneath the error code messages:
•
•
•
•
•
•
•
1 - Message Header Error
2 - SA-Request Error
3 - SA-Message or SA-Response Error
4 - Hold Timer Expired
5 - Finite State Machine Error
6 - Notification
7 - Cease
For information about these errors, refer to section 17 in the Internet draft describing
MSDP, "draft-ietf-msdp-spec".
Notification Message
Error SubCode
Received
See above.
Notification Message
The error message corresponding to the error code in the NOTIFICATION message this
Error Code Transmitted MSDP router sent to the neighbor. See the description for the Notification Message Error
Code Received field for a list of possible codes.
Notification Message
Error SubCode
Transmitted
See above.
TCP Statistics
130
FastIron Ethernet Switch IP Multicast Configuration Guide
53-1003085-02
Download from Www.Somanuals.com. All Manuals Search And Download.
IPv4 Multicast Protocols
TABLE 15 MSDP peer information (Continued)
This field...
Displays...
The state of the connection with the neighbor. Can be one of the following:
TCP connection state
•
•
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.
ESTABLISHED - Data can be sent and received over the connection. This is the
normal operational state of the connection.
FIN-WAIT-1 - Waiting for a connection termination request from the remote TCP, or
an acknowledgment of the connection termination request previously sent.
•
•
•
FIN-WAIT-2 - Waiting for a connection termination request from the remote TCP.
CLOSE-WAIT - Waiting for a connection termination request from the local user.
CLOSING - Waiting for a connection termination request acknowledgment from the
remote TCP.
•
LAST-ACK - Waiting for an acknowledgment of the connection termination request
previously sent to the remote TCP (includes an acknowledgment of the connection
termination request).
•
•
TIME-WAIT - Waiting for enough time to pass to be sure the remote TCP received
the acknowledgment of the connection termination request.
CLOSED - There is no connection state.
Local host
Local port
Remote host
Remote port
ISentSeq
The IP address of the MSDP device interface with the peer.
The TCP port the MSDP router is using for the BGP4 TCP session with the neighbor.
The IP address of the neighbor.
The TCP port number of the peer end of the connection.
The initial send sequence number for the session.
The next sequence number to be sent.
SendNext
TotUnAck
The number of sequence numbers sent by the MSDP device that have not been
acknowledged by the neighbor.
SendWnd
TotSent
The size of the send window.
The number of sequence numbers sent to the neighbor.
ReTrans
The number of sequence numbers the MSDP device retransmitted because they were
not acknowledged.
IRcvSeq
RcvNext
RcvWnd
The initial receive sequence number for the session.
The next sequence number expected from the neighbor.
The size of the receive window.
FastIron Ethernet Switch IP Multicast Configuration Guide
53-1003085-02
131
Download from Www.Somanuals.com. All Manuals Search And Download.
IPv4 Multicast Protocols
TABLE 15 MSDP peer information (Continued)
This field...
Displays...
TotalRcv
RcvQue
SendQue
The number of sequence numbers received from the neighbor.
The number of sequence numbers in the receive queue.
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.
device # show ip msdp vrf blue sa-cacheTotal of 10 SA cache entriesIndex RP
address (Source, Group) Orig Peer Age1 2.2.2.2 (192.6.1.10, 227.1.1.1)
192.1.1.2 0 2 2.2.2.2 (192.6.1.10, 227.1.1.2) 192.1.1.2 0 3 2.2.2.2
(192.6.1.10, 227.1.1.3) 192.1.1.2 0 4 2.2.2.2 (192.6.1.10, 227.1.1.4)
192.1.1.2 0 5 2.2.2.2 (192.6.1.10, 227.1.1.5) 192.1.1.2 0 6 2.2.2.2
(192.6.1.10, 227.1.1.6) 192.1.1.2 0 7 2.2.2.2 (192.6.1.10, 227.1.1.7)
192.1.1.2 0 8 2.2.2.2 (192.6.1.10, 227.1.1.8) 192.1.1.2 0 9 2.2.2.2
(192.6.1.10, 227.1.1.9) 192.1.1.2 0 10 2.2.2.2 (192.6.1.10, 227.1.1.10)
192.1.1.2 0
Syntax: show ip msdp [ vrf vrf-name ] sa-cache [source-address | group-address | peer-as as-
number | counts | orig-rp rp-address | peer peer-address ] [ rejected | self-originated ] ]
The source-address parameter selects the source address of the SA entry.
The group-address parameter selects the group address of the SA entry.
The peer-as keyword specifies the BGP AS Number of the forwarding peer.
The counts keyword displays only the count of entries.
The orig-rp keyword specifies the originating RP address.
The peer keyword specifies the peer address.
The rejected keyword displays the rejected SAs.
The self-originated keyword displays the self-originated SAs.
The following table describes the output from this command.
TABLE 16 MSDP source active cache
This field...
Total
Displays...
The number of entries the cache currently contains.
The cache entry number.
Index
RP
The RP through which receivers can access the group traffic from the source
The IP address of the multicast source.
SourceAddr
GroupAddr
The IP multicast group to which the source is sending information.
132
FastIron Ethernet Switch IP Multicast Configuration Guide
53-1003085-02
Download from Www.Somanuals.com. All Manuals Search And Download.
Displaying MSDP RPF-Peer
TABLE 16 MSDP source active cache (Continued)
This field...
Orig Peer
Age
Displays...
The peer from which this source-active entry was received.
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.
device#show ip msdp sa-cache 239.1.1.1
You can use the following command to filter the output to display only the SA cache entries that are
received from peers in the BGP AS Number 100.
device#show ip msdp sa-cache 100
You can use the following command to filter the output to display only the SA cache entries that are
originated by the RP 1.1.1.1.
device#show ip msdp sa-cache orig-rp 1.1.1.1
You can use the following command to filter the output to display only the SA cache entries that are
received from the peer 1.1.1.1.
device#show ip msdp sa-cache peer 1.1.1.1
You can use the following command to display the rejected SAs. You can further narrow down by
quoting the reason for rejection.
device#show ip msdp sa-cache rejected
You can use the following command to display the self-originated SAs.
device#show ip msdp sa-cache self-originated
Displaying MSDP RPF-Peer
To display MSDP peer information for the RP 1.1.1.1, enter the following command.
device# show ip msdp rpf-peer 1.1.1.1
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 [vrf vrf-name ] rpf-peer ip-addr
FastIron Ethernet Switch IP Multicast Configuration Guide
53-1003085-02
133
Download from Www.Somanuals.com. All Manuals Search And Download.
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.
Brocade#sh ip msdp vrf Blue rpf-peer 40.40.40.2
MSDP Peer Status Summary
KA: Keepalive SA:Source-Active NOT: Notification
Peer Address
Peer As
State
KA
SA
NOT
Age
57
In
0
Out
In
Out
In
1001
Out
40.40.40.2
ESTABLISH 5569
5568
0
0
0
Syntax: show ip msdp vrf VRF-name rpf-peer ip-addr
Clearing MSDP information
You can clear the following MSDP information:
•
Peer information
Source active cache
MSDP statistics
•
•
Clearing peer information
To clear MSDP peer information, enter the following command at the Privileged EXEC level of the CLI.
device# clear ip msdp peer 205.216.162.1
Syntax: clear ip msdp peer [ip-addr ]
The command in this example clears the MSDP peer connection with MSDP router 205.216.162.1.
The CLI displays a message to indicate when the connection has been successfully closed. To clear
all the peers, omit the ip-addr variable from the command.
Clearing peer information on a VRF
To clear the MSDP VRF peers, enter the following command at the MSDP VRF configuration level.
device#clear ip msdp vrf blue peer 207.207.162.5
Syntax: clear ip msdp [vrf vrf-name ] peer [ ip-addr ]
134
FastIron Ethernet Switch IP Multicast Configuration Guide
53-1003085-02
Download from Www.Somanuals.com. All Manuals Search And Download.
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.
Clearing the source active cache for a VRF
To clear the MSDP VRF source active cache by entering the following command at the MSDP VRF
configuration level.
device#clear ip msdp sa-cache
vrf blue
Syntax: clear ip msdp [vrf vrf-name ] sa-cache [ ip-addr ]
Clearing MSDP statistics
To clear MSDP statistics, enter the following command at the Privileged EXEC level of the CLI.
device# clear ip msdp statistics
Syntax: clear ip msdp statistics [ ip-addr ]
The command in this example clears statistics for all the peers. To clear statistics for only a specific
peer, enter the IP address of the peer.
Clearing MSDP VRF statistics
To clear the MSDP VRF statistics by entering the following command.
device# clear ip msdp vrf blue statistics
Syntax: clear ip msdp [vrf vrf-name ] statistics [ip-addr ]
The command in this example clears statistics for all the peers. To clear statistics for only a specific
peer, enter the IP address of the peer.
The command in this example clears all statistics for all the peers in the VRF "blue".
Configuring MSDP mesh groups
A PIM Sparse domain can have several RPs that are connected to each other to form an MSDP mesh
group. To qualify as a mesh group, the RPs have to be fully meshed; that is, each RP must be
A mesh group reduces the forwarding of SA messages within a domain. Instead of having every RP in a
domain forward SA messages to all the RPs within that domain, only one RP forwards the SA message.
Since an MSDP mesh group is fully meshed, peers do not forward SA messages received in a domain
from one member to any member of the group. The RP that originated the SA or the first RP in a
domain that receives the SA message is the only one that forwards the message to the members of a
FastIron Ethernet Switch IP Multicast Configuration Guide
53-1003085-02
135
Download from Www.Somanuals.com. All Manuals Search And Download.
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
example, RP 206.251.21.31 originates or receives an SA message from a peer in another domain, it
sends the SA message to its peers within the mesh group. However, the peers do not send the
message back to the originator RP or to each other. The RPs then send the SA message farther away
to their peers in other domains.The process continues until all RPs within the network receive the SA
message.
Configuring MSDP mesh group
To configure an MSDP mesh group, enter commands such as the following on each device that will be
included in the mesh group.
device(config)# router msdp
device(config-msdp-router)# msdp-peer 206.251.18.31 connect-source loopback 2
device(config-msdp-router)# msdp-peer 206.251.19.31 connect-source loopback 2
device(config-msdp-router)# msdp-peer 206.251.20.31 connect-source loopback 2
device(config-msdp-router)# mesh-group GroupA 206.251.18.31
device(config-msdp-router)# mesh-group GroupA 206.251.19.31
device(config-msdp-router)# mesh-group GroupA 206.251.20.31
device(config-msdp-router)# exit
136
FastIron Ethernet Switch IP Multicast Configuration Guide
53-1003085-02
Download from Www.Somanuals.com. All Manuals Search And Download.
MSDP Anycast RP
Syntax: [no] mesh-group group-name peer-address
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.
The group-name parameter identifies the mesh group. Enter up to 31 characters for group-name. You
can have up to 4 mesh groups within a multicast network. Each mesh group can include up to 15 peers.
The peer-address parameter specifies the IP address of the MSDP peer that is being placed in the
mesh group. Each mesh group can include up to 32 peers.
NOTE
On each of the device that will be part of the mesh group, there must be a mesh group definition for all
the peers in the mesh-group.
A maximum of 32 MSDP peers can be configured per mesh group.
MSDP Anycast RP
MSDP Anycast RP is a method of providing intra-domain redundancy and load-balancing between
multiple Rendezvous Points (RP) in a Protocol Independent Multicast Sparse mode (PIM-SM) network.
It is accomplished by configuring all RPs within a domain with the same anycast RP address which is
typically a loopback IP address. Multicast Source Discovery Protocol (MSDP) is used between all of the
RPs in a mesh configuration to keep all RPs in sync regarding the active sources.
PIM-SM routers are configured to register (statically or dynamically) with the RP using the same
anycast RP address. Since multiple RPs have the same anycast address, an Interior Gateway Protocol
(IGP) such as OSPF routes the PIM-SM router to the RP with the best route. If the PIM-SM routers are
distributed evenly throughout the domain, the loads on RPs within the domain will be distributed. If the
RP with the best route goes out of service, the PIM-SM router’s IGP changes the route to the closest
operating RP that has the same anycast address.
This configuration works because MSDP is configured between all of the RPs in the domain.
Consequently, all of the RPs share information about active sources.
This feature uses functionality that is already available on the Brocade device but re-purposes it to
provide the benefits desired as described in RFC 3446.
Configuring MSDP Anycast RP
To configure MSDP Anycast RP, you must perform the following tasks:
•
•
Configure a loopback interface with the anycast RP address on each of the RPs within the domain
and enable PIM-SM on these interfaces.
Ensure that the anycast RP address is leaked into the IGP domain. This is typically done by
enabling the IGP on the loopback interface (in passive mode) or redistributing the connected
loopback IP address into the IGP.
FastIron Ethernet Switch IP Multicast Configuration Guide
53-1003085-02
137
Download from Www.Somanuals.com. All Manuals Search And Download.
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.
•
The non-RP PIM-SM routers may be configured to use the anycast RP address statically or
dynamically (by the PIMv2 bootstrap mechanism).
Example
PIM-SM routers. Loopback 1 in RP 1 and RP 2 have the same IP address. Loopback 2 in RP1 and
Loopback 2 in RP2 have different IP addresses and are configured as MSDP peering IP addresses in
a mesh configuration.
In the PIM configuration for PIM-SM routers PIMR1 and PIMR2 the RP address is configured to be the
anycast RP address that was configured on the Loopback 1 interfaces on RP1 and RP2. OSPF is
configured as the IGP for the network and all of the devices are in OSPF area 0.
Since PIMR1 has a lower cost path to RP1 and PIMR2 has a lower cost path to RP2 they will register
with the respective RPs when both are up and running. This shares the load between the two RPs. If
one of the RPs fails, the higher-cost path to the IP address of Loopback 1 on the RPs is used to route
to the still-active RP.
138
FastIron Ethernet Switch IP Multicast Configuration Guide
53-1003085-02
Download from Www.Somanuals.com. All Manuals Search And Download.
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
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.1/32
RP1(config-lbif-1)# ip pim-sparse
RP1(config-lbif-1)# exit
RP1(config)# interface loopback 2
RP1(config-lbif-2)# ip ospf area 0
RP1(config-lbif-2)# ip ospf passive
RP1(config-lbif-2)# ip address 10.1.1.1/32
RP1(config-lbif-2)# exit
RP1(config)# interface ethernet 5/1
RP1(config-if-e1000-5/1)# ip ospf area 0
RP1(config-if-e1000-5/1)# ip address 192.1.1.1/24
RP1(config-if-e1000-5/1)# ip pim-sparse
RP1(config)# interface ethernet 5/2
RP1(config-if-e1000-5/2)# ip ospf area 0
RP1(config-if-e1000-5/2)# ip ospf cost 5
RP1(config-if-e1000-5/2)# ip address 192.2.1.1/24
RP1(config-if-e1000-5/2)# ip pim-sparse
RP1(config)# interface ethernet 5/3
RP1(config-if-e1000-5/3)# ip ospf area 0
RP1(config-if-e1000-5/3)# ip ospf cost 10
RP1(config-if-e1000-5/3)# ip address 192.3.1.1/24
RP1(config-if-e1000-5/3)# ip pim-sparse
RP1(config-if-e1000-5/3)# exit
FastIron Ethernet Switch IP Multicast Configuration Guide
53-1003085-02
139
Download from Www.Somanuals.com. All Manuals Search And Download.
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
RP2(config)#router ospf
RP2(config-ospf-router)# area 0
RP2(config-ospf-router)# exit
RP2(config)# interface loopback 1
RP2(config-lbif-1)# ip ospf area 0
RP2(config-lbif-1)# ip ospf passive
RP2(config-lbif-1)# ip address 10.0.0.1/32
RP2(config-lbif-1)# ip pim-sparse
RP2(config-lbif-1)# exit
RP2(config)# interface loopback 2
RP2(config-lbif-2)# ip ospf area 0
RP2(config-lbif-2)# ip ospf passive
RP2(config-lbif-2)# ip address 10.1.1.2/32
RP2(config-lbif-2)# exit
RP2(config)# interface ethernet 5/1
RP2(config-if-e1000-5/1)# ip ospf area 0
RP2(config-if-e1000-5/1)# ip address 192.1.1.2/24
RP2(config-if-e1000-5/1)# ip pim-sparse
RP2(config)# interface ethernet 5/2
RP2(config-if-e1000-5/2)# ip ospf area 0
RP2(config-if-e1000-5/2)# ip ospf cost 5
RP2(config-if-e1000-5/2)# ip address 192.5.2.1/24
RP2(config-if-e1000-5/2)# ip pim-sparse
RP2(config)# interface ethernet 5/3
RP2(config-if-e1000-5/3)# ip ospf area 0
RP2(config-if-e1000-5/3)# ip ospf cost 10
RP2(config-if-e1000-5/3)# ip address 192.6.1.2/24
RP2(config-if-e1000-5/3)# ip pim-sparse
RP2(config-if-e1000-5/3)# exit
RP2(config)# router pim
RP2(config-pim-router)# rp-candidate loopback 1
RP2(config-pim-router)# exit
RP2(config)# router msdp
RP2(config-msdp-router)# msdp-peer 10.1.1.1 connect-source loopback 2
RP2(config-msdp-router)# originator-id loopback 2
PIMR1 configuration
PIMR1(config)#router ospf
PIMR1(config-ospf-router)# area 0
PIMR1(config-ospf-router)# exit
PIMR1(config)# interface ethernet 6/2
PIMR1(config-if-e1000-6/2)# ip ospf area 0
PIMR1(config-if-e1000-6/2)# ip ospf cost 5
PIMR1(config-if-e1000-6/2)# ip address 192.2.1.2/24
PIMR1(config-if-e1000-6/2)# ip pim-sparse
PIMR1(config)# interface ethernet 6/3
PIMR1(config-if-e1000-6/3)# ip ospf area 0
PIMR1(config-if-e1000-6/3)# ip ospf cost 10
PIMR1(config-if-e1000-6/3)# ip address 192.6.1.1/24
PIMR1(config-if-e1000-6/3)# ip pim-sparse
PIMR1(config-if-e1000-6/3)# exit
PIMR1(config)# router pim
PIMR1(config-pim-router)# rp-address 10.0.0.1
PIMR1(config-pim-router)# exit
140
FastIron Ethernet Switch IP Multicast Configuration Guide
53-1003085-02
Download from Www.Somanuals.com. All Manuals Search And Download.
PIM Anycast RP
PIMR2 configuration
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.2/24
PIMR2(config-if-e1000-1/2)# ip pim-sparse
PIMR2(config)# interface ethernet 1/3
PIMR2(config-if-e1000-1/3)# ip ospf area 0
PIMR2(config-if-e1000-1/3)# ip ospf cost 10
PIMR2(config-if-e1000-1/3)# ip address 192.3.1.2/24
PIMR2(config-if-e1000-1/3)# ip pim-sparse
PIMR2(config-if-e1000-1/3)# exit
PIMR2(config)# router pim
PIMR2(config-pim-router)# rp-address 10.0.0.1
PIMR2(config-pim-router)# exit
PIM Anycast RP
PIM Anycast RP is a method of providing load balancing and fast convergence to PIM RPs in an IPv4
multicast domain. The RP address of the Anycast RP is a shared address used among multiple PIM
routers, known as PIM RP. The PIM RP routers create an Anycast RP set. Each router in the Anycast
RP set is configured using two IP addresses; a shared RP address in their loopback address and a
separate, unique ip address. The loopback address must be reachable by all PIM routers in the
multicast domain. The separate, unique ip address is configured to establish static peering with other
PIM routers and communication with the peers.
When the source is activated in a PIM Anycast RP domain, the PIM First Hop (FH) will register the
source to the closet PIM RP. The PIM RP follows the same MSDP Anycast RP operation by
decapsulating the packet and creating the (s,g) state. If there are external peers in the Anycast RP set,
the router will re-encapsulate the packet with the local peering address as the source address of the
encapsulation. The router will unicast the packet to all Anycast RP peers. The re-encapsulation of the
data register packet to Anycast RP peers ensures source state distribution to all RPs in a multicast
domain.
Configuring PIM Anycast RP
A new PIM CLI is introduced for PIM Anycast RP under the router pim sub mode. The PIM CLI specifies
mapping of the RP and the Anycast RP peers.
To configure PIM Anycast RP, enter the following command.
device(config)#router pim
device(config-pim-router)#rp-address 100.1.1.1
device(config-pim-router)#anycast-rp 100.1.1.1 my-anycast-rp-set-acl
Syntax: [no] anycast-rp rp-address anycast-rp-set-acl
The rp address parameter specifies a shared RP address used among multiple PIM routers.
The anycast-rp-set-acl parameter specifies a host based simple acl used to specifies the address of
the Anycast RP set, including a local address.
The following example is a configuration of PIM Anycast RP 100.1.1.1.The example avoids using
loopback 1 interface when configuring PIM Anycast RP because the loopback 1 address could be used
FastIron Ethernet Switch IP Multicast Configuration Guide
53-1003085-02
141
Download from Www.Somanuals.com. All Manuals Search And Download.
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.1/24
device(config-lbif-2)#ip pim-sparse
device(config-lbif-2)#interface loopback 3
device(config-lbif-3)#ip address 1.1.1.1/24
device(config-lbif-3)#ip pim-sparse
device(config-lbif-3)#router pim
device(config-pim-router)#rp-address 100.1.1.1
device(config-pim-router)#anycast-rp 100.1.1.1 my-anycast-rp-set
device(config-pim-router)#ip access-list standard my-anycast-rp-set
device(config-std-nacl)#permit host 1.1.1.1
device(config-std-nacl)#permit host 2.2.2.2
device(config-std-nacl)#permit host 3.3.3.3
The RP shared address 100.1.1.1 is used in the PIM domain. IP addresses 1.1.1.1, 2.2.2.2, and
3.3.3.3 are listed in the ACL that forms the self inclusive Anycast RP set. Multiple anycast-rp instances
can be configured on a system; each peer with the same or different Anycast RP set.
NOTE
The PIM software supports up to eight PIM Anycast-RP routers. All deny statements in the
anycast_rp_set acl and additional routers more than eight listed in an access list are ignored.
The example shown in the following figure is a PIM Anycast-enabled network with 3 RPs, 1 PIM-FH
router connecting to its active source and local receiver. Loopback 2 in RP1, RP2, and RP3 have the
same IP addresses 100.1.1.1. Loopback 3 in RP1, RP2, and RP3 each have separate IP addresses
configured to communicate with their peers in the Anycast RP set.
FIGURE 9 Example of a PIM Anycast RP network
Displaying information for a PIM Anycast RP interface
To display information for a PIM Anycast RP interface, enter the following command.
device(config)#show ip pim anycast-rp
Number of Anycast RP: 1
Anycast RP: 100.1.1.1
ACL ID: 200
ACL Name: my-anycast-rp-set
ACL Filter: SET
Peer List:
1.1.1.1
2.2.2.2
3.3.3.3
Syntax: show ip pim [vrf vrf-name ] anycast-rp
142
FastIron Ethernet Switch IP Multicast Configuration Guide
53-1003085-02
Download from Www.Somanuals.com. All Manuals Search And Download.
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
ACL Filter
Peer List
The ACL Name specifies the name of the Anycast RP set.
The ACL Filter specifies the ACL filter state SET or UNSET.
The Peer List specifies host addresses that are permitted in the Anycast RP set.
NOTE
MSDP and Anycast RP do not interoperate. If transitioning from MSDP to Anycast RP or vice versa, all
RPs in the network must be configured for the same method of RP peering; either Anycast RP or
MSDP.
Static multicast routes
Configure static multicast routes to control the network paths, administrative distance, and precedence
for multicast routes.
Static multicast routes allow you to control the network path used by multicast traffic. Static multicast
routes are especially useful when the unicast and multicast topologies of a network are different. By
configuring static multicast routes you don't have to make the topologies similar.
NOTE
In IP multicasting, source IP addresses are unicast addresses while destination IP addresses are
multicast (group) addresses. Therefore, in IP multicasting, a route lookup is done for source IP address,
rather than its destination IP address.
You can configure more than one static multicast route. The device always uses the most specific route
that matches a multicast source address. Thus, if you want to configure a multicast static route for a
specific multicast source and also configure another multicast static route for all other sources, you can
configure two static routes
Configure the distance keyword in the ip mroute command to specify the administrative distance,
which the device uses to determine the best path for a route. When comparing multiple paths for a
route, the device prefers the path with the lower administrative distance. To ensure that the default
static route is used, configure a low administrative distance value. However, the device prefers directly
connected routes over other routes, no matter what the administrative distance.
FastIron Ethernet Switch IP Multicast Configuration Guide
53-1003085-02
143
Download from Www.Somanuals.com. All Manuals Search And Download.
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. The router acts as a proxy for its hosts and performs the
host portion of the IGMP task on the upstream interface as follows:
•
•
When queried, the router sends group membership reports for the groups learned.
When one of its hosts joins a multicast address group to which none of its other hosts belong, the
router sends unsolicited membership reports to that group.
•
When the last of its hosts in a particular multicast group leaves the group, the router sends an
unsolicited leave group membership report to group (multicast IP address 224.0.0.2).
IGMP proxy configuration notes
When using IGMP Proxy, you must do the following.
1. Configure PIM on all multicast client ports to build the group membership table. The group
membership table will be reported by the proxy interface. Refer to Globally enabling and disabling
PIM on page 85.
2. Enable IP multicast on an interface to an upstream router that will be the IGMP proxy interface
and configure IGMP Proxy on that interface.
IGMP proxy limitations
•
•
IGMP Proxy cannot be enabled on the same interface on which PIM SM or PIM DM is enabled.
IGMP Proxy is only supported in a PIM Dense environment where there are IGMP clients
connected to the Brocade device. The Brocade device does not send IGMP reports on an IGMP
proxy interface for remote clients connected to a PIM neighbor,because it is not aware of groups
that the remote clients are interested in. Static groups on the other PIM interfaces are included in
proxy reports.
•
PIM DM must be enabled in passive mode. This is a change from the previous implementation; to
be backward compatible, PIM-DM passive mode is enabled in passive mode indirectly if PIM-DM
is not enabled explicitly.
Configuring IGMP Proxy
Perform the following steps to configure IGMP Proxy.
144
FastIron Ethernet Switch IP Multicast Configuration Guide
53-1003085-02
Download from Www.Somanuals.com. All Manuals Search And Download.
Filtering groups in proxy report messages
1. Configure router PIM globally.
device(config)#router pim
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)#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.
device(config-if-e1000-1/3)#ip igmp proxy
Syntax: [no] ip igmp proxy
Filtering groups in proxy report messages
Once IGMP Proxy is configured and the router receives a query on an IGMP Proxy interface, the router
sends a report in response to the query before the IGMP maximum response time expires.
You can filter out groups in proxy report messages by specifying an access list name or number.
Brocade(config-if-e1000-1/3)#ip igmp proxy group-filter ACL1
Syntax: [no] ip igmp proxy group-filter access_list
To remove the group filter association without disabling the proxy, please apply the command ip igmp
proxy without the group filter option.
Displaying IGMP Proxy information
Use the show ip igmp proxy command to see information about the proxy groups and interfaces on
the default VRF. For other VRF instances, use the same command with the vrf option. For example,
show ip igmp proxy vrfvrf_name .
Brocade#sh ip igmp proxy
Proxy instance name: default-vrf
Total proxy groups: 4
Address
Mode
Source
count
ref
flags
count
----------------------------------------------------
225.1.1.1
exclude
exclude
exclude
exclude
0
0
0
0
0
0
0
0
0
0
0
0
225.1.1.2
225.1.1.3
225.1.1.4
Proxy interfaces
----------------
Name
Oper
Cfg
Unsoli
Interval Acl Id
Filter
Filter
Name
Version Robust
-----------------------------------------------------
e1/3
2
2
1
0
Syntax: show ip igmp proxy
The report shows the following information.
FastIron Ethernet Switch IP Multicast Configuration Guide
53-1003085-02
145
Download from Www.Somanuals.com. All Manuals Search And Download.
IPv4 Multicast Protocols
TABLE 18 Output of show ip igmp proxy
Field
Description
Address
Mode
Group address.
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
flags
Number of proxy interfaces where the responses (query, state, change, etc) are scheduled.
Can be "0" or "1." "1" indicates that the group state has changed and it needs to be reevaluated
before a response is generated. "0" indicates that no change in state response is scheduled.
Name
Interface name.
Oper version Current querier version or configured version.
Cfg Robust Configured robustness value.
Unsoli Interval Unsolitcited report interval in seconds.
Filter Acl Id
Filter Name
Number of the access list.
Name of the access list.
Use theshow ip igmp proxy summary
command to see summary information.
Brocade#sh ip igmp proxy summary
Proxy instances:
-----------------------------------
Inst-Name
Total Grps
-----------------------------------
default-vrf
4
The report shows the following information.
TABLE 19 Output of show ip igmp proxy summary
Field
Description
Inst-Name
Total Grps
Number of the proxy instance.
NUmber of proxy groups.
Syntax: show ip igmp proxy summary
Use theshow ip igmp proxy stats
command to see information about queries and reports on a specific interface.
Brocade#sh ip igmp proxy stats
Intf
genQv1 genQv2 genQv3 GrpQ
RX RX RX RX
SrcQ
RX
Rprtv1 Rprtv2 Rprtv3 leave
TX TX TX TX
--------------------------------------------------------------------------------
v3000
0
0
0
0
0
0
0
0
0
Syntax: show ip igmp proxy stats
146
FastIron Ethernet Switch IP Multicast Configuration Guide
53-1003085-02
Download from Www.Somanuals.com. All Manuals Search And Download.
IGMP V3
The report shows the following information.
TABLE 20 Output of show ip igmp proxy stats
Field
Description
Intf
Interface
genQv1 RX
genQv2 RX
genQv3 RX
GrpQ RX
SrcQ RX
Rprtv1 TX
Rprtv2 TX
Rprtv3 TX
leave TX
IGMP v1 general query received on proxy interface.
IGMP v2 general query received on proxy interface.
IGMP v3 general query received on proxy interface.
Group query received.
Source query received.
IGMP v1 report generated.
IGMP 2 report generated.
IGMP v3 report generated.
IGMP v2 leave generated.
IGMP V3
The Internet Group Management Protocol (IGMP) allows an IPV4 system to communicate IP Multicast
group membership information to its neighboring routers. The routers in turn limit the multicast of IP
packets with multicast destination addresses to only those interfaces on the router that are identified as
IP Multicast group members.
In IGMP V2, when a router sent a query to the interfaces, the clients on the interfaces respond with a
membership report of multicast groups to the router. The router can then send traffic to these groups,
regardless of the traffic source. When an interface no longer needs to receive traffic from a group, it
sends a leave message to the router which in turn sends a group-specific query to that interface to see
if any other clients on the same interface is still active.
In contrast, IGMP V3 provides selective filtering of traffic based on traffic source. A router running IGMP
V3 sends queries to every multicast enabled interface at the specified interval. These general queries
determine if any interface wants to receive traffic from the router. The following are the three variants of
the Query message:
•
A "General Query" is sent by a multicast router to learn the complete multicast reception state of
the neighboring interfaces. In a General Query, both the Group Address field and the Number of
Sources (N) field are zero.
•
A "Group-Specific Query" is sent by a multicast router to learn the reception state, with respect to a
*single* multicast address, of the neighboring interfaces. In a Group-Specific Query, the Group
FastIron Ethernet Switch IP Multicast Configuration Guide
53-1003085-02
147
Download from Www.Somanuals.com. All Manuals Search And Download.
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. In a Group-and-Source-Specific Query, the Group Address field contains
the multicast address of interest, and the Source Address [i] fields contain the source address(es)
of interest.
The hosts respond to these queries by sending a membership report that contains one or more of the
following records that are associated with a specific group:
•
Current-State Record that indicates from which sources the interface wants to receive and not
receive traffic. The record contains source address of interfaces and whether or not traffic will be
received or included (IS_IN) or not received or excluded (IS_EX) from that source.
The following messages are generated by hosts, not the response Query. These messages are
generated when there is a change in the group member state.
•
Filter-mode-change record. If the interface changes its current state from IS_IN to IS_EX, a
TO_EX record is included in the membership report. Likewise, if an interface’s current state
changes from IS_EX to IS_IN, a TO_IN record appears in the membership report.
IGMP V2 Leave report is equivalent to a TO_IN (empty) record in IGMP V3. This record means that no
traffic from this group will be received regardless of the source.
An IGMP V2 group report is equivalent to an IS_EX (empty) record in IGMP V3. This record means
that all traffic from this group will be received regardless of source.
•
Source-List-Change Record. If the interface wants to add or remove traffic sources from its
membership report, the membership report can have an ALLOW record, which contains a list of
new sources from which the interface wishes to receive traffic. It can also contains a BLOCK
record, which lists current traffic sources from which the interfaces wants to stop receiving traffic.
In response to membership reports from the interfaces, the router sends a Group-Specific or a Group-
and-Source Specific query to the multicast interfaces. For example, a router receives a membership
report with a Source-List-Change record to block old sources from an interface. The router sends
Group-and-Source Specific Queries to the source and group (S,G) identified in the record. If none of
the interfaces is interested in the (S,G), it is removed from (S,G) list for that interface on the router.
Each IGMP V3-enabled router maintains a record of the state of each group and each physical port
within a virtual routing interface. This record contains the group, group-timer, filter mode, and source
records information for the group or interface. Source records contain information on the source
address of the packet and source timer. If the source timer expires when the state of the group or
interface is in Include mode, the record is removed.
Default IGMP version
IGMP V3 is available for Brocade devices; however, these routers are shipped with IGMP V2-enabled.
You must enable IGMP V3 globally or per interface.
Also, you can specify what version of IGMP you want to run on a device globally, on each interface
(physical port or virtual routing interface), and on each physical port within a virtual routing interface. If
you do not specify an IGMP version, IGMP V2 will be used.
Compatibility with IGMP V1 and V2
Different multicast groups, interfaces, and routers can run their own version of IGMP. Their version of
IGMP is reflected in the membership reports that the interfaces send to the router. Routers and
interfaces must be configured to recognized the version of IGMP you want them to process.
148
FastIron Ethernet Switch IP Multicast Configuration Guide
53-1003085-02
Download from Www.Somanuals.com. All Manuals Search And Download.
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.
If an interface continuously receives queries from routers that are running versions of IGMP that are
different from what is on the interface, the interface logs warning messages in the syslog every five
minutes. Reports sent by interfaces to routers that contain different versions of IGMP do not trigger
warning messages; however, you can see the versions of the packets using the show ip igmp traffic
command.
The version of IGMP can be specified globally, per interface (physical port or virtual routing interface),
and per physical port within a virtual routing interface. The IGMP version set on a physical port within a
virtual routing interface supersedes the version set on a physical or virtual routing interface. Likewise,
the version on a physical or virtual routing interface supersedes the version set globally on the device.
The sections below present how to set the version of IGMP.
Globally enabling the IGMP version
To globally identify the IGMP version on a Brocade device, enter the following command.
device(config)# ip igmp version 3
Syntax: [no] ip igmp version version-number
Enter 1, 2, or 3 for version-number . Version 2 is the default version.
Enabling the IGMP version per interface setting
To specify the IGMP version for a physical port, enter a command such as the following.
device(config)# interface eth 1/5
device(config-if-1/5)# ip igmp version 3
To specify the IGMP version for a virtual routing interface on a physical port, enter a command such as
the following.
device(config)# interface ve 3
device(config-vif-1) ip igmp version 3
Syntax: [no] ip igmp version version-number
Enter 1, 2, or 3 for version-number . Version 2 is the default version.
Enabling the IGMP version on a physical port within a virtual routing
interface
To specify the IGMP version recognized by a physical port that is a member of a virtual routing
interface, enter a command such as the following.
device(config)# interface ve 3
device(config-vif-3)# ip igmp version 2
device(config-vif-3)# ip igmp port-version 3 e1/3 to e1/7 e2/9
FastIron Ethernet Switch IP Multicast Configuration Guide
53-1003085-02
149
Download from Www.Somanuals.com. All Manuals Search And Download.
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.
The ethernetport-number parameter specifies which physical port within a virtual routing interface is
being configured.
Enabling membership tracking and fast leave
NOTE
The IGMP V3 fast leave feature is supported in include mode, but does not work in the exclude mode.
IGMP V3 provides membership tracking and fast leave of clients. In IGMP V2, only one client on an
interface needs to respond to a router’s queries; therefore, some of the clients may be invisible to the
router, making it impossible for the switch to track the membership of all clients in a group. Also, when
a client leaves the group, the switch sends group specific queries to the interface to see if other clients
on that interface need the data stream of the client who is leaving. If no client responds, the switch
waits three seconds before it stops the traffic.
IGMP V3 contains the tracking and fast leave feature that you enable on virtual routing interfaces.
Once enabled, all physical ports on that virtual routing interface will have the feature enabled. IGMP
V3 requires all clients to respond to general and group specific queries so that all clients on an
interface can be tracked. Fast leave allows clients to leave the group without the three second waiting
period, if the following conditions are met:
•
If the interface, to which the client belongs, has IGMP V3 clients only. Therefore, all physical ports
on a virtual routing interface must have IGMP V3 enabled and no IGMP V1 or V2 clients can be
on the interface. (Although IGMP V3 can handle V1 and V2 clients, these two clients cannot be on
the interface in order for fast leave to take effect.)
•
No other client on the interface is receiving traffic from the group to which the client belongs.
Every group on the physical interface of a virtual routing interface keeps its own tracking record. It can
track by (source, group).
For example, two clients (Client A and Client B) belong to group1 but each is receiving traffic streams
from different sources. Client A receives a stream from (source_1, group1) and Client B receives it
from (source_2, group1). Now, if Client B leaves, the traffic stream (source_2, group1) will be stopped
immediately. The show ip igmp group tracking command displays that clients in a group that are
being tracked.
If a client sends a leave message, the client is immediately removed from the group. If a client does
not send a report during the specified group membership time (the default is 140 seconds), that client
is removed from the tracking list.
To enable the tracking and fast leave feature, enter commands such as the following.
device(config)# interface ve 13
device(config-vif-13)# ip igmp tracking
Syntax: [no] ip igmp tracking
150
FastIron Ethernet Switch IP Multicast Configuration Guide
53-1003085-02
Download from Www.Somanuals.com. All Manuals Search And Download.
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.2
Syntax: [no] ip igmp static-group ip-address [ count count-number | to ip-address ]
Enter the IP address of the static IGMP group for ip-address. The count-number range is 2-256.
To configure two static groups on virtual ports 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 ethernet 1/5
Or this command:
Device(config)# interface ve 10
Device(config-vif-10)# ip igmp static-group 226.0.0.1 to 226.0.0.2 ethernet 1/5
Syntax: [no] ip igmp static-group ip-address [ count count-number | to ip-address ] ethernet slot-
number
Enter the IP address of the static IGMP group for ip-address. The count-number range is 2-256.
Enter the ID of the physical port of the VLAN that will be a member of the group for ethernet slot-
number.
NOTE
IGMPv3 does not support static IGMP group members.
NOTE
Static IGMP groups are supported only in Layer 3 mode.
Setting the query interval
The IGMP query interval period defines how often a switch will query an interface for group
membership. Possible values are 2-3600 seconds and the default value is 125 seconds, but the value
you enter must be a little more than twice the group membership time.
To modify the default value for the IGMP query interval, enter the following.
device(config)# ip igmp query-interval 120
Syntax: [no] ip igmp query-interval 2-3600
The interval must be a little more than two times the group membership time.
FastIron Ethernet Switch IP Multicast Configuration Guide
53-1003085-02
151
Download from Www.Somanuals.com. All Manuals Search And Download.
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.
device(config)# ip igmp group-membership-time 240
Syntax: [no] ip igmp group-membership-time 5-26000
Setting the maximum response time
The maximum response time defines the maximum number of seconds that a client can wait before it
replies to the query sent by the router. Possible values are 1 - 25. The default is 10.
To change the IGMP maximum response time, enter a command such as the following at the global
CONFIG level of the CLI.
device(config)# ip igmp max-response-time 8
Syntax: [no] ip igmp max-response-time num
The num parameter specifies the maximum number of seconds for the response time. Enter a value
from 1 - 25. The default is 10.
Displaying IGMPv3 information
The sections below present the show commands available for IGMP V3.
Displaying IGMP group status
You can display the status of all IGMP multicast groups on a device by entering the following
command.
device# show ip igmp group
Total 2 entries
-----------------------------------------------------
Idx Group Address
Port
Intf
Mode
Timer Srcs
---+----------------+------+------+-------+-----+----
1 232.0.0.1
2 226.0.0.1
e6/2
e6/2
e6/3
v30
include
exclude
include
0
240
0
7
2
3
v30
e6/3
Total number of groups 2
To display the status of one IGMP multicast group, enter a command such as the following.
device# show ip igmp group 239.0.0.1 detail
Total 2 entries
-----------------------------------------------------
Idx Group Address
Port
Intf
Mode
Timer Srcs
---+----------------+------+------+-------+-----+----
1 226.0.0.1
S: 40.40.40.12
e6/2
v30
exclude
218
2
S: 40.40.40.11
S: 40.40.40.10
S: 40.40.40.2
S: 40.40.40.3
226.0.0.1
S: 30.30.30.3
S: 30.30.30.2
S: 30.30.30.1
(Age: 218)
(Age: 218)
e6/3
e6/3
include
0
3
(Age: 165)
(Age: 165)
(Age: 165)
152
FastIron Ethernet Switch IP Multicast Configuration Guide
53-1003085-02
Download from Www.Somanuals.com. All Manuals Search And Download.
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
S: 40.40.40.12
e6/2
v30
exclude
253
3
S: 40.40.40.11
S: 40.40.40.10
S: 40.40.40.2
(Age: 253)
C: 10.10.10.1
(Age: 253)
(Age: 253)
(Age: 253)
S: 40.40.40.3
C: 10.10.10.1
226.0.0.1
S: 30.30.30.3
e6/3
e6/3
include
0
3
(Age: 196)
C: 10.2.0.1
(Age: 196)
(Age: 196)
(Age: 196)
S: 30.30.30.2
S: 30.30.30.1
(Age: 196)
C: 10.2.0.1
(Age: 196)
C: 10.2.0.1
Syntax: show ip igmp [vrf [vrf-name ] group [ group-address [ detail ] [tracking ] ]
If you want a report for a specific multicast group, enter that group’s address for group-address . Omit
the group-address if you want a report for all multicast groups.
The vrf parameter specifies that you want to display IGMP group information for the VRF specified by
the vrf-name variable.
Enter detail if you want to display the source list of the multicast group.
Enter tracking if you want information on interfaces that have tracking enabled.
IGMP V2 and V3 statistics displayed on the report for each interface.
TABLE 21 Output of show ip igmp group
This field Displays
Group
Port
The address of the multicast group
The physical port on which the multicast group was received.
The virtual interface on which the multicast group was received.
Intf
Timer
Shows the number of seconds the interface can remain in exclude mode. An exclude mode changes to
include mode if it does not receive an "IS_EX" or "TO_EX" message during a certain period of time.
The default is 140 seconds.
Mode
Srcs
Indicates current mode of the interface: include or exclude. If the interface is in Include mode, it admits
traffic only from the source list. If an interface is in exclude mode, it denies traffic from the source list
and accepts the rest.
Identifies the source list that will be included or excluded on the interface.
If IGMP V2 group is in exclude mode with a #_src of 0, the group excludes traffic from 0 (zero) source
list, which means that all traffic sources are included.
FastIron Ethernet Switch IP Multicast Configuration Guide
53-1003085-02
153
Download from Www.Somanuals.com. All Manuals Search And Download.
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.
Displaying static IGMP groups
The following command displays static IGMP groups for the "eng" VRF.
device#show ip igmp vrf eng static
Group Address
Interface Port List
----------------+---------+---------
229.1.0.12
229.1.0.13
229.1.0.14
229.1.0.92
4/1 ethe 4/1
4/1 ethe 4/1
4/1 ethe 4/1
4/1 ethe 4/1
Syntax: show ip igmp [ vrf vrf-name ] static
The vrf parameter specifies that you want to display static IGMP group information for the VRF
specified by the vrf-name variable.
TABLE 22 Output of show ip igmp vrf static
This field
Displays
Group Address
Interface Port List
The address of the multicast group.
The physical ports on which the multicast groups are received.
Displaying the IGMP status of an interface
You can display the status of a multicast enabled port by entering a command such as the following.
device# show ip igmp interface
---------+------+---------+---------------+---------+-----+-----+---------
Intf/Port|Groups| Version |Querier
| Timer |V1Rtr|V2Rtr|Tracking
|OQrr GenQ|
|
|Oper Cfg|
|
|
---------+------+----+----+---------------+----+----+-----+-----+---------
e6/3
e6/4
v30
1
0
1
3
2
3
3
3
3
2
2
2
2
3 Self
- Self
3
0
0
94 No
94 No
No
No
Disabled
Disabled
Disabled
e6/2
e6/2
- Self
3
0
0
20 No
20 No
No
No
v40
v50
0
0
Disabled
Disabled
- Self
-
- Self
- 50.1.1.10
- Self
e12/1
e6/8
e6/1
0
46
29 No
0 No
No
Yes
Yes
0 115 No
Syntax: show ip igmp [ vrf vrf-name ] interface [ ve number | ethernet port-address | tunnel num ]
The vrf parameter specifies that you want to display IGMP interface information for the VRF specified
by the vrf-name variable.
154
FastIron Ethernet Switch IP Multicast Configuration Guide
53-1003085-02
Download from Www.Somanuals.com. All Manuals Search And Download.
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.
The report shows the following information:
TABLE 23 Output of show ip igmp interface
This field
Intf
Displays
The virtual interface on which IGMP is enabled.
The physical port on which IGMP is enabled.
The number of groups that this interface or port has membership.
Port
Groups
Version
Oper
The IGMP version that is operating on the interface.
The IGMP version that is configured for this interface.
Cfg
Querier
Where the Querier resides:
The IP address of the router where the querier is located
or
Self - if the querier is on the same router as the intf or port.
Max response
oQrr
Other Querier present timer.
GenQ
General Query timer
V1Rtr
Whether IGMPv1 is present on the intf or port.
Whether IGMPv2 is present on the intf or port.
V2Rtr
Tracking
Fast tracking status:
Enabled
or
Disabled
FastIron Ethernet Switch IP Multicast Configuration Guide
53-1003085-02
155
Download from Www.Somanuals.com. All Manuals Search And Download.
Clearing IGMP traffic statistics
Displaying IGMP traffic status
To display the traffic status on each virtual routing interface, enter the following command.
device# show ip igmp traffic
Recv QryV2 QryV3 G-Qry GSQry MbrV2 MbrV3 Leave IsIN IsEX ToIN ToEX ALLOW BLK
v5
29
15
0
0
0
0
0
0
0
0
0
0
0
0
0
0
30
97
0
0
0
0
60
142
0
0
37
0
0
2
0
0
2
0
0
3
0
0
2
v18
v110
Send QryV1 QryV2 QryV3 G-Qry GSQry
v5
v18
v110
0
0
0
2
0
0
0
30
30
0
30
44
0
0
11
Syntax: show ip igmp [vrf vrf-name ] traffic
The vrf parameter specifies that you want to display IGMP traffic information for the VRF specified by
the vrf-name variable.
The report shows the following information:
TABLE 24 Output of show ip igmp vrf traffic
This field Displays
QryV2
QryV3
G-Qry
GSQry
MbrV2
MbrV3
Leave
IsIN
Number of general IGMP V2 query received or sent by the virtual routing interface.
Number of general IGMP V3 query received or sent by the virtual routing interface.
Number of group specific query received or sent by the virtual routing interface.
Number of source specific query received or sent by the virtual routing interface.
The IGMP V2 membership report.
The IGMP V3 membership report.
Number of IGMP V2 "leave" messages on the interface. (See ToEx for IGMP V3.)
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.
Number of times the interface mode changed from include to exclude.
Number of times that additional source addresses were allowed or denied on the interface:
Number of times that sources were removed from an interface.
ToEX
ALLOW
BLK
Clearing IGMP traffic statistics
To clear statistics for IGMP traffic, enter the following command.
device# clear ip igmp traffic
156
FastIron Ethernet Switch IP Multicast Configuration Guide
53-1003085-02
Download from Www.Somanuals.com. All Manuals Search And Download.
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.
Brocade#show ip igmp settings
IGMP Global Configuration
Query Interval
: 125s
: 10s
: 260s
: 2
Configured Interval
Configured Version
: 125
: 0
Max Response Time
Group Membership Time
Operating Version
Robustness Variable
Router Alert Check
: 2
: Enabled
Last Member Query Interval: 1
Older Host Present Timer : 260
Last Member Query Count: 2
Maximum Group Address
: 4096
Syntax: show ip igmp [vrf vrf-name ] settings
The vrf parameter specifies that you want to display IGMP settings information for the VRF specified by
the vrf-name variable.
The report shows the following information:
TABLE 25 Output of show ip igmp settings
This field
Displays
Query Interval
How often the router will query an interface for group membership.
The query interval that has been configured for the router.
Configured Query
Interval
Max Response Time
The length of time in seconds that the router will wait for an IGMP (V1 or V2) response
from an interface before concluding that the group member on that interface is down and
removing it from the group.
Group Membership
Time
The length of time in seconds that a group will remain active on an interface in the
absence of a group report.
Configured Version
Operating Version
Robustness Variable
The IGMP version configured on the router.
The IGMP version operating on the router.
The Robustness Variable allows tuning for the expected packet loss on a network. If a
network is expected to be lossy, the Robustness Variable may be increased. IGMP is
robust to (Robustness Variable -1) packet losses. The Robustness Variable must not be
zero, and should not be one. Default: 2
Router Alert Check
IGMP (v2/v3) messages have a router-alert option in the IP header. By default this is
validated by the router and it drops the packets without the router-alert option. If this
check is disabled, IGMP messages without the router-alert option are accepted.
FastIron Ethernet Switch IP Multicast Configuration Guide
53-1003085-02
157
Download from Www.Somanuals.com. All Manuals Search And Download.
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. Default: 10 (1 second)
Last Member Query
Count
The Last Member Query Count is the number of Group-Specific Queries sent before the
router assumes there are no local members. The Last Member Query Count is also the
number of Group-and-Source-Specific Queries sent before the router assumes there are
no listeners for a particular source. Default: the Robustness Variable.
Older Host Present
Timer
The Older Host Present Interval is the time-out for transitioning a group back to IGMPv3
mode when an older version report is sent for that group. When an older version report is
received, routers set their Older Host Present Timer to Older Host Present Interval.
This value must be ((the Robustness Variable) times (the Query Interval)) plus (one
Query Response Interval).
Maximum Group
Address
This value indicates the maximum number of group address that can be accepted by the
router.
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.
With Source-specific multicast (SSM), the "channel" concept is introduced where a "channel" consists
of a single source and multiple receivers who specifically register to get broadcasts from that source.
Consequently, receivers are not burdened with receiving data they have no interest in, and network
bandwidth requirements are reduced because the broadcast need only go to a sub-set of users. The
address range 232/8 has been assigned by the Internet Assigned Numbers Authority (IANA) for use
with SSM.
IGMP V3 and source specific multicast protocols
When IGMP V3 and PIM Sparse (PIM-SM) is enabled, the source specific multicast service (SSM) can
be configured. SSM simplifies PIM-SM by eliminating the RP and all protocols related to the RP.
IGMPv3 and PIM-SM must be enabled on any ports that you want SSM to operate.
Configuring PIM SSM group range
PIM Source Specific Multicast (SSM) is a subset of the PIM SM protocol. In PIM SSM mode, the
shortest path tree (SPT) is created at the source. The SPT is created between the receiver and
source, but the SPT is built without the help of the RP. The router closest to the interested receiver
host is notified of the unicast IP address of the source for the multicast traffic. PIM SSM goes directly
to the source-based distribution tree without the need of the RP connection. PIM SSM is different from
PIM SM because it forms its own SPT, without forming a shared tree. The multicast address group
range is 232.0.0.0/8.
158
FastIron Ethernet Switch IP Multicast Configuration Guide
53-1003085-02
Download from Www.Somanuals.com. All Manuals Search And Download.
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. If this is not
configured, the range will default to 232/8 as assigned by the Internet Assigned Numbers Authority
(IANA) for use with SSM.
The address-mask parameter specifies the mask for the SSM address range.
To disable SSM, use the [no] form of this command.
Displaying source-specific multicast configuration information
To display PIM Sparse configuration information, use the show ip pim sparse command as described
Configuring multiple SSM group ranges
The ssm-enable rangeacl-id/acl-name command allows you to configure multiple SSM group ranges
using an ACL.
Configuration Considerations
•
•
The existing ssm-enable rangegroup-addressaddress-mask command will continue to exist.
The ACL must be configured with the SSM group address in the permit clause of the ssm-enable
rangeacl-id or acl-name command. If the ssm-enable rangegroup-addressaddress-mask
command permits a clause, then that group will also operate in the PIM-SM mode.
•
•
•
If the ssm-enable rangeacl-id or acl-name command is configured with a non-existent or empty
ACL, then the SSM group will operate in PIM-SM mode (non PIM-SSM mode). However when an
ACL is added or updated, then the group will exist in a PIM-SSM mode. By default, an empty ACL
will deny all.
By default, the group address mentioned in the IGMPv2 ssm-mapping ACL will decide if the group
address is a PIM-SSM group or non PIM-SSM group. Therefore, if a user wants to prevent a group
from operating in PIM-SSM mode, then the user’s configuration must consistently deny the group in
all configuration options for PIM-SSM range.
ACL of any type (named or unnamed, standard or extended) can be used to specify the SSM group
range. If an extended ACL is used, then the destination ip address should be used to specify the
group address. Any configuration in the source address of an extended ACL is ignored. Only permit
statements are considered in the ACL configuration. Any deny statements in the ACL clause are
also ignored.
To configure multiple SSM group address using an ACL, enter the following command under the router
pim configuration:
device(config)#router pim
device(config-pim-router)#ssm-enable range xyz
The example displayed above configures PIM so that it uses the group addresses allowed by ACL, xyz
as its PIM SSM range.
Syntax: [no] ssm-enable range acl-id or acl-name
FastIron Ethernet Switch IP Multicast Configuration Guide
53-1003085-02
159
Download from Www.Somanuals.com. All Manuals Search And Download.
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.
Displaying information for PIM SSM range ACL
To display information for PIM SSM range ACL configuration enter the following command at any CLI
level:
device#show ip pim sparse
Global PIM Sparse Mode Settings
Maximum Mcache
: 0
: 30
: 60
Current Count
: 0
Hello interval
Neighbor timeout
Inactivity interval
Register Probe Time
Hardware Drop Enabled
: 105
Join/Prune interval
: 180
: 10
: Yes
Register Suppress Time : 60
SPT Threshold
: 1
Bootstrap Msg interval : 60
Candidate-RP Msg interval : 60
Register Suppress interval : 60
Register Stop Delay
SSM Enabled
: 60
: Yes
SSM Group Range
SSM Group Range ACL
Route Precedence
: 224.1.1.1/24
: xyz
: mc-non-default mc-default uc-non-default uc-default
NOTE
The show ipv6 pim sparse command also displays PIM SSM range ACL configuration.
IGMPv2 SSM mapping
The PIM-SSM feature requires all IGMP hosts to send IGMPv3 reports. Where you have an IGMPv2
host, this can create a compatibility problem. In particular, the reports from an IGMPv2 host contain a
Group Multicast Address but do not contain source addresses. The IGMPv3 reports contain both the
Group Multicast Address and one or more source addresses. This feature converts IGMPv2 reports
into IGMPv3 reports through use of the ip igmp ssm-map commands and a properly configured ACL.
The ACL used with this feature filters for the Group Multicast Address. The ACL is then associated
with one or more source addresses using the ip igmp ssm-map command. When the ip igmp ssm-
map enable command is configured, IGMPv3 reports are sent for IGMPv2 hosts.
The following sections describe how to configure the ACL and the ip igmp ssm-map commands to
use the IGMPv2 SSM mapping feature:
•
•
Configuring an ACL for IGMPv2 SSM mapping
Configuring the IGMPv2 SSM Mapping Commands
NOTE
IGMPv2 SSM Mapping is not supported for IGMP static groups.
160
FastIron Ethernet Switch IP Multicast Configuration Guide
53-1003085-02
Download from Www.Somanuals.com. All Manuals Search And Download.
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.0) is implied.
In the following example, access-list 20 is configured for the group multicast address: 224.1.1.0 with a
subnet mask of 0.0.0.255.
device(config)# access-list 20 permit 224.1.1.0 0.0.0.225
In the following example, access-list 20 is configured for the group multicast address: 239.1.1.1 by
including the host keyword.
device(config)# access-list 20 host 239.1.1.1
For extended ACLs, the source address variable must contain either 000 or the any keyword.
Additionally, the extended ACL must be configured with a permit clause and the host keyword. 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.0) is implied.
The ip-destination-address variable must contain the group multicast address.
In the following example, access-list 100 is configured for the group multicast address: 232.1.1.1 with a
subnet mask of 0.0.0.255.
device(config)# access-list 20 permit 224.1.1.0 0.0.0.225
In the following example, access-list 100 is configured for the group multicast address: 232.1.1.1.
device(config)# access-list 100 permit any host 232.1.1.1
Configuring the IGMPv2 SSM mapping commands
The ip ssm-map commands are used to enable the IGMPv2 mapping feature and to define the maps
between IGMPv2 Group addresses and multicast source addresses as described in the following
sections.
Enabling IGMPv2 SSM mapping
To enable the IGMPv2 mapping feature enter the command as shown in the following.
device(config)# ip igmp ssm-map enable
Syntax: [no] ip igmp ssm-map enable
The no option is used to turn off the IGMPv2 mapping feature that has previously been enabled.
Configuring the map between a IGMPv2 group address and a multicast source
To configure a map between an IGMPv2 Group address and a multicast source address use the ip
igmp ssm-map static command, as shown in the following.
device(config)# ip igmp ssm-map 20 1.1.1.1
Syntax: [no] ip igmp ssm-map aci-id source-address
FastIron Ethernet Switch IP Multicast Configuration Guide
53-1003085-02
161
Download from Www.Somanuals.com. All Manuals Search And Download.
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. The ip igmp ssm-map commands are configured to map the ACLs to
source addresses and to enable the feature on the router.
device(config)# access-list 20 host 239.1.1.1
device(config)# access-list 20 permit 224.1.1.0 0.0.0.225
device(config)# access-list 100 permit any host 232.1.1.1
device(config)# ip igmp ssm-map 20 1.1.1.1
device(config)# ip igmp ssm-map 20 2.2.2.2
device(config)# ip igmp ssm-map 100 1.1.1.1
device(config)# ip igmp ssm-map enable
Displaying an IGMP SSM mapping information
The show ip igmp ssm-map command displays the association between a configured ACL and
source address mapped to it, as shown in the following.
device# show ip igmp ssm-map
+---------+-----------------+
| Acl id | Source Address |
+---------+-----------------+
20
100
20
1.1.1.1
1.1.1.1
2.2.2.2
2.2.2.3
2.2.2.4
2.2.2.5
2.2.2.6
20
20
20
20
Syntax: show ip igmp [vrf vrf-name ] ssm-map
The show ip igmp ssm-map group-address displays the ACL ID that has the specified multicast
group address in its permit list and lists the source addresses mapped to the specified multicast group
address, as shown in the following.
device# show ip igmp ssm-map 232.1.1.1
+---------+-----------------+
| Acl id | Source Address |
+---------+-----------------+
20
100
20
1.1.1.1
1.1.1.1
2.2.2.2
2.2.2.3
2.2.2.4
2.2.2.5
2.2.2.6
20
20
20
20
Syntax: show ip igmp ssm-map group-address
162
FastIron Ethernet Switch IP Multicast Configuration Guide
53-1003085-02
Download from Www.Somanuals.com. All Manuals Search And Download.
IPv6 Multicast Protocols
● Supported IPv6 Multicast Features...............................................................................163
● PIM Anycast RP............................................................................................................194
● Multicast Listener Discovery and source-specific multicast protocols...........................196
Supported IPv6 Multicast Features
Lists IPv6 Multicast features supported on FastIron devices.
The following table displays the individual device and the IPv6 Multicast features supported.
Feature
ICX 6430
ICX 6450
FCX
ICX 6610
ICX 6650
FSX 800
ICX 7750
FSX 1600
08.0.012
08.0.012
08.0.013
MLD (v1 and v2)
No
No
08.0.01
08.0.01
08.0.01
08.0.01
08.0.10a
08.0.10a
08.0.10
08.0.10
08.0.013
MLD membership tracking and fast
leave for v2
IPv6 PMRI
No
No
No
No
No
No
No
No
08.0.012
08.0.012
08.0.012
08.0.01 2
08.0.012
08.0.012
08.0.12
08.0.01
08.0.01
08.0.01
08.0.01
08.0.01
08.0.01
08.0.01
08.0.01
08.0.01
08.0.01
08.0.01
08.0.01
08.0.01
08.0.01
08.0.10a
08.0.10a
08.0.10a
08.0.10a
08.0.10a
08.0.10a
08.0.10a
08.0.013
08.0.013
08.0.013
08.0.013
08.0.013
08.0.013
08.0.013
08.0.013
08.0.10
08.0.10
08.0.10
08.0.10
08.0.10
08.0.10
08.0.10
IPv6 PIM-SSM
IPv6 PIM Sparse
IPv6 PIM Anycast RP
IPv6 multicast boundaries
Embedded RPv6
Multi-VRF support
Hardware replication resource sharing
08.0.012
08.0.012
08.0.01
08.0.01
08.0.01
08.0.01
08.0.10a
08.0.10a
08.0.10
08.0.10
Concurrent support for multicast routing No
and snooping
08.0.013
Static mroute
No
08.0.10a2
08.0.10a3
08.0.10a
08.0.10a
08.0.10a
08.0.10a
2
In a mixed stack only.
3rd generation modules only.
3
FastIron Ethernet Switch IP Multicast Configuration Guide
53-1003085-02
163
Download from Www.Somanuals.com. All Manuals Search And Download.
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).
FIGURE 10 Example IPv6 PIM Sparse domain
PIM Sparse router types
Routers that are configured with PIM Sparse interfaces also can be configured to fill one or more of
the following roles:
•
BSR - The Bootstrap Router (BSR) distributes RP information to the other PIM Sparse routers
within the domain. Each PIM Sparse domain has one active BSR. For redundancy, you can
configure ports on multiple routers as candidate BSRs. The PIM Sparse protocol uses an election
process to select one of the candidate BSRs as the BSR for the domain. The BSR with the
highest BSR priority (a user-configurable parameter) is elected. If the priorities result in a tie, then
page 164, PIM Sparse router B is the BSR. Port 2/2 is configured as a candidate BSR.
•
RP - The Rendezvous Points (RP) is the meeting point for PIM Sparse sources and receivers. A
PIM Sparse domain can have multiple RPs, but each PIM Sparse multicast group address can
have only one active RP. PIM Sparse routers learn the addresses of RPs and the groups for
which they are responsible from messages that the BSR sends to each of the PIM Sparse routers.
a candidate Rendezvous Point (RP).
To enhance overall network performance, the device uses the RP to forward only the first packet from
a group source to the group receivers. After the first packet, the device calculates the shortest path
164
FastIron Ethernet Switch IP Multicast Configuration Guide
53-1003085-02
Download from Www.Somanuals.com. All Manuals Search And Download.
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. The source is attached to PIM Sparse router A and the recipient is attached to
PIM Sparse router C. PIM Sparse router B is the RP for this multicast group. As a result, the default
path for packets from the source to the receiver is through the RP. However, the path through the RP
sometimes is not the shortest path. In this case, the shortest path between the source and the receiver
is over the direct link between router A and router C, which bypasses the RP (router B).
To optimize PIM traffic, the protocol contains a mechanism for calculating the Shortest Path Tree (SPT)
between a given source and a receiver. PIM Sparse routers can use the SPT as an alternative to using
the RP for forwarding traffic from a source to a receiver. By default, the device forwards the first packet
it receives from a given source to a given receiver using the RP path, but subsequent packets from that
source to that receiver through the SPT. In Figure 10 on page 164, router A forwards the first packet
from group fec0:1111::1 source to the destination by sending the packet to router B, which is the RP.
Router B then sends the packet to router C. For the second and all future packets that router A receives
from the source for the receiver, router A forwards them directly to router C using the SPT path.
RFC 3513 and RFC 4007 compliance for IPv6 multicast scope-based
forwarding
The IPv6 multicast implementation recognizes scopes and conforms to the scope definitions in RFC
3513. Per RFC 3513, scopes 0 and 3 are reserved and packets are not forwarded with an IPv6
destination multicast address of scopes 0 and 3. Additionally, scopes 1 and 2 are defined as Node-
Local and Link-Local and are not forwarded. Thus, the implementation forwards only those packets with
an IPv6 multicast destination address with scope 4 or higher.
RFC 4007 defines ‘scope zones’ and requires that the forwarding of packets received on any interface
of a particular scope zone be restricted to that scope zone. Currently, the device supports one zone for
each scope, and the default zone for scope 4 and higher consists of all interfaces in the system. Thus,
the default zones for scope 4 and higher are the same size.
Configuring PIM Sparse
To configure the device for IPv6 PIM Sparse, perform the following tasks:
•
•
Enable the IPv6 PIM Sparse of multicast routing.
Configure VRF then enable IPv6 Protocol Independent Multicast Sparse mode (PIM-SM) for a
specified VRF, if applicable.
•
•
•
•
•
•
Configure an IPv6 address on the interface.
Enable IPv6 PIM Sparse.
Identify the interface as an IPv6 PIM Sparse border, if applicable.
Identify the device as a candidate PIM Sparse Bootstrap Router (BSR), if applicable.
Identify the 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).
FastIron Ethernet Switch IP Multicast Configuration Guide
53-1003085-02
165
Download from Www.Somanuals.com. All Manuals Search And Download.
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.
device(config)# ipv6 router pim
device(config-ipv6-pim-router)#
To enable IPv6 PIM Sparse mode on an interface, enter commands such as the following.
device(config)# interface ethernet 2/2
device(config-if-e10000-2/2)# ipv6 address a000:1111::1/64
device(config-if-e10000-2/2)# ipv6 pim-sparse
Syntax: [no] ipv6 pim-sparse
Use the no option to remove IPv6 PIM sparse configuration from the interface.
The commands in this example add an IPv6 interface to port 2/2, then enable IPv6 PIM Sparse on the
interface.
Configuring IPv6 PIM-SM on a virtual routing interface
You can enable IPv6 PIM-SM on a virtual routing interface by entering commands such as the
following.
device(config)# interface ve 15
device(config-vif-15)# ipv6 address a000:1111::1/64
device(config-vif-15)# ipv6 pim-sparse
Enabling IPv6 PIM-SM for a specified VRF
To enable IPv6 PIM-SM for the VRF named "blue", create the VRF named "blue", enable it for IPv6
routing, and then enable IPv6 PIM-SM for the VRF, as shown in the following example.
device(config)# vrf blue
device(config-vrf-blue)# rd 11:1
device(config-vrf-blue)# address-family ipv6
device(config-vrf-blue-ipv6)# router pim
device(config-pim-router)# ipv6 router pim vrf blue
device(config-ipv6-pim-router-vrf-blue)
Syntax: [no] ipv6 router pim [ vrf vrf-name ]
The vrf parameter allows you to configure IPv6 PIM-SM on the virtual routing instance (VRF) specified
by the vrf-name variable. All PIM parameters available for the default router instance are configurable
for a VRF-based PIM instance.
Use the no option to remove all configuration for PIM multicast on the specified VRF.
166
FastIron Ethernet Switch IP Multicast Configuration Guide
53-1003085-02
Download from Www.Somanuals.com. All Manuals Search And Download.
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.
To configure the device as a candidate BSR, enter commands such as the following.
device(config)# ipv6 router pim
device(config-ip6-pim-router)# bsr-candidate ethernet 1/3 32 64
This command configures Ethernet interface 1/3 as the BSR candidate with a mask length of 32 and a
priority of 64.
To configure the device as a candidate BSR for a specified VRF, enter the commands as shown in the
following example.
device(config)# ipv6 router pim vrf blue
device(config-ipv6-pim-router-vrf-blue)# bsr-candidate ethernet 1/3 32 64
Syntax: [no] bsr-candidate {ethernet slot / portnum | loopback num | ve num hash-mask-length [
priority ]}
Use the no option to remove the candidate BSR configuration for a specified VRF.
The ethernetslot /portnum | loopbacknum | venum parameter specifies the interface. The device will
advertise the specified interface’s IP address as a candidate BSR:
•
•
•
Enter ethernetslot /portnum for a physical interface (port).
Enter loopbacknum for a loopback interface.
Enter venum for a virtual interface.
The hash-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 through 32.
The priority variable specifies the BSR priority. You can specify a value from 0 through 255. When the
election process for BSR takes place, the candidate BSR with the highest priority becomes the BSR.
The default is 0.
Setting the BSR message interval
The BSR message interval timer defines the interval at which the BSR sends RP candidate data to all
IPv6-enabled routers within the IPv6 PIM Sparse domain. The default is 60 seconds.
To set the IPv6 PIM BSR message interval timer to 16 seconds, enter commands such as the following.
device(config)# ipv6 router pim
device(config-ipv6-pim-router)# bsr-msg-interval 16
To set the IPv6 PIM BSR message interval timer to 16 seconds for a specified VRF, enter the
commands as shown in the following example.
device(config)# ipv6 router pim vrf blue
device(config-ipv6-pim-router-vrf-blue)# bsr-msg-interval 16
Syntax: [no] bsr-msg-interval num
FastIron Ethernet Switch IP Multicast Configuration Guide
53-1003085-02
167
Download from Www.Somanuals.com. All Manuals Search And Download.
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.
device(config)# ipv6 router pim vrf blue
device(config-ipv6-pim-router-vrf-blue)# rp-candidate ethernet 2/2
Syntax: [no] rp-candidate { ethernet slot / portnum | loopback num | ve num }
The ethernetslot /portnum | loopbacknum | venum parameter specifies the interface. The device will
advertise the specified interface IP address as a candidate RP:
•
•
•
Enter ethernetslot /portnum for a physical interface (port).
Enter loopbacknum for a loopback interface.
Enter venum for a virtual interface.
To add address ranges for which the device is a candidate RP, enter commands such as the following.
device(config)# ipv6 router pim
device(config-ipv6-pim-router)# rp-candidate add ff02::200:2 64
To add address ranges for a specified VRF for which the device is a candidate RP, enter commands
such as the following.
device(config)# ipv6 router pim vrf blue
device(config-ipv6-pim-router-vrf-blue)# rp-candidate add ff02::200:2 64
Syntax: [no] rp-candidate add group-ipv6address mask-bits
You can delete the configured RP candidate group ranges by entering commands such as the
following.
device(config)# ipv6 router pim
device(config-ipv6-pim-router)# rp-candidate delete ff02::200:1 128
You can delete the configured RP candidate group ranges for a specified VRF by entering commands
such as the following:
device(config)# ipv6 router pim vrf blue
device(config-ipv6-pim-router-vrf-blue)# rp-candidate delete ff02::200:1 128
Syntax: [n]o rp-candidate delete group-ipv6address mask-bits
The usage for the group-ipv6 addressmask-bits parameter is the same as for the rp-candidate add
command.
Statically specifying the RP
It is recommended that you use the IPv6 PIM Sparse mode RP election process so that a backup RP
can automatically take over if the active RP router becomes unavailable. However, if you do not want
the RP to be selected by the RP election process but instead you want to explicitly identify the RP by
its IPv6 address, use the rp-address command.
168
FastIron Ethernet Switch IP Multicast Configuration Guide
53-1003085-02
Download from Www.Somanuals.com. All Manuals Search And Download.
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.
To specify the IPv6 address of the RP, enter commands such as the following.
device(config)# ipv6 router pim
device(config-ipv6-pim-router)# rp-address 31::207
The command in the previous example identifies the router interface at IPv6 address 31:207 as the RP
for the IPv6 PIM Sparse domain. The device will use the specified RP and ignore group-to-RP
mappings received from the BSR.
To specify the IPv6 address of the RP 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-address 31::207
Syntax: [no] rp-address ipv6-addr
The ipv6-addr parameter specifies the IPv6 address of the RP.
Updating IPv6 PIM Sparse forwarding entries with a new RP configuration
If you make changes to your static RP configuration, the entries in the IPv6 PIM Sparse multicast
forwarding table continue to use the old RP configuration until they are aged out.
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 the
rp-address command.
To update the entries in an IPv6 PIM Sparse static multicast forwarding table with a new RP
configuration, enter the following command at the privileged EXEC level of the CLI.
device(config)# clear ipv6 pim rp-map
Syntax: clear ipv6 pim [ vrf vrf_name ] rp-map
Embedded Rendezvous Point
Global deployment of IPv4 multicast relies on Multicast Source Discovery Protocol (MSDP) to convey
information about the active sources. Because IPv6 provides more address space, the RP address can
be included in the multicast group address.
NOTE
The IPv6 group address must be part of the FF70:/12 prefix.
Embedded RP support is enabled by default. You can disable it using the following commands.
device(config)# ipv6 router pim
device(config-ipv6-pim-router)# no rp-embedded
FastIron Ethernet Switch IP Multicast Configuration Guide
53-1003085-02
169
Download from Www.Somanuals.com. All Manuals Search And Download.
Changing the Shortest Path Tree threshold
To disable embedded RP support for a specified VRF, enter the following commands.
device(config)# ipv6 router pim vrf blue
device(config-ipv6-pim-router-vrf-blue)# no rp-embedded
Syntax: [no] rp-embedded
Changing the Shortest Path Tree threshold
In a typical IPv6 PIM Sparse domain, there may be two or more paths from a designated router (DR)
for a multicast source to an IPv6 PIM group receiver:
•
Path through the RP - This is the path the device uses the first time it receives traffic for an IPv6
PIM group. However, the path through the RP may not be the shortest path from the device to the
receiver.
•
Shortest Path - Each IPv6 PIM Sparse router that is a DR for an IPv6 receiver calculates a short
path tree (SPT) towards the source of the IPv6 multicast traffic. The first time the device
configured as an IPv6 PIM router receives a packet for an IPv6 group, it sends the packet to the
RP for that group, which in turn will forward it to all the intended DRs that have registered with the
RP. The first time the device is a recipient, it receives a packet for an IPv6 group and evaluates
the shortest path to the source and initiates a switchover to the SPT. Once the device starts
receiving data on the SPT, the device proceeds to prune itself from the RPT.
By default, the device switches from the RP to the SPT after receiving the first packet for a given IPv6
PIM Sparse group. The device maintains a separate counter for each IPv6 PIM Sparse source-group
pair.
You can change the number of packets the device receives using the RP before switching to using the
SPT.
To change the number of packets the device receives using the RP before switching to the SPT, enter
commands such as the following.
device(config)# ipv6 router pim
device(config-ipv6-pim-router)# spt-threshold 1000
To change the number of packets the device receives using the RP before switching to the SPT for a
specified VRF, enter commands such as the following.
device(config)# ipv6 router pim vrf blue
device(config-ipv6-pim-router-vrf-blue)# spt-threshold 1000
Syntax: [no] spt-threshold num
The num parameter specifies the number of packets. If you enter a specific number of packets, the
device does not switch over to using the SPT until it has sent the number of packets you specify using
the RP.
Setting the RP advertisement interval
To specify how frequently the candidate RP configured on the device sends candidate RP
advertisement messages to the BSR, enter commands such as the following.
device(config)# ipv6 router pim
device(config-ipv6-pim-router)# rp-adv-interval 180
170
FastIron Ethernet Switch IP Multicast Configuration Guide
53-1003085-02
Download from Www.Somanuals.com. All Manuals Search And Download.
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.
Changing the PIM Join and Prune message interval
By default, the device sends PIM Sparse Join or Prune messages every 60 seconds. These messages
inform other PIM Sparse routers about clients who want to become receivers (Join) or stop being
receivers (Prune) for PIM Sparse groups.
NOTE
Use the same Join or Prune message interval on all the PIM Sparse routers in the PIM Sparse domain.
If the routers do not all use the same timer interval, the performance of PIM Sparse can be adversely
affected.
To change the Join or Prune interval, enter commands such as the following:
Device(config)# ipv6 router pim
Device(config-ipv6-pim-router)# message-interval 30
To change the Join or Prune interval for a specified VRF, enter the commands as shown in the following
example:
Device(config)# ipv6 router pim vrf blue
Device(config-ipv6-pim-router-vrf-blue)# message-interval 30
Syntax: [no] message-interval seconds
The seconds parameter specifies the number of seconds and can be from 10 through 18724 seconds.
The default is 60 seconds.
Modifying neighbor timeout
Neighbor timeout is the interval after which a PIM router will consider a neighbor to be absent. If the
timer expires before receiving a new hello message, the PIM router will time out the neighbor.
To apply an IPv6 PIM neighbor timeout value of 50 seconds to all ports on the router operating with
PIM, enter the commands such as the following.
device(config)# ipv6 router pim
device(config-ipv6-pim-router)# nbr-timeout 50
To apply an IPv6 PIM neighbor timeout value of 50 seconds for a specified VRF operating with PIM,
enter the commands such as the following.
device(config)# ipv6 router pim vrf blue
device(config-ipv6-pim-router-vrf-blue)# nbr-timeout 50
Syntax: [no] nbr-timeout seconds
The seconds parameter specifies the number of seconds. The valid range is from 35 through 65535
seconds. The default is 105.
FastIron Ethernet Switch IP Multicast Configuration Guide
53-1003085-02
171
Download from Www.Somanuals.com. All Manuals Search And Download.
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.
device(config)# ipv6 router pim
device(config-ipv6-pim-router)# prune-wait 2
To change the default join override time to 2 seconds for a specified VRF, enter commands such as
the following.
device(config)# ipv6 router pim vrf blue
device(config-ipv6-pim-router-vrf-blue)# prune-wait 2
Syntax: [no] prune-wait seconds
The seconds parameter specifies the number of seconds. The valid range is from 0 through 30
seconds. The default is 3 seconds.
Setting the register suppress interval
The register-suppress-time command allows you to set the amount of time the PIM router uses to
periodically trigger the NULL register message.
NOTE
The register suppress time configuration applies only to the first hop PIM router.
To change the default register suppress time to 90 seconds, enter commands such as the following:
device(config)# ipv6 router pim
device(config-ipv6-pim-router)# register-suppress-time 90
To change the default register suppress time to 90 seconds for a specified VRF, enter commands
such as the following:
device(config)# ipv6 router pim vrf blue
device(config-ipv6-pim-router-vrf-blue)# register-suppress-time 90
Syntax: [no] register-suppress-time seconds
The seconds parameter specifies the number of seconds. The valid range is from 60 through 120
seconds. The default is 60 seconds.
Setting the register probe time
The register-probe-time command allows you to set the amount of time the PIM router waits for a
register-stop from an RP before it generates another NULL register to the PIM RP. The register probe
time configuration applies only to the first hop PIM router.
NOTE
Once a PIM first hop router successfully registers with a PIM RP, the PIM first hop router will not
default back to the data registration. All subsequent registers will be in the form of the NULL
registration.
172
FastIron Ethernet Switch IP Multicast Configuration Guide
53-1003085-02
Download from Www.Somanuals.com. All Manuals Search And Download.
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.
device(config)# ipv6 router pim vrf blue
device(config-ipv6-pim-router-vrf-blue)# register-probe-time 20
Syntax: [no] register-probe-time seconds
The seconds parameter specifies the number of seconds. The valid range is from 10 through 50
seconds. The default is 10 seconds.
Setting the inactivity timer
The router deletes a forwarding entry if the entry is not used to send multicast packets. The IPv6 PIM
inactivity timer defines how long a forwarding entry can remain unused before the router deletes it.
To apply an IPv6 PIM inactivity timer of 160 seconds to all IPv6 PIM interfaces, enter the following.
device(config)# ipv6 router pim
device(config-ipv6-pim-router)# inactivity-timer 160
To apply an IPv6 PIM inactivity timer of 160 seconds for a specified VRF, enter the commands as
shown in the following example.
device(config)# ipv6 router pim vrf blue
device(config-ipv6-pim-router-vrf-blue)# inactivity-timer 160
Syntax: [no] inactivity-timer seconds
The seconds parameter specifies the number of seconds. The valid range is 60 through 3600 seconds.
The default is 180 seconds.
Changing the hello timer
The hello timer defines the interval at which periodic hellos are sent out to PIM interfaces. Routers use
hello messages to inform neighboring routers of their presence. To change the hello timer, enter a
command such as the following.
device(config)# ipv6 router pim
device(config-ipv6-pim-router)# hello-timer 62
To change the hello timer for a specified VRF, enter the commands as shown in the following example.
device(config)# ipv6 router pim vrf blue
device(config-ipv6-pim-router-vrf-blue)# hello-timer 62
Syntax: [n]o hello-timer seconds
The seconds parameter specifies the number of seconds. The valid range is 10 through 3600 seconds.
The default is 30 seconds.
FastIron Ethernet Switch IP Multicast Configuration Guide
53-1003085-02
173
Download from Www.Somanuals.com. All Manuals Search And Download.
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.
With Source-specific Multicast (SSM), the "channel" concept is introduced where a "channel" consists
of a single source and multiple receivers that specifically register to get broadcasts from that source.
Consequently, receivers are not burdened with receiving data they have no interest in, and network
bandwidth requirements are reduced because the broadcast need only go to a subset of users. The
address range ff30:/12 has been assigned by the Internet Assigned Numbers Authority (IANA) for use
with SSM.
SSM simplifies IPv6 PIM-SM by eliminating the RP and all protocols related to the RP.
Configuring Source-specific Multicast
IPv6 PIM-SM must be enabled on any ports on which you want SSM to operate. Enter the ssm-
enable command under the IPv6 router PIM level to globally enable SSM filtering.
device(config)# ipv6 router pim
device(config-ipv6-pim-router)# ssm-enable
To enable SSM for a specified VRF and user-defined address range, enter the commands as shown in
the following.
device(config)# ipv6 router pim vrf blue
device(config-ipv6-pim-router-vrf-blue)# ssm-enable ff44::/32
Syntax: [no] ssm-enable [ range address-range ]
The rangeaddress-range option allows you to define the SSM range of IPv6 multicast addresses.
Configuring a DR priority
The DR priority option lets a network administrator give preference to a particular router in the DR
election process by giving it a numerically higher DR priority. To set a DR priority higher than the
default value of 1, use the ipv6 pim dr-priority command as shown in the example below.
device(config-if-e10000-3/24)# ipv6 pim dr-priority 50
To set a DR priority higher than the default value of 1 on a virtual Ethernet interface, use the ipv6 pim
dr-priority command as shown in the following.
device(config)# interface ve 10
device(config-vif-10)# ipv6 pim dr-priority 50
Syntax: [no] ipv6 pim dr-priority priority-value
The priority-value variable is the value that you want to set for the DR priority. The range of values is
from 0 through 65535. The default value is 1.
The no option removes the command and sets the DR priority back to the default value of 1.
The following information may be useful for troubleshooting:
174
FastIron Ethernet Switch IP Multicast Configuration Guide
53-1003085-02
Download from Www.Somanuals.com. All Manuals Search And Download.
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. If there is at least one PIM router on the subnet that does not
support this option, then the DR election falls back to the backwards compatibility mode in which
the router with the numerically highest IP address on the subnet is declared the DR regardless of
the DR priority values.
Passive Multicast Route Insertion
To prevent unwanted multicast traffic from being sent to the CPU, IPv6 PIM routing and Passive
Multicast Route Insertion (PMRI) can be used together to ensure that multicast streams are only
forwarded out ports with interested receivers and unwanted traffic is dropped in hardware on Layer 3
routers.
PMRI enables a Layer 3 switch running IPv6 PIM Sparse to create an entry for a multicast route (for
example, (S,G)), with no directly attached clients or when connected to another PIM router (transit
network).
When a multicast stream has no output interfaces, the Layer 3 switch can drop packets in hardware if
the multicast traffic meets the following conditions in IPv6 PIM-SM.
•
•
The route has no OIF.
The directly connected source passes source RPF check and completes data registration with the
RP, or the non-directly connected source passes source RPF check.
If the OIF is inserted after the hardware-drop entries are installed, the hardware entries will be updated
to include the OIFs.
NOTE
Disabling hardware-drop does not immediately take away existing hardware-drop entries, they will go
through the normal route aging processing when the traffic stops.
Configuring PMRI
PMRI is enabled by default. To disable PMRI, enter the following commands.
device(config)# ipv6 router pim
device(config-ipv6-pim-router)# hardware-drop-disable
To disable PMRI for a specified VRF, enter the commands as shown in the following example.
device(config)# ipv6 router pim vrf blue
device(config-ipv6-pim-router-vrf-blue)# hardware-drop-disable
Syntax: [no] hardware-drop-disable
Displaying hardware-drop
Use the show ipv6 pim sparse command to display if the hardware-drop feature has been enabled or
disabled.
Brocade# show ipv6 pim sparse
Global PIM Sparse Mode Settings
Maximum Mcache
Hello interval
: 4096
: 30
Current Count
Neighbor timeout
: 7
: 105
FastIron Ethernet Switch IP Multicast Configuration Guide
53-1003085-02
175
Download from Www.Somanuals.com. All Manuals Search And Download.
Displaying system values
Join/Prune interval
: 60
Inactivity interval
Prune Wait Interval
: 180
: 3
Hardware Drop Enabled : Yes
Bootstrap Msg interval : 60
Register Suppress Time : 60
Candidate-RP Msg interval : 60
Register Probe Time
Register Suppress interval : 60
SPT Threshold : 1
: 10
Register Stop Delay
SSM Enabled
SSM Group Range
Route Precedence
Embedded RP Enabled
: 10
: Yes
: ff30::/32
: mc-non-default mc-default uc-non-default uc-default
: Yes
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 PIM6 hardware mcache values.
device(config)#show default values
System Parameters
pim6-hw-mcache
Default
512
Maximum
1024
Current
1024
Configured
1024
Displaying PIM Sparse configuration information and statistics
You can display the following PIM Sparse information:
•
•
•
•
•
•
•
•
•
•
•
•
•
•
Basic PIM Sparse configuration information
IPv6 interface information
Group information
BSR information
Candidate RP information
RP-to-group mappings
RP information for an IPv6 PIM Sparse group
RP set list
Multicast neighbor information
The IPv6 PIM multicast cache
IPv6 PIM RPF
IPv6 PIM counters
IPv6 PIM resources
IPv6 PIM traffic statistics
Displaying basic PIM Sparse configuration information
Enter the show ipv6 pim sparse command at any CLI level to display IPv6 PIM Sparse configuration
information.
Brocade# show ipv6 pim sparse
Global PIM Sparse Mode Settings
Maximum Mcache
: 4096
: 30
Current Count
: 7
Hello interval
Join/Prune interval
Neighbor timeout
Inactivity interval
Prune Wait Interval
: 105
: 180
: 3
: 60
Hardware Drop Enabled : Yes
Bootstrap Msg interval : 60
Register Suppress Time : 60
Candidate-RP Msg interval : 60
Register Probe Time : 10
Register Suppress interval : 60
SPT Threshold : 1
Register Stop Delay
SSM Enabled
SSM Group Range
Route Precedence
Embedded RP Enabled
: 10
: Yes
: ff30::/32
: mc-non-default mc-default uc-non-default uc-default
: Yes
176
FastIron Ethernet Switch IP Multicast Configuration Guide
53-1003085-02
Download from Www.Somanuals.com. All Manuals Search And Download.
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
Current Count
Hello interval
Maximum number of multicast cache entries.
Number of multicast cache entries used.
How frequently the device sends IPv6 PIM Sparse hello messages to its IPv6 PIM Sparse
neighbors. This field shows the number of seconds between hello messages. IPv6 PIM
Sparse routers use hello messages to discover one another.
Neighbor timeout
Number of seconds the device waits for a hello message from a neighbor before
determining that the neighbor is no longer present and is not removing cached IPv6 PIM
Sparse forwarding entries for the neighbor. Default is 105 seconds.
Join or Prune interval
How frequently the device sends IPv6 PIM Sparse Join or Prune messages for the
multicast groups it is forwarding. This field shows the number of seconds between Join or
Prune messages.
The device sends Join or Prune messages on behalf of multicast receivers that want to
join or leave an IPv6 PIM Sparse group. When forwarding packets from IPv6 PIM Sparse
sources, the device sends the packets only on the interfaces on which it has received join
requests in Join or Prune messages for the source group.
Inactivity interval
Number of seconds a forwarding entry can remain unused before the router deletes it.
Default is 180 sec.
Hardware Drop
Enabled
Indicates whether hardware drop is enabled or disabled.
To prevent unwanted multicast traffic from being sent to the CPU, PIM Routing and
Passive Multicast Route Insertion (PMRI) can be used together to ensure that multicast
streams are only forwarded out ports with interested receivers and unwanted traffic is
dropped in the hardware on Layer 3 Switches.
Prune Wait Interval
Number of seconds a PIM device waits before stopping traffic to neighbor devices that do
not want the traffic. Range is from zero to three seconds. Default is three seconds.
Bootstrap Msg interval How frequently the BSR configured on the device sends the RP set to the RPs within the
IPv6 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 IPv6 PIM Sparse group
numbers for which it can be an RP.
NOTE
This field contains a value only if an interface on the device is elected to be the BSR.
Otherwise, the field is blank.
FastIron Ethernet Switch IP Multicast Configuration Guide
53-1003085-02
177
Download from Www.Somanuals.com. All Manuals Search And Download.
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. A lower value means more frequent register bursts at RP, while
a higher value means longer join latency for new receivers. Default: 60 seconds.
Register Probe Time
Register Stop Delay
Number of seconds the PIM router waits for a register-stop from an RP before it generates
another NULL register to the PIM RP. Default is 10 seconds.
Register stop message. Default is 10 seconds.
Register Suppress
interval
Number of seconds that it takes the designated router to send Register-encapsulated data
to the RP after receiving a Register-Stop message. Default is 60 seconds.
SSM Enabled
SPT threshold
If yes, source-specific multicast is configured globally on this router.
Number of packets the device sends using the path through the RP before switching to the
SPT path. Default is 1 packet.
SSM Group Range
Route Precedence
Source-specific multicast group range.
The route precedence configured to control the selection of routes based on the four route
types:
•
•
•
•
Non-default route from the mRTM
Default route from the mRTM
Non-default route from the uRTM
Default route from the uRTM
Embedded RP
Enabled
Indicates whether the embedded RP is enabled or disabled.
Displaying IPv6 PIM interface information
You can display IPv6 PIM multicast interface information using the show ipv6 pim interface
command.
device# show ipv6 pim interface ethernet 1/1/7
Flags
: SM - Sparse Mode v2
---------+---------------------------------------------------+----+---+---+---------
+-------+----------------
Interface|Global Address
Multicast| VRF | DR
|Mode|St |TTL|
| Override
| + Designated Router
| Prio | Interval
Port | |Thr|Boundary
|
|
---------+---------------------------------------------------+----+---+---+---------
+-------+----------------
e1/1/1 a141::1
default 1 3000ms
+ Itself
Total Number of Interfaces : 1
SM
Ena
1 None
178
FastIron Ethernet Switch IP Multicast Configuration Guide
53-1003085-02
Download from Www.Somanuals.com. All Manuals Search And Download.
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.
The following table displays the output from the show ip pim interface ethernet command.
TABLE 27 Output from the show ipv6 pim interface ethernet command
Field
Description
Interface
Global Address
Port
Name of the interface.
IP address of the interface.
Port number of the designated router.
PIM mode.
Mode
St
State.
TTL Thr
Time to live threshold.
Multicast boundary, if one exists.
Name of the VRF.
Multicast Boundary
VRF
DR Prio
Designated router priority.
Override interval in milliseconds.
Override Interval
Displaying a list of multicast groups
To display IPv6 PIM group information, enter the show ipv6 pim group command at any CLI level.
device# show ipv6 pim group
Total number of groups: 1
1
Group ff7e:a40:2001:3e8:27:0:1:2
Group member at e3/1: v31
Syntax: show ipv6 pim [ vrf vrf-name ] group
The vrf parameter allows you to display IPv6 PIM group information for the VRF instance identified by
the vrf-name variable.
The following table displays the output from the show ipv6 pim group command.
FastIron Ethernet Switch IP Multicast Configuration Guide
53-1003085-02
179
Download from Www.Somanuals.com. All Manuals Search And Download.
Displaying BSR information
TABLE 28 Output from the show ipv6 pim group command
Field
Description
Total number of Groups
Group
Lists the total number of IPv6 multicast groups the device is forwarding.
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.
Brocade# show ipv6 pim bsr
PIMv2 Bootstrap information for Vrf Instance : default-vrf
------------------------------------------------------------------
This system is the Elected BSR
BSR address: 2006:1001::1. Hash Mask Length 64. Priority 32.
Next bootstrap message in 00:01:00
Configuration:
Candidate loopback 1 (Address 2006:1001::1). Hash Mask Length 64. Priority 32.
Next Candidate-RP-advertisment in 00:00:50
RP: 2006:1001::1
group prefixes:
ff00:: / 8
Candidate-RP-advertisement period: 60
Candidate-RP-advertisement period: 60
Candidate-RP-advertisement period: 60
The following example shows information displayed on a device that is not the BSR. Notice that some
fields shown in the previous example do not appear in the following example.
Brocade# show ipv6 pim bsr
PIMv2 Bootstrap information for Vrf Instance : default-vrf
------------------------------------------------------------
BSR address: 2006:1001::1. Hash Mask Length 64. Priority 32.
This system is not a Candidate-RP.
This system is not a Candidate-RP.
Syntax: show ipv6 pim [ vrf vrf-name ] bsr
The vrf parameter allows you to display IPv6 PIM BSR information for the VRF instance identified by
the vrf-name variable.
The following table displays the output from the show ipv6 pim bsr command.
TABLE 29 Output from the show ipv6 pim bsr command
Field
Description
BSR address
The IPv6 address of the interface configured as the IPv6 PIM Sparse Bootstrap
Router (BSR).
BSR priority
The priority assigned to the interface for use during the BSR election process. During
BSR election, the priorities of the candidate BSRs are compared and the interface
with the highest BSR priority becomes the BSR.
180
FastIron Ethernet Switch IP Multicast Configuration Guide
53-1003085-02
Download from Www.Somanuals.com. All Manuals Search And Download.
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.
Next bootstrap message Indicates how many seconds will pass before the BSR sends its next Bootstrap
in
message.
NOTE
This field appears only if this device is the BSR.
Next Candidate-RP-
advertisement message
in
Indicates how many seconds will pass before the BSR sends its next candidate RP
advertisement message.
NOTE
This field appears only if this device is a candidate BSR.
RP
Indicates the IPv6 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.
Candidate-RP-
Indicates how frequently the BSR sends candidate RP advertisement messages.
advertisement period
NOTE
This field appears only if this device is a candidate BSR.
Displaying candidate RP information
To display candidate RP information, enter the show ipv6 rp-candidate command at any CLI level.
device# show ipv6 pim rp-candidate
Next Candidate-RP-advertisement in 00:00:10
FastIron Ethernet Switch IP Multicast Configuration Guide
53-1003085-02
181
Download from Www.Somanuals.com. All Manuals Search And Download.
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.
Syntax: show ipv6 pim [ vrf vrf-name ] rp-candidate
The vrf parameter allows you to display IPv6 candidate RP information for the VRF instance identified
by the vrf-name variable.
The following table displays the output from the show ipv6 pim rp-candidate command.
TABLE 30 Output from the show ipv6 pim rp-candidate command
Field
Description
Candidate-RP-advertisement Indicates how many seconds will pass before the BSR sends its next RP
in
message.
NOTE
This field appears only if this device is a candidate RP.
RP
Indicates the IPv6 address of the Rendezvous Point (RP).
NOTE
This field appears only if this device is a candidate RP.
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 RP.
Candidate-RP-advertisement Indicates how frequently the BSR sends candidate RP advertisement messages.
period
NOTE
This field appears only if this device is a candidate RP.
Displaying RP-to-group mappings
To display RP-to-group-mappings, enter the show ipv6 pim rp-map command at any CLI level.
Brocade#show ipv6 pim rp-map
Number of group-to-RP mappings: 3
-------------------------------------------------------------------------------
S.No Group address
RP address
182
FastIron Ethernet Switch IP Multicast Configuration Guide
53-1003085-02
Download from Www.Somanuals.com. All Manuals Search And Download.
Displaying RP information for an IPv6 PIM Sparse group
-------------------------------------------------------------------------------
1
2
3
ff07::c:1
ff07::c:2
ff07::c:3
3200:12::32
3200:12::32
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.
TABLE 31 Output from the show ipv6 pim rp-map command
Field
Description
Index
The index number of the table entry in the display.
Group address Indicates the IPv6 PIM Sparse multicast group address using the listed RP.
RP address Indicates the Iv6 address of the Rendezvous Point (RP) for the listed PIM Sparse group.
Displaying RP information for an IPv6 PIM Sparse group
To display RP information for an IPv6 PIM Sparse group, enter the following command at any CLI level.
device# show ipv6 pim rp-hash ff1e::1:2
RP: 2001:3e8:255:255::17, v2
Info source: 2001:3e8:255:255::17, via bootstrap
Syntax: show ipv6 pim [ vrf vrf-name ] rp-hash group-addr
The vrf parameter allows you to display RP information for a PIM Sparse group for the VRF instance
identified by the vrf-name variable.
The group-addr parameter is the address of an IPv6 PIM Sparse IP multicast group.
The following table displays the output from the show ipv6 pim rp-hash group-addr command.
TABLE 32 Output from the show ipv6 pin rp-hash group-addr command
Field
Description
RP
Indicates the IPv6 address of the Rendezvous Point (RP) for the specified IPv6 PIM Sparse group.
Following the IPv6 address is the port or virtual interface through which this device learned the identity
of the RP.
Info source Indicates the IPv6 address on which the RP information was received. Following the IPv6 address is
the method through which this device learned the identity of the RP.
Displaying the RP set list
To display the RP set list, enter the show ipv6 pim rp-set command at any CLI level.
device# show ipv6 pim rp-set
Static RP
FastIron Ethernet Switch IP Multicast Configuration Guide
53-1003085-02
183
Download from Www.Somanuals.com. All Manuals Search And Download.
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.
TABLE 33 Output from the show ipv6 pim rp-set command
Field
Description
Number of group prefixes The number of IPv6 PIM Sparse group prefixes for which the RP is responsible.
Group prefix
Indicates the multicast groups for which the RP listed by the previous field is a
candidate RP.
RPs expected or
received
Indicates how many RPs were expected and received in the latest Bootstrap
message.
RP num
Indicates the RP number. If there are multiple RPs in the IPv6 PIM Sparse domain, a
line of information for each of them is listed, and they are numbered in ascending
numerical order.
priority
age
The RP priority of the candidate RP. During the election process, the candidate RP
with the highest priority is elected as the RP.
The age (in seconds) of this RP-set.
NOTE
If this device is not a BSR, this field contains zero. Only the BSR ages the RP-set.
Displaying multicast neighbor information
To display information about IPv6 PIM neighbors, enter the show ipv6 pim neighbor command at
any CLI level.
FBrocade#show ipv6 pim neighbor
--------+--------+-----------------------------+--------+---+---------+---------
+-----+---------------+--------+----+
PPort
|PhyPort |Neighbor
|Holdtime|T |PropDelay|Override |
Age |UpTime
|VRF
|Prio
|
|
|
|sec |Bit|msec |msec |
sec |
|
--------+--------+-----------------------------+--------+---+---------+---------
+-----+---------------+--------+----+
vv503
25
e2/1/11 fe80::204:ff:fe05:6
105
1
500
3000
06:50:10
default 1
+ 2006:503::1001
vv503
12
e2/1/11 fe80::768e:f8ff:fe2c:cb80
06:50:10
105
1
500
3000
default 1
+ 2006:503::1004
TTotal Number of Neighbors : 2
Syntax: show ipv6 pim [ vrf vrf-name ] neighbor
184
FastIron Ethernet Switch IP Multicast Configuration Guide
53-1003085-02
Download from Www.Somanuals.com. All Manuals Search And Download.
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.
The physical interface through which the device is connected to the neighbor.
The IPv6 interface of the IPv6 PIM neighbor interface.
Phyport
Neighbor
Holdtime sec
Indicates how many seconds the neighbor wants this device to hold the entry for this neighbor in
memory. The neighbor sends the Hold Time in its hello packets.
•
•
If the device receives a new hello packet before the Hold Time received in the previous
packet expires, the device updates its table entry for the neighbor.
If the device does not receive a new hello packet from the neighbor before the Hold time
expires, the device assumes the neighbor is no longer available and removes the entry for
the neighbor.
T Bit
Specifies the ability of the sending router to disable joins suppression.
PropDelay msec Expected propagation delay over the local link.
Override msec
Age sec
Default delay interval over which to randomize, when scheduling a delayed join message.
The number of seconds since the device received the last hello message from the neighbor.
UpTime
The number of seconds the PIM neighbor has been up. This timer starts when the device
receives the first hello messages from the neighbor.
VRF
Prio
The DR priority that is used in the DR election process. This can be a configured value or the
default value of 1.
Displaying the IPv6 PIM multicast cache
To display the IPv6 PIM multicast cache, enter the show ipv6 pim mcache command at any CLI level.
NOTE
Brocade NetIron CES and NetIron CER devices display incorrect hardware programmed entries. The
information displayed for the forwarding port should be disregarded.
device#show ipv6 pim mcache
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
FastIron Ethernet Switch IP Multicast Configuration Guide
53-1003085-02
185
Download from Www.Somanuals.com. All Manuals Search And Download.
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 00:27:26 (SM)
upstream neighbor fe80::204:ff:fe05:6 (2006:503::1001)
Flags (0x002604a2) SM RPT LRCV TAG
slow ports: ethe 3/1/1
AgeSltMsk: 0, L2 FID: 8192, DIT: NotReq, profile: none
Forwarding_oif: 1, Immediate_oif: 1, Blocked_oif: 0
L3 (SW) 1:
e3/1/1(VL170), 1d 00:27:26/0, Flags: MJ
(2006:170::1010, ff34::500) in v170 (tag e3/1/1), Uptime 00:37:51, Rate 0 (SM)
Source is directly connected. RP 2006:1001::1
Flags (0x20429ce1) SM SPT REG L2REG LSRC HW FAST TAG
fast ports: ethe 2/1/11
2
AgeSltMsk: 1, L2 FID: 4188, DIT: 1 , AvgRate: 0, profile: none
Forwarding_oif: 1, Immediate_oif: 1, Blocked_oif: 0
L3 (HW) 1:
TR(e2/1/11,e2/1/11)(VL503), 00:37:26/183, Flags: IM
Src-Vlan: 170
Syntax: show ipv6 pim mcache [ multicast cache entries source/group address | multicast
cache ipv6-group-address ]
Syntax: show ipv6 pim [ vrf vrf-name ] mcache [ source-address | group-address | counts |
dense | dit-idx dit-idx | g_entries | receiver | sg_entries | sparse | ssm ]
The vrf option allows you to display the IPv6 PIM multicast cache for the VRF instance identified by
the vrf-name variable.
The source-address parameter selects the multicast cache source address.
The group-address parameter selects the multicast cache group address.
The counts keyword indicates the count of entries.
The dense keyword displays only the PIM Dense Mode entries.
The dit-idx variable allows you to display all entries that match a specified dit.
The g_entries keyword displays only the (*, G) entries.
The receiver keyword allows you to display all entries that egress a specified interface.
The sg_entries keyword displays only the (S, G) entries.
The sparse keyword displays only the PIM Sparse Mode entries.
The ssm keyword displays only the SSM entries.
The following table describes the output parameters of the show ipv6 pim vrf mcache command.
TABLE 35 Output parameters of the show ipv6 pim mcache command
Field
Total entries in mcache Shows the total number of PIM mcache entries.
upstream neighbor Shows the upstream neighbor for the Source/RP based on the type of entry.
Description
For (*,G) it shows the upstream neighbor towards the RP. For (S,G) entries it
shows the upstream neighbor towards the source.
186
FastIron Ethernet Switch IP Multicast Configuration Guide
53-1003085-02
Download from Www.Somanuals.com. All Manuals Search And Download.
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
L2 FID
Shows the slot number on which MP expects ingress traffic.
Shows the hardware resource allocated for the traffic switched to receivers in the
ingress VLAN.
DIT
Shows the hardware resource allocated for routed receivers.
Shows the average data traffic rate for the mcache entry
Shows the profile ID associated with the stream.
AvgRate
profile
Forwarding_oif
immediate_oifs
blocked_oifs
L3 (SW) 1
L3 (HW) 1
Src-Vlan
Shows the number of outgoing interfaces of the mcache entry.
Shows the local immediate outgoing interface of the mcache entry.
Shows the PIM Sparse mode blocked outgoing interfaces.
Shows whether the traffic is switched or routed out of the interface.
The forwarding entries by using hardware.
VLAN associated with the ingress interface.
Displaying IPv6 PIM RPF
The show ipv6 pim rpf command displays what PIM sees as the reverse path to the source. While
there may be multiple routes back to the source, the one displayed by the show ipv6 pim rpf command
is the one that PIM thinks is best.
device# show ipv6 pim rpf 2008:165::1010
upstream nbr 2006:503::1001 on v503
Syntax: show ipv6 pim [ vrf vrf-name ] rpf ip-address
The vrf parameter allows you to display what PIM sees as the reverse path to the source for a VRF
instance specified by the vrf-name variable.
The ip-address variable specifies the source address for RPF check.
Displaying IPv6 PIM counters
You can display the number of default-vlan-id changes that have occurred since the applicable VRF
was created and how many times a tagged port was placed in a VLAN since the applicable VRF was
created, as shown in the following example.
FastIron Ethernet Switch IP Multicast Configuration Guide
53-1003085-02
187
Download from Www.Somanuals.com. All Manuals Search And Download.
Displaying the IPv6 PIM resources
Brocade#show ipv pim vrf eng counter
Event Callback:
DFTVlanChange : 0
LP to MP IPCs:
VlanPort : 0
SM_REGISTER : 8315
MCAST_CREATE :
WRONG_IF :
MCAST_FIRST_DATA : 3
SET KAT INFINITY : 3
0
0
S_G_AGEOUT :
3
ABOVE_THRESHOLD: 0
SET KAT :
MP to LP IPCs:
INIT : 25
3
INSERT_VPORT : 30
DELETE_VIF :
DEL_ENTRY :
DELETE_SOURCE : 0
MOVE_TNNL_PORT : 0
FDB_VIDX_CHANGE: 0
DELETE_VPORT : 186
162
16
MOVE_VPORT :
0
INSERT_SOURCE : 0
RESET_SRC_LIST : 0
FLAG_CHANGE :
6
OIF_FLAG_CHANGE :0
Error Counters:
PIM_PKT_DRP : 0
MCGRP_PKT_DRP: 0
RPSET_MAXED : 0
PIM_PKT_DRP(Glb) : 0
MCGRP_PKT_DRP(Gl): 0
Syntax: show ipv6 pim [ vrf vrf-name ] counter
The vrf parameter allows you to display IPv6 PIM counters for the VRF instance identified by the vrf-
name variable.
The following table displays the output from the show ipv6 vrf eng counter command.
TABLE 36 Output from the show ipv6 pim vrf eng counter command
Field
Description
DFTVlanChange The number of default-vlan-id changes that have occurred since the applicable VRF was
created.
VlanPort
The number of times that a tagged port was placed in a VLAN since the applicable VRF was
created.
Displaying the IPv6 PIM resources
To display the hardware resource information, such as hardware allocation, availability, and limit for
software data structure, enter the show ipv6 pim resource command.
Brocade#show ipv6 pim vrf white res
Global PIM Parameters :-
GLOBAL Ipv6 MULTICAST CLASS Size:23573 bytes
GLOBAL Ipv6 PIM CLASS Size:2162 bytes
MULTICAST IPV6 CLASS Num alloc:2, System max:17, Size:1346 bytes
PIM IPV6 CLASS Num alloc:2, System max:17, Size:50485
Vrf Instance : white
--------------------------------------
alloc in-use avail get-fail limit get-mem size init
NBR list
64
256
64
2
1
0
0
0
0
0
62
255
64
0
0
0
0
0
512
1536
64
73
96
49 256
42 64
47 512
64
RP set list
Static RP
12824
0
0
LIF Entry
512
64
512
64
512
64
Anycast RP
timer
0 190
64
64
32
64
32
64
32
0 14848
65
0
64
34
prune
0
7424
pimsm J/P elem
Timer Data
mcache SLIB Sync
mcache
1024
512
1120
896
197
1000
1024
0 1024
0 48960
0 14848
0 64960
0 12992
0 45704
0 116000
0 59392
640448
1409
9502
29 128
2
510
28
64
34 280
2 1118
2
0
2
894
197
998
5570 1144
56
64 197
66 500
81 256
graft if no mcache
HW replic vlan
HW replic port
0
170179
170179
2 1022
188
FastIron Ethernet Switch IP Multicast Configuration Guide
53-1003085-02
Download from Www.Somanuals.com. All Manuals Search And Download.
IPv6 Multicast Protocols
pim/dvm intf. group
64
0
0
64
0 14848
0 14848
0 237568
0
6700
24
46
64
64
pim/dvm global group 512
repl entry(Global) 1024
MLD Resources(All Vrfs):
512
2 1022
40644
49 1024
groups
phy-ports
exist-phy-port
group-query
1024
2048
1792
56
0 1024
0 2048
0 1792
0
0
4096
4096
7100 328 256
7600 148 256
196484
0
0 12992
0 12992
62
84
56
56
0
56
Hardware-related Resources:
Total (S,G) entries 2
Total SW FWD entries 0
Total sw w/Tag MVID entries 0
Total sw w/Tag invalid MVID entries 0
Total HW FWD entries 2
Total hw w/Tag MVID entries 2
Total hw w/Tag invalid MVID entries 0
Brocade#
Syntax: show ipv6 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 ipv6 pim resource command.
TABLE 37 Output from the show ipv6 pim resource command
Field
Description
Num alloc
Number of allocated PIM resources.
System max Maximum number of VRF resources.
Size
Internal size.
alloc
in-use
avail
get-fail
limit
Number of nodes of that data that are currently allocated in memory.
Number of allocated nodes in use.
Number of allocated nodes are not in use.
Number of allocated notes that failed.
Maximum number of nodes that can be allocated for a data structure. This may or may not be
configurable, depending on the data structure
get-mem
size
Current memory allocation.
Unit size.
init
Initial number.
To display usage and fail-count information for SG entries on each VRF, use the show ipv6 pim all-vrf
hw-resource command.
device# show ipv6 pim all-vrf hw-resource
VRF In-Use
Fail
default-vrf
blue
3072
3072
8
0
-------------------------------
Total usage
6144
FastIron Ethernet Switch IP Multicast Configuration Guide
53-1003085-02
189
Download from Www.Somanuals.com. All Manuals Search And Download.
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
VRF
Description
Name of the VRF.
Usage
Fail
Number of allocated SG entries in this VRF.
Number of failures while allocating SG entries in this VRF (due to system-max
limit).
Total usage
Total number of SG entries in the system (All-VRFs).
System-max limit for SG entries Configured system limit using the pim6-hw-mcache command.
Displaying PIM traffic statistics
To display IPv6 PIM traffic statistics, enter the show ipv6 pim traffic command at any CLI level.
device# show ipv6 pim traffic
Port
HELLO
JOIN-PRUNE ASSERT
REGISTER REGISTER BOOTSTRAP CAND. RP Err
GRAFT(DM) STOP(SM) MSGS (SM) ADV. (SM)
-------+---------+-----------+---------+---------+---------+---------+---------+---
Rx
Rx
Rx
Rx
Rx
Rx
Rx
Rx
------+---------+-----------+---------+---------+---------+---------+---------+---
v170
v501
v503
Port
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
3302
HELLO
2524
JOIN-PRUNE ASSERT
REGISTER REGISTER BOOTSTRAP CAND. RP Err
GRAFT(DM) STOP(SM) MSGS (SM) ADV. (SM)
-------+---------+-----------+---------+---------+---------+---------+---------+---
Tx
Tx
Tx
Tx
Tx
Tx
Tx
------+---------+-----------+---------+---------+---------+---------+---------+---
v170
v501
v503
3576
1456
1456
0
0
0
0
0
0
0
0
0
0
0
0
2
0
0
0
0
1314
Syntax: show ipv6 pim [ vrf vrf-name ] traffic
The vrf parameter allows you to display IPv6 traffic statistics for the VRF instance identified by the vrf-
name variable.
The following table displays the output from the show ipv6 pim traffic command.
TABLE 39 Output from the show ipv6 pim traffic command
Field
Port
Description
The port or virtual interface on which the IPv6 PIM interface is configured.
The number of IPv6 PIM Hello messages sent or received on the interface.
Hello
190
FastIron Ethernet Switch IP Multicast Configuration Guide
53-1003085-02
Download from Www.Somanuals.com. All Manuals Search And Download.
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.
Regiser Stop (SM) The number of Register Stop messages sent or received on the interface.
Bootstrap Msgs (SM) The number of bootstrap messages sent or received on the interface.
Cand. RP Adv. (SM) The total number of Candidate-RP-Advertiment messages sent or received on the
interface.
Err
The total number of MLD messages discarded, including a separate counter for those that
failed the checksum comparison.
Clearing the IPv6 PIM forwarding cache
You can clear the IPv6 PIM forwarding cache using the clear ipv6 pim cache command.
device# clear ipv6 pim cache
Syntax: clear ipv6 pim [ vrf vrf-name ] cache
Use the vrf parameter to clear the IPv6 PIM forwarding cache for a VRF instance specified by the vrf-
name variable.
Clearing the IPv6 PIM message counters
You can clear the IPv6 PIM message counters using the clear ipv6 pim counters command.
device# clear ipv6 pim counters
Syntax: clear ipv6 pim [ vrf vrf-name ] counters
Use the vrf parameter to clear the IPv6 PIM message counters for a VRF instance specified by the vrf-
name variable.
Updating PIM Sparse forwarding entries witha new RP configuration
If you make changes to your static RP configuration, the entries in the IPv6 PIM Sparse multicast
forwarding table continue to use the old RP configuration until they are aged out.
FastIron Ethernet Switch IP Multicast Configuration Guide
53-1003085-02
191
Download from Www.Somanuals.com. All Manuals Search And Download.
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.
device(config)# clear ipv6 pim rp-map
Syntax: clear ipv6 pim [ vrf vrf-name ] rp-map
Use the vrf parameter to clear the IPv6 PIM Sparse static multicast forwarding table for a VRF
instance specified by the vrf-name variable.
Clearing the IPv6 PIM traffic
To clear counters on IPv6 PIM traffic, enter the clear ipv6 pim traffic command.
device# clear ipv6 pim traffic
Syntax: clear ipv6 pim [ vrf vrf-name ] traffic
Use the vrf par meter to clear counters on IPv6 PIM traffic for a VRF instance specified by the vrf-
name variable.
Defining the maximum number of IPv6 PIM cache entries
You can use the max-mcache 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
the maximum for the default VRF, enter the max-mcache command.
device(config)# ipv6 router pim
device(config-ipv6-pim-router)# max-mcache 999
Syntax: [no] max-mcache num
The num variable specifies the maximum number of IPv6 multicast cache entries for PIM in the default
VRF. If not defined by this command, the maximum value is determined by the system max command
parameter, pim6-hw-mcache , or by available system resources.
To define the maximum number of IPv6 PIM Cache entries for a specified VRF, use the following
command.
device(config)# ipv6 router pim vrf blue
device(config-ipv6-pim-router-vrf-blue)# max-mcache 999
Syntax: [no] ipv6 router pim [ vrf vrf-name ]
The vrf parameter specified with the ipv6 router pim command allows you to configure the max-
mcache command for a virtual routing instance (VRF) specified by the variable vrf-name .
The vrf parameter specified with the router pim command allows you to configure the max-mcache
command for a virtual routing instance (VRF) specified by the variable vrf-name .
The num variable specifies the maximum number of multicast cache entries for PIM in the specified
VRF. If not defined by this command, the maximum value is determined by the system max command
parameter, pim6-hw-mcache , or by available system resources.
There is a system-max command parameter change with the following new runtime command:
Syntax: system-max pim6-hw-mcache
192
FastIron Ethernet Switch IP Multicast Configuration Guide
53-1003085-02
Download from Www.Somanuals.com. All Manuals Search And Download.
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. Configure a VRF.
Device(config)# vrf vpn1
2. Configure the VRF address family for IPv6 and enter IPv6 address family configuration mode.
Device (config-vrf-vpn1)#address-family ipv6
3. Configure the destination IPv6 address.
Device (config-vrf-vpn1-ipv6)#ipv6 mroute 2001:0DB8:0:1::1/120 5100::192:1:1:1
Configuring the route precedence by specifying the route types
Precedence tables specify how routes are selected for multicast
PIM must be enabled at the global level.
Configure the none keyword to fill up the precedence table and ignore certain types of routes.
1. Enable PIM at the global level.
Device(config)# ipv6 router pim
2. Configure a precedence table.
Device(config-ipv6-pim-router)# route-precedence mc-non-default uc-non-default mc-
default uc-default
Configures a precedence table for multicast route selection that first looks for 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.
3. Configure the none keyword to fill up the precedence table in order to ignore certain types of route.
Device(config-ipv6-pim-router)# route-precedence mc-non-default mc-default uc-non-
default none
Configures a precedence table for multicast route selection that ignores the default route from
uRTM .
4. Return to global level.
Device(config-ipv6-pim-router)# exit
5. Enable PIM for a VRF.
Device(config)# ipv6 router pim vrf blue
6. Configure a precedence table for the VRF.
Device (config-ipv6-pim-router-vrf-blue)# route-precedence mc-non-default uc-non-
default mc-default uc-default
Configures a precedence table that 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 for the specified VRF,.
7. Configure the none keyword to fill up the precedence table.
Device(config-ipv6-pim-router-vrf-blue)# route-precedence mc-non-default mc-
default uc-non-default none
Configures a precedence table that specifies the unicast default route for multicast for the specified
VRF.
FastIron Ethernet Switch IP Multicast Configuration Guide
53-1003085-02
193
Download from Www.Somanuals.com. All Manuals Search And Download.
PIM Anycast RP
The following examples show how to configure the route precedence and
display the route-precedence setting.
Device(config-ipv6-pim-router)#route-precedence mc-non-default mc-default uc-non-
default uc-default
Device(config-ipv6-pim-router)#show ipv6 pim sparse
Global PIM Sparse Mode Settings
Maximum Mcache
: 12992
: 30
Current Count
: 2
Hello interval
Neighbor timeout
: 105
: 180
: 3
Join/Prune interval
Hardware Drop Enabled
Bootstrap Msg interval
Register Suppress Time
Register Stop Delay
SSM Enabled
: 60
Inactivity interval
Prune Wait Interval
Candidate-RP Msg interval
Register Probe Time
Register Suppress interval
SPT Threshold
: Yes
: 60
: 60
: 10
: 60
: 1
: 60
: 10
: No
Route Precedence
: mc-non-default mc-default uc-non-default uc-default
: Yes
Embedded RP Enabled
Device(config-ipv6-pim-router)#route-precedence admin-distance
Device(config-ipv6-pim-router)#show ipv6 pim sparse
Global PIM Sparse Mode Settings
Maximum Mcache
: 12992
: 30
Current Count
: 2
Hello interval
Neighbor timeout
: 105
: 180
: 3
Join/Prune interval
Hardware Drop Enabled
Bootstrap Msg interval
Register Suppress Time
Register Stop Delay
SSM Enabled
: 60
Inactivity interval
Prune Wait Interval
Candidate-RP Msg interval
Register Probe Time
Register Suppress interval
SPT Threshold
: Yes
: 60
: 60
: 10
: 60
: 1
: 60
: 10
: No
Route Precedence
Embedded RP Enabled
: admin-distance
: Yes
Device(config-ipv6-pim-router)
PIM Anycast RP
PIM Anycast RP is a method of providing load balancing and fast convergence to PIM RPs in an IPv6
multicast domain. The RP address of the Anycast RP is a shared address used among multiple PIM
routers, known as PIM RP. The PIM RP routers create an Anycast RP set. Each router in the Anycast
RP set is configured using two IPv6 addresses: a shared RP address in their loopback address and a
separate, unique IPv6 address. The loopback address must be reachable by all PIM routers in the
multicast domain. The separate, unique IP address is configured to establish static peering with other
PIM routers and communication with the peers.
When the source is activated in a PIM Anycast RP domain, the PIM First Hop (FH) will register the
source to the closet PIM RP. The PIM RP follows the same MSDP Anycast RP operation by
decapsulating the packet and creating the (s,g) state. If there are external peers in the Anycast RP set,
the router will re-encapsulate the packet with the local peering address as the source address of the
encapsulation. The router will unicast the packet to all Anycast RP peers. The re-encapsulation of the
data register packet to Anycast RP peers ensures source state distribution to all RPs in a multicast
domain.
Configuring PIM Anycast RP
A new PIM CLI is introduced for PIM Anycast RP under the router pim submode. The PIM CLI
specifies mapping of the RP and the Anycast RP peers.
To configure PIM Anycast RP, enter the following commands.
device(config)# ipv6 router pim
194
FastIron Ethernet Switch IP Multicast Configuration Guide
53-1003085-02
Download from Www.Somanuals.com. All Manuals Search And Download.
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.
device(config)# ipv6 router pim vrf blue
device(config-ipv6-pim-router-vrf-blue)# rp-address 1001::1
device(config-ipv6-pim-router-vrf-blue)# anycast-rp 1001::1 my-anycast-rp-set-acl
Syntax: [no] anycast-rp rp-address my-anycast-rp-set-acl
The rp address parameter specifies a shared RP address used among multiple PIM routers.
The my-anycast-rp-set-acl parameter specifies a host-based simple ACL used to specify the address of
the Anycast RP set, including a local address.
The following example is a configuration of PIM Anycast RP 1001:1.The example avoids using the
loopback 1 interface when configuring PIM Anycast RP because the loopback 1 address could be used
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. Refer to the figure
“Example of a PIM Anycast RP network” as described in the configuration of PIM Anycast RP 1001:1.
device(config)# interface loopback 2
device(config-lbif-2)# ipv6 address 1001::1/96
device(config-lbif-2)# ipv6 pim-sparse
device(config-lbif-2)# interface loopback 3
device(config-lbif-3)# ipv6 address 1:1:1::1/96
device(config-lbif-3)# ipv6 pim-sparse
device(config-lbif-3)# ipv6 router pim
device(config-ipv6-pim-router)# rp-address 1001::1
device(config-ipv6-pim-router)# anycast-rp 1001::1 my-anycast-rp-set
device(config-ipv6-pim-router)# ipv6 access-list my-anycast-rp-set
device(config-std-nacl)# permit ipv6 host 1:1:1::1 any
device(config-std-nacl)# permit ipv6 host 2:2:2::2 any
device(config-std-nacl)# permit ipv6 host 3:3:3::3 any
The RP shared address 1001:1 is used in the PIM domain. IPv6 addresses 1:1:1::1, 2:2:2::2, and
3:3:3::3 are listed in the ACL that forms the self-inclusive Anycast RP set. Multiple Anycast RP
instances can be configured on a system; each peer with the same or different Anycast RP set.
NOTE
The PIM Anycast CLI applies to only PIM routers running RP. All deny statements in the anycast_rp_set
ACL are ignored.
The example shown in the figure “Example of a PIM Anycast RP network”is a PIM Anycast-enabled
network with three RPs and one PIM-FH router connecting to its active source and local receiver.
Loopback 2 in RP1, RP2, and RP3 each have the same IP addresses 1001:1. Loopback 3 in RP1, RP2,
and RP3 each have separate IP address configured to communicate with their peers in the Anycast RP
set.
FIGURE 11 Example of a PIM Anycast RP network
FastIron Ethernet Switch IP Multicast Configuration Guide
53-1003085-02
195
Download from Www.Somanuals.com. All Manuals Search And Download.
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.
device(config)# show ipv6 pim anycast-rp
Number of Anycast RP: 1
Anycast RP: 1001::1
ACL ID: 200
ACL Name: my-anycast-rp-set
ACL Filter: SET
Peer List:
1:1:1::1
2:2:2::2
3:3:3::3
Syntax: show ipv6 pim [ vrf vrf-name ] anycast-rp
The vrf parameter allows you to display information for an IPv6 Anycast RP interface for the VRF
instance identified by the vrf-name variable.
The following table describes the parameters of the show ipv6 pim anycast-rp command.
TABLE 40 Output from the show ipv6 pim anycast-rp command
Field
Description
Number of Anycast RP
Anycast RP
ACL ID
Specifies the number of Anycast RP sets in the multicast domain.
Specifies a shared RP address used among multiple PIM routers.
Specifies the ACL ID assigned.
ACL Name
ACL Filter
Specifies the name of the Anycast RP set.
Specifies the ACL filter state SET or UNSET.
Specifies host addresses that are permitted in the Anycast RP set.
Peer List
Multicast Listener Discovery and source-specific multicast protocols
Multicast Listener Discovery Version 2 (MLDv2) protocol is supported. IPv6 routers use the MLDv2
protocol to discover multicast listeners, or nodes that wish to receive multicast packets on directly
attached links. MLDv2 supports source filtering, the ability of a node to send reports on traffic that is
from a specific address source or from all multicast addresses except the specified address sources.
The information is then provided to the source-specific multicast (SSM) routing protocols such as PIM-
SSM.
The IPv6 router stores a list of multicast addresses for each attached link. For each multicast address,
the IPv6 router stores a filter mode and a source list. The filter mode is set to INCLUDE if all nodes in
the source list for a multicast address are in the INCLUDE state. If the filter mode is INCLUDE, then
only traffic from the addresses in the source list is allowed. The filter mode is set to EXCLUDE if at
least one of the nodes in the source list is in an EXCLUDE state. If the filter mode is EXCLUDE, traffic
from nodes in the source list is denied and traffic from other sources is allowed.
196
FastIron Ethernet Switch IP Multicast Configuration Guide
53-1003085-02
Download from Www.Somanuals.com. All Manuals Search And Download.
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.
Address specific and source specific query - The querier sends this query to determine if specified
sources of a specific multicast address have any listeners.
In response to these queries, multicast listeners send the following reports:
•
•
•
Current state - This report specifies the source list for a multicast address and whether the filter
mode for that source list is INCLUDE or EXCLUDE.
Filter-mode change - This report specifies if there has been a change to the filter mode for the
source list and provides a new source list.
Source list change - This report specifies the changes to the source list.
MLDv1 is compatible with IGMPv2 and MLDv2 is compatible with IGMPv3.
Enabling MLDv2
The default MLD version when PIM Sparse Mode (PIM-SM) is enabled on an interface is MLDv1. You
must configure the ipv6 mld version 2 command to enable MLDv2.
To enable MLDv2, enter the following command at the interface level.
device(config)# ipv6 router pim
device(config-if-e10000-1/1)# ipv6 mld version 2
Syntax: [no] ipv6 mld version 2
Configuring MLD parameters for default and non-default VRFs
MLD allows you to configure the following parameters on default and non-default VRFs:
•
•
•
•
•
•
•
•
Setting the group membership time
You can set the group membership time for the default VRF or for a specified VRF. 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 through 26,000 seconds and the default value is 260 seconds.
To define an MLD group membership time of 2000 seconds, enter the following command.
device(config)# ipv6 mld group-membership-time 2000
Syntax: [no] ipv6 mld group-membership-time 5-26000
FastIron Ethernet Switch IP Multicast Configuration Guide
53-1003085-02
197
Download from Www.Somanuals.com. All Manuals Search And Download.
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 .
Defining the maximum number of MLD group addresses
You can use the following run-time command to set the maximum number of MLD addresses for the
default VRF or for a specified VRF. To define this maximum for the default VRF, enter the following
command.
device(config)# ipv6 mld max-group-address 1000
Syntax: [no] ipv6 mld max-group-address num
The num variable specifies the maximum number of MLD group addresses you want to make
available for the default VRF. If not defined by this command, the maximum value is determined by
available system resources.
To define this maximum for a specified VRF, enter the following commands.
device(config)# ipv6 router pim vrf blue
device(config-vrf-blue)# address-family ipv6
device(config-vrf-blue-ipv6)# ipv6 mld max-group-address 1000
Syntax: [no] vrf vrf-name
Syntax:[no] address-family ipv6
Syntax: [no] ipv6 mld max-group-address num
The vrf parameter specifies the virtual routing instance (VRF) specified by the variable vrf-name .
Setting the maximum response time
You can define the maximum amount of time a multicast listener has to respond to queries by entering
a command such as the following.
device(config)# ipv6 mld max-response-time 5
Syntax: [no] ipv6 mld max-response-time seconds
The seconds variable specifies the MLD maximum response time in seconds. You can specify from 1
through 25 seconds. The default is 10 seconds.
To define the maximum amount of time a multicast listener has to respond to queries for a specified
VRF, enter the following commands.
device(config)# ipv6 router pim vrf blue
device(config-ipv6-pim-router-vrf-blue)# ipv6 mld max-response-time 5
Syntax: [no] ipv6 router pim [ vrfvrf-name ]
The vrf parameter specifies the virtual routing instance (VRF) specified by the variable vrf-name .
198
FastIron Ethernet Switch IP Multicast Configuration Guide
53-1003085-02
Download from Www.Somanuals.com. All Manuals Search And Download.
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.
To define the frequency at which MLD query messages are sent for a specified VRF, enter the following
commands.
device(config)# ipv6 router pim vrf blue
device(config-ipv6-pim-router-vrf-blue)# ipv6 mld query-interval 50
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 last listener query interval
The Last Listener Query Interval is the Maximum Response Delay inserted into Multicast-Address-
Specific Queries sent in response to Done messages, and is also the amount of time between
Multicast- Address-Specific Query messages. When the device receives an MLDv1 leave message or
an MLDv2 state change report, it sends out a query and expects a response within the time specified by
this value. Using a lower value allows members to leave groups more quickly. You can set the last
listener query interval by entering a command such as the following.
device(config)# ipv6 mld llqi 5
Syntax: [no] ipv6 mld llqi seconds
The seconds variable sets the last listener query interval in seconds. You can specify from 1 through 25
seconds. The default is 1.
To set the last listener query interval for a specified VRF, enter the following commands.
device(config)# ipv6 router pim vrf blue
device(config-ipv6-pim-router-vrf-blue)# ipv6 mld llqi 5
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 robustness
You can specify the number of times that the switch sends each MLD message from this interface. Use
a higher value to ensure high reliability from MLD. You can set the robustness by entering a command
such as the following.
device(config)# ipv6 mld robustness 3
Syntax: ipv6 mld robustness seconds
The seconds variable sets the MLD robustness in seconds. You can specify from 2 through 7 seconds.
The default is 2 seconds.
FastIron Ethernet Switch IP Multicast Configuration Guide
53-1003085-02
199
Download from Www.Somanuals.com. All Manuals Search And Download.
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.
device(config)# ipv6 mld version 1
Syntax: ipv6 mld version version-number
The version-number variable sets the MLD version. You can specify 1 or 2 for the MLD version.The
default version is 2.
To set the global MLD version for a specified VRF, enter the following commands.
device(config)# ipv6 router pim vrf blue
device(config-ipv6-pim-router-vrf-blue)# ipv6 mld version 1
Syntax: [no] ipv6 router pim [ vrf vrf-name ]
The vrf parameter specifies the virtual routing instance (VRF) specified by the variable vrf-name .
Configuring MLD parameters at the interface level
The following MLD parameters can be configured at the interface level:
•
•
•
•
Specifying a port version
To set the MLD version on a virtual Ethernet interface, enter the following commands as shown
in the example.
device(config)# interface ve 10
device(config-vif-10)# ipv6 mld port-version 2
Syntax: ipv6 mld port-version version-number
Enter 1 or 2 for version-number . Be sure to enter 2 if you want to use source filtering.
Specifying a static group
A multicast group is usually learned when an MLDv1 report is received. You can configure one or
more static groups without having to receive an MLDv1 report.
200
FastIron Ethernet Switch IP Multicast Configuration Guide
53-1003085-02
Download from Www.Somanuals.com. All Manuals Search And Download.
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 mld static-group ff0d::1 count 2 ethernet 1/5
Or this command:
Device(config)# interface ve 10
Device(config-vif-10)# ipv6 mld static-group ff0d::1 to ff0d::2 ethernet 1/5
Syntax: ipv6 mld static-group multicast-group-address [ count count-number | to multicast-group-
address ] [ ethernet port-number [ ethernet port-number | to port-number ] * ]
Enter the IPv6 multicast group address for the multicast-group-address.
The count-number range is 2-256.
Enter the number of the port that will be included in this static group for the ethernet port-number
parameter. The asterisk (*) in the syntax means that you can enter as many port numbers as you want
to include in the static group. For a virtual routing interface (ve), specify the physical Ethernet ports on
which to add the group address.
Enabling MLD tracking on an interface
When MLD tracking is enabled, a Layer 3 switch tracks all clients that send membership reports. When
a Leave message is received from the last client, the device immediately stops forwarding to the
physical port (without waiting 3 seconds to confirm that no other clients still want the traffic). To enable
MLD tracking on a virtual interface, enter the following commands.
device(config)# interface ve 10
device(config-vif-10)# ipv6 mld tracking
Syntax: ipv6 mld tracking
Setting the version on an interface
You can use this command to set the MLD version (1 or 2) on an interface. You can select the version
of MLD by entering a command such as the following.
device(config)# interface ve 10
device(config-vif-10)# ipv6 mld version 2
Syntax: ipv6 mld version version-number
The version-number variable sets the MLD version on an interface. You can specify 1 or 2 for the MLD
version.The default version is 2.
Displaying MLD information
The sections below present the show commands for MLD.
FastIron Ethernet Switch IP Multicast Configuration Guide
53-1003085-02
201
Download from Www.Somanuals.com. All Manuals Search And Download.
Displaying MLD group information
Displaying MLD group information
To display the list of multicast groups, enter a command such as the following.
device #show ipv6 mld group
Total 2 groups
-------------------------------------------------------------------------------------
-
Idx Group Address
Srcs
Port
Intf
GrpCmpV Mode
Timer
----+----------------------------------------+------+------+-------+-------+-----
+----
1 ff05::4422
e3/1/1 v170
Ver1 exclude
221
0
1
2 ff3f::300
e3/1/1 v170
Ver2 include
0
Total number of groups 2
Syntax: show ipv6 mld [ vrf vrf-name ] group
The vrf parameter allows you to display the list of IPv6 MLD groups for the VRF instance identified by
the vrf-name variable.
The following table displays the output from the show ipv6 mld group command.
TABLE 41 Output from the show ipv6 mld group command
Field
Description
IDX
Index for the MLD group.
Group Address
IPv6 address of the multicast group.
Port
The physical port to which the group belongs.
The routing interface to which the port belongs.
The version of the MLD group report message.
Indicates if the filter mode of the multicast group is in INCLUDE or EXCLUDE.
The number of seconds the interface can remain in its current mode.
The total number of MLD groups.
Intf
GrpCmpV
Mode
Timer
Total number of groups
Displaying MLD definitions for an interface
To display the MLD parameters on an interface, including the various timers, the current querying
router, and whether or not MLD is enabled, enter the following command.
Brocade#show ipv6 mld interface
---------+------+---------+---------------------------------------+--
Intf/Port|Groups| Version |
|Oper Cfg|
Querier
| Timer |V1Rtr| Tracking
|
|OQrr GenQ| |
---------+------+----+----+---------------------------------------+--
e1/1/1
v40
0
0
1
1
1
0
2
2
2
2
2
2
- Self
-
- Self
- Self
- Self
-
0
0
No Disabled
Disabled
e3/1/1
e2/1/1
e1/1/1
v50
0
0
0
0
0
0
No
No
No
Disabled
202
FastIron Ethernet Switch IP Multicast Configuration Guide
53-1003085-02
Download from Www.Somanuals.com. All Manuals Search And Download.
Displaying MLD settings
e1/1/2
v220
e1/1/1
0
0
3
2
2
2
- Self
-
- Self
0
0
0
No
No
Disabled
12
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.
The following table displays the output from the show ipv6 mld interface command.
TABLE 42 Output from the show ipv6 mld interface command
Field
Description
version
Version of the MLD being used.
Query interval in seconds.
query int
max resp time
Number of seconds multicast groups have to respond to queries.
group mem time Number of seconds multicast groups can be members of this group before aging out.
(details) The following is displayed for each interface:
•
•
•
•
•
The port ID
The default MLD version being used
The multicast protocol used
IPV6 address of the multicast interface
If the interface has groups, the group source list, IPv6 multicast address, and the filter mode
are displayed.
To display the MLD parameters on an interface for a specified VRF, enter the following
command as shown in the example below.
device(config)# show ipv mld vrf public interface
---------+------+---------+---------------------------------------+---------+-----
+---------
Intf/Port|Groups| Version |Querier
Tracking
| Timer |V1Rtr|
|
|
Oper Cfg|
|
OQrr
GenQ|
|
---------+------+----+----+---------------------------------------+----+----+-----
+---------
v6
0
2
-
Disabled
e5/1
2
2
- fe80::20c:dbff:fee2:5000
-
11
0 No
v61
Disabled
e11/1
0
2
- Self
0 122 No
Displaying MLD settings
To display MLD settings for the "eng" VRF, enter the following command.
device# show ipv6 mld vrf eng settings
MLD Global Configuration
Query Interval
: 125s
Configured Interval
: 125s
FastIron Ethernet Switch IP Multicast Configuration Guide
53-1003085-02
203
Download from Www.Somanuals.com. All Manuals Search And Download.
Displaying static MLD groups
Max Response Time
: 10s
: 260s
: 2
Group Membership Time
Operating Version
Configured Version
: 0
Robustness Variable
Last Member Query Interval: 1s
Older Host Present Timer : 260s
: 2
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.
The following table displays the output from the show ipv6 mld vrf eng settings command.
TABLE 43 Output from the show ipv6 mld vrf eng settings command
Field
Description
Query Interval
Configured Interval
Max Response Time
How often the router will query an interface for group membership.
The interval that has been configured for the router.
The length of time in seconds that the router will wait for an IGMP (V1 or V2)
response from an interface before concluding that the group member on that
interface is down and removing it from the group.
Group Membership Time
The length of time in seconds that a group will remain active on an interface in the
absence of a group report.
Operating Version
Configured Version
Robustness Variable
The IGMP version operating on the router.
The IGMP version configured on the router.
Used to fine-tune for unexpected loss on the subnet. The value is used to calculate
the group interval.
Last Member Query Interval Indicates when a leave is received; a group-specific query is sent. The last member
query count is the number of queries with a time interval of (LMQT) is sent.
Last Member Query Count Specifies the number of group-specific queries when a leave is received.
Displaying static MLD groups
The following command displays static MLD groups for the "cs" VRF.
device# show ipv6 mld vrf cs static
Group Address
Interface Port List
----------------------------------------+---------+---------
ff1e:1::1
ff1e:a::7f
v3
v3
ethe 2/10
ethe 2/10
Syntax: show ipv6 mld [ vrf vrf-name ] static
The vrf parameter specifies that you want to display static MLD group information for the VRF
specified by the vrf-name variable.
The following table displays the output from the show ipv6 mld vrf cs static command.
204
FastIron Ethernet Switch IP Multicast Configuration Guide
53-1003085-02
Download from Www.Somanuals.com. All Manuals Search And Download.
Displaying MLD traffic
TABLE 44 Output from the show ipv6 mld vrf cs static command
Field
Description
Group Address
Interface Port List
The address of the multicast group.
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.
device# show ipv6 mld traffic
Recv QryV1 QryV2 G-Qry GSQry MbrV1 MbrV2 Leave IS_IN IS_EX ToIN ToEX ALLO BLK
e3/1
e3/2
e6/18
e6/19
e6/20
e6/25
l1
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
176
176
176
176
0
0
0
0
0
0
0
0
0
0
110
110
110
110
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
66
66
66
66
0
0
0
0
0
0
0
0
Send QryV1 QryV2 G-Qry GSQry
e3/1
e3/2
e6/18
e6/19
e6/20
e6/25
l1
0
0
0
0
0
0
0
0
0
10
10
10
10
0
0
0
10
10
10
10
0
0
0
0
0
0
0
0
R2#
The report has a Receive and a Send section.
Syntax: show ipv6 mld [ vrf vrf-name ] traffic
The vrf parameter specifies that you want to display information on MLD traffic for the VRF specified by
the vrf-name variable.
The following table displays the output from the show ipv6 mld traffic command.
TABLE 45 Output from the show ipv6 mld traffic command
Field
Description
QryV1
QryV2
G-Qry
GSQry
MbrV1
MbrV2
Leave
Is_IN
Number of general MLDv1 queries received or sent by the virtual routing interface.
Number of general MLDv2 queries received or sent by the virtual routing interface.
Number of group-specific queries received or sent by the virtual routing interface.
Number of source specific queries received or sent by the virtual routing interface.
Number of MLDv1 membership reports received.
Number of MLDv2 membership reports received.
Number of MLDv1 "leave" messages on the interface. (See 2_Ex for MLDv2.)
Number of source addresses that were included in the traffic.
FastIron Ethernet Switch IP Multicast Configuration Guide
53-1003085-02
205
Download from Www.Somanuals.com. All Manuals Search And Download.
Clearing IPv6 MLD traffic
TABLE 45 Output from the show ipv6 mld traffic command (Continued)
Field
Description
Is_EX
ToIN
Number of source addresses that were excluded in the traffic.
Number of times the interface mode changed from exclude to include.
Number of times the interface mode changed from include to exclude.
ToEX
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.
Clearing IPv6 MLD traffic
To clear counters on IPv6 MLD traffic, enter the following command.
device# clear ipv6 mld traffic
Syntax: clear ipv6 mld [ vrf vrf-name ] traffic
Use the vrf option to clear counters on IPv6 MLD traffic for a VRF instance specified by the vrf-name
variable.
Clearing the IPv6 MLD group membership table cache
You can clear the IPv6 PIM group membership table cache using the following command.
device# clear ipv6 pim cache
Syntax: clear ipv6 pim [ vrf vrf-name ] cache
Use the vrf option to clear the IPv6 PIM group membership table cache for a VRF instance specified
by the vrf-name variable.
IPv6 Multicast Boundaries
The Multicast Boundary feature is designed to selectively allow or disallow multicast flows to
configured interfaces.
The ipv6 multicast-boundary command allows you to configure a boundary on PIM enabled interface
by defining which multicast groups may not forward packets over a specified interface. This includes
incoming and outgoing packets. By default, all interfaces that are enabled for multicast are eligible to
participate in a multicast flow provided they meet the multicast routing protocol’s criteria for
participating in a flow.
206
FastIron Ethernet Switch IP Multicast Configuration Guide
53-1003085-02
Download from Www.Somanuals.com. All Manuals Search And Download.
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. In such a situation,
the ACL would prevail and the port will not be added to the relevant entries.
Either standard or extended ACLs can be used with the multicast boundary feature. When a
standard ACL is used, the address specified is treated as a group address and NOT a source
address.
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 ipv6 multicast-boundary command may not stop clients from receiving multicast traffic if the
filter is applied on the egress interface up-stream from RP.
Configuring multicast boundaries
To define boundaries for PIM enabled interfaces, enter commands such as the following.
device(config)# interface ethernet 1/2
device(config-if-e1000-1/2)#ipv6 multicast-boundary MyBrocadeAccessList
Syntax: [no] ipv6 multicast-boundary acl-spec
Use the acl-spec parameter to define the number or name identifying an access list that controls the
range of group addresses affected by the boundary.
Use the no ipv6 multicast boundary command to remove the boundary on a PIM enabled interface.
The ACL, MyBrocadeAccessList can be configured using standard ACL syntax. Some examples of how
ACLs can be used to filter multicast traffic are as follows:
ACL to permit multicast traffic
To permit multicast traffic for group ff1e::300 and deny all other traffic, enter the following commands.
Brocade(config)# ipv6 access-list abc
Brocade(config-ipv6-access-list abc)# permit ipv6 any host ff1e::300
Brocade(config-ipv6-access-list abc)# deny ipv6 any any
To permit multicast data traffic from source 5555::14 for group ff55::5514 and deny all other traffic, enter
the following commands.
Brocade(config)# ipv6 access-list ex2
Brocade(config-ipv6-access-list ex2)# permit ipv6 host 5555::14 host ff55::5514
Brocade(config-ipv6-access-list ex2)# deny ipv6 any any
ACL to deny multicast traffic
To deny multicast data traffic for group ff55::55 and permit all other traffic, enter the following
commands.
Brocade(config)# ipv6 access-list ex1
Brocade(config-ipv6-access-list ex1)# deny ipv6 any host ff55::55
Brocade(config-ipv6-access-list ex1)# permit ipv6 any any
FastIron Ethernet Switch IP Multicast Configuration Guide
53-1003085-02
207
Download from Www.Somanuals.com. All Manuals Search And Download.
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.
device# show ipv6 pim interface ethernet 1/1/7
Flags
: SM - Sparse Mode v2
---------+---------------------------------------------------+----+---+---+---------
+-------+----------------
Interface|Global Address
Multicast| VRF | DR
|Mode|St |TTL|
| Override
| + Designated Router
| Prio | Interval
Port | |Thr|Boundary
|
|
---------+---------------------------------------------------+----+---+---+---------
+-------+----------------
e1/1/1 a141::1
default 1 3000ms
+ Itself
Total Number of Interfaces : 1
SM
Ena
1
abc
208
FastIron Ethernet Switch IP Multicast Configuration Guide
53-1003085-02
Download from Www.Somanuals.com. All Manuals Search And Download.
IP Multicast Commands
● ip mroute (next hop)......................................................................................................212
● ip multicast disable-flooding..........................................................................................214
● route-precedence..........................................................................................................219
● show ipv6 mroute..........................................................................................................223
● show ipv6 multicast optimization ..................................................................................224
clear ip mroute
Removes multicast routes from the mRTM.
Syntax
clear ip mroute [vrf vrf-name] [ip-address ip-mask | ip-address | mask-bits ]
Parameters
vrf vrf-name
Specifies a VRF.
ip-address
Specifies an IP address.
ip-mask
Specifies an IP subnet mask.
mask-bits
Specifies a subnet mask in bits.
FastIron Ethernet Switch IP Multicast Configuration Guide
53-1003085-02
209
Download from Www.Somanuals.com. All Manuals Search And Download.
clear ipv6 mroute
Modes
Privileged EXEC mode
Usage Guidelines
After mroutes are cleared from an IP multicast routing table, the best static mroutes are added back to
it.
Examples
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.2/24 from the IP multicast routing table:
Device(config)# clear ip mroute 10.0.0.2/24
History
Release version
Command history
8.0.10a
This command was introduced.
clear ipv6 mroute
Removes IPv6 multicast routes from the mRTM.
Syntax
clear ipv6 mroute [ vrf vrf-name] | [ ipv6-address-prefix/prefix-length ]
Parameters
vrf vrf-name
Specifies a VRF route.
ipv6-address-prefix/prefix-length
Specifies an IPv6 address prefix in hexadecimal using 16-bit values between colons as
documented in RFC 2373 and a prefix length as a decimal value.
Modes
Privileged EXEC mode
Usage Guidelines
After mroutes are removed from an IPv6 multicast routing table, the best static mroutes are added back
to it.
Examples
This example removes all mroutes from the IPv6 multicast routing table:
Device(config)# clear ipv6 mroute
This example removes all mroutes from the vrf green IPv6 multicast routing table:
Device(config)# clear ipv6 mroute vrf green
This example removes mroute 2000:7838::/32 from the IPv6 multicast routing table:
Device(config)# clear ipv6 mroute 2000:7838::/32
History
Release version
Command history
8.0.10a
This command was introduced.
210
FastIron Ethernet Switch IP Multicast Configuration Guide
53-1003085-02
Download from Www.Somanuals.com. All Manuals Search And Download.
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
The default is no limit.
num
Command Default
Parameters
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.
Device(config)# vrf my_vrf
Device(config)# address-family ipv4
Device(config-vrf)# ip max-mroute 20
History
Release version
Command history
8.0.10a
This command was introduced.
ip mroute
Adds a directly connected static multicast route.
Syntax
ip mroute [ vrf vrf-name ] ip-address ip-address mask { ethernet | ve | tunnel num } [cost ] [ distance
distance-value ] [ name name ]
no ip mroute [ vrf vrf-name ] ip-address ip-address mask { ethernet | ve | tunnel num } [cost ] [
distance distance-value ] [ name name ]
Command Default
Parameters
No directly connected static multicast route is configured.
vrf vrf-name
Configures a static mroute for this virtual routing and forwarding (VRF) route.
ip-address ip-address mask
Configures the destination IP address and prefix for which the route should be added.
ethernet
Configures an Ethernet interface as the route path.
ve
FastIron Ethernet Switch IP Multicast Configuration Guide
53-1003085-02
211
Download from Www.Somanuals.com. All Manuals Search And Download.
ip mroute (next hop)
Configures a virtual interface as the route path.
Configures a tunnel interface as the route path.
tunnel num
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.
Modes
VRF configuration mode
Usage Guidelines
The no form of this command deletes a previously configured directly connected static multicast route.
Connected routes on PIM enabled interfaces are automatically added to the mRTM table.
Examples
History
This example adds a directly connected mroute to network 10.1.1.0/24 on interface ve 10.
Device(config-vrf)# ip mroute 10.1.1.0 255.255.255.0 ve 10
Release version
Command history
8.0.10a
This command was introduced.
ip mroute (next hop)
Configures a static multicast route with a next hop.
Syntax
ip mroute [ vrf vrf-name ] ip-address ip-address mask next-hop address [ cost ] [ distance distance-
value ] [ name name ]
no ip mroute [ vrf vrf-name ] ip-address ip-address mask next-hop address [ cost ] [ distance distance-
value ] [ name name ]
Command Default
Parameters
No next-hop static multicast route is configured.
vrf vrf-name
Configures a static mroute for this virtual routing and forwarding (VRF) route.
ip-address ip-address mask
The destination IP address and prefix for which the route should be added.
next-hop address
Configures a next-hop address as the route path.
cost
212
FastIron Ethernet Switch IP Multicast Configuration Guide
53-1003085-02
Download from Www.Somanuals.com. All Manuals Search And Download.
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.
This example adds a route to network 10.1.1.0/24 with next hop 10.2.1.1.
Device(config-vrf)# ip mroute 10.1.1.0 255.255.255.0 10.2.1.1
History
Release version
Command history
8.0.10a
This command was introduced.
ip mroute next-hop-enable-default
Enables the option to use the default mroute to resolve a static mroute next hop.
ip mroute [ vrf vrf-name ] next-hop-enable-default
Syntax
no ip mroute [ vrf vrf-name ] next-hop-enable-default
Static mroutes are not resolved using the default mroute.
vrf vrf-name
Command Default
Parameters
Configures a static mroute for this virtual routing and forwarding (VRF) route.
Modes
Usage Guidelines
Examples
VRF configuration mode
The no form of this command disables the default mroute option for next hops.
This example enables the use of the default mroute to resolve a static mroute next hop:
Device(config-vrf)# ip mroute next-hop-enable-default
History
Release version
Command history
8.0.10a
This command was introduced.
FastIron Ethernet Switch IP Multicast Configuration Guide
53-1003085-02
213
Download from Www.Somanuals.com. All Manuals Search And Download.
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
The recursion level for resolving a static mroute next hop is 3.
vrf vrf-name
Command Default
Parameters
Configures a static mroute for this virtual routing and forwarding (VRF) route.
Modes
Usage Guidelines
Examples
VRF configuration mode
The no form of this command restores the default recursion level for resolving a static mroute next hop.
This example sets the recursion level for resolving a static mroute next hop to 7:
Device(config-vrf)# ip mroute next-hop-recursion 7
This example sets the recursion level for resolving a static mroute next hop to the default value, 3:
Device(config-vrf)# ip mroute next-hop-recursion
This example disables the recursion for resolving a static mroute next hop:
Device(config-vrf)# no ip mroute next-hop-recursion
History
Release version
Command history
8.0.10a
This command was introduced.
ip multicast disable-flooding
Disables the flooding of unregistered IPv4 multicast frames in an IGMP-snooping-enabled VLAN.
ip multicast disable-flooding
Syntax
no ip multicast disable-flooding
Command Default
Modes
The switch floods unregistered IPv4 multicast frames in an IGMP-snooping-enabled VLAN.
Global configuration mode
Usage Guidelines
NOTE
This command is supported only on ICX 6650 devices.
The no form of this command enables the flooding of unregistered IPv4 multicast frames in an IGMP-
snooping-enabled VLAN.
214
FastIron Ethernet Switch IP Multicast Configuration Guide
53-1003085-02
Download from Www.Somanuals.com. All Manuals Search And Download.
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
History
The following example shows the disabling of flooding of unregistered IPv4 multicast frames.
Brocade(config)# ip multicast disable-flooding
Release version
Command history
08.0.01
This command was introduced.
ipv6 max-mroute
Configures a limit to the number of IPv6 multicast routes supported.
ipv6 max-mroute num
Syntax
no ipv6 max-mroute
Command Default
Parameters
The default is no limit.
num
Configures the maximum number of IPv6 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 IPv6 multicast routes supported on the VRF named my_vrf to 20.
Device(config)# vrf my_vrf
Device(config)# address-family ipv6
Device(config-vrf)# ipv6 max-mroute 20
History
Release version
Command history
8.0.10a
This command was introduced.
ipv6 mroute
Configures a static IPv6 route to direct multicast traffic along a specific path.
Syntax
ipv6 mroute [vrf vrf-name] ipv6-address-prefix/prefix-length { ethernet | ve | tunnel num } [cost ] [
distance distance-value ] [ name name ]
no ipv6 mroute [vrf vrf-name] ipv6-address-prefix/prefix-length { ethernet | ve | tunnel num } [cost ] [
distance distance-value ] [ name name ]
Command Default
No static multicast route is configured.
FastIron Ethernet Switch IP Multicast Configuration Guide
53-1003085-02
215
Download from Www.Somanuals.com. All Manuals Search And Download.
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.
Configures a virtual interface as the route path.
ve
cost
Configures a metric for comparing the route to other static routes in the IPv6 static route
table that have the same destination. The range is 1 to 16; the default is 1.
distance distance-value
Configures the route's administrative distance. The range is 1 to 255; the default is 1.
name name
Name for this static route.
Modes
VRF configuration mode
Usage Guidelines
The no form of this command deletes a previously configured static multicast route.
Connected routes on PIM enabled interfaces are automatically added to the mRTM table.
Examples
History
This example configures a static IPv6 mroute to directly connected network 2020::0/120 on virtual
interface ve 130.
Device(config-vrf)# ipv6 mroute 2020::0/120 ve 130
Release version
Command history
8.0.10a
This command was introduced.
ipv6 mroute (next hop)
Configures a static mroute with a next hop.
Syntax
ipv6 mroute [ vrf vrf-name ] ipv6-address-prefix/prefix-length next-hop address [ cost ] [ distance
distance-value ] [ name name ]
no ipv6 mroute [ vrf vrf-name ] ipv6-address-prefix/prefix-length next-hop address [ cost ] [ distance
distance-value ] [ name name ]
Command Default
Parameters
No next-hop static mroute is configured.
vrf vrf-name
216
FastIron Ethernet Switch IP Multicast Configuration Guide
53-1003085-02
Download from Www.Somanuals.com. All Manuals Search And Download.
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
cost
Configures a next-hop address as the route path.
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 to 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 mroute.
This example adds a route to network 2020::0/120 with 2022::0/120 as the next hop.
Device(config-vrf)# ipv6 mroute 2020::0/120 2022::0/120
History
Release version
Command history
8.0.10a
This command was introduced.
ipv6 mroute next-hop-enable-default
Enables the option to use the default mroute to resolve a static mroute next hop.
ipv6 mroute [ vrf vrf-name ] next-hop-enable-default
Syntax
no ipv6 mroute [ vrf vrf-name ] next-hop-enable-default
Static mroutes are not resolved using the default mroute.
vrf vrf-name
Command Default
Parameters
Configures a static mroute for this virtual routing and forwarding (VRF) route.
Modes
Usage Guidelines
Examples
VRF configuration mode
The no form of this command disables the default mroute option for next hops.
This example enables the use of the default mroute to resolve a static mroute next hop:
Device(config-vrf)# ipv6 mroute next-hop-enable-default
FastIron Ethernet Switch IP Multicast Configuration Guide
53-1003085-02
217
Download from Www.Somanuals.com. All Manuals Search And Download.
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.
ipv6 mroute [ vrf vrf-name ] next-hop-recursion 1-10
Syntax
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.
vrf vrf-name
Configures a static mroute for this virtual routing and forwarding (VRF) route.
Modes
Usage Guidelines
Examples
VRF configuration mode
The no form of this command restores the default recursion level for resolving a static mroute next hop.
This example sets the recursion level for resolving a static mroute next hop to 7:
Device(config-vrf)# ipv6 mroute next-hop-recursion 7
This example sets the recursion level for resolving a static mroute next hop to the default value, 3:
Device(config-vrf)# ipv6 mroute next-hop-recursion
This example disables the recursion for resolving a static mroute next hop:
Device(config-vrf)# no ipv6 mroute next-hop-recursion
History
Release version
Command history
8.0.10a
This command was introduced.
ipv6 multicast disable-flooding
Disables the flooding of unregistered IPv6 multicast frames in an MLD-snooping-enabled VLAN.
ipv6 multicast disable-flooding
Syntax
no ipv6 multicast disable-flooding
Command Default
Modes
The switch floods unregistered IPv6 multicast frames in an MLD-snooping-enabled VLAN.
Global configuration mode
218
FastIron Ethernet Switch IP Multicast Configuration Guide
53-1003085-02
Download from Www.Somanuals.com. All Manuals Search And Download.
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 MLD-
snooping-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.
Examples
History
The following example shows the disabling of flooding of unregistered IPv6 multicast frames.
Brocade(config)# ipv6 multicast disable-flooding
Release version
Command history
08.0.01
This command was introduced.
route-precedence
Configures a table that specifies the order in which routes are selected for multicast.
Syntax
route-precedence { [ mc-non-default | none ] | [ mc-default | none ] | [ uc-non-default | none ] | [ uc-
default | none ] }
no route-precedence
Command Default
Parameters
The default is route-precedence mc-non-default mc-default uc-non-default uc-default.
mc-non-default
Specifies precedence for a non-default multicast route table (mRTM).
none
Specifies that certain types of route be ignored.
mc-default
Specifies precedence for an mRTM.
uc-non-default
Specifies precedence for a non-default unicast route table (uRTM).
uc-default
Specifies precedence for a uRTM.
Modes
PIM configuration mode
Usage Guidelines
The no form of this command removes the configuration and restores the default route precedence
settings.
FastIron Ethernet Switch IP Multicast Configuration Guide
53-1003085-02
219
Download from Www.Somanuals.com. All Manuals Search And Download.
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.
Device(config)# router pim
Device(config-pim-router)# route-precedence mc-non-default uc-non-default mc-default
uc-default
This command specifies that the unicast default route be ignored.
Device(config)# router pim
Device(config-pim-router)# route-precedence mc-non-default mc-default uc-non-default
none
History
Release version
Command history
8.0.10a
This command was introduced.
route-precedence admin-distance
Specifies that multicast routes are selected from the best route from the multicast routing table
(mRTM) and the unicast routing (uRTM) table.
Syntax
route-precedence admin-distance
no route-precedence admin-distance
Command Default
Modes
The default is route-precedence mc-non-default mc-default uc-non-default uc-default.
PIM configuration mode
Usage Guidelines
The no form of this command removes the configuration and restores the default route precedence
settings.
If both the mRTM and the uRTM have routes of equal cost, the route from the mRTM is preferred.
Examples
History
The following example shows how to specify that the best multicast route from the mRTM and uRTM
tables is selected.
Device(config-pim-router)#route-precedence admin-distance
Release version
Command history
8.0.10a
This command was introduced.
show ip mroute
Displays information on multicast routes. You can specify whether you want to display information
from static or connected mroutes or from a particular mroute.
Syntax
show ip mroute [vrf vrf-name ] [ static | connected] | [ ip-subnet [ mask]]
vrf vrf-name
Parameters
220
FastIron Ethernet Switch IP Multicast Configuration Guide
53-1003085-02
Download from Www.Somanuals.com. All Manuals Search And Download.
IP Multicast Commands
Specifies a VRF route.
static
Specifies a static multicast route.
connected
ip-subnet [ mask ]
Specifies a directly attached (connected) multicast route.
Specifies an IP address.
Modes
Privileged EXEC mode
Examples
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
Uptime
Gateway
220.220.220.1
DIRECT
Port
Cost
1/1
0/0
0/0
0/0
0/0
Type
1
S
2
D
3
D
4
D
5
D
20.20.20.0/24
8m54s
ve 220
ve 50
50.50.50.0/24
8h26m
77.1.1.1/32
8h26m
DIRECT
loopback 1
ve 129
ve 220
129.129.129.0/24
8h26m
DIRECT
220.220.220.0/24
2h49m
DIRECT
This example displays information for static multicast routes:
Device(config)# show ip mroute static
Type Codes - B:BGP D:Connected S:Static;
Cost - Dist/Metric
Destination
Gateway
Port
Cost
1/1
Type
S
Uptime
8m54s
1
20.20.20.0/24
220.220.220.1
ve 220
This example displays information for directly attached multicast routes:
Device(config)# show ip mroute connected
Type Codes - B:BGP D:Connected S:Static;
Cost - Dist/Metric
Destination
Gateway
DIRECT
DIRECT
DIRECT
DIRECT
Port
Cost
Type
Uptime
1
2
3
4
50.50.50.0/24
77.1.1.1/32
129.129.129.0/24
220.220.220.0/24
ve 50
0/0
0/0
0/0
0/0
D
D
D
D
8h26m
8h26m
8h26m
2h49m
loopback 1
ve 129
ve 220
This example displays information for IP multicast route 50.50.50.100:
Device(config)# show ip mroute 50.50.50.100
Type Codes - B:BGP D:Connected S:Static;
Cost - Dist/Metric
Destination
Gateway
DIRECT
Port
Cost
0/0
Type
D
Uptime
8h26m
1
50.50.50.0/24
ve 50
History
Release version
8.0.10a
Command history
This command was introduced.
FastIron Ethernet Switch IP Multicast Configuration Guide
53-1003085-02
221
Download from Www.Somanuals.com. All Manuals Search And Download.
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
show ip multicast optimization [ ipmc ]
Parameters
ipmc
Specifies the IPMC group index.
Modes
Privileged EXEC mode
Usage Guidelines
NOTE
The show ip multicast optimization command is available only on ICX 7750 devices.
Examples
This example displays resource information showing that IPMC group index 4 is shared by two users
and the ports included in the set are 1/1/6 and 1/1/1:
Device(config-vlan-150)#show ip multicast optimization
Total IPMCs Allocated:
0; Available: 8192; Failed:
0
Index
1.
IPMC
4
1
SetId
0x161fcbd8
0x161d0930
Users
Set
2 {<1/1/6>,<1/1/1>,}
2.
10 {<1/1/6>,<1/1/4>,<1/1/3>,<1/1/2>,
<1/1/1>,}
Sharability Coefficient: 76%
History
Release version
Command history
This command was introduced.
8.0.10
show ip static mroute
Displays information for configured multicast routes.
show ip static mroute [ vrf vrf-name ] ip-subnet mask
Syntax
Parameters
vrf vrf-name
Specifies a VRF route.
Specifies an IP address.
ip-subnet [ mask ]
Modes
Privileged EXEC mode
Usage Guidelines
Only resolved and best static mroutes are added to the mRTM table. These routes are prefixed with an
asterisk in the output from the show ip static mroute command.
222
FastIron Ethernet Switch IP Multicast Configuration Guide
53-1003085-02
Download from Www.Somanuals.com. All Manuals Search And Download.
show ipv6 mroute
Examples
History
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 Dis/Metric/Tag Name
*20.20.20.0/24
20.20.20.0/24
21.21.21.0/24
220.220.220.1
50.50.50.2
1.2.3.4
-
-
-
1/1/0
1/2/0
1/1/0
Release version
Command history
This command was introduced.
8.0.10a
show ipv6 mroute
Displays information on IPv6 multicast routes. You can specify whether you want to display information
from static or connected mroutes or from a particular mroute.
Syntax
show ipv6 mroute [vrf vrf-name ] [ static | connect] | [ ipv6-address ipv6-prefix/prefix-length] [
summary ]
Parameters
vrf vrf-name
Specifies displaying mroutes for a particular VRF
ipv6-address ipv6-prefix/prefix-length
Specifies displaying an IPv6 mroute for the specified destination.
static
Specifies displaying only static multicast routes.
connect
Specifies displaying only connected multicast routes.
summary
Specifies displaying summary information.
Modes
Privileged EXEC mode
Examples
This example displays information for IPv6 multicast routes:
Device(config)# show ipv6 mroute
IPv6 Routing Table - 7 entries:
Type Codes - B:BGP C:Connected S:Static
Type IPv6 Prefix
Next Hop Router
Interface
ve 90
Dis/Metric
1/1
Uptime
2d16h
6d21h
1d21h
1d21h
1d21h
6d21h
6d21h
S
C
C
C
C
C
C
1:1::1:0/120
2090::/64
2100::/64
2110::/64
2120::/64
2130::/64
8811::1/128
::
::
::
::
::
::
::
ve 90
0/0
ve 100
0/0
ve 110
0/0
ve 120
0/0
ve 130
0/0
loopback 1
0/0
FastIron Ethernet Switch IP Multicast Configuration Guide
53-1003085-02
223
Download from Www.Somanuals.com. All Manuals Search And Download.
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
1:1::1:0/120
Next Hop Router
::
Interface
ve 90
Dis/Metric
1/1
Uptime
2d16h
S
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
Interface
ve 90
Dis/Metric
0/0
Uptime
6d21h
1d21h
1d21h
1d21h
6d21h
6d21h
C
C
C
C
C
C
2090::/64
2100::/64
2110::/64
2120::/64
2130::/64
8811::1/128
::
::
::
::
::
::
ve 100
0/0
ve 110
0/0
ve 120
0/0
ve 130
0/0
loopback 1
0/0
This example displays information for IPv6 multicast route 2090::1:
Device(config)# show ipv6 mroute 2090::1
Type Codes - B:BGP C:Connected S:Static
Type IPv6 Prefix
2090::/64
Next Hop Router
::
Interface
ve 90
Dis/Metric
0/0
Uptime
6d21h
C
History
Release version
Command history
8.0.10a
This command was introduced.
show ipv6 multicast optimization
Displays multicast listening discovery (MLD) snooping hardware resource-sharing information. You
can configure it to display the availability of Layer 2 multicast (L2MC) group indexes in the hardware
and how it is been used and shared.
Syntax
show ipv6 multicast optimization [ l2mc ]
Parameters
l2mc
Specifies the L2MC group index.
Modes
Privileged EXEC mode
Usage Guidelines
NOTE
The show ipv6 multicast optimization command is available only on ICX 7750 devices.
Examples
This example displays resource information showing that L2MC group index 4 is shared by two users
and the ports included in the set are 1/1/6 and 1/1/1:
Device (config-vlan-150)#show ipv6 multicast optimization
Total L2MCs Allocated:
0; Available: 8192; Failed:
0
Index
1.
L2MC
4
1
SetId
0x161fcbd8
0x161d0930
Users
Set
2 {<1/1/6>,<1/1/1>,}
2.
10 {<1/1/6>,<1/1/4>,<1/1/3>,<1/1/2>,
<1/1/1>,}
Sharability Coefficient: 76%
224
FastIron Ethernet Switch IP Multicast Configuration Guide
53-1003085-02
Download from Www.Somanuals.com. All Manuals Search And Download.
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
show ipv6 static mroute [ vrf vrf-name ] ipv6-address-prefix/prefix-length
Parameters
vrf vrf-name
Specifies a VRF route.
ipv6-address-prefix/prefix-length
Specifies an IPv6 address.
Modes
Privileged EXEC mode
Usage Guidelines
Only resolved and best static mroutes are added to the mRTM table. These routes are prefixed with an
asterisk in the output from the show ipv6 static mroute command.
Examples
History
This example displays information for configured IPv6 multicast routes:
Device(config)# show ipv6 static mroute
IPv6 Static Routing Table - 1 entries:
IPv6 Prefix
*1:1::1:0/120
Interface Next Hop Router
Met/Dis/Tag Name
1/1/0
ve 90
::
Release version
Command history
8.0.10a
This command was introduced.
FastIron Ethernet Switch IP Multicast Configuration Guide
53-1003085-02
225
Download from Www.Somanuals.com. All Manuals Search And Download.
show ipv6 static mroute
226
FastIron Ethernet Switch IP Multicast Configuration Guide
53-1003085-02
Download from Www.Somanuals.com. All Manuals Search And Download.
Index
clear commands 34
C
command
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
modifying the maximum response time 22
modifying the query interval 22
overview 13
queriers and non-queriers 14
tracking and fast leave 15
VLAN-specific configuration 15
clear ip multicast counters 35
clear ip multicast mcache 34
clear ip multicast vlan 34
ip multicast 20
ip multicast age-interval 22
ip multicast leave-wait-time 23
ip multicast max-response-time 22
ip multicast mcache-age 23
ip multicast query-interval 22
ip multicast report-control 23
ip multicast verbose-off 24
ip multicast version 19
multicast pimsm-snooping 39
multicast proxy-off 24
multicast static-group 21
command output
show ip igmp traffic 145
show ip multicast error 27
Interface
show ip multicast group 27
show ip multicast mcache 28
show ip multicast pimsm-snooping 41
show ip multicast resource 29
show ip multicast traffic 30
show ip multicast vlan 26
Internet Group Management Protocol (IGMP)
displaying proxy traffic information 145
proxy configuration 144
M
multicast
enabling or disabling error and warning messages
modifying the cache age time 23
turning off static group proxy 24
F
feature support
IP multicast reduction 13
P
PIM
I
IGMP
overview 102
PIM SM snooping
configuring for individual ports in a VLAN 21
configuring the mode 19
membership tracking and fast leave for the VLAN
modifying the age interval for group membership
entries 22
IGMP snooping
FastIron Ethernet Switch IP Multicast Configuration Guide
53-1003085-02
227
Download from Www.Somanuals.com. All Manuals Search And Download.
multicast activeVLAN
multicast passive 20
displaying errors 27
displaying information for a specific group or
source group pair 41
enabling on a VLAN 39
show commands
multicast disable-multicast-snoop 22
multicast fast-convergencecommand
multicast fast-convergence 25
multicast fast-leave-v2command
multicast fast-leave-v2 25
multicast port-version 21
multicast proxy-off 24
show command
multicast router-portcommand
multicast router-port ethernet 24
multicast trackingcommand
multicast tracking 24
show ip multicast 26
PIM SM traffic snooping
enabling globally on the device 19
global tasks 17
multicast version 2VLAN
multicast version 3 20
port-specific tasks 17
VLAN-specific tasks 17
PIM Sparse domains joined by MSDP devices 121
S
show command
show ip igmp traffic 145
show ip multicast error 27
show ip multicast group 27
show ip multicast mcache 28
show ip multicast resource 29
show ip multicast traffic 30
show ip multicast vlanPIM SM snooping
show commands 32
show ip pimsm-snooping 40
static router ports, configuring 24
V
VLAN
mld-snooping active | passive 52
mld-snooping disable-mld-snoop 52
mld-snooping fast-convergence 55
mld-snooping fast-leave-v1 54
mld-snooping port-version 1 | 2 ethernet 53
mld-snooping proxy-off 53
mld-snooping router-port ethernet 53
mld-snooping static-group 53
mld-snooping tracking 54
mld-snooping version 1 | 2 52
228
FastIron Ethernet Switch IP Multicast Configuration Guide
53-1003085-02
Download from Www.Somanuals.com. All Manuals Search And Download.
|