How to enable SFTP on NetApp filer

How to enable SFTP on NetApp filer

Follow the below mentioned steps to enable SFTP on netapp filer.

1. rdfile /etc/passwd
2. cifs passwd root
3. copy the encrypted password and replace with existing root password on /etc/passwd file.
4. options sftp
sftp.auth_style              unix
sftp.bypass_traverse_checking off
sftp.dir_override            /vol/vol0
sftp.dir_restriction         off
sftp.enable                  on
sftp.idle_timeout            900s       (value might be overwritten in takeover)
sftp.locking                 none
sftp.log_enable              on
sftp.log_filesize            512k
sftp.log_nfiles              6
sftp.max_connections         15         (value might be overwritten in takeover)
sftp.max_connections_threshold 75%        (value might be overwritten in takeover)
sftp.override_client_permissions off

5. options secu

security.admin.authentication nsswitch,internal

security.admin.nsswitchgroup

security.passwd.firstlogin.enable off

security.passwd.lockout.numtries 4294967295

security.passwd.rootaccess.enable on

security.passwd.rules.enable off

security.passwd.rules.everyone off

security.passwd.rules.history 0

security.passwd.rules.maximum 256

security.passwd.rules.minimum 8

security.passwd.rules.minimum.alphabetic 2

security.passwd.rules.minimum.digit 1

security.passwd.rules.minimum.symbol 0

6. options ssh

ssh.access                   *

ssh.enable                   on

ssh.idle.timeout             0

ssh.passwd_auth.enable       on

ssh.port                     22

ssh.pubkey_auth.enable       on

ssh1.enable                  off

ssh2.enable                  on

now try to connect.

VMAX and Symmetrix SYMCLI commands

symcfg

Before you can do anything with a VMAX, you need to install the Solution enabler software, which you can get from powerlink.emc.com. You download the software, unzip or untar it, run the emc-install program and get the product licensed.
Now you have your software, but you need to run an initialisation command before you can connect to your DMX. Navigate to /usr/symcli/bin and run;

 symcfg discover
 symcfg list 

The first command gets information from the DMX and uses it to build a configuration database on your host. The second command lists that information out.

However symcfg is a very powerful command that can be used to display and alter the configuration of a VMAX. My preference is to use symconfigure for most of this, but symcfg can be used to manage VMAX locks, RDF and director ports, gatekeeper devices, hosts and host ports, mainframe connections, and more.

Discover all VMAX arrays connected to this host, then build or refresh the Symmetrix configuration database file using this information:

  symcfg discover

Display information held in the Symmetrix configuration database about all attached Symmetrix arrays

  symcfg list

Display more detailed information about the attached Symmetrix arrays and their directors

  symcfg list -v -dir all

Display detailed information about a specific director, in this case 0E

  symcfg list -v -dir 0E

Display information about all front-end directors on Symmetrix array 824

  symcfg list -SA ALL -sid 824

Display information about all the registered hosts that are connected to the Symmetrix array 824

  symcfg list -connections -sid 824

To list all gatekeeper and database access locks, enter:

  symcfg list -semaphores

To verify whether the Symmetrix 824 configuration and the Symmetrix configuration database are in sync, enter:

  symcfg verify -sid 824

list the port flags for port 0 on director 5 position A

  symcfg -sid 38 list -sa 5A -p 0 -v

Take the above port offline (necessary to change port flags - and remember this could make storage unavailable to users so use with caution)

  symcfg -sid 38 offline -sa 5A -p 0 

enable port flag vcm-state on the above port

  symcfg -sid 38 set port 5A:0 vcm-state=enable 

put the port back online

  symcfg -sid 38 online -sa 5A -p 0 

symconfigure

The symconfigure command lets you make changes to your Symmetrix device, for example to add new volumes, add or change port and host assignments and configure remote mirroring RDF devices. It updates the symm.bin file on the symm. device. The command cannot be shortened, symcfg is a different command

As part of making changes, symconfigure lets you save the current configuration, reserve devices to prevent others from using them, and gives you a number of query, list and verify options to check the current status of a symmetrix and validate any proposed changes before applying them.

You run symconfigure from a host server that is connected to the symmetrix, If anything happens to that host or the connection to the symm. while a change was in progress then the symm. could be left in an indeterminate state. To cater for this scenario, symconfigure has an abort option that lets you back out uncompleted changes.

symconfigure itself has a fairly small set of parameters, it does most of its powerful processing by reading a command file. The simplest command is symconfigure -h, the online help facility. The other symconfigue commands require a -sid parameter which identifies the Symmetrix that you are going to change. Before you want to start to make changes you will probably want to see your existing Symmetrix configuration.

If the query command shows that a hung session exists, then no more updates will be possible as any session puts a lock 15 on the symm.

Checking VMAX status using symconfigure and managing reserves

These examples commands are running against a VMAX with a symmetrix ID of 123

Query VMAX 123 to see what total freespace is available

    symconfigure -sid 123 -freespace -unit mb list 

Display the version number of the SYMCLI, SYMAPI and the configuration server. -sid is optional, leave it off and the versions for all attached symms are displayed.

    symconfigure -sid 123 -version -v 

The query command will check for any existing active configuration activity. If this command cannot get the information, it will keep retrying. You can control this with the -i and -c options which are interval between retries and number of retries.
Query a VMAX 8 times at 5 second intervals to see if any updates are running

    symconfigure -sid 123 -i 5 -c 8 -v query

Query a VMAX for reserves

    symconfigure -sid 123 -reserved list

Query a given reserve to get more details

    symconfigure -sid 123 -reserve-id 4567 show

Safely attempt to release reserve 4567

    symconfigure -sid 123 -reserve-id 4567 -noprompt release

Symconfigure examples using the command file

If you are planning updates to your VMAX configuration, then generally the best way to do this is to put all your updates into a command file, then run that file through the symconfigure command. The advantages of doing this is that you can get your commands peer checked by a colleague and syntax checked by the system before you run them. Each command has three options,
'preview' which checks the syntax of your command list;
'prepare', which also checks your syntax, then checks that the VMAX is in a healthy enough state to process the commands, with enough free resources to process the command,
'commit' which does the first two, then applies the updates.

The basic syntax for running symconfigure updates using a command file called command.txt is

    symconfigure -sid 123 -v -file command.txt preview  
    symconfigure -sid 123 -v -file command.txt prepare
    symconfigure -sid 123 -v -file command.txt commit 

SAMPLE File format :

save below content in txt file.

Form meta from dev 0112, config=striped, stripe_size=1920;
add dev 0113 to meta 112;
add dev 0114 to meta 112;
add dev 0115 to meta 112;
add dev 0118 to meta 112;
add dev 0119 to meta 112;

Some optional parameters are -noprompt which suppresses the 'do you really want to ...' messages and -v for verbose which means echo results back to the terminal

Changing devices

Create 2 small Gatekeeper devices. Gatekeepers are used to communicate with the VMAX. EMC recommends 4 gatekeepers per port and they are typically created with just 6 cylinders.

    create dev count=2 size=6 emulation=fba;

Create 20 bigger Standard devices

    create dev     count=20,
  SIZE=50 GB, 
 eMulation=FBA;

Note that the commands are not case sensitive, parameters can be separated by commas or spaces, can span more than one line, can contain extra white space, but must end with a semicolon ';' .

Add 6 a new spare devices

create spare count=4, format = 520;

Older symmetrix devices has 512 bytes in a block, new devices have 520 bytes in a block.

To delete disks use

  delete dev Device-name

Working with Metas

EMC split a physical device into between 1 and 128 hyper volumes, which are then combined together to form meta devices. A meta corresponds to a LUN as presented to a host, so a LUN can be bigger than a physical device. A meta-device can consist of up to 1024 hypers, but all the hypers must be the same size and type and have the same protection. Valid hyper sizes range from between 0.5 and 32GB. A Meta can be concatenated, that is, it can consist of hypers strung together, or it can be striped, when the data is striped across the hypers. The first device in a meta is known as the meta head.

The starting point is to find any unmapped devices using the command symdev list -noport. If any of these devices are allocated as BCV pairs or defined to device groups, then split them out using commands like this

 symmir -g group_name split
 symmir -g group_name rmall

define a concatenated meta and add 2 more devices to it. Concatenated metas are best for sequential data access, and they are easier to gorw or shrink that striped metas.

   form meta from device 028
      config=concatenated;
   add dev 015:016 to meta 028;

define a striped meta and add 2 more devices to it. Striped metas are best for random data access, but they can't be shrunk and are more difficult to grow.

   form meta from device 02b
      config=striped
   stripe-size=1920;
   add dev 017:018 to meta 02b;

Split meta 02b back into it's constituent hypers - this will destroy any data on the meta!

 dissolve meta dev 02b;

remove device 016 from meta 028

 remove dev 016 from meta 028;

Using SYMTIER to work with FAST tiering

Two types of FAST tier exist, disk provisioned virtual tiers and virtual provisioned storage tiers. 'Disk provisioned' is also split into static and dynamic. The following command will list all the storage tiers in array '123', including DiskGroup and Virtual Pool Tiers. If you just wanted to list DiskGroups or Virtual Pools you would add the switch -dp or -vp as appropriate.

symtier -sid 123 list

To get more detailed information about a specific tier use this command - obviously with your subsystem id and tier name.

symtier -sid 124 show -tier_name TEFD1

SYMTIER EXAMPLES

Click to See Examples

To work with FAST tiers, you need to be able to create and delete them, and also add and remove disks from them. The following command will create a static, disk provisioned pool called 'TSDP1', configured in RAID5, 3+1 format in disk array '123' from SATA disks. Alternative disk tecnology options are FC (Fiber Channel) or EFD (Enterprise Flash Drive). -dsk_grp is the disk groups to be added to the tier. In this case we are allocating a single disk group ID=2, but you can allocate a list of disk groups, and you can allocate them by name.

symtier -sid 123 create -name TSDP1 -inc_type static -tgt_raid5 -tgt_prot 3+1
   -technology SATA -dsk_grp 2

This command will create a flash disk tier in RAID1 format. -vp means this tier will be allocated using virtual provisioning

symtier -sid 123 create -name TEFD1 -tgt_raid1 -technology EFD -vp

To add a disk group to an exisiting tier use the following command. This adds 'disk group 3' to existing Storage Tier 'TSDP1'.

symtier -sid 123 -tier_name TSDP1 add -dsk_grp 3

and to remove it again use

symtier -sid 123 -tier_name TSDP1 remove -dsk_grp 3

You can also rename a tier if you did not like the existing naming standard, so 'TSDP1' becomes 'Tier_qxy29p

1'

symtier -sid 123 rename -tier_name TSDP1 -name Tier_qxy29p1

and finally, to delete a tier use this command.

symtier -sid 123 delete -tier_name Tier_qxy29p1

Create a mainframe striped meta. This must include at least 4 meta devices. This example creates 4 * 500 cylinder metas, then uses them to create a 2000 cylinder striped CKD meta in a RAID1 configuration.

   create dev count=4 size=2000
    emulation=CKD-3390 config=2-way-mir
 attribute=CKD-meta;

PAV aliases are used to allow multiple concurrent access to mainframe devices. See the PAV section for details. The following commands can be used to allocate PAV aliases. The first command will add 4 aliases to a specific symm. device. The second command allocates a range of aliases to a sub system

  add pav alias to dev 02b alias count=4 
  add pav alias range 127:255 to mvs ssid=B000 

Some other useful commands

symdev

One of the main uses of the symdev command is to see what free hypers are available. The command to do this is

   symdev list -noport
   
   symdev list -da all space   
   
   symdev list -meta 
   
   symdev show meta head address 

The second command will show all backend space available
The third command will list out all the meta heads, and also tell you how many hypers are associated with each meta head.
The last command will list out all the details for one meta. The show command usually gives more detail than list, as it reads its information from the host database.

symapierr

Returns a string with a detailed description of any return code generated by any SYMAPI function
To return a string for error number 10, enter:

   symapierr 10

The following will be output:

 SYMAPI Error Symbol : SYMAPI-C-NO-DEVS-FND-UPGRADE
 SYMAPI Error Message: No Symmetrix devices found with microcode version 5x63 or up.

syminq

This command checks which devices are mapped to a host
To work out directory and port mappings enter:

   syminq -pdevfile

DMX commands

Command for DMX symcli operations

symmask -sid 123 list logins -wwn 00000000000000000000
symmaskdb -sid 123 list assignment -dev 0913
symcfg -sid 123 list -avail -addr -dir 8a -p 1
symdev -sid 123 list -noport
 symcfg -sid 123 list -available -addr -dir 8d -p 1
symmaskdb -sid 123 list assignment -dev
symmaskdb -sid 123 list assignment -dev 05CE
 symmaskdb -sid 123 list devs -wwn 000000000000000000000

symconfigure -sid 76 -cmd "unmap dev 170 from dir all:all;" commit
symdev -sid 76 write_disable 170
symcfg -sid 76 release -lockn 15 -force
symcfg -sid 76 list -lock -lockn all

symcfg -sid 76 list -sa all

map dev 0A77 to dir 4d:0 lun=82;
symcfg list -sid 76 -dir 4d -p 0 -add -avail | find/i "*"
dissolve meta dev 170;

form meta from dev 112, config=striped, stripe_size=1920;
add dev 113:016f to meta 112;

symconfigure -sid 76 -cmd "map dev 172 to dir 4d:0, lun=07;" preview


symmask -sid 76 list logins

>symcfg list -sid 76 -dir 4c -p 0 -add -avail |more


new lun provisioning.



symcfg -sid 1234 list -available -dir 8A -port 1

symcfg -sid 1234 list -available -dir 8A -p 1

symcfg -sid 1234 list -available -addr -dir 8A -p 1

symmaskdb -sid 1234 list devs -wwn 0000000000000000

symmaskdb -sid 1234 list assignment -dev 1430

symconfigure -sid 1234 -cmd "map dev 159E to dir 8A:1, vbus=6, Target=0A, lun=02;" preview

symcfg -sid 1234 list -available -addr -dir 9A -p 1

symconfigure -sid 1234 -cmd "map dev 159E to dir 8A:1, vbus=6, Target=0A, lun=02;" commit

symmaskdb -sid 1234 list assignment -dev 159E

symconfigure -sid 1234 -cmd "map dev 159E to dir 9A:1, vbus=6, Target=0A, lun=02;" commit

symconfigure -sid 1234 -cmd "map dev 159E to dir 9A:1, vbus=6, Target=0A, lun=02;" preview

symconfig -sid 1234 -cmd "set dev 159E  attribute=SCSI3_persist_reserv;" preview

symconfigure -sid 1234 -cmd "set dev 159E  attribute=SCSI3_persist_reserv;" preview

symconfigure -sid 1234 -cmd "set dev 159E  attribute=SCSI3_persist_reserv;" commit

symmask -sid 1234 -wwn 0000000000000000 -dir 8A -p 1 add devs 159E

 symmask -sid 1234 -wwn 0000000000000000 -dir 8A -p 1 add devs 159E

 symmask -sid 1234 -wwn 0000000000000000 -dir 9A -p 1 add devs 159E

 symmask -sid 1234 -wwn 0000000000000000 -dir 9A -p 1 add devs 159E

symmaskdb -sid 1234 list assignment -dev 159E


 1430    0000000000000000  FIBRE  FA-8A:1
        0000000000000000  FIBRE  FA-8A:1
        0000000000000000  FIBRE  FA-9A:1
        0000000000000000  FIBRE  FA-9A:1

 symmask -sid 1234 -wwn 0000000000000000 -dir 8A -p 1 add devs 159E

 symmask -sid 1234 -wwn 0000000000000000 -dir 8A -p 1 add devs 159E

 symmask -sid 1234 -wwn 0000000000000000 -dir 9A -p 1 add devs 159E

 symmask -sid 1234 -wwn 0000000000000000 -dir 9A -p 1 add devs 159E


 0EAF
 1445

 symmask -sid 1234 -wwn 0000000000000000 -dir 8A -p 1 remove devs 0EAF

 symmask -sid 1234 -wwn 0000000000000000 -dir 8A -p 1 remove devs 0EAF

 symmask -sid 1234 -wwn 0000000000000000 -dir 9A -p 1 remove devs 0EAF

 symmask -sid 1234 -wwn 0000000000000000 -dir 9A -p 1 remove devs 0EAF

  symmask -sid 1234 -wwn 0000000000000000 -dir 8A -p 1 remove devs 1445

 symmask -sid 1234 -wwn 0000000000000000 -dir 8A -p 1 remove devs 1445

 symmask -sid 1234 -wwn 0000000000000000 -dir 9A -p 1 remove devs 1445

 symmask -sid 1234 -wwn 0000000000000000 -dir 9A -p 1 remove devs 1445


 symconfigure -sid 1234 -cmd "unmap dev 0EAF to dir 9A:1, vbus=6, Target=0A, lun=02;" preview

symcfg

symcfg list : A brief description of the all connected Symmetrix boxes.
symcfg -sid 1234 list -lockn all : Lists all the external locks held in Symmetrix array 1234.
symcfg -sid 1234 -lockn 15 release -force : Release the lock 15 held on array 1234 .
symcfg -sid 1234 list -v : Displays detailed information about the Symmetrix Array 1234.
symcfg -sid 1234 -dir 4a -p 0 list -addr -avail : Lists the LUN information / availability of lun ids on port 4a:0 in array 1234 .
symcfg -sid 1234 list -rdfg all : List details about all the rdf groups in array.
symcfg -sid 1234 list -rdfg 3 : List details about rdf group 3 .
symcfg -sid 1234 list -rdfg all -dynamic : List details about all the dynamic rdf groups in array .
symcfg -sid 1234 list -rdfg all -static : List details about all the static rdf groups in array .
symcfg -sid 1234 list -ra all : List all RA ports with details like rdfg number , remote array sid and online status.
symcfg discover : Scans all the devices in hosts looking for new symmetrix devices and rebuilds the symmetrix configuration database .

symdev

symdev -sid 1234 list : Lists all devices in symmetrix 1234.
symdev -sid 1234 list -noport : Lists the devices which are not mapped to any ports.
symdev -sid 1234 list -noport -meta : Lists all unmapped meta devices .
symdev -sid 1234 list -dynamic : Lists all devices whose dyn_rdf attribute set .
symdev -sid 1234 list -hotspare : Checks whether hotspare invoked in the array .
symdev -sid 1234 show ABC : show the detailed information about the devioce ABC.
symdev -sid 1234 write_disable ABC -SA all : Write disable the device ABC from through all directors.
symdev -sid 1234 not_ready ABC -SA all : Not ready the device ABC from through all directors.

symmaskdb

symmaskdb -sid 1234 -dev ABC list assign : List the masking details of the dev ABC .
symmaskdb -sid 1234 -wwn xxxxxxx list devs : List the devices masked to the given wwn number .

symmask

symmask list hba : List the HBA details of the host.
symmask -sid 1234 -dir 4a -p 0 list logins : List out wwn s logged through port 4a:0 .
symmask -sid 1234 refresh : Refresh the VCM Data Base after a masking and unmasking operation.
symmask -sid 1234 -wwn xxxx -dir 4a -p 0 add devs ABC,ABD : Mask the devices ABC and ABD to the given wwn in 1234 arrray .
symmask -sid 1234 -wwn xxxx -dir 4a -p 0 remove devs ABC,ABD : Unmask the devices ABC and ABD from the given wwn in 1234 arrray .

symdg

symdg -sid 1234 list : List the device groups which include the devices from array 1234.
symdg create mydg -type rdf1 : Create device group mydg of rdf1 type .
symdg show mydg : Shows the members/details of mydg.
symdg rename mydg yourdg : Renames the mydg to yourdg.
symdg delete mydg -force : Delete device group mydg.

symld

symld -g mydg -sid 1234 add dev ABC DEV006 : Add the RDF device ABC to device group mydg as DEV006
symld -g mydg remove DEV006 : Remove DEV006 form device group mydg.

symrdf

symrdf -sid 1234 -rdfg 3 -type rdf1 -file rdf.txt -g mydg createpair -establish : Establish the SRDF relation between the devices given in the file rdf.txtfrom array 1234(R1) and remote box according to the rdf group . This command start sync between R1 and R2, and also add these devices after creating the device group mydg.
symrdf -sid 1234 -rdfg 3 -file rdf.txt query : Query the Devices by using the device pair file.
symrdf -g mydg set mode acp_disk : Set syncing mode to Adaptive Copy.
symrdf -g mydg query : Query the device group.
symrdf -g mydg split : Split the dynamic srdf pair.
symrdf -sid 1234 -rdfg 3 -file rdf.txt deletepair.txt -force : Delete the srdf pairing between R1/R2 and return them to normal.

symdisk

symdisk -sid 1234 list -hotspare : Lists the Hotpsraes configured in the array.
symdisk -sid 1234 list -by_diskgroup : Dispalys all the disks in the array by grouping by disk groups.
symdisk -sid 1234 list -diskg_roup 1 : Dispalys all the disks in disk group 1.

VMAX commands

below command to check failed disk in RG  

 

942  symdev -sid 599 list -datadev -v |grep Degraded
  943  symdev -sid 599 list -datadev -v |grep -i failed

 

 

symcli command for VMAX operations.
VMAX3 lun decom, we need to free all devs to delete

symdev -sid 123-devs 028F free -all

******************************************

symaccess show IG_SERVER01 -type init -sid 1234 -detail


symcfg -sid 740 list -tdev -bound -gb -detail |more

*************************************

lun id reset command 

If we wish to remove this identity, this is a disruptive process. You can do the following to reset the identity:

1. Take devices offline to the host and then remove them from their current storage group
2. Issue the command: ‘symdev set -no_identity <dev>’ against each device
3. Add the devices back to the storage group and rescan on the host
4. Confirm that the correct identity is now seen in syminq

*********************************************

Decomission Process

Start

symaccess -sid 589 list devs 0B81 -type storage
symdev -sid 589 not_ready -dev 0B81
symconfigure -sid 589 -cmd "unbind tdev 0B81 from pool F15_R5_02_1B;" prepare
symconfigure -sid 589 -cmd "unmap dev 0B81 from dir all:all;" prepare
symcfg -sid 589 list -tdev -gb |grep -i u
symdev -sid 589 list -tdev -unbound to check the status
symconfigure -sid 589 -cmd "dissolve meta dev 0B81 ;" prepare
symconfigure -sid 589 -cmd "delete dev 0B81:0B84;" prepare

symdev -sid 1234 -dev AAA:AAC,DDD unbind (to unbind multiple devs)

Done

***********************************************
to check tdev lun utilization
symcfg -sid 1234 list -tdev -gb -sg SG_ABCD -detail

**********************************************

symcfg -sid 123 show -pool F15_R5_02_1B -thin -detail

symconfigure -sid 123 -cmd "set pool F15_R5_02_1B, type=thin, max_subs_percent=400;" prepare

symconfigure -sid 123 -cmd "set pool F15_R5_02_1B, type=thin, max_subs_percent=400;" commit

**********************************************

Steps to dissolve tdev:

symconfigure -sid 1234 -cmd "unbind tdev 4444 from pool abcd_abcd_pool; " prepare

symconfigure -sid 1234 -cmd "unmap dev 4444 from dir all:all;" commit

symcfg -sid 1234 list -tdev -gb |grep -i u

symconfigure -sid 1234 -cmd "dissolve meta dev 4444 ;" commit

symconfigure -sid 1234 -cmd "delete dev 4444 ;4449;" prepare

***************************************************

symdisk -sid 124 list -failed

symconfigure -sid 1234 -cmd "unbind tdev 165 from pool F10_R6_05_2B; " commit
symdev -sid 1234 not_ready -dev 165

 symdev -sid 1234 write_disable -dev 165
 symdev -sid 1234 rw_enable -dev 165


symaccess -sid 123 list -type init -wwn 00000000000000000
symdev -sid 589 list -unbound -tdev -nomember   (to check unbound luns)

symcfg list (check storage device)

symmaskdb -sid 123 list assignment -dev 00C3F

symmaskdb -sid 123 list devs -wwn 000000000000000

symmask -sid 123 list logins -wwn 000000000000000 -v

symcfg -sid 123 list -dir 3d -p 0 -v

symmask -sid 123 -wwn 000000000000000 -dir 3d -p 0 set hba_flag on SPC2 -enable
symmask -sid 123 -wwn 000000000000000 -dir 14d -p 0 set hba_flag on SPC2 -enable
symmask -sid 123 refresh

symdev -sid 3197 list -diskgroup 10
symcfg -sid 3197 list -pool -thin -GB (check thin pools)

vi create_tdev
cat create_tdev

symconfigure -sid 3197 -f create_tdev commit

symconfigure -sid 123 -cmd "delete dev lunids" -commit


symaccess -sid id list logins -wwn wwpn

symaccess -sid id rename -wwn -alias gtams/fiki(name)

symaccess -sid 123 -wwn 0000000000000000 -dir

symaccess -sid 123 -ig dfdgdg


symconfigure -sid 3197 -f create_tdev prepare

symconfigure -sid 3197 -f disolve_meta prepare

symdev -sid 123 show lunid |grep

symaccess -sid 123 create -name abc -type storage

symaccess -sid 123 add -name abc -type storage devs 1004,

symaccess -sid 123 create view -name -def -ig abc -pg portgroupname

symaccess -sid 123 list view -v |grep -i gtams

symaccess -sid 123 delete view -name def

symaccess -sid

symsg show -sid 123 abc

symdisk -sid 123 list -failed (check failed disk)

symdisk -sid 123 list -isspare

symcfg -sid 124 list -env_data -v   (check environment status)


symaccess -sid 123 - name IG_gtams -type init ass -wwn wwpns


symsg -sid 123 -sg abc removeall -dev 1078,107C

symsg -sid 123 show abc

naviseccli

symcfg -sid 124 list -sa all
symaccess -sid 123 show view MV_ESX123 (to see host lun id)
symaccess -sid 123 show IG_esx123 -type init (to see wwn on IG)

symaccess -sid 123 list -dev 0818 -type storage (to see lun is mapped to which SG group)

symaccess

Specifically using for Vmax Allocation to do various operations on Masking view and related Groups under Vmax commands.

• symaccess -sid 1234 list
  List all Initiator, Port and Storage Groups Created for Array 1234
• symaccess -sid 1234 list -v
  List all Initiator,Port and Storage Groups Created for Array 1234 along with related Masking Views
• symaccess -sid 1234 list -type storage
  List all Storage Groups Created for Array 1234
• symaccess -sid 1234 list -type initiator
  List all Initiator Groups Created for Array 1234
• symaccess -sid 1234 list -type port
  List all Port Groups Created for Array 1234
• symaccess -sid 1234 list view
  List masking views Created for Array 1234 with related groups details
