Hitachi / Remote Ops Service Processor Agent Version D.6

Hitachi Remote Operations (önceki adı ile Hi-Track, kısaca HRO) yazılımı aktif kontratı bulunan sistemlerin sağlık durumlarının düzenli olarak raporlanmasını ve bir arıza durumunda otomatik olarak çağrı kaydı oluşturulmasını sağlayan bir servistir.

Yeni versiyona geçişte önceki versiyondan tüm ayarlar korunduğu için bir değişiklik ya da düzenleme yapılmasına gerek bulunmuyor, sistem eski versiyonu silerek yenisini aynı ayarlar ile kuruyor.

Download:
Support Portal’e login olduktan sonra Answers / Downloads /  Software Download / Remote Ops (Hi-Track)  seçip ekranın en altındaki menüden Remote Ops Agent seçip D6 ISO download ediyoruz.

ISO’yu SVP üzerine kopyalayıp extract ettikten sonra kurulum uygulamasını çalıştırdığımızda eski versiyonu uninstall edip yenisini kuruyor.

 

Kurulum sonrasında servislerin durumlarını uygulama üzeriden kontrol ediyoruz.

IBM Storwize / satask restartservice

Syntax
>>- satask -- restartservice -- -service -- service_name -- panel_name-><
Parameters
sataskSystem Administrator task; service commands that are only used in specific circumstances.
-service service_nameSpecifies the name of the service that you want to restart. The following services are supported:
sshd               Secure Shell Daemon
slpd               Service Location Protocol Daemon
easy               Easy Tier®
tomcat            Web server
cimom            CIMOM
panel_name   Identifies the node being serviced.

Description
When directed to do so by IBM® support, use this command to restart a named service.
An invocation example

satask restartservice -service tomcat

satask restartservice -service cimom

https://www.ibm.com/support/knowledgecenter/en/STLM5A/com.ibm.storwize.v3700.641.doc/svc_restartservice03171204.html

IBM Storwize / lsarraymemberprogress

IBM_Storwize:V3700:superuser>lsarraymemberprogress
mdisk_id mdisk_name member_id drive_id task     new_drive_id progress estimated_completion_time
0        mdisk1     7         20       exchange 9            23       180124172214

IBM Storwize / Remove all system information

IBM Storwize / Remove all system information

This procedure guides you through the process to completely remove all system information. When the procedure is finished, the system performs like a new installation.

Attention: This procedure makes all the volume data that you have on your system inaccessible. You cannot recover the data. This procedure affects all volumes that are managed by your system, which includes the drives in the control enclosure, in the expansion enclosures, and on the managed disks on external storage systems. The only volumes not affected are image mode volumes on external storage systems.

Do not continue unless you are certain that you want to remove all the volume data and configuration data from your system. This procedure is not used as part of any recovery action.

There are two stages to this procedure. First, the node canisters are reset. Second, the enclosure data is reset.

Procedure

1. Start the service assistant on one of the node canisters.
2. Use the service assistant node action to hold the node in service state.
3. Use the Manage System option to remove the system data from the node.
4. Perform the previous steps on the second node canister in the enclosure and then on every node in every other enclosure in the system.
5. On one node in every enclosure, open the service assistant Configure Enclosure and select the Reset System ID option.
   This action causes the system to reset.
6. Power each enclosure off and on before creating a system.

http://www.ibm.com/support/knowledgecenter/ST3FR7_6.4.1/com.ibm.storwize.v7000.641.doc/tbrd_dltclstr_9090sd.html

IBM Storwize V7000 disk firmware upgrade test

IBM Storwize V7000 disk firmware upgrade test

pscp.exe ile diğer firmware ve upgrade test dosyları aynı klasör içerisinde bulunmalı

upgrade test uygulmasını storvize içerisine almak için aşağıdaki komutları kullanıyoruz.

pscp.exe IBM2076_INSTALL_upgradetest_15.15 superuser@10.10.10.45:/home/admin/upgrade

superuser@10.10.10.45's password:

IBM2076_INSTALL_upgradete | 66 kB |  66.8 kB/s | ETA: 00:00:00 | 100%

Disk firmware dosyamızı benzeri şekilde storwize içerisine alıyoruz.

pscp.exe IBM2076_DRIVE_20150619  superuser@10.10.10.45:/home/admin/upgrade

superuser@10.10.10.45's password:

IBM2076_DRIVE_20150619    | 51860 kB | 25930.3 kB/s | ETA: 00:00:00 | 100%

------------------------------------------------------------------------------

Storwize V7000 üzerinden aşağıdaki komutları çalıştırıyoruz.

login as: superuser
superuser@10.10.10.45's password:
IBM_Storwize:Storwize7000:superuser>

Upgrade uygulamasını aktif etmek için aşağıdaki komutu kullanıyoruz.
IBM_Storwize:Storwize7000:superuser>svctask applysoftware -file
IBM2076_INSTALL_upgradetest_15.15

CMMVC6227I The package installed successfully.


Upgrade test işlemine başlamak için svcupgradetest komutunu kullanıyoruz.

IBM_Storwize:Storwize7000:superuser>svcupgradetest -f -d

svcupgradetest version 15.15

Please wait, the test may take several minutes to complete.


******************* Warning found *******************

This tool has found the internal disks of this system are
not running the recommended firmware versions.
Details follow:

+----------------------+-----------+------------+------------------------------------------+
| Model                | Latest FW | Current FW | Drive Info                               |
+----------------------+-----------+------------+------------------------------------------+
| ST9300653SS          | B63M      | B63L       | Drive   23 in slot 10 in enclosure  2    |
|                      |           |            | Drive   24 in slot 14 in enclosure  2    |
|                      |           |            | Drive   25 in slot 23 in enclosure  2    |
|                      |           |            | Drive   26 in slot 20 in enclosure  2    |
|                      |           |            | Drive   27 in slot 15 in enclosure  2    |
|                      |           |            | Drive   28 in slot 16 in enclosure  2    |
|                      |           |            | Drive   29 in slot 22 in enclosure  2    |
|                      |           |            | Drive   30 in slot 24 in enclosure  2    |
| ST900MM0006          | B56S      | B56N       | Drive  230 in slot 17 in enclosure  7    |
|                      |           |            | Drive  231 in slot 18 in enclosure  7    |
|                      |           |            | Drive  232 in slot 19 in enclosure  7    |
|                      |           |            | Drive  233 in slot 20 in enclosure  7    |
|                      |           |            | Drive  235 in slot 22 in enclosure  7    |
|                      |           |            | Drive  236 in slot 23 in enclosure  7    |
|                      |           |            | Drive  237 in slot 24 in enclosure  7    |
|                      |           |            | Drive  238 in slot 24 in enclosure  1    |
|                      |           |            | Drive  239 in slot 23 in enclosure  5    |
|                      |           |            | Drive  240 in slot 21 in enclosure  7    |
+----------------------+-----------+------------+------------------------------------------+

We recommend that you upgrade the drive microcode at an
appropriate time. If you believe you are running the latest
version of microcode, then check for a later version of this tool.
You do not need to upgrade the drive firmware before starting the
software upgrade.

Results of running svcupgradetest:
==================================

The tool has found 0 errors and 1 warnings.

IBM_Storwize:Storwize7000:superuser>

IBM Storwize V7000 - Source and target pools must have the same extent size

Bir volumu başka bir pool üzerine taşımak istediğimizde, aşağıdaki uyarı ile birlikte taşınacak hiç bir pool gözükmeyebilir.

Böyle bir durumda volumu başka bir pool üzerine taşıma için mirrored özelliğini kullanabiliriz.

Mirrored volumun yeni pool üzerinde oluşması ile eski poldaki volume silinebilir.


You selected to migrate the volume WINOS in pool SSD_DISK_POOL.

Select the new pool that this volume will be migrated to.

Source and target pools must have the same extent size.