About Prashanth Kuma4

Prashanth Kuma4 · 02-17-2022

Can you check ECC Queue output status. If it is ready, MID server didn't pick the output. It can happen if the MID server is in hung state or there are lots of records in queue which are in ready state. Restart the MID service and try. If it still do...

Prashanth Kuma4 · 01-12-2021

Did you try to telnet from MID server to Target IP on the port 22/135/161

Prashanth Kuma4 · 10-20-2020

Hi Peter, You have to configure Health Inclusion Rules in CI class manager to exclude CIs with status retired. For more info on CMDB Health configuration, visit below link. https://docs.servicenow.com/bundle/paris-servicenow-platform/page/product/co...

Prashanth Kuma4 · 10-10-2020

Hi Vinil, Rubrik discovery is in ServiceNow roadmap. Pattern development team is working on Rubrik discovery. I think it will be available in few months. Regards,Prashanth Kumar

Prashanth Kuma4 · 10-04-2020

Hi, This error will be shown when the your instance is upgraded and not matching the MID server version. Ideally the MID server should auto upgrade. But in your case it didn't.To fix this, open MID server record in your instance and manually click on...

User Activity

Re: Cloud AWS Discovery is not completing

Re: External Credential test fails: Invalid Target Specified

Re: How to reduce stale CI count

Re: Anybody been able to discover Rubrik node and Rubrick Cluster?

Re: The Mid Server did not upgrade Error " reported mid server version 'newyork-06-26-2019__patch9a-06-24-2020_08-10-2020_1624' is not compatible with instance version 'paris-06-24-2020__patch1-hotfix3-09-23-2020_09-24-2020_1618'.