Hello. In this video, we will look at profiler feed reports.

We'll start off by

reviewing reports that are based on profiling data that was gathered in previous
labs.
Our first step in doing so is to navigate to Work Centers, Profiler, and then
Feeds. We'll scroll to the bottom of the Profiler Feed Service Configuration page,
where we can see information about the latest profiler feed update. Here, we'll
first verify that there is a time stamp showing when the latest applied feed
occurred.
If you are not able to see a time stamp in your own lab, you may need to verify and
troubleshoot why the Cisco Profile Feed Service is not working for your lab. There
is a button here that allows me to undo the latest changes that were made based on
the feed shown by the time stamp, but I'm more interested in the link below the
button that says Go To Update Report Page. I'll click on that link and a new tab
opens in my browser.
On this new page, the Change Configuration Audit Report has shown, but it has been
filtered to show only the entries where the administrator of the change is the
Cisco Feed Service. Scrolling down the list of entries shows where the Feed Service
has changed existing profile configurations and also where the Feed Service has
added new profile configurations, both shown as the type of event. Under Objects,
you can see different types of endpoints and also some of the rules used when
profiling.
I'll scroll down the list of changes until I find an entry where the event type
shows as Added Configuration. Clicking on that event opens another tab with more
details about the entry. From the Details page, I can see the object type was an
Endpoint Policy and that the object in this case was workstations running the
Catalina Release of macOS.
Again, the event was that this configuration was added to my ISE system. A lot more
details are shown under Modified Properties. If I hover my mouse over the entry, I
can see the full details of the event. I'll close the Details tab for the Added
Configuration Event.
Next let's click to see the details of a Changed Configuration Event. Another tab
opens up with those details. In this case, the object type was a rule for an HP
Color LaserJet Multifunction printer. The server details remain the same and more
details show under the Modified Properties section. And again, hovering my mouse
over this item shows even more information about the changed configuration.
I'll close the two report tabs on my browser, and we'll now load the Opera Email
Client by clicking on its icon, which is located on the desktop of my admin PC. The
Opera Client shows that I have a number of emails related to the ISE Feed. The very
top message is not part of the plan lab, but I'll point it out.
This email indicates that the Automated Feed Service failed at 1:06 AM on Friday.
This is likely related to certificate issues between my ISE server and the Cisco
Feed Service. I'll try to resolve that issue later. We can, however, follow the lab
steps and view the emails that were received on Thursday, when the feed updated
successfully.
The top message from Thursday is the Feed OUI Applied Update email. If I click on
it, I can see that when the update occurred, 5374 OUIs were added and 766 OUIs were
updated. This large number shows because this is the very first time that the
update was run on my ISE system. The numbers of additions and updates shown on your
own system will probably be different.
The second email that we'll look at is the one titled Feed Policies Applied Update.
This email shows that Version 1, Version 2, and Version 3 policies were downloaded.
243 policies were identified to be applied, and 243 policies were applied to my
system. As with the OUI updates, the number that you see on your own system may be
different from what I show here.