Welcome to Connectrix B-Series Architecture and Management Overview.

Copyright © 1996, 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009, 2010, 2011, 2012,
2013 , 2014 EMC Corporation. All Rights Reserved. EMC believes the information in this publication is
accurate as of its publication date. The information is subject to change without notice.

THE INFORMATION IN THIS PUBLICATION IS PROVIDED “AS IS.” EMC CORPORATION MAKES NO
REPRESENTATIONS OR WARRANTIES OF ANY KIND WITH RESPECT TO THE INFORMATION IN THIS
PUBLICATION, AND SPECIFICALLY DISCLAIMS IMPLIED WARRANTIES OF MERCHANTABILITY OR
FITNESS FOR A PARTICULAR PURPOSE.

Use, copying, and distribution of any EMC software described in this publication requires an applicable
software license.

EMC2, EMC, Data Domain, RSA, EMC Centera, EMC ControlCenter, EMC LifeLine, EMC OnCourse, EMC
Proven, EMC Snap, EMC SourceOne, EMC Storage Administrator, Acartus, Access Logix, AdvantEdge,
AlphaStor, ApplicationXtender, ArchiveXtender, Atmos, Authentica, Authentic Problems, Automated
Resource Manager, AutoStart, AutoSwap, AVALONidm, Avamar, Captiva, Catalog Solution, C-Clip,
Celerra, Celerra Replicator, Centera, CenterStage, CentraStar, ClaimPack, ClaimsEditor, CLARiiON,
ClientPak, Codebook Correlation Technology, Common Information Model, Configuration Intelligence,
Configuresoft, Connectrix, CopyCross, CopyPoint, Dantz, DatabaseXtender, Direct Matrix Architecture,
DiskXtender, DiskXtender 2000, Document Sciences, Documentum, elnput, E-Lab, EmailXaminer,
EmailXtender, Enginuity, eRoom, Event Explorer, FarPoint, FirstPass, FLARE, FormWare,
Geosynchrony, Global File Virtualization, Graphic Visualization, Greenplum, HighRoad, HomeBase,
InfoMover, Infoscape, Infra, InputAccel, InputAccel Express, Invista, Ionix, ISIS, Max Retriever,
MediaStor, MirrorView, Navisphere, NetWorker, nLayers, OnAlert, OpenScale, PixTools, Powerlink,
PowerPath, PowerSnap, QuickScan, Rainfinity, RepliCare, RepliStor, ResourcePak, Retrospect, RSA,
the RSA logo, SafeLine, SAN Advisor, SAN Copy, SAN Manager, Smarts, SnapImage, SnapSure,
SnapView, SRDF, StorageScope, SupportMate, SymmAPI, SymmEnabler, Symmetrix, Symmetrix DMX,
Symmetrix VMAX, TimeFinder, UltraFlex, UltraPoint, UltraScale, Unisphere, VMAX, Vblock, Viewlets,
Virtual Matrix, Virtual Matrix Architecture, Virtual Provisioning, VisualSAN, VisualSRM, Voyence,
VPLEX, VSAM-Assist, WebXtender, xPression, xPresso, YottaYotta, the EMC logo, and where
information lives, are registered trademarks or trademarks of EMC Corporation in the United States
and other countries.

All other trademarks used herein are the property of their respective owners.

© Copyright 2014 EMC Corporation. All rights reserved. Published in the USA.
Revision Date: 09/2014
Revision Number: MR-1WP-NSBROC.10711.7.0

Copyright 2014 EMC Corporation. All rights reserved. Connectrix B-Series Architecture and Management Overview 1
 This course covers the hardware components, management options, and software
configurations of Connectrix B-Series switches. The course also covers the FCoE features
and functions offered with B-Series products.

Copyright 2014 EMC Corporation. All rights reserved. Connectrix B-Series Architecture and Management Overview 2
 This module focuses on the hardware components, features, and software configurations of
the Connectrix B-Series family.

Copyright 2014 EMC Corporation. All rights reserved. Connectrix B-Series Architecture and Management Overview 3
 This lesson covers the Connectrix B-Series director, blade, and switch options, as well as
their configurations.

Copyright 2014 EMC Corporation. All rights reserved. Connectrix B-Series Architecture and Management Overview 4
 The Connectrix family represents the industry’s most extensive selection of networked
storage connectivity products. Connectrix integrates high-speed Fibre Channel connectivity
(1 Gbps to 16 Gbps), highly resilient switching technology, and options for intelligent IP
storage networking. You may incorporate 8 Gbps and 16 Gbps Fibre Channel or 10GE DCB/FCoE
technology with Connectrix products to build a virtual data center. This wide range of
connectivity options allow you to configure Connectrix directors, switches, and routers to meet
any business requirement.

Copyright 2014 EMC Corporation. All rights reserved. Connectrix B-Series Architecture and Management Overview 5
 In this table we see the current EMC portfolio of B-Series switches. Please take a moment
to compare the different models and their features.

Copyright 2014 EMC Corporation. All rights reserved. Connectrix B-Series Architecture and Management Overview 6
 The table above shows the current EMC portfolio of B-Series directors. Please take a
moment to compare the different models and some of the features.

Note that all of these are high availability models with redundant core processor blades and
redundant core routing blades.

The Connectrix ED-DCX8510 models are capable of 16 Gbps with QSFP (Quad SFP), and
they have 64 Gbps ICL (Inter-Chassis Link) connectors, that provide high-speed director-to-
director links without using ISLs. These directors are designed to be the backbone for very
large Enterprise SANs.

Copyright 2014 EMC Corporation. All rights reserved. Connectrix B-Series Architecture and Management Overview 7
 Performance statistics include 4.6 Tbps of bandwidth on the front-end ports, 8.50 Gbps line
speed, full duplex per slot plus local switching ability, and 512 Gbps of aggregated ICL
bandwidth. The director supports 2, 4, and 8 Gbps Fibre Channel and FICON speeds
requiring Brocade-branded small form-factor pluggables (SFPs).

Redundancy is attained with dual Control Processors, core blades, and WWN cards. With local
switching, a fully loaded chassis, and using eight 64-port blades, the switch is capable of
supplying 512 ports at 8 Gbps with an oversubscription ratio of 2:1.

Note here that other oversubscription rates for various blades are shown above.

Copyright 2014 EMC Corporation. All rights reserved. Connectrix B-Series Architecture and Management Overview 8
 Performance statistics include 2.3 Tbps of bandwidth on the front-end ports, 8.50 Gbps line
speed, full duplex per slot plus local switching ability, and 512 Gbps of aggregated ICL
bandwidth. The director supports 1, 2, 4, and 8 Gbps Fibre Channel and FICON speeds
requiring Brocade-branded SFPs (small form-factor pluggables).

With local switching, a fully loaded chassis, and using four 64-port blades, the switch is capable
of supplying 256 ports at 8 Gbps with an oversubscription ratio of 2:1.

Copyright 2014 EMC Corporation. All rights reserved. Connectrix B-Series Architecture and Management Overview 9
 Performance statistics include 6 Tbps of bandwidth on the front-end ports, 512 Gbps per
