Wireless Access

Hi,

i have an issue with a legacy b wireless client. We are migrating some old client devices from a Motorola Symbol wireless system to Aruba but one client fails to stay connected. The client works fine on the Symbol system so there must be a mismatch somewhere with the Aruba kit. I have enabled debugging but do not see anything useful in the log apart from the client does not report an IP address when being placed in a role (via derivation rule).  All the clients are statically addressed and all work aprt from this one. As soon as i switch back to Symbol it works. SNR is very good at >48

Some detail from the log below

May 20 16:02:50 :501109:  <NOTI> |AP LHR4085T4-A1-AP00445-d8:c7:c8:c7:10:8b@10.15.47.28 stm|  Auth request: 00:a0:f8:68:ae:3c: AP 10.15.47.28-d8:c7:c8:f1:08:b0-LHR4085T4-A1-AP00445-d8:c7:c8:c7:10:8b auth_alg 0
May 20 16:02:50 :501093:  <NOTI> |AP LHR4085T4-A1-AP00445-d8:c7:c8:c7:10:8b@10.15.47.28 stm|  Auth success: 00:a0:f8:68:ae:3c: AP 10.15.47.28-d8:c7:c8:f1:08:b0-LHR4085T4-A1-AP00445-d8:c7:c8:c7:10:8b
May 20 16:02:50 :501095:  <NOTI> |stm|  Assoc request @ 16:02:50.549678: 00:a0:f8:68:ae:3c (SN 2165): AP 10.15.47.28-d8:c7:c8:f1:08:b0-LHR4085T4-A1-AP00445-d8:c7:c8:c7:10:8b
May 20 16:02:50 :501100:  <NOTI> |stm|  Assoc success @ 16:02:50.550602: 00:a0:f8:68:ae:3c: AP 10.15.47.28-d8:c7:c8:f1:08:b0-LHR4085T4-A1-AP00445-d8:c7:c8:c7:10:8b
May 20 16:02:50 :501095:  <NOTI> |AP LHR4085T4-A1-AP00445-d8:c7:c8:c7:10:8b@10.15.47.28 stm|  Assoc request @ 16:02:50.512175: 00:a0:f8:68:ae:3c (SN 2165): AP 10.15.47.28-d8:c7:c8:f1:08:b0-LHR4085T4-A1-AP00445-d8:c7:c8:c7:10:8b
May 20 16:02:50 :522035:  <INFO> |authmgr|  MAC=00:a0:f8:68:ae:3c Station UP: BSSID=d8:c7:c8:f1:08:b0 ESSID=TFPRANK VLAN=987 AP-name=LHR4085T4-A1-AP00445-d8:c7:c8:c7:10:8b
May 20 16:02:50 :522077:  <DBUG> |authmgr|  MAC=00:a0:f8:68:ae:3c ingress 0x0x102b5 (tunnel 693), u_encr 8, m_encr 2056, slotport 0x0x2100 , type: local, FW mode: 0, AP IP: 0.0.0.0 mdie 0 ft_complete 0
May 20 16:02:50 :501100:  <NOTI> |AP LHR4085T4-A1-AP00445-d8:c7:c8:c7:10:8b@10.15.47.28 stm|  Assoc success @ 16:02:50.513459: 00:a0:f8:68:ae:3c: AP 10.15.47.28-d8:c7:c8:f1:08:b0-LHR4085T4-A1-AP00445-d8:c7:c8:c7:10:8b
May 20 16:02:50 :522078:  <DBUG> |authmgr|  MAC=00:a0:f8:68:ae:3c, wired: 0, vlan:987 ingress:0x0x102b5 (tunnel 693), ingress:0x0x102b5 new_aaa_prof: TFPRANK_AAA, stored profile: TFPRANK_AAA stored wired: 0 stored essid: TFPRANK, stored-ingress: 0x0x102b5
May 20 16:02:50 :522258:  <DBUG> |authmgr|  "VDR - Add to history of user user 00:a0:f8:68:ae:3c vlan 0 derivation_type Reset VLANs for Station up index 14.
May 20 16:02:50 :522255:  <DBUG> |authmgr|  "VDR - set vlan in user for 00:a0:f8:68:ae:3c vlan 987 fwdmode 0 derivation_type Default VLAN.
May 20 16:02:50 :522258:  <DBUG> |authmgr|  "VDR - Add to history of user user 00:a0:f8:68:ae:3c vlan 987 derivation_type Default VLAN index 15.
May 20 16:02:50 :522255:  <DBUG> |authmgr|  "VDR - set vlan in user for 00:a0:f8:68:ae:3c vlan 987 fwdmode 0 derivation_type Current VLAN updated.
May 20 16:02:50 :522258:  <DBUG> |authmgr|  "VDR - Add to history of user user 00:a0:f8:68:ae:3c vlan 987 derivation_type Current VLAN updated index 16.
May 20 16:02:50 :522246:  <DBUG> |authmgr|  Idle timeout should be driven by STM for MAC 00:a0:f8:68:ae:3c.
May 20 16:02:50 :522254:  <DBUG> |authmgr|  VDR - mac 00:a0:f8:68:ae:3c rolename TFPRANK_ROLE fwdmode 0 derivation_type Initial Role Contained vp not present.
May 20 16:02:50 :522258:  <DBUG> |authmgr|  "VDR - Add to history of user user 00:a0:f8:68:ae:3c vlan 0 derivation_type Reset Role Based VLANs index 17.
May 20 16:02:50 :522019:  <INFO> |authmgr|  MAC=00:a0:f8:68:ae:3c IP=0.0.0.0 Derived role 'TFPRANK_ROLE' from user rules: utype=L2
May 20 16:02:50 :522127:  <DBUG> |authmgr|  {L2} Update role from TFPRANK_ROLE to TFPRANK_ROLE for IP=0.0.0.0.
May 20 16:02:50 :522049:  <INFO> |authmgr|  MAC=00:a0:f8:68:ae:3c,IP=N/A User role updated, existing Role=TFPRANK_ROLE/none, new Role=TFPRANK_ROLE/none, reason= Setting role for user attributes
May 20 16:02:50 :522148:  <DBUG> |authmgr|  Update L3 entry role to TFPRANK_ROLE: IP=??.
May 20 16:02:50 :522254:  <DBUG> |authmgr|  VDR - mac 00:a0:f8:68:ae:3c rolename TFPRANK_ROLE fwdmode 0 derivation_type User Rule Role Contained vp not present.
May 20 16:02:50 :522258:  <DBUG> |authmgr|  "VDR - Add to history of user user 00:a0:f8:68:ae:3c vlan 0 derivation_type Reset Role Based VLANs index 18.
May 20 16:02:50 :522254:  <DBUG> |authmgr|  VDR - mac 00:a0:f8:68:ae:3c rolename NULL fwdmode 0 derivation_type Matched User Rule vp present.
May 20 16:02:50 :524124:  <DBUG> |authmgr|  dot1x_supplicant_up(): MAC:00:a0:f8:68:ae:3c, pmkid_present:False, pmkid:N/A
May 20 16:02:50 :522255:  <DBUG> |authmgr|  "VDR - set vlan in user for 00:a0:f8:68:ae:3c vlan 987 fwdmode 0 derivation_type Current VLAN updated.
May 20 16:02:50 :522258:  <DBUG> |authmgr|  "VDR - Add to history of user user 00:a0:f8:68:ae:3c vlan 987 derivation_type Current VLAN updated index 19.
May 20 16:02:50 :522260:  <DBUG> |authmgr|  "VDR - Cur VLAN updated 00:a0:f8:68:ae:3c mob 0 inform 1 remote 0 wired 0 defvlan 987 exportedvlan 0 curvlan 987.
May 20 16:02:50 :522243:  <DBUG> |authmgr|  MAC=00:a0:f8:68:ae:3c Station Updated Update MMS: BSSID=d8:c7:c8:f1:08:b0 ESSID=TFPRANK VLAN=987 AP-name=LHR4085T4-A1-AP00445-d8:c7:c8:c7:10:8b
May 20 16:02:50 :501102:  <NOTI> |AP LHR4085T4-A1-AP00445-d8:c7:c8:c7:10:8b@10.15.47.28 stm|  Disassoc from sta: 00:a0:f8:68:ae:3c: AP 10.15.47.28-d8:c7:c8:f1:08:b0-LHR4085T4-A1-AP00445-d8:c7:c8:c7:10:8b Reason STA has left and is disassociated

Thanks

Do you have band steering or spectrum load balancing  turned on by any chance ?

No, neither are enabled, it is 2.4Ghz only

Also do a show ap association client-mac 

Sorry for delay on replying to this

acl is any any any permit

ap association client -mac

Association Table
-----------------
Name                                    bssid              mac                auth  assoc  aid  l-int  essid    vlan-id  tunnel-id  phy  assoc. time  num assoc  Flags  Band steer moves (T/S)
----                                    -----              ---                ----  -----  ---  -----  -----    -------  ---------  ---  -----------  ---------  -----  ----------------------
LHR4085T4-A1-AP00445-d8:c7:c8:c7:10:8b  d8:c7:c8:f1:08:b0  00:a0:f8:68:ae:3c  y     y      1    100    TFPRANK  987      0x104ba    g    2s           54         A      0/0

00:a0:f8:68:ae:3c-d8:c7:c8:f1:08:b0 Stats
------------------------------------------
Parameter                            Value
---------                            -----
Channel                              1
Channel Frame Retry Rate(%)          0
Channel Frame Low Speed Rate(%)      0
Channel Frame Non Unicast Rate(%)    0
Channel Frame Fragmentation Rate(%)  0
Channel Frame Error Rate(%)          2
Channel Bandwidth Rate(kbps)         16
Channel Noise                        96
Client Frame Retry Rate(%)           0
Client Frame Low Speed Rate(%)       0
Client Frame Non Unicast Rate(%)     0
Client Frame Fragmentation Rate(%)   0
Client Frame Receive Error Rate(%)   0
Client Bandwidth Rate(kbps)          0
Client Tx Packets                    5876
Client Rx Packets                    4535
Client Tx Bytes                      138025
Client Rx Bytes                      437586
Client SNR                           47

The client bridge is a 3 Com CB3000 (I believe this used to be manufactured by Motorola). I enabled g rates but it had no effect and I also enabled 802.11d which again had no effect.

The client associates for a maximum of 3 seconds. I have forced the AP to several different channels but still no luck.

There are two other CB3000's that connect fine and as far as I can see have the same settings.

If you put all three 3-COM devices in the same area, would two of them connect and this other one would have a problem?  If so, I'd think you're wasting time troubleshooting it as an infrastructure issue and would go ahead and reset the device.

All 3 devices connect immediately to the Symbol infrastructure but one will not connect to Aruba when I switch the AP's. I will try resetting the problem device

---

@ssmith wrote:

No, neither are enabled, it is 2.4Ghz only

---

If it is a Motorola device, please check out this article here:  https://arubanetworkskb.secure.force.com/pkb/articles/Troubleshooting/Why-Motorola-MC2180-bar-codes-is-unable-to-connect

If it is not, please tell us what make and model the device is..