OID reference

serverClientHardwareAddress

1.3.6.1.2.1.99.1.1.6.5.1.1

Description

The hardware type and hardware address of the client that has been assigned this lease. The first octet of this object contains the hardware type from the 'htype' field of the BOOTP packet and the remaining octets contain the hardware address from the 'chaddr' field of the BOOTP packet.

Full description and source information

Identification

Identifier and names

Parent
1.3.6.1.2.1.99.1.1.6.5.1 (serverClientEntry)
Node code
1
Node name
serverClientHardwareAddress
Category
SNMP management object
Numeric OID
1.3.6.1.2.1.99.1.1.6.5.1.1
URN notation
urn:oid:1.3.6.1.2.1.99.1.1.6.5.1.1
Type
OBJECT-TYPE
ASN.1, OID-IRI and named path variants
ASN.1 notation

{1 3 6 1 2 1 99 1 1 6 5 1 1}

  • {iso(1) identified-organization(3) dod(6) internet(1) mgmt(2) mib-2(1) entitySensorMIB(99) entitySensorObjects(1) entPhySensorTable(1) serverConfiguration(6) serverClientTable(5) serverClientEntry(1) serverClientHardwareAddress(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) mgmt(2) mib-2(1) entitySensorMIB(99) entitySensorObjects(1) serverMIBObjects(1) serverConfiguration(6) serverClientTable(5) serverClientEntry(1) serverClientHardwareAddress(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) mgmt(2) mib-2(1) entitySensorMIB(99) serverMIB(1) entPhySensorTable(1) serverConfiguration(6) serverClientTable(5) serverClientEntry(1) serverClientHardwareAddress(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) mgmt(2) mib-2(1) entitySensorMIB(99) serverMIB(1) serverMIBObjects(1) serverConfiguration(6) serverClientTable(5) serverClientEntry(1) serverClientHardwareAddress(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) mgmt(2) mib-2(1) dhcp(99) entitySensorObjects(1) entPhySensorTable(1) serverConfiguration(6) serverClientTable(5) serverClientEntry(1) serverClientHardwareAddress(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) mgmt(2) mib-2(1) dhcp(99) entitySensorObjects(1) serverMIBObjects(1) serverConfiguration(6) serverClientTable(5) serverClientEntry(1) serverClientHardwareAddress(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) mgmt(2) mib-2(1) dhcp(99) serverMIB(1) entPhySensorTable(1) serverConfiguration(6) serverClientTable(5) serverClientEntry(1) serverClientHardwareAddress(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) mgmt(2) mib-2(1) dhcp(99) serverMIB(1) serverMIBObjects(1) serverConfiguration(6) serverClientTable(5) serverClientEntry(1) serverClientHardwareAddress(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) mgmt(2) mib(1) entitySensorMIB(99) entitySensorObjects(1) entPhySensorTable(1) serverConfiguration(6) serverClientTable(5) serverClientEntry(1) serverClientHardwareAddress(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) mgmt(2) mib(1) entitySensorMIB(99) entitySensorObjects(1) serverMIBObjects(1) serverConfiguration(6) serverClientTable(5) serverClientEntry(1) serverClientHardwareAddress(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) mgmt(2) mib(1) entitySensorMIB(99) serverMIB(1) entPhySensorTable(1) serverConfiguration(6) serverClientTable(5) serverClientEntry(1) serverClientHardwareAddress(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) mgmt(2) mib(1) entitySensorMIB(99) serverMIB(1) serverMIBObjects(1) serverConfiguration(6) serverClientTable(5) serverClientEntry(1) serverClientHardwareAddress(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) mgmt(2) mib(1) dhcp(99) entitySensorObjects(1) entPhySensorTable(1) serverConfiguration(6) serverClientTable(5) serverClientEntry(1) serverClientHardwareAddress(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) mgmt(2) mib(1) dhcp(99) entitySensorObjects(1) serverMIBObjects(1) serverConfiguration(6) serverClientTable(5) serverClientEntry(1) serverClientHardwareAddress(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) mgmt(2) mib(1) dhcp(99) serverMIB(1) entPhySensorTable(1) serverConfiguration(6) serverClientTable(5) serverClientEntry(1) serverClientHardwareAddress(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) mgmt(2) mib(1) dhcp(99) serverMIB(1) serverMIBObjects(1) serverConfiguration(6) serverClientTable(5) serverClientEntry(1) serverClientHardwareAddress(1)}
  • Additional combinations skipped.
OID-IRI notation
  • /1/3/6/1/2/1/99/1/1/6/5/1/1
  • /ISO/Identified-Organization/6/1/2/1/99/1/1/6/5/1/1
  • /ISO/3/6/1/2/1/99/1/1/6/5/1/1
Named path variants
  • /iso/identified-organization/dod/internet/mgmt/mib-2/entitySensorMIB/entitySensorObjects/entPhySensorTable/serverConfiguration/serverClientTable/serverClientEntry/serverClientHardwareAddress
  • /iso/identified-organization/dod/internet/mgmt/mib-2/entitySensorMIB/entitySensorObjects/serverMIBObjects/serverConfiguration/serverClientTable/serverClientEntry/serverClientHardwareAddress
  • /iso/identified-organization/dod/internet/mgmt/mib-2/entitySensorMIB/serverMIB/entPhySensorTable/serverConfiguration/serverClientTable/serverClientEntry/serverClientHardwareAddress
  • /iso/identified-organization/dod/internet/mgmt/mib-2/entitySensorMIB/serverMIB/serverMIBObjects/serverConfiguration/serverClientTable/serverClientEntry/serverClientHardwareAddress
  • /iso/identified-organization/dod/internet/mgmt/mib-2/dhcp/entitySensorObjects/entPhySensorTable/serverConfiguration/serverClientTable/serverClientEntry/serverClientHardwareAddress
  • /iso/identified-organization/dod/internet/mgmt/mib-2/dhcp/entitySensorObjects/serverMIBObjects/serverConfiguration/serverClientTable/serverClientEntry/serverClientHardwareAddress
  • /iso/identified-organization/dod/internet/mgmt/mib-2/dhcp/serverMIB/entPhySensorTable/serverConfiguration/serverClientTable/serverClientEntry/serverClientHardwareAddress
  • /iso/identified-organization/dod/internet/mgmt/mib-2/dhcp/serverMIB/serverMIBObjects/serverConfiguration/serverClientTable/serverClientEntry/serverClientHardwareAddress
  • /iso/identified-organization/dod/internet/mgmt/mib/entitySensorMIB/entitySensorObjects/entPhySensorTable/serverConfiguration/serverClientTable/serverClientEntry/serverClientHardwareAddress
  • /iso/identified-organization/dod/internet/mgmt/mib/entitySensorMIB/entitySensorObjects/serverMIBObjects/serverConfiguration/serverClientTable/serverClientEntry/serverClientHardwareAddress
  • /iso/identified-organization/dod/internet/mgmt/mib/entitySensorMIB/serverMIB/entPhySensorTable/serverConfiguration/serverClientTable/serverClientEntry/serverClientHardwareAddress
  • /iso/identified-organization/dod/internet/mgmt/mib/entitySensorMIB/serverMIB/serverMIBObjects/serverConfiguration/serverClientTable/serverClientEntry/serverClientHardwareAddress
  • /iso/identified-organization/dod/internet/mgmt/mib/dhcp/entitySensorObjects/entPhySensorTable/serverConfiguration/serverClientTable/serverClientEntry/serverClientHardwareAddress
  • /iso/identified-organization/dod/internet/mgmt/mib/dhcp/entitySensorObjects/serverMIBObjects/serverConfiguration/serverClientTable/serverClientEntry/serverClientHardwareAddress
  • /iso/identified-organization/dod/internet/mgmt/mib/dhcp/serverMIB/entPhySensorTable/serverConfiguration/serverClientTable/serverClientEntry/serverClientHardwareAddress
  • /iso/identified-organization/dod/internet/mgmt/mib/dhcp/serverMIB/serverMIBObjects/serverConfiguration/serverClientTable/serverClientEntry/serverClientHardwareAddress
  • Additional combinations skipped.

SNMP properties

Value type
PhysicalAddress
Maximum access defined by MIB
not-accessible
Status in MIB
current

Properties come from available MIB definitions. Actual device support and access can differ. See source records below for original files and qualifications.

Meaning

Descriptions

1 unique

Identical descriptions are grouped. Different wording and device-specific notes are retained.

The hardware type and hardware address of the client that has
been assigned this lease. The first octet of this object
contains the hardware type from the 'htype' field of the BOOTP
packet and the remaining octets contain the hardware address
from the 'chaddr' field of the BOOTP packet.
Sources for this description

MIBdepot

Parsed from DHCP-SERVER-MIB.txt · riverstone · DHCP-SERVER-MIB

Source file: Download DHCP-SERVER-MIB.txt

Browse all files from MIBdepot

Historical records

Additional source information

Information from OID Repository
Vendor: Riverstone Networks
Module: DHCP-SERVER-MIB (DHCP-SERVER-MIB)
Type: TABULAR
Access: not-accessible
Syntax: PhysicalAddress

Automatically extracted from www.mibdepot.com
Information from MIBdepot
serverClientHardwareAddress  OBJECT-TYPE 
           SYNTAX      PhysicalAddress 
           MAX-ACCESS  not-accessible 
           STATUS      current 
           DESCRIPTION 
              "The hardware type and hardware address of the client that has 
              been assigned this lease.  The first octet of this object 
              contains the hardware type from the 'htype' field of the BOOTP 
              packet and the remaining octets contain the hardware address 
              from the 'chaddr' field of the BOOTP packet." 
           ::= { serverClientEntry 1 }

Registration

Registration authorities

First Registration Authority (inferred from ancestor 1.3.6)

Defense Communication Agency

Current Registration Authority (inferred from ancestor 1.3.6.1.2)

Internet Assigned Numbers Authority

Siblings (5)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.2.1.99.1.1.6.5.1.2 serverClientAddress00 The IP address of the entry. May be used to index into the
serverAddressTable. May be 0.0.0.0 if an address is not
associated w…
1.3.6.1.2.1.99.1.1.6.5.1.3 serverClientSubnetMask00 The subnet mask (DHCP option 1) applied to
serverClientAddress.
1.3.6.1.2.1.99.1.1.6.5.1.4 serverClientLastRequestTime00 The timestamp of the last request received, to millisecond
precision if available on the server.
1.3.6.1.2.1.99.1.1.6.5.1.5 serverClientLastRequestType00 The type of the last request message received for this
client.If the server does not capture this information, the
value 32,767 i…
1.3.6.1.2.1.99.1.1.6.5.1.6 serverClientLastResponseType00 The type of the last response message sent to this client. If
the server does not capture this information, the value 32,767
is …