Simple VMAX device allocation steps

Here we will discuss the basics of VMAX, a new device allocation to a new host. For a new host, we will have to create a Masking View (we will use MV or View later in this post), which will be containing Storage Group ( SG – Containing all the devices to be presented to the host ), Port Group ( PG -Containing the VMAX director ports through which the host will access the devices ) and Initiator Group ( IG – containing the host HBA WWNs ). Lets look more in to the configuration via symcli.

Read more

Let’s assume we are using Thin Devices with a pool named T_Pool_1 already present in our VMAX.We will create 2 TDEVs devices first. The command will be,

symconfigure -sid 1234 -cmd ” create dev count=2, size=54614, emulation=FBA, config=TDEV;” commit -v

The new devices AAAA and AAAB  of 50GB are now created. Now we will bind these to the pool T_Pool_1. The commad we will use,

symconfigure -sid 1234 -cmd “bind tdev AAAA:AAAB to pool T_Pool_1;” commit -nop -v

 

 

Now we are all set to allocate these devices to the server. But it requires the View created. We are assuming the zoning is done and the HBAs are having good connectivity with the VMAX. We can verify this by running the command,

symaccess -sid 1234 list logins -wwn 1xxxxxxxxxxx  # where 1xxxxxxxxxxx is the HBA WWN

If the HBA is logged in, we are good.Now we will create the IG first.

symaccess -sid 1234 -type init create -name BForum_IG -f WWN_file

Where the WWN_file should have the WWNs mentioned in the form,

WWN:1xxxxxxxxxxx  

WWN:2xxxxxxxxxxx  

If we need to a WWN later we can do it by running,

symaccess -sid 1234 -name BForum_IG -type init -wwn 3xxxxxxxxxxx add

Now we have the IG created. The initiators in IG will be listed with their WWN only. If we need to rename to make it human-readable, we can use the command –

symaccess -sid 1234 -wwn 1xxxxxxxxxxx  rename -alias BForum_HBA1/1xxxxxxxxxxx 

The next step, we will create the PG.

symaccess -sid 1234 create -name BForum_PG -type port -dirport 7f:0,9f:0

 

 

Now we have the PG created with the FA port 7F:0 and 9F:0 added to it. Now we are left with the SG. We will create it with the devices AAAA and AAAB added to it,.

symaccess -sid 1234 create -name BForum_SG -type storage -devs AAAA:AAAB 

Yes, we have all the groups created. Now we will create the View,

symaccess -sid 1234 create view -name BForum_MV -ig BForum_IG -pg BForum_PG -sg BForum_SG

That’s it..! The view is set with the host and devices added to it.Now the server will be able to discover the devices.

Backup is of top priority for your production data and VMs. We recommend Nakivo for your VMware, Hyper-V and EC2 instances backups.

That was easy, right ? Hope you enjoyed it.You may find more EMC VMAX posts here.

 

Initializing a Cisco MDS FC switch

Trouble in initializing brand new Cisco MDS FC switch ? This post may help you. This post here discusses the procedure to initialize a new FC switch.

MDS_9124

You have to connect the Console cable with Read more

the serial (COM) port on your laptop/desktop. You may use any terminal emulation utility such as Putty, Hyper Terminal etc.. and should use the default settings for serial connection (9600 baud,8 data bits,1 stop bit,No parity). Now you are all set to receive get the serial console.

 

Now you can connect the power and switch the switch ON. Once the switch is powered ON and booted up, you will asked to set the password for administrator. You should be setting a strong password otherwise the entered one will be rejected.

Once this is done, you will be prompted whether or not to continue with entering the configuration data. You can proceed with yes once you have the necessary information.

 

 

Press Enter at anytime to skip a dialog. Use ctrl-c at anytime
to skip the remaining dialogs.

Would you like to enter the basic configuration dialog (yes/no): yes

Create another login account (yes/no) [n]:

Configure read-only SNMP community string (yes/no) [n]:

Configure read-write SNMP community string (yes/no) [n]:

Enter the switch name : B-Forum-SW01

Continue with Out-of-band (mgmt0) management configuration? (yes/no) [y]:

Mgmt0 IPv4 address : 12x.23x.234.123

Mgmt0 IPv4 netmask : 255.255.255.0

Configure the default gateway? (yes/no) [y]:

IPv4 address of the default gateway : 12x.23x.234.1

