Start a Conversation

Unsolved

This post is more than 5 years old

2281

April 8th, 2008 11:00

LUN Lock ?

When I map a new LUN on a DMX-3 or DMX-4 the LUN shows up behind the FA as it should but then has a strange icon associated with the LUN. I have never seen this on the DMX-1000 or the Symm5 before, only the DMX-3 and DMX-4. That does not mean it has not occurred, but I think I would have noticed it before now.

It looks like a small red lock to me but I am not sure. I can¿t find any documentation on it. The icon eventually just disappears by itself and I see nothing in the ECC log about it either.

21 Posts

April 8th, 2008 11:00

btw..its ECC 6.0, sorry

2 Intern

 • 

385 Posts

April 9th, 2008 04:00

We had this exact same issue - it will prevent you from making any changes until a discovery is run and removes this lock. You need to patch your Symmetrix/SDM agent - the latest patch should fix your issue.

We are at agent version 6.0.0,0.336 and the issue is resolved.

2 Intern

 • 

5.7K Posts

April 9th, 2008 05:00

So this a lock 9 then ?

2 Intern

 • 

385 Posts

April 9th, 2008 05:00

This is not a lock you can release from the command line - I believe it is a bug where the ECC store "thinks" there is still a lock when it actually has been released. You can manipulate the device from the command line or SMC - only ECC chokes on this "lock" being set.

2 Intern

 • 

5.7K Posts

April 9th, 2008 07:00

Ah ! I knew about reservatiuons, but I never saw this happening in ECC.

Correct me if I'm wrong, but you cannot make reservations in ECC, but you can by using SMC ? But after making the reservations it will be visible in ECC.

Ok....

2 Intern

 • 

385 Posts

April 9th, 2008 07:00

Quinton is correct on his commands, but I will confirm that ECC 6.0 has a bug with certain versions of microcode where the lock WILL NOT be released from ECC itself.

You can run all of the symdev/symconfigure commands and will find that no lock or reservation exists - the only fix was updating the Symmetrix/SDM agent.

In fact until the patch was released the "work-around" was to disable the reservation code in Solutions Enabler to prevent ECC from confusing itself :)

With the reservation set you will not see the device in any masking or configuration screens which is what you would want/expect - unless you did not set the reservation intentionally ;)

21 Posts

April 21st, 2008 04:00

Thanks to all the patch worked as advertised

2 Intern

 • 

5.7K Posts

April 24th, 2008 00:00

Could you please mark the correct answer as "correct" and helpful ones with "helpful" ?
No Events found!

Top