Prime 3.4.1 Patch 2 - Copy & Replace AP broken

[patoberli]

I recently upgraded to the Patch 2 for PI 3.4.1.

I just discovered that the Single AP copy and replace functionality is now broken, at least when using APs with XOR radios (like the 2802i).

I'm replacing 3502i with 2802i. The copy&replace worked in Patch 1.

Now the job always fails with the error:

Failure:MEDIATION-1,Attempt to set conflicting attribute value,AP 3502AGN-1021-1, Interface 802.11a/b/g/n/ac,antennaGain

The new AP gets renamed, but will not be placed on the map, nor will the old AP get deleted.

Patrick

[Haydn Andrews]

I'm thinking that this is a bug, due fact it worked before the upgrade/ patch and now its not. 

Raise a TAC case.

If you need to keep going you could remove the patch:

patch remove

https://www.cisco.com/c/en/us/td/docs/net_mgmt/prime/infrastructure/3-4/command/reference/cli34.pdf

I would shut it down and take a snapshot  otherwise a back up

[patoberli]

Hello Haydn
Thanks for the hint about removing a patch. Wasn't aware that this should be possible now (wasn't in the past). Luckily I have just ~15 more APs to replace, so it's probably less risky doing that manually.

Support created the following bugid: CSCvo19314

[Haydn Andrews]

Hi Patoberli
Thanks for the bug ID.
Yeah I would agree its going to be less risky finishing it off manually than rolling back and maybe hitting another Prime bug.

[patoberli]

Quick update, yesterday was Patch 2 for PI 3.5 released and it contains this bug as fixed. I'm thinking now of upgrading to 3.5.
https://www.cisco.com/web/software/284272933/145488/PI_3_5_Update_02_Release_Note.pdf

[Scott Fella]

I know that feature worked for me on 3.5 update 1 and on update 2. I have also used it when I was on 3.4, don’t remember which update. I don’t have the x802’s, majority are 3702’s.

[Scott Fella]

Oh by the way, I built 3.5 from scratch as there are issues like usual when upgrading to a different code train. I did initially upgrade and ran into some db issues in which I decided to rebuild since I had the compute and only took me a few hours. 

[patoberli]

I'm now running the upgrade to 3.5 and then install the new patch 2. Let's see how it runs for me with the upgrade.

-
Sorry clicked in error on the "Accept as Solution" button.

[Scott Fella]

TAC mentioned that there is a known issue with upgrade from 3.4 to 3.5. Had issues with devices not showing up on the inventory but was in the db when you query. 

[patoberli]

Might that be this one, which was fixed in Update 2?

CSCvn71019