Great Brendon and no worries, This matches my tests then. So what you are saying that timeout isn´t there at all by default. So you have to configure it if you want it to timeout and search for others. This would best match your question in my oppinion, cause it will work for all MACs and not only a parent list. btw. That parent list can only contain 4 mac addresess isn´t that right ?
kv.Kristján -----Original Message----- From: Stalder Dominic [mailto:[email protected]] Sent: 18. febrúar 2011 10:32 To: Kristján Ólafur Eðvarðsson; Brendon Hwang; [email protected] Subject: Re: [CCIE Wireless] 2. Question / Workgroup bridge parent command (Stalder Dominic) Hi Kristjan and Brendon Sorry for not responding to your mail, but I first wanted to test it. I think the keyword is really the timeout. As long as I configured only the following, it did never associate to my parent 003a.9929.4ad0: int dot 1 parent 1 aaaa.aaaa.aaaa ! Feb 18 10:23:23 UTC: %DOT11-4-CANT_ASSOC: Interface Dot11Radio1, cannot associate: Not specified parent (from 003a.9929.4ad0) But as soon as I enter the timeout value, it tries first aaaa.aaaa.aaaa BUT then it associates to my parent, even if it is not in the parent list: int dot 1 parent 1 aaaa.aaaa.aaaa parent timeout 5 ! Feb 18 10:25:05 UTC: %DOT11-4-UPLINK_ESTABLISHED: Interface Dot11Radio1, Associated To AP 1240WGB-1 003a.9929.4ad0 [None] Great work guys, thanks! As an addition to Kristjans statement: > So this timer must be longer by default. I think it will never work without the timeout parameter. Regards Dominic > Von: Kristján Ólafur Eðvarðsson <[email protected]> > Datum: Sun, 13 Feb 2011 13:54:14 +0000 > An: Brendon Hwang <[email protected]>, Dominic Stalder > <[email protected]>, "[email protected]" > <[email protected]> > Betreff: RE: [CCIE Wireless] 2. Question / Workgroup bridge parent command > (Stalder Dominic) > > Very good! > > I tried this command when the bridge didn´t accociate cause I had a bogus > parent 1 mac. > And as soon as I entered the parent timeout 10 command (it is the time the > bridge gives up on the parent) > I waited 10 seconds and after that it accociated to my root, even though the > root wasn´t in the parent list. > So this timer must be longer by default. We will have to look that up. Perhaps > this is more precise for Dominic's > question before ? Then we have all potential roots to accociate to without > knowing their MAC's. > But I would ask my proctor :D > ! > interface Dot11Radio0 > no ip address > no ip route-cache > ! > encryption vlan 150 mode ciphers tkip > ! > encryption vlan 1 mode ciphers tkip > ! > ssid BOB > ! > ssid client > ! > parent 1 0000.1111.2222 > parent timeout 10 > speed basic-1.0 basic-2.0 basic-5.5 6.0 9.0 basic-11.0 12.0 18.0 24.0 36.0 > 48.0 54.0 > station-role repeater > end > > ! > RepeaterAP#sh dot11 ass > > 802.11 Client Stations on Dot11Radio0: > > SSID [BOB] : > > MAC Address IP address Device Name Parent > State > 003a.9969.2c20 192.168.20.14 ap1240-Parent RootAP - > Assoc > > regards. Kristjan > > -----Original Message----- > From: Brendon Hwang [mailto:[email protected]] > Sent: 13. febrúar 2011 12:45 > To: Stalder Dominic; Kristján Ólafur Eðvarðsson; > [email protected] > Subject: Re: [CCIE Wireless] 2. Question / Workgroup bridge parent command > (Stalder Dominic) > > Hello, > > There is a command called "parent timeout". > Have you tried this? > > Cheers, > Brendon > > On 13/02/11 12:17 AM, "Stalder Dominic" <[email protected]> wrote: > >> Hi Kristjan >> >> The same I thought though, but what would you configure, if the task would >> be something like: >> >> - Configure the WGB to prefer the parent 1240XXX, but if 1240XXX is not >> available, the WGB should be able to scan for other root aps >> >> Maybe the command "mobile station" would be helpful, but this only forces >> the WGB to scan for a new parent, before the old parent is lost. But I >> think, if you configure it in parallel with "parent", then only the parent >> list is scanned? >> >> I will try this on Monday, but maybe someone knows it right here ;-) >> >> Regards and have a nice weekend >> Dominic >> >> >>> Von: Kristján Ólafur E›var›sson <[email protected]> >>> Datum: Fri, 11 Feb 2011 21:17:25 +0000 >>> An: "[email protected]" >>> <[email protected]> >>> Cc: Dominic Stalder <[email protected]> >>> Betreff: 2. Question / Workgroup bridge parent command (Stalder Dominic) >>> >>> 2. Question / Workgroup bridge parent command (Stalder Dominic) >>> >>> >>> Helo Dominic, >>> >>> I was happy to refresh my memory on this. I had a Root vs. Repeater >>> setup. It >>> must be the same. >>> They key here is to test it if and see if the log gives you feedback >>> on what you need to know :D And this was the case now. >>> >>> The answer according to my test below is: No it won´t try anything else >>> if the >>> only parent it has is not reachable. >>> >>> cannot associate: Not specified parent (from 003a.9969.2c20) >>> >>> Im my example I had no parents configured. Then configured a bogus >>> parent MAC >>> (see output below) and it couldn´t associate to anything. >>> When I entered the real root AP mac as parent 2, it immitiately >>> associated to >>> the "old" root. >>> >>> RepeaterAP#sh dot11 ass >>> >>> 802.11 Client Stations on Dot11Radio0: >>> >>> SSID [BOB] : >>> >>> MAC Address IP address Device Name Parent >>> State >>> 003a.9969.2c20 192.168.1.14 ap1240-Parent RootAP - >>> Assoc >>> >>> RepeaterAP#conf t >>> Enter configuration commands, one per line. End with CNTL/Z. >>> RepeaterAP(config)#int dot0 >>> RepeaterAP(config-if)#parent 1 0000.1111.2222 >>> RepeaterAP(config-if)# >>> *Mar 10 18:10:50.447: %LINK-5-CHANGED: Interface Dot11Radio0, changed >>> state to >>> reset >>> RepeaterAP(config-if)# >>> *Mar 10 18:10:50.470: %LINK-3-UPDOWN: Interface Dot11Radio0, changed >>> state to >>> down >>> RepeaterAP(config-if)# >>> *Mar 10 18:10:51.447: %LINEPROTO-5-UPDOWN: Line protocol on Interface >>> Dot11Radio0, changed state to down >>> RepeaterAP(config-if)# >>> *Mar 10 18:10:52.445: %LINK-3-UPDOWN: Interface FastEthernet0, changed >>> state >>> to up >>> *Mar 10 18:10:52.447: %LINK-3-UPDOWN: Interface BVI1, changed state to >>> down >>> *Mar 10 18:10:53.445: %LINEPROTO-5-UPDOWN: Line protocol on Interface >>> FastEthernet0, changed state to up >>> RepeaterAP(config-if)# >>> *Mar 10 18:10:53.447: %LINEPROTO-5-UPDOWN: Line protocol on Interface >>> BVI1, >>> changed state to down >>> RepeaterAP(config-if)# >>> *Mar 10 18:10:58.976: %LINK-3-UPDOWN: Interface BVI1, changed state to >>> up >>> *Mar 10 18:10:59.976: %LINEPROTO-5-UPDOWN: Line protocol on Interface >>> BVI1, >>> changed state to up >>> RepeaterAP(config-if)# >>> *Mar 10 18:11:00.976: %DOT11-4-CANT_ASSOC: Interface Dot11Radio0, cannot >>> associate: Not specified parent (from 003a.9969.2c20) >>> RepeaterAP(config-if)# >>> RepeaterAP(config-if)#parent 2 003a.9969.2c20 >>> RepeaterAP(config-if)# >>> *Mar 10 18:11:37.120: %LINK-5-CHANGED: Interface Dot11Radio0, changed >>> state to >>> reset >>> *Mar 10 18:11:37.305: %DOT11-4-UPLINK_ESTABLISHED: Interface >>> Dot11Radio0, >>> Associated To AP RootAP 003a.9969.2c20 [None WPA PSK] >>> RepeaterAP(config-if)# >>> *Mar 10 18:11:37.305: %LINK-3-UPDOWN: Interface Dot11Radio0, changed >>> state to >>> up >>> *Mar 10 18:11:38.305: %LINEPROTO-5-UPDOWN: Line protocol on Interface >>> Dot11Radio0, changed state to up >>> RepeaterAP(config-if)# >>> *Mar 10 18:11:39.304: %LINK-3-UPDOWN: Interface FastEthernet0, changed >>> state >>> to down >>> *Mar 10 18:11:40.304: %LINEPROTO-5-UPDOWN: Line protocol on Interface >>> FastEthernet0, changed state to down >>> RepeaterAP(config-if)#do show run int dot0 >>> Building configuration... >>> >>> Current configuration : 338 bytes >>> ! >>> interface Dot11Radio0 >>> no ip address >>> no ip route-cache >>> ! >>> encryption vlan 150 mode ciphers tkip >>> ! >>> encryption vlan 1 mode ciphers tkip >>> ! >>> ssid BOB >>> ! >>> ssid client >>> ! >>> parent 1 0000.1111.2222 >>> parent 2 003a.9969.2c20 >>> speed basic-1.0 basic-2.0 basic-5.5 6.0 9.0 basic-11.0 12.0 18.0 24.0 >>> 36.0 >>> 48.0 54.0 >>> station-role repeater >>> end >>> >>> ------------------------------ >>> >>> Message: 2 >>> Date: Fri, 11 Feb 2011 10:27:10 +0000 >>> From: Stalder Dominic <[email protected]> >>> To: "[email protected]" >>> <[email protected]> >>> Subject: [CCIE Wireless] Question / Workgroup bridge parent command >>> Message-ID: <c97acd8b.2f19%[email protected]> >>> Content-Type: text/plain; charset="windows-1252" >>> >>> Hi there >>> >>> If I have to configure a workgroup bridge with a preferred parent and I >>> configure the following: >>> >>> int dot 0 >>> parent xxxx.yyyy.zzzz >>> >>> Will the WGB even try to associate to any other parent (not specified >>> in the >>> parent list), when the first parent is not available? Because in the >>> configuration guide is stated and this is not clear for me, based on >>> the text >>> below: >>> >>> (Optional) Enter the MAC address for the access point to which the >>> workgroup >>> bridge should associate. >>> ? You can enter MAC addresses for up to four parent access points. >>> The >>> workgroup bridge attempts to associate to MAC address 1 first; if that >>> access >>> point does not respond, the workgroup bridge tries the next access >>> point in >>> its parent list. >>> >>> Regards >>> Dominic >>> -------------- next part -------------- >>> An HTML attachment was scrubbed... >>> URL: >>> >>> </archives/ccie_wireless/attachments/20110211/91adaf73/attachment-0001.ht >>> ml> >>> >>> ------------------------------ >>> >>> _______________________________________________ >>> CCIE_Wireless mailing list >>> [email protected] >>> http://onlinestudylist.com/cgi-bin/mailman/listinfo/ccie_wireless >>> >>> >>> End of CCIE_Wireless Digest, Vol 23, Issue 12 >>> ********************************************* >> >> _______________________________________________ >> For more information regarding industry leading CCIE Lab training, please >> visit www.ipexpert.com > > _______________________________________________ For more information regarding industry leading CCIE Lab training, please visit www.ipexpert.com
