Date: Tue, 15 May 2007 11:56:12 +0530 From: Channa <channa.kad@gmail.com> Subject: [users:00332] Re: Help on remote files To: users@tahi.org Message-Id: <515c64960705142326h4debf4a5o2a4d3f967d35e3f1@mail.gmail.com> In-Reply-To: <607194575BD8CE46BCC8D747996FA7F9034C83A2@SI-RD10-MS01.LGE.NET> References: <515c64960705140710t150051e5o43a63e64604f989f@mail.gmail.com> <OF59155FBF.7E07FCC8-ON862572DB.004FE8CB-862572DB.005113B2@us.ibm.com> <515c64960705142105t286e44cbx2b0f301dbdea4212@mail.gmail.com> <607194575BD8CE46BCC8D747996FA7F9034C83A2@SI-RD10-MS01.LGE.NET> X-Mail-Count: 00332Ok thanks for the infromation. How will i come to know what all commands have to be done manually? Since when i run certain test cases for ipv6 specification the test cases are getting passed.And for ipv6 tunneling the test cases are getting failed. Can you just gimme an example wherein i have to run the commands manually except reboot:) Thank in Advance, Channa On 15/05/07, Ravi Prasad <ravi.prasad@lgsoftindia.com> wrote: > > Hi, > > First I am not sure whether Tahi works on Fedora or not. > > Generally FreeBSD is used as the TN. > > The NUT can be any OS that u want to test. > > > > The Tahi test script works in 2 modes. Manual and Automatic. > > The Actual mode is set in the nut.def file. > > Mode Manual > > No requirements for remote files > > No requirement for serial cable. > > NUT can be any Operating system. > > Certain commands like Reboot, Setting of Address etc have to > be done manually. > > You have to sit in front of the system and carry out testing. > > The Phase 2 test cases of ND have lots of manual intervention > requirement. > > > > Mode Automatic (serial in nut.def) > > In this case you have to specify the target name, for e.g. > FreeBSD5.4, Linux, Windows etc > > Serial cable is required > > Tahi scripts have a directory containing the commands (remote > files) for each of the supported OS. > > When the TN has to start the testing it logs in to the system > and then executes the command. > > You have to provide the login name and password. > > For e.g. In FreeBSD using the .rmt files first TN > gets a remote terminal in NUT and then executes the reboot command. > > The commands to be executed in the NUT go through the Serial > cable. > > This is usefull if your target (NUT) is one of the standard OS > supported by Tahi. Otherwise you have to write your own .rmt files. > > This automates the testing. > > > > Thanks and Regards > > Ravi Prasad > > > > > > > > > > > ------------------------------ > > *From:* Channa [mailto:channa.kad@gmail.com] > *Sent:* Tuesday, May 15, 2007 9:35 AM > *To:* users@tahi.org > *Subject:* [users:00330] Re: Help on remote files > > > > Hi, > > Thanks for the information. You mean to say .rmt fiels are not required > when i specify the system as manual?? and i have to do things which scripts > do manually?? > > And also since i am using Fedora Core linux what should i specify in the > system column of nut.def file?? > > Can you just tell me how do i write the remote files? > > > > On 14/05/07, *Christy L Norman* <cnorman@us.ibm.com> wrote: > > > If you want the TN to configure the NUT for you, don't specify 'manual' in > the nut.def file. If you do this, you'll have to do what the script would > do, then hit Enter every time - and in the case of 'manual' you don't need > .rmt files at all. > > Instead, if you want to use the .rmt files, change the 'system' value in > the nut.def file to your NUT. Then create a folder with that system name > in /usr/local/v6eval/bin/ called whatever you put as 'system' and copy all > the .rmt files in the '/bin/manual' folder into it. Then, when you run the > tests, you'll see "not yet supported" in the log (html) file where scripts > should be implemented. Try putting something of your own into the .rmt file > it's calling then when the scripts are run you'll see them show up in the > log file like this: > vRemote(reboot_async.rmt) > ``/usr/local/v6eval//bin/mySystem//reboot_async.rmt -t mySystem-u userName-p > password-d fxp1 -l 1 timeout=120'' > Use that information to figure out which parameters are being passed and > depending on which type of system you're using, you can figure how to write > the script. For rebooting linux, for example, you would probably just edit > the rebootasync.rmt file to have "reboot" in it. I'm not sure on all the > Linux commands since I've never run these tests against a Linux kernel. I > could be wrong, but I don't think there are any pre-written Linux .rmt files > out there. > > Hopefully that helps... > > - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - > - - - > Christy L Norman/Rochester/IBM <cnorman@us.ibm.com> > Software Engineer, i5/OS TCP/IP Development > - > 3605 HWY 52 N > Dept GY4A 015-2/D112 > Rochester, MN 55901 > 507.253.6125 > - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - > - - - > > > *Channa <channa.kad@gmail.com>* > > 05/14/2007 09:10 AM > > Please respond to > users@tahi.org > > To > > users@tahi.org > > cc > > > > Subject > > [users:00328] Re: Help on remote files > > > > > > > > > > > > > Hi, > Thanks for the information. > I have installed TAHI on Fedora core linux after doing some pacthing. > Its installed fine. If i am not wrong i need to modify the remote files > for it rite? > And in NUT.def file i have specified the system as manual. > > Can you tell me how to proceed with writing these rmt files? > Or these are available for Redhat Linux?? > Can you please help me in this? > > Thanks in advance, > Channa > > On 14/05/07, *Christy L Norman* < cnorman@us.ibm.com> wrote: > > Some of the tests need for something on your NUT to change. Look at their > names: clearmtu, ikeStart, ikeSetSA. They give you a good idea of what the > script will need to do. Depending on which tests you're running, you'll need > to create scripts inside those .rmt files to do what they should. If a > script that your test needs hasn't been filled in yet you'll see, "Not yet > supported" in the test output. So if you're not seeing that you don't need > to worry about the remote files yet. > > > - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - > - - - > Christy L Norman/Rochester/IBM < cnorman@us.ibm.com> > Software Engineer, i5/OS TCP/IP Development > - > 3605 HWY 52 N > Dept GY4A 015-2/D112 > Rochester, MN 55901 > 507.253.6125 > - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - > - - - > > *Channa <* *channa.kad@gmail.com* <channa.kad@gmail.com>*>* > > 05/14/2007 07:53 AM > > Please respond to* > *users@tahi.org > > > > To > > users@tahi.org > > cc > > > > Subject > > [users:00325] Re: Help on remote files > > > > > > > > > > > > > > > Can you tell me why these remote files are needed?? > > > > On 14/05/07, *Channa* < channa.kad@gmail.com> wrote: > Ok got it thanks. > > > On 14/05/07, *Santosh Bhavsar* < santoshb@sarksoft.com > wrote: > > 1. TAHI is for Free BSD you should have free BSD on your machine then it > work as per my knowledge. > on linux it will not work. > 2. About that message you have to reboot it manually . > > > > ----- Original Message ----- * > From:* Channa <channa.kad@gmail.com> * > To:* users@tahi.org * > Sent:* Monday, May 14, 2007 5:21 PM * > Subject:* [users:00319] Help on remote files > > > Hi, > I have installed TAHI on Fedora core linux . > When i run the test cases can any one tell me how the remote commands are > executed. > Because when i run the test cases i get the messages like > > ========== TEST 1 ========== > ./BEGIN.seq -pkt /dev/null -log 1.html -ti "Initialization" > Target: Reboot > > reboot> > reboot> Reboot NUT. > reboot> * Wait until NUT boot up completely. > reboot> Ex.) Wait until catch up login prompt. > reboot> > reboot> Press Enter key for continue. > > reboot> > > Wait 10 second > OK > > But the TARGET is not getting rebooted. > > Can anyone throw some idea on this... > > > > Thanks in advance, > > Channa > > > > > > ######################################### THIS EMAIL MESSAGE IS FOR THE > SOLE USE OF THE INTENDED RECIPIENT(S) AND MAY CONTAIN CONFIDENTIAL AND > PRIVILEGED INFORMATION. ANY UNAUTHORIZED REVIEW, USE, DISCLOSURE OR > DISTRIBUTION IS PROHIBITED.BEFORE OPENING ANY ATTACHMENTS PLEASE CHECK FOR > VIRUSES AND DEFECTS.IF YOU ARE NOT THE INTENDED RECIPIENT, PLEASE NOTIFY > US IMMEDIATELY BY REPLY E-MAIL AND DELETE THE ORIGINAL MESSAGE. > ######################################### >332_2.html (attatchment)(tag is disabled)