1230AG non-root bridge not associating

Hello everyone,
I am new at setting up root and non-root bridges. I am trying to set-up three 1230ag devices.
One as the root and the othe two as non-root, I copied the config txt from the root and
copied that into the two I am going to use for the non-root. That way the ssid's are the
same. When I set the role to non-root the radio is not enabled and I get a message saying
Interface Dot11Radio0,cannot associate:No Response
Does any know what I am doing wrong, and how to fix it
Thanks

The radio interface will go down in response to being configured as a non-root bridge, so that much is working. But there must be a configuration error if it won't associate. Can you post the configs so we can review them?
Are the bridges mounted, or are they on your desk?

Similar Messages

7920 associates to root bridge but not to non-root bridge

I have 7920s using open authentication with WEP128 cipher. I have two 1300 root AP's (with client support) and three non-root AP's (also client support) in the same lab area. The root AP's and non-Root AP's associate and link to each other no problem. However, the 7920's will only associate with the Root APs. If I power down the root APs, the 7920s show "no AP found". I've verified SSID and WEP128 keys. I've also noted that the root AP does have a channel specified under dot11radio0 but the non-roots do not. Do the 7920's just scan for any channel until it finds an association or do I need to specify a channel in the non-root bridges?
Thanks,
Mike.

With static WEP, the authentication is happening at the AP level. Will want to ensure non-root is associated to a root though otherwise the interface may be in "reset" state.
The 7920 will look at these 2 as individual APs regardless of channel. Non-roots should have the same channel as the root, otherwise will not be able to communicate.

Non-root bridge association problem

I have an installation using Cisco 1242 Access Points (IOS) as bridges
in 5Ghz band, and as AP in 2,4 GHz band. Sometimes I get problems
with the non-root bridges, after mains outage, they will not
associate to the root bridge. Command "dot11 do 1 carrier busy"
issued to the non-root bridge helps, but sometimes I have to use it
several times. Have anybody any idea about possible cause?
Thanks

Hi Frank,
I think I have found the reason of my troubles. It is the following configuration command:
(interface Dot11Radio1)
world-mode dot11d country CZ outdoor
which is not only not-needed on the non-root bridge AP, it prevents associating the non-root bridge to the root-bridge AP. It does not cause the troubles on each root non-root couple. The troubles are more frequent with IOS version 12.3(11)JA or 12.3(8)JEA than with 12.3(8)JA2.
Regards
Frantisek Opravil

Non-root bridges associating with each other.

We have a point to multi-point bridge setup with 3 BR1310s. One is set to be a root bridge and the other two are set to be non-root bridges. From past experience (not to mention Cisco documentation) I would expect the 2 non-roots to associate to the root. What is happening is that one of the non-roots associates with the root and the other non-root associates with the first non-root. The good bit is that everything still works, the puzzling bit is why this is happening, the bridges are physically in a V pattern so there's no reason for the second non-root to behave as it is, even if we force it off the first non-root it just jumps right back in there again. Bridges are all running 12.3.4-JA.

Configurations of both non-root bridges attached. I've just found out that the customer has mounted the second non-root bridge in such a way that there is probably no line of site to the root bridge (failing to follow clear instructions!) which explains why we can't get it to associate with the root bridge but doesn't explain how it can associate with the other non-root. The only thing I can think of is that both are "non-root with clients" and the second bridge is being accepted as a client rather than a bridge.

1310 Root Bridge will not Authenticate with 350 Non Root Bridge

I've exhausted myself solving this issue.
I have a 1310 set as a root bridge using WEPS. I have a 350 set as a non root bridge/without clients, also using WEPS (they both use the same SSID)
The 350 will not authenticate to the 1310. After doing a Carrier Busy Test, it is clear the 350 see's the 1310 with signal strengh of 100 percent.
(I have a test lab setup in my office)
If I make the 350 the Root Bridge and the 1310 the Non Root, The 1310 will authenticate to the 350.
I hoping someone else has seen this problem and can enlighten me.
Thank you.

I have successfully configured a 1310 Bridge as a Root Bridge and a BR350 Bridge and a Non Root Bridge/with Clients. I also had to force the 1310 to operate at 11MB only.
As soon as I make the BR350 Bridge a Non Root Bridge/without Clients, the authentication is dropped between the two.
I was hoping I could transition to the 1310 one unit at a time since I have over a dozen 350's to replace.

Non-root is not associate with root

I am working to setup the non-root associate with root. I have checked every configuration from the root are the same as non-root. Accept it set to non-root.
- It is the same VLAN, SSID, authentication is open. I have encryption from both sides are the same.
It is still not associated. What else should I check from the non-root to get association? Please give me some helps
I am really appreciated that.
The root configuration:
version 12.4
no service pad
service timestamps debug datetime msec
service timestamps log datetime msec localtime show-timezone
service password-encryption
hostname Root_Bridge
no logging console
aaa new-model
aaa group server radius rad_eap
aaa group server radius rad_mac
aaa group server radius rad_acct
aaa group server radius rad_admin
aaa group server tacacs+ tac_admin
aaa group server radius rad_pmip
aaa group server radius dummy
aaa authentication login default local
aaa authentication login eap_methods group rad_eap
aaa authentication login mac_methods local
aaa authorization exec default local
aaa accounting network acct_methods start-stop group rad_acct
aaa session-id common
resource policy
clock timezone MST -7
clock save interval 24
ip subnet-zero
ip domain name Bridge
ip ssh time-out 60
ip ssh version 2
no dot11 igmp snooping-helper
dot11 vlan-name Management vlan 51
dot11 vlan-name User vlan 11
dot11 ssid LOCALBRIDGE
   vlan 51
   authentication open
   infrastructure-ssid
