Send netdisco-users mailing list submissions to
[email protected]
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.sourceforge.net/lists/listinfo/netdisco-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 netdisco-users digest..."
Today's Topics:
1. Re: device_port_power_pkey on Cisco catalyst 3850 (Eric Miller)
2. Re: device_port_power_pkey on Cisco catalyst 3850 (Sassan Dibadj)
3. Problem after upgrade (Sassan Dibadj)
4. Re: Problem after upgrade (Oliver Gorwits)
5. Re: Prevent port configuration changes (Oliver Gorwits)
6. Re: Prevent port configuration changes (Oliver Gorwits)
--- Begin Message ---
The uninitialized value in string error should be corrected with the
next release of SNMP::Info.
The duplicate key value errors are caused by the way the Cisco 3850
switches are reporting the PoE port numbering. It does not adhere to
the Cisco specification and match the reporting of all other Cisco
switches. This would be best addressed with Cisco bug report.
The database table holding the per-port PoE status for these ports will
not be populated due to the error, but there should be no other adverse
impact.
Thanks,
Eric
On 2014-07-02 10:41, Sassan Dibadj wrote:
Hello everyone,
I finally took the plunge and setup a new Netdisco 2 server running on
RHEL 6.5.
I did a DB dump from Netdisco 1.3.2 and imported that and the topology
file into Netdisco 2.
Everything seems to be working well and the housekeeping jobs seem to
be running, I looked in the daemon log file and noticed an error that
only seems to be coming up on our Cisco 3850 switches.
Here are a couple of entries from the log.
error running job:
DBIx::Class::Storage::DBI::_dbh_execute_for_fetch():
execute_for_fetch() aborted with 'ERROR: duplicate key value violates
unique constraint "device_port_power_pkey"
DETAIL: Key (port, ip)=(GigabitEthernet3/0/36, 172.xx.xx.3) already
exists.' at populate slice:
{
admin => "true",
class => "class0",
ip => "172.xx.xx.3",
module => 3,
port => "GigabitEthernet3/0/36",
power => 5333,
status => "deliveringPower"
} at /home/netdisco/perl5/lib/perl5/App/Netdisco/Core/Discover.pm line
546
error running job:
DBIx::Class::Storage::DBI::_dbh_execute_for_fetch():
execute_for_fetch() aborted with 'ERROR: duplicate key value violates
unique constraint "device_port_power_pkey"
DETAIL: Key (port, ip)=(GigabitEthernet2/0/35, 172.xx.xx.81) already
exists.' at populate slice:
{
admin => "true",
class => "class0",
ip => "172.xx.xx.81",
module => 4,
port => "GigabitEthernet2/0/35",
power => 0,
status => "searching"
I also see a bunch of
Use of uninitialized value in string eq at
/home/netdisco/perl5/lib/perl5/SNMP/Info/Layer3/Cisco.pm line 127
Any idea on what to try or more info I can provide?
--- End Message ---
--- Begin Message ---
Thank you for the information, I'll contact Cisco regarding the PoE port
numbering and open up a case. Hopefully that will get things moving on that
front.
So far everything else has been running great with the Netdisco 2 upgrade.
Definitely the most useful app we use. Thank you for all the hard work on it.
-----Original Message-----
From: Eric Miller [mailto:[email protected]]
Sent: Tuesday, July 08, 2014 9:00 PM
To: Sassan Dibadj
Cc: [email protected]
Subject: Re: [Netdisco] device_port_power_pkey on Cisco catalyst 3850
The uninitialized value in string error should be corrected with the next
release of SNMP::Info.
The duplicate key value errors are caused by the way the Cisco 3850 switches
are reporting the PoE port numbering. It does not adhere to the Cisco
specification and match the reporting of all other Cisco switches. This would
be best addressed with Cisco bug report.
The database table holding the per-port PoE status for these ports will not be
populated due to the error, but there should be no other adverse impact.
Thanks,
Eric
On 2014-07-02 10:41, Sassan Dibadj wrote:
> Hello everyone,
>
> I finally took the plunge and setup a new Netdisco 2 server running on
> RHEL 6.5.
>
> I did a DB dump from Netdisco 1.3.2 and imported that and the topology
> file into Netdisco 2.
>
> Everything seems to be working well and the housekeeping jobs seem to
> be running, I looked in the daemon log file and noticed an error that
> only seems to be coming up on our Cisco 3850 switches.
>
> Here are a couple of entries from the log.
>
> error running job:
> DBIx::Class::Storage::DBI::_dbh_execute_for_fetch():
> execute_for_fetch() aborted with 'ERROR: duplicate key value violates
> unique constraint "device_port_power_pkey"
>
> DETAIL: Key (port, ip)=(GigabitEthernet3/0/36, 172.xx.xx.3) already
> exists.' at populate slice:
>
> {
>
> admin => "true",
>
> class => "class0",
>
> ip => "172.xx.xx.3",
>
> module => 3,
>
> port => "GigabitEthernet3/0/36",
>
> power => 5333,
>
> status => "deliveringPower"
>
> } at /home/netdisco/perl5/lib/perl5/App/Netdisco/Core/Discover.pm line
> 546
>
> error running job:
> DBIx::Class::Storage::DBI::_dbh_execute_for_fetch():
> execute_for_fetch() aborted with 'ERROR: duplicate key value violates
> unique constraint "device_port_power_pkey"
>
> DETAIL: Key (port, ip)=(GigabitEthernet2/0/35, 172.xx.xx.81) already
> exists.' at populate slice:
>
> {
>
> admin => "true",
>
> class => "class0",
>
> ip => "172.xx.xx.81",
>
> module => 4,
>
> port => "GigabitEthernet2/0/35",
>
> power => 0,
>
> status => "searching"
>
> I also see a bunch of
>
> Use of uninitialized value in string eq at
> /home/netdisco/perl5/lib/perl5/SNMP/Info/Layer3/Cisco.pm line 127
>
> Any idea on what to try or more info I can provide?
________________________________
UT Southwestern Medical Center
The future of medicine, today.
--- End Message ---
--- Begin Message ---
I upgraded to the newest version but now I seem to not have any jobs running
and am getting strange errors.
If I run netdisc-daemon-fg by itself I get
[netdisco@netdisco bin]$ ./netdisco-daemon-fg
Can't locate App/Netdisco.pm in @INC (@INC contains: /home/netdisco/perl5/lib
/home/netdisco/perl5/bin/lib /home/netdisco/perl5/lib/perl5/App
/usr/local/lib64/perl5 /us r/local/share/perl5 /usr/lib64/perl5/vendor_perl
/usr/share/perl5/vendor_perl /usr/lib64/perl5 /usr/share/perl5 .) at
./netdisco-daemon-fg line 17.
BEGIN failed--compilation aborted at ./netdisco-daemon-fg line 17.
Daemon log shows the below.
Use of uninitialized value in subroutine entry at
/home/netdisco/perl5/bin/netdisco-daemon-fg line 83.
DBIx::Class::Storage::DBI::_dbh_execute(): DBI Exception: DBD::SQLite::st
execute failed: UNIQUE constraint failed: admin.job [for Statement "INSERT INTO
admin ( action
, debug, device, entered, finished, job, log, port, started, status, subaction,
type, userip, username) VALUES ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ? )"]
at /home/n
etdisco/perl5/lib/perl5/App/Netdisco/Daemon/LocalQueue.pm line 17
## netdisco-daemon-fg: caught signal '__DIE__', exiting
Totally dead in the water trying to get jobs to run...not really sure what
happened.
Any help would be much appreciated.
________________________________
UT Southwestern Medical Center
The future of medicine, today.
--- End Message ---
--- Begin Message ---
Hi Sassan,
Yes, something is fishy with the @INC shown in your output. I believe
the correct directory to have included would be:
/home/netdisco/perl5/lib/perl5/
Does the web frontend work OK?
Can you try logging out, then back in, then running "~/bin/localenv
perl -V" and looking at the content of @INC to see if it's different?
The second item, about the admin.job error can safely be ignored for
now, I think.
regards,
oliver.
On 2014-07-11 21:12, Sassan Dibadj wrote:
I upgraded to the newest version but now I seem to not have any jobs
running and am getting strange errors.
If I run netdisc-daemon-fg by itself I get
[netdisco@netdisco bin]$ ./netdisco-daemon-fg
Can't locate App/Netdisco.pm in @INC (@INC contains:
/home/netdisco/perl5/lib /home/netdisco/perl5/bin/lib
/home/netdisco/perl5/lib/perl5/App /usr/local/lib64/perl5 /us
r/local/share/perl5 /usr/lib64/perl5/vendor_perl
/usr/share/perl5/vendor_perl /usr/lib64/perl5 /usr/share/perl5 .) at
./netdisco-daemon-fg line 17.
BEGIN failed--compilation aborted at ./netdisco-daemon-fg line 17.
Daemon log shows the below.
Use of uninitialized value in subroutine entry at
/home/netdisco/perl5/bin/netdisco-daemon-fg line 83.
DBIx::Class::Storage::DBI::_dbh_execute(): DBI Exception:
DBD::SQLite::st execute failed: UNIQUE constraint failed: admin.job
[for Statement "INSERT INTO admin ( action
, debug, device, entered, finished, job, log, port, started, status,
subaction, type, userip, username) VALUES ( ?, ?, ?, ?, ?, ?, ?, ?,
?,
?, ?, ?, ?, ? )"] at /home/n
etdisco/perl5/lib/perl5/App/Netdisco/Daemon/LocalQueue.pm line 17
## netdisco-daemon-fg: caught signal '__DIE__', exiting
Totally dead in the water trying to get jobs to run…not really sure
what happened.
Any help would be much appreciated.
-------------------------
UT Southwestern Medical Center
The future of medicine, today.
--- End Message ---
--- Begin Message ---
On 2014-07-07 16:43, [email protected] wrote:
Hi,
i'm in 2 minds about whether NetDISCO should only be an
inventory/reporting system or whether it should
continue down the route of being a switch configuration/control tool
too.... :-)
Good question, but we can only do so much with SNMP anyway - so I don't
see the feature extending much beyond the current. Having better role
based access control is a good thing nonetheless.
So we're all using NETCONF to do this now anyway, right? ;-)
regards,
oliver.
--- End Message ---
--- Begin Message ---
Hi,
On 2014-07-07 16:19, Francesco Schiavarelli wrote:
the attached patch introduces a new configuration directive named
'portctl' that completely disables port configuration changes.
When enabled (default value) it does not change the actual behaviour.
When set to false instead it prevents changing port configuration
(VLAN ID, operational status, etc...) from the web interface while
letting an authorised user change the interface description.
Many thanks for the patch, much appreciated.
I've included this feature in the next point release: 2.028001
I changed the logic and name, however. The name is now portctl_nameonly
and the logic is that this defaults to false and is enabled if set to
true. When true, port control actions are limited to changing interface
name only.
regards,
oliver.
--- End Message ---
------------------------------------------------------------------------------
_______________________________________________
Netdisco mailing list - Digest Mode
[email protected]
https://lists.sourceforge.net/lists/listinfo/netdisco-users
