Blog Archives

Cisco UCS Invicta Storage – How to Provision a LUN to ESX Host

Hi All,

I am writing this post to show the process on how to provision LUN’s from Cisco UCS Invicta  to ESX host in 3 steps hope you enjoy the post.


  1.  Create a default LUN and add MAP ID 0 ‘zero’ when ever you are provisioning a new ESX  rule of thumb for Invicta is add a default lun  lun0_ default with MAP ID 0
  2. Keep all the LUN’s with the same MAP id on each host when provisioning them. ( Caution : If you do not give the same MAP ID for a LUN which is already provisioned and the lun has VM running. The LUN comes up as a new lun to be added to VMware so the Administrator if he is not aware of this issue may end up formating it assuming its a new LUN to provision using VMFS 5.
  3. You need to remember that you can right click and drag and drop luns to map them.

In our environment I have created a default lun with 10 GB and never provision this on VMware, however always add this default lun first  with MAP ID 0 to any ESX host you want to provision.

Login to the invicta with admin or superuser account.

Step 1: Creating a LUN

Click on LUN Configuration and LUNs and Click on Create LUN

 1.LUN Page

As I have mentioned in the Notes at the top that we need to first create a default lun which is what I am creating below. just fill in the details I call it lun0_default

Create a Default lun0

The size of this lun can even be 1 GB as you are not going to use this lun . I have put 10 GB a I have 65 TB of thin provisioned disk and I am not going to provision this lun its just what is recommended by Cisco documentation to have a default  lun 0 provisioned on each host with MAP ID 0

Create LUN Page

I have created another LUN of 1 TB calling it lun1 as shown below


Step 2.  Adding a Host Initiator Group

Click on LUN Configuration and Initiator Groups and Click on Create New Group

Read the rest of this entry


advanced boot or secure boot configuration cannot be applied to the specified server There are not enough resources overall

If you are looking at this Failure Reason: advanced boot or secure boot configuration cannot be applied to the specified server There are not enough resources overall, You might have come across this error.

advance boot or secure boot configuration cannot be applied

Although the above error looks like a very generic error when you apply a service profile to a Server. Most of the on-line search takes you in the direction of making sure you are using the legacy CD ROM drive.

With the process of elimination I found that while using the Flex Flash ‘SD Card’ in Boot Option this error was trigged. once I removed the SD Card, I was able to apply the profile with out any problems.  But I wanted to use the Flex Flash with RAID-1,( SD Cards) to boot.  more info on  Cisco UCS FlexFlash Configuration of Secure Digital (SD) Card

As you might be aware that boot from SD card is a new feature introduced in version 2.2 , we then started looking at he version of UCS Manager and Firmware running on the environment. I had recently upgraded this UCS to the 2.2(1d) so that was not an issue.

We thought to double check the firmware configuration, when going through this options we create a Host Firmware Policy specifically only for M3 and just selecting the M 200 M3 CIMC and Bios with the latest version of firmware.  more info on firmware can be found CISCO UCS Firmware Update Process

Once this option was applied to the Service profile The blade started to boot up.

The only thing different to this was I had created a custom firmware on Host Firmware Policy called 2.2 firmware but ended up selected quite a lot of servers with latest version of software .. However in my UCS Environment I have only got M 200 M3.

So to fix this issue, make  sure in ‘Host Firmware Package’ make sure you have customized firmware profile for every different server you have, so that you can individually apply it to the service profile you are assign to that specific server.

Example M2 and M3 Blades we can have two Host Firmware Packages which you can add to specific Service profiles individually.

Additional resources:

If you want to learn more about the process of doing a Firmware update please checkout my link CISCO UCS Firmware Update Process

If you want to learn more about the process of doing a Firmware update please checkout my link Cisco UCS FlexFlash Configuration of Secure Digital (SD) Card




Cisco UCS FlexFlash Configuration of Secure Digital (SD) Card

 Cisco UCS FlexFlash /SDCard Configuration for Booting Server Operating System.

As most of the Cisco UCS users might be aware that Cisco has now add a lot of improvements and new features on the latest upgrade 2.2(1e).

One of the feature which we have started using is Cisco FlexFlash which is an SD Card. Its fully support if you buy the SD  Card from Cisco and we can even do mirroring on the Flash cards for redundancy, we will be installing ESXi Server 5.5 on these blades after mirroring them.

So where and How to install the Secure Digital (SD) Card  ?

If the CISCO UCS B200 Blade is in the Chassis you will need to power it off and slide it out just half way through and you should find the SD Card slot on the left


cisco ucs sdcard slot

for more information on how about this can be found on the following link

As you might be aware that CISCO UCS blade is just as equal to a brick and all the configuration is done on the logical server called Service profile. you will need to create a new  / clone an existing Service profile template and modify with the below changes which I have shown below on this post.

You will have to create a boot policy with CD Drive (legacy ) and SD Card and Some time you may end up getting this error ‘ advanced boot or secure boot configuration cannot be applied to the specified server There are not enough resources overall ‘ if you see it follow my blog post.

I have to make you aware that if you want to use SD card with Mirroring or RAID 1 you have to create the following new policies and create a Boot policy as mentioned above.

1. Disk policy with Mirror and any configuration

















2.   We have to create two Scrub policy under policy ( you can call it any thing you want which makes you understand what configuration you have selected)

  1. Flex Flash Scrub
  2. No Scrub

So where will you find the Flex Flash Controller?

Click on the Left pan on Equipment and Select the Chassis then the Server, on the right you will find the below details

click on Inventory and select the last tab which is Storage on the Storage tab you will find FlexFlash Controller

Note: this FlexFlash is only support if you are running 2.2 (d1) firmware.


%d bloggers like this: