ewy's Posts

I need some help validating this Network config for a stretched cluster. Ill summarize whats on the attached, not so good, diagram. - cluster is running 6.7u1 - Each data site has Nexus vpc Pairs as cores. - L2 between data site. the vsan vlan has an EIGRP advertised SVI which is part of an HSRP group with 4 members (1 SVI per nexus, so 2 per site) (this is one of the key things i want to validate)  - Each host has static route which uses the vsan SVI (10.10.1.0      255.255.255.0        10.10.0.0   vmk2       MANUAL) (want to make sure this is recommended or if i should use something else) - das.usedefaultisolationaddress = false - HA advance setting is configured with the following das.isolationaddress(1-4): IPs 10.10.0.2(Site A),  10.10.0.4(SiteB), 10.10.0.3(SiteA),  10.10.0.5(SiteB) in that order (want to validate this too) - As you can see vsan witness traffic always flows through the primary site (sub optimal routing, not big deal unless HSRP fail-over time is too high and could cause vsan issues after a site failure while 10.10.0.1 becomes available again. Questions: 1- Should i advertise (route) the vsan SVIs. 2- Can i use a different route for witness traffic to avoid traversing the ISL 3- Is the HA advanced settings (Isolation addresses) configured properly. What would you recommend to improve this design. Dont be shy with the details . I understand this is very networking "heavy" but that is what we have to deal with by using Ethernet based distributed storage systems which HCI is. As we always hear.. network reliability is key to HCI. Thanks in advance folks!! Looking forward to your responses.

    Having the attached errors showing up in a few vms after an HA event.     I am unable to create snapshots. It is not a space issue as a KB suggested. these are running on a vsan datastore.      Thanks in advance for your help!

Can some from VMware clarify this (non-consistent backups when VMware Snapshot Provided disabled). We have several non-2019 servers too where this "fix" has been applied and the assumption is that the snapshots are app consistent as long as the app "can be quiesced", not that we were removing the possibility of it being quiesced and being fooled into thinking all is good. Also where in this architecture if so would this service sit. Thanks

Is this bug back, what am i missing. This is a vsan stretched cluster running 6.7u1. HA Admission Control configuration can be seen in the pics attached. I am using cluster resource  % (50) as recommended for vsan stretched clusters. The weird thing is on the HTML interface the Host Failure option is available but in the vSphere web client is not (which I think is how it should be on the HTML), not sure if this is a bug/issue just letting you know. I have plenty of resources, as you can see in the picture attached... I can lose half of the cluster and still will have plenty to support my operation. Yet, the "Insufficient configured resources to satisfy the desired vSphere HA failover level on the cluster" warning is still showing. What did i do wrong or am not understanding. PS: I do have like 3 Vms with "small" cpu/mem reservations. Thanks

Here is my scenario. I have an Existing Windows vCenter server v6.5d with an embedded PSC. I am planning to upgrade it to 6.5U2 and then deploy a new VCSA v6.7 with an embedded PSC (Same SSO and Site as the existing Windows one and configure ELM between them. Is this supported? I may have misunderstood an online blog where it mentions that it is but only on Greenfield deployment...if that's the case that really sucks ! Thanks in advance for your help!