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 12800 and 12800E V200R005C10

This document describes the configurations of Network Management and Monitoring, including SNMP, RMON, LLDP, NQA, Service Diagnosis, Mirroring, Packet Capture, sFlow, and NETCONF.
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 Transit Node

Configuring Transit Node

Context

In the IOAM system, OAM information or actions about the local hop need to be configured on the ingress, transit, and egress nodes. This section describes how to configure the transit node.

NOTE:

The CE12800E (configured with FD-X series cards) can function only as a transit node but not an ingress or egress node. For details about how to configure an ingress and egress nodes, see "IOAM Configuration" in Configuration > Network Management and Monitoring Configuration Guide in the CloudEngine 8800, 7800, 6800, and 5800 series switches product documentation.

The same value of header header-value must be configured on the ingress, transit, and egress nodes. Otherwise, IOAM traffic fails to be forwarded.

Procedure

  1. Run system-view

    The system view is displayed.

  2. Run ioam [ header header-value ] [ device-id { number | ip-address } ] add-metadata

    OAM information about the local hop is configured.

  3. (Optional) Configure nodes or interfaces to drop IOAM packets.

    On a node or an interface that does not need to transmit IOAM packets, you can configure the node or interface to drop IOAM packets to prevent IOAM packets from being incorrectly forwarded or flooded.

    • Configure all interfaces to drop outgoing IOAM packets.

      Run the ioam [ header header-value ] [ device-id { number | ip-address } ] drop command to configure all interfaces to drop IOAM packets.

    • Configure a specified interface to drop outgoing IOAM packets.

      1. Run the interface interface-type interface-number command to enter the interface view.
      2. Run the ioam [ header header-value ] drop command to configure the interface to drop outgoing IOAM packets.
      3. Run the quit command to quit the system view.

  4. Run commit

    The configuration is committed.

Translation
Download
Updated: 2019-04-20

Document ID: EDOC1100075344

Views: 21003

Downloads: 23

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