NMSP Down on MSE-PRIME-WLC

Hi,
I am trying to synchronize MSE with WLC by Prime.
Everything is correct but the NMSP service does not synchronize between them.
On the part of the WLC, OK, time and HASH, but in the MSE gives me the error of time.
Not sure what else I can do, Has anyone had the same problem?
Attach two images.
Thanks for all

MSE doesn't sync with WLC when added with PI 2.1.1
CSCup93101
Description
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.
Workaround:
Push a template (Templates > Features and Technologies > Controller > Security > AAA > AP or MSE Authorization) with MSE MAC address and key hash.
Please contact Cisco TAC for a patch.
Last Modified:
Dec 11,2014
Status:
Fixed
Severity:
2 Severe
Product:
Network Level Service
Known Affected Releases:
(1)
2.1(1)

Similar Messages

Prime, MSE and WLC NMSP Status

I have a 5508 WLC and have loaded a demo of Prime 2.1 and MSE 8.0.
The NMSP status is showing as inactive in Prime and MSE and therefore the clients are not showing on the map I have loaded.
Any ideas?

MSE doesn't sync with WLC when added with PI 2.1.1
CSCup93101
Description
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.
Workaround:
Push a template (Templates > Features and Technologies > Controller > Security > AAA > AP or MSE Authorization) with MSE MAC address and key hash.
Please contact Cisco TAC for a patch.
Last Modified:
Dec 11,2014
Status:
Fixed
Severity:
2 Severe
Product:
Network Level Service
Known Affected Releases:
(1)
2.1(1)

Prime MSE and WLC

Hi
Just installed Prime 1.3, currently upgrading wlc's to 7.0.240 (WiSM), we have a MSE as well, what version should this be on, currently on 7.0.230 as this matched the WCS?
I'm sure I read somewhere it had to be the same version as the controllers or the WCS.

Hi,
on this link you can find all compatibility information
http://www.cisco.com/en/US/docs/wireless/controller/5500/tech_notes/Wireless_Software_Compatibility_Matrix.html

MSE and WLC Operation

Hello,
I need to develop a solution of wIPS, but I'm not sure about the compatibility between the MSE and the WLC. My WLC is in 7.6.100 version and the MSE is 3310 model. Reviewing documentation, the MSE can only update until 7.3 version. Somebody knows if the version between wlc and mse must match, or which are the restrictions. Additionally, i can use Prime I or WSC, we have both systems.

but I'm not sure about the compatibility between the MSE and the WLC.
Here is the compatibility information.
http://www.cisco.com/c/en/us/td/docs/wireless/compatibility/matrix/compatibility-matrix.html#pgfId-148604
My WLC is in 7.6.100 version
You should consider upgrade this to min 7.6.130.0 as that is the stable code of 7.6.x software train.
MSE is 3310 model. Reviewing documentation, the MSE can only update until 7.3 version. Somebody knows if the version between wlc and mse must match, or which are the restrictions.
It does not need to be exact match between WLC & MSE versions. Refer release notes of each product & version, it will listed the new features added in each releases. Since MSE 3310 not supporting 7.3.x onward, I would plan for MSE migration anyway. You can go with VM in later versions of MSE & no need to buy hardware for that.
Additionally, i can use Prime I or WSC, we have both systems
Go with Prime as WCS is not supported any longer. What's the reason still keeping the WCS ?
HTH
Rasika
**** Pls rate all useful responses ****

Traversing down catalog tree w/ WLCS

I'm trying to make an efficient traversal down an entire catalog tree on
          WLCS with a large product catalog, starting at root, and putting all
          subsequent recursive subcategories (with links) into a DHTML menu for
          leftside.inc. WLCS isn't very good at traversing down the tree in my
          attempts (just breadcrumbing ancestors up), so any help would be greatly
          appreciated!
          Andy Hawks
          [email protected]


          "Andy Hawks" <[email protected]> wrote in message
          news:[email protected]..
          > I'm trying to make an efficient traversal down an entire catalog tree on
          > WLCS with a large product catalog, starting at root, and putting all
          > subsequent recursive subcategories (with links) into a DHTML menu for
          > leftside.inc. WLCS isn't very good at traversing down the tree in my
          > attempts (just breadcrumbing ancestors up), so any help would be greatly
          > appreciated!
          >
          > Andy Hawks
          > [email protected]
          >
          Just a "me too" posting - we've been trying to do the same thing.
          Currently we're using a very bodge solution - use JDBC to go directly to the
          category and hierarchy tables, and pull out all the relationships between
          categories, then use a bunch of Java and JSP processing to build the
          relevant displayed tree.
          This is not a nice solution, we'd prefer something slightly more elegant,
          possibly a custom tag solution?
          One thing we may do soon is to write a pipeline component which does the
          tree building using the CategoryManager to wander the hierarchy building up
          some form of "hashtable of hashtables" structure which we'll then store in
          the pipeline session for the JSP.
          Any better solutions greatfully received.
          cheers.

