Status in source: current.
Technical details
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"tmnxOamPmCfgBinEntry",
"OBJECT-TYPE",
"SYNTAX",
"TmnxOamPmCfgBinEntry",
"MAX-ACCESS",
"not-accessible",
"STATUS",
"current",
"DESCRIPTION",
"\"tmnxOamPmCfgBinEntry contains the configuration information for one OAM Performance Monitoring bin. Rows are created in this table when one (or more) of the following objects is set: tmnxOamPmCfgBinGroupFdBinCount, tmnxOamPmCfgBinGroupFdrBinCount, or tmnxOamPmCfgBinGroupIfdvBinCount. Suppose, for example, that the following values are set for bin group 255. Object Value ------------------------------------ ----- tmnxOamPmCfgBinGroupFdBinCount.255 4 tmnxOamPmCfgBinGroupFdrBinCount.255 3 tmnxOamPmCfgBinGroupIfdvBinCount.255 2 Then, the following rows will be created in this table (where index columns are underlined with '#', column names have been abbreviated by replacing 'tmnxOamPmCfg' with '_', and the _BinLowerBound column shows the default values). _BinGroupId _BinGroupType _BinId _BinLowerBound (microsec) ########### ############# ###### ------------------------- 255 fd(1) 1 5000 255 fd(1) 2 10000 255 fd(1) 3 15000 255 fdr(2) 1 5000 255 fdr(2) 2 10000 255 ifdv(3) 1 5000 Note that tmnxOamPmCfgBinGroupFdBinCount.255 is 4, but there are only three corresponding rows in this table. The fourth bin is bin 0, which has a hard coded lower bound of 0 microseconds. Bin 0 never has a row in this table. The lower bounds for a particular {tmnxOamPmCfgBinGroupId, tmnxOamPmCfgBinType} pair must be strictly ascending. See the tmnxOamPmCfgBinGroupAdminStatus DESCRIPTION clause for more information.\"",
"INDEX",
"{",
"tmnxOamPmCfgBinGroupId",
",",
"tmnxOamPmCfgBinType",
",",
"tmnxOamPmCfgBinNum",
"}",
"::=",
"{",
"tmnxOamPmCfgBinTable",
"1",
"}"
],
"syntax_tree": [
[
"row",
"TmnxOamPmCfgBinEntry"
],
null,
[
"MaxAccessPart",
"not-accessible"
],
[
"Status",
"current"
],
[
"DESCRIPTION",
"tmnxOamPmCfgBinEntry contains the configuration information for one OAM Performance Monitoring bin. Rows are created in this table when one (or more) of the following objects is set: tmnxOamPmCfgBinGroupFdBinCount, tmnxOamPmCfgBinGroupFdrBinCount, or tmnxOamPmCfgBinGroupIfdvBinCount. Suppose, for example, that the following values are set for bin group 255. Object Value ------------------------------------ ----- tmnxOamPmCfgBinGroupFdBinCount.255 4 tmnxOamPmCfgBinGroupFdrBinCount.255 3 tmnxOamPmCfgBinGroupIfdvBinCount.255 2 Then, the following rows will be created in this table (where index columns are underlined with '#', column names have been abbreviated by replacing 'tmnxOamPmCfg' with '_', and the _BinLowerBound column shows the default values). _BinGroupId _BinGroupType _BinId _BinLowerBound (microsec) ########### ############# ###### ------------------------- 255 fd(1) 1 5000 255 fd(1) 2 10000 255 fd(1) 3 15000 255 fdr(2) 1 5000 255 fdr(2) 2 10000 255 ifdv(3) 1 5000 Note that tmnxOamPmCfgBinGroupFdBinCount.255 is 4, but there are only three corresponding rows in this table. The fourth bin is bin 0, which has a hard coded lower bound of 0 microseconds. Bin 0 never has a row in this table. The lower bounds for a particular {tmnxOamPmCfgBinGroupId, tmnxOamPmCfgBinType} pair must be strictly ascending. See the tmnxOamPmCfgBinGroupAdminStatus DESCRIPTION clause for more information."
],
null,
null,
[
"INDEX",
[
[
0,
"tmnxOamPmCfgBinGroupId"
],
[
0,
"tmnxOamPmCfgBinType"
],
[
0,
"tmnxOamPmCfgBinNum"
]
]
],
null
]
}