Welcome To The VPLEX VS6 Hardware Architecture Course

Welcome to the VPLEX VS6 Hardware Architecture course
Copyright ©2015 EMC Corporation. All Rights Reserved. Published in the USA. 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. The trademarks, logos, and service marks (collectively "Trademarks")
appearing in this publication are the property of EMC Corporation and other parties. Nothing contained in this publication should be construed as granting any license or right to use any
Trademark without the prior written permission of the party that owns the Trademark.
EMC, EMC² AccessAnywhere Access Logix, AdvantEdge, AlphaStor, AppSync ApplicationXtender, ArchiveXtender, Atmos, Authentica, Authentic Problems, Automated Resource Manager,
AutoStart, AutoSwap, AVALONidm, Avamar, Bus-Tech, Captiva, Catalog Solution, C-Clip, Celerra, Celerra Replicator, Centera, CenterStage, CentraStar, EMC CertTracker. CIO Connect,
ClaimPack, ClaimsEditor, Claralert ,cLARiiON, ClientPak, CloudArray, Codebook Correlation Technology, Common Information Model, Compuset, Compute Anywhere, Configuration
Intelligence, Configuresoft, Connectrix, Constellation Computing, EMC ControlCenter, CopyCross, CopyPoint, CX, DataBridge , Data Protection Suite. Data Protection Advisor, DBClassify, DD
Boost, Dantz, DatabaseXtender, Data Domain, Direct Matrix Architecture, DiskXtender, DiskXtender 2000, DLS ECO, Document Sciences, Documentum, DR Anywhere, ECS, elnput, E-Lab,
Elastic Cloud Storage, EmailXaminer, EmailXtender , EMC Centera, EMC ControlCenter, EMC LifeLine, EMCTV, Enginuity, EPFM. eRoom, Event Explorer, FAST, FarPoint, FirstPass, FLARE,
FormWare, Geosynchrony, Global File Virtualization, Graphic Visualization, Greenplum, HighRoad, HomeBase, Illuminator , InfoArchive, InfoMover, Infoscape, Infra, InputAccel, InputAccel
Express, Invista, Ionix, ISIS,Kazeon, EMC LifeLine, Mainframe Appliance for Storage, Mainframe Data Library, Max Retriever, MCx, MediaStor , Metro, MetroPoint, MirrorView, Multi-Band
Deduplication,Navisphere, Netstorage, NetWorker, nLayers, EMC OnCourse, OnAlert, OpenScale, Petrocloud, PixTools, Powerlink, PowerPath, PowerSnap, ProSphere, ProtectEverywhere,
ProtectPoint, EMC Proven, EMC Proven Professional, QuickScan, RAPIDPath, EMC RecoverPoint, Rainfinity, RepliCare, RepliStor, ResourcePak, Retrospect, RSA, the RSA logo, SafeLine, SAN
Advisor, SAN Copy, SAN Manager, ScaleIO Smarts, EMC Snap, SnapImage, SnapSure, SnapView, SourceOne, SRDF, EMC Storage Administrator, StorageScope, SupportMate, SymmAPI,
SymmEnabler, Symmetrix, Symmetrix DMX, Symmetrix VMAX, TimeFinder, TwinStrata, UltraFlex, UltraPoint, UltraScale, Unisphere, Universal Data Consistency, Vblock, Velocity, Viewlets, ViPR,
Virtual Matrix, Virtual Matrix Architecture, Virtual Provisioning, Virtualize Everything, Compromise Nothing, Virtuent, VMAX, VMAXe, VNX, VNXe, Voyence, VPLEX, VSAM-Assist, VSAM I/O
PLUS, VSET, VSPEX, Watch4net, WebXtender, xPression, xPresso, Xtrem, XtremCache, XtremSF, XtremSW, XtremIO, YottaYotta, Zero-Friction Enterprise Storage.
Copyright 2016 EMC Corporation. All rights reserved. VPLEX VS6 Hardware Architecture 1
This course covers the hardware architecture of the next generation VS6 VPLEX. It will
explain the different configurations available as well as the proper way to wire the systems.
This module focuses on the different models of the VS6, the individual hardware
components and how to connect to the MMCS.
The VPLEX VS6 is the 3rd generation in the VPLEX family of products. It is more powerful than its predecessor, the
VS2, in that it comes with the latest generation of multi-core CPUs by Intel, makes better utilization of the multi-
core capabilities, has four times the amount of cache installed per director and has over four times the bandwidth
for intra cluster communications through the use of InfiniBand rather than Fibre Channel technologies. For the
front end (FE) and back end (BE), the system has double the speed of the previous version going from 8 Gb to
4/8/16 Gb FC I/O modules. A big change in this generation is the replacement of the external management server
to a pair of integrated Management Module Control Stations (MMCS) which are part of the base engine. Only the
MMCS in the A Director is active for the initial release of the product. All additional engines come with standard
management modules in the same slot. In a Metro configuration, the MMCS-A modules act the same as the
Management Servers in prior versions of VPLEX where management can be done from either site. Another
enhancement in the VS6 is the addition of a Baseboard Management Controller (BMC) which is used to remotely
monitor and manage directors when needed. It can reset or power on/off each director individually to improve
serviceability of the system.
It should be noted that the initial release of the VS6, if used in a metro configuration, only supports using the 16
Gb FC module for connectivity. This will be an increase over the current 10 Gb connectivity option but will limit the
distance supported. IP-metro will be supported in a future release of GeoSynchrony.
Shown here is a comparison between the current VS2 model and the new VS6. The first item of note is the
dual 6-core Intel Haswell/Broadwell processors with two threads per core. This is a 300% increase in the amount of
processing power of the VS2 per director. Each director is loaded with eight 16 GB 2133 MHz DDR4 DIMMS with a
bandwidth of 136.5 GB/s, four times the amount of the VS2. The VS2 has an external management server whereas
the VS6 has dual MMCS installed in the base engine. At release only the MMCS-A unit will be actively managing the
system. The MMCS do not manage customer data. Failure of MMCS-A will block configuration changes until
replaced or recovered but the loss of the MMCS will not interrupt host I/O. The loss of MMCS-B will have no
impact for day to day operations, but MMCS-B must be operational for NDU purposes. Another big difference in
the two models is the use of dual 40 Gb InfiniBand switches for intra engine communications. This will increase the
bandwidth more than four times the 8 Gb FC of the previous model. At release time the VS6 will support up to
12,000 virtual volumes, a 50% increase over the VS2. That is expected to increase with future releases of
GeoSynchrony. The last item of note here is the inter cluster communications used in VPLEX Metro. At release time
the VS6 will support the 16 Gb FC module only. While this is an increase over the 8 Gb FC and 10 Gb IP options of
the VS2, it does limit the distance supported due to the FC only option. IP connectivity is expected in a future
GeoSynchrony release.
As noted on the previous screen, the configuration maximums are increased for VS6. Using
the health-check command, we can see that the maximum number of storage volumes is
12,000, which is an increase of 50% over VS2 systems. We can also see that VS6 is being
identified as the VPL hardware type. This will be displayed in all the VPlexcli commands
where the model type is displayed.
The VPLEX VS6 consists of several sizes and configurations. It comes in three sizes, small
with a single engine holding two directors, medium with 2 engines and 4 directors, and
large with four engines and 8 directors. At release there will be no upgrades from one size
to another. The VS6 is also supported in two configurations. The first is a stand-alone
system in any of the three sizes, small, medium or large, called a VPLEX Local. The second
configuration is a VPLEX Metro with one VPLEX VS6 being mirrored to a separate VPLEX VS6
of the same size. At the time of release only Fibre Channel is supported as a connectivity
option in a metro configuration. IP-Metro will be supported in a later release. Also only a
VS6 to VS6 metro configuration is supported. VS2 to VS6 will only be supported for a short
time while performing a migration from the VS2 platform to the VS6. This is discussed in
the VPLEX VS2 migration to VS6 course.
As with other EMC products, the VPLEX VS6 can be ordered preinstalled in an EMC rack. For
the small configuration you get a rack loaded with a single base engine with the MMCS
installed, two cable management trays and a laptop tray preinstalled. The medium
configuration comes with two VS6 engines, a base engine with the MMCS and a second
engine with just management modules installed, two Infiniband switches, two UPS for the
InfiniBand switches, three cable management trays and the laptop tray. The large
configuration is preinstalled with a base engine, three engines with management modules,
two Infiniband switches, two UPS for the switches, six cable management trays and the
laptop tray. The VS6 chassis are physically longer than the VS2 and as such require
customer facing racks with rear facing PDUs or front facing models that are easily
accessible. Depending on the number of engines purchased, from 2-4 PDUs are required.
The number of cable management trays also varies depending on the number of engines
installed. Other than the laptop tray, the rest of any unused space can be used in the rack
for the customers equipment to be installed. If a customer does use the space, and later
decides that they will expand their cluster when available, they will have to move non-
VPLEX equipment so that the VPLEX can be installed in contiguous spaces. There is a
service cable installed which runs from the MMCS-A to the laptop tray for customer and PS
usage as shown in the image here.
The customer has the option of having the VPLEX VS6 installed in their own cabinet as part
of a PS engagement. The small, single engine system is shipped in a box with any WAN
COM modules installed in it. Two cable management assemblies and the required cables are
in separate boxes. It should be noted that a fully loaded VS6 engine weighs 119 Lbs. and
requires two people and a lift to safely install it. Please refer to the EMC VS6 Field Deploy
manual for the proper instructions. With the introduction of the VS6, quad engine systems
can now be installed in a customer’s rack, unlike the VS2. As noted earlier verify that the
rack has sufficient depth to accommodate the added length of the VS6 and that the PDUs
will be accessible. If a customer orders a 2 or 4 engine cluster, the engines will come in 1 or
2 virtual shipping racks with the I/O cards already installed. Additionally they will receive
dual UPS and InfiniBand switches in boxes shipped with the virtual racks. Shown here is an
illustration of the virtual rack.
Here we will take a high level look at the components which make up the VPLEX VS6
starting with the Base Engine from the front side. An in depth look will be done in the next
module. The first thing to note is that the VS6 (VPL) DPE is a 4U chassis compared to the
2U VS2. It has 25 slots for 2.5” drives, which are not planned to be used and instead are
filled with disk fillers. The bottom half of the engine compartment is dedicated to Director-A
components in an upright position. The top half of the engine compartment holds Director-
B. Notice that Director-B is inverted compared to A. This is different from the VS2 where
the directors are side by side in the engine. The CPU PCA for each director sits behind six
replaceable cooling fans and is removable from the front of the unit. The last components
are the paired Battery Backup Units (BBUs) for each director. These are NOT in an N+1
configuration as both are required to power the directors in the event of a power failure.
This view is of the rear of the Base Engine compartment. As noted on the previous slide,
Director-A is on the bottom of the compartment sitting in an upright position. The I/O slots
for Director-A run from left to right. A0 is for the 16 Gb FC FE card, A1 has the 16 Gb BE
card, A2 the 16 Gb WANCOM card if ordered, A3 the 40 Gb Infiniband card and slot A4 is
left empty. This slot is used for another FC card temporarily when migrating from a VS2 to
the VS6. The ports are numbered from bottom to top. Director-B is inverted above it in the
top of the engine compartment, running right to left. Take note of the slots for the I/O
modules are numbered in the reverse order and the ports are numbered from the top to the
bottom.
Now for a closer look at the components that make up the directors. As shown previously the first components
running left to right in a director when viewed right-side up, are the I/O modules sitting is slots 0-4. The WCOM
slot will only be filled if a metro configuration is ordered and, for release, it can only be a 4/8/16 Gb FC module.
The next components in the center of the unit are the dual chassis fans which are not used in the VPLEX VS6 and so
have fillers installed. Below the fans are the Management Module Control Station (MMCS) used to manage and
monitor the actions of the VPLEX system. Only the Director-A MMCS is active at introduction. If the directors are in
engines 2-4, instead of an MMCS, there is a Management Module as shown here. These units are connected to the
MMCS through Ethernet cables to manage the other directors. In the top right of the director sits the Base
Module. In this implementation of the VPL engine, the Base Module has no functionality and is just a filler,
although it is used in other EMC products. Since it needs no cooling, the fan modules are also fillers. The last
components are the dual power supplies (PS). They are in an N+1 configuration and either has enough wattage to
run the director.
Connecting to and configuring the IP address is a bit different on the VS6 with MMCS versus the VS2
and its management server. First an overview of the MMCS ports and their usage, then how to
configure the IP addresses of the MMCSs. When looking at the MMCS and the lower, Director-A
positioning, the top two ports on the upper left are for USB connectivity when a system has to be re-
imaged by a Support Engineer. The top center port is for video. Using the supplied cable you can
connect a monitor on the MMCS if desired. The bottom left port is for the MRJ21 cable. This 3 leg
adapter is used to connect to the A and B sides of the management network between engines, with
the lime colored leg for the .252 subnet for A and the violet colored leg for the .253 B side. The black
colored leg is used to connect the eth3 interface port to the customers management IP network. The
last port used for management is the eth1 service port. When the VS6 is shipped in an EMC rack, this
reddish cable connects the service port to the laptop tray installed in the rack. To configure the IP
address for MMCS-A do the following:
1. Connect your laptop to the service port on MMCS-A using the red cable.
2. Set the laptop to an IP address on the 128.221.252.3-30 range, then open a command window
and ping the 128.221.252.2 IP address to verify the port is available. Note: DHCP can also be
used on your laptop rather than a manual setting.
3. Launch PuTTY to connect to IP address 128.221.252.2.
4. Log in to MMCS-A with username service and the service account password. From the shell
prompt, type the following command, where hostname is a name that replaces the default name
(ManagementServer) in the shell prompt in subsequent logins to the MMCS: do not use the Linux
OS hostname command to make this change.
sudo /opt/emc/VPlex/tools/ipconfig/changehostname.py -n <hostname>
1. Type the vplexcli command, which connects you to the VPlexcli.
2. From the VPlexcli prompt, type the following command to configure the IP address of the Ethernet
public port (eth3) of the MMCS: management-server set-ip -i IP_address/netmask -g
gateway eth3.
3. To configure the eth3 port on MMCS-B, use the same command with the –r option at the end of
the command: management-server set-ip -i IP_address/netmask -g gateway eth3 -r
4. You can now change your laptop IP address to the users management subnet and connect to the
MMCS through that network if desired.
For more configuration details see the Configuring a VPLEX Local implementation EMC VPLEX
GeoSynchrony VS6 Configuration Guide.
Other components needed for VPLEX systems are shown in this rack illustration. Unlike the
dual FC switches in the VS2 for 2 or more engines, the VS6 uses dual 40 Gb InfiniBand
switches to provide all the Local Communications between the directors. They are fully
populated with ports and there are no licenses needed. These switches will remain running
until the system powers off in case of a power failure. To keep them running, the system
comes with dual Uninterruptible Power Supplies (UPS ), which are connected to each power
leg in the rack, and they have enough power individually to keep both switches running for
5 minutes, until the system powers off. The VS6 also comes with 2-6 cable management
trays, depending on the number of engines installed, which sit above and below each
engine to secure all the cables. These have labels on them for component location, and also
to make it easier for component replacement by keeping the cables out of the way.
This is a list of all the FRUs in the VPLEX VS6. There are no Customer Replaceable Units
(CRUs) in the VS6.
All these FRUs have replacement procedures that need to be followed when a replacement
is needed.
Note: These FRUs have procedures for Configured state (after the EZ-Setup utility has
successfully created the VPLEX cluster) and for Unconfigured state replacements (before
the EZ-setup was run). Make sure you know which state your VPLEX is in and use the
correct replacement procedure.
The VS6 VPL Engine part number labels are attached to blue plastic tags that can be pulled out for inspection for
part and serial numbers from the front of the engines. The locations are as follows:
The VPL chassis part number is located in the left side of the drive bay. The WWN seed number tag is in the right
side of the drive bay. The tags for the A and B Director part numbers are at the end of the row of fans. There are
also tags with the part number for Director spares which come without any DIMMs or an SSD drive loaded.
Starting in GeoSynchrony 5.5, during a power failure the VPLEX will immediately quiesce all
I/O and halt operations. In the VS6 there is enough power in the BBUs and the UPS to keep
the directors, IB switches and the Management Modules running until the data is safely
stored away. This should take less than a minute. If the power resumes and drops again
there is enough reserve power for a second shutdown.
The VS6 model introduces a Baseboard Management Controller (BMC) into the system. It
provides board control for the directors so that reset and power commands can be
implemented on each one individually.
The thermal shutdown strategy for the VS6 is the following:
When the temperature reaches 35 oC, a warning event is emitted. When it reaches 40 oC, a
critical event is emitted which triggers the BMC to generate an event and to shutdown the
director. Once the temperature has receded below 35 oC, the BMC will auto-start the
director.
This module gave an overview of the VS6 components and their FRU strategy.
Copyright 2016 EMC Corporation. All rights reserved. Course Name 18

