VCS engine log reports errors with loopback interfaces which it doesn't control
Article ID: 100013976
Updated On:
Description
Error Message
VCS engine log reported when monitoring a net0 device:
ifconfig: status: SIOCGLIFFLAGS: lo0:245: no such interface
Cause
In this instance, when the “SIOCGLIFFLAGS: no such interface” error occurs, “ifconfig –a” command does not give complete output, and our monitor script does not get the information it expected - hence the NIC resource faults.
Resolution
The monitor script for the NIC agent was modified. The fix involves replacing “ifconfig –a ” with “ifconfig ”. This helps suppress any error message resulting and impacting the monitor result.
The issue is fixed via Hot Fix 6.0.5.003 ( e3600409 (e3585764)) for the Bundled agents for VCS, and will be incorporated into a future, main Bundled Agents release.
Applies To
Solaris 11 (Solaris 10 also applicable)
6.0.300 Storage Foundation HA
Issue/Introduction
Customer was running Solaris 11 and multiple loopback interfaces for the Solaris zones configured. This caused a problem for the NIC agent's monitor script which caused it to report erroneously the fact that a non-related loopback interface had an issue.
Was this article helpful?
Yes
No
Powered by
