toasters September 1999

toasters@lists.teaparty.net

81 participants
95 discussions

RE: DLT problems on F740s
by Benn, Paul 01 Sep '99

01 Sep '99

It's been my experience that "differential" SCSI drives as well as terminators are clearly marked as being such. Best Regards, Paul -----Original Message----- This sounds remarkably similar to the symptoms I saw when I accidentally plugged a single-ended (i.e, non-differential) DLT4000 into our F740. I removed the drive after I noticed it was hanging at a similar point to where yours was, and all was well. I've since had a wide differential DLT7000 on the F740 working without any problems. As to how to test the tape drives; no idea. `Check with your vendor'?

1 0

RE: DLT problems on F740s
by Benn, Paul 01 Sep '99

01 Sep '99

Hello Dave, Is it possible that a single ended SCSI drive and terminator were plugged into the differential SCSI port? Regards, Paul Network Appliance -----Original Message----- From: Dave Atkin [mailto:dla1@york.ac.uk] Sent: Wednesday, September 01, 1999 1:02 AM To: toasters(a)mathworks.com Subject: DLT problems on F740s On startup the 740 hangs for a long time just after the memory test and the "Complete" message. We've tried each drive on two 740s and they both act the same. We used the cable and terminator supplied with drives. The 740s hang even with the drive powered off.

2 1

Re: DLT problems on F740s
by Luke Mewburn 01 Sep '99

01 Sep '99

Dave Atkin writes: > We are just in the process of replacing our two F230s with three F740s > and it's all going well apart from the DLT drives. We bought two Quantum > DLT7000 differential SCSI drives, but we can't get them to work. > > On startup the 740 hangs for a long time just after the memory test and > the "Complete" message. We've tried each drive on two 740s and they both > act the same. We used the cable and terminator supplied with drives. The > 740s hang even with the drive powered off. > > Any ideas anyone? Could it be that these drives are not really > differential - how could we tell? This sounds remarkably similar to the symptoms I saw when I accidentally plugged a single-ended (i.e, non-differential) DLT4000 into our F740. I removed the drive after I noticed it was hanging at a similar point to where yours was, and all was well. I've since had a wide differential DLT7000 on the F740 working without any problems. As to how to test the tape drives; no idea. `Check with your vendor'?

1 0

DLT problems on F740s
by Dave Atkin 01 Sep '99

01 Sep '99

We are just in the process of replacing our two F230s with three F740s and it's all going well apart from the DLT drives. We bought two Quantum DLT7000 differential SCSI drives, but we can't get them to work. On startup the 740 hangs for a long time just after the memory test and the "Complete" message. We've tried each drive on two 740s and they both act the same. We used the cable and terminator supplied with drives. The 740s hang even with the drive powered off. We've tried 5.2.2P1 and 5.3.2. Booting the diagnostic disk and running the scsi disgnostic tends to report SCSI errors of various types, eg "SCSI bus reset failed". Any ideas anyone? Could it be that these drives are not really differential - how could we tell? ------------------------------------------------------ Dave Atkin, Head of Technical Services Computing Service, University of York, YORK YO10 5DD Phone: +44-1904-433804 (ddi) Fax: +44-1904-433740 Email: D.Atkin(a)york.ac.uk ------------------------------------------------------

1 0

Re: Does the netapp support etherchannel/trunking?
by Sam Cramer 01 Sep '99

01 Sep '99

> Ehhhh, I'm still having problems with ifconfig of virtual interfaces. I > tried "ifconfig eta partner eta" and it took, although I don't know what > that means semantically. This means: in takeover mode, have the local "eta" interface takeover for the partner "eta" interface. > Then I came up with another enlightened idea "ifconfig eta -partner > 10.10.10.11" that does not do what "ifconfig eta partner 10.10.10.11" did > in the past (Oh, BTW, thanks NetApp for changing the syntax of the > command between revs). "partner" and "-partner" mean different things. "partner" specifies the takeover interface mapping; the argument after the "partner" keyword specifies the interface that should be taken over. "-partner" clears such a mapping, and takes no argument. These keywords were introduced in 5.2; we haven't changed the meaning of them since. "ifconfig" consumes its arguments one at a time, processing a keyword (and arguments, if applicable) and progressing on to the next keyword. Thus, when you specified "ifconfig eta -partner 10.10.10.11", "ifconfig" parsed it as follows: ifconfig eta -partner # clear the eta partner mapping ifconfig eta 10.10.10.11 # set eta's address Granted, this is somewhat counter-intuitive. > I should add that I tried "ifconfig eta partner 10.10.10.11" before only > to receive this error: > ifconfig: 10.10.10.11: bad vif partner address This is a very poor error message which will be fixed in an upcoming release. Partner mapping for vifs and ATM must be specified by interface name only; partner mapping for other interfaces can be specified by IP address or interface name. The error message is trying to tell you, in a round-about way, that you've specified a IP address, not an interface name. Thanks for your feedback; please don't hesitate to bring other such issues to our attention. Sam

1 0

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 September 1999