slot plus local switching ability, and 2 Tbps of aggregated ICL bandwidth. The director
supports 2, 4, 8, 10, and 16 Gbps Fibre Channel and FICON speeds requiring Brocade-
branded small form-factor pluggables (SFPs).

When local switching occurs, a fully loaded chassis using eight 48-port blades supplies 384
ports at 16 Gbps with an oversubscription ratio of 1.5:1.

Copyright 2014 EMC Corporation. All rights reserved. Connectrix B-Series Architecture and Management Overview 10
 Performance statistics include 3 Tbps of bandwidth on the front-end ports, 512 Gbps per
slot plus local switching ability, and 1 Tbps of aggregated ICL bandwidth. The director
supports 2, 4, 8, 10, and 16 Gbps Fibre Channel and FICON speeds requiring Brocade-
branded small form-factor pluggables (SFPs).

When local switching occurs, a fully loaded chassis, using four 48-port blades, supplies 128
ports at 16 Gbps with an oversubscription ratio of 1.5:1.

Copyright 2014 EMC Corporation. All rights reserved. Connectrix B-Series Architecture and Management Overview 11
 This slide shows the latest additions to the port blade lineup and ranges from 16 to 64
ports. 8 Gbps FC8-16, FC8-32, and FC8-48 blades require proprietary SFPs, LC connector, 8
Gbps SWL, and 8 Gbps LWL. FC8-64 blades require proprietary mSFP, mSFP LC connector
and 8 Gbps SWL only. The 8-Gbps SFP+s and mSFPs auto-negotiate at 2, 4, and 8 Gbps. All
those port blades are compatible with the DCX-B and DCX-4S-B directors. The 64-port
blade is compatible with the DCX-8510B and DCX directors. The 8-Gbps SFPs and mSFPs
auto-negotiate at 2, 4, and 8 Gbps. The 4-Gbps SFPs auto-negotiate at 1, 2, and 4 Gbps.

The 16-Gbps SFP+s auto-negotiate at 2, 4, 8, 10, and 16 Gbps. The 10 Gbps FC-type SFPs
can be installed on only the first eight ports of the 16 Gbps port blades.

The 32-, 48- and 64- port blades also support port-based in-flight encryption/decryption
and compression/decompression. Those blades are compatible with the DCX-8510B
directors.

Copyright 2014 EMC Corporation. All rights reserved. Connectrix B-Series Architecture and Management Overview 12
 The 24-port distance extension blade is designed specifically for the Connectrix DCX
backbone directors. Leveraging 8 Gbps Fibre Channel, 10 Gigabit Ethernet, and advanced
Fibre Channel over IP (FCIP) technology, the blade provides 12 FC ports at 8 Gbps, 10 ports
at 1 GbE, and up to two optional 10 Gigabit Ethernet ports for unmatched bandwidth, port
density, and throughput over WAN links.

Copyright 2014 EMC Corporation. All rights reserved. Connectrix B-Series Architecture and Management Overview 13
 This lesson covers the most commonly used Connectrix B-Series features.

Copyright 2014 EMC Corporation. All rights reserved. Connectrix B-Series Architecture and Management Overview 14
 The optional ISL Trunking feature allows inter-switch links between two Connectrix B-Series
models to merge into a logical link. ISL Trunking reduces situations that require static
traffic routes and individual ISL management.

Trunking optimizes fabric performance by distributing traffic across the shared bandwidth of
all the inter-switch links in the Trunking group. This allows traffic to flow through any
available link in a group rather than restricting it to a specific, potentially congested link. A
Trunking license is required on each switch that participates in Trunking.

Trunks distribute traffic dynamically and in order, at the frame level. Trunking is enabled
automatically when the ISL Trunking license is activated and ports are reinitialized.

Trunks are easily managed using either CLI commands or Web Tools. You can enable and
disable Trunking and set Trunk port speeds for entire switches or for individual ports. The
maximum number of ports per trunk and trunks per switch depends on the Connectrix B-
Series model.

Copyright 2014 EMC Corporation. All rights reserved. Connectrix B-Series Architecture and Management Overview 15
 ICLs connect three DCX or DCX-4S chassis (or up to six DCX8510-8Bs or DCX8510-4Bs)
together without sacrificing front-end ports. These connections utilize copper cables to link
the director’s core blades without combining domains. Unlike Inter-Switch Links (ISLs) that
use standard front-end ports on the line module card, ICLs use dedicated backplane ports
to provide maximum host and storage connectivity. Using these connections preserves
valuable E_Ports of application blades.

On the Brocade DCX and DCX-4S, there are two ICL connectors at ports ICL0 and ICL1 on
each core blade. On Brocade DCX-4S, each ICL aggregates a set of 8 ports. The DCX-4S
allows 16 ICL ports per core blade and 32 ICL ports available per chassis. On Brocade DCX,
each ICL aggregates a set of 16 ports. Each core blade provides 32 ICL ports meaning there
are 64 ICL ports available for the entire Brocade DCX chassis.

On the DCX8510 family, you can have up to 32 by 64 Gbps QSFP ports in a Brocade DCX
8510-8B chassis or a 16 by 64 Gbps QSFP ports in a Brocade DCX 8510-4B chassis, with up
to 2 Tbps ICL bandwidth.

Brocade DCX 8510 Backbones with core blade ICL ports use laser transmission for data
traffic. The distance limit is extended up to 100m (FOS 7.1.0 and above, otherwise, up to
50m). This enables the use of ICLs, instead of ISLs, for regular connections between
chassis. The longer cable length allows for flexible topologies while connecting different
Brocade DCX 8510 platforms. This is in contrast to the restrictions imposed by shorter ICL
cables on Brocade DCX/DCX-4S, which limited the number of topologies using ICLs.

You cannot interconnect a B-Series DCX Backbone family chassis to a B-Series DCX-8510
Backbone family chassis.

Copyright 2014 EMC Corporation. All rights reserved. Connectrix B-Series Architecture and Management Overview 16
 Integrated Routing is a licensed capability introduced in Fabric OS v6.1. It allows any port
in an ED-DCX-B with 8 Gig port blades, ED-DCX-8510B, DS-5100B, or DS-6510 to be
configured as an Ex_Port.

Fibre Channel Routing Service (FCRS) enables device connectivity across SAN fabrics
without merging them and using logical SANs called LSANs. Turning on Fibre Channel
Routing capability requires the Integrated Routing feature license. This connectivity is
available when using EX_Ports configured in an Inter-Fabric Link (IFL). A front domain
appears in the edge fabric as a logical domain for each IFL.

The diagram displayed on this slide shows two edge fabrics communicating through a
backbone fabric via Fibre Channel Routing Protocol. The physical configuration connects an
edge fabric switch E_Port to the backbone switch Ex_Port. This configuration creates a
logical domain in each edge fabric.

Device sharing is established via LSAN zones configured in each fabric. The zone definitions
must include the same WWNs of the devices that need to communicate. LSAN Zones must
be defined only with Port WWNs or Port WWN aliases because PIDs are not unique
identifiers.

In order to route frames between the edge fabrics, phantom domains and phantom devices
must be introduced into each edge fabric. The routers themselves are not present in the
edge fabrics. All traffic between fabrics traverses the backbone fabric, and all switches
participating in the Backbone fabric(s) are E_Port attached.

Copyright 2014 EMC Corporation. All rights reserved. Connectrix B-Series Architecture and Management Overview 17
 The Virtual Fabrics feature allows some physical Connectrix B-Series switches to be
partitioned into independently managed logical switches, each with their own data, control,
and management paths.

Logical switches can allocate fabric resources “by the port” rather than by the switch. They
also provide a way to simplify charge-back for storage by customer, department, or
application while cost-effectively consolidating SAN resources. Because logical switches do
not need to be enabled on every switch in a SAN, deployment is simple and non-disruptive
in existing environments.

In the example above, the physical switch has 8 FC ports. When the Virtual Fabrics feature
is enabled, a single logical switch is created in the physical chassis. This logical switch is
called the Default Logical switch, and it initially contains all of the 8 FC ports in the physical
chassis. When a logical switch is created, you must assign it a fabric ID (FID). The fabric ID
uniquely identifies each logical switch within a chassis. FID 128 is assigned to the Default
Logical switch by default, although you can change this value later.

Now, new logical switches can be created and have ports assigned to them. A given port
can be in only one logical switch. As they are allocated, they are removed from the default
logical switch.

The example above shows a logical switch with an FID 10 and two ports (ports 2 and 5). A
third Logical switch was created with an FID 15 and ports 4, 6 and 7.

Copyright 2014 EMC Corporation. All rights reserved. Connectrix B-Series Architecture and Management Overview 18
 A logical fabric is a fabric that contains at least one logical switch. The four fabrics shown in
the example above are logical fabrics because they each have at least one logical switch.

In this example, in logical switch 2, ports 2 (H1 device connected) and 5 (A1 device
connected) are F_Ports forming the Logical Fabric 10.

It is possible to create a logical fabric connecting a logical switch to a non-Virtual Fabrics

switch using ISLs, as shown in the graphic above. In this case, in logical switch 3, port 6
(H2 device connected) is an F_port and port 7 is an E_Port that forms an inter-switch link
(ISL) between logical switch 3 and the non-Virtual Fabrics switch S1. Logical switch 3 is the
only logical switch that can communicate with the non-Virtual Fabrics switch and the
storage array A2, because the other logical switches are in different fabrics.
The Base switch is an optional component that can be utilized to provide connectivity
between switches at the chassis level using Extended ISLs (XISLs). Base switches also
provide FCR connectivity between Logical Fabrics or between a Logical Fabric and an Edge
Fabric (physical). In a single chassis environment, the Base switch would only be required
to provide FCR capabilities between the user-defined Logical Switches. The Base switch
should only contain connectivity (ISL) ports.

Copyright 2014 EMC Corporation. All rights reserved. Connectrix B-Series Architecture and Management Overview 19
 There are some options to implement long-distance SAN fabrics. One of the most commonly
used is placing FC switches at each location in the SAN. Thus, each switch handles local
connectivity and multiplexes traffic across long-distance connections. In this case, ISLs can
use dark fiber connections to transfer data. Wave division multiplexing, such as DWDM
(Dense Wave Division Multiplexing) or CWDM (Coarse Wave Division Multiplexing) can be
used to increase the capacity of the links. As Fibre Channel speeds increase, the maximum
distance decreases for each switch.

The Brocade Extended Fabrics is an optional licensed feature for B-Series deployment over
distance beyond 10 km. This feature extends the distance the ISLs can reach over an
extended fiber. This is accomplished by providing enough buffer credits on each side of the
link to compensate for latency introduced by the extended distance.

Long distance link modes

• Static Mode (LO): L0 is the normal (default) mode for a port. The maximum
supported link distance is up to 5 km at 2 Gbps, up to 2 km at 4 Gbps, and up to 1 km
at 8, 10, and 16 Gbps.
• Static Mode (LE): - LE configures an E_Ports distance greater than 5 km and up to
10 km. LE does not require an Extended Fabrics license.
• Dynamic Mode (LD): LD calculates BB credits based on the distance measured
during port initialization.
• Static Long-Distance Mode (LS): LS calculates a static number of BB credits based
only on a user-defined desired_distance value. Specify LS mode to configure a static
long distance link with a fixed buffer allocation greater than 10 km.

Copyright 2014 EMC Corporation. All rights reserved. Connectrix B-Series Architecture and Management Overview 20
 To ensure that data reaches all the users who need it, organizations are now looking for
ways to transport data throughout the enterprise, both locally over the SAN as well as over
much longer distances. One of the best ways to achieve this goal is to interconnect
geographically dispersed SANs through reliable, high-speed links. This approach involves
transporting Fibre Channel block data over existing IP infrastructures currently used
throughout the enterprise.

Fibre Channel over IP or FCIP is a TCP/IP-based tunneling protocol connecting

geographically distributed SAN islands over Ethernet. The IP network is transparent to the
Fibre Channel fabric. Only edge devices need to be aware of FCIP encapsulation. This
solution can take advantage of existing Fiber Channel networks and tie them together using
existing IP networks.

The FCIP protocol standard has rapidly gained acceptance as a manageable, cost-effective
way to blend the best of both worlds: Fibre Channel block data storage across a widely
deployed IP infrastructure. As a result, organizations now have an excellent way to protect,
store, and move their data while leveraging existing technology investments.

The B-Series hardware required to configure FCIP includes the MP-7800 or the PB-DCX-FX8-
24 blade.

Copyright 2014 EMC Corporation. All rights reserved. Connectrix B-Series Architecture and Management Overview 21
 Applications that benefit from an FCIP connection include: data backup, consolidation of
SAN islands, data mirroring, and business continuity. FCIP can minimize the cost of SAN
connections by using an existing IP network to span a distance that would normally require
costly FC media. By using existing IP networks, organizations can direct SAN traffic to a
WAN rather than implementing a whole new Fibre Channel topology.

Copyright 2014 EMC Corporation. All rights reserved. Connectrix B-Series Architecture and Management Overview 22
 N_Port ID Virtualization (NPIV) is a standard that describes how a single Fibre Channel HBA
port (single N_Port/single FCID) can register with several World Wide Port Names (WWPNs)
or multiple N_Port IDs in the SAN fabric. This allows a fabric-attached N_Port to claim
multiple fabric addresses. Each address appears as a unique entity on the Fibre Channel
fabric.

In other words, NPIV-capable HBAs can provide multiple WWPNs rather than registering a
single WWPN in the fabric. This is beneficial in two ways:

1) In a virtual machine environment, each VM can have separate WWPNs so that the
hypervisor will be released to provide the I/O blending operation.

2) In a virtual machine environment where many host operating systems or applications

are running on a physical host, each virtual machine can now be managed
independently from zoning, aliasing, and security perspectives. Also, there would be no
extra physical ports to be connected in the SAN fabric, so the addition of more edge
switches would not be required.

Copyright 2014 EMC Corporation. All rights reserved. Connectrix B-Series Architecture and Management Overview 23
 Access Gateway is a Fabric OS feature that permits configuration of an Enterprise fabric to
handle additional N_Ports instead of domains. To do this, configure F_Ports to connect to
the fabric as N_Ports, which increases the number of device ports you can connect to a
single fabric. Multiple Access Gateways can connect to the ED-DCX-B enterprise-class
platform, directors, and switches. After you set a B-Series switch to AG mode, the F_Ports
connect to the Enterprise fabric as N_Ports rather than as E_Ports. They connect as E_Ports
if the B-Series switch is in Native mode.

B-Series switches in AG mode are logically transparent to the host and the fabric. You can
increase the number of hosts that have access to the fabric without increasing the number
of switches. This simplifies configuration and management in a large fabric by reducing the
number of domain IDs and ports.

The B-Series switch in Native mode is a part of the fabric. It requires two to four times as
many physical ports, consumes fabric resources, and can connect to a B-Series or M-Model
fabric only. AG is outside the fabric. It reduces the number of switches in the fabric and
the number of required physical ports. You can connect AG to a B-Series, M-EOS, or Cisco-
based fabric.

Copyright 2014 EMC Corporation. All rights reserved. Connectrix B-Series Architecture and Management Overview 24
 The implementation of the Fibre Channel-switched fabric environment allows users to
dynamically add and remove nodes. When users add or remove a node, hosts are notified
of the change to the fabric environment. Most hosts query the fabric name server to receive
an update. Nodes that do not query the name server may not be aware that their target is
no longer available, and will therefore continue to send frames to the same destination
port.

With hardware-enforced WWN zoning, the active zoning configuration is pushed to the port
ASIC where the ingress and egress ports are located. Only zone members in the same zone
can communicate when they are logged in to the switch. There is no license required to
enable this feature. It is enabled by default and requires no customer configuration.

Copyright 2014 EMC Corporation. All rights reserved. Connectrix B-Series Architecture and Management Overview 25
 This module covered the hardware components, features, and software configurations of
Connectrix B-Series family.

Copyright 2014 EMC Corporation. All rights reserved. Connectrix B-Series Architecture and Management Overview 26
 This module focuses on the Connectrix B-Series management tools and the basic initial
configuration of a B-Series switch.

Copyright 2014 EMC Corporation. All rights reserved. Connectrix B-Series Architecture and Management Overview 27
 This lesson covers the Connectrix B-Series management options and licensing practices.

Copyright 2014 EMC Corporation. All rights reserved. Connectrix B-Series Architecture and Management Overview 28
 The Command Line Interface can be utilized by connecting to the IP address of the switch
via Telnet or SSH. This interface can be used to perform all switch configuration and
maintenance tasks.

Copyright 2014 EMC Corporation. All rights reserved. Connectrix B-Series Architecture and Management Overview 29
 Web Tools is a graphical user interface (GUI) that enables administrators to monitor and
manage switches and directors from a standard workstation. It is a factory-installed
licensed product that runs on Fabric OS. Web Tools require any browser that conforms to
HTML version 4.0, JavaScript version 1.0, and Java Plug-in 1.6.0 or higher. At the browser,
enter the IP address of the switch as the URL.

This slide shows an example of an ED-DCX-4S director and its default view within Web
Tools. For this director, the left side of the window provides activities, monitoring
capabilities, and a fabric view. The center pane displays the physical view of the switch. The
right pane displays switch information and switch events. The action buttons are displayed
across the top of the screen.

Copyright 2014 EMC Corporation. All rights reserved. Connectrix B-Series Architecture and Management Overview 30
 Connectrix Manager Converged Network Edition CMCNE is the industry's first unified
network management solution for data, storage, application delivery, wireless, and
converged networks. It supports Fibre Channel SANs, FCoE, IP switching and routing
(including Ethernet fabrics), and MPLS networks — providing end-to-end visibility across
different network types through a seamless and unified user experience.

CMCNE offers the following capabilities:

• Simplifies operations by providing unified network management of SAN, IP (including
Ethernet fabric), and wireless environments
• Reduces operating expenses by providing comprehensive operations support within a
single framework
• Simplifies data center automation through enhanced support for Brocade VCS fabric
technology
• Integrates seamlessly with industry-leading hypervisors and management solutions
from Microsoft, VMware, and EMC, maximizing the value of IT investments

Previous versions of CMCNE were called Connectrix Manager Data Center Edition (Until
version 10.4) or just Connectrix Manager (Until version 10)

Copyright 2014 EMC Corporation. All rights reserved. Connectrix B-Series Architecture and Management Overview 31
 CMCNE is offered with three licensing options; Professional, Enterprise, and Professional
Plus Edition.

The Professional edition showcases a subset of features and hardware platforms of the
Enterprise edition. The free of charge Professional version is intended for the management
of smaller fabrics with Connectrix B-Series departmental switches and DCX-4S-B and
DCX8510-4B directors. It cannot manage DCX-B and DCX-8510-8B directors, has no FICON
or routing support, and does not have remote clients or Call home support.

The Professional Plus edition is designed for medium-sized businesses or departmental

storage networks. It’s very similar in functionality to the Enterprise version but limited in
features/scalability by a license key to support only up to 36 fabrics and 2,560 switch ports,
DCX-4S-B and DCX8510-4B directors, encryption products, extension products, and
Brocade HBA/CNAs. The Professional Plus supports FOS fabrics and it can be updated to the
Enterprise edition via a license key update.

The Enterprise edition builds on top of the functionality available with the Professional
edition, and provides a comprehensive fabric management framework for the end-to-end
management of the data center fabric. Enterprise edition can scale to manage up to 9,000
switch ports, and also contains several new features along with significant enhancements to
several of the older Connectrix Manager and Fabric Manager features. Enterprise edition
also supports all enterprise-class products/technologies including the ED-DCX-B Backbone
Director, FICON, Fibre Channel Routing (FCR), Fibre Channel over IP (FCIP), IP switching
and routing, and MPLS networks.

Copyright 2014 EMC Corporation. All rights reserved. Connectrix B-Series Architecture and Management Overview 32
 In B-Series switches, licenses can be associated with a feature-version or a blade-type. If a
feature has a version-based license, that license is valid only for a particular version of the
feature. If you want a newer version of the feature, you must purchase a new license.

Here is an example with a version upgrade: A zoning license that is for Fabric OS version
6.0.0 is added. You can add another zoning license with a version greater than v5.2.0 and
above without removing the zoning license for Fabric OS v5.2.0. Upgrading is allowed but
downgrading is not supported. If a license is not version-based, then it is valid for all
versions of the feature.

If a license is associated with a blade-type, the licensed feature can be used only with the
associated blade. If you want to use the feature on a second blade, you must purchase an
additional license.

