Monthly Archives: November 2013

UCS Service Profile Template creation for SolidFire ISCSI Boot

Note: At the time of writing Cisco has not certified booting UCS blades from Solidfire ISCSI boot disks.

UCS Pre-Requisites:

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


Do not select MAC Address Assignment


Should look like this




Leave default click next


Leave default


Create boot policy if not already created


Select manintenance policy if required, recommend using user ack!


Leave defaults


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!

vShield Edge Static Routing between External networks


1 x VCNS Edge Gateway with Public IP Block – VLAN 200

External Network 1 – with Public IP Block – VLAN 201

External Network 2 – with Public IP Block – VLAN 202

I recently came across a customer requirement where they wanted to set up some static routes between External Network 1 (VLAN 201) and External Network 2 (VLAN 202) as above.  Both networks had been created in vCloud Director as external networks and did not have any Organisation Networks attached to them. 

We had an existing VCNS Edge Gateway with a public IP block assinged on VLAN 200, my assumption was that we add both external networks to the existing VCNS Edge Gateway and apply the static routes between them.  It turns out that it’s not that simple! when I attempted to apply the routes between Network 1 and Network 2  I got the following message… “Static routing between overlapping networks is not supported”, it seems that the because they are connected to vCloud Director as external networks it will not allow you to add static routes as VCD sees them as overlapping networks.

This was a misunderstanding on my part on how static routing works on VCNS Edge Gateways, it seems that I’m not the only one as several of my colleagues had the same misconception.  In the end we applied the static routes on an upstream switch as we could not get the routes to stick on the VCNS Gateway.  Static Routes work well on VAPP networks and Organisation networks on the internal side of the vShield Edge, but there is very little information on there on using them for external networks, I aim to do some more research in this area so will update the blog in due course.