Configures properties of account policy.

The administrator account.

Used for initial and recovery scenarios when authentication to regular O&M accounts is inaccessible.

This MO is created by the system.

Enables configuration of the Arwa server connection properties.

Autonomous Mode state information.

This MO is created by the system.

BrM Root MO class.

This MO is created by the system.

Represents a backup of the type and domain specified by BrmBackupManager in which it is contained.

This MO is created by the system.

Provides optional support for automated housekeeping of manually created backups.

If autoDelete is set to ENABLED, before creating a new manual backup, BRM first checks the number of manual backups and if the limit specified by the value of maxStoredManualBackups is reached, BRM removes the oldest manual backup before creating a new one.

This MO is created by the system.

Provides optional support for labeling of certain backups.
This class contains attributes that help distinguish certain backups such as the last restored backup, primary restore candidate, and so on.

This MO is created by the system.

Serves as container for Backup instances of a particular backupType and backupDomain.

This class also provides the actions for creating new backups, importing backups from other locations, and deleting existing backups of the corresponding type and domain.

This MO is created by the system.

Provides optional support for scheduling of backup creation.

Each instance of BrmBackupScheduler MOC serves as the backup scheduler for the backup type indicated by its parent instance of BrmBackupManager. The scheduled backup event(s) can be instance(s) of BrmSingleEvent MOC, BrmCalendarBasedPeriodicEvent MOC, or BrmPeriodicEvent MOC contained in the instance of BrmBackupScheduler.

This MO is created by the system.

Periodic backup event using calendar-based interval.

This construct can be used to configure a periodic scheduled backup event by specifying the desired interval using calendar. For instance, in order to configure a scheduled backup event to occur every night at 2:00 am, the following setup must be done:
time=02:00:00
The start time for calculating scheduled events is assumed to be the current system time by default, unless explicitly set using the startTime attribute. Furthermore, if the configured event is to stop at a specific date, stopTime attribute must be set accordingly. Note that the default value of stopTime is the end of century.
A scheduled backup event of this type is triggered only if ALL the conditions with regard to attribute values are satisfied. For example, if "dayOfWeek" is set to Monday and "dayOfMonth" is set to 1, the event will be triggered only if the first day of month is Monday.
Daylight saving adjustments in Spring and Fall are addressed such that the affected scheduled backup events are triggered exactly once.

MO for activating and deactivating failsafe backups.
Failsafe backups can be used when making changes to sensitive parts of the model, in which an error in configuration can lead to lost OAM connectivity or other failures from which the system can recover by a restore from a backup. When activated the failsafe backup function will automatically restore the system from a backup if the configuration as not been confirmed within a defined time period.

This MO is created by the system.

Periodic backup event.
This construct can be used to configure a periodic scheduled backup event by specifying the number of months, weeks, days, hours, or minutes. For instance, in order to configure a scheduled backup event to occur every 12 hours, the following setup must be done:

hours=12

The start time for calculating scheduled events is assumed to be the current system time by default, unless explicitly set using the startTime attribute. Furthermore, if the configured event is to stop at a specific date, stopTime attribute must be set accordingly. Note that the default value of stopTime is the end of century.

Confirm a restore action or automatic rollback after an unconfirmed restore operation was executed.
The existence of an instance of this class indicates that this feature is supported by the implementation.
This is optional support.

This MO is created by the system.

A single scheduled backup event.

This construct can be used to configure a single (one-shot) scheduled backup event by specifying the desired date and time.

Key of a licensed capacity that is available for the Managed Element.

This MO is created by the system.

The Carrier Select Managed Object (MO) represents the top level of the Carrier Select application.

This MO is created by the system.

Global configuration parameters for Local Call

Configuration for CarrierContext

CarrierSelectionCode contains attributes to match CSC codes in
the uri.
The CSC will be replaced with CarSelCscReplaceDigits and also add a
cic parameter with the value of CarSelCscCarrierIdentityCode
The Dialed String Analysis carrier code handling supports the
carrier select code appearing in the following locations in a string
of dialed digits:
Within an international number of the form <IDP><CC><national number>:
<IDP><CSC><CC><national number>
<CSC><IDP><CC><national number>

Within a national or local number of the form <NDP><AC><subscriber number>:
<NDP><CSC><AC><subscriber number>
<CSC><NDP><AC><subscriber number>
<CSC><AC><subscriber number>
<CSC><subscriber number>

Where
AC Area Code
CC Country Code
CSC Carrier Select Code
IDP International Dialing Prefix
NDP National Dialing Prefix

*Note that: All combinations of NDP/CSC that is to be used must be
configured in CarrierSelect. This means that to be able
to use <NDP><CSC><AC><Subscriber number>
then the following must be configured:

CarSelCscCarrierIdentityCode: <CIC>
CarSelCarrierSelectionCodeEntry: <NDP><CSC>
CarSelCscReplaceDigits: <NDP>

In this way the carrier select code can appear before the national
dialing prefix (NDP), after the NDP, or instead of the NDP,
and before the international dialing prefix (IDP), after the IDP, or
instead of the IDP.

Container for CarSelCallConfiguration, CarSelCarrierContext and
CarSelIneligibleNumbers MOs.


This MO is created by the system.

Container for DialedStringAnalysis MOs

This MO is created by the system.

This Managed Object Class specifies the set of ineligible
destination numbers for Carrier Select.
There are up to 256 instances of this Managed Object Class in each
instance of Carrier Select.
Instances of this Managed Object Class are created by the user.

The top class of the Certificate Management model.

Certificate management encompasses management of node credentials and trusted certificates.

This MO is created by the system.

Contains the certificate management capabilities of the ME.

This MO is created by the system.

Represents the CLI configuration management service over Secure Shell.

This MO is created by the system.

Represents the CLI configuration management service over Transport Layer Security (TLS).

This MO is created by the system.

Represents a compute resource (virtual or physical) that is allocated to the managed element.
This resource can be a piece of hardware or a VM provided by a virtualization infrastructure management system.



This MO is created by the system.

Represents the service (defined by the role) provided by the compute resource.
Logically, an instance of this class represents the state of the software stack (operating system, middleware, and application) running on the compute resource.

This MO is created by the system.

The root class

This MO is created by the system.

Authorization roles defined by the MS that may be assigned to users.

CustomRole MO instances are associated to CustomRule MO instances, which define the access controls to objects.

The rules created by the MS that define the access control to objects.

The CustomRule MO instances are associated with CustomRole MO instances, which may be then applied to users.

Local time and time zone values.

This MO is created by the system.

This MO is a container for Accounting Application Routing MOs.

This MO is a main entry for all Diameter Application configuration.
It is configured at installation time and value not defined as DIA.

This MO is created by the system.

This MO encapsulates routing information.
Depending on this information decision how to process (what action to be applied to and what destination to be used for routing) the incoming requests from a particular Diameter Application is made.

This MO is a container for Authorization and Authentication Application Routing MOs.

This MO represents Diameter Attribute-Value Pair (AVP) definition.

This MO handles a common Diameter Application configuration.

This MO encapsulates a configuration for a particular Connection object.

This MO is a container for Diameter Vendor and AvpDef MOs.

This MO represents an entry in Realm Routing Table (RRT).