« Steve Knudson on NIM | Main | Moving a Filesystem »

September 13, 2011


TrackBack URL for this entry:

Listed below are links to weblogs that reference Higher Availability for VIO Clients: An alternative:


I probably should read the paper first, but in the past, this has had several issues. One is that LPAR's using different primary VIO's have issues communicating. If they do, that traffic is then sent out on the actual backbone, where in a SEA configuration it stays local.

Also, I need to see how the VLAN tagging is slated to work, but that has been always an issue with a NIB configuration.

But I'll read the paper and hopefully stand corrected and then it's lab time... :)

Question: The article states creating a seperate VLAN adapter in each VIOS. What does this accomplish. I typically only create one VLAN adapter for the VLAN that my VIO server address will be on. Is it required in this setup to create a VLAN adapter on the VIOS for each VLAN tagged.

According to Jim Mitchelle (IBM Austin Briefing Centre) at the IBM TopFlight in Johannesburg yesterday, the latest version on VIOS supports an Active-Active SEA configuration between the VIOS.
I have not tested nor found the actual details but definitely on my "to-research" list

Verify your Comment

Previewing your Comment

This is only a preview. Your comment has not yet been posted.

Your comment could not be posted. Error type:
Your comment has been saved. Comments are moderated and will not appear until approved by the author. Post another comment

The letters and numbers you entered did not match the image. Please try again.

As a final step before posting your comment, enter the letters and numbers you see in the image below. This prevents automated programs from posting comments.

Having trouble reading this image? View an alternate.


Post a comment

Comments are moderated, and will not appear until the author has approved them.