VSA Time : Fix the blue screen

First off, special thanks to Jason Boche for finding the root cause of this issue.

Turns out in an OVA deployment the time syncing with ESX and VMware tools will cause problems with the SSL cert generation. Basically with some setups it will bounce time 5 hours forward *before* the SSL cert is generated. This is related to some time zone funkiness I have a fix for.

Problem is this means that cert is always invalid because it comes from the future where Chad Sakac is fully cyborg and Microsoft just makes wallpaper.

I will build a fix into the future versions. But, if you want to fix now follow this simple step:

Login to Celerra UBER VSA as root. Default user/password is ‘root/nasadmin’.
Make sure time on VSA is synced. Use NTP or set manually.

Run the following command:


This will regenerate the SSL certificate and should fix any blue screen issues.



Celerra VSA

14 Comments Leave a comment

    • Unable to resolve the Bluse screen i did everything. Can you please help me how to resolve this issue.

      Thanks in advance

  1. Here is a small addition to modify the Timezone of the UBER VSA prior to generating the certicates

    Modify UBER VSA timezone prior to /nas/http/webui/bin/gen_ssl_cert.pl

    1 Log in as root/nasadmin, check which timezone your machine is currently using by executing `date`. You’ll see something like Mon 17 Jan 2005 12:15:08 PM PST, PST in this case is the current timezone.

    2 Change to the directory /usr/share/zoneinfo here you will find a list of time zone regions. Choose the most appropriate region, if you live in Canada or the US this directory is the “America” directory.

    3 If you wish, backup the previous timezone configuration by copying it to a different location. Such as
    mv /etc/localtime /etc/localtime-old

    4 Create a symbolic link to the appropriate timezone from /etc/localtime. Example:
    ln -sf /usr/share/zoneinfo/Europe/Amsterdam /etc/localtime

    5 If you have the utility rdate, update the current system time by executing
    /usr/bin/rdate -s time-a.nist.gov

    6 Set the ZONE entry in the file /etc/sysconfig/clock file (e.g. “America/Los_Angeles”)

    7 Set the hardware clock by executing:
    /sbin/hwclock –systohc

    8 Generate new SSL Certificate

    • /usr/bin/perl /nas/http/webui/bin/timezone.pl -s America/Denver is executed while doing it over the Unisphere gui, wich should be the prefered way to change time zone settings.

      As best do all those changes, like NTP/DNS/TimeZone settings over the WebGui, it updated all those funky files automatically, and you can be sure to not forget anything….

      also best should be to reboot the CS so that all running processes reread their configuration files

      simply use the command designed to update those SSL certificates

      /nas/sbin/nas_config -ssl

  2. I cant get jumbo frames to work on this VSA. I have gone into system > network > interfaces and modified my interface to give it an MTU of 9000, but it still isnt working. verified from 2 ESX servers with vmkping -s 9000 command. vmkernel ports, Physical and vswitch ports are verified with mtu 9000 Is this a bug or am i doing something wrong?

  3. Hi Nick…..I’ve tried follow your procedure, but the problem still there.
    When I make logon in unisphere, the browser load just the blue screen.

    Could you help me ? Do you have some suggestions to solve this problem ?


    Rafael Nunes

  4. Just a quick note….in order to change the Timezone, there is an easier way instead of all that stuff that Erik Bussink mentions (Thanks though!)

    Just login as he indicates (root/nasadmin) and type timeconfig

    Then generate your new cert. I also found rebooting afterwards helped.


  5. Thanks this helped me fix my issue.

    1. time in bios was incorrect. – set the correct time.
    2. login to celerra with root:nasadmin
    # timeconfig
    set the the correct time zone etc..
    3. run command
    #  /nas/http/webui/bin/gen_ssl_cert.pl (to generate new certs)4. On windows client…remove any previously installed celerra root & personal certificates.

  6.  I tried all what was written above and more and more and more…
    I tried celerra OVF and Virtual machine (zip) and vnx …..
    but Nomatter what I did or what pc I use or whatever I f**k … this BLUE SCREEN never goes ….
    Never means never … NEEEEEEVEEEEEEEEEEER
    if there’s a tip to use it’d be nice to share because all what I wanted it for has simply collapsed .

  7. Hi,

    I am having same issue of blue screen even after trying all the fixes as mentioned above. Can anyone throw some light on where I might be going wrong?
    Downloaded and created VM from ovf. Assigned IP address etc. I could connect to it but then blue screen came. The timezone is correct one from the start still I tried all the steps as mentioned by @nick and @Erik Bussink above. Then I generated certificate with the command but then I just can’t go to the IP address anymore. It just fails to even go to the webpage!

    Anything that has changed? Any help will be appreciated.


  8. Just got this working before moderation of previous comment.

    You need to download latest version of VNX VSA as explained in this link (http://techhead.co/emc-vnx-simulator-vsahow-to-download-the-latest-version/) – I got VNX_8.1.0-38015, and then install, give it correct IP, network etc.
    The last thing to do is run /nas/sbin/nas_config -ssl command in the VM.
    After this, just try the ip and the accept all the certificates and java applet security exceptions, you should see a login dialog. Sometimes you have to reload that applet in order for it to go ahead and not get stuck at blue screen.
    Runs really badly on Mac (CPU touches the roof) with FF (UI is flickering). Windows and IE combination works better.

    Thanks @nickapedia and @techhead

%d bloggers like this: