On Apr 8, 2009, at 7:58 PM, Darren Reed wrote: > On 8/04/09 06:50 PM, Nicolas Droux wrote: >> On Apr 8, 2009, at 3:46 PM, Darren Reed wrote: >> >>> I've filed 6828070 to track this issue... >> >> I don't see a bug here, the virtual switch in MAC is doing its job >> correctly, and IP is doing its own duplication since you have >> plumbed two interfaces on the same subnet in the same IP instances. > > In this case: > ping -s 1.1.1.255 > PING 1.1.1.255: 56 data bytes > 64 bytes from 1.1.1.1: icmp_seq=0. time=1.712 ms > 64 bytes from 1.1.1.2: icmp_seq=0. time=41.451 ms > 64 bytes from 1.1.1.3: icmp_seq=0. time=48.621 ms > 64 bytes from 1.1.1.3: icmp_seq=0. time=133.777 ms > 64 bytes from 1.1.1.1: icmp_seq=0. time=134.181 ms > 64 bytes from 1.1.1.2: icmp_seq=0. time=141.408 ms > > 1.1.1.2 belongs to a zone, test1, that has an exclusive IP instance.
Since you have plumbed the two VNICs on the same subnet in the global zone from which you are sending, IP will send a duplicate of the broadcast ICMP packets through the two ill's corresponding to these VNICs. Because you created both of these VNICs on the same etherstub, and the VNIC of zone test1 is also created on top of the same etherstub, the zone test1 will receive two ICMP requests. If you snoop on the VNIC from the zone test1, you should see two ICMP requests with the same sequence number coming from the two IP addresses you configured in the global zone. If you had only one VNIC per subnet in your global zone, IP wouldn't do the duplication and you would see only one reply per ICMP request for the hosts connected to the virtual switch. Nicolas. > > > Darren > -- Nicolas Droux - Solaris Kernel Networking - Sun Microsystems, Inc. droux at sun.com - http://blogs.sun.com/droux
