Hi all,

Got a strange setup issue with a couple of our new v5035's. We have used a laptop to successfully go through the config pages on the technician port to set the IP addresses. We then are trying to use the laptop to connect through port 1 to get the MGMT GUI up, it produces a completely blank screen. We are using Firefox, and even though the tab of the webpage changes correctly to the IBM icon, with name of the device, the actual webpage is completely blank. Checking debug of FIrefox all the info is there in the debug for the login screen, but it does not render. Anyone have any ideas of how to fix this?

We did try the service webpage and that comes up just fine, as of course did the initial config pages, but we just can't get the MGMT GUI to come up correctly. 

Any help or advice will be gratefully received.

Cheers, 

Andy

------------------------------
Andy Heath
------------------------------

did you try it with Chrome or Edge? 
you can also try to restart web service via service page or "satask restartservice -service tomcat" command

------------------------------
Nezih Boyacioglu
------------------------------

Try Chrome or another browser. I have setup many of these arrays and that always solved the issue. Don't know why, but it worked!

------------------------------
Christopher Aveta
------------------------------

Hi Andy,

As I wrote earlier in private reply, please make sure that both nodes are active (it can be done from service assistant GUI), also check which node is config node, it can be done on the panel below the list of nodes. Then please choose the config node in the list and on the left panel look for services - there you can choose tomcat service to restart. Check if that helped with empty Cluster GUI page.
Other possibility is to restart the config node - this will cause config role to failover to another node and thus all services on that node will start over.

Best Regards, Denis.

------------------------------
Denis Olshanskiy
------------------------------

​Hi all,

Thanks for the help and advice. In the end, once we got the network ports enabled to the storage, so we didn't need the laptop, we used one of the host servers to connect through, using Edge, and it worked ok first time, we have the GUI working properly. I'm guessing the laptops we had to use had an older version of Firefox which is just not compatible anymore. We did also try Chrome, but again it's not the most recent of versions, and it didn't work. The v5035 is on 8.4 code level being a newly delivered piece of kit.

So lesson learnt, if we get an empty screen, and browser tab says it's connected, try another browser, or preferably a latest version of browser, and it should work fine.

We'll pass on our feedback to our hosting teams so next time we get a more recent browser version on our servers and laptops so we can use them properly next time.

Cheers,

Andy

------------------------------
Andy Heath
------------------------------

Original Message:
Sent: Thu May 19, 2022 02:31 AM
From: Denis Olshanskiy
Subject: FS5035 MGMT GUI Screen completely blank

Hi Andy,

As I wrote earlier in private reply, please make sure that both nodes are active (it can be done from service assistant GUI), also check which node is config node, it can be done on the panel below the list of nodes. Then please choose the config node in the list and on the left panel look for services - there you can choose tomcat service to restart. Check if that helped with empty Cluster GUI page.
Other possibility is to restart the config node - this will cause config role to failover to another node and thus all services on that node will start over.

Best Regards, Denis.

------------------------------
Denis Olshanskiy
------------------------------

Hi,

I've experienced that behavior with very laggy GUI response on several FlashSystem and Storwize disk arrays I manage several times. Not only can the GUI load and respond slowly but it may also take ages to display tasks results and upload new Spectrum Virtualize and disk firmware. In my many cases that was not browser related but eventually the only working remedy was to restart config node, as even restarting Tomcat wouldn't help. One thing I've noticed that behavior started to occur once I upgraded 8.4.X Spectrum Virtualize.

------------------------------
Janusz Panicz
------------------------------