Mailing List Archive: Netapp: toasters

dedicating a network interface to a vfiler

Index | Next | Previous | View Threaded

dl888 at cox

Dec 2, 2008, 12:22 PM

Post #1 of 6 (3217 views)
Permalink

dedicating a network interface to a vfiler

Just got asked about the best practice regarding dedicating a network interface to a vfiler to increase performance. I searched through NOW site and read some of the documentation and saw that ipspace should do the trick? Is it the best way? So i'd create an ipspace, assign interface to it, ifconfig the interface, then create a vfiler in that ipspace? Is there a way to move a vfiler to a different ipspace later? I didn't see that in the documentation.

Thanks,

Derek
Intuit Software

Adam.Fox at netapp

Dec 2, 2008, 3:51 PM

Post #2 of 6 (3130 views)
Permalink

RE: dedicating a network interface to a vfiler [In reply to]

I don't think you need to go as far as an ipspace to do this. Just only have 1 IP on the interface then assign that IP to the vfiler in question. That should do the trick. To me, the main reason to use different ipspace's is when you multiple private networks (like two 10.x.x.x networks) and you need to differentiate between them.

-- Adam Fox
adamfox [at] netapp

-----Original Message-----
From: dl888 [at] cox [mailto:dl888 [at] cox]
Sent: Tuesday, December 02, 2008 3:22 PM
To: toasters [at] mathworks
Subject: dedicating a network interface to a vfiler

Just got asked about the best practice regarding dedicating a network interface to a vfiler to increase performance. I searched through NOW site and read some of the documentation and saw that ipspace should do the trick? Is it the best way? So i'd create an ipspace, assign interface to it, ifconfig the interface, then create a vfiler in that ipspace? Is there a way to move a vfiler to a different ipspace later? I didn't see that in the documentation.

Thanks,

Derek
Intuit Software

dl888 at cox

Dec 2, 2008, 4:27 PM

Post #3 of 6 (3123 views)
Permalink

RE: dedicating a network interface to a vfiler [In reply to]

Adam,

Thanks! That is exactly the answer I was looking for. Please forward this email to your manager regarding the great job you are doing! We need more people like you from NetApp.

Can't say the same thing about quality of NetApp support. The quality seems to have gotten very un-even. I opened a case to try to get an answer and had to spend 20 minutes waiting only to have some inexperienced young guy ask me how I found the documentation. (I did keyword search on NOW) then they inaccurately tell me I should look under V series documentation (I realized afterwards the V-series are the IBM gateway filers?) and then proceed to try to read the manual pages (for the first time) back to me. When I got frustrated and explained that I am looking for best practice instead of someone re-reading the documentation for the first time and trying to interpret to me, he became quite rude! Anyway, NetApp has probably gotten quite big and I can understand some people needing more training but aren't getting it.

Anyway, thanks to you and keep up the good work!

Derek

---- "Fox wrote:
> I don't think you need to go as far as an ipspace to do this. Just only have 1 IP on the interface then assign that IP to the vfiler in question. That should do the trick. To me, the main reason to use different ipspace's is when you multiple private networks (like two 10.x.x.x networks) and you need to differentiate between them.
>
> -- Adam Fox
> adamfox [at] netapp
>
> -----Original Message-----
> From: dl888 [at] cox [mailto:dl888 [at] cox]
> Sent: Tuesday, December 02, 2008 3:22 PM
> To: toasters [at] mathworks
> Subject: dedicating a network interface to a vfiler
>
> Just got asked about the best practice regarding dedicating a network interface to a vfiler to increase performance. I searched through NOW site and read some of the documentation and saw that ipspace should do the trick? Is it the best way? So i'd create an ipspace, assign interface to it, ifconfig the interface, then create a vfiler in that ipspace? Is there a way to move a vfiler to a different ipspace later? I didn't see that in the documentation.
>
>
> Thanks,
>
> Derek
> Intuit Software
>
>

dl888 at cox

Dec 2, 2008, 5:03 PM

Post #4 of 6 (3120 views)
Permalink

RE: dedicating a network interface to a vfiler [In reply to]

Adam & Scott,

Thanks. You were both dead-on. ipspace will do it but it seem designed for a pretty specific purpose and comes with a lot of restrictions. Other storage admins have already setup this filer with 4 network interfaces for 3 vfilers (including vfiler0) so vfiler0 has 2 network interfaces (e0a and e0d, see below). e0d has to go through firewall that slows things down tremendously so now we want to move that interface from vfiler0 to vfiler ctie02 but it won't allow us to move it without downing the interface and removing the ip address. Then we have problem assigning an ip address to e0d once we ipspace assign it to ctie02. Also we have figured out how to do it through GUI but is there a good whitepaper or documentation on doing this, especially through the command line?

Cheers,

Derek

----------------------------------------------------------------------------
constantine-even> vfiler status
vfiler0 running
ctvcorp02 running
ctvie02 running
constantine-even> ipspace list
Number of ipspaces configured: 3
default-ipspace (e0a e0d)
ctie02 (e0b)
ctvcorp02 (e0c)
constantine-even> ifconfig -a
e0a: flags=948043<UP,BROADCAST,RUNNING,MULTICAST,TCPCKSUM> mtu 1500
inet xxx.xxx.xxx.xxx netmask 0xfffffe00 broadcast xxx.xxx.xxx.xxx
partner e0a (not in use)
ether 00:a0:98:03:8a:32 (100tx-fd-up) flowcontrol none
e0b: flags=4948043<UP,BROADCAST,RUNNING,MULTICAST,TCPCKSUM,NOWINS> mtu 1500
inet 10.21.1.27 netmask 0xffffff00 broadcast 10.21.1.255
partner e0b (not in use)
ether 00:a0:98:03:8a:33 (auto-1000t-fd-up) flowcontrol full
e0c: flags=948043<UP,BROADCAST,RUNNING,MULTICAST,TCPCKSUM> mtu 1500
inet xxx.xxx.xxx.xxx netmask 0xffff0000 broadcast xxx.xxx.xxx.xxx
partner e0c (not in use)
ether 00:a0:98:03:8a:30 (100tx-fd-up) flowcontrol full
e0d: flags=948043<UP,BROADCAST,RUNNING,MULTICAST,TCPCKSUM> mtu 1500
inet xxx.xxx.xxx.xxx netmask 0xffffff00 broadcast xxx.xxx.xxx.xxx
partner inet 10.9.2.61 (not in use)
ether 00:a0:98:03:8a:31 (auto-1000t-fd-up) flowcontrol full
lo: flags=1948049<UP,LOOPBACK,RUNNING,MULTICAST,TCPCKSUM> mtu 8160
inet 127.0.0.1 netmask 0xff000000 broadcast 127.0.0.1
ether 00:00:00:00:00:00 (VIA Provider)
constantine-even> sysconfig
NetApp Release 7.2.2: Sat Mar 24 20:38:59 PDT 2007
System ID: 0101174139 (constantine-even); partner ID: 0101176434 (constantine-odd)
System Serial Number: 3058646 (constantine-even)
System Rev: B0
slot 0: System Board
Processors: 4
Memory Size: 3072 MB
Remote LAN Module Status: Online
slot 0: Dual 10/100/1000 Ethernet Controller VI
e0a MAC Address: 00:a0:98:03:8a:32 (100tx-fd-up)
e0b MAC Address: 00:a0:98:03:8a:33 (auto-1000t-fd-up)
e0c MAC Address: 00:a0:98:03:8a:30 (100tx-fd-up)
e0d MAC Address: 00:a0:98:03:8a:31 (auto-1000t-fd-up)
slot 0: Fibre Channel Target Host Adapter 0a
slot 0: Fibre Channel Target Host Adapter 0b
slot 0: Fibre Channel Target Host Adapter 0c
slot 0: Fibre Channel Target Host Adapter 0d
slot 0: SCSI Host Adapter 0e
slot 0: NetApp ATA/IDE Adapter 0f (0x000001f0)
0f.0 245MB
slot 1: FC Host Adapter 1a
84 Disks: 11424.0GB
6 shelves with ESH2
slot 1: FC Host Adapter 1b
84 Disks: 11424.0GB
6 shelves with ESH2
slot 2: FC Host Adapter 2a
84 Disks: 17136.0GB
6 shelves with ESH2
slot 2: FC Host Adapter 2b
84 Disks: 17136.0GB
4 shelves with ESH2, 2 shelves with ESH4
slot 3: NVRAM
Memory Size: 512 MB
constantine-even>

---- "Fox wrote:
> I don't think you need to go as far as an ipspace to do this. Just only have 1 IP on the interface then assign that IP to the vfiler in question. That should do the trick. To me, the main reason to use different ipspace's is when you multiple private networks (like two 10.x.x.x networks) and you need to differentiate between them.
>
> -- Adam Fox
> adamfox [at] netapp
>
> -----Original Message-----
> From: dl888 [at] cox [mailto:dl888 [at] cox]
> Sent: Tuesday, December 02, 2008 3:22 PM
> To: toasters [at] mathworks
> Subject: dedicating a network interface to a vfiler
>
> Just got asked about the best practice regarding dedicating a network interface to a vfiler to increase performance. I searched through NOW site and read some of the documentation and saw that ipspace should do the trick? Is it the best way? So i'd create an ipspace, assign interface to it, ifconfig the interface, then create a vfiler in that ipspace? Is there a way to move a vfiler to a different ipspace later? I didn't see that in the documentation.
>
>
> Thanks,
>
> Derek
> Intuit Software
>
>

silkey at ece

Dec 3, 2008, 6:02 AM

Post #5 of 6 (3112 views)
Permalink

Re: dedicating a network interface to a vfiler [In reply to]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

dl888 [at] cox wrote:
> (I realized afterwards the V-series are
> the IBM gateway filers?)

Not exactly. V-Series filers allow you to set a vSeries head in-front
of non-Netapp disk (EMC, IBM, Hitachi, et al) and lay WAFL atop them and
get all sorts of OnTAP goodness. Thats what I recall from my time at my
prior employer. The VMWare guys had a heavy investment in EMC
infrastructure for enterprise shared storage, management found
additional disk costs palatable, but both wanted A-SIS goodness. Just
prior to my bouncing, they were going to demo a V-Series to do a dedupe PoC.

FYI. Cheers.

- --
Nick Silkey

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.8 (Darwin)

iEYEARECAAYFAkk2kZAACgkQrDQjhjXrMeK/PQCfb7JHumYVk30eTNPTLG7N6mjx
DoUAnixBQH5lMYfrmHfND2uzw8WWK+cD
=pYaV
-----END PGP SIGNATURE-----

Adam.Fox at netapp

Dec 3, 2008, 12:09 PM

Post #6 of 6 (3081 views)
Permalink

RE: dedicating a network interface to a vfiler [In reply to]

Derek:

You will need to down the interface, there's just no good way to do this otherwise. Once the interface is down and has no IP associated with it (just set the ip to 0.0.0.0 via ifconfig and that will do the trick), then you can use 'ipspace assign ctie02 e0d' to move it over, then reassign the address via ifconfig. Keep in mind that ifoconfig statements are not persistent so you'd need to set them up in /etc/rc if you want them to be so. The GUI will most likely do that for you.

Hope this helps.

-- Adam Fox
Systems Engineer
adamfox [at] netapp

-----Original Message-----
From: dl888 [at] cox [mailto:dl888 [at] cox]
Sent: Tuesday, December 02, 2008 8:04 PM
To: Fox, Adam; toasters [at] mathworks
Subject: RE: dedicating a network interface to a vfiler

Adam & Scott,

Thanks. You were both dead-on. ipspace will do it but it seem designed for a pretty specific purpose and comes with a lot of restrictions. Other storage admins have already setup this filer with 4 network interfaces for 3 vfilers (including vfiler0) so vfiler0 has 2 network interfaces (e0a and e0d, see below). e0d has to go through firewall that slows things down tremendously so now we want to move that interface from vfiler0 to vfiler ctie02 but it won't allow us to move it without downing the interface and removing the ip address. Then we have problem assigning an ip address to e0d once we ipspace assign it to ctie02. Also we have figured out how to do it through GUI but is there a good whitepaper or documentation on doing this, especially through the command line?

Cheers,

Derek

----------------------------------------------------------------------------
constantine-even> vfiler status
vfiler0 running
ctvcorp02 running
ctvie02 running
constantine-even> ipspace list
Number of ipspaces configured: 3
default-ipspace (e0a e0d)
ctie02 (e0b)
ctvcorp02 (e0c)
constantine-even> ifconfig -a
e0a: flags=948043<UP,BROADCAST,RUNNING,MULTICAST,TCPCKSUM> mtu 1500
inet xxx.xxx.xxx.xxx netmask 0xfffffe00 broadcast xxx.xxx.xxx.xxx
partner e0a (not in use)
ether 00:a0:98:03:8a:32 (100tx-fd-up) flowcontrol none
e0b: flags=4948043<UP,BROADCAST,RUNNING,MULTICAST,TCPCKSUM,NOWINS> mtu 1500
inet 10.21.1.27 netmask 0xffffff00 broadcast 10.21.1.255
partner e0b (not in use)
ether 00:a0:98:03:8a:33 (auto-1000t-fd-up) flowcontrol full
e0c: flags=948043<UP,BROADCAST,RUNNING,MULTICAST,TCPCKSUM> mtu 1500
inet xxx.xxx.xxx.xxx netmask 0xffff0000 broadcast xxx.xxx.xxx.xxx
partner e0c (not in use)
ether 00:a0:98:03:8a:30 (100tx-fd-up) flowcontrol full
e0d: flags=948043<UP,BROADCAST,RUNNING,MULTICAST,TCPCKSUM> mtu 1500
inet xxx.xxx.xxx.xxx netmask 0xffffff00 broadcast xxx.xxx.xxx.xxx
partner inet 10.9.2.61 (not in use)
ether 00:a0:98:03:8a:31 (auto-1000t-fd-up) flowcontrol full
lo: flags=1948049<UP,LOOPBACK,RUNNING,MULTICAST,TCPCKSUM> mtu 8160
inet 127.0.0.1 netmask 0xff000000 broadcast 127.0.0.1
ether 00:00:00:00:00:00 (VIA Provider)
constantine-even> sysconfig
NetApp Release 7.2.2: Sat Mar 24 20:38:59 PDT 2007
System ID: 0101174139 (constantine-even); partner ID: 0101176434 (constantine-odd)
System Serial Number: 3058646 (constantine-even)
System Rev: B0
slot 0: System Board
Processors: 4
Memory Size: 3072 MB
Remote LAN Module Status: Online
slot 0: Dual 10/100/1000 Ethernet Controller VI
e0a MAC Address: 00:a0:98:03:8a:32 (100tx-fd-up)
e0b MAC Address: 00:a0:98:03:8a:33 (auto-1000t-fd-up)
e0c MAC Address: 00:a0:98:03:8a:30 (100tx-fd-up)
e0d MAC Address: 00:a0:98:03:8a:31 (auto-1000t-fd-up)
slot 0: Fibre Channel Target Host Adapter 0a
slot 0: Fibre Channel Target Host Adapter 0b
slot 0: Fibre Channel Target Host Adapter 0c
slot 0: Fibre Channel Target Host Adapter 0d
slot 0: SCSI Host Adapter 0e
slot 0: NetApp ATA/IDE Adapter 0f (0x000001f0)
0f.0 245MB
slot 1: FC Host Adapter 1a
84 Disks: 11424.0GB
6 shelves with ESH2
slot 1: FC Host Adapter 1b
84 Disks: 11424.0GB
6 shelves with ESH2
slot 2: FC Host Adapter 2a
84 Disks: 17136.0GB
6 shelves with ESH2
slot 2: FC Host Adapter 2b
84 Disks: 17136.0GB
4 shelves with ESH2, 2 shelves with ESH4
slot 3: NVRAM
Memory Size: 512 MB
constantine-even>

---- "Fox wrote:
> I don't think you need to go as far as an ipspace to do this. Just only have 1 IP on the interface then assign that IP to the vfiler in question. That should do the trick. To me, the main reason to use different ipspace's is when you multiple private networks (like two 10.x.x.x networks) and you need to differentiate between them.
>
> -- Adam Fox
> adamfox [at] netapp
>
> -----Original Message-----
> From: dl888 [at] cox [mailto:dl888 [at] cox]
> Sent: Tuesday, December 02, 2008 3:22 PM
> To: toasters [at] mathworks
> Subject: dedicating a network interface to a vfiler
>
> Just got asked about the best practice regarding dedicating a network interface to a vfiler to increase performance. I searched through NOW site and read some of the documentation and saw that ipspace should do the trick? Is it the best way? So i'd create an ipspace, assign interface to it, ifconfig the interface, then create a vfiler in that ipspace? Is there a way to move a vfiler to a different ipspace later? I didn't see that in the documentation.
>
>
> Thanks,
>
> Derek
> Intuit Software
>
>

Index | Next | Previous | View Threaded

Interested in having your list archived? Contact Gossamer Threads