Location Appliance Issue

Hi
I have a WCS that has been upgraded to Version 7.0.164.0 and a Location Appliance that is running 6.0.102.0
The RFID tracking is no longer working.
I can't see that WCS 7.0.164.0 supports the 6.0.102.0 on the Location Appliance and think I need to back off the Location Appliance to 6.0.101.0
Has anyone had similar problems?
Has anyone reverted the software on a Location Appliance before?
Thanks for any advice.
Regards
Roger

Hello Roger,
this is due to bug CSCth48443
Location Appliance stops tracking Wireless Client when WLC code is 7.0
you need location image 006.000.103
please contact us (TAC) to get this image posted to your CCO..
Kind regards
Talal
===
please rate answers that you find useful , and mark as answered - when it is :-) - so others can find it easily

Similar Messages

Location Appliance Help required

Hello,
I have a WCS,WLC and LOC deployed. The integration betwen the WLC and WCS is working perfectly. We didn't put a lot of access points in the deployment because we didn't need acurate location tracking but at least we need some.
The problem is the location appliance is not able to pull any information about the connected clients. No clients shows on the map eventhough the APs report connected clients.
One issue I had is when I try to synchronize the network design with the location appliance I get the below error:
"Element found and will be pulled to WCS".
I appreciate any help with issue as it is quite urgent,
Regards,

Hello Sabhasin,
The message I was receiving above was due to time difference between the location appliance and WLC. Now all systems are using an NTP server and in sych.
As for the location on the map I was able to point the problem to the following:
If you delete the location from the WCS and add it again and then go to the MAP you can see the clients and the rogue stuff within a two minutes time range. When the two minutes pass you no more able to see the last two minutes info from the location.
If you choose the past 5 minutes then you see the information on the map. When 3 more minutes pass you no more see anything for the last 5 minutes data.
If you choose 15 minutes after 10 minutes pass you no more see anything on the map.
If you delete the location appliance and add it again you will be able to see the information again starting with two minutes and again same pattern.
Therefore, the issue is that the info is pulled from the location once you add it and after that nothing is pulled.
I tried synchronizing all the servers and no luck,
I appreciate your response,
Regards,

Location Appliance not detecting elements after upgrade

Hi
Our loacation appliance had version 2.1.42.0. After upgrading it to version 3.1.36 there are no clients been discovered.
I must admit we don't have read-write access to the WLAN Controller 4400, and read somehwere that ntp plays a big role from AppLoc ver 3.0 upwards in this. The WCS , Location Appliance and the WLC is syncing to the same NTP server.
Some errors I have noticed:
5/15/08 00:12:38 ERROR[locp] [13] Error in ConnectHandler(endPoint) <LocpSessionTarget mode=CLIENT><LocpEndPoint status=HANDSHAKE t
otalBytesSent=19740 totalBytesReceived=16730><LocpEndPoint.Key host=10.1.30.10 port=16113/></LocpEndPoint></LocpSessionTarget>
5/15/08 00:12:38 TRACE[com.aes] [13] [ConnectHandler:handle-09] THROW
javax.net.ssl.SSLException: Received fatal alert: certificate_unknown at com.sun.net.ssl.internal.ssl.Alerts.getSSLException(Unknown Source) at com.sun.net.ssl.internal.ssl.SSLEngineImpl.fatal(Unknown Source) at com.sun.net.ssl.internal.ssl.SSLEngineImpl.fatal(Unknown Source) at com.sun.net.ssl.internal.ssl.SSLEngineImpl.recvAlert(Unknown Source) at com.sun.net.ssl.internal.ssl.SSLEngineImpl.readRecord(Unknown Source) at om.sun.net.ssl.internal.ssl.SSLEngineImpl.readNetRecord(Unknown Source) at com.sun.net.ssl.internal.ssl.SSLEngineImpl.unwrap(Unknown Source) at javax.net.ssl.SSLEngine.unwrap(Unknown Source) at com.aes.server.locp.transport.IOChannelSecure.doHandshake(Unknown Source) at com.aes.server.locp.transport.LocpTransportService$ConnectHandler.handle(Unknown Source) at com.aes.server.locp.transport.ChannelEventDispatcherImpl$HandlerTask.run(Unknown Source)
The WCS is Version 5.0.56.2 , Type: Base + Location; Licensed APs: 1000.
I have reverted back to the old version and its working fine now. And we have only a few hours of change control to get this upgrade right.
Any ideas? Much appreciated.

Have you verified that the times are all correct on the devices?
I had an AP issue with time+certificates and even though all my controllers were set to sync to the same ntp server, the times were off. I manually set the times and that fixed it.

WCS & 2710 Location Appliance