dot11 network-map
crypto pki trustpoint TP-self-signed-4076113752
enrollment selfsigned
subject-name cn=IOS-Self-Signed-Certificate-4076113752
revocation-check none
rsakeypair TP-self-signed-4076113752
crypto pki certificate chain TP-self-signed-4076113752
certificate self-signed 01
30820261 308201CA A0030201 02020101 300D0609 2A864886 F70D0101 04050030
31312F30 2D060355 04031326 494F532D 53656C66 2D536967 6E65642D 43657274
69666963 6174652D 34303736 31313337 3532301E 170D3032 30333031 30303030
33345A17 0D323030 31303130 30303030 305A3031 312F302D 06035504 03132649
4F532D53 656C662D 5369676E 65642D43 65727469 66696361 74652D34 30373631
31333735 3230819F 300D0609 2A864886 F70D0101 01050003 818D0030 81890281
8100B329 87F691CA 1107EC3A 9EF4676D 2F96A7E4 42DBB88F 426D78C1 0E9E09A0
8F5EA9A1 DF88C33A A0DF128A E13E6E59 E9232487 0F5C953C 274DF314 1F48544F
E213D232 85B1E45A 4D186A9E FF9581E6 3E471891 16B627B6 CB3D8F01 BCFF89E0
77E8EA44 0E255F75 BFF1299A B3198E9B 61B3056B 8F365D98 2A8D463E F3122C47
B80D0203 010001A3 81883081 85300F06 03551D13 0101FF04 05300301 01FF3032
0603551D 11042B30 29822737 3332385F 42726964 67652E64 61766973 2D6D6F6E
7468616E 2E616363 2E64732E 61662E6D 696C301F 0603551D 23041830 1680145F
9DB7F2A6 BD563ACB 429F6938 6AF9D336 69139F30 1D060355 1D0E0416 04145F9D
B7F2A6BD 563ACB42 9F69386A F9D33669 139F300D 06092A86 4886F70D 01010405
00038181 00372387 521D029A FAE2F579 73EDCF3B FDF262EE 5DF6154E 5469A5BD
6630E5FD C8A1311A A24493D4 D1856862 8979692B CDFE65D7 29E97B60 FCC37584
A27FA332 9CC5F175 2EDC871C D41BA4F5 A50634DE 75210305 47240D4F A30D0046
532F68ED 569CE374 98C5F53D A417CFBF 3A93C98A D399B06E A73E61AB D4889452
0B695B54 86
quit
bridge irb
interface Dot11Radio0
no ip address
no ip route-cache
encryption key 1 size 128bit 7 E99521751C16125A7754722A6B72 transmit-key
encryption key 2 size 128bit 7 1857F02303182327EA1A9242A53B
encryption key 3 size 128bit 7 FE1CF103855EBB2763224F129556
encryption key 4 size 128bit 7 19A03A5D596B029A01C208EF1C0F
encryption mode ciphers wep128
encryption vlan 11 key 1 size 128bit 7 419258EC0B7E6C7413C571760B67 transmit-key
encryption vlan 11 key 2 size 128bit 7 AB3C5B091B37223F39306B1F7442
encryption vlan 11 key 3 size 128bit 7 3E1CF103855EBB2763224F129556
encryption vlan 11 key 4 size 128bit 7 E858C5382B5D5E372A6C0438604C
encryption vlan 11 mode wep mandatory
encryption vlan 51 key 1 size 128bit 7 90792B34ACD2C8D18A0B7AF3AC68 transmit-key
encryption vlan 51 key 2 size 128bit 7 72063EA2FEF03A39E5468E92A7C5
encryption vlan 51 key 3 size 128bit 7 8607AEADB49EE0B7E4529770D9AE
encryption vlan 51 key 4 size 128bit 7 F60210B48CB39887A59255187D6D
encryption vlan 51 mode wep mandatory
ssid LOCALBRIDGE
speed basic-6.0 basic-9.0 basic-12.0 basic-18.0 basic-24.0 basic-36.0 basic-48.0 basic-54.0
packet retries 128
station-role root
rts threshold 4000
rts retries 128
cca 87
concatenation
distance 5
beacon period 20
infrastructure-client
interface Dot11Radio0.11
encapsulation dot1Q 11
no ip route-cache
no snmp trap link-status
bridge-group 11
interface Dot11Radio0.51
encapsulation dot1Q 51 native
no ip route-cache
no snmp trap link-status
bridge-group 1
interface FastEthernet0
no ip address
no ip route-cache
hold-queue 80 in
interface FastEthernet0.11
encapsulation dot1Q 11
no ip route-cache
no snmp trap link-status
bridge-group 11
interface FastEthernet0.51
encapsulation dot1Q 51 native
no ip route-cache
no snmp trap link-status
bridge-group 1
interface BVI1
ip address 192.168.0.5 255.255.255.0
no ip route-cache
no ip http server
ip http authentication aaa
no ip http secure-server
ip http help-path http://www.cisco.com/warp/public/779/smbiz/prodconfig/help/eag
ip radius source-interface BVI1
logging history informational
snmp-server view dot11view ieee802dot11 included
snmp-server community PUBLICSTRING RW
snmp-server chassis-id Bridge
snmp-server enable traps snmp authentication linkdown linkup coldstart warmstart
snmp-server enable traps tty
snmp-server enable traps entity
snmp-server enable traps disassociate
snmp-server enable traps deauthenticate
snmp-server enable traps authenticate-fail
snmp-server enable traps dot11-qos
snmp-server enable traps wlan-wep
snmp-server enable traps config
snmp-server enable traps syslog
snmp-server enable traps cpu threshold
snmp-server enable traps aaa_server
snmp-server enable traps envmon
snmp-server host 192.168.9.10 PUBLICSTRING
tacacs-server host 192.168.6.100
tacacs-server host 192.168.4.100
tacacs-server directed-request
radius-server attribute 32 include-in-access-req format %h
radius-server vsa send accounting
bridge 1 protocol ieee
bridge 1 route ip
line con 0
access-class 111 in
line vty 0 4
access-class 111 in
line vty 5 15
access-class 111 in
end
The non-root configuration:
version 12.4
no service pad
service timestamps debug datetime msec
service timestamps log datetime msec
service password-encryption
hostname Bridge
logging console informational
logging monitor informational
aaa new-model
aaa group server radius rad_eap
aaa group server radius rad_mac
aaa group server radius rad_acct
aaa group server radius rad_admin
aaa group server radius rad_pmip
aaa group server radius dummy
aaa authentication login default local
aaa authentication login eap_methods group rad_eap
aaa authentication login mac_methods local
aaa authorization exec default local
aaa accounting network acct_methods start-stop group rad_acct
aaa cache profile admin_cache
all
aaa session-id common
resource policy
clock timezone MST -7
clock save interval 24
ip subnet-zero
ip domain name Bridge
no dot11 igmp snooping-helper
dot11 activity-timeout bridge default 3600
dot11 vlan-name Management vlan 51
dot11 vlan-name User vlan 11
dot11 ssid LOCALBRIDGE
   vlan 51
   authentication open
   infrastructure-ssid
