So besides the Singlecast/Multicast packet difference, setDestinationAddress() and addUnit() do the same thing?
setDestinationAddress isn't used on the singlecast version; just addunit... . I should probably change setDestinationAddress to addUnit to avoid confusion.
I had originally just written this so I could easily monitor my 5 NV/NV+s and it seems to have grown lately 😛
So besides the Singlecast/Multicast packet difference, setDestinationAddress() and addUnit() do the same thing?
setDestinationAddress isn't used on the singlecast version; just addunit... . I should probably change setDestinationAddress to addUnit to avoid confusion.
I had originally just written this so I could easily monitor my 5 NV/NV+s and it seems to have grown lately 😛
Updated the library, cleaned up code and made the interfaces more consistent. See the top of the thread for the updated link.
So this is probably more down to the weird ways of RAIDar... but see what you think of this...
One NAS, a ReadyNAS Pro, eth0: 192.168.2.5, eth1: 192.168.2.6. Using multicast or unicast, I get (3) found NASes (localhost, .5, .6).------------[/code]
Hmm yeah, some kind of filtering is gonna be best to prevent that. raidard must respond once per interface for some reason.
So this is probably more down to the weird ways of RAIDar... but see what you think of this...
One NAS, a ReadyNAS Pro, eth0: 192.168.2.5, eth1: 192.168.2.6. Using multicast or unicast, I get (3) found NASes (localhost, .5, .6).------------[/code]
Hmm yeah, some kind of filtering is gonna be best to prevent that. raidard must respond once per interface for some reason.
Okay, now it shows two, the localhost entry is gone (I'm running it directly on the NAS).
Each interface is giving back its own MAC address, so I'd say things are good now.
# perl sample.pl addUnit::Adding 192.168.2.5 to Unit List NETGEAR ReadyNAS Status Using UPNP-UNICAST NETGEAR ReadyNAS Perl Communications Library v200904300056
Please Wait... identifyProgram::UPNP-UNICAST NETGEAR ReadyNAS Perl Communications Library v200904300056 identifyProgram:: Verbose: 1 identifyProgram:: Debug Mode: 0 identifyProgram:: Output: console identifyProgram::Socket Timeout: 10 identifyProgram:: Error Timeout: 2 loadReadyNASData::Querying 1 Unit(s) loadReadyNASData::Address List: |192.168.2.5 loadReadyNASData::Processing Address: 192.168.2.5 loadReadyNASData::Building Packet loadReadyNASData::Opening Socket loadReadyNASData::Sending Packet loadReadyNASData::Sent 28 bytes to 192.168.2.5:22081 loadReadyNASData::Receiving Packets loadReadyNASData::0 units processed loadReadyNASData::Read 8562 bytes loadReadyNASData::Processing Data processReadyNASData::Start processReadyNASData::Processing Data Stream processReadyNASData::0: Found Data Record processReadyNASData::1: Adding Data Block to Array processReadyNASData::1: Adding 192.168.2.5 to Unit List processReadyNASData::0: MAC Already Present processReadyNASData::0: MAC Already Present processReadyNASData::0: IP Already Present processReadyNASData::1: Found Data Record processReadyNASData::2: Adding Data Block to Array processReadyNASData::2: Adding 192.168.2.6 to Unit List processReadyNASData::0: MAC Already Present processReadyNASData::Counted 2 Units processReadyNASData::Exit loadReadyNASData::Returning 8552 bytes loadReadyNASData::Exit(8552) Received Data for 2 Unit(s) getUnitData::Start getUnitData::Last Octet is 5 getUnitData::Data Record of 1413 getUnitData::Exit(1413) parseReadyNASData::Start parseReadyNASData::Processing Outer Layer parseReadyNASData::001F33EA0535: Adding MAC parseReadyNASData::001F33EA0535: Adding HOST parseReadyNASData::001F33EA0535: Adding IP Address parseReadyNASData::001F33EA0535: Generating Summaries parseReadyNASData::001F33EA0535: Building Disk List ( 6 Records ) parseReadyNASData::001F33EA0535: Processing System Status parseReadyNASData::001F33EA0535: Generating System Summary parseReadyNASData::Exit(0) Unit #1: Model: ReadyNAS Pro OS: RAIDiator v4.2.5-T16 (Tue Apr 14 17:48:55 2009) Host: pronto IP: 192.168.2.5 MAC: 00:1F:33:EA:00:35 Cooling: 932RPM (OK) System Temp: 60.0C/140.0F (OK) UPS: Not present (NOT_PRESENT) Volumes: Volume C: RAID Level X2, Redundant. 2224897 MB (78%) of 2774 GB used (OK) Disks: 1: 43C/109F (OK); 2: 46C/114F (OK); 3: 44C/111F (OK); present: N/A (NOT_PRESENT); present: N/A (NOT_PRESENT); present: N/A (NOT_PRESENT) Uptime: N/A ------------ getUnitData::Start getUnitData::Last Octet is 6 getUnitData::Data Record of 1413 getUnitData::Exit(1413) parseReadyNASData::Start parseReadyNASData::Processing Outer Layer parseReadyNASData::001F33EA0534: Adding MAC parseReadyNASData::001F33EA0534: Adding HOST parseReadyNASData::001F33EA0534: Adding IP Address parseReadyNASData::001F33EA0534: Generating Summaries parseReadyNASData::001F33EA0534: Building Disk List ( 6 Records ) parseReadyNASData::001F33EA0534: Processing System Status parseReadyNASData::001F33EA0534: Generating System Summary parseReadyNASData::Exit(0) Unit #2: Model: ReadyNAS Pro OS: RAIDiator v4.2.5-T16 (Tue Apr 14 17:48:55 2009) Host: pronto IP: 192.168.2.6 MAC: 00:1F:33:EA:00:34 Cooling: 932RPM (OK) System Temp: 60.0C/140.0F (OK) UPS: Not present (NOT_PRESENT) Volumes: Volume C: RAID Level X2, Redundant. 2224897 MB (78%) of 2774 GB used (OK) Disks: 1: 43C/109F (OK); 2: 46C/114F (OK); 3: 44C/111F (OK); present: N/A (NOT_PRESENT); present: N/A (NOT_PRESENT); present: N/A (NOT_PRESENT) Uptime: N/A ------------
Okay, now it shows two, the localhost entry is gone (I'm running it directly on the NAS).
Each interface is giving back its own MAC address, so I'd say things are good now.
Could perhaps put an option in to filter out duplicate hostnames. I think I'll do that just so it's there.
I'd actually like to request some additional information be added to the RAIDar daemon, specifically system uptime. 🙂 ( Yeah I know the answer is probably no but I gotta try 😛 )
Okay, now it shows two, the localhost entry is gone (I'm running it directly on the NAS).
Each interface is giving back its own MAC address, so I'd say things are good now.
Could perhaps put an option in to filter out duplicate hostnames. I think I'll do that just so it's there.
I'd actually like to request some additional information be added to the RAIDar daemon, specifically system uptime. 🙂 ( Yeah I know the answer is probably no but I gotta try 😛 )
Filter duplicate hostnames feature added, link updated.
Thanks for the SNMP addition on this. It works great across network segments.
One comment on the note in sample.pl "SNMP (TCP)". SNMP by default uses UDP, as does the perl Net::SNMP module. here is an excerpt from the CPAN page on the SNMP module:
The Net::SNMP module uses UDP/IPv4 as the default Transport Domain to exchange SNMP messages between the local and remote devices. The module also supports UDP/IPv6, TCP/IPv4, and TCP/IPv6 as alternative Transport Domains. The -domain argument can be used to change the Transport Domain by setting the value to one of the following strings: 'udp6', 'udp/ipv6'; 'tcp', 'tcp4', 'tcp/ipv4'; 'tcp6', or 'tcp/ipv6'. The -domain argument also accepts the strings 'udp', 'udp4', or 'udp/ipv4' which correspond to the default Transport Domain of UDP/IPv4.
Thanks for the SNMP addition on this. It works great across network segments.
One comment on the note in sample.pl "SNMP (TCP)". SNMP by default uses UDP, as does the perl Net::SNMP module. here is an excerpt from the CPAN page on the SNMP module:
The Net::SNMP module uses UDP/IPv4 as the default Transport Domain to exchange SNMP messages between the local and remote devices. The module also supports UDP/IPv6, TCP/IPv4, and TCP/IPv6 as alternative Transport Domains. The -domain argument can be used to change the Transport Domain by setting the value to one of the following strings: 'udp6', 'udp/ipv6'; 'tcp', 'tcp4', 'tcp/ipv4'; 'tcp6', or 'tcp/ipv6'. The -domain argument also accepts the strings 'udp', 'udp4', or 'udp/ipv4' which correspond to the default Transport Domain of UDP/IPv4.
On my LAN here, with 14 ReadyNAS's, the script takes forever it seems. Where RAIDar gets data and reports then all there within 10 seconds, your script takes 3m25.605s to do the same output.
It receives a packet from one system, then: receiveUDPPackets::Waiting for Timeout or New Data (up to 5 second(s)) Few seconds later, another packet, and that timeout again...
Was going to PM you the output, but "Your message contains 221799 characters. The maximum number of allowed characters is 60000." heh. I'll send you a URL with the output instead.
Webstats PL isn't filling in the HREF clickable admin links for me, using latest version from your webpage.
<a href=http:///admin>QA-NV</a>
Something on your network isn't providing reverse DNS lookups for your ReadyNAS unit(s). I'll look to see if there's another way to do it as a fallback.
