Hp SAN Virtualization Services Platform User Manual download pdf (Page 271)

13 Indication Profile

Profile introduction

Indications are support for unsolicited event notifications. Each profile that supports event notification

through CIM indications would support this profile, its classes, and its associations.

The following profiles are related to this one:

• Storage Management Technical Specification: Part 2 Common Profiles. V1.4.0. Rev 1. Clause

43 Profile Registration Profile

• Storage Management Technical Specification: Part 2 Common Profiles. V1.4.0. Rev 1. Clause

45 Experimental Indication Profile

Functional description

Indications are asynchronous notifications. They are used by a client to get a telemetry feed of changes

on the stripe set. They are also used by a client to warn it of problems that may be occurring. Often,

the indications are simply observations. Some effort by the client may be required to use the

observations to determine the nature of the event that gives rise to the observations.

The foundation for supporting the Indication Profile is typically provided by the SMI agent (for example,

CQL query language parsing, an Indication provider interface, and Indication subscription/delivery

support). This section will outline how an SMI agent handles Indication Subscription, what a provider

that supports Indications must implement, and how the supported Indications must be advertised.

A CIM client subscribes for Indication delivery on a per-Indication basis.

First, a client locates or creates an instance of CIM_IndicationFilter. The query, query language, and

SourceNamespace properties identify the desired Indication type and origin of indications. Note that

since this implementation is designed as a proxy implementation that will migrate to an embedded

implementation, creation of CIM_IndicationFilter instances will not be supported. In order to maintain

the smallest footprint and deliver Indications as efficiently as possible, a predefined instance of

CIM_IndicationFilter will be provided for each Indication supported (each implemented profile outlines

the required indication filters). This prevents CIM clients from creating unnecessary CIM_IndicationFilter

instances that would have to be interrogated by the SMI agent each time Indications are delivered.

The next step in the CIM client Indication Subscription process is to create an instance of

CIM_ListenerDestinationCIMXML. This instance provides the information necessary for the SMI agent

to deliver indications to the CIM client when it occurs.

Finally, the CIM client activates Indication Subscription by creating an instance of the

CIM_IndicationSubscription association specifying an CIM_IndicationFilter and

CIM_ListenerDestinationCIMXML as the reference property values.

When a CIM client activates an Indication Subscription as described above, the SMI agent will parse

the CIM_IndicationFilter reference in the CIM_IndicationSubscription. Based on the

CIM_IndicationFilter.QueryLanguage property value, the appropriate query language parser will be

loaded (for example, CQL). The CIM_IndicationFilter.Query property value is then parsed to identify

the CIM class(es) to which the Indication pertains. Based on the FROM clause or ISA clause's value,

SAN Virtualization Services Platform SMI-S User Guide 271

1 2 ... 266 267 268 269 270 271 272 273 274 275 276 ... 323 324

No comments

Hp SAN Virtualization Services Platform User Manual Page 271