Autonomous Aironet 3602e clientlink not working

[samuel.cornielle]

Guys I cant get my autonomous Aironet 3602e to use ClientLink beamforming

The commands are:

  conf terminal

  int dot11Radio 0

  beamform ofdm

dot11Radio 0 'show run' info shows nothing, unlike my 1602e which says beamform ofdm on the dot11Radio config:

ap-1602e#show run

no ip address
 no ip route-cache
 !
 ssid cisco
 !
 antenna gain 4
 stbc
 beamform ofdm
 mbssid
 power client local
 channel 2412
 station-role root

ap-1602e#show controllers | inc Beam
Hardware Beamforming: Configured Yes, Active Yes
Hardware Beamforming: Configured Yes, Active Yes

[Stephen Rodriguez]

where is that show controllers from?

remember that IOS doesn't show a command that is default

--

Steve

[samuel.cornielle]

Thats on my 1602e. That same command on the 3602e shows nothing...

[Rasika Nayanajith]

Do you have same version of IOS in both models ?

Did you try with different IOS image of your 3602e ? If not give it a try with upgraded image

HTH

Rasika

**** Pls rate all useful responses ***

[samuel.cornielle]

The 3602e has the latest autonomous IOS version (15.3)

The 1602e has the previous autonomous version (15.2)

If I were to try with another image on the 3602e, it would be a previous version... should I try downgrading?

[Rasika Nayanajith]

I do not have 3602e model, but have 3602i for a test. I will let you know output of that AP (in couple of hrs time when I am at office) with the image information.

For a test it won't harm downgrade & see if that is not impacting your production

HTH

Rasika

*** Pls rate all useful responses ***

[Rasika Nayanajith]

Hi Samuel,

I had my 3602 with 802.11ac module plug on to it. It had the same image you used. As you can see, beamforming config was only shown under radio 2

AP3602-3#sh ver | in k9w7
System image file is "flash:/ap3g2-k9w7-mx.153-3.JAB/ap3g2-k9w7-xx.153-3.JAB"

AP3602-3#sh run | in Dot11|beam
interface Dot11Radio0
interface Dot11Radio1
interface Dot11Radio2
 beamform ofdm

AP3602-3#show controllers | in Beam|Dot11
Number of supported simultaneous BSSID on Dot11Radio2: 16
Hardware Beamforming: Configured Yes, Active Yes

If I removed 802.11ac module, then I cannot see those configs even if I manually configure it.

I have changed the IOS image to a previous release & same status.

AP3602-3#sh ver | in k9w7
System image file is "flash:/ap3g2-k9w7-mx.v152_4_jb.201311151055/ap3g2-k9w7-xx.v152_"

AP3602-3#show controllers | in Beam|Dot11
interface Dot11Radio2
Number of supported simultaneous BSSID on Dot11Radio2: 16
Hardware Beamforming: Configured Yes, Active Yes

AP3602-3#sh run | in Dot11|beam
interface Dot11Radio0
interface Dot11Radio1
interface Dot11Radio2
 beamform ofdm

I think there is some problem with these codes on 3600. Best if you could check with TAC & clarify the reason for these differences.

HTH

Rasika

**** Pls rate all useful responses ****

[ddebin001]

Did you find a solution ?

I have the same problem with a 2602i (ap3g2-k9w7-xx.153-3.JBB), I can't activate beamforming...

[samuel.cornielle]

Nope. No solution so far. It just wont show it neither figure out if it is working

[Yahya Jaber · Accepted solution]

Hi,

on those AP's the beam forming is hardware based, and its always enabled. no need to have it disabled.

the 1600 has this command since its software based.

to check if beam forming is enabled on the AP, get something like this

“from your show tech”  "BF "which means Beam Forming is working:

OFDM             : LBF              : HT20-7           : HT20-15          : HT20-23          : HT40-7           :

        HT40-15          : HT40-23          : N-HT40 Dup       : HT20 BF-7        : HT20 BF-15       : HT20 BF-23       :

        HT40 BF-7        : HT40 BF-15       : HT40 BF-23       : HT20 STBC-7      : HT40 STBC-7      :

         2 2 2 2 :

         2 2 2 2 2 2 2 2 :  2 2 2 2 2 2 2 2 :  2 2 2 2 2 2 2 2 :  2 2 2 2 2 2 2 2 :  2 2 2 2 2 2 2 2 :  2 2 2 2 2 2 2 2 :

         2 2 2 2 2 2 2 2 :  2 2 2 2 2 2 2 2 :  2 2 2 2 2 2 2 2 :  2 2 2 2 2 2 2 2 :  2 2 2 2 2 2 2 2 :  2 2 2 2 2 2 2 2 :

         2 2 2 2 2 2 2 2 :  2 2 2 2 2 2 2 2 :  2 2 2 2 2 2 2 2 :  2 2 2 2 2 2 2 2 :  2 2 2 2 2 2 2 2 : 11

its also documented here  https://tools.cisco.com/bugsearch/bug/CSCuo25989/?reffering_site=dumpcr