I have trying to setup Iscsi boot for our esxi servers.
Below are the steps I followed.
1. Created common/global vlans Vlan-nfs-20, mangement-10, vmotion-30, vmtraffic-40,
Created vlan 50 for iscsi in FI-A and Created Vlan 50 for iscsi FI-B
2. Created the 4 vnics
Two for Vnic (1 from FI-A and second one from FI-B, selected Mac Pool-A and Macpool-B respectively and also selected all the vlans except vlan 50 )
Two for Iscsi (1 from FI-A and second one from FI-B, selected Mac Pool-A and Macpool-B respectively, Selected 9000 MTU and selected only vlan 50 and selected radio botton to enable native vlan)
3. Changed qos system to 9216
4. Created Lan connection policy added these four vnics to vnic and two vnic for iscsi and confiured overlay.
5. Created placement policy and slected vcon1 and assigned all 4 nics on to that.
6. Created IP pools for CIMC, ISCSI, IQN, BIOS,UUID pools, Maintance policy, host firmwarepolicy, server pool.
7, Boot policy created iscsi-a for primary and set boot parameters and iscs-b for secondary and set boot parameters.
uplinks are configured in vpc and Iscsi uplinks also configured in vpc.
We are using 6100 FI's and two Nexus 5k.
We have created service profile template and associate to blade i am getting config failure. Please help.
I have also attached screenshot for reference.
Please let me know any details required.
Please doublecheck http://www.cisco.com/c/en/us/support/docs/servers-unified-computing/ucs-manager/116003-iscsi-ucs-config-00.html which has an example.
It sounds like one of your vnics or iSCSI overlays is referencing something invalid (referencing default MAC pool which is empty is VERY common).
Once you determine what is source of config error, if you have Boot from san issues still, I would issue iscsi_get_config command referenced in above config example. We run into a lot of jumbo/MTU issues where the complete path to storage does not allow jumbo end to end.