"No facility available for disk upload" when creating MCS VMs on AWS
book
Article ID: CTX473075
calendar_today
Updated On:
Description
The following error occurs during the process of machine creation via MCS on AWS
"No facility available for disk upload. Unable to create any functioning volume service VMs when create mcs vms on AWS"
Resolution
Since this is only a general error, additional troubleshooting steps are required to determine the root cause. Below is a list of several steps to verify along with the subsequent actions to take.
- The capacity in the current zone is not available.
- Select another zone when creating VMs via MCS.
- The security group settings for VMs on AWS has blocked the 443 connections from DDC.
- Check Inbound/Outbound rules. Make sure 443 port is opened for security group for VMs on AWS.
- The instance type for MCS VM is not in the AWS offering list.
- Check if the selected instance type is in the list in C:\Program Files\Common Files\Citrix\HCLPlugins\Hypervisor\v2.27.0.0\AWS\AWSConfiguration\instancetype.xml, if not update it following CTX139707
- AWS Transit Gateway configuration may block the 443 test process from DDC to the Volume Worker. When a VPC is associated with a Transit Gateway, you can attach one subnet from each Availability Zone in the region to the Transit Gateway. When a subnet is associated, Transit Gateway creates an Elastic Network Interface in this subnet which carries all the transit traffic back and forth.
- Open an AWS case and check the configuration of Transit Gateway settings.
Problem Cause
Improper configuration between Citrix DDC and AWS.
Was this article helpful?
thumb_up
Yes
thumb_down
No