• symaccess -sid 1234 list assignment -dev 9A0:9AF
  Shows the masking details of devices from 9A0 to 9AF
• symaccess -sid 1234 -wwn xxxx replace -new_wwn yyyy
  Replace all occurance of wwn xxxx with yyyy in array 1234
• symaccess -sid 1234 list logins -wwn xxxx
  Check whether wwn xxx logged in to any of the FAs on array 1234.
• symaccess -sid 1234 list -type initiator -wwn xxxx
  Check whether the HBA WWN xxxx is a member of any Initiator Group.
• symaccess -sid 1234 list -type storage -dev AAA
  Check whether the HBA WWN xxxx is a member of any Initiator Group.
• symaccess -sid 1234 list no_assignments -dirport 12f:1
  Shows the devices are mapped to 12f:1 but not masked.
• symaccess -sid 1234 list -name MyGroup
  List all groups named MyGroup
• symaccess -sid 1234 list -name MyGroup -v
  List all groups named MyGroup and also shows the related Masking Views
• symaccess -sid 1234 list devinfo -ig MyInitiator
  List the details of devices assigned to the initiatorgroup MyInitiator
• symaccess -sid 1234 show MyStorageGroup -type storage
  Shows the contents of storage group MyStorageGroup Created on Array 1234
• symaccess -sid 1234 show MyInitiatorGroup -type initiator
  Shows the contents of initiator group MyInitiatorGroup Created on Array 1234
• symaccess -sid 1234 show MyPortGroup -type port
  Shows the contents of port group MyPortGroup Createdon Array 1234
• symaccess -sid 1234 show view MyView
  Shows the contents of view MyView Created on Array 1234
• symaccess -sid 1234 -f MyBackup.txt backup
  Creates a file MyBackup containing all the group and view information currently on the Symmetrix array 1234
• symaccess -sid 1234 -f MyBackup.txt restore
  Restores all the group
• symaccess -sid 1234 -type initiator -name Host1 create -wwn 1000000000000001
  Creates and initiator group called Host1 by adding the specified wwn
• symaccess -sid 1234 -type initiator -name Host1 rename -new_name Host2
  Rename the Initiator Gorup Host1 as Host2
• symaccess -sid 1234 -type port -name 3E0_4E0_13E0_14E0 -dirport 3e:0,4e:0,13e:0,14e:0 create
  Create the portgroup E0_4E0_13E0_14E0 with specified ports
• symaccess -sid 1234 -type port -name 3E0_4E0_13E0_14E0 rename -new_name 3E1_4E1_13E1_14E1
  Rename the Port Gorup 3E0_4E0_13E0_14E0 as 3E1_4E1_13E1_14E1
• symaccess -sid 1234 -type storage -name Host1 create devs AAA:AAB
  Create the storage group Host1 with specified range of devices
• symaccess -sid 1234 -type storage -name Host1 add devs AAA:AAB
  Create the storage group Host1 with specified range of devices
• symaccess -sid 1234 -type storage -name Host1 remove devs AAA:AAB
  Remove the device AAA to AAB from storage group Host1
• symaccess -sid 1234 -type storage -name Host1 remove devs AAA:AAB -unmap
  Remove the device AAA to AAB from storage group Host1 and also unmap from the FAs
• symaccess -sid 1234 -type storage -name Host1 rename -new_name Host2
  Rename the Storage Gorup Host1 as Host2
• symaccess -sid 1234 create view -name Host1_Allocation -sg Host1 -pg 3E0_4E0_13E0_14E0 -ig Host1
  Create a masking view combined with specified groups
• symaccess -sid 1234 view -name Host1_Allocation rename -new_name Host2_Allocation
  Rename name of view Host1_Allocation as Host2_Allocation
• symaccess -sid 1234 delete view -name Host1_Allocation
  Delete view Host1_Allocation.
• symaccess -sid 1234 delete view -name Host1_Allocation -unmap
  Delete view Host1_Allocation and also unmap all the device in associated storage group.
• symconfigure -sid 1234 list -freespace -units mb
  Shows the Formatted and Unformatted freespace in MegaBytes on array 1234
• symconfigure -sid 1234 -f command_file.txt preview
  Validates the syntax of the commands in ‘command_file.txt’ and also verify the configuration changes.
• symaccess -sid 1234 -name PG_1_2_15_16_E0_Group -type port -dirport 1e:0,16e:0 remove
  Remove ports 1e:0 and 16e:0 from port group ‘PG_1_2_15_16_E0_Group’.
• symaccess -sid 1234 -name PG_1_2_15_16_E0_Group -type port -dirport 1e:0,16e:0 remove
  Remove ports 1e:0 and 16e:0 from port group ‘PG_1_2_15_16_E0_Group’.
• symaccess -sid 1234 -name IG_Server_A -type initiator -wwn xxxx remove
  Remove HBA WWN ‘xxxx’ from Initiator Group ‘IG_Server_A’
• symaccess -sid 1234 -name IG_Servers -type initiator -ig IG_Server_A remove
  Remove Initiator Group ‘IG_Server_A’ from parent Initiator Group ‘IG_Servers’
• symaccess list hba
  Shows the wwn of the local HBA and the devices assigned to those.
• symaccess -sid 1234 view -name Host1_Allocation rename -new_name Host2_Allocation
  Rename name of view Host1_Allocation as Host2_Allocation
• symaccess -sid 1234 -f Total_views backup
  This command will backup all the Maksing Views information for array 1234 to file Total_views.
• symaccess -sid 1234 -f Total_views restore
  This command will restore all Masking view information for Vmax Array 1234 from file Total_views , which is earlier created by “backup” option.
• symaccess -sid 1234 -type initiator -name Host1 add -wwn 1000000000000002
  Add another HBA WWN to the existing Initiator group(IG) “Host1″.
• symaccess -sid 1234 -type port -name MyPorts add -dirport 6e:0
  Add an aditional port 6e:0 to the existing port group(PG) “MyPorts”.
• symaccess -sid 1234 -type initiator -name Host1_Host2_IG add -ig Host2_IG
  Add a child Initiator Group(Host2_IG) to the parent Initiator Group(Host1_Host2_IG).
• symaccess -sid 1234 show MyInitiatorGroup -type initiator -detail
  By including ‘-detail’ option will shows the Flag settings like ‘FCID Lockdown’ ,’Consistent Lun’.. for each WWN number in the initiator group.
• symaccess -sid 1234 show view MyView -detail
  This command is the best option to see both parent and child initiator groups( cascaded initiator group) and associated devices for a masking view.
• symaccess -sid 1234 show view Server_A_B_View -ig Server_B_IG
  Displays the content of view ‘Server_A_B_View’ with the WWN details of child-Initiator group ‘Server_B_IG’.
• symaccess -sid 1234 remove -login -wwn 1000000000000001 -dirport 12g:1
  Delete the wwn 1000000000000001 on port 6g:1 from the login history table of vmax 1234

symsg

Performs variuos operations like create,list,show,export,copy on Storage Groups(SG) in a Vmax Commands

• symsg -sid 1234 list
  Lists all the storage groups in Vmax array 1234 along with informations like whether the SG a member of Masking View and is a part of FAST Policy.
• symsg -sid 1234 list -v
  the -v options displays the member devices of Storage Groups along with other details given by list.
• symsg -sid 1234 create MyStorageGroup
  Create a new SG,’MySrorageGroup’ in Vmax Array 1234
• symsg -sid 1234 delete MyStorageGroup
  Deletes the empty SG ‘MySrorageGroup’ from 1234.The SG should not be associated with any Masking View.
• symsg -sid 1234 delete MySrorageGroup -force
  Deletes the SG ‘MySrorageGroup’ which contains devices but not associated with any Masking View.
• symsg -sid 1234 show MyStorageGroup
  Shows the devices in MyStorageGroup along with its Masking View and FAST Policy association status.
• symsg -sid 1234 export MyStorageGroup -file mystoragegroup.txt
  export the device information from SG to the text file.
• symsg -sid 1234 exportall -storagegroups.txt
  exports the device information from all the SGs from 1234 array to the text file storagegroups.txt
• symsg -sid 1234 import MyStorageGroup -file MystorageGroup.txt
  Create SG ‘MyStorageGroup’ from the earlier exported file MystorageGroup.txt.
• symsg -sid 1234 importall -file MystorageGroups.txt
  Create storage groups from the earlier exported file MystorageGroup.txt.Storage Group names will be created according to the names in text file.
• symsg -sid 1234 rename MyStorageGroup MyNewStorageGroup
  Rename SG MyStorageGroup to MyNewStorageGroup
• symsg -sid 1234 -sg MyStorageGroup ready
  Set the status of all devices in SG ‘MyStorageGroup’ to READY.
• symsg -sid 1234 -sg MyStorageGroup not_ready
  Change the status of all the devices in SG ‘MyStorageGroup’ from READY to NOT READY.
• symsg -sid 1234 -sg MyStorageGroup rw_enable
  Write enable all the devices in SG ‘MyStorageGroup’
• symsg -sid 1234 -sg MyStorageGroup write_disable
  Write Disable all the devices in SG ‘MyStorageGroup’