HP DL380 Gen9 question -- remove all drives and send to another identical server...
-
LOL, I'm guessing they aren't using iLo, Scott. That would require two ethernet cables.
I agree with Scott, assuming you have any influence at your company... now is a great time to look at your entire deployment process. Revamp it to include the requirement of iLo and a hypervisor just like I'm guessing that you require RAID.
-
@Dashrender said:
LOL, I'm guessing they aren't using iLo, Scott. That would require two ethernet cables.
Why would they be paying for HP gear and skipping the stuff that makes it valuable? You lose tons of the value of HP gear if you disable their management and monitoring tools.
-
@scottalanmiller said:
@Dashrender said:
LOL, I'm guessing they aren't using iLo, Scott. That would require two ethernet cables.
Why would they be paying for HP gear and skipping the stuff that makes it valuable? You lose tons of the value of HP gear if you disable their management and monitoring tools.
Because that's what the vendor sells. You can lead a horse to water...
-
@scottalanmiller I will try to investigate this and try to get in touch with our customer's IT dept. early in the process for our next project. It will be interesting to see what will happen. Already it is quite puzzling that most customers want us to deliver the hardware, rather than just providing a server to us, or ask us for a VM. I guess that should be an indication the the instrumentation part of offshore business is a little "special" when it comes to these things.
-
@flomer said:
@scottalanmiller I will try to investigate this and try to get in touch with our customer's IT dept. early in the process for our next project. It will be interesting to see what will happen. Already it is quite puzzling that most customers want us to deliver the hardware, rather than just providing a server to us, or ask us for a VM. I guess that should be an indication the the instrumentation part of offshore business is a little "special" when it comes to these things.
To be fair, instrumentation people do have lots of weird add in cards. It's possible (not probable) that they have some hardware that doesn't play nice inside a VM.
-
If these are offshore systems, it seems likely that they might not have internet access out there. Remote support might be sole by phone or radio.
-
@Dashrender said:
If these are offshore systems, it seems likely that they might not have internet access out there. Remote support might be sole by phone or radio.
Which would just make use of a hypervisor even more important. Can you even compare walking someone through rebuilding a server compared to talking them through copying a file and starting it on another box. I got all the steps in a single run-on sentence!
-
@flomer said:
@scottalanmiller I will try to investigate this and try to get in touch with our customer's IT dept. early in the process for our next project. It will be interesting to see what will happen. Already it is quite puzzling that most customers want us to deliver the hardware, rather than just providing a server to us, or ask us for a VM. I guess that should be an indication the the instrumentation part of offshore business is a little "special" when it comes to these things.
Supplying hardware is fine and normal, but it should still be "treated well." The customer is trusting you to do the best job possible and support everything top to bottom. Big vendors like Oracle and IBM do this all of the time. This allows you to be responsible for every decision, every short coming, every benefit, etc.
So, for example, in this case, any problems arising from bad RAID selection, bad hardware selection, lacking virtualization, ILO not being configured... is all your issue, not the customer's. If they supplied their own hardware, you could blame them for not doing things well. Since they get everything from you, all risks associated with lacking virtualization and ILO, for example, can be pushed off to you.
Same reason that we like working with Scale for HA clusters... they certify every component in the system and certify them all together. The storage, servers, software, virtualization, remote access, networking, NIC cards, patches, BIOS firmware... you name it, they test and certify every piece so that there are no surprises in the field. Those are things that the customer cannot realistically do on their own.
That's why customers want their vendors to supply the whole thing as an appliance rather than as software for them to maintain themselves.
-
Well, it's not so simple for us. We usually have no remote support, and it's up to the customer's IT dept. to take care of things once the system leaves our premises. After commissioning we often don't even have admin rights. It's really puzzling, but we often feel that we abandon the systems once the customer takes over. Our company do have service personnel on the customer's site regularly, but that is for other tasks, and not to service our system. We have had cases where we have been told that "the machine beeps, it's been like that for 3 months"... I guess you could say that someone, somewhere has a job to do. I will try to investigate this when we get our next project. We are often a sub contractor, and we rarely speak to the end user or the IT staff supporting him in the early stages of a project.
-
@travisdh1 said:
To be fair, instrumentation people do have lots of weird add in cards. It's possible (not probable) that they have some hardware that doesn't play nice inside a VM.
Instrumentation is the key piece here @scottalanmiller. These things are very often proprietary add in cards. Being proprietary, there is very little chance for the hypervisor vendors to support them.
I have a client in the oil industry with servers running various versions of RHEL (4 and 5 mostly). They are not capable of being virtualized due to a serial card that cannot be passed through in Hyper-V Server or VMWare.
Of course the OS can be virtualized, but without the access to the serial fed data, there is no point to the OS. The industry has a new solution that is not yet certified. Once certified, I am certain adoption will be quick, but it will not be immediate because it will require millions of dollars in hardware replacement.
-
@JaredBusch said:
Instrumentation is the key piece here @scottalanmiller. These things are very often proprietary add in cards. Being proprietary, there is very little chance for the hypervisor vendors to support them.
Agreed, if there is very special add-in hardware. Although that feels unlikely given the manner in which the hardware is being handled. Doesn't mean that that impression is correct, but having worked on the hardware vendor side of that if we were doing that kind of stuff we would either abstract it using a sensor device separate from the server itself or, more likely, be on site to get hardware working properly because it is so unique that the customer can't just add it in and get it working.
-
This conversation is no different for the hundreds of others we'd had and seen - many industries and businesses do not care about their IT, and never keep modern - Look at my CAT scan machine installed in 2008 that came with Windows 2000, or a print businesses print server coming with XP in 2010.
As Scott reminded me again yesterday - it's not our responsibility to care more about the business than the business drivers/owners.
Even so, I just can't help that, I want things I'm involved with to be better.
