Quantum Scalar Intelligent Libraries SMI-S Reference Guide 7CIM Profiles and SubprofilesSMI-S defines a number of profiles that specify the managed objects that control and monitor elements ofa Storage Area Network (SAN). The CIM server embedded within your library supports the followingstandard profiles:• Server Profile, Version 1.2• Storage Library Profile, Version 1.2When using CIM servers to manage a network of SAN elements, you must first discover the location of allavailable 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 gatheringgeneric information about which services the CIM servers provide and the specific URL where theseservices are located. After the CIM client discovers the CIM servers within the SAN, the CIM client mustdetermine the level of support that each CIM server provides. For details about discovering the CIM serverembedded 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.2Your 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 theCIM server and all profiles and subprofiles that the CIM server supports. For each supported profile, theServer profile instantiates the RegisteredProfile class. Each instance of this class gives the CIM clientthe profile name and unique ID that is supported by the CIM server. Similarly, the CIM server lists allsupported optional subprofiles, using the RegisteredSubProfile class and theSubprofileRequiresProfile association class to associate the subprofile with the profile.Storage Library Profile, Version 1.2The schema for a storage library provides the classes and associations necessary to represent variousforms of removable media libraries. This profile is based upon the CIM 2.9 object model and defines thesubset 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 offerssuggestions to agent implementors and client application developers. Detailed descriptions of classes canbe 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.