Yes, the message is self-explanatory: Unable to find distributed vSwitch dvSwitch0
and you said you are not having dvSwitch0 in your DC- so this does indeed comes from some TRAFFIC LABEL - so please check your traffic labels for management and storage and public traffic (guest not being important as SSVM is attached to only those other 3 networks) Best, On Wed, 12 May 2021 at 20:29, Corey, Mike <mike.co...@sap.com.invalid> wrote: > Hi again, > > > > When I enable the zone my system vms just continue to cycle through a > deployment and expunge. Only thing I can find in the logs to hint at an > issue is the line below regarding capacity. I don’t understand how I can > have insufficient resources…these are 2 Gen 10 blades with (2) 24 core cpus > and 764GB memory. > > > > Is there a setting I need to adjust or something else I should be looking > for in the logs as an indication as to why they are failing? > > > > 2021-05-12 12:05:30,769 WARN [o.a.c.s.SecondaryStorageManagerImpl] > (secstorage-1:ctx-dfe12939) (logid:61e5d345) Exception while trying to > start secondary storage vm > > com.cloud.exception.InsufficientServerCapacityException: Unable to create > a deployment for VM[SecondaryStorageVm|s-14-VM]Scope=interface > com.cloud.dc.DataCenter; id=1 > > > > > > Another error I’m seeing is regarding the distributed vSwitch – I setup > three physical networks – management, storage, guest – each with their own > VDS “traffic label”. (example: vds2-phl-csm02-nfs,0,vmwaredvs). > > > > I don’t have a distributed vSwitch named dvSwitch0 so if ACS is looking > for that I don’t know why or why it isn’t looking for the switch names I > have configured under the “traffic label”. > > > > Line 71606: com.cloud.exception.InsufficientServerCapacityException: > Unable to create a deployment for > VM[SecondaryStorageVm|s-26-VM]Scope=interface com.cloud.dc.DataCenter; id=1 > > Line 71638: > com.cloud.exception.InsufficientServerCapacityException: Unable to create a > deployment for VM[SecondaryStorageVm|s-26-VM]Scope=interface > com.cloud.dc.DataCenter; id=1 > > Line 71660: 2021-05-12 14:15:47,330 INFO > [o.a.c.s.SecondaryStorageManagerImpl] (secstorage-1:ctx-433a9990) > (logid:64b260ab) Unable to start secondary storage vm for standby capacity, > vm id : 26, will recycle it and start a new one > > Line 71722: 2021-05-12 14:15:49,045 ERROR > [c.c.h.v.m.HypervisorHostHelper] (DirectAgent-12:ctx-69b57f06 > usphlmvesxt01.phl.global.corp.sap, job-112/job-119, cmd: StartCommand) > (logid:a5237296) Unable to find distributed vSwitch dvSwitch0 > > Line 71723: 2021-05-12 14:15:49,045 INFO > [c.c.h.v.u.VmwareHelper] (DirectAgent-12:ctx-69b57f06 > usphlmvesxt01.phl.global.corp.sap, job-112/job-119, cmd: StartCommand) > (logid:a5237296) [ignored]failed to get message for exception: Unable to > find distributed vSwitch dvSwitch0 > > Line 71725: Message: Unable to find distributed vSwitch > dvSwitch0 > > Line 71727: java.lang.Exception: Unable to find distributed > vSwitch dvSwitch0 > > Line 71747: Message: Unable to find distributed vSwitch > dvSwitch0 > > Line 71751: 2021-05-12 14:15:49,053 INFO > [c.c.v.VirtualMachineManagerImpl] (Work-Job-Executor-7:ctx-81037bca > job-112/job-119 ctx-43bfb160) (logid:a5237296) Unable to start VM on > Host[-2-Routing] due to StartCommand failed due to Exception: > java.lang.Exception > > Line 71752: Message: Unable to find distributed vSwitch > dvSwitch0 > > > > > > > > > > > > *Mike Corey* > > > Technology Senior Consultant, IT CS CTW Operation & Virtualization Service > US > > > *SAP AMERICA, INC.* 3999 West Chester Pike, Newtown Square, 19073 United > States > > > T +1 610 661 0905, M +1 484 274 2658, E mike.co...@sap.com > > > > > > > -- Andrija Panić
