Sie sind auf Seite 1von 45

Copyright © 2007 EMC Corporation. Do not Copy - All Rights Reserved.

Symmetrix Configuration and Device


Masking

© 2007 EMC Corporation. All rights reserved.

Welcome to Symmetrix Configuration and Device Masking training.


The AUDIO portion of this course is supplemental to the material and is not a replacement for the
student notes accompanying this course.
EMC recommends downloading the Student Resource Guide from the Supporting Materials tab, and
reading the notes in their entirety.

Copyright © 2007 EMC Corporation. All rights reserved.


These materials may not be copied without EMC's written consent.
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.

EMC, _____ , and _____ are registered trademarks, and _____ , and _____ are trademarks of EMC Corporation.

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

Symmetrix Configuration and Device Masking - 1


Copyright © 2007 EMC Corporation. Do not Copy - All Rights Reserved.

Course Objectives
Upon completion of this course, you will be able to:
y Describe the use of Configuration Change software to:
– Create and map Symmetrix devices
– Modify Symmetrix attributes

y Describe the use of device masking software to allow


host access to Symmetrix devices

© 2007 EMC Corporation. All rights reserved. Symmetrix Configuration and Device Masking - 2

The objectives for this course are shown here. Please take a moment to read them.

Symmetrix Configuration and Device Masking - 2


Copyright © 2007 EMC Corporation. Do not Copy - All Rights Reserved.

Symmetrix Configuration Change Component


Upon completion of this module, you will be able to
y Describe the functions of the Configuration Change
software
y Describe the process to:
– Create and map Symmetrix devices
– Modify Symmetrix attributes

© 2007 EMC Corporation. All rights reserved. Symmetrix Configuration and Device Masking - 3

The objectives for this module are shown here. Please take a moment to read them.

Symmetrix Configuration and Device Masking - 3


Copyright © 2007 EMC Corporation. Do not Copy - All Rights Reserved.

Configuration Manager Overview


y Execute using the symconfigure SYMCLI command
y Accessible via the Symmetrix Management Console GUI
y Performs configuration changes pertaining to:
– Creation and attribute modification of all Symmetrix devices including
save devices, spare devices and metadevices
– SRDF group and device level characteristics
– Mapping of devices to front end ports
– Setting Symmetrix metrics
– Setting front end port attributes

© 2007 EMC Corporation. All rights reserved. Symmetrix Configuration and Device Masking - 4

The SYMCLI Configuration Change Component, frequently referred to as the Config Manager, is
invoked using the symconfigure command. It can also be invoked through the Symmetrix Management
Console GUI.
Config Manager is capable of configuration operations in the Symmetrix. A few SRDF related
configuration activities cannot be performed by Config Manager. These include:
y Dynamic RDF group and pair creation and deletion which can be done with the symrdf
command.
y Modification of dynamic RDF group parameters such as Prevent Automatic RDF Link
Recovery which can be set using the symrdf command.
y Modify the RAs online upon Power On parameter which has to be set through the
Symmetrix Service Processor using Symwin.

Symmetrix Configuration and Device Masking - 4


Copyright © 2007 EMC Corporation. Do not Copy - All Rights Reserved.

Architecture

Host Symmetrix Symmetrix


SYMCLI SMC
SYMAPI
FA
SIL

RA RA

Ethernet Ethernet

SYMMWIN SYMMWIN
Scripts Scripts

SYMMWIN SYMMWIN

Service Processor Service Processor

© 2007 EMC Corporation. All rights reserved. Symmetrix Configuration and Device Masking - 5

The Config Manager architecture allows it to run Symmwin scripts on the Symmetrix service
processor. Configuration change requests are generated by the symconfigure SYMCLI command
or a SYMAPI library call that is generated by a user making a request through the Symmetrix
Management Console (SMC) GUI.
These requests are converted by SYMAPI on the host to Symmetrix syscalls and transmitted to the
Symmetrix through the channel interconnect. The Symmetrix front end routes the requests to the
service processor, which invokes Symmwin procedures to perform the requested changes to the
Symmetrix.
Since these scripts are the same as what a Customer Services Engineer would employ to configure the
Symmetrix, Config Manager is able to do almost everything that is possible through Symmwin scripts.

Symmetrix Configuration and Device Masking - 5


Copyright © 2007 EMC Corporation. Do not Copy - All Rights Reserved.

Configuration Operations Classes

y Device Creation y Manage spare disks


y Device Conversion y Map devices to ports
y Set device Attributes
y Change Protection by
adding/removing mirrors y Set device emulation

y Device Deletion y Set Front end port


attributes
y RDF Configuration y Set RDF group
parameters
y Manage Metadevices
y Set Symmetrix metrics
y Manage Save Pools

© 2007 EMC Corporation. All rights reserved. Symmetrix Configuration and Device Masking - 6

The list shown describes the classes of configuration operations that the Config Manager can perform.
For more details on the classes, please refer to Chapter 1 of the Symmetrix Array Controls CLI Guide.

Symmetrix Configuration and Device Masking - 6


Copyright © 2007 EMC Corporation. Do not Copy - All Rights Reserved.

Submission of Configuration Change Requests


y Create command file
– Multiple commands separated with semi-colon

y Commands can belong to separate classes except


– Dynamic RDF changes
– Save pool changes
– Expanding striped metavolumes with protection

y Submit file as a parameter to symconfigure

© 2007 EMC Corporation. All rights reserved. Symmetrix Configuration and Device Masking - 7

Configuration change requests are placed in a command file. The syntax for these commands is
described in Chapter 1 of the Symmetrix Array Control CLI Product Guide.
Prior to Enginuity 5669, only one class of commands could be submitted for execution at one time.
Though that restriction does not exist today, changes to dynamic RDF, Save pools and protected
expansion of striped metavolumes can still not be mixed with other class operations in the same
command file.

Symmetrix Configuration and Device Masking - 7


Copyright © 2007 EMC Corporation. Do not Copy - All Rights Reserved.

Stages of a Configuration Change


y Preview
– Verifies syntax of the command file

y Prepare
– Runs the Preview step
– Verifies appropriateness of the requested changes against the
current state of the Symmetrix

y Commit
– Performs the Preview and Prepare steps
– Performs the requested changes

Symmetrix lock #15 during configuration permits host I/O to


flow, but blocks overlapping change requests
© 2007 EMC Corporation. All rights reserved. Symmetrix Configuration and Device Masking - 8

The Configuration Manager performs configuration changes in three steps.


The preview argument (stage) verifies the syntax and correctness of each individual change defined,
their correctness as a set, and then terminates the session without change execution (correct within the
realm of the host and valid as a possible Symmetrix configuration).
The prepare argument (stage) performs the preview checks and also verifies the appropriateness of the
resulting configuration definition against the current state of the Symmetrix arrays; the argument then
terminates the session without change execution (correct within the realm of both the host and the
Symmetrix array). The prepare argument has no function for SAVEDEV pool sessions.
The commit argument (last stage) completes all stages and activates the changes in the specified
Symmetrix array.
If an error is found during the preview and prepare steps, the config change session is aborted at the
point where the error was found. Errors during commit are rare, since the prepare step is intended to
ensure that the requested changes are valid. If errors do occur during the commit step, it is best to enlist
the help of someone with access to the service processor (such as an EMC customer services engineer)
to diagnose the problem and rerun the failed Symmwin script after resolving the problem.

Symmetrix Configuration and Device Masking - 8


Copyright © 2007 EMC Corporation. Do not Copy - All Rights Reserved.

Steps to Create a New Device


y Discover the amount of free space available
– symconfigure list –v
– symdisk list
– symdev list –da all -space

y If device is to equal other devices ascertain their size


– symdev list –cylinders

y Verify that Symmetrix is available for config changes


– symconfigure list –verify

y Create a command file and use it as an argument to


symconfigure
– symconfigure –file <command file> -sid <SID>
commit
© 2007 EMC Corporation. All rights reserved. Symmetrix Configuration and Device Masking - 9

The preparatory steps before device creation involves the use of various SYMCLI commands to
discover the amount of free space on the available disks, the size of the device(s) that must be created
and the availability of the Symmetrix.
A command file containing the configuration change commands is created using a text editor. Then the
symconfigure command is used to make the configuration change requests.
The scope of this course does not warrant a detailed discussion of these commands. Please refer to
Chapter 7 of the Solutions Enabler Array Controls guide V 6.4 for detailed Config Manager examples.

Symmetrix Configuration and Device Masking - 9


Copyright © 2007 EMC Corporation. Do not Copy - All Rights Reserved.

Example of a Command File


create dev count=4, config=2-Way-Mir, size=2300, emulation=FBA;

Physical Disks Residing


in the Symmetrix Unit

Logical Volumes
Four
Visible to the Host Hyper
DEV001 M2 Volumes
DEV001 M1

Standard 2-Way-Mir
DEV001

DEV002 M2
Standard DEV002 M1
DEV002

2-Way-Mir

© 2007 EMC Corporation. All rights reserved. Symmetrix Configuration and Device Masking - 10

The command file shown requests the creation of four 2-Way-Mirror FBA devices of size 2300
cylinders (1 GB) each. This command file is then passed as a parameter to the symconfigure command
as shown on the previous page.

Symmetrix Configuration and Device Masking - 10


Copyright © 2007 EMC Corporation. Do not Copy - All Rights Reserved.

Meta Device
y Several symmetrix volumes presented to the front-end as
one device
y Two types
– Concatenated
– Striped

© 2007 EMC Corporation. All rights reserved. Symmetrix Configuration and Device Masking - 11

A meta device is a Symmetrix mechanism for defining a device larger than the current maximum
hyper-volume size. You can concatenate existing devices to form a larger meta device that is
presented to the host as a single addressable device.
There are two kinds of meta devices - concatenated and striped.
y On a concatenated meta device, addressing of data continues to the end of a device before any data
on the next device is referenced.
y On a striped meta device, data on meta members is addressed in user-defined stripes or chunks
instead of filling an entire volume first before addressing the next volume.

Symmetrix Configuration and Device Masking - 11


Copyright © 2007 EMC Corporation. Do not Copy - All Rights Reserved.

Meta Device Configurations

Meta Member Member Meta


Head Device Device Tail

Concatenated
Meta Device

Unrelated
Hyper
Volumes

Concatenated Meta Device on Four Physical Disk Spindles


Striped
Meta Device

Unprotected Striped Meta Device on Four Physical Disk Spindles

© 2007 EMC Corporation. All rights reserved. Symmetrix Configuration and Device Masking - 12

The meta head is the Symmetrix device recognized by the host and used for performing I/O.

Symmetrix Configuration and Device Masking - 12


Copyright © 2007 EMC Corporation. Do not Copy - All Rights Reserved.

Meta Device Creation


y The form meta and add dev command file entries create meta devices. Specify the device to
be used as the meta head, the devices to be used as the meta members, and the meta type
configuration:
form meta from dev 030, config=concatenated; add dev 031:033 to meta 030;
y Partial list of device creation steps for meta devices

Desired Device Configuration Session 1 - create Session 2 - form Session 3 - convert


Meta 2-Way-BCV-Mir 2-Way-BCV-Mir → Meta 2-Way-BCV-Mir
Meta 2-Way-Mir 2-Way-Mir → Meta 2-Way-Mir
Meta 2-Way-Mir-RDF 2-Way-Mir → Meta 2-Way-Mir → Meta 2-Way-Mir-RDF
Meta 3-Way-Mir 3-Way-Mir → Meta 3-Way-Mir
Meta 4-Way-Mir 4-Way-Mir → Meta 4-Way-Mir
Meta BCV BCV → Meta BCV
Meta Parity RAID RAID-S → Meta Parity RAID
Meta RAID 5 RAID 5 → Meta RAID 5
Meta RAID 6 RAID 6 → Meta RAID 6

Meta RAID 5 BCV RAID 5 BCV → Meta RAID 5 BCV

Meta RAID 6 BCV RAID 6 BCV → Meta RAID 6 BCV

Meta RDF1 Unprotected → Meta Unprotected → Meta RDF1

Meta RDF1+R-5 RAID 5 → Meta RAID 5 → Meta RDF1+R-5

© 2007 EMC Corporation. All rights reserved. Symmetrix Configuration and Device Masking - 13

The creation of metadevices often requires more than one configuration change session. Some require
three sessions - create, form, and convert - as shown here. This table is excerpted from Chapter 1 of the
Solutions Enabler Array Controls CLI Product Guide V6.4.
The form meta and add dev command file entries create meta devices. Specify the device to
be used as the meta head, the devices to be used as the meta members, and the meta type configuration:
form meta from dev 030, config=concatenated;
add dev 031:033 to meta 030;

These commands create a concatenated meta device using device 030 as the meta head and devices
031, 032, and 033 as the meta members.
When forming a striped meta device, specify the stripe size in number of blocks (for example, specify
stripe_size=1920 for two cylinders).

Symmetrix Configuration and Device Masking - 13


Copyright © 2007 EMC Corporation. Do not Copy - All Rights Reserved.

Map a Device to a Port Using Config Manager


y Symmetrix Devices are made
available on an FA port by assigning
Host
them a channel address
– Referred to as mapping
HBA HBA C#
y Channel address is used by the host
to access device
– Often reflected in the c#t#d# device
naming convention FA FA
T#
– Example channel address 0003 may be
seen as c1t0d3 00 01 02 03 D#
y Devices are mapped to 2 or more 04 … FF

ports and managed by host based


Symmetrix
path management software for
– Higher Availability
– Load balancing
© 2007 EMC Corporation. All rights reserved. Symmetrix Configuration and Device Masking - 14

A Symmetrix can have over 64000 devices configured. Not all devices are accessed by every front-
end port. Instead, specific devices are “mapped” to specific ports by assigning a channel address. Host
systems discover and access Symmetrix devices using these Channel Addresses. For open systems
hosts, the Channel address is the SCSI ID. Normally, a host uses a combination of the Controller,
Target, and Logical Unit Number to address a disk device. The Controller number is the Host Bus
Adapter, the Target is the port on the Storage System, and the Logical Unit Number is the Channel
Address we assign.
The reverse of mapping a device is unmapping a device. Unmapping can become necessary prior to a
device being converted from one type to another (for example, a standard to a meta member). Before
the device is unmapped it has to be set not ready. The unmap action fails if the device is R/W enabled.

Symmetrix Configuration and Device Masking - 14


Copyright © 2007 EMC Corporation. Do not Copy - All Rights Reserved.

Steps to Map a Device to a Front-end Port


y Identify FA port to which the host receiving the new
device is connected
– symcfg list –connections

y Identify available addresses that the device could be


assigned to
– symcfg list –available –address -sid <SID> -sa <XX>
-p<YY>

y Create a command file containing the mapping request


– map dev <xx> to dir <XX>:<YY>, lun=<LUN>

y Execute the command file


– symconfigure –file <command file> -sid <SID>
commit
© 2007 EMC Corporation. All rights reserved. Symmetrix Configuration and Device Masking - 15

Before the newly created device can be used it has to be mapped to a front end port to which the receiving host is connected.
For example, the output below indicates that the host DMX800SUN1 is connected to FA 2C port 0

# symcfg list -connections


Symmetrix ID : 000190300477
Symmetrix Host
------------- -----------------------------------------------------------
Director Port Node Name IP Address HW Type OS Name OS Revision
-------- ---- ------------- --------------- -------- -------- -----------
..........................................................................
FA-2C 0 DMX800SUN1 10.127.38.35 sun4u SunOS 5.9
1 DMX800WIN1 10.127.38.33 INTEL WinNT 5.2.3790

The next command shows that LUN numbers 41 and higher are available for assignment

# symcfg list -addr -avail -sid 77 -fa 2C -p 0


Symmetrix ID: 000190300477
Director Device Name Attr Address
---------------------- ----------------------------- ---- --------------
Ident Symbolic Port Sym Physical VBUS TID LUN
------ -------- ---- ---- ----------------------- ---- --- ---
FA-2C 02C 0 0020 /dev/rdsk/c2t0d0s2 VCM 0 00 000
00A9 /dev/rdsk/c2t0d1s2 0 00 001
.............................................................................
00EA /dev/rdsk/c2t0d62s2 0 00 03E
00EC /dev/rdsk/c2t0d64s2 0 00 040
- AVAILABLE 0 00 041*

Symmetrix Configuration and Device Masking - 15


Copyright © 2007 EMC Corporation. Do not Copy - All Rights Reserved.

Setting Port Characteristics


y Port characteristics can be viewed by using symcfg
y Port characteristics make it possible to customize the
front end adapter to suit the host that connects to it
– Example: HP hosts can use octal mode addressing with Volume Set
Addressing enabled

y Port characteristics can be set in the command file


– set port 04A:0 volume_set_addressing=enable;

© 2007 EMC Corporation. All rights reserved. Symmetrix Configuration and Device Masking - 16

Excerpt from symcfg command to view port characteristics:


DMX800SUN1/usr/sengupta> symcfg list -fa 2C -p 0 –v
......................................................
Fibre Specific Flags
{
Volume_Set_Addressing(V) : Disabled
Non_Participating(NP) : Disabled
Init_Point_to_Point(PP) : Enabled
Unique_WWN(UWN) : Enabled
VCM_State(VCM) : Enabled
OpenVMS(OVMS) : Disabled
AS400(AS4) : Disabled
Auto_Negotiate(EAN) : Disabled
}

Symmetrix Configuration and Device Masking - 16


Copyright © 2007 EMC Corporation. Do not Copy - All Rights Reserved.

Symmetrix Metrics
y Metrics that can be set with Config Manager

Metric Name Metric Value


concurrent_rdf ENABLE or DISABLE
dynamic_rdf ENABLE or DISABLE
dynamic_concurrent_rdf ENABLE or DISABLE
fba_multi_access_cache ENABLE or DISABLE
hot_swap_policy ENABLE or DISABLE
max_hypers_per_disk 1 to 255
pav_alias_limit 1-15
rdfa_cache_percent 0 to 100
rdfa_host_throttle_time 0 to 65535
raid_5_support ENABLE or DISABLE (NA in 5772)
raid_s_members 3 or 7 (Prior to 5771)
raid_s_support ENABLE or DISABLE (NA in 5772)
VCMDB_restricted_access ENABLE or DISABLE

© 2007 EMC Corporation. All rights reserved. Symmetrix Configuration and Device Masking - 17

Below is a description of some of the more commonly used Symmetrix metrics.


y concurrent rdf: Enables access to the concurrent RDF feature – multiple R2 devices for a single
static R1.
y dynamic_rdf: Enables the creation of a set of devices that are RDF-capable, (can be dynamically
assigned as RDF1 or RDF2 devices).
y dynamic_concurrent_rdf: Enables access to the concurrent RDF feature (multiple R2 devices for a
single R1) for dynamic RDF devices.
y fba_multi_access_cache: Determines whether a read request can share cache slots in some
conditions.
y hot_swap_policy: Indicates whether data from a failed disk should be relocated temporarily, or
permanently moved to a hot spare device.
y max_hypers_per_disk: Specifies the maximum number of hypers that can be created on a physical
disk.
y pav_alias_limit: If PAV is enabled, specifies the maximum number of aliases that can be assigned
to a device.
y rdfa_cache_percent: The percentage of write pending cache that can be used by RDFA
y rdfa_host_throttle_time: The number of seconds to throttle host writes to SRDF/A devices when
cache is full, before dropping RDFA sessions.
To enable concurrent dynamic RDF the command in the command file would be:
set symmetrix dynamic_rdf_configuration=Enabled;

Symmetrix Configuration and Device Masking - 17


Copyright © 2007 EMC Corporation. Do not Copy - All Rights Reserved.

Symmetrix Device Masking


Upon completion of this module, you will be able to
y Describe requirements for connecting an Open Systems
host to a Symmetrix
y Make a Symmetrix device visible to a host through the
use of device masking commands in Solutions Enabler

© 2007 EMC Corporation. All rights reserved. Symmetrix Configuration and Device Masking - 18

The objectives for this module are shown here. Please take a moment to read them.

Symmetrix Configuration and Device Masking - 18


Copyright © 2007 EMC Corporation. Do not Copy - All Rights Reserved.

Connect an Open Systems Host to a Symmetrix


y HBA and device drivers must be installed and configured
y SAN connection between the Host Bus Adapter (HBA) and the
Symmetrix front-end director port
– Physical cable connection
– Logical connection (zoning)
y Director Port Characteristics
– SCSI and Fibre Channel operating parameters
– Host Operating Systems Specific
y Device Mapping
– Make a device visible via the front end adapter port by assigning it a target
ID and logical Unit Number
y Device Masking
– A single FA port can be shared by many hosts
– Controls access so specific hosts see specific devices
– Masking information maintained in Volume Logix Database

© 2007 EMC Corporation. All rights reserved. Symmetrix Configuration and Device Masking - 19

Before connecting an open systems host to the Symmetrix, the following questions should be answered:
y Which host is going to connect to which port?
y What are the operating systems and versions of the hosts?
y Number, type, and firmware levels for Host Bus Adapters (HBA)?
y Is PowerPath or other multi-pathing failover software used?
y How many, what protection, what size volumes are required?
y What are the Performance considerations (e.g. faster disks should be picked for high performance applications)?
On the host side, the host bus adapter (HBA) has to be configured with the correct drivers. Multi-pathing software if present
needs to be set up on the host.
The physical SAN connection between the host and the Symmetrix consists of cables and SAN equipment such as Fibre
channel switches. Logical zones are needed to establish a connection between the host bus adapter and the Symmetrix front
end ports.
On the Symmetrix side the front end adapter (e.g. FA) needs to be cabled to the SAN and zoned such that the host HBA and
the front end adapter (e.g. FA) are in the same zone. Zoning can be done using software from the SAN vendors.
The characteristics of the front end adapter port, to which the HBA connects, need to be appropriately set so the host
operating system can access the Symmetrix devices. Device mapping permits a device to be accessible through a front end
port. Config Manager is the appropriate tool to perform both of these tasks..
Device masking permits only a subset of devices that are mapped to a port to be visible to an HBA. This feature allows
multiple hosts to share the same Symmetrix front end port without encroaching on another host’s devices. Device masking
is performed using the masking commands in Solutions Enabler symmask and symmaskdb.

Symmetrix Configuration and Device Masking - 19


Copyright © 2007 EMC Corporation. Do not Copy - All Rights Reserved.

Fibre Channel Initialization


y Physical cable connection Host
– FA Port and the Switch
– HBA Ports and the switch HBA HBA

y When the HBA and FA ports are FLOGI FLOGI


initialized, they log in to the switch
– Identifies itself using the World Wide F-port F-port
Name (WWN)
– Fabric Login (FLOGI)
PLOGI
Switch PLOGI

F-port F-port
y The Initiator (HBA) queries the
switch for a list of Target devices FLOGI FLOGI
(FA ports)
FA FA
y The HBA logs in to the FA ports
– Port Login (PLOGI)
– Device discovery Symmetrix
© 2007 EMC Corporation. All rights reserved. Symmetrix Configuration and Device Masking - 20

The first step in connectivity is to have a connection from the Host Bus Adapter to the FA port. This
requires physical cabling and a logical path controlled by Fabric Zoning.
When the HBA and FA ports are initialized (or when the cables are connected), a Fabric Log In
(FLOGI) occurs. This is a standard part of the Fibre Channel protocol where devices identify
themselves to the fabric using their World Wide Name (WWN), a unique 128 bit hex identifier. The
switch updates the Name Server database and assigns the device a Fibre Channel Address. After the
Fabric Log In, the HBA asks the switch for the address of target devices (FA ports) and then attempts
to log into each port. This is called a Port Log In or PLOGI. After the HBA has logged into the FA
port, it performs a device discovery.

Symmetrix Configuration and Device Masking - 20


Copyright © 2007 EMC Corporation. Do not Copy - All Rights Reserved.

Display HBAs with syminq


# syminq hba -fibre

Host Name : DMX800SUN2

HBA Type : FibreChannel HBA Type : FibreChannel


HBA Name : Emulex-LP9002-1 HBA Name : Emulex-LP9002-2
Vendor : Emulex Corporation Vendor : Emulex Corporation
Model : LP9002 Model : LP9002
Serial Number : MM44136888 Serial Number : MM43015891
Firmware Version : 3.90A7 (C2D3.90A7) Firmware Version : 3.90A7 (C2D3.90A7)
Driver Version : 5.01e; HBAAPI v1.6.a, Driver Version : 5.01e; HBAAPI v1.6.a,
10-8-02 10-8-02
Node WWN : 20000000c92ab6de Node WWN : 20000000c93124ae
Number of Ports : 1 Number of Ports : 1

Port WWN : 10000000c92ab6de Port WWN : 10000000c93124ae


Port name : Port name :
/devices/pci@1f,4000/fibre-channel@2 /devices/pci@1f,2000/fibre-channel@1
Port type : NPort Port type : NPort
Port FCID : 6436627 Port FCID : 6435603
Port speed : 2gbit Port speed : 2gbit
Supported speed : 2gbit Supported speed : 2gbit
Port state : Online Port state : Online

© 2007 EMC Corporation. All rights reserved. Symmetrix Configuration and Device Masking - 21

