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. ND2 inadequate recognition of Cisco Switches (Nikolaos Milas)
2. Re: ND2 inadequate recognition of Cisco Switches (Oliver Gorwits)
3. Re: ND2 inadequate recognition of Cisco Switches
(Jeroen van Ingen)
4. Re: ND2 inadequate recognition of Cisco Switches (Nikolaos Milas)
5. Netdisco 2 Neighbors Map - How to Add in hostname (Muris)
6. Re: Netdisco 2 Neighbors Map - How to Add in hostname
(Simon Hobson)
7. Re: Netdisco 2 Neighbors Map - How to Add in hostname
(Mark Cooper)
8. BNT / Blade / IBM / Lenovo rack switches (James M. Pulver)
--- Begin Message ---
Hello,
We are seeing that SG/SF series Cisco SBS switches do not get recognized
"well enough".
Esp. after some Firmware upgrade version, the problem is much worse.
Devices get recognized as:
SRW224G4-K9 V02
SRW2024-K9 V02
SRW2008-K9 V04
SRW2008-K9 V02
...
Could this be considered expected behavior? Initially (in earlier
Firmware versions) they were recognized as SG300/SF300/SG200/SF200, as
expected. If it is a MIB-related issue, could you please check whether
updating MIBs would help?
I have downloaded the most recent related MIB files I found at Cisco,
and you can find them here:
https://iweb.noa.gr/files/MIBs_Sx300_v1.4.1.03.zip
https://iweb.noa.gr/files/MIBs_Sx200_v1.4.1.03.zip
ND2 we are currently using:
Software Version
--------------------------
App::Netdisco 2.034000
DB Schema v40
Dancer 1.3132
Bootstrap 2.3.1
PostgreSQL PostgreSQL 8.4.20 on x86_64-redhat-linux-gnu, compiled
by GCC gcc (GCC) 4.4.7 20120313 (Red Hat 4.4.7-17),
64-bit. DBI 1.632, DBD::Pg 2.15.1
SNMP::Info 3.33
Perl 5.010001
Thanks a lot,
Nick
--- End Message ---
--- Begin Message ---
Hi Nikolaos,
You may be able to test whether the updated MIBs help, yourself. Look
into ~netdisco/netdisco-mibs/cisco and copy the downloaded files to that
location, then run a discover job on the device.
Note that sometimes vendors do ship broken MIBs, and if that causes
netdisco to abort, simply move the netdisco-mibs folder out of the way
and reinitialise it using the netdisco-deploy script.
oliver.
On 2016-11-15 15:37, Nikolaos Milas wrote:
Hello,
We are seeing that SG/SF series Cisco SBS switches do not get
recognized
"well enough".
Esp. after some Firmware upgrade version, the problem is much worse.
Devices get recognized as:
SRW224G4-K9 V02
SRW2024-K9 V02
SRW2008-K9 V04
SRW2008-K9 V02
...
Could this be considered expected behavior? Initially (in earlier
Firmware versions) they were recognized as SG300/SF300/SG200/SF200, as
expected. If it is a MIB-related issue, could you please check whether
updating MIBs would help?
I have downloaded the most recent related MIB files I found at Cisco,
and you can find them here:
https://iweb.noa.gr/files/MIBs_Sx300_v1.4.1.03.zip
https://iweb.noa.gr/files/MIBs_Sx200_v1.4.1.03.zip
ND2 we are currently using:
Software Version
--------------------------
App::Netdisco 2.034000
DB Schema v40
Dancer 1.3132
Bootstrap 2.3.1
PostgreSQL PostgreSQL 8.4.20 on x86_64-redhat-linux-gnu,
compiled
by GCC gcc (GCC) 4.4.7 20120313 (Red Hat 4.4.7-17),
64-bit. DBI 1.632, DBD::Pg 2.15.1
SNMP::Info 3.33
Perl 5.010001
Thanks a lot,
Nick
------------------------------------------------------------------------------
_______________________________________________
Netdisco mailing list
netdisco-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/netdisco-users
--- End Message ---
--- Begin Message ---
Hi Nikolaos,
Can you check in eg the web interface, Details page for one of these
switches, if it's recognized as SNMP::Info::Layer2::CiscoSB class?
That's the class that I'd expect for them.
The CiscoSB class returns the model string just as reported by the
device itself, using the first non-empty value from
ENTITY-MIB::entPhysicalModelName.
Probably the firmware update for these switches also changes some values
returned for ENTITY-MIB. Updating your MIBs won't help then.
Can you do an snmpwalk for ENTITY-MIB::entPhysicalModelName, and/or
execute 'netdisco-do show -d <device_ip> -e e_model'? That will show
what the switch returns, and thus what Netdisco stores in the database
and displays in the web interface.
Regards,
Jeroen van Ingen
ICT Service Centre
University of Twente, P.O.Box 217, 7500 AE Enschede, The Netherlands
On 11/15/2016 04:37 PM, Nikolaos Milas wrote:
Hello,
We are seeing that SG/SF series Cisco SBS switches do not get recognized
"well enough".
Esp. after some Firmware upgrade version, the problem is much worse.
Devices get recognized as:
SRW224G4-K9 V02
SRW2024-K9 V02
SRW2008-K9 V04
SRW2008-K9 V02
...
Could this be considered expected behavior? Initially (in earlier
Firmware versions) they were recognized as SG300/SF300/SG200/SF200, as
expected. If it is a MIB-related issue, could you please check whether
updating MIBs would help?
I have downloaded the most recent related MIB files I found at Cisco,
and you can find them here:
https://iweb.noa.gr/files/MIBs_Sx300_v1.4.1.03.zip
https://iweb.noa.gr/files/MIBs_Sx200_v1.4.1.03.zip
ND2 we are currently using:
Software Version
--------------------------
App::Netdisco 2.034000
DB Schema v40
Dancer 1.3132
Bootstrap 2.3.1
PostgreSQL PostgreSQL 8.4.20 on x86_64-redhat-linux-gnu, compiled
by GCC gcc (GCC) 4.4.7 20120313 (Red Hat 4.4.7-17),
64-bit. DBI 1.632, DBD::Pg 2.15.1
SNMP::Info 3.33
Perl 5.010001
Thanks a lot,
Nick
------------------------------------------------------------------------------
_______________________________________________
Netdisco mailing list
netdisco-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/netdisco-users
--- End Message ---
--- Begin Message ---
On 17/11/2016 3:26 μμ, Jeroen van Ingen wrote:
Can you do an snmpwalk for ENTITY-MIB::entPhysicalModelName, and/or
execute 'netdisco-do show -d <device_ip> -e e_model'? That will show
what the switch returns, and thus what Netdisco stores in the database
and displays in the web interface.
Thank you all for your replies.
How should I do the snmpwalk check?
Here is the second query, which indeed returns the model displayed in
the web GUI:
$ ~/bin/netdisco-do show -d 10.201.0.56 -e e_model
[31327] 2016-11-17 17:07:36 info show: started at Thu Nov 17
19:07:36 2016
\ {
67108992 "SRW2024-K9",
68157952 "",
68420352 "",
68424704 "",
68424769 "",
68424770 "",
68424771 "",
68424772 "",
68424773 "",
68424774 "",
68424775 "",
68424776 "",
68424777 "",
68424778 "",
68424779 "",
68424780 "",
68424781 "",
68424782 "",
68424783 "",
68424784 "",
68424785 "",
68424786 "",
68424787 "",
68424788 "",
68424789 "",
68424790 "",
68424791 "",
68424792 "",
68424793 "",
68424794 "",
68424795 "",
68424796 ""
}
[31327] 2016-11-17 17:07:37 info show: finished at Thu Nov 17
19:07:37 2016
[31327] 2016-11-17 17:07:37 info show: status done: Showed e_model
response from 10.201.0.56.
I might try the MIB files as Oliver suggests.
Thanks,
Nick
--- End Message ---
--- Begin Message ---
Hi,
I been using Netdisco 2 and ive found it to be great, i wanted to know on a
device for the "Neighbors" Map it has the circles with the IP address, is
there anyway of adding in the hostname above the IP, or below the IP of the
device. This way i have full visibility of adjacent networks with an IP and
hostname.
If a hostname can be added on along with the IP, it would be most useful
either above or below the IP.
Thanks!
--- End Message ---
--- Begin Message ---
Muris <alcat...@gmail.com> wrote:
> I been using Netdisco 2 and ive found it to be great, i wanted to know on a
> device for the "Neighbors" Map it has the circles with the IP address, is
> there anyway of adding in the hostname above the IP, or below the IP of the
> device.
On mine it shows the DNS name, and only shows IP address if the DNS name is
unknown - or at least, that's what it appears to be doing. I haven't done any
tests to see if the IP addresses get replaced by names if I fix the missing
reverse DNS entries for the few devices showing Ip addresses.
--- End Message ---
--- Begin Message ---
If you have DNS names for all the possible IP's for the devices then
you'll always get a name regardless of which IP is being discovered. It
is an easy way to know if you're missing an IP in DNS. :-)
Thanks,
Mark Cooper
On 11/18/2016 04:58 AM, Simon Hobson wrote:
Muris <alcat...@gmail.com> wrote:
I been using Netdisco 2 and ive found it to be great, i wanted to know on a device for
the "Neighbors" Map it has the circles with the IP address, is there anyway of
adding in the hostname above the IP, or below the IP of the device.
On mine it shows the DNS name, and only shows IP address if the DNS name is
unknown - or at least, that's what it appears to be doing. I haven't done any
tests to see if the IP addresses get replaced by names if I fix the missing
reverse DNS entries for the few devices showing Ip addresses.
------------------------------------------------------------------------------
_______________________________________________
Netdisco mailing list
netdisco-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/netdisco-users
--- End Message ---
--- Begin Message ---
We have a lot of these G8000, G8052, G8124 and G8264 as well as some
similar Flex EN4093R IO modules. Netdisco 2 doesn't seem to be able to
get LLDP information from them and hence while it sees the switch ports,
doesn't create maps. I was on the IRC chat and told this may be because
the BNT plugin was last updated in 2013. I'd really like to get NetDisco
2 going in my environment with these switches, so I'm looking for ideas,
including any consulting recommendations for having the plugin updated.
Any help would be appreciated.
I'm running on Scientific Linux 6.8, I could also use SL7.2, though I
don't think the server OS is very relevant to this issue as the rest of
NetDisco runs "perfectly" as far as I've been able to tell.
--
James Pulver
CLASSE Computer Group
Cornell University
--- End Message ---
------------------------------------------------------------------------------
_______________________________________________
Netdisco mailing list - Digest Mode
netdisco-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/netdisco-users
