Introduction | Service Extensions |
|
|
The following information can be found in the referenced document:
zService concept definitions and descriptions
zFunctional behaviors and relationships
zA complete set of service data types exposed to the service user
zThe set of Service APIs available to the service user
An application managed by AvSv is provided with APIs to perform the following:
zComponent registration and unregistration
zPassive monitoring of processes of a component
zComponent health monitoring
zComponent service instance management
zComponent life cycle management
zProtection group management
zError reporting
An application also provides certain "Component Life Cycle" commands that are used by AvSv to instantiate, terminate, and clean it up. Applications can also use the APIs specified in Section
3 of the
1.2.5Service Extensions
AvSv’s AvM service is proprietary to Motorola. All functionality and associated behaviors identified in this documentation are supported, as explained in this document.
1.2.6Implementation 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.
1.2.7Configuration
An application managed by AvSv to provide high service availability must be modeled in terms of logical entities in accordance with the structure of the "System Model". Further, the application must implement the state models and callback interfaces according to the AMF specification.
Availability Service provides a management interface to configure the System Model and to perform runtime administrative operations. The System Model configuration can be done either using SNMP or XML, while the runtime administrative operations can be performed using SNMP or CLI.
22 | Availability Service Programmer’s Reference (6806800C44B) |
