Problem with IPMultiNIC resource going offline

book

Article ID: 100006621

calendar_today

Updated On:

Description

Error Message

in.mpathd[430]: [ID 168056 daemon.error] All Interfaces in group NIC_CARD have failed
AgentFramework[1873]: [ID 702911 daemon.notice] VCS ERROR V-16-1-13067 Thread(3) Agent is calling clean for resource(oraqaapp_IP) because the resource became OFFLINE unexpectedly, on its own.

Cause

The MultiNICB resource in VCS is not configured correctly to work with Solaris Mpathd. So any Failover/Failback done by Solaris Mpathd is not correctly reflected in VCS.

Resolution

If using Solaris mpathd
ensure to:
Set UseMpathd to 1
Set MpathdCommand to "/usr/lib/inet/in.mpathd -a" (Check with ps -ef command the correct path of in.mpathd process)

If Solaris mpathd is not required then ensure to:
Set UseMpathd to 0
Set MpathdCommand to "/usr/lib/inet/in.mpathd -a". This is make sure that with MultiNICB running in Base more, if a user starts in.mpathd then VCS will kill it.


Issue/Introduction

Incorrect configuration of MultiNICB resource when Solaris mapthd being used causes unexptected IPMultiNICB failures during mpathd failover/failback operation.
Powered by Wolken Software