hi again
I think I've found the problem,on VIOS I have 2 virtual ethernet adapters, one set for 'bridged' connections the other not set in this manner.hmc 8.2
vm1 I has two virtual NICs one didn't work ( I'm assuming the one not set to 'bridged' on VIOS profile)
I will re-create one add'l ethernet adapter on Vios, select if for bridged access, and config LPAR #2 to use it..
have to say, I've read a lot of documentation and googled quite a bit about powervm networking.
it's a jungle.it really is confusing.
trying to relate this to the vmware world - in esxi,you go to configuration,and select physical vmnic, and add it to a vswitch(0) by creating a virtual network.it's actually quite easy.same with oracle solaris.the problem ariese with IBM and their convoluted use of the word 'logical'..
in theory, and correct me if I'm wrong, I should be able to use the two existing virtual NICs created on VIOS, the same ones that LPAR1 uses, and use them on LPAR #2,as long as LPAR 2 has two ethernet adapters installed in its profile. so vios doesn't need any add'l ethernet adapters created for a second LPAR. If I have 50 LPARS I need 50 virtual ethernet adapters created on the VIOS server's profile? no way..
it should be the same as putting a virtual machine on vmNetwork1 on VmWare esxi.you add a virtual NIC ( vmxnet3) , assing it to a virtual network.boot the OS, and configure it with DHCP or static IP.thats it.you can have many VMs using the same VNIC and it's related virtual network.same with oracle LDOMS.
I'm trying to put it in the vmware vocabulary so I can better understand it.
IBM PowerVM Design for a VCDX | vcdx133.com
I'm apparently not the only lost soul out when it comes to PowerVM. ;-)
---------- Post updated at 01:22 PM ---------- Previous update was at 10:34 AM ----------
I figured it out,got LPAR #2 on the network, and can see every other server from it.
I see under the LPARs profile, the LHEA lists 4 etities. leave it to IBM to NOT call them NICs or give them names of any sort, like 'broadcom xxxx' , they just leave them as
U7aa.001.wzsg7kk-p1-c3-t1
" " t2
" "t3
" " t4
t1 and t3 were used for and on LPAR 1, but apparently VLANs were set to 'deny all' for this LPAR.
so I just took another NIC, t2, and allowed 'all' through it.