udp-port port-number: Specifies a UDP port for the collector to communicate with the analyzer. The value range is 1024 to 65535, and the default is 53312. To allow the collector report the data to the analyzer, make sure the specified value is the same as that configured on the analyzer by using the protocol udp-port command.

vpn-instance vpn-instance-name: Specifies an MPLS L3VPN instance by its name, a case-sensitive string of 1 to 31 characters. To specify an analyzer on the public network, do not specify this option.

Usage guidelines

A collector instance must be bound to an analyzer so that the collector can send instance-specific data to the analyzer.

The binding between the analyzer and the collector is used as follows:

1. The collector encapsulates the data collected from MPs into packets, uses the analyzer ID bound to a collector instance as the destination IPv4 address, and sends the packets to the analyzer.

2. The analyzer compares the analyzer ID in the packets with its own ID.

¡ If a match is found, the analyzer accepts the packets and summarizes the data in the packets.

¡ If no match is found, the analyzer identifies the packets illegal and discards them.

For the successful communication, make sure the specified analyzer ID meets the following requirements:

· The analyzer ID and a collector can reach each other.

· The analyzer ID bound to a collector instance must be the same as the analyzer ID configured on an analyzer by using the analyzer id command.

You can bind an analyzer to a collector instance or a specific collector.

· An analyzer specified in collector view is bound to all collector instances.

· An analyzer specified in collector instance view is bound to the specific collector instance.

The analyzer ID in collector instance view takes precedence over that in collector view. If no analyzer ID is specified in collector instance view, the analyzer ID in collector view applies.

A collector and a collector instance can be bound to only one analyzer. If you execute this command multiple times in the same view, the most recent configuration takes effect.

Examples

# Bind all collector instances to the analyzer with ID 10.1.1.1.

<Sysname> system-view

[Sysname] inqa collector

[Sysname-inqa-collector] analyzer 10.1.1.1

# Bind collector instance 1 to the analyzer with ID 11.1.1.1.

<Sysname> system-view

[Sysname] inqa collector

[Sysname-inqa-collector] instance 1

[Sysname-inqa-collector-instance-1] analyzer 11.1.1.1

collector id

Use collector id to specify a collector ID.

Use undo collector id to restore the default.

Syntax

collector id collector-id

undo collector id

Default

No collector ID is specified.

Views

Collector view

Predefined user roles

network-admin

mdc-admin

Parameters

collector-id: Specifies a collector ID in dotted decimal format, for example, 10.1.1.1. The collector ID must be an IPv4 address that already exists on the collector.

Usage guidelines

The collector ID is used for communication between the analyzer and collector as follows:

1. The collector encapsulates the data collected from MPs into packets, uses its ID as the source IPv4 address, and sends the packets to the analyzer.

2. The analyzer compares the collector ID in the packets with collector IDs bound to analyzer instances.

¡ If a match is found, the analyzer accepts the packets and summarizes the data in the packets.

¡ If no match is found, the analyzer identifies the packet illegal and discards them.

For the successful communication, make sure the specified collector ID meets the following requirements:

· The ID must be globally unique. As a best practice, configure the Router ID of the device as the collector ID.

· The specified collector ID must be the same as the collector ID bound to an analyzer instance on the analyzer.

You can execute the collector command on the analyzer to bind the specified collector ID to an analyzer instance.

· The collector ID and the analyzer can reach each other.

Examples

# Specify 10.1.1.1 as the collector ID.

<Sysname> system-view

[Sysname] inqa collector

[Sysname-inqa-collector] collector id 10.1.1.1

delay-measure enable continual

Use delay-measure enable continual to enable continual latency measurement for a collector instance.

Use undo delay-measure enable continual to disable continual latency measurement for a collector instance.

Syntax

delay-measure enable continual

undo delay-measure enable continual

Default

The continual latency measurement is disabled.

Views

Collector instance view

Predefined user roles

network-admin

mdc-admin

Usage guidelines

Use delay-measure enable continual to enable continual latency measurement for a collector instance. Once started, it does not stop unless you execute the undo delay-measure enable continual command to disable it manually.

For a collector instance, the fixed duration and continual latency measurements cannot be both enabled.

Examples

# Enable continual latency measurement for collector instance 1.

<Sysname> system-view

[Sysname] inqa collector

[Sysname-inqa-collector] instance 1

[Sysname-inqa-collector-instance-1] delay-measure enable continual

Related commands

delay-measure enable duration

Use delay-measure enable duration to enable the fixed duration latency measurement for a collector instance.

Use undo delay-measure enable duration to disable the fixed duration latency measurement for a collector instance.

Syntax

delay-measure enable duration [ duration ]

undo delay-measure enable duration

Default

The fixed duration latency measurement is disabled.

Views

Collector instance view

Predefined user roles

network-admin

mdc-admin

Parameters

duration: Specifies the number of minutes for which the measurement lasts. The values can be 5, 10, 15, and 30, and the default is 10.

Usage guidelines

iNQA measures the latency in the specified time period. It is helpful when you want to measure the network performance in a time period or to accurately locate the fault points for latency.

This command will not be saved to the configuration file. The fixed duration latency measurement cannot survive the master/subordinate, active/standby switchover, or device reboot. Configure this feature again in such circumstances as needed.

For a collector instance, the fixed duration and continual latency measurements cannot be both enabled.

Examples

# Run the latency measurement for 30 minutes for collector instance 1.

<Sysname> system-view

[Sysname] inqa collector

[Sysname-inqa-collector] instance 1

[Sysname-inqa-collector-instance-1] delay-measure enable duration 30

Related commands

delay-measure enable continual

description

Use description to configure a description for a collector instance.

Use undo description to restore the default.

Syntax

description text

undo description

Default

A collector instance does not have a description.

Views

Collector instance view

Predefined user roles

network-admin

mdc-admin

Parameters

text: Specifies a description, a case-sensitive string of 1 to 64 characters.

Usage guidelines

A description allows easy identification of a collector instance.

Examples

# Set the description to AtoB for collector instance 1.

<Sysname> system-view

[Sysname] inqa collector

[Sysname-inqa-collector] instance 1

[Sysname-inqa-collector-instance-1] description AtoB

display inqa collector

Use display inqa collector to display the collector configuration.

Syntax

display inqa collector

Views

Any view

Predefined user roles

network-admin

network-operator

mdc-admin

mdc-operator

Examples

# Display the collector configuration.

<Sysname> display inqa collector

Collector ID : 10.1.1.1

Loss-measure flag : --

Delay-measure flag : --

Analyzer ID : 10.2.2.2

Analyzer UDP-port : 53312

VPN-instance-name : --

Current instance count : 2

Table 1 Command output

Field	Description
Collector ID	Collector ID.
Loss-measure flag	ToS field bit to flag packet loss measurement: · 5—Uses the bit 5 as the flag bit. · 6—Uses the bit 6 as the flag bit. · 7—Uses the bit 7 as the flag bit.
Delay-measure flag	ToS field bit to flag latency measurement: · 5—Uses bit 5 as the flag bit. · 6—Uses bit 6 as the flag bit. · 7—Uses bit 7 as the flag bit.
Analyzer ID	ID of the analyzer bound to the collector.
Analyzer UDP-port	UDP port number for the communication between the analyzer and collector.
VPN-instance-name	Name of the VPN instance to which the analyzer belongs.
Current instance count	Total number of collector instances.

‌

display inqa collector instance

Use display inqa collector instance to display the collector instance configuration.

Syntax

display inqa collector instance { instance-id | all }

Views

Any view

Predefined user roles

network-admin

network-operator

mdc-admin

mdc-operator

Parameters

instance-id: Specifies a collector instance ID in the range of 1 to 8355838.

all: Displays the configuration of all collector instances.

Examples

# Display the configuration of collector instance 1.

<Sysname> display inqa collector instance 1

Instance ID : 1

Loss-measure status : Enabled

Loss-measure duration : --

Delay-measure status : Enabled

Delay-measure duration : --

Description : AtoB

Analyzer ID : 10.2.2.2

Analyzer UDP-port : 53312

VPN-instance-name : --

Interval : 10 sec

Flow configuration:

flow bidirection source-ip 10.1.1.1 destination-ip 10.2.2.2 protocol udp source-port 1025

MP configuration:

mp 100 in-point inbound, XGE1/0/1

mp 200 in-point inbound, XGE1/0/2

# Display the configuration of all collector instances.

<Sysname> display inqa collector instance all

Instance ID : 1

Loss-measure status : Enabled

Loss-measure duration : --

Delay-measure status : Enabled

Delay-measure duration : --

Description : AtoB

Analyzer ID : 10.2.2.2

Analyzer UDP-port : 53312

VPN-instance-name : --

Interval : 10 sec

Flow configuration:

flow bidirection source-ip 10.1.1.1 destination-ip 10.2.2.2 protocol udp source-port 1025

MP configuration:

mp 100 in-point inbound, XGE1/0/1

mp 200 in-point inbound, XGE1/0/2

Instance ID : 2

Loss-measure status : Enabled

Loss-measure duration : --

Delay-measure status : Enabled

Delay-measure duration : --

Description : BtoA

Analyzer ID : 10.2.2.3

Analyzer UDP-port : 53312

VPN-instance-name : --

Interval : 10 sec

Flow configuration:

flow forward source-ip 10.1.1.2 destination-ip 10.2.2.3 protocol udp source-port 1025

MP configuration:

mp 300 in-point inbound, XGE1/0/3

mp 400 mid-point outbound, XGE1/0/4

Table 2 Command output

Field	Description
Instance ID	Collector instance ID.
Loss-measure status	Packet loss measurement status of the collector instance: · Enabled. · Disabled.
Loss-measure duration	Period of the fixed duration packet loss measurement.
Delay-measure status	Latency measurement status of the collector instance: · Enabled. · Disabled.
Delay-measure duration	Period of the fixed duration latency measurement.
Description	Description for the collector instance.
Analyzer ID	ID of the analyzer bound to the collector instance.
Analyzer UDP-port	UDP port number for the communication between the analyzer and collector
VPN-instance-name	Name of the VPN instance to which the analyzer belongs.
Interval	Measurement interval for the collector instance.
Flow configuration	Configuration of the flow monitored by the collector instance.
MP configuration	MP configuration.

‌

flag

Use flag to specify a ToS field bit to flag packet loss measurement.

Use undo flag to restore the default.

Syntax

flag loss-measure tos-bit tos-bit

undo flag loss-measure

Default

No ToS field bit is specified to flag packet loss measurement.

Views

Collector view

Predefined user roles

network-admin

mdc-admin

Parameters

tos-bit tos-bit: Specifies a ToS field bit. The value range is 5 to 7.

Usage guidelines

iNQA uses ToS field bits 5 to 7 in the IPv4 packet header as the flag bit. By setting the flag bit value to 1 or 0 alternately at intervals, you can distinguish a target flow from unintended traffic flows.

The ToS field consist of a 6-bit (bits 0 to 5) DSCP filed and a 2-bit (bits 6 and 7) ECN field. If bit 5 is used as the flag bit, to avoid inaccurate packet loss statistics, do not use it for DSCP purposes.

To modify the flag bit for a collector instance that is already enabled, you must disable the collector instance first.

Examples

# Specify ToS field bit 5 as the flag bit.

<Sysname> system-view

[Sysname] inqa collector

[Sysname-inqa-collector] flag loss-measure tos-bit 5

flag delay-measure

Use flag delay-measure to specify a ToS field bit to flag latency measurement.

Use undo flag delay-measure to restore the default.

Syntax

flag delay-measure tos-bit tos-bit

undo flag delay-measure

Default

No ToS field bit is specified to flag latency measurement.

Views

Collector view

Predefined user roles

network-admin

mdc-admin

Parameters

tos-bit tos-bit: Specifies a ToS field bit. The value range is 5 to 7.

Usage guidelines

iNQA uses ToS field bits 6 to 7 in the IPv4 packet header as the flag bit. By setting the flag bit value to 1 at intervals, you can distinguish a target flow from unintended traffic flows.

The ToS field consist of a 6-bit (bits 0 to 5) DSCP filed and a 2-bit (bits 6 and 7) ECN field.

In the current software version, you can specify only ToS field bit 6 or 7 as the latency flag bit.

To edit the latency flag bit for a collector instance on which the latency measurement is already enabled, you must disable the latency measurement for the collector instance first.

For correct latency measurement, follow these restrictions and guidelines:

· You must specify the same ToS field bit as the latency flag bit for all collectors in the same network.

· Do not specify the same ToS field bit as both the latency flag bit and the packet loss flag bit.

Examples

# Specify ToS field bit 6 as the latency flag bit.

<Sysname> system-view

[Sysname] inqa collector

[Sysname-inqa-collector] flag delay-measure tos-bit 6

flow (collector instance view)

Use flow to specify a flow to be monitored by a collector instance.

Use undo flow to remove the flow settings.

Syntax

flow { backward | bidirection | forward } { destination-ip dest-ip-address [ dest-mask-length ] | dscp dscp-value | protocol { { tcp | udp } { destination-port dest-port-number1 [ to dest-port-number2 ] | source-port src-port-number1 [ to src-port-number2 ] } * | protocol-number } | source-ip src-ip-address [ src-mask-length ] } * [ vxlan-transmit | vxlan-hybrid ]

flow { backward | bidirection | forward } ipv6 { destination-ipv6 dest-ipv6-address [ dest-prefix-length ] | dscp dscp-value | protocol { { tcp | udp } { destination-port dest-port-number1 [ to dest-port-number2 ] | source-port src-port-number1 [ to src-port-number2 ] } * | protocol-number } | source-ipv6 src-ipv6-address [ src-prefix-length ] } * [ vxlan-transmit | vxlan-hybrid ]

undo flow { backward | bidirection | forward }

Default

No flow is specified for a collector instance.

Views

Collector instance view

Predefined user roles

network-admin

mdc-admin

Parameters

backward: Specifies a backward flow.

bidirection: Specifies the symmetric bidirectional flows. If you specify this keyword, both the src-ip-address and dest-ip-address arguments are required.

forward: Specifies a forward flow.

destination-ip dest-ip-address: Specifies a destination IPv4 address of the flow, in dotted decimal format. Only the unicast IPv4 addresses are supported.

dest-mask-length: Specifies a mask length for the destination IPv4 address. The value range is 1 to 32, and the default is 32.

dscp dscp-value: Specifies a DSCP value of the flow, in the range of 0 to 63. If bit 5 is used as the flag bit, do not specify this option to avoid inaccurate packet loss statistics.

protocol: Specifies a protocol type of the flow.

· { tcp | udp }: Specifies the TCP or UDP protocol.

¡ destination-port dest-port-number1 [ to dest-port-number2 ]: Specifies a single destination port or a range of destination ports. The value range is 0 to 65535. For a port range, the dest-port-number2 argument must be higher than the dest-port-number1 argument.

¡ source-port src-port-number1 [ to src-port-number2 ]: Specifies a single source port or a range of source ports. The value range is 0 to 65535. For a port range, the src-port-number2 argument must be higher than the src-port-number1 argument.

· protocol-number: Specifies the number of the protocol type. The value range is 0 to 255, excluding 6 (TCP protocol number) and 17 (UDP protocol number).

source-ip src-ip-address: Specifies a source IPv4 address of the flow, in dotted decimal format. Only the unicast IPv4 addresses are supported.

src-mask-length: Specifies a mask length for the source IPv4 address. The value range is 1 to 32, and the default is 32.

ipv6: Specifies an IPv6 flow.

destination-ipv6 dest-ipv6-address: Specifies a destination IPv6 address of the flow, in hexadecimal format. Only the unicast IPv6 addresses are supported.

dest-prefix-length: Specifies a prefix length for the destination IPv6 address. The value range is 1 to 128, and the default is 128.

source-ipv6 src-ipv6-address: Specifies a source IPv6 address of the flow, in hexadecimal format. Only the unicast IPv6 addresses are supported.

src-prefix-length: Specifies a prefix length for the source IPv6 address. The value range is 1 to 128, and the default is 128.

vxlan-transmit: Matches inner IP headers of VXLAN packets. If you do not specify the vxlan-transmit or vxlan-hybrid keyword, iNQA matches outer IP headers of packets.

vxlan-hybrid: Matches outer IP headers of non-VXLAN packets, inner P headers of VXLAN packets, and outer IP headers of VXLAN packets. If a match is found, the packets will be measured by iNQA. After a VXLAN tunnel egress interface receives VXLAN packets, some packets are transmitted in the VXLAN network and some packets are decapsulated to transmit in the IP network. To measure packet loss in the VXLAN tunnel, specify the vxlan-hybrid keyword. If you do not specify the vxlan-transmit or vxlan-hybrid keyword, iNQA matches outer IP headers of packets.

Usage guidelines

The target flows are key elements for iNQA operations. You can specify a flow by using any combination of the following items: protocol type, source IPv4 address, destination IPv4 address, source port number, destination port number, and DSCP value. Using more items defines a more explicit flow and generates more accurate analysis data.

A collector instance can monitor a maximum of two flows. Follow these guidelines when you specify the target flows:

· To monitor only one flow, specify the forward keyword. The collector instance does not support monitoring only a backward flow.

· To monitor two flows:

¡ If the endpoint devices of the two flows are the same, use the bidirection keyword, and specify both the destination IPv4 address and source IPv4 address..

¡ If the endpoint devices of the two flows are not identical, specify a forward flow and then a backward flow. Alternatively, you can create two collector instances, and specify a forward flow in each collector instance.

For the flows to be monitored by different collector instances, the flow attributes must not be identical.

For a forward flow and backward flow monitored by a collector instance, the flow attributes cannot be all identical. If they have the same attributes except the direction, define them as bidirectional flows.

Examples

# Configure collector instance 1 to monitor the forward UDP flow from 10.1.1.1 to 20.1.1.1 with the source port number 1025.

<Sysname> system-view

[Sysname] inqa collector

[Sysname-inqa-collector] instance 1

[Sysname-inqa-collector-instance-1] flow forward source-ip 10.1.1.1 destination-ip 20.1.1.1 protocol udp source-port 1025

# Configure collector instance 2 to monitor the forward flow from 1.1.1.1 to 2.2.2.2 and to monitor the backward TCP flow from 3.3.3.3 to 1.2.3.4 with the destination port number 1024.

<Sysname> system-view

[Sysname] inqa collector

[Sysname-inqa-collector] instance 2

[Sysname-inqa-collector-instance-1] flow forward source-ip 1.1.1.1 destination-ip 2.2.2.2

[Sysname-inqa-collector-instance-1] flow backward source-ip 3.3.3.3 destination-ip 1.2.3.4 protocol tcp destination-port 1024

# Configure collector instance 3 to monitor the bidirectional UDP flows between 10.1.1.1 and 20.1.1.1 with the source port number 1025.

<Sysname> system-view

[Sysname] inqa collector

[Sysname-inqa-collector] instance 3

[Sysname-inqa-collector-instance-3] flow bidirection source-ip 10.1.1.1 destination-ip 20.1.1.1 protocol udp source-port 1025

inqa collector

Use inqa collector to enable the collector functionality and enter its view, or enter the view of an enabled collector.

Use undo inqa collector to disable the collector functionality.

Syntax

inqa collector

undo inqa collector

Default

The collector functionality is disabled.

Views

System view

Predefined user roles

network-admin

mdc-admin

Usage guidelines

The intelligent network quality analyzer (iNQA) operations include the following device roles:

· Collector—Manages measurement points (MPs), collects data from MPs, and reports the data to the analyzer.

· Analyzer—Collects the data from collectors and summarizes the data.

· After you configure this command on a device, the device functions as a collector.

· You can enable the collector and analyzer functionalities on different devices or the same device.

Examples

# Enable the collector functionality and enter its view.

<Sysname> system-view

[Sysname] inqa collector

[Sysname-inqa-collector]

Related commands

collector id

inqa mp

Use inqa mp to bind an MP to an interface.

Use undo inqa mp to unbind an MP from an interface.

Syntax

inqa mp mp-id

undo inqa mp

Default

No interface is bound to an MP.

Views

Ethernet interface view

Aggregate interface view

Predefined user roles

network-admin

mdc-admin

Parameters

mp-id: Specifies an MP ID in the range of 1 to 16777215.

Usage guidelines

An MP can be bound to only one interface, and one interface can be bound to only one MP.

After an interface is bound to an MP, iNQA can count the number of packets passing through the interface.

Examples

# Bind Ten-GigabitEthernet 1/0/1 to MP 100.

<Sysname> system-view

[Sysname] interface ten-gigabitethernet 1/0/1

