...

• opConfig installed and setup
• Understanding of opConfig terms and operation refer to 

  Excerpt Include
  opConfig User Manual opConfig User Manual

Configure access:  Adding Adding Credential Sets, Managing Credential Sets

...

Credentials for all connections made by opConfig are configurable from the opConfig GUI ONLY.  Before Before anything else you need to create sets of credentials to access you devices.   At this point in time, opConfig supports only Telnet and SSH, and for SSH only password-based authentication is supported.

...

A credential set has to specify a User Name property, which is used when logging in to the nodes the set applies to. At this time, opConfig supports only password-based authentication at the node, and the Password property of the credential  credential set establishes the primary password for this user name.

...

• On Cisco IOS devices, this password  password is used with the enable command.
• With personality bash (the default for Unix-like systems), the command sudo is used to become the superuser. Sudo therefore needs to be installed and configured on such nodes, and the User Name in question needs to be authorized for sudo.

Naturally not all commands require elevated privileges; see the section on Command Sets for how to determine and configure those.

Please note that the Credential  Credential Set editing dialogs never show existing passwords (or their legth length or existence); You can only overwrite password entries. All credential sets are stored in the database in encrypted form.

...

• System menu
  • Edit Nodes.
    
    
    • "Import new Nodes from NMIS" or   "Add Node"   -  These These let you create new node records either automatically or manually.  

If you successfully import the node from NMIS you should only need to add the credential set and the transport protocol (which are in the connection tab).  Import Import generally works for "LinixLinux" like devices and for Cisco devices.  For For all other device types you simply need to add some details by hand.  You You will see what configuration you MUST still add displayed as part of the "Edit Node" screen.  

The problem reports are fairly self-explanatory (and clickable).

...

1. General TAB - This is generic information about the device and is the information imported from NMIS / OpenAudit.   Only the host entry needs to be correct here, and it must be a usable FQDN or IP address the rest is informational only.
2. Connection TAB -  To To connect to a node, opConfig needs to know some information about it
   1.  Personality this is the CLI Parsing to use to enable the issuing of commands e.g. line endings, prompts etc.  The Personality includes information about the prompts, line-ending conventions etc. a node is subject to; for example, the 'ios' personality handles understanding the > prompt and  "enable" command and "bash" understands shell prompts.  The personalities supported are available in the drop down.
   2.  CredentialSet - NOT automatic and needs to be set - authentication and authorization in the form of the access credential set created earlier.
   3. Transport (Telnet or SSH) - NOT automatic and needs to be set Also note this cannot get flagged as not being changed in the Configuration Problems window so do check it.
3. OS info TAB -  Once connected to a node we need to know the OS and maybe version, subversion, platform in use to select the right commands to issue and how to parse the command results.  This where COMMAND SETS ("command_sets.nmis" file) that opConfig uses, makes association between the OS and maybe a  version and maybe a major release or train and the command to issue and how to parse it. 
   1. These fields should be automatically populated if your device was discovered by NMIS or OpenAudit and if they are Cisco IOS or Linux devices

   2. The OS field and potentially the version and other fields must match the 'os' => and any 'version' =>   fields in the command_sets.nmis file.

   3. See the command sets section later and have a look in the file if you want to know what os and version fields will work.  If the import did not get results you can try the following: for Cisco IOS typically if you put OS as "IOS" and version as "12.2" you will get results and Linux OSs use just OS as "Linux"

...