Table of Contents

Related Documents

05-iFIT commands

Title	Size	Download
05-iFIT commands	230.83 KB

iFIT commands for application-level measurement

bind interface

Use bind interface to bind an interface to an instance.

Use undo bind interface to unbind an interface from an instance.

Syntax

bind interface interface-type interface-number

undo bind interface [ interface-type interface-number ]

Default

An instance is not bound to any interface.

Views

iFIT instance view

Predefined user roles

network-admin

Parameters

interface-type interface-number: Specifies an interface by its type and number. If you do not specify this argument, the default setting will be restored. Currently, you can only bind a Layer 3 physical interface to an instance.

Usage guidelines

Before enabling iFIT measurement on the ingress node of an instance, execute this command to bind an interface to the instance. After you bind an interface to an instance, iFIT parses the packets passing through the interface to identify the target packets and add an iFIT header to each target packets. Meanwhile, iFIT will count the number of target packets, and send the packet count and timestamp to the analyzer at intervals through gRPC.

Examples

# Bind interface Ten-GigabitEthernet0/0/6 to instance abc.

<Sysname> system-view

[Sysname] ifit enable

[Sysname-ifit] instance abc

[Sysname-ifit-instance-abc] bind interface ten-gigabitethernet 0/0/6

delete dynamic-flow

Use delete dynamic-flow to delete iFIT dynamic flows.

Syntax

delete dynamic-flow { all | device-id device-id flow-id flow-id }

Views

iFIT view

Predefined user roles

network-admin

Parameters

all: Specifies all dynamic flows.

device-id device-id: Specifies an iFIT device by its ID in the range of 1 to 1048575.

flow-id flow-id: Specifies an iFIT flow by its ID in the range of 1 to 1048575.

Usage guidelines

A flow ID is generated on the ingress node and passed to the transmit nodes and egress node. A flow ID and a device ID uniquely identify a flow and you can execute the display ifit instance command to view the flow ID.

Examples

# Delete the dynamic flow with device ID 2 and flow ID 4098.

<Sysname> system-view

[Sysname] ifit enable

[Sysname-ifit] delete dynamic-flow device-id 2 flow-id 4098

device-id

Use device-id to specify a device ID.

Use undo device-id to restore the default.

Syntax

device-id device-id

undo device-id

Default

No device ID is specified.

Views

iFIT view

Predefined user roles

network-admin

Parameters

device-id: Specifies a device ID in the range of 1 to 1048575.

Usage guidelines

A device ID uniquely identifies a device in an iFIT network. To make iFIT function correctly, specify a device ID and make sure the specified device ID is unique.

Examples

# Specify 100 as the device ID.

<Sysname> system-view

[Sysname] ifit enable

[Sysname-ifit] device-id 100

display ifit global-information

Use display ifit global-information to display global iFIT flow information.

Syntax

display ifit global-information

Views

Any view

Predefined user roles

network-admin

network-operator

Examples

# Display global iFIT flow information.

<Sysname> display ifit global-information

Current instance count : 2

Enabled instance count : 1

Current static flow count : 1

Current dynamic flow count : 1

Current SRv6 TE policy created flow count : 1

Current SRv6 TE policy created inactive flow count : 1

Table 1 Command output

Field	Description
Current instance count	Number of configured iFIT instances.
Enabled instance count	Number of instances enabled with iFIT.
Current static flow count	Number of static flows.
Current dynamic flow count	Number of dynamic flows.
Current SRv6 TE policy created flow count	Number of iFIT target flows for the SRv6 TE policy
Current SRv6 TE policy created inactive flow count	Number of inactive iFIT target flows for the SRv6 TE policy.

‌

display ifit instance

Use display ifit instance to display iFIT instance information.

Syntax

display ifit instance [ instance-name ]

Views

Any view

Predefined user roles

network-admin

network-operator

Parameters

instance-name: Specifies an iFIT instance by its name, a case-sensitive string of 1 to 31 characters.

Examples

# Display IPv4 iFIT instance information.

<Sysname> display ifit instance 1

Instance name : 1

Device ID : 1

Flow information:

Flow type : Static

Flow direction : Unidirection

Source IP/mask length : 1.1.1.1/24

Destination IP/mask length : 2.2.2.2/32

Protocol : TCP

Source port : Any

Destination port : Any

DSCP : 23

VPN instance name : --

Measurement information:

Period : 10 sec

Measurement mode : e2e

Loss measurement : Enabled

Delay measurement : Enabled

Measurement configuration : Disabled

Measurement status : Inactive

Flow items:

Flow ID Interface

1 Ten-GigabitEthernet0/0/6

# Display the IPv6 static flow configuration.

<Sysname> display ifit instance 3

Instance name : 3

Device ID : 1

Flow information:

Flow type : Static

Flow direction : Unidirection

Source IPv6/prefix length : 1::1/68

Destination IPv6/prefix length : 2::2/128

Protocol : UDP

Source port : 8080

Destination port : 2308

DSCP : --

VPN instance name : vpn3

Measurement information:

Period : 30 sec

Measurement mode : e2e

Loss measurement : Enabled

Delay measurement : Enabled

Measurement configuration : Enabled

Measurement status : Active

Flow items:

Flow ID Interface

11 Ten-GigabitEthernet0/0/6

12 Ten-GigabitEthernet0/0/7

Table 2 Command output

Field	Description
Instance Name	iFIT instance name.
Device ID	iFIT device ID.
Flow information	iFIT target flow information.
Flow type	iFIT flow type: · Static. · Dynamic.
Flow direction	iFIT flow direction.
Source IP/maskLength	Source IP address and mask length of the target flow.
Destination IP/maskLength	Destination IP address and mask length of the target flow.
Source IPv6/prefix length	Source IPv6 address and prefix length of the target flow.
Destination IPv6/prefix length	Destination IPv6 address and prefix length of the target flow.
Protocol	Target flow protocol: · any. · udp. · tcp. · sctp.
Source port	Source port number of the target flow.
Destination port	Destination port number of the target flow.
DSCP	DSCP value of the target flow.
VPN-instance name	Name of the VPN instance bound to the iFIT flow.
Measurement information	Measurement information.
Period	Measurement period.
Measurement mode	Measurement mode: · e2e—End to end measurement. · trace—Hop by hop measurement.
Loss measurement	Whether packet loss measurement is enabled: · Enabled. · Disabled.
Delay measurement	Whether delay measurement is enabled: · Enabled. · Disabled.
Measurement configuration	Whether measurement is enabled: · Enabled. · Disabled.
Measurement status	Actual measurement state: · Active—iFIT measurement is in progress. · Inactive—iFIT measurement has not started.
Flow items	iFIT target flow. Flow information is displayed only when the measure enable command is executed.
Flow ID	iFIT target flow ID. -- indicates that the flow has not been assigned with an ID.
Interface	Interface bound to the iFIT target flow. All indicates that the iFIT flow has been bound to all Layer 3 physical interfaces.

‌

display ifit flow dynamic

Use display ifit flow dynamic to display dynamic flow information.

Syntax

display ifit flow dynamic [ device-id device-id flow-id flow-id ]

Views

Any view

Predefined user roles

network-admin

network-operator

Parameters

device-id device-id: Specifies an iFIT device by its ID in the range of 1 to 1048575.

flow-id flow-id: Display information about a dynamic flow by its ID. The value range for the flow-id argument is 1 to 1048575.

Usage guidelines

A transmit node or the egress node parses the received packets and identifies the target flow according to the iFIT headers of the packets. A dynamic flow is identified by the device ID and flow ID in the iFIT headers of the packets. If the device does not receive the packets using the same device ID and the same flow ID for a period of time, the device will age out the dynamic flow entry.

A flow ID is generated on the ingress node and passed to the transmit nodes and egress node. A flow ID and device ID uniquely identify a flow and you can execute the display ifit instance command to view the flow ID.

Examples

# Display dynamic flow information.

<Sysname> display ifit flow dynamic

Device ID : 1

Flow ID : 4099

Flow type : Dynamic

Flow direction : Unidirection

Period : 10 sec

Actual aging-time : 300 sec

Interface information

Name Direction

Ten-GigabitEthernet0/0/6 TransitInput

Ten-GigabitEthernet0/0/7 TransitOutput

Table 3 Command output

Field	Description
Device ID	iFIT device ID.
Flow ID	Flow ID of a dynamic flow.
Flow type	Flow type: · Static. · Dynamic.
Flow direction	Flow direction. If the field value is Unidirection, the flow is a unidirectional flow.
Period	Measurement period in seconds.
Actual aging-time	Actual time when the dynamic flow is aged out.
Interface information	Information about the interfaces that receive the dynamic flow.
Name	Interface name.
Direction	Flow direction for the interface: · Ingress—The target flow enters the transit network from this interface. · TransitInput—The target flow enters the node from this interface. · TransitOutput—The target flow leaves the node from this interface. · Egress—The target flow leaves the transit network from this interface.

‌

display ifit flow static

Use display ifit flow static to display static flow information for the most recent 10 measurement periods.

Syntax

display ifit flow static [ flow-id flow-id ]

Views

Any view

Predefined user roles

network-admin

network-operator

Parameters

flow-id flow-id: Display information about a static flow by its ID. The value range for the flow-id argument is 1 to 1048575.

Usage guidelines

You can specify a flow on the ingress node by using any combination of the following items: source IP address/segment, source port number, destination IP address/segment, destination port number, protocol type, DSCP value, and VPN instance. If a packet matches the configured items, the ingress node will add an iFIT header to the packet and the flow is the static flow.

Examples

# Display the IPv4 static flow configuration.

<Sysname> display ifit flow static flow-id 4097

Instance name : 1

Device ID : 1

Flow ID : 4097

Flow information:

Flow type : Static

Flow direction : Unidirection

Source IP/mask length : 1.1.1.1/24

Destination IP/mask length : 2.2.2.2/32

Protocol : TCP

Source port : Any

Destination port : Any

DSCP : 23

VPN instance name : --

Measurement information:

Period : 10 sec

Measurement mode : e2e

Loss measurement : Enabled

Delay measurement : Enabled

Measurement configuration : Enabled

Measurement status : Active

Bound interface:

All

# Display the IPv6 static flow configuration.

<Sysname> display ifit flow static flow-id 4099

Instance name : 3

