Questions and Answers

• Fault Management
• Configuration Management
• Accounting Management
• Performance Management
• Security Management

Four and a fifth is scheduled for December 2005. The Bluefin specification was published in May 2002, SMI-S 1.0.0 in July 2003, SMI-S 1.0.1 September 2003, SMI-S 1.0.2 in February 2004 and SMI-S 1.1.0 is scheduled to be published in December 2005

The Service Location Protocol (SLP)

The Storage Management Initiative Specification

A Dedicated SMI-S Server manages just one SAN resource while a General-Purpose SMI-S Server can manage more than one SAN resource.

A Subprofile represents an optional enhancement to a Profile. For example, for the Array Profile, a vendor can choose, but is not required, to implement the Masking and Mapping Subprofile to allow a Client to control access to the storage resources.

A vendor must implement all mandatory Classes defined in the Profile. However, not all Classes in a Profile are mandatory. If a Class is designated as optional, then a vendor can choose not to implement support for that Class.

Some Subprofiles are called Common Subprofiles because they can be referenced by many different types of Profiles. For example, the Location Subprofile applies to any Profile that contains a physical component whose physical location may be important to a Client.

The storage space for Logical Disks is allocated from Storage Pools?

To express CIM Data as XML elements as defined by the CIM Data Type Definition (DTD) file.

A Recipe describes the specific WBEM operations that must be performed, the order in which they must be performed and the argument values to be used for each WBEM operation.

The Conformance Test Program (CTP) is a test harness that is configured to exercise a vendor's product for conformance to a particular Profile and Subprofiles.

• Data

• MetaData

• Association Traversal

• Query Execution

• Extrinsic Method Invocation

• Qualifier Declarations

Like a Profile, a Package defines a set of CIM classes, the associations that will be used to traverse between classes and the properties and extrinsic methods to be used by the classes.

The CIM elements of a Package are incorporated into the referencing Profile and must be implemented as part of the Profile. In contrast, the CIM elements in a Subprofile are not required to be implemented.

FALSE. It is a Switch Subprofile for Director Class Switch devices.

• Health

• Physical Package

• Software

• Block Services

• Fabric

• Switch

Yes. A Profile only defines the minimal implementation requirements. A test suite need only test for the required elements. Therefore, an implementation is considered conformant even though it contains elements not in the Profile.

The Service Location Protocol (SLP)

FALSE. CIM-XML is the protocol that uses HTTP as the transport and  xmlCIM as the payload

An Profile marked as Experimental means that its definition is subject to change.

The Location Subprofile allows a Client to retrieve information about the physical location of the device or element managed by the referencing Profile.

TRUE

If a Profile defines a long running operation, then it may reference the Job Control Subprofile because the purpose of the Subprofile is to spawn a job to monitor the progress and completion of a long running operation. Without it, the Client must wait for the operation to complete before resuming operation. Doing so may not be desired.

Defining Profiles in SMI-S 1.1.0, by itself, does not ensure interoperability. Implementation errors, design flaws and misinterpretation of the specification can prevent this goal. CTP exercises an implementation to verify that it behaves correctly.

CIM Operations over HTTP Specification v2.3. This specification is published by the Distributed Management Task Force (DMTF).

FALSE. The NAS System managed by this Profile does NOT include local storage.

2002

A Client uses the Service Location Protocol (SLP).

TRUE. The DMTF CIM DTD defines the XML elements for the CIM meta schema.

In SMI-S 1.1.0, a Durable Name allows a Client to determine when two different CIM Object Names refer to the same real world SAN resource.

A SMI Agent can be a Dedicated Server that manages just one SAN resource. Alternatively, a General Purpose Server that manages more than one SAN resource.

The Server Profile allows a Client to manage and retrieve information about a SMI Agent and its components.

FALSE. This is the definition of the References operation.

CIM Schema version 2.11

Six. Array, Volume Management, NAS Head, Self-Contained NAS System, Storage Library and Storage Virtualizer

A Proxy Dedicated SMI-S Server is one that is hosted on a system separate from its managed storage resource and communicates with the remote resource using a network protocol.

The FC Target Ports Subprofile allows a Client to discover the ports on a storage system using Fibre Channel (FC) that are acting as front-end ports.

FALSE

• SCSI Logical Units that are exported from storage systems

• External Ports on hosts and storage devices

• Fibre Channel ports on interconnect elements

• Fibre Channel fabric

• Storage systems

• Operating system device

TRUE. This lab is supplied with equipment from all leading storage product vendors.

 The Enhanced Zoning and Enhanced Zoning Control Subprofile allows a Client to manage Zone Aliases in a Fabric

TRUE.

For each Profile and Subprofile, an XML file explicitly defines the CIM elements used along with the permissible values allowed. Using an XML file, the CTP exercises the product for conformance to the SMI-S Profile and Subprofile definition.

• Level 5 Application Level Functionality - allows a Client to manage applications (e.g., database, mail server, etc) in a SAN that use data at the File/Record level.

• Level 4 File/Record Level Functionality - allows a Client to manage SAN resources that expose data as files or records such as filesystems.

• Level 3 Block Level Functionality - allows a Client to manage the SAN resources that are used by the File/Record resources such as Storage Volumes (e.g., LUNs) and Logical Disks.

• Level 2 Connectivity Level Functionality - allows a Client to manage the connectivity between physical devices in a SAN such as Fabrics, Zones and iSCSI Sessions.

• Level 1 Device Level Functionality - allows a Client to manage the physical devices in a SAN such as Host Based Adapters (HBA) and disk drives.

TRUE

The Device Credentials Subprofile allows a Client to change the shared secret (i.e., password) that is used to control access to the devices of the referencing Profile.

A Deprecated Profile should not be used in new development.

FALSE