Product Compatibility

Refer to product compatibility to determine supported Operating Systems and Database Versions.

Download opConfig here - https://opmantek.com/network-management-download/opconfig-download/

Important

If you are upgrading from a version previous to 3.5.0 or greater, please read: Upgrading Opmantek Applications

opConfig 3.6.0

Improvements

• Added secrets randomise and secure cookies. For more information see Security Configurations. 
• Updated jQuery dependencies.

opConfig 3.5.3

Bug Fixes

• Fixed issue in opConfig where a large amount MongoDB connections were created and retained.

opConfig 3.5.2

RELEASED  30 March 2021

• This version provides new authentication configurations:

  • Limit the number of sessions per user
  • Lock users that have not logged in in a specified period of time

opConfig 3.5.1

RELEASED  30 Oct 2020

• Bugfix: When a command throws an error - For example, opConfig has no access to the node anymore - The last revision information was lost. It still persists in the database, in the collection command_output_log.  But in the GUI, the revision is shown as no data. The behaviour was modified: 
  • If there is an error with the command, a new revision is saved, indicating the last attempt and the error, even if no text output is received. 
  • If the new revision has the same result as the previous, the information will be assigned to revision 0. This is the same behaviour, but now also happens with revisions with error. 
• Purging rules: The command purge_revisions has been modified. Now, it also removes a queue when a revision is removed, if there are not other existing jobs referencing another existing revision. Also, a new command was created, purge_queue, to remove old jobs not linked with any revision, based in the parameter 

  opconfig_queue_expire_after_seconds
  This parameter is 8 days by default, and is specified in seconds. You can read more about the purging data in opConfig in the next link. 

• List queue: Now it returns only the pending jobs by default. All the jobs can be listed with all=1.

opConfig 3.5.0

RELEASED 01 Oct 2020.

Upgrade Notes

The new upcoming release of opConfig 3 will work on Opmantek's latest and fastest platform, however, the currently installed products are incompatible with this upgrade. 
To find out more about this upgrade please read: Upgrading Opmantek Applications

opConfig 3.4.0

Released 15 July 2020

• Maintenance release.

This release requires updated licenses, please contact Opmantek Support to organise new licenses.

opConfig 3.2.4

Released 5 June 2020

...

• More robust handling of slow commands
  You can now configure how opConfig should react to a particular command (or command set) timing out:
  it can either terminate and reopen the connection (default) or attempt a state resynchronisation (at the cost of some extra delay).
• Improved handling of interaction with very slow devices
  opConfig now handles complex and/or slow logins (e.g. ones with extra banners) more robustly.
• This version of opConfig introduces "Device Presets", which allow more fine-grained control of a device's timing options.
• Various minor bug fixes

...

• opConfig now fully supports SSH keys for authentication at at target system, managed using the Credential Set GUI.
• opConfig now properly supports devices which provide direct access to privileged/superuser/enabled mode (e.g. when TACACS+ is configured to put theuser in enable mode).
  To inform opConfig to adjust its behaviour accordingly you'll have to set the new option "Automatically Privileged" for the given credential set.
• Connection details and credential discovery was improved for greater robustness.
  opConfig now deals properly with partially overlapping credentials (e.g. same user name and login password but different privileged/enable passwords), also taking into account the privileged mode.
• Discovery of a node's connection details and credentials is now possible from the GU
  The new button "Discover Connection Details" schedules an immediate (but asynchronous) (re)discovery of a node.
• Discovery of connection details can now be scheduled for a future time using opconfig-cli.
• Initial state of nodes imported from NMIS is now configurable.
  This is meant for sites with lots of nodes in NMIS but only a few managed by opConfig: If you set the configuration option opconfig_import_nodes_activated to false, then any newly imported nodes will be added as 'deactivated for opConfig'.
  Please note that this applies only to new nodes, and only to the node's activation state for opConfig (i.e. not opEvents or other applications).
• Configuration change pushing for devices without explicit 'configure' mode (e.g. Unix servers) is now more robust
  opConfig now autodetects whether a configuration mode is available, based on the phrasebook for the selected node personality. If no configuration mode is available, opConfig performs the configuration change operations in privileged/enabled/superuser mode instead.
• The installer now automatically sets up a unique application secret (on install or upgrade), unless your system is already configured for SSO.
• Various bug fixes and minor improvements

...

• This version comes with the interactive Opmantek Installer which guides you through both upgrades and initial installations.
• opConfig no longer uses CGI scripts; instead it integrates with the Opmantek Web Server infrastructure, which provides consistency across applications and better scalability.
  opConfig now runs out of  /usr/local/omk and interoperates with all other current Opmantek Applications (ie. opExport, opEvents, opCharts, opHA 2, Open-AudIT Enterprise).
• The GUI was revised and modernized, and both interactive response time and performance have improved substantially.
• opConfig now provides a flexible and extensible facility for (software and configuration) Compliance Management.
• Credential sets are now stored in encrypted form within the database.
• opConfig now provides integration with Open-AudIT Enterprise and optionally imports complete audit information for nodes known to Open-AudIT Enterprise.
• opConfig now interoperates better with opEvents, and node configurations are shared between the applications. Importing node information from NMIS also has been simplified.
• User authorization (using groups) is now supported and nodes are completely invisible to users whose authorization doesn't match the nodes' groups.
• The default command sets were reorganized and now support easier separation into different classes, e.g. hourly/daily/weekly sets of commands.
• The functionality of the opconfig-cli.pl CLI tool and its builtin documentation were extended and improved.
• opConfig now also ships with the Opmantek Support Tool.
• Almost all configuration is now performed from within the GUI. The only remaining configuration files are the opCommon file, and the command set and compliance policy files.
  Existing credential sets and connection lists are migrated automatically on first startup.
• Application logging was revised and overhauled.
• opConfig now deals better with querying Unix systems for configuration.
• And of course lots of bugs were resolved, and minor imperfections repaired.

...