Home

How do I

Soft - is your software and documentation
Asset - is something that must be protected
Management - is what we do
Enterprise - is the capability
Computing - is the power
Services - are what we provide


ClearCase MultiSite “How do I” covers: (Last updated 20-Feb-12)

Ø  Interfaces – Web console, Global Monitoring, etc...

Ø  Shipping – shipping orders, target VOBs, ms_rtn directories, etc...

Ø  Packets – size, fragments, encryption, etc...

Ø  Epoch Numbers – changing and resolving issues, etc..

Ø  Mastership – element, reqmaster, ACL, etc...

Ø  Replicas – issues, incompatibility, etc...

Ø  Oplogs – Calculating disk space used by, etc..

Ø  Permissions & Access Control Lists – setting, etc...

Ø  Types – global definitions, avoiding naming conflicts, etc...

Ø  Feature Levels – understanding, etc...

Ø  Storage – replacing storage containers from, etc...

Ø  Synchronisation mode and, etc...

Ø  Environment – MultiSite port requirements, etc...

Ø  Utilities – multisiteinfo.pl script, etc...

Ø  Sync Manager – Sync Manager Alert, changing synchronisation mode, etc...

Ø  Problems & Issues – Group not on secondary group list, etc...

Table of Contents     

ClearCase MultiSite “How do I” covers: (Last updated 20-Feb-12) 1

Table of Contents. 1

Interfaces. 5

1.       How do I – why the ClearCase installer disables the ClearCase Multisite Global Monitor feature on Linux x86 platforms  5

2.       How do I – understand the unexpected confirming message box while administering Global Monitoring user setting  5

3.       How do I – understand why the ITM OS agent is not connected after remote deployment in cross domain environment 6

4.       How do I – understand that ClearCase MultiSite Global Monitor installation should run "rgy_upgrade" and "rgy_upgrade -hnames". 7

5.       How do I – use the ClearCase MultiSite Administration Web Console. 7

6.       How do I – understand about the Global monitor deselect option during ClearCase installation. 8

7.       How do I – understand the unexpected confirming message box while administering Global Monitoring user setting  9

8.       How do I – understand the failure to install ClearCase MultiSite Global Monitor option on Solaris Sparc 5.10  9

Shipping.. 10

9.       How do I – understand the alternatives to store-and-forward shipping across a firewall on Windows. 10

10.     How do I - configure the ClearCase MultiSite store-and-forward facility from the command line. 10

11.     How do I – understand troubleshooting: Diagnosing Shipping Server Problems. 11

12.     How do I - creating a MultiSite shipping order to send a file. 12

13.     How do I - identify the target VOB for ClearCase MultiSite import packet 12

14.     How do I - understand the ms_rtn directory. 13

15.     How do I – understand the expected additional packet fragments error 13

16.     How do I – understand the request to configure the ClearCase MultiSite store-and-forward facility through the command line  14

Packets. 15

17.     How do I – understand why the import of new replica creation packet fails with error: multitool: Error: Replica "replica-x" already exist 15

18.     How do I - Identify ClearCase MultiSite packet fragments in version 7.0. 15

19.     How do I – understand the supplement to the MultiSite Command Reference Guide on lspacket 18

20.     How do I – understand the MultiSite ignores the specified maximum packet size setting issue. 19

21.     How do I - use data encryption with ClearCase MultiSite packets. 20

22.     How do I – understand the bad magic number on packet error reported during syncreplica -import 21

23.     How do I - Set the ClearCase MultiSite scheduled job to send packets to a group of replicas. 22

24.     How do I – understand the supplement to the MultiSite Command Reference Guide on lspacket 26

Epoch Numbers. 27

25.     How do I - Manually change epoch numbers to resend missing changes. 27

26.     How do I – resolve lsepoch -actual and chepoch -actual fail when run against prior ClearCase versions issue  27

27.     How do I – understand the could not find our own epoch number in our own epoch row issue. 28

Mastership. 29

28.     How do I – use a static port for mastership requests with ClearCase MutiSite. 29

29.     How do I - Creating a ClearCase element in a directory that does not master the main branch type and where reqmaster is not enabled to allow mastership changes to occur automatically. 30

30.     How do I - determine if an unreserved checkout is nonmastered. 31

31.     How do I - use the extended naming suffix when attempting to chmaster a branch. 31

32.     How do I – understand the extended naming suffix when attempting to chmaster a branch issue. 32

33.     How do I - update the reqmaster ACL on UNIX without an NIS domain. 32

34.     How do I – use command line checking of request for mastership operations. 32

35.     How do I - hide the Request for Mastership features from the ClearCase GUIs. 33

36.     How do I - determine if an unreserved checkout is nonmastered. 34

37.     How do I - pull mastership of an improperly removed VOB replica. 34

38.     How do i – understand the could not set ACL when changing the reqmaster permissions issue. 35

39.     How do I – understand why the chmaster command requires a view context 37

40.     How do I - assign mastership of new branches to the local replica. 37

41.     How do I - make the Current Replica the Master of All Newly Created Branches fails when directory is view private  38

42.     How do I – understand about requesting mastership in a firewall environment 38

43.     How do I - find the master replica name for a ClearCase element 38

44.     How do I – why reqmaster fails without specific error 39

Replicas. 41

45.     How do I - pull mastership of an improperly removed VOB replica. 41

46.     How do I – understand why the sum output is different when run against the same element version in different IBM® Rational® ClearCase® MultiSite® replicas. 42

47.     How do I – understand about being unable to unlock a VOB after completing restorereplica. 42

48.     How do I – understand the White paper: ClearCase Multisite Replica Recovery in secure one-way synchronization environments  43

49.     How do I – understand about stale restorereplica oplogs. 43

50.     How do I - restore a damaged replica when using single-hub synchronisation and the database backup is available for ClearQuest MultiSite. 46

51.     How do I – understand about the restorereplica process. 47

52.     How do I - recover a lost or corrupted restorereplica packet 49

53.     How do I – understand about deleted replicas. 49

54.     How do I – understand why a replica cannot update itself 50

55.     How Do I – understand the multitool lsreplica -fmt "%[replica_name]p" does not return replica names for VOB issue  52

56.     How do I – understand the “Process not running on registry specified hostname” issue. 52

57.     How do I – resolve a Replica incarnation is old issue. 53

58.     How do I – understand the packet is not applicable to any local VOB replicas. 56

59.     How do I – understand about vob_sidwalk changes and propagation between MultiSite replicas. 56

60.     How do I – resolve a Checkouts are not visible after a VOB replica replacement issue. 57

61.     How do I – resolve cannot list all replicas, incompatible versions of clearcase software and or database issue  58

62.     How do I – resolve a replica creation fails with Unable to open file …\s\sdft error issue. 59

63.     How do I – understand the difference between the TMPDIR variable and the -WORKDIR switch with respect to synchronization  60

64.     How do I – understand about location of comment provided at replica creation time. 62

65.     ow do I - replace a source container in a replicated VOB from a container in a sibling replica. 63

66.     How do I – understand the could not determine synchronization mode for replica issue. 69

67.     How do I – understand about the restorereplica process. 71

68.     How do I – understand the replica cannot be created from the packet issue. 73

69.     How do I - understand the replica already exists issue when trying to import a new replica. 73

70.     How do I - determine from which VOB a replica creation packet originated. 74

71.     How do I – understand the path in packet does not match previous: string_dump_file. 75

72.     How do I – understand about replicating cross-VOB symlinks. 75

73.     How do I – understand about the mkreplica -import with -preserve is failing when a group is in a user's large groups list 76

74.     How do I – understand the replica is still gateway for replica type issue. 77

75.     How do I - pull mastership of an improperly removed VOB replica. 77

76.     How do I - set the ClearCase MultiSite scheduled job to send packets to a group of replicas. 78

77.     How do I - determine or change the synchronization mode of a replica. 82

78.     How do I – understand about VOB cloning and MultiSite replica family separation. 83

79.     How do I – understand about the syncreplica export and import process during reqmaster 83

80.     How do I – understand about the protect Container failed error during mkreplica -import –preserve. 83

81.     How do I – understand why MultiSite ignores the specified maximum packet size setting. 84

82.     How do I – understand the synchronization packets being generated larger than the specified -maxsize option issue  86

83.     How do I - determine when the Properties of a replica changed. 86

84.     How do I – understand the “Error db_dumper.54.exe when creating a new VOB replica”. 87

85.     How do I – “create a replica creation packet when the storage bay is full”. 87

Oplogs. 89

86.     How do I – understand about the Import error: File "/var/tmp/syncsXXX" had the wrong length (expected: YYY, found: ZZZ) 89

87.     How do I - calculate oplog records and disk space usage. 89

88.     How do i – use the multitool dumpoplog command. 90

89.     How do I – understand the operation "xdr_vob_oplog_data_t (decode)" failed issue. 92

90.     How do I – understand about stale restorereplica oplogs. 94

91.     How do I – understand the “Gap in oplog detected for replica” issue. 94

Permissions and Access Control Lists (ACL) 96

92.     How do I – understand why the msadm_acls file located in the VOB storage directory is created with root ownership not as VOB creator/owner 96

93.     How do I – understand the could not set ACL when changing the reqmaster permissions issue. 96

94.     How do I - protect Container failed error during mkreplica -import -npreserve. 96

Types. 97

95.     How do I - avoid name conflicts for type object in MultiSite. 97

96.     How do I – understand about ClearCase MultiSite mastership of global types. 98

97.     How do I – resolve a too many global definitions for local type. 98

98.     How do I - change unused element types in a replicated VOB. 99

99.     How do I – understand changing used element types in a replicated VOB. 102

Feature Levels. 108

100.        How do I – understand the replica feature level displayed as unknown issue. 108

101.        How do I – understand why the replica feature level displayed as unknown. 108

102.        How do I – understand the feature level of the VOB family is not high enough to permit this operation issue  109

Storage. 110

103.        How do I – understand why a VOB container database size mismatch is recorded. 110

104.        How do I - replace a source container in a replicated VOB from a container in a sibling replica. 110

105.        How do I - replace a source container from backup in a replicated VOB. 113

Synchronisation.. 118

106.        How do I - enhance sync_receive receipt-handler to queue and prioritize incoming MultiSite packets to improve import efficiency and throughput. 118

107.        How do – understand the could not determine synchronization mode for replica issue. 118

Cause 1.. 118

108.        How do I - compress replica sync packets on export 120

109.        How do I – understand the unable to create a container in VOB issue. 120

110.        How do I – understand the problem of starting or contacting sync manager on host 121

111.        How do I - get the scheduler to sync VOBs located in different regions. 122

112.        How do I – understand why replicas continue to re-generate the same packet data with each subsequent syncreplica -export 122

113.        How do I understand about syncreplica -export sends packet but process does not quit 124

114.        How do I – disable the syncmgr_server process. 125

Environment. 126

115.        How do I – understand about the CCRC .ccase_wvreg file. 126

The work around is to use -cvi\ew... 127

116.        How do I - move a VOB using ClearCase MultiSite. 127

117.        How do I – understand the MultiSite port requirements for firewalls. 130

118.        How do I – understand that “Support for ClearCase MultiSite Admin Console and ClearCase MultiSite Synchronization Management to be Discontinued” from v7.1 2008 release. 131

Utilities. 132

119.        How do I – understand bout multisiteinfo.pl perl script 132

120.        How do I - trace ClearCase MultiSite. 133

Sync Manger. 138

121.        How do I – disable the syncmgr_server process. 138

122.        How do I debug the MultiSite sync_receive.bat and sync_export_list.bat scripts. 139

123.        How do I – understand the ALERT: Sites using Sync Manager for ClearCase MultiSite. 140

124.        How do I - determine or change the synchronization mode of a replica. 141

125.        How do I – understand the problem starting or contacting sync manager on host 141

126.        How do I - enhance sync_receive receipt-handler to queue and prioritize incoming MultiSite packets to improve import efficiency and throughput. 143

Problems and Issues. 143

127.        msadm_acls file located in the VOB storage directory is created with root ownership not as VOB creator/owner 143

128.        How do I – why the multitool man pages are not displayed when using ClearCase 7.1. 144

129.        How do I – understand the MustGather: Tracing ClearCase MultiSite. 144

Run the failing syncmgr command. Each time a command is run more information should be sent to STDOUT in the shell running the syncmgr_server command.. 150

130.        How do I - replicate only parts of a VOB using ClearCase MultiSite. 150

131.        How do I – understand “the current replica has a host name of "old-host" Should this be updated to "new-host" before proceeding” issue. 150

132.        How do I – understand the “Unable to contact albd_server on host” issue. 150

133.        the “ALERT: Sites using MultiSite and versioned derived objects”. 151

134.        How do I – understand the multitool: Error: Can't create object with group that is not in the VOB's group list problems  152

135.        How do I – understand about Version data file had the wrong length errors. 154

136.        How do I – understand that a data file <source container> had the wrong length (expected: ##, found: ##) error during syncreplica. 155

137.        How do I – understand the Version data file <cleartext container> had the wrong length (expected: ##, found: ##) error during syncreplica issue. 158

138.        How do I – understand the Version data file <source container> had the wrong length (expected: ##, found: ##) error during syncreplica issue. 160

139.        How do I – understand why the version data file <cleartext container> had the wrong length (expected: ##, found: ##) error during syncreplica export 162

140.        How do I – resolve the multitool mkreplica -import -preserve does not preserve permissions on containers issue  166

141.        How do I – understand the trouble removing view references from a replicated VOB using rmview -uuid -vob command issue  167

142.        How do I – understand the can't redefine element types when VOB is replicated issue. 168

143.        How do I – understand the unable to decode packet header unknown packet version issue. 169

144.        How do I – understand the performance hit running db_loader associated commands with ClearCase 7.x  170

145.        How do I – understand the unable to create a new element when the parent directory cannot be checked out due to branch mastership issues. 170

146.        How do I – understand the multitool: Warning: Object "file_name" no longer referenced issue. 171

147.        How do I - set the ClearCase MultiSite scheduled job to send packets to a group of replicas. 172

148.        How do I – understand the impact of renaming the VOB storage or changing the VOB tag of a replicated VOB  177

Interfaces

1.        How do I – why the ClearCase installer disables the ClearCase Multisite Global Monitor feature on Linux x86 platforms

When selecting the ClearCase Multisite Global Monitoring feature, the installer disables the feature with the following message:


"/usr/local/ibm" either doesn't exist or is not writable. This directory is necessary for the installation of Global Monitor.

 

Resolving the problem

Manually create the writable directory /usr/local/ibm before starting the installation process.

2.        How do I – understand the unexpected confirming message box while administering Global Monitoring user setting

To enable ClearCase view of MultiSite Global Monitor, it is required to configure a user setting in 'Administer Users' panel of Tivoli Enterprise Portal(TEP) client. In the 'Administer Users' panel of TEP client, a message box pops up unexpectedly, saying:
KFWITM037W User information has changed, do you want to save the changes?
even though nothing is changed yet.
If [Yes] button is clicked, another error message box appears.

 

Cause

<CCUSER> template user is provided as read-only and it is flagged as having unsaved change.

 

The unexpected prompt is displayed when you deselect the <CCUSER> item. The <CCUSER> item is provided as a template to make it easy to add a new user, and the template itself is read-only. There is no harm to choose either [Yes] or [No] to the prompt, although the save operation always fails.

3.        How do I – understand why the ITM OS agent is not connected after remote deployment in cross domain environment

When the IBM Tivoli Monitoring(ITM) OS agent is deployed remotely as part of ClearCase MultiSite Global Monitor installation, the agent does not report its status to the monitoring hub host (Tivoli Enterprise Monitoring Server) if the agent and hub hosts are in different network domains

 

Symptom

When you type the following command to deploy OS agent remotely from monitoring hub host to ClearCase server machines :


C:\IBM\ITM\bin\tacmd createNode -h target_host -u user -w password

the command completes with a successful message. But OS agent does not report its status. Therefore, the following ITM command does not list your OS agent:

C:\IBM\ITM\bin\tacmd listsystems -t NT UX LZ

 

Cause

To deploy the OS agent remotely, the agent host must be configured with the hub host's domain suffix.
TEMS hostname in the agent's configuration is set as the TEMS machine name without a fully qualified domain name while you deploy OS agent remotely.

Here is an example case. Given those fully qualified names:
TEMS host : test-tems.domain1.com
agent's host : test-target.domain2.com
Agent's configuration points to 'test-tems' as opposed to 'test-tems.domain1.com', and then the agent failed to locate TEMS server to connect. to.

 

Resolving the problem

If you have not deployed OS agent remotely yet, you can avoid this problem by adding DNS suffix to the agent host machine's network setting.

1.     add a domain name of TEMS in DNS suffix on agent host machine

2.     deploy OS agent remotely from TEMS

3.     execute "tacmd listsystems" on TEMS, and confirm the name of the agent host with "Y" status

If you already have deployed OS agent, you can reconfigure OS agent to connect to TEMS host in a different domain.
To reconfigure TEMS hostname of OS agent configuration on Linux or on Solaris,
( please read $AGENT_CODE as 'lz' on Linux, and as 'ux' on Solaris )

1.     stop OS agent by this command
/opt/IBM/ITM/bin/itmcmd agent stop $AGENT_CODE

2.     reconfigure OS agent by this command
/opt/IBM/ITM/bin/itmcmd config -A $AGENT_CODE

3.     set TEMS hostname with fully qualified domain name when asked to input TEMS hostname.

4.     start OS agent again by this command
/opt/IBM/ITM/bin/itmcmd agent start $AGENT_CODE

5.     go back to TEMS host, execute "tacmd listsystems", and confirm the name of the agent host with "Y" status

To reconfigure TEMS hostname of OS agent configuration on Windows,

1.     navigate to [IBM Tivoli Monitoring] -> [Manage Tivoli Monitoring Services] from Windows' start menu

2.     right-click at Monitoring Agent for Windows OS and select Reconfigure menu

3.     click OK to the first dialog

4.     set TEMS hostname with fully qualified domain name in Hostname of IP Address field at the second dialog

5.     click OK to the second dialog

6.     In the [Manage Tivoli Enterprise Monitoring Services] window, right-click at Monitoring Agent for Windows OS and select Start menu

go back to TEMS host, execute "tacmd listsystems", and confirm the name of the agent host with "Y" status

4.        How do I – understand that ClearCase MultiSite Global Monitor installation should run "rgy_upgrade" and "rgy_upgrade -hnames"

The ClearCase MultiSite installation and ClearCase MultiSite Global Monitor installation queue the execution of "rgy_upgrade" and "rgy_upgrade -hnames" to occur after the next reboot rather than running the commands as part of the install itself.

 

Symptom

The ms_site_name setting cannot be set on Windows Clearcase Servers. The Global Monitor TEP Client cannot display the hostinfo workspace or all the views and VOBs for Windows ClearCase Servers installed with Global Monitoring until "rgy_upgrade" and "rgy_upgrade -hnames" are run.

 

Cause

The Rational ClearCase Global Monitor data collection scripts rely on the ms_site_name setting and the file generated by "rgy_upgrade" and "rgy_upgrade -hnames" to organize monitored hosts and determine all the variations of the local hostname used in the ClearCase registry for this server.

 

Diagnosing the problem

Check if the ms_site_name is set by running:
"multitool lssetting -site ms_site_name"
Check if the file below exists and contains all the local hostname variations used in the CC registry:
<ClearCase Install directory>\var\adm\cache\global_monitor\equiv_hostnames
If it does not exist or the contents is incomplete, follow instructions below for resolving this.

 

Resolving the problem

If ms_site_name is not set, run "rgy_uprade". If the "equiv_hostnames" file does not exist, run "rgy_upgrade -hnames".

The following instructions allow you to run "rgy_upgrade -hnames" via the Global Monitor TEP Client UI,

From the Global Monitor TEP client, select the ClearCase node under the ClearCase server node. Right click and choose Take Action -> Select. In the Take Action dialog drop down menu for Name, choose Alternate_Hosts. Cancel out of the Edit Argument dialog and click okay to execute "rgy_upgrade -hnames" on that ClearCase server. The new equiv_hostnames file will be used during the next cache refresh. Alternatively, you can force cache refreshes by choosing Take Action -> Select again and choosing Clear_All_Caches. Note that there will be a delay in reloading displays while the data is collected.

5.        How do I – use the ClearCase MultiSite Administration Web Console

The ClearCase MultiSite Administration Web Console is a web-based interface that MultiSite administrators can use to manage all replicas at their site. This feature was introduced in version 2003.06.14 (Service Release 4).

To access the ClearCase MultiSite Administration Web Console from a web client go to:


http://<hostname_multisite_server>/msweb/


Using the MultiSite Administration Web Console, you (acting as an administrator) have access to information about the environment and can perform specific tasks:

a.     Replica Properties

b.     VOB Family and Replica server information

c.     Scheduled jobs on a Replica server

d.     Current Imports and Exports for a replica or replica server

e.     Export or Import history for a replica or replica server

f.      Packets in the shipping bays on a host, as well as details about synchronization packets

g.     Server Logs on a host


A MultiSite environment can contain multiple machines that host MultiSite Administration Web Consoles, although only one is necessary. The machine that hosts the MultiSite Administration Web Console does not need to have ClearCase or MultiSite installed, but it must meet the following criteria:

MultiSite Web Administration Console supports SSL

The ClearCase MultiSite Web Administration Console supports the use of Secure Socket Layer (SSL).

The Rational Web Platform (RWP) Server is the underlying Web server used for ClearCase MultiSite Web console. To properly configure the MultiSite Web console to use the https protocol, refer to
technote 1220726 which details how to configure RWP to use SSL.

For more information about the MultiSite Administration Web Console, review the IBM Rational ClearCase Documentation Supplemental for SR4.

Note: This document is also located in the
IBM Publication Center under publication number GI11-5977-04.
Related information

About Firewalls and ClearCase
MS Administration Web Console and Sync Manager
Firewall and MultiSite Administration Web Console
Persistent filters and MSWeb Console
ClearCase 2002.05.x upgrade to 2003.06.x on Windows

6.        How do I – understand about the Global monitor deselect option during ClearCase installation

What information is available to explain the graphical representation of Global Monitor deselect option during the installation of IBM® Rational® ClearCase MultiSite® (CC) 7.1 on a Unix or Linux host?

 

Answer

This information helps to explain the meaning of the graphical display of the Global Monitor deselect options that are listed during the installation of ClearCase MultiSite version 7.1.

There are three states with the check-box of installation components:


empty   -  Indicates this is not selected

checked(v) -  Indicates this is selected

minus (-) -  Indicates this is partially selected

The Install Manager's graphical representation is:

empty    docview
checked(v)   docview
minus (-)  docview

In these screen captures, the difference between the empty and minus states are slight and may be hard to distinguish.

If you select the MultiSite option and deselect the Global Monitor option, it will appear like a Minus state which means partially selected

7.        How do I – understand the unexpected confirming message box while administering Global Monitoring user setting

To enable ClearCase view of MultiSite Global Monitor, it is required to configure a user setting in 'Administer Users' panel of Tivoli Enterprise Portal(TEP) client. In the 'Administer Users' panel of TEP client, a message box pops up unexpectedly, saying:
KFWITM037W User information has changed, do you want to save the changes?
even though nothing is changed yet.
If [Yes] button is clicked, another error message box appears. What is this messages about?

 

Cause

<CCUSER> template user is provided as read-only and it is flagged as having unsaved change.

 

Answer

The unexpected prompt would appear when you select away from <CCUSER> item. The <CCUSER> item is provided as a template to make it easy to add a new user, and the template itself is read-only. There is no harm to choose either [Yes] or [No] to the prompt, although the save operation fails every time.

8.        How do I – understand the failure to install ClearCase MultiSite Global Monitor option on Solaris Sparc 5.10

cInstallation of ClearCase MultiSite Global Monitor option fails on Solaris Sparc 5.10 when ITM(IBM Tivoli Monitoring)'s OS agent is already installed.
In a typical deployment of Global Monitoring, IBM Tivoli Monitoring(ITM)'s OS agent is installed remotely before installing ClearCase 7.1 through Installation Manager, as described in this document:
http://publib.boulder.ibm.com/infocenter/cchelp/v7r1m0/topic/com.ibm.rational.clearcase.cc_ms_install.doc/topics/c_planning_gmon_install_worksheet.htm

 

Problem(Abstract)

Installation of ClearCase MultiSite Global Monitor option fails on Solaris Sparc 5.10.

The error message at the failure of the installation is:
Error during "install" phase:
  Unable to find custom install operation class "com.ibm.rational.clearcase.globalmonitoring.UnconfigureUnix" for installable unit: MS.gmon.64bit.sun5
    java.lang.ClassNotFoundException: com.ibm.rational.clearcase.globalmonitoring.UnconfigureUnix
  Action GskitAction (install /opt/IBM/RationalSDLC) failed: java.io.IOException: Exit status 1 from command: pkgadd -a ./admin -n -d . gsk7bas
stderr: pkgadd: ERROR: The package <gsk7bas> is currently installed on the system in the
global zone. To install the new instance of this package in the global
zone only, you must specify the -G option. To install the new instance
of this package in all zones you must first remove the existing instance
of this package from the global zone first (via pkgrm) and then install
the new instance of this package in all zones.
pkgadd: ERROR: package <gsk7bas> cannot be installed on this system/zone

 

Cause

There is a conflict in GSKit ( Global Security Kit ) installation between ITM's OS agent installer and Installation Manager.

 

Resolving the problem

There are two ways to work it around.

1.     If you have not installed ITM's OS agent yet,

1.     skip installing OS agent, and install Global Monitoring through Installation Manager

2.     once Global Monitor installation is completed, go back to ITM's OS agent installation with remote deploy from TEMS(Tivoli Enterprise Monitoring Server)

2.     If you have already installed ITM's OS agent, and experienced this installation failure,

1.     stop OS agent with this command:
/opt/IBM/ITM/bin/itmcmd agent stop ux

2.     uninstall GSKit ( the one installed by OS agent ) with this command:
/usr/sbin/pkgrm gsk7bas

3.     install Global Monitor option with Installation Manager again
(it should work fine this time because there is no GSKit installation conflict )

restart OS agent with this command:
/opt/IBM/ITM/bin/itmcmd agent start ux

Shipping

9.        How do I – understand the alternatives to store-and-forward shipping across a firewall on Windows

Store and forward shipping across a firewall for IBM® Rational® ClearCase MultiSite® is only available on UNIX® and Linux® servers; however, this technote provides two alternative for Microsoft® Windows® shipping servers.

There are two alternatives available for sites which utilize a Windows shipping server:

1.     Use a third party automated transport that does not involve the MultiSite shipping server. For example, you could automate an FTP process so that it puts (and gets) packets on a server that both replicas can access securely.

2.     Use a UNIX/Linux server as the store-and-forward server, straddling the firewall.

Note: Using a Windows hosted store-and-forward server that is exposed outside your companies firewall is not recommended. Refer to the
Firewall Issues section of the IBM ClearCase MultiSite Administrators Guide under the topic of Other services can be accessible for further details.

Because all ClearCase related processes are affected by the CLEARCASE_MIN_PORT and CLEARCASE_MAX_PORT environment variables outlined in technote 1207525, this server cannot be used for other ClearCase operations. Although the chance is minimal, there is the potential for a port conflict between the shipping_server and other ClearCase processes even if this server is only used for shipping purposes

10.     How do I - configure the ClearCase MultiSite store-and-forward facility from the command line

How can I configure IBM® Rational® ClearCase MultiSite® store-and-forward facility from the command line? This technote provides you with information about a change request for ClearCase MultiSite regarding functionality to allow the modification of the MultiSite store-and-forward facility from the command line

 

Cause

Change request (RFE) RATLC01025818 has been opened to further investigate implementing a command line option to allow modifications to the MultiSite store-and-forward configuration parameters.

 

Answer

The RFE is still open and remains under investigation for possible inclusion in a future release. Currently, there is no command line equivalent for modifying the MultiSite store-and-forward settings.

WORKAROUND:

Edit the shipping.conf file (located in /var/adm/rational/clearcase/config directory ) on UNIX® or Linux® or the MultiSite Control Panel on Microsoft® Windows® to update the shipping server configuration settings.

Windows: