Status in source: current.
Technical details
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"tmnxOamPmNotifThrType",
"OBJECT-TYPE",
"SYNTAX",
"INTEGER",
"{",
"delay",
"(",
"1",
")",
",",
"lossAvgFlr",
"(",
"2",
")",
",",
"lossChli",
"(",
"3",
")",
",",
"lossHli",
"(",
"4",
")",
",",
"lossUnavail",
"(",
"5",
")",
",",
"lossUndetAvail",
"(",
"6",
")",
",",
"lossUndetUnavail",
"(",
"7",
")",
"}",
"MAX-ACCESS",
"accessible-for-notify",
"STATUS",
"current",
"DESCRIPTION",
"\"The value of tmnxOamPmNotifThrType indicates the type of the OAM-PM threshold crossing being reported. The code points are as follows. delay (1) - a threshold (e.g.tmnxOamPmCfgThrDelayRaise) on a MEF-35 delay count has been crossed lossAvgFlr (2) - a threshold (e.g. tmnxOamPmCfgThrLossAvgFlrClear) on a MEF-35 Average Frame Loss Ratio (FLR) has been crossed lossChli (3) - a threshold (e.g. tmnxOamPmCfgThrLossChliRaise) on a MEF-35 Consecutive High Loss Interval (CHLI) count has been crossed lossHlii (4) - a threshold (e.g. tmnxOamPmCfgThrLossHliClear) on a MEF-35 High Loss Interval (HLI) count has been crossed lossUnavail (5) - a threshold (e.g. tmnxOamPmCfgThrLossUnavlIndRaise) on a MEF-35 Unavailability Indicator count has been crossed lossUndetAvail (6) - a threshold (e.g. tmnxOamPmCfgThrLossUndtAvlClear) on an Undetermined Availability Indicator count has been crossed lossUndetUnavail(7) - a threshold (e.g. tmnxOamPmCfgThrLossUndtUnavlRais) on an Undetermined Unavailability Indicator count has been crossed\"",
"REFERENCE",
"\"MEF-35, 'Service OAM Performance Monitoring Implementation Agreement', Metro Ethernet Forum, April 2012\"",
"::=",
"{",
"tmnxOamPmNotificationObjs",
"1",
"}"
],
"syntax_tree": [
[
"SimpleSyntax",
"INTEGER",
[
"enumSpec",
[
[
"delay",
1
],
[
"lossAvgFlr",
2
],
[
"lossChli",
3
],
[
"lossHli",
4
],
[
"lossUnavail",
5
],
[
"lossUndetAvail",
6
],
[
"lossUndetUnavail",
7
]
]
]
],
null,
[
"MaxAccessPart",
"accessible-for-notify"
],
[
"Status",
"current"
],
[
"DESCRIPTION",
"The value of tmnxOamPmNotifThrType indicates the type of the OAM-PM threshold crossing being reported. The code points are as follows. delay (1) - a threshold (e.g.tmnxOamPmCfgThrDelayRaise) on a MEF-35 delay count has been crossed lossAvgFlr (2) - a threshold (e.g. tmnxOamPmCfgThrLossAvgFlrClear) on a MEF-35 Average Frame Loss Ratio (FLR) has been crossed lossChli (3) - a threshold (e.g. tmnxOamPmCfgThrLossChliRaise) on a MEF-35 Consecutive High Loss Interval (CHLI) count has been crossed lossHlii (4) - a threshold (e.g. tmnxOamPmCfgThrLossHliClear) on a MEF-35 High Loss Interval (HLI) count has been crossed lossUnavail (5) - a threshold (e.g. tmnxOamPmCfgThrLossUnavlIndRaise) on a MEF-35 Unavailability Indicator count has been crossed lossUndetAvail (6) - a threshold (e.g. tmnxOamPmCfgThrLossUndtAvlClear) on an Undetermined Availability Indicator count has been crossed lossUndetUnavail(7) - a threshold (e.g. tmnxOamPmCfgThrLossUndtUnavlRais) on an Undetermined Unavailability Indicator count has been crossed"
],
[
"REFERENCE",
"MEF-35, 'Service OAM Performance Monitoring Implementation Agreement', Metro Ethernet Forum, April 2012"
],
null,
null,
null
]
}