Thanks Liam! It is S10U4 and the work-around from the blog fixed my problem. I unplumbed the physical and gave it's IP to vsw0 and then things worked as expected.
Regards, Vic On 10/20/07, Liam Merwick <Liam.Merwick at sun.com> wrote: > > Hi Vic, > > Vic Engle wrote: > > This is a strange problem. My control domain has e1000g2 configured with IP > > address 10.60.181.11. On the control domain I created a virtual switch > > interface associated with e1000g2 and it is configured with IP address > > 10.60.181.230. I can access the control domain via both interfaces. > > > > So then I created a guest domain and added vnet1 to the guest with vnet1 > > associated with the vsw previously created. Next I jumpstarted the guest > > using this command... > > > > "boot vnet1 - install" > > > > This worked well and now I can access the guest from another host via the > > IP I assigned which is 10.60.181.231. > > > > The problem is that from the control domain I seem to have no IP > > connectivity to the guest even though I know the guest is working normally > > on the network. All 2 IPs are in the same subnet so no routing should be > > required. > > > >>From the control domain I can access the guest only via the vxx on port > >>5000. > > > > Is there any additional configuration needed to make IP between control and > > guest work via the vsw? > > Yes, you need to plumb the vsw. This is documented in the Admin and Beginner > Guides (search for "plumb" - a few different scenarios are listed). > > I'm not sure what OS you are running - if it is S10U4 make sure to check out > http://blogs.sun.com/narayan/entry/configuring_ldoms_vswitch_following_a > (this bug is fixed in OpenSolaris and will be backported to S10) > > -- Liam > > > ------------------------------------------------------------------------ > Liam Merwick | SPARC Platform S/W - Common S/W Eng (Ireland) > Ext. x(70)19038 | Tel. +353-21-4778600 | Mobile. +353-86-8366459 > >
