nerdexam
Cisco

300-370 · Question #114

Cisco WCS v7.0 using a Cisco 3300 Series MSE can map and track wireless clients but is unable to track RSSI-based RFID tags. What is the most likely cause of this problem?

The correct answer is B. Tags are not compatible with Cisco Compatible Extensions. The inability of Cisco WCS v7.0 with a 3300 Series MSE to track RSSI-based RFID tags, despite tracking wireless clients, is most likely due to the RFID tags not being compatible with Cisco Compatible Extensions.

Troubleshooting Wireless Infrastructure

Question

Cisco WCS v7.0 using a Cisco 3300 Series MSE can map and track wireless clients but is unable to track RSSI-based RFID tags. What is the most likely cause of this problem?

Options

  • ATags are multicasting and not associating.
  • BTags are not compatible with Cisco Compatible Extensions.
  • CThe Cisco WLC RFID timeout needs a configuration change.
  • DThe Cisco WLC RFID tracking needs to be enabled.
  • ELicense is not installed on Cisco MSE.
  • FNMSP is incorrectly configured between Cisco WCS and Cisco MSE.

How the community answered

(64 responses)
  • A
    13% (8)
  • B
    78% (50)
  • C
    2% (1)
  • D
    5% (3)
  • E
    3% (2)

Why each option

The inability of Cisco WCS v7.0 with a 3300 Series MSE to track RSSI-based RFID tags, despite tracking wireless clients, is most likely due to the RFID tags not being compatible with Cisco Compatible Extensions.

ATags are multicasting and not associating.

RFID tags typically broadcast or beacon and do not associate like clients, nor does multicasting prevent RSSI-based tracking.

BTags are not compatible with Cisco Compatible Extensions.Correct

Cisco Compatible Extensions (CCX) certify wireless devices for advanced features and compatibility with Cisco infrastructure, including specialized location services for RFID tags. If RFID tags lack CCX compatibility, the MSE cannot properly process their proprietary or enhanced location data, preventing RSSI-based tracking while basic client tracking (which relies on standard 802.11 associations) still functions.

CThe Cisco WLC RFID timeout needs a configuration change.

A Cisco WLC RFID timeout configuration change would affect how long tags are tracked after their last signal, not the initial inability to track them at all.

DThe Cisco WLC RFID tracking needs to be enabled.

If Cisco WLC RFID tracking was completely disabled, no tags would be tracked; however, lack of CCX compatibility prevents proper processing even if tracking is enabled.

ELicense is not installed on Cisco MSE.

A missing license on the Cisco MSE would likely affect all location services, including wireless client tracking, which the question states is working.

FNMSP is incorrectly configured between Cisco WCS and Cisco MSE.

Incorrect NMSP configuration between Cisco WCS and Cisco MSE would generally disrupt all communication and thus all location services, including client tracking, which is functioning.

Concept tested: Cisco MSE RFID tag tracking requirements

Source: https://www.cisco.com/c/en/us/td/docs/wireless/mse/7-0/LBS_Dep_Guide/lbs_deploy_guide.html

Topics

#RFID tracking#MSE#WCS#compatibility#Cisco Compatible Extensions

Community Discussion

No community discussion yet for this question.

Full 300-370 Practice