toasters

toasters@lists.teaparty.net

2 participants
13529 discussions

RE: Access the filer via passwordless ssh
by Potakamuri, Sreenivasa 09 Dec '02

09 Dec '02

This feature is not possible with ONTAP 6.3. But, this will be available in the future release. Thanks, Sreenivasa Potakamuri Network Appliance. -----Original Message----- From: Leslie Wang To: toasters(a)mathworks.com Sent: 12/8/02 3:49 AM Subject: Access the filer via passwordless ssh Does anyone know if his is possible with ONTAP 6.3?

1 0

RE: Accessing Filer from DOS
by Hall, Tom 08 Dec '02

08 Dec '02

I ran into a similar issue with a network boot disk that Norton Ghost made. I solved the problem by using Bart's network boot disk to connect to our filer. They seem to keep up with new dos drivers/utils for tcp/ip, ms network client, and nic drivers. You can download the disk from http://students.lco-college.edu/bootcd/network_boot_disk.htm <http://students.lco-college.edu/bootcd/network_boot_disk.htm> -----Original Message----- From: steven boyer [mailto:sboyer1@tampabay.rr.com] Sent: Wednesday, December 04, 2002 12:11 PM To: toasters(a)mathworks.com Subject: Accessing Filer from DOS If a NT server goes down, we want to be able to re-image the windows server from the filer. We must do this from a DOS prompt. So the question is how do I access the filer using DOS. The following is the information from our NT Admin: I am trying to connect to the filer at \\crsqfiler\image to create and store images of our WIN2K servers. I used Powerquest to create the boot disks (Powerquest Boot Disk Builder Version 5.01 Build Bdb501.012). I receive the following error when attempting to connect to the filer from DOS - Error 58 The network has responded incorrectly. Attempts to connect to other sharepoints on the filer are also unsuccessful. I can connect to any WIN2K Share with no problem. I have reviewed the issues in the NETAPP Knowledge base, as well as, Powerquest's knowledge base and can find no remedy Has anyone been able to get this to work? Steven

2 1

Placing Oracle onto a cluster
by George Kahler 07 Dec '02

07 Dec '02

I would appreciate if someone could share how they break the various Oracle parts (pls excuse, I'm not a DBA), ie. data, logs, archives, & etc. amongst the various volumes in a NetApp cluster. I have an Oracle instance running on a singe F840 that very shortly is going to be clustered. The Oracle binaries are in a separate qtree and the rest the DBAs put in another qtree that I created for them. The qtrees and mount are by the SID. (HR) On the toaster /vol/db/<sid>/archs archive logs /ctl control files /data dbf files /rbs dbs files /redo redo logs /system /temp this gets mounted on a Sun DB server as filer:/vol/db/HR /rmounts/HR /oradata/HR --> /rmounts/DB/HR The DBAs refer to the database by a slink /oradata/HR in this case. A new mandate is to utilize the clustered F840s and to separate the database (.dbf), the redo and archive logs. In the cluster env there are now 4 volumes, 2 on each head. One for database, the other for logs (one has snapshots the other does not). Production DB is on one head, QA on the other. filer: A filer: B ------------------------ vol DB vol DB vol log vol log Do you folks that spread your logs end up with multiple nfs mounts per database? Do I suggest to my DBAs that I will have something like: A:/vol/db/HR/u01/data /rmounts/HR/u01 /rbs /system /temp A:/vol/log/HR/u02/redo1 /rmounts/HR/u02 /arch1 /ctl1 B:/vol/log/HR/u03/redo2 /rmounts/HR/u03 /arch2 /ctl2 /oradata/HR --> /rmounts/HR So I end up with 3 nfs mounts for each instance of the database? How do you people do this? There are about 10 other DBs waiting. What about a DSS; a reporting database? At the present time with all of the DB components on one volume all the DBAs have to snap the one volume and they can start up a DSS instance. In this new scenario, I guess they will still have to snap the DB volume and also snap one of the LOG volumes. What do you do? Sorry for being so winded but I was looking for specifics, unfortunately I couldn't find anything on either the NOW site or the archive list. Just the White Papers that describe the concept. Thanks, George ------------------------------------------------------------------------------- George Kahler e-mail: george(a)yorku.ca Sr. Systems Administrator humans: (416) 736-2100 x.22699 Computing and Network Services machines: (416) 736-5830 Ontario, Canada, M3J-1P3

2 2

new gigabit card
by Piotr KUCHARSKI 06 Dec '02

06 Dec '02

Are there more than one model of gigabit card for filer 740? Which is the best, then? p. -- Beware of he who would deny you access to information, for in his heart he dreams himself your master. -- Commissioner Pravin Lal http://nerdquiz.sgh.waw.pl/ -- polska wersja quizu dla nerdów ;)

2 1

AW: Accessing Filer from DOS
by Friedrich, Bernhard 06 Dec '02

06 Dec '02

There's yet another entry you may need to set: preferredredir=full This needs to be set in system.ini, typically in the directory where you keep the "net" command on your bootdisk. That way, you won't have to issue "net start /full" but a "net start" will suffice. If that still doesn't help, also set autostart=full in system.ini - this has always worked for us. See http://now.netapp.com/Knowledgebase/solutionarea.asp?id=ntapcs3583 for details and also see http://now.netapp.com/Knowledgebase/solutionarea.asp?id=ntapcs2762 - there's a typo in that article, though - it needs to be preferredredir instead of prefrredredir. Greetings, Bernhard Friedrich Uniklinikum Heidelberg ZIM - Server und Basissysteme -----Ursprüngliche Nachricht----- Von: Steven Boyer GD-Mail [mailto:steven.boyer@gd-centcom.com] Gesendet: Donnerstag, 5. Dezember 2002 17:40 An: Kumar, Rahul; Hall, Tom; toasters(a)mathworks.com Betreff: Re: Accessing Filer from DOS We made all those changes and still no glory ----- Original Message ----- From: Kumar, Rahul To: Hall, Tom ; steven boyer ; toasters(a)mathworks.com Sent: Wednesday, December 04, 2002 10:52 PM Subject: RE: Accessing Filer from DOS Hi, You just need to modify the following line in the floppy to gain access to filers from DOS prompt. By default, the boot disk builder uses basic redirection. The Filers require Full redirection to make connections. Edit the A:\autoexec.bat on the floppy you just created and look for the line net start basic Change this line to read net start full That will take care of the problem. Rahul Kumar, Tele: + 91 20 2930812 (D), Cell: + 91 982230 9177. EDS PLM Solutions, Pune, India. -----Original Message----- From: Hall, Tom [mailto:Tom.Hall@exchange.webmd.net] Sent: Thursday, December 05, 2002 2:46 AM To: 'steven boyer'; toasters(a)mathworks.com Subject: RE: Accessing Filer from DOS I ran into a similar issue with a network boot disk that Norton Ghost made. I solved the problem by using Bart's network boot disk to connect to our filer. They seem to keep up with new dos drivers/utils for tcp/ip, ms network client, and nic drivers. You can download the disk from http://students.lco-college.edu/bootcd/network_boot_disk.htm -----Original Message----- From: steven boyer [mailto:sboyer1@tampabay.rr.com] Sent: Wednesday, December 04, 2002 12:11 PM To: toasters(a)mathworks.com Subject: Accessing Filer from DOS If a NT server goes down, we want to be able to re-image the windows server from the filer. We must do this from a DOS prompt. So the question is how do I access the filer using DOS. The following is the information from our NT Admin: I am trying to connect to the filer at \\crsqfiler\image to create and store images of our WIN2K servers. I used Powerquest to create the boot disks (Powerquest Boot Disk Builder Version 5.01 Build Bdb501.012). I receive the following error when attempting to connect to the filer from DOS - Error 58 The network has responded incorrectly. Attempts to connect to other sharepoints on the filer are also unsuccessful. I can connect to any WIN2K Share with no problem. I have reviewed the issues in the NETAPP Knowledge base, as well as, Powerquest's knowledge base and can find no remedy Has anyone been able to get this to work? Steven

1 0

RE: Accessing Filer from DOS
by Kumar, Rahul 05 Dec '02

05 Dec '02

Hi, You just need to modify the following line in the floppy to gain access to filers from DOS prompt. By default, the boot disk builder uses basic redirection. The Filers require Full redirection to make connections. Edit the A:\autoexec.bat on the floppy you just created and look for the line net start basic Change this line to read net start full That will take care of the problem. Rahul Kumar, Tele: + 91 20 2930812 (D), Cell: + 91 982230 9177. EDS PLM Solutions, Pune, India. -----Original Message----- From: Hall, Tom [mailto:Tom.Hall@exchange.webmd.net] Sent: Thursday, December 05, 2002 2:46 AM To: 'steven boyer'; toasters(a)mathworks.com Subject: RE: Accessing Filer from DOS I ran into a similar issue with a network boot disk that Norton Ghost made. I solved the problem by using Bart's network boot disk to connect to our filer. They seem to keep up with new dos drivers/utils for tcp/ip, ms network client, and nic drivers. You can download the disk from http://students.lco-college.edu/bootcd/network_boot_disk.htm -----Original Message----- From: steven boyer [mailto:sboyer1@tampabay.rr.com] Sent: Wednesday, December 04, 2002 12:11 PM To: toasters(a)mathworks.com Subject: Accessing Filer from DOS If a NT server goes down, we want to be able to re-image the windows server from the filer. We must do this from a DOS prompt. So the question is how do I access the filer using DOS. The following is the information from our NT Admin: I am trying to connect to the filer at \\crsqfiler\image to create and store images of our WIN2K servers. I used Powerquest to create the boot disks (Powerquest Boot Disk Builder Version 5.01 Build Bdb501.012). I receive the following error when attempting to connect to the filer from DOS - Error 58 The network has responded incorrectly. Attempts to connect to other sharepoints on the filer are also unsuccessful. I can connect to any WIN2K Share with no problem. I have reviewed the issues in the NETAPP Knowledge base, as well as, Powerquest's knowledge base and can find no remedy Has anyone been able to get this to work? Steven

2 1

Netware file security migration to CIFS NetApp filer
by Hight, Steve - Perot 05 Dec '02

05 Dec '02

Has anyone used the Migration Tool for Netware that came with NT 4.0 to migrate from Netware 4.x to a CIFS filer? There is already a NT domain setup, all clients are authenticating to both NDS and a NT4 domain. The problem is that it looks like there is not a way to use the Migration Tool for Netware that came with NT 4.0 to migrate straight to the filer. The tool wants to copy from a Netware volume to local disk on the NT domain controller that you have the tools and gateway service on. Anyone know of a workaround to copy from Netware to the filer? I realize that if I did not need to migrate security my options would be much greater (NFS, FTP, etc), but migrating security is a must. Thanks for your help. Steve Hight Perot Systems

1 0

RE: Accessing Filer from DOS
by Hill, Aaron 04 Dec '02

04 Dec '02

One word; SAMBA If you are running unix/linux servers in the same environment, run samba on one of them and modify your share connection on the Norton bootdisk or whatever you are using. Eg net use z \\ <file:///\\%3cunix_servername%3e\%3csamba_share_to_image_dir> <unix_servername>\<samba_share_to_image_dir>. SAMBA will take care of all the authentication with your DC with your existing ghost userid. We use it for our pc/laptop images. SAMBA and unix/linux. Never leave home without them! Aaron www.navitaire.com -----Original Message----- From: Hall, Tom [mailto:Tom.Hall@exchange.webmd.net] Sent: Thursday, December 05, 2002 8:16 AM To: 'steven boyer'; toasters(a)mathworks.com Subject: RE: Accessing Filer from DOS I ran into a similar issue with a network boot disk that Norton Ghost made. I solved the problem by using Bart's network boot disk to connect to our filer. They seem to keep up with new dos drivers/utils for tcp/ip, ms network client, and nic drivers. You can download the disk from http://students.lco-college.edu/bootcd/network_boot_disk.htm <http://students.lco-college.edu/bootcd/network_boot_disk.htm> -----Original Message----- From: steven boyer [mailto:sboyer1@tampabay.rr.com] Sent: Wednesday, December 04, 2002 12:11 PM To: toasters(a)mathworks.com Subject: Accessing Filer from DOS If a NT server goes down, we want to be able to re-image the windows server from the filer. We must do this from a DOS prompt. So the question is how do I access the filer using DOS. The following is the information from our NT Admin: I am trying to connect to the filer at \\crsqfiler\image to create and store images of our WIN2K servers. I used Powerquest to create the boot disks (Powerquest Boot Disk Builder Version 5.01 Build Bdb501.012). I receive the following error when attempting to connect to the filer from DOS - Error 58 The network has responded incorrectly. Attempts to connect to other sharepoints on the filer are also unsuccessful. I can connect to any WIN2K Share with no problem. I have reviewed the issues in the NETAPP Knowledge base, as well as, Powerquest's knowledge base and can find no remedy Has anyone been able to get this to work? Steven

1 0

Accessing Filer from DOS
by steven boyer 04 Dec '02

04 Dec '02

If a NT server goes down, we want to be able to re-image the windows server from the filer. We must do this from a DOS prompt. So the question is how do I access the filer using DOS. The following is the information from our NT Admin: I am trying to connect to the filer at \\crsqfiler\image to create and store images of our WIN2K servers. I used Powerquest to create the boot disks (Powerquest Boot Disk Builder Version 5.01 Build Bdb501.012). I receive the following error when attempting to connect to the filer from DOS - Error 58 The network has responded incorrectly. Attempts to connect to other sharepoints on the filer are also unsuccessful. I can connect to any WIN2K Share with no problem. I have reviewed the issues in the NETAPP Knowledge base, as well as, Powerquest's knowledge base and can find no remedy Has anyone been able to get this to work? Steven

1 0

Tape Jukebox and scsi errors (Overland LXS mini library express)
by Darragh, Stephen J 04 Dec '02

04 Dec '02

Hello, We have a F820 with a lvd scsi card and a Overland Data LXS mini library express (1 dlt7000 and 15 slots) This is directly attached and controlled via ndmp and Veritas NetBackup 3.4.1 We are getting the following errors: Sun Dec 1 12:30:18 EST [isp_timeout:warning]: 1.4(0x015e8ca4, 0x00): command timeout, quiescing bus to allow outstanding I/O to complete. Sun Dec 1 12:30:24 EST [isp_timeout:warning]: Resetting SCSI adapter 1 (ha #0) Sun Dec 1 12:30:25 EST [isp_timeout:warning]: Resetting SCSI bus 1 (ha #0) to clear outstanding I/O. Sun Dec 1 12:30:39 EST [isp_timeout:warning]: 1.4(0x015e8ca4, 0x00): command timeout, quiescing bus to allow outstanding I/O to complete. Sun Dec 1 12:30:45 EST [isp_timeout:warning]: Resetting SCSI adapter 1 (ha #0) Sun Dec 1 12:30:45 EST [isp_timeout:warning]: Resetting SCSI bus 1 (ha #0) to clear outstanding I/O. Sun Dec 1 12:31:31 EST [isp_timeout:warning]: 1.4(0x015ea0a4, 0x00): command timeout, quiescing bus to allow outstanding I/O to complete. When we reboot we can use the jukebox, we can use this and it will run fine till we power cycle the jukebox and then we have to bounce the filer. And we can't figure out why we are getting these errors. I have tried swapping cables, terminator, scsi cards, and the jukebox itself. The jukebox is a SE device that is attached to the lvd scsi controller on the filer which should be supported. In fact, if I try to add a 2nd jukebox, the errors are so bad that I can't see either one. I have set the indentification to be DEC TL800, since the filer did not recognize this as a Overland LXS. Does anyone have one of these jukebox's and what Vendor ID and Prodcut ID are you using??? Thanks Stephen Darragh

1 0

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

2000

1999

1998

1997

toasters