This command (# syminq hba -fibre) provides more detail about the HBAs. The port WWN is
used for device masking purposes. The Port Online state indicates that the FLOGI process was
successful and the HBA has logged into the switch.

Symmetrix Configuration and Device Masking - 21


Copyright © 2007 EMC Corporation. Do not Copy - All Rights Reserved.

Displaying HBA Connections


# symmask list hba -v

WWN : 10000000c92ab6de WWN : 10000000c93124ae


ip Address : N/A ip Address : N/A
Type : Fibre Type : Fibre
Adapter : pci@1f,4000/fibre- Adapter : pci@1f,2000/fibre-
channel@2 channel@1

Physical Device Path : Physical Device Path :


/dev/rdsk/c2t0d0s2 /dev/rdsk/c3t0d0s2
Director Identification : FA-2C Director Identification : FA-2C
Director Port : 0 Director Port : 0

Physical Device Path : Physical Device Path :


/dev/rdsk/c2t1d0s2 /dev/rdsk/c3t1d0s2
Director Identification : FA-15C Director Identification : FA-15C
Director Port : 1 Director Port : 1

© 2007 EMC Corporation. All rights reserved. Symmetrix Configuration and Device Masking - 22

This command (# symmask list hba –v) shows that the host from which the command was
issued has two HBAs and each of them is connected (via proper zoning) to fibre ports 2C:0 and 15C:1.

Symmetrix Configuration and Device Masking - 22


Copyright © 2007 EMC Corporation. Do not Copy - All Rights Reserved.

Front-end Director Status


# symcfg -fa all list -port -sid 77
Symmetrix ID: 000190300477
S Y M M E T R I X D I R E C T O R P O R T S

Director Port Status Connection Status


Ident Type Status P0 P1 P2 P3 P0 P1 P2 P3

FA-1C FibreChannel Online ON ON N/A N/A X X - -


FA-2C FibreChannel Online ON ON N/A N/A X X - -
FA-15C FibreChannel Online ON ON N/A N/A X X - -
FA-16C FibreChannel Online ON ON N/A N/A X X - -

Legend for Connection Status:

(X) : Fibre Port is Connected to a Fibre Port (HBA, Switch or RF


Director)
(-) : Fibre Port is Not Connected.

© 2007 EMC Corporation. All rights reserved. Symmetrix Configuration and Device Masking - 23

This command (# symcfg -fa all list -port -sid 77) shows whether a port on the
Symmetrix is online and connected.

Symmetrix Configuration and Device Masking - 23


Copyright © 2007 EMC Corporation. Do not Copy - All Rights Reserved.

Front-end Director Details


# symcfg list -fa 2C -p 0 -sid 77 –v
...........................
Director Identification: FA-2C
Director Type : FibreChannel
Director Status : Online
Number of Director Ports : 2
Director Ports Status : [ON,ON,N/A,N/A]
Director Connection Status : [Yes,Yes,N/A,N/A]

Director Symbolic Number : 02C


Director Numeric Number : 34
Director Slot Number : 2

Director Port: 0

WWN Node Name : 5006048AD5F04F41


WWN Port Name : 5006048AD5F04F41

Fibre Channel Loop ID : N/A


Fibre Adapter Type : N/A
...........................
© 2007 EMC Corporation. All rights reserved. Symmetrix Configuration and Device Masking - 24

This command (# symcfg list -fa 2C -p 0 -sid 77 –v) displays detailed information about
the port. The example here is an excerpt from the output that describes the readiness of the director and
its world wide node and port names. The symcfg command can also be used to place a director on and
offline.
Example:
symcfg -SA 2C -p 0 -sid 77 online

Symmetrix Configuration and Device Masking - 24


Copyright © 2007 EMC Corporation. Do not Copy - All Rights Reserved.

Port Flags Support Different Hosts and O/S


# symcfg list -fa 2C -p 0 -sid 77 –v
...........................
SCSI Flags
{
Negotiate_Reset(N) : Disabled
Soft_Reset(S) : Disabled
Environ_Set(E) : Disabled
HP3000_Mode(B) : Disabled
Common_Serial_Number(C) : Disabled
Disable_Q_Reset_on_UA(D) : Disabled
Sunapee(SCL) : Disabled
Siemens(S) : Disabled
Sequent(SEQ) : Disabled
Avoid_Reset_Broadcast(ARB) : Disabled
Server_On_AS400(A4S) : Disabled
SCSI_3(SC3) : Disabled
SPC2_Protocol_Version(SPC2) : Disabled
SCSI_Support1(OS2007) : Disabled
}
Fibre Specific Flags
{
Volume_Set_Addressing(V) : Disabled
Non_Participating(NP) : Disabled
Init_Point_to_Point(PP) : Enabled
Unique_WWN(UWN) : Enabled
VCM_State(VCM) : Enabled
OpenVMS(OVMS) : Disabled
AS400(AS4) : Disabled
Auto_Negotiate(EAN) : Disabled
}
...........................

© 2007 EMC Corporation. All rights reserved. Symmetrix Configuration and Device Masking - 25

Displayed here is a continuation of the previous slide’s command output. SCSI and Fibre flags are
designed to support a wide variety of hosts. These flags are enabled or disabled using the Config
Manager.
Protocols used to communicate between hosts and storage systems are designed to support a wide
variety of applications and operating system requirements. SCSI is a standards-based protocol that has
been around for over twenty years and the command set and nexus is flexible enough to support many
different types of storage devices and host operating systems. Nearly every server vendor supports
SCSI; unfortunately, not every vendor implements SCSI in exactly the same way. For example, while
HP-UX and IBM AIX support the SCSI protocol, they support a different subset of the operational
parameters. Fibre Channel and IP are transport protocol used with the SCSI protocol and also have a
number of configurable protocol and link parameters.
The emulation code in the Symmetrix front-end director port is implemented in software. This allows
the director to be configured to suit a wide variety of hosts and operating systems. The settings are
called port flags.

Symmetrix Configuration and Device Masking - 25


Copyright © 2007 EMC Corporation. Do not Copy - All Rights Reserved.

Switch Perspective - Fabric Login


Root> show zoning
Default Zone Enabled: False
Zone Set: All_in_one_ZoneSet
Zone: DMX3_HP3A
Zone Member: 50:06:04:8A:CC:C8:3E:0F
Zone Member: 50:06:0B:00:00:07:79:1A
Zone: DMX3_HP3B
Zone Member: 50:06:04:8A:CC:C8:3E:00
Zone Member: 50:06:0B:00:00:07:7F:36
Zone: DMX3_IBM3A
Zone Member: 10:00:00:00:C9:25:44:B7
Zone Member: 50:06:04:8A:CC:C8:3E:20
.................................................
© 2007 EMC Corporation. All rights reserved. Symmetrix Configuration and Device Masking - 26

Connectivity status can also be verified by logging into the fibre channel switch. When an HBA or FA
port is connected to the switch, it identifies itself by its WWN and specifies operating parameters (such
as buffer credits, link speed, and class of services), and is assigned a Fibre Channel address.
The example shows HBA and FA ports logged into the switch. Please note that the example is for a
McData switch, but other vendors have commands that provide similar information.

Symmetrix Configuration and Device Masking - 26


Copyright © 2007 EMC Corporation. Do not Copy - All Rights Reserved.

Device Masking
y Device masking Host Host Host Host Host Host Host
A B C D X Y Z
allows multiple HBA HBA HBA HBA HBA HBA HBA HBA HBA HBA HBA HBA HBA HBA

hosts to effectively
share the same front-end ports FC
Switch
– FA port can “see” up to 256 HBAs

y Restrict access FA or SE FA or SE
to specific host p0 p1
VCMDB
p0 p1
and/or host clusters
y Implemented in the
Symmetrix with
Volume Logix
– Fibre Channel
Symmetrix
– iSCSI

© 2007 EMC Corporation. All rights reserved. Symmetrix Configuration and Device Masking - 27

Storage Area Networks provide a fan-out capability where it is likely that more than one host is
connected to the same Symmetrix port. The actual number of HBAs that can be configured to a single
port is operating system and configuration dependent, but fan-out ratios as high as 256:1 are currently
supported. Reference the support matrix for specific configuration limitations.
Each port may have as many as 4096 addressable volumes presented. When several hosts connect to a
single Symmetrix port, an access control conflict can occur because all hosts have the potential to
discover and use the same storage devices. However, by creating entries in the Symmetrix’s device
masking database (VCMDB), it is possible to control the volumes “seen” by a host.
Device Masking is independent from zoning, but zoning and masking are typically used together in an
environment. Zoning provides access control at the port level. It establishes a logical connection
between the host bus adapter and port on the storage system. Device masking allows a subset of
volumes mapped to a port to be visible to the host bus adapter.
With Fibre Channel, Device Masking uses the UWWN (Unique Worldwide Name) of Host Bus
Adapters and a VCM database device. In iSCSI, the iSCSI Qualified Name (IQN) is used. Regardless
of the protocol, the concepts are the same. The device-masking database (VCMDB) on each
Symmetrix unit specifies the devices that a particular WWN or IQN can access through a specific
Fibre port.

Symmetrix Configuration and Device Masking - 27


Copyright © 2007 EMC Corporation. Do not Copy - All Rights Reserved.

Volume Logix Database - VCMDB


y Database types are Symmetrix model specific and sized
to handle the maximum number of logical volumes
– Originally a separate Symmetrix Logical Volume
– Starting with the DMX-3, it is stored in the Symmetrix File System
y VCM DB is maintained using Solutions Enabler symmask
and symmaskdb commands
y Solutions Enabler accesses Management Symmetrix
the VCM database using a Host
VCMDB
File System
VCM gatekeeper device
– VCM gatekeeper is host accessible
– The SFS is not directly accessible
VCM
VCM
– VCM GK only needs to be mapped GK
GK
to the management host

© 2007 EMC Corporation. All rights reserved. Symmetrix Configuration and Device Masking - 28

The Volume Logix Database persistently maintains the device masking information. Originally, the
database was located directly on a Symmetrix Logical Volume. On DMX-3 it is maintained in the
Symmetrix File System (SFS). Rather than create the actual VCMDB device, we now create a VCM
Gatekeeper device which is used by the Solutions Enabler to access the database on the SFS, as the
SFS volumes are not host addressable. The VCM Gatekeeper is a 6-cyl device.
By default, the device masking VCMDB is accessible to all HBAs that log into the director port where
the database is configured. Thus, any host with access privileges can effectively modify the contents of
the database if it has device masking commands installed. Beginning with Enginuity Version 5670, the
VCMDB can be unmapped from any director that is not being used for masking control.

Symmetrix Configuration and Device Masking - 28


Copyright © 2007 EMC Corporation. Do not Copy - All Rights Reserved.

Connection Records Maintained in VCMDB


Host A
y Example: HBA0 HBA1
WWN WWN
– HBA0 WWN -> FA03a:0 - dev 000-010
– HBA0 WWN -> FA14a:0 - dev 000-010
– HBA1 WWN -> FA03a:0 - dev 000-010
– HBA1 WWN -> FA14a:0 - dev 000-010

y Entries in the VCMDB define FA3a:0 FA14a:0

relationship between masked 00 01 02 …


connections and devices
– FA consults VCMDB to resolve access rights VCMDB

y Same approach for both FC and iSCSI


Symmetrix

© 2007 EMC Corporation. All rights reserved. Symmetrix Configuration and Device Masking - 29

Device Masking controls host access to a set of devices by maintaining a set of entries in the VCMDB
on the array that defines the relationship between masked connections and devices. These entries are
sometimes called initiator records.
Each entry includes a host's HBA identity (WWN or iSCSI Qualified Name), its associated FA port,
and a range of devices mapped to the FA port that should be visible only to the corresponding HBA.
Once you make this VCMDB entry and activate the configuration, the Symmetrix makes visible to a
host those devices that the VCMDB indicates are available to that host's initiator through that FA port.
Volume Logix is the brand name for the software in the Symmetrix that performs the device masking
function. The capability is built into Enginuity, but its use is optional.

Symmetrix Configuration and Device Masking - 29


Copyright © 2007 EMC Corporation. Do not Copy - All Rights Reserved.

Set-up Device Masking


y There are four steps in setting up device masking on
the Symmetrix
1. Configure a VCM gatekeeper device
2. Set the VCM attribute for the device Typically performed
when the bin file is
3. Set the VCM flag for front-end director port
initially created
4. Assign the VCM gatekeeper to front-end port

y After the VCM is setup, the database is maintained


using the SE symmask and symmaskdb commands
– Add and remove masking entries
– Initialize, query, backup, and restore database
– May also be configured with EMC ControlCenter or SMC
– External configuration locks are used to coordinate updates

© 2007 EMC Corporation. All rights reserved. Symmetrix Configuration and Device Masking - 30

To set-up device masking, a database volume (VCMDB) must be created and flags must be set on the
Fibre Channel or iSCSI ports to enable use. Once the database is setup and enabled, the Solutions
Enabler symmask command can be used to configure entries granting specific hosts access to specific
volumes.
During the execution of the symmask or symmaskdb commands, the SYMCLI sets a Symmetrix
External Lock on the Symmetrix where the device masking database (VCMDB) resides. This lock
ensures that only one host can make changes to the database at any one point in time. If, during the
processing of a symmask or symmaskdb command, the host fails or a Ctrl/C is performed in the
middle of the command, the lock might not release and could lock out further needed changes or
control actions. If a device masking command is interrupted and the lock is not released, future
invocations of a device masking command displays the following error message: The operation failed
because another process has an exclusive lock on the local Symmetrix.
To further examine the presence of this lock, use the following form:
symcfg -sid SymmID list -lock -lockn ALL
The command will list Symmetrix external locks being held. For masking commands the lock number
is 14. The lock can be released with the command:
symcfg -sid SymmID -lockn 14 release

Symmetrix Configuration and Device Masking - 30


Copyright © 2007 EMC Corporation. Do not Copy - All Rights Reserved.

Discovery
Host A
y The symmask discover hba command HBA0 HBA1
WWN WWN
– Verifies VCM is enabled for port
– Identifies paths to the VCMDB
– Assigns alias names to the HBAs AWWN

C:\>symmask
C:\>symmask discover
discover hba
hba
FA3a:0 FA14a:0

Symmetrix
Symmetrix ID
ID :: 000190102254
000190102254
Device
Device Masking
Masking Status
Status :: Success VCM
Success
GK VCMDB

Identifier
Identifier Type
Type User-generated
User-generated Name
Name 00 01 02 …
----------------
---------------- -----
----- -------------------------------
-------------------------------
10000000c93da44a
10000000c93da44a Fibre
Fibre W2K3-39-106/10000000c93da44a
W2K3-39-106/10000000c93da44a
10000000c93da45c Fibre W2K3-39-106/10000000c93da45c
Symmetrix
10000000c93da45c Fibre W2K3-39-106/10000000c93da45c

© 2007 EMC Corporation. All rights reserved. Symmetrix Configuration and Device Masking - 31

The symmask discover command can be run on the management host and/or other attached hosts.
The symmask discover identifies paths to the device masking database (VCMDB) and assigns
alias names (AWWN/AISCSI) to the HBAs residing on the host where the command was executed.
When the symmask discover finds a host HBA, it reads the login history table and checks
whether an alias exists in the device masking VCMDB. If one does, this command writes it to the login
history table. If there is no alias in the device masking VCMDB record, or the login history table, it
creates an ASCII alias and writes it to the login history table.
Next, it outputs the initiator identifier (WWN/iSCSI) of the HBAs that are connected to the masked
channel and Symmetrix array.
Alias names can be used in the command line, replacing the cumbersome numeric identifiers. These
names, which are stored in the Symmetrix array’s login history table, identify the HBAs connected to
the network interface. Alias names can be shorter in length and much more recognizable than the
cryptic WWNs/iSCSIs.
ASCII alias names generated by the discover action consists of two parts: the name of the host and the
name of the HBA. For example: the AWWN for a host whose TCP/IP hostname is john4554b, on
adapter 10000000c920cf87, would be john4554b/10000000c920cf87.

Symmetrix Configuration and Device Masking - 31


Copyright © 2007 EMC Corporation. Do not Copy - All Rights Reserved.

Initialize and Format the VCMDB Database


## symmaskdb
symmaskdb list
list database
database

The
The Symmetrix
Symmetrix device
device masking
masking database
database has
has not
not been
been initialized
initialized

C:>symmaskdb
C:>symmaskdb init
init -file
-file VCMdbBackup070707
VCMdbBackup070707

Initialize
Initialize Symmetrix
Symmetrix SymMask
SymMask database
database on
on Symmetrix
Symmetrix 000190100172
000190100172 (y/[n])?
(y/[n])? yy

Symmetrix
Symmetrix SymMask
SymMask database
database on
on Symmetrix
Symmetrix 000190100172
000190100172 initialized
initialized
C:>
C:>

© 2007 EMC Corporation. All rights reserved. Symmetrix Configuration and Device Masking - 32

During the initial setup of any device masking environment, the database has to be initialized. To
check whether the VCMDB has already been initialized and already contains records, issue the
command::

symmaskdb list database


To initialize and clear the VCMDB database, you must specify a backup file name to safeguard against
clearing data in the database that should not be lost. For example, the following command creates a file
called MyInitBackup and attempts to write any current data to it prior to initializing and formatting the
VCMDB:

symmaskdb init –file MyInitBackup

Note:
The Solutions Enabler device masking function requires a license key. This is installed using the
symlmf command.

Symmetrix Configuration and Device Masking - 32


Copyright © 2007 EMC Corporation. Do not Copy - All Rights Reserved.

Add HBA Access to Symmetrix Devices - 1


C:>
C:> symmask
symmask list
list hba
hba
Identifier
Identifier Type
Type Adapter
Adapter Physical
Physical Device
Device Path
Path Dir:P
Dir:P
----------------
---------------- -----
----- ----------------
---------------- ------------------------
------------------------ -----
-----
10000000c9274156
10000000c9274156 Fibre
Fibre i@1f,4000,@2
i@1f,4000,@2 Physicaldrive0
Physicaldrive0 7A:0
7A:0
Physicaldrive1
Physicaldrive1 7A:0
7A:0
10000000c92741a1
10000000c92741a1 Fibre
Fibre i@1f,4000,@4
i@1f,4000,@4 Physicaldrive2
Physicaldrive2 8A:0
8A:0
Physicaldrive3
Physicaldrive3 8A:0
8A:0
C:>
C:> symcfg
symcfg list
list -FA
-FA 7a
7a -addr
-addr
Symmetrix
Symmetrix ID:
ID: 000190100172
000190100172 (Local)
(Local)
Director
Director Device
Device Name
Name Attr
Attr Address
Address
----------------------
---------------------- -----------------------------
----------------------------- ----
---- --------------
--------------
Ident
Ident Symbolic
Symbolic Port
Port Sym
Sym Physical
Physical VBUS
VBUS TID
TID LUN
LUN
------
------ --------
-------- ----
---- ----
---- -----------------------
----------------------- ----
---- ---
--- ---
---
FA-7A
FA-7A 07A
07A 00 0040
0040 Not
Not Visible
Visible 00 00
00 000
000
0041
0041 Not
Not Visible
Visible 00 00
00 001
001
0042
0042 Not
Not Visible
Visible 00 00
00 002
002
0043
0043 Not
Not Visible
Visible 00 00
00 003
003
0044
0044 Not
Not Visible
Visible 00 00
00 004
004

© 2007 EMC Corporation. All rights reserved. Symmetrix Configuration and Device Masking - 33

When configuring device masking, three pieces of information are needed:


The World Wide Port Number for the Host Bus Adapter(s).
The number of the front end director and port to which the HBA is connected, e.g. director 7A port 0
List of Symmetrix devices that are mapped to the port. Available devices are those that have a channel
address assigned.
The symmask list hba command displays the WWN for each HBA in the host. It also displays the
director and port of the connection to the Symmetrix and the device file for the gatekeeper device.
In the example shown the host has two HBAs: one with the WWN of 10000000c9274156, and the
other 10000000c92741a1.One HBA is connected through director 7a port0 and the other through 8a
por0.
The symcfg list –FA 7A –addresses command displays a list of devices mapped to that port starting
with Symmetrix logical volume 40.

Symmetrix Configuration and Device Masking - 33


Copyright © 2007 EMC Corporation. Do not Copy - All Rights Reserved.

Add HBA Access to Symmetrix Devices - 2

C:>
C:> symmask
symmask add
add dev
dev 40,41,42
40,41,42 -wwn
-wwn 10000000c9274156
10000000c9274156 -dir
-dir 7a
7a -p
-p 00
C:>
C:> symmask
symmask add
add dev
dev 40,41,42
40,41,42 -wwn
-wwn 10000000c92741a1
10000000c92741a1 -dir
-dir 8a
8a -p
-p 00

C:>
C:> symmask
symmask refresh
refresh

Refresh
Refresh Symmetrix
Symmetrix FA
FA directors
directors with
with contents
contents of
of SymMask
SymMask database
database
000190100172
000190100172 (y/[n])
(y/[n]) ?? yy

Symmetrix
Symmetrix FA
FA directors
directors updated
updated with
with contents
contents of
of SymMask
SymMask Database
Database
000190100172
000190100172
C:>
C:>

© 2007 EMC Corporation. All rights reserved. Symmetrix Configuration and Device Masking - 34

The symmask command shown masks devices 40 through 42 to the specified HBAs through directors
7A port 0 and 8A port 0 respectively.
The symmask refresh command updates the access control tables in the directors with the new
information after the changes are made.

Symmetrix Configuration and Device Masking - 34


Copyright © 2007 EMC Corporation. Do not Copy - All Rights Reserved.

The Case for Using for LUN offset


y More than one host sharing an FA port
y Each host is assigned a different subset of devices
through device masking
y LUN offset is used when
– Both hosts need a LUN 0 OR
– A host needs to see contiguous LUN addresses though the devices
in the Symmetrix are non-contiguous

© 2007 EMC Corporation. All rights reserved. Symmetrix Configuration and Device Masking - 35

LUN offset is an enhanced visibility feature that allows any host type to adjust host visibility by
offsetting (renumbering) LUN addresses. This is useful for host types that need to see LUN 0000 or
transform a noncontiguous LUN sequence to a contiguous sequence. In a case where two hosts access
the same Symmetrix director port and need to see a LUN 0000 - but not the same device, you can use
LUN offset. This is used so that one host sees the devices mapped from LUN “x” as starting from LUN
0000, and the other host sees devices from LUN “y” as starting from LUN 0000.
To account for noncontiguous device LUN addresses, specify a LUN base and offset as hexadecimal
values to adjust for the break in the LUN sequence. The base hex value represents the first LUN in a
renumbered LUN sequence. The offset hex value added to the base value determines where to begin
renumbering. For example, if a host needs to detect LUN 0000, but you want your host to detect only
LUNs 0005 through 0008, you can specify a LUN base address of 0000 and an offset of 0005.
The use of the Solutions Enabler symmask command is discussed later in this module, but below is an
example of a command to renumbers LUNs 0005 through 0008 as LUNs 0000 through 0003:
:
symmask set lunoffset on 0005 0000 –dir 16A -p 0
–wwn 10000000c920b484

Symmetrix Configuration and Device Masking - 35


Copyright © 2007 EMC Corporation. Do not Copy - All Rights Reserved.

Example: Hosts share a Front-end Port


y A Linux and a Windows host share same FA port
# symcfg list -connections
Symmetrix ID : 000190300477
Symmetrix Host
------------- -----------------------------------------------------------
Director Port Node Name IP Address HW Type OS Name OS Revision
-------- ---- ------------- --------------- -------- -------- -----------
......................................................................
FA-15C 0 DMX800WIN1 10.127.38.33 INTEL WinNT 5.2.3790
0 DMX800LIN1 127.0.0.1 i686 LINUX 2.6.9-34.E
1 DMX800SUN1 10.127.38.35 sun4u SunOS 5.9
FA-16C 0 DMX8HP1 10.127.38.39 9000/800 HPUX B.11.23
......................................................................

© 2007 EMC Corporation. All rights reserved. Symmetrix Configuration and Device Masking - 36

The output of the symcfg list –connections –sid 77 shows that both a Linux host and a
Windows host are connected to director 15C port 0 on Symmetrix 77.

Symmetrix Configuration and Device Masking - 36


Copyright © 2007 EMC Corporation. Do not Copy - All Rights Reserved.

Scenario for Using LUN Offset


y 10 data devices are mapped to director 15C port 0
# symcfg list -addr -sid 77 -dir 15c -p 0
Symmetrix ID: 000190300477
Director Device Name Attr Address
---------------------- ----------------------------- ---- --------------
Ident Symbolic Port Sym Physical VBUS TID LUN
------ -------- ---- ---- ----------------------- ---- --- ---
FA-15C 15C 0 00ED Not Visible 0 00 000
00EE Not Visible 0 00 001
00EF Not Visible 0 00 002
00F0 Not Visible 0 00 003
00F1 Not Visible 0 00 004
00F2 Not Visible 0 00 005
00F3 Not Visible 0 00 006
00F4 Not Visible 0 00 007
00F5 Not Visible 0 00 008
00F6 Not Visible 0 00 009
00F7 Not Visible 0 00 00A
..............................................................................

© 2007 EMC Corporation. All rights reserved. Symmetrix Configuration and Device Masking - 37

The output of the command symcfg list –addresses –sid 77 –dir 15C –p 0 shows
that devices ED through F7 are mapped to director 15C port 0 as LUNs 0 through A.

Symmetrix Configuration and Device Masking - 37


Copyright © 2007 EMC Corporation. Do not Copy - All Rights Reserved.

Setting Base and Offset


y If Linux host needed a LUN 0 a LUN offset could be set:
– symmask –sid 77 set lunoffset on 7 0 –awwn <awwn
of Linux HBA> -dir 15C –p 0

y After setting the offset, devices F4 through F7 appear as


LUNs 0 through 4 to the Linux host

Windows Linux host Base Offset


host LUNs LUNs
000 – 006
Devs ED:F3
007 – 00A 000 7
Devs F4:F7

© 2007 EMC Corporation. All rights reserved. Symmetrix Configuration and Device Masking - 38

As shown in the table, devices 0ED through 0F3 could be made visible to the Windows host as LUNs 0
through 6. This requires no LUN offset because these devices are in fact mapped to the Symmetrix
front end port as LUNs 0 through 6.
By setting the LUN offset for the Linux host to 7, devices F4 through F7 are visible to the Linux host
as LUNs 0 through 4.

Symmetrix Configuration and Device Masking - 38


Copyright © 2007 EMC Corporation. Do not Copy - All Rights Reserved.

Setting Skip Adjustment


y If Windows host needs
contiguous LUNs while
addressing devices ED : EF Windows Linux Base Offset
and F4:F5 LUNs LUNs
– symmask –sid 77 set 000 – 002
lunoffset on 3 4 –awwn Devs ED:EF
<awwn of W2K HBA> -dir
007 – 008 003 4
15C –p 0
Devs F4:F5
y Linux host needs LUN 0 while 003 – 006 000 3
addressing devices 03 : 06 Devs F0:F3
– symmask –sid 77 set
lunoffset on 0 3 –awwn
<awwn of Linux HBA> -dir
15C –p 0
© 2007 EMC Corporation. All rights reserved. Symmetrix Configuration and Device Masking - 39

Here the Windows host has visibility to devices ED through EF as LUNs 0 through 2, without the use
of LUN offset. By assigning a base of 3 and an offset value of 4, devices F4 and F5 appear to be LUNs
3 and 4 to the Windows host.
In the case of the Linux host, the base of 0 and offset of 3 allows the host to view devices F0 through
F3 to appear as LUNs 0 through 4.
It is not possible to have more than one skip hole covered by LUN offsets.

Symmetrix Configuration and Device Masking - 39


Copyright © 2007 EMC Corporation. Do not Copy - All Rights Reserved.

Dynamic Addressing with 5772 and SE 6.4


y When devices are mapped to front-
end ports, a channel address is Host A Host B Host C
assigned
HBA HBA HBA HBA HBA HBA
y The LUN address can be specified in
the connection record overriding the
mapped address
y Allows each host sharing a port to
used the same addresses to access FA FA

different devices
00 01 02 03
y Example:
04 … FF
symmask add devs 15,18,20
-lun 0 -wwn 20000000c920b484 Symmetrix
-dir 14C -p 1

© 2007 EMC Corporation. All rights reserved. Symmetrix Configuration and Device Masking - 40

Dynamic LUN addressing is more convenient than using LUN offsets. If dynamic LUN addressing is
used, using LUN offsets is no longer permitted. However, it is only supported on Enginuity 5772 and
Solutions Enabler 6.4
When adding devices you can specify the starting LUN address for each device using the -lun option.
Or have SYMAPI assign the LUN address using the -dynamic_lun option.
-lun = Specifies starting LUN addresses. You can specify a single starting LUN or multiple LUNs to
match the given ranges. For example:
symmask add devs 15,18 -lun 0 -wwn 20000000c920b484 -dir 4C -p 1

-dynamic_lun = Specifies the use of dynamic LUN addressing. The application assigns the
addresses based on what is already in use for the host HBA.-
symmask add devs 2C,2E,30 -dynamic_lun -wwn 20000000c920b484
-dir 2a -p 1

Symmetrix Configuration and Device Masking - 40


Copyright © 2007 EMC Corporation. Do not Copy - All Rights Reserved.

Setting HBA Port Flags


y Supported in SE 6.4 and later (supersedes
heterogeneous host configuration)
y Host flags enabled or disabled on per initiator basis
Common_Serial_Number [C] AS400 [AS4]
Disable_Q_Reset_on_UA [D] OpenVMS [OVMS]
Environ_Set [E] SCSI_3 [SC3]
Siemens [S] Sunapee [SCL]
Volume_Set_Addressing [V] Sequent [SEQ]
Avoid_Reset_Broadcast [ARB] SPC2_Protocol_Version [SPC2]
SCSI_Support1 [OS2007]

y Example
– symmask –sid <sid> set hba_flags on C, SC3 –enable
–wwn <wwn of HBA> -dir <dir> –p <port #>

© 2007 EMC Corporation. All rights reserved. Symmetrix Configuration and Device Masking - 41

This feature allows specific host flags to be enabled or disabled on a director port and permits
heterogeneous hosts to share a single director FA port even though they may require different port
settings for their distinctive interface protocol.

Symmetrix Configuration and Device Masking - 41


Copyright © 2007 EMC Corporation. Do not Copy - All Rights Reserved.

Display the Contents of the VCMDB


C:>
C:> cd
cd \Program
\Program Files\EMC\SYMCLI\bin
Files\EMC\SYMCLI\bin
C:>
C:> symmaskdb
symmaskdb list
list database
database

Symmetrix
Symmetrix ID
ID :: 000190100172
000190100172

Database
Database Type
Type :: Type6
Type6
Last
Last updated
updated at
at :: 01:40:29
01:40:29 PM
PM on
on Thu
Thu Sep
Sep 01,2007
01,2007

Director
Director Identification
Identification :: FA-7A
FA-7A
Director
Director Port
Port :: 00

User-generated
User-generated
Identifier
Identifier Type
Type Node
Node Name
Name Port
Port Name
Name Devices
Devices
----------------
---------------- -----
----- ---------------------------------
--------------------------------- ---------
---------
10000000c92741a1
10000000c92741a1 Fibre
Fibre 10000000c92741a1
10000000c92741a1 10000000c92741a1
10000000c92741a1 0040:0042
0040:0042

© 2007 EMC Corporation. All rights reserved. Symmetrix Configuration and Device Masking - 42

You can display the entire contents of the VCMDB or use options to restrict the display to your area of
interest. In the example above we are displaying access control records for the entries we previously
added. Note: the entire output is not displayed.
You can restrict the output to a specific HBA. For example:

symmaskdb -list devs -wwn 10000000c9238053


You can also view which HBAs have been assigned to specific devices. For example:

symmaskdb list assignment -dev 0040:0043

Symmetrix Configuration and Device Masking - 42


Copyright © 2007 EMC Corporation. Do not Copy - All Rights Reserved.

VCM Database Maintenance


y Access control is tied to the WWN of an HBA
y If a HBA fails and must be replaced, the VCMDB must be
updated to reflect the change
– Example:
symmask –wwn 20000000c920b484
replace 20000000c920b393
– Updates all masking records

y Backup the VCM database


– Periodically and before making changes
– Example:
symmaskdb –sid 123 –file VCM_backup073007 backup

© 2007 EMC Corporation. All rights reserved. Symmetrix Configuration and Device Masking - 43

Because device masking is tied to the WWN of an HBA, if it must be replaced, the VCMDB must be
updated to reflect the new WWN.

Symmetrix Configuration and Device Masking - 43


Copyright © 2007 EMC Corporation. Do not Copy - All Rights Reserved.

Module Summary
Key points covered in this module
y Requirements for connecting an Open Systems host to a
Symmetrix
y Making a Symmetrix device visible to a host through the
use of device masking commands in Solutions Enabler

© 2007 EMC Corporation. All rights reserved. Symmetrix Configuration and Device Masking - 44

These are the key points covered in this module. Please take a moment to review them.

Symmetrix Configuration and Device Masking - 44


Copyright © 2007 EMC Corporation. Do not Copy - All Rights Reserved.

Course Summary
Key points covered in this course:
y Use of Configuration Change software to
– create and map Symmetrix devices
– modify Symmetrix attributes

y Use of device masking software to allow host access to


Symmetrix devices

© 2007 EMC Corporation. All rights reserved. Symmetrix Configuration and Device Masking - 45

These are the key points covered in this training. Please take a moment to review them.
This concludes the training. Please proceed to the Course Completion slide to take the assessment.

Symmetrix Configuration and Device Masking - 45