Smarts NCM: Receiving an error while running Autodiscovery Using Command Line, but discovery from Smarts NCM console succeeds
search cancel

Smarts NCM: Receiving an error while running Autodiscovery Using Command Line, but discovery from Smarts NCM console succeeds

book

Article ID: 330952

calendar_today

Updated On:

Products

VMware Smart Assurance

Issue/Introduction

Symptoms:




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

  • Smarts NCM discovers the device successfully when discovery is initiated on Smarts NCM console interface.
  • The following error is received in the commandLineUtil.log when using autodiscovery through the command line:

2013-11-11 03:48:06,145 INFO [com.powerup.configmgr.util.commandline.ad.NewScheduleAutoDiscCmd] IncludeRanges from hostsFile=[xx.xx.xx.xx, yy.yy.yy.yy]
2013-11-11 03:48:06,145 INFO [com.powerup.configmgr.util.commandline.ad.NewScheduleAutoDiscCmd] IncludeRanges from hostsFile=[xx.xx.xx.xx, yy.yy.yy.yy]
2013-11-11 03:48:06,145 INFO [com.powerup.configmgr.util.commandline.ad.NewScheduleAutoDiscCmd] NewScheduleAutoDiscCmd:credentials=[global:TAC-MIB, PRIV-MIB, SNMP Community (j4m35), SNMP Community (b1gb3n)]
2013-11-11 03:48:06,145 INFO [com.powerup.configmgr.util.commandline.ad.NewScheduleAutoDiscCmd] NewScheduleAutoDiscCmd:credentials=[global:TAC-MIB, PRIV-MIB, SNMP Community (j4m35), SNMP Community (b1gb3n)]
2013-11-11 03:48:06,170 INFO [com.powerup.configmgr.util.commandline.ad.NewScheduleAutoDiscCmd] Found network...
2013-11-11 03:48:06,170 INFO [com.powerup.configmgr.util.commandline.ad.NewScheduleAutoDiscCmd] Found network...
2013-11-11 03:48:06,178 ERROR [com.powerup.configmgr.util.commandline.ad.NewScheduleAutoDiscCmd] Unable to find the deviceServerIDX by name:Deviceserver9
java.rmi.ServerException: RemoteException occurred in server thread; nested exception is:
java.rmi.RemoteException: Caller not authenticated
at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:334)
at sun.rmi.transport.Transport$1.run(Transport.java:159)
at java.security.AccessController.doPrivileged(Native Method)
at sun.rmi.transport.Transport.serviceCall(Transport.java:155)
at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:535)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(TCPTransport.java:790)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:649)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
at sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(StreamRemoteCall.java:255)
at sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:233)
at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:142)
at com.powerup.configmgr.deviceservice.daemon.DevSrvDaemonProxy_Stub.getAccessServers(Unknown Source)
at com.powerup.configmgr.util.commandline.ad.NewScheduleAutoDiscCmd.getDeviceServerIDX(NewScheduleAutoDiscCmd.java:354)
at com.powerup.configmgr.util.commandline.ad.NewScheduleAutoDiscCmd.execute(NewScheduleAutoDiscCmd.java:99)
at com.powerup.configmgr.util.commandline.CommandController.processCommand(CommandController.java:155)
at com.powerup.configmgr.util.commandline.CommandController.commandPrompt(CommandController.java:126)
at com.powerup.configmgr.util.commandline.CommandController.main(CommandController.java:75)

 

  • Smarts NCM Device Server name is correct but the log still shows the following:

[com.powerup.configmgr.util.commandline.ad.NewScheduleAutoDiscCmd] Unable to find the deviceServerIDX by name:Deviceserver9

java.rmi.ServerException: RemoteException occurred in server thread; nested exception is:
java.rmi.RemoteException: Caller not authenticated"


Environment

VMware Smart Assurance - NCM

Resolution

Attached to this article in the CommandLineUtil.zip file, which contains a jar file with the fix for the error message above. To implement the fix, do the following:
  1. Make a backup copy of the CommandLineUtil.jar from $VOYENCE_HOME/tools/bulk-import directory.
  2. Copy the attached jar to the $VOYENCE_HOME/tools/bulk-import directory
  3. Change the permission of the attach jar to the following:
"chown root:voyence $VOYENCE_HOME/tools/bulk-import/CommandLineUtil.jar"
  1. Run the script: ./runCmd.sh


Powered by Wolken Software