| Managed Object Model 2/155 54-4/AXM10104/1-V1 Uen H |
All Differences in
| Name | : MrfMOM | |
| Version | : 2 | |
| Release | : 5 | |
| Correction | : 0 | |
| Compared to |
| Name | : MrfMOM | |
| Version | : 2 | |
| Release | : 4 | |
| Correction | : 0 | |
| The default Language code of the announcements. Language code has the format of an RFC 5646 language tag. The default language code is used as language code for the basic and variable announcements in case the H.248 (or SIP) message doesn���t doesn???t contain any language code for the requested announcement. Example: en-GB |
| Licensed capacity limit as defined in the installed key file.
For LM deployments that connect to Arwa, the licensed capacity limit is defined in the Arwa License Server. For LM deployments that connect to NeLS, the licensed capacity limit is the capacity limit value granted by NeLS. |
| This MO models the EVS configuration data in the node. The Relative Distinguished Name (RDN) for this MO type is: EvsConfData=1 |
| Basic information about the key file installed on the Managed Element.
This MO is not applicable to LM deployments that connect to Arwa. NeLS. |
| Enables installation of key files and provides information about the installed key file.
This MO is not applicable to LM deployments that connect to Arwa. This MO is not applicable to LM deployments that connect to NeLS. |
| The unique identification of the Managed Element.
Limited to 256 alphanumeric characters including hyphens (-) and underscores (_), no white spaces. This attribute is not applicable to LM deployments that connect to Arwa. NeLS. |
| Indicates whether or not the fingerprint of the Managed Element can be updated.
This attribute is not applicable to LM deployments that connect to Arwa. NeLS. |
| Date and time of the last change in the license inventory.
Change in the license inventory may occur when the key file is updated on the Managed Element or when license information is refreshed by synchronizing with license servers. This attribute is not applicable to LM deployments that connect to Arwa. NeLS. |
| Locking code to be used by the supply organization to provide site-specific license key files.
This attribute is not applicable to LM deployments that connect to Arwa NeLS or LM deployments using ELIM. |
| Publish the License Inventory.
Triggers the immediate publication of license information from the License Key File and usage information from the LmServer cache to the information model. Return value is true if the publication is successful, false otherwise. For LM deployments that connect to Arwa, NeLS, the license information is retrieved from the Arwa Network License Server. |
| The actual SCTP Maximum Transmission Unit (MTU) size size. Contains the actual SCTP MTU towards the Multimedia Telephony Application Server (MTAS). |
| Automatic discovery of SCTP Maximum Transmission Unit (MTU) size based on ICMP. false (default) : Disable automatic discovery of SCTP MTU size towards the Multimedia Telephony Application Server (MTAS). controller node. The used SCTP MTU size value is based on the 'maxSctpPduSize' attribute. true : Enable automatic discovery of SCTP MTU size towards the Multimedia Telephony Application Server (MTAS). controller node. The initial value and upper limit for the SCTP MTU size value is based on the 'maxSctpPduSize' attribute. |
| The maximum size of the SCTP PDU towards the Multimedia Telephony Application Server (MTAS). controller node. The maximum number of bytes in an SCTP PDU that can be transferred in a single unit over a specific path in an IP network. If an SCTP PDU exceeds the configured value it is segmented into multiple IP packets. Note that the value does not include the IP header. When 'enablePathMtuDiscovery' is set, the upper limit of the discovered MTU is based on the value of this attribute. |
| Configuration of the SNMP protocol. For instance configuration of the protocol, for example IP addresses and ports used for SNMP are supported. ports. |
| The administrative state for the SNMP protocol. If LOCKED, no SNMP Traps (alarm, are generated, for example, alarm, alerts or heartbeats) are generated and heartbeats. Also, all access to the SNMP protocol is disabled. |
| Listen addresses for the SNMP agent. This attribute Attribute defines on which ports and IP addresses the agent shall listen listens to for incoming SNMP requests using the that use UDP protocol. The typical configuration is using Typical configurations use one port with IP address 0.0.0.0 and port 161, which means that the standard SNMP port is used on all interfaces. |
| Listen addresses for the SNMP agent using that uses DTLS. This attribute Attribute defines on which ports and IP addresses the agent shall listen listens to for incoming SNMP requests using the that use DTLS transport protocol. The typical configuration is using uses one port with IP address 0.0.0.0 and port 10161, which 10161. This means that the standard port for SNMP over DTLS is used on all interfaces. |
| The node Node credential to be used for SNMP notifications using the with Transport Security Model. Specifies the DN of a NodeCredential MO in Certificate Management. If Transport Sercurity Model (DTLS) Security Model, DTLS, is not used, the attribute value may can be empty. |
| The value component of Holds the RDN. name used when identifying the MO. |
| The trust category used for authentication of DTLS protocol users. Specifies the DN of a TrustCategory MO in Certificate Management. If not the DTLS protocol is not used, the attribute value may can be empty. |
| Host address (or or DNS name) name for the SNMP Trap trap target. |
| Administrative state for the SNMP target. When LOCKED, for this MO instance traps will are not be sent and access is not allowed. allowed for this MO instance. |
| Specifies if the user has write access write-access to MIB or not. MIB. If false, the user is only allowed to perform read access (SNMP GET etc.) The read-access, such as SNMP GET. Attribute value of this attribute has no relevance if there is a SnmpViewV1 exists for the community of this instance. The permissions Permissions in the view will then override this attribute. |
| The value component of Holds the RDN. name used when identifying the MO. |
| An SNMP target defines a Trap trap receiver and gives access privileges. This class, defines V2C protocol attributes attributes. |
| Host address (or or DNS name) name for the SNMP Trap trap target. |
| Administrative state for the SNMP target. When If LOCKED, for this MO instance traps will are not be sent and access is not allowed. allowed for this MO instance. |
| The SNMP community string. |
| The number of retries to be attempted when a no response is not received for a notification. This Attribute value has relevant only relevance if transportMethod is set to INFORM. |
| Timeout for SNMP INFORM. When an If SNMP INFORM is not acknowledged within during this time period, an time, the implementation may can assume that the notification has was not been delivered. This Attribute value has relevant only relevance if transportMethod is set to INFORM. The unit is centisecond (0.01 seconds). hundredth of a second, 0.01 seconds. |
| Specifies if the user has write access users have write-access to MIB or not. MIB. If false, the user is users are only allowed to perform read access (SNMP GET etc.) The read-access, such as SNMP GET. Attribute value of this attribute has no relevance if there is a SnmpViewV2C exists for the community of this instance. The permissions Permissions in the view will then override this attribute. |
| The value component of Holds the RDN. name used when identifying the MO. |
| The Method type of method to use, can used. Can be TRAP or INFORM. |
| An SNMP target defines a Trap trap receiver and gives access privileges. This class, defines V3 USM protocol attributes. |
| Host address (or or DNS name) name for the SNMP Trap trap target. |
| Administrative state for the SNMP target. When If LOCKED, for this MO instance traps will are not be sent and access is not allowed. allowed for this MO instance. |
| The authentication Authentication key used for signing SNMP notifications. Authentication is performed by using a user's authKey AuthKey used to sign the messages being sent. Note that the length of the key Key must be contain at least 8 characters. This Must have a value, but the value attribute has is used only relevance if authorization is enabled (see enabled. See attribute snmpSecurityLevel). snmpSecurityLevel. If authorization is disabled, attribute can contain any arbitrary value. |
| The authentication Authentication protocol used. This value attribute has Value relevant only relevance if authorization is enabled (see enabled. See attribute snmpSecurityLevel). snmpSecurityLevel. |
| The number of retries to be attempted when a no response is not received for a notification. This Attribute value has relevant only relevance if transportMethod is set to INFORM. |
| Timeout for SNMP INFORM. When an If SNMP INFORM is not acknowledged within during this time period, an time, the implementation may can assume that the notification has was not been delivered. This Attribute value has relevant only relevance if transportMethod is set to INFORM. The unit is centisecond (0.01 seconds). hundredth of a second, 0.01 seconds. |
| Specifies if the user has write access users have write-access to MIB or not. MIB. If false, the user is users are only allowed to perform read access (SNMP GET etc.). The read-access, such as SNMP GET. Attribute value of this attribute has no relevance if there is a SnmpViewV3 exists for the user community of this instance. The permissions Permissions in the view will then override this attribute. |
| Privacy key used for encryption. Encryption is performed by using a user's User's privKey to encrypt encrypts the data portion of the message being sent. Note that the length of the key message. Key must be contain at least 8 characters. This Must have a value, but the value attribute has is used only relevance if privacy is enabled (see enabled. See attribute snmpSecurityLevel). snmpSecurityLevel. If privacy is disabled, attribute can contain any arbitrary value. |
| The privacy Privacy protocol used. This Attribute value attribute has relevant only relevance if privacy is enabled (see enabled. See attribute snmpSecurityLevel). snmpSecurityLevel. |
| The SNMP Specifies the level of security level. applied to messages exchanged with this target. |
| The value component of Holds the RDN. name used when identifying the MO. |
| The Method type of method to use, can used. Can be TRAP or INFORM. |
| The SNMP V3 user name for the SNMP V3 message. |
| An SNMP target defines a Trap trap receiver and gives access privileges. This class, class defines attributes needed for SNMP over DTLS. The attributes Attributes nodeCredential and trustCategory defined in the Snmp MO class/instance are used. DTLS is used as transport protocol both for incoming requests, outgoing responses and SNMP notifications. |
| Host address (or or DNS name) name for the SNMP Trap trap target. |
| Administrative state for the SNMP target. When If LOCKED, for this MO instance traps will are not be sent and access is not allowed. allowed for this MO instance. |
| The number of retries to be attempted when a no response is not received for a notification. This Attribute value has relevant only relevance if transportMethod is set to INFORM. |
| Timeout for SNMP INFORM. When an If SNMP INFORM is not acknowledged within during this time period, an time, the implementation may can assume that the notification has was not been delivered. This Attribute value has relevant only relevance if transportMethod is set to INFORM. The unit is centisecond (0.01 seconds). hundredth of a second, 0.01 seconds. |
| Specifies if the user has write access users have write-access to MIB or not. MIB. If false, the user is users are only allowed to perform read access (SNMP GET etc.). The read-access, such as SNMP GET. Attribute value of this attribute has no relevance if there is a SnmpViewV3 exists for the user community of this instance. The permissions Permissions in the view will then override this attribute. |
| The value component of Holds the RDN. name used when identifying the MO. |
| The Method type of method to use, can used. Can be TRAP or INFORM. |
| The SNMP V3 user name. The user name is used Used for authorization of incoming SNMP requests. The user name is defined Defined by the subject alternative name field of field, from the certificate provided by the client at the during DTLS session setup. |
| An SNMP view gives users access to SNMP MIBs. This class explicitly defines a view for one or several SNMP V1 users. A user is Users are identified by a community name. Communities that are not configured in any view, are given by default given access to the following SNMP MIBs: - Ericsson Alarm MIB - SNMP-FRAMEWORK-MIB - MIB-2 The default Default status denies access to other SNMP MIBs. An explicit Create a new view configuration must be created if this default behaviour is not sufficient. insufficient. |
| Defines which SNMP OIDs the user is allowed to read. The defined OIDs and all their contained OIDs will be are readable. |
| The value component of Holds the RDN. name used when identifying the MO. |
| Defines which SNMP OIDs the user is allowed to write. The defined OIDs and all their contained OIDs will be are writeable. |
| An SNMP view gives users access to SNMP MIBs. This class explicitly defines a view for one or several SNMP V2C users. A user is Users are identified by a community name. Communities that are not configured in any view, are given by default given access to the following SNMP MIBs: - Ericsson Alarm MIB - SNMP-FRAMEWORK-MIB - MIB-2 The default Default status denies access to other SNMP MIBs. An explicit Create a new view configuration must be created if this default behaviour is not sufficient. insufficient. |
| Defines which SNMP OIDs the user is allowed to read. The defined OIDs and all their contained OIDs will be are readable. |
| The value component of Holds the RDN. name used when identifying the MO. |
| Defines which SNMP OIDs the user is allowed to write. The defined OIDs and all their contained OIDs will be are writeable. |
| An SNMP view gives users access to SNMP MIBs. This class explicitly defines a view for one or several SNMP V3 users. A user is Users are identified by a user community name. Users Communities that are not configured in any view, are given by default given access to the following SNMP MIBs: - Ericsson Alarm MIB - SNMP-FRAMEWORK-MIB - MIB-2 The default Default status denies access to other SNMP MIBs. An explicit Create a new view configuration must be created if this default behaviour is not sufficient. insufficient. |
| Defines which SNMP OIDs the user is allowed to read. The defined OIDs and all their contained OIDs will be are readable. |
| The value component of Holds the RDN. name used when identifying the MO. |
| Defines which SNMP OIDs the user is allowed to write. The defined OIDs and all their contained OIDs will be are writeable. |
| The root structural element of SW management activities.
activities. |
| Reference to the active software version(s) actively controlling the behavior of the managed element. Deprecated: Attribute has been removed from ECIM SWM 4.2, deprecated in CmwSwM 5.1 |
| Stops Cancel can be invoked during any long-lasting operation.
It stops the operation and restores the (consistent) consistent state present that existed before the long lasting long-lasting operation was started. Cancel can be invoked during any long lasting operation. The action returns immediately after invocation. The consequences of the action can be tracked via the progressReport attribute. by attribute progressReport. The action returns false if the action is refused by the ME, ME. In all other cases, it returns true otherwise. true. |
| Creates a new UpgradePackage MO representing an that represents a UP specified by a URI.
This action includes all activities to initialize the UP MO. After the UP MO is created, all descriptive information will be available: e.g. is available, for example, administrativeData, number/names number or names of activation step(s) step data. This action can be invoked when there is no other action in progress on this MO. MO. The action returns immediately after invocation. The progress of the action can be tracked via the by attribute progressReport attribute. . The action returns 0 if the action could not cannot start for any reason (e.g., reason, for example, another parallel action is in progress), otherwise returns the id of the action. progress. The action id is different and unique for every invocation of the action. The action also returns 0 if the ME cannot handle the URI (e.g., URI, for example, it does not support the protocol specified in the URI). URI. In all other cases, it returns the id of the action. The action id is different and unique for every invocation of the action. |
| A password to the server which that provides the UP.
If authentication is not password based, password-based, this parameter will be is ignored. |
| Contains a URI pointing that points to a directory containing that contains the UP content.
The generic URI syntax is defined by RFC 2396 2396. The URI must not contain any password. (The The password shall must be provided in the second parameter of this action.) action. The URI may can be local absolute (e.g., file:///data/dir/subdir), or remote (e.g., sftp://hostname/dir/subdir). absolute, for example, file:///data/dir/subdir. It can also be remote, for example, sftp://hostname/dir/subdir. |
| Maximum interval in seconds within which the next action must be invoked to avoid fallback.
The maximum number of seconds allowed to elapse between the finish of an activation step and the start of the next action - a new activate() action - or commit() action. I.e., this new confirm() action. This attribute holds the value to which the attribute timeRemainingBeforeFallback is set after the action activate() is successfully completeted. completed. -1 symbolizes "infinity". means infinity. In this case, the starting start value of timeRemainingBeforeFallback shall must also be set to -1 when the timer stars starts, even though no counting down countdown ever starts (it remains always -1). |
| Action removeSwVersion is deprecated, it is recommended to use action removeSoftwareVersion.
Removes a SW version as completely as possible without disturbing node functionality. Files shared with other SW versions are not deleted. The active SW version cannot be removed. This action can only be invoked when there is no other action in progress on this MO. The action returns false if any of these conditions are violated. The action returns immediately after invocation. The progress of the action can be tracked via the progressReport attribute. Deprecated: Action has been removed from ECIM SWM 4.2, deprecated in CmwSwM 5.1 |
| Removes an UpgradePackage.
This action removes the UpgradePackage MO specified as action parameter as well as parameter. It also removes all files temporarily stored in the ME and associated with the UP. UP. The action returns immediately after invocation. The progress of the action can be tracked via the progressReport attribute. by attribute progressReport. This action can be invoked when there is no other action in progress on this MO. The action returns false if the action could not start for any reason (e.g., reason, for example, another parallel action is in progress), otherwise progress. In all other cases, it returns true. |
| An UpgradePackage MO to be removed. The DN of the UpgradePackage MO to be removed. |
| Represents the progress report (including result) report, including the result, of the ongoing action.
This MO supports only one action to be executed execution at a time. |
| The value component of Holds the RDN.
name used when identifying the MO. |
| Indicates Shows whether fallback capability is supported or not.
not.
If fallback capability is not supported, then setting SwM fallbackTimer has no effect and automatic fallback never happens. does not occur. |
| Remaining number of seconds before performing fallback.
The value fallback.
Value -1 indicates an infinite number of seconds. seconds. Fallback means that the system returns to the state PREPARE_COMPLETED. PREPARE_COMPLETED . |
| This class is used to represent the main SW version running on the ME.
Such MO may be created after activating an UP. An active software version is actively controlling the behaviour of the ME, while a non-active version represents software not yet activated or software which has been de-activated during some previous activation. There may be one or more active software versions. This class is similar to the SwVersion class in the SW Inventory Fragment. Both SW Inventory SwVersion MOC and SwM SwVersionMain MOC represent overall software version of the ME. Deprecated: Class has been removed from ECIM SwM 4.2, deprecated in CmwSwM 5.1 |
| The product identification of the software version.
Deprecated: Attribute has been removed from ECIM SwM 4.2, deprecated in CmwSwM 5.1 |
| Everyday name of the SW version.
It may contain any longer textual description. Deprecated: Attribute has been removed from ECIM SwM 4.2, deprecated in CmwSwM 5.1 |
| Amount of disk space in KB that will be freed if this SW version is deleted.
This figure may thus vary depending on what other SW versions exist - files shared between two SW versions will only be deleted when the last of those SW versions is deleted. Deprecated: Attribute has been removed from ECIM SwM 4.2, deprecated in CmwSwM 5.1 |
| Associated Software Inventory Management MO.
Both SW Inventory SwVersion MOC and SwM SwVersionMain MOC represent overall software version of the ME. Deprecated: Attribute has been removed from ECIM SwM 4.2, deprecated in CmwSwM 5.1 |
| The value component of the RDN. Deprecated: Attribute has been removed from ECIM SwM 4.2, deprecated in CmwSwM 5.1 |
| old: | 0 | |
| new: | 1 |
| old: | 0 | |
| new: | 1 |
| Describes Controls the change process of changing the software configuration of an ME and actions to control the change process.
a ME.
An instance of UpgradePackage (UP) represents a specific change change of software configuration from the existing one to the new one identified by the attribute administrativeData. The execution of the change process described by UP class is the normal way to change the content of the SW inventory. inventory. An UP may can be seen as a "modification agent": it modification agent. It can add new, remove, or modify functionality. When the upgrade package MO is created the upgrade control file is downloaded to specify the administrative data and the activation steps for this upgrade. functionality. The sequence in which a Software upgrade executes is: is as follows: 1. Prepare 2. Verify (optional) Verify, which is optional 3. Activate 4. Commit Confirm When the upgrade package MO is created the upgrade control file is downloaded to specify the administrative data and the activation steps for this upgrade. |
| Current upgrade package is taken into operation fully or partially.
Partial activation occurs if the UCF defines activation steps and the attribute ignoreBreakPoints is false. The ME upgrade engine notifies the operator that the activation step is completed. The next activation step starts when the operator invokes an activate action. Each UP has to must have at least 1 activation step. step. When the attribute ignoreBreakPoints=true, all activation steps are executed in sequence, when sequence. When an activation step is complete complete, the ME executes the next activation step i.e. step. That means there is no operator invocation when an activation step is complete. The time for observation of the correct operation of the ME ME, after each completed step step, is always monitored by a supervision timer. timer. The invocation of activate() may can be monitored by a supervision timer. timer. If the supervision timer expires before invocation of activate() or commit(), then confirm(), the activation fails and the ME falls back to the state PREPARE_COMPLETED. PREPARE_COMPLETED. The action returns immediately after invocation. The progress of the action can be tracked via the progressReport attribute. by attribute progressReport. The action returns false if the action could not start for any reason (e.g., reason, for example, another parallel action is in progress), otherwise progress. In all other cases, it returns true. true. This action can be invoked when the state is PREPARE_COMPLETED or ACTIVATION_STEP_COMPLETED. If the action is invoked in a state where the action has no meaning, ME is expected to return an error message. |
| List of activation steps in the activation procedure consists of.
procedure.
It is possible to stop after each step, perform supervision supervision, and continue with the procedure. The procedure.The upgrade procedure consists of at least one activation step. |
| The product identification of the software version(s) being versions that are activated at successful completion of the full sequence of actions for when an upgrade.
upgrade is completed.
If the resulting software version after activation is unknown or uncertain, the administrativeData could can be empty. empty. |
| Cancel can be invoked during any long-lasting operation.
Stops the operation and restores the (consistent) consistent state present that existed before the long lasting long-lasting operation was started. Cancel can be invoked during any long lasting operation. Furthermore, cancel() can also be invoked when the UP is in state WAITING_FOR_COMMIT or ACTIVATION_STEP_COMPLETED state (without without having a long lasting long-lasting operation in progress). progress. Calling cancel(), cancel() in this state, state orders the ME to restore the state present that existed before the activation procedure was started (PREPARE_COMPLETED). started. The action returns immediately after invocation. The consequences of the action can be tracked via the progressReport attribute. by attribute progressReport. The action returns false if the action is refused by the ME, returns true otherwise. This action can be invoked when the UP state is PREPARE_IN_PROGRESS, VERIFICATION_IN_PROGRESS, ACTIVATION_IN_PROGRESS, ACTIVATION_STEP_COMPLETED, or WAITING_FOR_COMMIT. ME. If the action is invoked in a state where the action has no meaning, the ME is expected to return false. false. In all other cases, it returns true. This action can be invoked when the UP state is PREPARE_IN_PROGRESS, ACTIVATION_IN_PROGRESS, ACTIVATION_STEP_COMPLETED, or WAITING_FOR_COMMIT. |
| Action commit is deprecated, it is recommended to use action confirm.
Stops the activation supervision timer (fallback timer) and confirms the upgrade. The action returns when immediately after invocation. The progress of the action has completed (synchronous). can be tracked by attribute progressReport. The action returns false if the action could not start for any reason, for example, another parallel action is in progress. In all other cases, it returns true. This action can be invoked when the state is WAITING_FOR_COMMIT. WAITING_FOR_COMMIT. The CoreMW implementation of the commit action returns true on success, false on failure. has always been ansynchronous. This is an deviation from the ECIM SwM commit which was an synchronous action. Deprecated: Action has been removed from ECIM SWM 4.2, deprecated in CmwSwM 5.1 |
| Date and time this Upgrade Package instance was created.
is created. |
| The Id (actionId) of the action that have created this UpgradePackage managed object.
The default 0 MO.
Default value denotes 0 shows that the managed element ME does not record this information. |
| Influences the behaviour behavior of the activate() action.
false => There False means there is a breakpoint between each activation step. Activation process stops at each breakpoint. true => Execution shall ignore True means execution ignores breakpoints between activation steps and instead execute executes the end to end end-to-end activation process invoking process. This invokes all activation steps in sequence (assuming sequence, assuming no errors occur). occur. |
| Prepares the Managed Element for the activation of the current upgrade package.
package.
Executing prepare() does not have any negative impact on the in service in-service performance of the Managed Element. Element. The action returns immediately after invocation. The progress of the action can be tracked via the progressReport attribute. by attribute progressReport. The action returns false if the action could not start for any reason (e.g., reason, for example, another parallel action is in progress), otherwise progress. In all other cases, it returns true. true. |
| Represents the progress report (including result) report, including the result, of the ongoing action.
This MO supports only one action to be executed execution at a time. time. |
| The value component of Holds the RDN. name used when identifying the MO. |
| A URI pointing that points to the directory where the UP can be found.
The URI may can be local (e.g., file://data/dir/subdir) or a remote (e.g., ftp://hostname/dir/subdir). local, for example, file://data/dir/subdir. It can also be remote, for example, ftp://hostname/dir/subdir. |
| Used for free-text description. Free-text description of the Upgrade Package. |
| Verifies the ability to activate the current upgrade package.
The action returns immediately after invocation. The progress of the action can be tracked via the progressReport attribute. by attribute progressReport. The action returns false if the action could not start for any reason (e.g., reason, for example, another parallel action is in progress), otherwise progress. In all other cases, it returns true. true. This action can be invoked when the state is PREPARE_COMPLETED. If the action is invoked in a state where the action has no meaning, the ME is expected to return an error message. Calling this message.This action is optional can be called as an option in the whole upgrade procedure. The action can be called more than once if wished. required. |
| Any text describing Textual description of the role/meaning/interpretation activation step.
It can describe the role, meaning, or interpretation of the activation step, or any info information which is useful for to the operator operator. |
| Activation step number, number.The position of the activation step in the activation procedure.
Starting procedure.Starts at 1. |
| old: |
|
|
| new: |
|
| The progress of an ongoing action.
Some actions can have 1+ breakpoints. Breakpoints 1 or more breakpoints.Breakpoints allow an action to be be divide divided into defined steps. A breakpoint is an intentional stop of an (executing) action. Example executing action, for example, the Activate action in the ECIM SwM MOM. The activate action puts an upgrade package into operation. A breakpoint represents a part of the upgrade after upgrade,after which the functionality of the ME can be manually observed. I.e. observed manually.In other words, the breakpoint(s) breakpoints give the operator an option to manually verify manually that the (upgrade) upgrade step has been executed correctly. The ProgressReport MOC models a standard action. This MOC struct has the same attributes as the ProgressReport MOC, plus two extra attributes attributes, step and stepProgressPercentage. step: This attribute stepProgressPercentage.step stores the current execution action Step (number) stepProgressPercentage: This attribue step. stepProgressPercentage stores the Progress Percentage progress percentage of current the currently executing action step. |
| Id of the action.
action. Each action has an action id, which id. The Id is used for querying to query the progress of an action. |
| Name of the invoked action.
(e.g., action, for example, prepare(), verify(), activate() on UpgradePackage MO). MO. |
| Used for logging to log significant messages during execution of an action.
I.e., it It contains information about the "history" history of the execution. This execution.This field contains the log entries as an array. It may can be empty. This empty.This information is for display only; it only. It is not recommended to build any logic on the content of this field. |
| Textual information (description) Description of the "actual state" actual state of the execution, which might can be useful/needed useful or required by NMS.
This information is for display only; it only. It is not recommended to build any logic on the content of this field. |
| Progress of This represents the overall progress for completion of the action.
Range is between 0 and 100. The implementation shall intend to calculate 100.
It calculates the percentage time-wise. (This is preferable, but not compulsory.) with regard to time. |
| Result of completed action.
This action.This field has a value NOT_AVAILABLE if the action is not finished. |
| Textual description of the outcome/result outcome or result of the action containing action.
It contains useful info information for the NMS. E.g., NMS. For example, it can contain an error message if the action failed. failed. This information is for display only; it only. It is not recommended to build any logic on the content of this field. |
| Progress This represents the progress percentage of completion of the currently executing action step.
It goes from 0 to 100 percentage for each and every step. |
| The date and time when the action was completed either successfully or unsuccessfully. |
| The date and time when the current action was started. |
| The date and time when this of the last MO Struct was update. The last updated.
I.e., the last date and time when any attribute changed. |
| IP address to listen for SNMP requests. This is is typically Typically 0.0.0.0, which means that requests on any interface is accepted. |
| old: |
|
|
| new: |
|
| old: |
|
|
| new: |
|
| The Method type of method to use, can used. Can be TRAP or INFORM. |
| Indicates Shows that the fallback capability is not supported. |
| Indicates Shows that the fallback capability is supported. |
| Activation is in progress.
In this state, only the cancel() action may can be called. called. If the cancel() action is called, the UP moves to DEACTIVATION_IN_PROGRESS state. state DEACTIVATION_IN_PROGRESS. If the activation step completes successfully, the UP moves to state ACTIVATION_STEP_COMPLETED state. . |
| The previous activitation activation step completed successfully, but there successfully.
There are still more activation step(s) left. steps left. In this state, only the activate() or the cancel() action may can be called. called. If the cancel() action is called, the UP moves to state DEACTIVATION_IN_PROGRESS state. . If the activate() action is called, the ME starts the activation of the next activation step and the UP moves to state ACTIVATION_IN_PROGRESS state. . If the fallback timer expires in this state, the UP moves to state DEACTIVATION_IN_PROGRESS state. . |
| The upgrade is committed.
The confirmed.The whole upgrad upgrade procedure has completed. |
| The deactivation Deactivation of the UP is in progress.
This may can be a the result of a cancel() action having been called action, or the fallback timer may have has expired. In this state, no action can be called. In At the end of fallback operation, the UP moves back to PREPARE_COMPLETED state. state PREPARE_COMPLETED. |
| The Upgrade Package is initialized.
initialized.
The administrative data and activations activation steps of the UP can be read. In read.In this state, only the prepare() action may can be called. called. |
| Prepare action has successfully finished.
finished successfully.
In this state, only the verify() or the activate() action may can be called. called. If the activate() action is called, the UP moves to state ACTIVATION_IN_PROGRESS state. . |
| Prepare action in progress.
In this state, only the cancel() action may can be called. If the prepare() action completes successfully, the UP moves to state PREPARE_COMPLETED state. . If the prepare() action fails (or fails, or cancel() is called), called, the UP moves back to state INITIALIZED state. . |
| The last activation step completed successfully.
successfully.
The operator has to commit must confirm the upgrade. upgrade. In this state, only the commit() confirm() or the cancel() action may can be called. called. If the cancel() action is called, the UP moves to DEACTIVATION_IN_PROGRESS state. state DEACTIVATION_IN_PROGRESS. If the commit() confirm() action is called, the UP moves to state COMMIT_COMPLETED state. . |
| old: |
|
|
| new: |
|
| Derived string for the specification of a cipher suite list.
Contains colon-delimited (':') cipher strings that can be of any value of the members contained by a Cipher struct. A cipher string indicates an individual cipher or a set of ciphers that use the same protocol version, key exchange etc. The cipher strings can be combined in logical order and operation by character '+'. They can be optionally preceded by either an '!' or a '-' character. Character '!' means that the preceded cipher suite or cipher suite type is permanently deleted from the list. Character '-' means that the preceded cipher suite or cipher suite type is deleted from the list, but any of the cipher suites can be added by later options. They must contain at least one positive expression, that is, without character '!' or '-' in the cipher string, otherwise the filter results in an empty cipher suite list. Cipher strings with special meaning: ALL - all cipher suites except for the NULL encryption ciphers, which must be explicitly enabled. NULL authentication ciphers are included. DEFAULT - all cipher suites except the NULL authentication and NULL encryption ciphers. Example: ALL:!SSLv2:!RSA:!aRSA:!3DES:!DES:!MD5 ALL:!EXP-EDH-RSA-DES-CBC-SHA AES:-kRSA AES:RC4 kEDH+EXPORT:-MD5 ALL:!EXP-EDH-RSA-DES-CBC-SHA AES:-kRSA AES:RC4 kEDH+EXPORT:-MD5 The examples above demonstrate the syntax only and may contain unsupported cipher suites. |
| old: |
|
|
| new: |
|
| old: |
|
|
| new: |
|
| IP address or DNS name of a logical interface. A host may Hosts can have one or more physical hardware network interfaces. Each of these interfaces is interfaces, each associated with an IP address. In addition, TCP/IP software also supports ���loopback��� interfaces (127.0.0.1 interfaces, 127.0.0.1 in IPv4 and ::1 in IPv6), IPv6, which do not use any physical hardware. There is a special IP address for listening on all interfaces (0.0.0.0 interfaces, 0.0.0.0 for IPv4 and ::0 for IPv6). IPv6. A version Version 4 IP address is specified in addresses use dotted quad notation, for example 130.100.92.154. RFC 791 describes the syntax details. A version Version 6 IP address is specified by addresses use 8 groups of 16 bit hexadecimal values separated by colons, for example 2001:0db8:85a3:0000:0000:8a2e:0370:7334. RFC 4291 describes the syntax details. A DNS name is specified as a names must be fully qualified domain name, names, for example myhost.ericsson.com. Internet domain domains are loosely specified but RFC 1034 recommends a syntax. |
| The IpDNSAddress type represents an IP address or a DNS domain name.
A version 4 IP An unicast IPv4 address is presented in three-digit decimal blocks. It is specified in dotted quad notation, for example 130.100.92.154. RFC 791 describes the syntax dotted-quad decimal notation (i.e. three-digit decimal blocks) in detail. A version 6 accordance with RFC791, The blocks are separated by a dot. - The unicast IPV4 address is within range [1-126,128-223].[0-255].[0-255].[0-255], 7-15 characters. - The IP address range 127.0.0.0 ��� 127.255.255.255 is reserved for loopback - The IP address range 0��� 0.255.255.255 are reserved A IPv6 address is specified by 8 groups of 16 bit hexadecimal values separated by colons, for example, 2001:0db8:85a3:0000:0000:8a2e:0370:7334. colons as described in RFC 4291 describes 4291. ��� IPv6 addresses length: 3-39 characters. ��� Valid characters: 0123456789abcdefABCDEF: The format of the syntax embedded IPv4/IPv6 addresses is described in detail. RFC 6052. A DNS domain name is specified in dot separated alphanumeric notation as a fully qualified domain name, for example, myhost.ericsson.com. described in RFC 1034 . The internet domain name consists of one or more parts, called labels, that are delimited by dots. - Domain Name length: 253 characters - Label length: 63 characters - Valid characters: a-z, A-Z, 0,1,2,3,4,5,6,7,8,9, - - The Label���s first character is loosely specified but RFC 1034 recommends a syntax. letter - Labels shall not start or end with a hyphen. - Labels shall not start with a number - Label shall end with a number or a letter. |
| old: | ^((([0-9][1-9])|([1-9][0-9])|[1-9]|1[0-1][0-9]|12[0-6]|12[8-9]|1[3-9][0-9]|2[0-2][0-3])\.)((([2][5][0-5]|([2][0-4]|[1][0-9]|[0-9])?[0-9])\.){2})([2][5][0-5]|([2][0-4]|[1][0-9]|[0-9])?[0-9])$|^\s*((([0-9A-Fa-f]{1,4}:){7}(([0-9A-Fa-f]{1,4})|:))|(([0-9A-Fa-f]{1,4}:){6}(:|((25[0-5]|2[0-4][0-9]|[01]?[0-9]{1,2})(\.(25[0-5]|2[0-4][0-9]|[01]?[0-9]{1,2})){3})|(:[0-9A-Fa-f]{1,4})))|(([0-9A-Fa-f]{1,4}:){5}((:((25[0-5]|2[0-4][0-9]|[01]?[0-9]{1,2})(\.(25[0-5]|2[0-4][0-9]|[01]?[0-9]{1,2})){3})?)|((:[0-9A-Fa-f]{1,4}){1,2})))|(([0-9A-Fa-f]{1,4}:){4}(:[0-9A-Fa-f]{1,4}){0,1}((:((25[0-5]|2[0-4][0-9]|[01]?[0-9]{1,2})(\.(25[0-5]|2[0-4][0-9]|[01]?[0-9]{1,2})){3})?)|((:[0-9A-Fa-f]{1,4}){1,2})))|(([0-9A-Fa-f]{1,4}:){3}(:[0-9A-Fa-f]{1,4}){0,2}((:((25[0-5]|2[0-4][0-9]|[01]?[0-9]{1,2})(\.(25[0-5]|2[0-4][0-9]|[01]?[0-9]{1,2})){3})?)|((:[0-9A-Fa-f]{1,4}){1,2})))|(([0-9A-Fa-f]{1,4}:){2}(:[0-9A-Fa-f]{1,4}){0,3}((:((25[0-5]|2[0-4][0-9]|[01]?[0-9]{1,2})(\.(25[0-5]|2[0-4][0-9]|[01]?[0-9]{1,2})){3})?)|((:[0-9A-Fa-f]{1,4}){1,2})))|(([0-9A-Fa-f]{1,4}:)(:[0-9A-Fa-f]{1,4}){0,4}((:((25[0-5]|2[0-4][0-9]|[01]?[0-9]{1,2})(\.(25[0-5]|2[0-4][0-9]|[01]?[0-9]{1,2})){3})?)|((:[0-9A-Fa-f]{1,4}){1,2})))|(:(:[0-9A-Fa-f]{1,4}){0,5}((:((25[0-5]|2[0-4][0-9]|[01]?[0-9]{1,2})(\.(25[0-5]|2[0-4][0-9]|[01]?[0-9]{1,2})){3})?)|((:[0-9A-Fa-f]{1,4}){1,2}))))(%.+)?\s*$|^(([a-zA-Z]|[a-zA-Z][a-zA-Z0-9\-]*[a-zA-Z0-9])\.)*([A-Za-z]|[A-Za-z][A-Za-z0-9\-]*[A-Za-z0-9])$ | |
| new: | ^(((|[1-9]|[1-9][0-9]|12[012345689]|1[013456789][0-9]|2[0-1][0-9]|22[0-3])\.)(([0-9]|[0-9][0-9]|[0-1][0-9][0-9]|2[0-4][0-9]|25[0-5])\.){2})([0-9]|[0-9][0-9]|[0-1][0-9][0-9]|2[0-4][0-9]|25[0-5])$|^((([0-9A-Fa-f]{1,4}:){1,5}:((25[0-5]|2[0-4][0-9]|[01]?[0-9]{1,2})(\.(25[0-5]|2[0-4][0-9]|[01]?[0-9]{1,2})){3})?)|(([0-9A-Fa-f]{1,4}:){6,7}:)|(([0-9A-Fa-f]{1,4}:){6}((25[0-5]|2[0-4][0-9]|[01]?[0-9]{1,2})(\.(25[0-5]|2[0-4][0-9]|[01]?[0-9]{1,2})){3}))|(([0-9A-Fa-f]{1,4}:){6}:[0-9A-Fa-f]{1,4})|(([0-9A-Fa-f]{1,4}:){5}(:[0-9A-Fa-f]{1,4}){1,2})|(([0-9A-Fa-f]{1,4}:){4}(:[0-9A-Fa-f]{1,4}(:(25[0-5]|2[0-4][0-9]|[01]?[0-9]{1,2})(\.(25[0-5]|2[0-4][0-9]|[01]?[0-9]{1,2})){3})?))|(([0-9A-Fa-f]{1,4}:){4}(:[0-9A-Fa-f]{1,4}){2,3})|((([0-9A-Fa-f]{1,4}:){3}(:[0-9A-Fa-f]{1,4}){1,2})(:(25[0-5]|2[0-4][0-9]|[01]?[0-9]{1,2})(\.(25[0-5]|2[0-4][0-9]|[01]?[0-9]{1,2})){3})?)|(([0-9A-Fa-f]{1,4}:){3}(:[0-9A-Fa-f]{1,4}){3,4})|(([0-9A-Fa-f]{1,4}:){2}(:[0-9A-Fa-f]{1,4}){1,3}(:(25[0-5]|2[0-4][0-9]|[01]?[0-9]{1,2})(\.(25[0-5]|2[0-4][0-9]|[01]?[0-9]{1,2})){3})?)|(([0-9A-Fa-f]{1,4}:){2}(:[0-9A-Fa-f]{1,4}){4,5})|(([0-9A-Fa-f]{1,4}:)(:[0-9A-Fa-f]{1,4}){1,4}(:(25[0-5]|2[0-4][0-9]|[01]?[0-9]{1,2})(\.(25[0-5]|2[0-4][0-9]|[01]?[0-9]{1,2})){3})?)|(([0-9A-Fa-f]{1,4}:)(:[0-9A-Fa-f]{1,4}){5,6})|((:(:[0-9A-Fa-f]{1,4}){1,5})(:(25[0-5]|2[0-4][0-9]|[01]?[0-9]{1,2})(\.(25[0-5]|2[0-4][0-9]|[01]?[0-9]{1,2})){3})?)|(:(:[0-9A-Fa-f]{1,4}){6,7})|(([0-9A-Fa-f]{1,4}:){7}[0-9A-Fa-f]{1,4})|(((::FFFF)|(0:0:0:0:0:FFFF))(:(25[0-5]|2[0-4][0-9]|[01]?[0-9]{1,2})(\.(25[0-5]|2[0-4][0-9]|[01]?[0-9]{1,2})){3})))$|^(([a-zA-Z]|[a-zA-Z][a-zA-Z0-9\-]*[a-zA-Z0-9])\.)*([A-Za-z]|[A-Za-z][A-Za-z0-9\-]*[A-Za-z0-9])$|^ $ |
| Represents the international standard for the representation of Distinguished Names to be used with the LDAP protocol (RFC 4514).
4514). The string representation of the Distinguished Name structure is as follows: follows: distinguishedName = [ relativeDistinguishedName ( COMMA relativeDistinguishedName ) ] ] relativeDistinguishedName = attributeTypeAndValue ( PLUS attributeTypeAndValue ) ) attributeTypeAndValue = attributeType EQUALS attributeValue attributeValue attributeType = descr/numericoid descr/numericoid attributeValue = string/hexstring |
| old: | ^([0-9\.]*)$ | |
| new: | ^([\.]?[0-9]+)+$ |