- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - Linux
- >
- RTLS setup with controller
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-21-2024 11:08 PM - last edited on 01-23-2024 10:18 PM by support_s
01-21-2024 11:08 PM - last edited on 01-23-2024 10:18 PM by support_s
RTLS setup with controller
Setup:
RTLS service running on LInux server
Standalone-standby setup with 7210 controllers
225 AP model
Configuration fro rtls on ap system profile:
rtls-server ip-or-dns "10.229.26.148" port 8816 key 84ccc7538308e0c4cdecb673e6fea298 station-message-frequency 30 include-unassoc-sta enable
Issue:
The data seen on server is not clear as we are getting more than 1 response from one ap same user at same time frame
AP mac, client mac, time, rssi, ttl,value
94:B4:0F:C7:7F:44,08:5B:D6:FF:54:42,1705387469420,-85,334,true,1
94:B4:0F:C7:7F:44,08:5B:D6:FF:54:42,1705387469420,-74,9,false,1
94:B4:0F:C7:7F:44,08:5B:D6:FF:54:42,1705387469420,-74,9,false,1
Took uplink captures but that was encrypted so unable to check what details have been shared. Need help to understand how the data will be send of to server
- Will it send associated clients list first or unassociated list?
- Why do we see duplicate entries for same user
- Why do we see more than one reply for same user
- Tags:
- Operating System
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-23-2024 10:09 PM
01-23-2024 10:09 PM
Re: RTLS setup with controller
Good day!
It looks like you're dealing with a Real-Time Location Services (RTLS) setup using 7210 controllers and 225 AP models, with the RTLS service running on a Linux server. The issue you're facing involves unclear data on the server, specifically multiple responses from one AP for the same user at the same time frame.
Here are some points to consider
1. Data Sent to the Server
>> The APs typically send data to the RTLS server about associated and unassociated clients.
>> The information usually includes details such as AP MAC, client MAC, time, RSSI (Received Signal Strength Indicator), TTL (Time to Live), and other relevant values.
2. Duplicate Entries
>> Duplicate entries for the same user could be caused by multiple APs detecting the same client simultaneously.
>> It's essential to ensure that the RTLS configuration on each AP is correct and consistent.
3. Data Transmission Order
>> The order in which APs send data about associated and unassociated clients may vary based on the implementation.
>> Associated clients are typically reported more frequently as they are actively connected to the AP.
4. Possible Causes for Multiple Replies
>> APs might be reporting data at different intervals, leading to multiple entries for the same client in a short time frame.
>> Interference or overlapping coverage areas between APs could also contribute to receiving multiple responses for the same user.
5. Uplink Captures
>> If the uplink captures are encrypted, it might be challenging to inspect the details.
>> Ensure that the encryption keys and configurations are correctly set up to decrypt and analyze the captured data.
6. Troubleshooting Steps
>> Verify the RTLS configuration on each AP, ensuring consistency in settings.
>> Check for interference or overlapping coverage areas that might cause multiple APs to detect the same client.
>> Review logs on both the APs and the RTLS server for any errors or unusual behavior.
>>Confirm that the RTLS server is properly configured to handle and process the incoming data.
7. Refer to the documentation of the RTLS solution, AP models, and controllers for any specific considerations or troubleshooting steps.
For a more detailed analysis and resolution, it may be beneficial to consult the documentation of the RTLS solution, contact the vendor's support.
Hope this gives some insights! Let me know...