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 NETBSD
virt
VIRT(4) BSD Kernel Interfaces Manual VIRT(4)NAME
virt -- rump virtual network interface
SYNOPSIS
#include <rump/rump.h>
int
rump_pub_virtif_create(int num);
DESCRIPTION
The virt interface acts as a link between a rump virtual kernel and a host tap(4) interface. Interface number <n> always corresponds with
the host tap interface tap<n>. All data sent by virt is written into /dev/tap<n> and all data read from /dev/tap<n> is passed as Ethernet
input to the rump virtual kernel.
A virt interface can be created in two ways:
o Programmatically by calling rump_pub_virtif_create().
o Dynamically at runtime with ifconfig(8) or equivalent using the create command.
Destroying a virt interface is possible only through ifconfig(8) destroy.
The host's tap(4) interface can be further bridged with hardware interfaces to provide full Internet access to a rump kernel.
SEE ALSO rump(3), bridge(4), tap(4), brconfig(8), ifconfig(8)BSD November 15, 2010 BSD