09-02-2020 05:40 AM
Solved! Go to Solution.
10-27-2020 04:34 PM - edited 10-28-2020 07:17 AM
It is not an issue with the Endpoint Attribute Filter which is basically limited to non-essential attributes and would not apply to custom attributes. To ensure custom attributes are available for profiling, you need to first go to Administration > System > Settings > Profiling and enable the option "Enable Custom Attribute for Profiling Enforcement."
There is another caveat that is not well documented which has the following requirement: In order to update custom attributes for a device using pxGrid Context-In, you must have
These requirements must be met even if you don't want to modify the endpoint's profile policy and just want to leverage pxGrid for learning new attributes unrelated to profile policy assignment.
A couple bugids have resulted from these caveats including:
I recommend working with your Cisco account team to help prioritize resolution to these issues.
09-09-2020 08:21 AM
Can you provide examples of what is being used?
Are you trying the context-in use case? https://developer.cisco.com/docs/pxgrid/#!pxgrid-context-in
Make sure you call with macaddress and ipaddress
Please find the below expected response content [Working].
{"asset":{"assetMacAddress":"44:39:C4:51:00:37","assetIpAddress":"10:10:10:10","assetCustomAttributes":[{"key":"YourAttribute","value":"1"}]},"opType":"UPDATE"}
What they are sending now from customer setup[Non-Working].
{"asset":{"assetMacAddress":"44:39:C4:51:00:37","assetCustomAttributes":[{"key":"YourAttribute","value":"1"}]},"opType":"UPDATE"}
Modify the script to add IP address along with the mac address, then ISE will profile the custom attributes
09-10-2020 08:00 AM
Thank you for your answer, Jason.
What I am trying to accomplish is using the endpoint custom attributes feature to enrich existing endpoints with additional data. I've set up custom attributes as described in the context-in use case documentation you've linked to.
The request I am sending matches the working content example you've provided, including the IP address. If the endpoint doesn't already exist prior to me sending this request, ISE will create a new endpoint and also successfully profile the custom attributes. However, when I execute the same request for an already existing endpoint, the custom attributes aren't being profiled. All else is - for example, if I supply a new assetSerialNumber, it will be updated successfully.
Is there anything else I can try?
Thanks.
09-15-2020 12:51 PM - edited 09-15-2020 01:50 PM
Hi,
I'm having the same issue in version 2.6 using the Context-In use-case. For endpoints that are already active in the system I cannot update any custom attribute but I can update normal attributes (AssetName, AssetHwRevision, etc).
If I remove the endpoint and add it back in through pxGrid I'm able to set the custom attribute, but once it's set, I'm not able to modify it it via pxGrid.
Every time I try to update an existing endpoint's custom attribute this shows up in profiler.log for the MAC/IP pair I'm trying to update:
2020-09-15 14:46:13,208 INFO [Grizzly(2)][] cisco.profiler.infrastructure.probemgr.Forwarder -::- Forwarder Mac 3A:A7:75:E4:A6:CD MessageCode null epSource PXGRIDPROBE
2020-09-15 14:46:18,208 INFO [Grizzly(1)][] cisco.profiler.infrastructure.probemgr.Forwarder -::- Forwarder Mac 3A:A7:75:E4:A6:CD MessageCode null epSource PXGRIDPROBE
2020-09-15 14:59:24,718 INFO [Grizzly(1)][] cisco.profiler.infrastructure.probemgr.Forwarder -::- Forwarder Mac 3A:A7:75:E4:A6:CD MessageCode null epSource PXGRIDPROBE
2020-09-15 15:03:15,017 INFO [Grizzly(1)][] cisco.profiler.infrastructure.probemgr.Forwarder -::- Forwarder Mac 3A:A7:75:E4:A6:CD MessageCode null epSource PXGRIDPROBE
2020-09-15 15:10:05,352 INFO [Grizzly(1)][] cisco.profiler.infrastructure.probemgr.Forwarder -::- Forwarder Mac 3A:A7:75:E4:A6:CD MessageCode null epSource PXGRIDPROBE
2020-09-15 15:10:10,345 INFO [Grizzly(2)][] cisco.profiler.infrastructure.probemgr.Forwarder -::- Forwarder Mac 3A:A7:75:E4:A6:CD MessageCode null epSource PXGRIDPROBE
Is this expected behavior, permissions issue, something else?
Thank you!
09-20-2020 07:49 AM
Check if Endpoint attribute Filter setting is enabled under Profiling settings.
ISE gets many attributes for an endpoint but filters them to consume the selected one's.
10-27-2020 04:34 PM - edited 10-28-2020 07:17 AM
It is not an issue with the Endpoint Attribute Filter which is basically limited to non-essential attributes and would not apply to custom attributes. To ensure custom attributes are available for profiling, you need to first go to Administration > System > Settings > Profiling and enable the option "Enable Custom Attribute for Profiling Enforcement."
There is another caveat that is not well documented which has the following requirement: In order to update custom attributes for a device using pxGrid Context-In, you must have
These requirements must be met even if you don't want to modify the endpoint's profile policy and just want to leverage pxGrid for learning new attributes unrelated to profile policy assignment.
A couple bugids have resulted from these caveats including:
I recommend working with your Cisco account team to help prioritize resolution to these issues.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide