My Multi-AZ file system is in a MISCONFIGURED
state
There are a number of potential causes for a file system to be in a MISCONFIGURED
state,
each with their own resolution, as follows.
Topics
The VPC owner account has disabled Multi-AZ VPC sharing
Multi-AZ file systems created by a participant Amazon Web Services account in a shared VPC subnet will go into
a MISCONFIGURED
state for one of the following reasons:
The owner account that shared the VPC subnet has disabled Multi-AZ VPC sharing support for FSx for ONTAP file systems.
The owner account has unshared the VPC subnet.
If the owner account has unshared the VPC subnet, you will see the following message in the console for that file system:
The vpc ID
vpc-012345abcde
does not exist
You need to contact the owner account that shared the VPC subnet with you to resolve the issue. For more information see Creating FSx for ONTAP file systems in shared subnets for more information.
You can't create a new SVM on a Multi-AZ file system
For Multi-AZ file systems created by a participant Amazon Web Services account in a shared VPC, you will be unable to create a new SVM for one of the following reasons:
The owner account that shared the VPC subnet has disabled Multi-AZ VPC sharing support for FSx for ONTAP file systems.
The owner account has unshared the VPC subnet.
You need to contact the owner account that shared the VPC subnet with you to resolve the issue. For more information see Creating FSx for ONTAP file systems in shared subnets for more information.