4-80
Cisco Wireless LAN Controller Configuration Guide
OL-17037-01
Chapter 4 Configuring Controller SettingsWireless Device Access
Configuring RFID Tag Tracking
Note Network Mobility Services Protocol (NMSP) runs on location appliance software release 3.0 or later. In
order for NMSP to function properly, the TCP port (16113) over which the controller and location
appliance communicate must be open (not blocked) on any firewall that exists between these two
devices. Refer to the Cisco Location Appliance Configuration Guide for additional information on
NMSP and RFID tags.
The Cisco-approved tags support these capabilities:
• Information notifications—Enable you to view vendor-specific and emergency information.
• Information polling—Enables you to monitor battery status and telemetry data. Many telemetry
data types provide support for sensory networks and a large range of applications for RFID tags.
• Measurement notifications—Enable you to deploy chokepoints at strategic points within your
buildings or campuses. Whenever an RFID tag moves to within a defined proximity of a chokepoint,
the tag begins transmitting packets that advertise its location in relation to the chokepoint.
The number of tags supported varies depending on controller platform. Table 4-4 lists the number of tags
supported per controller.
Table 4-3 Cisco Compatible Extensions for RFID Tags Summary
Partners AeroScout WhereNet Pango (InnerWireless)
Product Name T2 T3 Wheretag IV V3
Telemetry
Temperature X X X
Pressure
Humidity
Status
Fuel
Quantity
Distance
Motion Detection X X X
Number of Panic
Buttons
12 0 1
Tampering X X X
Battery Information X X X X
Multiple-Frequency Tags
1
XX X
1. For chokepoint systems, note that the tag can work only with chokepoints coming from the same vendor.
To Next Page
Loading...
Need help?
General
