Overview  Containers  Contained  Inheritance  Events  Faults  FSMs  Properties Summary  Properties Detail  Naming 

Class equipment:ChassisIssues (CONCRETE)

Class ID:2390
Encrypted: false - Exportable: false - Persistent: true
Privileges: [admin, pn-equipment, pn-maintenance, pn-policy]
SNMP OID: .1.3.6.1.4.1.9.9.719.1.40.28

Configuration Issues on the Chassis Profile. This is a singleton object implicitly populated to proactively show configuration issues/missing/invalid configurations in the given chassis profile, under the following scenarios:- a: Chassis profile association b: template association Users should use this object for all configuration issues going forward.

Naming Rules 
RN FORMAT: config-issue

    [1] PREFIX=config-issue


DN FORMAT: 

[0] org-[name]/cp-tier-[name]/cp-[name]/config-issue

[1] org-[name]/cp-[name]/config-issue


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:ChassisIssues
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:ChassisIssues


Contained Hierarchy
equipment:ChassisIssues
 ├
 		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
equipment:ChassisIssues
Events


Faults


Fsms


Properties Summary
Defined in: equipment:ChassisIssues
equipment:ChassisConfigIssues
          scalar:Bitmask64 		chassisConfigIssues  (equipment:ChassisIssues:chassisConfigIssues)
           Chassis Configuration Issues including the insufficient-resource bit
equipment:ConfigWarnings
          scalar:Bitmask64 		configWarnings  (equipment:ChassisIssues:configWarnings)
           Issues not resulting in configuration failure : Warnings
mo:PropAclMask
          scalar:Uint64 		propAcl  (equipment:ChassisIssues:propAcl)
           NO COMMENTS
storage:ConfigIssues
          scalar:Bitmask64 		storageConfigIssues  (equipment:ChassisIssues:storageConfigIssues)
           Storage Configuration Issues including the insufficient-resource bit
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

chassisConfigIssues

Type: equipment:ChassisConfigIssues
Primitive Type: scalar:Bitmask64
Units: null
Encrypted: false
Access: oper
Category: TopLevelRegular
Property Validators:

Comments:
Chassis Configuration Issues including the insufficient-resource bit
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

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

configWarnings

Type: equipment:ConfigWarnings
Primitive Type: scalar:Bitmask64
Units: null
Encrypted: false
Access: oper
Category: TopLevelRegular
Property Validators:

Comments:
Issues not resulting in configuration failure : Warnings
Constants
not-applicable 0ull NO COMMENTS
DEFAULT not-applicable(0ull) 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" />

propAcl

Type: mo:PropAclMask
Primitive Type: scalar:Uint64
Units: null
Encrypted: false
Access: implicit
Category: TopLevelRegular
Property Validators:

Comments:
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.

storageConfigIssues

Type: storage:ConfigIssues
Primitive Type: scalar:Bitmask64
Units: null
Encrypted: false
Access: oper
Category: TopLevelRegular
Property Validators:

Comments:
Storage Configuration Issues including the insufficient-resource bit
Constants
not-applicable 0ull NO COMMENTS
incomplete-drive-security-config 0x100000ull NO COMMENTS
cimc-mgmt-not-configured 0x10000ull NO COMMENTS
multiple-security-policies 0x20000ull NO COMMENTS
sed-unsupported-server 0x40000ull NO COMMENTS
jbod-disk-used-for-luns 0x4000ull NO COMMENTS
no-deployed-key 0x80000ull NO COMMENTS
bmc-certs-absent 0x8000ull NO COMMENTS
flexflash-metadata 1024ull NO COMMENTS
unsupported-disk-controller-config 1073741824ull NO COMMENTS
unsupported-expand-to-available 1099511627776ull NO COMMENTS
unsupported-use-remaining-disks 1125899906842624ull NO COMMENTS
unsupported-strip-size-change 1152921504606846976ull NO COMMENTS
zone-capacity 128ull NO COMMENTS
duplicated-lun-name 134217728ull NO COMMENTS
unsupported-hotspare-change 137438953472ull NO COMMENTS
unsupported-vd-modification 140737488355328ull NO COMMENTS
invalid-disk-slot-ownership 144115188075855872ull NO COMMENTS
disk-role-mismatch 16777216ull NO COMMENTS
missing-raid-key 16ull NO COMMENTS
orphaned-lun-ref-missing 17179869184ull NO COMMENTS
virtual-drive-access-denied 17592186044416ull NO COMMENTS
unsupported-disk-slot-zoning 18014398509481984ull NO COMMENTS
destructive-local-disk-config 1ull NO COMMENTS
storage-feature-capability-mismatch 2048ull NO COMMENTS
insufficient-disks 2097152ull Local Storage Config Issues
conflicting-lun-config 2147483648ull NO COMMENTS
unsupported-global-hotspares 2199023255552ull NO COMMENTS
drive-cache-not-supported 2251799813685248ull NO COMMENTS
unsupported-chassis-disk-zoning 2305843009213693952ull NO COMMENTS
flexflash-controller 256ull NO COMMENTS
unsupported-controller 268435456ull NO COMMENTS
invalid-storage-profile-binding 274877906944ull NO COMMENTS
lun-in-use 281474976710656ull NO COMMENTS
disk-sharing-not-supported 288230376151711744ull NO COMMENTS
incompatible-disk-types 2ull NO COMMENTS
storage-path-configuration-error 32ull NO COMMENTS
disk-type-mismatch 33554432ull NO COMMENTS
orphaned-lun-ref-access-denied 34359738368ull NO COMMENTS
virtual-drive-deletion-in-progress 35184372088832ull NO COMMENTS
unsupported-partial-disk-group-zoning 36028797018963968ull NO COMMENTS
virtual-drive-hidden-or-transport-ready 4096ull NO COMMENTS
unsupported-raid-level 4194304ull (use above)
incomplete-lun-config 4294967296ull NO COMMENTS
unsupported-order 4398046511104ull NO COMMENTS
embedded-controller-not-supported 4503599627370496ull NO COMMENTS
unsupported-security-operation 4611686018427387904ull NO COMMENTS
incompatible-number-of-local-disks 4ull NO COMMENTS
flexflash-card 512ull NO COMMENTS
unsupported-destructive-change 536870912ull NO COMMENTS
invalid-local-lun-disk-policy-reference 549755813888ull NO COMMENTS
set-proper-order 562949953421312ull NO COMMENTS
unsupported-chassis-spare-controller 576460752303423488ull NO COMMENTS
wwnn-assignment 64ull NO COMMENTS
unsupported-orphan-lun-modification 67108864ull NO COMMENTS
unsupported-lun-map-modification 68719476736ull NO COMMENTS
unsupported-write-cache-policy 70368744177664ull NO COMMENTS
invalid-zoning-virtual-drive-state 72057594037927936ull NO COMMENTS
invalid-zoning-disk-bootable 8192ull NO COMMENTS
insufficient-storage-space 8388608ull NO COMMENTS
order-should-be-unique 8589934592ull NO COMMENTS
virtual-drive-capacity 8796093022208ull NO COMMENTS
incompatible-raid-level 8ull NO COMMENTS
invalid-dzp-reference 9007199254740992ull Disk Zoning Config Issues
DEFAULT not-applicable(0ull) NO COMMENTS
Overview  Containers  Contained  Inheritance  Events  Faults  FSMs  Properties Summary  Properties Detail  Naming