I am running version 7.0.164.0 on my WCS and have a 2700 and a 2710 Location Appliance both running version 6.0.102.0. I used to be able track clients on the WCS maps but now I am not able to. No clients show up on the maps anymore, just the APs and their heat maps. I'm not sure when this started but I am guessing there is a compatability issue between the two. Can anyone verify this?

I am running the same versions and able to track clients. You might need to
click on the ">" to pull up the filter for the client view and check the show all clients checkbox

Cisco 2700 Location Appliance

Deployed and setup for the first time. (4404,2700 and WCS). All the device are communicating to each other.Snmp v1/2 setup at the Controller pointing to WCS. The time of the devices are the same with ntp setup. All with the latest version Software. My problem is I can't see the clients from the Location Appliance. It won't show in the Map.
An assistant is greatly appreciated.

Yes I did. After a few days posting my problem to the forum, I decided to open a tac case to cisco. They asked me to send some snapshots of the setting of my Location Appliance. Before I could reply with the settings there requesting, I able to resolve the issues. I was reading of how the Controller and Location Appliance communicate. Not only that time is very important for all Unified devices have to be syncronize, It was also the SNMP V3 needs to be properly configured or the SNMP v1/2 have to be set to 0.0.0.0 When I set my snmp ip to 0.0.0.0 then everything worked. Anyhow, thank you for the responce.

Location Appliance ...Getting started...

After the initial setup..I can ping the appliance but cannot access it through http or https. Even tried port 8001. WCS also cannot add the appliance. What else has to be done?

I have come across the same issue myself however, I can go through the configuration process no problem. I have 3 Cisco 2710 Location Appliances all running version 3.0 code. I got one to work no problem. I configured it, it reset, then I could connect it with WCS. Beautiful. However, the other two WILL NOT work for the life of me.
Basically, I get through the installation process and they reboot. I get back to the CLI after it reboots and log in. From there I do a "getserverinfo" and get the following message:
[root@LocationApp-Area4 root]# getserverinfo
com.aes.client.AesClientException: Request to server failed, reason: java.security.PrivilegedActionException: com.sun.xml.messaging.saaj.SOAPExceptionImpl: Message send failed
at com.aes.client.AesClientAdminImpl.getServerInfo(Unknown Source)
at com.aes.server.cli.CmdGetServerInfo.run(Unknown Source)
at com.aes.server.cli.CmdGetServerInfo.main(Unknown Source)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at com.zerog.lax.LAX.launch(DashoA8113)
at com.zerog.lax.LAX.main(DashoA8113)
Ok, great, i know this means that the Location Appliance is NOT running for whatever reason. So (and I have been looking at the configuration documents posted online) I tried the following command to start the location:
[root@LocationApp-Area3 root]# /etc/init.d/locserverd start
Starting locserverd: [ OK ]
[root@LocationApp-Area3 root]#
Ok, so it appears as if everything should be ok so I do another getserverinfo and get the same message again.
What do we need to do to get this running and what other trouble shooting methods are there so we can get this working?

Location appliance tracking limit??

Hello,
One question that I haven't found an answer for yet!
When the location appliance reaches the maximum number of tracking devices of 2500 what happens next???
It stops collecting information for new devices?
It deletes information for older devices hence allowing tracking of new devices?
Stops working all together??
It ??????
Thanks for any clarification.
Jorge.

Hi Jorge,
I am not sure if this would answer your query, but this is what I managed to find -
The location appliance can track up to 2,500 elements. You can track the following elements: client stations, active asset tags and rogue clients and access points.Updates on the locations of elements being tracked are provided to the location server from the Cisco wireless LAN controller.
Only those elements designated for tracking by the controller are viewable in Cisco WCS maps, queries and reports. No events and alarms are collected for non-tracked elements and they are not used in calculating the 2,500 element limit.
You can modify the following tracking parameters using Cisco WCS:
â¢Enable and disable which element locations (client stations, active asset tags; and rogue clients and access points) you actively track
â¢Set limits on how many of a specific element you want to track
You can set limits on how many of a specific element you wish to track. For example, given a limit of 2,500 trackable units, you could set a limit to track only 1,500 client stations. Once the tracking limit is met, the number of elements not being tracked is summarized on the Tracking Parameters page.
â¢Disable tracking and reporting of ad hoc rogue clients and access points
http://www.cisco.com/en/US/docs/wireless/location/2700/4.0/configuration/guide/lacg_ch4.html#wp998931
A major alert appears on the Advanced Parameter window if the tracked elements limit of 2,500 for the location server is reached.
http://www.cisco.com/en/US/docs/wireless/location/2700/4.0/configuration/guide/lacg_ch8.html#wp999251
In addition to this I found a resolved issue in release 3.0.37.0 -
CSCse76683-Previous to this release, once the 2,500 limit of supported elements for the location appliance was met, no new location calculations were reported for any element beyond the 2,500 limit. Location calculations were reported once an element within the recognized 2,500 elements aged out. This condition occurred even when polling was turned "off."
Symptom:
The location calculation is not happenning for some of the elements. There are ERROR events saying 'Location limit hit, can not add any more location elements'. Even if the polling is turned OFF for the type of element that are too many, the location is not calculated for new elements.
-> Sushil

Location appliance grup menu

Does someone know how to enable and disable the GRUB menu on Location appliance running vesion 6.0.101.0? I cannot see anywhere in docs how to disable it or enable it.

Hi,
Still got the issue. Someone must know what the issue is??
Cheers,
Matt

Location Appliance - Can't enable History Stats

Hi,
We've got WCS v4.2.62.11 and Location Appliance v4.0.32 running fine apart from enabling History Stats.
When I go into the "History Parameters" menu and tick enable button for Client Station history I get an error message from WCS:-
"Unable to save History Pararmeters. Reason: Wired Client history interval is less than 1 minute"
Any ideas what the solution is??
Thanks very much,
Matt.

Hi,
Still got the issue. Someone must know what the issue is??
Cheers,
Matt

How can use my Wireless Location Appliance to work with RF ID's?

How can use my Wireless Location Appliance to work with RF ID's for Asset Tagging.
It seems Smartcard used for ID cards have a small RF ID, can I use this for Asset Tagging?
Thanks in Advance

There are two kinds of RFID tags: Active tags, which have a battery or other internal power source, and passive tags, which have no power source and work by reflecting the energy from an RFID scanner (basically). At the energy levels and distances used for WiFi location detection, passive tags will not return a detectable signal.
Take a look at http://www.aeroscout.com/ for more info on WiFi RFID tagging.

Cisco Wireless Location Appliance

dear
i have WCS with 500 ap License
i need to have Cisco Wireless Location Appliance what lisens i need for 500 ap
please explain to me that

Hi Ahmed,
This is the upgrade License SKU for upgrading WCS to WCS Location;
WCS-LOC-UPG-K9
Supports deployment of Cisco WCS on a single server only.
For customers upgrading from their existing Cisco WCS base licenses to equivalent Cisco WCS location licenses running Cisco WCS Software Release 4.1 or later.
Available as Cisco WCS location in increments of 50, 100, or 500 lightweight access points.
Customers currently using this license with Cisco WCS Software Release 4.0 are encouraged to upgrade to Cisco WCS Software Release 4.1, but they are not required to do so.
Order the Correct Cisco WCS SKUs
The process to order Cisco WCS SKUs for WCS-STANDARD-K9, WCS-LOC-UPG-K9, WCS-WLSE-UPG-K9 and WCS-ENT-K9 is presented below. To request help with ordering, please contact Cisco Customer Service: http://www.cisco.com/go/customerservice.
1. Login to the Cisco Ordering Tool.
2. Enter the family SKU of WCS-STANDARD-K9 or WCS-LOC-UPG-K9 or WCS-WLSE-UPG-K9 or WCS-ENT-K9 into "Enter Product" in the Ordering Tool and then press "Enter."
3. The family SKU will display in the ordering area. (Figure 6).
4. Select the "Line" for the family SKU
5. Once you have been taken to the configuration screen, select one of these options from the left side (Figure 7):
For WCS-STANDARD-K9 select one of the sub-SKUs based on the following:
Base: WCS Standard AP Base Option
Location: WCS Standard AP Location Option
For WCS-WLSE-UPG-K9 select one of the sub-SKUs based on the following:
Base: WLSE to WCS AP Base Upgrade Option
Location: WLSE to WCS AP Location Upgrade Option
**For WCS-LOC-UPG-K9 select the sub-SKU:
**WCS AP Location Upgrade Option
For WCS-ENT-K9 select the sub-SKU:
WCS Enterprise AP Location Option
For the WCS-STANDARD-K9 or **WCS-LOC-UPG-K9 SKU families, customers are prompted to order the optional CD (WCS-CD-K9), for a nominal charge, during the ordering process. The WCS-CD-K9 contains one software image of Cisco WCS Software Release 4.1 on a CD for Windows and Linux. This CD is shipped by U.S. mail to the purchaser's address. The optional CD is not available for WCS-WLSE-UPG-K9 because this SKU family already ships in CD format.
6. The right side of the screen will display the licenses available (Figure 7). The price for each SKU is displayed in the Ordering Tool.
7. Each license is orderable in a quantity of one (1) for the quantity blocks specified. To add multiple quantities of license blocks, you must go back to the main screen and order additional family SKUs and then select the sub-SKU option and license quantity block required. Repeat this process as needed, until the correct quantity of license blocks for your sub-SKU have been ordered.
From this good doc;
http://www.cisco.com/en/US/products/ps6305/pro ducts_data_sheet0900aecd804b4646.html
Hope this helps!
Rob

WLC upgrade to 7.0.98.0, WCS & Location Appliance to upgrade - Building maps location

Hi,
We recently upgraded about 24 WLCs (4402s and 5508s) from 6.x to 7.0.98.0. In order to support these WLCs through WCS, we also need to upgrade the WCS to 7.0.164 which is currently running at 6.0.132.0 (Linux OS). Same is the case with Wireless Location Appliance 2700 to be upgraded as well. Wireless Management system has number of building maps with AP locations.
Prior to upgrade the WCS / Location appliance we need to take the backup of these building maps, already stored to export after the upgrade. Kindly let us know the directory where all these maps are being stored, as during upgrade we will loose all the stored data / maps.
Thanks for your kind assistance.
Regards.
Shuja

Hi Shuja:
Who says you're going to lose all your maps and stored data during a WCS upgrade? The installer for WCS 7.0.164.0 will see the 6.0.132.0 installation and upgrade it in place, modifying the existing data to work in the new 7.0 format. The installer for WCS 7.0.164.0 will even ask you if you want to make a backup of this data before the upgrade process even starts, although it would be a good idea to pull a backup of everything before you start. (One can never have too many backups, right?) The backup application in your existing install should be at /opt/WCS6.0.132.0/backup . Run that application and it will prompt you for a location to put the .nmsbackup file.
The .nmsbackup file that results from a WCS backup is what gives WCS its portability across platforms (physical/virtual) and operating systems (Windows/Linux). It's essentially the lifeboat of WCS, containing the database, the maps, the licenses and other supporting files.
Performing Maintenance Operations chapter of the WCS Configuration Guide:
http://tools.cisco.com/squish/08725
Sincerely,
Rollin Kibbe
Network Management Systems Team

Hi, 2nd trial on the CS6 Master Coll downloaded (to prev app location) no issues, but when I open an

Hi, 2nd trial on the CS6 Master Coll downloaded (to pref app location) no issues, but when I open a n appl I get 'Your Trial has Expired'. What should I do?

There is nothing you can do. You misunderstand how this works. Trials only run once and that is that. After you have exhausted your 30 days, there is no way to run a trial a second time on the same machine. You will have to buy the software if you want continue using it.
Mylenium

Location Appliance

Location 2700 - 3.1.42.0
WCS - 4.2.81.0
WLC - 4402 - 5.1.151.0
I recently added a 2nd controller into my wireless infrastructure and I cant seem to get the location device to locate clients. It works no problem with the 1st controller.
The time on the devices is good, they sync with no problem...just wont locate any clients in WCS with AP's connected to my new controller. I get the error There are no clients on this floor. Either you don't have any location server which locates clients or none of your location servers detected any clients on this floor error message is reported on the Wirless Control System (WCS)
I would really appreciate any suggestions. Thanks.

You are using incompatible version. Considering your controller version is 5.1.51.0, you should have the following versions on your WCS and the location appliance.
WCS - 5.1.64.0
Location - 5.1.30.0
Please upgrade to these versions and if you still cannot locate clients, we can troubleshoot further.
Pushkar

WLC, WCS. Location Appliance upgrade order

Folks -
I am about to upgrade my system from 4.1 code to 4.2 code. I am wondering if it's possible to have the WCS and 2700 Location Appliance upgraded to 4.2 d-cubed revs first while still running Concannon WLC code 4.1.185? I am hoping to be able to upgrade WCS/2700 several days before doing all of my controllers.
So in summary, will the following combo work? WCS-4.2.97, 2700-3.1.38.0, WLCs-4.1.185.

Hi Charles,
Yes, this would be the supported method :)
Upgrading to a New Software Release
The Cisco WCS release must be the same or more recent than the controller software release. **Upgrade the Cisco WCS first to prevent any unexpected problems. Cisco WCS supports database upgrades only from the following official Cisco WCS releases:
â¢4.0.66.0
â¢4.0.81.0
â¢4.0.87.0
â¢4.0.96.0
â¢4.0.97.0
â¢4.0.100.0
â¢4.1.83.0
â¢4.1.91.0
â¢4.2.62.0
â¢4.2.62.11
â¢4.2.81.0
Wireless LAN Controller Requirements
Cisco WCS 4.2.97.0 supports management of the following wireless LAN controllers:
â¢4.0.155
â¢4.0.179.8
â¢4.0.179.11
â¢4.0.206.0
â¢4.0.216.0
â¢4.1.171.0
â¢4.1.185.0
â¢4.2.61.0
â¢4.2.99.0
â¢4.2.112.0
â¢4.2.130.0
â¢4.2.172.0
http://www.cisco.com/en/US/docs/wireless/wcs/release/notes/WCS4_2MR2.html#wp69815
Hope this helps!
Rob

Location Appliance Issue

Similar Messages

Maybe you are looking for