multicast - extreme networksextrcdn.extremenetworks.com/wp-content/uploads/2014/04/multicast.… ·...

MulticastExtremeXOS 15.5 User Guide

120936-00 Rev. 2

Published June 2014

Copyright © 2011–2014 All rights reserved.

Legal NoticeExtreme 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 thisdocument and its website without prior notice. The reader should in all cases consultrepresentatives 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 documentare subject to change without notice.

TrademarksExtreme Networks and the Extreme Networks logo are trademarks or registered trademarks ofExtreme Networks, Inc. in the United States and/or other countries.All other names (including any product names) mentioned in this document are the property oftheir respective owners and may be trademarks or registered trademarks of their respectivecompanies/owners.For additional information on Extreme Networks trademarks, please see: www.extremenetworks.com/company/legal/trademarks/

SupportFor product support, including documentation, visit: www.extremenetworks.com/support/

For information, contact:Extreme Networks, Inc.145 Rio RoblesSan Jose, California 95134USA

http://extremenetworks.com/company/legal/trademarks

http://www.extremenetworks.com/support/

Table of ContentsPreface.........................................................................................................................................8

Conventions.............................................................................................................................................................................8Related Publications............................................................................................................................................................9Providing Feedback to Us.............................................................................................................................................. 10

Navigating the ExtremeXOS User Guide...........................................................................................................................11

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

Chapter 2: IPv6 Multicast....................................................................................................... 60Multicast Listener Discovery (MLD) Overview....................................................................................................60Managing MLD.................................................................................................................................................................... 60

Chapter 3: MSDP...................................................................................................................... 69MSDP Overview.................................................................................................................................................................. 69PIM Border Configuration.............................................................................................................................................. 70MSDP Peers...........................................................................................................................................................................70MSDP Mesh-Groups...........................................................................................................................................................72Anycast RP............................................................................................................................................................................ 73SA Cache................................................................................................................................................................................ 75Redundancy.......................................................................................................................................................................... 76SNMP MIBs.............................................................................................................................................................................76

Chapter 4: Multicast Commands............................................................................................77clear igmp group................................................................................................................................................................. 81clear igmp snooping......................................................................................................................................................... 82clear mld counters............................................................................................................................................................. 83clear mld group...................................................................................................................................................................84clear mld snooping............................................................................................................................................................84clear msdp counters......................................................................................................................................................... 85clear msdp sa-cache.........................................................................................................................................................87clear pim cache................................................................................................................................................................... 88clear pim snooping............................................................................................................................................................89configure forwarding ipmc compression...............................................................................................................90configure forwarding ipmc lookup-key....................................................................................................................91configure igmp router-alert receive-required......................................................................................................92configure igmp router-alert transmit....................................................................................................................... 93configure igmp snooping filters..................................................................................................................................94configure igmp snooping flood-list...........................................................................................................................96configure igmp snooping leave-timeout................................................................................................................ 98configure igmp snooping timer.................................................................................................................................. 98

Multicast 3

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

Table of Contents

Multicast 4

configure mvr delete vlan.............................................................................................................................................153configure mvr mvr-address......................................................................................................................................... 154configure mvr static group.......................................................................................................................................... 155configure pim add vlan.................................................................................................................................................. 156configure pim border...................................................................................................................................................... 158configure pim cbsr........................................................................................................................................................... 159configure pim crp static................................................................................................................................................ 160configure pim crp timer.................................................................................................................................................. 161configure pim crp vlan................................................................................................................................................... 162configure pim delete vlan............................................................................................................................................. 163configure pim dr-priority.............................................................................................................................................. 164configure pim iproute sharing hash.........................................................................................................................165configure pim register-policy rp .............................................................................................................................. 166configure pim register-policy..................................................................................................................................... 167configure pim register-checksum-to...................................................................................................................... 168configure pim register-rate-limit-interval............................................................................................................. 169configure pim register-suppress-interval register-probe-interval........................................................... 170configure pim shutdown-priority............................................................................................................................... 171configure pim spt-threshold........................................................................................................................................ 172configure pim ssm range...............................................................................................................................................173configure pim ssm............................................................................................................................................................ 174configure pim state-refresh timer origination-interval...................................................................................175configure pim state-refresh timer source-active-timer................................................................................. 176configure pim state-refresh ttl................................................................................................................................... 177configure pim state-refresh......................................................................................................................................... 178configure pim timer vlan............................................................................................................................................... 179configure pim vlan trusted-gateway...................................................................................................................... 180create msdp mesh-group.............................................................................................................................................. 181create msdp peer..............................................................................................................................................................182delete msdp mesh-group............................................................................................................................................. 183delete msdp peer..............................................................................................................................................................184disable igmp snooping vlan fast-leave...................................................................................................................185disable igmp snooping................................................................................................................................................... 185disable igmp ssm-map................................................................................................................................................... 187disable igmp........................................................................................................................................................................ 187disable ipmcforwarding ipv6...................................................................................................................................... 188disable ipmcforwarding................................................................................................................................................. 189disable mld...........................................................................................................................................................................190disable mld snooping....................................................................................................................................................... 191disable mld-ssm map...................................................................................................................................................... 192disable msdp data-encapsulation.............................................................................................................................193disable msdp export local-sa......................................................................................................................................194disable msdp peer............................................................................................................................................................ 195disable msdp process-sa-request.............................................................................................................................195disable msdp....................................................................................................................................................................... 197disable mvr...........................................................................................................................................................................197disable pim iproute sharing......................................................................................................................................... 198disable pim snooping......................................................................................................................................................199disable pim ssm vlan..................................................................................................................................................... 200

Table of Contents

Multicast 5

disable pim...........................................................................................................................................................................201enable igmp snooping vlan fast-leave.................................................................................................................. 202enable igmp snooping with-proxy..........................................................................................................................203enable igmp snooping.................................................................................................................................................. 204enable igmp ssm-map...................................................................................................................................................205enable igmp........................................................................................................................................................................206enable ipmcforwarding ipv6......................................................................................................................................207enable ipmcforwarding................................................................................................................................................ 208enable mld.......................................................................................................................................................................... 209enable mld snooping with-proxy..............................................................................................................................210enable mld snooping........................................................................................................................................................ 211enable mld-ssm map........................................................................................................................................................ 211enable msdp data-encapsulation..............................................................................................................................212enable msdp export local-sa....................................................................................................................................... 213enable msdp peer............................................................................................................................................................. 215enable msdp process-sa-request..............................................................................................................................216enable msdp........................................................................................................................................................................ 217enable mvr............................................................................................................................................................................218enable pim iproute sharing.......................................................................................................................................... 219enable pim snooping..................................................................................................................................................... 220enable pim ssm vlan........................................................................................................................................................ 221enable pim........................................................................................................................................................................... 222mrinfo.....................................................................................................................................................................................223mtrace................................................................................................................................................................................... 224refresh mld ssm-map..................................................................................................................................................... 227rtlookup rpf.........................................................................................................................................................................228rtlookup................................................................................................................................................................................ 229show igmp group............................................................................................................................................................ 230show igmp snooping cache........................................................................................................................................232show igmp snooping vlan filter.................................................................................................................................233show igmp snooping vlan static.............................................................................................................................. 234show igmp snooping vlan............................................................................................................................................235show igmp snooping......................................................................................................................................................236show igmp ssm-map......................................................................................................................................................237show igmp...........................................................................................................................................................................238show ipmroute.................................................................................................................................................................. 239show iproute multicast.................................................................................................................................................240show L2stats...................................................................................................................................................................... 242show mcast cache...........................................................................................................................................................243show mcast ipv6 cache................................................................................................................................................ 245show mld............................................................................................................................................................................. 246show mld counters......................................................................................................................................................... 248show mld group............................................................................................................................................................... 249show mld snooping vlan filter................................................................................................................................... 250show mld snooping vlan static................................................................................................................................. 250show mld snooping..........................................................................................................................................................251show mld ssm-map.........................................................................................................................................................253show msdp memory.......................................................................................................................................................255show msdp mesh-group.............................................................................................................................................. 256

Table of Contents

Multicast 6

show msdp peer...............................................................................................................................................................257show msdp sa-cache..................................................................................................................................................... 259show msdp...........................................................................................................................................................................261show mvr cache............................................................................................................................................................... 262show mvr............................................................................................................................................................................. 263show pim cache................................................................................................................................................................263show pim snooping........................................................................................................................................................ 265show pim..............................................................................................................................................................................266unconfigure igmp snooping vlan ports set join-limit..................................................................................... 272unconfigure igmp ssm-map........................................................................................................................................273unconfigure igmp.............................................................................................................................................................273unconfigure mld............................................................................................................................................................... 274unconfigure mld ssm-map.......................................................................................................................................... 275unconfigure msdp sa-cache-server........................................................................................................................276unconfigure pim border................................................................................................................................................277unconfigure pim ssm range........................................................................................................................................ 278unconfigure pim............................................................................................................................................................... 279

Table of Contents

Multicast 7

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 IconsIcon 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 ConventionsConvention Description

Screen displaysThis typeface indicates command syntax, or represents information as it appears onthe screen.

The words enter andtype

When you see the word “enter” in this guide, you must type something, and then pressthe Return or Enter key. Do not press the Return or Enter key when an instructionsimply says “type.”

[Key] names Key names are written with brackets, such as [Return] or [Esc]. If you must press twoor 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 inthe text. Italics are also used when referring to publication titles.

Multicast 8

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 inthe heading for the section describing that implementation in the ExtremeXOS commanddocumentation. In many cases, although the command is available on all platforms, each platform usesspecific keywords. These keywords specific to each platform are shown in the Syntax Description anddiscussed 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 tothe product as the “switch.”

Related PublicationsDocumentation for Extreme Networks products is available at: www.extremenetworks.com. Thefollowing 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 isavailable at: www.extremenetworks.com/services/osl-exos.aspx

Preface

Multicast 9

http://www.extremenetworks.com/go/documentation

http://www.extremenetworks.com/services/osl-exos.aspx

Providing Feedback to Us

We are always striving to improve our documentation and help you work better, so we want to hearfrom 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 aboutthis document, please contact us using our short online feedback form. You can also email us directly at [email protected].

Preface

Multicast 10

http://marketing.extremenetworks.com/acton/form/1730/001b:d-0001/0/index.htm

mailto:[email protected]?subject=Feedback

Navigating the ExtremeXOS User Guide

This guide consists of the following eight volumes that contain feature descriptions, conceptualmaterial, 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

http://extrcdn.extremenetworks.com/wp-content/uploads/2014/04/Basic_Switch_Operation.pdf

http://extrcdn.extremenetworks.com/wp-content/uploads/2014/04/Policies_and_Security.pdf

http://extrcdn.extremenetworks.com/wp-content/uploads/2014/04/Layer_2_Basics.pdf

http://extrcdn.extremenetworks.com/wp-content/uploads/2014/04/Layer_2_Protocols.pdf

http://extrcdn.extremenetworks.com/wp-content/uploads/2014/04/Layer_3_Basics.pdf

http://extrcdn.extremenetworks.com/wp-content/uploads/2014/04/Layer_3_Unicast_Protocols.pdf

http://extrcdn.extremenetworks.com/wp-content/uploads/2014/04/Multicast.pdf

http://extrcdn.extremenetworks.com/wp-content/uploads/2014/04/Advanced_Features.pdf

1 Multicast Routing and Switching

Multicast Routing OverviewMulticast Table ManagementPIM OverviewIGMP OverviewConfiguring EAPS Support for Multicast TrafficConfiguring IP Multicast RoutingMulticast VLAN RegistrationDisplaying Multicast InformationTroubleshooting PIM

This chapter introduces the features and usage of IP multicasting, which allows a single host on anetwork to send a packet to a group of hosts. For more information on IP multicasting, refer to thefollowing publications:

• RFC 1112—Host Extension for IP Multicasting

• RFC 2236—Internet Group Management Protocol, Version 2

• RFC 3569—SSM for IPv4/IPv6 (only for IPv4)

• PIM-SM Version 2—draft-ietf-pim-sm--v2-new-05

• RFC 4601—PIM 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 3569—draft-ietf-ssm-arch-06.txt PIM-SSM PIM Source Specific Multicast

• PIM-DM Draft IETF Dense Mode—draft-ieft-idmr-pimdm-05.txt, draft-ieft-pim-dm-new-v2-04.txt

• RFC 3376—Internet 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 OverviewMulticast routing and switching is the functionality of a network that allows a single host (the multicastserver) to send a packet to a group of hosts. With multicast, the server is not forced to duplicate andsend enough packets for all the hosts in a group. Instead, multicast allows the network to duplicatepackets for allof the hosts in a group. Multicast greatly reduces the bandwidth required to send data toa group of hosts. IP multicast routing is a function that allows multicast traffic to be forwarded fromone subnet to another across a routing domain.

IP multicast routing requires the following functions:

• A router that can forward IP multicast packets

Multicast 12

http://www.ietf.org/html.charters/pim-charter.html

http://www.ietf.org/html.charters/pim-charter.html

• 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))

NoteYou should configure IP unicast routing before you configure IP multicast routing.

Multicast Table ManagementThe 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 ModesExtreme platforms support various hardware forwarding lookup modes by using a combination of L3hash table and L2 (FDB) table. Refer to Multicast Table Management for details on these tables. Thescalability limits vary based on the lookup mode used.

Configuration Options

Configuration options allow you to choose the hardware forwarding lookup mode for multicastforwarding. 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 platformsexcept 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 appliedon installing the cache entries in the hardware:

Multicast cache entries requiring forwarding across VLANs would be installed in the L3 IPmulticast table. This includes PIM, MVR, and PVLAN cache entries.Multicast cache entries requiring L2 forwarding within a VLAN are installed in the L2 table. Thisincludes 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) areinstalled in the L3 IP multicast table as needed. These reserved addresses map to the following

Multicast Routing and Switching

Multicast 13

multicast MAC addresses: 01:00:5e:00:00:xx, 33:33:00:00:00:xx, 33:33:00:00:01:xx, or33:33:ff:xx:xx:xx.

NoteAny change in the lookup key configuration causes all cache entries to be cleared, andtraffic is temorarily dropped until the system re-learns the multicast caches andassociated subscriptions.

Notemac-vlan mode helps increase scaling and is particularly useful on platforms like theSummit X440, which has limited L3 hardware table entries. This mode is also supported inother Summit platforms, and the BlackDiamond8K and BlackDiamond X.

Notemac-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 HALthe same way as today. EXOS hardware abstraction layer (HAL) applies the logic explained above andinstalls the cache entries in the appropriate hardware table. If the cache entry needs to be installed inthe L2 multicast table, HAL derives the MAC address based on the standard logic and installs the MACentry in the L2 table.

The IP multicast address to MAC address mapping is not validated for the received/forwardedmulticast packets in EXOS to date. If the lookup mode is configured either as "mac-vlan" or "mixed-mode", the multicast kernel module is modified to validate this mapping and, if a packet does not usethe standard mapping, the packet is dropped.

IPMC Compression

In order to increase the scaling of multicast entries, EXOS implements a feature called IPMCcompression which allows multiple <S,G,V> (or <*,G,V>) IP multicast FDB entries to utilize the same IPmulticast group table entry when the associated egress port lists are the same. The base IP multicastcompression 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 cacheentries 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 inthe L2 table and use the L2MC table for hardware forwarding. If there is a dynamic <MAC,VLAN> entryfrom MCMGR and a static entry from FDB manager, the static entry takes precedence and the dynamicentry would get deleted in hardware. Compression of L2MC indices is not supported on these types ofentries. 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 installedas static in the hardware L2 table to avoid undesirable interactions with L2 protocol or useradministered FDB flushing. These multicast L2 entries also take precedence over dynamic unicast L2MAC entries. If there is a hash bucket collision upon inserting an L2 multicast entry, it will replaceanother 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, L3routes, ACLs, and/or IPMC forwarding entries based on configuration. Only the internal L2 table is usedto store <MAC,VLAN> forwarding entries for IP multicast caches on these platforms due to a hardwarelimitation. Additionally, the configure forwarding external-table l2-and-l3-and-ipmc configuration option, which uses the external TCAM to store <S,G,V> entries, is not compatiblewith 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 withthe ingress virtual router. In this feature, <MAC, VLAN> cache entries are stored in the L2 table whichdoes not additionally include the VRID. However, user VRs are still supported since the VLAN portion ofthe 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 limitingimplementation 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 insoftware.

Supported Platforms

This feature is implemented on all Summit, BD8K, and BDX8 platforms.

NoteThe mixed-mode setting is supported on all platforms except: BD8K "e2-series", 8500-G48T-e.

Limitations

The following limitations exist for the L2MC table feature:

• The "mixed-mode" configuration option is not allowed on platforms using older chipsets. Please seethe "Platforms Supported" section for details.

• When the "mixed-mode" configuration option is engaged on BD8K platforms, newly inserted slotswhich do not support "mixed-mode" will fail initialization.

• On SummitStack, this same condition causes the following log to be displayed repeatedly every 30seconds:

<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 modePrivate 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 lowerorder 23 bits of the IP multicast address is used in the MAC address derivation. As only 23 bits ofMAC 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 isinstalled in hardware based on the IGMP group membership of received traffic’s destinationmulticast IP address. After this installation, traffic to any of the remaining 31 addresses is deliveredbased on the existing cache entry and the actual receiver list of the remaining 31 addresses will notbe honored.

IPv6 multicast streams use multicast MAC addresses in the form 33:33:xx:xx:xx:xx. The lower 24 bitsof the IPv6 multicast address are used to derive the MAC address. So, the address ambiguity issue isalso applicable to IPv6 with more severity. Given this condition, we do not recommend usingoverlapping 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. Forexample, 224.0.0.5 (address used for OSPF) and 225.0.0.5 would use the same MAC address01: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 addressesmapping to the LNCB block will not be installed in the L2 table, resulting in software forwarding forthose 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 rangeof 0x00000001 to 0x3FFFFFFF. As a result, EXOS switches flood traffic addressed to ff02::/98 toall ports of the VLAN. Since the lower 32 bits of IPv6 multicast addresses are mapped to themulticast 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 besoftware forwarded.

In addition, the following important IPv6 multicast addresses cannot be installed as hardwareforwarding entries:

DHCP: All-dhcp-agents address FF02:0:0:0:0:0:1:2All-dhcp-servers address FF05:0:0:0:0:0:1:3Neighbor Discovery (ND): Solicited-node-address FF02::1:FF00:0000/104

Therefore, the following multicast MAC addresses are not programmed in hardware, and thecorresponding packets are handled in slowpath: 33:33:00:00:01:xx , 33:33:ff:xx:xx:xx

• Given the issues with IP multicast address to MAC address mapping, no attempt is made to mergesubscriber lists of multiple overlapping IP groups.

• The following limitation regarding IPMC compression is also applicable for this feature, because thisfeature uses the same L2MC entry for multiple l2 multicast entries with same egress ports. All MAC-VLAN forwarding entries utilizing the same L2MC entry will be subject to a single BD8K backplanelink (12Gbps).


Multicast 16

• On those platforms supporting the "external-table" (X480, BD8K "xl-series"), any IP multicastcaches installed in the L2 table will be only installed in the internal L2 table due to a hardwarelimitation which prevents L2MC access from the ESM (External Search Machine).

• When IP multicast forwarding entries are installed as <MAC,VLAN>, IGMP or MLD packets whichhave a MAC-DA=<group> will cause the refresh of the IP multicast cache, preventing timely entryage-out.

• The L2MC table is limited to 1K entries on all platforms. This means that only up to 1K unique portlists can be addressed from the <MAC,VLAN> IP multicast forwarding entries that are stored in theL2 table. Additionally, statically created multicast FDB entries do not perform L2MC indexcompression.

IPv4 Multicast Route TableBeginning with Release 12.1, all IP multicast routes are stored and maintained in the software multicastroute 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 theinterface on which the router would send a packet to the source. The switch forwards only thosepackets 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 routecompression 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 selectbetween 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 themulticast table.

The advantage to having separate routing tables for unicast and multicast traffic is that the two typesof traffic can be separated, using different paths through the network.

L3 Hash TableThe L3 hash table is introduced in Introduction to Hardware Forwarding Tables. The L3 hash tablestores 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 IPMulticast Group table.

To make more space available in the L3 hash table for IPv4 and IPv6 multicast groups, you can do thefollowing:


Multicast 17

• Configure the extended IPv4 host cache feature to move IPv4 local and remote routes to the LPMtable as described in Extended IPv4 Host Cache.

• Configure BlackDiamond 8900 xl-series modules or Summit X480 series switches to do one of thefollowing:

• 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 inthe external LPM table.

For more information, see the description for the configure forwarding external-tables command.

NoteTo benefit from the use of the external LPM tables, you must leave the IP multicastcompression feature enabled, which is the default setting.

IP Multicast Group TableThe 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 hashentries 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 InstallationsA mixed installation is a switch configuration that contains I/O modules with different table sizes. Theactual IP multicast group table capacity for the switch is set to that supported on the I/O module withthe smallest tables. To increase the capacity of IP multicast tables, all I/O modules must support theminimum table size you want.

Multicast forwarding entries are programmed in all I/O modules. Only multicast traffic ingressing agiven I/O module utilize these forwarding entries. Other egress-only I/O modules only require themulticast group table entry.

If you add a higher-capacity I/O module to a switch that has been running with lower capacitymodules, the switch generates a message and adjusts the table capacity on the higher-capacity card tothat 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. Theentry from this table provides an index to the L2MC table that specifies the egress ports.


Multicast 18

PIM OverviewProtocol Independent Multicast (PIM) is the de-facto standard for routing multicast traffic over theInternet. Other multicast routing protocols such as DVMRP and MOSPF are sometimes used incontrolled environment, but are not widely deployed. PIM does not depend on a particular unicastrouting 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 theuser. 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 twoflavors, 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 throughIGMP) from the network segment. PIM-DM is based on a "flood and prune" mechanism, where everyone receives traffic until they explicitly inform (through the PIM-DM prune mechanism) that they do notwant that particular stream. Thus, PIM-DM is typically deployed in topologies where listeners aredensely populated. And PIM-SM is typically deployed where the receivers are sparsely populated overthe 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, someinterfaces can run dense mode, while others run sparse mode. The switch supports both dense modeand sparse mode operation.

The switch also supports PIM snooping.

PIM Edge ModePIM 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 ofpassive interfaces (within the limit of the maximum IP interfaces).

• Only PIM Sparse Mode (PIM-SM) is supported.

NoteThis feature is supported at and above the license level listed for this feature in the licensetables in the Feature License Requirements document.

Active PIM interfaces can have other PIM enabled routers on them. Passive interfaces should only havehosts sourcing or receiving multicast traffic. If another PIM router is connected to a multi-access VLANthen passive mode should not be enabled for that respective VLAN. OSPF passive mode should not beenabled for a VLAN when a PIM neighbor is present.

PIM Dense ModeProtocol-Independent Multicast - Dense Mode (PIM-DM) is a multicast routing protocol. PIM dense-mode is a flood and prune-based protocol. Convergence is based on the downstream routers' responsefor the traffic received. The downstream router in turn floods the traffic to its own downstreaminterfaces. Each router sends prune to the interface on which it received the traffic under the followingconditions:


Multicast 19

http://extrcdn.extremenetworks.com/wp-content/uploads/2014/04/ExtremeXOS_Feature_License_Requirements.pdf

• 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 describedin the following sections:

NoteFor additional information on PIM-DM, see RFC 3973, Protocol Independent Multicast - DenseMode (PIM-DM): Protocol Specification.

PIM-DM Without State Refresh

PIM-DM is a broadcast and prune protocol, which means that multicast servers initially broadcast trafficto all destinations, and then switches later prune paths on which there are no receivers. The followingfigure 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 floodsmulticast traffic to both neighbors S2 and S3 which in turn flood multicast traffic to S4 and S5. S4 hasIGMP 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 activebranch, and the red line shows the prune sent upstream for the pruned branch. After outgoing interfaceV2 is pruned from the multicast tree, subsequent multicast traffic from S1 flows only through S2 and S4and is not forwarded to S3.

After S3 sends a prune upstream, S3 starts a prune hold time timer on outgoing interface V5. When thistimer expires, S3 adds V5 back to the multicast egress list and sends a graft upstream to pull multicasttraffic down again. When multicast traffic arrives from S1, it is forwarded to S5, which repeats theupstream prune message because it still has no members. This prune, time-out, and flood processrepeats as long as the traffic flow exists and no members are on the pruned branch, and this processconsumes bandwidth during every cycle.



Multicast 20


PIM-DM routers perform reverse path multicasting (RPM). However, instead of exchanging its ownunicast route tables for the RPM algorithm, PIM-DM uses the existing unicast routing table for thereverse 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 periodicallysending a state refresh control message down the source tree. These control messages reset the prunehold time timer on each pruned interface and prevent the bandwidth waste that occurs with eachprune, 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-availabilityof a route. Without PIM-DM State Refresh, multicast traffic is blocked for minutes (due to a time-out onthe upstream routers). In the meantime if an IGMP member or a PIM-DM neighbor joins S5, there is noway to pull traffic down immediately because S5 does not have any S, G information. State refreshcontrol messages solve this problem by indicating S, G state information periodically to all downstreamrouters. When S5 receives a state refresh from S3, it scans the S, G information and all pending requestsfrom PIM-DM neighbors and IGMP members. If there are pending requests for the group in the staterefresh message, S5 can immediately send a graft message upstream to circumvent the upstreamtimers 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 ModeUnlike PIM-DM, Protocol-Independent Multicast - Sparse Mode (PIM-SM) is an explicit join and pruneprotocol, which means that multicast receivers, and the routers that support them, must join multicastgroups before they receive multicast traffic. When all receivers on a network branch leave a multicastgroup, that branch is pruned so that the multicast traffic does not continue to consume bandwidth onthat branch. PIM-SM supports shared trees as well as shortest path trees (SPTs). PIM-SM is beneficialfor large networks that have group members that are sparsely distributed.


Using PIM-SM, the router sends a join message to the rendezvous point (RP). The RP is a centralmulticast router that is responsible for receiving and distributing the initial multicast packets. You canconfigure a dynamic or static RP.

When a router has a multicast packet to distribute, it encapsulates the packet in a unicast message andsends it to the RP. The RP decapsulates the multicast packet and distributes it among all memberrouters.


Multicast 21


When a router determines that the multicast rate has exceeded a configured threshold, that router cansend an explicit join to the originating router. When this occurs, the receiving router gets the multicastdirectly from the sending router and bypasses the RP.

NoteYou can run either PIM-DM or PIM-SM per virtual LAN (VLAN).

PIM Mode InteroperationAn Extreme Networks switch can function as a PIM multicast border router (PMBR). A PMBR integratesPIM-SM and PIM-DM traffic.

When forwarding PIM-DM traffic into a PIM-SM network, the PMBR acts as a virtual first hop andencapsulates 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 PMBRsends a (*.*.RP) join message to the RP, and the PMBR forwards traffic from the RP into the PIM-DMnetwork.

No commands are required to enable PIM mode interoperation. PIM mode interoperation isautomatically enabled when a dense mode interface and a sparse mode interface are enabled on thesame switch.

PIM Source Specific Multicast

PIM-SM works well in many-to-many multicasting situations. For example, in video conferencing, eachparticipating site multicasts a stream that is sent to all the other participating sites. However, PIM-SM isoverly complex for one-to-many multicast situations, such as multimedia content distribution orstreaming stock quotes. In these and similar applications, the listener is silent and can know the sourceof the multicast in advance, or can obtain it. In these situations, there is no need to join an RP, as thejoin request can be made directly towards the source.


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 arequest 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 sourcefirst became available with IGMPv3. The PIM-SSM capable router interprets the IGMPv3 message toinitiate a PIM-SM join towards the source.

NoteIGMPv1 and IGMPv2 hosts can use PIM SSM if IGMP-SSM mapping is enabled and configuredon 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 andoutside the SSM range for IPv4:

Table 3: Using PIM-SSM While Sending IGMPV3 Joins (IPv4)ExtremeXOS 15.4 ExtremeXOS 15.5

SSMEnabled

SSM range Mode Include Src Action Observation Action Observation

No Yes Incl Yes Send IGMPv3join in SSMrange

-the group islearned -(*;G)is not created

Send IGMPv3join in SSMrange

-the group islearned - (*;G)is created

No Yes Incl Yes Send IGMPv3out of SSMrange

-the group islearned -no(*;G) iscreated

Send IGMPv3out of SSMrange


No Yes Excl No Send IGMPv3join in SSMrange

-the group isnot learned(PD4-3138792131) -no (*;G)is created


-the group isnot learned(PD4-3138792131) -no (*;G)is created

No Yes Excl No Send IGMPv3join out ofSSM range


Send IGMPv3join out ofSSM range


No Yes Excl Yes Send IGMPv3join in SSMrange

-the group isnot learned -no (*;G) iscreated



No Yes Excl Yes Send IGMPv3join out SSMrange


Send IGMPv3join out SSMrange


No No Incl Yes Send IGMPv3join


Send IGMPv3join

-the group islearned -(*;G)is created

No No Excl No Send IGMPv3join

-the group islearnt - (*;G)is created

Send IGMPv3join

-the group islearnt - (*;G)is created

No No Excl Yes Send IGMPv3join


Send IGMPv3join



Multicast 23

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

SSMEnabled


Yes Yes Incl Yes Send IGMPv3join in SSMrange

-the group islearned -(S;G)is created


-the group islearned -(S;G)is created

Yes Yes Incl Yes Send IGMPv3out of SSMrange


Send IGMPv3out of SSMrange


Yes Yes Excl No Send IGMPv3join in SSMrange




Yes Yes Excl No Send IGMPv3join out ofSSM range


Send IGMPv3join out ofSSM range


Yes Yes Excl Yes Send IGMPv3join in SSMrange




Yes Yes Excl Yes Send IGMPv3join out SSMrange


Send IGMPv3join out SSMrange


Yes No Incl Yes Send IGMPv3join


Send IGMPv3join


Yes No Excl No Send IGMPv3join


Send IGMPv3join


Yes No Excl Yes Send IGMPv3join


Send IGMPv3join


The following table describes PIM-SSM behavior while sending MLDV2 joins in the SSM range andoutside the SSM range for IPv6:


Multicast 24

Table 4: Using PIM-SSM While Sending MLDV2 Joins (IPv6)ExtremeXOS15.4

ExtremeXOS15.5

SSMEnabled


No Yes Incl Yes Send MLDv2join in SSMrange

-the group islearned - no(*;G) iscreated

Send MLDv2join in SSMrange


No Yes Incl Yes Send MLDv2out of SSMrange

-the group islearned - no(*;G) iscreated -(S;G) iscreated

Send MLDv2out of SSMrange


No Yes Excl No Send MLDv2join in SSMrange




No Yes Excl No Send MLDv2join out ofSSM range


Send MLDv2join out ofSSM range


No Yes Excl Yes Send MLDv2join in SSMrange




No Yes Excl Yes Send MLDv2join out SSMrange


Send MLDv2join out SSMrange


No No Incl Yes Send MLDv2join

-the group islearned -(S;G) iscreated

Send MLDv2join


No No Excl No Send MLDv2join


Send MLDv2join


No No Excl Yes Send MLDv2join


Send MLDv2join


Yes Yes Incl Yes Send MLDv2join in SSMrange




Yes Yes Incl Yes Send MLDv2out of SSMrange

-the group islearned - no(*;G) iscreated -(S;G) iscreated

Send MLDv2out of SSMrange



Multicast 25

Table 4: Using PIM-SSM While Sending MLDV2 Joins (IPv6) (continued)ExtremeXOS15.4

ExtremeXOS15.5

SSMEnabled


Yes Yes Excl No Send MLDv2join in SSMrange




Yes Yes Excl No Send MLDv2join out ofSSM range


Send MLDv2join out ofSSM range


Yes Yes Excl Yes Send MLDv2join in SSMrange




Yes Yes Excl Yes Send MLDv2join out SSMrange


Send MLDv2join out SSMrange


Yes No Incl Yes Send MLDv2join


Send MLDv2join


Yes No Excl No Send MLDv2join


Send MLDv2join


Yes No Excl Yes Send MLDv2join


Send MLDv2join


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 andPIM-SM can coexist in a PIM network; only the last hop router need to be configured for PIM-SSM ifboth source and receivers are present all the time. However, to avoid any JOIN delay, it isrecommended 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 messagesare ignored, and any IGMPv3 exclude messages are ignored. These messages are ignored for all routerinterfaces, even those not configured for PIM-SSM. By default there is no PIM-SSM range specified onthe router. If you choose the default keyword in the CLI when specifying the PIM-SSM range, youconfigure the range 232.0.0.0/8. You can also choose to specify a different range for PIM-SSM by usinga policy file.

To configure the PIM-SSM address range, use the following command:

configure pim ssm range [default | policy policy-name]

PIM SnoopingPIM snooping provides a solution for handling multicast traffic on a shared media network moreefficiently. In networks where routers are connected to a L2 switch, multicast traffic is essentiallytreated 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. Switchports are flooded with multicast packets. PIM snooping addresses this flooding behavior by efficientlyreplicating multicast traffic only onto ports which routers advertise the PIM join requests (see thefollowing figure).


Multicast 27

Figure 3: Multicast With PIM Snooping

PIM snooping does not require PIM to be enabled. However, IGMP snooping must be disabled onVLANs 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}

NotePIM snooping can be enabled only between PIM SM enabled switches. It should not enabledbetween PIM DM enabled switches.

PIM Register PolicyThis feature allows you to filter register messages based on the policy file configured at the First HopRouter (FHR) and Rendezvous Point (RP) in PIM-SM domain. You can use the register policy to filterout specific PIM register messages that have encapsulated specific (S,G) packets. This feature allowsyou to detect and deny malicious multicast packets from flowing into a multicast shared tree, andcausing a potential service blackout. The PIM Register Policy feature is supported in both the PIM IPV4and PIM IPV6 mode .

Filtering at FHR

• FHR receives the source multicast packet and sends a register message towards the RP. Before itsends the register message to the RP, the FHR checks the configured register filter policy. If the


Multicast 28

(S,G) is denied by the policy, the register will not send a message to the RP. The FHR adds the L3entries 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 deniedby the filter then the NULL register is not sent to the RP.

• If the cache’s Group is in the SSM range, or is received in the PIM dense circuit, then this filtering isnot 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 isremoved. 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 deniedby the registering filter policy, the register message is discarded. Additionally, no (S,G) cache iscreated 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 PriorityThe DR_Priority option allows a network administrator to give preference to a particular router in theDR election process by giving it a numerically larger DR Priority. The DR_Priority option is included inevery Hello message, even if no DR Priority is explicitly configured on that interface. This is necessarybecause priority-based DR election is only enabled when all neighbors on an interface advertise thatthey 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. Arouter's idea of the current DR on an interface can change when a PIM Hello message is received, whena neighbor times out, or when a router's own DR Priority changes. If the router becomes the DR orceases 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) willnot considered for the all the neighbors in the circuit and the primary IP address will be consideredfor 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 viahash 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 hashingaccording 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 hashalgorithm based on the selected criteria to pick up the path to use and will result in load-sharing thetraffic when there are many multicast streams that utilize approximately the same amount ofbandwidth.

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 state’sgroup address. There is no randomization applied when calculating the hash value. The same hashvalue 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 givensource, 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 thestate’s group address, the same hash will be chosen for both (*, G) and (S, G) states as the same groupaddress 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 twoequal cost paths ("left" and "right") available at the last hop router and at each of the intermediaterouters for a given group, each of these routers pick the same hash and the traffic flows can getskewed (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 sourceand group addresses. For an (S, G) state, the address considered for hashing is the source address ofthe state. For a (*, G) state, the address considered for hashing is the address of the RP that isassociated with the state’s group address. There is no randomization applied when calculating the hashvalue. The same hash value is generated on all the EXOS routers for a given source-group address. Ifthere are two equal cost paths ("left" and "right") available at the last hop router and at each of theintermediate routers for a given source-group, each of these routers pick the same hash and the trafficflows 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 interfacefor each (*, G) or (S,G) state is selected among the equal cost paths based on the hash derived from thesource, group and next hop addresses. The hash value derived after introducing the next hop address isstill predictable as there is no randomization applied when calculating the hash value. However, sincethe next hop address used at each of the routers vary, the hash value generated on each of the EXOSrouters is different. As the hash value is different on each of the routers, the problem of traffic pathskew 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 pathbecomes available), all the (*, G) and (S, G) states change based on the available unicast routeinformation 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. Thehash function based on Source-Group-Next Hop avoids skewing of traffic flows because it introducesthe actual next-hop IP address of PIM neighbors into the calculation resulting in different hash valuebeing computed for each router. The Source-Group-Next Hop based hash function doesn’t take thetotal number of available paths into consideration and so it increases stability of the paths chosenduring path failures. During path failures, the multicast states that were using the failed path wouldneed to reconverge onto the remaining paths. All other states using the unaffected paths are notaffected.

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 inthe multicast routing table.

• Load splitting is only effective when the equal cost paths are upstream PIM neighbors on differentinterfaces. When the equal cost paths are PIM neighbors on the same shared VLAN, PIM assertmechanism chooses one path to avoid traffic duplication. The path chosen by PIM assert mechanismoverrides 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 PIMimplementation:

• 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. Thereceiving router must process these addresses and must associate the same with the neighbor thatsent the message.

• Tunnel interface - This is similar to a VLAN interface. APIs are now added to get callbacks fromVLAN 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 thesource interface of the router originating the message. These addresses are associated with the


Multicast 31

neighbor, and are used to compute the neighbor’s primary address. The function NBR uses informationgathered through PIM Hello messages to map the IP address A of a directly connected PIM neighbor oninterface I to the primary IP address of the same router. The primary IP address of a neighbor is theaddress 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 thedomains communicate over the IPv4 network by tunneling the IPv6 packets inside IPv4 headers. Toenable 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. Newkeywords are added to support IPv6, and show command output is modified to display IPv6 relatedinformation. For specific configuration details, refer to IP Multicast Commands.

IGMP OverviewIGMP is a protocol used by an IP host to register its IP multicast group membership with a router. Ahost that intends to receive multicast packets destined for a particular multicast address registers as amember of that multicast address group. Periodically, the router queries the multicast group to see ifthe group is still in use. If the group is still active, a single IP host responds to the query, and groupregistration 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 beenabled 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 therouter-alert option is set in received IGMP packets.

By default, the ExtremeXOS software receives and processes all IGMP packets, regardless of the settingof the router-alert option within a packet. When the switch will be used with third-party switches thatexpect 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) willalways 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 asystem 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 beinteroperable with IGMPv1 and IGMPv2.

NoteThe ExtremeXOS software supports IGMPv3 source include mode filtering, but it does notsupport IGMPv3 specific source exclude mode filtering.

NoteIt 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 cannotmatch ICMP/IGMP types on egress pipeline.

IGMP SnoopingIGMP snooping is a Layer 2 function of the switch; it does not require multicast routing to be enabled. InIGMP snooping, the Layer 2 switch keeps track of IGMP reports and only forwards multicast traffic tothat part of the local network that requires it. IGMP snooping optimizes the use of network bandwidthand prevents multicast traffic from being flooded to parts of the local network that do not need it. Theswitch 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 isdisabled on a VLAN or VMAN, all IGMP and IP multicast traffic floods within the VLAN or VMAN. IGMPsnooping 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}

NoteIGMP snooping is not supported on SVLANs on any platform.

The IGMP snooping proxy feature represented by "with-proxy" in the above commands is enabled bydefault. This feature optimizes the forwarding of IGMPv1 and IGMPv2 reports. The following is true foreach 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 ifproxy is enabled (even if it is a non-querier). The switch removes the port from the group after leavetimeout (The timeout value is configurable, with a default value of 1000 ms., and a range from 0 to175000 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 forwardedupstream.

NoteIGMP snooping proxy does not apply to IGMPv3 reports.

IGMP snooping is implemented primarily through ACLs, which are processed on the interfaces. Thesespecial purpose ACLs are called IGMP snooping hardware filters. On Summit family switches andBlackDiamond 8800 series switches, the software allows you to choose between two types of IGMPsnooping 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. Thetwo primary hardware resources to consider when selecting the IGMP snooping hardware filters are theLayer 3 multicast forwarding table, and the interface ACLs. The size of both of these hardwareresources is determined by the switch model. In general, the per-port filters consume more resourcesfrom the multicast table and less resources from the ACL table. The per-VLAN filters consume lessspace 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 upthe multicast table and place an extra load on the CPU. To avoid this, configure the switch to use theper-VLAN filters.

NoteThe impact of the per-VLAN filters on the ACL table increases with the number of VLANsconfigured on the switch. If you have a large number of configured VLANs, we suggest thatyou use the per-port filters.

IGMP Snooping FiltersIGMP snooping filters allow you to configure a policy file on a port to allow or deny IGMP report andleave packets coming into the port. (For details on creating policy files, see Policy Manager.) The IGMPsnooping filter feature is supported by IGMPv2 and IGMPv3.

NoteDo not confuse IGMP snooping filters with IGMP snooping hardware filters explained inprevious section. IGMP snooping filters are software filters, and the action is applied at thesoftware level by the ExtremeXOS multicast manager.

For the policies used as IGMP snooping filters, all the entries should be IP address type entries, and theIP address of each entry must be in the class-D multicast address space but should not be in themulticast 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 leavepackets 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 aset 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 IGMPTo 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 beforwarded to a port where a multicast-enabled host is not available (for example, when you testmulticast configurations).

Static IGMP emulates a host or router attached to a switch port, so that multicast traffic is forwarded tothat port, and the switch sends a proxy join for all the statically configured IGMP groups when an IGMPquery is received. You can emulate a host to forward a particular multicast group to a port; and youmay emulate a router to forward all multicast groups to a port. Static IGMP is only available withIGMPv2.

• 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 LoopbackPrior 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 staticand/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. Sometimesthere 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 allowsyou to configure groups on a VLAN without specifying a port, so the traffic is pulled from upstream butnot forwarded to any port.

The loopback (Lpbk) port is the logical port on a VLAN in the application context. If you configure agroup on a VLAN but do not specify the port, the switch forms an IGMPv2 join and assumes it to bereceived on the Lpbk port. A dynamic group ages out after the membership timeout if there are noother receivers. Membership joins refresh the dynamic group. The static group remains until it isremoved 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. Toplace 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 LeaveWhen the fast leave feature is enabled and the last host leaves a multicast group, the routerimmediately removes the port from the multicast group. The router does not query the port for othermembers 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 MappingThe 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 usedfor a group/group range for which SSM functionality has to be applied. You also have the option toconfigure 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 cansend source specific joins. When the host leaves or when the membership times out, PIM is informed sothat 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 configurationfor 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 50sources 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 thatrange should include all groups to which the clients want access. If IGMPv1 and IGMPv2 clients requestgroup addresses outside the PIM-SSM range, those addresses are ignored by PIM-SSM and forwardedto PIM as (*, G) requests.

• To enable IGMP-SSM mapping, first configure a PIM-SSM range, and then enable IGMP-SSMmapping 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 mappingsfor 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 multicasttraffic after an EAPS topology change. For more information, see the descriptions for the followingcommands:

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.

NoteUsing the configure eaps multicast send-query command applies to both IGMP andMLD. This also replaces the configure eaps multicast send-igmp-query command.

Configuring IP Multicast Routing

Enabling Multicast ForwardingTo enable IP multicast forwarding:

1 Configure the system for IP unicast routing.

2 Enable multicast forwarding on the interface.

enable ipmcforwarding {vlan name}

Configuring PIMTo configure PIM multicast routing, enable multicast forwarding as described in Enabling MulticastForwarding 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 followingcommands:

configure pim {ipv4 | ipv6} state-refresh {vlan} [vlan_name | all] [on | off]

configure pim state-refresh timer origination-interval interval

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 interfacesusing 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

NoteMulticast static routes are supported in the IPv4 address family, but not the IPv6 addressfamily.

Static routes are used to reach networks not advertised by routers, and are manually entered into therouting table.

• You can use either of two commands to create multicast static routes. The recommended commandis 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 ExtremeXOSsoftware 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 protocolinformation 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 theprotocol route is available. Otherwise, the route is Down. In the example above, the multicast staticroute 58.1.10.0/24 is shown as UP only when the OSPF route is available to reach the network58.1.10.0/24.

Static routes are stored in the switch configuration and can be viewed with the show configurationcommand. Static multicast routes that do not include protocol information are displayed using theconfigure iproute command format, even if they were created using the configure ipmroutecommand. Static routes that are created with a protocol field are displayed using the configureipmroute command format.

Disabling IP Multicast CompressionThe IP multicast compression feature is available only on Summit family switches and BlackDiamond8000 series modules, and is enabled by default. You should only disable this feature if you suspect thatswitch 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 ConfigurationConsider 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 MLAGswitches.

• RP and BSR can be configured on same device along with MLAG config but we recommend to keepRP node away from MLAG peers. One MLAG peer will be Designated Router(DR) and another onewill be elected as NON-DR for MLAG vlan. DR node will send *,G and try to pull the traffic from RPand Non-DR won’t be pull the traffic until DR is alive. If you config RP on Non-DR node then bothMLAG peers will pull the traffic which will trigger the assert to avoid the traffic duplication. It is notrecommended 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 thethis 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 fromExtremeXOS15.3.2 release onwards).

• It is recommended that for PIM-SM deployments that the RP is configured on loopback VLANsinstead of regular VLANs. This ensures continuous connectivity to the RP needing active portspresent 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

NoteThe 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 theExtremeXOS 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.0configure vlan HQ_10_0_2 ipaddress 10.0.2.2 255.255.255.0configure ospf add vlan all area 0.0.0.0enable ipforwardingenable ospfenable ipmcforwardingconfigure pim add vlan all denseenable pimconfigure 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

NoteThe 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 theExtremeXOS User Guide for more information about configuring OSPF.

The router labeled ABR1 has the following configuration:

configure vlan HQ_10_0_2 ipaddress 10.0.2.1 255.255.255.0configure vlan HQ_10_0_3 ipaddress 10.0.3.1 255.255.255.0configure vlan LA_161_48_2 ipaddress 161.48.2.2 255.255.255.0configure vlan CHI_160_26_26 ipaddress 160.26.26.1 255.255.255.0configure ospf add vlan all area 0.0.0.0enable ipforwardingenable ipmcforwardingconfigure pim add vlan all sparsetftp TFTP_SERV -g -r rp_list.polconfigure pim crp HQ_10_0_3 rp_list 30configure 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 ofgroup addresses are advertised as candidate RPs. Each router then elects the common RP for a groupaddress 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 and232.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. Hoststhat use IGMPv3 on VLAN v13 can request and receive source specific multicast streams for addressesin the PIM-SSM range.

create vlan v12create vlan v13configure v12 add port 1configure v13 add port 2configure v12 ipaddress 12.1.1.1/24configure v13 ipaddress 11.1.1.1/24configure pim add vlan all sparseenable ipforwardingenable ipmcforwardingenable igmp IGMPv3configure pim ssm range defaultenable pim ssm vlan v13enable 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 S1through the VLAN comm_vlan. Switches S3, S4, and S5 are multicast capable switches, and switch S2 isa 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 floodingbecause it floods the multicast traffic to all router ports.

The network design calls for most multicast traffic to egress switch S5. PIM snooping helps byintercepting the PIM joins received from the downstream routers and forwarding multicast traffic onlyto 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_vlanconfigure vlan comm_vlan add port 1,2,3,4disable igmp snoopingdisable igmp_snooping comm_vlanenable pim snoopingenable pim snooping comm_vlan

Switch S3 Configuration Commands

The following is an example configuration for switch S3, which also serves as an RP:

create vlan comm_vlanconfigure vlan comm_vlan add port 1configure comm_vlan ipa 10.172.168.4/24enable ipforwarding comm_vlanenable ipmcforwarding comm._vlanconfigure pim add vlan comm_vlan sparseconfigure ospf add vlan comm._vlan area 0.0.0.0

create vlan sender_vlanconfigure vlan sender_vlan add port 2configure sender_vlan ipa 10.172.169.4/24enable ipforwarding comm_vlan


Multicast 44

enable ipmcforwarding comm._vlanconfigure pim add vlan comm._vlan sparseconfigure ospf add vlan comm_vlan area 0.0.0.0

enable pimenable 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 formulticast traffic:


create vlan receiver_vlanconfigure vlan sender_vlan add port 1configure sender_vlan ipa 10.172.170.4/24enable ipforwarding comm_vlanenable ipmcforwarding comm._vlanconfigure pim add vlan comm._vlan sparseconfigure ospf add vlan comm_vlan area 0.0.0.0




The following is an example configuration for switch S4, which is neither an LHR nor a RP:





Multicast 45


The following is an example configuration for switch S2, which is not enabled for PIM:

create vlan comm_vlanconfigure vlan comm_vlan add port 1configure comm_vlan ipa 10.172.168.6/24enable ipforwarding comm_vlanenable ipmcforwarding comm._vlanconfigure ospf add vlan comm._vlan area 0.0.0.0

enable ospf

PIM Snooping Example Configuration Displays

After the example configuration is complete, multicast receivers connect to the network through switchS5 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_vlanPIM Snooping ENABLEDVlan comm_vlan(3971) Snooping ENABLEDSource Group RP UpPort DownPort Age HoldTime* 225.1.1.1 10.172.169.4 1 2 15 210Neighbor IP DR Port Age Hold Time10.1272.168.4 YES 1 2 10510.1272.168.2 NO 2 2 10510.1272.168.3 NO 3 2 105

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 byentering the following command at switch S1:

# show pim snooping vlan comm_vlanPIM Snooping ENABLEDVlan comm_vlan(3971) Snooping ENABLEDSource Group RP UpPort DownPort Age HoldTime* 225.1.1.1 10.172.169.4 1 2 15 21010.172.169.10 225.1.1.1 10.172.169.4 1 2 15 210Neighbor IP DR Port Age Hold Time10.1272.168.4 YES 1 2 10510.1272.168.2 NO 2 2 10510.1272.168.3 NO 3 2 105

Multicast traffic is forwarded only to those ports that have received (*, G) or (S, G) joins and designatedrouter (DR) ports.


Multicast 46

Multicast VLAN RegistrationMulticast VLAN Registration (MVR) is designed to support distributing multicast streams for IPTV tosubscribers over a Layer 2 network. In a standard Layer 2 network, a multicast stream received on aVLAN is not forwarded to another VLAN. The streams are confined to the Layer 2 broadcast domain. Inan IGMP snooping environment, streams are forwarded only to interested hosts on a VLAN. For inter-VLAN 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 anotherVLAN, eliminating the need for a Layer 3 routing protocol. It simplifies the multicast stream distributionand is a better solution for IPTV-like services. With MVR, a multicast stream is forwarded to all VLANscontaining 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 notreceive the multicast traffic because no IP multicast routing protocol forwards the stream to VLANVlan2. On the right side of the figure, H2 does receive the multicast stream. Because Vlan1 wasconfigured 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 thefollowing command: configure mvr add vlan vlan-name

Typically, IGMP snooping is enabled, so only hosts that have requested a stream can see the multicasttraffic. For example, another host on VLAN2 cannot receive the traffic unless it has sent an IGMPrequest to be included in the group.

Notice that only VLAN1 is MVR enabled. Configure MVR only on the ingress VLAN. To enable MVR onthe switch, use the following command: enable mvr

NoteMVR is not supported on the Summit X430.

Basic MVR DeploymentBecause MVR is primarily targeted for IPTV and similar applications, a basic deployment for thatapplication is shown in the following figure. In the figure, an IPTV server is connected through a routerto 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 andsome kind of redundant protection to provide high availability. For example, McastVlan forms a ringthrough switches Switch1 through Switch4. The link from Switch2 to Switch4 is shown as blocked, as itwould 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 portsconnecting 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 samestream (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 amulticast 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 leaksthe 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 defaultIGMP and IGMP snooping are enabled on Extreme Networks’ switches).

• For all the multicast streams (IPTV channels), configure static IGMP snooping membership on therouter on McastVlan.

• Enable MVR on the switches in the network.

NoteMVR works best with IGMPv1 and IGMPv2. We recommend that you do not use MVR withIGMPv3.

The strategy above conserves bandwidth in the core and does not require running PIM on thesubscriber switches.


Multicast 48

In this topology, a host (for example, a cable box or desktop PC) joins a channel through an IGMP joinmessage. Switch1 snoops this message and adds the virtual port to the corresponding cache's egresslist. This is possible because an MVR enabled VLAN can leak traffic to any other VLAN. When the userswitches to another channel, the host sends an IGMP leave for the old channel and a join for the newchannel. The corresponding virtual port is removed from the cache for the old channel and is added tothe cache for the new channel.

As discussed in Static and Dynamic MVR on page 49, McastVlan also proxies IGMP joins learned onother VLANs to the router. On an MVR network it is not mandatory to have a router to serve themulticast stream. All that is required is to have a designated IGMP querier on McastVlan. The IPTVserver 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 leastone 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. Youhave the option to use the static router configuration in each of the switches in the core. But this willcause all the channels to be available in the core, which may not be desired. For example, on anExtreme 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 shouldbe flooded. If a multicast stream for a group in the static MVR range is received on an MVR enabledVLAN, it is always flooded on the MVR VLAN. This allows the neighbor switch in the ring to receive allthe static MVR streams.

Dynamic MVR

In contrast, since a video content provider would like to provide a variety of on-demand and otherpremium channels, there are often many lower demand (fewer viewers) premium channels that cannotall be made available simultaneously at the core network. These should be streamed from the routeronly if requested by a host.

IGMP is the standard method used by a host to request a stream. However, IGMP packets areconstrained to a VLAN. Thus, subscribers' IGMP join requests on the VLAN cannot be forwarded ontoother VLANS. You can use a dynamic MVR configuration, and choose the groups for which the IGMPjoin requests should be proxied over the MVR VLAN. Thus, in Figure 8: Basic MVR Deployment on page48, McastVlan sends join and leave messages on behalf of Vlan2, Vlan3, and Vlan4. The router receivesthe messages on McastVlan and streams corresponding channels onto the core network. This provideson-demand service, and an administrator does not need to configure static IGMP on the router for eachof 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 theMVR 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 aredynamic. If you want all the groups to be dynamic, specify a policy file for the static groupcommand that denies all multicast addresses.

MVR Configuration Example

The following example configuration is a two DUT scenario, in L2 mode , with no routing protocol orPIM 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 thisport.

Configure MVR on vlan v1 on DUT-2

* X460-48t.157 # show config "mcmgr" ## Module mcmgr configuration.#enable mvr vr VR-Defaultconfigure mvr add vlan v1configure mvr vlan v1 mvr-address noneconfigure 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 willreceive 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 thetraffic.

If you configure static policy (by default – permit), traffic for that group range will always be availablein 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 thejoin 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 whichtraffic 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 thegroup 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 designatedmulticast VLAN. If the backbone Layer 2 port is tagged with multiple VLANs, as shown in the followingfigure, 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. WithMVR, multicast traffic should be confined to McastVlan, and should not be forwarded to vc1 and vc2. Itshould be noted that MVR is configured only on the ingress VLAN (McastVlan). MVR is not configuredon any other VLANs.

In the same way as the IGMP snooping forwarding rules, the multicast stream is forwarded ontomember ports and router ports on the VLAN. For a stream received on MVR enabled ports, this rule isextended to extend membership and router ports to all other VLANs. This rule works well on thetopology in the following figure. However, in a tagged core topology, this rule forwards traffic ontoVLANs, such as vc1 and vc2, on ports PC1 and PC2. This results in multiple copies of same stream on thecore 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. MVRtraffic is not forwarded to another VLAN unless a host is detected on the port. On the ingress MVRVLAN, packets are not duplicated to ports belonging to MVR VLANs. This is to prevent duplicatemulticast traffic streams on ingress ports. Streams belonging to static MVR groups are alwaysforwarded on MVR VLANs so that any host can join such channels immediately. However, dynamicgroups are streamed from the server only if some host is interested in them. A command is provided toreceive traffic on a port which is excluded by MVR. However, regular IGMP rules still apply to theseports, 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 onVLAN pc2 in the following figure. These rules also allow that, in most topologies, MVR can be deployedwith minimal configuration. However, unlike EAPS and STP, MVR is not intended to be a Layer 2protocol to solve packet looping problems. Since multicast packets leak across VLANs, one canmisconfigure and end up with a multicast storm. MVR does not attempt to solve such problems.

NoteIf a port is blocked by Layer 2 protocols, that port is removed from the egress list of thecache. 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 canmanually receive the MVR multicast streams by using the following command:

configure mvr vlan vlan_name add receiver port port-list

Inter-Multicast VLAN ForwardingIn Basic MVR Deployment on page 47, only simple topologies are considered, in which subscribers ondifferent VLANs access a multicast VLAN. There are topologies where streams need to be forwardedonto another multicast VLAN, as shown in the following figure. In this figure, a Multicast ServiceProvider (MSP) multicast VLAN is attached to ports 1:1-2 on both switches, SW1 and SW2. On thecustomer 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 eitherswitch SW1 or SW2. However, as described in MVR Forwarding on page 51, packets are not forwardedto router ports (ports 1:4 and 1:5 can be router ports if SW2 is an IGMP querier). To get around this, MVRneeds to be configured on CustVlan either on SW1 or SW2. Since the forwarding rules apply only tonon-MVR VLANs, traffic from one MVR VLAN is leaked into the router ports of another VLAN, if MVR isenabled on that.

In the topology above, the MSP multicast VLAN is carried on two switches that also carry the customermulticast VLAN. When multiple switches carry both multicast VLANs, it is imperative that MVR isconfigured on only one switch. Only that switch should be used as the transit point for multicaststreams from one multicast ring into another. Otherwise, duplicate packets are forwarded. Also on thenon-MVR switches, the ring ports should be configured as static router ports, so that ring ports areexcluded from forwarding packets onto the customer ring. There is no mechanism to elect a designatedMVR forwarder, so it must be configured correctly.

MVR ConfigurationsMVR enables Layer 2 network installations to deliver bandwidth intensive multicast streams. It isprimarily aimed at delivering IPTV over Layer 2 networks, but it is valuable in many existing EAPS orSTP 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 topresent some ideas on how to deploy MVR over existing networks, as well as to design new networksthat support MVR.

MVR with EAPS

Since MVR is designed with a Layer 2 ring topology in mind, it is strongly recommended that it shouldbe deployed with EAPS. The MVR plus EAPS combination provides a superior solution for any tripleplay network, where the service provider intends to provide data, voice, and video services. EAPS is aproven solution for providing sub-second SONET-like protection to Layer 2 rings. For more detail onEAPS refer to EAPS.

Consider a typical EAPS topology in the following figure, where 3 VLANs on the core ring serve variousclients 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 isanother protected VLAN. A router serving the multicast feed would typically run PIM on mcastvlan, tosupport 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 mcastvlanconfigure mcastvlan add port 1:1create vlan serverconfigure server add port 1:2configure mcastvlan ipaddress 10.1.1.1/24configure server ipaddress 11.1.1.1/24configure igmp snooping mcastvlan port 1:1 add static group 239.1.1.1enable ipforwardingenable ipmcforwardingconfigure igmp snooping leave-timeout 2000configure pim add vlan allenable pim

Switch1:

create vlan mcastvlancreate vlan v1create vlan v2create vlan vlan2configure vlan vlan2 add port 1:3configure vlan vlan2 ipaddress 10.20.1.1/24configure mcastvlan tag 20configure mcastvlan add port 1:1,1:2 tagconfigure mvr add vlan mcastvlanconfigure vlan v1 tag 30configure v1 add port 1:1,1:2 tagconfigure vlan v2 tag 40


Multicast 54

configure v2 add port 1:1,1:2 tag

create eaps e1configure eaps e1 mode transitconfigure eaps e1 add control vlan v1configure eaps e1 add protect vlan mcastvlanconfigure eaps e1 add protect vlan v2configure eaps port primary port 1:1configure eaps port secondary port 1:2enable eapsenable mvr

Switch3:

create vlan McastVlancreate vlan v1create vlan v2configure mcastvlan tag 20configure mcastvlan add port 1:2,1:3 tagconfigure mcastvlan add port 1:1configure mvr add vlan mcastvlanconfigure vlan v1 tag 30configure v1 add port 1:2,1:3 tagconfigure vlan v2 tag 40configure v2 add port 1:2,1:3 tag

create eaps e1configure eaps e1 mode masterconfigure eaps e1 add control vlan v1configure eaps e1 add protect vlan mcastvlanconfigure eaps e1 add protect vlan v2configure eaps port primary port 1:3configure eaps port secondary port 1:2enable eapsenable mvr

NoteIn this example, Switch3 is the EAPS master, but any of the other switches in the ring couldhave 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 2topologies, additional configuration steps may be needed to make sure that multicast feeds reach allnetwork segments. Extra configuration is required because all ports in the VLAN are part of an STPdomain, so that solely by examining the configuration it is not clear whether a port is part of bigger ringor is just serving a few hosts. In EAPS this problem is solved by distinguishing between configuredprimary or secondary ports from other VLAN ports. Consider a simplified Layer 2 STP network asshown 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 forwardedon V1 blindly. Forwarding rules (described in MVR Forwarding on page 51), dictate that multicast trafficis not forwarded on STP enabled ports. This is to make sure that multiple copies of multicast packetsare not forwarded on the ring. However, since other STP enabled ports on V1 (1:3,1:4) are not part of thering multicast stream, they need to be configured so that they get the packets. To configure the portsto receive packets, use the following command (mentioned in MVR Forwarding on page 51):

configure mvr vlan vlan-name add receiver port port-list

NoteIf the Layer 2 cloud is connected back to ring ports, traffic may end up leaking into VLAN V1in 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 v1configure v1 tag 200configure v1 add port 1:1, 1:2 tagconfigure v1 add port 1:3, 1:4create vlan mvlanconfigure mvlan add port 1:1, 1:2configure mvr add vlan mvlancreate stpd stp1configure stp1 add vlan v1 port allenable stpd stp1 port allconfigure mvr vlan v1 add receiver port 1:3,1:4enable 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 isto provide VLAN aggregation for all customer traffic in the VMAN ring. Each customer is given its ownVLAN, 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 bedistributed over a separate VLAN in the metro core. These packets are not subjected to VMANtunneling. 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, sincea separate multicast VLAN on the metro ring is used for multicasting. However, it provides interestingcapabilities to MSPs for their video offerings. Different service bundles can be offered on separateVLANs. 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 multicastpacket entering on MVlan is forwarded on MVlan to the next switch. These multicast packets are nottunneled.

With MVR, switches on the VMAN do not have to run any routing protocol. If MVR is enabled on themulticast VLAN, MVlan, traffic is pulled from the IPTV server. Such multicast packets egressing from theCE port are always untagged. The downstream DSLAM distributes untagged multicast packets to therespective subscriber VLANs.

Figure 13: MVR in a VMAN Environment

The following is a typical configuration for Switch 1 in the above figure:

create vman vman2configure vman vman2 tag 300configure vman vman2 add port 2:2-2:3 untaggedconfigure vman vman2 add port 1:1,1:2 taggedenable port 2:*enable port 1:*create vlan mvlanconfigure vlan mvlan tag 200configure vlan mvlan add port 1:1,1:2 tagconfigure mvr add vlan mvlanenable 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 inthe 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 themulticast 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 ToolThe multicast trace tool is the multicast equivalent of unicast trace route mechanism and is an effectivetool 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 runfrom 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. Whenthe multicast tree is established and traffic is flowing, this tool traces the actual traffic flow. If there is notraffic while executing the command, this tool displays the potential path for the group and sourcebeing traced.

You can direct a multicast trace to any network destination, which can be a multicast source ordestination, or a node located between a source and destination. After you initiate the trace, a multicasttrace query packet is sent to the last-hop multicast router for the specified destination. The querypacket 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,Gentry 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 appendingresponse data (for the last hop router) into the received query packet, and the last hop router forwardsthe request packet to the router that it believes is the proper previous hop for the given source andgroup.

Each multicast router adds its response data to the end of the request packet, and then forwards themodified unicast request to the previous hop.

The first hop router (the router that determines that packets from the source originate on one of itsdirectly connected networks) changes the packet type to response packet and sends the completedresponse to the query generator. If a router along the multicast route is unable to determine theforwarding state for a multicast group, that router sends a response back to the originator with NOROUTE 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 ToolThe multicast router information tool is an ExtremeXOS command that allows you to requestinformation from a specific multicast router. For more information, see the command description forthe following command:

mrinfo {router_address} {from from_address} {timeout seconds} {multiple-response-

timeout multi_resp_timeout} {vr vrname}


Multicast 59

2 IPv6 Multicast

Multicast Listener Discovery (MLD) OverviewManaging MLD

This chapter introduces IPv6 multicast, which allows a single IPv6 host to send a packet to a group ofIPv6 hosts, and the features and configuration of the Multicast Listener Discovery (MLD) protocol. Formore information on IPv6 multicasting, refer to the following publications:

• RFC 2710—Multicast Listener Discovery (MLD) for IPv6

• RFC 3810—Multicast Listener Discovery Version 2 (MLDv2) for IPv6

Multicast Listener Discovery (MLD) OverviewMulticast Listener Discovery (MLD) is a protocol used by an IPv6 host to register its IP multicast groupmembership with a router. To receive multicast traffic, a host must explicitly join a multicast group bysending an MLD report; then, the traffic is forwarded to that host. Periodically, the router queries themulticast group to see if the group is still in use. If the group is still active, a single IP host responds tothe query, and group registration is maintained.

MLD is the IPv6 equivalent to IGMP, and MLDv1 is equivalent to IGMPv2. The ExtremeXOS softwaresupports both MLDv1 and MLDv2 protocol.

NoteThis release does not support MVR, PVLAN, VLAN Aggregation, and MulticastTroubleshooting tools for MLD/IPv6.

Managing MLD

Enabling and Disabling MLD on a VLANMLD 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.

• 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.

Multicast 60

MLD SnoopingSimilar to IGMP snooping, MLD snooping is a Layer 2 function of the switch; it does not requiremulticast routing to be enabled. In MLD snooping, the Layer 2 switch keeps track of MLD reports andonly forwards multicast traffic to the part of the local network that requires it. MLD snooping optimizesthe use of network bandwidth and prevents multicast traffic from being flooded to parts of the localnetwork 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 querymessages.

• 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 enabledswitch. 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 (Addressesallocated by IANA as per RFC 3307) are always flooded to all ports of the VLAN by hardware and acopy of the packet is provided to slow path. There are no cache entries in software or hardware forthese 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 queryinterval + Maximum response time), if there are no members for this group.

Otherwise, the traffic is forwarded based on the snooping database. Multicast cache entries forthese 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 beforwarded based on the snooping database.

Cache entries for these multicast addresses will be installed in hardware. Unregistered packets aredropped.

• 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 addresswill 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 arecontrolled by the PIMv6 protocol.

PIMv6 provides a list of egress VLANs for which packets need to be forwarded. The snoopingdatabase 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 ingressVLAN.

In both cases, cache entry is installed in the hardware, and traffic is fast path forwarded.

IPv6 Multicast

Multicast 61

• The MLD snooping proxy feature is enabled automatically when MLD snooping is enabled. Thisfeature 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 thatport if proxy is enabled (even if it is a non-querier). The switch removes the port from the groupafter the leave timeout (a configuable value from 0 - 175000ms with a default of 1000ms). If allthe ports are removed from the group, the group is deleted and the MLD leave is forwardedupstream. If MLD snooping proxy is disabled, then all the MLD reports are forwarded upstream.

NoteMLD snooping proxy does not apply to MLDv2 reports.

• MLD snooping is implemented primarily through ACLs, which are processed on the interfaces. Thesespecial purpose ACLs are called MLD snooping hardware filters. On Summit family switches andBlackDiamond 8800 series switches, the software allows you to choose between two types of MLDsnooping 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 filtersare the Layer 3 multicast forwarding table, and the interface ACLs. The size of both of thesehardware resources is determined by the switch model. In general, the per-port filters consumemore resources from the multicast table and less resource from the ACL table. The per-VLAN filtersconsume 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 issmaller, 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.

NoteThe impact of the per-VLAN filters on the ACL table increases with the number of VLANsconfigured on the switch. If you have a large number of configured VLANs, we suggestthat 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 andleave packets coming into the port.

(For details on creating policy files, see Policy Manager.) The MLD snooping filter feature is supportedby MLDv1 and MLDv2.

NoteDo not confuse MLD snooping filters with MLD snooping hardware filters explained inprevious section. MLD snooping filters are software filters, and the action is applied atsoftware level by the ExtremeXOS multicast manager.

For the policies used as MLD snooping filters, all the entries should be IPv6 address type entries, andthe IPv6 address of each entry must not be in the range of FF02::/96.

IPv6 Multicast

Multicast 62

Use the following template to create a snooping filter policy file that denies MLD report and leavepackets for the FF03::1/128 and FF05::1/112 multicast groups:

## Add your group addresses between "Start" and "end"# Do not touch the rest of the file!!!!entry mldFilter {if match any {#------------------ Start of group addresses ------------------nlri FF03::1/128;nlri FF05::1/112;#------------------- end of group addresses -------------------} then {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 ofports:

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. Toplace 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 requiremulticast routing to be enabled. MLD snooping keeps track of MLD reports, and only forwardsmulticast traffic to that part of the local network that requires it. MLD snooping is disabled bydefault on all VLANs. If MLD snooping is disabled on a VLAN, all MLD and IPv6 multicast trafficfloods within the VLAN. To enable IGMP snooping, use the command:

enable mld snooping {vlan name}

IPv6 Multicast

Multicast 63

Clearing MLD Group RegistrationTo clear a single group or all groups in a VLAN learned through MLD, use the command:

clear mld group {v6grpipaddress} {{vlan} name}

Configuring Static MLDIn some situations, you might want multicast traffic to be forwarded to a port where a multicast-enabled host is not available (for example, when you test multicast configurations). Static MLDemulates 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 isreceived. You can emulate a host to forward a particular multicast group to a port; and you mayemulate 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 LoopbackPrior 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 alongwith the existing static group feature supports the configuration of static and/or dynamic groups withor 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 youto configure groups on a VLAN without specifying a port, so the traffic is pulled from upstream but notforwarded to any port.

The loopback (Lpbk) port is the logical port on a VLAN in the application context. When you configurea group on a VLAN but do not specify the port, the switch forms an MLDv1 join and assumes it to bereceived on the Lpbk port. A dynamic group ages out after the membership timeout if there are noother receivers. Membership joins refresh the dynamic group. The static group remains until it isremoved from the configuration.

Display MLD Information

• To display MLD configuration and operation information, use the command:

show mld group {{vlan} {name} | {v6grpipaddress}} {MLDv2}

IPv6 Multicast

Multicast 64

• To display the MLD static group information, use the command:

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

MLD SSM MappingThe MLD-SSM Mapping feature allows MLDv1 hosts to participate in SSM functionality, and eliminatesthe 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 nameand 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 sourcespecific joins. When the host leaves, or when the membership times out, PIM is informed so that it canconsider sending prunes.

NoteThe 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 aresult of RPT to SPT switchover in PIM-SM. There is no indication that the cache is created as resultof MLDv1 join, or MLDv2 report.

Limitations

• Only 50 sources (static or dynamic) are allowed for each group address, or group range.

NoteThe DNS server may send only 15 IPv6 source addresses in its response thereby limitingthe 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=1and plen=0. RFC 3306 mandates that the network prefix is zero, which results in the SSM address rangeto be in FF3x::/96 range. Since future documents may allow a non-zero network prefix, this featureallows 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. MCMGRapplies this range for the MLD SSM feature.

IPv6 Multicast

Multicast 65

Handling MLD Reports

The following table captures the enhanced functionality.

Table 5: MLD MappingMLDv1 Join MLD SSM Map Disabled MLD SSM Map Enabled

Group in SSM range but no mapentries

Dropped Dropped

Group in SSM range with mapentries

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 managerwill 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 SSMgroup 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 theSSM map are considered only when a MLDv1 receiver is connected to a port. For the same group, theremay be another port on which only MLDv2 receiver is present. For this port, SSM map sources are notconsidered.

L3 forwarding decision of SSM data traffic is taken by PIM. PIM provides the list of egress VLANs to beincluded, 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 notsent. This feature uses the AAAA record type. For example, if the multicast group is FF30::1234:5678and the configured domain name is ext.foo.bar, then the DNS request is sent for8.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 followingscenarios:

• When a DNS name is configured for a group.

• When the refresh ssm-map command is used.

• When the DNS age timer expires.

IPv6 Multicast

Multicast 66

The DNS response may contain one or more addresses. These addresses are updated to the SSMmapping table against the specific group.

NoteLPM 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, thedynamic sources are flushed and the static sources are added. Static mapped addresses are preferredover DNS resolved addresses.

DNS Timers

The DNS age timer is a decrementing timer to zero and applies to a group/group range. The value ofthis 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 notremoved until the wait TTL time expires.

On receiving the DNS response, the existing DNS resolved addresses which are not in the DNSresponse are removed. Any new addresses in the DNS response are added and the DNS age timer isrefreshed. The L2 SSM data caches are modified for the addresses removed, or added. PIM is notified totake action on L3 SSM caches.

If the DNS response is not received and the DNS age timer expires, the mapping entry is removed (ifthere are no static addresses). The SSM data traffic forwarding is stopped immediately when the groupis removed.

DNS Server

This feature does not check or track DNS servers configured in the switch. You must correctly configureand 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-clientNumber of domain suffixes: 0Number of domain servers: 1Name Server 0: 10.120.89.75 VR-Default

MCMGR uses nettools library to perform DNS lookups. gethostbyname_c is used by specifying thecallback function to be invoked when DNS response is received.

Configuring MLD SSM Mapping

Use the following commands to configure MLD SSM Mapping in ExtremeXOS:

IPv6 Multicast

Multicast 67

• 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}

• Display the status of MLD-SSM mapping feature on a VR, and display the MLD-SSM mappingentries: show mld ssm-map { v6groupnetmask } { {vr} vrname }

• Send out a DNS request for a particular group. On receiving the DNS response, the "DNS Age" in theSSM mapping entry is refreshed: refresh mld ssm-map v6groupnetmask { {vr} vrname}

• Configure the DNS server: configure dns-client add name-server ip_address {vrvr_name}]

• Display the DNS Servers: show dns-client

IPv6 Multicast

Multicast 68

3 MSDP

MSDP OverviewPIM Border ConfigurationMSDP PeersMSDP Mesh-GroupsAnycast RPSA CacheRedundancySNMP MIBs

This chapter introduces MSDP (Multicast Source Discovery Protocol), an interdomain multicast protocolused to connect multiple multicast routing domains that run PIM-SM (Protocol Independent Multicast-Sparse Mode). This chapter discusses the features and configuration for PIM border, MSDP peers, meshgroups, anycast RP, SA cache, redundancy, and SNMP MIBs.

NoteFor more information about MSDP, refer to RFC 3618.

MSDP OverviewMulticast Source Discovery Protocol (MSDP) is an interdomain multicast protocol used to connectmultiple 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 relationshipwith other MSDP speakers through secured TCP connections. When the source sends traffic, the MSDPspeaker learns about the source through its Rendezvous Point (RP). In turn, the RP advertises thesource to its peers through Source Active (SA) messages. The peers receive these advertisements andinform their RPs about the presence of the active source in the other PIM-SM domain, which triggersthe normal PIM operation in the corresponding domains.

For example, as businesses expand and networks grow in size, it might become necessary to connectPIM domains to allow multicast applications to reach other offices across the network. MSDP simplifiesthis process by providing a mechanism to connect those multicast routing domains withoutreconfiguring existing domains. Each PIM domain remains separate and has its own RP. The RP in eachdomain establishes an MSDP peering relationship over a TCP connection either with RPs in otherdomains or with border routers leading to other domains. When an RP learns about a new multicastsource in its own domain (using the normal PIM registration process), it then sends a SA message to allof its MSDP peers, letting them know about the new stream. In this way, the network can receivemulticast traffic from all over the network without having to reconfigure each existing PIM domain.

Multicast 69

Supported PlatformsMSDP is supported on all platforms running a minimum software version of ExtremeXOS 12.0 with theCore license.

Our implementation of MSDP is compliant with RFC 3618 and RFC 3446, and compatible with otherdevices that are compliant with these standards.

LimitationsThe limitations of MSDP are as follows:

• There is no support for MSDP operating with SA cache disabled (transit node). MSDP will alwayscache/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 exactlyconform 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 ConfigurationTo 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 interfaceconfigured 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 PeersMSDP peers exchange messages to advertise active multicast sources. The peer with the higher IPaddress passively listens to a well-known port number and waits for the side with the lower IP addressto establish a Transmission Control Protocol (TCP) connection on port 639. When a PIM-SM RP that isrunning MSDP becomes aware of a new local source, it sends an SA message over the TCP connectionto its MSDP peer. When the SA message is received, a peer-RPF check is performed to make sure thepeer is toward the originating RP. If so, the RPF peer floods the message further. If not, the SA messageis 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}

MSDP

Multicast 70

MSDP Default PeersYou can configure a default peer to accept all SA messages. Configuring a default peer simplifies thepeer-RPF checking of SA messages. If no policy is specified, the current peer is the default RPF peer forall SA messages.

When configuring a default peer, you can also specify an optional policy filter. If the peer-RPF checkfails, and a policy filter is configured, the default peer rule is applied to see if the SA message should beaccepted or rejected.

You can configure multiple default peers with different policies. However, all default peers must eitherbe configured with a default policy or not. A mix of default peers, with a policy and without a policy, isnot 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 AuthenticationMSDP 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 MSDPpeer 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. AllMSDP messages that fail TCP RSA Data Security, Inc. MD5 Message-Digest Algorithm authenticationare dropped.

• Configure TCP RSA Data Security, Inc. MD5 Message-Digest Algorithm authentication on an MSDPpeer 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 FiltersYou can configure a policy filter to control the flow of SA messages going to or coming from an MSDPpeer. For example, policy filters can help mitigate state explosion during denial of service (DoS) orother attacks by limiting what is propagated to other domains using MSDP.

MSDP

Multicast 71

• 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 ProcessingYou can configure the router to accept or reject SA request messages from a specified MSDP peer or allpeers. If an SA request filter is specified, only SA request messages from those groups permitted areaccepted. All others are ignored.

• Configure the router to accept SA request messages from a specified MSDP peer or all peers usingthe command:

enable msdp [{peer} remoteaddr | peer all] process-sa-request {sa-request-

filter filter-name } {vr vr_name}

• Configure the router to reject SA request messages from a specified MSDP peer or all peers usingthe command:

disable msdp [{peer} remoteaddr | peer all] process-sa-request {vr vrname}

• Display configuration and run-time parameters about MSDP peers using the command:


MSDP Mesh-GroupsMSDP can operate in a mesh-group topology. A mesh-group limits the flooding of SA messages toneighboring peers. In a mesh-group, every MSDP peer must be connected to every other peer in thegroup. In this fully-meshed topology, when an SA message is received from a member of the mesh-group, 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 notrequired to forward SA messages to other members of the same mesh-group. However, SA messagesare flooded to members of other mesh-groups. An MSDP mesh-group is an easy way to implementinter-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.

NoteWe 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}

MSDP

Multicast 72

• 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 RPAnycast RP is an application of MSDP that allows multiple RPs to operate simultaneously in a PIM-SMdomain. Without anycast RP, multiple routers can be configured as candidate RPs, but at any point intime, only one router can serve as RP. Because anycast RP allows multiple RPs to be simultaneouslyactive, anycast RP provides both load sharing and redundancy, as each RP serves the receivers that areclosest 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 aloopback VLAN. The loopback VLAN IP address should have a 32-bit mask, so that it specifies a hostaddress. All the routers within the PIM-SM domain select the nearest RP for each source and receiver. Ifthe senders and receivers within the PIM-SM domain are distributed evenly, the number of senders thatregister with each RP is approximately equal.

Another requirement of the anycast RP topology is that MSDP must run on all RPs in the PIM-SMdomain, so all RPs are also MSDP peers. We recommend that you configure an MSDP mesh connectionbetween all MSDP peers in the domain.

Whenever any multicast source becomes active, this information is sent in an MSDP SA message to theother MSDP peers in the domain, announcing the presence of the source. If any RP within the domainfails, the IP routing protocol mechanism ensures that next available RP is chosen. If a sender registerswith one RP and a receiver joins another RP, the information shared through MSDP enables PIM-SM toestablish an SPT between the receiver and the source.

NoteWe 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 tosee 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 theother MSDP peers.

• The MSDP SA message includes the configured originator ID, which is a mandatory configurationcomponent.

• Each remote peer checks the RPF of the originator ID address and informs the PIM process on thatremote router about active multicast sources.

• Remote receivers get data packets through the remote shared tree, and can then switch over to theSPT by sending join messages directly towards the source.

To configure anycast RP, do the following at each anycast RP router:

MSDP

Multicast 73

1 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 thecommand:

configure {vlan} vlan_name ipaddress [ipaddress {ipNetmask} | ipv6-link-local

| {eui64} ipv6_address_mask]

NoteThe anycast RP address must be unique to the loopback VLAN and be the same on allanycast RP peers. It must not match the router IP address, the PIM BSR address, or anyother 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}

enable ipmcforwarding {vlan name}

4 Add the loopback VLAN into the unicast routing domain using the appropriate command for yourunicast 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 thecommands:

create msdp peer remoteaddr {remote-as remote-AS} {vr vrname}

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}

MSDP

Multicast 74

SA CacheAs an MSDP router learns of new sources either through a PIM-SM Source-Register (SR) message or SAmessage 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 messagesreceived 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 turnremoves the SA information from the local database.

Caching makes it easy for local receivers to know immediately about inter-domain multicast sourcesand to initiate building a source tree towards the source. However, maintaining a cache is heavy both inCPU processing and memory requirements.

NoteOur 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 arestriction that no more than two advertisements per cache entry will be forwarded peradvertisement interval. This is helpful in reducing an SA message storm and unnecessarilyforwarding them to peers.

By default, the router does not send SA request messages to its MSDP peers when a new memberjoins a group and wants to receive multicast traffic. The new member simply waits to receive SAmessages, which eventually arrive.

• Configure the MSDP router to send SA request messages immediately to the MSDP peer when anew 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} {source-

address src-addr} {as-number as-num} {originator-rp originator-rp-addr}

{local} {peer remoteaddr} {vr vrname}

Maximum SA Cache Entry LimitYou can configure a limit on the maximum number of SA cache entries that can be stored in the cachedatabase. Once the number of SA cache entries exceeds the pre-configured limit, any newly receivedcache entries are discarded. You can configure the limit on a per-peer basis. By default, no SA messagelimit 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.

MSDP

Multicast 75

• Display the SA cache limit.


RedundancyBecause the peering relationship between MSDP peers is based on TCP connections, after a failoveroccurs 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 onnew TCP connections.

On a dual MSM system, MSDP runs simultaneously on both MSMs. During failover, the MSDP process onthe active MSM receives and processes all control messages. MSDP on the standby MSM is in a downstate, and doesn’t receive, transmit, or process any control messages. If the active MSM fails, the MSDPprocess loses all state information and the standby MSM becomes active. However, the failover fromthe active MSM to the standby MSM causes MSDP to loses all state information and dynamic data, so itis not a hitless failover.

On fixed-configuration, stackable switches, an MSDP process failure brings down the switch.

SNMP MIBsSNMP MIB access is not supported for MSDP.

MSDP

Multicast 76

4 Multicast Commands

clear igmp groupclear igmp snoopingclear mld countersclear mld groupclear mld snoopingclear msdp countersclear msdp sa-cacheclear pim cacheclear pim snoopingconfigure forwarding ipmc compressionconfigure forwarding ipmc lookup-keyconfigure igmp router-alert receive-requiredconfigure igmp router-alert transmitconfigure igmp snooping filtersconfigure igmp snooping flood-listconfigure igmp snooping leave-timeoutconfigure igmp snooping timerconfigure igmp snooping vlan ports add dynamic groupconfigure igmp snooping vlan ports add static groupconfigure igmp snooping vlan ports add static routerconfigure igmp snooping vlan ports delete static groupconfigure igmp snooping vlan ports delete static routerconfigure igmp snooping vlan ports filterconfigure igmp snooping vlan ports set join-limitconfigure igmp ssm-map addconfigure igmp ssm-map deleteconfigure igmpconfigure ipmcforwardingconfigure ipmroute addconfigure ipmroute deleteconfigure iproute add (Multicast)configure iproute deleteconfigure mcast ipv4 cache timeoutconfigure mcast ipv6 cache timeoutconfigure mldconfigure mld snooping fast-learningconfigure mld snooping filters

Multicast 77

configure mld snooping flood-listconfigure mld snooping leave-timeoutconfigure mld snooping timerconfigure mld snooping vlan ports add dynamic groupconfigure mld snooping vlan ports add static groupconfigure mld snooping vlan ports add static routerconfigure mld snooping vlan ports delete static groupconfigure mld snooping vlan ports delete static routerconfigure mld snooping vlan ports filterconfigure mld snooping vlan ports join-limitconfigure mld ssm-map addconfigure mld ssm-map deleteconfigure msdp as-display-formatconfigure msdp max-rejected-cacheconfigure msdp originator-idconfigure msdp peer default-peerconfigure msdp peer descriptionconfigure msdp peer mesh-groupconfigure msdp peer no-default-peerconfigure msdp peer passwordconfigure msdp peer sa-filterconfigure msdp peer sa-limitconfigure msdp peer source-interfaceconfigure msdp peer timerconfigure msdp peer ttl-thresholdconfigure msdp sa-cache-serverconfigure mvr add receiverconfigure mvr add vlanconfigure mvr delete receiverconfigure mvr delete vlanconfigure mvr mvr-addressconfigure mvr static groupconfigure pim add vlanconfigure pim borderconfigure pim cbsrconfigure pim crp staticconfigure pim crp timerconfigure pim crp vlanconfigure pim delete vlanconfigure pim dr-priorityconfigure pim iproute sharing hashconfigure pim register-policy rp

Multicast Commands

Multicast 78

configure pim register-policyconfigure pim register-checksum-toconfigure pim register-rate-limit-intervalconfigure pim register-suppress-interval register-probe-intervalconfigure pim shutdown-priorityconfigure pim spt-thresholdconfigure pim ssm rangeconfigure pim ssmconfigure pim state-refresh timer origination-intervalconfigure pim state-refresh timer source-active-timerconfigure pim state-refresh ttlconfigure pim state-refreshconfigure pim timer vlanconfigure pim vlan trusted-gatewaycreate msdp mesh-groupcreate msdp peerdelete msdp mesh-groupdelete msdp peerdisable igmp snooping vlan fast-leavedisable igmp snoopingdisable igmp ssm-mapdisable igmpdisable ipmcforwarding ipv6disable ipmcforwardingdisable mlddisable mld snoopingdisable mld-ssm mapdisable msdp data-encapsulationdisable msdp export local-sadisable msdp peerdisable msdp process-sa-requestdisable msdpdisable mvrdisable pim iproute sharingdisable pim snoopingdisable pim ssm vlandisable pimenable igmp snooping vlan fast-leaveenable igmp snooping with-proxyenable igmp snoopingenable igmp ssm-mapenable igmp

Multicast Commands

Multicast 79

enable ipmcforwarding ipv6enable ipmcforwardingenable mldenable mld snooping with-proxyenable mld snoopingenable mld-ssm mapenable msdp data-encapsulationenable msdp export local-saenable msdp peerenable msdp process-sa-requestenable msdpenable mvrenable pim iproute sharingenable pim snoopingenable pim ssm vlanenable pimmrinfomtracerefresh mld ssm-maprtlookup rpfrtlookupshow igmp groupshow igmp snooping cacheshow igmp snooping vlan filtershow igmp snooping vlan staticshow igmp snooping vlanshow igmp snoopingshow igmp ssm-mapshow igmpshow ipmrouteshow iproute multicastshow L2statsshow mcast cacheshow mcast ipv6 cacheshow mldshow mld countersshow mld groupshow mld snooping vlan filtershow mld snooping vlan staticshow mld snoopingshow mld ssm-mapshow msdp memory

Multicast Commands

Multicast 80

show msdp mesh-groupshow msdp peershow msdp sa-cacheshow msdpshow mvr cacheshow mvrshow pim cacheshow pim snoopingshow pimunconfigure igmp snooping vlan ports set join-limitunconfigure igmp ssm-mapunconfigure igmpunconfigure mldunconfigure mld ssm-mapunconfigure msdp sa-cache-serverunconfigure pim borderunconfigure pim ssm rangeunconfigure pim

clear igmp groupclear igmp group {grpipaddress} {{vlan} name}

DescriptionRemoves one or all IGMP groups.

Syntax Description

grpipaddress Specifies the group IP address.

name Specifies a VLAN name.

DefaultN/A.

Usage GuidelinesThis command can be used by network operations to manually remove learned IGMP group entriesinstantly. Traffic is impacted until the IGMP groups are relearned. Use this command for diagnosticpurposes only.

Multicast Commands

Multicast 81

Example

The following command clears all IGMP groups from VLAN accounting:

clear igmp group accounting

HistoryThis command was first available in ExtremeXOS 10.1.

Platform AvailabilityThis command is available on platforms that support the appropriate license. For complete informationabout software licensing, including how to obtain and upgrade your license and which licenses supportthe IPv4 multicast feature, see the Feature License Requirements document.

clear igmp snoopingclear igmp snooping {{vlan} name}

DescriptionRemoves one or all IGMP snooping entries.

Syntax Description


DefaultN/A.

Usage GuidelinesThis command can be used by network operations to manually remove IGMP snooping entriesinstantly. However, removing an IGMP snooping entry can disrupt the normal forwarding of multicasttraffic until the snooping entries are learned again.

The dynamic IGMP snooping entries are removed, and then recreated upon the next general query. Thestatic 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 Commands

Multicast 82



Platform AvailabilityThis command is available on platforms that support the appropriate license. For complete informationabout software licensing, including how to obtain and upgrade your license and which licenses supportthe IGMP snooping feature, see the Feature License Requirements document.

clear mld countersclear mld counters {{vlan} vlan_name}

DescriptionClears MLD statistics counters.

Syntax Description

vlan_name Specifies a VLAN name.

DefaultN/A.

Usage GuidelinesUse 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.


Platform AvailabilityThis command is available on the platforms listed for the IPv6 multicast routing feature in the FeatureLicense Requirements document.

Multicast Commands

Multicast 83




clear mld groupclear mld group {v6grpipaddress} {{vlan} name}

DescriptionRemoves one or all MLD groups.

Syntax Description

v6grpipaddress Specifies the group IP address.


DefaultN/A.

Usage GuidelinesThis 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



clear mld snoopingclear mld snooping {{vlan} name}

DescriptionRemoves one or all MLD snooping entries.

Multicast Commands

Multicast 84



Syntax Description


DefaultN/A.

Usage GuidelinesThis 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 untilthe snooping entries are learned again.

The static and dynamic MLD snooping entries are removed, and then recreated upon the next generalquery. The static router entry is removed and recreated immediately.

Example

The following command clears MLD snooping from VLAN accounting:

clear mld snooping accounting



clear msdp countersclear msdp counters {peer remoteaddr | peer all | system} {vr vrname}

DescriptionThis 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 Commands

Multicast 85



system Clears the global MSDP counters.

vrname Specifies the name of the virtual router to which this command applies. If a name is notspecified, it is extracted from the current CLI context.

DefaultN/A.

Usage GuidelinesThe 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 allother 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 Commands

Multicast 86

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


Platform AvailabilityThis command is available on platforms that support the appropriate license. For complete informationabout software licensing, including how to obtain and upgrade your license and which licenses supportthe MSDP feature, see the Feature License Requirements document.

clear msdp sa-cacheclear msdp sa-cache {{peer} remoteaddr | peer all} {group-address grp-addr} {vr

vrname}

DescriptionThis 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 fromthe database.

grp-addr Specifies the IP address and subnet mask of the multicast group you want to clear. All SAcache 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 thespecified peer are removed from the database.


DefaultN/A.

Multicast Commands

Multicast 87


Usage GuidelinesMSDP 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



clear pim cache

clear pim {ipv4 | ipv6} cache {group_addr {source_addr}}

DescriptionResets the IP multicast cache table.

Syntax Description

ipv4 Specifies an IPv4 address.


group_addr Specifies a group address.

source_addr Specifies a source IP address.

DefaultIf no options are specified, all IP multicast cache entries are flushed.

Usage GuidelinesThis command can be used by network operators to manually remove IPMC software and hardwareforwarding cache entries instantly. If the stream is available, caches are re-created; otherwise, cachesare removed permanently. This command can disrupt the normal forwarding of multicast traffic.

Multicast Commands

Multicast 88


Example

The following example resets the IP multicast table for group 224.1.2.3:

clear pim cache 224.1.2.3


Platform AvailabilityThis command is available on platforms that support the appropriate license. For complete informationabout software licensing, including how to obtain and upgrade your license and which licenses supportthe PIM feature, see the Feature License Requirements document.

clear pim snoopingclear pim snooping {vlan} name}

DescriptionClears 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.

DefaultN/A.

Usage GuidelinesNone.

Example

The following command clears the PIM snooping database for the Default VLAN:

clear pim snooping "Default"


Multicast Commands

Multicast 89


Platform AvailabilityThis command is available on platforms that support the appropriate license. For complete informationabout software licensing, including how to obtain and upgrade your license and which licenses supportthe PIM snooping feature, see the Feature License Requirements document.

configure forwarding ipmc compressionconfigure forwarding ipmc compression {group-table | off}

DescriptionEnables or disables compression of entries in the IP multicast group table to facilitate improved IPmulticast scaling.

Syntax Description

group-table Enables compression.

off Disables compression.

Defaultgroup-table.

Usage GuidelinesCompression of IP multicast group table entries allows the switch to process more multicast trafficusing the faster switch hardware instead of the relatively slower switch software. Compression requiresadditional processing. Disable this feature if you suspect a problem exposed by IP multicastcompression.

When you enable or disable this feature, all IP multicast entries are flushed, and this can result in atemporary loss of multicast traffic while the IP multicast entries are relearned.

NoteOn BlackDiamond X8 series switches and BlackDiamond 8800 series switches, all IP multicastforwarding entries utilizing the same IP multicast group table entry share a single backplanelink, 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 Commands

Multicast 90



Platform AvailabilityThis command is available on all Summit family switches, BlackDiamond X8 series switches andBlackDiamond 8000 series modules.

configure forwarding ipmc lookup-key

configure forwarding ipmc lookup-key [group-vlan | source-group-vlan | mac-vlan |

mixed-mode]

DescriptionEnables 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 Specifies that IP multicast forwarding database entries are programmed as(SourceIP, GroupIP, VlanId). (Default).

mac-vlan Specifies that IP multicast forwarding database entries are programmed as(Mac, VlanId).

mixed-mode Specifies that IP multicast forwarding database entries are programmed asfollows: L3 cache entries (PIM/MVR/PVLAN) use source-group-vlan; L2 cacheentries (IGMP/MLD/PIM snooping) use mac-vlan.

Defaultsource-group-vlan.

Usage GuidelinesUse this command to choose the lookup-key for multicast forwarding. The following restrictions applyto this command:

The configure forwarding ipmc lookup-key mac-vlan command is disallowed under thefollowing 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 Commands

Multicast 91

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 isdisallowed. After enabling this mode, if a new member with unsupported chipset joins, then thatcard will be failed. The following warning message is displayed when the “mixed-mode” option isspecified:

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 couldbe 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 wasintroduced. Because we are introduced IPv6 multicast support in ExtremeXOS 15.2, this command isdeprecated, and the new configure forwarding ipmc lookup-key command now coversboth 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


Platform AvailabilityThis command is available on all Summit family switches, BlackDiamond X8 series switches andBlackDiamond 8000 series modules.

configure igmp router-alert receive-requiredconfigure igmp router-alert receive-required [on | off] {{vlan} vlan_name}

Multicast Commands

Multicast 92

DescriptionControls when the router-alert option is required for IGMPv2 and IGMPv3 packet reception andprocessing.

Syntax Description

vlan Applies the configuration only to the specified VLAN. If no VLAN is specified,the configuration applies to all VLANs.

DefaultOff—All IGMP packets are received and processed.

Usage GuidelinesBy default, the ExtremeXOS software receives and processes all IGMP packets, regardless of the settingof the router-alert option within a packet. The default configuration works with all switches thatsupport the ExtremeXOS software.

IETF standards require that a router accept and process IGMPv2 and IGMPv3 packets only when therouter-alert option is set. The on setting for this command sets the ExtremeXOS software to complywith the IETF standards and should be used when the switch will be used with third-party switches thatexpect IETF compliant behavior.

Example

The following command configures the switch for IETF compliant IGMP packet processing:

configure igmp router-alert receive-required on

HistoryThis command was first available in ExtremeXOS 12.5.3.


configure igmp router-alert transmitconfigure igmp router-alert transmit [on | off] {{vlan} vlan_name}

DescriptionControls whether the router-alert option is set when forwarding IGMPv2 and IGMPv3 packets.

Multicast Commands

Multicast 93


Syntax Description

vlan Applies the configuration only to the specified VLAN. If no VLAN is specified,the configuration applies to all VLANs.

DefaultOn—The router-alert option is set when forwarding IGMPv2 and IGMPv3 packets.

Usage GuidelinesIETF standards require that a router set the router-alert option in forwarded IGMPv2 and IGMPv3packets. The ExtremeXOS software has been updated to comply with this requirement using thedefault settings.

Earlier versions of the ExtremeXOS software forwarded all IGMP packets without setting the router-alertoption. If compatibility issues arise, you can configure the software to use the legacy behavior byusing 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



configure igmp snooping filtersconfigure igmp snooping filters [per-port | per-vlan]

DescriptionSelects 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 Commands

Multicast 94


Defaultper-port.

Usage GuidelinesThis 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 themaximum numbers listed in the following table. This option conserves usage of the hardware Layer 3multicast forwarding table.

When the number of configured VLANs is larger than the maximum values listed here, select the per-port option. Each VLAN requires additional interface hardware ACL resources. The per-port optionconserves usage of the interface hardware ACL resources.

Table 6: Maximum Number of VLANs Supported by per-VLAN IGMP Snooping FiltersSummit Switch and BlackDiamond 8000 SeriesModule Type

Maximum Number of VLANs When per-VLAN SnoopingFilters 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 thistable. The maximum number specified here is individual limit for IGMP snooping filters. If bothIGMP and MLD snooping filters are used, the maximum numbers are lower than the onesspecified.

Example

The following command configures the switch to install the per-VLAN IGMP snooping filters:

configure igmp snooping filters per-vlan


1 The actual maximum value is smaller if other processes require entries in the interface ACL table.

Multicast Commands

Multicast 95


configure igmp snooping flood-listconfigure igmp snooping flood-list [policy | none] {vr vrname}

DescriptionConfigures 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.

DefaultNone.

Usage GuidelinesWith this command, a user can configure certain multicast addresses to be slow path flooded withinthe VLAN, which otherwise are fast path forwarded according to IGMP and/or Layer 3 multicastprotocol.

A policy file is a text file with the extension, .pol. It can be created or edited with any text editor. Thespecified policy file policy file should contain a list of addresses which determine if certainmulticast streams are to be treated specially. Typically, if the switch receives a stream with adestination address which is in the policy file in 'permit' mode, that stream is software floodedand 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 addresseswithin system reserved ranges. Specifically this feature was introduced to solve the problem ofrecognizing 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" # Do not touch the rest of the file!!!! entry igmpFlood { if match any { #------------------ Start of group addresses ------------------

Multicast Commands

Multicast 96


nlri 234.1.1.1/32; nlri 239.1.1.1/32; #------------------- end of group addresses ------------------- } then { permit; } } entry catch_all { if { } then { deny; } }

NoteThe 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 optionoverrides any default mechanism of hardware forwarding (with respect to IGMP, PIM, orDVMRP), 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 pathflooding:

configure igmp snooping flood-list none



Multicast Commands

Multicast 97


configure igmp snooping leave-timeoutconfigure igmp snooping leave-timeout leave_timeout_ms {vr vrname}

DescriptionConfigures the IGMP snooping leave timeout.

Syntax Description

leave_timeout_ms Specifies an IGMP leave timeout value in milliseconds.


Default1000 ms.

Usage GuidelinesThe leave-timeout is the IGMP leave override interval. If no other hosts override the IGMP leave by theend 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 theleave-timeout to a multiple– of 100 ms. For values of more than one second, you must set the leave-timeout 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



configure igmp snooping timerconfigure igmp snooping timer router_timeout host_timeout {vr vrname} {vlan

vlan_name}

Multicast Commands

Multicast 98


DescriptionConfigures 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 host’s group snooping entry.


vlan Specifies a VLAN.

vlan_name Specifies the VLAN name. If no VLAN is specified, the setting is applied to allexisting VLANs.

DefaultThe router timeout default setting is 260 seconds. The host timeout setting is 260 seconds.

Usage GuidelinesTimers should be set to approximately 2.5 times the router query interval in use on the network. Specifythe following:

• router timeout—The maximum time, in seconds, that a router snooping entry can remain in theIGMP snooping table without receiving a router report. If a report is not received, the entry isdeleted. The range is 10 to 214,748,364 seconds (6.8 years). The default setting is 260 seconds.

• host timeout—The maximum time, in seconds, that a group snooping entry can remain in theIGMP snooping table without receiving a group report. If a report is not received, the entry isdeleted. The range is 10 to 214,748,364 seconds. The default setting is 260 seconds.

NoteThe host_timeout value should be less than or equal to the query timeout value, whichis 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 querymessages. Without an IGMP querier, the switch eventually stops forwarding IP multicast packets to anyport, because the IGMP snooping entries time out, based on the value specified in host_timeout orrouter_timeout.

Example

The following example configures the IGMP snooping timers:

configure igmp snooping timer 600 600


Multicast Commands

Multicast 99


configure igmp snooping vlan ports add dynamic groupconfigure igmp snooping {vlan} vlan_name {ports portlist} add dynamic group

[ grpipaddress ]

DescriptionConfigures an IGMP dynamic group.

Syntax Description

vlan_name Specifies a vlan name.

portlist Specifies a port list.

grpipaddress Specifies the multicast group IP address.

DefaultN/A.

Usage GuidelinesThis command is not saved in the configuration. The following message is displayed on execution ofthis 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 Port Age 225.1.1.1 2 ixia113 47 3

Total: 1 switch.113 #

Multicast Commands

Multicast 100


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



switch.114 # show igmp group Group Address Ver Vlan Port Age 225.1.1.1 2 ixia113 Lpbk 37

Total: 1 switch.115 #



configure igmp snooping vlan ports add static groupconfigure igmp snooping {vlan} vlanname {ports portlist }add static group

grpipaddress

DescriptionConfigures VLAN ports to receive the traffic from a multicast group, even if no IGMP joins have beenreceived on the port.

Syntax Description

vlanname Specifies a VLAN name.

portlist Specifies one or more ports or slots and ports.

grpipaddress Specifies the multicast group IP address.

DefaultN/A.

Multicast Commands

Multicast 101


Usage GuidelinesUse this command to forward a particular multicast group to VLAN ports. In effect, this commandemulates a host on the port that has joined the multicast group. As long as the port is configured withthe 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 messagesuse 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 multicastcontrol subnet range (224.0.0.x/24).

If the ports also have an IGMP filter configured, the filter entries take precedence. IGMP filters areconfigured 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 toVLAN "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 Age 225.1.1.1(s) 2 marketing 47 0

Total: 1switch.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


switch.33 # show igmp group Group Address Ver Vlan Port Age 225.1.1.1(s) 2 marketing Lpbk 0

Total: 1switch.34 #


Multicast Commands

Multicast 102


configure igmp snooping vlan ports add static routerconfigure igmp snooping {vlan} vlanname ports portlist add static router

DescriptionConfigures VLAN ports to forward the traffic from all multicast groups, even if no IGMP joins have beenreceived on the port.

Syntax Description



DefaultN/A.

Usage GuidelinesUse this command to forward all multicast groups to the specified VLAN ports. In effect, this commandemulates a multicast router attached to those ports. As long as the ports are configured with the staticentry, 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 VLANmarketing on ports 2:1-2:4:

configure igmp snooping marketing ports 2:1-2:4 add static router



Multicast Commands

Multicast 103



configure igmp snooping vlan ports delete static groupconfigure igmp snooping {vlan} vlan_name {ports port_list} delete static group

[ip_address | all]

DescriptionRemoves the port configuration that causes multicast group traffic to be forwarded, even if no IGMPleaves have been received on the port.

Syntax Description


port_list Specifies one or more ports or slots and ports.

ip_address Specifies the multicast group IP address.

all Delete all the static groups.

DefaultN/A.

Usage GuidelinesUse 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 tothe VLAN marketing on ports 2:1-2:4:

configure igmp snooping marketing ports 2:1-2:4 delete static group 224.34.15.37



Multicast Commands

Multicast 104


configure igmp snooping vlan ports delete static routerconfigure igmp snooping vlan vlanname ports portlist delete static router

DescriptionRemoves 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


portlist Specifies one or more ports or slots and ports. On a modular switch, can be alist of slots and ports. On a standalone switch, can be one or more portnumbers. May be in the form 1, 2, 3-5, 2:5, 2:6-2:8.

DefaultN/A.

Usage GuidelinesUse 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 forwardedto VLAN marketing on ports 2:1-2:4:

configure igmp snooping marketing ports 2:1-2:4 delete static router



configure igmp snooping vlan ports filterconfigure igmp snooping vlan vlanname ports portlist filter [policy | none]

Multicast Commands

Multicast 105


DescriptionConfigures an IGMP snooping policy file filter on VLAN ports.

Syntax Description


portlist Specifies one or more ports or slots and ports. On a modular switch, can be a list ofslots and ports. On a stand-alone switch, can be one or more port numbers. May be inthe form 1, 2, 3-5, 2:5, 2:6-2:8.

policy Specifies the policy file for the filter.

DefaultNone.

Usage GuidelinesUse 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 multicastgroups 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 Commands

Multicast 106

Example

The following example configures the policy file ap_multicast to filter multicast packets forwarded toVLAN marketing on ports 2:1-2:4:

configure igmp snooping marketing ports 2:1-2:4 filter ap_multicast



configure igmp snooping vlan ports set join-limitconfigure igmp snooping {vlan} vlanname ports portlist set join-limit {num}

DescriptionConfigures VLAN ports to support a maximum number of IGMP joins.

Syntax Description



num Specifies the maximum number of joins permitted on the ports. The range is 1to 500.

DefaultNo limit.


Example

The following example configures port 2:1 in the Default VLAN to support a maximum of 100 IGMPjoins:

configure igmp snooping "Default" ports 2:1 set join-limit 100

Multicast Commands

Multicast 107




configure igmp ssm-map addconfigure igmp ssm-map add group_ip [prefix | mask] [source_ip | src_domain_name]

{vr vr-name}

DescriptionConfigures 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 to32.

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 theVR specified by the current CLI VR context.

DefaultN/A.

Usage GuidelinesIGMP SSM mapping operates only with IPv4.

Example

The following example configures an IGMP-SSM mapping for the range of multicast IP addresses at232.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 Commands

Multicast 108




configure igmp ssm-map deleteconfigure igmp ssm-map delete group_ip [prefix} | mask] [source_ip | all] vr vr-

name}

DescriptionUnconfigures 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 to32.

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.


DefaultN/A.


Example

The following example deletes an IGMP-SSM mapping for the range of multicast IP addresses at232.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 Commands

Multicast 109




configure igmpconfigure igmp query_interval query_response_interval last_member_query_interval

{robustness}

DescriptionConfigures 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_interval

Specifies the maximum group-specific query response time (in seconds).

robustness Specifies the degree of robustness for the network.

Default

• query interval—125 seconds

• query response interval—10 seconds

• last member query interval—1 second

• robustness—2

Usage GuidelinesTimers are based on RFC2236. Specify the following:

• query interval—The amount of time, in seconds, the system waits between sending out generalqueries. The range is 1 to 429,496,729 seconds.

• query response interval—The maximum response time inserted into the periodic general queries.The range is 1 to 25 seconds.

• last member query interval—The maximum response time inserted into a group-specific query sentin response to a leave group message. The range is 1 to 25 seconds.

Multicast Commands

Multicast 110


• robustness—The degree of robustness of the network. The range is 2 to 7. This parameter allowstuning for the expected packet loss on a link. If a link is expected to have packet loss, this parametercan 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 usingthe configure igmp snooping timer router_timeout host_timeout {vr vrname}command. The effective host_timeout is the lesser value of the group_timeout and theconfigured host_timeout.

Example

The following command configures the IGMP timers:

configure igmp 100 5 1 3



configure ipmcforwardingconfigure ipmcforwarding to-cpu [auto | off] ports port_list

DescriptionConfigure whether IP multicast CPU filters are installed automatically.

Syntax Description

auto The software will automatically program IP multicast processing based onconfiguration.

off IP multicast packets received on this port are always flooded with no CPUprocessing.

port_list Specifies on or more ports.

DefaultN/A.

Multicast Commands

Multicast 111


Usage GuidelinesIP 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



configure ipmroute addconfigure ipmroute add [source-net mask-len | source-net mask] {{protocol}

protocol} rpf-address {metric} {vr vr-name}

DescriptionAdds 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.

DefaultThe following defaults apply:

• metric—1

• vr-name—VR of the current CLI context

• protocol—none

Multicast Commands

Multicast 112


Usage GuidelinesThis command allows you to statically configure where multicast sources are located (even though theunicast routing table has different entries). It allows you to configure a multicast static route in such away 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 networksubnet 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 ametric of 100:

configure ipmroute add 0.0.0.0/0 192.75.0.91 100



configure ipmroute deleteconfigure ipmroute delete [source-net/mask-len | source-net mask] {{protocol}

protocol} rpf-address {vr vr-name}

DescriptionDeletes a static multicast address from the multicast routing table.

Syntax Description


mask-len Mask length for the IP multicast source's subnet. Range is 1–32.


protocol Unicast routing protocol that is to be used for route learning.

rpf-address Next hop through which the multicast source can be reached.


Multicast Commands

Multicast 113


Defaultvr-name is the VR of the current CLI context.

Usage GuidelinesThis command allows you to delete an existing multicast static route. It allows you to configurecongruent 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



configure iproute add (Multicast)configure iproute add [ipNetmask | ip_addr mask] gateway {metric} {multicast |


DescriptionAdds a static route to the routing table.

Syntax Description

ipNetmask Specifies an IP address/mask length.

ip_addr Specifies an IP address.


gateway Specifies a VLAN gateway.

metric Specifies a cost metric.

vrname Specifies the virtual router to which the route is added.

multicast Adds the specified route to the multicast routing table.

multicast-only Adds the specified route to the multicast routing table. This option isprovided for backward compatibility with releases prior to ExtremeXOS 12.1.

Multicast Commands

Multicast 114


unicast Adds the specified route to the unicast routing table.

unicast-only Adds the specified route to the unicast routing table. This option is providedfor backward compatibility with releases prior to ExtremeXOS 12.1.

DefaultIf you do not specify a virtual router, the current virtual router context is used.

Usage GuidelinesUse a mask value of 255.255.255.255 to indicate a host entry.

NoteAlthough dynamic unicast routes can be captured in the multicast routing table, unicast staticroutes cannot be captured in the multicast routing table. To create a static route for themulticast 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


The multicast and unicast keywords were first available in ExtremeXOS 12.1. These keywordsreplace multicast-only and unicast-only, which remain in the software for backwardcompatibility.


configure iproute deleteconfigure iproute delete [ipNetmask | ipaddress mask] gateway {multicast |


DescriptionDeletes a static address from the routing table.

Multicast Commands

Multicast 115


Syntax Description

ipNetmask Specifies an IP address/mask length.

ipaddress Specifies an IP address.


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.

DefaultIf you do not specify a virtual router, the current virtual router context is used.

Usage GuidelinesUse 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


The multicast and unicast keywords were first available in ExtremeXOS 12.1. These keywordsreplace multicast-only and unicast-only, which remain in the software for backwardcompatibility.


configure mcast ipv4 cache timeoutconfigure mcast ipv4 cache timeout {seconds | none}

Multicast Commands

Multicast 116


DescriptionConfigures the IPv4 multicast cache timeout.

Syntax Description

seconds Idle time after which cache entries are deleted.

none Cache entries are not timed out.

Default300 seconds.

Usage GuidelinesCache timeout is the time after which the cache entries are deleted if traffic is not received for thatduration. 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 tobe 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



configure mcast ipv6 cache timeoutconfigure mcast ipv6 cache timeout {seconds | none}

Multicast Commands

Multicast 117


DescriptionConfigures the IPv6 multicast cache timeout.

Syntax Description

seconds Idle time after which cache entries are deleted.

none Cache entries are not timed out.

Default300 seconds.

Usage GuidelinesCache timeout is the time after which the cache entries are deleted if traffic is not received for thatduration. 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 tobe 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


Platform AvailabilityThis command is available on platforms that support the appropriate license. For complete informationabout software licensing, including how to obtain and upgrade your license and which licenses supportthe MLD snooping feature, see the Feature License Requirements document.

configure mldconfigure mld query_interval query_response_interval last_member_query_interval

{robustness}

Multicast Commands

Multicast 118


DescriptionConfigures 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_interval

Specifies the maximum group-specific query response time (in seconds).

robustness Specifies the degree of robustness for the network.

Default

• query interval—125 seconds

• query response interval—10 seconds

• last member query interval—1 second

• robustness—2

Usage GuidelinesTimers are based on RFC2710. Specify the following:

• query interval—The amount of time, in seconds, the system waits between sending out generalqueries. The range is 1 to 429,496,729 seconds.

• query response interval—The maximum response time inserted into the periodic general queries.The range is 1 to 25 seconds.

• last member query interval—The maximum response time inserted into a group-specific query sentin response to a leave group message. The range is 1 to 25 seconds.

• robustness—The 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



Multicast Commands

Multicast 119



configure mld snooping fast-learningconfigure mld snooping fast-learning [on | off] [vlan vlan_name]

DescriptionConfigures fast-learning mode.

Syntax Description

vlan_name Specifies a vlan name

Defaultoff.

Usage GuidelinesWhen MLD snooping is enabled on a VLAN, learning of group entries will happen only when the nextperiodic query is sent by the querier in the network. When fast-learning is turned on using thiscommand, 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



configure mld snooping filtersconfigure mld snooping filters [per-port | per-vlan]

Multicast Commands

Multicast 120


DescriptionSelects 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.

Defaultper-port.

Usage GuidelinesThis 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 themaximum numbers listed in Table 6: Maximum Number of VLANs Supported by per-VLAN IGMPSnooping Filters on page 95. This option conserves usage of the hardware Layer 3 multicast forwardingtable.

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 theper-port option. Each VLAN requires additional interface hardware ACL resources. The per-port optionconserves 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



configure mld snooping flood-listconfigure mld snooping flood-list [policy | none]

Multicast Commands

Multicast 121


DescriptionConfigures 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.

DefaultNone.

Usage GuidelinesWith this command, you can configure certain multicast addresses to be slow path flooded within theVLAN, 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. Thespecified policy file policy file should contain a list of addresses that determine if certain multicaststreams are to be treated specially. Typically, if the switch receives a stream with a destination addresswhich is in the policy file in 'permit' mode, that stream is software flooded and no hardware entryis 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 addresseswithin system reserved ranges. Specifically this feature was introduced to solve the problem ofrecognizing 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;#------------------- end of group addresses -------------------} then {permit;}}entry catch_all {if {} then {deny;

Multicast Commands

Multicast 122

}}

NoteThe 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, suchas control packets. It should not be used for multicast data packets. This option overrides anydefault mechanism of hardware forwarding (with respect to MLD or PIM), so it should beused 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.

NoteThis command has no effect in the current release, as IPv6 multicast traffic floods on allplatforms.

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-pathflooding:

configure mld snooping flood-list none



configure mld snooping leave-timeoutconfigure mld snooping leave-timeout leave_timeout_ms

DescriptionConfigures the MLD snooping leave timeout.

Multicast Commands

Multicast 123



Syntax Description

leave_timeout_ms Specifies an MLD leave timeout value in milliseconds upon receiving an MLDdone message.

Default1000 ms.

Usage GuidelinesThe range is 0–175000 ms (175 seconds). For timeout values of one second or less, you must set theleave-timeout to a multiple of 100 ms. For values of more than one second, you must set the leave-timeout 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 donemessage 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



configure mld snooping timerconfigure mld snooping timer router_timeout host_timeout

DescriptionConfigures 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 host’s group snooping entry.

Multicast Commands

Multicast 124



DefaultThe router timeout default setting is 260 seconds. The host timeout setting is 260 seconds.

Usage GuidelinesTimers should be set to approximately 2.5 times the router query interval in use on the network. Specifythe following:

• router_timeout—The maximum time, in seconds, that a router snooping entry can stay withoutreceiving a router report. The range is 10 to 214,748,364 seconds (6.8 years). The default setting is260 seconds.

• host_timeout—The maximum time, in seconds, that a group snooping entry can stay withoutreceiving a group report. The range is 10 to 214,748,364 seconds (6.8 years). The default setting is260 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 theusage of network bandwidth and prevents multicast traffic from being flooded to parts of the networkthat 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 everyVLAN to periodically generate MLD query messages. Without an MLD querier, the switch eventuallystops 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



configure mld snooping vlan ports add dynamic groupconfigure mld snooping {vlan} vlan_name {ports portlist} add dynamic group

[v6group]

Multicast Commands

Multicast 125



DescriptionConfigures an MLD dynamic group.

Syntax Description


portlist Specifies a port list.

v6group Specifies a version 6 group.

DefaultN/A.

Usage GuidelinesThis command is not saved in the configuration. The following message is displayed on execution ofthis command:


Example

# show mcast cache Snooping/MVR Cache Timeout: 300 sec

Type Group Sender Age InVlan

pim 225.1.1.1 20.20.20.50 0 v1 Vlan Port Vid v1 1 10 v3 pbk 4088

snoop 224.0.0.5 10.10.10.1 21 v1 Vlan Port Vid v1 1 10

snoop 224.0.0.13 10.10.10.1 21 v1 Vlan Port Vid v1 1 10

Multicast cache distribution: 2 entries from Snooping 0 entries from MVR 1 entries from PIMTotal Cache Entries: 3


Multicast Commands

Multicast 126


configure mld snooping vlan ports add static groupconfigure mld snooping {vlan} vlan_name {ports port_list } add static group

v6grpipaddress

DescriptionConfigures VLAN ports to receive the traffic from a multicast group, even if no MLD joins have beenreceived on the port.

Syntax Description


port_list Specifies one or more ports or slots and ports. On a modular switch, it can bea list of slots and ports. On a standalone switch, it can be one or more portnumbers. In the form 1, 2, 3-5, 2:5, 2:6-2:8.

v6grpipaddress Specifies the multicast group IPv6 address.

DefaultN/A.

Usage GuidelinesUse this command to forward a particular multicast group to VLAN ports. In effect, this commandemulates a host on the port that has joined the multicast group. As long as the port is configured withthe 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 messagesuse the VLAN IPv6 address for source address of the messages. If the VLAN has no IPv6 addressassigned, 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 toVLAN marketing on ports 2:1-2:4:

configure mld snooping marketing ports 2:1-2:4 add static group ff02::1:1

Multicast Commands

Multicast 127




configure mld snooping vlan ports add static routerconfigure mld snooping {vlan} vlan_name ports port_list add static router

DescriptionConfigures VLAN ports to forward the traffic from all multicast groups, even if no MLD joins have beenreceived on the port.

Syntax Description


port_list Specifies one or more ports or slots and ports. On a modular switch, it can bea list of slots and ports. On a standalone switch, it can be one or more portnumbers. May be in the form 1, 2, 3-5, 2:5, 2:6-2:8.

DefaultN/A.

Usage GuidelinesUse this command to forward all multicast groups to the specified VLAN ports. In effect, this commandemulates a multicast router attached to those ports. As long as the ports are configured with the staticentry, 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 VLANmarketing on ports 2:1-2:4:

configure mld snooping marketing ports 2:1-2:4 add static router


Multicast Commands

Multicast 128




configure mld snooping vlan ports delete static groupconfigure mld snooping {vlan} vlan_name ports port_list delete static group [all

| v6grpipaddress]

DescriptionRemoves the configuration that causes VLAN ports to receive the traffic from a multicast group, even ifno MLD joins have been received on the port.

Syntax Description


port_list Specifies one or more ports or slots and ports. On a modular switch, it can bea list of slots and ports. On a standalone switch, it can be one or more portnumbers. 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.

DefaultN/A.

Usage GuidelinesUse 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 toVLAN 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


Multicast Commands

Multicast 129




configure mld snooping vlan ports delete static routerconfigure mld snooping {vlan} vlan_name ports port_list delete static router

DescriptionConfigures VLAN ports to stop forwarding the traffic from all multicast groups, unless MLD joins havebeen received on the port.

Syntax Description


port_list Specifies one or more ports or slots and ports. On a modular switch, it can bea list of slots and ports. On a standalone switch, it can be one or more portnumbers. May be in the form 1, 2, 3-5, 2:5, 2:6-2:8.

DefaultNone.

Usage GuidelinesUse this command to remove the configuration that forwards all multicast groups to the specifiedVLAN ports.

Example

The following example removes a static MLD entry so all multicast groups are not forwarded to VLANmarketing 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



Multicast Commands

Multicast 130





configure mld snooping vlan ports filterconfigure mld snooping vlan vlan_name ports port_list filter [policy]

DescriptionConfigures a MLD snooping policy file filter on VLAN ports.

Syntax Description


port_list Specifies one or more ports or slots and ports. On a modular switch, can be alist of slots and ports. On a standalone switch, can be one or more portnumbers. May be in the form 1, 2, 3-5, 2:5, 2:6-2:8.

policy Specifies the policy file for the filter.

DefaultNone.

Usage GuidelinesUse 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 themulticast 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:

## Add your group addresses between "Start" and "end"# Do not touch the rest of the file!!!!entry mldFilter {if match any {#------------------ Start of group addresses ------------------nlri FF03::1/128;nlri FF05::1/112;#------------------- end of group addresses -------------------} then {deny;}}entry catch_all {if {} then {permit;}

Multicast Commands

Multicast 131

Example

The following example configures the policy file ap_multicast to filter multicast packets forwarded toVLAN marketing on ports 2:1-2:4:

configure mld snooping marketing ports 2:1-2:4 filter ap_multicast



configure mld snooping vlan ports join-limit

configure mld snooping {vlan} vlan_name ports port_list join-limit [num_joins |

no-limit]

DescriptionConfigures VLAN ports to support a maximum number of MLD joins.

Syntax Description

vlan_name Specifies a VLAN name


num Specifies the maximum number of joins permitted on the ports. The range is 1to 5000.

DefaultNo limit.


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 Commands

Multicast 132




configure mld ssm-map addconfigure mld ssm-map add v6groupnetmask [v6sourceip | src_domain_name] { {vr}

vr_name }

DescriptionAdds an MLD SSM Mapping entry on a VR.

Syntax Description

v6groupnetmask You must provide group address with the mask length. Instead of configuringseparate entries for a continuous range of IP addresses, this optimizes a rangeof 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 byspecifying the domain name.

VR vr_name Specifies the virtual router name.

DefaultDisabled.

Usage GuidelinesWhen an MLDv1 report is received for this group or group range, the list of sources configured usingthis 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 aspecific 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 Commands

Multicast 133


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 :

configure mld ssm-map add



configure mld ssm-map delete

configure mld ssm-map delete v6groupnetmask [v6sourceip | src_domain_name | all]

{{vr} vr_name}

DescriptionDeletes an MLD SSM Mapping entry on a VR.

Syntax Description

v6groupnetmask You must provide group address with the mask length. Instead of configuringseparate entries for a continuous range of IP addresses, this optimizes a rangeof 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 byspecifying the domain name.

all Specifies that all the mapping entries associated with v6groupnetmask aredeleted.

vr vr_name Specifies the virtual router name.

DefaultDisabled.

Multicast Commands

Multicast 134



Usage GuidelinesWhen an MLDv1 report is received for this group or group range, the list of sources configured usingthis 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 :

configure mld ssm-map delete



configure msdp as-display-formatconfigure msdp as-display-format [asdot | asplain]

DescriptionConfigures the AS number format displayed in show commands.

Syntax Description

asdot Specifies the ASDOT format.

asplain Specifies the ASPLAIN format.

DefaultN/A.

Usage GuidelinesThe ASPLAIN and ASDOT formats are described in RFC 5396, Textual Representation of AutonomousSystem (AS) Numbers.

Multicast Commands

Multicast 135



Example

The following command selects the ASDOT 4-byte AS number format:

configure msdp as-display-format asdot



configure msdp max-rejected-cacheconfigure msdp max-rejected-cache max-cache {vr vrname}

DescriptionConfigures the maximum limit on rejected SA cache entries that an MSDP router will store in itsdatabase.

Syntax Description

max-cache Specifies the maximum number of rejected SA cache entries that the MSDP router willstore in its database. To remove the limit, enter 0 (zero) for the max-cache value.


DefaultBy 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 GuidelinesSA 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 policyrule 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 entriesto store them, which will help debug/diagnose some issues; however, it consumes extra memory.

Multicast Commands

Multicast 136


Example

The following command sets the maximum rejected cache limit to 100 for an MSDP router:

configure msdp max-rejected-cache 100


Platform AvailabilityThis command is available on platforms that support the appropriate license. For complete informationabout software licensing, including how to obtain and upgrade your license and which licenses supportthe MSDP feature,see the Feature License Requirements document.

configure msdp originator-idconfigure msdp originator-id ip-address {vr vrname}

DescriptionConfigures 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 anoriginator ID (that is, to use the default RP address), enter the IP address 0.0.0.0.


DefaultBy default, the RP address is used as the originator ID in locally originated SA messages.

Usage GuidelinesUse this command to override the default RP address used in SA messages. Because only RPs andMSDP border routers originate SAs, there are times when it is necessary to change the ID used for thispurpose. 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 Commands

Multicast 137


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



configure msdp peer default-peerconfigure msdp peer [remoteaddr | all] default-peer {default-peer-policy filter-

name} {vr vrname}

DescriptionThis 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 bethe default peer for all SA entries that are permitted by the policy filter. If an SA messageis allowed by the policy filter, it will be accepted. Otherwise, the SA message has to gothrough the regular RPF-check. The static peer RPF check is the last step in peer RPFalgorithm. So, if an SA message is denied by the default peer policy, ultimately the SAmessage will be rejected by MSDP.




DefaultBy default, no static RPF peer is configured.

Multicast Commands

Multicast 138


The default-peer-policy keyword specifies the name of the policy filter associated with the defaultpeer. You can configure multiple default peers with different policies. If no policy is specified, then thecurrent peer is the default RPF peer for all SA messages.

Usage GuidelinesConfiguring 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 eitherhave 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 canuse 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 canuse a single active peer to accept all SA messages. If that peer goes down, then the next configureddefault 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 peerpolicy for "sales":

configure msdp peer 192.168.45.43 default-peer default-peer-policy sales



Multicast Commands

Multicast 139


configure msdp peer descriptionconfigure msdp peer remoteaddr description {peer-description} {vr vrname}

DescriptionConfigures a name or description for an MSDP peer. This text is for display purposes only.

Syntax Description


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 isnot specified, it is extracted from the current CLI context.

DefaultBy default, no name or description is specified.

Usage GuidelinesUse this command to configure a name or description to make an MSDP peer easier to identify. Thedescription 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



Multicast Commands

Multicast 140


configure msdp peer mesh-groupconfigure msdp peer [remoteaddr | all] mesh-group [mesh-group-name | none] {vr

vrname}

DescriptionThis command configures an MSDP peer to become a member of a mesh-group. To remove a peerfrom 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.




DefaultN/A.

Usage GuidelinesA mesh-group is a group of MSDP peers with fully meshed MSDP connectivity. Any SA messagesreceived 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 amember of a mesh-group called "intra":

configure msdp peer 192.168.45.43 mesh-group intra


Multicast Commands

Multicast 141


configure msdp peer no-default-peerconfigure msdp peer [remoteaddr | all] no-default-peer {vr vrname}

DescriptionThis command removes a default peer.

Syntax Description



no-default-peer Removes a default peer.


DefaultN/A.


ExampleThe following command removes all MSDP peers:

configure msdp peer all no-default-peer



Multicast Commands

Multicast 142



configure msdp peer passwordconfigure msdp peer [remoteaddr | all] password [none | {encrypted} tcpPassword]

{vr vrname}

DescriptionThis command configures a TCP RSA Data Security, Inc. MD5 Message-Digest Algorithm password foran MSDP peer.This command enables TCP RSA Data Security, Inc. MD5 Message-Digest Algorithmauthentication for a MSDP peer. When a password is configured, MSDP receives only authenticatedMSDP messages from its peers. All MSDP messages that fail TCP RSA Data Security, Inc. MD5 Message-Digest Algorithm authentication are dropped.

Syntax Description



none Removes the previously configured password.

encrypted Encrypts the password for RSA Data Security, Inc. MD5 Message-Digest Algorithmauthentication. To improve security, the password displays in encrypted format andcannot 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-DigestAlgorithm authentication at the TCP level. The password must be an ASCII string with amaximum of 31 characters.


DefaultsBy default, TCP RSA Data Security, Inc. MD5 Message-Digest Algorithm authentication is disabled forthe MSDP peer.

Usage GuidelinesWe recommend that you enable TCP RSA Data Security, Inc. MD5 Message-Digest Algorithmauthentication for all MSDP peers to protect MSDP sessions from attacks. You can execute thiscommand 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 Commands

Multicast 143

The following command removes the password:

configure msdp peer 192.168.45.43 password none



configure msdp peer sa-filterconfigure msdp peer [remoteaddr | all] sa-filter [in | out] [filter-name | none]

{vr vr_name}

DescriptionThis command configures an incoming or outgoing policy filter for SA messages.

Syntax Description



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 Specifies the name of the virtual router to which this command applies. If a name isnot specified, it is extracted from the current CLI context.

DefaultBy default, no SA filter is configured for an MSDP peer. That is, incoming and outgoing SA messagesare not filtered.

Usage GuidelinesThis command configures an SA filter such that only a specified set of SA messages are accepted orsent to a peer. Note that an SA filter does not adversely impact the flow of SA request and responsemessages.

To remove an SA filter, enter the none CLI keyword instead of filter-name.

Multicast Commands

Multicast 144


You can use the following policy attributes in an SA filter policy. All other attributes are ignored.

• Match:

• multicast-group


• pim-rp

• Set:

• permit

• deny

Example

The following example configures an incoming SA messages filter on an MSDP peer with the IP address192.168.45.43:

configure msdp peer 192.168.45.43 sa-filter in allow_229



configure msdp peer sa-limitconfigure msdp peer [remoteaddr | all] sa-limit max-sa {vr vr_name}

DescriptionThis command allows you to limit the number of SA entries from an MSDP peer that the router willallow in the SA cache. To allow an unlimited number of SA entries, use 0 (zero) as the value for max-sa.

Syntax Description



max-sa Specifies the maximum number of SA entries from an MSDP peer allowed in the SAcache. To specify an unlimited number of SA entries, use 0 (zero) as the value formax-sa.

vr_name Specifies the name of the virtual router to which this command applies. If a name isnot specified, it is extracted from the current CLI context.

Multicast Commands

Multicast 145


DefaultBy default, no SA entry limit is set. The router can receive an unlimited number of SA entries from anMSDP peer.

Usage GuidelinesYou can use this command to prevent a distributed denial of service (DOS) attack. We recommend thatyou configure an MSDP SA limit on all MSDP peer sessions. Note that a rejected SA cache entry is notincluded 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 address192.168.45.43:

configure msdp peer 192.168.45.43 sa-limit 500



configure msdp peer source-interfaceconfigure msdp peer [remoteaddr | all] source-interface [ipaddress | any] {vr

vrname}

DescriptionThis command configures the source interface for the MSDP peer TCP connection.

Syntax Description



ipaddress Specifies the IP address of the MSDP router interface to use on one end of a TCPconnection. The ipaddress must be one of the MSDP router interface addresses;otherwise, the command fails and an error message displays.

Multicast Commands

Multicast 146


any Specifies to use any interface as one end of the TCP connection. The sourceinterface 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 interfacefor the TCP connection. Basically, this command removes the previouslyconfigured source interface of the MSDP peer.

vrname Specifies the name of the virtual router to which this command applies. If a nameis not specified, it is extracted from the current CLI context.

DefaultsBy 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 GuidelinesYou must first disable MSDP or the MSDP peer before using this command. We recommend that youconfigure a source interface for MSDP peers that are not directly connected. We also recommend usingthe loopback address as the MSDP peer connection endpoint.

Example

The following example configures a source interface for an MSDP peer with the IP address192.168.45.43:

configure msdp peer 192.168.45.43 source-interface 60.0.0.5



configure msdp peer timerconfigure msdp peer [remoteaddr | all] timer keep-alive keep-alive-sec hold-time

hold-time-sec {vr vrname}

DescriptionThe command configures the keep-alive and hold timer intervals of the MSDP peers.

Multicast Commands

Multicast 147


Syntax Description



keep-alive-sec Specifies the keep-alive timer interval in seconds. The range is1–60 seconds.

hold-time-sec Specifies the hold timer interval in seconds. The range is 3–75 seconds.


DefaultBy default, the:

• Keep-alive timer interval is 60 seconds.

• Hold timer interval is 75 seconds.

• SA timer interval is 60 seconds.

Usage GuidelinesYou can use this command only when either MSDP or the MSDP peer is disabled. The hold timerinterval 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



configure msdp peer ttl-thresholdconfigure msdp peer [remoteaddr | all] ttl-threshold ttl {vr vrname}

DescriptionConfigures the limit to which multicast data packets are sent in SA messages to an MSDP peer. If thetime-to-live (TTL) in the IP header of an encapsulated data packet exceeds the TTL thresholdconfigured, encapsulated data is not forwarded to MSDP peers.

Multicast Commands

Multicast 148


Syntax Description

remoteaddr Specifies the IP address of the MSDP peer on which to configure a TTL threshold.

all Specifies all MSDP peers.

ttl Specifies the TTL value. The range is 0–255. To restore the default value, enter a TTLvalue of 0 (zero).


DefaultThe default value is zero, meaning all multicast data packets are forwarded to the peer regardless ofthe TTL value in the IP header of the encapsulated data packet.

Usage GuidelinesThis 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



configure msdp sa-cache-serverconfigure msdp sa-cache-server remoteaddr {vr vr_name}

DescriptionConfigures the MSDP router to send SA request messages to the MSDP peer when a new memberbecomes active in a group.

Multicast Commands

Multicast 149


Syntax Description

remoteaddr Specifies the IP address of the MSDP peer from which the local router requests SAmessages when a new member becomes active in a group, and MSDP has no cache entryfor the group in the local database.

vr_name Specifies the name of the virtual router on which the MSDP cache server is configured. If avirtual router name is not specified, it is extracted from the current CLI context.

DefaultBy default, the router does not send SA request messages to its MSDP peers when a new member joinsa group and wants to receive multicast traffic. The new member simply waits to receive SA messages,which eventually arrive.

Usage GuidelinesYou can use this command to force a new member of a group to learn the current active multicastsources in a connected PIM-SM domain that are sending to a group. The router will send SA requestmessages to the specified MSDP peer when a new member joins a group and MSDP doesn’t have acache entry for that group in the local database. The peer replies with the information in an SA cacheresponse message.

NoteAn MSDP peer must exist before it can be configured as an SA cache server. The configuremsdp sa-cache-server command accepts the value for remoteaddr only if it is an existingpeer’s IP address.

Example

The following example configures an MSDP cache server:

configure msdp sa-cache-server 172.19.34.5



configure mvr add receiverconfigure mvr vlan vlan-name add receiver port port-list

Multicast Commands

Multicast 150


DescriptionConfigures a port to receive MVR multicast streams.

Syntax Description

vlan-name Specifies a VLAN name.

port-list A list of ports or slots and ports.

DefaultN/A.

Usage GuidelinesThis 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 fromthe MVR cache egress list. This command is used to override these rules, so that if valid IGMPmemberships 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


Platform AvailabilityThis command is available on platforms that support the appropriate license. For complete informationabout software licensing, including how to obtain and upgrade your license and which licenses supportthe MVR feature, see the Feature License Requirements document.

configure mvr add vlanconfigure mvr add vlan vlan-name

DescriptionConfigures a VLAN as an MVR VLAN.

Multicast Commands

Multicast 151


Syntax Description


DefaultN/A.

Usage GuidelinesConfigures MVR on the specified VLAN. When a multicast stream in the specified MVR address range isreceived on the VLAN, it is leaked to all other VLAN ports where the corresponding IGMP join messageis received. By default, the entire multicast address range 224.0.0.0/4, except for the multicast controlrange 224.0.0.0/24 is used for MVR. To change the MVR address range, use the following command:

configure mvr vlan vlan-name mvr-address {policy-name | none}

Example

The following example configures VLAN v1 as an MVR VLAN:

configure mvr add vlan v1



configure mvr delete receiverconfigure mvr vlan vlan-name delete receiver port port-list

DescriptionConfigures a port not to receive MVR multicast streams.

Syntax Description


port-list A list of ports or slots and ports.

Multicast Commands

Multicast 152


DefaultN/A.

Usage GuidelinesThis command is used to delete a group of virtual ports for multicast forwarding through MVR. Afterusing 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



configure mvr delete vlanconfigure mvr delete vlan vlan-name

DescriptionDeletes a VLAN from MVR.

Syntax Description


DefaultN/A.

Usage GuidelinesRemoves MVR from the specified VLAN.

Multicast Commands

Multicast 153


Example

The following example configures VLAN v1 as a non-MVR VLAN:

configure mvr delete vlan v1



configure mvr mvr-addressconfigure mvr vlan vlan-name mvr-address {policy-name | none}

DescriptionConfigures the MVR address range on a VLAN.

Syntax Description


policy-name Specifies a policy file.

DefaultThe default address range is 224.0.0.0/4 (all multicast addresses), but excluding 224.0.0.0/24 (themulticast control range).

Usage GuidelinesIf no policy file is specified (the none option), the entire multicast address range 224.0.0.0/4, except forthe 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 fromfast path forwarding. This allows synching existing channels with the new policy, without disturbingexisting channels.

Multicast Commands

Multicast 154


The following is a sample policy file mvrpol.pol. This policy configures 236.1.1.0/24 as the MVR addressrange. 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 theVLAN v1:

configure mvr vlan v1 mvr-address mvrpol



configure mvr static groupconfigure mvr vlan vlan-name static group {policy-name | none}

DescriptionConfigures the MVR static group address range on a VLAN.

Syntax Description


policy-name Specifies a policy file.

DefaultBy default, all the MVR group addresses work in static mode.

Multicast Commands

Multicast 155


Usage GuidelinesIf no policy file is specified (the none option), the entire multicast address range 224.0.0.0/4, except forthe 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 staticgroup 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 themulticast 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 filemvrpol.pol for the VLAN v1:

configure mvr vlan v1 static group mvrpol



configure pim add vlanconfigure pim {ipv4 | ipv6} add vlan [vlan-name | all] {dense | sparse} {passive}

DescriptionConfigures an IP interface for PIM.

Multicast Commands

Multicast 156


Syntax Description

ipv4 Specifies the IPv4 address family.



all Specifies all VLANs.

dense Specifies PIM dense mode (PIM-DM).

sparse Specifies PIM sparse mode (PIM-SM).

passive Specifies a passive interface.

DefaultDense.

Usage GuidelinesWhen 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 orsparse 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 beforwarded to edge hosts. Since they do not peer with other PIM routers, you should not connect amulticast router to a passive interface.

In order for the interface to participate in PIM, PIM must be enabled on the switch using the followingcommand: enable pim

Example

The following example enables PIM-DM multicast routing on VLAN accounting:

configure pim add vlan accounting dense


The passive option was added in ExtremeXOS 11.1.

The IPv4 and IPv6 options were added in ExtremeXOS 15.3.

Multicast Commands

Multicast 157


configure pim borderconfigure pim {ipv4 | ipv6} [{vlan} vlan_name | vlan all] border

DescriptionConfigures 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.



vlan all Specifies all VLANs.

border Interface is domain border.

DefaultNone.

Usage GuidelinesMSDP is used to connect multiple multicast routing domains. A PIM-SM domain is created bylimitingthe reach of PIM BSR advertisements. When a border VLAN is configured, PIM BSRadvertisements 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


The ipv4 and ipv6 keywords were added giving an option to support this functionality in IPv6 as wellin ExtremeXOS 15.3.

Multicast Commands

Multicast 158


Platform AvailabilityThis command is available on platforms that support the appropriate license. For complete informationabout software licensing, including how to obtain and upgrade your license and which licenses supportthe PIM feature, see the ExtremeXOS User Guide.

configure pim cbsrconfigure pim cbsr {ipv4 | ipv6} [{vlan} vlan_name {priority [0-254]} | none]

DescriptionConfigures a candidate bootstrap router for PIM sparse-mode operation.

Syntax Description




priority Specifies a priority setting. The range is 0 - 254.

none Deletes a CBSR.

DefaultThe default setting for priority is 0, and indicates the lowest priority.

Usage GuidelinesThe VLAN specified for CBSR must have PIM enabled for it to take effect. After PIM is enabled, CBSRsadvertise themselves in the PIM domain. A bootstrap router (BSR) is elected among all the candidatesbased on CBSR priority. To break the tie among routers with the same priority setting, the router withthe 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 groupand 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


Multicast Commands

Multicast 159


configure pim crp staticconfigure pim {ipv4 | ipv6} crp static ip_address [none | policy] {priority

[0-254]}

DescriptionConfigures a rendezvous point and its associated groups statically, for PIM sparse mode operation.

Syntax Description



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.

DefaultThe default setting for priority is 0, which indicates highest priority.

Usage GuidelinesIn PIM-SM, the router sends a join message to the rendezvous point (RP). The RP is a central multicastrouter that is responsible for receiving and distributing multicast packets. If you use a static RP, allswitches 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 asingle RP policy file. If you configure more than 180 group entries in a single RP policy file, the switchwill 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 acontainer for a list of addresses. So a typical policy file used for RP configuration looks a little differentfrom a policy used for other purposes.

If routers have different group-to-RP mappings, due to misconfiguration of the static RP (or any otherreason), traffic is disrupted.

Multicast Commands

Multicast 160


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 ;}}



configure pim crp timerconfigure pim {ipv4 | ipv6} crp timer crp_adv_interval

DescriptionConfigures the candidate rendezvous point advertising interval in PIM sparse mode operation.

Syntax Description



crp_adv_interval Specifies a candidate rendezvous point advertising interval in seconds. Therange is 1 to 1,717,986,918.

DefaultThe default is 60 seconds.

Multicast Commands

Multicast 161


Usage GuidelinesIncreasing 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



configure pim crp vlanconfigure pim {ipv4 | ipv6} crp vlan vlan_name [none | policy] {priority}

DescriptionConfigures the dynamic candidate rendezvous point (CRP) for PIM sparse-mode operation.

Syntax Description




none Specifies to delete a CRP.


priority Specifies a priority setting. The range is 0–254.

DefaultThe default setting for priority is 0 and indicates the highest priority.

Usage GuidelinesExtremeXOS switches support up to 50 RPs in a switch, and up to 180 groups (group/mask entries) in asingle RP policy file. If you configure more than 180 group entries in single RP policy file, then the switchwill not process entries added after first 180.

Multicast Commands

Multicast 162


The policy file contains the list of multicast group addresses serviced by this RP. This set of groupaddresses are advertised as candidate RPs. Each router then elects the common RP for a groupaddress 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 acontainer for a list of addresses. So a typical policy file used for RP configuration looks a little differentfrom a policy used for other purposes. The following is a sample policy file that configures the CRP forthe 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 onthe 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



configure pim delete vlanconfigure pim delete vlan [vlanname | all]

DescriptionDisables PIM on a router interface.

Multicast Commands

Multicast 163


Syntax Description



DefaultN/A.


Example

The following example disables PIM on VLAN accounting:

configure pim delete vlan accounting



configure pim dr-priorityconfigure pim {ipv4 | ipv6} [ {vlan} vlan_name | vlan all ] dr-priority priority

DescriptionConfigures 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 1–4294967295.

Multicast Commands

Multicast 164


DefaultThe default setting for dr-priority is 1.

Usage GuidelinesThe dr-priority option allows a network administrator to give preference to a particular router in theDR election process by giving it a numerically larger DR priority. The dr-priority option is included inevery hello message, even if no DR priority is explicitly configured on that interface. This is necessarybecause priority-based DR election is only enabled when all neighbors on an interface advertise thatthey 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. Arouter's idea of the current DR on an interface can change when a PIM hello message is received, whena neighbor times out, or when a router's own DR priority changes. If the router becomes the DR orceases 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 asfollows:

• If any one of the neighbor on the interface is not advertised the DR priority (not DR capable) thenDR priority will not considered for the all the neighbors in the circuit, and the primary IP address willbe 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



configure pim iproute sharing hashconfigure pim {ipv4 | ipv6} iproute sharing hash [source | group | source-group |

source-group-nexthop]

DescriptionThis command is used to configure the PIM ECMP hash algorithm.

Multicast Commands

Multicast 165


Syntax Description



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 hopaddresses (default).

DefaultSource-group-nexthop.


Example

The following command configures the PIM ECMP hash algorithm based on source-group-nexthop:

configure pim ipv6 iproute sharing hash source-group-nexthop


Platform AvailabilityThis command is available on platforms that support the appropriate license. All platforms exceptSummit X440 support IP route sharing in ExtremeXOS 15.3.2. For complete information about softwarelicensing, 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 rpconfigure pim {ipv4 | ipv6} register-policy rp [rp_policy_name | none]

DescriptionConfigures the register filter at the Rendezvous Point.

Multicast Commands

Multicast 166


Syntax Description



rp_policy_name Specifies the Policy File for RP Register filter.

none Unconfigures the configured RP Register filter.

DefaultN/A.


Example

The following example configures IPv4 register policy named "entry_policy":

configure pim ipv4 register-policy rp entry_policy



configure pim register-policyconfigure pim {ipv4 | ipv6} register-policy [rp_policy_name | none]

DescriptionConfigures the register filter at the First Hop Router (FHR).

Syntax Description



rp_policy_name Specifies the Policy File for Register filter.

none Unconfigures the configured RP Register filter.

Multicast Commands

Multicast 167


DefaultIPv4.


Example

The following example configures an IPv4 register policy named "entry_policy" at the FHR:

configure pim ipv4 register-policy entry_policy



configure pim register-checksum-to

configure pim {ipv4 | ipv6} register-checksum-to [include-data | exclude-data]

DescriptionConfigures the checksum computation to either include data (for compatibility with Cisco Systemsproducts) or to exclude data (for RFC-compliant operation), in the register message.

Syntax Description



include-data Specifies to include data.

exclude-data Specifies to exclude data.

DefaultExclude data.

Multicast Commands

Multicast 168



Example

The following example configures the checksum mode to include data for compatibility with CiscoSystems products:

configure pim register-checksum-to include-data



configure pim register-rate-limit-intervalconfigure pim {ipv4 | ipv6} register-rate-limit-interval interval

DescriptionConfigures the initial PIM-SM periodic register rate.

Syntax Description



interval Specifies an interval time in seconds. Range is 0 - 60. Default is 0.

DefaultThe default interval is 0.

Usage GuidelinesConfiguring a non-zero interval time can reduce the CPU load on the first hop switch, in case registerstop messages are not received normally.

When a non-zero value is configured, the first hop switch sends a few register messages and then waitsfor a corresponding register stop from the RP for time seconds. The process is repeated until the

Multicast Commands

Multicast 169


register stop is received. This command should be used when the (S,G) tree between the first hoprouter and the RP is not converging quickly.

When the default value is zero in default mode, the switch sends continuous register messages until theregister stop is received.

Example

The following example configures the initial PIM register rate limit interval:

configure pim register-rate-limit-interval 2



configure pim register-suppress-interval register-probe-intervalconfigure pim {ipv4 | ipv6} register-suppress-interval reg-interval register-

probe-interval probe_interval

DescriptionConfigures an interval for periodically sending null-registers.

Syntax Description



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.

DefaultThe following defaults apply:

• register-suppress-interval—60

• register-probe-interval—5

Multicast Commands

Multicast 170


Usage GuidelinesThe 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). Aresponse to the null register is expected within register probe interval. By specifying a larger interval, aCPU peak load can be avoided because the null-registers are generated less frequently. The registerprobe 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



configure pim shutdown-priorityconfigure pim {ipv4 | ipv6} [ {vlan} vlan_name | vlan all ] shutdown-priority

number

DescriptionConfigures the priority for out of memory shutdown.

Syntax Description





number Priority for VLAN range is [0 - 65535].

DefaultIPv4.

Multicast Commands

Multicast 171



Example

The following example configures the shutdown priority for VLAN 36:

config pim vlan v36 shutdown-priority 22


The ipv4 and ipv6 keywords were added giving an option to support this functionality in IPv6 as wellin ExtremeXOS 15.3.


configure pim spt-thresholdconfigure pim {ipv4 | ipv6} spt-threshold leaf-threshold {rp_threshold}

DescriptionConfigures the threshold, in kbps, for switching to SPT. On leaf routers, this setting is based on datapackets. On the RP, this setting is based on register packets.

Syntax Description



leaf-threshold Specifies the rate of traffic per (s,g,v) group in kbps for the last hop. Range is0 - 419403.

rp_threshold Specifies an RP threshold. Range is 0 - 419403.

DefaultThe default setting is 0 for both parameters.

Usage GuidelinesFor the best performance, use default value of 0.

Multicast Commands

Multicast 172


Example

The following example changes the threshold for switching to SPT:

configure pim spt-threshold 4 16



configure pim ssm rangeconfigure pim {ipv4 | ipv6} ssm range [default | policy policy-name]

DescriptionConfigures the range of multicast addresses for PIM SSM.

Syntax Description



default Specifies the default address range, 232.0.0.0/8.

policy-name Specifies a policy that defines the SSM address range.

DefaultBy default, no SSM range is configured. Using this command with the default keyword sets the range to232.0.0.0/8. To reset the switch to the initial state, use the unconfigure pim ssm rangecommand.

Usage GuidelinesYou must disable PIM before configuring or unconfiguring a PIM-SSM range. Use the disable pimcommand.

Initially, no range is configured for SSM. After a range is configured, you can remove the range with theunconfigure pim ssm range command. If you wish to change the PIM SSM range, you must firstunconfigure the existing range, and then configure the new range.

Multicast Commands

Multicast 173


SSM requires that hosts use IGMPv3 messages to register to receive multicast group packets. When arange is configured for SSM, any IGMPv2 messages for an address in the range are ignored. Also, anyIGMPv3 Exclude messages are ignored.

NoteIf a PIM-SSM range is configured, IGMPv2 messages and IGMPv3 exclude messages within thePIM-SSM range are ignored on all IP interfaces, whether or not PIM-SSM is configured on theinterfaces.

To specify a range different from the default PIM SSM range, create a policy file. The match statementof the policy file contains the group addresses to be treated as PIM SSM addresses. For example, tospecify 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 filessmrange.pol contains the policy example used above:

configure pim ssm range policy ssmrange.pol



configure pim ssm

configure pim {ipv4 | ipv6} [{vlan} vlan_name | vlan all

DescriptionConfigures PIM on an IPv4 or IPv6 router interface.

Multicast Commands

Multicast 174


Syntax Description

ipv4 Configures PIM functionality on IPv4 router interfaces.




DefaultN/A.

Usage GuidelinesYou must disable PIM before configuring or unconfiguring a PIM-SSM range.

Example

The following command sets:

configure pim


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-intervalconfigure pim state-refresh timer origination-interval interval

DescriptionConfigures the interval at which state refresh messages are originated.

Syntax Description

interval Specifies a refresh interval in seconds. The range is 30–90 seconds.

Multicast Commands

Multicast 175


Default60 seconds.


Example

The following example configures the interval to 45 seconds:

configure pim state-refresh timer origination-interval 45



configure pim state-refresh timer source-active-timerconfigure pim {ipv4 | ipv6} state-refresh timer source-active-timerinterval

DescriptionDefines how long a multicast source (S,G) is considered active after a packet is received from thesource.

Syntax Description



interval Specifies a source-active timer interval in seconds. The range is 90–300seconds.

Default210 seconds.


Multicast Commands

Multicast 176


Example

The following example configures the interval to 45 seconds:

configure pim state-refresh timer source-active-timer 180



configure pim state-refresh ttl

configure pim {ipv4 | ipv6} state-refresh ttl ttlvalue

DescriptionConfigures a time-to-live (TTL) value for PIM-DM state refresh messages.

Syntax Description



ttl_value Specifies a TTL value. The range is 1–64.

Default16.


Example

The following example configures the TTL value for 24:

configure pim state-refresh ttl 24

Multicast Commands

Multicast 177




configure pim state-refreshconfigure pim {ipv4 | ipv6} state-refresh {vlan} [vlan_name | all] [on | off]

DescriptionEnables or disables the PIM-DM state refresh feature on one or all VLANs.

Syntax Description



vlan_name Specifies a VLAN on which to enable or disable the PIM-DM state refreshfeature.

on Enables the PIM-DM state refresh feature on the specified VLANs.

off Disables the PIM-DM state refresh feature on the specified VLANs.

DefaultDisabled.

Usage GuidelinesWhen 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 Commands

Multicast 178




configure pim timer vlanconfigure pim {ipv4 | ipv6} timer hello_interval jp_interval [{vlan} vlan_name |

vlan all]

DescriptionConfigures the global PIM timers on the specified router interfaces.

Syntax Description



hello_interval Specifies the amount of time before a hello message is sent out by the PIMrouter. The range is 1–65,535 seconds.

jp_interval Specifies the join/prune interval. The range is 1–65,535 seconds.



Default

• hello_interval—30 seconds

• jp_interval—60 seconds

Usage GuidelinesThese default timers should only be adjusted when excess PIM control packets are observed on theinterface.

Example

The following example configures the PIM timers on the VLAN accounting:

configure pim timer 150 300 vlan accounting

Multicast Commands

Multicast 179




configure pim vlan trusted-gatewayconfigure pim {ipv4 | ipv6} [{vlan} vlan_name | vlan all ] trusted-gateway

[policy | none]

DescriptionConfigures a trusted neighbor policy.

Syntax Description






none Specifies no policy file, so all gateways are trusted.

DefaultNo policy file, so all gateways are trusted.

Usage GuidelinesBecause PIM leverages the unicast routing capability that is already present in the switch, the accesspolicy capabilities are, by nature, different. When the PIM protocol is used for routing IP multicasttraffic, the switch can be configured to use a policy file to determine trusted PIM router neighbors forthe 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 Commands

Multicast 180




create msdp mesh-groupcreate msdp mesh-group mesh-group-name {vr vrname}

DescriptionCreates an MSDP mesh-group.

Syntax Description

mesh-group-name Specifies the name for the MSDP mesh-group.


DefaultN/A.

Usage GuidelinesA 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 samemesh-group, which reduces SA message flooding.

A mesh group name must begin with an alphabetical character and may contain alphanumericcharacters and underscores ( _ ), but it cannot contain spaces. The maximum allowed length for aname 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 Commands

Multicast 181




create msdp peercreate msdp peer remoteaddr {remote-as remote-AS} {vr vrname}

DescriptionCreates 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 optionalparameter is deprecated in ExtremeXOS 12.1, though the option is still available in the CLIfor backward compatibility. The software ignores this parameter.


DefaultN/A.

Usage GuidelinesThe BGP route database is used by MSDP to determine the AS number for the peer. You can displaythe 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


Multicast Commands

Multicast 182



delete msdp mesh-groupdelete msdp mesh-group mesh-group-name {vr vrname}

DescriptionRemoves an MSDP mesh-group.

Syntax Description

mesh-group-name Specifies the name of the MSDP mesh-group. The character string can be amaximum of 31 characters.


DefaultN/A.

Usage GuidelinesA mesh-group is a group of MSDP peers with fully meshed MSDP connectivity. Mesh-groups are usedto achieve two goals:



SA messages received from a peer in a mesh-group are not forwarded to other peers in the samemesh-group.

Use the delete msdp mesh-group command only if you created a mesh-group that you want toremove. By default, there is no MSDP mesh-group.

Example

The following example removes a mesh-group called "verizon":

delete msdp mesh-group verizon


Multicast Commands

Multicast 183



delete msdp peerdelete msdp peer [all | remoteaddr] {vr vr_name}

DescriptionDeletes 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 Specifies the name of the virtual router to which this command applies. If a name is notspecified, it is extracted from the current CLI context.

DefaultN/A.


Example

The following example deletes an MSDP peer:

delete msdp peer 192.168.45.43



Multicast Commands

Multicast 184



disable igmp snooping vlan fast-leavedisable igmp snooping {vlan} name fast-leave

DescriptionDisables the IGMP snooping fast leave feature on the specified VLAN.

Syntax Description

name Specifies a VLAN.

DefaultDisabled.


Example

The following command disables the IGMP snooping fast leave feature on the default VLAN:

disable igmp snooping “Default” fast-leave



disable igmp snoopingdisable igmp snooping {forward-mcrouter-only | with-proxy | vlan name}

DescriptionDisables IGMP snooping.

Multicast Commands

Multicast 185


Syntax Description

forward-mcrouter-only Specifies that the switch forwards all multicast traffic to the multicast routeronly.

with-proxy Disables the IGMP snooping proxy.


DefaultIGMP snooping and the with-proxy option are enabled by default, but forward-mcrouter-only option isdisabled by default.

Usage GuidelinesIf a VLAN is specified, IGMP snooping is disabled only on that VLAN, otherwise IGMP snooping isdisabled 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 snoopingforward-mcrouter-only changes the mode so that all multicast traffic is forwarded to any IProuter. If not in the forward-mcrouter-mode, the command disable igmp snooping forward-mcrouter-only has no effect.

To change the snooping mode you must disable IP multicast forwarding. Use the command: disableipmcforwarding

The with-proxy option can be used for troubleshooting purpose. It should be enabled for normalnetwork operation.

Enabling the proxy allows the switch to suppress the duplicate join requests on a group to forward tothe connected Layer 3 switch. The proxy also suppresses unnecessary IGMP leave messages so thatthey 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



Multicast Commands

Multicast 186


disable igmp ssm-mapdisable igmp ssm-map {vr vr-name}

DescriptionDisables IGMP SSM mapping.

Syntax Description

vr-name Specifies a virtual router name. If the VR name is omitted, the switch disablesmapping on the VR specified by the current CLI VR context.

DefaultDisabled on all interfaces.


Example

The following command disables IGMP-SSM mapping on the VR in the current CLI VR context:

disable igmp ssm-map



disable igmpdisable igmp {vlan name}

DescriptionDisables IGMP on a router interface. If no VLAN is specified, IGMP is disabled on all router interfaces.

Multicast Commands

Multicast 187


Syntax Description


DefaultEnabled.

Usage GuidelinesIGMP 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 stillactive, 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 thegeneration and processing of IGMP packets. IGMP should be enabled when the switch is configured toperform IP multicast routing.

This command disables IGMPv2 and IGMPv3.

Example

The following example disables IGMP on VLAN accounting:

disable igmp vlan accounting



disable ipmcforwarding ipv6disable ipmcforwarding ipv6 {{vlan} name}

DescriptionDisables IPv6 multicast forwarding on a router interface.

Syntax Description


Multicast Commands

Multicast 188


DefaultDisabled.

Usage GuidelinesIf no options are specified, all configured IPv6 interfaces are affected. When new IPv6 interfaces arecreated, IPv6 multicast forwarding is disabled by default.

Disabling IPv6 multicast forwarding disables any Layer 3 IPv6 multicast routing for the streams comingto the interface.

Example

The following example disables IPv6 multicast forwarding on VLAN accounting:

disable ipmcforwarding ipv6 vlan accounting



disable ipmcforwardingdisable ipmcforwarding {vlan name}

DescriptionDisables IP multicast forwarding on a router interface.

Syntax Description


DefaultDisabled.

Multicast Commands

Multicast 189


Usage GuidelinesIf 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 theinterface.

Example

The following example disables IP multicast forwarding on the VLAN accounting:

disable ipmcforwarding vlan accounting



disable mlddisable mld {vlan name}

DescriptionDisables MLD on a router interface. If no VLAN is specified, MLD is disabled on all router interfaces.

Syntax Description


DefaultDisabled.

Usage GuidelinesMLD is a protocol used by an IPv6 host to register its IPv6 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 stillactive, hosts respond to the query, and group registration is maintained.

Multicast Commands

Multicast 190


MLD is disabled by default on the switch. However, the switch can be configured to enable thegeneration and processing of MLD packets. MLD should be enabled when the switch is configured toperform IPv6 unicast or IPv6 multicast routing.

This command disables all MLD versions. When MLD is disabled, the MLDv2 compatibility mode settingis lost. If compatibility mode is not specified in the command when MLD is enabled again, MLDv1compatibility mode is set.

Example

The following example disables MLD on VLAN accounting:

disable mld vlan accounting



disable mld snoopingdisable mld snooping {with-proxy | vlan name}

DescriptionDisables MLD snooping.

Syntax Description

with-proxy Disables the MLD snooping proxy.


DefaultThe with-proxy option is enabled by default, but MLD snooping and forward-mcrouter-only option isdisabled by default.

Usage GuidelinesIf a VLAN is specified, MLD snooping is disabled only on that VLAN, otherwise MLD snooping isdisabled on all VLANs.

Multicast Commands

Multicast 191



The with-proxy option can be used for troubleshooting purpose. It should be enabled for normalnetwork operation.

Enabling the proxy allows the switch to suppress the duplicate join requests on a group to forward tothe connected Layer 3 switch. The proxy also suppresses unnecessary MLD done messages so thatthey are forwarded only when the last member leaves the group.

Example

The following example disables MLD snooping on the VLAN accounting:

disable mld snooping accounting



disable mld-ssm mapdisable mld-ssm map {{vr} vr_name}

DescriptionDisables MLD SSM mapping on a VR.

Syntax Description

vr vr_name Specifies a virtual router name.

DefaultDisabled.

Usage GuidelinesUse this command to disable MLD SSM mapping on a VR.

Enabling or disabling SSM Mapping when PIMv6 is enabled throws the following error:


Multicast Commands

Multicast 192



Example

The following example disables SSM mapping on VR1:

disable mld-ssm map vr vr1



disable msdp data-encapsulation

disable msdp data-encapsulation {vr vrname}

DescriptionDisables the encapsulation of locally originated SA messages with multicast data (if available).

Syntax Description


DefaultBy default, multicast data packet encapsulation is enabled for locally originated SA messages.


ExampleThe following command disables multicast data packet encapsulation:

disable msdp data-encapsulation


Multicast Commands

Multicast 193




disable msdp export local-sa

disable msdp export local-sa {vr vrname}

DescriptionDisables the advertisement of local sources to groups for which the router is an RP.

Syntax Description


DefaultBy default, the export of local sources is enabled. All sources are advertised if the router is an RP for thegroups. Use this command to disable it.

Usage GuidelinesYou can create a policy to filter out some of the local sources so that they are not advertised to MSDPpeers and exposed to the external multicast domain. To configure an export filter, you must first disablethe export of local sources (with the disable msdp export local-sa command), and then re-enable it with an export filter (with the enable msdp export local-sa export-filtercommand).

Example

The following example disables the advertisement of local sources:

disable msdp export local-sa



Multicast Commands

Multicast 194



disable msdp peerdisable msdp [{peer} remoteaddr | peer all] {vr vr_name}

DescriptionConfigures 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.


DefaultBy default, MSDP peers are disabled.

Usage GuidelinesUse 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



disable msdp process-sa-requestdisable msdp [{peer} remoteaddr | peer all] process-sa-request {vr vrname}

Multicast Commands

Multicast 195


DescriptionThis command configures a router to reject SA request messages from a specified peer or all peers.

Syntax Description




DefaultBy default, all SA request messages are accepted from all peers.

Usage GuidelinesUse this command to configure the router to reject SA request messages from a specified peer or allpeers.

You cannot change an SA request filter while SA request processing is enabled for an MSDP peer. Youmust 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


• pim-rp

• Set:

• permit

• deny

Example

The following example disables processing of SA request messages received from a peer with the IPaddress 192.168.45.43:

disable msdp peer 192.168.45.43 process-sa-request


Multicast Commands

Multicast 196


disable msdp

disable msdp {vr vrname}

DescriptionDisables MSDP on a virtual router.

Syntax Description

vrname Specifies the name of the virtual router on which MSDP is being enabled or disabled. If aname is not specified, it is extracted from the current CLI context.

DefaultMSDP is disabled by default.

Usage GuidelinesUse this command to disable MSDP on a virtual router.

Example

The following command disables MSDP on a virtual router:

disable msdp



disable mvr

disable mvr

Multicast Commands

Multicast 197



DescriptionDisables MVR on the system.

Syntax DescriptionThis command has no arguments or variables.

DefaultDisabled.


Example

The following example disables MVR on the system:

disable mvr



disable pim iproute sharingdisable pim {ipv4 | ipv6} iproute sharing

DescriptionDisables the PIM Equal Cost Multi Path (ECMP) feature.

Syntax Description

iproute IP Route

sharing Equal Cost Multipath Routing

Multicast Commands

Multicast 198


DefaultDisabled.


Example

The following command disables the PIM ECMP feature:

disable pim ipv4 iproute sharing


Platform AvailabilityThis command is available on platforms that support the appropriate license. All platforms exceptSummit X440 support IP route sharing in the ExtremeXOS 15.3.2 release. For complete informationabout software licensing, including how to obtain and upgrade your license and which licenses supportthe PIM feature, see the Feature License Requirements document.

disable pim snooping

disable pim snooping {{vlan} name}

DescriptionDisables PIM snooping and clears all the snooping PIM neighbors, joins received on the VLAN, and theforwarding entries belonging to one or all VLANs.

Syntax Description


DefaultDisabled.


Multicast Commands

Multicast 199


Example

The following command disables PIM snooping for all VLANs on the switch:

disable pim snooping



disable pim ssm vlandisable pim {ipv4 | ipv6} ssm vlan [vlan_name | all]

DescriptionDisables PIM SSM on a router interface.

Syntax Description






Usage GuidelinesThis 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-SSMis enabled on the interface. Any non-IGMPv3 messages in the SSM range are not processed by PIM onany switch interface, whether SSM is enabled or not.

Multicast Commands

Multicast 200


Example

The following example disables PIM-SSM multicast routing on VLAN accounting:

disable pim ssm vlan accounting



disable pim

disable pim {ipv4 | ipv6}

DescriptionDisables PIM on the system.

Syntax Description



priority Specifies a priority setting. The range is 0–254.

DefaultDisabled.


Example

The following example disables PIM on the system:

disable pim

Multicast Commands

Multicast 201




enable igmp snooping vlan fast-leaveenable igmp snooping {vlan} name fast-leave

DescriptionEnables the IGMP snooping fast leave feature on the specified VLAN.

Syntax Description


DefaultDisabled.

Usage GuidelinesThe fast leave feature operates only with IGMPv2.

To view the fast leave feature configuration, use the show configuration msmgr command. Thisshow 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


Multicast Commands

Multicast 202



enable igmp snooping with-proxyenable igmp snooping with-proxy

DescriptionEnables the IGMP snooping proxy. The default setting is enabled.


DefaultEnabled.

Usage GuidelinesEnabling the proxy allows the switch to suppress the duplicate join requests on a group to forward tothe connected Layer 3 switch. The proxy also suppresses unnecessary IGMP leave messages so thatthey are forwarded only when the last member leaves the group.

This command can be used for troubleshooting purpose. It should be enabled for normal networkoperation. 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:

enable igmp snooping with-proxy



Multicast Commands

Multicast 203



enable igmp snooping

enable igmp snooping {forward-mcrouter-only | {vlan} name | with-proxy vr vrname}

DescriptionEnables IGMP snooping on one or all VLANs.

Syntax Description

forward-mcrouter-only Specifies that the switch forward all multicast traffic to themulticast 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 thespecified virtual router. If this option is specified, one join messageper query is forwarded, and a leave message is forwarded only if itis from the last receiver on the VLAN.

DefaultEnabled.

Usage GuidelinesThis command applies to both IGMPv2 and IGMPv3.

IGMP snooping is enabled by default on the switch. If you are using multicast routing, IGMP snoopingcan be enabled or disabled. If IGMP snooping is disabled, all IGMP and IP multicast traffic floods within agiven VLAN or VMAN.

The forward-mcrouter-only, vlan, and with-proxy options control three separate andindependent features. You can manage one feature at a time with this command, and you can enter thecommand multiple times as needed to control each feature. For example, you can enter the commandtwice 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 VLANor VMAN. If no options are specified, IGMP snooping is enabled on all VLANs.

NoteIGMP 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 andleave messages forwarded on the virtual router as described in the table above. This feature is enabledby default.

An optional optimization for IGMP snooping is the strict recognition of routers only if the remotedevices are running a multicast protocol. Two IGMP snooping modes are supported:

• The forward-mcrouter-only mode forwards all multicast traffic to the multicast router (that is,the router running PIM, DVMRP or CBT).

Multicast Commands

Multicast 204

• When not in the forward-mcrouter-only mode, the switch forwards all multicast traffic to any IProuter (multicast or not), and any active member port to the local network that has one or moresubscribers.

NoteThe forward-mcrouter-only mode for IGMP snooping is enabled/disabled on a switch-wide basis, not on a per-VLAN basis. In other words, all the interfaces enabled for IGMPsnooping are either in the forward-mcrouter-only mode or in the non-forward-mcrouter-only mode, and not a mixture of the two modes.

To change the snooping mode you must disable IP multicast forwarding. To disable IP multicastforwarding, use the command:

disable ipmcforwarding {vlan name}

To change the IGMP snooping mode from the non-forward-mcrouter-only mode to the forward-mcrouter-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-forward-mcrouter-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:

enable igmp snooping



enable igmp ssm-map

enable igmp ssm-map {vr vr-name}

DescriptionEnables IGMP SSM mapping on a VR.

Multicast Commands

Multicast 205


Syntax Description



Usage GuidelinesConfigure the range of multicast addresses for PIM SSM before you enable IGMP SSM mapping. IGMPSSM 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



enable igmpenable igmp {vlan vlan name } {IGMPv1 | IGMPv2 | IGMPv3}

DescriptionEnables IGMP on a router interface. If no VLAN is specified, IGMP is enabled on all router interfaces.

Syntax Description

vlan name Specifies a VLAN name.

IGMPv1 Specifies the compatibility mode as IGMPv1.



Multicast Commands

Multicast 206


DefaultEnabled, set to IGMPv2 compatibility mode.

Usage GuidelinesIGMP 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 stillactive, 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 thegeneration and processing of IGMP packets. IGMP should be enabled when the switch is configured toperform 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


The IGMPv1, IGMPv2, and IGMPv3 options were added in ExtremeXOS 11.2.


enable ipmcforwarding ipv6enable ipmcforwarding ipv6 {vlan name }

DescriptionEnables IPv6 multicast forwarding on a router interface.

Syntax Description


Multicast Commands

Multicast 207


DefaultDisabled.

Usage GuidelinesIf no options are specified, all configured IPv6 interfaces are affected. When new IPv6 interfaces arecreated, 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



enable ipmcforwardingenable ipmcforwarding {vlan name}

DescriptionEnables IP multicast forwarding on an IP interface.

Syntax Description


DefaultDisabled.

Usage GuidelinesIf no options are specified, all configured IP interfaces are affected. When new IP interfaces are added,IPMC forwarding is disabled by default.

Multicast Commands

Multicast 208


IP forwarding must be enabled before enabling IPMC forwarding.

Example

The following example enables IPMC forwarding on the VLAN accounting:

enable ipmcforwarding vlan accounting



enable mldenable mld {vlan vlan_name {MLDv1 | MLDv2}

DescriptionEnables MLD on a router interface. If no VLAN is specified, MLD is enabled on all router interfaces.

Syntax Description


MLDv1 Sets the compatibility mode to MLDv1.

MLDv2 Sets the compatibility mode to MLDv2.

DefaultDisabled.

Usage GuidelinesMLD is a protocol used by an IPv6 host to register its IPv6 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 stillactive, 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 thegeneration 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 Commands

Multicast 209


Example

The following example enables MLDv1 on the VLAN accounting:

enable mld vlan accounting



enable mld snooping with-proxyenable mld snooping with-proxy

DescriptionEnables the MLD snooping proxy.


DefaultEnabled.

Usage GuidelinesEnabling the proxy allows the switch to suppress the duplicate join requests on a group to forward tothe connected Layer 3 switch. The proxy also suppresses unnecessary MLD leave messages so thatthey are forwarded only when the last member leaves the group.

This command can be used for troubleshooting purpose. It should be enabled for normal networkoperation. The command does not alter the snooping setting.

Example

The following command enables the MLD snooping proxy:

enable mld snooping with-proxy

Multicast Commands

Multicast 210





enable mld snoopingenable mld snooping vlan name

DescriptionEnables MLD snooping on the switch.

Syntax Description


DefaultDisabled.

Usage GuidelinesIf a VLAN is specified, MLD snooping is enabled only on that VLAN, otherwise MLD snooping is enabledon 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



Multicast Commands

Multicast 211





enable mld-ssm mapenable mld-ssm map {{vr} vr_name}

DescriptionEnables MLD SSM mapping on a virtual router (VR).

Syntax Description

vr vr_name Specifies a virtual router name.

DefaultDisabled.

Usage GuidelinesUse 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



enable msdp data-encapsulationenable msdp data-encapsulation {vr vrname}

Multicast Commands

Multicast 212



DescriptionEnables the encapsulation of locally originated SA messages with multicast data (if available).

Syntax Description


DefaultBy default, multicast data packet encapsulation is enabled for locally originated SA messages. Multicastdata packets with a packet size of up to 8 KB are encapsulated in SA messages.

Usage GuidelinesEnable data encapsulation to handle bursty sources.

Example

The following command enables multicast data packet encapsulation:

enable msdp data-encapsulation



enable msdp export local-saenable msdp export local-sa {export-filter filter-name} {vr vrname}

DescriptionEnables the advertisement of local sources to groups for which the router is an RP.

Multicast Commands

Multicast 213


Syntax Description

filter-name Specifies the policy to associate with the export of local sources. No policy is specified bydefault.


DefaultBy default, the export of local sources is enabled. All sources are advertised if the router is an RP for thegroups.

Usage GuidelinesYou can create a policy to filter out some of the local sources so that they are not advertised to MSDPpeers and exposed to the external multicast domain. To configure an export filter, you must first disablethe export of local sources (with the disable msdp export local-sa command), and then re-enable it with an export filter (with the enable msdp export local-sa export-filtercommand).

You can use the following policy attributes in an export policy. All other attributes are ignored.

• Match:

• multicast-group


• pim-rp

• Set:

• permit

• deny

Please note that the syntax for “multicast-group”, “multicast-source,” and “pim-rp” are the same as forthe “nlri” policy attribute.

[multicast-group | multicast-source | pim-rp] [<ipaddress> | any]/<mask-length> {exact}[multicast-group | multicast-source | pim-rp] [<ipaddress> | any] mask <mask> {exact}

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-group 239.0.0.0/8;

Multicast Commands

Multicast 214

multicast-source 23.123.45.0/24;} then {deny;}}entry allow_external_rp_172 {if {multicast-group 234.172.0.0/16;} then {permit}}# deny remaining entries

