They are in separate switches.These network cables are plugged from different switches.Switches are made of Cisco Catalyst 3640.They are managed switches.
What are the configuration that needs to be checked in these switches to verify whether they are properly configured for Linux bonding or not?Can u guide me on this?
I have the following configuration made for bonding.
ifconfig of bond0
---------- Post updated 09-14-15 at 12:54 AM ---------- Previous update was 09-13-15 at 01:20 PM ----------
Is there any hint can you give seeing my above reply?
Last edited by Don Cragun; 09-14-2015 at 03:14 AM..
Reason: Add CODE and ICODE tags.
I have a Ubuntu linux (Ubuntu 6.06) at home. I have a ADSL modem (eth0) connected to it for my Broadband connection. It all works fine when the system gets started. But, when I receive a call, the link goes off. And then I lose my internet connection. I tried ifup/ifdown to bring the connection... (2 Replies)
Hi guys,
I got a global zone with with two zones runnig.
After a patch upgrade (July 2010) one of them stop to working fine: basically I can't ping it ( I mean I can ping from the other zone, but actually the ping pass across the global zone..) and I can't access it in ssh or telnet...(actually... (0 Replies)
Hi, I'm trying to create a lab environment in my personal laptop. I have created a virtualbox RHEL6.1 and I want to make another copy out of it to make it 4 instances by simply copying the whole folder and changing their name and then changing their IP addresses. is this OK? please advice.
for... (2 Replies)
Hello,
I am trying to set up Channel Bonding on a RHEL6 Virtual Box VM. I have 2 ethernet cards on the machine which are set up in Internal Network mode. I followed all the steps exactly as mentioned in the RHEL6 deployment Guide, but for some reason i think results are not correct. Here are my... (13 Replies)
Hi team,
I'm running into a problem configuring bonding on an CentOS 64bit on DELL Server. I'm connecting eth0 and eth1
to a Cisco 2948 (CatOS 8.1(3)) and receiving flapping notices. The
ethernet address is that of the primary interface. I have tried
several different modes,... (3 Replies)
HI all,
First post on the forum, and my first proper project on the Paspberry Pi, so sorry if this is in the wrong place.
I am trying to turn my Pi in to a 3G/4G Bonding router. I have been researching and trying this for a week or so now. The basic plan is to have up to 6 ZTE MF823 USB... (0 Replies)
We have two hosts in same vlan with same route rules.
One of them is not able to connect to an outside IP while in another I get "failed: Connection timed out" while testing the connectivity through netcat.
I have tried mtr /traceroute and it gives me the same results.
Is there a netcat... (1 Reply)
Dear All ,
Very recently we have configured Network bonding in our Linux Server Redhat Linux 5.x.
After configuring , we restarted the network services , the link was down after that , we could not login in to the Server.
So after that , we logged in to console and tried to... (2 Replies)
Respected Members,
We encountered an issue during node reboot when eth1 and eth5 of bond1 were behaving unusual(both eth1 and eth5 were in unknown states and ifdown and ifup were used to rectify). Please find the messages and configuration files as below and please let me know for any other... (0 Replies)
bond0 active in eth0 and inactive in eth4. why eth4 received network package?
Bonding Mode: fault-tolerance (active-backup)
Primary Slave: eth0 (primary_reselect failure)
Currently Active Slave: eth0
MII Status: up
MII Polling Interval (ms): 100
Up Delay (ms): 0
Down Delay (ms): 0
... (4 Replies)
Discussion started by: samran35
4 Replies
LEARN ABOUT OSX
miibus
MIIBUS(4) BSD Kernel Interfaces Manual MIIBUS(4)NAME
miibus -- IEEE 802.3 Media Independent Interface network bus
SYNOPSIS
For most network interface cards (NIC):
device miibus
DESCRIPTION
The miibus driver provides an interconnection between the Media Access Control (MAC) sublayer, the Physical Layer entities (PHY), Station
Management (STA) entities, and the PHY Layer as defined by the IEEE 802.3 Standard.
The miibus layer allows network device drivers to share common support code for various external PHY devices. Most 10/100 network interface
cards either use an MII transceiver or have built-in transceivers that can be programmed using an MII interface. The miibus driver currently
handles all of the media detection, selection, and reporting using the ifmedia interface. A generic driver has been included for all PHYs
that are not handled by a specific driver, this is possible because all 10/100 PHYs implement the same general register set along with their
vendor specific register set.
The following network device drivers use the miibus interface:
age(4) Attansic/Atheros L1 Gigabit Ethernet
alc(4) Atheros AR8131/AR8132 PCIe Ethernet
ale(4) Atheros AR8121/AR8113/AR8114 PCIe Ethernet
aue(4) ADMtek USB Ethernet
axe(4) ASIX Electronics AX88172 USB Ethernet
bce(4) Broadcom NetXtreme II Gigabit Ethernet
bfe(4) Broadcom BCM4401 Ethernet
bge(4) Broadcom BCM570xx Gigabit Ethernet
cas(4) Sun Cassini/Cassini+ and National Semiconductor DP83065 Saturn
dc(4) DEC/Intel 21143 and various workalikes
ed(4) NE[12]000, SMC Ultra, 3c503, DS8390 cards
et(4) Agere ET1310 Gigabit Ethernet
fxp(4) Intel EtherExpress PRO/100B
gem(4) Sun ERI, Sun GEM and Apple GMAC Ethernet
hme(4) Sun HME Ethernet
jme(4) JMicron JMC250 Gigabit/JMC260 Fast Ethernet
lge(4) Level 1 LXT1001 NetCellerator Gigabit Ethernet
msk(4) Marvell/SysKonnect Yukon II Gigabit Ethernet
nfe(4) NVIDIA nForce MCP Networking Adapter
nge(4) National Semiconductor DP83820/DP83821 Gigabit Ethernet
nve(4) NVIDIA nForce MCP Networking Adapter
pcn(4) AMD Am79C97x PCI 10/100
re(4) RealTek 8139C+/8169/8169S/8110S
rl(4) RealTek 8129/8139
rue(4) RealTek RTL8150 USB To Fast Ethernet
sf(4) Adaptec AIC-6915
sge(4) Silicon Integrated Systems SiS190/191 Ethernet
sis(4) Silicon Integrated Systems SiS 900/SiS 7016
sk(4) SysKonnect SK-984x and SK-982x Gigabit Ethernet
ste(4) Sundance ST201 (D-Link DFE-550TX)
stge(4)
Sundance/Tamarack TC9021 Gigabit Ethernet
tl(4) Texas Instruments ThunderLAN
tx(4) SMC EtherPower II (83c170)
udav(4)
Davicom DM9601 USB Ethernet
vge(4) VIA VT612x PCI Gigabit Ethernet
vr(4) VIA Rhine, Rhine II
wb(4) Winbond W89C840F
xl(4) 3Com 3c90x
COMPATIBILITY
The implementation of miibus was originally intended to have similar API interfaces to BSD/OS 3.0 and NetBSD, but as a result are not well
behaved newbus device drivers.
SEE ALSO age(4), alc(4), ale(4), arp(4), aue(4), axe(4), bce(4), bfe(4), bge(4), cas(4), dc(4), ed(4), et(4), fxp(4), gem(4), hme(4), jme(4), lge(4),
msk(4), netintro(4), nfe(4), nge(4), nve(4), pcn(4), re(4), rgephy(4), rl(4), rue(4), sf(4), sge(4), sis(4), sk(4), ste(4), stge(4), tl(4),
tx(4), udav(4), vge(4), vr(4), wb(4), xl(4)STANDARDS
More information on MII can be found in the IEEE 802.3 Standard.
HISTORY
The miibus driver first appeared in FreeBSD 3.3.
AUTHORS
This manual page was written by Tom Rhodes <trhodes@FreeBSD.org>.
BSD January 15, 2011 BSD