FCoE VMware ESXi LUN paths visible but vCenter ESXi in different location cannot access the datastore using Fibre Channel over Ethernet (FCoE) Output of command esxcli storage core device list Status ...FCoE VMware ESXi LUN paths visible but vCenter ESXi in different location cannot access the datastore using Fibre Channel over Ethernet (FCoE) Output of command esxcli storage core device list Status : degraded ( means single path ) Note: "unknown" means ESXi does not recognize the state of the device or "off" may indicate Permanent Device Loss (PDL) Output of vmkwarning.log while trying to access LUN cpu12:123)WARNING: Partition: 123: Partition table read from device naa.xyz failed: I/O error
Large compute environment: over 180 compute nodes Not limited to HCI systems only This article explains how to send the compute/vCenter telemetry for large-scale compute environments. By default the t...Large compute environment: over 180 compute nodes Not limited to HCI systems only This article explains how to send the compute/vCenter telemetry for large-scale compute environments. By default the timeout for pulling telemetry from the vCenter onto the mNode is set to 60 seconds. For large environments it can take more than 60 seconds transferring the larger payload. As such the data will not be sent to or appear in Active IQ. """Default timeout for AIQ API requests in seconds"""
ONTAP Tools for VMware vSphere (OTV) 9.12 ONTAP Tools for VMware vSphere (OTV) 9.13 When provisioning a new datastore using ONTAP Tools for VMware vSphere (OTV): The wrong datacenter is displayed as t...ONTAP Tools for VMware vSphere (OTV) 9.12 ONTAP Tools for VMware vSphere (OTV) 9.13 When provisioning a new datastore using ONTAP Tools for VMware vSphere (OTV): The wrong datacenter is displayed as the 'provisioning destination' in the OTV wizard Datacenter1 is selected and the OTV Provision Datstore wizard is launched: The provisioning wizard displays the Test02 datacenter instead of the correct datacenter which is Datacenter1:
