Re: [Samba] Samba and Multiple NICs
On Mon, 2004-04-05 at 06:06, [EMAIL PROTECTED] wrote: Clint, Thanks for your reply. What I want to do is straightforward in concept (perhaps difficult in practice, though I doubt it). I want to put two Gigabit Ethernet Cards in one Linux server -- and have each card talk to half the Windows workstations in my place. In part, I'm looking for a way to get more data in and out of my server (the storage part can support it). Each workstation is running a video editing application and it's looking for about 4 to 4.5 MB/sec of data. The data is time critical. It HAS to arrive when needed, or the editing application stops. So far I'm doing okay with just one network segment, but I think I can add a few additional workstations if I split the network -- because my storage subsystem is capable of doing well over 100 MB/sec -- and that's a lot more than I'm going to push down one Gigabit Ethernet pipe. In part, I want to configure the two Ethernet cards differently so that one can talk to workstations that are optimized for Gigabit Ethernet and Jumbo Frames and the other can talk to workstations that only have normal Ethernet capabilities. I'm NOT looking to get more data to a single workstation. I'm looking to get the maximum number of workstations that can all receive the 4 to 4.5 MB/sec that they need. By the way, my Server hardware is: 3.06 Ghz single processor Xeon, 1 GB RAM, Intel Gigabit nics, fast RAID arrays, two switches capable of supporting Jumbo Frames. Andy Andy, This describes your network a bit better. I think Samba probably handles a multi-homed domain master browser much better than Windows, as a quick search has not revealed problems with joining browse lists from multiple subnets on a domain controller (this is a major problem with Windows 2000, one I fought for quite some time and ended up having to purchase additional hardware to solve, by moving the domain controller to a dedicated single homed box). This is good, as it shouldn't break network browsing on a subnetted network with a multi-homed domain controller (I'm assuming, maybe incorrectly, that Samba is your DC) like Windows does. Firstly, the machine will exist twice in WINS. As long as there are no routers between your clients (and you're indicating they're not, based on your support for GigE and jumbo frames) you should be fine, seeing as WINS client resolution will choose a name returned from a multi-homed WINS entry on it's local subnet over another not in it's subnet, where as a multi-homed machine not on the subnet chooses an IP at random, see http://www.pmg.com/tip_archive/01_11.htm). However, you might want to give consideration to any clients which might be accessing this from beyond the router (although it appears from your description of your setup that you have one LAN connected to the Internet, so it seems pretty simple) However, secondly, I think you need to give consideration to how you're going to implement Internet routing and routing between the different subnets/VLANs as well as DHCP. The easiest way to set this up is to setup separate VLANs for the jumbo and non-jumbo frames and trunk between your switches, this way switching a connection from jumbo to standard framing is just a matter of changing the VLAN you're on. However, if your Samba server is not also your DHCP server, and your DHCP is also not multi-homed, you'll need to implement a dhcp relay, probably at the router level. Also, you'll want to make sure your router supports trunking 802.1q VLANs (or whatever proprietary VLANs your switch might support) or has multiple Ethernet interfaces. Keep in mind all traffic not destined for the Samba server will flow through this Router, and it will become a bottleneck for you. If you have little traffic going machine to machine, I think this would probably be a good solution for you, but I'd seriously consider the amount of machine to machine traffic you have that will cross subnets, as while you may gain increased performance from your fileserver, you may kill network performance for other peer to peer file copies etc. Something to seriously consider, but I think Samba should accommodate your situation quite well (better than Windows probably!). Clint -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Samba and Multiple NICs
In a message dated 4/4/2004 11:13:44 PM Eastern Daylight Time, [EMAIL PROTECTED] writes: Andy, I'd have to say you've got yourself a bit of a conundrum. Basically at this point, if you want to double the capacity your server can output, I would recommend segmenting your network into two VLANs (or separate switches if your switches aren't capable of doing VLANs, although any switch worth it's snuff is). However, before I go into more detail about how to actually accomplish that, what kind of hardware is this running on? I'd be seriously concerned that you'd be wasting a lot of time and effort if your hardware isn't capable of capping two GigE cards. I'd attach one machine with a GigE interface via a crossover cable to the second GigE interface on your Samba server and leave the other interface connected to the switch you have now. I'd then try to cap the interface from the side connected to the switch and from the side connected to another computer via the crossover and see if you can actually exceed greater than the speed one GigE is going to give you (or at least what you were getting previously). Also, some details on your hardware would be helpful. Clint Clint, Thanks for your reply. What I want to do is straightforward in concept (perhaps difficult in practice, though I doubt it). I want to put two Gigabit Ethernet Cards in one Linux server -- and have each card talk to half the Windows workstations in my place. In part, I'm looking for a way to get more data in and out of my server (the storage part can support it). Each workstation is running a video editing application and it's looking for about 4 to 4.5 MB/sec of data. The data is time critical. It HAS to arrive when needed, or the editing application stops. So far I'm doing okay with just one network segment, but I think I can add a few additional workstations if I split the network -- because my storage subsystem is capable of doing well over 100 MB/sec -- and that's a lot more than I'm going to push down one Gigabit Ethernet pipe. In part, I want to configure the two Ethernet cards differently so that one can talk to workstations that are optimized for Gigabit Ethernet and Jumbo Frames and the other can talk to workstations that only have normal Ethernet capabilities. I'm NOT looking to get more data to a single workstation. I'm looking to get the maximum number of workstations that can all receive the 4 to 4.5 MB/sec that they need. By the way, my Server hardware is: 3.06 Ghz single processor Xeon, 1 GB RAM, Intel Gigabit nics, fast RAID arrays, two switches capable of supporting Jumbo Frames. Andy -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Samba and Multiple NICs
Hello AndyLiebman, Monday, April 5, 2004, 5:23:43 AM, you wrote: Aac Hi, Aac I'm a happy Samba user. I've been working sucessfully in Linux for the past 6 Aac months. I've built a Linux Server with very fast storage and I'm connecting Aac it to many Windows XP video editing workstations via Gigabit Ethernet (all Aac NICs using Jumbo Frames, by the way). Aac Now I want to see if I can increase my data flow in and out of the Server so Aac that more workstations to connect to it simultaneously. I'm pretty much maxing Aac out on the amount of data that can flow through a single Gigabit Ethernet Aac connection (from the Server to a single Gigabit Switch). So I'm wondering what's Aac involved in adding a second NIC to my Server and dividing my workstations into Aac two groups. Aac Is this a difficult thing to configure? Would somebody be willing to tell me Aac what are the crucial settings that need to be made (in smb.conf, for example, Aac or in /etc/*.* stuff). Do I have to create subnets? Aac I'm currently working on an internal network where all the workstations have Aac 192.168.1.XXX static addresses. These workstations occasionally connect to the Aac Internet through a Cable/DSL router that's also on the network and that Aac serves as the gateway. Aac Is it possible to give my server two fixed IP addresses (one corresponding to Aac each NIC) and then connect each NIC to its own switch, which would then be Aac connected to half of the workstations? I tried this today and had no luck. Aac And how can I make it possible for each workstations to have access to the Aac Internet. Presumably, only one switch can be connected to the cable/dsl router Aac -- or else data traffic could go through the cable/dsl router to get from a Aac workstation to the Server. But I suppose that's the least of my worries. Aac I'm not looking for somebody else to do my homework. I've spent about 6 hours Aac today googling around trying to figure out what's required and I'm coming up Aac more confused with each article or discussion thread I read. Aac I would sure appreciate it if somebody out there was willing to lend a hand. Aac I'm sure this is basic stuff to an IT guy, but I'm just working on this Aac networking stuff at a hobby level -- doing pretty well, but now a bit stumped. Aac By the way, does anybody know if this scenario is covered in the new Samba Aac cookbook? I'd be happy to purchase it tomorrow if I thought it would give me the Aac recipe to do what I'm trying to accomplish. Can't explain my solution in detail but i will try to give you right direction. First of all take a look at the Advanced linux routing howto. We did things similiar to your request but with two FastEthernet interfaces. First of all we just install two interface cards and give to it ips within the same network. 10.10.10.40 and 10.10.10.41 for example (both mask 255.0.0.0). Next we setup a routing like that: # Deleting ordinary routes ip route del 10.0.0.0/8 dev eth0 ip route del 10.0.0.0/8 dev eth1 # Adding multipath route ip route add 10.0.0.0/8 scope global nexthop via 10.10.10.40 dev eth0 weight 1 nexthop via 10.10.10.41 dev eth1 weight 1 ip route flush cache After that got something like connection balancing for OUTGOING traffic over two our interfaces. It's just keeps balance of clients over interfaces, but not the clients bandwidth. But it's better than nothing. The more clients you have, the better balance you will reach. -- Best regards, Alexandermailto:[EMAIL PROTECTED] -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Samba and Multiple NICs
On Mon, 2004-04-05 at 09:24, Alexander Sbitnev wrote: Hello AndyLiebman, Monday, April 5, 2004, 5:23:43 AM, you wrote: Aac Hi, Aac I'm a happy Samba user. I've been working sucessfully in Linux for the past 6 Aac months. I've built a Linux Server with very fast storage and I'm connecting Aac it to many Windows XP video editing workstations via Gigabit Ethernet (all Aac NICs using Jumbo Frames, by the way). Aac Now I want to see if I can increase my data flow in and out of the Server so Aac that more workstations to connect to it simultaneously. I'm pretty much maxing Aac out on the amount of data that can flow through a single Gigabit Ethernet Aac connection (from the Server to a single Gigabit Switch). So I'm wondering what's Aac involved in adding a second NIC to my Server and dividing my workstations into Aac two groups. snip Can't explain my solution in detail but i will try to give you right direction. First of all take a look at the Advanced linux routing howto. We did things similiar to your request but with two FastEthernet interfaces. First of all we just install two interface cards and give to it ips within the same network. 10.10.10.40 and 10.10.10.41 for example (both mask 255.0.0.0). Next we setup a routing like that snip If your NICs and your switch supports it, teaming is a more elegant and efficient approach and won't require you to reconfigure your network settings. In a teaming environment, the NIC drivers support bundling several individual NICs together so that they appear as one NIC to the operating system. This is much like a RAID controller teams several physical hard drives together to appear as one drive to the operating system. We do this a lot with name-brand file servers (Compaq, HP, etc.). Load balancing and other neat features are handled by the driver automatically, with nothing to configure manually in the operating system. On the switch end, you do need a managed switch so you can team multiple ports together as one port. Again, the switch will handle load balancing, routing, etc. Compaq provides drivers that support SuSE; the switch end obviously doesn't care what operating system you are running. But, there are several standards, and you want to make sure that your NICs and your switch support the same standard! (Most better-quality hardware support multiple standards, so this isn't a big deal except if you have low-end hardware.) I hope this is helpful; if your hardware supports this, it will be a lot less work to configure. Possibly the average throughputs will be higher too. Mark -- _ A Message From L. Mark Stone President Reliable Networks of Maine, LLC 477 Congress Street, 5th Floor Portland, ME 04107 Tel: (207) 772-5678 Web: http://www.rnome.com -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] Samba and Multiple NICs
Hi, I'm a happy Samba user. I've been working sucessfully in Linux for the past 6 months. I've built a Linux Server with very fast storage and I'm connecting it to many Windows XP video editing workstations via Gigabit Ethernet (all NICs using Jumbo Frames, by the way). Now I want to see if I can increase my data flow in and out of the Server so that more workstations to connect to it simultaneously. I'm pretty much maxing out on the amount of data that can flow through a single Gigabit Ethernet connection (from the Server to a single Gigabit Switch). So I'm wondering what's involved in adding a second NIC to my Server and dividing my workstations into two groups. Is this a difficult thing to configure? Would somebody be willing to tell me what are the crucial settings that need to be made (in smb.conf, for example, or in /etc/*.* stuff). Do I have to create subnets? I'm currently working on an internal network where all the workstations have 192.168.1.XXX static addresses. These workstations occasionally connect to the Internet through a Cable/DSL router that's also on the network and that serves as the gateway. Is it possible to give my server two fixed IP addresses (one corresponding to each NIC) and then connect each NIC to its own switch, which would then be connected to half of the workstations? I tried this today and had no luck. And how can I make it possible for each workstations to have access to the Internet. Presumably, only one switch can be connected to the cable/dsl router -- or else data traffic could go through the cable/dsl router to get from a workstation to the Server. But I suppose that's the least of my worries. I'm not looking for somebody else to do my homework. I've spent about 6 hours today googling around trying to figure out what's required and I'm coming up more confused with each article or discussion thread I read. I would sure appreciate it if somebody out there was willing to lend a hand. I'm sure this is basic stuff to an IT guy, but I'm just working on this networking stuff at a hobby level -- doing pretty well, but now a bit stumped. By the way, does anybody know if this scenario is covered in the new Samba cookbook? I'd be happy to purchase it tomorrow if I thought it would give me the recipe to do what I'm trying to accomplish. Regards, Andy Liebman -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Samba and Multiple NICs
On Sun, 2004-04-04 at 18:23, [EMAIL PROTECTED] wrote: Hi, I'm a happy Samba user. I've been working sucessfully in Linux for the past 6 months. I've built a Linux Server with very fast storage and I'm connecting it to many Windows XP video editing workstations via Gigabit Ethernet (all NICs using Jumbo Frames, by the way). Now I want to see if I can increase my data flow in and out of the Server so that more workstations to connect to it simultaneously. I'm pretty much maxing out on the amount of data that can flow through a single Gigabit Ethernet connection (from the Server to a single Gigabit Switch). So I'm wondering what's involved in adding a second NIC to my Server and dividing my workstations into two groups. Is this a difficult thing to configure? Would somebody be willing to tell me what are the crucial settings that need to be made (in smb.conf, for example, or in /etc/*.* stuff). Do I have to create subnets? I'm currently working on an internal network where all the workstations have 192.168.1.XXX static addresses. These workstations occasionally connect to the Internet through a Cable/DSL router that's also on the network and that serves as the gateway. Is it possible to give my server two fixed IP addresses (one corresponding to each NIC) and then connect each NIC to its own switch, which would then be connected to half of the workstations? I tried this today and had no luck. And how can I make it possible for each workstations to have access to the Internet. Presumably, only one switch can be connected to the cable/dsl router -- or else data traffic could go through the cable/dsl router to get from a workstation to the Server. But I suppose that's the least of my worries. I'm not looking for somebody else to do my homework. I've spent about 6 hours today googling around trying to figure out what's required and I'm coming up more confused with each article or discussion thread I read. I would sure appreciate it if somebody out there was willing to lend a hand. I'm sure this is basic stuff to an IT guy, but I'm just working on this networking stuff at a hobby level -- doing pretty well, but now a bit stumped. By the way, does anybody know if this scenario is covered in the new Samba cookbook? I'd be happy to purchase it tomorrow if I thought it would give me the recipe to do what I'm trying to accomplish. Regards, Andy Liebman Andy, I'd have to say you've got yourself a bit of a conundrum. Basically at this point, if you want to double the capacity your server can output, I would recommend segmenting your network into two VLANs (or separate switches if your switches aren't capable of doing VLANs, although any switch worth it's snuff is). However, before I go into more detail about how to actually accomplish that, what kind of hardware is this running on? I'd be seriously concerned that you'd be wasting a lot of time and effort if your hardware isn't capable of capping two GigE cards. I'd attach one machine with a GigE interface via a crossover cable to the second GigE interface on your Samba server and leave the other interface connected to the switch you have now. I'd then try to cap the interface from the side connected to the switch and from the side connected to another computer via the crossover and see if you can actually exceed greater than the speed one GigE is going to give you (or at least what you were getting previously). Also, some details on your hardware would be helpful. Clint -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
