No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

Configuration Guide - System Monitor 01

NE05E and NE08E V300R003C10SPC500

This is NE05E and NE08E V300R003C10SPC500 Configuration Guide - System Monitor
Rate and give feedback :
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
Configuring Telemetry Static Subscription

Configuring Telemetry Static Subscription

Telemetry static subscription indicates that a device functioning as a client initiates a connection to a collector functioning as a server to send data collected.

Usage Scenario

The controller uses commands to configure devices that support Telemetry, subscribe to data sources, and collect data. The protocol used to send data can be gRPC or UDP.

If the connection between a device and the collection is interrupted, the device connects to the collector and sends data again. However, the data sampled when the connection is being re-established is lost.

After an active/standby switchover is performed or the system saves Telemetry service configurations and restarts, the Telemetry service reloads its configurations and continues to run. However, the data sampled during the restart or active/standby switchover is lost. This poses high pressure on devices. Therefore, Telemetry static subscription is often used for coarse-grained data collection.

Pre-configuration Tasks

Before configuring Telemetry static subscription, configure a static or dynamic routing protocol so that devices can communicate at the network layer.

Configuration Procedures

Perform one or more of the following configurations as required.

Configuring a Destination Collector

When you configure Telemetry static subscription to the data sampled or a customized event, you need to create a destination group and specify a destination collector to which the data is sent.

Context

When static subscription is configured, a device functions as a client and a collector functions as a server. To statically subscribe to the data sampled or a customized event, you need to configure the IP address and port number of a destination collector, and the protocol and encryption mode for data sending.

Procedure

  1. Run system-view

    The system view is displayed.

  2. Run telemetry

    The Telemetry view is displayed.

  3. Run destination-group destination-name

    A destination group to which the data sampled is sent is created, and the Destination-group view is displayed.

    By default, no destination group to which the data sampled is sent is created.

  4. Run ipv4-address ip-address port port [ vpn-instance vpn-instance ] [ protocol { grpc [ no-tls ] | udp } ]

    An IP address and a port number are configured for the destination collector, and a protocol and an encryption mode are configured for data sending.

    By default, no IP address or port number is configured for the destination collector, and no protocol or encryption mode is configured for data sending.

    NOTE:

    This command can be run for no more than five times for each destination group.

    Both this command and the protocol command in the Subscription view can be run to configure a protocol and encryption mode for the target collector. If the target collector is associated with the subscription, command configurations take effect based on the following rules:
    • If the protocol command has been run in the Subscription view, the protocol and encryption mode configured in the Subscription view take effect.

    • If the protocol command is not run in the Subscription view, the protocol and encryption mode configured in the Destination-group view take effect.

  5. Run commit

    The configuration is committed.

Configuring the Data to Be Sampled or a Customized Event

When you configure Telemetry static subscription to the data sampled or a customized event, you need to create a sampling sensor group and specify a sampling path and filter criteria.

Context

When static subscription is configured, a device functions as a client and a collector functions as a server. To statically subscribe to the data sampled or a customized event, you need to configure a source of the data to be sampled.

You can configure a Telemetry customized event. If a performance indicator of a resource object that Telemetry monitors exceeds the user-defined threshold, the customized event is reported to the collector in time for service policy determination.

Procedure

  • Configure the data to be sampled.
    1. Run system-view

      The system view is displayed.

    2. Run telemetry

      The Telemetry view is displayed.

    3. Run sensor-group sensor-name

      A sampling sensor group is created, and the Sensor-group view is displayed.

      By default, no sampling sensor group is created.

    4. Run sensor-path path { [ condition express op-field field op-type op op-value value [ { and | or } op-type op op-value value ] ] | [ policy reset-when-start ] } *

      A sampling path is configured for the Telemetry sensor group.

      By default, no sampling path is configured for the Telemetry sensor group.

      NOTE:

      A maximum of five sampling paths can be configured for a sampling sensor group, including sampling paths configured using the sensor-path and sensor-path self-defined-event commands. When the number of sampling paths reaches the upper limit, the device displays a message indicating that the maximum number of paths is reached.

      A sampling path name can be configured in a maximum of 10 sampling sensor groups at the same time. When the number of sampling paths reaches the upper limit, the device displays a message indicating that the maximum number of paths is reached.

      If the sampling sensor group is subscribed and configured with redundancy suppression, sampling paths with filter criteria specified cannot be configured in this sampling sensor group.

      This parameter is supported only when the sampling path is huawei-qos:qos/qosPortQueueStatInfos/qosPortQueueStatInfo.

    5. Run commit

      The configuration is committed.

  • Configure a customized event.
    1. Run system-view

      The system view is displayed.

    2. Run telemetry

      The Telemetry view is displayed.

    3. Run sensor-group sensor-name

      A sampling sensor group is created, and the Sensor-group view is displayed.

      By default, no sampling sensor group is created.

    4. Run sensor-path path self-defined-event condition express op-field field op-type op op-value value [ { and | or } op-type op op-value value ] { [ suppress-period period ] | [ level level ] }* [ description description ]

      A Telemetry customized event is configured.

      By default, no Telemetry customized event is configured.

      NOTE:

      A maximum of five sampling paths can be configured for a sampling sensor group, including sampling paths configured using the sensor-path self-defined-event and sensor-path commands. When the number of sampling paths reaches the upper limit, the device displays a message indicating that the maximum number of paths is reached.

      A sampling path name can be configured in a maximum of 10 sampling sensor groups at the same time. When the number of sampling paths reaches the upper limit, the device displays a message indicating that the maximum number of paths is reached.

      If a sampling sensor group is subscribed to and configured with redundancy suppression, Telemetry customized events cannot be configured in this sampling sensor group.

    5. Run commit

      The configuration is committed.

Creating a Subscription

When you configure Telemetry static subscription to the data sampled or a customized event, you need to create a subscription to associate the configured destination group with the configured sampling sensor group so that data can be sent to the collector.

Context

When static subscription is configured, a device functions as a client and a collector functions as a server. To statically subscribe to the data sampled or a customized event, you need to create a subscription to set up a data sending channel. The protocol used to send data can be gRPC or UDP.

To configure an SSL policy for a client so that the server and client establish a secure SSL connection, you must ensure that an SSL policy has been created. For details about how to create an SSL policy, see "Configuring and Binding an SSL Policy" in "Basic Configuration" in the configuration guide.

