Network Management

Hey all!

I recently replaced a customers M3 controller with two 7220 controllers. I migrated configuration, assigned IP-adresses and made the change.

In Airwave though, one of the controllers came up in new device list since it was a backup master but the primary one was still contacted on the same old IP-address and just complained about that it had found a new mac address on the device. I clicked reset mac (maybe this was my error) and then tried to rename it to the new name but it doesn´t happen. When I view the information about it it´s all the old information about "contact", Upstream device, interfaces etc. It lists the controller as a 3600, must have been wrong the whole time since it used to be an M3.

I´m using SNMPv2 and the polling succeeds. How can I update all of this info without loosing historical data?

Thanx alot,

These articles may help describe Replace Hardware in AirWave:

http://community.arubanetworks.com/t5/Unified-Wired-Wireless-Access/Replace-Hardware-Migration-to-new-controller/m-p/200285/highlight/true#M40022

http://community.arubanetworks.com/t5/Unified-Wired-Wireless-Access/Difference-between-quot-Replace-hardware-quot-and-just-deleting/td-p/45632

Hi!

Thank you for your advice. I tried changing the IP-address of the controller I wished to replace to a non-existent one so the controller appeared down. Then I added the new controller again using Device setup -> add. Finally I chose replace hardware on the down controller and picked the one I just added to replace it. The replacement was successful but it only updated the model number from 3600 to 7220.

These parameters are still stuck (wrong): Name, Upstream device, Upstream port, SNMP Contact.

I manually put auto discover upstream device to "off" and choose none. That removed the upstream device but the upstream port is still stuck. I´ve tried to rename the device but it doesn´t change.

Any more tips or will I need to delete and add? I´m running AMP 8.0.3

Thanx,

Name and SNMP contact should have come up properly from the Device Setup -> Add step.

Please double check the values that SNMP responds with:

# s2w <controller ip address> <community string> <OID>

OIDs = sysName, sysContact, sysDescr

example:

# s2w 10.10.10.10 secretpw sysName

RFC1213-MIB::sysName.0 = STRING: "7220-aw-rob"

If these responses are all correct, you can force a recheck of these data fields from AirWave by using the 'import settings' on the Device Manage page.  This import is different from import on the audit page.  Import settings on the manage page is only refreshing data that is checked 1-time at the time of adding the device.  Import from the audit page is what updates the group config template.

Hi Rob!

I verified the SNMP commands and all the values returned by the controllers are the correct new ones. When I tried the import settings I asume you mean the one where I click "Modify Devices" on the group monitor page, check the controller with the issue, and pick "Import settings from selected devices (and discard current predevice desired settings)"

When I do that, I get the error message at the top of the page: "No selected devices have settings to import."

If I click the controller with the issue and go to the "Manage" page, there´s no button for importing settings. Is this perhaps a group setting I need to enable? We have Audit set to No on the group configuration.

We´re running Airwave 8.0.3, perhaps this is solved in a more recent version?

Thanx,

Any more ideas on this or do I need to delete and readd?

odd, in my group settings i have audit to yes but Manage local configuration on controllers: set to no and i am able to import settings and i am running 8.0.0.

-edit- added missing step 3, otherwise it will complain of 2 device with same mac address

Try the following:

1) go to manage page for the controller that's showing wrong model

2) set IP to something else that won't respond to SNMP

3) in the db, set the lan_mac address to something different as well (this step is required in order to fake out the database for the replacement)

# dbc "update ap set lan_mac = '00:0B:86:11:11:11' where id=<ap_id>"

ap_id is gotten from existing controller entry's URL

4) go to device setup -> add

5) add the controller again (with correct IP)

6) confirm that it comes up with correct model

7) then go to the original controller entry (it should be reporting down by now) and do replace hardware, selecting the newer good controller entry as the replacement

This should keep historical data attached to the controller entry.

Hi!

Sorry for the late response, I awaited firmware upgrade before I attempted your above solution. I´m now on 8.0.8.1 and unfortunately I still have the same problem after going through all of your steps. Everything works fine until the very last step, replace hardware. I click in to the old controller(nemo) that is down after changing IP, LAN mac etc and choose replace hardware. In the list I can find the newly added controller(sonic) added with the correct name and I choose replace.

Everything that was stuck before is still stuck. The name, the upstream port and the SNMP information. It seems as if it has taken the name, configuration wise, but ignores it display wise. See attached screenshot. When I try to rename "nemo" to "sonic" it says there are no changes to be made.

Any other suggestions?

That sounds like there's an issue with the steps taken.  Please open a support case and have them document the step by step taken.  Meanwhile, I will add it to the queue for additional testing.

Better late than never, we finally got this issue resolved with Aruba TAC.

What was probably causing the issue was that the "Use Global Aruba Configuration:" was enabled under AMP Setup even if we weren´t using it. This created a global template that probably had the name and snmp information stick to that controller somehow.

After importing after disabling the global configuration all the information updated, except for the upstream port which was still stuck. Since I don´t care about the history of the switches and went in and deleted the switch I knew was the old uplink switch and that also made the incorrect upstream port on the controller go away! I´m guessing this information is acctually stored in the switch entry of the database so maybe doing an import/poll on the old switch would´ve cleared the error aswell.

Thanks for all your help!

Chris

pmonardo:

I think import settings is only related to configuration and we´re only monitoring with Airwave. I would prefer not to start importing configurations to my groups as it it shared with other controller.  (We´re not auditing either)

Please correct me if I´m wrong.