1 tony 1.1 // ===================================================================
2 // Title: System Boot 2.8
3 // Filename: System28_Boot.mof
4 // Version: 2.8
5 // Status: Final
6 // Date: Jan 26, 2004
7 // ===================================================================
8 // Copyright 1998-2003 Distributed Management Task Force, Inc. (DMTF).
9 // All rights reserved.
10 // DMTF is a not-for-profit association of industry members dedicated
11 // to promoting enterprise and systems management and interoperability.
12 // DMTF specifications and documents may be reproduced for uses
13 // consistent with this purpose by members and non-members,
14 // provided that correct attribution is given.
15 // As DMTF specifications may be revised from time to time,
16 // the particular version and release date should always be noted.
17 //
18 // Implementation of certain elements of this standard or proposed
19 // standard may be subject to third party patent rights, including
20 // provisional patent rights (herein "patent rights"). DMTF makes
21 // no representations to users of the standard as to the existence
22 tony 1.1 // of such rights, and is not responsible to recognize, disclose, or
23 // identify any or all such third party patent right, owners or
24 // claimants, nor for any incomplete or inaccurate identification or
25 // disclosure of such rights, owners or claimants. DMTF shall have no
26 // liability to any party, in any manner or circumstance, under any
27 // legal theory whatsoever, for failure to recognize, disclose, or
28 // identify any such third party patent rights, or for such party's
29 // reliance on the standard or incorporation thereof in its product,
30 // protocols or testing procedures. DMTF shall have no liability to
31 // any party implementing such standard, whether such implementation
32 // is foreseeable or not, nor to any patent owner or claimant, and shall
33 // have no liability or responsibility for costs or losses incurred if
34 // a standard is withdrawn or modified after publication, and shall be
35 // indemnified and held harmless by any party implementing the
36 // standard from any and all claims of infringement by a patent owner
37 // for such implementations.
38 //
39 // For information about patents held by third-parties which have
40 // notified the DMTF that, in their opinion, such patent may relate to
41 // or impact implementations of DMTF standards, visit
42 // http://www.dmtf.org/about/policies/disclosures.php.
43 tony 1.1 // ===================================================================
44 // Description: The System Model defines system related management
45 // concepts. This file defines the specific concepts for
46 // booting a system.
47 //
48 // The object classes below are listed in an order that
49 // avoids forward references. Required objects, defined
50 // by other working groups, are omitted.
51 // ==================================================================
52 // Change Log for 2.8 Final
53 // CR1233 - Sysdev Omnibus Minor MOF correction CR
54 //
55 // Change Log for v2.7 - None
56 //
57 // Change Log for v2.7
58 // CR718 - Promote HostedBootSAP.Antecedent from UnitaryComputer
59 // System to ComputerSystem
60 // ===================================================================
61
62 #pragma locale ("en_US")
63
64 tony 1.1
65 // ===================================================================
66 // BootService
67 // ===================================================================
68 [Version ( "2.6.0" ), Description (
69 "BootService represents the functionality provided by a Device, "
70 "software or via a Network to load an Operating System on a "
71 "UnitaryComputerSystem.")]
72 class CIM_BootService : CIM_Service {
73 };
74
75
76 // ===================================================================
77 // BootSAP
78 // ===================================================================
79 [Version ( "2.6.0" ), Description (
80 "A representation of the access points of a BootService.")]
81 class CIM_BootSAP : CIM_ServiceAccessPoint {
82 };
83
84
85 tony 1.1 // ===================================================================
86 // BootServiceAccessBySAP
87 // ===================================================================
88 [Association, Version ( "2.6.0" ), Description (
89 "BootServiceAccessBySAP is the relationship between a Boot "
90 "Service and its access points.")]
91 class CIM_BootServiceAccessBySAP : CIM_ServiceAccessBySAP {
92
93 [Override ( "Antecedent" ), Description (
94 "The BootService.")]
95 CIM_BootService REF Antecedent;
96
97 [Override ( "Dependent" ), Description (
98 "An access point for the BootService.")]
99 CIM_BootSAP REF Dependent;
100 };
101
102
103 // ===================================================================
104 // HostedBootService
105 // ===================================================================
106 tony 1.1 [Association, Version ( "2.6.0" ), Description (
107 "HostedBootService defines the hosting System for a Boot "
108 "Service. Since this relationship is subclassed from Hosted "
109 "Service, it inherits the scoping/naming scheme defined for "
110 "Service - where a Service is weak to its hosting System.")]
111 class CIM_HostedBootService : CIM_HostedService {
112
113 [Override ( "Antecedent" ), Min ( 1 ), Max ( 1 ), Description (
114 "The hosting System.")]
115 CIM_System REF Antecedent;
116
117 [Override ( "Dependent" ), Description (
118 "The BootService hosted on the System.")]
119 CIM_BootService REF Dependent;
120 };
121
122
123 // ===================================================================
124 // HostedBootSAP
125 // ===================================================================
126 [Association, Version ( "2.7.0" ), Description (
127 tony 1.1 "HostedBootSAP defines the hosting UnitaryComputerSystem for a "
128 "BootSAP. Since this relationship is subclassed from "
129 "HostedAccessPoint, it inherits the scoping/naming scheme "
130 "defined for AccessPoint - where an AccessPoint is weak to its "
131 "hosting System. In this case, a BootSAP must be weak to its "
132 "hosting UnitaryComputerSystem.")]
133 class CIM_HostedBootSAP : CIM_HostedAccessPoint {
134
135 [Override ( "Antecedent" ), Min ( 1 ), Max ( 1 ), Description (
136 "The UnitaryComputerSystem.")]
137 CIM_ComputerSystem REF Antecedent;
138
139 [Override ( "Dependent" ), Description (
140 "The BootSAP hosted on the UnitaryComputer System.")]
141 CIM_BootSAP REF Dependent;
142 };
143
144
145 // ===================================================================
146 // OOBAlertService
147 // ===================================================================
148 tony 1.1 [Version ( "2.6.0" ), Description (
149 "This Service is implemented by a LogicalDevice (e.g. a "
150 "NetworkAdapter or Modem) that is capable of sending alert "
151 "messages to a remote destination. The alert messages reflect "
152 "the state of one or more ManagedSystemElements. The Elements "
153 "for which alert messages are forwarded, are defined by "
154 "enumerating the ProvidesServiceToElement association for the "
155 "Service. Out of Band (OOB) refers to the mechanisms in use "
156 "when normal OS-based management mechanisms are not possible. "
157 "This occurs when the OS is down or not functioning properly.")]
158 class CIM_OOBAlertService : CIM_Service {
159
160 [Description (
161 "The type of the alert destination. For example, the alert "
162 "may be received by an application listening on a UDP Port "
163 "on a remote destination, or could be sent to a pager "
164 "(values 4 or 2, respectively)."),
165 ValueMap { "0", "1", "2", "3", "4" },
166 Values { "Unknown", "Other", "Pager", "TCP Port", "UDP Port" },
167 ModelCorrespondence {
168 "CIM_OOBAlertService.OtherDestinationTypeDescription" }]
169 tony 1.1 uint16 DestinationType;
170
171 [Description (
172 "The description of the alert DestinationType. This is used "
173 "when the DestinationType is set to \"Other\" (value=1)."),
174 ModelCorrespondence { "CIM_OOBAlertService.DestinationType" }]
175 string OtherDestinationTypeDescription;
176
177 [Description (
178 "The address where this Service sends the alerts. The format "
179 "of this address depends on the DestinationType. For "
180 "example, if the DestinationType is a UDP Port (value=4), "
181 "then this property contains a string identifying the IP "
182 "address of the Port (for example, 111.222.333.444:4567). If "
183 "DestinationType is a pager (value=2), then the address is a "
184 "Pager number (for example, 18002257654).")]
185 string DestinationAddress;
186
187 [Description (
188 "The format of the Alert Message sent by the Service."),
189 ValueMap { "0", "1", "2", "3", "4", "5" },
190 tony 1.1 Values { "Unknown", "Other", "Numeric", "AlphaNumeric",
191 "Free Form Text", "Platform Event Trap" },
192 ModelCorrespondence {
193 "CIM_OOBAlertService.OtherMessageFormatDescription" }]
194 uint16 MessageFormat;
195
196 [Description (
197 "The description of the format of the alert message used by "
198 "the Service when the AlertMessageFormat property is set to "
199 "\"Other\" (value=1)."),
200 ModelCorrespondence { "CIM_OOBAlertService.MessageFormat" }]
201 string OtherMessageFormatDescription;
202
203 [Description (
204 "If the AlertService only uses a fixed message to send an "
205 "alert, then this flag should be set to TRUE.")]
206 boolean OnlySendsFixedMessage;
207
208 [Description (
209 "The AlertService may require some fixed data to send as "
210 "part of the message. This may include things like the "
211 tony 1.1 "address or name of the System. This string contains the "
212 "complete message when the property, OnlySendsFixedMessage, "
213 "is set to TRUE.")]
214 string FixedPartOfMessage;
215
216 [Description (
217 "If the destination is capable of sending an acknowledgement "
218 "to the alert, then this flag is set to TRUE. The format of "
219 "the acknowledgement is determined by the DestinationType "
220 "and the MessageFormat.")]
221 boolean DestinationIsAckCapable;
222
223 [Description (
224 "The AlertService may retry and send an alert more than "
225 "once. The RetryCount identifies how often the operation "
226 "will be repeated. If DestinationIsAckCapable is set to "
227 "TRUE, then the retry will only be done if an Ack is not "
228 "received. Otherwise, the retries are done unconditionally.")]
229 uint16 RetryCount;
230
231 [Description (
232 tony 1.1 "The interval between each successive retry, in seconds. If "
233 "DestinationIsAckCapable is set to TRUE, then this interval "
234 "is used as a timeout interval, before the next retry is "
235 "done."),
236 Units ( "Seconds" )]
237 uint16 RetryInterval;
238
239 [Description (
240 "If the OOB Alerting service is capable of sending Presence "
241 "heart beat messages."),
242 Read]
243 boolean PresenceHeartbeatCapable;
244
245 [Description (
246 "When set to true causes the OOBAlertService to send "
247 "Presence heart beat messages."),
248 ModelCorrespondence {
249 "CIM_OOBAlertService.PresenceHeartbeatCapable" }]
250 boolean EnablePresenceHeartbeats;
251 };
252
253 tony 1.1
254 // ===================================================================
255 // WakeUpService
256 // ===================================================================
257 [Version ( "2.8.0" ), Description (
258 "WakeUpService allows a UnitaryComputerSystem to be woken up "
259 "from a low power sleep state. This Service is implemented by a "
260 "LogicalDevice (e.g. NetworkAdapter or Modem) that is capable "
261 "of receiving wakeup messages, and notifying the System.")]
262 class CIM_WakeUpService : CIM_Service {
263
264 [Description (
265 "The Type of the WakeUp Service."),
266 ValueMap { "0", "1", "2", "3", "4" },
267 Values { "Unknown", "Other", "Wake On LAN - Magic Packet",
268 "Wake on LAN - Packet Filtering", "Wake On Ring" },
269 ModelCorrespondence {
270 "CIM_WakeUpService.OtherWakeUpTypeDescription" }]
271 uint16 WakeUpType;
272
273 [Description (
274 tony 1.1 "A description of the type of WakeUpService used when "
275 "WakeUpType is set to \"Other\" (value=1)."),
276 ModelCorrespondence { "CIM_WakeUpService.WakeUpType" }]
277 string OtherWakeUpTypeDescription;
278
279 [Description (
280 "The filter type on the packets/messages that trigger the "
281 "WakeUpService. This field is only used when the WakeUp Type "
282 "is set to \"Wake On LAN - Packet Filtering\" (value =3)."),
283 ValueMap { "0", "1", "2", "3", "4", "5", "6", "7" },
284 Values { "Unknown", "Other", "ARP Broadcast",
285 "Neighbor Discovery Multicast",
286 "IP Packet with Directed MAC Address",
287 "IPX Diagnostic Responder", "NBT Name Query",
288 "Binary Match" },
289 ModelCorrespondence {
290 "CIM_WakeUpService.OtherFilterTypeDescription" }]
291 uint16 FilterType;
292
293 [Description (
294 "The binary data that is used to compare the contents of the "
295 tony 1.1 "received packet. This is used when the FilterType is set to "
296 "\"Binary Match\" (value=7). This could also be used when "
297 "the FilterType is set to \"Other\" (value=1)."),
298 OctetString]
299 uint8 FilterData[];
300
301 [Description (
302 "The description of the format of the FilterType used by the "
303 "Service when the FilterType is set to \"Other\" (value=1)."),
304 ModelCorrespondence { "CIM_WakeUpService.FilterType" }]
305 string OtherFilterTypeDescription;
306 };
307
308
309 // ===================================================================
310 // end of file
311 // ===================================================================
|
Return to
System28_Boot.mof
CVS log
Up to [Pegasus] / pegasus / Schemas / CIM28