I initially tested the EdgeSwitch 8-150W with software v1.4.0. Firmware v1.7.1 was released 6/30/17, so I downloaded this latest firmware from the Ubiquiti support website and updated the switch.
The EdgeSwitch 8-150W GUI look and feel are mostly the same between v.1.4.0 and v1.7.1. The main difference I noticed was some menu reorganization, such as the PoE menu has been moved to a sub-menu under the Basic menu. Below is a screenshot of the EdgeSwitch 8-150W dashboard. You can see the main menu options on the top right, additional sub-menu options on the top left, and basic info about the switch in the main section of the screenshot.
The EdgeSwitch 8-150W GUI is organized with six configuration tabs labeled Basic, System, Switching, Routing, Security, and QoS. Each tab provides access to other configuration menus and sub-menus. I had to hunt around the GUI to find various functions. But for the most part, I found the GUI relatively intuitive. Subsequently, I didn't have to consult the 273 page admin guide too frequently.
An important interesting feature of the EdgeSwitch 8-150W is it has Layer 3 switch capabilities. With a Layer 3 switch, you can enable routing on physical interfaces and virtual VLAN interfaces, allowing a Layer 3 switch to function as both a router and a switch.
The EdgeSwitch 8-150W can function as a DHCP server, route traffic between subnets and static routes and support policy-based routing. Policy-based routing allows creating rules to control traffic routed between VLANs. The EdgeSwitch 8-150W can be configured with up to 15 routable interfaces and 16 routes.
I tested the EdgeSwitch 8-150W's routing capabilities by connecting it to the recently reviewed EdgeRouter Lite. I enabled routing on the EdgeSwitch 8-150W and configured a port as a routed port. Once you configure routing on a Layer 3 switch port, you can then assign an IP address to that port, just like a port on a router. I connected the switch's routed port to the EdgeRouter Lite. I then configured a few VLANs on the switch, and configured a DHCP server on the switch for both VLANs. I also configured a static default route on the EdgeSwitch 8-150W to route internet traffic to the EdgeRouter Lite.
I applied most of my Layer 3 configurations to the EdgeSwitch 8-150W via the GUI, but had to enter a couple of the commands via the CLI to get it all to work. Fortunately, Ubiquiti's admin guide for the EdgeSwitches has an appendix with several configuration examples, including how to configure routing. It took a little trial and error. But once I got the configurations right, it worked as expected. Let's walk through the steps.
In the first screenshot, you can see that port 8 is configured as a routed port, and I've given that port an IP address of 192.168.2.2, which is on the same subnet as the port it's connected to on the EdgeRouter Lite.
The next image shows the two VLAN interfaces I created on the EdgeSwitch 8-150W, which enables traffic routing between VLANs 4 and 5.
Next, I've created DHCP servers for each VLAN, so devices connected to ports assigned to those VLANs will get an IP address via DHCP.
And finally, the Route Table Summary shows the switch has a default route to send Internet traffic (0.0.0.0) to the EdgeRouter Lite at 192.168.2.1, and connected routes to the 192.168.2.0, 192.168.4.0 (VLAN 4), and 192.168.5.0 (VLAN 5) networks.
With this configuration in place, the EdgeSwitch routed traffic between the 192.168.2.0, 192.168.4.0, and 192.168.5.0 networks, as well as routed internet traffic to and from the EdgeRouter Lite.
Layer 3 switching isn't commonly used on small networks. But it can be useful to keep all intra and inter VLAN traffic on the switch, allowing the router to handle just WAN traffic. This kind of network segmentation can provide better network design and performance. A Layer 3 switch can typically forward IP traffic much faster than a router, which along with reducing the router's tasks, enables the higher network performance.
Ubiquiti states the EdgeSwitch 8-150W supports up to 4093 802.1q (VLAN tagging), private, and voice VLANs. Adding VLANs to the switch and configuring ports for VLANs worked really well via the EdgeSwitch 8-150W GUI VLAN wizard. You add the VLANs by entering them individually, in a list, or in a range. You assign ports to VLANs simply by clicking on the port by VLAN to make it an untagged (U), tagged (T), or excluded (E) member of each VLAN.
In the below image, I've configured port 2 on the EdgeSwitch 8-150W as a trunk port and an untagged member of VLAN 1 and a tagged member of VLANs 4 and 5. I also configured port 4 as an untagged member of VLAN 4 and port 5 as an untagged member of VLAN 5.
With the trunk port, I was successfully able to pass VLAN 1, 4, and 5 traffic to another 802.1q enabled network device. With ports 4 and 5, I was successfully able to connect devices to VLANs 4 and 5. It was easy to see my devices were on VLAN 4 and 5 as they received IP addresses from the DHCP servers I configured in the previous section.
As mentioned previously, all 8 RJ45 ports on the EdgeSwitch 8-150W are PoE capable. The EdgeSwitch 8-150W is rated to provide up to 150W of PoE power. Per port power is limited to 34.2 W for 802.3at PoE+ devices and 17 W for 802.3af PoE.
Ubiquiti EdgeSwitches are a useful complement to a Ubiquiti Unifi based Wi-Fi network. I was able to power an older 802.11n Unifi AP Pro directly from the EdgeSwitch, as well as a NETGEAR M4100 PoE powered network switch. It is efficient to use the EdgeSwitch to power the Unifi Access Point (AP), as you no longer need to use the Unifi AP's PoE injector.
As you can see below, port 0/3 on my EdgeSwitch 8-150W is providing 3.96 W to the AP and port 0/4 is providing 12.82 W to the NETGEAR switch.
Power over Ethernet
The switch also supports Ubiquiti's 24V "passive" PoE that is used by some of its access points, such as the low-cost UAP-AC-Lite. The default PoE+ auto setting shown above is the default. If you need 24 V passive PoE, you must manually switch to it. PoE can also be disabled entirely on each port.