Device ID : 1

Flow ID : 4099

Flow information:

Flow type : Static

Flow direction : Unidirection

Source IPv6/prefix length : 1::1/68

Destination IPv6/prefix length : 2::2/128

Protocol : UDP

Source port : 8080

Destination port : 2308

DSCP : --

VPN instance name : vpn3

Measurement information:

Period : 30 sec

Measurement mode : e2e

Loss measurement : Enabled

Delay measurement : Enabled

Measurement configuration : Enabled

Measurement status : Active

Bound interface:

Ten-GigabitEthernet0/0/6

Table 4 Command output

Field	Description
Instance Name	Name of the iFIT instance.
Device ID	ID of the device that generates the iFIT target flow.
Flow ID	Flow ID of the target flow.
Flow information	Information about the target flow.
Flow type	Flow type: · Static. · Dynamic.
Flow direction	Flow direction. If the field value is Unidirection, the flow is a unidirectional flow.
Source IP/maskLength	Source IP address and mask length.
Destination IP/maskLength	Destination IP address and mask length.
Source IPv6/prefix length	Source IPv6 address and prefix length.
Destination IPv6/prefix length	Destination IPv6 address and prefix length.
Protocol	Protocol: · Any. · UDP. · TCP. · SCTP.
Source port	Source port number.
Destination port	Destination port number.
DSCP	DSCP value of the target flow.
VPN-instance name	Name of the VPN instance bound to the target flow.
Measurement information	Information about iFIT measurement.
Period	Measurement period.
Measurement mode	Measurement mode: · trace—Hop-by-hop measurement. · e2e—End-to-end measurement.
Next hop configuration	Configured next hop.
Loss measurement	Delay measurement state: · Enabled. · Disabled.
Delay measurement	Loss measurement state: · Enabled. · Disabled.
Measurement configuration	Configured measurement state: · Enabled. · Disabled.
Measurement status	Actual measurement state: · Active—iFIT measurement is in progress. · Inactive—iFIT measurement has not started.
Bound interface	Interface bound with the target flow.

‌

display ifit statistic

Use display ifit statistic to display statistics about an iFIT flow for the most recent 10 measurement periods.

Syntax

display ifit statistic device-id device-id flow-id flow-id [ verbose ]

Views

Any view

Predefined user roles

network-admin

network-operator

Parameters

device-id device-id: Specifies an iFIT device by its ID in the range of 1 to 1048575.

flow-id flow-id: Displays statistics about an iFIT flow by its flow ID. The value range for the flow-id argument is 1 to 1048575.

verbose: Displays detailed statistics about an iFIT flow. If you do not specify this keyword, this command displays brief statistics about an iFIT flow.

Usage guidelines

Examples

# Display brief measurement information about the flow with device ID 1 and flow ID 123.

<Sysname> display ifit statistic device-id 1 flow-id 123

Period ID Direction PktCount Timestamp(sec, nsec) Interface

159627365 TransitIn 1500 1596273655,349433112 XGE0/0/6

# Display detailed measurement information about the flow with device ID 1 and flow ID 123.

<Sysname> display ifit statistic device-id 1 flow-id 123 verbose

Period ID : 159627365

Period started at : 2020-08-01 17:20:55

Direction : TransitInput

Interface : Ten-GigabitEthernet0/0/6

PktCount : 1500

ByteCount : 1295489456450

Timestamp (sec, nsec): 2020-08-01 17:20:55.349433112 (1619278726, 349433112)

TTL : 0

Table 5 Command output

Field	Description
PeriodID	Measurement period number.
Period started at	Start time of the measurement period.
Direction	Flow direction of the interface: · Ingress—The target flow enters the transit network from this interface. · TransitIn—The target flow enters the node from this interface. You can view this value only in the simplified iFIT flow statistics. · TransitInput—The target flow enters the node from this interface. You can view this value only in the detailed iFIT flow statistics. · TransitOut—The target flow leaves the node from this interface. You can view this value only in the simplified iFIT flow statistics. · TransitOutput—The target flow leaves the node from this interface. You can view this value only in the detailed iFIT flow statistics. · Egress—The target flow leaves the transit network from this interface.
Interface	Interface name.
PktCount	Number of packets measured in the period.
ByteCount	Number of bytes detected in the period.
Timestamp (sec, nsec)	Timestamp value for the delay measurement. In the detailed information, this field is displayed in the YY-MM-DD HH:MM:SS.nanosecond format.
TTL	This field is not supported in the current software version. TTL value of the packet.

‌

dynamic-flow aging-time

Use dynamic-flow aging-time to specify the aging time for dynamic flows.

Use undo dynamic-flow aging-time to restore the default.

Syntax

dynamic-flow aging-time multi-value

undo dynamic-flow aging-time

Default

The aging time for dynamic flows is 10 times the measurement period and it cannot be less than 5 minutes.

Views

iFIT view

Predefined user roles

network-admin

Parameters

multi-value: Specifies a multiplier value. The aging time for dynamic flows is equal to the measurement period multiplied by the multiplier value. The value range is 2 to 100.

Usage guidelines

The aging time for dynamic flows must be equal to or greater than 5 minutes. If the configured aging time is less than 5 minutes, the actual aging time will be 5 minutes.

Examples

# Configure the aging time for dynamic flows to be 20 times the measurement period.

<Sysname> system-view

[Sysname] ifit enable

[Sysname-ifit] dynamic-flow aging-time 20

flow

Use flow to specify a static flow to be monitored by an iFIT instance.

Use undo flow to remove the static flow settings.

Syntax

· iFIT measurement based on 5-tuple granularity:

¡ IPv4:

flow unidirection source-ip src-ip-address [ src-mask-length ] destination-ip dest-ip-address [ dest-mask-length ] [ protocol { { tcp | udp | sctp } [ source-port src-port-number ] [ destination-port dest-port-number ] | protocol-number } ] [ dscp dscp-value ] [ vpn-instance vpn-instance-name ]

undo flow

¡ IPv6:

flow unidirection source-ipv6 src-ipv6-address [ src-prefix-length ] destination-ipv6 dest-ipv6-address [ dest-prefix-length ] [ protocol { { tcp | udp | sctp } [ source-port src-port-number ] [ destination-port dest-port-number ] | protocol-number } ] [ dscp dscp-value ] [ vpn-instance vpn-instance-name ]

undo flow

· iFIT measurement based on PeerLocator granularity:

¡ IPv4:

flow unidirection source-ip any destination-ip any [ vpn-instance vpn-instance-name ] peer-locator ipv6-address prefix-length

undo flow

¡ IPv6:

flow unidirection source-ipv6 any destination-ipv6 any [ vpn-instance vpn-instance-name ] peer-locator ipv6-address prefix-length

undo flow

Default

No static flow is specified for an iFIT instance.

Views

iFIT instance view

Predefined user roles

network-admin

Parameters

unidirection: Specifies the unidirectional flows.

source-ip src-ip-address: Specifies a source IPv4 address of the flow, in dotted decimal format.

src-mask-length: Specifies a mask length for the source IPv4 address. The value range is 1 to 32. If you do not specify this argument, the exact match of the source IPv4 address is used.

destination-ip dest-ip-address: Specifies a destination IPv4 address of the flow, in dotted decimal format.

dest-mask-length: Specifies a mask length for the destination IPv4 address. The value range is 1 to 32. If you do not specify this argument, the exact match of the source IPv4 address is used.

source-ipv6 src-ipv6-address: Specifies a source IPv6 address of the flow.

src-prefix-length: Specifies a prefix length for the source IPv6 address. The value range is 1 to 128. If you do not specify this argument, the exact match of the source IPv6 address is used.

destination-ipv6 dest-ipv6-address: Specifies a destination IPv6 address of the flow.

dest-prefix-length: Specifies a prefix length for the destination IPv6 address. The value range is 1 to 128. If you do not specify this argument, the exact match of the destination IPv6 address is used.

protocol: Specifies a protocol type of the flow. If you do not specify this keyword, the flow can use any protocol.

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

· destination-port dest-port-number: Specifies a destination port number. The value range is 0 to 65535. If you do not specify this option, the flow can use any port number as the destination port number.

· source-port src-port-number: Specifies a source port number. The value range is 0 to 65535. If you do not specify this option, the flow can use any port number as the source port number.

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

dscp dscp-value: Specifies a DSCP value of the flow, in the range of 0 to 63.

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

source-ip any: Specifies any source IPv4 address.

destination-ip any: Specifies any destination IPv4 address.

source-ipv6 any: Specifies any source IPv6 address.

destination-ipv6 any: Specifies any destination IPv6 address.

peer-locator ipv6-address prefix-length: Specifies the locator to which the flow belongs. The ipv6-address argument represents the IPv6 address prefix. The prefix-length argument represents the prefix length, in the range of 32 to 120. The IPv6 address prefix cannot be an IPv4-compatible IPv6 address.

Usage guidelines

Operating mechanism

Static flows are key elements for iFIT measurement. Before starting an iFIT measurement, you must execute this command to specify a flow to be measured on the ingress node. You do not need to specify a flow on the transmit nodes and egress node because the device can automatically learn the target flow through the iFIT header of the packets.

The device can perform iFIT measurement based on the following granularities in different scenarios:

· 5-tuple granularity—Used for measuring communication quality of the specified service flow. You can use 5-tuple to match service flows or perform iFIT measurement on any service traffic on a network. This granularity is available for all networks supported by iFIT.

· PeerLocator granularity—Used for measuring end-to-end communication quality on the entire network. The peer-locator keyword can specify a tunnel. The device performs iFIT measurement on any service flows through the tunnel.

Restrictions and guidelines

An iFIT instance can monitor only one flow. If you execute this command multiple times for the same iFIT instance, the most recent configuration takes effect.

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

The source and destination IP addresses must be legal unicast IP addresses, and they cannot be broadcast or multicast IP addresses.

Examples

# Configure instance 1 to monitor the unidirectional flow from 10.10.10.1 to 10.10.10.2 with the VPN instance vpn1.

<Sysname> system-view

[Sysname] ifit enable

[Sysname-ifit] instance abc

[Sysname-ifit-instance-abc] flow unidirection source-ip 10.10.10.1 24 destination-ip 10.10.10.2 24 vpn-instance vpn1