This module focuses on the individual hardware components, their locations, and the proper
way they are cabled together.
In this section we will take a closer look at all the components which make up the VPLEX
VS6 engine. Looking at the front of the engine chassis the first thing to note is that it is 4U
in height. There are two VPLEX Directors, 25 disk fillers in the disk slots since the disks are
not used in this implementation, 4 Battery Backup Units (BBUs), and 12 removable fans.
We will look at these in detail in the next few slides. Now for a look at the rear of the engine
chassis. Here we can see are 10 I/O module slots, 2 Base modules, 4 power supplies, either
2 MMCS if this is the Base engine, or 2 Management Modules if engines 2-4, and finally 8
fan fillers as there are no active fans on the rear side at introduction.
Lets start with the front of the engine. We see that Director A is on the bottom of the unit
sitting right side up, and Director B is inverted on the top side of the chassis. With the
director pulled out of the engine we can get a closer look as shown in this top view. Each
Director has two CPU sockets loaded with a 135W Haswell/Broadwell Intel 6-core Processor,
giving each director 12 CPU cores to use. There are 12 DDR4 DIMM slots available per CPU,
but only eight are filled with a 16 GB DIMM for a total of 128 GB. The CPUs are covered with
an air baffle which shows the DIMM locations. Shown here is a view of the bottom of the
director.
Looking at the director without the air baffle we get a better look at the DIMM slots and the
CPUs. Shown here is the DDR4 DIMM which can use 8 memory channels per CPU module.
Another component of the director is the Solid State Disk (SSD) assembly which holds the
boot image. The initial shipping version will be a SmartModular PS3108 64 GB SSD (60 mm
length). An Intel S3500DC 80 GB SSD (80 mm length) version will be supported by the end
of the year. The SSDs are held in with a thumb screw and if the 64 GB is replaced with the
80 GB version, it will have to be relocated to a larger slot mounting position.
There are two more components on the front of the engines to take a look at. On the VPLEX
VS6, the engine Battery Backup Units (BBUs) are built into or embedded into the engine
chassis. The embedded BBUs provide power directly to the engine DC power bus hence
sometimes called ‘Battery-on-Bus’ or ‘BoB’ units. These are dual Lithium-Ion batteries
which are NOT redundant. Both units need to be charged in order to support the directors in
case of a power failure. On failure the system will immediately quiesce and cache active
data with the BBUs providing 2 minutes of shutdown power. If the system reboots and loses
power right away, the BBUs will be able to provide a second 2 minute window. The reduced
hold time helps to extend the life of the battery. The BBUs are a hot swappable FRU.
The front of each director is loaded with six cooling fans. Each fan module has dual-counter-
rotating fans; one inlet fan and one outlet fan per module. When a fan fails, the BMC
creates entries in the Sensor Event Log (SEL). The SEL entries reference the specific fan by
sensor number as outlined in a table found at the end of this module. A director will run
indefinitely with one fan failed or removed (removed has an SEL entry). A second fan failure
will force a shutdown after 5 minutes. Note that these fans only cool the directors, as the
base modules have separate cooling zones.
Now we turn to the rear of the engine to examine the components. The first items
highlighted here are the dual power supply units for each director, in this case for Director
B. They easily pull out from the chassis as shown for Director A’s units. The units are N+1
redundant for each director and are hot swappable. Depending on the manufacturer there
are two part numbers and the power ranges from 1050-1100 Watts. The units are auto
sensing for the input voltage. Each power supply unit connects to the PDU on its respective
side in the Titan Rack. The left and right PDUs connect to main power through their
respective power distribution units (PDUs) mounted in the rack. If viewed from the rear of
the rack, the side-A PDU is on the right and the Side-B PDU is on the left. So each director
will have one power supply connected to side-A (grey cord) and one connected to side-B
(black cord).
The next items to look at are the I/O modules. VPLEX I/O Modules are small hot pluggable
PCIe cards that perform director I/O operations. With VS6 technology, there are also two
types of I/O modules. The first we will look at is the 4-port 4/8/16 Gbps Fibre Channel
module that is used as follows:
• Slot 0 for FE connections to hosts and Slot 1 for BE connections to storage arrays.
• Slot 2 for WAN COM (2 ports are used if a VPLEX Metro – other 2 ports are not used).
• The I/O modules have dual ASICs onboard which each control two ports for better
performance, unlike the previous 8 Gbps of the VS2 which had a single ASIC for four
ports. The cards are not hot swappable and will cause a system reboot if they are
removed while the director is powered on. The ports require the use of an Small Form
Pluggable (SFP) transceiver for each port used. The cards are manufactured by Avago
(formerly Emulex) and supply 4/8/16 Gb/s throughput. They support P2P (Nport to FPort,
NPort to NPort), Loop (Public and Private) – but Loop is only supported at 8 Gb/s. They
are also backward compatible with 8 Gb and 4 Gb FC.
The second I/O module to look at is in slot 3 of both directors. It is a 2-Port InfiniBand
module that is used for Local Com communications between all the directors. The ports are
4x FDR (approx. 40 Gbps). This is more than four times the throughput of the VS2 using 8
Gbps FC technology. The unit ships with InfiniBand cables of either .5m or 2.0m depending
on the number of engines in the configuration. The cards are not hot swappable and as with
the FC modules will cause a reboot of the director if removed with the power on. If only a
single engine is installed the cables are configured direct connect from one director to the
other. If 2-4 engines are used they will be plugged into a switched fabric.
The VPL chassis used in the VPLEX VS6 is also used in other EMC products. One component
of the chassis is the Base module highlighted here. The version of Base module in the VS6
is just a filler. It has been stripped of its functionality and as such requires no fans for
cooling so they have been replaced with fillers. The Base module is in a separate cooling
zone from the directors so the lack of fans does not affect them. The Base module is a hot
swappable assembly should it ever fail and need replacing.
A major change in the VPL Engine as compared to the VS2 is the addition of the MMCS,
outlined here, which takes the place of the Management Server in the VS2. The dual MMCS
are only in the base Engine number 1, and are not redundant. During normal operation the
Side-A MMCS acts as the system management server (SMS) interface providing VPlexcli
support. The Side-B MMCS will function as a router with enhanced Management Module
functionality supporting only management network communication on subnet-B and some
logging functions. The user will log-in through a fixed customer IP address dedicated to the
Side-A MMCS customer connection. Side-B customer connectivity will not be supported.
VPLEX services are disabled on MMCS-B: VPLEX CLI, Call Home and Core Collection. The
MMCS Mini-SP servers are provided with a default Atom processor and DRAM
configurations. However, the VPLEX version of the MMCS includes a 128 GB mSATA SSD
drive which is not a FRU. If there is any component failure, the entire MMCS must be
replaced. The Management Module shown here is in Engines 2-4, and provides Ethernet
management network connectivity for the cluster as well as serial and USB connection to
each of the storage processors. Both the MMCS and the MM are hot swappable
components.
The MMCS in engine 1 director 1 is used as the management server for the cluster. There
is a service port for connecting a service laptop, and a MRJ21 cable assembly that provides
three more IP ports. The lime-green cable is for the .252 subnet, the pink/violet cable is for
the .253 subnet, and the black cable is used to connect to the data center management
network for customer access and control.
Now for a look at the rest of the components in the VS6 rack when 2-4 engines are
installed. The first items are the dual InfiniBand switches. These are Mellanox MSX6005T-
2BFS 12 port QDR/FDR10 IB switches, which are unmanaged and so are plug and play.
They have dual embedded power supplies (not FRUs) which are backed up by external UPS
units, are 1U, half width, standard depth units. The mounting solution supports two
switches side-by-side in a standard rack. These create dual 40 Gbps fabrics for the LCOM
inter-Director communications network. Shown here are the status and error conditions
which are displayed on the front of each switch.
To keep the InfiniBand switches running in the event of a power loss, the system will need
UPS units. Two Emerson UPS units, which will provide BBU support, are racked just above
them. The UPS units are capable of keeping the Infiniband switches running for a 5-minute
shutdown period at power fail, and if the system resumes operation and then fails again,
they can support another 5-minute period. The UPS are unmanaged, but they are
monitored through a serial control interface which connects to the Management Modules of
Engine #2’s COM2 battery port as shown here. UPS-A goes to the MM-A module and UPS-B
goes to the MM-B module. If the Replace Battery LED on the front of the UPS is red, it
indicates that the battery is faulty or has expired. Replace the entire UPS, whether the fault
is in the UPS itself or its battery.
This graphic represents how power is supplied to the InfiniBand switches in the VS6
technology models. We have used several colors to make them easier to see in the
graphic, [click] but the cables are actually grey for Zone A and IB SW-A, and black for Zone
B and IB SW-B.
These Emerson UPS units are the same for both VS2 (to backup Local COM FC switches)
and VS6 technology (to backup Local COM IB switches).
This interactive display will allow you to see how the VPLEX VS6 system is cabled depending
on the number of engines installed.
Shown here are the different error LEDs in the system for the Engine and InfiniBand
switches, and their meanings. Please take a moment to review the tables and the notes
below.
Component LED color when powered on:

Director power LED: Solid blue
Marker LED solid yellow for approximately 30 seconds, then flashes for several minutes, then turns off.
Chassis Power LED: Solid blue.
Marker LED: Solid yellow for approximately 30 seconds, then turns off.
Battery Backup Unit Power LED: Solid blue
MMCS Power LED: Solid green
Power Supply Unit Power LED: Solid green
I/O modules Power LEDs Solid green after several seconds
Each Hyperion director has six dual-counter-rotating fans; one inlet fan and one outlet fan
per module. Each pair of fans correlate to a director fan module described in the Fan #
column of the table. When a fan fails, the BMC creates entries in the Sensor Event Log
(SEL). The SEL entries reference the specific fan by sensor number as outlined in the table.
This module covered the system components which make up the VPLEX VS6.
Copyright 2016 EMC Corporation. All rights reserved. Course Name 36

This course covered the new hardware of the VPLEX VS6 including hardware component
details, system types and the correct way to cable the unit.
This concludes the training. Proceed to the course assessment on the next slide.

Welcome To The VPLEX VS6 Hardware Architecture Course

Hochgeladen von

Dokumentinformationen

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Welcome To The VPLEX VS6 Hardware Architecture Course

Hochgeladen von

Copyright:

Verfügbare Formate

Welcome to the VPLEX VS6 Hardware Architecture course

The thermal shutdown strategy for the VS6 is the following:

Copyright 2016 EMC Corporation. All rights reserved. Course Name 18

Component LED color when powered on:

Copyright 2016 EMC Corporation. All rights reserved. Course Name 36

Das könnte Ihnen auch gefallen