Direkt zum Inhalt

Command line way to display the version and build level of the VMware appliance?

Thread solved

We're just starting our Acronis Backup 12.5 on-premise deployment.  Due to government regulations we have tight security requirements.  One of them is to prove the there has been no unwanted software installed.  On typical servers we install the Tripwire agent to monitor software changes and ports and services.  On appliances or other locked down equipment, we have Tripwire SSH or some other CLI into the device and issue a command to display the firmware or OS level.  It compares it to the  baseline defined in Tripwire to verify nothing has changed.

On the Acronis VMware appliance, is there a command to display the version and build level?  and is there an SSH interface available to issue the command from?

Thanks,

Cathy

0 Users found this helpful
frestogaslorastaswastavewroviwroclolacorashibushurutraciwrubrishabenichikucrijorejenufrilomuwrigaslowrikejawrachosleratiswurelaseriprouobrunoviswosuthitribrepakotritopislivadrauibretisetewrapenuwrapi
Beiträge: 22
Kommentare: 3800

Hi Cathy,

You can get these details from any backup agent including Agent for VMware (Virtual Appliance) via command line "acrocmd" utility. Here's an example of accomplishing the task (basing on https://www.acronis.com/en-us/support/documentation/AcronisBackup_12.5_Command_Line_Reference/index.html#37074.html):

1) Install Command Line utility onto some machine, for example where Acronis Management Server is running (usually CLI is installed by default)

2) Issue the following command via command prompt:

acrocmd list disks --host=[IP_address_of_the_appliance] --credentials=[Credentials_to_connect_to_vSphere_used_by_this_appliance] --log=c:\temp\log.txt

Example:

acrocmd list disks --host=10.250.10.10 --credentials=administrator@vsphere.local,p@ssw0rd --log=c:\temp\log.txt

Where 10.250.10.10 = IP address of the appliance. The c:\temp\log.txt will contain information about the version of the agent which executed the command. "list disks" command will produce empty output, since appliance itself doesn't have any disks which can be listed, so this command is used only to generate the log file where version/build of the agent can be checked from.

Example of log.txt outputs:

<list_disks>
  <name>list disks
  </name>
  <raw_command>list disks --host=10.250.10.10 --credentials=* --log=c:\123\log.txt
  </raw_command>
  <options>
    <option>
      <name>host
      </name>
      <values>
        <value>10.250.10.10
        </value>
      </values>
    </option>
    <option>
      <name>credentials
      </name>
      <values>
        <value>*
        </value>
      </values>
    </option>
    <option>
      <name>log
      </name>
      <values>
        <value>c:\123\log.txt
        </value>
      </values>
    </option>
  </options>
  <output_data>
    <sys_info>
      <cmd_client>
        <major_version>12
        </major_version>
        <minor_version>5
        </minor_version>
        <build>13400
        </build>
      </cmd_client>
      <server>
        <major_version>12
        </major_version>
        <minor_version>5
        </minor_version>
        <build>13400
        </build>

      </server>
    </sys_info>
    <total_time>00:00:01
    </total_time>
  </output_data>
</list_disks>

The bolded parts above contain the exact version of the agent (under <server> section), which is 12.5.13400 in the above example, so these outputs can be analyzed by 3rd party application.

It is also possible to connect to appliance via SSH, however SSH access must be enabled from local appliance console first + keeping SSH access opened forever might not be secure enough. Practically SSH is enabled only temporarily for troubleshooting purposes:

1) Open appliance VM console in vSphere client

2) Switch to appliance command prompt via Ctrl+Shift+F2 (switch back to GUI can be done via Alt+F1)

3) Issue /bin/sshd command which will enable SSH access

4) To connect over SSH you can use root/root login/password (these credentials cannot be changed)

Thank you.

I'll pass that on to the automation team but I would think they should be able to make that work.

Thank you!

Cathy