EMC – Using naviseccli to expand a pool

I haven’t banged on about how much I like naviseccli in a little while. I was reading a white paper on FAST VP in the new VNX series recently, and came across the storage pool -expand command. This isn’t so exciting, but the -skipRules option was intriguing. It seems you would use this if you didn’t want to follow all of the rules associated with a normal pool expansion. I inferred from the white paper that by default a FAST VP pool will automatically redistribute its LUNs across the new disks. This may be non-optimal if you’re in the middle of a busy period on the array, and if you don’t want this to happen, you should use the skipRules option.  Note that this is for Release 5.33. If I’ve misunderstood this I’m happy to be corrected.

In any case, here’s an example of how to expand a pool using naviseccli.

storagepool -expand -id poolID| -name poolName-disks disksList [-rtype raidType[-rdrivecountdrivecount]][-initialverify yes|no][-skipRules] [-o]

The RAID types you can select are r_5, r_6 and r_10. This is important if you already have disks of a certain tier type in the pool. The capacity tier (NL-SAS drives) uses RAID 6, the performance tier (SAS drives) uses RAID 5, and the extreme performance tier (Flash drives) is RAID 1/0.

naviseccli -h SP_IPaddress storagepool -expand -id 10 -rtype r_6 -disks 0_2_0 0_2_1 0_2_2 0_2_3 0_2_4 0_2_5 0_2_6 0_2_7 –o

EMC Elect 2014


I am very pleased to say that I’ve been once again selected to participate in EMC Elect 2014. For those of you who haven’t heard, EMC Elect is an EMC programme similar in style to Microsoft’s MVP programme and VMware’s vExpert recognition. You can find out a little more about it here. I’m stoked to be part of this, and am looking forward to what I can give back to the community through my participation in EMC Elect. The official list is here, and the people I know on it are all passionate about what they do.

But enough from me, check out the write-up by Dave Henry here, as well as  Cody Hosterman’s piece here.

Update: Here’s a more comprehensive list of links covering EMC Elect, primarily from Elect members themselves.

EMC – DIY Heatmaps – Updated Version

I’ve patched the DIY Heatmaps script, fixing a problem with the table names generated in the database files. You can download it from the Utilities page.




EMC – CX POST output

Following on from my two previous posts on the CLARiiON POST and troubleshooting – here’s what a CX POST looks like when viewed from SP B.


Note that the chassis and disk WWN seeds match – this is useful if you’ve moved multiple arrays (during a data centre move, for example) and didn’t take note of the SP and DPE pairings (tsk, tsk). Note also that it’s looking at disks 1 and 3 – these are the boot disks for SP B (SP A uses disks 0 and 2).


Note that you never get to a point where you can login via the serial console – it’s really only used for early diagnostics and monitoring.


EMC – CX Troubleshooting – Part 2

In my previous post I talked about how error codes on a CX POST actually mean something, and can assist in your troubleshooting activities. But what does that stupid alphabet soup mean when you see a CLARiiON boot up?


Turns out all of those crazy letters mean something too, and you can refer to this PDF file I put together to work out at what point the array is failing its tests. Please note that I haven’t verified if these apply to the CX3, CX4 or VNX.

EMC – CX Troubleshooting – Part 1

Despite that fact that I’ve written over 270 posts in the past 5 years on this blog, one of my most popular posts has been my article on CLARiiON CX700 FLARE Recovery. I’ve been assisting someone via e-mail over the past month or so who was having problems getting a CX700 he’d acquired to boot. He’s a smart guy, but hasn’t used a CLARiiON before. And I was working from muscle memory and unable to eyeball the console for myself. So it was an interesting challenge, combined with varying time zones.

Anyway, I thought it would be interesting to do one or two posts on some basic CX stuff that may or may not assist people who are doing this for the first time. This isn’t going to be a comprehensive series but rather a few notes and examples as I think of them.

In this instance, my correspondent had a terminal connection to the array, and was seeing the following output:

EndTime: 07/29/2013 04:11:59
.... Storage System Failure - Contact your Service Representative ...
ErrorCode: 0x00000142
Device: LCC 0 UART
Description: LCC slot indicator Error!
Error detected when handling LCC READ command
ErrorTime: 07/29/2013 04:11:38

Basically, the key thing was that error code ending in 142. According to this list of CX error codes I dug up, it indicates some sort of problem with the LCC. What wasn’t clear until much later, unfortunately, was which SP my correspondent was connected to. It turned out that SP A was faulty and needed to be replaced. There’s also a LCC 0 UART Sub-Menu available from the Diagnostics section of the Utility Partition. You can perform LCC diagnostics at this point to verify the POST errors you’re seeing. In short, pulling SP A allowed the system to boot, and error codes mean something to someone. Please note that I haven’t verified if these apply to the CX3, CX4 or VNX.

EMC – DIY Heatmaps – Updated Version

Mat has patched the DIY Heatmaps script, fixing a problem with current model VNXs and updated naviseccli whereby using the –get_drive_type –display_drive_type options of the heatmap script would cause a JavaScript error in the resulting heatmap HTML file. You can download it from the Utilities page.

EMC – DIY Heatmaps – Updated Version

Mat has updated the DIY Heatmaps script to support SAS-type Flash drives. Download it from here, take it for a spin and let us know what you think. And tell your friends.

EMC – Unisphere / Analyzer weirdness

Mat came across a weird problem with Unisphere the other day while he was trying to retrieve some nar files for EMC to look at. Normally I like to post solutions up here but in this case I don’t know what the solution is. Previously, it was my understanding that we could retrieve access multiple nar files from multiple arrays in the same domain via the one Unisphere session. This doesn’t seem to be the case anymore. As background, we run 4 CX4-960s and a CX4-240 in a single Unisphere domain. These arrays were all upgraded to 30.525 recently.

Normally, I’d login to one of the arrays and go to Monitoring -> Analyzer and then Retrieve Archive. So far, so good.


But when I change the “Retrieve Archive From:” selection, I get the following.


Notice that I’m trying to retrieve files from the array serial number 0260, but I’m still seeing 0679, even after hitting Refresh. Maybe it’s Unisphere on that array, let’s try another.


Ok, I’ve logged on to array 0260 and can now retrieve the files I want. But do I still get weird behaviour? Yes, yes I do.


If anyone has any ideas, I’m all ears. I think Mat is going to log a call at some stage.


Dell EqualLogic Masterclass 2013 is coming up

DanMoz posted on his blog recently that Dell is running another series of EqualLogic Masterclass sessions in the near future. I attended these last year and found the day to be very useful (you can read my posts here, here and here). Register here.