MultiNICB Agent does not work properly with Solaris 10

book

Article ID: 100002711

calendar_today

Updated On:

Description

Error Message

VCS WARNING V-16-10001-6519 MultiNICB:.....:monitor:Deleting default router (a8fa9fa)

VCS INFO V-16-1-10307 Resource (Owner: unknown, Group: ....) is offline on .. (Not initiated by VCS)

Cause

Starting with Solaris 10 the path of in.mpathd command was changed: if MultiNICB resources were configured to work with previous Solaris release, they will no longer work properly.

The default path was:

/sbin/in.mpathd

this is now a symbolic link to:

/usr/lib/inet/in.mpathd

Hence, must be changed in resource configuration else, MultiNICB Agent will not be able to determine if process is running and kill/restart when requested

Resolution

Change the path of mpathd command with in MultiNICB  resource using below steps

1) Open the VCS configuration in read-write mode using below

# haconf -makerw

 

2) Modify the path:

# hares -modify  MpathdCommand "/usr/lib/inet/in.mpathd -a"
# haconf -dump -makero

 

3) Next, check if the new attribute is properly set:

#  hares -display  -attribute MpathdCommand
#Resource               Attribute                         System   Value

    MpathdCommand          global     /usr/lib/inet/in.mpathd -a
 

4) Finally, restart the Agent on all of cluster nodes

# haagent -stop MultiNICB -sys

# haagent -start MultiNICB -sys

 

After performing the above steps, looking at process table, the mpathd daemon should be running:

ps -ef |grep mpathd

root   ....     1   0   ......          ... /usr/lib/inet/in.mpathd -a
 

Issue/Introduction

MultiNICB Agent does not work properly with Solaris 10. The MultiNICB resource goes to FAULTED state, without any clear reason