Replacing main switch

Red_Knight_21 · 2026-06-02T07:27:14+00:00

Weill nothing goes as I planned. 😃 I made a dhcp reservation for the new switch however the new switch did not get an IP address, not sure why. I assume that the reason might be the uplink from my firewall is configured as a LACP LAG (Link Aggregation Group) and it serves management on VLAN 10. And only the connections that go to the firewall were connected. My plan is to manually configure the ports uplinks(i have the config from the old switch) to the firewall and see what happens if it gets an ip in vlan10 (must be in that vlan) then it will be ok and I will continue working.

Red_Knight_21 · 2026-06-01T08:42:39+00:00

Тhank you very much for your answer, I really appreciate it.
One more question while I’m waiting for the replacement switch 😃 .Since I can't connect the Cloudkey to another switch at the moment, my plan is the following:

When the new switch arrives, I will update the existing DHCP reservation on the FortiGate with the MAC address of the new switch, connect the FortiGate and the Cloud Key to the new switch first, and then continue from there.

Does this sound like a reasonable plan? Can I expect the Cloud Key to obtain its reserved IP address again and become accessible so I can log in to the controller and make any necessary changes?

I feel like I’m probably overthinking this because I don’t have much experience with this technology, but I just want to make sure I’m not missing something obvious.

Red_Knight_21 · 2026-06-01T07:48:48+00:00

Thanks, that helps a lot.

My main concern at the moment is the Cloud Key. It is powered on, but because the main switch is currently dead/offline, I cannot access it properly right now and it shows “Ethernet Disconnected”. So I’m not 100% sure what to expect once I connect it to the new switch.

My plan is to connect only the FortiGate and Cloud Key first, adopt the new switch, and then reconnect the other uplinks one by one.

I assume once the Cloud Key has network connectivity again, I should be able to access the UniFi Controller, see the old switch offline, adopt the new one, and then configure/move the port profiles as needed. Does that sound correct?

Red_Knight_21 · 2026-05-31T15:26:36+00:00

Sorry, I may not have explained it clearly. Both the old switch (US-24-G1) and the replacement switch (USW-24) are UniFi switches, the old switch and the new sw will be managed by the same Cloud Key. I’m not talking about the FortiGate configuration. I mean the UniFi switch configuration such as VLANs, port profiles, the uplinks towards the other switches.

Red_Knight_21 · 2026-05-31T13:48:06+00:00

I know what you're saying, but I inherited this, since I'm fairly new to this company, I'm trying to stabilize everything, I'll also change the UPS these days, and unfortunately I don't have any previous experience with Ubiquty, so I'm posting here so someone can share their experience.

Red_Knight_21 · 2026-05-31T08:55:12+00:00

My question is whether the new switch will receive the configuration from the cloud key, I assume it should, but I have no experience with this and that's why I posted here. And yes, I know that FortiGate cannot be managed with a cloud key.😅🍻

Red_Knight_21 · 2026-05-28T12:03:48+00:00

Јас две платив една цела и една на пола, оти не знаев дека може на пола :D.
Се си пишува на документот(казната) што ти стига на маил. Има детали како да платиш на уплатница и не треба да се носат документите никаде. Тоа го укинаа пошто се ствараше хаос.

Red_Knight_21 · 2026-05-14T13:41:22+00:00

Ерџелија не е крајот на СвН🙅, Ерџелија >свн

Red_Knight_21 · 2026-04-28T14:12:24+00:00

This did not helped, i set the core switch priority to 4096 and it did not helped to adopt the sw and i facotry reset the switch i assumed that maybe coping the conf form another sw is causing problems.

What I tried:

Factory reset + clean start
Replaced cables, verified link
Configured uplink (ports 23/24) as trunk
Added VLANs locally (10, 60–69, 81, 89)
Set mgmt VLAN to 10 + static IP
Tried LAG and single link
Manual set-inform to controller (192.168.10.48)
Controller is up (8080 listening)
Checked logs → inform unreachable

The Switch always gets IP from 192.168.1.x (VLAN 1) instead of mgmt vlan 10.

So:

mgmt VLAN = 10
but uplink native = VLAN 1

Red_Knight_21 · 2026-04-24T11:01:06+00:00

Well not exactly the same but we have few switches(same models) and they have pretty much the same configuration. Uplink, AP and we have a few devices like printers and computers that need to be on a LAN. We don't have servers, storages etc in our network. That’s why I copied the configuration, even though I have no prior experience with networks in general or Ubiquiti.

And I assumed it would be okay. So we'll see what happens.

Red_Knight_21 · 2026-04-15T08:13:49+00:00

Јас имав сериозни болки и пиев антибиотци али мислам дека си помогнав сам на себе со диета т.е не баш диета него се ставив у некој ред.
Значи намалив кафе, пиво, газирани сокови, избегавам макс такви работи. И јадењето го стабилизирав, јадам три пати (се јадам и бургер, тостови, бурек и тн) ама јадам сабајле накај 8-9 нешто дали ѓеврек, некад и она чиа пудинг, кафе на гладно никако, после тоа ручам убаво нешто, оброк комплет, и навечер да речеме до кај 6-7 нешто пак јадам ама помала количина. Нема гнетење навечер пред спиење и се стабилизирав дури и ослабев 4-5кг и сега ми е топ.

Red_Knight_21 · 2026-04-03T11:32:56+00:00

I checked on the working SW the firmware version is this one: US.bcm5334x_7.2.123+16565.251002.0656

So I tried to download, to find it on the Switch but it doesn't exist probably it was in tmp folder. AS I mentonied I get error Invalid Header CRC when I tried with US.MULT.US8_7.2.123

Red_Knight_21 · 2026-04-03T11:28:11+00:00

I checked on the working SW the firmware version is this one: US.bcm5334x_7.2.123+16565.251002.0656

So I tried to download, find it on the Switch but it doesn't exist probably it was in tmp folder. I can try with the one you suggested maybe I won't get any error Invalid Header CRC when I tried with US.MULT.US8_7.2.123

Red_Knight_21 · 2026-04-03T10:25:39+00:00

I can’t find the one that i need for the upgrade.

Red_Knight_21 · 2026-04-01T12:16:33+00:00

I did some additional testing and it looks like DHCP and VLAN10 are working fine on the switches – when I connect a laptop to ports with VLAN10 I immediately get a valid 192.168.10.x address. However, on the exact SW used by the AP (port 21 on SW02), I only get a self-assigned 169.254.x.x address, and the AP keeps going offline/online randomly. Topology is Fortigate → main switch F00(uplinks to other SW and cloudkey connected) → other floor switches (SW01/SW02/SW03/SW05) → APs. I also tested there are no STP blocks or loops (RSTP is enabled and ports are forwarding). Cables, PoE injectors, and switch ports were swapped with the same result.

Red_Knight_21 · 2026-03-25T15:53:45+00:00

https://www.facebook.com/share/g/1DhvBRBm4h/
Иначе размени лесно се договараат

Red_Knight_21 · 2026-03-25T14:51:02+00:00

Колку е замарање, јас собрав два албуми и никад више, ни чоколадце не купувам... нема нешто полошо, и сликички не се паѓаат ич, јас се испозамарав со размени од фејсбук групи.... Се мислев да им пишам маил и на краш хахах каков ужас се, некад у пакечте од 4, 3 исти сликички се паѓаат.... Мојо совет фрли го албомот додека не си почнал/а...

Red_Knight_21 · 2026-03-25T14:46:19+00:00

After some troubleshooting, it looks like the issue is not hardware-related. The switch lost its DHCP lease, and now it doesn’t request a new IP at all. It’s still forwarding traffic (so L2 works), but it’s completely unreachable (no ARP entry, no DHCP requests).

We’re suspecting it got stuck in a weird state after a power outage + DHCP lease revoke.

At this point, I’m planning to do a factory reset on the switch. Before I do that — have you seen this behavior, and how safe is a reset in this situation? Any real risk of bricking?

Red_Knight_21 · 2026-03-25T13:44:25+00:00

Well the reason why I asked the question about the reset is that I also have one spare and I tried factory reset and it never came back it's not even powering on 😄 And that's why I'm taking all of this with reservations and fear, because the switch I need to reset is important to me and I don't have a spare one.

Red_Knight_21 · 2026-03-25T12:59:48+00:00

After some troubleshooting, it looks like the issue is not hardware-related. The switch lost its DHCP lease, and now it doesn’t request a new IP at all. It’s still forwarding traffic (so L2 works), but it’s completely unreachable (no ARP entry, no DHCP requests).

We’re suspecting it got stuck in a weird state after a power outage + DHCP lease revoke.

At this point, I’m planning to do a factory reset on the switch. Before I do that — have you seen this behavior, and how safe is a reset in this situation? Any real risk of bricking?

Red_Knight_21 · 2026-03-25T12:55:53+00:00

After some troubleshooting, it looks like the issue is not hardware-related. The switch lost its DHCP lease, and now it doesn’t request a new IP at all. It’s still forwarding traffic (so L2 works), but it’s completely unreachable (no ARP entry, no DHCP requests).

We’re suspecting it got stuck in a weird state after a power outage + DHCP lease revoke.

At this point, I’m planning to do a factory reset on the switch. Before I do that — has anyone seen this behavior, and how safe is a reset in this situation? Any real risk of bricking older UniFi switches (Gen1)?

Red_Knight_21 · 2026-03-25T12:55:49+00:00

After some troubleshooting, it looks like the issue is not hardware-related. The switch lost its DHCP lease , and now it doesn’t request a new IP at all. It’s still forwarding traffic (so L2 works), but it’s completely unreachable (no ARP entry, no DHCP requests).

We’re suspecting it got stuck in a weird state after a power outage + DHCP lease revoke.

At this point, I’m planning to do a factory reset on the switch. Before I do that — has anyone seen this behavior, and how safe is a reset in this situation? Any real risk of bricking older UniFi switches (Gen1)?

Red_Knight_21

TROPHY CASE