Configure advanced IP options? (yes/no) [n]:

Enable the ssh service? (yes/no) [y]:

===== Output shortened =====

 

 

The switch will be showing all the parameters going  to be set on the switch. If you need to edit any of them, you may enter yes for the query to edit. If you are OK with the values, you can go for the default , no.You can save the configuration by entering yes to the next query.

Would you like to edit the configuration? (yes/no) [n]: no

Use this configuration and save it? (yes/no) [y]: yes

The switch will reboot and the new configuration will take affect. Yes, we are done..

If you wish to reset these values later, you may try the command setup. You will be receiving the same questionnaire as you did for the first time initialization.

You may click here for SAN switch related posts.

Hope this post was helpful for you. Comments are always welcome…

 

 

Scanning new LUNs from Celerra/VNX File

Once you have provisioned a new LUN (or Symmetrix device), you have to scan for this LUN from Celerra/VNX file components to make use of it at the File side – for making filesystem and then CIFS share/ NFS export. Here we are discussing the simple steps to scan the new LUN.

1. From the GUI – Unisphere Manager

Read more

Login to the Unisphere manager console by entering the control station IP address in web browser. Select the system you have to scan for new LUN from top left drop-down. Navigate to System > System Information tab.You will be given with a Rescan All Storage Systems button there which will do the rescan for you.

RescanOnce rescan is completed, the devices/LUNs will be visible under the disks and space will be available as the potential storage for the respective pool (Storage Pool for file).

 

 

 2. Now via CLI

From the CLI we have to scan for the new LUN on all data movers. We will use the command server_devconfig. We can run the command for each DM (data mover) separately starting with the standby one first. The syntax for a dual data mover system will be,

server_devconfig server_3 -create -scsi -all      # for standby DM

server_devconfig server_2 -create -scsi -all      # for primary DM

This is the recommended way but I have never heard of any issue occurred while scanning across all DMs at a time.For a multi DM system if we want to scan for all data movers in single command, the only change will be just ALL in the place of the server name.

server_devconfig ALL -create -scsi -all      # for all DMs

After the successful scanning you can find the new devices/LUNs at the bottom of the  output of nas_disks -list command.

$nas_disks -l

id   inuse  sizeMB    storageID-devID           type     name          servers

1     y      11263    CK1234512345-0000    CLSTD   root_disk     1,2

============== Shortened output ==============

18    n     51200    CK1234512345-0010    CLSTD   d18             1,2

 

You can verify the increased space of the respective pool by running the nas_pool -size [Pool Name].

Hope this post helped you. For more Celerra/VNX posts click here

 

Basic healthcheck commands for EMC Celerra/VNX

For the Celerra or a VNX file/Unified system we can verify the system health by running the nas_checkup command.  This will do all the checks including the file and block hardware components, configuration checks – NTP, DNS etc…

A sample output is given below,

[[email protected] ~]$ nas_checkup

Check Version:  7.1.72-1 Read more

Check Command:  /nas/bin/nas_checkup
Check Log    :  /nas/log/checkup-run.123456-654321.log

————————————-Checks————————————-
Control Station: Checking statistics groups database………………….. Pass
Control Station: Checking if file system usage is under limit………….. Pass
Control Station: Checking if NAS Storage API is installed correctly…….. Pass
Control Station: Checking if NAS Storage APIs match……………………  N/A
Control Station: Checking if NBS clients are started………………….. Pass
Control Station: Checking if NBS configuration exists…………………. Pass
Control Station: Checking if NBS devices are accessible……………….. Pass
Control Station: Checking if NBS service is started…………………… Pass
Control Station: Checking if PXE service is stopped…………………… Pass
Control Station: Checking if standby is up……………………………  N/A
Control Station: Checking integrity of NASDB…………………………. Pass
Control Station: Checking if primary is active……………………….. Pass
Control Station: Checking all callhome files delivered………………… Pass
Control Station: Checking resolv conf……………………………….. Pass

 


Control Station: Checking if NAS partitions are mounted……………….. Pass
Control Station: Checking ipmi connection……………………………. Pass
Control Station: Checking nas site eventlog configuration……………… Pass
Control Station: Checking nas sys mcd configuration…………………… Pass
Control Station: Checking nas sys eventlog configuration………………. Pass
Control Station: Checking logical volume status………………………. Pass
Control Station: Checking valid nasdb backup files……………………. Pass
Control Station: Checking root disk reserved region…………………… Pass
Control Station: Checking if RDF configuration is valid………………..  N/A
Control Station: Checking if fstab contains duplicate entries………….. Pass
Control Station: Checking if sufficient swap memory available………….. Pass
Control Station: Checking for IP and subnet configuration……………… Pass
Control Station: Checking auto transfer status……………………….. Fail
Control Station: Checking for invalid entries in etc hosts…………….. Pass
Control Station: Checking for correct filesystem mount options…………. Pass
Control Station: Checking the hard drive in the control station………… Pass
Control Station: Checking if Symapi data is present…………………… Pass
Control Station: Checking if Symapi is synced with Storage System………. Pass
Blades         : Checking boot files………………………………… Pass
Blades         : Checking if primary is active……………………….. Pass
Blades         : Checking if root filesystem is too large……………… Pass
Blades         : Checking if root filesystem has enough free space……… Pass
Blades         : Checking network connectivity……………………….. Pass
Blades         : Checking status……………………………………. Pass
Blades         : Checking dart release compatibility………………….. Pass
Blades         : Checking dart version compatibility………………….. Pass
Blades         : Checking server name……………………………….. Pass
Blades         : Checking unique id…………………………………. Pass
Blades         : Checking CIFS file server configuration………………. Pass
Blades         : Checking domain controller connectivity and configuration. Pass
Blades         : Checking DNS connectivity and configuration…………… Pass
Blades         : Checking connectivity to WINS servers………………… Pass
Blades         : Checking I18N mode and unicode translation tables……… Pass
Blades         : Checking connectivity to NTP servers…………………. Warn
Blades         : Checking connectivity to NIS servers…………………. Pass
Blades         : Checking virus checker server configuration…………… Pass
Blades         : Checking if workpart is OK………………………….. Pass
Blades         : Checking if free full dump is available………………. Pass
Blades         : Checking if each primary Blade has standby……………. Pass
Blades         : Checking if Blade parameters use EMC default values……. Info
Blades         : Checking VDM root filesystem space usage………………  N/A
Blades         : Checking if file system usage is under limit………….. Pass
Blades         : Checking slic signature…………………………….. Pass
Storage System : Checking disk emulation type………………………… Pass
Storage System : Checking disk high availability access……………….. Pass
Storage System : Checking disks read cache enabled……………………. Pass
Storage System : Checking disks and storage processors write cache enabled. Pass
Storage System : Checking if FLARE is committed………………………. Pass
Storage System : Checking if FLARE is supported………………………. Pass
Storage System : Checking array model……………………………….. Pass
Storage System : Checking if microcode is supported……………………  N/A
Storage System : Checking no disks or storage processors are failed over… Pass
Storage System : Checking that no disks or storage processors are faulted.. Pass
Storage System : Checking that no hot spares are in use……………….. Warn
Storage System : Checking that no hot spares are rebuilding……………. Warn
Storage System : Checking minimum control lun size……………………. Pass
Storage System : Checking maximum control lun size…………………….  N/A
Storage System : Checking maximum lun address limit…………………… Pass
Storage System : Checking system lun configuration……………………. Pass
Storage System : Checking if storage processors are read cache enabled….. Pass
Storage System : Checking if auto assign are disabled for all luns………  N/A
Storage System : Checking if auto trespass are disabled for all luns…….  N/A
Storage System : Checking storage processor connectivity………………. Pass
Storage System : Checking control lun ownership……………………….  N/A
Storage System : Checking if Fibre Channel zone checker is set up……….  N/A
Storage System : Checking if Fibre Channel zoning is OK………………..  N/A
Storage System : Checking if proxy arp is setup………………………. Pass
Storage System : Checking if Product Serial Number is Correct………….. Pass
Storage System : Checking SPA SPB communication………………………. Pass
Storage System : Checking if secure communications is enabled………….. Pass
Storage System : Checking if backend has mixed disk types……………… Pass
Storage System : Checking for file and block enabler………………….. Pass
Storage System : Checking if nas storage command generates discrepancies… Pass
Storage System : Checking if Repset and CG configuration are consistent…. Pass
Storage System : Checking block operating environment…………………. Pass
Storage System : Checking thin pool usage…………………………….  N/A
Storage System : Checking for domain and federations health on VNX……… Pass

 

 

All the warnings, errors and information will be listed at the  bottom of the output with corrective action if required.

The below commands will help you to collect the necessary information while registering a Service Request etc…

/nas/sbin/model    # to find the VNX/Celerra Model

/nas/sbin/serial    # to find the VNX/Celerra Serial number

nas_server -l       # to list the Data movers and their status.  A sample result is as below.

———————————————–

[email protected] ~]$ nas_server -l

id      type  acl  slot groupID  state  name

1        1    0     2              0    server_2

2        4    0     3              0    server_3

[[email protected] ~]

———————————————–

 /nas/sbin/getreason       # to see the Data movers and Control Station boot status. A sample result is as below.

———————————————–

[[email protected] ~]$ /nas/sbin/getreason

10 – slot_0 primary control station

5 – slot_2 contacted

5 – slot_3 contacted

———————————————–

Control station status should be 10 and Data movers should be 5 with state contacted for a healthy system.

And finally, collecting the logs – the support materials.

/nas/tools/collect_support_materials will help you in collecting the logs. The logs will be saved under /nas/var/emcsupport. The file location and name will be displayed at the bottom of the command output. You can use FTP/SCP tools to copy the file to your desktop.

More in coming posts…

You may refer this post for reading how to collect the SP collects from control station CLI. Hope this post helped you. For more Celerra/VNX posts click here .

 

VNX/Celerra – SP Collects from Control Station command line..

Personally, I prefer Control Station CLI to get the SP Collects for a VNX/Celerra with attached Clariion, quicker..! Opening the Unisphere Manager takes time, of course it is Java enabled. Here let us see how this can be done via the CLI.

Logs.Open an SSH/Telnet session to the control station and login. Read more

You have to navigate to /nas/tools. Basic Linux command “cd /nas/tools” will do this. Once you are in tools, there will be a hidden script get_spcollect which is used to collect the SP Collects (will have to use ls -la for listing it as it is a hidden file).

Now we have to use the below command to execute the script.

./.get_spcollect  [don’t miss the dots before and after the /]

This will run the SPCollects script and gather all the logs and create a single SPCOLLECT.zip file. A sample output will be as below.

 

 

[[email protected]_NAME ~]$ cd /nas/tools/
[[email protected]_NAME tools]$ ./.get_spcollect

Generating spcollect zip file for Clariion(s)

Creating spcollect zip file for the Service Processor SP_A. Please wait…

spcollect started to pull out log files(it will take several minutes)…
Wait until new _data.zip file size becomes final(it will take several minutes)
Retrieving new _data.zip file…
   — truncated output–
Wait until new _data.zip file size becomes final(it will take several minutes)
Retrieving new _data.zip file…
spcollect zip file SYS_SERIAL_SPA_DATE_TIME-STAMP_data.zip for the Service Processor SP_A was created
Creating spcollect zip file for the Service Processor SP_B. Please wait…

spcollect started to pull out log files(it will take several minutes)…
Wait until new _data.zip file size becomes final(it will take several minutes)
Retrieving new _data.zip file…
   — truncated output–
Wait until new _data.zip file size becomes final(it will take several minutes)
Retrieving new _data.zip file…
spcollect zip file SYS_SERIAL_SPB_DATE_TIME-STAMP_data.zip for the Service Processor SP_B was created

Deleting old SPCOLLECT.zip file from /nas/var/log directory…
Old SPCOLLECT.zip deleted
Zipping all spcollect zip files in one SPCOLLECT.zip file and putting it in the /nas/var/log directory…
  adding: SYS_SERIAL_SPA_DATE_TIME-STAMP_data.zip (stored 0%)
  adding: SYS_SERIAL_SPB_DATE_TIME-STAMP_data.zip (stored 0%)
[[email protected]_NAME tools]$

 

 

Now, as mentioned towards the end of the output , the logs – SPCOLLECT.zip will be located at /nas/var/log directory. How can we access it ? I use WinSCP software to collect it via SCP. Enter the IP address/CS name and login credentials. Once the Session is open, navigate to /nas/var/log on the right panel and your required directory on the left. Select the log file and click F5 (or select copy)

WINSCP

 

That’s it..! You have the SPCollects on your desktop. Quite faster , right ? Hope this post helped you. For more Celerra/VNX posts click here

 

1 2