> 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
Note: control is still at 164.113.110.129
guest is now at 164.113.110.132
I changed vsw1 to use the mac address of e1000g1
pinging between guest and control is working:
from control
ping 164.113.110.132
164.113.110.132 is alive
from guest
ping 164.113.110.129
164.113.110.129 is alive
However, getting to the outside world (ping, traceroute, nslookup) only works
from control not from the guest.
I do not have time today to update the firmware, but will try that tomorrow.
Thanks,
Glen
>
>
> 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
> esolved.
> 7.1.6.d, 7.1.5.c, and 7.1.4.g.
> the communication between the guest domain and
> control domain works
> fine, then this could be a different problem. In
> that case, please
> end the
> info that you see with the following command:
> kstat -p vsw
> Raghuram.
--
This message posted from opensolaris.org
