IBM Sterling Ideas
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:
Post your ideas
IBM is transforming its request for enhancement (RFE) process. The purpose of the transformation is to provide a more consistent experience for you to submit requests and to enable IBM product owners to respond to your requests more quickly. For more information click here.
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, 1. Post an idea 2. Upvote ideas that matter most to you 3. 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.
We often get Secure+ error messages (prefix CSPA) that don’t necessarily indicate a Secure+ issue. This makes it difficult to monitor for errors. The error messages that have caused us the most difficulty are:
We often see these error messages but they reflect a transient networking issue rather than an actual Secure+ error. That makes it difficult to alert on Secure+ issues because of the large number of false positives we would generate with a simple message alert.
If the SSL handshake fails because the remote side doesn’t respond or sends a TCP reset, we would like the error message to indicate that as opposed to the case where the SSL handshake fails because of a true SSL handshake failure. The former error is transient while the latter will require some change to the security configuration on either the remote or local node to correct the problem.
I’ve attached a document showing some examples of CSPA error messages followed by successful connections.
|What is your industry?||Financial Markets|
How will this idea be used?
If implemented, we will use this idea to improve the monitoring of remote nodes. Currently, we have a custom-built monitor running in CA's Netmaster product that checks connectivity to remote nodes by submitting a "heartbeat" process periodically and monitoring whether the connection succeeds. with accurate diagnostic messages we will more easily be able to alert our Operations team if there are Secure+ issues.
Do not place IBM confidential, company confidential, or personal information into any field.