Cisco Prime WLC mismatch due to expired guest voucher

Hi Cisco Community,
a customer of mine likes to administrate his guest vouchers via lobby ambassador accounts on Cisco Prime.
Unfortunately if one of these Guest Vouchers expires Cisco Prime shows up an Audit Mismatch because this Voucher isnt present at the Controller but still present at Cisco Prime.
I have already tried to execute the Background Task -> Guest Accounts Sync manually but this doesnt solve the issue.
I will add some Screenshots for explanation.
1. I deploy the guest voucher to our WLC´s
2. The guest voucher is visible at the controllers security configuration tab.
3. The guest voucher reaches its validity period and disapears from all the controllers.
4.Then only one controller shows up a configuration mismatch.
After executing the Background Task -> Guest Accounts Sync manually this voucher will be shown as "Expired"
But the mismatch still remain between Controller and PI
Why is this happening and why does it happen only at one of the controllers??
How am I able to fix this issue?
Thanks for your support
regards
Benedikt

Since it has been a while, you might be better off opening a TAC case. If PI doesn't get the config refreshed from the WLC, thats when you get the error your showing. So maybe run the background task just on that one WLC and see if it fails or you get an error.
Thanks,
Scott
Help out other by using the rating system and marking answered questions as "Answered"

Visio Stencils MSE / Prime

Good day -
I am trying to locate some specific Visio stencils and am struggling to locate them.
MSE 3300
Prime Infrastructure appliance
Can somebody point me to what Visio stencil pack these belong to?
Thanks

More specifically MSE3550 appliance you can find here (wireless section)
http://www.cisco.com/en/US/products/hw/prod_cat_visios.html
Did not find icon for the "Prime Infrastructure Appliance" in that section though.
HTH
Rasika
**** Pls rate all useful responses ****

Is there a MSE/Prime Infrastructure map legend?

I am looking for a legend for the maps in Prime Infrastructure. I have found one, but it only has a few items on it. I have many showing up on my maps along with numbers on the side of them. Any document to reference would be great. Thanks!

Hello,
May the link below help you out:-
http://www.cisco.com/en/US/docs/wireless/prime_infrastructure/1.3/configuration/guide/pi_13_cg.pdf

MSE NMSP status inactive after WLC 5508 HA failover

I have a customer who has a Prime Infrastructure 2.0 server and MSE 7.4 server for Context Aware Services.   The MSE also has the AeroScout Tag Engine for Tracking the AeroScout RFID tags it has deployed.    They have a WLC 5508 HA pair running version 7.4 at their main campus, and two other standalone WLC 5508s at 2 other smaller campuses.   The issue they are having is that when a failover of the WLC5508 HA pair occurs at their main campus, they lose tracking of the WiFi and AeroScout clients.   The other WLCs are not affected.
When this happens, the Prime Infrastructure show the NMSP status of the WLC5508 HA pair as inactive.   The PI gives the message that the time of the WLC is before the MSE. But the PI, MSE, and WLCs are all synched to the same Campus NTP server, and the time shows the same time down to the second.   I can get the WLC communicating to the MSE again by removing the Assignment of the WLC to the MSE, then re-adding it to the MSE a few minutes later.
We are not sure why the WLC 5508 HA pair occasionally fails over to the standby or back to the primary. We have not seen any cause for the HA pair failover.   Is there something we need to do to the WLC HA pair so that the NMSP still works if a failover of the WLC occurs. The customer is planning on converting one of their other Standalone WLCs to a HA Pair also.

That is what I have been doing. But the problem is that the I have had to do this about 3 times in the last 6 weeks. Each time correlates with a failover of the WLC 5508 pair.   Will this have to be done each time there is a failover, or is there some setting on the WLCs, MSE, or Prime Infrastructure that can prevent having manually to un-assign, then re-assign the WLC to the MSE.

Prime 1.3: incorrect MSE license count

Hello!
I have the following equipment for the WiFi infrasrtucture
Prime NCS (1.3)
MSE 3355 (7.4.100.0)
WLC 5508 (7.4.100.0)
The problem is that Prime 1.3 incorrectly displays MSE wIPS Monitor Mode APs license count.
I have 20 monitor mode LAPs, but Prime displays only one LAP under MSE wIPS Monitor Mode APs count. In addition this one LAP is not in monitor mode.
The wIPS Monitor Mode APs license (AIR-WIPS-AP-25) is permanent.
At first MSE had been shipped with 7.2.110 with preinstalled wIPS license and then was uprgaded to 7.4.100.
MSE and WLC are synced.
I tried to change the modes for these LAPs from monitor to local and backwards, but had no luck.
Has anyine faced this problem?

Thank you, Scott!
This is really, confusing, because there is no exact information about it in documentation.
In conclusion (correct me, if I am wrong):
MSE 7.4 supports the old AIR-WIPS-AP-25 license, but doesn't display it in proper way. This situation is normal and it should be so.

Cisco Prime Infrastructure 2.0 Alarms (switch port down)

We have a cisco Prime Infrastructure 2.0 managing switches, routers and AP.
By default, when a port of a switch goes down, the cisco Prime Infrastructre generates a Critical Alarm for that. (this is a problem, because every phone of laptop disconnection will generate a critical alarm for me)
I found out that if we go to Administration --> Alarm Severity --> Link down, I can change the Alarm from Critical to another type of alarm.(ex: warning)
The problem is that I want to keep the Critical Alarm for my Uplinks ports and for some important switch ports, and I would like to make the alarm as warning for the normal user ports.
I know that I can create Port Groupping and add ports to each group and apply monitoring templates on those groups. But This couldn't Help me solving my alarm problem.
So I just need to know how to manage the alarms severity for each group of ports.
Thank you

Hi,
Same problem here.
I am using Cisco Prime Infrastructure 2.0 (evaluation version for 60 days). I want to deploy port monitoring for my trunk ports between switches and some other important ports e.g. servers. Basically I want to get alarms when these ports are down, there are errors on ports and etc.
So in Design>Port Grouping I created User Defined group with important ports. In Deploy>Monitoring Deployment I selected Interface Health (default)>Deploy selected Port Groups and when selected port group I created.
Now the rule shows Deployed: Yes and Status: Active. After that I just pulled out one port which was in monitored group, waited 5min as it is set in Interface Health (default) template, and nothing happened, and worse, alarms started to show up of other ports where regular users are connected (computers was turned off), which I do not want to see at all. I tried redeploy template, I even created my own template but still no desired result.
Any suggestions how to make port monitoring work?

MSE 8.0.110.0 not showing any clients

hi all,
i just posted a reply in some other thread stating the same thing but decided to make my own topic.
set-up:
2x5760 running 3.6.0
mse appliance running 8.0.110.0
prime infra in VM running 2.2
ap - 3702I / E
problem:
wireless clients not showing on the prime floor maps.
what have done so far:
wlc synced with mse thru nmsp - check
wlc added to prime - check
mse added to prime - check
mse synced with wlc thru prime - check
all aps positioned on the maps - check
CAS enabled on mse - check
NTP configured to wlc , mse and prime - check
check time all synced
nmsp status in mse - active
nmsp status in wlc :
WLC1#show nmsp status
MSE IP Address   Tx Echo Resp Rx Echo Req   Tx Data     Rx Data
x.x.x.x      618           618           43878       10
WLC1#show nmsp subscription sum
Mobility Services Subscribed
Server IP         Services
x.x.x.x       RSSI, Info, Statistics, AP Monitor, Attachment, Wired Location
WLC1#show nmsp subscription deta
Mobility Services Subscribed by 10.29.220.9:
Service         Subservice
RSSI            Mobile Station, Tags, Rogue
Info            Mobile Station, Rogue
Statistics      Mobile Station, Tags
Attachment      Wired Station
Location        Subscription
AP Monitor      Subscription
troubleshooting done so far:
deleted then added mse on prime then resynced to wlc
reconfigured nmsp on wlc and resynced again with mse
rebooted mse - no avail
rebooted prime - no avail
reboot wlc - not an option coz theres a lot of users =)
tia,
chris

Thanks Pete, I have done that, in fact I used a useful utility to update that property on a batch of servers.
Thanks for the thought, any additional ideas?
Cheers
Andrew

MSE not detecting associated clients

Hi,
i have one MSE 7.0, one WLC 7.6.120 and CPI 2.1. the AP's are 1602i and 3702i
I had a map in CPI, showing my AP's, but i can't see associated clients, if i modify the client filter to all clients, they appear in the map, but for some reason when i modify back the filter to associated clients the followinf message appears:
there are no clients on this floor. Either you don have any MSE which locates clients or none of your MSE detected any clients on this floor.
NMSP status is active.
WLC and MSE are synchronyze.
anybody knows whats the problem?
thank you!

Hi, thanks for your reply.
I checked your link, but in my opinion must be other problem, because sometimes i can see associated clients in CPI map, but most part of the time only shows clients when i modify the client filter to all.
NMSP protocol is up and active between MSE and WLC, service are synchronyzed.
NTP is configured in CPI, WLC and MSE, and time is the same.
In the top of the map there is a message:
Data may be delayed up to 15 minutes or more depending on background polling interval
I waited for more than 30 minutos and the associated client still not showed on the map. furthermore, in my opnion, 15 minutes is a long time to locate a client, if i have to wait 15 minutes to locate every client in my network, there is no way to make location works!
Regards!

HA in 5508 WLC running 7.3 image

Hi ,
For configuring the HA between the WLC we will be configuring these in both controllers
1)management ip
2)Redundant management ip
Once HA is done , standby wlc will get all the configuration including management interface ip address.So the Active WLC only visble on cisco Prime.
1)If active goes down , whether the standby WLC will work with its management IP or with active wlc ip address?
2)Once HA is done , standby wlc will get all the configuration including management interface ip address.So is there possiblity of network loop in the below scenario?

Is it possible that Cisco rushed the HA functionality out the door prematurely without proper regression testing to thwart market pressure from Aruba's 6.1.3.4 HA announcement back in August. http://www.arubanetworks.com/news-releases/aruba-delivers-high-availability/ http://www.arubanetworks.com/pdf/technology/TR_HABenchmark.pdf
7.3.101.0 was posted on CCO around the same timeframe.
There is a 7.4 engineering release that will address the following, but only 1 seems to target HA issues...
CSCuc06605 AP1142 r0 coredump: corrupted rcv pak pointer
CSCub88183 WLC Crashing at emWeb instruction: ewaFormSubmit_login_callback
CSCud83441 7.4 changes radius callStationIdType from radio to eth mac
CSCuc84338 Fenway AP showing up in Local mode instead of MAP or RAP mode
CSCud16003 MSAP gets unavailable after certain period.
CSCue01983 3600 sends continueos corrupted deauth frames when in WIPS + 7.4
CSCue09354 cant find rogue on wire, if rogue ap on non native vlan of RD's trunk
CSCue13108 TPC in 7.4 reduces transmit power to lower than expected values
CSCud99466 Debug leaking due to lack of mac address for APF
CSCud97830 Telnet Access to WLC lost
CSCuc07384 Web access issue on SRE with 7.2 code
CSCud93574 Memory Leak on Anchor WLC for client auth trap.
CSCue27021 Memory leak in bonjour
CSCud95613 WISM 2 crash after upgrading to 7.4.100.0 only when High traffic load
CSCue02707 HA redundancy does not fail-over to standby when powercycled
CSCud10200 CAP1552 local mode not obeying 30 min channel blacklist after DFS event
CSCue19334 Crash DHCP Socket Task nfaSyncMsgSendToTask dhcpSendRaw
CSCue33125 Unable to enable "bootp-broadcast" with HA SSO configured

Clients Freeze when MSE is deployed ?

Hi All
I just wanted to ask the community if anyone has ever experienced this problem.
Problem description:
At a customer we where making a small test with MSE, and a couple of tags.
When we enabled / setup the MSE in NCS, and enable synchronization with the controller that was running the APs in our location, all of the clients (a Bar code scanner) the customer uses in his production started to freeze.
There was simply no reponse from the operating system, just plain frozen.
Rebooting the devices didn't solve the problem either. The minute they had started up, they froze.
The APs in the affected productionarea, was also under the control of the WLC we where using for our small test.
All other production areas, with APs not associated to this controller, where not affected.
Other types of clients in the area where also not affected (PCs, smartphones, tablets and so on) only the bar code scanners.
The scanners are using a 802.11g NIC from Summit http://www.summitdata.com
The client are being reported as supporting CCX v4 in NCS.
The minute we shut down the MSE everything returned to normal (maybe after another reboot of the clients, I cant remember).
The customer has also made another test with the client, where he has turned off CCX in the NIC properties.
When doing this the client does not freeze.
/End Problem description.
So what could be the problem ? and has anyone else experienced something like this ?
I speculate that the client NIC hears some addition to CCX relating to location, and fails (catastrophically) because it does not understand this addition.
I know that tags send out CCX tag information, that the wireless system then hears, processes and sends to the MSE.
But does the wireless system start to send out, or request new information from normal CCX clients when enabling MSE ?
Just looking for some logical explanation :-)
/Thomas

I've also just encountered a failure to associate using LXE MX9 scanners with a Summit card. Moving the setting from CCX FULL to CCX OPTIMIZED in the SCU resolves but is not a recommendation from Honeywell/LXE. have you had any response from TAC or Teklogix?

NMSP Down on MSE-PRIME-WLC

Similar Messages

Maybe you are looking for