Do you that list of both IBM and non-IBM products that will never run on 7.2?


-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of rob@xxxxxxxxx
Sent: Wednesday, July 30, 2014 7:14 AM
To: Midrange Systems Technical Discussion
Subject: Re: vlan configuration on Power 8

Perfect explanation, I'm crossing my fingers that it wasn't a typo but in your last paragraph you said "Now in i 7.1"
The reason I am thinking that you really meant 7.2 was because you had just mentioned the 7.1 way of doing it in the previous paragraph.

You know me, I'm all on a gallop for being on the latest release, however, there are a number of products (mostly IBM products that run on IBM i) that will never run on 7.2. And other IBM products that require you be on a later version of their product which is more of a total rip migration version a transition. And, after about a year I am still waiting for IBM to give me the name of one happy customer using the new version on IBM i, who would be willing to talk to me.

Rob Berendt
IBM Certified System Administrator - IBM i 6.1 Group Dekko Dept 1600 Mail to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755

From: DrFranken <midrange@xxxxxxxxxxxx>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Date: 07/30/2014 12:47 AM
Subject: Re: vlan configuration on Power 8
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>

See in-line.....

- Larry "DrFranken" Bolhuis

On 7/30/2014 12:40 AM, rob@xxxxxxxxx wrote:
Actually, if by "native vlan" you mean what is set by
Virtual Ethernet Adapter Properties - vios21
General tab
Port Virtual Ethernet (VLAN ID)
they used 3999 (after getting permission from our lan guy) not 1.

Yep. 3999 eh? So they really don't have a Native Vlan in the switch
config I'm guessing.

But, our lan guy really wants us out of 10.10.1 and on to 10.10.6 anyway
so I will probably end up changing a bunch of IP addresses into that
anyway. Why fight a battle for a short term solution when we should
to something else anyway?


Now, on to the 252 issue...
Assuming that the Virtual Ethernet for VIOS includes 252 and that it's a
valid VLAN in yours switches AND that it's not restricted on the trunk
AND that there is another port on that VLAN with a device to talk to?
Yes, the virtual ethernet for VIOS includes 4, 6, 209 and 252.
Yes, these are valid and have all been blessed by our network guy.
Addresses such as 10.10.4.x, 10.10.6.x, 10.17.4,x, 10.17.6.x, 209 is
252 is Mimix; like 10.10.252.x matches 10.17.252.x. Second octet
indicates city (usually), third octet normally matches vlan.

Didn't quite grasp "AND that there is another port on that VLAN with a
device to talk too?" Like is this some switch setting, a hmc setting,

Just that if you're all alone on vlan 252 you can't get much dialogue
going. :-)

On our old box we had two line descriptions, to two different physical
ports. One ran 10.10.1.x and the other ran Mimix 10.10.252.x. And the
other city was 10.17.6.x and 10.17.252.x for matching stuff.
Does, when I get this working right, this create two 'resources' that I
then associate with two different line descriptions and associate the
interface to the right line description?
Or is it done some how differently? Like multiple vlans on the same
resource/line description?

It Depends.

In i 7.1 yes you need a separate virtual Ethernet for each vlan. Each of
those gets a line description in IBM i. And the appropriate IP
interfaces attached to that line.

Now in i 7.1 you create a virtual Ethernet for ALL vlans. You check the
802.1Q box and then select as you did for VIOS all the vlans you want to
be available to IBM i. Then you create a single Ethernet line
description for that resource. When you add the IP Interfaces there is a
new parm to indicate the VLAN associated with this IP interface. Each
IP interface has a VLAN associated with it.

- DrF

This thread ...


Return to Archive home page | Return to MIDRANGE.COM home page