Indicates whether a module conflict has been detected. A conflict
indicates that the agent has discovered a module in this slot which is
a different type from the module which already exists in the agent's
database. Examples of conflicts are:
- A module has been discovered in this slot and there is an active
module already in this slot. In this case, dh90SlotProxyStatus
would have a value of present(4). This indicates that the active
module was manually added to an incorrect slot and should be moved
to its correct location.
- A module has been discovered in this slot and the last known module
in this slot was of a different type and that last known module had
other than default parameters set. The last known module was
physically removed and possibly moved to a new location. In this
case, the dh90SlotProxyStatus may have the a of unreachable(2) or
not-present(3). Either delete the module from this slot to allow
the discovered module to replace it, or move the module in this
slot to a new location.
Parsed from file DEChub90.mib.txt
Company: None
Module: DECHUB90-MIB
Indicates whether a module conflict has been detected. A conflict
indicates that the agent has discovered a module in this slot which is
a different type from the module which already exists in the agent's
database. Examples of conflicts are:
- A module has been discovered in this slot and there is an active
module already in this slot. In this case, dh90SlotProxyStatus
would have a value of present(4). This indicates that the active
module was manually added to an incorrect slot and should be moved
to its correct location.
- A module has been discovered in this slot and the last known module
in this slot was of a different type and that last known module had
other than default parameters set. The last known module was
physically removed and possibly moved to a new location. In this
case, the dh90SlotProxyStatus may have the a of unreachable(2) or
not-present(3). Either delete the module from this slot to allow
the discovered module to replace it, or move the module in this
slot to a new location.
Parsed from file DECHUB90-MIB.mib
Module: DECHUB90-MIB
Vendor: DEC
Module: DECHUB90-MIB
[Automatically extracted from oidview.com]
dh90SlotConflictStatus OBJECT-TYPE SYNTAX INTEGER { none(1), conflict(2) } ACCESS read-only STATUS mandatory DESCRIPTION "Indicates whether a module conflict has been detected. A conflict indicates that the agent has discovered a module in this slot which is a different type from the module which already exists in the agent's database. Examples of conflicts are: - A module has been discovered in this slot and there is an active module already in this slot. In this case, dh90SlotProxyStatus would have a value of present(4). This indicates that the active module was manually added to an incorrect slot and should be moved to its correct location. - A module has been discovered in this slot and the last known module in this slot was of a different type and that last known module had other than default parameters set. The last known module was physically removed and possibly moved to a new location. In this case, the dh90SlotProxyStatus may have the a of unreachable(2) or not-present(3). Either delete the module from this slot to allow the discovered module to replace it, or move the module in this slot to a new location." ::= { dh90SlotEntry 19 }
dh90SlotConflictStatus OBJECT-TYPE SYNTAX INTEGER { none(1), conflict(2) } ACCESS read-only STATUS mandatory DESCRIPTION "Indicates whether a module conflict has been detected. A conflict indicates that the agent has discovered a module in this slot which is a different type from the module which already exists in the agent's database. Examples of conflicts are: - A module has been discovered in this slot and there is an active module already in this slot. In this case, dh90SlotProxyStatus would have a value of present(4). This indicates that the active module was manually added to an incorrect slot and should be moved to its correct location. - A module has been discovered in this slot and the last known module in this slot was of a different type and that last known module had other than default parameters set. The last known module was physically removed and possibly moved to a new location. In this case, the dh90SlotProxyStatus may have the a of unreachable(2) or not-present(3). Either delete the module from this slot to allow the discovered module to replace it, or move the module in this slot to a new location." ::= { dh90SlotEntry 19 }
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.36.2.18.10.1.5.1.1 | dh90SlotIndex | 0 | 0 | The slot number containing the module. Setting this variable to the slot number of an empty slot in the community will result i… |
| 1.3.6.1.4.1.36.2.18.10.1.5.1.2 | dh90SlotModuleType | 0 | 0 | - do not use, provided for backwards compatibility only - Use dh90SlotObjectID instead. The type of the module in a slot. If the… |
| 1.3.6.1.4.1.36.2.18.10.1.5.1.3 | dh90SlotModuleName | 0 | 0 | A textual description of the module. Setting a value with embedded spaces or tabs will result in a 'badValue' response. Note tha… |
| 1.3.6.1.4.1.36.2.18.10.1.5.1.4 | dh90SlotModuleVersion | 0 | 0 | A textual description of the version level of the hardware and firmware of the module. |
| 1.3.6.1.4.1.36.2.18.10.1.5.1.5 | dh90SlotCounterTime | 0 | 0 | Time since the counters of this module were zeroed. Devices which do not support MOP counters will return a 'noSuchName' respon… |
| 1.3.6.1.4.1.36.2.18.10.1.5.1.6 | dh90SlotIfBase | 0 | 0 | An index into the ifTable for the first network interface on this module. Add one to this value to reference the ifTable entry … |
| 1.3.6.1.4.1.36.2.18.10.1.5.1.7 | dh90SlotIfNumber | 0 | 0 | The number of network interfaces on this module. For example, a DECbridge 90 has 2 network interfaces, the backbone and the wor… |
| 1.3.6.1.4.1.36.2.18.10.1.5.1.8 | dh90SlotPhysicalAddress | 0 | 0 | A read-write variable for the physical address to allow devices to be added to the hub remotely. Writing this variable as part … |
| 1.3.6.1.4.1.36.2.18.10.1.5.1.9 | dh90SlotNumberOfPorts | 0 | 0 | The number of ports on this module. Returns the following values for the indicated devices: Device Value ==========… |
| 1.3.6.1.4.1.36.2.18.10.1.5.1.10 | dh90SlotPassword | 0 | 0 | Password used to enable privileged operations on devices which support the MOP and RBMS protocols for remote management. Settin… |
| 1.3.6.1.4.1.36.2.18.10.1.5.1.11 | dh90SlotNewPassword | 0 | 0 | Setting this variable causes the agent to set a new password on the device using the value provided as the new password and the … |
| 1.3.6.1.4.1.36.2.18.10.1.5.1.12 | dh90SlotPolling | 0 | 0 | The current polling status of the module. If the DECagent 90 is polling this device, a get of this variable will return on(2), o… |
| 1.3.6.1.4.1.36.2.18.10.1.5.1.13 | dh90SlotPrimarySpecific | 0 | 0 | None |
| 1.3.6.1.4.1.36.2.18.10.1.5.1.14 | dh90SlotSecondarySpecific | 0 | 0 | None |
| 1.3.6.1.4.1.36.2.18.10.1.5.1.15 | dh90SlotIpAddress | 0 | 0 | The IP address of the device in the given slot. This value is returned only for devices which implement their own on-board SNMP… |
| 1.3.6.1.4.1.36.2.18.10.1.5.1.16 | dh90SlotCommunityString | 0 | 0 | The community string of the device in the given slot. This value is returned only for devices which implement their own on-boar… |
| 1.3.6.1.4.1.36.2.18.10.1.5.1.17 | dh90SlotObjectID | 0 | 0 | The sysObjectID of the module in the given slot. This value is provided by the DECagent 90 for modules in community 1. It can b… |
| 1.3.6.1.4.1.36.2.18.10.1.5.1.18 | dh90SlotProxyStatus | 0 | 0 | The state of the module as known by the proxy agent. The possible states and their meanings are: reachable - indicates an oper… |
| 1.3.6.1.4.1.36.2.18.10.1.5.1.20 | dh90SlotConflictDiscoveredID | 0 | 0 | If dh90SlotConflictStatus has a value of conflict(2) then this object indicates the sysObjectID of the module that has been disc… |
| 1.3.6.1.4.1.36.2.18.10.1.5.1.21 | dh90SlotReset | 0 | 0 | A control variable to perform reset functions on DEChub 90 modules which are in the same hub as the managing agent. The agent m… |