Status in source: deprecated.
Technical details
{
"smi_kind": "NOTIFICATION-TYPE",
"definition": [
"nonFatalSoftwareError",
"NOTIFICATION-TYPE",
"OBJECTS",
"{",
"managedObjectClass",
",",
"managedObjectInstance",
",",
"sequenceNumber",
",",
"perceivedSeverity",
",",
"eventTime",
",",
"eventTypePem",
",",
"probableCause",
",",
"processName",
",",
"processState",
",",
"fileName",
",",
"lineNo",
",",
"errorCode",
",",
"errorData",
"}",
"STATUS",
"deprecated",
"DESCRIPTION",
"\"A non-fatal SW error has been detected on the device. This type of software error is normally not fatal for your system, It could be a configuration error or a minor problem in the software, so do not panic if this alarm is seen. Corrective Actions: - Save the alarm information to a file, e.g. using a screenshot. It has to show all the trap parameters. - Give a brief explanation to how the error was provoked. If it can be provoked again, then it is important for the Ericsson support team to know how this is done. - Create a trouble report, which includes the log files, and send it to Ericsson support. Deprecated from: EDA 1.1 R2A Parameters 1: Managed object class IPDSLAM 2: Managed object ID [MAC] 3: Sequence number [Alarm sequence number] 4: Perceived severity Major 5: Event time [Timestamp is retrieved from a SNTP server] 6: Event type ProcessingErrorAlarm 7: Probable cause SoftwareError 8: Process name [Name of DMAPI task] 9: Process state [DMAPI task state] 10: File name [The file name from where the alarm was sent] 11: Line no [The line number in the specified file] 12: Error code [Additional error information] 13: Error data [Additional data related to the error - hex bytes] \"",
"::=",
"{",
"traps",
"5",
"}"
],
"syntax_tree": [
[
"Objects",
[
"managedObjectClass",
"managedObjectInstance",
"sequenceNumber",
"perceivedSeverity",
"eventTime",
"eventTypePem",
"probableCause",
"processName",
"processState",
"fileName",
"lineNo",
"errorCode",
"errorData"
]
],
[
"Status",
"deprecated"
],
[
"DESCRIPTION",
"A non-fatal SW error has been detected on the device. This type of software error is normally not fatal for your system, It could be a configuration error or a minor problem in the software, so do not panic if this alarm is seen. Corrective Actions: - Save the alarm information to a file, e.g. using a screenshot. It has to show all the trap parameters. - Give a brief explanation to how the error was provoked. If it can be provoked again, then it is important for the Ericsson support team to know how this is done. - Create a trouble report, which includes the log files, and send it to Ericsson support. Deprecated from: EDA 1.1 R2A Parameters 1: Managed object class IPDSLAM 2: Managed object ID [MAC] 3: Sequence number [Alarm sequence number] 4: Perceived severity Major 5: Event time [Timestamp is retrieved from a SNTP server] 6: Event type ProcessingErrorAlarm 7: Probable cause SoftwareError 8: Process name [Name of DMAPI task] 9: Process state [DMAPI task state] 10: File name [The file name from where the alarm was sent] 11: Line no [The line number in the specified file] 12: Error code [Additional error information] 13: Error data [Additional data related to the error - hex bytes]"
],
null
]
}