01-13-2016
Server inventory software
Hi,
do you know any good server inventory open source products?
I want information like, server hostnames, ram, cpu, os, filesystems, volume groups, disks, adapters, installed software versions, firmware levels and so on
os: aix, solaris, linux, hpux
data should be kept in a database, web front end and history functions would be good
I can load the data directly into the db, something agent based is ok too
thanks in advance
cheers funksen
7 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
How can I find out what software is installed on the machine, other than ls? Is there a registry program like in Windows? The os is Sun 2.5.
Thanks (1 Reply)
Discussion started by: ViperD
1 Replies
2. UNIX for Advanced & Expert Users
how to obtain/ collect a list of all the applications installed in the system.. is there a configuration file(like the one which exists for hardware ) which holds all this information?? if no is there any command/shell script or utility that we can use for the same ??
I am using Red hat linux... (2 Replies)
Discussion started by: superghost
2 Replies
3. UNIX for Dummies Questions & Answers
Hi All,
I am looking for a way to inventory the hardware and software components of many Solaris 8 servers/workstations. I would like to script this to run against a list of IP's in a text file.
For Windows there are many such programs available (like Belarc)
Is there anything similar for... (4 Replies)
Discussion started by: limey
4 Replies
4. Shell Programming and Scripting
Dear Team,
I am very new to shell scripting & and presently monitoring unix boxes
I am looking for a shell script which will give me the below output
script should contain -
hostname,OS Version,CPU details, Physical Memory, Partitions Details, Network Details and Software Installed,... (5 Replies)
Discussion started by: whizkidash
5 Replies
5. UNIX for Advanced & Expert Users
we create a HP-UX software depot with a new perl-modul. after installation of the software depot, the perl module
i can't find with instmodsh in the inventory for installed Perl modules.
- i have learned of using instmodsh command : i find out what modules are already installed on my system.
... (0 Replies)
Discussion started by: bora99
0 Replies
6. Solaris
Hi Experts,
we are planning to upgrade the End of life servers to new servers and from solaris 8/9 to 11. Server loads are minimum and not heavily loaded. After analysis we came to conclusion
to use the below. Can experts out there please let me know whether it make sense or any way we can... (3 Replies)
Discussion started by: sundba
3 Replies
7. Solaris
How can I get the hardware inventory details of the Sun Servers like T5220 running Solaris 10?
I would like to see the following details:
1. Chassis Information - Part Number, Serial Number etc.
2. Slots Present in the chassis
3. Modules/Cards equipped on the slots. Module details like Part... (8 Replies)
Discussion started by: baddy
8 Replies
LEARN ABOUT ULTRIX
tarsets
tarsets(1) General Commands Manual tarsets(1)
Name
tarsets - subset kitting command file generator
Syntax
/usr/sys/dist/tarsets [ -d ] pathname
Arguments
pathname
Specify the root directory for the file hierarchy containing the files to be kitted in the subset.
Description
The command reads subset inventory records from standard input and writes a command procedure to standard output. This command procedure
contains the commands required to create subset images for the subset described in the input.
The command is used by the utility to produce software kits for use with the utility.
All error diagnostics are written to the file stderr in the current directory.
Options
-d Enable debugging. Debug trace diagnostics are written to ts.dbg in the current directory.
Restrictions
The output command procedure produces multiple tar files. Each tar file has a goal size of 400Kb. This is an anachronism from the days of
software distribution on RX50 diskettes. The command procedure is modified automatically to produce a single subset image when is called
from the utility.
Return Values
The exit status from the command is zero unless a hard link referenced in the input inventory cannot be found in the input inventory, in
which case the status is 1.
Diagnostics
Invalid Record on line n
The input record on line n is not in subset inventory format.
path1 -> path2 link reference unresolved.
The input record for path1 contains a pointer to path2 in the referent field and path2 does not appear in the inventory. This indi-
cates that path2 was deleted from the inventory after being created by the invcutter command.
Warning: file filename is n blocks too large for diskette
This is an obsolete message. It can be ignored.
Writing Oversized File Volume...
This is an obsolete message. It can be ignored.
i Blocks, j Chars on Volume k
This is an informational message. The number j is the number of characters in the command written to the output to produce volume k.
Files
stderr Diagnostic output.
ts.dbg Debug diagnostic output.
See Also
invcutter(1), kits(1), stl_inv(5), setld(8)
Guide to Preparing Software for Distribution on ULTRIX Systems
tarsets(1)