toasters

toasters@lists.teaparty.net

2 participants
13529 discussions

RE: iSCSI HOWTO question
by Benn, Paul 11 Jan '04

11 Jan '04

> So consider doing the disk configuration on the console. ...unless you're using SnapDrive. > -----Original Message----- > From: Michel Geldenhuys [mailto:michel@geldenhuys.com] > Sent: Thursday, January 08, 2004 10:58 PM > To: toasters(a)mathworks.com > Subject: RE: iSCSI HOWTO question > > Hi, > > Just beware that is you do the stuff through a Terminal > Server connection, you might not see the new disk devices in > disk administrator. > So consider doing the disk configuration on the console. > > Kind regards, > Michel Geldenhuys > > > -----Original Message----- > > From: owner-toasters(a)mathworks.com > [mailto:owner-toasters@mathworks.com] > > On Behalf Of Haber, David J. > > Sent: jeudi 8 janvier 2004 18:43 > > To: toasters(a)mathworks.com > > Subject: RE: iSCSI HOWTO question > > > > Once the Lun is created and properly set up on the Windows (2000?) > > server, you should be able to do a scan of your drives in > disk manager > > and it will show up. Then format and your good to go. > > > > -----Original Message----- > > From: Geoff Hardin [mailto:geoff.hardin@dalsemi.com] > > Sent: Thursday, January 08, 2004 11:59 AM > > To: toasters > > Subject: iSCSI HOWTO question > > > > I am new to the SAN environment, and most especially to > the iSCSI > > way of doing things. I have the iSCSI protocol enabled on my filer, > and > > I have the Microsoft iSCSI initiator downloaded and installed on my > PC. > > From the filer, I have created a couple LUNs on my filer, I have > > created igroups, mapped the LUNs to the igroups, set the > create_ucode > > option to on, and started the iSCSI service. On the > Windows system, I > > have added the target portal, logged on, and I can see an active > > session. I think I have all the basics under control. > > What I can't seem to figure out is how the LUNs now show up as > being > > somehow connected to my Windows computer. I'm sure I've missed > > something, but I can't figure out what. I've tried reading > the "ONTAP > > SysAdmin Block Access Management Guide" and working through the > examples > > step by step, still to no avail. > > Some details: > > > > Host (initiator): Windows 2000 > > ONTAP version 6.4.3 > > toaster> iscsi show adapter > > Adapter: iswta > > Slot: N/A > > Description: NetApp Software Implementation > > Status: Online > > Target Portal Groups: > > portal group 1: inet 192.168.1.3 port 3260 > > > > toaster> igroup show > > windows-igroup0 (iSCSI) (ostype: windows): > > iqn.1992-08.com.netapp:sn.123456789 > > > > toaster> lun show -v > > /vol/vol0/iscsi/lun0 10.0g (10742215680) (r/w, > online, > > mapped) > > Comment: "iSCSI test lun0" > > Serial#: HPlwFYo6bJoZ > > Share: none > > Space Reservation: enabled > > Multiprotocol Type: windows > > Maps: windows-igroup0=0 > > /vol/vol0/iscsi/lun1 10.0g (10742215680) (r/w, > online, > > mapped) > > Comment: "iSCSI test lun1" > > Serial#: HPlwFYo6bQDV > > Share: none > > Space Reservation: enabled > > Multiprotocol Type: windows > > Maps: windows-igroup0=1 > > > > toaster> iswt interface show > > Interface e0 enabled > > > > toaster> iscsi nodename > > iSCSI target nodename: iqn.1992-08.com.netapp:sn.123456789 > > > > > > > > Any help would be greatly appreciated. > > > > Thanks, > > > > Geoff Hardin > > geoff.hardin(a)dalsemi.com > > > > > > > > > > > > Confidentiality Notice: > > This message, and any attachments, may contain information that is > > confidential, privileged, and/or protected from disclosure > under state > and > > federal laws that deal with the privacy and security of medical > > information. If you received this message in error or through > > inappropriate means, please reply to this message to notify > the Sender > > that the message was received by you in error, and then permanently > delete > > this message from all storage media, without forwarding or > retaining a > > copy. > >

4 3

RE: ntp time synchronization is not working
by Jason Truong 09 Jan '04

09 Jan '04

