1. Log in to ZCF.
2. In the upper-right corner, switch to Global Management.
3. In the top navigation bar, click ZNS Network Center.
4. Select the target page in the left navigation pane.

   The left navigation pane contains Fabric Overview, Cluster Management, Quick Start, Hosts, Edge Clusters, Profiles, Transport Zones, Compute Managers, Settings, IP Address Pool, Tier-0 Gateway, Tier-1 Gateway, Segments, NAT, Layer 4 Load Balancing, Router QoS Profile, Segment QoS Profile, and SpoofGuard Profile.

1. Navigate to ZNS Network Center.
2. In the left navigation pane, click Fabric Overview.
3. View Fabric resource counts.

   The resource count area displays the number of Compute Managers, Hosts, Edge Clusters, and Transport Zones. Click a resource card to open the corresponding resource details page.

4. View Resource Summary.

   The Resource Summary section displays the number of data-plane resources, such as transport node profiles, host switch profiles, uplink profiles, edge cluster profiles, and uplinks.

5. To get the latest data, click Refresh.

1. Navigate to ZNS Network Center.
2. In the left navigation pane, click Cluster Management.
3. View the cluster summary.

   The page displays cluster health state, the number of online nodes, VIP address and VIP holder, primary database node, and OVN Northd state.

4. View the cluster node list.

   Node cards display node name, IP address, health state, role, version, uptime, API port, collection time, and component state.

5. Click View Details for the target node.

   Node details show basic information, running state, and software version. Running state includes information about zstack-zns, Controller Manager, etcd, Patroni, PostgreSQL, OVN Northd, OVN Northbound, OVN Southbound, Keepalived, work queue, and event queue.

6. View control plane service status.

   The control plane service area displays the health state of the database, OVN, and controllers, including the primary node, replica count, replication delay, OVN Raft Leader node, work queue, and event queue.

7. To get the latest data, click Refresh.

The Quick Start page initializes base ZNS resources through a step-by-step wizard. The workflow registers or reuses a compute manager and creates resources such as transport zones, uplinks, IP address pools, profiles, edge clusters, Tier-0 gateways, and Tier-1 gateways.

Note: Quick Start creates or reuses multiple types of ZNS resources. Before you run it, confirm that the compute manager, host NICs, IP address pools, LAG mode, VLAN, and gateway plan are ready.

Note: If a Quick Start task has been started, is running, or has completed, the system automatically returns to the Quick Start status page when you open the Quick Start configuration page. Check the current task progress and step results on the status page first.

1. Navigate to ZNS Network Center.
2. In the left navigation pane, click Quick Start.
3. Confirm or enter compute manager information.

   A compute manager connects to the compute platform. After ZNS is installed from the marketplace, the current ZStack Cloud environment is usually registered automatically as a compute manager. To connect to another compute platform, enter the compute manager information according to the site plan.

4. Confirm the transport zone and IP address pool plan.

   Transport zones usually include VLAN and Overlay types. IP address pools must be consistent with the address plan for host TEPs, gateways, or other network resources.

   The IP address pool CIDR must be a valid IPv4 CIDR, for example 172.31.10.0/24. An empty Overlay VLAN means that no value is specified. If you enter a value, it must be an integer from 0 to 4094.

5. Configure uplinks and host NIC mappings.

   Uplinks map logical uplinks to physical NICs on each host. When you select NICs, use the physical NICs planned for the ZNS data plane. Do not select management NICs or NICs that already carry other service traffic.

   You must select NICs for each selected host. If you select two uplinks, the two uplinks on the same host cannot reuse the same NIC.

6. Configure edge cluster, Tier-0 gateway, and Tier-1 gateway information.
7. Check all parameters before you submit the task.

   Confirm that resource names, IP address pools, LAG mode, host NIC mappings, edge hosts, Tier-0 gateway, and Tier-1 gateway match the plan before you run Quick Start.

   When you submit the task, the system runs Quick Start validation first. The Quick Start task starts only after the validation passes.

8. After execution is complete, return to the Quick Start page to view execution status and step results.

   Step results display the execution state for registering the compute manager, creating transport zones, creating uplinks and host switches, creating the edge cluster, creating the Tier-0 gateway, and creating the Tier-1 gateway. Resources might be shown as created, reused, or skipped.

1. Go to ZNS Network Center > Compute Managers.
2. View existing compute managers.

   The list displays Name, Type, FQDN / IP, Version, Connection Status, Configuration State, and Created At.

3. Confirm that the target compute manager Connection Status is Connected and Configuration State is Deployed.
4. To add a compute manager, click Register Compute Manager.
5. Enter compute manager parameters.

   The form fields include Name, Description, Type, FQDN / IP, Username, and Password.

   FQDN / IP must be the compute platform API address that includes the http or https protocol, for example http://192.0.2.10:8080.

   Name is required and cannot contain spaces. Username and Password are required, must be 255 characters or fewer, and cannot contain spaces.

6. After you confirm that the parameters are correct, click OK.

1. Go to ZNS Network Center > Settings.
2. View BFD settings.

   BFD settings include BFD Minimum Receive Interval (ms), BFD Minimum Transmit Interval (ms), and BFD Probe Multiplier (times).

   BFD Minimum Receive Interval (ms) and BFD Minimum Transmit Interval (ms) must be greater than or equal to 0. BFD Probe Multiplier (times) must be an integer greater than or equal to 0.

3. View tunnel settings.

   Tunnel settings include Tunnel MTU (bytes). Tunnel MTU must be an integer and cannot be less than 1280.

4. To adjust global settings, click Edit, modify the parameters, and click OK.
   Note: Modify global settings only when the site network plan or troubleshooting procedure explicitly requires the change.
5. Go to ZNS Network Center > Transport Zones.
6. Confirm that VLAN and Overlay transport zones exist.

   The transport zone list displays Name, Traffic Type, and Created At.

1. Go to ZNS Network Center > IP Address Pool.
2. Click Create IP Address Pool.
3. Enter Name.
4. Enter CIDR.

   CIDR is required and must be in IPv4 CIDR format, for example 192.168.1.0/24. Enter an address range that can be used by the ZNS data plane or related network resources according to the site network plan.

5. After you confirm that the parameters are correct, click OK.

1. Go to ZNS Network Center > Hosts.
2. Click the Uplinks tab.
3. Click Create Uplink.
4. On the host selection page, select the hosts for which you want to configure uplinks.

   The host list displays Name, Management IP, Hostname, Status, Configuration State, Provision State, and Created At.

5. Enter the uplink name, description, and host NIC mappings.

   Host NIC mappings map each host physical NIC to a logical uplink. Use the physical NICs planned for the ZNS data plane.

   Note: Do not select management NICs or physical NICs that already carry other service traffic.
6. After you confirm that the mappings are correct, click OK.

1. Go to ZNS Network Center > Profiles.
2. Create an uplink profile.

   Click the Uplink Profiles tab, and then click Create Uplink Profile. The form fields include Name, Description, MTU, LAG Mode, LAG Members, Overlay VLAN, and Transport VLAN.

   LAG Mode and LAG Members must match the link aggregation configuration on the physical switch.

   An empty MTU means that no value is specified. If you enter a value, it must be an integer from 1 to 9216. LAG Members must be an integer from 1 to 16. Empty Overlay VLAN and Transport VLAN values mean that no value is specified. If you enter a value, it must be an integer from 0 to 4094.

3. Create a host switch profile.

   Click the Host Switch Profiles tab, and then click Create Host Switch Profile. The form fields include Name, Description, Switch Type, Type, Transport Zones, IP Address Pool, and Uplink Profile.

   Transport zones are populated by the page by default. You cannot add or remove transport zones when you create a host switch profile.

   If the transport zones include an Overlay type, an IP address pool is required. After you select the type, IP address pool, and uplink profile, the page displays Bond-Uplink Mapping. Mapping items are generated based on the LAG member count of the selected uplink profile, for example bond0-0 and bond0-1. Select the corresponding uplink for each Bond member according to the host-side network plan.

