Video Screencast Help

What is MultiNICA and MultiNICB ?

Created: 06 Sep 2012 • Updated: 18 Oct 2012 | 8 comments
Zahid.Haseeb's picture
This issue has been solved. See solution.

What is difference between MultiNICA and MultiNICB

Discussion Filed Under:

Comments 8 CommentsJump to latest comment

Zahid.Haseeb's picture

The link is not working of Mayank vasa

Any comment will be appreciated. Mark as Solution if your query is resolved
__________________
Thanks in Advance
Zahid Haseeb

zahidhaseeb.wordpress.com

Zahid.Haseeb's picture

Thanks got it

Any comment will be appreciated. Mark as Solution if your query is resolved
__________________
Thanks in Advance
Zahid Haseeb

zahidhaseeb.wordpress.com

Zahid.Haseeb's picture
  • Does MultiNICA resource is used for Ethernet Teaming configured on physical system.

          if yes

  • How many Ethernet cards (configured in teaming) we can use in MultiNICA resource (means two or three etc) any limitation in MultiNICA resource ?

Any comment will be appreciated. Mark as Solution if your query is resolved
__________________
Thanks in Advance
Zahid Haseeb

zahidhaseeb.wordpress.com

g_lee's picture

Zahid,

As usual, providing the platform and the version of VCS your configuration relates to would expedite you getting the answers you're requesting.

Generally the bundled agents reference guide is a good place to check for this, eg: see the following note on trunking from VCS 5.1 Solaris Bundled Agents Reference Guide

https://sort.symantec.com/public/documents/sf/5.1/...

Under Network Agents -> About the network agents

https://sort.symantec.com/public/documents/sf/5.1/...

----------

802.1Q trunking

The IP/NIC, IPMultiNIC/MultiNICA, and IPMultiNICB/MultiNICB agents support 802.1Q trunking.

The IP/NIC, IPMultiNIC/MultiNICA, and IPMultiNICB/MultiNICB agents support 802.1Q trunking on Solaris 8, 9 and 10. However, on Solaris 8, only "ce" interfaces can be configured as VLAN interfaces. This is a Sun restriction.

On Solaris 9, the IPMultiNICB and MultiNICB agents works only if Sun patch 116670-04 is installed on the system. No patch is required for the IP and NIC agents and the IPMultiNIC and MultiNICA agents

On Solaris 9 and 10, VLAN is not supported on the Fast Ethernet interfaces. (eg: hme/qfe interfaces).

You need to specify the VLAN interfaces, for example: bge20001 , bge30001, as the base interfaces in the device list in the main.cf file. You also must make sure that the IP addresses that are assigned to the interfaces of a particular VLAN are in the same subnet.

----------

If this post has helped you, please vote or mark as solution

Zahid.Haseeb's picture

Thanks g_less for your kind response.

 

Expected Environment

Solaris 10

HA 6.0 (2 nodes cluster)

teaming would be configured already on NIC's

 

After reading the .PDF i have few queries

"" First query ""

 

MultiNICA

  • The MultiNICA represents a set of network interfaces and provides failover capabilities between them.      Undestood
  • Each interface in a MultiNICA resource has a base IP address. Undestood
  • The MultiNICA agent configures one interface at a time. If it does not detect activity on the configured interface, it configures a new interface and migrates IP aliases to it.Required Question

(     the above words are drived from this link :
https://sort.symantec.com/public/documents/sf/5.1/... )

Question:

MultiNICA handles the base or physical ip address. If MultiNICA does not detect activity on the configured interface, it configures a new interface and migrates IP aliases or Base IP ?? The IP aliases migration is the responsibility of IPMultiNICA, is not it ? as per the below document of IPMultiNICA say:

The IPMultiNIC agent manages the virtual IP address that is configured as an alias on one interface of a MultiNICA resource

(  the above words are drived from this link :

https://sort.symantec.com/public/documents/sf/5.1/... )

 

"" Second query ""

                                      Difference between MultiNICA and MultiNICB

( correct me if i am wrong )

MultiNICA and MultiNICB do the same thing

  • The MultiNICA agent configures one interface at a time and when this interface fails it configures another interface. (configuration of another interface takes time)
  • The work which MultiNICA does(which is configures one interface at a time) already done for MultiNICB, means base ip addresses already configured on all interfaces which(interfaces) are highly available.

                  - Because of this (not assigning base IP's) MultiNICB take less time to failover of interfaces than MultiNICA as the assigning of base IP's are already done in MultiNICB case but MultiNICB needs more IP's as all interfaces should have all base IP's. But the MultiNICA dont have to assign base IP's on all interfaces prior and need only one IP but need time to assign the base IP on the partner/backup interface while failover of interface.

"" Third query ""

( correct me if i am wrong )

Teaming on NIC's is configured on a system where no HA is installed. Suppose we installed HA and configuing a MultiNICA or MultiNICB resource. Do we have to unconfigure teaming which is already configured before HA installation and then configure the teaming in HA which in HA case teaming=MultiNICA/MultiNICB agent functionality ?

Any comment will be appreciated. Mark as Solution if your query is resolved
__________________
Thanks in Advance
Zahid Haseeb

zahidhaseeb.wordpress.com

g_lee's picture

Zahid,

The documents for 5.1 were provided as an example as you hadn't mentioned which version was being used. If you know you're using 6.0, why refer to the doc for the old version?? Surely it would make more sense to use the documents for the correct version so you have the relevant/up-to-date details.

VCS 6.0 Solaris Bundled Agents Reference Guide

http://www.symantec.com/business/support/resources...

Other product guides for VCS 6.0 Solaris:

https://sort.symantec.com/documents/doc_details/vc...

Regarding your queries (though if you actually read the Network Agents section (pp81-129 of the above guide) this would actually answer most of your questions anyway .....)

1. MultiNICA handles the base or physical ip address. If MultiNICA does not detect activity on the configured interface, it configures a new interface and migrates IP aliases or Base IP ?? The IP aliases migration is the responsibility of IPMultiNICA, is not it ?

IPMultiNIC handles failover of the virtual IP address(es) (ie: when you failover groups from one system to another)

That is saying that in the event of NIC failure on the same system, MultiNICA migrates the base IP to the new interface, as well as the IP aliases that were configured with the corresponding IPMultiNIC resources on the original interface.

Example: sysA, sysB, both with interfaces le0, qfe0

MultiNIC mnic sysA base IP for le0, qfe0 = 10.128.8.42

MultiNIC mnic sysB base IP for le0, qfe0 = 10.128.8.43

IPMultiNIC ip1 virtual IP = 10.128.10.14

IPMultiNIC ip2 virtual IP = 10.128.9.4

Say sysA is running both ip1, ip2, with le0 as the active interface

le0 fails, so MultiNIC fails the base IP 10.128.8.42, and also fails over the virtual IPs 10.128.10.14, 10.188.9.4 onto qfe0 (otherwise the IPs are not much use if they're left on the failed interface le0)

However, if both le0 and qfe0 failed on sysA, then the IPMultiNIC & MultiNIC resources would be faulted, and the agents would work in tandem to bring the addresses up on sysB

Note: example taken from Sample configuration: IPMultiNIC and MultiNICA pp99-100 of above document

2. - Because of this (not assigning base IP's) MultiNICB take less time to failover of interfaces than MultiNICA as the assigning of base IP's are already done in MultiNICB case but MultiNICB needs more IP's as all interfaces should have all base IP's. But the MultiNICA dont have to assign base IP's on all interfaces prior and need only one IP but need time to assign the base IP on the partner/backup interface while failover of interface.

If you're asking if your understanding is correct, re: why MultiNICB failover is faster than MultiNICA; then yes, not having to failover the base IP makes it faster

3. Teaming on NIC's is configured on a system where no HA is installed. Suppose we installed HA and configuing a MultiNICA or MultiNICB resource. Do we have to unconfigure teaming which is already configured before HA installation and then configure the teaming in HA which in HA case teaming=MultiNICA/MultiNICB agent functionality ?

From the VCS 6.0 Solaris Bundled Agents Reference Guide pp82-83

--------------------

802.1Q trunking

The IP/NIC, IPMultiNIC/MultiNICA, and IPMultiNICB/MultiNICB agents support 802.1Q trunking.

On Solaris, VLAN is not supported on the Fast Ethernet interfaces. (for example, hme/qfe interfaces).

You need to specify the VLAN interfaces, for example: bge20001 , bge30001, as the base interfaces in the device list in the main.cf file. You also must make sure that the IP addresses that are assigned to the interfaces of a particular VLAN are in the same subnet.

Link aggregation support

The link aggregation feature aggregates multiple network interfaces so that they appear as a single interface. For example, you can combine bge0 and bge1 and name the combined interface aggr100.

You can use the NIC, MultiNICA, or MultiNICB agents to monitor an aggregated interface. You can use the IP, IPMultiNIC, or IPMultiNICB agent respectively to configure and monitor an IP address on the aggregated interface.

All VCS networking agents support link aggregation. However, VCS has no control over the local adapter swapping performed by the link aggregation module. For guidelines on creating and managing link aggregations, refer to the topic Overview of Link Aggregations in the System Administration Guide: IP Services guide available on the Oracle Solaris documentation website.

Note: After you set up an aggregated interface, the constituting interfaces are no longer configurable. Hence, you must specify aggregated interfaces while configuring the Device attribute of IP, NIC, MultiNICA, or MultiNICB resources.

--------------------

If this post has helped you, please vote or mark as solution

SOLUTION