NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Greg_905
Feb 20, 2025Follower
S3300-52X VLAN trunking not working on uplinks
Hello! Wanted to use this switch for management interfaces and related, but I can't reach any hosts on it that are connected to it, only the switch itself is reachable. Before it worked fine, but we were not doing any trunking, all ports were on the same VLAN, the default.
There are a few VLANs trunked to this switch, here i'm attempting to reach a host on VLAN 104 on port 1, the host is set up correctly network wise - it was using DHCP, when that failed I gave it a static.
Switch management IP is in VLAN 106, and it is reachable. I can load the web interface without issue from other L3 networks at work.
Port 51 is configured to Tag all VLANs excluding VLAN 1 which is left untagged.
Port 1 is set to Untag VLAN 104. the Host connected to this port was first configured to use DHCP, but when that didn't work I gave it a static IP in the proper CIDR for VLAN 104.
The switch which this is connected to is a Dell S5248F-ON. We have about 20 some other switches connected to this and other S5248F-ON's, of various brands, Brocade, Mellanox, Cisco, and other Dells. All have the trunk ports configured the same way on the Dells, and all switches are able to pass Tagged VLAN traffic between them, this is the first time running into an issue.
I've configured something wrong perhaps, but it looks sane and I referenced the setup guide (first time using a Netgear at work).
On the web portal - Switching - VLAN - Advanced - VLAN Membership, I have port 1 (where host is connected) set to Untagged VLAN 104, and port 51 set to Tagged.
Connected to port 51 is the Dell with a 'standard' configuration for trunking VLANs to another switch, same stanza used with all the other switches.
sw-work1# show running-configuration interface eth 1/1/1:1
!
interface ethernet1/1/1:1
description UPLINK_TO_SW-WORK-MAN1
no shutdown
switchport mode trunk
switchport access vlan 1
switchport trunk allowed vlan 100-104,106-108
flowcontrol receive off
sw-work1#On the netgear:
interface 1/xg51
description 'UPLINK_TO_SW-WORK'
vlan participation include 102,104,106-107,200-201
vlan tagging 102,104,106-107,200-201
exit(VLANs allowed matched on both ends when I started problem solving - they will again when done)
And the access port:
interface 1/g1
description 'PC-TEST'
vlan participation auto 1
vlan participation include 104
exit
Here you can see we have tagging enabled on port 51 and Untagged on Port 1:
And here I see something that does not look correct:
It sees MAC's from the network on the uplink, it seems to know some of them are from VLAN 102, Oddly, its only seeing a fraction of the hosts, there are a lot more on VL102, 103, 104 and 107, yet none are seen. most all those ones on "VLAN 1" are not part of VLAN 1, no hosts of any sort are on VLAN 1 within the production network.
the A4:BB one on port 1, is the host I'm speaking of, even tho its 'hard set' to VLAN 104 membership on the Netgear. Tried another host on different ports but same behaviour.
Any idea why this may be happening?
No RepliesBe the first to reply
Related Content
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!