Answer the question
In order to leave comments, you need to log in
Solaris Cluster. When installing a cluster, is a common virtual ip address created between two nodes using the SC 3.2 package?
Good day to all!
The following question came up while planning the implementation of Solaris Cluster.
The task is this, there are two servers, two arrays, with the help of SC, I wrap everything in a cluster. It turns out a 2-node configuration, plus a quorum server.
The question is, when installing a cluster, is a common virtual ip address created between two nodes using the SC 3.2 package? And how does load balancing work in this case?
Or, this task (with a common virtual ip address) is solved in a different way? If yes, then how?
Thanks in advance for the detailed answers.
ps Unfortunately, I did not find a detailed answer in the documentation,
Answer the question
In order to leave comments, you need to log in
As far as I understand, yes (in the doc, though, SC 3.3):
www.oracle.com/technetwork/server-storage/solaris-...
The LogicalHost resource is an IP address that is active from only one virtual node at a time. The administrator can switchover the LogicalHost resource from one virtual node to another. The system automatically configures the LogicalHost resource on the node where the application uses that LogicalHost resource. Should a virtual node fail, the system will automatically move the LogicalHost resource along with the dependent application to a surviving node. The zone cluster validates the permissions of the LogicalHost when creating a LogicalHost resource and when activating a LogicalHost resource on a node. Any LogicalHost resource always stays within one zone cluster.
The SharedAddress resource is an IP address that appears to be active for the entire cluster, while in reality the IP address is hosted on one machine and the cluster distributes incoming traffic across the cluster based upon the selected load balancing policy. The system automatically changes the node hosting the IP address for the SharedAddress in case of node failure. The zone cluster validates the permissions of the SharedAddress when creating a SharedAddress resource and when activating a SharedAddress resource on a node. A SharedAddress resource operates strictly within one zone cluster.
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question