TL-SG3452P 3.0 | VLAN Issues
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
Hello Supporters,
I'm trying to configure my core switch and it fails even with the basic setup of VLAN.
It is not my first L2/L3 switch and I've managed a lot complicated configuration so far - but it is the first time with TP-Link and I don't know if it's the last...
On a untagged port of VLAN888 it won't pull any ip address over dhcp.
If I'm using static ip for device on that port I can access the device.
So I think something with the DHCP relaying is not working.
L3 Features > DHCP Service > DHCP Relay > Enabled
L3 Features > DHCP Service > DHCP L2 Relay > Enabled and for VLAN Config also Enabled
I've tried to configure the ports in CLI:
For the "trunk" port for firewall/dhcp connection in VLAN1 untagged and VLAN555,666,777,888,999 tagged.
config
interface gigabitEthernet 1/0/48
switchport pvid 1
switchport general allowed vlan 1 untagged
switchport general allowed vlan 555,666,777,888,999 tagged
show interface switchport gigabitEthernet 1/0/48
Port Gi1/0/48:
PVID: 1
Acceptable frame type: All
Ingress Checking: Enable
Member in LAG: N/A
Link Type: General
Member in VLAN:
Vlan Name Egress-rule
---- ----------- -----------
1 System-VLAN Untagged
555 SANDBOX Tagged
666 SOURCES Tagged
777 FAMILY Tagged
888 TECHNICS Tagged
999 GUEST Tagged
end
For the untagged port for device in VLAN888
config
interface gigabitEthernet 1/0/5
switchport pvid 888
switchport general allowed vlan 888 untagged
show interface switchport gigabitEthernet 1/0/5
Port Gi1/0/5:
PVID: 888
Acceptable frame type: All
Ingress Checking: Enable
Member in LAG: N/A
Link Type: General
Member in VLAN:
Vlan Name Egress-rule
---- ----------- -----------
888 TECHNICS Untagged
end
I didn't find any way to change the port type from General to Trunk or Access - this Option is just not available in GUI or CLI.
Please provide me the correct steps in GUI or even CLI to setup the VLAN properly.
I'm also sending this thread to the official support - and will post the outcome here as well.
I know that is working somehow.
Thanks for your help.
Lukas
@Tedd404 Hello,
you are totally right and that's the point why I was confused about.
But I've managed it and Iit was my fault.
>>> I used the wrong patch to the firewall...
All ports, even the LACP and uplink Static-LAG to another TL-SG1016PE are working fine and as expected.
I was just searching on the wrong side and since the switch was the only unknown in my constellation I was handling this part.
Sometimes the solution is easier than expected.
All done and case closed.
Thanks for your response.
Cheers
Lukas