You probably shoud open a case with EMC support on this and have them sort it out for you.  However, you may want to start by restarting the management server on each SP.  This is not the same as rebooting the SPs.  If you browse to http:// _ip_address>/setup  After logging in, there is a button for restarting the management server.  You will need to do both SPs seperately.  You will lose access to navisphere for a while until the services come back online.  This may help clear out the snapshot status.  If not you may have to reboot the SPs themselves, but I would defer to support on that.  I found the following Primus article about a similar issue, but it seems like this isn't your actual problem.  I'm pasting it here just in case...  ID: emc155687Domain: EMC1Solution Class: 3.X Compatibility  Fact       Product: CLARiiON CX Series Fact       EMC SW: Navisphere Manager Fact       EMC SW: SnapView Fact       EMC Firmware: FLARE Release 19 patch 40  Symptom    Snap activation stops session.  Symptom    Script running on the host is unable to mount a snapshot with "active" status, which is actually "inactive."  Change     FLARE was upgraded from Release 19 patch 30 to patch 40. The problem existed even before FLARE was upgraded but with lesser frequency.  Cause      The problem occurs when SnapView returns a finish signal to navicli before the snapshot itself has been activated. During this time when the snapshot is not activated and if an I/O request is made to it, the session will be stopped. EMC Engineering confirmed that this known FLARE issue has been fixed in the Release 24 code.  Fix        Upgrade the array to FLARE Release 24.  A workaround is to put a "wait" step in the script so that the snapshot is activated prior to any I/O request is made to it. This will prevent the server from accessing the snapshot too early.  Note       The customer site has two CX500 arrays. The problem array is the target for synch mirrors from the first array.  A backup host connected to the problem array is running Novell NetWare 5.70.05. Multiple SnapView sessions and snapshots are running properly on the problem array except one particular snapshot that stops the session when activated. A script running on the Management Server manages all snapshots. Navisphere shows the status of the snapshot as "active," but attempting to manually deactivate it results in an error stating that it is already inactive. Restarting the Management server fixed the problem temporarily.
Hi,  On a CX500 running FLARE 19, I have a really strange problem.  Using both 'naviseccli' and the Navisphere GUI, I have a snapshot called 'backup_snap_58' which shows as 'active' and associated with a session that doesn't exist.  I can't stop the session (it isn't there) and I can't deactivate the snapshot, because it thinks it's part of a session.  To make things even more interesting, when I get 'properties' on the active snapshot in the GUI, the properties window says that it's inactive, though the entry in the snapshots window displays it as active.  Also, if I use 'navicli' instead of 'naviseccli', there is no problem, and I can use the snapshot normally.  Using 'naviseccli', it won't allow me to work with the snapshot because it's wedged in this state.  Also, at first SP2 had the problem but SP1 did not, but after poking at it both of them say the same thing.  Anybody know how to get in there and get this thing busted loose?  Thanks,  Marcus
Strange problem with snapview snapshot