SG2016P gets ip address from non-management VLAN DHCP server
Our SG2016P is configured with VLAN 2 as the management VLAN and has a static ip on that LAN, where it is managed by the Omada controller. Yet the SG2016P also gets an ip address from a DHCP server on a non-management VLAN and serves up the web GUI on that non-management IP with a message saying "This switch is being managed by controller". Is there a config setting to prevent switch management on non-management VLANs?
Also in our setup there is no reason for the switch to use a DHCP client. Is there a config setting to disable the DHCP client? We configured the non-management VLAN network where the switch received an ip with a static ip address on a bogus LAN, yet the switch runs its DHCP client anyway and gets an ip regardless.
Thanks
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
Followup: turned out to be an issue on our side. Switch is working exactly as we need. The routing table now only has Management VLAN (2) routes and the managment HTTP service is only available from VLAN 2.
- Copy Link
- Report Inappropriate Content
If the switch is being managed by a controller on the management VLAN, there is no need to enable a switch interface on any other VLAN unless you are routing or providing DHCP services with the switch.
- Copy Link
- Report Inappropriate Content
Hi @jra11500 ,
Only the management VLAN (2) is enabled on the switch and it is assigned a static ip. Yet the switch still leases an ip from disabled VLAN 1 via the upstream DHCP server. It should not matter but disabled VLAN 1 is configured with a bogus static ip.
It seems the switch insists on getting an ip via DHCP regardless of which VLANs are enabled. Even when all VLANs are set to DHCP: None, the switch still leases an ip.
- Copy Link
- Report Inappropriate Content
To help assist and streamline the identification of the behavior, we recommend sending an email to forumsupport.usa@tp-link.com with the following information:
Subject: [Forum Escalation][ID 854286]
Forum Nickname:
Thread URL:
Model&Version:
Description:
Any Other Relevant Information (Logs, Config Files, Images, etc.):
Once sent, a ticket will be created in our support system, and a member of the team will follow up to gather more information or troubleshoot a cause.
- Copy Link
- Report Inappropriate Content
Followup: turned out to be an issue on our side. Switch is working exactly as we need. The routing table now only has Management VLAN (2) routes and the managment HTTP service is only available from VLAN 2.
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 408
Replies: 5
Voters 0
No one has voted for it yet.