Cisco System Model: Classls: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 ...

├

cimcvmedia:MountConfigDef This is the DefMo maintained under computePhysicalMo and also the same MO is used for specific vMedia policy (unnamed) where it is maintained under lsServerMo

├

cimcvmedia:ConfigMountEntry This MO represents each of the configured vmedia mapping entries(ex: CD or HDD type)

fabric:VCon Represents a virtual network interface connection (vCon), which is a virtual representation of a physical adapter. When a vNIC/vHBA placement policy is assigned to a service profile, and the service profile is associated with a server, the vCons in the vNIC/vHBA placement policy are assigned to the physical adapters. vNICs or vHBAs can be assigned to a vCon. Cisco UCS Man...

├

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.

├

fault:SuppressTask

├

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.

├

trig:LocalSched A locally defined user-defined schedule. The schedule is contained locally by the Managed Object that needs the schedule, as opposed to being referred by name.

├

trig:SchedWindow Scheduled Window.

├

ident:RequestEp

├

initiator:RequestorEp Beginning of objects related to storage devices this represents the compute node

├

initiator:GroupEp

├

initiator:InitiatorEp this represents the hostep that a Lun is visible to

storage:IScsiTargetIf

ls:ComputeBinding Abstract Representation of a binding between a ls:Server and physical server.

├

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.

├

ls:FcLocale The FcLocale hierarchy should not get copied from one service profile to another while cloning (creating template from SP or instantiating a Template). FcLocaleMo is created one per side under lsServer.

├

ls:FcZoneGroup FcZoneGroupMo created per Vsan. It contains FcZones created under this Vsan.

├

ls:ZoneInitiatorMember Initiator member of a Fibre Channel Zone.

├

ls:FcZone Mo for representing a Fibre Channel Zone.

├

ls:ZoneTargetMember Target Member of a Zone

├

ls:IdentityInfo

├

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.

├

