VMAX3 Hardware Overview: Models, Components, Layout

SYMMETRIX VMAX3
INTERNALS: Essentials
Hardware Overview
EMC CONFIDENTIALINTERNAL USE ONLY
Symmetrix Hardware Objectives

After completing this module you will be able to:
Differentiate the 100K, 200K, & 400K VMAX3 models

Describe the physical components of the system and
their function
Describe the physical placement of components in

the rack
Map the physical layout of the Symmetrix VMAX to
the logical architecture
Identify the source and destination points for cables
that interconnect the system components
Symmetrix VMAX3 Family

Current generation of the Symmetrix VMAX Family
New hardware platform
Redesigned Operating Environment
Virtual Provisioning preconfigured from factory

Significant changes to logical layout
Provisioning based on Service Level Objective (SLO)
Ongoing monitoring of SLO to ensure compliance
Fewer knobs to turn to ensure optimum performance
Flexible configuration
Single and two engine rack with associated physical disk
Dispersed system bays
Support for customer provided racks
Symmetrix VMAX3 Family

VMAX 100K
VMAX 200K
VMAX 400K
Internal Nick Name
Lapis
Alexandrite
Ruby
# of Engines
1-2
1-4
1-8
Engine Type
Megatron Lite
2.1 GHz
24 IVB core
128GB,
256GB, 512GB
Memory
Megatron
2.6 GHz
32 IVB core
256GB, 512GB
1TB, 2 TB
Memory
Megatron Heavy
2.7 GHz
48 IVB core
256GB, 512GB
1TB, 2 TB
Memory
Cache Memory
Up to 1 TB
Up to 8 TB
Up to 16 TB
Max. 2.5 Drives
1440
2880
5760
Max. 3.5 Drives
720
1440
2880
Max Front End

ports
64
128
256
VMAX 100K
Supports 1-2 engines
Each engine includes two directors with dual
(6) core 2.1 Ghz Ivy Bridge processors
512GB, 1TB memory per engine
Up to 1440 2.5 drives, up to 720 3.5 drives

Up to 1 TB raw memory
Up to 440 TBu capacity
Up to 64 FE ports
Integrated Management Module Control Station
(MMCS)
InfiniBand 56Gb/sec Virtual Matrix Fabric for

systems with > 1 engine
VMAX 200K
Each engine includes two directors with dual (8)
core 2.6 GHz Ivy Bridge processors
512GB, 1TB, 2TB memory per engine

Up to 8 TBr memory
Up to 1.8 PBu capacity
Up to 128 FE ports
Integrated Management Module Control Station
(MMCS)
InfiniBand 56Gb/sec Virtual Matrix for systems
with > 1 engine
VMAX 400K
Each engine includes two directors with dual
(12) core 2.7 GHz Ivy Bridge processors
512GB, 1TB, 2TB memory per engine

Up to 16 TBr memory
Up to 3.8 PBu capacity
Up to 256 FE ports
Integrated Management Module Control
Station (MMCS)
InfiniBand 56Gb/sec Virtual Matrix for systems
with > 1 engine
VMAX 100K, 200K, 400K All Flash Array

All Flash drive configuration
Available in all models

Simplified SW packaging/pricing
Common Set of Configuration Rules

Apply to all Models
Engines may be added in single increments
DAEs may be added in single increments

DAE types may be mixed in single increments
Max 720 2.5 drives / 360 3.5 drives per
engine
Same drive types and RAID protection
11 Slots for IO modules with same modules
types and placement
Models are differentiated by type and quantity

of engines and the attributes of the engine
Processor speed and number of cores
Cache memory size
Drive count and usable capacity
VMAX3 Engine
Basic building block for Symmetrix system
System contains 1 8 engines depending on model

One or two engines per rack
Each engine includes two

director boards
All engines have similar
attributes
4U enclosure
Redundant power and cooling
Two management modules
11 slots for IO modules
10
VMAX3 Director
Each engine contains two directors
Odd number director on bottom
Even number director on top
Removed through the front
Multi-core processor
100K - 2.1GHz, 12 IVB core
200K - 2.6 GHz, 16 IVB core
400K - 2.7 GHz, 24 IVB core
Memory 16 DIMMs
16GB, 32GB, 64 GB DIMMs
All slots must be populated
(11) IO modules slots access from the back

Redundant power and cooling
11
Director Board Details

Dual Ivy Bridge Processors
100K - 2.1GHz, 12 core
200K - 2.6 GHz, 16 core
400K - 2.7 GHz, 24 core
PCH Platform Control Hub

Management Module
PLX 8748/24 PCI Express
Gen 3 switches
11 PCIe IO Modules
12
Memory and CPU

CPU
Memory
2 CPU sockets per director
16 Memory Slots
100K
2.1GHz, 24 IVB core
200K
2.6 GHz, 32 IVB core
400K
2.7 GHz, 48 IVB core
Hyper threading is enabled

Logical cores are dynamically
allocated to Emulation code
in the IMPL.bin
16GB, 32GB, 64 GB DIMMs
All slots must be populated

Requirements based on
system configuration
~1TB cache for every
250TiB of raw capacity
Plan for over subscription
and replication overhead
DXCX configuration tool

follows SymmWin logic and
can provide more precise
estimates
13
Management Module Control Station

(MMCS)
Point of Management for the
System
Replaces the service processor
Runs Windows 2007, SymmWin ,
and other services
IA64 Atom processor, 4GB
Memory, 128 GB SATA drive
(4) Ethernet for Customer, Mgmt,
2 Service LAN
(3) Serial ports in micro HDMI for
SPS & Modem
(3) Micro-USB for light bar,
Service, KVM
MMCS are installed in both

directors of the first engine of
each system
14
MMCS Redundancy
Primary (MMCS1) installed in director slot 1
Secondary (MMCS2) installed in director slot 2

Manual failover in the event primary fails
Call home on system errors
Replacement scripts for MMCS1 and Director 1
components
Secondary has own unique IP address and user

would need to reconnect
KVM connects only to primary
In the event primary fails, cables must be moved
manually following instructions in Simplified Symmwin
Files and directories are synchronized between

MMCS using the RSync utility
Primary
MMCS
RSync
When secondary is elevated, it has limited

capability
Secondary
MMCS
15
Management Module
MMCS is only in the first engine,
all other engines have
Management Modules (MM)
Provides Ethernet connection
between the engine and the
MMCS
Second IP port goes to service tray
Environmental monitoring
I2C interface to board resume,
power sequencer
Monitor and control of SPS
USB Power to Bay Locater LEDs
Odd number director - Front LED
Even number director - Rear LED
16
SymmWin Management Application That

Runs on MMCS
SymmWin
Legacy full feature
Engineering Interface
Simplified SymmWin
New graphical user
interface intended for
Customer Service use
17
11 Slots for IO Modules Per Director

Up to four slots are used for front end IO modules
Including 4-Port 8/16 Gb FC IO modules
Two backend IO modules per director

Each module provides two ports
Each port has 4 lanes of 6 Gb/sec SAS
Two or four Flash IO module

Each director vaults to Flash if required
Flash also used for system Meta Data
Flash IO modules eliminate the need for vault disk
drives or battery backup for DAEs
System Interface Board

Single engine systems will have no fabric
Multi-Engine systems will have fabric
Fabric switches and SIB are added online when second
engine is configured
18
Engine Physical Layout

I/O Module Slots numbers 0-10 from left to right
Management Vault to
Module
Flash
Slot
5
2
1
0
2
1
0
2
1
0
2
1
0
2
1
0
2
1
0
2
1
0
2
1
0
Universal/FE
Back-End
Slot
6
Slot
7
Vault to
Flash
Slot
4
Vault to
Flash
Slot
3
Vault to
Flash
Slot
2
Vault to
Flash
Vault to
Flash
Slot
1
Vault to
Flash
Vault to
Flash
Vault to
Flash
Management
A
Management
B
Slot
0
Vault to
Flash
Slot
8
Slot
9
2
1
0
2
1
0
2
1
0
2
1
0
Universal/FE
Slot
10
1
0
1
0
Even
Director
Odd
Director
Fabric
19
IO Module Slots
Designated for Specific Purposes
Two SAS backend IO modules always occupies slots 4 & 5
Two or four Flash SliC (Whirlwind) for Vault and MDP

Slot 0 - first, Slot 6 second, Slot 1 third, Slot 7 - fourth
Frontend IO modules always installed in pairs across directors

Slots 2,3 & 8,9
Non-Bifurcated I/O Modules will be populated left to right
Glacier (FE )
Bifurcated I/O modules will be populated right to left

Rainfall (FE)
Compression module is installed in any available universal slot

This is a Non-Bifurcated IO Module
Populated after FE modules
System Interface Board must occupy slot 10
20

Management Vault to
Module
Flash
Slot
5
2
1
0
2
1
0
2
1
0
2
1
0
2
1
0
2
1
0
2
1
0
2
1
0
Universal/FE
Back-End
Slot
6
Slot
7
Vault to
Flash
Slot
4
Vault to
Flash
Slot
3
Vault to
Flash
Slot
2
Vault to
Flash
Vault to
Flash
Slot
1
Vault to
Flash
Vault to
Flash
Vault to
Flash
Management
A
Management
B
Slot
0
Vault to
Flash
Slot
8
Slot
9
2
1
0
2
1
0
2
1
0
2
1
0
Universal/FE
Slot
10
1
0
1
0
Even
Director
Odd
Director
Fabric
21
IO Module Slots


Slots 2,3 & 8,9
Glacier (FE )

Rainfall (FE)

22

Management Vault to
Module
Flash
Slot
5
2
1
0
2
1
0
2
1
0
2
1
0
2
1
0
2
1
0
2
1
0
2
1
0
Universal/FE
Back-End
Slot
6
Slot
7
Vault to
Flash
Slot
4
Vault to
Flash
Slot
3
Vault to
Flash
Slot
2
Vault to
Flash
Vault to
Flash
Slot
1
Vault to
Flash
Vault to
Flash
Vault to
Flash
Management
A
Management
B
Slot
0
Vault to
Flash
Slot
8
Slot
9
2
1
0
2
1
0
2
1
0
2
1
0
Universal/FE
Slot
10
1
0
1
0
Even
Director
Odd
Director
Fabric
23
IO Module Slots


Slots 2,3 & 8,9
Glacier (FE )

Rainfall (FE)

24
I/O Module Population Order
Vault to
Flash
Slot
1
Vault to
Flash
Vault to
Flash
Vault to
Flash
Management
A
Management
A
Slot
0
Management Vault to
Module
Flash
3rd
1st
Slot
2
Slot
3
2
1
0
2
1
0
2
1
0
2
1
0
Universal/FE
Slot
4
1
0
1
0
Slot
5
1
0
1
0
Back-End
Slot
6
4th
Slot
7
Vault to
Flash
I/O Mod
Pop Oder
2nd
Vault to
Flash
3rd
Vault to
Flash
1st
Vault to
Flash
Vault Mod
Pop Order
Vault to
Flash
4th
2nd
Slot
8
Slot
9
2
1
0
2
1
0
2
1
0
2
1
0
Universal/FE
Slot
10
1
0
1
0
Even
Director
Odd
Director
Fabric
25
Frontend IO Modules
Provide host connectivity to the Symmetrix and
SRDF replication between systems
Type of
Emulations
Connection
Internal
Nickname
# Ports
Link
Speeds
Fibre
Channel
FC Host,
SRDF
Glacier
2/4/8 Gbps
Fibre
Channel
FC Host,
Rainfall
4/8/16 Gbps
Ethernet
10GigE
ISCSI*,
FCOE*,
SRDF
Heatwave
10 Gbps
Ethernet
1GigE
ISCSI*,
SRDF
Thunderbolt
2+2
1 Gbps
* Not available at GA
26
8Gb FC IO Module
Host and SRDF
connectivity
Quad port 8Gb Fibre

Channel IO interface
Supports both copper
(4G) and optical (8G)
media via SFP+
connector
8 lane PCIE Gen2.0
interface
Non-Bifurcated IO Modules
populated left to right
PMC Sierra Tachyon QE8

Fibre Channel controller
27
16Gb FC IO Module
Open Systems host
connectivity
Quad Port 16G Fibre

Channel IO interface
Supports optical media
via SFP+ connector
Two 4 lane PCIE Gen3

interfaces
Bifurcated I/O module
populated right to left
Emulex Lancer Fibre

Channel controller
28
10Gb Ethernet IO Module

Open Systems, and
SRDF connectivity
Dual Port 10GbE/FCoE

interface
Copper and optical
media via SFP+
connector
8 lane PCIE Gen1.0
interface or 4 lane PCIE
Gen2.0 interface
Qlogic EP8112
Converged Network
controller
29
IO Module Slots


Slots 2,3 & 8,9
Glacier (FE )

Rainfall (FE)

30
Director Board Details

Dual Ivy Bridge Processors
100K - 2.1GHz, 12 core
200K - 2.6 GHz, 16 core
400K - 2.7 GHz, 24 core
PCH Platform Control Hub

Management Module
PLX 8748/24 PCI Express
Gen 3 switches
11 PCIe IO Modules
31
10Gb Ethernet IO Module

Open Systems, and
SRDF connectivity
Dual Port 10GbE/FCoE

interface
Copper and optical
media via SFP+
connector
8 lane PCIE Gen1.0
interface or 4 lane PCIE
Gen2.0 interface
Qlogic EP8112
Converged Network
controller
32
1Gb Ethernet SLiC

Open Systems, and
SRDF connectivity
Quad port 1GbE

interface
Two Copper using RJ45
Two Optical using SFP+
connector
4 lane PCIE Gen1.0

interface
Two dual core Broadcom

GbE controller
BCM5715C Copper
BCM5715S - Optical
33
Other IO Modules
Provide backend, fabric interconnect, Flash storage
for vault and MDP, and compression
Type of
Connection
Purpose
Internal
Nickname
# Ports
Link
Speeds
SAS
Backend
DA
Moonshadow
6 Gbps
System
Interface
InfiniBand
Fabric
Gorgon
56 Gbps
Flash Drive
Vault &
Metadata
Paging
Whirlwind
NA
NA
SRDF
Asteroid
NA
NA
Compression*
34
6Gbs SAS Back End SLiC

Back end connectivity
from director to Disk
Array Enclosure (DAE)
Dual Port x4-lane

6Gb/sec SAS interface
8 lane PCIE Gen3.0
Copper media using
mini-SAS HD connector
Supports SAS wide-port
target mode and T10
DIF
Supports IEEE1619
compliant AES
encryption
35
Introducing SAS (Serial Attached SCSI)

Point-to-point full duplex, serial protocol that uses the standard
SCSI command set
Network-like star topology
SAS uses a connectionless tree structure with unique paths to

individual devices
Different than FC topology
Paths are stored in routing tables that are built during the
discovery phase and then used to route I/O to the desired end
points
Supports dual initiator and multi-pathed configurations
VMAX DA emulation threads function remains nearly the same

as Fibre Channel
SAS thread handles link state, connection table and enclosure DB
DA functions get handled by several separate threads
36
System Interface Board

PCIe to InfiniBand
Inter-director communication
and access to Global Memory
One per director on all multi

engine systems
Dual Port x4-lane 56
Gbits/sec InfiniBand FDR IB
16 lane PCIe Gen3.0
56 Gbits/sec IB FDR transfer
protocol per port using
copper QSFP cables
Mellanoxs Golan ASIC
37
FLASH IO Module
Provides FLASH storage
Global Memory Vaulting
Meta Data
Quantity and size

dependent on system
configuration
Micron P320 design with

32 Flash channels
Capacity: 350 & 700GB
Quantity and size
dependent on system
configuration
Sized for:
3 copies of metadata
2 Copies of cache
38
Vaulting
Vaulting: Process of saving
Global Memory data into a
reserved space during an
offline or Shutdown event
Uses FLASH IO modules
rather than disk space
Improved reliability
Eliminates the cost of SPS for
Disk Array Enclosures
Flash is faster than physical
disk and allows the vaulting
to complete quicker
Does not use disk space
39
Determining the Number of FLASH IO

Modules
Total required capacity is 2
x vault cache plus system
metadata
Engine
Cache
Flash IO
Modules
Installed in the following

order:
Total
FLASH
Capacity
512 GB
2 x 350GB
700GB
512 GB
2 x 700GB
1400GB
512 GB
4 x 350GB
1400GB
1024 GB
4 x 350GB
1400GB
1024 GB
6 x 350GB
2100GB
1024 GB
4 x 700GB
2800GB
2048 GB
6 x 700GB
4200GB
2048 GB
8 x 700GB
5600GB
1.
2.
3.
4.
Slot
Slot
Slot
Slot
0
6
1
7
Installed in pairs
All FLASH IO modules in an
engine must be the same
capacity
40
Compression IO Module
Hardware Compression
for SRDF
Optional
Optimize link utilization
Compression chip set

3 Exar chips
8 lane PCIE Gen2.0

interface
Installed in any
available universal slot
Non-bifurcated IO
module
Populated after FE
modules in systems
41
System Interconnection
Two different networks connect directors to each
other to form single system
IP network for management
InfiniBand network for director to director communication
and shared access to global memory
System with >1 Engine
Type of
Connection
Ethernet
InfiniBand
Purpose
Internal
Nickname
# Ports
Link
Speeds
System
Management
NA
16
1 Gbps
InfiniBand
Fabric
Gorgon
56 Gbps
42
GS900/16
Ethernet Switch
Used for system

initialization,
monitoring, and
management
Symmwin communication
Pair of 16-Port
unmanaged switches
Star topology connects:
MMCS in engine 1
connect to both switches
Each management
modules connect to one
switch
Connect to management
port on InfiniBand
switches
Only system
components may be
connected
43
Ethernet Connections
Dual switch, Star network topology, assigned ports
Both MMCS connect to both switches
MM in Directors 3-16 spread across switch
Assigned ports
MCCS-1
Eng 1
MCCS-2
Eng 1
MM-4
Eng 2
MM-12
Eng 6
MM-16
Eng 8
MM-3
Eng 2
MM-7
Eng 4
MM-11
Eng 6
01 03 05 07 09 11 13 15
01 03 05 07 09 11 13 15
ETHER-SW B
172.17.0.0/16
ETHER-SW A
172.16.0.0/16
02 04 06 08 10 12 14 16
02 04 06 08 10 12 14 16
MIBE-B
MM-8
Eng 4
MM-6
Eng 3
MM-10
Eng 5
MM-14
Eng 7
Customer
Service
MIBE-B
MM-5
Eng 3
MM-9
Eng 5
MM-15
Eng 8
MM-13
ENG 7
44
InfiniBand Fabric Switches

Dual 18-port Stingray
switches in 1st Engine
1 Port per director
Used in 400K and All
Flash Arrays
Redundant and hot

