Attributes in this section are managed internally by the configuration wizards or by RMS at runtime.
Possible Values: Any interconnect name
Valid for SysNode objects. Space-separated list that RMS uses as additional cluster interconnects if the interconnect assigned to the SysNode name becomes unavailable. All these interconnects must be found in the /etc/hosts database. By default, the configuration wizards assume the alternate interconnects to node <nodename> have names of the form <nodename>rmsAI<nn>, where <nn> is a two-digit, zero-filled number. This setting is restricted to very specific configurations and must never be used in a cluster with CF as interconnect.
Possible Values: Any string
Valid for resource objects. Used for display purposes in the user interface - no functional meaning within RMS.
Possible Values: 0, 1
Valid for controller objects. If set to 1, and AutoRecover is 1, then a faulted child application is requested to go Offline before recovering. If set to 0 and AutoRecover is 1, then a faulted child application recovers without going Offline.
Possible Values: any string
Valid for all objects except SysNode. Describes the class of the resource object. Used by other programs for various purposes (for example, SNMP agents). This value is supplied by the configuration wizards.
Possible Values: any string
Valid for all objects. Used for documentation in the configuration file - no functional meaning within RMS.
Possible Values: 0, 1
Valid for controlled userApplication objects. If set to 0, RMS allows a manual switch request from the CLI or the GUI. If set to 1, only the parent controller can issue switch requests to this userApplication.
Possible Values: Any valid detector start script
Valid for resource objects with detector. Specify the detector start command directly in the <configname>.us file.
Note that a controller object has no detector because RMS determines its state internally.
Possible Values: Any SysNode name
Must be set only in the first-level andOp children of a userApplication object. Each of these andOp objects associates its parent application with the SysNode specified in its HostName attribute; the child andOp objects also determine the priority of the application's nodes.
Possible Values: Space-separated list of SysNode
Valid for all SysNode objects. List of additional cluster interconnects that should be monitored by RMS. These interconnects are used only by customer applications and not by any PRIMECLUSTER products. All monitored interconnects must be found in the /etc/hosts database. In addition, all SysNode objects must have the same number of additional interconnects.
Possible Values: Online, Offline, Faulted, Standby
Valid for resource objects with detector. This attribute contains the most recent detector report for the object. The value may be displayed in the Cluster Admin GUI; the possible values depend on the type of resource the object represents.
Possible Values: 0-512
Valid for userApplication objects. Upper limit of parent userApplication objects for the specified child application.
Possible Values: 0, 1
Valid for all object types. The resource object set to 1 is displayed only when specifying it with the -i option of the hvdisp command.
Possible Values: on, off
Valid for resource objects with detector. Used to disable a detector at runtime by setting NullDetector to on. This attribute is for use with dynamic reconfiguration only. NullDetector must never be set hard-coded to on in the RMS configuration file.
Possible Values: Valid list of SysNode names (character)
Valid for userApplication objects. Contains a list of SysNode objects where the application can come Online. The order in the list determines the next node to which the application is switched during a priority switchover, ordering a switchover after a Fault. The list is processed circularly. The user specifies this attribute indirectly when selecting the nodes for an application. RMS uses the order in which the nodes were selected and creates PriorityList automatically. The user can change the PriorityList by adding individual nodes from the list in the desired order, rather than automatically selecting the entire list.
For applications controlled by local gController or controller objects, the order of nodes in PriorityList is ignored. However, each controlled application must be able to run on the nodes specified by the controller objects.
Possible Values: Valid name (character)
Valid for gController and controller objects. Contains the name of the child (controlled) userApplication.
Possible Values: 0-2047
Valid for gResource objects. Specifies the kind of detector for the object.
Possible Values: Valid string (character)
Valid for gResource objects. Specifies a string to be forwarded to the generic detector.
Possible Values: 0, 1
Valid for controller objects. If set to 1, then PreOffline and PreOnline requests will be propagated to child applications separately from the Offline and Online requests. If 0, then separate PreOffline or PreOnline requests will not be issued for the child applications.
Possible Values: Any string
Valid for all objects. Displays additional state details in the Cluster Admin GUI or the hvdisp CLI user interface. In most cases, the state details field is empty. RMS typically provides this extra information when an application is in maintenance mode, or when an object is in a transitional, inconsistent, or standby state.
