Greetings; (Posted to VMESA-L and VSE-L and LINUX-390)
- - Now in its sixth year! - - Includes VSE and linux/390!
I have set up a public service web page at
http://www.eskimo.com/~wix/vm/
for posting positions available and wanted for VM, VSE and linux/390.
Please visit the web
Have you tried OpenNMS? (opennms.org).
David
Ranga Nathan
[EMAIL PROTECTED]To: [EMAIL PROTECTED]
bal.com cc:
Sent by: Linux Subject: Performance Monitoring for
Linux
Thanks. Cacti is an improved version also takes feeds and charts
OpenNMS seems to be equivalent to Nagios which I have installed and am
happy with. Nagios was a bit difficult to implement but the Perl-based
architechture made it easier to trouble-shoot.
__
Another good package which comes with SuSe SLES8 is GNUPLOT.
http://www.gnuplot.info
Regards,
Mike Fry
Capacity Planning SAS Consultant
Performance Capacity Support
ISS/Mainframe Infrastructure, Enable
Tel c/w: 2000 x4813
Tel ext: 01565 614813
Internet communications are not secure and
PLEASE PLEASE be aware that the CPU numbers you get from
ANY linux monitor when under z/VM or VMWARE or any other
virtualization are GROSSLY WRONG when you need them most.
Please see
HTTP://velocitysoftware.com/present/prorate/;
for a better explanation.
I am unaware of any product other than
On Thu, 2004-06-17 at 10:29, Barton Robinson wrote:
I am unaware of any product other than ESALPS on the market
that is either aware of this problem or addresses
it. Linux monitors do NOT have the ability to correct this
problem - they are unaware they are virtualized.
They still have some
Interesting. So it seems that if you want to track CPU and memory
performance you have to do it at the aggregate VM level. That makes it
difficult to size the guests. How does one know how much resource to give
to a guest. I do understand that if the guest is under-performing then you
give it some
Sizing is actually pretty easy. What Barton is getting at is that when
Linux reports performance numbers, it does so on the assumption that it
owns the hardware. When running under VM (or LPAR), it doesn't so you
need something that understands VM's influence and can adjust the
numbers that
On Thu, 2004-06-17 at 12:58, Ranga Nathan wrote:
Interesting. So it seems that if you want to track CPU and memory
performance you have to do it at the aggregate VM level.
Or use Barton's ESALPS product, which is designed to do exactly that.
That makes it
difficult to size the guests. How
We are looking around for some basic VM performance stats.
We tried grabbing the TRACKZVM VMARC file from
http://sinenomine.net/downloads/trackzvm.php
After installing TRACKZVM and running T we get:
Unsupported CP version z/VM Version 4 Release 4.0, service level 0301
(64-bit)
I found some
List Linux Guests
Show Total CPU used %
Show Total Memory used (Real/Paging)
Show CPU Usage of a Linux Guest
Show Memory Usage of a Linux Guest
Show All Disks
Show Disk I/O rate for a given Disk
IMHO, there's two problems here: capacity planning for real resources
(ie making sure you
Anybody heard from the Gentoo guys about their S/390 Port?
--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
See: http://www.linuxplanet.com/linuxplanet/reports/5448/1/
Sigh... we still get references to Linux source code for the OS/390 and ZOS-based
mainframes.
--
For LINUX-390 subscribe / signoff / archive access instructions,
send
I have an existing Linux system (non-VM) running SuSE Enterprise Server 8 in
an LPAR using an IFL. My root file system and swap space are on unit 150e.
I am using LVM to manage two other units 1611, and 1242 and I have /home,
/var/and /opt filesystems mounted on volume group system in my
You mentioned that you added the device before extending your volume, but
did you take any steps to ensure that the new dasd is found when the
machine boots?
I use the 'echo add device range=113e /proc/dasd/device' command to
assign another unit to my system
Normally you would add the new
You didn't indicate that you updated your dasd= parameter in your parmfile
and re-ran zipl. Take a look at this:
http://linuxvm.org/info/howtos/mkinitrd-notes.html
Mark Post
-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of
[EMAIL PROTECTED]
Sent:
That was it. I was really doing two steps.
First, I was adding a new disk to the Linux system, which I failed to do
properly.
And two, I was extending an existing LVM managed filesystems which worked
fine.
I kind of feel like I asked tech support for help and the came by and
plugged in my
17 matches
Mail list logo