Wireless Access

Reply
Occasional Contributor II
Posts: 12
Registered: ‎01-21-2012

Error 419

[ Edited ]

Hi,

 

i'm trying to connect a laptop with the VIA software to one of my controller.

 

I have never used this software before so i have made all the steps mentioned in the manual but when i try to connect i get an 419 error (ISAKMP could not be initialized). Anyone esle had this error before.

 

Thank you very much!

 

PS:

 

Now i have played a bit with the pre-shared keys and so on. Now  i have another error (see screenshot).

Guru Elite
Posts: 20,821
Registered: ‎03-29-2007

Re: Error 419

What version of ArubaOS?



Colin Joseph
Aruba Customer Engineering

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

Occasional Contributor II
Posts: 12
Registered: ‎01-21-2012

Re: Error 419

Hi,

 

6.1.2.4

Guru Elite
Posts: 20,821
Registered: ‎03-29-2007

Re: Error 419

Do you have the PEF-VIA license and are you allowing both UDP4500 and TCP443 inbounds to the controller?

 



Colin Joseph
Aruba Customer Engineering

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

Occasional Contributor II
Posts: 12
Registered: ‎01-21-2012

Re: Error 419

Yes i have installed the license and forwarded both ports to the controller

Guru Elite
Posts: 20,821
Registered: ‎03-29-2007

Re: Error 419

That is a fairly generic error message.  If you want quick help, you should open a TAC (support) case, because they can get access to your logs and other information that you probably cannot post here publicly.

 

You could, on the controller's commandline ensure that the traffic is being received by the controller by doing this:

 

show datapation session table <public ip address of via client>

 

 

 

 



Colin Joseph
Aruba Customer Engineering

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

Occasional Contributor II
Posts: 12
Registered: ‎01-21-2012

Re: Error 419

The error number is 8949...

 

I think it's not a bug but more a config-issue. I have checked the traffic with your command. The first part is a communication on port 443 and then the communications switches over to port 4500 (i think this is correct?) 

Guru Elite
Posts: 20,821
Registered: ‎03-29-2007

Re: Error 419

Okay.  Let's do some debugging on the commandline:

 

config t
logging level debugging security subcat ike
logging level debugging security process aaa
logging level debugging security process authmgr
logging level debugging security subcat l2tp
logging level debugging security subcat vpn

 

 

When you are trying to connect, type "show log security 50" to see what it says.



Colin Joseph
Aruba Customer Engineering

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

Occasional Contributor II
Posts: 12
Registered: ‎01-21-2012

Re: Error 419

Hi,

 

i have done the debugging like you said. I have attached the output. 

Regular Contributor I
Posts: 231
Registered: ‎05-04-2011

Re: Error 419

I just recently had the same problem. Make sure you have an ip address pool range defined in IPSec settings Configuration- Advanced services- VPN Services- IPSEC tab. Define an address pool Also make sure to create a route in your firewall for that range to point all that subnet traffic to the controller's IP address.
Search Airheads
Showing results for 
Search instead for 
Did you mean: