Class equipment:Requirement (CONCRETE)

Class ID:2393
Encrypted: false - Exportable: true - Persistent: true
Privileges: [admin, pn-equipment, pn-maintenance, pn-policy, read-only]
SNMP OID: .1.3.6.1.4.1.9.9.719.1.40.160

Represents a Binding between a ChassisProfile and a pool of Chassis The Requirements refers to a pool of chassis and a chassis qualification


Naming Rules
RN FORMAT: chassis-req

    [1] PREFIX=chassis-req


DN FORMAT: 

[0] org-[name]/cp-tier-[name]/cp-[name]/chassis-req

[1] org-[name]/cp-[name]/chassis-req

                



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.
 ├
org:Org
 
 ├
equipment:ChassisProfile Chassis Profile Definition. Holds and Regulates Specification of: identity connectivity applied to the chassis upon association. Chassis profile can serve the following purposes: associatable instance initialization template persistent binding template ...
 
 
 ├
equipment:Requirement
top:Root This class represents the root element in the object hierarchy. All managed objects in the system are descendants of the Root element.
 ├
org:Org
 
 ├
equipment:Tier Tier
 
 
 ├
equipment:ChassisProfile Chassis Profile Definition. Holds and Regulates Specification of: identity connectivity applied to the chassis upon association. Chassis profile can serve the following purposes: associatable instance initialization template persistent binding template ...
 
 
 
 ├
equipment:Requirement


Contained Hierarchy
equipment:Requirement
 ├
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.

Inheritance
naming:NamedObject
 ├
policy:Object
 
 ├
policy:Binding
 
 
 ├
equipment:ChassisProfileBinding Abstract Representation of a binding between a Chassis profile and chassis //TODO -> define access properly
 
 
 
 ├
equipment:Requirement

Events
                



Faults
                



Fsms
                



Properties Summary
Defined in: equipment:Requirement
reference:Object chassisPoolDn  (equipment:Requirement:chassisPoolDn)
           NO COMMENTS
naming:Name
          string:Basic
name  (equipment:Requirement:name)
           Overrides:policy:Object:name | naming:NamedObject:name
           NO COMMENTS
reference:Object operName  (equipment:Requirement:operName)
           NO COMMENTS
naming:Name
          string:Basic
qualifier  (equipment:Requirement:qualifier)
           NO COMMENTS
Defined in: equipment:ChassisProfileBinding
reference:Object assignedToDn  (equipment:ChassisProfileBinding:assignedToDn)
           NO COMMENTS
reference:Object chassisDn  (equipment:ChassisProfileBinding:chassisDn)
           NO COMMENTS
equipment:ChassisConfigIssues
          scalar:Bitmask64
issues  (equipment:ChassisProfileBinding:issues)
           NO COMMENTS
equipment:ChassisProfileBindingOperState
          scalar:Enum8
operState  (equipment:ChassisProfileBinding:operState)
           NO COMMENTS
scalar:Bool restrictMigration  (equipment:ChassisProfileBinding:restrictMigration)
           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

assignedToDn

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

chassisDn

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

chassisPoolDn

Type: reference:Object
Refers: equipment:Pool
Units: null
Encrypted: false
Access: implicit
Category: TopLevelRegular
Property Validators:
Comments:
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

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

issues

Type: equipment:ChassisConfigIssues
Primitive Type: scalar:Bitmask64
Units: null
Encrypted: false
Access: oper
Category: TopLevelRegular
Property Validators:
Comments:
NO COMMENTS
Constants
not-applicable 0ull Indicates there are no issues
chassis-profile-not-supported 1024ull NO COMMENTS
single-path-not-supported 1048576ull NO COMMENTS
invalid-cmc-version 1073741824ull NO COMMENTS
migration 128ull NO COMMENTS
single-path-unsupported-cmc-version 131072ull NO COMMENTS
single-path-operation-not-supported 134217728ull NO COMMENTS
firmware-version-mismatch 16384ull NO COMMENTS
invalid-sas-exp-config-policy-reference 16777216ull NO COMMENTS
non-interrupt-fsm-running 16ull NO COMMENTS
insufficient-resources 1ull overall there are not enough resources
compute-conn-invalid-hw-config 2048ull NO COMMENTS
connection-management-unsupported-cmc-version 2097152ull NO COMMENTS
physical-requirement 256ull NO COMMENTS
single-path-expander-inoperable 262144ull NO COMMENTS
connection-management-feature-not-supported 268435456ull NO COMMENTS
chassis-undiscovered 2ull Chassis is still not discovered
chassis-feature-capability-mismatch 32768ull NO COMMENTS
resource-ownership-conflict 32ull NO COMMENTS
unsupported-sas-exp-config-settings 33554432ull NO COMMENTS
compute-conn-unsupported-cmc-version 4096ull NO COMMENTS
connection-management-expander-inoperable 4194304ull NO COMMENTS
chassis-unavailable 4ull Chassis unavailable
invalid-chassis-pack 512ull NO COMMENTS
single-path-invalid-configuration 524288ull NO COMMENTS
connection-management-operation-not-supported 536870912ull NO COMMENTS
missing-firmware-image 64ull NO COMMENTS
chassis-feature-capability-mismatch-non-fatal 65536ull NO COMMENTS
single-path-feature-not-supported 67108864ull NO COMMENTS
compute-second-controller-unsupported-cmc-version 8192ull NO COMMENTS
connection-management-not-supported 8388608ull NO COMMENTS
insufficient-power-budget 8ull NO COMMENTS
DEFAULT not-applicable(0ull) Indicates there are no issues

name

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

operName

Type: reference:Object
Refers: equipment:Pool
Units: null
Encrypted: false
Access: oper
Category: TopLevelRegular
Property Validators:
Comments:
NO COMMENTS

operState

Type: equipment:ChassisProfileBindingOperState
Primitive Type: scalar:Enum8
Units: null
Encrypted: false
Access: oper
Category: TopLevelRegular
Property Validators:
Comments:
NO COMMENTS
Constants
unused 0 NO COMMENTS
used 1 NO COMMENTS
failed-to-apply 2 NO COMMENTS
DEFAULT unused(0) NO COMMENTS

qualifier

Type: naming:Name
Primitive Type: string:Basic
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

restrictMigration

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

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.