Installing another NIC on my Linux box

[Ian Derringer]

Greetings,
I am in the process of installing another NIC on my Itanium server running RHAS3.0 - Will the OS auto detect the new H/W or I have to do something else? I am a newbie to Linux world and I would like some help.

Thank you in advance.

Ian

[NiCK_76 · Accepted solution]

Hi Ian Derringer ,

1/ restart the kudzu service to auto detect new nic , command is " /etc/init.d/kudzu restart "
2/You will auto enter network configure window to assign ip address.
3/use command ifconfig to check new nic.

NiCK

[Steven E. Protter]

If the card is supported, the OS will autodetect and kudzu will pick it up.

Most 100 BaseT cards now are supported. Few 1000 BaseT cards other than Intel's are correctly configured for their top speed. Some are not detected at all.

Card choice is key to not having a big headache here.

SEP

[Ross Minkov]

Ian,

The kudzu utility maintains a DB of detected and configured hardware, found at /etc/sysconfig/hwconf. To install the new card you need to shutdown the system. Once done with the installation you will boot it back up. As part of the boot process, kudzu compares the currently detected hardware to the stored DB. If new hardware is detected, or previousely existing hardware is removed, kudzu will attempt to automatically reconfigure the system, or steer the administrator to the appropriate interactive configuration utility.

Regards,
Ross

[rick jones]

Likely as not, if the add-on NIC was oen of those listed as an "accessory" for the Itanium server, the OS will deal with it just fine, even if it is not based on Intel chips. For example, the core 1000Base-T on HP Itegrity servers is based on a Broadcom chip, as the the HP-branded addon, single-port GbE, and it seems to do just fine.

[Ian Derringer]

Greetings,
Thanks for everyone that have replied so far. I successfully installed the 2nd NIC "A0761A" certified NIC for my Itanium server. The server magicly found the new NIC. I was able to configured the "eth2" NIC via RH gui interface. However, when I ran ifconfig at the command line, I see only the eth0 & eth1 but nothing for eth2. What else do I need to do at this point?? Anyone have any ideas??

Thank you in advance.

Ian

[Ross Minkov]

try /sbib/ifconfig eth2 and post the output here.

[Dave Falloon]

You may have to bring the interface up:

run this to let you visually verify the settings for the nic:
ifconfig eth2

If all looks good run this:
ifup eth2

How many ethernet cards are in the machine?

if there are only two cards you should only see eth0 and eth1.

Unless they are multi port adapters then you would see an eth(n) for every port starting with 0.

--Dave

[Ian Derringer]

The problem has been solved. Now, I am off to work on why my HBA is not talking to my SANs disks

Thanks everyone.

Ian

[Ross Minkov]

Ian,

How was the problem solved? How about some points for the folks that tried to help?

Regards,
Ross

[Ian Derringer]

Ross,
I start up my KDE xwindows and add a new NIC under the network tab and configured the NIC. I did not add a new alias for the second NIC "eth2" at this point. If I do ifconfig, the 2nd NIC does not show up, but if I do ifconfig eth2 this will show up just fine.

[Ross Minkov]

Ian,

Here is how ifconfig works:

If no arguments are given, ifconfig displays the status of the currently active interfaces.

If a single interface argument is given, it displays the status of the given interface only.

If a single -a argument is given, it displays the status of all interfaces, even those that are down.

HTH,
Ross