Wireless Access

Reply
Occasional Contributor II

Debugging DHCP process with when the controller is the client

Hello all,

 

I can't debug the packets sent on dhcp when the controller is the client.

I have the server in the same Lan but I cannot acces to it, I need to follow the process from the controller POV

 

 

Tried with:

 

packet-capture reset-pcap controlpath-pcap
 packet-capture destination local-filesystem
 packet-capture controlpath udp 67,68
show packet-capture controlpath-pcap

 

<no result with controller packets>

 

packet-capture reset-pcap datapath-pcap
packet-capture destination local-filesystem
packet-capture datapath mac <controller-mac> all

 

<no result at all>

 

packet-capture reset-pcap datapath-pcap
packet-capture destination local-filesystem
packet-capture datapath mac <dhcp-server-mac> all

<no result at all>

 

logging network subcat dhcp level debugging

<no really sure about this>

Re: Debugging DHCP process with when the controller is the client

The dhcp debugging command you listed usually works for me.What are you trying to achieve? Have you tried running a pcap on the client as well?


ACMA, ACMP, ACSA, ACDX #985
If my post addresses your query, give kudos:)
Occasional Contributor II

Re: Debugging DHCP process with when the controller is the client

Hello,

 

This commands work fine for me when the controller is the DHCP server.

But I have an vlan on the controller set as dhcp client and the controller dhcp packets (neither discover or request) are not shown on the controlpath nor the datapath

New Contributor

Re: Debugging DHCP process with when the controller is the client

Hi Pedro,

 

I can recommend you try the logging options of the controller. In this case, a debug of the process fpapps (layer 2 and 3 control) may be help you with your problem.

 

#logging network process fpapps level debugging

#show logging level verbose
LOGGING LEVELS
--------------
Facility  Level     Sub Category  Process
--------  -----     ------------  -------
arm       warnings  N/A           N/A
network   debugging N/A           fpapps
security  warnings  N/A           N/A
system    warnings  N/A           N/A
user      warnings  N/A           N/A
wireless  warnings  N/A           N/A
#

You can obtain the logs with the next command (I recommend you play with "include" and "begin" options)

 

#show log all | include fpapps | include DHCP

When you finish, remember to disable it:

  

#no  logging network process fpapps
#show logging level verbose
LOGGING LEVELS
--------------
Facility  Level     Sub Category  Process
--------  -----     ------------  -------
arm       warnings  N/A           N/A
network   warnings  N/A           N/A
security  warnings  N/A           N/A
system    warnings  N/A           N/A
user      warnings  N/A           N/A
wireless  warnings  N/A           N/A
#

You can obtain more info in this link. :)

Occasional Contributor II

Re: Debugging DHCP process with when the controller is the client

Wow this answer really worked for me, ipenido

 

Thank you very much!

Search Airheads
cancel
Showing results for 
Search instead for 
Did you mean: