SSY-V: livestop only with password with v10 PSP4 and above

For all DCIE the livestop command is a very powerful and often used command to bring the SSY-V software back on track. The livestop command restarts the management services of SSY-V without affecting the storage virtualization layer, so I/O still can pass the system. Formerlay wirh SANmelody or SANsymphony the virtualization layer and the management layer were backed by two different services, so one was able to restart one of them without the other. With SSY-V DataCore merged both functions into a single service making the restart of the management a bit harder to do.

Livestop is normally required by the DataCore support whenever you open a case and something is wrong on the management layer. Unfortunatley in some of our installations livestop is rather common because we heavily use the Powershell to gather information about the DataCore environment to use them in ICINGA/Nagios. Although Datacore offers tons of perf counters but the ones we need aren't native available so we have to calculate them by getting data with powershell and combine them to get what we want.

The powershell implementation seems to have some kind of memory bug because after a while (and this can be only a few days), the management services denies access via powershell. I already wrote about this problem here.

The root cause was never found by DataCore support although we had calls open with them. The workaround was always to do a livestop.

Exactly this problem now occured once again after we upgraded to SSY-V 10 PSP4 Update1. As usual we tried to to a livestop but this time the command didn't complete. First I checked for some kind of typo but everything was fine. The printed messages an the screen told me that from now on I have to provide a password with the livestop command and this password is changed on a daily base. WHAT THE HELL...... I mean, I understand Datacores concerns about someone doing livestops without the needed knowledge. Sometimes a livestop can produce more problems than solving them but for such reoccuring tasks (and there are other examples to mention here) the "self-service" livestop keeps the business of DataCore's support low and solves the problems. Now I have to open a case EACH time I want to restart the management services and sometimes I will spent unneeded time to wait for the support team to provide the password. Okay, I have to admit I never tried to get the password within a chat session but chats are for prio 1 calls and I don't think that getting errors from powershell is a prio 1.


So be warned if you upgrade to PSP4 Update1, you will loose some flexibility in self-solving your problems and I hope this change is worth the additional work at DataCore support.

Leave your comments

Post comment as a guest

Your comments are subjected to administrator's moderation.

People in this conversation

  • Guest - DCIE

    I can comprehend what DataCore has driven to implement this: Blogs like this, where customers possibly find "solutions" that threaten the availability. Your management plane isn't working? Do a livestop. Your script is causing a memory leak? Do a livestop. A livestop is nothing you should do regular, especially not, if it's a workaround for something else.

    The support is dealing regularly with cases where customers tried something that they have found in a blog - regardless if it was suitable for their problem or not.

  • Guest - Falk

    Hi Oliver,
    ein kleiner Tip, das Passwort für den Livestop scheint immer das gleiche zu sein für jeden Tag.
    Du musst nur genügend Calls eröffnen und die Passwörter sammeln. ;)
    Gruß Falk

  • Guest - Oliver Krehan

    Hi DCIE,

    thanks for your input. Of course doing livestops is nothing a normal user should do without deep knowledge of what these task do. My articles only contain hints for SPECIAL problems. Livestopping can never be a "first-to-do" like rebooting Windows when it doesn't do what you want.
    On the other hand, publishing an official statement from DataCore support that is given to me as a workaround because DataCore isn't able to solve the problem finally is nothing wrong as far as I can see. I'm pretty sure you found this website because you also searched the internet for tips that could help you in a special case. No one is forced to do what I publish ;). You can also say "let this creep alone I will ask the official Datacore support for help". That's abolutely okay.
    By the way, this blog is check by DataCore staff regulary and I will get notified and asked to remove special "instructions" if they are marked as "problematic" by DataCore.
    So once again, thanks for your input, with the password restrictions these kind of tips will come to an end and everyone should be happy.

Powered by Komento
joomla templatesfree joomla templatestemplate joomla
2018   globbers joomla template