Skip to Main Content
Cloud Platform

This is an IBM Automation portal for Cloud Platform 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 (

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
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.

Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal ( - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal ( - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM. - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Future consideration
Categories ClearCase
Created by Guest
Created on Jun 5, 2017

ClearCase MultiSite adminstration is required to work through a firewall and through a proxy

Multisite administration is required to work through a firewall and/or proxy

ClearCase MultiSite does today offer some support for lsepoch through a firewall,
but it does not offer support for lsepoch through a proxy. Required on this RFE is full support through a firewall, and include support through a proxy.

Given sites: "MAIN", "DR" and "SECURE".

Each site has 2 IP addresses for [each] VOB server host:
* the "vip" (presumably "virtual IP")
* the physical host, which would change in the event of a "failover"
And of course the replica host (seen in lsreplica) is the "vip"

Given: "albd_rt_params.conf" ( )

* MSADM_SVR_PORT - Designates a single port to be used by MultiSite request for mastership (reqmaster) from a remote replica.

It can be seen how this is used for "lsepoch -actual" and "chepoch -actual"
It can be set for a firewall be opened for requests to this port.
This port however is not a reserved port.

MultiSite normally assumes that it is open for request to that port on the server, from any requesting IP address, but security is only allowing requests to "open" ports only between specifically requested IP addresses pairs.

Given command "cleartool hostinfo", which sends a request to port 371, and gets its reply completely from albd_server (port 371). This showed that
* "cleartool hostinfo [physical host name]" DOES get the expected answer
* "cleartool hostinfo [vip name]" does NOT get the expected answer

lsepoch is going to
* send a request to vip:371
* expect a response from vip:371 informing it of the MSADM_SVR_PORT on the VOB server
* send a request to vip:MSADM_SVR_PORT
* get the epoch table info as a response from vip:MSADM_SVR_PORT

So, for "DR" <--> "SECURE" , you may have the MSADM_SVR_PORT sufficiently open on the firewall
but does not have port 371 sufficiently open - it is open only when communicating to the physical host name/IP

And for "MAIN" to do "lsepoch -actual SECURE" it would need to have to open the ports for direct communication between "MAIN" and "SECURE", because "DR" cannot be used as a proxy server.
This RFE is to request that this does work through a proxy. RFE for "msadm_server proxy support" but it needs to stay generic to allow all Multisite administration through a proxy for all cases.

Idea priority High
RFE ID 106064
RFE Product Rational ClearCase
  • Guest
    Jan 25, 2018

    A preliminary evaluation of this request indicates that it is consistent with our business strategy. Further evaluation of this RFE is underway.