Discovery not creating IP affinity records

[Praveen37]

Hi All

I am trying to perform discovery, even though with successful discovery, IP affinity record is not getting created. But while I am performing discovery using mid server IP, it creates record in IP affinity table. 

Also when I am trying to perform discovery by deactivating credentials in the credential table, discovery is successful means it is carried out using service credentials of mid server. 

Now we are using the same service credentials what we have created in snow table(credential is active), Discovery is successful and No IP affinity record is created.

According to the article: 

https://docs.servicenow.com/bundle/jakarta-servicenow-platform/page/product/discovery/task/t_ConfigMIDUseCredFmCredTable.html

Service now credentials should be used first for performing discovery and then it will come to mid server service credential, So that way, it should create IP affinity record.

Now I don't understand what is the order of using service credentials and snow table credential.

Please help on this. 

[tim_broberg]

I'm not entirely certain I understand the question. Apologies if I'm answering the wrong thing, and please correct me if I'm missing the point.

You can see the affinities by typing dscy_credentials_affinity.list in the filter box on the upper left corner.

You should see one record for each pair of mid server and ip with a field for the sys_id of the credential that most recently worked for that mid on that IP.

When an ecc_queue output record gets created to launch a probe, after the mid is assigned, a business rule searches the credential affinity table for the source IP and the mid, and shoves the resultant sys_id, if any, in the credential_id parameter of the mid.

When the mid server marshalls his set of credentials to try when running the probe, he starts with the one in credential_id and goes on from there according to the order field.

When one of the credentials works, he reports it back to the instance to update the affinity. (This does not happen on the test credential action on the credential form.)

I'm not sure what you mean by a "mid server service credential." Can you explain that?

    - Tim.

[Praveen37]

Hi Tim

Thanks for your reply.

What I am saying is, If discovery is successful, it should create the affinity But it is not doing the same.

Although it is creating affinity, when I am trying to discover Mid server host IP, But not for the other IPs which is discovered successfully.

Mid server service credential are those which we define on the Mid server host machine service.

Regards

[tim_broberg]

So, what are you discovering when it fails to create the affinity?

[Dave Ainsworth]

Hi Praveen,

I think it is using the MID server service credential for all discoveries except the MID server host itself. As you mention, this is a fallback and it will try the credentials in the credentials table first but these are possibly failing (except when discovering the MID server host).

There are a couple of things you can try:

1. For credentials in the credentials table, try "Test Credential" against hosts where you expect them to work but where no affinity is being created. If the test fails, there is something wrong with the credential definition or that credential does not have access to the host.

2. Set the following configuration parameter on the MID Server to "false":

"mid.powershell.local_mid_service_credential_fallback"

This will prevent the MID Server service credential being used. Run the discovery again and see if discovery is successful. 

Regards,

Dave