4. Create an edge cluster profile.

   Click the Edge Cluster Profiles tab, and then click Create Edge Cluster Profile. The form fields include Name and Description.

5. Return to the profile lists and confirm that the profiles have been created.

   Different tabs display different fields. The Host Switch Profiles list displays uplink profile, switch type, type, and IP address pool. The Uplink Profiles list displays LAG mode, LAG members, MTU, Overlay VLAN, and Transport VLAN. The Edge Cluster Profiles list displays name, description, and creation time.

A transport node profile references host switch profiles and is used to apply host-side network configuration to target hosts. Applying configuration affects the host data-plane network. Run the operation only after you confirm the plan.

Note: Applying configuration to hosts pushes related settings such as host switch, uplink, IP address pool, Bond/LAG, and TEP. Run the operation during a maintenance window and confirm the rollback plan in advance.

1. Go to ZNS Network Center > Hosts.
2. Click the Transport Node Profiles tab.
3. Click Add Transport Node Profile.
4. Select the target host switch profile.

   The selection page displays host switch profile name, switch type, type, IP address pool, and creation time.

5. Enter transport node profile information and click OK.
6. Return to the Hosts tab and select the hosts to which you want to apply the configuration.

   Prefer hosts that are connected, have a normal configuration state, and match the network plan.

7. In the host actions, select Apply Configuration, and then select the transport node profile that you created.

   You must select a transport node profile when you apply configuration. When you apply configuration in bulk, all selected hosts use the same transport node profile.

8. After you confirm that the hosts, transport node profile, and NIC plan are correct, submit the operation.

1. Go to ZNS Network Center > Edge Clusters.
2. Click Create Edge Cluster.
3. Select an edge cluster profile.

   The selection page displays edge cluster profile name, description, and creation time.

4. Select hosts, and enter the edge cluster name and description.
5. After you confirm that the parameters are correct, click OK.

1. Go to ZNS Network Center > Tier-0 Gateway.
2. View existing Tier-0 gateways.

   The list displays Name, Configuration State, HA Mode, Edge Cluster, Router Link CIDR, Description, and Created At.

3. To create a Tier-0 gateway, click Create Tier-0 Gateway.
4. Select an edge cluster.

   The edge cluster is required. The selection page displays edge cluster name, configuration state, edge cluster profile, host count, and creation time.

5. Enter the Tier-0 gateway name, HA mode, Router Link CIDR, and description.

   On the current page, HA mode is fixed to Active-Standby. The name is required, must be 64 characters or fewer, and cannot contain spaces. The description must be 256 characters or fewer.

6. After you confirm that the parameters are correct, click OK.

1. Go to ZNS Network Center > Tier-1 Gateway.
2. View existing Tier-1 gateways.

   The list displays Name, Configuration State, HA Mode, Edge Cluster, Linked Tier-0 Gateway, Description, and Created At.

3. To create a Tier-1 gateway, click Create Tier-1 Gateway.
4. Select the linked Tier-0 gateway.

   The linked Tier-0 gateway is required. The selection page displays Tier-0 gateway name, configuration state, HA mode, and creation time.

5. Enter the Tier-1 gateway name, HA mode, and description.

   On the current page, HA mode is fixed to Active-Standby. The name is required, must be 64 characters or fewer, and cannot contain spaces. The description must be 256 characters or fewer.

6. Configure Route Advertisement as required.

   Setting	Description
   All NAT IPs	Advertises routes through the linked Tier-0 gateway for the external IP addresses used by enabled NAT rules on this Tier-1 gateway.
   All LB VIP Routes	Advertises routes through the linked Tier-0 gateway for the VIPs of load balancing virtual servers associated with this Tier-1 gateway.

   Both settings are disabled by default and can be configured independently. Route advertisement controls only whether the corresponding routes are advertised. It does not change the state of NAT rules or virtual servers.

   Note: Before you enable route advertisement, verify that each NAT IP or LB VIP is within the CIDR of an external interface on the linked Tier-0 gateway and is not advertised by another Tier-1 gateway linked to the same Tier-0 gateway.
7. Select an Ingress QoS Profile and an Egress QoS Profile as required.

   Ingress QoS Profile and Egress QoS Profile are optional. Select them according to the service traffic control plan.

8. After you confirm that the parameters are correct, click OK.

1. Go to ZNS Network Center > Segments.
2. View the segment list.

   The list displays Name, Configuration State, Traffic Type, VNI/VLAN ID, Connected Gateway, Gateway Address, IP CIDR, IP Range, MTU, Description, and Created At.

3. Locate the target segment by name or connected gateway.
4. Confirm that the target segment Configuration State is Deployed.

Create an SNAT rule to translate the source IP of matching traffic to an IP used for outbound traffic.

1. Navigate to ZNS Network Center > NAT.
2. Click Create NAT Rule and set Rule Type to SNAT.
3. Enter a Name and Description, and select a Gateway.

   The name must be 1–64 characters and cannot contain spaces. The description cannot exceed 255 characters.

   After you select a gateway, you can optionally select an Apply To interface. Only logical router interfaces on the selected gateway are available. If you leave this field blank, the rule uses the default forwarding scope of the gateway. Changing the gateway clears the selected interface.

4. Configure the addresses under Translation.
   1. In Source IP, enter the internal IPv4 address or CIDR.
   2. In Translated IP, enter one IPv4 address to use for outbound traffic.
5. Optionally configure Match criteria.

   Destination IP accepts one IPv4 CIDR or multiple IPv4 addresses separated by commas. Leave it blank to match any destination.

   If you specify a Destination Port, enter a value from 1 through 65535 and select TCP or UDP for Protocol.

6. Under Rule Settings, set the Priority.

   Priority must be an integer from 0 through 32767. This value does not determine the NAT rule match order.

7. Review the configuration and click OK.

Create a DNAT rule to translate the destination IP or port of external traffic to an internal service IP or port.

1. Navigate to ZNS Network Center > NAT.
2. Click Create NAT Rule and set Rule Type to DNAT.
3. Enter a Name and Description, select a Gateway, and optionally select an Apply To interface.

   The name must be 1–64 characters and cannot contain spaces. The description cannot exceed 255 characters.

   Only logical router interfaces on the selected gateway are available for Apply To. If you leave this field blank, the rule uses the default forwarding scope of the gateway. Changing the gateway clears the selected interface.

4. Configure the addresses under Translation.
   1. In Destination IP, enter the IPv4 address that external users access.
   2. In Translated IP, enter the IPv4 address of the internal service.
5. Configure source matching or port translation as required.

   To match traffic by source, enter one IPv4 CIDR or multiple IPv4 addresses separated by commas in Source IP. Leave it blank to match any source.

   To translate the destination port, specify both Destination Port and Translated Port, and select TCP or UDP for Protocol. Each port must be from 1 through 65535. Only single-port mapping is supported.

   Note: Port mapping does not support source IP matching. When either destination port is specified, Source IP is cleared and disabled.
6. Review the configuration and click OK.

Create a Reflexive NAT rule to establish a one-to-one bidirectional translation between an internal IP and an external IP.

1. Navigate to ZNS Network Center > NAT.
2. Click Create NAT Rule and set Rule Type to Reflexive NAT.
3. Enter a Name and Description, select a Gateway, and optionally select an Apply To interface.

   The name must be 1–64 characters and cannot contain spaces. The description cannot exceed 255 characters.

   Only logical router interfaces on the selected gateway are available for Apply To. If you leave this field blank, the rule uses the default forwarding scope of the gateway. Changing the gateway clears the selected interface.

4. In Source IP, enter one IPv4 address to map.
5. In Translated IP, enter one IPv4 address to use externally.
   Note: Reflexive NAT supports a one-to-one mapping between individual IPv4 addresses. CIDRs and multiple addresses are not supported.
6. Review the configuration and click OK.

Modify the basic information, apply-to interface, translation settings, or match criteria of a NAT rule.

1. Navigate to ZNS Network Center > NAT and locate the rule by name or gateway.
2. In the Actions column for the rule, select Edit.
3. Modify the settings for the rule type.
   • For all rules, you can modify Name, Description, and Apply To.
   • For an SNAT rule, you can modify Source IP, Translated IP, Destination IP, Protocol, and Destination Port.
   • For a DNAT rule, you can modify Destination IP, Translated IP, Source IP, Protocol, Destination Port, and Translated Port.
   • For a Reflexive NAT rule, you can modify Source IP and Translated IP.

   Note: You cannot modify Gateway, Rule Type, or Priority. To change these settings, create a new rule and delete the original rule after you verify that the new rule is available.
4. Review the configuration and click OK.

Enable or disable NAT rules to control whether they process NAT traffic.

1. Navigate to ZNS Network Center > NAT.
2. Enable or disable the required rules.
   • For one rule, select Enable or Disable from the Actions column.
   • For multiple rules in the same state, select the rules, click Bulk Action, and select Enable or Disable.

   You can enable only disabled rules and disable only enabled rules.

   Note: After you disable a rule, it no longer processes NAT traffic. The rule configuration is retained, and you can enable the rule again when required.
3. In the confirmation dialog box, verify the rules and click Enable or Disable.

Delete NAT rules that are no longer required so that they no longer provide address translation.

1. Navigate to ZNS Network Center > NAT.
2. Select the rules to delete.
   • To delete one rule, select Delete from the Actions column.
   • To delete multiple rules, select the rules, click Bulk Action, and select Delete.
3. In the confirmation dialog box, verify the rules and click OK.
   Note: Deleting a NAT rule removes its configuration. Before you delete a rule, verify that no services depend on the rule for address or port translation.

To monitor pool member availability, create a health monitor and associate it with a server pool.

1. Navigate to ZNS Network Center > Load Balancing and select the Health Monitors tab.
2. Click Create Health Monitor, and enter a Name and Description.

   The name must be 1–64 characters and cannot contain spaces. The description cannot exceed 256 characters.

3. Configure the health monitor.
   1. Verify that Type is set to OVN.
   2. Set Monitoring Interval (seconds) and Timeout Period (seconds).
   3. Set Rise Count and Fall Count.

   All four values must be integers greater than 0. The timeout period cannot exceed the monitoring interval.

   Rise Count specifies the number of consecutive successful checks required to mark a pool member as available. Fall Count specifies the number of consecutive failed checks required to mark a pool member as unavailable.

4. Review the configuration and click OK.

To configure session persistence, create a profile that forwards traffic with the same characteristics to the same pool member.

1. Navigate to ZNS Network Center > Load Balancing and select the Profiles tab.
2. Click Create Profile, and enter a Name and Description.

   The name must be 1–64 characters and cannot contain spaces. The description cannot exceed 256 characters.

3. Verify that Type is set to Session Persistence.
4. Select at least one Persistence Criteria.

   You can select Source IP, Source Port, Destination IP, and Destination Port. The system identifies sessions to persist by the selected combination of fields.

5. Optionally set Persistence Timeout (seconds).

   Leave the field blank to use the system default. A custom value must be an integer from 1 through 65535.

6. Review the configuration and click OK.

Create a server pool associated with a Tier-1 gateway and add pool members that receive traffic.

1. Navigate to ZNS Network Center > Load Balancing and select the Server Pools tab.
2. Click Create Server Pool, and enter a Name and Description.

   The name must be 1–64 characters and cannot contain spaces. The description cannot exceed 256 characters.

3. Select the Tier-1 Gateway that hosts the server pool.
4. Optionally select a Health Monitor.
5. Click OK.
6. On the Server Pools page, click the name of the new server pool and select the Pool Members tab.
7. Click Add Pool Member and select one or more Segment Ports.

   Segment ports associated with the gateway and assigned an IP address are available. You can add up to 100 pool members at a time.

8. Verify the IP address of each pool member and set the service Port.

   The default port is 80. You can enter an integer from 1 through 65535. An IP address and port combination cannot be duplicated in the same server pool.

9. Review the configuration and click OK.

Create a virtual server that receives client traffic on a VIP and listener port and forwards the traffic to an associated server pool.

1. Navigate to ZNS Network Center > Load Balancing and select the Virtual Servers tab.
2. Click Create Virtual Server, and enter a Name and Description.

   The name must be 1–64 characters and cannot contain spaces. The description cannot exceed 256 characters.

3. Select the Tier-1 Gateway that hosts the virtual server.
   Note: Changing the Tier-1 gateway clears the selected server pool. Select the gateway before you select the server pool.
4. Enter the VIP and set Listener Port and Protocol.

   The VIP must be one IPv4 address. The listener port must be an integer from 1 through 65535. TCP and UDP are supported.

5. Select a Server Pool.

   After you select a Tier-1 gateway, the Server Pool field appears. Only server pools associated with the selected Tier-1 gateway are available.

6. Optionally select a Profile for session persistence.
7. Review the configuration and click OK.

Modify the basic information and service settings of load balancing resources.

1. Navigate to ZNS Network Center > Load Balancing.
2. Open the page for the target resource and select Edit.
   • To edit a virtual server, server pool, health monitor, or profile, select the corresponding tab and select Edit from the Actions column for the resource.
   • To edit a pool member, select the Server Pools tab, click the server pool name, select the Pool Members tab, and select Edit from the Actions column for the member.
3. Modify the settings for the resource type.

   Resource	Editable Settings
   Virtual Server	Name, Description, VIP, Listener Port, Protocol, Server Pool, and Profile
   Server Pool	Name, Description, and Health Monitor
   Pool Member	Port
   Health Monitor	Name, Description, Monitoring Interval (seconds), Timeout Period (seconds), Rise Count, and Fall Count
   Profile	Name, Description, Persistence Criteria, and Persistence Timeout (seconds)

4. Review the configuration and click OK.

Enable or disable virtual servers and pool members to control load balancing traffic.

1. Navigate to ZNS Network Center > Load Balancing.
2. Open the page for the target resource.
   • To manage virtual servers, select the Virtual Servers tab.
   • To manage pool members, select the Server Pools tab, click the server pool name, and select the Pool Members tab.
3. Enable or disable the required resources.
   • For one resource, select Enable or Disable from the Actions column.
   • For multiple resources, select the resources, click Bulk Action, and select Enable or Disable.

   You can enable only disabled virtual servers or pool members and disable only enabled virtual servers or pool members.

   For a bulk enable operation, the confirmation dialog box lists only disabled resources in the selection. For a bulk disable operation, it lists only enabled resources.

   • After you disable a virtual server, it no longer forwards traffic. The VIP, listener port, and resource associations are retained.
   • After you disable a pool member, it no longer participates in traffic distribution for the server pool. The member configuration is retained.
4. In the confirmation dialog box, verify the resources and click Enable or Disable.

Disable or delete affected pool members before you detach their segment from a Tier-1 gateway.

Detaching a segment from a Tier-1 gateway does not automatically disable or delete the pool members on that segment. After the segment is detached, Pool Member Status on the virtual server details page might continue to show Up even when clients can no longer access the backend service through the VIP.

