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. [SCM] Netdot branch netdot-1.0 updated.
netdot-1.0.6-69-g2649c28 ([email protected])
2. [Netdot - Feature #1843] (New) Enhance netdot_prune to allow
deletion of specific netblock records ([email protected])
----------------------------------------------------------------------
Message: 1
Date: Mon, 1 Dec 2014 13:19:34 -0800
From: [email protected]
Subject: [Netdot-devel] [SCM] Netdot branch netdot-1.0 updated.
netdot-1.0.6-69-g2649c28
To: [email protected]
Message-ID: <[email protected]>
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "Netdot".
The branch, netdot-1.0 has been updated
via 2649c2837387f88b549fe3d62fa149c5124fb406 (commit)
via bdaf2529e8898311eac50bad9bf23f550baf5d72 (commit)
from bb6e660c11226373e753f33d85f3c83db90842f0 (commit)
Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.
- Log -----------------------------------------------------------------
commit 2649c2837387f88b549fe3d62fa149c5124fb406
Merge: bb6e660 bdaf252
Author: Carlos Vicente <[email protected]>
Date: Mon Dec 1 16:18:48 2014 -0500
Merge pull request #28 from Krakozaber/master
Update Device.pm
commit bdaf2529e8898311eac50bad9bf23f550baf5d72
Author: Krakozaber <[email protected]>
Date: Thu Nov 13 11:43:07 2014 +0400
Update Device.pm
diff --git a/lib/Netdot/Model/Device.pm b/lib/Netdot/Model/Device.pm
index b1bbb39..4217928 100644
--- a/lib/Netdot/Model/Device.pm
+++ b/lib/Netdot/Model/Device.pm
@@ -71,6 +71,7 @@ my @SMETHODS = qw(
i_up_admin i_duplex i_duplex_admin
ip_index ip_netmask i_mac ip_table
i_vlan_membership qb_v_name v_name v_state
+ hasLLDP
);
@@ -970,7 +971,7 @@ sub get_snmp_info {
################################################################
# CDP/LLDP stuff
- if ( $hashes{hasCDP} ){
+ if (( $hashes{hasCDP} ) or ($hashes{hasLLDP})){
# Call all the relevant methods
my %dp_hashes;
my @dp_methods = qw ( c_id c_ip c_port c_platform );
-----------------------------------------------------------------------
Summary of changes:
lib/Netdot/Model/Device.pm | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
hooks/post-receive
--
Netdot
------------------------------
Message: 2
Date: Mon, 1 Dec 2014 18:06:01 -0800
From: [email protected]
Subject: [Netdot-devel] [Netdot - Feature #1843] (New) Enhance
netdot_prune to allow deletion of specific netblock records
To: [email protected], [email protected]
Message-ID: <[email protected]>
Content-Type: text/plain; charset=utf-8
Issue #1843 has been reported by OJ LaBoeuf.
----------------------------------------
Feature #1843: Enhance netdot_prune to allow deletion of specific netblock
records
https://osl.uoregon.edu/redmine/issues/1843
Author: OJ LaBoeuf
Status: New
Priority: Normal
Assignee:
Category:
Target version:
Resolution:
Certain parts of our neighborhood have lots of mac and IP addresses being
created / destroyed all of the time.
We would like to be able to more aggressively prune these netblocks than the
rest of our network.
Being able to run prune_db with a filter instead of globally on the entire
dataset would solve this issue.
--
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 93, Issue 1
*******************************************
