The guest-facing side of the VSWITCH does not support LACP.
(Let's avoid terms like port side and trunk side. When a guest is
using a virtual trunk, which side is the trunk side?) LACP is the thing
that lets the host and switch coordinate traffic.
Ok, that's a better terminology, guest-facing
For who have DIRMAINT enabled and properly configured (file EXTENT CONTROL,
at least), the steps 1-5, 7 and 9 can be substituted by a unique command:
DIRM CMD (ChangeMDisk).
The step 6 can be started as a batch of commands, using several CMD
commands; see DIRM BATCH.
Full packs can be managed the
To avoid this risk doesn't put all these disks on SYSTEM CONFIG.
If you need repeated volsers, is secure to use fullpack dasd defined as
MDISK ... DEVNO. VM mounts them only when necessary and volser doesn't
matter
I know a VM system that process many Disaster Recovery tests
simultaneously,
Martin, Terry R. (CMS/CTR) (CTR) wrote:
Hi
I am looking into XIP and I am wondering someone can share their
experiences in terms of setting up XIP and actually running with it.
Also does RedHat 4.6 support XIP?
Thanks,
Terry
Check out How to use Execute-in-Place Technology with Linux
The reasons Alan lists are the reasons we went LACP. With Guest Lan, we
were lighting up 4 osa ports. We were concerned about sending all the
traffic over 1. And OSA failures (and they do fail) result in a pause
to switch over to the backup vswitch port. We have an app that doesn't
like tiny
On 1/22/2009 at 6:09 PM, Harder, Pieter pieter.har...@brabantwater.nl
wrote:
-snip-
That is strange. Mode 1 is active-backup, where by definition only one nic is
active.
That was a typo on my part. I meant I tried both mode 0 and mode 2. Again,
the results were outgoing traffic was
On 1/22/2009 at 6:51 PM, Alan Altmark alan_altm...@us.ibm.com wrote:
-snip-
While you can have multiple vNICs on an aggregating VSWITCH, there's
nothing that will spray/deal queued frames across the vNICs since they
each have a unique MAC address.
When the bonded NIC starts up, both of the
Right,
And not sure if it would help Pieter's problem anyway:
# ifconfig
bond0 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
On 1/23/2009 at 10:59 AM, Marcy Cortes marcy.d.cor...@wellsfargo.com
wrote:
Right,
And not sure if it would help Pieter's problem anyway:
It didn't seem to, no.
-snip-
Given the counts, it seems to greatly favor one over the other (this one
is sles 10 sp2)
That looks more like mode 1
For comparison have a look at cp q nic details and note the difference between
Adapter MAC and Unicast MAC
Anyway, I have set up a production test for tonight that will transfer on the
order of 2-3 TB with about 100 clients. We'll see what will happen there both
balance and performance
Tuning WebSphere Application Server Cluster with Caching
The paper is available at:
TecDocs:
http://www-03.ibm.com/support/techdocs/atsmastr.nsf/WebIndex/WP101406
developerWorks:
http://www-128.ibm.com/developerworks/linux/linux390/perf/tuning_pap_websphere.html#wascc
This paper
On 1/22/09 4:38 PM, John Summerfield wrote:
Larry Ploetz wrote:
Scott Rohling _/*DID NOT*/_ wrote:
If I must configure bind, maybe I need a text editor. If I can use a
text editor maybe I can edit /etc/sudoers
I said that
That's what sudoedit (not visudoers!) is for.
The point is that I
Oh, you are right! (as usual :)
# cat /proc/net/bonding/bond0
Ethernet Channel Bonding Driver: v3.0.3 (March 23, 2006)
Bonding Mode: fault-tolerance (active-backup)
Primary Slave: None
Currently Active Slave: eth0
MII Status: up
MII Polling Interval (ms): 1
Up Delay (ms): 0
Down Delay (ms): 0
On 1/23/2009 at 11:32 AM, Marcy Cortes marcy.d.cor...@wellsfargo.com
wrote:
-snip-
Now... To figure out how to try the balanced mode.
I put options bonding mode=? in /etc/modprobe.conf.local for my testing. Be
careful, though. Some of the examples I ran across on the 'net showed this
Thanks! Saves me some looking (and finding the stuff that doesn't work
:)
I'm going to consult with my network guy and see which he advises for
our case.
Marcy
This message may contain confidential and/or privileged information. If
you are not the addressee or authorized to receive this for
On Friday, 01/23/2009 at 10:54 EST, Mark Post mp...@novell.com wrote:
On 1/22/2009 at 6:51 PM, Alan Altmark alan_altm...@us.ibm.com
wrote:
-snip-
While you can have multiple vNICs on an aggregating VSWITCH, there's
nothing that will spray/deal queued frames across the vNICs since they
On 1/23/2009 at 1:24 PM, Alan Altmark alan_altm...@us.ibm.com wrote:
On Friday, 01/23/2009 at 10:54 EST, Mark Post mp...@novell.com wrote:
-snip-
When the bonded NIC starts up, both of the slave's MAC addresses are set
to be
the same. So, they're not unique.
Then this must be a Layer 3
On Friday, 01/23/2009 at 01:30 EST, Mark Post mp...@novell.com wrote:
Then this must be a Layer 3 VSWITCH where we don't care about or use
guest
MACs. A Layer 2 VSWITCH (required for LACP) enforces unique MACs.
Nope, it's Layer 2. If I tried to use a Layer 3, it didn't work. (It
would
John Summerfield wrote:
Hugo Luis Vitelli wrote:
Excuse David .. if I do not speak well ... the truth is that I have to
install a zVM in Suse Linux 5.3 and wanted to consult because they have
more experience if I could show the best way to configure the file
system,
if I install in a disk or
On Friday, 01/23/2009 at 07:58 EST, Clovis Pereira gclo...@br.ibm.com
wrote:
To avoid this risk doesn't put all these disks on SYSTEM CONFIG.
If you need repeated volsers, is secure to use fullpack dasd defined as
MDISK ... DEVNO. VM mounts them only when necessary and volser doesn't
matter
Alan wrote:
Iffen I had my druthers, I'druther SYSTEM CONFIG allowed volumes to be
specified by device address instead of, or in addition to, volser.
Ewww. That'd suck for disaster recovery and PPRC Hyperswap.
:)
Marcy
--
Iffen I had my druthers, I'druther SYSTEM CONFIG allowed volumes to
be specified by device address instead of, or inaddition to,
volser.
Alan,
I see your point, but many would have an issue with that approach - many
DR scenarios would be at risk.
Pat
On Friday, 01/23/2009 at 03:23 EST, Marcy Cortes
marcy.d.cor...@wellsfargo.com wrote:
Alan wrote:
Iffen I had my druthers, I'druther SYSTEM CONFIG allowed volumes to be
specified by device address instead of, or in addition to, volser.
Ewww. That'd suck for disaster recovery and PPRC
And if I remember correctly, when Mark joined Novell, we had this little 2 GB
memory problem in VM. That would force many large zLinux shops to have
production running in LPARs. They could still leave test and smaller zLinux
images under z/VM.
But the 2 GB line is no longer much of a
Alan Altmark wrote:
Convenience and Security are rarely bedfellows. Hopefully you use a
different system ID when you're in DR. Use it to qualify the
OFFLINE/ONLINE_AT_IPL so that you get the correct address range
depending
whether you are at home or abroad.
I've seen a number of posts, either
I had reset values using ulimit command:
ulimit -n 4096
ulimit -u 4096
ulimit - s 10240
Then issued ulimit -a to verify the new values were set
After rebooting the server - whoops the values are gone!
How should I properly set ulimit values more permanently?
Do I need to update
On Tue, Jan 13, 2009 at 12:46:08PM -0600, Adam Thornton wrote:
On Jan 13, 2009, at 12:16 PM, Mark Post wrote:
On 1/13/2009 at 1:00 PM, David L. Craig d...@radix.net wrote:
I curate a museum which includes a uni-CP Multiprise 3000
-snip-
Do current distros still support this
platform or
We currently do not change system id's.
We do however have different IP addresses at DR now - that's fun.
Don't know the network folks's latest plans. Always changing.
They don't consider the impacts to the zVM and zOS support folks who
have to make it work.
-Original Message-
From:
On 1/23/2009 at 4:30 PM, Smith, Ann (ISD, IT) ann.sm...@thehartford.com
wrote:
-snip-
How should I properly set ulimit values more permanently?
Do I need to update /etc/security/limits.conf ?
Yes.
Mark Post
--
For
On 1/23/2009 at 4:48 PM, David L. Craig d...@radix.net wrote:
-snip-
Sigh... We're running VM/ESA 2.2 which means CP doesn't
know about the IEEE floating point hardware. As I see it,
we can upgrade VM, tell the kernel to use emulation even
though the hardware is there, or put Debian (and
Thanks Shawn
-Original Message-
From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of
Shawn Wells
Sent: Friday, January 23, 2009 10:25 AM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: XIP (Execute In Place) for z/Linux running with RedHat 4.6
Martin, Terry R. (CMS/CTR) (CTR)
On Friday, 01/23/2009 at 03:56 EST, O'Brien, Dennis L
Dennis.L.O'br...@bankofamerica.com wrote:
I've seen a number of posts, either here or on IBMVM, that suggest
changing system ID's for DR. We don't do that. We have 18 VM systems.
They're all somewhat different, or we wouldn't have that
A mystery indeed. As Pieter suggested, seeing the output of QUERY NIC
DETAILS would be edifying.
Here is the answer on my system:
TSMSERV:~ # vmcp q nic details
Adapter 0C00.P00 Type: QDIO Name: 0 Devices: 3
MAC: 02-00-00-02-03-96 VSWITCH: SYSTEM QDIOL
RX Packets:
On 1/23/2009 at 1:58 PM, Alan Altmark alan_altm...@us.ibm.com wrote:
-snip-
A mystery indeed. As Pieter suggested, seeing the output of QUERY NIC
DETAILS would be edifying.
s390a13:~ # ifconfig
bond0 Link encap:Ethernet HWaddr 02:00:00:00:00:06
inet addr:10.10.220.13
34 matches
Mail list logo
