IBM Data and AI Ideas Portal for Customers
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
Post 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 product management 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 notification 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.
Additional Information
To view our roadmaps: http://ibm.biz/Data-and-AI-Roadmaps
Reminder: This is not the place to submit defects or support needs, please use normal support channel for these cases
IBM Employees:
The correct URL for entering your ideas is: https://hybridcloudunit-internal.ideas.aha.io
Documentation had been updated in Symphony 7.2 release to support the scenario.
Documentation will be updated in Knowledge Center.
Customer shared more information for this request, Support appends it here:
1) TCP supports auto-negotiation and packet fragmentation and re-assembly. This can be controlled by switches, but the usual error; you transmit at the wrong packet size because you don't catch the misconfiguration.
2) UPD COULD support something similar in the app (just like you support recovery), with the errno EMSGSIZE error. It can be pretty simple, done during socket accept and only basic support for MTU 9000 or 1500, or more sophisticated, where you hone in on the exact/optimal size. There are at least 4 sizes that might work. Complicating this, you COULD check for this error on every sendto(), but recovery gets really ugly then. And, since this would normally ONLY be done at socket setup, done once (on each side) and no performance impacts after for old users. (Send dummy packet of 65K, get EMSGSIZE error and retrieve IP_MTU and use this number for the specific server going forward).
3) For multi-homed environments (basically a network for public and network for grid), which we always set up, static routes don't work. They used to… The latest technique is to include the “Source IP” in the socket connection (the local IP), and that forces the algorithms to select that IP for the traffic, unless down.
4) All this available in both C and Java (not sure what Symphony was developed in.
Some useful links:
C to get MTU size and test connectivity (local MTU): http://www.tenouk.com/Module43a.html
GREAT description of Linux IP_MTU and IP_MTUDISCOVERY in Linux http://man7.org/linux/man-pages/man7/ip.7.html
Linux IP_MTU description. http://www.skrenta.com/rt/man/udp.4.html
Windows SO_MAX_MSG_SIZE option (they never do it the same): https://msdn.microsoft.com/en-us/library/windows/desktop/ms738544(v=vs.85).aspx
Java to get interface info (including MTU, but suspect defined not open socket): http://www.java-tips.org/java-se-tips-100019/31-java-net/1767-programmatic-access-to-network-parameters.html