If you hover your cursor on words " Credentails Used" You will see tool tip saying Credentials showing is for UI only.
If you do the exact same for the devices/hosts that are successfully discovered you will see both the last credentials used and sysObjectID.
I am aware of the UI only "Credential Used" however I am navigating to the Device Info via query constructor which has the attribute last_credential which is expected to fetch the credential info.
Please hover your cursor on words "Last Credential ID" on the Discovery Access > Device Info page.
If you just need list of credential used for DA whose end state is UnsupportedDevice how about looking at Session results?
From DA go to #DiscoveryAccess:Metadata:Detail:SessionResult ?
The idea is to collate all the sysObjectID's that have been obtained using the defined credentials, even though the device is currently unsupported.
Neither the credentials shows up nor the sysObjectID, even though both of them can be seen under the device info.
Your search is a little strange.
- there is no point in having flags(include_destroyed) as DDD does not record destroyed nodes,
- for some reason you are traversing to the next DiscoveryAccess to get the credential rather than using the DiscoveryAccess associated with the DiscoveryRun.
I am just adding to the OOTB query that is seen when clicked at the Skipped/ Unsupported devices.
The purpose is to narrow down on the sysObjectID based on the credentials that are used.
As a matter of fact 6 of the IP's from the same list does show the credential used, where do they come from then?
In simple words, "How do I see the sysObjectID's/credential used of the IP's/devices that are classified as Result=Skipped with End State=Unsupported" for a "particular" scan run".
In my case for the 805 Skipped IP's under summary.
Something like this?
WHERE result = "Skipped"
AND end_state = "UnsupportedDevice"
SHOW endpoint, device_summary,
Diwakar - Please note in Andrew's query <id> is nothing but node id of your DiscoveryRun. You can get that from URL of DiscoveryRun
Thanks a lot Andrew and Saurabh. This worked absolutely fine. Thanks once again.