thanks alot guys for clearing this up. I'll try to update my version of ntp. I really hate to upgrade my Netapp unless I HAVE to. Right now I have the device syncing with an external time source but would prefer to use our internal time server. I'll see how far I get with this. Thanks again. Jason -----Original Message----- From: Frank Bonnet [mailto:bonnetf@bart.esiee.fr] Sent: Friday, January 09, 2004 2:23 AM To: Stephane Bentebba Cc: Jerry; Jason Truong; toasters(a)mathworks.com Subject: Re: ntp time synchronization is not working On Fri, Jan 09, 2004 at 10:10:02AM +0100, Stephane Bentebba wrote: > i personnally also tried to sync a netapp on a linux box > it didn't work either > i think netapp don't want to support linux ntp service > why ?... Hi all NTP is a UNIX service described in RFC 1119 it is not "Linux special" I use NTP to sync two filers and I had troubles with some old versions of Ontap and NTP. Actually the bug _seems_ to be corrected. -- Frank Bonnet

1 0

ntp time synchronization is not working
by Jason Truong 09 Jan '04

09 Jan '04

I have ntp running on my of my linux servers which acts as the time server for my network. I want to have my netapp sync to this server using ntp. However I keep getting error messages like: Tue Jan 6 10:52:19 PST [Java Thread:ALERT]: TimeDaemon: Time server 10.1.88.44 is not responding to time synchronization requests Solaris, linux and windows can sync to this server except for my netapp. (Running NetApp Release 6.2.1R1) Does anyone experience the same problem ... and if so, how did you fix this? Thank you. Here is my ntp.conf file: #################################################### restrict 127.0.0.1 # syncing with mule server 192.168.1.3 restrict 192.168.1.3 mask 255.255.255.255 nomodify notrap noquery # ntp-cup.external.hp.com in Cupertino, CA server ntp-cup.external.hp.com # ip address 192.6.38.127 # clock.isc.org in Palo Alto, CA server clock.isc.org # ip address 192.5.5.250 # Use local system time if time servers are not available server 127.127.1.0 # local clock fudge 127.127.1.0 stratum 10 driftfile /etc/ntp/drift broadcastdelay 0.008 authenticate yes keys /etc/ntp/keys ############################################# Jason Truong Plumtree Software (415) 399-7006

4 3

RE: iSCSI HOWTO question
by Neto, Antonio Jose Rodrigues 09 Jan '04

09 Jan '04

Hi Michel, This is neto from NetApp Brazil. How are you? The terminal services is not good to manage new hardware resources. 2 tips : - If you need to use Terminal Services - Workaround : Please logoff your session and login again. Now I can see the new hardware resources, the NetApp disks. - Another tip is that you can use another terminal services, for example : Pc Anywhere (not free) or UltraVNC (free) - http://sourceforge.net/projects/ultravnc . I've make tests using PC Anywhere and UltraVNC and this problems doesn't ocurr. If you need more informations or any help, please let me know. Best Regards from Brazil. neto -----Original Message----- From: Michel Geldenhuys [mailto:michel@geldenhuys.com] Sent: Friday, January 09, 2004 4:58 AM To: toasters(a)mathworks.com Subject: RE: iSCSI HOWTO question Hi, Just beware that is you do the stuff through a Terminal Server connection, you might not see the new disk devices in disk administrator. So consider doing the disk configuration on the console. Kind regards, Michel Geldenhuys > -----Original Message----- > From: owner-toasters(a)mathworks.com [mailto:owner-toasters@mathworks.com] > On Behalf Of Haber, David J. > Sent: jeudi 8 janvier 2004 18:43 > To: toasters(a)mathworks.com > Subject: RE: iSCSI HOWTO question > > Once the Lun is created and properly set up on the Windows (2000?) > server, you should be able to do a scan of your drives in disk manager > and it will show up. Then format and your good to go. > > -----Original Message----- > From: Geoff Hardin [mailto:geoff.hardin@dalsemi.com] > Sent: Thursday, January 08, 2004 11:59 AM > To: toasters > Subject: iSCSI HOWTO question > > I am new to the SAN environment, and most especially to the iSCSI > way of doing things. I have the iSCSI protocol enabled on my filer, and > I have the Microsoft iSCSI initiator downloaded and installed on my PC. > From the filer, I have created a couple LUNs on my filer, I have > created igroups, mapped the LUNs to the igroups, set the create_ucode > option to on, and started the iSCSI service. On the Windows system, I > have added the target portal, logged on, and I can see an active > session. I think I have all the basics under control. > What I can't seem to figure out is how the LUNs now show up as being > somehow connected to my Windows computer. I'm sure I've missed > something, but I can't figure out what. I've tried reading the "ONTAP > SysAdmin Block Access Management Guide" and working through the examples > step by step, still to no avail. > Some details: > > Host (initiator): Windows 2000 > ONTAP version 6.4.3 > toaster> iscsi show adapter > Adapter: iswta > Slot: N/A > Description: NetApp Software Implementation > Status: Online > Target Portal Groups: > portal group 1: inet 192.168.1.3 port 3260 > > toaster> igroup show > windows-igroup0 (iSCSI) (ostype: windows): > iqn.1992-08.com.netapp:sn.123456789 > > toaster> lun show -v > /vol/vol0/iscsi/lun0 10.0g (10742215680) (r/w, online, > mapped) > Comment: "iSCSI test lun0" > Serial#: HPlwFYo6bJoZ > Share: none > Space Reservation: enabled > Multiprotocol Type: windows > Maps: windows-igroup0=0 > /vol/vol0/iscsi/lun1 10.0g (10742215680) (r/w, online, > mapped) > Comment: "iSCSI test lun1" > Serial#: HPlwFYo6bQDV > Share: none > Space Reservation: enabled > Multiprotocol Type: windows > Maps: windows-igroup0=1 > > toaster> iswt interface show > Interface e0 enabled > > toaster> iscsi nodename > iSCSI target nodename: iqn.1992-08.com.netapp:sn.123456789 > > > > Any help would be greatly appreciated. > > Thanks, > > Geoff Hardin > geoff.hardin(a)dalsemi.com > > > > > > Confidentiality Notice: > This message, and any attachments, may contain information that is > confidential, privileged, and/or protected from disclosure under state and > federal laws that deal with the privacy and security of medical > information. If you received this message in error or through > inappropriate means, please reply to this message to notify the Sender > that the message was received by you in error, and then permanently delete > this message from all storage media, without forwarding or retaining a > copy.

1 0

Re: ntp time synchronization is not working
by Michel GELDENHUYS 09 Jan '04

09 Jan '04

Hello, Maybe should you check if your NTP server can be upgraded to a new one. There might be a flaw in the implementation of the protocol that might prevent the Filer to correctly understand the time sync message or on the other hand, a flaw that might prevent NTP server to correctly understand the request from the Filer. I must say that I'm very surprised that a Linux NTP does not work correctly with a Filer... Indeed, we rely on a NTP server on Windows NT 4.0 which is W32Time from Microsoft, a very simple product, and I haven't got any problem synchronizing our Filers with it. Since MS is well known for their "particular" implentation of public protocols, I would not be surprised to have problems with it, which it's not the case! Kind regards, Michel Geldenhuys Danone Belgium SA/NV +32 2 776 68 23 michel.geldenhuys(a)danone.com Stephane Bentebba <stephane.bentebba(a)fps.fr> Sent by: owner-toasters(a)mathworks.com 09/01/2004 10:10 To: Jerry <juanino(a)yahoo.com> cc: Jason Truong <JasonT(a)plumtree.com>, toasters(a)mathworks.com Subject: Re: ntp time synchronization is not working i personnally also tried to sync a netapp on a linux box it didn't work either i think netapp don't want to support linux ntp service why ?... Jerry wrote: >I'm pretty sure I am syncing to a linux box. Can you >run ntpq -c peers or ntpq -c ass on the linux box? >Try taking out your restrict line, restarting and then >try it... this will just confirm you are not >restricting yourself on accident. > >--- Jason Truong <JasonT(a)plumtree.com> wrote: > > >>I have ntp running on my of my linux servers which >>acts as the time server for my network. I want to >>have my netapp sync to this server using ntp. >>However I keep getting error messages like: >> Tue Jan 6 10:52:19 PST [Java Thread:ALERT]: >>TimeDaemon: Time server 10.1.88.44 is not responding >>to time synchronization requests >> >>Solaris, linux and windows can sync to this server >>except for my netapp. (Running NetApp Release >>6.2.1R1) >>Does anyone experience the same problem ... and if >>so, how did you fix this? >>Thank you. >>Here is my ntp.conf file: >>#################################################### >>restrict 127.0.0.1 >># syncing with mule >>server 192.168.1.3 >>restrict 192.168.1.3 mask 255.255.255.255 nomodify >>notrap noquery >> >># ntp-cup.external.hp.com in Cupertino, CA >>server ntp-cup.external.hp.com >># ip address 192.6.38.127 >> >># clock.isc.org in Palo Alto, CA >>server clock.isc.org >># ip address 192.5.5.250 >> >># Use local system time if time servers are not >>available >>server 127.127.1.0 # local clock >>fudge 127.127.1.0 stratum 10 >> >>driftfile /etc/ntp/drift >>broadcastdelay 0.008 >>authenticate yes >>keys /etc/ntp/keys >>############################################# >> >>Jason Truong >>Plumtree Software >>(415) 399-7006 >> >> >> >> > > >__________________________________ >Do you Yahoo!? >Yahoo! Hotjobs: Enter the "Signing Bonus" Sweepstakes >http://hotjobs.sweepstakes.yahoo.com/signingbonus > > >

1 0

RE: iSCSI HOWTO question
by Haber, David J. 09 Jan '04

09 Jan '04

Once the Lun is created and properly set up on the Windows (2000?) server, you should be able to do a scan of your drives in disk manager and it will show up. Then format and your good to go. -----Original Message----- From: Geoff Hardin [mailto:geoff.hardin@dalsemi.com] Sent: Thursday, January 08, 2004 11:59 AM To: toasters Subject: iSCSI HOWTO question I am new to the SAN environment, and most especially to the iSCSI way of doing things. I have the iSCSI protocol enabled on my filer, and I have the Microsoft iSCSI initiator downloaded and installed on my PC. From the filer, I have created a couple LUNs on my filer, I have created igroups, mapped the LUNs to the igroups, set the create_ucode option to on, and started the iSCSI service. On the Windows system, I have added the target portal, logged on, and I can see an active session. I think I have all the basics under control. What I can't seem to figure out is how the LUNs now show up as being somehow connected to my Windows computer. I'm sure I've missed something, but I can't figure out what. I've tried reading the "ONTAP SysAdmin Block Access Management Guide" and working through the examples step by step, still to no avail. Some details: Host (initiator): Windows 2000 ONTAP version 6.4.3 toaster> iscsi show adapter Adapter: iswta Slot: N/A Description: NetApp Software Implementation Status: Online Target Portal Groups: portal group 1: inet 192.168.1.3 port 3260 toaster> igroup show windows-igroup0 (iSCSI) (ostype: windows): iqn.1992-08.com.netapp:sn.123456789 toaster> lun show -v /vol/vol0/iscsi/lun0 10.0g (10742215680) (r/w, online, mapped) Comment: "iSCSI test lun0" Serial#: HPlwFYo6bJoZ Share: none Space Reservation: enabled Multiprotocol Type: windows Maps: windows-igroup0=0 /vol/vol0/iscsi/lun1 10.0g (10742215680) (r/w, online, mapped) Comment: "iSCSI test lun1" Serial#: HPlwFYo6bQDV Share: none Space Reservation: enabled Multiprotocol Type: windows Maps: windows-igroup0=1 toaster> iswt interface show Interface e0 enabled toaster> iscsi nodename iSCSI target nodename: iqn.1992-08.com.netapp:sn.123456789 Any help would be greatly appreciated. Thanks, Geoff Hardin geoff.hardin(a)dalsemi.com Confidentiality Notice: This message, and any attachments, may contain information that is confidential, privileged, and/or protected from disclosure under state and federal laws that deal with the privacy and security of medical information. If you received this message in error or through inappropriate means, please reply to this message to notify the Sender that the message was received by you in error, and then permanently delete this message from all storage media, without forwarding or retaining a copy.

2 1

RE: iSCSI HOWTO question - Summary
by Neto, Antonio Jose Rodrigues 08 Jan '04

08 Jan '04