Example

The following command enables the advertisement of local sources:

nable msdp export local-sa



enable msdp peerenable msdp [{peer} remoteaddr | peer all] {vr vr_name}

DescriptionConfigures 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 Specifies the name of the virtual router to which this command applies. If a nameis not specified, it is extracted from the current CLI context.

DefaultBy default, MSDP peers are disabled.

Multicast Commands

Multicast 215


Usage GuidelinesYou must use this command to administratively enable the MSDP peers before they can establishpeering sessions and start exchanging SA messages.

Example

The following example enables an MSDP peer:

enable msdp peer 192.168.45.43



enable msdp process-sa-requestenable msdp [{peer} remoteaddr | peer all] process-sa-request {sa-request-filter

filter-name } {vr vr_name}

DescriptionThis command configures MSDP to receive and process SA request messages from a specified peer orall peers. If an SA request filter is specified, only SA request messages from those groups permitted areaccepted. All others are ignored.

Syntax Description


filter-name Specifies the name of the policy filter associated with SA request processing.


vr_name Specifies the name of the virtual router to which this command applies. If aname is not specified, it is extracted from the current CLI context.

DefaultBy default, all SA request messages are accepted from peers.

Multicast Commands

Multicast 216


Usage GuidelinesUse this command to configure the router to accept all or just some SA request messages from peers. Ifno policy is specified, all SA request messages are accepted. If a policy is specified, only SA requestmessages 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. Youmust 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


• pim-rp

• Set:

• permit

• deny

Example

The following example enables processing of SA request messages received from a peer with the IPaddress 192.168.45.43:

enable msdp peer 192.168.45.43 process-sa-request sa-request-filter intra_domain



enable msdp

enable msdp {vr vrname}

DescriptionEnables MSDP on a virtual router.

Multicast Commands

Multicast 217


Syntax Description

vrname Specifies the name of the virtual router on which MSDP is being enabled or disabled. If aname is not specified, it is extracted from the current CLI context.

DefaultMSDP is disabled by default.


Example

The following command enables MSDP on a virtual router:

enable msdp



enable mvr

enable mvr

DescriptionEnables MVR on the system.

Syntax DescriptonThis command has no arguments or variables.

DefaultDisabled.

Multicast Commands

Multicast 218



Example

The following command enables MVR on the system:

enable mvr



enable pim iproute sharingenable pim {ipv4 | ipv6} iproute sharing

DescriptionEnables the PIM Equal Cost Multi Path (ECMP) feature.

Syntax Description

iproute IP Route.

sharing Equal Cost Multipath Routing.

DefaultDisabled.

Usage GuidelinesUse this feature to allow downstream PIM router to choose multiple ECMP path to source via hash fromone of the following selections without affecting the existing unicast routing algorithm:

• Source

• Group

• Source-Group

• Source-Group-Next-Hop

Multicast Commands

Multicast 219


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 criteriadefined 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


Platform AvailabilityThis command is available on platforms that support the appropriate license. All platforms exceptSummit X440 support IP route sharing in the ExtremeXOS 15.3.2 release. For complete informationabout software licensing, including how to obtain and upgrade your license and which licenses supportthe PIM feature, see the Feature License Requirements document.

enable pim snoopingenable pim snooping {{vlan} name}

DescriptionEnables PIM snooping on one or all VLANs.

Syntax Description


DefaultDisabled.

Usage GuidelinesPIM snooping does not require PIM to be enabled. However, IGMP snooping must be disabled onVLANs 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 Commands

Multicast 220


Example

The following example enables PIM snooping on the default VLAN:

enable pim snooping default



enable pim ssm vlanenable pim {ipv4 | ipv6} ssm vlan [vlan_name | all]

DescriptionEnables PIM SSM on an IP interface.

Syntax Description






Usage GuidelinesThis 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 IPmulticast forwarding).

IGMPv3 include messages for multicast addresses in the SSM range are only processed by PIM if PIM-SSM is enabled on the interface. Any non-IGMPv3 include messages in the SSM range are not processedby PIM on any switch interface, whether SSM is enabled or not.

Multicast Commands

Multicast 221


Example

The following example enables PIM-SSM multicast routing on VLAN accounting:

enable pim ssm vlan accounting



enable pim

enable pim {ipv4 | ipv6}

Syntax Description




DefaultDisabled.


Example

The following command enables PIM on the system:

enable pim


Multicast Commands

Multicast 222



mrinfomrinfo {router_address} {from from_address} {timeout seconds} {multiple-response-

timeout multi_resp_timeout} {vr vrname}

DescriptionRequests 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 1–30 seconds.

multi_resp_timeout Specifies a maximum time to wait for additional responses after the first response isreceived. The range is 0 to 3 seconds.

vrname Specifies a VR name.

Defaultrouter_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 GuidelinesThe 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 Commands

Multicast 223


Table 7: mrinfo Command Display DataData Description

Metric This should always be 1 because mrinfo queries the directly connected interfaces of adevice.

Threshold This should always be 0 because the threshold feature is not supported inExtremeXOS software.

Type The type specifies the multicast protocol type. Because the ExtremeXOS softwareonly 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.11.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]



mtracemtrace 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}

DescriptionTraces multicast traffic from the receiver back to the source.

Multicast Commands

Multicast 224


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 requestoriginates. This is used as the IP destination address of the mtrace responsepacket.

gw_address Specifies the gateway router IP address of the multicast router to which theunicast mtrace query is sent.

seconds Specifies a maximum time to wait for the mtrace response before making thenext attempt. The range is 1–30 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 mtracepackets.

vrname Specifies a VR name.

Defaultdestination: 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 GuidelinesThe multicast traceroute initiator node generates a multicast query and waits for timeout period toexpire. If there is no response for the timeout period, the initiator node makes two more attempts. If noresponse is received after three attempts, the initiator node moves to a hop-by-hop trace bymanipulating the maximum hop fields to perform a linear search.

The multicast trace response data contains the following fields:

• Incoming interface address—Interface on which traffic is expected from the specific source andgroup

• Outgoing interface address—Interface on which traffic is forwarded from the specified source andgroup towards the destination

Multicast Commands

Multicast 225

• 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 isnot supported.

The last column of the mtrace command output displays forwarding codes, which are described in thefollowing table.

Table 8: mtrace Command Forwarding CodesForwarding Code Description

Wrong interface mtrace request arrived on an interface to which this router would not forward forthis source and group.

Prune sent upstream This router has sent a prune request upstream for the source and group in themtrace request.

Output pruned This router has stopped forwarding for this source and group in response to a prunerequest 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 potentialroute.

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 foran unspecified reason.

Reached RP/Core Reached rendezvous point or core.

RPF Interface mtrace request arrived on the expected RPF interface (upstream interface) for thissource 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.1Mtrace from 1.1.1.100 to Self via 225.1.1.10 34.2.2.4

2 ExtremeXOS switches along the mtrace path do not provide this forwarding code.

Multicast Commands

Multicast 226

-1 34.2.2.4 PIM thresh^ 0 1.1.1.100/32 RPF Interface-2 34.2.2.3 PIM thresh^ 0 1.1.1.100/32-3 23.1.1.2 PIM thresh^ 0 1.1.1.100/32-4 2.2.2.1 PIM thresh^ 0 1.1.1.100/32Round trip time 9 ms; total ttl of 4 required.


The router-alert option was added in ExtremeXOS 12.5.3.


refresh mld ssm-map

refresh mld ssm-map { v6groupnetmask } {{vr} vr_name}

DescriptionSends a DNS request for a particular group. On receiving the DNS response, the “DNS Age” in the SSMmapping entry is refreshed.

Syntax Description

v6groupnetmask Refreshes the specific group information.


DefaultDisabled.

Usage GuidelinesUse 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 Commands

Multicast 227


When v6groupnetmask is specified, the SSM Mapping status and the SSM Mapping entries specificto the group range on the VR are displayed.



rtlookup rpfrtlookup [ipv4_address | ipv6_address] rpf {vr vr_name}

DescriptionDisplays the RPF for a specified multicast source.

Syntax Description

ipv4_address Specifies an IPv4 address.


rpf Selects the RPF for the specified multicast source.

vr_name Specifies the virtual router for which to display the route.

Defaultvr_name is the VR of the current CLI context.


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-defaultOri Prefix Route Gateway VLAN@d 12.1.10.22 12.1.10.0/24 12.1.10.10 v1Origin(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 Commands

Multicast 228



(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



rtlookuprtlookup [ipv4_address | ipv6_address] { unicast | multicast | rpf } {vr vr_name}

DescriptionDisplays the available routes to the specified IP address.

Syntax Description



unicast Displays the routes from the unicast routing table in the current routercontext.

multicast Displays the routes from the multicast routing table in the currentrouter context.

rpf Displays the RPF route to the specified destination.

vr_name Specifies the virtual router for which to display the route.


When no option (unicast or multicast) is provided, this command displays the route in the unicastrouting table.


Multicast Commands

Multicast 229


Example

The following example displays the route lookup for 12.1.20.12 in the multicast routing table for thedefault 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:1sOrigin(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(oa) OSPFIntra, (oe) OSPFAsExt, (or) OSPFInter, (pd) PIM-DM, (ps) PIM-SM(r) RIP, (ra) RtAdvrt, (s) Static, (sv) SLB_VIP, (un) UnKnown(*) Preferred unicast route (@) Preferred multicast route(#) Preferred unicast and multicast routeFlags: (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 RouteMariner # rtlookup 12.1.20.12 multicast vr vr-defaultNo route to 12.1.10.12


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 groupshow igmp group {{vlan} {name} | {grpipaddress}} {IGMPv3}

DescriptionLists the IGMP group membership for the specified VLAN.

Multicast Commands

Multicast 230


Syntax Description


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).

DefaultIGMPv2.

Usage GuidelinesIf no VLAN is specified, all VLANs are displayed. You can also filter the display by group address or bymulticast 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 havesubscribers for the group, all the ports are listed.

• The age since the last IGMP report for this group was received.

NoteThe show igmp group command output is populated on the router that is the PIMRendezvous Point.

Example

The following is sample output from the show igmp groupcommand, listing the IGMP groupmembership:

Group Address Ver Vlan Port Age239.2.4.70 2 banana 7 101224.0.1.24 2 banana 7 107239.255.255.254 2 banana 7 103Total: 3


The IGMPv3 option was added in ExtremeXOS 11.2.

Multicast Commands

Multicast 231


show igmp snooping cacheThis 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}

DescriptionDisplays multicast cache entries added by IGMP snooping for all VLANs and groups. The display can belimited to specific VLANs or groups.

Syntax Description


grpaddressMask Specifies a multicast group address and mask.

DefaultDisplays information for all VLANs and groups.


Example

The following command displays IGMP snooping cache information for all VLANs and groups:

show igmp snooping cache

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}}


Multicast Commands

Multicast 232



show igmp snooping vlan filtershow igmp snooping {vlan} name filter

DescriptionDisplays IGMP snooping filters.

Syntax Description


DefaultNone.

Usage GuidelinesUse this command to display IGMP snooping filters configured on the specified VLAN. When no VLANis specified, all the filters are displayed.

Example

The following command displays the IGMP snooping filter configured on VLAN vlan101:

# show igmp snooping vlan101 filterFilter Port Flagsigmppermit0 5:10 aFlags: (a) Active



Multicast Commands

Multicast 233



show igmp snooping vlan staticshow igmp snooping {vlan} name static [group | router]

DescriptionDisplays static IGMP snooping entries.

Syntax Description


group Displays static multicast groups.

router Displays static router entries.

DefaultNone.

Usage GuidelinesUse this command to display the IGMP snooping static groups or router ports configured on thespecified 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 groupVLAN vlan101 (4094)Group Port Flags239.1.1.2 29 s-239.1.1.2 30 s-239.1.1.2 31 sa239.1.1.2 32 s-239.1.1.2 34 s-Total number of configured static IGMP groups = 5Flags: (s) Static, (a) Active



Multicast Commands

Multicast 234


show igmp snooping vlanshow igmp snooping {vlan} name {port port} {IGMPv3}

DescriptionDisplays IGMP snooping registration information for a specific VLAN. The display can be further limitedto a specific port or to only IGMPv3 entries.

Syntax Description


port Specifies a single port for which information is displayed.

IGMPv3 Displays the IGMP group in IGMPv3 format (if group record is IGMPv3compatible, otherwise displays in earlier format).

DefaultIGMPv2.

Usage GuidelinesThe 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 v1Router Timeout : 260 secHost Timeout : 260 secIgmp Snooping Fast Leave Time : 1000 msVLAN v1 d (4084) Snooping=EnabledPort Host Subscribed Age Group-Limit25 118.1.1.100 All Groups 3 0

The following command displays IGMP snooping registration information for port 2:1 on VLAN test:

show igmp snooping test port 2:1

Multicast Commands

Multicast 235



show igmp snoopingshow igmp snooping {detail {IGMPv3}}

DescriptionDisplays 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 IGMPv3compatible, otherwise displays in earlier format).

DefaultIGMPv2.


Example

The following command displays IGMP snooping registration information for all VLANs:

# show igmp snoopingIgmp Snooping Flag : forward-all-routerIgmp Snooping Flood-list : noneIgmp Snooping Proxy : DisableIgmp Snooping Filters : per-portVlan Vid Port #Senders #Receivers Router Enable--------------------------------------------------------------Default 1 0 Yesv1 4090 0 Yes

Multicast Commands

Multicast 236



The IGMP Forwding Lookup mode output was removed from this command in ExtremeXOS 15.3.


show igmp ssm-mapshow igmp ssm-map {group_ip} {vr vr-name}

DescriptionDisplays the IGMP SSM feature status (enabled or disabled), the mappings for the specified multicastgroup 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 rangeare to be displayed. If no group address is specified, the switch displays allIGMP-SSM mappings.

vr-name Specifies a virtual router name. If the VR name is omitted, the switch displaysthe mappings on the VR specified by the current CLI VR context.

DefaultN/A.

Usage GuidelinesWhen a target group is specified, this command displays all mapping entries for the configured range inwhich 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


Multicast Commands

Multicast 237



show igmpshow igmp {vlan} {vlanname}

DescriptionThis command can be used to display an IGMP-related configuration and group information, per VLAN.

Syntax Description


DefaultN/A.

Usage GuidelinesThe 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 igmpVLAN IP Address Flags nLRMA nLeMA IGMPverDefault 0.0.0.0 / 0 ---izpt- 0 0 3isc 50.50.50.1 /24 ---izpt- 0 0 3v1 0.0.0.0 / 0 U--izpt- 0 2 3v3000 1.1.1.1 /24 ---izpt- 0 0 3v666 6.0.0.1 /16 ---izpt- 0 0 3Flags: (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 Commands

Multicast 238


(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 vlan1Query Interval : 125 secMax Response Time : 10 secLast Member Query : 1 secRobustness : 2Interface on VLAN vlan1 is enabled and up.inet 0.0.0.0/0Locally registered multicast addresses:Learned multicast addresses(Last Querier=118.1.1.100):224.0.0.2 224.0.0.22s = static igmp memberFlags:IP Fwding NO IPmc Fwding NO IGMP YESIGMP Ver V3 Snooping YES Proxy Query YESXmitRtrAlrt YES RcvRtrAlrtReq NO



show ipmrouteshow ipmroute {source-net mask-len | source-net mask | summary} {vr vr-name}

DescriptionDisplays the contents of the IP multicast routing table or the route origin priority.

Syntax Description


mask-len Mask length for the IP multicast source's subnet. Range is 1–32.


summary Displays the statistics of multicast static routes.


Multicast Commands

Multicast 239


Defaultvr-name is the VR of the current CLI context.

Usage GuidelinesThis command allows you to view the configured multicast static routes. You can specify the filteringcriteria on this CLI to view only the desired route. The multicast static routes are displayed in ascendingorder 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 ipmrouteDestination Gateway Mtr Flags Protocol VLANDefault Route 20.20.20.1 255 UG None pc4-1*1.1.0.0/16 20.20.20.1 10 UG bgp pc4-1*11.0.0.0/8 30.30.30.1 12 U- None pc5-311.22.0.0/16 20.20.20.1 10 UG None pc4-1*11.22.33.0/24 30.30.30.1 8 U- None pc5-311.22.33.44/32 20.20.20.1 4 UG None pc4-1*12.0.0.0/8 20.20.20.1 0 UG None pc4-112.24.0.0/16 30.30.30.1 0 U- None pc5-3*12.24.48.96/32 30.30.30.1 2 U- ospf-extern1 pc5-344.66.0.0/16 30.30.30.1 0 U- None pc5-3Flags: (*) Active, (G) Gateway, (U) UpMask distribution:1 default routes 2 routes at length 84 routes at length 16 1 routes at length 242 routes at length 32Total number of multicast static routes = 10



show iproute multicastshow iproute {ipv4} {{vlan} name | [ipaddress netmask | ipNetmask] | origin

[direct | static | mbgp | imbgp | embgp]} multicast {vr vr_name}

DescriptionDisplays all or a filtered set of multicast routes in the IP multicast routing table.

Multicast Commands

Multicast 240


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) forwhich 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 specifiedorigin. Origin options select direct routes, static routes, and routes created bythe MBGP, IMBGP, and EMBGP protocols.

vr_name Specifies the virtual router for which to display multicast routes.


Usage GuidelinesThis 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 multicastOri Destination Gateway Mtr Flags VLAN Duration@d 3.3.3.3/32 3.3.3.3 1 U-------m--- lpbk 12d:1h:30m:36s@d 28.0.0.0/24 28.0.0.15 1 U-------m--- trunk28 12d:1h:30m:36s@mbe 77.0.0.0/24 50.1.10.21 1 UG---S--m--- toronto 0d:0h:41m:1s@mbe 77.0.1.0/24 50.1.10.21 1 UG---S--m--- toronto 0d:0h:41m:1s@mbe 77.0.2.0/24 50.1.10.21 1 UG---S--m--- toronto 0d:0h:41m:1s@mbe 77.0.3.0/24 50.1.10.21 1 UG---S--m--- toronto 0d:0h:41m:1s@mbe 77.0.4.0/24 50.1.10.21 1 UG---S--m--- toronto 0d:0h:41m:1s@mbe 77.0.5.0/24 50.1.10.21 1 UG---S--m--- toronto 0d:0h:41m:1s@mbe 77.0.6.0/24 50.1.10.21 1 UG---S--m--- toronto 0d:0h:41m:1s@mbe 77.0.10.0/24 50.1.10.21 1 UG---S--m--- toronto 0d:0h:41m:1s@mbe 77.0.11.0/24 50.1.10.21 1 UG---S--m--- toronto 0d:0h:41m:1s@mbe 77.0.12.0/24 50.1.10.21 1 UG---S--m--- toronto 0d:0h:41m:1s@mbe 77.0.13.0/24 50.1.10.21 1 UG---S--m--- toronto 0d:0h:

Multicast Commands

Multicast 241

41m:1s@mbe 77.0.14.0/24 50.1.10.21 1 UG---S--m--- toronto 0d:0h:41m:1s@d 82.0.0.0/24 82.0.0.15 1 U-------m--- trunk28-2 12d:1h:30m:36sOrigin(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(is) ISIS, (mb) MBGP, (mbe) MBGPExt, (mbi) MBGPInter, (mp) MPLS Lsp(mo) MOSPF (o) OSPF, (o1) OSPFExt1, (o2) OSPFExt2(oa) OSPFIntra, (oe) OSPFAsExt, (or) OSPFInter, (pd) PIM-DM, (ps) PIM-SM(r) RIP, (ra) RtAdvrt, (s) Static, (sv) SLB_VIP, (un) UnKnown(*) Preferred unicast route (@) Preferred multicast route(#) Preferred unicast and multicast routeFlags: (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 RouteMask distribution:14 routes at length 24 1 routes at length 32Route Origin distribution:3 routes from DirectTotal number of routes = 15Total number of compressed routes = 0



show L2statsshow L2stats {vlan vlan_name}

DescriptionDisplays the counters for the number of packets bridged, switched, and snooped (Layer 2 statistics).

Syntax Description


DefaultN/A.

Multicast Commands

Multicast 242



Example

The following command displays the counters for the number of packets bridged, switched, andsnooped (Layer 2 statistics) for the VLAN accounting:

show L2stats accounting

NoteYou can also enter the command as show l2stats. We use the uppercase letter here toavoid confusion with the numeral 1.


Platform AvailabilityThis command is available on all platforms.

show mcast cacheshow mcast {ipv4 | ipv6} cache {{vlan} name} {{[group grpaddressMask |

grpaddressMask] {source sourceIP | sourceIP}} {type [snooping | pim | mvr]}|

{summary}}

DescriptionDisplays multicast cache information.

The display can be limited to entries for specific VLANs or groups, and it can be limited to specific typesof entries, such as those created by snooping protocols, PIM, or MVR.

Syntax Description




grpaddressMask Specifies a multicast group address and mask.

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 Commands

Multicast 243

mvr Limits the display to cache entries created by MVR.

summary Specifies the summary display format.

DefaultDisplays information for all entries in the multicast cache.

Usage GuidelinesIf the configure forwarding ipmc lookup-key mac-vlan command is configured, thefollowing 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 cacheSnooping/MVR Cache Timeout: 300 secType Group Sender Age InVlansnoop 225.1.1.1 222.222.222.222 17 snvlanVlan Port Vidsnvlan 2 40023 400snoop 224.0.0.5 100.1.2.2 2 pmvlan2Vlan Port Vidpmvlan2 4 402snoop 224.0.0.5 100.1.3.3 17 pmvlan3Vlan Port Vidpmvlan3 23 403snoop 224.0.0.13 100.1.2.2 11 pmvlan2Vlan Port Vidpmvlan2 4 402snoop 224.0.0.13 100.1.3.3 14 pmvlan3Vlan Port Vidpmvlan3 23 403pim 226.1.1.1 100.1.1.12 0 pmvlan1Vlan Port Vidpmvlan2 4 402pmvlan3 23 403Multicast cache distribution:5 entries from Snooping 0 entries from MVR 1 entries from PIMTotal Cache Entries: 6

Multicast Commands

Multicast 244

The following command displays summary cache information for VLAN pmvlan1:

# show mcast cache vlan pmvlan1 summarySnooping/MVR Cache Timeout: 300 sec==============MULTICAST CACHE SUMMARY==============Multicast cache distribution:5 entries from Snooping 0 entries from MVR 1 entries from PIMpmvlan1: Multicast cache distribution:0 entries from Snooping 0 entries from MVR 1 entries from PIMTotal Cache Entries: 6Total Cache Entries for VLAN pmvlan1: 1


Platform AvailabilityThis command is available on all platforms.

show mcast ipv6 cacheshow mcast ipv6 cache {{vlan} name} {{[group v6GrpAddressMask | v6GrpAddressMask]

{source v6SourceIP | v6SourceIP}} {type [snooping | pim]} {with-in-port} |

{summary}}

DescriptionDisplays 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


v6GrpAddressMask Specifies a multicast group address and mask.

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.

DefaultDisplays information for all entries in the multicast cache.

Multicast Commands

Multicast 245


Example

The following command displays all multicast cache information:

# show mcast ipv6 cacheSnooping Cache Timeout: 300 sec(ff03::1 3001::1)Type: snoop Age: 9 Ingress Vlan: v1Vlan Port Vidv1 25 4084(ff03::1 3001::2)Type: snoop Age: 9 Ingress Vlan: v1Vlan Port Vidv1 25 4084Multicast cache distribution:2 entries from Snooping 0 entries from PIMTotal Cache Entries: 2

The following command displays summary cache information for VLAN v1:

# show mcast ipv6 cache vlan v1 summarySnooping Cache Timeout: 300 sec==============MULTICAST CACHE SUMMARY==============Multicast cache distribution:2 entries from Snooping 0 entries from PIMv1: Multicast cache distribution:2 entries from Snooping 0 entries from PIMTotal Cache Entries: 2Total Cache Entries for VLAN v1: 2*X480-48t.22 #



show mldshow mld {vlan} {name}

Multicast Commands

Multicast 246


DescriptionThis command can be used to display an MLD-related configuration and group information, per VLANor for the switch as a whole.

Syntax Description


DefaultN/A.

Usage GuidelinesIf you do not specify a VLAN, the command displays the switch configuration.

Example

The following is sample output from the show mld command:

# show mldVLAN IP Address Flags nLRMA nLeMA MLDverDefault ::/0 ---iz- 0 0 0v1 ::/0 U--iz- 0 5 0Flags: (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 v1Query Interval : 125 secMax Response Time : 10 secLast Member Query : 1 secRobustness : 2Interface on VLAN v1 is enabled and up.inet6 ::/0Locally registered multicast addresses:Learned multicast addresses(Last Querier=fe80::204:96ff:fe3a:ce50):ff02::2 ff02::1:ff56:5c2bff02::1:ff00:2 ff02::1:ff3a:ce50ff02::1:ff55:5c27s = static MLD memberFlags:IP Fwding NO IPmc Fwding NO MLD YESMLD Ver v0 Snooping YES

Multicast Commands

Multicast 247



show mld countersshow mld counters {{vlan} name}

DescriptionUse this command to display an MLD packet statistics.

Syntax Description


DefaultN/A.

Usage Guidelines

The following command displays the MLD configuration:

* topleft.74 # show mld countersMLD Message type Received Originated ForwardedMLD Query (v1/v2) 0 20 0MLDv1 Report 499 0 157MLDv1 Done 101 0 91MLDv2 Report 0 0 0Global Statistics:MLD Packet unknown 0MLD Packet Error 617



Multicast Commands

Multicast 248





show mld groupshow mld group {{vlan} {name} | {v6grpipaddress}} {MLDv2}

DescriptionLists the MLD group membership for the specified VLAN or group.

Syntax Description


v6grpipaddress Specifies a group IPv6 address.

MLDv2 DisplayS the MLD group in MLDv2 format (if group record is MLDv2compatible, otherwise displayS in earlier format). This option is not supportedin this release.

DefaultMLDv1.

Usage GuidelinesIf no VLAN is specified, all VLANs are displayed. You can also filter the display by group address or bymulticast 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 Ver Vlan Port Ageff03::1:1 1 vtest3 4:5 25ff03::1:2 1 vtest3 4:5 25ff02::1:ff22:124 1 vtest3 4:45 26ff05::a:abcd 1 vtest3 4:15 23ff05::a:abce 1 vtest3 4:15 23ff02::1:ff22:112 1 vtest3 4:45 26ff02::1:ff1f:a418 1 vtest3 4:45 26


Multicast Commands

Multicast 249


show mld snooping vlan filtershow mld snooping {vlan} name filter

DescriptionDisplays MLD snooping filters..

Syntax Description


DefaultNone.

Usage GuidelinesUse this command to display MLD snooping filters configured on the specified VLAN. When no VLAN isspecified, all the filters are displayed.

Example

The following command displays the MLD snooping filter configured on VLAN vlan101:

# show mld snooping vlan101 filterFilter Port Flagsmldpermit0 5:10 aFlags: (a) Active



show mld snooping vlan static

Multicast Commands

Multicast 250




show mld snooping vlan name static [group | router]

DescriptionDisplays static MLD snooping entries.

Syntax Description


DefaultNone.

Usage GuidelinesUse this command to display the MLD snooping static groups or router ports configured on thespecified 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 Flags ff03::1:1:1 7 sa ff03::1:1:1 15 saFlags: (s) Static, (a) Active



show mld snoopingshow mld snooping {vlan name | detail} {MLDv2}

NoteMLD snooping is not supported in this software release.

Multicast Commands

Multicast 251



DescriptionDisplays MLD snooping registration information and a summary of all MLD timers and states.

Syntax Description


detail Displays the information in detailed format.

MLDv2 Displays the MLD group in MLDv2 format (if group record is MLDv2compatible, otherwise displays in earlier format). This option is not supportedin this release.

DefaultMLDv1.

Usage GuidelinesThe 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 snoopingMLD Snooping Flood-list : noneMLD Snooping Proxy : EnableMLD Snooping Filters : per-portVlan Vid Port #Senders #Receivers Router Enable--------------------------------------------------------------Default 1 0 Yesv1 4084 0 Yes25 1 Yes41 2 No42 2 No

The following command displays MLD snooping registration information for the VLAN V1:

# show mld snooping v1Router Timeout : 260 secHost Timeout : 260 secMLD Snooping Fast Leave Time : 1000 msVLAN v1 (4084) Snooping=EnabledPort Host AgeSubscribed Join Limit

Multicast Commands

Multicast 252

25 fe80::204:96ff:fe3a:ce50 13ff02::1:ff3a:ce50 No Limit25 fe80::204:96ff:fe3a:ce50 14All Groups No Limit41 fe80::200:8ff:fe55:5c27 13ff02::1:ff00:2 No Limit41 fe80::200:8ff:fe55:5c27 13ff02::1:ff55:5c27 No Limit42 fe80::200:8ff:fe56:5c2b 14ff02::1:ff00:2 No Limit42 fe80::200:8ff:fe56:5c2b 13ff02::1:ff56:5c2b No Limits = static MLD member* X480-48t.27 #



show mld ssm-mapshow mld ssm-map {v6groupnetmask} {{vr} vr_name}

DescriptionDisplays the status of MLD-SSM mapping feature on a VR (if it is enabled or disabled), and displays theMLD-SSM mapping entries.

Syntax Description

v6groupnetmask Displays the specific group information. When v6groupnetmask is notspecified, the SSM Mapping status and all SSM Mapping entries on the VR aredisplayed.


DefaultDisabled.

Usage GuidelinesUse this command to display the status of MLD-SSM mapping feature on a VR (if it is enabled ordisabled), or to display the MLD-SSM mapping entries.

Multicast Commands

Multicast 253



Example

The following command displays MLD SSM mapping on a VR :

# show mld ssm-mapMLD SSM mapping : Enabled Group------ Flags Source ----- -------ff33::1/128 d 2001:0DB8:1::3 d 2001:0DB8:1::4ff33::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 specificto the group range on the VR are displayed.

The following example displays a group containing only DNS name. “DNS” in parenthesis indicates thesource is learned from the DNS server.

# show mld ssm-map ff33::1/128MLD SSM mapping : Enabled

Group : ff33::1/128DNS Name : abcDNS Age : 1512 secondsSources : 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/128MLD SSM mapping : Enabled Group : ff32::1/128Sources : 2001:0DB8:1::5 2001:0DB8:1::6

Total Entries : 2


Multicast Commands

Multicast 254


show msdp memoryshow msdp memory {detail | memoryType}

DescriptionThis command displays current memory utilization of the MSDP process, including all virtual routerinstances of the MSDP process.

Syntax Description

detail Displays detailed statistics for all memory types.

memoryType Displays statistics for a particular memory type.

DefaultN/A.

Usage GuidelinesUse 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 routerinstances of the MSDP process:

show msdp memory

The following is sample output from this command:

MSDP Memory Information-----------------------Bytes Allocated: 79792 AllocFailed: 0 OversizeAlloc: 0Current Memory Utilization Level: GREENMemory 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 4peer 0 0 0 0 0 0 0 0 0 0 0 4mesh-group 0 0 0 3 0 0 0 0 0

Multicast Commands

Multicast 255



0 0 0sa-node 0 0 0 255 0 0 0 0 0 0 0 0sa-entry 0 0 255 0 0 0 0 0 0 0 0 0vr-node 0 0 0 0 0 0 0 0 1 0 0 0rt-cache 0 0 0 5 0 0 0 0 0 0 0 0rp-node 0 0 1 0 0 0 0 0 0 0 0 0client 0 0 0 0 0 0 2 0 0 0 0 0misc 0 0 0 0 3 0 0 0 0 0 0 0



show msdp mesh-groupshow msdp [mesh-group {detail} | {mesh-group} mesh-group-name] {vr vrname}

DescriptionThis 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 amaximum of 31 characters.


DefaultN/A.

Usage GuidelinesUse this command to display configuration information about MSDP mesh-groups, as follows:

Multicast Commands

Multicast 256


• 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 namecommand.

Example

The following command displays the peer count for a mesh-group:

show msdp mesh-group


MeshGroupName PeerCount-------------------------------------------external 0internal 0msdp_mesh 4

The following command displays detailed information about a mesh-group called "msdp_mesh":

show msdp mesh-group "msdp_mesh"


Mesh Group Name : msdp_mesh Num of Peers : 4Peers : 54.172.168.97 55.0.0.83 124.56.78.90221.160.90.228



show msdp peershow msdp [peer {detail} | {peer} remoteaddr] {vr vr_name}

DescriptionThis command displays configuration and run-time parameters about MSDP peers.

Multicast Commands

Multicast 257


Syntax Description

detail Displays detailed information about MSDP peers.



DefaultN/A.

Usage GuidelinesUse 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 0Flags: (*) 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 peer 16.0.0.2MSDP Peer : 16.0.0.2Enabled : No AS Number : 100.100Keepalive Interval : 60 Holdtimer Interval : 75Source Address : not known TTL Threshold : 0Default Peer : No Default Peer Filter : not configuredProcess In Request : Yes In Request filter : not configuredMaximum SA Limit : not configured Mesh Group : not configuredInput SA Filter : not configured Output SA Filter : not configuredState : DISABLED Uptime/Downtime : 00:00:02Local Port : 0 Remote Port : 0

Multicast Commands

Multicast 258

In Total Msgs : 0 Out Total Msgs : 0In SA Msgs : 0 Out SA Msgs : 0In SA Req Msgs : 0 Out SA Req Msgs : 0In SA Resp Msgs : 0 Out SA Resp Msgs : 0Time since Last Msg : 00:00:02 Hold Tmr Exp in : 00:00:00Connection Attempts : 0 Entered Established : 0RPF Fails : 0 Output Queue Size : 0



show msdp sa-cacheshow 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}

DescriptionThis 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: thecache 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 rendezvouspoint.

local Displays locally originated SA cache entries only.

remoteaddr Displays the SA cache entries received from the MSDP peer with the specified IPaddress.


DefaultN/A.

Multicast Commands

Multicast 259


Usage GuidelinesUse this command to view and troubleshoot the SA cache database. There are various filtering criteriayou 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-cacheGroup 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:10235.100.200.2 10.20.30.2 60.0.0.5 192.0.0.16 00:44:24/05:16235.100.200.3 10.20.30.3 60.0.0.5 10.0.0.1 00:44:24/05:10235.100.200.4 10.20.30.4 60.0.0.5 10.0.0.1 00:44:24/05:10235.100.200.5 10.20.30.5 60.0.0.5 55.0.0.5 00:44:24/05:01235.100.200.6 10.20.30.6 60.0.0.5 178.54.67.23 00:44:24/05:17235.100.200.7 10.20.30.7 60.0.0.5 112.234.213.12 00:44:24/05:43235.100.200.8 10.20.30.8 60.0.0.5 10.0.0.1 00:44:24/05:10235.100.200.9 10.20.30.9 60.0.0.5 10.0.0.1 00:44:24/05:10235.100.200.10 10.20.30.10 60.0.0.5 0.0.0.0 00:44:24/00:00235.100.200.11 10.20.30.11 60.0.0.5 0.0.0.0 00:44:24/00:00235.100.200.12 10.20.30.12 60.0.0.5 0.0.0.0 00:44:24/00:00235.100.200.13 10.20.30.13 60.0.0.5 0.0.0.0 00:44:24/00:00235.100.200.14 10.20.30.14 60.0.0.5 0.0.0.0 00:44:24/00:00235.100.200.15 10.20.30.15 60.0.0.5 0.0.0.0 00:44:24/00:00235.100.200.16 10.20.30.16 60.0.0.5 0.0.0.0 00:44:24/00:00235.100.200.17 10.20.30.17 60.0.0.5 0.0.0.0 00:44:24/00:00235.100.200.18 10.20.30.18 60.0.0.5 0.0.0.0 00:44:24/00:00235.100.200.19 10.20.30.19 60.0.0.5 0.0.0.0 00:44:25/00:00Number of accepted SAs : 255Number of rejected SAs : 0Flags: (a) Accepted, (f) Filtered by policy, (r) RPF check failed



Multicast Commands

Multicast 260


show msdpshow msdp {vr vrname}

DescriptionThis command displays global configuration and run-time parameters for MSDP.

Syntax Description


DefaultN/A.

Usage GuidelinesUse 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 msdpMSDP Enabled : No VR-Name : VR-DefaultOriginator RP Addr : not configured SA Cache ageout time : 360Store SA Cache : Yes SA Cache Server : not configuredExport Local SAs : Yes Export SA filter : not configuredMax Rejected Cache : not configured Encapsulate data : YesNum of Rejected SAs : 0 Total Num of SAs : 0Num of Local SAs : 0 AS Disp Format : Asdot



Multicast Commands

Multicast 261


show mvr cacheThis 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}

DescriptionDisplays the multicast cache entries added by MVR.

Syntax Description


DefaultN/A.

Usage GuidelinesIf 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}}



Multicast Commands

Multicast 262


show mvrshow mvr {vlan vlan_name}

DescriptionDisplays the MVR configuration on the switch.

Syntax Description


DefaultN/A.

Usage GuidelinesIf 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



show pim cacheshow pim { ipv4 | ipv6 } cache {{detail} | {state-refresh} {mlag-peer-info}

{group_addr {source_addr}}}

DescriptionDisplays the multicast cache entries created by PIM.

Multicast Commands

Multicast 263


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.

DefaultN/A.

Usage GuidelinesDisplays 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 VLANlist.

Example

The following command displays the PIM cache entry for group 239.255.255.1:

Switch.33 # show pim cache 239.255.255.1Index Dest Group Source InVlan Origin[0000] 239.255.255.1 124.124.124.124 (WR) v4 SparseEntry timer is not run; UpstNbr: 200.124.124.24EgressIfList = vbs15(0)(FW)(SM)(I)[0001] 239.255.255.1 118.5.1.1 (S) vbs5 SparseExpires after 186 secs UpstNbr: 0.0.0.0RP: 124.124.124.124 via 200.124.124.24 in v4EgressIfList = vbs15(0)(FW)(SM)(I) , vpim5(170)(FW)(SM)(S)PrunedIfList = v4(0)(SM)Number of multicast cache = 20Entry flags :-R: RP tree. S: Source tree. W: Any source.Egress/Pruned interface flags :-SM: Sparse Mode DM: Dense ModeFw: Forwarding PP: Prune pendingAL: Assert Loser N: Neighbor present

Multicast Commands

Multicast 264

I: IGMP member present S: (s,g) join receivedZ: (*,g) join received Y: (*,*,rp) join received

The following command displays the PIM-DM cache entry with state-refresh information for group225.0.0.1:

Switch.5 # show pim cache state-refresh 225.0.0.1Index Dest Group Source InVlan Origin[0001] 225.0.0.1 64.1.1.100 (S) vixia Dense Not PrunedExpires after 204 secs UpstNbr: 0.0.0.0Refresh State: Originator(20), TTL: 16EgressIfList = v36(0)(FW)(DM)(N)[0001] 225.0.0.1 65.1.1.100 (S) vixia Dense Not PrunedExpires after 195 secs UpstNbr: 65.1.1.200Refresh State: Not-Originator(25), TTL: 8EgressIfList = v36(0)(FW)(DM)(N)

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 Expires after 203 secs UpstNbr: 51.15.15.2 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)


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 snoopingshow pim snooping {vlan} vlan_name

Multicast Commands

Multicast 265


DescriptionDisplays the PIM snooping configuration for a VLAN.

Syntax Description

vlan_name Specifies a VLAN.

DefaultDisabled.


Example

The following command displays the PIM snooping configuration for the default VLAN:

BD-8810Rack3.8 # show pim snooping defaultGlobal PIM Snooping DISABLEDDefault Snooping DISABLED



show pim

show pim {ipv4 | ipv6 | detail | rp-set {group_addr} | vlan vlan_name}

DescriptionDisplays the PIM configuration and statistics.

Syntax Description

ipv4 Displays PIM IPv4 configuration information.

ipv6 Displays PIM IPv6 configuration information.

Multicast Commands

Multicast 266


detail Displays show output in the detailed format.

group_addr Specifies an IP multicast group, for which the RP is to be displayed.


DefaultIPv4 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 GuidelinesThe detail version of this command displays the global statistics for PIM, as well as the details of eachPIM enabled VLAN.

Example

The following command displays the global PIM configuration and statistics:

* sw4.30 # show pimPIM Enabled, Version 2PIM CRP DisabledBSR state : ACCEPT_PREFERRED ; BSR Hash Mask : 255.255.255.252Current BSR Info : 61.2.2.2 (Priority 20) expires after 78 secConfigured BSR Info : 0.0.0.0 (Priority 0) CRP Adv Interval : 60 sec ; CRP Holdtime: 150BSR Interval : 60 sec ; BSR Timeout : 130Cache Timer : 210 sec ; Prune Timer : 210Assert Timeout : 210 sec ; Register Suppression Timeout,Probe: 60, 5Generation Id : 0x52af433d Dense Neighbor Check : On PIM-DM State Refresh TTL : 16PIM-DM State Refresh Source Active Timer : 210PIM-DM State Refresh Origination Interval : 60Threshold for Last Hop Routers: 0 kbpsThreshold 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 : DisabledPIM IP Route Sharing Hash : Source-Group-Next HopRegister Checksum to exclude data Active Sparse Ckts 10 Dense Ckts 0 State Refresh Ckts 0

Global Packet Statistics ( In Out Drop ) C-RP-Advs 0 0 0 Registers 0 0 0 RegisterStops 0 0 0

VLAN Cid IP Address Designated Flags Hello J/P Nbrs

Multicast Commands

Multicast 267

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 IntervalFlags : 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 Enabled, Version 2PIM CRP DisabledBSR state : ACCEPT_ANY ; BSR Hash Mask : 255.255.255.252Current BSR Info : 0.0.0.0 (Priority 0)Configured BSR Info : 0.0.0.0 (Priority 0) CRP Adv Interval : 60 sec ; CRP Holdtime: 150BSR Interval : 60 sec ; BSR Timeout : 130Cache Timer : 210 sec ; Prune Timer : 210Assert Timeout : 210 sec ; Register Suppression Timeout,Probe: 60, 5Generation Id : 0x533331c7 Dense Neighbor Check : On PIM-DM State Refresh TTL : 16PIM-DM State Refresh Source Active Timer : 210PIM-DM State Refresh Origination Interval : 60Threshold for Last Hop Routers: 0 kbpsThreshold 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 : DisabledPIM IP Route Sharing Hash : Source-Group-Next HopRegister Checksum to exclude data Active Sparse Ckts 10 Dense Ckts 0 State Refresh Ckts 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 Commands

Multicast 268

State Refresh : Off State Refresh Capable : No Border : No Generation State DR Neighbor IP address Id Expires Refresh Priority 51.8.8.3 0x53332567 97 No 1 51.8.8.6 0x5332e6d8 94 No 1

Packet Statistics (In/Out) Hellos 30 15 Bootstraps 10 0 Join/Prunes 12 0 Asserts 0 0 Grafts 0 0 GraftAcks 0 0 State Refresh 0 0

The following command displays the elected, active RP for the group 239.255.255.1:

show pim rp-set 239.255.255.1Group Mask C-RP Origin Priority224.0.0.0 240.0.0.0 10.10.10.2 Bootstrap 0224.0.0.0 240.0.0.0 124.124.124.124 Bootstrap 0224.0.0.0 240.0.0.0 124.124.124.124 static 0239.255.255.0 255.255.255.0 124.124.124.124 Bootstrap 0Elected RP is 124.124.124.124

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 : 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 : pimPolicy with priority 0 Shutdown priority : 1024 Source Specific Multicast : Disabled State Refresh : Off State Refresh Capable : No Border : No

Generation State DR Neighbor IP address Id Expires Refresh Priority 30.30.30.2 0x5199b2db 105 No 1 Packet Statistics (In/Out) Hellos 41 40 Bootstraps 0 20 Join/Prunes 0 0 Asserts 0 0 Grafts 0 0 GraftAcks 0 0 State Refresh 0 0

Multicast Commands

Multicast 269

The following is PIM IPv4 show output for the show register policy configuration, including dropcounters:

sw2.6 # show pimPIM Enabled, Version 2PIM CRP Enabled on 1 interfacesBSR state : ELECTED ; BSR Hash Mask : 255.255.255.252Current BSR Info : 61.2.2.2 (Priority 20) expires after 36 secConfigured BSR Info : 61.2.2.2 (Priority 20) in vlan l1CRP Adv Interval : 60 sec ; CRP Holdtime: 150BSR Interval : 60 sec ; BSR Timeout : 130Cache Timer : 210 sec ; Prune Timer : 210Assert Timeout : 210 sec ; Register Suppression Timeout,Probe: 60, 5Generation Id : 0x5331f58c Dense Neighbor Check : On PIM-DM State Refresh TTL : 16PIM-DM State Refresh Source Active Timer : 210PIM-DM State Refresh Origination Interval : 60Threshold for Last Hop Routers: 0 kbpsThreshold for RP : 0 kbps Register-Rate-Limit-Interval : Always active PIM SSM address range : None PIM Register Policy : sw1_rp_filterPIM Register Policy RP : None PIM IP Route Sharing : DisabledPIM IP Route Sharing Hash : Source-Group-Next HopRegister Checksum to exclude data Active Sparse Ckts 3 Dense Ckts 0 State Refresh Ckts 0


The following is PIM show output with IP Route Sharing information:

sw6.19 # show pimPIM Enabled, Version 2PIM CRP DisabledBSR state : ACCEPT_PREFERRED ; BSR Hash Mask : 255.255.255.252Current BSR Info : 61.2.2.2 (Priority 20) expires after 78 secConfigured BSR Info : 0.0.0.0 (Priority 0) CRP Adv Interval : 60 sec ; CRP Holdtime: 150BSR Interval : 60 sec ; BSR Timeout : 130Cache Timer : 210 sec ; Prune Timer : 210Assert Timeout : 210 sec ; Register Suppression Timeout,Probe: 60, 5Generation Id : 0x5332e6d1 Dense Neighbor Check : On PIM-DM State Refresh TTL : 16PIM-DM State Refresh Source Active Timer : 210PIM-DM State Refresh Origination Interval : 60Threshold for Last Hop Routers: 0 kbpsThreshold 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 : DisabledPIM IP Route Sharing Hash : Source-Group-Next HopRegister Checksum to exclude data

Multicast Commands

Multicast 270

Active Sparse Ckts 11 Dense Ckts 0 State Refresh Ckts 0


VLAN Cid IP Address Designated Flags Hello J/P Nbrs Router Int Int eight 1 51.8.8.6 / 24 51.8.8.6 rifms------- 30 60 2 eleven 2 51.11.11.6 / 24 51.11.11.6 rifms------- 30 60 0

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 State Refresh Capable : No Border : No Secondary Interfaces: 2003::2/ 64 Generation State DR Neighbor IP address Id Expires Refresh Priority fe80::204:96ff:fe26:6c89 0x5192f6f5 101 No 1

Packet Statistics (In/Out) Hellos 5 6 Bootstraps 0 0 Join/Prunes 0 0 Asserts 0 0 Grafts 0 0 GraftAcks 0 0 State Refresh 0 0


Multicast Commands

Multicast 271

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

DescriptionRemoves the join limit set on VLAN ports.

Syntax Description



DefaultNo limit.


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


Multicast Commands

Multicast 272



unconfigure igmp ssm-mapunconfigure igmp ssm-map {{vr} vr-name}

DescriptionUnconfigures 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 VRspecified by the current CLI VR context.

DefaultN/A.


Example

The following command deletes all IGMP-SSM mappings on the virtual router "xyz":

unconfigure igmp ssm-map vr xyz



unconfigure igmpunconfigure igmp

Multicast Commands

Multicast 273



DescriptionResets all IGMP settings to their default values and clears the IGMP group table.


DefaultN/A.


Example

The following command resets all IGMP settings to their default values and clears the IGMP group table:

unconfigure igmp



unconfigure mldunconfigure mld

DescriptionResets all MLD settings to their default values and clears the MLD group table.

DescriptionThis command has no arguments or variables.

Multicast Commands

Multicast 274


DefaultN/A.


Example

The following command resets all MLD settings to their default values and clears the MLD group table:

unconfigure mld



unconfigure mld ssm-mapunconfigure mld ssm-map {{vr}vr_name }

DescriptionDeletes all MLD SSM Mapping entries on a VR.

Syntax Description


DefaultDisabled.

Usage GuidelinesUse this command to delete all MLD SSM Mapping entries on a specified VR.



Multicast Commands

Multicast 275



Example

The following command deletes MLD SSM mapping on VR1 :

unconfigure mld ssm-map vr vr1



unconfigure msdp sa-cache-serverunconfigure msdp sa-cache-server {vr vrname}

DescriptionRemoves the MSDP SA cache server.

Syntax Description

vrname Specifies the name of the virtual router on which the MSDP cache server is configured. Ifa virtual router name is not specified, it is extracted from the current CLI context.

DefaultBy default, the router does not send SA request messages to its MSDP peers when a new member joinsa group and wants to receive multicast traffic. The new member simply waits to receive SA messages,which eventually arrive.

Usage GuidelinesUse this command to remove the MSDP SA cache server you specified with the configure msdpsa-cache-server command.

Example

The following command removes the MSDP SA cache server:

unconfigure msdp sa-cache-server

Multicast Commands

Multicast 276





unconfigure pim borderunconfigure pim {ipv4 | ipv6} {vlan} vlan_name border

DescriptionUnconfigures a PIM VLAN that has been configured as a border VLAN, which is used to demarcate aPIM domain.

Syntax Description




DefaultBy default, no PIM VLANs are configured as border VLANs.

Usage GuidelinesA PIM-SM domain is created by limiting the reach of PIM BSR advertisements. When a border VLAN isconfigured, PIM BSR advertisements are not forwarded out of the PIM VLAN. Use the unconfigurepim 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


The IPv6 configuration option was added in ExtremeXOS 15.3.

Multicast Commands

Multicast 277



unconfigure pim ssm range

unconfigure pim {ipv4 | ipv6} ssm range

DescriptionUnconfigures the range of multicast addresses for PIM SSM.

Syntax Description



DefaultBy default, no SSM range is configured.

Usage GuidelinesYou must disable PIM before configuring or unconfiguring a PIM-SSM range. Use the disable pimcommand.

Initially, no range is configured for SSM. After a range is configured, you can remove the range with theunconfigure 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:

unconfigure pim ssm range


The ipv4 and ipv6 keywords were added, giving an option to support this functionality in IPv6 as well,in ExtremeXOS 15.3.

Multicast Commands

Multicast 278



unconfigure pimunconfigure pim {ipv4 | ipv6} [{vlan vlan_name} | {tunnel} tunnel_name] border

DescriptionResets 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.

DefaultIf no VLAN is specified, the configuration is reset for all PIM interfaces.

Usage GuidelinesIf 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


The ipv4 and ipv6 keywords were added, giving an option to support this functionality in IPv6 as well,in ExtremeXOS 15.3.

Multicast Commands

Multicast 279



Multicast Commands

Multicast 280


multicast - extreme networksextrcdn.extremenetworks.com/wp-content/uploads/2014/04/multicast.… ·...

Documents