Vserver migrate Configuration Baseline has not arrived

Last updated
Save as PDF
Share
1. Share
2. Tweet
3. Share

Views:: 7

Visibility:: Public

Votes:: 0

Category:: ontap-9

Specialty:: dp

Last Updated:

Applies to

ONTAP 9
FAS
AFF A20, AFF A30, AFF A50, AFF C30, AFF C60

Issue

Vserver migration failed during the setup-configuration phase.

The migrate operation could not be completed because the configuration baseline for the Vserver "soure_svm" did not arrive, resulting in a setup-configuration-failed status.

Destination_Cluster::> vserver migrate show

Destination Source

Vserver Cluster Cluster Status

---------------- ------------------- ------------------- ---------------------

soure_svm Destination_Cluster Source_Cluster setup-configuration-failed

Status Details: Migrate operation failed. Reason: Application of configuration failed for Vserver "soure_svm". Reason: Failed when polling for the migrate operation completion for Vserver "soure_svm". Reason: Configuration Baseline has not arrived for Vserver xxxxxx-xxxxxx-xxxxx-xxxxxx. To resume the Vserver migrate operation, use the "vserver migrate resume" command. To change the source Vserver configuration, use the "vserver migrate pause" command on the destination cluster, make the configuration     changes on the source cluster, and then use the "vserver migrate resume" command on the destination cluster.

- Pre- check is PASS without issue:

Destination_Cluster::> vserver migrate start -vserver soure_svm -source-cluster Source_Cluster -check-only true

Info: Vserver migrate checks finished. Vserver migrate can be started now.

00000007.001967ed 01643139 Tue Sep 29 2026 00:57:59 -06:00 [kern_audit:info:4261] 8003e80000065cd5:8003e80000065cd7 :: bocfslab3:ssh :: x.x.x.x:61453 :: bocfslab3:admin :: vserver migrate start -vserver soure_svm -source-cluster Source_Cluster -check-only true :: Pending

00000007.00196d0e 016431ac Tue Sep 29 2026 00:58:10 -06:00 [kern_audit:info:4261] 8003e80000065cd5:8003e80000065cd7 :: bocfslab3:ssh :: x.x.x.x:61453 :: bocfslab3:admin :: vserver migrate start -vserver soure_svm -source-cluster Source_Cluster -check-only true :: Success

00000007.00196e54 01644345 Tue Sep 29 2026 01:05:41 -06:00 [kern_audit:info:4261] 8003e80000065cd5:8003e80000065d30 :: bocfslab3:ssh :: x.x.x.x:61453 :: bocfslab3:admin :: vserver migrate start -vserver soure_svm -source-cluster Source_Cluster :: Pending

- MGWD log:

00000007.0011d91d 00f6ac58 Sun Sep 20 2026 17:35:31 -06:00 [kern_mgwd:info:4261] vserver_migrate:Sun Sep 20 17:35:31 2026:src/tables/vserverdr/migrate/vserver_migrate_util.cc:319 (thr_id:0x84a403b00) Txn: 0:src/tables/vserverdr/migrate/vserver_migrate_precheck.cc:is_audit_created_for_svm:6440 Failed to determine if audit is enabled for vserver soure_svm. Reason:Internal error. Failed to get the audit config for Vserver "soure_svm" in cluster "Source_Cluster". Reason: entry doesn't exist.

- Checked audit configuration no issue:

Source_Cluster::*> debug smdb table vserver_audit_config_db show

This table is currently empty.

Source_Cluster::*> vserver audit show -vserver soure_svm

There are no entries matching your query.

The SVM migration from source cluster Source_Cluster to destination cluster Destination_Cluster for SVM soure_svm failed due to the error "Configuration Baseline has not arrived," despite multiple troubleshooting steps including verification of name-service and audit configurations, disabling VSCAN, and rebooting the source node. All relevant configurations were confirmed as correct, and the audit tables were empty, indicating no misconfiguration on the source SVM.