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

Similar Messages

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

Root Bridge vs. Non-Root Bridge

Hi,
I want to understand the Root Bridge vs. the Non-Root Bidge when using Autonomous 1131 AP's on the same /24 network. Does that command matter in Autonomous? I have many devices working without issues on the same /24 network and all have the Root Bridge set,
Clearly confused...
Thanks,

The command is used on point to point links deployments
A non root bridge becomes a client and connect to another ap in order to do wireless bridging.
Sent from Cisco Technical Support iPhone App

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!

IdM 8.1: Problems to provision Solaris 10 with non root user.

Hello
When IdM 8.1 tries to create a user into Solaris 10 I got this Error:
com.waveset.util.WavesetException: An error occurred adding user 'testSolaris' to resource 'Test_Solaris'. com.waveset.util.WavesetException: Script failed waiting for "_,)#(:" in response "> > > > > > > > > > > pbmasterd3.5.4-01: 5408.07 select: Bad file number [email protected]: 3005 Request en...roblem in readMuxHeader fd 1. - fd closed unexpectedly [email protected]: 3005 Request ended unexpectedly " com.waveset.util.WavesetException: Script processor timed out with nothing to read and the following unprocessed text: "> > > > > > > > > > > pbmasterd3.5.4-01: 5408.07 select: Bad file number [email protected]: 3005 Request ended unexpectedly pbmasterd3.5.4-01@pbr9c: 5430.1 header problem in readMuxHeader fd 1. - fd closed unexpectedly [email protected]: 3005 Request ended unexpectedly pbmasterd3.5.4-01@pbr9c: 5430.1 header problem in readMuxHeader fd 1. - fd closed unexpectedly [email protected]: 3005 Request ended unexpectedly pbmasterd3.5.4-01@pbr9c: 5430.1 header problem in readMuxHeader fd 1. - fd closed unexpectedly [email protected]: 3005 Request ended unexpectedly ".+
*The non root user has the privileges that describes the IdM documentation. This error doesn't occure when the connection user is root.*
*What's wrong?*

The non - root doesn't work yet. I try to use a user with SUDO = TRUE but I got this error when I Test the connection:
Script failed waiting for "ASSWORD:" in response "_,)#+(:" ==> com.waveset.util.WavesetException: Script processor timed out with nothing to read and the following unprocessed text: "++_,)#+(:".+
I haver already configured the parameter tty_tickets to TRUE and the sudoers file as following:
+# sudoers file.+
+#+
+# This file MUST be edited with the 'visudo' command as root.+
+#+
+# See the sudoers man page for the details on how to write a sudoers file.+
+#+
++Defaults syslog=auth+
Defaults:idm_sudo tty_tickets
root ALL=(ALL) ALL
idm_sudo ALL = NOPASSWD: /usr/bin/auths,/usr/sbin/groupadd,/usr/sbin/groupdel,/usr/sbin/groupmod,/usr/bin/last,/usr/bin/listusers,/usr/bin/logins,/usr/bin/passwd,/usr/bin/profiles,
+/usr/bin/roles,/usr/sbin/useradd,/usr/sbin/userdel,/usr/sbin/usermod,/usr/bin/awk,/usr/bin/cat,/usr/bin/chmod,/usr/bin/chown,/usr/bin/cp,/usr/bin/cut,/usr/bin/diff,/usr/bin/echo,+
+/usr/bin/grep,/usr/bin/ls,/usr/bin/mv,/usr/bin/rm,/usr/bin/sed,/usr/bin/sleep,/usr/bin/sort,/usr/bin/tail,/usr/bin/touch,/usr/bin/which+
What's wrong?

Managing Internet clients with non unique names

I've got a wee complication which revolves around the fact the majority clients I am looking to deploy to are workgroup clients which have non-unique netbios/short names.
So when trying to manage said clients when looking at the Assets / Devices tab they for all intensive purposes appear identical - until I look at the properties of each item and look at the Resource Name - which will show the FQDN fo said machine.
If I was able to select Resource name as a viewable field in the view this would fix my problem. Unfortunately all machines currently have the same Workgroup set so just displaying the "Domain" field will not suffice.
Has anyone run into this issue and what can be done to work around it short of renaming all my intended clients? I've seen mention of creating your own Console custom nodes however this looks rather hairy.
Any thoughts are greatly appreciated. Cheers.

Also, I don't think that it will really help you, because the Devices
node is build on the SMS_CombinedDeviceResources class and that WMI class simply doesn't contain the
Resource Name property.
In this case it would mean creating a whole new node in the console. Probably using a Query, or Report is the most simple and best workaround.
My Blog: http://www.petervanderwoude.nl/
Follow me on twitter: pvanderwoude

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.

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.

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

Network Design - Root and Non root bridges

Hi,
We have a network set-up as the below image. Where the switches have STP enable to handle the muliple paths for the data to flow.
What I would like to know is should the 2 bridges plugged into the same switch e.g Switch A (Bridge A and Bridge B) both be root bridges and (Bridge C and Bridge D) both be non root.
Or should for example, Bridge A be a root and Bridge C a non root and Bridge B a non root and Bridge D the root?
Similarly with the rest of the other bridges E, F, G and H
Thanks

