Re: p550 LHEA and port trunking

All,

I found the answer to this.

It is necessary on the AIX partition to set up an ethernet interface of the type vlan to get the packets tagged outbound.

This can be done via smitty vlan

This creates an interface similar to what you see with etherchannel. The ip number then needs assigned to the vlan interface.

S

Shawn Geil wrote:
yeah thats exactly what i've found the documentation is non-existent or still refers to the p5 SEA methods.

I was trying to avoid the support call because that can be a painful experience.

Thanks

S

Mills, John T wrote:
Ahh. You are using VLAN tagging on T1 to support multiple VLANs. Yeah
based on my experience, which is limited, with the IVE impletmentations,
I can see where that may have issues. We aren't using VLAN tagging but
we spent a couple of days going through what limited documentation is
available just to get aggregation working. Sorry I can't be more help.
You may want to engage support on this one. I haven't met very many
people that really understand IVE's restrictions for different
implementations, and, I couldn't find any resource that really explained
the how-to of each scenario.

John T. Mills
-----Original Message-----
From: IBM AIX Discussion List [mailto:aix-l@xxxxxxxxxxxxx] On Behalf Of
Shawn Geil
Sent: Friday, April 03, 2009 11:34 AM
To: aix-l@xxxxxxxxxxxxx
Subject: Re: p550 LHEA and port trunking

What I'm meaning is

LPAR 1 off of T1 in VLAN 1
LAPR 2 off of T1 in VLAN 2
LPAR 3 off of T1 in VLAN 1
LPAR 4 off of T1 in VLAN 6

So T1 is trunked to handle multiple VLANs.


Mills, John T wrote:
I'm not sure I understand the middle sentence, but, we had an initial
issue with trunking on LHEA. The resolution was to allocate both
ports
and EtherChannel all clients that use those ports. Basically:

Before After
Lpar1 T1,T2 2 port agg Lpar1 T1,T2 2 port agg
Lpar2 T1 Lpar2 T1,T2 2 port agg
Lapr3 T2 Lpar3 T1,T2 2 port agg

We haven't had a problem since. Also the factoy enabled promiscuous
on
the "serial number" lpar. We usually just ignore that one and
sometimes
use them in an emegency situation for a full system service partition.
We had to disable the setting to just get started.

John T. Mills

-----Original Message-----
From: IBM AIX Discussion List [mailto:aix-l@xxxxxxxxxxxxx] On Behalf
Of
Shawn Geil
Sent: Friday, April 03, 2009 8:23 AM
To: aix-l@xxxxxxxxxxxxx
Subject: p550 LHEA and port trunking

I have a new p550 that uses LHEA (logical host ethernet adapter) for network connectivity.

I'm having an issue where I can not trunk to a physical port on the adapter to use different VLANs on different LPARs.

The switches are cisco and we are using .1q trunking. Has anyone
tried
this or have any ideas. What happens is the LPAR has no connectivity
to
anything inside or outside its subnet.

S

Relevant Pages

  • Cisco 877w: Fa0-3 Interfaces up but no traffic passes
    ... Data Vlan101 only, no voice vlan required, WPA ... output errors, 0 collisions, 0 interface resets ... switchport trunk native vlan 101 ... bridge-group 101 subscriber-loop-control ...
    (comp.dcom.sys.cisco)
  • Re: Need help adding device to new vlan
    ... The vlan 99 ... - If I assign an ip address to the vlan 199 interface, ... switchport trunk encapsulation dot1q ... switchport trunk allowed vlan 40,51,99,199,997,998 ...
    (comp.dcom.sys.cisco)
  • Re: 2600 router + 2924 switch and vlans
    ... I can route from a port ... assigned to the def vlan, but not from any port assigned to vlan 2 ... interface FastEthernet0/0 ... switchport trunk encapsulation isl ...
    (comp.dcom.sys.cisco)
  • Need help adding device to new vlan
    ... The vlan 99 ... - If I assign an ip address to the vlan 199 interface, ... switchport trunk allowed vlan 40,51,99,199,997,998 ... no ip proxy-arp ...
    (comp.dcom.sys.cisco)
  • Re: kern/109815: wrong interface identifier at pfil_hooks for vlans + if_bridge
    ... It is cleared when an mbuf chain is passed to another entity which may consume the frame in that mbuf chain, in case the entity re-enters ether_inputwith the same mbuf chain for local delivery (e.g. bridge, netgraph, vlan). ... "logical" interface. ...
    (freebsd-net)