eth1 not showing up 3

[skiflyer]

I have a HP ProLiant DL360 which I just installed Debian Sarge on... had a bit of a bear getting things going... but it looks pretty stable now.

However, when I type ifconfig, I see only one of my two network cards.

If I boot up Knoppix, it loads up both, and during install it asked me which I wanted to use as the primary network controller... so I know it's capable of seeing both... is there something I need to modify to get both up and running full time?

 

[thedaver]

what do you see under
"ifconfig -a" ???

does it appear there? if so, then you have not enabled it as an active interface.

Hosting Solutions for Home or Business.

http://www.surfinbox.com/hosting/

 

[skiflyer]

It shows up there...

eth0      Link encap:Ethernet  HWaddr 00:12:79:3C:86:1E
          inet addr:172.17.17.64  Bcast:172.17.19.255  Mask:255.255.252.0
          inet6 addr: fe80::212:79ff:fe3c:861e/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:246363 errors:0 dropped:0 overruns:0 frame:0
          TX packets:126488 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:233187005 (222.3 MiB)  TX bytes:11887677 (11.3 MiB)
          Interrupt:209

eth1      Link encap:Ethernet  HWaddr 00:12:79:3C:86:1D
          BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)
          Interrupt:217

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:8 errors:0 dropped:0 overruns:0 frame:0
          TX packets:8 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:560 (560.0 b)  TX bytes:560 (560.0 b)

sit0      Link encap:IPv6-in-IPv4
          NOARP  MTU:1480  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)

Does that mean I'm ok? It doesn't appear that it's being used at all though.

 

[ericbrunson]

That's correct. The default behavior of ifconfig is to only show running interfaces. What do you expect it to be doing?

 

[skiflyer]

I want it to be able to take over if the cable coming into eth0 were to break... or eventually, I may be hooking it up via crossover to another server, and I'd like it to use that path when transferring files between the two machines.

 

[ericbrunson]

Though the first may seem simple, it is actually quite a bit more complicated than you would think. The best way to do it is to run a routing protocol on the server and have it advertise a route to a loopback address via both of the interfaces to your upstream router.

If any of that doesn't make immediate sense to you, or you don't know how to configue OSPF or similar on your router, then it would take a lotta 'splaining, Lucy.

The second is easy, you'd simple config the two servers connected via crossover on a separate network than the rest of the lan. Whenever you would refer to the other server via that interface's IP address (or name bound to that address) it will use the dedicated crossover connection.

If I were you, I wouldn't bother with the first. Unless you have two hub/switches and two routers for the redundant connections, the probability that your switch or router dies is exponentially more likely than your cable spontaneously failing.

 

[skiflyer]

I do have the two switches for redundant connections... but it sounds like for the time being it'd be faster for me to walk over and swap the cable than to worry about that.

 

[Castor66]

You want to do channel bonding. It's the same as teaming under Windows. I have a couple of servers that I set it up on. It's not too dificult but some bits are annoying. The most important thing is ensuring all the names are right and the case-sensitivity is okay. Here's the HP link:

http://docs.hp.com/en/B9903-90005/ch05s04.html

I have 4 interfaces configured in two pairs for Front-end and back-end communication. For us it works fine although I have seen some issues with failing back once the old link comes back up again.

 

[ericbrunson]

Castor,

That's a very interesting article, that's for posting it.

e.