Solaris

Disappearing when not used is an arp cache feature, in case you are changing NICs on an host. I think 5 minutes is pretty usual, esp for Windows. This makes things tricky/slow if you design a failover that puts a new MAC on an IP.

If you pull the cable on the first NIC, does it move over gracefully?

If you provide saturating load, does it ever use the other NICs?

Ok, that makes sense, so maybe that is only happening since the traffic is only going out of e1000g0. Thanks for that. So now I need to figure out how to make the traffic from each NIC go out of it directly.


I am not physically where the machine is so I simulated this by shutting down the switch port to which e1000g0 is connected and the machine loses connection to the internet. I am unable to then receive any ping response from any of the other interfaces, although doing a packet capture on the other interfaces I can see the "ping request" come in. The same applies to when I try to ping out of any specific interface, it fails as I'm suspecting the pings try to get out of e1000g0 but it's shutdown.


I don't know how to simulate that

Network link saturation is usually 2-3 big file transfers, unless the disk is slower (first cat the file to dev null to get it in cache?).

It seems like the load balancing originally set up was linked to the old IP addresses, and you need to redo whatever that was. This looks applicable: http://download.oracle.com/docs/cd/E...22a/index.html

What does routeadm show?

I see...those will have to be really large files(?) to saturate these GigE links?

The weird thing is that this machine has moved 2-3 times already and have had to change IPs on it every single time and the last time I did it, everything went smooth and was a non-issue. This time, I did the same thing but am faced with this issue and I don't remember doing anything special. I just assumed that when the interfaces are connected to the network directly, they pass traffic directly

You're right, this DOES look relevant. Unfortunately this is a restricted version of Solaris delivered by the vendor of this appliance and does not have svcadm or routeadm as commands. Maybe I'll have to see if I can find them on the net somewhere but finding anything for Solaris-8 is becoming harder and harder.

So now I have to figure out how to do what this article says without the svcadm or routeadm commands. I know there's a file that stores the ip forwarding info etc. Can't remember which one, also ndd might help?

Maybe you can find hints in open solaris source code.

Big enough files so the first is still moving when the others start moving. Content is not important, but no compression on the sending tool.