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: TPLink MIBs for Netdisco (Karel V?chodsk?)
2. Re: TPLink MIBs for Netdisco (Jeroen van Ingen)
3. detecting err-disabled ports (Stuart Kendrick)
4. Re: detecting err-disabled ports (Jeroen van Ingen)
--- Begin Message ---
Hi Jeroen,
thanks for help. I have downloaded all the ZIP files available from
TP-Link site (each ZIP file contains MIBs for specific device). If I
understood well the whole principle, vendor should be marking each
property of device with unique item number (or how to explain). So
there's a file at http://download.skynet-systems.cz/tplmibs.zip
containing all the ZIP archives downloaded from their site and another
file http://download.skynet-systems.cz/tpl_biggest_files.zip which is
all the files unpacked from original ZIPs placed in one directory,
keeping the bigger file when asked for overwrite, thus keeping file
containing more information which I understood should be more recent.
IDK if it's correct but I upload anyways.
I don't know the version of net-snmp, I have a Debian server, so
installed libnet-snmp-perl (6.0.1-2), snmpd (5.7.2.1) and snmptrapd
(5.7.2.1) if that's enough.. Or do I need to get something via CPAN??
Thanks very much one more time, if you could process the files and add
some quick info about how to update, it would be very helpful.
BR
Karel Vychodsky
--- End Message ---
--- Begin Message ---
Hi Karel,
Thanks for supplying both versions. The first didn't yield a usable
collection, way too many errors when trying to load them all.
I used the files for the T1600G-52PS model, because that one had a
combination of a very recent date (20160411) and slightly larger ZIP
file than another that was dated 20160412. I noticed that
TPLINK-PRODUCTS-MIB contained three additional models, compared to
several other copies of that MIB.
Fixed a few errors, only left out the TP-Link vendor specific MIB for
PoE because that had a few errors as well which were harder to fix.
This should probably be enough to be able to translate most of the SNMP
outputs from all current TP-Link switches. I've already committed my
work to the netdisco-mibs git repository.
These MIBs won't change anything for Netdisco yet. To take advantage of
them in Netdisco, you'll need to extend SNMP::Info for a new class for
TP-Link switches.
Regards,
Jeroen van Ingen
ICT Service Centre
University of Twente, P.O.Box 217, 7500 AE Enschede, The Netherlands
On 09/09/2016 10:35 AM, Karel Východský wrote:
Hi Jeroen,
thanks for help. I have downloaded all the ZIP files available from
TP-Link site (each ZIP file contains MIBs for specific device). If I
understood well the whole principle, vendor should be marking each
property of device with unique item number (or how to explain). So
there's a file at http://download.skynet-systems.cz/tplmibs.zip
containing all the ZIP archives downloaded from their site and another
file http://download.skynet-systems.cz/tpl_biggest_files.zip which is
all the files unpacked from original ZIPs placed in one directory,
keeping the bigger file when asked for overwrite, thus keeping file
containing more information which I understood should be more recent.
IDK if it's correct but I upload anyways.
I don't know the version of net-snmp, I have a Debian server, so
installed libnet-snmp-perl (6.0.1-2), snmpd (5.7.2.1) and snmptrapd
(5.7.2.1) if that's enough.. Or do I need to get something via CPAN??
Thanks very much one more time, if you could process the files and add
some quick info about how to update, it would be very helpful.
BR
Karel Vychodsky
------------------------------------------------------------------------------
_______________________________________________
Netdisco mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/netdisco-users
--- End Message ---
--- Begin Message ---
Generically, I don't see a way to identify ports in the err-disable state. Am
I missing something? Or is this an unsolved problem?
test-esx#sh int status | include err
Gi2/0/4 err-disabled 60 auto auto
10/100/1000BaseTX
Gi4/0/36 err-disabled 60 auto auto
10/100/1000BaseTX
test-esx#
Status for these ports in NetDisco show as 'Up/Up'.
Though interestingly, poking through snmpwalk output, I see 'Up/Down':
guru> grep 10604 test-esx.walk
IF-MIB::ifDescr.10604 = STRING: GigabitEthernet2/0/4
[...]
IF-MIB::ifName.10604 = STRING: Gi2/0/4
[...]
IF-MIB::ifAdminStatus.10604 = INTEGER: up(1)
IF-MIB::ifOperStatus.10604 = INTEGER: down(2)
[...]
IF-MIB::ifStackStatus.0.10604 = INTEGER: active(1)
IF-MIB::ifStackStatus.10604.0 = INTEGER: active(1)
[...]
CISCO-VLAN-MEMBERSHIP-MIB::vmPortStatus.10604 = INTEGER: active(2)
[...]
Poking through MIB files ... I guess I was hoping that ifAdminStatus would
offer a "dynamically-down" status ... but of course it does not:
ifAdminStatus OBJECT-TYPE
SYNTAX INTEGER {
up(1), -- ready to pass packets
down(2),
testing(3) -- in some test mode
}
I poked through CISCO-ERR-DISABLE-MIB and don't see anything port-specific.
Anyway, is this an unsolved problem? Or can anyone think of a clever way to
identify an interface in err-disable.
I notice that SwitchMap flags the interface with the string "port is active,
but no packets have been seen recently"
which suggests one way to do this.
?
--sk
--- End Message ---
--- Begin Message ---
Hi Stuart,
When ifOperStatus is down, Netdisco should also show it as being down.
Doesn't matter whether that "oper down" is because the switch has
err-disabled the port, the host on the port is powered of or nothing is
plugged in at all.
My guess is that your port shows Up/Up in Netdisco because it was
actually up when the switch was last discovered.
When you manually run a Discover job on a switch that has an
err-disabled port, after the discover is completed, I'd expect the port
to have Up/Down status.
Netdisco doesn't know about vendor-specific constructs of err-disabled
ports though, so even when a port is correctly discovered as being admin
up / oper down, you won't know why it's oper down.
Implementing vendor-specific err-disabled states would require changes
to both SNMP::Info and Netdisco. For the Cisco case, looks like
CISCO-ERR-DISABLE-MIB would be usable after all; see the description for
cErrDisableIfStatusTable.
I haven't looked at SwitchMap, but from the text "port is active" I'd
expect that it flags ports that are admin up / oper up (ie ports that
have link) but don't receive any packets. That's a common state for
hosts that are sleeping but have link up to support Wake-on-LAN, and
also often seen on embedded devices, vending machines and network
printers. Since err-disabled ports are always link down, SwitchMap
probably wouldn't flag them with the text you described.
Regards,
Jeroen van Ingen
ICT Service Centre
University of Twente, P.O.Box 217, 7500 AE Enschede, The Netherlands
On 09/13/2016 03:36 PM, Stuart Kendrick wrote:
Generically, I don’t see a way to identify ports in the err-disable
state. Am I missing something? Or is this an unsolved problem?
test-esx#sh int status | include err
Gi2/0/4 err-disabled 60 auto auto
10/100/1000BaseTX
Gi4/0/36 err-disabled 60 auto auto
10/100/1000BaseTX
test-esx#
Status for these ports in NetDisco show as ‘Up/Up’.
Though interestingly, poking through snmpwalk output, I see ‘Up/Down’:
guru> grep 10604 test-esx.walk
IF-MIB::ifDescr.10604 = STRING: GigabitEthernet2/0/4
[…]
IF-MIB::ifName.10604 = STRING: Gi2/0/4
[…]
IF-MIB::ifAdminStatus.10604 = INTEGER: up(1)
IF-MIB::ifOperStatus.10604 = INTEGER: down(2)
[…]
IF-MIB::ifStackStatus.0.10604 = INTEGER: active(1)
IF-MIB::ifStackStatus.10604.0 = INTEGER: active(1)
[…]
CISCO-VLAN-MEMBERSHIP-MIB::vmPortStatus.10604 = INTEGER: active(2)
[…]
Poking through MIB files … I guess I was hoping that ifAdminStatus
would offer a “dynamically-down” status … but of course it does not:
ifAdminStatus OBJECT-TYPE
SYNTAX INTEGER {
up(1), -- ready to pass packets
down(2),
testing(3) -- in some test mode
}
I poked through CISCO-ERR-DISABLE-MIB and don’t see anything port-specific.
Anyway, is this an unsolved problem? Or can anyone think of a clever
way to identify an interface in err-disable.
I notice that SwitchMap flags the interface with the string “/port is
active, but no packets have been seen recently”/
which suggests one way to do this.
?
--sk
--- End Message ---
------------------------------------------------------------------------------
_______________________________________________
Netdisco mailing list - Digest Mode
[email protected]
https://lists.sourceforge.net/lists/listinfo/netdisco-users
