Status in source: mandatory.
Names: eqptSlotPlannedType
Technical details
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"eqptSlotPlannedType",
"OBJECT-TYPE",
"SYNTAX",
"DisplayString",
"ACCESS",
"read-write",
"STATUS",
"mandatory",
"DESCRIPTION",
"\"A string representing the board (NT, EXT, LSM, ACU, CTRL, Applique) that is planned in the slot. If the board is planned, the string consists of a mnemonic that identifies the board-type. Following mnemonics are valid: <BOARD_MNEMONIC> A board of a specific type. Refer to the ETSI and US Configurations documents for the list of boards that are supported in a given release. ODM board types are planned with the board mnemonic, they are treated as unmanaged boards. EXT_MANAGED The presence of the LT module can be detected but it is not managed by this NT in the HYNT module. The LT type must be planned on the other NT. UNMANAGED Unmanaged board: this means that the presence of the board can be detected and that the board can be reset and powered-down but that it is not possible to establish communication with the board in software. NOT_PLANNED No board is planned in the slot. NOT_ALLOWED Slot planning is not allowed in this position. ALCATEL NOTE: SUPPORT: YES INSRVMOD: YES RANGE: See above PERSIST: YES DEFVALUE: 'NOT_PLANNED' UNITS: -\"",
"::=",
"{",
"eqptBoardEntry",
"2",
"}"
],
"syntax_tree": [
[
"row",
"DisplayString"
],
null,
[
"MaxAccessPart",
"read-write"
],
[
"Status",
"mandatory"
],
[
"DESCRIPTION",
"A string representing the board (NT, EXT, LSM, ACU, CTRL, Applique) that is planned in the slot. If the board is planned, the string consists of a mnemonic that identifies the board-type. Following mnemonics are valid: <BOARD_MNEMONIC> A board of a specific type. Refer to the ETSI and US Configurations documents for the list of boards that are supported in a given release. ODM board types are planned with the board mnemonic, they are treated as unmanaged boards. EXT_MANAGED The presence of the LT module can be detected but it is not managed by this NT in the HYNT module. The LT type must be planned on the other NT. UNMANAGED Unmanaged board: this means that the presence of the board can be detected and that the board can be reset and powered-down but that it is not possible to establish communication with the board in software. NOT_PLANNED No board is planned in the slot. NOT_ALLOWED Slot planning is not allowed in this position. ALCATEL NOTE: SUPPORT: YES INSRVMOD: YES RANGE: See above PERSIST: YES DEFVALUE: 'NOT_PLANNED' UNITS: -"
],
null,
null,
null,
null
]
}
- Nokia networking MIB copies (LibreNMS/Observium Community)
· Publisher's source file: ASAM-EQUIP-MIB
Vendor MIB copy from the LibreNMS archive.
Nokia support.
Module: ASAM-EQUIP-MIB
See published definition above
Module imports
{'ITF-MIB': ['InterfaceIndex'], 'RFC-1212': ['OBJECT-TYPE'], 'SNMPv2-TC': ['DisplayString', 'RowStatus', 'TruthValue'], 'SYSTEM-MIB': ['asam'], 'ASAM-TC-MIB': ['AsamNextProfileIndex', 'AsamProfileRefCount', 'AsamProfilePointer', 'AsamProfileIndex', 'AsamProfileName', 'NetworkTimeInSeconds'], 'RFC1155-SMI': ['IpAddress', 'TimeTicks', 'Counter'], 'ASAM-ALARM-MIB': ['AsamAlarmSeverityType']}
· Download ASAM-EQUIP-MIB
Related source files and packages:
- Multiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community)
· Publisher's source file: ASAM-EQUIP-MIB
Vendor MIB copy from the LibreNMS archive.
Module: ASAM-EQUIP-MIB
Same published definition
Module imports
{'ITF-MIB': ['InterfaceIndex'], 'RFC-1212': ['OBJECT-TYPE'], 'SNMPv2-TC': ['DisplayString', 'RowStatus', 'TruthValue'], 'SYSTEM-MIB': ['asam'], 'ASAM-TC-MIB': ['AsamNextProfileIndex', 'AsamProfileRefCount', 'AsamProfilePointer', 'AsamProfileIndex', 'AsamProfileName', 'NetworkTimeInSeconds'], 'RFC1155-SMI': ['IpAddress', 'TimeTicks', 'Counter'], 'ASAM-ALARM-MIB': ['AsamAlarmSeverityType']}
· Download ASAM-EQUIP-MIB
Related source files and packages:
Same file in Observium Community.