Integrity server ready before MSA1500

[Records Management]

I have a rx2660 connected to a MSA1500cs.

The problem is that at bootup, the server outruns the MSA. This results in the server not seeing the MSA LUNs via the bootup sequence.

It's easily fixed by doing an ioscan, and a vgchange. But, I'd like to figure a way to have this done during the boot process.

Thoughts? Someone else has to have run into this also.

[Torsten.]

Follow a proper boot sequence:

power up the switch, the msa and finally the server(s).

I guess you will not do this every morning ...

;-))

[Records Management]

The problem is during a long power failure. The UPS has shutdown the server.

When the power is restored, both the server and the MSA1500 are powered up. The problem is that the MSA takes longer to get itself in order than the server does. Result is missing LUNs.

As this is at a remote site, we end up with a phone call that their application isn't working.

[Torsten.]

Even if we solve this problem, next time the msa itself is faster than the disk enclosure, hence an array without disks - what now?

The only safe workaround is a manual power on in a proper sequence IMHO ...

[Torsten.]

To quote the arrays user manual:

wing order:
1. Storage Enclosuresâ Power on all storage expansion enclosures.

2. MSA1500 csâ Power the MSA1500 cs on with the power switch located in the far-right
lower area of the front panel. After powering on, wait until the message â MSA1000
Startup Completeâ appears on your display. This process may take up to two
minutes.

3. Server(s)â Ensure that the servers that are attached to the MSA1500 cs are powered on.

[Torsten.]

Problem with copy'n'paste, sorry.

Applying power

Before applying power to the MSA1500 cs all components of the storage system must be
installed and connected to the supported interconnect options

The MSA1500 cs components must be powered up in the following order:

1. Storage Enclosures Power on all storage expansion enclosures.
2. MSA1500 cs Power the MSA1500 cs on with the power switch located in the far-right
lower area of the front panel. After powering on, wait until the message â MSA1000
Startup Completeâ appears on your display. This process may take up to two
minutes.
3. Server(s)â Ensure that the servers that are attached to the MSA1500 cs are powered on.

[Steven E. Protter]

Shalom,

This is really much less complex that it appears.

The MSA-1500 must start first and be fully spun up before the server start sequence begins.

You can do this by providing it a different UPS to give it a better chance of running through the power failure.

APC sells PDU Power Distribution Units that can permit you to program delays in the startup sequence plug by plug, permitting you to control the startup sequence.

You could also make an /sbin/init.d start up job and position it at the beginning of run level 2 to slow down the server startup. Problem with that approach is that when you are patching you will find the delay maddening.

If you are getting power outages frequently enough for this to be a problem, you need to talk to management about a server room UPS that can ride your critical servers through a long outage.

SEP

[Records Management]

In a better world, they would have better power, or even someone on-site who could handle this.

So, I'm going to add a script into /sbin/init.d.

[Hein van den Heuvel]

Well Torsten and SEP, you are of course entirely correct, but it's bulls(*t anyway.

Yes, myself, I use a careful power up sequence in my kitchen, and for my entertainment system, and for my basemetn coputer lab, and for my car. Like I'll switch on the lights in the car _after_ I cold start the car to avoid the extra 15 amps drain on the battery. My kids have a 4 letter word for that. It stars with an a and ends in "an l".

I find it entirely unreasonable to have to power up a system in some particular careful order. (but do it anyway).

If order is needed, then it should be imposed through automation not by a playbook.

It should be possible to loose all power, and
bring it all back un-attended with the flip of one switch (the power company).

The init.d script should be there to check that the resources are in place to move to a next level in the init. If I have drives... mount then and onwards... otherwise write message, wait and try again. If I have a network, then onwards, ... otherwise write a message (where? :-), wait and try again. If I can bring up Oracle then onwards else .. page someone.

fwiw,
Hein

[rick jones · Accepted solution]

In the EFI there is an option when configuring boot options to change the timeout before the default boot happens. If the problem is unattended reboot after power failure, you can set that timeout to be longer than the MSA1500's startup time and be assured that the OS will not try to boot before the MSA is running.