ArubaOS and Controllers

Reply
Occasional Contributor II
Posts: 100
Registered: ‎11-05-2009

Connection Problem in Linux

Hello all,

I am very new to Aruba (1st day having been loaned some equipment from Aruba), so go easy on me!

I've created a couple of Virtual APs (including the SSID / AAA profiles etc). One provides open access, the other WPA2 enterprise.

If I connect my laptop in Linux to either SSID, I am granted access and can ping my default route for ~15 pings. After this I get Destination Host Unreachable, the Laptop thinks it is connected.

Under Controller --> Clients the Laptop is listed with an 'authenticated' user role to begin with, but eventually disapears from here (all the time the laptop says it is connected).

If I boot into Windows then it stays connected with full connectivity.

Looking at the Client Debug I get under Windows:
Jan 4 12:23:53 stm Assoc request @ 12:23:53.808621: 00:21:6a:75:24:7e (SN 97): AP 172.16.0.253-00:24:6c:80:c9:39-AP105-1-93
Jan 4 12:23:53 stm Assoc success @ 12:23:53.814474: 00:21:6a:75:24:7e: AP 172.16.0.253-00:24:6c:80:c9:39-AP105-1-93
Jan 4 12:23:53 stm Sending STA 00:21:6a:75:24:7e message to Auth and Mobility Unicast Encr Open Multicast Encr Open VLAN 0xe0
Jan 4 12:23:53 authmgr MAC=00:21:6a:75:24:7e Station UP: BSSID=00:24:6c:80:c9:39 ESSID=aruba-college VLAN=224 AP-name=AP105-1-93
Jan 4 12:23:53 authmgr MAC=00:21:6a:75:24:7e ingress 0x10cb (tunnel 11), u_encr 1, m_encr 1, slotport 0x1020
Jan 4 12:23:53 authmgr MAC=00:21:6a:75:24:7e def_vlan 224 derive vlan: 0 auth_type 0 auth_subtype 0
Jan 4 12:23:53 mobileip Station 00:21:6a:75:24:7e, 0.0.0.0: Received association on ESSID: aruba-college Mobility service ON, HA Discovery on Association Off, Fastroaming Disabled, AP: Name AP105-1-93 Group whitechapel BSSID 00:24:6c:80:c9:39, phy a, VLAN 224
Jan 4 12:23:54 authmgr MAC=00:21:6a:75:24:7e IP=10.228.56.1 User miss: ingress=0x10cb, VLAN=224
Jan 4 12:23:54 authmgr MAC=00:21:6a:75:24:7e IP=10.228.56.1 User entry added: reason=Sibtye
Jan 4 12:33:13 stm Deauth from sta: 00:21:6a:75:24:7e: AP 172.16.0.253-00:24:6c:80:c9:39-AP105-1-93 Reason Unspecified Failure
Jan 4 12:33:13 stm Sending STA 00:21:6a:75:24:7e message to Auth and Mobility Unicast Encr Open Multicast Encr Open VLAN 0xe0
Jan 4 12:33:13 mobileip Station 00:21:6a:75:24:7e, 0.0.0.0: Received disassociation on ESSID: aruba-college Mobility service ON, HA Discovery on Association Off, Fastroaming Disabled, AP: Name AP105-1-93 Group whitechapel BSSID 00:24:6c:80:c9:39, phy a, VLAN 224
Jan 4 12:33:13 authmgr MAC=00:21:6a:75:24:7e Station DN: BSSID=00:24:6c:80:c9:39 ESSID=aruba-college VLAN=224 AP-name=AP105-1-93
Jan 4 12:33:13 authmgr MAC=00:21:6a:75:24:7e ingress 0x10cb (tunnel 11), u_encr 1, m_encr 1, slotport 0x1020
Jan 4 12:33:13 stm Station 00:21:6a:75:24:7e: Clearing state

