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

NAME
fence_mcdata - I/O Fencing agent for McData FC switches SYNOPSIS
fence_mcdata [OPTION]... DESCRIPTION
fence_mcdata is an I/O Fencing agent which can be used with McData FC switches. It logs into a McData switch via telnet and disables a specified port. Disabling the port which a machine is connected to effectively fences that machine. Lengthy telnet connections to the switch should be avoided while a GFS cluster is running because the connection will block any necessary fencing actions. fence_mcdata accepts options on the command line as well as from stdin. fenced sends parameters through stdin when it execs the agent. fence_mcdata can be run by itself with command line options which is useful for testing. After a fence operation has taken place the fenced machine can no longer connect to the McData FC switch. When the fenced machine is ready to be brought back into the GFS cluster (after reboot) the port on the McData FC switch needs to be enabled. This can be done by running fence_mcdata and specifying the enable action. Vendor URL: http://www.brocade.com OPTIONS
-a IPaddress IP address of the switch. -h Print out a help message describing available options, then exit. -l login Username name for the switch. -n port The port number to disable on the switch. -o action The action required. disable (default) or enable. -p password Password for login. -S path Full path to an executable to generate the password for login. -q Quiet mode: print only error messages. -V Print out a version message, then exit. STDIN PARAMETERS
agent = < param > This option is used by fence_node(8) and is ignored by fence_mcdata. ipaddr = < hostname | ip > IP address or hostname of the switch. login = < param > Login name. option = < param > The action required. disable (default) or enable. passwd = < param > Password for login. passwd_script = < param > Full path to an executable to generate the password for login. port = < param > The port number to disable on the switch. SEE ALSO
fence(8), fence_node(8) fence_mcdata(8)
All times are GMT -4. The time now is 04:33 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy