Skip to main content

BOOT FROM SAN - CISCO UCS 240 M5

Configuring QLogic BIOS to Boot from SAN

1. Take it into legacy mode 

Go to Compute > BIOS











2. Configure Boot order 

Boot order also must be created . Go to Compute > BIOS  > Configuration Order 




Go to Advanced and create Add SAN Boot . As we have 2 HBA Qlogic card we need to create 2 SAN BOOT and add the slot accordingly



Name : SAN-BOOT-ORDER

Status : Enabled 

Order : 1

Slot : 4

LUN : 0  ( Note : LUN ID must be verified from storage )

Name : SAN-BOOT-ORDER

Status : Enabled 

Order : 1

Slot : 6

LUN : 0  ( Note : LUN ID must be verified from storage )


3. While booting the server, press Ctrl-Q to enter the Fast!UTIL configuration utility.


4. Do one of the following : 

  • If you have only one host bus adapter (HBA), it is selected automatically, and the Fast!UTIL Options screen appears.

  • If you have more than one HBA, you need to select it manually. In the Select Host Adapter screen, use the cursor keys to select the chosen HBA and press Enter.

    Note: Booting from SAN requires choosing the lowest numbered HBA that has any LUNs visible.


As you can see we have 2 HBA card and total in 4 ports . Now we need to select all those 4 ports inorder to use all of the 4 ports for booting from the lun in case of failover.

 In the Fast!UTIL Options screen, select Configuration Settings and press Enter. ( Noted : Inorder to use all 4 ports we need to configure it all of the 4 ports available.)



Go to Adapter Settings and enable Host Adapter BIOS 






Then go into Selectable boot settings and enabled  selectable boot





NOTE : You will need to enable selectable boot and  Host adapter BIOS in all 4 ports available which has not been displayed in this blog.


5. You will ne able to see the initiator in your storage as well. 



You will now need to create a LUN and attached the host accordingly. 





6 .Booting ESXi




As you can see in the below screenshot LUN has been detected.




Reference 

https://kb.vmware.com/s/article/1448

Comments

Popular posts from this blog

High Availability Palo Alto (Active/Standby)

 High Availability is usually performed in most of the data centers networks today which ensures application availability . High Availability is usually achieved in case one of the appliance goes down or have some physical or logical connectivity issues.  Achieving high availability in Palo Alto firewall is relatively very easy. Palo Alto firewall can work in both Active/Standby mode or in Active/Active. We will basically be talking about Active/Standby mode in this article. There are basically two links that needs to be configure in Palo Alto for HA. 1. Control Links Control Links are associated with control plane traffic which is mainly used for heartbeat exchanged, configuration synchronization. Dedicate HA ports are available in higher series of Palo Alto or even a HA interface can be created for some inband ports.   2. Data Links Data Links are mainly used for session synchronization, forwarding table synchronization. Dedicated HSCI Ports are available for highe...

SAN Switch Zoning with Brocade

Zoning in Brocade SAN Switch Let's begin with resetting the switch completely. In my environment I have two brocade SAN Switch connecting to 2 Dell R940 server configured with VMware. The SAN switch will be having connectivity between Dell Unity 500 storage and Dell R940 servers. Multipathing will be done between the server and storage with the help of SAN Switch. Multipathing, also called SAN multipathing or I/O multipathing, is the establishment of multiple physical routes between a server and the storage device that supports. It results in better fault tolerance and performance enhancement. DESIGN The idea behind zoning is that intended WWPN talk with each other . This is more like ACL in the world of Ethernet. To see the devices which are logged into the switch the following commands can be executed. SAN-A:admin> switchshow switchName: SAN-A switchType: 118.1 switchState: Online switchMode: Native switchRole: Principal switchDomain: 1 switchId: ...

In-Band vs Out of Band Management

There are always multiple ways of allocating IP address when it comes to management of routers and switches. There are dedicated management port as well as things like SVI ( Switch Virtual Interface) can always come into handy. Why to us SVI when you have a dedicated management port might always come into mind. Let me shortly explain the difference between SVI and dedicated management port and also its use case. Out of Band Management Dedicated management port with dedicate management plane  Better in terms of security More preferable In-Band Switch Virtual Interface (SVI) needs to be created  Data Plane is used instead of dedicated management plane. Not preferable in case of security kept in mind. So why In-Band is required ? So , recently I came across a scenario where I had to connect back to back management port for vPC in Nexus 9000 series switch for peer link connectivity. So, I had to create a SVI interface for managing the device . This can be one of the scenario. The ...