NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
GS724Tv3 VLan tagging issues
Hello all!,
Forgive me if I misformat this a bit as I am new to the forum
Recently I came into owning a Netgear Prosafe GS724Tv3 and I am planning on using it as the core switch for my virtualization rack at my home lab. I ran into some issues properly configuring VLANs, I (to the best of my knowledge) seem to have built a proper configuration but it appears as if my traffic is not getting tagged and my ESXi on a trunked port is not able to send VLAN traffic and can only communicate with a VLAN of 0.
Any advice would be welcome! attached are a few images of my configuration
Imgur: Model + Boot / Software version
ESXi configuration included to demonstrate how I troubleshot the issue, I am including it primarily to make sure that my troubleshooting steps diagnosed the issue properly
imgur: ESXi vSwitch + Port Groups
To troubleshoot I configured the VLANs as above and attempted to obtain a DHCP IP address on VLAN 10 to no success, added the DHCP TEST portgroup on VLAN 0 and was able to successfully get an IP address
The ESXi is plugged into ports 24 and 22 and I access the device via port 23.
Thank you!
I found the issue!,
luckily when I was diagnosing the vSwitch as you mentioned I seem to have come accross the problem being,
and do I feel very dumb for not realizing this sooner, I had the two cables connecting the ESXi in the opposite ports,
so the correctly tagged VLAN 10 traffic was allowing me to manage the ESXi and the PVID with an untagged port was not allowing me to tag my own VLAN traffic.
I was able to test this and verify it is all functioning as intended,
thank you for all the help and I appriciate you taking your time on my problem!
and I am sorry it was such a small issue!
7 Replies
Replies have been turned off for this discussion
There are several VLAN configured with the same ports untagged - this is not a plain standard VLAN config, this kind of asymetrical VLAN will cause issues. Use only tagged ports for any kind of trunks (where you want to access mutiple VLAN from the vSwitch). Run only one untgged VLAN to one port, and set the PVID to the same VLAN.
Thank you for your response!,
I believe I am a bit confused,
For VLAN 40 Ports 1-6 are untagged - Port 24 is tagged - all others have no membership
For VLAN 30 Ports 7-12 are untagged - Port 24 is tagged - all others have no membership
For VLAN 20 Ports 13-18 are untagged - Port 24 is tagged - all others have no membership
For VLAN 10 Ports 19-23 are untagged - Port 24 is tagged - all others have no membership
does the asymetry occur because I have multiple instances of ports with no membership to that VLAN?
It appears as if all untagged ports belong to a single VLAN and PVIDS match to the VLAN and physical port.
Thank you again!
Oh sorry for the confusion - I must have had opened the same Imgur link multiple times - ignore what I wrote above.
Everything on the port 24 (VLAN 10, 20, 30, and 40) must be tagged on the Vmware side.
Ensure the PVID on the untaged port does match the VLAN ID - otherwise the traffic flowing to the switch will end on a wrong subnet (as defined by the PVID of course).
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
