robot deployment via OC (20.3) doesnt work

[Stefan Pivoda]

Hi,
are there any prerequisites to deploy a robot via OC (20.3) to a Windows server except WMI access?
= i added the needed user credentials for WMI access into Setup Wizard/Discover Devices/WMI Credentials, then ran a discovery, and the server where i want to deploy a robot is shown in the inventory.
but if i choose the server, and click on robot deployment/Deploy a pop-up message appears that the Deployment is in progress, change will be reflected in a few moments, but nothing happens. tried several times. the robot is not installed and neither an error message nor any other information can be seen.

did i miss something? or where should i check at least any log? automated_deployment_enginge.log doesnt show anything about it.

thank you,
stefan

[Gene Howard]

set your disccovery_server loglevel to 5 and your ADE loglevel to 5 restart and check both again.
Is the robot attached to the primary hub or a secondary hub?
Is there a tunnel between the hubs if a secondary hub?
If a secondary hub do you have Distsrv installed and the packages forwarded to it to do the install?

------------------------------
Gene Howard
Principal Support Engineer
Broadcom
------------------------------

[Stefan Pivoda]

Hi Gene,
the robot ( = server, where i'd like to deploy the robot), should be attached to the primary hub without any tunnel or secondary server.
1. could you please tell me the workflow of the deplyment? = if i click on deploy, which probe/process does it trigger first, second, and so on? 
2. the part of discovery server probe is only for the discovery process, right? so i can skip the investigation of it, if i can see the server in the inventory, right?
3. i suppose, i dont need any XML file, if i use OC, right?
4. did i miss anything? as i increased the loglevel, but i dont see any suggestions in the log file. i tried to deploy the robot at 9:21. 
so, if the deploy button in OC should trigger the ADE probe, it seems that it doesnt trigger anything. what else can i test/try in that case?
thank you, stefan


10162020 09:20:30,215 [attach_socket] TRACE AutomatedDeploymentArchiveCallbacks - Inside ADE Archive Callbacks - 'archive_package_is_deployable' Package Name: rsp Package Version: 5.20 Target: null
10162020 09:20:30,440 [attach_socket] TRACE AutomatedDeploymentArchiveCallbacks - Inside ADE Archive Callbacks - 'archive_package_is_deployable' Package Name: rsp Package Version: 5.33 Target: null
10162020 09:20:30,763 [attach_socket] TRACE AutomatedDeploymentArchiveCallbacks - Inside ADE Archive Callbacks - 'archive_package_is_deployable' Package Name: attr_publisher Package Version: null Target: null
10162020 09:20:37,689 [FileMonitorThread] TRACE FileMonitor - File C:\Program Files (x86)\Nimsoft\probes\service\automated_deployment_engine\host-profiles.xml has not changed. Deployment cancelled.
10162020 09:20:37,689 [FileMonitorThread] TRACE FileMonitor - File C:\Program Files (x86)\Nimsoft\probes\service\automated_deployment_engine\submit_job.xml has not changed. Deployment cancelled.
10162020 09:20:52,688 [FileMonitorThread] TRACE FileMonitor - File C:\Program Files (x86)\Nimsoft\probes\service\automated_deployment_engine\host-profiles.xml has not changed. Deployment cancelled.
10162020 09:20:52,688 [FileMonitorThread] TRACE FileMonitor - File C:\Program Files (x86)\Nimsoft\probes\service\automated_deployment_engine\submit_job.xml has not changed. Deployment cancelled.
10162020 09:21:07,688 [FileMonitorThread] TRACE FileMonitor - File C:\Program Files (x86)\Nimsoft\probes\service\automated_deployment_engine\host-profiles.xml has not changed. Deployment cancelled.
10162020 09:21:07,688 [FileMonitorThread] TRACE FileMonitor - File C:\Program Files (x86)\Nimsoft\probes\service\automated_deployment_engine\submit_job.xml has not changed. Deployment cancelled.
10162020 09:21:22,687 [FileMonitorThread] TRACE FileMonitor - File C:\Program Files (x86)\Nimsoft\probes\service\automated_deployment_engine\host-profiles.xml has not changed. Deployment cancelled.
10162020 09:21:22,687 [FileMonitorThread] TRACE FileMonitor - File C:\Program Files (x86)\Nimsoft\probes\service\automated_deployment_engine\submit_job.xml has not changed. Deployment cancelled.
10162020 09:21:37,687 [FileMonitorThread] TRACE FileMonitor - File C:\Program Files (x86)\Nimsoft\probes\service\automated_deployment_engine\host-profiles.xml has not changed. Deployment cancelled.
10162020 09:21:37,687 [FileMonitorThread] TRACE FileMonitor - File C:\Program Files (x86)\Nimsoft\probes\service\automated_deployment_engine\submit_job.xml has not changed. Deployment cancelled.
10162020 09:21:52,686 [FileMonitorThread] TRACE FileMonitor - File C:\Program Files (x86)\Nimsoft\probes\service\automated_deployment_engine\host-profiles.xml has not changed. Deployment cancelled.
10162020 09:21:52,686 [FileMonitorThread] TRACE FileMonitor - File C:\Program Files (x86)\Nimsoft\probes\service\automated_deployment_engine\submit_job.xml has not changed. Deployment cancelled.
10162020 09:22:07,685 [FileMonitorThread] TRACE FileMonitor - File C:\Program Files (x86)\Nimsoft\probes\service\automated_deployment_engine\host-profiles.xml has not changed. Deployment cancelled.
10162020 09:22:07,685 [FileMonitorThread] TRACE FileMonitor - File C:\Program Files (x86)\Nimsoft\probes\service\automated_deployment_engine\submit_job.xml has not changed. Deployment cancelled.
10162020 09:22:22,684 [FileMonitorThread] TRACE FileMonitor - File C:\Program Files (x86)\Nimsoft\probes\service\automated_deployment_engine\host-profiles.xml has not changed. Deployment cancelled.
10162020 09:22:22,684 [FileMonitorThread] TRACE FileMonitor - File C:\Program Files (x86)\Nimsoft\probes\service\automated_deployment_engine\submit_job.xml has not changed. Deployment cancelled.
10162020 09:22:37,683 [FileMonitorThread] TRACE FileMonitor - File C:\Program Files (x86)\Nimsoft\probes\service\automated_deployment_engine\host-profiles.xml has not changed. Deployment cancelled.

here are the discovery server logs as well:
16 Oct 2020 09:20:01,129 [scanTask-3] INFO com.nimsoft.discovery.server.hub.subscribe.HubSubscriptionManager - BEGIN running 1 hub subscribers
16 Oct 2020 09:20:03,129 [scanTask-3] INFO com.nimsoft.discovery.server.hub.subscribe.HubSubscriptionManager - END running 1 hub subscribers
16 Oct 2020 09:20:20,131 [scanTask-3] INFO com.nimsoft.discovery.server.hub.subscribe.HubSubscriptionManager - BEGIN running 1 hub subscribers
16 Oct 2020 09:20:22,132 [scanTask-3] INFO com.nimsoft.discovery.server.hub.subscribe.HubSubscriptionManager - END running 1 hub subscribers
16 Oct 2020 09:20:39,133 [scanTask-4] INFO com.nimsoft.discovery.server.hub.subscribe.HubSubscriptionManager - BEGIN running 1 hub subscribers
16 Oct 2020 09:20:41,133 [scanTask-4] INFO com.nimsoft.discovery.server.hub.subscribe.HubSubscriptionManager - END running 1 hub subscribers
16 Oct 2020 09:20:45,144 [probeTask-7] DEBUG com.nimsoft.discovery.server.qos.origin.EnrichedOriginPollerTask - 0 S_QOS_DATA rows with enriched origins
16 Oct 2020 09:20:57,259 [probeTask-10] DEBUG com.nimsoft.discovery.server.agent.config.DiscoveryAgentConfigUpdateManager - BEGIN running config update workers for 1 discovery agents
16 Oct 2020 09:20:57,259 [probeTask-10] TRACE com.nimsoft.discovery.server.agent.config.DAVersionMismatchNotifier - Discovery Agent /S-DDCB-IM-PHUB_domain/S-DDCB-IM-PHUB_hub/S-DDCB-IM-PHUB/discovery_agent has valid version 20.30.
16 Oct 2020 09:20:57,277 [daConfigWorker-1] DEBUG com.nimsoft.discovery.server.agent.config.DiscoveryAgentConfigUpdater - Sending configuration to agent /S-DDCB-IM-PHUB_domain/S-DDCB-IM-PHUB_hub/S-DDCB-IM-PHUB/discovery_agent (version 20.30).
16 Oct 2020 09:20:57,277 [daConfigWorker-1] DEBUG com.nimsoft.discovery.common.nimbus.PooledNimRequestWrapper - Sending set_config request to /S-DDCB-IM-PHUB_domain/S-DDCB-IM-PHUB_hub/S-DDCB-IM-PHUB/discovery_agent
16 Oct 2020 09:20:57,615 [attach_socket] DEBUG com.nimsoft.discovery.server.agent.status.RecordDiscoveryAgentStatusCallback - Starting callback record_agent_status.
16 Oct 2020 09:20:57,615 [attach_socket] DEBUG com.nimsoft.discovery.server.agent.status.RecordDiscoveryAgentStatusCallback - Received agent status from /S-DDCB-IM-PHUB_domain/S-DDCB-IM-PHUB_hub/S-DDCB-IM-PHUB/discovery_agent with version 20.30.
16 Oct 2020 09:20:58,132 [scanTask-3] INFO com.nimsoft.discovery.server.hub.subscribe.HubSubscriptionManager - BEGIN running 1 hub subscribers
16 Oct 2020 09:20:59,259 [probeTask-10] DEBUG com.nimsoft.discovery.server.agent.config.DiscoveryAgentConfigUpdateManager - END running config update workers for 1 discovery agents
16 Oct 2020 09:21:00,133 [scanTask-3] INFO com.nimsoft.discovery.server.hub.subscribe.HubSubscriptionManager - END running 1 hub subscribers
16 Oct 2020 09:21:17,132 [scanTask-2] INFO com.nimsoft.discovery.server.hub.subscribe.HubSubscriptionManager - BEGIN running 1 hub subscribers
16 Oct 2020 09:21:19,132 [scanTask-2] INFO com.nimsoft.discovery.server.hub.subscribe.HubSubscriptionManager - END running 1 hub subscribers
16 Oct 2020 09:21:36,131 [scanTask-5] INFO com.nimsoft.discovery.server.hub.subscribe.HubSubscriptionManager - BEGIN running 1 hub subscribers
16 Oct 2020 09:21:38,131 [scanTask-5] INFO com.nimsoft.discovery.server.hub.subscribe.HubSubscriptionManager - END running 1 hub subscribers
16 Oct 2020 09:21:38,142 [probeTask-8] DEBUG com.nimsoft.discovery.server.qos.origin.EnrichedOriginPollerTask - 0 S_QOS_DATA rows with enriched origins
16 Oct 2020 09:21:42,125 [scanTask-3] INFO com.nimsoft.discovery.common.nimbus.scan.QuickHubLocator - BEGIN gethubs for /S-DDCB-IM-PHUB_domain/S-DDCB-IM-PHUB_hub/S-DDCB-IM-PHUB/hub
16 Oct 2020 09:21:42,125 [scanTask-3] DEBUG com.nimsoft.discovery.common.nimbus.NonPooledNimRequestWrapper - Sending gethubs request to /S-DDCB-IM-PHUB_domain/S-DDCB-IM-PHUB_hub/S-DDCB-IM-PHUB/hub
16 Oct 2020 09:21:42,127 [scanTask-3] INFO com.nimsoft.discovery.common.nimbus.scan.QuickHubLocator - END gethubs for /S-DDCB-IM-PHUB_domain/S-DDCB-IM-PHUB_hub/S-DDCB-IM-PHUB/hub : 1 hubs found with status=0
16 Oct 2020 09:21:55,131 [scanTask-5] INFO com.nimsoft.discovery.server.hub.subscribe.HubSubscriptionManager - BEGIN running 1 hub subscribers
16 Oct 2020 09:21:57,131 [scanTask-5] INFO com.nimsoft.discovery.server.hub.subscribe.HubSubscriptionManager - END running 1 hub subscribers
16 Oct 2020 09:21:58,257 [probeTask-9] DEBUG com.nimsoft.discovery.server.agent.config.DiscoveryAgentConfigUpdateManager - BEGIN running config update workers for 1 discovery agents
16 Oct 2020 09:21:58,257 [probeTask-9] TRACE com.nimsoft.discovery.server.agent.config.DAVersionMismatchNotifier - Discovery Agent /S-DDCB-IM-PHUB_domain/S-DDCB-IM-PHUB_hub/S-DDCB-IM-PHUB/discovery_agent has valid version 20.30.
16 Oct 2020 09:21:58,276 [daConfigWorker-2] DEBUG com.nimsoft.discovery.server.agent.config.DiscoveryAgentConfigUpdater - Sending configuration to agent /S-DDCB-IM-PHUB_domain/S-DDCB-IM-PHUB_hub/S-DDCB-IM-PHUB/discovery_agent (version 20.30).
16 Oct 2020 09:21:58,276 [daConfigWorker-2] DEBUG com.nimsoft.discovery.common.nimbus.PooledNimRequestWrapper - Sending set_config request to /S-DDCB-IM-PHUB_domain/S-DDCB-IM-PHUB_hub/S-DDCB-IM-PHUB/discovery_agent
16 Oct 2020 09:21:58,505 [attach_socket] DEBUG com.nimsoft.discovery.server.agent.status.RecordDiscoveryAgentStatusCallback - Starting callback record_agent_status.
16 Oct 2020 09:21:58,505 [attach_socket] DEBUG com.nimsoft.discovery.server.agent.status.RecordDiscoveryAgentStatusCallback - Received agent status from /S-DDCB-IM-PHUB_domain/S-DDCB-IM-PHUB_hub/S-DDCB-IM-PHUB/discovery_agent with version 20.30.
16 Oct 2020 09:22:00,259 [probeTask-9] DEBUG com.nimsoft.discovery.server.agent.config.DiscoveryAgentConfigUpdateManager - END running config update workers for 1 discovery agents
16 Oct 2020 09:22:14,132 [scanTask-3] INFO com.nimsoft.discovery.server.hub.subscribe.HubSubscriptionManager - BEGIN running 1 hub subscribers
16 Oct 2020 09:22:16,132 [scanTask-3] INFO com.nimsoft.discovery.server.hub.subscribe.HubSubscriptionManager - END running 1 hub subscribers
16 Oct 2020 09:22:31,142 [probeTask-7] DEBUG com.nimsoft.discovery.server.qos.origin.EnrichedOriginPollerTask - 0 S_QOS_DATA rows with enriched origins
16 Oct 2020 09:22:33,131 [scanTask-1] INFO com.nimsoft.discovery.server.hub.subscribe.HubSubscriptionManager - BEGIN running 1 hub subscribers
16 Oct 2020 09:22:35,131 [scanTask-1] INFO com.nimsoft.discovery.server.hub.subscribe.HubSubscriptionManager - END running 1 hub subscribers
16 Oct 2020 09:22:52,130 [scanTask-3] INFO com.nimsoft.discovery.server.hub.subscribe.HubSubscriptionManager - BEGIN running 1 hub subscribers
16 Oct 2020 09:22:54,131 [scanTask-3] INFO com.nimsoft.discovery.server.hub.subscribe.HubSubscriptionManager - END running 1 hub subscribers

[Stefan Pivoda]

[Marius Nitu]

I'm not sure if it is related to your problem, but you also need some open ports in firewall. Also WMI must be allowed in forewall.

netsh advfirewall firewall add rule dir=in name ="WMI_FOR_CA_Agent_Deployment" program=%systemroot%\system32\svchost.exe service=winmgmt action = allow protocol=TCP localport=any

 

netsh advfirewall firewall add rule dir=in name ="OPEN_UDP_PORTS_FOR_CA_Agent_Deployment" action = allow protocol=UDP localport="135,137"

 

netsh advfirewall firewall add rule dir=in name ="OPEN_TCP_PORTS_FOR_CA_Agent_Deployment" action = allow protocol=TCP localport="135,137"

[Stefan Pivoda]

Hi Marius,
TCP/135 is clear for me for WMI.
but what is UDP/135, UDP/137 and TCP/137 for? if i hadnt overlooked anything, i didnt see these ports anywhere in the official documentation. are they really needed?
thank you,
stefan

[Marius Nitu]

Actually, UDP/135 might not be necessary. I thought it was necessary for WMI (DCOM).
Port 137 is necessary for NetBIOS.

EDIT: You might need only UDP/137 for NetBIOS. And you can remove the rules after the robot is installed.

[Stefan Pivoda]

and is NetBIOS needed for robot deployment?

[Marius Nitu]

From my experience yes.
In documentation is mentioned for discovery_agent.

Discovery_agent

DNS - port 53 NetBIOS - port 137 SSH - port 22 SNMP - port 161; configurable WMI - port 135 and others

https://techdocs.broadcom.com/us/en/ca-enterprise-software/it-operations-management/unified-infrastructure-management/20-3/installing/pre-installation-planning/firewall-port-reference.html

[Stefan Pivoda]

could you please help me with this issue?

i have couple of questions:
1. what is the workflow please? i didnt modify any xml or other file. is any modification needed?
2. how is the installation file transferred for windows? via SSH or WMI? because i didnt add any SSH credentials and didnt configure it on the target server either. if it's needed, where should i configure it in UIM?
3. any idea why no log message is about the deployment?


explanation:
i literally cant see any information in the ADE, discovery server logs about the deployment although i increased the loglevel to 5.  it seems that the robot deployment doesnt trigger any action in the background.

after clicking on deploy in the OC, a "deployment is in progress. your change will be reflected in the system in a few moments" popup message appers in OC.

the target server, where the robot should be deployed is a Windows 2012 server and it is directly connected to the primary HUB (windows as well and in the same domain).

thank you,
stefan

[Gene Howard]

Hi Stef,

Sorry, you are having an issue. Unfortunately, I no longer work on the UIM team and I have not had a chance to really look into 20.3
I would hope some others could help shed more light here.

In the past, the process was as follows.
1) you would run a discovery scope that was sent to a discovery_agent and then populated into the cm_computer_system table by the discovery_server.
or
1) you used an XML file to provide the information target machine information and connection information.

One of the two methods must be done to make sure you have the WMI or SSH credentials associated with the robot so the install can be done.
without the credentials, ADE can not connect and do an install

2) the next step would be for the ADE to take this information and connect to the system using WMI/NetBIOS for windows or SSH for Linux to install the robot.
3) With windows machines the ADE will try and create a network share and transfer the files to it.
4) then execute the installer from this location.

Are you getting any error messages or what exactly is happening?

​

------------------------------
Gene Howard
Principal Support Engineer
Broadcom
------------------------------

[David Michel]

Tried it in my lab and see the same thing, with the same results. 
Open a support case.

------------------------------
Support Engineer
Broadcom
------------------------------