Dell PowerVault ML6000 Dell PowerVault ML6000 SMI-S Reference Guide - Page 11

CIM Profiles and Subprofiles, Server Profile, Version 1.2, Storage Library Profile

Get Dell PowerVault ML6000 PDF manuals and user guides View all Dell PowerVault ML6000 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 11 highlights

CIM Profiles and Subprofiles SMI-S defines a number of profiles that specify the managed objects that control and monitor elements of a Storage Area Network (SAN). The CIM server embedded within your library supports the following standard profiles: • Server Profile, Version 1.2 • Storage Library Profile, Version 1.2 When using CIM servers to manage a network of SAN elements, you must first discover the location of all available CIM servers and discover which services they support. The Service Location Protocol (SLP) version 2 provides this discovery mechanism. CIM clients use SLPv2 to discover CIM servers by gathering generic information about which services the CIM servers provide and the specific URL where these services are located. After the CIM client discovers the CIM servers within the SAN, the CIM client must determine the level of support that each CIM server provides. For details about discovering the CIM server embedded in your library, refer to Discovering the CIM Server on page 12. The next step to using CIM servers to manage a network of SAN elements is to implement CIM indications. For details about CIM indications, refer to Using CIM Indications on page 13. Server Profile, Version 1.2 Your library contains a CIM server, and the CIM server includes a standard profile called the Server profile. The Server profile defines the capabilities of a CIM server. This includes providing the namespace for the CIM server and all profiles and subprofiles that the CIM server supports. For each supported profile, the Server profile instantiates the RegisteredProfile class. Each instance of this class gives the CIM client the profile name and unique ID that is supported by the CIM server. Similarly, the CIM server lists all supported optional subprofiles, using the RegisteredSubProfile class and the SubprofileRequiresProfile association class to associate the subprofile with the profile. Storage Library Profile, Version 1.2 The schema for a storage library provides the classes and associations necessary to represent various forms of removable media libraries. This profile is based upon the CIM 2.9 object model and defines the subset of classes that supply the information necessary for robotic storage libraries. This profile further describes how the classes are to be used to satisfy various use cases, and offers suggestions to agent implementors and client application developers. Detailed descriptions of classes can be found in the CIM 2.9 preliminary schema. For a comprehensive view of all the supported profiles and subprofiles, see Figure 1 on page 8. Dell PowerVault ML6000 SMI-S Reference Guide 7

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
Dell PowerVault ML6000 SMI-S Reference Guide
7
CIM Profiles and Subprofiles
SMI-S defines a number of profiles that specify the managed objects that control and monitor elements of
a Storage Area Network (SAN). The CIM server embedded within your library supports the following
standard profiles:
•
Server Profile, Version 1.2
•
Storage Library Profile, Version 1.2
When using CIM servers to manage a network of SAN elements, you must first discover the location of all
available CIM servers and discover which services they support. The Service Location Protocol (SLP)
version 2 provides this discovery mechanism. CIM clients use SLPv2 to discover CIM servers by gathering
generic information about which services the CIM servers provide and the specific URL where these
services are located. After the CIM client discovers the CIM servers within the SAN, the CIM client must
determine the level of support that each CIM server provides. For details about discovering the CIM server
embedded in your library, refer to
Discovering the CIM Server
on page 12.
The next step to using CIM servers to manage a network of SAN elements is to implement CIM indications.
For details about CIM indications, refer to
Using CIM Indications
on page 13.
Server Profile, Version 1.2
Your library contains a CIM server, and the CIM server includes a standard profile called the Server profile.
The Server profile defines the capabilities of a CIM server. This includes providing the namespace for the
CIM server and all profiles and subprofiles that the CIM server supports. For each supported profile, the
Server profile instantiates the
RegisteredProfile
class. Each instance of this class gives the CIM client
the profile name and unique ID that is supported by the CIM server. Similarly, the CIM server lists all
supported optional subprofiles, using the
RegisteredSubProfile
class and the
SubprofileRequiresProfile
association class to associate the subprofile with the profile.
Storage Library Profile, Version 1.2
The schema for a storage library provides the classes and associations necessary to represent various
forms of removable media libraries. This profile is based upon the CIM 2.9 object model and defines the
subset of classes that supply the information necessary for robotic storage libraries.
This profile further describes how the classes are to be used to satisfy various use cases, and offers
suggestions to agent implementors and client application developers. Detailed descriptions of classes can
be found in the CIM 2.9 preliminary schema.
For a comprehensive view of all the supported profiles and subprofiles, see
Figure 1
on page 8.