toasters

toasters@lists.teaparty.net

1 participants
13516 discussions

Re: bringing up a new eth interface on a pci nic card. some question s
by Rune Bakken 10 Oct '02

10 Oct '02

Daniel Finn <DFinn(a)studentadvantage.com> writes: > I'm trying to bring up a new interface on a pci nic card inside my F740. > Without being at the netapp is there any way to see if the nic card is > seeing a good link status. Here's what I have: > > na4m-be> ifconfig -a > e0: flags=200043<UP,BROADCAST,RUNNING> mtu 1500 > inet 10.209.68.211 netmask 0xffffff00 broadcast 10.209.68.255 > ether 00:a0:98:00:52:76 (100tx-fd-up) > e2a: flags=200043<UP,BROADCAST,RUNNING> mtu 1500 > inet 10.221.88.41 netmask 0xfffffff0 broadcast 10.221.88.47 > ether 00:20:fc:1e:20:cc (auto-100tx-up) This port has link > e3a: flags=42<BROADCAST,RUNNING> mtu 1500 > inet 10.221.88.41 netmask 0xfffffff0 broadcast 10.221.88.47 > ether 00:c0:95:e0:f4:00 (auto--down) This doesn't > Is there any type of command such as snoop for > Solaris or tcpdump for linux where I can see raw network traffic? pktt > My other question is how can I force this link to 100FDX. It's cisco gear > on the other side and I know that cisco stuff generally has trouble > auto-negotiating. ifconfig e2a mediatype 100tx-fd You would want to have the cisco side set to the same >>>>>>>>>>>>.rune -- Rune Bakken Senior System Administrator Telenor Business Solutions (Nextra), Communications/IP-Services Ph: +47 22 77 03 93

1 0

bringing up a new eth interface on a pci nic card. some question s
by Daniel Finn 10 Oct '02

10 Oct '02

I'm trying to bring up a new interface on a pci nic card inside my F740. Without being at the netapp is there any way to see if the nic card is seeing a good link status. Here's what I have: na4m-be> ifconfig -a e0: flags=200043<UP,BROADCAST,RUNNING> mtu 1500 inet 10.209.68.211 netmask 0xffffff00 broadcast 10.209.68.255 ether 00:a0:98:00:52:76 (100tx-fd-up) e2a: flags=200043<UP,BROADCAST,RUNNING> mtu 1500 inet 10.221.88.41 netmask 0xfffffff0 broadcast 10.221.88.47 ether 00:20:fc:1e:20:cc (auto-100tx-up) e2b: flags=42<BROADCAST,RUNNING> mtu 1500 ether 00:20:fc:1e:20:cd (auto-unknown-cfg_down) e2c: flags=42<BROADCAST,RUNNING> mtu 1500 ether 00:20:fc:1e:20:ce (auto-unknown-cfg_down) e2d: flags=42<BROADCAST,RUNNING> mtu 1500 ether 00:20:fc:1e:20:cf (auto-unknown-cfg_down) e3a: flags=42<BROADCAST,RUNNING> mtu 1500 inet 10.221.88.41 netmask 0xfffffff0 broadcast 10.221.88.47 ether 00:c0:95:e0:f4:00 (auto--down) e3b: flags=42<BROADCAST,RUNNING> mtu 1500 ether 00:c0:95:e0:f4:01 (auto--down) e3c: flags=42<BROADCAST,RUNNING> mtu 1500 ether 00:c0:95:e0:f4:02 (auto--down) e3d: flags=42<BROADCAST,RUNNING> mtu 1500 ether 00:c0:95:e0:f4:03 (auto--down) lo: flags=200049<UP,LOOPBACK,RUNNING> mtu 1536 inet 127.0.0.1 netmask 0xff000000 broadcast 127.0.0.1 I was at the data center the other day and when I plugged the cat5 in the link light lit up so I'm assuming that is all set. I believe I plugged it into the quad card in slot two, and I no for sure I plugged it into the port labeled "1". I cannot howerver seem to ping other servers on this network, whithin the same subnet. Is there any type of command such as snoop for Solaris or tcpdump for linux where I can see raw network traffic? My other question is how can I force this link to 100FDX. It's cisco gear on the other side and I know that cisco stuff generally has trouble auto-negotiating. Thanks Dan

2 1

AIT-3 drives on a F760 with LVD SCSI
by Moshe Linzer 10 Oct '02

10 Oct '02

I am in the process of upgrading my Qualstar library to AIT-3, and I thought it would be a good idea to ask if anyone is using AIT-3 on a filer? I am installing LVD SCSI cards on my 2 filers to connect directly to the drives, and I want to make sure everything will be compatible. Today the library has AIT-2 drives connected to the filers via SCSI converters. We are running OnTap 6.2.1 for the AIT-3 support. We are using Veritas Netbackup DC 3.4 with NDMP for backup. Thanks, Moshe -- ----------------------------------------------------------------------------- Moshe Linzer | On the Internet, IT Manager | National Semiconductor, Israel | nobody knows you're a moron. Phone: 972-9-970-2247 | Fax: 972-9-970-2001 | - Network Magazine Email: Moshe.Linzer(a)nsc.com | -----------------------------------------------------------------------------

1 0

NetApp/Sun df
by Motoyoshi 10 Oct '02

10 Oct '02

Dear Toasters, I could not find any answers on NOW site/Sun Site... Dose anyone had experience SUN df command displayed "-1" files field ? Environments: F720 w/ONTAP 5.3.6R2 Sun220 w/5.7 Symptoms: Although transmitted to NetApp by ftp. In rarely case , write failed. At this time If the result of df is seen It is -1. In other hosts (HOST-B), it is displayed normally. HOST-A host-a% df /proc (/proc ): 0 blocks 15813 files / (/dev/dsk/c0t0d0s0 ): 123072 blocks 52195 files /usr (/dev/dsk/c0t0d0s6 ): 148284 blocks 214554 files /dev/fd (fd ): 0 blocks 0 files /var (/dev/dsk/c0t0d0s5 ): 1731610 blocks 252653 files /opt (/dev/dsk/c0t0d0s4 ): 1421834 blocks 235910 files /export/home (/dev/dsk/c0t0d0s7 ):60153804 blocks 3800525 files /tmp (swap ): 3128960 blocks 111964 files /netapp (netapp_local:/vol/vol0):472371288 blocks -1 files /tester (netapp_local:/vol/vol0/home/sys_V5):472371288 blocks -1 files /u (netapp_local:/vol/vol0/home/repair_data):472371288 blocks -1 files /tester/INS (netapp_local:/vol/vol0/home/INS):472371288 blocks 7206566 files /user1 (netapp_local:/vol/vol0/user1):19177520 blocks -1 files /user2 (netapp_local:/vol/vol0/user2): 4194304 blocks 7206566 files /user3 (netapp_local:/vol/vol0/user3): 4194304 blocks 7206566 files HOST-B(Normal) host-b% df /proc (/proc ): 0 blocks 7805 files / (/dev/dsk/c0t0d0s0 ): 127416 blocks 47339 files /usr (/dev/dsk/c0t0d0s6 ): 252250 blocks 212855 files /dev/fd (fd ): 0 blocks 0 files /var (/dev/dsk/c0t0d0s5 ): 308820 blocks 94841 files /export/home (/dev/dsk/c0t0d0s7 ): 9989440 blocks 734548 files /opt (/dev/dsk/c0t0d0s4 ): 2016614 blocks 253612 files /tmp (swap ): 1439184 blocks 55180 files /netapp (netapp_local:/vol/vol0):472495256 blocks 7206575 files /tester (netapp_local:/vol/vol0/home/sys_V4):472495256 blocks 7206575 files /u (netapp_local:/vol/vol0/home/repair_data):472495256 blocks 7206575 files /user1 (netapp_local:/vol/vol0/user1):19177520 blocks 7206575 files /user2 (netapp_local:/vol/vol0/user2): 4194304 blocks 7206575 files /user3 (netapp_local:/vol/vol0/user3): 4194304 blocks 7206575 files Awaiting your reply by return. Regards, -Motoyoshi

1 0

Self contained shelves moving between filers
by Stephen C. Woods 10 Oct '02

10 Oct '02

If I have a storage shelf with a raidgroup and a volume (say vol3) on it (completely self contained), can I take the shelf and plug it into a different filer and use the volume? Same question but with multiple shelves (assuming that I move the whole set)? <scw> ----- Stephen C. Woods; UCLA SEASnet; 2567 Boelter hall; LA CA 90095; (310)-825-8614 Unless otherwise noted these statements are my own, Not those of the University of California. Internet mail:scw@seas.ucla.edu

3 2

Replacing a SCSI cable
by Igor Schein 09 Oct '02

09 Oct '02

Hi, what is the current recommendation as far as replacing a SCSI cable connecting the filer and the tape library? Does filer need to be rebooted, or is it safe to hot-swap the cable? Thanks Igor

1 0

tape duplication
by Igor Schein 09 Oct '02

09 Oct '02

Hi, I have 2 filers, DLT7000 tape drive attached to one of them, and SuperDLT tape drive attached to the other. What I need is to copy a DLT tape in dump format onto an SDLT tape, but I don't have enough disk space on either filer to restore the source tape. Does there exist a trick which would accomplish that? Thanks Igor

1 0

CIFS Directory Sizes
by Drew O'Donnell 09 Oct '02

09 Oct '02

Toasters, Anyone know of any good programs to use to check the directory size of a CIFS share that the administrators do not have access to? We use Security Explorer to change the security of shares where we have this situation. We are familiar with diruse, which works great, but will only run under the context of the user executing it. Thanks Drew

1 0

Sybase Backup server and filer
by Bruno Boyer 09 Oct '02

09 Oct '02

