Protocol version between 6.3 control-m agent and 6.2 server

abhipali · Post by **abhipali** » 20 Jan 2010 11:26

Hi All,

Can any one confirm me what would be the protocol version between control-m agent 6.3 and control-m server 6.2. BMC confirmed that higher version agent can work with lower version server.

rahulsehgal · Post by **rahulsehgal** » 20 Jan 2010 12:52

Default Port numbers for agent 6.2 and Server 6.3 communication is specified below:-

Agent-to-Server Port Number
Listening port in the Server computer that receives data this Agent. The value specified must match the value assigned to the Agent-to-Server Port Number parameter on the Server. Verify that this port number is not used in the Server for any other purpose. Specify a numeric value between 1025 and 65535. Default: 7005

Server-to-Agent Port Number
Listening port of this Agent that receives data from the Server. The value specified must match the value assigned to the Server-to-Agent Port Number parameter (for this Agent) on the Server. Verify that this port number is not used for any other purpose. Specify a numeric value between 1025 and 65535. Default: 7006

Regards,
Rahul Sehgal

abhipali · Post by **abhipali** » 20 Jan 2010 1:01

thnaks woddy i think so it shld be 06 as server can not take value more then 06 while server, agent shld retain same protocol version

philmalmaison · Post by **philmalmaison** » 20 Jan 2010 10:27

in wich case or knowledge or documentation BMC write somethink like 6.3 agent with 6.2 server, i confirm they're not supporting that kind of infrastructure, only if the case is the result of a possible bug ?

regards
philmalmaison

nicolas_mulot · Post by **nicolas_mulot** » 21 Jan 2010 11:14

Hi all,

Refer to Knowledge base entry SLN000000192368. In some cases, for example to support specific versions of OS without upgrading the entire control-m environment, it is possible to simply upgrade one or a little number of control-m agents which hence are at a higher version than the server.

I dont know whether a specific fix is to be applied on the server to support protocol numbers which are not in the admin guide: the best in that situation is to contact BMC support. All I know is that such a situation does exist

Nicolas_Mulot

philmalmaison · Post by **philmalmaison** » 27 Jan 2010 12:02

ok
As a general rule of thumb, the CONTROL-M/Enterprise Manager version has to be greater or equal to the CONTROL-M/Server version, which in turn should to be greater or equal to the CONTROL-M/Agent version. (This only applies to the product version, not to the Fix pack version.)

The exception to this rule is the CONTROL-M/Agent. It is possible to run an environment where the CONTROL-M/Agent is a higher release than the CONTROL-M/Server provided that the Protocol Version the CONTROL-M/Server users to communicate with the CONTROL-M/Agent is correctly configured. You can find out more about Protocol Version in the CONTROL-M/Server Administrator Guide.

Examples:

For instance CONTROL-M/Agent 6.1.03, with Fix pack version 6.1.03.300 will be compatible with CONTROL-M/Server 6.1.03 with Fix pack 6.1.03.100. We only look at the product version here, which is 6.1.03.

CONTROL-M/Enterprise Manager 6.4.0.1 supports CONTROL-M/Server 6.3.01 (because it is a lesser version) with CONTROL-M/Agent 6.1.03.

CONTROL-M/Server 6.3.01 will support CONTROL-M/Agent 6.1.03 but CONTROL-M/Server 6.3.01 will not work under CONTROL-M/Enterprise Manager 6.2.01 because the version of CONTROL-M/Enterprise Manager must always be at least the same or higher version as the CONTROL-M/Server.

Note: CONTROL-M/Enterprise Manager Fix packs levels should be the same on the client and the server. This means that if Fix pack 6.1.03.100 has been installed on the CONTROL-M/Enterprise Manager Server, it also needs to be installed on the Windows client.

ITS ONLY TALKING ABOUT FIXPACK VERSION BEETWWEEN SERVER AND AGENT.

regards
philmalmaison