Trend SVM gets deployed but not power on and vmservice-vswitch not created
search cancel

Trend SVM gets deployed but not power on and vmservice-vswitch not created

book

Article ID: 416187

calendar_today

Updated On:

Products

VMware NSX

Issue/Introduction

  • Trend SVM gets deployed in vCenter
  • Trend SVM is unable to Power On
  • vmservice-vswitch is not created
  • The eam log shows the SVM Power Off

/var/log/vmware/eam/eam.log

INFO | vim-inv-update | VirtualMachinePropertyChangeHandler.java | 298 | VM: vm-xxxx power state set to poweredOff

  • The component vdl2 is down during the SVM deployment

/var/run/log/hostd.log

 In(166) Hostd[2099549]: [Originator@6876 sub=Hostsvc.NetworkProvider] Setting NSXT status on DVS [50 xxx xxx xxx xxx  82] to [down]

 Er(163) Hostd[2099549]: [Originator@6876 sub=Hostsvc.NetworkProvider] Component [com.vmware.common.opaqueDvs.status.component.vdl2] status [down] on DVS

 In(166) Hostd[2099542]: [Originator@6876 sub=Hostsvc.NetworkProvider] Setting NSXT status on DVS [50 xxx xxx xxx xxx 82] to [up]

/var/run/log/vmkernel.log

 In(182) vmkernel: cpu69:2117278)vdl2: VDL2_SetOpaqueDVSStatusCB:1462: [nsx@6876 comp="nsx-esx" subcomp="vdl2-23786738"]Set opaque DVS status com.vmware.common.opaqueDvs.status.component.vdl2 to up for portset DvsPortset-0

Environment

VMware NSX

Cause

The Virtual Distributed L2 (VDL2) component is down. This component must be up for NSX to successfully complete VM operations that are attached to a segment on the transport node.

Resolution

To resolve this issue:

1: Put ESXi to Maintenance Mode

2: Move ESXi to NSX prepared cluster with TNP

3: Ensure NSX prepared for the ESXi host successfully

4: ESXi exits Maintenance Mode and redeploy the SVM

Additional Information

Powered by Wolken Software