toasters September 2007

toasters@lists.teaparty.net

67 participants
41 discussions

snapmirror status / lag
by Brett Rabe 20 Sep '07

20 Sep '07

Howdy. Trivial question for y'all. I have two FAS3040 heads (-01 and -02) in an HA configuration. I have one FAS3040 head (-03) to which both of these are mirroring their data (every 5 minutes). The following is the status output on the backup toaster: mpls-toaster-03> snapmirror status Snapmirror is on. Source Destination State Lag Status mpls-toaster-01-priv:vol1 mpls-toaster-03:vol1 Snapmirrored 00:04:28 Idle mpls-toaster-02-priv:vol1 mpls-toaster-03:vol2 Snapmirrored 17895:54:16 Idle It all works just fine. I'm curious about the Lag time. What exactly does that mean? Why is it "17895:54:16"? It appeared that way after I did a failover of -02 (to -01) for the purposes of replacing a DIMM. Brought it back, did the giveback, and everything is working fine. The mirroring still seems to be working just great ... this is more of a curiosity question than anything, I guess. -bmr

3 2

ESX FC Give & Take
by Carl Howell 20 Sep '07

20 Sep '07

I'm troubleshooting an issue we're having with three ESX 3.01 hosts connected to a FAS3050c via Fibre Channel. After a takeover of the filer node that has active VM/LUN's running on it, the following appears in the /var/log/vmkernel file of the ESX host that owns the active VM's: Device vmhba2:0:2 has disappeared but is currently in use and could not be removed. Device vmhba2:0:3 has disappeared but is currently in use and could not be removed. On the other two ESX hosts, this appears in the /var/log/vmkernel file: Device vmhba2:0:2 has disappeared and has been removed. Device vmhba2:0:3 has disappeared and has been removed. Now, the VM's survive the takeover and are still up and running, but if I attempt a giveback, all three hosts lose access to these LUN's and the VM's go down. It appears to me that the ESX host that owns the active VM's has a SCSI reservation to these LUN's and a takeover is not enough to cause it to reset and remove that reservation(even though the paths failover properly). This type of behavior is mentioned in http://www.vmware.com/community/thread.jspa?messageID=752442. All of the timeout values have been verified etc. . . Thanks in advance for the help, --Carl

6 7

SCSI LTO3 Drive for NDMP Backup problems
by Ernesto Silvera 20 Sep '07

20 Sep '07

Hi all, We are getting errors while trying to replace with a new HP LTO3 drive, the actual LTO1 drive connected to the scsi adapter X2027A of a FAS920 NetApp Release 7.0.4 (see errors and actual configuration below). NetApp Log # 2475693 I would really appreciate any hints.. Actual Configuration Model Name: FAS920 NetApp Release 7.0.4 LTO1 drive connected to scsi Adapter slot 10: SCSI Host Adapter 10a (Adaptec AIC7902, <ONLINE>) HW Version 0.0 Ultra320 SCSI, Low Voltage Differential I/O base 0xdd00, size 0x100 memory mapped I/O base 0xa04c0000, size 0x2000 I/O base 0xdf00, size 0x100 slot 10: SCSI Host Adapter 10b (Adaptec AIC7902, <ONLINE>) HW Version 0.0 Ultra320 SCSI, Low Voltage Differential 4: Tape: Seagate ULTRIUM06242 1613 I/O base 0xde00, size 0x100 memory mapped I/O base 0xa04c2000, size 0x2000 I/O base 0xdc00, size 0x100 SCSI ERRORS Sat Sep 8 11:04:38 VET [adpch_timeoutd:warning]: adpch_timeoutd: 10a.3(0x0568ede0, 0x12): command timeout, quiescing bus to allow outstanding I/O to complete(ticks = 8). Sat Sep 8 11:04:46 VET [adpch_asyncd:warning]: adpch asyncd: Resetting SCSI 10a target 3 to clear outstanding I/O. Sat Sep 8 11:04:46 VET [adpch_intrd:warning]: adpch_timeoutd: 10a: unquiescing bus Sat Sep 8 11:04:57 VET [adpch_timeoutd:warning]: adpch_timeoutd: 10a.3(0x0568ede0, 0x12): command timeout, quiescing bus to allow outstanding I/O to complete(ticks = 8). Sat Sep 8 11:05:05 VET [adpch_asyncd:warning]: adpch asyncd: Resetting SCSI 10a target 3 to clear outstanding I/O. Sat Sep 8 11:05:05 VET [adpch_intrd:warning]: adpch_timeoutd: 10a: unquiescing bus Sat Sep 8 11:06:10 VET [adpch_intrd:warning]: Unexpected page code: Ultrium 3 serial number not available. Sat Sep 8 11:34:49 VET [rc:info]: relog syslog Sat Sep 8 11:33:24 VET [adpch_asyncd:warning]: adpch asyncd: Resetting SCSI bus 10a to clear outstanding I/O. Sat Sep 8 11:34:56 VET [adpch_asyncd:warning]: adpch asyncd: Resetting SCSI bus 10a to clear outstanding I/O. Sat Sep 8 11:36:28 VET [adpch_asyncd:warning]: adpch asyncd: Resetting SCSI bus 10a to clear outstanding I/O. Sat Sep 8 11:41:17 VET [adpch_asyncd:warning]: adpch asyncd: Resetting SCSI bus 10b to clear outstanding I/O.

5 6

Reconnect to tape drive
by Bryano 19 Sep '07

19 Sep '07

Hi, We had a power failure the other day (dont ask...!) and as a result it looks as though our filer was brought back up before the tape library was started. One of the drives in the library is directly connected to the filer however it is not showing as being available, when I run a sysconfig -t no tape drive is shown. How can I get the filer to see the tape drive without rebooting it again?? Thanks -- View this message in context: http://www.nabble.com/Reconnect-to-tape-drive-tf4480451.html#a12775717 Sent from the Network Appliance - Toasters mailing list archive at Nabble.com.

5 5

Connect to filer via CIFS from MacOS9/Dave
by Josef Radinger 18 Sep '07

18 Sep '07

Hello, We again have troubles connecting to a filer. Connecting via Windows XP,... works great, but some Clients are old MacOS9 systems, which cannot get updated as they hold software for which no OSX version exists (or it is to expensive). We can connect with the help of DAVE http://www.thursby.com/products/dave.html (Software which enables OS9 to connect to windows/samba,...). If we try to copy folders with files, the folders get created, but the data (the actual files) is not copied. The other way (copying from the filer to the Mac) is the same. If we try this with a samba-system everything is ok. Support from DAVE tells us that they had problems with ontap 6 and macos9, but he was not too sure about this as his tests were a long time ago. They tell us, that from there side everything seems to be ok and that it is very unlikely that we could get an updated version of DAVE for OS9. Does someone have the same problem and maybe a solution? ps.: DAVE under OSX works as expected. -- MfG Josef Radinger it-services Medizinische Universitaet Innsbruck

4 3

RE: HBA Cards
by Saxena, Mayank 17 Sep '07

17 Sep '07

hi, please contact NetApp support team, they should be able to help you with supported and recommended configurations. ~Mayank ________________________________ From: Hisham Sanad [mailto:Hisham.sanad@amwaj-it.com] Sent: Monday, September 17, 2007 2:08 AM To: toasters(a)mathworks.com Subject: HBA Cards Hi toaster, I have 2 servers with FCA2214 2GB FC HBA which were connected to HP SAN. Now we are going to switch to NetApp FAS2050. How can I know if these HBA cards are be compatible with the new setup. Also will have FC Cisco switch 9124

3 2

HBA Cards
by Hisham Sanad 17 Sep '07

17 Sep '07

Hi toaster, I have 2 servers with FCA2214 2GB FC HBA which were connected to HP SAN. Now we are going to switch to NetApp FAS2050. How can I know if these HBA cards are be compatible with the new setup. Also will have FC Cisco switch 9124

1 0

Re: DFM 3.6 Fails to Start
by Raj Patel 15 Sep '07

15 Sep '07

>I agree with Rohit, dfm should be the only application installed. I guess I'll go down this path - maybe stick it in a VM. However it doesn't strike me as a particularly efficient solution. We're trying to consolidate monitoring not spread it out. Is there a application compatibility list for DFM ? Can I install AV software at least ? How minimalist does the OS install need to be ? Does it play nice with Microsoft MOM ? Or does anyone use the 3rd party NetApp MOM monitoring pack ? Thanks again for the comments. Cheers, Raj.

1 0

DFM 3.6 Fails to Start
by Raj Patel 14 Sep '07

14 Sep '07

Hi, Anyone had issues with DFM 3.6 on Windows 2003 sp1 ? I've done a clean install of DFM and it installs fine but the Apache service fails to start - it can't talk to database (I get an error code 103 which doesn't seem to match anything on the NOW support site). The server is also acting as a domain controller and IBM Director management server. I initially thought maybe Director was hogging port 80 but netstat didn't show this to be the case and I couldn't enable https anyway as the dfm option command wouldn't run because it couldn't talk to the database (the service itself is running and there is no local firewall). The app has never worked so if theres some knack to installing it I'd be grateful for any advice. Cheers, Raj.

3 2

[Fwd: Network Appliance Customer Support Bulletin: Critical Upgrade - AT-FCX FW to v34 (CSB-0708-03)]
by Paul Letta 14 Sep '07

14 Sep '07

Hello, I can't stress the below bulletin enough. Our site experienced a 12+ hour outage on a FAS3040's first day of production due to this bug. On Sunday, I did a migration from 2 FAS940's and 1 F880 to a new FAS3040 with 3 SATA shelves. The first day of production on Monday was great, it took the load with ease and response was great. Level 0 backups were due. So at about 5pm on Monday, I started level 0's of the volumes on the new 3040. At 7pm, it panic'ed and halted. It said it lost 1 disk in the root aggr and was rebuilding, during which time it said it lost 2 more. I wasn't on the phone with L3 tech support more than 5 minutes before they said I was hit with this firmware bug. The shelves came with V33, and I hadn't put them in production before the May 31st email alert about the FW upgrade to V34 came out. So by around 11pm Monday we started the WAFL_check on the root aggr. And it finished about 5am. But there were a lot of lost files and support did not want us to accept the changes by this WAFL_check and do it against a snapshot from before the crash. We elected to accept the lost files and then search the snapshot and copy the lost files back to the live file system ourselves. But the file system was offline until about 11am, 3 hours into a work day for 2200 users -- not good. And then the 3040 was so slow during that day doing a double reconstruction that many services were not responsive at all, our email spool being the most visible. So, If you have shelves with this firmware -- update it as soon as possible ! The firmware upgrade was the first thing I did the night of the crash, and it only took about 15 minutes to do 3 shelves with 2 modules each. The good news is, we got a 4th shelf that was came later than the rest, and it came with V34 firmware. Paul 9 August 2007 Customer Support Bulletin CSB-0708-03 Critical Upgrade – AT-FCX FW to v34 *Summary**:* This Customer Support Bulletin is meant to reinforce and amplify the need to expeditiously upgrade to the AT-FCX v34 Firmware Release that is described in CSB-0705-03 . Customers are required to schedule a maintenance window and upgrade to AT-FCX FW v34 as soon as possible. *What is the potential service impact **if AT-FCX firmware is not upgraded to v34**:* Systems with AT-FCX I/O modules (X/SP-5612A-R5) not upgraded to firmware v34 can experience the following problems (see link above for more details): * WAFL® file system inconsistency * Write-data loss * Extended system outages * The need to run WAFL recovery utilities to restore data integrity * Unexpected reservation conflicts that in turn can cause additional service outages *What are the failure symptoms if AT-FCX firmware is not upgraded to v34?* Systems with AT-FCX I/O modules (X/SP-5612A-R5) not upgraded to firmware v34 would see the following failure symptoms related to pre-v34 firmware:** o Multiple RAID lost-write or checksum errors are seen on multiple drives attached to an AT-FCX shelf running shelf I/O module firmware version 33 or lower. These errors are caused by misdirected writes and/or reads to a disk. In some cases, not only is the location wrong, but the wrong disk is involved. o The AT-FCX I/O module can occasionally panic during shelf firmware downloading. This will result in loss of disk connectivity and storage multi-disk panic. *Additional Benefits* In addition to protection against the above-mentioned problems, the following fixes are included in firmware v34: * Corrective action that recognizes the failure of the first I/O AFTER a cache flush has failed. This I/O is returned with a senseKey/asc/ascq of 9/88/01 error that causes Data ONTAP® to take the drive out of service. The data on the drive will then be reconstructed normally without data loss. * Corrects an issue in which the reservation database is not updated properly, resulting in unexpected reservation conflicts that in turn can cause service outages. * Avoids a known problem in which a controller failover can occur while downloading shelf firmware. *Support* Please contact NetApp Global Services and/or Professional Services for questions or assistance concerning the firmware upgrade of AT-FCX (X/SP-5612A-R5) to v34.** *NOW Self-Service Options* * To register online for NOW access, go to http://now.netapp.com/newuser/ * To unsubscribe from the Customer Product Announcement distribution list, deselect the Field Alerts option in the Subscriptions <https://now.netapp.com/eservice/personal/loadSubscription.do?moduleName=MYP…> area on NOW. <https://now.netapp.com/eservice/personal/loadSubscription.do?moduleName=MYP…> * To review, order, and renew software subscriptions, click Manage Service Contracts on the Service and Support <http://now.netapp.com/Self-Service/Forms/SupportHome.asp> home page on NOW. The purpose of this communication is for NetApp Global Services to notify its installed base end users about urgent and important product information that may affect product performance or reliability. The information contained herein and the distribution list are Network Appliance™ confidential materials that are subject to restrictions on redistribution and that cannot be shared outside of this email distribution list. © 2007 Network Appliance, Inc. All rights reserved. Specifications subject to change without notice. NetApp, the Network Appliance logo, Data ONTAP, and WAFL are registered trademarks and Network Appliance and NOW are trademarks of Network Appliance, Inc. in the U.S. and other countries. All other brands or products are trademarks or registered trademarks of their respective holders and should be treated as such.

8 12

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 2007