Wireless Access

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!

Attachment(s)

hlkrm04_debug.txt   3 KB 1 version

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

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 - -

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

(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 -

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

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 -

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

Ready!

You can find in attachment.

Attachment(s)

dhcp_debug.txt   4 KB 1 version

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.

I have just one dhcp.. i tried static ip earlier.. 

192.168.14.100 just stayed in device config.

I try again:

ip: 0.0.0.0

gw: 0.0.0.0

mask: 0.0.0.0

Device config show that IP is 192.168.14.95 but i dont ping from other device and i dont see on Aruba managemant side..

Attachment(s)

dhcp_debugv2.txt   2 KB 1 version

Is that the only device that does not get a dhcp address?

yes just this one. :(