NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
webrat11
Dec 14, 2018Tutor
DAISY CHAINING 3 PROSAFE SWITCHES - TAGGING ISSUE
Hi all,
I am trying (again) to apply VLANS to my network. Just for the fun of it, to separate my IP Cameras and Media Server and to prune back VLAN1.
I have had success connecting several pairs of switches but have reached a problem when daisy chaining 3 Prosafe switches. All on latest software. This picture is a partial snapshot of my network. I have tried several combinations of Tags but I haven’t cracked it yet. I refer to them as
Top --> Middle --> Bottom here.
The chain starts at Port 11 on the main the distribution switch (top). Between the top switch and middle switch the trunk ports are tagged 'T' at both ends - that works. If I tag both ports on the middle to bottom switch I lose sight of the bottom switch, on the Prosafe Client PLUS Utility and the web interface.
Interestingly after setting the last switch to factory defaults and rebooting via DHCP (with VLAN unchanged i.e. All VLAN1) it returns a VLAN3 address for default 192.168.3.239 IP address . So the PFsense DHCP server is seeing it on VLAN3. Possibly tagged by the middle switch, but why VLAN3?
For info Port 1 on the top switch connects to the Pfsense router. Any 'T' Tags added to this line results in loosing access downstream. VLAN3 and VALN4 work fine with this configuration.
Any suggestions please?
Thanks,
Ian
All sorted. One of the devices had a fixed IP which seemed to upset the others ...weird.
Thanks for your help.
6 Replies
Replies have been turned off for this discussion
- DaneANETGEAR Employee Retired
Hi webrat11,
Interestingly after setting the last switch to factory defaults and rebooting via DHCP (with VLAN unchanged i.e. All VLAN1) it returns a VLAN3 address for default 192.168.3.239 IP address . So the PFsense DHCP server is seeing it on VLAN3. Possibly tagged by the middle switch, but why VLAN3?
Kindly double-check the physical connections as it might lead why the pfSense DHCP server is able to detect the bottom GS105E switch on VLAN3.
Let us try this: Set a static IP address to the GS105E switch that is within the IP address range of VLAN1. Then, disconnect the middle GS108Ev3 switch from port 11 (tagged) of the top JGS516PE switch for the meantime and connect port 4 (tagged) of the bottom GS105E switch to port 11 of the top JGS516PE switch. Check if both the JGS516PE and GS105E can be accessed from the pfSense router through VLAN1. Are you able to access both JGS516PE and GS105E web-GUI through VLAN1?
Regards,
DaneA
NETGEAR Community Team
- webrat11Tutor
Hi DaneA,
thanks for the response. I did as you suggested; both switches can be accessed through the web-GUI on VLAN1. The VLAN3 problem was due to an incorrect PVID I suspect.
Out of necessity I have reset the GS105E switch and disabled the VLAN. In that mode all three switches are visible. The devices on the bottom swicth are visble.
Is my tagging correct in theory if not practice?
Thanks, Ian
The U(ntagged) for the daisy chain link for the VLAN1 on the office switch looks wrong, as the next hop is T(agged).
Related Content
NETGEAR Academy

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