Restored the date base found AP location lost in heat maps

jkumar3 · ‎07-26-2018

We are using Cisco Prime infrastructure 3.2.1

as our data base crashed ......we got the data base restored .

Heat maps >> found A.P's location were lost ........though the AP are recovered .

Cisco says it's by default product design whenever you restore the data base it will only restore Heat maps with AP 's not with original mapped location .

Any idea is it true upon restoration of data AP' location lost .

Rasika Nayanajith · ‎07-26-2018

"our data base crashed ......we got the data base restored"

Pls provide bit more information what happens & how did you restore it ?

I Have done backup & restore & I did not have to go through placing AP on maps.

HTH

Rasika

jkumar3 · ‎07-26-2018

we were not able to access the GUI version of the Cisco Prime Infrastructure 3.2.1 on 19th July.

We log in via CLI found:

usmkeapln7003/admin# show ver

Cisco Application Deployment Engine OS Release: 3.1
ADE-OS Build Version: 3.1.0.001
ADE-OS System Architecture: x86_64

Copyright (c) 2009-2017 by Cisco Systems, Inc.
All rights reserved.
Hostname: usmkeapln7003

Version information of installed applications
---------------------------------------------

Cisco Prime Infrastructure
********************************************************
Version : 3.2.0
Build : 3.2.0.0.258
Critical Fixes:
PI 3.2.1 Maintenance Release ( 1.0.0 )
usmkeapln7003/admin#

usmkeapln7003/admin# ncs status
Health Monitor Server is running. ( [Role] Primary [State] HA not Configured )
Database server is stopped
FTP Service is running
TFTP Service is running
Matlab Server is running
Matlab Server Instance 1 is running
Matlab Server Instance 2 is running
Matlab Server Instance 3 is running
NMS Server is running.
SAM Daemon is running ...
DA Daemon is running ...
Compliance engine is running
usmkeapln7003/admin# show back history
Mon Jun 11 05:18:10 CDT 2018: backup usmkeapln7003-180611-0331__VER3.2.0.203.47_
BKSZ331G_CPU16_MEM4G_RAM23G_SWAP15G_APP_CK1082870134.tar.gpg to repository defau
ltRepo: success
Tue Jun 12 05:22:12 CDT 2018: backup usmkeapln7003-180612-0330__VER3.2.0.203.47_
BKSZ331G_CPU16_MEM4G_RAM23G_SWAP15G_APP_CK1281178713.tar.gpg to repository defau
ltRepo: success
Wed Jun 13 05:12:20 CDT 2018: backup usmkeapln7003-180613-0331__VER3.2.0.203.47_
BKSZ331G_CPU16_MEM4G_RAM23G_SWAP15G_APP_CK2916121950.tar.gpg to repository defau
ltRepo: success
Thu Jun 14 05:12:43 CDT 2018: backup usmkeapln7003-180614-0331__VER3.2.0.203.47_
BKSZ331G_CPU16_MEM4G_RAM23G_SWAP15G_APP_CK3897665157.tar.gpg to repository defau
ltRepo: success
Fri Jun 15 05:32:30 CDT 2018: backup usmkeapln7003-180615-0334__VER3.2.0.203.47_
BKSZ331G_CPU16_MEM4G_RAM23G_SWAP15G_APP_CK1558032544.tar.gpg to repository defau
ltRepo: success
Sat Jun 16 05:10:58 CDT 2018: backup usmkeapln7003-180616-0330__VER3.2.0.203.47_
BKSZ331G_CPU16_MEM4G_RAM23G_SWAP15G_APP_CK2452244926.tar.gpg to repository defau
ltRepo: success
Sun Jun 17 05:39:14 CDT 2018: backup usmkeapln7003-180617-0330__VER3.2.0.203.47_
BKSZ331G_CPU16_MEM4G_RAM23G_SWAP15G_APP_CK3834106794.tar.gpg to repository defau
ltRepo: success
Mon Jun 18 05:19:42 CDT 2018: backup usmkeapln7003-180618-0330__VER3.2.0.203.47_
BKSZ331G_CPU16_MEM4G_RAM23G_SWAP15G_APP_CK422182408.tar.gpg to repository defaul
tRepo: success
Tue Jun 19 05:11:35 CDT 2018: backup usmkeapln7003-180619-0330__VER3.2.0.203.47_
BKSZ331G_CPU16_MEM4G_RAM23G_SWAP15G_APP_CK1870947356.tar.gpg to repository defau
ltRepo: success
Wed Jun 20 05:20:20 CDT 2018: backup usmkeapln7003-180620-0330__VER3.2.0.203.47_
BKSZ331G_CPU16_MEM4G_RAM23G_SWAP15G_APP_CK1509868686.tar.gpg to repository defau
ltRepo: success
Thu Jun 21 05:23:03 CDT 2018: backup usmkeapln7003-180621-0331__VER3.2.0.203.47_
BKSZ331G_CPU16_MEM4G_RAM23G_SWAP15G_APP_CK3094578569.tar.gpg to repository defau
ltRepo: success
Fri Jun 22 05:24:28 CDT 2018: backup usmkeapln7003-180622-0331__VER3.2.0.203.47_
BKSZ331G_CPU16_MEM4G_RAM23G_SWAP15G_APP_CK595930037.tar.gpg to repository defaul
tRepo: success
Sat Jun 23 05:11:52 CDT 2018: backup usmkeapln7003-180623-0330__VER3.2.0.203.47_
BKSZ331G_CPU16_MEM4G_RAM23G_SWAP15G_APP_CK3255331506.tar.gpg to repository defau
ltRepo: success
Sun Jun 24 05:08:15 CDT 2018: backup usmkeapln7003-180624-0330__VER3.2.0.203.47_
BKSZ331G_CPU16_MEM4G_RAM23G_SWAP15G_APP_CK2273948009.tar.gpg to repository defau
ltRepo: success
Mon Jun 25 05:25:09 CDT 2018: backup usmkeapln7003-180625-0330__VER3.2.0.203.47_
BKSZ331G_CPU16_MEM4G_RAM23G_SWAP15G_APP_CK4045679485.tar.gpg to repository defau
ltRepo: success
Tue Jun 26 05:43:11 CDT 2018: backup usmkeapln7003-180626-0332__VER3.2.0.203.47_
BKSZ332G_CPU16_MEM4G_RAM23G_SWAP15G_APP_CK3957831382.tar.gpg to repository defau
ltRepo: success
Wed Jun 27 05:43:17 CDT 2018: backup usmkeapln7003-180627-0331__VER3.2.0.203.47_
BKSZ332G_CPU16_MEM4G_RAM23G_SWAP15G_APP_CK552229952.tar.gpg to repository defaul
tRepo: success
Thu Jun 28 05:42:00 CDT 2018: backup usmkeapln7003-180628-0331__VER3.2.0.203.47_
BKSZ332G_CPU16_MEM4G_RAM23G_SWAP15G_APP_CK3712250338.tar.gpg to repository defau
ltRepo: success
Fri Jun 29 05:38:15 CDT 2018: backup usmkeapln7003-180629-0331__VER3.2.0.203.47_
BKSZ332G_CPU16_MEM4G_RAM23G_SWAP15G_APP_CK2884234230.tar.gpg to repository defau
ltRepo: success
Sat Jun 30 05:29:43 CDT 2018: backup usmkeapln7003-180630-0331__VER3.2.0.203.47_
BKSZ332G_CPU16_MEM4G_RAM23G_SWAP15G_APP_CK851690446.tar.gpg to repository defaul
tRepo: success
usmkeapln7003/admin#

TAC have restarted the NCS status & reset the data base .

& restored the data base from repo

after the data base is restored & we do find the AP's & heat maps but heap map lost their location for the dates 26th June & 4 th July on these two dates Users have added new A.P's

tac is saying it's product by design won't restore AP location on heat map .

Rasika Nayanajith · ‎07-26-2018

If that is the case we have to go by what TAC is saying. I know it is time consuming task, looks like no choice here.

Have you got any exports of map in recent past ? if so you can try to import that & see

HTH

Rasika