NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
Vlan port issue
We have phone system equipment that we are moving from a Netgear GSM7224P to a Netgear M4100-24G-POE+ switch. A couple of the ports need to have vlan tagging a certain way in order to work with the phone system equipment. When I moved the equipment to their new ports, I was no longer able to ping or see the equipment on the network. Here is what we have for the old switch and the new switch.
Devices ports being moved
device 1 Vlan 1 none, Vlan 2 untagged
7224 -> M4100
20 21
Device 2 Vlan 1 none, Vlan 2 tagged
7224 -> M4100
22 19
7224p
Vlan 1 ports
7224 vlan 1
Vlan 2 ports
7224 vlan 2
M4100
Vlan 1 ports
Vlan 2 Ports
I do see a new vlan trunking configuration that is on the M4100 that is not on the 7224, would this have an impact?
Ok, I have found and resolved my problem! I forgot to check the PVID configuration, which for those ports needed to be assigned to vlan 2. Good rookie mistake on my part.
2 Replies
Ok, I have found and resolved my problem! I forgot to check the PVID configuration, which for those ports needed to be assigned to vlan 2. Good rookie mistake on my part.
Hi Joel_pscu,
Thank you for sharing that in our community!
Definitely, if we are about to create VLANs on our NETGEAR switch, Always remember that if the device that will be connected to a port is a VLAN aware unit, the port should always be set to T or Tagged on the VLAN membership and if not, it should be U or Untagged then specify the VLAN under PVID configuration.
Welcome to our community!
Regards,
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
