Send Netdot-users mailing list submissions to
[email protected]
To subscribe or unsubscribe via the World Wide Web, visit
https://osl.uoregon.edu/mailman/listinfo/netdot-users
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-users digest..."
Today's Topics:
1. Re: error on deleting device (Carlos Vicente)
2. Re: tracking trunking interfaces (Carlos Vicente)
3. Re: L3 to L2 Mapping (Carlos Vicente)
4. Re: Device Polling Statistics (Carlos Vicente)
5. Re: Device Polling Statistics (Alan KT So)
6. Re: Device Polling Statistics (Carlos Vicente)
----------------------------------------------------------------------
Message: 1
Date: Thu, 23 Aug 2012 02:03:55 -0400
From: Carlos Vicente <[email protected]>
Subject: Re: [Netdot-users] error on deleting device
To: Markus Wigge <[email protected]>
Cc: [email protected]
Message-ID: <[email protected]>
Content-Type: text/plain; charset=ISO-8859-1
Hi Markus,
That's strange. There was a related bug but it was fixed in 1.0.1
Try dropping the table
fwtableentry_1341107103
and see if that clears it.
Let me know so I can follow up.
Thx
cv
On 8/20/12 8:44 AM, Markus Wigge wrote:
> Hi,
>
> when I try to delete a device in netdot 1.0.1 I get the following error:
>
> delete.html produced the following error:
>
>
> Transaction aborted: Can't delete 449: DBD::mysql::st execute failed:
> Cannot delete or update a parent row: a foreign key constraint fails
> (`netdot`.`fwtableentry_1341107103`, CONSTRAINT `fk_interface_1` FOREIGN
> KEY (`interface`) REFERENCES `interface` (`id`)) [for Statement "DELETE
> FROM interface
> WHERE id=?
> " with ParamValues: 0='449'] at /usr/share/perl5/DBIx/ContextualFetch.pm
> line 52, line 4.
>
> Stack:
> [/usr/share/perl5/DBIx/ContextualFetch.pm:52]
> [/usr/share/perl5/DBIx/ContextualFetch.pm:32]
> [/usr/share/perl5/Class/DBI.pm:737]
> [/opt/netdot/lib/Netdot/Model.pm:867]
> [/opt/netdot/lib/Netdot/Model/Interface.pm:198]
> [/usr/share/perl5/Class/DBI/Iterator.pm:106]
> [/usr/share/perl5/Class/DBI/Cascade/Delete.pm:21]
> [/usr/share/perl5/Class/DBI/Relationship/HasMany.pm:75]
> [/usr/share/perl5/Class/Trigger.pm:74]
> [/usr/share/perl5/Class/DBI.pm:735]
> [/opt/netdot/lib/Netdot/Model.pm:867]
> [/opt/netdot/lib/Netdot/Model/Device.pm:2273]
> [/opt/netdot/htdocs/generic/delete.html:106]
> [/opt/netdot/htdocs/generic/delete.html:108]
> [/opt/netdot/htdocs/autohandler:110]
> [/opt/netdot/htdocs/management/dhandler:1]
> [/opt/netdot/htdocs/management/autohandler:83]
> [/usr/share/perl5/HTML/Mason/Request.pm:948]
>
> [/opt/netdot/htdocs/masondata/obj/1077268618/management/autohandler.obj:21]
> [/opt/netdot/htdocs/autohandler:76]
> at /usr/share/perl5/Class/DBI/Iterator.pm line 106
>
> Stack:
> [/usr/share/perl/5.10/Carp.pm:44]
> [/usr/share/perl5/Class/DBI.pm:169]
> [/usr/share/perl5/Class/DBI.pm:175]
> [/usr/share/perl5/Class/DBI.pm:739]
> [/opt/netdot/lib/Netdot/Model.pm:867]
> [/opt/netdot/lib/Netdot/Model/Interface.pm:198]
> [/usr/share/perl5/Class/DBI/Iterator.pm:106]
> [/usr/share/perl5/Class/DBI/Cascade/Delete.pm:21]
> [/usr/share/perl5/Class/DBI/Relationship/HasMany.pm:75]
> [/usr/share/perl5/Class/Trigger.pm:74]
> [/usr/share/perl5/Class/DBI.pm:735]
> [/opt/netdot/lib/Netdot/Model.pm:867]
> [/opt/netdot/lib/Netdot/Model/Device.pm:2273]
> [/opt/netdot/htdocs/generic/delete.html:106]
> [/opt/netdot/htdocs/generic/delete.html:108]
> [/opt/netdot/htdocs/autohandler:110]
> [/opt/netdot/htdocs/management/dhandler:1]
> [/opt/netdot/htdocs/management/autohandler:83]
> [/usr/share/perl5/HTML/Mason/Request.pm:948]
>
> [/opt/netdot/htdocs/masondata/obj/1077268618/management/autohandler.obj:21]
> [/opt/netdot/htdocs/autohandler:76]
>
>
> With another device it worked properly some days ago. Any ideas?
>
> Regards,
> Markus
> _______________________________________________
> Netdot-users mailing list
> [email protected]
> https://osl.uoregon.edu/mailman/listinfo/netdot-users
>
--
cv
------------------------------
Message: 2
Date: Thu, 23 Aug 2012 02:05:41 -0400
From: Carlos Vicente <[email protected]>
Subject: Re: [Netdot-users] tracking trunking interfaces
To: William Bulley <[email protected]>
Cc: [email protected]
Message-ID: <[email protected]>
Content-Type: text/plain; charset=ISO-8859-1
On 8/20/12 2:49 PM, William Bulley wrote:
> Many (most?) of our devices have a trunking port (at least to their
> upstream neighbor). How does NETDOT track this type of interface?
It doesn't. However, it's likely that the information is in SNMP and we
can add a field to the interface table to identify that.
> There doesn't seem to be an entry in ifType (IF-MIB) for trunks.
>
> The "trunks" on some of our building routers are identified with
> the interface "type" of "ethernetCsmacd" - which is pretty generic.
Yeah, the interface type is a physical property is independent of the
bridging status.
--
cv
------------------------------
Message: 3
Date: Thu, 23 Aug 2012 02:06:20 -0400
From: Carlos Vicente <[email protected]>
Subject: Re: [Netdot-users] L3 to L2 Mapping
To: Ramon Velazquez <[email protected]>
Cc: [email protected]
Message-ID: <[email protected]>
Content-Type: text/plain; charset=ISO-8859-1
On 8/22/12 10:54 AM, Ramon Velazquez wrote:
> Hi Guys,
>
>
>
> Discovered IP devices are not mapped to a MAC Address; However; I can
> find them by MAC Address or IP address individually. Is this the way
> supposed to work?
>
I'm not sure if I understand the question.
--
cv
------------------------------
Message: 4
Date: Thu, 23 Aug 2012 02:07:51 -0400
From: Carlos Vicente <[email protected]>
Subject: Re: [Netdot-users] Device Polling Statistics
To: Alan KT So <[email protected]>
Cc: [email protected]
Message-ID: <[email protected]>
Content-Type: text/plain; charset=ISO-8859-1
On 8/16/12 11:51 PM, Alan KT So wrote:
> Dear all,
>
> I have empty graphs for all polling statistics. I have followed advises
> from previous mail to change pollstats.rdd to world writable. I notice
> that most values are NaN and the files can be updated. Are there any
> possible reasons that the rrd file is not keeping the correct values?
>
How frequently do you poll? Once an hour?
--
cv
------------------------------
Message: 5
Date: Thu, 23 Aug 2012 14:11:33 +0800
From: Alan KT So <[email protected]>
Subject: Re: [Netdot-users] Device Polling Statistics
To: Carlos Vicente <[email protected]>
Cc: [email protected]
Message-ID: <[email protected]>
Content-Type: text/plain; charset=us-ascii
Twice a day from Monday to Friday. Does it matter?
# Retrieve forwarding tables and ARP caches
0 10 * * 1-5 root $PREFIX/bin/updatedevices.pl -DFA
# Twice a day, rediscover devices and topology (in addition to above)
#0 12,17 * * * root $PREFIX/bin/updatedevices.pl -DIFAT
0 15 * * 1-5 root $PREFIX/bin/updatedevices.pl -DIFAT
On Thu, Aug 23, 2012 at 02:07:51AM -0400, Carlos Vicente wrote:
> On 8/16/12 11:51 PM, Alan KT So wrote:
> > Dear all,
> >
> > I have empty graphs for all polling statistics. I have followed advises
> > from previous mail to change pollstats.rdd to world writable. I notice
> > that most values are NaN and the files can be updated. Are there any
> > possible reasons that the rrd file is not keeping the correct values?
> >
>
> How frequently do you poll? Once an hour?
>
>
> --
> cv
------------------------------
Message: 6
Date: Thu, 23 Aug 2012 02:14:24 -0400
From: Carlos Vicente <[email protected]>
Subject: Re: [Netdot-users] Device Polling Statistics
To: Alan KT So <[email protected]>
Cc: [email protected]
Message-ID: <[email protected]>
Content-Type: text/plain; charset=ISO-8859-1
On 8/23/12 2:11 AM, Alan KT So wrote:
> Twice a day from Monday to Friday. Does it matter?
Yes, I think it does. The sampling frequency is configured into the RRD
file. You can probably create your own RRD file with the desired
sampling frequency.
--
cv
------------------------------
_______________________________________________
Netdot-users mailing list
[email protected]
https://osl.uoregon.edu/mailman/listinfo/netdot-users
End of Netdot-users Digest, Vol 45, Issue 19
********************************************
