On CM Server - ctm_diag_comm question

Everything about Control-M Enterprise Manager Server installation or setup.
Post Reply
User avatar
GregE
Nouveau
Nouveau
Posts: 15
Joined: 02 May 2011 12:00

On CM Server - ctm_diag_comm question

Post by GregE » 18 May 2011 5:43

On my CM server, when I login as the CM Server user and run ctm_diag_comm, I get different results for the same address, depending on whether I use hostname only, or fully qualified hostname. If I use fully qualified, CTMS Pings as a regular agent only.

#
Enter Agent platform node ID: SERVER1.company.com

Executing ctmping SERVER1.company.com as Regular Agent

CONTROL-M/Server to CONTROL-M/Agent Communication Diagnostic Report
-------------------------------------------------------------------

CTMS User Name : ctms630
CTMS Directory : /opt/controlm/ctms630/ctm_server
CTMS Platform Architecture : Solaris
CTMS Installed Version : PACTV.6.3.01.400
CTMS Local IP Host Interface Name : SERVER1.company.com
Server-to-Agent Port Number : 7006
Agent-to-Server Port Number : 7005
Server-Agent Comm. Protocol : TCP
Server-Agent Protocol Version : 07
Server-Agent Connection mode : Transient
Agent Platform Name : SERVER1.company.com
Agent Status : Available
Agent known Type : Regular
UNIX ping to Agent or Remote host : Succeeded
CTMS ping to Agent or Remote host : Succeeded

CTMS Ping SERVER1.company.com as Regular Agent
===============================================
Agent [SERVER1.company.com] is available
##
##
##
But If I use node ID of only the hostname, SERVER1, its pinged as both remote, and regular agent, and goes through fully qualified name SERVER1.company.com and results in an Agent Status of "unknown" and Agent known Type of "undefined." Why is there a difference in the results?

Enter Agent platform node ID: SERVER1

Executing ctmping SERVER1 as Regular Agent

Executing ctmping SERVER1 as Remote Host ..


CONTROL-M/Server to CONTROL-M/Agent Communication Diagnostic Report
-------------------------------------------------------------------

CTMS User Name : ctms630
CTMS Directory : /opt/controlm/ctms630/ctm_server
CTMS Platform Architecture : Solaris
CTMS Installed Version : PACTV.6.3.01.400
CTMS Local IP Host Interface Name : SERVER1.company.com
Server-to-Agent Port Number : 7006
Agent-to-Server Port Number : 7005
Server-Agent Comm. Protocol : TCP
Server-Agent Protocol Version : 07
Server-Agent Connection mode : N/A
Agent Platform Name : rchdev1
Agent Status : Unknown
Agent known Type : Undefined
UNIX ping to Agent or Remote host : Succeeded
CTMS ping to Agent or Remote host : Succeeded

CTMS Ping SERVER1 as Regular Agent
==================================
Agent [SERVER1] is available

CTMS Ping SERVER1 as Remote Host
================================
Remote host [SERVER1] is available through Agent [SERVER1.company.com]
Connection protocol : SSH
Port number : 22
Encryption method : BLOWFISH
Compression : No

#

I also have a regular agent installed on this same machine, with a Logical Agent Name of SERVER1.company.com and a Server-to-Agent Port Number of 8006.

Why do my ping results differ?

User avatar
gglau
Nouveau
Nouveau
Posts: 317
Joined: 13 Jun 2007 12:00

Post by gglau » 18 May 2011 9:47

Remote host [SERVER1] is available through Agent [SERVER1.company.com]
As indicated by the output, FQDN has been registered as Agent but the short name is not.

User avatar
philmalmaison
Nouveau
Nouveau
Posts: 1148
Joined: 08 Jun 2007 12:00
Location: Ile de France

Post by philmalmaison » 20 May 2011 4:16

Hi,
Probably you are using etc/hosts file and this short name is not design in it, so if no dns server are registred with this short name, no name resolution.

Regards,
Philmalmaison

Post Reply