Skip to end of metadata
Go to start of metadata

Purpose

Some customers NMIS/OMK environments are are comprised of many servers.  Leveraging the built in automation tools of NMIS and OMK modules will simplify and standardize the deployment.

Automation of application configuration will greatly improve the consistency and efficiency of the application deployment, saving time in deployment and then in troubleshooting later.

Domain Wide Standard NMIS/OMK Properties

Some NMIS/OMK configuration properties will be the same across servers in an administrative domain.  Some popular examples follow, but any setting that would be the same across all servers should be considered.

  • Authentication methods
  • Authentication server parameters
  • Domain name
  • Single sign on parameters
  • Email server parameters
  • Collection policy
  • Threshold policy
  • Syslog parameters
  • Node Models
  • Icons

Server Unique NMIS/OMK Properties

  • NMIS host name
  • NMIS server name
  • OMKD hostname
  • OMK module hostname

Standardization Script Example

This is an example script that will set some attributes statically and prompt the user for server unique attributes.  This script converts the nmis8/conf/Config.nmis and omk/conf/opCommon.nmis files into a perl hash.  Any attribute may be set in these configuration files with a script such as this.  This script should be run on each server from the nmis8/admin directory as it relies on NMIS perl libraries.  Notice the use of FindBin in order to find the NMIS libraries.

  • No labels