High Availability Monitors Version A.03.02 Release Notes

Writing NOF Applications
Ordering and Dependencies between NOF Verbs
Chapter 2 109
Ordering and Dependencies between NOF
Verbs
The main restriction on the order of NOF verbs is that the first reference
to a particular resource must be in a DEFINE_* verb for that resource.
This leads to the following dependencies:
• When creating a new node configuration file, the first verb issued
must be DEFINE_NODE.
• A DLC must be defined before any port that refers to it.
• A port must be defined before any LS or CN that refers to it.
• A COS must be defined before any mode that refers to it.
• A PU name must be defined (as part of an LS definition) before a
dependent LU that refers to this PU.
• An LU must be defined before an LU pool that includes it.
• A downstream PU name (as part of an LS definition) and a host LU
must be defined before a downstream LU that refers to them.
• A resource must be defined before a START_* verb refers to it, and
must be started before a STOP_* verb refers to it.
In addition, when modifying a running node, using a DEFINE_* verb a
second time (to modify the previous definition) is not always valid. For
some of these verbs, a second definition is never valid (the resource must
be deleted and then defined again); for others, a second definition is valid
only if the resource is currently inactive. The descriptions of individual
DEFINE_* verbs in Chapter 3, “NOF API Verbs (ACTIVATE_SESSION
to OPEN_FILE),” provide information about whether a second definition
is valid. When modifying the domain configuration file, a second
DEFINE_* verb can always be used to modify a previous definition.
When creating a new node configuration file, the first verb issued must
be DEFINE_NODE. This must be followed by DEFINE_* and SET_*
verbs for all the resources associated with the node.
In the domain configuration file, there is no restriction on the ordering of
domain resource records.