AIX

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.

You might want to read this for help on configuring LHEAs. IMHO you should go for SEAs instead because these are more high-availability.

Anyhow, the "ugly names" you belittle are location codes. You can deduct from the location code exactly where a (physical) adapter has been placed and of which type it is. This information is much more valuable when you have a big system with several CECs and dozens of adapters and you want to replace one of these than the "Broadcom blabla" would be. It is really not IBMs fault that you seemingly have never had to administrate anything even midrange-sized, let alone the bigger irons.

You might have a very small system but it is built (and works) the same way as the dozen or so p780s that populate our data center. To work with a system that houses 50 LPARs with ease you need other methods than when you work with some PC. ESX basically run on PC hardware, somewhat rugged ip to be data center-ready. AIX does not. AIX runs on systems far bigger in every respect than any PC. Just have a look at the p780 and p870 datasheets to find out just how big these systems can get.

You might find the methods employed overly complicated but i can tell you from years-long experience that they are perfectly reasonable in an enterprise-level context. I suggest you either start using these methods and exploit the advantages they offer or you return to administrating your ESXi- or whatever virtualisation-platform you prefer.

I hope this helps.

bakunin

As bakunin said, SEA - Shared Ethernet Adapters - are the way to go in an n+1 VIO environment for your client LPAR network availability.

Of course each VIO should also have n+1, like etherchannel.

Dual VIO allows for rolling, concurrent, upgrades to the VIO servers...

This is obviously a big step for you in the world of IT virtualisation, you are moving into a very different class so don't try and dumb it down to terms and other technologies you are familiar with.

You need to do the homework if you are going to get anything like the best out of this experience and the same applies for your companies investment in this kit.