AIX LPARs, IVM and network segmentation


We have bought a couple of new IBM blades, each blade has two internal ethernet switch and is connected to other switches on the network. Our "friendly communication admins" has segmented the network in multiples VLANs. One of them is the IVM-VIOserver that is in another segment. I meant there's no connection between segments, all ports are closed. I have clear that between the IVM and LPARs there's services like ctrmc but dont know if they, the IVM and LAPRs needs others tcp or udop ports.  ALso, I need multiples services between segments like NFS, SSH, portamp, xwindows are other..
1- Is there any document regarding best practices regarding connectivity between the VIOserver (IVM) and LPARs? Must they be in the same VLAN?
2- Is there any document or best practices regarding  the configuration of internal blade's switches VLANS?
My boss is asking me if it's necesary to have TOO MUCH security inside the blade or not. Take in mind there's only one VIOserver by blade and it's not easy to make changes constantly on it  because a new vlan is added to the blade.[

is my spanish-english clear for you? :-)
Who is Participating?
woolmilkporcConnect With a Mentor Commented:
Hi again,

sorry for the delay (lots of work here, two new machines ...).

Whereas communication between the VIO (IVM) and the Hypervisor is carried out using a network-independent device (the VMC, virtual management channel, ibmvmc0), Dynamic LPAR needs regular TCP/IP communication between IVM and the LPARS, particularly RMC.
So there must be at least one VLAN accessible by all partitions and the VIO/IVM, allowing communication over (at least) RMC port 657.
You might of course want more ports for inter-partition communication, such as ssh and the like.

This should not be a problem, since you have by default four virtual LANs inside a blade and you can create additional ones with an appropriate VLAN ID, if needed.

The LPARs are not aware of VLAN tagging, this is done by the hypervisor.

To bridge the VLAN to the outside world you must avoid the default behaviour of stripping the VLAN tags by the VIO SEA (Use  "mkvdev -vlan ...")

Now you'll just have give your LPARs a virtual adapter connected to the right VLAN.
To change the virtual ethernet adapter of an LPAR it must be down (at least under IVM), so using LPM will not be sufficient.

As for LPM: In order to make LPM work the migrating LPAR's VLAN must of course be bridged to a physical network, and your LAN must be configured so that migrating partitions can continue to communicate with other necessary clients and servers after a migration is completed.

Here are some links for you:

Redpaper about IVM setup:

DeveloperWorks about virtual VLANs:

DeveloperWorks about Blade Networking:

Hope I could give you a bit of help.

sminfoAuthor Commented:
I forgot, besides any explication from you I need, if exists, some documentation of IBM,  to refuse the communication admins regarding if there's not need to exaggerate the creation of VLAns inside the blade or not.
Well, Israel,

I think I'll need some time to understand what you're after.

In the meantime you could read this, maybe it has some info.

The IBM Blade Center JS12/22 Implementation Guide:

I don't have much time at the moment, but I'll be back soon!


sminfoAuthor Commented:
ok wmp, teh fact is the communications admins are always making VLANs on their side, but it means I have to create the same VLAns on the VIOserver. The blades we have are JS43, and I read that to add a new vlan I have to make a live migration to all LPARs to another blade and then maek the change. That's what I see nonfunctional (dont know if it's the word). And in the other side, I have to give them all TCP/UDP ports LPARs and/or VIOserver (IVM) needs to work properly.. It's a really pain i.....
I'll go home now... see you later..
sminfoAuthor Commented:
Good!  wmp..
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.