Forum Discussion

Mark_Davies's avatar
13 years ago

VCS Warning errors in IPMultiNICB

Hi,

I am using VCS5.1 SP1 on two Solaris 10 servers with a Solaris 9 container as a service.  I have three networks on the physical hosts using link based ip and then through VCS setting the cluster to ip the three networks onto the Solaris 9 container.

I am receiving the following errors every 30 seconds in the IPMultiNICB logs:

2012/02/08 15:09:03 VCS WARNING V-16-10001-6559 IPMultiNICB:ipb_backup:monitor:Unknown Protocol () type. Set Protocol to default (IPv4).
2012/02/08 15:09:04 VCS WARNING V-16-10001-6559 IPMultiNICB:ipb_ukcsn:monitor:Unknown Protocol () type. Set Protocol to default (IPv4).
2012/02/08 15:09:04 VCS WARNING V-16-10001-6559 IPMultiNICB:ipb_prod:monitor:Unknown Protocol () type. Set Protocol to default (IPv4).

Here is what is set in the main.cf file for each MultiNICB resource and IPMultiNICB resource and types file entries:

IPMultiNICB ipb_backup (
                Critical = 0
                BaseResName = mnb_backup
                Address = "10.6.241.83"
                NetMask = "255.255.255.0"
                )

        IPMultiNICB ipb_prod (
                Critical = 0
                BaseResName = mnb_prod
                Address = "10.6.8.66"
                NetMask = "255.255.255.0"
                )

        IPMultiNICB ipb_ukcsn (
                Critical = 0
                BaseResName = mnb_ukcsn
                Address @ecsclapmanu001 = "10.101.14.65"
                Address @ecscscomanu001 = "10.101.142.128"
                NetMask = "255.255.255.0"
                )

 MultiNICB mnb_backup (
                Critical = 0
                UseMpathd = 1
                ConfigCheck = 0
                Device = { nxge2 = 0, nxge6 = 0 }
                GroupName = backup
                )

        MultiNICB mnb_prod (
                Critical = 0
                UseMpathd = 1
                ConfigCheck = 0
                Device = { nxge0 = 0, nxge4 = 0 }
                GroupName = prod
                )

        MultiNICB mnb_ukcsn (
                Critical = 0
                UseMpathd = 1
                ConfigCheck = 0
                Device = { nxge1 = 0, nxge5 = 0 }
                GroupName = ukcsn
                )

type IPMultiNICB (
        static int MonitorInterval = 30
        static int OnlineRetryLimit = 1
        static int ToleranceLimit = 1
        static str ArgList[] = { BaseResName, Address, NetMask, DeviceChoice, RouteOptions, PrefixLen, IgnoreMultiNICBFailure, "BaseResName:Protocol", Option
s }
        static int ContainerOpts{} = { RunInContainer=0, PassCInfo=1 }
        str BaseResName
        str Address
        str NetMask
        str DeviceChoice = 0
        str RouteOptions
        int PrefixLen
        int IgnoreMultiNICBFailure
        str Options
)

type MultiNICB (
        static int MonitorInterval = 10
        static int OfflineMonitorInterval = 60
        static str ArgList[] = { UseMpathd, MpathdCommand, ConfigCheck, MpathdRestart, Device, NetworkHosts, LinkTestRatio, IgnoreLinkStatus, NetworkTimeout,
 OnlineTestRepeatCount, OfflineTestRepeatCount, NoBroadcast, DefaultRouter, Failback, GroupName, Protocol }
        static str Operations = None
        int UseMpathd
        str MpathdCommand = "/usr/lib/inet/in.mpathd"
        int ConfigCheck = 1
        int MpathdRestart = 1
        str Device{}
        str NetworkHosts[]
        int LinkTestRatio = 1
        int IgnoreLinkStatus = 1
        int NetworkTimeout = 100
        int OnlineTestRepeatCount = 3
        int OfflineTestRepeatCount = 3
        int NoBroadcast
        str DefaultRouter = "0.0.0.0"
        int Failback
        str GroupName
        str Protocol = IPv4
)

Can anyone recommend a solution - the ip addresses are up.

Regards,

Mark Davies

  • Are you able to run "ha" commands from local zone without been prompted for a password - this file is normally needed so you have permissions to run VCS commands from an essentially unauthorised node.

    Also just making sure you noticed the file has a dot at front, so obvioulsly need to use "ls -a" to list and that this should be in roots home directory (normally /root)

    I believe the permissions work differently in VCS 6.0, so maybe Symantec brought them in early so work differently from 5.1SP1

    Mike