Status in source: current.
Technical details
{
"smi_kind": "NOTIFICATION-TYPE",
"definition": [
"adslAtucDspUnexpectedResponseTrap",
"NOTIFICATION-TYPE",
"OBJECTS",
"{",
"managedObjectClass",
",",
"managedObjectInstance",
",",
"sequenceNumber",
",",
"perceivedSeverity",
",",
"eventTime",
",",
"eventTypePem",
",",
"probableCause",
",",
"messageId",
",",
"errorCode",
"}",
"STATUS",
"current",
"DESCRIPTION",
"\"DSP replies with an unexpected result code such as: 'unknown application id', 'unknown command id', 'wrong message format', 'request data not valid' or 'request cannot be performed in current state'. This should not happen and comes from either incompatible SW versions or state mismatch between UC and DSP due to internal SW problems. If necessary a LinkDown should proceed this fault.The line will be reset and possibly taken into service again. In case too many line resets have been performed a DSP Communication Failure shall be triggered and the DSP reset and reloaded. The operator must change the configuration settings. Valid from: EDA 1.1R2A Parameters 1: Managed object class IP DSLAM Port 2: Managed object ID (MAC + PortNo) 3: Sequence number (Alarm sequence number) 4: Perceived severity Minor 5: Event time (Timestamp is retrieved from a SNTP server) 6: Event type Equipment 7: Probable cause UnexpectedInformation 8: Message ID (Internal message number) 9: Err Code (Additional error information) \"",
"::=",
"{",
"adslAtucXTrapsEntry",
"9",
"}"
],
"syntax_tree": [
[
"Objects",
[
"managedObjectClass",
"managedObjectInstance",
"sequenceNumber",
"perceivedSeverity",
"eventTime",
"eventTypePem",
"probableCause",
"messageId",
"errorCode"
]
],
[
"Status",
"current"
],
[
"DESCRIPTION",
"DSP replies with an unexpected result code such as: 'unknown application id', 'unknown command id', 'wrong message format', 'request data not valid' or 'request cannot be performed in current state'. This should not happen and comes from either incompatible SW versions or state mismatch between UC and DSP due to internal SW problems. If necessary a LinkDown should proceed this fault.The line will be reset and possibly taken into service again. In case too many line resets have been performed a DSP Communication Failure shall be triggered and the DSP reset and reloaded. The operator must change the configuration settings. Valid from: EDA 1.1R2A Parameters 1: Managed object class IP DSLAM Port 2: Managed object ID (MAC + PortNo) 3: Sequence number (Alarm sequence number) 4: Perceived severity Minor 5: Event time (Timestamp is retrieved from a SNTP server) 6: Event type Equipment 7: Probable cause UnexpectedInformation 8: Message ID (Internal message number) 9: Err Code (Additional error information)"
],
null
]
}