Hi,
We cannot expect much performance when the array has just archive tier hard drives.
The disk IOPS seems to be normal.
Usually archive tier disk IOPS will report consistently high values above 300 if there is a huge latency.
It would be better to log an HPE support case so that debug logs could be verified whether the disks are overloaded consistently. This will also help to check whether any specific disk is reporting errors.
May I aks you to do the following:
Clear Browser Cache and Cookies:
Use a Different Browser:
Reset the MSA 2062:
Update Firmware:
Connect via CLI:
Try Default Admin Credentials:
Network Configuration:
Thank you for your response.
set ciphers list ALL:!TLS_RSA_WITH_AES_128_GCM_SHA256:!TLS_RSA_WITH_AES_256_CBC_SHA256:!TLS_RSA_WITH_AES_256_CCM:!TLS_RSA_WITH_AES_ 256_CCM_8:!TLS_RSA_WITH_AES_256_GCM_SHA384"
After executing the above, the following cipher suites, including the specified cipher suite, were activated. Is there a problem with the way I specified it?
------------------------------------
TLS_DHE_RSA_WITH_AES_128_CBC_SHA
TLS_DHE_RSA_WITH_AES_256_CBC_SHA
TLS_DHE_RSA_WITH_CAMELLIA_128_CBC_SHA
TLS_DHE_RSA_WITH_CAMELLIA_256_CBC_SHA
TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA
TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA
TLS_RSA_WITH_AES_128_CBC_SHA
TLS_RSA_WITH_AES_128_CBC_SHA256
TLS_RSA_WITH_AES_128_CCM
TLS_RSA_WITH_AES_128_CCM_8
TLS_RSA_WITH_AES_128_GCM_SHA256
TLS_RSA_WITH_AES_256_CBC_SHA
TLS_RSA_WITH_AES_256_CBC_SHA256
TLS_RSA_WITH_AES_256_CCM
TLS_RSA_WITH_AES_256_CCM_8
TLS_RSA_WITH_AES_256_GCM_SHA384
TLS_RSA_WITH_ARIA_128_GCM_SHA256
TLS_RSA_WITH_ARIA_256_GCM_SHA384
TLS_RSA_WITH_CAMELLIA_128_CBC_SHA
TLS_RSA_WITH_CAMELLIA_128_CBC_SHA256
TLS_RSA_WITH_CAMELLIA_256_CBC_SHA
TLS_RSA_WITH_CAMELLIA_256_CBC_SHA256
------------------------------------
新たに指摘された暗号スイートを指定して以下のコマンドを改めて実行すれば、指定された暗号スイートを無効化できるものと考えておりますが、認識に誤りはありませんでしょうか。
「set ciphers list ALL:!TLS_DHE_RSA_WITH_AES_128_CBC_SHA:!TLS_DHE_RSA_WITH_AES_256_CBC_SHA:!TLS_DHE_RSA_WITH_CAMELLIA_128_CBC_SHA:!TLS_DHE_RSA_WITH_CAMELLIA_256_CBC_SHA:!TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA:!TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA:!TLS_RSA_WITH_AES_128_CBC_SHA:!TLS_RSA_WITH_AES_128_CBC_SHA256:!TLS_RSA_WITH_AES_128_CCM:!TLS_RSA_WITH_AES_128_CCM_8:!TLS_RSA_WITH_AES_128_GCM_SHA256:!TLS_RSA_WITH_AES_256_CBC_SHA:!TLS_RSA_WITH_AES_256_CBC_SHA256:!TLS_RSA_WITH_AES_256_CCM:!TLS_RSA_WITH_AES_256_CCM_8:!TLS_RSA_WITH_AES_256_GCM_SHA384:!TLS_RSA_WITH_ARIA_128_GCM_SHA256:!TLS_RSA_WITH_ARIA_256_GCM_SHA384:!TLS_RSA_WITH_CAMELLIA_128_CBC_SHA:!TLS_RSA_WITH_CAMELLIA_128_CBC_SHA256:!TLS_RSA_WITH_CAMELLIA_256_CBC_SHA:!TLS_RSA_WITH_CAMELLIA_256_CBC_SHA256」
それとも一旦、以下のコマンドでデフォルト設定に戻すべきでしょうか。
「reset ciphers」
Since I posted this in Japanese, I will correct it and post it again.
I am assuming that I can disable the specified cipher suite by running the following command again, specifying the newly indicated cipher suite.
set ciphers list ALL:!TLS_DHE_RSA_WITH_AES_128_CBC_SHA:!TLS_DHE_RSA_WITH_AES_256_CBC_SHA:!TLS_DHE_RSA_WITH_CAMELLIA_128_CBC_SHA:!TLS _DHE_RSA_WITH_CAMELLIA_256_CBC_SHA:!TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA:!TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA:!TLS_RSA_WITH_AES_128_! CBC_SHA:!TLS_RSA_WITH_AES_128_CBC_SHA256:!TLS_RSA_WITH_AES_128_CCM:!TLS_RSA_WITH_AES_128_CCM_8:!TLS_RSA_WITH_AES_128_GCM_SHA256:! TLS_RSA_WITH_AES_256_CBC_SHA:!TLS_RSA_WITH_AES_256_CBC_SHA256:!TLS_RSA_WITH_AES_256_CCM:!TLS_RSA_WITH_AES_256_CCM_8:!TLS_RSA_WITH_ AES_256_GCM_SHA384:!TLS_RSA_WITH_ARIA_128_GCM_SHA256:!TLS_RSA_WITH_ARIA_256_GCM_SHA384:!TLS_RSA_WITH_CAMELLIA_128_CBC_SHA:!TLS_RSA TLS_RSA_WITH_CAMELLIA_128_CBC_SHA256:!TLS_RSA_WITH_CAMELLIA_256_CBC_SHA:!TLS_RSA_WITH_CAMELLIA_256_CBC_SHA256"
Or should I just restore the default settings with the following command?
reset ciphers".
hello@y-tanaka0805,
Reset the cipher suites and then activate the ciphers which you want and do not specify 'ALL' when setting ciphers. All ciphers will be activated if you specify the ALL option.
The 'reset ciphers' command clears user-supplied ciphers and sets the cipher list to the system default.
Hope this helps!
Regards,
Venkat
Hello Michael,
We have sent you a private message. Kindly review it and respond with the details via private message
Nothing worked .. initially. As my original message had said, CLI wouldn't work, drivers were installed. You can't use a default admin credential as they don't exist, thw welcome screen tells you to create an admin acount for management on first post. I clearly had network as I was getting to the web ui, just the web ui was shite. I had tried the connection in Chrome and Edge both gave the same issue (infact i think I tried a third one aswell).
Anyways... I just left it alone fo maybe 30 mins and went to go through the process again. And this time after I typed in an admin username and password, the next prompt wasn't "User has been created successfully" as I was getting before it was a popup that said "Creating user"... This time it created the user and I was able to move forward and creat my arrays etc.
So what ever happened it is working now, but there is a deffo a flaw in the system where it doesn't actually create a user even though it tells you it has!
This method doesn't seem acccurate anymore. I also have a 2062 and wanted to shutdown. There isn't the mentioned shutdown options as you state from the SMU.
When you log in to the SMU there isn't a "System's" tab, there are four menu options Dashboard, Provissioning, Settings and Maintenance. Under Settings there is a System option. but this is just an area to set up some very basic system settings such as System Name, Date/Time, turn on things like SMART, or adjust drive cache. Nothing at all to do with Restarting or Shutdown.
If you navigate to Maintencance > Hardware > Eclosure there is a drop down called "Actions" where you can choose Shutdown/Restart and you are given the following options.
You can shut down controllers, you restart controllers, and you can restart the management controller but nothing at all to just shutdown the Enclosure. There was a reddit post that says you can't gracefully shutdown MSA remotely you just have to stop IO (is shut down any connected hosts and then press the power button to turn it off I am not convinced this is correct as you can't be sure no parity writes etc are doing on on the disks and end up forcing things like disk scrubbing on your array which you would have if you just turned the power off.
So any ideas what the actual correct method for shutting down is, the text in that popup talkins about shutting down the controllers needs to be done before powering off its enclosure but how to porperly power off the enclosure I don't know.
Thank you for your response.
I understood that specifying "ALL" will enable all cipher suites.
I am planning to run the one that does not specify "ALL" as you advised, but I am concerned that I may have made a mistake in specifying the cipher suites to disable.
For example, I have read the "HPE MSA 1060/2060/2062 CLI
Reference Guide", the example on page 174 is " set ciphers list ALL:!AES128:!AES256:!SHA256:ECDHE-PSK-CAMELLIA127-SHA256:!ADH:@STRENGTH"
The cipher suite specification scheme is "ECDHE-PSK-CAMELLIA127-SHA256", and "OpenSSL name" is used.
From the above, the following can be inferred, for example
I want to disable "TLS_RSA_WITH_AES_128_GCM_SHA256",
Use "AES128-GCM-SHA256" as "OpenSSL name" instead of "TLS_RSA_WITH_AES_128_GCM_SHA256".
Are there any restrictions on how to specify cipher suites?
Also, is there a restriction that the cipher suite designation method must be specified by "OpenSSL name" rather than "IANA name"?
For example, for "TLS_RSA_WITH_AES_128_GCM_SHA256", do we need to specify "AES128-GCM-SHA256"?
Hello@y-tanaka0805,
Yes, specify the same as what you specified ("AES128-GCM-SHA256"), and separate one or more ciphers by a colon (without space).
Please use the show ciphers command to view the active cipher list, the user-supplied cipher list (which was specified using the set ciphers command), and the default cipher list after execution.
Hope this helps!
Regards,
Venkat.
经过测试，在ESXI上新建虚拟机后，再删除虚拟机，ESXI文件浏览已经被自动删除，但MSA2060 WEB页面在新建虚拟机空间增长后，经过ESXI环境下删除的虚拟机，MSA2060无法回收空间，而一台ESXI物理主机连接的CF8820存储设备，同样的操作，CF8820就可以自动回收空间
Google Translated:
Hello,
Let us know if you were able to resolve the issue.
If you have no further query, and you are satisfied with the answer then kindly mark the topic as Solved so that it is helpful for all community members.
Please click on "Thumbs Up/Kudo" icon to give a "Kudo".
Thank you for being a HPE valuable community member.
Good Day,
I am trying to setup a SAN storage for 7 servers with each server attached storage been 92TB with capability for Snapshot etc Can this be done with HPMSA 2060. Please help advise the best way to go about this. Appreciate
Automated space reclamation in ESXI might not work effeCtively due to 4MB page size on MSA.
Hi,
There is no specific actions needed on MSA end to initiate space reclamation.
Space reclamation is a slow process and might not reflect immediately as soon as data is deleted from host server end.
You could try manual unmap operation and check whether it helps in space reclamation.
https://knowledge.broadcom.com/external/article/323112/reclaiming-vmfs-deleted-blocks-on-thin-p.html
NOTE: The above-mentioned URL will take you to a non-HPE website. HPE does not control and is not responsible for information outside the HPE Website
@Lawtajh2024
Part of your question can be answered using the MSA Sizer: https://ninjaonline.ext.hpe.com/
Part of your question is more complex. The MSA does allow for Snapshots but more information would be required as to how you are using snapshots.
@Emexrulsier
The only documentation which I can find that indicates shutting down the Storage System is the Chassis Replacement guide: https://www.hpe.com/psnow/doc/a00105306en_us
You are in the right place. MC == Management Controller you can only restart this, you always want your management interface available even if the Storage Controller is shutdown. The MC up will allow you to remotely restart the Storage Controller.
SC == Storage Controller you can restart this controller or shut it down. If it is shutdown the system will not communicate on the Host Protocol ports. And all data in Cache is written out to disk. (See CLI Guide, shutdown description: https://www.hpe.com/psnow/doc/a00105313en_us)
The instructions above are pretty close. The reddit comment is incorrect. Graceful shutdown is when BOTH (controller A and Controller B) Storage Controllers are shutdown.
As stated you should stop I/O from the hosts before shutting down the SCs.
Shutdown the SC --> LEDs on the back of the controller will indicate it is down (White LEDs) (Installation Guide Appendix A: https://support.hpe.com/hpesc/public/docDisplay?docId=a00128579en_us)
Power off the main enclosure
Power off any expansion enclosures
When powering back up make sure all enclosures are in the same order
Power on expansion enclosures - wait 1min+
Power on the main enclosure - should be fully up in 15min
The system will return to the running state on power on, NOT to the shutdown state.
@Emexrulsier
Glad you got past the initial onboarding. There are times when the management interface is showing details during the initial onboarding where it is not ready for input. Check to see if there is a spinning wheel in the browser tab (at the top) wait for that to stop. (I know you are already past this so hopefully your message will help someone else).
The SSH CLI should have worked but the login would be 'setup' and no password. It will then ask you to create a user and then ask to login as that user. The SSH CLI also takes some time on first power on to become available but it is much more obvious that it is not ready. (SSH connection refused)
