Cisco ISE Discovery

AbdulBadi
Tera Contributor

Hi Community,

I am working on discovering Cisco ISE virtual appliances hosted on VMware.

VMware Discovery can identify the virtual machines and their hosting infrastructure, but I also need to classify the Cisco ISE appliances properly in the CMDB. I could not find a clear Cisco ISE-specific Discovery pattern or dedicated CI class in our installed content.

Has anyone implemented Cisco ISE Discovery successfully? I would appreciate guidance on:

  • The recommended Discovery protocol, such as SNMP, SSH, or REST API
  • The appropriate CMDB class for a Cisco ISE virtual appliance
  • Whether an out-of-box classifier or pattern is available
  • How the appliance CI should be related to the existing VMware VM CI
  • How to avoid duplicate CIs or reclassification issues

Even a brief overview of the protocol, CI class, identification method, and relationship design would be very helpful.

Thank you.

1 REPLY 1

kmohammed
Tera Guru

Hi AbdulBadi,

 

Short version first: there is no out-of-box Cisco ISE classifier or pattern in Discovery. ISE is handled as an SNMP-discovered network appliance with a small custom classifier/pattern extension. Point by point:

 

Protocol - use SNMP.

- SNMP (v3 preferred, v2c works) is the right protocol for the appliance itself. Enable SNMP in ISE first (Administration > System > Settings > SNMP on each node) and allow the MID Server IPs - ISE does not answer SNMP until it is switched on, and without it Discovery stops at an active, could-not-classify result.

- Do not rely on SSH. ISE runs the Cisco ADE-OS restricted CLI, not a general-purpose Linux shell, so the out-of-box Linux/Unix patterns cannot collect what they need and produce inconsistent results.

- The ISE REST APIs (ERS / Open API) are the wrong layer for this: they return endpoints, SGTs and policy data, not appliance inventory. Useful for enrichment later, not for discovering the nodes.

 

Class - Network Gear, extended if you need it.

- Let the appliance land in Network Gear (cmdb_ci_netgear). If you need ISE-specific attributes or reporting, create a custom class extending Network Gear (for example, a Cisco ISE appliance class) instead of a free-standing table - you inherit the network-gear identification rules, and you set the model once (manufacturer Cisco, model Cisco Identity Services Engine).

 

Classifier/pattern - this is the custom piece.

- Create a custom SNMP classifier keyed on the sysObjectID the ISE nodes return in the SNMP classification probe, with higher precedence than the generic Cisco classifiers, and point it at a copy/extension of the standard network-gear pattern that sets class, model ID and serial number (from ENTITY-MIB) deterministically. Having exactly one classifier match is what prevents reclassification flip-flopping between runs.

 

Relationship to the VMware CI, and duplicates.

- Keep two records at two different layers and relate them, do not merge them: the appliance CI from IP/SNMP discovery, and the VMware Virtual Machine Instance (cmdb_ci_vmware_instance) from vCenter discovery. Link them with the Virtualized by relationship (appliance CI > Virtualized by > VMware VM instance; the VM instance virtualizes the appliance). Do not let vCenter discovery create a separate computer CI for the guest.

- Duplicates in this design come from port scanning, not from vCenter: if the same ISE IP also triggers SSH/Unix classification you can get an extra computer-class CI alongside the appliance CI. Prevent that with a dedicated Discovery behavior / IP range for the ISE nodes that runs SNMP classification only, and with the classifier precedence above. The appliance CI and the VM instance live in different classes with different identifiers (serial number vs. VMware instance UUID), so IRE will not collapse them into each other once the relationship is in place.

 

Regards,

Karimuddin