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: Netdisco 2 - port name problem (Steven Xu)
2. Re: Netdisco 2 - port name problem (Edward Vopata)
3. Report for Cisco Catalyst 3K Advisory (Zachary McGibbon)
--- Begin Message ---
Hi Edward,
Discovering this device seems to have taken 4 minutes, where it times out four times and reconnects with different SNMP classes. In contrast, one of our routers takes 5 seconds to discover. How is the load on your Netdisco server? What about your device? It's strange it should be taking so long since the logs suggest it's a fairly simple setup.
There aren't any errors, from my eyes, that I observe that would be affecting your discover. A wild guess I'm making is that i_descr MIB is not being reported correctly by your devices sometimes, which results in ifValues for your port names. This may also account for the fact that SNMP::Info (the SNMP library for netdisco) to not recognize some ports.
I'm a bit in over my head since my networking knowledge is weak. I'm hoping someone else will be able to take over for this issue. Hopefully my observations may help you or someone else debug the issue.
Best of luck,
Steven
-----Edward Vopata <[email protected]> wrote: -----To: Steven Xu <
[email protected]>
From: Edward Vopata <
[email protected]>
Date: 02/11/2016 10:05AM
Cc: <
[email protected]>
Subject: Re: [Netdisco] Netdisco 2 - port name problem
Thank you for your support. If it wasn't bizarre, then it probably
wouldn't be an issue
> You said you disabled arpnip and macsuck, but I'm
still seeing log entries for arpnip and macsuck. Did you restart
the netdisco daemon?
The issue is some where in the discovery code, so the macwalk and
the arpwalk are just cluttering up the logs.
I will disable them.
> Can you
confirm that there were no physical changes to the device while
you were running discovers? How many actual interfaces are on this
device?
No one is making any changes to the device (physical or
configuration).
The device has 68 interfaces.
My device table now has only 16 devices:
I am still trying to isolate the issue.
So I am going to disable the aprwalk, disable the macwalk, and set
the discover to run once an hour during the day.
I have also set my works back to "AUTO * 2" == 32 workers
schedule:
discoverall:
when: '1 9,10,11,12,1,2,3,4,5 * * *'
expire:
when: '20 23 * * *'
workers:
tasks: 'AUTO * 2'
---------------
This is getting really bizarre.
I just ran a manual discover on the device (which has 68
interface), but the discover only found 2 interfaces,
and 1 of the interfaces got set with ifindex value. Attached are
some log files.
--Ed.
On 02/10/16 16:22, Steven Xu wrote:
Hi Edward,
I don't have a solution yet, but I'm offering my observations in
case anyone wants to add to this. I'll ponder a solution
tomorrow (hopefully after you can answer some of the following
questions).
You have no shortage of bizarre results:
You said you disabled arpnip and macsuck, but I'm
still seeing log entries for arpnip and macsuck. Did you
restart the netdisco daemon?
On several occasions, Netdisco is trying to connect to the
same device with different SNMP Classes and SNMP versions,
timing out after 20 seconds if it isn't able to connect. I
suspect this is caused by your Netdisco SNMP configuration or
with the code.
I find it interesting that at 15:07:37 of your logs, it says
the device has 9 interfaces, but on the next discover at
16:07:37, it removes 68 interfaces. How is netdisco removing
more interfaces than were already there?
Is this after you purged your database? Still very confusing
to me.
Can you confirm that there were no physical changes to the
device while you were running discovers? How many actual
interfaces are on this device?
In addition, on two discovers, it fails to update the ports
because it is not able to get the uptime for the device. This
might be caused by the fact that you are discovering this
device too often, but this only happens to 1 of our 300
devices, and we discover every four hours.
Netdisco also complains about a wrapped uptime two times out
of the four times it successfully updates device port entries,
but these messages aren't after sequential discovers. I would
expect that it would complain about a wrapped uptime all four
times.
Steven
[attachment "device_port.txt" removed by Steven Xu/fs/YorkU]
[attachment "discover_log.txt" removed by Steven Xu/fs/YorkU]
--- End Message ---
--- Begin Message ---
The load on my netdisco server is trivial.
The server is dedicated to doing netdisco (v2) and
since it in only polling 16 devices at this time.
The router devices are also very lightly used.
-- Ed.
On 02/11/16 10:28, Steven Xu wrote:
Hi Edward,
Discovering this device seems to have taken 4 minutes, where it times
out four times and reconnects with different SNMP classes. In
contrast, one of our routers takes 5 seconds to discover. How is the
load on your Netdisco server? What about your device? It's strange it
should be taking so long since the logs suggest it's a fairly simple
setup.
There aren't any errors, from my eyes, that I observe that would be
affecting your discover. A wild guess I'm making is that i_descr MIB
is not being reported correctly by your devices sometimes, which
results in ifValues for your port names. This may also account for the
fact that SNMP::Info (the SNMP library for netdisco) to not recognize
some ports.
I'm a bit in over my head since my networking knowledge is weak. I'm
hoping someone else will be able to take over for this issue.
Hopefully my observations may help you or someone else debug the issue.
Best of luck,
Steven
--- End Message ---
--- Begin Message ---
We have a lot of Cisco switches on our network and we were just made aware
of a sort of recall for some models of switches due to bad memory. I wrote
a custom report and wanted to share it with everyone in case you want to
use it.
This said, it would be nice to have a page somewhere on the netdisco site
where users could contribute custom reports like this.
http://www.cisco.com/c/en/us/support/docs/field-notices/637/fn63745.html
Add this in environments/deployment.yml
reports:
- tag: cisco_fn_63745
label: 'Cisco Field Notice 63745'
columns:
- {name: 'Name'}
- {ip: 'IP'}
- {pos: 'Switch Number'}
- {model: 'Model'}
- {serial: 'Serial'}
- {hw_ver: 'HW Ver'}
- {fw_ver: 'Firmware'}
- {last_discover: 'Last Discover'}
query: |
select distinct
device.name,
device.ip,
device_module.pos + 1 as pos,
device_module.model,
device_module.serial,
device_module.hw_ver,
device_module.fw_ver,
device_module.last_discover
from device
inner join device_module
on device.ip=device_module.ip
where
device_module.last_discover >= CURRENT_DATE
and device_module.model like 'WS-C3560V2-24TS-E'
or device_module.model like 'WS-C3560V2-24TS-S'
or device_module.model like 'WS-C3560V2-24TS-SD'
or device_module.model like 'WS-C3560V2-48TS-E'
or device_module.model like 'WS-C3560V2-48TS-S'
or device_module.model like 'WS-C3560V2-24PS-E'
or device_module.model like 'WS-C3560V2-24PS-S'
or device_module.model like 'WS-C3560V2-48PS-E'
or device_module.model like 'WS-C3560V2-48PS-S'
or device_module.model like 'WS-C3560-24PS-E'
or device_module.model like 'WS-C3560-24PS-S'
or device_module.model like 'WS-C3560-24TS-E'
or device_module.model like 'WS-C3560-24TS-S'
or device_module.model like 'WS-C3560-48PS-E'
or device_module.model like 'WS-C3560-48PS-S'
or device_module.model like 'WS-C3560-48TS-E'
or device_module.model like 'WS-C3560-48TS-S'
or device_module.model like 'WS-C3560G-24PS-E'
or device_module.model like 'WS-C3560G-24PS-S'
or device_module.model like 'WS-C3560G-24TS-E'
or device_module.model like 'WS-C3560G-24TS-S'
or device_module.model like 'WS-C3560G-48PS-E'
or device_module.model like 'WS-C3560G-48PS-S'
or device_module.model like 'WS-C3560G-48TS-E'
or device_module.model like 'WS-C3560G-48TS-S'
or device_module.model like 'WS-C3560-12PC-S'
or device_module.model like 'WS-C3560-8PC-S'
or device_module.model like 'WS-C3560E-12D-E'
or device_module.model like 'WS-C3560E-12D-S'
or device_module.model like 'WS-C3560E-12SD-E'
or device_module.model like 'WS-C3560E-12SD-S'
or device_module.model like 'WS-C3560E-24PD-E'
or device_module.model like 'WS-C3560E-24PD-S'
or device_module.model like 'WS-C3560E-24TD-E'
or device_module.model like 'WS-C3560E-24TD-S'
or device_module.model like 'WS-C3560E-24TD-SD'
or device_module.model like 'WS-C3560E-48PD-E'
or device_module.model like 'WS-C3560E-48PD-EF'
or device_module.model like 'WS-C3560E-48PD-S'
or device_module.model like 'WS-C3560E-48PD-SF'
or device_module.model like 'WS-C3560E-48TD-E'
or device_module.model like 'WS-C3560E-48TD-S'
or device_module.model like 'WS-C3560E-48TD-SD'
or device_module.model like 'WS-C3560X-48PF-S'
or device_module.model like 'WS-C3750V2-24TS-E'
or device_module.model like 'WS-C3750V2-24TS-S'
or device_module.model like 'WS-C3750V2-48TS-E'
or device_module.model like 'WS-C3750V2-48TS-S'
or device_module.model like 'WS-C3750V2-24PS-E'
or device_module.model like 'WS-C3750V2-24PS-S'
or device_module.model like 'WS-C3750V2-48PS-E'
or device_module.model like 'WS-C3750V2-48PS-S'
or device_module.model like 'WS-C3750-24FS-S'
or device_module.model like 'WS-C3750-24PS-E'
or device_module.model like 'WS-C3750-24PS-S'
or device_module.model like 'WS-C3750-24TS-E'
or device_module.model like 'WS-C3750-24TS-S'
or device_module.model like 'WS-C3750-48PS-E'
or device_module.model like 'WS-C3750-48PS-S'
or device_module.model like 'WS-C3750-48TS-E'
or device_module.model like 'WS-C3750-48TS-S'
or device_module.model like 'WS-C3750G-12S-E'
or device_module.model like 'WS-C3750G-12S-S'
or device_module.model like 'WS-C3750G-12S-SD'
or device_module.model like 'WS-C3750G-24PS-E'
or device_module.model like 'WS-C3750G-24PS-S'
or device_module.model like 'WS-C3750G-24T-E'
or device_module.model like 'WS-C3750G-24T-S'
or device_module.model like 'WS-C3750G-24TS-E1U'
or device_module.model like 'WS-C3750G-24TS-S1U'
or device_module.model like 'WS-C3750G-48PS-E'
or device_module.model like 'WS-C3750G-48PS-S'
or device_module.model like 'WS-C3750G-48TS-E'
or device_module.model like 'WS-C3750G-48TS-S'
or device_module.model like 'WS-C3750E-24PD-E'
or device_module.model like 'WS-C3750E-24PD-S'
or device_module.model like 'WS-C3750E-24TD-E'
or device_module.model like 'WS-C3750E-24TD-S'
or device_module.model like 'WS-C3750E-24TD-SD'
or device_module.model like 'WS-C3750E-48PD-E'
or device_module.model like 'WS-C3750E-48PD-EF'
or device_module.model like 'WS-C3750E-48PD-S'
or device_module.model like 'WS-C3750E-48PD-SF'
or device_module.model like 'WS-C3750E-48TD-E'
or device_module.model like 'WS-C3750E-48TD-S'
or device_module.model like 'WS-C3750E-48TD-SD'
order by device.name,pos
--- 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=272487151&iu=/4140
_______________________________________________
Netdisco mailing list - Digest Mode
[email protected]
https://lists.sourceforge.net/lists/listinfo/netdisco-users
