This portal is to open public enhancement requests against products and services offered by the IBM Data & AI organization. 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 updateson them if they matter to you. If you can't find what you are looking for,
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
Specific links you will want to bookmark for future use
This happened between our egosh "client" on on-prem workstation and the cluster on AWS.
On-prem in our workstation we've setup a "egosh client" which basically is a collection of binaries and dependency of egosh.exe for the purpose of administration. It's not a Symphony client nor a Symphony host, just a collection of egosh commands and soam commands as well as commands/scripts we developed.
Everything has been working fine as always, until last week Xibei found that "egosh service list" executed from the on-prem workstation to our AWS cluster AWAPPRD0 failed to get the service output, instead it got "Cannot list services. EGOSC or VEMKD does not respond."
After days of investigation, we found it is related to CNAME of the master. The background is, the master setup on the AWS is named sgwpawgridmst01.grid-prod.aws.hedani.net and through AWS Route 53 we set a CNAME awapprd0mst0.grid-prod.aws.hedani.net for sgwpawgridmst01.grid-prod.aws.hedani.net. Then in ego.conf file on the on-prem workstation the EGO_MASTER_LIST is set to the CNAME before it was changed to sgwpawgridmst01.grid-prod.aws.hedani.net yesterday. After the change, "egosh service list" can get service output as expected.
We also figured out that if we want to keep the CNAME for EGO_MASTER_LIS, we need to add the short name(sgwpawgridmst01) and the IP into local ..\drivers\etc\hosts file.
We want to understand why CNAME does not work for "egosh service list", because as for other egosh commands like "resource list","consumer list" etc. and soam commands we've never had such issue. After all CNAME is necessary for users. Thanks.
Do not place IBM confidential, company confidential, or personal information into any field.