Skip to end of metadata
Go to start of metadata
  • Men & Mice DNS Server Controller, Men & Mice DHCP Server Controller, Men & Mice Updater are distributed in one combined installer for each operating system
  • Men & Mice Central is distributed as installer for each supported operating system.
  • Men & Mice Web Interface is distributed in a separate installer.
  • Men & Mice Management Console (runs only on Windows and is mandatory for the initial setup of the Men & Mice Suite)

Running an installer

Linux

Solaris

Then change into the newly-created directory and run the installer as described in the following sections.

With version 7.1 of the Men & Mice Suite a new Python based installer for the Men & Mice Controllers is available.

By default, when executed it tries to figure out the installed service (e.g. BIND) automatically and will try to install it without further user input.
In case it can't install the service it will print out hints and further information.
If the machine has multiple services installed, like ISC DHCP and ISC BIND DNS you want to specify explicitly the Men & Mice Controllers that
should be installed.

To get the list of available controllers/parameters just run the installer script with the --help parameter:

 

Multiple controllers can be specified. If you have for instance ISC BIND and ISC DHCP runnning on the machine just run the installer as follows:

 

Quiet/unattended installation is possible with the --quiet parameter (no output at all):

 

Please note that the Men & Mice Update Controller always gets automatically added to the list when another M&M service is installed, e.g. in the above listed example the --update-controller gets added automatically.
If you have only a single service like BIND or Unbound installed we recommend to run the installer without parameter. It will then use the --auto parameter and figure out the service automatically.

If you plan to use the Generic DNS Controller, please see the article about the Generic DNS Server Controller setup.

If you run into issues with the new installer, the old interactive Perl based installer is still present in the same archive as:

deprecated_installer.pl

To execute the deprecated installer for the Men & Mice Controllers please run it as follows:


The installer will ask a series of questions. Be prepared to answer them, as indicated below for each component.
The Kea DHCP4 Controller can not be installed by the deprecated installer.

Installing Men & Mice Central

Before installing Men & Mice Central, decide the following:

  • What user account will own the Men & Mice Central process?
  • Where do you want everything stored? There are defaults provided.

User Account

Men & Mice Central has the ability to discover devices in an IP range by sending ping packets (requires the IPAM module). However, in order to do so, it must run as root. If this is not a concern for you, you can run it as a less-privileged user; you should then create a dedicated user and group for the service.
On a Linux distribution with libcap2 installed and functioning properly, Men & Mice Central can be given the needed privilege without running as root. Execute the following:

Note that many Linux distributions do not have libcap2 installed.

Execution of the installer

Installer Questions

Here are the questions asked by the installer that pertain to Men & Mice Central:

  • Do you want to install Men & Mice Central?
  • Where do you want Men & Mice Central to keep its configuration files?
  • Enter the user and group names under which you want to run Men & Mice Central.
  • Where do you want to install the Men & Mice Central binary?

Men & Mice DNS Server Controller

Before installing Men & Mice DNS Server Controller, examine your named data and operating environment, plus the init script and/or settings file used to start named. Be aware that the installer will rearrange named.conf and your named data directory. Know how to answer the following questions:

  • Is there a starting configuration file, such as /etc/named.conf?
    • If not, you will need to create one.
    • If there is, is it valid? It must load without errors.
  • Does named.conf contain the necessary statements? See the notes below.
  • Does the named init script change the ownership of the named data directory? If so, this will cause problems and should be fixed. (This is aimed at users of some Red Hat Linux versions, and derivatives. Look for the ENABLE_ZONE_WRITE setting.)
  • Does named run in a chroot environment? If so, look for the following problems, and fix or work around any encountered. (Check the installation walkthroughs in the knowledge base for solutions.)
    • Does the named init script copy anything into the chroot jail when starting the service? (This is aimed at users of SUSE Linux.)
    • When the installer rearranges the data directory listed in named.conf, will that cause problems? (This again is aimed at users of SUSE Linux.)
  • What user account owns the named process? Men & Mice DNS Server Controller must typically run as the same user. However, it is sometimes possible to use group membership instead.

Required named.conf Statements

Men & Mice DNS Server Controller requires that named.conf (including any files listed in include statements in named.conf) have certain settings. The following are required:

directory

The directory substatement of the options statement must be present and must point to a directory that the installer can replace. Specifically, it may not refer to /, /etc, the root of a chroot jail, or any partition mount point. If you need to change or add the directory statement, you may then have to move files around or change the paths used elsewhere in your named.conf (or its included files).

key

For BIND, there must be a key defined, so that Men & Mice DNS Server Controller can control named using rndc commands. It is common for there to be a key in a default file such as rndc.key, which is almost always found in the same location as named.conf; however, Men & Mice DNS Server Controller requires that this key be defined explicitly in named.conf. If there is a file named rndc.key, its contents can simply be copied directly into named.conf.

To generate a key, the following command usually works, though you may have to specify a path to the command:

rndc-confgen > /etc/rndc.conf

This creates the file rndc.conf in the default directory (usually /etc , which may or may not be where you want it). This file contains a complete rndc configuration for local use, as well as key and controls statements, in comments, that can be copied into named.conf (after removing the comment marks).

controls

Men & Mice DNS Server Controller uses a controls statement for BIND. There must be a controls statement with an inet substatement that references an explicitly defined key (see above); the inet statement must allow connections from the loopback address, 127.0.0.1. If there is no controls statement defined, the installer will remind you to create one manually.

SELinux

Some newer Linux distributions come with SELinux (Security Enhanced Linux) enabled by default. Due to the complexity of and variation between SELinux configuration files, we are unable to support SELinux configuration at this time. SELinux settings commonly interfere with the normal operation of named after its configuration has been rewritten by the installer for Men & Mice DNS Server Controller, so our recommendation is to disable SELinux. It is possible to make named, Men & Mice Suite, and SELinux all work together, but we cannot currently offer support for this.

The $INCLUDE and $GENERATE Directives

Please refer to the Men & Mice Knowledge Base for information about how these directives are handled in Men & Mice Suite.
Handling of $INCLUDE: https://otrs.menandmice.com/otrs/public.pl?Action=PublicFAQZoom;ItemID=84
Handling of $GENERATE: https://otrs.menandmice.com/otrs/public.pl?Action=PublicFAQZoom;ItemID=83

Installation with Dynamic Zones

Men & Mice Suite expects dynamic zones to be made dynamic by allowing signed updates. Any dynamic zone must have an allow-update statement whose ACL contains a key. If you do not otherwise have a need for signed updates, add the rndc key (or any other key) to the list.
Furthermore, after installation, be sure that your server allows zone transfers of dynamic zones to the loopback address, 127.0.0.1, or users will be unable to open dynamic zones from this server. Zone transfer restrictions can be set or changed in the server's Options window and in each zone's Options window in Men & Mice Management Console.

Installer Questions

Here are the questions asked by the installer that pertain to Men & Mice DNS Server Controller:

  • Do you want to install the Men & Mice DNS Server Controller?
  • Are you running named in a chroot() environment?
  • What is the chroot() directory?
  • Where is the BIND configuration file?
  • Would you like the DNS Server Controller to run name-checkconf to verify changes when editing advanced server and zone options?
  • Where is named-checkconf?
  • The installer needs to rearrange the files in <directory> and restart the name server. A backup will be created. Is this OK?
  • Enter the user and group names under which you want to run the Men & Mice DNS Server Controller. This must be the user which is running named.
  • Where would you like to install the Men & Mice external static zone handling utilities?
  • Where do you want to install the Men & Mice Server Controller binaries?
  • BIND needs to be restarted. Would you like to restart it now?

Men & Mice DHCP Server Controller

Installing Men & Mice DHCP Server Controller is typically quite straightforward, with far fewer considerations than Men & Mice DNS Server Controller.
Here are the questions asked by the installer that pertain to Men & Mice DHCP Server Controller:

  • Do you want to install the Men & Mice DHCP Server Controller?
  • Where is the DHCP server configuration file?
  • Wher is the DHCP server lease file?
  • Where do you want the Men & Mice DHCP Server Controller to keep its configuration files?
  • Enter the user and group names under which you want to run the Men & Mice DHCP Server Controller. This must be the user which is running dhcpd.
  • Where do you want to install the Men & Mice Server Controller binaries?

Managing Cisco IOS with DHCP support

Men & Mice DHCP Server Controller can also manage Cisco IOS servers with DHCP support. There is no need to install any software on the Cisco device, but it is necessary to create a user account on the device that has the ability to telnet or SSH in. You will be asked for the username and password when adding the server.
When adding a Cisco IOS server to Men & Mice Suite, the options are very similar to those shown when adding an MS DHCP server; by default, if possible, Men & Mice Central will look for a copy of the DHCP Server Controller on the same server as itself, but you can also specify a particular installation to use as a proxy. It is recommended to use a copy of the DHCP Server Controller that is on the same network segment as the Cisco IOS server.

Men & Mice Updater

Installing Men & Mice Updater is typically quite straightforward.
Here are the questions asked by the installer that pertain to Men & Mice Updater:

  • Do you want to install the Men & Mice Updater?
  • Where do you want to install the Men & Mice Server Controller binaries?

Men & Mice Management Console

Men & Mice Management Console is the primary client application for Men & Mice Suite. It is necessary to initially configure the Suite through this interface; this initial configuration cannot be performed through the command line or web interfaces. Therefore, it is necessary to have this component installed somewhere.


Men & Mice Management Console is only available as a Windows executable. However, if necessary, it can be run using the open-source Windows API replacement called Wine. Free packages for Wine are readily available for most Linux distributions, as well as for FredBSD and Solaris. For Mac OS X, there is a free implementation available known as Darwine and a commercial solution named Crossover Mac from Codeweavers. For more information regarding Wine and Crossover Mac, please see the following websites: http://www.winehq.org/ http://www.codeweavers.com/

Men & Mice Web Interface

The Men & Mice Web Interface consists of several parts, which are installed in different locations:

  • Men & Mice XML Interface, a service, plus an associated init script
  • an Apache .conf file (to be included by httpd.conf)
  • a collection of HTML and related files

The Men & Mice Web Interface installer, by default, will try to put all of these parts in standard locations, near other similar software. For example, it may suggest putting the HTML and related files under your web server's docroot. However, there's no reason this has to be: The .conf file and the init script will be given the paths of everything else, regardless of where you choose to install the rest.

Installer Questions

The installer will first ask for the location of your httpd.conf (or equivalent) in order to try to guess the rest of the answers. It then presents these guesses as suggestions to the other questions. Here are those questions:

  • Where is the Apache 2 server configuration file?
  • Where would you like to install the configuration file for the Men & Mice Web Interface?
  • Where is the Apache modules directory?
  • Where would you like to install the Men & Mice Web Interface?
  • Enter the user and group names that will be assigned ownership of any files that are a part of the Men & Mice Web Interface.
  • Men & Mice Web Interface uses a daemon to communicate with Men & Mice Central. Where would you like to install the daemon binary?
  • Where do you want the daemon to keep its configuration files?
  • What port would you like the daemon to listen on?
  • Would you like to run the daemon as some user other than "root:root"?
  • Enter the user and group names under which you want to run the daemon.

Detailed Installation Information

This section contains some background information regarding what the Unix installers (Solaris and Linux) for the various Men & Mice service components do to the system, and how to remove the software and revert to your original configuration.

Men & Mice DNS Server Controller Installation

Installing Men & Mice DNS Server Controller rearranges your named configuration data, including rewriting named.conf and rearranging the data directory. The new configuration is functionally equivalent to the old, except the logging statement is either added or changed to add some new channels.

Common Files

The file layout is a little different with or without BIND views. Here are the parts in common:

Description

File(s) or directory

Men & Mice DNS Server Controller daemon

mmremoted, usually in /usr/sbin or /usr/local/sbin

Men & Mice external static zone handling utilities

mmedit and mmlock, usually in /usr/bin or /usr/local/bin

Data directory for Men & Mice DNS Server Controller

Usually /var/named, /etc/namedb, /var/lib/named, or something within a chroot jail; the same location as before the DNS Server Controller was installed

Backup of original data directory

Same as above, with ".bak" appended to the path

New starting configuration file

Usually either /etc/named.conf or /etc/namedb/named.conf; possibly located within a chroot jail

Backup of original starting configuration file

Same as above, with ".bak" appended to the path

logging statement from named.conf

conf/logging, relative to the data directory

key and acl statements from named.conf

conf/user_before, relative to the data directory

options statement from named.conf

conf/options, relative to the data directory

controls, server, and trusted-keys statements from named.conf; also,

if present and if not using views, the root hints zone statement

conf/user_after, relative to the data directory

Preferences file

mmsuite/preferences.cfg, located in the data directory

init script, the shell script that can be used to control the service;

used by init during system startup

Solaris: /etc/init.d/mmremote

 

Linux: /etc/init.d/mmremote

settings file used by the init script (Ubuntu Linux only)

/etc/default/mmremote

Without Views

If views are not defined, the following files are created inside the data directory:

Description

File(s) or directory

List of include statements, one for each zone statement file

conf/zones

Directory of zone statement files

conf/zoneopt

A sample zone statement file, for the zone "localhost."

conf/zoneopt/localhost.opt

Directory of primary master zone files

hosts/masters

Directory of slave zone files

hosts/slaves

A sample zone file, for the primary master zone "localhost."

hosts/masters/localhost-hosts

With Views

If views are defined, the following files are created inside the data directory:

Description

File(s) or directory

View statements, not including zone statements within each view

conf/zones

List of include statements for a particular view, one for each zone statement file

conf/zones_viewname

Directory of zone statement files for a particular view

conf/zo_viewname

A sample zone statement file, for the zone "localhost." in the view "internal"

conf/zo_internal/localhost.opt

Directory of primary master zone files for a particular view

hosts/view_viewname/masters

Directory of slave zone files for a particular view

hosts/view_viewname/slaves

A sample zone file, for the primary master zone "localhost." in the view "internal"

hosts/view_internal/masters/localhost-hosts

Removing the DNS Server Controller and Reverting to Original Data

To remove the DNS Server Controller, first use the init script to stop the service (give it the "stop" argument). Then simply delete the daemon and the init script, and remove any references to the init script in the rest of the boot system if necessary. To revert to your original data, stop named with its init script. Then delete the initial configuration file and the data directory and rename the originals, removing the ".bak" from their names.

Men & Mice Central

Installing Men & Mice Central puts the following files on your system:

Description

File(s) or directory

Men & Mice Central daemon

mmcentrald, usually in /usr/sbin or /usr/local/sbin

Data directory for Men & Mice Central

Usually /var/mmsuite/mmcentral

Update directory

update, located in the data directory

Preferences file

preferences.cfg, located in the data directory

init script, the shell script that can be used to control the service; used by init during system startup

Solaris: /etc/init.d/mmcentral

 

Linux: /etc/init.d/mmcentral

settings file used by the init script (Ubuntu Linux only)

/etc/default/mmcentral

To remove Men & Mice Central, first use the init script to stop the service (give it the "stop" argument). Then simply delete the daemon and the init script, and remove any references to the init script in the rest of the boot system if necessary. Also delete the data directory if desired.

Men & Mice Web Interface

Installing Men & Mice Web Interface puts the following files on your system:

Description

File(s) or directory

Apache 2 configuration file

mmwebext.conf, usually in a directory of similar .conf files to be included by httpd.conf

directory of HTML, javascript, and other related files

usually named MenAndMice/, a directory that might be under the Apache document root

Men & Mice XML Interface daemon

mmxmlintd, usually in /usr/sbin or /usr/local/sbin

init script, the shell script that can be used to

control the service; used by init during system startup

Solaris: /etc/init.d/mmxmlint

 

Linux: /etc/init.d/mmxmlint

settings file used by the init script (Ubuntu Linux only)

/etc/default/mmxmlint

To remove Men & Mice Web Interface, first use the init script to stop the Men & Mice XML Interface daemon (give it the "stop" argument). Then simply delete all files referenced above, and remove any references to the init script in the rest of the boot system if necessary. If an include statement had to be created in httpd.conf expressly for Men & Mice Web Interface, remove it; check your Apache configuration with apachectl configtest to be sure it is valid after removing the Web Interface. Finally, restart the Apache web server.x

  • No labels