Disclaimer
The Author of this posting offers the information contained within this posting without consideration and with the reader's understanding that there's no implied or expressed suitability or fitness for any purpose. Information provided is for informational purposes only and should not be construed as rendering professional advice of any kind. Usage of this posting's information is solely at reader's own risk.
Liability Disclaimer
In no event shall Author be liable for any damages whatsoever (including, without limitation, damages for loss of use, data or profit) arising out of the use or inability to use the posting's information even if Author has been advised of the possibility of such damage.
Posting
Ah, I think I understand. So the wireless bridges are "transparent" to the rest of the network. They just convert wired to wireless and back again.
If I have that right, we can ignore them and just consider your switches.
In that case, it appears you have two L2 loops, those formed by the dual paths between switches A and B and between switches C and D. From a topology standpoint, it doesn't seem to matter what switch you select as root and secondary root. However, as switches B and C are the interior switches, I would suggest those as your root and secondary root switches.

340 bridge traffic between two non root bridges

I have a deployent with a 340 series bridge acting as root bridge and two 340 bridges acting as non-root remotes. The hosts hanging off the non-root bridges can communicate with the hosts hanging off the root bridge but i cannot get communication to work between hosts on the two non-root bridges. Is there some sort of split horizon type setting I need to configure on the root-bridge to allow traffic back out the radio interface.

There isn't anything in the bridges that would block traffic between the two sites. Is this one large subnet, or are there two subnets? If there are two, how are you routing between the two?
Can one non-root bridge ping the other non-root?

Weblogic server with OIM non-root

Friends,
I am installing OIAM on top of Weblogic Server on CentOSLinux OS .
The problem is i want to install weblogic server and OIAM with non-root so that it does not have security issues.
When i try to install weblogic i am unable to install it with normal user rights in /opt dir it requires root access. As per the document oiam install on top of weblogic should not be a problem but the major issue is running weblogic with non-root.
pls let me know abt install and running weblogic as a non-root user, or a pointer to the documentation.
thank you

I have installed weblogic server as an nt service. In install Nt service
cmd, if I make any change in the script, I have to uninstall and install it
again. I do not know where to specify the weblogic.management.username =(Non
system user)
I have created a user name in NT server and added them to Administrator
group. I have also modified in file realm propertes i.e to boot and shutdown
the non system user.
I have to start weblogic server as a non system user.
Thanks
Madhu
I think I replied to some of the questions when I found out the answers.
Only thing I did was hit reply, instead of reply group. Might it went to
persons e-mail. That might be the reason, the answers I posted is not found
in the newsgroup
Thanks
freelance_code_inspector <[email protected]> wrote in message
news:[email protected]..
"m holur" <[email protected]> wrote in message
news:<3bfbafce$[email protected]>...
I want to start wls6.1 as an nt service with different user name otherthan
system.Madhu,
Specify weblogic.management.username={Non system user} in your -D
option. BTW, just curious, have observed that u have been posting a
lot of weblogic questions lately, did u find out the answers? If so, u
should share it back to this community.
Regards
drit
Freelance Java Developer/Code Inspector
http://www.geocities.com/doc_i_t/CodeInspectionService.html

NON-ROOT TO NON-ROOT ASSOCIATION??

Hi,
I have one AIR-AP1242AG-A-K9, and two AIR-AP1242AG-N-K9. I have already configure them to work as bridge.
Root Bridge with wireless-clients ----------->     1   AIR-AP1242AG-N-K9
Non-Root Bridge1 with wireless-clients --->      1   AIR-AP1242AG-N-K9
Non-Root Bridge2 with wireless-clients ---->      1   AIR-AP1242AG-A-K9
I notice after reseting the root bridge or one of the non-root bridges that when I type the command "sh DOt11 associations" the results shows that there is an associatiation between the 2 Non-Root bridge. When this happend the connection of the clients associated to this APs is very unstable.
as far as I know the association is just between Root and Non-Root bridges.
I don´t know why this happend.
In order to avoid this I disable in one of the non-root bridge (AIR-AP1242AG-A-K9) the option "Force Infrastructure Device to associate only...."
Cisco's Docs show an example of config when there is one root bridge and one non-root bridge but in my scenario I have 2 non-root bridge and one root bridge.
I would like to know if the config for my scenario must be different from the simple scenario (1 root and 1 non-root).
I hope any of you can help me.
Regards

Hi Scott,
Thanks for your recommendations.
The mac-address authentication option you recommend is the option shown as "Root Parent MAC 1" ,"Root Parent MAC 2 ....." on Setting---> Network interface???
For root bridge , I should write down the MAC addres of the non-root bridge1 on Root Parent MAC 1 field and on the field of Root Parent MAC 2, the MAC of the non-root bridge2 ?? , am I right?
and for the non-root bridges I should just set on Root Parent MAC 1 just the MAC address of the root bridge???
Regards,

Cisco 1300 configs; ROOT - NON ROOT

I'm using a AIR-BR1310-E-K9-R as ROOT and 5 NON ROOTS type (AIR-BR1310-E-K9).
Im looking for a default config to setup a wireless PTMP link between the ROOT and the NON ROOTS. To make this wireless connection i'm using an AIR-ANT2506

In a point-to-multipoint configuration, two or more non-root bridges associate to a root bridge. Up to 17 non-root bridges can associate to a root bridge, but the non-root bridges must share the available bandwidth See "Configuring the Access Point/Bridge for the First Time," for instructions on initial bridge setup.
http://www.cisco.com/en/US/docs/wireless/access_point/1300/12.2_15_JA/configuration/guide/o13frst.html#wpxref80859

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

Similar Messages

Maybe you are looking for