We are testing how to backup our Sybase db (dump) on a NFS mounted partition (with a filer). We simulate an NFS problem (by disconnecting the network link) during the backup, so the Backup Server falls in sleep state, the transaction log continues to increase and then Sybase tries to backup it, whereas the Backup Server is still sleeping. During the test, Sybase doesn't detect that the NFS server was not responding. How can I configure (is it possible) my Sybase to detect the problem and tell the backup server to stop instead of falling in sleeping mode ? How can I configure my Sybase server to backup my log transaction in another place (locally) in this case ? Is there an other strategy to backup our database on a filer ? We are running on Solaris 2.6, ASE 11.9.2, F840 Thanks Bruno ------------------------------------------------- This mail sent through IMP: http://horde.org/imp/

1 0

NFS tuning parameters for AIX version 5.1
by sanjay swamy 09 Oct '02

09 Oct '02

Have anyone installed Netapp Filers with IBM rs6000 server in a very high oltp environment. We are runing AIX version 5.1 . Netapp site does not have any recomendations for AIX . Can someone provide us with the recomended setings for NFS parameters on AIX version 5.1 & also recomended pathes for NFS , gigabit card & kernel for performance. --------------------------------- Do you Yahoo!? Faith Hill - Exclusive Performances, Videos, & more faith.yahoo.com

1 0

Root permissions failing.
by Chris Josephes 08 Oct '02

08 Oct '02

I have one Solaris host using a NetApp for home directories. I want to transition the content over to a newer NetApp, and take the other system out of commision. However, when I tried to rsync the files, it complained about permissions errors. I tried a manual chown, which failed, and I discovered that chmod fails as well. So, it would look like the Solaris client does not have root permissions on the NetApp. But, the export configs on both NetApps are identical, and I did specify root access in the exports file (and tried a couple of variations using "exportfs -i", including specifying the whole class C the Solaris host was in). Hostname resolution is going through the local files table, and then DNS. The new NetApp and the Solaris client both have host table entries for the IP of the other host. The new NetApp is a 720, running 5.3.6r1. Any ideas? -- _______________ Chris Josephes __/ MRNet/Onvoy \ chrisj(a)mr.net __/ www.onvoy.com / \________________/

1 1

RE: Root permissions failing.
by Toal, Dave 08 Oct '02

08 Oct '02

Chris, To allow world read-write access, try exportfs with 'exportfs -i -o anon=0 /vol/volname'? -----Original Message----- From: Chris Josephes To: toasters(a)mathworks.com Sent: 10/7/02 10:03 PM Subject: Root permissions failing. I have one Solaris host using a NetApp for home directories. I want to transition the content over to a newer NetApp, and take the other system out of commision. However, when I tried to rsync the files, it complained about permissions errors. I tried a manual chown, which failed, and I discovered that chmod fails as well. So, it would look like the Solaris client does not have root permissions on the NetApp. But, the export configs on both NetApps are identical, and I did specify root access in the exports file (and tried a couple of variations using "exportfs -i", including specifying the whole class C the Solaris host was in). Hostname resolution is going through the local files table, and then DNS. The new NetApp and the Solaris client both have host table entries for the IP of the other host. The new NetApp is a 720, running 5.3.6r1. Any ideas? -- _______________ Chris Josephes __/ MRNet/Onvoy \ chrisj(a)mr.net __/ www.onvoy.com / \________________/

1 0

RE: upgrading the ONTAP version
by Paul Caron 07 Oct '02

07 Oct '02

That fixed it. >From: "Potakamuri, Sreenivasa" <Sreenivasa.Potakamuri(a)netapp.com> >To: "'Paul Caron'" <caron(a)sig.com> >Subject: RE: upgrading the ONTAP version >Date: Fri, 4 Oct 2002 11:43:58 -0700 >MIME-Version: 1.0 > >Please remove the following line from /etc/registry.local file manually. > > options.cifs.access_logging.buffer_size=4096 > >That should fix your problem. We have filed a bug (number: 60595) for this. >We will make it online soon. > > >Please let me know the result after removing the line. > > >Thanks, >Sreeni

1 0

Summary: Gig Enet and Filer NFS problems
by Darragh, Stephen J 07 Oct '02

07 Oct '02

> Problem: > Clients using nfs (Sun and HP unix workstations) were taking much > longer to open files. > Home, Tools, and Project data was moved to the filer and it was > running GigE > To open a drawing, it took 2hrs vs 20min on a older Sun server > running 100mb ethernet. > Data OnTap v6.1.2R1 > > Once we made changes, it now takes 18min to open the same drawing (this is > a > normal time for the types of schmetics they are working on). > > Solution (so far): > Use options nfs.udp.xfersize 8192 (instead of the default 32768) > Also, set the filer to match the cisco switch for flow control > (cisco has send flow, filer now has receive) > > ToDo: > Investigation to see if full flow control will improve performance > even more. > Try enabling TCP over nfs > Make sure that the xfersize does not serously affect the few > machines we have on GigE that mount from the filer > > Thanks to the following for all the help and email (hope I didn't forget > anyone). > > Philip Meidell > John F. Detke > Paul Jones > Neil Stichbury > Mike Ball > Adam Fox > Neil Stichbury > devnull(a)adc.idt.com (whoever your are :-) > > ----------------- Details from some of the responses > > The major known issue is with NFS over UDP and packet drops causing the > UDP cascading error problem. If you are running NFS over UDP I'd strongly > suggest switching to NFS over TCP. > > I believe this is a buffering issue, where the Gig interface is > "overloading" a buffer somewhere on its way to a 100M interface, and > packets gets dropped. When that happens the entire UDP datagram gets > resent. Also check rsize/wsize on the client, it may work better set to > 8k, rather than the (default?) 32KB. > > This problem is related to network hardware, I've seen in most often on > Cisco gear but it happens with others too. A quick nfsstat on client(s) > can show the problem, look for retrans stats. > --------- > We had a similar problem and solved it by changing the UDP transfer size. > Have a look at bug ID 29146 which includes the following :- > > "In Data ONTAP 5.3.4 and earlier releases the default UDP transfer size > is > > 8192. In 5.3.5 and later releases the default is 32768. This larger value > improves performance in some situations, but may cause problems in others. > > Problem 1 - 100-Mbit client is reading from Gigabit interface With the > larger > default, problems may result when the Gigabit interface on the filer is > sending > to a 100-Mbit client. Switches can drop packets on the outbound 100-Mbit > port > because too many packets become queued due to the difference in line > speeds > and > the larger transfer size. Few complete 32K UDP datagrams are received by > the > > client, and the client assumes the filer has gone away and increases its > delay > between retries. Poor performance may be seen. If a client does not > specify > the > rsize and wsize parameters in the mount command, the filer's default UDP > transfer size is used. If a client does specify rsize and wsize, and the > values > are larger than the default, then the default is used. This means that you > may > see problems after you upgrade from 5.3.4 (or earlier release) to 5.3.5 > (or > later release) if the resulting transfer size is 32768. Problem 2 - > Multiple > > clients are reading from 100-Mbit interface When the UDP transfer size is > 32768 > and multiple clients are reading from a 100-Mbit interface, the driver > transmit > queue on the filer can overflow more readily and packets may be discarded. > This > can lead to erratic or poor performance on the clients." > > --- > First thing to check in GigE is typically flow control settings on the > switch, filer, and client side. Typically it's best to have both > transmit and receive flow control turned on. On the filer, it's > called full flowcontrol. That isn't the default for some switch > vendors and OS NICs. > > It's at least a start. Like most performance issues, you may > have to work several rounds of stuff to find the culprit. Before > you open a case with NTAP, which I strongly suggest, you may need > to quantify your performance in some way. MB/sec is a good one. > By putting a value on your performance it's easier to figure out > what areas could be wrong and also easier to figure out when > you can't get anymore based on your environment. That's the thing > with Gigabit, most clients can't max it out so you will hit a ceiling > for a single client that is less than the capacity of the wire. > Slower forms of Ethernet were easier in this way because you knew > pretty much where the ceiling was. > > --- > now that you have mentioned running Sun boxes try this > in the /etc/system file of one of them and see if you perceive > a performance improvement. > > set sq_max_size=2048 > set nstrpush = 90 > set nfs:nfs3_max_threads = 24 > set nfs:nfs3_nra = 10 > set nfs:nfs_max_threads = 24 > set nfs:nfs_nra = 10 > --- > > When you're using NFS over UDP with disparate speeds, i.e. gigabit to the > switch, then fast ethernet to clients, you can address performance > problems > in > one of two ways: > > 1) If all of your client machines are on fast ethernet (yep, that means NO > > gigabit clients) the simple approach is to set the filer option > > options nfs.udp.xfersize 8192 > > If you do have gigabit clients, doing the above will impact performance to > them, > in which case you have to do the more management intensive step two... > > 2) If you have some gigabit client machines, add the following options to > the > mount command on each 100 Mbit client machine: > wsize=8192,rsize=8192 > > >

1 0

Samba server as PDC ?
by Frank Bonnet 07 Oct '02

07 Oct '02

Hi Does anybody has already used a samba server as PDC for a filer ? We actually use samba servers with LDAP (openldap) authentication and I wonder if it would be possible to use a filer in such configuration ? Actually PCs use samba servers as PDC, the samba servers use NFS to store user's data thru NFS mounts. I know it is far to be the best configuration and I would like to let PC users use SMB directly to the filer using samba servers as PDC only. infos welcome. Thanks a lot -- Frank Bonnet

3 3

is it bad that disk scrubs don't finish
by Daniel Finn 07 Oct '02

07 Oct '02

More often than not the disk scrubbing on the netapps that I have don't finish. I assume this is because most of them see pretty high I/O and the netapp puts that I/O in higher order than the disk scrub. The disk scrub can be though of as a parity check correct?

2 1

Summary: Gig Enet and Filer NFS problems
by Darragh, Stephen J 05 Oct '02

05 Oct '02

> Problem: > Clients using nfs (Sun and HP unix workstations) were taking much > longer to open files. > Home, Tools, and Project data was moved to the filer and it was > running GigE > To open a drawing, it took 2hrs vs 20min on a older Sun server > running 100mb ethernet. > Data OnTap v6.1.2R1 > > Once we made changes, it now takes 18min to open the same drawing > (this is anormal time for the types of schmetics they are working on). > > Solution (so far): > Use options nfs.udp.xfersize 8192 (instead of the default 32768) > Also, set the filer to match the cisco switch for flow control > (cisco has send flow, filer now has receive) > > ToDo: > Investigation to see if full flow control will improve performance > Try enabling TCP over nfs > Make sure that the xfersize does not serously affect the few > machines we have on GigE that mount from the filer > > Thanks to the following for all the help and email (hope I didn't forget > anyone). > > Philip Meidell > John F. Detke > Paul Jones > Neil Stichbury > Mike Ball > Adam Fox > devnull(a)adc.idt.com (whoever your are :-) > > ----------------- Details from some of the responses > > The major known issue is with NFS over UDP and packet drops causing the > UDP cascading error problem. If you are running NFS over UDP I'd strongly > suggest switching to NFS over TCP. > > I believe this is a buffering issue, where the Gig interface is > "overloading" a buffer somewhere on its way to a 100M interface, and > packets gets dropped. When that happens the entire UDP datagram gets > resent. Also check rsize/wsize on the client, it may work better set to > 8k, rather than the (default?) 32KB. > > This problem is related to network hardware, I've seen in most often on > Cisco gear but it happens with others too. A quick nfsstat on client(s) > can show the problem, look for retrans stats. > --------- > We had a similar problem and solved it by changing the UDP transfer size. > Have a look at bug ID 29146 which includes the following :- > > "In Data ONTAP 5.3.4 and earlier releases the default UDP transfer size > is > > 8192. In 5.3.5 and later releases the default is 32768. This larger value > improves performance in some situations, but may cause problems in others. > > Problem 1 - 100-Mbit client is reading from Gigabit interface With the > larger > default, problems may result when the Gigabit interface on the filer is > sending > to a 100-Mbit client. Switches can drop packets on the outbound 100-Mbit > port because too many packets become queued due to the difference in line > speeds > and the larger transfer size. Few complete 32K UDP datagrams are received > by the client, and the client assumes the filer has gone away and > increases its delay between retries. Poor performance may be seen. If a > client does not specify > the rsize and wsize parameters in the mount command, the filer's default > UDP > transfer size is used. If a client does specify rsize and wsize, and the > values are larger than the default, then the default is used. This means > that you > may see problems after you upgrade from 5.3.4 (or earlier release) to > 5.3.5 (or > later release) if the resulting transfer size is 32768. Problem 2 - > Multiple > clients are reading from 100-Mbit interface When the UDP transfer size is > 32768 and multiple clients are reading from a 100-Mbit interface, the > driver > transmit queue on the filer can overflow more readily and packets may be > discarded. > This can lead to erratic or poor performance on the clients." > > --- > First thing to check in GigE is typically flow control settings on the > switch, filer, and client side. Typically it's best to have both > transmit and receive flow control turned on. On the filer, it's > called full flowcontrol. That isn't the default for some switch > vendors and OS NICs. > > It's at least a start. Like most performance issues, you may > have to work several rounds of stuff to find the culprit. Before > you open a case with NTAP, which I strongly suggest, you may need > to quantify your performance in some way. MB/sec is a good one. > By putting a value on your performance it's easier to figure out > what areas could be wrong and also easier to figure out when > you can't get anymore based on your environment. That's the thing > with Gigabit, most clients can't max it out so you will hit a ceiling > for a single client that is less than the capacity of the wire. > Slower forms of Ethernet were easier in this way because you knew > pretty much where the ceiling was. > > --- > > When you're using NFS over UDP with disparate speeds, i.e. gigabit to the > switch, then fast ethernet to clients, you can address performance > problems > in > one of two ways: > > 1) If all of your client machines are on fast ethernet (yep, that means NO > > gigabit clients) the simple approach is to set the filer option > > options nfs.udp.xfersize 8192 > > If you do have gigabit clients, doing the above will impact performance to > them, > in which case you have to do the more management intensive step two... > > 2) If you have some gigabit client machines, add the following options to > the > mount command on each 100 Mbit client machine: > wsize=8192,rsize=8192 > > >

1 0

RE: getting MRTG stats
by Manny Ortega 04 Oct '02

04 Oct '02

http://redhook.univ-wea.com/mrtg/ The name of my filer is pike... The only thing I've changed is the snmp password, everything else (mistakes, comments, et al) is unchanged... Hope this helps... -MannyO #------------------------------------------------------ ### Interface CPU for pike Utilization --MannyO Target[cpu]: 1.3.6.1.4.1.789.1.2.1.3.0&1.3.6.1.4.1.789.1.2.1.3.0:SMNP_PWD@12.31.213.6 RouterUptime[cpu]: public(a)12.31.213.6 MaxBytes[cpu]: 100 Title[cpu]: Pike Cpu utilization PageTop[cpu]: <H1>Pike Cpu utilization</H1> <TABLE> <TR><TD>System:</TD> <TD>pike.univ-wea.com in Universal Weather & Aviation - 8787 Tallyho - Houston, TX</TD></TR> <TR><TD>Maintainer:</TD> <TD>Steve Johnston - <A HREF="mailto:stevej@univ-wea.com">stevej(a)univ-wea.com</a> - 713.944.1622 x3650</TD></TR> </TABLE> ShortLegend[cpu]: % YLegend[cpu]: CPU Utilization Legend1[cpu]: CPU Utilization in % (Load) Legend2[cpu]: Legend3[cpu]:. Legend4[cpu]:. LegendI[cpu]:  Load:  LegendO[cpu]: Options[cpu]: gauge, integer, nopercent #--------------------------------------------------------------- ##### Pike CIFS Sessions Target[pikecifssessions]: .1.3.6.1.4.1.789.1.7.2.12.0&.1.3.6.1.4.1.789.1.7.2.12.0:SMNP_PWD@12.31.213.6 RouterUptime[pikecifssessions]: public(a)12.31.213.6 MaxBytes[pikecifssessions]: 9999999 Title[pikecifssessions]: Pike CIFS sessions PageTop[pikecifssessions]: <H1>Pike CIFS sessions</H1> <TABLE> <TR><TD>System:</TD><TD>Pike CIFS sessions</TD></TR> <TR><TD>Maintainer:</TD><TD>Manny Ortega</TD></TR> <TR><TD>Pike CIFS sessions</TD><TD>1.3.6.1.4.1.789.1.7.2.12.0</TD></TR> </TABLE> ShortLegend[pikecifssessions]: users #WithPeak[pikecifssessions]: ym YLegend[pikecifssessions]: # Sessions Legend1[pikecifssessions]: Number of users Legend2[pikecifssessions]: Legend3[pikecifssessions]:. Legend4[pikecifssessions]:. LegendI[pikecifssessions]:  Sessions:  LegendO[pikecifssessions]: Options[pikecifssessions]: gauge, nopercent, integer #### Pike c$ current usage Target[pikec$]: .1.3.6.1.4.1.789.1.5.4.1.3.3&.1.3.6.1.4.1.789.1.5.4.1.4.3:SMNP_PWD@12.31.213 .6 RouterUptime[pikec$]: public(a)12.31.213.6 MaxBytes[pikec$]: 28183960 Title[pikec$]: Pike c$ current usage Vol0 PageTop[pikec$]: <H1>Pike c$ current usage Vol0</H1> <TABLE> <TR><TD>System:</TD><TD>Pike c$ current usage Vol0</TD></TR> <TR><TD>Maintainer:</TD><TD>Manny Ortega</TD></TR> <TR><TD>Pike c$ kbytes total:</TD><TD>1.3.6.1.4.1.789.1.5.4.1.3.3</TD></TR> <TR><TD>Pike c$ kbytes used:</TD><TD>1.3.6.1.4.1.789.1.5.4.1.4.3</TD></TR> </TABLE> ShortLegend[pikec$]: B #WithPeak[pikec$]: dwmy kMG[pikec$]: k,M,G,T,P kilo[pikec$]: 1024 Unscaled[pikec$]: dwmy YLegend[pikec$]: Disk Utilization Legend1[pikec$]: Volume size Legend2[pikec$]: Volume usage Legend3[pikec$]: . Legend4[pikec$]: . LegendI[pikec$]: Max size:  LegendO[pikec$]: usage:  Options[pikec$]: gauge # ThreshMinI[pikec$]: $THRESHOLDMIN # ThreshMaxI[pikec$]: 21137970 # ThreshProgI[pikec$]: c$.bat # ThreshProgOKI[pikec$]: BATCHLOCthreshold_oki.bat # ThreshMinO[pikec$]: $THRESHOLDMIN ThreshMaxO[pikec$]: 21137970 ThreshProgO[pikec$]: c$.bat #ThreshProgOKO[pikec$]: c$ok.bat # 75% 21137970 #### Pike User_Data current usage Target[pike.user.data]: .1.3.6.1.4.1.789.1.5.4.1.3.1&.1.3.6.1.4.1.789.1.5.4.1.4.1:SMNP_PWD@12.31.213 .6 RouterUptime[pike.user.data]: public(a)12.31.213.6 MaxBytes[pike.user.data]: 175366844 Title[pike.user.data]: Pike User_Data current usage PageTop[pike.user.data]: <H1>Pike User_Data current usage</H1> <TABLE> <TR><TD>System:</TD><TD>Pike User_Data current usage</TD></TR> <TR><TD>Maintainer:</TD><TD>Manny Ortega</TD></TR> <TR><TD>Pike User_Data kbytes total:</TD><TD>1.3.6.1.4.1.789.1.5.4.1.3.1</TD></TR> <TR><TD>Pike User_Data kbytes used:</TD><TD>1.3.6.1.4.1.789.1.5.4.1.4.1</TD></TR> </TABLE> ShortLegend[pike.user.data]: B #WithPeak[pike.user.data]: dwmy kMG[pike.user.data]: k,M,G,T,P kilo[pike.user.data]: 1024 Unscaled[pike.user.data]: dwmy YLegend[pike.user.data]: Disk Utilization Legend1[pike.user.data]: Volume size Legend2[pike.user.data]: Volume usage Legend3[pike.user.data]:. Legend4[pike.user.data]:. LegendI[pike.user.data]: Total size:  LegendO[pike.user.data]: usage:  Options[pike.user.data]: gauge # ThreshMinI[pike.user.data]: $THRESHOLDMIN # ThreshMaxI[pike.user.data]: 21137970 # ThreshProgI[pike.user.data]: c$.bat # ThreshProgOKI[pike.user.data]: BATCHLOCthreshold_oki.bat # ThreshMinO[pike.user.data]: $THRESHOLDMIN ThreshMaxO[pike.user.data]: 131525133 ThreshProgO[pike.user.data]: usrdta.bat #ThreshProgOKO[pike.user.data]: usrdtaok.bat # 75% 131525133 #### Pike Homes current usage Target[pike.homes]: .1.3.6.1.4.1.789.1.5.4.1.3.5&.1.3.6.1.4.1.789.1.5.4.1.4.5:SMNP_PWD@12.31.213 .6 RouterUptime[pike.homes]: public(a)12.31.213.6 MaxBytes[pike.homes]: 75157220 Title[pike.homes]: Pike Homes current usage PageTop[pike.homes]: <H1>Pike Homes current usage</H1> <TABLE> <TR><TD>System:</TD><TD>Pike Homes current usage</TD></TR> <TR><TD>Maintainer:</TD><TD>Manny Ortega</TD></TR> <TR><TD>Pike Homes kbytes total:</TD><TD>1.3.6.1.4.1.789.1.5.4.1.3.5</TD></TR> <TR><TD>Pike Homes kbytes used:</TD><TD>1.3.6.1.4.1.789.1.5.4.1.4.5</TD></TR> </TABLE> ShortLegend[pike.homes]: B #WithPeak[pike.homes]: dwmy kMG[pike.homes]: k,M,G,T,P kilo[pike.homes]: 1024 Unscaled[pike.homes]: dwmy YLegend[pike.homes]: Disk Utilization Legend1[pike.homes]: Volume size Legend2[pike.homes]: Volume usage Legend3[pike.homes]:. Legend4[pike.homes]:. LegendI[pike.homes]: Total size:  LegendO[pike.homes]: usage:  Options[pike.homes]: gauge #ThreshMinI[pike.homes]: $THRESHOLDMIN #ThreshMaxI[pike.homes]: 21137970 #ThreshProgI[pike.homes]: c$.bat #ThreshProgOKI[pike.homes]: BATCHLOCthreshold_oki.bat #ThreshMinO[pike.homes]: $THRESHOLDMIN #ThreshMaxO[pike.homes]: 131525133 #ThreshProgO[pike.homes]: usrdta.bat #ThreshProgOKO[pike.homes]: usrdtaok.bat # 75% 56367915 -----Original Message----- From: Daniel Finn [mailto:DFinn@studentadvantage.com] Sent: Friday, October 04, 2002 4:30 PM To: 'toasters(a)mathworks.com' Subject: getting MRTG stats Could someone send me sample config files for getting mrtg stats from my netapp F760s and F740. Thanks Dan

1 0

getting MRTG stats
by Daniel Finn 04 Oct '02

04 Oct '02

Could someone send me sample config files for getting mrtg stats from my netapp F760s and F740. Thanks Dan

1 0

RE: ndmpcopy question
by Francett, Robert D (SAIC) 04 Oct '02

04 Oct '02

If nothing's changed, I believe it is: email to: majordomo(a)mathworks.com subject: unsubscribe toasters -----Original Message----- From: Dawn Lovell [mailto:dlovell@centurytel.net] Sent: Friday, October 04, 2002 10:30 AM To: Premanshu Jain Cc: toasters(a)mathworks.com Subject: Re: ndmpcopy question I encountered this same message when doing an incremental while migrating to a new filer. The NetApp support person with whom I spoke contacted one of the developers about it. The developer said that the error means that a directory being restored (to the target of the ndmpcopy) referred to an inode which wasn't in the dumpmap. The process assumes that the directory is correct and that the dumpmap is wrong, so it goes with the directory data instead of the dumpmap. I'm not clear on how that works if the affected file is not in the dump (how is it restored to the target machine?), but I'm undoubtedly missing part of the picture. :-) He mentioned that the message might be changed to only appear in debug output, since it should not signal anything that would cause data loss. I had started over with a new level 0 and was on a new incremental by the time I found out that info, so I can't comment as to whether the affected files were actually copied by the incremental that generated the message. Dawn Lovell dlovell(a)centurytel.net On Thu, 3 Oct 2002, Premanshu Jain wrote: > While doing level 1 ndmpcopy, i encounter the following error message in the > log: > > nacktheknife: LOG: RESTORE: nacktheknife: LOG: Inconsistent dumpmap on inode > 1819691. > nacktheknife: LOG: RESTORE: nacktheknife: LOG: Inconsistent dumpmap on inode > 1819692. > nacktheknife: LOG: RESTORE: nacktheknife: LOG: Inconsistent dumpmap on inode > 1819693. > nacktheknife: LOG: RESTORE: nacktheknife: LOG: Inconsistent dumpmap on inode > 1819694. > nacktheknife: LOG: RESTORE: nacktheknife: LOG: Inconsistent dumpmap on inode > 1819695. > nacktheknife: LOG: RESTORE: nacktheknife: LOG: Inconsistent dumpmap on inode > > WHAT DOES THIS MEAN ? > >

1 0

the list
by Paul J. Bell 04 Oct '02

04 Oct '02

my apologies for addressing this to the list. i have attempted, on several occasions, to remove myself from this list, in the approved fashion, all to no avail. on sunday, we will drop the domain of which my current e-mail address is a part, and consequently, all mail to me at that address will be returned to sender. what i have been trying to do is to unsubscribe so that i might re-subscribe under the new address. sounds simple, right. if anyone knows how i can accomplish this i would be most appreciative if you would share such knowledge with me. -paul

1 0

ndmpcopy question
by Premanshu Jain 04 Oct '02

04 Oct '02

While doing level 1 ndmpcopy, i encounter the following error message in the log: nacktheknife: LOG: RESTORE: nacktheknife: LOG: Inconsistent dumpmap on inode 1819691. nacktheknife: LOG: RESTORE: nacktheknife: LOG: Inconsistent dumpmap on inode 1819692. nacktheknife: LOG: RESTORE: nacktheknife: LOG: Inconsistent dumpmap on inode 1819693. nacktheknife: LOG: RESTORE: nacktheknife: LOG: Inconsistent dumpmap on inode 1819694. nacktheknife: LOG: RESTORE: nacktheknife: LOG: Inconsistent dumpmap on inode 1819695. nacktheknife: LOG: RESTORE: nacktheknife: LOG: Inconsistent dumpmap on inode WHAT DOES THIS MEAN ?

2 1

quota
by Lance R Bailey 04 Oct '02

04 Oct '02

hi, we hava a user who wants to know their user quota. the quota is set up with: * user@/vol/vol1/home 7G but they don't know it's 7G, and it's different from project to project, from home disk to home disk. if i cd into their home dir, and do a df, i see the tree quota not the user quota now, they could remsh into the filer, do a quota report and grep for their name, but we don't let users remsh into the filer :) are there any tools or approaches for this? -- email: lance_bailey(a)pmc-sierra.com box: Lance R. Bailey, unix Administrator vox: +1 604 415 6646 PMC-Sierra, Inc fax: +1 604 415 6151 105-8555 Baxter Place http://www.lydia.org/~zaphod Burnaby BC, V5A 4V7

3 4

Re: Finding who has files open (in use)
by Seth Moskowitz 04 Oct '02

04 Oct '02

I have used a product called Whohasnt.exe which has workied quite well. >From: "Maglinger, Paul" <PMAGLINGER(a)scvl.com> >To: "'NetApps list server'" <toasters(a)mathworks.com> >Subject: Finding who has files open (in use) >Date: Thu, 26 Sep 2002 15:24:02 -0500 > >Greetings toasters! > >Looking for a way to list files that are in use on the filer and who is >using them. I want an output similiar to what you would see if you went >into Windows Server Manager, selected the server and clicked on the "In >Use" >button, but I want something more user friendly than scrolling down looking >for the file name. Specifically, we are having problems with users leaving >files open, which prevents us from writing over them. I'm looking for a >way >to quickly track down who has this file open so they can be flogged, >keel-hauled, then drawn and quartered. Your thoughts, please? > >Remember, you are unique... just like everyone else! > > > >Paul Maglinger, A+, CA, CCA, CET, MCSE >Systems Administrator Shoe Carnival Inc. (812)867-4674 pmaglinger(a)scvl.com _________________________________________________________________ MSN Photos is the easiest way to share and print your photos: http://photos.msn.com/support/worldwide.aspx

2 1

Re: can't login at 6.2.1R1 ...
by Paul Caron 04 Oct '02

04 Oct '02

Are the hosts listed in your filer's /etc/hosts.equiv file and/or /etc/trusted.hosts file fully qualified? You might be experiencing a host name lookup failure. You could try just specifying IP addresses for the admin hosts as a temporary fix.

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