# On an L3VPN/EVPN L3VPN over SRv6 network, configure instance abc to monitor IPv4 service flows based on PeerLocator granularity of unidircetional flow and PeerLocator 2001::1.

<Sysname> system-view

[Sysname] ifit enable

[Sysname-ifit] instance abc

[Sysname-ifit-instance-abc] flow unidirection source-ip any destination-ip any peer-locator 2001::1 64

# On an L3VPN/EVPN L3VPN over SRv6 network, configure instance abc to monitor IPv6 service flows based on PeerLocator granularity of unidirectional flow and PeerLocator 2001::1.

<Sysname> system-view

[Sysname] ifit enable

[Sysname-ifit] instance abc

[Sysname-ifit-instance-abc] flow unidirection source-ipv6 any destination-ipv6 any peer-locator 2001::1 64

ifit enable

Use ifit enable to enable the iFIT functionality globally and enter its view, or enter the existing iFIT view.

Use undo ifit enable to disable the iFIT functionality globally.

Syntax

ifit enable

undo ifit enable

Default

The iFIT functionality is disabled.

Views

System view

Predefined user roles

network-admin

Usage guidelines

To measure the packet loss and packet delay of the network in real time, you can enable iFIT measurement.

To start iFIT measurement, perform the following tasks:

· On the ingress node, enable the iFIT functionality, configure iFIT device ID, create an instance, and configure a flow to be monitored by the instance. The configured flow is a static flow. The ingress node automatically uses the device ID to generates a flow ID, and encapsulates the flow ID and local iFIT device ID in the iFIT header of packets transmitted to the transmit nodes and egress node. The flow ID uniquely identifies a flow.

· On the transmit nodes and egress node, enable the iFIT functionality. If the received packet carries an iFIT header, a transmit node or the egress node will perform iFIT measurement according to the flow ID, measurement period number, timestamp in the iFIT header.

Examples

# Enable iFIT and enter its view.

<Sysname> system-view

[Sysname] ifit enable

[Sysname-ifit]

instance

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

Use undo instance to delete an iFIT instance.

Syntax

instance instance-name

undo instance instance-name

Default

No iFIT instance exists.

Views

iFIT view

Predefined user roles

network-admin

Parameters

instance-name: Specifies an iFIT instance by its name. The instance name is a case-sensitive string of 1 to 31 characters.

Usage guidelines

You must configure an iFIT instance on the ingress node. You can configure target flow match criteria in instance view. An instance can be bound to multiple interfaces, and an interface is associated with one target flow.

To perform iFIT measurement on the transmit nodes and egress node, you only need to enable iFIT. After you enable iFIT on a transmit node or the egress node, the node automatically identifies the flow according to the iFIT header, and perform iFIT measurement on the flow. The flow identified automatically is a dynamic flow.

Examples

# Create iFIT instance abc and enter its view.

<Sysname> system-view

[Sysname] ifit enable

[Sysname-ifit] instance abc

[Sysname-ifit-abc]

measure enable

Use measure enable to enable iFIT measurement for an iFIT instance.

Use undo measure enable to disable iFIT measurement for an iFIT instance.

Syntax

measure enable

undo measure enable

Default

iFIT measurement for an iFIT instance is disabled.

Views

iFIT instance view

Predefined user roles

network-admin

Usage guidelines

You can execute this command to start iFIT measurement for an iFIT instance to monitor the packet delay and packet loss of the flow.

Before starting iFIT measurement, configure a device ID, create an iFIT instance, configure a flow, and then bind an interface to the iFIT instance.

To modify the configuration for the device-id command or an iFIT enabled instance, disable iFIT measurement for the instance firstly.

Examples

# Enable iFIT measurement for iFIT instance abc.

[Sysname] ifit enable

[Sysname-ifit] instance abc

[Sysname-ifit-instance-abc] measure enable

measure mode

Use measure mode to specify an iFIT measurement mode.

Use undo measure mode to restore the default.

Syntax

measure mode { e2e | trace }

undo measure mode

Default

End-to-end measurement is used.

Views

iFIT instance view

Predefined user roles

network-admin

Parameters

e2e: Specifies end-to-end measurement. In this mode, only the ingress node and egress node report the measurement data.

trace: Specifies hop-by-hop measurement. In this mode, all nodes that are enabled with iFIT and receive the flow packets will report the measurement data.

Usage guidelines

iFIT measurement helps you to measure the network performance, troubleshoot the network faults, and measure the service quality.

To measure the packet loss and packet delay of the whole network, you can use end-to-end measurement. To accurately locate the packet loss and packet delay of each network node, you can use the hop-by-hop measurement.

Examples

# Specify hop-by-hop measurement as the measurement mode.

<Sysname> system-view

[Sysname] ifit enable

[Sysname-ifit] instance abc

[Sysname-ifit-instance-abc] measure mode trace

period

Use period to specify the measurement period for an iFIT instance.

Use undo period to restore the default.

Syntax

period period

undo period

Default

The measurement period for an iFIT instance is 30 seconds.

Views

iFIT instance view

Predefined user roles

network-admin

Parameters

period: Specifies the measurement period in seconds. Valid values include 1, 10, 30, 60, and 300.

Usage guidelines

iFIT collects performance statistics based on the measurement period.

· The sender records the sending time of the first iFIT packet in each sending interval, and counts the number of the iFIT packets sent from an interface in each sending interval. Sending interval = iFIT measurement period.

· The receiver records the receiving time of the first iFIT packet in each receiving interval, and counts the number of the iFIT packets received by an interface in each receiving interval. To reduce the impact of network delay and disorder on statistics, the receiving interval equals to (1+1/3) measurement period.

If network delay between the ingress and egress nodes is greater than 1/3 measurement period, the accuracy of iFIT packet loss statistics might be affected. This is because iFIT considers packets received beyond the receiving interval as packet loss. For example, if the measurement period is 1 second and the network delay greater than 1/3 seconds (333 milliseconds), the accuracy of iFIT packet loss statistics might be affected. In this case, set the measurement period to a greater value.

Examples

# Specify 60 seconds as the measurement period for an iFIT instance.

<Sysname> system-view

[Sysname] ifit enable

[Sysname-ifit] instance abc

[Sysname-ifit-instance-abc] period 60

reset ifit statistic

Use reset ifit statistic to clear iFIT statistics for the most recent 10 measurement periods.

Syntax

reset ifit statistic [ device-id device-id flow-id flow-id | instance instance-name ]

Views

Any view

Predefined user roles

network-admin

Parameters

device-id device-id: Specifies an iFIT device by its ID in the range of 1 to 1048575.

flow-id flow-id: Clears statistics about an iFIT flow by its flow ID. The value range for the flow-id argument is 1 to 1048575.

instance instance-name: Clears statistics about an iFIT flow by its instance name. The instance name is a case-sensitive string of 1 to 31 characters. Only the ingress node supports instances. The transmit nodes and egress node do not support instances.

Usage guidelines

Examples

# Clear iFIT statistics generated in the most recent 10 measurement periods for the flow with device ID 1 and flow ID 40962.

<Sysname> reset ifit statistic device-id 1 flow-id 40962

iFIT commands for tunnel-level measurement

display ifit global-information

Use display ifit global-information to display global information of iFIT target flows.

Syntax

display ifit global-information

Views

Any view

Predefined user roles

network-admin

network-operator

Examples

# Display global information of iFIT target flows.

<Sysname> display ifit global-information

Current instance count : 2

Enabled instance count : 1

Current static flow count : 1

Current dynamic flow count : 1

Current SRv6 TE policy created flow count : 1

Current SRv6 TE policy created inactive flow count : 1

Table 6 Command output

Field	Description
Current instance count	Number of iFIT instances.
Enabled instance count	Number of instances enabled with iFIT.
Current static flow count	Number of iFIT static target flows.
Current dynamic flow count	Number of iFIT dynamic target flows.
Current SRv6 TE policy created flow count	Number of the iFIT target flows for the SRv6 TE policy
Current SRv6 TE policy created inactive flow count	Number of inactive iFIT target flows for the SRv6 TE policy.

‌

display ifit srv6-segment-list

Use display ifit srv6-segment-list to display information about iFIT target flows for SRv6 TE policies on iFIT Analyzer.

Syntax

display ifit srv6-segment-list [ segment-list-id ]

Views

Any view

Predefined user roles

network-admin

network-operator

Parameters

segment-list-id: Specifies a segment list by its ID in the range of 0 to 4294967295. This value is automatically assigned to an SRv6 path by the SRv6 TE policy. If you do not specify a segment list, this command displays iFIT target flows for all SRv6 TE policies.

Examples

# Display information about the iFIT target flows for SRv6 TE policies on iFIT Analyzer.

<Sysname> display ifit srv6-segment-list

Device ID : 1

Flow ID : 2866

Flow direction : Unidirectional

Measurement information:

Loss measurement : Enabled

Delay measurement : Enabled

Measurement mode : e2e

Period : 30(s)

Segment list information:

Segment list ID : 0

Color : 4

Binding SID : 2001:DB8:1::1

EndPoint : 2001:DB8:3::3

Reverse binding SID : 2001:DB8:2::1

Device ID : 1

Flow ID : 2867

Flow direction : Unidirectional

Measurement information:

Loss measurement : Enabled

Delay measurement : Enabled

Measurement mode : e2e

Period : 30(s)

Segment list information:

Segment list ID : 0

Color : 4

Binding SID : 2001:DB8:1::1

EndPoint : 2001:DB8:3::3

Reverse binding SID : 2001:DB8:2::1

Device ID : 1

Flow ID : 2868

Flow direction : Unidirectional

Measurement information:

Loss measurement : Enabled

Delay measurement : Enabled

Measurement mode : e2e

Period : 30(s)

Segment list information:

Segment list ID : 0

Color : 4

Binding SID : 2001:DB8:1::1

EndPoint : 2001:DB8:3::3

Reverse binding SID : 2001:DB8:2::1

Table 7 Command output

Field	Description
Device ID	iFIT device ID.
Flow ID	iFIT flow ID.
Flow direction	iFIT flow direction. The value is Unidirectional.
Measurement information	Information about the measurement parameters.
Loss measurement	Whether packet loss is measured. · Enabled. · Disabled.
Delay measurement	Whether delay is measured. · Enabled. · Disabled.
Measurement mode	Measurement Mode: · e2e: End-to-end measurement. · Trace: Hop-by-hop measurement.
Period	Measurement interval, in seconds.
Segment list information	SRv6 segment list information
Segment list ID	ID of the segment list for the SRv6 TE policy candidate path.
Color	Color value of the SRv6 TE policy.
Binding SID	Binding SID of the SRv6 TE policy.
EndPoint	Destination address of the SRv6 TE policy.
Reverse binding SID	Reverse binding SID of the SRv6 TE policy.

‌

Related commands

work-mode analyzer

display ifit statistic-type

Use display ifit statistic-type to display the iFIT measurement result from iFIT Analyzer.

Syntax

display ifit statistic-type { one-way-delay | two-way-delay | one-way-loss } { srv6-segment-list segment-list-id | device-id device-id flow-id flow-id }

Views

Any view

Predefined user roles

network-admin

network-operator

Parameters

one-way-delay: Displays the iFIT one-way delay measurement result.

two-way-delay: Displays the iFIT two-way delay measurement result.

one-way-loss: Displays the iFIT one-way packet loss measurement result.

srv6-segment-list segment-list-id: Specifies an SRv6 path by its segment list ID in the range of 0 to 4294967295. The value is automatically assigned to the SRv6 path by the SRv6 TE policy.

device-id device-id flow-id flow-id: Specifies the target flow. The device-id argument represents the iFIT device ID in the range of 1 to 1048575. The flow-id argument represents the target slow in the range of 1 to 1048575.

Usage guidelines

Application scenarios

The command displays the iFIT measurement result for the SRv6 TE policy from iFIT Analyzer in the SRv6 TE policy and iFIT collaboration scenario.

Restrictions and guidelines

This command is not available for static iFIT flows configured by using the flow command and dynamically learned iFIT flows.

Examples

# Display the one-way packet loss information for the iFIT target flow with device ID 1 and flow ID 123.

<Sysname> display ifit statistic-type one-way-loss device-id 1 flow-id 123

One-way-loss statistics:

Period ID Loss Loss Ratio Trust flag (Error code)

1 0 0 Untrusted (1)

2 0 0 Untrusted (1)

3 0 0 Trusted (0)

4 0 0 Trusted (0)

5 0 0 Trusted (0)

6 0 0 Trusted (0)

7 0 0 Trusted (0)

8 0 0 Trusted (0)

9 0 0 Trusted (0)

10 0 0 Trusted (0)

# Display the two-way delay information for the iFIT target flow with device ID 1 and flow ID 123.

<Sysname> display ifit statistic-type two-way-delay device-id 1 flow-id 123

Two-way-delay statistics:

Period ID Delay(us) Jitter(us) Trust flag (Error code)

1 1000000 0 Untrusted (1)

2 1000000 0 Untrusted (1)

3 1000000 0 Trusted (0)

4 1000000 0 Trusted (0)

5 1000000 0 Trusted (0)

6 1000000 0 Trusted (0)

7 1000000 0 Trusted (0)

8 1000000 0 Trusted (0)

9 1000000 0 Trusted (0)

10 1000000 0 Trusted (0)

# Display the one-way delay information for the iFIT target flow with device ID 1 and flow ID 123.

<Sysname> display ifit statistic-type one-way-delay device-id 1 flow-id 123

One-way-delay statistics:

Period ID Delay(us) Jitter(us) Trust flag (Error code)

1 0 0 Untrusted (1)

2 0 0 Untrusted (1)

3 0 0 Trusted (0)

4 0 0 Trusted (0)

5 0 0 Trusted (0)

6 0 0 Trusted (0)

7 0 0 Trusted (0)

8 0 0 Trusted (0)

9 0 0 Trusted (0)

10 0 0 Trusted (0)

Table 8 Command output

Field	Description
One-way-loss statistics	One-way packet loss statistics.
Period ID	Measurement cycle ID.
Loss	Dropped packet count
Loss Ratio	Packet loss rate, with accuracy to one part per million.
Delay(us)	End-to-end delay from the ingress node to the egress node on the SRv6 path, in microseconds.
Jitter(us)	End-to-end jitter from the ingress node to the egress node on the SRv6 path, in microseconds.
Trust flag (Error code)	Whether the data reported in this cycle can be trusted. · Trusted: The data can be trusted. · Untrusted: The data cannot be trusted. The accuracy of the measurement data for the new target flow generated in the first and second cycles cannot be guaranteed and is considered untrustworthy. As a best practice, configure the controller to not use the data generated in the first and second measurement cycles for the new target flow. The values of the error code are 0 and 1. · 0: Indicates that the data can be trusted. · 1: Indicates that the data cannot be trusted.

‌

Related commands

work-mode analyzer

service-type srv6-segment-list

Use service-type srv6-segment-list to configure iFIT Collector to only collect and report the iFIT measurement results for SRv6 paths.

undo service-type to restore the default.

Syntax

service-type srv6-segment-list

undo service-type

Default

iFIT Collector does not collect or report the iFIT measurement results for SRv6 paths.

Views

iFIT Collector view

Predefined user roles

network-admin

Usage guidelines

Application scenarios

In the SRv6 TE policy and iFIT collaboration scenario, you need to execute this command on the egress node for iFIT Collector to only collect and report the iFIT measurement results for SRv6 paths.

Operating mechanism

In the SRv6 TE policy and iFIT collaboration scenario, iFIT is used to measure the end-to-end latency from the ingress node to the egress node on the SRv6 TE policy path. The measurement result will be used to guide SRv6 TE policy routing on the ingress node. An iFIT flow is created on the ingress node, and the egress node performs iFIT measurement only on packets carrying the iFIT header. The egress node can perform iFIT measurements for multiple service flows simultaneously. If you execute this command on the egress node, the egress node will only collect and report the iFIT measurement result for the SRv6 paths.

Examples

# Specify the SRv6 TE policy service for iFIT measurement.

<Sysname> system-view

[Sysname] ifit enable

[Sysname-ifit] work-mode collector

[Sysname-ifit-work-mode-collector] service-type srv6-segment-list

Related commands

work-mode collector

work-mode analyzer

Use work-mode analyzer to configure the device to act as iFIT Analyzer and enter iFIT Analyzer view.

Use undo work-mode analyzer to cancel iFIT Analyzer settings.

Use undo work-mode to restore the default.

Syntax

work-mode analyzer

undo work-mode [ analyzer ]

Default

The device does not act as iFIT Analyzer or iFIT Collector.

Views

iFIT view

Predefined user roles

network-admin

Usage guidelines

Application scenarios

In the scenario where the SRv6 TE policy and iFIT do not operate collaboratively, the device sends the iFIT measurement data to a separately deployed analyzer through Telemetry. This analyzer gathers the statistics transmitted from the ingress, transmit, and egress nodes and performs the aggregation and analysis.

In the scenario where the SRv6 TE policy and iFIT operate collaboratively, iFIT is used to measure the end-to-end delay from the ingress node to the egress node on the SRv6 paths. The measurement results are used to guide route selection on the ingress node. If the device acts as the ingress node of SRv6 paths, you must execute this command on the device.

Operating mechanism

In scenarios where an SRv6 TE policy and iFIT operate collaboratively, iFIT reuses BFD sessions of the SRv6 TE policy to encapsulate iFIT headers to the matched BFD packets for iFIT measurement. An SRv6 TE policy supports both SBFD and BFD in echo packet mode for iFIT measurement , with slightly different Analyzer processing as follows:

· For iFIT measurement based on SBFD, the Analyzer (ingress node) performs the following steps:

a. Enable iFIT to periodically send the measurement results to Analyzer on the same node.

b. Calculate the packet loss rate based on the number of SBFD packets received on both the ingress and egress nodes.

c. Calculate the one-way delay and one-way jitter based on the timestamp when the ingress node sent the SBFD packet and the timestamp when the egress node received the same SBFD packet.

d. Report the iFIT calculation results to the local SRv6 TE policy module for intelligent route selection by the SRv6 TE policy.

· For iFIT measurement based on iFIT in echo packet mode, the Analyzer (ingress node) performs the following steps:

a. Enables iFIT to periodically send the measurement results to Analyzer on the same node.

b. Calculate the packet loss rate based on the number of BFD echo packets received on both the ingress and egress nodes.

c. Calculate the two-way delay and two-way jitter based on the timestamp when the ingress node sent a BFD echo packet and the timestamp when the ingress node received a BFD echo packet.

d. Report the iFIT calculation results to the local SRv6 TE policy module for intelligent route selection by the SRv6 TE policy.

Examples

# Configure the device to act as iFIT Analyzer and enter iFIT Analyzer view.

<Sysname> system-view

[Sysname] ifit enable

[Sysname-ifit] work-mode analyzer

[Sysname-ifit-work-mode-analyzer]

Related commands

display ifit srv6-segment-list

display ifit statistic-type

work-mode collector

Use work-mode collector to configure the device to act as iFIT Collector and enter iFIT Collector view.

Use undo work-mode collector to cancel the iFIT Collector settings.

Use undo work-mode to restore the default.

Syntax

work-mode collector

undo work-mode collector

Default

The device does not act as iFIT Analyzer or iFIT Collector.

Views

iFIT view

Predefined user roles

network-admin

Usage guidelines

Application scenarios

In the scenario where iFIT collaborates with the SRv6 TE policy for intelligent route selection, you can execute this command on the egress node of the SRv6 TE policy path.

Operating mechanism

After you configure the egress node of an SRv6 TE policy to act as iFIT Collector, the egress node establishes a UDP session using the source address of the received SRv6 packets with the ingress node. Over this UDP session, the egress node sends the packet count statistics and timestamps to the ingress node at the iFIT monitoring cycle of the SRv6 TE policy.

Examples

# Configure the device to act as iFIT Collector and enter iFIT Collector view.

<Sysname> system-view

[Sysname] ifit enable

[Sysname-ifit] work-mode analyzer

[Sysname-ifit-work-mode-analyzer]

Related commands

service-type srv6-segment-list

20-Network Management and Monitoring Command Reference

iFIT commands for application-level measurement

delete dynamic-flow

Operating mechanism

Restrictions and guidelines

Application scenarios

Restrictions and guidelines

Application scenarios

Operating mechanism

Application scenarios

Operating mechanism

Application scenarios

Operating mechanism

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

News & Events

Contact Us