swappable PS
Dual 12 Port Dingo

switches in 1st Engine
1 port per director
Used in 100K and 200K
configuration
Same chipset as stingray
Switch is complete FRU
45
InfiniBand Virtual Matrix

Provides low latency, high bandwidth connectivity
Required on all multi-engine configurations

Directors in a single engine system communicate over
internal message interface
Online upgrade when adding 2nd engine
Allows independent emulations on different director

boards to act as a single system
Inter-director communication
Access to Global Memory
System Metadata
Cache slots
Supports 25M System Bay dispersion using optical

connectors
46
Virtual Matrix Architecture

Virtual Matrix enables inter-director communications
CPU
CPU
CPU
Core
CPU
Core
CPU
Core
CPU
Core
CPU
Core
CPU
Core
Core
Core
Director
Matrix B
CPU
CPU
CPU
Core
CPU
Core
CPU
Core
CPU
Core
CPU
Core
CPU
Core
Core
Core
CPU
CPU
CPU
Core
CPU
Core
CPU
Core
CPU
Core
CPU
Core
CPU
Core
Core
Core
Frontend
Matrix A
Backend
CPU
CPU
CPU
Core
CPU
Core
CPU
Core
CPU
Core
CPU
Core
CPU
Core
Core
Core
Virtual Matrix
Memory
Memory
Memory
Memory
Memory
Memory
Memory
Memory
Memory
Memory
Memory
Memory
System Interface
Board (SIB)
Backend
Memory
Memory
Memory
Memory
Memory
Memory
Memory
Memory
Memory
Memory
Memory
Memory
System Interface
Board (SIB)
Frontend
System Interface Board (SIB) IO Module

Two independent InfiniBand switches
Director
47
Virtual Matrix
Distributed memory, single Global Memory address space
InfiniBand
Switch
SIB
CPUs
Mem
CTL
Memory
BE
(Disk)
FE
(Host)
SIB
CPUs
Mem
CTL
Memory
BE
(Disk)
FE
(Host)
InfiniBand
Switch
SIB
CPUs
Mem
CTL
SIB
CPUs
SIB
Mem
CTL
CPUs
Global Memory - Cache Slots

Memory
Memory ID Tables
Global
Memory Track
Global Memory Other Meta Data
BE
(Disk)
FE
(Host)
BE
(Disk)
FE
(Host)
Mem
CTL
Memory
BE
(Disk)
FE
(Host)
SIB
CPUs
Mem
CTL
Memory
BE
(Disk)
FE
(Host)
48
Disk Array Enclosures (DAE)

Provide physical enclosure for disk drives and connectivity to
the back end IO module
3U/4U Drawer
Redundant Link Control Cards (LCC)
Up to (60) 3.5 drives or (120) 2.5 drives
Point-to-point, full duplex, serial protocol with network-like star
topology
Directors in an engine share access to the same DAEs

Drives within DAE are dual ported
Redundant Power and cooling

Four separate power zones
Up to six DAEs per engine

Minimum of one
Two direct attached
Up to four more daisy chained
49
Disk Array Enclosures
Odd Director
Even Director
SAS IO SAS IO
Module 4 Module 5
0
1
0
1
SAS IO SAS IO
Module 4 Module 5
0
1
0
1
L
C
C
Direct Attached DAE
L
C
C
B
Daisy Chained DAE
L
C
C
L
C
C
L
C
C
L
C
C
All cable connections

are x4 6Gb/sec SAS
Drives are dual-ported
and have connection
to each LCC in a DAE
L
C
C
Direct Attached DAE
L
C
C
Daisy Chained DAE
50
Drawer-like Enclosures
DAE -120
Up to (120) 2.5 drives
DAE -60
Up to (60) 3.5 drives
3U drawer-style enclosure
4 U drawer-style enclosure
Two Link Control Cards (LCC)
Two Link Control Cards (LCC)
6G SAS connectivity, 8 x 4 mini SAS

connectors
6G SAS connectivity, 8 x 4 mini SAS

connectors
51
Power Zones Within DAE Eliminate

Single Points of Failure
Voyager DAE
E
D
C
B
A
PSU
A1
PSU A
PSU
A2
PSU
B1
Viking DAE
9
1
0
1
1
0 1 2 3 4
5 6 7 8 9
1 1 1 1 1
0 1 2 3 4
1 1 1 1 1
5 6 7 8 9
1
0
1
1
0 1 2 3 4
5 6 7 8 9
1 1 1 1 1
0 1 2 3 4
1 1 1 1 1
5 6 7 8 9
0 1 2 3 4
5 6 7 8 9
1 1 1 1 1
0 1 2 3 4
1 1 1 1 1
5 6 7 8 9
0 1 2 3 4
5 6 7 8 9
1 1 1 1 1
0 1 2 3 4
1 1 1 1 1
5 6 7 8 9
0 1 2 3 4
5 6 7 8 9
1 1 1 1 1
0 1 2 3 4
1 1 1 1 1
5 6 7 8 9
0 1 2 3 4
5 6 7 8 9
1 1 1 1 1
0 1 2 3 4
1 1 1 1 1
5 6 7 8 9
PSU B
1
0
1
0
1
0
PSU
B2
1
1
1
1
1
1
PSU
A1
PSU A
PSU
A2
PSU
B1
PSU B
PSU
B2
52
Physical Disks - 6 Gb/s SAS Interface

