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 - Network Management and Monitoring

CloudEngine 8800, 7800, 6800, and 5800 V200R005C10

This document describes the configurations of Network Management and Monitoring, including SNMP, RMON, NETCONF, OpenFlow, LLDP, NQA, Mirroring, Packet Capture, Packet Trace, Path and Connectivity Detection Configuration, NetStream, sFlow, and iPCA.
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).
Licensing Requirements and Limitations for IOAM

Licensing Requirements and Limitations for IOAM

Involved Network Elements

The switch needs to work with an analyzer.

Licensing Requirements

The IOAM function is controlled by a license and is disabled on a new switch by default. To use the IOAM function, apply for and purchase the license from the equipment supplier.

Version Requirements

Table 17-4 Products and minimum version supporting IOAM

Product Model

Minimum Version Required

CE8868EI/CE8861EI

V200R005C10

CE8850-64CQ-EI

V200R005C00

CE6865EI

V200R005C00

Feature Limitations

  • Currently, IOAM can be used to collect and copy only UDP, TCP, and VXLAN packets. Packets can be forwarded to the analyzer through a maximum of eight hops (including the ingress node, transit nodes, and egress node). The IOAM function must be configured on all the nodes that packets pass through. Otherwise, Packets are discarded due to the check failure on the egress node.

  • The header ID of IOAM packets is a special value (0xaaaaaaaabbbbbbbb by default). If other types of packets use the same header ID as IOAM packets, they may be processed as IOAM packets due to a mismatch.

  • The maximum IOAM packet processing capability of the ingress or egress node does not exceed 200 kpps.

  • The CE8850-64CQ-EI can function only as a transit node but not an ingress or egress node. On the CE8850-64CQ-EI, do not add any device ID, ingress port, or egress port; otherwise, the switch cannot accurately determine the path for sending packets.

  • When the CE6865EI acts as an ingress node, the IOAM function needs to be enabled. The IOAM function and the interface split function of 100GEx/0/3 (x indicates the stack ID of the switch) are mutually exclusive and cannot be configured together. When you configure the IOAM function after canceling the interface split function of 100GEx/0/3, restart the switch for the IOAM function to take effect.

  • When the CE8868EI or CE8861EI acts as an ingress node, the IOAM function needs to be enabled. The IOAM function and the interface split function of some interfaces are mutually exclusive and cannot be configured together. When you configure the IOAM function after canceling the interface split function of these interfaces, restart the switch for the IOAM function to take effect. These interfaces are 100GEx/1/2 of CE88-D24S2CQ and CE88-D24S2CQ_U, 100GEx/1/1 of CE88-D24T2CQ, 100GEx/1/8 of CE88-D8CQ, and 40GEx/1/13 and 40GEx/1/14 of CE88-D16Q.

  • On the ingress node, when the link type of an interface is set to dot1q-tunnel, packets on the interface cannot be encapsulated into IOAM packets.

  • In VXLAN scenarios, the IOAM function and VXLAN function cannot be used together on the VXLAN encapsulation and decapsulation devices. If they are used together, the IOAM function is unavailable.

  • In stack scenarios, when non-known unicast packets are collected and copied, the port number and device ID carried in IOAM packets are incorrect.

  • If the sFlow or NetStream sampling ratio is configured on an interface and then a traffic policy containing the traffic behavior configured using the ioam enable sampling-rate sampling-rate command (sampling ratio not set to 1) is applied to the interface, the sFlow or NetStream sampling ratio is that specified by the ioam enable sampling-rate sampling-rate command. If a traffic policy containing the traffic behavior configured using the ioam enable sampling-rate sampling-rate command (sampling ratio not set to 1) is applied on an interface and then the sFlow or NetStream sampling ratio is configured on the interface, the IOAM sampling ratio is the sFlow or NetStream sampling ratio.

  • When the switch collects and copies packets using the IOAM function, only the first 128 bytes of the payload in the original packet are captured.

  • The ingress node adds the reserved VLAN dedicated to a main interface to the IOAM packets arriving at the main interface, and sends the IOAM packets to an external analyzer.

  • Differentiated scheduling for elephant and mice flows in lossless queues and IOAM are mutually exclusive.
  • In V200R005C10 and earlier versions, when the outbound interface of the route from the egress node to the analyzer is a Layer 3 sub-interface, IOAM packets cannot be sent to the analyzer.
Translation
Download
Updated: 2019-04-20

Document ID: EDOC1100075365

Views: 40041

Downloads: 127

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