- Table of Contents
-
- 05-Layer 3 - IP Services
- 01-HH3C-ARP-RATELIMIT-MIB
- 02-HH3C-ARP-SUPPRESSION-MIB
- 03-HH3C-ARP-TRAP-MIB
- 04-HH3C-DHCP-SNOOP2-MIB
- 05-HH3C-DHCP4-CLIENT-MIB
- 06-HH3C-DHCP4-MIB
- 07-HH3C-DNS-MIB
- 08-HH3C-FIB-MIB
- 09-HH3C-IP-ADDRESS-MIB
- 10-HH3C-IPV6-ADDRESS-MIB
- 11-HH3C-ND-TRAP-MIB
- 12-HH3C-TCP-MIB
- 13-IP-FORWARD-MIB
- 14-IP-MIB
- 15-IPV6-ICMP-MIB
- 16-IPV6-MIB
- 17-IPV6-TCP-MIB
- 18-IPV6-UDP-MIB
- 19-TCP-MIB
- 20-UDP-MIB
- Related Documents
-
Title | Size | Download |
---|---|---|
05-HH3C-DHCP4-CLIENT-MIB | 107.46 KB |
Contents
hh3cDhcp4ClientUserInfoMacAddr
hh3cDhcp4ClientIpConflictAlmRsm
HH3C-DHCP-CLIENT-MIB
About this MIB
Use this MIB to obtain IP address information and configure alarm settings.
MIB file name
hh3c-dhcp4-client.mib
Root object
iso(1).org(3).dod(6).internet(1).private(4).enterprises(1).hh3c(25506).hh3cCommon(2).hh3cDhcp4Client(242)
Scalar objects
hh3cDhcp4ClientConflictIP
Object (OID) |
Access |
Syntax |
Value range |
Description |
Implementation |
hh3cDhcp4ClientConflictIP (1.3.6.1.4.1.25506.2.242.1.1.1) |
accessible-for-notify |
InetAddressIPv4 |
OCTET STRING (4) |
Conflicting IP address assigned to the DHCP client. |
hh3cDhcp4ClientReacquiredIP
Object (OID) |
Access |
Syntax |
Value range |
Description |
Implementation |
hh3cDhcp4ClientReacquiredIP (1.3.6.1.4.1.25506.2.242.1.1.2) |
accessible-for-notify |
InetAddressIPv4 |
OCTET STRING (4) |
Usable address obtained by the DHCP client after it sent an address request again. |
As per the MIB. |
hh3cDhcp4ClientUserInfoMacAddr
Object (OID) |
Access |
Syntax |
Value range |
Description |
Implementation |
hh3cDhcp4ClientUserInfoMacAddr (1.3.6.1.4.1.25506.2.242.1.1.3) |
accessible-for-notify |
MacAddress |
OCTET STRING (6) |
MAC address of the DHCP client. |
As per the MIB. |
Notifications
hh3cDhcp4ClientIpConflictAlm
Basic information
OID |
Event |
Type |
Severity |
Recovery notification |
Default status |
1.3.6.1.4.1.25506.2.242.3.0.1 |
The DHCP client obtains a conflicting IP address. |
Error |
Warning |
1.3.6.1.4.1.25506.2.242.3.1.2 (hh3cDhcp4ClientIpConflictAlmRsm) |
OFF |
Notification triggers
This notification is generated when the DHCP client obtains an IP address that is in the same network segment as another interface address on the local device.
System impact
The DHCP client fails to obtain an IP address.
Status control
ON
CLI: Use the snmp-agent trap enable dhcp-client local-conflict command.
OFF
CLI: Use the undo snmp-agent trap enable dhcp-client local-conflict command.
Objects
OID (object name) |
Description |
Index nodes |
Type |
Value range |
1.3.6.1.2.1.31.1.1.1.1 (ifName) |
Interface name. |
ifindex |
DisplayString |
Standard MIB values. |
1.3.6.1.4.1.25506.2.242.1.1.1 (hh3cDhcp4ClientConflictIP) |
Conflicting IP address assigned to the DHCP client. |
N/A |
InetAddressIPv4 |
Standard MIB values. |
Recommended action
To resolve this issue:
1. Use the display dhcp client command in any view to identify whether the DHCP client has obtained an IP address:
¡ If the DHCP client has obtained an IP address, no action is required.
¡ If the DHCP client has not obtained any IP address, use the display ip routing-table command to identify whether the assigned IP address is in the same network segment as the IP address of another interface.
- If yes, change the IP address of the interface.
- If no, proceed to step 2.
hh3cDhcp4ClientIpConflictAlmRsm
Basic information
OID |
Event |
Type |
Severity |
Recovery notification |
Default status |
1.3.6.1.4.1.25506.2.242.3.0.2 |
The DHCP client obtains a usable IP address after obtaining a conflicting IP address. |
Recovery |
Warning |
N/A |
OFF |
Notification triggers
This notification is generated when the DHCP client obtains a usable IP address after obtaining a conflicting IP address.
System impact
No negative impact on services.
Status control
ON
CLI: Use the snmp-agent trap enable dhcp-client local-conflict command.
OFF
CLI: Use the undo snmp-agent trap enable dhcp-client local-conflict command.
Objects
OID (object name) |
Description |
Index nodes |
Type |
Value range |
1.3.6.1.2.1.31.1.1.1.1 (ifName) |
Interface name. |
ifindex |
DisplayString |
Standard MIB values. |
1.3.6.1.4.1.25506.2.242.1.1.2 (hh3cDhcp4ClientReacquiredIP) |
Usable IP address obtained by the DHCP client. |
N/A |
InetAddressIPv4 |
Standard MIB values. |
Recommended action
No action is required.
hh3cDhcp4ClientApplyIpFailAlm
Basic information
OID |
Event |
Type |
Severity |
Recovery notification |
Default status |
1.3.6.1.4.1.25506.2.242.3.0.3 |
The DHCP client fails to request an IP address. |
Error |
Warning |
1.3.6.1.4.1.25506.2.242.3.1.4 (hh3cDhcp4ClientApplyIpFailAlmRsm) |
OFF |
Notification triggers
This notification is generated when the DHCP client fails to request an IP address.
System impact
The DHCP client fails to obtain an IP address.
Status control
ON
CLI: Use the snmp-agent trap enable dhcp-client ip-apply-failed command.
OFF
CLI: Use the undo snmp-agent trap enable dhcp-client ip-apply-failed command.
Objects
OID (object name) |
Description |
Index nodes |
Type |
Value range |
1.3.6.1.2.1.31.1.1.1.1 (ifName) |
Interface name. |
ifindex |
DisplayString |
Standard MIB values. |
Recommended action
To resolve this issue:
1. Use the display dhcp client command in any view to identify whether the DHCP client has obtained an IP address:
¡ If the DHCP client has obtained an IP address, no action is required.
¡ If the DHCP client has not obtained any IP address, proceed to step 2.
hh3cDhcp4ClientApplyIpFailAlmRsm
Basic information
OID |
Event |
Type |
Severity |
Recovery notification |
Default status |
1.3.6.1.4.1.25506.2.242.3.0.4 |
The DHCP client successfully requests an IP address after an IP address request failure. |
Recovery |
Warning |
N/A |
OFF |
Notification triggers
This notification is generated when the DHCP client successfully requests a usable IP address after an IP address request failure.
System impact
No negative impact on services.
Status control
ON
CLI: Use the snmp-agent trap enable dhcp-client ip-apply-failed command.
OFF
CLI: Use the undo snmp-agent trap enable dhcp-client ip-apply-failed command.
Objects
OID (object name) |
Description |
Index nodes |
Type |
Value range |
1.3.6.1.2.1.31.1.1.1.1 (ifName) |
Interface name. |
ifindex |
DisplayString |
Standard MIB values. |
1.3.6.1.4.1.25506.2.242.1.1.2 (hh3cDhcp4ClientReacquiredIP) |
Usable IP address assigned to the DHCP client. |
N/A |
InetAddressIPv4 |
Standard MIB values. |
Recommended action
No action is required.
hh3cDhcp4ClientApplyIpConflictAlm
Basic information
OID |
Event |
Type |
Severity |
Recovery notification |
Default status |
1.3.6.1.4.1.25506.2.242.3.0.5 |
The DHCP client obtains an IP address conflicting with the IP address of another host. |
Informational |
Warning |
N/A |
OFF |
Notification triggers
This notification is generated when the DHCP client obtains an IP address that conflicts with the IP address of another host. The DHCP client detects for address conflicts by sending gratuitous ARP packets.
System impact
The DHCP client cannot obtain an IP address.
Status control
ON
CLI: Use the snmp-agent trap enable dhcp-client arp-conflict command.
OFF
CLI: Use the undo snmp-agent trap enable dhcp-client arp-conflict command.
Objects
OID (object name) |
Description |
Index nodes |
Type |
Value range |
1.3.6.1.2.1.31.1.1.1.1 (ifName) |
Interface name. |
ifindex |
DisplayString |
Standard MIB values. |
1.3.6.1.4.1.25506.2.242.1.1.2 (hh3cDhcp4ClientReacquiredIP) |
Usable IP address assigned to the DHCP client. |
N/A |
InetAddressIPv4 |
Standard MIB values. |
Recommended action
To resolve this issue:
1. Use the display dhcp client command in any view to identify whether the DHCP client has obtained an IP address:
¡ If the DHCP client has obtained an IP address, no action is required.
¡ If the DHCP client has not obtained any IP address, use the display ip routing-table command to identify whether IP address conflicts occur in the network.
- If multiple IP address conflicts exist, make a new network plan as a best practice.
- If no, proceed to step 2.