Hello.

In this video, we will walk through verifying the profiling configuration on

our pod's virtual Wireless LAN Controller and 3K access switch.
We'll start by opening a new browser tab and then going to the web console of the
Wireless LAN Controller. I already have a bookmark on my browser that I can click
on to go to that URL. I'll log in to the Wireless LAN Controller with the correct
credentials that I've already saved on my PC. Once I'm logged in and on the web
interface, I'll navigate to the wireless LAN, or WLANs section, by clicking that
tab at the top of the page and then clicking the WLANs navigation link on the left
side of the new page that shows.
I'll click on WLAN ID 1 to view the settings for that WLAN, which is the wpa2e WLAN
for my pod. Next, I'll click on the Advanced tab to see those configuration
settings for WLAN 1. Then, I'll scroll down to about halfway down the page until I
see the settings for Local Client Profiling. Here, I can see that DHCP Profiling
and HTTP Profiling are both selected. If I had needed to enable one or both of
these settings, I'd need to click on Apply to apply the new configuration. But
clicking on Apply will also ensure that those settings are applied regardless.
I'll click on OK to close the warning message about changes affecting the WLAN.
I've verified the settings for the clients on that wireless LAN, so I'll now return
to the ISE console by clicking on that tab in my browser. Next, I'll open the
console connection to the 3K access switch. I'll log in to the switch with the
username of admin and the password of ISEisCOOL. Once I'm logged in I'll use the
en, or enable, command to enter privilege mode on the switch so that I can view the
configuration of the switch.
Now, I can use the show run command with the | symbol and then section snmp-server
to limit the output of the command to show only the section of the configuration
related to the SNMP server settings. From the output, I can see that the read-only,
or RO, community is set to ISEisCOOL, which matches the configuration in the ISE
Profiler settings.
We disabled SNMP MAC trap queries in the ISE server. The switch is showing that it
is set to generate MAC notification traps due to its use in another training lab.
This will not affect its interaction with ISE. I can also see that the SNMP server
is set to be the ISE server at 10.1.100.21, and that SNMP version 2c will be used
with that server.
After that, I can use the show run command with the | symbol and then section mac
to limit the output of my command to show only the section of the configuration
related to the MAC address notification settings. I see that the switch is
configured to notify the SNMP server about any MAC changes, which would include
when a MAC address is added or removed from the switches' address table, or also
when a MAC address moves from one switch port to another.
Show run interface vlan 10 shows me that VLAN 10 is configured with two IP helper
addresses. One is set to send DHCP probes and requests to the DHCP server in my
network, which is at 10.1.100.10. But the other helper address command sends those
same DHCP probes and request to the ISE server at 10.1.100.21 to help with
profiling the endpoints.
In the lab, VLAN 10 used as the regular access VLAN, and VLAN 50 is used for guest
access. So I'll repeat the show run command, but now for interface vlan 50, and can
see the same IP helper addresses configured on VLAN 50 as well.