Vmkernel log and Aria report multiple repeated alerts related to LAG:
vmkernel: cpu##:###### opID=######)Uplink: 2729: LAG name: not found
vmkernel: cpu##:###### opID=######)Uplink: 2729: LAG name: not found
vmkernel: cpu##:###### opID=######)Uplink: 2729: LAG name: not found
VMware vSphere ESXi
VMware vSAN
The above alerts are generated by the vSAN management daemon trying to retrieve uplink information for LACP LAG, when it shouldn't:
vsansystem log:
vsansystem[2101359]: [vSAN@6876 sub=AdapterServer opId=c5b4c269-######] Invoking 'getNetworkDiagnosticsHealthInfo' on 'ha-vsan-health-system' session '5223f0c4-bc17-e3c0-f14d-#########' active 1
vsansystem[2101359]: [vSAN@6876 sub=Libs opId=c5b4c269-######] VsanInfoImpl: Refresh config generation
vsansystem[2101359]: [vSAN@6876 sub=Libs opId=c5b4c269-######] VsanInfoCluster: vSan mode is set to : Mode_None
vsansystem[2101359]: [vSAN@6876 sub=Libs opId=c5b4c269-######] VsanInfoImpl: LoadEncryptionConfigFromConfigStore enabled 0 kekId hostKeyId dekId kmsId
vsansystem[2101359]: [vSAN@6876 sub=Libs opId=c5b4c269-######] VsanInfoDatastore: Load default datastore name vsanDatastore
vsansystem[2101359]: [vSAN@6876 sub=AdapterServer opId=c5b4c269-######] Finished 'getNetworkDiagnosticsHealthInfo' on 'ha-vsan-health-system' (161 ms): done
Issue will be fixed in vSphere 9.0 u1.
The alerts do not cause any production impact.