HOWTO: Using Dell iDRAC 7 Lifecycle Controller 2 to update R720 server

HOWTO: Using Dell iDRAC 7 Lifecycle Controller 2 to update Dell PowerEdge R420, R620, and R720 servers

 

Newer Dell Servers have an option as part of their iDRAC v7 (Dell Remote Assistance Controller) to include a “Lifecycle Controller” v2.  This feature can be utilized to provide updates to all firmware on a Dell server with minimal stress and interaction.  However – with a non v1.3.0.x Lifecycle Controller firmware, there is no ability to set a VLAN on the NIC’s. These NIC’s are the LOM (LAN Onboard Modules), and in my vSphere environment, these are trunked from the switch to allow VLAN tagging at the host. So when you reboot to the LCC, with no VLAN tagging option, you’re going to find that the “Update via FTP/Network Share” option to not work as well as you might hope. Whether you might be doing this manually/interactively, or via the Dell vSphere Open Manage Integration plug-in, it’s going to require you to fix this first.

This will guide you through the process of doing an ISO based LCC update of all current updates. After that, you’ll be able to do your next round via network – which I’ll cover in another post.

Prerequisites/Assumptions:

1) You have acquired the latest “Q# Server Update Utility DVD ISO” – currently (as of March 11 2014) v7.4 dated 2/1/2014 –http://www.dell.com/support/drivers/us/en/19/DriverDetails/Product/poweredge-r720?driverId=4V8PP&osCode=WS8R2&fileId=3338639762&languageCode=en&categoryId=SM

NOTE: if you do NOT have this ISO, expect it to take 3-4 hours to download even at 500KB/sec, as it is 8.4GB in size

2) You will NOT be using Network based Lifecycle Controller updates with a central FTP or SMB based share, and you will NOT be using Dell Repository Manager to create said repository, but using the above SUU media.

3) The existing iDRAC on the ESXi host in question is functioning normally – allowing both Remote Console and Virtual Media

4) You are able to place the ESXi host(s) into maintenance – either with zero downtime with DRS in a cluster or in a maintenance window for a standalone host (as you will be rebooting the host, so no VM’s or host operations can occur during the update)

Process:

1) Place the host in Maintenance Mode in vSphere and evacuate all VM’s.  Manually resolve any VM migration issues as required.

2) Connect to the iDRAC while the host is entering Maintenance Mode and Launch the Virtual Console.

clip_image002

3) From the Virtual Console, change NEXT BOOT to LIFECYCLE CONTRLLER:

clip_image004

4) From the Virtual Console, click on VIRTUAL MEDIA -> LAUNCH VIRTUAL MEDIA:

clip_image006

5) Click ADD IMAGE, and locate your downloaded ISO:

clip_image008

Check the box for MAPPED to ensure the ISO is mapped to the host

6) By now, your ESXi host should be in maintenance mode.  If so, right click and reboot the host.

7) When the server reboots, it will boot automatically into the Lifecycle Controller, likely to the Network Setup screen:

clip_image010

Note that while you can pick any of the add-in or onboard NIC’s, you are not able to select the iDRAC NIC and/or are you able to specify VLAN ID.  As our vSphere facing ports are all Trunked and require VLAN tag’s, this prevents us from using network based lifecycle updates.  It is likely that this oversight is corrected in an updated version of the Lifecycle Controller.  If so, documentation will be updated to reflect this.  Click CANCEL to exit the Lifecycle Controller Network Setup.

8) From the Lifecycle Controller 2 HOME screen, click FIRMWARE UPDATE:

clip_image012

9) Choose LAUNCH FIRMWARE UPDATE:

clip_image014

10) On Step 1 of 3, choose LOCAL DRIVE (CD or DVD or USB):

clip_image016

Click NEXT.

11) On Step 2 of 3, choose the local (VIRTUAL CD) drive:

clip_image018

Click NEXT.

12) Wait while it VERIFIES SELECTION:

clip_image020

13) You will now see a list of updates for items that are present and available.  This will display both their current and available versions. 

clip_image022

I would recommend installation of ALL available updates to the most current version.  Note that it indicates “System will reboot after selected updates are applied”.   What is convenient about this is we chose the “Next Boot” option to get into the Lifecycle Controller, thus when it reboots, it should reboot normally back into ESXi.   Click APPLY.

14) You will then see it copying the updates to the local flash so it can perform the updates without the Virtual Media.

clip_image024

clip_image026

The next screen shows the AUTOMATED TASK APPLICATION, which shows the progress of the update(s).

clip_image028

Note that prior to the completion of all updates, the system automatically rebooted.  Likely due to update of the Lifecycle Controller itself.  It then automatically selected “ENTERING LIFECYCLE CONTROLLER” as shown, to continue the update process.

clip_image030

And the remaining updates continued as expected…

clip_image032

Understandably, I was surprised to see the system eventually restart back into the Lifecycle Controller. 

15) If you now rescan for FIRMWARE UPDATES from the Virtual Media ISO, you should see that Current matches Available and all components are unchecked as they do not require updates. 

clip_image034

This confirms that we are largely done with the update process.

16) Return to the main menu and enter SETTINGS -> NETWORK SETTINGS:

clip_image036

clip_image038

You will now note that there is a VLAN setting.  This will allow us to utilize the network vs Virtual Media to perform later updates.  Equally, as the Lifecycle Controller can then be network reached, this update process can largely be updated via the Dell vSphere vCenter Server Integration tools and/or Dell Open Manage Express server. 

clip_image040

You should see this screen if the VLAN/DHCP settings worked as expected. 

As this HOWTO is intended to cover performing the updates via Virtual Media ISO, this is where we will stop for now.  A later document will cover how to use network based Lifecycle Controller updates as well as automation with Dell Open Manage Essentials (DOME).  Reboot the server and verify it boots as normally intended.

clip_image042

Press ESC and then YES to Exit and Reboot.

Sometime soon, I’ll post how to create a Dell SUU network repository, and then how to perform a LCC controller update interactively using said network location.

Measure
Measure
 
 

Read more

How to migrate Raspberry Pi 5 OS from micro SD to NVME m.2 SSD

首先我買了Raspberry Pi CM5後來買了Raspberry Pi CM5 I/O board來當個人電腦使用,系統是安裝在256GB SD卡上運行的很好。用久了在開啟較肥的程式像Web Browser或LiberOffice會有慢半拍的反應,而有了升級NVME m.2 SSD念頭。 因為Raspberry Pi 5支援的最快PCIe gen3 x 4就不去考慮快的Gen4 or Gen5 m.2 SSD。找了ADATA出的 LEGEND 710入門級的產品,會利用HMB(Host Memory Buffer)來加速I/O速度,因為是Raspberry Pi OS kernel會認不得而無法正常使用 事先在SD卡的/boot/firmware/cmdline.txt 加入 kernel command line參數如下,然後重開機m.

By Phillips Hsieh

How to document Home Lab and Network

運維機房和跨域的網路,會遇到各式需求與問題,用對工具才能分析問題,個人覺得最重要的是使用能處理問題的工具。 推薦目前想學和正在使用的平台與軟體,協助將公司/家用機房文件化 佈告欄任務管理 Focalboard 白板可管理任務指派 網路架構文件編寫 netbox 精細管理網路設備與連接線路 IP 資源管理 phpipam 專注網路IP分配 邏輯塊文件編寫 draw.io 視覺化概念圖 機房設備管理 ITDB 管理設備生命週期與使用者

By Phillips Hsieh

如何在Raspberry Pi4上安裝Proxmox for ARM64

第一步 準備好Raspberry Pi 4 / CM4 4GB RAM,這裡要留意CM4如果是買有內建eMMC storage會限制不能使用SD卡開機而限制本地空間容量,如果沒有NAS外接空間或使用USB開機的話,建議買CM4 Lite插上大容量SD卡 第二步 去Armbian官網下載最小化Debian bookworm image https://www.armbian.com/rpi4b/ Armbian 25.2.2 Bookworm Minimal / IOT 然後寫入SD/USB開機碟,寫入方法參考官方文件 https://github.com/raspberrypi/usbboot/blob/master/Readme.md Note: 官方提供的預先設定系統方法,可以在Armbian初次啟動自動化完成系統設定。連結在此 https://docs.armbian.com/User-Guide_Autoconfig/

By Phillips Hsieh

世界越快心越慢

在晚飯後的休息時間,我特別享受在客廳瀏灠youtube上各樣各式創作者的影音作品。很大不同於傳統媒體,節目多是針對大多數族群喜好挑選的,在youtube上我會依心情看無腦的動畫、一些旅拍記錄、新聞時事談論。 尤其在看了大量的Youtube的分享後,我真的感受到會限制我的是我的無知,特別是那些我想都沒想過的實際應用,在學習後大大幫助到我的生活和工作層面。 休息在家時,我喜歡想一些沒做過的菜,動手去設計生活和工作上的解決方案,自己是真的很難閒著沒事做。 如創作文章,陪養新的習慣都能感覺到成長的喜悅,是不同於吃喝玩樂的快樂的。 創作不去限制固定的形式,文字是創作、影像聲音也是創作,記錄生活也是創作,我想留下的就是創造—》實現—》回憶,這樣子的循環過程,在留下的足跡面看到自己一路上的成長、失敗、絕望、重新再來。 雖然大部份的時候去做這些創作也不明白有什麼特別的意義,但不去做也不會留下什麼,所以呀不如反事都去試試看,也許能有不一樣的水花也許有意想不到的結果,投資自己永遠不會是失敗的決定,不是嗎?先問問自己再開始計畫下一步,未來沒人說得準。 像最近看youtube仍大一群人在為DOS開

By Phillips Hsieh