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 #1818] (New) Could not insert base MAC: : Error
while inserting PhysAddr: Missing address ([email protected])
2. [Netdot - Bug #1819] (New) SNMP error for VLAN 1: Can't fetch
data as class method ([email protected])
3. [Netdot - Bug #1820] (New) Could not get a valid iptree4 from
cache ([email protected])
4. [Netdot - Feature #1821] (New) Use ifName as label on
topology graph ([email protected])
5. [Netdot - Bug #1822] (New) Topology shows different devices
with same name prefix as the same device ([email protected])
6. [Netdot - Feature #1823] (New) Make topology graph an
imagemap ([email protected])
7. [Netdot - Feature #1821] Use ifName as label on topology
graph ([email protected])
8. [Netdot - Feature #1824] (New) Improve Depth Up / Depth Down
display ([email protected])
9. [Netdot - Feature #1824] Improve Depth Up / Depth Down
display ([email protected])
10. [Netdot - Feature #1821] Use ifName as label on topology
graph ([email protected])
----------------------------------------------------------------------
Message: 1
Date: Thu, 26 Jun 2014 14:37:01 -0700
From: [email protected]
Subject: [Netdot-devel] [Netdot - Bug #1818] (New) Could not insert
base MAC: : Error while inserting PhysAddr: Missing address
To: [email protected], [email protected]
Message-ID: <[email protected]>
Content-Type: text/plain; charset=utf-8
Issue #1818 has been reported by Brian Candler.
----------------------------------------
Bug #1818: Could not insert base MAC: : Error while inserting PhysAddr: Missing
address
https://osl.uoregon.edu/redmine/issues/1818
Author: Brian Candler
Status: New
Priority: Normal
Assignee:
Category:
Target version:
Resolution:
[Netdot 1.0.6, configured with IFNAME_SHORT => 1, running under Ubuntu 14.04]
This is when adding the first device, which is the Netdot server itself,
running snmpd.
It was added via the GUI and using SNMP, and then I ran from the CLI:
<pre>
/usr/local/netdot/bin/updatedevices.pl -DIFAT -d
...
DEBUG - Device::get_snmp_info: Finished getting SNMP info from x.x.x.21
DEBUG - monitor.example.net did not return base MAC. Using first available
interface MAC.
Use of uninitialized value $address in sprintf at
/usr/local/netdot/lib/Netdot/Model/Device.pm line 5641.
DEBUG - monitor.example.net: Could not insert base MAC: : Error while inserting
PhysAddr: Missing address
DEBUG - monitor.example.net: No suitable base MAC found
ERROR - Error while inserting Asset: Can't insert new Asset: DBD::mysql::st
execute failed: Cannot add or update a child row: a foreign key constraint
fails (`netdot`.`asset`, CONSTRAINT `fk_physaddr_1` FOREIGN KEY (`physaddr`)
REFERENCES `physaddr` (`id`)) [for Statement "INSERT INTO asset (product_id,
reserved_for, physaddr)
VALUES (?, ?, ?)
" with ParamValues: 0='1', 1=undef, 2=2] at
/usr/share/perl5/DBIx/ContextualFetch.pm line 52.
at /usr/local/netdot/bin/updatedevices.pl line 213.
</pre>
So two issues.
Problem 1: error handling when no base MAC address can be found (shouldn't try
to insert undef value; shouldn't continue with a SQL constraint failure). I
haven't looked at ways of improving this. Note that recent fix #1814 will
suppress the sprintf error, but I'm not sure it will fix the Asset insertion.
Problem 2: why no base MAC address was found on a machine which clearly has
interfaces?
<pre>
$ snmpwalk -v2c -c XXXX x.x.x.21 ifTable
IF-MIB::ifIndex.1 = INTEGER: 1
IF-MIB::ifIndex.2 = INTEGER: 2
IF-MIB::ifDescr.1 = STRING: lo
IF-MIB::ifDescr.2 = STRING: em1
IF-MIB::ifType.1 = INTEGER: softwareLoopback(24)
IF-MIB::ifType.2 = INTEGER: ethernetCsmacd(6)
IF-MIB::ifMtu.1 = INTEGER: 65536
IF-MIB::ifMtu.2 = INTEGER: 1500
IF-MIB::ifSpeed.1 = Gauge32: 10000000
IF-MIB::ifSpeed.2 = Gauge32: 100000000
IF-MIB::ifPhysAddress.1 = STRING:
IF-MIB::ifPhysAddress.2 = STRING: 90:b1:1c:90:d2:1c
</pre>
Note that because this machine has a modern 3.13 kernel, it is using the new
"predictable network interface names" instead of eth0. See
http://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames/
I will skip all the boring debugging I had to do to get to the bottom of this,
which in fact is explained in a lowly debug message:
<pre>
DEBUG - Device::get_snmp_info: x.x.x.21: Interface em1 ignored per config
option (IFRESERVED)
</pre>
Grr. The pattern explicitly excludes <code>em\d+</code>. But why? Also, the
default IFRESERVED regexp is missing parentheses, so only the first item is
anchored.
So I would suggest a better default to be:
<pre>
IFRESERVED =>
'^(bme|pime|mtun|lsi|jsrv|pimd|vt-|tap|pe-|pd-|dsc|rptr|unrouted)',
</pre>
However this still assumes that we won't ever come across any Linux devices
with names like bme0 or dsc0.
--
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: Thu, 26 Jun 2014 14:40:38 -0700
From: [email protected]
Subject: [Netdot-devel] [Netdot - Bug #1819] (New) SNMP error for VLAN
1: Can't fetch data as class method
To: [email protected], [email protected]
Message-ID: <[email protected]>
Content-Type: text/plain; charset=utf-8
Issue #1819 has been reported by Brian Candler.
----------------------------------------
Bug #1819: SNMP error for VLAN 1: Can't fetch data as class method
https://osl.uoregon.edu/redmine/issues/1819
Author: Brian Candler
Status: New
Priority: Normal
Assignee:
Category:
Target version:
Resolution:
When adding a new device (discovered via neighbor detection):
<pre>
INFO - All Devices updated. 3 devices in 23 sec
INFO - Discovering Network Topology using sources: STP, FDB, P2P, DP. Min
score: 6
INFO - Topology::get_dp_links: Discovering unknown neighbor: 10.0.1.2
ERROR - 10.0.1.2: SNMP error for VLAN 60: Can't fetch data as class method at
/usr/local/netdot/lib/Netdot/Topology.pm line 595.
ERROR - 10.0.1.2: SNMP error for VLAN 30: Can't fetch data as class method at
/usr/local/netdot/lib/Netdot/Topology.pm line 595.
ERROR - 10.0.1.2: SNMP error for VLAN 44: Can't fetch data as class method at
/usr/local/netdot/lib/Netdot/Topology.pm line 595.
...
ERROR - 10.0.1.2: SNMP error for VLAN 48: Can't fetch data as class method at
/usr/local/netdot/lib/Netdot/Topology.pm line 595.
ERROR - 10.0.1.2: SNMP error for VLAN 1: Can't fetch data as class method at
/usr/local/netdot/lib/Netdot/Topology.pm line 595.
INFO - Inserted new RR: admin-core.example.net
</pre>
Maybe related:
http://stackoverflow.com/questions/8667079/dbixclass-find-or-create-error-cant-fetch-data-as-class-method-at
--
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: Thu, 26 Jun 2014 14:42:17 -0700
From: [email protected]
Subject: [Netdot-devel] [Netdot - Bug #1820] (New) 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 #1820 has been reported by Brian Candler.
----------------------------------------
Bug #1820: Could not get a valid iptree4 from cache
https://osl.uoregon.edu/redmine/issues/1820
Author: Brian Candler
Status: New
Priority: Normal
Assignee:
Category:
Target version:
Resolution:
I only saw this once, but it had a long traceback so I thought I'd report it.
<pre>
INFO - admin-core.example.net [Vl60]: Created Subnet 10.6.0.0/24
WARN - admin-core.example.net [Vl60]: Could not insert IP 10.6.0.1: Could not
get a valid iptree4 from cache
Trace begun at /usr/local/netdot/lib/Netdot.pm line 105
Netdot::throw_fatal('Ipblock=HASH(0x5aa6598)', 'Could not get a valid iptree4
from cache') called at /usr/local/netdot/lib/Netdot/Model/Ipblock.pm line 3561
Netdot::Model::Ipblock::_tree_get('Ipblock=HASH(0x5aa6598)') called at
/usr/local/netdot/lib/Netdot/Model/Ipblock.pm line 3361
Netdot::Model::Ipblock::_tree_delete('Ipblock=HASH(0x5aa6598)') called at
/usr/local/netdot/lib/Netdot/Model/Ipblock.pm line 1752
Netdot::Model::Ipblock::delete('Ipblock=HASH(0x5aa6598)') called at
/usr/local/netdot/lib/Netdot/Model/Ipblock.pm line 679
Netdot::Model::Ipblock::insert('Ipblock', 'HASH(0x5ab1cd8)') called at
/usr/local/netdot/lib/Netdot/Model/Interface.pm line 749
eval {...} at /usr/local/netdot/lib/Netdot/Model/Interface.pm line 748
Netdot::Model::Interface::update_ip('Interface=HASH(0x5aa6af0)', 'subnet',
'10.6.0.0/24', 'version', 4, 'subs_inherit', 1, 'address', 10.6.0.1,
'add_subnets', 1) called at /usr/local/netdot/lib/Netdot/Model/Interface.pm
line 600
Netdot::Model::Interface::snmp_update('Interface', 'doc_status', 'snmp',
'device', 'Device=HASH(0x59c0098)', 'monitored', 0, 'number', 60,
'overwrite_descr', 1, 'name', 'Vl60', 'auto_dns', 1, 'snmp_info',
'HASH(0x598b740)', 'add_subnets', 1, 'subs_inherit', 1, 'stp_instances',
'HASH(0x5969fb0)') called at /usr/local/netdot/lib/Netdot/Model/Device.pm line
6219
Netdot::Model::Device::_update_interfaces('Device=HASH(0x59c0098)', 'info',
'HASH(0x4e009b0)', 'add_subnets', undef, 'subs_inherit', undef,
'overwrite_descr', 1) called at /usr/local/netdot/lib/Netdot/Model/Device.pm
line 3068
Netdot::Model::Device::info_update('Device=HASH(0x59c0098)', 'add_subnets',
undef, 'subs_inherit', undef, 'bgp_peers', undef, 'pretend', undef, 'session',
'SNMP::Info::Layer3::C6500=HASH(0x55566e8)', 'info', 'HASH(0x4e009b0)',
'device_is_new', 1) called at /usr/local/netdot/lib/Netdot/Model/Device.pm line
2821
Netdot::Model::Device::snmp_update('Device=HASH(0x59c0098)', 'session',
'SNMP::Info::Layer3::C6500=HASH(0x55566e8)', 'info', 'HASH(0x4e009b0)',
'device_is_new', 1) called at /usr/local/netdot/lib/Netdot/Model/Device.pm line
1606
Netdot::Model::Device::discover('Device', 'name', 10.0.1.2, 'auth_proto',
undef, 'sec_name', undef, 'communities', undef, 'priv_pass', undef,
'sec_level', undef, 'auth_pass', undef, 'priv_proto', undef, 'version', undef,
'timeoutretries', undef) called at /usr/local/netdot/lib/Netdot/Topology.pm
line 595
eval {...} at /usr/local/netdot/lib/Netdot/Topology.pm line 594
Netdot::Topology::get_dp_links('Netdot::Topology', 'version', undef, 'retries',
1, 'sec_level', undef, 'priv_proto', undef, 'auth_pass', undef, 'auth_proto',
undef, 'priv_pass', undef, 'sec_name', undef, 'timeout', 1000000) called at
/usr/local/netdot/lib/Netdot/Topology.pm line 74
Netdot::Topology::discover('Netdot::Topology', 'auth_pass', undef,
'priv_proto', undef, 'retries', 1, 'sec_level', undef, 'version', undef,
'timeout', 1000000, 'priv_pass', undef, 'sec_name', undef, 'auth_proto', undef)
called at /usr/local/netdot/bin/updatedevices.pl line 231
INFO - admin-core.example.net: Interface 64 (Vl64) updated
</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
------------------------------
Message: 4
Date: Thu, 26 Jun 2014 14:47:50 -0700
From: [email protected]
Subject: [Netdot-devel] [Netdot - Feature #1821] (New) Use ifName as
label on topology graph
To: [email protected], [email protected]
Message-ID: <[email protected]>
Content-Type: text/plain; charset=utf-8
Issue #1821 has been reported by Brian Candler.
----------------------------------------
Feature #1821: Use ifName as label on topology graph
https://osl.uoregon.edu/redmine/issues/1821
Author: Brian Candler
Status: New
Priority: Low
Assignee:
Category:
Target version:
Resolution:
When using C3750 in topology graphs the interfaces are labelled as "10101",
"10105" etc.
If IFNAME_SHORT is enabled I think it would be better to use the interface name
(which is "ifName" in this case), or to have an option to do so. For these
switches it uses similar amount of space but is clearer. From MIB:
<pre>
IF-MIB::ifName.10101 = STRING: Gi1/0/1
IF-MIB::ifName.10102 = STRING: Gi1/0/2
IF-MIB::ifName.10103 = STRING: Gi1/0/3
IF-MIB::ifName.10104 = STRING: Gi1/0/4
IF-MIB::ifName.10105 = STRING: Gi1/0/5
</pre>
(aside: can graphviz be told to use slightly longer lines between devices by
default?)
--
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: 5
Date: Thu, 26 Jun 2014 14:49:25 -0700
From: [email protected]
Subject: [Netdot-devel] [Netdot - Bug #1822] (New) Topology shows
different devices with same name prefix as the same device
To: [email protected], [email protected]
Message-ID: <[email protected]>
Content-Type: text/plain; charset=utf-8
Issue #1822 has been reported by Brian Candler.
----------------------------------------
Bug #1822: Topology shows different devices with same name prefix as the same
device
https://osl.uoregon.edu/redmine/issues/1822
Author: Brian Candler
Status: New
Priority: Normal
Assignee:
Category:
Target version:
Resolution:
In the topology graph, if there are two different devices called "ap" (e.g.
"ap.library-tech" and "ap.old-library"), they are drawn as a single node called
"ap" which is connected to both uplink switches.
The graphviz should use the device id to distinguish the node, but the device
name as the label.
--
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: 6
Date: Thu, 26 Jun 2014 14:55:30 -0700
From: [email protected]
Subject: [Netdot-devel] [Netdot - Feature #1823] (New) Make topology
graph an imagemap
To: [email protected], [email protected]
Message-ID: <[email protected]>
Content-Type: text/plain; charset=utf-8
Issue #1823 has been reported by Brian Candler.
----------------------------------------
Feature #1823: Make topology graph an imagemap
https://osl.uoregon.edu/redmine/issues/1823
Author: Brian Candler
Status: New
Priority: Low
Assignee:
Category:
Target version:
Resolution:
It would be very cool if the whole topology graph was a clickable imagemap
where each graph node links to the page for the relevant device.
graphviz supports this:
http://stackoverflow.com/questions/15837283/graphviz-embedded-url
Indeed, the device-level 'topology' section does this already. Maybe this
toplogy tab of the device info should be the link target, i.e.
<code>/netdot/management/device.html?id=XXX&view=Topology</code>
--
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: 7
Date: Thu, 26 Jun 2014 14:58:43 -0700
From: [email protected]
Subject: [Netdot-devel] [Netdot - Feature #1821] Use ifName as label
on topology graph
To: [email protected], [email protected]
Message-ID: <[email protected]>
Content-Type: text/plain; charset=utf-8
Issue #1821 has been updated by Brian Candler.
This is equivalent to the "Show Interface Names?" checkbox in the device level
Topology tab <code>/netdot/management/device.html?id=XXX&view=Topology</code>
----------------------------------------
Feature #1821: Use ifName as label on topology graph
https://osl.uoregon.edu/redmine/issues/1821#change-3194
Author: Brian Candler
Status: New
Priority: Low
Assignee:
Category:
Target version:
Resolution:
When using C3750 in topology graphs the interfaces are labelled as "10101",
"10105" etc.
If IFNAME_SHORT is enabled I think it would be better to use the interface name
(which is "ifName" in this case), or to have an option to do so. For these
switches it uses similar amount of space but is clearer. From MIB:
<pre>
IF-MIB::ifName.10101 = STRING: Gi1/0/1
IF-MIB::ifName.10102 = STRING: Gi1/0/2
IF-MIB::ifName.10103 = STRING: Gi1/0/3
IF-MIB::ifName.10104 = STRING: Gi1/0/4
IF-MIB::ifName.10105 = STRING: Gi1/0/5
</pre>
(aside: can graphviz be told to use slightly longer lines between devices by
default?)
--
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: 8
Date: Fri, 27 Jun 2014 00:36:32 -0700
From: [email protected]
Subject: [Netdot-devel] [Netdot - Feature #1824] (New) Improve Depth
Up / Depth Down display
To: [email protected], [email protected]
Message-ID: <[email protected]>
Content-Type: text/plain; charset=utf-8
Issue #1824 has been reported by Brian Candler.
----------------------------------------
Feature #1824: Improve Depth Up / Depth Down display
https://osl.uoregon.edu/redmine/issues/1824
Author: Brian Candler
Status: New
Priority: Normal
Assignee:
Category:
Target version:
Resolution:
When viewing the topology from the view of at a particular device, you can
select "Depth Up" (towards the NMS_DEVICE) and "Depth Down" (away from the
NMS_DEVICE)
This works, but it displays a tree rooted at the chosen device on the left and
both "Up" and "Down" devices mixed together to the right.
What I was expecting was a chain of "Up" devices to be on the left, and the
"Down" devices to the right.
In the attached example diagram, "lib-core" is actually the parent (closer to
NMS_DEVICE) and the other devices are children, but you can't tell this from
the diagram.
--
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: 9
Date: Fri, 27 Jun 2014 01:45:08 -0700
From: [email protected]
Subject: [Netdot-devel] [Netdot - Feature #1824] Improve Depth Up /
Depth Down display
To: [email protected], [email protected]
Message-ID: <[email protected]>
Content-Type: text/plain; charset=utf-8
Issue #1824 has been updated by Brian Candler.
File Device-4--0-0-0 (1).png added
Fix at https://github.com/cvicente/Netdot/pull/17
----------------------------------------
Feature #1824: Improve Depth Up / Depth Down display
https://osl.uoregon.edu/redmine/issues/1824#change-3195
Author: Brian Candler
Status: New
Priority: Normal
Assignee:
Category:
Target version:
Resolution:
When viewing the topology from the view of at a particular device, you can
select "Depth Up" (towards the NMS_DEVICE) and "Depth Down" (away from the
NMS_DEVICE)
This works, but it displays a tree rooted at the chosen device on the left and
both "Up" and "Down" devices mixed together to the right.
What I was expecting was a chain of "Up" devices to be on the left, and the
"Down" devices to the right.
In the attached example diagram, "lib-core" is actually the parent (closer to
NMS_DEVICE) and the other devices are children, but you can't tell this from
the diagram.
--
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: 10
Date: Fri, 27 Jun 2014 02:48:22 -0700
From: [email protected]
Subject: [Netdot-devel] [Netdot - Feature #1821] Use ifName as label
on topology graph
To: [email protected], [email protected]
Message-ID: <[email protected]>
Content-Type: text/plain; charset=utf-8
Issue #1821 has been updated by Brian Candler.
File Device-4--0-1-.png added
There is code for this at https://github.com/candlerb/Netdot/tree/candlerb/1821
I can't make a sensible pull request until
https://github.com/cvicente/Netdot/pull/17 is merged
It allows minlen to be set from the command line with build_topo_graph.pl (and
hence from crontab) and also in the per-device topo view.
----------------------------------------
Feature #1821: Use ifName as label on topology graph
https://osl.uoregon.edu/redmine/issues/1821#change-3196
Author: Brian Candler
Status: New
Priority: Low
Assignee:
Category:
Target version:
Resolution:
When using C3750 in topology graphs the interfaces are labelled as "10101",
"10105" etc.
If IFNAME_SHORT is enabled I think it would be better to use the interface name
(which is "ifName" in this case), or to have an option to do so. For these
switches it uses similar amount of space but is clearer. From MIB:
<pre>
IF-MIB::ifName.10101 = STRING: Gi1/0/1
IF-MIB::ifName.10102 = STRING: Gi1/0/2
IF-MIB::ifName.10103 = STRING: Gi1/0/3
IF-MIB::ifName.10104 = STRING: Gi1/0/4
IF-MIB::ifName.10105 = STRING: Gi1/0/5
</pre>
(aside: can graphviz be told to use slightly longer lines between devices by
default?)
--
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 87, Issue 10
********************************************
