EMC – Notes for day to day operation

sanspire.com/emc-notes-for-day-to-day-operation/

By sanaswati

DISCLAIMER:Information mentioned below as been compiled from various sources such as first hand experience by myself and
my colleagues, from webpages searched via google etc. I do not take credit for the tips mentioned below.

If a linux host using QLogic card is seeing 18 paths per disk instead of 2, chances are you might need to Enable
SPC2 version for that host’s wwn on a particular dir/port
# symmask -sid 1234 -wwn 1000000000000000 set hba_flags on SPC2 -enable -dir 08C -p 1
# symmaskdb -sid 1234 list database -v -dir 08C -p 1
Originator Port wwn : 1000000000000000
Type : Fibre
User-generated Name : hostA/qla1
Visibility : No
FCID Lockdown : No
Lun Offset : No
Heterogeneous Host : No
Port Flag Overrides : Yes
Enabled : SPC2_Protocol_Version(SPC2)
Disabled : N/A
Dynamic Addressing : No
Authentication State : N/AG
Devices : 1003 1007 100B

How do you import BCV devices in Veritas?

Steps to import the clone disk (including EMC BCVs) using VxVM 5.0 :
1) Before we split the BCV device from testdg (as in example below), “vxdisk list” shows the clone disk in an error udid_mismatch status
DEVICE TYPE DISK GROUP STATUS
EMC0_1 auto:cdsdisk EMC0_1 testdg online
EMC0_2 auto:cdsdisk - - error udid_mismatch

2) Split the BCV device

# symmir -g testdg split DEV001

3) After we split the BCV device DEV001 from testdg, we need to issue “vxdctl enable” or “vxdisk scandisks” to update the configuration in
order to seee clone disk is in “online udid_mismatch” state issuing “vxdctl enable” ( or “vxdisk scandisks”).
DEVICE TYPE DISK GROUP STATUS
EMC0_1 auto:cdsdisk EMC0_1 testdg online
EMC0_2 auto:cdsdisk - - online udid_mismatch

4) Use the following command to import the clone disk

# vxdg -n newdg -o useclonedev=on -o updateid import testdg

5) Issue “vxdisk list” to see the clone disk is imported

DEVICE TYPE DISK GROUP STATUS
EMC0_1 auto:cdsdisk EMC0_1 testdg online
EMC0_2 auto:cdsdisk EMC0_1 newdg online clone_disk

How to interpret inq/syminq output?

When running inq or syminq, you’ll see a column titled Ser Num. This column has quite a bit of information hiding in it.
Device Product Device
---------------- ------------------------- --------------------------------
Name Type Vendor ID Rev Ser Num Cap(KB)
---------------- ----- ------- --------- ------- --------- --------
/dev/dsk/c1t0d0 EMC SYMMETRIX 5265 73009150 459840
/dev/dsk/c1t4d0 BCV EMC SYMMETRIX 5265 73010150 459840
/dev/dsk/c1t5d0 GK EMC SYMMETRIX 5265 73019150 2880
/dev/dsk/c2t6d0 GK EMC SYMMETRIX 5265 7301A281 2880

Using the first and last serial numbers as examples, the serial number is broken out as follows:

73 Last two digits of the Symmetrix serial number

009 Symmetrix device number
15 Symmetrix director number. If greater than 16, using the A processor
0 Port number on the director

73 Last two digits of the Symmetrix serial number

01A Symmetrix device number
28 Symmetrix director number. If less than 16, using the B proccessor on board
0 Port number on the director

1/9
So, the first example, device 009 is mapped to director 15, processor A, port 0 while the second example has device 01A mapped to
director 12, processor B, port 0.

How are hypers laid out across underlying hard drives> (Courtsey – James Spurin)
The recommendation internally with the V-Max is for 8 hyper splits across the disk, in testing this configuration has been proven to
provide the best pormance as each lun has dedicated access to one of the disks internal queues, in essence.

Disk1 would service part of 0001, 0002, 0003, 0004, 0005, 0006, 0007, 0008
Disk2 would service part of 0001, 0002, 0003, 0004, 0005, 0006, 0007, 0008
Disk3 would service part of 0001, 0002, 0003, 0004, 0005, 0006, 0007, 0008
Disk4 would service part of 0001, 0002, 0003, 0004, 0005, 0006, 0007, 0008
Disk5 would service part of 0001, 0002, 0003, 0004, 0005, 0006, 0007, 0008
Disk6 would service part of 0001, 0002, 0003, 0004, 0005, 0006, 0007, 0008
Disk7 would service part of 0001, 0002, 0003, 0004, 0005, 0006, 0007, 0008
Disk8 would service part of 0001, 0002, 0003, 0004, 0005, 0006, 0007, 0008...

Therefore when device 0006 is accessed it is served from 8 spindles…

You can work out the size necessary for this by dividing the size of the disk by 8, i.e. a 450GB disk would be 56.25GB … in our case the
magic number 53872 cylinders for accuracy.

Another good point to know is that also confirmed is that there is no degradation in performance when you configure these through
symconfigure instead symwin as per a bin file configuration … it.s just more difficult to get your initial figures correct with symconfigure
and you don.t get the pretty phical view and the number optimization.

With regards to the ACLX setting on the directors … by default the ACLX lun is presented to all directors and subsequently any host will
always see t lun which can be annoying and cause confusion … you can resolve this by presenting gatekeepers to the management host and
then unpresenting the ACLXn from the directors.

How to use a single Unix server (client) to run commands on various remote management servers (symapi
servers) managing different arrays?
It involves 2 steps:
1. On client, edit /var/symapi/config/netcnfg on local Unix server (client) to define remote management servers.
DC1_SERVER - TCPIP hostA 192.168.0.1 2707 ANY #
DC2_SERVER - TCPIP hostB 192.168.1.1 2707 ANY #

2. On client, connect to DC1_SERVER or DC2_SERVER by exporting following variables (can be done either manually or via profile files)
# export SYMCLI_CONNECT_TYPE=REMOTE
# export SYMCLI_CONNECT=DC1_SERVER

Errors while running the commands remotely

ERROR
CLIENT# symcfg list
The remote connection is refused. The symapi server is probably not running
SOLUTION

storsrvd is not running on remote server. Start the stordaemon as below

DC1_SERVER# stordaemon list

Available Daemons ('[*]': Currently Running):

[*] storapid EMC Solutions Enabler Base Daemon
storgnsd EMC Solutions Enabler GNS Daemon
storrdfd EMC Solutions Enabler RDF Daemon
storevntd EMC Solutions Enabler Event Daemon
[*] storwatchd EMC Solutions Enabler Watchdog Daemon
storstpd EMC Solutions Enabler STP Daemon
storsrvd EMC Solutions Enabler SYMAPI Server Daemon

DC1_SERVER# stordaemon start storsrvd

Waiting for daemon to start. This may take several seconds.
DC1_SERVER# stordaemon list

Available Daemons ('[*]': Currently Running):

[*] storapid EMC Solutions Enabler Base Daemon
storgnsd EMC Solutions Enabler GNS Daemon
storrdfd EMC Solutions Enabler RDF Daemon
storevntd EMC Solutions Enabler Event Daemon
[*] storwatchd EMC Solutions Enabler Watchdog Daemon
storstpd EMC Solutions Enabler STP Daemon
[*] storsrvd EMC Solutions Enabler SYMAPI Server Daemon

ERROR

2/9
CLIENT# symcfg list
The remote client/server handshake failed. Please consult symapi and storsrvd log files

SOLUTION
This is because remote server is expecting either a secure/nonsecure protocol for connection. Change the parameter
storsrvd:security_level in /var/symapi/config/daemon_options on server.

Before change:
# storsrvd:security_level = SECURE

After change (remove hash and change SECURE to NONSECURE):

storsrvd:security_level = NONSECURE

Shutdown and start storsrvd using stordaemon command and try again.

ERROR

CLIENT# symcfg list

The remote connection is refused. The client cannot have a newer SYMAPI version than the server

SOLUTION
Its for an obviously stated reason – Solution Enabler on client is of a higher version than that on server. Check the version by running
command symcli

CLIENT# symcli
Symmetrix Command Line Interface (SYMCLI) Version V7.6.1.0 (Edit Level: 1755) built with SYMAPI Version V7.6.1.0
(Edit Level: 1755)

DC1_SERVER# symcli
Symmetrix Command Line Interface (SYMCLI) Version V7.1.2.0 (Edit Level: 1059) built with SYMAPI Version V7.1.2.0
(Edit Level: 1059)

ERROR

CLIENT# symcfg list

The trusted host file disallowed a client server connection

SOLUTION
On remote server that is running storsrvd, check /var/symapi/config/nethost file and add an entry in the format “FQDN_of_client
userid_allowed_from_client” (example: hostnameA username). Restart storsrvd daemon by running
stordaemon shutdown storsrvd and stordaemon start storsrvd .

ERROR
CLIENT# symcfg list
The gatekeeper device (while using the Base Daemon) has an error (Please see the Log file)
CLIENT# symcfg discover
This operation may take up to a few minutes. Please be patient...
Unable to obtain unique ID for host
CLIENT#

SOLUTION
On remote server that is running storsrvd, change SYMAPI_USE_ACCESS_ID = LOCAL to SYMAPI_USE_ACCESS_ID = SERVER in
/var/symapi/config/options file and restart the daemons by running
stordaemon shutdown storsrvd and stordaemon start storsrvd .

How to set up WLA on the new arrays?

Log onto the console and drill down to- Administration/Data Collection Policies/Storage Agent for symmetrix/
Highlight one of the previously installed arrays.
Right mouse button / copy as/
New dialogue box rename the unique Descriptor as _SYM_15min
Go into Apply To tab and select from storage system from the left box to the right box ( selected Symmetrix).
Press Ok.

Problem with ECC – Gaps in stats

This happens because of repository.lb file getting corrupt. Go to the ecc\lockbox directory verify that the repository.lb file is greater than
0kb prefbly 3kb. If the repository.lb file is 0kb you need to stop ecc services, rename the repository.lb file within ecc\lockbox and copy the
file in from ecckup\exp and then start the services, all should work fine then.

Where to get EMCgrab from?

o From FTP: (AIX, HP-UX, Linux, Solaris, Tru64) ftp://ftp.emc.com/pub/emcgrab/Unix
o For OpenVMS: ftp://ftp.emc.com/pub/emcgrab/vms
o For ESX: ftp://ftp.emc.com/pub/emcgrab/ESX
o For ESXi: ftp://ftp.emc.com/pub/emcgrab/ESXi

Control and Log files locations

3/9
/usr/emc/ECC/data/swdata/symmWin.passwd – ECC Passwords are stored in this file.
/var/symapi/db/symapi_db.bin – default symapi database file (used to sync the configuration from the array to the management host
and is creatupdated when you do a symcfg discover. No problem with renaming it and then re-doing a symcfg discover to recreate it)
/var/symapi/config/netcnfg – lists the network services available from that host
/var/symapi/config/options – the options file contains behavior parameters that can be set to critically change default behavior of
SYMCLI oations, SYMAPI calls and their control actions
/var/symapi/config/symavoid – identifies devices to skip over when looking for devices
/var/symapi/config/gkavoid – identifies devices not chosen as gatekeepers
/var/symapi/config/inqfile – lists devices to be added to the symapi database
/var/symapi/log/symapi-.log – logfile for symcli.symapi functions, calls, activities

How do you fresh install symcli and discover emc kit?

First the Solution enabler software has to be installed which can be obtained from powerlink.emc.com. The should be unzip/untarred and
the emc_install gram should be run. You need to license the product and then run the following command to discover the connected
symmetrix:
# symcfg discover
# symcfg list

Powermt display showing several devices in asb:iopf state:

Issue
The powermt display dev=all command shows hardware path with asb:iopf instead of active
Symmetrix ID=xxxxxxxxxxx
state=alive; policy=SymmOpt; queued-IOs=0
=============================================================================================
--------------- Host ----------------------------------------
-Stor- -I/O Path- -Stats-
### HW Path I/O Paths Interf. Mode State Q-IOs Errors
=============================================================================================
3072 pci@1e,600000/SUNW,qlc@3,1/fp@0,0 c3t50000972081ADD18d4s0 FA 7eA asb:iopf alive 0 0
3074 pci@1e,600000/SUNW,qlc@3/fp@0,0 c2t50000972081ADD1Cd4s0 FA 8eA active alive 0 0

Resolution: The setting asb:iopf stands for “Auto standby intermittent I/O failure” algorithm.
This feature, the intermittent I/O failure algorithm, means the path will not be used unless all other active paths are dead.
asb path mode settings do not persist across reboots.
This can be turned on using the following options:
Turn on: powermt set autostanby=on trigger=iopf
Turn off: powermt set autostanby=off trigger=iopf
Usages: powermt set autostandby={on|off|reinitialize} [trigger={prox|iopf}]
This determines whether or not a path that has intermittent I/O failures should be placed into autostandby mode (asb:iopf). You can
override autostandby for a path by running powermt set mode={standby|active} dev= force .
If the path is already in the requested mode, then the command is ignored.
dev=||all sets the mode for the specified path, or all paths to the specified device (all specifies all paths to all devices.) The default is
all.
Example for device path:
# powermt set mode=active dev=/pci@8,700000/QLGC,qla@3/sd@
Example for all devices:
# powermt set mode=active dev=all devices
# powermt set mode=active dev=all devices
To verify if the asb:iopf is disabled or enabled check powermt display options or powermt
display dev=all.

The following modes are available in powermt set mode:

* ative – specifies a path that will be actively used for I/O for multipathing.
* sandby – specifies a path that has been manually placed in standby mode by the user.
This path will not be used unless all other active paths are dead. This path state cannot
change unless the user changes it back to active.
* asb – (for autostandby) specifies a path that has been placed into standby automatically
either using the VPLEX proximity autostandby algorithm (asb:prox) or the intermittent I/O
failure algorithm (asb:iopf). This path will not be used unless all other active paths are
dead. asb path mode settings do not persist across reboots.
* unlic -indicates that unlicensed PowerPath is running for a Symmetrix, VNX, and
CLARiiON storage system (no license key has been installed). In this scenario, all paths
are marked unlicensed except one path to each SP. Unlicensed paths cannot become candidates
for path failover.

A bug/problem with symapi_db.bin:

You’ve changed the name of the views/groups etc. however when you run symaccess view/list command it still shows old view names. In
order to change therename /var/symapi/db/symapi_db.bin the file on management host, and recreate it using symcfg discover.

4/9
A note on FAN in and FAN out rations:
Fan in Raito : The Fan ratio defines the number of storage connections to a particular server.
For example Server A can access storage from Storage A, B, C, and D So the fan in ratio is 1:4

Fan out ratio: The fan out ratio is the number of initiators per storage port. So you could have Server A, B, C and D accessing Storage port-
A. The fant ratio would be 3:1

Thumb rules for Fan in Ratio

2:1. Ideally keep it 1:1 to avoid difficulties in troubleshooting performance related issues.
Thumb rules for Fan out ratio
For High IO hosts 1:1
For med IO hosts 4:1 or even 7:1 depending on how you describe medium IO.
For low IO hosts 12:1 or even 20:1 depending on how you describe low IO

Also remember that each storage port has a definite queue length so connecting more hosts means sharing of that queue depth and thus
can lead to perforce bottlenecks.

Call logging procedure for EMC:

Telephone
EMC Global Support is available 24×7 and can be contacted through the UK Local Telephone Number : 0870 6000 300 , AUS –
1800653565
A Global list of support contact numbers is available from EMC Global Support Contacts
When raising a telephone support call, please have on hand the serial number of the system. It is important to include the leading
CK/HK/FP reference ohe serial number as all systems are stored internally within EMC using this reference.
Online Powerlink
Support cases can be raised through http://powerlink.emc.com – for this you will need to have an existing powerlink account. See
theCreate EMC Powerlinccount Guide for further details.
Online Support Chat
The Online Support Chat can be used to start a technical call and in doing so, a case is automatically raised. To access the Online Support
Chat, Login Powerlink (see the Create EMC Powerlink Account Guide for details on creating an account), Select Support –> Request
Support –> Live Chat

Rule of pair mapping:

On DMXs – a to d, b to c with rule of 17 and ports opposed. So 3a:0 will be partnered with 14d:1. 5c:1 will be paired with 12b:0.
On VMAXs – a to a, b to b, c to c, d to d with rule of 17 and ports opposed. so 3a:0 will be 14a:0, 5c:1 will be 12c:1 and so on.

If device comes up as “Reserved” on server after masking on the array (the dev was in use before somewhere)
Find out disks which have SCSI reservation
# symdev -sid 1234 -resv list | grep 0CD8
/dev/rdsk/c2t5006048C52A90B46d172s2 0CD8 RAID-5 08 03B:1 Group
/dev/rdsk/c2t5006048C52A90B46d172s2 0CD8 RAID-5 08 03B:1 Group
/dev/rdsk/c2t5006048C52A90B46d172s2 0CD8 RAID-5 08 10B:1 Group
/dev/rdsk/c2t5006048C52A90B46d172s2 0CD8 RAID-5 00 07C:0 Group
/dev/rdsk/c2t5006048C52A90B46d172s2 0CD8 RAID-5 00 14C:0 Group
/dev/rdsk/c2t5006048C52A90B46d172s2 0CD8 RAID-5 00 14C:0 Group

Create device group, add the devices in it, break the device away from device group, delete the device group
# symdg -type regular create testdg (chose -type rdf1 for R1s and rdf2 for R2s)
# symld -sid 1234 -g testdg addall -range 0CD8:0CE8
# symld -g testdg break DEV0001 (Do this for all the dev)
# symdg -force delete testdg
http://knowledgebase.emc.com/emcice/documentDisplay.do?
docType=1006&clusterName=DefaultCluster&resultType=5002&groupId=1&page=&docProp=$solution_id&docpValue=emc81931&passedT

How to check the lock on the configuration and release it?

# symcfg -sid 1234 -lockn all list
Symmetrix ID: 000290101234

S Y M M E T R I X L O C K S

Lock Lock Lock Time

SymmID Attachment Status Number Usage Held (Sec)

000290101234 Local Locked 15 Config Change 183

# symcfg -sid 1234 -lockn 15 release

The specified Symmetrix External Lock cannot be released except if the force flag is used

# symcfg -sid 1234 -lockn 15 release -force

5/9
Interrogating Configuration Server for config change session information
Lock 15 was obtained to protect a configuration change session.

The Application that initiated the configuration change : SYMCONFIGURE

The Host that initiated the configuration change : hostA
The Process ID that initiated the configuration change : 28701
The last action requested by the application : N/A
Type of changes being made : N/A
The session length : 3 min 59 secs

Abort the configuration change session for Symmetrix unit 000290101234 (y/[n]) ? y

The configuration change session has been aborted.

A few devices on server can’t pick up the pseudo name (last column). What is the solution?
# syminq |egrep -i "hdisk5|hdisk25"
/dev/rhdisk5 EMC SYMMETRIX 5772 8300562000 N/A
/dev/rhdisk25 EMC SYMMETRIX 5772 8300562000 N/A
/dev/rhdisk50 EMC SYMMETRIX 5772 8300610000 23809920

# lscfg -vpl hdiskpower0

hdiskpower0 U787F.001.DPM32TZ-P1-C1-T1-L2 PowerPath Device

Manufacturer................EMC
Machine Type and Model......SYMMETRIX
ROS Level and ID............5772
Serial Number...............83562000
Part Number.................000000000000510026000290
EC Level....................102783
LIC Node VPD................0562
Device Specific.(Z0)........00
Device Specific.(Z1)........51
Device Specific.(Z2)........577201040000000000093010
Device Specific.(Z3)........12000000
Device Specific.(Z4)........54110008
Device Specific.(Z5)........FF80
Device Specific.(Z6)........4D

SOLUTION:
Go into /etc and look for any files with a .FCS extension. If there are, remove them.
Then move the /kernel/drv/emcp.conf file and any .saved versions to a different location and rename them.
Once this is done, do a touch /kernel/drv/emcp.conf to recreate the file.
Run powercf -q and a powermt config.
Check with the powermt_display_dev=all command to see if all the devices now have Pseudo Names.

When server logs the errors about paths going dead and coming back, chances are they running short of
gatekeepers, and are using data devices as gatekeepers instead.
May 18 20:18:38 hostA kern:err|error unix: emcp: Error: Killing bus 0 to Symmetrix 000294901111 port 7gA.
May 18 20:18:38 hostA kern:err|error unix: emcp: Error: Path hdisk390 to 000294901111 is dead.
May 18 20:18:38 hostA kern:err|error unix: emcp: Error: Path hdisk123 to 000294901111 is dead.
May 18 20:18:38 hostA kern:err|error unix: emcp: Error: Path hdisk395 to 000294901111 is dead.
...

Then after few seconds the path appears to be alive:

May 18 20:18:47 hostA kern:info unix: emcp: Info: Path hdisk390 to 000294901111 is alive.
May 18 20:18:47 hostA kern:info unix: emcp: Info: Path hdisk123 to 000294901111 is alive.
May 18 20:18:47 hostA kern:info unix: emcp: Info: Path hdisk395 to 000294901111 is alive.

