• Add a Comment
  • Edit
  • More Actions v
  • Quarantine this Entry

Comments (9)

1 AnthonyEnglish commented Permalink

Excellent troubleshooting, Chris. I've seen VLAN tagging set up via IVM before, but given that it can only be done on the command line and the sheer complexity of it, I wonder whether they'd be better to have an HMC or SDMC anyway. Much as I love the command line, many users just want a simple solution that they can manage, or at least view, by themselves via a browser. <div>&nbsp;</div> If your only connection to the IVM is via the same adapter used for the SEA, it's pretty challenging to set up.

2 cggibbo commented Permalink

One point I did not make in this post: I performed all of these tasks from the blade center console terminal session. Given that I was removing the active network interface from the VIOS, I was unable to perform the changes using an SSH session to a network interface that I needed to remove!

3 Teguh Budiman commented Permalink

Hi chris and friend, <div>&nbsp;</div> I try to create SEA on blade system but always fail. <br /> the example flow is like this <br /> LHEA adapter ent0 <br /> LHEA adapter ent1 <div>&nbsp;</div> create etherchannel from ent0 and ent1-&gt; ent2 <div>&nbsp;</div> create virtual adapter -&gt; ent3 (add vlan id) <div>&nbsp;</div> create SEA adapter -&gt; ent4 <div>&nbsp;</div> please advice... thx so much :)

4 SEYY_Babu_Chunduri commented Permalink

Chris, I had issues configuring VLAN into the client partitions on an existing setup and I got the clue only after going through this blog where I was going wrong. The solution is bit tricky and strong to the problem of partition unable to communicate the VIOS on the same subnet. This caused us to think if there is an issue with the DLPAR capabilities and tried to play with RMC stuff, also we suspected vlan tagging on the network switches might have went wrong. <div>&nbsp;</div> Lastly, the trick was applied and all started working well. Thanks a lot for sharing this quality piece of information.

5 MVF0_Vladimir_Burlay commented Permalink

Hi Chris, <br /> I have one question in another area vios troubleshouting: <br /> 1. I installed aix on blade p-series <br /> 2. I want to change it to vios, when I try to install vios on this blade, I had error : " i/o hosting requires a hosting partition" <br /> I think partition on blade has some flag with "Aix/linux", how I chage it to "Vios"? <br /> I can't find it in ASMI and other, can you help me? <br /> burlay@i-teco.ru

6 cggibbo commented Permalink

Hi burlay@i-teco.ru, this is could be a hardware/FSP issue. What model blade are you using? Have you logged a hardware call with IBM for this issue?

7 anchinna commented Permalink

Hi burlay@i-teco.ru, Is your query resolved by now? For installing VIOS, the LPAR need to be created with lpar environment as 'vioserver'. (if creating from command line using mksyscfg command, use the option 'lpar_env=vioserver')

8 deonarain commented Permalink

Hello Chris, I have a similar issue on a FLEX p260 node with VIOS and AIX 6.1 LPARs. I do not have FSM nor HMC. I am using IVM. The VIO has to be in VLAN 250 and the LPARs in VLAN 2. I could put the VIO on VLAN 250 but the AIX LPARS in VLAN 2 are not able to communicate through the VIOS to the client's network. Any tips for me. Thanks.

9 Hugo_Lia commented Permalink

Excelent guide for VLANs. <br /> Does anybody have a similar guide for non-VLAN tagging?

Add a Comment Add a Comment