[Sysname-Ten-GigabitEthernet1/0/1] inqa mp 100

Related commands

instance (collector view)

Use instance to create a collector instance and enter its view, or enter the view of an existing collector instance.

Use undo instance to delete a collector instance.

Syntax

instance instance-id

undo instance instance-id

Default

No collector instance exists on a collector.

Views

Collector view

Predefined user roles

network-admin

mdc-admin

Parameters

instance-id: Specifies a collector instance ID. The value range is 1 to 256.

Usage guidelines

A collector collects data based on the collector instance. You can configure the target flows, MPs, measurement interval, and bound analyzer ID for a collector instance.

To collect packet loss statistics on the same target flow passing through multiple collectors, create an instance on the analyzer and each collector, and make sure the instance IDs are the same.

Examples

# Create instance 1 on the collector.

<Sysname> system-view

[Sysname] inqa collector

[Sysname-inqa-collector] instance 1

Related commands

Description (collector instance view)

flow (collector instance view)

interval (collector instance view)

Interval

Use interval to specify the measurement interval for a collector instance.

Use undo interval to restore the default.

Syntax

interval interval

undo interval

Default

The measurement interval for a collector instance is 10 seconds.

Views

Collector instance view

Predefined user roles

network-admin

mdc-admin

Parameters

interval: Specifies a measurement interval in seconds. The available values are 10, 60, and 600.

Usage guidelines

During a measurement interval, a collector instance counts the packets reported form MPs and reports the data results to the analyzer. Set a proper interval according to your measurement requirements and the actual network conditions.

The shorter the interval, the more frequently the data is reported to the analyzer, which might affect the processing performance of collector and the analyzer. Make sure the same collector instance on all collectors uses the same measurement interval.

Examples

# Set the measurement interval to 60 seconds for collector instance 1.

<Sysname> system-view

[Sysname] inqa collector

[Sysname-inqa-collector] instance 1

[Sysname-inqa-collector-instance-1] interval 60

Related commands

flow (collector instance view)

instance (collector view)

loss-measure enable continual

Use loss-measure enable continual to enable continual packet loss measurement for a collector instance.

Use undo loss-measure enable continual to disable continual packet loss measurement for a collector instance.

Syntax

loss-measure enable continual

undo loss-measure enable continual

Default

The continual packet loss measurement is disabled.

Views

Collector instance view

Predefined user roles

network-admin

mdc-admin

Usage guidelines

To avoid unperceived packet loss, enable continual packet loss measurement. Once starting, it does not stop unless you execute the undo loss-measure enable continual command to disable it manually.

For a collector instance, the fixed duration and continual packet loss measurements cannot be both enabled.

Examples

# Enable continual packet loss measurement for collector instance 1.

<Sysname> system-view

[Sysname] inqa collector

[Sysname-inqa-collector] instance 1

[Sysname-inqa-collector-instance-1] loss-measure enable continual

Related commands

loss-measure enable duration

Use loss-measure enable duration to enable the fixed duration packet loss measurement for a collector instance.

Use undo loss-measure enable duration to disable the fixed duration packet loss measurement for a collector instance.

Syntax

Generic configuration:

loss-measure enable duration [ duration ]

undo loss-measure enable duration

Configuration on middle points (for compatibility with early versions):

loss-measure enable mid-point duration [ duration ]

undo loss-measure enable mid-point duration

Default

The fixed duration packet loss measurement is disabled.

Views

Collector instance view

Predefined user roles

network-admin

mdc-admin

Parameters

duration: Specifies the number of minutes for which the measurement lasts. The values can be 5, 10, 15, and 30, and the default is 10.

mid-point: Enables the fixed duration packet loss measurement for a collector instance on the middle point. This keyword applies only to point-to-point packet loss measurements.

Usage guidelines

iNQA counts the packet loss information in the specified time period. It is helpful when you want to measure the network performance in a time period or to accurately locate the fault points for packet loss.

This command will not be saved to the configuration file. The packet loss measurement cannot survive the master/subordinate, active/standby switchover, or device reboot.

For a collector instance, the fixed duration and continual packet loss measurements cannot be both enabled.

Examples

# Run the packet loss measurement for 30 minutes for collector instance 1.

<Sysname> system-view

[Sysname] inqa collector

[Sysname-inqa-collector] instance 1

[Sysname-inqa-collector-instance-1] loss-measure enable duration 30

Related commands

loss-measure enable continual

mp

Use mp to configure an MP.

Use undo mp to delete an MP.

Syntax

mp mp-id { in-point | mid-point | out-point } port-direction { inbound | outbound }

undo mp mp-id

Default

No MP is configured.

Views

Collector instance view

Predefined user roles

network-admin

mdc-admin

Parameters

mp-id: Specifies an MP ID in the range of 1 to 16777215.

in-point: Specifies the MP as an ingress point. An ingress point colors the forward flow, and decolors the backward flow, and collects packet statistics for the forward flow.

mid-point: Specifies the MP as a middle point. A middle point only collects packet statistics for the target flow.

out-point: Specifies the MP as an egress point. An egress point decolors the forward flow, colors the backward flow, and collects packet statistics for the backward flow.

inbound: Specifies the flows entering the MP.

outbound: Specifies the flow leaving MP.

Usage guidelines

A collector instance measures the data passing through MPs. After specifying a collector instance, configure an MP.

Specify the in-point, mid-point, or out-point keyword as follows:

· If the MP is the first point that the target flow passes through, specify the in-point keyword for the MP.

· If the MP is the final point that the target flow passes through, specify the out-point keyword for the MP.

· If you define an MP between an ingress point and egress point, specify the mid-point keyword for the MP. When packet loss occurs between an ingress point and egress point, you can specify middle points to locate the problem.

Specify the port direction as follows:

· To collect the statistics on the flows entering the MP, specify the inbound keyword.

· To collect the statistics on the flows leaving the MP, specify the outbound keyword.

One MP cannot be both an ingress point and an egress point of a measured flow.

Examples

# Configure ingress MP 100 for collector instance 1 to collect traffic data for the flows entering the MP.

<Sysname> system-view

[Sysname] inqa collector

[Sysname-inqa-collector] instance 1

[Sysname-inqa-collector-instance-1] mp 100 in-point port-direction inbound

Related commands

inqa mp

iNQA analyzer commands

ams

Use ams to create an atomic measurement span (AMS) and enter its view, or enter the view of an existing AMS.

Use undo ams to delete an AMS. After an AMS is deleted, all settings in AMS view are deleted.

Syntax

ams ams-id [ delay-measure { oneway | twoway } ]

undo ams ams-id

Default

No AMS exists.

Views

Analyzer instance view

Predefined user roles

network-admin

mdc-admin

Parameters

ams-id: Specifies an AMS ID in the range of 1 to 2147483647.

delay-measure: Enables latency measurement for the AMS. If you do not specify this keyword, the AMS measures only the packet loss rate.

oneway: Enables one-way latency measurement.

twoway: Enables two-way latency measurement.

Usage guidelines

To measure point-to-point packet loss, configure AMSs in an analyzer instance.

For an AMS to measure the packet loss rate of a target flow, the following tasks are required in the AMS view:

· Configure the direction of the target flow.

· Configure the ingress MP group and egress MP group.

The latency measurement and packet loss measurement are mutually exclusive on an AMS.

If you do not enable latency measurement, the AMS measures packet loss rate by default.

To enable two-way latency measurement, make sure the following conditions are met:

· In AMS view, use the flow bidirection command to specify both directions of the target flow for collecting statistics.

· Do not configure the flow backward or flow forward command, so that bidirectional latency statistics can be obtained.

Examples

# Create an AMS and enter its view.

<Sysname> system-view

[Sysname] inqa analyzer

[Sysname-inqa-analyzer] instance 1

[Sysname-inqa-analyzer-instance-1] ams 1

# Create AMS 2, enable two-way latency measurement for it, and enter its view.

<Sysname> system-view

[Sysname] inqa analyzer

[Sysname-inqa-analyzer] instance 1

[Sysname-inqa-analyzer-instance-1] ams 2 delay-measure twoway

Related commands

flow (analyzer AMS view)

in-group

out-group

analyzer id

Use analyzer id to specify an analyzer ID.

Use undo analyzer id to restore the default.

Syntax

analyzer id analyzer-id

undo analyzer id

Default

No analyzer ID is specified.

Views

Analyzer view

Predefined user roles

network-admin

mdc-admin

Parameters

analyzer-id: Specifies an analyzer ID in dotted decimal format, for example, 10.1.1.1. The analyzer ID must be an IPv4 address that already exists on the analyzer.

Usage guidelines

The analyzer ID is used for communication between the analyzer and collector as follows:

1. The collector encapsulates the data collected from MPs into packets, uses the analyzer ID as the destination IPv4 address, and sends the packets to the analyzer.

2. The analyzer compares the analyzer ID in the packets with its own ID.

¡ If a match is found, the analyzer accepts the packets and summarizes the data in the packets.

¡ If no match is found, the analyzer identifies the packets illegal and discards them.

For the successful iNQA communication, make sure the specified analyzer ID meets the following requirements:

· The analyzer ID must be an IPv4 address that can be routable from the collector.

· The specified analyzer ID must be the same as the analyzer ID bound to a collector instance on the collector.

· As a best practice, configure the Router ID of the device as the analyzer ID.

With this command configured, iNQA uses the configured analyzer ID and the port number configured by the protocol udp-port command to start the UDP server. If the configured UDP port number is used by other services, the UDP server cannot be started, causing the configuration failure of this command.

Examples

# Specify 10.1.1.1 as the analyzer ID.

<Sysname> system-view

[Sysname] inqa analyzer

[Sysname-inqa-analyzer] analyzer id 10.1.1.1

Related commands

protocol udp-port

collector

Use collector to bind a collector to an analyzer instance.

Use undo collector to unbind a collector from an analyzer instance.

Syntax

collector collector-id

undo collector [ collector-id ]

Default

No collector is bound to an analyzer instance.

Views

Analyzer instance view

Predefined user roles

network-admin

mdc-admin

Parameters

collector-id: Specifies a collector ID in dotted decimal format, for example, 10.1.1.1. The collector ID must be the same as that configured on the collector. If you do not specify this argument in the undo collector command, you unbind all collectors from the analyzer instance.

Usage guidelines

To bind multiple collectors to an analyzer instance, repeat this command. The analyzer instance collects and analyzes the reported data of all bound collectors.

Specify the collector ID the same as that specified on the collector in the collector id command.

After you enable the measurement functionality for an analyzer instance, you cannot modify the bound collectors. To modify the collectors bound to an analyzer instance, first disable the measurement functionality for the analyzer instance.

Examples

# Bind analyzer instance 1 to the collector whose ID is 10.1.1.1.

<Sysname> system-view

[Sysname] inqa analyzer

[Sysname-inqa-analyzer] instance 1

[Sysname-inqa-analyzer-instance-1] collector 10.1.1.1

Related commands

collector id

delay-measure alarm

Use delay-measure alarm to configure latency logging for an analyzer instance.

Use undo delay-measure alarm to restore the default.

Syntax

delay-measure alarm upper-limit { upper-limit | microsec upper-limit-us } lower-limit { lower-limit | microsec lower-limit-us }

undo delay-measure alarm

Default

The latency logging is not configured for an analyzer instance. The analyzer will not generate logs for threshold crossing events.

Views

Analyzer instance view

Predefined user roles

network-admin

mdc-admin

Parameters

upper-limit: Specifies the latency upper limit.

· upper-limit: Specifies the latency upper limit in milliseconds, in the range of 0 to 3600000.

· microsec upper-limit-us: Specifies the latency upper limit in microseconds, in the range of 0 to 3600000000.

lower-limit: Specifies the latency lower limit. The lower limit must be smaller than the upper limit.

· lower-limit: Specifies the latency lower limit in milliseconds, in the range of 0 to 3600000.

· lower-limit-us: Specifies the latency lower limit in microseconds, in the range of 0 to 3600000000.

Usage guidelines

iNQA calculates latency periodically, and the analyzer generates a log on five consecutive crossings of a threshold.

· If latency exceeds the upper limit for consecutive five measurement intervals, the analyzer sends a log to the information center.

· If latency is less than the lower limit for consecutive five measurement intervals, the analyzer sends an event clearing log to the information center.

You can configure the information center to determine whether to output logs and the output destination. For more information about the information center, see "Configuring the information center."

If you execute this command multiple times, the most recent configuration takes effect.

Examples

# Set the upper limit to 50 milliseconds and the lower limit to 5 milliseconds for analyzer instance 1.

<Sysname> system-view

[Sysname] inqa analyzer

[Sysname-inqa-analyzer] instance 1

[Sysname-inqa-analyzer-instance-1] delay-measure alarm upper-limit 50 lower-limit 5

description

Use description to configure a description for an analyzer instance.

Use undo description to restore the default.

Syntax

description text

undo description

Default

An analyzer instance does not have a description.

Views

Analyzer instance view

Predefined user roles

network-admin

mdc-admin

Parameters

text: Specifies a description, a case-sensitive string of 1 to 64 characters.

Usage guidelines

A description allows easy identification of an analyzer instance.

Examples

# Set the description to AtoB for analyzer instance 1.

<Sysname> system-view

[Sysname] inqa analyzer

[Sysname-inqa-analyzer] instance 1

[Sysname-inqa-analyzer-instance-1] description AtoB

display inqa analyzer

Use display inqa analyzer to display the analyzer configuration.

Syntax

display inqa analyzer

Views

Any view

Predefined user roles

network-admin

network-operator

mdc-admin

mdc-operator

Examples

# Display the analyzer configuration.

<Sysname> display inqa analyzer

Analyzer ID : 10.1.1.1

Protocol UDP-port : 53312

Current instance count : 1

Table 3 Command output

Field	Description
Analyzer ID	Analyzer ID.
Protocol UDP-port	UDP port number for the communication between the analyzer and collector.
Current instance count	Total number of analyzer instances.

‌

display inqa analyzer instance

Use display inqa analyzer instance to display the analyzer instance configuration.

Syntax

display inqa analyzer instance { instance-id | all }

Views

Any view

Predefined user roles

network-admin

network-operator

mdc-admin

mdc-operator

Parameters

instance-id: Specifies an analyzer instance ID in the range of 1 to 8355838.

all: Displays the configuration of all analyzer instances.

Examples

# Display the configuration of analyzer instance 1.

<Sysname> display inqa analyzer instance 1

Instance ID : 1

Status : Enabled

Description : AtoB

Loss-alarm upper-limit : 8.000000%

Loss-alarm lower-limit : 4.500000%

Delay-alarm upper-limit : 5 ms

Delay-alarm lower-limit : 1 ms

Current AMS count : 2

Collectors : 10.1.1.1

12.56.66.21

21.23.13.14

# Display the configuration of all analyzer instances.

<Sysname> display inqa analyzer instance all

Instance ID : 1

Status : Enabled

Description : AtoB

Loss-alarm upper-limit : 8.000000%

Loss-alarm lower-limit : 4.500000%

Delay-alarm upper-limit : 5 ms

Delay-alarm lower-limit : 1 ms

Current AMS count : 2

Collectors : 10.1.1.1

12.56.66.21

21.23.13.14

Instance ID : 2

Status : Enabled

Description : BtoA

Loss-alarm upper-limit : 8.000000%

Loss-alarm lower-limit : 4.500000%

Delay-alarm upper-limit : 5 ms

Delay-alarm lower-limit : 1 ms

Current AMS count : 2

Collectors : 10.1.1.2

12.56.66.22

21.23.13.15

Table 4 Command output

Field	Description
Instance ID	Analyzer instance ID.
Status	Analyzer instance status: · Enabled. · Disabled.
Description	Description of the analyzer instance.
Loss-alarm upper-limit	Packet loss upper limit.
Loss-alarm lower-limit	Packet loss lower limit.
Delay-alarm upper-limit	Latency upper limit. The unit of this value is the same as that specified for the delay-measure alarm command.
Delay-alarm lower-limit	Latency lower limit.
Collectors	IDs of the collector bound to the analyzer instance.
Current AMS count	Total number of AMSs in the analyzer instance.

‌

display inqa analyzer instance ams

Use display inqa analyzer instance ams to display the AMS configuration in an analyzer instance.

Syntax

display inqa analyzer instance instance-id ams { ams-id | all }

Views

Any view

Predefined user roles

network-admin

network-operator

mdc-admin

mdc-operator

Parameters

instance-id: Specifies an analyzer instance ID in the range of 1 to 8355838.

ams-id: Specifies an AMS ID in the range of 1 to 2147483647.

all: Displays the configuration of all AMSs in an analyzer instance.

Examples

# Display the configuration of AMS 1 in analyzer instance 1.

<Sysname> display inqa analyzer instance 1 ams 1

AMS ID : 1

Flow direction : Forward

Delay-measure status : Enabled (one-way)

In-group : collector 10.1.1.1 mp 20

collector 12.56.66.21 mp 100

Out-group : collector 21.23.13.14 mp 110

# Display the configuration of all AMSs in analyzer instance 1.

<Sysname> display inqa analyzer instance 1 ams all

AMS ID : 1

Flow direction : Forward

Delay-measure status : Enabled (one-way)

In-group : collector 10.1.1.1 mp 20

collector 12.56.66.21 mp 100

Out-group : collector 21.23.13.14 mp 110

AMS ID : 2

Flow direction : Forward

Delay-measure status : Disabled

In-group : collector 21.23.13.14 mp 110

Out-group : collector 21.23.13.15 mp 120

Table 5 Command output

Field	Description
AMS ID	AMS ID.
Flow direction	Direction of the flow to be measured by the analyzer.
Delay-measure status	Latency measurement status of the collector instance: · Enabled (one-way). · Enabled (two-way). · Disabled.
In-group	Ingress MP group for the AMS.
Out-group	Egress MP group for the AMS.

‌

display inqa statistics delay

Use display inqa statistics delay to display iNQA latency statistics.

Syntax

display inqa statistics delay instance instance-id ams ams-id

Views

Any view

Predefined user roles

network-admin

network-operator

mdc-admin

mdc-operator

Parameters

instance-id: Specifies an analyzer instance ID in the range of 1 to 8355838.

ams ams-id: Specifies an AMS ID in the range of 1 to 2147483647. If you do not specify this option, the system displays the end-to-end latency statistics of an analyzer instance.

Usage guidelines

With the ams keyword specified, the system displays the point-to-point latency statistics and then you can locate the fault point based on the statistics.

The iNQA data in the first measurement interval might be incorrect. As a best practice, do not use it to judge the network performance.

Examples

# Display iNQA latency statistics of AMS 1 in analyzer instance 1. (If you configure the ams 1 delay-measure oneway and flow forward commands for AMS 1, only forward flow statistics are collected.)

<Sysname> display inqa statistics delay instance 1 ams 1

Delay measurement mode: One-way

Flow direction: Forward

Latest delay statistics:

Period Delay(usec) Delay variation(usec)

19122483 15 0

19122482 15 0

19122481 15 0

19122480 15 0

19122479 15 0

19122478 15 0

# Display iNQA latency statistics of AMS 1 in analyzer instance 2. (If you configure the ams 1 delay-measure oneway and flow backward commands for AMS 1, only backward flow statistics are collected.)

<Sysname> display inqa statistics delay instance 2 ams 1

Delay measurement mode: One-way

Flow direction: Backward

Latest delay statistics:

Period Delay(usec) Delay variation(usec)

19122483 15 0

19122482 15 0

19122481 15 0

19122480 15 0

19122479 15 0

19122478 15 0

# Display iNQA latency statistics of AMS 1 in analyzer instance 3. (If you configure the ams 1 delay-measure twoway and flow bidirection commands for AMS 1, bidirectional flow statistics are collected.)

<Sysname> display inqa statistics delay instance 3 ams 1

Delay measurement mode: Two-way

Flow direction: Bidirection

Latest delay statistics:

Period Delay(usec) Delay variation(usec)

19122483 15 0

19122482 15 0

19122481 15 0

19122480 15 0

19122479 15 0

19122478 15 0

# Display iNQA latency statistics of AMS 1 in analyzer instance 4. (If you configure the ams 1 delay-measure oneway and flow bidirection commands for AMS 1, bidirectional flow statistics are collected.)

<Sysname> display inqa statistics delay instance 4 ams 1

Delay measurement mode: One-way

Flow direction: Forward

Latest delay statistics:

Period Delay(usec) Delay variation(usec)

19122483 15 0

19122482 15 0

19122481 15 0

19122480 15 0

19122479 15 0

19122478 15 0

Delay measurement mode: One-way

Flow direction: Backward

Latest delay statistics:

Period Delay(usec) Delay variation(usec)

19122483 15 0

19122482 15 0

19122481 15 0

19122480 15 0

19122479 15 0

19122478 15 0

Table 6 Command output

Field	Description
Delay measurement mode	Latency measurement mode: · One-way · Two-way
Flow direction	Direction of the target flow: · Forward · Backward · Bidirection
Latest delay statistics	Most recent latency statistics for the target flow.
Period	Index of the measurement interval.
Delay(usec)	Latency in microseconds. · When the latency measurement mode is set to one-way, this field displays one-way latency. · When the latency measurement mode is set to two-way, this field displays two-way latency.
Delay variation(usec)	Latency jitter in microseconds. · When the latency measurement mode is set to one-way, this field displays one-way latency jitter. · When the latency measurement mode is set to two-way, this field displays two-way latency jitter.

‌

display inqa statistics loss

Use display inqa statistics loss to display iNQA packet loss statistics.

Syntax

display inqa statistics loss instance instance-id [ ams ams-id ]

Views

Any view

Predefined user roles

network-admin

network-operator

mdc-admin

mdc-operator

Parameters

instance-id: Specifies an analyzer instance ID in the range of 1 to 8355838.

ams ams-id: Specifies an AMS ID in the range of 1 to 2147483647. If you do not specify this option, the system displays the end-to-end packet loss statistics of an analyzer instance.

Usage guidelines

With the ams keyword specified, the system displays the point-to-point packet loss statistics and then you can locate the fault point based on the statistics.

The iNQA data in the first measurement interval might be incorrect. As a best practice, do not use it to judge the network performance.

Examples

# Display iNQA packet loss statistics of analyzer instance 1.

<Sysname> display inqa statistics loss instance 1

Latest packet loss statistics for forward flow:

Period LostPkts PktLoss% LostBytes ByteLoss%

19122483 15 15.000000% 1500 15.000000%

19122482 15 15.000000% 1500 15.000000%

19122481 15 15.000000% 1500 15.000000%

19122480 15 15.000000% 1500 15.000000%

19122479 15 15.000000% 1500 15.000000%

19122478 15 15.000000% 1500 15.000000%

Latest packet loss statistics for backward flow:

Period LostPkts PktLoss% LostBytes ByteLoss%

19122483 15 15.000000% 1500 15.000000%

19122482 15 15.000000% 1500 15.000000%

19122481 15 15.000000% 1500 15.000000%

19122480 15 15.000000% 1500 15.000000%

19122479 15 15.000000% 1500 15.000000%

19122478 15 15.000000% 1500 15.000000%

Table 7 Command output

Field	Description
Latest packet loss statistics for forward flow	Most recent statistics about target forward flow
Latest packet loss statistics for backward flow	Most recent statistics about target backward flow.
Period	Index of the measurement interval.
LostPkts	Number of lost packets.
PktLoss%	Packet loss rate. Packet loss rate = (Total number of packets at the ingress MP – Total number of packets at the egress MP)/Total number of packets at the ingress MP. If the clock of the collectors are not synchronized, or the ingress MP do not report any data, the packet loss rate might be negative. The minimum packet loss rate is –100%.
LostBytes	Number of lost bytes.
ByteLoss%	Byte loss rate. Byte loss rate = (Total number of bytes at the ingress MP – Total number of bytes at the egress MP)/Total number of bytes at the ingress MP. If the clock of the collectors are not synchronized, or the ingress MP do not report any data, the byte loss rate might be negative. The minimum packet loss rate is –100%.

‌

flow (analyzer AMS view)

Use flow to specify the flow direction to be measured in an analyzer AMS.

Use undo flow to restore the default.

Syntax

flow { backward | bidirection | forward }

undo flow

Default

No flow direction is specified to be measured in the analyzer AMS.

Views

Analyzer AMS view

Predefined user roles

network-admin

mdc-admin

Parameters

backward: Specifies a backward flow.

bidirection: Specifies the symmetric bidirectional flows.

forward: Specifies a forward flow.

Usage guidelines

The command is a must if you configure an AMS for point-to-point packet loss measurements.

The collector and analyzer each provide a flow command, and the direction keywords (forward, backward, and bidirection) in these commands function differently.

· In collector instance view, the collector instance collects the statistics about the flows of the specified direction and reports the statistics to the analyzer.

· In analyzer AMS view, the analyzer calculates the statistics about the flows of the specified direction.

The following matrix shows how the direction setting in the flow command results in different data calculation on the analyzer:

In collector instance view

In analyzer AMS view

Analyzer calculates data for

bidirection

forward

Only the forward flow.

The analysis data does not contains statistics for the backward flow.

forward

backward

Only for the backward flow.

Because the collectors does not report any backward flow data, the backward flow statistics in the AMS is 0.

Examples

# Specify forward flow to be measured in analyzer AMS 1 on analyzer 1.

<Sysname> system-view

[Sysname] inqa analyzer

[Sysname-inqa-analyzer] instance 1

[Sysname-inqa-analyzer-instance-1] ams 1

[Sysname-inqa-analyzer-instance-1-ams-1] flow forward

Related commands

flow (analyzer AMS view)

in-group

Use in-group to add an MP to the ingress MP group for an AMS.

Use undo in-group to remove an MP from the ingress MP group for an AMS.

Syntax

in-group collector collector-id mp mp-id

undo in-group [ collector collector-id mp mp-id ]

Default

The ingress MP group does not have any MP.

Views

Analyzer AMS view

Predefined user roles

network-admin

mdc-admin

Parameters

collector collector-id: Specifies the ID of the collector where the MP resides, in dotted decimal format.

mp mp-id: Specifies an MP ID in the range of 1 to 16777215.

Usage guidelines

If packet loss occurs in a specific segment of the network, divide the network segment into multiple AMSs to locate the AMS where packet loss occurs.

The ingress MP group is required for an AMS. You can repeat this command to add multiple MPs to the ingress MP group.

Examples

# Add MP 100 of the collector with ID 10.1.1.1 to the ingress MP group for AMS 1 in analyzer instance 1.

<Sysname> system-view

[Sysname] inqa analyzer

[Sysname-inqa-analyzer] instance 1

[Sysname-inqa-analyzer-instance-1] ams 1

[Sysname-inqa-analyzer-instance-1-ams-1] in-group collector 10.1.1.1 mp 100

Related commands

out-group

inqa analyzer

Use inqa analyzer to enable the analyzer functionality and enter its view, or enter the view of an enabled analyzer.

Use undo inqa analyzer to disable the analyzer functionality.

Syntax

inqa analyzer

undo inqa analyzer

Default

The analyzer functionality is disabled.

Views

System view

Predefined user roles

network-admin

mdc-admin

Usage guidelines

The intelligent network quality analyzer (iNQA) operations include the following device roles:

· Collector—Manages measurement points (MPs), collects data from MPs, and reports the data to the analyzer.

· Analyzer—Collects the data from collectors and summarizes the data.

After you configure this command on a device, the device functions as an analyzer.

You can enable the collector and analyzer functionalities on different devices or the same device.

Examples

# Enable the analyzer functionality and enter its view.

<Sysname> system-view

[Sysname] inqa analyzer

[Sysname-inqa-analyzer]

instance (analyzer view)

Use instance to create an analyzer instance and enter its view, or enter the view of an existing analyzer instance.

Use undo instance to delete an analyzer instance.

Syntax

instance instance-id

undo instance instance-id

Default

No analyzer instance exists on an analyzer.

Views

Analyzer view

Predefined user roles

network-admin

mdc-admin

Parameters

instance-id: Specifies an analyzer instance ID in the range of 1 to 8355838.

Usage guidelines

An analyzer instance collects and counts the measurement results for the same target flow passing through all collectors in the instance.

For an analyzer instance, you must bind it to a collector and choose to configure the description, packet loss upper limit, and packet loss lower limit. If you want to perform point-to-point performance measurements for an analyzer instance, configure AMSs.

To collect packet loss statistics on the same target flow passing through multiple collectors, create an instance on the analyzer and each collector, and make sure the instance IDs are the same.

Examples

# Create instance 1 on the analyzer.

<Sysname> system-view

[Sysname] inqa analyzer

[Sysname-inqa-analyzer] instance 1

loss-measure alarm

Use loss-measure alarm to configure packet loss logging for an analyzer instance.

Use undo loss-measure alarm to restore the default.

Syntax

loss-measure alarm upper-limit upper-limit lower-limit lower-limit

undo loss-measure alarm

Default

The packet loss logging is not configured for an analyzer instance. The analyzer will not generate logs for threshold crossing events.

Views

Analyzer instance view

Predefined user roles

network-admin

mdc-admin

Parameters

upper-limit upper-limit: Specifies the packet loss upper limit, a string of 1 to 10 characters. The value range is 0.000001% to 100%, correct to six decimal places. The threshold is crossed if the packet loss rate exceeds it.

lower-limit lower-limit: Specifies the packet loss lower limit, a string of 1 to 10 characters. The value range is 0.000001% to 100%, correct to six decimal places. It must not be greater than the upper limit. The threshold is crossed if the packet loss rate drops below it.

Usage guidelines

iNQA calculates the packet loss rate periodically, and the analyzer generates a log on five consecutive crossings of a threshold.

· If the packet loss rate exceeds the upper limit for consecutive five measurement intervals, the analyzer sends a log to the information center.

· If the packet loss rate is less than the lower limit for consecutive five measurement intervals, the analyzer sends an event clearing log to the information center.

You can configure the information center to determine whether to output logs and the output destination. For more information about the information center, see "Configuring information center."

If you execute this command multiple times, the most recent configuration takes effect.

Examples

# Set the upper limit to 8% and the lower limit to 4.5% for analyzer instance 1.

<Sysname> system-view

[Sysname] inqa analyzer

[Sysname-inqa-analyzer] instance 1

[Sysname-inqa-analyzer-instance-1] loss-measure alarm upper-limit 8 lower-limit 4.5

measure enable (analyzer instance view)

Use measure enable to enable the measurement functionality of an analyzer instance.

Use undo measure enable to disable the measurement functionality of an analyzer instance.

Syntax

measure enable

undo measure enable

Default

The measurement functionality of an analyzer instance is disabled.

Views

Analyzer instance view

Predefined user roles

network-admin

mdc-admin

Usage guidelines

To avoid incorrect statistics on the analyzer, do not modify the iNQA settings on the collector when the measurement functionality of an analyzer instance is enabled. To modify the iNQA settings on a collector, perform the following steps:

1. On the analyzer, execute the undo measure enable command to disable the measurement functionality of the analyzer instance bound to a collector.

2. Log in to the collector and modify the collector settings.

3. On the analyzer, execute the measure enable command to enable the measurement functionality of the analyzer instance.

For both packet loss and latency measurement, you must configure this command to enable the analyzer to start operation.

Examples

# Enable the measurement functionality of analyzer instance 1.

<Sysname> system-view

[Sysname] inqa analyzer

[Sysname-inqa-analyzer] instance 1

[Sysname-inqa-analyzer-instance-1] measure enable

out-group

Use out-group to add an MP to the egress MP group for an AMS.

Use undo out-group to remove an MP from the egress MP group for an AMS.

Syntax

out-group collector collector-id mp mp-id

undo out-group [ collector collector-id mp mp-id ]

Default

The egress MP group does not have any MP.

Views

Analyzer AMS view

Predefined user roles

network-admin

mdc-admin

Parameters

collector collector-id: Specifies the ID of the collector where the MP resides, in dotted decimal format.

mp mp-id: Specifies an MP ID in the range of 1 to 16777215.

Usage guidelines

If packet loss occurs in a specific segment of the network, divide the network segment into multiple AMSs to locate the AMS where packet loss occurs.

The egress MP group is required for an AMS. You can repeat this command to add multiple MPs to an egress MP group.

Examples

# Add MP 200 of the collector with ID 2.1.1.1 to the egress MP group for AMS 1 in analyzer instance 1.

<Sysname> system-view

[Sysname] inqa analyzer

[Sysname-inqa-analyzer] instance 1

[Sysname-inqa-analyzer-instance-1] ams 1

[Sysname-inqa-analyzer-instance-1-ams-1] out-group collector 20.1.1.1 mp 200

Related commands

in-group

protocol udp-port

Use protocol udp-port to specify a UDP port for communication between the analyzer and collectors.

Use undo protocol udp-port to restore the default.

Syntax

protocol udp-port port-number

undo protocol udp-port

Default

The UDP port number used for communication between the analyzer and collectors is 53312.

Views

Analyzer view

Predefined user roles

network-admin

mdc-admin

Parameters

port-number: Specifies a UDP port number in the range of 1024 to 65535. To avoid configuration failure, make sure the specified UDP port number is not used by other services. You can execute the display udp verbose command to view the state of the UDP port number.

Usage guidelines

With the analyzer id command configured, iNQA uses the configured analyzer ID and the port number configured by this command to start the UDP server. If the configured UDP port number is used by other services, the UDP server cannot be started, causing the failure of the analyzer. Please modify the UDP port number and then configure the analyzer id command again.

To allow the collector to report the data to the analyzer, make sure the UDP port number specified by the analyzer command on the collector is the same as the UDP port number specified by this command.

Examples

# Specify UDP port 1024 for communication between the analyzer and collectors.

<Sysname> system-view

[Sysname] inqa analyzer

[Sysname-inqa-analyzer] analyzer id 10.1.1.1

Related commands

analyzer

analyzer id

13-Network Management and Monitoring Command Reference

iNQA commands

collector id

Intelligent Terminal Products

Product Support Services

Technical Service Solutions

Resource Center

Policy

Online Help

Become a Partner

Partner Policy & Program

Global Learning

Partner Sales Resources

Service Business

Company Information

News & Events

Contact Us