Wireless Access

i have two aruba controller cluster in two differnet building. both two cluster are in Master/Local(active/passive) model.

now these two builging are connect to a large building, so we have a project to set a roaming between this two cluster controller.(from buliding A to building B and vise)

as there are two different clients subnet on each side, so i need to enable the L3-mobility between these two cluster ?
or do i add the same building A vlans on controllers to building B controllers to do a L2 mobility??

what is my decision should i concern or care about on ?
which mobility model should i perfrom??

all help are very appreciate..

arubafresher

Since you have two different Master-local clusters, I would enable L3 mobility for these clients.

Can you give a deeper explanation, Seth?

I would configure L3 roaming (IP Mobility) between these buildings vs. adding VLANs to both sides.  This is covered in our user guide but a basic config (in 6.3) would look like this...

ip mobile domain CampusXYZ

   description <description>

   hat 172.16.100.100 description "Bldg1 ihome agent"

   hat 192.168.100.100 description "Bldg 2 home agent"

Right. but he does not define VRRP. souldnt he have that first? :)

or am i way off?

edit: nwm. he does. sorry :fool's errand)

active\passive

YOu don't need VRRP between these buildings

nahh . not between the buildings. just in the cluster.

? or

dear Seth Fiermonti,,

many thanks for soon reply...

controller A is in building A

controller B is in building B

one more question for L3 mobility. if i associate with AP_a in building A,i will go though controller A to internet....now i am going to building B....i will asoociate another AP_b on building B and the roaming is occured... the whole path is " Controller B -> Controller A -> internet"...Controller B and Controller A will form a mobility tunnel and i don't lose my original IP get from building A. do my concept right?

if the above concept right...but my goal is when i go to building B....i don't want the traffic go back to building A then go to internet. how can i do? so , i dont need mobility , right ? if i don't want lose my original IP...should i need create vlans same as the Building A to do a L2 mobility..???

many thanks,

any limitation of the l3 mobility between two controller? my controller model is 7200 series...

how many concurrent roaming user/serssion support?? assume that my building at most 5000 people will use wifi and walk across two building...

There wont be 5000 users roaming :)  I think you will be good to go.

hi Seth R. Fiermonti

ip mobile domain CampusXYZ

   description <description>

   hat 172.16.100.100 description "Bldg1 ihome agent"

   hat 192.168.100.100 description "Bldg 2 home agent"

the <hat agent ip> should be in the loacl controllers which under the same master controller???

thx a lot..