TL-SG3452XP acting very strange

TL-SG3452XP acting very strange

TL-SG3452XP acting very strange
TL-SG3452XP acting very strange
2023-12-21 19:18:58
Model: TL-SG3452XP  
Hardware Version: V2
Firmware Version: 2.0.3

I'm trying (and failing badly) at setting up a TL-SG3452XP remotely in the EMEA region, from the US - we used a TL-SG3428MP as a local testing environment with minimal issue (after help with this community!)

 

Connection:

FortiGate 60F, port 1 - configured to send DHCP 10.50.1.80-200 > TL-SG3452XP, port 1 (set for VLAN 1400, defined in the relay with 10.50.1.1 as the server)

 

TL-SG3452XP configured as we tested, with DHCP & VLAN relays, working correctly as far as we can tell (devices plugged into the TL-SG3452XP obtain an IP address).

 

The current issue is: how do I set the TL-SG3452XP to a static IP address in the 10.50.1.x range? If I set the VLAN (either management VLAN 1 or the created VLAN 1400) to a static IP (or secondary IP) the switch becomes inaccessible until it's rebooted (been making changes without saving until we know it works).

 

The other issue is the switch is DHCP hopping and consuming IP addresses?

bb12cf9f3f8445e9a1a46fa7ce2163e3

This is a new behavior that showed up during troubleshooting this morning.

 

Do I need to just reset / wipe the switch then start over? Forget DHCP in the FortiGate and move it to the TL-SG3452XP? (is this a possible option? We're intending to connect three APs to the switch, which need to give two IP ranges for internal and guest AP connections).

 

Thanks in advance.

 

Jason

  0      
  0      
#1
Options
5 Reply
Re:TL-SG3452XP acting very strange
2023-12-21 22:18:32 - last edited 2023-12-21 22:35:28

I made a change (to be honest, I'm not sure what specifically) and the switch is no longer grabbing multiple IP addresses.

 

The issue of the switch getting/releasing the IP address and not listening on the IP (10.50.1.80 as DHCP, 10.50.1.10 as a static IP).

 

Do I need to specify the PVID for all the non tagged ports (3-44 - 45-48 are tagged)?

  0  
  0  
#2
Options
Re:TL-SG3452XP acting very strange
2023-12-22 02:34:06 - last edited 2023-12-22 02:34:48

 Hi @JFrisbee 

Thanks for posting in our business forum.

Not sure why you have to use DHCP relay. It seems you are using simple VLAN interfaces on Fortigate and all you need to do is to set up the VLAN and pass the DHCP over. Not DHCP relay.

Get to the User Guide and read 5.2. I don't think your case should be using DHCP relay.

 

To set a static IP, you go here and edit your interface IP and as static. L3 > Interface.

 

Best Regards! If you are new to the forum, please read: Howto - A Guide to Use Forum Effectively. Read Before You Post. Look for a model? Search your model NOW Beta firmware got some NEW features! Subscribe for the latest update!Download Beta Here☚ ☛ ★ Configuration Guide ★ ☚ ☛ ★ Knowledge Base ★ ☚ ☛ ★ Troubleshooting Manual ★ ☚ (Disclaimer: Short links are used above solely for guidance to TP-Link subdomains and are safe and tracker-free. Exercise caution with short links from non-official members on forums. We are not liable for external content or damage from non-official members' link use.)
  0  
  0  
#3
Options
Re:TL-SG3452XP acting very strange
2023-12-22 16:14:48

  @Clive_A The VLANs aren't defined in the FortiGate however, but DHCP scopes assigned to the ports (port 1 for 10.50.1.x, port 2 for 192.168.80.x) - it feels like the VLAN 1 on the switch is where the "issue" comes from.

  0  
  0  
#4
Options
Re:TL-SG3452XP acting very strange
2023-12-28 16:46:59

I performed a system reset to wipe the switch back to factory, and now so far after setting the configuration up again the switch is working as expected - it seems that when the on site installer connected the internet directly to the switch instead of through the FortiGate firewall, the DHCP setting for VLAN 1 was "set".

 

Thanks,
Jason

  0  
  0  
#5
Options
Re:TL-SG3452XP acting very strange
2023-12-29 00:10:25

And now, hours later, we're back to the same functionality problem - the switch won't stay on an IP, and is inaccessible from that 10.50.1.x IP range. 

I'm inclined to say the switch is defective, but when my manager travels to Switzerland, he can make that decision.

  0  
  0  
#6
Options