association CIM_ProtectedExtentBasedOn : CIM_BasedOn

Description:

Protected StorageExtents map to an underlying StorageExtent. This mapping includes information about the placement of check data on the underlying extent. The mapping is made explicit in this association.

Definition:

Feature Type Class Origin Qualifiers
Antecedent CIM_StorageExtent CIM_Dependency
Override Antecedent
Description The underlying StorageExtent.
Key TRUE
Dependent CIM_StorageExtent CIM_Dependency
Override Dependent
Description The Protected Space is built on this StorageExtent.
Key TRUE
StartingAddress uint64 CIM_BasedOn
Override StartingAddress
Description The starting logical block address of the underlying StorageExtent from which this protected StorageExtent is derived. In SCC, this is equivalent to the START LBA_P field in the Redundancy Group P_Extent Descriptor.
MappingStrings MIF.DMTF|Physical Extent|001.2
EndingAddress uint64 CIM_BasedOn
Description EndingAddress indicates where in lower level storage, the higher level Extent ends. This property is useful when mapping non-contiguous Extents into a higher level grouping.
OrderIndex uint16 CIM_BasedOn
Description If there is an order to the BasedOn associations that describe how a higher level StorageExtent is assembled, the OrderIndex property indicates this. When an order exists, the instances of BasedOn with the same Dependent value (i.e., the same higher level Extent) should place unique values in the OrderIndex property. The lowest value implies the first member of the collection of lower level Extents, and increasing values imply successive members of the collection. If there is no ordered relationship, a value of zero should be specified. An example of the use of this property is to define a RAID-0 striped array of 3 disks. The resultant RAID array is a StorageExtent that is dependent on (BasedOn) the StorageExtents that describe each of the 3 disks. The OrderIndex of each BasedOn association from the disk Extents to the RAID array could be specified as 1, 2 and 3 to indicate the order in which the disk Extents are used to access the RAID data.
NumberOfBlocks uint64 CIM_ProtectedExtentBasedOn
Description The size of the protected space. Note that this is limited by the Antecedent->NumberOfBlocks, but is included explicitly to provide for the DMTF MIF mapping. In SCC, this is equivalent to the NUMBER OF LBA_P(s) field in the Redundancy Group P_Extent Descriptor.
MappingStrings MIF.DMTF|Physical Extent|001.3
ModelCorrespondence CIM_StorageExtent.NumberOfBlocks
BlockSize uint64 CIM_ProtectedExtentBasedOn
Description The block size of the protected space. Note that this is limited by the Antecedent->BlockSize. In SCC, this is equivalent to the NUMBER OF BYTES PER LBA_P field in the Redundancy Group P_Extent Descriptor.
Units Bytes
MappingStrings MIF.DMTF|Physical Extent|001.4
ModelCorrespondence CIM_StorageExtent.BlockSize
PUnit byte
UnitsBeforeCheckDataInterleave uint64 CIM_ProtectedExtentBasedOn
Description Number of bytes of user data to skip before starting the check data interleave.
Units Bytes
MappingStrings MIF.DMTF|Physical Extent|001.6
PUnit byte
UnitsOfCheckData uint64 CIM_ProtectedExtentBasedOn
Description Number of bytes to be reserved for check data.
Units Bytes
MappingStrings MIF.DMTF|Physical Extent|001.7
PUnit byte
UnitsOfUserData uint64 CIM_ProtectedExtentBasedOn
Description Number of bytes to be reserved for user data.
Units Bytes
MappingStrings MIF.DMTF|Physical Extent|001.8
PUnit byte

Typographical Conventions:

  1. Inherited properties are italicized.
  2. Local properties are bolded.
  3. Key properties are highlighted in gold

Generated by mof2html v.2.1.0(002). simplewbem.org Mon Nov 2 09:43:16 2009