AIX

AIX

Connect with fellow AIX users and experts to gain knowledge, share insights, and solve problems.

 View Only
Back to discussions
Expand all | Collapse all

dual-VIOS and SEA (not failover) with trunking -> possible NIB on client?

  • 1.  dual-VIOS and SEA (not failover) with trunking -> possible NIB on client?

    Posted Thu February 09, 2012 07:03 AM

    Originally posted by: tech100


    to be able use/utilize both SEAs at the same time (as opposed to SEA failover where one SEA is backup/stby) I preffere "common" SEA on each VIOS and on NIB on client side.

    but how to hadle such NIB (possible?) in case of VLAN tagging -- many VLANs through SEA? is it feasible or only SEA failover is supported when trunk is enabled and vlans on SEA are created (mkvdev -vlan) on each VIOS?

    I know that for NIB on client we need two vent each one with different internal switch vlan id (one used for sea on vios1 and the other for sea on vios2)...


  • 2.  Re: dual-VIOS and SEA (not failover) with trunking -> possible NIB on client?

    Posted Sat February 11, 2012 02:24 AM

    Originally posted by: SystemAdmin


    You can work with NIB and trunk configurations without problems, all you need to do is create two virtual switch on the server and configure a virtual interface in the profile of virtual I/O adapter as trunk and the other Virtual I/O, you do same but in the second virtual switch for each vlan id added in the trunk must also add from the command line of your virtual i / o with mkvdev -vlan command.


  • 3.  Re: dual-VIOS and SEA (not failover) with trunking -> possible NIB on client?

    Posted Sat February 11, 2012 02:27 PM

    Originally posted by: tech100


    what for the "mkvdev -vlan" is needed for? I have created sea with trunked virtual adapter (with two external vlans) and it was enough to to configure for client LPARs virtual adapters with the vlans Id to get both vlans working on client LPARs. I did not do any "mkvdev -vlan" on VIOS... what for I should do it there? (I don't need to configure

    I also noticed, that if I assigned to client (sic!) LPARs trunked (sic!) virtual adapter with the same internal switch vlan ID and mentioned two additional vlans (the two VLAN IDs which I also configured for virtual ent on VIOS used in SEA config) and then in the system I created two VLAN ents (smitty vlan), they were also working fine and I was able access external networks through real gateway....

    Probably if I would do common SEAs (not failover) and then trunked virtual ents on client lpars (one with vlan id used for vent used for sea on vios1 and the second one with vlan id used for ent used for sea on vios2) and the do "smitty vlan" on each of them creating two vlan ents, then I would be able to create again NIB interfaces using such "OS" vlan ents.


Related Content