Unsolved
This post is more than 5 years old
2 Posts
0
491
December 11th, 2013 02:00
AX4 LUNS that refuse to go!
Hi All,
I've been given a Clariion AX4-5 which came about as inventory from an acquisition. It orginally had the the IP addresses of 'old company' on it, so using the forums, I figured out how to change the IPs of SPs A&B to get the system online. I'd like to clear the unit down and integrate this into a VMWare cluster that I'm building, but I'm having trouble deleting the LUNs on this unit.
The goal is to remove the old data on this unit and 'start afresh' to integrate it into my VMWare cluster.
Here's a shot of the current state of the unit from Navisphere 6:
As you can see, there aren't any storage groups, and I'd like to get rid of the RAID groups, and the LUNS in the reserved pool.
I'm getting the age old error of "LUN xx - Being used by a feature of the storage system" when i try to remove it from either the RAID group or the reserve pool:
$> naviseccli -h 1.1.1.1 -User admin -Password password -Scope 0 getlun -xxxx 200 -stack
Listed Driver: K10SnapCopyAdmin
So they're being held by SnapCopy - a common issue. The issue though is that I can't see how to disable snap copy to release them.
I've seen in other threads that you use the NST to remove the service, but I understand that this has been superceded by the USM?
Any help is gratefully appreciated!
UPDATE: I accessed the array using USM, and tried to remove the SnapView service - the process fails on the check scripts portion, with a fairly generic error saying the scripts failed. I've rebooted both SPs, same issue. Any ideas?
christopher_ime
4 Operator
•
2K Posts
0
December 11th, 2013 11:00
Open up the "Sessions" folders under "SnapView" as seen in your screenshot. The Reserved LUNs are "Allocated" (versus "Free") meaning they are participating in an active SnapView session. You won't be able to remove them from the Reserved LUN Pool until the status is "Free" (as seen with LUN 215 which btw is the only LUN you would be able to currently remove from the Reserved LUN Pool).
Let's start there, the lack of storage groups also makes it likely they aren't also activated via a Snapshot (container) which is how they are presented to hosts.
It is also possible (not seen in your screenshot), but SnapView snapshot technology is also the foundation to MirrorView/A and SAN Copy incremental so we may need to dig a little further but again, let's start at the SnapView session folder and work our way up as only as needed which would include: Snapshot (Names), Mirrorview/A mirrors, SAN Copy (incremental) sessions, etc.
superhands
2 Posts
0
December 11th, 2013 16:00
Thanks very much - session are as follows:
If i try to stop the session either via the GUI or with:
$> NaviSECCli.exe -h 10.134.20.90 snapview -stopsession rvukepo-0009-21939
Not a lot happens!