Still working on it...Now that I think about it, it would best to keep the
cpu/mem, etc at the host level. But is there a way to link these nodes
back to the host?
The next problem I found is monitoring processes on a per node basis.
This too seems to be tied to the host/MACHINE. Is there any way to break
this out or should I look at hacking this up?
Basically we need the nodes grouped by type on the BBDISPLAY. On these
node drill downs, I need to show cpu/mem, swap, procs, etc. I have them
all grouped, just can't get it to display all the tests I need it to.
- Mike
-----Original Message-----
From: owner-bb@bb4.com [mailto:owner-bb@bb4.com] On Behalf Of Mike Smith
Sent: Monday, August 30, 2004 2:09 PM
To: bb@bb4.com
Subject: {bb} Multiple nodes on one host
Hi all,
What's the best way to accomplish this? I've tried everything and can't
get
it to work.
On each of our servers we have multiple nodes plumbed on virtual
interfaces. These nodes are portable and can be moved from host to host.
On
each of these nodes I need to track cpu/mem, processes, etc. I can get the
nodes to track conn, and some ext scripts, but can't get it to display the
local tests. CPU/MEM, etc only shows up for the host that the node lives
on.
Looking at bbinc.sh and bb-cpu.sh it seems that this is a one for one
deal
at the host level. Is there any way to get around it?
In my bb-hosts, I have the following to accommodate the nodes. Am I going
about this wrong?
10.10.10.1 h3.foo.net # LARRD:*
10.10.10.1 h3.foo.net # CLIENT:n01.foo.net NAME:n01.foo.net queue
This seems to give me the CPU/MEM and local tests for h3.foo.net, and on
n01.foo.net in the display server I get : conn, info, lard, queue, &
trends.
Any info would be great.
- Mike
--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=-=
To unsubscribe from this list, or to subscribe to the bb-digest list
send e-mail to mailto:majordomo@bb4.com with unsubscribe bb -and/or-
subscribe bb-digest in the BODY of the message.