Note: Pool Member Status and the pool member State represent different information. After a network topology change, access the VIP from a client to verify that the load balancing service is available. Do not rely solely on Pool Member Status.

1. Navigate to ZNS Network Center > Load Balancing, and select the Virtual Servers tab.
2. Click the target virtual server name. On the virtual server details page, check Pool Member Status and identify the affected pool members by their IP addresses and ports.
3. Return to the Load Balancing page, select the Server Pools tab, click the target server pool name, and select the Pool Members tab.
4. Process the affected pool members according to the planned network change.
   • For a temporary detachment, select Disable from the Actions column for the target pool member. To process multiple pool members, select them, click Bulk Action, and select Disable.
   • For a permanent detachment, select Delete from the Actions column for the target pool member. To process multiple pool members, select them, click Bulk Action, and select Delete.
5. In the confirmation dialog box, verify the target pool members and confirm the operation.
6. Verify that temporarily disabled pool members show Disabled in the State column, or that permanently deleted pool members are removed from the page.

Delete virtual servers, server pools, pool members, health monitors, or profiles that are no longer required.

1. Navigate to ZNS Network Center > Load Balancing.
2. Open the page for the target resource.
   • To delete a virtual server, server pool, health monitor, or profile, select the corresponding tab.
   • To delete a pool member, select the Server Pools tab, click the server pool name, and select the Pool Members tab.
3. Select the resources to delete.
   • To delete one resource, select Delete from the Actions column.
   • To delete multiple resources, select the resources, click Bulk Action, and select Delete.
4. In the confirmation dialog box, verify the resources and click OK.
   Note: Before you delete resources, verify their relationships and the impact on services. Deleting a virtual server removes its VIP access point. Deleting a pool member removes it from the server pool.

1. Go to ZNS Network Center > Router QoS Profile.
2. Click Create Router QoS Profile.
3. Enter profile parameters.

   The form fields include Name, Direction, Description, Action, Bandwidth (kbps), and Burst Size (kb).

   Direction is required. Empty bandwidth and burst size values mean that no value is specified. If you enter a value, it cannot be negative.

4. After you confirm that the parameters are correct, click OK.

After the profile is created, you can view profile name, direction, action, default profile, bandwidth, burst size, description, and creation time in the list.

Note: Default profiles cannot be deleted. Before you delete a profile, confirm that it is no longer used by service gateways.

1. Go to ZNS Network Center > Segment QoS Profile.
2. Click Create Segment QoS Profile.
3. Enter basic information.

   Basic information includes Name and Description.

4. Enter ingress configuration.

   Ingress configuration includes Action, Average Bandwidth (kbps), Peak Bandwidth (kbps), and Burst Size (kb).

   Empty average bandwidth, peak bandwidth, and burst size values mean that no value is specified. If you enter a value, it cannot be negative.

5. Enter egress configuration.

   Egress configuration includes Action, Average Bandwidth (kbps), Peak Bandwidth (kbps), and Burst Size (kb).

   Empty average bandwidth, peak bandwidth, and burst size values mean that no value is specified. If you enter a value, it cannot be negative.

6. After you confirm that the parameters are correct, click OK.

After the profile is created, you can view default profile, ingress average bandwidth, ingress peak bandwidth, ingress burst size, egress average bandwidth, egress peak bandwidth, egress burst size, description, and creation time in the list.

Note: Default profiles cannot be deleted. Before you delete a profile, confirm that it is no longer used by service segments.

1. Go to ZNS Network Center > SpoofGuard Profile.
2. Click Create SpoofGuard Profile.
3. Enter basic information.

   Basic information includes Name and Description.

4. Set State.

   You can enable or disable the profile based on service security requirements. The default state is Enabled.

5. After you confirm that the parameters are correct, click OK.

After the profile is created, you can view profile name, state, default profile, description, and creation time in the list.

Note: Default profiles cannot be deleted. Before you delete a profile, confirm that it is no longer used by service networks.