SSD Solid State Disk
3.5 - 200GB, 400GB, 800GB, 1.6 TB
2.5 - 200GB, 400GB, 800GB, 1.6 TB
10K RPM Mechanical Disk

3.5 - 300GB, 600GB, 1200GB
2.5 - 300GB, 600GB, 1200GB
7.2K RPM Mechanical Disk

3.5 - 2TB, 4TB
53
Tiered Solutions
Most workloads are skewed with 80-90% of the work being
performed by 10-20% of capacity
Therefore most system configurations are expected to have
multiple drive tiers
Exception might be all FLASH Arrays
Typical three tier solution

Flash
10K/15K RPM SAS drives
7.2K RPM larger capacity SAS drives
Typical two tier solution

10% 800 GB FLASH
90% 10K RPM 1.2 TB drives
Must balance engine power with drive capacity
Model workload and configuration using SymmMerge
54
Drive Sparing
Symmetrix proactively monitors drive errors and invokes hot
spares are required
Data is copied from failing drive or rebuilt from RAID
Sparing is typically a permanent configuration change
Configured as empty disks on a disk group basis

Each disk group must have a minimum of one spare configured
Requires one spare for every 50 drive of size, type, protection
1-50 disks requires 1 spare minimum

51-100 disks require 2 spares minimum
101-150 disks require 3 spares minimum and so on.
Rules same for HDD and Flash drives.
Preferred spare will be within the same DAE as the failed drive
55
Other System Components

KVM Keyboard Video Mouse
Interface for MMCS
Service Tray
Present in System Bay 2-n
Includes power and Ethernet for support
person to connect laptop
Standby Power Supplies (SPS) for each

Engine and for the InfiniBand Fabric
Li-Ion
Two Power Distribution Unit (PDU) per

system bay
56
IMPL.bin File
Configuration details are defined in the IMPL.bin file
Also know as simply the bin file
Created when system is initially configured in manufacturing
Displayed and modified using SymmWin utility on MMCS
Defines static configuration information

Number and type of Engines
Cache memory configuration
IMPL.bin
Physical disk and DAEs
IO Modules
Emulation instances and mapping of CPU
cores and IO ports to instances
Logical device configuration including pools and SRP
Guest OS configuration
Updated online to reflect logical changes, resource assignment,

and hardware upgrades
57
Each Physical Director Executes up to

Eight Independent Emulations (A H)
A. IM Emulation (always present)
Infrastructure Management
B. EDS Emulation (always present)
Enginuity Data Services
C. DS Emulation (always present)
Disk Adapter backend services
D.
Fiber (FA)
(SE)*
E.
One or more iSCSI
FCoE (FE)*
F.
Front End FICON (EF)*
Emulations Fiber SRDF (RA)
G.
GbE SRDF (RE)
H.
FTS (DX)*
Director
H
G
F
E
D
C
B
A
58
Example of an Eight Engine System

Slices A, B, & C are fixed (IM, EDS, DS)
Slices D, E, F, G, & H
Front end emulation (FA

SRDF emulation (RF or RE)
FTS Disk External (DX)
Not Configured (NC)
59
CPU Cores are Mapped to Emulation

Instances
VMAX multi-core processors allows the allocation of the
appropriate number of cores to an emulation
With hyper threading a single core provides two logical cores
Mapping of CPU cores to emulation code is dynamically

configured in the IMPL.bin file
Can be changes using an online configuration change*
Three policies:
Balanced
Frontend biased
Backend biased
Allocated to Guest OS containers as well as emulation code

Provides flexibility while maintaining a balanced configuration
that best leverages all available resources
Pooling of CPUs to emulation maintains balance
Respond to bursts of activity
60
Frontend Ports Mapped to Emulation

System designed to support up to
64 ports per director board
Ports 0-31 external
Ports 32-63 internal
FC
Emulation
RDF
Emulation
Ports on IO modules are mapped to

emulation instances
Provides flexibility to assign ports
as needed
Ports on IO modules can serve
multiple purposes
IO
Module
IO
Module
IO
Module
Same IO module can support both

FC host and SRDF connections
Ports are mapped to emulations in

the IMPL.bin file
61
Engine Logical Port Numbering

Logical ports are numbered left to right bottom to top across
the slots that contain FE or BE I/O Modules
Ports 0-31 (front end 4-11 & 24-31)
Management
Module
Vault to
Flash
Slot
5
11
15
19
10
14
18
13
17
12
11
Slot
8
Slot
9
27
31
26
30
25
29
16
24
28
15
19
27
31
10
14
18
26
30
13
17
25
29
12
16
24
28
Universal/FE
Back-End
Slot
6
Slot
7
Vault to
Flash
Slot
4
Vault to
Flash
Slot
3
Vault to
Flash
Slot
2
Vault to
Flash
Vault to
Flash
Slot
1
Vault to
Flash
Vault to
Flash
Vault to
Flash
Management
B
Management
B
Slot
0
Vault to
Flash
Slot
10
Even
Director
Odd
Director
Universal/FE
Fabric
62
Director Instances, Cores, & Ports
symcfg list -dir all

Symmetrix ID: 000196700571 (Local)
S Y M M E T R I X
D I R E C T O R S
Ident Type
Engine
Cores
Ports
Status
----- -------- ------------------IM-1A IM
1
4
0
Online
IM-2A IM
1
4
0
Online
ED-1B EDS
1
9
0
Online
ED-2B EDS
1
9
0
Online
DF-1C DISK
1
10
4
Online
DF-2C DISK
1
10
4
Online
FA-1D FibreChannel
1
9
5
Online
FA-2D FibreChannel
1
9
5
Online
63
System Rack Configuration

System Bays contain one or two
engines, supporting system
components, and up to six DAEs
System Bays may be dispersed
Up to 25 meters from Engine 1
Standard rack layout

Consistency improves supportability
Optimum power and cooling
Single and dual engine options

Supports onsite racking using 3rd party
racks
64
Single Engine System Bay Rack

System
Bay 1
SPS for Engine
InfiniBand Switch
Engine
Zone A & B System PDU
Daisy Chain DAE
KVM / Ethernet Switch
Daisy Chain DAE
Direct DAE
Daisy Chain DAE

SPS for IB Switch
65
Single Engine System Bay Rack

System
Bay 1
System
Bay 2- 8
SPS for Engine
InfiniBand Switch
No IB Switch
Engine
Daisy Chain DAE
Daisy Chain DAE
Work tray replaces

KVM / Ethernet
Switch
Direct DAE
Daisy Chain DAE

SPS for IB Switch
No SPS for
IB Switch
66
Two Engine System Bay Rack

System
Bay 1
SPS for Engine 1
InfiniBand Switch
Engine 1
Engine 2
SPS for Engine 2
Engine 1 Direct DAE
Engine 2 Direct DAE

SPS for IB Switch
67
Two Engine System Bay Rack

System
Bay 1
System
Bay 2- 4
SPS for Engine 1
InfiniBand Switch
No IB Switch
Engine 1
Engine 2
SPS for Engine 2
Work tray replaces

KVM / Ethernet
Switch
Engine 1 Direct DAE
Engine 2 Direct DAE

SPS for IB Switch
No SPS for
IB Switch
68
VMAX 100K
One or Two Engine System Bay
System
Bay 1
System
Bay 2
Engine
1
Engine
2
System
Bay 1
69
VMAX 200K
One or Two Engine System Bay
System
Bay 1
System
Bay 2
System
Bay 3
Engine
1
Engine
2
Engine
3
System
Bay 4
System
Bay 1
System
Bay 2
Engine
4
70
VMAX 400K -
Single Engine System Bay
System
Bay 1
System
Bay 2
System
Bay 3
System
Bay 4
System
Bay 5
System
Bay 6
System
Bay 7
System
Bay 8
Engine
1
Engine
2
Engine
3
Engine
4
Engine
5
Engine
6
Engine
7
Engine
8
71
VMAX 400K - Two Engine System Bay

System
Bay 1
System
Bay 2
System
Bay 3
System
Bay 4
72
Dispersion Single Engine System

Engine
3
Engine
4
Engine
2
Engine
5
Engine 1
Engine
6
Engine
7
Engine
8
Up to 25 Meters
from Sys Bay 1
73
Dispersion Two Engine System
74
Mixing DAE types within a System Bay

Different DAE types (120
drive and 60 drive) may be
added to the same engine
DAE 120/DAE60
DAE 120/DAE60
Can be mixed in increments

of 1 DAE
Direct connect
1st Level Daisy Chaining
2nd Level Daisy Chaining
DAE60
Start with DAE120

DAE 120/DAE60
DAE 120/DAE60r
75
Third Party Racking

Optionally, customers can use
their own racks to house a
VMAX3 system
Maximum flexibility
Datacenter standards
Standard NEMA 19 inch rack

Must meet EMC standards for
cable access and cooling
Reference:
VMAX3 Family with HYPERMAX
OS 5977 Third Party Racking
Guide
76
System Power Options

3-phase delta
Primary use case
2 drops/ bay
3-phase wye
Only if required
2 drops/bay
Single-phase
Only if required
Up to 6 drops/bay
77
Li-Ion Standby Power Supply (SPS)

2.2KW provides required
vault time
2 X 5 minutes
Li-Ion battery instead of

lead-acid
Battery is FRU
SPS Tray
10-lb battery
Removed from front of the
system
Lithium Battery Pack
78
Standby Power Supply location

Standby Power Supply
designed to keep the system
running long enough to
perform a vault operation in
the event of a power failure
Capacity to handle two 5

minute vault cycles
Protects engine and
InfiniBand switch
Pair of SPS for each Engine
SPS for IB switch only present
in first system bay
79
Power Distribution
Provides interface to customer utility power
Provides central On/Off switch for cabinet

24 outlets
Breaker protected in groups of 4
Breakers accessible thru rear door
80
Reference: https://support.emc.com
81
Summary Symmetrix VMAX Hardware

VMAX 100K, 200K, and 400K systems are the latest
members of the VMAX family
Based on latest technology including INTEL multi core
processors, PCIe Gen3 internal interconnection and high
capacity DIMM memory
InfiniBand based Virtual Matrix
Flexible configurations
CPU cores mapped to emulation instances statically and can
be changed in the IMPL.bin file
IO Module Ports are mapped to Emulation code in the
IMPL.bin file
One and two engines per system bay and the ability
to disperse system bays
82
EMC VMAX Family System Viewer

Internal tool that provides the user
with visual representation of
hardware layout
Wizard dialog builds specific
configurations based on user
defined requirements
Usable capacity
Drive type and data protection
Single or dual engine system bay
Dispersion
Not a replacement for the CX/DX

configuration tools
https://download.emc.com/downloa
ds/DL43617_SYMMETRIX-SYSTEMVIEWER.air
83
84
85
86
87
88
89
90
91
92

VMAX3 Hardware Overview: Models, Components, Layout

Încărcat de

Informații document

Descriere originală:

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

VMAX3 Hardware Overview: Models, Components, Layout

Încărcat de

Drepturi de autor:

Formate disponibile

SYMMETRIX VMAX3

EMC CONFIDENTIALINTERNAL USE ONLY

Symmetrix Hardware Objectives

Differentiate the 100K, 200K, & 400K VMAX3 models

Describe the physical placement of components in

EMC CONFIDENTIALINTERNAL USE ONLY

Symmetrix VMAX3 Family

Virtual Provisioning preconfigured from factory

EMC CONFIDENTIALINTERNAL USE ONLY

Symmetrix VMAX3 Family

Internal Nick Name

Max. 2.5 Drives

Max. 3.5 Drives

Max Front End

EMC CONFIDENTIALINTERNAL USE ONLY

Up to 1440 2.5 drives, up to 720 3.5 drives

InfiniBand 56Gb/sec Virtual Matrix Fabric for

EMC CONFIDENTIALINTERNAL USE ONLY

Up to 2880 2.5 drives, up to 1440 3.5 drives

EMC CONFIDENTIALINTERNAL USE ONLY

Up to 5760 2.5 drives, up to 2880 3.5 drives

EMC CONFIDENTIALINTERNAL USE ONLY

VMAX 100K, 200K, 400K All Flash Array

Available in all models

EMC CONFIDENTIALINTERNAL USE ONLY

Common Set of Configuration Rules

DAEs may be added in single increments

Models are differentiated by type and quantity

System contains 1 8 engines depending on model

Each engine includes two

EMC CONFIDENTIALINTERNAL USE ONLY

(11) IO modules slots access from the back

EMC CONFIDENTIALINTERNAL USE ONLY

Director Board Details

PCH Platform Control Hub

EMC CONFIDENTIALINTERNAL USE ONLY

Memory and CPU

2 CPU sockets per director

2.1GHz, 24 IVB core

Hyper threading is enabled

EMC CONFIDENTIALINTERNAL USE ONLY

16GB, 32GB, 64 GB DIMMs

All slots must be populated

DXCX configuration tool

Management Module Control Station

MMCS are installed in both

Secondary (MMCS2) installed in director slot 2

Secondary has own unique IP address and user

Files and directories are synchronized between

EMC CONFIDENTIALINTERNAL USE ONLY

When secondary is elevated, it has limited

SymmWin Management Application That

EMC CONFIDENTIALINTERNAL USE ONLY

11 Slots for IO Modules Per Director

Two backend IO modules per director

Two or four Flash IO module

System Interface Board

EMC CONFIDENTIALINTERNAL USE ONLY

Engine Physical Layout

EMC CONFIDENTIALINTERNAL USE ONLY

Two or four Flash SliC (Whirlwind) for Vault and MDP

Frontend IO modules always installed in pairs across directors