To enable the tracking of the DHCP operations as per the configured debug level, use the command debug ip dhcp in Privileged EXEC Mode. The no form of the command disables the tracking of the DHCP client operations. This command allows combination of debug levels to be configured (that is, more than one level of trace can be enabled or disabled). The debug levels are configured one after the other and not in single execution of the command.
Parameter | Type | Description |
---|---|---|
client |
Enter to enable the tracking of the DHCP client operations as per the configured debug levels. The debug statements are generated for the specified trace levels. | |
all |
Enter to generate debug statements for all kind of failure traces. | |
event |
Enter to generate debug statements for DHCP client events that provide DHCP client service status. The DHCP client events are generated when any of packets are sent successfully or when an ACK is received | |
packets |
Enter to generate debug statements for packets related messages. These messages are generated for all events generated during processing of packets. | |
errors |
Enter to generate debug statements for Link State Acknowledge Packet traces | |
bind |
Enter to generate debug statements for trace bind messages. These messages are generated when a DHCP ACK is received. | |
relay |
Enter to enable the tracking of the DHCP relay operations as per the configured debug levels. The debug statements are generated for the specified trace levels. | |
all |
Enter to generate debug statements for all kind of failure traces. | |
errors |
Enter to generate debug statements for trace error code debug messages. These messages are generated for all error events generated. | |
server |
Enter too enable the tracking of the DHCP relay operations as per the configured debug levels. The debug statements are generated for the specified trace levels. | |
all |
Enter to generate debug statements for all kind of failure traces. | |
event |
Enter to generate debug statements for DHCP server events that provide DHCP server service status. The DHCP client events are generated when any of packets are sent successfully or when an ACK is received | |
packets |
Enter to generate debug statements for packets related messages. These messages are generated for all events generated during processing of packets. | |
errors |
Enter to generate debug statements for trace error code debug messages. These messages are generated for all error events generated. | |
bind |
Enter to generate debug statements for trace bind messages. These messages are generated when a DHCP ACK is received. | |
linkage |
Enter to generate debug statements for database linkage messages. | |
snooping |
Enter to enable the tracing of the DHCP snooping module as per the configured debug level. The trace statements are generated for the configured trace levels. | |
entry |
Enter to generate debug statements for function entry traces. The names of the functions entered are displayed in the log. | |
exit |
Enter to generate debug statements for function exit traces. The names of the functions exited are displayed in the log. | |
debug |
Enter to generate debug statements for debug traces. This is used for debugging the packet flow of DHCP snooping functionality. | |
fail |
Enter to generate debug statements for all failure traces. These traces are used for all valid and invalid failures. The valid failures represent the expected error. The invalid failures represent the unexpected error | |
all |
Enter to generate debug statements for all types of traces. |
Privileged EXEC Mode
Tracking of all DHCP modules operation is disabled
iS5Comm# debug ip dhcp client all
iS5Comm# debug ip dhcp relay all
iS5Comm# debug ip dhcp server all
iS5Comm# debug ip dhcp snooping entry