Indicator of whether or not the AIX Mid-Level Manager
should perform a broadcast query to determine which
machines are on the network at the configured
BroadcastSearchTime, on the configured BroadcastSearchDays.
It is a good idea to perform a broadcast search to discover
nodes that are not initiating communication
(e.g. file servers, bridges, hubs, etc.). In addition,
this should be done at least as often as the
NodeExpirationPeriod to avoid deleting them from
the DiscoveryTable.
If enabledOnce(2), then the broadcast search is only
done once - at the next configured time and day. This
field is then automatically set back to disabled(1) after
the broadcast search is initiated.
If enabledRepeated, then the broadcast search is done
periodically at each configured time and day.
The time and day to perform the broadcast search are
configured using the ActiveSearchTime and ActiveSearchDay
fields.
It is a good idea to configure a broadcast search to
be done at least as often as the configured
NodeExpirationPeriod.
Parsed from file ibm-midlevelmgr.mib.txt
Company: None
Module: MIDLEVELMGR-MIB
Indicator of whether or not the AIX Mid-Level Manager
should perform a broadcast query to determine which
machines are on the network at the configured
BroadcastSearchTime, on the configured BroadcastSearchDays.
It is a good idea to perform a broadcast search to discover
nodes that are not initiating communication
(e.g. file servers, bridges, hubs, etc.). In addition,
this should be done at least as often as the
NodeExpirationPeriod to avoid deleting them from
the DiscoveryTable.
If enabledOnce(2), then the broadcast search is only
done once - at the next configured time and day. This
field is then automatically set back to disabled(1) after
the broadcast search is initiated.
If enabledRepeated, then the broadcast search is done
periodically at each configured time and day.
The time and day to perform the broadcast search are
configured using the ActiveSearchTime and ActiveSearchDay
fields.
It is a good idea to configure a broadcast search to
be done at least as often as the configured
NodeExpirationPeriod.
Parsed from file MIDLEVELMGR-MIB.mib
Module: MIDLEVELMGR-MIB
Vendor: IBM
Module: MIDLEVELMGR-MIB
[Automatically extracted from oidview.com]
smMlmDiscoveryBroadcastSearch OBJECT-TYPE SYNTAX INTEGER { disabled(1), enabledOnce(2), enabledRepeated(3) } ACCESS read-write STATUS mandatory DESCRIPTION "Indicator of whether or not the AIX Mid-Level Manager should perform a broadcast query to determine which machines are on the network at the configured BroadcastSearchTime, on the configured BroadcastSearchDays. It is a good idea to perform a broadcast search to discover nodes that are not initiating communication (e.g. file servers, bridges, hubs, etc.). In addition, this should be done at least as often as the NodeExpirationPeriod to avoid deleting them from the DiscoveryTable. If enabledOnce(2), then the broadcast search is only done once - at the next configured time and day. This field is then automatically set back to disabled(1) after the broadcast search is initiated. If enabledRepeated, then the broadcast search is done periodically at each configured time and day. The time and day to perform the broadcast search are configured using the ActiveSearchTime and ActiveSearchDay fields. It is a good idea to configure a broadcast search to be done at least as often as the configured NodeExpirationPeriod." ::= { smMlmDiscovery 5 }
smMlmDiscoveryBroadcastSearch OBJECT-TYPE SYNTAX INTEGER { disabled(1), enabledOnce(2), enabledRepeated(3) } ACCESS read-write STATUS mandatory DESCRIPTION "Indicator of whether or not the AIX Mid-Level Manager should perform a broadcast query to determine which machines are on the network at the configured BroadcastSearchTime, on the configured BroadcastSearchDays. It is a good idea to perform a broadcast search to discover nodes that are not initiating communication (e.g. file servers, bridges, hubs, etc.). In addition, this should be done at least as often as the NodeExpirationPeriod to avoid deleting them from the DiscoveryTable. If enabledOnce(2), then the broadcast search is only done once - at the next configured time and day. This field is then automatically set back to disabled(1) after the broadcast search is initiated. If enabledRepeated, then the broadcast search is done periodically at each configured time and day. The time and day to perform the broadcast search are configured using the ActiveSearchTime and ActiveSearchDay fields. It is a good idea to configure a broadcast search to be done at least as often as the configured NodeExpirationPeriod." ::= { smMlmDiscovery 5 }
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.2.6.12.13.5.0 | smMlmDiscoveryBroadcastSearch | 0 | 0 | None |
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.2.6.12.13.1 | smMlmDiscoveryState | 1 | 1 | This variable is used to indicate whether the Mid-Level Manager should engage in discovery activity. Once enabled(2), the MLM wi… |
| 1.3.6.1.4.1.2.6.12.13.2 | smMlmDiscoverySensor | 1 | 1 | This field indicates whether or not the Mid-Level Manager should watch network packets in order to ascertain which nodes are curr… |
| 1.3.6.1.4.1.2.6.12.13.3 | smMlmDiscoverySensorMaxReads | 1 | 1 | Maximum number of packets which discovery reads at one time. The higher this number is, the faster nodes will be discovered, but … |
| 1.3.6.1.4.1.2.6.12.13.4 | smMlmDiscoverySensorMaxInterval | 1 | 1 | Discovery uses an adaptive algorithm in deciding how often to search for new nodes; as more nodes are discovered, the frequency a… |
| 1.3.6.1.4.1.2.6.12.13.6 | smMlmDiscoveryBroadcastSearchTime | 1 | 1 | smMlmDiscoveryBroadcastSearchtime |
| 1.3.6.1.4.1.2.6.12.13.7 | smMlmDiscoveryBroadcastSearchDays | 1 | 1 | This field specifies the days of the week to perform the broadcast search at the time specified in the BroadcastSearchTime field … |
| 1.3.6.1.4.1.2.6.12.13.8 | smMlmDiscoveryBroadcastSearchNow | 1 | 1 | When set to true(2), a broadcast search for which machines are on the network is initiated immediately. It may take up to 15 seco… |
| 1.3.6.1.4.1.2.6.12.13.9 | smMlmDiscoveryNodeExpirationPeriod | 1 | 1 | This field specifies the amount of time a node remains in the table of discovered nodes. Setting this field allows nodes that ha… |
| 1.3.6.1.4.1.2.6.12.13.10 | smMlmDiscoveryNotificationFrequency | 1 | 1 | This field specifies the amount of time before a new/old node trap is sent. This allows many new nodes to be sent in the same tr… |
| 1.3.6.1.4.1.2.6.12.13.11 | smMlmDiscoveryNumberOfAddresses | 1 | 1 | This field contains the number of addresses that have been discovered (i.e. the number of entries in the DiscoveryTable). |
| 1.3.6.1.4.1.2.6.12.13.12 | smMlmDiscoveryMaxBridges | 1 | 1 | This field contains the maximum number of rings away from the current ring that a node can be on and still be discovered. For ex… |
| 1.3.6.1.4.1.2.6.12.13.13 | smMlmDiscoveryMessages | 1 | 1 | This field contains messages concerning the discovery component of Mid-Level Manager. |
| 1.3.6.1.4.1.2.6.12.13.50 | smMlmDiscoveryTable | 1 | 11 | Entries define a node that was detected to occur on the local network. The table is indexed by the smMlmDiscoveryAddressFamily, sm… |