Reference Information
Review what ZNS network resources mean and how they relate to ZStack Cloud service networks.
Core Definitions
| Term | Description |
|---|---|
| ZNS Network Center | Console entry point for managing site networks, gateways, network services, and traffic observation. |
| Site | A management scope in ZNS for organizing compute Clusters and network infrastructure. For a single-site service network, prepare Fabric in its site first. Cross-site connectivity also requires DCI resources and a peering connection between sites. |
| Cluster | A compute Cluster that hosts nodes on the compute platform and can be associated with a site. It is different from the ZNS control plane cluster shown on the Cluster Management page. |
| Fabric Common Configuration | Site-level basic network configuration, including host switches, transport zones, and related uplink settings. Complete the common configuration for each site before connecting hosts. |
| Compute Manager | Connects ZNS to a compute platform so that ZNS can discover hosts, Clusters, and other compute resources. After a compute manager is registered, ZNS can obtain the host resources needed for later network configuration. |
| Host | A compute node that carries service networks. After connecting a host to site Fabric, it can use network parameters from the site common configuration or a host shared configuration. |
| Transport Zone | Defines the range of hosts or nodes across which a network segment can be transported. Common types include VLAN and Overlay. |
| Uplink | A host's uplink to the physical network. When connecting a host, map logical Uplink members in the site configuration to the host's physical NICs. |
| VTEP IP Address Pool | Provides addresses for Overlay network tunnel endpoints (VTEPs). Plan its address range before configuring site Fabric. |
| Host Shared Configuration | A site configuration that multiple hosts can reuse for NIC and uplink mappings and related settings. Create it only when hosts need to share the same configuration. |
| Edge Cluster | A group of edge resources that provides north-south routing and other network services. It can be associated with Tier-0 and Tier-1 gateways. |
| Tier-0 Gateway | A core gateway facing the external network or upstream routing. It provides edge routing and high availability. Tier-1 gateways can reach external networks through a Tier-0 gateway. |
| Tier-1 Gateway | A gateway for tenant or service networks. It can connect upstream to a Tier-0 gateway and provide routing for segments. |
| DCI Gateway | A gateway for interconnecting sites. Before establishing a DCI link, configure a DCI Gateway and its member hosts at both sites. |
| DCI Link | A network resource that connects two sites. A cross-site Tier-1 peering connection requires an available DCI link between the two sites. |
| Tier-1 Peering Connection | Establishes a routing relationship between two Tier-1 gateways. A same-site connection does not require a DCI link. For a cross-site connection, establish a DCI link first. |
| Segment | A ZNS network object that carries a service subnet and can use VLAN or Overlay networking. Creating a Geneve or VPC network in the ZStack Cloud console can generate a corresponding segment in ZNS. |
| NAT Rule | Translates source or destination addresses for traffic on a Tier-0 or Tier-1 gateway. ZNS supports SNAT, DNAT, and Reflexive rules. |
| Load Balancing | Receives TCP or UDP traffic through a VIP on a Tier-1 gateway and forwards it to pool members in a server pool. |
| Virtual Server | The traffic entry point for load balancing. It defines a VIP, port, protocol, Tier-1 gateway, server pool, and optional profile. |
| Server Pool | A group of pool members associated with a Tier-1 gateway. A health monitor can be associated with it as needed. |
| Pool Member | A service endpoint in a server pool that receives traffic. It consists of a segment port IP address and a service port. |
| Health Monitor | Checks pool member availability at a specified interval, timeout, and success or failure threshold. |
| Load Balancing Profile | Defines session persistence criteria and duration for a virtual server. |
| Router QoS Profile | Controls bandwidth and burst capacity for router traffic. |
| Segment QoS Profile | Controls rate limiting for ingress and egress segment traffic. |
| SpoofGuard Profile | A security policy that prevents VM IP/MAC address spoofing. |
| Host Traffic Collection | Provides data for Traffic Overview, Traffic Topology, and VM NIC packet capture. Results depend on the collection interface, filter scope, and time range. |
| Agent | A ZNS agent running on a host. Its connection status and failure reason can be viewed in the host details for a site. |
| SDN Controller | A setting in the ZStack Cloud console for connecting to ZNS. It determines how ZStack Cloud networks relate to ZNS compute managers, gateways, segments, and other resources. |
Relationship with ZStack Cloud Resources
Responsibilities
In ZNS Network Center, ZNS administrators configure and check the status of sites, Fabric, gateways, peering connections, network services, and policies. In the ZStack Cloud console, ZStack Cloud administrators create and use service networks and VMs.
When ZStack Cloud networks use ZNS resources, ZNS administrators can check compute managers, sites, Tier-1 gateways, segments, network policies, and other resources in ZNS Network Center. ZNS administrators configure cross-site Tier-1 peering connections in ZNS.
Resource Relationships
| Resource | What to Check in ZNS | Relationship |
|---|---|---|
| Compute Manager | Confirm that the compute platform is registered, its connection status is Connected, and its configuration status is Deployed. | The ZStack Cloud console connects to ZNS through an SDN Controller. |
| Site and Fabric | Check compute Cluster associations, the VTEP IP address pool, site Fabric configuration, and host connection status. | ZNS assigns compute-side Clusters to sites. Prepare the underlying network for each site before using service networks. |
| Tier-1 Gateway | Provides upstream connectivity and routing for service networks. Create gateways according to service domain or tenant plans. | When creating a ZNS network in the ZStack Cloud console, select or associate the planned Tier-1 gateway. |
| DCI Link and Tier-1 Peering Connection | Check the DCI Gateway at each site, the DCI link, the gateway sites, connection status, and connectivity mode. | Cross-site service networks require explicit configuration of a ZNS DCI link and a peering connection between the two Tier-1 gateways. |
| Segment | Check the segment name, configuration status, traffic type, VNI/VLAN ID, associated gateway, and address information. | Creating a Geneve or VPC network in the ZStack Cloud console might generate a corresponding segment in ZNS. |
| QoS and SpoofGuard Profiles | Create profiles according to service performance and security requirements, and maintain their status. | After a service network or gateway uses a profile, check the associated profile status in ZNS. |
Multiple ZStack Cloud Environments
When multiple ZStack Cloud environments connect to the same ZNS deployment, first determine the site for each compute Cluster. Then plan Tier-1 gateways and segments according to service isolation and connectivity requirements. For cross-site connectivity, prepare a DCI Gateway at each site in ZNS, establish a DCI link, and create a peering connection between the Tier-1 gateways.
Note: DCI links and peering connections do not replace service network configuration in ZStack Cloud. Confirm that the service subnets at both sites do not overlap, routing and upstream networks are correct, and connectivity is verified from the service networks.