Guest

Preview Tool

Cisco Bug: CSCup93101 - MSE doesn't sync with WLC when added with PI 2.1.1

Last Modified

Sep 17, 2019

Products (1)

  • Cisco Prime Infrastructure

Known Affected Releases

2.1(1)

Description (partial)

Symptom:
NMSP is not active between MSE and WLC when added using PI 2.1.1.

Conditions:
This applies to only MSE added Prime Infrastructure after upgrade to 2.1.1 on Prime Infrastructure.
If the MSE was already added to Prime Infrastructure in 2.1 or previous releases, and then upgrade to PI 2.1.1 was performed customers will not run into the NMSP problem between MSE and WLC after the PI upgrade to PI 2.1.1.

Related Community Discussions

PI2.1.1 に登録した MSE と WLAN コントローラ間の NMSP Status が Inactive となる問題
2015年4月24日(初版) TAC SR Collection 主な問題 PI2.1.1 に登録した MSE と WLAN コントローラを同期させても、NMSP Status が Inactive となる問題が発生します。 この場合、NMSP セッション確立時に使用する MSE の Key Hash 値と WLAN コントローラが認識している Key Hash 値が一致しているかどうか確認ください。 (1) MSE の Key Hash 値を確認する方法 [root@MSEv7-6 ~]# cmdshell cmd> show server-auth-info invoke command: com.aes.server.cli.CmdGetServerAuthInfo AesLog queue high mark: 50000 AesLog queue low mark: 500 ---------------- Server Auth Info ---------------- MAC Address: xx:xx:xx:xx:xx:xx Key Hash: aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa ...
Latest activity: Apr 24, 2015
Bug details contain sensitive information and therefore require a Cisco.com account to be viewed.

Bug Details Include

  • Full Description (including symptoms, conditions and workarounds)
  • Status
  • Severity
  • Known Fixed Releases
  • Related Community Discussions
  • Number of Related Support Cases
Bug information is viewable for customers and partners who have a service contract. Registered users can view up to 200 bugs per month without a service contract.