Thanks for the info you provided, but I am still unable to root cause
and need additional information. I suspect either of the following:
1) A FW bug that we have seen in the recent past that affected the
communication between the Guest domain and Control domain.
If this fails, then Guest domain to External network communication
will also fail.
I have not seen info whether you were able to ping the Guest domain
from the Control domain. Please let us know if you can ping from
the control domain with the IP address of vnet1 in the guest domain.
During this if you can snoop, that will help.
If the ping from control domain is not working, then I suspect it is
the FW issue(CR 6725223). To confirm this, we may need additional
data by running the following command on both control domain and
guest domain:
#!/bin/sh
mdb -k <<END
::ldcinfo !grep net
$q
END
BTW, this FW bug has been fixed in the following FW releases, you
can choose to update the compatible FW and see if the problem is
resolved.
7.1.6.d, 7.1.5.c, and 7.1.4.g.
2) If the communication between the guest domain and control domain works
fine, then this could be a different problem. In that case, please
send the
info that you see with the following command:
kstat -p vsw
-Raghuram.
Glen Gunselman wrote:
>>> Thanks, I'll give up on trying to set the mac
>>>
>> address.
>>
>>> As far as ping goes, I see the same pattern when
>>>
>> pinging from nnn.nnn.nnn.209:
>>
>>> ping to nnn.nnn.nnn.129 (to the control domain
>>>
>> works)
>>
>>> ping to nnn.nnn.nnn.149 (to the guest fails)
>>>
>>>
>> I was looking for another data point, that is guest
>> domain from control
>> domain.
>>
>>> snoop -Vd vnet0 shows:
>>>
>>>
>> Is the vnet0 interface is the one that is failing? I
>> thought you
>> had two interfaces, in that vnet1 was failing.
>>
>>> 164.113.110.149 -> (broadcast) ETHER Type=0806
>>>
>> (ARP), size = 42 bytes
>>
>>> 164.113.110.149 -> (broadcast) ARP C Who is
>>>
>> 164.113.110.150, 164.113.110.150 ?
>>
>>> ________________________________
>>> 164.113.110.131 -> (broadcast) ETHER Type=0806
>>>
>> (ARP), size = 60 bytes
>>
>>> 164.113.110.131 -> (broadcast) ARP C Who is
>>>
>> 164.113.110.131, 164.113.110.131 ?
>>
>>>
>>>
>> Please explain why we are seeing two IP addresses, is
>> there
>> another logical interface plumbed on vnet0?
>>
>> So, we are seeing only outbound packets no input
>> packets. To confirm
>> this, please run the following command in the guest
>> domain and let me now.
>> Please also let us know the FW version you are using,
>> you can get the FW
>> info from SP by running "showhost" command.
>>
>>
>> kstat -p vnet:*:*:*packets
>>
>> -Raghuram.
>>
>
> Sorry, finger check, the output is from snoop -Vd vnet1.
>
>
> -> show /HOST
>
> /HOST
> Targets:
> bootmode
> diag
>
> Properties:
> autorestart = reset
> autorunonerror = false
> hypervisor_version = Hypervisor 1.6.0.b 2008/03/01 01:47
> macaddress = 00:21:28:01:5e:98
> obp_version = OBP 4.28.0 2008/01/22 21:10
> post_version = POST 4.28.0 2008/01/22 21:38
>
> send_break_action = (none)
> status = Solaris running
> sysfw_version = Sun System Firmware 7.1.0.g 2008/04/03 19:35
>
> kstat -p vnet:*:*:*packets
> vnet:0:mac:ipackets 3763
> vnet:0:mac:opackets 61
> vnet:0:vnet0:ipackets 3763
> vnet:0:vnet0:opackets 61
> vnet:0:vnetldc0x0:ipackets 3763
> vnet:0:vnetldc0x0:opackets 61
> vnet:1:mac:ipackets 96
> vnet:1:mac:opackets 5031
> vnet:1:vnet1:ipackets 96
> vnet:1:vnet1:opackets 5031
> vnet:1:vnetldc0x1:ipackets 96
> vnet:1:vnetldc0x1:opackets 5031
>
> Glen
> --
> This message posted from opensolaris.org
> _______________________________________________
> ldoms-discuss mailing list
> ldoms-discuss at opensolaris.org
> http://mail.opensolaris.org/mailman/listinfo/ldoms-discuss
>
