Unable to execute remote pu command: _command failed: communication error
search cancel

Unable to execute remote pu command: _command failed: communication error

book

Article ID: 215417

calendar_today

Updated On:

Products

DX Unified Infrastructure Management (Nimsoft / UIM)

Issue/Introduction

We are not able to make remote pu command as we get the error _command failed: communication error

For example, we are trying to clear niscache on a remote robot running the command from the primary hub (UIM_hub) to remote robot (ROBOT1)

C:\Program Files (x86)\Nimsoft\bin>pu -u administrator -p p@ssword123 /UIM_domain/UIM_hub/ROBOT1/controller  _nis_cache_clean ROBOT1
May 18 13:18:44:159 2 pu: _nimInit
May 18 13:18:44:164 2 pu: nimCharsetSet() - charset=
May 18 13:18:44:173 0 pu: Failed to read a valid probe_crypto_mode from controller. Assuming pre-FIPS and using TWO_FISH
_command failed: communication error

Environment

Release : 20.3+
Component : UIM - Probe Utility

Cause

The _command failed: communication error can be seen if:

  • The probe address (eg. /UIM_domain/UIM_hub/ROBOT1/controller) is incorrect
  • There is some sort of networking related issue

Resolution

There are several approaches that may resolve this issue.

  • Verify if the address mentioned in the command is correct and that the remote robot is in the same domain where the command is executed.
  • Verify that the command will run for other robots
  • Verify if the command will run from IM running on the same hub where the command line is being run

Additional Information

  • For debugging purposes it is possible to add -d 5 to the command to obtain additional information about the error.
    Example:
    C:\Program Files (x86)\Nimsoft\bin>pu -d 5 -u administrator -p p@ssword123 /UIM_domain/UIM_hub/ROBOT1/controller  _nis_cache_clean ROBOT1

  • The error: Failed to read a valid probe_crypto_mode from controller. Assuming pre-FIPS and using TWO_FISH can be safely ignored

  • Run Probe Commands from a Command Prompt (broadcom.com)