05-14-2009
Quote:
Originally Posted by
kwachtler
Frozentin,
Yes, ifconfig can be used to setup IPMP live, but you still need to configure hostname.xxx files to make it persistent across reboots.
Reiterating, IPMP has two failure detection modes: 1) pinging, typically a router, 2) link status on the NIC, which does not ping. I have found link status to be a dependable IPMP failover trigger, conversely, I have found the ping method to falsely trigger failover when the default router was busy and could not respond to ping in a timely manner (but this is very rare).
KW
That's really good ! I'm going to test that ! I thought the Link-based shouldn't rely on ping...it's really not practical to rely on pinging gateway...what if your gateway goes down ? !!
I'm gona try it and return to you
10 More Discussions You Might Find Interesting
1. Solaris
Hi there
I have a requirement to provide failover to our customer boxes in case of interface / switch failure, I have been looking at Solaris Link Aggregation with LACP and I wanted to ask a question
Ive seen multiple websites that say the following
Does this also mean that if the... (2 Replies)
Discussion started by: hcclnoodles
2 Replies
2. UNIX for Advanced & Expert Users
Hi there
I have a requirement to provide failover to our customer boxes in case of interface / switch failure, I have been looking at Solaris Link Aggregation with LACP and I wanted to ask a question
Ive seen multiple websites that say the following
Does this also mean that if the... (1 Reply)
Discussion started by: hcclnoodles
1 Replies
3. IP Networking
I have some linux machines that I am trying to increase the throughput to on a single connection. They connect to a switch with two 1GbE lines and the switch does not have Link Aggregation support for these machines. I have tried bonding with balance-rr, balance-alb, but the machines can only... (4 Replies)
Discussion started by: Eruditass
4 Replies
4. AIX
Hi,
I need to setup a hacmp cluster (my first one, we usually use VCS on AIX), but I require more network bandwith than a normal gigabit etherchannel setup can provide, so I am thinking about using linkaggregation - 2 active adapters to one switch and a single backup adapter to another switch... (4 Replies)
Discussion started by: zxmaus
4 Replies
5. HP-UX
Hi,
Hoping someone can offer some advice on something i have not dealt with before.
We have a server that seems to have some very strange configuration done on it. It has 2 physical NIC's and rather than both be aggregated into LAN900 we have 1 in LAN900 and 1 in LAN901? (See Below)... (2 Replies)
Discussion started by: Andyp2704
2 Replies
6. Solaris
Me again :)
I'm trying to find a page describing the L2, L3 und L4 modes of dladm.
It's nice to read "hashed by ip header", but how should I use that?
On the file-server it's ok to have the six interfaces serving six clients each on it's own. But an rsync connection via switch between two... (8 Replies)
Discussion started by: PatrickBaer
8 Replies
7. HP-UX
Hi,
I want to Break the Link Aggregation. My aggregation are lan0+lan1 = lan900.
Now I want to break this and put the IP in lan0. But i have cluster environment and this is the main database server.
So It need to change in cluster script.
But I dont know where I have to change it.
Please... (1 Reply)
Discussion started by: mkiron
1 Replies
8. Solaris
Hi,
I'm not from the Solaris world and some of these things are new to me. Can someone tell me if it is possible to configure link aggregation without using LACP?
I am told etherchannel was setup without LACP. (3 Replies)
Discussion started by: techy1
3 Replies
9. IP Networking
Hi
ihave three link of internet and iwant to put one linux front of a firewall that this three linux speard firewall such az load balance and fialover but dont close any port and protocol and only firewall have been internet what way can i use for it ?
are there any script and services do that... (0 Replies)
Discussion started by: mnnn
0 Replies
10. Solaris
Hi,
I have Solaris-10 server and link aggregation is configured on this in below way
# dladm show-aggr
key: 1 (0x0001) policy: L4 address: 3c:d9:2b:ee:a8:a (auto)
device address speed duplex link state
bnx1 3c:d9:2b:ee:a8:a... (8 Replies)
Discussion started by: solaris_1977
8 Replies
LEARN ABOUT DEBIAN
iodine-client-start
IODINE-CLIENT-START(8) System Administration Utilities IODINE-CLIENT-START(8)
NAME
iodine-client-start - start an iodine IPv4-over-DNS tunnel
SYNOPSIS
iodine-client-start [option]
DESCRIPTION
'iodine-client-start' starts an iodine IP-over-DNS tunnel.
-h, --help
Print help and exit
-v, --version
Print version info and exit
Invoking the program without options attempts to set up and configure an iodine IP-over-DNS tunnel using the configuration in the file
/etc/default/iodine-client or by querying the user. It tries to figure out the right way to set things up by observing the network, and if
all else fails by guessing.
QUICK CONFIGURATION
Put two lines in the file /etc/default/iodine-client
subdomain=your.tunnel.sub.domain
passwd=password_for_that_tunnel
or invoke the script with those environment variables set:
env subdomain=xxx passwd=xxx iodine-client-start
If these are not set, the script will query the user for them.
DETAILS
The configuration file consists of lines which are either comments starting with '#', or settings of the form VAR="val". Valid VARs are:
subdomain
Sample value: your.tunnel.sub.domain (no default, must be set)
passwd
Sample value: password_for_that_tunnel (no default, must be set)
testhost
Hostname to ping when testing if network is working (default: slashdot.org)
bounce_localnet
Take the local network down and then up again before starting tunnel (default: false)
test_ping_localnet
Test if the local network is working by pinging the gateway (default: true)
test_ping_tunnel
Test if the iodine tunnel is working after it has been set up by pinging the host at the other end (default: true)
test_ping_final
Test if the tunnel is working after everything is ostensibly set up by trying to ping an external host (default: true)
default_router
IP address of router on the local network---should be found automatically, set this if that fails and the program guesses wrong.
interface
Interface to use (e.g., eth1, eth0, etc) for connection to DNS server used for the iodine tunnel---should be found automatically,
set this if that fails and the program guesses wrong.
mtu
Set if tunnel MTU needs to be manually changed (lowered). Should not be necessary anymore, as recent versions of iodine negotiate an
appropriate MTU during tunnel setup. But if that negotiation does not happen, or if you are using an older version of iodine, the
default tunnel MTU is 1024, and if the local DNS server restricts to 512 byte packets you might need to use an MTU of 220.
skip_raw_udp_mode
Set "-r" option in iodine command line. With this option, iodine does not try to establish a direct UDP socket to the iodine server
on port 53. (default: true).
continue_on_error
Set if the script should continue even if a command fails. Use to test script when running as non-root. Defaults to false if run-
ning as root, true otherwise.
iodine-client-start 1.0.4 June 2014 IODINE-CLIENT-START(8)