Class CIM_PhysicalPackage

Used in features: Hardware Asset
Compatible with the following Intel AMT Releases: 3.0, 3.2, 4.0, 5.0, 5.1, 6.0, 6.1, 6.2, 7.0, 8.0, 8.1, 9.0, 9.5
CIM_ManagedElement
   extended by CIM_ManagedSystemElement
      extended by CIM_PhysicalElement
         extended by CIM_PhysicalPackage

Known Subclasses:
CIM_Card CIM_PhysicalFrame CIM_Chassis

class CIM_PhysicalPackage
extends CIM_PhysicalElement

General Information:
The PhysicalPackage class represents PhysicalElements that contain or host other components. Examples are a Rack enclosure or an adapter Card.

Qualifiers:
-------------
Version=2.18.0
UMLPackagePath=CIM::Physical::Package


Supported Fields Summary
 boolean CanBeFRUed
Boolean that indicates whether this PhysicalElement can be FRUed (TRUE) or not (FALSE).
 string VendorEquipmentType
A vendor-specific hardware type for the PhysicalElement . . .
 string SerialNumber
A manufacturer-allocated number used to identify the Physical Element.
 string SKU
The stock-keeping unit number for this PhysicalElement.
 string Model
The name by which the PhysicalElement is generally known.
 string Manufacturer
The name of the organization responsible for producing the PhysicalElement . . .
 string ElementName

 string CreationClassName Key
CreationClassName indicates the name of the class or the subclass used in the creation of an instance . . .
 string Tag Key
An arbitrary string that uniquely identifies the Physical Element and serves as the key of the Element . . .
 uint16[] OperationalStatus
Indicates the current statuses of the element . . .
 uint16 PackageType
Enumeration defining the type of the PhysicalPackage . . .

Methods Summary
  Get(Instance)
Gets the representation of the instance
  Pull(EnumerationContext, MaxElements)
Pulls instances of this class, following an Enumerate operation
  Enumerate()
Enumerates the instances of this class
  Release(EnumerationContext)
Releases an enumeration context

Field Detail

CanBeFRUed

public boolean CanBeFRUed
General Information:
Boolean that indicates whether this PhysicalElement can be FRUed (TRUE) or not (FALSE).

Product Specific Usage:
Additional Notes:
1) 'CanBeFRUed' property is enabled in Intel AMT Release 6.1 and later releases.

Qualifiers:
-------------
MappingStrings={MIB.IETF|Entity-MIB.entPhysicalIsFRU}


VendorEquipmentType

public string VendorEquipmentType
General Information:
A vendor-specific hardware type for the PhysicalElement. It describes the specific equipment type for the element, as defined by the vendor or manufacturer.

Product Specific Usage:
Additional Notes:
1) 'VendorEquipmentType' property is enabled in Intel AMT Release 6.1 and later releases.

Qualifiers:
-------------
MappingStrings={MIB.IETF|Entity-MIB.entPhysicalVendorType}
MaxLen=10


SerialNumber

public string SerialNumber
General Information:
A manufacturer-allocated number used to identify the Physical Element.

Qualifiers:
-------------
MaxLen=256
MappingStrings={MIB.IETF|Entity-MIB.entPhysicalSerialNum, MIF.DMTF|FRU|003.7}


SKU

public string SKU
General Information:
The stock-keeping unit number for this PhysicalElement.

Product Specific Usage:
Additional Notes:
1) 'SKU' property is enabled in Intel AMT Release 6.1 and later releases.

Qualifiers:
-------------
MaxLen=20


Model

public string Model
General Information:
The name by which the PhysicalElement is generally known.

Qualifiers:
-------------
MaxLen=41
MappingStrings={MIB.IETF|Entity-MIB.entPhysicalDescr, MIF.DMTF|FRU|003.5}


Manufacturer

public string Manufacturer
General Information:
The name of the organization responsible for producing the PhysicalElement. This organization might be the entity from whom the Element is purchased, but this is not necessarily true. The latter information is contained in the Vendor property of CIM_Product.

Product Specific Usage:
Additional Notes:
1) 'Manufacturer' property is enabled in Intel AMT Release 6.1 and later releases.

Qualifiers:
-------------
MaxLen=20
MappingStrings={MIB.IETF|Entity-MIB.entPhysicalMfgName, MIF.DMTF|FRU|003.4}


ElementName

public string ElementName
General Information:


Qualifiers:
-------------
Override=ElementName
MappingStrings={MIB.IETF|Entity-MIB.entPhysicalName}
MaxLen=65


CreationClassName Key

public string CreationClassName
General Information:
CreationClassName indicates the name of the class or the subclass used in the creation of an instance. When used with the other key properties of this class, this property allows all instances of this class and its subclasses to be uniquely identified.

Qualifiers:
-------------
Key
MaxLen=19


Tag Key

public string Tag
General Information:
An arbitrary string that uniquely identifies the Physical Element and serves as the key of the Element. The Tag property can contain information such as asset tag or serial number data. The key for PhysicalElement is placed very high in the object hierarchy in order to independently identify the hardware or entity, regardless of physical placement in or on Cabinets, Adapters, and so on. For example, a hotswappable or removable component can be taken from its containing (scoping) Package and be temporarily unused. The object still continues to exist and can even be inserted into a different scoping container. Therefore, the key for Physical Element is an arbitrary string and is defined independently of any placement or location-oriented hierarchy.

Qualifiers:
-------------
Key
MaxLen=50


OperationalStatus

public uint16[] OperationalStatus
General Information:
Indicates the current statuses of the element. Various operational statuses are defined. Many of the enumeration's values are self-explanatory. However, a few are not and are described here in more detail.
"Stressed" indicates that the element is functioning, but needs attention. Examples of "Stressed" states are overload, overheated, and so on.
"Predictive Failure" indicates that an element is functioning nominally but predicting a failure in the near future.
"In Service" describes an element being configured, maintained, cleaned, or otherwise administered.
"No Contact" indicates that the monitoring system has knowledge of this element, but has never been able to establish communications with it.
"Lost Communication" indicates that the ManagedSystem Element is known to exist and has been contacted successfully in the past, but is currently unreachable.
"Stopped" and "Aborted" are similar, although the former implies a clean and orderly stop, while the latter implies an abrupt stop where the state and configuration of the element might need to be updated.
"Dormant" indicates that the element is inactive or quiesced.
"Supporting Entity in Error" indicates that this element might be "OK" but that another element, on which it is dependent, is in error. An example is a network service or endpoint that cannot function due to lower-layer networking problems.
"Completed" indicates that the element has completed its operation. This value should be combined with either OK, Error, or Degraded so that a client can tell if the complete operation Completed with OK (passed), Completed with Error (failed), or Completed with Degraded (the operation finished, but it did not complete OK or did not report an error).
"Power Mode" indicates that the element has additional power model information contained in the Associated PowerManagementService association.
"Relocating" indicates the element is being relocated.
OperationalStatus replaces the Status property on ManagedSystemElement to provide a consistent approach to enumerations, to address implementation needs for an array property, and to provide a migration path from today's environment to the future. This change was not made earlier because it required the deprecated qualifier. Due to the widespread use of the existing Status property in management applications, it is strongly recommended that providers or instrumentation provide both the Status and OperationalStatus properties. Further, the first value of OperationalStatus should contain the primary status for the element. When instrumented, Status (because it is single-valued) should also provide the primary status of the element.

Qualifiers:
-------------
ValueMap={0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, .., 0x8000..}
Values={Unknown, Other, OK, Degraded, Stressed, Predictive Failure, Error, Non-Recoverable Error, Starting, Stopping, Stopped, In Service, No Contact, Lost Communication, Aborted, Dormant, Supporting Entity in Error, Completed, Power Mode, Relocating, DMTF Reserved, Vendor Reserved}
ArrayType=Indexed
ModelCorrespondence={CIM_ManagedSystemElement.StatusDescriptions}


PackageType

public uint16 PackageType
General Information:
Enumeration defining the type of the PhysicalPackage. Note that this enumeration expands on the list in the Entity MIB (the attribute, entPhysicalClass). The numeric values are consistent with CIM's enum numbering guidelines, but are slightly different than the MIB's values.
Unknown - indicates that the package type is not known.
Other - The package type does not correspond to an existing enumerated value. The value is specified using the OtherPackageType property.
The values "Rack" through "Port/Connector" are defined per the Entity-MIB (where the semantics of rack are equivalent to the MIB's 'stack' value). The other values (for battery, processor, memory, power source/generator and storage media package) are self-explanatory.
A value of "Blade" should be used when the PhysicalPackage contains the operational hardware aspects of a ComputerSystem, without the supporting mechanicals such as power and cooling. For example, a Blade Server includes processor(s) and memory, and relies on the containing chassis to supply power and cooling. In many respects, a Blade can be considered a "Module/Card". However, it is tracked differently by inventory systems and differs in terms of service philosophy. For example, a Blade is intended to be hot-plugged into a hosting enclosure without requiring additional cabling, and does not require a cover to be removed from the enclosure for installation. Similarly, a "Blade Expansion" has characteristics of a "Blade" and a "Module/Card". However, it is distinct from both due to inventory tracking and service philosophy, and because of its hardware dependence on a Blade. A Blade Expansion must be attached to a Blade prior to inserting the resultant assembly into an enclosure.

Qualifiers:
-------------
ValueMap={0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17}
Values={Unknown, Other, Rack, Chassis/Frame, Cross Connect/Backplane, Container/Frame Slot, Power Supply, Fan, Sensor, Module/Card, Port/Connector, Battery, Processor, Memory, Power Source/Generator, Storage Media Package (e.g., Disk or Tape Drive), Blade, Blade Expansion}
MappingStrings={MIB.IETF|ENTITY-MIB.entPhysicalClass}
ModelCorrespondence={CIM_PhysicalPackage.OtherPackageType}


Method Detail

Get

public  Get([OUT]CIM_PhysicalPackage Instance)
Permission Information:
Permitted realms: ADMIN_SECURITY_HARDWARE_ASSET_REALM

General Information:
Gets the representation of the instance

Pull

public  Pull([IN]String EnumerationContext, [IN]String MaxElements)
Permission Information:
All users permitted to use method, only instances to whom the user has permissions will be returned

General Information:
Pulls instances of this class, following an Enumerate operation

Enumerate

public  Enumerate()
Permission Information:
All users permitted to use method

General Information:
Enumerates the instances of this class

Release

public  Release([IN]String EnumerationContext)
Permission Information:
All users permitted to use method

General Information:
Releases an enumeration context

Copyright © 2006-2013, Intel Corporation. All rights reserved.