300-430 Question 192
Select 3You are configuring a Cisco Wireless LAN Controller (WLC) and Cisco Identity Services Engine (ISE) to enable client profiling. The goal is to identify and classify wireless devices connecting to the network based on their operating system and device type. What steps must you take to ensure proper client profiling?
- A
Enable RADIUS accounting on the WLC to send device information to ISE.
- B
Enable DHCP Profiling and HTTP Profiling on the WLC.
- C
Manually assign endpoint profiles for all clients in ISE.
- D
Configure a RADIUS server on the WLC and point it to the ISE server.
- E
Enable SNMP traps on the WLC for device classification.
Show answer and explanation
Correct answers: A, B, D
Explanation
To configure client profiling, the WLC and ISE must work together to collect and analyze device information. Enabling RADIUS accounting ensures device data is sent to ISE. Configuring DHCP and HTTP profiling on the WLC allows for additional device attribute collection, which aids in profiling accuracy. Finally, the WLC must be configured with a RADIUS server pointing to ISE for communication. Manual profiling or SNMP traps are either impractical or not relevant in this context.
- A. Correct.
Correct. RADIUS accounting must be enabled on the WLC to send device-related information (such as MAC address, user ID, and session details) to ISE for profiling.
- B. Correct.
Correct. Enabling DHCP Profiling and HTTP Profiling on the WLC allows the system to collect additional attributes from client devices, such as hostname, OS, and browser information, which aids in accurate profiling.
- C. Incorrect.
Incorrect. While manual assignment is possible, it is not scalable or recommended in dynamic environments where many devices connect. Automated profiling methods (e.g., RADIUS, DHCP) are preferred.
- D. Correct.
Correct. Configuring the RADIUS server on the WLC to point to ISE is essential for proper communication and integration between the two systems for client profiling.
- E. Incorrect.
Incorrect. SNMP traps are used for monitoring and alerts but are not necessary for client profiling.