The list above shows some of the FOS included and optional licensed features. If you want
to know more about them, check the Brocade FOS Administrator’s guide. Alternatively,
refer to the EMC Education Services website https://education.emc.com/default_guest.aspx
and check for SAN Connectrix trainings.

Copyright 2014 EMC Corporation. All rights reserved. Connectrix B-Series Architecture and Management Overview 33
 The Connectrix B-Series family offers a number of optional software features that provide
additional capabilities. Here is a summary of some of these optional features.
• Inter-Switch Link trunking: Logically merges up to eight ISLs into one, full 8 Gbps
logical link
• Advanced Performance Monitor: Provides end-to-end traffic analysis
• Fabric Watch: Provides real-time SAN monitoring
• Extended Fabrics: Provides greater than 10km of switched fabric connectivity at full
bandwidth over long distances (depending on the platform this can be up to 3000km)
• Adaptive Networking: A suite of tools for optimizing fabric behavior and ensuring
ample bandwidth for mission-critical applications; includes Quality of Service, Ingress
Rate Limiting, Traffic Isolation, and Top Talkers
• Integrated Routing: Allows ports to be configured as EX_Ports supporting Fibre
Channel Routing, eliminating the need to add a PB-DCX-FX8-24 Fibre Channel routing
blade or use the MP-7800B router for Fibre Channel Routing purposes
• Enhanced Group Management: Enables full management of the device in a data
center fabric with the Connectrix Manager Data Center Edition for deeper element
management functionality and greater management task aggregation throughout the
environment
• 10 Gbps FCIP/Fibre Channel license (10G license): Enables 10 Gbps access on
the 16 Gbps FC ports on the Brocade 6510 switch.
• Advanced Extension — This license enables two advanced extension features: FCIP
Trunking and Adaptive Rate Limiting.
• Ports on Demand—Allows customers to instantly scale the fabric by provisioning
additional ports via license key upgrade.
• Inter Chassis Links (ICLs) for interconnecting ED-DCX8510-4B and ED-DCX8510-
8B chassis without using ports on the port blades at distances of up to 50meters
apart.

Copyright 2014 EMC Corporation. All rights reserved. Connectrix B-Series Architecture and Management Overview 34
 To verify what licenses are installed in a switch, use the licenseShow command. The
licensed features currently installed are listed. If the feature is not listed, use the
licenseAdd command to install it.

Copyright 2014 EMC Corporation. All rights reserved. Connectrix B-Series Architecture and Management Overview 35
 This lesson covers the Connectrix B-Series initial basic configuration and basic zoning
configuration.

Copyright 2014 EMC Corporation. All rights reserved. Connectrix B-Series Architecture and Management Overview 36
 To manage a B-Series switch from a serial connection, connect the B-Series serial cable to
the Comm port for the switch. Open a terminal emulator application (such as HyperTerminal
on a PC, or TERM, TIP, or Kermit in a UNIX environment) and configure the application.

Log in using an administrator level account. This will allow configuration of the management
IP address.

Copyright 2014 EMC Corporation. All rights reserved. Connectrix B-Series Architecture and Management Overview 37
 Connect to the Fabric OS CLI using a console session on the serial port. Use the admin
account to log in to the switch. The default password is password.

The first task might be to assign an IP address to the switch. Use the ipaddrset command
to set static addresses for the Ethernet network interface. Use static Ethernet network
interface addresses on the director and enterprise-class platforms, and in environments
where DHCP service is not available. You may enter static Ethernet information and disable
DHCP at the same time.

Copyright 2014 EMC Corporation. All rights reserved. Connectrix B-Series Architecture and Management Overview 38
 The switch automatically prompts to change the default account passwords after logging in
for the first time. If the passwords are not changed, the switch prompts after each
subsequent login until all the default passwords have been changed.

The default accounts on the switch are admin, user, root, and factory. Use the admin
account to log in to the switch for the first time and to perform the basic configuration
tasks.

The change default account passwords prompt accepts a maximum of eight characters. Any
characters beyond the eighth characters are ignored. Only the default password is subject
to the eight character limit. User-defined passwords can have 8 to 40 characters. They
must begin with an alphabetic character and can include numeric characters, the period (.),
and the underscore ( _ ). They are case-sensitive and they are not displayed when you
enter them on the command line.

Copyright 2014 EMC Corporation. All rights reserved. Connectrix B-Series Architecture and Management Overview 39
 When executing the initial setup, it is possible to customize the switch name. Switch names
can be from 1 to 31 characters long, except for the ED-DCX-B and ED-DCX-4S-B. These
platforms must be 1 to 15 characters in length. All names must begin with a letter and can
contain letters, numbers, or the underscore character. It is not necessary to use quotation
marks.

Switches maintain the current date and time inside of a battery-backed real-time clock
(RTC) circuit. The date and time are used for logging events. Switch operation does not
depend on the date and time. A switch with an incorrect date and time value still functions
properly. However, because the date and time are used for logging, error detection, and
troubleshooting, they should be set correctly.

In a Virtual Fabric there can be a maximum of eight logical switches per director or
enterprise-class platform. Only the default switch in the chassis will update the hardware
clock. When the date command is issued from a non-principal pre-Fabric OS v6.2.0 switch,
it will be dropped by a Fabric OS v6.2.0 or later switch, and the older switch will not receive
an error.

Authorization access to set or change the date and time for a switch is role-based.

To set the date and time use the mmddHHMMyy syntax.

Copyright 2014 EMC Corporation. All rights reserved. Connectrix B-Series Architecture and Management Overview 40
 Although Domain IDs are assigned dynamically when a switch is enabled, you can reset
them manually so that you can control the ID number or to resolve a Domain ID conflict
when you merge fabrics. If a switch already has a Domain ID when it is enabled, and that
Domain ID conflicts with a switch already in the fabric, the conflict is automatically
resolved. The process can take several seconds during which time traffic is delayed.
The default Domain ID for Connectrix B-series switches is 1.

During the same process, it is possible to change other fabric parameters. The following
parameters only can be changed if the switch is disabled. Also, they must be identical for a
fabric to merge:
• BB Credit
• R_A_TOV
• E_D_TOV
• Switch PID format
• Insistent Domain ID Mode
Changing these values may segment the Fabric or affect the Fabric performance. Unless
necessary, don’t change most of these values from the defaults.

Copyright 2014 EMC Corporation. All rights reserved. Connectrix B-Series Architecture and Management Overview 41
 Zoning is the process of grouping initiator and targets into zones. Initiators and targets
placed in the same zone are allowed to communicate by the fabric. Zoning also plays a
critical role in event isolation, i.e., Registered State Change Notifications (RSCN)
distribution. In order for a fabric to work properly, it must be properly zoned.

A collection of zones is called a zone set. The zone set can be active or inactive. An active
zone set is the collection of zones currently being used by the switched fabric to manage
data traffic.

Single HBA zoning consists of a single HBA port and one or more storage ports. It is
important to note that a port can reside in multiple zones which provide the ability to map a
single Storage port to multiple host ports. For example, a VMAX FA port or a VNX SP port
can be mapped to multiple Single HBA zones. This allows multiple hosts to share a single
storage port (for example, hosts in a cluster). Single HBA zoning simulates a single initiator
SCSI environment. This reduces risks associated with issues such as different driver
revisions, HBA types, and heterogeneous servers on the same fabric. It is a best practice to
zone a single HBA to a single storage port.

Copyright 2014 EMC Corporation. All rights reserved. Connectrix B-Series Architecture and Management Overview 42
 Zoning commands make changes that affect the entire fabric. When executing fabric-level
configuration tasks, allow time for the changes to propagate across the fabric before
executing any subsequent commands. For a large fabric, it may be necessary to wait
several seconds for commands to complete and propagate within the fabric.

Some B-Series zoning concepts are:

• Zone object: A zone object is any device in a zone, such as physical port number,
Node World Wide Name (nWWN) or Port World Wide Name (pWWN)
• Zone alias: It is a name assigned to a device or a group of devices. This simplifies
cumbersome data entry and allows an intuitive naming structure (such as using
“NT_Hosts” to define all NT hosts in the fabric).
• Zone configuration: It is a group of one or more zones. A zone can be included in
more than one zone configuration.

Zoning in the B-series uses the CLI, Webtools, or Connectrix Manager Converged Network
Edition CMCNE. Some recommendations when zoning in B-Series are:
• Always zone using the highest Fabric OS-level switch.
• Zone using the core switch versus an edge switch.
• Zone using a director over a switch. A director has more resources to handle zoning
changes and implementations.

Copyright 2014 EMC Corporation. All rights reserved. Connectrix B-Series Architecture and Management Overview 43
 It is possible to monitor and manage zoning through the Web Tools Zone Admin module.
Click the Zone Administration icon in the Fabric Toolbar to access the Zone Admin
module. All switches include a zoning license.

Use the Zone tab to create, modify, rename, or delete zones in the zoning
database.

To create a zone:
• Click the Zone tab.
• Click New Zone. The Create New Zone dialog displays.
• Enter a name for the new zone in the Create New Zone dialog, and click OK.
The zone name must be a unique alphanumeric string beginning with an alpha
character.
• Click the + signs in the Member Selection List to view the nested elements.
The choices available in the Member Selection List depend on the selection
made in the View menu (Zoning Methods).
– Zone membership can include ports, WWNs, aliases, or any combination of
these. A device can be included in more than one zone.
– To specify by port number, specify the switch domain ID and area number.
For example, 2,12 indicates switch domain ID 2, area number 12. When a
member is specified by port number, all devices connected to the port are
included in the zone.
– To specify by WWN, specify node name or port name as an eight byte hex
number separated by colons, for example, 10:00:00:00:60:69:00:8a.
These eight numbers are compared to the node and port name presented
in a login frame (FLOGI or PLOGI).
• Select an element in the Member Selection List to be included in the zone.
• The Add Member button becomes active.
• Click Add Member to add the zone member.

Copyright 2014 EMC Corporation. All rights reserved. Connectrix B-Series Architecture and Management Overview 44
 A zone configuration is a group of zones that are enforced whenever that zone configuration
is enabled. There are different configuration types:
• Defined Configuration – The complete set of all zone objects defined in the fabric.
• Effective Configuration – A single zone configuration that is currently in effect.
• Saved Configuration – A copy of the defined configuration plus the name of the
effective configuration, which is saved in flash memory by the cfgSave command.
• Disabled Configuration – The effective configuration that is removed from flash
memory.

Use the following procedure to create a zone configuration. After creating a zone
configuration, enable it for it to take effect.
1. Click the Zone Config tab.
2. Click New Zone Config (The Create New Config dialog box appears).
3. Type a name for the new configuration and click OK. The zone configuration name
must be a unique alphanumeric string beginning with an alphabetic character and
cannot exceed 64 characters.

Now, add the zones to the zone configuration

1. Click “+” signs in the Member Selection List to view the nested elements.
2. Highlight an element in the Member Selection List to be included in the configuration.
3. The Add Member button becomes active. Click the Add Member button to add
configuration members.
4. Repeat steps 4 and 5 to add more elements to the configuration.
5. Click Actions, Save Config Only to save the configuration changes.

Copyright 2014 EMC Corporation. All rights reserved. Connectrix B-Series Architecture and Management Overview 45
 Several zone configurations can reside on a switch at once. However, only one zone
configuration can be enabled at a time.

When enabling a zone configuration from Web Tools, you should keep in mind that the
entire zoning database is automatically saved, and the selected zone configuration is
enabled.

If the zoning database size exceeds the maximum size allowed, the zone configuration
cannot be enabled. The zoning database summary (Zone configuration summary report)
displays the maximum zoning database size. It can be obtained by clicking Print > Print
Zone Database Summary.

To enable a zone configuration:

1. Click Enable Config.
2. Select the configuration to be enabled from the menu, and click OK.
3. Click Yes to save and enable the selected configuration.

If inconsistencies are discovered, an error occurs and the previous state of the Fabric is
restored. For example, if zoning is disabled, it remains disabled. If an existing configuration
is enabled, it remains enabled.

Copyright 2014 EMC Corporation. All rights reserved. Connectrix B-Series Architecture and Management Overview 46
 This module covered the Connectrix B-Series management tools and the basic initial
configuration of a B-Series switch.

Copyright 2014 EMC Corporation. All rights reserved. Connectrix B-Series Architecture and Management Overview 47
 This module focuses on the Connectrix B-Series FCoE products, features and functions.

Copyright 2014 EMC Corporation. All rights reserved. Connectrix B-Series Architecture and Management Overview 48
 This lesson covers the Connectrix B-Series FCoE architecture and FCoE features.

Copyright 2014 EMC Corporation. All rights reserved. Connectrix B-Series Architecture and Management Overview 49
 Fibre Channel over Ethernet (FCoE) is a new technology protocol, defined by the T11
standards committee. It expands FC into the Ethernet environment. Basically FCoE allows
Fibre Channel frames to be encapsulated within Ethernet frames, providing a transport
protocol that is more efficient than TCP/IP sharing a single, integrated infrastructure; it
thereby reduces network complexities in the data center.

FCoE consolidates both SANs and Ethernet traffic onto one Converged Network Adapter
(CNA), eliminating the need for using separate Host Bus Adapters (HBAs) and Network
Interface Cards (NICs).

Copyright 2014 EMC Corporation. All rights reserved. Connectrix B-Series Architecture and Management Overview 50
 The Fibre Channel portion of FCoE appears as normal Fibre Channel to a host or a switch,
and therefore to a user. It is based completely on the FC model, which makes it easy to
understand, manage, and troubleshoot. A major value is that FCoE uses Ethernet hardware
to deliver an enterprise storage solution, while also using the existing FC management
infrastructure.

Copyright 2014 EMC Corporation. All rights reserved. Connectrix B-Series Architecture and Management Overview 51
 Converged Network Adapters (CNAs) are intelligent multi-protocol adapters that provide
