Hi guys, new to the forum, though I have read quite a few posts on here.
I am needing some help with my Aruba 3200XM controller. I have been trying to upgrade our controller from 126.96.36.199 to 188.8.131.52. The problem I keep having is that after the upgrade, any device that connects will not get a DHCP address. I have turned of control plane security. I have the radios set up in tunnel mode. I have tried it with control plane security on, and in bridge mode, and control plane security off, and in split tunnel mode. I have made sure that users and radios are on the VLAN 1 (we use just the standard VLan). If I restart the controller back to 184.108.40.206, everything works fine again. Any thoughts on this? Thanks!
*You dont need to mess up your configuration too much - leave everyting like it's working in 3.4.5.X.
Uour DHCP is internal or extrnal?
It's sound like u got a PEF/PEFNG issue.
What is the user-role that your usersgetting in version 220.127.116.11 when connecting to SSID
And on what access roles it's based.
Can u please print screen of amount of licesnse installed on your controller in version 18.104.22.168 - and then on version 22.214.171.124
update me in needed details - and i will be able to help you.
DHCP is external to the Aruba system (disabled on controller). All users are just using the standard logon user. There are two pics attached. I will have to wait to do the upgrade again until tonight since we only have one controller and it is our production unit. Our system is very simple. Basically it just needs to be an extension of the wired network to wireless clients.
I should also add that after the 126.96.36.199 upgrade, the AP's show the "a" flag for "a = Reduce ARP packets in the air". Not sure if that matters or not.
Oh yeah, and with the licenses, it says in 188.8.131.52 the PEF is disabled, but in 184.108.40.206 after the upgrade it is enabled. I can't find where to disable it.
kdisc98 is right .
You don't have a PEF license according to the screen shot you provided.
if u didnt had pef | after moving from 220.127.116.11 to 18.104.22.168 You cant suddenly have PEFNG installed.
can u please screenshot me the licesnse page in the 22.214.171.124 page (like u did in the 126.96.36.199)
*Dont forget to disable the control-plane secutiry after upgrading (in order to allow your ap to boot up and provision)
*ALSO - after upgrading - check that u still have VLAN/IP connectiviy to the extranl DHCP (By doing ping)
*ALSO - after upgrading - check your AP/VAP settings - check that u are using the same working mode as in 188.8.131.52 and also - make sure that there is a vlan tagging
I have 24 licenses on the Aruba licensing site for PEFNG. And after I upgrade to 184.108.40.206 it shows that PEF is enabled. I will have to upgrade again tonight and take some screen shots for you.
I will be here also in the evening.
feel free to post a new screenshots.
and also check if u have red flag in the gui (in 220.127.116.11 after upgraindg)
What's the sequece you are taking to upgrade from 3.4 to 6x ?
Basically, I have the 18.104.22.168 system on partition 1, and 22.214.171.124 on partiton 2. I backup up the settings to the flashbackup.tar.gz file, and then reboot to partition 1. It updates the AP's and they all show "up" and the SSID information is correct, they just no longer get a DHCP address from my server. I also turn off control plane security after the upgrade.
So again like i wrote earlier - please print screen your 126.96.36.199 GUI
look for a red flag (at the top in the configuration)
also - printout user roles / fw roles that u assigning to this VAP
also - printout the VAP settings.
Thanks - when we will see all of those - i might find the problematic issue - that making your DHCP stop working.
I would try going to 5.x first and then to 6.x
The path he's attempting is permitted in the documentation, and will probably work fine - he's described a very simple setup.
It sounds like something in licensing or control-plane-securtiy is the issue.
A running-config from before and after may just show a setting change which is causing the problem.
I am really beginning to think it might be the PEFNG license. Neither of them are showing up in my list of licenses on 188.8.131.52. I still think it is weird that it shows PEF is enabled though when I upgrade to 184.108.40.206, but it shows disabled in 220.127.116.11, and the two licenses I have aren't listed.
I just tried to re-add the PEF licenses in 18.104.22.168, but it says that "Key contains limits that are not valid for ArubaOS". I am going to reboot to 22.214.171.124 here in just a minute.
I just updated back to 126.96.36.199, and here is what I have. This is the licenses page on 188.8.131.52. It shows the licenses at the bottom are all there that I should have. 16 AP licenses (8 are built in from what I am told), 24 PEFNG licenses (that seem to be missing after downgrading back to 184.108.40.206), and 24 RF protect licenses.
As for the red flag at the top, I have an error that says role 'authenticated' is unknown. That is listed twice, and it takes me to the system settings page if I click on the error.
I did try the 5.0 path to 6.1 in the past, and that did the same thing in 5.0.
I just rebooted back to 220.127.116.11. If you need anything later on, let me know. They have a meeting here after a while, so it had to be functional again. I am beginning to wonder if a factory reset might be the way to go. I did move some of this config from an older 2400 controller about a year ago, so it's possible maybe that is where the problem may lie?
Any thoughts guys?
Ok guys, here is the next step I took. I upgraded again tonight to 18.104.22.168. Thinking of messing with licenses, I actually went and turned off Control Plane Security, then removed the PEFNG licenses. After rebooting the controller, DHCP is now passing through and things seem to work fine. I have no idea why those licenses were causing issues, but at least things are working now. Now I just need to figure out what to do about the fixing that issue when I have time. Thanks for the thoughts and ideas guys.
cant say much about the speed, could be lots of things, do you get the 50mb when on version 3.x?
as for "I have an error that says role 'authenticated' is unknown." that usually points to the PEFNG config missing, haven't found a nice way to correct that except for just pasting stuff from another controller.
perhaps wiping config and starting over is an option?
Ok, next step. Last night I added the PEFNG licenses back. Things seem to be getting IP addresses now. But, now the issue is that when you try to go to a website, all you get is a message saying that web authentication is not enabled (or something close to that). Any ideas?
yes, you have the license but you lost some of your default pefng configuration, like the default roles and such. the role you get in probably has web auth configured, but missing parts of the config.
like i said, havent found a clear way to solve this, contacting TAC might be a good step by now. or if you have another controller you could pick up the config there. another way would be to save the config, reset to factory default and add the sections you configured in the past.
At Aruba, we believe that the most dynamic customer experiences happen at the Edge. Our mission is to deliver innovative solutions that harness data at the Edge to drive powerful business outcomes.
© Copyright 2020 Hewlett Packard Enterprise Development LPAll Rights Reserved.