New To T1600G-28TS, need a little guidance
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
New To T1600G-28TS, need a little guidance
Model :
Hardware Version :
Firmware Version :
ISP :
Hey All,
I'm a bit new here, as well as to the TP-Link series Smart Switches. I recently acquired 2 shiny new T1600G-28TS switches for my home network. These switches are my core switches, with a few Dlink 8-port desktop switches spread around the house for different "sub-nets". In setting up my T1600G's I have the following VLANs:
VLAN 1: General Data; 1 primary DHCP server and 1 backup DHCP server;
VLAN 10: IP Phone Intercom; 1 DHCP server provided by Dlink router (for inter-VLAN routing to VLAN 1);
VLAN 100: IPTV; 1 DHCP server provided by Telus T3200M router.
So far, most of the setup is working well. 3 of the sub-switches are DLink DGS-1100-08 desktop units, with VLANs 1 and 10 configured. All that works really well. All well and good.
Now, my issue is with the DHCP setups:
On VLAN 1 the primary DHCP is a linux box. The secondary DHCP is a Windows XP box, and is only activated when the primary is offline (power outage or maintenance, etc). On the old Dlink core switch, this was not an issue. Down the primary, start the secondary, reboot all DHCP clients, and we're off to the races. Now, however, the secondary DHCP OFFER packets are not getting back to the requesting clients. I can see the server responding to the DHCP request, but the client never receives the response. Again, the primary DHCP works fine. The secondary does not.
On VLAN 10, the DHCP is provided by an older DLink broadband router. Clients connecting directly to the router have no issue getting a DHCP lease. But through the T1600G's, forget it. This router does not supply any indication of an active lease until it becomes active. So, for the moment, all devices on VLAN 10 must be either connected directly to the router, or have static IP's to operate properly. Not desirable.
On VLAN 100, the DHCP comes from the Telus T3200M. All good here.
So, what gives? Why on VLAN 1 only the primary DHCP can do its job, and on VLAN 10, no DHCP is available? I don't have any blocking setup anywhere, in any form, especially since VLAN 100 works as well. Or are the switches determining which ports have DHCP servers hanging off them, and assuming those ports are to be the ONLY DHCP ports?:confused:
Hopefully, someone might have some insight on this one.
Cheers!
Mike
Hardware Version :
Firmware Version :
ISP :
Hey All,
I'm a bit new here, as well as to the TP-Link series Smart Switches. I recently acquired 2 shiny new T1600G-28TS switches for my home network. These switches are my core switches, with a few Dlink 8-port desktop switches spread around the house for different "sub-nets". In setting up my T1600G's I have the following VLANs:
VLAN 1: General Data; 1 primary DHCP server and 1 backup DHCP server;
VLAN 10: IP Phone Intercom; 1 DHCP server provided by Dlink router (for inter-VLAN routing to VLAN 1);
VLAN 100: IPTV; 1 DHCP server provided by Telus T3200M router.
So far, most of the setup is working well. 3 of the sub-switches are DLink DGS-1100-08 desktop units, with VLANs 1 and 10 configured. All that works really well. All well and good.
Now, my issue is with the DHCP setups:
On VLAN 1 the primary DHCP is a linux box. The secondary DHCP is a Windows XP box, and is only activated when the primary is offline (power outage or maintenance, etc). On the old Dlink core switch, this was not an issue. Down the primary, start the secondary, reboot all DHCP clients, and we're off to the races. Now, however, the secondary DHCP OFFER packets are not getting back to the requesting clients. I can see the server responding to the DHCP request, but the client never receives the response. Again, the primary DHCP works fine. The secondary does not.
On VLAN 10, the DHCP is provided by an older DLink broadband router. Clients connecting directly to the router have no issue getting a DHCP lease. But through the T1600G's, forget it. This router does not supply any indication of an active lease until it becomes active. So, for the moment, all devices on VLAN 10 must be either connected directly to the router, or have static IP's to operate properly. Not desirable.
On VLAN 100, the DHCP comes from the Telus T3200M. All good here.
So, what gives? Why on VLAN 1 only the primary DHCP can do its job, and on VLAN 10, no DHCP is available? I don't have any blocking setup anywhere, in any form, especially since VLAN 100 works as well. Or are the switches determining which ports have DHCP servers hanging off them, and assuming those ports are to be the ONLY DHCP ports?:confused:
Hopefully, someone might have some insight on this one.
Cheers!
Mike
