Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. If you'd prefer to explore, try our test area to get started. And see here for current known issues.

New Member

1600 and 2600 series aps no heatmap on cisco prime 1.4.0.45

 

 

after plotting 1600 series and 2600 series aps on the respective uploaded maps, there's NO heatmap coming out. 

setup composed of:

1600 series aps

2600 series aps

wlc running HA (7.4.121.0)

cisco prime 1.4.0.45

 

i noticed some errors from prime:

error 1: Exception while computing Coverage Heatmap. Message: COMMON-1 Try Recompute RF Prediction - this error message shows after positioning the aps on the map and clicking save button. it took sometime to display then this error message shows. 

error 2: Error in Recompute RF Prediction: SyntaxError:syntax error - this error shows after running recompute rf prediction option

 

i tried 802.11a/n and 802.11b/g/n protocols but still no heatmap. i tried unselecting ap heatmaps option and select it again but still no heatmap.

 

anybody have an idea what is going on? tia

 

  • Security and Network Management
4 REPLIES
New Member

Did you ever get any

Did you ever get any resolution to this problem
 

New Member

oh trent, sorry for answering

oh trent, sorry for answering your quesry so late. yes, we managed to solve the issue by just rebooting the cisco prime. that's all. hope this help

Bronze

Hi,Try removing both APs from

Hi,

Try removing both APs from the map and saving. Next, go back into the map an assign the APs. If they still do not map then I would look at the traps on the controller and make sure that the AP is fine. I would also look at performing an on demand refresh from the controller to the WCS. You can do this from the management page in WCS.

New Member

hi abwahid, thanks for the

hi abwahid,

 

thanks for the input. but what i have encountered was actually a bug.  it was settled by rebooting the PI.

 

504
Views
5
Helpful
4
Replies
This widget could not be displayed.