Send Netdot-users mailing list submissions to
        netdot-users@osl.uoregon.edu

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
        netdot-users-requ...@osl.uoregon.edu

You can reach the person managing the list at
        netdot-users-ow...@osl.uoregon.edu

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Netdot-users digest..."


Today's Topics:

   1. Re: Netdot and device topology via LLDP (Matej Vadnjal)
   2. Re: Netdisco errors or what? (Bernard Fay)
   3. Re: Netdisco errors or what? (Matej Vadnjal)


----------------------------------------------------------------------

Message: 1
Date: Tue, 18 Oct 2016 13:34:47 +0200
From: Matej Vadnjal <matej.vadn...@arnes.si>
Subject: Re: [Netdot-users] Netdot and device topology via LLDP
To: Stefano Martini <s.mart...@ifinet.it>,
        "netdot-users@osl.uoregon.edu" <netdot-users@osl.uoregon.edu>
Message-ID: <55152e1b-5f84-2671-357b-cca67c21e...@arnes.si>
Content-Type: text/plain; charset="windows-1252"

Hi Stefano

It is possible that the LLDP neigbour interface info these devices 
return via SNMP makes it impossible to determine the correct neighbours.

Some devices report the local interface name to their neighbour. Some 
others report ifIndex or a short or long interface name.

I don't have any HP or 3com gear in my network, so I can't be certain 
this is the issue in your case as well.

You'll need do do an snmpwalk for ifTable and lldpRemTable on two 
adjacent devices and compare interface values returned.

Also take a look at the code of SNMP::Info Perl module (this is what 
netdot uses for snmp discovery). You might be able to hack together a 
patch for your device types. If you do, make sure to submit it to 
SNMP::Info developers.


Best regards
Matej Vadnjal


On 10/14/2016 04:13 PM, Stefano Martini wrote:
>
> Hi people,
>
> I am using Netdot 1.6 in a network with 150 switches (HP and 3Com). 
> The configuration parameters of these switches (IP, SNMP community, 
> SNMP version, ?) are stored into the Netdot database. For each switch 
> Netdot correctly collects information such as: device name, system 
> description, interfaces list, ?
>
> All the switches are configured to have LLDP enabled. Some switches 
> have CDP enabled too.
>
> This is the Site.conf file:
>
> ?
>
> TOPO_USE_DP   => 1,
>
> TOPO_WEIGHT_DP => 8,
>
> ?
>
> ADD_UNKNOWN_DP_DEVS => 1,
>
> ?
>
> The updatedevice.pl (run with ?T ?D ?A ?I ) gets uplinks only for 
> devices with CDP enabled. All devices with LLDP only have no uplinks.
>
> Does Netdot support LLDP enabled devices ?
>
> If yes, how can I solve the missing of uplinks for devices with LLDP ?
>
> Thanks in advance
>
> Stefano
>
>
>
> _______________________________________________
> Netdot-users mailing list
> Netdot-users@osl.uoregon.edu
> https://osl.uoregon.edu/mailman/listinfo/netdot-users

-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
http://osl.uoregon.edu/pipermail/netdot-users/attachments/20161018/b60099cb/attachment-0001.html
 

------------------------------

Message: 2
Date: Tue, 18 Oct 2016 07:42:00 -0400
From: Bernard Fay <bernard....@gmail.com>
Subject: Re: [Netdot-users] Netdisco errors or what?
To: netdot-users@osl.uoregon.edu
Message-ID:
        <cah3ae4bvbna6mw_b4skw3anqxyymxow-r+7yguvslj9a4m8...@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"

So far, I didn't comment out any mibdirs. I was trying to get netdot
working first then clean after.  I'll have to do it the other way around.

I don't know if I want to patch and I have to maintain it separately
thought I might have to do it. We have so many different kinds of
equipment. Do you remember where you patched it?  Can you tell me?

Thanks,
Bernard


On Tue, Oct 18, 2016 at 7:23 AM, Matej Vadnjal <matej.vadn...@arnes.si>
wrote:

> Which mibdirs did you uncomment in snmp.conf?
>
> The problem is that net-snmp library has a hard limit of 4096 textual
> conventions. See: https://sourceforge.net/p/net-
> snmp/mailman/message/16144537/
>
> If you try to load enough mibs to go over this limit, you'll get the
> warnings you're getting.
>
> You can:
>
> * only use mibdirs you really need in snmp.conf
> * ask the developers on net-snmp list to increase this limit
> * patch net-snmp yourself and raise the limit yourself (that's what I did)
>
> Regards
> Matej Vadnjal
>
> On 10/17/2016 08:18 PM, Bernard Fay wrote:
>
> When I run snmp command or netdot scripts, I see a lot of the following
> errors:
>
> Too many textual conventions (INTEGER): At line 273 in
> /usr/local/netdisco/mibs/cisco/CISCO-DIGITAL-MEDIA-SYSTEMS-MIB.my
> : (is a reserved word): At line 273 in /usr/local/netdisco/mibs/
> cisco/CISCO-DIGITAL-MEDIA-SYSTEMS-MIB.my
> Bad operator ((): At line 274 in /usr/local/netdisco/mibs/
> cisco/CISCO-DIGITAL-MEDIA-SYSTEMS-MIB.my
> Too many textual conventions (OCTETSTRING): At line 52 in
> /usr/local/netdisco/mibs/cisco/CISCO-ATM-SWITCH-ADDR-MIB.my
> : (is a reserved word): At line 52 in /usr/local/netdisco/mibs/
> cisco/CISCO-ATM-SWITCH-ADDR-MIB.my
> SIZE (is a reserved word): At line 52 in /usr/local/netdisco/mibs/
> cisco/CISCO-ATM-SWITCH-ADDR-MIB.my
> 13 (is a reserved word): At line 52 in /usr/local/netdisco/mibs/
> cisco/CISCO-ATM-SWITCH-ADDR-MIB.my
> 20 (is a reserved word): At line 52 in /usr/local/netdisco/mibs/
> cisco/CISCO-ATM-SWITCH-ADDR-MIB.my
> ) (is a reserved word): At line 55 in /usr/local/netdisco/mibs/
> cisco/CISCO-ATM-SWITCH-ADDR-MIB.my
> OBJECT-TYPE (is a reserved word): At line 56 in /usr/local/netdisco/mibs/
> cisco/CISCO-ATM-SWITCH-ADDR-MIB.my
>
> [snip]
>
> STATUS (is a reserved word): At line 102 in /usr/local/netdisco/mibs/rfc/
> SYSLOG-MSG-MIB.txt
> DESCRIPTION (is a reserved word): At line 121 in
> /usr/local/netdisco/mibs/rfc/SYSLOG-MSG-MIB.txt
> REFERENCE (is a reserved word): At line 123 in
> /usr/local/netdisco/mibs/rfc/SYSLOG-MSG-MIB.txt
> SYNTAX (is a reserved word): At line 124 in /usr/local/netdisco/mibs/rfc/
> SYSLOG-MSG-MIB.txt
> Did not find 'SyslogFacility' in module SYSLOG-TC-MIB
> (/usr/local/netdisco/mibs/rfc/SYSLOG-MSG-MIB.txt)
> Did not find 'SyslogSeverity' in module SYSLOG-TC-MIB
> (/usr/local/netdisco/mibs/rfc/SYSLOG-MSG-MIB.txt)
> Cannot adopt OID in LLDP-EXT-DOT1-EVB-EXTENSIONS-MIB:
> lldpV2Xdot1RemCdcpTlvEntry ::= { lldpV2Xdot1RemCdcpTlvTable 1 }
> Cannot adopt OID in Finisher-MIB: finDeviceAttributeTable ::= {
> finDeviceAttribute 1 }
> Cannot adopt OID in UCD-DEMO-MIB: ucdDemoPublic ::= { ucdDemoMIBObjects 1 }
> Cannot adopt OID in LLDP-EXT-DOT1-PE-MIB: lldpXdot1PeLocPECSPAddress ::= {
> lldpXdot1PeLocPortExtensionEntry 3 }
> Cannot adopt OID in LLDP-EXT-DOT1-PE-MIB: lldpXdot1PeLocPEAddress ::= {
> lldpXdot1PeLocPortExtensionEntry 2 }
>
> [snip]
>
> Cannot adopt OID in NET-SNMP-EXTEND-MIB: nsExtendOutLine ::= {
> nsExtendOutput2Entry 2 }
> Cannot adopt OID in LLDP-EXT-DOT1-PE-MIB: lldpXdot1PeCompliance ::= {
> lldpXdot1PeCompliances 1 }
> Cannot adopt OID in LLDP-EXT-DOT1-EVB-EXTENSIONS-MIB:
> lldpV2Xdot1RemEvbTlvTable ::= { lldpXdot1EvbRemoteData 1 }
> Cannot adopt OID in LLDP-EXT-DOT1-EVB-EXTENSIONS-MIB:
> lldpV2Xdot1RemCdcpTlvTable ::= { lldpXdot1EvbRemoteData 2 }
>
>
> I have nearly 6000 lines similar to the above.
>
> Did I do something wrong in the installation of Netdot or Netdisco?
>
> Thanks,
> Bernard
>
>
>
> _______________________________________________
> Netdot-users mailing 
> listNetdot-users@osl.uoregon.eduhttps://osl.uoregon.edu/mailman/listinfo/netdot-users
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
http://osl.uoregon.edu/pipermail/netdot-users/attachments/20161018/b314a326/attachment-0001.html
 

------------------------------

Message: 3
Date: Tue, 18 Oct 2016 13:53:02 +0200
From: Matej Vadnjal <matej.vadn...@arnes.si>
Subject: Re: [Netdot-users] Netdisco errors or what?
To: Bernard Fay <bernard....@gmail.com>, netdot-users@osl.uoregon.edu
Message-ID: <f8d39396-ddfd-1d5b-6b2c-c7213f3ba...@arnes.si>
Content-Type: text/plain; charset="windows-1252"

Yeah, it's a pain to maintain patchsets for common software for us too.

I've attached a patch to increase MAXTC. And also a patch for the spec 
file in case you're using RPMs and you'll be making your own.

Best regards
Matej


On 10/18/2016 01:42 PM, Bernard Fay wrote:
> So far, I didn't comment out any mibdirs. I was trying to get netdot 
> working first then clean after.  I'll have to do it the other way around.
>
> I don't know if I want to patch and I have to maintain it separately 
> thought I might have to do it. We have so many different kinds of 
> equipment. Do you remember where you patched it?  Can you tell me?
>
> Thanks,
> Bernard
>
>
> On Tue, Oct 18, 2016 at 7:23 AM, Matej Vadnjal <matej.vadn...@arnes.si 
> <mailto:matej.vadn...@arnes.si>> wrote:
>
>     Which mibdirs did you uncomment in snmp.conf?
>
>     The problem is that net-snmp library has a hard limit of 4096
>     textual conventions. See:
>     https://sourceforge.net/p/net-snmp/mailman/message/16144537/
>     <https://sourceforge.net/p/net-snmp/mailman/message/16144537/>
>
>     If you try to load enough mibs to go over this limit, you'll get
>     the warnings you're getting.
>
>     You can:
>
>     * only use mibdirs you really need in snmp.conf
>     * ask the developers on net-snmp list to increase this limit
>     * patch net-snmp yourself and raise the limit yourself (that's
>     what I did)
>
>     Regards
>     Matej Vadnjal
>
>
>     On 10/17/2016 08:18 PM, Bernard Fay wrote:
>>     When I run snmp command or netdot scripts, I see a lot of the
>>     following errors:
>>
>>     Too many textual conventions (INTEGER): At line 273 in
>>     /usr/local/netdisco/mibs/cisco/CISCO-DIGITAL-MEDIA-SYSTEMS-MIB.my
>>     : (is a reserved word): At line 273 in
>>     /usr/local/netdisco/mibs/cisco/CISCO-DIGITAL-MEDIA-SYSTEMS-MIB.my
>>     Bad operator ((): At line 274 in
>>     /usr/local/netdisco/mibs/cisco/CISCO-DIGITAL-MEDIA-SYSTEMS-MIB.my
>>     Too many textual conventions (OCTETSTRING): At line 52 in
>>     /usr/local/netdisco/mibs/cisco/CISCO-ATM-SWITCH-ADDR-MIB.my
>>     : (is a reserved word): At line 52 in
>>     /usr/local/netdisco/mibs/cisco/CISCO-ATM-SWITCH-ADDR-MIB.my
>>     SIZE (is a reserved word): At line 52 in
>>     /usr/local/netdisco/mibs/cisco/CISCO-ATM-SWITCH-ADDR-MIB.my
>>     13 (is a reserved word): At line 52 in
>>     /usr/local/netdisco/mibs/cisco/CISCO-ATM-SWITCH-ADDR-MIB.my
>>     20 (is a reserved word): At line 52 in
>>     /usr/local/netdisco/mibs/cisco/CISCO-ATM-SWITCH-ADDR-MIB.my
>>     ) (is a reserved word): At line 55 in
>>     /usr/local/netdisco/mibs/cisco/CISCO-ATM-SWITCH-ADDR-MIB.my
>>     OBJECT-TYPE (is a reserved word): At line 56 in
>>     /usr/local/netdisco/mibs/cisco/CISCO-ATM-SWITCH-ADDR-MIB.my
>>
>>     [snip]
>>
>>     STATUS (is a reserved word): At line 102 in
>>     /usr/local/netdisco/mibs/rfc/SYSLOG-MSG-MIB.txt
>>     DESCRIPTION (is a reserved word): At line 121 in
>>     /usr/local/netdisco/mibs/rfc/SYSLOG-MSG-MIB.txt
>>     REFERENCE (is a reserved word): At line 123 in
>>     /usr/local/netdisco/mibs/rfc/SYSLOG-MSG-MIB.txt
>>     SYNTAX (is a reserved word): At line 124 in
>>     /usr/local/netdisco/mibs/rfc/SYSLOG-MSG-MIB.txt
>>     Did not find 'SyslogFacility' in module SYSLOG-TC-MIB
>>     (/usr/local/netdisco/mibs/rfc/SYSLOG-MSG-MIB.txt)
>>     Did not find 'SyslogSeverity' in module SYSLOG-TC-MIB
>>     (/usr/local/netdisco/mibs/rfc/SYSLOG-MSG-MIB.txt)
>>     Cannot adopt OID in LLDP-EXT-DOT1-EVB-EXTENSIONS-MIB:
>>     lldpV2Xdot1RemCdcpTlvEntry ::= { lldpV2Xdot1RemCdcpTlvTable 1 }
>>     Cannot adopt OID in Finisher-MIB: finDeviceAttributeTable ::= {
>>     finDeviceAttribute 1 }
>>     Cannot adopt OID in UCD-DEMO-MIB: ucdDemoPublic ::= {
>>     ucdDemoMIBObjects 1 }
>>     Cannot adopt OID in LLDP-EXT-DOT1-PE-MIB:
>>     lldpXdot1PeLocPECSPAddress ::= { lldpXdot1PeLocPortExtensionEntry 3 }
>>     Cannot adopt OID in LLDP-EXT-DOT1-PE-MIB: lldpXdot1PeLocPEAddress
>>     ::= { lldpXdot1PeLocPortExtensionEntry 2 }
>>
>>     [snip]
>>
>>     Cannot adopt OID in NET-SNMP-EXTEND-MIB: nsExtendOutLine ::= {
>>     nsExtendOutput2Entry 2 }
>>     Cannot adopt OID in LLDP-EXT-DOT1-PE-MIB: lldpXdot1PeCompliance
>>     ::= { lldpXdot1PeCompliances 1 }
>>     Cannot adopt OID in LLDP-EXT-DOT1-EVB-EXTENSIONS-MIB:
>>     lldpV2Xdot1RemEvbTlvTable ::= { lldpXdot1EvbRemoteData 1 }
>>     Cannot adopt OID in LLDP-EXT-DOT1-EVB-EXTENSIONS-MIB:
>>     lldpV2Xdot1RemCdcpTlvTable ::= { lldpXdot1EvbRemoteData 2 }
>>
>>
>>     I have nearly 6000 lines similar to the above.
>>
>>     Did I do something wrong in the installation of Netdot or Netdisco?
>>
>>     Thanks,
>>     Bernard
>>
>>
>>
>>     _______________________________________________
>>     Netdot-users mailing list
>>     Netdot-users@osl.uoregon.edu <mailto:Netdot-users@osl.uoregon.edu>
>>     https://osl.uoregon.edu/mailman/listinfo/netdot-users
>>     <https://osl.uoregon.edu/mailman/listinfo/netdot-users>
>
> _______________________________________________
> Netdot-users mailing list
> Netdot-users@osl.uoregon.edu
> https://osl.uoregon.edu/mailman/listinfo/netdot-users
-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
http://osl.uoregon.edu/pipermail/netdot-users/attachments/20161018/10eaec15/attachment.html
 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: net-snmp-5.7.2-increase-maxtc.patch
Type: text/x-patch
Size: 329 bytes
Desc: not available
Url : 
http://osl.uoregon.edu/pipermail/netdot-users/attachments/20161018/10eaec15/attachment.bin
 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: net-snmp.spec.patch
Type: text/x-patch
Size: 1104 bytes
Desc: not available
Url : 
http://osl.uoregon.edu/pipermail/netdot-users/attachments/20161018/10eaec15/attachment-0001.bin
 

------------------------------

_______________________________________________
Netdot-users mailing list
Netdot-users@osl.uoregon.edu
https://osl.uoregon.edu/mailman/listinfo/netdot-users


End of Netdot-users Digest, Vol 91, Issue 4
*******************************************

Reply via email to