We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:
Post your ideas
Start by posting ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,
Post an idea
Upvote ideas that matter most to you
Get feedback from the IBM team to refine your idea
Help IBM prioritize your ideas and requests
The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The offering manager team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.
Receive notifications on the decision
Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.
Please use the following category to raise ideas for these offerings for all environments (traditional on-premises, containers, cloud):
Cloud Pak for Multicloud Management
Cloud Pak for Network Automation - incl Orchestration and Performance Management
Cloud Pak for Watson AIOps - incl Netcool Operations Management portfolio
Edge Application Manager
IBM Observability with Instana
ITM-APM Products - incl IBM Tivoli Monitoring v6 and Application Performance Monitoring v8
Workload Automation - incl Workload Scheduler
Tivoli System Automation - inc Tivoli System Automation Application Manager (SA AM), Tivoli System Automation for Multiplatforms (SA MP)
Process to clean up old entities from active devices
Once a device is discovered bu ITNM, it creates many entities in NCIM database, representing the device, interfaces etc.
If any of those entities are not valid anymore (e.g., one of the interfaces is disabled), it is not deleted from the database.
It makes sense to keep the interface on the database for some time, to easily recover in case there was an error); however, over time this can cause to an accumulation of entities on the database and the increase of database size.
Also, and this is the case we have attached to this RFE, if an entity is wrongly created, it is impossible to have it removed, unless we delete the entire device and have it rediscovered, which is not desired.
I suggest two possible solutions:
1. Configurable maximum age
Having a property setting to the domain, that once an entity (and not a device) has not been discovered for more than X days/months/years, it will be removed from the database.
This is a nice way to keep the entire system clean, but may be too generic, and that's why I suggest also a second solution below.
2. Script for specific cases
A script similar to RemoveNode.pl script, but instead of removing the entire node, it wil only remove the entities of that node that has not been discovered in the last X days/months/years. This solution should handle single IP/hostnames or files with IP/hostnames, just like RemoveNode.pl script.
Do not place IBM confidential, company confidential, or personal information into any field.