Credential Affinity Cleanup best practice

[BK14]

Hello everyone,

I see many IPs in the Credential Affinity table that are related to "let's say" SNMP but when I search the devices in CMDB with those IPs from cred affinity table, I see that majority of them are not network devices. Perhaps one of the reason can be that IP service affinity is not active in our instance. We are activating that feature but wondering what is the best practice to:

1. Clean up the old incorrect data in Cred Affinity table

2. Removing duplicated IPs that are related to SNMPv2 and SNMPv3 and keep the newest one.

3. Removing the record in Cred Affinity when the device is retired

 I have more concerns and question in this area but leave it to these 3 questions for this post.

Any information and help will highly be appreciated.

Thank you all,

bk

[Rahul Priyadars · Accepted solution]

Have you checked in 'dscy_credentials_affinity' table ,because when First time  Discovery and Orchestration tries to access the device,they check the all credentials... until get valid credential..,when they find valid credential updates into 'dscy_credentials_affinity' table,and continues all the discovery with the information it gets from this table.

Again if credentials change or modified again same process will execute till get valid credential and update into same table.

So is Your Credentials Changed else continue 

1. Clean up the old incorrect data in Cred Affinity table-->Yes 

2. Removing duplicated IPs that are related to SNMPv2 and SNMPv3 and keep the newest one.--> If there are too many remove all and let discovery Auto Refresh It.

3. Removing the record in Cred Affinity when the device is retired ->YES You Can

How bid your discovery Scope is and How many Creds you have? There is just 1 time update effort by Discovery even if you completely Flush the Affinity Table and let it rebuild by Discovery.

Hope this Helps

Regards

RP

[BK14]

Hi Rahul and thank you for your comments.

I was hoping there would be a solution to clean it up and not to remove all affinities from the table. Our discovery scope is pretty big, about 10s of thousands of discoverable CIs. And MIDs cannot handle it. Some schedules fail in weekly basis. That's why I was trying to clean the table without removing all records so discovery will have less hard time to discover the CIs, even for one time.

But as you said I think it is the best to clean all records.

Regarding the CIs that are retired and the affinity records, is there a way we can automate that?

Thank you again,

bk

[BK14]

Thank you Rahul,

we roughly have about 30 credentials for different CI types. I can do as you advised for my first and second questions. thank you. My last question is not stated fully and can be confusing, sorry about that. What I really mean is to develop a rule to automatically remove the affinity record when a device is retired. So we don't need to go check and delete them manually. 

Do you know how I can achieve that?

Thank you Rahul.

bk