Troubleshooting network management and monitoring

iFIT issues

iFIT deployment failure

Symptom

The gRPC collector cannot receive iFIT statistics or the display ifit statistic command does not display iFIT statistics.

Common causes

The following are the common causes of this type of issue:

·     The device cannot reach the gRPC collector, resulting in a failure to report iFIT statistics.

·     The gRPC subscription configuration on the device is incorrect, causing the device to fail to report iFIT statistics.

·     On an SRv6 network, the device is not a node of an SRv6 tunnel and does not support iFIT statistics.

·     The iFIT configuration is missing on the device, resulting in no iFIT statistics being generated on the device.

·     The driver does not report iFIT statistics to the iFIT module.

·     The iFIT module does not correctly handle iFIT statistics reported by the driver.

Troubleshooting flow

Figure 1 shows the troubleshooting flowchart.

Figure 1 Flowchart for troubleshooting iFIT deployment failure

 

Solution

1.     Identify whether the device can ping the gRPC collector.

Execute the ping command to check network connectivity.

¡     If the ping fails, iFIT measurement data cannot be uploaded to the collector via gRPC.

¡     If the ping succeeds, see the ping failure troubleshooting procedure for ping and tracert troubleshooting.

2.     Identify whether the GRPC subscription configuration on the device is correct.

To upload iFIT measurement data to the GRPC collector periodically, enable gRPC on the device and configure gRPC subscription and sampling path ifit/flowstatistics/flowstatistic. For more information, see configuration examples in iFIT Configuration Guide.

3.     For SRv6 networking, identify whether the device is in the SID list of an SRv6 tunnel.

On an SRv6 or G-SRv6 network, deploy iFIT on the nodes in the SID list. If the device acts as a transit node and is not in the SID list, the device will not parse SRv6 and iFIT headers. Therefore, even if the device is configured with iFIT, the device will not perform iFIT measurement.

To configure the device as a transit node (that is not in the SID list and does not parse SRv6 headers) to perform iFIT measurement, use one of the following methods depending on networking conditions:

¡     Add the device to the SID list through SRv6 configuration, and then enable iFIT measurement on the device.

¡     Execute the trace-measure per-hop command to enable iFIT measurement on the transit node.

-     On an SRv6 TE policy or SRv6 BE network for CMCC, specify the CMCC technical standards and the hop-by-hop measurement mode, and execute ifit enable and trace-measure per-hop on the transit node.

-     On an SRv6 BE network for China Telecom or China Unicom, specify the China Telecom or China Unicom iFIT technical standards, receptively, and the hop-by-hop measurement mode, and execute ifit enable and trace-measure per-hop on the transit node. On an SRv6 TE policy network China Telecom or China Unicom, transit nodes using China Telecom or China Unicom technical standards do not perform iFIT measurement as required by these standards.

4.     Identify whether iFIT configuration is correct.

Verify iFIT configuration based on the node type.

For example, execute the display ifit flow static command on the ingress node to identify whether a static flow is created. Then, identify the Measurement status has the field value as follows:

¡     If the field value is Active, iFIT measurement is in progress. Then, identify whether the static flow parameters comply with the network. If not, see iFIT Configuration Guide for modification. For example, to perform end-to-end measurement and hop-by-hop measurement, specify the e2e and trace measurement modes, receptively.

¡     If the field value is Inactive, iFIT measurement is not in progress. The iFIT configuration is probably incorrect. Then, identify whether a VPN or APN6 instance is bound correctly. If a bound instance does not exist, edit the configuration.

<Sysname> display ifit flow static flow-id 4097

Instance name                  : 1

Device ID                      : 1

Flow ID                        : 4097

Transmit network type          : Tunnel

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:

  GigabitEthernet1/0/6

Execute the display ifit flow dynamic command on the transit and egress nodes to view information about iFIT dynamic target flows.

¡     If the output does not display any iFIT dynamic target flows, no iFIT dynamic target flows are matched. You can capture packets in the ingress direction to identify whether the specified service packets are received. If the device cannot receive the specified service packets, first resolve the issue of service packet loss.

¡     If the output displays iFIT dynamic target flows, proceed to step 5.

5.     Identify whether the device driver reports iFIT statistics.

Execute the display system internal ifit flow command to obtain iFIT flow information.

¡     If the RcvCount field value keeps increasing, the driver has reported iFIT statistics to the iFIT module.

¡     If the RcvCount field value displays 0, does not increase, or increases slowly, which is far smaller than the number of service packets, the driver has not reported iFIT statistics to the iFIT module. This might be because device hardware does not support iFIT measurement or the device does not have enough resources for iFIT measurement. In this case, perform the following operations:

-     Execute the display logbuffer | include IFIT_NO_SUPPORT command to identify whether the system log contains log messages with the IFIT_NO_SUPPORT abstract. If the system log includes such log messages, the device does not support iFIT. Then, replace the hardware for the device to support iFIT. If the system log does not include such log messages, proceed to the next step.

-     Execute the display logbuffer | include IFIT_NO_RESOURCE command to identify whether the system log contains log messages with the IFIT_NO_RESOURCE abstract. If the system log includes such log messages, the device lacks resources to perform iFIT measurement. If the system log does not include such log messages, proceed to the next step.

<Sysname> display  system internal ifit flow slot 2

iFit Kernel flow information:

  NodeID     FlowID  IfIndex  RcvCount  Smooth  Encap  Mode  Period

  1          2       0        2         0       0      0     0

6.     Identify whether the iFIT module can process iFIT statistics reported by the driver correctly.

Enable iFIT debugging for further troubleshooting.

a.     To avoid generating too much debugging information, perform the following operations: Execute the debugging ifit error command to examine debugging information for iFIT processing errors.

b.     If no iFIT processing errors occur, execute the debugging ifit event command to identify whether the iFIT module is processing the driver-reported iFIT statistics correctly.

If the debugging information indicates that the iFIT module cannot process iFIT statistics, execute undo ifit enable and ifit enable to re-enable iFIT, or execute reboot to restart the device.

7.     If the issue persists, collect the following information and contact Technical Support:

¡     Results of each step.

¡     The configuration files, log messages, and alarm messages.

Related alarm and log messages

Alarm messages

N/A

Log messages

·     IFIT_NO_SUPPORT

·     IFIT_NO_RESOURCE