Network interfaces problem


 
Thread Tools Search this Thread
Operating Systems SCO 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. IP Networking

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
lfa(7)							 Miscellaneous Information Manual						    lfa(7)

NAME
lfa - DAPCA/DAPBA Asynchronous Transfer Mode (ATM) Network Interface SYNOPSIS
config-driver lfa DESCRIPTION
The lfa interface can be either the Compaq ATM HE622 ATM adapter (DAPCA) or to the Compaq ATM HE155 ATM adapter (DAPBA), providing trans- mission rates of 622 megabits per second and 155 megabits per second, respectively. Both adapters use the same driver. The lfa driver controls the transmission and reception of data across the ATM network over specified Virtual Circuits (VCs). The creation and management of the VCs is controlled by the ATM subsystem software that sits above the driver. When the driver is started, it registers with the ATM subsystem and then performs any task that the subsystem requests. Note that the transmission rate of the link is not the same as the transmission rate as seen by a user application. The following factors can contribute to this: the speed of the Peripheral Component Interconnect (PCI) bus, the signaling overhead on the link medium itself, the speed of the host processor, and other activity in the system (especially on the same PCI bus). See the sys_attrs_lfa(5) reference page for a list of the lfa subsystem attributes. ERRORS
The following diagnostic and error messages contain relevant information provided by the lfa interface, and are displayed on the console. Each message begins with the adapter identification, including the adapter number (for example, lfa0). Ensure that either a Compaq HE622 or HE155 ATM adapter is installed in the system and that it is a DAPBA-FA, DAPBA-UA, or DAPCA-FA. The specified adapter failed its ini- tialization due to insufficient memory resources. This could possibly happen if kernel memory debugging was enabled in the /etc/syscon- figtab file. If this message is displayed, the adapter will not operate. The driver failed when it tried to register itself with the ATM subsystem because the optional ATM components are not configured in the kernel. Reconfigure your kernel with the the ATM, UNI3X, ATMIP, and LANE options. See Asynchronous Transfer Mode for more information. An error occurred when trying to gather the resources necessary (for example, memory for data structures and specified bit rate for transmission) to set up a Virtual Circuit (VC). An invalid VPI or VCI value was passed to the VC activation routine. Ensure that the values specified fit into the range given for the num_vpi_bits attribute described in the "Subsystem Attributes" section. A request to delete a VC was made and the VC was transmitting. This condition did not go away after 1 second so the VC will be deleted anyway. It is possible that the VC's state is inconsistent, and that this may indicate a problem with the driver. Informational messages contain information provided by the lfa driver. These messages are printed on the console and begin with the adapter identification, including the adapter number. The driver successfully configured and registered itself with the ATM subsystem software. The connection either to a switch or to another system (in a point-to-point configuration) exists. This message is displayed after the driver is initially brought up. If it is not displayed, it is likely there is a problem with the cables. The connection either to a switch or to another system existed, but no longer exists. An administrator issued a command to shut down the adapter. If you do not see this message, the adapter is still operational. To shut down the adapter, use the atmconfig down command. RELATED INFORMATION
Commands: netstat(1), atmarp(8), atmconfig(8), atmelan(8), atmsig(8), sysconfig(8). Attributes: sys_attrs_lfa(5). Network Information: arp(7), inet(7), intro(7). Asynchronous Transfer Mode Network Administration delim off lfa(7)