VM's logical ports are deleted after the vMotion
search cancel

VM's logical ports are deleted after the vMotion

book

Article ID: 383509

calendar_today

Updated On:

Products

VMware NSX

Issue/Introduction

  • Host Transport Nodes are prepared for NSX Security Only. 
  • VM is migrated with vMotion.
  • Post migration, VM is correctly connected to virtual switchport.
  • A few seconds after the migration, VM's logical ports are deleted (while VM remains connected to vDS switchport).
  • This will impact IP bindings, which will be cleared by IP discovery.
  • This may cause connectivity issues due to missing filters / missing DFW ruleset configuration.
  • On NSX Manager, you may see logs similar to the sample below:
    /var/log/proton/nsxapi.log:
    2024-10-24T05:29:08.892Z INFO L2TaskExecutor3 LogicalPortServiceImpl 3584210 SWITCHING [nsx@6876 comp="nsx-manager" level="INFO" subcomp="manager"] Removing attacher [########-####-####-####-########f4f3] vmxPath [[<datastore>] <vm_name>.vmx] from logical port [########-####-####-####-########bfd4]
    ..
    2024-10-24T05:29:38.962Z INFO L2DelayedLogicalPortDeletionScheduler1 PolicyUfoUtils 3584210 SWITCHING [nsx@6876 comp="nsx-manager" level="INFO" subcomp="manager"] Deleted LogicalPort InternalLogicalPort/########-####-####-####-########bfd4 from internal store
    ..
    [host_switches { switch_id: "## ## ## ## ## ## ## ##-## ## ## ## ## ## ## ##" host_switch_profiles { uplink_profile { teaming_policy: LOADBALANCE_PORT_ID active { type: PHYSICAL_NIC name: "Uplink-1" } active { type: PHYSICAL_NIC name: "Uplink-2" } rolling_order: false } } pnics { device_name: "Uplink-1" uplink_name: "Uplink-1" } pnics { device_name: "Uplink-2" uplink_name: "Uplink-2" } transportzone_id: "########-####-####-####-########c695" transport_vlan: 0 mtu: 9000 switch_name: "<switch_name>" subnet_mask: "" default_gateway: "" vtep_on_static_ip: false overlay: false mode: STANDARD type: VDS vlan_transportzone_id: "########-####-####-####-########c695" vifCollectionStatus: DISABLED ipv6_prefix_length: "" ipv6_default_gateway: "" ipv6_dhcp: false ipv6_auto_conf: false }
    host_switches { switch_id: "## ## ## ## ## ## ## ##-## ## ## ## ## ## ## ##" host_switch_profiles { uplink_profile { teaming_policy: LOADBALANCE_PORT_ID active { type: PHYSICAL_NIC name: "Uplink 1" } active { type: PHYSICAL_NIC name: "Uplink 2" } rolling_order: false } } pnics { device_name: "Uplink 1" uplink_name: "Uplink 1" } pnics { device_name: "Uplink 2" uplink_name: "Uplink 2" } transportzone_id: "########-####-####-####-########8337" transport_vlan: 0 mtu: 1500 switch_name: "P_VR_MetroDR_Classic_MGMT" subnet_mask: "" default_gateway: "" vtep_on_static_ip: false overlay: false mode: STANDARD type: VDS vlan_transportzone_id: "########-####-####-####-########8337" vifCollectionStatus: DISABLED ipv6_prefix_length: "" ipv6_default_gateway: "" ipv6_dhcp: false ipv6_auto_conf: false }
    config_version: "11"
  • On the ESXi host where the impacted VM is running, logging may indicate the below:
    /var/log/nsx-syslog.log:
    2024-10-24T05:29:08.879Z nsx-opsagent[69304095]: NSX 69304095 - [nsx@6876 comp="nsx-esx" subcomp="opsagent" s2comp="nsxa" tid="69304494" level="INFO"] [AddVifRequests] Clearing security extra config from dvs [## ## ## ## ## ## ## ##-## ## ## ## ## ## ## ##] lport [1657] on detach
    2024-10-24T05:29:08.879Z nsx-opsagent[69304095]: NSX 69304095 - [nsx@6876 comp="nsx-esx" subcomp="opsagent" s2comp="nsxa" tid="69304494" level="INFO"] [PortOp] Clearing [com.vmware.port.extraConfig.security.enable] from port [1657]
    2024-10-24T05:29:08.879Z nsx-opsagent[69304095]: NSX 69304095 - [nsx@6876 comp="nsx-esx" subcomp="opsagent" s2comp="nsxa" tid="69304494" level="INFO"] [PortOp] Property [com.vmware.port.extraConfig.security.enable] is not found on the port [1657] to clear
    2024-10-24T05:29:08.879Z nsx-opsagent[69304095]: NSX 69304095 - [nsx@6876 comp="nsx-esx" subcomp="opsagent" s2comp="nsxa" tid="69304494" level="INFO"] [AddVifRequests] Cleared security extra config from dvs [## ## ## ## ## ## ## ##-## ## ## ## ## ## ## ##] lport [1657] on detach
    2024-10-24T05:29:08.879Z nsx-opsagent[69304095]: NSX 69304095 - [nsx@6876 comp="nsx-esx" subcomp="opsagent" s2comp="nsxa" tid="69304494" level="INFO"] [AddVifRequests] Adding new vif request [opId: dvport-detach-4000] [opId:[dvport-detach-4000] op:[HOSTD_DETACH_PORT(2)] vif:[1566405522] ls:[dvportgroup-1332:## ## ## ## ## ## ## ##-## ## ## ## ## ## ## ##] vmx:[[<datastore>] <vm_name>.vmx] lp:[1657]] to hostd handlers:[dvportgroup-1334:## ## ## ## ## ## ## ##-## ## ## ## ## ## ## ##] vmx:[[<datastore>] <vm_name>.vmx] lp:[1665]]

Environment

VMware NSX 4.2.0.x

VMware NSX 4.2.1.0

Cause

This issue is caused by incorrect setting of vifCollectionStatus to VIF_COLLECTION_STATUS_INVALID by NSX Manager, due to which a logical port will not be created after the vMotion.

Resolution

This issue is resolved in VMware NSX 4.2.1.1, available at Broadcom Downloads.
If you are having difficulty finding and downloading software, please review the Download Broadcom products and software KB.

To workaround this issue, please vMotion the impacted VM to a different ESXi host. 

Powered by Wolken Software