Linux - Networking This forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game. |
Notices |
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
|
 |
08-04-2013, 02:18 PM
|
#1
|
Member
Registered: Apr 2005
Posts: 252
Rep:
|
What kind of network setup could this have been?
I have obtain two PowerEdge 2800 servers FREE. Nice right! They have a hardware setup that interests me and I am curious of why they may have them setup they way that they are. The servers are labeled Server 1 and Server 2 and they are identical in setup. Of course the hard drives were pulled but they were originally shipped with Windows 2003 Std. PowerEdge servers have 2 built on on 1gb NIC's. But they added two more Dual NIC cards on each server. Making them each have 6 NIC's. These servers came from an Alarm company. I am just curious to why they had them setup this way. Maybe they didn't have a switch? I didn't get to pull these servers myself. My brother does construction and they were left behind by the company when they were demoing the building and of course he knew I may want these and of course I did. I will make them Linux boxes. Does anyone have any idea's of what kind of setup they "might" have been used for? The reason I want to know is it might be something I have not used before and could be useful but I can not think of anything to why they would have so many ports. I assume one server was a backup domain controller I guess. But it seems like over kill of network ports.
|
|
|
08-04-2013, 03:11 PM
|
#2
|
LQ Newbie
Registered: Aug 2011
Location: Alaska
Distribution: CentOS, Debian PowerPC, OS X
Posts: 12
Rep: 
|
Can only guess
The only reason I can think of right off is to avoid the use of a switch. Thus avoiding any perceived latency issues, or configuration snaffoos? They might have thought avoiding a switch would tighten the security of their network with everything forced to static IP's and no way for an external intruder to tap into the network through an appliance? Think of direct connecting one of the NIC's to say, a SQL server and it's backup server. And another to a domain controller, etc. So one server to another server. Or maybe they had that many inbound lines from their ISP and they put each on it's own WAN connection?
This is all guess work
|
|
|
08-04-2013, 03:26 PM
|
#3
|
Senior Member
Registered: Jan 2012
Distribution: Slackware
Posts: 3,349
Rep: 
|
That many NICs would typically indicate the use of trunking/teaming.
The high number of NICs suggests more than one network segment, teaming nonwithstanding. They may have had a dedicated storage network for iSCSI or AoE. It could also be that the servers were running some sort of High Availability service, with some of the NICs being used for heartbeat signaling between the nodes.
Last edited by Ser Olmy; 08-04-2013 at 03:28 PM.
|
|
|
08-05-2013, 09:20 AM
|
#4
|
Member
Registered: Sep 2012
Distribution: RHEL5/6, CentOS5/6
Posts: 218
Rep:
|
2+2*2 NICs looks like they used to team or bond 2 NICs together for redundancy and connect the server to 3 different networks.
Why they had dedicated networks is hard to say without more background information, but it could possibly be a management network, a production network and a intranet. There are many companies out there building didicated networks for special uses to make sure one can't interfere with the other. Maybe they weren't even using TCP/IP on some of the networks but other protocols.
|
|
|
08-08-2013, 12:22 AM
|
#5
|
Member
Registered: Jul 2012
Location: München
Distribution: Debian, CentOS/RHEL
Posts: 587
Rep:
|
I'd go for teaming the interfaces, which is more likely the more common practice nowadays than connecting to dual WAN interfaces. Teaming+load balancing i guess??
|
|
|
All times are GMT -5. The time now is 06:21 PM.
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|