Probe-based IPMP active - active
Probe-based IPMP active - passive
Link-based only active -standby
????
What are differences between
Probe-based IPMP active - passive anddd
Link-based only active -standby
???!!!
For example in active active probe-based IPMP there are
lets... (6 Replies)
Guide me in setting up IPMP on solaris 10 box .
my system has 2 physical interface
bge0 - not used
bge1 - 10.10.10.10
bge1:1 - 10.10.10.11
please guide , how can i implement IPMP on this server , how many additional test ip is required ? , as 2 ip's are configured on bge1 interface ,... (3 Replies)
Hi,
I've a problem when try to detach nic e1000g1.
IPMP configuration:
# ifconfig -a
...cut...
e1000g1: flags=1000842<BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 7
inet 0.0.0.0 netmask 0
ether 0:c:29:67:16:ef
e1000g2: flags=1000842<BROADCAST,RUNNING,MULTICAST,IPv4>... (3 Replies)
Dear All,
I have configured IPMP in one of my SUN machine which is having solros 9 version. I have updated all files like /etc/hosts,/etc/hostname.ce0 and /etc/hostname.ce1 and rebooted the server. But IP's are not mounted which i have given in /etc/hosts file.
Please find the below ifconfig... (6 Replies)
Can any one please explain me the concept behind IPMP in solaris clustering.Basic explanation would be really appreciated...
Thanks in Advance
vks (2 Replies)
Hi,
I have two physical interface connected to solaris box.
1. e1000g1
2. e1000g2
I have added these interfaced under a same IPMP group "IPMP1"
After that I have configured a test address for e1000g1 like below
ifconfig e1000g1 addif <ip-address> netmask + broadcast + -failover... (1 Reply)
Discussion started by: praveensharma21
1 Replies
LEARN ABOUT DEBIAN
epair
EPAIR(4) BSD Kernel Interfaces Manual EPAIR(4)NAME
epair -- A pair of virtual back-to-back connected Ethernet interfaces.
SYNOPSIS
To compile this driver into the kernel, place the following line in your kernel configuration file:
device epair
Alternatively, to load the driver as a module at boot time, place the following line in loader.conf(5):
if_epair_load="YES"
DESCRIPTION
The epair is a pair of Ethernet-like software interfaces, which are connected back-to-back with a virtual cross-over cable.
Each epair interface pair is created at runtime using interface cloning. This is most easily done with the ifconfig(8) create command or
using the cloned_interfaces variable in rc.conf(5). While for cloning you only give either epair or epair<n> the epair pair will be named
like epair<n>[ab]. This means the names of the first epair interfaces will be epair0a and epair0b.
Like any other Ethernet interface, an epair needs to have a network address. Each epair will be assigned a locally administered address by
default, that is only guaranteed to be unique within one network stack. To change the default addresses one may use the SIOCSIFADDR ioctl(2)
or ifconfig(8) utility.
The basic intend is to provide connectivity between two virtual network stack instances. When connected to a if_bridge(4) one end of the
interface pair can also be part of another (virtual) LAN. As with any other Ethernet interface one can configure vlan(4) support on top of
it.
SEE ALSO ioctl(2), altq(4), bpf(4), if_bridge(4), vlan(4), loader.conf(5,) rc.conf(5), ifconfig(8)HISTORY
The epair interface first appeared in FreeBSD 8.0.
AUTHORS
The epair interface was written by Bjoern A. Zeeb, CK Software GmbH, under sponsorship from the FreeBSD Foundation.
BSD July 26, 2009 BSD