Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.

How do I add additional MultiNicB and IpMultiNicB in the cluster?

Created: 20 Jul 2012 | 8 comments

Comments 8 CommentsJump to latest comment

mikebounds's picture

If MultiNICB is for a different NIC then you just add the same way as current, but if you want a second service group using the same NIC, then you should use Proxy resources - see post https://www-secure.symantec.com/connect/forums/are-proxy-and-phantom-still-need

IPMultiNICBs are added the same way regardless of whether Proxy resource is used for MultiNICB.

If you are using Java GUI then you can just right click on a resource to copy an existing resource and then change name and attributes to what is required.

Really need some information on what you are trying to do to give a better answer.

Mike

UK Symantec Consultant in VCS, GCO, SF, VVR, VxAT on Solaris, AIX, HP-ux, Linux & Windows

If this post has answered your question then please click on "Mark as solution" link below

Gaurav Sangamnerkar's picture

Not sure what you mean by additional ... but in usual scenario ..

1. Multinicb is configured in a separate parallel group along with a phantom resource (since multinic will be a persistent resource)

2. Data service groups are configured with IPMultiNICA or IPMultiNICB  resources. You can configure as many IPMutiNIC resources depending on availability of IPs & need .. In data service groups, these IPMultiNIC resources will be dependent on proxy resource .. These proxy resource would point to MultiNIC resources which you configured in separate parallel service group ...

G

PS: If you are happy with the answer provided, please mark the post as solution. You can do so by clicking link "Mark as Solution" below the answer provided.
 

rajup99's picture

After adding MultinicB for different nic I am getting this error

2012/07/30 12:36:14 VCS ERROR V-16-10001-6525 MultiNICB:NIC_ipmp:monitor:Interface configuration is not valid. Check IP addresses, subnet masks, flags, groupnames on all interfaces. Make sure that all the interfaces of only one IP subnet are included under the resource. See Bundled Agents Reference Guide
 

here is what my multinicb lookslike

IPMultiNICB ip_NDIO (
                Critical = 0
                BaseResName = NIC_ipmp
                Address = "10.90.9.190"
                NetMask = "255.255.248.0"
                DeviceChoice = ce4
                )

        IPMultiNICB ip_TSMBackupIO (
                Critical = 0
                BaseResName = NIC_ipmp
                Address = "10.90.10.9"
                NetMask = "255.255.248.0"
                DeviceChoice = ce4

and MultinicB is

 MultiNICB NIC_ipmp (
                Critical = 0
                UseMpathd = 1
                MpathdCommand = "/usr/lib/inet/in.mpathd -a"
                Device @nehc-pbs-nd3 = { ce0 = 0, ce4 = 1 }
                Device @nehc-pbs-nd4 = { ce0 = 0, ce4 = 1 }
                NetworkHosts = { "10.90.15.254", "10.90.15.253" }
                IgnoreLinkStatus = 0
                NetworkTimeout = 200
                Failback = 1
                )

        MultiNICB NIC_ipmp_tsm (
                Critical = 0
                UseMpathd = 1
                MpathdCommand = "/usr/lib/inet/in.mpathd -a"
                Device @nehc-pbs-nd3 = { ce2 = 2, " ce6" = 3 }
                Device @nehc-pbs-nd4 = { ce2 = 2, " ce6" = 3 }
                NetworkHosts = { "10.90.15.254", "10.90.15.253" }
                IgnoreLinkStatus = 0
                NetworkTimeout = 200
                Failback = 1
                )

Gaurav Sangamnerkar's picture

Hi Raju,

as the error explains there is something wrong with the configuration of IP addressing ...

I see you have assigned two different C class networks on to 1 interface , i.e

Address = "10.90.9.190"
NetMask = "255.255.248.0"

&

Address = "10.90.10.9"  >>>>>>> This is a different C class then previous one ..
NetMask = "255.255.248.0"

As the subnet is /29, you can only have 6 hosts in one network, I believe if the two IP addresses would be in same range of network like 10.90.9.190 & 10.90.9.191 or 192 etc ... you wouldn't get this error .. because of two different IP class you might be getting this ...

for troubleshooting purpose, if you can change one IP address to match class of other, you can know if we are on right track to solve ...

G

PS: If you are happy with the answer provided, please mark the post as solution. You can do so by clicking link "Mark as Solution" below the answer provided.
 

rajup99's picture

those 2 ip addresses were working fine before; it was when adding additional MultinicB that caused an issue

Paresh Bafna's picture

Hi Raju,

The error you are getting - V-16-10001-6525 - is generated by MultiNICB agent. MultiNICB agent performs some basic checks –
- All specified physical interfaces are in the same IP subnet and group, and have "DEPRECATED" and "NOFAILOVER" flags set on them.
- No other physical interface has the same subnet as the specified interfaces.
If any of these checks fail error mentioned above will be generated. Please check if network interface configuration on your systems meet above checks.

In case of Mpathd mode (UseMpathd = 1) you can disable these checks by setting ConfigCheck attribute of all MultiNICB resources to 0.

For more details you can refer to Network Agents section of Bundled Agent Reference Guide for the VCS version you are using.

Hope this helps.

Thanks and Regards,
Paresh Bafna

Thanks and Regards,
Paresh Bafna

rajup99's picture

What are the cons for setting ConfigCheck attribute to 0? Will it affect detection of IPMP failure?  Thanks

Gaurav Sangamnerkar's picture

Hi Raju,

As explained in the section of bundled agents guide, config check as name suggests is doing two of above mentioned config checks, if you turn the value to 0, agent won't monitor for DEPRECATED & NOFAILOVER flag, so even if you have a configuration where interface doesn't have above mentioned flags, faults will not be reported .. which I believe is not correct ... the base interface IP address should be a deprecated for no broadcase & no failover to base IP address to avoid confusion of base IP & VIP.

If you select this option to 0, at a normal function won't be a problem (unless there is an error) .. however you will face difficulties administering when a real fault occurs ...

Interesting to know is, IP addresses were working before, since you are using mpathd , can u paste me following outputs:

# ifconfig -a 

# cat /etc/hostname.xxx (for interfaces in multinic)

G

PS: If you are happy with the answer provided, please mark the post as solution. You can do so by clicking link "Mark as Solution" below the answer provided.