Wireless Access

Hello,

 

I currently have an old Aruba 2400 mobility controller running version 5.0.3.1.  I would like to add a 2nd 2400 controller simply so that I can save money and add more access points.  I would like to use the configuration in my original 2400 and somehow have it be the master.  Can someone point me to documentation on how to do this? 

 

Thanks!

 

If the current controller is a local do the following to make it a master  :

 

(controller) (config) #no masterip

 

And then it is going to ask you to reboot the controller (save the config)

 

After that add the new 2400 as a local on the current 2400 (master) do the following :

 

(controller) (config) #localip 10.10.10.2 ipsec "KEY"

 

And finally on the new 2400 (local) add the current 2400 (master)

 

(controller) (config) #masterip 10.10.10.1 ipsec "KEY"

 

Both have to be the same key

 

Awesome!  I'll give that a shot

 

Thanks!

So far so good... I have the 2nd controller connected and set to read from the master. 

 

I'm still however showing unlicensed access points above 48.  How do I fix this?

 

Thanks!

 

run  a show licenses ?

 

and check if you have enough AP licenses installed on your controller.

 

you can also do a show ap licenses

 

Thanks

 

Vic

I'm showing 47 used 1 unused licenses on the master and 48 unused on the slave.

 

Thanks

 

 

 

What do you see if you run show ap license-usage ?

When you do show licenses , check if there's a flag indicating that you have to restart the controller .

 

flags: A - auto-generated; E - enabled; R - reboot required to activate

 

 

On the 1st controller I'm showing...

 

(Aruba2400) #show ap license-usage

Total AP Licenses                       : 48
AP Licenses Used                        : 48
MUX Licenses Used                       : 0
Unused AP Licenses                      : 0
Total RAP Licenses                      : 48
RAP Licenses Used                       : 0
Total Ortronics AP Licenses             : 0
Ortronics AP Licenses Used              : 0
Total Indoor Mesh AP's Supported        : 48
Indoor Mesh AP's Active                 : 0
Total Outdoor Mesh AP's supported       : 48
Outdoor Mesh AP's Active                : 0
Total 802.11n-120abg Licenses   : 0
802.11n-120abg Licenses Used    : 0
Total 802.11n-121abg Licenses   : 0
802.11n-121abg Licenses Used    : 0
Total 802.11n-124abg Licenses   : 0
802.11n-124abg Licenses Used    : 0
Total 802.11n-125abg Licenses   : 0
802.11n-125abg Licenses Used    : 0

 

On the 2nd controller...

 

(Aruba2400-2) #show ap license-usage

Total AP Licenses                       : 48
AP Licenses Used                        : 0
MUX Licenses Used                       : 0
Unused AP Licenses                      : 48
Total RAP Licenses                      : 48
RAP Licenses Used                       : 0
Total Ortronics AP Licenses             : 0
Ortronics AP Licenses Used              : 0
Total Indoor Mesh AP's Supported        : 48
Indoor Mesh AP's Active                 : 0
Total Outdoor Mesh AP's supported       : 48
Outdoor Mesh AP's Active                : 0
Total 802.11n-120abg Licenses   : 0
802.11n-120abg Licenses Used    : 0
Total 802.11n-121abg Licenses   : 0
802.11n-121abg Licenses Used    : 0
Total 802.11n-124abg Licenses   : 0
802.11n-124abg Licenses Used    : 0
Total 802.11n-125abg Licenses   : 0
802.11n-125abg Licenses Used    : 0

On the 2nd controller I'm showing this for some reason...

 

(Aruba2400-2) #show license

License Table
-------------
Key  Installed  Expires  Flags  Service Type
---  ---------  -------  -----  ------------

License Entries: 0

Flags: A - auto-generated; E - enabled; R - reboot required to activate

The 1st controller does not show that a re-boot is needed either.

just to be sure, you did have the APs above 48 connect the local controller? it is not that you can add a local and continue like you did before, you will have to actively spread them over the controllers.

Ok, thanks boneyard,

 

I figured out how to create a 2nd system profile for the 2nd controller.  For some reason, I'm not quite there yet, though.  The access point that I'm testing with does attach to the 2nd controller but it still comes up as inactive.  I set up all the vlans as I saw in another post and followed instructions from the campus setup guide.  There are no vlan pools listed on my master so I did not do anything there.  Any idea what I might be missing?

 

Thanks!

Joel

so it is shown in the list of APs of the 2nd controller? it comes up as just Inactive, no other flags? can you provision it to another AP group?

 

does the log show anything?

The logs didn't show a thing, but I figured it out by looking at the ap-group as you suggested trying another.  The ap-group was not configured correctly.

 

Thanks for all of your help.

You will need to add licenses if you plan attach APs to this controller.

from privilege mode you can run the "add license <license key>"