Well, harrumph indeed. Would be nice if hyperswapping didn't require a
non-vswitch'd Linux!
Mark, that was my instinct too, but it doesn't appear to be working - note the
RX packets = 0 on the vlan755 device.
ifconfig
bond0 Link encap:Ethernet HWaddr 02:00:00:00:00:41
inet6 addr: fe80::ff:fe00:41/64 Scope:Link
UP BROADCAST RUNNING MASTER MULTICAST MTU:1500 Metric:1
RX packets:23497 errors:0 dropped:0 overruns:0 frame:0
TX packets:15896 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:2729220 (2.6 Mb) TX bytes:3601718 (3.4 Mb)
eth0 Link encap:Ethernet HWaddr 02:00:00:00:00:41
UP BROADCAST RUNNING SLAVE MULTICAST MTU:1500 Metric:1
RX packets:17301 errors:0 dropped:0 overruns:0 frame:0
TX packets:15880 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:2420206 (2.3 Mb) TX bytes:3600454 (3.4 Mb)
eth1 Link encap:Ethernet HWaddr 02:00:00:00:00:41
UP BROADCAST RUNNING SLAVE MULTICAST MTU:1500 Metric:1
RX packets:6196 errors:0 dropped:0 overruns:0 frame:0
TX packets:16 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:309014 (301.7 Kb) TX bytes:1264 (1.2 Kb)
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:4036 errors:0 dropped:0 overruns:0 frame:0
TX packets:4036 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:443889 (433.4 Kb) TX bytes:443889 (433.4 Kb)
vlan755 Link encap:Ethernet HWaddr 02:00:00:00:00:41
inet addr:10.93.27.250 Bcast:10.93.27.255 Mask:255.255.255.0
inet6 addr: fe80::ff:fe00:41/64 Scope:Link
UP BROADCAST RUNNING MASTER MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:164 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
Marcy
This message may contain confidential and/or privileged information. If you are
not the addressee or authorized to receive this for the addressee, you must not
use, copy, disclose, or take any action based on this message or any
information herein. If you have received this message in error, please advise
the sender immediately by reply e-mail and delete this message. Thank you for
your cooperation.
-----Original Message-----
From: Linux on 390 Port [mailto:[email protected]] On Behalf Of Alan
Altmark
Sent: Tuesday, March 29, 2011 9:23 AM
To: [email protected]
Subject: Re: [LINUX-390] VLAN tagging and Channel Bonding with Linux
On Tuesday, 03/29/2011 at 12:07 EDT, Marcy Cortes
<[email protected]> wrote:
> (and no, don't say use a vswitch - believe me - I'd love to, but not
allowed
> for this !)
"Use a VSWITCH anyway." Ha! There. I said it. ("Not allowed."
Harrumph.)
According to an article I read, VLAN tags are applied to the bonding
interface. (Google vlan channel bonding.) Be sure that the only VLANs
authorized on the trunk are those needed by Linux, as there are no
controls in the OSA firmware to restrict VLAN usage. And if necessary,
turn off Ip forwarding.
Alan Altmark
z/VM and Linux on System z Consultant
IBM System Lab Services and Training
ibm.com/systems/services/labservices
office: 607.429.3323
mobile; 607.321.7556
[email protected]
IBM Endicott
----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
----------------------------------------------------------------------
For more information on Linux on System z, visit
http://wiki.linuxvm.org/
----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
----------------------------------------------------------------------
For more information on Linux on System z, visit
http://wiki.linuxvm.org/
