NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
PeterA23
Jul 12, 2017Initiate
WC7600v2 only connects to one switch / strange behaviour
Hi Netgear Community, We have a strange situation here at my site. We currently use a WC7600v2 with the latest firmware (6.5.1.11) and a wireless network of 32 AP's of various makes and models of...
- Jul 17, 2017
Hi John,
Thanks for the reply.
After some more of the gnashing of teeth, I decided to consult the manual of the 7600v2 once more and I realised that the ports on the 7600v2 are already set to TRUNK mode if you DON'T tick the Untagged management option in the web interface settings. Meaning management traffic the 7600v2 by default is TAGGED and the device is expecting the traffic to appear as such on the port.
Since I was following the configuration that was implement previously at the site I replicated the port config on 5120EI that was on the port the GSM7224 that originally had connect the 7600v2. The port on the 5120EI was configured as follows,
interface Gigabit 1/0/3
description ** Link to Netgear 7600v2 **
undo port trunk permit vlan 1
port link-type trunk
port trunk permit vlan 200 400 to 410
port trunk pvid vlan 400
broadcast-suppression 20
Now knowing that VLAN 400 was the management VLAN for management traffic for the wireless network you would expect that there would be no problem in port 1/0/3 providing management traffic to the 7600v2 but alas, because of the PVID 400 statement the traffic would appear on the port as UNTAGGED traffic to the wireless controller and thus inaccessible.
On the GSM7224 the PVID port config allows for ANY type of 400 traffic both tagged and untagged by nature of the software on Netgear devices and it looks like the H3C 5120EI adheres to a stricter standard. Once I removed the PVID on port 1/0/3 statement, the 7600v2 performed as expected and configured.
I just find it so strange that the interpretation of such basic standards are so different between vendors.
Let us not even get started on Netgear's GSM7224 10.0.2.26 firmware igmp-snooping implementation that breaks cisco router traffic, but that will be a post for another time after some testing.
JohnC_V
Jul 12, 2017NETGEAR Moderator
Hi PeterA23,
It seems that you pretty isolated the issue already. Netgear wireless controllers doesn't have any propriety issues with other manufacturers. In order to assist you further on this issue, please open a chat / case online on NETGEAR Support and let them know the status of your network.
Welcome to our community!
Regards,
PeterA23
Jul 17, 2017Initiate
Hi John,
Thanks for the reply.
After some more of the gnashing of teeth, I decided to consult the manual of the 7600v2 once more and I realised that the ports on the 7600v2 are already set to TRUNK mode if you DON'T tick the Untagged management option in the web interface settings. Meaning management traffic the 7600v2 by default is TAGGED and the device is expecting the traffic to appear as such on the port.
Since I was following the configuration that was implement previously at the site I replicated the port config on 5120EI that was on the port the GSM7224 that originally had connect the 7600v2. The port on the 5120EI was configured as follows,
interface Gigabit 1/0/3
description ** Link to Netgear 7600v2 **
undo port trunk permit vlan 1
port link-type trunk
port trunk permit vlan 200 400 to 410
port trunk pvid vlan 400
broadcast-suppression 20
Now knowing that VLAN 400 was the management VLAN for management traffic for the wireless network you would expect that there would be no problem in port 1/0/3 providing management traffic to the 7600v2 but alas, because of the PVID 400 statement the traffic would appear on the port as UNTAGGED traffic to the wireless controller and thus inaccessible.
On the GSM7224 the PVID port config allows for ANY type of 400 traffic both tagged and untagged by nature of the software on Netgear devices and it looks like the H3C 5120EI adheres to a stricter standard. Once I removed the PVID on port 1/0/3 statement, the 7600v2 performed as expected and configured.
I just find it so strange that the interpretation of such basic standards are so different between vendors.
Let us not even get started on Netgear's GSM7224 10.0.2.26 firmware igmp-snooping implementation that breaks cisco router traffic, but that will be a post for another time after some testing.
Related Content
NETGEAR Academy

Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!