4 Operator

 • 

2.8K Posts

July 30th, 2008 09:00

The command sounds good to me .. however before releasing the lock I'd check who is holding the lock .. Anybody else running symconfigure commands from a host ?? Maybe you can check with symaudit and search for symconfigure actions running elsewhere...

If you are completly sure that it's good to release the lock, you already have the right command.. :-)

1 Rookie

 • 

12 Posts

July 30th, 2008 10:00

I tried to release the lock using -force but the lock is still not removed. Below is the output from the command.

C:\Program Files\EMC\SYMCLI\bin>symcfg -sid 128 -lockn 15 release -force

Interrogating Configuration Server for config change session information

The configuration change session cannot be interrogated; may be terminated.

C:\Program Files\EMC\SYMCLI\bin>symcfg -sid 128 list -lock -lockn all

Symmetrix ID: 000xxxx00128

S Y M M E T R I X L O C K S

Lock Lock Lock Time
SymmID Attachment Status Number Usage Held (Sec)

000xxxx00128 Local Locked 15 Config Change 8325

Message was edited by:
Stefano Del Corno

removed symmetrix sn

4 Operator

 • 

2.1K Posts

July 30th, 2008 10:00

I've only run into this once (a config change lock that I couldn't get released) and I had to call EMC Support to dial in and release it for me.

I actually used to have to do this a fair bit (releasing locks manually) but now that we do most of this work through SMC (instead of ECC) it doesn't happen very often.

4 Operator

 • 

2.8K Posts

July 30th, 2008 13:00

Devarsh, as per primus emc22464, the command is right .. I agree that's better to open a SR and have someone dial in the box and check what's going on. Maybe there is a hung symconfigure session.

2 Intern

 • 

292 Posts

August 4th, 2008 07:00

You might also want to check with your local CE to see if they were the ones to set the lock. If the CE has pulled the bin for an upcoming config change they would have set the lock to prevent any changes from occurring until the config change.

4 Operator

 • 

2.8K Posts

August 7th, 2008 12:00

Oh yes .. I forgot that even Optmz do change the bin !!! Good point !!! :D

4 Operator

 • 

5.7K Posts

August 12th, 2008 13:00

So is the issue now resolved ?

October 28th, 2008 11:00

Usually the Optmz lock is #13 though... if I remember right?

T

4 Operator

 • 

2.8K Posts

October 28th, 2008 13:00

Have a look at emc60458 .. :-D

2 Intern

 • 

138 Posts

March 15th, 2011 07:00

I just had this exact same problem:

"Interrogating Configuration Server for config change session information

The configuration change session cannot be interrogated; may be terminated."

the only solution is to call in to EMC Support and have them dial in and clear the lock.

859 Posts

March 16th, 2011 04:00

Hi,

If its happening regularly that config lock does not get released on its own after the successful completion of the config changes then you must talk to Support. What is the enguinity code and SE version you are running?

regards,

Saurabh

No Events found!

Top