This field specifies the amount of time a node remains
in the table of discovered nodes. Setting this field
allows nodes that have not been heard from to be removed
from the discovered nodes table. If this field is blank,
nodes are NEVER removed from the discovered nodes table.
However, if the same Network Address is used with a new
MAC Address, the MAC address of the existing entry
is changed and a trap is sent.
The node expiration period is specified using decimal values
appended by the unit: d - day, h - hour, m - minute,
s - second, u - millisecond. If no unit is appended,
the value is minutes. Multiple values/units are
allowed (i.e. 1h45m = 1 hour, 45 minutes). The default
for this field is 7d (7 days).
It is a good idea to perform an active search at least
as often as this node expiration time period to avoid
losing nodes that are not initiating communication
(e.g. file servers, bridges, hubs, etc.). However,
nodes of this type that are being status checked by
the status checker table will continue to exist.
Parsed from file ibm-midlevelmgr.mib.txt
Company: None
Module: MIDLEVELMGR-MIB
This field specifies the amount of time a node remains
in the table of discovered nodes. Setting this field
allows nodes that have not been heard from to be removed
from the discovered nodes table. If this field is blank,
nodes are NEVER removed from the discovered nodes table.
However, if the same Network Address is used with a new
MAC Address, the MAC address of the existing entry
is changed and a trap is sent.
The node expiration period is specified using decimal values
appended by the unit: d - day, h - hour, m - minute,
s - second, u - millisecond. If no unit is appended,
the value is minutes. Multiple values/units are
allowed (i.e. 1h45m = 1 hour, 45 minutes). The default
for this field is 7d (7 days).
It is a good idea to perform an active search at least
as often as this node expiration time period to avoid
losing nodes that are not initiating communication
(e.g. file servers, bridges, hubs, etc.). However,
nodes of this type that are being status checked by
the status checker table will continue to exist.
Parsed from file MIDLEVELMGR-MIB.mib
Module: MIDLEVELMGR-MIB
Vendor: IBM
Module: MIDLEVELMGR-MIB
[Automatically extracted from oidview.com]
smMlmDiscoveryNodeExpirationPeriod OBJECT-TYPE SYNTAX DisplayString ACCESS read-write STATUS mandatory DESCRIPTION "This field specifies the amount of time a node remains in the table of discovered nodes. Setting this field allows nodes that have not been heard from to be removed from the discovered nodes table. If this field is blank, nodes are NEVER removed from the discovered nodes table. However, if the same Network Address is used with a new MAC Address, the MAC address of the existing entry is changed and a trap is sent. The node expiration period is specified using decimal values appended by the unit: d - day, h - hour, m - minute, s - second, u - millisecond. If no unit is appended, the value is minutes. Multiple values/units are allowed (i.e. 1h45m = 1 hour, 45 minutes). The default for this field is 7d (7 days). It is a good idea to perform an active search at least as often as this node expiration time period to avoid losing nodes that are not initiating communication (e.g. file servers, bridges, hubs, etc.). However, nodes of this type that are being status checked by the status checker table will continue to exist." ::= { smMlmDiscovery 9 }
smMlmDiscoveryNodeExpirationPeriod OBJECT-TYPE SYNTAX DisplayString ACCESS read-write STATUS mandatory DESCRIPTION "This field specifies the amount of time a node remains in the table of discovered nodes. Setting this field allows nodes that have not been heard from to be removed from the discovered nodes table. If this field is blank, nodes are NEVER removed from the discovered nodes table. However, if the same Network Address is used with a new MAC Address, the MAC address of the existing entry is changed and a trap is sent. The node expiration period is specified using decimal values appended by the unit: d - day, h - hour, m - minute, s - second, u - millisecond. If no unit is appended, the value is minutes. Multiple values/units are allowed (i.e. 1h45m = 1 hour, 45 minutes). The default for this field is 7d (7 days). It is a good idea to perform an active search at least as often as this node expiration time period to avoid losing nodes that are not initiating communication (e.g. file servers, bridges, hubs, etc.). However, nodes of this type that are being status checked by the status checker table will continue to exist." ::= { smMlmDiscovery 9 }
OID | Name | Sub children | Sub Nodes Total | Description |
---|---|---|---|---|
1.3.6.1.4.1.2.6.12.13.9.0 | smMlmDiscoveryNodeExpirationPeriod | 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.5 | smMlmDiscoveryBroadcastSearch | 1 | 1 | Indicator of whether or not the AIX Mid-Level Manager should perform a broadcast query to determine which machines are on the net… |
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.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… |