|
The issue typically occurs when users use the AeroScout engine to generate tag information. Real-Time Location Systems (RTLS) leverage Wi-Fi networks, Active RFID, sensors, and telemetry to track the real-time location and status of valuable assets. AeroScout, specifically, uses Wi-Fi networks to accurately track assets such as equipment and personnel.
The tag protocol operates between access points (APs) and the AeroScout engine. Fortinet's implementation of AeroScout supports tag messages transmitted in either IBSS (default) or WDS frame formats. However, Fortinet APs only receive and process tag frames in IBSS format.
Important Configuration Requirements.
To ensure proper functionality, the following configuration settings must be applied:
- Both the AeroScout engine and the FortiAP should be provisioned within the same VLAN.
- FortiAP should be on the latest recommended version
- Ensure that the Third radio is in the dedicated monitor radio.
- WTP Profile Settings:
- Enable ddscan.
- Enable Sensor Mode Scan.
Radio config:
config radio-3
set mode monitor
set wids-profile "wids profile name"
WIDS profile configure:
config wireless-controller wids-profile
edit "wids profile name"
set sensor-mode both
set ap-scan enable
next
end
Follow these steps to troubleshoot the issue:
Ensure all the points mentioned in the Important Configuration section are properly configured.
Use the following command on the FortiAP to verify the third radio configuration:
cw_diag -c radio-cfg
Check if FortiAP Can Detect Tags. To verify if the AP can detect the AeroScout tag, use the following command:
cw_diag -c aero-tag
If no tags are detected, proceed with the following troubleshooting steps:
On Aeroscout engine settings(can involve the concerned team to verify the following):
- FortiAP supports IBSS mode make sure that mode is selected under tag configuration.
- Configure tag to send packets in multiple channels
- Make sure the tag is configured to send the packet after a short time interval to send a packet (for example: 5 seconds).
Verify Allowed Channels in the WIDS Profile.
If the issue persists, check the allowed channels configured under the WIDS profile.
Example:
config wireless-controller wids-profile
edit "<wids profile name>"
show full
For more efficient scanning, restrict the allowed channels to only those on which the tags are operating.
Example Channel Configuration:
config wireless-controller wids-profile
edit "<wids profile name>"
set ap-scan-channel-list-2G-5G "1" "6" "11"
next
end
After verifying and adjusting the above settings, restart the tags and check if they are detected by the FortiAP.
Collect an OTA (Over-The-Air) capture on any of the allowed channels to check if the packets are being transmitted properly by the tags. This will help confirm whether the tags are sending data correctly.
|
