DocsKnowledge BaseAPI Explorer
Documentation›Explore more›ZStack Cloud›OverviewZCF
Document navigation

Overview

SNMP stands for Simple Network Management Protocol, a protocol used to manage the devices in the network. ZStack Cloud provides the SNMP Management service. After you enable and configure this feature, you can obtain monitoring data of ZStack Cloud resources on a 3rd-party platform (such as an SNMP monitoring platform like ZABBIX) and receive alarms pushed by ZStack Cloud.

This document explains how to enable and configure the SNMP Management feature.

Quick Start Guide

Obtain Monitoring Data via SNMP

  1. Prepare an SNMP monitoring platform and MIB browser.
  2. Log in to ZStack Cloud, enable SNMP Management and configure required parameters.
  3. Download and view the ZStack Cloud MIB file.
  4. Log in to the SNMP monitoring platform, connect to ZStack Cloud and add monitoring items based on the MIB file.
  5. View monitoring data of ZStack Cloud resources on the SNMP monitoring platform.

Receive Alarm Messages via SNMP

  1. Prepare an SNMP monitoring platform and configure its Trap service.
  2. Log in to ZStack Cloud, enable SNMP Management and add an SNMP Trap receiver.
  3. Create an alarm endpoint of the SNMP Trap receiver type.
  4. Create an alarm and attach the SNMP Trap receiver endpoint to the alarm.
  5. Log in to the SNMP monitoring platform and connect to ZStack Cloud.
  6. When an ​​alarm is triggered​​, the SNMP monitoring platform can receive alarm messages pushed by ZStack Cloud.

Typical Scenarios

View Monitoring Data of the Cloud Resources via SNMP Platform

About this task

With the SNMP protocol, you can view monitoring data of ZStack Cloud resources on a 3rd-party platform and receive alarm messages pushed by ZStack Cloud. This chapter mainly explains how to obtain monitoring data of ZStack Cloud resources on a 3rd-party platform via SMNP.

Currently, you can obtain monitoring data for these resources via SNMP: hosts, primary storage, image storage, VM instances, and VPC vRouters.

This scenario takes the ZABBIX platform as an example. You can also use other SNMP platforms.

Configuration Information

The following table lists the basic configurations in this scenario.
ZStack Cloud Information ZABBIX Platform Information SNMP Protocol Information
Management Node IP: 172.26.51.91 Server IP: 172.26.51.240 Protocol Version: v2c
SNMP Agent Port: 1161 Community: v2c-test
The practical procedure is as follows:
  1. Prepare the ZABBIX platform and MIB Browser.
  2. Log in to ZStack Cloud and enable SNMP Management.
  3. Download the ZStack Cloud MIB file and view OIDs of resource monitoring items.
  4. Log in to the ZABBIX platform and connect to ZStack Cloud.
  5. Add monitoring items on the ZABBIX platform.
  6. View monitoring data of ZStack Cloud resources on the ZABBIX platform.

Procedure

  1. Prepare the ZABBIX platform and MIB browser.
    1. Prepare an SNMP monitoring platform that gets monitoring data from the Cloud resources through SNMP. This scenario uses ZABBIX.
    2. Prepare an MIB browser tool to view the ZStack Cloud MIB file. Click here to download the tool.
  2. Log in to ZStack Cloud and enable SNMP Management.
    On the main menu of ZStack Cloud, choose Settings > Platform Setting > SNMP Management. Then, the SNMP Management page is displayed. On the SNMP Management page, click Enable. The Enable SNMP Management page is displayed.
    Set the following parameters on the displayed page:
    • SNMP Agent Port: Set the port on the management node for receiving and responding to requests from ZABBIX. Default: 1161.
    • Protocol Version: Select v2c or v3. In this scenario, use v2c.
    • Community: Set a community for authentication between ZABBIX and the Cloud. In this scenario, use v2c-test.
    • SNMP Trap Receiver: Optional. Add a 3rd-party server to receive alarm messages pushed by the Cloud. You can add the receiver during or after enabling SNMP Management. Leave the SNMP Trap receiver unconfigured for this scenario.
    Figure 1. Enable SNMP Management


  3. Download the ZStack Cloud MIB file and view OIDs for resource monitoring items.
    1. On ZStack Cloud, click Download MIB in the upper-right corner of the SNMP Management page.
      Figure 2. Download MIB File


    2. Open MIB Browser. On the main menu, click Advanced... and configure SNMP Agent by setting the following parameters:
      • Address: Enter the IP address of the ZStack Cloud management node.
      • Port: Enter the SNMP Agent port of ZStack Cloud. In this scenario, enter 1161.
      • Read Community: Enter the community set in ZStack Cloud. In this scenario, enter v2c-test.
      • Write Community: Optional. Leave blank in this scenario.
      • SNMP Version: Select the SNMP version set in ZStack Cloud. In this scenario, select v2.
      Figure 3. Configure SNMP Agent Information in MIB Browser


    3. On the main menu of MIB Browser, click File > Load MIBs. Open the MIB file downloaded from ZStack Cloud.
      The MIB file contains monitoring items for five resource types: Host (kvmHost), Primary Storage (primaryStorage), Image Storage (backupStorage), VM instance (vm), VPC vRouter (vRouter).
    4. Expand the resource category folders to view OIDs for resource monitoring:
      Resource monitoring OIDs consist of two parts: the OID prefix and resource Index Value.
      • OID Prefix: The OID prefix identifies a monitoring item. In an expanded MIB directory, you can click any monitoring item to view its OID prefix.
      • Resource Index Value: Resource Index Value identifies the monitored resource. Right-click a resource Table (for example: kvmHostTable) and choose Table View. Then you can view Index Values for resources in the Index Value column.
      • Example:
        • The OID prefix for Host free memory percentage (memoryFreeInPercent): .1.3.6.1.4.1.60687.1.1.101.101.1.25
        • The Index Value for Host A (UUID: bf6c3abe4fff41f5b6212d9a64fe2480): 49004.15038.20479.16885.46625.11674.25854.9344
        • The Index Value for Host B (UUID: d23cf9c3839c47a9af056fd3f0829f7f): 53820.63939.33692.18345.44805.28627.61570.40831
        • Complete OID for monitoring Host A free memory: .1.3.6.1.4.1.60687.1.1.101.101.1.25.49004.15038.20479.16885.4
        • Complete OID for monitoring Host B free memory: .1.3.6.1.4.1.60687.1.1.101.101.1.25.53820.63939.33692.18345.44805.28627.61570.40831
      Figure 4. OID Prefix for Monitoring Items


      Figure 5. Resource Index Value


      Figure 6. Complete OID


  4. Log in to the ZABBIX platform and connect to ZStack Cloud.
    On the ZABBIX main menu, choose Configuration > Hosts. The Hosts page is displayed. On this page, click Create Host. The New Host page is displayed. Add ZStack Cloud as a host to ZABBIX.
    Set the following parameters on the displayed page:
    • Host Name: Enter a host name. In this scenario, enter Cloud.
    • Group: Select a group for the host.
    • Interface: Click Add > SNMP. Set the following parameters:
      • IP address: Enter the IP address of the ZStack Cloud management node.
      • Connect to: Select Connect to IP.
      • Port: Enter the SNMP Agent port set in ZStack Cloud. In this scenario, enter 1161.
      • SNMP version: Select the SNMP version. The version need to match the configuration in ZStack Cloud. In this scenario, select SNMPv2.
      • SNMP community: Enter the community set in ZStack Cloud. In this scenario, use v2c-test.
      • Set other parameters as needed.
    Figure 7. Connect ZStack Cloud to ZABBIX


    The connected ZStack Cloud appears in the ZABBIX Hosts list. Wait a few minutes. Check the Availability column. Green status indicates successful connection.
    Figure 8. Successful Connection to ZStack Cloud


  5. Add monitoring items on the ZABBIX platform.
    Three methods are available to connect ZStack Cloud monitoring items to ZABBIX: Connect single resource monitoring items, Connect batch resource monitoring items, Import full-set resource monitoring items. Using batch connection or full-set import is recommended.
    • Connect single resource monitoring items:

      On the ZABBIX main menu, choose Configuration > Hosts. The Hosts page is displayed. Select the newly added host. Click the Items column. The Items page is displayed. Click Create Item to add a monitoring item.

      This method adds monitoring items for only one specific metric of a single resource. Example: Obtain free memory percentage for Host A by setting these parameters:
      • Name: Set the monitoring item name. Example: Host A free memory percentage.
      • Type: Select SNMP agent.
      • Key: Enter the corresponding monitoring item. Example: memoryFreeInPercent-HostA.
      • Type of Information: Select Character.
      • Host Interface: Select the newly added host IP address and port.
      • SNMP OID: Enter the complete OID including both the OID prefix identifying the monitoring items and the resource Index Value identifying the specific resource. Example: OID for Host A free memory: 1.3.6.1.4.1.60687.1.1.101.101.1.25.49004.15038.20479.16885.46625.11674.25854.9344
      • Update Interval: Set the monitoring data collection interval. ZABBIX periodically gets new monitoring data from ZStack Cloud.
      • Set other parameters as needed.
      Figure 9. Connect Single Resource Monitoring Item


    • Connect batch resource monitoring items:

      Through batch connection, ZABBIX can obtain monitoring data for one or multiple types of resources on ZStack Cloud. Example: Acquire monitoring data for hosts:

      1. Add Template:

        On the ZABBIX main menu, click Configuration > Templates. On the Template page, click Create template to create a template. In this scenario, set the template name as For-Cloud.

      2. Add Discovery Rule:
        In the Template main list, select the created For-Cloud template. On the template details page menu, choose Discovery rules > Create discovery rule. Add a discovery rule. ZABBIX can use this rule to actively discover resources on ZStack Cloud. Set the following parameters on the displayed page:
        • Name: Enter a discovery rule name. For example, discover-host. This rule discovers host resources.
        • Type: Select SNMP agent.
        • Key: Enter a discovery rule key. For example, cloud.if.discovery.
        • SNMP OID: Enter an easily identifiable resource field OID. ZABBIX discovers and tags resources using this field. In this scenario, use resource UUID to discover and tag hosts. Enter: discovery[{#UUID},.1.3.6.1.4.1.60687.1.1.101.101.1.0]. Here, .1.3.6.1.4.1.60687.1.1.101.101.1.0 is the OID prefix for host UUID.
        • Update Interval: Set the discovery interval for ZABBIX to automatically discover ZStack Cloud resources.
        • Other parameters can be configured as needed.
        Figure 10. Add Discovery Rule


        A single template can add multiple discovery rules to discover different types of resources on ZStack Cloud and obtain monitoring data for multiple resource categories.

      3. Add Item Prototypes:

        In the Template main list, select the previously created discovery rule discover host within the For-Cloud template. Then, the discovery rule details page is displayed. Choose Item prototypes > Create item prototype to add item prototypes to the discovery rule. Based on the discovery rule and item prototypes, ZABBIX can automatically generate monitoring items in batches for resources on ZStack Cloud.

        Example: Batch-generate monitoring items for host memory free percentage by setting the following parameters:
        • Name: Set the monitoring item name template. For example, Host Memory Free Percentage-{#UUID}. ZABBIX automatically fills {#UUID} with the discovered resource ID.
        • Type: Select SNMP agent.
        • Key: Set the monitoring item key template. For example, HostMemoryFreeInPercent-[{#UUID}]. ZABBIX automatically fills in {#UUID}.
        • Type of Information: Select Character.
        • SNMP OID: Set the OID template for resource monitoring using this format: OID. prefix.{#SNMPINDEX}. The OID prefix identifies a specific monitoring item. ZABBIX automatically fills {#SNMPINDEX} with the Index Value of the discovered resource. For example, obtain the host memory free percentage by filling .1.3.6.1.4.1.60687.1.1.101.101.1.25.{#SNMPINDEX} here.
        • Update Interval: Set the monitoring data refresh interval. ZABBIX can periodically obtain new metrics from ZStack Cloud.
        • Configure other parameters as needed.
        Figure 11. Add Item Prototype


        A single template can add multiple monitoring items to obtain various monitoring data. This scenario adds monitoring items for host memory free percentage, host memory free amount, host memory used percentage, and host memory used amount.
        Figure 12. Add Multiple Item Prototypes for Discovery Rule


      4. Link the template to hosts:
        On the ZABBIX main menu, choose Configuration > Host. On the Host page, click the host corresponding to ZStack Cloud. Then, the editing page is displayed. On the displayed page, select the newly created For-Cloud template for the host.
        Figure 13. Link Template to Host


        After linking, on the ZABBIX main menu, choose Configuration > Hosts. On the Hosts page, select the host corresponding to ZStack Cloud and check its Items column. You can see that, based on the template discovery rules and item prototypes, the system has automatically generated 4 monitoring items for each host on ZStack Cloud.

        Figure 14. Batch-generate Monitoring Items Automatically


      5. Optional. Export the configured template.

        On the ZABBIX main menu, choose Configuration > Templates. On the Template page, select the created For-Cloud template, then click Export at the bottom to export the configured template as an offline file.

        You can import this file into other ZABBIX platforms to quickly create identical templates and simplify manual configuration.

    • Import Full-set Monitoring Items for ZStack Cloud.
      1. Contact ZStack Cloud official technical support for the full-set SNMP monitoring items file. This file contains all SNMP monitoring items for ZStack Cloud. You can import the file directly into ZABBIX without manual templates or monitoring item prototypes configuration.
        Note: The provided full-set monitoring items file currently only supports ZABBIX 6.0.
      2. On the main menu of ZABBIX, choose Configurations > Templates. On the Templates page, click Import to import the obtained full-set SNMP monitoring items file.
      3. On the ZABBIX main menu, choose Configuration > Host. On the Host page, click the host corresponding to ZStack Cloud. Then the editing page is displayed. On the displayed page, select the newly imported template named Cloud interfaces discovery all for the host.
      4. Return to the Host page, select the host corresponding to ZStack Cloud, and click Items. You can see that, based on the imported template, the system has generated full-set monitoring items for the host.
        Figure 15. Generate Full-set Monitoring Items


  6. View monitoring data of ZStack Cloud resources on the ZABBIX platform.
    On the ZABBIX main menu, choose Monitoring > Hosts. On the Host page, select the host corresponding to ZStack Cloud and click Latest Data to view the latest data for each monitoring item.
    Figure 16. View Latest Data of Monitoring Items




    Click the History column next to a monitoring item to view its history data.
    Figure 17. View Historical Data of Monitoring Items




What to do next

You have now successfully viewed the monitoring data of ZStack Cloud resources on the ZABBIX platform. For more information about using the ZABBIX platform, you can refer to the ZABBIX Official Documentation.

Receive Cloud Platform Alarm Messages via SNMP Platform

About this task

ZStack Cloud supports actively pushing alarm messages to 3rd-party platforms through the SNMP protocol. This chapter mainly explains how to receive ZStack Cloud alarm messages via SNMP.

This scenario takes the ZABBIX platform as an example. You can also use other SNMP platforms.

Configuration Information

The following table lists the basic configurations in this scenario.
ZStack Cloud Information ZABBIX Platform Information SNMP Protocol Information
Management Node IP: 172.26.51.205 Server IP: 172.26.51.240 Protocol Version: v2c
SNMP Agent Port: 1161 SNMP Trap Port: 162 Community: v2c-test
The practical procedure is as follows:
  1. Prepare the ZABBIX platform.
  2. Log in to ZStack Cloud, enable SNMP Management and add a SNMP Trap receiver.
  3. Download the ZStack Cloud MIB file.
  4. Configure the ZABBIX server.
  5. Log in to ZStack Cloud, create an alarm and set the SNMP Trap receiver as the endpoint.
  6. Add an SNMP trap receiver as an endpoint and attach it to an alarm.
  7. Log in to the ZABBIX platform and connect to ZStack Cloud.
  8. Add SNMP Trap monitoring items on the ZABBIX platform.
  9. View alarm messages.

Procedure

  1. Prepare the ZABBIX platform.
    Prepare an SNMP monitoring platform to receive alarm messages pushed as Traps from ZStack Cloud. This scenario takes ZABBIX platform as an example. You can also use other SNMP platforms.
  2. Log in to ZStack Cloud and enable SNMP Management.
    On the main menu of ZStack Cloud, choose Settings > Platform Setting > SNMP Management. Then, the SNMP Management page is displayed. On the SNMP Management page, click Enable. The Enable SNMP Management page is displayed.
    Set the following parameters on the displayed page:
    • SNMP Agent Port: Set the port on the management node for receiving and responding to requests from ZABBIX. Default: 1161.
    • SNMP Protocol Version: Select SNMP version. Supported protocol versions: v2c and v3. In this scenario, use v2c.
    • Community: Set a community for authentication between ZABBIX and the Cloud. In this scenario, use v2c-test.
    • SNMP Trap Receiver: Add the ZABBIX platform as an SNMP Trap receiver to receive alarm messages from ZStack Cloud. Set the following parameters:
      • Name: Set the SNMP Trap receiver name. In this scenario, use SNMP Trap Receiver.
      • IP Address: Enter the ZABBIX server IP address.
      • Port: Enter the Trap message receiving port on ZABBIX server. Default: 162
    Figure 18. Enable SNMP Management and Add SNMP Trap Receiver


  3. Download the ZStack Cloud MIB file.
    On ZStack Cloud, click Download MIB in the upper-right corner of the SNMP Management page.
    Figure 19. Download MIB File


  4. Configure the ZABBIX server.
    1. Log in to the ZABBIX server and run the following commands to download the Trap receiver script: 
      [root@appliance~]# yum install -y net-snmp-utils net-snmp-perl net-snmp    # Install Trap component package
[root@appliance~]# sudo yum install wget    # Install wget command-line tool
[root@appliance~]# wget https://cdn.zabbix.com/zabbix/sources/stable/6.0/zabbix-6.0.31.tar.gz    # Download ZABBIX Sources files (ensure version matches current platform)
[root@appliance~]# sudo yum install tar    # Install tar command-line tool
[root@appliance~]# tar zxvf zabbix-6.0.31.tar.gz    # Extract ZABBIX Sources files
[root@appliance~]# cp /root/zabbix-6.0.31/misc/snmptrap/zabbix_trap_receiver.pl /usr/bin/zabbix_trap_receiver.pl    # Copy Trap receiver script to /usr/bin
[root@appliance~]# chmod +x /usr/bin/zabbix_trap_receiver.pl    # Grant execute permissions to the Trap receiver script
    2. Edit the snmptrapd configuration file by setting the following parameters: 
      [root@appliance~]# vi /etc/snmp/snmptrapd.conf    # Enter editing mode for snmptrapd.conf and add this configuration:
-----------------------------------------------------------------------------------------------------------------------
# Modify at XXXXXXXX
disableAuthorization yes
perl do "/usr/bin/zabbix_trap_receiver.pl"
    3. Edit the ZABBIX Server configuration file by setting the following parameters: 
      [root@appliance~]# vi /etc/zabbix/zabbix_server.conf    # Enter editing mode for snmptrapd.conf
-------------------------------------------------------------------------------------------------------------------
Set these two parameters in the configuration file:
StartSNMPTrapper=1    # Enable SNMP Trap service
SNMPTrapperFile=/tmp/zabbix_traps.tmp    # Ensure the path entered here matches the SNMPTrapperFile parameter in zabbix_trap_receiver.pl
    4. Store the ZStack Cloud MIB file in the ZABBIX server's /usr/share/snmp/mibs directory. You can download it directly using the following commands: 
      [root@appliance~]# wget -P /usr/share/snmp/mibs http://172.26.51.205:5000/public/ZSTACK-CLOUD-MIB.mib
# 172.26.51.205:5000 is the ZStack Cloud UI access address for this scenario. Please replace it according to your actual environment.
[root@appliance~]# vi /etc/snmp/snmp.conf    # Create the snmp.conf file and add this configuration:
-----------------------------------------------------------------------------------------------------------------------
mibs +ALL
    5. Run the following commands to restart ZABBIX Server and activate the configuration: 
      [root@appliance~]# systemctl restart snmptrapd.service
[root@appliance~]# systemctl restart zabbix-server
  5. Log in to ZStack Cloud, create a new alarm and set SNMP Trap receiver as the endpoint.
    On the main menu of ZStack Cloud, choose Platform O&M > Cloud Monitoring > Endpoint. The Endpoint page is displayed. On this page, click Create Endpoint. The Create Endpoint page is displayed.
    Set the following parameters on the displayed page:
    • Name: Set an endpoint name. In this scenario, enter SNMP Trap.
    • Type: Select a SNMP Trap Receiver.
    • SNMP Trap Receiver: Select the previously added SNMP Trap receiver.
    Click Send Test Message. Upon success, you can add the endpoint.
    Figure 20. Add SNMP Trap Receiver Endpoint


  6. Add an SNMP trap receiver as an endpoint and attach it to an alarm.
    This scenario demonstrates creating a resource alarm that triggers when the VM Instance's CPU Idle Rate exceeds 80% for 30 seconds. Adjust these configurations according to your actual business requirements.
    On the main menu of ZStack Cloud, choose Platform O&M > Cloud Monitoring > Alarm > Resource Alarm. The Resource Alarm page is displayed. On this page, click Create Resource Alarm. The Create Resource Alarm page is displayed. On this page, create the resource alarm as mentioned above, making sure to select the created SNMP Trap receiver for the endpoint.
    Figure 21. Create Alarm and Attach SNMP Trap Receiver as the Endpoint


  7. Log in to the ZABBIX platform and connect to ZStack Cloud.
    On the ZABBIX main menu, choose Configuration > Hosts. The Hosts page is displayed. On this page, click Create Host. The New Host page is displayed. Add ZStack Cloud as a host to ZABBIX.
    Set the following parameters on the displayed page:
    • Host Name: Enter a host name. In this scenario, enter the Cloud.
    • Group: Select a group for the host.
    • Interface: Click Add > SNMP. Set the following parameters:
      • IP address: Enter the IP address of ZStack Cloud management node.
      • Connect to: Select Connect to IP.
      • Port: Enter the SNMP Agent port set in ZStack Cloud. In this scenario, enter 1161.
      • SNMP version: Select the SNMP version. The version needs to match the configuration in ZStack Cloud. In this scenario, select SNMPv2.
      • SNMP community: Enter the community set in ZStack Cloud. In this scenario, enter v2c-test.
      • Set other parameters as needed.
    Figure 22. Connect ZStack Cloud to ZABBIX


    The connected ZStack Cloud appears in the ZABBIX Hosts list. Wait a few minutes. Check the Availability column. Green status indicates successful connection. ZABBIX can now communicate with ZStack Cloud.
    Figure 23. Successful Connection to ZStack Cloud


  8. Add SNMP Trap monitoring items.
    On the ZABBIX main menu, choose Configuration > Hosts. Select the newly created Cloud host. Click Items. The Items page is displayed. On this page, click Create. The Create Item page is displayed.
    Set the following parameters on the displayed page:
    • Name: Set an monitoring item name. In this scenario, enter Cloud_SNMP_Trap.
    • Type: Select SNMP trap.
    • Key: Select snmp.fallback.
    • Type of information: Select Log.
    • Host interface: Select the IP interface of the newly created Cloud host.
    • History storage period: Set the retention period of history data.
    Set other parameters as needed.
    Figure 24. Add SNMP Trap Monitoring Items


  9. View alarm messages.
    On the ZABBIX main menu, choose Monitoring > Latest data. The Latest Data page is displayed. Find the newly created SNMP trap monitoring items. Click History to view alarm messages pushed by ZStack Cloud.
    Figure 25. View Alarm Messages




What to do next

You have successfully configured ZABBIX platform to receive alarm messages from ZStack Cloud. For more information about using ZABBIX platform, refer to the ZABBIX Official Documentation.

Glossary

Instance

An instance is a virtual machine or server that runs the images of operating systems in Cloud, such as VM instance and elastic baremetal instance.

VM Instance

A VM instance is a virtual machine instance running on a host. A VM instance has its own IP address and can access public networks and run application services.

Volume

A volume provides storage space for a VM instance. Volumes are categorized into root volumes and data volumes.

Root Volume

A root volume provides support for the system operations of a VM instance.

Data Volume

A data volume provides extended storage space for a VM instance.

Image

An image is a template file used to create a VM instance or volume. Images are categorized into system images and volume images.

Instance Offering

An instance offering defines the number of vCPU cores, memory size, network bandwidth, and other configuration settings of VM instances.

Disk Offering

A disk offering defines the capacity and other configuration settings of volumes.

GPU Specification

A GPU specification defines the frame per second (FPS), video memory, resolution, and other configuration settings of a physical or virtual GPU. GPU specifications are categorized into physical GPU specifications and virtual GPU specifications.

vNUMA Configuration

vNUMA uses CPU pinning to passthrough the topology of associated host physical NUMA (pNUMA) nodes to a VM instance, generating a topology of virtual NUMA (vNUMA) nodes for the VM instance. This topology enables a vCPU on a vNUMA node to primarily access the local memory and thus improves VM performance.

NUMA (Non-Uniform Memory Access)

Non-uniform memory access (NUMA) is a computer memory design where the memory access time depends on the memory location relative to the CPU. Under NUMA, a processor can access its own local memory faster than non-local memory and thus improves VM performance.

pNUMA Node (physical NUMA Node)

A pNUMA node (physical NUMA node) is a host NUMA node predefined based on the host NUMA architecture. It is used to manage the CPUs and memory of the host.

pNUMA Topology (physical NUMA Topology)

A pNUMA topology (physical NUMA topology) is the topology of the host NUMA nodes predefined by the CPU vendor based on the host NUMA architecture.

vNUMA Node (virtual NUMA Node)

A vNUMA node (virtual NUMA node) is generated by passing-through associated pNUMA nodes via CPU pinning. It is used to manage the CPUs and memory of a VM instance.

vNUMA Topology (virtual NUMA Topology)

A vNUMA topology (virtual NUMA topology) is the topology of VM NUMA nodes generated by passing-through associated pNUMA nodes via CPU pinning.

Local Memory

Local memory is the memory that a CPU (pCPU or vCPU) accesses through the Uncore iMC (Integrated Memory Controller) of the same NUMA (pNUMA or vNUMA) node. Compared with accessing non-local memory, accessing local memory has lower latencies.

CPU Pinning

CPU pinning assigns the virtual CPUs (vCPUs) of a VM instance to specific physical CPUs (pCPUs) of the host, which improves VM performance.

EmulatorPin Configuration

EmulatorPin assigns all other threads than virtual CPU (vCPU) threads and IO threads of a VM instance to physical CPUs (pCPUs) of the host so that these threads run on assigned pCPUs.

Auto-Scaling Group

An auto-scaling group is a group of VM instances that are used for the same scenarios. An auto-scaling group can automatically scale out or in based on application workloads or health status of VM instances in the group.

Snapshot

A snapshot is a point-in-time capture of data status in a volume.

Affinity Group

A VM scheduling policy is a resource orchestration policy based on which VM instances are assigned hosts to achieve the high performance and high availability of businesses.

Zone

A zone is a logical group of resources such as clusters, L2 networks, and primary storage. Zone is the largest resource scope defined in the Cloud.

Cluster

A cluster is a logical group of hosts (compute nodes).

Host

A host provides compute, network, and storage resources for VM instances.

Primary Storage

A primary storage is one or more servers that store volume files of VM instances. These files include root volume snapshots, data volume snapshots, image caches, root volumes, and data volumes.

Image Storage

An image storage is a storage server that stores VM image templates, including ISO image files.

iSCSI Storage

iSCSI storage is an SAN storage that uses the iSCSI protocol for data transmission. You can add an iSCSI SAN block as a Shared Block primary storage or pass through the block to a VM instance.

FC Storage

FC storage is an SAN storage that uses the FC technology for data transmission. You can add an FC SAN block as a Shared Block primary storage or pass through the block to a VM instance.

NVMe Storage

A type of storage implemented via the NVMe-oF (NVMe over fabrics) protocol. You can add a block device configured from an NVMe storage as SharedBlock primary storage.

L2 Network

An L2 network is a layer 2 broadcast domain used for layer 2 isolation. Generally, L2 networks are identified by names of devices on the physical network.

VXLAN Pool

A VXLAN pool is a collection of VXLAN networks established based on VXLAN Tunnel Endpoints (VTEPs). The VNI of each VXLAN network in a VXLAN pool must be unique.

L3 Network

An L3 network includes IP ranges, gateway, DNS, and other network configurations that are used by VM instances.

Public Network

Generally, a public network is a logical network that is connected to the Internet. However, in an environment that has no access to the Internet, you can also create a public network.

Flat Network

A flat network is connected to the network where the host is located and has direct access to the Internet. VM instances in a flat network can access public networks by using elastic IP addresses.

VPC Network

A VPC network is a private network where VM instances can be created. A VM instance in a VPC network can access the Internet through a VPC vRouter.

Management Network

A management network is used to manage physical resources in the Cloud. For example, you can create a management network to manage access to hosts, primary storage, image storage, and VPC vRouters.

Flow Network

A flow network is a dedicated network for port mirror transmission. You can use a flow network to transmit the mirrors of data packets of NIC ports to the target ports.

VPC vRouter

A VPC vRouter is a dedicated VM instance that provides multiple network services.

VPC vRouter HA Group

A VPC vRouter HA group consists of two VPC vRouters. Either VPC vRouter can be a primary or secondary VPC vRouter for the group. If the primary VPC vRouter does not work as expected, the VPC vRouter becomes the secondary VPC vRouter in the group to ensure high availability of business.

vRouter Image

A vRouter image encapsulates network services and can be used to create VPC vRouters.

Dedicated-Performance LB Image

A dedicated-performance load balancer (LB) image encapsulates dedicated-performance load-balancing services and can be used to create load balancer instances. However, a dedicated-performance load balancer image cannot be used to create VM instances.

vRouter Offering

A vRouter offering defines the number of vCPU cores, memory size, image, management network, and public network configuration settings of VPC vRouters. You can use a vRouter offering to create VPC vRouters that can provide network services for public networks and VPC networks.

LB Instance Offering

A load balancer (LB) instance offering defines the CPU, memory, image, and management network configuration settings used to create LB instances. LB instances provide load balancing services for the public network, flat network, and VPC network.

SDN Controller

The SDN controller is the core of the SDN architecture, responsible for centralized management and control of network devices.

SDN Cluster

A cluster of dedicated VM instances designed to provide highly available SDN capabilities.

SDN Instance

A dedicated VM instance designed to provide SDN network capabilities.

SDN Image

An SDN image encapsulates an SDN software and can be used to create SDN instances.

SDN Instance Offering

An SDN instance offering defines the CPU, memory, SDN image, and management network configuration used for creating SDN instances.

Security Group

A security group provides security control services for VM NICs. It filters the ingress or egress TCP, UDP, and ICMP packets of VM NICs based on the specified security rules.

VIP

In bridged network environments, a virtual IP address (VIP) provides network services such as serving as an elastic IP address (EIP), port forwarding, load balancing, IPsec tunneling. When a VIP provides the preceding network services, packets are sent to the VIP and then routed to the destination network where VM instances are located.

EIP

An elastic IP address (EIP) functions based on the NAT technology. IP addresses in a private network are translated into an EIP that is in another network. This way, private networks can be accessed from other networks by using EIPs.

Port Forwarding

Port forwarding functions based on the layer-3 forwarding service of VPC vRouters. This service forwards traffic flows of the specified IP addresses and ports in a public network to specified ports of VM instances by using the specified protocol. If your public IP addresses are insufficient, you can configure port forwarding for multiple VM instances by using one public IP address and port.

Load Balancer

A load balancer distributes traffic flows of a virtual IP address to backend servers. It automatically inspects the availability of backend servers and isolates unavailable servers during traffic distribution. This way, the load balancer improves the availability and service capability of your business.

Listener

A listener monitors the frontend requests of a load balancer and distributes the requests to a backend server based on the specified policy. In addition, the listener performs health checks on backend servers.

Forwarding Rule

A forwarding rule forwards the requests from different domain names or URLs to different backend server groups.

Backend Server Group

A backend server group is a group of backend servers that handles requests distributed by load balancers. It is the basic unit for traffic distribution by load balancer instances.

Backend Server

A backend server handles requests distributed by a load balancer. You can add a VM instance on the Cloud or a server on a third-party cloud as a backend server.

Frontend Network

A frontend network is a type of network that is associated with a load balancer. Requests from the network are distributed by the load balancer to backend servers based on a specified policy.

Backend Network

A backend network is a type of network that is associated with a load balancer. Requests from frontend networks are distributed by the load balancer to servers in the backend network.

Load Balancer Instance

A load balancer instance is a custom VM instance used to provide load balancing services.

Certificate

If you select HTTPS for a listener, associate it with a certificate to make the listener take effect. You can upload either a certificate or certificate chain.

Firewall

A firewall is an access control policy that monitors ingress and egress traffic of VPC vRouters and decides whether to allow or block specific traffic based on the associated rule sets and rules.

Firewall Rule Set

A firewall rule set is a set of rules that a firewall uses to defend against network attacks. You need to associate a rule set with the egress or ingress flow direction of VPC vRouter NICs to make the rule set take effect.

Firewall Rule

A firewall rule is an access control entry associated with the egress or ingress flow direction of VPC vRouter NICs to defend against network attacks. A firewall rule includes rule priority, match condition, and behavior.

Rule Template

A rule template is a template that you can select when you add rules to a rule set or a firewall.

IP/Port Set

An IP or port set is a set of IP addresses or ports that you can select when you add rules to a rule set or a firewall.

IPsec Tunnel

An IPSec tunnel encrypts and verifies IP packets that transmit over a virtual private network (VPN) from one site to another.

OSPF Area

An Open Shortest Path First (OSPF) area is divided from an autonomous system based on the OSPF protocol. This simplifies the hierarchical management of vRouters.

NetFlow

A NetFlow monitors the ingress and egress traffic of the NICs of VPC vRouters. The supported versions of data flows are V5 and V9.

Port Mirroring

Port mirroring mirrors the traffic data of VM NICs and sends the traffic data to the target ports. This allows for the analysis of data packets of ports and simplifies the monitoring and management of data traffic and makes it easier to locate network errors and exceptions.

Route Table

A route table contains information about various routes that you configure. Route entries in a route table must include the destination network, next hop, and route priority.

CloudFormation

CloudFormation is a service that simplifies the management of cloud resources and automates deployment and O&S. You can create a stack template to configure cloud resources and their dependencies. This way, resources can be automatically configured and deployed in batches. CloudFormation provides easy management of the lifecycle of cloud resources and integrates automatic O&S into API and SDK.

Resource Stack

A resource stack is a stack of resources that are configured by using a stack template. The resources in the stack have dependencies with each other. You can manage resources in the stack by managing the resource stack.

Stack Template

A stack template is a UTF8-encoded file based on which you can create resource stacks. The stack template defines the resources that you want, the dependencies between the resources, and the configuration settings of the resources. When you use a stack template to create a resource stack, CloudFormation parses the template and the resources are automatically created and configured.

Sample Template

A sample template is a commonly used resource stack. You can use a sample template provide by the Cloud to create resource stacks.

Designer

A designer is a CloudFormation tool that allows you to orchestrate cloud resources. You can drag and drop resources on a canvas and use lines to establish dependencies between the resources.

Baremetal Cluster

A baremetal cluster consists of baremetal chassis. You can manage baremetal chassis by managing a baremetal cluster where the chassis reside.

Deployment Server

A deployment server is a server that provides PXE service and console proxy service for baremetal chassis.

Baremetal Chassis

A baremetal chassis is used to create a baremetal instance and is identified based on the BMC interface and IPMI configuration setting.

Preconfigured Template

A preconfigured template is used to create a preconfigured file that allows for unattended batch installation of an operating system for baremetal instances.

Baremetal Instance

A baremetal instance is an instantiated baremetal chassis.

Elastic Baremetal Management

Elastic Baremetal Management provides dedicated physical servers for your applications to ensure high performance and stability. In addition, this feature allows elastic scaling. You can apply for and scale resources based on your needs.

Provision Network

A provision network is a dedicated network for PXE boot and image downloads while creating elastic baremetal instances in a gateway proxy cluster.

Elastic Baremetal Cluster

Provides a separated cluster to manage baremetal nodes.

Gateway Node

A gateway node is a node where the ingress and egress traffic of the Cloud and elastic baremetal instances in gateway proxy clusters is forwarded.

Baremetal Node

A baremetal node is used to create a baremetal instance and is identified based on the BMC interface and IPMI configuration setting.

Elastic Baremetal Instance

An elastic baremetal instance has the same performance as physical servers and allows elastic scaling. You can apply for and scale resources based on your needs.

Elastic Baremetal Offering

An elastic baremetal offering defines the number of vCPU cores, memory size, CPU architecture, CPU model, and other configuration settings of elastic baremetal instances.

vCenter

The Cloud allows you to take over vCenter and manage resources on the vCenter.

VM Instance

A VM instance is an ESXi virtual machine instance running on a host. A VM instance has its own IP address to access public networks and can run application services.

Network

A vCenter network defines the network settings of VM instances on vCenter, such as IP range, gateway, DNS, and network services.

Volume

A volume provides storage space for a VM instance on vCenter. A volume attached to a VM instance can be used as a root volume or data volume. A root volume provides support for the system operations of a VM instance. A data volume provides extended storage space for a VM instance.

Image

An image is a template file used to create a VM instance or volume on vCenter. Images are categorized into system images and volume images.

Event Message

Event Message displays event alarm messages of vCenter that is took over by the Cloud. This feature allows you to locate errors and exceptions efficiently.

Network Topology

A network topology visualizes the network architecture of the Cloud. It allows for efficient planning, management, and improvement of network architecture. Network topologies can be categorized into global topologies and custom topologies.

Performance Analysis

Performance Analysis displays the performance metrics of key resources monitored externally or internally in the Cloud. You can view the performance analysis or export the analysis report as needed to improve the O&M efficiency.

Capacity Management

Capacity Management visualizes the capacities and usages of key resources in the Cloud. You can use this feature to improve O&S efficiency.

MN Monitoring

Management Node (MN) monitoring allows you to view the health status of each management node when you use multiple management nodes to achieve high availability.

Alarm

An alarm is used to monitor the status of time-series data and events and respond to the status change. Alarms can be categorized into resource alarm, event alarm, and extended alarm.

One-Click Alarm

A one-click alarm integrates multiple metrics of a resource. You can create one-click alarms for multiple resources to monitor these resources.

Alarm Template

An alarm template is a template of alarm rules. If you associate an alarm template with a resource group, an alarm is created to monitor the resources in the group.

Resource Group

A resource group consists of resources grouped based on your business needs. If you associate an alarm template with a resource group, the alarm rules specified by the template take effect on all the resources in the group.

Message Template

A message template specifies the text template of a resource alarm message or event alarm message sent to an SNS system.

Message Source

A message source is used to take over extended alarm messages. If you configure alarms for message sources, extended alarm messages can be sent to various endpoints.

Endpoint

An endpoint is a method that users obtain subscribed messages. Endpoints are categorized into system endpoints, email, DingTalk, HTTP application, short message service, and Microsoft Teams.

Alarm Message

An alarm message is a message sent the time when an alarm is triggered.

Current Task

A current task is an ongoing operation performed in the Cloud. You can perform centralized management over ongoing operations.

Operation Log

An operation log is a chronological record of operations on the specified objects and their operation results.

Audit

Audit monitors and records all activities on the Cloud. You can use this feature to implement operation tracking, cybersecurity classified protection compliance, security analysis, troubleshooting, and automatic O&M.

Log Collection

Allows you to collect with one click the log data from the Cloud and various nodes on the Cloud generated in the specified time period and download the log data.

One-Click Inspection

Comprehensively inspects the health status of key resources and services of the Cloud and scores their healthiness based on the inspection results. In addition, the one-click inspection service provides O&M suggestions and inspection reports.

Backup Management

Backup management integrates multiple disaster recovery technologies such as incremental backup and full backup that are suitable for multiple business scenarios. You can implement local backup and remote backup based on your business needs.

Backup Job

You can create a backup job to back up local VM instances, volumes, or databases to a specified storage server on a regular basis.

Local Backup Data

Local backup data of VM instances, volumes, and databases is stored in the local backup server.

Local Backup Server

A local backup server is located at the local data center and is used to store local backup data.

Remote Backup Server

A remote backup server is located at a remote data center or a public cloud and is used to store remote backup data.

Continuous Data Protection (CDP)

Continuous Data Protection (CDP) provides second-level and fine-grained continuous backups for important business systems in VM instances, allowing users to restore VM data to a specific time state, and retrieve files without restoring the system.

CDP Task

You can create a CDP task to continuously back up your VM data to a specified backup server to achieve continuous data protection and recovery.

CDP Data

The backup data generated from continuous data protection on VM instances is stored in local backup servers.

Recovery Point

A recovery point is a data point generated during continuous data protection. A recovery point corresponds to a data record within the recovery point interval specified by the user.

Locked Recovery Point

You can lock or unlock a recovery point as needed. After a recovery point is locked, data of the recovery point will not be automatically cleared or deleted.

Recovery Task

A recovery task helps you quickly restore data by specifying a CDP task and recovery point, and allows you to view the recovery progress and logs in a more friendly way.

Cryptography Security Compliance

The Cryptography Security Compliance service provides applications with cloud security capabilities based on commercial cryptography, meeting the requirements of commercial cryptography application security assessments.

HSM Pool

An HSM pool is a logical group of hardware security modules (HSMs) and is used to provide unified cryptography services such as signature validation and encryption.

HSM

A hardware security module (HSM) is a dedicated device that encrypts, decrypts, and authenticates information by using the cryptographic technology.

Platform Cryptography Security Compliance

Enables the Cloud to meet the requirements of Cryptography Security Compliance through the cryptography capabilities provided by HSM pools.

Certificate Login

Authenticates the identity of a user by using a UKey device.

Data Protection

Protects important data on the Cloud to ensure the data confidentiality and integrity.

Scheduled Job

A scheduled job defines that a specific action be implemented at a specified time based on a scheduler.

Scheduler

A scheduler is used to schedule jobs. It is suitable for business scenarios that last for a long time.

Tag

A tag is used to mark resources. You can use a tag to search for and aggregate resources.

Migration Service

The Cloud provides V2V migration service that allows you to migrate VM instances and data from other virtualized platform to the current cloud platform.

ZMigrate Migration Service

A migration service installed from Application Market that migrates VM instances and their data from VMware environments to the current cloud platform.

V2V Migration

V2V Migration allows you to migrate VM instances from the VMware or KVM platform to the current cloud platform.

V2V Conversion Host

A V2V conversion host is a host in the destination cluster that you need to specify during V2V migration to cache VM instances and data when you implement V2V migration. After the VM instances and data are cached in the V2Vconversion host, they are migrated to the destination primary storage.

User

A user is a natural person that constructs the most basic unit in Tenant Management.

User Group

A user group is a collection of natural persons or a collection of project members. You can use a user group to grant permissions.

Role

A role is a collection of permissions that can be granted to users. A user that assumes a role can call API operations based on the permissions specified by the role. Roles are categorized into platform roles and project roles.

Single Sign-On

The Single Sign-On service provided by the Cloud. It supports seamless access to SSO systems. Through the service, related users can directly log in to the Cloud and manage cloud resources.

Project

A project is a task that needs to be accomplished by specific personnel at a specified time. In Tenant Management, you can plan resources at the project granularity and allocate an independent resource pool to a project. The word Tenant in Tenant Management mainly refers to projects. A project is a tenant.

Project Member

A project member is a member in a project who is granted permissions on specific project resources and can use the resources to accomplish tasks. Project members include the project admin, project managers, and normal project members.

Process Management

Process management is part of ticket management that manages the processes related to the resources of projects. Processes can be categorized into default processes and custom processes.

My Approvals

In the Cloud, only the administrator and project administrators are granted approval permissions. the administrator and project administrators can approve or reject a ticket. If a ticket is approved, resources are automatically deployed and allocated to the specified project.

Bills

A bill is the expense of resources totaled at a specified time period. Billing is accurate to the second. Bills can be categorized into project bills, department bills, and account bills.

Pricing List

A pricing list is a list of unit prices of different resources. The unit price of a resource is set based on the specification and usage time of the resource.

Console Proxy

Console proxy allows you to log in to a VM instance by using the IP address of a proxy.

AccessKey Management

An AccessKey pair is a security credential that one party authorizes another party to call API operations and access its resources in the Cloud. AccessKey pairs shall be kept confidential.

IP Allowlist/Blocklist

An IP allowlist or blocklist identifies and filters IP addresses that access the Cloud. You can create an IP allowlist or blocklist to improve access control of the Cloud.

Application Center

Application Market allows you to add applications to the Cloud and then access the applications with one click. It extends the functionality of the Cloud. You can add default applications through the built-in installation package or add more applications through URLs.

Sub-Account Management

A sub-account can be created by the admin or synced from an SSO authentication system and is managed by the admin. Resources created under a sub-account are managed by the sub-account.

Theme and Appearance

You can customize the theme and appearance of the Cloud.

Email Server

If you select Email as the endpoint of an alarm, you need to set an email server. Then alarm messages are sent to the email server.

Log Server

A log server is used to collect management node logs or the platform operation logs. You can add a log server to the cloud and use the collected logs for operation trace or troubleshooting. This makes your O&M more efficient.

Global Setting

Global Setting allows you to configure settings that take effect on the whole platform.

Scenario Template

Scenario Template provides multiple templates that encapsulate scenario-based global settings. You can apply a template globally with one click based on your business needs. This improves your O&M efficiency.

HA Policy

HA Policy is a mechanism that ensures sustained and stable running of the business if VM instances are unexpectedly stopped or are errored because of errors occurring to compute, network, or storage resources associated with the VM instances. By enabling this feature, you can customize VM HA policies to ensure your business continuity and stability.

Time Management

Manages the Cloud system time and allows you to configure time servers for the Cloud. After you configure NTP time servers for the Cloud, the clock of the time servers is synced with all nodes of the Cloud.

GPU Device

A GPU device is a powerful microprocessor with high computational capabilities. You can use a GPU device to handle intricate graphics rendering and parallel computing jobs, thus improving the efficiency of businesses such as graphic production, video processing, and machine learning.

Script Library

The script library stores and manages script files centrally. By executing scripts on VM instances, you can complete complex O&M operations and automated jobs.

XML Hook

An XML Hook is a script that can flexibly insert or modify parameters in XML files of VM instances. By attaching an XML Hook to a VM instance, you can customize VM configurations and enable specialized functionalities.

Container Service

A simple and user-friendly container management service, providing features like GPU management & scheduling, multi-tenancy, multi-cluster, quota configuration, CI/CD. and microservice. The service reduces the container using complexity and aligns well with traditional user's habits, helping you easily manage and deploy your container cluster, and enjoy the benefits of cloud-native technologies in a quick and convenient way.

Advanced Monitoring Server

An advanced monitoring server is a dedicated VM instance used to receive advanced monitoring data of load balancers and other resources.

Advanced Monitoring Server Image

An advanced monitoring server image encapsulates the advanced monitoring service and can be used to create advanced monitoring server.

Advanced Monitoring Server Offering

An advanced monitoring server offering defines the CPU cores, memory size, image, management network, and public network configurations of advanced monitoring server. You can use an advanced monitoring server offering to create advanced monitoring servers.

Plugin Management

You can package extended resources or tools into standardized plugins for quick installation and integration, expanding the Cloud capabilities.

Region Management

A region is a self-contained cloud environment with independent management node(s), networks, hardware, and cloud resources. ZStack IAM enabled user synchronization and SSO across multiple regions.
PreviousZStack CloudNextZStack Cloud
SNMP Management Tutorial | 5.5.38 | ZStack Cloud · ZCF | ZStack Resource Center