manuals.online logo
Brands
  1. Home
  2. •
  3. Brands
  4. •
  5. ICP
  6. •
  7. Software
  8. •
  9. ICP GDTMON User manual

ICP GDTMON User manual

This manual suits for next models

1

Other ICP Software manuals

ICP ICPCON User manual

ICP

ICP ICPCON User manual

ICP MS Windows NT Guide

ICP

ICP MS Windows NT Guide

ICP ICP Controller Guide

ICP

ICP ICP Controller Guide

ICP Interactive UNIX Guide

ICP

ICP Interactive UNIX Guide

ICP Novell NetWare Guide

ICP

ICP Novell NetWare Guide

Popular Software manuals by other brands

Red Hat ENTERPRISE LINUX 4 -  FOR X86-ITANIUM AND... installation guide

Red Hat

Red Hat ENTERPRISE LINUX 4 - FOR X86-ITANIUM AND... installation guide

Avaya OAISYS NetSuite 4.2 Application notes

Avaya

Avaya OAISYS NetSuite 4.2 Application notes

Asante SmartBridge V1.0 user manual

Asante

Asante SmartBridge V1.0 user manual

Xerox Wide Format 6204 installation guide

Xerox

Xerox Wide Format 6204 installation guide

SAS Scalable Performance Data Server 4.5 Administrator's guide

SAS

SAS Scalable Performance Data Server 4.5 Administrator's guide

Lucid FM2A85X Extreme6 installation guide

Lucid

Lucid FM2A85X Extreme6 installation guide

Juniper JUNOS PUS MOBILE SECURITY SUITE datasheet

Juniper

Juniper JUNOS PUS MOBILE SECURITY SUITE datasheet

GRASS VALLEY NETCONFIG V2.0.12 instruction manual

GRASS VALLEY

GRASS VALLEY NETCONFIG V2.0.12 instruction manual

Epson Stylus Pro 9880 ColorBurst Edition - Stylus Pro 9880... Getting started

Epson

Epson Stylus Pro 9880 ColorBurst Edition - Stylus Pro 9880... Getting started

COMPRO COMPROFM manual

COMPRO

COMPRO COMPROFM manual

Muratec OFFICEBRIDGE ONLINE user guide

Muratec

Muratec OFFICEBRIDGE ONLINE user guide

Oracle Contact Center Anywhere 8.1 installation guide

Oracle

Oracle Contact Center Anywhere 8.1 installation guide

Avaya NULL One-X for RIM Blackberry user guide

Avaya

Avaya NULL One-X for RIM Blackberry user guide

HP ProLiant BL420c user guide

HP

HP ProLiant BL420c user guide

PS Audio PowerPlay Programming manual

PS Audio

PS Audio PowerPlay Programming manual

Brady LOCKOUT PRO 3.0 Administrator's guide

Brady

Brady LOCKOUT PRO 3.0 Administrator's guide

Avaya Interaction Center user guide

Avaya

Avaya Interaction Center user guide

Texas Instruments TI-83 Plus Silver Edition Guide book

Texas Instruments

Texas Instruments TI-83 Plus Silver Edition Guide book

manuals.online logo
manuals.online logoBrands
  • About & Mission
  • Contact us
  • Privacy Policy
  • Terms and Conditions

Copyright 2025 Manuals.Online. All Rights Reserved.


&KDSWHU.'LDJQRVLV3URJUDP*'7021
&KDSWHU.
7KH
'LDJQRVLV3URJUDP
*'7021

&KDSWHU.*'78VHUV0DQXDO
.7KH'LDJQRVLV3URJUDP*'7021
GDTMON (GDT monitor) is a helpful and flexible diagnosis tool for the monitoring, mainte-
nance and tuning of mass storage subsystems which are based on one or more ICP Con-
trollers. The key features of GDTMON:
Diagnosis program with a graphical user interface. Clear performance representation
with variable horizontal bars
Available under MS-DOS, NetWare 3.x & 4.x, Windows 95, Windows NT, OS/2 and
SCO UNIX
Loadable locally (on the server) or remotely from an authorized workstation (NCPE
and NETBIOS protocol support)
Indicates the performance, expressed in [KB/sec] and [IO/sec], of:
- Host Drives (Disk, Chain, RAID 0, 1, 4, 5, 10)
- Logical Drives
- SCSI Drives
Indicates the GDT cache utilization
- Read-Hits
- Write-Hits
- Separate indication for data- and parity-cache (RAID 4/5 )
Allows online changing of the GDT cache parameters:
- Cache ON/OFF
- Delayed Write ON/OFF
Allows online changing of the SCSI devices’ parameters:
- SCSI protocol
- Synchronous or Asynchronous data transfer
- Setting of the synchronous data transfer rate
- Disconnect/Reconnect
- Disk Cache ON/OFF
- Tagged Queues ON/OFF
Indicates the structure of Logical, Array and Host Drives
Performs online parity checking of RAID 4 and RAID 5 Host Drives
Allows the online RAID Level migration and capacity expansion of existing Array
Drives
Saves all relevant configuration data to floppy disk or hard disk
Sets up or removes RAID 1 Disk Arrays while maintaining full operational conditions
Performs Hot Plugs on RAID 4 / RAID 5 disk arrays
Allows to add or remove a dedicated or pool Hot Fix drive while maintaining full op-
erational conditions

&KDSWHU.'LDJQRVLV3URJUDP*'7021
./RDGLQJ*'7021
As mentioned before, the GDTMON program is available for various operating systems.
It can be used either locally or remotely. This means that all ICP Controllers in a network
can be monitored and serviced from one (or several) workstation(s). The communication
between the ICP Controller(s) and the GDTMON program is based on the NETBIOS or NCPE
protocols. Thus, for example, it is possible to monitor the ICP Controller in an OS/2 work-
station or the ICP Controller in the Novell NetWare fileserver from a Windows 95 worksta-
tion.
In order to be able to access a certain computer system with its ICP Controller remotely on
the network, a special communication module has to be loaded first, which routes the in-
formation through the network. For a Novell NetWare fileserver this is the CTRLSRV.NLM
module (NCPE). For Windows NT (server and workstation), Windows 95 and OS/2 (server
and workstation) this is the NBSERVx.EXE module (NETBIOS). While the module is loaded
it searches for a CTRLSRV.CFG (Novell NetWare) or NBSERV.CFG (Windows NT, Windows
95 and OS/2) file, which includes the definition of the access rights of the different users
and their passwords. The CFG file assigns every user to two different access levels. Access
level 0 gives the user all functions to view and change the controller-, disk-drive and disk-
array-settings. Access level 1 entitles the user only to view the various settings and per-
formance data.
The Windows NT, Windows 95 and OS/2 driver diskettes include so-called DLLs for the sup-
ported protocols. Example: If the MON4NETB.DLL file is located in the same directory as
GDTMON.EXE file for Windows NT, the NETBIOS protocol is automatically used for the
GDTMON on this system. As soon as the NETBIOS support of this operating system is in-
stalled during the network configuration, the GDTMON on this system can communicate
through this protocol with another system in the network which has a ICP Controller.
The following drivers for the ‘remote’ GDTMONitor are currently available:
OS/2
GDTMON32.EXE GDTMONitor for OS/2
MON2NETB.DLL NETBIOS DLL for OS/2
MON2NCPE.DLL NCPE DLL for OS/2
NBSRV2.EXE NETBIOS Server for OS/2
NBSRV.CFG Configuration file for NetBios Server
NBCLEAN2.EXE NETBIOS analysis program
Windows NT
GDTMON.EXE GDTMONitor for Windows NT
MON4NETB.DLL NETBIOS DLL for Windows NT
NBSRV4.EXE NETBIOS Server for Windows NT
NBSRV.CFG Configuration file for NETBIOS Server
NBCLEAN4.EXE NETBIOS analysis program
Windows 95
GDTMON.EXE GDTMONitor for Windows 95
MON5NETB.DLL NETBIOS DLL for Windows 95
NBSRV5.EXE NETBIOS Server for Windows 95
NBSRV.CFG Configuration file for NETBIOS Server
NBCLEAN5.EXE NETBIOS analysis program
The MS-DOS GDTMON also allows remote access. The DLLs are integrated into the GDT-
MON.EXE file, thus there is no NETBIOS server available for MS-DOS. Since there is no
NETBIOS support within MS-DOS, it is necessary to load the NETBIOS program to access
from a MS-DOS workstation through the network a ICP Controller in a Windows NT and

&KDSWHU.*'78VHUV0DQXDO
OS/2 workstation or server, or a Windows 95 workstation. NETBIOS is part of the Novell
NetWare operating system. For the remote access of a Novell NetWare fileserver the
NETBIOS program is not needed.
..//RRDDGGLLQQJJWWKKHH**''7700221133UURRJJUUDDPP88QQGGHHUU11HHWW::DDUUHH
The GDTMON program for NetWare is part of the GDT Novell NetWare disk.
GDTMON can be used either under NetWare 3.1x or under NetWare 4.0x. There are two dif-
ferent methods of loading GDTMON:
- loading GDTMON on the fileserver
- loading GDTMON on an authorized workstation (remote)
Loading GDTMON on the fileserver. Beforehand, the GDT NetWare driver (GDTRP311.DSK
for NetWare 3.11, GDTRP312.DSK for NetWare 3.12 and GDTRP400.DSK for NetWare 4.x)
and the auto-loading module CTRLTRAN.DSK must have been loaded on the fileserver.
LOAD GDTMON <ENTER>
on the fileserver.
Loading GDTMON on a workstation. In this case, too, the GDT NetWare driver and the
auto-loading module CTRLTRAN.DSK must have been previously loaded on the fileserver
console. In addition, the module CTRLSRV.NLM has to be loaded. This module searches for
a file named CTRLSRV.CFG. This file must be located in the same directory as
CTRLSRV.NLM. The system administrator has to set up a user group named
GDT_OPERATOR. All users belonging to this group are given access (through GDTMON) to
the ICP Controller(s) in this specific fileserver (Access level 0). Now, the GDTMON program
can be loaded from one (or more) workstation(s):
GDTMON <ENTER>
By selecting the menu Select Controller of the GDTMON main menu, you can now choose ei-
ther a fileserver (equipped with a ICP Controller), or a ICP Controller in your workstation.
..//RRDDGGLLQQJJWWKKHH**''7700221133UURRJJUUDDPP88QQGGHHUU2266
The GDTMON program for OS/2 is part of the GDT OS/2 disk. To load the program under
OS/2, enter:
GDTMON32 <ENTER>
..//RRDDGGLLQQJJWWKKHH**''7700221133UURRJJUUDDPP88QQGGHHUU::LLQQGGRRZZVV1177
The GDTMON program for Windows NT is part of the GDT Windows NT disk. To load the pro-
gram under Windows NT, enter:
GDTMON <ENTER>
..//RRDDGGLLQQJJWWKKHH**''7700221133UURRJJUUDDPP88QQGGHHUU::LLQQGGRRZZVV
The GDTMON program for Windows 95 is part of the GDT Windows 95 disk. To load the pro-
gram under Windows 95, enter:

&KDSWHU.'LDJQRVLV3URJUDP*'7021
GDTMON <ENTER>
..//RRDDGGLLQQJJJJGGWWPPRRQQXXQQGGHHUU66&&228811,,;;
In order to be able to use the gdtmon program under SCO UNIX (2.x, 4.x and 5.x), it be-
comes necessary to substitute the standard terminal entry by a new one:
cd /usr/lib/terminfo <ENTER>
tic gdt386.src <ENTER>
Before each loading of gdtmon, this terminal has to be activated by:
TERM = gdt386 <ENTER>
export TERM <ENTER>
These two lines can also be inserted in the .profile file and will then be automatically proc-
essed during each login. The gdtmon program itself is copied during the SCO UNIX installa-
tion (chapter G of this User's Manual) into the /etc directory. gdtmon is loaded by entering:
gdtmon <ENTER>
.7KH*'70213URJUDP
As mentioned before, the GDTMON program appears identical for all operating systems, so
we can demonstrate the use and functioning of this program regardless of the operating
system used. In previous chapters we have already described the hierarchical structure of
the GDT firmware. We have defined 4 different levels of hierarchy: Level 1 where the physi-
cal SCSI drives named Physical Drives are found, level 2 containing the Logical Drives
(made up of one or several Physical Drives), level 3 where we have the Array Drives, and fi-
nally, level 4 where the Host Drives are. Only the latter ones are known to the operating sys-
tem. The drive of a given level of hierarchy is always set up by using the drives of the next
lower level as components. Accordingly, GDTMON has various menu options, each referring
to one level of hierarchy
+RVW'ULYHV Level 4
/RJLFDO'ULYHV Level 2
3K\VLFDO'ULYHV Level 1
Each menu option displays the performance of the drives belonging to the corresponding
level. (Note: The performance of Array Drives and Host Drives is identical). The performance
is measured in KB/s (kilobyte per second, transfer rate) and IO/s (I/Os per second, number
of simultaneously processed I/Os on the ICP Controller). The performance is displayed nu-
merically as well as graphically in the form of variable horizontal bars, with separate indica-
tions for each drive and its write and read accesses.
..66HHOOHHFFWW&&RRQQWWUURROOOOHHUU
This menu option yields a list of available ICP Controllers. By selecting a protocol, you have
either access to the ICP Controller(s) in your local computer (e.g., MS-DOS, Windows NT,
Windows 95 or OS/2 protocol), or to a ICP Controller in another computer (server or work-
station) in the network (NetWare NCPE or IBM NETBIOS protocol). All diagnosis and main-
tenance functions of GDTMON refer to the ICP Controller you have selected here (and the
SCSI devices connected with this controller).

&KDSWHU.*'78VHUV0DQXDO
(MS-DOS) in the Select Protocol menu indicates that the GDTMON program was loaded on
a MS-DOS computer. I.e.: If GDTMON had been loaded under Windows NT, we would see
there (Windows NT).

&KDSWHU.'LDJQRVLV3URJUDP*'7021
..++RRVVWW''UULLYYHHVV
This menu option leads to the list of available Host Drives (level 4). We would like to recall
that the operating system (e.g., NetWare) only recognizes these Host Drives and not their
possibly complex structures. This means that it is of no importance for the operating sys-
tem if a Host Drive consists of one single SCSI drive (of the type disk), or of 5 SCSI drives
configured to form a RAID 4 Array Drive. Apart from the performance, the name, type, state
and capacity (1024KB = 1MB) of a Host Drive is displayed. The figures shown at Total repre-
sent the overall performance of the Host Drives as a whole. With the mand okeys you
may change the scale of the graphical KB/s indication. With the nand pkeys you can scroll
the screen to see further Host Drives (if available).

&KDSWHU.*'78VHUV0DQXDO
(Note: All Host Drives on the screen shown above are idle.)
..//RRJJLLFFDDOO''UULLYYHHVV
This menu option yields a list of available Logical Drives (level 2). Logical Drives are the
components for Array Drives and Host Drives. In its most simple form, a Host Drive consists
of one Logical Drive which is made up of a single SCSI drive (type disk). In case of RAID Host

&KDSWHU.'LDJQRVLV3URJUDP*'7021
Drives, the performance of the Logical Drives forming a RAID Host Drive are shown in the
menu Logical Drives. The performance data displayed here gives immediate information on
the quality of a given Host Drive. When judging the indicated performance of Logical Drives
belonging to a RAID Host Drive, the following considerations should be taken into account:
(a) RAID 0, RAID 1, RAID 10 and RAID 5 Host Drives
If a certain Logical Drive shows poor performance for a longer period (when compared to
the other Logical Drives), this Logical Drive impairs the overall performance, making it the
bottle neck of the entire RAID Host Drive.
(b) RAID 4 Host Drives
In principle, the same as in (a) applies to RAID 4 Host Drives, with the exception made for
the parity Logical Drive. The poor performance can have various reasons: the SCSI drive
forming the Logical Drive
is too slow (different from the other SCSI drives with regard to type or manufacturer)
has wrong parameters (SCSI II, disk cache, tagged queues etc.)
has too many defects, causing the read/write actuator to have to move to alternate tracks
very often
When setting up RAID 4/5 Host Drives, please observe the notes on RAID 4/5 Host Drives
exposed in the chapter GDTSETUP in Detail.

&KDSWHU.*'78VHUV0DQXDO
The figures under Total represent the total performance of all Logical Drives. With the mand
okeys you may change the scale of the graphical KB/s indication. With the nand pkeys
you can scroll the screen to see more Logical Drives (if available).
..33KK\\VVLLFFDDOO''UULLYYHHVV
In addition to the performance report on the SCSI drives, you are given additional informa-
tion on each device: