Smarts NPM: Probe error: netSSH2 encountered a problem
book
Article ID: 332061
calendar_today
Updated On:
Products
VMware Smart Assurance
Issue/Introduction
Symptoms:
There are number of Perl related errors that can appear with Network Protocol Manager for probes of BGP v3 and OSPF v3. These protocols do not support SNMP and must be done via CLI which uses a Perl script to connect via SSH.
Some of the examples of error messages that can be seen are:
Exited with status -1: Probe error: netSSH2 encountered a problem! Protocol major versions differ: 2 vs. 1 at D:/InCharge/NPM/smarts/perl/5.16.2/SMARTS/CLI/Remote/PerlSSH.pm line 141. result FAILED changed TRUE discoveryError Probe ready to run Child process exited with status 72057594037927935 ($?) objectName SNMPAgent-dustuktk5c7232
Exited with status -1: Probe error: netSSH2 encountered a problem! SSH2 is the only supported protocol under MSWin32! at D:/InCharge/NPM/smarts/perl/5.16.2/lib/Net/SSH/W32Perl.pm line 57, line 1. result FAILED changed TRUE discoveryError Probe ready to run Child process exited with status 72057594037927935 ($?) objectName SNMPAgent-cusqui001cn3ks
Exited with status -1: Probe error: netSSH2 encountered a problem! Can't use an undefined value as a symbol reference at D:/InCharge/NPM/smarts/perl/5.16.2/lib/Net/SSH/Perl.pm line 304. result FAILED changed TRUE discoveryError Probe ready to run Child process exited with status 72057594037927935 ($?) objectName SNMPAgent-zcnshadinc6n01
Environment
VMware Smart Assurance - SMARTS
Cause
While the error messages are somewhat vague, they all reference an inability to access the device in question using SSH v2. Either the device is not responding to SSH at all or will not negotiate with SSH v2. These error indicate a problem that should be corrected on the device to make sure that SSH v2 connections can be made.
Resolution
Verify SSH v2 connectivity and support on the device. If this information is not readily available, consult the vendor of the specific device.