Motorola 6806800C44B 用户手册
1
Availability Service Programmer’s Reference (6806800C44B)
13
Introduction
1.1
Overview
The NCS Availability Service (AvSv) is the core service of the NetPlane 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.
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 AvSv functionality is a highly compliant implementation of Service Availability Forum’s
Application Interface Specification of Availability Management Framework (SAI-AIS-AMF-
B.01.01) and Cluster Membership Service (SAI-AIS-CLM-B.01.01).
Application Interface Specification of Availability Management Framework (SAI-AIS-AMF-
B.01.01) and Cluster Membership Service (SAI-AIS-CLM-B.01.01).
The Availability Service (AvSv) provides the following functionality:
z
Leverage the SAF "System Description and Conceptual Model"
z
Honour the Availability Management Framework" API
z
Honour the SA Cluster membership Service API
z
House the MIB tables corresponding to the hardware portion of the deployment system
description which includes entity containment and fault domain hierarchy information
description which includes entity containment and fault domain hierarchy information
z
House the MIB tables corresponding to the software portion of the deployment system
description which include configuration of AMF-defined logical entities and their
relationship
description which include configuration of AMF-defined logical entities and their
relationship
z
Perform blade validation on receipt of HPI hot swap insertion events
z
Handle fault events such as HPI hot swap extraction events, threshold crossing events etc.
The AvSv maintains a software system model database which captures SAF-described 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.
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. A Service Unit is also
scoped to one or more (physical) fault domains. Service Units of the same type are grouped
into Service Groups (SG) which exhibit particular redundancy modelling characteristics.
Service Units within a SG are assigned to Service Instances (SI) and given a High Availability
state of active and standby.
view of physical resources such as processes, drivers or devices. Components are grouped into
Service Units according to fault dependencies that exist among them. A Service Unit is also
scoped to one or more (physical) fault domains. Service Units of the same type are grouped
into Service Groups (SG) which exhibit particular redundancy modelling characteristics.
Service Units within a SG are assigned to Service Instances (SI) and given a High Availability
state of active and standby.
The hardware database maintained by AvSv includes hardware entity containment information
and the hardware fault domain hierarchy. All hardware entities are represented by their HPI
entity paths. The hardware entity containment tree only includes managed FRUs which may or
may not include processor environments., and non-FRU resources which include processor
environments. The fault domain data includes dependency relationships between parent-child
and the hardware fault domain hierarchy. All hardware entities are represented by their HPI
entity paths. The hardware entity containment tree only includes managed FRUs which may or
may not include processor environments., and non-FRU resources which include processor
environments. The fault domain data includes dependency relationships between parent-child