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>

How to Shadow a Terminal Server Session Without Prompt for Approval

How to Shadow a Terminal Server Session Without Prompt for Approval

Shadow Error "The oprerator or administrator has refused the request"

If you would like to shadow the Terminal Server sessionand you do not want to be prompted for permission, set the local Group Policy on the server that is running Terminal Services.

To remote control the console with no prompt for approval:

1. Open Group Policy Editor (Gpedit.msc) on the server that is running Terminal services.
2. Under Computer Configuration, expand Administrative templates, expand Windows Components, and then click Remote Desktop Services, and then click Remote Desktop Session Host, Connections.
3. Right-click Sets rules for remote control of Remore Desktop Service user sessions, and then clickProperties.
4. Select the Enabled option.
5. Under Options, click Full Control without user's permission.

Installation of component VCSServiceManager failed with error code '1603

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2113068

Cause

This issue occurs when the vCenter Servers Data Source Name (DSN) has a trailing space at the end of its name.

Resolution

This is a known issue affecting vCenter Server 6.0.

To resolve this issue, edit and rename the vCenter Server's DSN and remove the trailing space.

To edit and rename the vCenter Server's DSN and remove the trailing space:

1. Log in to the vCenter Server as an administrator.
2. Click Start > Control Panel > Administrative Tools > Data Sources (ODBC).
3. Click the System DSN tab.
4. In System Data Sources, select the Data Source that vCenter Server is using, as noted in the previous section of this article.
5. Click Configure.
6. In the Configure pane, you see the name of the configured database server in the server text box. Update the DSN to remove the trailing white space.
7. Click Next.
8. Enter the appropriate log in credentials on the next page.
   
   Note: The log in information here is not saved, it is simply used for the configuration and testing of the Data Source.
   
9. Complete the wizard and run the installation again.