Symptoms

An environment alert may be posted, and the file system is down. The cloud provider metadata server is not reachable: Event Id: EVT-ENVIRONMENT-00063 Event Message: Unable to communicate with the cloud provider metadata server. Additional Information: Cause=Network configuration Event Description: This virtual DD system is not able to connect with the metadata server of the cloud provider. Prolonged loss of connectivity with the metadata server will cause the filesystem to go down. Recommended Action: Check the network configuration of the system and confirm that the primary network interface and DHCP service are active. Also, validate that there are no firewall rules that may be blocking access to the metadata server. ------------------------------------------------ Message Unsupported virtual hardware configuration. p0-257 Wed Jul 19 CRITICAL Environment Component=Configuration EVT-ENVIRONMENT-00040: Unsupported virtual hardware configuration. Post Additional Information Cause=instance type - Fail to retrieve the instance type information from metadata server! Clear Additional Information Event Id EVT-ENVIRONMENT-00040 Event Name UnsupportedHardwareConfig Description Unsupported virtual machine hardware configuration was detected. This configuration may cause unexpected behavior. Action Fix the hardware configuration to resolve the problem. If problem persists, restart the system. ------------------------------------------------- ------------------------------------------------- Alert Id p0-257 Post Time Tue Jul 22 13:55:35 2025 Severity CRITICAL Class Environment Object Component=Configuration Message Unsupported virtual hardware configuration. Additional Information Cause=instance type - Fail to retrieve the instance type information from metadata server! -------------------------------------------------

Cause

A cloud provider such as GCP (but also potentially applicable to others) can use a "metadata server" transparently, associated to cloud storage for active tier data. If this metadata server cannot be accessed for a long time, the DDVE file system may be disabled for safety.The DDVE file system may be unable to contact the metadata server anymore is because of changes made to the DDVE DNS or interface (DHCP) settings. 

Resolution

If data storage is unavailable due to earlier issues with cloud storage communication, address the issue causing the access to the metadata server to fail. Trying to "filesys enable" fails.Google Cloud Platform (GCP)For example, for Google Cloud Platform (GCP), the metadata server is hostname "metadata.google.internal" with (internal) IP 169.254.169.254. Any VM in GCP knows how to resolve and reach the metadata server if at least one interface has been configured through DHCP. If, for example, a DDVE was configured that way and later the interface was given a static IP (no DHCP). The DDVE cannot resolve the metadata server IP address. Add a static name to the IP host mapping in the DDVE for the GCP metadata server to resolve the condition.Microsoft AzureInstance Metadata Service (IMDS) requests must be sent using the VM's primary NIC and primary IP. Interface ethV0 must be used for metadata server communication.Azure Instance Metadata Service for virtual machines - Azure Virtual Machines | Microsoft Learn Add the route back. Replace 127.1.1.1 with the correct gateway IP for ethV0. net route add host 169.254.169.254 gw 127.1.1.1 dev ethV0

Support Cases