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.

Note:

  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

4.creating_default_lun

Step 2.  Adding a Host Initiator Group

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

Continue reading “Cisco UCS Invicta Storage – How to Provision a LUN to ESX Host”

Cisco UCS Firmware Overview

Hello Everyone,

Cisco has recently launched a lot of  Firmware for CISCO UCS, it is becoming rather hard to keep up with the new release. We had 5 New Release in Version 2.2 starting from 2.2.(1b),  2.2.(1c), 2.2.(1d),  2.2.(1e), 2.2.(2c).

The good thing is, in every release CISCO  is adding some good features. In one of  the release 2.2.(1d) they have introduced boot from SD, FlexFlash, this option was not available on the older versions of  UCS Manager.

If you are intreasted in this, and want to find how you can boot the ESXi or any other OS off the Secure Digital (SD)  FlexFlash  and how this can be implemented do check  my post  here: Cisco UCS FlexFlash Configuration of Secure Digital (SD) Card

So, for the newbee  to Cisco UCS,  its confusing about the firmware. In this post I am trying to clarify few aspects of this, feel free to post comment below if you have any questions and I will get back to you.

The CISCO UCS firmware is bundled into two packages as given below:

ucs_firmware

 

1. Infrastructure Firmware

In Infrastructure Software firmware we update the firmware of the following

  • Cisco UCS Manager software
  •  Kernel and system firmware for the fabric interconnects
  •  I/O module firmware

2. Server Firmware

Cisco UCS B-Series Blade Server Software Bundle

  • CIMC firmware
  • BIOS firmware
  • Adapter firmware
  • Board controller firmware
  • Third-party firmware images required by the new server

This also includes the firmware of Adapter, BIOSFC Adapters,  HBA Option ROM, Storage, Controller, Local Disk

Cisco UCS C-Series Rack-Mount UCS-Managed Server Software

  • CIMC firmware
  • BIOS firmware
  • Adapter firmware
  • Board controller firmware
  • Third-party firmware images required by the new server

As most of you might be aware the UCS manager is the GUI Java based which allows you to fully manage the CISCO Unified Computing System.

Note I have noticed that the Java version  7 update 40 is only compatible with the UCS Manager. 

So, where does the UCS Manager run ?

This was one of my first questions, Well the Software of the UCS Manager runs on the FI ( Fabric Interconnect 62xx) as we have a pair of Fabric Interconnect it has got resilience.

The UCS System is designed to be highly scalable and available, so upgrading the firmware should not bring any outage to the environment. However Cisco still suggests to arrange a Change windows and get this done out of hours or the quite period of your business.

This UCS Manager is bundled in the Infrastructure Firmware Software along with the Kernal update of the FI which is the NXOS, Finally we have the I/O Module firmware which is a part of the Infrastructure firmware software too.

The Other Bundle is the Server Firmware which has the firmware for BIOS, the Blades, Adapter, Board controller etc.

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

Hope this information is useful, feel free to comment.