Procedure

  • Create a static subscription based on gRPC.
    1. Run system-view

      The system view is displayed.

    2. Run telemetry

      The Telemetry view is displayed.

    3. Run subscription subscription-name

      A subscription is created to associate a destination group with a sampling sensor group, and the Subscription view is displayed.

      By default, no subscription is created in the Telemetry view.

    4. Run sensor-group sensor-name [ sample-interval sample-interval [ suppress-redundant [ heartbeat-interval heartbeat-interval ] ] ]

      A sampling sensor group is associated with the subscription, and a sampling interval, a heartbeat interval, and redundancy suppression are configured for the sampling sensor group.

      By default, no sampling sensor group is associated.

      NOTE:

      If a sampling path of the associated sampling sensor group has threshold filter criteria, redundancy suppression cannot be configured. That is, threshold filtering and redundancy suppression are mutually exclusive.

    5. Run destination-group destination-name

      A destination group is associated with the subscription.

      By default, no destination group is associated.

      NOTE:

      A maximum of five destination groups can be associated with each subscription using this command. Five IP addresses and five port numbers can be configured for each destination group.

    6. (Optional) Run dscp dscp-value

      A DSCP value is set for data packets sent.

      The default DSCP value of data packets is 0.

      NOTE:

      When network data transmission is stable, Telemetry does not need to change the DSCP value of the data packets sent. When packet loss occurs during data transmission, you can configure a DSCP value in the Telemetry view for the data packets sent. You can improve the priority of packet transmission to ensure the quality of network data transmission.

    7. (Optional) Run protocol { grpc [ no-tls ] | udp }

      A protocol and encryption mode are configured for the target collector that is associated with this subscription.

      By default, no protocol and encryption mode are configured for the target collector that is associated with this subscription.

      NOTE:
      Both this command and the ipv4-address command in the Destination-group view can configure a protocol and encryption mode for the target collector. If the target collector is associated with the subscription, command configurations take effect based on the following rules:
      • If this command has been run, the protocol and encryption mode configured by running this command in the Subscription view take effect.

      • If this command is not run, the protocol and encryption mode configured by running the ipv4-address command in the Destination-group view take effect.

    8. (Optional) Configure an SSL policy for the client or enable the client to perform SSL verification on the server.

      NOTE:

      The certificate to be loaded must be supported by both the client and server.

      1. Run quit

        Return to the Telemetry view.

      2. Run quit

        Return to the system view.

      3. Run grpc

        The gRPC view is displayed.

      4. Run grpc client

        The gRPC client view is displayed.

      5. Run ssl-policy ssl-policy-name [ verify-cn cn-name ]

        An SSL policy is configured for the client during Telemetry static subscription.

        By default, no SSL policy is configured for a client during Telemetry static subscription.

        NOTE:

        If the no-tls parameter has been configured by running the ipv4-address or protocol (Subscription view) command and taken effect, the TLS encryption mode is not used. In this case, the client-specific SSL policy configured by running this command does not take effect.

      6. Run ssl-verify peer

        A client is enabled to perform SSL verification on a server during Telemetry static subscription.

        By default, a client does not perform SSL verification on a server during Telemetry static subscription.

        NOTE:

        If the no-tls parameter has been configured by running the ipv4-address or protocol (Subscription view) command and taken effect, the TLS encryption mode is not used. In this case, the configuration that enables the client to perform SSL verification on a server does not take effect.

    9. Run commit

      The configuration is committed.

  • Create a static subscription based on UDP.
    1. Run system-view

      The system view is displayed.

    2. Run telemetry

      The Telemetry view is displayed.

    3. Run subscription subscription-name

      A subscription is created to associate a destination group with a sampling sensor group, and the Subscription view is displayed.

      By default, no subscription is created in the Telemetry view.

    4. Run sensor-group sensor-name [ sample-interval sample-interval [ suppress-redundant [ heartbeat-interval heartbeat-interval ] ] ]

      A sampling sensor group is associated with the subscription, and a sampling interval, a heartbeat interval, and redundancy suppression are configured for the sampling sensor group.

      By default, no sampling sensor group is associated.

      NOTE:

      If a sampling path of the associated sampling sensor group has threshold filter criteria, redundancy suppression cannot be configured. That is, threshold filtering and redundancy suppression are mutually exclusive.

    5. Run destination-group destination-name

      A destination group is associated with the subscription.

      By default, no destination group is associated.

      NOTE:

      A maximum of five destination groups can be associated with each subscription using this command. Five IP addresses and five port numbers can be configured for each destination group.

    6. (Optional) Run local-source-address ipv4 ip-address [ port port ]

      A source IP address and a port number are configured for UDP-based data sending.

      By default, when UDP is used for data sending, the source IP address is the IP address of route's outbound interface selected by the socket and the port number is randomly selected.

      NOTE:

      The configured source IP address must be an existing service interface IP address. Otherwise, services may be interrupted.

    7. (Optional) Run dscp dscp-value

      A DSCP value is set for data packets sent.

      The default DSCP value of data packets is 0.

      NOTE:

      When network data transmission is stable, Telemetry does not need to change the DSCP value of the data packets sent. When packet loss occurs during data transmission, you can configure a DSCP value in the Telemetry view for the data packets sent. You can improve the priority of packet transmission to ensure the quality of network data transmission.

    8. (Optional) Run protocol { grpc [ no-tls ] | udp }

      A protocol and encryption mode are configured for the target collector that is associated with this subscription.

      By default, no protocol and encryption mode are configured for the target collector that is associated with this subscription.

      NOTE:
      Both this command and the ipv4-address command in the Destination-group view can configure a protocol and encryption mode for the target collector. If the target collector is associated with the subscription, command configurations take effect based on the following rules:
      • If this command has been run, the protocol and encryption mode configured by running this command in the Subscription view take effect.

      • If this command is not run, the protocol and encryption mode configured by running the ipv4-address command in the Destination-group view take effect.

    9. Run commit

      The configuration is committed.

Verifying the Telemetry Configuration

After configuring Telemetry static subscription to the data sampled or a customized event, check information about the sampling sensor group, destination group, and subscription.

Prerequisites

The Telemetry static subscription functions have been configured.

Procedure

  • Run the display telemetry sensor [ sensor-name ] command to check the sampling sensor information.
  • Run the display telemetry destination [ destination-name ] command to check information about a destination group to which the data sampled is sent.
  • Run the display telemetry subscription [ subscription-name ] command to check the subscription information.
  • Run the display telemetry sensor-path command to check the sampling path of a Telemetry sensor.
Translation
Download
Updated: 2019-01-14

Document ID: EDOC1100058924

Views: 6966

Downloads: 24

Average rating:
This Document Applies to these Products
Related Documents
Related Version
Share
Previous Next