To have a easy way to know which targets in scope were unreachable during the discovery

In our environment we usually run discoveries on big scopes. It could happen that some targets included in the scope were unreachable through ping. We are looking for a simple way to have a list of scoped targets, for each of them having the simple information if during the discovery it was possible to ping it or not.

After involving TADDM support on this request, we were informed that there is not any simple way for that. The information about ping failures is only traced in ping sensor log files, but anyway it is not possible to explore them in a simple way, considering that most discoveries include anchors and the ping logs are present both on TADDM DS and on any single anchor (eventually chained).

Idea priority	Urgent
RFE ID	100439
RFE URL	https://www.ibm.com/developerworks/rfe/execute?use_case=viewRfe&CR_ID=100439
RFE Product	Tivoli Application Dependency Discovery Mgmt (TADDM)

Post comment
Guest

Apr 16, 2019

Due to processing by IBM, this request was reassigned to have the following updated attributes:
Brand - Cloud
Product family - Operations Management
Product - Tivoli Application Dependency Discovery Mgmt (TADDM)

For recording keeping, the previous attributes were:
Brand - WebSphere
Product family - ITSM Operations
Product - Tivoli Application Dependency Discovery Mgmt (TADDM)
Guest

Feb 3, 2017

You could base a report on differences between on differences between BB_COMPUTERSYSTEM40_V and BB_OPERATINGSYSTEM62_V.

Whenever a Ping discovery is run, BB_COMPUTERSYSTER40_V receives an update when the DNS entry still exists, but as long as the OSSensor is not run, the lastmod date of BB_OPERATINGSYSTEM62_V is not updated.

We use this to identify login problems, but it could work for your purpose as well, assuming you're using L2 discovery. Good luck!

ps. I'm not an IBM employee or representative :)

The query:
select
A2.FQDN_C, A2.CONTEXTIP_C , A2.LASTMODIFIEDTIME_T as "SYSTEM MODIFIEDTIME", A1.LASTMODIFIEDTIME_T as "OS MODIFIEDTIME", A1.OSCONFIDENCE_C
from cmdb.bb_operatingsystem62_v A1
join cmdb.BB_COMPUTERSYSTEM40_V A2 on a1.PK_C = A2.PK__OSRUNNING_C
where
-- Time difference between system update and os update is more than 2 days:
(A2.LASTMODIFIEDTIME_C - A1.LASTMODIFIEDTIME_C) >= 2*3600*24*1000
and
A1.osconfidence_c = 100
and
-- where not interested in systems that haven't been seen at all for 21 days.
A2.LASTMODIFIEDTIME_C >= (((TRUNC(sys_extract_utc(SYSTIMESTAMP),'MI') - to_date('01-JAN-1970','DD-MON-YYYY')) * (86400) * (1000)) - (21*3600*24*1000))

By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.

Shape the future of IBM!

Search existing ideas

Post your ideas

Please use the following category to raise ideas for these offerings for all environments (traditional on-premises, containers, cloud):

Specific links you will want to bookmark for future use

To have a easy way to know which targets in scope were unreachable during the discovery

Please enter your email address

RELATED IDEAS

To have a easy way to know which targets in scope were unreachable during the discovery