Wireless Access

I need help in changing the "Enable" password.

I am consoled in using the Root.

Thanks

I also need the CLI command to enable debug.

Normal Cisco background does not help in the Aruba with this.

To change the enable password on the controller:

(ArubaController) #configure t
Enter Configuration commands, one per line. End with CNTL/Z

(ArubaController) (config) #enable secret
Password: xxxxxxx

PS - what are you looking to 'debug' ?    The basic command structure for that is to turn up logging...

e.g.  

(ArubaController) (config) #logging level debugging ?

ap-debug Debug an AP
network Network logs
security Security logs
system System logs
user User logs
user-debug Debug a User
wireless Wireless logs

I have created a new SSID/Network, but can't get it tp function.

I have an end user running the test with me, so I can get the MAC easily.

I need to see where the WPA2-PSK authenication if failing and then to see why when I make it an open network, they can connect, pull the correct IP but can't get to the internet.

Ok, 

For the WPA/encryption piece, try  'show auth' and look for the MAC you have collected as a first step. Will tell you how far that transaction is making it.

For the second instance, that sounds like a firewall and/or routing issue...   Thats where you should try pings to the clients default gateway as a first step (e.g. can they connect as far as the controller, or gateway out of controller (next hop)) 

I will try the Auth tomorrow.

As far as internet, I can ping to the last hop on my internal firewall (ASA 5505).

The new Wireless is in a 10.0.6.0/24, and I can ping from the Aruba to the VLAN residing on the Internal Switches.

As a whole, I can't ping past the ASA, but the main wireless network is up and active with no issue.

OK, let us know how you make out on the auth front.

If you can get to the ASA on the other issue, I would focus efforts there in terms of debugging/increased logging & monitoring.

---

@kmcintosh78 wrote:

I will try the Auth tomorrow.

As far as internet, I can ping to the last hop on my internal firewall (ASA 5505).

The new Wireless is in a 10.0.6.0/24, and I can ping from the Aruba to the VLAN residing on the Internal Switches.

As a whole, I can't ping past the ASA, but the main wireless network is up and active with no issue.

 

 

 

---

 

Check your ASA for NAT rules/etc.  If you're usng ASA with a new code, there is a packet trace option that you can input the source as 10.0.6.20 or some other IP within 10.0.6.0/24 and a destination IP on the Internet and it would tell you if the packet is allowed or not.  Also, check your policy on the ASA to make sure 10.0.6.0/24 is allowed to the Internet.

 

- Mike

I am at my witts end and about ready to have a break down.

I need help with figuring out why this **bleep** this will not work.  I have created new networks via the wizard and can't get them to operate either.

I can provide the config, maybe team viewer remote. I just need to get this.

Are you working with a local Aruba partner or have you in the past ?

We can attempt to assist you here, but the best help will be hands on/local help... have you explored that avenue ?

I never have. The Aruba was set up by a CCIE that specialized in Wireless.

I have since replaced this person, as a part time/side job person.

All my experience is with Cisco based products.

Sounds like you are having more than one problem. I do agree that onsite help might be your best bet but we will do what we can remotely. Where are you located?

Lets outline them and see where you are at in this.

Did you change the enable password like you wanted to?

Are you users able to connect to the wireless network?  (show user-table)

What role do they end up in? (show user-table)

What is the role able to do? (show rights <role name>)

As suggested before does your ASA have the NAT policies set up for the "wireless network"?