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 #1768] Problem adding ruckus zone director and
aps ([email protected])
2. [Netdot - Bug #1768] (Closed) Problem adding ruckus zone
director and aps ([email protected])
3. [Netdot - Bug #1761] (Closed) Adding an HP ProCurve switch
fails: "Invalid name: procurve j9029a. Contains invalid
characters" ([email protected])
4. [Netdot - Feature #531] Solve the problem of overlapping VLAN
and address space ([email protected])
----------------------------------------------------------------------
Message: 1
Date: Fri, 19 Jul 2013 13:08:36 -0700
From: [email protected]
Subject: [Netdot-devel] [Netdot - Bug #1768] Problem adding ruckus
zone director and aps
To: [email protected], [email protected]
Message-ID: <[email protected]>
Content-Type: text/plain; charset=utf-8
Issue #1768 has been updated by Carlos Vicente.
Category set to DeviceManagement
Resolution set to wontfix
Andy, glad you made it work.
Your modifications should be submitted to the SNMP::Info Sourceforge page
(notice that Netdisco and SNMP::Info are two separate projects).
Regards,
cv
----------------------------------------
Bug #1768: Problem adding ruckus zone director and aps
https://osl.uoregon.edu/redmine/issues/1768#change-3099
Author: Andy Linton
Status: New
Priority: Normal
Assignee:
Category: DeviceManagement
Target version:
Resolution: wontfix
I'm seeing updatedevices.pl complaining about adding these devices:
# bin/updatedevices.pl -H 10.0.14.3 -I -c somestring -d
INFO - bin/updatedevices.pl started at Tue Jul 16 11:52:09 2013
INFO - Updating single device: 10.0.14.3
DEBUG - Device::search: Address 10.0.14.3 exists but no Device associated
DEBUG - Device::_get_snmp_session: Trying SNMPv2 session with 10.0.14.3,
community bArtj93ZVc8kV
SNMP::Info::init() - Adding new mibdir:/usr/share/netdisco/mibs/allied
SNMP::Info::init() - Adding new mibdir:/usr/share/netdisco/mibs/arista
SNMP::Info::init() - Adding new mibdir:/usr/share/netdisco/mibs/aruba
SNMP::Info::init() - Adding new mibdir:/usr/share/netdisco/mibs/asante
SNMP::Info::init() - Adding new mibdir:/usr/share/netdisco/mibs/cabletron
SNMP::Info::init() - Adding new mibdir:/usr/share/netdisco/mibs/cisco
SNMP::Info::init() - Adding new mibdir:/usr/share/netdisco/mibs/cyclades
SNMP::Info::init() - Adding new mibdir:/usr/share/netdisco/mibs/dell
SNMP::Info::init() - Adding new mibdir:/usr/share/netdisco/mibs/enterasys
SNMP::Info::init() - Adding new mibdir:/usr/share/netdisco/mibs/extreme
SNMP::Info::init() - Adding new mibdir:/usr/share/netdisco/mibs/foundry
SNMP::Info::init() - Adding new mibdir:/usr/share/netdisco/mibs/hp
SNMP::Info::init() - Adding new mibdir:/usr/share/netdisco/mibs/juniper
SNMP::Info::init() - Adding new mibdir:/usr/share/netdisco/mibs/netscreen
SNMP::Info::init() - Adding new mibdir:/usr/share/netdisco/mibs/net-snmp
SNMP::Info::init() - Adding new mibdir:/usr/share/netdisco/mibs/nortel
SNMP::Info::init() - Adding new mibdir:/usr/share/netdisco/mibs/rfc
SNMP::Info::init() - Adding new mibdir:/usr/share/netdisco/mibs/ruckus
SNMP::Info::_global layers : sysServices.0
SNMP::Info::_global(layers) NOSUCHINSTANCE at
/usr/local/netdot/lib/Netdot/Model/Device.pm line 3941
SNMP::Info::_global description : sysDescr.0
Device doesn't implement sysServices but did return sysDescr. Might give
unexpected results.
at /usr/local/netdot/lib/Netdot/Model/Device.pm line 3941
SNMP::Info::_global id : sysObjectID.0
SNMP::Info 2.08
SNMP::Info::device_type() layers:00000000 id:25053 sysDescr:"Ruckus Wireless
zd1112"
ERROR: Device::_get_snmp_session: SNMPv2 error: device 10.0.14.3, community
'somestring': SNMP::Info::_global(layers) NOSUCHINSTANCE
An snmpwalk of the device shows the following (trimmed):
SNMPv2-MIB::sysDescr.0 = STRING: "Ruckus Wireless zd1112"
SNMPv2-MIB::sysObjectID.0 = OID: SNMPv2-SMI::enterprises.25053.3.1.5.2
DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (920379204) 106 days,
12:36:32.04
SNMPv2-MIB::sysContact.0 = STRING: "[email protected]"
SNMPv2-MIB::sysName.0 = STRING: "wn016-zd1"
SNMPv2-MIB::sysLocation.0 = STRING: "Citylink Ltd"
SNMPv2-MIB::sysORLastChange.0 = Timeticks: (101) 0:00:01.01
SNMPv2-MIB::sysORID.1 = OID: SNMPv2-MIB::snmpMIB
SNMPv2-MIB::sysORID.2 = OID: SNMP-VIEW-BASED-ACM-MIB::vacmBasicGroup
SNMPv2-MIB::sysORID.3 = OID: SNMP-FRAMEWORK-MIB::snmpFrameworkMIBCompliance
SNMPv2-MIB::sysORID.4 = OID: SNMP-MPD-MIB::snmpMPDCompliance
SNMPv2-MIB::sysORID.5 = OID: SNMP-USER-BASED-SM-MIB::usmMIBCompliance
SNMPv2-MIB::sysORID.6 = OID: TCP-MIB::tcpMIB
SNMPv2-MIB::sysORID.7 = OID: IP-MIB::ip
SNMPv2-MIB::sysORID.8 = OID: UDP-MIB::udpMIB
SNMPv2-MIB::sysORDescr.1 = STRING: The MIB module for SNMPv2 entities
SNMPv2-MIB::sysORDescr.2 = STRING: View-based Access Control Model for SNMP.
SNMPv2-MIB::sysORDescr.3 = STRING: The SNMP Management Architecture MIB.
SNMPv2-MIB::sysORDescr.4 = STRING: The MIB for Message Processing and
Dispatching.
SNMPv2-MIB::sysORDescr.5 = STRING: The management information definitions for
the SNMP User-based Security Model.
SNMPv2-MIB::sysORDescr.6 = STRING: The MIB module for managing TCP
implementations
SNMPv2-MIB::sysORDescr.7 = STRING: The MIB module for managing IP and ICMP
implementations
SNMPv2-MIB::sysORDescr.8 = STRING: The MIB module for managing UDP
implementations
.....
--
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: Fri, 19 Jul 2013 13:09:17 -0700
From: [email protected]
Subject: [Netdot-devel] [Netdot - Bug #1768] (Closed) Problem adding
ruckus zone director and aps
To: [email protected], [email protected]
Message-ID: <[email protected]>
Content-Type: text/plain; charset=utf-8
Issue #1768 has been updated by Carlos Vicente.
Status changed from New to Closed
----------------------------------------
Bug #1768: Problem adding ruckus zone director and aps
https://osl.uoregon.edu/redmine/issues/1768#change-3100
Author: Andy Linton
Status: Closed
Priority: Normal
Assignee:
Category: DeviceManagement
Target version:
Resolution: wontfix
I'm seeing updatedevices.pl complaining about adding these devices:
# bin/updatedevices.pl -H 10.0.14.3 -I -c somestring -d
INFO - bin/updatedevices.pl started at Tue Jul 16 11:52:09 2013
INFO - Updating single device: 10.0.14.3
DEBUG - Device::search: Address 10.0.14.3 exists but no Device associated
DEBUG - Device::_get_snmp_session: Trying SNMPv2 session with 10.0.14.3,
community bArtj93ZVc8kV
SNMP::Info::init() - Adding new mibdir:/usr/share/netdisco/mibs/allied
SNMP::Info::init() - Adding new mibdir:/usr/share/netdisco/mibs/arista
SNMP::Info::init() - Adding new mibdir:/usr/share/netdisco/mibs/aruba
SNMP::Info::init() - Adding new mibdir:/usr/share/netdisco/mibs/asante
SNMP::Info::init() - Adding new mibdir:/usr/share/netdisco/mibs/cabletron
SNMP::Info::init() - Adding new mibdir:/usr/share/netdisco/mibs/cisco
SNMP::Info::init() - Adding new mibdir:/usr/share/netdisco/mibs/cyclades
SNMP::Info::init() - Adding new mibdir:/usr/share/netdisco/mibs/dell
SNMP::Info::init() - Adding new mibdir:/usr/share/netdisco/mibs/enterasys
SNMP::Info::init() - Adding new mibdir:/usr/share/netdisco/mibs/extreme
SNMP::Info::init() - Adding new mibdir:/usr/share/netdisco/mibs/foundry
SNMP::Info::init() - Adding new mibdir:/usr/share/netdisco/mibs/hp
SNMP::Info::init() - Adding new mibdir:/usr/share/netdisco/mibs/juniper
SNMP::Info::init() - Adding new mibdir:/usr/share/netdisco/mibs/netscreen
SNMP::Info::init() - Adding new mibdir:/usr/share/netdisco/mibs/net-snmp
SNMP::Info::init() - Adding new mibdir:/usr/share/netdisco/mibs/nortel
SNMP::Info::init() - Adding new mibdir:/usr/share/netdisco/mibs/rfc
SNMP::Info::init() - Adding new mibdir:/usr/share/netdisco/mibs/ruckus
SNMP::Info::_global layers : sysServices.0
SNMP::Info::_global(layers) NOSUCHINSTANCE at
/usr/local/netdot/lib/Netdot/Model/Device.pm line 3941
SNMP::Info::_global description : sysDescr.0
Device doesn't implement sysServices but did return sysDescr. Might give
unexpected results.
at /usr/local/netdot/lib/Netdot/Model/Device.pm line 3941
SNMP::Info::_global id : sysObjectID.0
SNMP::Info 2.08
SNMP::Info::device_type() layers:00000000 id:25053 sysDescr:"Ruckus Wireless
zd1112"
ERROR: Device::_get_snmp_session: SNMPv2 error: device 10.0.14.3, community
'somestring': SNMP::Info::_global(layers) NOSUCHINSTANCE
An snmpwalk of the device shows the following (trimmed):
SNMPv2-MIB::sysDescr.0 = STRING: "Ruckus Wireless zd1112"
SNMPv2-MIB::sysObjectID.0 = OID: SNMPv2-SMI::enterprises.25053.3.1.5.2
DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (920379204) 106 days,
12:36:32.04
SNMPv2-MIB::sysContact.0 = STRING: "[email protected]"
SNMPv2-MIB::sysName.0 = STRING: "wn016-zd1"
SNMPv2-MIB::sysLocation.0 = STRING: "Citylink Ltd"
SNMPv2-MIB::sysORLastChange.0 = Timeticks: (101) 0:00:01.01
SNMPv2-MIB::sysORID.1 = OID: SNMPv2-MIB::snmpMIB
SNMPv2-MIB::sysORID.2 = OID: SNMP-VIEW-BASED-ACM-MIB::vacmBasicGroup
SNMPv2-MIB::sysORID.3 = OID: SNMP-FRAMEWORK-MIB::snmpFrameworkMIBCompliance
SNMPv2-MIB::sysORID.4 = OID: SNMP-MPD-MIB::snmpMPDCompliance
SNMPv2-MIB::sysORID.5 = OID: SNMP-USER-BASED-SM-MIB::usmMIBCompliance
SNMPv2-MIB::sysORID.6 = OID: TCP-MIB::tcpMIB
SNMPv2-MIB::sysORID.7 = OID: IP-MIB::ip
SNMPv2-MIB::sysORID.8 = OID: UDP-MIB::udpMIB
SNMPv2-MIB::sysORDescr.1 = STRING: The MIB module for SNMPv2 entities
SNMPv2-MIB::sysORDescr.2 = STRING: View-based Access Control Model for SNMP.
SNMPv2-MIB::sysORDescr.3 = STRING: The SNMP Management Architecture MIB.
SNMPv2-MIB::sysORDescr.4 = STRING: The MIB for Message Processing and
Dispatching.
SNMPv2-MIB::sysORDescr.5 = STRING: The management information definitions for
the SNMP User-based Security Model.
SNMPv2-MIB::sysORDescr.6 = STRING: The MIB module for managing TCP
implementations
SNMPv2-MIB::sysORDescr.7 = STRING: The MIB module for managing IP and ICMP
implementations
SNMPv2-MIB::sysORDescr.8 = STRING: The MIB module for managing UDP
implementations
.....
--
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: Fri, 19 Jul 2013 13:13:36 -0700
From: [email protected]
Subject: [Netdot-devel] [Netdot - Bug #1761] (Closed) Adding an HP
ProCurve switch fails: "Invalid name: procurve j9029a. Contains
invalid characters"
To: [email protected], [email protected]
Message-ID: <[email protected]>
Content-Type: text/plain; charset=utf-8
Issue #1761 has been updated by Carlos Vicente.
Status changed from New to Closed
Resolution set to worksforme
In netdot, device names are DNS records. When discovering a device, it tries to
assign a name by resolving the IP address. If a PTR record doesn't exist in DNS
for that IP address, Netdot tries to use the device's system name (sysName from
SNMP).
Since the value of your system name contains spaces (which are invalid in DNS
records), it fails.
----------------------------------------
Bug #1761: Adding an HP ProCurve switch fails: "Invalid name: procurve j9029a.
Contains invalid characters"
https://osl.uoregon.edu/redmine/issues/1761#change-3101
Author: Chris Wilson
Status: Closed
Priority: Normal
Assignee:
Category:
Target version:
Resolution: worksforme
I tried to discover one of my switches by its IP address, 192.168.2.11.
The first page looks OK, saying:
<pre>
Description PROCURVE J9029A - PA.03.01
</pre>
(which I can't change)
But when I click the Update button, I get this error:
<pre>
updatedevice.html produced the following error:
Invalid name: procurve j9029a. Contains invalid characters
</pre>
And the device seems not to be added to the database. I can't see any option to
change or override this name anywhere, and adding a network device by hand
seems to be a pretty painful process involving defining all the interfaces by
hand.
What am I doing wrong?
--
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: Fri, 19 Jul 2013 15:52:10 -0700
From: [email protected]
Subject: [Netdot-devel] [Netdot - Feature #531] Solve the problem of
overlapping VLAN and address space
To: [email protected], [email protected]
Cc: [email protected]
Message-ID: <[email protected]>
Content-Type: text/plain; charset=utf-8
Issue #531 has been updated by James Bothe.
Carlos Vicente wrote:
> Solve the problem of overlapping VLAN and address space
Where do I donate for this? Ultimately looking for multi-site support, the
same VLAN number attached to specific site/datacenter.
----------------------------------------
Feature #531: Solve the problem of overlapping VLAN and address space
https://osl.uoregon.edu/redmine/issues/531#change-3102
Author: Carlos Vicente
Status: New
Priority: Normal
Assignee: Carlos Vicente
Category:
Target version: 1.0
Resolution:
Solve the problem of overlapping VLAN and address space
--
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 76, Issue 13
********************************************
