This is a follow up post to the iSCSI Boot From SAN post that shows how the virtual networking and Storage Adapter configuration of ESXi looks post install.
Note: At the time that I posted this, only ESXi 4 is supported by Cisco for iSCSI Boot From SAN on Cisco UCS but ESXi 5 is what I had on hand to test the iSCSI Boot From SAN configuration.
Once the networking configuration for the host has been completed, connect to the host with the vSphere Client. The first iSCSI enabled vNIC for the Service Profile is automatically added to a vSwitch and a vmkernel port is configured with the IP address that was configured in the Boot Parameters for the 1st iSCSI vNIC in the server’s Service Profile referenced from my post here.
Note: At the time that I posted this, only ESXi 4 is supported by Cisco for iSCSI Boot From SAN on Cisco UCS but ESXi 5 is what I had on hand to test the iSCSI Boot From SAN configuration.
Once the networking configuration for the host has been completed, connect to the host with the vSphere Client. The first iSCSI enabled vNIC for the Service Profile is automatically added to a vSwitch and a vmkernel port is configured with the IP address that was configured in the Boot Parameters for the 1st iSCSI vNIC in the server’s Service Profile referenced from my post here.
In the above screen shot, even though the iSCSI vNIC is configured to behave as a physical iSCSI HBA in the UCS Service Profile, in vSphere I noticed that it is still installed as a software iSCSI adapter, and the vNIC is associated with the software iSCSI adapter for the ESXi host. The iScsiBootPG Port Group was automatically created on the iScsiBootvSwitch vSwitch.
To add additional LUNs to the host for datastores, I configured the Volumes and LUN Mappings via the Lefthand CMC and then configured the Dynamic Discover settings in the Storage Adpaters section of the ESXi host.
