Sponsored Content
Full Discussion: Network Bonding Issue
Operating Systems Linux Red Hat Network Bonding Issue Post 302954928 by hicksd8 on Sunday 13th of September 2015 07:03:42 AM
Old 09-13-2015
What you are describing can be caused by the network switch and not the Linux setup. Are these network cables both plugged into the same switch? Or different switches? Please explain.

What make/type of switch(es) is it? Are they managed switches? Have they been configured for bonding?

---------- Post updated at 12:03 PM ---------- Previous update was at 11:18 AM ----------

Link Aggregation on a RedHat (CentOS) server and a Cisco Catalyst switch - Charles Hooper
 

10 More Discussions You Might Find Interesting

1. Ubuntu

Network issue

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)
Discussion started by: ranj@chn
2 Replies

2. Solaris

Zone network issue

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)
Discussion started by: cecco16
0 Replies

3. Red Hat

VM network issue

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)
Discussion started by: messi777
2 Replies

4. IP Networking

Channel bonding Issue - Bond0 interface not getting up in on RHEL6

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)
Discussion started by: Rohit Bhanot
13 Replies

5. Red Hat

BONDING with Flapping issue!

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)
Discussion started by: leo_ultra_leo
3 Replies

6. IP Networking

Is bond0 ready and a bonding interface? - 4G Bonding Router Problems (RPI)

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)
Discussion started by: elliottlc
0 Replies

7. Red Hat

Network issue in same vlan

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)
Discussion started by: jacki
1 Replies

8. Red Hat

Network bonding

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)
Discussion started by: jegaraman
2 Replies

9. Linux

Issue in Bonding during Reboot(Linux)

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)
Discussion started by: Mudit Bansal
0 Replies

10. UNIX for Beginners Questions & Answers

Why inactive slave bonding received network package in redhat?

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
timed(8)						      System Manager's Manual							  timed(8)

NAME
timed - The network time daemon SYNOPSIS
timed [-tME] [-n | -i network] FLAGS
Specifies the names of the networks (as defined in the /etc/networks file) to be excluded from clock synchronization. Each network name that is an argument to the -i flag is added to the list of networks that the timed daemon will ignore. If the -i flag is used, timed accesses all networks to which the host is connected except for the specified networks. If neither the -i flag nor the -n flag is used, timed tries to access all the network devices connected to the local host. Do not use the -i and -n flags together. Specifies that a machine can become the time server if the master time server becomes inoperative. See the Restrictions section for more information. Overrides the input of slaves. Use the -E flag in conjunction with the -M flag. It specifies that a master timed system will not average the times of the slaves to calculate the network time. Instead, it distributes the time of its local host as the network time. This flag allows a master timed system to distribute time to a network while the network time is controlled by an outside agent (such as the Network Time Protocol (NTP)). Specifies the names of the networks (as defined in the /etc/networks file) to be included in clock synchronization. When timed is started, it gathers information about all the network devices connected to the local host. The network argument to the -n flag is the name of the network that timed should access. If the -n flag is used, only the specified networks are accessed. If neither the -n flag nor the -i flag is used, timed tries to access all the network devices connected to the local host. Do not use the -n and -i flags together. Enables tracing of messages received in /usr/adm/timed.log. DESCRIPTION
The timed daemon is not invoked at boot time by default. You can use /usr/sbin/timedsetup to configure the timed daemon. The timed daemon synchronizes the host's clock with those of other machines on the local area network that are also running the timed dae- mon. The timed daemon slows the clocks of some machines and speeds up the clocks on other machines to create an average network time. The average network time is computed from measurements of clock differences using the Internet Control Message Protocol ICMP timestamp request message. The service provided by timed is based on a master/slave (client/server) scheme. When timed is started on a machine, it asks the master timed daemon for the network time and sets the host's clock to that time. After that, the host accepts synchronization messages periodi- cally sent by the master and calls the adjtime system call to perform the needed corrections on the host's clock. The timed daemon also communicates with the date command to set the date globally, and with timedc, the timed control program. If the machine running the master ceases to function, a machine that is running the timed daemon with the -M flag becomes the new master timed daemon. Note The timed daemon is provided for compatibility. Tru64 UNIX also provides support for the Network Time Protocol through the xntpd daemon. You should use NTP for time synchronization. If you need to run both NTP and the timed daemon, you must run the timed daemon with the -E flag. If you plan to run both the timed daemon and NTP, you should also configure NTP first. RESTRICTIONS
In configurations with two or more hosts each connected to the same two or more subnetworks, only one of the host can run the timed with the -M option. FILES
Specifies the command path Contains messages traced for the timed command Contains information about the known networks RELATED INFORMATION
Commands: date(1), timedc(8), timedsetup(8) Daemons: xntpd(8) Functions: adjtime(2), gettimeofday(2) delim off timed(8)
All times are GMT -4. The time now is 05:09 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy