search cancel

How can I verify Nimsoft Robot and Probe versions from the Server's Nimsoft Directory

book

Article ID: 203417

calendar_today

Updated On:

Products

DX Unified Infrastructure Management (Nimsoft / UIM)

Issue/Introduction

How can I verify Nimsoft Robot and Probe versions from the Server's Nimsoft Directory without looking at Infrastructure Manager.

Environment

Release : 20.1

Component : UIM - CDM WITH IOSTAT

Resolution

The only file that shows the probe's info is the probe log.

For example, when you start the cdm probe it will show:

Oct 25 07:49:58:792 [5388] cdm: ****************[ Starting ]**************** 
Oct 25 07:49:58:792 [5388] cdm: cdm 6.42 

Another way is via callback (probe Utilily) 

 

To show all the PU commands just type from \Nimsoft\bin>pu.exe

<install folder>\Nimsoft\bin>pu.exe
Nov 16 12:00:43:802 2 pu: _nimInit
Nov 16 12:00:43:806 2 pu: nimCharsetSet() - charset=

Probe Utility.  Issues a callback from one probe to another.

Usage:
  pu [options] <nim-address> [<command> [<data>...]]
  pu [options] -H host [-P port] [-c controller_host [-e controller_port]] [<command> [<data>...]]

    <nim-address>        Name of the probe receiving the callback, must be fully qualified if
                           not on the local robot.  Will issue from the local controller probe.

                           Example of a fully qualified nim-address:
                                    "/nim-domain/nim-hub/nim-robot/controller".

    <command>            Name of the callback to run on the receiving probe.  If not specified,
                           lists the available commands on the receiving probe.
    <data>               Series of arguments to pass to the callback.  If required arguments
                           are not specified, user will be asked interactively.
    -V                   Print the version of the Probe Utility tool.
    -i                   Run in interactive mode.
    -u user              NimBUS username.
    -p password          NimBUS password.
    -t sec               Timeout in seconds.
    -d level             Debug level.
    -L                   List the available commands on the receiving probe.
    -I                   Show the receiving probe information.
    -R                   Restart the receiving probe.
    -S                   Stop the receiving probe.
    -H host              hostname or ip of the probe receiving the callback
    -P port              port number of the probe receiving the callback (default 48000)
    -c controller_host   hostname or ip of the probe issuing the callback (default localhost)
    -e controller_port   port number of the probe issuing the callback (default 48000)


For example, to show the cdm probe version:

C:\Program Files (x86)\Nimsoft\bin>pu -u administrator -p <Type_password_here> cdm get_info Version
Nov 16 11:54:41:645 2 pu: _nimInit
Nov 16 11:54:41:649 2 pu: nimCharsetSet() - charset=
Nov 16 11:54:41:655 0 pu: Failed to read a valid probe_crypto_mode from controller. Assuming pre-FIPS and using TWO_FISH
======================================================
Address: cdm Request: get_info
======================================================
CheckTime PDS_I 11 1605556482
Hostname PDS_PCH 14 lvntest001842
MachineType PDS_PCH 8 Windows
OsName PDS_PCH 45 Windows Server 2012 Standard Edition, 64-bit
OsVersion PDS_PCH 12 Build 9200
OsRelease PDS_PCH 9 6.2.9200
Processors PDS_I 2 4
PhysicalMemory PDS_I 6 16383
UptimeDays PDS_I 2 6
UptimeHours PDS_I 2 5
UptimeMinutes PDS_I 3 34
UptimeSeconds PDS_I 2 6
CpuLastCheck PDS_I 11 1605556347
CpuInterval PDS_I 4 300
MemLastCheck PDS_I 11 1605556347
MemInterval PDS_I 4 300
DisksLastCheck PDS_I 11 1605556047
DisksInterval PDS_I 4 900
Version PDS_PCH 5 6.42
Date PDS_PCH 12 Apr 13 2019
Loglevel PDS_I 2 0
RobotName PDS_PCH 14 lvntest001842

You can create your own scripts based no your needs.