This file is a compilation of the few various KeyLabs text files found in the tarball. These are made as one text file for quick and easy online viewing. The text files which come with the testing programs themselves are in separate folders in the tarball. The various text files are separated with lines like: >>> BEGIN KVM WORKSHEET <<< >>> END KVM WORKSHEET <<< >>> BEGIN TTCP TEST TOOL TEXT FILE <<< >>> END TTCP TEST TOOL TEXT FILE <<< The text files included in this file are: kvm_cert.txt If you have questions you can direct them to linux@keylabs.com. >>> BEGIN KVM WORKSHEET TEXT <<< KVM Certification Worksheet KeyLabs KVM Certification Test, Revision 1.5 - JCW Tester Name: __________________________________________ Date: _______________ Section 1: Product Information Manufacturer: ________________________________________________________________ Product Name and Model Number: _______________________________________________ Product Description: _________________________________________________________ Overall Result: PASS FAIL Details: _____________________________________________________________________ Section 2: Setup Information Hardware Testing Tools Mouse: _______________________________________________________________________ Monitor: _____________________________________________________________________ Keyboard: ____________________________________________________________________ Computer Systems: CPU ____________ RAM ____________ HD Space ______________ OS _________________ CPU ____________ RAM ____________ HD Space ______________ OS _________________ CPU ____________ RAM ____________ HD Space ______________ OS _________________ CPU ____________ RAM ____________ HD Space ______________ OS _________________ Linux Distribution for this Test: [ ] Caldera [ ] Pacific High Tech [ ] S.u.S.E. [ ] Redhat Section 3: Tests Install Through: PASS FAIL Power Cycle: PASS FAIL Hotkey Switching: PASS FAIL N/A Auto Switching: PASS FAIL N/A Mouse Point/Click/Drag: PASS FAIL Keyboard Functions: PASS FAIL Display Resolution: PASS FAIL N/A Monitor On/Off: PASS FAIL Idle Time: PASS FAIL Multiple OS: PASS FAIL Multi Head: PASS FAIL N/A Sound Connect Tests: PASS FAIL N/A Section 4: Testing Procedures Install Through Test Procedure: Tester installs the Linux distribution on one or more CPUs while the CPUs are connected and controlled via the KVM. Determination: If the KVM allows continuous and invisible usage of the connected items (mouse, keyboard, monitor) throughout the install process the test is a pass. If at any time there is a loss of access or control of any of the KVM-connected items, the test is a fail. Power Cycle Test Procedure: Tester sets the KVM switch to CPU 2 and cycles the power on CPU 1. After CPU 1 has restarted, tester switches KVM back to CPU1 to verify the keyboard, mouse and monitor work with CPU 1. Determination: If CPU1 has full access to KVM-connected items after switching power off and then on, the test is a pass. If CPU 1 does not have access to any one or more of the KVM-connected items, the test is a fail. Hotkey Switching Test Procedure: With X running on one machine, a vc on running on another terminal and misc. other graphical/command line combinations on all other machines, tester cycles through the systems checking for interference with X commands when using the hotkey commands used by the KVM. Determination: If the machines being tested show no changes to the command line or to the graphical display when switching units via hotkeys, the test is a pass. If any machine shows conflict with hotkeys, such as menus appearing without the tester calling for them, unusual characters on the command line, etc., then the test is a fail. Auto Switching Test Procedure: If the KVM has this feature, the tester sets up and activates the auto-switching mechanism of the KVM and lets it run for a few minutes. Determination: If the KVM unit switches between machines without stopping or otherwise interfering with the processes active on the test machines, the test is a pass. If the test machines show any confusion, loss of KVM-connected items, lock-up or degradation of performance of KVM-connected items. Mouse Point/Click/Drag Test Procedure: Tester cycles through the connected CPUs testing the mouse for movement, clicking, highlighting and drag/drop performance. Determination: If the mouse performs as it would when connected directly to the CPUs when clicking, highlighting, dragging, dropping, then the test is a pass. If there is any loss of mouse functionality or any degradation of performance, the test is a fail. Keyboard Functions Test Procedure: Tester cycles through the connected CPUs testing the keyboard by typing into either an editor, post-it-notes program or a word processor. Determination: If the keyboard functions properly without loss of performance or performance degradation, the test is a pass. Any keyboard confusion, loss or degradation of performance is a fail. Display Resolution Test Procedure: Tester cycles to each Linux CPU and cycles through all available monitor resolutions using to verify the monitor changes resolutions. Determination: If the monitor changes resolutions as requested, the test is a pass. If the monitor fails to register the resolution request or otherwise acts confused, the test is a fail. [Note: Not all Linux distributions make this feature available. In this case, mark this test N/A.] Monitor On/Off Test Procedure: Tester makes CPU1 current on the KVM, turns off the monitor, and then cycles through the other connected CPUs back to CPU1, then turns on the monitor. Determination: If the monitor powers back up correctly and shows the desktop of CPU1, as it should be, the test is a pass. If the monitor does not shows the desktop correctly, the test is a fail. Idle Time Test Procedure: Tester leaves the KVM and connected CPUs idle for a period of at least one hour, then repeats the mouse and keyboard tests above. Determination: If the mouse and keyboard respond and perform as they would if connected directly to the CPUs, the test is a pass. Multiple OS Procedure: Tester ensures at least one of the machines hooked up to the KVM is running a Microsoft OS. Determination: If the various operating systems function with the KVM cycling from machine to machine without performance loss or degradation, the test is a pass. If there is any loss of performance of the KVM-connected items, the test is a fail. Multi Head Procedure: Tester first switches through the attached units alternating between heads. Tester then switches both heads to the same unit. Determination: Each unit switched to must be completely responsive via mouse and keyboard regardless of order of switching. When both heads are positioned on the same unit, as least on of the two heads must have complete control of the unit. If both these procedures work as stated then the test is a pass; otherwise, fail. Sound Connect Tests Procedure: Tester first connects and checks that sound is working on each individual unit attached to the KVM. Tester then has each attached system playing sound files/CDs while switching between units. >>> END KVM WORKSHEET TEXT <<<