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: Netdisco 2 - port name problem (Edward Vopata)
2. Re: Netdisco 2 - port name problem (Jeroen van Ingen)
3. Re: Netdisco 2 - port name problem (Edward Vopata)
4. Re: Netdisco 2 - port name problem (Jeroen van Ingen)
--- Begin Message ---
I am still having a problem with Netdisco 2, where the port
(device_port.port) is being set to the SNMP ifIndex value of the port
instead of the port name value (ie: GigabitEthernet0/0).
I have been having this problem for several months (almost a full year).
An initial discover on the device will set the port to the correct name
value (ie GigabitEthernet0/0), however the port will often get changed
back to the ifIndex value. Once the port name gets set to the ifIndex
value, then the arpnip and macsuck procedures are no long able to match
the port from the arp or mac data with the port in the database, (that
is to say "GigabitEthernet0/0" != '3').
This problem make NetDisco 2, virtually useless and unreliable.
Here is my NetDisco Information:
Hostname : netdisco2
OS : Ubuntu 14.04.4 LTS
Perl : v5.18.2
App::NetDisco : 2.033006
DB Schema : 40
SNMP::Info : 3.31
Apache : 2.4.7
Net-SNMP : 5.7.2
PostgreSQL : 9.3.12
Is anyone else having this problem?
Does anyone have a recommendation on how to fix this problem?
Thanks.
--- End Message ---
--- Begin Message ---
Hi Edward,
I've not seen this issue in our network, as far as I can see the
interface names are stable.
You posted a discover log earlier; reading through it, I noticed that
there's a lot of lines regarding "Looping". I believe that indicates
Netdisco getting back SNMP responses with OIDs that are not ordered
correctly.
I'm not sure what could be causing this. Usually receiving SNMP
responses with OIDs returned out-of-order (ie not steadily incrementing)
is caused by bugs on the SNMP agent (ie device), but then it's usually
easy to reproduce and ND2 behavior would be expected to be the same as ND1.
Just a few random ideas:
- Does the number of (virtual) interfaces on these Cisco 2800's change
dynamically, eg do they terminate VPN sessions or VoIP / PSTN phone
calls? I've seen devices where (in general) adding/removing instances
from SNMP tables can trigger bugs in OID sorting.
- Did you try turning SNMP bulkwalk off for the devices with issues?
(bulkwalk_no directive in deployment.yml iirc)
- Is there any way that SNMP responses can be received out-of-order?
(very very unlikely TBH)
- Is it possible to upgrade the IOS on one of the affected devices to a
more recent version? Looks like the example device still runs a pretty
old IOS.
- When you run several consecutive tests on the command line, eg using
'snmpbulkwalk -c <community> <device> .1' to retrieve all SNMP data from
a device, does each walk complete without snmpbulkwalk giving errors
about a non-increasing OID?
Regards,
Jeroen van Ingen
ICT Service Centre
University of Twente, P.O.Box 217, 7500 AE Enschede, The Netherlands
On 04/19/2016 03:41 PM, Edward Vopata wrote:
I am still having a problem with Netdisco 2, where the port
(device_port.port) is being set to the SNMP ifIndex value of the port
instead of the port name value (ie: GigabitEthernet0/0).
I have been having this problem for several months (almost a full year).
An initial discover on the device will set the port to the correct name
value (ie GigabitEthernet0/0), however the port will often get changed
back to the ifIndex value. Once the port name gets set to the ifIndex
value, then the arpnip and macsuck procedures are no long able to match
the port from the arp or mac data with the port in the database, (that
is to say "GigabitEthernet0/0" != '3').
This problem make NetDisco 2, virtually useless and unreliable.
Here is my NetDisco Information:
Hostname : netdisco2
OS : Ubuntu 14.04.4 LTS
Perl : v5.18.2
App::NetDisco : 2.033006
DB Schema : 40
SNMP::Info : 3.31
Apache : 2.4.7
Net-SNMP : 5.7.2
PostgreSQL : 9.3.12
Is anyone else having this problem?
Does anyone have a recommendation on how to fix this problem?
Thanks.
------------------------------------------------------------------------------
Find and fix application performance issues faster with Applications Manager
Applications Manager provides deep performance insights into multiple tiers of
your business applications. It resolves application problems quickly and
reduces your MTTR. Get your free trial!
https://ad.doubleclick.net/ddm/clk/302982198;130105516;z
_______________________________________________
Netdisco mailing list
netdisco-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/netdisco-users
--- End Message ---
--- Begin Message ---
> - Does the number of (virtual) interfaces on these Cisco 2800's
change dynamically,
No. I don't think those 2800 are doing any virtual/dynamic interfaces.
> - Did you try turning SNMP bulkwalk off for the devices with issues?
(bulkwalk_no directive in deployment.yml iirc)
I think I tried that at one point,
> - Is there any way that SNMP responses can be received out-of-order?
(very very unlikely TBH)
I don't think so. My NetDisco 1 system is working just fine,
> - Is it possible to upgrade the IOS on one of the affected devices to
a more recent version?
Probably not. I'm in an enterprise environment, router upgrades have to
be planned
months/years in advanced.
> - When you run several consecutive tests on the command line, eg
using 'snmpbulkwalk -c <community> <device> .1' to retrieve all SNMP
data from a device, does each walk complete without snmpbulkwalk giving
errors about a non-increasing OID?
$ snmpbulkwalk -v2c -c {comm} {host} .1
I've tried several devices and I get a bunch of data followed by a
"Timeout: No Response from"
message.
Like I said, my NetDisco 1 is functioning reasonably well.
But the NetDisco 2 is flaky.
-- Ed.
On 04/19/16 09:24, Jeroen van Ingen wrote:
Hi Edward,
I've not seen this issue in our network, as far as I can see the
interface names are stable.
You posted a discover log earlier; reading through it, I noticed that
there's a lot of lines regarding "Looping". I believe that indicates
Netdisco getting back SNMP responses with OIDs that are not ordered
correctly.
I'm not sure what could be causing this. Usually receiving SNMP
responses with OIDs returned out-of-order (ie not steadily
incrementing) is caused by bugs on the SNMP agent (ie device), but
then it's usually easy to reproduce and ND2 behavior would be expected
to be the same as ND1.
Just a few random ideas:
- Does the number of (virtual) interfaces on these Cisco 2800's change
dynamically, eg do they terminate VPN sessions or VoIP / PSTN phone
calls? I've seen devices where (in general) adding/removing instances
from SNMP tables can trigger bugs in OID sorting.
- Did you try turning SNMP bulkwalk off for the devices with issues?
(bulkwalk_no directive in deployment.yml iirc)
- Is there any way that SNMP responses can be received out-of-order?
(very very unlikely TBH)
- Is it possible to upgrade the IOS on one of the affected devices to
a more recent version? Looks like the example device still runs a
pretty old IOS.
- When you run several consecutive tests on the command line, eg using
'snmpbulkwalk -c <community> <device> .1' to retrieve all SNMP data
from a device, does each walk complete without snmpbulkwalk giving
errors about a non-increasing OID?
Regards,
Jeroen van Ingen
ICT Service Centre
University of Twente, P.O.Box 217, 7500 AE Enschede, The Netherlands
On 04/19/2016 03:41 PM, Edward Vopata wrote:
I am still having a problem with Netdisco 2, where the port
(device_port.port) is being set to the SNMP ifIndex value of the port
instead of the port name value (ie: GigabitEthernet0/0).
I have been having this problem for several months (almost a full year).
An initial discover on the device will set the port to the correct name
value (ie GigabitEthernet0/0), however the port will often get changed
back to the ifIndex value. Once the port name gets set to the ifIndex
value, then the arpnip and macsuck procedures are no long able to match
the port from the arp or mac data with the port in the database, (that
is to say "GigabitEthernet0/0" != '3').
This problem make NetDisco 2, virtually useless and unreliable.
Here is my NetDisco Information:
Hostname : netdisco2
OS : Ubuntu 14.04.4 LTS
Perl : v5.18.2
App::NetDisco : 2.033006
DB Schema : 40
SNMP::Info : 3.31
Apache : 2.4.7
Net-SNMP : 5.7.2
PostgreSQL : 9.3.12
Is anyone else having this problem?
Does anyone have a recommendation on how to fix this problem?
Thanks.
------------------------------------------------------------------------------
Find and fix application performance issues faster with Applications
Manager
Applications Manager provides deep performance insights into multiple
tiers of
your business applications. It resolves application problems quickly and
reduces your MTTR. Get your free trial!
https://ad.doubleclick.net/ddm/clk/302982198;130105516;z
_______________________________________________
Netdisco mailing list
netdisco-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/netdisco-users
--- End Message ---
--- Begin Message ---
Hi Edward,
Even though ND1 works fine, there must be a reason why you're having
these issues with ND2. The core logic hasn't really changed, so I'm
trying to figure out what the root cause may be and what could be
different between your ND1 and ND2 setup.
I'm assuming that you're running ND1 and ND2 on two separate hosts, each
with their own database. Is that correct? Would you mind comparing a few
devices between your ND1 and ND2 database to see whether both use the
same SNMP version?
The timeouts during bulkwalk shouldn't happen, so that's worth further
investigation. Do you have the same timeout values configured in ND1 and
ND2? When doing consecutive snmpbulkwalks from the CLI, can you
experiment with higher timeout values (-t option for snmpbulkwalk) and
see what timeout is needed to get full results each time?
Regards,
Jeroen van Ingen
ICT Service Centre
University of Twente, P.O.Box 217, 7500 AE Enschede, The Netherlands
On 04/19/2016 04:55 PM, Edward Vopata wrote:
> - Does the number of (virtual) interfaces on these Cisco 2800's
change dynamically,
No. I don't think those 2800 are doing any virtual/dynamic interfaces.
> - Did you try turning SNMP bulkwalk off for the devices with issues?
(bulkwalk_no directive in deployment.yml iirc)
I think I tried that at one point,
> - Is there any way that SNMP responses can be received out-of-order?
(very very unlikely TBH)
I don't think so. My NetDisco 1 system is working just fine,
> - Is it possible to upgrade the IOS on one of the affected devices to
a more recent version?
Probably not. I'm in an enterprise environment, router upgrades have to
be planned
months/years in advanced.
> - When you run several consecutive tests on the command line, eg
using 'snmpbulkwalk -c <community> <device> .1' to retrieve all SNMP
data from a device, does each walk complete without snmpbulkwalk giving
errors about a non-increasing OID?
$ snmpbulkwalk -v2c -c {comm} {host} .1
I've tried several devices and I get a bunch of data followed by a
"Timeout: No Response from"
message.
Like I said, my NetDisco 1 is functioning reasonably well.
But the NetDisco 2 is flaky.
-- Ed.
On 04/19/16 09:24, Jeroen van Ingen wrote:
Hi Edward,
I've not seen this issue in our network, as far as I can see the
interface names are stable.
You posted a discover log earlier; reading through it, I noticed that
there's a lot of lines regarding "Looping". I believe that indicates
Netdisco getting back SNMP responses with OIDs that are not ordered
correctly.
I'm not sure what could be causing this. Usually receiving SNMP
responses with OIDs returned out-of-order (ie not steadily
incrementing) is caused by bugs on the SNMP agent (ie device), but
then it's usually easy to reproduce and ND2 behavior would be expected
to be the same as ND1.
Just a few random ideas:
- Does the number of (virtual) interfaces on these Cisco 2800's change
dynamically, eg do they terminate VPN sessions or VoIP / PSTN phone
calls? I've seen devices where (in general) adding/removing instances
from SNMP tables can trigger bugs in OID sorting.
- Did you try turning SNMP bulkwalk off for the devices with issues?
(bulkwalk_no directive in deployment.yml iirc)
- Is there any way that SNMP responses can be received out-of-order?
(very very unlikely TBH)
- Is it possible to upgrade the IOS on one of the affected devices to
a more recent version? Looks like the example device still runs a
pretty old IOS.
- When you run several consecutive tests on the command line, eg using
'snmpbulkwalk -c <community> <device> .1' to retrieve all SNMP data
from a device, does each walk complete without snmpbulkwalk giving
errors about a non-increasing OID?
Regards,
Jeroen van Ingen
ICT Service Centre
University of Twente, P.O.Box 217, 7500 AE Enschede, The Netherlands
On 04/19/2016 03:41 PM, Edward Vopata wrote:
I am still having a problem with Netdisco 2, where the port
(device_port.port) is being set to the SNMP ifIndex value of the port
instead of the port name value (ie: GigabitEthernet0/0).
I have been having this problem for several months (almost a full year).
An initial discover on the device will set the port to the correct name
value (ie GigabitEthernet0/0), however the port will often get changed
back to the ifIndex value. Once the port name gets set to the ifIndex
value, then the arpnip and macsuck procedures are no long able to match
the port from the arp or mac data with the port in the database, (that
is to say "GigabitEthernet0/0" != '3').
This problem make NetDisco 2, virtually useless and unreliable.
Here is my NetDisco Information:
Hostname : netdisco2
OS : Ubuntu 14.04.4 LTS
Perl : v5.18.2
App::NetDisco : 2.033006
DB Schema : 40
SNMP::Info : 3.31
Apache : 2.4.7
Net-SNMP : 5.7.2
PostgreSQL : 9.3.12
Is anyone else having this problem?
Does anyone have a recommendation on how to fix this problem?
Thanks.
------------------------------------------------------------------------------
Find and fix application performance issues faster with Applications
Manager
Applications Manager provides deep performance insights into multiple
tiers of
your business applications. It resolves application problems quickly and
reduces your MTTR. Get your free trial!
https://ad.doubleclick.net/ddm/clk/302982198;130105516;z
_______________________________________________
Netdisco mailing list
netdisco-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/netdisco-users
--- End Message ---
------------------------------------------------------------------------------
Find and fix application performance issues faster with Applications Manager
Applications Manager provides deep performance insights into multiple tiers of
your business applications. It resolves application problems quickly and
reduces your MTTR. Get your free trial!
https://ad.doubleclick.net/ddm/clk/302982198;130105516;z
_______________________________________________
Netdisco mailing list - Digest Mode
netdisco-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/netdisco-users
