Solaris

I think you have active/active, check with

Code:

netstat -i

It can lead to hickups - sudden delay or packet loss.
For active/standby have
hostname.igb1

Code:

group IPMP standby

No second IP-address.

In case you want to go for a symmetric active/active aggregate with LACP (this is not called IPMP by Sun and Oracle):
1. enable LACP on the LAN switch port
2. create an executable script on the local disk

Code:

!/bin/sh

echo "Creating LACP setup"
/usr/sbin/ifconfig bge0 down
/usr/sbin/ifconfig bge0 unplumb
/usr/sbin/ifconfig bge1 unplumb
/usr/sbin/dladm create-aggr -P L3 -l passive -d bge0 -d bge1 1
/usr/sbin/ifconfig aggr1 plumb

mv /etc/hostname.bge0 /etc/hostname.aggr1

The script is for bge0 and bge1; rename them to your NIC drivers.
Run the script from a console (e.g. an ILO board - not over ssh!)
See also https://docs.oracle.com/cd/E25539_01.../cgfcadjd.html
Note they advertise -l active but usually it should be -l passive because the LAN switch is the active part.
Because the aggregated links are hidden, netstat -i 1 shows the sum only, while the per-link packets are shown with dladm show-aggr -s -i 1.

Hi MadeInGermany,

Greatly appreciate the examples.
I am trying to setup ACTIVE,ACTIVE IPMP and do a packet sniff to see what are the actual IPs and mac address being send out of both interfaces... but sadly.. solaris doesn't seems to have wireshark

Regards,
Noobb

Solaris has something better than wireshark... It is called snoop.

Hi DukeNuke2,

Is there anyway i can capture both interfaces at the same time with snoop ?
Been trying but doesn't seems like it.


Look forward to your advice.

Regards,
Noob

Never tried that... You can open multiple snoop sessions and capture the output in multiple terminal sessions...

Hi,

I don't know if you still need more info but I thought I would Chime in as I recently switched from IPMP over to Link-aggr and LACP.

What we found is due the application we were using, Load spreading was not working as expected.

IPMP is supposed to load balance only outbound traffic based on my research. What I found when reviewing dlstats, were only one port was actually being used.
- Due to this our application was impacted. Users reported slow connectivity during peek times. We took a look at the server and there were plenty resources available since this is a new implementation and only one application on the server at the time. The application is network heavy. (IPMP configuration is what was recommended to us. There is a possibility that when it was setup, it was not done correctly).

As Solaris was pretty new to me and I came into the project half way, I suggested switching over to using link aggregation instead. Once switched over, performance has improved from the user experience which was the goal.

Not sure if this helps.
(I'm not a solaris admin but was only helping out to troubleshoot the issues)