PowerPath Common Error Code Reference Guide
ESX error messages
The following table covers all the ESX platform error messages that are displayed in PowerPath. You can also search a specific error detail based on its error code.
| Error Code | Error Message | Action |
|---|---|---|
| EKBE001 | No valid path found | Check if paths to the back end array are connected properly. |
| EKBE002 | Path %s : could not issue async IO command: %s | This error is rarely seen. Contact customer support in case of a critical functionality failure. |
| EKBE003 | Path %s : could not issue sync IO command: %s | This error is rarely seen. Contact customer support in case of a critical functionality failure. |
| EKBE004 | Failed to alloc Pirp | Check if sufficient memory is available in the system. |
| EKBE005 | Failed to create Platform scsicmd | This error is rarely seen. Contact customer support in case of a critical functionality failure. |
| EKBE006 | Failed to create Pirp | This error is rarely seen. Contact customer support in case of a critical functionality failure. |
| EKBE007 | Failed to Create Scsi Pirp | This error is rarely seen. Contact customer support in case of a critical functionality failure. |
| EKBE008 | IO Retryable : Other error ScsiStatus: %x HostStatus: %x" "PluginStatus: %x | This error is rarely seen. Contact customer support in case of a critical functionality failure. |
| EKME001 | Reading PID/VID from persistent string error: empty LAM name | Review the number of Third Party Array (TPA) being managed or those that need to be managed by PowerPath. Contact customer support to raise a ticket with Dell PowerPath for assistance. |
| EKME002 | Unable to store more PID/VID pairs | Review the number of Third Party Array (TPA) managed by PowerPath. Remove those that are not currently managed and remove the entries so that new TPA Ids can be added. |
| EKME003 | Writing PID/VID to persistent string error: empty LAM name | Review the number of Third Party Array (TPA) being managed or those that need to be managed by PowerPath. Contact customer support to raise a ticket with Dell PowerPath for assistance. |
| EKME004 | Could not create vol Daemon | Contact customer support to raise a ticket with Dell PowerPath for further investigation. |
| EKME005 | Could not create vol IO dispatch multi threaded Daemon | Though there is no DU/DL situation, performance degradation may occur. Contact customer support to raise a ticket with Dell PowerPath for further investigation. |
| EKME012 | Could not allocate SCSI device | Review the LUN provision/attached to this host and keep them under limits as supported by OS. |
| EKME013 | Failed to add seconday UID %s to device %s | This error is rarely seen. Contact customer support in case of a critical functionality failure. |
| EKME014 | Failed to create Hash table for Vvol PE | This impacts clustered vVol migration use case. Contact customer support to raise a ticket with Dell PowerPath for further investigation. |
| EKME015 | Status:%s. Failed to register" "device. User should unclaim paths. | Review the SAN connectivity and restore any issues. Re-scan HBA for discovery for devices. |
| EKME016 | Failed to request .probe | No action required. The health check is done periodically if this request is not accepted. |
| EKME017 | Failed to request .probe | No action required. The health check is done periodically if this request is not accepted. |
| EKME018 | Auto HostReg: Invalid host UUID. Status:%s | PowerPath host registration feature with PowerMax is broken. Contact customer support to raise a ticket with Dell PowerPath for further investigation. |
| EKME019 | Device %s has exceeded timeout %u and has been resumed | No action required. This log message can be ignored. |
| EKME022 | SCSI-2 reservation failed with SCSI status 0x%x | This error is rarely seen. Contact customer support in case of a critical functionality failure. |
| EKME023 | SCSI-2 release failed with SCSI status 0x%x\ | This error is rarely seen. Contact customer support in case of a critical functionality failure. |
| EKME024 | Failed to get nicename for VVOL %lx | No action required. VM PMI feature CLI output will not display the vVol secondary identity. This may be a temporary problem. This logging is not part of default logmask and will not be seen unless enabled at the customer location. |
| EKME025 | Use Secondary Id %s | No action required. VM PMI feature CLI output will not display the vVol secondary identity. This may be a temporary problem. This logging is not part of default logmask and will not be seen unless enabled at the customer location. |
| EKME026 | Failed to Set Second Level ID in vmk_ScsiCommand | The PowerPath VM PMI feature is broken. Contact customer support to raise a ticket with Dell PowerPath for further investigation. |
| EKME027 | Successfully set cmd context to VVOL - %lx API result %lx | No action required. PowerPath logs an info message. |
| EKME028 | Failed to get host name | Auto host registration functionality is not working. Review to see if command line is able to fetch the host name. If not, contact customer support to raise a ticket with Dell PowerPath for further investigation. |
| EKME029 | Failed to get host UUID | Auto host registration functionality is not working. Review to see if command line is able to fetch the host UUID. If not, contact customer support to raise a ticket with Dell PowerPath for further investigation. |
| EKME030 | MpxEsxSetVmInfo fail to copy vmdata %d %s | PowerMAX performance optimizations may not work. Contact customer support to raise a ticket with Dell PowerPath for further investigation. |
| EKME031 | MpxEsxHostInfo fail to copy HW Vendor Name | PowerMAX performance optimizations may not work. Contact customer support to raise a ticket with Dell PowerPath for further investigation. |
| EKME032 | Failed to Register path %s to vVol SSLID %lx ", "CDB : %x %x %x %x %x %x %x %x %x %x " "cmdStatus %x ScsiStatus %x SKey %x ASC %x ASCQ %x | Registration of vVol through a new path has failed. PowerPath received an unexpected status from the OS. Contact customer support to raise a ticket with Dell PowerPath for further investigation. |
| EKME033 | Failed to Register path %s to vVol SSLID %lx cmdStatus %x ScsiStatus %x | Registration of vVol through a new path has failed. PowerPath received an unexpected status from the OS. Contact customer support to raise a ticket with Dell PowerPath for further investigation. |
| EKME034 | pluginIoctl entry point is currently not implemented. | No action required. PowerPath logs an info message. |
| EKME035 | Path %s has already been claimed | No action required. This path has already been claimed. |
| EKME036 | Unable to determine the conformance for, path %s : status %s | PowerPath is unable to definitely determine if a path belongs to a PE volume or not. Path may not be claimed. Please reach out to VMWare to check the APIs. |
| EKME037 | Path %s does not meet PE conformance | PowerPath is unable to definitely determine if a path belongs to a PE volume or not. Path may not be claimed. Please reach out to VMWare to check the APIs. |
| EKME038 | Path claim failed. Check system limits. Path %s not claimed. | LUN count may have reached beyond system limit (currently 256). check and follow VMware recommendation. |
| EKME039 | MpxRecognize failed. Path %s not claimed | PowerPath is unable to claim the device. Check the claim rule if this path is expected to be claimed by PowerPath, if so, contact customer support to raise a ticket with Dell PowerPath for further assistance. |
| EKME040 | EKME040: Could not claim path %s. Status : %s | PowerPath is unable to claim the device. Check the claim rule if this path is expected to be claimed by PowerPath, if so, contact customer support to raise a ticket with Dell PowerPath for further assistance. |
| EKME041 | Path %s has not been claimed | This error is rarely seen. Contact customer support in case of a critical functionality failure. |
| EKME042 | The volume is open. Cannot unclaim last path %s. | Volume has outstanding opens, path unclaim is failing. Check if the Volume is mounted or the volume is used by any VM, if so stop using the Volume. |
| EKME043 | The volume is being registered or unregistered. Cannot unclaim last path %s. | Path unclaim has failed. Contact customer support in case of a critical functionality failure. |
| EKME044 | Could not unregister the Path. Status:%s, Path:%s | Last path to a volume has been requested to be unclaimed. The operation to unregister the he volume has failed. Contact customer support in case of a critical functionality failure. |
| EKME045 | PathProbe: Path %s has not been claimed | No action required. PowerPath has not configured the path when a OS probe for the same has been requested. |
| EKME046 | PathProbe: Path %s is being unclaimed | No action required. PowerPath printing the path is being unclaimed. |
| EKME047 | VolProbe: Volume not found | No action required. PowerPath has not configured the volume when a OS probe for the same has been requested. |
| EKME048 | VolProbe: Volume %s probe already in progress | No action required. Volume probe already in progress. |
| EKME049 | VolProbe: Probe of path %s failed. Status : %s | Check for dead paths to the Storage array. Contact customer support in case of a critical functionality failure. |
| EKME051 | PathSetState: Path Probe Failed %s | Check for dead paths to the Storage array. Contact customer support in case of a critical functionality failure. |
| EKME052 | PathSetState: Path %s could not be disabled. It is the last working path to volume. | No action required. Trying to disable or turn off the last alive path. |
| EKME053 | PathSetState: ProbePath Failed %s | Check the environment. Path is still not ready to be claimed. |
| EKME054 | Failed to create Char device %s. Status : %s | Contact customer support in case of a critical functionality failure. |
| EKME055 | PowerPath license has expired | Check PowerPath license and renew it if expired. |
| EKME056 | GetDeviceScsiInfo- Volume is not Registered | Contact customer support to raise a ticket with Dell PowerPath for further assistance. |
| EKME057 | GetDeviceScsiInfo- Not valid vol or Mpxdevice | Contact customer support to raise a ticket with Dell PowerPath for further assistance. |
| EKME058 | GetDeviceScsiInfo- Not a valid extension device | Contact customer support to raise a ticket with Dell PowerPath for further assistance. |
| EKME059 | PacketIocmd- POWER_IOCMD_ERR_COPYIN_FAILED. | Contact customer support to raise a ticket with Dell PowerPath for further assistance. |
| EKME060 | PacketIocmd- POWER_IOCMD_ERR_NO_SUCH_EXTENSION. | Contact customer support to raise a ticket with Dell PowerPath for further assistance. |
| EKME061 | PacketIocmd- POWER_IOCMD_ERR_COPYOUT_FAILED. | This error is rarely seen. Contact customer support in case of a critical functionality failure. |
| EKME062 | Add and Delete path commands are issued using the plugin entry points | This error is rarely seen. Contact customer support in case of a critical functionality failure. |
| EKME063 | PiocPacketIocmd- POWER_IOCMD_ERR_COPYIN_FAILED. | This error is rarely seen. Contact customer support in case of a critical functionality failure. |
| EKME064 | PiocPacketIocmd- POWER_IOCMD_ERR_COPYIN_FAILED. | This error is rarely seen. Contact customer support in case of a critical functionality failure. |
| EKME065 | PiocPacketIocmd- IOCMD VMK_FAILURE rc %d. | This error is rarely seen. Contact customer support in case of a critical functionality failure. |
| EKME066 | Path %s : could not issue async IO command: %s | Check device and path connectivity for any failures. |
| EKME067 | Failed to Create Pirp | Check to see if there is high memory usage/memory leak due to other components. |
| EKME068 | Start Cmd: Not a valid extension device | This error is rarely seen. Contact customer support in case of a critical functionality failure. |
| EKME069 | Completed the platform IO %x with H:0x%x P:0x%x because of the PowerPath error | This error is rarely seen. Contact customer support in case of a critical functionality failure. |
| EKME071 | QGOOD Line:%d, Before Assert: Total Ent:%d | This error is rarely seen. Contact customer support in case of a critical functionality failure. |
| EKME072 | Vol Task Mgmt: Volume not found | This error is rarely seen. Contact customer support in case of a critical functionality failure. |
| EKME075 | Allocation of dummy ASyncIoDaemon " "entry failed. Not aborting it. | This error is rarely seen. Contact customer support in case of a critical functionality failure. |
| EKME078 | Allocation of dummy TestDaemon entry failed. Not aborting it. | This error is rarely seen. Contact customer support in case of a critical functionality failure. |
| EKME079 | Task management failed on all paths to %s, aggregateStatus is %x | This error occurs if there are no good paths to volume. Check the device connectivity status. |
| EKME080 | Volume to be opened not found. | This error is rarely seen. Contact customer support in case of a critical functionality failure. |
| EKME081 | %s Volume is being destroyed. Volume Open failed. | This error is rarely seen. Contact customer support in case of a critical functionality failure. |
| EKME083 | Volume to be closed not found. | This error is rarely seen. Contact customer support in case of a critical functionality failure. |
| EKME084 | Vol Inquiry: Volume not found | This error is rarely seen. Contact customer support in case of a critical functionality failure. |
| EKME085 | Vol Dump Cmd: Volume not found | This error is rarely seen. Contact customer support in case of a critical functionality failure. |
| EKME086 | Vol Dump Cmd: No active path to the device found. | No active path to the device found. Check paths to back-end array. |
| EKME087 | Get Path Names:Volume not found | This error is rarely seen. Contact customer support in case of a critical functionality failure. |
| EKME088 | %s Volume is being destroyed. Cannot open. | Check whether Volume is unclaimed explicitly or removed from the array back end. |
| EKME089 | Vol Is Pseudo: Volume not found | This error is rarely seen. Contact customer support in case of a critical functionality failure. |
| EKME090 | Allocation of dummy EmcMpioVolIoDispatchDaemon entry failed. Not aborting it. | This error is rarely seen. Contact customer support in case of a critical functionality failure. |
| EKME091 | MpxEsxScsiIO Not valid vol or Mpxdevice | This error is rarely seen. Contact customer support in case of a critical functionality failure. |
| EKME092 | MpxEsxScsiIO: Not a valid extension device | This error is rarely seen. Contact customer support in case of a critical functionality failure. |
| EKME093 | MpxEsxGetVVOLInfo: No alive paths found for this volume | Check paths to back-end arrays. No alive paths found for this device volume. |
| EKME094 | MpxEsxVolOpenDevice: %s Volume is busy. regState %d devState %d Volume Open failed. | This error is rarely seen. Contact customer support in case of a critical functionality failure. |
| EKME095 | License has not been refreshed for more than %d days," "marking host unlicensed." | Customer needs to connect to PPMA and refresh the license immediately. |
| EKME096 | License type requested: %s is not allowed for this host,host license state is %d | Customer needs to upgrade to latest PPMA and ensure enough permanent licenses are added to PPMA. |
| EKME097 | Invalid request for license register,invalid parameter ppmaIP or serverCheckedOut is NULL. | Customer needs to check data collector logs on PPMA for this host to diagnose further. |
1～5個の星の数で評価してください。
1～5個の星の数で評価してください。
1～5個の星の数で評価してください。
この記事は役に立ちましたか?
コメントでは、以下の特殊文字は利用できません: <>()\