# Chapter 9. LAN Test Case Details

The individual test cases in this chapter can be used when rerunning a single test manually. This may be necessary after a test failure has been corrected. These tests are run by typing the appropriate command from the command line.

Note: | Copies of the log files will be located in the \xxxlogs directory on each system that the individual tests were started on.

The following information is included, where appropriate, for each test:

- The name of the test, or part of the test

- A description of the test

- The steps to run the test

- The test results

- The test duration

## LAN Test Case Summary

The following table lists the test cases in the LAN testkit, where to get the details about each test case, and the approximate run time.

Table 3. Summary of LAN Tests

Test | Description | Approximate Run Time
ITLDUMP | OS/2 Dump Utility on page 71 | 15 Minutes
ITLLS56.CMD | LAN Server Exerciser for Domain on page 61 | 2 Hours
ITLLS57.CMD | LAN Server Exerciser for Server on page 61 | 2 Hours
ITLFTP01.CMD | FTP Server/Ping Exerciser of S01 on page 64 | 2 Hours
ITLFTP02.CMD | FTP Server/Ping Exerciser of D01 on page 64 | 2 Hours
ITLTCP01.CMD | TCP/IP Remote Execution on R01 on page 64 | 15 Minutes
ITLALERT.CMD | Alert Reporting on S01 on page 63 | 15 Minutes
ITLLD.CMD | LAN Distance Connection to S01 on page 63 | 2 Hours
ITLMSG.CMD | LAN Messaging on page 62 | 1 Hour
ITLPEER.CMD | PEER Services Exerciser on page 62 | 2 Hours
ITLPSF00 | Advanced Print Services on page 70 | 1 Hour
ITLPSNS00 | Backup/Restore on page 69 | 30 Minutes
ITLRAID | SystemView RAID Information on page 71 | 30 Minutes
ITLSV00 | Group Management on page 64 | 15 Minutes
ITLSV06 | Monitor Remote Workstation on page 65 | 30 Minutes
ITLSV07 | Hardware Inventory (Group) on page 66 | 15 Minutes
ITLSV08 | Software Inventory (Group) on page 67 | 15 Minutes
ITLSV11 | S01-System Information Tool on page 68 | 10 Minutes

## LAN Server Exerciser (ITLLS56, ITLLS57)

This test case will generate network traffic by creating a link between multiple requesters and a file server.

The itlls56.cmd test runs on S01, R01, and R02. The itlls57.cmd test runs on D01, R01, and R02.

### ITLLS56 and ITLLS57 Test Steps

1. Open an OS/2 window.

2. Type net name and press Enter to verify the system is logged on to the domain controller. If the system is not logged on, type the following:

3. logon IT01xxxU /d:IT01D01A /p:UPW01xxx /v:d

4. where xxx is the system name (D01, S01, R01, R02).

5. To test the domain controller, type itlls56.cmd on systems S01, R01, and R02. This test must be started on all three systems at the same time. Log files for itlls56 will be copied to the \d01logs directory on the domain controller.

To test the additional server, type itlls57.cmd on systems D01, R01, and R02. This test must be started on all three systems at the same time. Log files for itlls57 will be copied to the \s01logs directory on the additional server.

### Results of ITLLS56 and ITLLS57

This test is successful if all three of the requesters are able to connect to the domain controller or additional server and are able to run the tests for a minimum of two hours without a failure.

## Peer Services (ITLPEER)

This test case will exercise the OS/2 Peer function by sharing a local subdirectory with the network. The test case runs on the additional server (S01) and client 2 (R02).

### ITLPEER Test Steps

Start the test case from client 2 and the additional server by typing the command itlpeer.cmd.

Note: | If problems occur from the remote workstation while trying to access the shared resource, verify that the correct access is being granted for this resource. In order to run the test case, the resource needs to be given read/write access. To verify the access, double-click on the Sharing and Connecting icon. Clicking on this icon will open a notebook. Select the Access controls tab, the specific resource, and then click on the Set Access Permissions button.

This test will run for approximately two hours. The log file itlpeer.xxx will be copied to \r01logs on client 1.

### Results of ITLPEER

This test is successful if both the additional server (S01) and the client 2 (R02) systems are able to access the Peer workstation (client 1) and run ITLPEER a minimum of two hours without a failure.

## LAN Messaging (ITLMSG)

This test will generate light messaging traffic on the network. This test is run from the domain controller and client 1 systems.

### ITLMSG Test Steps

1. Enter the following command on the domain controller or client 1:

itlmsg

If the target workstation is busy, this test case might stop with a message indicating the workstation is busy or not responding. This is normal if the workstation getting the message is running multiple test cases.

Notes:

- This executable will send a message to the target systems once every 30 seconds. 120 messages will run for little more than a hour.

- NETPOPUP Service should be running on the domain controller and can be stopped by typing net stop netpopup. To restart, type net start netpopup.

2. To view the log on the target systems, open the IBM LAN Services folder and double-click on the Network Messaging icon.

### Results of ITLMSG

This test is successful if the test case runs to completion without a failure. This test should run for a minimum of one hour.

## LAN Alerts (ITLALERT)

The purpose of this test is to generate an FFST/2 alert on the additional server (S01). To generate this alert, available space on the c: drive is reduced to less than 15,000,000 bytes. Run this test on the additional server (S01).

### ITLALERT Test Steps

1. Make sure that the LAN Server was started as follows (this should be in the startup.cmd file):

2. net start server /e:1 /alerts:1 /alertn:IT01S01 /di:15000

3. net start alerter

4. net start genalert

5. On the additional server:

- Type itlalert at the c: drive. This command will build a temporary directory and fill it with test data files. When the available space is less than 15 MB, the program will sleep for two minutes before the test data files are erased and the \temp directory is removed. The amount of free disk space will dictate how long the executable will take.

Note: | A drive with 180 MB of free space will be filled up in approximately 10 minutes.

- You should receive a pop-up message when the alert is detected. You can check the message log to determine if the message was received. Open the IBM LAN Services folder on the Desktop, and then select Network Messaging. From here you can review all messages.

### Results of ITLALERT

This test is successful if the FFST alert is successfully posted in a pop-up window.

## LAN Distance Exerciser (ITLLD)

The LAN Distance tests are run on the LAN Distance Remote Requester (client 2). They include LAN exerciser, LAN messaging, FTP traffic, and LAN NetBIOS traffic.

### ITLLD Test Steps

The OS/2 LAN Distance Remote Requester is connected to the Connection Server (the additional server) using a modem, which should already be installed on both systems.

#### LAN Distance Connection Server

1. Press Ctrl+Esc to open the Window List and verify if LAN Distance has been started. If not, type ldstart at an OS/2 command prompt.

2. Wait until the LAN Distance window is displayed.

#### LAN Distance Remote Requester (Client 2)

1. Open an OS/2 window.

2. Type lanrboot.cmd and press Enter.

This command will back up startup.cmd and replace it with the startup.cmd for LAN Distance testing. It will also issue the ldshuttl remote command and reboot the system. On reboot, the itlld.cmd test case will be started automatically.

When itlld.cmd completes successfully, the original startup.cmd is restored, the command ldshuttl lan is issued and the system automatically reboots to resume regular LAN connection.

### Results of ITLLD

This test is successful if the tests complete the appropriate number of successful passes without a failure.

## TCP/IP FTP to Host and Ping (ITLFTP01, ITLFTP02)

This test case will ftp to a remote host and ping the host before sleeping. This test case is run on client 1 and client 2.

### ITLFTP01 and ITLFTP02 Test Steps

1. Open an OS/2 window.

2. To test the domain controller, type itlftp01.cmd on client 1.

To test the additional server, type itlftp02.cmd on client 2.

### Results of ITLFTP01 and ITLFTP02

This test is successful if the FTP test case is able to run on both requesters for a minimum of two hours without a failure.

## TCP/IP Remote Execution (ITLTCP01)

This test case will run commands on a remote host, sleep, and then continue looping. This test case is run on the domain controller.

### ITLTCP01 Test Steps

1. Open an OS/2 window.

2. Type itltcp01.

### Results of ITLTCP01

This test is successful if the REXEC test case is able to run for a minimum of two hours without a failure.

## Group Management (ITLSV00)

This test case verifies Netfinity functions in the creation of several groups of managed systems based on communication protocol, and operating system.

This test is run on the additional server.

- With OS/2 Warp Server for e-business and Convenience Package for OS/2 Warp Server for e-business, Netfinity is used.

1. Open the Netfinity, folder on the desktop.

2. Open the Netfinity Service Manager icon.

3. Open the Remote System Manager icon.

Note: | If a group ALL already exists, then continue with step 6 to add systems to the group.

1. From the Group pull down menu, select Add Group, and enter ALL for the group name. Then click on Add to close the window.

Note: | No keywords are used for this group.

1. Click on the ALL group once with the right mouse button and then select Discovery Filters. Highlight the TCP/IP and NETBIOS protocols, and click on Save.

2. In the System Group Management window, double-click on All to open the Group window.

3. From the Systems pull down menu, select Discover Systems.

Note: | This should fill the window with systems as they are being discovered. It should find two entries for systems D01, S01, and R02, and one entry for R01. When all systems are found, close the Group window.

1. Create two additional groups following step 4 above and name them NETBIOSWS and TCPIPWS.

Note: | No keywords are used for either group.

1. Click on each group once with the right mouse button and then select Discovery Filters. Select the appropriate protocol for each group and click on Save.

2. Then use steps 6 and 7 above to discover systems for each group.

### Results of ITLSV00

Demonstrate that the correct systems are discovered in each of the defined groups.

- In the All group, you should see two icons for D01, S01, and R02, and one icon for R01.

- In the NETBIOSWS group, you should see one icon for each of the systems.

- In the TCPIPWS group, you should see one icon for D01, S01, and R02, and no icon for R01.

## Monitor Remote System's Resources (ITLSV06)

This test case verifies Netfinity functions for remote monitoring of a managed system.

This test must run after ITLSV00 because it relies on having groups of systems already defined.

This test is run on the additional server.

- With OS/2 Warp Server for e-business and Convenience Package for OS/2 Warp Server for e-business, Netfinity is used.

### ITLSV06 Test Steps

1. Open the Netfinity, folder on the desktop.

2. Open the Netfinity Service Manager icon.

3. Open the Remote System Manager icon.

4. From the System Groups window, double-click on the ALL group to open it. Active workstations will have a green screen on their icon.

5. Double-click on one of the active systems to open the Remote Service window for that system.

6. Double-click on the System Monitor icon to bring up the window that shows CPU utilization.

7. From the System Monitor Service panel, use the Windows pull down menu and select Show Monitors.

8. CPU Utilization should already be highlighted, highlight one or two other resources to monitor from the list and click on Accept to begin monitoring the highlighted selections.

9. Let the monitor run for at least 30 minutes.

10. From the System Monitor Service panel, use the Windows pull down menu and select Export to database.

11. Click on OK to accept the defaults on the Database selection panel.

12. Click on OK to accept the defaults on the Export to File panel.

13. Click on OK on the Data Base Status pop-up panel.

14. Close the Monitor and all folders.

### Results of ITLSV06

This test is successful if the Netfinity Managing system can monitor the target system without errors. Monitoring should take place in 30 minute intervals.

For OS/2 Warp Server for e-business and Convenience Package for OS/2 Warp Server for e-business, the file IT01____.DBF, will be created in the \NETFIN directory on the OS/2 Boot Drive.

The appropriate file will be verified during results processing.

## Hardware Inventory (ITLSV07)

This test case verifies Netfinity functions to collect hardware information from all clients and store the information in files on the additional server.

This test must run after ITLSV00 because it relies on having groups of systems already defined.

This test is run on the additional server.

This test case is set up to run one time.

