Raid group and LUN creation in EMC NS480

We are migrating our storage environment to the new Data center. As a result of which we had to replicate the storage environment from our current CX3-80 to the new NS-480. We had managed to get the excat snapshot of the existing setup in and excel sheet with raid type, lun number, raid group, lun size etc. We started like this:
1. The code 28 of the Flare on the NS-480 backend supports the navisecli as default not the classic navicli. So we had to create the security file for the user nasadmin on the Celerra control station in order to access the Clariion. We had created the user nasadmin on the Clariion as well.

/nas/opt/Navisphere/bin/naviseccli -AddUserSecurity -scope 0 -password -user nasadmin

2. We had only about 14 raid groups so we created them manually one comand at a time. This is just one example

/nas/opt/Navisphere/bin/naviseccli -h SPA createrg 101 0_1_0 1_1_0 0_2_0 1_2_0 0_1_1 1_1_1 0_2_1 1_2_1 -rm no -pri high -raidtype R10

3. Once the raid groups are in place, we had a simple script in place to bind the luns to the raid group.

---- Script starts -----
#!/bin/bash
FILE=/home/nasadmin/NewLun/Book1.csv
SP=a
while read line; do
RT=`echo $line awk -F\ '{print $1}'`
SZ=`echo $line awk -F\ '{print $2}'`
NU=`echo $line awk -F\ '{print $3}'`
RG=`echo $line awk -F\ '{print $4}'`
if [ "$SP" = "a" ]; then
SP=b
else
SP=a
fi
echo "echo $RT-$SZ-$NU-$RG" >> /home/nasadmin/LUN.sh
echo "/nas/opt/Navisphere/bin/naviseccli -h SPA bind $RT $NU -rg $RG -sp $SP -sq gb -rc 1 -wc 1 -cap $SZ" >> /home/nasadmin/LUN.sh
done< $FILE
---- Script end ----

The file Book1.csv is a pipe seperated list with raid type,lun size,lun number and raid group number. The lun ownership alternates between spa and spb.
That's done. Simple isn't it.

Comments

Post a Comment

Popular posts from this blog

zpool and power path partial compatibility

Is power path fully supported with zpools, no. It's partial. You can have the pseudo devices assigned to a pool but it uses the native ctd disk only. Recently I lost 2 paths from the vnx array to m9000 server running Solaris 11.1. When I ran the zpool status -x command some of the pools were online while some of them were un available. Power path was reporting 2 paths only but it was active. So ideally the zpools should be online. But it's not. I enabled the remaining 2 paths and all became online. Internally the pools were pointing to one of the ctd devices that belonged to dead path and it was not coming online. Also few of the emcpower devices were renamed, so I had to do zpool import -d with the alternate disk. It seems power path is not completely supported now but may become in future.
Read more

Recoverpoint replication reporting with vmax splitter

Guys, Have you ever thought of automating the RP replication status and send status via email or post it to any reporting platform. Since the splitter impacts the VMAX FA's and there is an overhead of 13% on the utilization its good idea to see if the replication is driving the utilization of vmax FA. There are ways of pulling iops/read/write using symstat but its utilization (Director CPU utilization etc) which plays a significant role. As it crosses 80% we start seeing the increase in device response time. However, to measure FA utilization we will have to go through SMAS UI then pull out the reports. Its manual effort. But there is a way to automate it through REST API. You can get the details what type of objects are supported by pointing to : https://smc server :8443/univmax/restapi Coming to the point, getting recoverpoint consistency group status fully automated doesn't seems to be tough. Lets get through the steps. 1. Hash your SSH keys of the unix host to ...
Read more

Weird problem post power maintenance, no Powerpath pseudo name for Luns

We had the scheduled power maintenance activity in our data center. Every team was notified and we powered doen the servers through cron job. The servers were powered down first then storage (CX-380). And the reverse was followed during startup. After the power shutdown, the SAN was booted up. we forgot to disable the the snapshots. They were still active. Once it came up, the sessions were not there, but snapshot was active. Tried to deactivate the snapshot, failed with the error the "Failing Command: K10SnapCopyAdmin DBid 0 Op 1051. 71 00 80 43" Tried to create a session and attach the snapshot to the session, still unable to deactivate it, neither was able to attach to any other session. Looked at powerlink: It says the command issued to the snapshot is not owned by the SP. I trespassed all the snapshot source lun to SPA, and then tried to deactivate, nothing happened. Rebooted the SP's one by one through the management console. (http:/SP-IP/setup) Then I was able to...
Read more