host LAN and Fibre Channel SAN connectivity over 10 Gbps Ethernet using Fibre Channel
over Ethernet (FCoE) and Enhance Ethernet functionality.

CNAs are built using off-the-shelf NIC and HBA ASIC’s by Qlogic, Brocade and Emulex.
Usually a CNA offers full hardware offload for FCoE protocol reducing the system CPU
utilization for I/O operations, which leads to faster application performance and higher
levels of consolidation in virtualized systems. Implementing CNA creates minimum
disruption in existing environments.

Copyright 2014 EMC Corporation. All rights reserved. Connectrix B-Series Architecture and Management Overview 52
 FCoE switches or Fibre Channel Forwarders (FCFs) provide the connectivity between FCoE
initiators, FCoE targets, and conventional Fibre Channel fabrics. FCFs therefore offer both
FCoE ports and native FC ports for both device and switch-to-switch fabric connections.

The function of the Fibre Channel Forwarder (FCF) is essentially to de-encapsulate FC

frames that are coming from the CNA and going to the SAN and encapsulate FC frames that
are coming from the SAN and going to the CNA.

An example of Ethernet switches that provide the FCF functionality is the DCX director using
the FCOE24 blade.

Copyright 2014 EMC Corporation. All rights reserved. Connectrix B-Series Architecture and Management Overview 53
 A DCB Ethernet switch is an Ethernet switch implementation that has certain
characteristics, the most important being that they do not drop frames under congestion –
in other words, they are lossless. A lossless network is very important to block I/O
operations because unlike TCP/IP, the loss of a single frame typically requires the entire
exchange to be aborted and re-driven by the upper-level protocol (ULP), instead of just re-
sending a particular missing frame.

Data Center Bridging (DCB) includes Priority-based Flow Control, DCB Capability Exchange
Protocol, Congestion Notification, and Enhanced Transmission Selection.

Copyright 2014 EMC Corporation. All rights reserved. Connectrix B-Series Architecture and Management Overview 54
 This lesson covers the Connectrix B-Series FCoE hardware and cabling requirements in a B-
Series FCoE solution.

Copyright 2014 EMC Corporation. All rights reserved. Connectrix B-Series Architecture and Management Overview 55
 The PB-DCX-24FCOE is distinguished by the 24 Converged Enhanced Ethernet (CEE) ports
brandished on the exterior face of the blade. The blade comes factory-populated with 10
GbE SFP+ Optics, and is fully functional out of the box. In contrast to the MP-8000B
departmental switch, there are no Fibre Channel (FC) ports on the director blade. FC
communication is facilitated through the backplane via a specialized Application Specific
Integrated Circuit (ASIC).

The PB-DCX-24FCOE supports Layer 2 Ethernet features and provides DCB/CEE switching
via encapsulation/decapsulation of FCoE. The director blade ensures that all DCB/CEE
criteria is met, including the facilitation of lossless full-duplex Ethernet communication and
support for jumbo frames.

No FCoE licenses are required for utilization of the switch’s DCB/CEE functionality.

The PB-DCX-24FCOE is designed for “End of Row” Data Center deployment.

Copyright 2014 EMC Corporation. All rights reserved. Connectrix B-Series Architecture and Management Overview 56
 It is important to note that the PB-DCX-24FCOE is not compatible with older director
models; it is only compatible with the DCX and the DCX-4S. An upgrade to FOS code v6.3 is
required in order to use the blade.

There is a maximum of two FCoE blades per chassis. The two blades act as a single
DCB/CEE switch. The initial release of the PB-DCX-24FCOE will only coexist with standard
DCX or DCX-4S port blades. If an incompatible port card is simultaneously installed in the
DCX, either the incompatible port card or the PB-DCX-24FCOE will go into a faulty state.
Communications between blades always goes through the Core blade.

Copyright 2014 EMC Corporation. All rights reserved. Connectrix B-Series Architecture and Management Overview 57
 There are two options available for physical connectivity when using FCoE: Optical (fiber)
cable and Twinax (copper) cable.

Optical

You can use optical connections for any FCoE link. If you are using FC or 10 GbE, you are
probably already familiar with LC connectors. This cable is available in several diameters
and bandwidth distance product ratings.

The benefits of using optical cables include:

• Interoperability – If the other side supports optical cable, the two ports will inter-operate
from a physical connectivity perspective.

• Longer distance – OM4 allows for 10G connections up to 550m as opposed to a

maximum distance of 10m with twinax cables.

• Physically smaller in size – The smaller size allows the cable to be easily pushed to the
side of a cabinet to ensure that airflow is not restricted.

• Can use any vendor’s cable.

Limitations include:

• Expensive – Up to 10 times the cost of twinax.

• Uses more power than twinax.

Copyright 2014 EMC Corporation. All rights reserved. Connectrix B-Series Architecture and Management Overview 58
 Twinax

Typically, twinax is used between the server and the Top of Rack (ToR) switch. Unlike fiber
optic cable, twinax uses two copper conductors to pass electrical signals between the two
cable ends.

As shown in the table above, each E-node and FCF combination may only support a limited
set of cables available. Limited support is due to a software check that each vendor
performs when a new SFP+ module is inserted. When inserted, the hardware on the device
will read the serial data from the SFP+. If the SFP+ module is not recognized by the device,
it will log an error message and potentially prevent the device from initializing.

The benefits of using twinax cables include:

• Less expensive than optical cables

• Uses less power than optical cables

Limitations include:

• Limited in distance

• Interoperability concerns. For example, VMAX arrays do not support twinax cables.

Copyright 2014 EMC Corporation. All rights reserved. Connectrix B-Series Architecture and Management Overview 59
 The Small Form-Factor Pluggable Plus (SFP+) is the next generation transceiver module
initially targeted to support speeds of 10Gbps for next-generation Gigabit Ethernet
applications. Fibre SFPs must be Brocade-branded. The fibre connections support
SFP/SFP+, both of short and long wavelength.

The FC and 10 GigE SFPs can be identified by the markings on the label. The markings in
the label images differentiate the two optic types.

Copyright 2014 EMC Corporation. All rights reserved. Connectrix B-Series Architecture and Management Overview 60
 This module covered the Connectrix B-Series FCoE products, features, and functions.

Copyright 2014 EMC Corporation. All rights reserved. Connectrix B-Series Architecture and Management Overview 61
 This module focuses on the Connectrix B-Series FCoE management tools available for a
FCoE environment. The different options for host connectivity in an EMC FCoE solution are
also covered.

Copyright 2014 EMC Corporation. All rights reserved. Connectrix B-Series Architecture and Management Overview 62
 The initial introduction of FCoE technology enabled simplification of rack cabling by
converging Ethernet and Fibre Channel networking at the network edge, or access layer.

Once data moved into the top-of-rack switch, it was separated out in separate Ethernet and
Fibre Channel data streams to the LAN and SAN respectively.

The next step in networking evolution enabled end-to-end FCoE, provided it was limited to a
single hop.

Note: For simplification, we have removed all redundant components from this diagram.
Best practice is to design and build these networks in a way to eliminate single points of
failure.

Copyright 2014 EMC Corporation. All rights reserved. Connectrix B-Series Architecture and Management Overview 63
 The benefits that I/O consolidation brings to the access layer can now be achieved in the
core of the data center as well. With the capability to consolidate the network in the core,
as shown, the 24FCOE blade brings an immediate benefit by reducing data center
complexity.

Note: For simplification, we have removed all redundant components from this diagram.
Best practice is to design and build these networks in a way to eliminate single points of
failure.

Copyright 2014 EMC Corporation. All rights reserved. Connectrix B-Series Architecture and Management Overview 64
 VCS (Virtual Cluster Switching) Ethernet fabrics provide next generation access layer
connectivity and are designed specifically to provide enhanced support for virtual and cloud
environments. VCS Ethernet fabrics support converged networking and can transport
Ethernet, NAS, iSCSI and FCoE data.

VCS fabrics are created using Brocade VDX (Virtual Data Center) series switches.

FOS 7.0.1 supports connection of a Fibre Channel SAN to a Brocade VCS Ethernet fabric.

EMC does not sell or service these switches, but you should be aware of a couple of their
features.

Copyright 2014 EMC Corporation. All rights reserved. Connectrix B-Series Architecture and Management Overview 65
 Only VDX6730 switches have the Fibre Channel ports necessary to create a gateway to the
SAN. Fibre Channel routing (FCR) is used to connect the VDX6730 switches to the SAN. An
E-port on a VDX6730 connects to an Ex_Port on an FCR switch.

VDX series switches connecting to a SAN must be running Brocade Network Operating
System (NOS) v2.1.1 or later. B-Series SAN switches must be running FOS v7.0.1 or later.
An integrated Routing license is not required for device sharing between the VCS fabric and
the Fibre Channel SAN.

Some unsupported configurations are:

• Connecting an MP-8000B or FCoE10-24 blade to a VCS fabric is not supported.

• Servers connected to VCS can communicate with targets in a Fibre Channel SAN.
However, servers in a Fibre Channel SAN cannot communicate with targets attached to
VCS fabric.

• Long distance links between the VDX6730 and FOS FC router (FCR) are not supported
(IFL cannot be configured for Long Distance mode).

Copyright 2014 EMC Corporation. All rights reserved. Connectrix B-Series Architecture and Management Overview 66
 Host connectivity

There are two options for host connectivity to an FCoE switch. The first option is for hosts
that do not need to access storage over a SAN. In this scenario, a host will have one or
more (for redundancy) 10 Gbps Ethernet Network Interface Cards (NICs) installed. The
FCoE switch acts as a standard Ethernet switch for these hosts, and forwards Ethernet
frames to the next device in the Ethernet network. The standard 10 Gbps Ethernet NICs do
not provide access to Fibre Channel (SAN) resources at this time.

In the second environment, a host will have one or more Converged Network Adapters
(CNAs). The CNAs support the same standard networking protocols as the NICs as well as
Fibre Channel over Ethernet (FCoE). This allows hosts that have CNAs installed to access
both network resources as well as Fibre Channel resources by using a single interface.

Both NICs and CNAs can be used to connect different hosts on the same switch.

Storage connectivity

FCoE target ports can be used as targets only. Therefore, replication technologies (For
example: SRDF, RecoverPoint, and Mirror View) cannot be used on these. However, FC
ports on the same array can be used for replication. FCoE target ports can communicate
concurrently with CNAs and HBAs as long as they go through proper connections. LUNs can
be accessed by a host, either through HBAs (Fibre Channel technology) or through CNAs
(FCoE technology). LUNs may also be replicated between compatible arrays using native
array replication technology.

Copyright 2014 EMC Corporation. All rights reserved. Connectrix B-Series Architecture and Management Overview 67
 Here are the general configuration steps that must be completed on the B-Series DCX
directors with 24FCOE blades.

Copyright 2014 EMC Corporation. All rights reserved. Connectrix B-Series Architecture and Management Overview 68
 Supported management software includes SSH v2, HTTP/HTTPS, SNMP v1/3, Telnet, SNMP
for FE MIB, FC Management MIB, RMON, Web Tools, CMCNE, SMI-s, RADIUS, and LDAP.

Management connections can be RJ-45, In-Band, or serial port. One USB port is supplied for
backup of FC switch information. Please note that the DCB/CEE switch information cannot
be saved to the USB drive at this time.

Diagnostics include POST and all embedded online and offline diagnostics.

Copyright 2014 EMC Corporation. All rights reserved. Connectrix B-Series Architecture and Management Overview 69
 CMCNE provides unified management for a wide range of protocols supporting data storage
and converged networks, as well as FCIP, FCoE, and Data Center Bridging (DCB). CMCNE
fully supports FCoE and DCB protocols, as well as group management for Connectrix FCoE
products.

To configure; select Configure > FCoE from the menu bar or right-click the DCB device
and select FCoE; the FCoE Configuration dialog box displays (shown here).

Copyright 2014 EMC Corporation. All rights reserved. Connectrix B-Series Architecture and Management Overview 70
 The configuration of FCoE requires two command sets:
• FOS commands: used to configure the Fibre Channel switch (and general
switch/blade administration)
• DCB/CEE commands: used to configure the Ethernet switch (including all CEE ports
and Ethernet uplinks to the LAN.)

FOS commands are available as usual on a B-Series switch at the initial login prompt, while
DCB/CEE commands require getting into the DCB/CEE shell. To enter the DCB/CEE shell,
type cmsh at the FOS prompt as shown on this slide.

Notice the change in command prompt based on which command shell you are using.

Copyright 2014 EMC Corporation. All rights reserved. Connectrix B-Series Architecture and Management Overview 71
 Notice that there is similar data shown between the DCB/CEE show system command and
the FOS firmwareshow and switchshow command:
• Unit Name is the switch name
• Hardware Rev is the hardware type
• Fabric OS Version is the same as firmware version

Also notice that power supply and fan status is provided.

Copyright 2014 EMC Corporation. All rights reserved. Connectrix B-Series Architecture and Management Overview 72
 Please take a moment to review the DCB/CEE features supported through Web Tools.

Copyright 2014 EMC Corporation. All rights reserved. Connectrix B-Series Architecture and Management Overview 73
 After pointing a Java enabled browser to the IP address of the switch, Web Tools will load.
The CEE interface configuration and information can be viewed in the Port Administration
window on the CEE Interfaces tab.

Copyright 2014 EMC Corporation. All rights reserved. Connectrix B-Series Architecture and Management Overview 74
 This module covered the Connectrix B-Series FCoE management tools available for a FCoE
environment, and also the different options for host connectivity in a EMC FCoE solution.

Copyright 2014 EMC Corporation. All rights reserved. Connectrix B-Series Architecture and Management Overview 75
 This course covered the hardware components, management options, and software
configurations of Connectrix B-Series switches. The course also covered the FCoE features
and functions offered with B-Series products.

This concludes the training.

Copyright 2014 EMC Corporation. All rights reserved. Connectrix B-Series Architecture and Management Overview 76