Jump to content

Recommended Posts

Posted
It's probably hugely obvious to almost everyone else but why has our new server got two network ports. Apologies in advance to all those who see this as a stupid question:mullet:
Posted

if you think of a server as a room and each network port as a door then imagine that 100s or 1000s of people want to get in and out. More doors = faster people can get in and out.

 

Can also be used for port teaming as domino suggested (although i'm not sure it has to be supported by switches depending on manufacturer of the nic), or if you use MS network load balancing you can have several servers listening on one IP which is assigned to one port on each server, they then use the other nic to communicate with each other and the network.

  • Thanks 1
Posted
It's probably hugely obvious to almost everyone else but why has our new server got two network ports. Apologies in advance to all those who see this as a stupid question:mullet:

 

I didn't know, and now I have learnt something. Thanks for asking!

  • Thanks 1
Posted

There's no such thing as a stupid quesiton, only a stupid answer :)

 

I have our two file server NICs teamed, I assumed that that gives us doubel the bandwidth, but I've never looked into it!

 

Again, thanks for asking the question, I'm sure plenty others have learnt something to!

  • Thanks 1
Posted
Not much use if its a windows server, but I found this article an interesting read

 

Why? As others have said, you can use it for teaming, clustering, load balancing.

 

You can use it when you just want the machine to be on 2 networks - eg a proxy server or other firewall type device.

 

Ultimately, I suspect most server motherboards (and many desktop boards) come with 2 network connections because it's very cheap to do it and it can be useful to have it.

  • Thanks 1
Posted

i think there's confusion there, sroachford obviously thought you meant

 

"two network ports aren't much good for windows servers"

 

when you meant

"this article is about linux.."

 

:)

Posted
Back in the good old days (!) it was common to use servers as routers. Our Netware servers had about 4 network cards - on 10-Base-2 with BNC connectors. One NIC handled the incoming network uplink, and the others had long chains of PCs hanging off them.
  • Thanks 1
Posted
i think there's confusion there, sroachford obviously thought you meant

 

"two network ports aren't much good for windows servers"

 

when you meant

"this article is about linux.."

 

:)

 

I thought the same. It did sound like you were saying that dual ports weren't much use in windows RabbieBurns, rather than that the article isnt much use for his current situation. lol

Posted
Back in the good old days (!) it was common to use servers as routers.:

 

Lordy, brings back memories of building servers with two token ring cards in - and sometimes different servers for different protocol types !! One for IP and another for NetBUI - those were the days.....

Posted
If you team the two ports and plug each port into a different switch it will give you abit of redundancy incase one switch dies, you another to fall back on.
  • Thanks 1
Posted

Our storage server is a bit overkill, we have 4 HP network cards teamed in it, until recently it was just 2. It does have storage for all our users doucments, and all the shared areas on it, so the extra bandwidth can't do it any harm.

 

The HP network teaming tool is very good, most manufacturers also to their own variations so it's worth looking for them if they exist for your network cards, rather than using the built in Windows options in my opinion.

 

Mike.

  • Thanks 1
Posted
Just check that they are both network cards. Some servers (most of our HPs) have an additional managment port that connects to a web server built into the motherboard, lets you do hard reboots etc. remotely.
Posted
On our server, we have 1 network port for external (Internet) traffic and the other for internal (network) traffic.
  • Thanks 1
Posted
Just check that they are both network cards. Some servers (most of our HPs) have an additional managment port that connects to a web server built into the motherboard, lets you do hard reboots etc. remotely.

 

Goold old ILO on the HP servers has saved me a fair few times when I've accidently gone to shutdown insted of restart when working on a server remotely. I just wish you didn't have to purchase a licence to get the full functionality :( Still just the ability to operate the power button remotely is a real bonus!

 

Mike.

  • Thanks 1
Posted
i think there's confusion there, srochford obviously thought you meant

 

"two network ports aren't much good for windows servers"

 

when you meant

"this article is about linux.."

 

:)

 

Indeed - that'll teach me to read things too quickly :-)

  • Thanks 1
Posted
Goold old ILO on the HP servers has saved me a fair few times when I've accidently gone to shutdown insted of restart when working on a server remotely. I just wish you didn't have to purchase a licence to get the full functionality :( Still just the ability to operate the power button remotely is a real bonus!

 

Mike.

 

yeah, i only discovered that the other day...iLO advanced for proliant servers.

IBM make a point about users not having to license for advanced LOM features, but then you have to order a RSA II slimline card to get a fully featured LOM experience on some ibm servers, so IBM charge for it in hardware and HP charge for it in feature activation - not much difference really. The only ones that don't add an iLO 'tax' for full functionality are Sun, and those who've used the iLO on Sun X4x00's say it's the best LOM implementation out of all the vendors. I've only used DRAC so i can't comment.

 

Normally the BMC/iLO port is clearly defined, on Dell servers it's a little spanner icon if you've order the option the DRAC option, suns standar ELO port on it's X2x00's just says 'net mgmt'

 

out of interest what feature(s) did you require of the iLO advanced that weren't available with the standard iLO on the proliant ? Surely the standard iLO let's you do basic stuff like remote power on.

  • Thanks 1
Posted

On a linux machine, specifically Squid Proxy.

 

 

Two is ideal, one for inbound/outbound traffic from lan, and the other for inbound/outbound traffic from the Internet.

 

 

So the internet is theoretically never connected to the lan. The middle man and IPtables tell it what to-do with certain traffic. Good for a easy "load balance"

Posted

out of interest what feature(s) did you require of the iLO advanced that weren't available with the standard iLO on the proliant ? Surely the standard iLO let's you do basic stuff like remote power on.

 

 

I don't really need the extra functionality, the only bit I really use is the powerbutton control, but the full console control of the machine from within iLO would be handy. However terminal services will suffice for my needs as it's not worth the extra expence for the number of times it is likely to be used.

 

Mike.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...