ls:Issues Configuration Issues on the Logical Server. This is a singleton object implicitly populated under lsServer to proactively show configuration issues/missing/invalid configurations in the given logical server, under the following scenarios:- a: server profile association b: template association lsServer(configQuali...

├

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.

├

ls:Power Allows the user to control the power state of a Service Profile. For example, the API user can use this MO to power on the blade associated with a service profile.

compute:PhysicalAssocCtx

├

processor:UnitAssocCtx

ls:UuidHistory A temporary object used to hold the history of lsServer object properties.

├

ls:VConAssign The VConAssign is used by the server administrator to administratively assign a named vNIC or vHBA interface to a numbered virtual connection. The vCon assignment is used to specify the PCI placement when a service profile contains multiple interfaces. To specify the PCI placement and PCI order, there are three options: Specify a vNIC/vHBA placement policy by se...

├

ls:VersionBeh

├

lsboot:Def TODO: decide the role if it admin or read-only Def

├

lsboot:BootSecurity Container for secure boot variables Boot Security

├

lsboot:Category Boot order category base class

├

lsmaint:Ack Ack

├

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.

├

trig:LocalSched A locally defined user-defined schedule. The schedule is contained locally by the Managed Object that needs the schedule, as opposed to being referred by name.

├

trig:SchedWindow Scheduled Window.

├

lstorage:ProfileBinding Represents a binding between a Service Profile ({@link ls:Server}) and a {@link lstorage:Profile}

├

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.

├

lstorage:ProfileDef An object contained by {@link ls:Server} that encapsulates the service profile storage requirements. This object provides the same functionality as a {@link lstorage:Profile}, but unlike a {@link lstorage:Profile}, it is contained directly under a {@ls:Server}. This can be useful in cases when the {@link ls:Server} must be self-contained. The storage specified under a Stor...

├

lstorage:ControllerDef

├

lstorage:ControllerModeConfig

├

lstorage:ControllerQualifier

├

lstorage:LunSetConfig

├

lstorage:LunSetDiskSlot Represents the Diskslots which are part of LunSet.

├

lstorage:VirtualDriveDef Virtual Drive Def

├

lstorage:ScsiLun Encapsulates the storage requirements for a single SCSI LUN. The user specifies whether the LUN should be accessed locally or remotely. Based on the requirements, the system automatically creates the SCSI LUN using one of the following methods: SCSI LUN is created locally on a physical server, such as a SCSI LUN configured in a RAID group using Direct Atta...

├

lstorage:Security

├

lstorage:DriveSecurity

lstorage:Login This is used to store the login information for KMIP server

├

mgmt:Interface

├

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.

├

mgmt:Vnet

├

vnic:IpV4AddrExplConf

├

vnic:IpV6AddrExplConf

├

mo:KvCfgHolder A container for configured MO annotations

├

mo:AbstractCfgKv An abstract representation of a configured annotation.

├

sol:Config Abstraction of Serial over LAN configuration definition. Specifies configuration of Serial over LAN interface on a given compute resource. SOL configuration is optionally instantiated under logical server profile.

├

storage:ALunRefBase ALunInstRefBase is used for a service profile to reference a local/remote deployed LUN. We can define concrete subclasses for local/remote LUN ref, respectively.

├

storage:IniGroup Initiator Group definition. This specifies the list of initiators that form a logical group for HA/Multipath purpose.

├

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.

├

storage:Initiator Named initiator that participates in a storage IniGroup

├

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.

├

vnic:FcGroupDef vHBA Group

├

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.

├

storage:ConnectionDef Policy used for specifying the target storage configuration. storage::ConnectionDef is created under storage::IniGroup, hence a local storage:ConnectionDef can be created for every IniGroup.

├

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.

├

storage:FcTargetEp FcTargetEp represents target pWWNs given by the user. An FcTargetEpMo is created for every target pWWN.

├

storage:VsanRef VsanRefMo represents the Vsan applied on the storage:Target/ User-defined FC Zone. A VsanRefMo is created for every Vsan applied on the storage:Target/ User-defined FC Zone.

├

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.

├

storage:LocalDiskConfigDef LocalDiskConfig

├

lstorage:Security

├

lstorage:DriveSecurity

lstorage:Login This is used to store the login information for KMIP server

├

storage:LocalDiskPartition identifies a partition as identified by fdisk

├

vnic:ConnDef Connection Definition. A single ConnDef may be contained by a Logical Server in order to reference LAN/SAN connectivity policies. The referenced LAN/SAN connectivity policies describe the network/storage resources for the logical server.

├

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.

├

vnic:DefBeh A vnic behavior policy definition to apply to the containing service profile. Behavior policy definitions describe the vnics/vhbas (if any) that should be created for a service profile (ls::Server) that contains no vnics/vhbas. There may be at most 2 DefBeh created for a service profile - one for vnics and one for vhbas.

├

vnic:DynamicCon Specialization of Dynamic Connectivity Requirement. This sace defines the number of vnics preallocated for dynamic use. This object is contained logical server profile and treated as local definition.

├

vnic:FcNode Representation of virtualized abstraction of SAN network Node. This object holds directive to allocation of virtualized or derived World Wide Node Name.

├

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.

├

vnic:WwnnHistory A temporary object used to hold the history of vnicFcNode object properties.

├

vnic:IScsi An IScsi vnic.

├

fabric:FlowMonSrcEp An abstract representation of a source interface in a flow monitoring session.

├

fabric:MonSrcEp An abstract representation of a source port in a monitoring session.

├

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.

├

vnic:IPv4IscsiAddr Represents the IPv4 address of an iSCSI end-point, where the IP address is manually assigned. This object is used to provision a iSCSI vNIC with a static IP address.

├

vnic:IPv4Dns Represents the IP address of a DNS server, which is used to resolve host names to IP addresses.

├

vnic:IScsiAutoTargetIf IScsiAutoTargetIf

├

vnic:IScsiStaticTargetIf Represents one target

├

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.

├

vnic:Lun Represents a logical unit.

├

vnic:IqnHistory A temporary object used to hold the history of vnicIScsi object properties.

├

vnic:MacHistory A temporary object used to hold the history of vnicEtherBase object properties.

├

vnic:Vlan

├

vnic:IPv4If Represents a network end-point configured with an IPv4 Interface. An IP interface can be provisioned using a user-specified static address, a pool of IP addresses or through DHCP. Optionally, the IPv4 interface may be provisionned with a default gateway, static routes and DNS servers.

├

vnic:IPv4Dhcp Represents an IPv4 interface which is configured at run-time through DHCP.

├

vnic:IPv4Dns Represents the IP address of a DNS server, which is used to resolve host names to IP addresses.

├

vnic:IPv4StaticRoute Represents a statically configured IPv4 route entry. A static route is configured by specifying a destination network and next hop router.

├

vnic:IfRole An abstract base class representing the role(s) assigned to the IP interface

├

vnic:IpV4Addr An abstract base class for IP v4 addresses.

├

vnic:IpV4PooledAddr Represents the IPv4 address of an IP interface, where the IP address is obtained from a pool of IP addresses.

├

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.

├

vnic:IpV4History A temporary object used to hold the history of ipv4 address of MOs.

├

vnic:IpV4StaticAddr Represents a statically assigned IPv4 address.

├

vnic:IScsiTargetIfiscsi changes Begin IScsiTargetIf

├

vnic:IScsiBootParams Contains the iSCSI boot configuration of a service profile.

├

vnic:IScsiBootVnic Identifies the vnic for iscsi boot and contains settings.

├

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.

├

vnic:IPv4Dhcp Represents an IPv4 interface which is configured at run-time through DHCP.

├

vnic:IPv4Dns Represents the IP address of a DNS server, which is used to resolve host names to IP addresses.

├

vnic:IPv4StaticRoute Represents a statically configured IPv4 route entry. A static route is configured by specifying a destination network and next hop router.

├

vnic:IfRole An abstract base class representing the role(s) assigned to the IP interface

├

vnic:IpV4Addr An abstract base class for IP v4 addresses.

├

vnic:IpV4PooledAddr Represents the IPv4 address of an IP interface, where the IP address is obtained from a pool of IP addresses.

├

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.

├

vnic:IpV4History A temporary object used to hold the history of ipv4 address of MOs.

├

vnic:IpV4StaticAddr Represents a statically assigned IPv4 address.

├

vnic:IScsiTargetIfiscsi changes Begin IScsiTargetIf

├

vnic:IScsiNode IScsi Identity Information.

├

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.

├

vnic:IqnHistory A temporary object used to hold the history of vnicIScsi object properties.

├

vnic:IpV4AddrExplConf

├

vnic:Vnic An abstract representation of a logical interface within a ls:Server Sub-classes are used to define Ethernet, Fibre Channel, Scsi or other types of interfaces. The interface is realized when the ls:Server is associated with a physical server and the system can find a suitable hardware adapter that can implement the interface specified in this MO.

├

fabric:FlowMonSrcEp An abstract representation of a source interface in a flow monitoring session.

├

fabric:MonSrcEp An abstract representation of a source port in a monitoring session.

├

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

Events

Faults

Fsms

Properties Summary

Defined in: ls:Tier
ls:Apply scalar:Enum8	apply (ls:Tier:apply) NO COMMENTS
naming:Name string:Basic	name (ls:Tier:name) Overrides:policy:Object:name \| naming:NamedObject:name NO COMMENTS
naming:Name string:Basic	srcTemplName (ls:Tier:srcTemplName) NO COMMENTS

Defined in: policy:Definition
naming:Descr string:Basic	descr (policy:Definition:descr) NO COMMENTS
policy:InternalId scalar:Uint32	intId (policy:Definition:intId) NO COMMENTS
scalar:Uint32	policyLevel (policy:Definition:policyLevel) policyLevel is used internally by generic policy server.
policy:PolicyOwner scalar:Enum8	policyOwner (policy:Definition:policyOwner) "local" denotes policy created by local policy client, "policy" denotes a policy created by remote policy server.

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

apply

Type: ls:Apply
Primitive Type: scalar:Enum8

Units: null

Encrypted: false

Access: admin

Category: TopLevelRegular

Property Validators:

Comments:

NO COMMENTS

Constants
onAssociation	1	NO COMMENTS
runTime	2	NO COMMENTS
DEFAULT	onAssociation(1)	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

descr

Type: naming:Descr
Primitive Type: string:Basic

Like: naming:Described:descr

Units: null

Encrypted: false

Access: admin

Category: TopLevelRegular

Property Validators:
    Range:  min: "0"  max: "256"
        Allowed Chars:
            Regex: [a-zA-Z0-9\[\]!#$%()*+,-./:;@ _{|}˜?&]+

Comments:

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

intId

Type: policy:InternalId
Primitive Type: scalar:Uint32

Units: null

Encrypted: false

Access: implicit

Category: TopLevelRegular

Property Validators:

Comments:

NO COMMENTS

Constants
none	0u	NO COMMENTS
DEFAULT	none(0u)	NO COMMENTS

name

Type: naming:Name
Primitive Type: string:Basic

Overrides:policy:Object:name  |  naming:NamedObject:name

Units: null

Encrypted: false

Naming Property -- [NAMING RULES]

Access: naming

Category: TopLevelRegular

Property Validators:
    Range:  min: "1"  max: "16"
        Allowed Chars:
            Regex: [a-zA-Z0-9_.:-]+

Comments:

NO COMMENTS

policyLevel

Type: scalar:Uint32

Units: null

Encrypted: false

Access: implicit

Category: TopLevelRegular

Property Validators:

Comments:

policyLevel is used internally by generic policy server.

policyOwner

Type: policy:PolicyOwner
Primitive Type: scalar:Enum8

Units: null

Encrypted: false

Access: admin

Category: TopLevelRegular

Property Validators:

Comments:

"local" denotes policy created by local policy client, "policy" denotes a policy created by remote policy server.

Constants
local	0	NO COMMENTS
policy	1	NO COMMENTS
pending-policy	2	NO COMMENTS
DEFAULT	local(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

srcTemplName

Type: naming:Name
Primitive Type: string:Basic

Units: null

Encrypted: false

Access: admin

Category: TopLevelRegular

Property Validators:
    Range:  min: "0"  max: "32"
        Allowed Chars:
            Regex: [a-zA-Z0-9_.:-]+

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.