Multicast ExtremeXOS 15.5

Multicast
ExtremeXOS 15.5 User Guide
120936-00 Rev. 2
Published June 2014
Copyright 20112014 All rights reserved.
Legal Notice
Extreme Networks, Inc., on behalf of or through its wholly-owned subsidiary, Enterasys Networks,
Inc., reserves the right to make changes in specifications and other information contained in this
document and its website without prior notice. The reader should in all cases consult
representatives of Extreme Networks to determine whether any such changes have been made.
The hardware, firmware, software or any specifications described or referred to in this document
are subject to change without notice.
Trademarks
Extreme Networks and the Extreme Networks logo are trademarks or registered trademarks of
Extreme Networks, Inc. in the United States and/or other countries.
All other names (including any product names) mentioned in this document are the property of
their respective owners and may be trademarks or registered trademarks of their respective
companies/owners.
For additional information on Extreme Networks trademarks, please see:
www.extremenetworks.com/company/legal/trademarks/
Support
For product support, including documentation, visit: www.extremenetworks.com/support/
For information, contact:
Extreme Networks, Inc.
145 Rio Robles
San Jose, California 95134
USA
Table of Contents
Preface......................................................................................................................................... 8
Conventions.............................................................................................................................................................................8
Related Publications............................................................................................................................................................9
Providing Feedback to Us.............................................................................................................................................. 10
Navigating the ExtremeXOS User Guide...........................................................................................................................11
Chapter 1: Multicast Routing and Switching.........................................................................12

Multicast Routing Overview........................................................................................................................................... 12
Multicast Table Management.........................................................................................................................................13
PIM Overview.........................................................................................................................................................................19
IGMP Overview.................................................................................................................................................................... 32
Configuring EAPS Support for Multicast Traffic.................................................................................................37
Configuring IP Multicast Routing................................................................................................................................38
Multicast VLAN Registration........................................................................................................................................ 47
Displaying Multicast Information................................................................................................................................ 58
Troubleshooting PIM.........................................................................................................................................................58
Chapter 2: IPv6 Multicast....................................................................................................... 60

Multicast Listener Discovery (MLD) Overview....................................................................................................60
Managing MLD.................................................................................................................................................................... 60
Chapter 3: MSDP...................................................................................................................... 69
MSDP Overview.................................................................................................................................................................. 69
PIM Border Configuration.............................................................................................................................................. 70
MSDP Peers...........................................................................................................................................................................70
MSDP Mesh-Groups...........................................................................................................................................................72
Anycast RP............................................................................................................................................................................ 73
SA Cache................................................................................................................................................................................ 75
Redundancy.......................................................................................................................................................................... 76
SNMP MIBs.............................................................................................................................................................................76
Chapter 4: Multicast Commands............................................................................................77

clear igmp group................................................................................................................................................................. 81
clear igmp snooping......................................................................................................................................................... 82
clear mld counters............................................................................................................................................................. 83
clear mld group...................................................................................................................................................................84
clear mld snooping............................................................................................................................................................84
clear msdp counters......................................................................................................................................................... 85
clear msdp sa-cache......................................................................................................................................................... 87
clear pim cache................................................................................................................................................................... 88
clear pim snooping............................................................................................................................................................ 89
configure forwarding ipmc compression...............................................................................................................90
configure forwarding ipmc lookup-key....................................................................................................................91
configure igmp router-alert receive-required......................................................................................................92
configure igmp router-alert transmit....................................................................................................................... 93
configure igmp snooping filters..................................................................................................................................94
configure igmp snooping flood-list...........................................................................................................................96
configure igmp snooping leave-timeout................................................................................................................ 98
configure igmp snooping timer.................................................................................................................................. 98
Multicast
Table of Contents
configure igmp snooping vlan ports add dynamic group...........................................................................100

configure igmp snooping vlan ports add static group................................................................................... 101
configure igmp snooping vlan ports add static router..................................................................................103
configure igmp snooping vlan ports delete static group.............................................................................104
configure igmp snooping vlan ports delete static router.............................................................................105
configure igmp snooping vlan ports filter............................................................................................................105
configure igmp snooping vlan ports set join-limit........................................................................................... 107
configure igmp ssm-map add....................................................................................................................................108
configure igmp ssm-map delete...............................................................................................................................109
configure igmp....................................................................................................................................................................110
configure ipmcforwarding.............................................................................................................................................. 111
configure ipmroute add.................................................................................................................................................. 112
configure ipmroute delete............................................................................................................................................. 113
configure iproute add (Multicast)..............................................................................................................................114
configure iproute delete................................................................................................................................................. 115
configure mcast ipv4 cache timeout....................................................................................................................... 116
configure mcast ipv6 cache timeout........................................................................................................................117
configure mld....................................................................................................................................................................... 118
configure mld snooping fast-learning.................................................................................................................... 120
configure mld snooping filters................................................................................................................................... 120
configure mld snooping flood-list..............................................................................................................................121
configure mld snooping leave-timeout..................................................................................................................123
configure mld snooping timer.................................................................................................................................... 124
configure mld snooping vlan ports add dynamic group...............................................................................125
configure mld snooping vlan ports add static group..................................................................................... 127
configure mld snooping vlan ports add static router..................................................................................... 128
configure mld snooping vlan ports delete static group................................................................................ 129
configure mld snooping vlan ports delete static router............................................................................... 130
configure mld snooping vlan ports filter................................................................................................................ 131
configure mld snooping vlan ports join-limit...................................................................................................... 132
configure mld ssm-map add....................................................................................................................................... 133
configure mld ssm-map delete.................................................................................................................................. 134
configure msdp as-display-format...........................................................................................................................135
configure msdp max-rejected-cache......................................................................................................................136
configure msdp originator-id...................................................................................................................................... 137
configure msdp peer default-peer........................................................................................................................... 138
configure msdp peer description.............................................................................................................................140
configure msdp peer mesh-group............................................................................................................................ 141
configure msdp peer no-default-peer....................................................................................................................142
configure msdp peer password.................................................................................................................................143
configure msdp peer sa-filter..................................................................................................................................... 144
configure msdp peer sa-limit......................................................................................................................................145
configure msdp peer source-interface.................................................................................................................. 146
configure msdp peer timer.......................................................................................................................................... 147
configure msdp peer ttl-threshold...........................................................................................................................148
configure msdp sa-cache-server.............................................................................................................................. 149
configure mvr add receiver......................................................................................................................................... 150
configure mvr add vlan................................................................................................................................................... 151
configure mvr delete receiver.....................................................................................................................................152
Multicast
Table of Contents
configure mvr delete vlan.............................................................................................................................................153

configure mvr mvr-address......................................................................................................................................... 154
configure mvr static group.......................................................................................................................................... 155
configure pim add vlan.................................................................................................................................................. 156
configure pim border...................................................................................................................................................... 158
configure pim cbsr........................................................................................................................................................... 159
configure pim crp static................................................................................................................................................160
configure pim crp timer.................................................................................................................................................. 161
configure pim crp vlan................................................................................................................................................... 162
configure pim delete vlan............................................................................................................................................. 163
configure pim dr-priority.............................................................................................................................................. 164
configure pim iproute sharing hash.........................................................................................................................165
configure pim register-policy rp .............................................................................................................................. 166
configure pim register-policy..................................................................................................................................... 167
configure pim register-checksum-to...................................................................................................................... 168
configure pim register-rate-limit-interval............................................................................................................. 169
configure pim register-suppress-interval register-probe-interval........................................................... 170
configure pim shutdown-priority............................................................................................................................... 171
configure pim spt-threshold........................................................................................................................................ 172
configure pim ssm range...............................................................................................................................................173
configure pim ssm............................................................................................................................................................ 174
configure pim state-refresh timer origination-interval...................................................................................175
configure pim state-refresh timer source-active-timer................................................................................. 176
configure pim state-refresh ttl................................................................................................................................... 177
configure pim state-refresh......................................................................................................................................... 178
configure pim timer vlan............................................................................................................................................... 179
configure pim vlan trusted-gateway...................................................................................................................... 180
create msdp mesh-group.............................................................................................................................................. 181
create msdp peer..............................................................................................................................................................182
delete msdp mesh-group............................................................................................................................................. 183
delete msdp peer..............................................................................................................................................................184
disable igmp snooping vlan fast-leave...................................................................................................................185
disable igmp snooping................................................................................................................................................... 185
disable igmp ssm-map................................................................................................................................................... 187
disable igmp........................................................................................................................................................................ 187
disable ipmcforwarding ipv6...................................................................................................................................... 188
disable ipmcforwarding.................................................................................................................................................189
disable mld...........................................................................................................................................................................190
disable mld snooping....................................................................................................................................................... 191
disable mld-ssm map...................................................................................................................................................... 192
disable msdp data-encapsulation.............................................................................................................................193
disable msdp export local-sa......................................................................................................................................194
disable msdp peer............................................................................................................................................................ 195
disable msdp process-sa-request.............................................................................................................................195
disable msdp....................................................................................................................................................................... 197
disable mvr...........................................................................................................................................................................197
disable pim iproute sharing......................................................................................................................................... 198
disable pim snooping......................................................................................................................................................199
disable pim ssm vlan..................................................................................................................................................... 200
Multicast
Table of Contents
disable pim...........................................................................................................................................................................201
enable igmp snooping vlan fast-leave.................................................................................................................. 202
enable igmp snooping with-proxy..........................................................................................................................203
enable igmp snooping.................................................................................................................................................. 204
enable igmp ssm-map...................................................................................................................................................205
enable igmp........................................................................................................................................................................206
enable ipmcforwarding ipv6...................................................................................................................................... 207
enable ipmcforwarding................................................................................................................................................ 208
enable mld.......................................................................................................................................................................... 209
enable mld snooping with-proxy..............................................................................................................................210
enable mld snooping........................................................................................................................................................ 211
enable mld-ssm map........................................................................................................................................................ 211
enable msdp data-encapsulation..............................................................................................................................212
enable msdp export local-sa....................................................................................................................................... 213
enable msdp peer............................................................................................................................................................. 215
enable msdp process-sa-request..............................................................................................................................216
enable msdp........................................................................................................................................................................ 217
enable mvr............................................................................................................................................................................218
enable pim iproute sharing.......................................................................................................................................... 219
enable pim snooping..................................................................................................................................................... 220
enable pim ssm vlan........................................................................................................................................................ 221
enable pim........................................................................................................................................................................... 222
mrinfo.....................................................................................................................................................................................223
mtrace................................................................................................................................................................................... 224
refresh mld ssm-map..................................................................................................................................................... 227
rtlookup rpf......................................................................................................................................................................... 228
rtlookup................................................................................................................................................................................ 229
show igmp group............................................................................................................................................................ 230
show igmp snooping cache........................................................................................................................................232
show igmp snooping vlan filter.................................................................................................................................233
show igmp snooping vlan static.............................................................................................................................. 234
show igmp snooping vlan............................................................................................................................................235
show igmp snooping......................................................................................................................................................236
show igmp ssm-map...................................................................................................................................................... 237
show igmp...........................................................................................................................................................................238
show ipmroute.................................................................................................................................................................. 239
show iproute multicast.................................................................................................................................................240
show L2stats...................................................................................................................................................................... 242
show mcast cache...........................................................................................................................................................243
show mcast ipv6 cache................................................................................................................................................ 245
show mld............................................................................................................................................................................. 246
show mld counters......................................................................................................................................................... 248
show mld group............................................................................................................................................................... 249
show mld snooping vlan filter................................................................................................................................... 250
show mld snooping vlan static................................................................................................................................. 250
show mld snooping..........................................................................................................................................................251
show mld ssm-map.........................................................................................................................................................253
show msdp memory.......................................................................................................................................................255
show msdp mesh-group.............................................................................................................................................. 256
Multicast
Table of Contents
show msdp peer............................................................................................................................................................... 257

show msdp sa-cache..................................................................................................................................................... 259
show msdp...........................................................................................................................................................................261
show mvr cache............................................................................................................................................................... 262
show mvr............................................................................................................................................................................. 263
show pim cache................................................................................................................................................................263
show pim snooping........................................................................................................................................................ 265
show pim..............................................................................................................................................................................266
unconfigure igmp snooping vlan ports set join-limit..................................................................................... 272
unconfigure igmp ssm-map........................................................................................................................................273
unconfigure igmp.............................................................................................................................................................273
unconfigure mld............................................................................................................................................................... 274
unconfigure mld ssm-map.......................................................................................................................................... 275
unconfigure msdp sa-cache-server........................................................................................................................ 276
unconfigure pim border................................................................................................................................................277
unconfigure pim ssm range........................................................................................................................................ 278
unconfigure pim............................................................................................................................................................... 279
Multicast
Preface
Conventions
This section discusses the conventions used in this guide.
Text Conventions
The following tables list text conventions that are used throughout this guide.
Table 1: Notice Icons
Icon
Notice Type
Alerts you to...
Note
Important features or instructions.
Caution
Risk of personal injury, system damage, or loss of data.
Warning
Risk of severe personal injury.
New
This command or section is new for this release.
Table 2: Text Conventions

Convention
Screen displays
Description
This typeface indicates command syntax, or represents information as it appears on
the screen.
The words enter and

type
When you see the word enter in this guide, you must type something, and then press
the Return or Enter key. Do not press the Return or Enter key when an instruction
simply says type.
[Key] names
Key names are written with brackets, such as [Return] or [Esc]. If you must press two
or more keys simultaneously, the key names are linked with a plus sign (+). Example:
Press [Ctrl]+[Alt]+[Del]
Words in italicized type
Italics emphasize a point or denote new terms at the place where they are defined in
the text. Italics are also used when referring to publication titles.
Multicast
Preface
Platform-Dependent Conventions
Unless otherwise noted, all information applies to all platforms supported by ExtremeXOS software,
which are the following:
BlackDiamond X8 series switch

BlackDiamond 8800 series switches
Cell Site Routers (E4G-200 and E4G-400)
Summit family switches
SummitStack
When a feature or feature implementation applies to specific platforms, the specific platform is noted in
the heading for the section describing that implementation in the ExtremeXOS command
documentation. In many cases, although the command is available on all platforms, each platform uses
specific keywords. These keywords specific to each platform are shown in the Syntax Description and
discussed in the Usage Guidelines.
Terminology
When features, functionality, or operation is specific to a switch family, the family name is used.
Explanations about features and operations that are the same across all product families simply refer to
the product as the switch.
Related Publications
Documentation for Extreme Networks products is available at: www.extremenetworks.com. The
following is a list of related publications currently available:
ExtremeXOS User Guide

ExtremeXOS Hardware and Software Compatibility Matrix
ExtremeXOS Legacy CLI Quick Reference Guide
ExtremeXOS ScreenPlay User Guide
Using AVB with Extreme Switches
BlackDiamond 8800 Series Switches Hardware Installation Guide

BlackDiamond X8 Switch Hardware Installation Guide
Extreme Networks Pluggable Interface Installation Guide
Summit Family Switches Hardware Installation Guide
Ridgeline Installation and Upgrade Guide

Ridgeline Reference Guide
SDN OpenFlow Implementation Guide

SDN OpenStack Install Guide
Some ExtremeXOS software files have been licensed under certain open source licenses. Information is
available at: www.extremenetworks.com/services/osl-exos.aspx
Multicast
Preface
Providing Feedback to Us
We are always striving to improve our documentation and help you work better, so we want to hear
from you! We welcome all feedback but especially want to know about:
Content errors or confusing or conflicting information.
Ideas for improvements to our documentation so you can find the information you need faster.
Broken links or usability issues.
If you would like to provide feedback to the Extreme Networks Information Development team about
this document, please contact us using our short online feedback form. You can also email us directly at
internalinfodev@extremenetworks.com.
Multicast
10
Navigating the ExtremeXOS User Guide

This guide consists of the following eight volumes that contain feature descriptions, conceptual
material, configuration details, command references and examples:
Basic Switch Operation
Policies and Security
Layer 2 Basics
Layer 2 Protocols
Layer 3 Basics
Layer 3 Unicast Protocols
Multicast
Advanced Features
Multicast
11
1 Multicast Routing and Switching

Multicast Routing Overview
Multicast Table Management
PIM Overview
IGMP Overview
Configuring EAPS Support for Multicast Traffic
Configuring IP Multicast Routing
Multicast VLAN Registration
Displaying Multicast Information
Troubleshooting PIM
This chapter introduces the features and usage of IP multicasting, which allows a single host on a
network to send a packet to a group of hosts. For more information on IP multicasting, refer to the
following publications:
RFC 1112Host Extension for IP Multicasting
RFC 2236Internet Group Management Protocol, Version 2
RFC 3569SSM for IPv4/IPv6 (only for IPv4)
PIM-SM Version 2draft-ietf-pim-sm--v2-new-05
RFC 4601PIM SM (only for IPv4)
PIM-SM for IPv4/IPv6 (only for IPv4)
RFC 2362 PIM-SM (Edge Mode)
RFC 3973 PIM-DM (only for IPv4)
RFC 3569draft-ietf-ssm-arch-06.txt PIM-SSM PIM Source Specific Multicast
PIM-DM Draft IETF Dense Modedraft-ieft-idmr-pimdm-05.txt, draft-ieft-pim-dm-new-v2-04.txt
RFC 3376Internet Group Management Protocol, Version 3
The following URL points to the website for the IETF PIM Working Group: www.ietf.org/html.charters/
pim-charter.html.
Multicast Routing Overview

Multicast routing and switching is the functionality of a network that allows a single host (the multicast
server) to send a packet to a group of hosts. With multicast, the server is not forced to duplicate and
send enough packets for all the hosts in a group. Instead, multicast allows the network to duplicate
packets for allof the hosts in a group. Multicast greatly reduces the bandwidth required to send data to
a group of hosts. IP multicast routing is a function that allows multicast traffic to be forwarded from
one subnet to another across a routing domain.
IP multicast routing requires the following functions:
A router that can forward IP multicast packets
Multicast
12
Multicast Routing and Switching
A router-to-router multicast routing protocol (for example, Protocol Independent Multicast (PIM))
to discover multicast routes
A method for the IP host to communicate its multicast group membership to a router (for example,
Internet Group Management Protocol (IGMP))
Note
You should configure IP unicast routing before you configure IP multicast routing.
Multicast Table Management

The ExtremeXOS software uses the following tables to support IP multicast traffic:
IPv4 multicast route table
L3 hash table
IP multicast group table
FDB table (L2 table)
L2 multicast table (L2MC table)
IP Multicast Hardware Lookup Modes

Extreme platforms support various hardware forwarding lookup modes by using a combination of L3
hash table and L2 (FDB) table. Refer to Multicast Table Management for details on these tables. The
scalability limits vary based on the lookup mode used.
Configuration Options
Configuration options allow you to choose the hardware forwarding lookup mode for multicast
forwarding. Here is a list of options:
source-group-vlan -- Uses L3 hash table with S,G,V lookup. This is the default mode for all platforms
except the Summit X430.
group-vlan -- Uses L3 hash table with *,G,V lookup.
mac-vlan -- Uses L2 table with DMAC, VLAN lookup. This is the default mode for x430.
mixed-mode -- Uses both L2 and L3 tables for multicast. In this mode, the following logic is applied
on installing the cache entries in the hardware:
Multicast cache entries requiring forwarding across VLANs would be installed in the L3 IP
multicast table. This includes PIM, MVR, and PVLAN cache entries.
Multicast cache entries requiring L2 forwarding within a VLAN are installed in the L2 table. This
includes entries corresponding to IGMP Snooping, PIM snooping, and MLD snooping.
Any IPv4/v6 reserved multicast addresses (for example, 224.0.0.x or IPv6 equivalent) are
installed in the L3 IP multicast table as needed. These reserved addresses map to the following
Multicast
13
multicast MAC addresses: 01:00:5e:00:00:xx, 33:33:00:00:00:xx, 33:33:00:00:01:xx, or

33:33:ff:xx:xx:xx.
Note
Any change in the lookup key configuration causes all cache entries to be cleared, and
traffic is temorarily dropped until the system re-learns the multicast caches and
associated subscriptions.
Note
mac-vlan mode helps increase scaling and is particularly useful on platforms like the
Summit X440, which has limited L3 hardware table entries. This mode is also supported in
other Summit platforms, and the BlackDiamond8K and BlackDiamond X.
Note
mac-vlan and mixed-mode are not supported prior to ExtremeXOS 15.3.1.
The EXOS multicast process continues to maintain the cache entries as "S,G,V", and interacts with HAL
the same way as today. EXOS hardware abstraction layer (HAL) applies the logic explained above and
installs the cache entries in the appropriate hardware table. If the cache entry needs to be installed in
the L2 multicast table, HAL derives the MAC address based on the standard logic and installs the MAC
entry in the L2 table.
The IP multicast address to MAC address mapping is not validated for the received/forwarded
multicast packets in EXOS to date. If the lookup mode is configured either as "mac-vlan" or "mixedmode", the multicast kernel module is modified to validate this mapping and, if a packet does not use
the standard mapping, the packet is dropped.
IPMC Compression
In order to increase the scaling of multicast entries, EXOS implements a feature called IPMC
compression which allows multiple <S,G,V> (or <*,G,V>) IP multicast FDB entries to utilize the same IP
multicast group table entry when the associated egress port lists are the same. The base IP multicast
compression implementation will be reused for achieving L2 multicast entry reuse. In this case, multiple
<MAC,VLAN> multicast FDB entries can use a single L2MC index if the egress port lists of the cache
entries are the same.
Interactions with Static FDBs
EXOS allows you to create FDB entries for multicast MAC address using the create fdb
<mac_addr> {vlan} vlan_name ports port_list command. These entries also get installed in
the L2 table and use the L2MC table for hardware forwarding. If there is a dynamic <MAC,VLAN> entry
from MCMGR and a static entry from FDB manager, the static entry takes precedence and the dynamic
entry would get deleted in hardware. Compression of L2MC indices is not supported on these types of
entries. Each newly created static multicast FDB will cause the allocation of a new L2MC index.
Interactions with Dynamic FDBs
When IP multicast forwarding entries are utilizing the L2 MAC table, the multicast entries are installed
as static in the hardware L2 table to avoid undesirable interactions with L2 protocol or user
administered FDB flushing. These multicast L2 entries also take precedence over dynamic unicast L2
MAC entries. If there is a hash bucket collision upon inserting an L2 multicast entry, it will replace
another dynamic unicast L2 entry if one exists in the same hash bucket.
Multicast
14
Platforms with External-Tables (TCAM)

The X480 and BD8K xl-series have a large external TCAM that can be used to store MAC FDBs, L3
routes, ACLs, and/or IPMC forwarding entries based on configuration. Only the internal L2 table is used
to store <MAC,VLAN> forwarding entries for IP multicast caches on these platforms due to a hardware
limitation. Additionally, the configure forwarding external-table l2-and-l3-andipmc configuration option, which uses the external TCAM to store <S,G,V> entries, is not compatible
with the "mac-vlan" and "mixed-mode" options of this feature.
Virtual Router Support
Current IPMC cache hardware entries stored as <S,G,V> additionally include the VRID associated with
the ingress virtual router. In this feature, <MAC, VLAN> cache entries are stored in the L2 table which
does not additionally include the VRID. However, user VRs are still supported since the VLAN portion of
the lookup key is unique across all VRs.
IPMC Cache Rate Limiting
Based on the number of cache entries supported on each platform, there is a software cache limiting
implementation present in EXOS multicast. The HAL module informs MCMGR about the supported limit,
MCMGR creates cache entries up to MAX supported limit, and the remaining traffic is dropped in
software.
Supported Platforms
This feature is implemented on all Summit, BD8K, and BDX8 platforms.
Note
The mixed-mode setting is supported on all platforms except: BD8K "e2-series", 8500-G48Te.
Limitations
The following limitations exist for the L2MC table feature:
The "mixed-mode" configuration option is not allowed on platforms using older chipsets. Please see
the "Platforms Supported" section for details.
When the "mixed-mode" configuration option is engaged on BD8K platforms, newly inserted slots
which do not support "mixed-mode" will fail initialization.
On SummitStack, this same condition causes the following log to be displayed repeatedly every 30
seconds:
<HAL.IPv6Mc.Error> Stack slot %d is incompatible with the multicast
forwarding lookup configuration.
Either remove this node from the stack or change the multicast forwarding lookup configuration.
When using the "mac-vlan" configuration option:
PIMv4/V6, MVR features cannot be used.
IGMPv3 should not be used in conjunction with this mode
Private VLAN multicast should not be used.
Issues with IP multicast address to MAC address mapping:
Multicast
15
All IPv4 multicast frames use multicast mac addresses starting with 01:00:5e:xx:xx:xx. The lower
order 23 bits of the IP multicast address is used in the MAC address derivation. As only 23 bits of
MAC addresses are available for mapping layer 3 IP multicast addresses to layer 2 MAC addresses,
this mapping results in 32:1 address ambiguity.
When traffic is received for 1 out of these 32 overlapping address, then the MAC, Vlan entry is
installed in hardware based on the IGMP group membership of received traffics destination
multicast IP address. After this installation, traffic to any of the remaining 31 addresses is delivered
based on the existing cache entry and the actual receiver list of the remaining 31 addresses will not
be honored.
IPv6 multicast streams use multicast MAC addresses in the form 33:33:xx:xx:xx:xx. The lower 24 bits
of the IPv6 multicast address are used to derive the MAC address. So, the address ambiguity issue is
also applicable to IPv6 with more severity. Given this condition, we do not recommend using
overlapping IP multicast addresses with this mode.
This limitation applies to "mixed-mode", too.

IPv4 multicast addresses consist of a block of addresses (224.0.0.x) used for network control traffic.
Packets having IP destination addresses from the LNCB are always flooded to all ports of the VLAN.
The address ambiguity issue discussed above is applicable for the addresses in this block too. For
example, 224.0.0.5 (address used for OSPF) and 225.0.0.5 would use the same MAC address
01:00:5e:00:00:05. If a mac based multicast FDB entry is installed on the hardware for 01:00:5e:
00:00:05 based on the 225.0.0.5 join list, it would break OSPF functionality. Hence, MAC addresses
mapping to the LNCB block will not be installed in the L2 table, resulting in software forwarding for
those streams. We recommend that you avoid useing multicast addresses that map to the 01:00:5e:
00:00:xx MAC address range.
As per RFC 3307, IANA assigned reserved IPv6 multicast addresses could be in the group Id range
of 0x00000001 to 0x3FFFFFFF. As a result, EXOS switches flood traffic addressed to ff02::/98 to
all ports of the VLAN. Since the lower 32 bits of IPv6 multicast addresses are mapped to the
multicast mac address, not installing all of the addresses in this range would make it too restrictive.
So, installing entries for 33:33:00:00:00:xx in hardware would be avoided, and the traffic would be
software forwarded.
In addition, the following important IPv6 multicast addresses cannot be installed as hardware
forwarding entries:
DHCP: All-dhcp-agents address FF02:0:0:0:0:0:1:2
All-dhcp-servers address FF05:0:0:0:0:0:1:3
Neighbor Discovery (ND): Solicited-node-address FF02::1:FF00:0000/104
Therefore, the following multicast MAC addresses are not programmed in hardware, and the
corresponding packets are handled in slowpath: 33:33:00:00:01:xx , 33:33:ff:xx:xx:xx
Multicast
Given the issues with IP multicast address to MAC address mapping, no attempt is made to merge
subscriber lists of multiple overlapping IP groups.
The following limitation regarding IPMC compression is also applicable for this feature, because this
feature uses the same L2MC entry for multiple l2 multicast entries with same egress ports. All MACVLAN forwarding entries utilizing the same L2MC entry will be subject to a single BD8K backplane
link (12Gbps).
16
On those platforms supporting the "external-table" (X480, BD8K "xl-series"), any IP multicast
caches installed in the L2 table will be only installed in the internal L2 table due to a hardware
limitation which prevents L2MC access from the ESM (External Search Machine).
When IP multicast forwarding entries are installed as <MAC,VLAN>, IGMP or MLD packets which
have a MAC-DA=<group> will cause the refresh of the IP multicast cache, preventing timely entry
age-out.
The L2MC table is limited to 1K entries on all platforms. This means that only up to 1K unique port
lists can be addressed from the <MAC,VLAN> IP multicast forwarding entries that are stored in the
L2 table. Additionally, statically created multicast FDB entries do not perform L2MC index
compression.
IPv4 Multicast Route Table

Beginning with Release 12.1, all IP multicast routes are stored and maintained in the software multicast
route table. Routes are added to the multicast route table from the following sources:
Multicast static routes (configured manually by the network administrator)
Multicast dynamic routes (learned through protocols such as MBGP and MISIS)
The multicast route table is used for reverse path forwarding (RPF) checks, not for packet forwarding.
The switch uses RPF checks to avoid multicast forwarding loops. When a multicast packet is received,
the switch does an RPF lookup, which checks the routing tables to see if the packet arrived on the
interface on which the router would send a packet to the source. The switch forwards only those
packets that arrive on the interface specified for the source in the routing tables.
The RPF lookup uses the multicast routing table first, and if no entry is found for the source IP address,
the RPF lookup uses the unicast routing table.
Note
Because the multicast routing table is used only for RPF checks (and not for routing), IP route
compression and ECMP do not apply to multicast routes in the multicast routing table.
Beginning with ExtremeXOS software version 12.1, the route metric is no longer used to select
between multicast and unicast routes. If the RPF lookup finds a route in the multicast table,
that route is used. The unicast routing table is used only when no route is found in the
multicast table.
The advantage to having separate routing tables for unicast and multicast traffic is that the two types
of traffic can be separated, using different paths through the network.
L3 Hash Table
The L3 hash table is introduced in Introduction to Hardware Forwarding Tables. The L3 hash table
stores entries for IPv4 routes, IPv4 and IPv6 hosts, and IPv4 and IPv6 multicast groups. For multicast,
L3 hash table supports <S,G,V> and <*,G,V> lookups. The entry from this table provides an index to IP
Multicast Group table.
To make more space available in the L3 hash table for IPv4 and IPv6 multicast groups, you can do the
following:
Multicast
17
Configure the extended IPv4 host cache feature to move IPv4 local and remote routes to the LPM
table as described in Extended IPv4 Host Cache.
Configure BlackDiamond 8900 xl-series modules or Summit X480 series switches to do one of the
following:
Move IPv4 local and remote hosts to the external LPM table.
Move IPv6 local hosts to the external LPM table.
Move IPv4 local and remote hosts to the external LPM table and support IPv4 multicast entries in
the external LPM table.
For more information, see the description for the configure forwarding external-tables command.
Note
To benefit from the use of the external LPM tables, you must leave the IP multicast
compression feature enabled, which is the default setting.
IP Multicast Group Table

The IP multicast group table specifies the egress ports for Layer 2 and Layer 3 multicast traffic groups.
To make more space available in the IP multicast group table, you can do the following:
Leave IP multicast compression enabled (it is enabled by default). This allows multiple L3 hash
entries to share the same IP multicast group entry if the the egress list is the same.
Use the following I/O modules, which provide higher capacity tables:
BlackDiamond 8900 xl-series modules
BlackDiamond 8900-G96T-c
Capacity Restrictions for Mixed Installations

A mixed installation is a switch configuration that contains I/O modules with different table sizes. The
actual IP multicast group table capacity for the switch is set to that supported on the I/O module with
the smallest tables. To increase the capacity of IP multicast tables, all I/O modules must support the
minimum table size you want.
Multicast forwarding entries are programmed in all I/O modules. Only multicast traffic ingressing a
given I/O module utilize these forwarding entries. Other egress-only I/O modules only require the
multicast group table entry.
If you add a higher-capacity I/O module to a switch that has been running with lower capacity
modules, the switch generates a message and adjusts the table capacity on the higher-capacity card to
that of the lower-capacity card.
Compared to the L3 hash table that uses an IP address for forwarding, the L2 table uses a MAC address.
The L2 table stores unicast and multicast MAC entries, and it supports <DMAC, VLAN> lookup. The
entry from this table provides an index to the L2MC table that specifies the egress ports.
Multicast
18
PIM Overview
Protocol Independent Multicast (PIM) is the de-facto standard for routing multicast traffic over the
Internet. Other multicast routing protocols such as DVMRP and MOSPF are sometimes used in
controlled environment, but are not widely deployed. PIM does not depend on a particular unicast
routing protocol for its operation. Also, it does not have any mechanism of its own for route discovery.
PIM operation is based on the routing table being populated by another routing protocol, or by the
user. This provides flexibility in routing unicast and multicast traffic based on a common database.
PIM has two flavors, sparse and dense mode, that are deployed in different topologies. These two
flavors, called PIM-SM and PIM-DM, are different in operation. PIM-SM is based on a "join protocol",
where traffic is not forwarded on a segment unless an explicit request originates (typically through
IGMP) from the network segment. PIM-DM is based on a "flood and prune" mechanism, where every
one receives traffic until they explicitly inform (through the PIM-DM prune mechanism) that they do not
want that particular stream. Thus, PIM-DM is typically deployed in topologies where listeners are
densely populated. And PIM-SM is typically deployed where the receivers are sparsely populated over
the network, so that most of the network segments bandwidth is conserved.
You can configure dense mode or sparse mode on a per-interface basis. After they are enabled, some
interfaces can run dense mode, while others run sparse mode. The switch supports both dense mode
and sparse mode operation.
The switch also supports PIM snooping.
PIM Edge Mode

PIM Edge Mode is a subset of PIM that operates with the following restrictions:
The switch does not act as a candidate rendezvous point (CRP).
The switch does not act as a candidate bootstrap router (CBSR).
At most, four active PIM-SM interfaces are permitted. There is no restriction on the number of
passive interfaces (within the limit of the maximum IP interfaces).
Only PIM Sparse Mode (PIM-SM) is supported.
Note
This feature is supported at and above the license level listed for this feature in the license
tables in the Feature License Requirements document.
Active PIM interfaces can have other PIM enabled routers on them. Passive interfaces should only have
hosts sourcing or receiving multicast traffic. If another PIM router is connected to a multi-access VLAN
then passive mode should not be enabled for that respective VLAN. OSPF passive mode should not be
enabled for a VLAN when a PIM neighbor is present.
PIM Dense Mode

Protocol-Independent Multicast - Dense Mode (PIM-DM) is a multicast routing protocol. PIM densemode is a flood and prune-based protocol. Convergence is based on the downstream routers' response
for the traffic received. The downstream router in turn floods the traffic to its own downstream
interfaces. Each router sends prune to the interface on which it received the traffic under the following
conditions:
Multicast
19
Traffic was not received on RPF interface towards the source.

The PIM router is a leaf router, and there are no IGMP/MLD members.
All the downstream PIM routers have pruned the stream, and there are no IGMP/MLD members.
A new feature, called PIM-DM state refresh, creates two PIM-DM operating modes, which are described
in the following sections:
Note
For additional information on PIM-DM, see RFC 3973, Protocol Independent Multicast - Dense
Mode (PIM-DM): Protocol Specification.
PIM-DM Without State Refresh
PIM-DM is a broadcast and prune protocol, which means that multicast servers initially broadcast traffic
to all destinations, and then switches later prune paths on which there are no receivers. The following
figure shows a dense mode multicast tree with an active branch and a pruned branch.
Figure 1: PIM-DM Operation

In the previous figure, multicast traffic is flowing from VLAN V1 connected to switch S1. S1 floods
multicast traffic to both neighbors S2 and S3 which in turn flood multicast traffic to S4 and S5. S4 has
IGMP members, so it floods multicast traffic down to VLAN V6. S5, which has no multicast members,
sends a prune upstream towards the source. The green line shows the flow of traffic on the active
branch, and the red line shows the prune sent upstream for the pruned branch. After outgoing interface
V2 is pruned from the multicast tree, subsequent multicast traffic from S1 flows only through S2 and S4
and is not forwarded to S3.
After S3 sends a prune upstream, S3 starts a prune hold time timer on outgoing interface V5. When this
timer expires, S3 adds V5 back to the multicast egress list and sends a graft upstream to pull multicast
traffic down again. When multicast traffic arrives from S1, it is forwarded to S5, which repeats the
upstream prune message because it still has no members. This prune, time-out, and flood process
repeats as long as the traffic flow exists and no members are on the pruned branch, and this process
consumes bandwidth during every cycle.
Note
Multicast
20
PIM-DM routers perform reverse path multicasting (RPM). However, instead of exchanging its own
unicast route tables for the RPM algorithm, PIM-DM uses the existing unicast routing table for the
reverse path. As a result, PIM-DM requires less system memory.
PIM-DM with State Refresh
The PIM-DM State Refresh feature keeps the PIM-DM prune state from timing out by periodically
sending a state refresh control message down the source tree. These control messages reset the prune
hold time timer on each pruned interface and prevent the bandwidth waste that occurs with each
prune, time-out, and flood cycle.
When a topology change occurs, the PIM-DM State Refresh feature improves network convergence.
For example, suppose that an S, G entry on S5 in the following figure is removed due to non-availability
of a route. Without PIM-DM State Refresh, multicast traffic is blocked for minutes (due to a time-out on
the upstream routers). In the meantime if an IGMP member or a PIM-DM neighbor joins S5, there is no
way to pull traffic down immediately because S5 does not have any S, G information. State refresh
control messages solve this problem by indicating S, G state information periodically to all downstream
routers. When S5 receives a state refresh from S3, it scans the S, G information and all pending requests
from PIM-DM neighbors and IGMP members. If there are pending requests for the group in the state
refresh message, S5 can immediately send a graft message upstream to circumvent the upstream
timers and pull multicast traffic to its members and neighbors.
To enable, configure, and disable the PIM-DM State Refresh feature, use the following commands:
configure pim state-refresh {vlan} [vlanname | all] [on | off]
configure pim state-refresh timer origination-interval interval
configure pim state-refresh timer source-active-timer interval
configure pim state-refresh ttl ttlvalue
PIM Sparse Mode

Unlike PIM-DM, Protocol-Independent Multicast - Sparse Mode (PIM-SM) is an explicit join and prune
protocol, which means that multicast receivers, and the routers that support them, must join multicast
groups before they receive multicast traffic. When all receivers on a network branch leave a multicast
group, that branch is pruned so that the multicast traffic does not continue to consume bandwidth on
that branch. PIM-SM supports shared trees as well as shortest path trees (SPTs). PIM-SM is beneficial
for large networks that have group members that are sparsely distributed.
Note
Using PIM-SM, the router sends a join message to the rendezvous point (RP). The RP is a central
multicast router that is responsible for receiving and distributing the initial multicast packets. You can
configure a dynamic or static RP.
When a router has a multicast packet to distribute, it encapsulates the packet in a unicast message and
sends it to the RP. The RP decapsulates the multicast packet and distributes it among all member
routers.
Multicast
21
When a router determines that the multicast rate has exceeded a configured threshold, that router can
send an explicit join to the originating router. When this occurs, the receiving router gets the multicast
directly from the sending router and bypasses the RP.
Note
You can run either PIM-DM or PIM-SM per virtual LAN (VLAN).
PIM Mode Interoperation

An Extreme Networks switch can function as a PIM multicast border router (PMBR). A PMBR integrates
PIM-SM and PIM-DM traffic.
When forwarding PIM-DM traffic into a PIM-SM network, the PMBR acts as a virtual first hop and
encapsulates the initial traffic for the RP. The PMBR forwards PIM-DM multicast packets to the RP,
which, in turn, forwards the packets to those routers that have joined the multicast group.
The PMBR also forwards PIM-SM traffic to a PIM-DM network, based on the (*.*.RP) entry. The PMBR
sends a (*.*.RP) join message to the RP, and the PMBR forwards traffic from the RP into the PIM-DM
network.
No commands are required to enable PIM mode interoperation. PIM mode interoperation is
automatically enabled when a dense mode interface and a sparse mode interface are enabled on the
same switch.
PIM Source Specific Multicast

PIM-SM works well in many-to-many multicasting situations. For example, in video conferencing, each
participating site multicasts a stream that is sent to all the other participating sites. However, PIM-SM is
overly complex for one-to-many multicast situations, such as multimedia content distribution or
streaming stock quotes. In these and similar applications, the listener is silent and can know the source
of the multicast in advance, or can obtain it. In these situations, there is no need to join an RP, as the
join request can be made directly towards the source.
Note
Note
(*;G)s are created for groups inside the SSM range. SSM is not enabled for the ingress VLAN.
PIM Source Specific Multicast (PIM-SSM) is a special case of PIM-SM, in which a host explicitly sends a
request to receive a stream from a specific source, rather than from any source.
Multicast
22
IGMPv3 hosts can use PIM SSM directly, because the ability to request a stream from a specific source
first became available with IGMPv3. The PIM-SSM capable router interprets the IGMPv3 message to
initiate a PIM-SM join towards the source.
Note
IGMPv1 and IGMPv2 hosts can use PIM SSM if IGMP-SSM mapping is enabled and configured
on the ExtremeXOS switch. For more information, see Using IGMP-SSM Mapping.
The following table describes PIM-SSM behavior while sending IGMPV3 joins in the SSM range and
outside the SSM range for IPv4:
Table 3: Using PIM-SSM While Sending IGMPV3 Joins (IPv4)
ExtremeXOS 15.4
ExtremeXOS 15.5
SSM
Enabled
SSM range Mode
Include Src Action
Observation
No
Yes
Incl
Yes
Send IGMPv3
join in SSM
range
-the group is Send IGMPv3

learned -(*;G) join in SSM
is not created range
-the group is
learned - (*;G)
is created
No
Yes
Incl
Yes
Send IGMPv3
out of SSM
range
-the group is
learned -no
(*;G) is
created
Send IGMPv3
out of SSM
range
-the group is
learned - (*;G)
is created
No
Yes
Excl
No
Send IGMPv3
join in SSM
range

not learned
join in SSM
(PD4-3138792 range
131) -no (*;G)
is created
-the group is
not learned
(PD4-3138792
131) -no (*;G)
is created
No
Yes
Excl
No
Send IGMPv3
join out of
SSM range

learned - (*;G) join out of
is created
SSM range
-the group is
learned - (*;G)
is created
No
Yes
Excl
Yes
Send IGMPv3
join in SSM
range
-the group is
not learned no (*;G) is
created
Send IGMPv3
join in SSM
range
-the group is
created
No
Yes
Excl
Yes
Send IGMPv3
join out SSM
range
-the group is
learned -no
(*;G) is
created
Send IGMPv3
join out SSM
range
-the group is
learned -no
(*;G) is
created
No
No
Incl
Yes
Send IGMPv3
join
-the group is
learned -no
(*;G) is
created
Send IGMPv3
join
-the group is
learned -(*;G)
is created
No
No
Excl
No
Send IGMPv3
join
-the group is
learnt - (*;G)
is created
Send IGMPv3
join
-the group is
learnt - (*;G)
is created
No
No
Excl
Yes
Send IGMPv3
join
-the group is
learned -no
(*;G) is
created
Send IGMPv3
join
-the group is
learned -no
(*;G) is
created
Multicast
Action
Observation
23
Table 3: Using PIM-SSM While Sending IGMPV3 Joins (IPv4) (continued)

ExtremeXOS 15.4
ExtremeXOS 15.5
SSM
Enabled
SSM range Mode
Include Src Action
Observation
Action
Yes
Yes
Incl
Yes
Send IGMPv3
join in SSM
range

learned -(S;G) join in SSM
is created
range
-the group is
learned -(S;G)
is created
Yes
Yes
Incl
Yes
Send IGMPv3
out of SSM
range
-the group is
learned -no
(*;G) is
created
Send IGMPv3
out of SSM
range
-the group is
learned - (*;G)
is created
Yes
Yes
Excl
No
Send IGMPv3
join in SSM
range
-the group is
created
Send IGMPv3
join in SSM
range
-the group is
created
Yes
Yes
Excl
No
Send IGMPv3
join out of
SSM range

learned - (*;G) join out of
is created
SSM range
-the group is
learned - (*;G)
is created
Yes
Yes
Excl
Yes
Send IGMPv3
join in SSM
range
-the group is
created
Send IGMPv3
join in SSM
range
-the group is
created
Yes
Yes
Excl
Yes
Send IGMPv3
join out SSM
range
-the group is
learned -no
(*;G) is
created
Send IGMPv3
join out SSM
range
-the group is
learned -no
(*;G) is
created
Yes
No
Incl
Yes
Send IGMPv3
join
-the group is
learned -no
(*;G) is
created
Send IGMPv3
join
-the group is
learned -(*;G)
is created
Yes
No
Excl
No
Send IGMPv3
join

learned - (*;G) join
is created
-the group is
learned - (*;G)
is created
Yes
No
Excl
Yes
Send IGMPv3
join
-the group is
learned -no
(*;G) is
created
-the group is
learned -no
(*;G) is
created
Send IGMPv3
join
Observation
The following table describes PIM-SSM behavior while sending MLDV2 joins in the SSM range and
outside the SSM range for IPv6:
Multicast
24
Table 4: Using PIM-SSM While Sending MLDV2 Joins (IPv6)

ExtremeXOS
15.4
ExtremeXOS
15.5
SSM
Enabled
SSM range Mode
Include Src Action
Observation
Action
Observation
No
Yes
Incl
Yes
Send MLDv2
join in SSM
range
-the group is
learned - no
(*;G) is
created
Send MLDv2
join in SSM
range
-the group is
learned -(*;G)
is created
No
Yes
Incl
Yes
Send MLDv2
out of SSM
range
-the group is
learned - no
(*;G) is
created (S;G) is
created
Send MLDv2
out of SSM
range
-the group is
learned -(*;G)
is created
No
Yes
Excl
No
Send MLDv2
join in SSM
range
-the group is Send MLDv2

is created
range
-the group is
created
No
Yes
Excl
No
Send MLDv2
join out of
SSM range

learned -(*;G) join out of
is created
SSM range
-the group is
learned -(*;G)
is created
No
Yes
Excl
Yes
Send MLDv2
join in SSM
range

is created
range
-the group is
created
No
Yes
Excl
Yes
Send MLDv2
join out SSM
range

learned -(*;G) join out SSM
is created
range
-the group is
learned -(*;G)
is created
No
No
Incl
Yes
Send MLDv2
join
-the group is
learned (S;G) is
created
Send MLDv2
join
-the group is
learned - (*;G)
is created
No
No
Excl
No
Send MLDv2
join

learned -(*;G) join
is created
-the group is
learned -(*;G)
is created
No
No
Excl
Yes
Send MLDv2
join

learned -(*;G) join
is created
-the group is
learned -(*;G)
is created
Yes
Yes
Incl
Yes
Send MLDv2
join in SSM
range
-the group is
learned (S;G) is
created
Send MLDv2
join in SSM
range
-the group is
learned (S;G) is
created
Yes
Yes
Incl
Yes
Send MLDv2
out of SSM
range
-the group is
learned - no
(*;G) is
created (S;G) is
created
Send MLDv2
out of SSM
range
-the group is
learned -(*;G)
is created
Multicast
25
Table 4: Using PIM-SSM While Sending MLDV2 Joins (IPv6) (continued)

ExtremeXOS
15.4
ExtremeXOS
15.5
SSM
Enabled
SSM range Mode
Include Src Action
Observation
Action
Observation
Yes
Yes
Excl
No
Send MLDv2
join in SSM
range

is created
range
-the group is
created
Yes
Yes
Excl
No
Send MLDv2
join out of
SSM range

learned -(*;G) join out of
is created
SSM range
-the group is
learned -(*;G)
is created
Yes
Yes
Excl
Yes
Send MLDv2
join in SSM
range

is created
range
-the group is
created
Yes
Yes
Excl
Yes
Send MLDv2
join out SSM
range

learned -(*;G) join out SSM
is created
range
-the group is
learned -(*;G)
is created
Yes
No
Incl
Yes
Send MLDv2
join
-the group is
learned (S;G) is
created
Send MLDv2
join
-the group is
learned - (*;G)
is created
Yes
No
Excl
No
Send MLDv2
join

learned -(*;G) join
is created
-the group is
learned -(*;G)
is created
Yes
No
Excl
Yes
Send MLDv2
join

learned -(*;G) join
is created
-the group is
learned -(*;G)
is created
PIM-SSM has the following advantages:
No overhead of switching to the source-specific tree and waiting for the first packet to arrive
No need to learn and maintain an RP
Fewer states to maintain on each router
No need for the complex register mechanism from the source to the RP
Better security, as each stream is forwarded from sources known in advance
PIM-SSM has the following requirements:
Any host that participates directly in PIM-SSM must use IGMPv3.

To support IGMPv1 and IGMPv2 hosts, IGMP-SSM mapping must be enabled and configured.
PIM-SSM is designed as a subset of PIM-SM and all messages are compliant with PIM-SM. PIM-SSM and
PIM-SM can coexist in a PIM network; only the last hop router need to be configured for PIM-SSM if
both source and receivers are present all the time. However, to avoid any JOIN delay, it is
recommended that you enable all routers along the (s,g) path for PIM-SSM.
Multicast
26
Configuring the PIM-SSM Address Range

A range of multicast addresses is used for PIM-SSM. Within that address range, non-IGMPv3 messages
are ignored, and any IGMPv3 exclude messages are ignored. These messages are ignored for all router
interfaces, even those not configured for PIM-SSM. By default there is no PIM-SSM range specified on
the router. If you choose the default keyword in the CLI when specifying the PIM-SSM range, you
configure the range 232.0.0.0/8. You can also choose to specify a different range for PIM-SSM by using
a policy file.
To configure the PIM-SSM address range, use the following command:
configure pim ssm range [default | policy policy-name]
PIM Snooping
PIM snooping provides a solution for handling multicast traffic on a shared media network more
efficiently. In networks where routers are connected to a L2 switch, multicast traffic is essentially
treated as broadcast traffic (see the following figure).
Figure 2: Multicast Without PIM Snooping

IGMP snooping does not solve this flooding issue when routers are connected to a L2 switch. Switch
ports are flooded with multicast packets. PIM snooping addresses this flooding behavior by efficiently
replicating multicast traffic only onto ports which routers advertise the PIM join requests (see the
following figure).
Multicast
27
Figure 3: Multicast With PIM Snooping

PIM snooping does not require PIM to be enabled. However, IGMP snooping must be disabled on
VLANs that use PIM snooping. PIM snooping and MVR cannot be enabled on the same VLAN.
To enable PIM snooping on one or all VLANs, use the following command: enable pim snooping
{{vlan} name}
To disable PIM snooping on one or all VLANs, use the following command: disable pim snooping
{{vlan} name}
Note
PIM snooping can be enabled only between PIM SM enabled switches. It should not enabled
between PIM DM enabled switches.
PIM Register Policy

This feature allows you to filter register messages based on the policy file configured at the First Hop
Router (FHR) and Rendezvous Point (RP) in PIM-SM domain. You can use the register policy to filter
out specific PIM register messages that have encapsulated specific (S,G) packets. This feature allows
you to detect and deny malicious multicast packets from flowing into a multicast shared tree, and
causing a potential service blackout. The PIM Register Policy feature is supported in both the PIM IPV4
and PIM IPV6 mode .
Filtering at FHR
Multicast
FHR receives the source multicast packet and sends a register message towards the RP. Before it
sends the register message to the RP, the FHR checks the configured register filter policy. If the
28
(S,G) is denied by the policy, the register will not send a message to the RP. The FHR adds the L3
entries to stop the packet from arriving at the CPU. An EMS message is logged.
The FHR checks the register policy before generating a NULL register packet. If the policy is denied
by the filter then the NULL register is not sent to the RP.
If the caches Group is in the SSM range, or is received in the PIM dense circuit, then this filtering is
not applicable. The cache miss packet will go thru the normal processing.
If a non-SSM (S,G) cache already exists but is denied by the filter policy, then (S,G) cache is
removed. The cache miss comes to the CPU for register processing if the traffic is still flowing.
The PIM filtering policy is configured at the FHR using the configure pim {ipv4 | ipv6}
register-policy [policy | none] command.
Filtering at RP
When an encapsulated PIM register packet or PIM NULL register is received by the RP, and is denied
by the registering filter policy, the register message is discarded. Additionally, no (S,G) cache is
created in the PIM cache.
The register drop counter is incremented, and the EMS message is logged.
If a register is received from the MSDP, it also goes through the RP filtering policy.
The PIM filtering policy is configured at RP using the following command: configure pim {ipv4 |
ipv6} register-policy rp [rp_policy_name | none]
PIM DR Priority
The DR_Priority option allows a network administrator to give preference to a particular router in the
DR election process by giving it a numerically larger DR Priority. The DR_Priority option is included in
every Hello message, even if no DR Priority is explicitly configured on that interface. This is necessary
because priority-based DR election is only enabled when all neighbors on an interface advertise that
they are capable of using the DR_Priority Option. The default priority is 1.
DR Priority is a 32-bit unsigned number, and the numerically larger priority is always preferred. A
router's idea of the current DR on an interface can change when a PIM Hello message is received, when
a neighbor times out, or when a router's own DR Priority changes. If the router becomes the DR or
ceases to be the DR, this will normally cause the DR Register state machine to change state.
Subsequent actions are determined by that state machine.
The DR election process on the interface consists of the following:
If any one of the neighbors on the interface is not advertised, the DR priority (not DR capable) will
not considered for the all the neighbors in the circuit and the primary IP address will be considered
for all the neighbors.
Higher DR priority or higher primary address will be elected as DR.
Use the following command to configure PIM DR Priority: configure pim {ipv4 | ipv6} [{vlan}
vlan_name] dr-priority priority
Multicast
29
PIM ECMP Load Splitting

The PIM ECMP feature allows downstream PIM routers to choose multiple ECMP paths to source via
hash from one of following selections without affecting existing unicast routing algorithm:
Source
Group
Source-Group
Source-Group-Next Hop
This feature operates on a per (S,G) basis splitting the load onto available equal-cost paths by hashing
according to the selection criteria configured by the user. It does not operate by counting the flows.
Load splitting need not balance the traffic on the available paths. PIM ECMP load splitting uses a hash
algorithm based on the selected criteria to pick up the path to use and will result in load-sharing the
traffic when there are many multicast streams that utilize approximately the same amount of
bandwidth.
PIM ECMP Load Splitting Based on Source Address
When you enable PIM ECMP load splitting based on source address, the RPF interface for each (*, G) or
(S,G) state is selected among the equal cost paths based on the hash derived from the source address.
For an (S, G) state, the address considered for hashing is the source address of the state. For a (*, G)
state, the address considered for hashing is the address of the RP that is associated with the states
group address. There is no randomization applied when calculating the hash value. The same hash
value is generated on all the EXOS routers for a given source address. If there are two equal cost paths
("left" and "right") available at the last hop router and at each of the intermediate routers for a given
source, each of these routers pick the same hash, and the traffic flows can get skewed (to either "left"
or "right" paths).
PIM ECMP Load Splitting Based on Group Address
When you enable PIM ECMP load splitting based on group address, the RPF interface for each (*, G) or
(S,G) state is selected among the equal cost paths based on the hash derived from the group address.
If multiple equal cost common paths exist to the multicast source and the RP that is associated with the
states group address, the same hash will be chosen for both (*, G) and (S, G) states as the same group
address is used in deriving the hash. There is no randomization applied when calculating the hash value.
The same hash value is generated on all the EXOS routers for a given group address. If there are two
equal cost paths ("left" and "right") available at the last hop router and at each of the intermediate
routers for a given group, each of these routers pick the same hash and the traffic flows can get
skewed (to either "left" or "right" paths).
PIM ECMP Load Splitting Based on Source-Group Addresses
When you enable PIM ECMP load splitting based on source-group address, the RPF interface for each
(*, G) or (S,G) state is selected among the equal cost paths based on the hash derived from the source
and group addresses. For an (S, G) state, the address considered for hashing is the source address of
the state. For a (*, G) state, the address considered for hashing is the address of the RP that is
associated with the states group address. There is no randomization applied when calculating the hash
value. The same hash value is generated on all the EXOS routers for a given source-group address. If
there are two equal cost paths ("left" and "right") available at the last hop router and at each of the
intermediate routers for a given source-group, each of these routers pick the same hash and the traffic
flows can get skewed (to either "left" or "right" paths).
Multicast
30
PIM ECMP Load Splitting Based on Source-Group-Next Hop Addresses

When you enable PIM ECMP load splitting based on source-group-next hop address, the RPF interface
for each (*, G) or (S,G) state is selected among the equal cost paths based on the hash derived from the
source, group and next hop addresses. The hash value derived after introducing the next hop address is
still predictable as there is no randomization applied when calculating the hash value. However, since
the next hop address used at each of the routers vary, the hash value generated on each of the EXOS
routers is different. As the hash value is different on each of the routers, the problem of traffic path
skew present in the above mentioned schemes does not exist in this scheme.
Reconvergence Due to Unicast Routing Changes
When a unicast route to a source or RP address changes (when a path goes down or a new path
becomes available), all the (*, G) and (S, G) states change based on the available unicast route
information provided by Route Manager process. If one of the paths goes down and comes back up,
multicast forwarding will reconverge to same RPF path that was used before the path went down. The
hash function based on Source-Group-Next Hop avoids skewing of traffic flows because it introduces
the actual next-hop IP address of PIM neighbors into the calculation resulting in different hash value
being computed for each router. The Source-Group-Next Hop based hash function doesnt take the
total number of available paths into consideration and so it increases stability of the paths chosen
during path failures. During path failures, the multicast states that were using the failed path would
need to reconverge onto the remaining paths. All other states using the unaffected paths are not
affected.
Limitations
Cannot be used along with static multicast routes.

Not supported for ExtremeXOS Multicast Tools (mtrace and mrinfo) in current release.
Load splitting is not applied for configured static multicast routes and multicast routes present in
the multicast routing table.
Load splitting is only effective when the equal cost paths are upstream PIM neighbors on different
interfaces. When the equal cost paths are PIM neighbors on the same shared VLAN, PIM assert
mechanism chooses one path to avoid traffic duplication. The path chosen by PIM assert mechanism
overrides the path selected by Multicast ECMP load splitting.
IPv6 Specific Features

Apart from adding support for IPv6 addresses, PIMv6 adds the following functionality to existing PIM
implementation:
Secondary address list - This is a new option which will be added to the V6 Hello messages sent.
The list includes all addresses assigned to an interface, including the link local addresses. The
receiving router must process these addresses and must associate the same with the neighbor that
sent the message.
Tunnel interface - This is similar to a VLAN interface. APIs are now added to get callbacks from
VLAN manager client for IP address configuration for a tunnel, etc.
Secondary address list
The Address List Option, in a Hello message, advertises all the secondary addresses associated with the
source interface of the router originating the message. These addresses are associated with the
Multicast
31
neighbor, and are used to compute the neighbors primary address. The function NBR uses information
gathered through PIM Hello messages to map the IP address A of a directly connected PIM neighbor on
interface I to the primary IP address of the same router. The primary IP address of a neighbor is the
address that it uses as the source of its PIM Hello messages.
Tunnel interfaces
Two PIMv6 domains can be connected through an IPv4 network. In this case, PIMv6 routers across the
domains communicate over the IPv4 network by tunneling the IPv6 packets inside IPv4 headers. To
enable such communication, PIMv6 provides support for Tunnel interfaces.
The following tunnel types are supported:
6-in-4
6-to-4
Configuration details
PIMv6 is incorporated into all CLI commands that currently support the PIM implementation. New
keywords are added to support IPv6, and show command output is modified to display IPv6 related
information. For specific configuration details, refer to IP Multicast Commands.
IGMP Overview
IGMP is a protocol used by an IP host to register its IP multicast group membership with a router. A
host that intends to receive multicast packets destined for a particular multicast address registers as a
member of that multicast address group. Periodically, the router queries the multicast group to see if
the group is still in use. If the group is still active, a single IP host responds to the query, and group
registration is maintained.
IGMPv2 is enabled by default on the switch, and the ExtremeXOS software supports IGMPv3. However,
the switch can be configured to disable the generation of periodic IGMP query packets. IGMP should be
enabled when the switch is configured to perform IP multicast routing.
IETF standards require that a router accept and process IGMPv2 and IGMPv3 packets only when the
router-alert option is set in received IGMP packets.
By default, the ExtremeXOS software receives and processes all IGMP packets, regardless of the setting
of the router-alert option within a packet. When the switch will be used with third-party switches that
expect IETF compliant behavior, use the following command to manage this feature:
configure igmp router-alert receive-required [on | off] {{vlan} vlan_name}
configure igmp router-alert transmit [on | off] {{vlan} vlan_name}
By default, IGMP report/leave message for the local multicast address (224.0.0.x/24 groups) will
always have the router-alert option set, regardless of IGMP router-alert transmit option (on and off)
setting by the user.
IGMPv3, specified in RFC 3376, adds support for source filtering. Source filtering is the ability for a
system to report interest in receiving packets only from specific source addresses (filter mode include)
Multicast
32
or from all sources except for specific addresses (filter mode exclude). IGMPv3 is designed to be
interoperable with IGMPv1 and IGMPv2.
Note
The ExtremeXOS software supports IGMPv3 source include mode filtering, but it does not
support IGMPv3 specific source exclude mode filtering.
Note
It is not possible for the BlackDiamond X8 and Summit X670 series switches to have ICMP/
IGMP code and type fields on egress. ICMP/IGMP type requires UDF (user defined fields).
Ingress Pipeline has UDF but Egress pipeline hardware does not have UDF. So it cannot
match ICMP/IGMP types on egress pipeline.
IGMP Snooping
IGMP snooping is a Layer 2 function of the switch; it does not require multicast routing to be enabled. In
IGMP snooping, the Layer 2 switch keeps track of IGMP reports and only forwards multicast traffic to
that part of the local network that requires it. IGMP snooping optimizes the use of network bandwidth
and prevents multicast traffic from being flooded to parts of the local network that do not need it. The
switch does not reduce any IP multicast traffic in the local multicast domain (224.0.0.x).
IGMP snooping is enabled by default on all VLANs and VMANs in the switch. If IGMP snooping is
disabled on a VLAN or VMAN, all IGMP and IP multicast traffic floods within the VLAN or VMAN. IGMP
snooping expects at least one device on every VLAN to periodically generate IGMP query messages.
To enable or disable IGMP snooping, use the following command:
enable igmp snooping {forward-mcrouter-only | {vlan} name | with-proxy vr vrname}
disable igmp snooping {forward-mcrouter-only | {vlan} name | with-proxy vr
vrname}
Note
IGMP snooping is not supported on SVLANs on any platform.
The IGMP snooping proxy feature represented by "with-proxy" in the above commands is enabled by
default. This feature optimizes the forwarding of IGMPv1 and IGMPv2 reports. The following is true for
each group:
Only the first received IGMP join is forwarded upstream.
Only the IGMP leave for last host is forwarded upstream.
When a switch receives an IGMP leave message on a port, it sends a group-specific query on that port if
proxy is enabled (even if it is a non-querier). The switch removes the port from the group after leave
timeout (The timeout value is configurable, with a default value of 1000 ms., and a range from 0 to
175000 ms). If all the ports are removed from the group, the group is deleted and the IGMP leave is
Multicast
33
forwarded upstream. If IGMP snooping proxy is disabled, then all the IGMP reports are forwarded
upstream.
Note
IGMP snooping proxy does not apply to IGMPv3 reports.
IGMP snooping is implemented primarily through ACLs, which are processed on the interfaces. These
special purpose ACLs are called IGMP snooping hardware filters. On Summit family switches and
BlackDiamond 8800 series switches, the software allows you to choose between two types of IGMP
snooping hardware filters: per-port filters (the default) and per-VLAN filters.
The two types of IGMP snooping hardware filters use switch hardware resources in different ways. The
two primary hardware resources to consider when selecting the IGMP snooping hardware filters are the
Layer 3 multicast forwarding table, and the interface ACLs. The size of both of these hardware
resources is determined by the switch model. In general, the per-port filters consume more resources
from the multicast table and less resources from the ACL table. The per-VLAN filters consume less
space from the multicast table, and more from the ACL table.
In Summit family switches and BlackDiamond 8800 series switches, using the per-port filters can fill up
the multicast table and place an extra load on the CPU. To avoid this, configure the switch to use the
per-VLAN filters.
Note
The impact of the per-VLAN filters on the ACL table increases with the number of VLANs
configured on the switch. If you have a large number of configured VLANs, we suggest that
you use the per-port filters.
IGMP Snooping Filters

IGMP snooping filters allow you to configure a policy file on a port to allow or deny IGMP report and
leave packets coming into the port. (For details on creating policy files, see Policy Manager.) The IGMP
snooping filter feature is supported by IGMPv2 and IGMPv3.
Note
Do not confuse IGMP snooping filters with IGMP snooping hardware filters explained in
previous section. IGMP snooping filters are software filters, and the action is applied at the
software level by the ExtremeXOS multicast manager.
For the policies used as IGMP snooping filters, all the entries should be IP address type entries, and the
IP address of each entry must be in the class-D multicast address space but should not be in the
multicast control subnet range (224.0.0.x/24).
1
Use the following template to create a snooping filter policy file that denies IGMP report and leave
packets for the 239.11.0.0/16 and 239.10.10.4/32 multicast groups:
#
# Add your group addresses between "Start" and "end"
# Do not touch the rest of the file!!!!
entry igmpFilter {
if match any {
#------------------ Start of group addresses ------------------
Multicast
34
nlri 239.11.0.0/16;
nlri 239.10.10.4/32;
#------------------- end of group addresses ------------------} then {
deny;
}
}
entry catch_all {
if {
} then {
permit;
}
}
2 After you create a policy file, use the following command to associate the policy file and filter to a
set of ports:
configure igmp snooping vlan vlanname ports portlist filter [policy | none]
3 To remove the filter, use the none option.

4 To display the IGMP snooping filters, use the following command:
show igmp snooping {vlan} name filter
Static IGMP
To receive multicast traffic, a host must explicitly join a multicast group by sending an IGMP report;
then, the traffic is forwarded to that host. In some situations, you might like multicast traffic to be
forwarded to a port where a multicast-enabled host is not available (for example, when you test
multicast configurations).
Static IGMP emulates a host or router attached to a switch port, so that multicast traffic is forwarded to
that port, and the switch sends a proxy join for all the statically configured IGMP groups when an IGMP
query is received. You can emulate a host to forward a particular multicast group to a port; and you
may emulate a router to forward all multicast groups to a port. Static IGMP is only available with
IGMPv2.
To emulate a host on a port, use the following command:

configure igmp snooping {vlan} vlan_name {ports port_list}add static group
ip_address
To emulate a multicast router on a port, use the following command:

configure igmp snooping {vlan} vlan_name {ports port_list}add staticrouter
To remove these entries, use the corresponding commands:

configure igmp snooping {vlan} vlan_name {ports port_list }deletestatic group
[ip_address | all]
configure igmp snooping vlan vlan_name {portsport_list } deletestatic router
To display the IGMP snooping static groups, use the following command:
show igmp snooping {vlan} vlan_name static [group | router]
IGMP Loopback
Prior to ExtremeXOS 15.3.2, you could configure static groups, but it was necessary to specify port(s).
As of ExtremeXOS Release 15.3.2, the configuration of dynamic groups is supported. The IGMP
Multicast
35
Loopback feature, along with the existing static group feature, supports the configuration of static
and/or dynamic groups with or without ports.
A VLAN in loopback mode may not have ports associated with it, but its operational status is up.
However, it is not possible to have multicast receivers on a VLAN without having a port. Sometimes
there is a need to pull the multicast traffic from upstream to the loopback VLAN for troubleshooting.
The traffic need not always be forwarded to any ports/receivers. The IGMP Loopback feature allows
you to configure groups on a VLAN without specifying a port, so the traffic is pulled from upstream but
not forwarded to any port.
The loopback (Lpbk) port is the logical port on a VLAN in the application context. If you configure a
group on a VLAN but do not specify the port, the switch forms an IGMPv2 join and assumes it to be
received on the Lpbk port. A dynamic group ages out after the membership timeout if there are no
other receivers. Membership joins refresh the dynamic group. The static group remains until it is
removed from the configuration.
Limiting the Number of Multicast Sessions on a Port
The default configuration places no limit on the number of multicast sessions on each VLAN port. To
place a limit on the number of learned IGMP groups, use the following command:
configure igmp snooping {vlan} vlanname ports portlist set join-limit {num}
To remove a session limit, use the following command:

unconfigure igmp snooping {vlan} vlanname ports portlist set join-limit
Enabling and Disabling IGMP Snooping Fast Leave

When the fast leave feature is enabled and the last host leaves a multicast group, the router
immediately removes the port from the multicast group. The router does not query the port for other
members of the multicast group before removing the group, and/or the port.
The default setting for IGMP snooping fast leave is disabled.
To enable the fast leave feature, use the following command:

enable igmp snooping {vlan} name fast-leave
To disable the fast leave feature, use the following command:

disable igmp snooping {vlan} name fast-leave
IGMP-SSM Mapping
The IGMP-SSM Mapping feature allows IGMPv1 and IGMPv2 hosts to participate in SSM functionality,
and eliminates the need for IGMPv3. You can configure SSM map entries that specify the sources used
for a group/group range for which SSM functionality has to be applied. You also have the option to
configure the domain name and DNS server to use to obtain the source list.
When a IGMPv1 or IGMPv2 report is received, the configured sources are provided to PIM so that it can
send source specific joins. When the host leaves or when the membership times out, PIM is informed so
that it can consider sending prunes.
Multicast
36
In a multi-access network (where more than one router is receiving IGMP messages from the hosts),
only the designated router sends joins towards the source, so it is desirable to have same configuration
for SSM group range and SSM Mapping range on all routers in a VLAN.
Limitations
PIM must be disabled on a switch to configure IGMP-SSM mapping.

A single group address or range can be mapped to a maximum of 50 sources. If more than 50
sources are configured, the switch uses the 50 longest-matching prefixes.
We recommend a maximum of 500 mappings per switch, but no limit is imposed by the software.
Configuring IGMP-SSM Mapping

To support PIM-SSM for IGMPv1 and IGMPv2 clients, a PIM-SSM range must be configured, and that
range should include all groups to which the clients want access. If IGMPv1 and IGMPv2 clients request
group addresses outside the PIM-SSM range, those addresses are ignored by PIM-SSM and forwarded
to PIM as (*, G) requests.
To enable IGMP-SSM mapping, first configure a PIM-SSM range, and then enable IGMP-SSM
mapping using the following commands:
configure pim ssm range [default | policy policy-name]
enable igmp ssm-map {vr vr-name}
To configure an IGMP-SSM mapping, use the following command:

configure igmp ssm-map add group_ip [prefix | mask] [source_ip |
src_domain_name] {vr vr-name}
To remove a single IGMP-SSM mapping, use the following command:

configure igmp ssm-map delete group_ip [ prefix} | mask] [source_ip | all] vr
vr-name }
To remove all IGMP-SSM mappings on a virtual router, use the following command:
unconfigure igmp ssm-map {vr vr-name}
To disable IGMP-SSM mapping on a virtual router, use the following command:

disable igmp ssm-map {vr vr-name}
Displaying IGMP-SSM Mappings

To see whether or not IGMP-SSM mapping is enabled or disabled and to view the configured mappings
for a multicast IP address, use the following command:
show igmp ssm-map {group_ip} {vr vr-name}
Configuring EAPS Support for Multicast Traffic

The ExtremeXOS software provides several commands for configuring how EAPS supports multicast
traffic after an EAPS topology change. For more information, see the descriptions for the following
commands:
configure eaps multicast add-ring-ports [on | off]
configure eaps multicast send-query [on | off]
Multicast
37
configure eaps multicast temporary-flooding [on | off]
These commands apply for both IGMP and MLD.

Note
Using the configure eaps multicast send-query command applies to both IGMP and
MLD. This also replaces the configure eaps multicast send-igmp-query command.
Configuring IP Multicast Routing

Enabling Multicast Forwarding
To enable IP multicast forwarding:
1 Configure the system for IP unicast routing.
2 Enable multicast forwarding on the interface.
enable ipmcforwarding {vlan name}
Configuring PIM
To configure PIM multicast routing, enable multicast forwarding as described in Enabling Multicast
Forwarding on page 38 and do the following:
1
Configure PIM on all IP multicast routing interfaces using the following command:
configure pim {ipv4 | ipv6} add vlan [vlan-name | all] {dense | sparse}
{passive}
2 To enable and configure the PIM-DM state refresh feature on one or all VLANs, use the following
commands:
configure pim {ipv4 | ipv6} state-refresh {vlan} [vlan_name | all] [on | off]
configure pim {ipv4 | ipv6} state-refresh timer source-active-timer interval
configure pim {ipv4 | ipv6} state-refresh ttl ttlvalue
3 For PIM-SSM, specify the PIM-SSM range, enable IGMPv3, and enable PIM-SSM on the interfaces
using the following commands:
configure pim {ipv4 | ipv6} ssm range [default | policy policy-name]
enable igmp {vlan vlan name } {IGMPv1 | IGMPv2 | IGMPv3}
enable pim {ipv4 | ipv6} ssm vlan [vlan_name | all]
4 Enable PIM on the router using the following command:

enable pim
Multicast
38
Configuring Multicast Static Routes

Note
Multicast static routes are supported in the IPv4 address family, but not the IPv6 address
family.
Static routes are used to reach networks not advertised by routers, and are manually entered into the
routing table.
You can use either of two commands to create multicast static routes. The recommended command
is the following:
configure iproute add [ipNetmask | ip_addr mask] gateway {metric} {multicast |
multicast-only | unicast | unicast-only} {vr vrname}
For example:
configure iproute add 55.1.10.0/24 44.1.12.33 multicast
The following command is still supported for backward compatibility with earlier ExtremeXOS
software releases:
configure ipmroute add [source-net mask-len | source-net mask] {{protocol}
protocol} rpf-address {metric} {vr vr-name}
In the following example, the configure ipmroute add command is used to specify protocol
information for a route:
configure ipmroute add 58.1.10.0/24 ospf 44.1.12.33
When a static route is configured with protocol information, the route is shown as UP only when the
protocol route is available. Otherwise, the route is Down. In the example above, the multicast static
route 58.1.10.0/24 is shown as UP only when the OSPF route is available to reach the network
58.1.10.0/24.
Static routes are stored in the switch configuration and can be viewed with the show configuration
command. Static multicast routes that do not include protocol information are displayed using the
configure iproute command format, even if they were created using the configure ipmroute
command. Static routes that are created with a protocol field are displayed using the configure
ipmroute command format.
Disabling IP Multicast Compression

The IP multicast compression feature is available only on Summit family switches and BlackDiamond
8000 series modules, and is enabled by default. You should only disable this feature if you suspect that
switch processing resources are limited or if you think this feature is causing problems on the switch.
To disable or enable IP multicast compression, use the following command:

configure forwarding ipmc compression {group-table | off}
Multicast Over MLAG Configuration

Consider the following sample topology for MLAG:
Multicast
39
DUT-1(core lic)======ISC vlan========DUT-2(core lic)

||
+----------------DUT-3(edge lic)---------------+
DUT-1 and DUT-2 are MLAG peers, DUT-3 is a L2 switch whose uplink is a LAG up to the pair of MLAG
switches.
RP and BSR can be configured on same device along with MLAG config but we recommend to keep
RP node away from MLAG peers. One MLAG peer will be Designated Router(DR) and another one
will be elected as NON-DR for MLAG vlan. DR node will send *,G and try to pull the traffic from RP
and Non-DR wont be pull the traffic until DR is alive. If you config RP on Non-DR node then both
MLAG peers will pull the traffic which will trigger the assert to avoid the traffic duplication. It is not
recommended to setup RP on any vlan on MLAG peers.
It is best to avoid the assert operation since a small amount of traffic duplication happens during the
this operation. You can avoid assert in some, but not all the scenarios.
DR priority configuration will help to make RP node as DR. (The DR priority feature is available from
ExtremeXOS15.3.2 release onwards).
It is recommended that for PIM-SM deployments that the RP is configured on loopback VLANs
instead of regular VLANs. This ensures continuous connectivity to the RP needing active ports
present in that respective VLAN.
PIM Configuration Examples

PIM-DM Configuration Example
In the following figure, the system labeled IR 1 is configured for IP multicast routing, using PIM-DM.
Multicast
40
Figure 4: IP Multicast Routing Using PIM-DM Configuration Example

Note
The above figure is used in the OSPF chapter to describe the Open Shortest Path First
(OSPF) configuration on a switch. See the Layer 3 Unicast Protocols volume of the
ExtremeXOS User Guide for more information about configuring OSPF.
The router labeled IR1 has the following configuration:
configure vlan HQ_10_0_1 ipaddress 10.0.1.2 255.255.255.0
configure ospf add vlan all area 0.0.0.0
enable ipforwarding
enable ospf
enable ipmcforwarding
configure pim add vlan all dense
enable pim
configure pim state-refresh vlan all on
PIM-SM Configuration Example

In the following figure, the system labeled ABR1 is configured for IP multicast routing using PIM-SM.
Multicast
41
Figure 5: IP Multicast Routing Using PIM-SM Configuration Example

Note
The above figure is used in the OSPF chapter to describe the Open Shortest Path First
(OSPF) configuration on a switch. See the Layer 3 Unicast Protocols volume of the
ExtremeXOS User Guide for more information about configuring OSPF.
The router labeled ABR1 has the following configuration:
configure vlan LA_161_48_2 ipaddress 161.48.2.2 255.255.255.0
configure vlan CHI_160_26_26 ipaddress 160.26.26.1 255.255.255.0
configure ospf add vlan all area 0.0.0.0
enable ipforwarding
configure pim add vlan all sparse
tftp TFTP_SERV -g -r rp_list.pol
configure pim crp HQ_10_0_3 rp_list 30
configure pim cbsr HQ_10_0_3 30
The policy file, rp_list.pol, contains the list of multicast group addresses serviced by this RP. This set of
group addresses are advertised as candidate RPs. Each router then elects the common RP for a group
address based on a common algorithm. This group to RP mapping should be consistent on all routers.
Multicast
42
The following is a policy file that configures the CRP for the address ranges 239.0.0.0/24 and
232.144.27.0:
entry extreme1 {
if match any {
}
then {
nlri 239.0.0.0/24 ;
nlri 232.144.27.0/24 ;
}
}
PIM-SSM Configuration Example

In the following example, the default PIM-SSM range of 232.0.0.0/8 is configured. For all interfaces,
non-IGMPv3 messages and IGMPv3 exclude messages are ignored for addresses in this range. Hosts
that use IGMPv3 on VLAN v13 can request and receive source specific multicast streams for addresses
in the PIM-SSM range.
create vlan v12
create vlan v13
configure v12 add port 1
configure v13 add port 2
configure v12 ipaddress 12.1.1.1/24
configure v13 ipaddress 11.1.1.1/24
configure pim add vlan all sparse
enable ipforwarding
enable igmp IGMPv3
configure pim ssm range default
enable pim ssm vlan v13
enable pim
Note
(*;G)s are created for groups inside the SSM range. SSM is not enabled for the ingress vlan.
PIM Snooping Configuration Example
The following figure shows a network configuration that supports PIM snooping.
Multicast
43
Figure 6: PIM Snooping Configuration Example

In the figure above, Layer 3 switches S2, S3, S4, and S5 are connected using the Layer 2 switch S1
through the VLAN comm_vlan. Switches S3, S4, and S5 are multicast capable switches, and switch S2 is
a non-multicast capable switch, which has no multicast routing protocol running.
Without PIM snooping, any ingress multicast data traffic on comm_vlan is flooded to all the switches,
including switch S2, which does not support multicast traffic. IGMP snooping does not reduce flooding
because it floods the multicast traffic to all router ports.
The network design calls for most multicast traffic to egress switch S5. PIM snooping helps by
intercepting the PIM joins received from the downstream routers and forwarding multicast traffic only
to those ports that received PIM joins.
Switch S1 (PIM Snooping Switch) Configuration Commands
The following is an example configuration for the PIM snooping switch S1:
create vlan comm_vlan
configure vlan comm_vlan add port 1,2,3,4
disable igmp snooping
disable igmp_snooping comm_vlan
enable pim snooping
enable pim snooping comm_vlan
Switch S3 Configuration Commands
The following is an example configuration for switch S3, which also serves as an RP:
configure vlan comm_vlan add port 1
configure comm_vlan ipa 10.172.168.4/24
enable ipforwarding comm_vlan
enable ipmcforwarding comm._vlan
configure pim add vlan comm_vlan sparse
configure ospf add vlan comm._vlan area 0.0.0.0
create vlan sender_vlan
configure vlan sender_vlan add port 2
configure sender_vlan ipa 10.172.169.4/24
Multicast
44

configure pim add vlan comm._vlan sparse
configure ospf add vlan comm_vlan area 0.0.0.0
enable pim
enable ospf
configure pim crp static 10.172.169.4 pim_policy // RP is configured using
the policy pim_policy for the group 224.0.0.0/4
The following is an example configuration for switch S5, which serves as the last hop router for
multicast traffic:
create vlan receiver_vlan
configure vlan sender_vlan add port 1
configure sender_vlan ipa 10.172.170.4/24
configure pim add vlan comm._vlan sparse
configure ospf add vlan comm_vlan area 0.0.0.0
enable pim
enable ospf
The following is an example configuration for switch S4, which is neither an LHR nor a RP:
enable pim
enable ospf
Multicast
45
The following is an example configuration for switch S2, which is not enabled for PIM:
enable ospf
PIM Snooping Example Configuration Displays
After the example configuration is complete, multicast receivers connect to the network through switch
S5 and multicast sources connect through switch S3.
When switch S5 receives an IGMP request from the receiver_vlan for group 225.1.1.1, it sends a PIM (*, G)
join towards switch S3, which is the RP. The PIM snooping feature on switch S1 snoops the (*, G) join,
and the resulting entry can be viewed by entering the following command at switch S1:
# show pim snooping vlan comm_vlan
PIM Snooping
ENABLED
Vlan comm_vlan(3971)
Snooping ENABLED
Source
Group
RP
UpPort
DownPort
HoldTime
*
225.1.1.1
10.172.169.4
1
2
15
210
Neighbor IP
DR
Port
Age
Hold Time
10.1272.168.4
YES
1
2
105
10.1272.168.2
NO
2
2
105
10.1272.168.3
NO
3
2
105
Age
Once multicast traffic arrives from the sender_vlan, the LHR (switch S2) sends the (S, G) join message,
which is snooped by the PIM snooping switch, switch S1. The resulting entries can be viewed by
entering the following command at switch S1:
# show pim snooping vlan comm_vlan
PIM Snooping
ENABLED
Vlan comm_vlan(3971)
Snooping ENABLED
Source
Group
RP
UpPort
DownPort
HoldTime
*
225.1.1.1
10.172.169.4
1
2
15
210
10.172.169.10 225.1.1.1
10.172.169.4
1
2
15
210
Neighbor IP
DR
Port
Age
Hold Time
10.1272.168.4
YES
1
2
105
10.1272.168.2
NO
2
2
105
10.1272.168.3
NO
3
2
105
Age
Multicast traffic is forwarded only to those ports that have received (*, G) or (S, G) joins and designated
router (DR) ports.
Multicast
46
Multicast VLAN Registration

Multicast VLAN Registration (MVR) is designed to support distributing multicast streams for IPTV to
subscribers over a Layer 2 network. In a standard Layer 2 network, a multicast stream received on a
VLAN is not forwarded to another VLAN. The streams are confined to the Layer 2 broadcast domain. In
an IGMP snooping environment, streams are forwarded only to interested hosts on a VLAN. For interVLAN forwarding (routing) a multicast routing protocol, such as PIM/DVMRP must be deployed.
MVR breaks this basic rule, so that a stream received over Layer 2 VLANs is forwarded to another
VLAN, eliminating the need for a Layer 3 routing protocol. It simplifies the multicast stream distribution
and is a better solution for IPTV-like services. With MVR, a multicast stream is forwarded to all VLANs
containing interested hosts.
Figure 7: Standard VLAN Compared to an MVR VLAN

In the above figure, the left side shows a standard VLAN carrying a multicast stream.
The host H1 receives the multicast stream because it resides on VLAN Vlan1, but host H2 does not
receive the multicast traffic because no IP multicast routing protocol forwards the stream to VLAN
Vlan2. On the right side of the figure, H2 does receive the multicast stream. Because Vlan1 was
configured as an MVR VLAN, the multicast stream is forwarded to the other VLANs on the switch.
containing hosts that have requested the stream. To configure a VLAN as an MVR VLAN, use the
following command: configure mvr add vlan vlan-name
Typically, IGMP snooping is enabled, so only hosts that have requested a stream can see the multicast
traffic. For example, another host on VLAN2 cannot receive the traffic unless it has sent an IGMP
request to be included in the group.
Notice that only VLAN1 is MVR enabled. Configure MVR only on the ingress VLAN. To enable MVR on
the switch, use the following command: enable mvr
Note
MVR is not supported on the Summit X430.
Basic MVR Deployment

Because MVR is primarily targeted for IPTV and similar applications, a basic deployment for that
application is shown in the following figure. In the figure, an IPTV server is connected through a router
to a network of switches. Switch 1 has three customer VLANs, Vlan2, Vlan3, and Vlan4. The multicast
Multicast
47
streams are delivered through the network core (Metro Ethernets), which often use a ring topology and
some kind of redundant protection to provide high availability. For example, McastVlan forms a ring
through switches Switch1 through Switch4. The link from Switch2 to Switch4 is shown as blocked, as it
would be if some form of protection (such as EAPS) is used.
Figure 8: Basic MVR Deployment

Without MVR, there are two ways to distribute multicast streams in this topology:
Extend subscriber VLANs (Vlan2, Vlan3, and Vlan4) to the network core, by tagging the ports
connecting the switches.
Configure all VLANS with an IP address and run PIM or DVMRP on each switch.
There are problems with both of these approaches. In the first approach, multiple copies of the same
stream (IPTV channel) would be transmitted in the core, wasting bandwidth. In the second approach,
all switches in the network core would have to be Layer 3 multicast aware, and would have to run a
multicast protocol. Typical network cores are Layer 2 only.
MVR provides a simple solution to this problem If McastVlan in Switch1 is configured with MVR, it leaks
the traffic into the local subscriber VLANs that contain hosts that request the traffic. For simple cases,
perform these configuration steps:
Configure MVR on McastVlan.
Configure an IP address and enable IGMP and IGMP snooping on the subscriber VLANs (by default
IGMP and IGMP snooping are enabled on Extreme Networks switches).
For all the multicast streams (IPTV channels), configure static IGMP snooping membership on the
router on McastVlan.
Enable MVR on the switches in the network.
Note
MVR works best with IGMPv1 and IGMPv2. We recommend that you do not use MVR with
IGMPv3.
The strategy above conserves bandwidth in the core and does not require running PIM on the
subscriber switches.
Multicast
48
In this topology, a host (for example, a cable box or desktop PC) joins a channel through an IGMP join
message. Switch1 snoops this message and adds the virtual port to the corresponding cache's egress
list. This is possible because an MVR enabled VLAN can leak traffic to any other VLAN. When the user
switches to another channel, the host sends an IGMP leave for the old channel and a join for the new
channel. The corresponding virtual port is removed from the cache for the old channel and is added to
the cache for the new channel.
As discussed in Static and Dynamic MVR on page 49, McastVlan also proxies IGMP joins learned on
other VLANs to the router. On an MVR network it is not mandatory to have a router to serve the
multicast stream. All that is required is to have a designated IGMP querier on McastVlan. The IPTV
server can also be directly connected to McastVlan.
Static and Dynamic MVR
Static MVR
In a typical IPTV network, there are several high demand basic channels. At any instant there is at least
one viewer for each of these channels (streams), and they should always be available at the core (ring).
When a user requests one of these channels, it is quickly pulled locally from the multicast VLAN. You
have the option to use the static router configuration in each of the switches in the core. But this will
cause all the channels to be available in the core, which may not be desired. For example, on an
Extreme Networks router, you can use the following commands:
configure igmp snooping {vlan} vlan_name
ports port_list add static router
You can use the static MVR configuration and choose the groups for which the multicast stream should
be flooded. If a multicast stream for a group in the static MVR range is received on an MVR enabled
VLAN, it is always flooded on the MVR VLAN. This allows the neighbor switch in the ring to receive all
the static MVR streams.
Dynamic MVR
In contrast, since a video content provider would like to provide a variety of on-demand and other
premium channels, there are often many lower demand (fewer viewers) premium channels that cannot
all be made available simultaneously at the core network. These should be streamed from the router
only if requested by a host.
IGMP is the standard method used by a host to request a stream. However, IGMP packets are
constrained to a VLAN. Thus, subscribers' IGMP join requests on the VLAN cannot be forwarded onto
other VLANS. You can use a dynamic MVR configuration, and choose the groups for which the IGMP
join requests should be proxied over the MVR VLAN. Thus, in Figure 8: Basic MVR Deployment on page
48, McastVlan sends join and leave messages on behalf of Vlan2, Vlan3, and Vlan4. The router receives
the messages on McastVlan and streams corresponding channels onto the core network. This provides
on-demand service, and an administrator does not need to configure static IGMP on the router for each
of these channels.
Configuring Static and Dynamic MVR
By default, all MVR streams are static.

Use the following command to specify which groups are static:
Multicast
49
configure mvr vlan vlan-name static group {policy-name | none}
Any other groups in the MVR address range are dynamic. Use the following command to specify the
MVR address range:
configure mvr vlan vlan-name mvr-address {policy-name | none}
By using these two commands together, you can specify which groups are static and which are
dynamic. If you want all the groups to be dynamic, specify a policy file for the static group
command that denies all multicast addresses.
MVR Configuration Example
The following example configuration is a two DUT scenario, in L2 mode , with no routing protocol or
PIM configured.
DUT-1 is sender
DUT-2 is receiver
VLAN v1 spans over DUT-1 and DUT-2 , DUT-2 also has v2 where IGMP joins are coming IN (225.1.1.1)
DUT-2 has a VLAN v3, which also has a receiver connected sending IGMP join for same group as v2
(225.1.1.1)
VLAN v1 in the DUT-2 has another port apart from the trunk port, no joins are being sent on this
port.
Configure MVR on vlan v1 on DUT-2

* X460-48t.157 # show config "mcmgr"
#
# Module mcmgr configuration.
#
enable mvr vr VR-Default
configure mvr add vlan v1
configure mvr vlan v1 mvr-address none
configure mvr vlan v1 static group none*
*X460-48t.158 #
The traffic will be flooded for the group only on MVR vlan (v1).
Since there are IGMP joins coming in on v2 and v3, v2, v3, and the second port in the MVR vlan v1 will
receive traffic.
Configure the following policy file;
* X460-48t.155 # vi mvrPolicy.polentry policy1 {
if match any {
nlri 225.1.1.1/24;
} then {
permit;
}
}
-------------------------
Multicast
50
When applying this policy file under static group on DUT-2

# configure mvr vlan v1 static group mvrPolicy
#configure mvr vlan v1 mvr-address none
When the policy file contains "permit", the traffic flows to v2, v3, and the second port in MVR VLAN.
When the policy file is changed to "deny", the second port in the MVR VLAN v1 will stop receiving the
traffic.
If you configure static policy (by default permit), traffic for that group range will always be available
in the MVR VLAN, that is, it will be forwarded to all the ports in MVR VLAN.
When applying this policy file under mvr-address (Dynamic) on DUT-2:
# configure mvr vlan v1 static group none
# configure mvr vlan v1 mvr-address mvrPolicy
When the policy file contains "permit", the traffic flows to v2,v3 and the second port in MVR vlan.
When the policy file is changed to "deny", the second port in MVR VLAN v1 continues receiving traffic,
but VLAN v2 and v3 stop receiving traffic, in spite of IGMP groups being learned. This is because the
join on v2 and v3 will not be leaked to MVR VLAN.
Essentially, the dynamic policy does not directly apply on traffic, but it affects the joins, based on which
traffic is forwarded or blocked.
Dynamic means only if the join is sent then traffic is forwarded.
The join is leaked to MVR VLAN so traffic from MVR VLAN will be received by other VLANs (v2 and v3).
To confirm if a join was leaked to MVR VLAN use the show igmp group command. It should have the
group learned on MVR VLAN (v1) with port as "MVR".
MVR Forwarding
The goal for MVR is to limit the multicast traffic in the core Layer 2 network to only the designated
multicast VLAN. If the backbone Layer 2 port is tagged with multiple VLANs, as shown in the following
figure, a set of rules is needed to restrict the multicast streams to only one VLAN in the core.
Figure 9: Multiple VLANs in the Core Network
Multicast
51
In the above figure, the core network has 2 more VLANs, vc1 and vc2, to provide other services. With
MVR, multicast traffic should be confined to McastVlan, and should not be forwarded to vc1 and vc2. It
should be noted that MVR is configured only on the ingress VLAN (McastVlan). MVR is not configured
on any other VLANs.
In the same way as the IGMP snooping forwarding rules, the multicast stream is forwarded onto
member ports and router ports on the VLAN. For a stream received on MVR enabled ports, this rule is
extended to extend membership and router ports to all other VLANs. This rule works well on the
topology in the following figure. However, in a tagged core topology, this rule forwards traffic onto
VLANs, such as vc1 and vc2, on ports PC1 and PC2. This results in multiple copies of same stream on the
core network, thus reintroducing the problem that MVR was intended to solve.
To avoid multiple copies of the same stream, MVR forwards traffic with some special restrictions. MVR
traffic is not forwarded to another VLAN unless a host is detected on the port. On the ingress MVR
VLAN, packets are not duplicated to ports belonging to MVR VLANs. This is to prevent duplicate
multicast traffic streams on ingress ports. Streams belonging to static MVR groups are always
forwarded on MVR VLANs so that any host can join such channels immediately. However, dynamic
groups are streamed from the server only if some host is interested in them. A command is provided to
receive traffic on a port which is excluded by MVR. However, regular IGMP rules still apply to these
ports, so the ports must have a router connected or an IGMP host to receive the stream.
These rules are to prevent multicast packets from leaking into an undesired virtual port, such as p2 on
VLAN pc2 in the following figure. These rules also allow that, in most topologies, MVR can be deployed
with minimal configuration. However, unlike EAPS and STP, MVR is not intended to be a Layer 2
protocol to solve packet looping problems. Since multicast packets leak across VLANs, one can
misconfigure and end up with a multicast storm. MVR does not attempt to solve such problems.
Note
If a port is blocked by Layer 2 protocols, that port is removed from the egress list of the
cache. This is done dynamically per the port state.
For most situations, you do not need to manually configure ports to receive the MVR multicast streams.
But if one of the forwarding rules denies forwarding to a port that requires the streams, you can
manually receive the MVR multicast streams by using the following command:
configure mvr vlan vlan_name add receiver port port-list
Inter-Multicast VLAN Forwarding

In Basic MVR Deployment on page 47, only simple topologies are considered, in which subscribers on
different VLANs access a multicast VLAN. There are topologies where streams need to be forwarded
onto another multicast VLAN, as shown in the following figure. In this figure, a Multicast Service
Provider (MSP) multicast VLAN is attached to ports 1:1-2 on both switches, SW1 and SW2. On the
customer side, another multicast VLAN, delivers multicast streams to other switches around the ring.
Multicast
52
Figure 10: Inter-Multicast VLAN Forwarding

In this topology, a multicast stream can be leaked into the customer multicast network through either
switch SW1 or SW2. However, as described in MVR Forwarding on page 51, packets are not forwarded
to router ports (ports 1:4 and 1:5 can be router ports if SW2 is an IGMP querier). To get around this, MVR
needs to be configured on CustVlan either on SW1 or SW2. Since the forwarding rules apply only to
non-MVR VLANs, traffic from one MVR VLAN is leaked into the router ports of another VLAN, if MVR is
enabled on that.
In the topology above, the MSP multicast VLAN is carried on two switches that also carry the customer
multicast VLAN. When multiple switches carry both multicast VLANs, it is imperative that MVR is
configured on only one switch. Only that switch should be used as the transit point for multicast
streams from one multicast ring into another. Otherwise, duplicate packets are forwarded. Also on the
non-MVR switches, the ring ports should be configured as static router ports, so that ring ports are
excluded from forwarding packets onto the customer ring. There is no mechanism to elect a designated
MVR forwarder, so it must be configured correctly.
MVR Configurations
MVR enables Layer 2 network installations to deliver bandwidth intensive multicast streams. It is
primarily aimed at delivering IPTV over Layer 2 networks, but it is valuable in many existing EAPS or
STP installations. This section explores a few possible deployment scenarios and configuration details.
Of course, real world networks can be lot different from these examples. This section is meant to
present some ideas on how to deploy MVR over existing networks, as well as to design new networks
that support MVR.
MVR with EAPS
Since MVR is designed with a Layer 2 ring topology in mind, it is strongly recommended that it should
be deployed with EAPS. The MVR plus EAPS combination provides a superior solution for any triple
play network, where the service provider intends to provide data, voice, and video services. EAPS is a
proven solution for providing sub-second SONET-like protection to Layer 2 rings. For more detail on
EAPS refer to EAPS.
Consider a typical EAPS topology in the following figure, where 3 VLANs on the core ring serve various
clients on each switch. To provide video service, one of the VLANs on the EAPS ring is designated as a
Multicast
53
multicast VLAN. MVR is enabled only on this VLAN (mcastvlan). V1 is the control VLAN, and V2 is
another protected VLAN. A router serving the multicast feed would typically run PIM on mcastvlan, to
support the static and dynamic IGMP membership on the VLAN.
Figure 11: MVR on an EAPS Ring

The following is a typical configuration for the router and switches.
Router1:
create vlan mcastvlan
configure mcastvlan add port 1:1
create vlan server
configure server add port 1:2
configure mcastvlan ipaddress 10.1.1.1/24
configure server ipaddress 11.1.1.1/24
configure igmp snooping mcastvlan port 1:1 add static group 239.1.1.1
enable ipforwarding
configure igmp snooping leave-timeout 2000
configure pim add vlan all
enable pim
Switch1:
create vlan mcastvlan
create vlan v1
create vlan v2
create vlan vlan2
configure vlan vlan2 add port 1:3
configure vlan vlan2 ipaddress 10.20.1.1/24
configure mcastvlan tag 20
configure mcastvlan add port 1:1,1:2 tag
configure mvr add vlan mcastvlan
configure vlan v1 tag 30
configure v1 add port 1:1,1:2 tag
Multicast
54

create eaps e1
configure eaps
configure eaps
configure eaps
configure eaps
configure eaps
configure eaps
enable eaps
enable mvr
e1 mode transit
e1 add control vlan v1
e1 add protect vlan mcastvlan
e1 add protect vlan v2
port primary port 1:1
port secondary port 1:2
Switch3:
create vlan McastVlan
create vlan v1
create vlan v2
configure mcastvlan tag 20
configure mcastvlan add port 1:2,1:3 tag
configure mcastvlan add port 1:1
configure mvr add vlan mcastvlan
create eaps e1
configure eaps
configure eaps
configure eaps
configure eaps
configure eaps
configure eaps
enable eaps
enable mvr
e1 mode master
e1 add control vlan v1
e1 add protect vlan mcastvlan
e1 add protect vlan v2
port primary port 1:3
port secondary port 1:2
Note
In this example, Switch3 is the EAPS master, but any of the other switches in the ring could
have been configured as the master.
MVR with STP
In a Layer 2 ring topology, MVR works with STP as it works with EAPS. However, in other Layer 2
topologies, additional configuration steps may be needed to make sure that multicast feeds reach all
network segments. Extra configuration is required because all ports in the VLAN are part of an STP
domain, so that solely by examining the configuration it is not clear whether a port is part of bigger ring
or is just serving a few hosts. In EAPS this problem is solved by distinguishing between configured
primary or secondary ports from other VLAN ports. Consider a simplified Layer 2 STP network as
shown in the following figure.
Multicast
55
Figure 12: MVR with STP

In this topology, subscribers are in a Layer 2 cloud on VLAN V1.
STP is configured for all ports of V1. Since V1 spans on the ring as well, multicast cannot be forwarded
on V1 blindly. Forwarding rules (described in MVR Forwarding on page 51), dictate that multicast traffic
is not forwarded on STP enabled ports. This is to make sure that multiple copies of multicast packets
are not forwarded on the ring. However, since other STP enabled ports on V1 (1:3,1:4) are not part of the
ring multicast stream, they need to be configured so that they get the packets. To configure the ports
to receive packets, use the following command (mentioned in MVR Forwarding on page 51):
configure mvr vlan vlan-name add receiver port port-list
Note
If the Layer 2 cloud is connected back to ring ports, traffic may end up leaking into VLAN V1
in the ring. There is no way to avoid that. So, such topologies must be avoided.
The following is a typical configuration for Switch 1 in the above figure:
create vlan v1
configure v1 tag 200
configure v1 add port 1:1, 1:2 tag
configure v1 add port 1:3, 1:4
create vlan mvlan
configure mvlan add port 1:1, 1:2
configure mvr add vlan mvlan
create stpd stp1
configure stp1 add vlan v1 port all
enable stpd stp1 port all
configure mvr vlan v1 add receiver port 1:3,1:4
enable mvr
MVR in a VMAN Environment

In the case of a VMAN, a packet is tagged with a VMAN tag in addition to a possible VLAN tag. This is
to provide VLAN aggregation for all customer traffic in the VMAN ring. Each customer is given its own
VLAN, and traffic from all customers can be tunneled on a single VMAN tag into the metro ring to an
Multicast
56
outside Broadband Remote Access Server (BRAS). In a VMAN network, multicast traffic can be
distributed over a separate VLAN in the metro core. These packets are not subjected to VMAN
tunneling. Thus, IPTV service can be provided on this multicast VLAN on a VMAN network.
MVR deployment in a VMAN environment is not any different from that in an EAPS environment, since
a separate multicast VLAN on the metro ring is used for multicasting. However, it provides interesting
capabilities to MSPs for their video offerings. Different service bundles can be offered on separate
VLANs. Packets are not forwarded to any metro link segments where a stream is not required.
The following figure illustrates an example design for MVR in a VMAN environment. Any multicast
packet entering on MVlan is forwarded on MVlan to the next switch. These multicast packets are not
tunneled.
With MVR, switches on the VMAN do not have to run any routing protocol. If MVR is enabled on the
multicast VLAN, MVlan, traffic is pulled from the IPTV server. Such multicast packets egressing from the
CE port are always untagged. The downstream DSLAM distributes untagged multicast packets to the
respective subscriber VLANs.
Figure 13: MVR in a VMAN Environment

The following is a typical configuration for Switch 1 in the above figure:
create vman vman2
configure vman vman2 tag 300
configure vman vman2 add port 2:2-2:3 untagged
configure vman vman2 add port 1:1,1:2 tagged
enable port 2:*
enable port 1:*
create vlan mvlan
configure vlan mvlan tag 200
configure vlan mvlan add port 1:1,1:2 tag
configure mvr add vlan mvlan
enable mvr
Multicast
57
Displaying Multicast Information

Displaying the Multicast Routing Table
To display part or all of the entries in the multicast routing table, use the following command:
show iproute {ipv4} {{vlan} name | [ipaddress netmask | ipNetmask] | origin
[direct | static | mbgp | imbgp | embgp]} multicast {vr vr_name}
Displaying the Multicast Cache
The multicast cache stores information about multicast groups. To display part or all of the entries in
the multicast cache, use the following command:
show mcast cache {{vlan} vlan_name} {{[group grpaddressMask | grpaddressMask]
{source sourceIP | sourceIP}} {type [snooping | pim | mvr]}| {summary}}
Looking Up a Multicast Route
To look up the multicast route to a specific destination, use the following command with the
multicast option:
rtlookup [ipv4_address | ipv6_address] { unicast | multicast | rpf } {vr
vr_name}
Looking Up the RPF for a Multicast Source
To look up the RPF for a multicast source, use the following command with the rpf option:
rtlookup [ipv4_address | ipv6_address] { unicast | multicast | rpf } {vr
vr_name}
Displaying the PIM Snooping Configuration
To display the PIM snooping configuration for a VLAN, use the following command:
show pim snooping {vlan} vlan_name
Troubleshooting PIM
Multicast Trace Tool
The multicast trace tool is the multicast equivalent of unicast trace route mechanism and is an effective
tool for debugging multicast reachability problems. This tool is based on an IETF draft and uses IGMP.
Because it is harder to trace a multicast path from the source to the destination, a multicast trace is run
from the destination to the source. The multicast trace can be used to do the following:
Locate where a multicast traffic flow stops
Multicast
58
Identify sub-optimal multicast paths
A multicast trace is used for tracing both potential and actual multicast forwarding tree paths. When
the multicast tree is established and traffic is flowing, this tool traces the actual traffic flow. If there is no
traffic while executing the command, this tool displays the potential path for the group and source
being traced.
You can direct a multicast trace to any network destination, which can be a multicast source or
destination, or a node located between a source and destination. After you initiate the trace, a multicast
trace query packet is sent to the last-hop multicast router for the specified destination. The query
packet contains the source address, group address, destination/receiver address, response address,
maximum number of hops, and TTL to be used for the multicast trace response.
The previous hop router selection is based on the multicast routing protocol and the state for the S,G
entry in the processing router.
For example:
If there is no S,G state in the router, the parent closest to the RP is chosen as the previous hop.
If the S,G state exists in the router, the parent closest to the source is chosen as the previous hop.
The last hop router converts the multicast trace query into a unicast traceroute request by appending
response data (for the last hop router) into the received query packet, and the last hop router forwards
the request packet to the router that it believes is the proper previous hop for the given source and
group.
Each multicast router adds its response data to the end of the request packet, and then forwards the
modified unicast request to the previous hop.
The first hop router (the router that determines that packets from the source originate on one of its
directly connected networks) changes the packet type to response packet and sends the completed
response to the query generator. If a router along the multicast route is unable to determine the
forwarding state for a multicast group, that router sends a response back to the originator with NO
ROUTE forwarding code.
To initiate a multicast trace, use the following command:
mtrace source src_address {destination dest_address} {group grp_address} {from
from_address} {gateway gw_address} {timeout seconds} {maximum-hops number}
{router-alert [include | exclude]} {vr vrname}
Multicast Router Information Tool

The multicast router information tool is an ExtremeXOS command that allows you to request
information from a specific multicast router. For more information, see the command description for
the following command:
mrinfo {router_address} {from from_address} {timeout seconds} {multiple-responsetimeout multi_resp_timeout} {vr vrname}
Multicast
59
2 IPv6 Multicast
Multicast Listener Discovery (MLD) Overview
Managing MLD
This chapter introduces IPv6 multicast, which allows a single IPv6 host to send a packet to a group of
IPv6 hosts, and the features and configuration of the Multicast Listener Discovery (MLD) protocol. For
more information on IPv6 multicasting, refer to the following publications:
RFC 2710Multicast Listener Discovery (MLD) for IPv6
RFC 3810Multicast Listener Discovery Version 2 (MLDv2) for IPv6
Multicast Listener Discovery (MLD) Overview

Multicast Listener Discovery (MLD) is a protocol used by an IPv6 host to register its IP multicast group
membership with a router. To receive multicast traffic, a host must explicitly join a multicast group by
sending an MLD report; then, the traffic is forwarded to that host. Periodically, the router queries the
multicast group to see if the group is still in use. If the group is still active, a single IP host responds to
the query, and group registration is maintained.
MLD is the IPv6 equivalent to IGMP, and MLDv1 is equivalent to IGMPv2. The ExtremeXOS software
supports both MLDv1 and MLDv2 protocol.
Note
This release does not support MVR, PVLAN, VLAN Aggregation, and Multicast
Troubleshooting tools for MLD/IPv6.
Managing MLD
Enabling and Disabling MLD on a VLAN
MLD is disabled by default on all VLANs. You can enable MLD using the enable mld {vlan <vlan name>}
{MLDv1 | MLDv2} command.
This allows IPv6 hosts to register with IPv6 multicast groups and receive IPv6 multicast traffic.
Multicast
To disable MLD on a VLAN after it has been enabled, use the disable mld {vlan name}
command.
To enable MLD on a VLAN after it has been disabled, use the enable mld {vlan vlan_name}
{MLDv1 | MLDv2} command.
60
IPv6 Multicast
MLD Snooping
Similar to IGMP snooping, MLD snooping is a Layer 2 function of the switch; it does not require
multicast routing to be enabled. In MLD snooping, the Layer 2 switch keeps track of MLD reports and
only forwards multicast traffic to the part of the local network that requires it. MLD snooping optimizes
the use of network bandwidth and prevents multicast traffic from being flooded to parts of the local
network that do not need it.
MLD snooping is disabled by default on all VLANs in the switch.
When MLD snooping is disabled on a VLAN, all MLD and IPv6 multicast traffic floods within the VLAN.
MLD snooping expects at least one device on every VLAN to periodically generate MLD query
messages.
Enable or disable MLD snooping:

enable mld snooping
disable mld snooping
Multicast packets with a scope id less than 2 are not forwarded by the MLD snooping enabled
switch. Kill entry is installed in the hardware for this traffic.
Multicast packets with a scope id of 2 and group address in the range of FF02::/111 (Addresses
allocated by IANA as per RFC 3307) are always flooded to all ports of the VLAN by hardware and a
copy of the packet is provided to slow path. There are no cache entries in software or hardware for
these addresses.
Multicast packets with a scope id of 2 and group address as solicited multicast address
(FF02::1:FFXX:XXXX/104) are flooded to all ports of VLAN for 135 seconds (Default MLD query
interval + Maximum response time), if there are no members for this group.
Otherwise, the traffic is forwarded based on the snooping database. Multicast cache entries for
these addresses are maintained only in the software and traffic is always slow path forwarded.
Multicast addresses with a scope id of 2 and that do not qualify in the above categories will be
forwarded based on the snooping database.
Cache entries for these multicast addresses will be installed in hardware. Unregistered packets are
dropped.
In general, all multicast data traffic on a PIMv6 enabled VLAN is controlled by the PIMv6 protocol.
However, multicast traffic with either the group address or source address as the link local address
will not be controlled by PIMv6. Instead, it will be L2 forwarded based on the snooping database.
For multicast packets with a scope id greater than 2 on PIMv6 enabled VLANs, cache entries are
controlled by the PIMv6 protocol.
PIMv6 provides a list of egress VLANs for which packets need to be forwarded. The snooping
database is used to construct the set of ports for ingress VLANs as well as for each egress VLAN.
On PIMv6 disabled VLANs, traffic is forwarded based on the snooping database on the ingress
VLAN.
In both cases, cache entry is installed in the hardware, and traffic is fast path forwarded.
Multicast
61
IPv6 Multicast
The MLD snooping proxy feature is enabled automatically when MLD snooping is enabled. This
feature optimizes the forwarding of MLDv1 reports. The following conditions apply for each group:
Only the first received MLD join is forwarded upstream.
Only the MLD leave for last host is forwarded upstream.
When a switch receives an MLD leave message on a port, it sends a group-specific query on that
port if proxy is enabled (even if it is a non-querier). The switch removes the port from the group
after the leave timeout (a configuable value from 0 - 175000ms with a default of 1000ms). If all
the ports are removed from the group, the group is deleted and the MLD leave is forwarded
upstream. If MLD snooping proxy is disabled, then all the MLD reports are forwarded upstream.
Note
MLD snooping proxy does not apply to MLDv2 reports.
MLD snooping is implemented primarily through ACLs, which are processed on the interfaces. These
special purpose ACLs are called MLD snooping hardware filters. On Summit family switches and
BlackDiamond 8800 series switches, the software allows you to choose between two types of MLD
snooping hardware filters: per-port filters (the default) and per-VLAN filters.
The two types of MLD snooping hardware filters use switch hardware resources in different ways.
The two primary hardware resources to consider when selecting the MLD snooping hardware filters
are the Layer 3 multicast forwarding table, and the interface ACLs. The size of both of these
hardware resources is determined by the switch model. In general, the per-port filters consume
more resources from the multicast table and less resource from the ACL table. The per-VLAN filters
consume less space from the multicast table and more from the ACL table.
In Summit family switches and BlackDiamond 8800 series switches, since the multicast table size is
smaller, using the per-port filters can fill up the multicast table and place an extra load on the CPU.
To avoid this, configure the switch to use the per-VLAN filters.
Note
The impact of the per-VLAN filters on the ACL table increases with the number of VLANs
configured on the switch. If you have a large number of configured VLANs, we suggest
that you use the per-port filters.
MLD Snooping Filters

MLD snooping filters allow you to configure a policy file on a port to allow or deny MLD report and
leave packets coming into the port.
(For details on creating policy files, see Policy Manager.) The MLD snooping filter feature is supported
by MLDv1 and MLDv2.
Note
Do not confuse MLD snooping filters with MLD snooping hardware filters explained in
previous section. MLD snooping filters are software filters, and the action is applied at
software level by the ExtremeXOS multicast manager.
For the policies used as MLD snooping filters, all the entries should be IPv6 address type entries, and
the IPv6 address of each entry must not be in the range of FF02::/96.
Multicast
62
IPv6 Multicast
Use the following template to create a snooping filter policy file that denies MLD report and leave
packets for the FF03::1/128 and FF05::1/112 multicast groups:
#
entry mldFilter {
if match any {
#------------------ Start of group addresses -----------------nlri FF03::1/128;
nlri FF05::1/112;
deny;
}
}
entry catch_all {
if {
} then {
permit;
}
}
After you create a policy file, use the following command to associate the policy file and filter to a set of
ports:
configure mld snooping vlan vlan_name ports port_list filter [policy]
To remove the filter, use the none option.

To display the MLD snooping filters, use the following command:
show mld snooping {vlan} name filter
Limiting the Number of Multicast Sessions on a Port

The default configuration places no limit on the number of multicast sessions on each VLAN port. To
place a limit on the number of learned MLD reports, or remove the limit, use the command:
configure mld snooping {vlan} vlan_name ports port_list join-limit [num_joins |
no-limit]
Configuring MLD Snooping
To configure the timers that control MLD operation, use the command:
configure mld query_interval query_response_interval
last_member_query_interval {robustness}
Similar to IGMP snooping, MLD snooping is a Layer 2 function of the switch. It does not require
multicast routing to be enabled. MLD snooping keeps track of MLD reports, and only forwards
multicast traffic to that part of the local network that requires it. MLD snooping is disabled by
default on all VLANs. If MLD snooping is disabled on a VLAN, all MLD and IPv6 multicast traffic
floods within the VLAN. To enable IGMP snooping, use the command:
enable mld snooping {vlan name}
Multicast
63
IPv6 Multicast
Clearing MLD Group Registration

To clear a single group or all groups in a VLAN learned through MLD, use the command:
clear mld group {v6grpipaddress} {{vlan} name}
Configuring Static MLD

In some situations, you might want multicast traffic to be forwarded to a port where a multicastenabled host is not available (for example, when you test multicast configurations). Static MLD
emulates a host or router attached to a switch port, so that multicast traffic is forwarded to that port,
and the switch sends a proxy join for all the statically configured MLD groups when an MLD query is
received. You can emulate a host to forward a particular multicast group to a port; and you may
emulate a router to forward all multicast groups to a port.
To emulate a host on a port, use the command:

configure mld snooping {vlan} vlan_name{ ports port_list } add static
groupv6grpipaddress
To emulate a multicast router on a port, use the command:

configure mld snooping {vlan}vlan_name ports port_list add static router
To remove these entries, use the corresponding commands:

configure mld snooping {vlan} vlan_name {ports port_list } delete static group
[all | v6grpipaddress]
configure mld snooping {vlan} vlan_name ports port_list delete static router
MLD Loopback
Prior to ExtremeXOS 15.3.2, you could configure static groups, but it was necessary to specify port(s).
As of 15.3.2, the configuration of dynamic groups is now supported. The MLD Loopback feature along
with the existing static group feature supports the configuration of static and/or dynamic groups with
or without ports.
A VLAN in loopback mode may not have ports associated with it, but its operational status is up.
However, it is not possible to have multicast receivers on a VLAN without having a port. Sometimes,
there is a need to pull the multicast traffic from upstream to the loopback VLAN for troubleshooting.
The traffic need not always be forwarded to any ports/receivers. The MLD Loopback feature allows you
to configure groups on a VLAN without specifying a port, so the traffic is pulled from upstream but not
forwarded to any port.
The loopback (Lpbk) port is the logical port on a VLAN in the application context. When you configure
a group on a VLAN but do not specify the port, the switch forms an MLDv1 join and assumes it to be
received on the Lpbk port. A dynamic group ages out after the membership timeout if there are no
other receivers. Membership joins refresh the dynamic group. The static group remains until it is
removed from the configuration.
Display MLD Information
To display MLD configuration and operation information, use the command:

show mld group {{vlan} {name} | {v6grpipaddress}} {MLDv2}
Multicast
64
IPv6 Multicast
To display the MLD static group information, use the command:

show igmp snooping {vlan} name static [group | router]
MLD SSM Mapping

The MLD-SSM Mapping feature allows MLDv1 hosts to participate in SSM functionality, and eliminates
the need for MLDv2. You can configure SSM map entries that specify the sources used for a group/
group range for which SSM functionality is applied. You also have the option to configure domain name
and DNS server to use to obtain the source list.
When a MLDV1 report is received, the configured sources are provided to PIM so that it can send source
specific joins. When the host leaves, or when the membership times out, PIM is informed so that it can
consider sending prunes.
Note
The sources mapped to only the LPM group are used.
Feature Implementation Information
This feature is implemented as an extension to existing IGMP SSM support.

The CLI commands for this feature are applicable in VR context.
PIM is completely unaware of existence of this feature, so there is no change in PIM processing.
On last hop the (S, G) cache created through MLDv1 join is similar to the (S, G) cache created as a
result of RPT to SPT switchover in PIM-SM. There is no indication that the cache is created as result
of MLDv1 join, or MLDv2 report.
Limitations
Only 50 sources (static or dynamic) are allowed for each group address, or group range.
Note
The DNS server may send only 15 IPv6 source addresses in its response thereby limiting
the number of dynamic sources supported.
Only one DNS name is allowed for each group address/group range.
SSM Address Range

The address prefix FF3x::/32 is reserved by IANA for SSM use. All SSM addresses must have P=1, T=1
and plen=0. RFC 3306 mandates that the network prefix is zero, which results in the SSM address range
to be in FF3x::/96 range. Since future documents may allow a non-zero network prefix, this feature
allows the addresses in range FF3x::/32 in SSM map configuration. This is the default SSM range.
SSM address range is configured from the PIM context using the following command:
configure pim ipv6 ssm range default | policy policy_name
When this command is issued, PIM notifies MCMGR with the details of the SSM address range. MCMGR
applies this range for the MLD SSM feature.
Multicast
65
IPv6 Multicast
Handling MLD Reports

The following table captures the enhanced functionality.
Table 5: MLD Mapping
MLDv1 Join
MLD SSM Map Disabled
MLD SSM Map Enabled
Group in SSM range but no map

entries
Dropped
Dropped
Group in SSM range with map

entries
Dropped
SSM map sources included
Group not in SSM range
SSM map sources not included
SSM map sources not included
MLDv1 reduction messages in the SSM range are accepted and processed normally. Multicast manager
will send out a group-specific query and refresh the receivers on receiving joins.
When an MLDv2 report is received, following group records types are ignored if they refer to SSM
group range:
MODE_IS_EXCLUDE
CHANGE_TO_EXCLUDE_MODE
Other group records in the same report are processed.

SSM Data Forwarding
L2 forwarding decision of SSM data traffic is taken by the Multicast manager. Sources configured in the
SSM map are considered only when a MLDv1 receiver is connected to a port. For the same group, there
may be another port on which only MLDv2 receiver is present. For this port, SSM map sources are not
considered.
L3 forwarding decision of SSM data traffic is taken by PIM. PIM provides the list of egress VLANs to be
included, and the multicast manager decides the egress ports on each of these VLANs.
DNS Request/Response
When a DNS name is configured for a group in an SSM map, a DNS request is sent to resolve the name.
If static sources are already configured for the group, it takes precedence and the DNS request is not
sent. This feature uses the AAAA record type. For example, if the multicast group is FF30::1234:5678
and the configured domain name is ext.foo.bar, then the DNS request is sent for
8.7.6.5.4.3.2.1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.3.F.F.ext.xxx.xxx.
The DNS request is not sent every time a report is received. A DNS request is sent only in the following
scenarios:
Multicast
When a DNS name is configured for a group.

When the refresh ssm-map command is used.
When the DNS age timer expires.
66
IPv6 Multicast
The DNS response may contain one or more addresses. These addresses are updated to the SSM
mapping table against the specific group.
Note
LPM is used to match the group for a DNS response.
If a static source is configured for a group for which DNS resolved addresses are already present, the
dynamic sources are flushed and the static sources are added. Static mapped addresses are preferred
over DNS resolved addresses.
DNS Timers
The DNS age timer is a decrementing timer to zero and applies to a group/group range. The value of
this timer is calculated by the following formula:
DNS age = (value of TTL in the DNS response) + (wait TTL)
wait TTL = 260 seconds
A DNS request is sent when receiving an MLDv1 report, but the TTL has expired. The source is not
removed until the wait TTL time expires.
On receiving the DNS response, the existing DNS resolved addresses which are not in the DNS
response are removed. Any new addresses in the DNS response are added and the DNS age timer is
refreshed. The L2 SSM data caches are modified for the addresses removed, or added. PIM is notified to
take action on L3 SSM caches.
If the DNS response is not received and the DNS age timer expires, the mapping entry is removed (if
there are no static addresses). The SSM data traffic forwarding is stopped immediately when the group
is removed.
DNS Server
This feature does not check or track DNS servers configured in the switch. You must correctly configure
and administer the DNS server.
The following command is used to configure the DNS server:
configure dns-client add name-server ip_address {vr vr_name
The server(s) are displayed using the following command:

# show dns-client
Number of domain suffixes: 0
Number of domain servers: 1
Name Server 0: 10.120.89.75 VR-Default
MCMGR uses nettools library to perform DNS lookups. gethostbyname_c is used by specifying the
callback function to be invoked when DNS response is received.
Configuring MLD SSM Mapping
Use the following commands to configure MLD SSM Mapping in ExtremeXOS:
Multicast
67
IPv6 Multicast
Enable or disable MLD SSM Mapping on a VR: [enable | disable] mld ssm-map { {vr}
vrname }
Add an MLD SSM Mapping entry on a VR: configure mld ssm-map add v6groupnetmask
[v6sourceip | src_domain_name] { {vr} vrname}
Delete an MLD SSM Mapping entry on a VR:configure mld ssm-map delete v6groupnetmask
[v6sourceip | src_domain_name] { {vr} vrname}
Delete all MLD SSM Mapping entries on a VR: unconfigure mld ssm-map { {vr} vrname}
Send out a DNS request for a particular group. On receiving the DNS response, the "DNS Age" in the
SSM mapping entry is refreshed: refresh mld ssm-map v6groupnetmask { {vr} vrname}
Display the status of MLD-SSM mapping feature on a VR, and display the MLD-SSM mapping
entries: show mld ssm-map { v6groupnetmask } { {vr} vrname }
Configure the DNS server: configure dns-client add name-server ip_address {vr
vr_name}]
Multicast
Display the DNS Servers: show dns-client
68
3 MSDP
MSDP Overview
PIM Border Configuration
MSDP Peers
MSDP Mesh-Groups
Anycast RP
SA Cache
Redundancy
SNMP MIBs
This chapter introduces MSDP (Multicast Source Discovery Protocol), an interdomain multicast protocol
used to connect multiple multicast routing domains that run PIM-SM (Protocol Independent MulticastSparse Mode). This chapter discusses the features and configuration for PIM border, MSDP peers, mesh
groups, anycast RP, SA cache, redundancy, and SNMP MIBs.
Note
For more information about MSDP, refer to RFC 3618.
MSDP Overview
Multicast Source Discovery Protocol (MSDP) is an interdomain multicast protocol used to connect
multiple multicast routing domains that run Protocol Independent Multicast-Sparse Mode (PIM-SM).
MSDP speakers are configured on each PIM-SM domain. These speakers establish a peering relationship
with other MSDP speakers through secured TCP connections. When the source sends traffic, the MSDP
speaker learns about the source through its Rendezvous Point (RP). In turn, the RP advertises the
source to its peers through Source Active (SA) messages. The peers receive these advertisements and
inform their RPs about the presence of the active source in the other PIM-SM domain, which triggers
the normal PIM operation in the corresponding domains.
For example, as businesses expand and networks grow in size, it might become necessary to connect
PIM domains to allow multicast applications to reach other offices across the network. MSDP simplifies
this process by providing a mechanism to connect those multicast routing domains without
reconfiguring existing domains. Each PIM domain remains separate and has its own RP. The RP in each
domain establishes an MSDP peering relationship over a TCP connection either with RPs in other
domains or with border routers leading to other domains. When an RP learns about a new multicast
source in its own domain (using the normal PIM registration process), it then sends a SA message to all
of its MSDP peers, letting them know about the new stream. In this way, the network can receive
multicast traffic from all over the network without having to reconfigure each existing PIM domain.
Multicast
69
MSDP
Supported Platforms
MSDP is supported on all platforms running a minimum software version of ExtremeXOS 12.0 with the
Core license.
Our implementation of MSDP is compliant with RFC 3618 and RFC 3446, and compatible with other
devices that are compliant with these standards.
Limitations
The limitations of MSDP are as follows:
There is no support for MSDP operating with SA cache disabled (transit node). MSDP will always
cache/store received SA messages.
There is no support for logical RP.
There is no support for MSDP on user-created virtual routers (VRs).
RIP routes are not used for peer-RPF checking. So, our implementation of MSDP does not exactly
conform to rule (iii) in section 10.1.3 of RFC 3618. However, our implementation of MSDP uses BGP/
OSPF for peer-RPF checking as per rule (iii) in section 10.1.3.
Read-write/read-create access is not supported on MSDP MIB objects.
PIM Border Configuration

To create a PIM-SM domain for MSDP, you must restrict the reach of Bootstrap Router (BSR)
advertisements by defining a VLAN border. BSR advertisements are not sent out of a PIM interface
configured as a VLAN border, thereby defining a PIM domain for MSDP.
To configure a PIM VLAN border, use the command:
configure pim vlan_name border
MSDP Peers
MSDP peers exchange messages to advertise active multicast sources. The peer with the higher IP
address passively listens to a well-known port number and waits for the side with the lower IP address
to establish a Transmission Control Protocol (TCP) connection on port 639. When a PIM-SM RP that is
running MSDP becomes aware of a new local source, it sends an SA message over the TCP connection
to its MSDP peer. When the SA message is received, a peer-RPF check is performed to make sure the
peer is toward the originating RP. If so, the RPF peer floods the message further. If not, the SA message
is dropped and the message is rejected.
Configure an MSDP peer using the command:

create msdp peer remoteaddr {remote-as remote-AS} {vr vrname}
Delete an MSDP peer using the command:

delete msdp peer [all | remoteaddr] {vr vr_name}
Display configuration and run-time parameters about an MSDP peer using the command:
show msdp [peer {detail} | {peer} remoteaddr] {vr vr_name}
Multicast
70
MSDP
MSDP Default Peers

You can configure a default peer to accept all SA messages. Configuring a default peer simplifies the
peer-RPF checking of SA messages. If no policy is specified, the current peer is the default RPF peer for
all SA messages.
When configuring a default peer, you can also specify an optional policy filter. If the peer-RPF check
fails, and a policy filter is configured, the default peer rule is applied to see if the SA message should be
accepted or rejected.
You can configure multiple default peers with different policies. However, all default peers must either
be configured with a default policy or not. A mix of default peers, with a policy and without a policy, is
not allowed.
Configure an MSDP default peer, and optional policy filter using the command:
configure msdp peer [remoteaddr | all] default-peer {default-peer-policy
filter-name} {vr vrname}
Remove the default peer using the command:

configure msdp peer [remoteaddr | all] no-default-peer {vr vrname}
Verify that a default peer is configured using the command:

Peer Authentication
MSDP supports TCP RSA Data Security, Inc. MD5 Message-Digest Algorithm authentication (RFC 2385)
to secure control messages between MSDP peers. You must configure a secret password for an MSDP
peer session to enable TCP RSA Data Security, Inc. MD5 Message-Digest Algorithm authentication.
When a password is configured, MSDP receives only authenticated MSDP messages from its peers. All
MSDP messages that fail TCP RSA Data Security, Inc. MD5 Message-Digest Algorithm authentication
are dropped.
Configure TCP RSA Data Security, Inc. MD5 Message-Digest Algorithm authentication on an MSDP
peer using the command:
configure msdp peer [remoteaddr | all] password [none | {encrypted}
tcpPassword] {vr vrname}
Remove the password using the command:

configure msdp peer {all | remoteaddr} password none
The password displays in encrypted format and cannot be seen as simple text.
Additionally, the password is saved in encrypted format.
Display the password in encrypted format using the command:

Policy Filters
You can configure a policy filter to control the flow of SA messages going to or coming from an MSDP
peer. For example, policy filters can help mitigate state explosion during denial of service (DoS) or
other attacks by limiting what is propagated to other domains using MSDP.
Multicast
71
MSDP
Configure an incoming or outgoing policy filter for SA messages.

configure msdp peer [remoteaddr | all] sa-filter [in | out] [filter-name |
none] {vr vr_name}
To remove a policy filter for SA messages, use the none keyword:

configure msdp [{peer} remoteaddr | peer all] sa-filter [in | out] none
Verify that a policy filter is configured on an MSDP peer.

SA Request Processing
You can configure the router to accept or reject SA request messages from a specified MSDP peer or all
peers. If an SA request filter is specified, only SA request messages from those groups permitted are
accepted. All others are ignored.
Configure the router to accept SA request messages from a specified MSDP peer or all peers using
the command:
enable msdp [{peer} remoteaddr | peer all] process-sa-request {sa-requestfilter filter-name } {vr vr_name}
Configure the router to reject SA request messages from a specified MSDP peer or all peers using
the command:
Display configuration and run-time parameters about MSDP peers using the command:
disable msdp [{peer} remoteaddr | peer all] process-sa-request {vr vrname}
MSDP Mesh-Groups
MSDP can operate in a mesh-group topology. A mesh-group limits the flooding of SA messages to
neighboring peers. In a mesh-group, every MSDP peer must be connected to every other peer in the
group. In this fully-meshed topology, when an SA message is received from a member of the meshgroup, the SA message is always accepted, but not flooded to other members of the same group.
Because MSDP peers are connected to every other peer in the mesh-group, an MSDP peer is not
required to forward SA messages to other members of the same mesh-group. However, SA messages
are flooded to members of other mesh-groups. An MSDP mesh-group is an easy way to implement
inter-domain multicast, as it relaxes the requirement to validate looping of MSDP control traffic (that is,
peer-RPF checking is not required). Consequently, SA messages do not loop in the network.
Note
We recommend that you configure anycast RP peers in a mesh topology.
Configure an MSDP mesh-group using the command:

create msdp mesh-group mesh-group-name {vr vrname}
Remove an MSDP mesh-group using the command:

delete msdp mesh-group mesh-group-name {vr vrname}
Display information about an MSDP mesh-group using the command:

show msdp [mesh-group {detail} | {mesh-group} mesh-group-name] {vr vrname}
Multicast
72
MSDP
Configure a peer to be a member of an MSDP mesh-group using the command:

configure msdp peer [remoteaddr | all] mesh-group [mesh-group-name | none] {vr
vrname}
Remove a peer from an MSDP mesh-group using the command:

configure msdp [{peer} remoteaddr | peer all] mesh-group none {vr vrname}
Anycast RP
Anycast RP is an application of MSDP that allows multiple RPs to operate simultaneously in a PIM-SM
domain. Without anycast RP, multiple routers can be configured as candidate RPs, but at any point in
time, only one router can serve as RP. Because anycast RP allows multiple RPs to be simultaneously
active, anycast RP provides both load sharing and redundancy, as each RP serves the receivers that are
closest to it in the network and can take over for additional receivers if another RP fails.
In an anycast RP topology, all RPs in a PIM-SM domain are configured with the same IP address on a
loopback VLAN. The loopback VLAN IP address should have a 32-bit mask, so that it specifies a host
address. All the routers within the PIM-SM domain select the nearest RP for each source and receiver. If
the senders and receivers within the PIM-SM domain are distributed evenly, the number of senders that
register with each RP is approximately equal.
Another requirement of the anycast RP topology is that MSDP must run on all RPs in the PIM-SM
domain, so all RPs are also MSDP peers. We recommend that you configure an MSDP mesh connection
between all MSDP peers in the domain.
Whenever any multicast source becomes active, this information is sent in an MSDP SA message to the
other MSDP peers in the domain, announcing the presence of the source. If any RP within the domain
fails, the IP routing protocol mechanism ensures that next available RP is chosen. If a sender registers
with one RP and a receiver joins another RP, the information shared through MSDP enables PIM-SM to
establish an SPT between the receiver and the source.
Note
We recommend that you configure anycast RP peers in a mesh topology.
The exchange of information in an anycast RP process works as follows:
When the first-hop router sends a PIM Register message to the nearest RP, the PIM router checks to
see if the nearest RP is the RP for the group.
If the nearest RP is the RP for the group, an MSDP SA message is created and forwarded to the
other MSDP peers.
The MSDP SA message includes the configured originator ID, which is a mandatory configuration
component.
Each remote peer checks the RPF of the originator ID address and informs the PIM process on that
remote router about active multicast sources.
Remote receivers get data packets through the remote shared tree, and can then switch over to the
SPT by sending join messages directly towards the source.
To configure anycast RP, do the following at each anycast RP router:
Multicast
73
MSDP
Create and configure a loopback VLAN using the commands:

create vlan vlan_name {tag tag } {description vlan-description } {vr name }
enable loopback-mode vlan vlan_name
2 Assign the anycast RP address to the loopback VLAN with a 32 bit subnet mask using the
command:
configure {vlan} vlan_name ipaddress [ipaddress {ipNetmask} | ipv6-link-local
| {eui64} ipv6_address_mask]
Note
The anycast RP address must be unique to the loopback VLAN and be the same on all
anycast RP peers. It must not match the router IP address, the PIM BSR address, or any
other IP addresses used by the router or any other network devices.
3 Enable IP forwarding and IP multicast forwarding on the loopback VLAN using the commands:
enable ipforwarding {ipv4 | broadcast} {vlan vlan_name}
4 Add the loopback VLAN into the unicast routing domain using the appropriate command for your
unicast routing protocol:
configure ospf add vlan vlan-name area area-identifier link-type [auto |
broadcast | point-to-point] {passive}
configure rip add vlan [vlan_name | all]
configure isis add [vlan all | {vlan} vlan_name] area area_name {ipv4 | ipv6}
5 Add the loopback VLAN into the PIM-SM domain and configure it as an RP using the commands:
configure pim {ipv4 | ipv6} add vlan [vlan-name | all] {dense | sparse}
{passive}
configure pim {ipv4 | ipv6} crp static ip_address [none | policy] {priority
[0-254]}
6 Enable MSDP and establish a peering relationship with similar anycast RP neighbors using the
commands:
configure msdp peer [remoteaddr | all] password [none | {encrypted}
tcpPassword] {vr vrname}
configure msdp peer remoteaddr description {peer-description} {vr vrname}
enable msdp [{peer} remoteaddr | peer all] {vr vr_name}
enable msdp {vr vrname}
7 Configure a unique originator ID for each anycast RP peer using the command:
configure msdp originator-id ip-address {vr vrname}
Multicast
74
MSDP
SA Cache
As an MSDP router learns of new sources either through a PIM-SM Source-Register (SR) message or SA
message from its RPF peer, it creates an entry in SA cache (or refreshes the entry if it is already there)
and forwards this information to its peers. These entries are refreshed by periodic SA messages
received from the MSDP peers. If these entries are not refreshed within six minutes, they will time out.
When a PIM-SM RP detects that the source is no longer available it informs MSDP, which in turn
removes the SA information from the local database.
Caching makes it easy for local receivers to know immediately about inter-domain multicast sources
and to initiate building a source tree towards the source. However, maintaining a cache is heavy both in
CPU processing and memory requirements.
Note
Our implementation of MSDP does not support operating with local cache disabled.
Remove an SA cache server.

unconfigure msdp sa-cache-server {vr vrname}
As MSDP uses the flood-and-join model to propagate information about sources, there is a
restriction that no more than two advertisements per cache entry will be forwarded per
advertisement interval. This is helpful in reducing an SA message storm and unnecessarily
forwarding them to peers.
By default, the router does not send SA request messages to its MSDP peers when a new member
joins a group and wants to receive multicast traffic. The new member simply waits to receive SA
messages, which eventually arrive.
Configure the MSDP router to send SA request messages immediately to the MSDP peer when a
new member becomes active in a group.
configure msdp sa-cache-server remoteaddr {vr vr_name}
Purge all SA cache entries.

clear msdp sa-cache {{peer} remoteaddr | peer all} {group-address grp-addr}
{vr vrname}
Display the SA cache database.

show msdp [sa-cache | rejected-sa-cache] {group-address grp-addr} {sourceaddress src-addr} {as-number as-num} {originator-rp originator-rp-addr}
{local} {peer remoteaddr} {vr vrname}
Maximum SA Cache Entry Limit

You can configure a limit on the maximum number of SA cache entries that can be stored in the cache
database. Once the number of SA cache entries exceeds the pre-configured limit, any newly received
cache entries are discarded. You can configure the limit on a per-peer basis. By default, no SA message
limit is set. The router can receive an unlimited number of SA entries from an MSDP peer.
Configure a limit on the number of SA entries that can be stored in cache.

configure msdp peer [remoteaddr | all] sa-limit max-sa {vr vr_name}
To allow an unlimited number of SA entries, use 0 (zero) as the value for max-sa.
Multicast
75
MSDP
Display the SA cache limit.

Redundancy
Because the peering relationship between MSDP peers is based on TCP connections, after a failover
occurs the TCP connections need to be re-established again.
All SA cache entries learned from the old peering relationships must be flushed and relearned again on
new TCP connections.
On a dual MSM system, MSDP runs simultaneously on both MSMs. During failover, the MSDP process on
the active MSM receives and processes all control messages. MSDP on the standby MSM is in a down
state, and doesnt receive, transmit, or process any control messages. If the active MSM fails, the MSDP
process loses all state information and the standby MSM becomes active. However, the failover from
the active MSM to the standby MSM causes MSDP to loses all state information and dynamic data, so it
is not a hitless failover.
On fixed-configuration, stackable switches, an MSDP process failure brings down the switch.
SNMP MIBs
SNMP MIB access is not supported for MSDP.
Multicast
76
4 Multicast Commands
clear igmp group
clear igmp snooping
clear mld counters
clear mld group
clear mld snooping
clear msdp counters
clear msdp sa-cache
clear pim cache
clear pim snooping
configure forwarding ipmc compression
configure forwarding ipmc lookup-key
configure igmp router-alert receive-required
configure igmp router-alert transmit
configure igmp snooping filters
configure igmp snooping flood-list
configure igmp snooping leave-timeout
configure igmp snooping timer
configure igmp snooping vlan ports add dynamic group
configure igmp snooping vlan ports add static group
configure igmp snooping vlan ports add static router
configure igmp snooping vlan ports delete static group
configure igmp snooping vlan ports delete static router
configure igmp snooping vlan ports filter
configure igmp snooping vlan ports set join-limit
configure igmp ssm-map add
configure igmp ssm-map delete
configure igmp
configure ipmcforwarding
configure ipmroute add
configure ipmroute delete
configure iproute add (Multicast)
configure iproute delete
configure mcast ipv4 cache timeout
configure mld
configure mld snooping fast-learning
configure mld snooping filters
Multicast
77
Multicast Commands
configure mld snooping flood-list

configure mld snooping leave-timeout
configure mld snooping timer
configure mld snooping vlan ports add dynamic group
configure mld snooping vlan ports add static group
configure mld snooping vlan ports add static router
configure mld snooping vlan ports delete static group
configure mld snooping vlan ports delete static router
configure mld snooping vlan ports filter
configure mld snooping vlan ports join-limit
configure mld ssm-map add
configure mld ssm-map delete
configure msdp as-display-format
configure msdp max-rejected-cache
configure msdp originator-id
configure msdp peer default-peer
configure msdp peer description
configure msdp peer mesh-group
configure msdp peer no-default-peer
configure msdp peer password
configure msdp peer sa-filter
configure msdp peer sa-limit
configure msdp peer source-interface
configure msdp peer timer
configure msdp peer ttl-threshold
configure msdp sa-cache-server
configure mvr add receiver
configure mvr add vlan
configure mvr delete receiver
configure mvr delete vlan
configure mvr mvr-address
configure mvr static group
configure pim add vlan
configure pim border
configure pim cbsr
configure pim crp static
configure pim crp timer
configure pim crp vlan
configure pim delete vlan
configure pim dr-priority
configure pim iproute sharing hash
configure pim register-policy rp
Multicast
78
Multicast Commands
configure pim register-policy

configure pim register-checksum-to
configure pim register-rate-limit-interval
configure pim register-suppress-interval register-probe-interval
configure pim shutdown-priority
configure pim spt-threshold
configure pim ssm range
configure pim ssm
configure pim state-refresh timer origination-interval
configure pim state-refresh timer source-active-timer
configure pim state-refresh ttl
configure pim state-refresh
configure pim timer vlan
configure pim vlan trusted-gateway
create msdp mesh-group
create msdp peer
delete msdp mesh-group
delete msdp peer
disable igmp snooping vlan fast-leave
disable igmp ssm-map
disable igmp
disable ipmcforwarding ipv6
disable ipmcforwarding
disable mld
disable mld-ssm map
disable msdp data-encapsulation
disable msdp export local-sa
disable msdp peer
disable msdp process-sa-request
disable msdp
disable mvr
disable pim iproute sharing
disable pim snooping
disable pim ssm vlan
disable pim
enable igmp snooping vlan fast-leave
enable igmp snooping with-proxy
enable igmp snooping
enable igmp ssm-map
enable igmp
Multicast
79
Multicast Commands
enable ipmcforwarding ipv6

enable mld
enable mld snooping with-proxy
enable mld snooping
enable mld-ssm map
enable msdp data-encapsulation
enable msdp export local-sa
enable msdp peer
enable msdp process-sa-request
enable msdp
enable mvr
enable pim iproute sharing
enable pim snooping
enable pim ssm vlan
enable pim
mrinfo
mtrace
refresh mld ssm-map
rtlookup rpf
rtlookup
show igmp group
show igmp snooping cache
show igmp snooping vlan filter
show igmp snooping vlan static
show igmp snooping vlan
show igmp snooping
show igmp ssm-map
show igmp
show ipmroute
show iproute multicast
show L2stats
show mcast cache
show mcast ipv6 cache
show mld
show mld counters
show mld group
show mld snooping vlan filter
show mld snooping vlan static
show mld snooping
show mld ssm-map
show msdp memory
Multicast
80
Multicast Commands
show msdp mesh-group

show msdp peer
show msdp sa-cache
show msdp
show mvr cache
show mvr
show pim cache
show pim snooping
show pim
unconfigure igmp snooping vlan ports set join-limit
unconfigure igmp ssm-map
unconfigure igmp
unconfigure mld
unconfigure mld ssm-map
unconfigure msdp sa-cache-server
unconfigure pim border
unconfigure pim ssm range
unconfigure pim
clear igmp group

clear igmp group {grpipaddress} {{vlan} name}
Description
Removes one or all IGMP groups.
Syntax Description
grpipaddress
Specifies the group IP address.
name
Specifies a VLAN name.
Default
N/A.
Usage Guidelines
This command can be used by network operations to manually remove learned IGMP group entries
instantly. Traffic is impacted until the IGMP groups are relearned. Use this command for diagnostic
purposes only.
Multicast
81
Multicast Commands
Example
The following command clears all IGMP groups from VLAN accounting:
clear igmp group accounting
History
This command was first available in ExtremeXOS 10.1.
Platform Availability
This command is available on platforms that support the appropriate license. For complete information
about software licensing, including how to obtain and upgrade your license and which licenses support
the IPv4 multicast feature, see the Feature License Requirements document.
clear igmp snooping

clear igmp snooping {{vlan} name}
Description
Removes one or all IGMP snooping entries.
Syntax Description
name
Default
N/A.
Usage Guidelines
This command can be used by network operations to manually remove IGMP snooping entries
instantly. However, removing an IGMP snooping entry can disrupt the normal forwarding of multicast
traffic until the snooping entries are learned again.
The dynamic IGMP snooping entries are removed, and then recreated upon the next general query. The
static router entry and static group entries are removed and recreated immediately.
This command clears both the IGMPv2 and IGMPv3 snooping entries.
Example
The following command clears IGMP snooping from VLAN accounting:
clear igmp snooping accounting
Multicast
82
Multicast Commands
History
the IGMP snooping feature, see the Feature License Requirements document.
clear mld counters

clear mld counters {{vlan} vlan_name}
Description
Clears MLD statistics counters.
Syntax Description
vlan_name
Default
N/A.
Usage Guidelines
Use this command to manually clear MLD statistics counters.
Example
The following example clears all MLD counters for all VLANs:
clear mld counters
If a VLAN is specified, only the counters on the specific VLAN is cleared.
History
This command is available on the platforms listed for the IPv6 multicast routing feature in the Feature
License Requirements document.
Multicast
83
Multicast Commands
clear mld group

clear mld group {v6grpipaddress} {{vlan} name}
Description
Removes one or all MLD groups.
Syntax Description
v6grpipaddress
Specifies the group IP address.
name
Default
N/A.
Usage Guidelines
This command is used to manually remove learned MLD group entries instantly.
Example
The following command clears all MLD groups from VLAN accounting:
clear mld group accounting
History
clear mld snooping

clear mld snooping {{vlan} name}
Description
Removes one or all MLD snooping entries.
Multicast
84
Multicast Commands
Syntax Description
name
Default
N/A.
Usage Guidelines
This command can be used by network operations to manually remove MLD snooping entries instantly.
However, removing an MLD snooping entry can disrupt the normal forwarding of multicast traffic until
the snooping entries are learned again.
The static and dynamic MLD snooping entries are removed, and then recreated upon the next general
query. The static router entry is removed and recreated immediately.
Example
The following command clears MLD snooping from VLAN accounting:
clear mld snooping accounting
History
clear msdp counters

clear msdp counters {peer remoteaddr | peer all | system} {vr vrname}
Description
This command resets the MSDP counters to zero.
Syntax Description
peer all
Specifies all MSDP peers.
remoteaddr
Specifies the IP address of the MSDP peer.
Multicast
85
Multicast Commands
system
Clears the global MSDP counters.
vrname
Specifies the name of the virtual router to which this command applies. If a name is not
specified, it is extracted from the current CLI context.
Default
N/A.
Usage Guidelines
The clear msdp counters command clears the following MSDP counters:
Per peer counters:

Number of SA messages received.
Number of SA messages transmitted.
Number of SA request messages received.
Number of SA request messages transmitted.
Number of SA response messages received.
Number of SA response messages transmitted.
Number of SA messages received without encapsulated data.
Number of SA messages transmitted without encapsulated data.
Number of SA messages received with encapsulated data.
Number of SA messages transmitted with encapsulated data.
Number of times the MSDP peer attained an ESTABLISHED state.
Number of times the peer-RPF check failed.
Number of times the TCP connection attempt failed.
Total number of received messages.
Total number of transmitted messages.
Global counters:
None defined.
The clear counters command will also clear all MSDP counters, but it clears the counters for all
other applications too.
Example
The following command clears the counters for an MSDP peer with the IP address 192.168.45.43:
clear msdp counters peer 192.168.45.43
The following command clears the all peer and global counters:
clear msdp counters
Multicast
86
Multicast Commands
The following command clears all counters for a particular peer:

clear msdp counters peer 192.168.32.45
The following command clears the counters of all MSDP peers:

clear msdp counters peer all
The following command clears the global counters:

clear msdp counters system
History
the MSDP feature, see the Feature License Requirements document.
clear msdp sa-cache

clear msdp sa-cache {{peer} remoteaddr | peer all} {group-address grp-addr} {vr
vrname}
Description
This command purges all SA cache entries and notifies the PIM that the SA cache is empty.
Syntax Description
peer all
Specifies all MSDP peers. All matching SA cache entries from all peers are removed from
the database.
grp-addr
Specifies the IP address and subnet mask of the multicast group you want to clear. All SA
cache entries that match the specified group address are removed from the database.
remoteaddr
Specifies the IP address of the MSDP peer. All matching SA cache entries learned from the
specified peer are removed from the database.
vrname
Default
N/A.
Multicast
87
Multicast Commands
Usage Guidelines
MSDP receives SA messages periodically. After clearing SA cache entries from the local database,
MSDP relearns those entries during the next advertisement from its peer.
Example
The following exa,[;e clears SA cache records for an MSDP peer with the IP address 192.168.45.43:
clear msdp sa-cache peer 192.168.45.43
History
clear pim cache

clear pim {ipv4 | ipv6} cache {group_addr {source_addr}}
Description
Resets the IP multicast cache table.
Syntax Description
ipv4
Specifies an IPv4 address.
ipv6
group_addr
Specifies a group address.
source_addr
Specifies a source IP address.
Default
If no options are specified, all IP multicast cache entries are flushed.
Usage Guidelines
This command can be used by network operators to manually remove IPMC software and hardware
forwarding cache entries instantly. If the stream is available, caches are re-created; otherwise, caches
are removed permanently. This command can disrupt the normal forwarding of multicast traffic.
Multicast
88
Multicast Commands
Example
The following example resets the IP multicast table for group 224.1.2.3:
clear pim cache 224.1.2.3
History
the PIM feature, see the Feature License Requirements document.
clear pim snooping

clear pim snooping {vlan} name}
Description
Clears all PIM snooping neighbors, joins received on the VLAN, and the VLAN forwarding entries.
Syntax Description
name
Specifies the VLAN to which this command applies.
Default
N/A.
Usage Guidelines
None.
Example
The following command clears the PIM snooping database for the Default VLAN:
clear pim snooping "Default"
History
Multicast
89
Multicast Commands
the PIM snooping feature, see the Feature License Requirements document.
configure forwarding ipmc compression

configure forwarding ipmc compression {group-table | off}
Description
Enables or disables compression of entries in the IP multicast group table to facilitate improved IP
multicast scaling.
Syntax Description
group-table
Enables compression.
off
Disables compression.
Default
group-table.
Usage Guidelines
Compression of IP multicast group table entries allows the switch to process more multicast traffic
using the faster switch hardware instead of the relatively slower switch software. Compression requires
additional processing. Disable this feature if you suspect a problem exposed by IP multicast
compression.
When you enable or disable this feature, all IP multicast entries are flushed, and this can result in a
temporary loss of multicast traffic while the IP multicast entries are relearned.
Note
On BlackDiamond X8 series switches and BlackDiamond 8800 series switches, all IP multicast
forwarding entries utilizing the same IP multicast group table entry share a single backplane
link, limiting the total throughput to 12Gbps.
To display the compression feature configuration, enter the command:
show forwarding configuration
Example
The following command disables compression:
configure forwarding ipmc compression off
Multicast
90
Multicast Commands
History
This command is available on all Summit family switches, BlackDiamond X8 series switches and
BlackDiamond 8000 series modules.
configure forwarding ipmc lookup-key

configure forwarding ipmc lookup-key [group-vlan | source-group-vlan | mac-vlan |
mixed-mode]
Description
Enables you to choose the lookup-key for multicast forwarding.
Syntax Description
group-vlan
Specifies that IP multicast forwarding database entries are programmed as

(*,GroupIP,VlanId).
source-group-vlan

(SourceIP, GroupIP, VlanId). (Default).
mac-vlan

(Mac, VlanId).
mixed-mode

follows: L3 cache entries (PIM/MVR/PVLAN) use source-group-vlan; L2 cache
entries (IGMP/MLD/PIM snooping) use mac-vlan.
Default
source-group-vlan.
Usage Guidelines
Use this command to choose the lookup-key for multicast forwarding. The following restrictions apply
to this command:
The configure forwarding ipmc lookup-key mac-vlan command is disallowed under the
following conditions.
If IPMC forwarding is enabled on at least on one VLAN
If MVR is enabled either globally or on a VLAN
Similarly, enabling the above two features are disallowed,when the ipmc lookup-key is mac-vlan.
The following warning message is displayed when the mac-valn option is specified:
Multicast
91
Multicast Commands
Warning: Usage of multicast IP addresses that could result in overlapping MAC

addresses should be avoided. Example: Using 225.1.1.1, 226.1.1.1 and
225.129.1.1 should be avoided. Either one of the addresses could be used.
Using multicast with PVLAN should be avoided with this forwarding option.
Mixed-mode: configure forwarding ipmc lookup-key mixed-mode

If the chassis or stack has a member node with Felix/Helix/Firebolt*, then the command is
disallowed. After enabling this mode, if a new member with unsupported chipset joins, then that
card will be failed. The following warning message is displayed when the mixed-mode option is
specified:
Warning: Usage of multicast IP addresses that could result in overlapping MAC
addresses should be avoided for snooping (IGMP/MLD/PIM snooping) controlled
traffic.
Example: Using 225.1.1.1, 226.1.1.1 and 225.129.1.1 should be avoided. Either one of the addresses could
be used.
The configure igmp snooping forwarding-mode [group-vlan | source-group-vlan]
command was introduced to support (*, G, V) forwarding before the IPMC compression feature was
introduced. Because we are introduced IPv6 multicast support in ExtremeXOS 15.2, this command is
deprecated, and the new configure forwarding ipmc lookup-key command now covers
both IPv4 and IPv6.
Example
The following command specifies that IP multicast forwarding database entries are programmed as
(*,GroupIP,VlanId):
configure forwarding ipmc lookup-key group-vlan
To display the ipmc lookup-key configuration, enter the command:

show forwarding configuration
History
This command is available on all Summit family switches, BlackDiamond X8 series switches and
BlackDiamond 8000 series modules.
configure igmp router-alert receive-required

configure igmp router-alert receive-required [on | off] {{vlan} vlan_name}
Multicast
92
Multicast Commands
Description
Controls when the router-alert option is required for IGMPv2 and IGMPv3 packet reception and
processing.
Syntax Description
vlan
Applies the configuration only to the specified VLAN. If no VLAN is specified,

the configuration applies to all VLANs.
Default
OffAll IGMP packets are received and processed.
Usage Guidelines
By default, the ExtremeXOS software receives and processes all IGMP packets, regardless of the setting
of the router-alert option within a packet. The default configuration works with all switches that
support the ExtremeXOS software.
IETF standards require that a router accept and process IGMPv2 and IGMPv3 packets only when the
router-alert option is set. The on setting for this command sets the ExtremeXOS software to comply
with the IETF standards and should be used when the switch will be used with third-party switches that
expect IETF compliant behavior.
Example
The following command configures the switch for IETF compliant IGMP packet processing:
configure igmp router-alert receive-required on
History
This command was first available in ExtremeXOS 12.5.3.
configure igmp router-alert transmit

configure igmp router-alert transmit [on | off] {{vlan} vlan_name}
Description
Controls whether the router-alert option is set when forwarding IGMPv2 and IGMPv3 packets.
Multicast
93
Multicast Commands
Syntax Description
vlan
Applies the configuration only to the specified VLAN. If no VLAN is specified,

the configuration applies to all VLANs.
Default
OnThe router-alert option is set when forwarding IGMPv2 and IGMPv3 packets.
Usage Guidelines
IETF standards require that a router set the router-alert option in forwarded IGMPv2 and IGMPv3
packets. The ExtremeXOS software has been updated to comply with this requirement using the
default settings.
Earlier versions of the ExtremeXOS software forwarded all IGMP packets without setting the routeralertoption. If compatibility issues arise, you can configure the software to use the legacy behavior by
using this command with the off option.
Example
The following command configures the switch for IETF compliant IGMP packet processing:
configure igmp router-alert transmit on
History
configure igmp snooping filters

configure igmp snooping filters [per-port | per-vlan]
Description
Selects the type of IGMP snooping filters that are installed.
Syntax Description
per-port
Installs the per-port IGMP snooping filters.
per-vlan
Installs the per-VLAN IGMP snooping filters.
Multicast
94
Multicast Commands
Default
per-port.
Usage Guidelines
This command applies only to Summit family switches and BlackDiamond 8800 series switches.
Use the per-vlan option when the number of VLANs configured on the switch is lower than the
maximum numbers listed in the following table. This option conserves usage of the hardware Layer 3
multicast forwarding table.
When the number of configured VLANs is larger than the maximum values listed here, select the perport option. Each VLAN requires additional interface hardware ACL resources. The per-port option
conserves usage of the interface hardware ACL resources.
Table 6: Maximum Number of VLANs Supported by per-VLAN IGMP Snooping Filters
Summit Switch and BlackDiamond 8000 Series
Module Type
Maximum Number of VLANs When per-VLAN Snooping

Filters are Installed
a Series
1000
c Series
2000 1
e Series
448 1
xl Series
2000 1
To display the IGMP snooping filters configuration, use the show igmp snooping command.
Note
For MLD Snooping, the maximum number of VLANs is half of the numbers provided in this
table. The maximum number specified here is individual limit for IGMP snooping filters. If both
IGMP and MLD snooping filters are used, the maximum numbers are lower than the ones
specified.
Example
The following command configures the switch to install the per-VLAN IGMP snooping filters:
configure igmp snooping filters per-vlan
History
The actual maximum value is smaller if other processes require entries in the interface ACL table.
Multicast
95
Multicast Commands
configure igmp snooping flood-list

configure igmp snooping flood-list [policy | none] {vr vrname}
Description
Configures certain multicast addresses to be slow path flooded within the VLAN.
Syntax Description
policy
Specifies a policy file with a list of multicast addresses to be handled.
none
Specifies no policy file is to be used.
vrname
Specifies a virtual router.
Default
None.
Usage Guidelines
With this command, a user can configure certain multicast addresses to be slow path flooded within
the VLAN, which otherwise are fast path forwarded according to IGMP and/or Layer 3 multicast
protocol.
A policy file is a text file with the extension, .pol. It can be created or edited with any text editor. The
specified policy file policy file should contain a list of addresses which determine if certain
multicast streams are to be treated specially. Typically, if the switch receives a stream with a
destination address which is in the policy file in 'permit' mode, that stream is software flooded
and no hardware entry is installed.
When adding an IP address into the policy file, a 32-bit host address is recommended.
This feature is meant to solve the multicast connectivity problem for unknown destination addresses
within system reserved ranges. Specifically this feature was introduced to solve the problem of
recognizing certain streams as control packets.
To create a policy file for the snooping flood-list, use the following template:
# This is a template for IGMP Snooping Flood-list Policy File
# Add your group addresses between "Start" and "End"
entry igmpFlood {
if match any {
#------------------ Start of group addresses ------------------
Multicast
96
Multicast Commands
nlri 234.1.1.1/32;
nlri 239.1.1.1/32;
#------------------- end of group addresses ------------------}
then {
permit;
}
}
entry catch_all {
if {
}
then {
deny;
}
}
Note
The switch does not validate any IP address in the policy file used in this command.
Therefore, slow-path flooding should be used only for streams which are very infrequent,
such as control packets. It should not be used for multicast data packets. This option
overrides any default mechanism of hardware forwarding (with respect to IGMP, PIM, or
DVMRP), so it should be used with caution.
Slow path flooding is done within the L2 VLAN only.
Use the none option to effectively disable slow path flooding.
You can use the show igmp command to see the configuration of slow path flooding.
Example
The following example configures the multicast data stream specified in access1 for slow path flooding:
configure igmp snooping flood-list access1
The following command specifies that no policy file is to be used, this effectively disabling slow path
flooding:
configure igmp snooping flood-list none
History
Multicast
97
Multicast Commands
configure igmp snooping leave-timeout

configure igmp snooping leave-timeout leave_timeout_ms {vr vrname}
Description
Configures the IGMP snooping leave timeout.
Syntax Description
leave_timeout_ms
Specifies an IGMP leave timeout value in milliseconds.
vrname
Default
1000 ms.
Usage Guidelines
The leave-timeout is the IGMP leave override interval. If no other hosts override the IGMP leave by the
end of this interval, the receiver port is removed.
The range is 0175000 ms (175 seconds). For timeout values of one second or less, you must set the
leave-timeout to a multiple of 100 ms. For values of more than one second, you must set the leavetimeout to a multiple of 1000 ms (one second).
Example
The following exa,[;e configures the IGMP snooping leave timeout to one second:
configure igmp snooping leave-timeout 10000
History
configure igmp snooping timer

configure igmp snooping timer router_timeout host_timeout {vr vrname} {vlan
vlan_name}
Multicast
98
Multicast Commands
Description
Configures the IGMP snooping timers.
Syntax Description
router_timeout
Specifies the time in seconds before removing a router snooping entry.
host_timeout
Specifies the time in seconds before removing a hosts group snooping entry.
vrname
vlan
Specifies a VLAN.
vlan_name
Specifies the VLAN name. If no VLAN is specified, the setting is applied to all
existing VLANs.
Default
The router timeout default setting is 260 seconds. The host timeout setting is 260 seconds.
Usage Guidelines
Timers should be set to approximately 2.5 times the router query interval in use on the network. Specify
the following:
router timeoutThe maximum time, in seconds, that a router snooping entry can remain in the
IGMP snooping table without receiving a router report. If a report is not received, the entry is
deleted. The range is 10 to 214,748,364 seconds (6.8 years). The default setting is 260 seconds.
host
timeoutThe maximum time, in seconds, that a group snooping entry can remain in the
IGMP snooping table without receiving a group report. If a report is not received, the entry is
deleted. The range is 10 to 214,748,364 seconds. The default setting is 260 seconds.
Note
The host_timeout value should be less than or equal to the query timeout value, which
is defined by the following: (query_interval x robustness) + query_response_interval.
IGMP snooping expects at least one device on every VLAN to periodically generate IGMP query
messages. Without an IGMP querier, the switch eventually stops forwarding IP multicast packets to any
port, because the IGMP snooping entries time out, based on the value specified in host_timeout or
router_timeout.
Example
The following example configures the IGMP snooping timers:
configure igmp snooping timer 600 600
History
Multicast
99
Multicast Commands
configure igmp snooping vlan ports add dynamic group

configure igmp snooping {vlan} vlan_name {ports portlist} add dynamic group
[ grpipaddress ]
Description
Configures an IGMP dynamic group.
Syntax Description
vlan_name
Specifies a vlan name.
portlist
Specifies a port list.
grpipaddress
Specifies the multicast group IP address.
Default
N/A.
Usage Guidelines
This command is not saved in the configuration. The following message is displayed on execution of
this command:
INFO: This command is not saved in the configuration.
Example
The following example adds a dynamic group to a switch port:
switch.111 # configure igmp snooping vlan "ixia113" ports 47 add dynamic
group 225.1.1.1
The following command displays the group:

switch.112 # show igmp group
Group Address
Ver Vlan
225.1.1.1
2
ixia113
Port
47
Age
3
Total: 1
switch.113 #
Multicast
100
Multicast Commands
The following example adds a dynamic group to a vlan (loopback port):

switch sw5.113 # configure igmp snooping vlan "ixia113" add dynamic group
225.1.1.1

Group Address
Ver Vlan
225.1.1.1
2
ixia113
Port
Lpbk
Age
37
Total: 1
switch.115 #
History
configure igmp snooping vlan ports add static group

configure igmp snooping {vlan} vlanname {ports portlist }add static group
grpipaddress
Description
Configures VLAN ports to receive the traffic from a multicast group, even if no IGMP joins have been
received on the port.
Syntax Description
vlanname
portlist
Specifies one or more ports or slots and ports.
grpipaddress
Default
N/A.
Multicast
101
Multicast Commands
Usage Guidelines
Use this command to forward a particular multicast group to VLAN ports. In effect, this command
emulates a host on the port that has joined the multicast group. As long as the port is configured with
the static entry, multicast traffic for that multicast group is forwarded to that port.
This command is for IGMPv2 only.
The switch sends proxy IGMP messages in place of those generated by a real host. The proxy messages
use the VLAN IP address for source address of the messages. If the VLAN has no IP address assigned,
the proxy IGMP message uses 0.0.0.0 as the source IP address.
The multicast group should be in the class-D multicast address space, but should not be in the multicast
control subnet range (224.0.0.x/24).
If the ports also have an IGMP filter configured, the filter entries take precedence. IGMP filters are
configured using the command:
configure igmp snooping vlan vlanname ports portlist filterpolicy file
Example
The following example configures a static IGMP entry so that multicast group 225.1.1.1 is forwarded to
VLAN "marketing" on port 47:
switch.30 # configure igmp snooping marketing ports 47 add static group
225.1.1.1

* (pacman debug) sw4.31 # show igmp group
Group Address
Ver Vlan
Port
225.1.1.1(s)
2
marketing
47
Age
0
Total: 1
switch.32 #
The following example adds a static group to a vlan (loopback port):

switch.32 # configure igmp snooping marketing add static group 225.1.1.1

Group Address
Ver Vlan
225.1.1.1(s)
2
marketing
Port
Lpbk
Age
0
Total: 1
switch.34 #
History
Multicast
102
Multicast Commands
configure igmp snooping vlan ports add static router

configure igmp snooping {vlan} vlanname ports portlist add static router
Description
Configures VLAN ports to forward the traffic from all multicast groups, even if no IGMP joins have been
Syntax Description
vlanname
portlist
Default
N/A.
Usage Guidelines
Use this command to forward all multicast groups to the specified VLAN ports. In effect, this command
emulates a multicast router attached to those ports. As long as the ports are configured with the static
entry, all available multicast traffic is forwarded to those ports.
Example
The following example configures a static IGMP entry so all multicast groups are forwarded to VLAN
marketing on ports 2:1-2:4:
configure igmp snooping marketing ports 2:1-2:4 add static router
History
Multicast
103
Multicast Commands
configure igmp snooping vlan ports delete static group

configure igmp snooping {vlan} vlan_name {ports port_list} delete static group
[ip_address | all]
Description
Removes the port configuration that causes multicast group traffic to be forwarded, even if no IGMP
leaves have been received on the port.
Syntax Description
vlan_name
port_list
ip_address
all
Delete all the static groups.
Default
N/A.
Usage Guidelines
Use this command to remove a static group entry created by the following command:
configure igmp snooping vlan vlanname ports portlist add static group ipaddress
Example
The following example removes a static IGMP entry that forwards the multicast group 224.34.15.37 to
the VLAN marketing on ports 2:1-2:4:
configure igmp snooping marketing ports 2:1-2:4 delete static group
224.34.15.37
History
Multicast
104
Multicast Commands
configure igmp snooping vlan ports delete static router

configure igmp snooping vlan vlanname ports portlist delete static router
Description
Removes the configuration that causes VLAN ports to forward the traffic from all multicast groups,
even if no IGMP joins have been received on the port.
Syntax Description
vlanname
portlist
Specifies one or more ports or slots and ports. On a modular switch, can be a
list of slots and ports. On a standalone switch, can be one or more port
numbers. May be in the form 1, 2, 3-5, 2:5, 2:6-2:8.
Default
N/A.
Usage Guidelines
Use this command to remove an entry created by the following command:
configure igmp snooping vlan vlanname ports portlist add static router
Example
The following example removes the static IGMP entry that caused all multicast groups to be forwarded
to VLAN marketing on ports 2:1-2:4:
configure igmp snooping marketing ports 2:1-2:4 delete static router
History
configure igmp snooping vlan ports filter

configure igmp snooping vlan vlanname ports portlist filter [policy | none]
Multicast
105
Multicast Commands
Description
Configures an IGMP snooping policy file filter on VLAN ports.
Syntax Description
vlanname
portlist
Specifies one or more ports or slots and ports. On a modular switch, can be a list of
slots and ports. On a stand-alone switch, can be one or more port numbers. May be in
the form 1, 2, 3-5, 2:5, 2:6-2:8.
policy
Specifies the policy file for the filter.
Default
None.
Usage Guidelines
Use this command to filter multicast groups to the specified VLAN ports.
The policy file used by this command is a text file that contains the class-D addresses of the multicast
groups that you wish to block.
To remove IGMP snooping filtering from a port, use the none keyword version of the command.
Use the following template to create a snooping filter policy file:
# # Add your group addresses between "Start" and "end" # Do not touch the
rest of the
file!!!!
entry igmpFilter
{ if match any
{
#------------------ Start of group addresses -----------------nlri 239.11.0.0/16; nlri 239.10.10.4/32;
#------------------- end of group addresses ------------------} then { deny;
}
}
entry catch_all
{ if
{
} then
{ permit;
}
}
Multicast
106
Multicast Commands
Example
The following example configures the policy file ap_multicast to filter multicast packets forwarded to
VLAN marketing on ports 2:1-2:4:
configure igmp snooping marketing ports 2:1-2:4 filter ap_multicast
History
configure igmp snooping vlan ports set join-limit

configure igmp snooping {vlan} vlanname ports portlist set join-limit {num}
Description
Configures VLAN ports to support a maximum number of IGMP joins.
Syntax Description
vlanname
portlist
num
Specifies the maximum number of joins permitted on the ports. The range is 1
to 500.
Default
No limit.
Usage Guidelines
None.
Example
The following example configures port 2:1 in the Default VLAN to support a maximum of 100 IGMP
joins:
configure igmp snooping "Default" ports 2:1 set join-limit 100
Multicast
107
Multicast Commands
History
configure igmp ssm-map add

configure igmp ssm-map add group_ip [prefix | mask] [source_ip | src_domain_name]
{vr vr-name}
Description
Configures an IGMP SSM mapping.
Syntax Description
group_ip
Specifies the multicast IP address for the group mapping.
prefix
Specifies a prefix length for the multicast group IP address. The range is 4 to
32.
mask
Specifies the network mask for the group multicast IP address.
source_ip
The IP address for a multicast group source.
src_domain_name
The source domain name for the multicast group source.
vr-name
Specifies a virtual router name. If the VR name is omitted, the switch uses the
VR specified by the current CLI VR context.
Default
N/A.
Usage Guidelines
IGMP SSM mapping operates only with IPv4.
Example
The following example configures an IGMP-SSM mapping for the range of multicast IP addresses at
232.1.1.0/24 to IP host 172.16.8.1:
configure igmp ssm-map add 232.1.1.0/24 172.16.8.1
Multicast
108
Multicast Commands
History
configure igmp ssm-map delete

configure igmp ssm-map delete group_ip [prefix} | mask] [source_ip | all] vr vrname}
Description
Unconfigures an SSM mapping.
Syntax Description
group_ip
Specifies the multicast IP address for the group mapping.
prefix
Specifies a prefix length for the multicast group IP address. The range is 4 to
32.
mask
Specifies the network mask for the group multicast IP address.
source_ip
The IP address for a multicast group source.
all
Specifies that all sources for the specified group or mask are deleted.
vr-name
Default
N/A.
Usage Guidelines
None.
Example
The following example deletes an IGMP-SSM mapping for the range of multicast IP addresses at
232.1.1.0/24 to IP host 172.16.8.1:
configure igmp ssm-map delete 232.1.1.0/24 172.16.8.1
Multicast
109
Multicast Commands
History
configure igmp
configure igmp query_interval query_response_interval last_member_query_interval
{robustness}
Description
Configures the Internet Group Management Protocol (IGMP) timers.
Syntax Description
query_interval
Specifies the interval (in seconds) between general queries.
query_response_interval
Specifies the maximum query response time (in seconds).
last_member_query_interv Specifies the maximum group-specific query response time (in seconds).
al
robustness
Specifies the degree of robustness for the network.
Default
query interval125 seconds

query response interval10 seconds
last member query interval1 second
robustness2
Usage Guidelines
Timers are based on RFC2236. Specify the following:
Multicast
query intervalThe amount of time, in seconds, the system waits between sending out general
queries. The range is 1 to 429,496,729 seconds.
query response intervalThe maximum response time inserted into the periodic general queries.
The range is 1 to 25 seconds.
last member query intervalThe maximum response time inserted into a group-specific query sent
in response to a leave group message. The range is 1 to 25 seconds.
110
Multicast Commands
robustnessThe degree of robustness of the network. The range is 2 to 7. This parameter allows
tuning for the expected packet loss on a link. If a link is expected to have packet loss, this parameter
can be increased.
The group timeout is defined by the formula: group_timeout = (query_interval x robustness) +
query_response_interval, according to RFC 2236. You can explicitly define the host timeout using
the configure igmp snooping timer router_timeout host_timeout {vr vrname}
command. The effective host_timeout is the lesser value of the group_timeout and the
configured host_timeout.
Example
The following command configures the IGMP timers:
configure igmp 100 5 1 3
History
configure ipmcforwarding
configure ipmcforwarding to-cpu [auto | off] ports port_list
Description
Configure whether IP multicast CPU filters are installed automatically.
Syntax Description
auto
The software will automatically program IP multicast processing based on

configuration.
off
IP multicast packets received on this port are always flooded with no CPU
processing.
port_list
Specifies on or more ports.
Default
N/A.
Multicast
111
Multicast Commands
Usage Guidelines
IP forwarding and IPMC forwarding must be enabled for the configuration to operate.
Example
The following example configures automatic operation for port 2.1:
configure ipmcforwarding to-cpu auto ports 2.1
History
configure ipmroute add

configure ipmroute add [source-net mask-len | source-net mask] {{protocol}
protocol} rpf-address {metric} {vr vr-name}
Description
Adds a static multicast route to the multicast routing table.
Syntax Description
source-net
Specifies an IP address/mask length.
mask-len
Mask length for the IP multicast source's subnet. Range is [1-32].
mask
Specifies a subnet mask.
protocol
Unicast routing protocol that is to be used for route learning.
rpf-address
Next hop through which the multicast source can be reached.
metric
Specifies a cost metric.
vr-name
Specifies the virtual router to which the route is added.
Default
The following defaults apply:
Multicast
metric1
vr-nameVR of the current CLI context
protocolnone
112
Multicast Commands
Usage Guidelines
This command allows you to statically configure where multicast sources are located (even though the
unicast routing table has different entries). It allows you to configure a multicast static route in such a
way as to have non-congruent topology for Unicast and Multicast topology and traffic.
Example
The following example configures a multicast static route for all multicast sources within network
subnet 192.168.0.0/16. Those sources are reachable through the gateway 192.75.0.91.
configure ipmroute add 192.168.0.0/16 192.75.0.91
The following example configures multicast static route for all sources via a single gateway with a
metric of 100:
configure ipmroute add 0.0.0.0/0 192.75.0.91 100
History
configure ipmroute delete

configure ipmroute delete [source-net/mask-len | source-net mask] {{protocol}
protocol} rpf-address {vr vr-name}
Description
Deletes a static multicast address from the multicast routing table.
Syntax Description
source-net
mask-len
Mask length for the IP multicast source's subnet. Range is 132.
mask
protocol
Unicast routing protocol that is to be used for route learning.
rpf-address
Next hop through which the multicast source can be reached.
vr-name
Multicast
113
Multicast Commands
Default
vr-name is the VR of the current CLI context.
Usage Guidelines
This command allows you to delete an existing multicast static route. It allows you to configure
congruent topology for unicast and multicast packets and traffic.
Example
The following example deletes a multicast static route:
configure ipmroute delete 192.168.0.0/16 192.75.0.91
History
configure iproute add (Multicast)

configure iproute add [ipNetmask | ip_addr mask] gateway {metric} {multicast |
Description
Adds a static route to the routing table.
Syntax Description
ipNetmask
ip_addr
Specifies an IP address.
mask
gateway
Specifies a VLAN gateway.
metric
Specifies a cost metric.
vrname
multicast
Adds the specified route to the multicast routing table.
multicast-only
Adds the specified route to the multicast routing table. This option is
provided for backward compatibility with releases prior to ExtremeXOS 12.1.
Multicast
114
Multicast Commands
unicast
Adds the specified route to the unicast routing table.
unicast-only
Adds the specified route to the unicast routing table. This option is provided
for backward compatibility with releases prior to ExtremeXOS 12.1.
Default
If you do not specify a virtual router, the current virtual router context is used.
Usage Guidelines
Use a mask value of 255.255.255.255 to indicate a host entry.
Note
Although dynamic unicast routes can be captured in the multicast routing table, unicast static
routes cannot be captured in the multicast routing table. To create a static route for the
multicast routing table, you must specify the multicast option.
Example
The following example adds a static address to the multicast routing table:
configure iproute add 10.1.1.0/24 123.45.67.1 5 multicast
History
The multicast and unicast keywords were first available in ExtremeXOS 12.1. These keywords
replace multicast-only and unicast-only, which remain in the software for backward
compatibility.
configure iproute delete

configure iproute delete [ipNetmask | ipaddress mask] gateway {multicast |
Description
Deletes a static address from the routing table.
Multicast
115
Multicast Commands
Syntax Description
ipNetmask
ipaddress
Specifies an IP address.
mask
gateway
Specifies a VLAN gateway.
multicast
Specifies a multicast route to delete.
multicast-only
Specifies a multicast route to delete.
unicast
Specifies a unicast route to delete.
unicast-only
Specifies a unicast route to delete.
vrname
Specifies the virtual router to which the route is deleted.
Default
If you do not specify a virtual router, the current virtual router context is used.
Usage Guidelines
Use a value of 255.255.255.255 or /32 for mask to indicate a host entry.
Example
The following example deletes an address from the multicast routing table:
configure iproute delete 10.101.0.0/24 10.101.0.1 multicast
History
The multicast and unicast keywords were first available in ExtremeXOS 12.1. These keywords
replace multicast-only and unicast-only, which remain in the software for backward
compatibility.

configure mcast ipv4 cache timeout {seconds | none}
Multicast
116
Multicast Commands
Description
Configures the IPv4 multicast cache timeout.
Syntax Description
seconds
Idle time after which cache entries are deleted.
none
Cache entries are not timed out.
Default
300 seconds.
Usage Guidelines
Cache timeout is the time after which the cache entries are deleted if traffic is not received for that
duration. This applies only for snooping and MVR caches and does not apply for PIM caches.
The range is 90 to 100000 seconds. You can use the option none if you do not want the cache entry to
be deleted. If none is configured, the cache entries can be deleted only using the following command:
clear igmp snooping
Example
The following example configures the IPv4 multicast cache timeout to 400 seconds.
configure mcast ipv4 cache timeout 400
The following command clears he IPv4 multicast cache timeout.

configure mcast ipv4 cache timeout none
History

configure mcast ipv6 cache timeout {seconds | none}
Multicast
117
Multicast Commands
Description
Configures the IPv6 multicast cache timeout.
Syntax Description
seconds
Idle time after which cache entries are deleted.
none
Cache entries are not timed out.
Default
300 seconds.
Usage Guidelines
Cache timeout is the time after which the cache entries are deleted if traffic is not received for that
duration. This applies only for snooping and MVR caches and does not apply for PIM caches.
The range is 90 to 100000 seconds. You can use the option none if you do not want the cache entry to
be deleted. If none is configured, the cache entries could be deleted only using the following command:
clear igmp snooping
Example
The following example configures the IPv6 multicast cache timeout to 400 seconds.
configure mcast ipv6 cache timeout 400
The following command clears he IPv6 multicast cache timeout.

configure mcast ipv6 cache timeout none
History
the MLD snooping feature, see the Feature License Requirements document.
configure mld
configure mld query_interval query_response_interval last_member_query_interval
{robustness}
Multicast
118
Multicast Commands
Description
Configures the Multicast Listener Discovery (MLD) timers.
Syntax Description
query_interval
Specifies the interval (in seconds) between general queries.
query_response_interval
Specifies the maximum query response time (in seconds).
last_member_query_interv Specifies the maximum group-specific query response time (in seconds).
al
robustness
Specifies the degree of robustness for the network.
Default
query interval125 seconds

query response interval10 seconds
last member query interval1 second
robustness2
Usage Guidelines
Timers are based on RFC2710. Specify the following:
query intervalThe amount of time, in seconds, the system waits between sending out general
queries. The range is 1 to 429,496,729 seconds.
query response intervalThe maximum response time inserted into the periodic general queries.
The range is 1 to 25 seconds.
last member query intervalThe maximum response time inserted into a group-specific query sent
in response to a leave group message. The range is 1 to 25 seconds.
robustnessThe degree of robustness of the network. The range is 2 to 7.
Example
The following command configures the MLD timers:
configure mld 100 5 1 3
History
Multicast
119
Multicast Commands
configure mld snooping fast-learning

configure mld snooping fast-learning [on | off] [vlan vlan_name]
Description
Configures fast-learning mode.
Syntax Description
vlan_name
Specifies a vlan name
Default
off.
Usage Guidelines
When MLD snooping is enabled on a VLAN, learning of group entries will happen only when the next
periodic query is sent by the querier in the network. When fast-learning is turned on using this
command, a general is sent under the following conditions:
When MLD snooping is enabled.
When MLD snooping VLAN is operationally up.
Group join limit changed through configuration.
Query generated for faster learning uses unspecified address as the source address (both L2 and L3),
unless the switch generating the triggered query is the querier for the network.
Example
configure mld snooping fast-learning on
History
configure mld snooping filters

configure mld snooping filters [per-port | per-vlan]
Multicast
120
Multicast Commands
Description
Selects the type of MLD snooping filters that are installed.
Syntax Description
per-port
Installs the per-port MLD snooping filters.
per-vlan
Installs the per-VLAN MLD snooping filters.
Default
per-port.
Usage Guidelines
This command applies only to Summit family switches and BlackDiamond 8800 series switches.
Use the per-vlan option when the number of VLANs configured on the switch is lower than half of the
maximum numbers listed in Table 6: Maximum Number of VLANs Supported by per-VLAN IGMP
Snooping Filters on page 95. This option conserves usage of the hardware Layer 3 multicast forwarding
table.
When the number of configured VLANs is larger than half of the maximum values listed in Table 6:
Maximum Number of VLANs Supported by per-VLAN IGMP Snooping Filters on page 95, select the
per-port option. Each VLAN requires additional interface hardware ACL resources. The per-port option
conserves usage of the interface hardware ACL resources.
To display the MLD snooping filters configuration, use the show mld snooping command.
Example
The following command configures the switch to install the per-VLAN MLD snooping filters:
configure mld snooping filters per-vlan
History
configure mld snooping flood-list

configure mld snooping flood-list [policy | none]
Multicast
121
Multicast Commands
Description
Configures certain multicast addresses to be slow path flooded within the VLAN.
Syntax Description
policy
Specifies a policy file with a list of multicast addresses to be handled.
none
Specifies no policy file is to be used.
Default
None.
Usage Guidelines
With this command, you can configure certain multicast addresses to be slow path flooded within the
VLAN, instead of fast path forwarded according to MLD and/or Layer 3 multicast protocol.
A policy file is a text file with the extension .pol. It can be created or edited with any text editor. The
specified policy file policy file should contain a list of addresses that determine if certain multicast
streams are to be treated specially. Typically, if the switch receives a stream with a destination address
which is in the policy file in 'permit' mode, that stream is software flooded and no hardware entry
is installed.
When adding an IPv6 address into the policy file, a 128-bit host address is recommended.
This feature is meant to solve the multicast connectivity problem for unknown destination addresses
within system reserved ranges. Specifically this feature was introduced to solve the problem of
recognizing a certain stream as control packets.
To create a policy file for the snooping flood-list, use the following template:
# This is a template for MLD Snooping Flood-list Policy File
# Add your group addresses between "Start" and "End"
# Do not touch rest of file!!!!
entry mldFlood {
if match any {
#------------------ Start of group addresses -----------------nlri ff05::100:1/128;
nlri ff05::100:15/128;
permit;
}
}
entry catch_all {
if {
} then {
deny;
Multicast
122
Multicast Commands
}
}
Note
The switch does not validate any IP address in the policy file used in this command.
Therefore, slow-path flooding should be used only for streams that are very infrequent, such
as control packets. It should not be used for multicast data packets. This option overrides any
default mechanism of hardware forwarding (with respect to MLD or PIM), so it should be
used with caution.
Slow-path flooding occurs within the L2 VLAN only.
Use the none option to effectively disable slow path flooding.
You can use the show mld command to see the configuration of slow path flooding.
Note
This command has no effect in the current release, as IPv6 multicast traffic floods on all
platforms.
Example
The following example configures the multicast data stream specified in access1 for slow-path flooding:
configure mld snooping flood-list access1
The following command specifies that no policy file is to be used, thus effectively disabling slow-path
flooding:
configure mld snooping flood-list none
History
configure mld snooping leave-timeout

configure mld snooping leave-timeout leave_timeout_ms
Description
Configures the MLD snooping leave timeout.
Multicast
123
Multicast Commands
Syntax Description
leave_timeout_ms
Specifies an MLD leave timeout value in milliseconds upon receiving an MLD

done message.
Default
1000 ms.
Usage Guidelines
The range is 0175000 ms (175 seconds). For timeout values of one second or less, you must set the
leave-timeout to a multiple of 100 ms. For values of more than one second, you must set the leavetimeout to a multiple of 1000 ms (one second).
The specified time is the maximum leave timeout value. The switch could leave sooner if an MLD done
message is received before the timeout occurs.
Example
The following example configures the MLD snooping leave timeout to 10 seconds:
configure mld snooping leave-timeout 10000
History
configure mld snooping timer

configure mld snooping timer router_timeout host_timeout
Description
Configures the MLD snooping timers.
Syntax Description
router_timeout
Specifies the time in seconds before removing a router snooping entry.
host_timeout
Specifies the time in seconds before removing a hosts group snooping entry.
Multicast
124
Multicast Commands
Default
The router timeout default setting is 260 seconds. The host timeout setting is 260 seconds.
Usage Guidelines
Timers should be set to approximately 2.5 times the router query interval in use on the network. Specify
the following:
router_timeoutThe maximum time, in seconds, that a router snooping entry can stay without
receiving a router report. The range is 10 to 214,748,364 seconds (6.8 years). The default setting is
260 seconds.
host_timeoutThe maximum time, in seconds, that a group snooping entry can stay without
receiving a group report. The range is 10 to 214,748,364 seconds (6.8 years). The default setting is
260 seconds.
MLD snooping is a Layer 2 function of the switch. It does not require multicast routing to be enabled.
The feature reduces the flooding of IPv6 multicast traffic. On the VLAN, MLD snooping optimizes the
usage of network bandwidth and prevents multicast traffic from being flooded to parts of the network
that do not need it. The switch does not reduce any IP multicast traffic in the local multicast domain
(FF02::x).
MLD snooping is enabled by default on the switch. MLD snooping expects at least one device on every
VLAN to periodically generate MLD query messages. Without an MLD querier, the switch eventually
stops forwarding IPv6 multicast packets to any port, because the MLD snooping entries times out,
based on the value specified in host timeout.
Example
The following example configures the MLD snooping timers to 600 seconds for both timers:
configure mld snooping timer 600 600
History
configure mld snooping vlan ports add dynamic group

configure mld snooping {vlan} vlan_name {ports portlist} add dynamic group
[v6group]
Multicast
125
Multicast Commands
Description
Configures an MLD dynamic group.
Syntax Description
vlan_name
portlist
Specifies a port list.
v6group
Specifies a version 6 group.
Default
N/A.
Usage Guidelines
This command is not saved in the configuration. The following message is displayed on execution of
this command:
Example
# show mcast cache
Snooping/MVR Cache Timeout: 300 sec
Type Group
Sender
pim
20.20.20.50
Port
Vid
1
10
pbk
4088
v1
snoop 224.0.0.5
Vlan
v1
10.10.10.1
Port
Vid
1
10
21
v1
snoop 224.0.0.13
Vlan
v1
10.10.10.1
Port
Vid
1
10
225.1.1.1
Vlan
v1
v3
Age
21
InVlan
v1
Multicast cache distribution:

2 entries from Snooping
0 entries from MVR
1 entries from PIM
Total Cache Entries: 3
History
Multicast
126
Multicast Commands
configure mld snooping vlan ports add static group

configure mld snooping {vlan} vlan_name {ports port_list } add static group
v6grpipaddress
Description
Configures VLAN ports to receive the traffic from a multicast group, even if no MLD joins have been
Syntax Description
vlan_name
port_list
Specifies one or more ports or slots and ports. On a modular switch, it can be
a list of slots and ports. On a standalone switch, it can be one or more port
numbers. In the form 1, 2, 3-5, 2:5, 2:6-2:8.
v6grpipaddress
Specifies the multicast group IPv6 address.
Default
N/A.
Usage Guidelines
Use this command to forward a particular multicast group to VLAN ports. In effect, this command
emulates a host on the port that has joined the multicast group. As long as the port is configured with
the static entry, multicast traffic for that multicast group is forwarded to that port.
The switch sends proxy MLD messages in place of those generated by a real host. The proxy messages
use the VLAN IPv6 address for source address of the messages. If the VLAN has no IPv6 address
assigned, the proxy MLD message uses 0::0 as the source IP address.
Example
The following example configures a static MLD entry so the multicast group ff02::1:1 is forwarded to
configure mld snooping marketing ports 2:1-2:4 add static group ff02::1:1
Multicast
127
Multicast Commands
History
configure mld snooping vlan ports add static router

configure mld snooping {vlan} vlan_name ports port_list add static router
Description
Configures VLAN ports to forward the traffic from all multicast groups, even if no MLD joins have been
Syntax Description
vlan_name
port_list
Default
N/A.
Usage Guidelines
Use this command to forward all multicast groups to the specified VLAN ports. In effect, this command
emulates a multicast router attached to those ports. As long as the ports are configured with the static
entry, all available multicast traffic is forwarded to those ports.
Example
The following example configures a static MLD entry so all multicast groups are forwarded to VLAN
marketing on ports 2:1-2:4:
configure mld snooping marketing ports 2:1-2:4 add static router
History
Multicast
128
Multicast Commands
configure mld snooping vlan ports delete static group

configure mld snooping {vlan} vlan_name ports port_list delete static group [all
| v6grpipaddress]
Description
Removes the configuration that causes VLAN ports to receive the traffic from a multicast group, even if
no MLD joins have been received on the port.
Syntax Description
vlan_name
port_list
numbers. In the form 1, 2, 3-5, 2:5, 2:6-2:8.
all
Specifies all multicast groups.
v6grpipaddress
Specifies the multicast group IPv6 address.
Default
N/A.
Usage Guidelines
Use this command to delete a static group from a particular VLAN port.
To add a static group, use the following command:
configure mld snooping {vlan} vlan_name portsport_list add static
groupv6grpipaddress
Example
The following example removes a static MLD entry so the multicast group ff02::a:b is not forwarded to
VLAN marketing on ports 2:1-2:4, unless an MLD join message is received on the port:
configure mld snooping marketing ports 2:1-2:4 delete static group ff02::a:b
History
Multicast
129
Multicast Commands
configure mld snooping vlan ports delete static router

configure mld snooping {vlan} vlan_name ports port_list delete static router
Description
Configures VLAN ports to stop forwarding the traffic from all multicast groups, unless MLD joins have
been received on the port.
Syntax Description
vlan_name
port_list
Default
None.
Usage Guidelines
Use this command to remove the configuration that forwards all multicast groups to the specified
VLAN ports.
Example
The following example removes a static MLD entry so all multicast groups are not forwarded to VLAN
marketing on ports 2:1-2:4, unless an MLD join is received on the port:
configure mld snooping marketing ports 2:1-2:4 delete static router
History
Multicast
130
Multicast Commands
configure mld snooping vlan ports filter

configure mld snooping vlan vlan_name ports port_list filter [policy]
Description
Configures a MLD snooping policy file filter on VLAN ports.
Syntax Description
vlan_name
port_list
Specifies one or more ports or slots and ports. On a modular switch, can be a
list of slots and ports. On a standalone switch, can be one or more port
policy
Specifies the policy file for the filter.
Default
None.
Usage Guidelines
Use this command to filter multicast groups to the specified VLAN ports.
The policy file used by this command is a text file that contains the IPv6 multicast addresses of the
multicast groups that you wish to block.
To remove MLD snooping filtering from a port, use the none keyword version of the command.
Use the following template to create a snooping filter policy file:
#
entry mldFilter {
if match any {
#------------------ Start of group addresses -----------------nlri FF03::1/128;
nlri FF05::1/112;
deny;
}
}
entry catch_all {
if {
} then {
permit;
}
Multicast
131
Multicast Commands
Example
The following example configures the policy file ap_multicast to filter multicast packets forwarded to
configure mld snooping marketing ports 2:1-2:4 filter ap_multicast
History
configure mld snooping vlan ports join-limit

configure mld snooping {vlan} vlan_name ports port_list join-limit [num_joins |
no-limit]
Description
Configures VLAN ports to support a maximum number of MLD joins.
Syntax Description
vlan_name
Specifies a VLAN name
port_list
num
Specifies the maximum number of joins permitted on the ports. The range is 1
to 5000.
Default
No limit.
Usage Guidelines
None.
Example
The following example configures port 2:1 in the Default VLAN to support a maximum of 100 MLD joins:
configure mld snooping "Default" ports 2:1 join-limit 100
Multicast
132
Multicast Commands
History

configure mld ssm-map add v6groupnetmask [v6sourceip | src_domain_name] { {vr}
vr_name }
Description
Adds an MLD SSM Mapping entry on a VR.
Syntax Description
v6groupnetmask
You must provide group address with the mask length. Instead of configuring
separate entries for a continuous range of IP addresses, this optimizes a range
of group IP addresses to be configured as a single entry.
v6sourceip
Specifies the source IP address for which the SSM should apply.
src_domain_name
Provides the option to use DNS to obtain IP addresses dynamically by

specifying the domain name.
VR vr_name
Specifies the virtual router name.
Default
Disabled.
Usage Guidelines
When an MLDv1 report is received for this group or group range, the list of sources configured using
this command is used as part of source-specific information to PIM.
Using this command displays the following error message when PIMv6 is enabled:
ERROR: PIM IPv6 should be disabled before configuring MLD ssm-map on VR-Default
The following error message displays when more than 50 source addresses are configured for a
specific group:
ERROR: Cannot configure more than 50 sources for group ff30::1/128 on VR-Default
The following error message displays when a source address is already configured:
ERROR: Source 2001:0DB8:1::1 already present for group ff30::1/128 on VR-Default
Multicast
133
Multicast Commands
The following error message displays when a DNS name is already configured:
ERROR: Only one source domain name allowed for group ff30::1/128 on VR-Default
Example
The following command configures :
History

configure mld ssm-map delete v6groupnetmask [v6sourceip | src_domain_name | all]
{{vr} vr_name}
Description
Deletes an MLD SSM Mapping entry on a VR.
Syntax Description
v6groupnetmask
You must provide group address with the mask length. Instead of configuring
separate entries for a continuous range of IP addresses, this optimizes a range
of group IP addresses to be configured as a single entry.
v6sourceip
Specifies the source IP address for which the SSM should apply.
src_domain_name
Provides the option to use DNS to obtain IP addresses dynamically by

specifying the domain name.
all
Specifies that all the mapping entries associated with v6groupnetmask are
deleted.
vr vr_name
Default
Disabled.
Multicast
134
Multicast Commands
Usage Guidelines
When an MLDv1 report is received for this group or group range, the list of sources configured using
this command is used as part of source-specific information to PIM.
The following error message displays when specified entry is not found:
ERROR: SSM Mapping entry (ff30::1/128, 2001:0DB8:1::10) not found on VR-Default
Example
The following command deletes :
History
configure msdp as-display-format

configure msdp as-display-format [asdot | asplain]
Description
Configures the AS number format displayed in show commands.
Syntax Description
asdot
Specifies the ASDOT format.
asplain
Specifies the ASPLAIN format.
Default
N/A.
Usage Guidelines
The ASPLAIN and ASDOT formats are described in RFC 5396, Textual Representation of Autonomous
System (AS) Numbers.
Multicast
135
Multicast Commands
Example
The following command selects the ASDOT 4-byte AS number format:
configure msdp as-display-format asdot
History
configure msdp max-rejected-cache

configure msdp max-rejected-cache max-cache {vr vrname}
Description
Configures the maximum limit on rejected SA cache entries that an MSDP router will store in its
database.
Syntax Description
max-cache
Specifies the maximum number of rejected SA cache entries that the MSDP router will
store in its database. To remove the limit, enter 0 (zero) for the max-cache value.
vrname
Default
By default, the maximum cache entries stored is zero. That is, rejected SA cache entries are not stored.
Any SA cache entries that are stored and not refreshed for six minutes are removed.
Usage Guidelines
SA cache are rejected because of:
Peer-RPF failure
Policy denied
When a previously rejected SA cache entry is accepted because of an RP reachability change or policy
rule change, the rejected SA cache entry is moved to the accepted SA cache list.
By default, rejected SA cache entries are discarded. You can configure a limit for rejected cache entries
to store them, which will help debug/diagnose some issues; however, it consumes extra memory.
Multicast
136
Multicast Commands
Example
The following command sets the maximum rejected cache limit to 100 for an MSDP router:
configure msdp max-rejected-cache 100
History
the MSDP feature,see the Feature License Requirements document.
configure msdp originator-id

configure msdp originator-id ip-address {vr vrname}
Description
Configures the originator ID for an MSDP router. The originator ID is the RP address you want to use
(instead of the default) in locally originated SA messages.
Syntax Description
ip-address
Specifies the RP address to use in locally originated SA messages. To unconfigure an

originator ID (that is, to use the default RP address), enter the IP address 0.0.0.0.
vrname
Default
By default, the RP address is used as the originator ID in locally originated SA messages.
Usage Guidelines
Use this command to override the default RP address used in SA messages. Because only RPs and
MSDP border routers originate SAs, there are times when it is necessary to change the ID used for this
purpose. The originator ID address must be one of the interface addresses on the MSDP router.
You can configure the MSDP originator ID only when MSDP is disabled globally.
To remove an originator ID, enter the IP address 0.0.0.0.
Multicast
137
Multicast Commands
Example
The following example configures the originator ID for an MSDP router:
configure msdp originator-id 10.203.134.1
The following example unconfigures the originator ID for an MSDP router:

configure msdp originator-id 0.0.0.0
History
configure msdp peer default-peer

configure msdp peer [remoteaddr | all] default-peer {default-peer-policy filtername} {vr vrname}
Description
This command configures a default or static RPF peer from which all MSDP SA messages are accepted.
To remove the default peer, enter the configure msdp peer no-default-peer command.
Syntax Description
filter-name
Specifies the name of the policy filter associated with the default peer. The peer will be
the default peer for all SA entries that are permitted by the policy filter. If an SA message
is allowed by the policy filter, it will be accepted. Otherwise, the SA message has to go
through the regular RPF-check. The static peer RPF check is the last step in peer RPF
algorithm. So, if an SA message is denied by the default peer policy, ultimately the SA
message will be rejected by MSDP.
peer all
remoteaddr
vrname
Default
By default, no static RPF peer is configured.
Multicast
138
Multicast Commands
The default-peer-policy keyword specifies the name of the policy filter associated with the default
peer. You can configure multiple default peers with different policies. If no policy is specified, then the
current peer is the default RPF peer for all SA messages.
Usage Guidelines
Configuring a default peer simplifies peer-RPF checking of SA messages. If the peer-RPF check fails,
the default peer rule is applied to see if the SA messages should be accepted or rejected.
If a default peer policy is specified, the peer is the default peer only for the (Source, Group), or (S, G),
that satisfies the policy. If the policy is not specified, then the default peer is used for all (S, G, RP).
You can configure multiple default peers on an MSDP router; however, all default peers must either
have a default policy or not. A mix of default peers, with a policy and without a policy, is not allowed.
When configuring multiple default peer rules, follow these guidelines:
When you enter multiple default-peer commands with the default-peer-policy keyword, you can
use all the default peers at the same time for different RP prefixes.
When you enter multiple default-peer commands without the default-peer-policy keyword, you can
use a single active peer to accept all SA messages. If that peer goes down, then the next configured
default peer accepts all SA messages. This configuration is typically used at a stub site.
You can use the following policy attributes in a default peer policy. All other attributes are ignored.
Match:
multicast-group
multicast-source
pim-rp
Set:
permit.
deny.
Example
The following example configures an MSDP peer with the IP address 192.168.45.43 as the default peer
policy for "sales":
configure msdp peer 192.168.45.43 default-peer default-peer-policy sales
History
Multicast
139
Multicast Commands
configure msdp peer description

configure msdp peer remoteaddr description {peer-description} {vr vrname}
Description
Configures a name or description for an MSDP peer. This text is for display purposes only.
Syntax Description
remoteaddr
peer-description
Specifies the name or description of the MSDP peer. The maximum is 63 characters.
vrname
Specifies the name of the virtual router to which this command applies. If a name is
not specified, it is extracted from the current CLI context.
Default
By default, no name or description is specified.
Usage Guidelines
Use this command to configure a name or description to make an MSDP peer easier to identify. The
description is visible in the output of the show msdp peer command.
To remove the description, use this command without a description string.
Example
The following example configures the name "internal_peer" to an MSDP peer:
configure msdp peer 192.168.45.43 description internal_peer
The following example removes the description from an MSDP peer:

configure msdp peer 192.168.45.43 description
History
Multicast
140
Multicast Commands
configure msdp peer mesh-group

configure msdp peer [remoteaddr | all] mesh-group [mesh-group-name | none] {vr
vrname}
Description
This command configures an MSDP peer to become a member of a mesh-group. To remove a peer
from a mesh-group, enter the none CLI keyword for the mesh-group.
Syntax Description
mesh-group-name
Specifies the name of the MSDP mesh-group.
none
Removes a peer from a mesh-group.
peer all
remoteaddr
vrname
Default
N/A.
Usage Guidelines
A mesh-group is a group of MSDP peers with fully meshed MSDP connectivity. Any SA messages
received from a peer in a mesh-group are not forwarded to other peers in the same mesh-group.
Mesh-groups achieve two goals:
Reduce SA message flooding.
Simplify peer-RPF flooding.
Example
The following example configures an MSDP peer with the IP address 192.168.45.43 to become a
member of a mesh-group called "intra":
configure msdp peer 192.168.45.43 mesh-group intra
History
Multicast
141
Multicast Commands
configure msdp peer no-default-peer

configure msdp peer [remoteaddr | all] no-default-peer {vr vrname}
Description
This command removes a default peer.
Syntax Description
peer all
remoteaddr
no-default-peer
Removes a default peer.
vrname
Default
N/A.
Usage Guidelines
None.
Example
The following command removes all MSDP peers:
configure msdp peer all no-default-peer
History
Multicast
142
Multicast Commands
configure msdp peer password

configure msdp peer [remoteaddr | all] password [none | {encrypted} tcpPassword]
{vr vrname}
Description
This command configures a TCP RSA Data Security, Inc. MD5 Message-Digest Algorithm password for
an MSDP peer.This command enables TCP RSA Data Security, Inc. MD5 Message-Digest Algorithm
authentication for a MSDP peer. When a password is configured, MSDP receives only authenticated
MSDP messages from its peers. All MSDP messages that fail TCP RSA Data Security, Inc. MD5 MessageDigest Algorithm authentication are dropped.
Syntax Description
peer all
remoteaddr
none
Removes the previously configured password.
encrypted
Encrypts the password for RSA Data Security, Inc. MD5 Message-Digest Algorithm
authentication. To improve security, the password displays in encrypted format and
cannot be seen as simple text. Additionally, the password is saved in encrypted format.
tcpPassword
Specifies the password to use for RSA Data Security, Inc. MD5 Message-Digest
Algorithm authentication at the TCP level. The password must be an ASCII string with a
maximum of 31 characters.
vrname
Defaults
By default, TCP RSA Data Security, Inc. MD5 Message-Digest Algorithm authentication is disabled for
the MSDP peer.
Usage Guidelines
We recommend that you enable TCP RSA Data Security, Inc. MD5 Message-Digest Algorithm
authentication for all MSDP peers to protect MSDP sessions from attacks. You can execute this
command only when the MSDP peer is disabled or when MSDP is globally disabled on that VR.
Example
The following example configures a password for the MSDP peer with the IP address 192.168.45.43,
which automatically enables TCP MD5 authentication:
configure msdp peer 192.168.45.43 password test123
Multicast
143
Multicast Commands
The following command removes the password:

configure msdp peer 192.168.45.43 password none
History
configure msdp peer sa-filter

configure msdp peer [remoteaddr | all] sa-filter [in | out] [filter-name | none]
{vr vr_name}
Description
This command configures an incoming or outgoing policy filter for SA messages.
Syntax Description
peer all
remoteaddr
in
Associates the SA filter with inbound SA messages.
out
Associates the SA filter with outbound SA messages.
filter-name
Specifies the name of the policy associated with an SA filter. To remove an SA filter,
enter the none CLI keyword instead of filter-name.
vr_name
Default
By default, no SA filter is configured for an MSDP peer. That is, incoming and outgoing SA messages
are not filtered.
Usage Guidelines
This command configures an SA filter such that only a specified set of SA messages are accepted or
sent to a peer. Note that an SA filter does not adversely impact the flow of SA request and response
messages.
To remove an SA filter, enter the none CLI keyword instead of filter-name.
Multicast
144
Multicast Commands
You can use the following policy attributes in an SA filter policy. All other attributes are ignored.
Match:
multicast-group
multicast-source
pim-rp
Set:
permit
deny
Example
The following example configures an incoming SA messages filter on an MSDP peer with the IP address
192.168.45.43:
configure msdp peer 192.168.45.43 sa-filter in allow_229
History
configure msdp peer sa-limit

configure msdp peer [remoteaddr | all] sa-limit max-sa {vr vr_name}
Description
This command allows you to limit the number of SA entries from an MSDP peer that the router will
allow in the SA cache. To allow an unlimited number of SA entries, use 0 (zero) as the value for maxsa.
Syntax Description
peer all
remoteaddr
max-sa
Specifies the maximum number of SA entries from an MSDP peer allowed in the SA
cache. To specify an unlimited number of SA entries, use 0 (zero) as the value for
max-sa.
vr_name
Multicast
145
Multicast Commands
Default
By default, no SA entry limit is set. The router can receive an unlimited number of SA entries from an
MSDP peer.
Usage Guidelines
You can use this command to prevent a distributed denial of service (DOS) attack. We recommend that
you configure an MSDP SA limit on all MSDP peer sessions. Note that a rejected SA cache entry is not
included in the number of SA cache entries received from a peer.
Example
The following example configures the SA entry limit of 500 for the MSDP peer with the IP address
192.168.45.43:
configure msdp peer 192.168.45.43 sa-limit 500
History
configure msdp peer source-interface

configure msdp peer [remoteaddr | all] source-interface [ipaddress | any] {vr
vrname}
Description
This command configures the source interface for the MSDP peer TCP connection.
Syntax Description
peer all
remoteaddr
ipaddress
Specifies the IP address of the MSDP router interface to use on one end of a TCP
connection. The ipaddress must be one of the MSDP router interface addresses;
otherwise, the command fails and an error message displays.
Multicast
146
Multicast Commands
any
Specifies to use any interface as one end of the TCP connection. The source
interface is selected based on the IP route entry used to reach the MSDP peer.
The egress interface that reaches the MSDP peer is used as the source interface
for the TCP connection. Basically, this command removes the previously
configured source interface of the MSDP peer.
vrname
Specifies the name of the virtual router to which this command applies. If a name
is not specified, it is extracted from the current CLI context.
Defaults
By default, the source interface is selected based on the IP route entry used to reach the MSDP peer.
The egress interface that reaches the MSDP peer is used as the source interface for the TCP connection.
Usage Guidelines
You must first disable MSDP or the MSDP peer before using this command. We recommend that you
configure a source interface for MSDP peers that are not directly connected. We also recommend using
the loopback address as the MSDP peer connection endpoint.
Example
The following example configures a source interface for an MSDP peer with the IP address
192.168.45.43:
configure msdp peer 192.168.45.43 source-interface 60.0.0.5
History
configure msdp peer timer

configure msdp peer [remoteaddr | all] timer keep-alive keep-alive-sec hold-time
hold-time-sec {vr vrname}
Description
The command configures the keep-alive and hold timer intervals of the MSDP peers.
Multicast
147
Multicast Commands
Syntax Description
peer all
remoteaddr
keep-alive-sec
Specifies the keep-alive timer interval in seconds. The range is160 seconds.
hold-time-sec
Specifies the hold timer interval in seconds. The range is 375 seconds.
vrname
Default
By default, the:
Keep-alive timer interval is 60 seconds.
Hold timer interval is 75 seconds.
SA timer interval is 60 seconds.
Usage Guidelines
You can use this command only when either MSDP or the MSDP peer is disabled. The hold timer
interval must be greater than the keep-alive timer interval.
Example
The following example configures the keep-alive and hold timer intervals for the MSDP peer 55.0.0.83:
configure msdp peer 55.0.0.83 timer keep-alive 30 hold-time 60
History
configure msdp peer ttl-threshold

configure msdp peer [remoteaddr | all] ttl-threshold ttl {vr vrname}
Description
Configures the limit to which multicast data packets are sent in SA messages to an MSDP peer. If the
time-to-live (TTL) in the IP header of an encapsulated data packet exceeds the TTL threshold
configured, encapsulated data is not forwarded to MSDP peers.
Multicast
148
Multicast Commands
Syntax Description
remoteaddr
Specifies the IP address of the MSDP peer on which to configure a TTL threshold.
all
ttl
Specifies the TTL value. The range is 0255. To restore the default value, enter a TTL
value of 0 (zero).
vrname
Default
The default value is zero, meaning all multicast data packets are forwarded to the peer regardless of
the TTL value in the IP header of the encapsulated data packet.
Usage Guidelines
This command allows you to configure a TTL value to limit multicast data traffic.
Example
The following example configures a TTL threshold of 5:
configure msdp peer 192.168.45.43 ttl-threshold 5
History
configure msdp sa-cache-server

configure msdp sa-cache-server remoteaddr {vr vr_name}
Description
Configures the MSDP router to send SA request messages to the MSDP peer when a new member
becomes active in a group.
Multicast
149
Multicast Commands
Syntax Description
remoteaddr
Specifies the IP address of the MSDP peer from which the local router requests SA
messages when a new member becomes active in a group, and MSDP has no cache entry
for the group in the local database.
vr_name
Specifies the name of the virtual router on which the MSDP cache server is configured. If a
virtual router name is not specified, it is extracted from the current CLI context.
Default
By default, the router does not send SA request messages to its MSDP peers when a new member joins
a group and wants to receive multicast traffic. The new member simply waits to receive SA messages,
which eventually arrive.
Usage Guidelines
You can use this command to force a new member of a group to learn the current active multicast
sources in a connected PIM-SM domain that are sending to a group. The router will send SA request
messages to the specified MSDP peer when a new member joins a group and MSDP doesnt have a
cache entry for that group in the local database. The peer replies with the information in an SA cache
response message.
Note
An MSDP peer must exist before it can be configured as an SA cache server. The configure
msdp sa-cache-server command accepts the value for remoteaddr only if it is an existing
peers IP address.
Example
The following example configures an MSDP cache server:
configure msdp sa-cache-server 172.19.34.5
History
configure mvr add receiver

configure mvr vlan vlan-name add receiver port port-list
Multicast
150
Multicast Commands
Description
Configures a port to receive MVR multicast streams.
Syntax Description
vlan-name
port-list
A list of ports or slots and ports.
Default
N/A.
Usage Guidelines
This command is used to add a group of virtual ports for multicast forwarding through MVR. By default,
some ports on non-MVR VLANs (router ports, primary and secondary EAPS ports), are excluded from
the MVR cache egress list. This command is used to override these rules, so that if valid IGMP
memberships are received, or a router is detected, streams are forwarded out on the ports.
Example
The following example adds the ports 1:1 and 1:2 of VLAN v1 to MVR for forwarding:
configure mvr vlan v1 add receiver port 1:1-1:2
History
the MVR feature, see the Feature License Requirements document.
configure mvr add vlan

configure mvr add vlan vlan-name
Description
Configures a VLAN as an MVR VLAN.
Multicast
151
Multicast Commands
Syntax Description
vlan-name
Default
N/A.
Usage Guidelines
Configures MVR on the specified VLAN. When a multicast stream in the specified MVR address range is
received on the VLAN, it is leaked to all other VLAN ports where the corresponding IGMP join message
is received. By default, the entire multicast address range 224.0.0.0/4, except for the multicast control
range 224.0.0.0/24 is used for MVR. To change the MVR address range, use the following command:
Example
The following example configures VLAN v1 as an MVR VLAN:
configure mvr add vlan v1
History
configure mvr delete receiver

configure mvr vlan vlan-name delete receiver port port-list
Description
Configures a port not to receive MVR multicast streams.
Syntax Description
vlan-name
port-list
A list of ports or slots and ports.
Multicast
152
Multicast Commands
Default
N/A.
Usage Guidelines
This command is used to delete a group of virtual ports for multicast forwarding through MVR. After
using this command, the ports revert to the default forwarding rules.
Example
The following example deletes the ports 1:1 and 1:2 of VLAN v1 to MVR for forwarding:
configure mvr vlan v1 delete receiver port 1:1-1:2
History
configure mvr delete vlan

configure mvr delete vlan vlan-name
Description
Deletes a VLAN from MVR.
Syntax Description
vlan-name
Default
N/A.
Usage Guidelines
Removes MVR from the specified VLAN.
Multicast
153
Multicast Commands
Example
The following example configures VLAN v1 as a non-MVR VLAN:
configure mvr delete vlan v1
History
configure mvr mvr-address

Description
Configures the MVR address range on a VLAN.
Syntax Description
vlan-name
policy-name
Specifies a policy file.
Default
The default address range is 224.0.0.0/4 (all multicast addresses), but excluding 224.0.0.0/24 (the
multicast control range).
Usage Guidelines
If no policy file is specified (the none option), the entire multicast address range 224.0.0.0/4, except for
the multicast control range 224.0.0.0/24 is used for MVR.
MVR must first be configured on the VLAN before using this command.
If the policy is later refreshed, groups denied and newly allowed groups in the policy are flushed from
fast path forwarding. This allows synching existing channels with the new policy, without disturbing
existing channels.
Multicast
154
Multicast Commands
The following is a sample policy file mvrpol.pol. This policy configures 236.1.1.0/24 as the MVR address
range. Any address outside this range has the standard switching behavior on an MVR VLAN.
Entry extreme1 {
if match any {
nlri 236.1.1.0/24 ;
}
then {
permit ;
}
}
Example
The following example configures the MVR address range specified in the policy file mvrpol.pol for the
VLAN v1:
configure mvr vlan v1 mvr-address mvrpol
History
configure mvr static group

configure mvr vlan vlan-name static group {policy-name | none}
Description
Configures the MVR static group address range on a VLAN.
Syntax Description
vlan-name
policy-name
Specifies a policy file.
Default
By default, all the MVR group addresses work in static mode.
Multicast
155
Multicast Commands
Usage Guidelines
If no policy file is specified (the none option), the entire multicast address range 224.0.0.0/4, except for
the multicast control range 224.0.0.0/24, is used for static groups in MVR.
MVR must first be configured on the VLAN before using this command.
The following is a sample policy file mvrpol.pol. This policy configures 236.1.1.0/24 as the MVR static
group address range. Any MVR addresses outside this range are dynamically registered through IGMP.
An MVR VLAN will proxy join only for addresses that are not in the static group. If you want all the
multicast groups to by dynamic, use a policy file with this command that denies all multicast addresses.
Entry extreme1 {
if match any {
nlri 236.1.1.0/24 ;
}
then {
permit ;
}
}
Example
The following example configures the MVR static group address range specified in the policy file
mvrpol.pol for the VLAN v1:
configure mvr vlan v1 static group mvrpol
History
configure pim add vlan

configure pim {ipv4 | ipv6} add vlan [vlan-name | all] {dense | sparse} {passive}
Description
Configures an IP interface for PIM.
Multicast
156
Multicast Commands
Syntax Description
ipv4
Specifies the IPv4 address family.
ipv6
vlan-name
all
Specifies all VLANs.
dense
Specifies PIM dense mode (PIM-DM).
sparse
Specifies PIM sparse mode (PIM-SM).
passive
Specifies a passive interface.
Default
Dense.
Usage Guidelines
When an IP interface is created, per-interface PIM configuration is disabled by default.
The switch supports both dense mode and sparse mode operation. You can configure dense mode or
sparse mode on a per-interface basis. After they are enabled, some interfaces can run dense mode,
while others run sparse mode.
Passive interfaces are host only interfaces that allow a multicast stream from other VLANs to be
forwarded to edge hosts. Since they do not peer with other PIM routers, you should not connect a
multicast router to a passive interface.
In order for the interface to participate in PIM, PIM must be enabled on the switch using the following
command: enable pim
Example
The following example enables PIM-DM multicast routing on VLAN accounting:
configure pim add vlan accounting dense
History
The passive option was added in ExtremeXOS 11.1.
The IPv4 and IPv6 options were added in ExtremeXOS 15.3.
Multicast
157
Multicast Commands
configure pim border

configure pim {ipv4 | ipv6} [{vlan} vlan_name | vlan all] border
Description
Configures a PIM VLAN as a border VLAN, which is used to demarcate a PIM domain when using MSDP.
Syntax Description
ipv4
Configures a PIM timer on IPv4 router interfaces.
ipv6
vlan_name
vlan all
border
Interface is domain border.
Default
None.
Usage Guidelines
MSDP is used to connect multiple multicast routing domains. A PIM-SM domain is created by
limitingthe reach of PIM BSR advertisements. When a border VLAN is configured, PIM BSR
advertisements are not forwarded out of the PIM VLAN.
Example
The following example configures a PIM border on a VLAN called "vlan_border":
configure pim vlan_border border
History
The ipv4 and ipv6 keywords were added giving an option to support this functionality in IPv6 as well
in ExtremeXOS 15.3.
Multicast
158
Multicast Commands
the PIM feature, see the ExtremeXOS User Guide.
configure pim cbsr

configure pim cbsr {ipv4 | ipv6} [{vlan} vlan_name {priority [0-254]} | none]
Description
Configures a candidate bootstrap router for PIM sparse-mode operation.
Syntax Description
ipv4
ipv6
vlan_name
priority
Specifies a priority setting. The range is 0 - 254.
none
Deletes a CBSR.
Default
The default setting for priority is 0, and indicates the lowest priority.
Usage Guidelines
The VLAN specified for CBSR must have PIM enabled for it to take effect. After PIM is enabled, CBSRs
advertise themselves in the PIM domain. A bootstrap router (BSR) is elected among all the candidates
based on CBSR priority. To break the tie among routers with the same priority setting, the router with
the numerically higher IP address is chosen.
An ExtremeXOS switch can support up to 145 RPs per group when it is configured as a PIM BSR
(bootstrap router). If more than 145 RPs are configured for a single group, the BSR ignores the group
and does not advertise the RPs. Non-BSR switches can process more than 145 RPs in the BSR message.
Example
The following example configures a candidate bootstrap router on the VLAN accounting:
configure pim cbsr vlan accounting 30
History
Multicast
159
Multicast Commands
configure pim crp static

configure pim {ipv4 | ipv6} crp static ip_address [none | policy] {priority
[0-254]}
Description
Configures a rendezvous point and its associated groups statically, for PIM sparse mode operation.
Syntax Description
ipv4
ipv6
ip_address
Specifies a static CRP address.
none
Deletes the static rendezvous point.
policy
Specifies a policy file name.
priority
Specifies a priority setting. The range is 0 - 254.
Default
The default setting for priority is 0, which indicates highest priority.
Usage Guidelines
In PIM-SM, the router sends a join message to the rendezvous point (RP). The RP is a central multicast
router that is responsible for receiving and distributing multicast packets. If you use a static RP, all
switches in your network must be configured with the same RP address for the same group (range).
ExtremeXOS switches support up to 50 RPs in a switch, and up to 180 groups (group/mask entries) in a
single RP policy file. If you configure more than 180 group entries in a single RP policy file, the switch
will not process entries added after the first 180.
The policy file contains a list of multicast group addresses served by this RP.
This policy file is not used for filtering purposes. As used with this command, the policy file is just a
container for a list of addresses. So a typical policy file used for RP configuration looks a little different
from a policy used for other purposes.
If routers have different group-to-RP mappings, due to misconfiguration of the static RP (or any other
reason), traffic is disrupted.
Multicast
160
Multicast Commands
Example
The following example statically configures an RP and its associated groups defined in policy file rp-list:
configure pim crp static 10.0.3.1 rp-list
The following is a sample policy file:

entry extreme1 {
if match any { }
then { nlri 224.0.0.0/4 ;
nlri 239.255.0.0/24 ;
nlri 232.0.0.0/8 ;
nlri 238.1.0.0/16 ;
nlri 232.232.0.0/20 ;
}
}
History
configure pim crp timer

configure pim {ipv4 | ipv6} crp timer crp_adv_interval
Description
Configures the candidate rendezvous point advertising interval in PIM sparse mode operation.
Syntax Description
ipv4
ipv6
crp_adv_interval
Specifies a candidate rendezvous point advertising interval in seconds. The

range is 1 to 1,717,986,918.
Default
The default is 60 seconds.
Multicast
161
Multicast Commands
Usage Guidelines
Increasing this time results in increased convergence time for CRP information to the PIM routers.
Example
The following example configures the candidate rendezvous point advertising interval to 120 seconds:
configure pim crp timer 120
History
configure pim crp vlan

configure pim {ipv4 | ipv6} crp vlan vlan_name [none | policy] {priority}
Description
Configures the dynamic candidate rendezvous point (CRP) for PIM sparse-mode operation.
Syntax Description
ipv4
ipv6
vlan_name
none
Specifies to delete a CRP.
policy
priority
Specifies a priority setting. The range is 0254.
Default
The default setting for priority is 0 and indicates the highest priority.
Usage Guidelines
ExtremeXOS switches support up to 50 RPs in a switch, and up to 180 groups (group/mask entries) in a
single RP policy file. If you configure more than 180 group entries in single RP policy file, then the switch
will not process entries added after first 180.
Multicast
162
Multicast Commands
The policy file contains the list of multicast group addresses serviced by this RP. This set of group
addresses are advertised as candidate RPs. Each router then elects the common RP for a group
address based on a common algorithm. This group to RP mapping should be consistent on all routers.
This policy file is not used for filtering purposes. As used with this command, the policy file is just a
container for a list of addresses. So a typical policy file used for RP configuration looks a little different
from a policy used for other purposes. The following is a sample policy file that configures the CRP for
the address ranges 239.0.0.0/24 and 232.144.27.0/24:
entry extreme1 {
if match any {
}
then {
nlri 239.0.0.0/24 ;
nlri 232.144.27.0/24 ;
}
}
The VLAN specified for a CRP must have PIM configured.

To delete a CRP, use the keyword none as the access policy.
Example
The following example configures the candidate rendezvous point for PIM sparse-mode operation on
the VLAN HQ_10_0_3 with the policy rp-list and priority set to 30:
configure pim crp HQ_10_0_3 rp-list 30
History
configure pim delete vlan

configure pim delete vlan [vlanname | all]
Description
Disables PIM on a router interface.
Multicast
163
Multicast Commands
Syntax Description
vlanname
all
Default
N/A.
Usage Guidelines
None.
Example
The following example disables PIM on VLAN accounting:
configure pim delete vlan accounting
History
configure pim dr-priority

configure pim {ipv4 | ipv6} [ {vlan} vlan_name | vlan all ] dr-priority priority
Description
Configures the designated router (DR) priority that is advertised in PIM hello messages.
Syntax Description
ipv4
IPv4 address family (default).
ipv6
IPv6 address family.
vlan all
Apply to all VLANs.
dr-priority
Designated Router Priority for VLAN.
priority
Priority value for VLAN (default 1). The range is 14294967295.
Multicast
164
Multicast Commands
Default
The default setting for dr-priority is 1.
Usage Guidelines
The dr-priority option allows a network administrator to give preference to a particular router in the
DR election process by giving it a numerically larger DR priority. The dr-priority option is included in
every hello message, even if no DR priority is explicitly configured on that interface. This is necessary
because priority-based DR election is only enabled when all neighbors on an interface advertise that
they are capable of using the dr-priority option.
The DR priority is a 32-bit unsigned number, and the numerically larger priority is always preferred. A
router's idea of the current DR on an interface can change when a PIM hello message is received, when
a neighbor times out, or when a router's own DR priority changes. If the router becomes the DR or
ceases to be the DR, this will normally cause the DR register state machine to change states.
Subsequent actions are determined by that state machine. The DR election process on interface is as
follows:
If any one of the neighbor on the interface is not advertised the DR priority (not DR capable) then
DR priority will not considered for the all the neighbors in the circuit, and the primary IP address will
be considered for all the neighbors.
The higher DR priority or higher primary address will be elected as DR.
Example
configure pim ipv4 vlan accounting dr-priority 10
History
configure pim iproute sharing hash

configure pim {ipv4 | ipv6} iproute sharing hash [source | group | source-group |
source-group-nexthop]
Description
This command is used to configure the PIM ECMP hash algorithm.
Multicast
165
Multicast Commands
Syntax Description
ipv4
ipv6
hash
Configure Hash Algorithm for Equal Cost Multipath Routing.
source
Hash for route sharing is based on source address only.
group
Hash for route sharing is based on group address only.
source-group
Hash for route sharing is based on source and group addresses.
source-group-nexthop
Hash for route sharing is based on source, group, and next hop
addresses (default).
Default
Source-group-nexthop.
Usage Guidelines
None.
Example
The following command configures the PIM ECMP hash algorithm based on source-group-nexthop:
configure pim ipv6 iproute sharing hash source-group-nexthop
History
This command is available on platforms that support the appropriate license. All platforms except
Summit X440 support IP route sharing in ExtremeXOS 15.3.2. For complete information about software
licensing, including how to obtain and upgrade your license and which licenses support the PIM feature,
see the Feature License Requirements document.
configure pim register-policy rp

configure pim {ipv4 | ipv6} register-policy rp [rp_policy_name | none]
Description
Configures the register filter at the Rendezvous Point.
Multicast
166
Multicast Commands
Syntax Description
ipv4
ipv6
rp_policy_name
Specifies the Policy File for RP Register filter.
none
Unconfigures the configured RP Register filter.
Default
N/A.
Usage Guidelines
None.
Example
The following example configures IPv4 register policy named "entry_policy":
configure pim ipv4 register-policy rp entry_policy
History
configure pim register-policy

configure pim {ipv4 | ipv6} register-policy [rp_policy_name | none]
Description
Configures the register filter at the First Hop Router (FHR).
Syntax Description
ipv4
ipv6
rp_policy_name
Specifies the Policy File for Register filter.
none
Unconfigures the configured RP Register filter.
Multicast
167
Multicast Commands
Default
IPv4.
Usage Guidelines
None.
Example
The following example configures an IPv4 register policy named "entry_policy" at the FHR:
configure pim ipv4 register-policy entry_policy
History
configure pim register-checksum-to

configure pim {ipv4 | ipv6} register-checksum-to [include-data | exclude-data]
Description
Configures the checksum computation to either include data (for compatibility with Cisco Systems
products) or to exclude data (for RFC-compliant operation), in the register message.
Syntax Description
ipv4
ipv6
include-data
Specifies to include data.
exclude-data
Specifies to exclude data.
Default
Exclude data.
Multicast
168
Multicast Commands
Usage Guidelines
None.
Example
The following example configures the checksum mode to include data for compatibility with Cisco
Systems products:
configure pim register-checksum-to include-data
History
configure pim register-rate-limit-interval

configure pim {ipv4 | ipv6} register-rate-limit-interval interval
Description
Configures the initial PIM-SM periodic register rate.
Syntax Description
ipv4
ipv6
interval
Specifies an interval time in seconds. Range is 0 - 60. Default is 0.
Default
The default interval is 0.
Usage Guidelines
Configuring a non-zero interval time can reduce the CPU load on the first hop switch, in case register
stop messages are not received normally.
When a non-zero value is configured, the first hop switch sends a few register messages and then waits
for a corresponding register stop from the RP for time seconds. The process is repeated until the
Multicast
169
Multicast Commands
register stop is received. This command should be used when the (S,G) tree between the first hop
router and the RP is not converging quickly.
When the default value is zero in default mode, the switch sends continuous register messages until the
register stop is received.
Example
The following example configures the initial PIM register rate limit interval:
configure pim register-rate-limit-interval 2
History
configure pim register-suppress-interval register-probe-interval

configure pim {ipv4 | ipv6} register-suppress-interval reg-interval registerprobe-interval probe_interval
Description
Configures an interval for periodically sending null-registers.
Syntax Description
ipv4
ipv6
reg-interval
Specifies an interval time in seconds. Range is 30 - 200 seconds. Default is 60.
probe-interval
Specifies an interval time in seconds. Default is 5.
Default
The following defaults apply:
register-suppress-interval60
register-probe-interval5
Multicast
170
Multicast Commands
Usage Guidelines
The register-probe-interval time should be set less than the register-suppress-interval time. By default,
a null register is sent every 55 seconds (register-suppress-interval register-probe-interval). A
response to the null register is expected within register probe interval. By specifying a larger interval, a
CPU peak load can be avoided because the null-registers are generated less frequently. The register
probe time should be less than half of the register suppress time, for best results.
Example
The following example configures the register suppress interval and register probe time:
configure pim register-suppress-interval 90 register-probe time 10
History
configure pim shutdown-priority

configure pim {ipv4 | ipv6} [ {vlan} vlan_name | vlan all ] shutdown-priority
number
Description
Configures the priority for out of memory shutdown.
Syntax Description
ipv4
ipv6
vlan_name
all
number
Priority for VLAN range is [0 - 65535].
Default
IPv4.
Multicast
171
Multicast Commands
Usage Guidelines
None.
Example
The following example configures the shutdown priority for VLAN 36:
config pim vlan v36 shutdown-priority 22
History
The ipv4 and ipv6 keywords were added giving an option to support this functionality in IPv6 as well
in ExtremeXOS 15.3.
configure pim spt-threshold

configure pim {ipv4 | ipv6} spt-threshold leaf-threshold {rp_threshold}
Description
Configures the threshold, in kbps, for switching to SPT. On leaf routers, this setting is based on data
packets. On the RP, this setting is based on register packets.
Syntax Description
ipv4
ipv6
leaf-threshold
Specifies the rate of traffic per (s,g,v) group in kbps for the last hop. Range is
0 - 419403.
rp_threshold
Specifies an RP threshold. Range is 0 - 419403.
Default
The default setting is 0 for both parameters.
Usage Guidelines
For the best performance, use default value of 0.
Multicast
172
Multicast Commands
Example
The following example changes the threshold for switching to SPT:
configure pim spt-threshold 4 16
History
configure pim ssm range

configure pim {ipv4 | ipv6} ssm range [default | policy policy-name]
Description
Configures the range of multicast addresses for PIM SSM.
Syntax Description
ipv4
ipv6
default
Specifies the default address range, 232.0.0.0/8.
policy-name
Specifies a policy that defines the SSM address range.
Default
By default, no SSM range is configured. Using this command with the default keyword sets the range to
232.0.0.0/8. To reset the switch to the initial state, use the unconfigure pim ssm range
command.
Usage Guidelines
You must disable PIM before configuring or unconfiguring a PIM-SSM range. Use the disable pim
command.
Initially, no range is configured for SSM. After a range is configured, you can remove the range with the
unconfigure pim ssm range command. If you wish to change the PIM SSM range, you must first
unconfigure the existing range, and then configure the new range.
Multicast
173
Multicast Commands
SSM requires that hosts use IGMPv3 messages to register to receive multicast group packets. When a
range is configured for SSM, any IGMPv2 messages for an address in the range are ignored. Also, any
IGMPv3 Exclude messages are ignored.
Note
If a PIM-SSM range is configured, IGMPv2 messages and IGMPv3 exclude messages within the
PIM-SSM range are ignored on all IP interfaces, whether or not PIM-SSM is configured on the
interfaces.
To specify a range different from the default PIM SSM range, create a policy file. The match statement
of the policy file contains the group addresses to be treated as PIM SSM addresses. For example, to
specify the PIM SSM address range as 232.0.0.0/8 and 233.0.0.0/8, use the following policy file:
Entry extreme1 {
if match any {
nlri 232.0.0.0/8 ;
nlri 233.0.0.0/8 ;
}
then {
permit ;
}
}
Example
The following example sets the PIM SSM range to 232.0.0.0/8 and 233.0.0.0/8, if the policy file
ssmrange.pol contains the policy example used above:
configure pim ssm range policy ssmrange.pol
History
configure pim ssm

configure pim {ipv4 | ipv6} [{vlan} vlan_name | vlan all
Description
Configures PIM on an IPv4 or IPv6 router interface.
Multicast
174
Multicast Commands
Syntax Description
ipv4
Configures PIM functionality on IPv4 router interfaces.
ipv6
vlan_name
vlan all
Default
N/A.
Usage Guidelines
You must disable PIM before configuring or unconfiguring a PIM-SSM range.
Example
The following command sets:
configure pim
History
The ipv4 and ipv6 keywords were added giving an option to support this functionality in IPv6 as well,
in ExtremeXOS 15.3.
configure pim state-refresh timer origination-interval

Description
Configures the interval at which state refresh messages are originated.
Syntax Description
interval
Multicast
Specifies a refresh interval in seconds. The range is 3090 seconds.
175
Multicast Commands
Default
60 seconds.
Usage Guidelines
None.
Example
The following example configures the interval to 45 seconds:
configure pim state-refresh timer origination-interval 45
History
configure pim state-refresh timer source-active-timer

configure pim {ipv4 | ipv6} state-refresh timer source-active-timerinterval
Description
Defines how long a multicast source (S,G) is considered active after a packet is received from the
source.
Syntax Description
ipv4
ipv6
interval
Specifies a source-active timer interval in seconds. The range is 90300

seconds.
Default
210 seconds.
Usage Guidelines
None.
Multicast
176
Multicast Commands
Example
The following example configures the interval to 45 seconds:
configure pim state-refresh timer source-active-timer 180
History
configure pim state-refresh ttl

configure pim {ipv4 | ipv6} state-refresh ttl ttlvalue
Description
Configures a time-to-live (TTL) value for PIM-DM state refresh messages.
Syntax Description
ipv4
ipv6
ttl_value
Specifies a TTL value. The range is 164.
Default
16.
Usage Guidelines
None.
Example
The following example configures the TTL value for 24:
configure pim state-refresh ttl 24
Multicast
177
Multicast Commands
History
configure pim state-refresh

configure pim {ipv4 | ipv6} state-refresh {vlan} [vlan_name | all] [on | off]
Description
Enables or disables the PIM-DM state refresh feature on one or all VLANs.
Syntax Description
ipv4
ipv6
vlan_name
Specifies a VLAN on which to enable or disable the PIM-DM state refresh

feature.
on
Enables the PIM-DM state refresh feature on the specified VLANs.
off
Disables the PIM-DM state refresh feature on the specified VLANs.
Default
Disabled.
Usage Guidelines
When this feature is disabled on an interface, the interface behaves as follows:
State refresh messages are not originated.
State refresh messages received on the interface are dropped without processing.
State refresh messages received on other interfaces are not forwarded to the disabled interface.
Example
The following example enables the PIM-DM state refresh feature on VLAN blue:
configure pim state-refresh blue on
Multicast
178
Multicast Commands
History
configure pim timer vlan

configure pim {ipv4 | ipv6} timer hello_interval jp_interval [{vlan} vlan_name |
vlan all]
Description
Configures the global PIM timers on the specified router interfaces.
Syntax Description
ipv4
ipv6
hello_interval
Specifies the amount of time before a hello message is sent out by the PIM
router. The range is 165,535 seconds.
jp_interval
Specifies the join/prune interval. The range is 165,535 seconds.
vlan_name
all
Default
hello_interval30 seconds
jp_interval60 seconds
Usage Guidelines
These default timers should only be adjusted when excess PIM control packets are observed on the
interface.
Example
The following example configures the PIM timers on the VLAN accounting:
configure pim timer 150 300 vlan accounting
Multicast
179
Multicast Commands
History
configure pim vlan trusted-gateway

configure pim {ipv4 | ipv6} [{vlan} vlan_name | vlan all ] trusted-gateway
[policy | none]
Description
Configures a trusted neighbor policy.
Syntax Description
ipv4
ipv6
vlan_name
vlan all
policy
none
Specifies no policy file, so all gateways are trusted.
Default
No policy file, so all gateways are trusted.
Usage Guidelines
Because PIM leverages the unicast routing capability that is already present in the switch, the access
policy capabilities are, by nature, different. When the PIM protocol is used for routing IP multicast
traffic, the switch can be configured to use a policy file to determine trusted PIM router neighbors for
the VLAN on the switch running PIM. This is a security feature for the PIM interface.
Example
The following example configures a trusted neighbor policy on the VLAN backbone using hte policy
"nointernet":
configure pim vlan backbone trusted-gateway nointernet
Multicast
180
Multicast Commands
History
create msdp mesh-group

create msdp mesh-group mesh-group-name {vr vrname}
Description
Creates an MSDP mesh-group.
Syntax Description
mesh-group-name
Specifies the name for the MSDP mesh-group.
vrname
Default
N/A.
Usage Guidelines
A mesh-group is a group of MSDP peers with fully meshed MSDP connectivity. Create a mesh-group to:
SA messages received from a peer in a mesh-group are not forwarded to other peers in the same
mesh-group, which reduces SA message flooding.
A mesh group name must begin with an alphabetical character and may contain alphanumeric
characters and underscores ( _ ), but it cannot contain spaces. The maximum allowed length for a
name is 32 characters. For name creation guidelines and a list of reserved names, see Object Names.
Example
The following example creates a mesh-group called "verizon:":
create msdp mesh-group verizon
Multicast
181
Multicast Commands
History
create msdp peer

Description
Creates an MSDP peer.
Syntax Description
remoteaddr
Specifies the IP address of the MSDP router to configure as an MSDP peer.
remote-AS
Specifies the autonomous system (AS) number of the MSDP peer. This optional
parameter is deprecated in ExtremeXOS 12.1, though the option is still available in the CLI
for backward compatibility. The software ignores this parameter.
vrname
Default
N/A.
Usage Guidelines
The BGP route database is used by MSDP to determine the AS number for the peer. You can display
the AS number (which can be a 2-byte for 4-byte AS number) using the command:
show msdp [peer {detail} | {peer} remoteaddr] {vrvrname}.
Example
The following example creates an MSDP peer:
create msdp peer 192.168.45.43 remote-as 65001
History
Multicast
182
Multicast Commands
delete msdp mesh-group

delete msdp mesh-group mesh-group-name {vr vrname}
Description
Removes an MSDP mesh-group.
Syntax Description
mesh-group-name
Specifies the name of the MSDP mesh-group. The character string can be a
vrname
Default
N/A.
Usage Guidelines
A mesh-group is a group of MSDP peers with fully meshed MSDP connectivity. Mesh-groups are used
to achieve two goals:
SA messages received from a peer in a mesh-group are not forwarded to other peers in the same
mesh-group.
Use the delete msdp mesh-group command only if you created a mesh-group that you want to
remove. By default, there is no MSDP mesh-group.
Example
The following example removes a mesh-group called "verizon":
delete msdp mesh-group verizon
History
Multicast
183
Multicast Commands
delete msdp peer

delete msdp peer [all | remoteaddr] {vr vr_name}
Description
Deletes an MSDP peer.
Syntax Description
all
Deletes all MSDP peers.
remoteaddr
Specifies the IP address of the MSDP router to configure as an MSDP peer.
vr_name
Default
N/A.
Usage Guidelines
None.
Example
The following example deletes an MSDP peer:
delete msdp peer 192.168.45.43
History
Multicast
184
Multicast Commands
disable igmp snooping vlan fast-leave

disable igmp snooping {vlan} name fast-leave
Description
Disables the IGMP snooping fast leave feature on the specified VLAN.
Syntax Description
name
Specifies a VLAN.
Default
Disabled.
Usage Guidelines
None.
Example
The following command disables the IGMP snooping fast leave feature on the default VLAN:
disable igmp snooping Default fast-leave
History

disable igmp snooping {forward-mcrouter-only | with-proxy | vlan name}
Description
Disables IGMP snooping.
Multicast
185
Multicast Commands
Syntax Description
forward-mcrouter-only
Specifies that the switch forwards all multicast traffic to the multicast router
only.
with-proxy
Disables the IGMP snooping proxy.
name
Specifies a VLAN.
Default
IGMP snooping and the with-proxy option are enabled by default, but forward-mcrouter-only option is
disabled by default.
Usage Guidelines
If a VLAN is specified, IGMP snooping is disabled only on that VLAN, otherwise IGMP snooping is
disabled on all VLANs.
This command applies to both IGMPv2 and IGMPv3.
If the switch is in the forward-mcrouter-only mode, then the command disable igmp snooping
forward-mcrouter-only changes the mode so that all multicast traffic is forwarded to any IP
router. If not in the forward-mcrouter-mode, the command disable igmp snooping forwardmcrouter-only has no effect.
To change the snooping mode you must disable IP multicast forwarding. Use the command: disable
ipmcforwarding
The with-proxy option can be used for troubleshooting purpose. It should be enabled for normal
network operation.
Enabling the proxy allows the switch to suppress the duplicate join requests on a group to forward to
the connected Layer 3 switch. The proxy also suppresses unnecessary IGMP leave messages so that
they are forwarded only when the last member leaves the group.
Example
The following example disables IGMP snooping on the VLAN accounting:
disable igmp snooping accounting
History
Multicast
186
Multicast Commands

disable igmp ssm-map {vr vr-name}
Description
Disables IGMP SSM mapping.
Syntax Description
vr-name
Specifies a virtual router name. If the VR name is omitted, the switch disables
mapping on the VR specified by the current CLI VR context.
Default
Disabled on all interfaces.
Usage Guidelines
None.
Example
The following command disables IGMP-SSM mapping on the VR in the current CLI VR context:
History
disable igmp
disable igmp {vlan name}
Description
Disables IGMP on a router interface. If no VLAN is specified, IGMP is disabled on all router interfaces.
Multicast
187
Multicast Commands
Syntax Description
name
Default
Enabled.
Usage Guidelines
IGMP is a protocol used by an IP host to register its IP multicast group membership with a router.
Periodically, the router queries the multicast group to see if the group is still in use. If the group is still
active, hosts respond to the query, and group registration is maintained.
IGMP is enabled by default on the switch. However, the switch can be configured to disable the
generation and processing of IGMP packets. IGMP should be enabled when the switch is configured to
perform IP multicast routing.
This command disables IGMPv2 and IGMPv3.
Example
The following example disables IGMP on VLAN accounting:
disable igmp vlan accounting
History
disable ipmcforwarding ipv6

disable ipmcforwarding ipv6 {{vlan} name}
Description
Disables IPv6 multicast forwarding on a router interface.
Syntax Description
name
Multicast
188
Multicast Commands
Default
Disabled.
Usage Guidelines
If no options are specified, all configured IPv6 interfaces are affected. When new IPv6 interfaces are
created, IPv6 multicast forwarding is disabled by default.
Disabling IPv6 multicast forwarding disables any Layer 3 IPv6 multicast routing for the streams coming
to the interface.
Example
The following example disables IPv6 multicast forwarding on VLAN accounting:
disable ipmcforwarding ipv6 vlan accounting
History
disable ipmcforwarding
disable ipmcforwarding {vlan name}
Description
Disables IP multicast forwarding on a router interface.
Syntax Description
name
Default
Disabled.
Multicast
189
Multicast Commands
Usage Guidelines
If no options are specified, all configured IP interfaces are affected. When new IP interfaces are added,
IP multicast forwarding is disabled by default.
IP forwarding must be enabled before enabling IP multicast forwarding.
Disabling IP multicast forwarding disables any Layer 3 multicast routing for the streams coming to the
interface.
Example
The following example disables IP multicast forwarding on the VLAN accounting:
disable ipmcforwarding vlan accounting
History
disable mld
disable mld {vlan name}
Description
Disables MLD on a router interface. If no VLAN is specified, MLD is disabled on all router interfaces.
Syntax Description
name
Default
Disabled.
Usage Guidelines
MLD is a protocol used by an IPv6 host to register its IPv6 multicast group membership with a router.
active, hosts respond to the query, and group registration is maintained.
Multicast
190
Multicast Commands
MLD is disabled by default on the switch. However, the switch can be configured to enable the
generation and processing of MLD packets. MLD should be enabled when the switch is configured to
perform IPv6 unicast or IPv6 multicast routing.
This command disables all MLD versions. When MLD is disabled, the MLDv2 compatibility mode setting
is lost. If compatibility mode is not specified in the command when MLD is enabled again, MLDv1
compatibility mode is set.
Example
The following example disables MLD on VLAN accounting:
disable mld vlan accounting
History

disable mld snooping {with-proxy | vlan name}
Description
Disables MLD snooping.
Syntax Description
with-proxy
Disables the MLD snooping proxy.
name
Specifies a VLAN.
Default
The with-proxy option is enabled by default, but MLD snooping and forward-mcrouter-only option is
disabled by default.
Usage Guidelines
If a VLAN is specified, MLD snooping is disabled only on that VLAN, otherwise MLD snooping is
disabled on all VLANs.
Multicast
191
Multicast Commands
The with-proxy option can be used for troubleshooting purpose. It should be enabled for normal
network operation.
the connected Layer 3 switch. The proxy also suppresses unnecessary MLD done messages so that
Example
The following example disables MLD snooping on the VLAN accounting:
disable mld snooping accounting
History
disable mld-ssm map

disable mld-ssm map {{vr} vr_name}
Description
Disables MLD SSM mapping on a VR.
Syntax Description
vr vr_name
Specifies a virtual router name.
Default
Disabled.
Usage Guidelines
Use this command to disable MLD SSM mapping on a VR.
Enabling or disabling SSM Mapping when PIMv6 is enabled throws the following error:
Multicast
192
Multicast Commands
Example
The following example disables SSM mapping on VR1:
disable mld-ssm map vr vr1
History

disable msdp data-encapsulation {vr vrname}
Description
Disables the encapsulation of locally originated SA messages with multicast data (if available).
Syntax Description
vrname
Default
By default, multicast data packet encapsulation is enabled for locally originated SA messages.
Usage Guidelines
None.
Example
The following command disables multicast data packet encapsulation:
History
Multicast
193
Multicast Commands

disable msdp export local-sa {vr vrname}
Description
Disables the advertisement of local sources to groups for which the router is an RP.
Syntax Description
vrname
Default
By default, the export of local sources is enabled. All sources are advertised if the router is an RP for the
groups. Use this command to disable it.
Usage Guidelines
You can create a policy to filter out some of the local sources so that they are not advertised to MSDP
peers and exposed to the external multicast domain. To configure an export filter, you must first disable
the export of local sources (with the disable msdp export local-sa command), and then reenable it with an export filter (with the enable msdp export local-sa export-filter
command).
Example
The following example disables the advertisement of local sources:
History
Multicast
194
Multicast Commands
disable msdp peer

disable msdp [{peer} remoteaddr | peer all] {vr vr_name}
Description
Configures the administrative state of an MSDP peer.
Syntax Description
remoteaddr
Specifies the IP address of the MSDP peer to disable.
all
Disables all MSDP peers.
vr_name
Default
By default, MSDP peers are disabled.
Usage Guidelines
Use this command to administratively disable MSDP peers to stop exchanging SA messages.
Example
The following command disables an MSDP peer:
disable msdp peer 192.168.45.43
History
disable msdp process-sa-request

disable msdp [{peer} remoteaddr | peer all] process-sa-request {vr vrname}
Multicast
195
Multicast Commands
Description
This command configures a router to reject SA request messages from a specified peer or all peers.
Syntax Description
peer all
remoteaddr
vrname
Default
By default, all SA request messages are accepted from all peers.
Usage Guidelines
Use this command to configure the router to reject SA request messages from a specified peer or all
peers.
You cannot change an SA request filter while SA request processing is enabled for an MSDP peer. You
must first disable SA request processing for a peer and then re-enable it with an SA request filter.
You can use the following policy attributes in an SA request policy. All other attributes are ignored.
Match:
multicast-group
multicast-source
pim-rp
Set:
permit
deny
Example
The following example disables processing of SA request messages received from a peer with the IP
address 192.168.45.43:
disable msdp peer 192.168.45.43 process-sa-request
History
Multicast
196
Multicast Commands
disable msdp
disable msdp {vr vrname}
Description
Disables MSDP on a virtual router.
Syntax Description
vrname
Specifies the name of the virtual router on which MSDP is being enabled or disabled. If a
name is not specified, it is extracted from the current CLI context.
Default
MSDP is disabled by default.
Usage Guidelines
Use this command to disable MSDP on a virtual router.
Example
The following command disables MSDP on a virtual router:
disable msdp
History
disable mvr
disable mvr
Multicast
197
Multicast Commands
Description
Disables MVR on the system.
Syntax Description
This command has no arguments or variables.
Default
Disabled.
Usage Guidelines
None.
Example
The following example disables MVR on the system:
disable mvr
History
disable pim iproute sharing

disable pim {ipv4 | ipv6} iproute sharing
Description
Disables the PIM Equal Cost Multi Path (ECMP) feature.
Syntax Description
iproute
IP Route
sharing
Equal Cost Multipath Routing
Multicast
198
Multicast Commands
Default
Disabled.
Usage Guidelines
None.
Example
The following command disables the PIM ECMP feature:
disable pim ipv4 iproute sharing
History
Summit X440 support IP route sharing in the ExtremeXOS 15.3.2 release. For complete information

disable pim snooping {{vlan} name}
Description
Disables PIM snooping and clears all the snooping PIM neighbors, joins received on the VLAN, and the
forwarding entries belonging to one or all VLANs.
Syntax Description
name
Specifies a VLAN.
Default
Disabled.
Usage Guidelines
None.
Multicast
199
Multicast Commands
Example
The following command disables PIM snooping for all VLANs on the switch:
History
disable pim ssm vlan

disable pim {ipv4 | ipv6} ssm vlan [vlan_name | all]
Description
Disables PIM SSM on a router interface.
Syntax Description
ipv4
ipv6
vlan_name
all
Default
Usage Guidelines
This command disables PIM-SSM on the specified Layer 3 VLAN.
IGMPv3 include messages for multicast addresses in the SSM range is only processed by PIM if PIM-SSM
is enabled on the interface. Any non-IGMPv3 messages in the SSM range are not processed by PIM on
any switch interface, whether SSM is enabled or not.
Multicast
200
Multicast Commands
Example
The following example disables PIM-SSM multicast routing on VLAN accounting:
disable pim ssm vlan accounting
History
disable pim
disable pim {ipv4 | ipv6}
Description
Disables PIM on the system.
Syntax Description
ipv4
ipv6
priority
Specifies a priority setting. The range is 0254.
Default
Disabled.
Usage Guidelines
None.
Example
The following example disables PIM on the system:
disable pim
Multicast
201
Multicast Commands
History
enable igmp snooping vlan fast-leave

enable igmp snooping {vlan} name fast-leave
Description
Enables the IGMP snooping fast leave feature on the specified VLAN.
Syntax Description
name
Specifies a VLAN.
Default
Disabled.
Usage Guidelines
The fast leave feature operates only with IGMPv2.
To view the fast leave feature configuration, use the show configuration msmgr command. This
show command displays the fast leave configuration only when the feature is enabled.
Example
The following example enables the IGMP snooping fast leave feature on the default VLAN:
enable igmp snooping "Default" fast-leave
History
Multicast
202
Multicast Commands

Description
Enables the IGMP snooping proxy. The default setting is enabled.
Syntax Description
Default
Enabled.
Usage Guidelines
the connected Layer 3 switch. The proxy also suppresses unnecessary IGMP leave messages so that
This command can be used for troubleshooting purpose. It should be enabled for normal network
operation. The command does not alter the snooping setting.
This feature can be enabled when IGMPv3 is enabled; however, it is not effective for IGMPv3.
Example
The following command enables the IGMP snooping proxy:
History
Multicast
203
Multicast Commands

enable igmp snooping {forward-mcrouter-only | {vlan} name | with-proxy vr vrname}
Description
Enables IGMP snooping on one or all VLANs.
Syntax Description
forward-mcrouter-only
Specifies that the switch forward all multicast traffic to the

multicast router only.
name
Specifies a VLAN or VMAN on which to enable IGMP snooping.
with-proxy vr vrname
Controls how join and leave messages are forwarded from the
specified virtual router. If this option is specified, one join message
per query is forwarded, and a leave message is forwarded only if it
is from the last receiver on the VLAN.
Default
Enabled.
Usage Guidelines
This command applies to both IGMPv2 and IGMPv3.
IGMP snooping is enabled by default on the switch. If you are using multicast routing, IGMP snooping
can be enabled or disabled. If IGMP snooping is disabled, all IGMP and IP multicast traffic floods within a
given VLAN or VMAN.
The forward-mcrouter-only, vlan, and with-proxy options control three separate and
independent features. You can manage one feature at a time with this command, and you can enter the
command multiple times as needed to control each feature. For example, you can enter the command
twice to enable both the forward-mcrouter-only and with-proxy options.
If a VLAN or VMAN name is specified with this command, IGMP snooping is enabled only on that VLAN
or VMAN. If no options are specified, IGMP snooping is enabled on all VLANs.
Note
IGMP snooping is not supported on SVLANs on any platform.
The with-proxy option enables the IGMP snooping proxy feature, which reduces the number of join and
leave messages forwarded on the virtual router as described in the table above. This feature is enabled
by default.
An optional optimization for IGMP snooping is the strict recognition of routers only if the remote
devices are running a multicast protocol. Two IGMP snooping modes are supported:
Multicast
The forward-mcrouter-only mode forwards all multicast traffic to the multicast router (that is,
the router running PIM, DVMRP or CBT).
204
Multicast Commands
When not in the forward-mcrouter-only mode, the switch forwards all multicast traffic to any IP
router (multicast or not), and any active member port to the local network that has one or more
subscribers.
Note
The forward-mcrouter-only mode for IGMP snooping is enabled/disabled on a switchwide basis, not on a per-VLAN basis. In other words, all the interfaces enabled for IGMP
snooping are either in the forward-mcrouter-only mode or in the non-forward-mcrouteronly mode, and not a mixture of the two modes.
To change the snooping mode you must disable IP multicast forwarding. To disable IP multicast
forwarding, use the command:
disable ipmcforwarding {vlan name}
To change the IGMP snooping mode from the non-forward-mcrouter-only mode to the forwardmcrouter-only mode, use the commands:
disable ipmcforwarding enable igmp snooping forward-mcrouter-only enable
ipmcforwarding {vlan name}
To change the IGMP snooping mode from the forward-mcrouter-only mode to the non-forwardmcrouter-only mode, use the commands:
disable ipmcforwarding disable igmp snooping forward-mcrouter-only enable
ipmcforwarding {vlan name}
Example
The following command enables IGMP snooping on the switch:
History
enable igmp ssm-map

enable igmp ssm-map {vr vr-name}
Description
Enables IGMP SSM mapping on a VR.
Multicast
205
Multicast Commands
Syntax Description
vr-name
Default
Usage Guidelines
Configure the range of multicast addresses for PIM SSM before you enable IGMP SSM mapping. IGMP
SSM mapping operates only with IPv4.
Example
The following example enables IGMP-SSM mapping on the VR in the current CLI VR context:
enable igmp ssm-map
History
enable igmp
enable igmp {vlan vlan name } {IGMPv1 | IGMPv2 | IGMPv3}
Description
Enables IGMP on a router interface. If no VLAN is specified, IGMP is enabled on all router interfaces.
Syntax Description
vlan name
IGMPv1
Specifies the compatibility mode as IGMPv1.
IGMPv2
IGMPv3
Multicast
206
Multicast Commands
Default
Enabled, set to IGMPv2 compatibility mode.
Usage Guidelines
IGMP is a protocol used by an IP host to register its IP multicast group membership with a router.
active, IP hosts respond to the query, and group registration is maintained.
IGMPv2 is enabled by default on the switch. However, the switch can be configured to disable the
generation and processing of IGMP packets. IGMP should be enabled when the switch is configured to
perform IP multicast routing.
Example
The following example enables IGMPv2 on the VLAN accounting:
enable igmp vlan accounting
The following example enables IGMPv3 on the VLAN finance:

enable igmp vlan finance igmpv3
History
The IGMPv1, IGMPv2, and IGMPv3 options were added in ExtremeXOS 11.2.
enable ipmcforwarding ipv6

enable ipmcforwarding ipv6 {vlan name }
Description
Enables IPv6 multicast forwarding on a router interface.
Syntax Description
name
Multicast
207
Multicast Commands
Default
Disabled.
Usage Guidelines
If no options are specified, all configured IPv6 interfaces are affected. When new IPv6 interfaces are
created, IPv6 multicast forwarding is disabled by default.
IPv6 forwarding must be enabled before enabling IPv6 multicast forwarding.
Example
The following example enables IPv6 multicast forwarding on VLAN accounting:
enable ipmcforwarding ipv6 vlan accounting
History
Description
Enables IP multicast forwarding on an IP interface.
Syntax Description
name
Default
Disabled.
Usage Guidelines
If no options are specified, all configured IP interfaces are affected. When new IP interfaces are added,
IPMC forwarding is disabled by default.
Multicast
208
Multicast Commands
IP forwarding must be enabled before enabling IPMC forwarding.
Example
The following example enables IPMC forwarding on the VLAN accounting:
enable ipmcforwarding vlan accounting
History
enable mld
enable mld {vlan vlan_name {MLDv1 | MLDv2}
Description
Enables MLD on a router interface. If no VLAN is specified, MLD is enabled on all router interfaces.
Syntax Description
vlan_name
MLDv1
Sets the compatibility mode to MLDv1.
MLDv2
Sets the compatibility mode to MLDv2.
Default
Disabled.
Usage Guidelines
MLD is a protocol used by an IPv6 host to register its IPv6 multicast group membership with a router.
active, IPv6 hosts respond to the query, and group registration is maintained.
MLD is disabled by default on the switch. However, the switch can be configured to enable the
generation and processing of MLD packets. If compatibility mode is not specified in the command,
MLDv1 compatibility mode is set.
A VLAN must have an IPv6 address to support MLD.
Multicast
209
Multicast Commands
Example
The following example enables MLDv1 on the VLAN accounting:
enable mld vlan accounting
History

Description
Enables the MLD snooping proxy.
Syntax Description
Default
Enabled.
Usage Guidelines
the connected Layer 3 switch. The proxy also suppresses unnecessary MLD leave messages so that
This command can be used for troubleshooting purpose. It should be enabled for normal network
operation. The command does not alter the snooping setting.
Example
The following command enables the MLD snooping proxy:
Multicast
210
Multicast Commands
History
enable mld snooping

enable mld snooping vlan name
Description
Enables MLD snooping on the switch.
Syntax Description
name
Specifies a VLAN.
Default
Disabled.
Usage Guidelines
If a VLAN is specified, MLD snooping is enabled only on that VLAN, otherwise MLD snooping is enabled
on all VLANs.
A VLAN must have an IPv6 address to support MLD.
Example
The following command enables MLD snooping on the switch:
enable mld snooping
History
Multicast
211
Multicast Commands
enable mld-ssm map

enable mld-ssm map {{vr} vr_name}
Description
Enables MLD SSM mapping on a virtual router (VR).
Syntax Description
vr vr_name
Specifies a virtual router name.
Default
Disabled.
Usage Guidelines
Use this command to enable MLD SSM mapping on a VR.
Configure the SSM address range using the configure pim ipv6 ssm range [default |
{policy} policy_name] command before you enable SSM Mapping.
Enabling or disabling SSM Mapping when PIMv6 is enabled throws the following error:
Example
The following example enables SSM mapping on VR1:
enable mld-ssm map vr vr1
History

enable msdp data-encapsulation {vr vrname}
Multicast
212
Multicast Commands
Description
Enables the encapsulation of locally originated SA messages with multicast data (if available).
Syntax Description
vrname
Default
By default, multicast data packet encapsulation is enabled for locally originated SA messages. Multicast
data packets with a packet size of up to 8 KB are encapsulated in SA messages.
Usage Guidelines
Enable data encapsulation to handle bursty sources.
Example
The following command enables multicast data packet encapsulation:
History
enable msdp export local-sa

enable msdp export local-sa {export-filter filter-name} {vr vrname}
Description
Enables the advertisement of local sources to groups for which the router is an RP.
Multicast
213
Multicast Commands
Syntax Description
filter-name
Specifies the policy to associate with the export of local sources. No policy is specified by
default.
vrname
Default
By default, the export of local sources is enabled. All sources are advertised if the router is an RP for the
groups.
Usage Guidelines
You can create a policy to filter out some of the local sources so that they are not advertised to MSDP
peers and exposed to the external multicast domain. To configure an export filter, you must first disable
the export of local sources (with the disable msdp export local-sa command), and then reenable it with an export filter (with the enable msdp export local-sa export-filter
command).
You can use the following policy attributes in an export policy. All other attributes are ignored.
Match:
multicast-group
multicast-source
pim-rp
Set:
permit
deny
Please note that the syntax for multicast-group, multicast-source, and pim-rp are the same as for
the nlri policy attribute.
[multicast-group | multicast-source | pim-rp]
length> {exact}
[multicast-group | multicast-source | pim-rp]
<mask> {exact}
[<ipaddress> | any]/<mask[<ipaddress> | any]
mask
An example of an MSDP policy file follows:

entry allow_internal_rp {
if match any {
multicast-group 234.67.89.0/24;
multicast-source 23.123.45.0/24;
pim-rp 10.203.134.5/32;
} then {
permit;
}
}
entry deny_local_group239 {
if match any {
Multicast
214
Multicast Commands
multicast-source 23.123.45.0/24;
} then {
deny;
}
}
entry allow_external_rp_172 {
if {
} then {
permit
}
}
# deny remaining entries
Example
The following command enables the advertisement of local sources:
nable msdp export local-sa
History
enable msdp peer

enable msdp [{peer} remoteaddr | peer all] {vr vr_name}
Description
Configures the administrative state of an MSDP peer.
Syntax Description
all
Enables all MSDP peers.
remoteaddr
Specifies the IP address of the MSDP peer to configure.
vr_name
Default
By default, MSDP peers are disabled.
Multicast
215
Multicast Commands
Usage Guidelines
You must use this command to administratively enable the MSDP peers before they can establish
peering sessions and start exchanging SA messages.
Example
The following example enables an MSDP peer:
enable msdp peer 192.168.45.43
History
enable msdp process-sa-request

enable msdp [{peer} remoteaddr | peer all] process-sa-request {sa-request-filter
filter-name } {vr vr_name}
Description
This command configures MSDP to receive and process SA request messages from a specified peer or
all peers. If an SA request filter is specified, only SA request messages from those groups permitted are
accepted. All others are ignored.
Syntax Description
peer all
filter-name
Specifies the name of the policy filter associated with SA request processing.
remoteaddr
vr_name
Specifies the name of the virtual router to which this command applies. If a
Default
By default, all SA request messages are accepted from peers.
Multicast
216
Multicast Commands
Usage Guidelines
Use this command to configure the router to accept all or just some SA request messages from peers. If
no policy is specified, all SA request messages are accepted. If a policy is specified, only SA request
messages from those groups permitted are accepted, and all others are ignored.
You cannot change an SA request filter while SA request processing is enabled for an MSDP peer. You
must first disable SA request processing for a peer and then re-enable it with an SA request filter.
You can use the following policy attributes in an SA request policy. All other attributes are ignored.
Match:
multicast-group
multicast-source
pim-rp
Set:
permit
deny
Example
The following example enables processing of SA request messages received from a peer with the IP
address 192.168.45.43:
enable msdp peer 192.168.45.43 process-sa-request sa-request-filter
intra_domain
History
enable msdp
enable msdp {vr vrname}
Description
Enables MSDP on a virtual router.
Multicast
217
Multicast Commands
Syntax Description
vrname
Specifies the name of the virtual router on which MSDP is being enabled or disabled. If a
Default
MSDP is disabled by default.
Usage Guidelines
None.
Example
The following command enables MSDP on a virtual router:
enable msdp
History
enable mvr
enable mvr
Description
Enables MVR on the system.
Syntax Descripton
Default
Disabled.
Multicast
218
Multicast Commands
Usage Guidelines
None.
Example
The following command enables MVR on the system:
enable mvr
History
enable pim iproute sharing

enable pim {ipv4 | ipv6} iproute sharing
Description
Enables the PIM Equal Cost Multi Path (ECMP) feature.
Syntax Description
iproute
IP Route.
sharing
Equal Cost Multipath Routing.
Default
Disabled.
Usage Guidelines
Use this feature to allow downstream PIM router to choose multiple ECMP path to source via hash from
one of the following selections without affecting the existing unicast routing algorithm:
Source
Group
Source-Group
Source-Group-Next-Hop
Multicast
219
Multicast Commands
This feature does load splitting, not load balancing, and operates on a per (S, G) and (*;G) basis,
splitting the load onto the available equal cost paths by hashing according to the selection criteria
defined by the user.
Make sure that IP route sharing is also enabled using enable iproute {ipv4| ipv6} sharing.
Example
The following command enables the PIM ECMP feature:
enable pim ipv4 iproute sharing
History
Summit X440 support IP route sharing in the ExtremeXOS 15.3.2 release. For complete information
enable pim snooping

enable pim snooping {{vlan} name}
Description
Enables PIM snooping on one or all VLANs.
Syntax Description
name
Specifies a VLAN.
Default
Disabled.
Usage Guidelines
PIM snooping does not require PIM to be enabled. However, IGMP snooping must be disabled on
VLANs that use PIM snooping. PIM snooping and MVR cannot be enabled simultaneously on a switch.
PIM snooping should not be enabled on a VLAN that supports PIM-DM neighbors.
Multicast
220
Multicast Commands
Example
The following example enables PIM snooping on the default VLAN:
enable pim snooping default
History
enable pim ssm vlan

enable pim {ipv4 | ipv6} ssm vlan [vlan_name | all]
Description
Enables PIM SSM on an IP interface.
Syntax Description
ipv4
ipv6
vlan_name
all
Default
Usage Guidelines
This command enables PIM-SSM on the specified Layer 3 VLAN.
PIM-SM must also be configured on the interface for PIM to begin operating (which includes enabling IP
multicast forwarding).
IGMPv3 include messages for multicast addresses in the SSM range are only processed by PIM if PIMSSM is enabled on the interface. Any non-IGMPv3 include messages in the SSM range are not processed
by PIM on any switch interface, whether SSM is enabled or not.
Multicast
221
Multicast Commands
Example
The following example enables PIM-SSM multicast routing on VLAN accounting:
enable pim ssm vlan accounting
History
enable pim
enable pim {ipv4 | ipv6}
Syntax Description
ipv4
ipv6
Syntax Description
Default
Disabled.
Usage Guidelines
None.
Example
The following command enables PIM on the system:
enable pim
History
Multicast
222
Multicast Commands
mrinfo
mrinfo {router_address} {from from_address} {timeout seconds} {multiple-responsetimeout multi_resp_timeout} {vr vrname}
Description
Requests information from a multicast router.
Syntax Description
router_address
Specifies the unicast IP address of the router for which you want information.
from_address
Specifies the unicast IP address of the interface where the mrinfo request is generated.
seconds
Specifies a maximum time to wait for a response. The range is 130 seconds.
multi_resp_timeout Specifies a maximum time to wait for additional responses after the first response is
received. The range is 0 to 3 seconds.
vrname
Specifies a VR name.
Default
router_address: One of the local interface addresses.
from_address: IP address of interface from which the mrinfo query is generated.
timeout: 3 seconds
multiple-response-timeout: 1 second
vr: DefaultVR
Usage Guidelines
The last column of the mrinfo command output displays information in the following format:
[Metric/threshold/type/flags]
This information is described in detail in the Syntax Description on page 223..
Multicast
223
Multicast Commands
Table 7: mrinfo Command Display Data

Data
Description
Metric
This should always be 1 because mrinfo queries the directly connected interfaces of a
device.
Threshold
This should always be 0 because the threshold feature is not supported in

ExtremeXOS software.
Type
The type specifies the multicast protocol type. Because the ExtremeXOS software
only supports PIM, this value is always pim.
querier
The querier flag indicates that the queried router is the IGMP querier.
leaf
The leaf flag indicates that the IP interface has no neighbor router.
down
The down flag indicates that the interface link status is down.
Example
The following command requests information from multicast router 1.1.1.1:
Switch.1 # mrinfo 1.1.1.1
1.1.1.1 [Flags:PGM]
2.2.2.1 -> 2.2.2.2 [1/0/pim/querier]
1.1.1.1 -> 0.0.0.0 [1/0/pim/querier/leaf]
8.8.8.1 -> 8.8.8.4 [1/0/pim/querier]
3.3.3.1 -> 0.0.0.0 [1/0/pim/down]
History
mtrace
mtrace source src_address {destination dest_address} {group grp_address} {from
from_address} {gateway gw_address} {timeout seconds} {maximum-hops number}
{router-alert [include | exclude]} {vr vrname}
Description
Traces multicast traffic from the receiver back to the source.
Multicast
224
Multicast Commands
Syntax Description
src_address
Specifies the unicast IP address of the multicast source.
dest_address
Specifies the unicast IP address of the multicast group receiver.
grp_address
Specifies the multicast IP address of the group.
from_address
Specifies the unicast IP address of the interface where the mtrace request
originates. This is used as the IP destination address of the mtrace response
packet.
gw_address
Specifies the gateway router IP address of the multicast router to which the
unicast mtrace query is sent.
seconds
Specifies a maximum time to wait for the mtrace response before making the
next attempt. The range is 130 seconds.
number
Specifies the maximum number of hops for the trace. The range is 1 to 255.
router-alert
Specifies whether the router-alert option is included or excluded in mtrace

packets.
vrname
Specifies a VR name.
Default
destination: IP address of interface from which mtrace query is generated.
group: 0.0.0.0
from: IP address of interface from which mtrace query is generated.
gateway: 224.0.0.2 when the destination is in the same subnet as one of the IP interfaces. For a non-
local destination address, it is mandatory to provide a valid multicast router address.

timeout: 3 seconds
maximum-hops: 32
router-alert: include
vr: DefaultVR
Usage Guidelines
The multicast traceroute initiator node generates a multicast query and waits for timeout period to
expire. If there is no response for the timeout period, the initiator node makes two more attempts. If no
response is received after three attempts, the initiator node moves to a hop-by-hop trace by
manipulating the maximum hop fields to perform a linear search.
The multicast trace response data contains the following fields:
Multicast
Incoming interface addressInterface on which traffic is expected from the specific source and
group
Outgoing interface addressInterface on which traffic is forwarded from the specified source and
group towards the destination
225
Multicast Commands
Previous hop router address

Input packet count on incoming interface
Output packet count on outgoing interface
Total number of packets for this source-group pair
Multicast routing protocol
Forwarding code
Extreme Networks switches set the packet count statistics field to 0xffffffff to indicate that this field is
not supported.
The last column of the mtrace command output displays forwarding codes, which are described in the
following table.
Table 8: mtrace Command Forwarding Codes
Forwarding Code
Description
Wrong interface
mtrace request arrived on an interface to which this router would not forward for
this source and group.
Prune sent upstream
This router has sent a prune request upstream for the source and group in the
mtrace request.
Output pruned
This router has stopped forwarding for this source and group in response to a prune
request from the next hop router.
Hit scope boundary
The group is subject to administrative scoping at this hop.
No route
This router has no route for the source or group and no way to determine a potential
route.
Wrong Last Hop
This router is not the proper last-hop router.
Not forwarding 2
This router is not forwarding for this source and group on the outgoing interface for
an unspecified reason.
Reached RP/Core
Reached rendezvous point or core.
RPF Interface
mtrace request arrived on the expected RPF interface (upstream interface) for this
source and group.
Multicast disabled
mtrace request arrived on an interface which is not enabled for multicast.
Info. Hidden 2
One or more hops have been hidden from this trace.
No space in packet
There was not enough room to insert another response data block in the packet.
Next router no mtrace 2
The previous hop router does not understand mtrace requests.
Admin. Prohibiteda
mtrace is administratively prohibited.
Example
The following command initiates an mtrace for group 225.1.1.1 at IP address 1.1.1.100:
Switch.6 # mtrace source 1.1.1.100 group 225.1.1.1
Mtrace from 1.1.1.100 to Self via 225.1.1.1
0
34.2.2.4
2
ExtremeXOS switches along the mtrace path do not provide this forwarding code.
Multicast
226
Multicast Commands
-1
34.2.2.4
-2
34.2.2.3
-3
23.1.1.2
-4
2.2.2.1
Round trip time 9 ms;
PIM thresh^ 0
1.1.1.100/32
PIM thresh^ 0
1.1.1.100/32
PIM thresh^ 0
1.1.1.100/32
PIM thresh^ 0
1.1.1.100/32
total ttl of 4 required.
RPF Interface
History
The router-alert option was added in ExtremeXOS 12.5.3.
refresh mld ssm-map

refresh mld ssm-map { v6groupnetmask } {{vr} vr_name}
Description
Sends a DNS request for a particular group. On receiving the DNS response, the DNS Age in the SSM
mapping entry is refreshed.
Syntax Description
v6groupnetmask
Refreshes the specific group information.
vr vr_name
Default
Disabled.
Usage Guidelines
Use this command to send out DNS requests for a particular group. On receiving the DNS response, the
DNS Age in the SSM mapping entry is refreshed.
Example
The following command send out DNS requests:
refresh mld ssm-map
Multicast
227
Multicast Commands
When v6groupnetmask is specified, the SSM Mapping status and the SSM Mapping entries specific
to the group range on the VR are displayed.
History
rtlookup rpf
rtlookup [ipv4_address | ipv6_address] rpf {vr vr_name}
Description
Displays the RPF for a specified multicast source.
Syntax Description
ipv4_address
ipv6_address
rpf
Selects the RPF for the specified multicast source.
vr_name
Specifies the virtual router for which to display the route.
Default
vr_name is the VR of the current CLI context.
Usage Guidelines
None.
Example
The following example displays the RPF lookup for multicast source 12.1.20.12 in the default VR:
# rtlookup 12.1.20.12 rpf vr vr-default
Ori Prefix
Route
Gateway
VLAN
@d 12.1.10.22
12.1.10.0/24
12.1.10.10
v1
Origin(Ori): (b) BlackHole, (be) EBGP, (bg) BGP, (bi) IBGP, (bo) BOOTP
(ct) CBT, (d) Direct, (df) DownIF, (dv) DVMRP, (e1) ISISL1Ext
(e2) ISISL2Ext, (h) Hardcoded, (i) ICMP, (i1) ISISL1 (i2) ISISL2
(mb) MBGP, (mbe) MBGPExt, (mbi) MBGPInter, (mp) MPLS Lsp
(mo) MOSPF (o) OSPF, (o1) OSPFExt1, (o2) OSPFExt2
Multicast
228
Multicast Commands
(oa) OSPFIntra, (oe) OSPFAsExt, (or)OSPFInter, (pd) PIM-DM,(ps) PIM-SM

(r) RIP, (ra) RtAdvrt, (s) Static, (sv) SLB_VIP, (un) UnKnown
(*) unicast route (@) multicast route
History
rtlookup
rtlookup [ipv4_address | ipv6_address] { unicast | multicast | rpf } {vr vr_name}
Description
Displays the available routes to the specified IP address.
Syntax Description
ipv4_address
ipv6_address
unicast
Displays the routes from the unicast routing table in the current router
context.
multicast
Displays the routes from the multicast routing table in the current
router context.
rpf
Displays the RPF route to the specified destination.
vr_name
Specifies the virtual router for which to display the route.
Default
When no option (unicast or multicast) is provided, this command displays the route in the unicast
routing table.
Usage Guidelines
None.
Multicast
229
Multicast Commands
Example
The following example displays the route lookup for 12.1.20.12 in the multicast routing table for the
default VR:
# rtlookup 12.1.20.12 multicast vr vr-default
@mbe 12.1.0.0/16
50.1.10.21
1
UG---S--m--- toronto
0d:0h:
41m:1s
(mb) MBGP, (mbe) MBGPExt, (mbi) MBGPInter, (mp) MPLS Lsp
(oa) OSPFIntra, (oe) OSPFAsExt, (or) OSPFInter, (pd) PIM-DM, (ps) PIM-SM
(*) Preferred unicast route (@) Preferred multicast route
(#) Preferred unicast and multicast route
Flags: (B) BlackHole, (D) Dynamic, (G) Gateway, (H) Host Route
(L) Matching LDP LSP, (l) Calculated LDP LSP, (m) Multicast
(P) LPM-routing, (R) Modified, (S) Static, (s) Static LSP
(T) Matching RSVP-TE LSP, (t) Calculated RSVP-TE LSP, (u) Unicast, (U) Up
(c) Compressed Route
Mariner # rtlookup 12.1.20.12 multicast vr vr-default
No route to 12.1.10.12
History
The xhostname option was removed in ExtremeXOS 11.0.
Support for IPv6 was added in ExtremeXOS 11.2.
The unicast and multicast options were added in ExtremeXOS 12.1.
show igmp group

show igmp group {{vlan} {name} | {grpipaddress}} {IGMPv3}
Description
Lists the IGMP group membership for the specified VLAN.
Multicast
230
Multicast Commands
Syntax Description
name
grpipaddress
Specifies a group IP address.
IGMPv3
Displays the IGMP group in IGMPv3 format (if group record is IGMPv3 compatible,
otherwise displays in earlier format).
Default
IGMPv2.
Usage Guidelines
If no VLAN is specified, all VLANs are displayed. You can also filter the display by group address or by
multicast stream sender address.
The output of this command shows:
The multicast group address received.

The version of the IGMP group.
The name of the VLAN where the group address is being received.
The physical port where the group address is being received. If multiple ports within the VLAN have
subscribers for the group, all the ports are listed.
The age since the last IGMP report for this group was received.
Note
The show igmp group command output is populated on the router that is the PIM
Rendezvous Point.
Example
The following is sample output from the show igmp groupcommand, listing the IGMP group
membership:
Group Address
239.2.4.70
224.0.1.24
239.255.255.254
Total: 3
Ver
2
2
2
Vlan
banana
banana
banana
Port
7
7
7
Age
101
107
103
History
The IGMPv3 option was added in ExtremeXOS 11.2.
Multicast
231
Multicast Commands

This command is provided for backward compatibility. The recommended command is:
show mcast cache {{vlan} name} {{[group grpaddressMask | grpaddressMask] {source
sourceIP | sourceIP}} {type [snooping | pim | mvr]}| {summary}}
The syntax for the original form of this command is:

show igmp snooping cache {{vlan} name} {{group} grpaddressMask}
Description
Displays multicast cache entries added by IGMP snooping for all VLANs and groups. The display can be
limited to specific VLANs or groups.
Syntax Description
name
grpaddressMask
Specifies a multicast group address and mask.
Default
Displays information for all VLANs and groups.
Usage Guidelines
None.
Example
The following command displays IGMP snooping cache information for all VLANs and groups:
This command display is the same as for the following preferred command:
show mcast cache {{vlan} name} {{[group grpaddressMask |grpaddressMask] {source
sourceIP |sourceIP}} {type [snooping | pim | mvr]}| {summary}}
History
Multicast
232
Multicast Commands
show igmp snooping vlan filter

show igmp snooping {vlan} name filter
Description
Displays IGMP snooping filters.
Syntax Description
name
Default
None.
Usage Guidelines
Use this command to display IGMP snooping filters configured on the specified VLAN. When no VLAN
is specified, all the filters are displayed.
Example
The following command displays the IGMP snooping filter configured on VLAN vlan101:
# show igmp snooping vlan101 filter
Filter
Port Flags
igmppermit0
5:10 a
Flags: (a) Active
History
Multicast
233
Multicast Commands
show igmp snooping vlan static

show igmp snooping {vlan} name static [group | router]
Description
Displays static IGMP snooping entries.
Syntax Description
name
group
Displays static multicast groups.
router
Displays static router entries.
Default
None.
Usage Guidelines
Use this command to display the IGMP snooping static groups or router ports configured on the
specified VLAN. When no VLAN is specified, all the static groups or router ports are displayed.
Example
The following command displays the IGMP snooping static groups configured on VLAN vlan101:
# show igmp snooping vlan101 static group
VLAN vlan101 (4094)
Group
Port
Flags
239.1.1.2
29
s239.1.1.2
30
s239.1.1.2
31
sa
239.1.1.2
32
s239.1.1.2
34
sTotal number of configured static IGMP groups = 5
Flags: (s) Static, (a) Active
History
Multicast
234
Multicast Commands
show igmp snooping vlan

show igmp snooping {vlan} name {port port} {IGMPv3}
Description
Displays IGMP snooping registration information for a specific VLAN. The display can be further limited
to a specific port or to only IGMPv3 entries.
Syntax Description
name
port
Specifies a single port for which information is displayed.
IGMPv3
Displays the IGMP group in IGMPv3 format (if group record is IGMPv3
compatible, otherwise displays in earlier format).
Default
IGMPv2.
Usage Guidelines
The two types of IGMP snooping entry are sender entry and subscribed entry.
The following information is displayed in a per-interface format:
Group membership information
Router entry
Timeout information
Sender entry
Example
The following output displays IGMP snooping registration information on VLAN v1:
# show igmp snooping vlan v1
Router Timeout
:
260 sec
Host Timeout
:
260 sec
Igmp Snooping Fast Leave Time :
1000 ms
VLAN v1 d
(4084) Snooping=Enabled
Port
Host
Subscribed
Age
25
118.1.1.100
All Groups
3
Group-Limit
0
The following command displays IGMP snooping registration information for port 2:1 on VLAN test:
show igmp snooping test port 2:1
Multicast
235
Multicast Commands
History
show igmp snooping

show igmp snooping {detail {IGMPv3}}
Description
Displays IGMP snooping registration information for all VLANs.
Syntax Description
detail
Displays the information in detailed format.
IGMPv3
Displays the IGMP group in IGMPv3 format (if group record is IGMPv3
compatible, otherwise displays in earlier format).
Default
IGMPv2.
Usage Guidelines
None.
Example
The following command displays IGMP snooping registration information for all VLANs:
# show igmp snooping
Igmp Snooping Flag
: forward-all-router
Igmp Snooping Flood-list
: none
Igmp Snooping Proxy
: Disable
Igmp Snooping Filters
: per-port
Vlan
Vid Port
#Senders #Receivers Router Enable
-------------------------------------------------------------Default
1
0
Yes
v1
4090
0
Yes
Multicast
236
Multicast Commands
History
The IGMP Forwding Lookup mode output was removed from this command in ExtremeXOS 15.3.
show igmp ssm-map

show igmp ssm-map {group_ip} {vr vr-name}
Description
Displays the IGMP SSM feature status (enabled or disabled), the mappings for the specified multicast
group IP address, and the total count of maps.
Syntax Description
group_ip
Specifies an IP multicast group, for which all mappings in the PIM SSM range
are to be displayed. If no group address is specified, the switch displays all
IGMP-SSM mappings.
vr-name
Specifies a virtual router name. If the VR name is omitted, the switch displays
the mappings on the VR specified by the current CLI VR context.
Default
N/A.
Usage Guidelines
When a target group is specified, this command displays all mapping entries for the configured range in
which the group IP address resides.
Example
The following example displays the mappings for the multicast group IP address 232.1.1.2:
show igmp ssm-map 232.1.1.2
History
Multicast
237
Multicast Commands
show igmp
show igmp {vlan} {vlanname}
Description
This command can be used to display an IGMP-related configuration and group information, per VLAN.
Syntax Description
vlanname
Default
N/A.
Usage Guidelines
The output of this command shows:
The VLAN name.
The router interface IP address and subnet mask.
If the interface is active (up), by the letter U.
If IP forwarding is enabled for the interface, by the letter f.
If multicast forwarding is enabled, by the letter M.
If IGMP is enabled, by the letter i.
If IGMP snooping is enabled, by the letter z.
Example
The following command displays the IGMP configuration:
# show igmp
VLAN
IP Address
Flags
nLRMA nLeMA IGMPver
Default
0.0.0.0
/ 0
---izpt0
0
3
isc
50.50.50.1
/24
---izpt0
0
3
v1
0.0.0.0
/ 0
U--izpt0
2
3
v3000
1.1.1.1
/24
---izpt0
0
3
v666
6.0.0.1
/16
---izpt0
0
3
Flags: (f) Forwarding Enabled, i) IGMP Enabled
(m) Multicast Forwarding Enabled, (p) IGMP Proxy Query Enabled
(r) Receive Router Alert Required (t) Transmit Router Alert
(U) Interface Up, (z) IGMP Snooping Enabled
Multicast
238
Multicast Commands
(nLeMA) Number of Learned Multicast Addresses

(nLRMA) Number of Locally Registered Multicast Addresses
The following command displays the IGMP configuration for VLAN vlan1:
# show igmp vlan1
Query Interval
:
125 sec
Max Response Time :
10 sec
Last Member Query :
1 sec
Robustness
:
2
Interface on VLAN vlan1 is enabled and up.
inet 0.0.0.0/0
Locally registered multicast addresses:
Learned multicast addresses(Last Querier=118.1.1.100):
224.0.0.2
224.0.0.22
s = static igmp member
Flags:
IP Fwding NO
IPmc Fwding NO
IGMP YES
IGMP Ver V3
Snooping YES
Proxy Query YES
XmitRtrAlrt YES
RcvRtrAlrtReq NO
History
show ipmroute
show ipmroute {source-net mask-len | source-net mask | summary} {vr vr-name}
Description
Displays the contents of the IP multicast routing table or the route origin priority.
Syntax Description
source-net
mask-len
Mask length for the IP multicast source's subnet. Range is 132.
mask
summary
Displays the statistics of multicast static routes.
vr-name
Multicast
239
Multicast Commands
Default
vr-name is the VR of the current CLI context.
Usage Guidelines
This command allows you to view the configured multicast static routes. You can specify the filtering
criteria on this CLI to view only the desired route. The multicast static routes are displayed in ascending
order of their prefix (same order as show iproute displays).
Example
The following example displays a multicast static route from a default virtual router:
* (debug) Summit-PC.19 # show ipmroute
Destination
Gateway
Mtr Flags Protocol
Default Route
20.20.20.1
255 UG
None
*1.1.0.0/16
20.20.20.1
10
UG
bgp
*11.0.0.0/8
30.30.30.1
12
UNone
11.22.0.0/16
20.20.20.1
10
UG
None
*11.22.33.0/24
30.30.30.1
8
UNone
11.22.33.44/32
20.20.20.1
4
UG
None
*12.0.0.0/8
20.20.20.1
0
UG
None
12.24.0.0/16
30.30.30.1
0
UNone
*12.24.48.96/32
30.30.30.1
2
Uospf-extern1
44.66.0.0/16
30.30.30.1
0
UNone
Flags: (*) Active, (G) Gateway, (U) Up
Mask distribution:
1 default routes
2 routes at length 8
Total number of multicast static routes = 10
VLAN
pc4-1
pc4-1
pc5-3
pc4-1
pc5-3
pc4-1
pc4-1
pc5-3
pc5-3
pc5-3
History
show iproute multicast

show iproute {ipv4} {{vlan} name | [ipaddress netmask | ipNetmask] | origin
[direct | static | mbgp | imbgp | embgp]} multicast {vr vr_name}
Description
Displays all or a filtered set of multicast routes in the IP multicast routing table.
Multicast
240
Multicast Commands
Syntax Description
ipv4
Selects only IPv4 multicast routes.
name
Specifies a VLAN for which to display multicast routes.
ipaddress netmask
Specifies an IP address and network mask (in dotted decimal notation) for
which to display multicast routes.
ipNetmask
Specifies the IP address and network mask in classless inter domain routing
(CIDR) notation.
origin
Limits the displayed multicast routes to those generated by the specified

origin. Origin options select direct routes, static routes, and routes created by
the MBGP, IMBGP, and EMBGP protocols.
vr_name
Specifies the virtual router for which to display multicast routes.
Default
Usage Guidelines
This command does not display unicast routes, which can be used for multicast traffic.
Example
The following example displays all the routes in multicast routing table:
# show iproute multicast
Ori
Destination
@d
3.3.3.3/32
30m:36s
@d
28.0.0.0/24
30m:36s
@mbe 77.0.0.0/24
41m:1s
@mbe 77.0.1.0/24
41m:1s
@mbe 77.0.2.0/24
41m:1s
@mbe 77.0.3.0/24
41m:1s
@mbe 77.0.4.0/24
41m:1s
@mbe 77.0.5.0/24
41m:1s
@mbe 77.0.6.0/24
41m:1s
@mbe 77.0.10.0/24
41m:1s
@mbe 77.0.11.0/24
41m:1s
@mbe 77.0.12.0/24
41m:1s
@mbe 77.0.13.0/24
Multicast
Gateway
3.3.3.3
Mtr
1
Flags
VLAN
U-------m--- lpbk
Duration
12d:1h:
28.0.0.15
U-------m--- trunk28
12d:1h:
50.1.10.21
0d:0h:
50.1.10.21
0d:0h:
50.1.10.21
0d:0h:
50.1.10.21
0d:0h:
50.1.10.21
0d:0h:
50.1.10.21
0d:0h:
50.1.10.21
0d:0h:
50.1.10.21
0d:0h:
50.1.10.21
0d:0h:
50.1.10.21
0d:0h:
50.1.10.21
0d:0h:
241
Multicast Commands
41m:1s
@mbe 77.0.14.0/24
50.1.10.21
1
0d:0h:
41m:1s
@d
82.0.0.0/24
82.0.0.15
1
U-------m--- trunk28-2 12d:1h:
30m:36s
(is) ISIS, (mb) MBGP, (mbe) MBGPExt, (mbi) MBGPInter, (mp) MPLS Lsp
(oa) OSPFIntra, (oe) OSPFAsExt, (or) OSPFInter, (pd) PIM-DM, (ps) PIM-SM
(*) Preferred unicast route (@) Preferred multicast route
(#) Preferred unicast and multicast route
Flags: (B) BlackHole, (D) Dynamic, (G) Gateway, (H) Host Route
(L) Matching LDP LSP, (l) Calculated LDP LSP, (m) Multicast
(P) LPM-routing, (R) Modified, (S) Static, (s) Static LSP
(T) Matching RSVP-TE LSP, (t) Calculated RSVP-TE LSP, (u) Unicast, (U) Up
(f) Provided to FIB (c) Compressed Route
Mask distribution:
Route Origin distribution:
3 routes from Direct
Total number of routes = 15
Total number of compressed routes = 0
History
show L2stats
show L2stats {vlan vlan_name}
Description
Displays the counters for the number of packets bridged, switched, and snooped (Layer 2 statistics).
Syntax Description
vlan_name
Default
N/A.
Multicast
242
Multicast Commands
Usage Guidelines
None.
Example
The following command displays the counters for the number of packets bridged, switched, and
snooped (Layer 2 statistics) for the VLAN accounting:
show L2stats accounting
Note
You can also enter the command as show l2stats. We use the uppercase letter here to
avoid confusion with the numeral 1.
History
This command is available on all platforms.
show mcast cache

show mcast {ipv4 | ipv6} cache {{vlan} name} {{[group grpaddressMask |
grpaddressMask] {source sourceIP | sourceIP}} {type [snooping | pim | mvr]}|
{summary}}
Description
Displays multicast cache information.
The display can be limited to entries for specific VLANs or groups, and it can be limited to specific types
of entries, such as those created by snooping protocols, PIM, or MVR.
Syntax Description
ipv4
ipv6
name
grpaddressMask
sourceIP
Specifies the source IP address for a multicast group.
snooping
Limits the display to cache entries created by PIM or IGMP snooping.
pim
Limits the display to cache entries created by PIM.
Multicast
243
Multicast Commands
mvr
Limits the display to cache entries created by MVR.
summary
Specifies the summary display format.
Default
Displays information for all entries in the multicast cache.
Usage Guidelines
If the configure forwarding ipmc lookup-key mac-vlan command is configured, the
following message displays: displayed:
NOTE: Traffic is forwarded based on MAC address. Actual traffic forwarded based
on the installed MAC address need not be the same displayed in this command, if
overlapping IP multicast addresses are used in the network.
If the mode is mixed-mode, the following message displays:

NOTE: Traffic could be forwarded based on MAC address. Actual traffic forwarded
based on the installed MAC address need not be the same displayed in this
command, if overlapping IP multicast addresses are used in the network.
Example
The following command displays all multicast cache information:
# show mcast cache
Type Group
Sender
Age InVlan
snoop 225.1.1.1
222.222.222.222
17
snvlan
Vlan
Port
Vid
snvlan
2
400
23
400
snoop 224.0.0.5
100.1.2.2
2
pmvlan2
Vlan
Port
Vid
pmvlan2
4
402
snoop 224.0.0.5
100.1.3.3
17
pmvlan3
Vlan
Port
Vid
pmvlan3
23
403
snoop 224.0.0.13
100.1.2.2
11
pmvlan2
Vlan
Port
Vid
pmvlan2
4
402
snoop 224.0.0.13
100.1.3.3
14
pmvlan3
Vlan
Port
Vid
pmvlan3
23
403
pim 226.1.1.1
100.1.1.12
0
pmvlan1
Vlan
Port
Vid
pmvlan2
4
402
pmvlan3
23
403
0 entries from MVR
PIM
Multicast
1 entries from
244
Multicast Commands
The following command displays summary cache information for VLAN pmvlan1:
# show mcast cache vlan pmvlan1 summary
==============MULTICAST CACHE SUMMARY==============
0 entries from MVR
PIM
pmvlan1: Multicast cache distribution:
0 entries from MVR
PIM
Total Cache Entries for VLAN pmvlan1: 1
1 entries from
1 entries from
History
This command is available on all platforms.
show mcast ipv6 cache

show mcast ipv6 cache {{vlan} name} {{[group v6GrpAddressMask | v6GrpAddressMask]
{source v6SourceIP | v6SourceIP}} {type [snooping | pim]} {with-in-port} |
{summary}}
Description
Displays multicast cache information. The display can be limited to entries for specific VLANs or groups,
and it can be limited to specific types of entries, such as those created by snooping protocols, or PIM.
Syntax Description
name
v6GrpAddressMask
v6SourceIP
Specifies the source IP address for a multicast group.
snooping
Limits the display to cache entries created by MLD snooping.
pim
Limits the display to cache entries created by PIM.
summary
Specifies the summary display format.
Default
Displays information for all entries in the multicast cache.
Multicast
245
Multicast Commands
Usage Guidelines
None.
Example
The following command displays all multicast cache information:
# show mcast ipv6 cache
Snooping Cache Timeout: 300 sec
(ff03::1 3001::1)
Type: snoop Age: 9 Ingress Vlan: v1
Vlan
Port
Vid
v1
25
4084
(ff03::1 3001::2)
Type: snoop Age: 9 Ingress Vlan: v1
Vlan
Port
Vid
v1
25
4084
0 entries from PIM
The following command displays summary cache information for VLAN v1:
# show mcast ipv6 cache vlan v1 summary
Snooping Cache Timeout: 300 sec
==============MULTICAST CACHE SUMMARY==============
0 entries from PIM
v1: Multicast cache distribution:
0 entries from PIM
Total Cache Entries for VLAN v1: 2
*X480-48t.22 #
History
show mld
show mld {vlan} {name}
Multicast
246
Multicast Commands
Description
This command can be used to display an MLD-related configuration and group information, per VLAN
or for the switch as a whole.
Syntax Description
name
Default
N/A.
Usage Guidelines
If you do not specify a VLAN, the command displays the switch configuration.
Example
The following is sample output from the show mld command:
# show mld
VLAN
IP Address
Flags nLRMA nLeMA
MLDver
Default
::/0
---iz0
0
0
v1
::/0
U--iz0
5
0
Flags:
(f) Forwarding Enabled, (g) Fast-learning on, (i) MLD Enabled,
(m) Multicast Forwarding Enabled, (U) Interface Up,
(z) MLD Snooping Enabled.
(nLeMA) Number of Learned Multicast Addresses
(nLRMA) Number of Locally Registered Multicast Addresses
The following command displays the MLD configuration for VLAN v1:
# show mld v1
Query Interval
: 125 sec
Max Response Time : 10 sec
Last Member Query : 1 sec
Robustness
: 2
Interface on VLAN v1 is enabled and up.
inet6 ::/0
Locally registered multicast addresses:
Learned multicast addresses(Last Querier=fe80::204:96ff:fe3a:ce50):
ff02::2
ff02::1:ff56:5c2b
ff02::1:ff00:2
ff02::1:ff3a:ce50
ff02::1:ff55:5c27
s = static MLD member
Flags:
IP Fwding NO
IPmc Fwding NO
MLD YES
MLD Ver v0
Snooping YES
Multicast
247
Multicast Commands
History
show mld counters

show mld counters {{vlan} name}
Description
Use this command to display an MLD packet statistics.
Syntax Description
name
Default
N/A.
Usage Guidelines
The following command displays the MLD configuration:
* topleft.74 # show mld counters
MLD Message type
Received
MLD Query (v1/v2)
0
MLDv1 Report
499
MLDv1 Done
101
MLDv2 Report
0
Global Statistics:
MLD Packet unknown
0
MLD Packet Error
617
Originated
20
0
0
0
Forwarded
0
157
91
0
History
Multicast
248
Multicast Commands
show mld group

show mld group {{vlan} {name} | {v6grpipaddress}} {MLDv2}
Description
Lists the MLD group membership for the specified VLAN or group.
Syntax Description
name
v6grpipaddress
Specifies a group IPv6 address.
MLDv2
DisplayS the MLD group in MLDv2 format (if group record is MLDv2
compatible, otherwise displayS in earlier format). This option is not supported
in this release.
Default
MLDv1.
Usage Guidelines
If no VLAN is specified, all VLANs are displayed. You can also filter the display by group address or by
multicast stream sender address.
Example
The following command lists the MLD group membership for the VLAN accounting:
show mld group vtest3
Output from this command looks similar to the following:

Group Address
ff03::1:1
ff03::1:2
ff02::1:ff22:124
ff05::a:abcd
ff05::a:abce
ff02::1:ff22:112
ff02::1:ff1f:a418
Ver
1
1
1
1
1
1
1
Vlan
vtest3
vtest3
vtest3
vtest3
vtest3
vtest3
vtest3
Port
4:5
4:5
4:45
4:15
4:15
4:45
4:45
Age
25
25
26
23
23
26
26
History
Multicast
249
Multicast Commands
show mld snooping vlan filter

show mld snooping {vlan} name filter
Description
Displays MLD snooping filters..
Syntax Description
name
Default
None.
Usage Guidelines
Use this command to display MLD snooping filters configured on the specified VLAN. When no VLAN is
specified, all the filters are displayed.
Example
The following command displays the MLD snooping filter configured on VLAN vlan101:
# show mld snooping vlan101 filter
Filter Port Flags
mldpermit0 5:10 a
Flags: (a) Active
History
show mld snooping vlan static
Multicast
250
Multicast Commands
show mld snooping vlan name static [group | router]
Description
Displays static MLD snooping entries.
Syntax Description
name
Default
None.
Usage Guidelines
Use this command to display the MLD snooping static groups or router ports configured on the
specified VLAN. When no VLAN is specified, all the static groups or router ports are displayed.
Example
The following command displays the MLD snooping static groups configured on VLAN vlan101:
show mld snooping vlan101 static group
The following is sample output for this command:

Group
Port
ff03::1:1:1
7
ff03::1:1:1
15
Flags: (s) Static, (a) Active
Flags
sa
sa
History
show mld snooping

show mld snooping {vlan name | detail} {MLDv2}
Note
MLD snooping is not supported in this software release.
Multicast
251
Multicast Commands
Description
Displays MLD snooping registration information and a summary of all MLD timers and states.
Syntax Description
name
detail
Displays the information in detailed format.
MLDv2
Displays the MLD group in MLDv2 format (if group record is MLDv2
compatible, otherwise displays in earlier format). This option is not supported
in this release.
Default
MLDv1.
Usage Guidelines
The two types of MLD snooping entries are sender entry and subscribed entry.
The following information is displayed in a per-interface format:
Group membership information
Router entry
Timeout information
Sender entry
Example
Here is an example of the show output:
# show mld snooping
MLD Snooping Flood-list : none
MLD Snooping Proxy
: Enable
MLD Snooping Filters
: per-port
Vlan
Vid Port
#Senders #Receivers Router Enable
-------------------------------------------------------------Default
1
0
Yes
v1
4084
0
Yes
25
1
Yes
41
2
No
42
2
No
The following command displays MLD snooping registration information for the VLAN V1:
# show mld snooping v1
Router Timeout
:
260 sec
Host Timeout
:
260 sec
MLD Snooping Fast Leave Time :
1000 ms
VLAN v1
(4084) Snooping=Enabled
Port
Host
Age
Subscribed
Join Limit
Multicast
252
Multicast Commands
25
fe80::204:96ff:fe3a:ce50
ff02::1:ff3a:ce50
25
fe80::204:96ff:fe3a:ce50
All Groups
41
fe80::200:8ff:fe55:5c27
ff02::1:ff00:2
41
fe80::200:8ff:fe55:5c27
ff02::1:ff55:5c27
42
fe80::200:8ff:fe56:5c2b
ff02::1:ff00:2
42
fe80::200:8ff:fe56:5c2b
ff02::1:ff56:5c2b
s = static MLD member
* X480-48t.27 #
13
No Limit
14
No Limit
13
No Limit
13
No Limit
14
No Limit
13
No Limit
History
show mld ssm-map

show mld ssm-map {v6groupnetmask} {{vr} vr_name}
Description
Displays the status of MLD-SSM mapping feature on a VR (if it is enabled or disabled), and displays the
MLD-SSM mapping entries.
Syntax Description
v6groupnetmask
Displays the specific group information. When v6groupnetmask is not

specified, the SSM Mapping status and all SSM Mapping entries on the VR are
displayed.
vr vr_name
Default
Disabled.
Usage Guidelines
Use this command to display the status of MLD-SSM mapping feature on a VR (if it is enabled or
disabled), or to display the MLD-SSM mapping entries.
Multicast
253
Multicast Commands
Example
The following command displays MLD SSM mapping on a VR :
# show mld ssm-map
MLD SSM mapping : Enabled
Group
-----Flags
Source
----------ff33::1/128
d
2001:0DB8:1::3
d
2001:0DB8:1::4
ff33::2/128
2001:0DB8:1::5
2001:0DB8:1::6
Flags : (d) Dynamic address obtained from DNS server
Total Entries
: 6
When v6groupnetmask is specified, the SSM Mapping status and the SSM Mapping entries specific
to the group range on the VR are displayed.
The following example displays a group containing only DNS name. DNS in parenthesis indicates the
source is learned from the DNS server.
# show mld ssm-map ff33::1/128
Group
DNS Name
DNS Age
Sources
:
:
:
:
ff33::1/128
abc
1512 seconds
2001:0DB8:1::3(DNS)
2001:0DB8:1::4(DNS)
Total Entries
: 4
The following example displays a group not configured with DNS name.
# show mld ssm-map ff32::1/128
Group
: ff32::1/128
Sources
: 2001:0DB8:1::5
2001:0DB8:1::6
Total Entries
: 2
History
Multicast
254
Multicast Commands
show msdp memory

show msdp memory {detail | memoryType}
Description
This command displays current memory utilization of the MSDP process, including all virtual router
instances of the MSDP process.
Syntax Description
detail
Displays detailed statistics for all memory types.
memoryType
Displays statistics for a particular memory type.
Default
N/A.
Usage Guidelines
Use this command to view and diagnose the memory utilization of the MSDP process.
Example
The following displays current memory utilization of the MSDP process, including all virtual router
instances of the MSDP process:
show msdp memory
The following is sample output from this command:

MSDP Memory Information
----------------------Bytes Allocated: 79792 AllocFailed: 0 OversizeAlloc: 0
Current Memory Utilization Level: GREEN
Memory Utilization Statistics
----------------------------Size
16
32
48
64
80
96
128
256
1024
4096
8192 12288
--------- ----- ------ ------ ------ ------ ------ ------ ------ ----------- ------ ------ Used Blocks
0
0
256
263
3
0
2
0
1
0
0
4
peer
0
0
0
0
0
0
0
0
0
0
0
4
mesh-group
0
0
0
3
0
0
0
0
0
Multicast
255
Multicast Commands
0
0
0
sa-node
0
0
0
0
0
sa-entry
0
0
0
0
0
vr-node
0
0
0
0
0
rt-cache
0
0
0
0
0
rp-node
0
0
0
0
0
client
0
0
0
0
0
misc
0
0
0
0
0
255
255
0
0
0
0
1
0
2
0
0
0
0
0
0
0
0
5
0
0
0
0
0
0
History

show msdp [mesh-group {detail} | {mesh-group} mesh-group-name] {vr vrname}
Description
This command displays configuration information about MSDP mesh-groups.
Syntax Description
detail
Displays detailed information about MSDP mesh-groups.
mesh-group-name
Specifies the name of the MSDP mesh-group. The character string can be a
vrname
Default
N/A.
Usage Guidelines
Use this command to display configuration information about MSDP mesh-groups, as follows:
Multicast
256
Multicast Commands
For summary information, enter the show msdp mesh-group command.

For detailed information, enter the show msdp mesh-group detail command.
For detailed information about a specific mesh-group, enter the show msdp mesh-group name
command.
Example
The following command displays the peer count for a mesh-group:

MeshGroupName
PeerCount
------------------------------------------external
0
internal
0
msdp_mesh
4
The following command displays detailed information about a mesh-group called "msdp_mesh":
show msdp mesh-group "msdp_mesh"

Mesh Group Name
Peers
221.160.90.228
: msdp_mesh Num of Peers : 4

: 54.172.168.97
55.0.0.83
124.56.78.90
History
show msdp peer

Description
This command displays configuration and run-time parameters about MSDP peers.
Multicast
257
Multicast Commands
Syntax Description
detail
Displays detailed information about MSDP peers.
remoteaddr
vr_name
Default
N/A.
Usage Guidelines
Use this command to verify the configuration and run-time parameters for MSDP peers, as follows:
For summary information, enter the show msdp peer command.

For detailed information for all peers, enter the show msdp peer detail command.
For detailed information for a specific peer, enter the show msdp peer remoteaddr command.
Example
The following command displays configuration and run-time parameters for MSDP peers:
show msdp peer

Peer Address
AS
State
Up/Down
Resets SA_Cnt Name
---------------------------------------------------------------------------d 54.172.168.97
14490 DISABLED
00:31:36 0
0
test
*e 55.0.0.83
100
ESTABLISHED 00:21:04 1
0
to-Hawaii
-d 124.56.78.90
2345 DISABLED
00:31:36 0
0
-d 221.160.90.228 23456 DISABLED
00:31:36 0
0
Flags: (*) default peer, (d) disabled, (e) enabled
The following command displays output from an MSDP peer with the IP address 16.0.0.2:
* Switch.8 # show msdp
MSDP Peer
:
Enabled
:
Keepalive Interval
:
Source Address
:
Default Peer
:
configured
Process In Request
:
configured
Maximum SA Limit
:
configured
Input SA Filter
:
configured
State
:
Local Port
:
Multicast
peer 16.0.0.2
16.0.0.2
No
60
not known
No
AS Number
Holdtimer Interval
TTL Threshold
Default Peer Filter
:
:
:
:
Yes
In Request filter
: not
not configured
Mesh Group
: not
not configured
Output SA Filter
: not
DISABLED
0
Uptime/Downtime
Remote Port
: 00:00:02
: 0
100.100
75
0
not
258
Multicast Commands
In Total Msgs
In SA Msgs
In SA Req Msgs
In SA Resp Msgs
Time since Last Msg
Connection Attempts
RPF Fails
:
:
:
:
:
:
:
0
0
0
0
00:00:02
0
0
Out Total Msgs

Out SA Msgs
Out SA Req Msgs
Out SA Resp Msgs
Hold Tmr Exp in
Entered Established
Output Queue Size
:
:
:
:
:
:
:
0
0
0
0
00:00:00
0
0
History
show msdp sa-cache

show msdp [sa-cache | rejected-sa-cache] {group-address grp-addr} {source-address
src-addr} {as-number as-num} {originator-rp originator-rp-addr} {local} {peer
remoteaddr} {vr vrname}
Description
This command displays the SA cache database. The following quadruplet per SA cache entry displays:
{Group, Source, originating RP, and peer}. In addition, information about the following displays: the
cache uptime, aging, whether sources are local or remote, etc.
Syntax Description
grp-addr
Displays the SA cache within the specified group address range.
src-addr
Displays the SA cache within the specified source address range.
as-num
Displays all SA cache that originated from the specified Autonomous System (AS)
number.
originator-rp-addr
Displays all SA cache entries that were originated by the specified rendezvous
point.
local
Displays locally originated SA cache entries only.
remoteaddr
Displays the SA cache entries received from the MSDP peer with the specified IP
address.
vrname
Default
N/A.
Multicast
259
Multicast Commands
Usage Guidelines
Use this command to view and troubleshoot the SA cache database. There are various filtering criteria
you can use to display just a subset of the SA cache database. The following are some of the criteria,
which you can use together or separately, to display information about the SA cache:
Filtering on the group address range.

Filtering on the source address range.
Filtering on the originator rendezvous point address.
Filtering of the advertising MSDP peer.
Locally originated SA cache.
Rejected SA cache.
Example
The following command displays the SA cache database:
# show msdp sa-cache
Group Address
Source Address Originator
Peer Address
Age/Ageout In
------------------------------------------------------------------------------235.100.200.1
10.20.30.1
60.0.0.5
10.0.0.1
00:44:24/05:10
235.100.200.2
10.20.30.2
60.0.0.5
192.0.0.16
00:44:24/05:16
235.100.200.3
10.20.30.3
60.0.0.5
10.0.0.1
00:44:24/05:10
235.100.200.4
10.20.30.4
60.0.0.5
10.0.0.1
00:44:24/05:10
235.100.200.5
10.20.30.5
60.0.0.5
55.0.0.5
00:44:24/05:01
235.100.200.6
10.20.30.6
60.0.0.5
178.54.67.23
00:44:24/05:17
235.100.200.7
10.20.30.7
60.0.0.5
112.234.213.12 00:44:24/05:43
235.100.200.8
10.20.30.8
60.0.0.5
10.0.0.1
00:44:24/05:10
235.100.200.9
10.20.30.9
60.0.0.5
10.0.0.1
00:44:24/05:10
235.100.200.10 10.20.30.10
60.0.0.5
0.0.0.0
00:44:24/00:00
235.100.200.11 10.20.30.11
60.0.0.5
0.0.0.0
00:44:24/00:00
235.100.200.12 10.20.30.12
60.0.0.5
0.0.0.0
00:44:24/00:00
235.100.200.13 10.20.30.13
60.0.0.5
0.0.0.0
00:44:24/00:00
235.100.200.14 10.20.30.14
60.0.0.5
0.0.0.0
00:44:24/00:00
235.100.200.15 10.20.30.15
60.0.0.5
0.0.0.0
00:44:24/00:00
235.100.200.16 10.20.30.16
60.0.0.5
0.0.0.0
00:44:24/00:00
235.100.200.17 10.20.30.17
60.0.0.5
0.0.0.0
00:44:24/00:00
235.100.200.18 10.20.30.18
60.0.0.5
0.0.0.0
00:44:24/00:00
235.100.200.19 10.20.30.19
60.0.0.5
0.0.0.0
00:44:25/00:00
Number of accepted SAs
: 255
Number of rejected SAs
: 0
Flags: (a) Accepted, (f) Filtered by policy, (r) RPF check failed
History
Multicast
260
Multicast Commands
show msdp
show msdp {vr vrname}
Description
This command displays global configuration and run-time parameters for MSDP.
Syntax Description
vrname
Default
N/A.
Usage Guidelines
Use this command to verify the global configuration parameters of MSDP.
Example
The following command displays global configuration and run-time parameters for MSDP:
Switch.2 # show msdp
MSDP Enabled
Originator RP Addr
Store SA Cache
configured
Export Local SAs
configured
Max Rejected Cache
Num of Rejected SAs
Num of Local SAs
: No
: not configured
: Yes
VR-Name
: VR-Default
SA Cache ageout time : 360
SA Cache Server
: not
: Yes
Export SA filter
: not
: not configured
: 0
: 0
Encapsulate data
Total Num of SAs
AS Disp Format
: Yes
: 0
: Asdot
History
Multicast
261
Multicast Commands
show mvr cache

This command is provided for backward compatibility. The recommended command is:
show mcast cache {{vlan} vlan_name} {{[group grpaddressMask | grpaddressMask]
{source sourceIP | sourceIP}} {type [snooping | pim | mvr]}| {summary}}
The syntax for the original form of this command is:

show mvr cache {vlan vlan_name}
Description
Displays the multicast cache entries added by MVR.
Syntax Description
vlan_name
Default
N/A.
Usage Guidelines
If no VLAN is specified, information for all VLANs is displayed.
Example
The following command displays the multicast cache in the MVR range for the VLAN vlan110:
Switch.78 # show mvr cache vlan110
This command display is the same as for the following preferred command:
show mcast cache {{vlan} name} {{[group grpaddressMask | grpaddressMask] {source
sourceIP |sourceIP}} {type [snooping | pim | mvr]}| {summary}}
History
Multicast
262
Multicast Commands
show mvr
show mvr {vlan vlan_name}
Description
Displays the MVR configuration on the switch.
Syntax Description
vlan_name
Default
N/A.
Usage Guidelines
If a VLAN is specified, information for the VLAN is displayed.
Example
The following command displays the MVR configuration for the VLAN accounting:
show mvr accounting
History
show pim cache

show pim { ipv4 | ipv6 } cache {{detail} | {state-refresh} {mlag-peer-info}
{group_addr {source_addr}}}
Description
Displays the multicast cache entries created by PIM.
Multicast
263
Multicast Commands
Syntax Description
ipv4
Displays IPv4 PIM information
ipv6
Displays IPv6 PIM information.
detail
Specifies to display the information in detailed format.
group_addr
Specifies an IP group address.
source_addr
Specifies an IP source address.
state-refresh
Specifies to display the PIM cache entries with state refresh parameters.
mlag-peer-info
Shows MLAG peer related information.
Default
N/A.
Usage Guidelines
Displays the following information:
IP group address
IP source address / source mask
Upstream neighbor (RPF neighbor)
Interface (VLAN) to upstream neighbor
Cache expire time
Egress and prune interface list
When the detail option is specified, the switch displays the egress VLAN list and the pruned VLAN
list.
Example
The following command displays the PIM cache entry for group 239.255.255.1:
Switch.33 # show pim cache 239.255.255.1
Index Dest Group
Source
InVlan
Origin
[0000] 239.255.255.1
124.124.124.124 (WR) v4
Sparse
Entry timer is not run; UpstNbr: 200.124.124.24
EgressIfList = vbs15(0)(FW)(SM)(I)
[0001] 239.255.255.1
118.5.1.1 (S)
vbs5 Sparse
Expires after 186 secs UpstNbr: 0.0.0.0
RP: 124.124.124.124 via 200.124.124.24 in v4
EgressIfList = vbs15(0)(FW)(SM)(I) , vpim5(170)(FW)(SM)(S)
PrunedIfList = v4(0)(SM)
Number of multicast cache = 20
Entry flags :R: RP tree. S: Source tree. W: Any source.
Egress/Pruned interface flags :SM: Sparse Mode
DM: Dense Mode
Fw: Forwarding
PP: Prune pending
AL: Assert Loser
N: Neighbor present
Multicast
264
Multicast Commands
I: IGMP member present

Z: (*,g) join received
S: (s,g) join received

Y: (*,*,rp) join received
The following command displays the PIM-DM cache entry with state-refresh information for group
225.0.0.1:
Switch.5 # show pim cache state-refresh 225.0.0.1
Index Dest Group
Source
InVlan
[0001] 225.0.0.1
64.1.1.100 (S)
vixia
Refresh State: Originator(20), TTL: 16
EgressIfList = v36(0)(FW)(DM)(N)
[0001] 225.0.0.1
65.1.1.100 (S)
vixia
Refresh State: Not-Originator(25), TTL: 8
EgressIfList = v36(0)(FW)(DM)(N)
Origin
Dense
Not Pruned
Dense
Not Pruned
The following command displays the ingress VLAN information of all MLAG peers:
* (pacman debug) sw6.2 # show pim c mlag-peer-info
Index Dest Group
Source
InVlan
Origin
[0000] 226.1.1.1
61.2.2.2 (WR)
fifthteen Sparse
Entry timer is not run; UpstNbr: 51.15.15.2
Peer Ingress VLAN (ISC 1): 51.15.15.4/24 (Same)
EgressIfList = eight(0)(FW)(SM)(I) , five(0)(FW)(SM)(I) , ten(0)(FW)
(SM)(I)
[0001] 226.1.1.1
112.2.2.202 (S)
fifthteen Sparse
RP: 61.2.2.2 via 51.15.15.2 in fifthteen
Peer Ingress VLAN (ISC 1): 51.15.15.4/24 (Same)
EgressIfList = eight(0)(FW)(SM)(I) , five(0)(FW)(SM)(I)
PrunedIfList = ten(0)(SM)(AL)
History
This command was modified in ExtremeXOS 15.2 to display MLAG peer information.
The ipv4 and ipv6 keyword options were added in ExtreameXOS 15.3.
show pim snooping

show pim snooping {vlan} vlan_name
Multicast
265
Multicast Commands
Description
Displays the PIM snooping configuration for a VLAN.
Syntax Description
vlan_name
Specifies a VLAN.
Default
Disabled.
Usage Guidelines
None.
Example
The following command displays the PIM snooping configuration for the default VLAN:
BD-8810Rack3.8 # show pim snooping default
Global PIM Snooping DISABLED
Default
Snooping DISABLED
History
show pim
show pim {ipv4 | ipv6 | detail | rp-set {group_addr} | vlan vlan_name}
Description
Displays the PIM configuration and statistics.
Syntax Description
ipv4
Displays PIM IPv4 configuration information.
ipv6
Displays PIM IPv6 configuration information.
Multicast
266
Multicast Commands
detail
Displays show output in the detailed format.
group_addr
Specifies an IP multicast group, for which the RP is to be displayed.
vlan_name
Default
IPv4 is the default for the show pim {ipv4 | ipv6} command.
If no VLAN is specified, the configuration is displayed for all PIM interfaces.
If no multicast group is specified for the rp-set option (Rendezvous Point set), all RPs are displayed.
Usage Guidelines
The detail version of this command displays the global statistics for PIM, as well as the details of each
PIM enabled VLAN.
Example
The following command displays the global PIM configuration and statistics:
* sw4.30 # show pim
PIM Enabled, Version 2
PIM CRP Disabled
BSR state
: ACCEPT_PREFERRED ; BSR Hash Mask : 255.255.255.252
Current BSR Info
: 61.2.2.2 (Priority 20) expires after 78 sec
Configured BSR Info : 0.0.0.0 (Priority 0)
CRP Adv Interval
: 60 sec ; CRP Holdtime: 150
BSR Interval
: 60 sec ; BSR Timeout : 130
Cache Timer
: 210 sec ; Prune Timer : 210
Assert Timeout
: 210 sec ; Register Suppression Timeout,Probe: 60, 5
Generation Id
: 0x52af433d
Dense Neighbor Check : On
PIM-DM State Refresh TTL
: 16
PIM-DM State Refresh Source Active Timer : 210
PIM-DM State Refresh Origination Interval : 60
Threshold for Last Hop Routers: 0 kbps
Threshold for RP
: 0 kbps
Register-Rate-Limit-Interval : Always active
PIM SSM address range
: None
PIM Register Policy
: None
PIM Register Policy RP
: None
PIM IP Route Sharing
: Disabled
PIM IP Route Sharing Hash
: Source-Group-Next Hop
Register Checksum to exclude data
Active Sparse Ckts 10 Dense Ckts 0 State Refresh Ckts 0
Global Packet Statistics ( In
C-RP-Advs
0
Registers
0
RegisterStops
0
VLAN
Nbrs
Multicast
Cid
IP Address
Out
0
0
0
Designated
Drop )
0
0
0
Flags
Hello J/P
267
Multicast Commands
Router
Int
Int
eight
1 51.8.8.4
/ 24 51.8.8.6
rifms------- 30
60
2
fifthteen
2 51.15.15.4
/ 24 51.15.15.4
rifms------- 30
60
0
Legend: J/P Int: Join/Prune Interval
Flags : r - Router PIM Enabled, i - Interface PIM Enabled, f - Interface,
Forwarding Enabled, m - Interface Multicast Forwarding Enabled,
s - Sparse mode, d - Dense mode, c - CRP enabled,
t - Trusted Gateway configured, n - Multinetted VLAN,
p - Passive Mode, S - Source Specific Multicast, b - Border,
R - State Refresh Enabled.
The following command displays the detailed PIM configuration and statistics:
sw4.3 # show pim detail
PIM CRP Disabled
BSR state
: ACCEPT_ANY ; BSR Hash Mask : 255.255.255.252
Current BSR Info
: 0.0.0.0 (Priority 0)
CRP Adv Interval
BSR Interval
Cache Timer
Assert Timeout
Generation Id
: 0x533331c7
: 16
Threshold for RP
: 0 kbps
: None
PIM Register Policy
: None
: None
: Disabled
C-RP-Advs
0
Registers
0
RegisterStops
0
Out
0
0
0
Drop )
0
0
0
PIM SPARSE Interface[1] on VLAN eight is enabled and up

IP adr: 51.8.8.4
mask: 255.255.255.0
DR of the net: 51.8.8.6
DR Priority
: 1
Passive
: No
Hello Interval
: 30 sec
Neighbor Time out
: 105 sec
Join/Prune Interval
: 60 sec
Join/Prune holdtime
: 210 sec
Trusted Gateway
: none
CRP group List
: none with priority 0
Shutdown priority
: 1024
Source Specific Multicast : Disabled
Multicast
268
Multicast Commands
State Refresh
State Refresh Capable
Border
Neighbor IP address
51.8.8.3
51.8.8.6
: Off
: No
: No
Generation
Id
0x53332567
0x5332e6d8
Packet Statistics (In/Out)

Hellos
30
Join/Prunes
12
Grafts
0
State Refresh
0
15
0
0
0
State
Refresh
No
No
Expires
97
94
Bootstraps
Asserts
GraftAcks
DR
Priority
1
1
10
0
0
0
0
0
The following command displays the elected, active RP for the group 239.255.255.1:
show pim rp-set 239.255.255.1
Group
Mask
224.0.0.0
240.0.0.0
224.0.0.0
240.0.0.0
224.0.0.0
240.0.0.0
239.255.255.0
255.255.255.0
Elected RP is 124.124.124.124
C-RP
10.10.10.2
124.124.124.124
124.124.124.124
124.124.124.124
Origin
Bootstrap
Bootstrap
static
Bootstrap
Priority
0
0
0
0
The following command displays the PIM configuration for VLAN v3:
# show pim v3
PIM SPARSE Interface[2] on VLAN v3 is enabled and up
IP adr: 30.30.30.1
mask: 255.255.255.0
DR of the net: 30.30.30.2
DR Priority
Passive
Hello Interval
Neighbor Time out
Join/Prune Interval
Join/Prune holdtime
Trusted Gateway
CRP group List
Shutdown priority
Source Specific Multicast
State Refresh
Border
:
:
:
:
:
:
:
:
:
:
:
:
:
1
No
30 sec
105 sec
60 sec
210 sec
none
pimPolicy with priority 0
1024
Disabled
Off
No
No
Generation
Neighbor IP address
Id
30.30.30.2
0x5199b2db
Hellos
41
40
State
Refresh
No
Expires
105
DR
Priority
1
Bootstraps
20
Join/Prunes
Asserts
Grafts
GraftAcks
State Refresh
0
0
Multicast
269
Multicast Commands
The following is PIM IPv4 show output for the show register policy configuration, including drop
counters:
sw2.6 # show pim
PIM CRP Enabled on 1 interfaces
BSR state
: ELECTED ; BSR Hash Mask : 255.255.255.252
Current BSR Info
Configured BSR Info : 61.2.2.2 (Priority 20) in vlan l1
CRP Adv Interval
BSR Interval
Cache Timer
Assert Timeout
Generation Id
: 0x5331f58c
: 16
Threshold for RP
: 0 kbps
: None
PIM Register Policy
: sw1_rp_filter
: None
: Disabled
C-RP-Advs
1153
Registers
3251
RegisterStops
0
Out
1155
0
3239
Drop )
0
10
0
The following is PIM show output with IP Route Sharing information:

sw6.19 # show pim
PIM CRP Disabled
BSR state
: ACCEPT_PREFERRED ; BSR Hash Mask : 255.255.255.252
Current BSR Info
CRP Adv Interval
BSR Interval
Cache Timer
Assert Timeout
Generation Id
: 0x5332e6d1
: 16
Threshold for RP
: 0 kbps
: None
PIM Register Policy
: None
: None
: Disabled
Multicast
270
Multicast Commands

C-RP-Advs
0
Registers
0
RegisterStops
5376
VLAN
Nbrs
Cid
IP Address
Out
0
3315
0
Designated
Drop )
0
0
0
Flags
Router
Int
eight
2
eleven
Hello J/P
Int
1 51.8.8.6
/ 24 51.8.8.6
rifms------- 30
60
2 51.11.11.6
/ 24 51.11.11.6
rifms------- 30
60
The following command shows the output for the show pim ipv6 v3 command:
# show pim ipv6 v3
PIM SPARSE Interface[1] on VLAN v3 is enabled and up
Global IP adr
: 2010::2/64
Local IP adr
: fe80::204:96ff:fe27:f2c6/64
DR of the net
: fe80::204:96ff:fe27:f2c6
DR Priority
: 1
Passive
: No
Hello Interval
: 30 sec
Neighbor Time out
: 105 sec
Join/Prune Interval
: 60 sec
Join/Prune holdtime
: 210 sec
Trusted Gateway
: none
CRP group List
: none with priority 0
Shutdown priority
: 1024
Source Specific Multicast : Disabled
State Refresh
: Off
: No
Border
: No
Secondary Interfaces: 2003::2/ 64
Generation
State
DR
Neighbor IP address
Id
fe80::204:96ff:fe26:6c89
No
1
Hellos
5
Bootstraps
0
Join/Prunes
0
Asserts
0
Grafts
0
GraftAcks
0
State Refresh
0
Expires Refresh
0x5192f6f5
101
Priority
6
0
0
0
0
0
0
History
Multicast
271
Multicast Commands
The PIM-SSM information was added in ExtremeXOS 11.4.

Border VLAN information was added in ExtremeXOS 12.0.
The ipv6 keyword was added to PIM Register Policy Filter feature in ExtremeXOS 15.3.
DR Priority output was added in ExtremeXOS 15.3.2.
IP Route Sharing output was added in ExtremeXOS 15.3.2.
unconfigure igmp snooping vlan ports set join-limit

unconfigure igmp snooping {vlan} vlan_name ports port_list set join-limit
Description
Removes the join limit set on VLAN ports.
Syntax Description
vlan_name
port_list
Default
No limit.
Usage Guidelines
None.
Example
The following command removes the join limit for port 2:1 in the Default VLAN:
unconfigure igmp snooping "Default" ports 2:1 set join-limit
History
Multicast
272
Multicast Commands
unconfigure igmp ssm-map

unconfigure igmp ssm-map {{vr} vr-name}
Description
Unconfigures all SSM mappings on the virtual router.
Syntax Description
vr-name
Specifies a virtual router name. If the VR name is omitted, the switch uses the VR
specified by the current CLI VR context.
Default
N/A.
Usage Guidelines
None.
Example
The following command deletes all IGMP-SSM mappings on the virtual router "xyz":
unconfigure igmp ssm-map vr xyz
History
unconfigure igmp
unconfigure igmp
Multicast
273
Multicast Commands
Description
Resets all IGMP settings to their default values and clears the IGMP group table.
Syntax Description
Default
N/A.
Usage Guidelines
None.
Example
The following command resets all IGMP settings to their default values and clears the IGMP group table:
unconfigure igmp
History
unconfigure mld
unconfigure mld
Description
Resets all MLD settings to their default values and clears the MLD group table.
Description
Multicast
274
Multicast Commands
Default
N/A.
Usage Guidelines
None.
Example
The following command resets all MLD settings to their default values and clears the MLD group table:
unconfigure mld
History
unconfigure mld ssm-map

unconfigure mld ssm-map {{vr}vr_name }
Description
Deletes all MLD SSM Mapping entries on a VR.
Syntax Description
vr vr_name
Default
Disabled.
Usage Guidelines
Use this command to delete all MLD SSM Mapping entries on a specified VR.
ERROR: PIM IPv6 should be disabled before configuring MLD ssm-map on VRDefault
Multicast
275
Multicast Commands
Example
The following command deletes MLD SSM mapping on VR1 :
unconfigure mld ssm-map vr vr1
History

unconfigure msdp sa-cache-server {vr vrname}
Description
Removes the MSDP SA cache server.
Syntax Description
vrname
Specifies the name of the virtual router on which the MSDP cache server is configured. If
a virtual router name is not specified, it is extracted from the current CLI context.
Default
By default, the router does not send SA request messages to its MSDP peers when a new member joins
a group and wants to receive multicast traffic. The new member simply waits to receive SA messages,
which eventually arrive.
Usage Guidelines
Use this command to remove the MSDP SA cache server you specified with the configure msdp
sa-cache-server command.
Example
The following command removes the MSDP SA cache server:
Multicast
276
Multicast Commands
History
unconfigure pim border

unconfigure pim {ipv4 | ipv6} {vlan} vlan_name border
Description
Unconfigures a PIM VLAN that has been configured as a border VLAN, which is used to demarcate a
PIM domain.
Syntax Description
ipv4
ipv6
vlan_name
Default
By default, no PIM VLANs are configured as border VLANs.
Usage Guidelines
A PIM-SM domain is created by limiting the reach of PIM BSR advertisements. When a border VLAN is
configured, PIM BSR advertisements are not forwarded out of the PIM VLAN. Use the unconfigure
pim border command to remove the border functionality of the specified PIM VLAN.
Example
The following command unconfigures a PIM border on a VLAN called "vlan_border":
unconfigure pim vlan_border border
History
The IPv6 configuration option was added in ExtremeXOS 15.3.
Multicast
277
Multicast Commands

unconfigure pim {ipv4 | ipv6} ssm range
Description
Unconfigures the range of multicast addresses for PIM SSM.
Syntax Description
ipv4
ipv6
Default
By default, no SSM range is configured.
Usage Guidelines
You must disable PIM before configuring or unconfiguring a PIM-SSM range. Use the disable pim
command.
Initially, no range is configured for SSM. After a range is configured, you can remove the range with the
unconfigure pim ssm range command.
When no range is configured for PIM SSM, the switch does not use PIM SSM for any multicast groups.
Example
The following command removes the PIM SSM range:
History
The ipv4 and ipv6 keywords were added, giving an option to support this functionality in IPv6 as well,
in ExtremeXOS 15.3.
Multicast
278
Multicast Commands
unconfigure pim
unconfigure pim {ipv4 | ipv6} [{vlan vlan_name} | {tunnel} tunnel_name] border
Description
Resets all PIM settings on an IPv4 or IPv6 module, or on one or all VLANs, to their default values.
Syntax Description
ipv4
Specifies the IPv4 module from which PIM is to be unconfigured.
ipv6
Specifies the IPv6 module from which PIM is to be unconfigured.
vlan_name
Specifies the VLAN from which PIM is to be unconfigured.
tunnel
Specifies the tunnel which PIM is to be unconfigured.
tunnel_name
Specifies the tunnel name.
border
Specifies the border.
Default
If no VLAN is specified, the configuration is reset for all PIM interfaces.
Usage Guidelines
If you unconfigure PIM, you also unconfigure PIM-SSM, removing the PIM-SSM range.
Example
The following command resets all PIM settings on the VLAN accounting:
unconfigure pim vlan accounting
History
The ipv4 and ipv6 keywords were added, giving an option to support this functionality in IPv6 as well,
in ExtremeXOS 15.3.
Multicast
279
Multicast Commands
Multicast
280

Multicast ExtremeXOS 15.5

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Multicast ExtremeXOS 15.5

Uploaded by

Copyright:

Available Formats

Multicast

ExtremeXOS 15.5 User Guide

Copyright 20112014 All rights reserved.

Chapter 1: Multicast Routing and Switching.........................................................................12

Chapter 2: IPv6 Multicast....................................................................................................... 60

Chapter 4: Multicast Commands............................................................................................77

configure igmp snooping vlan ports add dynamic group...........................................................................100

configure mvr delete vlan.............................................................................................................................................153

show msdp peer............................................................................................................................................................... 257

Alerts you to...

Important features or instructions.

Risk of personal injury, system damage, or loss of data.

Risk of severe personal injury.

This command or section is new for this release.

Table 2: Text Conventions

The words enter and

Words in italicized type

BlackDiamond X8 series switch

ExtremeXOS User Guide

BlackDiamond 8800 Series Switches Hardware Installation Guide

Ridgeline Installation and Upgrade Guide

SDN OpenFlow Implementation Guide

Navigating the ExtremeXOS User Guide

1 Multicast Routing and Switching

Multicast Routing Overview

Multicast Routing and Switching

Multicast Table Management

IP Multicast Hardware Lookup Modes

Multicast Routing and Switching

multicast MAC addresses: 01:00:5e:00:00:xx, 33:33:00:00:00:xx, 33:33:00:00:01:xx, or

Multicast Routing and Switching

Platforms with External-Tables (TCAM)

Multicast Routing and Switching

This limitation applies to "mixed-mode", too.

Multicast Routing and Switching

IPv4 Multicast Route Table

Multicast Routing and Switching

IP Multicast Group Table

Capacity Restrictions for Mixed Installations

Multicast Routing and Switching

PIM Edge Mode

PIM Dense Mode

Multicast Routing and Switching

Traffic was not received on RPF interface towards the source.

Figure 1: PIM-DM Operation

Multicast Routing and Switching

PIM Sparse Mode

Multicast Routing and Switching

PIM Mode Interoperation

PIM Source Specific Multicast

Multicast Routing and Switching

SSM range Mode

Include Src Action

-the group is Send IGMPv3

-the group is Send IGMPv3

-the group is Send IGMPv3

Multicast Routing and Switching

Table 3: Using PIM-SSM While Sending IGMPV3 Joins (IPv4) (continued)

SSM range Mode

Include Src Action

-the group is Send IGMPv3

-the group is Send IGMPv3

-the group is Send IGMPv3

Multicast Routing and Switching