IP Affinity Automatically Moved Between SNMP Credentials After Discovery

[deebika019]

I noticed that in DEV, a particular IP affinity IP is associated with the SNMP2 Device Credential, whereas in PROD the same IP affinity IP is now associated with a different SNMP Device Credential.

The IP affinity record appears to have been created automatically through Discovery. Could someone explain how an IP affinity entry can move from one credential to another automatically? Are there any Discovery processes, credential affinity rules, or updates that would cause this behavior?

Any insights would be appreciated. Thanks.

[Vishnu-K]

Hi @deebika019 ,

The reason could be that, during the discovery process, ServiceNow checks the credentials in the Discovery Credentials table one by one based on the Order field. So, in production, while the discovery is running, if another credential is tried first and successfully authenticates with the device, ServiceNow may create the Credential Affinity for that IP against that credential instead of the specific credential you're expecting.

Also, Credential Affinity doesn't necessarily have to be tied to only one credential permanently. If you deactivate the other credential and run the discovery again, the discovery will try the remaining active credentials. If the credential successfully satisfies the device, ServiceNow will create a new Credential Affinity record for that IP against that credential.

Hope this helps, if it helped you please do mark it as helpful and accept the solution

Thanks,

Vishnu 

[Pratiksha]

Vishnu is right, when you have two matching credentials based on order it will be tried, accordingly the affinity will be created. 

Regards, 

Pratiksha