SG24-4723-00 Systems Management from an NT Server Point of View September 1996
IBML International Technical Support Organization Systems Management from an NT Server Point of View September 1996 SG24-4723-00
Take Note! Before using this information and the product it supports, be sure to read the general information in Appendix D, “Special Notices” on page 175. First Edition (September 1996) This edition applies to V4.0 of TME 10 NetFinity, Part Number 78H5375 and 78H5376 for use with the NT V3.51 Server Operating System. Comments may be addressed to: IBM Corporation, International Technical Support Organization Dept. HZ8 Building 678 P.O.
Contents Preface . . . . . . . . . . . . . . . . . How This Redbook Is Organized The Team That Wrote This Redbook . . . . . . . . Comments Welcome . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Chapter 1. TME 10 NetFinity Overview . . . . . . . . 1.1 What Is TME 10 NetFinity under NT . . . . . . . 1.2 Hardware and Software Requirements under NT 1.
4.1 Installation and Configuration . . . . . . . . . 4.1.1 Windows 3.1 and Windows 95 Installation . . . . . . . . . . . . 4.1.2 NetWare Installation 4.2 Functions and Differences . . . . . . . . . . . . 4.2.1 Windows 95 and Windows 3.11 . . . . . . . . . . . . . . . . . . . . . . . . 4.2.2 OS/2 Warp 4.2.3 NetWare . . . . . . . . . . . . . . . . . . . . 4.3 Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
How IBM Employees Can Get ITSO Redbooks How Customers Can Get ITSO Redbooks . . . . . . . . . . . . . IBM Redbook Order Form Index . . . . . . . . . . . . . . . . . . . 179 180 181 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
vi Systems Management from an NT Server Point of View
Preface This redbook is unique in its detailed coverage of systems management on the NT operating system. In addition, its main focus is on using the IBM systems management tool, TME 10 NetFinity. It provides information on built-in tools that come with NT Server V3.51 as well as the NT Resource Kit. It also shows how to manage from the NT operating system using a new Web browser interface.
This appendix provides a list of the monitors that are available with TME 10 NetFinity on all platforms. The Team That Wrote This Redbook This redbook was produced by a team of specialists from around the world working at the Systems Management and Networking ITSO Center, Raleigh. Barry D. Nusbaum is a Senior International Technical support representative at the Systems Management and Networking ITSO Center, Raleigh.
Chapter 1. TME 10 NetFinity Overview This chapter provides an overview of the TME 10 NetFinity product, as well as shows the installation and configuration of TME 10 TME 10 NetFinity on the NT platform. This includes the hardware and software requirements. 1.1 What Is TME 10 NetFinity under NT TME 10 NetFinity is a set of applications used for systems management and monitoring capabilities.
− • Novell NetWare 3.1x or higher TME 10 NetFinity Version 4.0 (Services or Manager) 2. Hardware requirements: • Personal computer with at least a 80386 processor, depending on the operating system used for this workstation. • 7 - 10 MB (Services); 12-15 MB (Manager) - available hard disk space • At least one LAN adapter with one of the following communications protocol drivers installed: − NetBIOS At least two names, one session and five NCBs are required for NetBIOS.
Figure 1. TME 10 NetFinity Connections 1.3 Installation under NT In this section we describe how to install TME 10 NetFinity under Windows NT as a manager, as well as a client. The TME 10 NetFinity for NT consists of a package of five diskettes or one CD. You first have to decide whether you want to install the TME 10 code as services or manager . On the CD-ROM you will find the code in different subdirectories. The diskettes are labeled TME 10 NetFinity Services or TME 10 NetFinity Manager .
Figure 2. Drive Selection for TME 10 NetFinity Installation Figure 3. Choice of Client User Interface 5. The following are the different types of clients that you can install. Figure 3 depicts what the options are. • Stand-alone client The stand-alone client can only perform TME 10 NetFinity functions locally and has no network interface support installed. This means that the network administrator has no access to this workstation over the LAN using TME 10 NetFinity.
Figure 4. Passive Client User Interface • Active client The active client can perform all TME 10 NetFinity Services locally. See 2.1.1, “ TME 10 NetFinity Functions for Services” on page 12 for a complete list of available functions. It also can react to requests from a TME 10 NetFinity manager over the LAN. Also see Figure 5 for the user interface of this client. Figure 5. Active and Stand-Alone Client User Interface 6.
1.3.2 Installation of a TME 10 NetFinity Manager To install the TME 10 NetFinity Manager code on your workstation you have to insert the first manager diskette and also start the NETFINST program from this diskette. The installation of the TME 10 NetFinity Manager after this is very similar to the services installation except that instead of being asked for the type of client, you are asked whether you want to use your manager with Web Enhancement support or without it.
• Read Me First This is a typical readme file, that provides some hints and tips as well as some general information on TME 10 NetFinity. • TME 10 NetFinity Database Tables If you select this function you will get detailed information on how the database tables, created by TME 10 NetFinity, are structured. This might be very useful, if you create your own databases and want to include the TME 10 NetFinity information in that database.
Figure 9. Network Driver Configuration The main purpose of the network driver configuration is to define the connections to and from the other workstations using TME 10 NetFinity. Let′ s have a look at the following definition fields within this menu and their meanings: • System Name The System Name field can be any combination of alphanumeric characters including blanks. It shows the name of the workstation. This name can be seen later in the management process when monitoring the client groups.
The system keywords are not required for TME 10 NetFinity, but it makes life easier for the network administrators. They are used to identify and group the workstations and servers within the network. If you are running in a stand-alone environment, these keywords won′t be used. The keywords are used within a network environment to identify and define groups among the workstations.
Figure 10. Driver Configurations Options After you have finished your installation as a TME 10 NetFinity manager and you have rebooted your system once to activate the device drivers you will see the following window. You now may use the different functions of TME 10 NetFinity. Figure 11. TME 10 NetFinity Service Manager 1.5 Hints and Tips We didn′t experience any major problems during the installation and configuration of this product.
Chapter 2. NT Systems Management Functions This chapter shows examples of TME 10 NetFinity for NT systems management functions, as well as built-in systems management functions of NT. 2.1 System Management Functions Provided by TME 10 NetFinity Within this chapter we describe all the different TME 10 NetFinity functions available under NT with the appropriate definitions and menu descriptions. There are two different products available for TME 10 NetFinity. 1.
2.1.1 TME 10 NetFinity Functions for Services Figure 12. TME 10 NetFinity Services In the above picture you can see the functions that are available if you install TME 10 NetFinity Services. It is limited to local functions within your workstation. Of course you may also use the same functions as a manager locally. For additional remote functions, see 2.1.2, “ TME 10 NetFinity Functions for Manager” on page 39. 2.1.1.1 System Information Figure 13. System Information Service Figure 14.
details of the information which can be retrieved depends on the hardware and software that is installed. For example, if you have an AT bus-based system installed, then you cannot get any detailed adapter information from this system, because the hardware architecture does not provide you with these details. However, you may use this service on any personal computer, independent of the brand it is.
Selecting this provides you with information on the hard disk controller and its definition as well as information on the connected hard drives and other drives that are also connected to the same controller. An example of this could be a CD-ROM. • Security Information Selecting this gives you details about the installed hardware security features.
Figure 16. Database Selection In addition, you can transfer all information from the System Information Service to a database. Figure 16 shows the format of the definition and that it is possible to also include the System Profile Service Information, which will be discussed in 2.1.1.2, “System Profile Service.” Within 5.5, “Export Data from TME 10 NetFinity to Database” on page 140 you can find more details about how this database looks and how to export this data to the database.
Figure 18. System Profile In Figure 18 you can see the type of information that could be within the system profile. It automatically inserts information about the system which can be gathered via the System Information service, such as type and model serial number. You may now edit the remaining information. This consists of user information such as name, location, address, telephone number, contact names and also some additional information, which you may define on the so-named miscellaneous pages.
Figure 20. Software Inventory To obtain information from the Software Inventory service, TME 10 NetFinity uses a built-in database (for example, DEFAULT.SID file), where all the product information can be found for the inventory process. By choosing the Inventory pull-down menu you can select different inventory functions such as: • Full Directory Search This function looks for all the products defined within the inventory database (.SID file) and tries to find all products in the workstation.
Figure 21. Add New Product The database (dictionary) for the software inventory can be maintained. You first can select different dictionaries for the inventory search. Then there are more ways to actually update this selected dictionary. You may manually update it by adding, deleting or updating the dictionary information using the dictionary pull-down menu. In Figure 21 you can see an example on how to define or update a new or existing product.
generally available for details on the DMI interface. You can find information about that at the following Web site: http://www.dmtf.org All the manufacturers who participated in the DMTF (Desktop Management Task Force) have agreed to implement the DMI standard interface within their products.
Figure 24. DMI Data Flow 2.1.1.5 Security Manager Figure 25. Security Manager Service The Security Manager defines the access profile for accessing the workstation. The definitions will be saved on the workstation and not on the managing workstation. You may define any TME 10 NetFinity Manager user ID and give it different access rights to the different NetFinity Services. This can be done as shown in Figure 26 on page 21.
Figure 26. Security Manager • User ID Here you define the different manager users that are allowed to have access to this workstation from a remote manager workstation. Please be aware that the user defines the access rights for all users that don′ t identify themselves with a user ID and password. This means, that in case a NetFinity Manager just hits the Enter key, when asked for a user ID and password without entering it, he or she will be treated as a public user.
complete access rights, even if they have no access rights themselves to one of the other services. Note: Remember to remove all access rights, including the Security Manager access from the public user. Please define a new manager with Security Manager access, before you remove the rights from the PUBLIC user.
files), DGS (diagnostic files) and ADP (adapter description program) files. By changing this information you may also change the system configuration. So be careful who you give access to this service. Figure 29. System Partition Access In Figure 29 you can see how the system partition may be accessed. In the upper half of the menu you can see the contents of the system partition of the remote system named TFLICK. In the bottom half of the menu you can see the drives connected to the local system.
You may also define an alert due to PFA errors. If a PFA error occurs, you will automatically get an alert depending on how you configured the alert, for example, you may get a pop-up screen. Also see the Alert Manager definitions within this chapter for other types of alerts. Figure 31. Predictive Failure Analysis If you display the PFA information via this icon, you may see two different status possibilities. • Display of hard disk OK, means everything is working fine and no problem was encountered.
Figure 32. PFA Details The above menu gives you more detailed information on the errors that occurred on this drive. In addition to the PUN, LUN, you can also see information such as manufacturer and modify the alerts generated by PFA (severity and message text for the alert log). 2.1.1.9 ECC Memory Service Figure 33. ECC M e m o r y Service ECC memory has the capability to correct single-bit errors. A problem might come up that the memory has an increasing amount of memory errors.
Figure 34. ECC M e m o r y Service Details 2.1.1.10 System Monitor Figure 35. System Monitor Service The System Monitor provides a method to monitor the activities of different resources within a system.
you can find an overview of the different information that you may get from the clients. You will find more details on how to use and configure the monitor functions in the IBM TME 10 NetFinity Services Users Guide . Figure 36. Monitoring Chapter 2.
Figure 37. Threshold Definitions In the above figure you can see how to configure thresholds within the monitor service. You just have to double-click the mouse button on the monitor display to which you want to set up a threshold. Then the threshold definition menu will show up (see Figure 37). You can give this threshold a name and then you have to specify the following data.
will be issued with the alert information at the network administrators workstation. See an example on how to configure this in Figure 39 on page 29 and Figure 40 on page 29. Figure 39. Critical File Monitor Figure 40. Critical File Monitor Definitions Within the monitor definitions for the critical files you can define: • Monitor filename This is the name of the file that should be monitored, including the complete path except the drive ID.
service. See also the description of the severity subject in 2.1.1.12, “Alert Manager” on page 30. • Drive Here you type in the logical drive ID of your drive where the monitored file is located. • File and Directory These are definition areas that make the definition of the file and path for the file that has to be monitored, easier. If these definitions have been completed, don′t forget to select the Monitor button, otherwise the monitoring has been defined, but is not active. 2.1.1.
Figure 42. Alert Action List Figure 43. Alert Action Editor With the Alert action editor, which is accessed by the selecting the Actions button of the Alert Log menu shown in Figure 44 on page 33, you can define all the previously described actions due to different error conditions within the system. • Alert Type Chapter 2.
The Alert Type defines what kind of an alert is being issued such as one of the following. You may also define any if you want to include all possible alert types. • − Unknown − Information − Failure − Warning − Error − All different kinds of alert source information such as system, disk, network, operating system or security Severity The Severity defines how serious a problem is. Normally you would define severity levels 0-7, where 0 is the most serious condition.
Figure 44. Alert Log M e n u The Alert Log menu shows you all alerts, which have been issued or received by this workstation. If you select an alert you will see in the upper half of the screen the complete text of the alert. In our case, we selected the first alert issued at 04:12:29 on August 11th. You can see more details about this alert in this menu such as the type of alert, severity, the application which issued the alert and information about the station from where the alert was received.
Figure 45. View Alert Log The Alert Log View is used to modify the way the alerts are shown within the alert log, such as selecting date/time for the display range. You may also select the alert types that you want to look at. You may select different alert types that you want to display from the alert log. 2.1.1.13 Process Manager Figure 46. Process Manager Service The Process Manager service is used to monitor the different processes that are running in a workstation.
Figure 47. Process Manager Functions After you select the Process Manager service you receive a complete list of actually running processes. If you now select one of these processes and click the right mouse button, you will get an additional pull-down menu as you can see in Figure 47. The functionality of this pull-down menu depends on the operating system of the remote workstation.
• Alert Severity is the severity, which is later being used by the alert manager to identify the alert and issue the appropriate action due to this severity. • Generate.... depending on the required status of this process you have to select at least one of the conditions, which should lead to an alert generation. 2.1.1.14 Serial Connection Figure 49. Serial Connection Service The Serial Connection Service is used to access remote workstations using TME 10 NetFinity and a serial modem link.
You may also use this cascading management function to change the communication protocols within the same LAN. This way you can also access a workstation from your managing station, even if the client only has a network protocol driver installed, which you don′t have on your workstation. In our example the network administrator is working at the local Managing Station-1, which only has the NetBIOS protocol driver installed.
• Number Phone number, which is used to dial to the remote workstation. • COM Port to use Select the appropriate COM port, where the modem is connected to. • Port Baud Rate Select the baud rate for the data transfer to the remote workstation. • User ID The user ID is used to identify your managing workstation to the remote workstation. See also the Security Services definitions in your remote workstation for the appropriate user ID. • Password This is the password for the above mentioned user ID.
2.1.2 TME 10 NetFinity Functions for Manager Figure 53. Remote Administrator Service The user interface shown in Figure 53 shows all the available functions that can be used for the workstation which you have accessed, which means, that only those functions that are supported by the remote workstation are shown within the menu. In addition the supported functions at a workstation can still be limited by the Security Manager function, which will be explained later within this chapter.
• You may also limit the workstation within a group not only by using keywords, but also by using Discovery Filters, which can be defined by clicking on the right mouse button on a group, then selecting Discovery Filters. You may now limit the workstations in this group by selecting the operating systems such as Windows 95, OS/2 and NetWare. Also you can select the protocols that are being used to access protocols such as NetBIOS, IPX and TCP/IP. Figure 55.
Figure 56. Group View - Icons Figure 57. Group View - Details If you now select one of the workstations shown within this group and the public access to this workstation has been removed, you will receive a pop-up window for entering a user ID and a password to access the station. After entering the requested information, you will receive a menu with all the authorized TME 10 NetFinity services for this particular user ID, which you used to log on. Chapter 2.
2.1.2.2 Event Scheduler Figure 58. Event Scheduler Service Up until now, we only discussed the different services that can be used manually by a TME 10 NetFinity manager. The Event Scheduler service can be used to run several services automatically time and date controlled. Figure 59. Event Scheduler - Event List After you select the Event Scheduler service, you get a list of events that have already been defined. You may add, delete or modify any of these events.
First you have to define an event name, which will later be shown in the above mentioned event list. Then select one of the available TME 10 NetFinity services, which might be limited by your manager′s user ID. Then you have to select the task, which is one of the available services. You now have to select the way of selecting the workstations that you want to access by selecting the action buttons Groups or Systems.
Figure 62. Output Definitions Figure 63. Schedule Time and Date In the menu shown in Figure 63, you now define the frequency and the time schedule for this event. You may define a one-time event as well as repeating events (daily, weekly, monthly and yearly). Depending on your selection you also have to give now more details about time and date. After you finish the definitions, click on the Save button to save the configuration and the newly defined event becomes automatically active.
Figure 64. Schedule SW Inventory You can also use other functions such as Software Inventory or File Transfer service. You always have to define the event name, service and frequency. Depending on the defined service you may have to give more details. See Figure 64 for a software inventory example. With software inventory you can create outputs that do the following: • Export to a database. • Generate system reports that show a complete software inventory sorted by systems.
Figure 65. Schedule File Transfer The File Transfer Service in the event scheduler enables you to transfer data to multiple systems at the same time. You then can define the source and target information and define, if you want to copy a single file, single directories or nested directories. In addition, you may also delete files and directories on remote workstations. 2.1.2.3 File Transfer Figure 66.
Figure 67. File Transfer M e n u In the upper half of the File Transfer menu (see Figure 67) you can see the local devices, which are installed in your managers workstation or are logically connected to it using a LAN requester software. In the lower half of the window you can see the drives, which are located in the remote workstation or connected to it by using LAN resources defined by a LAN server software. You can see the logical name of the remote workstation at the top of the lower half of the menu.
system partition can use this function. See 3.1.1, “Alert Manager” on page 95 for a description on how to define a workstation, so that it is enabled to send POED alerts. It will send a broadcast package to all systems running the POED Service. If you have a central systems manager to control all workstations in a multiple segment network, you need at least one system running the POED service per segment and forward the alert to the central manager.
Figure 70. POED Entry Within the menu shown above you can see some more details about the POED error. The arrow shows the component that issued the error condition. In our case it says that there is an error within the adapter configuration. If you click on the Adapter icon, you will receive the window shown in Figure 71. Figure 71. POED Entry Details Within this menu we can see that the error came from adapter slot 3, which shows that the adapter was not responding during power-on.
2.1.2.5 Remote Session Figure 72. Remote Session Service The Remote Session Service can be used to start and control a command session that runs in the remote workstations. This means, for example, if the remote workstation is a Windows NT workstations, then a DOS command prompt will be started in the background of the remote workstation. This session will be controlled by the manager. Figure 73.
2.1.2.6 Screen View Figure 74. Screen View Service The Screen View service is an easy way to capture a screen from the remote workstation. This screen contents is saved and sent to the managing workstation as a bit map file. The screen contents therefore may also be saved in a file at the managing workstation for later problem determination and problem tracking. Also, in case of an error at a workstation, very often there are communication problems between the user and the help desk staff.
2.1.2.7 Web Manager Figure 76. Web Manager Service The Manager Service is used to connect to remote workstations over the Internet or an intranet. Figure 77 shows the connection to remote LANs using this facility. Figure 77. Internet Connection You can monitor remote LANs via the Internet if you can connect to one station within the remote LAN that is attached to the Internet; you only need to have a Web browser installed as a managing workstation.
Figure 78. Web Manager Remote Figure 78 shows the main menu when you are connected to a remote workstation via the Internet. From a functionality point of view there are very few differences if you are connected via the LAN or via the Internet. For example, the user interface for the manager looks a little different as you can see. Look in Chapter 6, “Webability” on page 145 for more details about this subject. Figure 79. Web Manager - System Information Chapter 2.
2.2 System Management Functions Provided by Windows NT Here we describe all the different management functions available provided by NT with the appropriate menu examples and descriptions. This part of the chapter shows examples of the built-in Windows NT systems management and monitoring functions. 2.2.1 Windows NT Disk Administrator The local disks are administered through the Disk Administrator.
with either disk mirroring or, with a second disk controller, disk duplexing. − Volume set A volume set is the combination of two or more various-sized areas of free space on one or more physical disks into one logical drive, treated like a single partition. This mechanism allows you to use the total available disk space more effectively. Volume sets can be extended dynamically by adding more unused space to the set. However, the system must be rebooted before the additional disk space is accessible.
2.2.2 Windows NT Performance Monitor Windows Performance Monitor features two main functions: • Charting and displaying system resources • Generating alerts according to threshold settings This chapter covers the system resources charts. For the alert functions see 3.3, “Alerts by Windows NT Performance Monitor” on page 114. NT Performance Monitor lets you supervise the local or remote Windows NT systems through the network. The system resources shown can be divided into the following groups: 1.
• Server work queues 5. Application resources: • SQL server • SQL server replication published DB • SQL server locks • SQL server log • SQL server user This listing does not contain all possible objects. The shown objects depend on the configuration of the system. All these objects contain multiple counters and a counter can have multiple instances. You can define a graph for every instance or, if the counter does not have multiple instances, for the counter itself.
2.2.3 Windows NT Server Manager Windows NT Server Manager is used to manage systems and their resources on local or remote system within or outside the domain. Besides adding servers and workstations to the domain, promoting backup servers to primary servers and synchronizing the domain, you can do the following system administration tasks. Before you perform any task, select the server to be managed.
2.2.4 Windows NT Event Viewer All events from Windows NT system and subsystems are logged in three log files: • System log • Security log • Application log The Windows NT Event Viewer is the tool to format and read these logs. They can be from the local system or from a remote system through the network. This is the first place to check if you have any problems with the system. The entries are either Information (blue), Warnings (yellow) or Errors (red).
2.2.5 Windows NT Diagnostics Windows NT Diagnostics (WINMSD.EXE) is the Windows equivalent to the MSD.EXE utility included in Microsoft products before. It analyzes the system configuration and displays the data to the user. No changes can be made to displayed values with this tool. Figure 83. Windows NT Diagnostics As you can see in Figure 83, Diagnostics shows you a lot of information about hardware, memory, drivers and much more. It lets you generate a report and send it to a printer or a file.
Figure 84. Windows NT Diagnostics - M e m o r y This utility can only be executed locally as long as it is not used in conjunction with MS Systems Management Server (SMS). 2.2.6 Windows NT Registry Editor The Windows NT Registry is the configuration database for the entire system. Information that used to be in multiple .INI files in different places is now kept in one hierarchically database.
The registry is divided in different hives, one for the system configuration (HKEY_LOCAL_MACHINE) and one for the user profiles (HKEY_USERS). These hives are hierarchically structured and every level can have values and/or one or more sublevels assigned. The Windows NT Registry Editor displays four hives by default: • HKEY_LOCAL_MACHINE • HKEY_USERS • HKEY_CLASSES_ROOT (subtree of HKEY_LOCAL_MACHINE) • HKEY_CURRENT_USER (subtree of HKEY_USERS) Figure 85.
System Contains Windows NT setup information, a control set for each found system configuration and the current control set with the current configuration values. In the hardware and software branch of the tree, you normally don′t have to edit entries. These are made through the installation and configuration program. In the software branch you might found some values that can be changed manually to alter the settings for an application.
2.2.6.2 Entries by TME 10 NetFinity TME 10 NetFinity Manager and Agent makes its own entries into the software branch of the HKEY_LOCAL_MACHINE.
stack that the application was on when the error occurred. The fifth field is the time/date that the error occurred. • The next two log sections indicate what was in the various CPU registers at the time of failure. The 32-bit registers are listed separately in the second register section. • The System Info section provides information about the system and Windows. User name and Organization are taken from Windows .INI files. • The Stack Dump section is divided into frames.
With the License by Server you buy for each server a certain amount of client access licenses and configure them on the server. The amount must match the maximum of concurrent user connections to this server. Multiple connections from one client to the server count as one connection. This type of licensing makes the most sense if users do not connect to multiple servers or do not change servers often. If you choose to license the clients by seat, the amount of clients in the whole network counts.
Figure 86. License Manager - Purchase History This is only an information page. Entries can′t be modified nor deleted. If you add or delete licenses, a new entry will be made. • Product View: Gives you an overview of the installed products, the licenses per mode and how many times accessed. It also shows how the defined number of licenses compares with the actually number of claimed licenses. Figure 87.
• Clients (per seat): Shows the workstation and user name that accessed a product and if a license is provided or not. Figure 88. License Manager - Clients This page shows you all accounted clients and if they have assigned a license or not. Double-click on the system/user name to revoke or upgrade the license. • Server Browser: Displays a tree view of all found domains and their servers with a licensing service running. Figure 89.
license mode from by seats to by server . The Microsoft documentation does inform you that this it is not legal to do this. You can always add a license by clicking on the New License button or choosing License, New License from the top menu. Figure 90. License Manager - New Client Access License Choose the product to add licenses, set the amount of new purchased licenses and add a comment. Click on OK to activate the new licenses. 2.2.8.
Figure 92. License Replication Configuration 2.2.9 Windows NT Replication Service Windows NT provides a service to replicate files and directories from a system to one or more other systems. The sending system is called the export server and the receiving system is the import server. The export server is checking the defined export directory for new, deleted or changed files in regular intervals. If it encounters a change, the import directories of the import server will be updated.
Figure 93. NT User Manager - New User • Click on the Groups button and put the new user into the replicator group by selecting Replicator from the Not Member of window and click on the Add button. Figure 94. NT User Manager - Group Membership • Click on OK to close the Group Membership window. • Click on Add to add the user to the database. • Click on OK to close the New User window. • Close NT User Manager. 2. Configure the Replication Service.
Figure 95. Service Manager - Service Configuration • Click on OK to close the window. A message that replicator status has been granted to the service should be shown. • Click on Start to start the Replicator Service. • Close the Services window when the replicator has been started successfully. 3. Configure the export directories. • Start the Server Manager from the Administrators Tool group. • Select the system with the export server service and choose Computer and Properties from the top menu.
Figure 96. NT Server Manager - Directory Replication • Click on the Manage button to add, configure or remove subdirectories. Figure 97. NT Server Manager - Manage Exported Directories • Add, edit or delete directories. Click on Help for more information about the function of each setting. • Click the OK button three times to close the windows and leave the NT Server Manager. 2.2.9.2 Import Service To configure the Import service do the following: 1.
of logon scrips. If the system you are configuring acts as a logon server with LAN Manager logon scripts, do not alter this path. 6. Click on Add to add names of one or more export servers. By default, the import services imports from the local domain manager. If you make any entries in this list, files will be imported only from the listed servers. 7. Click on the Manage button to add, configure or remove subdirectories to be imported. Figure 98. NT Server Manager - Manage Imported Directories 8.
Figure 99. Windows NT Resource Kit - Program Group With the installation of the Windows NT Resource Kit, additional utilities, not shown in the program group, are copied to the root directory of the Resource Kit. To get more information about these tools, click on the Resource Kit Tools Help push button from the Resource Kit group. This help utility contains the descriptions and explanations for all delivered tools and programs.
Figure 100.
Figure 101. Windows NT Resource Kit - Utilities 2.3.1 Automatic Login and Shutdown Management The NT Resource Kit provides several utilities that help with automating logins and shutdowns of NT. 2.3.1.1 Automatic Login With the Windows NT Autologon Setter (AUTOLOG.EXE) utility you can set Windows NT to log on a user automatically at startup. You have to provide the user ID and the password.
2. Start AUTOLOG.EXE or double-click on the Auto Logon Utility in the Resource Kit window. 3. Enter the password into the Password field as shown in Figure 102. 4. Click on OK to perform the changes in the Registry. To stop the system from automatically logging on do the following: 1. Start AUTOLOG.EXE. 2. Choose the Remove Auto Logon radio button. 3. Click on OK to perform the changes in the registry. Figure 102.
Figure 103. Shutdown Manager (GUI) 2.3.1.3 Shutdown Manager Command (SHUTCMD.EXE) The Shutdown Manager command provides the same functions as the GUI utility, but it can be used in a batch program with the following parameters: Figure 104. SHUTCMD.EXE - Help Screen You can use the shutcmd command in an automated process to reboot systems after performing some system maintenance. Chapter 2.
2.3.2 Process Management 2.3.2.1 Process Viewer (PVIEWER.EXE) The Process Viewer shows you all of the currently running processes and their threads on the desired Windows NT system. You can also see the memory details of the process/thread. If the select process is running on the local system, you can change its task priority or kill the process. Figure 105. Process Viewer The process shown in Figure 105 is from TME 10 NetFinity. 2.3.2.2 The Tools TLIST.EXE and KILL.
Figure 106. TLIST.EXE Output Figure 107. TLIST.EXE Output 2.3.2.3 Process Statistics PSTAT.EXE PSTAT.EXE displays all running processes on the system with a process ID (PID), priority and handles. There is also a line for every thread belonging to the process with the thread ID (TID), the assigned priority and the status of the thread. Run the programs with the parameter /? to get more instruction about using these utilities or see the Resource Kit help utility. Chapter 2.
Figure 108. PSTAT - Listing 2.3.3 Performance Monitoring 2.3.3.1 Performance Monitor PMON.EXE PMON.EXE lists out all running processes with memory usage, CPU usage and also an overview off the overall system load. The screen is updated approximately every 5 seconds. If not all processes are shown, change the properties of the command prompt box to display more lines.
Figure 109. Performance Monitor - PMON.EXE 2.3.3.2 QuickSlice Process Monitor QSLICE.EXE QuickSlice displays all active processes with the process ID and their CPU usage in real time in a graphical interface. Chapter 2.
Figure 110. QuickSlice Process Monitor QSLICE.EXE The QuickSlice window shows two bars per process: • Red bar = kernel time • Blue bar = user time By double-clicking on the image name, a second window is shown with the threads and their CPU usage. Figure 110 has the thread window in the middle of it.
For more information about the usage of the AT command type AT /? in a command line box. You will get a window like the following: Figure 111. Fields for the AT Command With the Windows NT Resource Kit comes a graphical user interface to set, change or delete job schedules. The program name is WINAT.EXE. The Command Scheduler displays the current settings and allows you to create a new job and delete or change an existing job. Figure 112.
2.3.5 Network and Domain Monitoring 2.3.5.1 Net Watch Net Watch (NETWATCH.EXE) lets you supervise one or more NT systems (server or workstation) in the network, shows you the shares and resources to be shared and, if they are in use, by which user they are accessed in a tree view. By double-clicking on an object with the right mouse button and choosing Properties, more detailed information can be seen.
2.3.5.2 Browser Monitor In every Windows NT domain as well as in Windows NT, Windows 95, Windows for Workgroup workgroups is one system, the master browser. Within domains, usually the domain controller supports this function. In workgroups, the first system joining a workgroup becomes the master browser. The master browser allows all other systems within or outside the domain to browse through the systems and their resources known by the browser database.
Figure 115. Browser Monitor - Browser Status By clicking on the Info button, a window with the browsers statistics is shown. Figure 116. Browser Monitor - Browser Statistics Select the refresh rate for Browser Monitor by choosing Options and Intervals. Enter a value in seconds. (Default is 900 seconds.) Do not choose too short of a value because every check causes quite a lot of network traffic.
2.3.5.3 Domain Monitor With the Domain Monitor (DOMMON.EXE) you can supervise multiple domains and the status of the Domain Controller Service and the trusted domains. To do so do the following: 1. Open the Domain Monitor. 2. Add one or more domain by choosing Domain and Add Domain. The status of the domains will be shown with graphical indicators: • A green domain sign indicates that the domain controller is found, is working and all connections are established.
Figure 118. Domain Monitor - Domain Controller Status Windows NT Domain Monitor can not be used on IBM LAN Server Domains or on any workgroups; use it only with Windows NT Server Domains. 2.3.6 Windows NT Setup Manager Windows NT Setup Manager (SETUPMGR.EXE) is a tool to create answer files for unattended or predefined installation of Windows NT. The answer file contains answer values for the input to be provided during the setup process.
Figure 119. Windows NT Setup Manager (SETUPMGR.EXE) By clicking on Network Options you can define the network transport protocol the system should use and select an adapter card. Usually it′s best to let the system autodetect the card. Figure 120. Windows NT Setup Manager - Network Options Note You can not define an IP address for a specific system in the Setup Manager. If your system does not use DHCP Service, you have to set up the information in the file %systemroot%\system32\IPINFO.INF.
; Copyright (C) 1993 Microsoft Corporation ; All rights reserved. ; ; The ipinfo.inf file allows network administrators to provide smart ; defaults for TCP/IP configuration parameters. By modifying this ; template, an administrator can distribute the Windows NT TCP/IP ; software over the network or on floppy disks to users with some ; smart default configuration parameters.
Figure 121. NT Registry Contents Chapter 2.
94 Systems Management from an NT Server Point of View
Chapter 3. Alert Flows This chapter covers alert generation and alert forwarding within Windows NT by looking at two different methods: • Alerts generated by TME 10 NetFinity • Alerts generated by Windows NT Performance Monitor 3.1 Alerts by TME 10 NetFinity Within TME 10 NetFinity, multiple services have the capability to generate alerts and forward them to the TME 10 NetFinity Alert Manager.
If you click on Alert Log Views, you can set a filter to the alert log, depending on predefined profiles. 3.2 View Alert Log To view the alert log, simply click on the alert and the alert details are displayed in the upper half of the window. To set a filter to see only specific alarms do the following: 1. Click on Alert Log Views. 2. Set time and date range if desired. 3. Activate one or more profiles. 4. Check the Enable box for the time and date range and/or the active profiles. 5.
Figure 124. Alert Flow in a Corporate Environment • From each local network the workstations and servers report all their alerts to the Alert Manager of the local TME 10 NetFinity Manager. • The local Alert Manager forwards the alerts to the focal point Alert Manager. • The focal point Alert Manager writes the alerts to its log file and resends the alerts according to the alert type and severity to the alert manager on the workstation of the responsible person.
5. Select one or more Alert Type Depends on the application ID Severity See 3.2.3, “Severity” on page 100 Application ID See 3.2.6, “Applications Sending Alerts to the Alert Manager” on page 104 Application Alert Type Depends on the application ID Sender To receive alerts from remote systems 6. Define an action to be taken if the alert responds to the above definitions (see 3.2.4, “Alert Actions” on page 100). 7. Click on Save to save the new action.
8. Define an action to be taken if the alert responds to the above profiles (see 3.2.2, “Alert Profiles” on page 99). Figure 126. Alert Manager - Action Editor 3.2.2 Alert Profiles Alert profiles are objects that help the user better manage the alerts received by the system. In TME 10 NetFinity many alert profiles are predefined. Open the Profile Editor by clicking on Profiles and browse through the profiles.
6. Enter a name for the new profile in the field Profile Name. 7. Click on Save to save the new profile. Figure 127. Alert Manager - Edit Profiles by Profile Composition 3.2.3 Severity The severity code classifies the importance of an alert. The range is from 0 (Failure) to 7 (Information). The lower the importance of an error the higher the severity code value. That means a severity code of 0 is very important and immediate action should be taken as response to the alert.
The Alert Received window will pop up and display the alarm to the user logged in to the system. • Execute command ′ < P 1 > ′ On every occurrence of the defined alarm condition, the command ′ < P 1 > ′ will be executed in foreground. Include drive, path and parameters in the command statement. The following variables can be passed with the command line as parameters to the command. They are provided from the alert manager and contain alert specific data.
of a defined mail user and the E-Mail address of the receiver (P2) into the appropriate fields. • Add alert to log file Writes the alert to the log file of the Alert Manager. • Export to a DB2 Database This action is only available if the data export to DB2 is defined. It will append a database record for each alert. • Export Database Information via ODBC This action is only available if the data export through the ODBC interface is defined. It will append a database record for each alert.
Figure 128. GENALERT.EXE - Command Line Syntax An example of a genalert and its resulting alert follows: genalert /t:″ Genalert test″ / sev:3 /atype:0001 /APP:user /type:appinf /atype:55 Figure 129. Generated Alert Chapter 3.
3.2.6 Applications Sending Alerts to the Alert Manager For detailed information about the TME 10 NetFinity functions mentioned here, please see 2.1.1, “ TME 10 NetFinity Functions for Services” on page 12. In this paragraph only the alert handling is described. Note Most of the following definitions can be ether done from the administered system itself or remotely through the Remote System Manager. However, all guidelines given here, refer to the managed system. 3.2.6.
Figure 130. Security Manager - User Profile Definition Note In the version we were testing, alerts with a severity code 6 or 7 were not forwarded to other systems nor written to the system log. They were only displayed in the alert log. 3.2.6.2 System Monitor The System Monitor shows you the usage of a variety of system resources on the managed system.
Figure 131. Visible Monitors 3. To define a threshold value, click with the right mouse button on the desired monitor. 4. Choose Open and Threshold to display the threshold definitions. 5. Enter a name for the threshold and press Enter. You must press Enter as tabbing or selecting another field won′t do the job. 6. Define the value and severity for one or more alert conditions: • Error if above or equal to value with severity . • Warning if above or equal to value with severity .
Figure 132. System Monitor Service - System Monitors Figure 133. System Monitor Service - Threshold Definition Chapter 3.
3.2.6.3 Power-On Error Detect The Power-On Error Detect (POED) utility listens to the network segment for systems reporting errors while executing the power-on self test (POST). Systems with system partition can be enabled to report POST errors through the network. They will send a broadcast package to all systems running the POED service.
Figure 134. Predictive Failure Analysis - PFA Options 3.2.6.5 Critical File Monitor The Critical File Monitor supervises system files or other files defined by users and sends an alert to the Alert Manager if one of these files are changed, deleted or created. To define an alert condition do the following: 1. Start the Critical File Monitor. 2. Check the boxes for the System Files and select a severity class if you want these files supervised. 3.
Figure 135. Critical File Monitor - System Files Figure 136. Critical File Monitor - Monitor Additional File 3.2.6.6 Process Manager The Process Manager controls the active System Processes of Windows NT. For every process, an alert can be generated if the process starts, stops or is not running. To define an alert condition do the following: 1. Start the Process Manager. 2. Choose Process and Process Alerts. 3. Click on Add to add a new alert condition.
4. Enter the program execution file name in the field Program, including the file extension. 5. Select the severity class. 6. Select one or more alert conditions. For the Generate alert if program not started field, define a time-out after the program must be active, otherwise the alert is not generated. 7. Check the Notify box. If the Notify box is not checked, no alert will be generated. This is useful if you want a defined alert temporarily to disable. 8. Click on OK to set the condition. Figure 137.
Figure 138. Remote System Monitor - Set System Notification To define a global default alert condition profile do the following: 1. Start the Remote System Manager. 2. Choose Options and System Notification Defaults. 3. Check the boxes to generate the alert if system is online and/or system is offline. 4. Set the Presence Check Interval to the time between two presence checks. 5. Click on OK to set the default alert condition profile. Figure 139.
Figure 140. Remote System Monitor - Set Group System Notification Defaults Warning Consider that a short Presence Check Interval will generate a lot of network traffic, especially if you check on multiple systems. 3.2.6.8 Service Manager The Service Manager controls the TME 10 NetFinity services. It can generate an alert for each time a service or the Service Manager itself is started. This must be enabled in the Network Driver Configuration for the entire system.
Figure 141. Network Driver Configuration - Options 3.3 Alerts by Windows NT Performance Monitor Windows NT Performance Monitor is a part of the Windows NT system. It can supervise a wealth of system functions of Windows NT on the local or remote system. See 2.2.2, “Windows NT Performance Monitor” on page 56 for more details about NT Performance Monitor. This chapter only covers the alerts generation and forwarding. Alerts in Windows NT are triggered from the controller in defined time intervals.
8. Define a threshold condition in the Alert if field. 9. Insert a program name or command in the Run Program on Alert field if desired. Repeat this procedure for all alerts in the profile. 10. Choose Options and Alert from the top menu. 11. Set the interval time (time between two checks on the alert trigger). 12. Insert a network name if you would like to forward the alert through Messenger Service. 13.
instances. This might be desirable, because there is only one interval time setting per profile possible. 3.3.2 Alert Forwarding Windows NT Performance Monitor has very limited ability to forward alerts. It can do so in the following ways: • A run command statement can be defined to be executed either every time an alert is triggered or only the first time. This can be set up for each alert separately. • The alerts can be logged to the Windows NT application log file to be viewed with the Event Viewer.
Chapter 4. Managing Clients Examples of managing clients from the NT platform are shown in this chapter. We tested the functionality of the TME 10 NetFinity Manager running under Windows NT accessing the clients running under different operating systems. The clients were on the following platforms: • Windows NT 3.51 • Windows 95 • Windows 3.11 • OS/2 Warp • OS/2 LAN Server • NetWare 4.1 4.
under NetWare does not use a graphical user interface, because native NetWare 4.1 does not support it. The installation process is simply in a text mode only. It still gives you the full functionality of installing and configuring the NetFinity services. At the end of the installation process you will also be asked for the configuration information such as network protocols, names and keywords.
The Remote Session Service does not start a DOS session in the background of the NetWare servers, but it gives you control of the system console of the NetWare server. This is very similar to the RCONSOLE function of NetWare, but you are not able to switch to a different task in your NetWare server. For example, if your server console is currently showing the NetWare monitor, then you can work within the monitor, but you are able to switch to the server system console.
120 Table 1 (Page 1 of 2). Monitor Functions by Operating Systems Systems Management from an NT Server Point of View Function CPU utilization Windows NT 3.51 Windows 95 Windows 3.1 OS/2 Warp OS/2 LAN Server NetWare 4.
Table 1 (Page 2 of 2). Monitor Functions by Operating Systems Function Windows NT 3.51 Windows 95 Windows 3.1 OS/2 Warp OS/2 LAN Server NetWare 4.
122 Systems Management from an NT Server Point of View
Chapter 5. TME 10 NetFinity Database Support This chapter shows the different databases supported for TME 10 NetFinity and how they can be implemented. You can access databases from Windows applications in the following ways: • Through a database client either on the workstation or as part of the application. • Through the Microsoft Open Database Connectivity (ODBC) interface driver.
5.1 Database Support with ODBC Drivers This section shows the new ability of TME 10 NetFinity to use the ODBC interface. ODBC drivers in Windows allows you to access many different database products through a standardized interface. Microsoft′s ODBC provides a common SQL (Structured Query Language) syntax for communication between applications and database management systems (DBMS).
Figure 147. Automatic Startup of Database Services 4. Create a new database for the TME 10 NetFinity data. Open the DB2 Command Line Processor and enter the following commands to create a new database: • db2 => start database manager • db2 => create database NETFINS For more help about the DB2 Commands type ? command or refer to the online reference. Figure 148. Create DB2 Database NETFINS 5.2.2 Install and Configure DB2 ODBC Support 1.
Figure 149. Create DB2 Database NETFINS This installs the IBM DB2 ODBC Driver and creates a new Program Manager group with the name ODBC and puts the 32-bit ODBC administrator in it. Figure 150. 32-Bit ODBC Administrator 2. Start the 32-bit ODBC Administrator from the newly created ODBC group. 3. In the Data Sources windows choose Add.... Figure 151.
4. From the installed ODBC drivers, choose IBM DB2 ODBC DRIVER and click on OK. Figure 152. 32-Bit ODBC Administrator - Add Data Source 5. Select the newly created database in the Database Alias field and add a description in the Description field. Then click on OK. Figure 153. 32-Bit ODBC Administrator - I B M DB2 ODBC DRIVER 6. Close the Data Source window. The IBM DB ODBC driver is now installed and the defined databases are available to all applications using the ODBC interface. 5.2.
Figure 154. TME 10 NetFinity Administration 2. Choose the database to use with TME 10 NetFinity. Figure 155. Database Selection 3. Enter the user ID and password to log on to the database. The user ID and the password depends on the database definition. This user ID must have the right to create and delete tables in the database. The user ID and password you were logged in with when creating the database is automatically granted the appropriate database access rights.
Figure 156. TME 10 NetFinity Database Access 4. Check the Results window for any errors. If no error occurred, the system will show you the following window: Figure 157. TME 10 NetFinity Database Administration Results TME 10 NetFinity is now ready to export collected data to the DB2 Database for Windows NT. To check this, open TME 10 NetFinity Service Manager, start System Information and wait until the system has collected the data. From the System Information window choose File and Database.
Figure 158. System Information Tool Data Exported Note The IBM DB2 ODBC Driver supports only 32-bit applications. With 16-bit applications the Microsoft 16-bit ODBC Driver must be installed. For how to work around the problems with a 16-bit Windows application check out the text file DB2ODBC.TXT in the \SQLLIB directory. 5.
Figure 159. Microsoft SQL 6.5 2. On the SQL Server System start Microsoft SQL Enterprise Manager. 3. Register your server to the Enterprise Tree if it does not appear in the tree. 4. Click on your server in the tree and choose Server from the top menu. Figure 160. Microsoft SQL Enterprise Manager - Server Manager Tree View 5. Select Configurations... to open the Server Configuration window. 6.
Figure 161. Microsoft SQL Enterprise Manager - Server Configuration, Server Options 7. On the Security Options page set Login Security Mode to Windows NT Integrated. This will allow all users defined in the domain or locally on the system to access the database.
Figure 162. Microsoft SQL Enterprise Manager - Server Configuration, Security Options Next, you have to create a new database. For better performance it should be created on a separate device. A device is a part of the disk reserved for use by databases. Within this space multiple databases can be placed. For each database, you must allocate a place to store the data log itself and a place to store log entires. In our case the data and logs will be put into same device.
Figure 163. Microsoft SQL Enterprise Manager - Manage Databases 9. Click on the New Database icon (the left of the three icons in the upper left corner) to open the window to create a new database (see Figure 165 on page 135). 10. Choose < n e w > in the Data Device drop-down box and a window to create a new device will appear. Figure 164. Microsoft SQL Enterprise Manager - New Databases Device In the lower half of the window, the local drives with the available disk space for new devices is shown.
already use the whole device or leave some space for further expansions of the database. Figure 165. Microsoft SQL Enterprise Manager - New Database If you click on OK, the database is created and should be shown in the Manage Databases window. 12. To enable TME 10 NetFinity to use the new database, a specific database user must be created with all access rights to the database. This user must be named NETFIN. Choose Manage and Logins from the top menu.
Figure 166. Microsoft SQL Enterprise Manager - Managing Logins 13. After creating the user, appropriate rights must be granted to it. Again select Manage and Databases. Double-click on the TME 10 NetFinity Database Name in the graphic to edit the database properties. Select the Permissions page and grant all rights to the NETFIN user as shown in Figure 167 on page 137. Click on Modify, then on Close.
Figure 167. Microsoft SQL Enterprise Manager - Edit Databases, Permissions 14. Click on OK to close the Edit Database window and close the Microsoft SQL Enterprise Manager. Looking at an SQL 6.5 view of the Server Manager, you would see the following: Chapter 5.
Figure 168. Microsoft SQL Enterprise Manager - Managing Logins 5.3.2 Install and Configure Microsoft ODBC Support If the ODBC Support is not already installed, you need to install it from the SQL Server CD. After installation do the following to set up the database support: 1. Open the Windows NT Control Panel from the Main Group and choose ODBC. 2. In the Data Source window choose Add. 3. Choose SQL Server from the installed ODBC Drivers. 4.
Data Source Name: Alias or name of the TME 10 NetFinity database Description: A brief description of the database Server LOCAL (Select the server name if you have Microsoft SQL Server running on another system and are connecting through the network.) Database Name: Name of the TME 10 NetFinity database in the SQL Server Figure 169. MS ODBC - ODBC SQL Server Setup 5. Close all windows and return to the Program Manager. 5.3.
5.4 TME 10 NetFinity with Direct Access to the IBM DB2 NT Database Since TME 10 NetFinity supports database access through the ODBC interface, direct access to the database is not supported anymore. However, it still works the same as it has in older versions. The only problem is creating the database tables. The NetFinity database creation program NETFINDB.EXE is not included anymore in the delivered diskettes or CD install image. The only way for you to create the tables is through the ODBC interface.
− Select Export Database Information via ODBC and check the boxes if you would like to include the System Profile and/or Syslevel information. Figure 170. System Information - Database Export − Select the database to export to and click on OK to save the data. Figure 171. Database Selection • System Profile The export of the System Profile data can be included while saving data from System Information. • Software Inventory Software Inventory lets you save the search results to the database.
System Monitor lets you collect data during a certain period of time and store them into the database. This data can later be used for reports. To save data to a database do the following: − Open the System Monitor Service. − From the System Monitor Service top menu choose Windows and select Export to Database. − Select the database to export to one or more monitors and define the time period to be monitored. Figure 172.
5.6 Query the TME 10 NetFinity Database With TME 10 NetFinity no utility to query the database is provided. Depending on the database that contains the TME 10 NetFinity data, different programs can be used for example, to query Microsoft SQL Server Microsoft ISQL/w (provided with SQL Server) or Microsoft Query (provided with Microsoft Excel). The only tool provided with IBM DB2 for Windows NT is the DB2 Command Line Processor where you can enter SQL statements to query the database.
144 Systems Management from an NT Server Point of View
Chapter 6. Webability This chapter shows how to use a Web browser workstation to remotely manage your environment. 6.1 Internet Connections to TME 10 NetFinity This chapter shows the different ways to connect from a managing workstation to remote workstations or LANs over the Internet using the TME 10 NetFinity 4.0 product.
Figure 174. Internet Connection There are some prerequisites for getting remote access. Of course you have to have a hardware connection to the Internet, which might be established in several ways, depending on your logical connection. Let′s have a look at the different possibilities. For all of the possible connections to the remote site there are the following prerequisites for the local TME 10 NetFinity Manager: 1. NetFinity Manager code must not have been installed.
• Directly connecting to the Internet with a TCP/IP address provided by a service provider. 6.1.1 Accessing Remote LANs Using an Internet Server on the Remote Site Figure 175. Connection Using Internet Server A prerequisite for this solution is that you have a registered Internet server installed at your remote location. On this Internet server the TME 10 NetFinity Manager code must also be installed to enable the access to the server using TME 10 NetFinity.
TME 10 NetFinity manager with dedicated TCP/IP addresses and not configure the access with any remote host access. This is very important, because if you don′t restrict this access, then you might compromise security and your LAN would be open to any Internet user, if this user has the TME 10 NetFinity code installed and got information about one of your TCP/IP addresses.
6.1.2 Accessing Remote LANs Using a Service Provider Figure 176. Connection Using Service Provider The easiest way to use the Internet access facilities is to use an Internet service provider, for example, CompuServe. These service providers give you with an official Internet address for your workstation, which may be used to access your local managing workstation. See the information below for an explanation. You may get access to the Internet on either or both sites using a service provider.
ask you to define a specific connection within your network for this access. This means, that you may have to install and define a gateway for this connection at a fixed phone number/connection and you might only be able to access this remote LAN using the service provider only through this defined connection. This might also gives you more security for your connection. Please check with your service provider on these details. For example, we checked with CompuServe to see if this is possible.
provided by a service provider and the Internet connections have been established. 4. The gateway workstation to the Internet also has the TME 10 NetFinity Manager code installed. 5. The TME 10 NetFinity Manager at the Internet gateway workstation has the proper security configuration set up, so that the local managing workstation is allowed to access this system. See 6.2, “Configuration of the Web M a n a g e r ” for details on how to set up the configuration. 6.
Figure 179. Web Manager Configuration Figure 179 shows the definition screen for the Web access to your gateway. You at least have to enable the Web Manager and define a Web server socket. • 152 Web Manager defines the status of the Web access to your gateway with: − Enabled means that in general the access to your gateway from the Internet is enabled.
− Any Remote Host - Means, that anybody, who manages to get the connection to your gateway may access at least the main menu of the gateways TME 10 NetFinity Manager. How far these users can get then depends on the Security Managers definitions in the gateway or the managing workstation, which you should define very carefully. See also 2.1.1.5, “Security Manager” on page 20 for details on the Security Manager definitions.
Figure 181. TME 10 NetFinity Main M e n u When you try to access a gateway from a TME 10 NetFinity managing workstation you first have to start a Web browser. In our example we use Netscape running under Windows NT 3.51 and under AIX. It should also soon be supported on OS/2. Of course, the same functions are also available using other Web browser software products like OS/2 WebExplorer. Each make of the Web browsers have slightly different functions, so you need to be aware of their capabilities.
Note These are just examples that were suitable for our environment. The host name shown above and the TCP/IP address are not accessible from outside the IBM firewall. Also, the socket address of 411 is a default address that you can change when you configure the Webability function. HTTP://NTCLI1.ITSO.RAL.IBM.
Figure 182. Remote System Manager In our example we selected the Remote System Manager service, because we didn′t want to monitor the gateway, but the workstations connected to the LAN. After selecting the Remote System Manager you get a list of already defined groups, which you also may edit the way you did when you were defining and editing groups locally.
Figure 183. Group Details If you now select a group, then you have the same display functions as you had with the regular TME 10 NetFinity interface. This means that you can view the groups either as an Icon View or with the Group Details View. With the Group Details menu shown in Figure 183 you can see one of the groups we defined in this managing workstation. From the background color of the workstations icon you can easily recognize the status of it.
Figure 184. RAID Information 1 of 2 In our example we selected an IBM PC Server 520 and then we selected the RAID Manager service. The information from this service can be seen in Figure 184 and Figure 185 on page 159. Using the Internet access to TME 10 NetFinity functions usually provides you with detailed information right away instead of forcing you to drill down through many menus to get to the information. This saves the company time and money.
Figure 185. RAID Information 2 of 2 There are also some differences with the other TME 10 NetFinity services via the Internet. Following you will see two menus that show the some of the information that you get from the System Information service. In Figure 186 on page 160 you can see the overview of the information available for the system information. Next select one of the functions such as Adapter Information. If you select one of the functions, you will go directly to the requested information.
Figure 186. System Information Icons Figure 187. System Information Details Another example of how the TME 10 NetFinity services look when using the Web interface is the following. We were using the event scheduler to schedule the usage of the system information service.
Figure 188. Event Scheduler Definition 1 of 3 It is very easy to use the event scheduler function using the Web service, because you don′t have to go through several different definition menus; you get all the required definitions in one. Figure 188 through Figure 190 on page 163 shows the configuration menus for this function. Chapter 6.
Figure 189.
Figure 190. Event Scheduler Definition 3 of 3 Chapter 6.
Figure 191. Event Scheduler Results Note The failures in the scheduled activities were due to the fact that the public user ID did not have access to the sysinfo service. After updating the security information, we successfully ran the service, using the scheduler function. 6.3.1 Limitations When Using the Web Manager There are a few limitations if you will be using the TME 10 NetFinity Manager with a Web browser. In this chapter we show you these restrictions and requirements. 1.
3. Be careful that you are not defining a TCP/IP socket number that is already used by another Internet server. 4. When accessing a workstation with the Web manager, you will see all available TME 10 NetFinity services on the remote workstation, but some of them might not be available to you. This is different from a connection using a local LAN protocol, where you only receive the icons for the services for which you have access. 5.
166 Systems Management from an NT Server Point of View
Appendix A. Application Alerts and Alert IDs Table 2 (Page 1 of 2).
Table 2 (Page 2 of 2).
Appendix B. List of Supported Modems Table 3 (Page 1 of 2). Supported Modems for TME 10 NetFinity Copyright IBM Corp. 1996 Manufacturer Type/Model Aspen 14.4IFX 28.8IFX 14.4EFX 28.8EFX Bocamodem MV.34I MV.34E M144AE Cardinal MVP288XF Hayes ACCURA 9 6 + F A X 9 6 ACCURA 9 6 B + F A X 9 6 ACCURA 1 4 4 + F A X 1 4 4 ACCURA 1 4 4 B + F A X 1 4 4 ACCURA 288V.FC+FAX OPTIMA 9 6 + F A X 9 6 OPTIMA 9 6 B + F A X 9 6 OPTIMA 1 4 4 + F A X 1 4 4 OPTIMA 1 4 4 B + F A X 1 4 4 OPTIMA 288V.34/V.
Table 3 (Page 2 of 2). Supported Modems for TME 10 NetFinity 170 Manufacturer Type/Model Practical Peripherals PC144T2 PC144T2-EZ PM14400FXMT PM288MT II V.34 USRobotics Sportster 14,400 FAX Modem Sportster 28,800 FAX Modem VIVA 14.
Appendix C. TME 10 NetFinity Monitors Here is the list of NetFinity monitors for Version 4.0 plus NetFinity Partners monitors: C.
IP Packets Received IP Packets with Errors TCP Connections Unicast Packets Sent Broadcast Packets Sent Unicast Packets Received Broadcast Packets Received Bytes Sent Bytes Received C.3 NetWare 3.x/4.x Monitors CPU Utilization Cache Blocks in Use Percent of Cache in Use Process Count Thread Count Volume Space Used Volume Spaced Remaining Connected Users C.4 Windows 3.x and Windows 95 Monitors CPU Utilization Disk Space Used Disk Space Remaining Memory Usage Locked Memory Windows Resources Disk Workload C.
C.5.
*DirtyDirDelay *MaxConnDirWrites *MaxDirCacheBuffers *MinDirCacheBuffers *MaxRecvBuffers *MaxServProcs LAN Adapters Total Packets Sent/Min Total Packets Received/Min *No ECB Available Count/Min *Send Packet Too Big Count/Min *Send Packet Too Small Count/Min *Receive Packet Overflow Count/Min *Receive Packet Too Big Count/Min *Receive Packet Too Small Count/Min *Send Packet Miscellaneous Errors/Min *Receive Packet Miscellaneous Errors/Min *Send Packet Retry Count/Min *Checksum Errors/Min *Hardware Receive Mi
Appendix D. Special Notices This publication is intended to help technical support personnel implement systems management using NetFinity V4.0 on the NT platform. In addition, it will help show how to use other built-in systems management functions. The information in this publication is not intended as the specification of any programming interfaces that are provided by TME 10 NetFinity.
DB2 IBM Mwave NetView OS/400 Predictive Failure Analysis WebExplorer 400 FFST/2 Micro Channel NetFinity OS/2 PowerPC SystemView XGA The following terms are trademarks of other companies: C-bus is a trademark of Corollary, Inc. PC Direct is a trademark of Ziff Communications Company and is used by IBM Corporation under license. UNIX is a registered trademark in the United States and other countries licensed exclusively through X/Open Company Limited.
Appendix E. Related Publications The publications listed in this section are considered particularly suitable for a more detailed discussion of the topics covered in this redbook. E.1 International Technical Support Organization Publications For information on ordering these ITSO publications see “How To Get ITSO Redbooks” on page 179.
178 Systems Management from an NT Server Point of View
How To Get ITSO Redbooks This section explains how both customers and IBM employees can find out about ITSO redbooks, CD-ROMs, workshops, and residencies. A form for ordering books and CD-ROMs is also provided. This information was current at the time of publication, but is continually subject to change. The latest information may be found at URL http://www.redbooks.ibm.com.
How Customers Can Get ITSO Redbooks Customers may request ITSO deliverables (redbooks, BookManager BOOKs, and CD-ROMs) and information about redbooks, workshops, and residencies in the following ways: • Online Orders (Do not send credit card information over the Internet) — send orders to: In United States: In Canada: Outside North America: • • United States (toll free) Canada (toll free) 1-800-879-2755 1-800-IBM-4YOU Outside North America (+45) 4810-1320 - Danish (+45) 4810-1420 - Dutch (+45) 4810-15
IBM Redbook Order Form Please send me the following: Title Order Number Quantity • Please put me on the mailing list for updated versions of the IBM Redbook Catalog. First name Last name Company Address City Postal code Telephone number Telefax number • Invoice to customer number • Credit card number Credit card expiration date Card issued to Country VAT number Signature We accept American Express, Diners, Eurocard, Master Card, and Visa.
182 Systems Management from an NT Server Point of View
Index A H active client 5 Adapter Details 13 Alert Actions 31 Definitions 31 Logs 33 Process Alerts 35 Alert Manager 30, 31 Alerts 29 Hints and Tips 10 Host Access Definition HTTP 154 I Installation 3, 117 Installation of TME 10 NetFinity Manager TME 10 NetFinity Services Internet 145 Browser 146 CompuServe 149 Server 147 Service Provider 149 Web Manager 151 B bibliography 177 C Clients active 5 Passive 4 Standalone 4 COM port 38 CompuServe 149 Configuration 7, 117, 152 Connections 2, 145, 146, 150 C
Power-On Error Detect 47 Predictive Failure Analysis 23 Process Alerts 35 Process Manager 34 PUN 24 R RAID Manager 22 Remote Hosts 152 Remote Session 50 Remote System Manager Requirements 1, 146 39, 156 TME 10 NetFinity functions (continued) Security Manager 20 Serial Connection 36 Software Inventory 16 System Information 12 System Monitor 26 System Partition Access 22 System Profile 15 Web Manager 52 U Utilization 26 S W Scheduler 45 Screen View 51 Security 10, 21 Security Manager 20 Serial Connect
IBML Printed in U.S.A.
