Note: At the time of writing Cisco has not certified booting UCS blades from Solidfire ISCSI boot disks.
1. VNIC Templates created
2. UUID Pool Created
3. Boot Policy Created (can be created during service profile template creation)
4. Maintenance Policy Created
5. Authentication Policy Created (used to authenticate with the ISCSI target, can be created during service profile template creation )
6. Initiator IP address policy created (IP addresses assigned to the ISCSI vNICs)
7. Create dedicated ISCSI VLAN, use dedicated uplinks for the ISCSI VLAN
Create Service Profile Template
VNIC Creation Select ‘Expert’
Click add to create the iscsi vnics from vnic templates
Create ISCSI VNICS, click ‘add’ in the lower pane
Name the vnic
choose the overlay vnic previously created
do not set iscsi adapter policy
Select ISCSI VLAN
Do not select MAC Address Assignment
Should look like this
Leave default click next
Create boot policy if not already created
Select manintenance policy if required, recommend using user ack!
Create Policies as required
Service Profile template is created…
Create service profile from template
Once created select the new Service Profile in the left pane and browse to ‘boot order’ in the tab selections
Select the ISCI vNIC, you will NOT be able to modify the ‘set iscsi boot parameters’ as the service profile is bound to a template.
Work around is to unbind the service profile from it’s template, Cisco say they will fix this, no date as yet!
Go to general tab and click ‘unbind’, now you will be able to modify iscsi boot parameters
Choose authentication profile for accessing the iscsi target
Select IQN pool
Select Initator IP address pool, create if not there.
Create iscsi target
Enter the IQN ID provided to you by the storage team
Do not select authentication profile
Enter IP address of ISCSI target.
You are now ready to boot from the SolidFire Array, my next post will go through booting the ESXi host!