Class capability:Item (ABSTRACT)

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

NO COMMENTS


Naming Rules


DN FORMAT: 

                




Inheritance
capability:Item
 ├
compute:QualItem
 
 ├
adaptor:CapDef Object representing a single adaptor unit capability. This object has a capability qualifier - type that describes what capability is represented. In addition qualitative properties of this capability are represented via maximum and available indicators.
 
 
 ├
adaptor:CapQual
 
 
 ├
adaptor:CapSpec
 
 
 ├
adaptor:RnicCapSpec
 
 ├
adaptor:DynamicConfigCap
 
 ├
adaptor:Qual
 
 ├
compute:BladePosQual
 
 
 ├
compute:ChassisQual
 
 
 ├
compute:InstanceIdQual
 
 
 ├
compute:SlotQual
 
 ├
compute:PhysicalQual
 
 ├
compute:RackPosQual
 
 
 ├
compute:RackQual
 
 ├
memory:Qual
 
 ├
power:GroupQual Server Pooling Policy Qualification to select a Power Group. Indicates that server belonging to a powergroup are added automatically
 
 ├
processor:Qual
 
 ├
storage:Qual
 ├
equipment:BehCap
 
 ├
adaptor:BehCap
 
 
 ├
adaptor:DiagCap
 
 
 ├
adaptor:HostPortCap
 
 
 ├
adaptor:HwAddrCap
 
 
 
 ├
adaptor:HostVnicHwAddrCap Encapsulate offsets of MAC addresses that can be used for implicit vNIC configuration. The offset range should not conflict with other MAC address offsets specified in subclasses of {@link adaptor:HwAddrCap}.
 
 
 
 ├
adaptor:HostethHwAddrCap
 
 
 
 ├
adaptor:HostfcHwAddrCap
 
 
 
 ├
adaptor:IScsiCap
 
 
 
 ├
adaptor:UplinkHwAddrCap
 
 
 ├
adaptor:LanCap
 
 
 ├
adaptor:LldpCap 1. NETWORK LAN CONFIGURATION OPTIONS: a. how to interpret default vlan: - default vlan is a native vlan - tagging handled @ switch (Oplin) - default vlan is a default vlan - tagging handled @ adaptor (Menlo, Palo) b. Network Management Mode - is this adaptor fully manageable from network (Palo) - is this adaptor partially manag...
 
 
 ├
adaptor:MgmtCap
 
 
 
 ├
adaptor:HostMgmtCap
 
 
 
 ├
adaptor:NwMgmtCap
 
 
 
 ├
adaptor:NwStatsMgmtCap
 
 
 ├
adaptor:SanCap
 
 ├
compute:BehCap
 
 
 ├
compute:PciCap
 
 
 ├
compute:ServerTypeCap Specifies if this server is general purpose and can be assigned to a user-created service profile, or if it is a special purpose server (such as storage appliance).
 
 ├
equipment:DiscoveryCap
 
 ├
equipment:DriveSecCap Added for SED mgmt on CIMC
 
 ├
equipment:HxCap Added for HX specific capabilities
 
 ├
equipment:InbandMgmtCap Added for inband mgmt of CIMC
 
 ├
equipment:KvmMgmtCap Added for Kvm mgmt of CIMC
 
 ├
equipment:MgmtControllerCap Describes a capability of a management controller. A management controller is an entity that can be used for management operations.
 
 
 ├
equipment:HostMgmtControllerCap The host management controller capability describes the management controller that can be run on the host. For example: PNUOS. This capability describes the preferred method of instantiating this controller.
 
 ├
equipment:StorageLimitCap Added for Storage Controller Limits
 ├
equipment:HwRevisionModifier
 ├
equipment:Picture
 ├
equipment:QualItem
 
 ├
equipment:ChassisPosQual
 
 
 ├
equipment:ChassisQual
 
 ├
equipment:PhysicalQual Adarsh TODO Define the proper access policies
 ├
equipment:ServerFeatureCap Capability that indicates if a feature is supported/unsupported on a server.
 ├
equipment:StorageControllerSlotDef Defines the supported slots for storage controllers in rack servers. Servers without these catalog entries are indeterminite with regard to multi-controller support and require hard coding to determine this.
 ├
equipment:UuidFeatureCap
 ├
firmware:AChassisConstraint Specifies the min CMC version that is required to support the feature.
 
 ├
firmware:ConnectionManagementChassisConstraint Specifies the min CMC version that is required to support Connection Management feature of SAS Expander for Colusa Server.
 
 ├
firmware:DualVicChassisConstraint Specifies the min CMC version that is required to support single server dual vic feature.
 
 ├
firmware:SecondControllerChassisConstraint Specifies the min CMC version that is required to support Second Controller for Colusa Server.
 
 ├
firmware:ServerChassisConstraint Specifies the min CMC version that is required to support waterford Server.
 
 ├
firmware:SinglePathChassisConstraint Specifies the min CMC version that is required to support Single Path for Colusa Server.
 ├
firmware:AConstraint Specifies the min BIOS and CIMC versions that are required to support the feature.
 
 ├
firmware:DriveSecurityConstraint Specifies the min CIMC versions that are required to support Drive Security
 
 ├
firmware:DualVicServerConstraint Specifies the min BIOS and CIMC versions that are required to support Single Server Dual VIC feature for Colusa Chassis.
 
 ├
firmware:PCHStorageConfigConstraint Specifies the min BIOS versions that are required to support the Controller definition on PCH controller.
 
 ├
firmware:ProcessorTypeConstraint Specifies the min BIOS and CIMC versions that are required to support the CPU installed on the server.
 
 ├
firmware:RackPowerCapConstraint
 
 ├
firmware:SecondControllerServerConstraint Specifies the min BIOS and CIMC versions that are required to support Second Controller for Colusa Server.
 
 ├
firmware:ServerTypeConstraint Specifies the min BIOS and CIMC versions that are required to support the type of server(this was added to prevent cimc/bios downgrade of DN NEBS to a build below Granada).
 
 ├
firmware:TPMConstraint Specifies the min BIOS version required to support the server with TPM 02.
 
 ├
firmware:VicSlotConstraint
 
 ├
firmware:VnicCdnConstraint Specifies the min BIOS versions that are required to support the vnic cdn.
 
 ├
firmware:WaterbaySiocServerConstraint Specifies the min CIMC versions that is required to support Waterbay Sioc on a Colusa Chassis.
 ├
firmware:Constraints Holder for firmware downgrade constraints imposed on the FRU (rack/blade).
 ├
firmware:Dependency
 ├
firmware:Type identifies image type in the capability/type catalogue. Specifies that corresponding image types are applicable to a given FRU. This object also limits which versions apply to a FRU.
 ├
firmware:UpgradeConstraint Mo to define a firmware constraint for an upgrade operation
 ├
storage:EnclosureCap
 ├
storage:SasLinkDescriptor
 ├
storage:SasPortDescriptor

Events
                



Faults
                



Fsms
                



Properties Summary
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

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" />

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.