| Managed Object Model 2/155 54-4/AXM10104/1-V1 Uen J |
All Differences in
| Name | : MrfMOM | |
| Version | : 2 | |
| Release | : 6 | |
| Correction | : 0 | |
| Compared to |
| Name | : MrfMOM | |
| Version | : 2 | |
| Release | : 5 | |
| Correction | : 0 | |
| The Secure Hash Algorithm (SHA) fingerprint of the certificate to be installed.
The fingerprint is checked against the fingerprint calculated on the installed file. If fingerprint verification is not required, the 'NULL' string has to be provided. The hash must be calculated by the SHA algorithm indicated in fingerprintSupport of the CertMCapabilities MO. |
| The password section of the URI.
If a password is not required, the 'NULL' string must be provided. URI. |
| The trusted cerificate of the RA or CA used for enrollment authentication.
Represents the certificate by the DN of the appropriate TrustedCertificate MO. The RA or CA certificate provided in the PKI response is authenticated by this trusted certificate. certificate. If this attribute has any value, the attribute enrollmentCaFingerprint is ignored. |
| The URI of the enrollment server.
The URI consists of a protocol, an IP or DNS address and an optional port number. Specify the optional port designation by appending a colon followed by the port number to the host part, for example, 192.168.33.27:8080. If no port number is provided, the default port is used. For SCEP, the URI contains the relative URI of the enrollment CA HTTP Common Gateway interface (CGI) script path, which is the resource identifier of the resource on the server which will process the enrollment request. Example for CMP: http://192.168.33.27:8080 or cmp://192.168.33.27 cmp://192.168.33.27 Example for SCEP: http://192.168.33.27:8080/cgi-bin/pkiclient.exe |
| This is The root MOC of the fault management fragment and is used to manage the stateful alarms. Fault Management branch. |
| Internal Id to unique identify MOC instance. Holds the name used when identifying the MO. |
| The interval in seconds, with which a heartbeat event will be notification is sent to all alarm and alert consumers. |
| This attribute contains a The timestamp of when any Fm alarm has was last changed. With the Fm:lastSequenceNo, this attribute, an external system can determine if a resynchronization operation is needed, such as following a loss and restore of a communications link. |
| The last used sequence number for an alarm state change notification. The sequence numbers are consecutive. With the Fm:lastChanged, this attribute, an external system can determine if a resynchronization operation is needed, such as following a loss and restore of a communications link. |
| old: |
|
|
| new: |
| old: |
|
|
| new: |
| Shows the number of active alarms with perceived severity 'major'. ���major���. |
| old: |
|
|
| new: |
| Shows the number of active alarms with perceived severity 'minor'. ���minor���. |
| old: |
|
|
| new: |
| Shows the number of active alarms with perceived severity 'warning'. ���warning���. |
| old: |
|
|
| new: |
| This attribute shows Shows the total number of currently active alarms, i.e. alarms. This corresponds to the the total number of instantiated FmAlarm objects. |
| old: |
|
|
| new: |
| An FmAlarm instance models represents an active alarm. An alarm type that is reported at a specific time and for persistent indication of a specific managed object instance. The FmAlarm MOC will get fault that clears only when the static data from the FmAlarmType . The Managed alarming object instance and alarm type make the alarm instance unique within a managed element. FmAlarmType:majorType and FmAlarmType:minorType are the two key attributes used by an alarming object to identify the Alarm Type. Assignment of values for each alarm type shall be centrally administered. triggering condition has been resolved. |
| This attribute is used to define the current The perceived severity level. Attributes values are aligned to ITU-T X.733 Perceived Severity values of the alarm. It may change during the alarm's lifetime. Specification: RFC3877 |
| This attribute contains further Further information in text format that is appended to an alarm. about the problem. The information is provided by represented as a set of data structures with two items of information, an identifier and a value. It may change during the alarming object. alarm's lifetime. |
| This attribute gets its value from Extra information about the FmAlarmType:additionalText attribute. For alarm. It may change during the attribute description see FmAlarmType:additionalText attribute. alarm's lifetime. |
| This attribute gets its value from General category for the FmAlarmType:eventType attribute. For the attribute description see FmAlarmType:eventType attribute. alarm. Specification: ITU-T X.733 X.736 |
| Unique Id for MO instance. Holds the name used when identifying the MO. |
| This attribute is the The timestamp of when the alarm was last updated, i.e. updated. This is set at alarm status information change or severity change. |
| The attributes majorType and minorType are the two key attributes used to identify the Alarm Type applicable to the raised alarm. alarm type. |
| This attribute gets its value from Qualifies and provides further information on the FmAlarmType:probableCause attribute. For reason for the attribute description see FmAlarmType:probableCause attribute. event. A standard set of probableCause values is provided in the ERICSSON-ALARM-PC-MIB. |
| This attribute is the notification A unique identity for this object instance. every notification sent. This identity changes at every notification, that is, severity change and information change. It is not the same as the fmAlarmId as multiple notifications may be sent for one alarm instance. This changes at every notification (i.e. severity change, alarm clear, etc). |
| This attribute is The distinguished name of the DN pointer towards the alarming object. |
| This attribute gets its value from Provides further refinement to the FmAlarmType:specificProblem attribute. For the attribute description see FmAlarmType:specificProblem attribute. information given by probableCause. Can be used to find an associated operating instruction (OPI). |
| FmAlarmModel is a class that represents all alarm types (FmAlarmType) that can be generated from the managed element. This MOC is used a container for grouping FM Alarm alarm types. |
| Unique Id for MO instance Holds the name used when identifying the MO. |
| An Alarm type is a A specific kind of alarm that can be reported, for example "power failure". Within Ericsson this maps to specific problem. In an X.733 context it maps to event type, probable cause, and specific problem. The Ericsson ECIM FM MOC uses integers major and minor to uniquely identify Fm alarm types and assumes a 1:1 mapping to textual specific problems. The same principle is used for Alert alert types as is for Alarm types. The FmAlarmType MOC is used to model alarm and alert types. FmAlarmTypes are predefined Alarm types that are stored in FmAlarmType libraries. The predefined FmAlarmTypes contain all the data for a specific alarm type (i.e. Power failure). They are not considered as MOCs in ECIM. They are a predefined alarm type instance. There is however one specific FmAlarmType MOC. Refer to ECIM Tool-Chain (ET) User Guide (2/1553-LXA 119 613/3 ). The FmAlarmTypes are stored as XML files in the data model. Some applications may extend the model to instantiate FmAlarmTypes. This could be done for application specific purposes. NMS only reads FmAlarmTypes in XML format. |
| this attribute is used by the application designer when creating an Alarm type to specify extra Extra information that would not be contained in by other FmAlarmType attributes. |
| This is a general General category for the alarm or alert type. The allowed values are defined by ITU-T X.733 and X.736.
type.
Specification: ITU-T X.733, X.736 |
| Unique Id for MO instance Holds the name used when identifying the MO. |
| This True indicates whether the Alarm Type is an alarm (i.e. has state) or an alert (i.e. has no state). TRUE indicates a stateful alarm and FALSE indicates a stateless alarm. False indicates alert (stateless alarm). |
| The attributes majorType and minorType are the two key attributes used to identify the Alarm Type. Ericsson practice is to define alarm types according to a combination of event type, probable cause and specific problem. Assignment of values for each alarm type shall be centrally administered. type. |
| The attributes majorType and minorType are the two key attributes used to identify the Alarm Type. Ericsson practice is to define alarm types according to a combination of event type, probable cause and specific problem. Assignment of values for each alarm type shall be centrally administered. type. |
| This represents A list of the Managed Object classes that can raise this alarm type. This attribute contains a comma seperated list of Managed Object Classes classes types that use this AlarmType . alarm type. It is for information only. Deprecated: This attribute shall be empty in the alarm type library has no purpose and is filled out not used by the application designer when an alarm type is put into an instance model. See ECIM Tool-Chain User Guide 2/1553-LXA 119 613/3. anyone. |
| This attribute qualifies Qualifies and provides further information on the reason for the event. A standard set of probableCause values is provided in the ERICSSON-ALARM-PC-MIB - 4/196 03-CXC 172 7549 rev A. ERICSSON-ALARM-PC-MIB. Specification: ITU-T M.3100, X.733, X.736; ETSI GSM 12.11. |
| This provides Provides further refinement to the information given in by probableCause. The specificProblem is a unique string i.e no other Alarm type can have the same specificProblem value. Can be used to find an associated operating instruction (OPI). |
| The top-level class in the Common Information Model is the Managed Element root Managed Object Class (MOC).
Class.
From this class, all model entities are contained. The MOC Managed Object Class (MOC) has attributes that provide information on the Managed Element Identity, primary location and the products it contains. |
| Deprecated. Difference between the value of the localDateTime attribute and UTC (Coordinated Universal Time). UTC. Deprecated: Deprecated at version 2.3. Functionality replaced by TimeM model.��� |
| It provides additional naming context that allows the managed objects to be partitioned into logical domains.
A Distingushed Name (DN) is defined by 3GPP TS 32.300 32.300, which splits the DN in into a DN Prefix and Local DN, for example DN e.g. DN format: dnPrefix=<DN Prefix>, localDn =<Local DN> Fault Management: dnPrefix does not impact Fault Management, since an NMS recognises a Managed Element by IP address Performance Management (PM): The dnPrefix is present in the PM Data file, Result Output Period (ROP) file, if the dnPrefix attribute is specified, that is, not an empty string. Example: DC=ericsson.se,g3SubNetwork=Sweden Example: DC=ericsson.se,g3SubNetwork=Sweden |
| Deprecated. This is the local date and time for the Managed Element.
The following format is used: YYYY-MM-DDThh:mm:ss The meaning of each field is as follows: YYYY is a 4-digit year. = four digit year MM is the = two digit month within the year (starting with 01). (01=January, etc.) DD is the = two digit day within the of month (starting with 01). (01 through 31) T is used as = time designator to indicate the (shows start of the time of day component in the expression. component) hh is the = two digits of hour within the day (24-hour clock, starting with 00). (00 through 23, AM/PM not allowed) mm is the = two digits of minute within the hour (starting with 00). (00 through 59) ss is the = two digits of second within the minute (starting with 00). (00 through 59, leap second not allowed) The hyphen [-] and the colon [:] are used as separators within the date and time of day expressions, respectively. Deprecated: Deprecated at version 2.3. Functionality replaced by TimeM model.��� Specification: ISO 8601:2004(E) |
| The value component of Holds the RDN.
The allowed character set is defined by 3GPP TS 32.300. name used when identifying the MO. |
| The type of product being managed.
managed.
For example the type could be RBS or CSCF. |
| Contains product information for the Managed Element and its Managed Function(s).
Functions.
This attribute is deprecated. Deprecated: |
| The release of the type of product type specified by the attribute managedElementType.
managedElementType.
It commonly contains the Managed Element release e.g. release, for example L12.0, 13A, R1A |
| DEPRECATED. This is the timeZone that in which the Managed Element resides in.
resides.
The possible values for this attribute are defined in the public-domain zoneinfo (or Olson) database. or Olson database. Locations are identified by a string indicating the continent or ocean and then the name of the location, which is typically the largest city within the region. See http://www.twinsun.com/tz/tz-link.htm http://www.iana.org/time-zones for more information. information. Example: Europe/Stockholm Europe/Stockholm. Deprecated: Deprecated at version 2.3. Functionality replaced by TimeM model. |
| The enrollment poll timer in minutes.
If the time indicated by this timer elapses before the enrollment is finished, the enrollment fails. No value means the timer is disabled. Used only for online enrollment. |
| Installs a node credential or certificate from the specified Uniform Resource Identifier (URI).
If the container file is in PKCS#12 format, the action implicitly starts an offline enrollment. If the file is a certificate in Privacy Enhanced Mail (PEM) or Distinguished Encoding Rules (DER) format, this action closes the ongoing offline enrollment process started by the startOfflineCsrEnrollment action. The action can be invoked if the enrollmentSupport attribute of the CertMCapabilites MO indicates that offline enrollment is supported. Chain certificates are imported from PEM formatted file or PKCS#12 container file. For a container file in PKCS#12 format, the The action can be invoked if there is no other action in progress on this MO. For a certificate file in PEM or DER format, the action can be invoked if there enrollmentSupport attribute of the CertMCapabilities MO indicates that offline enrollment is a startOfflineCsrEnrollment action in progress on this MO. supported. For a container file in PKCS#12 format, the action can be invoked if there is no other action in progress on this MO, and the URI scheme is a secure file transfer protocol, or points to a local file. For a certificate file in PEM or DER format, the action can be invoked if there is a startOfflineCsrEnrollment action in progress on this MO. The action returns immediately after invocation. The progress of the action can be tracked via the enrollmentProgress attribute. The action returns with TRUE after successful invocation, otherwise it returns with FALSE. The generic URI syntax is defined by RFC 3986. Example: sftp://myuser@myhostname.ericsson.local/dir/subdir/file sftp://myuser@myhostname.ericsson.local/dir/subdir/certificate Example: http://myhostname.ericsson.local/dir/subdir/certificate |
| The password for decrypting the PKCS#12 container file.
If the action is called to install a certificate in Privacy Enhanced Mail (PEM) or Distinguished Encoding Rules (DER) format to finish a running enrollment process, the value of password has to be 'NULL'. file. |
| The Secure Hash Algorithm (SHA) fingerprint of the certificate to be installed.
The fingerprint is checked against the fingerprint calculated on the installed file. If the verification of the fingerprint is not required, the 'NULL' string must be provided. The hash must be calculated by the SHA algorithm indicated in fingerprintSupport of the CertMCapabilities MO. |
| This parameter contains a URI assumed to point to the certificate or credential container file.
The generic Uniform Resource Identifier (URI) syntax is defined by RFC 3986. Example: sftp://myuser@myhostname.ericsson.local/dir/subdir/file Example: http://myhostname.ericsson.local/dir/subdir/certificate The URI must not contain any password. The password shall be provided in the second parameter of this action. The URI may be local relative (e.g. data/dir/subdir/file), or local absolute (e.g. file:///data/dir/subdir/file), or remote (e.g. sftp://user@hostname/dir/subdir/file) or remote relative (e.g. sftp://user@hostname/~/cert.pem). If the URI is local relative, the file is expected to be under directory path indicated by the localFileStorePath attribute in the CertM MO. |
| The password part of the Uniform Resource Identifier (URI).
If a password is not required, the 'NULL' string has to be provided. (URI). |
| Specifies the key type and length that is used for the next enrollment. enrollment.
Mandatory for actions startOfflineCsrEnrollment or startOnlineEnrollment. For the supported key types see CertMCapabilities MO keySupport attribute. Deprecated key types are not recommended for new enrollments. |
| Starts a manual enrollment procedure.
Creates a PKCS#10 Certificate Signing Request (CSR) that is stored at the specified local Uniform Resource Identifier URI. A file transfer service can be used to fetch the CSR file from the ME. The action can be invoked if the enrollmentSupport attribute of the CertMCapabilites CertMCapabilities MO indicates that offline CSR-based enrollment is supported. The action uses attributes subjectName and keyInfo attributes as inputs. If no other action is in progress on this MO, the action can be invoked and it returns immediately after invocation. The action progress can be tracked via the enrollmentProgress attribute. The action returns with TRUE after successful invocation, otherwise it returns with FALSE. |
| The password section of the Uniform Resource Identifier (URI).
If a password is not required, the 'NULL' string must be provided. (URI). |
| Starts the online enrollment process.
For initial enrollment If a vendor credential is not available, a challengePassword must be provided. provided for initial enrollments. Otherwise, the active vendor credential, indicated in the CertM MO, or the existing valid node credential signs the PKI request. The action can be invoked if If the enrollmentSupport attribute of the CertMCapabilites CertMCapabilities MO indicates that online enrollment is supported. supported, the action can be invoked. As inputs, the action uses subjectName, keyInfo, enrollmentServerGroup and enrollmentAuthority attributes. If no other action is in progress on this MO, the action can be invoked and it returns immediately after invocation. Action progress can be tracked via the enrollmentProgress attribute. The action returns with TRUE after successful invocation, otherwise it returns with FALSE. |
| This is model has a container class for all common OAM purpose to group the management of the system functions provided by of the Managed Element.
Examples of these functions include Fault Management, Performance Management, System Management and Heartbeat Management. |
| The value component of Holds the RDN.
The allowed character set is defined by 3GPP TS 32.300. name used when identifying the MO.
|
| The value component of Holds the RDN.
The allowed character set is defined by 3GPP TS 32.300. name used when identifying the MO.
|
| Indicates the trust categories this trusted certificate belongs to.
Contains the Distinguished Names of the TrustCategory Managed Objects. Deprecated: Deprecated in version 3.0. Restrictive to TrustCategory objects. Replaced by reservedBy. |
| This MO represents Represents a tone as used by the Tone Sender (TS) service in the node. An instance of this MO exists for each tone type used. The MO instances are created automatically by the system when the ToneSenderService MO instance is created. An instance of this MO exists for each tone type used. The MO instances are created automatically by the system when the ToneSenderService MO instance is created. The Relative Distinguished Name (RDN) for this MO type is: TsTone=<toneId> |
| Deprecated, Contains product information for a Managed Element and Managed Function(s).
This entity is deprecated. ManagedFunction(s).
Replaced by ProductData |
| The Common product designation is the common name for the product. name. |
| The product number in Ericsson's Ericsson ABC format. See format.
For information, refer to Ericsson Corporate Basic Standards for information. Standards. |
| The product revision in the form R[1-9][A-Z]. See R[1-9][A-Z].
For information, refer to Ericsson Corporate Basic Standards for information. Standards. |
| The certificate was revoked by a trusted CA. Deprecated: Deprecated in version 3.0. Improper state descriptor for local certificates. |
| This is a general General category for the alarm or alert type. The allowed values are defined by ITU-T X.733 and X.736. alarm. |
| Indicates the key type and length in bits.
This enumeration supports Rivest Shamir Adleman (RSA) and Elliptic Curve Digital Signature Algorithm (ECDDSA). (ECDSA). |
| A key generated for the ECDSA algorithm with bit-length ranging from 160 bits to 223 bits. P-160 curve. Deprecated: Improperly specified key type. |
| A key generated for the ECDSA algorithm with bit-length ranging from 224 bits to 255 bits. P-224 curve. Deprecated: Improperly specified key type. |
| A key generated for the ECDSA algorithm with bit-length ranging from 256 bits to 383 bits. P-256 curve. Deprecated: Improperly specified key type. |
| A key generated for the ECDSA algorithm with bit-length ranging from 384 bits to 511 bits. P-384 curve. Deprecated: Improperly specified key type. |
| A key generated for the ECDSA algorithm with bit-length of at least 512 bits. P-512 curve. Deprecated: Improperly specified key type. |
| 1024-bit long key generated for the RSA algorithm. Deprecated: Outdated key type. |
| The ENUM values are aligned to ERICSSON-ALARM-MIB numbering. The Indeterminiate severity level alarms (or alerts) are not supported as per Generic OaM Requirements (FM10).
The ericsson Alarm MIB is compliant with the IETF understanding of the ITU X.733.
SnmpItuAlarmPercSeverity:
DESCRIPTION "The perceived severity of the possible alarm as specified in [X.733] and [X.736]." SYNTAX INTEGER {cleared (1), indeterminate (2), critical (3), major (4), minor (5), warning (6)} serverities. |
| 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 The examples above demonstrate the syntax only and may contain unsupported cipher suites. |
| Represents the International Standard international standard for the representation of date and time ( ISO 8601) .
8601).
The string format is "YYYY-MM-DDThh:mm:ss.SSSZ" (excluding quotes). A DateTime string consists of a date part, a time part, and an optional time zone information part. The time zone part may be a "Z" "Z", representing UTC the Coordinated Universal Time (UTC) time zone (equals to +00) or a time zone offset (e.g., (for example, +02:00). If the time zone part is not present, the DateTime value represents local time. The following pattern describes the DateTime format in detail: format: YYYY-MM-DDThh:mm:ss[.S+][Z|+-hh:mm] Where: YYYY = four Four digit year MM = two Two digit month (01=January, etc.) and so on) DD = two Two digit day of month (01 through 31) T = time Time designator (shows start of time component) hh = two Two digits of hour (00 through 23, AM/PM not allowed) mm = two Two digits of minute (00 through 59) ss = two Two digits of second (00 through 59, leap second not allowed) S+ = one One or more digits of decimal fraction of a second Z = time is Coordinated Universal Time (UTC) is UTC +- = + or - character indicating positive or negative offset to UTC DateTime values are compliant with ISO 8601 "Representation of dates and times" but are restricted according to RFC 3339 "Date and Time on the Internet: Timestamps". The DateTime format is further restricted: restricted as follows: - T and Z designators are upper case. - . (dot) is used to indicate start of fractions of seconds (ISO 8601 also allows comma) |
| old: | ^([0-9]{4})-(1[0-2]|0[1-9])-(0[1-9]|[1|2][0-9]|3[0-1])T(0[0-9]|1[0-9]|2[0-3]):([0-5][0-9]):([0-5][0-9])([\.][0-9]+)*(([\+|\-](0[0-9]|1[0-9]|2[0-4])(:[0-5][0-9])?)|(Z)?)$ | |
| new: | ^([0-9]{4})-(1[0-2]|0[1-9])-(0[1-9]|[1|2][0-9]|3[0-1])T(0[0-9]|1[0-9]|2[0-3]):([0-5][0-9]):([0-5][0-9])([\.][0-9]+){0,1}(([\+|\-](0[0-9]|1[0-9]|2[0-4])(:[0-5][0-9])?)|(Z)?)$ |
| Represents the international standard for the representation of local date and time ( ISO 8601) .
(ISO 8601).
The following pattern describes the DateTimeWithoutOffset format in detail: format: YYYY-MM-DDThh:mm:ss[.S+] Where: YYYY = four Four digit year MM = two Two digit month (01=January, etc.) and so on) DD = two Two digit day of month (01 through 31) T = time Time designator (shows start of time component) hh = two Two digits of hour (00 through 23, AM/PM not allowed) mm = two Two digits of minute (00 through 59) ss = two Two digits of second (00 through 59, leap second not allowed) S+ = one One or more digits of decimal fraction of a second DateTimeWithoutOffset values are compliant with ISO 8601 (Representation "Representation of dates and times) times" but are restricted according to RFC 3339 (Date "Date and Time on the Internet: Timestamps). Timestamps". The DateTimeWithoutOffset format is further restricted: restricted as follows: - T designator is upper case. - . (dot) is used to indicate start of fractions of seconds (ISO 8601 also allows comma) |
| old: | ^([0-9]{4})-(1[0-2]|0[1-9])-(0[1-9]|[1|2][0-9]|3[0-1])T(0[0-9]|1[0-9]|2[0-4]):([0-5][0-9]):([0-5][0-9])([\.][0-9]+)*$ | |
| new: | ^([0-9]{4})-(1[0-2]|0[1-9])-(0[1-9]|[1|2][0-9]|3[0-1])T(0[0-9]|1[0-9]|2[0-3]):([0-5][0-9]):([0-5][0-9])([\.][0-9]+){0,1}$ |
| Time zone difference between the local current time and UTC (Coordinated Coordinated Universal Time).
Time (UTC).
The following format shall be used is as follows: [+/-]hh:mm It is expressed as positive (i.e. (that is, with the leading plus sign [+]) if the local time is ahead of or equal to UTC of day and as negative (i.e. (that is, with the leading minus sign [-]) if it is behind UTC. the UTC of day. Example: +01:00 |
| A derived string type that allows hexadecimal digits.
The string must be entered in two-digit groups separated by colons. For example: b7:a8:c6:d5:43:fa:50:43 'b7:a8:c6:d5:43:fa:50:43' |
| Probable cause as specified in ITU recommendations M.3100, X.733 and X.736, and in ETSI recommendation GSM 12.11. This attribute value corresponds a Probable cause number. Reference the Ericsson Alarm Probable Cause MIB 4/196 03-CXC 172 7549 (Rev. A) recommendations. The values are aligned to see the valid values for probable causes. ERICSSON-ALARM-MIB. |