11-06-2008
Quote:
Originally Posted by
DukeNuke2
this is no problem. the pci bus is scanned before the internel nics are scanned. so they will become net0 and so on. if you like to have the internal nics to be net0... you have to pull out the additional cards, install the system and then insert the cards again.
Thank you vimes for the info.
![Big Grin Smilie](https://www.unix.com/images/smilies/biggrin.gif)
DukeNuke, our practise is to integrate the h/w first then we install the OS. Other systems did not have such issue, only this. But seeing your explanation, it does make sense to follow such procedure.. But for this server, we lack time to do re-installation now..
Thx alot guys!
![Smilie Smilie](https://www.unix.com/images/smilies/smile.gif)
9 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hi,
what are the basic steps/command to configure a new nic (2nd) on Solaris 9? :eek:
10x N. (4 Replies)
Discussion started by: nadav
4 Replies
2. SCO
Hi guys,
I am a newbie in SCO UNIX, and I am having problem in installing a NIC for my machine:
My machine: UnixWare scou 5 7.1.4 i386 x86at SCO UNIX_SVR5
My NIC is dLink DFE-538TX, I got the driver from:
http://support.dlink.ca/ProductView.asp?ProductModel=DFE-538TX
The driver... (1 Reply)
Discussion started by: Voldi
1 Replies
3. Shell Programming and Scripting
how can I know the Network Interface Card physical address? (4 Replies)
Discussion started by: nokia1100
4 Replies
4. HP-UX
how can I determine which NIC card is virtual NIC Card
which condition can make a decision
Does HP UX have Virtual Network Adapter Concept
if ,it has
where I can Find if I Install Virutal Network Adapter
or which command that i can get it
or which software can generate
thanks (2 Replies)
Discussion started by: alert0919
2 Replies
5. Solaris
I couldn't install my nic in solaris 10. I compiled and added
the driver but failed to attach the driver and ifconfig output
shows only loopback dev. Please see the following output and tell
me whether my nic has been detected and why the driver failed to
attach?
My nic is detected in linux... (0 Replies)
Discussion started by: vectrum
0 Replies
6. IP Networking
I am new in squid proxy.
My question is how to (and if it's necessary) to set one NIC for inbound traffic (http requests) and one NIC for outbound traffic (http answers)?
Thank you in advance! (4 Replies)
Discussion started by: aixlover
4 Replies
7. Red Hat
Dear All
I want tune my NIC's rps, rfs and xps value.
In my system I have two NIC (eth0, eth1) and I have a bond0 ( eth0, eth1).
Here is the question? Which device should I modify ?
eth0 and eth1? or just modify bond0 or modify all device (eth0, eth1, bond0)
Any advice is welcome.... (0 Replies)
Discussion started by: nnnnnnine
0 Replies
8. HP-UX
Hello,
I need to configure a second NIC on my HP UX, B.11.31 U ia64 ...if it is helpful.
I see a good thread to start on:
Configuring NIC
https://www.unix.com/hp-ux/15589-configuring-nic.html
I have started reading the man pages listed. Without having to know every last detail is there... (3 Replies)
Discussion started by: KmJohnson
3 Replies
9. Linux
Hello Admins,
My ask is how can I add two different subnet IPs to same box with two different gateways?
The issue is I can connect to the box when I am on ethernet LAN, but I am not able to connect to the same IP when I am on wifi. The server is RHEL 7 VM on vmware.
How can I get connected... (4 Replies)
Discussion started by: snchaudhari2
4 Replies
LEARN ABOUT REDHAT
axnet_cs
AXNET_CS(4) Kernel Interfaces Manual AXNET_CS(4)
NAME
axnet_cs - Asix AX88190 chipset PCMCIA Ethernet Driver
SYNOPSIS
insmod axnet_cs.o [pc_debug=n] [irq_list=i,j,...]
DESCRIPTION
Axnet_cs is a driver for PCMCIA ethernet cards based on the Asix AX88190 chipset. These cards are mostly NE2000 compatible but have sev-
eral bugs that are sufficiently tricky to work around that a separate driver was deemed necessary. When this driver is bound to a card, it
allocates the next available ethernet device (eth0..eth#). This device name will be reported in the kernel log file, and passed on to
cardmgr(8).
PARAMETERS
pc_debug=n
Selects the PCMCIA debugging level. This parameter is only available if the module is compiled with debugging enabled. A non-zero
value enables debugging.
irq_list=i,j,...
Specifies the set of interrupts that may be allocated by this driver.
DIAGNOSTICS
axnet_cs: this is not an AX88190 card!
Indicates that this card is probably a normal NE2000 compatible card, which requires the pcnet_cs driver.
eth#: interrupt(s) dropped!
Indicates that the driver did not receive an interrupt notification for some reason. The driver will poll the card (with a signifi-
cant performance penalty) if the problem persists. The most likely cause is an interrupt conflict and/or host bridge configuration
problem.
AUTHOR
David Hinds - dahinds@users.sourceforge.net
SEE ALSO
cardmgr(8), pcmcia(5).
pcmcia-cs 2001/08/17 12:51:58 AXNET_CS(4)