Send Netdot-devel mailing list submissions to
[email protected]
To subscribe or unsubscribe via the World Wide Web, visit
https://osl.uoregon.edu/mailman/listinfo/netdot-devel
or, via email, send a message with subject or body 'help' to
[email protected]
You can reach the person managing the list at
[email protected]
When replying, please edit your Subject line so it is more specific
than "Re: Contents of Netdot-devel digest..."
Today's Topics:
1. [Netdot - Bug #1790] FATAL - Could not get a valid iptree4
from cache ([email protected])
2. [Netdot - Bug #1790] FATAL - Could not get a valid iptree4
from cache ([email protected])
3. [Netdot - Bug #1790] FATAL - Could not get a valid iptree4
from cache ([email protected])
4. [Netdot - Feature #1791] (New) Exclude static IP information
from prune_db.pl's IP address pruning ([email protected])
----------------------------------------------------------------------
Message: 1
Date: Tue, 4 Feb 2014 01:27:08 -0800
From: [email protected]
Subject: [Netdot-devel] [Netdot - Bug #1790] FATAL - Could not get a
valid iptree4 from cache
To: [email protected], [email protected]
Message-ID: <[email protected]>
Content-Type: text/plain; charset=utf-8
Issue #1790 has been updated by Matej Vadnjal.
File delete.pl added
Yeah, this is the same bug as I was noticing. You can see that in the frozen
iptree the last byte is 00100000 (or 0x20 or Space in ASCII), but when that
tree is retrieved from the database the last byte is missing.
Here is a workaround script I was using. It will delete an ipblock entry from
the database without updating the iptree. You could use this script to delete a
bunch of entries you don't need. Then try to rebuild the tree and hopefully the
bug will go away.
Run it as perl delete.pl <address>
For a proper fix we'll have to wait for developers to give their opinion. It is
also likely when using Postgres database this bug could not happen.
----------------------------------------
Bug #1790: FATAL - Could not get a valid iptree4 from cache
https://osl.uoregon.edu/redmine/issues/1790#change-3153
Author: Alen F
Status: New
Priority: Urgent
Assignee: Alen F
Category: Netdot
Target version: 1.0.5
Resolution:
Hello,
since Upgrade to 1.5 this error is on add/delete etc.
IP Tree Update not solve the problem.
kind regards
--
You have received this notification because you have either subscribed to it,
or are involved in it.
To change your notification preferences, please click here:
http://osl.uoregon.edu/redmine/my/account
------------------------------
Message: 2
Date: Tue, 4 Feb 2014 01:38:08 -0800
From: [email protected]
Subject: [Netdot-devel] [Netdot - Bug #1790] FATAL - Could not get a
valid iptree4 from cache
To: [email protected], [email protected]
Message-ID: <[email protected]>
Content-Type: text/plain; charset=utf-8
Issue #1790 has been updated by Alen F.
Hello Matej,
follow error occoured after delete.pl
root@netdot:/usr/local/netdot# perl delete.pl "10.43.8.253"
Can't open 10.43.8.253: No such file or directory at delete.pl line 16.
Really delete 10.43.8.253 [y/N] root@netdot:/usr/local/netdot#
thanks for your help
----------------------------------------
Bug #1790: FATAL - Could not get a valid iptree4 from cache
https://osl.uoregon.edu/redmine/issues/1790#change-3154
Author: Alen F
Status: New
Priority: Urgent
Assignee: Alen F
Category: Netdot
Target version: 1.0.5
Resolution:
Hello,
since Upgrade to 1.5 this error is on add/delete etc.
IP Tree Update not solve the problem.
kind regards
--
You have received this notification because you have either subscribed to it,
or are involved in it.
To change your notification preferences, please click here:
http://osl.uoregon.edu/redmine/my/account
------------------------------
Message: 3
Date: Tue, 4 Feb 2014 01:44:49 -0800
From: [email protected]
Subject: [Netdot-devel] [Netdot - Bug #1790] FATAL - Could not get a
valid iptree4 from cache
To: [email protected], [email protected]
Message-ID: <[email protected]>
Content-Type: text/plain; charset=utf-8
Issue #1790 has been updated by Matej Vadnjal.
Ah, sorry.
Replace this line:
<pre>
my $confirm = <>;
</pre>
with:
<pre>
my $confirm = <STDIN>;
</pre>
And it should work.
----------------------------------------
Bug #1790: FATAL - Could not get a valid iptree4 from cache
https://osl.uoregon.edu/redmine/issues/1790#change-3155
Author: Alen F
Status: New
Priority: Urgent
Assignee: Alen F
Category: Netdot
Target version: 1.0.5
Resolution:
Hello,
since Upgrade to 1.5 this error is on add/delete etc.
IP Tree Update not solve the problem.
kind regards
--
You have received this notification because you have either subscribed to it,
or are involved in it.
To change your notification preferences, please click here:
http://osl.uoregon.edu/redmine/my/account
------------------------------
Message: 4
Date: Tue, 4 Feb 2014 10:57:47 -0800
From: [email protected]
Subject: [Netdot-devel] [Netdot - Feature #1791] (New) Exclude static
IP information from prune_db.pl's IP address pruning
To: [email protected], [email protected]
Message-ID: <[email protected]>
Content-Type: text/plain; charset=utf-8
Issue #1791 has been reported by Timothy Snowberger.
----------------------------------------
Feature #1791: Exclude static IP information from prune_db.pl's IP address
pruning
https://osl.uoregon.edu/redmine/issues/1791
Author: Timothy Snowberger
Status: New
Priority: Normal
Assignee:
Category: AddressTracking
Target version:
Resolution:
Currently, prune_db.pl appears to include 'Discovered' and 'Static' IPs as part
of the normal IP pruning process.
Scenario:
Assume you have a routing device which does not report back ARP information,
such as a non-Cisco device (or outdated Cisco device). A user then creates
static IP assignments within a block inside of netdot manually by hand, which
are not associated with actively polled devices, just description information.
If you run prune_db.pl -M -I -d 90, these items are eventually deleted because
they have a last seen time of whenever the static IP information was entered.
We have a couple of subnets behind old routing devices that do not report ARP
tables via SNMP, and would require some work to gather ARP information via CLI.
As I'd still like to be able to prune discovered IPs, I'd like to suggest that
either an option be added to prune_db.pl to exclude static IPs from the normal
pruning process, or make an option within the netdot GUI that prevents deletion
of static IPs that should never be removed, whether they are seen or not. I
realize that marking IPs as "Reserved" could be another solution, but I prefer
to label them as "Static".
This appears to be the relevant section of code in prune_db.pl (lines 167 - 187:
<pre>
if ( $self{IPS} ){
###########################################################################################
# Delete 'Discovered' and 'Static' IP addresses
# Note: This will also delete A/AAAA records, ArpCache entries, DhcpScopes,
etc.
my $q = $dbh->prepare("SELECT ipblock.id
FROM ipblock, ipblockstatus
WHERE (ipblockstatus.name='Discovered'
OR ipblockstatus.name='Static')
AND ipblock.status=ipblockstatus.id
AND ipblock.last_seen < ?");
$q->execute($sqldate);
while ( my $id = $q->fetchrow_array() ) {
if ( my $ip = Ipblock->retrieve($id) ){
$logger->debug(sprintf("Deleting IP %s", $ip->address));
unless ( $self{PRETEND} ){
$ip->delete() ;
$rows_deleted{ipblock}++;
}
}
}
}
</pre>
--
You have received this notification because you have either subscribed to it,
or are involved in it.
To change your notification preferences, please click here:
http://osl.uoregon.edu/redmine/my/account
------------------------------
_______________________________________________
Netdot-devel mailing list
[email protected]
https://osl.uoregon.edu/mailman/listinfo/netdot-devel
End of Netdot-devel Digest, Vol 83, Issue 3
*******************************************
