Class policy:Item (ABSTRACT)

Class ID:1342
Encrypted: false - Exportable: false - Persistent: true
Privileges: []
SNMP OID:

The base class for all objects contained by policy:Definition. Though no containment rules are specified here, by convention policy:Item must be contained by either policy:Definition or another policy:Item.


Naming Rules


DN FORMAT: 

                




Inheritance
policy:Item
 ├
aaa:Item
 
 ├
aaa:Config This MO represents generic AAA configuration. Though today it is used only for Authentication configuration, Accounting configuration could derive from this MO in future
 
 
 ├
aaa:AuthMethod This MO represents generic Authentication configuration.
 
 
 
 ├
aaa:ConsoleAuth MO representing the Authentication configuration for Console Login
 
 
 
 ├
aaa:DefaultAuth MO representing the Default Authentication configuration for all logins
 
 
 
 ├
aaa:DomainAuth MO representing the Default Authentication configuration domain logins
 
 ├
aaa:Domain This MO represents an AAA (accounting/authorization/accounting) domain. The AAA configuration can be configured per domain.
 
 ├
aaa:LdapGroupRule This MO is the end point for all Ldap Group related configuration. When contained under LdapEp, this represents the global configuration. When contained under LdapProvider, this represents per server configuration
 
 ├
aaa:Org Represents an org membership within a aaa:Locale object.
 
 ├
aaa:Provider
 
 
 ├
aaa:LdapProvider
 
 
 ├
aaa:RadiusProvider
 
 
 ├
aaa:TacacsPlusProvider
 
 ├
aaa:ProviderGroup This MO represents a group of AAA remote servers supporting same kind of protocol. A member of this group is repreented by ProviderRef MO
 
 ├
aaa:ProviderRef The MO represents member of ProviderGroup
 
 ├
aaa:SystemUser
 
 
 ├
aaa:EpUser An IPMI user
 
 
 ├
aaa:RemoteUser
 
 
 ├
aaa:User
 
 
 ├
comm:SnmpUser
 
 
 ├
storage:EpUser
 
 ├
aaa:UserGroup Top level abstract MO representing the mapping of user's group to roles and locales
 
 
 ├
aaa:LdapGroup Concrete MO representing the mapping of user's group downloaded from remote LDAP server to roles and locales
 
 ├
aaa:UserLocale This MO is used to assign a locale to local user, remote user, ldap groups. This is used to restrict an user's access to certain orgs.
 
 ├
aaa:UserRole This MO is used to assign a role to local user, remote user, ldap groups. This is used to manage access permission to an user.
 ├
callhome:AnonymousReporting
 ├
callhome:Dest
 ├
callhome:Item
 
 ├
callhome:Policy
 
 ├
callhome:Profile
 ├
callhome:PeriodicSystemInventory
 ├
callhome:Smtp
 ├
callhome:Source
 ├
callhome:TestAlert
 ├
comm:Item
 
 ├
comm:ClientItem
 
 
 ├
comm:DnsProvider
 
 
 ├
comm:NtpProvider
 
 ├
comm:Locale
 
 ├
comm:SyslogConsole
 
 ├
comm:SyslogFile
 
 ├
comm:SyslogMonitor
 
 ├
comm:SyslogSource
 ├
comm:SnmpTrap
 ├
comm:SyslogClient This object is used to control how syslog messages are sent to a remote destinations
 ├
extmgmt:ArpTargets
 ├
extmgmt:GatewayPing
 ├
extmgmt:MiiStatus
 ├
extmgmt:NdiscTargets
 ├
fault:SuppressPolicyItem
 ├
firmware:AExcludeComponent
 
 ├
firmware:ExcludeChassisComponent
 
 ├
firmware:ExcludeServerComponent
 ├
lstorage:Item An abstract base class to represent of a storage item provisionned by the user. Storage Technologies Multiple storage technologies are available as shown in the list below. Each storage technology may require a different set of properties for the provisioning. The lstorage:Item object is subclassed for each class of storage technology. SCSI block-...
 
 ├
lstorage:ControllerDef
 
 ├
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:DasScsiLun Represents the storage requirements for a Direct Attach Storage LUN. Direct Attach Storage LUNs are configured in local disks, such as locally attached SAS disks connected to SCSI controllers. Local LUN Provisioning There are multiple options for provisioning local LUNs: Creating a {@link storage:LocalDiskConfigDef} MO under a {@link ls...
 
 ├
lstorage:Security
 ├
lstorage:LocalDiskRef A specification of a local disk, by enclosure ID and disk slot ID.
 ├
qos:Item
 
 ├
epqos:Item
 
 
 ├
epqos:Egress
 
 ├
qosclass:Item
 
 
 ├
qosclass:Eth
 
 
 
 ├
qosclass:EthBE
 
 
 
 ├
qosclass:EthClassified
 
 
 ├
qosclass:Fc
 ├
sysdebug:LogBehavior Abstraction of managed endpoint log configuration definition. Specifies configuration of log behavior on a given compute resource. Managed endpoint log Interface is implicitly derived from corresponding configuration of the logical server. mo name="MEpLogIf" super="MEpLogDef" concrete="yes" >
 
 ├
sysdebug:BackupBehavior
 ├
trig:Window
 
 ├
trig:SchedWindow Scheduled Window.
 
 
 ├
trig:BaseAbsWindow
 
 
 
 ├
trig:AbsWindow
 
 
 
 ├
trig:LocalAbsWindow
 
 
 ├
trig:BaseRecurrWindow BaseRecurrWindow
 
 
 
 ├
trig:RecurrWindow RecurrWindow
 ├
vnic:EthConfig
 ├
vnic:IScsiConfig

Events
                



Faults
                



Fsms
                



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

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.