SOLUTION:
Add extra gatekeepers, and also add following parameter to file /var/symapi/config/daemon_options as described in emc217815,
emc231545.
storapid:parallel_inquiry_size = 0

URL to access EMC services, and ECC port number

https://:8443/sem => for SMC
https://:8443/spa => for SPA
ECC Port number: 10799

While running symmigrate for VLUN migration, the client host receives an error when establishing clone session
# symclone -sid 1234 -f clone_1234 -nop establish

'Clone Incremental Establish' operation execution is in progress for the device list in device file
'clone_1234'. Please wait...

6/9
Thin device is not bound to any pool
Establish failed

This is because if incorrect version of Solution Enabled being used. It should be V7.2.1.0 or above.

PowerPath Pseudo names for newly presented devices are missing upon reboot. Rnning “powercf -q; powermt
config” does not help OR powermt.custom is missing the entries for all the newly presented devices OR
emcp.conf has the entries for the missing pseudo names
Environment:
OS: Solaris 10 SPARC
EMC SW: PowerPath
EMC SW: PowerPath 5.3 P02

Cause:
The boot archive had not been updated after the configuration changes. The update normally occurs during the shutdown process but a
hard reset can interrupt this scheme.

Resolution/Workaround:
For each missing pseudo name, run a powermt unmanage/powermt manage command using the native name such as:
# powermt unmanage dev=c3t50000974C0149158d88
# powermt manage dev= c3t50000974C0149158d88
This will fix PowerPath configuration. Once this is done for all the devices, run a “powermt save” to update powermt.custom. Then run a
“bootadm update-archive” command to avoid the issue at the next reboot.

Permanent fix:
After each PowerPath configuration change, run a “bootadm update-archive” command to be sure that the changes are persistent upon
reboot even in case of “not so clean” reboot.

How to check statistics of individual tdevs in Unisphere

* Login to Unisphere (https://hostname:8443)
* Click Performance
* Click Analyze
* Double click Diagnostic
* Under Device group tab, double click ungrouped
* Double click tdev id
* Select desired performance matrix from bottom left pane
* Toggle between average and maximum value by click an icon in the right above the graph in local right pane

Server having issues in picking up newly allocated devices, configuring them or powerpath. Useful commands in
troubleshooting the issue
fcinfo hba-port
cfgadm -lao show_FCP_dev
powermt display
powermt display dev=all
powermt display paths
sympd list
syminq hba
syminq -wwn
syminq -pdevfile
symcfg list

How to rcreate symapi_db.bin and reimport all the diskgroups

# symdg -sid 1234 exportall -f mydgfile_1234.txt
# symdg -sid 1234 exportall -f mydgfile_1234.txt
# mv /var/symapi/db/symapi_db.bin /var/symapi/db/symapi_db.bin_old
# /usr/symcli/bin/stordaemon shutdown storapid -immediate
# /opt/emc/SYMCLI/V7.1.2/bin/symcfg discover
# symdg -sid 1234 importall -f mydgfile_1234.txt
# symdg -sid 1234 importall -f mydgfile_1234.txt
# symcfg discover

How to check stats on a volume n Unisphere

click performance
then click analyze
then double click diagnostic
in the device group tab
double click ungrouped
double click the volume

7/9
Powerpath not creating emcpowerpath devices for newly assigned devices
For this, unmanage and then remanage the device
# /var/tmp/uplift# syminq |grep 264C
/dev/rdsk/c1t500009740842B514d10s2 R1 EMC SYMMETRIX 5875 690264C000 23809920
/dev/rdsk/c1t500009740842B550d10s2 R1 EMC SYMMETRIX 5875 690264C000 23809920
/dev/rdsk/c3t500009740842B56Cd10s2 R1 EMC SYMMETRIX 5875 690264C000 23809920
/dev/rdsk/c3t500009740842B528d10s2 R1 EMC SYMMETRIX 5875 690264C000 23809920

Solution
#powermt config
powermt unmanage dev=c1t500009740842B514d10s0
powermt manage dev=c1t500009740842B514d10s0
# syminq |grep 264C
/dev/rdsk/c1t500009740842B514d10s2 R1 EMC SYMMETRIX 5875 690264C000 23809920
/dev/rdsk/c1t500009740842B550d10s2 R1 EMC SYMMETRIX 5875 690264C000 23809920
/dev/rdsk/c3t500009740842B56Cd10s2 R1 EMC SYMMETRIX 5875 690264C000 23809920
/dev/rdsk/c3t500009740842B528d10s2 R1 EMC SYMMETRIX 5875 690264C000 23809920
/dev/rdsk/emcpower0c R1 EMC SYMMETRIX 5875 690264C000 23809920

Error while adding the devices to storage group

# symaccess -sid 1234 -name host_sga -type storage add devs 2686,26A6,26D4,26E6
The action cannot be attempted because there are no devices which were selected
It means you are trying to add the devices that alaready exist in that storage group

Error while masking the devices using -lun

# symaccess -sid 1234 -name host_sga -type storage add dev 210F,2111,2113,218B -lun 32
The operation will result in consistent lun violation
Above command wants to mask 4 devices using lun ids 32,33,34,35 but these lun ids are in use.

Error while running any symcli command

serverA# symaccess -sid 1234 list logins
The host System Stable Values do not match the current system configuration
This has been observed specifically with SE 8.0.3 and occurs because during SE upgrade one or more out of 5 system parameters used by
SE got changed. This locks out the lockbox password (please don’t ask me what is lockbox – I just know the term :-))
This can be resolved by resetting the lockbox password as follows:
serverA# symcfg -lockbox -password serverA@SELockbox1 reset -ssv

