To resolve the issue, manually assign unique MAC addresses to each adapter.
Sample output:
# ifconfig -a
hme0: flags=1000843 <BROADCAST,RUNNING,MULTICAST,IPV4> mtu 1500 index 2
inet 10.20.30.40 netmask 0
ether 8:0:20:f7:c3:f
hme1: flags=1000842 <BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 8
inet 0.0.0.0 netmask 0
ether 8:0:20:f7:c3:f
hme0: flags=1000843 <BROADCAST,RUNNING,MULTICAST,IPV4> mtu 1500 index 2
inet 10.20.30.40 netmask 0
ether 8:0:20:f7:c3:f
hme1: flags=1000842 <BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 8
inet 0.0.0.0 netmask 0
ether 8:0:20:f7:c3:f
The "ether" line displays the adapter's MAC address. If any interfaces are showing identical MAC addresses and connected to the same subnet, new unique MAC addresses must be set manually.
Run the following command:
# ifconfig <interface> ether <new MAC address>
Although the chance of a MAC address conflict is extremely small, you should verify that there none by using the snoop command to search for the chosen MAC address. Then use the ping command to test connection to the broadcast address of the subnet.
Note: On Solaris systems with multiple interfaces on the same subnet, the operating system may route packets through any of the interfaces. Because of this, any Firewall Stateful Configuration options or Intrusion Prevention Rules should be applied to all interfaces equally.