Virtual Network
The Virtual Network (VNET) is the foundational building block of the Wanscale Platform. It serves as the central intelligence hub for your environment, performing several critical functions:
- Routing Management: Maintains the Routing Information Base (RIB).
- Cloud Integration: Manages BGP sessions to external services such as Azure or AWS.
- Static Routing: Handles static routes for services like LAN locations behind a Service Edge.
- SD-WAN Control: Manages WAN Interface Groups used for Path Selection on Service Edges.
- Policy Enforcement: Centralizes management for:
Tip
You can have multiple VNETs per tenant
Overview and health
Open the Virtual Network from Services. The overview brings together status, setup warnings, linked services, active alarms, bandwidth, and service locations.
- Follow a warning's Fix action to complete missing configuration.
- Open a linked service to inspect its health and settings. Use the overview's management actions and current sidebar to manage services.
- Review the active-alarm list and open an affected service to investigate.
- Compare bandwidth by service type. Types without measurements are omitted; the chart is hidden when no telemetry is available.
- Select a location marker to inspect the Service Edges there.
Note
Bandwidth adds traffic measured on member services. The same traffic can be counted at several hops, so the total is not unique traffic through the Virtual Network.
Explore topology
- Open General → Topology in the Virtual Network sidebar.
- Review the gateway pairs and their connected services, grouped by gateway type.
- Compare A · Primary and B · Primary to see which gateway is primary for each service group.
- Expand and … more to inspect a larger Service Edge group.
- Select a service, gateway, group, or the Virtual Network to focus its relationships. The details area identifies related services and the primary and secondary connections.
- Use a service's link to open its overview. Clear the focus to return to the whole network.
Topology shows connectivity and placement. It does not measure gateway load or traffic utilisation. If the network has no gateway groups or services yet, the page shows an empty state.
VNET Requirements
Before creating a VNET, ensure you have an appropriate IPv4 Address Space available. This space is used by the platform to facilitate internal connectivity between services.
Warning
This Address Space cannot overlap with IP addresses or prefixes you use elsewhere in your network. It must be unique in the VNET RIB
Creating a VNET
Follow these steps to deploy a new Virtual Network:
- Navigate to the Services page of the Wanscale Platform.
- Click the Add Service button.
- Select Virtual Network from the service list.
- Click Go to service form.
- Complete the following fields in the service form:
- Label: Enter a descriptive name for the VNET.
- Tags (Optional): Add metadata for easier filtering.
- Zone: Select the Geographic Zone where the VNET resources will be provisioned.
- Address Space: Enter a unique IPv4 prefix for your RIB.
- Click Submit
Tip
Sizing Recommendation: We suggest using an RFC1918 or CGNAT prefix no smaller than a /22.
- Each service attached to the VNET can consume up to four
/30prefixes. -
A
/22supports approximately 64 services, while a/16supports 4,096. -
Note: This prefix cannot be changed after the VNET is created.
Note
Applying Changes: Like all networking services in Control Center, your new VNET will not be active until you deploy the changes. See Workflows and Applying Changes.