Higher Education

last person joined: 11 days ago 

Got questions on how to enable mobility in education? Submit them here!
Expand all | Collapse all

roaming b/w building blocks

This thread has been viewed 0 times
  • 1.  roaming b/w building blocks

    Posted Sep 20, 2013 01:24 AM

    Hi,

     

    Building Blocks are saparated by two virtual AP's with same SSID name (different vlan), but occasuionally  vlan sticks to same ip even if moved across building, but connection shows to the respective building AP the user is in, but ip doesnt match to the ssid vlan, then disconnect reconnect is required, any help?

     

    Thanks

     



  • 2.  RE: roaming b/w building blocks

    EMPLOYEE
    Posted Sep 20, 2013 01:55 AM

    You have 2 choices:

     

    - Make both buildings the same virtual AP

    - Enable VLAN mobility in the Virtual AP profile; that will allow users coming from a different virtual AP to retain their VLAN when roaming to an access point in a different virtual AP on the same controller.



  • 3.  RE: roaming b/w building blocks

    Posted Sep 20, 2013 02:34 AM

    we dont want to retain the ip, we want to change the ip according to the buliding, our experience is that in occassionally ip retains.



  • 4.  RE: roaming b/w building blocks

    EMPLOYEE
    Posted Sep 20, 2013 02:37 AM

    Not possible unless the client sees that the link goes down.  You cannot roam between buildings on the same SSID and make the client change ip addresses, period.

     

    Network administrators should design their networks so that users who roam maintain the same ip address for seamless performance.  There is no advantage to changing ip addresses within the same network.

     



  • 5.  RE: roaming b/w building blocks

    Posted Sep 20, 2013 02:45 AM

    but SSID's are different in different VAP, however with same SSID name.



  • 6.  RE: roaming b/w building blocks

    EMPLOYEE
    Posted Sep 20, 2013 02:46 AM

    If you want users to connect to Apple TVs in the same building, make the VAP in the second building have the same VLAN, but a different role that blocks bonjour traffic from subnets in other buildings.  With that being said, the client will still maintain a "memory" of Apple TVs that it saw before, so it will not be perfect.  



  • 7.  RE: roaming b/w building blocks

    Posted Sep 20, 2013 02:50 AM

    we use /24 subnet, otherwise we end up a big broadcast subnet.



  • 8.  RE: roaming b/w building blocks

    EMPLOYEE
    Posted Sep 20, 2013 02:53 AM

    I am not sure how you would do this without airgroup.



  • 9.  RE: roaming b/w building blocks

    Posted Sep 20, 2013 03:13 AM

    Our issue is with Airgroup, can I ask your advise related to this,

     

    Should we enable igmp in vlan ip interface in ARUBA controller for AppleTv to work efficiently ?, also snooping to be checked or not.

     

    Thanks

     

     

     



  • 10.  RE: roaming b/w building blocks

    EMPLOYEE
    Posted Sep 20, 2013 07:29 AM

    No, you should not have to do that.

     

    What is not working with Airgroup?  

     

    FYI, soon there should be a 6.3.1.0 release that will probably have improvements.  You should probably wait on that..

     



  • 11.  RE: roaming b/w building blocks

    Posted Sep 20, 2013 08:15 AM

    Fifty APpleTv's, sometime no mirroring happening to the big screen eventhough mirrored from ipad.



  • 12.  RE: roaming b/w building blocks

    EMPLOYEE
    Posted Sep 20, 2013 08:29 AM

    You need to work closely with support to find out what your issue is, or determine if it is a bug.  There are many factors that will determine if you can support that number of devices and it would be painful for us to go through all of them here.  Please open a support case.



  • 13.  RE: roaming b/w building blocks

    Posted Sep 20, 2013 02:46 AM

    we do this to separate AppleTV's, we had hard time with AirGroup.



  • 14.  RE: roaming b/w building blocks

    Posted Sep 20, 2013 09:29 AM

    @cjoseph wrote:

    Not possible unless the client sees that the link goes down.  You cannot roam between buildings on the same SSID and make the client change ip addresses, period.

      


    This is not always true. Only with Windows laptops have we noticed this behavior. Other clients (e.g., iOS, Android, MacOS) will roam and perform 802.1X authentication, followed by sending a DHCPREQUEST for the IP the last had. DHCP servers should then respond with a DHCPNAK (assuming they're now on a different network), forcing the client to go ahead with a DHCPDISCOVER packet and obtain an address in the new network. We see this correct behavior all the time.

     


    @cjoseph wrote:

    Network administrators should design their networks so that users who roam maintain the same ip address for seamless performance.  There is no advantage to changing ip addresses within the same network.

     


    I agree - no advantage. However, with large geographic networks like ours, changing IP is inevitable. ArubaOS' vlan pooling hash algorithm deteriorates the more vlans you have in the pool, so I cannot maintain a single vlan pool across the campus. Thus, I must establish hard roaming boundaries wherein users will change their IP.



  • 15.  RE: roaming b/w building blocks

    MVP
    Posted Sep 20, 2013 09:32 AM

    Ryan,

     

    At what level are you noticing the vlan pool deterioration? We have 30 /23 vlans in a pool and have not noticed any issues (yet).



  • 16.  RE: roaming b/w building blocks

    Posted Sep 20, 2013 09:53 AM
    By deterioration, I'm referring to the exponential increase of wasted address space. If you're not NATing like we currently are, this is very bad. With ~23 vlans, we observe nearly 20% variance between the most and least utilized vlans. With /23s, this equated to 1,000 to 1,500 wasted addresses.


  • 17.  RE: roaming b/w building blocks

    MVP
    Posted Sep 20, 2013 10:00 AM

    We are NAting, so that is not as big a concern for us. 



  • 18.  RE: roaming b/w building blocks

    EMPLOYEE
    Posted Sep 20, 2013 10:27 AM

    @Ryan wrote:

    @cjoseph wrote:

    Not possible unless the client sees that the link goes down.  You cannot roam between buildings on the same SSID and make the client change ip addresses, period.

      


    This is not always true. Only with Windows laptops have we noticed this behavior. Other clients (e.g., iOS, Android, MacOS) will roam and perform 802.1X authentication, followed by sending a DHCPREQUEST for the IP the last had. DHCP servers should then respond with a DHCPNAK (assuming they're now on a different network), forcing the client to go ahead with a DHCPDISCOVER packet and obtain an address in the new network. We see this correct behavior all the time.

     


    @cjoseph wrote:

    Network administrators should design their networks so that users who roam maintain the same ip address for seamless performance.  There is no advantage to changing ip addresses within the same network.

     


    I agree - no advantage. However, with large geographic networks like ours, changing IP is inevitable. ArubaOS' vlan pooling hash algorithm deteriorates the more vlans you have in the pool, so I cannot maintain a single vlan pool across the campus. Thus, I must establish hard roaming boundaries wherein users will change their IP.


    Ryan,

     

    If something does not work with all clients, it is not a solution.  I do not want noninterference to think that something is worth pursuing, when it does not work, in general for all clients.

     

    Noninterference does not have a large geographic network, so devices maintaining the same ip address for good client experience is definitely applicable.  The answer was specific to his question and to his environment.

     



  • 19.  RE: roaming b/w building blocks

    Posted Sep 20, 2013 11:01 AM
    Understood Colin. Since the community also serves as an archive for others to seek information (ie, not just for the benefit of the original poster), I wanted to point out those details. I trust that I am permitted to add my personal experiences to this forum without having to frequently expect a rebuttal to said experience.


  • 20.  RE: roaming b/w building blocks

    EMPLOYEE
    Posted Sep 20, 2013 11:07 AM

    @Ryan wrote:
    Understood Colin. Since the community also serves as an archive for others to seek information (ie, not just for the benefit of the original poster), I wanted to point out those details. I trust that I am permitted to add my personal experiences to this forum without having to frequently expect a rebuttal to said experience.

    Ryan,

     

    This community benefits from and relies on full explanations and context.  Thank you for providing both to this thread.