IBM Z Hardware and Operating Systems Ideas Portal
This is the public portal for all IBM Z Hardware and Operating System related offerings. 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.
This item is not in our plans but is being kept in our backlog.
If understand your use case correctly, you're using PBR to direct return traffic from target servers through the distributor stack so that the stateful firewall in front of the distributor sees flows in both directions for the connections, is that correct? With 10 members in the sysplex it seems like that solution would be a large burden on the distributor node. Have you considered moving the firewalls out in front of the sysplex to prevent this problem? Or connecting the firewalls so they can share state? These are the solutions most of our customers use for this problem.
Also a question, why are more than 8 tables needed since you're directing back to the distributor, you have 10 members in the plex but are all of them possible distributor locations? Since the first table in the list that contains a route to the destination is used, can you give some more detail on how this solution works? Trying to better understand the use case.