K-Nets Quick Tasks

Use this page for fast network actions. For full context, use K-Nets (Full Guide).

Note

Paths below lead with the K-Nets module on the left icon rail. The same pages are also reachable from Control Center -> Network, which is the path non-root tenant accounts use - K-Nets is hidden from them.

Task 1: Decide if You Need Changes

When to Use:

Use this before creating or editing any network object.

Purpose:

Confirm whether an existing guest network already meets workload needs.

Steps:

  1. Open K-Nets -> Guest Network.

  2. Confirm at least one target guest network exists.

  3. Check network state and IP capacity for your target workload.

  4. Continue without changes if an existing network is already usable.

Expected Outcome:

  • You decide correctly whether to reuse an existing network or create new network resources.

If this fails:

  1. Refresh the Guest Network page and re-check state/capacity.

  2. Verify you are in the correct environment/zone context.

  3. Continue with Task 2 when no suitable network is available.

Task 2: Create a Basic Guest Network

When to Use:

Use this when no suitable guest network exists for the workload.

Purpose:

Create an isolated or shared guest network and make it available for VM provisioning.

Steps:

  1. Open K-Nets -> Guest Network.

  2. Click + Add Guest Network.

  3. Select Isolated, Shared, or L2. Isolated and L2 then ask you to choose VLAN or VXLAN encapsulation on the VLAN / VXLAN control.

  4. If Isolated, fill required fields: Zone, Network Name, Network Offering, Gateway, Netmask, and VLAN or VXLAN (VNI) (the VNI is hidden when an Auto-VNI offering is selected).

  5. If Shared, fill required fields including VLAN, Gateway, Netmask, Start IP, and End IP.

  6. If Isolated + VLAN, or Shared: the primary button reads Next. Click it and complete the NIC assignment step, then click Create Network. If Isolated + VXLAN, or L2 (either encapsulation): there is no second step and the button already reads Create Network.

  7. Verify the network appears in the table with a usable state.

Note

Creation is asynchronous. The API accepts the request and returns a job; a progress panel tracks bridge, network, and virtual-router provisioning live. Wait for it to finish (or to report a rollback) before assuming the network is ready.

Expected Outcome:

  • A new guest network is listed with the expected type and state.

  • VM provisioning can target the new network.

If this fails:

  1. Confirm required fields are complete and values are valid.

  2. Verify subnet/gateway/VLAN values do not overlap existing ranges.

  3. Retry from the create form after refreshing the page.

Task 3: Add Management, Storage, or Public IP Capacity

When to Use:

Use this when network operations fail because IP ranges are exhausted.

Purpose:

Expand available addressing capacity under the correct traffic type.

Steps:

  1. Open K-Nets -> Physical Network.

  2. Open the target physical network and go to Traffic Types.

  3. Open Management, Storage, or Public based on capacity need.

  4. Click + Add ... IP Range and add a new range.

  5. Save and re-check available capacity.

Note

Existing ranges cannot be resized. Management and Storage ranges can only be added - they have no edit or delete control in the UI, so to change coverage you add a second range. Public ranges can additionally be edited (gateway, netmask, start IP, end IP) and deleted. All of these actions require the NETWORK_MANAGE permission; without it the buttons and row icons are not rendered at all.

Expected Outcome:

  • New range is visible in the selected traffic type.

  • Related create/provision actions no longer fail due to capacity.

If this fails:

  1. Verify gateway, netmask, start IP, and end IP are in the same subnet.

  2. Confirm the range does not overlap existing ranges.

  3. Confirm your account holds NETWORK_MANAGE; if the + Add ... IP Range button is missing entirely, that permission is the reason.

Task 4: Fast Triage for VM Has No IP

When to Use:

Use this when a VM is running but has no expected network connectivity or IP assignment.

Purpose:

Quickly isolate whether the issue is guest network state, IP capacity, or service dependency.

Steps:

  1. Confirm guest network state and IP range availability.

  2. Confirm isolated-network service dependencies are healthy (when using isolated networks).

  3. Validate VM-side network configuration from VM console.

  4. Correlate findings with Observability.

Expected Outcome:

  • You identify the most likely failure layer and next remediation path.

If this fails:

  1. Repeat checks once after a controlled refresh.

  2. Capture guest network state, VM identity, and alert evidence.

  3. Escalate when state remains stuck or recurring alerts continue.

→ Next: Storage