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

NE20E-S2 V800R010C10SPC500 Feature Description - System Monitor 01

This is NE20E-S2 V800R010C10SPC500 Feature Description - 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).
Export of a Flow

Export of a Flow

  • Export of original flows

    Information in aging original flows is collected and then encapsulated into UDP packets to be sent to an NDC. The NDC obtains detailed information about each original flow and process these flow records flexibly. This, however, increases network bandwidth and CPU usage. In addition, to store these flow records, a great amount of memory is used, and the overhead of the NE20E is increased.

  • Export of aggregated flows

    After information about aging original flows is collected, original flows are classified, combined, and constructed into aggregated flows based on specified rules. When the aggregation timer in the system expires, aggregated flows are exported to the NDC as UDP packets. Aggregation helps original flows be transmitted with less network bandwidth, CPU usage, and storage space. The NE20E supports aggregation modes listed in Table 3-2. A device aggregates flows with the same attributes into one flow and then generates one record about the aggregated flow.

    Table 3-2 List of aggregation modes

    Aggregation Mode

    Description

    as Indicates the autonomous system (AS) aggregation, which aggregates flows with the same source AS number, destination AS number, inbound interface index, and outbound interface index.
    as-tos Indicates the AS-ToS aggregation, which aggregates flows with the same source AS number, destination AS number, inbound interface index, outbound interface index, and type of service (ToS).
    bgp-nexthop-tos Indicates the BGP-nexthop-ToS aggregation, which aggregates flows with the same Border Gateway Protocol (BGP) next hop, source AS number, destination AS number, inbound interface index, and outbound interface index.
    destination-prefix Indicates the destination-prefix aggregation, which aggregates flows with the same destination AS number, destination mask length, destination prefix, and outbound interface index.
    destination-prefix-tos Indicates the destination-prefix-ToS aggregation, which aggregates flows with the same destination AS number, destination mask length, destination prefix, outbound interface index and ToS.
    index-tos Indicates the index-ToS aggregation, which aggregates flows with the same inbound interface index, outbound interface index, and ToS.
    mpls-label Indicates the MPLS label aggregation, which aggregates flows with the same first layer label, second layer label, third layer label, TopLabelIpAddress, stack bottom symbol of the first layer label, and the EXP value of the first layer label.
    prefix Indicates the prefix aggregation, which aggregates flows with the same source AS number, destination AS number, source mask length, destination mask length, source prefix, destination prefix, inbound interface index, and outbound interface index.
    prefix-tos Indicates the prefix-ToS aggregation, which aggregates flows with the same source AS number, destination AS number, source mask length, destination mask length, source prefix, destination prefix, inbound interface index, outbound interface index, and ToS.
    protocol-port Indicates the protocol-port aggregation, which aggregates flows with the same protocol number, source port, and destination port.
    protocol-port-tos Indicates the protocol-port-ToS aggregation, which aggregates flows with the same protocol number, source port, destination port, ToS, inbound interface index, and outbound interface index.
    source-prefix Indicates the source-prefix aggregation, which aggregates flows with the same source AS number, source mask length, source prefix, and inbound interface index.
    source-prefix-tos Indicates the source-prefix-ToS aggregation, which aggregates flows with the same source AS number, source mask length, source prefix, ToS, and inbound interface index.
    source-index-tos Indicates the source interface index-ToS aggregation, which aggregates flows with the same source interface index, ToS and BGP next hop.
    vlan-id Indicates the VLAN-ID aggregation, which aggregates flows with the same virtual local area network (VLAN) ID and inbound interface index.
    bgp-community Indicates the BGP community aggregation, which aggregates flows with the same inbound and outbound interface indexes and BGP community.
    vni-sip-dip Indicates the VNI aggregation, which aggregates flows with the same VNI ID and the same source and destination IP addresses of tenants.
  • Export to a server

    NetStream packets can be exported to a specified server. The following server addresses can be used:

    • A global server address specified in the system view for original and aggregated flows
    • A server address specified in the aggregation view
    • A server address specified in a template that is bound to an interface

    For aggregated flows, a server address can be specified in the system, slot, or aggregation view. After sampling packets, including original flows, are aggregated, the aggregated flows are output to the same server.

    Multiple service addresses of interfaces can be specified in a monitor template so that sampling packets of original flows can be exported to different servers. Packets can be output to specified interfaces, which helps filter out unnecessary packets and improve flexibility.

    For original flows, server addresses can be specified in the system, slot, and monitor template view. The server addresses configured in the system view, and monitor template are prioritized in ascending order. If multiple server addresses are configured, the address with the highest priority takes effect.

    For aggregated flows, server addresses can be specified in the system and aggregation view. The server address configured in the aggregation view takes precedence over that configured in the system view. If server addresses are configured in both views, the address configured in the aggregation view takes effect.

  • Export of flexible flows

    NetStream supports 17 aggregation modes. For each aggregation mode, original flows are classified and combined to generate aggregated flow information and are aged and exported to the server based on fixed rules. Flexible customization is not supported. Flexible flow packets provide user-defined templates for users to customize matching and collected fields as required. The user-defined template improves traffic analysis accuracy and reduces network bandwidth occupation, CPU usage, and storage space usage.

Translation
Download
Updated: 2019-01-02

Document ID: EDOC1100055478

Views: 5201

Downloads: 2

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