Cisco Cisco Identity Services Engine Software Manual Técnico

Contents

Introduction

Prerequisites

Requirements

Components Used

Configure

Step 1. Standard AAA configuration

Step 2. Configure Device Sensor

Step 3. Configure profiling on ISE

Verify

Troubleshoot

Step 1. Verify information collected by CDP/LLDP

Step 2. Check Device Sensor cache

Step 3. Check if attributes are present in Radius Accounting

Step 4. Verify profiler debugs on ISE

Related Information

Related Cisco Support Community Discussions

Introduction

This document describes how to configure Device Sensor, so that it can be used for profiling
purposes on ISE. Device sensor is a feature of access devices. It allows to collect information
about connected endpoints. Mostly, information collected by Device Sensor can come from the
following protocols:

Cisco Discovery Protocol (CDP)

●

Link Layer Discovery Protocol (LLDP)

●

Dynamic Host Configuration Protocol (DHCP)

●

On some platforms it is possible to use also H323, SIP (Session Initiation Protocol),
MDNS (Multicast Domain Resolution) or HTTP protocols. Configuration possibilities
for device sensor capabilities can vary from protocol to protocol. As an example
above is available on Cisco Catalyst 3850 with software 03.07.02.E.

Once the information is collected, it can be encapsulated in radius accounting and send to a
profiling server. In this article Identity Service Engine (ISE) is used as a profiling server.

Prerequisites

Requirements

Cisco recommends that you have knowledge of these topics:

Radius protocol

●