Wireless Access

Reply
Regular Contributor I
Posts: 183
Registered: ‎10-20-2010

Netdestinations - "name" option limitation

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

MVP
Posts: 288
Registered: ‎08-27-2012

Re: Netdestinations - "name" option limitation

Was the lab testing done with the same version of AOS?
ACDX #419 | ACMP |
MVP
Posts: 4,301
Registered: ‎07-20-2011

Re: Netdestinations - "name" option limitation

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
Thank you

Victor Fabian
Lead Mobility Engineer @ Integration Partners
AMFX | ACMX | ACDX | ACCX | CWAP | CWDP | CWNA
MVP
Posts: 4,301
Registered: ‎07-20-2011

Re: Netdestinations - "name" option limitation

You may want to open a TAC case

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

Thank you

Victor Fabian
Lead Mobility Engineer @ Integration Partners
AMFX | ACMX | ACDX | ACCX | CWAP | CWDP | CWNA
Regular Contributor I
Posts: 183
Registered: ‎10-20-2010

Re: Netdestinations - "name" option limitation

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.

Guru Elite
Posts: 21,280
Registered: ‎03-29-2007

Re: Netdestinations - "name" option limitation

ascott,

 

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

 



Colin Joseph
Aruba Customer Engineering

Looking for an Answer? Search the Community Knowledge Base Here: Community Knowledge Base

Regular Contributor I
Posts: 183
Registered: ‎10-20-2010

Re: Netdestinations - "name" option limitation

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. 

Regular Contributor I
Posts: 183
Registered: ‎10-20-2010

Re: Netdestinations - "name" option limitation

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."

Occasional Contributor I
Posts: 8
Registered: ‎02-02-2014

Re: Netdestinations - "name" option limitation

Just curious what you do with the googleAPI net destination. Thanks.
Guru Elite
Posts: 8,641
Registered: ‎09-08-2010

Re: Netdestinations - "name" option limitation

[ Edited ]

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.


Tim Cappalli | Aruba Security TME
@timcappalli | timcappalli.me | ACMX #367 / ACCX #480
Search Airheads
Showing results for 
Search instead for 
Did you mean: