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: Possible netdisco bug (Muris)
   2. Re: Adding Aruba SDWAN/Silverpeak MIBS into netdisco (Muris)
--- Begin Message ---
Can do.. the other weird thing what happens is after a short period maybe during the next rescan as i have discovery set to once per day, if its still not reachable it automatically removes the device from the whole database.. have no idea how its doing that.

Hence my asking previously restricting snmp public strings to specific devices, cause im not sure if its causing some bug or something with whole netdisco..
Maybe might poke around the backend logs see what its doing.


On 23 Jun 2023, at 01:17, Oliver Gorwits <[email protected]> wrote:


Hi Muris, please would you open a ticket here https://github.com/netdisco/netdisco/issues

This is a strange one!

On Thu, 8 Jun 2023 at 09:05, Muris <[email protected]> wrote:

Hi,

 

Recently I had to enable SNMP v1 on a few devices because that’s all they support with “public” snmp string but in turn I think it’s causing issues to other devices.

 

When another devices that’s SNMP v2 or v3 goes down, and when netdisco tries to probe it, it generates these blank results.

Before it went down it had the full details etc, then suddenly after it goes down it changes it to these blank values etc.

 

Is this a bug or ?

 

<image001.png>

 

_______________________________________________
Netdisco mailing list
[email protected]
https://sourceforge.net/p/netdisco/mailman/netdisco-users/

--- End Message ---
--- Begin Message ---
Hey oliver was also just going to ask would it please be possible if you could add these to the mibs dir when you have a moment ?
Have uploaded the zip a little while ago in that issues URL
 
Thanks in advance

On 17 May 2023, at 22:00, Muris <[email protected]> wrote:



Hi Oliver, just wanted to ask if you would be able to integrate these Aruba/Silverpeak MIBS into netdisco, I have attached them a few months ago.

 

We have number of these devices and having these mibs working would be great, right now majority report as “unknown enterprises” etc

 

From: Muris <[email protected]>
Date: Friday, 10 March 2023 at 22:00
To: Oliver Gorwits <[email protected]>
Cc: "[email protected]" <[email protected]>
Subject: Re: [Netdisco] Adding Aruba SDWAN/Silverpeak MIBS into netdisco

 

Thanks Oliver, have done and put it there

 

From: Oliver Gorwits <[email protected]>
Date: Friday, 10 March 2023 at 21:33
To: Muris <[email protected]>
Cc: "[email protected]" <[email protected]>
Subject: Re: [Netdisco] Adding Aruba SDWAN/Silverpeak MIBS into netdisco

 

Hi Muris

 

Sure, please would you kindly open a ticket here on the netdisco-mibs repository: https://github.com/netdisco/netdisco-mibs/issues

 

Even better, if you can download the MIBs and attach them, please, because Netdisco devs do not have a contract with Aruba to do that.

 

Kind regards

Oliver.

 

On Fri, 10 Mar 2023 at 10:19, Muris <[email protected]> wrote:

Hey guys, I was wondering if someone would be able to add the following Aruba SDWAN/Silverpeak mibs into the base netdisco?

 

https://www.arubanetworks.com/website/techdocs/sdwan-PDFs/mibs/mibs-9.2.zip

 

 

Originally from this link

https://www.arubanetworks.com/techdocs/sdwan/mibs/

 

Thanks

Muris

_______________________________________________
Netdisco mailing list
[email protected]
https://sourceforge.net/p/netdisco/mailman/netdisco-users/


--- End Message ---
_______________________________________________
Netdisco mailing list - Digest Mode
[email protected]
https://lists.sourceforge.net/lists/listinfo/netdisco-users

Reply via email to