Cloud Management and AIOps
This is an IBM Automation portal for Cloud Management, Technology Cost Management, Network Automation and AIOps products. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).
Shape the future of IBM!
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:
Search existing ideas
Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,
Post your ideas
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Specific links you will want to bookmark for future use
Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.
IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.
ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.
Hi Atif
thanks for your update.
I agree that the agent should not be regularly restarted, however, maintenance for OS, ESX, DC, network or ITM dictates that is it necessary in a real-world environment on a semi-regular basis. This maybe required 3-4 weeks.
Monitoring Best Practice suggest that unnecessary events should be suppressed as close to source as possible, in this case it should not be generated by the agent in the first place.
The TEP database connection status is always a "momentary determination", at the time the agent is scheduled to execute the processing, so a "momentary determination" at start-up is not different. However, currently the agent is reporting mis-leading information. It is reporting there is no connectivity when it has not even attempted a connection.
Such a TEP Server check at agent start-up may be superfluous from a functional perspective, but it is not superfluous from a usability perspective, the accuracy of the "TEPS Connectivity" attribute value and usefulness of that data.
If IBM are unable to initiate a start-up TEPS check to accurately report the connectivity status, then maybe the attribute value should be set to indicated it has not been attempted, for example an "Unknown" state? At least that would enable the situation to be engineered to prevent the false positive. The negative of that approach is that if maintenance did introduce issues (which ITM SPs often have) it will not be know until the next process schedule is execute, 2 am by default.
thanks
Nick
If the Tivoli admin isn't sure whether the KSY Agent can connect to the TEPS after its installation or reconfiguration, then run a curl (linux/unix) or wget(windows) command to test if the URL that is used to connect to the TEPS works.
The enhancement would be to initiate a connection to the TEPS when the Agent started. This is just a momentary determination if the TEPS is available at KSY startup. But, the KSY Agent by default connects to the TEPS at 2AM everyday. So unless someone plans to start and stop the KSY Agent often, which is contrary to IBM's Best Practices, the initial connection to the TEPS is superfluous.