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: make Netdisco an elephant (Christian Ramseyer)
2. Re: make Netdisco an elephant (Joseph Bernard)
3. Some new Cisco WLC models missing (Kaido Saul)
4. Re: Some new Cisco WLC models missing (Jeremy Bresley)
--- Begin Message ---
On 15.06.21 17:04, Joseph Bernard wrote:
> If I wanted Netdisco to remember as much as possible for as long as
> possible, what settings would I use?
>
Hi Joseph
I'd just crank up expire_nodes and expire_devices to a very high setting
like 3650 days.
I have used a couple of years and it works fine, unless IP addresses of
no longer existing devices get reused on new gear. The IP is the primary
key so the new device can not co-exist - most likely the discovery will
overwrite some or all of the old data (interfaces, hardware etc).
Cheers
Christian
--- End Message ---
--- Begin Message ---
Thank you! I have added the following settings:
expire_devices: 3650
expire_nodes: 3650
expire_nodes_archive: 3650
expire_nodeip_freshness: 3650
Thanks,
Joseph B.
On 6/16/21, 12:16 PM, "Christian Ramseyer" <[email protected]> wrote:
On 15.06.21 17:04, Joseph Bernard wrote:
> If I wanted Netdisco to remember as much as possible for as long as
> possible, what settings would I use?
>
Hi Joseph
I'd just crank up expire_nodes and expire_devices to a very high setting
like 3650 days.
I have used a couple of years and it works fine, unless IP addresses of
no longer existing devices get reused on new gear. The IP is the primary
key so the new device can not co-exist - most likely the discovery will
overwrite some or all of the old data (interfaces, hardware etc).
Cheers
Christian
--- End Message ---
--- Begin Message ---
Hi,
Using Netdisco for many years and it has helped a lot.
We are implementing some new Cisco 9800 series Wireless controllers now. If to
look in inventory, it is showing Products.2391 and Products.2861 as a model.
Can I change them to real model names somehow?
Thank you
Lugupidamisega / Best regards
Kaido Saul
--- End Message ---
--- Begin Message ---
On 6/17/2021 12:54 AM, Kaido Saul wrote:
Hi,
Using Netdisco for many years and it has helped a lot.
We are implementing some new Cisco 9800 series Wireless controllers
now. If to look in inventory, it is showing Products.2391 and
Products.2861 as a model. Can I change them to real model names somehow?
Thank you
Lugupidamisega / Best regards
*Kaido Saul*
There's two ways to resolve this. One is to update the netdisco-mibs
package, this will pull in all the updated MIBs and is maintained by the
Netdisco team.
The second way is to replace the file CISCO-PRODUCTS-MIB.my which is
available from ftp://ftp.cisco.com/pub/mibs/v2/ This is the MIB which
does the OID to name mapping specific to Cisco devices. Unfortunately I
don't have a current Netdisco install to tell you exactly where that
file is located to replace it, but you should be able to find it pretty
easily.
After either update, rediscover the device and it should clear up the
product names.
Jeremy
--- End Message ---
_______________________________________________
Netdisco mailing list - Digest Mode
[email protected]
https://lists.sourceforge.net/lists/listinfo/netdisco-users
