Agent status showing unavailable...
Agent status showing unavailable...
Hi..need your guidance urgently..we had done a migration of ip and got a new ip id for the host but after starting all control-m services (server's,em) I found control-m agent is still in unavilable status we are using control-m for SAP platform even I tried to login through ctm_menu in unix server but its still showing the agent is unavliable kindly suggest what to do in this case.
Hi,
Hi,
here some suggestions to investigate.....
From the CONTROL-M/Server:
1) ctm_menu --> opt10 (Troubleshooting) --> opt15 (Communication Diagnostic Report). If the UNIX ping failed, there maybe an issue with DNS
2) ctm_menu --> opt6 (Parameter Customization) --> opt1 (Basic Communication) and check local IP host interface
3) <ctmping> controlm utility
ctmping -NODEID <Host Name> [ -NODETYPE <REGULAR|REMOTE> ]
[ -NODEID <Host Name> [ -NODETYPE <REGULAR|REMOTE> ] ]
[ -FILE <input file> ]
[ -DISCOVER <y|n>]
[ -DEBUG <debug level 0-5> ]
[ -QUIET ]
[ -FULLDETAILS ]
4) ctm_menu --> option9 --> opt 4 (Delete Agent entry) after run --> opt6 (Discover option) to re-identify the agent and run the availability tests again
5) Have you see the PROCLOG logs (agent or CONTROL-M/Server (ie:NSxxxx.log))
6) Execute nslookup <your_agent>
From the agent:
1) The process Agent & Tracker are running ? run <shagent>
2) Check the comunication from the agent to the server : run <ag_diag_comm>. If the agent ping CONTROL-M/Server failed, there maybe an issue with DNS
3) Check parameters (autorized CONTROL-M/Server,version protocol, ports,mode,etc...) run <ctmagcfg> or edit agent home directory/ctm/data/CONFIG.dat
Others:
If you used DNS, check entries
If you used /etc/hosts on CONTROL-M/Server or agent , check entries
Check file system (space)
Hi,
here some suggestions to investigate.....
From the CONTROL-M/Server:
1) ctm_menu --> opt10 (Troubleshooting) --> opt15 (Communication Diagnostic Report). If the UNIX ping failed, there maybe an issue with DNS
2) ctm_menu --> opt6 (Parameter Customization) --> opt1 (Basic Communication) and check local IP host interface
3) <ctmping> controlm utility
ctmping -NODEID <Host Name> [ -NODETYPE <REGULAR|REMOTE> ]
[ -NODEID <Host Name> [ -NODETYPE <REGULAR|REMOTE> ] ]
[ -FILE <input file> ]
[ -DISCOVER <y|n>]
[ -DEBUG <debug level 0-5> ]
[ -QUIET ]
[ -FULLDETAILS ]
4) ctm_menu --> option9 --> opt 4 (Delete Agent entry) after run --> opt6 (Discover option) to re-identify the agent and run the availability tests again
5) Have you see the PROCLOG logs (agent or CONTROL-M/Server (ie:NSxxxx.log))
6) Execute nslookup <your_agent>
From the agent:
1) The process Agent & Tracker are running ? run <shagent>
2) Check the comunication from the agent to the server : run <ag_diag_comm>. If the agent ping CONTROL-M/Server failed, there maybe an issue with DNS
3) Check parameters (autorized CONTROL-M/Server,version protocol, ports,mode,etc...) run <ctmagcfg> or edit agent home directory/ctm/data/CONFIG.dat
Others:
If you used DNS, check entries
If you used /etc/hosts on CONTROL-M/Server or agent , check entries
Check file system (space)
Best regards
Walty
Walty
- philmalmaison
- Nouveau
- Posts: 1148
- Joined: 08 Jun 2007 12:00
- Location: Ile de France
- philmalmaison
- Nouveau
- Posts: 1148
- Joined: 08 Jun 2007 12:00
- Location: Ile de France
- philmalmaison
- Nouveau
- Posts: 1148
- Joined: 08 Jun 2007 12:00
- Location: Ile de France
- philmalmaison
- Nouveau
- Posts: 1148
- Joined: 08 Jun 2007 12:00
- Location: Ile de France