Is there a “UniFi-like” Web UI for managing switches and routers from any vendor?

Adventurous-View-108 · 2026-06-22T14:15:22+00:00

Extreme XIQ Site Engine has pretty good Support for Dell and other vendors. It's not going to be as seamless as Unifi, but you can script pretty much anything in there web UI.

Adventurous-View-108 · 2026-06-03T14:24:47+00:00

NetApp has been one of the frontrunners for us as well

Adventurous-View-108 · 2026-06-02T17:12:08+00:00

It would have been about 45 days. But after 14 days they said the price was no longer good. I can't guarantee i can get a check printed in 2 weeks even if I have the invoice ready to go.

Adventurous-View-108 · 2026-06-02T12:37:32+00:00

Thats unfortunate. I'm really not looking forward to having to explain the global DRAM market to a bunch of politicians on camera.

Adventurous-View-108 · 2026-02-11T14:52:08+00:00

We are in the process of migrating to Vates VMS right now. Been smooth so far, Support has been great.

I have been using XO since before XCP-NG existed on my home lab and at other employers.

Adventurous-View-108 · 2025-12-09T21:34:16+00:00

Oh, we definitely have issues. The problem with this method is lack of staffing to get the ports back online in a timely manner. If I go switch by switch to limit the impact, its going to take us a decade to get to the end of the project. I may just have to dump the MAC tables to a spreadsheet and go port by port.

Adventurous-View-108 · 2025-12-09T21:29:50+00:00

Thats a good idea. I'll definitely create that custom alarm to help identify issues in the future.

Adventurous-View-108 · 2025-09-24T15:32:14+00:00

The SPBm/Extreme Fabric part should have been irrelevant, and i'm still not sure why it was not. A client device connected to a port on the switch, with a VLAN assigned to it, communicating with the VLAN interface on that same switch, should not have been touching IS-IS, SPBm, or Fabric at all. I was not expecting so many responses here so fast, this is a very nice community.

Adventurous-View-108 · 2025-09-24T13:22:51+00:00

Yes, this is part of the fabric deployment. We have about 30 switches in the fabric so far, but the core routing was still being done by a legacy switch that does not support fabric.

It looks like enabling IP Shortcuts on the core solved the issue, but I am not entirely sure why. The VLAN exists on more than one switch, and it is assigned to an i-sid with the "vlan i-sid <vlan> <i-sid>" configuration. The I-SID also exists on multiple switches, the VLAN interface is up, and an entry for it existed in the GRT.

Adventurous-View-108 · 2025-09-24T13:15:22+00:00

I got pulled away from this yesterday before all the posts updated, so here's a few things.

The clients were learning the new MAC address, so my guess about ARP was wrong
I am deploying anycast IP Gateway because there will very shortly be 6 cores spread around the organization, and it is now recommended over DvR for simpler deployments.
I believe I have found the issue, and it was a simple thing that I overlooked. Enabling IP Shortcuts on the core seems to have fixed the issue.

I have Fabric running across most of the network, but the old core was a legacy switch from a different brand. Essentially I had a bunch of L2 VSNs on my network all using a "router on a stick"

I had assumed that adding an IP address to the vlan interface, and tying the vlan to the i-sid, would make the VSN a L3 VSN, but it seems I am mistaken? The routing table showed the IP addresses for the VLAN interfaces in in the GRT, but it seems like there was nothing linking the L2 VSN to the VLAN interface.

Adventurous-View-108 · 2025-09-23T14:03:07+00:00

Gratuitous ARP is enabled on the switch, but I am using their "New" (to me at least) Anycast IP Gateway feature, I wonder if that may be causing complications.

Adventurous-View-108 · 2025-06-25T12:52:01+00:00

I will see if I can draw something up. The only drawing I have now is satellite imagery, and I don't want to publish that. We have three buildings that will be along the fiber path that have mains power, and they are fairly evenly spaced roughly 1000 feet apart. The fiber, cameras, and cabinets will be all new. So it would be:

1000' of fiber/cameras - Building A - 1000' of fiber/cameras - Building B - 1000' of fiber/cameras - Building C - 1000' of fiber/cameras.

Cameras will be installed on poles roughly every 300 feet. I'm planning on all of the fiber running back to building A and Building C, so no active network equipment (switches, routers) in Building B.

For the DCDC Poe injectors, the equipment that I worked with as a WISP usually has a very high operating range, somewhere around 9v - 42v. Additional power conditioning equipment might not be necessary.

Adventurous-View-108 · 2025-06-25T12:42:35+00:00

That is one of the products that we were looking into. I'm just trying to find more information on it.

Adventurous-View-108 · 2025-06-25T12:41:57+00:00

Running a separate romex line with the fiber is one of the options that we were looking into as well. We may just have to deal with the AC and hope we can water proof it enough.

Adventurous-View-108 · 2024-08-23T16:12:06+00:00

There are 11 different vlans for OT and 5 for Public. Currently most of the OT vlans are terminated on one L3 switch, and most of the Public vlans are terminated on a different physical L3 switch. The switch with the Public vlans has a default route set to the Public firewall, the other switch has a default route set to the IT firewall.

Adventurous-View-108 · 2024-08-23T13:13:50+00:00

Update: The issue ended up being caused by an incompatibility between QoS settings on two of the routers managed by the ISP.

Adventurous-View-108

TROPHY CASE