VMware

Does Vmware Support Custom vSAN config or Customized vSAN Ready Nodes?

I’m getting conflicting info, if I build my own vSAN cluster and all parts are on the VMWare HCL, what is the policy?

​

If I modify a ReadyNode config with parts that are within OTHER ReadyNodes from the same vendor, what is the policy?

​

So far the answer I recieved was: We might support trouble shooting as long as it’s not too hard, but if it is we might not support it or we might tell you to take it to a supported config (i.e. Swap out for the parts that would make it the node off the list.)



View Reddit by Secretitnerd1View Source

 

To see the full content, share this page by clicking one of the buttons below

Related Articles

5 Comments

  1. My belief is that if all parts are on the HCL you should be able to escalate and get support even if the front line person resists.

    While I like the idea of ReadyNodes, in practice I always need to change something in the config so then every one is deviated from the template. I find it easier to start with a regular R640 / 740 and add HCL listed HBA/NVMe/SSD.

    No disasters so far – I’m careful about HBA and NIC firmware versions. Recent drives haven’t given me any issues.

    Touching lots of wood here 🙂

  2. So long as your parts are on the HCL you are good to go.
    We BYO our vSAN clusters as it was MUCH cheaper than buying ready nodes of the same spec from the same vendor…

    No problems with VMware support. We do have BCS but that should not sway this.

    At the end of the day they will say you get a ‘superior’ support with their ready nodes, as they get a bigger cut of the pie!

  3. We bought what we thought were vSAN ReadyNodes, but because we changed some NICs (all HCL compatible), we later found out (when dealing with support) that they were never actually designated as ReadyNodes. And so we received the same level of support as we would with any other non-ReadyNode Dell server running vSAN.

    There was an attempt to get the servers re-designated as ReadyNodes, but it turned into a big ordeal and we eventually said screw it.

  4. >I build my own vSAN cluster and all parts are on the VMWare HCL, what is the policy?

    If all components are on the HCL and you have properly adhered to HCL driver and firmware guidance, you are 100% supported.

    >If I modify a ReadyNode config with parts that are within OTHER ReadyNodes from the same vendor, what is the policy?

    It’s not technically a ReadyNode, and there might be some variance in terms of how the OEM handles this (e.g. will they guarantee 1:1 replacement of components with exact hardware match or not), but from a VMware perspective, if you’re adhering to the HCL (including drivers and firmware), you’re covered.

    >​So far the answer I recieved was: We might support trouble shooting as long as it’s not too hard, but if it is we might not support it or we might tell you to take it to a supported config (i.e. Swap out for the parts that would make it the node off the list.)

    Who is telling you this?

Leave a Reply