CIG-SERVERS-MIB :: cigDhcpServersOptionType

MIB Reference — IPNetwork Monitor · Updated September 14, 2026

All MIBsCIG-SERVERS-MIBcigDhcpServersOptionType

cigDhcpServersOptionType

Module: CIG-SERVERS-MIB

OID (symbolic): CIG-SERVERS-MIB::cigDhcpServersOptionType

OID (numeric): 1.3.6.1.4.1.6889.2.1.16.2.2.2.1.4

Node type: OBJECT-TYPE

Type: INTEGER

Access: read-write

Description: The type of the DHCP option: ascii(1) is ASCII String as 'Avaya' hex(2) is HEX String as 'aa:bb:cc:dd:12:34:56' ipAddresses(3) can be array of up to 8 IP addresses with the structure as: '121.23.1.12 135.64.13.190 192.123.242.230' integer(4) - unsigned 32 bits integer word(5) - unsigned 16 bits integer

The defaults of cigDhcpServersOptionValue shall be changed according setting the type. If setting Type == ascii(1) then the default is '' If setting Type == hex(2) then the default is '' If setting Type == ipAddresses(3) then the default is '0.0.0.0' If setting Type == integer(4) then the default is '00000000' If setting Type == word(5) then the default is '0000'

What is cigDhcpServersOptionType?

This selects the data encoding used for the DHCP option's value -- ASCII text, hex bytes, up to eight IP addresses, a 32-bit integer, or a 16-bit word -- which in turn determines how cigDhcpServersOptionValue is interpreted and re-defaults when changed. Because DHCP options vary widely in what data type they carry (a TFTP server address versus a numeric lease parameter, for instance), this field is what tells the DHCP server how to package the raw bytes it sends to clients for that option number. Setting this to hex(2) for a custom option would mean an admin must then enter the value as a colon-separated hex string like 'aa:bb:cc:dd:12:34:56' rather than plain text.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.6889.2.1.16.2.2.2.1.4
snmpwalk -v2c -c public <target> CIG-SERVERS-MIB::cigDhcpServersOptionType

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.6889.2.1.16.2.2.2.1.4.1
snmpget -v2c -c public <target> CIG-SERVERS-MIB::cigDhcpServersOptionType.1

Set instance 1 (SNMPv2c):

snmpset -v2c -c private <target> 1.3.6.1.4.1.6889.2.1.16.2.2.2.1.4.1 i <value>

Start monitoring Avaya CIG (Common Interworking Gateway) server with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the CIG-SERVERS-MIB::cigDhcpServersOptionType OID value, configure state conditions and alerts, and monitor any Avaya CIG (Common Interworking Gateway) server from a single console.

OID Breakdown

Upper-level ancestors (9 from the standard OID tree / other modules)
Numeric OIDNameModule
1isoLANART-AGENT
1.3orgAirPair-MIB
1.3.6dodAirPair-MIB
1.3.6.1internetAirPair-MIB
1.3.6.1.4privateAirPair-MIB
1.3.6.1.4.1enterprisesAirPair-MIB
1.3.6.1.4.1.6889avayaAV-APPLICATION-ENABLEMENT-SERVICES-MIB
1.3.6.1.4.1.6889.2mibsAV-APPLICATION-ENABLEMENT-SERVICES-MIB
1.3.6.1.4.1.6889.2.1lsgAVAYAGEN-MIB
Numeric OIDNameModule
1.3.6.1.4.1.6889.2.1.16cigServersCIG-SERVERS-MIB
1.3.6.1.4.1.6889.2.1.16.2cigDhcpServersCIG-SERVERS-MIB
1.3.6.1.4.1.6889.2.1.16.2.2cigDhcpServersPoolCIG-SERVERS-MIB
1.3.6.1.4.1.6889.2.1.16.2.2.2cigDhcpServersPoolGenOptionTableCIG-SERVERS-MIB
1.3.6.1.4.1.6889.2.1.16.2.2.2.1cigDhcpServersPoolGenOptionEntryCIG-SERVERS-MIB
1.3.6.1.4.1.6889.2.1.16.2.2.2.1.4cigDhcpServersOptionTypeCIG-SERVERS-MIB