class EvipNode

ManagedElement
+-Transport
+-Evip
+-EvipDeclarations
+-EvipCluster
+-EvipNode

Describes the logical EvipNode and how it is allocated to a processing unit (blade/VM) in the cluster.

Attributes
string[0..]
commands
An array of commands that are executed on this node when EVIP starts. The commands are refered by their identity specified in the EvipCommandDefinition. The commands are preceeded by a floating point order number and a colon, for example "1.0:defroute". The commands are executed in order lower to higher. The commands defined here are executed after any commands defined on cluster level.
string
distribution = fixed
Floating behavior of the EvipNode can be selected by setting distribution to FLOATING. This means that the EvipNode automatically is allocated, and reallocated if needed, to any vacant processing unit in the cluster. If this parameter is set to FIXED (default) the EvipNode will be allocated to a specific processing unit identified by Hostname.
string
key
mandatory
noNotification
restricted
evipNodeId
This is the RDN attribute. The node identities must be a consecutive integer value for all nodes. This identity is used to define node ranges, for instance "3-9" at other places in the EVIP configuration.
string[0..1]
floatPriority
This attribute is used to prioritize which EvipNodes to keep running in the case where fewer vacant processing units than the number of floating EvipNodes are available in the cluster. Lower value equals higher priority and the use of decimal numbers (floating point) is allowed. The attribute is only valid if distribution is set to FLOATING.
string[0..1]
hostname
This is the hostname of the processing unit (blade/VM) in the cluster where the EvipNode shall be located. It is just the simple hostname printed when the "hostname" command is executed, not the fully qualified domain name. The attribute is only valid if distribution is set to FIXED.
string[0..1]
primaryInterface
Obsolete (Not used any more)
Names the interface to use for EVIP traffic. This interface should be redundant in some way for instance with bonding. This should only be specified if the interface name on this particular node differs from the one specified on cluster level.


Obsolete: 

  class EvipNode