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/

opConfig 4.5.5

• Fixed issue connecting to certain devices over ssh.
• Fixed issue when adding connection arguments in Node Admin.
• New opconfig-cli action, act=create_compliance_report. An action to generate compliance report which show compliant vs non-compliant policies.
• Report generates the summary of all the compliance policies run against the given node (if no node is given we get data for all active nodes).
• Report take policy rule name, extract all the rules run against the node and does a value mapping, if it passed or failed.

opConfig 4.5.4

• Added support for Debian 11 to the installer

opConfig 4.5.3

• New release with Improvements and bug-fixes.

Improvements

• New opconfig-cli action, act=refresh_os_info. An action to refresh the opConfig OS Info for a node.
• Improved node configuration detection. See  opConfig 4 User Manual#RelatedConfigurationforChangeNotification
• Improved Virtual Operator and Changes Overview dashboard's for consistency
• Minor template formatting improvements in opconfig GUI

Bug Fixes

• Fixed OS Summary links in opConfig dashboard not showing correct results
• Fixed OS Summary not filtering out Operating System records

opConfig 4.5.2

New release with improvements and bug-fixes.

Improvements

• When the compliance system generates an exception it generates an event.
• Added option print_command_output=true  for opConfig CLI config command sets.
• Automatically apply OS detection.  For example, if we know a node is Linux, run some commands to determine if it is Debian, Ubuntu, CentOS, etc.

Bug Fixes

• Fix deleting an entry in a Command Set would reappear after saving.
• Fix Command change detection so that opConfig raises an event with title "Node Configuration Change Detected".
• Fix adding schedule for Config Set from Schedule Configuration Changes screen, it now creates a schedule.
• Fix pre and post commands disappearing when a Config Set is saved.
• Fix Command Output screen where the  'Run Command Now' button didn't work when screen width was reduced.

opConfig 4.5.1

New release with improvements and bug-fixes.

Improvements

• Bug fix for events raised using command-sets with opConfig.

• opConfig CLI improvements to add print command output for action push_configset.

• Bug fixes for test connections.

• Bug fix for search options.

opConfig 4.5.0

Big release with an upgraded GUI framework to deliver accessibility enhancements and dark mode.

Improvements

• This release includes improved Accessibility options, including support for Dark Mode. We have taken the opportunity while we tidied up the screens to change Opmantek to FirstWave. These are new features that are backward compatible with earlier releases.

opConfig 4.4.2

18th August 2022

Support for MongoDB 4.2 please see Upgrading to MongoDB 4.2

opConfig 4.4.1

4th August 2022

This was an internal release

opConfig 4.3.2

8th March 2022

• Improved mongodb index for command sets.
• Improved the "Help screen" for Command Sets and Config Sets
• Added the "Discover OS Info", "Discover Connection Details" and "Test Connection" buttons for nodes in opAdmin
• New CRUD API for credential sets. 
• New CLI API for credential sets. 
• Improved main dashboard load times.
• Fix to protect a command.
• New parameter to increase the time out for a plugin per command set: 

  interaction_timeout

opConfig 4.3.1

16 Dec 2021

• Fix issue where using opConfig in classic auth node would show nodes you shouldn't have access to.
• Fix issue where virtual operator would break in classic auth mode.
• Fix issue where scheduling jobs would save the time using the browers timezone not the servers
• New improvement with a new parameter, compare_to_previous_revision, for config sets to avoid compare revisions. This parameter is specially helpful when the are big files to compare and the config sets are taking a really long time:

     "commands" : [
         {
            "privileged" : "true",
            "multipage" : "true",
            "compare_to_previous_revision" : "false",
            "use_processing_plugins" : [
               ""
            ],
            "report_level_min_changes" : null,
            "active" : "true",
            "tags" : [
               "application",
               "troubleshooting"
            ],
            "use_collection_plugin" : "",
            "command" : "scp my/file"
         },

opConfig 4.3.0

1 Dec 2021

RELEASED 

• Updated core dependencies
• Cookies now support samesite strict, see Security Configurations
• Fixed issue in checkdaemons.sh with stopping monogdb

opConfig 4.2.7

26 Oct 2021

RELEASED 

This release includes:

• Spanish translations.

opConfig 4.2.6

21 Sept 2021

RELEASED 

This release includes the following new features:

• New GUI for editing Config Sets. More information in the following link. 
• Config set parameters supported: It is possible to add parameters to a config set. More information.
• Run Virtual operator jobs with groups of nodes:

Image Added

• Now is possible to use phrasebook macros in Command Sets.
• GUI improvements.

opConfig 4.2.5

10 Aug 2021

RELEASED Bug fixes

• Fixed issue where editing a node in opConfig would overwrite the nodes configuration
• Test connection error now shows the current error state and if the node name cannot be found it will use the nodes uuid
• Installer now changes the config option opconfig_default_period from 8d to 2d

opConfig 4.2.4

RELEASED 30 Jul 2021

This release includes:

• Security updates. More information in the following link. 
• Migration script utility: To migrate the connection info and OS info node data when upgrading from opConfig 3. 

opConfig 4.2.3-1

RELEASED 29 Jul 2021

Bug Fix

• Fixes an issue in ./omk/conf/opCommon.json and ./omk/install/opCommon.json by changing the following entry:
  • "omk_show_getting_started_widgets" : true
    becomes
    "omk_show_getting_started_widgets" : "true"

opConfig 4.2.3

Features

• opConfig installer checks and sets opconfig_raise_alert_events and opconfig_raise_change_events. 
• Added security content header. This is affecting all the products. The content security policy can be overwritten using the configuration item "security_content_policy".
• Removed cron line with action import_audit. 
• Added AIX phrasebook.

Bug Fixes

• Connection errors are not saved as command revisions.
• Command collection was not run if no nodes were specified. This may prevent some cron tasks to run. Now, If no nodes are specified, the command will run for all nodes. 
• Considered just local nodes for license check. 
• Fixed "Can't call method node on an undefined value" error in some command outputs.
• Now it is possible to install opConfig on an alternative path using -t.
• Connect options was not working. 

opConfig 4.2.2

Bug Fixes

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

opConfig 4.2.1

Features

• Command Set Parameters
  • opConfig now supports parameterized command sets, eg . Eg: ping $ipaddress
  • Parameters can be passed in via the command line, eg . Eg parameters.x
  • When creating a new Virtual Operator Job and , if you have selected a command set which has parameters, the form will then display next "Next" and the second screen will ask you to provide parameters
  • Parameters can also be passed in through derived data
  • parameters Parameters currently have two data types, "string" and "ipaddress"
    • ipaddress is just used for front end validation, the cli does no validation
  • parameters_required => "true" can be set and if . If the parameters from the cli or gui have not been passed in then , opConfig will not run the command

  • Parameters get defined by a top level key and are an array of objects with two keys, : parameter and type

    Code Block
    "parameters" : [ { "parameter" : "id", "type" : "String" }, { "type" : "String", "parameter" : "name" } ],

    
    

• Command Set Editor under "System" > "Manage Command Sets"
  
  • You can delete, update and create new command sets through a visual GUI
  • Only command sets under conf/command_sets.d/ can be modified.
• Derived Data has new types of table columns to display related jobs or create new virtual operator jobs from. Plugins in opConfig#NewDerivedInformationElementsinopConfig4.2.1
• Conditions has new types of table columns to display tags, urls and tooltips, More details can be found here Plugins in opConfig#NewReportConditionElementsinopConfig4.2.1
• New top level key, "active" can be set to "true"/"false" if false the command set wont be loaded
• New key for commands "active" can be set to "true"/"false" if false the command from that set wont be loaded, other commands set to true will be loaded as part of the set.

BugFixes

• Fixed issue where opConfig would report duplicate command sets.
• Fixed Issue where the trouble shooting button would always display.
• Fixed issue with logging at debug levels not requested in opconfig-cli
• Fixed issue where opcharts-cli would not honor different debug levels

...

Upgrade Notes

The new upcoming release of opConfig 4 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

...