VCS NOTICE V-16-10001-5001 (hostname) IPMultiNICB:ipmnicb:monitor:Could not read MultiNICB export information. This may be because MultiNICB has not completed monitor yet
Article ID: 100030014
Updated On:
Description
Error Message
VCS NOTICE V-16-10001-5001 (hostname) IPMultiNICB:ipmnicb:monitor:Could not read MultiNICB export information.Resolution
The issue:
IPMultiNICB cannot start because it is dependent on MultiNICB.
The IPMultiNICB agent is not able to read the export file.
Possible reasons for failure to read the export file include:
-The file permissions for the export file(/var/VRTSvcs/lock/MultiNICB/_ multinicb_export)are incorrect.
-The file/var/VRTSvcs/lock/MultiNICB/_ multinicb_export is missing.
-The monitor for IPMultiNICB is invoked before the MultiNICB agent has started and the MultiNICB resource is not in an ONLINE status.
The command 'hastatus -sum' will show the MultiNICB resource(s) in an UNKNOWN state.
To resolve the issue:
The engine_A.log will show:
TheMultiNICB_A.log may indicate the reason that MultiNICB resource is not starting:
In this example, the path to mpathd is incorrect.
For this example, configure the MultiNICB agent to use the proper path to mpathd.
To determine / verify the proper path to the mpathd, execute:
IPMultiNICB cannot start because it is dependent on MultiNICB.
The IPMultiNICB agent is not able to read the export file.
Possible reasons for failure to read the export file include:
-The file permissions for the export file(/var/VRTSvcs/lock/MultiNICB/
-The file/var/VRTSvcs/lock/MultiNICB/
-The monitor for IPMultiNICB is invoked before the MultiNICB agent has started and the MultiNICB resource is not in an ONLINE status.
The command 'hastatus -sum' will show the MultiNICB resource(s) in an UNKNOWN state.
To resolve the issue:
The engine_A.log will show:
VCS NOTICE V-16-10001-5001 (hostname)IPMultiNICB:ipmnicb:monitor:Could not read MultiNICB export information. This may be because MultiNICB has not completed monitor yet TheMultiNICB_A.log may indicate the reason that MultiNICB resource is not starting:
2007/12/14 16:21:10 VCS ERRORV-16-10001-6505 MultiNICB:ipmp0:monitor:The mpathd process (/sbin/in.mpathd)does not exist 2007/12/14 16:21:10VCS WARNING V-16-10001-6506 MultiNICB:ipmp0:monitor:Will try to restart mpathd with (/sbin/in.mpathd) 2007/12/1416:21:10 VCS ERROR V-16-10001-6507 MultiNICB:ipmp0:monitor:Restart of mpathd failed In this example, the path to mpathd is incorrect.
For this example, configure the MultiNICB agent to use the proper path to mpathd.
To determine / verify the proper path to the mpathd, execute:
# ps -ef |grep mpathd 0S root 696 1 0 40 20 ? 364 ? Apr 07 ? 205:06 /usr/lib/inet/in.mpathd -a To fix the current configuration, change the "MpathdCommand" variable to reflect the proper path.
1) Make the configuration writeable:
# haconf -makerw 2) Modify the MultiNICB resource in the file'/etc/VRTSvcs/conf/config/main.cf':
# hares-modify MpathdCommand "/usr/lib/inet/in.mpathd -a" 3) Restart the mpathd daemon.
# pkill -HUP in.mpathd 4) Make the cluster configuration read-only:
# haconf -dump-makero The MultiNICB agent will start and IPMultiNICB will show online after successfully probing and starting the MultiNICB resource.
Issue/Introduction
VCS NOTICE V-16-10001-5001 (hostname) IPMultiNICB:ipmnicb:monitor:Could not read MultiNICB export information. This may be because MultiNICB has not completed monitor yet
Was this article helpful?
Yes
No
Powered by
