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

Class ls:Binding (CONCRETE)

Class ID:618
Encrypted: false - Exportable: true - Persistent: true
Privileges: [admin, ls-compute, ls-config, ls-config-policy, ls-server, ls-server-policy, read-only]
SNMP OID: .1.3.6.1.4.1.9.9.719.1.71.2

Represents a Binding between a ls:Server and a specified physical server. The API user explicitly bind a ls:Server to a physical server, which could be a blade in a specific slot, or a rack server.

Naming Rules 
RN FORMAT: pn

    [1] PREFIX=pn


DN FORMAT: 

[0] org-[name]/tier-[name]/ls-[name]/pn

[1] org-[name]/ls-[name]/pn


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
 
 		 ├
 		ls:Server Logical Server Definition. Holds and Regulates Specification of: identity connectivity applied to the physical compute node like compute:Blade upon association. Logical Server can serve the following purposes: associatable instance initialization template persistent ...
 
 		 
 		 ├
 		ls:Binding
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
 
 		 ├
 		ls:Tier Tier
 
 		 
 		 ├
 		ls:Server Logical Server Definition. Holds and Regulates Specification of: identity connectivity applied to the physical compute node like compute:Blade upon association. Logical Server can serve the following purposes: associatable instance initialization template persistent ...
 
 		 
 		 
 		 ├
 		ls:Binding


Contained Hierarchy
ls:Binding
 ├
 		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
 
 		 
 		 ├
 		ls:ComputeBinding Abstract Representation of a binding between a ls:Server and physical server.
 
 		 
 		 
 		 ├
 		ls:Binding
Events


Faults 
                ls:ComputeBinding:assignmentRequirementsNotMet


Fsms


Properties Summary
Defined in: ls:Binding
naming:Name
          string:Basic 		name  (ls:Binding:name)
           Overrides:policy:Object:name | naming:NamedObject:name
           NO COMMENTS
reference:Object pnDn  (ls:Binding:pnDn)
           Overrides:ls:ComputeBinding:pnDn
           property name="pnDn" type="reference:Object" refers="compute:Blade" owner="management" mod="explicit" backup="yes" /
mo:PropAclMask
          scalar:Uint64 		propAcl  (ls:Binding:propAcl)
           NO COMMENTS
Defined in: ls:ComputeBinding
ls:AdminActionType
          scalar:Enum8 		adminAction  (ls:ComputeBinding:adminAction)
           NO COMMENTS
ls:AdminActionTrigger
          scalar:Enum8 		adminActionTrigger  (ls:ComputeBinding:adminActionTrigger)
           NO COMMENTS
reference:Object assignedToDn  (ls:ComputeBinding:assignedToDn)
           NO COMMENTS
reference:Object computeEpDn  (ls:ComputeBinding:computeEpDn)
           a reference to FRU-specific end-point representing corresponding compute unit (fabric:ComputePhEp)
ls:ConfigIssues
          scalar:Bitmask64 		issues  (ls:ComputeBinding:issues)
           NO COMMENTS
ls:ComputeBindingOperState
          scalar:Enum8 		operState  (ls:ComputeBinding:operState)
           NO COMMENTS
scalar:Bool restrictMigration  (ls:ComputeBinding:restrictMigration)
           property name="prio" type="AssignmentPriority" owner="admin" mod="explicit" />
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

adminAction

Type: ls:AdminActionType
Primitive Type: scalar:Enum8
Units: null
Encrypted: false
Access: admin
Category: TopLevelRegular
Property Validators:

Comments:
NO COMMENTS
Constants
unspecified 0 NO COMMENTS
reapply-config 1 NO COMMENTS
DEFAULT unspecified(0) NO COMMENTS

adminActionTrigger

Type: ls:AdminActionTrigger
Primitive Type: scalar:Enum8
Units: null
Encrypted: false
Access: admin
Category: TopLevelRegular
Property Validators:

Comments:
NO COMMENTS
Constants
idle 0 NO COMMENTS
triggered 1 NO COMMENTS
DEFAULT idle(0) NO COMMENTS

assignedToDn

Type: reference:Object
Refers: compute:Physical
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

computeEpDn

Type: reference:Object
Refers: fabric:ComputePhEp
Units: null
Encrypted: false
Access: implicit
Category: TopLevelRegular
Property Validators:

