Guest

Cisco Remote Monitoring Suite Option

Installing the LGMapper Server (Release 4.6)

  • Viewing Options

  • PDF (543.9 KB)
  • Feedback
Installing the LGMapper Server

Table Of Contents

Installing the LGMapper Server

Overview

Backwards Compatibility

LGMapper and LGArchiver Installation Checklist

SQL Server Requirements

Installing the LGMapper and LGArchiver Servers

The Installation Process

Installation Procedure

Controlling Access to LGMapper - Populating User Groups

DCOMCnfg Tool

Overview

Examining LGMapper Properties

Starting DCOMCnfg

Examining the General Tab

Examining the Location Tab

Examining the Security Tab

Examining the Identity Tab

Examining LGArchiver Properties

Troubleshooting the LGMapper Installation

Post-Installation Inspection Checklist

Local Account or User Groups Creation Failures

DCOMCnfg Registry Settings Failure

Database Creation Failure


Installing the LGMapper Server


This chapter explains the process of installing the LGMapper Server and provides information on the use of the DCOMCnfg tool.


Note The installation of the LGMapper Server also includes the installation of the LGArchiver Server.


Overview

The LGMapper and LGArchiver servers are COM servers intended to serve multiple distributed out-of-process clients.

The installation consists of four parts:

Verifying that the Microsoft SQL Server 7.0 Service Pack 2 or higher is installed on the Server (see SQL Server Requirements).

Running the installation script (see Installing the LGMapper and LGArchiver Servers).

Verifying that the installation succeeded (see Controlling Access to LGMapper - Populating User Groups).

Populating User Groups to control access and user rights for the LGMapper and LGArchiver Servers (see Local Account or User Groups Creation Failures).

Backwards Compatibility

There are significant changes in the overall architecture of the Remote Monitoring Suite as compared to AlarmTracker Version 1. However, it is possible to install LGMapper Version 2 on the same computer as LGMapper Version 1. For additional information on this topic, refer to "Backwards Compatibility Considerations" before continuing the installation.

LGMapper and LGArchiver Installation Checklist

This checklist describes the tasks required to install the LGMapper and the LGArchiver Servers.

1. Log on with administrator rights.

2. Ensure SQL Server 7.0 Service Pack 2 or higher is installed on the system (see SQL Server Requirements).

3. Install the LGMapper and LGArchiver Servers (see Installing the LGMapper and LGArchiver Servers).

4. Monitor the installation process (see The Installation Process).

5. Create or modify the default user groups installed to fit within your administrative environment then populate the user groups with the users you want to have access to the LGMapper Server (see Local Account or User Groups Creation Failures).

6. Set up the security and the launch Identity for the LGMapper Server using the DCOMCnfg tool (seeDCOMCnfg Tool).

7. Tune the LGMapper Server environment by using LGMapperCnfg. A critical part of this configuration is specifying the Listener host for the LGMapper Server to connect to. Refer to "LGMapperCnfg and LGArchiverCnfg Tools" for additional information.

8. Set up the security and launch Identity for the LGArchiver Server using the DCOMCnfg tool (seeDCOMCnfg Tool).

9. Tune the LGArchiver Server environment by using LGArchiverCnfg. A critical part of this configuration is specifying the Listener host for the LGArchiver Server to connect to. Refer to "LGMapperCnfg and LGArchiverCnfg Tools" for additional information.

10. Test an AlarmTracker Client installation by starting the AlarmTracker Client on one of the Client systems and verifying the connection to the LGMapper (refer to Starting the AlarmTracker Client).

11. Install the AlarmTracker Client on the end user desktops (refer to Installing the AlarmTracker Client.

SQL Server Requirements

Microsoft SQL Server 7.0 Service Pack 2 or higher must be installed on the LGMapper Server computer prior to running the LGMapper installation program. If SQL Server is not installed, the LGMapper installation will not proceed.


Note When installing SQL Server, specify a Custom installation and select a binary search order during the setup.


Installing the LGMapper and LGArchiver Servers

The Installation Process

During the installation, the following actions occur:

Files are copied from the installation source to the destination folders.

A local user account LGMapper with Administrator privileges is created. When the LGMapper Server is launched by remote Client users, this is the account that LGMapper runs under. You can change this account to another local account or to a domain account using DCOMCnfg (see DCOMCnfg Tool).

Three local user Groups are created (LGM Readers, LGM Users and LGM Administrators).

Registry settings are made related to DCOMCnfg settings. This is an attempt to minimize your interaction with the DCOMCnfg tool, although, as indicated in the DCOMCnfg Tool section, you need to use this tool to grant Client access to the LGMapper Server.

The COM Servers and DLLs are registered.

The databases described in the Installation Procedure Step 9 are created.


Note Due to the installation of shared files, a system reboot may be necessary.


Installation Procedure


Note The LGMapper server installation also includes installation of the LGArchiver server.



Step 1 Log on with administrator rights

Step 2 Insert the Operations Support CD-ROM into the CD_ROM drive (i.e., drive Z).

Step 3 In the Start menu Run command dialog box enter:

Z:\LGMapper Server\Setup.exe and click OK (Figure 3-1).

Figure 3-1 Starting the LGMapper Server Installation

The InstallShield Wizard starts and the InstallShield Wizard Welcome screen (Figure 3-2) appears.

Figure 3-2 InstallShield Wizard Welcome Screen

Step 4 Click Next.

The InstallShield Wizard Information window (Figure 3-3) appears.

Figure 3-3 InstallShield Wizard Information Screen

Step 5 Click Next.

Step 6 Select a destination for the files (see Figure 3-4). You can accept the default location or, by selecting Browse, you can either choose a different existing folder or create and choose a new folder.

Figure 3-4 Choose Destination Folder

In the remainder of this guide, the destination folder you select for these files is referred to as the installation folder.

Step 7 Click Next to continue.

The Select Program Folder screen (Figure 3-5) appears.

Figure 3-5 Select Program Folder

Step 8 Select the default program folder LGMapper2 and click Next to continue.

The InstallShield Wizard copies the files to the installation folder (Figure 3-6).

Figure 3-6 Setup Status

Step 9 Specify the names of the SQL Server databases created during the installation process. It is recommended you use the following default database names (see Figure 3-7):

a. LGAlarms_Template - the default name of a template database used by the LGCnfg tool to create a new Alarms Database.


Note You must create this database so do not leave this field blank.


b. LGMapper_Alarms - the default name of the LGMapper Alarms database.


Note If you are not using the target computer as a LGMapper Server (i.e., it is an LGArchiver Server only), leave this field blank.


c. LGArchiver_Alarms - the default name of the LGArchiver Alarms database.


Note If you are not using the target computer as a LGArchiver Server (i.e., it is an LGMapper Server only), leave this field blank.


Figure 3-7 Specify AlarmTracker Databases

Step 10 Click Next to install the databases.

As each selected database is installed, the following applicable screens are displayed (Figure 3-8, Figure 3-9, and Figure 3-10).

Figure 3-8 Installing the LGAlarms_Template Database

Figure 3-9 Installing the LGMapper_Alarms Database

Figure 3-10 Installing the LGArchiver_Alarms Database

The InstallShield Wizard Complete screen (Figure 3-11) appears.

Figure 3-11 InstallShield Wizard Complete

Step 11 Click Finish.

The installation is complete.


Note If you are directed to reboot your computer, do so. Do not continue the installation process without rebooting if directed.



Controlling Access to LGMapper - Populating User Groups

Remote AlarmTracker clients can not properly use the LGMapper Server after a default (initial) installation. Security is usually the largest issue to resolve in order for users to have a proper access to the LGMapper Server.

Even if you have open security, AlarmTracker clients will not have read/write access to LGMapper unless special Windows user groups exist for the LGMapper to use. These user groups control the privileges that an AlarmTracker client user has.

Three types of access to the LGMapper Server are possible:

Read-only access. Users can see the object hierarchy and all messages, but they cannot clear, assign, exclude, or delete alarm objects. Users in this group have db_datareader access to the AlarmTracker SQL Server Alarms databases.

User access. Users can see the object hierarchy and all messages. They can clear, assign and exclude alarm objects. They can only delete single-state alarm objects. In addition, users in this group have db_datareader access to the AlarmTracker SQL Server Alarms databases.

Administrator access. Users have full control. They can see the object hierarchy and all messages. They can Clear, Assign and Exclude Alarm objects, and they can delete Listener Base Records. In addition, users in this group are given db_owner access to the SQL Server Alarms databases.

To support this functionality, the LGMapper installation creates three local Windows user groups. These three user groups must have the following names:

LGM Readers - this group should only contain users who should have read-only access.

LGM Users - this group should only contain users who can perform all operations on alarm objects except for deleting Listener Base Records.

LGM Administrators - this group should only contain users who can perform all operations on alarm objects including deleting Listener Base Records.

It is important to exactly follow this naming convention because these are the group names the LGMapper Server tries to find when a client connects. If these groups do not exist when you perform the post-installation checklist, use the local User Manager application (Windows NT 4.0) or the Windows 2000 Computer Management MMC snap in to create them.

Whether the groups are local to the machine that the LGMapper is installed on, or a local or global domain group is up to you and your environment. If all your users and machines are part of a single domain, you can create these groups as global domain groups. This means you only have to populate the groups once. If you choose to keep the groups local (maximizing connection performance), you have to populate these groups for each machine you install the LGMapper on. Remember, while the choice of global or local groups is yours, the group names are not. The groups must be named as indicated.

If you do not populate these user groups, users will have read-only access (if they can access the LGMapper Server at all, based on the DCOMCnfg Security settings). The following section (DCOMCnfg Tool) discusses how to accomplish this.

DCOMCnfg Tool

Overview

DCOMCnfg is a Windows utility used to configure general settings for DCOM and specific settings for individual DCOM servers. Settings for specific DCOM servers include setting the authentication level, the location of where the server will run, security settings (such as access and launch permissions), identity of the account under which the server will run, and the preferred protocols and endpoints for communication with remote clients.

DCOMCnfg.exe resides in the System32 directory and is a property-page-based GUI application.

Since LGMapper and LGArchiver are DCOM servers, use DCOMCnfg to administer DCOM properties. This is necessary in order to ensure proper server operation. The following sections detail the steps necessary to configure the LGMapper and LGArchiver Servers for distributed access to after a successful installation.

Examining LGMapper Properties

Examining the LGMapper properties consists of the following:

Starting DCOMCnfg

Examining the General Tab

Examining the Location Tab

Examining the Security Tab

Modifying Access Permissions

Modifying Launch Permissions

Examining the Identity Tab

Starting DCOMCnfg


Step 1 In the Start menu Run command dialog box enter:

C:\WINNT\system32\Dcomcnfg.exe and click OK (Figure 3-12).

Figure 3-12 Starting DCOMCnfg

The Distributed COM Configuration Properties window appears (Figure 3-13). The Applications tab displays a list of the registered DCOM servers.

Figure 3-13 Distributed COM Configuration Properties Window

Step 2 Scroll down to and select LGMapper2 (Figure 3-13). Click Properties.


Note If you do not see LGMapper2 listed, a serious installation problem occurred and the LGMapper Server was not properly registered. Manually register the LGMapper Server by opening a DOS command window, navigating to the Programs > Cisco Systems > LGMapper2 > bin directory, and running the LGMapper2 /RegServer command.



Examining the General Tab


Step 1 Select the General tab.

Step 2 Ensure the Authentication Level is Default .

Figure 3-14 LGMapper2 Properties Window - General Tab


Examining the Location Tab


Step 1 Select the Location tab (Figure 3-15).

Step 2 Ensure only Run application on this computer is checked and all others are unchecked.

Figure 3-15 LGMapper2 Properties Window - Location Tab


Examining the Security Tab


Step 1 Select the Security tab.

The LGMapper2 Properties window Security tab is where the client access permissions are set up. After the installation, the default settings should be Use default access permissions, Use default launch permissions, and Use custom configuration permissions (Figure 3-16). You must customize the access and/or launch permissions so that your AlarmTracker users are able to access the LGMapper Server.

Figure 3-16 LGMapper2 Properties Window - Security Tab Default Settings

The Security tab default settings are used when you first started DCOMCnfg.

For your environment, the system default settings are not likely to be sufficient to connect a general set of users to LGMapper Server. However, even if they are sufficient, you must create and use the three (3) user groups (LGM Administrators, LGM Readers, and LGM Users) as discussed in the Post-Installation Inspection Checklist in order for the users to have proper read/write access to the LGMapper Server. Since these user groups are already built and populated, use them to specify the access and launch permissions.


Note Ensure LGMapper User is part of the LGMapper Administrators Group.


Step 2 Modify the access permissions and/or launch permissions as shown in Modifying Access Permissions and/or Modifying Launch Permissions.

Modifying Access Permissions

a. Check Use custom access permissions to enable the Edit button (Figure 3-17).

Figure 3-17 LGMapper2 Properties - Editing Access Permissions

b. Click Edit (Figure 3-17).

The Registry Value Permissions dialog appears (Figure 3-18).

c. Click Add to add users and/or groups.

Figure 3-18 Registry Value Permissions Dialog Box - Blank

The Add Users and Groups dialog appears (Figure 3-19).

Figure 3-19 Add Users and Groups - Selecting the Local Machine Domain

d. Set the List Names From field to the local machine domain (i.e. Figure 3-19 DOCLAB-NT, the same name as the machine name).

e. Select the LGM Administrators, the LGM Readers, and the LGM Users user groups (Figure 3-20).

Figure 3-20 Add Users and Groups - Adding User Groups

f. Click Add (Figure 3-20). Adding all three groups allow all users in these groups access permission to the LGMapper Server.

Figure 3-21 Add Users and Groups - User Groups Added

g. When the three (3) user groups appear in the Add Names field, click OK (Figure 3-21).

The Registry Value Permissions dialog box appears displaying the user groups and their access permissions (Figure 3-22).

Figure 3-22 Registry Value Permissions Dialog Box- Completed

h. Click OK to return to the LGMapper2 Properties window.

Modifying Launch Permissions

a. Check Use custom launch permissions to enable the Edit button (Figure 3-23).

Figure 3-23 LGMapper2 Properties - Editing Launch Permissions

b. Click Edit (Figure 3-23).

The Registry Value Permissions dialog appears (Figure 3-24).

Figure 3-24 Registry Value Permissions Dialog Box

c. Click Add to add users and/or groups.

The Add Users and Groups dialog appears (Figure 3-25).

Figure 3-25 Add Users and Groups - Selecting the Local Machine Domain

d. Set the List Names From field to the local machine domain (i.e. Figure 3-25 DOCLAB-NT, the same name as the machine name).

e. Select the LGM Administrators, the LGM Readers, and the LGM Users user groups (Figure 3-26).

Figure 3-26 Add Users and Groups - Adding User Groups

f. Click Add (Figure 3-26). Adding all three groups allow all users in these groups launch permission.

Figure 3-27 Add Users and Groups - User Groups Added

g. When the three (3) user groups appear in the Add Names field, click OK (Figure 3-27).

The Registry Value Permissions dialog appears displaying the user groups and their launch permissions (Figure 3-28).

Figure 3-28 Registry Value Permissions Dialog Box- Completed

h. Click OK to return to the LGMapper2 Properties window.

All users in these groups can now launch the LGMapper Server.


Examining the Identity Tab


Step 1 Select the Identity tab.

If the LGMapper installation was successful, the Identity page appears as shown in Figure 3-29.

During installation a local user account called LGMapper was created and set as the launching user for LGMapper. Setting the account as This user is important since you want to assure that only one instance of the LGMapper is launched for multiple Client invocations.

Figure 3-29 LGMapper2 Properties - Identity Tab


Note You may change the user account the LGMapper Server is launched from. However, it is critical that the selected user account can Log on and has batch job rights. The user account must be a member of the LGM Administrators user group.


Step 2 Click OK to return to the Distributed COM Configuration Properties window.


Examining LGArchiver Properties

You can also use DCOMCnfg to examine the DCOM settings for the LGArchiver Server, although you should not have to change anything following the installation. Because the LGArchiver does not have any clients, you will not have to edit the Access and Launch Permissions as you did for LGMapper. In fact, the only client LGArchiver has is the LGArchiverNM service which runs under the SYSTEM account. By default, the SYSTEM account has Launch Permission for all DCOM servers.

However, if you want to examine the DCOM settings for LGArvhiver, you can follow the same steps as for the LGMapper (see DCOMCnfg Tool). To do this, select the LGArchiver Server from the list of applications show in Figure 3-30.

Figure 3-30 Distributed COM Configuration Properties Window

Troubleshooting the LGMapper Installation

If problems occur during the LGMapper and/or LGArchiver Server installations, an error dialog appears informing you of what actions to take to manually resolve the issue. The Post-Installation Inspection Checklist can also be used to help resolve any problems.

Post-Installation Inspection Checklist

Perform the following to ensure a successful installation of the LGMapper Server and the LGArchiver Server:

Ensure the databases have been created by running the SQL Server Enterprise manager (Start>Programs>Microsoft SQL Server 7.0>Enterprise Manager). Expand the SQL Server Group, the "Machine Name" (i.e. DOCLAB-NT), and the Databases nodes as in as in Figure 3-31.

Figure 3-31 Remote Monitoring Suite SQL Server Databases

Ensure the following four (4) new folders exist under the installation folder (Figure 3-32):

bin - contains most of the files from the installation are in the bin folder

log - stores ASCII log files written when the LGMapper and LGArchiver run

scripts - contains SQL Server script files to create the LGAlarms_Template database

helpsample - contains an example of how to implement the IWantHelp interface (see "Implementing the IWantHelp Interface").

Figure 3-32 Installation Folder Sub-directories

Ensure the log folder (Figure 3-33) includes a log file for each SQL Server database (the LGAlarms_Template database, the LGMapper_Alarms database, and the LGArchiver_Alarms database) discussed in the installation procedure. The log files are named utilizing the following syntax:

InitDatabase_<DatabaseName>.log where <DatabaseName> is the name specified in the prompting dialog.

Examine the contents of these files to check for any errors.

Figure 3-33 Log Files

Select Start>Programs>LGMapper2. Ensure the LGMapper2 menu option (Figure 3-34) contains the following applications:

LGArchiverCnfg

LGCnfg

LGMapperCnfg

Listener Base Pruner

Figure 3-34 LGMapper2 Applications

Local Account or User Groups Creation Failures

If the installation process fails to create a local account, or if you decide you want a different account to run the LGMapper Server, you need to create the account using the User Manager or Domain User Manager tool.

It is critical that the account created must have the user rights set to "Log on as batch job". If the account running the LGMapper does not have these rights, LGMapper Server execution fails because of the way DCOM Servers are started by the Service Control Manager (SCM) as requested by Remote Procedure Calls (RPC).

Once you have created or identified the user account that you wish to run the LGMapper Server, run DCOMCnfg (see DCOMCnfg Tool) to set the properties for the LGMapper Server.

Refer to the following procedures (Windows 2000 Procedure and Windows NT Procedure) to verify the a local LGMapper User account was created and is in the Administrators group. In addition, ensure three (3) local User Groups (LGM Administrators, LGM Readers and LGM Users) were created.


Note If you install the LGMapper Server or the LGArchiver Server on a Primary Domain Controller (PDC) or Backup Domain Controller (BDC), they are domain accounts and groups.


Windows 2000 Procedure


Step 1 Run Start>Programs>Administrative Tools>Computer Management.

Step 2 Expand the Local Users and Groups node.

Step 3 Select the Users folder. The LGMapper user account is displayed in the right column (Figure 3-35).

Figure 3-35 Displaying the LGMapper User Account in Windows 2000

Step 4 Double-click LGMapper (Figure 3-35), the LGMapper Properties dialog (Figure 3-36) appears.

Figure 3-36 LGMapper Properties Dialog

Step 5 Select the Members Of tab and double-click on Administrators.

Step 6 Continue at Step 1 of Ensuring LGM Administrators, LGM Readers, and LGM Users Were Created.


-or-


Step 1 Under Local Users and Groups, select the Groups folder (Figure 3-37).

Step 2 In the right column, select the Administrators group (Figure 3-37).

Figure 3-37 Displaying the Administrators Group in Windows 2000

Step 3 Double-click the Administrators group (or right-click and select Properties).

Step 4 Continue at Step 1 of Ensuring LGM Administrators, LGM Readers, and LGM Users Were Created.


Ensuring LGM Administrators, LGM Readers, and LGM Users Were Created


Step 1 Ensure LGMapper is a member of the Administrators group (Figure 3-38).

Figure 3-38 Windows 2000 Administrators Properties Window

Step 2 Select OK to return to the Computer Management window.

Step 3 Ensure Groups is selected.

If the installation process fails to create the three User Groups, or if you decide to use a different model for creating the User Groups, then you have to use the Windows User Manager or Domain User Manager to create and populate these groups.

Step 4 Ensure three (3) local User Groups (LGM Administrators, LGM Readers and LGM Users) were created (Figure 3-39). Refer to Local Account or User Groups Creation Failures.

Figure 3-39 Displaying LGM Administrators, LGM Readers, and LGM Users in Windows 2000


Windows NT Procedure


Step 1 Run Start>Programs>Administrative Tools (Common)>User Manager

Step 2 Ensure LGMapper is listed in the Username (top) section of the User Manager window (Figure 3-40).

Figure 3-40 Displaying the LGMapper User Account in Windows NT

Step 3 Ensure Administrators is listed in the Groups (bottom) section of the User Manager (Figure 3-41).

Figure 3-41 Displaying the Administrators Group in Windows NT

Step 4 Select the Administrators group and double-click it to display the Local Group Properties window (Figure 3-42).

Figure 3-42 Windows NT Local Group Properties Window

Step 5 Ensure LGMapper is a member of the Administrators group.

Step 6 Click OK to close the Local Group Properties window and return to the User Manager window.

Step 7 Ensure three (3) local User Groups (LGM Administrators, LGM Readers and LGM Users) were created (Figure 3-43). Refer to Local Account or User Groups Creation Failures.

Figure 3-43 Displaying LGM Administrators, LGM Readers, and LGM Users in Windows NT

Step 8 Close the User Manager window.


Run DCOMCnfg (refer to DCOMCnfg Tool) to inspect the default settings for the LGMapper and the LGArchiver Servers.

Verify the LGMapperNM and the LGArchiverNM NT Services have been installed (refer to "LGMapperNM and LGArchiverNM", ).

DCOMCnfg Registry Settings Failure

If the installation process fails to create a local account, or if it fails to create Registry setting for DCOMCnfg, use DCOMCnfg to complete the LGMapper Server setup. (refer to DCOMCnfg Tool)

If you do not see LGMapper2 listed, a serious installation problem occurred and the LGMapper Server was not properly registered. Manually register the LGMapper Server by opening a DOS command window, navigating to the Programs > Cisco Systems > LGMapper2 > bin directory, and running the LGMapper2 /RegServer command.

If you do not see LGArchiver listed, a serious installation problem occurred and the LGArchiver Server was not properly registered. Manually register the LGArchiver Server by opening a DOS command window, navigating to the Programs > Cisco Systems > LGMapper2 > bin directory, and running the LGArchiver /RegServer command.

Database Creation Failure

If the installation process fails to create the LGAlarms_Template database, you can create these manually. How this is accomplished is found in "Alarms Database Maintenance".