Wireless Access

last person joined: yesterday 

Access network design for branch, remote, outdoor, and campus locations with HPE Aruba Networking access points and mobility controllers.
Expand all | Collapse all

Netdestinations - "name" option limitation

This thread has been viewed 6 times
  • 1.  Netdestinations - "name" option limitation

    Posted Oct 08, 2014 08:51 PM

    Has anyone run into an issue where you can not add anymore domains with the name option to a netdestination?  For instance I have currently,

     

    netdestination GooglePlay
      network 74.125.0.0 255.255.0.0
      name play.google.com
      name googleplay.com
      name 1e100.net
      name android.clients.google.com

     

    If I try to add a name to another netdestination (or this one) I get the below.

    (FLRHO01-Aruba02) (config) #netdestination GooglePlay
    (FLRHO01-Aruba02) (config-dest) #  network 74.125.0.0 255.255.0.0
    (FLRHO01-Aruba02) (config-dest) #  name play.google.com
    Too many host names.

    (FLRHO01-Aruba02) (config-dest) #  name googleplay.com
    Too many host names.

    (FLRHO01-Aruba02) (config-dest) #  name 1e100.net
    Too many host names.

    (FLRHO01-Aruba02) (config-dest) #  name android.clients.google.com
    Too many host names.

     

     

    You can see it takes a host option just not the name option.

     

     

    Any ideas.  I have acase open but still no resolution.  Initial testing in the Aruba lab with my config support says they were able to add additional name entries.  This is on a 6000 controller with TWO MK3 modules with IP mobility -  AOS 6.1.3.7



  • 2.  RE: Netdestinations - "name" option limitation

    Posted Oct 08, 2014 08:54 PM
    Was the lab testing done with the same version of AOS?


  • 3.  RE: Netdestinations - "name" option limitation

    Posted Oct 08, 2014 09:07 PM
    This might be a code related issue I'm running 6.4.2.2 and I have one netdestination with 15 names
    And this also worked on 6.3.1.12
    I have a 3200xm


  • 4.  RE: Netdestinations - "name" option limitation

    Posted Oct 08, 2014 09:39 PM

    You may want to open a TAC case

    2014-10-08 21_38_00-Switch General Configuration.png



  • 5.  RE: Netdestinations - "name" option limitation

    Posted Oct 08, 2014 09:51 PM

    Yes Aruba Support case open they did a test on same model controller with my config and same AOS.  It worked for them.  I think I just have a messed up controller.  I had a few entries in there then I removed one and now cant add them back.  It takes just a "host entry"  just not a "name" entry.

     

    I also have an issue where I can not remove a netdestination that I know is not applied anywhere but it says it can not remove it because it is in use.  Need to talk to tac about this next.

     

    Thanks for all the quick replies.



  • 6.  RE: Netdestinations - "name" option limitation

    EMPLOYEE
    Posted Oct 09, 2014 07:47 AM

    ascott,

     

    Try to remove the network 74.125.0.0 255.255.0.0 and see if you still have the issue.

     



  • 7.  RE: Netdestinations - "name" option limitation

    Posted Oct 09, 2014 10:29 PM

    Yes still get the errors even with the host option removed.  I get the same on even a new netdestination.  Case has been escalated to engineering. 



  • 8.  RE: Netdestinations - "name" option limitation
    Best Answer

    Posted Oct 16, 2014 07:31 AM

    Aruba support informed me this is a known issue and engineering is working on a 6.1.x.x patch.  It was already fixed in 6.2.  Issue was not made public.

     

     

    "We have raised request to integrate the patch in 6.1.3.x forth coming code.

    I will update you once the code is released."



  • 9.  RE: Netdestinations - "name" option limitation

    Posted Mar 13, 2015 10:46 PM
    Just curious what you do with the googleAPI net destination. Thanks.


  • 10.  RE: Netdestinations - "name" option limitation

    EMPLOYEE
    Posted Mar 13, 2015 10:49 PM

    This thread is a bit dated. You don't need all of those anymore.

     

    In order to make things like Onboard and some guest services work, we need to allow certain traffic through in the registration role. 

     

    Using netdestinations with "name" allows for DNS lookups to happen on the controller meaning you don't have to maintain IP lists. Some services can have dozens of IP addresses tied to the same DNS name.



  • 11.  RE: Netdestinations - "name" option limitation

    Posted Mar 16, 2015 07:13 PM
    Thanks Tim my issue was more with not being able to add more host names to the netdestination. I had 6 or so and several host IPs. I was told.it was a known issue and an AOS upgrade was needed but I just rebooted the the 1 of 77 controllers having the issue and issue was resolved. I think later I also reduced some entries in the ACES table.