Smarts NCM: Device AutoDiscovery job fails for a device; Job summary details show job "Completed with warning" and "SSH Credentials are not Valid"; **MOBILE CODE** Command error seen in commmgr.log and autodisc.log files

Products

• VMware Smart Assurance

Issue/Introduction

Symptoms:


Smarts NCM device AutoDiscovery operation fails for a device.

 

The following conditions, events or system behaviors may be observed with this issue:

• Smarts NCM AutoDiscovery job summary appears similar to the following:

Total number of tasks                 : 1

 

Number of tasks completed successfully: 0

Number of tasks completed with warning: 1

Number of tasks completed with failure: 0

 

Tasks completed with warning:

[1877443), ]

 

Tasks completed with failure:

[]

-------------------------------- Job Details ------------------------------------

 

Job Number        : 1877442

Job Name          : AutoDiscovery Switches-AD1

Job Description   : test

Job Owner         : 31506([email protected])

Job Status        : Completed with Warning

Job Run Option    : Run Upon Approval

Target Time       : Tue, 9 Jul 2013 13:05:51 -0400

Approved By       : system

Preserve Order    : No

Network Name      : Switches

Job Priority      : High

Last Updated by   : system

Update Comment    : Completed with a warning

 

-------------------------------- Job History ------------------------------------

-------------- Task 1877443 --------------

Status: Completed with Warning

Results:

Action completed successfully...

Auto Discovery start...

Loading the configuration...

Loading the configuration...done

Locating devices...

Finding new devices by ping sweep...

Executing pingSweep: subRange 10.1.10.1 #1 of 1

Range #1/1 10.1.10.1: found 2 devices out of 2 requests (0 addresses failed)

>>> (10.1.10.1) Discovering drivers and protocols for device

  ---- RO community (Test-SNMP String) is invalid

  ---- RW community (Test-SNMP String) is invalid

  ---- RO community (Test-SNMP Public) is invalid

  ---- RW community (Test-SNMP Public) is invalid

!!! No Valid SNMPV1 Community Strings, check the R/O and R/W community strings.

  ---- RO community (Test-SNMP String) is invalid

  ---- RW community (Test-SNMP String) is invalid

  ---- RO community (Test-SNMP Public) is invalid

  ---- RW community (Test-SNMP Public) is invalid

!!! No Valid SNMPV2 Community Strings, check the R/O and R/W community strings.

+++ Device authenticated Global Account using SSH protocol

>>> Discovering Privilege Passwords using driver #100:Generic Device

---- Privilege Password voybas failed to authenticate at level 15

---- Device did not respond to SSH Global Account authentication

---- Device did not respond to SSH Account Priv authentication

!!! SSH Credentials are not Valid

---- Device did not respond to SSH Global Account authentication

---- Device did not respond to SSH Account Priv authentication

!!! SSH Credentials are not Valid

---- Device did not respond to SSH Global Account authentication

---- Device did not respond to SSH Account Priv authentication

!!! SSH Credentials are not Valid

---- Could not discover driver using SSH

=================================================

(10.1.10.1) Valid Credentials Found, but could not determine driver for device

Finding new devices by ping sweep...done

Locating devices...done

• MOBILE CODE messages similar to the following are seen in commmgr.log for Smarts NCM environment:

Jul 09 13:05:52 3972/ad(1877442)#1: AutoDisc Requested (8013733895517398): ad Accounts=global,1raoCqIQVqPNX+7seqFzahaM0QZEF2Hh,0a01075f5a9dd83f156bff663...
Jul 09 13:05:52 3972/ad(1877442)#4: 50000012: **MOBILE CODE** Command
Jul 09 13:05:52 3972/ad(1877442)#4: Info: Waiting for status file, will try again...
Jul 09 13:05:53 3972/ad(1877442)#3: AutoDiscovery: Status(0): Unknown
Jul 09 13:05:53 3972/ad(1877442)#4: Info: Waiting for status file, will try again...
Jul 09 13:05:59 3860/30#2: Queuing async cmd 1013733895547399 to **MOBILE CODE**...

• MOBILE CODE messages similar to the following are seen in autodisc.log for Smarts NCM:

Jul 09 13:05:50 :5444/10.1.10.1@1/SSH#4: Executing function "Cisco IOS Router::updateDevice"...

Jul 09 13:05:50 :5444/10.1.10.1@1/SSH#1: Error: RunTimeContext::**MOBILE CODE**: Can't find function updateDevice in driver #1("Cisco IOS Router") (RunTimeContext.cpp#403)

Jul 09 13:05:50 :5444/10.1.10.1@1/SSH#4: DeviceObj::updateDeviceFromDriver: 10.227.10.1: SCRIPT FAILED - optional

Environment

VMware Smart Assurance - NCM

Cause

A crypto pki token configuration is being used for the device authentication. If the device has a crypto pki token configuration, Smarts NCM will not be able to authenticate with the device.

Resolution

To address this issue, remove or disable the  crypto pki token configuration on the device, and run the AutoDiscovery job again.