Edge networks

In zCompute, Edge Networks provide the connectivity between VPC entities (e.g VMs, load-balancers) and the Internet or any other local datacenter-routable network. Under an Edge Network one or more IP-address pools can be defined. These IP pools are then used to create Elastic-IPs, that when attached to a VM, allow traffic from outside the cloud (Internet or the hosting datacenter to reach the VM. A single zCompute region may have multiple Edge Networks, each with multiple IP pools. IP pools can be public, available for all tenant accounts, or private to specific accounts. Edge Networks use VLANs to connect the cloud region to the hosting datacenter’s upstream switches and L3 gateways.

Viewing edge networks

Use the edge networks list view to find a network, review its state, and open the details page.

  1. Go to Region Networking > Edge Networks.

    The edge networks are displayed.

    The list view shows these columns:

    • Name

      The descriptive display name of the edge network.

      This is the main identifier used in list views and action dialogs. It is also the link that opens the details page.

    • Subnets

      The subnet CIDR values that are attached to the edge network.

      This field shows the network address range or ranges already assigned to the edge network.

    • Gateway

      The gateway IP address for the edge subnet.

      This address is the routed exit point for systems on the subnet.

    • VLAN

      The VLAN value for the edge network.

      This is the layer 2 tag used by the network. If the network is untagged, the UI can show an untagged value.

    • MTU

      The maximum transmission unit for the edge network.

      This value controls the largest packet size allowed on the network path.

    • Account

      The account associated with the edge network.

      This field helps an admin identify the owning account when the column is visible.

    • Project

      The project associated with the edge network.

      This field helps an admin identify the linked project when the column is visible.

    • Switch Domain

      The switch domain associated with the edge network.

      This is the switching domain that contains the edge network.

    • State

      The current lifecycle state of the edge network.

      This field helps the admin decide whether change actions are available.

      • The UI only enables Edit when the state is Available.

      • The UI disables Delete when the state is Pending.

    • ID

      The unique identifier of the edge network.

      Use this value when names are similar or when you must confirm the exact object in a prompt or a ticket.

  2. Select the edge network name to open its details page.

Viewing an edge network’s details

Use the details page to review the full configuration of one edge network.

Edge network main details

  1. Go to Region Networking > Edge Networks.

    The edge networks are displayed.

  2. In the edge networks list, select the edge network name.

    The top toolbar can show these controls:

    • Edit

    Opens the edge network edit flow.

    Use this control to update the editable edge network and subnet fields.

    • Services Proxy

    Opens the managed services proxy dialog.

    Use this control to store HTTP and HTTPS proxy settings for managed services.

    • Delete

    Opens the edge network delete confirmation prompt.

    Use this control to remove the edge network after you review dependencies.

    The details page displays the selected edge network’s details.

    • Info section:

      • Name

        The descriptive display name of the edge network.

      • ID

        The unique identifier of the edge network.

      • Description

        Brief description of the edge network.

    • IP Pools section:

      Each row in this block represents one non-internal IP pool.

      This means the block is meant to summarize allocatable pools that the admin can review at a glance, rather than internal-only pools.

      • Pool name

        The first column of each row is the IP pool name.

        This is the main label that identifies the pool in the summary block. It lets the admin match the summary row to the same pool in the IP Pools tab.

      • Allocation bar

        The value shown for each row is an allocation bar.

        It is a visual capacity summary for the pool indicating allocated and unallocated proportions. It can help admins estimate pool consumption without opening the full IP Pools tab.

    • Subnets

      Each row in this block represents one subnet from the edge network.

      This means that this section is a summary of the subnets already attached to the edge network. It helps admins confirm the current subnet layout before opening the Overview tab to see the subnets and their details.

      • CIDR

        The first column of each row is the subnet CIDR block.

        This is the subnet address range in CIDR notation. It defines the IP space of that subnet and gives the admin a quick view of the network range in use.

      • Gateway

        The value shown for each row is the gateway IP of that subnet.

        This is the routed exit point for systems on the subnet. It helps admins confirm the main layer 3 value for the subnet without opening the detailed subnet record.

    • Internal Resources section:

      The block summarizes the router-side internal resources that support the edge network.

      • Edge Router Public IP

        The public IP of the edge router.

        This is the external IP address assigned to the router. It helps admins identify the router’s public-facing address quickly, without opening the Overview tab.

      • Routers Subnet

        The CIDR block of the routers subnet, when that subnet exists.

        This is the subnet used for router-facing connectivity. It helps admins confirm the internal routed subnet that supports the edge router path.

      • Routers IP Pool

        Shows an allocation bar for the routers IP pool, when that pool exists.

        This is a capacity summary for the internal routers IP pool. It helps admins review router-related address consumption at a glance.

Overview tab

The Overview tab shows the main configuration record for the selected edge network.

It provides the best single-page view of the network, subnets, proxy, router, and routers subnet records.

Network section

  • Network ID

    The unique identifier of the edge network.

    Use it to confirm that you are working on the correct network object.

  • Name

    The edge network name and description.

    This is the main human-readable label for the network. It is used across lists, tabs, and prompts.

  • Shared

    The sharing state of the edge network.

    This shows whether the network is shared. It helps an MSP admin understand the intended scope of use.

  • VLAN

    The VLAN value of the edge network.

    This is the layer 2 tag used by the network. It affects the network’s underlay connectivity model.

  • Switch Domain

    The switch domain that contains the edge network.

    This identifies the switching domain that the network belongs to.

  • MTU

    The maximum transmission unit of the edge network.

    This controls the largest packet size allowed on the network path.

  • Account

    The account associated with the edge network.

    This field is useful for MSP review when account-level ownership matters.

  • Project

    The project associated with the edge network.

    This field helps identify the linked project context.

Subnets section

  • Subnet ID

    The unique identifier of the subnet record.

    Use it to confirm the exact subnet object attached to the edge network.

  • Name

    The subnet name.

    This is the human-readable label of the subnet. The UI can show no name when no value is set.

  • CIDR

    The subnet address range in CIDR notation.

    This defines the IP space available on the subnet.

  • Gateway

    The gateway IP address of the subnet.

    Systems on the subnet use this address to reach other networks.

  • DNS Servers

    The DNS server IP addresses assigned to the subnet.

    Systems use these addresses for name resolution.

Managed Services Proxy section

This section appears when proxy data exists for the edge network.

  • HTTP proxy

    The saved HTTP proxy value for the edge network.

    It identifies the proxy endpoint used for HTTP traffic.

  • HTTPS proxy

    The saved HTTPS proxy value for the edge network.

    It identifies the proxy endpoint used for HTTPS traffic.

  • Exclusion list

    The saved bypass list for proxy handling.

    It shows the destinations that should not use the proxy.

Edge Router section

  • Router ID

    The unique identifier of the edge router.

    Use it to confirm the exact router object.

  • Name

    The edge router name.

    This is the router label shown in the UI.

  • Internal Interfaces

    The internal router interface address or addresses.

    These values show the router-side addresses used on internal connectivity paths.

  • Public IP

    The public IP assigned to the edge router.

    Use it to identify the external address used by the router.

Routers Subnet section

  • Subnet ID

    The unique identifier of the routers subnet.

    Use it to confirm the exact routers subnet record.

  • Name

    The routers subnet name.

    This is the human-readable label of the routers subnet. The UI can show no name when no value is set.

  • CIDR

    The routers subnet address range in CIDR notation.

    This defines the address space used by router-facing interfaces.

  • Gateway

    The gateway IP address of the routers subnet.

    Use it to confirm the routed path on that subnet.

Events tab

The Events tab shows activity related to the selected edge network.

The screenshots show filter controls in this tab.

  • Date range

    The time filter for the event list.

    Use it to narrow the visible events to a specific time window.

  • Filter

    The text filter for the event list.

    Use it to find a specific event more quickly.

  • More filters

    Additional event filters.

    Use them when the basic filters are not enough to narrow the event list.

IP Pools tab

The IP Pools tab shows the IP pools that belong to the edge network.

The list shows these fields:

  • Name

    The display name of the IP pool.

    Use it to identify the pool in list views and confirmation prompts.

  • Usage

    The current used and total address count in the pool.

    Use it to estimate remaining capacity.

  • IP Ranges

    The start and end IP ranges assigned to the pool.

    These are the addresses that the pool can allocate.

  • Assigned Accounts

    The assignment or sharing state of the pool.

    This helps the admin see whether the pool is shared or linked to specific accounts.

  • Type

    The pool type.

    The screenshots show types such as VPC, Legacy, and Routers.

IP Pools tab actions

The IP Pools tab has its own toolbar menu of widgets, for creating a new IP pool, and modifying or deleting an existing IP pool.

Creating an IP pool

Use this action when the edge network needs a new address pool.

  1. Go to Region Networking > Edge Networks.

    The edge networks are displayed.

  2. In the edge networks list, select the edge network name.

    The selected edge network’s details page displays.

  3. Select the IP Pools tab.

  4. From the tab’s toolbar, select + Create.

    The Create IP Pool dialog opens.

  5. In the Create IP Pool dialog, enter the fields:

    • Name

      The descriptive display name for the IP pool.

      Use a name that helps admins identify the pool in list views and prompts.

    • Description

      A short text description of the IP pool.

      Use it to explain the purpose of the pool.

    • Shared

      The sharing state of the IP pool.

      Use it to mark the pool as shared when that matches the intended access model.

    • IP Ranges

      One or more start and end IP values.

      These values define the addresses that belong to the pool.

    • Accounts

      From the dropdown, select one or more accounts that will have use of the IP pool.

  6. To save the new IP pool, select Create.

Modify an IP pool

Use this action when an editable IP pool setting must change.

  1. Go to Region Networking > Edge Networks.

    The edge networks are displayed.

  2. In the edge networks list, select the edge network name.

    The selected edge network’s details page displays.

  3. Open the IP Pools tab.

  4. Select the IP pool.

  5. Select Modify.

    The Modify IP Pool dialog opens.

  6. In the Modify IP Pool dialog, the following fields can be updated:

    • Name

      The display name of the IP pool.

      It is recommended to change it only when the new name improves clarity.

    • Description

      The description of the IP pool.

      Change it when the pool purpose or operational notes need an update.

    • Shared

      The sharing state of the IP pool.

      Caution

      Review this carefully because it affects how the pool is intended to be used.

    • IP Ranges

      The start and end IP values in the pool.

      Caution

      Change IP ranges only after you confirm the target address plan.

  7. To save the changes to the IP pool, select Modify.

Delete an IP pool

Caution

Use this action only after you confirm that the pool is no longer needed.

  1. Go to Region Networking > Edge Networks.

    The edge networks are displayed.

  2. In the edge networks list, select the edge network name.

    The selected edge network’s details page displays.

  3. Open the IP Pools tab.

  4. Select the IP pool to delete.

  5. Select Delete.

    The Delete IP Pool dialog opens, displaying the name and ID of the selected IP pool.

    Review the prompt: Are you sure you want to delete this IP pool? and the IP pool’s name and ID, before progressing.

  6. To confirm deletion of the IP pool, select Delete.

VPC Projects tab

The VPC Projects tab shows which VPC projects use the edge network.

Note

  • Review this tab before IP pool changes.

    It helps you estimate the effect of a pool change on dependent projects.

  • Review this tab before deleting an edge network.

    It helps you see whether active projects still depend on the edge network.

The list displays these fields:

  • Name

    The VPC project name.

    This is the project label shown in the list and used to identify the dependent project.

  • IP Pool

    The linked IP pool name.

    This shows which IP pool the VPC project is using on the edge network.

  • Account

    The owning account of the VPC project.

    Use it to identify the tenant or account that owns the project.

Elastic IPs tab

The Elastic IPs tab shows the Elastic IP records that are associated with VPC projects that use this edge network as their default edge network.

The edge-network view gets these records by collecting the VPC projects linked to the edge network and then filtering Elastic IPs by those project IDs.

The list displays these fields:

  • Elastic IP

    The public Elastic IP address.

    This is the main public address assigned to the Elastic IP record. The table also shows an internal-resource tooltip next to this value.

  • Private IP

    The private IP address currently associated with the Elastic IP.

    This value shows the internal address that the public address maps to. If a network interface is known, the table also shows a link to that interface and its name.

  • Instance

    The attached VM instance.

    When an instance is associated, this field links to the VM and shows the instance name. This helps identify the workload that currently uses the Elastic IP.

  • VPC

    The VPC that owns the Elastic IP record.

    This field links to the VPC and shows its name. It helps the admin see which VPC context the Elastic IP belongs

  • Public DNS

    The public DNS name for the Elastic IP.

    This field shows the public DNS value when one exists.

  • Non-defult display columns

    The following columns are not displayed by default, but can optionally be selected for display using the column filter selection.

    • ID

      The unique Elastic IP identifier.

      This field helps distinguish records when IP values are similar or when exact confirmation is needed.

    • Subnet

      The subnet linked to the Elastic IP record.

    • Tags

      The tag list assigned to the Elastic IP.

Creating an edge network

Use this action when you need a new edge network.

Note

  • The create flow has two steps: Network and Subnets.

    This keeps network properties separate from subnet addressing.

  • Plan switch domain, VLAN, and MTU values before you create the network.

    Some of these fields are not editable later.

  1. Go to Region Networking > Edge Networks.

  2. Select + Create.

    The Create Edge Network dialog opens.

  3. In the Network step, enter the displayed fields:

    • Name

      The edge network name.

      This is the main display label used in list views, details pages, and prompts.

    • Description

      The short description of the edge network.

      Use it to explain the purpose of the network.

    • Switch Domain

      The switch domain for the edge network.

      This places the network in a specific switching domain.

    • Shared

      The sharing state of the edge network.

    • VLAN ID

      The VLAN value of the edge network.

      This is the layer 2 tag used by the network when the network is tagged.

    • Untagged

      The untagged option for the edge network.

      Use it when the network must not use a VLAN tag.

    • MTU

      The maximum transmission unit of the edge network.

      This controls the largest allowed packet size on the network path.

    • Public IP

      The public IP for the edge router.

      Use it when you need to set a specific router public address. If you leave it empty, the form states that a random available IP address is allocated from the IP pool.

  4. Select Next to progress to the Subnets step.

  5. In the Subnets step, enter the displayed subnet fields:

    • Subnet (CIDR)

      The subnet address range in CIDR notation.

      This defines the IP space available on the edge subnet.

    • Gateway

      The gateway IP address of the subnet.

      Systems on the subnet use this address to reach other networks.

    • DNS Servers

      The DNS server IP addresses for the subnet.

      Systems use these addresses for name resolution.

  6. To save the new edge network’s configuration, select Finish.

Modifying an edge network

Use this action when you need to update the editable edge network settings.

Note

  • The UI enables Edit only when the edge network state is Available.

    Review the current state before you plan the change.

  • Expect some fields to be visible but not editable.

    The system disables switch domain, VLAN, and untagged values in edit mode.

  1. Open the edge network details page.

  2. Select Edit.

    The Modify Edge Network dialog opens.

  3. In Network step, review and update the displayed fields:

    • Name

      The edge network name.

      Change it when the current name no longer describes the network clearly.

    • Description

      The short description of the edge network.

      Change it when the purpose or operational note needs an update.

    • Switch Domain

      The switch domain of the edge network.

    • Shared

      The sharing state of the edge network.

    • VLAN ID

      The VLAN value of the edge network.

    • Untagged

      The untagged option of the edge network.

    • MTU

      The maximum transmission unit of the edge network.

    • Public IP

      The public IP of the edge router.

  4. Select Next to progress to the Subnets step.

  5. In the Subnets step, review and update the displayed subnet fields:

    • Subnet (CIDR)

      The subnet address range in CIDR notation.

    • Gateway

      The gateway IP address of the subnet.

      The system checks whether the IP matches the subnet CIDR and excludes boundary addresses.

    • DNS Servers

      The DNS server IP addresses for the subnet.

  6. To save the changes, select Finish.

Configuring a services proxy

There may be several reasons for configuring a services proxy, including:

  • To force managed-services traffic through a controlled egress path.

  • To use a proxy that requires authentication.

  • To let some destinations bypass the proxy, by defining an exclusion list

Use this action when managed services for the edge network must use a proxy.

Note

  • Keep the exclusion list focused.

    A smaller bypass list is easier to review and support.

  • Review the Overview tab after saving proxy values.

    The tab shows the stored HTTP proxy, HTTPS proxy, and exclusion list when proxy data exists.

  1. Open the edge network details page.

  2. Select Services Proxy.

    The Configure Managed Services Proxy dialog opens.

  3. Enter the fields:

    • HTTP Domain

      The HTTP proxy host or IP value.

      Use it to define the proxy endpoint for HTTP traffic.

    • Port

      The HTTP proxy port.

      Use it with the HTTP domain to define the full HTTP proxy endpoint.

    • Username

      The HTTP proxy user name.

      Use it when the proxy requires authentication.

    • Password

      The HTTP proxy password.

      Use it with the user name when the proxy requires authentication.

    • HTTPS Domain

      The HTTPS proxy host or IP value.

      Use it to define the proxy endpoint for HTTPS traffic.

    • Port

      The HTTPS proxy port.

      Use it with the HTTPS domain to define the full HTTPS proxy endpoint.

    • Username

      The HTTPS proxy user name.

      Use it when the HTTPS proxy requires authentication.

    • Password

      The HTTPS proxy password.

      Use it with the user name when the HTTPS proxy requires authentication.

    • Exclusion list

      The proxy bypass list.

      Use it to enter destinations that must bypass the proxy. The dialog hint says the values are domain suffixes that bypass the proxy and must start with a period.

  4. To save the service proxy configuration, select Ok.

Deleting an edge network

Use this action only after you confirm that the edge network is no longer needed.

Note

  • The UI disables Delete when the edge network state is Pending.

    Review the state before you plan the delete action.

  • Review the VPC Projects and IP Pools tabs first.

    This helps you understand dependency and usage before removal.

  1. Open the edge network details page.

  2. Select Delete.

    The Delete Network dialog opens, displaying the edge network’s name and ID.

  3. Review the prompt:

    • Are you sure you want to delete this edge network?

      The confirmation prompt warns that the selected edge network will be removed.

      Use it as the final review step before deletion.

    • ID

      The unique edge network ID shown in the prompt.

      Use it to confirm the exact object to delete.

    • Name

      The edge network name shown in the prompt.

      Use it to confirm that the selected object is the correct one.

  4. To delete the edge network, select Delete.

  • Plan Switch Domain, VLAN ID, and Untagged values before you create the edge network.

    The create/edit form allows these values at creation time, but the edit form disables Switch Domain, VLAN ID, and Untagged. That makes them design-time choices, not routine change-time values.

  • Use the default MTU unless you have a clear reason to change it, and keep MTU changes controlled.

    The form always requires MTU and defaults it from the edge-network default. The input validation check also enforces minimum and maximum MTU values, which indicates that MTU is a core network setting that should be chosen carefully.

  • Treat subnet CIDR as stable after creation.

    In the Subnet step, the CIDR field is disabled for editing once the subnet record already exists. That means you should choose the subnet range carefully before production use.

  • Validate Gateway carefully against the subnet.

    The input validation checks the gateway IP against the subnet CIDR and excludes boundary addresses. A practical best practice is to review the subnet and gateway together before saving changes.

  • Enter only valid IP addresses in DNS Servers, and keep the list intentional.

    The DNS Servers field accepts multiple values and validates them as IPs. That makes it a good place to keep only the resolvers that are actually required for that subnet.

  • Use the edge network state as your first pre-change check.

    The UI enables Edit only when the edge network state is Available.

    It disables Delete when the state is Pending.

    Before any maintenance, verify that the network is in the right state.

  • Keep Public IP assignment deliberate.

    If no public IP is provided in the Network step, a random available IP is allocated from the IP pool. Use an explicit value when you need predictable router addressing, and leave it empty only when automatic assignment is acceptable.

  • Use the Services Proxy only when managed services actually need a proxy path, and keep the bypass list tight.

    The action stores proxy settings on the edge network, and the UI is specifically for managed-services proxy configuration. Because the Services Proxy dialog includes HTTP/HTTPS endpoints and an exclusion list, it is best to keep the configuration minimal and reviewable.

  • Review free address space before creating an IP pool.

    The IP pool dialog fetches unused ranges for the edge network and only presents IP-range entry when there is an existing pool to modify or unused ranges to consume.

    Check available space before adding more pools.

  • Use Shared IP pools only when that access model is intentional; otherwise assign accounts explicitly.

    In the IP pool dialog, when Shared is not selected, Accounts becomes required. That implies a clear operational split between shared pools and account-scoped pools.

  • Do not plan routine changes to the routers IP pool.

    The IP pool actions disable Modify and Delete for internal pools, with the message Routers IP Pool is managed internally. Treat router pools as platform-managed resources.

  • Use the built-in two-step workflow as your change checklist: Network first, then Subnets.

    The dialog explicitly separates these into two steps. In practice, this is a good admin habit as well: review network-wide properties first, then validate subnet addressing.

  • Before deleting an edge network, confirm both identity and state.

    The delete prompt shows the network ID and Name, and the UI disables delete while the network state is Pending. That means the safest delete workflow is: verify state, then verify exact identity in the confirmation prompt.

Troubleshooting

The edge network is not editable

Check the edge network state first.

The UI enables Edit only when the state is Available.

A field is visible but cannot be changed

This can be expected behavior.

Switch Domain, VLAN ID, and Untagged are disabled in edit mode. The subnet CIDR field is also disabled when the subnet record already exists.

A gateway value is rejected

Review the subnet CIDR first.

The system validates the gateway value against the subnet CIDR and excludes boundary addresses.

A DNS server value is rejected

Review the entered value format.

The system validates the DNS Servers field as IP values.

You are not sure whether a delete action is safe

On the edge network’s details page, review these tabs first:

  • Overview

    Review the exact network, subnet, router, and routers subnet records.

  • IP Pools

    Review current pool usage and ranges.

  • VPC Projects

    Review dependent project usage.

  • Events

    Review recent activity after the latest change.