tmnxDhcpsPoolFoState

TIMETRA-DHCP-SERVER-MIB · .1.3.6.1.4.1.6527.3.1.2.47.1.18.6.1.7

Object

The value of tmnxDhcpsPoolFoState indicates the failover state of the
IP pool instance.

Context

MIB
TIMETRA-DHCP-SERVER-MIB
OID
.1.3.6.1.4.1.6527.3.1.2.47.1.18.6.1.7
Type
column
Access
readonly
Status
current
Parent
tmnxDhcpsPoolFoEntry
Groups
1

Walk the column to discover its indexed instances, or supply every index to read one instance.

Walk the column
/usr/bin/snmpbulkwalk -v2c -c '<community>' -Pud -Ir -OQUs -m 'TIMETRA-DHCP-SERVER-MIB' -M '/opt/observium/mibs/nokia:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'TIMETRA-DHCP-SERVER-MIB::tmnxDhcpsPoolFoState'
More examples
Read one indexed instance
/usr/bin/snmpget -v2c -c '<community>' -Pud -Ir -OQUv -m 'TIMETRA-DHCP-SERVER-MIB' -M '/opt/observium/mibs/nokia:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'TIMETRA-DHCP-SERVER-MIB::tmnxDhcpsPoolFoState.<index>'
Translate to a numeric OID
/usr/bin/snmptranslate -Pud -Ir -On -m 'TIMETRA-DHCP-SERVER-MIB' -M '/opt/observium/mibs/nokia:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'TIMETRA-DHCP-SERVER-MIB::tmnxDhcpsPoolFoState'

Syntax

Source
TmnxDhcpsFoState
Base type
Enumeration
Type Description
The TmnxDhcpsFoState data type is an enumerated integer that describes
the values used to identify the failover state of a DHCP Server
instance.
          
unknown
init            : the DHCP Server instance is preparing
                         to startup;
startUp         : the DHCP Server instance is starting up;
noCommunication : the communication with the partner is lost;
partnerDown     : the partner is assumed down;
normal
shutdown        : the administrative state of the failover
                  facility of this DHCP server instance
                  is 'outOfService', or the administrative
                  state of this DHCP server instance
                  is 'outOfService';
transition
preNormal       : sub-state of 'normal', that applies to a pair of
                  servers A and B, while B is recovering after it went down:
    - server A is responding to (instead of dropping) renew and rebind messages
      for remote leases it has allocated during partnerDown;
    - server B is dropping (instead of NACKing) renew and rebind messages for
      yet unknown local leases while resynchronizing with the MCS database.

Values & Constraints

Type Values
1unknown
2init
3startUp
4noCommunication
5partnerDown
6normal
7shutdown
8transition
9preNormal

Conformance