toasters

toasters@lists.teaparty.net

2 participants
13529 discussions

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

Migrating data from Trad vol to Flex vol
by Ken Williams 14 Sep '07

14 Sep '07

I have some data still in traditional volumes that I would like to move to flex vols. The problem is I have snapshot data that we are keeping for a few more years. So is QSM my only option or can ndmpcopy work with snapshots? Has anyone had/seen anything similar? Your thoughts are appreciated. Thanks, __________________________________________________________ Ken Williams Storage Administrator, Business Technology Operations Sacramento Municipal Utility District E-Mail: kwillia(a)smud.org Phone: (916) 732-6744 Cell: (916) 240-4213

4 3

Remove disk from vol0??
by Bryano 10 Sep '07

10 Sep '07

Hi, I currently administer a FAS 940 and the vol0 volume has been assigned 5 disks giving it a total of 191GB of space however only 3% of this is used so in effect 3 of the disks are wasted. Is there anyway to remove 3 disks from this volume? the filer is running ontap 6.5.6 so we are not using aggregates. Regards -- View this message in context: http://www.nabble.com/Remove-disk-from-vol0---tf4413856.html#a12590665 Sent from the Network Appliance - Toasters mailing list archive at Nabble.com.

8 8

RE: No spare disks for root
by Alan McLachlan 10 Sep '07

10 Sep '07

Hi Mike, Agreed - but this can be avoided with judicious use of quota management - hence my comment"Any other issues are about configuration and administration and are easy to deal with if you know what you're doing." Having all CIFS shares and/or NFS exports coming from withing quota'd qtrees is something I would tend to do and recommend anyway, along with SNMP traps for warning thresholds etc., but admittedly it only takes someone to slack off and start putting data outside those qtrees and then you do run the risk of a full rootvol. Hence why a small FlexVol dedicated to root is the way to go if you're able to run newer versions of OnTap. Unfortunately in the situation under discussion it's an old F760 with a pre-7 version of version of OnTAP and no support contract therefore no way to (legally) upgrade the OS. Regards, Alan. _____________________________________________ From: "Sphar, Mike" [mailto:Mike_Sphar@bmc.com] Sent: Thursday, 6 September 2007 2:51 AM To: <toasters(a)mathworks.com> Subject: RE: No spare disks for root I certainly had many many years of filers sharing data on the root volume as well, but I would point out that one danger with that is sometimes running out of space on the root volume can do Bad Things(tm). I agree though that if I had an already production system serving data sharing the root volume I wouldn't go into panic mode over it, but if I had the freedom to start over and do it "right", I probably would. Though still, if I was starting over I'd prefer to upgrade to a version of the OS that supports flexvols, and then use a small root flexvol. -- Michael W. Sphar - IS&T - Lead Systems Administrator SMBU Engineering Support Services, BMC Software -----Original Message----- From: owner-toasters(a)mathworks.com [mailto:owner-toasters@mathworks.com] On Behalf Of Alan McLachlan Sent: Tuesday, September 04, 2007 11:52 PM To: toasters(a)mathworks.com Subject: RE: No spare disks for root Hi Coolhand, Why do you feel that having the small amount of root info in the /etc directory in the same volume as your data is a problem? Having all the disks on the root volume isn't really a problem. I installed many filers in the days before NetApp started recommending people dedicate two disks for the root volume, and never had any issues with using the root vol for data. In fact most of my customers for five years or so when I worked as an SE for a NetApp reseller user vol0 for data such as user homedirs and workgroup directories and no-one even really thought about it. A second volume is needed only where you want to change volume level options ("minra", "noatimeupdate" etc), or have a separate volume for database tablespace files or iSCSI/FCP LUN's. Qtree quotas can deal with most space restriction requirements. Also you will want multiple volumes if you're doing bare-metal backups ("snapmirror to tape") or DR replication for application data volumes with differing RTO's/RPO's. The only real advantage to be gained by dedicating disks for the root volume in earlier versions (before Ontap 7 with FlexVols with it's obvious additional benefits) is that the disks for a dedicated non-root data volume can be moved as a set to another filer and that data volume is then available on the second filer as a foreign volume without having to do extra steps after boot. Any other issues are about configuration and administration and are easy to deal with if you know what you're doing. The obvious major disadvantage to dedicating two disks for the root volume is the vast waste of storage space* at least in Ontap 7 with FlexVol you can have a dedicated root vol for administrative separation purposes without wasting space, although you now if you move physical disk sets all volumes in the same aggregate are visible on the filer you move the disks to. The administrative issues you mentioned are easily fixed. Just rerun CIFS setup and reconfigure to give yourself access. Or if you don't want to change an existing domain configuration you can modify the security information in /etc via the "rdfile" and "wrfile" commands with cut-and-paste, i.e. add the SID for the windows user to the "Administrators" group in lclgroups.cfg and/or add a mapping for the Windows user to "root" in usermap.cfg. Another thing to check is the security style on the volume and the permissions on the /etc directory. One handy thing to do is make the /etc directory a qtree: Filer> qtree create etcnew Copy the contents of /etc to /etcnew Rename /etc to /etcold (from Windows) Rename /etcnew to /etc Then you can delete the /etcold directory or keep it there for a backup. The advantage of doing this is it allows you to separate out /etc for quota management purposes. Also, for a CIFS-only filer in a large domain environment where you want to restrict access to /etc to only specific filer admins you can set the security style on /etc to "unix" then create mappings to "root" in usermap.cfg for specific Windows admin accounts while locking the rest of the "domain admins" out of /etc. You can edit the UNIX permissions on the new /etc qtree using the free SecureShare Access". I've done this on a couple of CIFS-only sites where they had lots of domain admins but wanted only specifically trained filer admins to have access to /etc and it works a treat. Hope this helps. If you need any more information send me an email to my personal address, AlanMac"at"technologist.com ^ (to avoid spambots when this post goes to the toasters archive web page) Regards, Alan McLachlan Technical Consultant EBM-2 Project Queensland Health Ph. +61 7 31311618 Mobile +61 428 655644 _____________________________________________ From: coolhand2120 [mailto:tony@claydesign.com] Sent: Wednesday, 5 September 2007 9:34 AM To: <toasters(a)mathworks.com> Subject: No spare disks for root I have a netapp F760 with 4 FC shelves, because I'm ignorant of how these things work I added all my disks (28x72gb) to my root volume. Now I have no spare disks, and no room in any shelf to add disks. What do I do? I don't care about the information on the filer, I just want a root volume with 2 disks! I promise not to use all the disks on a single root volume again! I have a /etc directory on a NFS host. I don't have NFS license though so I can't copy files onto the filer via NFS, I have a CIFS license but for some reasons it says "access denied" when a CIFS client tries to access it. I have console access and telnet access, I'm so frustrated I took the filer home so I have physical access. I don't however have a support contract with netapp or an account on their site (pending their review of my application). I can't create any new volumes because all the disks are assigned to the root volume vol0. Is there anyway to fix this? -Coolhand2120 -- View this message in context: http://www.nabble.com/No-spare-disks-for-root-tf4380728.html#a12487751 Sent from the Network Appliance - Toasters mailing list archive at Nabble.com. ***************************************************************** This email, including any attachments sent with it, is confidential and for the sole use of the intended recipient(s). This confidentiality is not waived or lost, if you receive it and you are not the intended recipient(s), or if it is transmitted/ received in error. Any unauthorised use, alteration, disclosure, distribution or review of this email is strictly prohibited. The information contained in this email, including any attachment sent with it, may be subject to a statutory duty of confidentiality if it relates to health service matters. If you are not the intended recipient(s), or if you have received this email in error, you are asked to immediately notify the sender by telephone collect on Australia +61 1800 198 175 or by return email. You should also delete this email, and any copies, from your computer system network and destroy any hard copies produced. If not an intended recipient of this email, you must not copy, distribute or take any action(s) that relies on it; any form of disclosure, modification, distribution and/or publication of this email is also prohibited. Although Queensland Health takes all reasonable steps to ensure this email does not contain malicious software, Queensland Health does not accept responsibility for the consequences if any person's computer inadvertently suffers any disruption to services, loss of information, harm or is infected with a virus, other malicious computer programme or code that may occur as a consequence of receiving this email. Unless stated otherwise, this email represents only the views of the sender and not the views of the Queensland Government. ****************************************************************

3 2

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