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
Labels:

Comments

Post a Comment

Popular posts from this blog

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: ...
Post a Comment
Read more

Upgrade Catalyst C9500

Upgrading Catalyst 9500 series switch is relatively easy. The one that I'm going to upgrade today is on Install mode containing packages.conf file. Install mode consumes far less resources in compared to the traditional bundle mode and has some advantage like auto upgrade when configured in stacked mode. We can talk about the difference between bundle and install mode later on. Let's focus on upgrading the Catalyst 9500 switch. Switch I am trying to upgrade is in 17.03.03 which has some bugs and security vulnerabilities. I am upgrading it from 17.03.03 to 17.6.5(MD) golden image present in the cisco download site for C9500 series switch and also reading down the linked document from cisco that is what they recommend. You can have a look at it . https://www.cisco.com/c/en/us/support/docs/switches/catalyst-9300-series-switches/221498-recommended-releases-for-catalyst-9200-9.html We will first need to create FTP username and password in the switch. The username and password must b...
1 comment
Read more

POLICY ROUTES FORTIGATE

 Policy routes also referred to as policy based routing is a very popular technique that routes the incoming packets based on the set of policy defined. The policy usually defines that the packet from particular source are routed to particular gateway.  Simply not trying to make it theoretically lengthy lets try this feature out in Fortigate. In our particular scenario there are 2 fortigate boxes residing in HA (Active/Passive) mode. There are two upstream ISP connected with the fortigate box one named after port 1 SUBISU and the other being port 2  WEBSURFER. We have two internal gateways which contains subnet of 172.16.0.0/28 and the other one being 172.16.0.16/28. We will be leveraging the privilege of policy route and send the packet incoming from 172.16.0.0/28 subnet towards Websurfer upstream and the packet coming from 172.16.0.16/28 subnet towards SUBISU upstream which will help us on utilizing both the links making it more efficient usage of bandwidth. We will nee...
Post a Comment
Read more