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).
Measurement Model

Measurement Model

iPCA measures network performance based on IP FPM. IP FPM can directly collect service flow statistics on the network, and obtain the performance indexes such as packet loss rate, number of lost packets, and delay.

The IP FPM measurement model is a universal model that directly measures packet loss rate and delay for service flows. As shown in Figure 16-1, the measurement model includes target flow, transit network, and measurement system.

The measurement system covers three roles: Target Logical Port (TLP), Data Collecting Point (DCP), and Measurement Control Point (MCP).

Figure 16-1 IP FPM model

Target Flow

Service packets on a network are the targets of IP FPM measurement. These service packets form target flows. IP FPM measures lost packets and delay in the target flows passing a network.

A target flow must be specified before measurement starts. Table 16-1 lists the IP packet fields in target flows. You can specify one field or a combination of multiple fields to determine a target flow. If you specify a few fields, the range of target flow is large. To make the statistics accurate, specify more fields.

Table 16-1 Fields defining target flows

Field

Description

Source IP address

Source IP address (or source IP address segment) of a target flow, located in the IP packet header.

Destination IP address

Destination IP address (or destination IP address segment) of a target flow, located in the IP packet header.

Protocol type

Protocol carried by a target flow, for example, ICMP, TCP, and UDP, located in the IP packet header.

Source port number

Layer 4 source port number of a target flow, located in the TCP or UDP packet header.

Destination port number

Layer 4 destination port number of a target flow, located in the TCP or UDP packet header.

DSCP

DSCP value in a target flow, located in the IP packet header.

VNI

VXLAN Network Identifier (VNI) in a target flow, located in the VXLAN packet header.

Transit Network

A transit network does not generate or terminate target flows. A transit network is a Layer 2 or Layer 3 network (IP or MPLS network), or a Layer 2 and Layer 3 mixed network. IP FPM requires that every node on the transit network have reachable routes to each other.

Measurement System

The measurement system is a logical concept. It is responsible for counting the received and sent packets on the ingress and egress of a network, and providing network performance indicators. The measurement system includes TLP, DCP, and MCP, as shown in Figure 16-2.

Figure 16-2 Components in the measurement system
  • TLP

    TLPs are the observing points distributed on network edge. They are the interfaces on network devices. For a target flow, the upstream TLP (also called in-point TLP or ingress TLP) receives packets and colors the specified bits in packets; the downstream TLP (also called out-point TLP or egress TLP) removes the color flags from the specified bits and sends packets out.

    TLPs execute measurement activities and generate statistics data (such as number of sent and received packets and time stamps).

  • DCP

    DCPs are the statistics aggregation points. They are network devices, for example, switches. A DCP manages and controls TLPs, aggregates the statistics data collected by TLPs, and sends the data to MCP.

  • MCP

    The MCP is the controller in the measurement system. It is also a network device, for example, a high-performance switch or an independent device in the network management center. The MCP receives statistics data sent from DCPs, summarizes and calculates statistics, and reports calculation results to user terminals or NMS. A network device can function as both an MCP and a DCP.

A network needs to transmit different types of service flows, such as voice flows and video flows. Generally, these flows pass the same devices. When the measurement system collects statistics for different service flows, the statistics on different target flows must be separated from each other. The concept of measurement instance is used to separate target flows. You can consider each measurement instance as a measurement system. The DCP and MCP collect statistics on the same target flow through the same measurement instance.

Translation
Download
Updated: 2019-04-20

Document ID: EDOC1100075365

Views: 33905

Downloads: 123

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