Release Notes

Unmapping LUNs from PowerEdge VRTX shared storage
generates inaccessible LUN entries In ESXi
Description: When you unmap LUNs from PowerEdge VRTX Shared Storage, ESXi displays
inaccessible LUN entries. This issue occurs if the mapped virtual disks are already
assigned to VMs.
Applies to: ESXi 5.1.x
Solution: Complete the following steps to resolve the issue:
1. Remove the virtual disks that are already mapped to the VM using vCenter
client.
2. Unmap the virtual disks from the CMC.
3. Rescan the shared Shared PERC 8 card from ESXi using vCenter client or the
Command Line Interface (CLI).
ESXi uses the management network interface for iSCSI
SAN traffic
Description: ESXi uses the Management Network Interface for iSCSI Storage Area Network
traffic, although there is a specific interface configured for iSCSI SAN traffic. The
log entry for iSCSI storage array displays the ESXi Management IP address instead
of the initiator IP address.
Applies to: ESXi 5.x
Solution: This is an expected behavior when both ESXi Management Network and iSCSI SAN
Network are configured in the same subnet. To resolve this issue, configure
separate subnets for ESXi management network and iSCSI SAN.
Microcode related error messages logged in the ESXi
Syslog.log file
Description: The syslog.log file lists entries similar to the ones listed below:
2013-10-31T06:43:52Z vmkmicrocode: Warning: File
microcode_amd_0x100fa0.bin does not contain a valid microcode
update for any of the processors
2013-10-31T06:43:52Z vmkmicrocode: Warning: Error: file
microcode-1027.dat is not a container file
2013-10-31T06:43:52Z vmkmicrocode: Warning: Error: file
m4010676860C0001.dat is not a container file
Applies to: ESXi 5.x
Solution: This issue can be ignored because there is no functionality loss.
20