Skip to main content
NetApp Knowledge Base

Vserver configuration locked after migrating to a new cluster

  1. Last updated
  2. Save as PDF
Views:
Visibility:
Public
Votes:
0
Category:
ontap-9
Specialty:
CORE
Last Updated:

​ ​

Applies to

  • ONTAP 9
  • Storage Virtual Machine (SVM)

Issue

  • After executing vserver migrate start, the Vserver is locked and clients are unable access CIFS.
  • EMS logging will show the following error:

    Error: command failed: Changes to the Vserver configuration are not permitted: the management configuration for the Vserver "vserver" is locked.

  • Logging indicates that during the migration, ONTAP attempted to unlock the Vserver.
  • Logging indicates complete, but throws errors likely due to it already being improperly unlocked before migrate completion:

Mon Nov 10 2025 21:36:49 -06:00 [kern_mgwd:info:4133] 0x84e895800: 0: ERR: Table::vserver: src/tables/vservermgmt/vserver_lock_db.cc:virtual smdb_error vserver_lock_db_iterator::unlock_imp(const smdb_type_boolean *, const smdb_type_mcc_op_context_temp *):166 Failed to unlock vserver xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx in lock db: entry doesn't exist
0000001c.002f715b 00a4d6e2 Mon Nov 10 2025 21:36:49 -06:00 [kern_mgwd:info:4133] 0x84e895800: 0: INFO: Table::vserver_migrate: Unlock of Vserver xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx was successful
Mon Nov 10 2025 21:36:49 -06:00 [kern_mgwd:info:4133] 0x84e895800: 0: INFO: Table::vserver_migrate: Migrate complete. Unlocked destination vserver VSERVER
Mon Nov 10 2025 21:36:49 -06:00 [kern_mgwd:info:4133] 0x84e895800: 0: ERR: Table::vserver: src/tables/vservermgmt/vserver_lock_db.cc:virtual smdb_error vserver_lock_db_iterator::unlock_imp(const smdb_type_boolean *, const smdb_type_mcc_op_context_temp *):159 mcc: unlocking vserver: xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx
Mon Nov 10 2025 21:36:49 -06:00 [kern_mgwd:info:4133] 0x84e895800: 0: ERR: Table::vserver: src/tables/vservermgmt/vserver_lock_db.cc:virtual smdb_error vserver_lock_db_iterator::unlock_imp(const smdb_type_boolean *, const smdb_type_mcc_op_context_temp *):166 Failed to unlock vserver xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx in lock db: entry doesn't exist
Mon Nov 10 2025 21:36:49 -06:00 [kern_mgwd:info:4133] 0x84e895800: 0: ERR: Table::vserver: src/tables/vservermgmt/vserver_lock_db.cc:virtual smdb_error vserver_lock_db_iterator::unlock_imp(const smdb_type_boolean *, const smdb_type_mcc_op_context_temp *):166 Failed to unlock vserver xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx in lock db: entry doesn't exist
Mon Nov 10 2025 21:36:49 -06:00 [kern_mgwd:info:4133] 0x84e895800: 0: ERR: Table::vserver: src/tables/vservermgmt/vserver_lock_db.cc:virtual smdb_error vserver_lock_db_iterator::unlock_imp(const smdb_type_boolean *, const smdb_type_mcc_op_context_temp *):166 Failed to unlock vserver xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx in lock db: entry doesn't

​  

Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.