tag:blogger.com,1999:blog-3818424847678287484.post7581404680660679288..comments2024-03-22T00:21:46.320-07:00Comments on CCIE Wireless: Mobility group / list / domain RF GroupJerome Henryhttp://www.blogger.com/profile/13895973186164519112noreply@blogger.comBlogger16125tag:blogger.com,1999:blog-3818424847678287484.post-75443244646735612072018-07-27T04:44:51.517-07:002018-07-27T04:44:51.517-07:00If you have 2 WLC's in the same mobility group...If you have 2 WLC's in the same mobility group, with same IP add for virtual interface (192.0.2.1), what about DNS name for virtual interfaces?<br />Anonymoushttps://www.blogger.com/profile/04272276121100808060noreply@blogger.comtag:blogger.com,1999:blog-3818424847678287484.post-75233832479945166952017-10-10T23:16:16.766-07:002017-10-10T23:16:16.766-07:00Keep up the best work guys, nice posts are here to...Keep up the best work guys, nice posts are here to get more benefits.<br /><a href="http://zeroup20bonus.com/" rel="nofollow">Zero Up 2.0 Review</a><br />dirty talking tipshttps://www.blogger.com/profile/15212314501431996543noreply@blogger.comtag:blogger.com,1999:blog-3818424847678287484.post-81838699947864460942017-09-07T05:51:10.007-07:002017-09-07T05:51:10.007-07:00best mobility/rf domain explanation I have seen be...best mobility/rf domain explanation I have seen bevor.. and so easy descripted!Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-3818424847678287484.post-31421535607349086682013-09-06T07:13:20.546-07:002013-09-06T07:13:20.546-07:00You are most welcome!
On later codes (now that we ...You are most welcome!<br />On later codes (now that we have 802.11r), 802.11r fast roaming uses a domain identifier (called Mobility Domain Information Element, MDIE) present in the AP beacons. The MDIE is based on the mobility group... so no seamless roaming with 802.11r between mobility groups either!Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-3818424847678287484.post-46251927208959688822013-09-06T06:40:31.456-07:002013-09-06T06:40:31.456-07:00Jerome, thanks so much for the explanation. I was...Jerome, thanks so much for the explanation. I was getting really confused as to what the difference really was between controllers in the same mobility group vs diff mobility group but in the mobility list. I kept reading that you could roam btwn either controller, so the obvious question was "then what's the difference?!?". Now I get that it's seamless if using PSK / Open, and quasi-seamless if using dot1x. So, roaming to a controller in your mobility list is better than roaming to a controller you don't know about at all (which would require both re-auth and re-IP).<br /><br />Thanks!!!Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-3818424847678287484.post-67407625017645937482013-07-25T11:35:00.065-07:002013-07-25T11:35:00.065-07:00huhu well, that's not a feature, its "so...huhu well, that's not a feature, its "something that may happen but this is not want we want to do" (is there an official term for that? :-)). This is why they use the "can" in there, in the sense "it may happen", not "this is something you can configure".<br />I can't go too deep into details, but this may happen when your anchor has a dynamic interface with no WLAN in the same L2 and subnet as the foreign controller management interface, but this is bad design.<br />Jerome Henryhttps://www.blogger.com/profile/13895973186164519112noreply@blogger.comtag:blogger.com,1999:blog-3818424847678287484.post-27093748634156062012013-07-25T04:50:07.536-07:002013-07-25T04:50:07.536-07:00Why is it then, that the below note is in the &quo...Why is it then, that the below note is in the "Prerequisites for Configuring Mobility Groups" section of the "Configuring Mobility Groups" chapter of the 7.3 Config Guide? It says it is possible, I just haven't figured out how to do it.<br /><br />Note <br /><br />Mobility control packets can use any interface address as the source, based on routing table. It is recommended that all controllers in the mobility group should have the management interface in the same subnet. A topology where one controller's management interface and other controller's dynamic interface are on same subnet not recommended for seamless mobility.Jlkuehn04https://www.blogger.com/profile/00838067208705460618noreply@blogger.comtag:blogger.com,1999:blog-3818424847678287484.post-44011280684626522522013-06-27T05:43:28.298-07:002013-06-27T05:43:28.298-07:00Hey Jlkuehn04,
Nope, you can't at this point. ...Hey Jlkuehn04,<br />Nope, you can't at this point. Mobility is always coming from the management interface (because it is management traffic for all WLANs and all clients tunneled to the anchor, and we want to make sure that there is only one tunnel per controller pair, to keep tight control on tunnel overhead... Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-3818424847678287484.post-34775120052193315992013-05-29T09:59:40.056-07:002013-05-29T09:59:40.056-07:00Jerome, is it possible to not use the management a...Jerome, is it possible to not use the management address for mobility control traffic? That is to say, using a dynamic interface to send/receive mobility messages and even use the dynamic interface to anchor WLAN traffic?Jlkuehn04https://www.blogger.com/profile/00838067208705460618noreply@blogger.comtag:blogger.com,1999:blog-3818424847678287484.post-7470045533664516482011-11-02T12:20:55.585-07:002011-11-02T12:20:55.585-07:00This makes a ton of sense! The Cisco Press books n...This makes a ton of sense! The Cisco Press books need to be revamped with this explanation!Robert M Parten IIhttp://www.humanlinux.comnoreply@blogger.comtag:blogger.com,1999:blog-3818424847678287484.post-23375532538582412672011-03-22T02:09:58.708-07:002011-03-22T02:09:58.708-07:00Not very accurate why? Seems pretty much the way 4...Not very accurate why? Seems pretty much the way 4.2 works...Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-3818424847678287484.post-5990333465485557692011-03-19T14:01:52.403-07:002011-03-19T14:01:52.403-07:00seems not very accurateseems not very accurateAnonymousnoreply@blogger.comtag:blogger.com,1999:blog-3818424847678287484.post-46363255833583389352010-12-20T02:40:50.997-08:002010-12-20T02:40:50.997-08:00Very helpful, not only informative but also easy t...Very helpful, not only informative but also easy to understand the idea.<br />The guide defines terms group/domain a little differently:<br />mobility domain A controller can be aware of another controller in a different mobility<br />group.<br />mobility group A setting that defines the controller as a member of a group.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-3818424847678287484.post-85702914549765825662010-03-16T09:54:29.765-07:002010-03-16T09:54:29.765-07:00This is by far the best write up of mobility I'...This is by far the best write up of mobility I've seen. Thanks alot for your help.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-3818424847678287484.post-53450132433895879432009-12-23T16:36:48.661-08:002009-12-23T16:36:48.661-08:00Thanks for the write up Jerome! Great stuff!Thanks for the write up Jerome! Great stuff!AvilleMCPhttps://www.blogger.com/profile/08634935757474607640noreply@blogger.comtag:blogger.com,1999:blog-3818424847678287484.post-41099892052467250532009-12-18T08:47:45.019-08:002009-12-18T08:47:45.019-08:00Thanks for this helpful explanation! The Cisco con...Thanks for this helpful explanation! The Cisco configuration guide and Cisco Press CCNA Wireless book are unclear on this subject, IMHO.Rorqualhttps://www.blogger.com/profile/15661290858265384505noreply@blogger.com