![](/images/new-backgrounds/1120837/12083731x1.webp)
Introduction | Compliance Report |
|
|
1.2.1.3Availability Node Director
The Availability Node Director (AvND) resides on each system node and its main task is to maintain the
The AvND coordinates local fault identification and repair of components and furthermore facilitates any wishes it receives from the Availability Director.
The AvND watches for components arriving or leaving the system and summarizes this information in a Service Unit (SU) presence state, and keeps the AvD informed about the current status and changes. The AvND is capable of disengaging, restarting and destroying any component within its scope. This may occur according to AvD instructions or as a result of an administrative action or automatically triggered by policies.
1.2.1.4Availability Agent
The Availability Agent (AvA) is the linkable library that provides a means for the AvSv to exchange information with system components overseen by the process in which this library is planted. It does not run as a separate thread.
The AvA implements the SAF Availability Management Framework API and provides the entry- point for accessing AMF functionality.
1.2.1.5Cluster Membership Agent
The Cluster Membership Agent (CLA) is a linkable library that enables AvSv to provide information about nodes in the cluster to the process in which it is linked. It does not run as a separate thread.
The CLA implements the SAF Cluster Membership Service Library functionality and provides an entry point to the SAF CLM functionality.
1.2.2Compliance Report
Availability Service conforms to the Application Interface specifications mentioned in the following SAF documents:
z
z
z
Table
Section | Description | Supported | Notes |
|
|
|
|
1 | Document Introduction | NA | Informational |
|
|
|
|
2 | Overview of the AIS | NA | Informational |
|
|
|
|
3 | Programming Model and Naming | Yes |
|
| Conventions |
|
|
|
|
|
|
16 | Availability Service Programmer’s Reference (6806800C44B) |