Solaris

Hi DukeNuke2. The - failover + failover in the config file should be ok. I had the Sun engineer take a look and he said it was fine. I'll ask him to double check it. The first -failover is for the test address which won't fail over. The second +failover is for the virtual address which will. I have implemented this on to three other servers with the exact same configuration and it has worked.

I have used if_mpadm to test the failover instead of unplugging the network cable. It worked with no problem. IPMP configuration aside, this failed interface problem has happened on a server I have without using IPMP.

We did a network test where the primary network was switched off. This server had one interface connected to that network. When the network was switched back on the interface on the Sun-Fire-V210 had a failed flag on it.

I couldn't get it working again so I plumbed a second interface and configured that. It only happened to that server. All the other servers were fine. Even unplumbing and plumbing the problem interface did not work. There has to be a hardware/software setting somewhere that prevents this from happening. Sun engineer so far has come back with nothing

Thanks.

Sparcman

just for test, use the settings from the admin guide like:

Code:

dummy1 netmask + broadcast + group netgroup up \
	addif hostname deprecated -failover netmask + broadcast + up

dummy2 netmask + broadcast + deprecated group netgroup -failover standby up

hth,
DN2

Mmmm IPMP, we meet again. :-) I had issue with this, and it was down to the config. Here's a copy of my setup :-

::::::::::::::
hostname.ce0
::::::::::::::
group bsun50-ipmp-grp0
set 148.253.138.36/27 broadcast + -failover standby deprecated up
::::::::::::::
hostname.ce2
::::::::::::::
group bsun50-ipmp-grp0
set 148.253.138.37/27 broadcast + -failover deprecated up
addif bsun50/27 broadcast +

I dont see any definition of group in your settings. Mind you, IVe seen a ton of different ways of configuring IPMP.

Here are some dos / donts :-

IPMP requires a default gateway to be set. (A remote to ping to ensure things are working)
Clients must connect to the logical interfaces not the physical.
Local mac address must be used. * (# eeprom local-macaddress?=true)
Load balancing is performed on a connection basis not per packet.
When the failover occurs you will see the logical address of the failed card or link appear on the working interface card.
Can be made permanent using /etc/hostname.(networkcardtype+number) e.g. hostname.ce0
*Applications should not bind to the physical IP addresses but use the logcal ip address


There's a comand that allows you to failover the cards, e.g. if_mpadm

# if_mpadm -d ce0 - detaches ce0
# if_mpadm -r ce0 - re-attaches ce0



HTH

SBK

This is how I will prefer. My following example provides failover with 1 public IP. Advantages will be easier debugging, 1 lesser IP used and easier firewalling.

Primary Interface
# cat /etc/hostname.ce0
DUMMY1 netmask + broadcast + group production deprecated -failover up \
addif REALNAME netmask + broadcast + failover up

Standby Interface
# cat /etc/hostname.ce1
DUMMY2 netmask + broadcast + group production deprecated -failover standby up

/etc/hosts file
# Internet host table
#
127.0.0.1 localhost
192.168.1.10 REALNAME loghost
192.168.1.11 DUMMY1
192.168.1.12 DUMMY2

The above sets up two dummy (private) IP addresses that are fixed to the interfaces. It sets up a failover group named production. It adds an IP REALNAME to the group and marks it as the failover IP that will be migrated, and ce1 is set as the standby interface. In most situations, ce0 will be used to transmit and receive packets. In the case of failure (interface, switch, cable, router, etc), the IP for REALNAME will migrate to ce1 interface. When ce0 recovers, the IP will migrate back.

Thanks for the input. I do have my group set up in the config files. It's called netgroup. I will change the configuration slightly and test it that way.

I'm implementing IPMP across all of my test servers at the moment so I can play around with the config a little to get it right before implementing on Prod.

I'm confident that the interface on this server hasn't physically failed. Solaris has just flagged it as failed. There must be some way of changing the flag manually or to get Solaris to probe the interface again?

I have the default router set up etc which is used to check the health of the interface. Basically all I did was unplug the network cable for about two minutes and then plug it back in. Won't be doing that again Still working with the Sun Engineer to resolve that problem. I will post the resolution if i get it.

Thanks.