If you experience difficulties with the Serial Port Test, do the following to determine if the serial port works. Your internal company engineers, who know the hardware, can provide the necessary information to configure the serial port.
Ensure that the serial port cable is connected between FS4 and SUT. SUT and FS4 Com port 1 must = 3f8 IRQ4..
(On FS4) Use Minicom Terminal Emulator to receive output.
At the shell prompt, type the following: minicom -s <Enter>.
Select
Ensure that the serial port setting is: /dev/ttyS0
HINT:Pressing Ctrl+AO displays the Minicom configuration screen.
NOTE:The speed of the com 1 port on FS4 and SUT must be the same.
(On SUT) Send output to FS4 via the serial port.
At the shell prompt, type echo -e “The serial port is working” > /dev/ttyS0<Enter>.
OR
At the shell prompt, type cat /etc/hosts > /dev/ttyS0<Enter>.
This outputs the contents of the file hosts to the serial port.
This information sent to the serial port on SUT should appear in the minicom screen on FS4. Minicom may display one character per line or display a complete sentence per line.
(On FS4) Exit minicom. In the minicom window, press , then select .
If the system has RAID and IDE/SCSI, test one of the RAID or Hard Disk Test items first and start the other one later. Do not place RAID and Hard Disk tests in the test queue together.
The test will not run when the local IP address is changed while TestConsole is running. Change the address back, or restart TestConsole
If, when reconfiguring the IP address of either of the two NICs, YaST consistently reboots after you click the Finish button at the Save Configuration Files window, the only way to edit the IP addresses of the NICs in the system is to edit the files that start with the following:
/etc/sysconfig/network/ifcfg-eth
There will be a file for each NIC which include the IP address and mask of the NIC.
To enable IP forwarding when YaST2 does not allow you to save the configuration:
Edit the contents of the following file to be “1” instead of “0”:
/proc/sys/net/ipv4/ip_forward
This will enable IP forwarding value will reset to the original value when the system reboots.
To make the configuration persistent, edit the /etc/sysconf file with the line that has “IP_FORWARD” to read IP_FORWARD=’yes’
If the steps above don’t work, try the following.
At a terminal, type ls /srv/ftp/ and verify the following files are listed: 300kb.md5sum, 300kb, 400mb, 400mb.md5sum
If you are having trouble with the Router Test, try the following troubleshooting tips.
From TestConsole, try pinging SUT card 1. If that is successful, try pinging SUT card 2. If that is successful, try pinging FS4. If that is successful, the routing is set up correctly.
If it doesn't work, type route at a shell prompt on TestConsole. The default gateway IP address for the SUT card on the TestConsole segment should be listed. If it is not listed, type route add default gw <IP address of the SUT TC segment> and press <Enter>. Type route again at the shell prompt to verify the new default gateway has been added. Pinging each card in SUT and FS4 should now work. IF the FS4 server does not ping, the default route gateway in FS4 may need to be set up as well.
When reconfiguring the IP address of either of the two NICs, YaST consistently reboots after you click the Finish button at the “Save Configuration Files” window.
The only way to edit the IP addresses of the NICs in the system is to edit the files that start with the following:
/etc/sysconfig/network/ifcfg-eth
There will be a file for each NIC. The relevant contents of the file are the IP address and mask of the NIC.
To enable IP forwarding when YaST2 does not allow you to save the configuration:
Edit the contents of the following file to be “1” instead of “0”:
/proc/sys/net/ipv4/ip_forward
This will enable IP forwarding for the current session, but will reset to the original value when the system reboots.
To make the configuration persistent, edit the /etc/sysconf file. Look for the line that has “IP_FORWARD” and make it read:
IP_FORWARD=’yes’
If you cannot mount or write to the SUT from TestConsole, perform the following steps:
On the SUT
Ensure the /etc/exports file has a line exactly as follows:
/ *(rw,no_root_squash)
If the file doesn’t have this line, run configure_sut again.
Type /etc/init.d/nfsserver stop<Enter> to stop the nfs server.
Type /etc/init.d/nfsserver start<Enter> to restart the nfs server with the new setting.
On TestConsole
Type mkdir -p /mnt/ <SUT IP Address> <Enter>.
Type mount -t nfs <SUT IP Address>:/ /mnt/<SUT IP Address>/<Enter>.
Copy a file or make a directory in /mnt/sut to verify that you can access and write to the SUT from TestConsole.
If the Router Test’s test result reverts back to “untested” within a few seconds after starting the test, you probably have not started tclink on TestConsole. The Router Test is the only test that requires tclink to be running on TestConsole.
Open a shell on TestConsole and type tclink<Enter>.
Double-click the router test.
The Testing Status should remain in the “testing” state for two hours. You may check for disk activity on the SUT and FS4.
If experiencing a message with from the TestConsole, go to the /var/opt/novell/NovellTestKits/ftpload directory.
NOTE:File names specified are case sensitive (ROUTER and router are different).
If you see a file like ROUTER_ftpload-{todaysdate}.{currenttime}.logerr, cat this file out (i.e., cat ROUTER_ftpload-{todaysdate}.{currenttime}.logerr) and check for the following message:
SUT mount point "/mnt/<SUT IP ADDRESS>" not found or invalid. -- storing logs locally
.
If you do NOT see this message, then the NFS mount to the SUT is okay, and the test is fine. If you DO see this message, then the router logs need to be copied back to the SUT, once the router test has run to completion.
Once the router test has finished, do the following:
From the TestConsole, go to the /var/opt/novell/NovellTestKits/ftpload directory.
If the directory does not exist on Testconsole, then the mountpoint worked. Please look on SUT for /var/opt/novell/NovellTestKits/ftpload.
Look for the most recent router log files (i.e., router_ftpload-{currentdate}.{currenttime}.log*) and issue the following:
scp router_ftpload-{currentdate}.{currenttime}.log* <SUT IP ADDRESS>:/var/opt/novell/NovellTestKits/ftpload
If you are asked to authenticate to the host answer . and then give the proper root password for the SUT.
NOTE:This must be done BEFORE running "Get Test Logs (run after tests)” is done.
If the NIC or Router test fails, it could be because old test kit was not uninstalled completely on the TC and FS4 machines.
Remove old files on TestConsole:
Open a terminal on TestConsole.
Type rm -rf /srv/ftp/*<Enter>.
Type run configure_tc<Enter>.
Remove old files on FS4.
Open a terminal on FS4.
Type rm -rf /srv/ftp/*<Enter>.
Type run configure_tc<Enter>.
If you accidentally reboot SUT before removing the USB hard drive partitions, follow the steps below to remove the USB Hard drives from the SLES configuration and recover.
The /etc/fstab file can be edited after a reboot with the USB drives attached.
Log in as root.
Open a terminal and type vi /etc/fstab<Enter>.
Place the cursor on the line with the USB entries (i.e., /media/tc/usb1 or /media/tc/usb2) and press D two times in a row.
Unplug the USB hard drives from the system (if you have not already done so).
Reboot the system.
The USB hard drives will not be configured with the system.