netdisco-users Digest, Vol 116, Issue 7

Wed, 03 Feb 2016 07:05:44 -0800 

Send netdisco-users mailing list submissions to
        netdisco-users@lists.sourceforge.net

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
        netdisco-users-requ...@lists.sourceforge.net

You can reach the person managing the list at
        netdisco-users-ow...@lists.sourceforge.net

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

Today's Topics:

   1. Re: SNMPv3 Configuration (Oliver Gorwits)
   2. Re: Netdisco 2 - port name problem (Steven Xu)
   3. Re: Netdisco 2 - port name problem (Edward Vopata)
--- Begin Message --- 
Hi Davy,

On 2016-02-02 14:51, Davy PECH wrote:

My problem is that I was unable to validate SNMP version 3 with SHA
and AES.
The configuration file is :
I see you have "priv: AES" and not "proto: AES" in the config below. Could that be it? 

https://metacpan.org/pod/distribution/App-Netdisco/lib/App/Netdisco/Manual/Configuration.pod#snmp_auth

Or else, try AES256.

regards,
oliver.


snmp_auth:
 - tag: 'default_v3'
 user: 'snmpuser'
 auth:
 pass: xxxyyyzzz
 proto: SHA
 priv:
 pass: xxxyyyzzz
 priv: AES
I have this error whith the command : ~/bin/netdisco-do discover -DISQ 
-d 10.2.x.x

SNMP::Info::_global uptime : DISMAN-EVENT-MIB::sysUpTimeInstance :
.1.3.6.1.2.1.1.3.0
SNMP::Info::_global(uptime) Timeout at
/home/netdisco/perl5/lib/perl5/App/Netdisco/Util/SNMP.pm line 176.
[29886] 2016-02-02 08:44:03 debug [10.2.1.11] try_connect with ver: 1, 
class: SNMP::Info::Layer3::Enterasys, comm: <hidden>
SNMP::Info::_global uptime : DISMAN-EVENT-MIB::sysUpTimeInstance :
.1.3.6.1.2.1.1.3.0
SNMP::Info::_global(uptime) Timeout at
/home/netdisco/perl5/lib/perl5/App/Netdisco/Util/SNMP.pm line 176.
[29886] 2016-02-02 08:44:06 debug [10.2.1.11] try_connect with ver: 1, 
class: SNMP::Info, comm: <hidden>
SNMP::Info::_global uptime : DISMAN-EVENT-MIB::sysUpTimeInstance :
.1.3.6.1.2.1.1.3.0
SNMP::Info::_global(uptime) Timeout at
/home/netdisco/perl5/lib/perl5/App/Netdisco/Util/SNMP.pm line 176.
[29886] 2016-02-02 08:44:09 debug [10.2.1.11] try_connect with ver: 3, 
class: SNMP::Info::Layer3::Enterasys, comm: v3user:snmpuser
SNMP::Info::_global uptime : DISMAN-EVENT-MIB::sysUpTimeInstance :
.1.3.6.1.2.1.1.3.0
SNMP::Info::_global(uptime) Timeout at
/home/netdisco/perl5/lib/perl5/App/Netdisco/Util/SNMP.pm line 176.
[29886] 2016-02-02 08:44:12 debug [10.2.1.11] try_connect with ver: 3, 
class: SNMP::Info, comm: v3user:snmpuser
SNMP::Info::_global uptime : DISMAN-EVENT-MIB::sysUpTimeInstance :
.1.3.6.1.2.1.1.3.0
SNMP::Info::_global(uptime) Timeout at
/home/netdisco/perl5/lib/perl5/App/Netdisco/Util/SNMP.pm line 176.
[29886] 2016-02-02 08:44:15 info discover: finished at Tue Feb 2
09:44:15 2016
[29886] 2016-02-02 08:44:15 info discover: status error: discover
failed: could not SNMP connect to 10.2.x.x

With the snmpwalk command , it work's : i have all results ok

snmpwalk -v 3 -u snmpuser -a SHA -A xxxyyyzzz -x AES -X xxxyyyzzz
10.2.x.x -l authpriv

When i try snmp v 3 with SHA and DES in the config file, it work's
too.
I have read the documentation of Network Switch and the version of AES 
used by default is 128 bits.
I also have try several way in the config file (AES(128) or AES[128]
...)

Thank you for your help
Best regard

--- End Message ---
--- Begin Message --- Hi Edward,

Since you're observing that the names change after a couple hours, it leads me to believe that some scheduled job is messing with your data. Can you include your scheduled jobs configuration?

You can also check the status of your scheduled jobs by checking the logs in logs/netdisco-daemon.log and searching for the last logs for a particular device.

I have a hard time imagining what could be causing this problem. When you ran the discover manually, the results are fine, but when some schedule job runs (presumably the scheduled discover), the device port entry is getting the wrong name.

Maybe someone else has had a similar issue before?

Steven

-----Edward Vopata <vop...@ti.com> wrote: -----
To: Steven Xu <stev...@yorku.ca>, <netdisco-users@lists.sourceforge.net>
From: Edward Vopata <vop...@ti.com>
Date: 02/02/2016 01:00PM
Subject: Re: [Netdisco] Netdisco 2 - port name problem


I have about 4300 devices in my netdisco2 database, of which 2200 of these devices are having this ifindex issue.

Attached is a list of device models that are having this issue.
I am currently focusing on the cisco 2911 and 2811 devices.

Attached are some log & data files:

 
Device-before-discover.txt    - this a query of a device before the discovery, showing the problem
                                                  (ie. device_port.port is the ifIndex number)

Device-netdisco-discover.log  - this is the log of the netdisco discover on that device.

Device-after-discover.txt    - this the same query after the discovery.

The view after the discover is how I would expect the device to look.
However, after several hours, the device reverts back to the "before" view,
which is NOT right.

This is a Netdisco 2 problem. 
    I am running an old version of netdisco (based on the 0.96 release),
    with the latest SNMP::Info (version 3.31) and I am not having the problem.

    The same device on the old netdisco does NOT exhibit this problem.

I did intend to reply to the mailing list.

Thanks,

- Ed Vopata


On 02/02/16 09:03, Steven Xu wrote:
Hi Ed,

I suspect the problem lies with the SNMP setup for your routers; netdisco always uses the port name given by SNMP. The problem could also lie in the SNMP::Info implementation for your routers (which netdisco uses to gather information). What model are they?

Some logging code is already present and may already be enough to diagnose your issue.  Run the script bin/netdisco-do to discover a device that has already been discover and is experiencing this problem, optionally with the -D and -S flags (try "bin/netdisco-do help" for more details).

I think, even without the flags, warnings will be present if there is a problem with discovering your device. Do this after you notice that the port name gets changed to the IFindex value. Include the logs or let me know what you find.

Also, I noticed that you didn't include the netdisco mailing list this time. Was this intentional? Others may have more insights into the problem that I don't.

Steven


-----Edward Vopata <vop...@ti.com> wrote: -----
To: Steven Xu <stev...@yorku.ca>
From: Edward Vopata <vop...@ti.com>
Date: 02/02/2016 09:44AM
Subject: Re: [Netdisco] Netdisco 2 - port name problem


It is very difficult to isolate this problem.

An initial device discovery will set the port name to the correct value (ie GigabitEthernet0/0),
but sometime later the value gets changed to the IFindex value.  I have a small group of
routers that are consistently exhibiting this problem, but I haven't been able to get much deeper.

Question:
    Where does the port name (device_port.port) value get set?
        - If it is a few places, then I can add some logging code to detect specific changes.
    Where is the source of the port name?
        - maybe I can add some checks there?

I still don't thing that the issue is a timeout issue.

-- Ed Vopata


On 02/01/16 07:09, Steven Xu wrote:
Hi Edward,

It would help to provide some debug logs, although I'm not entirely familiar with which logs you should be providing.

Steven

-----Edward Vopata <vop...@ti.com> wrote: -----
To: <netdisco-users@lists.sourceforge.net>
From: Edward Vopata <vop...@ti.com>
Date: 01/18/2016 02:05PM
Subject: [Netdisco] Netdisco 2 - port name problem

I am still having the a problem with netdisco 2, where the port
(device_port.port) is getting set to the SNMP ifIndex value of the port
instead of the port name value (ie: GigabitEthernet0/0).   I have tried
adjusting the SNMP retries and SNMP timeouts, but I am still getting the
same results.  An initial discover on the device will set the port to the
correct name value (ie GigabitEthernet0/0), however after a few hours the
port changes to the ifIndex value.

I don't believe that the problem is with the SNMP timeouts, since some
of the devices having the problem are in the same data center and the
netdisco server.

Here is my NetDisco Information:
     Hostname      : netdisco2
     OS            : Ubuntu 14.04.3 LTS
     Perl          : v5.18.2
     App::NetDisco : 2.033004
     DB Schema     : 40
     SNMP::Info    : 3.30
     Apache        : 2.4.7
     Net-SNMP      : 5.7.2
     PostgreSQL    : 9.3.10

Please advise.

Thanks.
-- Ed.

------------------------------------------------------------------------------
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=267308311&iu=/4140
_______________________________________________
Netdisco mailing list
netdisco-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/netdisco-users




[attachment "Netdisco-models.txt" removed by Steven Xu/fs/YorkU]
[attachment "Device-after-discover.txt" removed by Steven Xu/fs/YorkU]
[attachment "Device-before-discover.txt" removed by Steven Xu/fs/YorkU]
[attachment "Device-netdisco-discover.log" removed by Steven Xu/fs/YorkU]
--- End Message ---
--- Begin Message --- 

Attached is the schedule section from my deployment.yml file.
I'm found the logs/netdisco-daemon.log, however I don't find anything about the job scheduling. 

My Log level is set as:
    log: 'warning'
Now you are starting to understand my frustration, this is proving to be a very difficult problem.
Yes, there are other people having this problem. There was a message thread back in November 2015 "Subject: [Netdisco] Some Ports in Portview showing numbers instead of interface ID" 

Thanks,
-- Ed.




On 02/03/16 08:25, Steven Xu wrote:

Hi Edward,
Since you're observing that the names change after a couple hours, it leads me to believe that some scheduled job is messing with your data. Can you include your scheduled jobs configuration?
You can also check the status of your scheduled jobs by checking the logs in logs/netdisco-daemon.log and searching for the last logs for a particular device.
I have a hard time imagining what could be causing this problem. When you ran the discover manually, the results are fine, but when some schedule job runs (presumably the scheduled discover), the device port entry is getting the wrong name. 

Maybe someone else has had a similar issue before?

Steven

-----Edward Vopata <vop...@ti.com> wrote: -----
To: Steven Xu <stev...@yorku.ca>, <netdisco-users@lists.sourceforge.net>
From: Edward Vopata <vop...@ti.com>
Date: 02/02/2016 01:00PM
Subject: Re: [Netdisco] Netdisco 2 - port name problem
I have about 4300 devices in my netdisco2 database, of which 2200 of these devices are having this ifindex issue. 

Attached is a list of device models that are having this issue.
I am currently focusing on the cisco 2911 and 2811 devices.

Attached are some log & data files:
Device-before-discover.txt - this a query of a device before the discovery, showing the problem (ie. device_port.port is the ifIndex number)
Device-netdisco-discover.log - this is the log of the netdisco discover on that device. 

Device-after-discover.txt    - this the same query after the discovery.

The view after the discover is how I would expect the device to look.
However, after several hours, the device reverts back to the "before" view, 
which is NOT right.

This is a Netdisco 2 problem.
    I am running an old version of netdisco (based on the 0.96 release),
with the latest SNMP::Info (version 3.31) and I am not having the problem. 

    The same device on the old netdisco does NOT exhibit this problem.

I did intend to reply to the mailing list.

Thanks,

- Ed Vopata


On 02/02/16 09:03, Steven Xu wrote:

Hi Ed,
I suspect the problem lies with the SNMP setup for your routers; netdisco always uses the port name given by SNMP. The problem could also lie in the SNMP::Info implementation for your routers (which netdisco uses to gather information). What model are they?
Some logging code is already present and may already be enough to diagnose your issue. Run the script bin/netdisco-do to discover a device that has already been discover and is experiencing this problem, optionally with the -D and -S flags (try "bin/netdisco-do help" for more details).
I think, even without the flags, warnings will be present if there is a problem with discovering your device. Do this after you notice that the port name gets changed to the IFindex value. Include the logs or let me know what you find.
Also, I noticed that you didn't include the netdisco mailing list this time. Was this intentional? Others may have more insights into the problem that I don't. 

Steven


-----Edward Vopata <vop...@ti.com> wrote: -----
To: Steven Xu <stev...@yorku.ca>
From: Edward Vopata <vop...@ti.com>
Date: 02/02/2016 09:44AM
Subject: Re: [Netdisco] Netdisco 2 - port name problem


It is very difficult to isolate this problem.
An initial device discovery will set the port name to the correct value (ie GigabitEthernet0/0), but sometime later the value gets changed to the IFindex value. I have a small group of routers that are consistently exhibiting this problem, but I haven't been able to get much deeper. 

Question:
    Where does the port name (device_port.port) value get set?
- If it is a few places, then I can add some logging code to detect specific changes. 
    Where is the source of the port name?
        - maybe I can add some checks there?

I still don't thing that the issue is a timeout issue.

-- Ed Vopata


On 02/01/16 07:09, Steven Xu wrote:

Hi Edward,
It would help to provide some debug logs, although I'm not entirely familiar with which logs you should be providing. 

Steven

-----Edward Vopata <vop...@ti.com> wrote: -----
To: <netdisco-users@lists.sourceforge.net>
From: Edward Vopata <vop...@ti.com>
Date: 01/18/2016 02:05PM
Subject: [Netdisco] Netdisco 2 - port name problem

I am still having the a problem with netdisco 2, where the port
(device_port.port) is getting set to the SNMP ifIndex value of the port
instead of the port name value (ie: GigabitEthernet0/0).   I have tried
adjusting the SNMP retries and SNMP timeouts, but I am still getting the
same results. An initial discover on the device will set the port to the correct name value (ie GigabitEthernet0/0), however after a few hours the 
port changes to the ifIndex value.

I don't believe that the problem is with the SNMP timeouts, since some
of the devices having the problem are in the same data center and the
netdisco server.

Here is my NetDisco Information:
     Hostname      : netdisco2
     OS            : Ubuntu 14.04.3 LTS
     Perl          : v5.18.2
     App::NetDisco : 2.033004
     DB Schema     : 40
     SNMP::Info    : 3.30
     Apache        : 2.4.7
     Net-SNMP      : 5.7.2
     PostgreSQL    : 9.3.10

Please advise.

Thanks.
-- Ed.

------------------------------------------------------------------------------
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=267308311&iu=/4140
_______________________________________________
Netdisco mailing list
netdisco-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/netdisco-users






[attachment "Netdisco-models.txt" removed by Steven Xu/fs/YorkU]
[attachment "Device-after-discover.txt" removed by Steven Xu/fs/YorkU]
[attachment "Device-before-discover.txt" removed by Steven Xu/fs/YorkU]
[attachment "Device-netdisco-discover.log" removed by Steven Xu/fs/YorkU]



##############################################################################
# Schedule:

schedule:
  discoverall:
    when: '1 3 * * *'
  macwalk:
    when:
      min: 20
  arpwalk:
    when:
      min: 50
  nbtwalk:
    when: '0 8 * 1 *'
  expire:
    when: '20 23 * * *'

--- End Message ---
------------------------------------------------------------------------------
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=267308311&iu=/4140
_______________________________________________
Netdisco mailing list - Digest Mode
netdisco-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/netdisco-users

Reply via email to