Not "obviously not". :-)
The first time a VNIC talks to a particular destination MAC, an OSA is
selected and bound. All subsequent communication by that same VNIC with
that same MAC will use the same OSA. If the OSAs become sufficiently
unbalanaced, then a new OSA is selected and the VNIC traff
On Tuesday, 11/20/2007 at 01:02 EST, Pieter Harder
<[EMAIL PROTECTED]> wrote:
> To be more precise: I am looking for some guidelines what to expect for
a
> single Vnic talking to multiple targets. Alan pointed to the z/VM
performance
> documents for general LA performance, but that does not address
To be more precise: I am looking for some guidelines what to expect for a
single Vnic talking to multiple targets. Alan pointed to the z/VM performance
documents for general LA performance, but that does not address what I am
asking for.
Theoretical: when I aggregate 8 10GbE OSA's I have a thr
On Tuesday, 11/20/2007 at 12:32 EST, Bill Bitner <[EMAIL PROTECTED]>
wrote:
> One should not expect Link Aggregation to improve the
> performance of a single Vnic talking to a single target.
> The packets associated with a single conversation (probably
> not the right term) are not shuffled across
One should not expect Link Aggregation to improve the
performance of a single Vnic talking to a single target.
The packets associated with a single conversation (probably
not the right term) are not shuffled across the different
OSAs or spread across them. We do spread different
conversations acros
On Sunday, 11/18/2007 at 01:29 EST, Pieter Harder
<[EMAIL PROTECTED]> wrote:
> I have recently implemented Link Aggregation on my Vswitch. I was
expecting to
> see increased throughput on single Vnic's, but no such thing. Apparently
there
> is another bottleneck that I can't pinpoint yet. I have be
Hello list,
I have recently implemented Link Aggregation on my Vswitch. I was expecting to
see increased throughput on single Vnic's, but no such thing. Apparently there
is another bottleneck that I can't pinpoint yet. I have been looking at it with
IBM PTK but nothing obvious shows. I do have
Well...it may be telling me everything I need to know.but...I don't know if
it is meaningful.
1. Why, on a straight vanilla installation, I would get such an error?
2. Apparently, no one else has gotten this error (no one else chimed in saying
they had it also).
3. When I can't tie down
Tom,
ultimately complaints on how informative SPident is should go to SUSE
(Mark Post?) :-)
Looking at your output it is informing you that Xfree86-Mesa (64 and
32bit) is backlevel. But interestingly on SP1 and SP2, not SP3.
If your installation was followed to the letter of the SUSE docs, then
t
On Wed, 2007-03-14 at 10:42 -0500, Tom Duerbusch wrote:
> Thanks...that was interesting, but seemly useless . Have no idea what it
> is trying to tell me.
Just because you don't understand what it's saying, doesn't mean it's
useless... :)
> Just for kicks, here is the results:
>
> linux40:~ # S
Thanks...that was interesting, but seemly useless . Have no idea what it is
trying to tell me. As this was a fresh install of SLES9 with SP3 with the
default package selection, I would expect no conflicts.
So I expect:
> CONCLUSION: System is NOT up-to-date!
> foundSLES-9-s390x
> expe
Tom Duerbusch wrote:
I just installed SLES9 with SP3 64 bit. But when I do:
linux40:~ # SPident -v
Summary(using 549 packages)
Product/ServicePack conflictmatch update (shipped)
SLES-9-s390x 00%278 50.6% 0 (1555 17.9%)
SLES-9-s390x-SP1
I just installed SLES9 with SP3 64 bit. But when I do:
linux40:~ # SPident -v
Summary(using 549 packages)
Product/ServicePack conflictmatch update (shipped)
SLES-9-s390x 00%278 50.6% 0 (1555 17.9%)
SLES-9-s390x-SP1 2 0.4% 63 11.5
n 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of
> William Dodge
> Sent: Wednesday, January 10, 2007 11:42 AM
> To: LINUX-390@VM.MARIST.EDU
> Subject: SLES9 SP3 install dropping network connection
>
> I am doing a SLES9 SP3 install and when the install gets to the device
> mapper
riginal Message-
> From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of
> William Dodge
> Sent: Wednesday, January 10, 2007 11:42 AM
> To: LINUX-390@VM.MARIST.EDU
> Subject: SLES9 SP3 install dropping network connection
>
> I am doing a SLES9 SP3 install and when t
I am doing a SLES9 SP3 install and when the install gets to the device mapper
package on the SP3 CD1 my guest goes into a serious loop. It starts clocking
serious cpu percentage and through the roof paging then eventually the VNC
client or browser window (I have tried both) gets a network
g on existing SLES9 SP3 with
ECKD/LVM ...
See my previous note on multipath for setting up 2 or more paths to the
same Lun and I/O load balancing.
Using multipath-tools or EVMS will allow you to set more then one path
to a Lun and it will do I/O load balancing. I think I read that it will
monitor
the rpm file on CD1.
What do the multipath-tools buy you?
-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of
Terry Spaulding
Sent: Wednesday, June 07, 2006 7:31 AM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Implementing zFCP & Multipathing on existing SLES9
zFCP & Multipathing on existing SLES9 SP3 with
ECKD/LVM ...
I am trying to implement zFCP Multipathing on SLES9 SP3. This is under
zVM 5.2.
Regards,
Terry L. Spaulding
[EMAIL PROTECTED]
--
For LINUX-390 subscribe / signoff
@VM.MARIST.EDU
Subject: Re: Implementing zFCP & Multipathing on existing SLES9 SP3 with
ECKD/LVM ...
In my case I am using multipath-tools on SLES9 SP3. Is there a .conf for
multipath-tools ?
T
zFCP & Multipathing on existing SLES9 SP3 with
ECKD/LVM ...
I am trying to implement zFCP Multipathing on SLES9 SP3. This is under
zVM 5.2.
The Linux guest is an existing Linux using ECKD disk which also has LVM
non multipathing on the ECKD.
I have no problem adding the zFCP with SCSI Lun. Th
In my case I am using multipath-tools on SLES9 SP3. Is there a .conf for
multipath-tools ?
Terry
--
Arty Replied:
On Tue, 6 Jun 2006 12:33:35 -0400 Terry
On Tue, 6 Jun 2006 12:33:35 -0400 Terry Spaulding said:
>Has anyone been able to have a coexistence with ECKD LVM non Multipathing
>and SCSi with LVM Multipathing ?
We use ECKD (non-LVM) and SCSI (LVM Multipathing) by changing /etc/evms.conf
as follows:
- Under "legacy_devices", remove "dasd?"
I am trying to implement zFCP Multipathing on SLES9 SP3. This is under zVM
5.2.
The Linux guest is an existing Linux using ECKD disk which also has LVM non
multipathing on the ECKD.
I have no problem adding the zFCP with SCSI Lun. The problem is setting the
/etc/lvm/lvm.conf file filter to
On 5/5/06, Mace <[EMAIL PROTECTED]> wrote:
>All went well, but originally when I was in TOP different areas
>highlighted and it made it easier to read. Now all fields are the same.
>What do I need to do to get the fields to highlight again??
>thanks
>Mace
Did you try 'man top' in Linux? It sho
All went well, but originally when I was in TOP different areas
highlighted and it made it easier to read. Now all fields are the same.
What do I need to do to get the fields to highlight again??
thanks
Mace
--
For LINUX-390 su
On 3/22/06, Bruce Hayden <[EMAIL PROTECTED]> wrote:
> What I have found is that the rpm sles-release-9-82.nn.s390(x).rpm is
> on the service pack CD but *not* part of the service applied by YOU.
> If you find that rpm on the Service Pack cd and update it, then the
> output from SPident should indi
What I have found is that the rpm sles-release-9-82.nn.s390(x).rpm is
on the service pack CD but *not* part of the service applied by YOU.
If you find that rpm on the Service Pack cd and update it, then the
output from SPident should indicate you're at SP3 (as long as you're
not missing some other
To: LINUX-390@VM.MARIST.EDU
Subject: Re: SLES9 SP3
No, you won't need to install service packs if you keep your system
updated with YOU.
Mark Post
-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of
Mark D Pace
Sent: Wednesday, March 22, 2006 10:4
No, you won't need to install service packs if you keep your system
updated with YOU.
Mark Post
-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of
Mark D Pace
Sent: Wednesday, March 22, 2006 10:40 AM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: SLES9 SP3
One question regarding Service Packs. If I use YOU to keep my system up to
date, do I need to apply Service Packs? Or does the Service Pack have
more/different patches than the YOU server?
Mark D Pace
Senior Systems Engineer
Mainline Information Systems
1700 Summit Lake Drive
Tallahassee, FL.
Hi,
So it turns out, that if you use the YaST panels to add the zfcp driver,
then it is a simple matter of dropping a bunch of hwcfg configuration files
in /etc/sysconfig/hardware. A simple REXX EXEC makes light work of generating
the hwcfg files (with 8 paths to each LUN!) After a reboot, th
Hi,
I have a need to add a great many FCP LUNs to a SLES9 guest. Under SLES8,
it was a simple /etc/zfcp.conf file. With SLES9, is it more than building a
bunch of /etc/sysconfig/hardware/hwcfg-zfcp-bus-ccw-0.0. files? I'd
really, really, really hate to go through the YaST2 panels to do t
> I don't know how/when this directory has to be created
I believe it is documented in one of the README files on CD1 of SP3. Also,
see chapter 6 of the Virtualization Cookbook
(http://linuxvm.org/present/misc/virt-cookbook-1.pdf). If you have the 6
vanilla SLES9 ISO images and the 3 SP3 ISO im
Hi list -
I just installed Linux SLES9 under z/VM using NFS, then I downloaded
SLES-9-SP-3-s390x-GM-CD1a.iso, CD2, and CD3 from Novell and I put them
under /nfs/SP3 directory to apply SP3 maintenance using YaST2. I specify
NFS as Selected Type of URL, and /nfs/SP3/ as Directory on Server, but I'm
g
Well I should expect, to prevent confusion if this is really and truly your
gold master then the frelling name should reflect it. I don't, as a rule,
install release candidates. Even if the release candiate has been 'declared
gold'. You can declare lots of things. Doesn't make them true. Evidence
On 2/23/06, Ihno Krumreich <[EMAIL PROTECTED]> wrote:
> Yes. But as you said. Its a "Release Candidate" and this release candidate was
> declared gold master.
Considering the track record with SP3, starting with "bronze master"
would have been appropriate ;-)
Rob
---
On Thu, Feb 23, 2006 at 12:08:10PM -0600, James Melin wrote:
> Isn't SLES-9-SP-3-s390-RC4a-CD3.iso indicative of it being a Release
> Candidate and not the final?
>
Yes. But as you said. Its a "Release Candidate" and this release candidate was
declared gold master.
Ihno
> Linux on 390 Port wro
-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Ihno Krumreich
Sent: Thursday, February 23, 2006 10:47 AM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Another Corrected sles9 sp3 CD
On Wed, Feb 22, 2006 at 09:27:25AM -0700, Ledbetter, Scott E wrote:
> I was just downloading these t
On Wed, Feb 22, 2006 at 09:27:25AM -0700, Ledbetter, Scott E wrote:
> It looks to me like the latest SP3 CD images for 64-bit are labeled as
> follows:
>
> SLES-9-SP-3-s390x-GM-CD1a.iso -- e74f074fc81c1d1bb12ff59d9f2541bb
> SLES-9-SP-3-s390x-GM-CD2.iso -- 9ebbd79d41e46ee3c0f0b4e6997f7319
> SLES
Isn't SLES-9-SP-3-s390-RC4a-CD3.iso indicative of it being a Release Candidate
and not the final?
Linux on 390 Port wrote on 02/23/2006 11:46:46 AM:
> On Wed, Feb 22, 2006 at 09:27:25AM -0700, Ledbetter, Scott E wrote:
> > I was just downloading these this morning. It looks to me like the
> >
On Wed, Feb 22, 2006 at 09:27:25AM -0700, Ledbetter, Scott E wrote:
> I was just downloading these this morning. It looks to me like the
> latest SP3 CD images for 64-bit are labeled as follows:
>
>
> SLES-9-SP-3-s390x-GM-CD1a.iso -- e74f074fc81c1d1bb12ff59d9f2541bb
> SLES-9-SP-3-s390x-GM-CD2.i
[mailto:[EMAIL PROTECTED] On Behalf Of
Michael MacIsaac
Sent: Wednesday, February 22, 2006 8:54 AM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Another Corrected sles9 sp3 CD
> Does anyone have any information on the new corrected
> sles9 sp3 CD? I noticed there is a new "corrected"
Someone replied to me off-list that a PMR was opened and a reply from SuSE
was:
The "error" was: the media label which is written into the header part
of the ISO image was wrong, causing CDs burned from it to be
misidentified and YaST not accepting such CD as a SUSE patch CD.
Perhaps th
> Does anyone have any information on the new corrected
> sles9 sp3 CD? I noticed there is a new "corrected" CD1
> labeled CD1a that is now available on the Novell site.
What are the correct file names and md5sums for SLES9 SP3, s390 and s390x?
Can someone from SuSE please clar
Does anyone have any information on the new corrected sles9 sp3 CD? I
noticed
there is a new "corrected" CD1 labeled CD1a that is now available on the
Novell site.
John
--
For LINUX-390 subscribe / signoff / arch
SuSE has release a fix for SPident since SP3 that corrected a problem with
SPident not reporting SP3 correctly. See
http://support.novell.com/cgi-bin/search/searchtid.cgi?/psdb/25cb50c55b835861d91619ec0c9fdd9a.html
Could this be the problem?
Peter
This Email message and any attachment may contain
From the SuSE "Release Notes for SUSE LINUX Enterprise Server 9 for
zSeries and S390 (31bit) Service Pack 3"
SPident Reports the Service Pack Level
SPident is a tool to identify the Service Pack level of the current
installation.
SPident may report that the system has not reached the level of Se
Hi Listserv,
I just did a "Minimum graphical system (without KDE)" install. My
install tree contains the 6 original ISO's and the 3 SP3 iso's ( including
the new CD#2 for SP3 ). When I run SPident -vvv, I get this message:
CONCLUSION: System is NOT up-to-date!
foundSLES-9-s390x
expect
John,
I have installed SLES9-SP3 with the "old" CD2 . I will have to redo
everything with the new CD2 . However, this is what SPident -vvv shows at
our site currently . Is the CONCLUSION at the bottom accurate/correct.
Summary(using 279 packages)
Product/ServicePack
I am wondering if anyone else has had the same problems with the service
pak 3
install. I set up the install tree as is recommended and incorporated the
sp3 CD's
so that when I install sles9 the sp3 patches should be installed at the
same time.
The install completes and there are no errors. When I
Grega Bremec wrote:
> I believe the list of updated packages consists of all of the updates
> between SP2 ISO images and the SP3 release notes links on this page:
>
> http://support.novell.com/linux/psdb/product21.html
>
> It is a cumulative update, the service pack, so there should be care
> taken
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
Brandon Darbro wrote:
| Grega Bremec wrote:
|
|>Neale Ferguson wrote:
|>| See: http://www.linuxtoday.com/infrastructure/2006011301426NWSWSS
|>|
|>| "Novell has released Service Pack 3 for SuSE Enterprise Linux Server
|>9, which includes all s
Grega Bremec wrote:
> Neale Ferguson wrote:
> | See: http://www.linuxtoday.com/infrastructure/2006011301426NWSWSS
> |
> | "Novell has released Service Pack 3 for SuSE Enterprise Linux Server
> 9, which includes all security patches and bugfixes since SP2--of which
> there have been dozens--as w
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
Neale Ferguson wrote:
| See: http://www.linuxtoday.com/infrastructure/2006011301426NWSWSS
|
| "Novell has released Service Pack 3 for SuSE Enterprise Linux Server
9, which includes all security patches and bugfixes since SP2--of which
there
See: http://www.linuxtoday.com/infrastructure/2006011301426NWSWSS
"Novell has released Service Pack 3 for SuSE Enterprise Linux Server 9,
which includes all security patches and bugfixes since SP2--of which there have
been dozens--as well as consolidating driver updates for both storage
56 matches
Mail list logo
