- VMware Technology Network
- :
- Cloud & SDDC
- :
- VMware vSphere
- :
- VMware vSphere™ Discussions
- :
- How do you adjust SVMotion RPC Timeout
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
How do you adjust SVMotion RPC Timeout
When doing vmotion + storage vmotion on VMs with multi-TB disks, the source server is disconnecting with an RPC timeout
It looks like this occurs when the destination server takes over 20 seconds to complete DISKLIB-LIB_CREATE , then the source server logs vmx| W115: MigrateRPCCheckTimeouts: Declaring RPC timeout.
From the logs below you can see the first disk creation on the destination took 12 seconds, the second disk creation was underway but once it hit 20 seconds the source server declared it a timeout.
I've already changed the "Migrate.NetTimeout" value from 20 seconds to 120 seconds, but it had no impact, I'm still getting the timeout at 20 seconds.
Is there any way to change the SVMotion RPC Timeout value?
Source server: vmware.log
2019-07-19T21:05:44.143Z| worker-2124655| I125: SVMotionRemoteInit: Completed.
2019-07-19T21:05:44.145Z| worker-2124655| I125: SVMotion: Enter Phase 2
2019-07-19T21:06:16.609Z| vmx| W115: MigrateRPCCheckTimeouts: Declaring RPC timeout.
2019-07-19T21:06:16.609Z| worker-2124655| W115: SVMotionRemoteDiskCreate: Remote disk create failed: 1
Destination server: vmware.log
2019-07-19T21:05:44.144Z| worker-2106270| I125: SVMotion_RemoteInitRPC: Completed.
2019-07-19T21:05:44.149Z| worker-2106270| I125: SVMotionDiskGetCreateExtParams: not using a storage policy to create disk '/vmfs/volumes/5c52333e-f4cd754a-3efe-246e966ce79c/<########>/<########>_4.vmdk'
2019-07-19T21:05:44.149Z| worker-2106270| I125: DISKLIB-LIB_CREATE : CREATE: "/vmfs/volumes/5c52333e-f4cd754a-3efe-246e966ce79c/<########>/<########>_4.vmdk" -- vmfs capacity=2147483648 (1 TB) adapter=lsilogic info=cowGran=0 allocType=3 objType= policy=''
2019-07-19T21:05:44.149Z| worker-2106270| I125: DISKLIB-LIB_CREATE : CreateObjExtParams: Object backing type 0 is invalid. Figuring out the most suitable backing type...
2019-07-19T21:05:44.149Z| worker-2106270| I125: DISKLIB-LIB_CREATE : CREATE: Creating disk backed by 'file'
2019-07-19T21:05:56.321Z| worker-2106270| I125: DISKLIB-DSCPTR: "/vmfs/volumes/5c52333e-f4cd754a-3efe-246e966ce79c/<########>/<########>_4.vmdk" : creation successful.
2019-07-19T21:05:56.334Z| worker-2106270| I125: DISKLIB-VMFS : "/vmfs/volumes/5c52333e-f4cd754a-3efe-246e966ce79c/<########>/<########>_4-flat.vmdk" : open successful (1) size = 1099511627776, hd = 0. Type 3
2019-07-19T21:05:56.342Z| worker-2106270| I125: DISKLIB-VMFS : "/vmfs/volumes/5c52333e-f4cd754a-3efe-246e966ce79c/<########>/<########>_4-flat.vmdk" : closed.
2019-07-19T21:05:56.342Z| worker-2106270| I125: Hostlog_AddCleanupItem: Ignoring attempt to re-add /vmfs/volumes/5c52333e-f4cd754a-3efe-246e966ce79c/<########>/<########>_4.vmdk.
2019-07-19T21:05:56.347Z| worker-2106270| I125: SVMotionDiskGetCreateExtParams: not using a storage policy to create disk '/vmfs/volumes/5c52333e-f4cd754a-3efe-246e966ce79c/<########>/<########>_3.vmdk'
2019-07-19T21:05:56.347Z| worker-2106270| I125: DISKLIB-LIB_CREATE : CREATE: "/vmfs/volumes/5c52333e-f4cd754a-3efe-246e966ce79c/<########>/<########>_3.vmdk" -- vmfs capacity=2147483648 (1 TB) adapter=lsilogic info=cowGran=0 allocType=3 objType= policy=''
2019-07-19T21:05:56.347Z| worker-2106270| I125: DISKLIB-LIB_CREATE : CreateObjExtParams: Object backing type 0 is invalid. Figuring out the most suitable backing type...
2019-07-19T21:05:56.347Z| worker-2106270| I125: DISKLIB-LIB_CREATE : CREATE: Creating disk backed by 'file'
2019-07-19T21:06:16.831Z| vmx| I125: MigrateSetStateFinished: type=2 new state=12