CIG-CLIENTS-MIB :: cigDhcpClientsHostName

MIB Reference — IPNetwork Monitor · Updated October 05, 2026

All MIBs › CIG-CLIENTS-MIB › cigDhcpClientsHostName

cigDhcpClientsHostName

Module: CIG-CLIENTS-MIB

OID (symbolic): CIG-CLIENTS-MIB::cigDhcpClientsHostName

OID (numeric): 1.3.6.1.4.1.6889.2.1.17.1.1.1.7

Node type: OBJECT-TYPE

Type: DisplayString

Access: read-write

Description: Host name is sent by the DHCP client as Dhcp option 12. It is specifically used by part of DHCP servers (MS2000) to identify the client in the binding file (more user intuitive). This option is used as well by part of the DHCP server with the support of DHCP client (sending option 81) to update the DNS server with the new IP for specific host. The format of the string can be: 'usernameA'. The hostname shall comply to RFC 1035 naming convention with the following exceptions: a. allow digits at the start of the name. b. Do not check length constraints of 63 bytes. The default of the host name used by the DHCP client is the device host name.

What is cigDhcpClientsHostName?

This is the hostname string this interface sends to the DHCP server as option 12, which per the description is specifically consumed by certain DHCP servers, the description names MS2000, to make the client easier to identify in the server's lease binding table, and separately can be used by servers that support dynamic DNS updates to register this device's name automatically. An admin managing many similarly-configured gateways would set a distinct, meaningful hostname here, following RFC 1035 naming rules, specifically so the DHCP server's lease table shows recognizable names instead of a list of anonymous MAC addresses. For example, setting this to 'branch-gw-042' instead of leaving it blank makes that specific device's lease immediately identifiable in the DHCP server's admin console among dozens of other leased devices.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.6889.2.1.17.1.1.1.7
snmpwalk -v2c -c public <target> CIG-CLIENTS-MIB::cigDhcpClientsHostName

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.6889.2.1.17.1.1.1.7.1
snmpget -v2c -c public <target> CIG-CLIENTS-MIB::cigDhcpClientsHostName.1

Set instance 1 (SNMPv2c):

snmpset -v2c -c private <target> 1.3.6.1.4.1.6889.2.1.17.1.1.1.7.1 s <value>

Start monitoring Avaya communication gateways with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the CIG-CLIENTS-MIB::cigDhcpClientsHostName OID value, configure state conditions and alerts, and monitor any Avaya communication gateways 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.17cigClientsCIG-CLIENTS-MIB
1.3.6.1.4.1.6889.2.1.17.1cigDhcpClientsCIG-CLIENTS-MIB
1.3.6.1.4.1.6889.2.1.17.1.1cigDhcpClientsTableCIG-CLIENTS-MIB
1.3.6.1.4.1.6889.2.1.17.1.1.1cigDhcpClientsEntryCIG-CLIENTS-MIB
1.3.6.1.4.1.6889.2.1.17.1.1.1.7cigDhcpClientsHostNameCIG-CLIENTS-MIB