Você está na página 1de 44

OpenSAF Availability Management FrameworkOpenSAF Availability Service Release 34 Programmer's Reference December 2009May 2010

OpenSAF, 2008 GNU Lesser General Public License (LGPL)


Version 2.1, February 1999 Copyright 1991, 1999 Free Software Foundation, Inc. 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed. [This is the first released version of the Lesser GPL. It also counts as the successor of the GNU Library Public License, version 2, hence the version number 2.1.]

Preamble
The licenses for most software are designed to take away your freedom to share and change it. By contrast, the GNU General Public Licenses are intended to guarantee your freedom to share and change free software--to make sure the software is free for all its users. This license, the Lesser General Public License, applies to some specially designated software packages-typically libraries--of the Free Software Foundation and other authors who decide to use it. You can use it too, but we suggest you first think carefully about whether this license or the ordinary General Public License is the better strategy to use in any particular case, based on the explanations below. When we speak of free software, we are referring to freedom of use, not price. Our General Public Licenses are designed to make sure that you have the freedom to distribute copies of free software (and charge for this service if you wish); that you receive source code or can get it if you want it; that you can change the software and use pieces of it in new free programs; and that you are informed that you can do these things. To protect your rights, we need to make restrictions that forbid distributors to deny you these rights or to ask you to surrender these rights. These restrictions translate to certain responsibilities for you if you distribute copies of the library or if you modify it. For example, if you distribute copies of the library, whether gratis or for a fee, you must give the recipients all the rights that we gave you. You must make sure that they, too, receive or can get the source code. If you link other code with the library, you must provide complete object files to the recipients, so that they can relink them with the library after making changes to the library and recompiling it. And you must show them these terms so they know their rights. We protect your rights with a two-step method: (1) we copyright the library, and (2) we offer you this license, which gives you legal permission to copy, distribute and/or modify the library. To protect each distributor, we want to make it very clear that there is no warranty for the free library. Also, if the library is modified by someone else and passed on, the recipients should know that what they have is not the original version, so that the original author's reputation will not be affected by problems that might be introduced by others.

Page 2 of 44

OpenSAF Availability Service

Finally, software patents pose a constant threat to the existence of any free program. We wish to make sure that a company cannot effectively restrict the users of a free program by obtaining a restrictive license from a patent holder. Therefore, we insist that any patent license obtained for a version of the library must be consistent with the full freedom of use specified in this license. Most GNU software, including some libraries, is covered by the ordinary GNU General Public License. This license, the GNU Lesser General Public License, applies to certain designated libraries, and is quite different from the ordinary General Public License. We use this license for certain libraries in order to permit linking those libraries into non-free programs. When a program is linked with a library, whether statically or using a shared library, the combination of the two is legally speaking a combined work, a derivative of the original library. The ordinary General Public License therefore permits such linking only if the entire combination fits its criteria of freedom. The Lesser General Public License permits more lax criteria for linking other code with the library. We call this license the "Lesser" General Public License because it does Less to protect the user's freedom than the ordinary General Public License. It also provides other free software developers Less of an advantage over competing non-free programs. These disadvantages are the reason we use the ordinary General Public License for many libraries. However, the Lesser license provides advantages in certain special circumstances. For example, on rare occasions, there may be a special need to encourage the widest possible use of a certain library, so that it becomes a de-facto standard. To achieve this, non-free programs must be allowed to use the library. A more frequent case is that a free library does the same job as widey used non-free libraries. In this case, there is little to gain by limiting the free library to free software only, so we use the Lesser General Public License. In other cases, permission to use a particular library in non-free programs enables a greater number of people to use a large body of free software. For example, permission to use the GNU C Library in non-free programs enables many more people to use the whole GNU operating system, as well as its variant, the GNU/Linux operating system. Although the Lesser General Public License is Less protective of the users' freedom, it does ensure that the user of a program that is linked with the Library has the freedom and the wherewithal to run that program using a modified version of the Library. The precise terms and conditions for copying, distribution and modification follow. Pay close attention to the difference between a "work based on the library" and a "work that uses the library". The former contains code derived from the library, whereas the latter must be combined with the library in order to run.

TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION

Page 3 of 44

OpenSAF Availability Management Framework

0. This License Agreement applies to any software library or other program which contains a notice placed by the copyright holder or other authorized party saying it may be distributed under the terms of this Lesser General Public License (also called "this License"). Each licensee is addressed as "you". A "library" means a collection of software functions and/or data prepared so as to be conveniently linked with application programs (which use some of those functions and data) to form executables. The "Library", below, refers to any such software library or work which has been distributed under these terms. A "work based on the Library" means either the Library or any derivative work under copyright law: that is to say, a work containing the Library or a portion of it, either verbatim or with modifications and/or translated straightforwardly into another language. (Hereinafter, translation is included without limitation in the term "modification".) "Source code" for a work means the preferred form of the work for making modifications to it. For a library, complete source code means all the source code for all modules it contains, plus any associated interface definition files, plus the scripts used to control compilation and installation of the library. Activities other than copying, distribution and modification are not covered by this License; they are outside its scope. The act of running a program using the Library is not restricted, and output from such a program is covered only if its contents constitute a work based on the Library (independent of the use of the Library in a tool for writing it). Whether that is true depends on what the Library does and what the program that uses the Library does.

1. You may copy and distribute verbatim copies of the Library's complete source code as you receive it, in any medium, provided that you conspicuously and appropriately publish on each copy an appropriate copyright notice and disclaimer of warranty; keep intact all the notices that refer to this License and to the absence of any warranty; and distribute a copy of this License along with the Library. You may charge a fee for the physical act of transferring a copy, and you may at your option offer warranty protection in exchange for a fee You may modify your copy or copies of the Library or any portion of it, thus forming a work based on the Library, and copy and distribute such modifications or work under the terms of Section 1 above, provided that you also meet all of these conditions:

a) The modified work must itself be a software library. b) You must cause the files modified to carry prominent notices stating that you changed the files and the date of any change. c) You must cause the whole of the work to be licensed at no charge to all third parties under the terms of this License. d) If a facility in the modified Library refers to a function or a table of data to be supplied by an application program that uses the facility, other than as an argument passed when the facility is invoked, then you must make a good

Page 4 of 44

OpenSAF Availability Management Framework

faith effort to ensure that, in the event an application does not supply such function or table, the facility still operates, and performs whatever part of its purpose remains meaningful. (For example, a function in a library to compute square roots has a purpose that is entirely well-defined independent of the application. Therefore, Subsection 2d requires that any application-supplied function or table used by this function must be optional: if the application does not supply it, the square root function must still compute square roots.) These requirements apply to the modified work as a whole. If identifiable sections of that work are not derived from the Library, and can be reasonably considered independent and separate works in themselves, then this License, and its terms, do not apply to those sections when you distribute them as separate works. But when you distribute the same sections as part of a whole which is a work based on the Library, the distribution of the whole must be on the terms of this License, whose permissions for other licensees extend to the entire whole, and thus to each and every part regardless of who wrote it. Thus, it is not the intent of this section to claim rights or contest your rights to work written entirely by you; rather, the intent is to exercise the right to control the distribution of derivative or collective works based on the Library. In addition, mere aggregation of another work not based on the Library with the Library (or with a work based on the Library) on a volume of a storage or distribution medium does not bring the other work under the scope of this License. 3. You may opt to apply the terms of the ordinary GNU General Public License instead of this License to a given copy of the Library. To do this, you must alter all the notices that refer to this License, so that they refer to the ordinary GNU General Public License, version 2, instead of to this License. (If a newer version than version 2 of the ordinary GNU General Public License has appeared, then you can specify that version instead if you wish.) Do not make any other change in these notices. Once this change is made in a given copy, it is irreversible for that copy, so the ordinary GNU General Public License applies to all subsequent copies and derivative works made from that copy. This option is useful when you wish to copy part of the code of the Library into a program that is not a library.

4. You may copy and distribute the Library (or a portion or derivative of it, under Section 2) in object code or executable form under the terms of Sections 1 and 2 above provided that you accompany it with the complete corresponding machine-readable source code, which must be distributed under the terms of Sections 1 and 2 above on a medium customarily used for software interchange. If distribution of object code is made by offering access to copy from a designated place, then offering equivalent access to copy the source code from the same place satisfies the requirement to distribute the source code, even though third parties are not compelled to copy the source along with the object code. 5. A program that contains no derivative of any portion of the Library, but is designed to work with the Library by being compiled or linked with it, is called a "work that uses the Library". Such a work, in isolation, is not a derivative work of the Library, and therefore falls outside the scope of this License.

Page 5 of 44

OpenSAF Availability Management Framework

However, linking a "work that uses the Library" with the Library creates an executable that is a derivative of the Library (because it contains portions of the Library), rather than a "work that uses the library". The executable is therefore covered by this License. Section 6 states terms for distribution of such executables. When a "work that uses the Library" uses material from a header file that is part of the Library, the object code for the work may be a derivative work of the Library even though the source code is not. Whether this is true is especially significant if the work can be linked without the Library, or if the work is itself a library. The threshold for this to be true is not precisely defined by law. If such an object file uses only numerical parameters, data structure layouts and accessors, and small macros and small inline functions (ten lines or less in length), then the use of the object file is unrestricted, regardless of whether it is legally a derivative work. (Executables containing this object code plus portions of the Library will still fall under Section 6.) Otherwise, if the work is a derivative of the Library, you may distribute the object code for the work under the terms of Section 6. Any executables containing that work also fall under Section 6, whether or not they are linked directly with the Library itself. 6. As an exception to the Sections above, you may also combine or link a "work that uses the Library" with the Library to produce a work containing portions of the Library, and distribute that work under terms of your choice, provided that the terms permit modification of the work for the customer's own use and reverse engineering for debugging such modifications. You must give prominent notice with each copy of the work that the Library is used in it and that the Library and its use are covered by this License. You must supply a copy of this License. If the work during execution displays copyright notices, you must include the copyright notice for the Library among them, as well as a reference directing the user to the copy of this License. Also, you must do one of these things: a) Accompany the work with the complete corresponding machine-readable source code for the Library including whatever changes were used in the work (which must be distributed under Sections 1 and 2 above); and, if the work is an executable linked with the Library, with the complete machine-readable "work that uses the Library", as object code and/or source code, so that the user can modify the Library and then relink to produce a modified executable containing the modified Library. (It is understood that the user who changes the contents of definitions files in the Library will not necessarily be able to recompile the application to use the modified definitions.) b) Use a suitable shared library mechanism for linking with the Library. A suitable mechanism is one that (1) uses at run time a copy of the library already present on the user's computer system, rather than copying library functions into the executable, and (2) will operate properly with a modified version of the library, if the user installs one, as long as the modified version is interface-compatible with the version that the work was made with.

c) Accompany the work with a written offer, valid for at least three years, to give the same user the materials specified in Subsection 6a, above, for a charge no more than the cost of performing this distribution.

Page 6 of 44

OpenSAF Availability Management Framework

d) If distribution of the work is made by offering access to copy from a designated place, offer equivalent access to copy the above specified materials from the same place. e) Verify that the user has already received a copy of these materials or that you have already sent this user a copy. For an executable, the required form of the "work that uses the Library" must include any data and utility programs needed for reproducing the executable from it. However, as a special exception, the materials to be distributed need not include anything that is normally distributed (in either source or binary form) with the major components (compiler, kernel, and so on) of the operating system on which the executable runs, unless that component itself accompanies the executable. It may happen that this requirement contradicts the license restrictions of other proprietary libraries that do not normally accompany the operating system. Such a contradiction means you cannot use both them and the Library together in an executable that you distribute. 7. You may place library facilities that are a work based on the Library side-by-side in a single library together with other library facilities not covered by this License, and distribute such a combined library, provided that the separate distribution of the work based on the Library and of the other library facilities is otherwise permitted, and provided that you do these two things: a) Accompany the combined library with a copy of the same work based on the Library, uncombined with any other library facilities. This must be distributed under the terms of the Sections above. b) Give prominent notice with the combined library of the fact that part of it is a work based on the Library, and explaining where to find the accompanying uncombined form of the same work. 8. You may not copy, modify, sublicense, link with, or distribute the Library except as expressly provided under this License. Any attempt otherwise to copy, modify, sublicense, link with, or distribute the Library is void, and will automatically terminate your rights under this License. However, parties who have received copies, or rights, from you under this License will not have their licenses terminated so long as such parties remain in full compliance. 9. You are not required to accept this License, since you have not signed it. However, nothing else grants you permission to modify or distribute the Library or its derivative works. These actions are prohibited by law if you do not accept this License. Therefore, by modifying or distributing the Library (or any work based on the Library), you indicate your acceptance of this License to do so, and all its terms and conditions for copying, distributing or modifying the Library or works based on it. 10. Each time you redistribute the Library (or any work based on the Library), the recipient automatically receives a license from the original licensor to copy, distribute, link with or modify the Library subject to these terms and conditions. You may not impose any further restrictions on the recipients' exercise of the rights granted herein. You are not responsible for enforcing compliance by third parties with this License. 11. If, as a consequence of a court judgment or allegation of patent infringement or for any other reason (not limited to patent issues), conditions are imposed on you (whether by court order, agreement or otherwise) that contradict the conditions of this License, they do not excuse you from the conditions of this License. If you cannot distribute so as to satisfy simultaneously your obligations under this License and any other pertinent obligations, then as a consequence you may not distribute the Library at all. For example, if a patent license would not permit

Page 7 of 44

OpenSAF Availability Management Framework

royalty-free redistribution of the Library by all those who receive copies directly or indirectly through you, then the only way you could satisfy both it and this License would be to refrain entirely from distribution of the Library. If any portion of this section is held invalid or unenforceable under any particular circumstance, the balance of the section is intended to apply, and the section as a whole is intended to apply in other circumstances.

It is not the purpose of this section to induce you to infringe any patents or other property right claims or to contest validity of any such claims; this section has the sole purpose of protecting the integrity of the free software distribution system which is implemented by public license practices. Many people have made generous contributions to the wide range of software distributed through that system in reliance on consistent application of that system; it is up to the author/donor to decide if he or she is willing to distribute software through any other system and a licensee cannot impose that choice. This section is intended to make thoroughly clear what is believed to be a consequence of the rest of this License. 12. If the distribution and/or use of the Library is restricted in certain countries either by patents or by copyrighted interfaces, the original copyright holder who places the Library under this License may add an explicit geographical distribution limitation excluding those countries, so that distribution is permitted only in or among countries not thus excluded. In such case, this License incorporates the limitation as if written in the body of this License. 13. The Free Software Foundation may publish revised and/or new versions of the Lesser General Public License from time to time. Such new versions will be similar in spirit to the present version, but may differ in detail to address new problems or concerns. Each version is given a distinguishing version number. If the Library specifies a version number of this License which applies to it and "any later version", you have the option of following the terms and conditions either of that version or of any later version published by the Free Software Foundation. If the Library does not specify a license version number, you may choose any version ever published by the Free Software Foundation. 14. If you wish to incorporate parts of the Library into other free programs whose distribution conditions are incompatible with these, write to the author to ask for permission. For software which is copyrighted by the Free Software Foundation, write to the Free Software Foundation; we sometimes make exceptions for this. Our decision will be guided by the two goals of preserving the free status of all derivatives of our free software and of promoting the sharing and reuse of software generally. NO WARRANTY 15. BECAUSE THE LIBRARY IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY FOR THE LIBRARY, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES PROVIDE THE LIBRARY "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE LIBRARY IS WITH YOU. SHOULD THE LIBRARY PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION.

Page 8 of 44

OpenSAF Availability Management Framework

16. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR REDISTRIBUTE THE LIBRARY AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE LIBRARY (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE LIBRARY TO OPERATE WITH ANY OTHER SOFTWARE), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

END OF TERMS AND CONDITIONS How to Apply These Terms to Your New Libraries
If you develop a new library, and you want it to be of the greatest possible use to the public, we recommend making it free software that everyone can redistribute and change. You can do so by permitting redistribution under these terms (or, alternatively, under the terms of the ordinary General Public License). To apply these terms, attach the following notices to the library. It is safest to attach them to the start of each source file to most effectively convey the exclusion of warranty; and each file should have at least the "copyright" line and a pointer to where the full notice is found. <one line to give the library's name and an idea of what it does.> Copyright <year> <name of author>

This library is free software; you can redistribute it and/or modify it under the terms of the GNU Lesser General Public License as published by the Free Software Foundation; either version 2.1 of the License, or (at your option) any later version. This library is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU Lesser General Public License for more details. You should have received a copy of the GNU Lesser General Public License along with this library; if not, write to the Free Software Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA Also add information on how to contact you by electronic and paper mail.

Page 9 of 44

OpenSAF Availability Management Framework

You should also get your employer (if you work as a programmer) or your school, if any, to sign a "copyright disclaimer" for the library, if necessary. Here is a sample; alter the names: Yoyodyne, Inc., hereby disclaims all copyright interest in the library `Frob' (a library for tweaking knobs) written by James Random Hacker. signature of Ty Coon, 1 April 1990 Ty Coon, President of Vice

Page 10 of 44

OpenSAF Availability Management Framework

Contents
1 ABOUT THIS MANUAL........................................................................................ 12
1.1 Overview of Contents ............................................................................................................................................12 1.2 Abbreviations ..........................................................................................................................................................12 1.3 Conventions .............................................................................................................................................................12 1.4 Comments and Suggestions ..................................................................................................................................13

2 OVERVIEW............................................................................................................ 14
2.1 Availability Management Framework Overview ..............................................................................................14 2.2 Models and Concepts .............................................................................................................................................15 2.2.1 Service Structure Overview .......................................................................................................................15 2.2.1.1 Availability Management Framework Director .................................................................................16 2.2.1.2 Availability Management Framework Node Director ........................................................................16 2.2.1.3 Availability Management Framework Agent .....................................................................................17 2.2.1.4 Availability Management Framework Watchdog...............................................................................17 2.2.2 Compliance Report ....................................................................................................................................17 2.2.3 Dependencies .............................................................................................................................................21 2.2.3.1 Service Dependencies .........................................................................................................................21 2.2.3.2 Library Dependencies .........................................................................................................................22 2.2.4 Service Definition Documents ...................................................................................................................22 2.2.5 Implementation Notes ................................................................................................................................23

3 MANAGEMENT INTERFACE................................................................................ 24
3.1 Overview ..................................................................................................................................................................24 3.1.1 XML ...........................................................................................................................................................24 3.2 Command Line Interface.......................................................................................................................................24

4 SAMPLE APPLICATION.......................................................................................26
4.1 Sample Basic AMF Demo.......................................................................................................................................26 4.1.1 Introduction.................................................................................................................................................26 4.1.2 Bringing Up Sample AMF Demo..............................................................................................................28 4.1.2.1 Building and Installing the Sample AMF Demo Application:............................................................28 4.1.2.2 Expected Sample AMF Application Output .......................................................................................29

Page 11 of 44

OpenSAF Availability Management Framework

List of Tables
TABLE 1 COMPLIANCE TABLE - AVAILABILITY MANAGEMENT FRAMEWORK ..................................................................................................................................17 TABLE 2 AVAILABILITY MANAGEMENT FRAMEWORK - DEPENDENCIES.......21

Page 12 of 44

OpenSAF Availability Management Framework

List of Figures
FIGURE 1 AVAILABILITY MANAGEMENT FRAMEWORK - SUBPARTS.............17

Page 13 of 44

OpenSAF Availability Management Framework

About this Manual

1.1 Overview of Contents


This manual is divided into the following chapters and appendices. Overview Ddescribes the functionality and main features and modules of the AvailabilityAvailability Management Service Management Interface Ddescribes how to configure the various logical entities of the AvailabilityAvailability Management Service Sample Application Ddescribes the sample application which illustrates how to use functionality of the AvailabilityAvailability Management Service. The sample application is delivered with the OpenSAF software. Service.Availability ManagementAvailability Error: Reference source not found Provides references to further documentation and specifications that are related to OpenSAF and the For information on the list of OpenSAF technical documentation and the SAF specifications, refer the Related Documentation section of the OpenSAF Overview Release 4 Programmers' Reference.

1.2 Abbreviations
This document uses the following abbreviations:
Abbreviation AMF AvA AMFD AMFND AMFWD CLMSv IMMSv DTSv LOGSv NTFSv MBCSv MDS Definition Availability Management Framework Availability Agent AMF Director AMF Node Director AMF Watchdog Cluster Member ship Service Information Management Service Distributed Tracing Service Log Service Notification Service Message based Checkpoint Service Message Distribution Service

Page 14 of 44

OpenSAF Availability Management Framework

Abbreviation LEAP

Definition Layered Environment for Accelerated Portability

1.3 Conventions
The following table describes the conventions used throughout this manual.
Notation 0x00000000 Description Typical notation for hexadecimal numbers (digits are 0 through F), for example used for addresses and offsets Same for binary numbers (digits are 0 and 1) Used to emphasize a word Used for on-screen output and code related elements or commands in body text Used to characterize user input and to separate it from system output Used for references and for table and figure descriptions Notation for selecting a submenu Notation for variables and keys Notation for software buttons to click on the screen and parameter description Repeated item for example node 1, node 2, ..., node 12 Omission of information from example/command that is necessary at the time being Ranges, for example: 0..4 means one of the integers 0,1,2,3, and 4 (used in registers) Logical OR No danger encountered. Pay attention to important information

0b0000 bold Screen Courier + Bold Reference File > Exit <text> [text] ...

... .. |

Page 15 of 44

OpenSAF Availability Management Framework

1.4 Comments and Suggestions


If you have any comments about this document, you may submit your feedback and input to the following address: info@opensaf.org

Page 16 of 44

OpenSAF Availability Management Framework

2 Overview
2.1 Availability ServiceManagement Framework Overview
The OpenSAF Availability ServiceManagement Framework (AMF)mfvSv is the core service of the OpenSAF software. It provides service availability to applications by coordinating the redundant resources in a cluster to provide a system with no single point of failure. It provides high-availability mechanisms to the application software it manages. These include life-cycle management of application software, fault detection, fault isolation, escalation, recovery, and repair. The AvSvAmfMF functionality is a compliant implementation of Service Availability Forums Application Interface Specification of Availability Management Framework (SAI-AIS-AMFB.01.01 and partly SAI-AIS-AMF-B.04.01 for OI implementation according to SAI-AIS-IMMA.02.01). The AvailabilityAvailability Management FrameworkService (AMFAmfAvSv) provides the following functionality: Leverage the SAF "System Description and Conceptual Model" Honor the Availability Management Framework" API (only B.01.01) . Depends on CLM service and honors CLM track callbacks and takes appropriates actions for nodes leaving/joining the cluster. As OI implements all the classes defined in UML model of SAI-AIS-B.04.01 specification.

The AvSvAMFmf maintains a software system model database which captures SAFdescribed logical entities and their relationships to each other. The software system model database is initially configured from data contained in the System Description file. Through time the system model will modify due to changing system realities and administrative actions. The SAF logical entities related in the system model include components which normalize the view of physical resources such as processes, drivers or devices. Components are grouped into Service Units according to fault dependencies that exist among them. Service Units of the same type are grouped into Service Groups (SG) which exhibit particular redundancy

Page 17 of 44

OpenSAF Availability Management Framework

modeling characteristics. Service Units within a SG are assigned with Service Instances (SI) and given a High Availability state of active and standby on behalf of SI. Further functionality provided by AvSvAMFmf includes: Automatic and administrative means to instantiate, terminate and restart resources Automatic and administrative means to manage or reflect Service Group, Service Unit, Service Instance and Resource state To perform admin operations on the objects(logical entities) manged by AvSvAMFmf Health-check services to probe and prevent system trauma that lead to faults Fault recovery mechanisms to fail-over SIs which maintain service availability in case of system trauma Fault repair mechanisms to restore failed components

The AvSvAMFmf itself cannot be a single-point of failure. It provides its own internal scheme and mechanisms to protect itself from its own failure.

2.2 Models and Concepts


This chapter provides information on: Service Structure and architecture Compliance to SAF standard Service Dependencies References to SAF documents which provide details about the service functionality Service Extensions Implementation Notes Configuration

2.2.1 Service Structure Overview AvailabilityAvailability Management FrameworkService is made up of the following distributed sub-parts: Availability Management FrameworkAMF Director Availability Management FrameworkAMF Node Director

Page 18 of 44

OpenSAF Availability Management Framework

Availability Management Framework Agent Availability Management FrameworkAMF Watchdog

Page 19 of 44

OpenSAF Availability Management Framework

Figure 1 Availability Management Framework - Subparts

2.2.1.1 Availability Management FrameworkAMF Director The Availability Director (AMFD) maintains the entire system model, consisting of nodes, the Service Groups (SG), their constituent Service Units (SUs), their constituent components, and their corresponding component service instance (CSI) and service instances (SIs) that are in the system. There is an active and a standby instance of the AMFD in a system. The AMFD runs on the system controller node. Its main tasks include fault detection, isolation and recovery procedures as defined in the SAF AMF. Any problems and failures on a component that cannot be handled locally, are prompted to the Availability Director which controls and triggers the isolation of the affected component and, if possible, the activation of a stand-by component. 2.2.1.2 Availability Management Framework NodeNodeAMF Director The Availability Node Director (AMFND) resides on each system node and its main task is to maintain the node-scoped part of the software system model described above.

Page 20 of 44

OpenSAF Availability Management Framework

The AMFND coordinates local fault identification and repair of components and furthermore facilitates any wishes it receives from the Availability Director. The AMFND watches for components arriving or leaving the system and summarizes this information in a Service Unit (SU) presence state, and keeps the AMFD informed about the current status and changes. The AMFND is capable of disengaging, restarting and destroying any component within its scope. This may occur according to AMFD instructions or as a result of an administrative action or automatically triggered by policies. 2.2.1.3 Availability Management Framework Agent The Availability Management Framework Agent (AMFvA) is the linkable library that provides a means for the AMF 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 AMFAAvA implements the SAF Availability Management Framework API and provides the entry-point for accessing AMF functionality. 2.2.1.4 Availability Management FrameworkMF Watchdog The AMF Watchdog is a component that guarantees the high availability of the AMF node director by monitoring its health at regular intervals through AMF invoked health check. 2.2.2 Compliance Report AvailabilityAvailability Management Framework conforms to the Application Interface specifications mentioned in the following SAF documents: SAI-AIS Volume 1: Overview and Models (SAI-AIS-B.01.01) SAI-AIS Volume 2: Availability Management Framework (SAI-AIS-AMF-B.01.01) SAI-AIS Volume 3: Cluster Membership Service (SAI-AIS-CLM-B.01.01) Availability Management Framework (SAI-AIS-AMF-B.01.01) with AMF model SAI-AIS-AMFB.04.01. Cluster Membership Service (SAF-AIS-CLM-B.04.01) Information Model Management Service (SAI-AIS-IMM-A.02.01) Notification Service (SAI-AIS-NTF-A.01.01)

Table 1 Compliance Table - Availability Service, SAI-AIS Volume 1: Overview and Models

Page 21 of 44

OpenSAF Availability Management Framework

Section 1 2 3

Description Document Introduction Overview of the AIS Programming Model and Naming Conventions

Supported NA NA Yes

Notes Informational Informational

Table 2 Compliance Table - Availability Service, SAI-AIS Volume 1: Overview and Models Section 4 4.1 Description System Description and Conceptual Model Physical Entities Supporte d Yes Yes Notes

AvSv supports management of hardware resources only when they are modeled using proxy components Informational

4.2 5

Logical Entities AIS Abbreviations, Concepts, and Terminology

Yes NA

Table 3 Compliance Table - Availability Service, SAI-AIS Volume 2: Availability Management Framework Section 1 2 3 3.1 Description Document Introduction Overview System Description and System Model Logical Entities Support NA NA Yes Yes Constituent sub-sections that are only partially supported or not supported are mentioned below. Note that the rest of the sub-sections are fully supported. Notes Informational Informational

3.1.2

Components

Yes

Page 22 of 44

OpenSAF Availability Management Framework

Section 3.1.2.3

Description Proxy and Proxied Components

Support Yes

Notes External Components not supported

3.1.4

Service Units

Yes

3.2 3.3

State Models Fail-over and Switchover

Yes Yes AvSv supports switchover of service instances caused due to administrative operations specified in SAAIS-AMFB.01.01 and some proprietary switchover mechanisms not specified in the document.

3.4 3.5

Administrative Operations Possible Combination of States for Service Units Component Capability Model

Yes Yes

3.6 3.7

Yes Yes Constituent sub-sections that are only partially supported or not supported are mentioned below. Note that the rest of the sub-sections are fully supported. AMF currently does not support the failback option.

Service Group Redundancy Model

3.7.1 3.7.2 3.7.3

Common Characteristics 2N Redundancy Model N+M Redundancy Model

Yes Yes Yes

SIs based on saAmfSIRank are assigned to SUs based on saAmfSURank till each SU is assigned saAmfSGMaxActiveSIsperSU number of SIs. If there are SIs still left without assignments than the SUs will be assigned with SIs up to their capability level. The standby assignments of all the SIs assigned to an active SU will be assigned to the same standby SU. The saAmfSGMaxActiveSIsperSU

Page 23 of 44

OpenSAF Availability Management Framework

Section

Description

Support

Notes can be leveraged by the configurator to get the required spread of SI assignments to the SUs.

3.7.4

Yes

N-Way Redundancy Model

SIs based on saAmfSIRank are assigned to SU based on saAmfSUsperSIRankTabl e till all the SIs are assigned an active assignment. Then each SI based on saAmfSIRank is assigned fully to SUs as standby before the next SI is assigned as standby. When an SU fails and the system is in a degraded state, AMF may ignore the saAmfCompNumMaxActiveCsi attribute of a component and assign more active assignments than the permitted number. This policy has been adopted to maintain service continuity for as many SIs as possible even when the system is in a degraded state. AMF assigns an SI to SU only after the SI with better saAmfSIRank is fully assigned.

3.7.5 N-Way Active Redundancy Model 3.7.6 3.7.7

Yes

No Redundancy Model The Effect of Administrative Operations on Service Instance Assignments Component Capability Model and Service Group Redundancy Model Dependencies Among SIs, Component Service Instances, and Components

Yes Yes

3.8

Yes

3.9

Yes

Constituent sub-sections that are only partially supported or not supported are mentioned below. Note that the rest of the sub-sections are fully supported. Sample configuration of SI-SI dependencies are captured in AppConfig.xml file at <install_dir>/samples/ avsv directory.

3.9.1.1

Dependencies Between SIs when Assigning a Service Unit Active for a Service Instance

Yes

Page 24 of 44

OpenSAF Availability Management Framework

Section

Description

Support

Notes This configuration with in comments is just for the user reference. Not supported for N-Way redundancy model.Not supported

3.9.1.2

Impact of Disabling a Service Instance on the Dependent Service Instances Dependencies Between Component Service Instances of the Same Service Instance Dependencies Between Components Component Monitoring

YesNo

3.9.1.3

Yes

3.9.2 3.10 3.11

Yes Yes Yes Constituent sub-sections that are only partially supported or not supported are mentioned below. Note that the rest of the sub-sections are fully supported. AMF currently does both the component failover and SU failover after doing quiesced of the enabled active components in the SU. Node failover and switch over are done after doing quiesced of all the enabled active components in the node. In all the above cases the components that did not fail in the SUs are not terminated. Only automatic repair by component restart is supported.

Error Detection, Recovery, Repair, and Escalation Policy 3.11.1.3 Yes

Recovery

3.11.1.4 Repair 3.11.1.5 3.11.2.1 3.11.2.2 3.11.2.3

Yes

Recovery Escalation Recommended Recovery Action Escalations of Levels 1 and 2 Escalations of Levels 3

Yes Yes Yes Yes Cluster Reset is not supported.

Page 25 of 44

OpenSAF Availability Management Framework

Section 4

Description Local Component Life Cycle Management Interfaces Availability Management Framework API Basic Operational Scenarios Implementation of CLC Interfaces

Support Yes

Notes

Yes

6 Appendi xA

Yes Yes

Table 4 Compliance Table - Availability Service, SAI-AIS Volume 3: Cluster Membership Service

2.2.3 Dependencies This section describes dependencies between the AMFSv and other services and between the AMFSv and libraries. 2.2.3.1 Service Dependencies The following table lists other OpenSAF services and how the AvailabilityAvailability Management FrameworkService depends on them.
Table 5 AvailabilityAvailability Management ServiceFramework - Dependencies Service Layered Enhanced Accelerated Portability (LEAP) Dependency Availability Management Framework uses LEAP for portability. It uses the memory manager, timers, encode-decode utility, and handle manager services provided by LEAP. Interaction between the subparts of AMFAmfAvSv takes place using MDS messaging. AMF ServiceAvailability Management uses DTSv to log debug messages and to report informational events. AMF ServiceAvailability Management uses CLMSv for cluster membership of the nodes. AMF ServiceAvailability Management uses NTFSv to send all alarms and notifications generated by it. AMF uses saflog to log important data.

Message Distribution Service (MDS) Distributed Tracing Service (DTSv) Cluster Membership Service(CLMSv) Notification Service (NTFSv)

Log Service (LOGSv)

Page 26 of 44

OpenSAF Availability Management Framework

Service Information Model Management Service (IMMSv) Message Based Checkpoint Service (MBCSv)

Dependency AMF uses IMMSv to manage/configure objects defined in the AMF The active AMFD uses MBCSv to checkpoint the state information with a standby AMFD.

2.2.3.2 Library Dependencies The AvSvAMFmf library, libSaAmf.so depends on: libopensaf_core.so

2.2.4 Service Definition Documents To know more about the AvailabilityAvailability Management FrameworkService of OpenSAF, refer following documents. They provide the service definition for the AvailabilityAvailability Management FrameworkService. aisOverview B0101: This contains information about SAF AIS based system. aisAmf B0101: This contains information about Availability Management Framework (AMF) in SAF AIS SAI-AIS-AMF-B.04.01: This contains information about UML model of AMF logical entities.

The above documents are available at http://www.saforum.org/ . The following information can be found in the referenced document: Service concept definitions and descriptions Functional behaviors and relationships A complete set of service data types exposed to the service user The set of Service APIs available to the service user

An application managed by AMF is provided with APIs to perform the following: Component registration and unregistration Passive monitoring of processes of a component Component health monitoring Component service instance management Component life cycle management

Page 27 of 44

OpenSAF Availability Management Framework

Protection group management Error reporting

An application also provides certain "Component Life Cycle" commands that are used by AvSvAMFmf to instantiate, terminate, and clean it up. Applications can also use the APIs specified in Section 3 of the SAI-AIS-CLM-B.01.01 document to track and get information related to the nodes in the cluster. 2.2.5 Implementation Notes The MIB rows whose "row status" is "not active" are lost on failover or switchover of the active system management host. The configuration being performed when the failover/switchover occurs should be redone. Some of the Administrative operations are not supported on the middleware logical entities(like SU, SI, SG etc.). Administrative operations on AMF node will not affect the the middleware SUs. AMF handles CLM track callbacks received due to any administrative operations on CLM in the same way it handles administrative operations on a AMF node. Please refer Compliance report in section 2.2.2 for further. SI-swap issued on middleware SI of controller will cause the controller switchover.

2.2.6 Configuration An application managed by AvSvAMFmf to provide high service availability must be modeled in terms of logical entities in accordance with the structure of the "System Model". Further, the

Page 28 of 44

OpenSAF Availability Management Framework

application must implement the state models and callback interfaces according to the AMF specification. AvailabilityAvailability Management ServiceFramework provides a management interface through IMMSv to configure the System Model and to perform run-time administrative operations. The System Model configuration and run-time administrative operations can be done using utilities provided by IMM.

Page 29 of 44

OpenSAF Availability Management Framework

3 Management Interface
3.1 Overview
The AvailabilityAvailability Management FrameworkService is configured through IMMSv. Runtime administrative operations are performed using IMM utilities. 3.1.1 XML OpenSAF uses a IMM defined XML schema for configuring entities in the AMF system model. The XML syntax is described in the SAI-AIS-IMM-XSD-A.01.01.xsd (the schema file) and the OpenSAF System Description Programers Reference. The imm.xml that is generated by using immutil tools is used as the initial configuration for bringing up the system. In addition any user defined application configuration that is given as a xml file can be merged with the default imm.xml to bring up the system with the configured user applications. Please refer relevant documentation on how to generate/merge imm.xml file.

3.2 Command Line Interface


The utilities such as immadm, immcfg provided by IMM can be used to configure logical entities managed by AMF. Using the given commands user can create/modify/delete any object or attributes of an object as well perform administrative actions as defined in the B.04.01 AMFspecification. To configure a new application first define the Appconfig.xml consisting the object definitions and then type the following command at shell #>immcfg -f Appconfig.xml To perform administrative operations on an object managed by AMF: #>amf-adm <lock|unlock|lock-in|unlock-in|shutdown|restart|siswap|sg-adjust|repaired|eam-start|eam-stop> <object DN> alternatively, #>immadm -o <operation id> <object DN>

Page 30 of 44

OpenSAF Availability Management Framework

Note: Please Rrefer compliance report to find what all administrative operations are supported on each of the logical entities in AMF.

Some examples are provided belowhere on how to modify attributes of various objects managed by AMF:

#>immcfg -a saAmfNodeSuFailoverMax=7 safAmfNode=Node01,safAmfCluster=1 change one attribute for one objectCreate one object, setting one initialized attribute. #>immcfg -c SaAmfApplication -a saAmfAppType=Test safApp=myTestApp1 Delete one object. #>immcfg -d safAmfNode=Node01,safAmfCluster=1 Delete two objects. #>immcfg -d safAmfNode=Node01,safAmfCluster=1 safAmfNode=Node02,safAmfCluster=1 Add a value to an attribute. #>immcfg -a saAmfNGNodeList+=safAmfNode=PL_2_6,safAmfCluster=myAmfCluster safAmfNodeGroup=PLs,safAmfCluster=myAmfCluster Remove a value from an attribute. #>immcfg -a saAmfNGNodeList=safAmfNode=PL_2_6,safAmfCluster=myAmfCluster safAmfNodeGroup=PLs,safAmfCluster=myAmfCluster

Note: Refer SAI-AIS-AMF-B.04.01 UML model to find out what attibutes can be modified through runtime. Support for some of the attributes modification is only supported in a particular administrative state of its parent object. Refer compliance report for more information.

To perform controller swithover #>amf-adm si-swap safSi=SC-2N,safApp=OpenSAF or,

Page 31 of 44

OpenSAF Availability Management Framework

#>immadm -o 7 safSi=SC-2N,safApp=OpenSAF

Page 32 of 44

OpenSAF Availability Management Framework

4 Sample Application
4.1 Sample Basic AvSvAMFmf Demo
4.1.1 Introduction The sample AMFAmfAvSv application i is run in a 2N-redundancy model. The active entity. When it fails, the standby entity becomes active and resumes counting from where the previous active entity failed. The sample application shows you how to use some APIs defined in the SAI-AIS AMF service. It also demonstrates the following features: Passive monitoring The saAmfPmStart() function requests the Availability Management Framework (AMF) to start passive monitoring of specific errors, which may occur to a process and its descendents. Currently, only death of processes can be monitored. If one of the errors being monitored occurs for the process or one of its descendents, the AMF automatically report san error on the component identified by compName. The recommended recovery action will be set according to the recommendedRecovery parameter. Passive monitoring is done based on process ID (PID) of a component, which represents an application. If the process, for which passive monitoring was started, dies then AMF automatically recovers the error as per the recommended recovery specification in the API or application configuration if former is SA_AMF_NO_RECOMMENDATION. Passive monitoring can be started by any component for any other component on the same node. For more information about the API, refer AMF B.01.01 specification.

Protection Group tracking

A protection group for a specific component service instance is the group of components that component service instance has been assigned to. The name

Page 33 of 44

OpenSAF Availability Management Framework

of a protection group is the name of the component service instance that it protects. A protection group is a dynamic entity that changes when component service instances are assigned to, and removed from, components. By calling saAmfProtectionGroupTrack(), the AMF is requested to start tracking changes in the protection group associated with the component service instance, identified by csiName, or changes of attributes of any component in the protection group. These changes are notified via the invocation of the saAmfProtectionGroupTrackCallback() callback function, which must have been supplied when the process invoked the saAmfInitialize() call. Protection group tracking can be done for any CSI within the cluster. For more information about the API, refer AMF B.01.01 specification.

Component failover The saAmfComponentErrorReport() function reports an error and provides a recovery recommendation to the Availability Management Framework. The Availability Management Framework will react on the error report and carry out a recovery operation to retain the required availability of the component service instances supported by the erroneous component. The Availability Management Framework will not implement a weaker recovery action than that recommended by the error report, but the Availability Management Framework may decide to escalate to a higher recovery level. This is useful when application detects an internal error and wants AMF to perform the recovery action. For more information about the API, refer AMF B.01.01 specification.

AMF-invoked health check A component can request AMF to monitor the component by doing periodic health checks with the component. One way to do this is by saAmfHealthcheckStart() API. For more information about the API, refer AMF B.01.01 specification.

Configuration for the Sample Application

Page 34 of 44

OpenSAF Availability Management Framework

The configuration for the sample application is captured in the Appconfig-2N.xml. It comprises of the following entities: A service group (SG) that comprises 2 service units (SU) in a 2N-redundancy model Each SU contains a single component. A single service instance (SI) is configured to be assigned to the SG The two SUs come up in the payload nodes (safNode=PL-3 and safNode=PL-4 respectively) by default.

The sample application also provides scripts (available in <install_dir>/samples/avsvAmf directory) to control the component life cycle. amf_demo_script (to control CLC of the sample application).

4.1.2 Bringing Up Sample AvSv AMF Demo 4.1.2.1 Building and Installing the Sample AMF Demo Application:
To build the Sample AMF application on a node. 1. Copy the opensaf-samples-<version> -<architecture>.rpm and opensaf-devel-<version> -<architecture>.rpm to the any temporary directory on that node. 2. Install opensaf-samples-<version> -<architecture>.rpm and opensafdevel-<version> -<architecture>.rpm. rpm -ivh --nodeps opensaf-devel-<version> -<architecture>.rpm rpm -ivh --nodeps opensaf-samples-<version> -<architecture>.rpm
3. Go to /usr/share/opensaf/samples/ cd /usr/share/opensaf/samples/

4. ./bootstrap.sh 5. ./configure
6. Go to <install-dir>/samples/avsv/ cd <install-dir>/samples/avsv/ 7. Build the sample application.

Page 35 of 44

OpenSAF Availability Management Framework

make.

8. To Install the Sample AMF demo application: Package the demo executabe and script by running the following command ./amf_demo_package The above command generates amf_demo.tgz Copy amf_demo.tgz into root directory by running the following command cp amf_demo.tgz / 9. Extract the amf_demo.tgz in / directory 10. In the directoy /opt/amf_demo, you can find the executable amf_demo, and the script amf_demo_script . Set the execution permissions for both the files.

Page 36 of 44

OpenSAF Availability Management Framework

4.1.2.2 To run the sample application on the target architecture: Procedure 1. The given sample is made for a system which has at least one OpenSAF controller node and two payload nodes (safNode=PL-3 and safNode=PL-4). If you wish to run sample on other nodes then you need to replace the node names (PL-3 and PL-4) in the configuration (AppConfig-2N.xml). 2. Next you need to place the application's configuration on the system controller node. The configuration for the sample application is captured in AppConfig-2N.xml file in /usr/share/opensaf/samples/avsv/ location on the machine where opensaf samples rpm was installed. Please do read the comment s provied in Appconfig-2N.xml for further help. 3. Configure the application by typing the following on any of the nodes. #> immcfg -f Appconfig-2N.xml 4. By default the Sus configured for demo application are in locked-instantiation state, so they should be unlocked before they come up. #>amf-adm unlock-in safSu=SU1,safSg=AmfDemo,safApp=AmfDemo1 #>amf-adm unlock safSu=SU1,safSg=AmfDemo,safApp=AmfDemo1 #>amf-adm unlock-in safSu=SU2,safSg=AmfDemo,safApp=AmfDemo1 #>amf-adm unlock safSu=SU2,safSg=AmfDemo,safApp=AmfDemo1

5. After this the amf_demo should come up on the two configured nodes as active and standby instances, amf_demo logs into syslog messages.

4.1.2.2 Expected Sample AvSvAMF Application Output

For the active node: Apr 26 19:09:10 localhost amf_demo: ##############################################

Page 37 of 44

OpenSAF Availability Management Framework

Apr 26 19:09:10 localhost amf_demo: # Apr 26 19:09:10 localhost amf_demo: AvSvAmf Demo !!! # Apr 26 19:09:10 localhost amf_demo: #

# # # You are about to witness

Apr 26 19:09:10 localhost amf_demo: ############################################## Apr 26 19:09:10 localhost osafimmnd[29667]: Create implementer:<name:safCheckPointService, id:10, conn:321, node:2020f dead:0> Apr 26 19:09:10 localhost amf_demo: AMF thread entered

Apr 26 19:09:10 localhost amf_demo: AMF Initialization Done !!! Apr 26 19:09:10 localhost amf_demo: AmfHandle: ff900001

Apr 26 19:09:10 localhost amf_demo: AMF Selection Object Get Successful !!! Apr 26 19:09:10 localhost amf_demo: Component Name Get Successful !!! Apr 26 19:09:10 localhost amf_demo: CompName: safComp=AmfDemo,safSu=SU2,safSg=AmfDemo,safApp=AmfDemo1 Apr 26 19:09:10 localhost amf_demo: Component Registered !!!

Apr 26 19:09:20 localhost amf_demo: Dispatched 'CSI Set' Callback for Component: 'safComp=AmfDemo,safSu=SU2,safSg=AmfDemo,safApp=AmfDemo1' Apr 26 19:09:20 localhost amf_demo: CSIName: safCsi=AmfDemo,safSi=AmfDemo,safApp=AmfDemo1 HAState: Active CSIFlags: Add One Apr 26 19:09:20 localhost amf_demo: INVOKING saAmfHAStateGet() API !!! Apr 26 19:09:22 localhost amf_demo: CompName: safComp=AmfDemo,safSu=SU2,safSg=AmfDemo,safApp=AmfDemo1 CSIName: safCsi=AmfDemo,safSi=AmfDemo,safApp=AmfDemo1 HAState: Active Apr 26 19:09:22 localhost amf_demo: DEMONSTRATING AMF-INITIATED HEALTHCHECK !!! Apr 26 19:09:24 localhost amf_demo: Started AMF-Initiated HealthCheck (with Component Failover Recommended Recovery) Comp:

Page 38 of 44

OpenSAF Availability Management Framework

safComp=AmfDemo,safSu=SU2,safSg=AmfDemo,safApp=AmfDemo1 HealthCheckKey: AmfDemo Apr 26 19:09:24 localhost amf_demo: Dispatched 'HealthCheck' Callback Component: safComp=AmfDemo,safSu=SU2,safSg=AmfDemo,safApp=AmfDemo1 HealthCheckKey: AmfDemo Apr 26 19:09:44 localhost last message repeated 2 times Apr 26 19:10:45 localhost last message repeated 6 times Apr 26 19:10:55 localhost amf_demo: Dispatched 'HealthCheck' Callback Component: safComp=AmfDemo,safSu=SU2,safSg=AmfDemo,safApp=AmfDemo1 HealthCheckKey: AmfDemo Apr 26 19:10:55 localhost amf_demo: Stopped HealthCheck for Comp: safComp=AmfDemo,safSu=SU2,safSg=AmfDemo,safApp=AmfDemo1 with HealthCheckKey: AmfDemo Apr 26 19:10:55 localhost amf_demo: FAILOVER THROUGH ERROR REPORT !!! DEMONSTRATING COMPONENT

Apr 26 19:10:57 localhost osafamfnd[29730]: Component 'safComp=AmfDemo,safSu=SU2,safSg=AmfDemo,safApp=AmfDemo1' faulted due to 'errorReport(1)' - rcvr=11 Apr 26 19:10:57 localhost amf_demo: Sent Error Report for Comp: safComp=AmfDemo,safSu=SU2,safSg=AmfDemo,safApp=AmfDemo1 with CompFailover as the recommended recovery

Apr 26 19:10:57 localhost amf_demo: ############################################## Apr 26 19:10:57 localhost amf_demo: # Apr 26 19:10:57 localhost amf_demo: AvSvAmf Demo !!! # Apr 26 19:10:57 localhost amf_demo: # # # # You are about to witness

Apr 26 19:10:57 localhost amf_demo: ############################################## Apr 26 19:10:57 localhost amf_demo: AMF thread entered

Apr 26 19:10:57 localhost amf_demo: AMF Initialization Done !!!

Page 39 of 44

OpenSAF Availability Management Framework

Apr 26 19:10:57 localhost amf_demo:

AmfHandle: ff900001

Apr 26 19:10:57 localhost amf_demo: AMF Selection Object Get Successful !!! Apr 26 19:10:57 localhost amf_demo: Component Name Get Successful !!! Apr 26 19:10:57 localhost amf_demo: CompName: safComp=AmfDemo,safSu=SU2,safSg=AmfDemo,safApp=AmfDemo1 Apr 26 19:10:57 localhost amf_demo: Component Registered !!! Apr 26 19:10:57 localhost amf_demo: Dispatched 'CSI Set' Callback for Component: 'safComp=AmfDemo,safSu=SU2,safSg=AmfDemo,safApp=AmfDemo1' Apr 26 19:10:57 localhost amf_demo: CSIName: safCsi=AmfDemo,safSi=AmfDemo,safApp=AmfDemo1 HAState: Standby CSIFlags: Add One Apr 26 19:10:57 localhost amf_demo: Started Protection Group Tracking CSI: safCsi=AmfDemo,safSi=AmfDemo,safApp=AmfDemo1 Track Flags: Changes Only Apr 26 19:11:12 localhost amf_demo: Dispatched 'Protection Group' Callback CSI: safCsi=AmfDemo,safSi=AmfDemo,safApp=AmfDemo1 No. of Members: 2 Apr 26 19:11:12 localhost amf_demo: CompName[0]: safComp=AmfDemo,safSu=SU1,safSg=AmfDemo,safApp=AmfDemo1 Apr 26 19:11:12 localhost amf_demo: Apr 26 19:11:12 localhost amf_demo: Apr 26 19:11:12 localhost amf_demo: Rank[0] : 1

HAState[0] : Quiesced Change[0] : State Change

Apr 26 19:11:12 localhost amf_demo: Stopped Protection Group Tracking for CSI: safCsi=AmfDemo,safSi=AmfDemo,safApp=AmfDemo1

For the standby node: Apr 26 23:30:33 linux-amf amf_demo: ############################################## Apr 26 23:30:33 linux-amf amf_demo: # Apr 26 23:30:33 linux-amf amf_demo: AvSvAmf Demo !!! # # # You are about to witness

Page 40 of 44

OpenSAF Availability Management Framework

Apr 26 23:30:33 linux-amf amf_demo: #

Apr 26 23:30:33 linux-amf amf_demo: ############################################## Apr 26 23:30:33 linux-amf amf_demo: AMF thread entered

Apr 26 23:30:33 linux-amf amf_demo: AMF Initialization Done !!! Apr 26 23:30:33 linux-amf amf_demo: AmfHandle: ff900001

Apr 26 23:30:33 linux-amf amf_demo: AMF Selection Object Get Successful !!! Apr 26 23:30:33 linux-amf amf_demo: Component Name Get Successful !!! Apr 26 23:30:33 linux-amf amf_demo: CompName: safComp=AmfDemo,safSu=SU2,safSg=AmfDemo,safApp=AmfDemo1 Apr 26 23:30:33 linux-amf amf_demo: Component Registered !!! Apr 26 23:30:42 linux-amf amf_demo: Dispatched 'CSI Set' Callback for Component: 'safComp=AmfDemo,safSu=SU2,safSg=AmfDemo,safApp=AmfDemo1' Apr 26 23:30:42 linux-amf amf_demo: CSIName: safCsi=AmfDemo,safSi=AmfDemo,safApp=AmfDemo1 HAState: Standby CSIFlags: Add One Apr 26 23:30:42 linux-amf amf_demo: Started Protection Group Tracking CSI: safCsi=AmfDemo,safSi=AmfDemo,safApp=AmfDemo1 Track Flags: Changes Only Apr 26 23:32:18 linux-amf amf_demo: Dispatched 'Protection Group' Callback CSI: safCsi=AmfDemo,safSi=AmfDemo,safApp=AmfDemo1 No. of Members: 2 Apr 26 23:32:18 linux-amf amf_demo: CompName[0]: safComp=AmfDemo,safSu=SU1,safSg=AmfDemo,safApp=AmfDemo1 Apr 26 23:32:18 linux-amf amf_demo: Apr 26 23:32:18 linux-amf amf_demo: Apr 26 23:32:18 linux-amf amf_demo: Rank[0] : 1

HAState[0] : Quiesced Change[0] : State Change

Apr 26 23:32:18 linux-amf amf_demo: Stopped Protection Group Tracking for CSI: safCsi=AmfDemo,safSi=AmfDemo,safApp=AmfDemo1 Apr 26 23:32:18 linux-amf amf_demo: Started Passive Monitoring for Comp: safComp=AmfDemo,safSu=SU2,safSg=AmfDemo,safApp=AmfDemo1

Page 41 of 44

OpenSAF Availability Management Framework

Apr 26 23:32:18 linux-amf amf_demo: Stopped Passive Monitoring for Comp: safComp=AmfDemo,safSu=SU2,safSg=AmfDemo,safApp=AmfDemo1 Apr 26 23:32:18 linux-amf amf_demo: Dispatched 'CSI Set' Callback for Component: 'safComp=AmfDemo,safSu=SU2,safSg=AmfDemo,safApp=AmfDemo1' Apr 26 23:32:18 linux-amf amf_demo: CSIFlags: Target All Apr 26 23:32:18 linux-amf amf_demo: FINALIZE THE COMPONENT) !!! Apr 26 23:32:33 linux-amf amf_demo: Apr 26 23:32:35 linux-amf amf_demo: CSIName: HAState: Active

DEMO OVER (UNREGISTER & Component UnRegistered !!! AMF Finalize Done !!!

Page 42 of 44

OpenSAF Availability Management Framework

5 Related Documentation
5.1 OpenSAF Documents
A list of all the OpenSAF technical documentation can be found in the Related Documents section of the OpenSAF Overview Release 3 Programmers' Reference.

5.2 Related Specifications


For additional information, refer to the following table for related specifications. As an additional help, a source for the listed document is provided. Please note that, while these sources have been verified, the information is subject to change without notice.
Table 6 Related Specifications Document Title Service Availability Forum Application Interface Specification, Overview and Models Service Availability Forum Application Interface Specification, Availability Management Framework Service Availability Forum Application Interface Specification, Cluster Membership Service Service Availability Forum Application Interface Specification, Checkpoint Service Service Availability Forum Application Interface Specification, Event Service Service Availability Forum Application Interface Specification, Message Service Service Availability Forum Application Interface Specification, Lock Service Service Availability Forum Application Interface Specification, Information Model Management Service Service Availability Forum Application Interface Specification, Log Service Service Availability Forum Application Interface Specification, Notification Service Version/Source SAF-AIS-B.01.01/ http://www.saforum.org SAF-AIS-AMF-B.01.01/ http://www.saforum.org SAF-AIS-CLM-B.01.01/ http://www.saforum.org SAF-AIS-CKPT-B.02.02/ http://www.saforum.org SAF-AIS-EVT-B.03.01/ http://www.saforum.org SAF-AIS-MSG-B.03.01/ http://www.saforum.org SAF-AIS-LCK-B.01.01/ http://www.saforum.org

SAI-AIS-IMM-A.02.01 http://www.saforum.org SAI-AIS-LOG-A.02.01 http://www.saforum.org


SAI-AIS-NTF-A.01.01

http://www.saforum.org

Page 43 of 44

OpenSAF Availability Management Framework

Page 44 of 44

OpenSAF Availability Management Framework