and under Linux:
Jan 4 14:37:38 stm Assoc request @ 14:37:38.812188: 00:21:6a:75:24:7e (SN 2239): AP 172.16.0.253-00:24:6c:80:c9:39-AP105-1-93
Jan 4 14:37:38 stm Assoc success @ 14:37:38.817981: 00:21:6a:75:24:7e: AP 172.16.0.253-00:24:6c:80:c9:39-AP105-1-93
Jan 4 14:37:38 stm Sending STA 00:21:6a:75:24:7e message to Auth and Mobility Unicast Encr Open Multicast Encr Open VLAN 0xe0
Jan 4 14:37:38 mobileip Station 00:21:6a:75:24:7e, 0.0.0.0: Received association on ESSID: aruba-college Mobility service ON, HA Discovery on Association Off, Fastroaming Disabled, AP: Name AP105-1-93 Group whitechapel BSSID 00:24:6c:80:c9:39, phy a, VLAN 224
Jan 4 14:37:38 mobileip Station 00:21:6a:75:24:7e, 0.0.0.0: Mobility trail, on switch 172.22.16.2, VLAN 224, AP AP105-1-93, aruba-college/00:24:6c:80:c9:39/a
Jan 4 14:37:38 authmgr MAC=00:21:6a:75:24:7e Station UP: BSSID=00:24:6c:80:c9:39 ESSID=aruba-college VLAN=224 AP-name=AP105-1-93
Jan 4 14:37:38 authmgr MAC=00:21:6a:75:24:7e ingress 0x10cb (tunnel 11), u_encr 1, m_encr 1, slotport 0x1020
Jan 4 14:37:38 authmgr MAC=00:21:6a:75:24:7e IP=138.37.238.188 Send mobility delete message, flags=0x20
Jan 4 14:37:38 authmgr {138.37.238.188} datapath entry deleted
Jan 4 14:37:38 authmgr MAC=00:21:6a:75:24:7e IP=138.37.238.188 User entry deleted: reason=essid change
Jan 4 14:37:38 authmgr 00:21:6a:75:24:7e: station datapath entry deleted
Jan 4 14:37:38 authmgr MAC=00:21:6a:75:24:7e def_vlan 224 derive vlan: 0 auth_type 0 auth_subtype 0
Jan 4 14:37:38 authmgr MAC=00:21:6a:75:24:7e IP=138.37.238.188 Authentication result=Authentication Successful method=radius-accounting server=scarab
Jan 4 14:37:38 authmgr MAC=00:21:6a:75:24:7e IP=10.226.38.1 User miss: ingress=0x10cb, VLAN=224
Jan 4 14:37:38 authmgr MAC=00:21:6a:75:24:7e IP=10.226.38.1 User entry added: reason=Sibtye
Jan 4 14:43:37 authmgr MAC=00:21:6a:75:24:7e IP=10.226.38.1 Sending ping 1 of 3 (id=8214, seq=31)
Jan 4 14:43:42 authmgr MAC=00:21:6a:75:24:7e IP=10.226.38.1 Sending ping 2 of 3 (id=8214, seq=32)
Jan 4 14:43:47 authmgr MAC=00:21:6a:75:24:7e IP=10.226.38.1 Sending ping 3 of 3 (id=8214, seq=33)


The ping fails after the few few seconds (syslog reports ERROR: No TX rate available). I wouldn't expect the controller to be able to ping 10.226.38.1, although this tries after ~ 5 minutes of no connectivity.

Has anyone come across a problem like this before, or got any ideas what might be causing it or what I can try to resolve it?
Aruba Employee
Posts: 664
Registered: ‎04-15-2009

Re: Connection Problem in Linux

Did the client get the same IP both times? It looks like it got 10.226.38.1. the second time it associated. Is that a valid IP on VLAN 224? Is one of the two clients set for a static IP and the other for DHCP (or both for static and configured with different IP addresses)?

The 3 pings at the end of the Linux debug are normal. By default, after 5 minutes of no activity for a client (user idle-timeout), we send ICMP messages to that client to see if it is still connected.

What NIC/driver versions are you using on the Linux client? This may be a simple driver issue.

What ArubaOS version are you using? You can get that from the GUI under the Inventory screen or from the CLI by doing "show version".
Occasional Contributor II
Posts: 100
Registered: ‎11-05-2009

Re: Connection Problem in Linux

Thanks for your quick reply.

That is a valid IP address for the VLAN. I think windows gets a different IP address but that in itself isn't a problem. Both Windows & Linux are configured for DHCP and it is up to the DHCP server what address to allocate.

The WiFi card is a Intel 5300. It's the stock driver in Ubuntu 9.10 (2.6.31 kernel).

Aruba version is 3.4.1.1.

From a few more tests which I have been doing, if I turn off band steering and the laptop connects at 2.4GHz it seems fine. If I turn band steering back on the problem occurs.

I have just turned off band sterring and only allow 'a' band. I got to 259 ping replies before it stopped. I've now set it to 'g' band only and I'm up to 320 (and still going).
Aruba Employee
Posts: 19
Registered: ‎04-03-2007

Re: Connection Problem in Linux

Looking at what you described, I'd first check your ability of your system to connect to the 5Ghz band (I know the 5300 should be allowing this, but your drivers might not be configured that way).

In order to do this, just create a new SSID, broadcasting only in 11a and see whether the laptop can connect to it.
You might want to repeat the operation on various channels to have a better overview.
Occasional Contributor II
Posts: 100
Registered: ‎11-05-2009

Re: Connection Problem in Linux

Thanks. I have been able to connect to the a band. It 'feels' like there are more problems when connecting at a than g. What I will try tomorrow is turning off the n feature as I have used my laptop many many times a/g but only with this Aruba kit at an/gn.
Guru Elite
Posts: 21,269
Registered: ‎03-29-2007

Looks like

...you're not the only one with the problem on AN: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/420678


Colin Joseph
Aruba Customer Engineering

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

Occasional Contributor II
Posts: 100
Registered: ‎11-05-2009

Re: Connection Problem in Linux

OK, thanks. I'll try some of the suggestions in that thread.

At least I now know it isn't an issue with the Aruba kit itself.
Search Airheads
Showing results for 
Search instead for 
Did you mean: