i don't know why/how the IP 192.168.1.152 was assigned to the VLAN ...
Don't worry, discovered IP addresses are ones for which the vmnic sees network traffic. It has nothing to do with assignments to ESXi.
When you create the PortGroup at VLAN ID I suppose you left None(0) that's why you see there 0.
Can you go on the port group properties and check VLAN ID?
>>When you create the PortGroup at VLAN ID I suppose you left None(0) that's why you see there 0.
i don't recall me creating the PortGroups. None of the three listed port groups are at "VLAN ID 1"
>>Can you go on the port group properties and check VLAN ID?
"VM Network" i'm assuming was created when i only had one nic, the one embedded on mobo when i first installed esxi 5.0 some years ago. then when i added a dual port intel EXP19402PT card, the "VM Network 2" was created. may be i did create them years ago, honestly i don't recall. ;-)
should each "VM Network" port group be assigned a different VLAN ID number?
i'll attempt attaching an image of port groups for you to see...
then no reason to delete the "VLAN ID 0" and its discovered subnets, "Subnet 1 192.168.1.152-192.168.1.152 VLAN ID 0" ? which was my original post.
i viewed this KB tonight, VMware Knowledge Base (1003825)
i found where i can actually change the VLAN ID via web client or host console. and a value "0"/zero means no VLAN.
and i see an old post you made some years back regarding VLANs, i'll read up on this.
thank you for your help.
... then no reason to delete the "VLAN ID 0" and its discovered subnets
Correct. VLAN 0 is the default setting, which means that the vmnics are connected to "untagged" ("Access ports" on Cisco switches) ports on the physical switch(es).