Wiggins,
The purpose of my script is to auto discover every system on a network
Stack beginning using tcp/ip protocols and then later using snmp also.
The data I will be collecting is for the sole purpose of gather
information about a site and a site configuration. Similar to tools such as
Veritas SPC (SAN Point Control) does.
Type of data I'm collection is system configuration within a server, a
router, a San switch and then a storage array.
Example: Server:
CPU, speed and number of them
Memory, total
Storage Devices (Internal and external sizes)
NIC, Number of them, speed
HBA's, number of them, speed
Server Functionality (DNS, DHCP, NIS, NIS+, WINS, LDAP,
A/D...etc.)
The above is just a sample of what I'm getting. I'm very much aware of NMAP
And it's capability but it is limiting information. It just isn't networking
Info I'll be after at some stage this will be connected to a SQL database
So the collected data can be use to make some site analysis.
Storage and San information will also be tracked too. This will act as an
Inventory tool also. So with that in mind, Let's keep thing within perl as
I do NOT want to go other outside tools unless they have a perl interface.
Thanks for your help and feedback.
-----Original Message-----
From: Wiggins d'Anconia [mailto:[EMAIL PROTECTED]
Sent: Monday, November 03, 2003 4:54 PM
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: Re: win32 modules
[EMAIL PROTECTED] wrote:
> Hi,
>
>
>
> I've been looking at some perl modules that are win32 based.
>
>
> But what I can't seem to find is something that I can use
>
> based on my earlier scripting requirements.
>
>
>
> So I appreciate any advice from this list as to what I can use
>
> That will remotely go and grab system configurations without
>
> adding any code to those systems being discovered.
>
>
>
> Like to know if anyone has used any of the perl win32 modules
>
> that are listed on cpan in a similar fashion. If so could you please,
>
> share your thoughts.
>
What is your actual goal. The information you were gleaning before is
nice from a reporting standpoint but it doesn't really give any
indication of what you are doing with the information. So what is it
that you are *really* after? There are tools outside of Perl that can
provide reasonably good guesses about remote OSes and in some cases even
versions based on TCP/IP stack fingerprinting, see:
http://www.insecure.org/nmap/index.html
As far as "system configurations" that is a rather vague topic...
http://danconia.org
--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
