cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1017
Views
5
Helpful
0
Replies

Problem: Updating custom attributes of endpoints in pxGrid context-in

Yakirke
Level 1
Level 1

Hi,

We would like to update existing endpoints in ISE with custom attributes through pxGrid context-in. We tried sending endpoints data to com.cisco.endpoint.asset expecting all attributes to be updated for those endpoints. There seems to be an issue where custom attributes do not get updated while non-custom attributes do.

Following a similar issue posted here, we noticed that the device is updated with the correct attribute value only after changing a Profiling Policy that uses the same custom attribute.
Sending another attribute change after will not take effect until the next modification of such policy.

Example to an endpoint update could be:

{ "opType": "UPDATE", 
"asset": { "assetName": "My iPhone",
"assetMacAddress": "38:F9:D3:42:91:11",
"assetIpAddress": "192.168.10.5",
"assetCustomAttributes": [{"value": "Apple", "key": "Manufacturer"}] }
}

More info:

  1. This issue is consistent with both CREATE and UPDATE opType.
  2. IP is always specified for the endpoint as suggested on the found post.
  3. Profiling Setting is configured with: Enable Custom Attribute for Profiling – ON, EndPoint Attribute Filter – OFF.
  4. This issue was noticed on both 2.4 and 2.6 ISE versions.

This appears to be a bug in ISE getting out of sync with its own data.

I would really appreciate any idea on how to work around it.

Thanks,

Yakir

 

0 Replies 0
Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: