Лезвия
Я описывал процедуру обновления
здесь.
AMM модуль BladeCenter
Все
просто, скачивается с нужного раздела сайта IBM и заливается через
раздел “MM Control – Firmware update” веб интерфейса собственно AMM.
Обновлять стоит, с ростом версии хорошеет IPMI и прочие мелочи.
FC Brocade
Проверялось на p/n 32R1819.
- Через сайта IBM скачивается необходимая версия прошивки. Там будет редирект на сайт broacde.
- Перед
прошивкой - разархивировать до состояния папки, корневой папкой для
прошивки считается самый верхний каталог из архива с большим количеством
папок/файлов.
- Прошивать лучше подключаясь через ssh/telnet
- Листинг кода
brocade4Gb:USERID> firmwaredownload
Do you want to continue [Y]: y
Server Name or IP Address: 192.168.150.52 // IP сервера FTP сервера где лежит прошивка.
User Name: user
File Name: /v5.2.2 /v5.2.2/release.plist
Password: ****
Firmwaredownload has started.
Комментарии:
- Файла
release.plist в этом каталоге реально нету. т.е. указываем путь к
корневому каталогу с прошивкой, и приписываем к нему имя этого файла.
Несмотря на реальное отсутствие файла в файловой системе, все нормально
перешьется.
- Обновлять прошивки надо в таком порядке: 5.0.5 - 5.2.2 - 5.3.1 -6.0.1a - 6.1.0
- После
обновления первичной прошивки и перезагрузки свитча, начинается процесс
обновления вторичной прошивки. Это происходит в фоновом режиме и
требует какого то времени (10-15 мин). Состояние этого процесса можно
отследить командой "firmwaredownloadstatus" в течении этой подгрузки
загрузить новую версию не получится, будет выдаваться ошибка.
- От
версии к версии может меняться способ заливки прошивки на систему, я
всегда пользовался FTP. Если что то меняется, то об этом наглядно
пишется в консоли. У меня сложностей не возникало. Наиболее простой с
моей точки зрения вариант FTP сервера – FileZilla.
FC Cisco
Проверялось на p/n 39Y9281.
Eth BNT (Nortel)
Проверялось на p/n 32R1866.
- Идеология
такая: есть 3 банка (1,2 - независимые ОС, 3 - загрузчик). Процесс
обновления для разных версий критически различается. Сначала смотрим
версию - затем думаем - затем шьем.
Апдейт с версий ранее 1.2.5.1 до 1.2.5.1
Листинг:
1. #/boot/gtimg X TADDR GbESM-AOS-1.2.5.1_OS.img
2. #/boot/image X
3. #/boot/reset
4. (reboot)
5. #/boot/gtimg boot TADDR GbESM-ABoot-1.2.5.1_boot.img
6. #/boot/reset
7. (reboot)
Апдйет версий старше 1.2.5.1
Листинг:
1. #/boot/gtimg X TADDR GbESM-AOS-1.5.1.0_OS.img
2. #/boot/image X
3. #/boot/gtimg boot TADDR GbESM-AOS-1.5.1.0_boot.img
4. #/boot/reset
5. (reboot)
В 2-х абзацах выше
X - имя прошиваемого банка [image1 | image2]
TADDR - ip адрес сервера TFPT
*.img - файлы с прошивками
Комментарии:
- Шить через telnet.
- Несмотря на указанную возможность использования FTP использовать только TFPT.
- Скачать прошивку 1.2.5.1 просто так нельзя. На сайте IBM указателя на неё - нету. Нужна она для апдейта старых версий. http://www.bladenetwork.net/media/ZIPs/GbESM-AOS-1.2.5.1.zip
- Для скачки чего либо с www.bladenetwork.net
необходимо зарегится и зарегить свой продукт (иначе доступа не будет).
Для этого нужен его серийник который можно посмотреть через
#/info/sys/general - в консоли.
- Краткое пояснение команд
#/boot/gtimg - загрузка прошивки с TFPT в 1-ый или 2-ой банк памяти
#/boot/image - выбор с какого банка грузится следующий раз
#/info/sys/general - инфа о системе
#/boot/cur - просмотр текущих версий прошивок
Eth Cisco
Проверялось на p/n 32R1894.
Листинг:
>enable
#archive download-sw tftp://<xxx.yyy.zzz.aaa>/<image>
#reload
Комментарии:
- Полное название CIGESM
- Наименование прошивки - cigesm-i6q4l2-tar.121-22.ea12.tar
- Разархивировать – не надо.
- В текущей версии прошивки (show version) должно быть четко указано название железки (от начала файла до первого тире).
- На
сайте IBM к блэйду можно найти не только cigesm но и 3*** серию.
причем, что это 3*** говорится далеко не сразу можно не заметить.
определяем по названию файла. прошивка сливается с сайта IBM из суппорта
раздел Networking по BladeCenter.
- Прошивка делается с TFTP.
- Подключаться к свитчу обязательно через COM порт.
спасибо )
Прошивка SAS RAID CONTROLLER
Lenovo BladeCenter S RAID SAS Switch Module Firmware
Version 2.3.4.035, Build ID: S0CL234035 update via Windows
Windows Installation Notes
----------------------------
CONTENTS
-------------------------------------------------------------------------------
1.0 Windows Prerequisite Setup (DOS) (Setting up the command line firmware
upgrade tool)
2.0 Install Procedure (Windows - DOS)
--------------------------------------------------------------------------------
General Notes
--------------------------------------------------------------------------------
The Command Line Firmware Update should be run in a "serial" mode when running
from Windows.
Only one firmware update should be running at any time on a single machine.
Running multiple instances of the Command Line Firmware Update simultaneous is not
supported.
The Command Line Firmware Update Tool requires a minimum Python level of 2.5.4.
Python 3.x is not supported.
All unrelated programs should be closed before running this installation process.
Only a single IP address is supported on the system performing the update, or
system may encounter below telnet error message.
MSG:./SbInst.py failed in function runTelnetCmd, rc = 8.
1.0 Windows Prerequisite Setup (DOS)
--------------------------------------------------------------------------------
Before installing the command line firmware upgrade tool the following utility
must be downloaded and installed on the system which will be used for the
upgrade.
- Python (www.python.org) version 2.5.4 or higher
1.1 Install python 2.5.4 or greater. Python 3.x is not supported.
- Use the standard install method provided with the python package.
1.1.1 Configure Windows Environment Variable
- After the Python installation completes, configure windows by adding
the following environment variable:
- Click on the Start button -> Settings -> Control Panel
- At the Control Panel, select System
- From the System Properties window, select the Advanced tab
- Click on the Environment Variables button
- Within the User variables list or the System variables list select
the PATH variable then click on the Edit button
- Add the directory where Python was installed to the end of the
Variable value xxxx;xxxx;<Full Python Directory Path>
- Click on the OK button to close the Edit window
- Click on the OK button to close the Environment Variables panel
- Click on the OK button to close the System Properties panel
- Close the Control Panel
- Close any open DOS windows on the system and re-open as necessary.
1.2 Once the environment is set up, continue with downloading and Installing
the SAS RAID Module Firmware Update Package.
2.0 Install Procedure via Windows - DOS
--------------------------------------------------------------------------------
2.1 Installation Procedure Notes - IMPORTANT
2.1.1 SAS RAID Module Firmware Update Package Version 2.3.4.035 supports
Non-Concurrent Code Load (NCCL).
NOTE: The -n option in the command line for NCCL upgrade inhibits the
Pre-verify system check.
2.1.2 SAS RAID Module Firmware Update Package Version 2.3.4.035 supports
Concurrent Code Load (CCL) if a system is currently at
Version 1.2.1.015(PGA1) and newer versions.
IMPORTANT: The drive FW will NOT be updated if Concurrent Code Load
is used to upgrade.
This may result in a 4301 maskable alert being reported for any drive
with firmware different to the drive firmware in this Update Package.
NOTE: There is no -n option in the command line for a CCL firmware
update.
The Pre-Verify system check verifies the health of the system before
initiating the firmware update.
2.1.3 SAS RAID Module Firmware Update Package Version 2.3.4.035 supports a
Single controller configuration.
For a Single Controller configuration, Non-Concurrent Code Load must
be used, Concurrent Code Load is not applicable.
2.1.4 Prior to starting the firmware download and upgrade process all
persistent alerts must be resolved.
View the Active Alert List to verify if there are any persistent
alert(s) that require resolution.
In some instances, a persistent alert may be resolved by upgrading the
firmware.
Check the release letter content to determine if there are persistent
alert(s) that are fixed in this level of code.
2.1.5 If an alert 4101 is active, the diagnostic data should be retrieved
using the First Time Data Capture Utility before proceeding with the
firmware update process.
2.1.6 The DOS installation process is supported on Windows XP, Windows 2003,
Windows 2008 and Windows 7. Windows Vista is not supported.
2.1.7 For an NCCL firmware update, all IO processes must be shut down before
performing the firmware update.
2.2 Firmware Update - Bound Controllers - Non-Concurrent Code Load
2.2.1 Both RAID controllers must be rebooted into Service Mode.
From one of the controller CLI issue the following command:
<CLI> shutdown -system -state servicemode
Both of the RAID controllers will reboot into Service Mode. Login to
one of the RAID controllers and verify that both controllers are
in Service Mode by issuing the following command from the controller
CLI:
<CLI> list controller
Example output:
__________________________________________________________
| Ctlr# | Controller | Status | Ports | LUNs |
|________|____________|__________________|________|________|
| 0 | Ctlr0| SERVICE| 1| --|
| 1 | Ctlr1| SERVICE| 1| --|
|________|____________|__________________|________|________|
2.2.2 From a Windows-based system (XP, 2003, 2008 or Windows 7) create a
directory from which the code load will be performed.
Example: C:\codeload (make sure there are no spaces in the path name)
2.2.3 Download the code executable file
(lnvgy_fw_bcsw_s0cl-N.N.N.NNN_windows_noarch.bat) into the code load
directory.
2.2.4 Start the SAS RAID Module Firmware Update Installation
The syntax for the code installation command is provided below where
N.N.N.NNN is the build number of the downloaded package and
X.XXX.XXX.XXX is the IP address of one of the SAS RAID controllers.
NOTE: This command assumes that the default passwords on the
controllers have not been changed.
lnvgy_fw_bcsw_s0cl-N.N.N.NNN_windows_noarch.bat -i X.XXX.XXX.XXX -n
If the controllers have custom passwords then the following
syntax must be used where N.N.N.NNN is the build number of the
downloaded package, X.XXX.XXX.XXX is the IP address of either SAS
RAID controller and the following passwords are provided:
-passwd <Controller cli password>, -sas_p1 <SAS Switch Bay3 cli
password>, -sas_p2 <SAS Switch Bay4 cli password>, and -ftx_pwd
<mgmnt interface password>.
lnvgy_fw_bcsw_s0cl-N.N.N.NNN_windows_noarch.bat -i X.XXX.XXX.XXX -n
-passwd XXXXXXXX -sas_p1 XXXXXXXX -sas_p2 XXXXXXXX
-ftx_pwd XXXXXXXX
2.3 Firmware Update - Bound Controllers - Concurrent Code Load
NOTE: The system being upgraded must be at the Minimum Version 1.2.1.015
(H-2.1.1.2).
2.3.1 The RAID controllers must be in the bound state.
Verify the controllers are in the bound state by issuing the
following command from the controller CLI:
<CLI> list controller
Example output:
__________________________________________________________
| Ctlr# | Controller | Status | Ports | LUNs |
|________|____________|__________________|________|________|
| 0 | Ctlr0| PRIMARY| 1| 2|
| 1 | Ctlr1| SECONDARY| 1| 1|
|________|____________|__________________|________|________|
Verify the current RAID controller SW Version is 1.2.1.015 or above by
issuing the following command from the controller CLI:
<CLI> swversion
The Software Version must be H-2.1.1.2 or newer versions.
The Package Build No must be 1.2.1.015 or newer versions.
2.3.2 From a Windows-based system (XP, 2003, 2008 or Windows 7)create a
directory from which the code load will be performed.
Example: C:\codeload (make sure there are no spaces in the path name)
2.3.3 Download the code executable file
(lnvgy_fw_bcsw_s0cl-N.N.N.NNN_windows_noarch.bat) into the code load
directory.
2.3.4 Start the SAS RAID Module Firmware Update Installation
The syntax for the code installation command is provided below where
N.N.N.NNN is the build number of the downloaded package and
X.XXX.XXX.XXX is the IP address of one of the SAS RAID controllers.
NOTE: This command assumes that the default passwords on the
controllers have not been changed.
lnvgy_fw_bcsw_s0cl-N.N.N.NNN_windows_noarch.bat -i X.XXX.XXX.XXX
If the controllers have custom passwords then the following
syntax must be used where N.N.N.NNN is the build number of the
downloaded package, X.XXX.XXX.XXX isthe IP address of either SAS
RAID controller and the following passwords are provided:
-passwd <Controller cli password>, -sas_p1 <SAS Switch Bay3 cli
password>, -sas_p2 <SAS Switch Bay4 cli password>, and -ftx_pwd
<mgmnt interface password>.
lnvgy_fw_bcsw_s0cl-N.N.N.NNN_windows_noarch.bat -i X.XXX.XXX.XXX
-passwd XXXXXXXX -sas_p1 XXXXXXXX -sas_p2 XXXXXXXX
-ftx_pwd XXXXXXXX
2.3.5 If the Pre-verify fails, check the Alerts and clear any issues
associated with these Alerts.
Reboot the controller to clear the Pre-Verify failure Alert(s).
Restart the firmware update.
2.4 Firmware Update - Single Controller - Non-Concurrent Code Load
2.4.1 The Single controller is in Bay 3.
NOTE: A single controller status in the list controller output
is STANDALONE.
<CLI> list controller
Example output:
__________________________________________________________
| Ctlr# | Controller | Status | Ports | LUNs |
|________|____________|__________________|________|________|
| 0 | Ctlr0| STANDALONE| 1| 2|
| 1 | Ctlr1| NOTAVAILABLE| -| --|
|________|____________|__________________|________|________|
The RAID controller must be rebooted into Service Mode.
From the controller CLI issue the following command:
<CLI> shutdown -ctlr 0 -state servicemode
The RAID controller will reboot into Service Mode. Login to the
RAID controller and verify that the controller is in Service Mode
by issuing the following command from the controller CLI:
<CLI> list controller
Example output:
___________________________________________________________
| Ctlr# | Controller | Status | Ports | LUNs |
|________|____________|___________________|________|________|
| 0 | Ctlr0| SERVICE| 1| --|
| 1 | Ctlr1| NOTAVAILABLE| -| --|
|________|____________|___________________|________|________|
2.4.2 From a Windows-based system (XP, 2003, 2008 or Windows 7) create
a directory from which the code load will be performed.
Example: C:\codeload (make sure there are no spaces in the path name)
2.4.3 Download the code executable file
(lnvgy_fw_bcsw_s0cl-N.N.N.NNN_windows_noarch.bat)
into the code load directory.
2.4.4 Start the SAS RAID Module Firmware Update Installation
The syntax for the code installation command is provided below where
N.N.N.NNN is the build number of the downloaded package and
X.XXX.XXX.XXX is the IP address of one of the SAS RAID controllers.
NOTE: This command assumes that the default passwords on the
controllers have not been changed.
lnvgy_fw_bcsw_s0cl-N.N.N.NNN_windows_noarch.bat -i X.XXX.XXX.XXX -n
If the controllers have custom passwords then the following
syntax must be used where N.N.N.NNN is the build number of the
downloaded package, X.XXX.XXX.XXX isthe IP address of either SAS
RAID controller and the following passwords are provided:
-passwd <Controller cli password>, -sas_p1 <SAS Switch Bay3 cli
password>, -sas_p2 <SAS Switch Bay4 cli password>, and -ftx_pwd
<mgmnt interface password>.
lnvgy_fw_bcsw_s0cl-N.N.N.NNN_windows_noarch.bat -i X.XXX.XXX.XXX -n
-passwd XXXXXXXX -sas_p1 XXXXXXXX -sas_p2 XXXXXXXX
-ftx_pwd XXXXXXXX
This question has not been answered yet.