Pool was created already from previous lab. If you didn't create the pool you could evoke the creation form this page.

2.) Storage

No local storage has been selected you could choose RAID0 or RAID 5 this was what we configured perviously as part of the server hardware capabilities 

Next, click expert mode

Create vHBA1 for FI-A and choose the VMware adapter policy for the vHBA

Create the QoS policy for FC

This is what it should look like in the end

Name vHBA1 WWPN from UCS-ESX1-FABA and the VMWare Adapter policy and FC QoS Policy

You would know create vHBA2 for FI-B and the final result is as follows

3.) Networking (Create VNIC's 1 and 2 for the vmKernel)

Click Expert and Add to create the vNIC's

Pick the proper pool of MAC address (UCS-1-ESXi)

Choose the Fabric A and the VLAN's this vNIC will be associated with.

Choose the Adapter Policy VMWare

Create VNIC1 (FAB-A) for VMKernel MAC Address Pool UCS-1-ESXi, VLAN Default (native) 110-115, and Adapter policy VMWare

Create VNIC2 (FAB-B) for VMKernel MAC Address Pool UCS-1-ESXi, VLAN Default (native) 110-115, and Adapter policy VMWare

Create VNIC3 (FAB-A) for VMotion MAC Address Pool UCS-1-ESXi, VLAN 115, and Adapter policy VMWare

Create VNIC4 (FAB-B) for VMotion MAC Address Pool UCS-1-ESXi, VLAN 115, and Adapter policy VMWare

Create VNIC6 (FAB-B) For VMWare hosts AC Address Pool UCS-1-ESXi, VLANS 110-114, and Adapter policy VMWare

You could create VNIC 7 and 8 for NFS Data Stores as well

4.) vNIC/vHBA Placement

This is going to be dependent on the Server OS that will reside on the blade server itself. VMWare doesn't really matter what order, but for Windows Servers you should pay particular attention to the order of the vNIC's and vHBA's

5.) Create Boot Policy

The Boot order will start with Boot From SAN first and saying that vHBA1 is the primary 

Create vHBA2 for the secondary

Create a Boot Target primary under vHBA1 (DISK or LUN pWWN) to boot from

Create another Boot Target secondary under vHBA2 (DISK or LUN pWWN) to boot from.

Final configuration should look as follows

Finally pick the Boot Order Policy you just created and click next

6.) Maintenance Policy

I didn't choose any Maintenance Policy

7.) Server Assignments 

Choose one of the Server Pools that I created earlier and click Next

8.) Operational Policies 

Choose the BIOS Policy Loud Boot and the IPMI SoL-115200

 Choose the default option

Choose WipeBIOS

And Click Finish 

You'll see the final Configuration to make sure it's correct and then click Yes

You'll see the FSM is associating the Service Profile to the blades from that server pools