03-09-2022 03:36 AM
Hello,
We're installing new 9800 WLCs and we have an issue with the AP discovery feature on Prime 3.9.
The AP Discovery status stay in "Not Yet Completed", Telemetry failed and the AP count at "0" as shown below
FYI, it works fine with all other WLC model deployed 5520, 5508, 85xx., etc..
Thank you for your help.
Solved! Go to Solution.
03-16-2022 02:53 AM - edited 03-16-2022 04:25 AM
The solution was to open some new firewall rules as not needed for older WLC models
*************************************************************
Reachability is always needed from PI to WLC on Port 830
PI/admin# ssh <9800_ip_address_added_to_primeinfra> <priv15_username> port 830
And from WLC to PI on port 20830 or 20828
telnet <Prime_Infrastructure_ip_address> <20828/20830>
show telemetry internal protocol cntp-tcp manager <Prime IP> 20830/20828
***************************************************************
03-09-2022 04:52 AM
what is the version WLC 9800 check the compatable with PI 3.9 first step :
https://www.cisco.com/c/en/us/td/docs/wireless/compatibility/matrix/compatibility-matrix.html
03-09-2022 07:55 AM
Hello,
Already done of course
C9800-L-F with IosXE 17.3.4 is compatible with PI 3.9.
Thank you
03-09-2022 08:12 AM
- FYI : https://bst.cloudapps.cisco.com/bugsearch/bug/CSCvx46784?rfs=iqvred
03-09-2022 08:27 AM
We're using the 3.9 PI version which seems to not match this bug and no more this one : CSCvv04560
03-09-2022 09:35 AM
- Indeed but PI3.9 is also not mentioned as any of the resolving release , in fact no resolving releases are mentioned. That could mean that the bugs are still present in your current Prime version. If needed or wanted escalate with TAC and mention the bug reports too.
M.
03-09-2022 11:37 PM
Ok thank you.
Then I will open a case for this issue.
03-09-2022 12:06 PM
Hello,
do you have netconf enabled on the 9800s ?
03-10-2022 11:08 PM
Hello Georg,
I've enabled it and checked the step described in the link you've prtovided. I thank you for that, it' susefull.
Unfortunately, issue continue.
I will open a case.
03-16-2022 02:53 AM - edited 03-16-2022 04:25 AM
The solution was to open some new firewall rules as not needed for older WLC models
*************************************************************
Reachability is always needed from PI to WLC on Port 830
PI/admin# ssh <9800_ip_address_added_to_primeinfra> <priv15_username> port 830
And from WLC to PI on port 20830 or 20828
telnet <Prime_Infrastructure_ip_address> <20828/20830>
show telemetry internal protocol cntp-tcp manager <Prime IP> 20830/20828
***************************************************************
08-24-2022 02:46 PM
I run to the same issue and I wonder how you resolved it. Please let me know.
08-25-2022 01:09 AM
you need addional ports to be open for the new WLC for the prime to establish the connection, Port 830 and 20830 20828
08-31-2022 07:49 AM
The solution was to open some new firewall rules as not needed for older WLC models
*************************************************************
Reachability is always needed from PI to WLC on Port 830
PI/admin# ssh <9800_ip_address_added_to_primeinfra> <priv15_username> port 830
And from WLC to PI on port 20830 or 20828
telnet <Prime_Infrastructure_ip_address> <20828/20830>
show telemetry internal protocol cntp-tcp manager <Prime IP> 20830/20828
***************************************************************
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide