Network Management

Reply
New Contributor
Posts: 3
Registered: ‎01-03-2014

Replacing a device in AirWave with an existing device

Hi Everyone,

 

When replacing a device (AP1) in AirWave with an existing device (AP2), AP2's entry in AirWave seems to disappear, along with all historical data.

 

If you want to see historical data for AP2 (from before it replaced AP1) is there any way to do this or is that information gone forever?

 

Alternatively, if AP2 was used to replace AP1 is there another way to perform the replacement in AirWave that doesn't destroy the old data?

 

Any help would be appreciated, thanks. :)

 

-Gillian

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

Re: Replacing a device in AirWave with an existing device

Airwave's device replacement requires that:

 

- AP1 is on the Down List

- AP2 has no history, because it's history will be replaced by AP1 when you go through the hardware replacement workflow.

 

 



Colin Joseph
Aruba Customer Engineering

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

New Contributor
Posts: 3
Registered: ‎01-03-2014

Re: Replacing a device in AirWave with an existing device

Is that a hard-coded requirement? Because I was able to perform the replacement even though AP2 had history...

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

Re: Replacing a device in AirWave with an existing device

If you use the hardware replacement workflow, AP2's history is replaced with AP1.  If you just delete the first object and change the name on the second one, it will only have the history of the second, or newer device.  There is no way to merge the histories of two devices.  What did you want to do?

 



Colin Joseph
Aruba Customer Engineering

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

New Contributor
Posts: 3
Registered: ‎01-03-2014

Re: Replacing a device in AirWave with an existing device

Basically, one of our clients replaced a down AP (AP1) with another AP from a decommissioned network (AP2). The catch is that the client requires historical data be kept for all nodes, regardless of whether or not they're part of an old network that's been taken down.

 

To clarify:

When we did the change, AP1 was showing as down and AP2 was showing as up with mismatched config (AP2's name etc. had already been changed on the controller). Then we did a device replacement on AP1 and selected AP2. This got rid of AP2's entry and AP1 then showed as up with its own history.

 

Ideally, we wanted to have some way to change the MAC of AP1's entry so we can keep AP1's data while still keeping AP2's data as some sort of archived entry (despite the confliction MACs).

 

From what you're saying that's not really possible and the data from AP2 is just gone.

Search Airheads
Showing results for 
Search instead for 
Did you mean: