DX Unified Infrastructure Management

 View Only
  • 1.  Probes not visible in IM console

    Posted Jun 25, 2019 04:07 AM
    Hi All,

    We have CA UIM 8.5.1 in our production environment.. We are facing issues on viewing probes in IM console for few of the robots.. Where in we are able to see the probes for the same robots, if it is moved to different HUB servers.

    Already logged case for the same - but no solution from support team. How do we fix it..

    I tried uninstalling IM console and reinstalled - still same issue


  • 2.  RE: Probes not visible in IM console

    Posted Jun 25, 2019 07:43 AM
    Are you sure that the needed ports are open:
    - between hub (in error) and robots? (bi-directional)
    - between hub (in error) and main hub? (bi-directional)


  • 3.  RE: Probes not visible in IM console

    Broadcom Employee
    Posted Jun 25, 2019 07:48 AM
    Could you please share some Screenshoots to show the Behavior for a better understanding?

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



  • 4.  RE: Probes not visible in IM console
    Best Answer

    Posted Jun 25, 2019 08:30 AM
    To check the ports remote into the hub and telnet to the robot using port 48002 and then from the robot to the hub.

    update robot & hub to 7.97

    Is the status icon for the robot green, red, or yellow?
    Does the same problem happen when using Admin Console?
    At the robot edit robot.cfg to set log level to 3, restart the service, and then check the controller log.

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



  • 5.  RE: Probes not visible in IM console

    Posted Jun 26, 2019 03:46 AM
    Hi,

    is it so that you see the robot in the IM (green) but when you click on the robot no probes are displayed on the right?
    If it looks the same for you, then I have seen it for some customers as well. In my opinion, the reason is an error in the internal address management in the hub.
    An update to hub 7.97 helped in all cases.