Sponsored Content
Operating Systems Solaris Solaris 8: Multiple primary interfaces connected to the same network Post 302528548 by DGPickett on Tuesday 7th of June 2011 11:12:42 AM
Old 06-07-2011
Disappearing when not used is an arp cache feature, in case you are changing NICs on an host. I think 5 minutes is pretty usual, esp for Windows. This makes things tricky/slow if you design a failover that puts a new MAC on an IP.

If you pull the cable on the first NIC, does it move over gracefully?

If you provide saturating load, does it ever use the other NICs?
This User Gave Thanks to DGPickett For This Post:
 

10 More Discussions You Might Find Interesting

1. 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

2. 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

3. UNIX for Dummies Questions & Answers

How to display the primary network interface...

How do I find out what the primary network interface is on an AIX system.. Found commands to display information on the various interfaces but nothing that guides me to how to tell which one is the primary network interface. Thanks, ~D (1 Reply)
Discussion started by: djlerman
1 Replies

4. 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

5. 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

6. Shell Programming and Scripting

Shell script using ssh remains connected at primary site

Hi All, OS:AIX 5.3 L My shell script using ssh remains connected at primary site and ssh doesn't get disconnected.What should be typed and where in the shell script below to do it. Shell script ======== #!/usr/bin/ksh v_standby=`sqlplus -s /nolog <<END @standby.sql END` echo... (5 Replies)
Discussion started by: a1_win
5 Replies

7. 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

8. 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

9. 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

10. 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
RE(4)							   BSD Kernel Interfaces Manual 						     RE(4)

NAME
re -- RealTek 8139C+/8169/8169S/8110S PCI Ethernet adapter driver SYNOPSIS
re* at pci? dev ? function ? re* at cardbus? function ? DESCRIPTION
The re driver provides support for various NICs based on the RealTek RTL8139C+, RTL8169, RTL8169S, and RTL8110S PCI/Cardbus Ethernet con- trollers, including the following: o Alloy Computer Products EtherGOLD 1439E 10/100 (8139C+) o Compaq Evo N1015v Integrated Ethernet (8139C+) o Gigabyte 7N400 Pro2 Integrated Gigabit Ethernet (8110S) o NETGEAR GA311 (8169S) o PLANEX COMMUNICATIONS Inc. GN-1200TC (8169S) o Xterasys XN-152 10/100/1000 NIC (8169) o Corega CG-LAPCIGT Gigabit Ethernet (8169S) o D-Link DGE-528T Gigabit Ethernet (8169S) o US Robotics (3Com) USR997902 Gigabit Ethernet (8169S) o Linksys EG1032 rev. 3 Gigabit Ethernet (8169S) NICs based on the 8139C+ are capable of 10 and 100Mbps speeds over CAT5 cable. NICs based on the 8169, 8169S, and 8110S are capable of 10, 100, and 1000Mbps operation. All NICs supported by the re driver have TCP/IP checksum offload and hardware VLAN tagging/insertion features, and use a descriptor-based DMA mechanism. They are also capable of TCP large send (TCP segmentation offload). The 8139C+ is a single-chip solution combining both a 10/100 MAC and PHY, and its PHY is supported by rlphy(4). The 8169 is a 10/100/1000 MAC only, requiring a GMII or TBI external PHY and some 8169 based boards have Marvell 88E1000 PHY supported by makphy(4). The 8169S and 8110S are single-chip devices containing both a 10/100/1000 MAC and 10/100/1000 copper PHY, which is supported by rgephy(4). Standalone 10/100/1000 cards are available in both 32-bit PCI and 64-bit PCI models. The 8110S is designed for embedded LAN-on-motherboard applica- tions. The 8169, 8169S, and 8110S also support jumbo frames, which can be configured via the interface MTU setting. Selecting an MTU larger than 1500 bytes with the ifconfig(8) utility configures the adapter to receive and transmit jumbo frames. The re driver supports the following media types: autoselect Enable autoselection of the media type and options. The user can manually override the autoselected mode by adding media options to rc.conf(5). 10baseT/UTP Set 10Mbps operation. The ifconfig(8) mediaopt option can also be used to select either full-duplex or half-duplex modes. 100baseTX Set 100Mbps (Fast Ethernet) operation. The ifconfig(8) mediaopt option can also be used to select either full-duplex or half-duplex modes. 1000baseTX Set 1000baseTX operation over twisted pair. The RealTek GigE chips support 1000Mbps in full-duplex mode only. The re driver supports the following media options: full-duplex Force full duplex operation. half-duplex Force half duplex operation. For more information on configuring this device, see ifconfig(8). DIAGNOSTICS
re%d: can't map i/o space A fatal initialization error has occurred. re%d: can't map mem space A fatal initialization error has occurred. re%d: couldn't map interrupt A fatal initialization error has occurred. re%d: watchdog timeout The device has stopped responding to the network, or there is a problem with the network connection (cable). SEE ALSO
arp(4), cardbus(4), mii(4), netintro(4), pci(4), rgephy(4), rlphy(4), ifconfig(8) RealTek Semiconductor RTL8139C+, RTL8169, RTL8169S, and RTL8110S datasheets, http://www.realtek.com.tw. HISTORY
The re device driver first appeared in FreeBSD 5.2 and was ported to NetBSD 2.0. AUTHORS
The re driver was written by Bill Paul <wpaul@windriver.com>. BUGS
The Xterasys XN-152 32-bit PCI NIC, which uses the RTL8169 MAC and Marvell 88E1000 PHY, has a defect that causes DMA corruption if the board is plugged into a 64-bit PCI slot. The defect lies in the board design, not the chip itself: the PCI REQ64# and ACK64# lines should be pulled high, but they are not. The result is that the 8169 chip is tricked into performing 64-bit DMA transfers even though a 64-bit data path between the NIC and the bus does not actually exist. Unfortunately, it is not possible to correct this problem in software, however it is possible to detect it. When the re driver is loaded, it will run a diagnostic routine designed to validate DMA operation by placing the chip in digital loopback mode and initiating a packet trans- mission. If the card functions properly, the transmitted data will be echoed back unmodified. If the echoed data is corrupt, the driver will print an error message on the console and abort the device attach. The user should ensure the NIC is installed in a 32-bit PCI slot to avoid this problem. The RealTek 8169, 8169S, and 8110S chips appear to only be capable of transmitting jumbo frames up to 7.5K in size. BSD
January 8, 2007 BSD
All times are GMT -4. The time now is 10:53 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy