Feature Requirements |
Series |
Models |
|---|---|---|
1, HQoS Telemetry collects statistics only about default SQ data. 2, Ethernet physical interfaces and trunk interfaces can only support statistics collection. 3, Slow second-level data collection is supported. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
1, Telemetry starts to collect statistics after the configuration is enabled. However, port statistics are collected when traffic is running. Therefore, the two statistics results are different. 2, When telemetry is used to collect statistics on an interface and detection services (such as BFD, twamp, 1ag, y1731, nqa2544, y1564, tp oam) exist, the number of incoming packets is collected as detection packets, causing the number to be different from the port statistics. 3, When telemetry is used to collect statistics on an interface and ETM packet loss occurs, the number of outgoing packets is different from the port statistics. In this case, you are advised to use the port-queue statistics function of HQoS to collect the number of outgoing packets. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
1, Shared policies cannot be used in conditional collection. 2, For the following policies, the smallest sampling interval is 1s. The interval at which packets are sent cannot be less than 1s even if the interval is set to 100 ms: A, Policies that contain if-match any rules B, Shared policies are configured on multi-NP-equipped boards. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
1, If an eTM subcard is installed and HQoS is configured for the bandwidth, the HQoS function of common TE traffic statistics collection is implemented by the eTM subcard although the Telemetry function is implemented by the NP. Therefore, the Telemetry statistics and common traffic statistics may be different. 2, In inter-board scenarios such as the TE HSB switchover and outbound interface change, Telemetry statistics are reset and statistics collection starts from 0 after the outbound interface is changed, which is different from common TE traffic statistics collection. 3, When common TE traffic statistics collection is switched between the CAR and statistics ID modes, Telemetry statistics and common TE traffic statistics may be different. 4, In TE FRR protection, if the primary tunnel is faulty and traffic is transmitted through the bypass tunnel, the telemetry statistics about the primary tunnel do not contain traffic statistics after FRR switching, which are different from the statistics queried on the primary tunnel. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
Telemetry supports a four-level collection period: 10 ms, 100 ms, 1s, and 30s. For a collection object with a collection period of 10 ms or 100ms, if the number of collected instances exceeds the specification at this level, the system automatically enters the next-level collection. If the number of collected instances exceeds the specification at the level with a collection period of 30s, the instances will not be monitored due to insufficient resources. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
There are restrictions on any sampling paths: 1. The maximum depth for any path sampling is three layers (the layer where the sampling path is located, its sublayer, and the grandchild layer). 2. After memory usage of a sampling task exceeds 80%, the sampling task is stopped (except for memory and CPU sampling). 3. After CPU usage of a sampling task exceeds 90%, the sampling task is stopped (except for memory and CPU sampling). 4. When excessive sampling tasks are configured and the sampling period is short, 20% of CPU resources are consumed. It is recommended that: 1. Reduce the number of any-path-sampling tasks. 2. Configure a longer sampling period. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
1. If the number of collected instances exceeds the capability provided by the device, the sampling period is automatically prolonged. An example assumes that a user configures a sampling task to sample all interfaces within 100 ms. If a total of 20 interfaces are available, the sampling interval is 100 ms. If a total of 200 interfaces are available, the sampling interval is 1s. 2. Telemetry supports multi-level flow control in order to avoid too heavy traffic. Firstly, each board is restricted to report data to the main control board through telemetry at a maximum rate of 20 instances every 100 ms for each module. Secondly, the main control board is restricted to send a maximum of 60 instances every 100 ms through telemetry and cache a maximum of 7500 pieces of data. If the upper limit is exceeded, the extra data is discarded. Eventually, after data is aggregated to gRPC of the main control board, gRPC implements flow control at a rate of 500 pps. 3. For sampling tasks with the minimum sampling precision being 10 seconds or greater, if the CPU usage of the current main control board is greater than 90%, telemetry prolongs the sampling task period of the CPU usage and memory usage to 600 seconds and suspends other sampling tasks. 4. For sampling tasks with the minimum sampling precision being 10 seconds or greater, the number of sampling instances is limited to 200 every 10 seconds. Time required for completing a sampling task = (Total number of instances/200) x 10 seconds. However, the sampling task is always completed 10 seconds earlier due to the actual number of instances sampled at a time. You can reduce the number of configured samples or set a long sampling period to prevent the data collection efficiency from being reduced. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
Telemetry supports IPv6 addresses for destination collectors. After IPv6 addresses for destination collectors are supported, both IPv4 and IPv6 addresses can be configured for a destination collector in a subscription. However, only one source address, either an IPv4 or IPv6 address, can be configured for gRPC-based data sending. 1. If an IPv4 source address is configured, the configured address is used as the source address of the IPv4 session, and the system automatically selects a source address (address of the outbound interface by default) for the IPv6 session. 2. If an IPv6 source address is configured, the configured address is used as the source address of the IPv6 session, and the system automatically selects a source address (address of the outbound interface by default) for the IPv4 session. If both IPv4 and IPv6 addresses need to be configured for a destination collector and specified source addresses are required, you can create multiple subscriptions. For some subscriptions, configure IPv4 addresses for the destination collector and IPv4 source addresses for gRPC-based data sending. For other subscriptions, configure IPv6 addresses for the destination collector and IPv6 source addresses for gRPC-based data sending. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
Nodes with data type decimal64 are not supported and such node data is not reported. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |