Class capability:Def (ABSTRACT)

Class ID:515
Encrypted: false - Exportable: false - Persistent: false
Privileges: []
SNMP OID:

NO COMMENTS


Naming Rules


DN FORMAT: 

                




Inheritance
naming:NamedObject
 ├
policy:Object
 
 ├
policy:Definition
 
 
 ├
capability:Def
 
 
 
 ├
compute:ConstraintDef equipment constraints on blades
 
 
 
 ├
compute:MemoryUnitConstraintDef DIMM constraints on blades.
 
 
 
 ├
compute:PciSlotScanDef
 
 
 
 ├
equipment:AdaptorConnDef Adaptor ort Conn defines the end points (ports) on the adaptor and IOM sides.
 
 
 
 ├
equipment:AdaptorDef I/O adaptor properties such as maximum speeds.
 
 
 
 ├
equipment:AdvancedBootOrder
 
 
 
 ├
equipment:BeaconCapProvider
 
 
 
 ├
equipment:BiosDef Added for bios update for romley platforms
 
 
 
 ├
equipment:BiosTokenOverride Added to check if Option ROM is enabled
 
 
 
 ├
equipment:BladeAGLibrary
 
 
 
 ├
equipment:BladeConnDef Blade Connectivity defines the connectivity between the adaptor and the IOM/FEX.
 
 
 
 ├
equipment:BladeIOMConnDef
 
 
 
 ├
equipment:BladeSwitchConnDef
 
 
 
 ├
equipment:BoardControllerDef
 
 
 
 ├
equipment:BootDeviceConstraints
 
 
 
 ├
equipment:BreakoutCap
 
 
 
 ├
equipment:CimcVmedia
 
 
 
 ├
equipment:CiscoOsOpenGate
 
 
 
 ├
equipment:DiagFeatureSupport Added for E2E feature in delnorte
 
 
 
 ├
equipment:DimmMapping Holder for smbios dimm mapping DIMM's are identified in UCSM by a unique id. A mapping is needed between the locator in the SMBIOS table and the UCSM.
 
 
 
 ├
equipment:EmbeddedControllerConfig The embedded controller (PCH) on the server board can operate in SW-RAID and AHCI modes. This configuration is deployed through BIOS tokens. When the user selects the controller mode through ControllerDef, UCSM sets the bios-tokens to change the mode of the controller. This MO captures the token and its configurations to be applied by UCSM for the server
 
 
 
 ├
equipment:EmbeddedStorageDef catalog for storing disk properties of NVMe SSDs - required for supporting hot plug and HHHL form factor
 
 
 
 ├
equipment:FanModuleDef fan module capabilities
 
 
 
 ├
equipment:FanPresenceDef
 
 
 
 ├
equipment:FlashLife
 
 
 
 ├
equipment:FlexFlashNonRemovable
 
 
 
 ├
equipment:GemPortCap
 
 
 
 ├
equipment:HDDFaultMonDef
 
 
 
 ├
equipment:IOCardTypeDef IOCard Type Def
 
 
 
 ├
equipment:LocalDiskControllerDef
 
 
 
 ├
equipment:LocalDiskDef local disk unit properties
 
 
 
 ├
equipment:ManufacturingDef Manufacturing-related properties such as PID and SKU.
 
 
 
 ├
equipment:MemoryUnitDiscoveryModifierDef Rules for modifying DIMM discovery
 
 
 
 ├
equipment:NonCopperPassiveCap
 
 
 
 ├
equipment:NvmeDef Capability catalogue to specify the slot ID from which NVMe HHHL can start(Total number of NVMe disk slots plus 1). This is required to prevent conflict of ID between NVMe SFF and NVMe HHHL
 
 
 
 ├
equipment:NvmeSwitchConfig
 
 
 
 ├
equipment:OnboardDeviceDef
 
 
 
 ├
equipment:PciDef
 
 
 
 ├
equipment:PciSlotIdMapping Holder for pci slot name to id mapping
 
 
 
 ├
equipment:PfcMmuCap
 
 
 
 ├
equipment:PhysicalDef Physical properties such as maximum temperature and removal conditions.
 
 
 
 ├
equipment:PnuosBootMode
 
 
 
 ├
equipment:PortCap This defines capability of an aggregate-port. Aggregate Port can be divided into a number of Break-Out ports using a break-out cable.
 
 
 
 ├
equipment:PortGroupAggregationDef FEX/IOCARD portgroup aggregation properties
 
 
 
 ├
equipment:PortGroupDef FEX/IOCARD portgroup properties
 
 
 
 ├
equipment:PortGroupSwComplexDef FABRIC-INTERCONNECT PORT SWITCHING COMPLEX (ASIC) MAPPING DEFINITION
 
 
 
 ├
equipment:PortSwComplexRef
 
 
 
 ├
equipment:ProcessorUnitDef processor unit properties such as maximum clock rate.
 
 
 
 ├
equipment:PsuDef Psu capabilities
 
 
 
 ├
equipment:RackFanModuleDef Fan instances per fan module
 
 
 
 ├
equipment:RaidDef
 
 
 
 ├
equipment:SecureBoot
 
 
 
 ├
equipment:ServerPortCapProvider
 
 
 
 ├
equipment:ServiceDef Service properties such as removal conditions and slot array descriptor name.
 
 
 
 ├
equipment:SlotArray A Slot Array has sufficient properties to render a reasonable sketch of the chassis.
 
 
 
 ├
equipment:SlotArrayRef Reference from a FRU to a Slot Array. Also defines the slot span of the FRU.
 
 
 
 ├
equipment:SpeedCompatibility
 
 
 
 ├
equipment:StorageControllerConfig
 
 
 
 ├
equipment:StorageNvmeSwitchDef
 
 
 
 ├
equipment:StorageSasExpanderDef
 
 
 
 ├
equipment:SwitchCap Represents a Switch entry in the catalogue
 
 
 
 ├
equipment:SwitchTypeDef
 
 
 
 ├
equipment:UnifiedPortCapProvider

Events
                



Faults
                



Fsms
                



Properties Summary
Defined in: capability:Def
naming:Name
          string:Basic
name  (capability:Def:name)
           Overrides:policy:Object:name | naming:NamedObject:name
           NO COMMENTS
Defined in: policy:Definition
naming:Descr
          string:Basic
descr  (policy:Definition:descr)
           NO COMMENTS
policy:InternalId
          scalar:Uint32
intId  (policy:Definition:intId)
           NO COMMENTS
scalar:Uint32 policyLevel  (policy:Definition:policyLevel)
           policyLevel is used internally by generic policy server.
policy:PolicyOwner
          scalar:Enum8
policyOwner  (policy:Definition:policyOwner)
           "local" denotes policy created by local policy client, "policy" denotes a policy created by remote policy server.
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

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

descr

Type: naming:Descr
Primitive Type: string:Basic
Like: naming:Described:descr
Units: null
Encrypted: false
Access: admin
Category: TopLevelRegular
Property Validators:
    Range:  min: "0"  max: "256"
        Allowed Chars:
            Regex: [a-zA-Z0-9\[\]!#$%()*+,-./:;@ _{|}˜?&]+
Comments:
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" />

intId

Type: policy:InternalId
Primitive Type: scalar:Uint32
Units: null
Encrypted: false
Access: implicit
Category: TopLevelRegular
Property Validators:
Comments:
NO COMMENTS
Constants
none 0u NO COMMENTS
DEFAULT none(0u) NO COMMENTS

name

Type: naming:Name
Primitive Type: string:Basic
Overrides:policy:Object:name  |  naming:NamedObject:name
Units: null
Encrypted: false
Access: admin
Category: TopLevelRegular
Property Validators:
    Range:  min: "0"  max: "16"
        Allowed Chars:
            Regex: [a-zA-Z0-9_.:-]+
Comments:
NO COMMENTS

policyLevel

Type: scalar:Uint32
Units: null
Encrypted: false
Access: implicit
Category: TopLevelRegular
Property Validators:
Comments:
policyLevel is used internally by generic policy server.

policyOwner

Type: policy:PolicyOwner
Primitive Type: scalar:Enum8
Units: null
Encrypted: false
Access: admin
Category: TopLevelRegular
Property Validators:
Comments:
"local" denotes policy created by local policy client, "policy" denotes a policy created by remote policy server.
Constants
local 0 NO COMMENTS
policy 1 NO COMMENTS
pending-policy 2 NO COMMENTS
DEFAULT local(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.