Class bios:Unit (CONCRETE)

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

NO COMMENTS


Naming Rules
RN FORMAT: bios

    [1] PREFIX=bios


DN FORMAT: 

[0] sys/chassis-[id]/blade-[slotId]/ext-board-[id]/bios

[1] sys/rack-unit-[id]/ext-board-[id]/bios

[2] sys/chassis-[id]/cartridge-[slotId]/server-[serverInstanceId]/ext-board-[id]/bios

[3] sys/chassis-[id]/blade-[slotId]/bios

[4] sys/rack-unit-[id]/bios

[5] sys/chassis-[id]/cartridge-[slotId]/server-[serverInstanceId]/bios

[6] sys/chassis-[id]/cartridge-[slotId]/server-[serverInstanceId]/bios

                



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.
 
 
 ├
bios:Unit
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:ExtBoard Added for aggregate boards. Extended Motherboard contained by physical compute item.
 
 
 
 ├
bios:Unit
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.
 
 
 
 ├
bios:Unit
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:ExtBoard Added for aggregate boards. Extended Motherboard contained by physical compute item.
 
 
 
 
 ├
bios:Unit
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.
 
 
 
 
 ├
bios:Unit
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:ExtBoard Added for aggregate boards. Extended Motherboard contained by physical compute item.
 
 
 
 
 
 ├
bios:Unit


Contained Hierarchy
bios:Unit
 ├
bios:BOT
 
 ├
bios:BootDevGrp
 
 
 ├
bios:BootDev
 ├
bios:Settings
 
 ├
bios:TokenFeatureGroup A feature may consists of one or more tokens. If there are are more than one token then they are related.
 
 
 ├
bios:TokenParam One param represnets one bios token
 
 
 
 ├
bios:TokenSettings Every possible value of a bios token is represented as a TokenSettingsMo
 
 ├
bios:TokenParam One param represnets one bios token
 
 
 ├
bios:TokenSettings Every possible value of a bios token is represented as a TokenSettingsMo
 
 ├
bios:VFeat
 ├
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.
 ├
firmware:BootDefinition Container for BootUnit objects. This is needed since some components (like switch) have more then one BootUnit objects.
 
 ├
firmware:BootUnit
 
 
 ├
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.
 
 
 ├
firmware:Installable Represents a logical image that can be installed on an end-point. Ech physical File can have one or more installables. This is to Support Model changes without any software change. Created implicitely as part of download operation.
 
 
 
 ├
firmware:UcscInfo
 
 
 ├
firmware:ServicePack Representation of firmware image version that is loaded at reboot. Applicable to all the components that supports one or more backup image(s).
 
 ├
firmware:UcscInfo
 ├
firmware:Running Representation of primary firmware image (Currently running)
 
 ├
firmware:ServicePack Representation of firmware image version that is loaded at reboot. Applicable to all the components that supports one or more backup image(s).
 ├
firmware:Updatable Representation of backup firmware image for the chassis components that supports backup image (CMC/BMC/BIOS/Adaptor etc)
 
 ├
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.
 
 ├
firmware:Installable Represents a logical image that can be installed on an end-point. Ech physical File can have one or more installables. This is to Support Model changes without any software change. Created implicitely as part of download operation.
 
 
 ├
firmware:UcscInfo

Inheritance
bios:Unit

Events
                



Faults
                bios:Unit:FD0FailedSecurityVerification



Fsms
                



Properties Summary
Defined in: bios:Unit
naming:Descr
          string:Basic
initSeq  (bios:Unit:initSeq)
           NO COMMENTS
scalar:Date initTs  (bios:Unit:initTs)
           NO COMMENTS
equipment:Model
          string:Basic
model  (bios:Unit:model)
           NO COMMENTS
equipment:Revision
          string:Basic
revision  (bios:Unit:revision)
           NO COMMENTS
equipment:Serial
          string:Basic
serial  (bios:Unit:serial)
           NO COMMENTS
equipment:Vendor
          string:Basic
vendor  (bios:Unit:vendor)
           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

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

initSeq

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

initTs

Type: scalar:Date
Units: null
Encrypted: false
Access: implicit
Category: TopLevelRegular
Property Validators:
Comments:
NO COMMENTS
Constants
never 0ull NO COMMENTS
DEFAULT never(0ull) NO COMMENTS

model

Type: equipment:Model
Primitive Type: string:Basic
Like: equipment:Info:model
Units: null
Encrypted: false
Access: implicit
Category: TopLevelRegular
Property Validators:
    Range:  min: "0"  max: "510"
Comments:
NO COMMENTS

revision

Type: equipment:Revision
Primitive Type: string:Basic
Like: equipment:Info:revision
Units: null
Encrypted: false
Access: implicit
Category: TopLevelRegular
Property Validators:
    Range:  min: "0"  max: "510"
Comments:
NO COMMENTS
Constants
defaultValue "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

serial

Type: equipment:Serial
Primitive Type: string:Basic
Like: equipment:Info:serial
Units: null
Encrypted: false
Access: implicit
Category: TopLevelRegular
Property Validators:
    Range:  min: "0"  max: "510"
Comments:
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.


vendor

Type: equipment:Vendor
Primitive Type: string:Basic
Like: equipment:Info:vendor
Units: null
Encrypted: false
Access: implicit
Category: TopLevelRegular
Property Validators:
    Range:  min: "0"  max: "510"
Comments:
NO COMMENTS