Wireless Access

Reply
Occasional Contributor I

Device authenticated but dont get IP

Hi!

 

Could you help me please?

I would like to connect HLK-RM04 wireless module on the AP 105 (controller: Aruba3400)....

I created new SSID with WPA2-PSK.. when I try connecting its success but device dont get IP address.

If i try it with mobile or laptop its works. They got IP. 

I already tried mac authentication... problem is same, dont get ip....

 

Is it possible that device not supported?

 

Thank you in advance!

 

Guru Elite

Re: Device authenticated but dont get IP

Type "show auth-tracebuf mac 94:db:c9:e3:df:22" and paste that output into your reply..



Colin Joseph
Aruba Customer Engineering

Looking for an Answer? Search the Community Knowledge Base Here: Community Knowledge Base

Occasional Contributor I

Re: Device authenticated but dont get IP

Hi,

 

output:

 

Apr 11 15:54:58 station-up * 94:db:c9:e3:df:22 24:de:c6:51:40:22 - - wpa2 psk aes
Apr 11 15:54:58 wpa2-key1 <- 94:db:c9:e3:df:22 24:de:c6:51:40:22 - 117
Apr 11 15:54:58 wpa2-key2 -> 94:db:c9:e3:df:22 24:de:c6:51:40:22 - 117
Apr 11 15:54:58 wpa2-key3 <- 94:db:c9:e3:df:22 24:de:c6:51:40:22 - 151
Apr 11 15:54:58 wpa2-key4 -> 94:db:c9:e3:df:22 24:de:c6:51:40:22 - 95
Apr 11 16:11:48 station-down * 94:db:c9:e3:df:22 24:de:c6:51:40:22 - -

 

 

Guru Elite

Re: Device authenticated but dont get IP

There is something missing.

 

Try this:

 

show ap remote debug mgmt-frames ap-name 22-APB-1 client-mac 94:db:c9:e3:df:22



Colin Joseph
Aruba Customer Engineering

Looking for an Answer? Search the Community Knowledge Base Here: Community Knowledge Base

Occasional Contributor I

Re: Device authenticated but dont get IP

(Aruba3400-Master-T32) #show ap remote debug mgmt-frames ap-name APB-1 client-mac 94:db:c9:e3:df:22

Traced 802.11 Management Frames
-------------------------------
Timestamp stype SA DA BSS signal Misc
--------- ----- -- -- --- ------ ----
Apr 11 16:11:47 deauth 24:de:c6:51:40:22 94:db:c9:e3:df:22 24:de:c6:51:40:22 15 - (internal only)
Apr 11 15:54:57 assoc-resp 24:de:c6:51:40:22 94:db:c9:e3:df:22 24:de:c6:51:40:22 15 Success
Apr 11 15:54:57 assoc-req 94:db:c9:e3:df:22 24:de:c6:51:40:22 24:de:c6:51:40:22 29 -
Apr 11 15:54:57 auth 24:de:c6:51:40:22 94:db:c9:e3:df:22 24:de:c6:51:40:22 15 Success (seq num 11)
Apr 11 15:54:57 auth 94:db:c9:e3:df:22 24:de:c6:51:40:22 24:de:c6:51:40:22 58 -

Guru Elite

Re: Device authenticated but dont get IP

Nothing unusual.  Please try to reconnect the device and run the command again...



Colin Joseph
Aruba Customer Engineering

Looking for an Answer? Search the Community Knowledge Base Here: Community Knowledge Base

Occasional Contributor I

Re: Device authenticated but dont get IP

Its same, than earlier... :(

Timestamp stype SA DA BSS signal Misc
--------- ----- -- -- --- ------ ----
Apr 11 18:51:55 assoc-resp 24:de:c6:51:40:22 94:db:c9:e3:df:22 24:de:c6:51:40:22 15 Success
Apr 11 18:51:55 assoc-req 94:db:c9:e3:df:22 24:de:c6:51:40:22 24:de:c6:51:40:22 28 -
Apr 11 18:51:55 auth 24:de:c6:51:40:22 94:db:c9:e3:df:22 24:de:c6:51:40:22 15 Success (seq num 11)
Apr 11 18:51:55 auth 94:db:c9:e3:df:22 24:de:c6:51:40:22 24:de:c6:51:40:22 58 -

Guru Elite

Re: Device authenticated but dont get IP

Do this:

 

config t
logging level debugging network subcat dhcp
logging level debugging network process dhcpd

Disconnect then connect your device.  When it fails, type :

 

Show log network 50


Colin Joseph
Aruba Customer Engineering

Looking for an Answer? Search the Community Knowledge Base Here: Community Knowledge Base

Occasional Contributor I

Re: Device authenticated but dont get IP

Ready!

You can find in attachment.

Guru Elite

Re: Device authenticated but dont get IP

It looks like you have two DHCP servers that are answering:

 

Apr 11 19:26:17 :202546:  <DBUG> |dhcpdwrap| |dhcp| Datapath vlan24: OFFER 94:db:c9:e3:df:22 Transaction ID:0xc9e3df22 clientIP=192.168.14.100

Apr 11 19:26:17 :202546:  <DBUG> |dhcpdwrap| |dhcp| Datapath vlan24: OFFER 94:db:c9:e3:df:22 Transaction ID:0xc9e3df22 clientIP=192.168.14.95

 

Your client wants the .100 address:

Apr 11 19:26:24 :202536:  <DBUG> |dhcpdwrap| |dhcp| Datapath vlan24: REQUEST 94:db:c9:e3:df:22 Transaction ID:0xc9e3df22

reqIP=192.168.14.100 Options 3d:0194dbc9e3df22 36:c0a80ef9 37:0103

 

The DHCP server says ok:

Apr 11 19:26:24 :202544:  <DBUG> |dhcpdwrap| |dhcp| Datapath vlan24: ACK 94:db:c9:e3:df:22 Transaction ID:0xc9e3df22 clientIP=192.168.14.100

 

It looks like your client is not responding to the ACK.  I would try to disable one of your DHCP servers if you have two in your environment.

 

 

 

 

 

 



Colin Joseph
Aruba Customer Engineering

Looking for an Answer? Search the Community Knowledge Base Here: Community Knowledge Base

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