Service Edge

The Service Edge (SE) connects a physical customer location to a VNET. An SE is a network device with multiple ports and Wanscale SD-WAN software already installed.

With an SE you configure WAN ports and SD-WAN policies to steer traffic. You can also create (v)LANs for your internal networks and bridge them to your VNET.

A WAN interface can optionally name a Managed WAN as its upstream.

Hardware

Wanscale offers multiple hardware models for different performance needs. Higher-tier models provide extra CPU and RAM for higher WAN speeds.

Order a Service Edge

Talk to Wanscale if you want to order an SE.

You can also create a new SE in the Wanscale Control Center. A ticket is created and a Wanscale representative contacts you so the correct model can be determined. The hardware is then dispatched.

Overview and health

After you open a Service Edge, the overview puts health and what still needs attention first.

At the top you see whether the service is Up, Down, or Degraded, together with Last seen — the last time the device reported in.

The overview then shows:

• Bandwidth, Latency, and Packet loss for the last hour, plus Active alarms.
• Performance history — switch between Bandwidth, Latency, and Packet loss over periods such as Last 12 hours or Last 7 days.
• Details — name, tags, virtual network, and deployment status.
• Hardware — hardware identifier, uptime, and Platform status (when the SE is linked to a VNET).
• Location — address and map, or a warning when none is set.

Platform status sits on the Hardware card. Typical values are Connected, Connected (degraded), Disconnected, or a partial count of paths that are up. Expand the breakdown to see each WAN path, then click Platform paths for the full view.

Banners appear when something still needs work — for example when the SE is not linked to a VNET, has no location, or a WAN interface is not in a WAN interface group. Use Fix or Connect to VNET on the banner to continue.

Actions menu

Click Actions for high-impact work in one place:

• Edit name and Edit tags
• Set location or Edit location
• Connect to VNET (when none is linked)
• Disconnect from VNET (when a VNET is linked)
• Register hardware or Unregister hardware
• Delete service — only when the SE is not linked to a VNET

Platform paths

1. Navigate to Platform paths in the sidebar (under SD-WAN) to correlate live path quality with recent up and down changes.
2. Review path state next to live metrics.
3. Click Show historical information to include recent history.

Short time ranges load that period rather than a full day.

Provisioning workflow

The diagram below outlines the lifecycle of creating and deploying a Service Edge:

flowchart LR
    A(Create SE in Control Center) --> B(Configure SE) --> C(Link SE to VNET) --> D(Install the device) --> E(Link device to SE in Control Center)
    F(We are notified, model is determined and device is dispatched) --> I(Device received by customer)
    A --> F
    I --> D

    style A fill:#34ebb1
    style B fill:#34ebb1
    style C fill:#34ebb1
    style E fill:#34ebb1

Step 1: Create a Service Edge

1. Navigate to the Home page of the Wanscale Control Center.
2. Click Add Service.
3. Select Service Edge.
4. Click Go to service form.
5. Complete the following fields:
   • Service edge name: Enter a unique name for this SE.
   • Tags (optional): Add labels for your own organisation.
6. Click Add Service Edge.

Control Center opens the overview. A new SE typically shows Deployment status Ordered, no VNET yet, no location, and operational status still down until hardware is registered and changes are applied.

Step 2: Configure the Service Edge

Walk through the basics with one LAN interface and two WAN interfaces.

Set the location

1. On the overview, click Actions, then Set location. You can also click Fix on the location warning.
2. Choose Select Existing Location to reuse a site, or Create New Location.
3. For a new location, enter Location name and Address (or toggle Use coordinates), then complete House number.
4. Click Save.

To see every site and which services sit there, navigate to Admin and open Locations.

Configure basic interfaces

1. In the left sidebar, expand Interfaces and select Basics.
2. Review the physical port assignments. By default:
   • Ports 1 & 2: WAN.
   • Port 3: LAN.
3. To change a port function, click the ellipsis (...) in Actions and select the desired function.

Configure LAN interfaces

1. In the left sidebar, expand Interfaces and select LAN.
2. To view details for the LAN port (for example Port 3), click the arrow next to the port label.
3. Click Add IP configuration.
4. In the right sidebar, enter:
   • Label: A descriptive name for the interface.
   • Primary IP address: Enter the address in CIDR format (for example 192.168.1.1/24).
   • VlanID (optional): Enter a dot1q VLAN ID if required.
   • DHCP: Select DHCP Server (set pool/DNS), DHCP Relay, or No DHCP.
5. Click Add.

Configure WAN interfaces

1. In the left sidebar, expand Interfaces and select WAN.
2. Click the ellipsis (...) in Actions for the port and click Edit WAN interface.
3. Complete:
   • Type: A name you will recognise.
   • Bandwidth (in Mbps): The speed agreed with the provider (used for traffic shaping).
   • MTU size: The MTU in bytes. See MTU Size.
   • Upstream carrier type: Select Fixed, Mobile, or Starlink.
   • Upstream carrier reference: For example an IMSI or Starlink serial.
   • Managed WAN (optional): Select the Managed WAN that is the upstream for this port, or leave No Managed WAN.
4. Click Save.

Selecting a Managed WAN records which Managed WAN belongs with this WAN port. It does not change how the interface is addressed. Set Upstream carrier type to match the connection — Mobile when that Managed WAN is cellular. See Managed WAN.

Step 3: Connect to a VNET

1. Click Actions, then Connect to VNET. You can also use Connect to VNET on the overview banner or Details card.
2. Select the target virtual network.
3. Assign your SE interfaces to the appropriate WAN interface groups.
4. Click Connect.

Disconnect from a VNET

1. Click Actions.
2. Click Disconnect from VNET.
3. Confirm that you want to unlink the Service Edge from the virtual network.

The SE no longer takes part in that VNET until you connect it again. Loopback addresses taken from that VNET are removed as well, so you can connect again later without an overlap error.

Step 4: Register hardware

After the physical device arrives, link it using the hardware identifier on the device label:

1. Click Actions, then Register hardware. You can also click Register hardware on the Hardware card.
2. Enter the hardware identifier.
3. Click Register hardware.

To unlink hardware later, use Unregister hardware in Actions.