Comments:
a reference to FRU-specific end-point representing corresponding compute unit (fabric:ComputePhEp)

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: ls:ConfigIssues
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
boot-order-pxe 1024ull issue with boot order, possibly vnic not found
wwnn-derivation-from-vhba 1048576ull wwwnn derivation
migration 1073741824ull NO COMMENTS
incompat-bios-for-sriov-vnics 1099511627776ull NO COMMENTS
iscsi-initiator-ip-address 1125899906842624ull NO COMMENTS
remote-policy 1152921504606846976ull NO COMMENTS
wwnn-assignment 128ull wwnn address assignment failed for a vhba, possibly illegal wwnn address or no available wwn in the pool
processor-requirement 131072ull server does not fulfill processor requirements of the service profile
physical-requirement 134217728ull Physical requirement unfulfilled
hostimg-policy-invalid 137438953472ull NO COMMENTS
vif-resources-overprovisioned 140737488355328ull NO COMMENTS
pinning-invalid 144115188075855872ull NO COMMENTS
incompatible-number-of-local-disks 16384ull server does not fulfill local disk requirements of the service profile
mac-derivation-virtualized-port 16777216ull mac address cannot be cannot be hardware derived on a virtualized port
switch-virtual-if-capacity 16ull Not enough VIfs available on switch, check if blade is discovered from both sides, possibly have to add more uplinks from chassis to switch
invalid-wwn 17179869184ull Invalid wwn/wwpn
missing-raid-key 17592186044416ull Missing RAID key.
board-controller-update-unsupported 18014398509481984ull NO COMMENTS
insufficient-resources 1ull overall there are not enough resources
compute-undiscovered 2048ull server is still not discovered
boot-configuration-invalid 2097152ull Boot order cannot include entries of both san and local disk
incompatible-bios-image 2147483648ull Missing BIOS image.
iscsi-config 2199023255552ull NO COMMENTS
storage-path-configuration-error 2251799813685248ull NO COMMENTS
resource-ownership-conflict 2305843009213693952ull NO COMMENTS
system-uuid-assignment 256ull uuid address assignment failed, possibly illegal uuid or no available uuid in the pool
server-position-requirement 262144ull server does not fulfill chassis/blade id requirements of the service profile
destructive-local-disk-config 268435456ull Destructive local disk configuration.
imgsec-policy-invalid 274877906944ull NO COMMENTS
pinning-vlan-mismatch 281474976710656ull NO COMMENTS
non-interrupt-fsm-running 288230376151711744ull NO COMMENTS
vnic-capacity 2ull Not enough VNICs available
adaptor-requirement 32768ull server does not fulfill adapter requirements of the service profile
mac-address-assignment 32ull mac address assignment failed for a vnic, possibly illegal mac address or no available macs in the pool
qos-policy-invalid 33554432ull NO COMMENTS
insufficient-power-budget 34359738368ull NO COMMENTS
boot-order-iscsi 35184372088832ull Boot order cannot include entries of both san and local disk
vnic-vcon-provisioning-change 36028797018963968ull NO COMMENTS
adaptor-protected-eth-capability 4096ull server's adapter is not failover capable
connection-placement 4194304ull NO COMMENTS
incompatible-disk-types 4294967296ull Different disk technologies such as HDD and SSD cannot be mixed in a single RAID.
vnic-not-ha-ready 4398046511104ull NO COMMENTS
zone-capacity 4503599627370496ull NO COMMENTS
adaptor-out-of-vifs 4611686018427387904ull NO COMMENTS
duplicate-address-conflict 4611686018427387904ull NO COMMENTS
vhba-capacity 4ull Not enough VHBAs available
boot-order-san-image-path 512ull issue with boot order, possibly vhba not found or boot target not found
compute-unavailable 524288ull compute unavailable
power-group-requirement 536870912ull NO COMMENTS
provsrv-policy-invalid 549755813888ull NO COMMENTS
vnic-vlan-assignment-error 562949953421312ull NO COMMENTS
missing-firmware-image 576460752303423488ull missing firmware image.
wwpn-assignment 64ull wwpn address assignment failed for a vhba, possibly illegal wwpn address or no available wwn in the pool
memory-requirement 65536ull server does not fulfill memory requirements of the service profile
vlan-port-capacity 67108864ull NO COMMENTS
bootip-policy-invalid 68719476736ull gpxe policies error
vfc-vnic-pvlan-conflict 70368744177664ull NO COMMENTS
named-vlan-inaccessible 72057594037927936ull NO COMMENTS
adaptor-fcoe-capability 8192ull server's adapter is not fcoe capable
wwpn-derivation-virtualized-port 8388608ull WWWPN cannot be hardware derived on a virtualized port
incompatible-raid-level 8589934592ull Incomptible RAID level.
missing-primary-vlan 8796093022208ull NO COMMENTS
fcoe-capacity 8ull Not enough FCOE capable vnics
dynamic-vf-vnic 9007199254740992ull One of the vNICs referenced by a named VLAN is inaccessible to this server.
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: implicit
Category: TopLevelRegular
Property Validators:
    Range:  min: "0"  max: "16"
        Allowed Chars:
            Regex: [a-zA-Z0-9_.:-]+

Comments:
NO COMMENTS
Constants
defaultValue "pn-binding" NO COMMENTS

operState

Type: ls:ComputeBindingOperState
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

pnDn

Type: reference:Object
Refers: compute:Physical
Overrides:ls:ComputeBinding:pnDn
Units: null
Encrypted: false
Access: admin
Category: TopLevelRegular
Property Validators:

Comments:
property name="pnDn" type="reference:Object" refers="compute:Blade" owner="management" mod="explicit" backup="yes" /

propAcl

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

Comments:
NO COMMENTS

restrictMigration

Type: scalar:Bool
Units: null
Encrypted: false
Access: admin
Category: TopLevelRegular
Property Validators:

Comments:
property name="prio" type="AssignmentPriority" owner="admin" mod="explicit" />
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.

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