| Properties Summary |
| Defined in: lstorage:DasScsiLun |
|
scalar:Bool
|
deferredNaming (lstorage:DasScsiLun:deferredNaming)
NO COMMENTS
|
|
scalar:Bool
|
expandToAvail (lstorage:DasScsiLun:expandToAvail)
Indicates this LUN should use up any additional space available in local storage
|
storage:Size
scalar:Uint64
|
fractionalSize (lstorage:DasScsiLun:fractionalSize)
The fractionalSize, in MB, is additional size which is logically added
to the size. This is for users who desire greater precision. For example,
if you want 1.5GB, you would specify a size of 1 and fractionalSize of 512.
By default, this property is 0, so for users who only care about integral
values of GB, this property can be safely ignored.
|
naming:Name
string:Basic
|
localDiskPolicyName (lstorage:DasScsiLun:localDiskPolicyName)
Name reference to the local disk configuration policy specifying
configuration of local storage. Note that local disk policy can
also be contained by the profile definition, in which case local
definition is always checked first and then, if not found, hierarchical
resolution by name is performed.
|
naming:Name
string:Basic
|
name (lstorage:DasScsiLun:name)
Overrides:lstorage:Item:name
Lun name cannot be changed
|
|
reference:Object
|
operLocalDiskPolicyName (lstorage:DasScsiLun:operLocalDiskPolicyName)
NO COMMENTS
|
lstorage:Order
scalar:Uint16
|
order (lstorage:DasScsiLun:order)
NO COMMENTS
|
storage:Size
scalar:Uint64
|
size (lstorage:DasScsiLun:size)
Overrides:lstorage:ScsiLun:size
NO COMMENTS
|
lstorage:StorageClass
scalar:Enum8
|
storageClass (lstorage:DasScsiLun:storageClass)
Overrides:lstorage:ScsiLun:storageClass
NO COMMENTS
|
| Defined in: lstorage:ScsiLun |
lstorage:AutoDeploy
scalar:Enum8
|
autoDeploy (lstorage:ScsiLun:autoDeploy)
Indicates if the SCSI LUN should be automatically deployed at association.
This determines the initial setting of the adminAction in the instance ref.
Setting to undeployed provides a way to be able to set properties of the
instance ref prior to deployment
|
lstorage:BootDevice
scalar:Enum8
|
bootDev (lstorage:ScsiLun:bootDev)
Indicates if this SCSI LUN has been marked as a boot LUN in the Boot policy
or boot definition (i.e. under lsboot:ADef).
Since multiple LUNs can be marked as a boot device in the boot policy, a server
will not necessarily boot from a given LUN marked as bootable.
|
|
reference:Object
|
lunDn (lstorage:ScsiLun:lunDn)
An object reference to the configured LUN.
This property is empty until the LUN is actually configured in the storage sub-system.
This property is not set when the containing lstorage:Profile is a template.
|
lstorage:LunMapType
scalar:Enum8
|
lunMapType (lstorage:ScsiLun:lunMapType)
The type of OS that will use this storage item.
The system may optimize the LUN to get better better performance for a particular
operating system. For example, this can be done by adjusting the block alignment
on physical disk to be optimized for a particular file system.
Specifies whether this LUN can be accessed by a single initiator
or can be shared amongst multiple initiators.
When the user defines a storage profile templates, multiple ls:Server MOs
can use the same storage profile template. In that case, each server will get
an instantiated storage profile.
If the storage profile template includes a "shared" lstorage:ScsiLun,
the LUN will be shared among all ls:Server using the template.
If the storage profile template includes a "non-shared" lstorage:ScsiLun,
a new LUN will be created for each ls:Server.
For direct attach storage LUNs, sharing a LUN is possible with the possible constraints:
At most two servers can share a LUN
Both servers must be connected through a JBOD enclosure.
The JBOD enclosure must have dual-port SAS disks
With non-HA SCSI controllers, the SAS disks must be configured in JBOD mode
(no RAID configuration). HA SCSI controllers may suppport shared LUNs with RAID
configuration.
|
| Defined in: mo:TopProps |
mo:ModificationChildAction
scalar:Bitmask32
|
childAction (mo:TopProps:childAction)
|
|
reference:Object
|
dn (mo:TopProps:dn)
The Distinguished Name (dn) unambiguously identifies an object in the system.
The dn provides a fully qualified path from the top of the object tree, all the way to
the object. It is built as a sequence of relative names separated by the "/"
character.
For example:
< ... dn = "sys/chassis-5/blade-2/adaptor-1" />
|
|
reference:RN
|
rn (mo:TopProps:rn)
The Relative Name (rn) uniquely identifies an object within a given context.
Note that a dn is comprised of a sequence of relative names. For example,
the context "sys/chassis-1/blade-1/adaptor-1/host-eth-2" can be thought
of as the following expression:
dn = <root object>/{rn}/{rn}/{rn}/{rn}/{rn}.
The rn can then be used to identify the object (for instance, "adaptor-1")
within the context:
<... rn ="../" />
|
mo:InstSaclType
scalar:Bitmask8
|
sacl (mo:TopProps:sacl)
The system acl property for each Managed Object. br/>
This property is a 8 bit mask and supports the following values :-
a: del
b: mod
c: addchild
d: cascade
By default all Managed Objects have the following permissions
a: del
b: mod
c: addchild
This property is persisted in the db. If this property has a value none
it means, the user has read only permissions on this object.
|
mo:ModificationStatus
scalar:Bitmask32
|
status (mo:TopProps:status)
This property controls the life cycle of a managed object
|
adminState
Type: lstorage:AdminState
Primitive Type: scalar:Enum8
Units: null
Encrypted: false
Access: admin
Category: TopLevelRegular
Property Validators:
Comments:
-
Specifies the administrative state of this storage item.
| |
| Constants |
| online |
1 |
"online" means the storage item should be configured in the storage sub-system
and can be used by the storage initiator.
By default, the storage item is automatically configured when the service profile is
associated.
|
| offline |
2 |
"offline" means the storage item should be put in an offline mode where it is
no longer accessible from the initiator. This can be used for maintenance purpose.
When the item is "offline". the data is not discarded and can be accessed immediately
after setting the storage item back to "online".
|
| undeployed |
4 |
Specify the storage item should be configured immediately, even if the service
profile is not associated. This value is used to pre-deploy storage items.
When the XML API user sets the value to "deploy", the system triggers an FSM to
configure the LUN and then sets the value to "online".
It is not always possible to pre-deploy storage items. For example, local LUNs
cannot be configured before service profile association.
Specify the storage item should be undeployed. This is used for instance
ref's. This allows the user to configure certain properties of the instance
ref prior to deployment. It also allows the user to release a deployed LUN
|
| DEFAULT |
online(1) |
"online" means the storage item should be configured in the storage sub-system
and can be used by the storage initiator.
By default, the storage item is automatically configured when the service profile is
associated.
|
|
autoDeploy
Type: lstorage:AutoDeploy
Primitive Type: scalar:Enum8
Units: null
Encrypted: false
Access: admin
Category: TopLevelRegular
Property Validators:
Comments:
-
Indicates if the SCSI LUN should be automatically deployed at association.
This determines the initial setting of the adminAction in the instance ref.
Setting to undeployed provides a way to be able to set properties of the
instance ref prior to deployment
| |
| Constants |
| auto-deploy |
0 |
Specifies the SCSI LUN should be deployed automatically on association
|
| no-auto-deploy |
1 |
Specifies the SCSI LUN should not be deployed automatically on association.
This allows the user to configure properties on the instance ref prior to
deployment.
|
| DEFAULT |
auto-deploy(0) |
Specifies the SCSI LUN should be deployed automatically on association
|
|
bootDev
Type: lstorage:BootDevice
Primitive Type: scalar:Enum8
Units: null
Encrypted: false
Access: implicit
Category: TopLevelRegular
Property Validators:
Comments:
-
Indicates if this SCSI LUN has been marked as a boot LUN in the Boot policy
or boot definition (i.e. under lsboot:ADef).
Since multiple LUNs can be marked as a boot device in the boot policy, a server
will not necessarily boot from a given LUN marked as bootable.
| |
| Constants |
| disabled |
0 |
Indicates the SCSI LUN is not configured as a boot device
|
| enabled |
1 |
Indicates the SCSI LUN has been configured as a boot device
in the boot policy.
|
| DEFAULT |
disabled(0) |
Indicates the SCSI LUN is not configured as a boot device
|
|
childAction
Type: mo:ModificationChildAction
Primitive Type: scalar:Bitmask32
Units: null
Encrypted: false
Access: implicit
Category: TopLevelChildAction
Property Validators:
Comments:
-
| |
| Constants |
| deleteAll |
16384u |
NO COMMENTS
|
| ignore |
4096u |
NO COMMENTS
|
| deleteNonPresent |
8192u |
NO COMMENTS
|
| DEFAULT |
0 |
This type is used to
|
|
configQualifier
Type: lstorage:ConfigIssues
Primitive Type: scalar:Bitmask64
Units: null
Encrypted: false
Access: oper
Category: TopLevelRegular
Property Validators:
Comments:
-
Specifies the details of the configuration issues
| |
| Constants |
| not-applicable |
0ull |
NO COMMENTS
|
| identity-assignment |
128ull |
NO COMMENTS
|
| unsupported-storage-capability |
16ull |
NO COMMENTS
|
| lun-id-conflict |
1ull |
NO COMMENTS
|
| missing-firmware-image |
256ull |
NO COMMENTS
|
| lun-capacity-exceeded |
2ull |
NO COMMENTS
|
| insufficient-lun-resources |
32ull |
NO COMMENTS
|
| lun-limit-exceeded |
4ull |
NO COMMENTS
|
| lun-ownership-conflict |
64ull |
NO COMMENTS
|
| storage-unavailable |
8ull |
NO COMMENTS
|
| DEFAULT |
not-applicable(0ull) |
NO COMMENTS
|
|
configState
Type: lstorage:ConfigState
Primitive Type: scalar:Enum8
Units: null
Encrypted: false
Access: implicit
Category: TopLevelRegular
Property Validators:
Comments:
-
Specifies the configuration state of this storage item.
The value is set to "not-applied" when this Item belongs to a Storage Profile template.
| |
| Constants |
| ok |
0 |
NO COMMENTS
|
| applied |
1 |
NO COMMENTS
|
| failed-to-apply |
2 |
NO COMMENTS
|
| applying |
3 |
NO COMMENTS
|
| DEFAULT |
ok(0) |
NO COMMENTS
|
|
deferredNaming
Type: scalar:Bool
Units: null
Encrypted: false
Access: admin
Category: TopLevelRegular
Property Validators:
Comments:
-
NO COMMENTS
| |
| Constants |
| yes |
true |
NO COMMENTS
|
| defaultValue |
false |
NO COMMENTS
|
|
dn
Type: reference:Object
Units: null
Encrypted: false
Access: implicit
Category: TopLevelDn
Property Validators:
Comments:
-
The Distinguished Name (dn) unambiguously identifies an object in the system.
The dn provides a fully qualified path from the top of the object tree, all the way to
the object. It is built as a sequence of relative names separated by the "/"
character.
For example:
< ... dn = "sys/chassis-5/blade-2/adaptor-1" />
expandToAvail
Type: scalar:Bool
Units: null
Encrypted: false
Access: admin
Category: TopLevelRegular
Property Validators:
Comments:
-
Indicates this LUN should use up any additional space available in local storage
| |
| Constants |
| yes |
true |
NO COMMENTS
|
| no |
false |
NO COMMENTS
|
|
fractionalSize
Type: storage:Size
Primitive Type: scalar:Uint64
Units: null
Encrypted: false
Access: admin
Category: TopLevelRegular
Property Validators:
Range: min: 0 max: 1023
Comments:
-
The fractionalSize, in MB, is additional size which is logically added
to the size. This is for users who desire greater precision. For example,
if you want 1.5GB, you would specify a size of 1 and fractionalSize of 512.
By default, this property is 0, so for users who only care about integral
values of GB, this property can be safely ignored.
| |
| Constants |
| defaultValue |
0ull |
NO COMMENTS
|
|
localDiskPolicyName
Type: naming:Name
Primitive Type: string:Basic
Units: null
Encrypted: false
Access: admin
Category: TopLevelRegular
Policy Reference to: lstorage:DiskGroupConfigPolicy
Property Validators:
Range: min: "0" max: "16"
Allowed Chars:
Regex: [a-zA-Z0-9_.:-]+
Comments:
-
Name reference to the local disk configuration policy specifying
configuration of local storage. Note that local disk policy can
also be contained by the profile definition, in which case local
definition is always checked first and then, if not found, hierarchical
resolution by name is performed.
lunDn
Type: reference:Object
Units: null
Encrypted: false
Access: implicit
Category: TopLevelRegular
Property Validators:
Comments:
-
An object reference to the configured LUN.
This property is empty until the LUN is actually configured in the storage sub-system.
This property is not set when the containing lstorage:Profile is a template.
lunMapType
Type: lstorage:LunMapType
Primitive Type: scalar:Enum8
Units: null
Encrypted: false
Access: admin
Category: TopLevelRegular
Property Validators:
Comments:
-
The type of OS that will use this storage item.
The system may optimize the LUN to get better better performance for a particular
operating system. For example, this can be done by adjusting the block alignment
on physical disk to be optimized for a particular file system.
Specifies whether this LUN can be accessed by a single initiator
or can be shared amongst multiple initiators.
When the user defines a storage profile templates, multiple ls:Server MOs
can use the same storage profile template. In that case, each server will get
an instantiated storage profile.
If the storage profile template includes a "shared" lstorage:ScsiLun,
the LUN will be shared among all ls:Server using the template.
If the storage profile template includes a "non-shared" lstorage:ScsiLun,
a new LUN will be created for each ls:Server.
For direct attach storage LUNs, sharing a LUN is possible with the possible constraints:
At most two servers can share a LUN
Both servers must be connected through a JBOD enclosure.
The JBOD enclosure must have dual-port SAS disks
With non-HA SCSI controllers, the SAS disks must be configured in JBOD mode
(no RAID configuration). HA SCSI controllers may suppport shared LUNs with RAID
configuration.
| |
| Constants |
| non-shared |
0 |
Specifies the SCSI LUN can be accessed by a single initiator.
The system configures the storage such that at most one initiator can access the LUN.
For example, this could be implemented using FC zoning, FC LUN masking and/or iSCSI initiator groups.
|
| shared |
1 |
Specifies the SCSI LUN can be accessed by multiple initiators.
The system configures the storage such that multiple initiators can access the same LUN.
The topology and/or protocols may restrict which SCSI LUNs can be shared. For example, it is
not possible to share a LUN configured over a local SATA disk since the disk has physical
connectivity to a single server.
SAS disks may be shared by at most two servers.
|
| unassigned |
2 |
NO COMMENTS
|
| DEFAULT |
non-shared(0) |
Specifies the SCSI LUN can be accessed by a single initiator.
The system configures the storage such that at most one initiator can access the LUN.
For example, this could be implemented using FC zoning, FC LUN masking and/or iSCSI initiator groups.
|
|
name
Type: naming:Name
Primitive Type: string:Basic
Overrides:lstorage:Item:name
Units: null
Encrypted: false
Naming Property -- [NAMING RULES]
Access: naming
Category: TopLevelRegular
Property Validators:
Range: min: "1" max: "10"
Allowed Chars:
Regex: [a-zA-Z0-9_.:-]+
Comments:
-
Lun name cannot be changed
operLocalDiskPolicyName
Type: reference:Object
Refers: lstorage:DiskGroupConfigPolicy
Units: null
Encrypted: false
Access: oper
Category: TopLevelRegular
Property Validators:
Comments:
-
NO COMMENTS
operState
Type: storage:UnitOperState
Primitive Type: scalar:Enum8
Units: null
Encrypted: false
Access: implicit
Category: TopLevelRegular
Property Validators:
Comments:
-
Specifies the operational state of this storage item. The value is synchronized with
the corresponding item on storage side after the item is deployed on storage system.
| |
| Constants |
| undefined |
0 |
NO COMMENTS
|
| online |
1 |
NO COMMENTS
|
| offline |
2 |
NO COMMENTS
|
| compute-inoperable |
4 |
Block Boot & Install
|
| compute-degraded |
5 |
Allow Boot, Block Install
|
| DEFAULT |
undefined(0) |
NO COMMENTS
|
|
order
Type: lstorage:Order
Primitive Type: scalar:Uint16
Units: null
Encrypted: false
Access: admin
Category: TopLevelRegular
Property Validators:
Range: min: 0 max: 64
Comments:
-
NO COMMENTS
| |
| Constants |
| not-applicable |
0 |
NO COMMENTS
|
| DEFAULT |
not-applicable(0) |
NO COMMENTS
|
|
rn
Type: reference:RN
Units: null
Encrypted: false
Access: implicit
Category: TopLevelRn
Property Validators:
Comments:
-
The Relative Name (rn) uniquely identifies an object within a given context.
Note that a dn is comprised of a sequence of relative names. For example,
the context "sys/chassis-1/blade-1/adaptor-1/host-eth-2" can be thought
of as the following expression:
dn = <root object>/{rn}/{rn}/{rn}/{rn}/{rn}.
The rn can then be used to identify the object (for instance, "adaptor-1")
within the context:
<... rn ="../" />
sacl
Type: mo:InstSaclType
Primitive Type: scalar:Bitmask8
Units: null
Encrypted: false
Access: implicit
Category: TopLevelSacl
Property Validators:
Comments:
-
The system acl property for each Managed Object. br/>
This property is a 8 bit mask and supports the following values :-
a: del
b: mod
c: addchild
d: cascade
By default all Managed Objects have the following permissions
a: del
b: mod
c: addchild
This property is persisted in the db. If this property has a value none
it means, the user has read only permissions on this object.
| |
| Constants |
| none |
0 |
NO COMMENTS
|
| del |
1 |
NO COMMENTS
|
| mod |
2 |
NO COMMENTS
|
| addchild |
4 |
NO COMMENTS
|
| cascade |
8 |
NO COMMENTS
|
| DEFAULT |
0 |
NO COMMENTS
|
|
size
Type: storage:Size
Primitive Type: scalar:Uint64
Overrides:lstorage:ScsiLun:size
Units: null
Encrypted: false
Access: admin
Category: TopLevelRegular
Property Validators:
Range: min: 0 max: 245760
Comments:
-
NO COMMENTS
| |
| Constants |
| unspecified |
0ull |
NO COMMENTS
|
| defaultValue |
1ull |
NO COMMENTS
|
|
status
Type: mo:ModificationStatus
Primitive Type: scalar:Bitmask32
Units: null
Encrypted: false
Access: implicit
Category: TopLevelStatus
Property Validators:
Comments:
-
This property controls the life cycle of a managed object
| |
| Constants |
| removed |
16u |
In a setter method: specifies that an object should be removed.
In the return value of a setter method: indicates that an object has been removed.
|
| created |
2u |
In a setter method: specifies that an object should be created.
An error is returned if the object already exists.
In the return value of a setter method: indicates that an object has been created.
|
| modified |
4u |
In a setter method: specifies that an object should be modified
In the return value of a setter method: indicates that an object has been modified.
|
| deleted |
8u |
In a setter method: specifies that an object should be deleted.
In the return value of a setter method: indicates that an object has been deleted.
|
| DEFAULT |
0 |
This type controls the life cycle of objects passed in the XML API.
When used in a setter method (such as configConfMo), the ModificationStatus
specifies whether an object should be created, modified, deleted or removed.
In the return value of a setter method, the ModificationStatus indicates the actual
operation that was performed. For example, the ModificationStatus is set to "created"
if the object was created. The ModificationStatus is not set if the object was neither
created, modified, deleted or removed.
When invoking a setter method, the ModificationStatus is optional:
If a setter method such as configConfMo is invoked and the ModificationStatus
is not set, the system automatically determines if the object should be created or modified.
|
|
storageClass
Type: lstorage:StorageClass
Primitive Type: scalar:Enum8
Overrides:lstorage:ScsiLun:storageClass
Units: null
Encrypted: false
Access: implicit
Category: TopLevelRegular
Property Validators:
Comments:
-
NO COMMENTS
| |
| Constants |
| san |
1 |
Specifies the SCSI LUN must be configured over a Storage Area Network,
such as a FC, FCoE or iSCSI capable storage array.
The initiator must have an adapter that supports remote access to the SCSI LUN.
|
| das |
2 |
Specifies the SCSI LUN should be configured locally over Direct Attach Storage.
For example, the LUN might be configured using a SCSI controller, over local SAS HDD
or SSD drives in a rack server, or in a SAS-connected JBOD enclosure.
|
| DEFAULT |
das(2) |
Specifies the SCSI LUN should be configured locally over Direct Attach Storage.
For example, the LUN might be configured using a SCSI controller, over local SAS HDD
or SSD drives in a rack server, or in a SAS-connected JBOD enclosure.
|
|