Login or Register to Ask a Question and Join Our Community


IP Networking

Network interfaces problem

Login to Discuss or Reply to this Discussion in Our Community

 
Thread Tools Search this Thread
Special Forums IP Networking Network interfaces problem
# 1  
Old 09-19-2007
Network interfaces problem
Hi,

I have problems with my SCO unix network interfaces.
Intel integrated adapter was failing, so I installed new one - 3COM adapter into free PCI slot.
Installed driver using SCO Software manager - successfully
Added new Network adapter using SCO Network configuration manager - successfully
after that I checked using ifconfig -a
there was some loopback interfaces and - net0 -intel interface, and net1 -3com interface.
So I thought that everything is OK and removed intel adapter using Network configuration manager, after that things went wrong:
ifconfig -a displays only loopback interfaces.
3com driver is installed, 3com network adapter is added(Network configuration manager), but ifconfig -a don't display it!!!

So I thought that it's hardware problem - booted knoppix from cd - my 3com adapter is autodetected, up and running!

After that I tried all 'dumb' ways - rebooted, reinstalled(driver), changed apapter pci slot...- result is the same -driver - OK, adapter(Network configuration manager) - OK, "ifconfig -a" - no entries. By the way devices net0 and net1 are present(I asume net1 is my 3com adapter).

I'm newbe in unix so maybe I missing some 'obvious' step ?
How to force my 3com adapter(net1 ?) to apear in ifconfig list, and force it function corectlly ?

thank you
Vilius
Login or Register to Ask a Question

Previous Thread | Next Thread

10 More Discussions You Might Find Interesting

1. IP Networking

Network Interfaces Problem - Monitoring equipment

Dear gurus of Linux / Unix. I have a server, which I use to monitoring traffic, the problem that I find is when I run the following command: probe:~ # sar -n DEV 1 I see that I one second appear info in some interface and in the other second no appear, I don't know what will be the... (0 Replies)
Discussion started by: andresguillen
0 Replies

2. AIX

Problem with multiple network interfaces

Hi .. we have two AIX 5.3 systems with a small client server app communicating over a TCP socket. Box A has a single network interface where the server app (in Java) opens a well known port and waits for connections from Box B. Box B has two network interfaces, X and Y. Interface X has the... (4 Replies)
Discussion started by: RonBowater
4 Replies

3. UNIX for Dummies Questions & Answers

/etc/network/interfaces

i need a one liner command that writes in /var/log/net.log the date when i connect to the network and when i disconect ..i know that i need to write somethin in /etc/network/interfaces but idk what ! please help (1 Reply)
Discussion started by: g0dlik3
1 Replies

4. UNIX for Advanced & Expert Users

How to bond network interfaces

All, I have a quad NIC on a V880 running Solaris 9. I've heard you can bond interfaces together and get better throughput. I found this link that seems to describe the process well. However, the command mentioned (dladm) is missing. Is there some package I need to install to get this command? Thx.... (2 Replies)
Discussion started by: agcodba
2 Replies

5. Debian

/etc/network/interfaces problem

Hello i am configuring a debian lenny sever ,/etc/network/interfaces is modified so that eth1 takes a static IP address then i save it wq! then i restart the networking , /etc/init.d/networking restart . but after reboot ,the file is reset ,note that the interfaces had by defauklt IPv6 address... (5 Replies)
Discussion started by: learn82
5 Replies

6. Solaris

Network Interfaces

I got second IOU in my M5000 but not able bring internal network interfcae .. ike i don't get link on those 2 interfaces .. and the same network cable plugged in PCI network card it works like a charm Is there any special way to enable the internal IOU interfaces or i have bad nics ? (8 Replies)
Discussion started by: fugitive
8 Replies

7. AIX

NIM w/ two network interfaces

Hi all, this is my first post on this forum. My main problem is this: I have a NIM server that I am trying to configure two interfaces on. One interface is for an internal Admin VLAN, the other is so that the server can use SUMA to pull updates. The problem is that I need help w/ the routing.... (1 Reply)
Discussion started by: snakernetb
1 Replies

8. AIX

NIM w/ two network interfaces

Hi all, this is my first post on this forum. My main problem is this: I have a NIM server that I am trying to configure two interfaces on. One interface is for an internal Admin VLAN, the other is so that the server can use SUMA to pull updates. The problem is that I need help w/ the routing.... (0 Replies)
Discussion started by: snakernetb
0 Replies

9. SCO

Network interfaces problem

Hi, I have problems with my SCO unix network interfaces. Intel integrated adapter was failing, so I installed new one - 3COM adapter into free PCI slot. Installed driver using SCO Software manager - successfully Added new Network adapter using SCO Network configuration manager - successfully... (0 Replies)
Discussion started by: vilius
0 Replies

10. Solaris

HOW-TO Retrieve all network interfaces??!

Yes. But just wait a bit. How to do it via system calls? I'm just a newbie in Unix\Linux\Solaris e.t.c. programming. Can anyone help me? I need an advice probably how to do it or may be what API to read... :) Please, help... (2 Replies)
Discussion started by: LocalStorm
2 Replies
Login or Register to Ask a Question

LEARN ABOUT BSD

hy

HY(4)							     Kernel Interfaces Manual							     HY(4)

NAME

       hy - Network Systems Hyperchannel interface

SYNOPSIS

       /sys/conf/SYSTEM:
	    NHY  hy_controllers # Hyperchannel

DESCRIPTION

       The hy interface provides access to a Network Systems Corporation Hyperchannel Adapter.

       The  network  to  which the interface is attached is specified at boot time with an SIOCSIFADDR ioctl.  The host's address is discovered by
       reading the adapter status register.  The interface will not transmit or receive packets until the network number is known.

DIAGNOSTICS

       hy%d: unit number 0x%x port %d type %x microcode level 0x%x.  Identifies the device during autoconfiguration.

       hy%d: can't handle af%d.  The interface was handed a message with addresses formatted in an  unsuitable	address  family;  the  packet  was
       dropped.

       hy%d:  can't  initialize.  The interface was unable to allocate UNIBUS resources. This is usually due to having too many network devices on
       an 11/750 where there are only 3 buffered data paths.

       hy%d: NEX - Non Existent Memory.  Non existent memory error returned from hardware.

       hy%d:  BAR overflow.  Bus address register overflow error returned from hardware.

       hy%d: Power Off bit set, trying to reset.  Adapter has lost power, driver will reset the bit and see if power is still out in the adapter.

       hy%d: Power Off Error, network shutdown.  Power was really off in the adapter, network connections are dropped.	 Software  does  not  shut
       down the network unless power has been off for a while.

       hy%d: RECVD MP > MPSIZE (%d).  A message proper was received that is too big.  Probable a driver bug.  Shouldn't happen.

       hy%d: xmit error - len > hy_olen [%d > %d].  Probable driver error.  Shouldn't happen.

       hy%d: DRIVER BUG - INVALID STATE %d.  The driver state machine reached a non-existent state.  Definite driver bug.

       hy%d: watchdog timer expired.  A command in the adapter has taken too long to complete.	Driver will abort and retry the command.

       hy%d: adapter power restored.  Software was able to reset the power off bit, indicating that the power has been restored.

SEE ALSO

       intro(4N), inet(4F)

BUGS

       If  the	adapter  does not respond to the status command issued during autoconfigure, the adapter is assumed down.  A reboot is required to
       recognize it.

       The adapter power fail interrupt seems to occur sporadically when power has, in fact, not failed.  The driver will believe that	power  has
       failed  only  if it can not reset the power fail latch after a ``reasonable'' time interval.  These seem to appear about 2-4 times a day on
       some machines.  There seems to be no correlation with adapter rev level, number of ports used etc. and whether a  machine  will	get  these
       ``bogus powerfails''.  They don't seem to cause any real problems so they have been ignored.

3rd Berkeley Distribution					  August 20, 1987							     HY(4)