Error while running any symrdf commands after enabling symauth

# symrdf -g dgname query
The caller is not authorized to perform the requested operation

In most of the cases, this occurs because of mismatch between the users/groups defined in symauth database on the array, and credentials
of user running command from host. Find out the list of users/groups defined in symauth database using the command:
# symauth list -user -sid 1234
Ensure the users are defined as user and groups are defined as group. symauth will gleefully accept group name as user and vice versa,
and you will end up scratching your hairs why it isn’t working. To delete an entry from and to add a new entry into symauth database:
# cat delusergrp
delete user xyz; group=grpname;
# symauth -sid 1234 -f delusergrp comm -nop
# cat addusergrp
assign abc to role storageadmin; newgroup admin;
# symauth -sid 1234 -f addusergrp comm -nop

Error while running symaccess comands – Solution Enabler 8.0.3

# symaccess -sid 1234 delete view -name viewname -unmap
The current setting does not allow control operations on devices that are not host visible.

To get around this, add following line to /var/symapi/config/options file:

SYMAPI_CTRL_OF_NONVISIBLE_DEVS = ENABLE
Shutdown and start storapid.

Error while running symaccess comands – Solution Enabler 8.0.3

# symconfigure -sid 1234 -cmd 'unbind tdev abc from pool pooname;' prep -nop
Error occurred while Starting
Read or Read/Write permission/access not present
The configuration change session has failed.

To resolve this, change the permission of /var/symapi/db/symapi_db.bin file to 777.

8/9
powerpath fails to load with powershift script message
Error messages in /var/adm/messages:
Cancelling powershift script: PowerPath driver version () does not match expected version (53000)
The empty parenthesis in the error reported in /var/adm/messages (PowerPath driver version () does not..) is showing that the powershift
script can not find the emcp release with the “modinfo” command because it is not loaded.
Solution is to uninstall PowerPath and reinstall it.

Error while creating devices on local and remote array using symconfigure
# symconfigure -sid 1234 -cmd "create dev count=4, size=50 GB, emulation=FBA, dynamic_capability=dyn_rdf,
config=RDF1+TDEV, remote_config=RDF2+TDEV, ra_group=21, binding to pool=localpool_1,
remote_pool=remotepool_1,sg=localhostA_sga,remote_sg=remotehostB_sga; " prep -nop
A Configuration Change operation is in progress. Please wait...
Establishing a configuration change session...............Failed.
Error occurred while Starting
Remote configuration change sessions cannot define or abort RDF changes.
The configuration change session has failed.

Solution
Ensure the user you are running the command as has appropriate group asigned in symauth/symacl across both the arrays.

You’ve created new SRDF paired devices on local and remote array using symconfigure. However, when you try
to add the remote devices into storage groups, storage management server gives error “Devices not configured”
Solution
This happens because the either storage management servers (local and remote) have not refreshed their configurations with devices
remote to them. To refresh the configuration, run the following command:
symcfg -sid 1234 list -tdev -dev xxx:xxx

SANSPIRE © 2021. All Rights Reserved.

9/9