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).
Format Versions of NetStream Packets

Format Versions of NetStream Packets

The format versions of NetStream packets include V5, V8, IPFIX and V9. NetStream packets of all formats are transmitted using UDP. Each data packet contains a header and one or several stream records.

Original streams can be exported in V5, IPFIX or V9 format. Aggregated streams can be exported in V8, IPFIX or V9 format.

Different from V5 or V8, the V9 and IPFIX format is used in a template, which allows traffic statistics to be exported more flexibly, new fields to be used easily, and new records to be generated easily.

Figure 3-3 shows the structure of a NetStream packet.

Figure 3-3 NetStream packet

Figure 3-4 Header of a NetStream packet exported in V5 format

Table 3-3 describes fields in the header of the NetStream packet exported in V5 format.

Table 3-3 Description of fields in the header of the NetStream packet exported in V5 format

Field

Description

version

Version number of the format in which NetStream packets are exported. Value 0x05 indicates the V5 format.

count

Number of stream records in the existing NetStream packet. The value ranges from 1 to 30.

system up time

Period (in milliseconds) from the time the system is booted to the time a NetStream packet was generated.

unix_secs

Integer number of seconds elapsed from 00:00:00, January 1st, 1970 to the time a NetStream packet was generated.

unix_nsecs

Integer number of nanoseconds equal to the time the packet was generated minus unix_secs.

flow sequence

Sequence number of an exported stream record:

In the first NetStream packet, the value is 0, and the count of streams in the NetStream packet is c1 (count = c1).

In the second NetStream packet, the value is c1, and the count of streams in the NetStream packet is c2 (count = c2).

In the third NetStream packet, the value is c2 + c1.

...

In the n - 1 NetStream packet, the value is fs(n - 1), and the count of streams in the NetStream packet is c(n - 1).

In the Nth NetStream packet, the value is fs(n - 1) + c(n - 1).

You can check whether a NetStream packet is dropped based on the flow sequence value.

When the stream sequence number overflows, NetStream packets transmission continues.

engine type

Type of the stream switching engine, which is the device type.

engine ID

ID of a slot in which the switching engine resides, which is the slot ID of the NetStream board.

reserved

Reserved field, which is all 0s.

Information Carried in the NetStream Packet Exported in V5 Format

Information carried in an NetStream packet exported in V5 format is marked dark as shown in Figure 3-5.

Figure 3-5 V5 format information

NOTE:

The system constructs two types of UDP packets based on statistics about both incoming and outgoing traffic. These two types of UDP packets are exported in V5 format but carry different flag bits (incoming and outgoing).

Header of a NetStream Packet Exported in V8 Format

Figure 3-6 Header of a NetStream packet exported in V8 format

Table 3-4 describes fields in the header of the NetStream packet exported in V8 format.

Table 3-4 Description of fields in the header of the NetStream packet exported in V8 format

Field

Description

version

Version number of the format in which NetStream packets are exported. Value 0x08 indicates the V8 format.

count

Number of streams in the existing NetStream packet, not the number of streams in all NetStream packets.

system up time

Period (in milliseconds) from the time the system is booted to the time a NetStream packet was generated.

unix_secs

Integer number of seconds elapsed from 00:00:00, January 1st, 1970 to the time a NetStream packet was generated.

unix_nsecs

Integer number of nanoseconds equal to the time the packet was generated minus unix_secs.

flow sequence

Sequence number of an exported stream record:

In the first NetStream packet, the value is 0, and the count of streams in the NetStream packet is c1 (count = c1).

In the second NetStream packet, the value is c1, and the count of streams in the NetStream packet is c2 (count = c2).

In the third NetStream packet, the value is c2 + c1.

...

In the n - 1 NetStream packet, the value is fs(n - 1), and the count of streams in the NetStream packet is c(n - 1).

In the Nth NetStream packet, the value is fs(n - -1) + c(n - -1).

You can check whether a NetStream packet is dropped based on the flow sequence value.

When the stream sequence number overflows, NetStream packets transmission continues.

engine type

Type of the stream switching engine, which is the device type.

engine ID

ID of the slot in which the switching engine resides, which is the slot ID of the NetStream board.

aggregation

Aggregation mode:

01: as

02: protocol-port

03: source-prefix

04: destination-prefix

05: prefix

09: as-tos

0a: protocol-port-tos

0b: source-prefix-tos

0c: destination-prefix-tos

0d: prefix-tos

aggregation version

Version number of the format in which the aggregated NetStream packet is exported. The value is 0x02.

sampling Interval

Sampling interval. The value is 0.

reserved

Reserved field, which is all 0s.

Information Carried in the NetStream Packet Exported in V8 Format

Starting from V8, original streams can be aggregated on an NDE. Aggregation refers to the action of classifying and combining original streams into one stream based on specified rules. Aggregated streams can be transmitted with less network bandwidth. In V5 or V8, the stream aggregation is implemented on an NDC.

  • Aggregation based on the AS

    Figure 3-7 Schematic diagram for flow aggregation based on the AS

    This aggregation mode is primarily used to collect statistics about packets and bytes exchanged between devices in two ASs. Based on traffic statistics on different ASs, carriers can implement accounting schemes.

    • If an original AS is used as a source AS, the source AS number identifies the AS to which the source address belongs.
    • If a peer AS is used as a source AS, the source AS number identifies an AS along an AS path.
    • If the source address belongs to a local AS or if the AS number cannot be obtained from the routing table, the source AS number is set to 0.

    The destination AS numbers are as follows:

    • If the destination AS is the original AS, the destination AS number is the AS to which the destination address belongs.
    • If the destination AS is the peer AS, the destination AS identifies an AS along an AS path.
    • If the destination address belongs to the local AS or if the AS number cannot be obtained from the routing table, the destination AS number is set to 0.

    The source and destination AS numbers are used to perform AS-based flow aggregation.

  • Aggregation based on the protocol type

    Figure 3-8 Schematic diagram for flow aggregation based on the protocol type

    In this mode, packets of the same protocol type at the transmission layer (TCP and UDP), and with the same source and destination port numbers are aggregated. If the Protocol Type field is 6, the protocol is TCP. If the Protocol Type field is 17, that the protocol is UDP.

    For non-TCP or non-UDP packets, the source port number is 0. For ICMP packets, the destination port number is determined by the Type and Code fields in the packets.

    For non-TCP or non-UDP packets, the destination port number is 0.

  • Aggregation based on the destination IP address prefix

    Figure 3-9 Schematic diagram for flow aggregation based on the destination IP address prefix

    In this mode, packets with the same destination IP address prefix are aggregated.

  • Aggregation based on the source IP address prefix

    Figure 3-10 Schematic diagram for flow aggregation based on the source IP address prefix

  • Aggregation based on source and destination IP address prefixes

    Figure 3-11 Schematic diagram for flow aggregation based on source and destination IP address prefixes

    In this mode, packets with the same source IP address prefix and the destination IP address prefix are aggregated.

  • Aggregation based on ToS + AS

    Figure 3-12 Schematic diagram for flow aggregation based on ToS + AS

    Type of service (ToS) is a field in the IP packet header used to set a packet priority value.

  • Aggregation based on ToS + protocol type

    Figure 3-13 Schematic diagram for flow aggregation based on ToS + protocol type

  • Aggregation based on the IP address prefix + ToS + protocol type

    Figure 3-14 Schematic diagram for flow aggregation based on the IP address prefix + ToS + protocol type

  • Aggregation based on ToS + source IP address prefix

    Figure 3-15 Schematic diagram for flow aggregation based on ToS + source IP address prefix

  • Aggregation based on ToS + destination IP address prefix

    Figure 3-16 Schematic diagram for flow aggregation based on ToS + destination IP address prefix

  • Aggregation based on ToS + IP address prefix

    Figure 3-17 Schematic diagram for flow aggregation based on ToS + IP address prefix

Header of a NetStream Packet Exported in V9 Format

Figure 3-18 Header of the NetStream packet exported in V9 format

Table 3-5 describes fields in the header of the NetStream packet exported in V9 format.

Table 3-5 Description of fields in the header of the NetStream packet exported in V9 format

Field

Description

version

Version number of the format in which NetStream packets are exported. Value 0x09 indicates the V9 format.

count

Number of FlowSet records (including records in the template FlowSet and data FlowSet) exported in a NetStream packet.

system up time

Period (in milliseconds) from the time the system is booted to the time a NetStream packet was generated.

unix_secs

Integer number of seconds elapsed from 00:00:00, January 1st, 1970 to the time a NetStream packet was generated.

package sequence

Sequence number of an exported packet.

You can check whether a NetStream packet is dropped based on the flow sequence value.

NOTE:

The meaning of this field in the header of the NetStream packet exported in V9 is different from that in V5 or V8 format. In V5 and V8, this field indicates the sequence number of all flows.

source id

Source ID used to uniquely identify a device exporting packets. The value occupies 4 bytes.

The Source ID field is equal to the Engine Type and Engine ID fields in the header of a NetStream packet exported in V5 or V8 format. The Source ID field value can be defined.

Terms Related to the V9 Format

  • Template FlowSet

    Describes stream information in an exported NetStream packet. A NetStream-enabled device encapsulates template information in the NetStream packet and sends the packet to an NDC to establish a convention. Based on the convention, the device and the NDC parse information. A template FlowSet, as the V9 format core, consists of multiple template records. Upon receipt of the template sent by the device, the NDC can parse stream information carried in the exported NetStream packet without a parsing format pre-defined. This greatly increases the flexibility and scalability of NetStream records and facilitates the development of the third party's software and the NetStream function.

  • Template record

    Corresponds to each data record in an exported NetStream packet. Stream information in a data record is parsed based on a template record.

  • Template ID

    Identifies a template. Each template has a specific ID. A data record contains a template ID used to select a template.

  • Data FlowSet

    Indicates a combination of one or multiple data records.

  • Data record

    Corresponds to one NetStream record.

NetStream Packet Exported in V9 Format

In Figure 3-19, a NetStream packet exported in V9 format consists of a packet header, template FlowSets, and data FlowSets.

Figure 3-19 Schematic diagram for an NetStream packet exported in V9 format

Both a template FlowSet and a data FlowSet contain template IDs, but these FlowSets are independent of each other. Upon receipt of a NetStream packet, an NDC parses data records in a data FlowSet and obtains a template ID. Although the NDC also obtains a template ID carried in a template FlowSet, the NDC can only use this template ID to parse the following exported NetStream packets.

Exported NetStream packets may contain one of the following combinations of template FlowSets and data FlowSets:

  • Contain both template and data FlowSets. An NDC separately processes template FlowSets and data FlowSets. The NDC obtains template information carried in each template FlowSet and uses the template to parse data records carried in data FlowSets of subsequent NetStream packets.

  • Only contain data FlowSets. If the template ID is predefined, a NetStream-enabled device exports a NetStream packet only carrying the data FlowSet to the NDC.

  • Only contain template FlowSets. Template and data FlowSets are packed into one exported NetStream packet to better use network bandwidth. After templates are configured on a device and the device is restarted, the device sends all templates to NDC immediately. In this situation, each exported NetStream packet only contains a template FlowSet. When a template expires after a specified period of time elapses, the NDC deletes the template. To allow the NDC to use available templates, a device periodically transmits a template FlowSet to the NDC even if no data FlowSet is generated.

Template FlowSet Format

Figure 3-20 shows the template FlowSet format.

Figure 3-20 Template FlowSet format

In this example, a template FlowSet contains two template records. Table 3-6 describes the meaning of each field.

Table 3-6 Template FlowSet fields and their meanings

Field

Description

FlowSet ID

ID of a template FlowSet. The FlowSet ID value can be:
  • For a template FlowSet: 0 to 255
  • For a data FlowSet: 256 to 511
An NDC uses FlowSet IDs to distinguish template records from data records in an exported NetStream packet.

Length

Total length of the template FlowSet.

The Length field contents are represented in the type-length-value (TLV) format, and its value is equal to the sum of the following lengths:
  • Lengths of the FlowSet ID field and the Length field itself
  • Length of each template record carried in the template FlowSet

A single template FlowSet contains multiple template IDs. The length value helps determine the position of the next template or data FlowSet record.

Template ID

ID of a template record in the template FlowSet.

A template record is mapped to a specific type of NetStream data to be exported. The template ID is unique on a device. A template ID is equal to a data FLowSet ID and ranges from 256 to 511.

Field Count

Number of fields in a template record.

A template FlowSet includes one or more template records. The Field Count value helps determine the end of an existing template record and the start of the next one.

Field Type

Type of data in a template record.

The value can be defined. For example, if statistics are collected based on the destination IP address, protocol type, ToS, and MPLS label, a field type is used to define each of these four attributes.

Field Length

Length (in bytes) of a defined field type.

For example, if the field type is set to a destination IP address, the field length value is 4 bytes.

Data FlowSet Format

Figure 3-21 shows the packet format of the data FlowSet.

Figure 3-21 Data FlowSet format

In this example, a data FlowSet contains two data records. The data FlowSet ID is used to parse the two data records. Table 3-7 describes the fields carried in the data FlowSet.

Table 3-7 Data FlowSet fields and meanings

Field

Description

flowset ID = template ID

ID of a data FlowSet.

A data FlowSet ID is equal to a template ID in a template FlowSet. An NDC and a display application use a FlowSet ID to map to the type and length of a field.

length

Length of a data FlowSet.

The Length field contents are represented in the TLV format, and its value is equal to the sum of the following lengths:
  • Lengths of the FlowSet ID field and the length field itself
  • Length of each data record carried in the data FlowSet
  • Length of padding bits

record n - field n

Field value in each data record of the data FlowSet.

padding

A 32–bit field at the end of the data FlowSet.

Note that the length field includes the length of padding bits.

Relationship Between a Data Stream Format and the V9 Template Format

Figure 3-22 shows the relationship between the data stream format and the V9 template format.

Figure 3-22 Relationship between the data stream format and the V9 template format

Header of a NetStream Packet Exported in IPFIX Format

Figure 3-23 shows the header of a netStream packet exported in IPFIX format.

Figure 3-23 Header of a NetStream Packet Exported in IPFIX Format

Table 3-8 describes fields in the header of the NetStream packet exported in IPFIX format.

Table 3-8 IPFIX Format fields and meanings

Fields

Description

Version Number

Version number of the format in which NetStream packets are exported.

Length

The packet length of the Header of a NetStream Packet Exported in IPFIX Format, including message header, in bytes.

Export Time

The time when the flow record sends time from Exporter, in seconds. It is UTC time and record from January 1st.1970.

Sequence Number

The Sequence Number of the exporting packets. The value is cumulated. Therefore, the value can be used to check whether the packet loss occurred.

Observation Domain ID

Indicates the Observation Domain ID. It is a unique number to identify a flow sending from a router.

Translation
Download
Updated: 2019-01-02

Document ID: EDOC1100055478

Views: 5249

Downloads: 2

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