Selasa, 13 Desember 2022

Restarting or shutting down controllers HP MSA Series

 


Each controller module contains a Management Controller processor and a Storage Controller processor. When necessary, User can restart or shut down these processors for one controller or both controllers.

top

Restarting controllers

Perform a restart when the SMU informs user that user has changed a configuration setting that requires a restart or when the controller is not working properly.

When user restart a Management Controller, communication with it is lost until it successfully restarts. If the restart fails, the Management Controller in the partner controller module remains active with full ownership of operations and configuration information.

When user restart a Storage Controller, it attempts to shut down with a proper failover sequence. This sequence includes stopping all I/O operations and flushing the write cache to disk. At the end, the controller restarts. Restarting a Storage Controller restarts the corresponding Management Controller.

CAUTION: If user restart both controller modules, all users will lose access to the system and its data until the restart is complete.

NOTE: When a Storage Controller is restarted, current performance statistics that it recorded are reset to zero, but historical performance statistics are not affected. In a dual-controller system, disk statistics may be reduced but are not reset to zero, because disk statistics are shared between the two controllers.

To perform a restart

1.    Perform one of the following:

·         In the banner, click the system panel and select Restart System.

·         In the System topic, select Action > Restart System.

The Controller Restart and Shut Down panel opens.

2.    


3.    


4.    Select the Restart operation

5.    Select the controller type to restart: Management or Storage.

6.    Select the controller module to restart: Controller A, Controller B, or both.

7.    Click OK. A confirmation panel appears.

8.    Click OK to continue. Otherwise, click Cancel. If user clicked OK, a message describes restart activity

top

Shutting down controllers

Perform a shut down before user remove a controller module from an enclosure, or before user power off its enclosure for maintenance, repair, or a move. Shutting down the Storage Controller in a controller module ensures that a proper failover sequence is used, which includes stopping all I/O operations and writing any data in write cache to disk. If user shut down the Storage Controller in both controller modules, hosts cannot access system data and the SMU will be unavailable.

CAUTION: User can continue to use the CLI when either or both Storage Controllers are shut down, but some information might not be available.

To perform a shut down:

1.    . Perform one of the following:

·         In the banner, click the system panel and select Restart System.

·         In the System topic, select Action > Restart System.

The Controller Restart and Shut Down panel opens.

2.    Select the Shut Down operation, which automatically selects the Storage controller type.

3.    Select the controller module to shut down: Controller A, Controller B, or both

4.    Click OK. A confirmation panel appears.

5.    Click OK to continue. Otherwise, click Cancel. If user clicked OK, a message describes shutdown activity.

 

Upgrading the firmware of an Emulex FC HBA on VMware ESXi

 


A method for upgrading the Emulex FC HBA firmware


 

Preparation

Download Elxflash Standalone Utility for ESXi

Download Firmware file lancer_A11.4.204.20.grp

Elxflash Standalone

Masuk ke folder elxflash standalone yang sudah di unzip. Didalmnya ada 3 folder boot esxi dan firmware

# /tmp/elxflashStandalone-esxi-11.4.142.18-3 # ls -l

total 768

drwxr-xr-x 1 root root 8 Dec 12 13:07 boot

drwxr-xr-x 1 root root 8 Dec 14 16:55 esxi

drwxr-xr-x 1 root root 8 Dec 13 15:11 firmware

Put in Firmware file to firmware folder

Lalu masuk ke folder firmware dan simpan file firmware *.grp ke dalam folder tersebut

# cd /tmp/elxflashStandalone-esxi-11.4.142.18-3/ firmware

lancer_A11.4.204.20.grp

 

kembali ke folder esxi yang di dalamnya ada file elxflash.sh, linlpcfg.sh dan folder i386

# cd /tmp/elxflashStandalone-esxi-11.4.142.18-3/esxi

elxflash.sh

i386

linlpcfg.sh

change attribute or permission file

Rubah permission ke write read and execute dengan command chmod lalu jalankan command ./elxflash.sh /q untuk melihat firmweare existing

# chmod +x elxflash.sh

# ./elxflash.sh /q

HBA=LPe16000, Port Type=FC, WWN=10:00:00:90:FA:1C:C7:F4, PCI ID=E200, VID=10DF, SSID=E205, SVID=10DF, Firmware=11.4.142.23, Boot Code=11.4.142.23, Boot Enabled=1

 

elxflash: All required queries succeeded - Return Code=0

Upgrade or Downgrade prosses

Di tahap ini adalah eksekusi untuk proses upgrade atau downgrade firmwarenya, jalankan command di bawah ini

# ./elxflash.sh /auto /update (if Upgrade)

# ./elxflash.sh /auto /downgrade (if downgrade)

Output proses upgrade berhasil

Tue Dec 12 14:26:39 2017

HBA=LPe16000, Port Type=FC, WWN=10:00:00:90:FA:1C:C7:F4,

Update=Firmware, Image=lancer_A11.4.204.20.grp, New=11.4.204.20, Old=11.4.142.23, Status=Success

 

elxflash: All required updates succeeded - Return Code=0

Check and reboot

lakukan pengecekan kembali untuk firmware yang sudah di apply ke hba

# ./elxflash.sh /q

 

HBA=LPe16000, Port Type=FC, WWN=10:00:00:90:FA:1C:C7:F4, PCI ID=E200, VID=10DF, SSID=E205, SVID=10DF, Firmware=11.4.204.20, Boot Code=11.4.204.20, Boot Enabled=1

 

elxflash: All required queries succeeded - Return Code=0

 

Restart host

#reboot