Managed Object Model

The basic building block of a MOM-based management tool is an

MO. A node is managed through the creation, modification and
deletion of MOs.
An MO represents a resource in the node, either a physical
resource such as a plug-in unit, or a logical resource such as a
software program or a protocol. In either case, there are parameters
associated with the resource, called MO attributes.
An MO can be configured by setting values for the MO attributes.
The state and configuration of the resource represented by the MO
are shown by these attribute settings.
There can also be MO actions related to the resource. For
example, the action "assignIpAddress" sets all IP address attributes
on the MO.
Structures and enumerations are used to specify the type of an
attribute.

Naming of MOs
MOs are identified by means of a "naming attribute". All MO
classes have a naming attribute called MoClassNameId, for
example SubrackId. This name is also referred to as the
Relative Distinguished Name (RDN). The RDN is formed from a
type component, that is the MO name, and a value component.
A Local Distinguished Name (LDN) is a sequence of RDNs
based on the MO tree, which forms a unique name within the
node.

Creating and Deleting MOs

All the MOs in a node can be created by a create request,
except for those MOs marked System Created.
When an MO instance is created, its mandatory attributes
must be specified. If it has a parent MO, the instance of the
parent MO must exist already.
Only MO types that have the "delete" operation can be
removed by a delete request. MOs that are System Created do
not have the delete operation and they cannot be deleted.
Before an MO can be deleted, all its children must first be
deleted. Furthermore, all the references to other MOs must be
removed from the MO to be deleted, and all other MOs
containing references to the MO to be deleted must have these
references removed

Attributes
Attributes are used to configure an MO class. They can define the state
and the configuration of a resource represented by the MO class.

Attributes Properties
Mandatory
The initial value of the attribute must be set when the instance of the MO is
created.
Optional with initial value assigned
If no value is specified, the attribute is set automatically to its default value. The
default value is specified after the data type. The only exception concerns MO
references, that is, attributes of type moRef, for which the default value "null" is
assumed.
Restricted
The management tool can specify the attribute value when creating an MO
instance, but cannot change the value subsequently. The management tool can also
retrieve the attribute value by a get operation.
Read Only
The management tool can retrieve the attribute value by a get operation, but a set
operation cannot change the value.
Read Write
The management tool can retrieve the attribute value by a get operation, and use
a set operation to change the value.
Persistent
The attribute value is stored persistently, that is, the value is not changed by a
restart.
NonPersistent
The attribute value is not stored persistently. This applies mainly to state attributes
such as operational State and availability Status. Also, PM attributes are specified as
"nonPersistent"

Relationship between MO Classes

1. Containment, Parent-Child relation

2. Association
1. Containment, Parent-Child
In the MOM, there are parent-child relationships that
define containment between Mos

2. Association
In the MOM, there can be associations between several
MOs. In the diagrams of the MOM, associations are
indicated with solid lines, directed or non-directed.
Suppose there are MO-X and MO-Y, then an Association
can be defined as follows:

An association is when MO-Y uses and/or invokes

methods in MO-X, but MO-X does not have to exist
when MO-Y is created

Naming Rule for Managed Objects in M-MGw