- With OS/2 Warp Server for e-business and Convenience Package for OS/2 Warp Server for e-business, Netfinity is used.

### ITLSV07 Test Steps

1. Open the SystemView / TME10 / Netfinity, folder on the desktop.

2. Open the SystemView / Netfinity Service Manager icon.

3. Open the Remote System Manager icon.

4. Open the Event Scheduler icon.

5. Click on New and enter the event name HW_INVENTORY.

6. Highlight System Information Tool and click on Groups. This will open the Schedule Groups or Systems window.

7. Highlight TCPIPWS from the Groups listbox, this will fill in the Systems listbox with a highlighted entry for three systems (R01 is not discovered under TCPIP).

8. Click on Schedule.

9. Create Print Output or History File should already be selected with the history file directory. Click on Save.

10. The Schedule Time and Date panel is displayed. Click on the one time radio button and choose a time of at least 10 minutes from the current time.

11. Click on Save.

From the Scheduler Service panel, The event HW_INVENTORY will show as scheduled.

Wait for the event time to pass, then click on View Log to verify that the events were executed and successful.

### Results of ITLSV07

This test is successful if at least three successful events were executed and the results are in the specified files.

For OS/2 Warp Server for e-business and Convenience Package for OS/2 Warp Server for e-business, the files IT01____.HST, will be created in the \NETFIN directory on the OS/2 Boot Drive.

The appropriate file will be verified during results processing.

## Software Inventory (ITLSV08)

This test case verifies Netfinity functions to collect software inventory from all clients and store the information in files on the additional server.

This test must run after ITLSV00 because it relies on having groups of systems already defined.

This test is run on the additional server.

This test case is set up to run one time.

- With OS/2 Warp Server for e-business and Convenience Package for OS/2 Warp Server for e-business, Netfinity is used.

### ITLSV08 Test Steps

1. Open the Netfinity, folder on the desktop.

2. Open the Netfinity Service Manager icon.

3. Open the Remote System Manager icon.

4. Open the Event Scheduler icon.

5. Click on New and enter the event name SW_INVENTORY.

6. Highlight Software Inventory and click on Groups. This will open the Schedule Groups or Systems window.

7. Highlight NETBIOSWS from the Groups listbox, this will fill in the Systems listbox with a highlighted entry for all four systems.

8. Click on Schedule.

9. Click on OK to accept the default to generate system reports.

10. The Schedule Time and Date panel is displayed. Click on the one time radio button and choose a time of at least 10 minutes from the current time.

11. Click on Save.

From the Scheduler Service panel, The event SW_INVENTORY will show as scheduled.

Wait for the event time to pass, then click on View Log to verify that the events were executed and successful.

### Results of ITLSV08

This test is successful if at least four successful events were executed and the results are in the specified files.

For OS/2 Warp Server for e-business and Convenience Package for OS/2 Warp Server for e-business, the files IT01____.INV, will be created in the \NETFIN directory on the OS/2 Boot Drive.

The appropriate file will be verified during results processing.

## System Information Tool (ITLSV11)

This test case verifies SystemView / TME10 / Netfinity functions of correctly identifing a systems hardware information.

This test must run after ITLSV00 because it relies on having groups of systems already defined.

This test is run on the additional server.

- With OS/2 Warp Server for e-business and Convenience Package for OS/2 Warp Server for e-business, Netfinity is used.

### ITLSV11 Test Steps

1. Open the Netfinity, folder on the desktop.

2. Open the Netfinity Service Manager icon.

3. Open the Remote System Manager icon.

4. Open the System Information icon. This will bring up information about the local machine.

5. Verify the memory, adapter card, and CPU information is correctly identified in that view.

6. From the File pull down menu, select Save to file or Print All System Data To File, depending on the OS/2 version being tested.

7. Accept the default file name and directory.

8. If a completion pop-up panel is displayed, click on OK to close.

9. Close all folders.

### Results of ITLSV11

This test is successful if the System Information tool correctly gathers hardware information for the target machine.

For OS/2 Warp Server for e-business and Convenience Package for OS/2 Warp Server for e-business, the file sysinfo.rpt, will be created in the \NETFIN directory on the OS/2 Boot Drive.

The appropriate file will be verified during results processing.

## Personal Safe and Sound (ITLPSNS)

This test case will exercise some of the basic functions provided with the Personal Safe and Sound backup and restore utility provided with OS/2 Warp Server. This test is run on the domain controller.

### ITLPSNS Test Steps

1. At an OS/2 command prompt, net use to the directory where the backup will be stored by typing the following:

2. net use x: s01util

3. Open the OS/2 Warp Server PSNS Backup/Restore folder and click on the Backup/Restore icon, and then click on the Move on button and the Done for now button.

4. From the Tools pull-down menu, select Storage Devices. This will list available devices that the backup can be created upon.

5. Click on the button in the upper-left corner of the screen and select New. Select Remote Disk.

6. On Storage Device Remote Disk select the remote drive and directory name, which should be psns5bkp, and click on OK. Then close the Storage Devices window.

7. From the Tools pull-down menu, select Backup Sets. Click on the button in the upper-left corner of the screen, select Available Sets, and click on New. For Name, type: Backup of ITLUTIL on S01. For Storage Device, select the drive letter (x:) you created using the net use command earlier. Click on OK.

8. You will be prompted to enter another description. Enter a description and then click on OK. Close the Backup Sets window.

9. From the Tools pull-down menu, select Backup Methods. This will list the defined (default) ways in which the backup can be run. Click on the button in the upper-left corner of the screen and select New. Enter the following information from the example provided:

Description: Backup of ITLUTIL directory on Additional Server

Source: Select "Only allow backup of files below"

Select the C drive and for directory, type: ITLUTIL

Compression: Select for no compression

Preview: By pass this section (click on red arrow)

Backup Set: Select the name "Backup of ITLUTIL on S01"

1. At this point, click on Save As at the bottom of the screen and type Backup of ITLUTIL on S01. Close the Backup Methods window.

2. Click on the clock icon on the PSNS screen.

3. From the schedule window, click on the button in the upper-left corner and select Active Events.

4. Click on New and then click on Daily Event. For Backup Method, select Backup of ITLUTIL on S01. For time, select a time of at least five minutes from the current time. When complete, click on OK.

5. When the backup has been accomplished, the restore functions must be exercised. From the PSNS screen, select Restore and then select Everything.

Note: | It is necessary to build a Restore method first by doing the following: Select RESTORE from the pull-down menu. Select EDIT A NEW METHOD from the selection presented. Provide a description (your choice) in the description field. Select the backup set name you used when defining the backup. Bypass the preview selection. Click on Save as and give it a name of your choice. This is the name you will select to initiate the restore. Click on OK. This will take you back to the original PSnS menu. Select RESTORE from the pull-down menu and click on the restore name you supplied to start the restore.

1. Update the file \ITLUTIL\ITLPSNS.TXT with results.

### Results of ITLPSNS

This test is successful if the backup/restore exercises have been run and files have been restored to the domain controller.

## Print Service Facilities (ITLPSF00)

This test case will exercise some of the basic functions provided with the Print Services Facility provided by OS/2 Warp Server to print a postscript file on a non-postscript printer. Use the following steps to configure PSF/2 to output to the printer that was setup and installed in the PCM Test environment.

### ITLPSF00 Test Steps

1. Open the PSF/2 icon on the desktop.

2. Open the PSF/2 Control Panel icon.

3. From the PROFILE pull down menu, select NEW.

4. For Device name, enter ENVPRT2. This name should be different than the name of the printer setup for the PCM Test environment.

5. Highlight PARALLEL attachment type and click on SETTINGS.

6. For Data Stream, select the data stream type supported as the default mode for the printer.

Note: | Check the documentation for your system to verify the default mode, and the modes that the printer can be set to. The data stream mode must be supported by your printer for this testcase to function properly.

1. Printer port should be LPT1. Accept the other defaults and click on OK.

2. Click on CREATE.

3. The next set of steps set up queue and transform options. This can be done from within the PSF/2 folder.

4. From the OPTIONS pull down menu, select SETUP QUEUES.

5. For Queue name, enter PSFQUE, and for Description, enter PSF PRINTER QUEUE, and click on SETUP.

6. From the PROFILE pull down menu, select Change, and then Select Transform Options.

7. On the Transform Options panel, double-click on POSTSCRIPTS 4019, 4029, and HP-LJ, this will add it to the Transform Sequence listbox.

8. Click on Change.

9. Close all the folders and reboot the system.

10. Use the aprint command to print an ASCII and PostScript file. The \itlutil\reados2.ps file is provided for PostScript print test. At an OS/2 command prompt, type aprint c:\itlutil\reados2.ps.

11. Update the file \ITLUTIL\ITLPSF00.TXT with results.

Alternatively, you can use the PSF/2 print submitter icon in the PSF/2 folder to be presented with a directory from which you can choose a file to print.

### Results of ITLPSF00

This test is successful if files print successfully.

## OS/2 Dump Test Case (ITLDUMP)

This test case will verify the ability of a hardware system to take a successful system dump. This test is run on the domain controller (d01).

### ITLDUMP Test Steps

1. Create a FAT partition that is at least 1 MB larger than the amount of system memory. Format the partition and call it SADUMP.

2. Edit config.sys by adding `TRAPDUMP=ON,x:` where x is the drive letter for the FAT partition that was just created.

3. Shut down and reboot the system.

4. Edit config.sys and remove the TRAPDUMP line.

5. Shut down the system a second time and when you see the Ctrl+Alt+Del window, press Ctl+Alt+NumLock+NumLock.

This will start a dump of memory to the FAT partition. When it is complete the system should reboot.

1. Update the file \ITLUTIL\ITLDUMP.TXT with results.

### Results of ITLDUMP

This test is successful if the system successfully reboots and the SADUMP partition is loaded with dump data.

## Netfinity Raid Information (ITLRAID)

This test case will verify the ability of Netfinity to recognize that a system under test has a RAID driver, and that an alert is generated when a device fails, is replaced and rebuilt.

Depending on the RAID adapter, it may be necessary to add the RAID Support/Configuration Utilities to the system under test.

Setup of RAID-1 or RAID-5 must have been completed before installation of OS/2 as defined "Setting Up the Domain Controller".

### ITLRAID Test Steps

1. With OS/2 Running, install the RAID Support/Configuration Utilities for the RAID adapter. Shutdown and reboot only if required by the RAID Support Utility installation.

2. Create a disk failure:

- If disks are Hot-Swappable:

- Remove 1 RAID drive while system is running.

- Wait for alert pop-up before continuing.

- If disks are NOT Hot-Swappable:

- Shutdown OS/2 - but do not reboot yet.

- Remove 1 RAID drive.

- Reboot OS/2

- Wait for alert pop-up before continuing.

1. Close the Alert pop-up by double clicking on the system icon in the left corner of the title bar.

2. Replace the failed drive:

- If disks are Hot-Swappable:

- Re-insert the RAID drive while the system is running.

- If disks are NOT Hot-Swappable:

- Shutdown OS/2 - but do not reboot yet.

- Re-insert the RAID drive.

- Reboot OS/2

1. Rebuild the RAID drive using the RAID Support Utilities for the Adapter. If the RAID adapter can only be re-built during with a standalone boot utility, shutdown OS/2 and rebuild the drive.

Note: | Alerts should be generated when the drive is removed and flagged as failing, when the drive has been placed in rebuild status (if rebuild support utility runs while OS/2 is booted), and when the drive is placed back online following successful rebuild.

To check the alerts generated, do the following:

1. Open the Netfinity folder on the desktop.

2. Open the Netfinity Service Manager.

3. Open the Alert Manager.

### Results of ITLRAID

This test is successful if the alerts are generated and the system continued to operate after a drive was removed, replaced, and rebuilt.

The alerts are written to \netfin\alerts.log and checked during results processing for alerts expected.