Installing Management and Monitoring Services in a Cluster

Before installing Management and Monitoring Services in a cluster, make sure that you can map to the cluster volume using the name of the virtual server for the cluster node that is using the Novell Client.

The installation program walks you through installing the Management and Monitoring Services software.

o install Management and Monitoring Services in a cluster:

  1. Follow the instructions provided in Installation on NetWare and Windows, keeping in mind the following cluster-specific detail:

    • In Step 10, choose the destination volume for the components from the Authenticated Tree option through the cluster virtual server.

      The DNS entry for the virtual server object must be there, or the hosts file in the \Windows folder needs to have an entry for the virtual server object for the cluster volume where you want to install.

      If the same cluster volume is selected using the mapped drive option or by expanding the cluster node servers, then the install is considered to be a normal install and the system files are copied to all the cluster nodes. Therefore the product only works on that node.

      IMPORTANT:  The NetWare Management Agent cannot be installed on a cluster volume because it is used to manage the cluster node servers. To manage all the nodes, the Netware Management Agent needs to be present on all the nodes.

  2. After installation in the cluster, manually add the following line to the cluster volume load script:

    sys:\system\mmsstart.ncf

  3. Manually add the following line to the cluster volume unload script:

    sys:\system\mmsstop.ncf

  4. Ensure that the following lines are present in the cluster volume unload script in the order shown:

    sys:\system\mmsstop.ncf
    unload dbsrv8.nlm

    IMPORTANT:  If you have already installed ZENworks 6.5 Server Inventory in a clustered environment, add the sys:\system\mmsstop.ncf before the unload dbsrv8.nlm entry.

  5. Ensure that the volume ID is less than 32 for NetExplorerTM to work. This is because of the BTRIEVE database restriction. To specify the volume ID, use the following command in the load script:

    mount volume_name VOLID = volume_number

  6. You must install the Traffic Analysis Agent on the cluster volume only if all the cluster nodes are on the same segment. If you do not, the agent does not provide consistent information when you change the cluster node.

    If you are installing Traffic Analysis Agent or Management Site Server on the cluster shared volume, you must add SYS:\SYSTEM\MMSSTART.NCF to shared volume load script and SYS:\SYSTEM\MMSSTOP.NCF to shared volume unload script.

    When a shared volume is loaded on a node, MMSSTART.NCF file contains the information to start the Database, Naming Server, Discovery and Sloader if Management Site Server is installed and information to start Traffic Analysis Agent if Traffic Analysis Agent is installed on that cluster shared volume. When a shared volume is unloaded from a node, MMSSTOP.NCF contains the information to stop the Naming Server, Discovery, and Sloader and to stop Traffic Analysis Agent, depending on whether it is installed.

    If you are installing the Traffic Analysis Agent on a shared volume, update the lanz.ncf file in the \zfs_agnt\lanz directory by adding the location where you want the trend files to be generated as shown:

    load gtrend.nlm \dvolume_name:\directory