DX Unified Infrastructure Management

  • Private Community

  • 1.  ADE discovery

    Posted Dec 23, 2015 09:54 AM
      |   view attached

    Hi,

     

    Am trying to discover a device through ADE but getting error. attached is the log..

     

    please help me to fix this.

    Attachment(s)

    zip
    automated_deployment_engine.log.zip   59 KB 1 version


  • 2.  Re: ADE discovery

    Posted Dec 29, 2015 09:06 AM

    please help.



  • 3.  Re: ADE discovery

    Broadcom Employee
    Posted Dec 29, 2015 07:52 PM

    Have you followed the instruction found in this video?

    ADE Linux Robot Installation - YouTube

     

    What is this "ReleaseID-3251.zip" file?

     

    12182015 10:48:40,883 [main] INFO  NimDBProviderBase - post: successfully initialized driver: org.h2.Driver

    12182015 10:49:40,538 [main] INFO  AutomatedDeploymentEngineProbe - log4j: log level set to INFO. NimLogLevel=3

    12182015 10:49:40,539 [main] INFO  ArchiveManager - Setting Archive path to E:\Nimsoft\archive

    12182015 10:49:40,581 [main] INFO  ArchiveManager - Scanning E:\Nimsoft\archive for packages...

    12182015 10:49:51,491 [main] INFO  AutomatedDeploymentEngineProbe - ****************[ ADE Booting ]****************

    12182015 10:49:51,492 [main] INFO  AutomatedDeploymentEngineProbe - automated_deployment_engine

    12182015 10:49:51,492 [main] INFO  AutomatedDeploymentEngineProbe - Build: 791

    12182015 10:49:51,492 [main] INFO  AutomatedDeploymentEngineProbe - Archive Location E:\Nimsoft\archive

    12182015 10:49:51,503 [pool-2-thread-1] INFO  ArchiveWatcher - Starting file watcher for directory E:\Nimsoft\archive

    12182015 10:49:51,582 [main] INFO  H2DBProvider - H2 DB script execution successful.

    12182015 10:49:51,709 [main] INFO  ADEH2Manager - Successfully created new database schema...

    12182015 10:49:51,985 [main] INFO  AutomatedDeploymentEngineProbe - DB connection string : jdbc:h2:file:automated_deployment_engine;AUTO_SERVER=true

    12182015 10:49:52,005 [main] INFO  AutomatedDeploymentEngineProbe - ****************[ ADE Started ]****************

    Dec 18 10:49:52:010 [main, automated_deployment_engine] ****************[ Starting ]****************

    Dec 18 10:49:52:010 [main, automated_deployment_engine] 8.20

    Dec 18 10:49:52:010 [main, automated_deployment_engine] CA Technologies

    Dec 18 10:49:52:015 [main, automated_deployment_engine] port=48009

    Dec 18 10:49:52:153 [main, automated_deployment_engine] Login to NimBUS is OK

    12182015 11:11:08,756 [pool-2-thread-1] WARN  ArchiveWatcher - [Event -> ENTRY_CREATE] File ReleaseID-3251.zip is not a valid zip file

    12182015 11:11:09,191 [pool-2-thread-1] WARN  ArchiveWatcher - [Event -> ENTRY_MODIFY] File ReleaseID-3251.zip is not a valid zip file

     

    Are you using the ADE to deploy a Solaris robot?

    Is this a Solaris running on AMD processor? Is this a Solaris running on Sparc processor?

     

    12232015 19:50:27,905 [pool-4-thread-2] FATAL AbstractActor - Error encountered during distribution of robot_sol.zip to target 10.236.249.40: (4,Install Failure)

    com.nimsoft.ADE.core.DeploymentException: java.io.IOException: Error installing solaris robot on 10.236.249.40. Command was 'pkgadd -d /tmp/nimsoft-robot-amd64  -a /tmp/ask < /tmp/input'. Return code is 1

      at com.nimsoft.ADE.actor.HostActor.install(HostActor.java:43)

      at com.nimsoft.ADE.actor.HostActor.install(HostActor.java:20)

      at com.nimsoft.ADE.actor.AbstractActor.run(AbstractActor.java:76)

      at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)

      at java.util.concurrent.FutureTask.run(Unknown Source)

      at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)

      at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)

      at java.lang.Thread.run(Unknown Source)

    Caused by: java.io.IOException: Error installing solaris robot on 10.236.249.40. Command was 'pkgadd -d /tmp/nimsoft-robot-amd64  -a /tmp/ask < /tmp/input'. Return code is 1

      at com.nimsoft.ADE.strategy.deployment.robot.SolarisStrategy$Install.execute(SolarisStrategy.java:93)

      at com.nimsoft.ADE.strategy.deployment.robot.SolarisStrategy$Install.execute(SolarisStrategy.java:55)

      at com.nimsoft.ADE.strategy.deployment.AbstractDeploymentStrategy.execute(AbstractDeploymentStrategy.java:100)

      at com.nimsoft.ADE.actor.AbstractActor.push(AbstractActor.java:65)

      at com.nimsoft.ADE.actor.HostActor.install(HostActor.java:37)

      ... 7 more

     

    Thanks,

    Silvio



  • 4.  Re: ADE discovery

    Posted Dec 30, 2015 01:55 AM

    Hi,

     

    I have done the same as instructed in video. But still no luck.

     

    Attached host file and notepad created after deployment of file in ADE.( not sure of Release file which is mentioned above).

     

    please help.( client is solaris machine -Solaris sparc 10)

     

    <hosts>

     

     

    <host>

      <profile>Linux</profile>

      <arch>64</arch>

      <hostname>10.236.249.40</hostname>

      <username>root</username>

      <password>****</password>

      <domain>BOXISERVER_domain</domain>

      <hubip>10.236.246.27</hubip>

      <hub>BOXISERVER_hub</hub>

      <hubrobotname>BOXISERVER</hubrobotname>

      <hubport>48002</hubport>

    </host>

     

     

    </hosts>

     

     

     

    DOMAIN=BOXISERVER_domain

    HUBIP=10.236.246.27

    HUB=BOXISERVER_hub

    HUBROBOTNAME=BOXISERVER

    HUBPORT=48002

    FIRST_PROBE_PORT=

    SECONDARY_DOMAIN=

    SECONDARY_HUB=

    SECONDARY_HUBROBOTNAME=

    SECONDARY_HUBIP=

    SECONDARY_HUBPORT=

    SECONDARY_HUB_DNS_NAME=

    SECONDARY_ROBOTIP_ALIAS=

    ROBOT_MODE=

    ROBOTNAME=

    ROBOTIP=

    ROBOTIP_ALIAS=

    CONTROLLER_PORT=

    SPOOLER_PORT=

    HUB_DNS_NAME=

    HUBDOMAIN=

    OS_USER1=

    OS_USER2=

    SET_QOS_SOURCE=

    SYSTEM_UPTIME_QOS=

    AUTOREMOVE=

    DEFAULT_PRIORITY_LEVEL=

    PROXY_MODE=

    PROXY_LOG=

    HUB_UPDATE_INTERVAL=

    LOGLEVEL=

    LOGSIZE=

    LOGFILE=

    CONFIG_LOCK_TIMEOUT=

    PORT_ALIVE_CHECK=

    PORT_ALIVE_INCLUDE_LOCAL=

    STARTUP_TIMEOUT=

    SUSPEND_ON_LOOPBACK_ONLY=

    TEMPORARY_HUB_BROADCAST=

    DO_NOT_BROADCAST=

    UNMANAGED_SECURITY=

    SEND_ALIVE=

    ALARM_LEVEL_COMFAIL_RESTART=

    ALARM_LEVEL_DISPATCH_ERROR=

    ALARM_LEVEL_MAX_RESTARTS=

    ALARM_LEVEL_START_ERROR=

    ALARM_LEVEL_SUSPENDED=

    ALARM_LEVEL_TIMED_NOT_FINISHED=

    ALARM_LEVEL_TIMED_ERROR_RETURN=

    ALARM_LEVEL_UNREGISTER=

    ALARM_LEVEL_REQUEST_ERROR=

    ALARM_LEVEL_POSTINSTALL=

    AUDIT=

    AUDIT_MAX_CONFIG_SIZE=

    AUDIT_CHECKPOINT_COUNT=

    ALARM_TIMEOUT=

    WAIT_AFTER_UNREGISTER=

    TZ_OFFSET=

    CONFIG_LOCKING=

    CAPTURE_OUTPUT=

    DEFAULT_FAIL_WINDOW=

    MAX_RESTARTS=

    ORIGIN=

    IP_VERSION=



  • 5.  Re: ADE discovery

    Broadcom Employee
    Posted Dec 30, 2015 05:56 AM
    If you are deploying a robot to Solaris (SunOS) servers via the automated_deployment_engine (ADE) probe, when specifying the architecture you should only use sparc9 if the processor type of the target Solaris server is sparc.  You can determine the processor type by executing the following command from a login prompt on the target Solaris server:

     

    uname -p

     

    The correct XML directive here would be:
     <arch>sparc</arch>

    For other Solaris processor types, you would use either 32 or 64 depending on whether the server is a 32- or 64-bit processor.  You can determine this by executing the following command from a login prompt on the target Solaris server:

    isainfo -v

     

    The correct XML directive here would be:
    <arch>32</arch> or
    <arch>64</arch>


  • 6.  Re: ADE discovery

    Posted Dec 11, 2017 12:05 PM

    Hi,

     

    You have indirectly solved my issue, I got a Java error when trying to deploy but your XML example has fixed it!

     

    So thank you

     

    I now have errors on the next step (6,Connection Failure) in the logs.  I'm not sure what connectivity is required for ADE to work so I've asked support.

     

    Thanks!



  • 7.  Re: ADE discovery

    Posted Feb 20, 2019 08:19 AM

    I didn't have the time to sort this with Support, I'll get round to it one day!

     

    Here's my error if anyone has any suggestions? FYI, I've checked the username/password

     

    Cheers,ADE Error comms error