NIC agent does not ping check even if NetworkHosts is configured

book

Article ID: 100059063

calendar_today

Updated On:

Description

Error message

No error message provided.

 

Cause

Since InfoScale 7.4, the NIC agent checks for faults in /sys/class/net/{nic device}/operstate because it is no longer recommended to check the NIC status using Mii on the Linux side.

A ping check is only performed if this content is unknown and cannot detect failures during network problems where the state of the NIC does not change.

In other words, as long as the NIC is up, no ping check is performed and it is judged as ONLINE.
 

Resolution

PingOptimize can be set to 2 in the NIC resource.  By adding this attribute, the ping check will be executed regardless of the state of the operstate.
//////////////////////////////////////////////
        NIC testNIC (
                Device = ens161
                PingOptimize = 2
                NetworkHosts = { "192.168.10.200" }
                )

//////////////////////////////////////////////

This feature is provided from VRTSvcsag-8.0.0.2401. Please contact support you need the HF.
 

Issue/Introduction

When a network problem occurs where the state of the NIC does not change in Linux, the hosts specified in NetworkHosts are not pinged and failures cannot be detected.
For example, the NIC agent running on a virtual machine cannot detect a NIC failure on the physical host as shown in the images below. The NIC agent ping check does not work for failures in the following cases.

Error message

No error message provided.