Cant get through MSA 2060 initial configuration screen

[Limonad]

Hi, 
After first start I have created user account on MSA 2060. after reboot and login the system first asked to update MSA. aster that i 've got stack on  the    this  screen. all buttons are greyed out. Any hint?

[support_s]

System recommended content:

1. HPE MSA 1060/2060/2062 Installation Guide

Please click on "Thumbs Up/Kudo" icon to give a "Kudo".

Thank you for being a HPE valuable community member.

[JonPaul]

@Limonad 
Click the browser refresh button.  I've seen this a couple times and it has always resolved with a total browser refresh.  
If you close the browser and restart you will need to login as the user which you created (and not the 'setup' user)

[intersysteme]

I have exactly the same problem on a new msa 2060 bay.
In Cli mode everything works, only the Smu interface malfunctions.
I suspect a language problem, because until then the msa bays were initialized in English.
The last one I received is initialized in French in my case.

[JonPaul]

@intersysteme 
Thanks for the information. I will try a localized experiment.  I was also working with a system which was wildly out of date which was taking time to enable the start button.  Does your system have an accurate date?  NTP enabled?
Can you describe a little more of your environment and what steps you went through to do the initial configuration?
It sounds like you configured through the CLI and then went back through the WebUI.  What details did you configure through the CLI?  DId you use the USB serial to start the configuration?
Here is another thread which has the short answer to how to get past this issue.  But any details we can get on how it occurred in the first place will help in resolving.
https://community.hpe.com/t5/msa-storage/system-configuration-wizard-grey-out/td-p/7190190

Thanks

[Gaz350]

Ours was having the same problem.

Support advised SSH to device

set user-interactions onboarding-step 255. 

[JonPaul]

@Gaz350 
Thanks for the information. Did support also guide you to making sure that all details that would have been reviewed during onboarding were checked?
It would also be a good idea to run the FREE Health Check  https://www.hpe.com/storage/MSAHealthCheck   to make sure that best practices are validated.
Was your system localized in a non-english language?  Was the time on the system not accurate?
@Limonad 
The WebUI is designed to pickup the localized language from the browser.  It will initially come up in English but once it has completely loaded it should align with the browser default.
We appreciate all the information we are getting from users and sorry for the difficulty.

[Gaz350]

No additonal steps have been completed by support.

Licence is installed, time is correct. (in the process of building our disk pools.)

Intresetingly it fails to reconise the zip file as a valide file. (it being https://www.hpe.com/storage/MSAHealthCheck)

I'm not 100% convinced our MSA is working correctly still. Access to management is very speradic and/or the Storage controller won't load Performance data.

We did a firmware update intially to try and resolve the issue which took over an hour and reported back as failed although the system does report it running. I've also nnoticed a firmware Alert around the orginal 1st boot time saying "The bundle install is incomplete."

[Gaz350]

Example of what I seem to get when the Storage Controller becomes unresponsive..

[JonPaul]

@Gaz350 
Did you configured the Update Server in the process?
The Update Server will periodically download a manifest file from HPE support and compare it to the running firmware on the system and Alert you if they differ.   You can see what the manifest file looks like here:  https://www.hpe.com/support/MSAmanifest
If you don't want this even trying to happen you can set the Update Server URL to " " (space) using the CLI

The onboarding will run through these settings:
  Network - IPv4,  IPv6 and DNS  settings
  Date and Time - Manual Time set, NTP and timezone
  Users - Local, LDAP (Windows AD) and SNMPv
  Notifications - Email, SNMP and Syslog
It will also run through creating a Pool (Adding disk-groups)  and nicknaming initiators, creating 'hosts' and host groups, creating volumes and mapping the volume to the host/host-group.
All can be set separately in the SMU but the thought is to guide users through the high importance configuration settings. 

There are a couple of reasons I have seen that could cause a firmware update to not succeed but these should be taken care of by the smart component.  The smart component does have a 90 min overall timeout which may indicate the component lost network access to the system during the update.  Please try the Smart Component again during a time of lower I/O and if it faults please log a support case.

[toshigama]

I understand the part about creating disk groups, as i understand POOL A for example consists of disk groups.

What is don't understand are the initiators, when you are connecting MSA to the ESXI hosts.

Every tutorial on yt shows only the part about creating virtual volumes and disk groups.

Thanks

[JonPaul]

@toshigama 
This appears to be a different question than the initial post. The initial post is an issue where no buttons are clickable on the onboarding process and unable to proceed.  This appears to be an operational question.  Could you please open a new thread to start a new discussion.