Hi, The default gateway (172.17.220.1) cannot be pinged via the default interface bond0 (172.17.220.231), but can be pinged via interface eth1 (10.201.135.73).
Code:
# ping -I eth1 172.17.220.1
PING 172.17.220.1 (172.17.220.1) from 10.201.135.73 eth1: 56(84) bytes of data.
64 bytes from 172.17.220.1: icmp_seq=0 ttl=255 time=5.48 ms
64 bytes from 172.17.220.1: icmp_seq=1 ttl=255 time=0.523 ms
# ping -I bond0 172.17.220.1
PING 172.17.220.1 (172.17.220.1) from 172.17.220.231 bond0: 56(84) bytes of data.
From 172.17.220.231 icmp_seq=1 Destination Host Unreachable
From 172.17.220.231 icmp_seq=2 Destination Host Unreachable
Ping is supposed to work with the default interface bond0. Because the virtual interface bond0 can be pinged by systems in the same subnet, bond0 is working (right?). There must be a routing issue. Here is the interfaces info:
Hello,
I've moved to a new network with multiple AIX box's. Most of them are working fine and dandy.
On one box I need to set up a static route to a gateway.. no problem right?
Whenever I add the route it appears in the routing table as UGc and then begins adding new entries to the... (1 Reply)
I have a string as "Period= 20090531 Client Name= Clayton Lumbar Company Destination= MD"
I want to parse the string and store it in 3 different variables.
$period (should get value 20090531)
$client (should get value "Clayton Lumbar company")
$dest (should get value MD)
How can I do... (3 Replies)
I have an IP routing issue or I am just to stupid to work it out myself.
I have setup am old PC running SUSE Linux 11.3 as a router, the system has 3 Interfaces connecting 3 networks.
Interface 1 = 10.164.2.161/21
Interface 2 = 192.168.1.210/24
Interface 3 = 30.1.0.11/16
The default... (6 Replies)
I have run into a wall troubleshooting a Centos 5 networking issue. Hoping someone can assist.
I've got a box with two vlans trunked over bond0
bond0 Link encap:Ethernet HWaddr 00:22:64:C1:D6:60
inet6 addr: fe80::222:64ff:fec1:d660/64 Scope:Link ... (0 Replies)
hello everyone!:)
I have an exercise which I think is difficult for beginner like me. Here is the exercise
Create a shell script, which takes a directory as command line argument.
Script displays ten first lines from every text file in that directory. After
displaying the lines from the... (1 Reply)
hi guys
suse 11 SP1 x64
I have a server (4 NIC ports 192.168.100.100-103) that connects point to point to a storage device (same thing 4 ports 192.168.110.100-113) but this server connects to normal LAN 10.6.100.x - gateway 10.6.100.1
the issue is when testing connectivity to the storage... (7 Replies)
we are not able to ping client server (falcon-ebr.sbms.bsc.com) from netbackup master server (135.179.96.122 tsprd-ebr.edc.single.net)
However from client server we are able to ping the master Server.
Please assist on this (1 Reply)
Hi,
Please help me on issue described below,
I have 4 machine setup, M1 -> M2 -> M3 | M4. And A laptop that can be reachable through both M3 and M4.
M2 has 2 NIC conected to M3 and M4. Now I want to divide the flow coming from M1 for laptop.
At M2, I have done following,... (1 Reply)
Discussion started by: rahulbhansali24
1 Replies
LEARN ABOUT CENTOS
bond2team
BOND2TEAM(1) Bonding to Team conversion tool BOND2TEAM(1)NAME
bond2team -- Converts bonding configuration to team
SYNOPSIS
bond2team [options]
DESCRIPTION
bond2team is a tool to convert bonding options to team trying as much as possible to keep the original functionality.
The resulting files are saved in a temporary directory using ifcfg style by default. In the case of converting an ifcfg file, it translates
the bonding options to team, preserving all other options. In that case, it converts the respective slave ifcfg files to team port, pre-
serving all their other options too. In case of converting from given bonding options in the command line, the tool can use the specified
ports as team ports.
OPTIONS --master <interface>
Specify the interface name or ifcfg file to convert. If the interface name is specified, the tool will look at
/etc/sysconfig/network-scripts/ for the respective ifcfg file.
--rename <interface>
This is a convenient option to replace the original interface name by the specified name. For instance, if --master specifies bond0,
it is possible to use --rename team0 to change the final interface name to team0.
--ifcfg
Set the output format to ifcfg config style. [default]
--json Set the output format to JSON style. See teamd.conf(5) for further details.
--bonding_opts '<bonding options>'
Specify the bonding options to be converted instead of reading them from the ifcfg file.
--port <interface>
Set the specified interface as a team port.
--configdir <directory>
Change the ifcfg configuration path from /etc/sysconfig/network-scripts to the specified <directory>.
--outputdir <directory>
Set the output directory to <directory>.
--stdout
Print the result to the screen instead of writing to files.
--debug
Increase the debugging level.
--quiet
Disallow any messages to be printed to console.
--version
Print tool version to console and exit.
--help Print help text to console and exit.
--examples
Print common usage examples to console and exit.
EXAMPLES
To convert the current 'bond0' ifcfg configuration to team ifcfg:
# bond2team --master bond0
To convert the current 'bond0' ifcfg configuration to team ifcfg renaming the interface name to 'team0'. Caution : firewall rules, alias
interfaces, etc., that might be tied to the original interface name can break after the renaming because the tool will only change the
ifcfg file, nothing else.
# bond2team --master bond0 --rename team0
To convert given bonding parameters with ports without any ifcfg:
# bond2team --bonding_opts 'mode=1 miimon=500 primary=eth1 primary_reselect=0' --port eth1 --port eth2 --port eth3 --port eth4
For more examples, see the option --examples.
CAVEATS
The tool will not convert any other configuration which might be tied to the current setup. For instance, firewall rules, alias interfaces,
bridges, and so on.
AUTHOR
Flavio Leitner is the original author of the tool. Jiri Pirko is the original author and current maintainer of libteam.
SEE ALSO teamd(8), teamdctl(8), teamd.conf(5), teamnl(8)libteam 2013-07-18 BOND2TEAM(1)