This chapter contains instructions for installing EnlightenDSM. Topics include:
Pre-installation Considerations
Mounting the CD-ROM
Verifying that the CD-ROM is Mounted
Starting the CDINSTAL Program
Installing EnlightenDSM
Starting EnlightenDSM
Before installing EnlightenDSM, gather the following information about the hosts in your intranet.
Choose which hosts will run the EnlightenDSM installer. This machine needs to have access to a CD-ROM drive and be able to connect through TCP/IP to the hosts where you want to install EnlightenDSM. The host will also be in charge of EnlightenDSM license management. EnlightenDSM uses flexLM for all license management. The flexLM components are installed in the FLEXlm sub-directory of the EMD installation directory.
Choose which host(s) will run the Enterprise Management Database (EMD) and Programmable Event Processor (PEP) servers. The EMD requires 20 MB of disk space for the initial installation. Depending on your particular situation, this may grow to 50 MB (average) or even 100 MB. The PEP engine requires 10 MB of free disk space. EMD is currently supported on Solaris, HP-UX, AIX, and SGI IRIX.
Determine the root password for each host that will use EnlightenDSM.
Find a suitable partition with enough free space for each host that will use EnlightenDSM. The default EnlightenDSM installation directory is /opt/enlighten. If there isn't enough free space on your /opt partition, select another partition with a minimum of 60 MB for EnlightenDSM agents and an additional 60-80 MB for each host running an EnlightenDSM GUI interface (xenln). Any partition will do, as long as the installation directory will only be used by EnlightenDSM (e.g., don't install in /usr, install in /usr/enl or /usr/enlighten instead).
For optimal performance, installing EnlightenDSM on an NFS partition is not recommended. In addition:
EMD cannot be installed on an NFS mounted partitions.
You must have root write permissions on the NFS partition on which you will install EnlightenDSM.
EnlightenDSM runs with root privileges and may create files within the EnlightenDSM home directory during its activities. If root write permissions are not enabled on the partition on which EnlightenDSM is installed, many of EnlightenDSM's disk monitoring functions will not function. Be sure to install EnlightenDSM on a partition where root write permissions are enabled, such as local disk partitions.
Writing to NFS filesystems is relatively slow. Consequently, disk snapshots may take three to five times longer to create. This should be taken into consideration even if an NFS partition has root write permissions.
Consult the documentation that came with your network management application to manage EnlightenDSM Events Agent via SNMP. Your management application will need knowledge of our MIB. Some applications require a MIB in ASN-1 format while others require a copy of the MIB that meets the specifications of one or more RFC's. EnlightenDSM Events Agent provides both types of MIB formats.
 | Note: If you want to use the Events snmp daemon, AgentENL, delete any snmpd daemons that are running prior to installing Events on any of your hosts. |
Please note that the Enlighten Network Installer enl_xinstall, needs at least 32 free colors (viewed on an 800x700 or greater X-display) in order to start up. Some color intensive applications like Netscape will consume the entire colormap on your display, and enl_xinstall will not be able to come up. If you receive X-warnings regarding color, restart your x-server to clear your colormap, and try running enl_xinstall again.
This section describes how to mount the CD-ROM on various systems. For all platforms, you must be the root user.
Type the following command:
su root
Enter the root password when prompted. If the CD-ROM mount point, /cdrom, does not exist, type the command mkdir /cdrom to create it.
Type the following O/S specific commands to mount your CD-ROM (if you are unsure of your operating system, enter the command uname -a):
On Solaris 2 systems, the Volume manager, vold, may automatically mount the CD-ROM. If vold does not mount the CD-ROM, type the following commands:
/etc/mount -r -F hsfs /dev/sr0 /cdrom |
| Note: You may need to use the complete device name for the cdrom drive, such as /dev/dsk/c0t6d0s0. |
Type the following command:
/etc/mount -r -u -t cdfs <device name> /cdrom |
where <device name> is the device name and number associated with your local CD-ROM drive (e.g., /dev/dsk/2s0).
Use SMIT to mount the CD-ROM:
Type the following commands:
mkdir /cdrom smit storage
Select File Systems
Select Add / Change / Show / Delete File Systems
Select CD-ROM File Systems
Select Add a CD-ROM File System
Select the appropriate DEVICE name. If a conflict occurs, you may need to delete a previously defined CD-ROM file system.
Enter /cdrom as the MOUNT POINT.
Select Do.
Alternatively, press Enter if you are using the ASCII version of SMIT.
Exit SMIT.
Type the following command:
smit mountfs
Select /dev/cd0
Alternatively, select a previously selected device.
Select /cdrom as the DIRECTORY to mount.
Select cdrfs for the TYPE of file system.
Select yes for Mount as a READ-ONLY system.
Select Do.
Alternatively, press Return for the ASCII version of SMIT.
Exit SMIT.
To verify that the CD-ROM has been mounted, get a file list of the root directory of the CD-ROM by typing the following command:
ls /cdrom (or for IRIX, ls /CDROM) |
You should see the following files in the directory:
AIX41
COMMON
DOC
HP10X
IRIX5X6X
SOL2X
CDINSTAL
DEC3240
EXTRA
WINTEL
SCO5X
SUNOS41X
If these files are not visible, then the CD-ROM was not properly mounted. Try mounting your CD-ROM again. If the CD-ROM still fails to mount, make sure that your cables are connected, that the CD-ROM has a unique SCSI ID, and that the machine was rebooted after you installed your CD-ROM drive.
Once your X-Window System is running, you can run the CDINSTAL script.
Depending on your operating system, enter the following command:
For Solaris using vold, type /cdrom/cdrom0/cdinstal
For SunOS, type /cdrom/cdinstal
For SGI, type /CDROM/cdinstal
For all other platforms, type /cdrom/CDINSTAL
If this is your first-time installing EnlightenDSM, CDINSTAL will ask where you want to install EnlightenDSM components. The default EnlightenDSM installation directory is /opt/enlighten If there isn't enough free space on your /opt partition, select another partition with a minimum of 100 Mb of free space. Any partition will suffice, as long as the installation directory will only be used by EnlightenDSM.
Note: Don't install in /usr; instead, install in the /usr/enl or /usr/enlighten. The CDINSTAL script will display a list of all the components being extracted into your chosen directory.
When the extraction is complete, the EnlightenDSM License Agreement dialog will appear (Figure C-1).
Carefully read and follow the instructions in the window. To accept the terms of the Licensing Agreement and continue installing EnlightenDSM on your system type “I Agree” followed by your name in the green text field. Then click Accept. To decline the License Agreement and quit the installation process, click the DO NOT ACCEPT button.
If you accept the License Agreement, the main Network Installer window will appear (Figure C-2).
At the top of the Network Installer screen are buttons for each step in the installation process. The rest of this section details how to install EnlightenDSM using these buttons.
No files are transferred or modified in this installation process until you complete “Step 5: Install” and click the Start Installation button. If you make a mistake, just go back and type the correct information.
Because your configuration information is verified dynamically; a slow network will cause the installation to run slowly.
| Note: The EnlightenDSM Network Installer is SIGINT and SIGHUP aware. If you want to delete the EnlightenDSM Network Installer or cancel any operation, type <Ctrl>-c in the window where you started this process. EnlightenDSM will then prompt you to confirm your action. |
At the top of the Network Installer screen are buttons for each step in the installation process. For all the following steps, you can always click the Reset button to reset the fields to their default values. If you decide not to complete a particular step, simply click the Cancel button.
Once you have typed the necessary information for configuring a particular component, click the OK button to continue. If all the configuration information is acceptable, it will be added to the list in the Network Installer window.
Click the Step 1: EMD Setup button to configure the Enterprise Management Database (EMD).
The Setup the Enterprise Management Database window will appear, as shown in the example on page 178 (Figure C-3).
This window contains the following fields and toggles:
EMD
Use this toggle to Install, Upgrade, or Don't Install EMD. EnlightenDSM components must have access to both EMD and the Programmable Events Processor (PEP) to function properly.
Install EMD on host
Specify where to load EMD and the database Engine. The default is your local hostname or the location of a previously installed EMD, if available. Depending on your DNS settings, you may need to specify a fully qualified host and domain name.
At most, you may have to type in the IP address of the host.
EMD Install Dir
Specify the directory that will hold EMD. This directory must be a local partition. The default is /opt/emd.
Root Passwd
Specify the root password for the host shown in the Install EMD on host: field.
OS Type
Specify the O/S type for the EMD host machine.
Start daemons immediately after installation
Ensure that this checkbox is selected (the default) or EMD will not be available for the other EnlightenDSM components.
Automatically restart daemons after reboot
Ensure that this checkbox is selected (the default) or EMD will not be available for the other EnlightenDSM components.
Click the Step 2: PEP Setup button to configure the Programmable Events Processor (PEP). The Setup the Programmable Events Processor window will appear (Figure C-4).
This window contains the following fields and toggles:
Choose between Install, Upgrade, or Don't Install PEP. EnlightenDSM components must have access to both the Enterprise Management Database (EMD) and PEP to function properly.
Specify where to load PEP (hostname or IP address). The default is your local hostname or the location of a previously installed PEP, if available.
Enter the hostname (or IP address) of the EMD host. This defaults to the value specified in “Step 1: EMD Setup”.
Choose the O/S type for the PEP host machine. You may use the Auto Detect option (the default).
Ensure that this checkbox is selected (the default) or PEP will not be available for the other EnlightenDSM components.
Click the Step 3: Setup GUI/DSA button to configure EnlightenDSM for the remainder of the hosts on your intranet. The Setup EnlightenDSM Destination Host(s) window will appear (Figure C-5).
Every host in your intranet must be able to resolve the hostname of the install host and the hosts running the EMD, PEP, and GUIs through DNS (including reverse lookups), NIS/NIS+, or local /etc/hosts file entries.
| Note: To quickly modify the specified EMD and PEP hosts, double-click these entries in the Main Install list. |
This window contains the following fields and toggles:
Specify the host(s) where you will install the EnlightenDSM components specified in the EnlightenDSM Configuration area.
Enter the common root password for the hosts shown in the Hostname(s): field. If some hosts have different root passwords, they will remain in the Hostname(s): field after you complete this step. You can then enter the root password for those hosts.
This area contains the following fields and toggles:
Specify the directory that will hold the EnlightenDSM components. A full installation requires 100 Mb of free disk space.
This field defaults to the hostname for your EMD. You should leave this field with its default value.
This field defaults to the hostname for your PEP. You should leave this field with its default value.
Ensure that this checkbox is selected (the default) or the EnlightenDSM components will not come up automatically.
Ensure that this checkbox is selected (the default) or the EnlightenDSM components will not come up automatically.
| Note: If you want to manually configure your rc files, deselect the Restart daemons after reboot: button and add the call to <enlighten install dir>/bin/S92startenl in your system startup file. |
This area contains the following fields:
You can use this field to specify a hostname on your intranet that is running an SNMP-aware system manager. If you don't have such a manager installed, leave this set to <disabled> (the default). This will disable the SNMP trap generation.
This area contains the following field:
Use this list box to specify the host(s) that will be allowed to connect through the EnlightenDSM GUI to manage the hosts shown in the Hostname(s): list box. The default is your group management server (GMS).
 | Warning: If you leave this field blank, any host running the EnlightenDSM GUI can manage the hosts shown in the Hostname(s): field. You should only use this option if you have a firewalled intranet containing “trusted” hosts. |
Click the Modify button (in the Main window) to modify a host in the Main Install List. This will take you to the Step 3: Setup GUI/DSA screen.
Double-clicking a host in the Main Install List is the same as selecting that host and clicking on the Modify button. You can also click the Delete button (in the Main window) to delete the highlighted host(s) from the Main Install List.
Once you have completed the previous three steps, click the Step 4: Setup Licensing button. The EnlightenDSM Configure License File window will appear (Figure C-6).
Under License File, select Install, Upgrade or Don't Install.
If this is a new installation, enter the EMD hostname and the directory where EMD should be placed (the default is /opt/emd).
The first two lines of the license file are automatically entered values based on the installation information already provided. These lines should not be changed. They specify the name and location of the license server process (which must be the same as the EMD host specified in “Step 1: EMD Setup”) and the name of the EnlightenDSM license vendor daemon that is also located on the EMD host.
The remaining license file details provided by your EnlightenDSM vendor must be manually entered. Depending on the license features being activated, you may have already received license keys. You may also need to send additional information to your EnlightenDSM vendor to receive the properly validated license keys. Please contact your EnlightenDSM product vendor for additional information about license keys.
To read the existing license file, click the Get License File button. The contents of the existing license will be displayed in the License Information window. If you wish to update your license file and are not upgrading or installing additional EnlightenDSM components, you can manually edit the <emd_dir>/FLEXlm/license.dat file on the EMD host.
Once the license file has been updated, click OK to continue the installation process.
| Warning: It is important that the license file be installed correctly with valid license keys or the EnlightenDSM processes will not run. |
Click the Step 5: Install button to complete the installation process.
The Install to Local and Remote Hosts window will appear.
Click the Start Installation button to install EnlightenDSM in the configuration(s) you specified in the previous four steps.
The Installation progress information is written to you Enlighten directory as logs/install.log and to the Installation Log scrolled text field. Clicking on the Clear Log button will only clear the scrolled text field; this will not erase any entries in the install.log file.
Once the installation is complete, click Close to exit the EnlightenDSM Network Installer interface, and continue with the next section to start the EnlightenDSM GUI.
From a shelltool, xterm, or another such window, type the following commands:
cd <your enlighten installation directory> bin/xenln
If you have forgotten your EnlightenDSM installation directory, type the following command:
cat /etc/enlighten | grep “enlighten=” bin/xenln
Once you've found the correct directory and invoked xenln, the EnlightenDSM main menu toolbar will appear on your screen (Figure C-7).
Now you can begin using EnlightenDSM to help you administer your system and network needs. Refer to the EnlightenDSM Reference Manual and User Guide for more details on using this toolbar.
| Note: An EnlightenDSM Sysadmin Agent daemon must be running on each host that you want to manage. |
Windows 95, Windows, 98, Windows NT 4.0 Server or Windows NT 4.0 Workstation.
Intel-compatible machine (486 or later) with 32 Mb RAM and 6 Mb disk space available
EnlightenDSM for Windows NT must be installed on an NTFS partition.
Please note that installations of EnlightenDSM must be performed by an Administrator.
The following instructions will use D: to represent the letter that is assigned to your CD-ROM drive.
Insert the EnlightenDSM CD-ROM
From the Start menu, select Run...
In the Open: text field, type D:\Wintel\Disk1\Setup.exe, and click OK.
EnlightenDSM now uses FLEXlm license management to license it's components.
EnlightenDSM is now available with two different feature sets. (Workgroup and Advanced). The Workgroup set consists of the Configure, User, Printer and Network features. The Advanced set consists of the Workgroup set plus the Security, Disk, Archive, System, Events and Status Map features.
For the EnlightenDSM services to run properly, they must be able to communicate (through RPC) to a UNIX host running EMD and a UNIX host running PEP (which may be the same UNIX host). The configuration GUI, dsm_cfg.exe, will prompt for these hostnames.
To graphically manage your enterprise, you must use the EnlightenDSM GUI. The GUI must run on a UNIX host and be displayed on an X/motif-compliant host. Perform the following steps to display the EnlightenDSM GUI on a Windows machine:
Install third-party X software on the Windows machine you want to display the GUI on.
On a UNIX box that has the EnlightenDSM GUI, bin/xenln, set the DISPLAY environment variable to "<name of your Windows machine>:0.0"
Then run bin/xenln (from the UNIX machine).
EnlightenDSM provides SNMP services via the AgentMon and AgentENL services. AgentENL primarily provides SNMP and SMUX protocol services, AgentMon performs all monitoring functions. Because many other SNMP packages are available for Windows, some of which do not support the SMUX (SNMP Multiplexor) protocol, AgentMon has been modified to operate without SNMP/SMUX if it cannot connect to AgentENL or some other SMUX-compliant service. If AgentENL interferes with other SNMP services on your system, you may now safely disable the AgentENL service and AgentMon will continue to generate EMD events, send email, etc. It will just not be reachable from SNMP applications. AgentMon will automatically re-connect to an SMUX service if one becomes available at a later time.
Whether SNMP is in use by EnlightenDSM or not, you should still install the SNMP Service package. This package is needed to obtain meaningful network statistics, the Microsoft SNMP Service package contains drivers which provide network performance data. AgentMon monitors network statistics whether it will be generating SNMP traps or EMD events. After installing the SNMP package (Start->Settings->Control Panel->Network, select the Services tab, click Add..., then select “SNMP Service”). If you wish to run the SNMP service provided by EnlightenDSM, either run the DSM Configuration GUI, dsm_cfg.exe, or ensure the Microsoft SNMP service is disabled.
The Simple TCP/IP Services package must be installed in order to use EnlightenDSM's clock synch feature with a Windows machine as the time server. Install the package by opening Start->Settings->Control Panel->Network, select the Services tab, click Add..., then select “Simple TCP/IP Services”),
EnlightenDSM requires (and ships with) an ONCRPC-compliant portmap service. If you have installed a third-party NFS client, this service will already be registered, and the DSM Configuration GUI will not register EnlightenDSM's own ONCRPC portmapper. If you deinstall the NFS client software (and consequently remove the non-EnlightenDSM portmap service), make sure you run the DSM Configuration GUI after deinstallation - dsm_cfg.exe will then register EnlightenDSM's portmap service.
EnlightenDSM Events' default mailer destination is [email protected]. If your enterprise does not have a hostname alias for “mailhost,” or if you want Events notification to go elsewhere, use the EnlightenDSM GUI or simply edit config\testtab.<hostname>.
Be aware that the logout and system shutdown functionality is forceful in order to ensure the system actually shuts down at the specified time. Interactive users are warned about the impending shutdown, but cannot cancel the action.
The child process of the EnlightenDSM SysAdmin service, renldc, runs as the System Account. It is possible that ACL permissions on a file or set of files could disallow read access to the System Account. For that reason, disk snapshot databases may include every file on disk.
User and group administration information is always provided for the local machine - even if the interactive user is logged onto, for example, the “Workspace Domain,” the EnlightenDSM GUI will list users on the local machine. To get a listing of the users on the “Workspace Domain”, add the Primary Domain Controller for the “Workspace Domain” to your current Network Pool (in the EnlightenDSM GUI, click Configure->Pool Configuration, select your current pool, then click modify.)
On the Network Drive machine:
Insert the EnlightenDSM CD-ROM
Copy the contents of the CD-ROM's folder into a shared filesystem (example: \\networkdrive\sharename\wintel).
On the machine you want to install EnlightenDSM:
Map the Network Drive that contains the wintel installation fileset that you just copied to a drive letter. In the above example, you could map P: to \\networkdrive\sharename by right-clicking on “My Computer,” selecting Map Network Drive..., select Drive: P:, and in Shared Directories:, select \\networkdrive\sharename. Then click OK.
From the Start menu, select Run...
Click Browse..., access the mapped wintel\disk1 directory on the Network Drive, select Setup.exe, and click Open. To continue the example, you could instead type P:\Wintel\Disk1\Setup.exe in the Open: text field.
The Windows installation fileset has been broken up so that it can be copied from the EnlightenDSM CD-ROM onto two floppy disks (to install to machines that don't have a local CD-ROM drive).
To create these installation disks, perform the following steps:
Copy Wintel\Disk1 to Disk 1.
Copy Wintel\Disk2 to Disk 2.
Go to the Windows machine without a CD-ROM and insert Disk 1.
Run a:\Setup.exe.