Class storage:EnclosureDiskSlotEp (CONCRETE)

Class ID:2093
Encrypted: false - Exportable: false - Persistent: true
Privileges: [read-only]
SNMP OID: .1.3.6.1.4.1.9.9.719.1.118.15

Indicates the disk slot in an enclosure. When the slot is populated, peerDn references the disk present. This is the same as the LocalDiskSlotEp mo. This mo was created because of a conflict between LocalDiskSlotEp and LocalDisk. Both have the same rn and therefore cannot be contained under the same container.


Naming Rules
RN FORMAT: disk-slot-[id]

    [1] PREFIX=disk-slot- PROPERTY = id




DN FORMAT: 

[0] sys/chassis-[id]/blade-[slotId]/enc-[id]/disk-slot-[id]

[1] sys/rack-unit-[id]/enc-[id]/disk-slot-[id]

[2] sys/chassis-[id]/cartridge-[slotId]/server-[serverInstanceId]/enc-[id]/disk-slot-[id]

[3] sys/chassis-[id]/enc-[id]/disk-slot-[id]

[4] sys/chassis-[id]/blade-[slotId]/board/storage-[type]-[id]/enc-[id]/disk-slot-[id]

[5] sys/rack-unit-[id]/board/storage-[type]-[id]/enc-[id]/disk-slot-[id]

[6] sys/chassis-[id]/cartridge-[slotId]/server-[serverInstanceId]/board/storage-[type]-[id]/enc-[id]/disk-slot-[id]

[7] sys/chassis-[id]/storage-[type]-[id]/enc-[id]/disk-slot-[id]

                



Containers Hierarchies
top:Root This class represents the root element in the object hierarchy. All managed objects in the system are descendants of the Root element.
 ├
top:System Provides general information about this system, such as the name, IP address and current time.
 
 ├
compute:RackUnit A physical compute RackUnit. Physical compute item representing a Rack mountable unit.
 
 
 ├
compute:Board Motherboard contained by physical compute item.
 
 
 
 ├
storage:Controller
 
 
 
 
 ├
storage:Enclosure
 
 
 
 
 
 ├
storage:EnclosureDiskSlotEp
top:Root This class represents the root element in the object hierarchy. All managed objects in the system are descendants of the Root element.
 ├
top:System Provides general information about this system, such as the name, IP address and current time.
 
 ├
compute:RackUnit A physical compute RackUnit. Physical compute item representing a Rack mountable unit.
 
 
 ├
storage:Enclosure
 
 
 
 ├
storage:EnclosureDiskSlotEp
top:Root This class represents the root element in the object hierarchy. All managed objects in the system are descendants of the Root element.
 ├
top:System Provides general information about this system, such as the name, IP address and current time.
 
 ├
equipment:Chassis A physical unit that can accomodate multiple blade servers. For example, the Cisco UCS 5108 Blade Server Chassis is six rack units (6RU) high, can mount in an industry-standard 19-inch rack and uses front-to-back cooling.
 
 
 ├
compute:Blade A physical compute blade. Physical compute item in blade form factor.
 
 
 
 ├
compute:Board Motherboard contained by physical compute item.
 
 
 
 
 ├
storage:Controller
 
 
 
 
 
 ├
storage:Enclosure
 
 
 
 
 
 
 ├
storage:EnclosureDiskSlotEp
top:Root This class represents the root element in the object hierarchy. All managed objects in the system are descendants of the Root element.
 ├
top:System Provides general information about this system, such as the name, IP address and current time.
 
 ├
equipment:Chassis A physical unit that can accomodate multiple blade servers. For example, the Cisco UCS 5108 Blade Server Chassis is six rack units (6RU) high, can mount in an industry-standard 19-inch rack and uses front-to-back cooling.
 
 
 ├
compute:Blade A physical compute blade. Physical compute item in blade form factor.
 
 
 
 ├
storage:Enclosure
 
 
 
 
 ├
storage:EnclosureDiskSlotEp
top:Root This class represents the root element in the object hierarchy. All managed objects in the system are descendants of the Root element.
 ├
top:System Provides general information about this system, such as the name, IP address and current time.
 
 ├
equipment:Chassis A physical unit that can accomodate multiple blade servers. For example, the Cisco UCS 5108 Blade Server Chassis is six rack units (6RU) high, can mount in an industry-standard 19-inch rack and uses front-to-back cooling.
 
 
 ├
compute:Cartridge A physical compute cartridge.
 
 
 
 ├
compute:ServerUnit A server instance on a cartridge.
 
 
 
 
 ├
compute:Board Motherboard contained by physical compute item.
 
 
 
 
 
 ├
storage:Controller
 
 
 
 
 
 
 ├
storage:Enclosure
 
 
 
 
 
 
 
 ├
storage:EnclosureDiskSlotEp
top:Root This class represents the root element in the object hierarchy. All managed objects in the system are descendants of the Root element.
 ├
top:System Provides general information about this system, such as the name, IP address and current time.
 
 ├
equipment:Chassis A physical unit that can accomodate multiple blade servers. For example, the Cisco UCS 5108 Blade Server Chassis is six rack units (6RU) high, can mount in an industry-standard 19-inch rack and uses front-to-back cooling.
 
 
 ├
compute:Cartridge A physical compute cartridge.
 
 
 
 ├
compute:ServerUnit A server instance on a cartridge.
 
 
 
 
 ├
storage:Enclosure
 
 
 
 
 
 ├
storage:EnclosureDiskSlotEp
top:Root This class represents the root element in the object hierarchy. All managed objects in the system are descendants of the Root element.
 ├
top:System Provides general information about this system, such as the name, IP address and current time.
 
 ├
equipment:Chassis A physical unit that can accomodate multiple blade servers. For example, the Cisco UCS 5108 Blade Server Chassis is six rack units (6RU) high, can mount in an industry-standard 19-inch rack and uses front-to-back cooling.
 
 
 ├
storage:Controller
 
 
 
 ├
storage:Enclosure
 
 
 
 
 ├
storage:EnclosureDiskSlotEp
top:Root This class represents the root element in the object hierarchy. All managed objects in the system are descendants of the Root element.
 ├
top:System Provides general information about this system, such as the name, IP address and current time.
 
 ├
equipment:Chassis A physical unit that can accomodate multiple blade servers. For example, the Cisco UCS 5108 Blade Server Chassis is six rack units (6RU) high, can mount in an industry-standard 19-inch rack and uses front-to-back cooling.
 
 
 ├
storage:Enclosure
 
 
 
 ├
storage:EnclosureDiskSlotEp


Contained Hierarchy
storage:EnclosureDiskSlotEp
 ├
fault:Inst An abnormal condition or defect at the component, equipment, or sub-system level which may lead to a failure, as defined in ISO/CD 10303-226.
 ├
storage:ControllerRef Represents ownership for server,controller combination

Inheritance
storage:EnclosureDiskSlotEp

Events
                



Faults
                storage:EnclosureDiskSlotEp:chassis-spare
storage:EnclosureDiskSlotEp:equipment-inoperable
storage:EnclosureDiskSlotEp:hddslot-server2-ownership-unassigned
storage:EnclosureDiskSlotEp:hotspare-unsupported
storage:EnclosureDiskSlotEp:ioe-ownership-unassigned
storage:EnclosureDiskSlotEp:missing
storage:EnclosureDiskSlotEp:second-controller-absent
storage:EnclosureDiskSlotEp:sharing-unsupported



Fsms
                



Properties Summary
Defined in: storage:EnclosureDiskSlotEp
storage:SlotAutoZoneCause
          scalar:Enum8
autoZoneCause  (storage:EnclosureDiskSlotEp:autoZoneCause)
           NO COMMENTS
storage:Configuration
          scalar:Enum8
configuration  (storage:EnclosureDiskSlotEp:configuration)
           NO COMMENTS
storage:DiskPath
          scalar:Enum8
drivePath  (storage:EnclosureDiskSlotEp:drivePath)
           NO COMMENTS
equipment:Id
          scalar:Uint32
id  (storage:EnclosureDiskSlotEp:id)
           NO COMMENTS
fsm:Lifecycle
          scalar:Enum8
lc  (storage:EnclosureDiskSlotEp:lc)
           NO COMMENTS
equipment:OperQualifierReason
          string:Basic
operQualifierReason  (storage:EnclosureDiskSlotEp:operQualifierReason)
           NO COMMENTS
equipment:Operability
          scalar:Enum8
operability  (storage:EnclosureDiskSlotEp:operability)
           NO COMMENTS
storage:Ownership
          scalar:Enum8
ownership  (storage:EnclosureDiskSlotEp:ownership)
           NO COMMENTS
reference:Object peerDn  (storage:EnclosureDiskSlotEp:peerDn)
           NO COMMENTS
equipment:Presence
          scalar:Enum8
presence  (storage:EnclosureDiskSlotEp:presence)
           NO COMMENTS
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

Properties Detail

autoZoneCause

Type: storage:SlotAutoZoneCause
Primitive Type: scalar:Enum8
Units: null
Encrypted: false
Access: implicit
Category: TopLevelRegular
Property Validators:
Comments:
NO COMMENTS
Constants
none 0 NO COMMENTS
sharing-unsupported 1 NO COMMENTS
hddslot-unassigned 2 NO COMMENTS
hotspare-unsupported 3 NO COMMENTS
hdd-tray-in-lieu-of-server2 4 HDD Expansion Tray is present in Slot 2 in lieu of Server
mezz-controller-in-ioexpander 5 IO Expander with Mezz Controller is present in lieu of Server in Slot 1
second-controller-absent 6 Second Controller(either DD rock or DD Raid or IOE) attached to a server in colusa chassis is absent
DEFAULT none(0) NO COMMENTS

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

configuration

Type: storage:Configuration
Primitive Type: scalar:Enum8
Units: null
Encrypted: false
Access: implicit
Category: TopLevelRegular
Property Validators:
Comments:
NO COMMENTS
Constants
unknown 0 NO COMMENTS
supported 1 NO COMMENTS
not-supported 2 NO COMMENTS
DEFAULT unknown(0) 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" />

drivePath

Type: storage:DiskPath
Primitive Type: scalar:Enum8
Units: null
Encrypted: false
Access: implicit
Category: TopLevelRegular
Property Validators:
Comments:
NO COMMENTS
Constants
UNKNOWN 0 NO COMMENTS
PATH-BOTH 1 NO COMMENTS
PATH-0 2 NO COMMENTS
PATH-1 3 NO COMMENTS
NONE 4 NO COMMENTS
DEFAULT UNKNOWN(0) NO COMMENTS

id

Type: equipment:Id
Primitive Type: scalar:Uint32
Units: null
Encrypted: false
Naming Property -- [NAMING RULES]
Access: naming
Category: TopLevelRegular
Property Validators:
Comments:
NO COMMENTS

lc

Type: fsm:Lifecycle
Primitive Type: scalar:Enum8
Units: null
Encrypted: false
Access: implicit
Category: TopLevelRegular
Property Validators:
Comments:
NO COMMENTS
Constants
available 0 NO COMMENTS
allocated 1 NO COMMENTS
deallocated 2 NO COMMENTS
repurposed 3 NO COMMENTS
DEFAULT available(0) NO COMMENTS

operQualifierReason

Type: equipment:OperQualifierReason
Primitive Type: string:Basic
Like: equipment:StatefulIf:operQualifierReason
Units: null
Encrypted: false
Access: implicit
Category: TopLevelRegular
Property Validators:
    Range:  min: "0"  max: "256"
        Allowed Chars:
            Regex: [a-zA-Z0-9\[\]!#$%()*+,-./:;@ _{|}˜?&]+
Comments:
NO COMMENTS
Constants
defaultValue "N/A" NO COMMENTS

operability

Type: equipment:Operability
Primitive Type: scalar:Enum8
Like: equipment:StatefulIf:operability
Units: null
Encrypted: false
Access: implicit
Category: TopLevelRegular
Property Validators:
Comments:
NO COMMENTS
Constants
unknown 0 NO COMMENTS
operable 1 NO COMMENTS
inoperable 2 NO COMMENTS
degraded 3 NO COMMENTS
powered-off 4 NO COMMENTS
power-problem 5 NO COMMENTS
removed 6 NO COMMENTS
voltage-problem 7 NO COMMENTS
thermal-problem 8 NO COMMENTS
performance-problem 9 NO COMMENTS
accessibility-problem 10 NO COMMENTS
identity-unestablishable 11 NO COMMENTS
bios-post-timeout 12 NO COMMENTS
disabled 13 NO COMMENTS
malformed-fru 14 NO COMMENTS
backplane-port-problem 15 NO COMMENTS
chassis-intrusion 16 NO COMMENTS
non-optimal 17 NO COMMENTS
unsupported-config 18 NO COMMENTS
fabric-conn-problem 51 NO COMMENTS
fabric-unsupported-conn 52 NO COMMENTS
config 81 NO COMMENTS
equipment-problem 82 NO COMMENTS
decomissioning 83 NO COMMENTS
chassis-limit-exceeded 84 NO COMMENTS
not-supported 100 NO COMMENTS
discovery 101 NO COMMENTS
discovery-failed 102 NO COMMENTS
identify 103 NO COMMENTS
post-failure 104 NO COMMENTS
upgrade-problem 105 NO COMMENTS
peer-comm-problem 106 NO COMMENTS
auto-upgrade 107 NO COMMENTS
link-activate-blocked 108 NO COMMENTS
DEFAULT unknown(0) NO COMMENTS

ownership

Type: storage:Ownership
Primitive Type: scalar:Enum8
Units: null
Encrypted: false
Access: implicit
Category: TopLevelRegular
Property Validators:
Comments:
NO COMMENTS
Constants
unknown 0 NO COMMENTS
unassigned 1 NO COMMENTS
dedicated 2 NO COMMENTS
shared 3 NO COMMENTS
chassis-global-spare 4 NO COMMENTS
chassis-dedicated-spare 5 NO COMMENTS
DEFAULT unknown(0) NO COMMENTS

peerDn

Type: reference:Object
Refers: storage:LocalDisk
Units: null
Encrypted: false
Access: implicit
Category: TopLevelRegular
Property Validators:
Comments:
NO COMMENTS

presence

Type: equipment:Presence
Primitive Type: scalar:Enum8
Like: equipment:StatefulIf:presence
Units: null
Encrypted: false
Access: oper
Category: TopLevelRegular
Property Validators:
Comments:
NO COMMENTS
Constants
unknown 0 NO COMMENTS
empty 1 NO COMMENTS
equipped 10 NO COMMENTS
missing 11 NO COMMENTS
mismatch 12 NO COMMENTS
equipped-not-primary 13 NO COMMENTS
equipped-slave 14 NO COMMENTS
mismatch-slave 15 NO COMMENTS
missing-slave 16 NO COMMENTS
equipped-identity-unestablishable 20 NO COMMENTS
mismatch-identity-unestablishable 21 NO COMMENTS
equipped-with-malformed-fru 22 NO COMMENTS
inaccessible 30 NO COMMENTS
unauthorized 40 NO COMMENTS
not-supported 100 NO COMMENTS
equipped-unsupported 101 NO COMMENTS
equipped-deprecated 102 NO COMMENTS
equipped-disc-not-started 102 NO COMMENTS
equipped-disc-in-progress 103 NO COMMENTS
equipped-disc-error 104 NO COMMENTS
equipped-disc-unknown 105 NO COMMENTS
DEFAULT unknown(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

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.