Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

Smarts NCM: How to perform autodiscovery in NCM using Command Line? (304969)

Last Updated: 5/29/2020Categories: How toTotal Views: 2365Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Resolution

How to do auto discovery of Devices in NCM via command line?

Navigate to $VOYENCE_HOME/tools/bulk-import, and press Enter.

1. At the command prompt, enter runCmd.sh, then press Enter.
For Windows, enter runCmd.pl, then press Enter.

At the next command prompt, enter your User Name and Password.  See the following prompts:

Enter User Name: where you then enter the user name

Enter Password: where you enter the password

This is the same User Name and Password you use to access the NCM application. The Command Line Interface feature is now started by displaying a command prompt.
cmd>.

2. Here is the auto discovery Command you need to enter:
seedAD <network name> <device server name> <Discovery type> hostfile <credentials>

3. Make sure the format and syntax is exactly as shown in the following example.
cmd > seedAD Cust-1 devserver1 ping-sweep hosts "global:Acct-1,ppwd"

NOTES:
Discovery type can be one of the following:
- ping-sweep
- snmp-sweep
Hostfile is a tab separated format, similar to /etc/hosts. See examples.tar in the $VOYENCE_HOME/tools/bulk-import directory to see examples.
Credentials can be either global/network credentials.
- global - global credentials have a global: prefix.
- Network - network credentials are those that belong to the network provided in the command
If the credential names (in either global or network) contains any spaces or other special characters, you must enclose the name using double quotes ("). For example, if the global name is global: cred name, cred name2, then the name would be entered as: "global:cred name,cred name2".

- If you have multiple credentials to be entered, you will need to add the credentials using below command and attached file
cmd> importCredentials global input-file.csv false

Fill all credentials in attached .csv file and place the file in <Basedir>/smarts-ncm/tools/bulk-import.

Ex:
cmd > importCredentials global input-file.csv false

Creating Account:Account2
Creating Privilege Password:Privilege2
Creating Community String:SNMP5
Creating Community String:SNMP6
Creating Community String:SNMP7

4. Press Enter.
Here is the output you will see on executing this command:

Added the CS:MSP-CSto AD
Added the Account:Account 1to AD

**************AD Entry Details************

NameAUTODISC-CMDLINE-Tue Sep 28 11:32:20 CDT 2004

Account Identities[Account 1]

CS Identities[MSP-CS]

**************AD Entry Details************

Ex:
cmd > seedAD Test bngsmartsncm1.lss.emc.com snmp-sweep hosts "global:Account2,global:Privilege2,global:SNMP5,global:SNMP6,global:SNMP7"
Added the Account:Account2 to AD
Added the PrivPass:Privilege2 to AD
Added the CS:SNMP5 to AD
Added the CS:SNMP6 to AD
Added the CS:SNMP7 to AD
**************AD Entry Details************
NameAUTODISC-CMDLINE-Tue Sep 16 22:44:03 IST 2014
Account Identities: Account2
PrivPass Identities: Privilege2
CS Identities: SNMP5,SNMP6,SNMP7
SnmpV3 Identities:

**************AD Entry Details************
cmd >

5. In a separate telnet window, verify your command results by entering change directory (cd) to $VOYENCE_HOME/logs, then pressing Enter. The log file review is commandLineUtil.log. You can also go to the System Administrator screens (in Network Configuration Manager) to verify Auto Discovery.

Ex:

6. If you have completed command line auto discovery and no further actions are needed, enter quit at the command line, then press Enter. You are now logged off of Network Configuration Manager.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

input-file.csv

Additional Resources

KB
•
End Of General Availability of the Free vSphere Hypervisor (ESXi 7.x and 8.x) (2107518)

Result 1 of 1

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

Related Versions:

VMware Smart Assurance - NCM

Take Our Survey

Support Assistant