Hi Geoff, 1) Please use the FilerView to remove the filer nodename. 2) Click Right-Click on My Computer - manage - disk management Write Signature -> Format and assign the letter (e.g. N:\ = NetApp) If you have any questions please let me know. Best Regards Neto -----Original Message----- From: Geoff Hardin [mailto:geoff.hardin@dalsemi.com] Sent: Thursday, January 08, 2004 3:59 PM To: toasters Subject: Re: iSCSI HOWTO question - Summary Thanks to everyone who responded so quickly. Turns out I had two problems: 1) I had the wrong nodename in the node in the igroup (I had the filer's nodename, not the Windows system's nodename), and 2) I'm a UNIX system admin so I didn't know how to "mount" the drives to the Windows system. Special thanks to Antonio Jose Rodrigues Neto and Michael Smith (both from NetApp) for their input and quick responses. Thanks again, Geoff Geoff Hardin wrote: > I am new to the SAN environment, and most especially to the iSCSI > way of doing things. I have the iSCSI protocol enabled on my filer, > and I have the Microsoft iSCSI initiator downloaded and installed on > my PC. From the filer, I have created a couple LUNs on my filer, I > have created igroups, mapped the LUNs to the igroups, set the > create_ucode option to on, and started the iSCSI service. On the > Windows system, I have added the target portal, logged on, and I can > see an active session. I think I have all the basics under control. > What I can't seem to figure out is how the LUNs now show up as > being somehow connected to my Windows computer. I'm sure I've missed > something, but I can't figure out what. I've tried reading the "ONTAP > SysAdmin Block Access Management Guide" and working through the > examples step by step, still to no avail. > Some details: > > Host (initiator): Windows 2000 > ONTAP version 6.4.3 > toaster> iscsi show adapter > Adapter: iswta > Slot: N/A > Description: NetApp Software Implementation > Status: Online > Target Portal Groups: > portal group 1: inet 192.168.1.3 port 3260 > > toaster> igroup show > windows-igroup0 (iSCSI) (ostype: windows): > iqn.1992-08.com.netapp:sn.123456789 > > toaster> lun show -v > /vol/vol0/iscsi/lun0 10.0g (10742215680) (r/w, online, > mapped) > Comment: "iSCSI test lun0" > Serial#: HPlwFYo6bJoZ > Share: none > Space Reservation: enabled > Multiprotocol Type: windows > Maps: windows-igroup0=0 > /vol/vol0/iscsi/lun1 10.0g (10742215680) (r/w, online, > mapped) > Comment: "iSCSI test lun1" > Serial#: HPlwFYo6bQDV > Share: none > Space Reservation: enabled > Multiprotocol Type: windows > Maps: windows-igroup0=1 > > toaster> iswt interface show > Interface e0 enabled > > toaster> iscsi nodename > iSCSI target nodename: iqn.1992-08.com.netapp:sn.123456789 > > > > Any help would be greatly appreciated. > > Thanks, > > Geoff Hardin > geoff.hardin(a)dalsemi.com

1 0

iSCSI HOWTO question
by Geoff Hardin 08 Jan '04

08 Jan '04

I am new to the SAN environment, and most especially to the iSCSI way of doing things. I have the iSCSI protocol enabled on my filer, and I have the Microsoft iSCSI initiator downloaded and installed on my PC. From the filer, I have created a couple LUNs on my filer, I have created igroups, mapped the LUNs to the igroups, set the create_ucode option to on, and started the iSCSI service. On the Windows system, I have added the target portal, logged on, and I can see an active session. I think I have all the basics under control. What I can't seem to figure out is how the LUNs now show up as being somehow connected to my Windows computer. I'm sure I've missed something, but I can't figure out what. I've tried reading the "ONTAP SysAdmin Block Access Management Guide" and working through the examples step by step, still to no avail. Some details: Host (initiator): Windows 2000 ONTAP version 6.4.3 toaster> iscsi show adapter Adapter: iswta Slot: N/A Description: NetApp Software Implementation Status: Online Target Portal Groups: portal group 1: inet 192.168.1.3 port 3260 toaster> igroup show windows-igroup0 (iSCSI) (ostype: windows): iqn.1992-08.com.netapp:sn.123456789 toaster> lun show -v /vol/vol0/iscsi/lun0 10.0g (10742215680) (r/w, online, mapped) Comment: "iSCSI test lun0" Serial#: HPlwFYo6bJoZ Share: none Space Reservation: enabled Multiprotocol Type: windows Maps: windows-igroup0=0 /vol/vol0/iscsi/lun1 10.0g (10742215680) (r/w, online, mapped) Comment: "iSCSI test lun1" Serial#: HPlwFYo6bQDV Share: none Space Reservation: enabled Multiprotocol Type: windows Maps: windows-igroup0=1 toaster> iswt interface show Interface e0 enabled toaster> iscsi nodename iSCSI target nodename: iqn.1992-08.com.netapp:sn.123456789 Any help would be greatly appreciated. Thanks, Geoff Hardin geoff.hardin(a)dalsemi.com

1 1

RE: exports
by markallen＠micron.com 08 Jan '04

08 Jan '04

Tom, Does this apply to sharing out to netgroups and IP ranges as well? -Mark -----Original Message----- From: owner-toasters(a)mathworks.com [mailto:owner-toasters@mathworks.com] On Behalf Of Haynes, Tom Sent: Tuesday, January 06, 2004 9:48 AM To: Jerry Cc: toasters(a)mathworks.com Subject: Re: exports What happens if someone reuses the host name after a month? Say you have an export: /vol/payroll -access=george:harry:arnold:fred,rw=harry:arnold:george,root=arnold:geor ge And you retire arnold. You never change the export or there is a new admin who doesn't know to look at the export lists. Several times since the old arnold was retired, "exportfs -a" was run. Warning messages were printed to the console about no arnold being available. We don't let arnold have rw or root permissions, but due to the nature of -access, we have to leave the string "arnold" in that list, meaning that the client arnold would still have read/only access. Someone brings up a general purpose server on the network and being a huge fan of TV pigs, goes immediately for the available host name of arnold. The new arnold is immediatley able to get read permissions on /vol/payroll and several salaries get shared. A new volume gets created on the filer and someone reruns "exportfs -a". Now arnold is able to write as root to the payroll volume. In retrospect, a warning would have been nicer, wild security example aside, but at the time we were trying to patch the exports code and not redesign it to a new specification. We redesigned the exports code in 6.5 and as we no longer preload host IPs for -rw= and -root=, we do not detect that a host is no longer being resolved to IP. As a result, we do not throw away the entire export rule. The flip side is that arnold can still run amuck through your payroll, so check your export lists when you retire a secure server name. ;> > Has anyone seen where exporting a filesystem after a > reboot fails because exports has the name of a host > that no longer exists? > > My co-worker had this problem and support said this is > by design. This proved to be problematic for us when > we had a filer reboot and it failed to export some > filesystems because some host had been removed a long > time ago. Considering the reliability of the filer, > it's reasonable that some hosts in the export list > might disappear, I'd rather see this as a warning than > something that breaks the filer's ability to serve > volumes. After all, nothing a client does should > break a server, general rule. > > Jerry > > __________________________________ > Do you Yahoo!? > Yahoo! Hotjobs: Enter the "Signing Bonus" Sweepstakes > http://hotjobs.sweepstakes.yahoo.com/signingbonus > -- Tom Haynes, ex-cfb thomas(a)netapp.com

2 1

MUTUAL INVESTMENT
by Justice Mugato 07 Jan '04

07 Jan '04

Dear, I am Justice El' Mugato, a formal top government officer in ministry of Agriculture. I am 55 years of age, married with one wife and two children. I have served my beloved country Algeria for more than thirteen good years now. Sir, your cooperation and advise is of great importance to me and I will like to invest my money in any lucrative or money yielding venture in your country of which you will be part of this investment proposal as an active partner following your professional advise toward the pursuit of this investment. I would personally like you to look into, real estate and property. Please sir, I need to be educated professionally due to my low knowledge for any investment out side my country Algeria. I will likethis proposal to be treated with absolute trust and honesty. Kindly furnish and equip me with details about one. I am looking forward hearing from you with good news. Thanks for your anticipated cooperation and you can contact me with the above email address or my alternative email address : mugatojustice(a)netexecutive.com Best Regards. Justice El'Mugato -- Sent by Pinoymail, http://www.pinoymail.com/

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