dot11 network-map
no crypto provisioning petitioner
bridge irb
interface Dot11Radio0
no ip address
no ip route-cache
encryption key 1 size 128bit 7 E99521751C16125A7754722A6B72 transmit-key
encryption key 2 size 128bit 7 1857F02303182327EA1A9242A53B
encryption key 3 size 128bit 7 FE1CF103855EBB2763224F129556
encryption key 4 size 128bit 7 19A03A5D596B029A01C208EF1C0F
encryption mode ciphers wep128
encryption vlan 11 key 1 size 128bit 7 419258EC0B7E6C7413C571760B67 transmit-key
encryption vlan 11 key 2 size 128bit 7 AB3C5B091B37223F39306B1F7442
encryption vlan 11 key 3 size 128bit 7 3E1CF103855EBB2763224F129556
encryption vlan 11 key 4 size 128bit 7 E858C5382B5D5E372A6C0438604C
encryption vlan 11 mode wep mandatory
encryption vlan 51 key 1 size 128bit 7 90792B34ACD2C8D18A0B7AF3AC68 transmit-key
encryption vlan 51 key 2 size 128bit 7 72063EA2FEF03A39E5468E92A7C5
encryption vlan 51 key 3 size 128bit 7 8607AEADB49EE0B7E4529770D9AE
encryption vlan 51 key 4 size 128bit 7 F60210B48CB39887A59255187D6D
encryption vlan 51 mode wep mandatory
ssid LOCALBRIDGE
speed basic-6.0 basic-9.0 basic-12.0 basic-18.0 basic-24.0 basic-36.0 basic-48.0 basic-54.0
packet retries 128
station-role non-root bridge
rts threshold 4000
rts retries 128
cca 87
concatenation
beacon period 20
infrastructure-client
interface Dot11Radio0.11
encapsulation dot1Q 11
no ip route-cache
no snmp trap link-status
bridge-group 11
interface Dot11Radio0.51
encapsulation dot1Q 51 native
no ip route-cache
no snmp trap link-status
bridge-group 1
interface FastEthernet0
no ip address
no ip route-cache
hold-queue 80 in
interface FastEthernet0.11
encapsulation dot1Q 11
no ip route-cache
no snmp trap link-status
bridge-group 11
interface FastEthernet0.51
encapsulation dot1Q 51 native
no ip route-cache
no snmp trap link-status
bridge-group 1
interface BVI1
ip address 192.168.0.10 255.255.255.0
no ip route-cache
ip http server
no ip http secure-server
ip http help-path http://www.cisco.com/warp/public/779/smbiz/prodconfig/help/eag
ip radius source-interface BVI1
snmp-server community PUBLICSTRING RW
snmp-server enable traps snmp authentication linkdown linkup coldstart warmstart
snmp-server enable traps tty
snmp-server enable traps entity
snmp-server enable traps disassociate
snmp-server enable traps deauthenticate
snmp-server enable traps authenticate-fail
snmp-server enable traps dot11-qos
snmp-server enable traps wlan-wep
snmp-server enable traps config
snmp-server enable traps syslog
snmp-server enable traps cpu threshold
snmp-server enable traps aaa_server
snmp-server enable traps envmon
snmp-server host 192.168.9.10 PUBLICSTRING
tacacs-server host 192.168.6.100
tacacs-server host 192.168.4.100
tacacs-server directed-request
radius-server attribute 32 include-in-access-req format %h
radius-server vsa send accounting
bridge 1 protocol ieee
bridge 1 route ip
bridge 11 protocol ieee
line con 0
line vty 0 4
end

what happens if you go completely open, no WEP?
and I wouldn't use WEP, it's very breakable.
Steve

Can one Root Bridge support multiple non-root bridges?

Hey gang,
I have a pretty simple question here I think
I have a wireless bridge currently setup to support a separate office building on our property about 200 yards away from the main building. The wireless bridge has been working great and was a much cheaper solution when compared to the cost of making a fiber drop to this building. The needs of our business have changed (go figure), to include a warehouse building also on the backside of the property. It's not feasible to run a cable between these two building either. So I need to create another wireless bridge to this back warehouse as well. My question is can I just use another non-root bridge to link to the root bridge already in place, or does each wireless bridge require one root bridge and one non-root bridge?
I have good LoS to both buildings from where the current root bridge is, so if two non-root bridges can talk to one root bridge I should be able to just an additional non-root bridge and be good to go. But if wireless bridges are meant to be a one to one setup, then I'll need to setup an additional root bridge to link to the new non-root bridge?
It seems like you should be able to have one root bridge link to multiple non-root bridges but I haven't been able to find any clear examples of this being done.
Thanks in advance for the help!

That was just too easy.
I copied the configuration from the working non-root bridge to my laptop. I changed out the ip address of the BVI interface. I uploaded the configuration to the new 1300 bridge. I plugged it in and pointed the yagi antenna in the general direction of the original root bridge and started pinging the new 1300. Success!
I'll use my spare 1300 to get service up and running in the warehouse by the end of the week and I'll just need to order one more 1300 to make sure I have spare on hand if needed.
Thanks again!

B1400 non-root does not display/monitor temperature

I have root and non-root B1410 bridges. The root bridges will show temperatures in the GUI. The non-root do not. They show a WARNING: No Reading temperature monitoring is at 'INITIALIZE' state. What does this mean? I have not been able to find any reference. Other than root/non-root parms, I see nothing that is different in these configurations. They are in remote locations and temperature reporting is needed.

Thanks for the response. After some digging I found this BUG.
It says fixed in 12.3(8)JA
BUT I CANNOT FIND 12.3(8)JA for the 1400....
BUG ID: CSCsb63034
Bug Details
Headline show env No Reading Temperature monitoring is at INITIALIZE non-root
Product br1410
Feature OTHERS Duplicate of
Severity 3 Severity help Status Verified Status help
First Found-in Version 12.3(4)JA First Fixed-in Version 12.3(8)JA Version help
Release Notes
Symptom:
Non-root bridge running 12.3.4.JA & greater 'show env' output sometimes shows:
Environmental Statistics
Environmental status as of 09:47:18 S Aug 8 2005
Data is 55 second(s) old, refresh in 5 second(s)
WARNING: No Reading temperature monitoring is at 'INITIALIZE' state.
No Reading temperature is at 0 (C)
Workaround:
None but this appears to be cosmetic.
-pat

1250 802.11N series in root/non-root bridge mode

Using Yagi's, low loss cable, antenna outside, AP inside.
When operating autonomous 1250 series in root/non-root bridge mode, can I use 802.11N radios? Is it supported?
Or would it be better to use 1242's? This is for a customer, no time for testing, need rock solid design, in and out configuration...

@leolaohoo -
I was just asking for a definitive answer, weather its affirmative or negative, is there a benefit to using the 1252 over the 1242 giving the cost of each, since as you said the 802.11N can not be used to bridge, than I would say a 1242 is better fit for the AP bridge of 350', clear line of site over the 1252.

Root Bridge+Clients with Non-Root Bridge+Clients Howto?

Hi, i have two 1242AG access points. I would like to setup a bridge between the two to bridge ethernet lan segments, furthermore i would like to be able to connect wireless clients to either of the access points so i can get maximum range.
I did what i thought was correct, created the first access point a 'root bridge with wireless clients', and assigned the ssid.
I set the second access point to 'non-root bridge with wireless clients' amd set the same ssid as the first access point.
I cant even get the root bridge to work, i turn it on, it brings the radio interface up but i cannot connect with my wireless clients, infact i cannot even see the SSID!
Do i need to 'Set Single Guest Mode SSID' for the radios? What does that command do?
Any ideas? A link to config example would be much apreciated.
Thanks,
Chris

Hi, first, thanks for the help.
Second, this incompatibility is only valid
for RFC1042 or it is valid for 802.11g?
Third, If I configure my 1242 as Acess Point, and the 340 series as Client or Brigde_only, they should not talk too?
Sorry for the bad english...

Root-Bridge and Non-Root Bridge Support

I was wondering if the ISR Routers (Cisco 1811w) support the root-bridge and non-root-bridge feature. If not is there another device apart from the 1310 and 1410 bridges that support this feature?
Thank You,
VT

Hi VT,
The ISR AP supports both of these roles;
Access Point Link Role Flexibility
Access Point Link Role Flexibility allows access point radios to operate in a combination of radio roles,
such as access point root, bridge root (with or without clients), bridge nonroot (with or without clients).
This provides a more flexible deployment scheme to support the various applications requirement. Note
that the ISR AP does not support access point repeater and WGB.
Wireless Non-Root Bridge
The wireless non-root bridge allows the access point radio to operate as the remote node in a point to
point or point to multi-point network.
Wireless Root Bridge
The wireless root bridge role provides support for both point-to-point or point to multi-point bridging.
http://www.cisco.com/en/US/docs/ios/12_4/12_4x/release/notes/rn1800xj.html
Hope this helps!
Rob

Non-root bridge 1242AG with root 340 bridge series

I have a configuration with a root bridge 340 series and about 5 non-root bridge 340 series. I want to add a 1242 non root bridge, but the new device can't see the others, and neither the others can see the 1242.
Is there an issue in connecting these two devices in this configuration?

Hi, first, thanks for the help.
Second, this incompatibility is only valid
for RFC1042 or it is valid for 802.11g?
Third, If I configure my 1242 as Acess Point, and the 340 series as Client or Brigde_only, they should not talk too?
Sorry for the bad english...

Root-bridge non-root bridge security

Using AP1231, I have a point-to-point configuration with the option "without wireless clients". I have enabled WPA2-PSK/AES-CCMP to the infrastructureSSID/nativeVLAN.
Does this security automatically apply to the other SSID/VLAN I have configured? Or do I need to configure additional security on the other SSID/VLAN? Please advise. Thanks!

From your diagram, AP3 is the root bridge because it is connected to ISP, so AP2 will be a repeater, but 1242 can't work both as repeater and AP. So the diagram won't work. you have 3 alternative options:
1. not let AP2 to connect wireless clients, only configure AP2 as a repeater.
2. If AP1 can connect to AP3 directly, then configure AP3 as root-bridge with wireless clients, configure both AP1 and AP2 as non-root bridge withe wireless clients.
3. If AP1 can't connect to AP3 directly, you need to add an additional AP4 to have back-to-back connection with AP2, configure AP1 and AP4 as non-root bridge with wireless clients, configure AP2 and AP3 as root-bridge with wireless clients; ap1 peered with AP2, AP4 peered with AP3, AP2 and AP4 are interconnected by ethernet port.

SAP 1602 Wireless bridge issue. Non root bridge loses it's configuration

Hi guys,
Today I tried to configure wireless link between two autonomous AP 1602 APs.
There is a problem with Non-root bridge. I configured it with this command:
AP2(config-if)#station-role non-root wireless-clients
Non-root bridge successfully joins the root bridge (root AP). Anyway, this configuration does not work, if I reload my non-root bridge. Even without reload, If I check my non-root bridge configuration it looks like this:
interface Dot11Radio1
no ip address
no ip route-cache
encryption vlan 1 mode ciphers aes-ccm
ssid WiFi-Bridge
antenna gain 0
stbc
beamform ofdm
Command "station-role non-root wireless-clients" is missing here. But I just configured it few seconds ago... Does anyone know, where could be a problem?

Okay... Everything works with OPEN ssid. Not with my WPA 2 configuration.
On both APs configuration looks like this:
dot11 ssid Private
   vlan 10
   authentication open
   authentication key-management wpa version 2
   guest-mode
   wpa-psk ascii 7 01100F175804575D72
interface Dot11Radio0
encryption vlan 10 mode ciphers aes-ccm
ssid Private
infrastructure-client ( on Root AP)
station-role root bridge wireless-clients ( on Root AP)
Few debugs:
*Mar 2 09:57:30.554: %DOT11-6-ASSOC: Interface Dot11Radio0, Station 9c02.986d.9675 Reassociated KEY_MGMT[WPAv2 PSK]
*Mar 2 09:57:30.938: dot11_auth_client_abort: Received abort request for client 9c02.986d.9675
*Mar 2 09:57:30.938: dot11_auth_client_abort: No client entry to abort: 9c02.986d.9675 for application 0x1
*Mar 2 09:57:30.938: %DOT11-6-DISASSOC: Interface Dot11Radio0, Deauthenticating Station 9c02.986d.9675 Reason: Sending station has left the BSS
*Mar 2 09:57:30.986: %DOT11-6-ASSOC: Interface Dot11Radio0, Station 9c02.986d.9675 Reassociated KEY_MGMT[WPAv2 PSK]
*Mar 2 09:57:31.350: dot11_auth_client_abort: Received abort request for client 9c02.986d.9675
*Mar 2 09:57:31.350: dot11_auth_client_abort: No client entry to abort: 9c02.986d.9675 for application 0x1
*Mar 2 09:57:31.350: %DOT11-6-DISASSOC: Interface Dot11Radio0, Deauthenticating Station 9c02.986d.9675 Reason: Sending station has left the BSS
*Mar 2 09:57:31.398: %DOT11-6-ASSOC: Interface Dot11Radio0, Station 9c02.986d.9675 Reassociated KEY_MGMT[WPAv2 PSK]
*Mar 2 09:57:31.766: dot11_auth_client_abort: Received abort request for client 9c02.986d.9675
Everything works with android device and WPA2 if I change configuration to this:
dot11 ssid Private
   vlan 10
   authentication open
   authentication key-management wpa version 2
   mbssid guest-mode
   wpa-psk ascii 7 01100F175804575D72
interface Dot11Radio0
encryption vlan 10 mode ciphers aes-ccm
ssid Private
station-role root
mbssid

1242 Root or Non-Root Bridge

Greetings,
I have a small network that uses 1242 APs for clients machines. Our wired WAN link can be unreliable, so I would like to configure one of the 1242s as a bridge and connect it to one of the many wireless networks we have in our neighborhood.
I understand the 1242 APs can also operate in a bridge mode that could allow us to connect our network to one of these other wireless LANs. A couple of questions:
-Does the remote WLAN have to be a compatible cisco device in order for the 1242 to be able to bridge successfully?
-Which 'Role in Radio Network' do I choose for our 1242?
-How do I see what the SSIDs of the remote WLANS are and enter the relevant passwords (WEP, WPA, 802.1x, or WPA2)
-If this is not possible, what is the right device to use to connect our LAN to a remote WLAN without being able to control the hardware at 'both' ends of the bridge.
TIA

Can you please provide me with a network topology of what it is you would like to achieve. If you want the radio interfaces to associate to one another, then it is recommended to have them on the same channel, but for roaming instances, it is recommended that you have then at least 5 channels apart on the g radio so as to avoid any interference.
The 802.11A radios on the APs would be configured as bridges (one as
a "root" and the other two as "non-root") and the 802.11G radios
would service clients. Only one of the APs would require wired
connectivity in this scenario, as long as all of the APs are
communicating to each other on the 802.11A side. An important
consideration is that the 802.11A radios that are configured as "non-
root bridges" need only to communicate with the 802.11A radio that is
configured as the "root bridge". It is not necessary for the "non-
root bridges" to see each other. However, it is imperative that the
802.11A radio that is configured as the "root bridge" be able to
communicate with BOTH of the 802.11A "non-root" bridges. Therefore,
the antennas you choose for the devices is important.

1230AG non-root bridge not associating

Similar Messages

Maybe you are looking for