Closed K0nne closed 3 years ago
Hello and thank you for the feedback.
Could you please run these commands and check if the Network Interface which is deactivated is listed there?
icinga { Get-IcingaWindowsInformation -ClassName MSCluster_Network -Namespace 'Root\MSCluster'; };
icinga { Get-IcingaWindowsInformation -ClassName MSCluster_NetworkInterface -Namespace 'Root\MSCluster'; }
If they are not present during the WMI call, the plugin is unable to process them.
In this call the NIC completely disappears if its deactivated:
icinga { Get-IcingaWindowsInformation -ClassName MSCluster_NetworkInterface -Namespace 'Root\MSCluster'; }
Allright, we found the issue then. As this WMI space is not providing the data if the NIC is deactivated, we won't be able to add it's data into the plugin.
Is it still listed by simply using
Get-NetAdapter
Yes, it is listed there with state "disabled".
This only happens if the interface is manually disabled on the Windows machine. In case the cable is removed, it is displayed properly. We discussed this is the way to go, as it would be a lot of effort to fetch the state properly, as no cluster relation for disabled interfaces is present anymore, which would require us to manually map them in some way.
Hello,
today we tested a portion of the checks. While doing this we disabled a few NICs to see a state change in the plugin output. We tried to produce a "down" state. Our test object was the host 100001. Here its vNIC4 Interface was disabled. Instead of a state change the interface disappeared an the check was still OK: