1 a.dunfey 1.1 // ===================================================================
2 // Title: Core_Device
3 // $State: Exp $
4 // $Date: 2004/11/29 18:31:41 $
5 // $RCSfile: Core_Device.mof,v $
6 // $Revision: 1.6.2.3 $
7 // ===================================================================
8 //#pragma inLine ("Includes/copyright.inc")
9 // Copyright 1998-2005 Distributed Management Task Force, Inc. (DMTF).
10 // All rights reserved.
11 // DMTF is a not-for-profit association of industry members dedicated
12 // to promoting enterprise and systems management and interoperability.
13 // DMTF specifications and documents may be reproduced for uses
14 // consistent with this purpose by members and non-members,
15 // provided that correct attribution is given.
16 // As DMTF specifications may be revised from time to time,
17 // the particular version and release date should always be noted.
18 //
19 // Implementation of certain elements of this standard or proposed
20 // standard may be subject to third party patent rights, including
21 // provisional patent rights (herein "patent rights"). DMTF makes
22 a.dunfey 1.1 // no representations to users of the standard as to the existence
23 // of such rights, and is not responsible to recognize, disclose, or
24 // identify any or all such third party patent right, owners or
25 // claimants, nor for any incomplete or inaccurate identification or
26 // disclosure of such rights, owners or claimants. DMTF shall have no
27 // liability to any party, in any manner or circumstance, under any
28 // legal theory whatsoever, for failure to recognize, disclose, or
29 // identify any such third party patent rights, or for such party's
30 // reliance on the standard or incorporation thereof in its product,
31 // protocols or testing procedures. DMTF shall have no liability to
32 // any party implementing such standard, whether such implementation
33 // is foreseeable or not, nor to any patent owner or claimant, and shall
34 // have no liability or responsibility for costs or losses incurred if
35 // a standard is withdrawn or modified after publication, and shall be
36 // indemnified and held harmless by any party implementing the
37 // standard from any and all claims of infringement by a patent owner
38 // for such implementations.
39 //
40 // For information about patents held by third-parties which have
41 // notified the DMTF that, in their opinion, such patent may relate to
42 // or impact implementations of DMTF standards, visit
43 a.dunfey 1.1 // http://www.dmtf.org/about/policies/disclosures.php.
44 //#pragma inLine
45 // ===================================================================
46 // Description: The Core Model defines basic management concepts.
47 // This file defines the concepts for LogicalDevices (the
48 // logical abstractions and management of installed
49 // hardware).
50 //
51 // The object classes below are listed in an order that
52 // avoids forward references. Required objects, defined
53 // by other working groups, are omitted.
54 // ==================================================================
55 // Change Log for v2.8 Final
56 // CR1200 - ElementSoftwareIdentity
57 // CR1210 - Removal of experimental qualifiers for core.
58 // CR1223 - SysDev Omnibus CR - Minor MOF corrections.
59 //
60 // Change Log for v2.8 Preliminary
61 // CR932 - Add power mode status to OperationalStatus.
62 // Move the specific power mode states from availability
63 // to a property between the PowerMgmt service and its ME.
64 a.dunfey 1.1 // Remove the overlapping properties from Logical Device.
65 // CR943 - Move error code data from LogicalDevice to
66 // DeviceErrorCountData
67 // CR1002 - Move LogicalDevice.PowerOnHours and
68 // LogicalDevice.TotalPowerOnHours to PowerManagementStatistics
69 // CR1019 - CIM Versioning for 2.8 Preliminary
70 // CR1045 - Add method for requesting a "EnabledState" change in
71 // EnabledLogicalElement class / Deprecate or explain overlap
72 // with LogicalDevice and Service properties and methods
73 // CR1092 - Move DeviceSoftwareIdentity to Core28_Device.mof from
74 // Device28_DeviceElements.
75 //
76 // Change Log for v2.7 Final
77 // CR961 - Change references to EnabledStatus and RequestedStatus to
78 // EnabledState and RequestedState in the LogicalDevice.
79 // StatusInfo,
80 // EnableDevice(),
81 // OnlineDevice(),
82 // QuiesceDevice()
83 //
84 // Change Log for v2.7
85 a.dunfey 1.1 // CR624 - Fixed several of the DMI mapping strings that were missing
86 // the attribute number in LogicalDevice
87 // CR720 - Deprecate the use of LogicalDevice.PowerManagementSupported,
88 // LogicalDevice.PowerManagementCapabilities, & LogicalDevice.
89 // SetPowerState()
90 // CR761 - Add the Composition Qualifer to SystemDevice
91 // CR763 - Change subclassing of LogicalDevice from LogicalElement to
92 // EnabledLogicalElement
93 // - Deprecate LogicalDevice.StatusInfo
94 // - Update description of LogicalDevice.EnableDevice() to
95 // explain position relative to LogicalDevice.RequestedStatus
96 // - Update description of LogicalDevice.OnlineDevice() and
97 // QuiesceDevice to make reference to EnabledStatus
98 // ==================================================================
99
100 #pragma locale ("en_US")
101
102
103 // ===================================================================
104 // LogicalDevice
105 // ===================================================================
106 a.dunfey 1.1 [Abstract, Version ( "2.8.0" ), Description (
107 "An abstraction or emulation of a hardware entity, that may or "
108 "may not be Realized in physical hardware. Any characteristics "
109 "of a LogicalDevice that are used to manage its operation or "
110 "configuration are contained in, or associated with, the "
111 "LogicalDevice object. Examples of the operational properties "
112 "of a Printer would be paper sizes supported, or detected "
113 "errors. Examples of the configuration properties of a Sensor "
114 "Device would be threshold settings. Various configurations "
115 "could exist for a LogicalDevice. These configurations could be "
116 "contained in Setting objects and associated with the "
117 "LogicalDevice.")]
118 class CIM_LogicalDevice : CIM_EnabledLogicalElement {
119
120 [Key, Propagated ( "CIM_System.CreationClassName" ),
121 Description (
122 "The scoping System's CreationClassName."),
123 MaxLen ( 256 )]
124 string SystemCreationClassName;
125
126 [Key, Propagated ( "CIM_System.Name" ), Description (
127 a.dunfey 1.1 "The scoping System's Name."),
128 MaxLen ( 256 )]
129 string SystemName;
130
131 [Key, Description (
132 "CreationClassName indicates the name of the class or the "
133 "subclass used in the creation of an instance. When used "
134 "with the other key properties of this class, this property "
135 "allows all instances of this class and its subclasses to be "
136 "uniquely identified."),
137 MaxLen ( 256 )]
138 string CreationClassName;
139
140 [Key, Description (
141 "An address or other identifying information to uniquely "
142 "name the LogicalDevice."),
143 MaxLen ( 64 )]
144 string DeviceID;
145
146 [Deprecated { "CIM_PowerManagementCapabilities" }, Description (
147 "Boolean indicating that the Device can be power managed. "
148 a.dunfey 1.1 "The use of this property has been deprecated. Instead, the "
149 "existence of an associated PowerManagementCapabilities "
150 "class (associated using the ElementCapabilities "
151 "relationhip) indicates that power management is supported.")]
152 boolean PowerManagementSupported;
153
154 [Deprecated { "CIM_PowerManagementCapabilities.PowerCapabilities"
155 }, Description (
156 "An enumerated array describing the power management "
157 "capabilities of the Device. The use of this property has "
158 "been deprecated. Instead, the PowerCapabilites property in "
159 "an associated PowerManagementCapabilities class should be "
160 "used."),
161 ValueMap { "0", "1", "2", "3", "4", "5", "6", "7" },
162 Values { "Unknown", "Not Supported", "Disabled", "Enabled",
163 "Power Saving Modes Entered Automatically",
164 "Power State Settable", "Power Cycling Supported",
165 "Timed Power On Supported" }]
166 uint16 PowerManagementCapabilities[];
167
168 [Description (
169 a.dunfey 1.1 "The primary availability and status of the Device. "
170 "(Additional status information can be specified using the "
171 "Additional Availability array property.) For example, the "
172 "Availability property indicates that the Device is running "
173 "and has full power (value=3), or is in a warning (4), test "
174 "(5), degraded (10) or power save state (values 13-15 and "
175 "17). Regarding the Power Save states, these are defined as "
176 "follows: Value 13 (\"Power Save - Unknown\") indicates that "
177 "the Device is known to be in a power save mode, but its "
178 "exact status in this mode is unknown; 14 (\"Power Save - "
179 "Low Power Mode\") indicates that the Device is in a power "
180 "save state but still functioning, and may exhibit degraded "
181 "performance; 15 (\"Power Save - Standby\") describes that "
182 "the Device is not functioning but could be brought to full "
183 "power 'quickly'; and value 17 (\"Power Save - Warning\") "
184 "indicates that the Device is in a warning state, though "
185 "also in a power save mode."),
186 ValueMap { "1", "2", "3", "4", "5", "6", "7", "8", "9", "10",
187 "11", "12", "13", "14", "15", "16", "17", "18", "19", "20",
188 "21" },
189 Values { "Other", "Unknown", "Running/Full Power", "Warning",
190 a.dunfey 1.1 "In Test", "Not Applicable", "Power Off", "Off Line",
191 "Off Duty", "Degraded", "Not Installed", "Install Error",
192 "Power Save - Unknown", "Power Save - Low Power Mode",
193 "Power Save - Standby", "Power Cycle",
194 "Power Save - Warning", "Paused", "Not Ready",
195 "Not Configured", "Quiesced" },
196 MappingStrings { "MIF.DMTF|Operational State|006.5",
197 "MIB.IETF|HOST-RESOURCES-MIB.hrDeviceStatus",
198 "MIF.DMTF|Host Device|001.5" },
199 ModelCorrespondence { "CIM_LogicalDevice.AdditionalAvailability"
200 }]
201 uint16 Availability;
202
203 [Deprecated { "CIM_EnabledLogicalElement.EnabledState" },
204 Description (
205 "The StatusInfo property indicates whether the Logical "
206 "Device is in an enabled (value = 3), disabled (value = 4) "
207 "or some other (1) or unknown (2) state. If this property "
208 "does not apply to the LogicalDevice, the value, 5 (\"Not "
209 "Applicable\"), should be used. StatusInfo has been "
210 "deprecated in lieu of a more clearly named property with "
211 a.dunfey 1.1 "additional enumerated values (EnabledState), that is "
212 "inherited from ManagedSystemElement. \n"
213 "If a Device is (\"Enabled\")(value=3), it has been powered "
214 "up, and is configured and operational. The Device may or "
215 "may not be functionally active, depending on whether its "
216 "Availability (or AdditionalAvailability) indicate that it "
217 "is (\"Running/Full Power\")(value=3) or (\"Off line\") "
218 "(value=8). In an enabled but offline mode, a Device may be "
219 "performing out-of-band requests, such as running "
220 "Diagnostics. If (\"Disabled\") StatusInfo value=4), a "
221 "Device can only be \"enabled\" or powered off. In a "
222 "personal computer environment, (\"Disabled\") means that "
223 "the Device's driver is not available in the stack. In other "
224 "environments, a Device can be disabled by removing its "
225 "configuration file. A disabled device is physically present "
226 "in a System and consuming resources, but can not be "
227 "communicated with until a load of a driver, a load of a "
228 "configuration file or some other \"enabling\" activity has "
229 "occurred."),
230 ValueMap { "1", "2", "3", "4", "5" },
231 Values { "Other", "Unknown", "Enabled", "Disabled",
232 a.dunfey 1.1 "Not Applicable" },
233 MappingStrings { "MIF.DMTF|Operational State|006.4" }]
234 uint16 StatusInfo;
235
236 [Deprecated { "CIM_DeviceErrorData.LastErrorCode" },
237 Description (
238 "LastErrorCode captures the last error code reported by the "
239 "LogicalDevice.")]
240 uint32 LastErrorCode;
241
242 [Deprecated { "CIM_DeviceErrorData.ErrorDescription" },
243 Description (
244 "ErrorDescription is a free-form string supplying more "
245 "information about the error recorded in LastErrorCode, and "
246 "information on any corrective actions that may be taken.")]
247 string ErrorDescription;
248
249 [Deprecated { "CIM_ManagedSystemElement.OperationalStatus" },
250 Description (
251 "ErrorCleared is a boolean property indicating that the "
252 "error reported in LastErrorCode is now cleared.")]
253 a.dunfey 1.1 boolean ErrorCleared;
254
255 [Description (
256 "OtherIdentifyingInfo captures additional data, beyond "
257 "DeviceID information, that could be used to identify a "
258 "LogicalDevice. One example would be to hold the Operating "
259 "System's user friendly name for the Device in this "
260 "property."),
261 MaxLen ( 256 ), ArrayType ( "Indexed" ),
262 ModelCorrespondence {
263 "CIM_LogicalDevice.IdentifyingDescriptions" }]
264 string OtherIdentifyingInfo[];
265
266 [Description (
267 "The number of consecutive hours that this Device has been "
268 "powered, since its last power cycle."),
269 Units ( "Hours" ), Counter]
270 uint64 PowerOnHours;
271
272 [Description (
273 "The total number of hours that this Device has been "
274 a.dunfey 1.1 "powered."),
275 Units ( "Hours" ), Counter]
276 uint64 TotalPowerOnHours;
277
278 [Description (
279 "An array of free-form strings providing explanations and "
280 "details behind the entries in the OtherIdentifyingInfo "
281 "array. Note, each entry of this array is related to the "
282 "entry in OtherIdentifyingInfo that is located at the same "
283 "index."),
284 ArrayType ( "Indexed" ),
285 ModelCorrespondence { "CIM_LogicalDevice.OtherIdentifyingInfo" }]
286 string IdentifyingDescriptions[];
287
288 [Description (
289 "Additional availability and status of the Device, beyond "
290 "that specified in the Availability property. The "
291 "Availability property denotes the primary status and "
292 "availability of the Device. In some cases, this will not be "
293 "sufficient to denote the complete status of the Device. In "
294 "those cases, the AdditionalAvailability property can be "
295 a.dunfey 1.1 "used to provide further information. For example, a "
296 "Device's primary Availability may be \"Off line\" "
297 "(value=8), but it may also be in a low power state "
298 "(AdditonalAvailability value=14), or the Device could be "
299 "running Diagnostics (AdditionalAvailability value=5, \"In "
300 "Test\")."),
301 ValueMap { "1", "2", "3", "4", "5", "6", "7", "8", "9", "10",
302 "11", "12", "13", "14", "15", "16", "17", "18", "19", "20",
303 "21" },
304 Values { "Other", "Unknown", "Running/Full Power", "Warning",
305 "In Test", "Not Applicable", "Power Off", "Off Line",
306 "Off Duty", "Degraded", "Not Installed", "Install Error",
307 "Power Save - Unknown", "Power Save - Low Power Mode",
308 "Power Save - Standby", "Power Cycle",
309 "Power Save - Warning", "Paused", "Not Ready",
310 "Not Configured", "Quiesced" },
311 ModelCorrespondence { "CIM_LogicalDevice.Availability" }]
312 uint16 AdditionalAvailability[];
313
314 [Deprecated { "No value" }, Description (
315 "The MaxQuiesceTime property has been deprecated. When "
316 a.dunfey 1.1 "evaluating the use of Quiesce, it was determine that this "
317 "single property is not adequate for describing when a "
318 "device will automatically exit a quiescent state. In fact, "
319 "the most likely scenario for a device to exit a quiescent "
320 "state was determined to be based on the number of "
321 "outstanding requests queued rather than on a maximum time. "
322 "This will be re-evaluated and repositioned later. \n"
323 "Maximum time in milliseconds, that a Device can run in a "
324 "\"Quiesced\" state. A Device's state is defined in its "
325 "Availability and AdditionalAvailability properties, where "
326 "\"Quiesced\" is conveyed by the value 21. What occurs at "
327 "the end of the time limit is device-specific. The Device "
328 "may unquiesce, may offline or take other action. A value of "
329 "0 indicates that a Device can remain quiesced indefinitely."),
330 Units ( "MilliSeconds" )]
331 uint64 MaxQuiesceTime;
332
333 [Deprecated { "CIM_PowerManagementService.SetPowerState" },
334 Description (
335 "Sets the power state of the Device. The use of this method "
336 "has been deprecated. Instead, use the SetPowerState method "
337 a.dunfey 1.1 "in the associated PowerManagementService class.")]
338 uint32 SetPowerState(
339 [IN, Description (
340 "The power state to set."),
341 ValueMap { "1", "2", "3", "4", "5", "6" },
342 Values { "Full Power", "Power Save - Low Power Mode",
343 "Power Save - Standby", "Power Save - Other",
344 "Power Cycle", "Power Off" }]
345 uint16 PowerState,
346 [IN, Description (
347 "Time indicates when the power state should be set, "
348 "either as a regular date-time value or as an interval "
349 "value (where the interval begins when the method "
350 "invocation is received.")]
351 datetime Time);
352
353 [Description (
354 "Requests a reset of the LogicalDevice. The return value "
355 "should be 0 if the request was successfully executed, 1 if "
356 "the request is not supported and some other value if an "
357 "error occurred. In a subclass, the set of possible return "
358 a.dunfey 1.1 "codes could be specified, using a ValueMap qualifier on the "
359 "method. The strings to which the ValueMap contents are "
360 "'translated' may also be specified in the subclass as a "
361 "Values array qualifier.")]
362 uint32 Reset();
363
364 [Deprecated { "CIM_EnabledLogicalElement.RequestStateChange" },
365 Description (
366 "The EnableDevice method has been deprecated in lieu of the "
367 "more general RequestStateChange method that directly "
368 "overlaps with the functionality provided by this method. \n"
369 "Requests that the LogicalDevice be enabled (\"Enabled\" "
370 "input parameter = TRUE) or disabled (= FALSE). If "
371 "successful, the Device's StatusInfo/EnabledState properties "
372 "should reflect the desired state (enabled/disabled). Note "
373 "that this method's function overlaps with the "
374 "RequestedState property. RequestedState was added to the "
375 "model to maintain a record (i.e., a persisted value) of the "
376 "last state request. Invoking the EnableDevice method should "
377 "set the RequestedState property appropriately. \n"
378 "The return code should be 0 if the request was successfully "
379 a.dunfey 1.1 "executed, 1 if the request is not supported and some other "
380 "value if an error occurred. In a subclass, the set of "
381 "possible return codes could be specified, using a ValueMap "
382 "qualifier on the method. The strings to which the ValueMap "
383 "contents are 'translated' may also be specified in the "
384 "subclass as a Values array qualifier.")]
385 uint32 EnableDevice(
386 [IN, Description (
387 "If TRUE enable the device, if FALSE disable the device.")]
388 boolean Enabled);
389
390 [Deprecated { "CIM_EnabledLogicalElement.RequestStateChange" },
391 Description (
392 "The OnlineDevice method has been deprecated in lieu of the "
393 "more general RequestStateChange method that directly "
394 "overlaps with the functionality provided by this method. \n"
395 "Requests that the LogicalDevice be brought online "
396 "(\"Online\" input parameter = TRUE) or taken offline (= "
397 "FALSE). \"Online\" indicates that the Device is ready to "
398 "accept requests, and is operational and fully functioning. "
399 "In this case, the Device's Availability property would be "
400 a.dunfey 1.1 "set to a value of 3 (\"Running/Full Power\"). \"Offline\" "
401 "indicates that a Device is powered up and operational, but "
402 "not processing functional requests. In an offline state, a "
403 "Device may be capable of running diagnostics or generating "
404 "operational alerts. For example, when the \"Offline\" "
405 "button is pushed on a Printer, the Device is no longer "
406 "available to process print jobs, but could be available for "
407 "diagnostics or maintenance. \n"
408 "If this method is successful, the Device's Availability and "
409 "AdditionalAvailability properties should reflect the "
410 "updated status. If a failure occurs trying to bring the "
411 "Device online or offline, it should remain in its current "
412 "state. IE, the request, if unsuccessful, should not leave "
413 "the Device in an indeterminate state. When bringing a "
414 "Device back \"Online\", from an \"Offline\" mode, the "
415 "Device should be restored to its last \"Online\" state, if "
416 "at all possible. Only a Device that has an "
417 "EnabledState/StatusInfo of \"Enabled\" and has been "
418 "configured can be brought online or taken offline. \n"
419 "OnlineDevice should return 0 if successful, 1 if the "
420 "request is not supported at all, 2 if the request is not "
421 a.dunfey 1.1 "supported due to the current state of the Device, and some "
422 "other value if any other error occurred. In a subclass, the "
423 "set of possible return codes could be specified, using a "
424 "ValueMap qualifier on the method. The strings to which the "
425 "ValueMap contents are 'translated' may also be specified in "
426 "the subclass as a Values array qualifier. \n"
427 "Note that this method's function overlaps with the "
428 "RequestedState property. RequestedState was added to the "
429 "model to maintain a record (i.e., a persisted value) of the "
430 "last state request. Invoking the OnlineDevice method should "
431 "set the RequestedState property appropriately.")]
432 uint32 OnlineDevice(
433 [IN, Description (
434 "If TRUE, take the device online, if FALSE, take the "
435 "device OFFLINE.")]
436 boolean Online);
437
438 [Deprecated { "CIM_EnabledLogicalElement.RequestStateChange" },
439 Description (
440 "The QuiesceDevice method has been deprecated in lieu of the "
441 "more general RequestStateChange method that directly "
442 a.dunfey 1.1 "overlaps with the functionality provided by this method. \n"
443 "Requests that the LogicalDevice cleanly cease all current "
444 "activity (\"Quiesce\" input parameter = TRUE) or resume "
445 "activity (= FALSE). For this method to quiesce a Device, "
446 "that Device should have an Availability (or Additional "
447 "Availability) of \"Running/Full Power\" (value=3) and an "
448 "EnabledStatus/StatusInfo of \"Enabled\". For example, if "
449 "quiesced, a Device may then be offlined for diagnostics, or "
450 "disabled for power off and hot swap. For the method to "
451 "\"unquiesce\" a Device, that Device should have an "
452 "Availability (or AdditionalAvailability) of \"Quiesced\" "
453 "(value=21) and an EnabledStatus/StatusInfo of \"Enabled\". "
454 "In this case, the Device would be returned to an "
455 "\"Enabled\" and \"Running/Full Power\" status. \n"
456 "The method's return code should indicate the success or "
457 "failure of the quiesce. It should return 0 if successful, 1 "
458 "if the request is not supported at all, 2 if the request is "
459 "not supported due to the current state of the Device, and "
460 "some other value if any other error occurred. In a "
461 "subclass, the set of possible return codes could be "
462 "specified, using a ValueMap qualifier on the method. The "
463 a.dunfey 1.1 "strings to which the ValueMap contents are 'translated' may "
464 "also be specified in the subclass as a Values array "
465 "qualifier.")]
466 uint32 QuiesceDevice(
467 [IN, Description (
468 "If set to TRUE then cleanly cease all activity, if FALSE "
469 "resume activity.")]
470 boolean Quiesce);
471
472 [Description (
473 "Requests that the Device capture its current configuration, "
474 "setup and/or state information in a backing store. The goal "
475 "would be to use this information at a later time (via the "
476 "RestoreProperties method), to return a Device to its "
477 "present \"condition\". This method may not be supported by "
478 "all Devices. The method should return 0 if successful, 1 if "
479 "the request is not supported, and some other value if any "
480 "other error occurred. In a subclass, the set of possible "
481 "return codes could be specified, using a ValueMap qualifier "
482 "on the method. The strings to which the ValueMap contents "
483 "are 'translated' may also be specified in the subclass as a "
484 a.dunfey 1.1 "Values array qualifier.")]
485 uint32 SaveProperties();
486
487 [Description (
488 "Requests that the Device re-establish its configuration, "
489 "setup and/or state information from a backing store. The "
490 "intent is to capture this information at an earlier time "
491 "(via the SaveProperties method), and use it to return a "
492 "Device to this earlier \"condition\". This method may not "
493 "be supported by all Devices. The method should return 0 if "
494 "successful, 1 if the request is not supported, and some "
495 "other value if any other error occurred. In a subclass, the "
496 "set of possible return codes could be specified, using a "
497 "ValueMap qualifier on the method. The strings to which the "
498 "ValueMap contents are 'translated' may also be specified in "
499 "the subclass as a Values array qualifier.")]
500 uint32 RestoreProperties();
501 };
502
503
504 // ==================================================================
505 a.dunfey 1.1 // Realizes
506 // ==================================================================
507 [Association, Version ( "2.6.0" ), Description (
508 "CIM_Realizes is the association that defines the mapping "
509 "between LogicalDevices and the PhysicalElements that implement "
510 "them.")]
511 class CIM_Realizes : CIM_Dependency {
512
513 [Override ( "Antecedent" ), Description (
514 "The physical component that implements the Device.")]
515 CIM_PhysicalElement REF Antecedent;
516
517 [Override ( "Dependent" ), Description (
518 "The LogicalDevice.")]
519 CIM_LogicalDevice REF Dependent;
520 };
521
522
523 // ==================================================================
524 // SystemDevice
525 // ==================================================================
526 a.dunfey 1.1 [Association, Aggregation, Composition, Version ( "2.7.0" ),
527 Description (
528 "LogicalDevices may be aggregated by a System. This "
529 "relationship is made explicit by the SystemDevice association.")]
530 class CIM_SystemDevice : CIM_SystemComponent {
531
532 [Aggregate, Override ( "GroupComponent" ), Min ( 1 ), Max ( 1 ),
533 Description (
534 "The parent system in the Association.")]
535 CIM_System REF GroupComponent;
536
537 [Override ( "PartComponent" ), Weak, Description (
538 "The LogicalDevice that is a component of a System.")]
539 CIM_LogicalDevice REF PartComponent;
540 };
541
542
543 // ===================================================================
544 // DeviceServiceImplementation
545 // ===================================================================
546 [Association, Version ( "2.6.0" ), Description (
547 a.dunfey 1.1 "An association between a Service and how it is implemented. "
548 "The cardinality of this association is many-to-many. A Service "
549 "may be provided by more than one Logical Device, operating in "
550 "conjunction. And, any Device may provide more than one "
551 "Service. When multiple Devices are associated with a single "
552 "Service, it is assumed that these elements operate in "
553 "conjunction to provide the Service. If different "
554 "implementations of a Service exist, each of these "
555 "implementations would result in individual instantiations of "
556 "the Service object. These individual instantiations would then "
557 "have associations to the unique implementations.")]
558 class CIM_DeviceServiceImplementation : CIM_Dependency {
559
560 [Override ( "Antecedent" ), Description (
561 "The LogicalDevice.")]
562 CIM_LogicalDevice REF Antecedent;
563
564 [Override ( "Dependent" ), Description (
565 "The Service implemented using the Logical Device.")]
566 CIM_Service REF Dependent;
567 };
568 a.dunfey 1.1
569
570 // ===================================================================
571 // DeviceSAPImplementation
572 // ===================================================================
573 [Association, Version ( "2.6.0" ), Description (
574 "An association between a ServiceAccessPoint and how it is "
575 "implemented. The cardinality of this association is "
576 "many-to-many. A SAP may be provided by more than one "
577 "LogicalDevice, operating in conjunction. And, any Device may "
578 "provide more than one ServiceAccessPoint. When many "
579 "LogicalDevices are associated with a single SAP, it is assumed "
580 "that these elements operate in conjunction to provide the "
581 "AccessPoint. If different implementations of a SAP exist, each "
582 "of these implementations would result in individual "
583 "instantiations of the ServiceAccessPoint object. These "
584 "individual instantiations would then have associations to the "
585 "unique implementations.")]
586 class CIM_DeviceSAPImplementation : CIM_Dependency {
587
588 [Override ( "Antecedent" ), Description (
589 a.dunfey 1.1 "The LogicalDevice.")]
590 CIM_LogicalDevice REF Antecedent;
591
592 [Override ( "Dependent" ), Description (
593 "The ServiceAccessPoint implemented using the LogicalDevice.")]
594 CIM_ServiceAccessPoint REF Dependent;
595 };
596
597 // ===================================================================
598 // end of file
599 // ===================================================================
|
Return to
Core_Device.mof
CVS log
Up to [Pegasus] / pegasus / Schemas / CIM29