Vcs Fabric Formation Multicast DP

53-1003501-01
October 2014
Brocade VCS Fabric

Formation and Multicast
Deployment Guide
2014, Brocade Communications Systems, Inc. All Rights Reserved.
Brocade, the B-wing symbol, Brocade Assurance, ADX, AnyIO, DCX, Fabric OS, FastIron, HyperEdge, ICX, MLX, MyBrocade, NetIron,
OpenScript, VCS, VDX, and Vyatta are registered trademarks, and The Effortless Network and the On-Demand Data Center are trademarks
of Brocade Communications Systems, Inc., in the United States and in other countries. Other brands and product names mentioned may be
trademarks of others.
Notice: This document is for informational purposes only and does not set forth any warranty, expressed or implied, concerning any
equipment, equipment feature, or service offered or to be offered by Brocade. Brocade reserves the right to make changes to this document
at any time, without notice, and assumes no responsibility for its use. This informational document describes features that may not be
currently available. Contact a Brocade sales office for information on feature and product availability. Export of technical data contained in
this document may require an export license from the United States government.
The authors and Brocade Communications Systems, Inc. assume no liability or responsibility to any person or entity with respect to the
accuracy of this document or any loss, cost, liability, or damages arising from the information contained herein or the computer programs that
accompany it.
The product described by this document may contain open source software covered by the GNU General Public License or other open
source license agreements. To find out which open source software is included in Brocade products, view the licensing terms applicable to
the open source software, and obtain a copy of the programming source code, please visit http://www.brocade.com/support/oscd.
Contents
Preface..................................................................................................................................... 5
Introduction..............................................................................................................................7
What is Brocade VCS Ethernet Fabric?............................................................7
Multi-Layer Architecture.................................................................................... 7
VCS Fabric Technology.................................................................................... 8
Deploying Fabric Cluster Mode................................................................................................13

Configuring the VCS ID in Fabric Cluster Mode..............................................13
Configuring the Rbridge ID in Fabric Cluster Mode........................................ 13
Verifying Fabric Configuration and ISLs for Fabric Cluster Mode................... 14
Configuring Port Channels in Fabric Cluster Mode.........................................17
Split Recovery Options........................................................................18
vLAG scalability...................................................................................18
Deploying Logical Chassis Mode............................................................................................. 23

Configuration Management in Logical Chassis Mode.....................................23
Verifying VCS Fabric and ISL Formation in Logical Chassis Mode................ 24
Configuration Management in Logical Chassis Mode.....................................27
Enabling VLANs and OSPF............................................................................ 28
Configuring VLANs in the Aggregation Layer ................................................ 30
Deploying IP Multicast............................................................................................................ 35
PIM-SM........................................................................................................... 35
Configuring PIM-SM Multicast.........................................................................36
Procedure Summary........................................................................... 37
Detailed Procedure with Examples................................................................. 38
Configuring OSPF, PIM, and VRRP-E................................................ 40
Configuring Access 2 VLAN and Protocol...........................................41
OSPF Configuration............................................................................ 43
Configuring VE Interfaces................................................................... 45
Verifying OSPF and PIM..................................................................... 47
Starting the Receivers.........................................................................57
Deploying IGMP ..................................................................................................................... 67

Overview of IGMP........................................................................................... 67
IGMP Features, Options, and Terminology.....................................................67
Configuring and Verifying IGMP Snooping..................................................... 68
Configuring Layer 2 Multicast in Access and Aggregation Layers.................. 69
Procedure Summary....................................................................................... 70
Detailed Procedure with Examples................................................................. 70
Enabling IGMP Snooping....................................................................70
Configuring Layer 2 VLAN.................................................................. 71
Configuring VPLS................................................................................73
Configuring VLANs with IGMP Snooping............................................74
Brocade VCS Fabric Formation and Multicast Deployment Guide

53-1003501-01
Adding Ports to Aggregation1........................................................... 76

Starting the Receivers.......................................................................76
Verifying IGMP Snooping..................................................................76

53-1003501-01
Preface
This document is a deployment guide for implementing multicast functionality in a Brocade VCS fabric
using either Fabric Cluster or Logical Chassis mode. It is written for technology decision-makers,
architects, systems engineers, NOC engineers and other experts responsible for network deployment
and implementation.
This document provides step-by-step examples to prepare, perform, and verify the deployment of
multicast functionality, including IP multicast and Internet Group Management Protocol (IGMP)
snooping . It is assumed that the reader is familiar with establishing console access and entering
commands using the Brocade CLI.
Document History
Date
Version
Description
October 2014
Initial version

53-1003501-01
Preface

53-1003501-01
Introduction
What is Brocade VCS Ethernet Fabric?............................................................................7
Multi-Layer Architecture.................................................................................................... 7
VCS Fabric Technology.................................................................................................... 8
What is Brocade VCS Ethernet Fabric?

A Brocade VCS Ethernet fabric provides higher performance, utilization, availability, and reduced
complexity, compared to a traditional, hierarchical Ethernet network.
Data center networks rely on Ethernet to carry traffic for a diverse set of applications including client/
server, web services, unified communications, virtual machines, and storage. Each type of traffic has
different traffic patterns and network service requirements.
Applications are increasingly deployed using virtual machines (VMs) hosted on server clusters,
connected over Ethernet to shared storage pools. Distributed storage makes heavy demands on the
network, including lossless packet delivery, deterministic latency, and high bandwidth, and VCS
Ethernet fabric is designed to meet these demands.
VCS fabric is programmed with awareness of all network paths, nodes, requirements, and resources,
allowing it to elastically scale up or down depending on the network demand. VCS also eliminates the
need to run Spanning Tree Protocol (STP), forwarding over the redundant network paths that would be
placed in blocking state by STP.
To summarize, VCS provides the following benefits:
Flat topology: Eliminates the requirement for STP, while maintaining interoperability with existing
Ethernet networks.
Flexibility: Integrates easily with any topology to efficiently meet the requirements for a variety of
workloads.
Resiliency: Provides several least-cost paths to improve functionality, reliability, and stability.
Elasticity: Automatically scales up and down depending on application and other requirements.
Efficient link and bandwidth utilization: All links are forwarding; no links are blocking. All the links are
considered for the best traffic path.
Multi-Layer Architecture
A multi-layer architecture is oftetn used in Ethernet data centers to improve scalability, performance,
and management. This architecture typically has three layers:
Access Layer: Provides connectivity to all end devices, including storage, servers, hypervisors, and
so forth.
Aggregation Layer: Provides the boundary between Layer 2 and Layer 3 networks, and between
Access and Core layers. The best practice has been to connect multiple Access layer networks

53-1003501-01
VCS Fabric Technology
through the Aggregation layer to avoid Layer 2 loops on redundant links. The Aggregation layer
provides resiliency and acts as the Layer 3 gateway.
Core Layer: Interconnects multiple Aggregation layers and provides resiliency to avoid a single
point of failure, using a Layer 3 interior gateway protocol (IGP), such as Open Shortest Path First
(OSPF), Intermediate System-to-Intermediate System (IS-IS), or Border Gateway Protocol (BGP).

VCS provides advanced Ethernet fabric functionality, and allows a graceful transition to nextgeneration, elastic, highly automated, cloud-optimized data center networks. VCS fabrics share
information across nodes and may be managed as a single logical chassis, greatly simplifying
management and reducing operational overhead. VCS greatly improves VM awareness and
automation compared to traditional architectures and supports storage over a converged fabric.
VCS Ethernet fabrics are implemented through Brocade VDX datacenter switches, which support
cloud-optimized networking and greater enterprise agility. The following table summarizes the features
provided by each VDX switch model.
TABLE 1 Brocade VDS Data Center Switches
Features
VDX 6710
VDX 6720
VDX 6730/F
VDX 6740
VDX 8770
Ports
48 1-Gb
24 10-GB
2410 GB
48 10-Gb
48 1-Gb
6 10-Gb
60 10-Gb
8 8 Gb
4 40-Gb
4810-Gb
60 10-Gb
48 10-Gb
16 8-Gb
12 40-Gb
27 40-Gb
6 100-Gb
Ethernet ports
1-Gb
1-Gb
1-Gb
1-Gb
1-Gb
10-Gb
10-Gb
10-Gb
10-Gb
10-Gb
40-Gb
40-Gb
100-Gb
FCoE
Yes
Yes
Yes
Yes
Yes
FC
No
No
Yes, 8-Gb
Yes, 32
No
Flexports in NOS
Release 5
iSCSi
Yes
Yes
Yes
Yes
Yes
VCS
Yes
Yes
Yes
Yes
Yes
Virtual fabric/GVlan
No
No
No
Yes
Yes
VX-LAN
Gateway
No
No
No
Yes
No
In a Clos topology, also known as core-edge topology, edge switches connect to core switches (see
Figure 1 ). A fabric deployment using the Clos topology, illustrated in the figure below, provides a
balance between scalability, high availability and low latency.

53-1003501-01
Introduction
FIGURE 1 Clos Topology
In a full mesh topology, shown Figure 2 , every switch is connected directly to every other switch. A fullmesh topology provides a low-latency fabric with maximum path availability for deployments where
scalability is not a major requirement.
FIGURE 2 Full Mesh Topology

53-1003501-01
Introduction
The advantages and disadvantages of a full-mesh topology include the following:

Advantages: Minimizes the number of hops and reduces latency because any node in the cluster is
only one hop away. It is highly reliable with many paths through the fabric that are usable in case of
connection or node failure.
Disadvantages: Best suited for smaller fabrics that are not expected to scale rapidly. It does not
scale well because each additional node requires an exponential increase in the number of fabric
links. Also, traffic patterns should be evenly distributed with low overall bandwidth consumption.
The example in this document demonstrates the deployment of a full mesh topology.
Figure 3 illustrates the full-mesh topology used to demonstrate the configuration in this guide.
FIGURE 3 Configuration Topology
This example illustrates three separate VCS fabrics in two separate datacenters, each with its own
VCS ID:
VCS 10: Access fabric including four 6740 switches (VDX1, VDX2, VDX3, and VDX4)
VCS11: Aggregation fabric including two 8770 switches (VDX5 and VDX6)
VCS 12: Access fabric including four 6740 switches (VDX7, VDX8, VDX9, and VDX 10
These fabrics are interconnected through MLX core routers.
In Fabric Cluster mode, each switch is configured independently, but all switches in the same fabric
must be enabled with the same VCS ID. Changing the VCS ID of a switch reverts the configuration of
the switch to the default-config and restarts the switch.
Automatic Neighbor Discovery. When a new switch is connected to an existing switch in Fabric
Cluster mode, the switch in Fabric Cluster mode determines if the new neighbor has Fabric Cluster
mode enabled, and if so, joins the new switch to the existing Fabric Cluster VCS. With Fabric Cluster
mode enabled, if the f VCS IDs are the same, then the switch joins the fabric.
10

53-1003501-01
Introduction
Automatic ISL Formation and Hardware-based Trunk Formation. When a switch joins an Ethernet
fabric, ISLs automatically form between directly connected switches within the fabric. If more than one
ISL exists between two switches, Brocade trunks are automatically formed. All ISLs connected to the
same neighboring VDX switch attempt to form a trunk. The trunks are formed only when the ports
belong to the same port group. If the ports belong to different port groups then different ISLs are
formed. No user intervention is necessary to form a Brocade trunk.
Brocade trunks are hardware-based LAGs, which distribute traffic evenly across all the available links in
a trunk on a frame-by-frame basis without hashing. Brocade trunk ISLs are basically zero configuration
LAGs. The limitations affecting the deployment of Brocade trunks include the following:
ISL can be a separate link or can be a part of Brocade trunk.

Brocade trunks are not supported on 1-GbE interfaces in VDX 67xx switches.
Brocade trunks are not supported on 40-GbE interfaces in VDX 87xx using LC12x40G line cards.
Because Brocade trunk is implemented in hardware, all member ports should be on the same ASIC
on either side of the trunk (applies to VDX 67xxx and VDX 87xx switches).
Maximum of 8 ports per Brocade trunk and six Brocade trunks per ASIC (applies to VDX 67xxx and
VDX 87xx switches).
All ports in trunk must be in the same port group.
Brocade trunk has a maximum throughput of 80 Gb/s. Full link utilization of eight ports in a trunk
group requires a packet size greater than 128 bytes.
To gain the advantages of Brocade trunking between VDX switches, at least one two-member trunk and
multiple ECMP paths is recommended. It is also recommended to route the cables in a trunk through
separate conduits to ensure connectivity in case one conduit is accidentally cut.
A shutdown command on an operating ISL interface not only brings down the physical link but also its
FSPF adjacency. The main difference between a shutdown command and a no fabric isl enable
command is that the link stays up after a no fabric isl enable, while the link stays down after a shutdown
command.
When building a fabric it is important to think in terms of ISL bandwidth. Brocade ISL trunks can be
formed using up to eight links providing up to 80 Gb/s. However, the throughput of ISLs is limited to 80
million packets/sec (pps), which limits bandwidth when using small packets.
After you repair any segmented or disabled ISL ports, toggle the fabric ISL in order to propagate the
changes.

53-1003501-01
11
12

53-1003501-01
Deploying Fabric Cluster Mode

Configuring the VCS ID in Fabric Cluster Mode..............................................................13
Configuring the Rbridge ID in Fabric Cluster Mode........................................................ 13
Verifying Fabric Configuration and ISLs for Fabric Cluster Mode................................... 14
Configuring Port Channels in Fabric Cluster Mode.........................................................17
Configuring the VCS ID in Fabric Cluster Mode

To configure the VCS ID for the switches in the example deployment using Fabric Cluster mode,
perform the following steps.
Procedure
Step 1: Configure the VCS ID for the Access layer nodes in Datacenter 1.
VDX1-Access1#
VDX2-Access2#
10
VDX3-Access3#
10
VDX4-Access4#
10
vcs vcsid 10
vcs vcsid 10
<-Configuring vcsid 10
<-Configuring vcsid
vcs vcsid 10
<-Configuring vcsid
vcs vcsid 10
<-Configuring vcsid
Step 2: Configure the VCS ID for the Aggregation layer nodes in Datacenter
1.
VDX5-Agr1# vcs vcsid 10
VDX6-Agr2# vcs vcsid 10
Step 3: Configure the VCS ID for the Access layer nodes in Datacenter 2.
VDX7-Access7# vcs vcsid 12
VDX8-Access8# vcs vcsid 12
Configuring the Rbridge ID in Fabric Cluster Mode

All the switches in Access and Aggregation layers should be enabled with a unique rbridge id. This
erases any existing configuration in the switch and reverts the switch to the default-config and restarts
the switch.
The rbridge with the lowest WWN in the Ethernet fabric is elected as the principal switch. The principal
switch decides whether the configuration of a new rbridge joining the fabric conflicts with any of the
rbridges already in the fabric. If a conflict arises, the principal switch segments the new rbridge. The
rbridge id value has a range from 1 to 239.
In Fabric Cluster mode, complete the configuration individually on each node.

53-1003501-01
13
Verifying Fabric Configuration and ISLs for Fabric Cluster Mode
NOTE
if there is an rbridge Id conflict between two VDX switches, one of the offending switches has to
change its rbridge Id. The valid range for rbridge id is 1-239.
To configure the rbridge IDs for the example deployment, complete the following steps.
Procedure
Step 1: Configure the rbridge IDs for the Access layer nodes in Datacenter
1.
VDX1-Access1# vcs rbridge-id 100
100
VDX2-Access2 vcs rbridge-id 101
101
102
VDX4-Access4 vcs rbridge-id 103
103
<-Configuring rbridge id
Step 2: Configure the rbridge IDs for the Aggregation layer nodes in
Datacenter 2.
DX5-Agr1# vcs rbridge-id 200
VDX6-Agr2# vcs rbridge-id 201
<-Configuring rbridge id 200

<-Configuring rbridge id 201
Step 3: Configure the rbridge IDs for the Access layer nodes in Datacenter
2.
150
151
Verifying Fabric Configuration and ISLs for Fabric Cluster Mode

This section describes how to verify the fabric mode and the ISLs for the example deployment for
nodes running in Fabric Cluster mode.
To verify the fabric mode and the ISLs, complete the following steps
14

53-1003501-01
Procedure
Step 1: Verify VDX-1 Access1 VCS.
VDX1-Access1# show vcs
Config Mode
: Local-Only <- It is local mode and configuration should be done
individually on each node.
VCS ID
: 10 <-VCS ID
Total Number of Nodes
: 4
Rbridge-Id
WWN
Management IP
Status
HostName
---------------------------------------------------------------------------------------100
>10:00:00:27:F8:FD:F6:C0*
10.24.19.1
Online
VDX1Access1 <- Local
101
10:00:00:27:F8:FE:44:FC
10.24.19.2
Online
VDX2Access2 <-Other nodes
102
10:00:00:27:F8:FD:2B:98
10.24.19.3
Online
VDX3Access3
103
10:00:00:27:F8:FC:B7:89
10.24.19.4
Online
VDX4Access4
VDX1-Access1 VCS verification in detail
VDX1-Access1# show vcs detail
Config Mode
: Local-Only
VCS ID
: 10
: 4
Node :1
Serial Number
Condition
Status
VCS Id
Rbridge-Id
Co-ordinator
WWN
Switch MAC
FCF MAC
Switch Type
Internal IP
Management IP
management
<rbridge-id>/0
Node :2
Serial Number
Condition
Status
VCS Id
Rbridge-Id
Co-ordinator
WWN
Switch MAC
FCF MAC
Switch Type
Internal IP
Management IP
Node :3
Serial Number
Condition
Status
VCS Id
Rbridge-Id
Co-ordinator
WWN
Switch MAC
FCF MAC
Switch Type
Internal IP
Management IP
Node :4
Serial Number
Condition
Status
VCS Id
Rbridge-Id
Co-ordinator
WWN
:
:
:
:
:
:
:
:
:
:
:
:
CPLayer 2507K0CN
Good
Co-ordinator
10
100*
YES
10:00:00:27:F8:FD:F6:C0
00:27:F8:FD:F6:C0
00:27:F8:FD:F7:44
BR-VDX6740
127.1.0.100
10.24.19.1 <- Should be configured by the user on interface
:
:
:
:
:
:
:
:
:
:
:
:
CPLayer 2507K0CS
Good
Connected to Cluster
10
101
NO
10:00:00:27:F8:FE:44:FC
00:27:F8:FE:44:FC
00:27:F8:FE:45:80
BR-VDX6740
127.1.0.101
10.24.19.2
:
:
:
:
:
:
:
:
:
:
:
:
CPLayer 2507K0CP
Good
10
102
NO
10:00:00:27:F8:FD:2B:98
00:27:F8:FD:2B:98
00:27:F8:FD:2C:1C
BR-VDX6740
127.1.0.102
10.24.19.3
:
:
:
:
:
:
:
CPLayer 2507K0CJ
Good
10
103
NO
10:00:00:27:F8:FC:B7:89

53-1003501-01
15
Switch MAC
: 00:27:F8:FC:B7:89
FCF MAC
: 00:27:F8:FC:B8:0D
Switch Type
: BR-VDX6740
Internal IP
: 127.1.0.103
Management IP : 10.24.19.4
VDX1-Access1 ISL verification
VDX1-Access1# show fabric isl all
Rbridge-id: 100
#ISLs: 3 <- Rbridge ID 100 forms 3 ISLs
Src
Src
Nbr
Nbr
Index
Interface
Index
Interface
Nbr-WWN
BW
Trunk NbrName
--------------------------------------------------------------------------------------------4
Te 100/0/1
4
Te 101/0/1
10:00:00:27:F8:FE:44:FC
40-Gb
Yes
"VDX2-Access2" <-ISLs formed with other nodes in same fabric. It displays host-name
of
other switches. Hostnames should be configured by user under switch-attributes
<rbridge-id>
using the CLI host-name <name>
12
Te 100/0/9
12
Te 103/0/9
10:00:00:27:F8:FC:B7:89
40-Gb
Yes
"VDX4-Access4"
21
Te 100/0/18
21
Te 102/0/18
10:00:00:27:F8:FD:2B:98
40-Gb
Yes
"VDX3-Access3"
Step 2: Verify VDX1-Access1 ISL Ports.

VDX1-Access1# show fabric islports
Name:
VDX1-Access1 <- Host name of the switch
Type:
131.7
State:
Online
Role:
Fabric Principal
VCS Id:
10
Config Mode:Local-Only
Rbridge-id: 100
WWN:
10:00:00:27:f8:fd:f6:c0
FCF MAC:
00:27:f8:fd:f7:44
Index
Interface
State
Operational State
===================================================================
0
Fo 100/0/49
Down
1
Fo 100/0/50
Down
2
Fo 100/0/51
Down
3
Fo 100/0/52
Down
4
Te 100/0/1
Up
ISL 10:00:00:27:f8:fe:44:fc "VDX2-Access2"
(downstream)(Trunk Primary) <- ports 1 to 4 with Access2
5
Te 100/0/2
Up
ISL (Trunk port, Primary is Te 100/0/1 )
6
Te 100/0/3
Up
7
Te 100/0/4
Up
8
Te 100/0/5
Down
9
Te 100/0/6
Down
10
Te 100/0/7
Down
11
Te 100/0/8
Down
12
Te 100/0/9
Up
ISL 10:00:00:27:f8:fc:b7:89 "VDX4-Access4" (Trunk
Primary)
<- ports 9 to 12 with Access4
13
Te 100/0/10
Up
14
Te 100/0/11
Up
15
Te 100/0/12
Up
16
Te 100/0/13
Down
17
Te 100/0/14
Down
18
Te 100/0/15
Down
19
Te 100/0/16
Down
20
Te 100/0/17
Up
ISL (Trunk port, Primary is Te 100/0/18 ) <- ports
17 to 20
with Access3
21
Te 100/0/18
Up
ISL 10:00:00:27:f8:fd:2b:98 "VDX3-Access3" (Trunk
Primary)
22
Te 100/0/19
Up
23
Te 100/0/20
Up
24
Te 100/0/21
Down
<<snip>>
50
Te 100/0/47
Down
51
Te 100/0/48
Down
16

53-1003501-01
Configuring Port Channels in Fabric Cluster Mode
Step 3: Repeat Step 1 and 2 for all the switches in the fabric.
Configuring Port Channels in Fabric Cluster Mode

A LAG can originate from multiple VDX switches to form a vLAG, which appears on the network as a
single link to a single switch. As illustrated in the figure below, a vLAG works like a standard LAG using
the Link Aggregation Control Protocol (LACP), which controls the bundling of several physical ports to
form a single logical link or trunk.
FIGURE 4 vLAGs in a VCS Fabric
When establishing dynamic LACP LAGs, PDU frames are exchanged between the switch and end
devices. The PDU includes a unique identifier for both the switch and the device that is used to
determine the port channel with which a link should be associated.
Brocade NOS Release 2.1.0 and later supports a unique and consistent local LACP System ID (SID),
which is shared between all rbridges that are connected to the same vLAG. This SID is unique for each
switch in the VCS. You must configure the same parameters for a given vLAG on all participating nodes
in the FCS. Other important points to keep in mind when configuring vLAGs include the following:
Members of a vLAG in a VCS need not be directly connected with each other.
MAC addresses on a vLAG are learned as a multi-home MAC address reachable over all the
participating VCS nodes.
vLAGs are supported on 1-GbE, 10-GbE and 40-GbE ports, but all ports much be the same speed.
All VLAN, ACL and QoS configuration applied on a vLAG is similar to Layer 2 port channel
configuration.
All STP BPDUs are treated as data traffic on any member port of a vLAG.
If a MAC address learned on a vLAG moves to another vLAG or another edge port on the VCS, the
new source port triggers a fabric-wide update.
FCoE over vLAGs is not supported.
The first node and port to join the vLAG is treated as the primary node and port. All broadcast,
unicast, and multicast (BUM) traffic travels on the primary node and port.

53-1003501-01
17
Split Recovery Options
If the participating VCS nodes in the vLAG are not at equal distance from the VCS entry point where
the destination MAC address is looked up, the shortest-path algorithm chooses the node that is
closest and lowest cost.
You can specify the minimum number of links that must be active on a vLAG before it can form; the
default is 1. Until the minimum number of links is online, the port channel appears with "protocol down"
status.
Split Recovery Options

Split Recovery: In NOS Release 2.1.0 and later, the no-ignore-split option causes the SID to be
derived using the actual MAC address of one of the participating rbridges (the SID Master). The SID
from the first rbridge added to the vLAG is used. If the RBridge that owns the SID of the vLAG leaves
the cluster, a new SID is selected from the MAC of one of the other Rbridges, and the vLAG
converges again.
No Split Recovery: When using the no-split-recovery option, a virtual SID (VSID), which is a unique
identifier derived from the VCS ID, is used as the LACP SID for the vLAG. In this mode, when a node
is split from the vLAG, all rbridges continue to advertise the same VSID as their LACP SID. No reconvergence occurs when nodes leave or rejoin the vLAG. This mode is the only split recovery option
in NOS versions before Release 2.1.0.
vLAG scalability
The table below summarizes the maximum number of components allowed in a single VCS fabric.
18
vLAG Feature or Configuration
Maximum number
Total number of vLAG on a single VDX node (LAG ID

range is 1 to 6144)
384
Total number of member ports per vLAG
32
Total number of VDX node participating in a single

vLAG
Maximum number of vLAGs in a cluster
512
Maximum number of members per node in one vLAG
16

53-1003501-01
Procedure
To configure the port channels in the Fabric Cluster mode deployment, complete
the following steps.
The following steps are for configuring the Access layer nodes in Datacenter1.
Step 1: Configure the VDX1-Access1 interfaces.
interface FortyGigabitEthernet 100/0/49
no fabric isl enable <- Disabling isl and trunk
no fabric trunk enable
channel-group 50 mode active type standard <- configuring link aggregation
lacp timeout long <- LACP long timeout is configured
no shutdown <- Interface is enabled
!
no
Step 2: Configure the VDX2-Access2 Interfaces.

channel-group 50 mode active type standard <-configuring link aggregation
Step 3: Configuring the VDX1-Access1 port channels.

interface Port-channel 50
vlag ignore-split
speed 40000 <- adding speed to port-channel. This can be added when port-channel is
not UP.
Once this is added, the ports in that port-channel should be disabled and enabled for
them
to come up.
no shutdown <- Port-channel is enabled.
no no
Step 4: Configuring the VDX2-Access2 port channels.

vlag ignore-split
not UP.
Once this is added, the ports in that port-channel should be disabled and enabled for
them
to come up.
The following steps are for configuring the Aggregation layer nodes in
Datacenter1.
Step 5: Configure the VDX5-Agr1 interfaces.
no fabric isl enable

53-1003501-01
19

channel-group 50 mode active type standard
lacp timeout long
no shutdown
Step 6: Configure the VDX6-Agr2 interfaces.

channel-group 50 mode active type standard
lacp timeout long
no shutdown
Step 7: Configure the VDX5-Agre1 port channels.

vlag ignore-split
not UP.
Once this is added, the ports in that port-channel should be disabled and enabled
for them
to come up.
no
VDX6-Agr2 Port Channel Configuration

vlag ignore-split
not UP.
Once this is added, the ports in that port-channel should be disabled and enabled
for them
to come up.
The following steps are for verifying the port channels.

Step 8: Verify the VDX1-Access1 port channels.
VDX1-Access1# show port-channel 50
LACP Aggregator: Po 50 (vLAG) <-Port-channel id
Aggregator type: Standard
Ignore-split is enabled
Member rbridges:
rbridge-id: 100 (2) <- rbridge IDs
rbridge-id: 101 (2)
Admin Key: 0050 - Oper Key 0050
Partner System ID - 0x8000,01-e0-52-00-00-0b
Partner Oper Key 0050
Member ports on rbridge-id 100:
UP
Link: Fo 100/0/49 (0x640C0620C0) sync: 1
* <-Ports and sync 1 means the port is
Link: Fo 100/0/51 (0x640C0660C0) sync: 1

VDX2-Access2# show port-channel 50
LACP Aggregator: Po 50 (vLAG) <-Port-channel id
Aggregator type: Standard
Ignore-split is enabled
Member rbridges:
rbridge-id: 100 (2) <- rbridge IDs
rbridge-id: 101 (2)
Admin Key: 0050 - Oper Key 0050
Partner System ID - 0x8000,01-e0-52-00-00-0b
Partner Oper Key 0050
20

53-1003501-01
Member ports on rbridge-id 101:

Link: Fo 101/0/49 (0x650C0620C0) sync: 1 <-Ports and sync 1 means the port is UP
Link: Fo 101/0/51 (0x650C0660C0) sync: 1

VDX1-Access1# show interface port-channel 50
Port-channel 50 is up, line protocol is up
Hardware is AGGREGATE, address is 0027.f8fd.f709
Current address is 0027.f8fd.f709
Interface index (ifindex) is 671088690
Minimum number of links to bring Port-channel up is 1
MTU 2500 bytes
LineSpeed Actual
: 80000 Mbit
Allowed Member Speed : 40000 Mbit
Flowcontrol rx: off, tx: off
Priority Tag disable
IPv6 RA Guard disable
Last clearing of show interface counters: 19:58:38
Queueing strategy: fifo
Receive Statistics:
9477 packets, 1221114 bytes
Unicasts: 0, Multicasts: 9477, Broadcasts: 0
64-byte pkts: 0, Over 64-byte pkts: 53, Over 127-byte pkts: 9424
Over 255-byte pkts: 0, Over 511-byte pkts: 0, Over 1023-byte pkts: 0
Over 1518-byte pkts(Jumbo): 0
Runts: 0, Jabbers: 0, CRC: 0, Overruns: 0
Errors: 0, Discards: 0
Transmit Statistics:
Underruns: 0
Rate info (interval 299 seconds):
Input 0.000000 Mbits/sec, 0 packets/sec, 0.00% of line-rate
Output 0.000000 Mbits/sec, 0 packets/sec, 0.00% of line-rate
Time since last interface status change: 19:35:12

VDX2-Access2# show interface port-channel 50
Port-channel 50 is up, line protocol is up
Hardware is AGGREGATE, address is 0027.f8fe.4545
Current address is 0027.f8fe.4545
Interface index (ifindex) is 671088690
Minimum number of links to bring Port-channel up is 1
MTU 2500 bytes
LineSpeed Actual
: 80000 Mbit
Allowed Member Speed : 40000 Mbit
Flowcontrol rx: off, tx: off
Priority Tag disable
IPv6 RA Guard disable
Last clearing of show interface counters: 20:00:36
Queueing strategy: fifo
Receive Statistics:
64-byte pkts: 0, Over 64-byte pkts: 55, Over 127-byte pkts: 9448
Over 255-byte pkts: 0, Over 511-byte pkts: 0, Over 1023-byte pkts: 0
Over 1518-byte pkts(Jumbo): 0
Runts: 0, Jabbers: 0, CRC: 0, Overruns: 0
Transmit Statistics:
Underruns: 0
Rate info (interval 299 seconds):
Input 0.000000 Mbits/sec, 0 packets/sec, 0.00% of line-rate
Output 0.000000 Mbits/sec, 0 packets/sec, 0.00% of line-rate
Time since last interface status change: 19:38:20
Step 12: Perform Step 8 to 11 to verify the port-channel details for the other
switches in the fabric.

53-1003501-01
21
vLAG scalability
22

53-1003501-01
Deploying Logical Chassis Mode

Configuration Management in Logical Chassis Mode.....................................................23
Verifying VCS Fabric and ISL Formation in Logical Chassis Mode................................ 24
Configuration Management in Logical Chassis Mode.....................................................27
Enabling VLANs and OSPF............................................................................................ 28
Configuring VLANs in the Aggregation Layer ................................................................ 30
When enabling VDX switches in Logical Chassis mode, each switch should be configured with the
same VCS ID. This resets any existing configuration in the switch to the default-config and restarts the
switch.
Logical Chassis mode, sometimes called Management Cluster mode, provides unified control of the
fabric from a single node, called the principal node or switch. Logical Chassis mode is modular,
scalable, flexible, and simplified. Adding, removing, and rejoining nodes to the cluster is easy, and
switches can be configured with a virtual IP address and upgraded with a single firmware download.
In Logical Chassis mode, controlled failover occurs when an existing node is administratively removed
from the cluster. Details regarding that node are then no longer shown in the output from the show vcs
command. Uncontrolled failover occurs when a node leaves the cluster as a result of ISL links being
brought down (administratively or because of link failure) or a reboot. The show vcs command displays
the appropriate disconnected status.
Configuration Management in Logical Chassis Mode

The VCS in Logical Chassis mode has two types of configuration objects:
Global Configuration: Objects that can potentially span across multiple physical nodes, such as
VLAN, VLAG, ACL and so forth.
Local configuration: Objects that are strictly local to a single node, such as physical interfaces, Layer
3 protocols (OSPF, BGP, VRRP), virtual Ethernet (VE) interfaces, and so forth.
TABLE 2 Global and Local Configuration in Logical Chassis Mode
Global
Local (Port/interface or Node level configurations)
Username/RBACs
Fabric ISL
VLAN
MTU
Port Profiles (name, size, activate, Qos, security, vlan,

binding to Mac)
LLDP DCBX
Mac address list, Mac address
Channel group
IP Access List, IP IGMP snooping

LACP System Priority
LACP timeout
vCenter Name
QoS
aaa authentication login, Radius server
IP & Layer 3 configuration
VCS Virtual IP Address
Port Profile Port

53-1003501-01
23
Verifying VCS Fabric and ISL Formation in Logical Chassis Mode
TABLE 2 Global and Local Configuration in Logical Chassis Mode (Continued)

Global
Monitor Session
sFlow
Event trap level
License installation/enablement/removal
The following commands transition a device between standalone, Logical Chassis, and Fabric Cluster
modes:
vcs rbridge-id 2 vcsid 1 enable: Change standalone switch to Fabric Cluster.

vcs rbridge-id 3: Change the rbridge ID for all VCS-enabled modes.
vcs vcsid 1: Change the VCS ISD for all VCS-enabled modes.
vcs rbridge-id 3 vcsid 1 logical-chassis enable:Change mode from standalone to Logical
Chassis or Fabric Cluster to Logical Chassis for the local node.
vcs logical-chassis enable rbridge-id 2-3 default-config: Change mode from Fabric Cluster to
Logical Chassis for a set of rbridges.
no vcs logical-chassis enable rbridge-id all default-config
no vcs logical-chassis enable rbridge-id 1-4,7 default-config: Change the mode from Logical
Chassis to Fabric Cluster for a set of rbridges .
no vcs rbridge-id 3 vcsid 1 logical-chassis enable:Change the mode from Logical Chassis to
Fabric Cluster with a change to the Rbridge or VCS ID.
no vcs enable:Change the mode from Logical Chassis for a local node.
Procedure
To deploy a VCS in Logical Chassis mode, complete the following step.
Step 1: Configure Access Layer in Datacenter 1.
VDX1-Access1# vcs vcsid 10 rbridge-id 100 logical-chassis enable
vcsid 10 in logical-chassis mode
<-Configuring vcsid 10 in logical-chassis
mode
mode
mode
<-Configuring
Verifying VCS Fabric and ISL Formation in Logical Chassis Mode

Procedure
To verify the VCS Fabric and ISL formation in Logical Chassis mode, complete the following steps:
Step 1: Verify VDX3-Access3 VCS (Summary)
VDX3-Access3# show vcs
Config Mode
: Distributed
VCS ID
: 10
VCS GUID
: 813f8732-6920-4770-991a-9d964d8e62c0
: 4
Rbridge-Id
WWN
Management IP
Status
HostName
---------------------------------------------------------------------------------------100
10:00:00:27:F8:FD:F6:C0
10.24.19.1
Online
VDX1Access1
101
10:00:00:27:F8:FE:44:FC
10.24.19.2
Online
24

53-1003501-01
VDX2Access2
102
>10:00:00:27:F8:FD:2B:98*
10.24.19.3
Online
VDX3Access3 <- Principal switch. Configurations for other switches in the fabric can be
performed through this switch
103
10:00:00:27:F8:FC:B7:89
10.24.19.4
Online
VDX4Access4
Step 2: Verify VDX3-Access3 VCS (Details)

VDX3-Access3# show vcs detail
Config Mode
: Distributed
VCS ID
: 10
VCS GUID
: 813f8732-6920-4770-991a-9d964d8e62c0
Virtual IP
: 10.24.19.15/24
Associated rbridge-id
: 102
: 4
Nodes Disconnected from Cluster : 0
Cluster Condition
: Good
Cluster Status
: All Nodes Present in the Cluster
Node :1
Serial Number
: CPLayer 2507K0CN
Condition
: Good
Status
: Connected to Cluster
VCS Id
: 10
Rbridge-Id
: 100
Co-ordinator
: NO
WWN
: 10:00:00:27:F8:FD:F6:C0
Switch MAC
: 00:27:F8:FD:F6:C0
FCF MAC
: 00:27:F8:FD:F7:44
Switch Type
: BR-VDX6740
Firmware Ver
: v4.0.1
Internal IP
: 127.1.0.100
Management IP
: 10.24.19.1 <- Can be configured through principal switch by
accessing interface management 100/0
Node :2
Serial Number
: CPLayer 2507K0CS
Condition
: Good
Status
VCS Id
: 10
Rbridge-Id
: 101
Co-ordinator
: NO
WWN
: 10:00:00:27:F8:FE:44:FC
Switch MAC
: 00:27:F8:FE:44:FC
FCF MAC
: 00:27:F8:FE:45:80
Switch Type
: BR-VDX6740
Firmware Ver
: v4.0.1
Internal IP
: 127.1.0.101
Management IP
Node :3
Serial Number
: CPLayer 2507K0CP
Condition
: Good
Status
: Co-ordinator
VCS Id
: 10
Rbridge-Id
: 102*
Co-ordinator
: YES
WWN
: 10:00:00:27:F8:FD:2B:98
Switch MAC
: 00:27:F8:FD:2B:98
FCF MAC
: 00:27:F8:FD:2C:1C
Switch Type
: BR-VDX6740
Firmware Ver
: v4.0.1
Internal IP
: 127.1.0.102
Management IP
Node :4
Serial Number
: CPLayer 2507K0CJ
Condition
: Good
Status
VCS Id
: 10
Rbridge-Id
: 103
Co-ordinator
: NO
WWN
: 10:00:00:27:F8:FC:B7:89
Switch MAC
: 00:27:F8:FC:B7:89
FCF MAC
: 00:27:F8:FC:B8:0D
Switch Type
: BR-VDX6740
Firmware Ver
: v4.0.1

53-1003501-01
25
Internal IP
: 127.1.0.103
Management IP
Step 3: Verify VDX3-Access3 ISLs

VDX3-Access3# show fabric isl all
No. of nodes in cluster: 4
Rbridge-id: 100
#ISLs: 3
Src
Src
Nbr
Nbr
Index
Interface
Index
Interface
Nbr-WWN
BW
Trunk NbrName
-------------------------------------------------------------------------------------------4
Te 100/0/1
4
Te 101/0/1
10:00:00:27:F8:FE:44:FC
40-Gb
Yes
"VDX2-Access2"
14
Te 100/0/11
14
Te 103/0/11
10:00:00:27:F8:FC:B7:89
40-Gb
Yes
"VDX4-Access4"
20
Te 100/0/17
20
Te 102/0/17
10:00:00:27:F8:FD:2B:98
40-Gb
Yes
"VDX3-Access3"
Rbridge-id: 101
#ISLs: 3
Src
Src
Nbr
Nbr
Index
Interface
Index
Interface
Nbr-WWN
BW
Trunk NbrName
-------------------------------------------------------------------------------------------4
Te 101/0/1
4
Te 100/0/1
10:00:00:27:F8:FD:F6:C0
40-Gb
Yes
"VDX1-Access1"
12
Te 101/0/9
12
Te 102/0/9
10:00:00:27:F8:FD:2B:98
40-Gb
Yes
"VDX3-Access3"
20
Te 101/0/17
20
Te 103/0/17
10:00:00:27:F8:FC:B7:89
40-Gb
Yes
"VDX4-Access4"
Rbridge-id: 103
#ISLs: 3
Src
Src
Nbr
Nbr
Index
Interface
Index
Interface
Nbr-WWN
BW
Trunk NbrName
-------------------------------------------------------------------------------------------4
Te 103/0/1
4
Te 102/0/1
10:00:00:27:F8:FD:2B:98
30G
Yes
"VDX3-Access3"
14
Te 103/0/11
14
Te 100/0/11
10:00:00:27:F8:FD:F6:C0
40-Gb
Yes
"VDX1-Access1"
20
Te 103/0/17
20
Te 101/0/17
10:00:00:27:F8:FE:44:FC
40-Gb
Yes
"VDX2-Access2"
Rbridge-id: 102
#ISLs: 3
Src
Src
Nbr
Nbr
Index
Interface
Index
Interface
Nbr-WWN
BW
Trunk NbrName
-------------------------------------------------------------------------------------------4
Te 102/0/1
4
Te 103/0/1
10:00:00:27:F8:FC:B7:89
30G
Yes
26

53-1003501-01
"VDX4-Access4"
12
Te 102/0/9
Yes
"VDX2-Access2"
20
Te 102/0/17
Yes
"VDX1-Access1"
12
Te 101/0/9
10:00:00:27:F8:FE:44:FC
40-Gb
20
Te 100/0/17
10:00:00:27:F8:FD:F6:C0
40-Gb
Step 4: Verify VDX3-Access3 ISL ports

VDX3-Access3# show fabric islports
Name:
VDX3-Access3 <- Host name of the switch
Type:
131.7
State:
Online
Role:
Fabric Principal
VCS Id:
10
Config Mode:Distributed
Rbridge-id: 102
WWN:
10:00:00:27:f8:fd:2b:98
FCF MAC:
00:27:f8:fd:2c:1c
Index
Interface
State
Operational State
===================================================================
0
Fo 102/0/49
Down
1
Fo 102/0/50
Down
2
Fo 102/0/51
Down
3
Fo 102/0/52
Down
4
Te 102/0/1
Up
ISL 10:00:00:27:f8:fc:b7:89 "VDX4-Access4"
(downstream)(Trunk Primary) <- With VDX4
5
Te 102/0/2
Down
6
Te 102/0/3
Up
7
Te 102/0/4
Up
8
Te 102/0/5
Down
9
Te 102/0/6
Down
10
Te 102/0/7
Down
11
Te 102/0/8
Down
12
Te 102/0/9
Up
ISL 10:00:00:27:f8:fe:44:fc "VDX2-Access2" (Trunk
Primary)
<- With VDX2
13
Te 102/0/10
Up
14
Te 102/0/11
Up
15
Te 102/0/12
Up
16
Te 102/0/13
Down
17
Te 102/0/14
Down
18
Te 102/0/15
Down
19
Te 102/0/16
Down
20
Te 102/0/17
Up
ISL 10:00:00:27:f8:fd:f6:c0 "VDX1-Access1"
(downstream)(Trunk Primary) <- With VDX1
22
Te 102/0/19
Up
23
Te 102/0/20
Up
24
Te 102/0/21
Down
<<snip>>
50
Te 102/0/47
Down
51
Te 102/0/48
Down

The VCS in Logical Chassis mode has two types of configuration objects:
Global Configuration: Objects that can potentially span across multiple physical nodes, such as
VLAN, VLAG, ACL and so forth.
Local configuration: Objects that are strictly local to a single node, such as physical interfaces, Layer
3 protocols (OSPF, BGP, VRRP), virtual Ethernet (VE) interfaces, and so forth.
TABLE 3 Global and Local Configuration in Logical Chassis Mode
Global
Username/RBACs
Fabric ISL

53-1003501-01
27
Enabling VLANs and OSPF
TABLE 3 Global and Local Configuration in Logical Chassis Mode (Continued)

Global
VLAN
MTU
Port Profiles (name, size, activate, Qos, security, vlan,

binding to Mac)
LLDP DCBX
Mac address list, Mac address
Channel group
IP Access List, IP IGMP snooping

LACP System Priority
LACP timeout
vCenter Name
QoS
aaa authentication login, Radius server
IP & Layer 3 configuration
VCS Virtual IP Address
Port Profile Port
Monitor Session
sFlow
Event trap level
License installation/enablement/removal
The following commands transition a device between standalone, Logical Chassis, and Fabric Cluster
modes:
vcs rbridge-id 2 vcsid 1 enable: Change standalone switch to Fabric Cluster.

vcs rbridge-id 3: Change the rbridge ID for all VCS-enabled modes.
vcs vcsid 1: Change the VCS ISD for all VCS-enabled modes.
vcs rbridge-id 3 vcsid 1 logical-chassis enable:Change mode from standalone to Logical
Chassis or Fabric Cluster to Logical Chassis for the local node.
vcs logical-chassis enable rbridge-id 2-3 default-config: Change mode from Fabric Cluster to
Logical Chassis for a set of rbridges.
no vcs logical-chassis enable rbridge-id all default-config
no vcs logical-chassis enable rbridge-id 1-4,7 default-config: Change the mode from Logical
Chassis to Fabric Cluster for a set of rbridges .
no vcs rbridge-id 3 vcsid 1 logical-chassis enable:Change the mode from Logical Chassis to
Fabric Cluster with a change to the Rbridge or VCS ID.
no vcs enable:Change the mode from Logical Chassis for a local node.
Procedure
To deploy a VCS in Logical Chassis mode, complete the following step.
Step 1: Configure Access Layer in Datacenter 1.
vcsid 10 in logical-chassis mode
mode
mode
mode
<-Configuring
Enabling VLANs and OSPF

To enable VLANs and OSPF, complete the following steps:
28

53-1003501-01
Procedure
Complete the following steps to configure the Access layer nodes in Datacenter
1.
Step 1: Configure VDX1-Access1 VLAN
VDX3-Access3(config)# rbridg-id 100 <- Accessing rbridge-id from principal switch
VDX3-Access3(config-rbridge-id-100)# interface vlan 100 <-Configuring a VLAN 100
Step 2: Configure VDX2-Access2 VLAN

VDX3-Access3(config)# rbridg-id 101 <- Accessing rbridge-id from principal switch
VDX3-Access3(config-rbridge-id-101)# interface vlan 100 <- Configuring a VLAN 100.
Step 3: Add Port Channel 50 tagged to a VLAN (VDX1-Access1

vlag ignore-split
speed 40000
switchport <- Enabling switchport
switchport mode trunk <- Enabling mode as trunk to add a tagged port
switchport trunk allowed vlan add 100 <-Adding to vlan 100 as tagged
switchport trunk tag native-vlan <-Adding the port-channel tagged to default-vlan
spanning-tree shutdown
no shutdown
Step 4: Add Port Channel 50 tagged to a VLAN (VDX2-Access2)

vlag ignore-split
speed 40000
switchport <- Enabling switchport
no shutdown
Step 5: Enable OSPF (VDX1-Access1)

VDX3-Access3(config)# rbrid ge-id 100 <- Accessing rbridge from principal switch
VDX3-Access3(config-rbridge-id-100)# router ospf <-Enabling OSOF on that rbridge
VDX3-Access3(config-router-ospf-vrf-default-vrf)# area 1 <-Configuring OSPF area

VDX3-Access3(config-router-ospf-vrf-default-vrf)# rbridge-id 101 <- Accessing
rbridge from
principal switch
VDX3-Access3(config-router-ospf-vrf-default-vrf)# area 1 <-Configuring OSPF area
Step 7: Enable OSPF on VE interface (VDX1-Access1)

rbridge-id 100 <-Rbridge id
interface Ve 100 <- Interface ve 100 associated with VLAN 100
ip ospf area 1 <-Enabling ospf with area 1
ip proxy-arp
ip address 5.1.1.2/25 <-Configuring IP address
no shutdown <-Enabling the VE
!

rbridge-id 101 <-Rbridge id
ip ospf area 1<-Enabling ospf with area 1
ip proxy-arp
Step 9: Verify OSPF neighbors (VDX1-Access1)

VDX1-Access1# show ip ospf neighbor
Number of Neighbors is 3, in FULL state 2
Port
Address

53-1003501-01
Pri State
Neigh Address
Neigh ID
Ev
29
Configuring VLANs in the Aggregation Layer
Opt Cnt
Ve 100
5.1.1.2
254 FULL/BDR
5.1.1.1
5.1.1.1
7
2
0
Ve 100
5.1.1.2
255 FULL/DR
5.1.1.3
5.1.1.3
6
2
0
Ve 100
5.1.1.2
1
2WAY/OTHER 5.1.1.4
5.1.1.4
4
2
0
<-Because either of the nodes is DR/BDR, so neighborship stuck at 2WAY
Step 10: Verify OSPF Neighbors (VDX2-Access2)

Port
Address
Pri State
Neigh Address
Neigh ID
Ev
Opt Cnt
Ve 100
5.1.1.4
254 FULL/BDR
5.1.1.1
5.1.1.1
7
2
0
Ve 100
5.1.1.4
1
2WAY/OTHER 5.1.1.2
5.1.1.2
2
2
0
<-Because either of the nodes is DR/BDR, so neighborship stuck at 2WAY
Ve 100
5.1.1.4
255 FULL/DR
5.1.1.3
5.1.1.3
6
2
0
Step 11: Verify VLAN (VDX1-Access1)

VDX1-Access1# show vlan 100
VLAN
Name
State
Ports
(F)-FCoE
(u)-Untagged, (t)-Tagged
(R)-RSPAN
(c)-Converged
======== =============== ==========================
================================================
100
VLAN0100
ACTIVE
Po 50(t)
<- VLAN 100 has
active member
port port-channel 50
Step 12: Verify VLAN (VDX2-Access2)

VDX2-Access2# show vlan 100
VLAN
Name
State
Ports
(F)-FCoE
(R)-RSPAN
(c)-Converged
======== =============== ==========================
================================================
100
VLAN0100
ACTIVE
Po 50(t) <- VLAN 100 has active
member
port port-channel 50

To configure the nodes in the Aggregation layer in Datacenter 1, complete the following steps.
30

53-1003501-01
Procedure
Step 1: Configure VDX5-Agr1 VLAN
VDX6-Agr2(config)# rbridg-id 200 <- Accessing rbridge-id from principal switch
VDX3-Access3(config-rbridge-id-200)# interface vlan 100 <-Configuring a VLAN 100.
Step 2: Configure VDX6-Agr2 VLAN

VDX6-Agr2 (config)# rbridg-id 201 <- Accessing rbridge-id from principal switch
VDX6-Agr2(config-rbridge-id-201)# interface vlan 100 <-Configuring a VLAN 100.
Step 3: Add Port Channel 50 tagged to a VLAN (VDX5-Agr1)

vlag ignore-split
speed 40000
switchport <-Enabling switchport
no shutdown
Step 4: Add Port Channel 50 tagged to a VLAN (VDX6-Agr2)

vlag ignore-split
speed 40000
switchport <-Enabling switchport
switchport mode trunk <-Enabling mode as trunk to add a tagged port
no shutdown
Step 5: Enable OSPF (VDX5-Agr1)

VDX6-Agr2 (config)# rbrid ge-id 200 <-Accessing rbridge from principal switch
VDX3-Access3(config-router-ospf-vrf-default-vrf)# area 0
<-Configuring OSPF areas, area 0 between Agrs and area 1 is between AGR and Access
Step 6: Enable OSPF (VDX6-Agr2)

VDX6-Agr2 (config-router-ospf-vrf-default-vrf)# rbridge-id 201 <- Accessing rbridge
from principal switch
<-Configuring OSPF area
Step 7: Enable OSPF on VE Interface in Area 1 (VDX5-Agr1)

rbridge-id 200 <-rbridge id
ip ospf priority 254 <-Configuring OSPF priority to make it as BDR
ip proxy-arp
!
Step 8: Enable OSPF in Area 1 (VDX6-Agr2)

ip ospf priority 255 <-Configuring OSPF priority 255 to make it DR
ip proxy-arp
Step 9: Enable OSPF in Area 0 (VDX6-Agr2)


53-1003501-01
31
ip
ip
ip
no
ospf area 0 <-Enabling ospf with area 0

proxy-arp
address 6.1.1.1/25 <-Configuring IP address
shutdown ! <-Enabling the VE
Step 10: Enable OSPF on VE interface in Area 0 (VDX5-Agr1)

ip proxy-arp
Step 11: Verify OSPF on VDX5-Agr1

VDX5-Agr1# show ip ospf neighbor
Port
Ev
Cnt
Ve 101
6
Ve 100
5
Ve 100
6
Ve 100
5
Opt
2
Address
Pri State
Neigh Address
Neigh ID
6.1.1.1
FULL/DR
6.1.1.2
5.1.1.3
5.1.1.1
FULL/OTHER 5.1.1.2
5.1.1.2
5.1.1.1
255 FULL/DR
5.1.1.1
5.1.1.3
5.1.1.3
FULL/OTHER 5.1.1.4
5.1.1.4
Step 12: Verify OSPF on VDX6-Agr2

Port
Ev
Cnt
Ve 101
6
Ve 100
6
Ve 100
6
Ve 100
6
Opt
2
Address
Pri State
Neigh Address
Neigh ID
6.1.1.2
FULL/BDR
6.1.1.1
5.1.1.1
5.1.1.3
254 FULL/BDR
5.1.1.1
5.1.1.1
5.1.1.3
FULL/OTHER 5.1.1.2
5.1.1.2
5.1.1.3
FULL/OTHER 5.1.1.4
5.1.1.4
Step 13: Verify VDX5-Agr1 VLAN

VDX5-Agr1# show vlan 100
VLAN
Name
State
Ports
(F)-FCoE
(R)-RSPAN
(c)-Converged
======== =============== ==========================
================================================
100
VLAN0100
ACTIVE
Po 50(t)
<- Active member portchannel50
VDX5-Agr1#
VLAN
Name
State
Ports
(F)-FCoE
(R)-RSPAN
(c)-Converged
======== =============== ==========================
================================================
101
VLAN0101
INACTIVE(no member port) <-No port is tagged to this VLAN,
but
neighborship is formed with AGR2 through ISL
Step 14: Verify VDX6-Agr2 VLAN

VLAN
Name
State
Ports
(F)-FCoE
(R)-RSPAN
(c)-Converged
======== =============== ==========================
================================================
100
VLAN0100
ACTIVE
Po 50(t)
<- Active member port-
32

53-1003501-01
channel50
VLAN
Name
State
Ports
(F)-FCoE
(R)-RSPAN
(c)-Converged
======== =============== ==========================
================================================
101
VLAN0101
INACTIVE(no member port) <-No port is tagged to this VLAN,
but
neighborship is formed with AGR2 through ISL

53-1003501-01
33
34

53-1003501-01
Deploying IP Multicast
PIM-SM........................................................................................................................... 35
Configuring PIM-SM Multicast.........................................................................................36
Detailed Procedure with Examples................................................................................. 38
IP multicast is an efficient way for transmitting a data stream to multiple hosts simultaneously. Protocol
Independent Multicast (PIM) is one of many protocols designed for IP multicast. PIM does not rely on a
specific routing protocol to create its network topology state. The PIM messages are sent encapsulated
in an IP packet with the IP protocol field set to 103. Depending on the type of message, the packet is
either sent to all PIM routers at the multicast address (224.0.0.13) or sent as a unicast to a specific host.
The following four varieties of PIM are available for deployment in different scenarios and are described
below:
Sparse Mode (PIM-SM)

Dense Mode (PIM-DM)
Bidirectional (BIDIR-PIM)
Source Specific Multicast (PIM-SSM)
PIM-SM
PIM-SM is most commonly deployed and is designed for large networks where most of the hosts are
not interested in every multicast data stream. PIM-SM creates a unidirectional shared tree from a
common node in the network, called the Rendezvous Point (RP), acting as the root. The RP acts as the
middle man between the source for a specific multicast group and the interested hosts or devices. The
RP can be statically configured on each PIM router or dynamically assigned through mechanisms such
as Bootstrap Router (BSR), Auto-RP, Anycast-RP or Embedded RP.
Within a network, the RP should always be upstream in relation to the destination hosts. Each device
interested in joining a group, sends a request to the RP for the group. To limit the join messages, the
local network identifies an upstream router as the designated router (DR). All hosts downstream from
the DR send Internet Group Message Protocol (IGMP) join messages to it. The DR in turn sends a
single join message to the RP on behalf of all the downstream interested hosts.
The RP receives the first few packets of the multicast stream from the source hosts encapsulated in the
PIM register message. These messages are sent as a unicast to the RP. The RP removes the
encapsulation of these packets and forwards them to the subscribed DRs.
In addition to creating the shared tree, PIM-SM also provides the option to create a source-based tree
with the root at a router adjacent to the tree. This provides the destination hosts with an option of
switching to the source-based tree when it provides a shorter path from the multicast source. This helps
optimize the traffic flow by removing the extra hops.
NOTE
Each PIM-enabled node in the fabric should be connected with the RP.
PIM support with VDX switches is not provided for the following:

53-1003501-01
35
Configuring PIM-SM Multicast
Non Stop Routing (NSR)

More than 30 PIM out-interfaces (OIFs)
GVLAN or VXLAN
Support will be added in a subsequent NOS release for the following features:
IP Version 6
Virtual Routing and Forwarding (VRF)
Prefix list
Switch as BSR candidate (VDX switch processes BSR messages in current release)
Switch as RP candidate
Configuring PIM-SM Multicast

Figure 5 illustrates the topology of the deployment demonstrated in this example.
FIGURE 5 PIM-SIM Topology
Note the following regarding this deployment:

Aggregation 1 has VCS ID of 11, L2/L3 PIM enabled, and OSPF enabled.
Access 1 has VCS ID 10, L2 enabled, and IGMP enabled on VLANs in which receivers are
attached.
Access 2 has VCS ID 12, L2/L3 L2 on DX9 and VDX10 and L3 on other nodes with OSPF, PIM
enabled for L3 multicast, IGMP is enabled on all nodes on VLANs in which receivers are attached.
36

53-1003501-01
Procedure Summary
In the above topology, the source is attached to Access 1 in VLAN 100 from 20.1.1.3 to Group
225.0.0.10 to 225.0.0.19. Layer 2 VLAN 100 is enabled on Access1, and Layer 3 PIM is enabled on
Aggregation in that VLAN 100. Three receivers are attached.
One receiver is attached in Datacenter 1 on VLAN 120 by enabling IGMP snooping on VLAN 120 in
Access 1 and IP and PIM on Aggregation 1.
A second receiver is attached in Datacenter 2 on VLAN 150 by enabling IGMP snooping on VLAN
150 on VDX 9 and VDX 10 and by enabling Layer 3 with PIM on VDX7 and VDX8 on VLAN 150 and
VLANs 160 and 161 to Core2.
The third receiver is attached to Datacenter 2 in VLAN 200 by enabling IGMP snooping on Access 2
and Layer 3 and PIM on Core2.
MSDP anycast-RP is established between MLX1 and MLX2 in the same PIM domain. MSDP peering is
established from MLX1 and MLX2 to MLX3 in a different PIM domain.
Procedure Summary
Step 1: Configure Layer 2 VLANs.
Configure a Layer 2 VLAN 100 in Access 1 with ports connected to the source on VDX3 and VDX4
tagged to it. Tag the port channel connected to Aggregation1 in that VLAN.
Configure Layer 2 VLAN 100 on Aggregation 1 and tag the port channel to Access 1 in that VLAN.
Configure Layer 2 VLANS 101 and 103 on VDX5 and tag ports connected to MLX1 and MLX2 in
those VLANs respectively.
Configure Layer 2 VLANs 102 and 104 on VDX6 and tag ports connected to MLX1 and MLX2
respectively.
Step 2: Enable OSPF, VRRP-E and PIM.
Enable OSPF, VRRP-E and PIM globally in the Aggregation layer. OSPF, VRRP-E and PIM are
enabled on VE interface (VE 100) of the Aggregation layer on ports connected to Access 1.
OSPF and PIM is enabled on VE interfaces (VE 101, 102, 103, 104) to Core 1 on the respective VE
interfaces.
OSPF and PIM are enabled on ports from VDX 7 and VDX 8 connected to Core 2 in different VLANs
(VLAN 160, 161).
Step 3: Establish OSPF neighbors in Area 1 and Area 2.
Because IPV4 multicast with BGP is not supported in NOS 4.0.1, OSPF neighborship is established
between Aggregation1 and Core 1 (MLX-1 and MLX-2) in OSPF Area 1.
NOTE
This does not apply to Release 5.0.0 and later, which support IPv4 multicast with BGP.
OSPF neighborship is established between CORE 2 (MLX-3) and Access 2 (VDX7 and VDX8) in
OSPF Area 2.
PIM neighborship is established between Aggregation 1 and Core 1 (MLX-1 and MLX-2) and
between Access 2 (VDX7 and VDX8) and Core 2 (MLX-3).
Step 4: Establish OSPF neighbors in Area 0.
OSPF neighborship is established between MLX1, MLX2, MLX3 in Area 0.
IP PIM-Sparse is enabled on interfaces connecting MLX1, MLX2, and MLX3. IP PIM border is
configured on interfaces between MLX-1 to MLX-3 and MLX-2 to MLX-3 to differentiate PIM
domains.
Step 5: Establish MSDP peers.

53-1003501-01
37
Detailed Procedure with Examples
MSDP peering is established between MLX1, MLX2, and MLX3 with MSDP anycast RP between
MLX1 and MLX2 for load-balancing in the same PIM domain. With MSDP, individual source-group
pairs can be filtered in Source-Active messages.
Step 6: Configure Layer 2 VLANs on Access 1 and Access 2 with IGMP snooping.
Configure Layer 2 VLANs 120 and 200 on Access 1 and Access 2 respectively with IGMP snooping
enabled on them.
Add the ports on VDX 3, 4, and VDX 9, 10 connected to receivers in those VLANs respectively.
Add the ports connected to Aggregation 1 from Access 1 and Core 2 from Access 2 in those VLANs
with VE interfaces after adding IP address, OSPF, PIM on Aggregation 1 and Core 2 and VRRP-E
on Aggregation 1.
Step 7: Configure another Layer 2 VLAN 150 on Access2 with IGMP snooping.
Configure another Layer 2 VLAN 150 on Access2 with ports connected to Receivers on VDX 9 and
10 tagged in that VLAN with IGMP snooping.
Configure VE interface with OSPF, VRRP-E, IP address, and PIM on VDX 7 and VDX 8.
Step 8: Start the receivers.
Start the receivers to send IGMP joins.
Verify the IGMP group membership on all nodes.
Run the source traffic and verify traffic forwarding.

Configure Layer 2 VLAN 100 in Access 1 with ports connected to the Source on VDX3 and VDX4
tagged to it. Also, tag the port channel connected to Aggregation1 in that VLAN. VLAN should be
configured globally from the principal switch.
To configure PIM-SM Multicast in the example fabric, complete the following steps.
Procedure
Step 1: Configure VLANs.
Step 2: Configure VDX3-Access3 VLAN.
VDX3-Access3# interface Vlan 100 <- Enabling VLAN 100
Access1: Adding ports connected to source and port-channel connected to Aggregation Layer
in Layer 2 VLAN
VDX4-Access4# show run int ten 102/0/33
interface TenGigabitEthernet 102/0/33
fabric isl enable
fabric trunk enable
switchport
switchport mode trunk
switchport trunk allowed vlan add 100 <- Port is tagged to VLAN 100
switchport trunk tag native-vlan
no shutdown
!
fabric isl enable
fabric trunk enable
switchport
switchport trunk allowed vlan add 100
no shutdown
38

53-1003501-01
!
fabric isl enable
fabric trunk enable
switchport
no shutdown
!
fabric isl enable
fabric trunk enable
switchport
no shutdown
!
VDX4-Access4# show run int port-channel 50
vlag ignore-split
speed 40000
switchport
no shutdown
!
VDX4-Access4#
Step 3: Configure VLANs and tag ports.

Configure Layer 2 VLAN 100 on Aggregation 1 and tag the port-channel to Access 1 in that VLAN.
Configure Layer 2 VLANS 101 and 103 on VDX5 and tag ports connected to MLX1 and MLX2 in those
VLANs respectively.
Configure Layer 2 VLANs 102 and 104 on VDX6 and tag ports connected to MLX1 and MLX2
respectively. Enable OSPF, VRRP-E and PIM globally on the Aggregation layer. OSPF, VRRP-E and
PIM are enabled on VE interface (VE 100) of the Aggregation layer on the ports connected to Access 1.
OSPF and PIM are enabled on VE interfaces (VE 101, 102, 103, 104) to Core 1 on the respective VE
interfaces. Similarly OSPF and PIM are enabled on ports from VDX 7 and VDX 8 connected to Core 2
in different VLANs (VLAN 160, 161). VLAN and tagging interface are configured globally from the
principal switch.
Step 4: Configure VDX6-Agr2 VLAN.
VDX6-Agr2# interface Vlan 100 <- Enabling VLAN 100
interface Vlan 102
<- Enabling VLAN 102
interface Vlan 104
<- Enabling VLAN 104
Step 5: Configure port channels and interface VLAN tagging (VDX6-Agr2)

vlag ignore-split
speed 40000
switchport
switchport trunk allowed vlan add 100 <- Tagging to vlan 100
no shutdown
fabric isl enable
fabric trunk enable
switchport

53-1003501-01
39
Configuring OSPF, PIM, and VRRP-E

no shutdown
fabric isl enable
fabric trunk enable
switchport
no shutd
no shutdown
fabric isl enable
fabric trunk enable
switchport
no shutdown
<- Tagging to vlan 104

fabric isl enable
fabric trunk enable
switchport
no shutdown
Configuring OSPF, PIM, and VRRP-E

Complete the following steps to configure OSPF , PIM, and VRRP-E from the principal switch under
rbridge-id.
Procedure
Step 1: Configure OSPF, PIM, and VRRP-E on VDX5-Agr1.
router ospf <- Enabling OSPF
area 1 <-Configuring Area 1
router pim <- Enabling PIM
rp-address 11.11.11.11 <-Configuring static RP
protocol vrrp-extended <-Configuring VRRP-E
!
Step 2: Configure OSPF, PIM, and VRRP-E on VDX6-Agr2.

Step 3: Configure interface OSPF, PIM, and VRRP-E on VDX5-Agr1.

interface Ve 100
ip ospf area 1 <-OSPF area 1 is configured
ip ospf cost 20 <-OSPF cost is configured
ip ospf priority 255 <- Priority is configured for DR election
ip proxy-arp
ip address 20.1.1.4/25 <- IP address is configured
ip pim-sparse <- PIM-SM is enabled
vrrp-extended-group 100 <- VRRP-E is enabled with VRID 100
virtual-ip 20.1.1.1 <- Virtual-IP is configured and will be used as gateway from
Source
40

53-1003501-01
Configuring Access 2 VLAN and Protocol
enable <- VRRP-E is activated

no preempt-mode
short-path-forwarding <- Will allow the backup node to send traffic if it is
received
instead of going through master
interface Ve 101
ip proxy-arp
interface Ve 103
ip ospf area 1
ip ospf cost 10 <- Cost is 10
ip proxy-arp
! !
Step 4: Configure interface OSPF, PIM, and VRRP-E on VDX6-Agr2.

interface Ve 100
ip ospf priority 254 <- Priority is configured for DR election
ip proxy-arp
vrrp-extended-group 100 <- VRRP-E is enabled with VRID 100
virtual-ip 20.1.1.1 <- Virtual-IP is configured and will be used as gateway from
Source
enable <- VRRP-E is activated
no preempt-mode
short-path-forwarding <- Will allow the backup node to send traffic if it is
received
instead of going through master
interface Ve 102
ip proxy-arp
interface Ve 104
ip ospf area 1
ip ospf cost 10<- Cost is 10
ip proxy-arp
Configuring Access 2 VLAN and Protocol

To Configure Access 2 VLAN and protocol, complete the following steps.
Procedure
Step 1: Configure VLAN globally from principal switch VDX10.
VDX10-Access10 VLAN configuration
VDX10-ACCess10# interface Vlan 160 <- Enabling VLAN 160
Configure OSPF, PIM, VRRP-E from principal switch under rbridge-id.

Step 2: Configure OSPF, PIM, and VRRP-E on VDX7-Access7.

53-1003501-01
41

!
Step 3: Configure OSPF, PIM, and VRRP-E on VDX8-Access8.

Step 4: Configure interface OSPF, PIM, and VRRP-E on VDX7-Access7.

interface Ve 160
ip proxy-arp
Step 5: Configure interface OSPF, PIM, and VRRP-E on VDX8-Access8.

interface Ve 161
ip proxy-arp
Step 6: Establish OSPF and PIM neighbors.

Because IPV4 multicast with BGP is not supported in NOS 4.0.1, OSPF neighborship is established
between Aggregation1 and Core 1 (MLX-1 and MLX-2) in OSPF Area 1 and OSPF neighborship is
established between CORE 2 (MLX-3) and Access 2 (VDX7 and VDX8) in OSPF Area 2. PIM
neighborship is established between Aggregation 1 and Core 1 (MLX-1 and MLX-2) and between
Access 2 (VDX7 and VDX8) and Core 2(MLX-3).
Step 7: Configure MLX1 VLAN.
vlan 101 <- VLAN config
tagged ethernet 3/7 <-Tagged interface
router-interface ve 101 <- VE interface

tagged ethe 4/7 <-Tagged interface
router-interface ve 104<- VE interface

vlan 160 <- VLAN configuration
tagged ethernet 1/1 <- Tagged interface
vlan 161 <- VLAN configuration
Step 10: Configure OSPF and PIM on MLX1.

area 0 <- Areas 0 and 1 are configured
area 1
log adjacency

rp-address 11.11.11.11 <- Static RP
42

53-1003501-01
OSPF Configuration
! !
router ospf
<- Enabling OSPF
area 1
log adjacency
rp-address 11.11.11.11 <- Static RP

area 2
log adjacency
rp-address 11.11.11.11 <- Static
RP
Step 13: Configure OSPF and PIM on the MLX1 interface.

interface ve 101
ip ospf area 1 <- OSPF area 1
ip address 2.1.1.2/25 <- IP address
ip pim-sparse <- PIM-SM is configured
interface ve 102
ip pim-sparse <- IP address
!

interface ve 103
ip ospf area 1 <- OSPF area
ip address 3.1.1.2/25 <- IP
ip pim-sparse
interface ve 104
ip ospf area 1 <- OSPF area
ip address 3.2.1.2/25 <- IP
ip pim-sparse <- IP address
1
address
1
address

interface ve 160
ip ospf cost 5 <- OSPF cost 5, picks better cost path
interface ve 161
ip ospf cost 10 <- OSPF cost 10
!!
OSPF Configuration
To establish OSPF neighbors in the VCS fabric, complete the following steps.
Procedure
Step 1: Establish OSPF neighbors in Area 0.
OSPF neighborship is established between MLX1, MLX2, and MLX3 in Area 0. IP PIM-Sparse is
enabled on interfaces connecting MLX1, MLX2, and MLX3 and IP PIM border is configured on
interfaces between MLX-1 to MLX-3 and MLX-2 to MLX-3 to differentiate PIM domains.
Step 2: Configure OSPF, PIM and router-id on the MLX1 interface.
interface ethernet 3/2
enable
ip ospf cost 5

53-1003501-01
43

ip pim-sparse <- PIM-SM
ip pim border <- PIM border command to separate PIM domains
enable
ip ospf priority 255
interface loopback 2 <- Unique loopback address
ip ospf passive <- OSPF passive interface
interface loopback 1 <- Common loopback address used as RP and for MSDP
ip address 11.11.11.11/32 <- Common IP address
ip router-id 22.22.22.22 <- router-id with unique address
!! !
Step 3: Configure OSPF, PIM and router-id on the MLX2 interface.

enable
enable
ip ospf area 0- OSPF area 0
ip ospf cost 10
ip address 11.11.11.11/32 <-Common IP address
Step 4: Configure OSPF, PIM, and router-id on the MLX3 interface.

enable
ip ospf cost 5
enable
ip ospf cost 10
Step 5: Establish MSDP peers.

MSDP peering is established between MLX1, MLX2 and MLX3 with MSDP anycast RP between MLX1
and MLX2 for load-balancing in the same PIM domain. With MSDP, individual source-group pair can
be filtered in Source-Active messages.
44

53-1003501-01
Configuring VE Interfaces
Step 6: Configure MSDP on MLX1.

router msdp
msdp-peer 44.44.44.44 connect-source loopback 2 <- Two MSDP peers are configured to
MLX2
and MLX3 with unique loopback address loopback 2
msdp-peer 33.33.33.33 connect-source loopback 2
originator-id loopback 2 <- Loopback2s IP address will be used as RP address in SA
message
router msdp

MLX1
originator-id loopback 2 <-Loopback2s IP address will be used as RP address in SA
message
router msdp

MLX1
originator-id loopback 2 <-Loopback2s IP address will be used as RP address in SA
message
Step 9: Configure Layer 2 VLANs with IGMP snooping.

enabled on them. Add the ports on VDX 3, 4 and VDX 9, 10 connected to receivers in those VLANs
respectively. Add the ports connected to Aggregation 1 from Access 1 and Core 2 from Access 2 in
those VLANs with VE interfaces after adding the IP address, OSPF, PIM on Aggregation 1 and Core 2
and VRRP-E on Aggregation 1. VLANs and interface configurations are configured from principal switch
globally.
Step 10: Configuring VLAN (IGMP) on VDX1-Access1.
ip igmp snooping enable <- IGMP snooping is enabled to receive IGMP joins
Step 11: Configure VLAN (IGMP) on VDX2-Access2.



fabric isl enable
fabric trunk enable
switchport
switchport trunk allowed vlan add 100,120 <- Tagged to Vlan 100 and 120 to attach to
source
and receiver
no shutdown
Configuring VE Interfaces
To configure VE interface from principal switch under rbridge-id, complete the following steps.

53-1003501-01
45
Procedure
Step 1: Configure VLAN (IGMP) on VDX5-Agr1.
interface Ve 120
ip proxy-arp
ip address 40.1.1.1/25 <-Unique IP address
ip pim-sparse<-PIM-SM
no shutdown<-VE interface is enabled
vrrp-extended-group 120<-VRRP-E is configured with VRID 120
virtual-ip 40.1.1.4<-Virtual-IP is configured to be used as Gateway for the host
from
which joins are sent
enable<-VRRP-E is activated
no preempt-mode
short-path-forwarding<-To make the node to forward traffic when it receives instead
of going
through VRRP-E master
short-
Step 2: Configure VLAN (IGMP) on VDX6-Agr2.

interface Ve 120
ip proxy-arp
ip address 40.1.1.3/25<- Unique IP address
from
no preempt-mode
short-path-forwarding<-To make the node to forward traffic when it receives
instead of
going through VRRP-E master

interface Ve 150
ip ospf area 2<-OSPF area 2 is configured
ip ospf priority 255<- Priority to decide DR
ip proxy-arp
ip address 45.1.1.2/25<-Unique IP address
virtual-ip 45.1.1.1 <-Virtual-IP is configured to be used as Gateway for the host
from
no preempt-mode
instead of

interface Ve 150
ip ospf area 2<-OSPF area 2 is configured
ip ospf priority 254<- Priority to decide DR
ip proxy-arp
ip address 45.1.1.3/25 <-Unique IP address
46

53-1003501-01
Verifying OSPF and PIM
from
no preempt-mode
instead of


Step 7: Configure VLAN on Access2 with ports connected to receivers with IGMP snooping.
Configure another Layer 2 VLAN 150 on Access2 with ports connected to Receivers on VDX 9 and 10
tagged in that VLAN with IGMP snooping.
Configure VE interface with OSPF, VRRP-E, IP address, and PIM on VDX 7 and VDX 8.



switchport
switchport trunk allowed vlan add 150,200 <- Tagged to Vlan 150 and 200
no shutdown
Step 12:
vlan 200 <- VLAN 200
interface ve 200
ip address 30.1.1.1/25 <- IP address connected to host through Access 2
ip pim-sparse <- PIM-SM which will enable IGMP by default
Verifying OSPF and PIM

To verify OSPF, complete the following steps.
Procedure
Step 1: Verify OSPF on MLX1.
Core1-MLX1#show ip os neighbor
Port
Address
Pri State
Neigh Address
3/2
5.1.2.1
1
FULL/DR
5.1.2.2

53-1003501-01
Neigh ID
44.44.44.44
Ev Opt Cnt
6 66 0
47
3/4
v101
v102
6.1.1.1
2.1.1.2
2.2.1.2
254 FULL/DR
1
FULL/BDR
1
FULL/DR
6.1.1.2
2.1.1.1
2.2.1.1
33.33.33.33
2.1.1.1
20.1.1.2
5
4
6
66
2
2
0
0
0

Core1-MLX2#show ip ospf neighbor
Port
Cnt
4/4
4/5
v103
v104
Address
Pri State
Neigh Address
Neigh ID
Ev Opt
6.1.1.2
5.1.3.1
3.1.1.2
3.2.1.2
255
1
1
1
6.1.1.1
5.1.3.2
3.1.1.1
3.2.1.1
22.22.22.22
44.44.44.44
2.1.1.1
20.1.1.2
5
5
5
6
FULL/BDR
FULL/DR
FULL/BDR
FULL/DR
66
66
2
2
0
0
0
0

Port
Cnt
1/2
1/5
v160
v161
Address
Pri State
Neigh Address
Neigh ID
Ev
5.1.2.2
5.1.3.2
7.1.1.2
7.2.1.2
1
1
1
1
5.1.2.1
5.1.3.1
7.1.1.1
7.2.1.1
22.22.22.22
33.33.33.33
45.1.1.2
45.1.1.3
5
5
17
16
FULL/BDR
FULL/BDR
FULL/DR
FULL/DR
Opt
66
66
2
2
0
0
0
0
Step 4: Verify OSPF on VDX5-Agr1.

Port
Ev
Cnt
Ve 101
5
Ve 103
6
Ve 100
5
Ve 120
7
Opt
2
Address
Pri State
Neigh Address
Neigh ID
2.1.1.1
FULL/DR
2.1.1.2
22.22.22.22
3.1.1.1
FULL/DR
3.1.1.2
33.33.33.33
20.1.1.4
254 FULL/DR
20.1.1.2
20.1.1.2
40.1.1.1
40.1.1.3
20.1.1.2
FULL/DR
Step 5: Verify OSPF on VDX6-Agr2.

Port
Ev
Cnt
Ve 100
4
Ve 120
4
Ve 102
5
Ve 104
4
Opt
2
Address
Pri State
Neigh Address
Neigh ID
20.1.1.2
255 FULL/BDR
20.1.1.4
2.1.1.1
40.1.1.3
FULL/BDR
40.1.1.1
2.1.1.1
2.2.1.1
FULL/BDR
2.2.1.2
22.22.22.22
3.2.1.1
FULL/BDR
3.2.1.2
33.33.33.33
Step 6: Verify OSPF on VDX7-Access7.

Port
Ev
Cnt
Ve 150
7
Ve 160
10
Opt
2
Address
Pri State
Neigh Address
Neigh ID
45.1.1.2
254 FULL/BDR
45.1.1.3
45.1.1.3
7.1.1.1
7.1.1.2
44.44.44.44
FULL/BDR
Step 7: Verify OSPF on VDX8-Access8.

Port
Ev
Cnt
Ve 150
48
Opt
Address
Pri State
Neigh Address
Neigh ID
45.1.1.3
255 FULL/DR
45.1.1.2
45.1.1.2

53-1003501-01
8
Ve 161
2
02
2
0
7.2.1.1
FULL/BDR
7.2.1.2
44.44.44.44
10
Step 8: Verify PIM on MLX1.

Core1-MLX1#show ip pim neighbor
--------+--------+---------------+--------+---+---------+---------+----+----------------+----------+----+
Port
|PhyPort |Neighbor
|Holdtime|T |PropDelay|Override |Age |
UpTime
|VRF
|Prio
|
|
|sec
|Bit|msec
|msec
|sec
|
|
|
--------+--------+---------------+--------+---+---------+---------+----+----------------+----------+----+
e3/2
e3/2
5.1.2.2
105
1
500
3000
19
1d
23:04:51
default
1
e3/4
e3/4
6.1.1.2
105
1
500
3000
10
23:29:16
default
1
v101
e3/7
2.1.1.1
105
1
500
3000
28
1d
01:09:38
default
1
v102
e3/3
2.2.1.1
105
1
500
3000
19
1d
00:47:57
default
1
Total Number of Neighbors : 4
Core1-MLX1#show ip pim rp-set
Static RP
--------Static RP count: 1
11.11.11.11 <- Static RP
Number of group prefixes Learnt from BSR: 0
No BSR RP-Set present.
Core1-MLX1#show ip pim sparse
Global PIM Sparse Mode Settings
Maximum Mcache
: No limit
Current Count
:
Hello interval
: 30
Neighbor timeout
:
Join/Prune interval
: 60
Inactivity interval
:
Hardware Drop Enabled : Yes
Prune Wait Interval
:
Bootstrap Msg interval : 60
Candidate-RP Msg interval :
Register Suppress Time : 60
Register Probe Time
:
Register Stop Delay
: 60
Register Suppress interval :
SSM Enabled
: No
SPT Threshold
:
Route Precedence
: mc-non-default mc-default uc-non-default
10
105
180
3
60
10
60
1
uc-default
Core1-MLX1#show ip pim interface

---------+---------------+----+---+---------------------+---+---------+--------------+------+------+---------+
Interface|Local
|Ver |St | Designated Router |TTL|Multicast|
Filter
|
VRF | DR
| Override
|Address
|
|
|Address
Port|Thr|Boundary |
ACL
|
| Prio | Interval
---------+---------------+----+---+---------------------+---+---------+--------------+------+------+---------+
e3/2 5.1.2.1
SMv2 Ena 5.1.2.2
3/2
1 None
None
default 1
3000ms
e3/4 6.1.1.1
SMv2 Ena 6.1.1.2
3/4
1 None
None
default 1
3000ms
v101 2.1.1.2
SMv2 Ena Itself
1 None
None
default 1
3000ms
v102 2.2.1.2
SMv2 Ena Itself
1 None
None

53-1003501-01
49
default 1
3000ms
l1 11.11.11.11
SMv2 Ena Itself
None
default 1
3000ms
Total Number of Interfaces : 5
1 None

--------+--------+---------------+--------+---+---------+---------+----+----------------+
-----------+----+
Port
|PhyPort |Neighbor
UpTime
|VRF
|Prio
|
|
|sec
|Bit|msec
|msec
|sec
|
|
|
--------+--------+---------------+--------+---+---------+---------+----+----------------+
-----------+----+
e4/4
e4/4
6.1.1.1
105
1
500
3000
14
23:29:46
default
1
e4/5
e4/5
5.1.3.2
105
1
500
3000
8
23:26:15
default
1
v103
e4/1
3.1.1.1
105
1
500
3000
24
23:24:27
default
1
v104
e4/7
3.2.1.1
105
1
500
3000
20
23:24:24
default
1
Static RP
11.11.11.11 <- Static RP
Maximum Mcache
: No limit
Current Count
:
Hello interval
: 30
Neighbor timeout
:
Join/Prune interval
: 60
Inactivity interval
:
Prune Wait Interval
:
Register Probe Time
:
Register Stop Delay
: 60
SSM Enabled
: No
SPT Threshold
:
Route Precedence
20
105
180
3
60
10
60
1
uc-default

---------+---------------+----+---+---------------------+---+--------+---------------+------+------+---------+
Interface|Local
|Ver |St | Designated Router |TTL|Multicast|
Filter
|
VRF | DR
| Override
|Address
|
|
|Address
Port|Thr|Boundary |
ACL
|
| Prio | Interval
---------+---------------+----+---+---------------------+---+--------+---------------+------+------+---------+
e4/4 6.1.1.2
SMv2 Ena Itself
1 None
None
default 1
3000ms
e4/5 5.1.3.1
SMv2 Ena 5.1.3.2
4/5
1 None
None
default 1
3000ms
50

53-1003501-01
v103 3.1.1.2
SMv2 Ena Itself
None
default 1
3000ms
v104 3.2.1.2
SMv2 Ena Itself
None
default 1
3000ms
l1 11.11.11.11
SMv2 Ena Itself
None
default 1
3000ms
1 None
1 None
1 None

--------+--------+---------------+--------+---+---------+---------+----+----------------+
-----------+----+
Port
|PhyPort |Neighbor
UpTime
|VRF
|Prio
|
|
|sec
|Bit|msec
|msec
|sec
|
|
|
--------+--------+---------------+--------+---+---------+---------+----+----------------+----------+----+
e1/2
e1/2
5.1.2.1
105
1
500
3000
17
21:29:19
default
1
e1/5
e1/5
5.1.3.1
105
1
500
3000
8
20:57:05
default
1
v160
e1/1
7.1.1.1
105
1
500
3000
6
20:57:05
default
1
v161
e1/6
7.2.1.1
105
1
500
3000
7
20:57:05
default
1
Static RP
11.11.11.11 <- Static RP
Maximum Mcache
: No limit
Current Count
:
Hello interval
: 30
Neighbor timeout
:
Join/Prune interval
: 60
Inactivity interval
:
Prune Wait Interval
:
Register Probe Time
:
Register Stop Delay
: 60
SSM Enabled
: No
SPT Threshold
:
Route Precedence
20
105
180
3
60
10
60
1
uc-default

---------+---------------+----+---+---------------------+---+---------+-------+-----+--------+
Interface|Local
|Ver |St | Designated Router |TTL|Multicast| VRF | DR
|
Override
|Address
|
|
|Address
Port|Thr|Boundary |
| Prio
|
Interval
---------+---------------+----+---+---------------------+---+---------+-------+-----+--------+

53-1003501-01
51
e1/2 5.1.2.2
SMv2
1
3000ms
e1/5 5.1.3.2
SMv2
1
3000ms
v160 7.1.1.2
SMv2
1
3000ms
v161 7.2.1.2
SMv2
1
3000ms
v200 30.1.1.1
SMv2
1
3000ms
l1 11.11.11.11
SMv2
1
3000ms
Ena Itself
1 None
default
Ena Itself
1 None
default
Ena Itself
1 None
default
Ena Itself
1 None
default
Ena Itself
1 None
default
Ena Itself
1 None
default
Step 11: Verify PIM on VDX5-Agr1.

VDX5-Agr1# show ip pim neighbor
Port
Phy_Port
Neighbor
Ve
Ve
Ve
Ve
100
101
103
120
Ve
Ve
Ve
Ve
100
101
103
120
20.1.1.2
2.1.1.2
3.1.1.2
40.1.1.3
Holdtime
sec
105
105
105
105
Age
sec
21
17
2
4
UpTime
Dd HH:MM:SS
21:02:49
1d 01:22:36
23:36:58
20:37:32
Priority
1
1
1
1
VDX5-Agr1# show ip pim rp-set

Static RP
RP: 11.11.11.11 <- Static RP
VDX5-Agr1# show ip pim-sparse
Maximum mcache
: 2048 Current count
: 10
Hello interval
: 30
Neighbor timeout
: 105
Join/Prune interval
: 60
Inactivity interval
: 180
Hardware drop enabled
: Yes Prune wait interval
: 3
Register Suppress Time
: 60
Register Probe Time
: 10
Register Stop Delay
: 60
Register Suppress interval : 60
SSM Enabled
: No
SPT Threshold
: 1
-------------+---------------+----+-----+------------------------------+---+--------+----Interface
|Local
|Ver |Mode |
Designated Router
|TTL|
Multicast| DR
|Address
|
|
|Address
Port
|Thr|Boundary
| Prio
-------------+---------------+----+-----+------------------------------+---+--------+----Ve 100
20.1.1.4
v2SM SM
Itself
1
None
1
Ve 101
2.1.1.1
v2SM SM
2.1.1.2
Ve 101
1
None
1
Ve 103
3.1.1.1
v2SM SM
3.1.1.2
Ve 103
1
None
1
Ve 120
40.1.1.1
v2SM SM
40.1.1.3
Ve 120
1
None
1
VDX5-Agr1# show ip pim rpf 11.11.11.11
upstream nbr 2.2.1.2 on Ve 102 <- It points to VE 102 connected to MLX1 and it will
not do
ECMP
Step 12: Verify PIM on VDX6-Agr2.

VDX6-Agr2# show ip pim neighbor
Port
Phy_Port
Neighbor
52
Holdtime Age
sec
sec
UpTime
Dd HH:MM:SS
Priority

53-1003501-01
Ve
Ve
Ve
Ve
100
102
104
120
Ve
Ve
Ve
Ve
100
102
104
120
20.1.1.4
2.2.1.2
3.2.1.2
40.1.1.1
105
105
105
105
13
30
23
27
21:04:14
1d 01:02:20
23:38:19
20:38:58
1
1
1
1
VDX6-Agr2# show ip pim rp-set

Static RP
RP: 11.11.11.11 <- Static RP
VDX6-Agr2# show ip pim-sparse
Maximum mcache
: 20
Hello interval
: 30
Neighbor timeout
: 105
Join/Prune interval
: 60
Inactivity interval
: 180
: 3
: 60
Register Probe Time
: 10
Register Stop Delay
: 60
SSM Enabled
: No
SPT Threshold
: 1
-------------+---------------+----+-----+------------------------------+---+--------+-----Interface
|Local
|Ver |Mode |
Designated Router
|TTL|
Multicast| DR
|Address
|
|
|Address
Port
|Thr|Boundary
| Prio
-------------+---------------+----+-----+------------------------------+---+--------+-----Ve 100
20.1.1.2
v2SM SM
20.1.1.4
Ve 100
1
None
1
Ve 102
2.2.1.1
v2SM SM
2.2.1.2
Ve 102
1
None
1
Ve 104
3.2.1.1
v2SM SM
3.2.1.2
Ve 104
1
None
1
Ve 120
40.1.1.3
v2SM SM
Itself
1
None
1
VDX6-Agr2# show ip pim rpf 11.11.11.11
upstream nbr 2.1.1.2 on Ve 101 <- It points to VE 101 connected to MLX1 and it will
not do ECMP
Step 13: Verify PIM on VDX7-Access7.

VDX7-Access7# show ip pim neighbor
Port
Phy_Port
Neighbor
Ve 150
Ve 160
Ve 150
Ve 160
45.1.1.3
7.1.1.2
Holdtime
sec
105
105
Age
sec
21
27
UpTime
Dd HH:MM:SS
22:05:51
21:13:56
Priority
1
1
VDX7-Access7# show ip pim rp-set

Static RP
RP: 11.11.11.11 <- Static RP
VDX7-Access7# show ip pim-sparse
Maximum mcache
: 20
Hello interval
: 30
Neighbor timeout
: 105
Join/Prune interval
: 60
Inactivity interval
: 180
: 3
: 60
Register Probe Time
: 10
Register Stop Delay
: 60
SSM Enabled
: No
SPT Threshold
: 1
-------------+---------------+----+-----+------------------------------+---+--------+-----Interface
|Local
|Ver |Mode |
Designated Router
|TTL|
Multicast| DR
|Address
|
|
|Address
Port
|Thr|Boundary
| Prio

53-1003501-01
53
-------------+---------------+----+-----+------------------------------+---+--------+-----Ve 150
45.1.1.2
v2SM SM
45.1.1.3
Ve 150
1
None
1
Ve 160
7.1.1.1
v2SM SM
7.1.1.2
Ve 160
1
None
1
VDX7-Access7# show ip pim rpf 11.11.11.11
upstream nbr 7.1.1.2 on Ve 160 <- It shows the connected interface to MLX3
Step 14: Verify PIM on VDX8-Access8.

VDX8-Access8# show ip pim neighbor
Port
Phy_Port
Neighbor
Ve 150
Ve 161
Ve 150
Ve 161
45.1.1.2
7.2.1.2
Holdtime
sec
105
105
Age
sec
3
7
UpTime
Dd HH:MM:SS
22:07:02
21:15:06
Priority
1
1
VDX8-Access8# show ip pim rp-set

Static RP
RP: 11.11.11.11 <- Static RP
VDX8-Access8# show ip pim-sparse
Maximum mcache
: 20
Hello interval
: 30
Neighbor timeout
: 105
Join/Prune interval
: 60
Inactivity interval
: 180
: 3
: 60
Register Probe Time
: 10
Register Stop Delay
: 60
SSM Enabled
: No
SPT Threshold
: 1
-------------+---------------+----+-----+------------------------------+---+--------+-----Interface
|Local
|Ver |Mode |
Designated Router
|TTL|
Multicast| DR
|Address
|
|
|Address
Port
|Thr|Boundary
| Prio
-------------+---------------+----+-----+------------------------------+---+--------+-----Ve 150
45.1.1.3
v2SM SM
Itself
1
None
1
Ve 161
7.2.1.1
v2SM SM
7.2.1.2
Ve 161
1
None
1
VDX8-Access8# show ip pim rpf 11.11.11.11
upstream nbr 45.1.1.2 on Ve 150 <- It shows the interface connected to VDX7 as OSPF
cost is
10 on the link connected to MLX3.
Step 15: Verify MSDP on MLX1.

Core1-MLX1#show ip msdp summary
MSDP Peer Status Summary
KA: Keepalive SA:Source-Active NOT: Notification
Peer Address
Peer As
State
KA
SA
NOT
In
Out
In
Out
In
Out
44.44.44.44
N/A
ESTABLISH 1307
1307
69
1389
0
0
33.33.33.33
N/A
ESTABLISH 1313
1313
70
1323
0
0
Core1-MLX1#
Core1-MLX1#show ip msdp peer
IP Address
State
Mesh-group-name
1
44.44.44.44
ESTABLISH
Keep Alive Time Hold Time
Age
60
75
15
Message Sent
Message Received
Keep Alive
1307
1307
Notifications
0
0
Source-Active
1389
69
Lack of Resource
0
Last Connection Reset Reason:Reason Unknown
Notification Message Error Code Received:Unspecified
Notification Message Error SubCode Received:Not Applicable
Notification Message Error Code Transmitted:Unspecified
54
Age
10
11

53-1003501-01
Notification Message Error SubCode Transmitted:Not Applicable

Local IP Address: 22.22.22.22
TCP Connection state: ESTABLISHED
Local host: 22.22.22.22, Local Port: 8704
Remote host: 44.44.44.44, Remote Port: 639
ISentSeq: 2253389345 SendNext: 2253565398 TotUnAck:
0
SendWnd:
65000 TotSent:
176053 ReTrans:
8
IRcvSeq: 2317398145 RcvNext: 2317410566 RcvWnd:
65000
TotalRcv:
12421 RcvQue:
0 SendQue:
0
Input SA Filter:Not Applicable
Input (S,G) route-map:None
Input RP route-map:None
Output SA Filter:Not Applicable
Output (S,G) route-map:None
Output RP route-map:None
2
IP Address
33.33.33.33
Keep Alive Time
60
State
Mesh-group-name
ESTABLISH
Hold Time
Age
75
17
Message Sent
Message Received
Keep Alive
1313
1313
Notifications
0
0
Source-Active
1323
70
Lack of Resource
0
0
SendWnd:
65000 TotSent:
172324 ReTrans:
0
65000
TotalRcv:
12660 RcvQue:
0 SendQue:
0

Peer Address
Peer As
State
KA
In
Out
22.22.22.22
N/A
ESTABLISH 1606
1607
44.44.44.44
N/A
ESTABLISH 1308
1308
SA
In
1438
1381
Out
72
1385
In
0
0
NOT
Out
0
0
Age
38
31

IP Address
State
Mesh-group-name
1
22.22.22.22
ESTABLISH
Age
60
75
3
Message Sent
Message Received
Keep Alive
1607
1606
Notifications
0
0
Source-Active
72
1439
Lack of Resource
0
0
SendWnd:
65000 TotSent:
12922 ReTrans:
0
65000
TotalRcv:
172714 RcvQue:
0 SendQue:
0

53-1003501-01
55

2
IP Address
44.44.44.44
Keep Alive Time
60
State
Mesh-group-name
ESTABLISH
Hold Time
Age
75
4
Message Sent
Message Received
Keep Alive
1308
1308
Notifications
0
0
Source-Active
1385
1382
Lack of Resource
0
0
SendWnd:
65000 TotSent:
176651 ReTrans:
8
65000
TotalRcv:
176507 RcvQue:
0 SendQue:
0

Peer Address
Peer As
State
KA
In
Out
22.22.22.22
N/A
ESTABLISH 1307
1311
33.33.33.33
N/A
ESTABLISH 1307
1310
SA
In
1394
1384
Out
72
1385
In
0
0
NOT
Out
0
0
Age
15
13

IP Address
State
Mesh-group-name
1
22.22.22.22
ESTABLISH
Age
60
75
19
Message Sent
Message Received
Keep Alive
1311
1307
Notifications
0
0
Source-Active
72
1394
Lack of Resource
0
0
SendWnd:
64997 TotSent:
12817 ReTrans:
6
65000
TotalRcv:
177089 RcvQue:
0 SendQue:
0
2
56
IP Address
33.33.33.33
Keep Alive Time
60
State
Mesh-group-name
ESTABLISH
Hold Time
Age
75
18

53-1003501-01
Starting the Receivers
Message Sent
Message Received
Keep Alive
1310
1307
Notifications
0
0
Source-Active
1385
1384
Lack of Resource
0
0
SendWnd:
64872 TotSent:
176897 ReTrans:
6
65000
TotalRcv:
176913 RcvQue:
0 SendQue:
0

Start the receivers to send IGMP joins and verify the IGMP group membership on all nodes. Run the
source traffic and verify the traffic forwarding.
To start the receivers, complete the following steps.
Procedure
Step 1: Verify IGMP on VDX1-Access1.
VDX1-Access1# show ip igmp groups
Total Number of Groups: 10
IGMP Connected Group Membership
Group Address
Interface
Uptime
Expires
Last Reporter
225.0.0.10
Vlan 120
20:37:56
00:03:49
40.1.1.2 <- Each Group
membership should have correct VLAN ID, Group address and host address
Member Ports: Te 103/0/33
225.0.0.11
Vlan 120
20:37:56
00:03:42
40.1.1.2
225.0.0.12
Vlan 120
20:37:56
00:03:48
40.1.1.2
225.0.0.13
Vlan 120
20:37:56
00:03:43
40.1.1.2
225.0.0.14
Vlan 120
20:37:56
00:03:42
40.1.1.2
225.0.0.15
Vlan 120
20:37:56
00:03:41
40.1.1.2
225.0.0.16
Vlan 120
20:37:56
00:03:49
40.1.1.2
225.0.0.17
Vlan 120
20:37:56
00:03:46
40.1.1.2
225.0.0.18
Vlan 120
20:37:56
00:03:47
40.1.1.2
225.0.0.19
Vlan 120
20:37:56
00:03:47
40.1.1.2
VDX1-Access1# show ip igmp interface
Interface Vlan 1
IGMP Snooping disabled
IGMP Snooping fast-leave disabled
IGMP Snooping querier disabled
Number of router-ports: 0
Interface Vlan 100

53-1003501-01
57

Interface Vlan 120
IGMP Snooping enabled <- VLAN 120 is enabled for IGMP

Group Address
Interface
225.0.0.10
Vlan 120
225.0.0.11
Vlan 120
225.0.0.12
Vlan 120
225.0.0.13
Vlan 120
225.0.0.14
Vlan 120
225.0.0.15
Vlan 120
225.0.0.16
Vlan 120
225.0.0.17
Vlan 120
225.0.0.18
Vlan 120
225.0.0.19
Vlan 120
Uptime
20:40:48
Expires
00:03:00
Last Reporter
40.1.1.2
20:40:48
00:02:59
40.1.1.2
20:40:48
00:02:56
40.1.1.2
20:40:48
00:02:53
40.1.1.2
20:40:48
00:02:53
40.1.1.2
20:40:48
00:03:01
40.1.1.2
20:40:48
00:02:55
40.1.1.2
20:40:48
00:02:52
40.1.1.2
20:40:48
00:02:54
40.1.1.2
20:40:48
00:03:00
40.1.1.2
Uptime
20:42:01
Expires
00:03:48
Last Reporter
40.1.1.2
20:42:01
00:03:46
40.1.1.2
20:42:01
00:03:49
40.1.1.2
20:42:01
00:03:52
40.1.1.2
20:42:01
00:03:46
40.1.1.2
20:42:01
00:03:47
40.1.1.2
20:42:01
00:03:46
40.1.1.2
20:42:01
00:03:52
40.1.1.2
20:42:01
00:03:47
40.1.1.2

Interface Vlan 1
Interface Vlan 100
Interface Vlan 120
IGMP Snooping enabled
Group Address
Interface
225.0.0.10
Vlan 120
225.0.0.11
Vlan 120
225.0.0.12
Vlan 120
225.0.0.13
Vlan 120
225.0.0.14
Vlan 120
225.0.0.15
Vlan 120
225.0.0.16
Vlan 120
225.0.0.17
Vlan 120
225.0.0.18
Vlan 120
58

53-1003501-01
225.0.0.19
Vlan 120
20:42:01
00:03:47
40.1.1.2
Uptime
20:43:43
Expires
00:04:11
Last Reporter
40.1.1.2
20:43:43
00:04:10
40.1.1.2
20:43:43
00:04:12
40.1.1.2
20:43:43
00:04:10
40.1.1.2
20:43:43
00:04:14
40.1.1.2
20:43:43
00:04:15
40.1.1.2
20:43:43
00:04:12
40.1.1.2
20:43:43
00:04:14
40.1.1.2
20:43:43
00:04:11
40.1.1.2
20:43:43
00:04:10
40.1.1.2
Uptime
20:46:27
Expires
00:03:33
Last Reporter
40.1.1.2
20:46:27
00:03:30
40.1.1.2

Interface Vlan 1
Interface Vlan 100
Interface Vlan 120
Group Address
Interface
225.0.0.10
Vlan 120
225.0.0.11
Vlan 120
225.0.0.12
Vlan 120
225.0.0.13
Vlan 120
225.0.0.14
Vlan 120
225.0.0.15
Vlan 120
225.0.0.16
Vlan 120
225.0.0.17
Vlan 120
225.0.0.18
Vlan 120
225.0.0.19
Vlan 120

Interface Vlan 1
Interface Vlan 100
Interface Vlan 120
Step 5: Verify IGMP on VDX5-Agr1.

VDX5-Agr1# show ip igmp groups
Group Address
Interface
225.0.0.10
Vlan 120
Member Ports: Po 50
225.0.0.11
Vlan 120
Member Ports: Po 50

53-1003501-01
59
225.0.0.12
Member Ports:
225.0.0.13
Member Ports:
225.0.0.14
Member Ports:
225.0.0.15
Member Ports:
225.0.0.16
Member Ports:
225.0.0.17
Member Ports:
225.0.0.18
Member Ports:
225.0.0.19
Member Ports:
Vlan
Po 50
Vlan
Po 50
Vlan
Po 50
Vlan
Po 50
Vlan
Po 50
Vlan
Po 50
Vlan
Po 50
Vlan
Po 50
120
20:46:27
00:03:38
40.1.1.2
120
20:46:27
00:03:37
40.1.1.2
120
20:46:27
00:03:31
40.1.1.2
120
20:46:27
00:03:29
40.1.1.2
120
20:46:27
00:03:36
40.1.1.2
120
20:46:27
00:03:33
40.1.1.2
120
20:46:27
00:03:30
40.1.1.2
120
20:46:27
00:03:38
40.1.1.2
VDX5-Agr1# show ip igmp interface

Interface Vlan 1
Interface Vlan 100
Interface Vlan 101
Interface Vlan 102
Interface Vlan 103
Interface Vlan 104
Interface Vlan 120
RbridgeId: 200
Interface Ve 100
IGMP enabled
IGMP query interval 125 seconds
IGMP other-querier interval 255 seconds
IGMP query response time 10 seconds
IGMP last-member query interval 1000 milliseconds
IGMP immediate-leave disabled
IGMP querier 20.1.1.2(other system) <- IGMP querier is Agr2
IGMP version 2
Interface Ve 101
IGMP enabled
60

53-1003501-01
IGMP
IGMP
IGMP
IGMP
IGMP
query response time 10 seconds

last-member query interval 1000 milliseconds
immediate-leave disabled
querier 2.1.1.1(this system)
version 2
Interface Ve 103
IGMP enabled
IGMP querier 3.1.1.1(this system)
IGMP version 2
Interface Ve 120
IGMP enabled
IGMP querier 40.1.1.1(this system) <- IGMP querier is Agr1
IGMP version 2
Step 6: Verify IGMP on VDX6-Agr2.

Group Address
Interface
225.0.0.10
Vlan 120
Member Ports: Po 50
225.0.0.11
Vlan 120
Member Ports: Po 50
225.0.0.12
Vlan 120
Member Ports: Po 50
225.0.0.13
Vlan 120
Member Ports: Po 50
225.0.0.14
Vlan 120
Member Ports: Po 50
225.0.0.15
Vlan 120
Member Ports: Po 50
225.0.0.16
Vlan 120
Member Ports: Po 50
225.0.0.17
Vlan 120
Member Ports: Po 50
225.0.0.18
Vlan 120
Member Ports: Po 50
225.0.0.19
Vlan 120
Member Ports: Po 50
Uptime
20:49:07
Expires
00:02:56
Last Reporter
40.1.1.2
20:49:07
00:02:58
40.1.1.2
20:49:07
00:02:55
40.1.1.2
20:49:07
00:03:00
40.1.1.2
20:49:07
00:02:56
40.1.1.2
20:49:07
00:02:56
40.1.1.2
20:49:07
00:03:03
40.1.1.2
20:49:07
00:02:57
40.1.1.2
20:49:07
00:02:54
40.1.1.2
20:49:07
00:02:56
40.1.1.2

Interface Vlan 1
Interface Vlan 100
Interface Vlan 101
Interface Vlan
IGMP Snooping
IGMP Snooping
IGMP Snooping
102
disabled
fast-leave disabled
querier disabled

53-1003501-01
61
Interface Vlan 103
Interface Vlan 104
Interface Vlan 120
RbridgeId: 201
Interface Ve 100
IGMP enabled
IGMP querier 20.1.1.2(this system) <- IGMP querier is Agr2
IGMP version 2
Interface Ve 102
IGMP enabled
IGMP version 2
Interface Ve 104
IGMP enabled
IGMP version 2
Interface Ve 120
IGMP enabled
IGMP querier 40.1.1.1(other system) <- IGMP querier is Agr1
IGMP version 2
Similarly verify in other nodes.

Step 7: Verify VDX5-Agr1 PIM mcache.
VDX5-Agr1# show ip pim mcache
IP Multicast Mcache Table
Entry Flags
: sm - Sparse Mode, ssm - Source Specific Multicast
RPT - RPT Bit, SPT - SPT Bit, LSrc - Local Source
LRcv - Local Receiver, RegProbe - Register In Progress
RegSupp - Register Suppression Timer, Reg - Register Complete
Layer 2Reg - Layer 2 Registration, needRte - Route Required for
Src/RP
Total entries in mcache: 10 <- Only (S,G) will be programmed as AGR2 is the DR even
AGR1 is querier on vlan 120.
1
(20.1.1.3, 225.0.0.10) in Ve 100, Uptime 21:29:03
Sparse Mode, RPT=0 SPT=1 Reg=0 Layer 2Reg=1 RegSupp=1 RegProbe=0 LSrc=1 LRcv=0
62

53-1003501-01
Source is directly connected. RP 11.11.11.11

num_oifs = 0
Flags (0x0043a8d1)
sm=1 ssm=0 needRte=0
(20.1.1.3, 225.0.0.11) in Ve 100, Uptime 21:29:03
num_oifs = 0
Flags (0x0043a8d1)
(20.1.1.3, 225.0.0.12) in Ve 100, Uptime 21:29:03
num_oifs = 0
Flags (0x0043a8d1)
(20.1.1.3, 225.0.0.13) in Ve 100, Uptime 21:29:03
num_oifs = 0
Flags (0x0043a8d1)
Step 8: Verify VDX6-Agr2 PIM mcache.

VDX6-Agr2# sh ip pim mc
Entry Flags
: sm - Sparse Mode, ssm - Source Specific Multicast
RPT - RPT Bit, SPT - SPT Bit, LSrc - Local Source
LRcv - Local Receiver, RegProbe - Register In Progress
RegSupp - Register Suppression Timer, Reg - Register Complete
Layer 2Reg - Layer 2 Registration, needRte - Route Required for
Src/RP
Total entries in mcache: 20
1
(*, 225.0.0.10) RP 11.11.11.11 in Ve 104, Uptime 20:52:52
upstream neighbor=3.2.1.2 <- MLX2
num_oifs = 1
Ve 120, Ve 120(20:52:52/0) <- OIF is Ve120 on which join is received
Flags (0x012604a0)
2
(20.1.1.3, 225.0.0.10) in Ve 100, Uptime 20:52:51 <- Source is ve100
num_oifs = 2
Ve 102, Ve 102(20:50:35/162) Ve 120, Ve 120(20:52:51/0) VE 102 is to MLX1
and VE 120 is to receiver. Since SPT-Threshold is 1, after the first packet, it will
select SPT path as the source and receiver are attached in Data center 1.
Flags (0x00469cf1)
3
(*, 225.0.0.11) RP 11.11.11.11 in Ve 104, Uptime 20:52:52
upstream neighbor=3.2.1.2
num_oifs = 1
Ve 120, Ve 120(20:52:52/0)
Flags (0x012604a0)
4
(20.1.1.3, 225.0.0.11) in Ve 100, Uptime 20:52:51
num_oifs = 2
Ve 102, Ve 102(20:50:35/162) Ve 120, Ve 120(20:52:51/0)
Flags (0x00469cf1)
Step 9: Verify MLX1 PIM mcache.

Core1-MLX1#sh ip pim mcache
Entry Flags
: SM - Sparse Mode, SSM - Source Specific Multicast, DM - Dense Mode
RPT
- RPT Bit, SPT - SPT Bit, LSRC - Local Source, LRCV - Local
Receiver RPFS - RPF Shortcut
HW - HW Forwarding Enabled, FAST - Resource Allocated, TAG - Need
For Replication Entry
REGPROB - Register In Progress, REGSUPP - Register Suppression
Timer, Layer 2REG - Layer 2 Registration
MSDPADV - Advertise MSDP, NEEDRTE - Route Required for Src/RP, PRUN
- DM Prune Upstream
Interface Flags: IM - Immediate, IH - Inherited, WA - Won Assert
MJ - Membership Join, MI - Membership Include, ME - Membership

53-1003501-01
63
Exclude
BR - Blocked RPT, BA - Blocked Assert, BF - Blocked Filter, BI Blocked IIF, BM - Blocked MCT
1
(*, 225.0.0.10) RP 11.11.11.11, in NIL (NIL), Uptime 00:05:19 (SM)

No upstream neighbor because RP 11.11.11.11 is itself
Flags (0x00220480) SM RPT
slow ports: ethe 3/3
AgeSltMsk: 00000000, FID: NotReq, MVID: NotReq, RegPkt: 0, profile: none
Forwarding_oif: 1, Immediate_oif: 1, Blocked_oif: 0
Layer 3 (SW) 1:
e3/3(VL102), 00:05:19/178, Flags: IM
<- Showing downstream routers interface from which joins are received
2
(20.1.1.3, 225.0.0.10) in v102 (tag e3/3), Uptime 00:08:20, Rate 1000 (SM)
upstream neighbor 2.2.1.1
Flags (0xb002c4c1) SM SPT HW FAST MSDPADV
fast ports: ethe 3/2
AgeSltMsk: 00000004, FID: 0x800e, MVID: NotReq, RegPkt: 0, AvgRate: 1000,
profile: none, KAT Timer value: 240
Layer 3 (HW) 1:
e3/2(VL1), 00:08:06/209, Flags: IM <- Forward to MSDP peer MLX3 on 3/2
Blocked OIF 1:
e3/3(VL102), 00:05:19/178, Flags: IH BR BI <- Blocks to interface
connected to downstream peer for receiver attached to DataCenter1 as it picks SPT
path.
3

Flags (0x00220480) SM RPT
Layer 3 (SW) 1:
e3/3(VL102), 00:05:19/178, Flags: IM
(20.1.1.3, 225.0.0.11) in v102 (tag e3/3), Uptime 00:08:21, Rate 1000 (SM)
Flags (0xb002c4c1) SM SPT HW FAST MSDPADV
AgeSltMsk: 00000004, FID: 0x800e, MVID: NotReq, RegPkt: 0, AvgRate: 1000,
profile: none, KAT Timer value: 240
Layer 3 (HW) 1:
e3/2(VL1), 00:08:06/208, Flags: IM
Blocked OIF 1:
e3/3(VL102), 00:05:19/177, Flags: IH BR BI

Core1-MLX2#sh ip pim mc
Entry Flags
: SM - Sparse Mode, SSM - Source Specific Multicast, DM - Dense Mode
RPT
Receiver RPFS - RPF Shortcut
REGPROB - Register In Progress, REGSUPP - Register Suppression
Timer, Layer 2REG - Layer 2 Registration
MSDPADV - Advertise MSDP, NEEDRTE - Route Required for Src/RP,
PRUN - DM Prune Upstream
Exclude
BR - Blocked RPT, BA - Blocked Assert, BF - Blocked Filter, BI Blocked
IIF, BM - Blocked MCT
Total entries in mcache: 0 <- Since the join is not received and is not sending to
MSDP peer, it doesnt have mcache entries.
mcache not found

Core2-MLX3#show ip pim mcache
Entry Flags
: SM - Sparse Mode, SSM - Source Specific Mutlicast, DM - Dense Mode
RPT
Receiver
64

53-1003501-01

REGPROB - Register In Progress, REGSUPP - Register Suppression Timer
MSDPADV - Advertise MSDP, NEEDRTE - Route Required for Src/RP, PRUN
- DM Prune Upstream
Exclude
BR - Blocked RPT, BA - Blocked Assert, BF - Blocked Filter, BI Blocked IIF
1
VE 200

Flags (0x00260480) SM RPT LRCV
Layer 3 (SW) 2:
e1/1(VL160), 21:57:23/178, Flags: IM
e1/1(VLayer 200), 01:54:32/0, Flags: MJ <- Joins received from Ve 160 and
(20.1.1.3, 225.0.0.10) in e1/2 (e1/2), Uptime 21:57:27, Rate 1000 (SM)

Flags (0x700684e1) SM SPT LRCV HW FAST TAG
AgeSltMsk: 00000001, FID: 0x8007, MVID:
30 , RegPkt: 0, AvgRate: 1000,
profile: none
Layer 3 (HW) 2:
e1/1(VL160), 21:57:17/178, Flags: IM IH
e1/1(VLayer 200), 01:54:32/0, Flags: MJ <- Traffic is sent to two VEs 200
and 160
3

Flags (0x00260480) SM RPT LRCV
Layer 3 (SW) 2:
e1/1(VL160), 21:57:23/178, Flags: IM
e1/1(VLayer 200), 01:54:38/0, Flags: MJ
(20.1.1.3, 225.0.0.11) in e1/2 (e1/2), Uptime 21:57:30, Rate 1000 (SM)

Flags (0x700684e1) SM SPT LRCV HW FAST TAG
AgeSltMsk: 00000001, FID: 0x8007, MVID:
30 , RegPkt: 0, AvgRate: 1000,
profile: none
Layer 3 (HW) 2:
e1/1(VL160), 21:57:20/175, Flags: IM IH
e1/1(VLayer 200), 01:54:40/0, Flags: MJ
Step 12: Verify MLX1 MSDP sa-cache.
Core1-MLX1# show ip msdp sa-cache self-originated Since MLX1 is sending the sacache to peers, the entries will be available if self-originated option is used
Index RP address
(Source,Group)
Orig Peer
Age/Uptime
1
11.11.11.11
(20.1.1.3,225.0.0.10)
Self-Orig
NA /NA
2
11.11.11.11
(20.1.1.3,225.0.0.11)
Self-Orig
NA /NA
3
11.11.11.11
(20.1.1.3,225.0.0.12)
Self-Orig
NA /NA
4
11.11.11.11
(20.1.1.3,225.0.0.13)
Self-Orig
NA /NA
5
11.11.11.11
(20.1.1.3,225.0.0.14)
Self-Orig
NA /NA
6
11.11.11.11
(20.1.1.3,225.0.0.15)
Self-Orig
NA /NA
7
11.11.11.11
(20.1.1.3,225.0.0.16)
Self-Orig
NA /NA
8
11.11.11.11
(20.1.1.3,225.0.0.17)
Self-Orig
NA /NA
9
11.11.11.11
(20.1.1.3,225.0.0.18)
Self-Orig
NA /NA
10
11.11.11.11
(20.1.1.3,225.0.0.19)
Self-Orig
NA /NA
Total of 10 Self Orig SA entries

Core1-MLX2#show ip msdp sa-cache
Total of 10 SA cache entries
Index RP address
(Source,Group)
1
22.22.22.22
(20.1.1.3,225.0.0.10)
2
22.22.22.22
(20.1.1.3,225.0.0.11)

53-1003501-01
Orig Peer
22.22.22.22
22.22.22.22
Age/Uptime
44 /00:10:06
44 /00:10:06
65
3
4
5
6
7
8
9
10
Total
22.22.22.22
(20.1.1.3,225.0.0.12)
22.22.22.22
(20.1.1.3,225.0.0.13)
22.22.22.22
(20.1.1.3,225.0.0.14)
22.22.22.22
(20.1.1.3,225.0.0.15)
22.22.22.22
(20.1.1.3,225.0.0.16)
22.22.22.22
(20.1.1.3,225.0.0.17)
22.22.22.22
(20.1.1.3,225.0.0.18)
22.22.22.22
(20.1.1.3,225.0.0.19)
number of matching entries:10
22.22.22.22
22.22.22.22
22.22.22.22
22.22.22.22
22.22.22.22
22.22.22.22
22.22.22.22
22.22.22.22
44
44
44
44
44
44
44
44
Orig Peer
22.22.22.22
22.22.22.22
22.22.22.22
22.22.22.22
22.22.22.22
22.22.22.22
22.22.22.22
22.22.22.22
22.22.22.22
22.22.22.22
Age
9
9
9
9
9
9
9
9
9
9
/00:10:06
/00:10:06
/00:10:06
/00:10:05
/00:10:05
/00:10:05
/00:10:04
/00:10:04

Core2-MLX3#show ip msdp sa-cache
Total of 10 SA cache entries
Index RP address
(Source,Group)
1
22.22.22.22
(20.1.1.3,225.0.0.19)
2
22.22.22.22
(20.1.1.3,225.0.0.10)
3
22.22.22.22
(20.1.1.3,225.0.0.11)
4
22.22.22.22
(20.1.1.3,225.0.0.12)
5
22.22.22.22
(20.1.1.3,225.0.0.13)
6
22.22.22.22
(20.1.1.3,225.0.0.14)
7
22.22.22.22
(20.1.1.3,225.0.0.15)
8
22.22.22.22
(20.1.1.3,225.0.0.16)
9
22.22.22.22
(20.1.1.3,225.0.0.17)
10
22.22.22.22
(20.1.1.3,225.0.0.18)
Total number of matching entries:10
66

53-1003501-01
Deploying IGMP
Overview of IGMP........................................................................................................... 67
IGMP Features, Options, and Terminology.....................................................................67
Configuring and Verifying IGMP Snooping..................................................................... 68
Configuring Layer 2 Multicast in Access and Aggregation Layers.................................. 69
Procedure Summary....................................................................................................... 70
Detailed Procedure with Examples................................................................................. 70
Overview of IGMP
Internet Group Management Protocol (IGMP) snooping is a mechanism that allows a Layer 2 switch
more efficiently forward multicastes to VLAN port members. Snooping relates to learning forwarding
states for multicast data traffic on VLAN port members using the IGMP control (Join/Leave) packets
received. This feature also provides an option to statically configure forwarding states through CLI
commands.
In a multicast domain, IGMP snooping is required at Layer 2, while IGMP and PIM are required at Layer
3. IGMP snooping always works at Layer 2, with working at Layer 3. All IGMP snooping timers are
imported from the IGMP protocol.
Multicast Control and data packets through the Layer 2 switch configured with VLANs is most easily
achieved by Layer 2 forwarding of all multicast packets received on all the member ports of the VLAN
interfaces. However, this simple approach is not bandwidth efficient, because only a subset of member
ports may be connected to devices interested in receiving given multicast packets.
In the worst case scenario, data is forwarded to all port members of a VLAN with a large number of
member ports (for example, all 24 ports), even if a single VLAN member is interested in receiving the
data. Such scenarios can lead to loss of throughput on a switch that gets hit by a high rate of multicast
data traffic for many destinations on different VLANs.
IGMP Features, Options, and Terminology

It is helpful to be familiar withIGM terminology when learning how to deploy IGMP snooping. The
following summarizes key terms, concepts, and mechanisms:
Multicast source: he source host sending or streaming multicast data traffic to the Layer 2 multicast
domain.
IGMP host or listener: The destination host interested in receiving multicast traffic from the multicast
source.
IGMP querier: The devices that generates the general IGMP queries.
Layer 2 querier or Snooping querier: The IP IGMP Snooping Querier enabled at the VLAN level,
which sends periodic general queries using 0.0.0.0 as the source IP address. It maintains the IGMP
snooping entries for the VLAN for all rbridges within a single VCS.
Layer 3 querier: IGMP querier enabled on a Layer 3 interface enabled with PIM-SM mode. This
querier periodically sends general queries using the the IP address configured on the Layer 3
interface (VE) as the hsource IP address.

53-1003501-01
67
Configuring and Verifying IGMP Snooping
IGMP Join: This message is sent on an interface when the IGMP host decides to join the group. It
immediately transmits a Membership Report for that group, which occurs only in the Non-Member
state.
IGMP Leave: This message is sent on an interface when the IGMP host decides to leave the group.
It immediately transmits a Leave message for that group. In a Leave Group message, the group
address field contains the IP multicast group address.
IGMP general query: Used to learn which groups have members on an attached network. The
group address field is set to zero when sending a General Query, which applies to all memberships
on the interface from which the Query is received.
IGMP group specific query: Used to learn if a particular group has any members on an attached
network. A Group-Specific Query applies to membership in a single group on the interface from
which the Query is received. The group address in the IGMP header has a valid multicast group
address.
IGMP snooping table: When the host sends an IGMP join message when the VLAN is configured
for IGMP snooping, the switch learns the IGMP join and makes an entry in the IGMP Snooping
table. This table contains VLAN information, multicast group addresses, and member ports on the
switch connected to each host interested in receiving multicast traffic.
IGMP snooping entries: When the host sends an IGMP join message when the VLAN is configured
for IGMP snooping, makes an entry in the IGMP snooping table.
IGMP Snooping Entry Timers:
IGMP query interval: The query interval is the interval between general queries sent by the
querier. Valid values range from 1 through 18000 seconds; the default is 125 seconds.
IGMP lastmemberqueryinterval: The time in milliseconds that the IGMP router waits to
receive a response to a groupspecific query message, including messages sent in
response to a hostleave message. Valid values range from 100 through 25500
milliseconds; the default is 1000 milliseconds.
IGMP max query response time: Sets the maximum response time for IGMP queries for a
specific interface. When a host receives the query packet, it starts counting until it reaches
the maximum response time. When this timer expires, the switch (host) replies with a
report, provided that no other host from the same group has responded yet. Valid values
range from 1 through 25 seconds; the default is 10 seconds.
IGMP snooping fast leave: This enables the IGMP snooping fastleave option, which allows removal
of an interface from the forwardingtable without sending out group-specific queries to the interface.
IGMP snooping mrouter: A VLAN port member that is a multicast router interface, which is an
interface that faces toward a multicast router or other IGMP querier.
Configuring and Verifying IGMP Snooping

Figure 6 illustrates the topology for the IGMP snooping deployment demonstrated in this example.
68

53-1003501-01
Configuring Layer 2 Multicast in Access and Aggregation Layers
FIGURE 6 IGMP Snooping Topology
Note the following about this deployment:

Aggregation 1: IGMP is enabled on VCS ID 11 for VLANS in which receivers are attached.
Access 1: Layer 2 and IGMP are enabled on VCS ID 10 for VLANs in which receivers are attached.
Access 2: Layer 2 and IGMP are enabled on VCS ID 12 for VLANs in which receivers are attached.
Configuring Layer 2 Multicast in Access and Aggregation Layers

Figure 6 on page 69 the multicast source is attached to Access 1 in VLAN 50 from 30.1.1.3 to Group
226.0.0.10 to 225.0.0.19. Layer 2 VLAN 50 is enabled on Access1 and on Aggregation 1 with IGMP
snooping.
Two receivers are attached. One receiver is attached in Datacenter 1 on VLAN 60 by enabling IGMP
snooping on that VLAN 60 in Access 1 and Aggregation 1. The second receiver is attached in
Datacenter 2 in VLAN 70 by enabling IGMP snooping on VLAN 70 in Access2
Virtual Private LAN Service (VPLS) peering is established between MLX1 and MLX3 using an LDP
tunnel with MLX 2 in the MPLS core. VPLS end points on MLX1 are tagged in VLAN 50 and 60 and on
MLX3 are tagged in VLAN 70. IP multicast active is configured in the VPLS instance on MLX1 and
passive is configured on MLX3.
With active IGMP mode enabled, the router actively sends out IGMP queries to identify IP multicast
groups within the VLAN or VPLS instance and makes entries in the IGMP table based on the Group
Membership reports received from the network.

53-1003501-01
69
Procedure Summary
When passive IGMP mode is enabled, the router listens for IGMP Group Membership reports on the
VLAN or VPLS instance specified but does not send IGMP queries. The passive mode is called IGMP
snooping. Use this mode when another device in the VLAN or VPLS instance is actively sending
queries.
Procedure Summary
Step 1: Configure VLAN to source, tag port channel, and enable IGMP snooping.
Configure a Layer 2 VLAN 50 in Access 1 with ports connected to the source on VDX3 and VDX4
tagged to it. Also, tag the port-channel connected to Aggregation1 in that VLAN. Enable IGMP
snooping on VLAN 50 in Access1
Step 2: Configure VLAN, tag the port channel and ports to to Core1, and enable IGMP
snooping.
Configure Layer 2 VLAN 50 on Aggregation 1 and tag the port-channel to Access 1 and the ports
connected to Core1 in that VLAN. Enable IGMP snooping on VLAN 50 in Aggregation1.
Step 3: Establish OSPF neighbors in Area 0 and enable LDP.
Establish OSPF neighborship between MLX1, MLX2, and MLX3 in Area 0. Enabe LDP on the
interfaces. In order to bring up the LDP link session, ldr-id can be configured with unique address on
each node if the devices has Multicast Source Discovery Protocol (MSDP) configuration with common
loopback.
Step 4: Configure VPLS and add VPLS end points.
Configure VPLS between MLX1 and MLX3 with MLX2 at MPLS transit. VPLS is configured with IP
multicast active on MLX1 and passive on MLX3. The ports connected from MLX1 to Aggregation1 are
added as VPLS endpoints in VLAN 50.
Step 5: Configure VLANs with IGMP snooping, add ports to receivers, and add ports from
Access 1, Aggregation1, and Access 2.
enabled. Add the ports on VDX 3, 4 and VDX 9, 10 connected to receivers in those VLANs
respectively. Add the ports connected to Aggregation 1 from Access 1, Core1 from Aggregation1 and
Core 2 from Access 2 in those VLANs.
Step 6: Add ports from MLX1 in VPLS VLAN and from Core2 in VPLS VLAN 70.
Add the ports connected to Aggregation1 from MLX1 in VPLS VLAN 60 and the ports connected to
Access 2 from Core2 in VPLS VLAN 70.
Step 7: Start the receivers and verify IGMP group membership.
Start the receivers to send IGMP joins and verify the IGMP group membership on all nodes. Run the
source traffic and verify the traffic forwarding.

Enabling IGMP Snooping
To enable IGMP snooping, complete the following steps.
70

53-1003501-01
Configuring Layer 2 VLAN
Procedure
Step 1: Configure VLAN to source, tag port channel, and enable IGMP
snooping.
Configure a Layer 2 VLAN 50 in Access 1 with ports connected to Source on
VDX3 and VDX4 tagged to it. Also, tag the port-channel connected to
Aggregation1 in that VLAN. Enable IGMP snooping on VLAN 50 in Access1.
VLAN with IGMP snooping should be configured globally from principal switch.
VDX3-Access3# interface Vlan 50<- Enabling VLAN 50
ip igmp snooping enable <-Enabling IGMP snooping
Step 3: Configure VDX3-Access3 Interface.

fabric isl enable
fabric trunk enable
switchport
switchport trunk allowed vlan add 50,100 <- interface is tagged to VLAN 50
no shutdown
vlag ignore-split
speed 40000
switchport
switchport trunk allowed vlan add 50,100,120
no shutdown
Step 4: Configure VLAN, tag the port channel and ports to to Core1, and
enable IGMP snooping.
Configuring Layer 2 VLAN

Configure Layer 2 VLAN 50 on Aggregation 1 and tag the port-channel to Access 1 and the ports
connected to Core1 in that VLAN. Enable IGMP snooping on VLAN 50 in Aggregation1. VLAN with
IGMP snooping should be configured globally from principal switch.
VDX6-Agr2# interface Vlan 50<- Enabling VLAN 50

Step 2: Configure VDX6-Agr2 Interface.
vlag ignore-split
speed 40000
switchport
switchport trunk allowed vlan add 50, 100,120
no shutdown
!
fabric isl enable
fabric trunk enable
switchport
switchport trunk allowed vlan add 50,101

53-1003501-01
71
Deploying IGMP
no shutdown
!
Step 3: Establish OSPF neighbors in Area 0 and enable LDP.

Establish OSPF neighborship between MLX1, MLX2, and MLX3 in Area 0. Enabe LDP on the
interfaces. In order to bring up the LDP link session, ldr-id can be configured with unique address on
each node if the devices has MSDP configuration with common loopback.
Step 4: Configure MLX1 Interface, OSPF, LDP and router-id.

enable
ip ospf cost 5

enable
router mpls <- Enabling MPLS
ldp
lsr-id 22.22.22.22 <- LSR-id is configured to loopback 2
mpls-interface e3/2 <- Addded as MPLS interface
ldp-enable <- LDP is enabled on the interface
ldp-enable<- LDP is enabled on the interface
!! !
Step 5: Configure MLX2 Interface, OSPF, LDP, and router-id.

enable
enable
ip ospf cost 10
ip address 11.11.11.11/32 <-Common IP address
ip router-id 33.33.33.33 <-router-id with unique address
ldp
72

53-1003501-01
Configuring VPLS
lsr-id 33.33.33.33<- LSR-id is configured to loopback 2

mpls-interface e4/5<- Addded as MPLS interface
Step 6: Configure MLX3 Interface, OSPF, LDP, and router-id.

enable
ip ospf area 0 <-OSPF area 0
ip ospf cost 5

enable
ip ospf cost 10
ldp
lsr-id 44.44.44.44<- LSR-id is configured to loopback 2
Configuring VPLS
To configure VPLS, complete the following steps.
Procedure
Step 1: Configure VPLS and add VPLS end points .
VPLS is configured between MLX1 and MLX3 with MLX2 at MPLS transit. VPLS
will be configured with IP multicast active on MLX1 and passive on MLX3. The
ports connected from MLX1 to Aggregation1 are added as VPLS end points in
VLAN 50.
Step 2: Configure MLX1 VPLS.
vpls vp1 100 <- VPLS with name and ID
vpls-peer 44.44.44.44 <- VPLS-peer address
multicast active <- IGMP snooping
vlan 50 <- VPLS VLAN
tagged ethernet 3/7 <- VPLS end point

vpls vp 100 <- VPLS with name and ID
multicast passive<- IGMP snooping

53-1003501-01
73
Configuring VLANs with IGMP Snooping
Configuring VLANs with IGMP Snooping

To configure VLANs with IGMP snooping, complete the following steps.
74

53-1003501-01
Deploying IGMP
Step 1: Configure VLANs with IGMP snooping, add ports to receivers, and
add ports from Access 1, Aggregation1 and Access 2.
Configure Layer 2 VLANs 60, 70 on Access 1 and Access 2 respectively with
IGMP snooping enabled on them. Add the ports on VDX 3, 4 and VDX 9, 10
connected to receivers in those VLANs respectively. Add the ports connected to
Aggregation 1 from Access 1, Core1 from Aggregation1 and Core 2 from Access
2 in the respective VLANs. VLAN and interface configurations are done from
Principal switch.

fabric isl enable
fabric trunk enable
switchport
no shutdown
!
vlag ignore-split
speed 40000
switchport
switchport trunk allowed vlan add 50,60,100,120
no shutdown
!

VDX6-Agr2# interface Vlan 60<- Enabling VLAN 60
Step 5: Configure VDX6-Agr2 Interface.

vlag ignore-split
speed 40000
switchport
switchport trunk allowed vlan add 50,60,100,120
no shutdown
!
fabric isl enable
fabric trunk enable
switchport
switchport trunk allowed vlan add 60,102
no shutdown
!!


switchport

53-1003501-01
75
Adding Ports to Aggregation1

no shutdown
!
switchport
no spanning-tree shutdown
no shutdown
!
Adding Ports to Aggregation1

To add ports to Aggregation1, complete the following steps.
Procedure
Step 1: Add ports from MLX1 in VPLS VLAN and from Core2 in VPLS
VLAN 70.
Add the ports connected to Aggregation1 from MLX1 in VPLS VLAN 60 and the
ports connected to Access 2 from Core2 in VPLS VLAN 70.
vpls vp1 100 <- VPLS with name and ID
multicast active <- IGMP snooping
tagged ethernet 3/7 <- VPLS end point
tagged ethernet 3/3<- VPLS end point

vpls vp 100 <-VPLS with name and ID
multicast passive<- IGMP snooping
vlan 70<- VPLS VLAN
tagged ethernet 1/1<- VPLS end point

To start the receivers and verify IGMP group membership, complete the following steps:
Start the receivers to send IGMP joins and verify the IGMP group membership on all nodes.
Run the source traffic and verify the traffic forwarding.
Start the receiver by sending IGMP joins for Groups 226.0.0.10 to 226.0.0.19 to Datacenter1
through VDX4 in VLAN 60 and run the traffic from 56.1.1.2 on VLAN 50 through VDX3.
Start the receiver by sending IGMP joins for Groups 226.0.0.30 to 226.0.0.39 to Datacenter2
through VDX10 in VLAN 70 and run the traffic from 56.1.1.2 on VLAN 50 through VDX3.
Verifying IGMP Snooping

To verify IGMP snooping, complete the following steps.
76

53-1003501-01
Deploying IGMP
Procedure
Step 1: Verify VDX1-Access1 IGMP.
Group Address
Interface
Uptime
Expires
Last Reporter
226.0.0.10
Vlan 60
00:39:59
00:04:02
51.1.1.2
Member Ports: Te 103/0/33 <-Joins are received from interface 103/0/33 on VLAN 60
from host 51.1.1.2
226.0.0.11
Vlan 60
00:39:59
00:04:04
51.1.1.2
226.0.0.12
Vlan 60
00:39:59
00:03:59
51.1.1.2
226.0.0.13
Vlan 60
00:39:59
00:04:04
51.1.1.2
226.0.0.14
Vlan 60
00:39:59
00:03:57
51.1.1.2
226.0.0.15
Vlan 60
00:39:59
00:04:00
51.1.1.2
226.0.0.16
Vlan 60
00:39:59
00:04:02
51.1.1.2
226.0.0.17
Vlan 60
00:39:59
00:04:04
51.1.1.2
226.0.0.18
Vlan 60
00:39:59
00:03:59
51.1.1.2
226.0.0.19
Vlan 60
00:39:59
00:03:59
51.1.1.2
Interface Vlan 1
Interface Vlan 50
Interface Vlan 60
Interface Vlan 100
Interface Vlan 120
Step 2: Verify VDX6-Agr2 IGMP.

Group Address
Interface
Uptime
Expires
226.0.0.10
Vlan 60
00:43:09
00:02:53
received from interface port-channel 50on VLAN 60 from host
Member Ports: Po 50
226.0.0.11
Vlan 60
00:43:09
00:02:57
Member Ports: Po 50
226.0.0.12
Vlan 60
00:43:09
00:02:55
Member Ports: Po 50
226.0.0.13
Vlan 60
00:43:09
00:02:54
Member Ports: Po 50

53-1003501-01
Last Reporter
51.1.1.2 <- Joins are
51.1.1.2
51.1.1.2
51.1.1.2
51.1.1.2
77
Deploying IGMP
226.0.0.14
Member Ports:
226.0.0.15
Member Ports:
226.0.0.16
Member Ports:
226.0.0.17
Member Ports:
226.0.0.18
Member Ports:
226.0.0.19
Member Ports:
Vlan
Po 50
Vlan
Po 50
Vlan
Po 50
Vlan
Po 50
Vlan
Po 50
Vlan
Po 50
60
00:43:09
00:02:59
51.1.1.2
60
00:43:09
00:02:54
51.1.1.2
60
00:43:09
00:03:00
51.1.1.2
60
00:43:09
00:02:55
51.1.1.2
60
00:43:09
00:02:57
51.1.1.2
60
00:43:09
00:02:59
51.1.1.2

Interface Vlan 1
Interface Vlan 50
Interface Vlan 60
Interface Vlan 100
Interface Vlan 101
Interface Vlan 102
Interface Vlan 103
Interface Vlan 104
Interface Vlan 120
RbridgeId: 201
Interface Ve 100
IGMP enabled
78

53-1003501-01
Deploying IGMP

IGMP version 2
Interface Ve 102
IGMP enabled
IGMP version 2
Interface Ve 104
IGMP enabled
IGMP version 2
Interface Ve 120
IGMP enabled
IGMP querier 40.1.1.1(other system)
IGMP version 2
Step 3: Verify VDX10-Access10 IGMP.

Group Address
Interface
Uptime
226.0.0.30
Vlan 70
00:38:48
received from interface 153/0/33 on VLAN 70 from
226.0.0.31
Vlan 70
00:38:48
226.0.0.32
Vlan 70
00:38:48
226.0.0.33
Vlan 70
00:38:48
226.0.0.34
Vlan 70
00:38:48
226.0.0.35
Vlan 70
00:38:48
226.0.0.36
Vlan 70
00:38:48
226.0.0.37
Vlan 70
00:38:48
226.0.0.38
Vlan 70
00:38:48
226.0.0.39
Vlan 70
00:38:48
Expires
Last Reporter
00:03:09
57.1.1.2 <- Joins are
host 57.1.1.2
00:03:16
57.1.1.2
00:03:11
57.1.1.2
00:03:08
57.1.1.2
00:03:13
57.1.1.2
00:03:09
57.1.1.2
00:03:14
57.1.1.2
00:03:11
57.1.1.2
00:03:11
57.1.1.2
00:03:12
57.1.1.2

Interface Vlan 1
Interface Vlan 70
Interface Vlan 150

53-1003501-01
79
Deploying IGMP

Interface Vlan 160
Interface Vlan 161
Interface Vlan 200
Step 4: Verify MLX1 OSPF.

Core1-MLX1#show ip os neighbor
Port
3/2
3/4
Address
5.1.2.1
6.1.1.1
Pri State
1
FULL/DR
254 FULL/DR
Neigh Address
5.1.2.2
6.1.1.2
Neigh ID
44.44.44.44
33.33.33.33
Ev Opt Cnt
6 66 0
5 66 0
Neigh ID
22.22.22.22
44.44.44.44
Ev Opt Cnt
5 66 0
5 66 0
Neigh ID
22.22.22.22
33.33.33.33
Ev Opt Cnt
5 66 0
5 66 0

Port
4/4
4/5
Address
6.1.1.2
5.1.3.1
Pri State
255 FULL/BDR
1
FULL/DR
Neigh Address
6.1.1.1
5.1.3.2

Port
1/2
1/5
Address
5.1.2.2
5.1.3.2
Pri State
1
FULL/BDR
1
FULL/BDR
Neigh Address
5.1.2.1
5.1.3.1
Step 7: Verify MLX1 LDP.

Core1-MLX1#show mpls ldp neighbor
Number of link neighbors: 2 <- Interface LDP neighbors
Number of targeted neighbors: 1 <- Established through VPLS
Nbr Transport
33.33.33.33
44.44.44.44
44.44.44.44
Interface
e3/4
e3/2
(targeted)
Nbr LDP ID
33.33.33.33:0
44.44.44.44:0
44.44.44.44:0
Max Hold
15
15
45
Time Left
12
11
42
Core1-MLX1#show mpls ldp session

Number of link LDP sessions: 2
Number of Operational link LDP sessions: 2
Number of targeted LDP sessions: 0
Number of Operational targeted LDP sessions: 0
Peer LDP ID
State
Adj Used My Role
Max Hold
33.33.33.33:0
Operational
Link
Passive
36
Session
should be operational
44.44.44.44:0
Operational
Link
Passive
36
Core1-MLX1#
Core1-MLX1#show mpls ldp tunnel
Total number of LDP tunnels : 2
Oper
Tunnel
Outbound
To
State
Intf
Intf
33.33.33.33
UP
tnl0
e3/4 <- Tunnel should be UP
44.44.44.44
UP
tnl1
e3/2
80
Time Left
30
<35

53-1003501-01
Deploying IGMP

Number of targeted neighbors: 0
Nbr Transport
22.22.22.22
44.44.44.44
Interface
e4/4
e4/5
Nbr LDP ID
22.22.22.22:0
44.44.44.44:0
Max Hold
15
15
Time Left
14
13

Peer LDP ID
22.22.22.22:0
Session
44.44.44.44:0
State
Operational
Adj Used
Link
My Role
Active
Max Hold
36
Time Left
30
<-
Operational
Link
Passive
36
32

Oper
Tunnel
To
State
Intf
22.22.22.22
UP
tnl0
44.44.44.44
UP
tnl1
Outbound
Intf
e4/4 <-Tunnel should be UP
e4/4

Number of targeted neighbors: 1 <-Established through VPLS
Nbr Transport
22.22.22.22
33.33.33.33
22.22.22.22
Interface
e1/2
e1/5
(targeted)
Nbr LDP ID
22.22.22.22:0
33.33.33.33:0
22.22.22.22:0
Max Hold
15
15
45
Time Left
12
12
39

Peer LDP ID
22.22.22.22:0
Session
33.33.33.33:0
State
Operational
Adj Used
Link
My Role
Active
Max Hold
36
Time Left
31
<-
Operational
Link
Active
36
34

Oper
Tunnel
To
State
Intf
22.22.22.22
UP
tnl0
33.33.33.33
UP
tnl1
Outbound
Intf
e1/2 <- Tunnel should be UP
e1/2
MLX1
VPLS verification
MLX3 VPLS verification
Core1-MLX1#show mpls vpls id 100
VPLS vp1, Id 100, Max mac entries: 2048
Total vlans: 2, Tagged ports: 2 (2 Up), <- VPLS end points should be UP
Untagged ports 0 (0 Up)
IFL-ID: n/a
Vlan 50
Layer 2 Protocol: NONE
Tagged: ethe 3/7
Vlan 60
Tagged: ethe 3/3
VC-Mode: Raw
Total VPLS peers: 1 (1 Operational) <- Peer should be operational
Peer address: 44.44.44.44, State: Operational, Uptime: 59 min
Tnnl in use: tnl1(3)[LDP]
Peer Index:0
Local VC lbl: 983040, Remote VC lbl: 983040
Local VC MTU: 1500, Remote VC MTU: 1500
Local VC-Type: Ethernet(0x05), Remote VC-Type: Ethernet(0x05)

53-1003501-01
81
Deploying IGMP
CPU-Protection: OFF
Local Switching: Enabled
Extended Counter: ON
Multicast Snooping: Enabled - Active
Core2-MLX3#show mpls vpls id 100
VPLS vp, Id 100, Max mac entries: 8192
Total vlans: 1, Tagged ports: 1 (1 Up), <- VPLS end points should be UP
Untagged ports 0 (0 Up)
IFL-ID: n/a
Vlan 70
Tagged: ethe 1/1
VC-Mode: Raw
Total VPLS peers: 1 (1 Operational) <- Peer should be operational
Peer address: 22.22.22.22, State: Operational, Uptime: 1 hr 0 min
Tnnl in use: tnl0(3)[LDP]
Peer Index:0
Local VC lbl: 983040, Remote VC lbl: 983040
Local VC MTU: 1500, Remote VC MTU: 1500
Local VC-Type: Ethernet(0x05), Remote VC-Type: Ethernet(0x05)
CPU-Protection: OFF
Local Switching: Enabled
Extended Counter: ON
Multicast Snooping: Enabled - Passive
Step 10: Verify MLX1 VPLS IGMP snooping.

Core1-MLX1#show ip multicast vpls 100
----------+-----+---------+---------------+-----+-----+-----VPLS
State Mode
Active
Time (*, G)(S, G)
Querier
Query Count Count
----------+-----+---------+---------------+-----+-----+-----100
Ena
Active
Self
120
20
20
<-Since Core 1 receives
Joins
from Access 1 and 2 and it is active querier, it has 20 (S,g) and (*,g) entries are.
----------+-----+---------+---------------+-----+-----+-----Router ports:
Flags-
R: Router Port,
V2|V3: IGMP Receiver,
P_G|P_SG: PIM Join
(*, 226.0.0.39) 00:54:20

NumOIF: 1
Outgoing Interfaces:
TNNL peer 44.44.44.44 ( V2) 00:54:20/5s
1
none
(56.1.1.2, 226.0.0.39) in e3/7 vlan 50 00:52:34
profile: none
NumOIF: 1
profile:
TNNL peer 44.44.44.44 VC Label 983040 R Label * Port e3/2 ( V2)
00:52:34/0s
FID: 0x801a
MVID:
47
<- The groups 226.0.0.39 is received from
Access 2 and the traffic is forwarded via VPLS.
2
(*, 226.0.0.38) 00:54:20

NumOIF: 1
TNNL peer 44.44.44.44 ( V2) 00:54:20/3s
1
none
(56.1.1.2, 226.0.0.38) in e3/7 vlan 50 00:52:34
profile: none
NumOIF: 1
profile:
00:52:34/0s
FID: 0x8019
MVID:
46
3
(*, 226.0.0.37) 00:54:20

NumOIF: 1
TNNL peer 44.44.44.44 ( V2) 00:54:20/0s
1
none
(56.1.1.2, 226.0.0.37) in e3/7 vlan 50 00:52:34
profile: none
NumOIF: 1
profile:
00:52:34/0s
FID: 0x8018
MVID:
45
4
82
(*, 226.0.0.36) 00:54:20

NumOIF: 1
profile: none
TNNL peer 44.44.44.44 ( V2) 00:54:20/128s

53-1003501-01
Deploying IGMP
1
none
(56.1.1.2, 226.0.0.36) in e3/7 vlan 50 00:52:34
NumOIF: 1
profile:
00:52:34/0s
FID: 0x8017
MVID:
44
5
(*, 226.0.0.35) 00:54:22

NumOIF: 1
TNNL peer 44.44.44.44 ( V2) 00:54:22/2s
1
none
(56.1.1.2, 226.0.0.35) in e3/7 vlan 50 00:52:35
(*, 226.0.0.34) 00:54:22

NumOIF: 1
TNNL peer 44.44.44.44 ( V2) 00:54:22/2s
1
none
(56.1.1.2, 226.0.0.34) in e3/7 vlan 50 00:52:35
profile: none
NumOIF: 1
profile:
00:52:35/0s
FID: 0x8016
MVID:
43
profile: none
NumOIF: 1
profile:
00:52:35/0s
FID: 0x8015
MVID:
42
7
1
none
(*, 226.0.0.33) 00:54:22

NumOIF: 1
profile: none
TNNL peer 44.44.44.44 ( V2) 00:54:22/127s
(56.1.1.2, 226.0.0.33) in e3/7 vlan 50 00:52:35
NumOIF: 1
profile:
00:52:35/0s
FID: 0x8014
MVID:
41
8
(*, 226.0.0.32) 00:54:22

NumOIF: 1
TNNL peer 44.44.44.44 ( V2) 00:54:22/3s
1
none
(56.1.1.2, 226.0.0.32) in e3/7 vlan 50 00:52:35
(*, 226.0.0.31) 00:54:22

NumOIF: 1
TNNL peer 44.44.44.44 ( V2) 00:54:22/0s
1
none
(56.1.1.2, 226.0.0.31) in e3/7 vlan 50 00:52:35
10
(*, 226.0.0.30) 00:54:22

NumOIF: 1
TNNL peer 44.44.44.44 ( V2) 00:54:22/3s
1
none
(56.1.1.2, 226.0.0.30) in e3/7 vlan 50 00:52:35
profile: none
NumOIF: 1
profile:
00:52:35/0s
FID: 0x8013
MVID:
40
profile: none
NumOIF: 1
profile:
00:52:35/0s
FID: 0x8012
MVID:
39
profile: none
NumOIF: 1
profile:
00:52:35/0s
FID: 0x8011
MVID:
38
11
(*, 226.0.0.19) 01:00:33

NumOIF: 1
e3/3 vlan 60 ( V2) 01:00:33/2s

53-1003501-01
profile: none
83
Deploying IGMP
1
none
(56.1.1.2, 226.0.0.19) in e3/7 vlan 50 00:57:04
Access 1
12
1
none
13
1
none
14
1
none
15
1
none
16
1
none
17
1
none
18
1
none
84
NumOIF: 1
profile:
e3/3 vlan 60 ( V2) 00:57:04/0s
FID: 0x8010
MVID:
37
<- Traffic is forwared through 3/3 to
(*, 226.0.0.18) 01:00:33

NumOIF: 1
e3/3 vlan 60 ( V2) 01:00:33/4s
(56.1.1.2, 226.0.0.18) in e3/7 vlan 50 00:57:04
profile: none
NumOIF: 1
profile:
e3/3 vlan 60 ( V2) 00:57:04/0s
FID: 0x8004
MVID:
36
(*, 226.0.0.17) 01:00:33
NumOIF: 1
e3/3 vlan 60 ( V2) 01:00:33/124s
(56.1.1.2, 226.0.0.17) in e3/7 vlan 50 00:57:04
profile: none
NumOIF: 1
profile:
e3/3 vlan 60 ( V2) 00:57:04/0s
FID: 0x800f
MVID:
35
(*, 226.0.0.16) 01:00:33
NumOIF: 1
e3/3 vlan 60 ( V2) 01:00:33/5s
(56.1.1.2, 226.0.0.16) in e3/7 vlan 50 00:57:04
profile: none
NumOIF: 1
profile:
e3/3 vlan 60 ( V2) 00:57:04/0s
FID: 0x8006
MVID:
34
(*, 226.0.0.15) 01:00:33
NumOIF: 1
e3/3 vlan 60 ( V2) 01:00:33/1s
(56.1.1.2, 226.0.0.15) in e3/7 vlan 50 00:57:04
profile: none
NumOIF: 1
profile:
e3/3 vlan 60 ( V2) 00:57:04/0s
FID: 0x8007
MVID:
33
(*, 226.0.0.14) 01:00:33
NumOIF: 1
e3/3 vlan 60 ( V2) 01:00:33/6s
(56.1.1.2, 226.0.0.14) in e3/7 vlan 50 00:57:04
profile: none
NumOIF: 1
profile:
e3/3 vlan 60 ( V2) 00:57:04/0s
FID: 0x8008
MVID:
32
(*, 226.0.0.13) 01:00:33
NumOIF: 1
e3/3 vlan 60 ( V2) 01:00:33/1s
(56.1.1.2, 226.0.0.13) in e3/7 vlan 50 00:57:04
profile: none
NumOIF: 1
profile:
e3/3 vlan 60 ( V2) 00:57:04/0s
FID: 0x8009
MVID:
31
(*, 226.0.0.12) 01:00:33
NumOIF: 1
e3/3 vlan 60 ( V2) 01:00:33/7s
(56.1.1.2, 226.0.0.12) in e3/7 vlan 50 00:57:04
profile: none
NumOIF: 1
profile:
e3/3 vlan 60 ( V2) 00:57:04/0s

53-1003501-01
Deploying IGMP
FID: 0x800a
19
1
none
20
1
none
MVID:
30
(*, 226.0.0.11) 01:00:33

NumOIF: 1
e3/3 vlan 60 ( V2) 01:00:33/1s
profile: none
(56.1.1.2, 226.0.0.11) in e3/7 vlan 50 00:57:04
NumOIF: 1
profile:
e3/3 vlan 60 ( V2) 00:57:04/0s
FID: 0x800b
MVID:
29
(*, 226.0.0.10) 01:00:33
NumOIF: 1
e3/3 vlan 60 ( V2) 01:00:33/128s
profile: none
(56.1.1.2, 226.0.0.10) in e3/7 vlan 50 00:57:05
NumOIF: 1
profile:
e3/3 vlan 60 ( V2) 00:57:05/0s
FID: 0x800c
MVID:
28
Step 11: Verify MLX3 VPLS IGMP snooping.

Core2-MLX3#show ip multicast vpls 100
----------+-----+---------+---------------+-----+-----+-----VPLS
State Mode
Active
Time (*, G)(S, G)
Querier
Query Count Count
----------+-----+---------+---------------+-----+-----+-----100
Ena
Passive
22.22.22.22
69
20
10
<- Since Core 2 is
passive, it
will be having only 10 (S,g) entries for the joins it received from Access 2
----------+-----+---------+---------------+-----+-----+-----Router ports: TNNL peer 22.22.22.22 (73s) VC Label 983040 R Label *
Flags1
R: Router Port,
V2|V3: IGMP Receiver,
P_G|P_SG: PIM Join
(*, 226.0.0.39) 00:55:28

NumOIF: 2
e1/1 vlan 70 ( V2) 00:55:28/73s
TNNL peer 22.22.22.22 ( R) 00:55:28/73s
profile: none
1
(56.1.1.2, 226.0.0.39) in TNNL peer 22.22.22.22 00:53:41
NumOIF: 1
profile:
none
e1/1 vlan 70 ( V2) 00:53:41/0s
FID: 0x8010
MVID:
10
<- Traffic is forwarded to Access 2
through 1/1
in vlan 70.
2
(*, 226.0.0.38) 00:55:28

NumOIF: 2
e1/1 vlan 70 ( V2) 00:55:28/70s
TNNL peer 22.22.22.22 ( R) 00:55:28/73s
profile: none
1
(56.1.1.2, 226.0.0.38) in TNNL peer 22.22.22.22 00:53:41
profile:
none
e1/1 vlan 70 ( V2) 00:53:41/0s
FID: 0x800f
MVID:
9
3
(*, 226.0.0.37) 00:55:28

NumOIF: 2
e1/1 vlan 70 ( V2) 00:55:28/68s
TNNL peer 22.22.22.22 ( R) 00:55:28/73s
profile: none
1
(56.1.1.2, 226.0.0.37) in TNNL peer 22.22.22.22 00:53:41
profile:
none
e1/1 vlan 70 ( V2) 00:53:41/0s
FID: 0x800e
MVID:
8
4
(*, 226.0.0.36) 00:55:28

53-1003501-01
NumOIF: 2
NumOIF: 1
NumOIF: 1
profile: none
85
Deploying IGMP
e1/1 vlan 70 ( V2) 00:55:28/66s
TNNL peer 22.22.22.22 ( R) 00:55:30/76s
1
(56.1.1.2, 226.0.0.36) in TNNL peer 22.22.22.22 00:53:44
profile:
none
e1/1 vlan 70 ( V2) 00:53:44/0s
FID: 0x800d
MVID:
7
5
(*, 226.0.0.35) 00:55:30

NumOIF: 2
e1/1 vlan 70 ( V2) 00:55:30/71s
TNNL peer 22.22.22.22 ( R) 00:55:30/76s
profile: none
1
(56.1.1.2, 226.0.0.35) in TNNL peer 22.22.22.22 00:53:44
profile:
none
e1/1 vlan 70 ( V2) 00:53:44/0s
FID: 0x800c
MVID:
6
6
(*, 226.0.0.34) 00:55:30

NumOIF: 2
e1/1 vlan 70 ( V2) 00:55:30/70s
TNNL peer 22.22.22.22 ( R) 00:55:30/76s
(*, 226.0.0.33) 00:55:33

NumOIF: 2
e1/1 vlan 70 ( V2) 00:55:33/70s
TNNL peer 22.22.22.22 ( R) 00:55:33/78s
(*, 226.0.0.32) 00:55:33

NumOIF: 2
e1/1 vlan 70 ( V2) 00:55:33/74s
TNNL peer 22.22.22.22 ( R) 00:55:33/78s
(*, 226.0.0.31) 00:55:35

NumOIF: 2
e1/1 vlan 70 ( V2) 00:55:35/73s
TNNL peer 22.22.22.22 ( R) 00:55:35/80s
(*, 226.0.0.30) 00:55:35

NumOIF: 2
e1/1 vlan 70 ( V2) 00:55:35/76s
TNNL peer 22.22.22.22 ( R) 00:55:35/80s
NumOIF: 1
profile: none
1
(56.1.1.2, 226.0.0.30) in TNNL peer 22.22.22.22 00:53:48
profile:
86
NumOIF: 1
profile: none
1
(56.1.1.2, 226.0.0.31) in TNNL peer 22.22.22.22 00:53:48
profile:
none
e1/1 vlan 70 ( V2) 00:53:48/0s
FID: 0x8008
MVID:
2
10
NumOIF: 1
profile: none
1
(56.1.1.2, 226.0.0.32) in TNNL peer 22.22.22.22 00:53:46
profile:
none
e1/1 vlan 70 ( V2) 00:53:46/0s
FID: 0x8009
MVID:
3
9
NumOIF: 1
profile: none
1
(56.1.1.2, 226.0.0.33) in TNNL peer 22.22.22.22 00:53:46
profile:
none
e1/1 vlan 70 ( V2) 00:53:46/0s
FID: 0x800a
MVID:
4
8
NumOIF: 1
profile: none
1
(56.1.1.2, 226.0.0.34) in TNNL peer 22.22.22.22 00:53:46
profile:
none
e1/1 vlan 70 ( V2) 00:53:46/0s
FID: 0x800b
MVID:
5
7
NumOIF: 1
NumOIF: 1

53-1003501-01
Deploying IGMP
none
e1/1 vlan 70 ( V2) 00:53:48/0s
FID: 0x8007
MVID:
1
11
(*, 226.0.0.19) 01:01:46

NumOIF: 1
profile: none
TNNL peer 22.22.22.22 ( R V2) 01:01:46/75s
12
(*, 226.0.0.18) 01:01:48

NumOIF: 1
profile: none
TNNL peer 22.22.22.22 ( R V2) 01:01:48/78s
13
(*, 226.0.0.17) 01:01:48

NumOIF: 1
profile: none
TNNL peer 22.22.22.22 ( R V2) 01:01:48/73s
14
(*, 226.0.0.16) 01:01:48

NumOIF: 1
profile: none
TNNL peer 22.22.22.22 ( R V2) 01:01:48/80s
15
(*, 226.0.0.15) 01:01:48

NumOIF: 1
profile: none
TNNL peer 22.22.22.22 ( R V2) 01:01:48/76s
16
(*, 226.0.0.14) 01:01:48

NumOIF: 1
profile: none
TNNL peer 22.22.22.22 ( R V2) 01:01:48/81s
17
(*, 226.0.0.13) 01:01:48

NumOIF: 1
profile: none
TNNL peer 22.22.22.22 ( R V2) 01:01:48/76s
18
(*, 226.0.0.12) 01:01:51

NumOIF: 1
profile: none
TNNL peer 22.22.22.22 ( R V2) 01:01:51/85s
19
(*, 226.0.0.11) 01:01:51

NumOIF: 1
profile: none
TNNL peer 22.22.22.22 ( R V2) 01:01:51/78s
20
(*, 226.0.0.10) 01:01:51

NumOIF: 1
profile: none
TNNL peer 22.22.22.22 ( R V2) 01:01:51/76s

53-1003501-01
87
Verifying IGMP Snooping
88

53-1003501-01

Vcs Fabric Formation Multicast DP

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Vcs Fabric Formation Multicast DP

Uploaded by

Copyright:

Available Formats

53-1003501-01

Brocade VCS Fabric

2014, Brocade Communications Systems, Inc. All Rights Reserved.

Deploying Fabric Cluster Mode................................................................................................13

Deploying Logical Chassis Mode............................................................................................. 23

Deploying IGMP ..................................................................................................................... 67

Brocade VCS Fabric Formation and Multicast Deployment Guide

Adding Ports to Aggregation1........................................................... 76

Brocade VCS Fabric Formation and Multicast Deployment Guide

Brocade VCS Fabric Formation and Multicast Deployment Guide

Brocade VCS Fabric Formation and Multicast Deployment Guide

What is Brocade VCS Ethernet Fabric?

Brocade VCS Fabric Formation and Multicast Deployment Guide

VCS Fabric Technology

VCS Fabric Technology

Brocade VCS Fabric Formation and Multicast Deployment Guide

FIGURE 1 Clos Topology

Brocade VCS Fabric Formation and Multicast Deployment Guide

The advantages and disadvantages of a full-mesh topology include the following:

Brocade VCS Fabric Formation and Multicast Deployment Guide

ISL can be a separate link or can be a part of Brocade trunk.

Brocade VCS Fabric Formation and Multicast Deployment Guide

VCS Fabric Technology

Brocade VCS Fabric Formation and Multicast Deployment Guide

Deploying Fabric Cluster Mode

Configuring the VCS ID in Fabric Cluster Mode

Configuring the Rbridge ID in Fabric Cluster Mode

Brocade VCS Fabric Formation and Multicast Deployment Guide

Verifying Fabric Configuration and ISLs for Fabric Cluster Mode

<-Configuring rbridge id 200

Verifying Fabric Configuration and ISLs for Fabric Cluster Mode

Brocade VCS Fabric Formation and Multicast Deployment Guide

Deploying Fabric Cluster Mode

Brocade VCS Fabric Formation and Multicast Deployment Guide

Deploying Fabric Cluster Mode

Step 2: Verify VDX1-Access1 ISL Ports.

Brocade VCS Fabric Formation and Multicast Deployment Guide

Configuring Port Channels in Fabric Cluster Mode

Configuring Port Channels in Fabric Cluster Mode

Brocade VCS Fabric Formation and Multicast Deployment Guide

Split Recovery Options

Split Recovery Options

vLAG Feature or Configuration

Total number of vLAG on a single VDX node (LAG ID

Total number of member ports per vLAG

Total number of VDX node participating in a single

Maximum number of vLAGs in a cluster

Maximum number of members per node in one vLAG

Brocade VCS Fabric Formation and Multicast Deployment Guide

Deploying Fabric Cluster Mode

Step 2: Configure the VDX2-Access2 Interfaces.

Step 3: Configuring the VDX1-Access1 port channels.

Step 4: Configuring the VDX2-Access2 port channels.

Brocade VCS Fabric Formation and Multicast Deployment Guide

Deploying Fabric Cluster Mode

no fabric trunk enable

Step 6: Configure the VDX6-Agr2 interfaces.

Step 7: Configure the VDX5-Agre1 port channels.

VDX6-Agr2 Port Channel Configuration

The following steps are for verifying the port channels.

Link: Fo 100/0/49 (0x640C0620C0) sync: 1

* <-Ports and sync 1 means the port is

Link: Fo 100/0/51 (0x640C0660C0) sync: 1