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. Macsuck errors (Junk Mail)
2. Re: Macsuck errors (Oliver Gorwits)
3. Re: IP address confusion when discovering Arista switch
(Oliver Gorwits)
4. Re: IP address confusion when discovering Arista switch
(Oliver Gorwits)
--- Begin Message ---
Hey:
We have Cisco 3750X switch stacks in our environment and it looks like Netdisco
is having issues getting interface index mappings. Below is some relevant
info. Is there anything i can do to get this working?
Netdisco:
App::Netdisco 2.36.3
SNMP::Info 3.35
DB Schema 44
PostgreSQL 9.2.18
Perl 5.16.3
Switch:
Cisco IOS Software, C3750E Software (C3750E-UNIVERSALK9-M), Version 15.0(2)SE9,
RELEASE SOFTWARE (fc1)
cisco WS-C3750X-48P (PowerPC405) processor (revision A0) with 262144K bytes of
memory.
Some debug info:
SNMP::Info::_load_attr i_index : IF-MIB::ifIndex : .1.3.6.1.2.1.2.2.1.1
SNMP::Info::_load_attr i_description : IF-MIB::ifDescr : .1.3.6.1.2.1.2.2.1.2
SNMP::Info::_load_attr qb_fw_port : Q-BRIDGE-MIB::dot1qTpFdbPort :
.1.3.6.1.2.1.17.7.1.2.2.1.2
SNMP::Info::_load_attr orig_fw_mac : BRIDGE-MIB::dot1dTpFdbAddress :
.1.3.6.1.2.1.17.4.3.1.1
SNMP::Info::_load_attr qb_fw_port : Q-BRIDGE-MIB::dot1qTpFdbPort :
.1.3.6.1.2.1.17.7.1.2.2.1.2
SNMP::Info::_load_attr orig_fw_port : BRIDGE-MIB::dot1dTpFdbPort :
.1.3.6.1.2.1.17.4.3.1.2
SNMP::Info::_load_attr qb_fw_port : Q-BRIDGE-MIB::dot1qTpFdbPort :
.1.3.6.1.2.1.17.7.1.2.2.1.2
SNMP::Info::_load_attr dot1qVlanFdbId : Q-BRIDGE-MIB::dot1qVlanFdbId :
.1.3.6.1.2.1.17.7.1.4.2.1.3
SNMP::Info::_load_attr bp_index : BRIDGE-MIB::dot1dBasePortIfIndex :
.1.3.6.1.2.1.17.1.4.1.2
[24191] 2017-08-14 20:14:56 debug [172.16.252.70] macsuck 9c:5d:12:87:70:00 -
port 226 has no bp_index mapping - skipping.
[24191] 2017-08-14 20:14:56 debug [172.16.252.70] macsuck e0:1c:41:6d:91:c0 -
port 94 has no bp_index mapping - skipping.
[24191] 2017-08-14 20:14:56 debug [172.16.252.70] macsuck e0:1c:41:6d:92:c0 -
port 269 has no bp_index mapping - skipping.
[24191] 2017-08-14 20:14:56 debug [172.16.252.70] macsuck e0:1c:41:6d:91:00 -
port 98 has no bp_index mapping - skipping.
[24191] 2017-08-14 20:14:56 debug [172.16.252.70] macsuck e0:1c:41:6d:92:00 -
port 92 has no bp_index mapping - skipping.
[24191] 2017-08-14 20:14:56 debug [172.16.252.70] macsuck 10:f3:11:87:86:99 -
port Port-channel31 has neighbor 172.16.252.75 - skipping.
[24191] 2017-08-14 20:14:56 debug [172.16.252.70] macsuck 4c:4e:35:97:ef:b8 -
port Port-channel19 has neighbor 172.16.252.100 - skipping.
[24191] 2017-08-14 20:14:56 debug [172.16.252.70] macsuck e0:1c:41:6d:91:80 -
port 96 has no bp_index mapping - skipping.
[24191] 2017-08-14 20:14:56 debug [172.16.252.70] macsuck 4c:4e:35:c0:41:b1 -
port Port-channel31 has neighbor 172.16.252.75 - skipping.
[24191] 2017-08-14 20:14:56 debug [172.16.252.70] macsuck 4c:4e:35:97:f0:78 -
port Port-channel19 has neighbor 172.16.252.100 - skipping.
SNMP::Info::_load_attr i_type : IF-MIB::ifType : .1.3.6.1.2.1.2.2.1.3
--- End Message ---
--- Begin Message ---
Hi
You could send the output of the following to a ticket at github.com or
as an attachment to this list:
~netdisco/bin/netdisco-do show -DI -d 1.2.3.4 -e fw_port
~netdisco/bin/netdisco-do show -DI -d 1.2.3.4 -e bp_index
regards,
oliver.
On 2017-08-16 14:16, Junk Mail wrote:
Hey:
We have Cisco 3750X switch stacks in our environment and it looks like
Netdisco is having issues getting interface index mappings. Below is
some relevant info. Is there anything i can do to get this working?
Netdisco:
App::Netdisco 2.36.3
SNMP::Info 3.35
DB Schema 44
PostgreSQL 9.2.18
Perl 5.16.3
Switch:
Cisco IOS Software, C3750E Software (C3750E-UNIVERSALK9-M), Version
15.0(2)SE9, RELEASE SOFTWARE (fc1)
cisco WS-C3750X-48P (PowerPC405) processor (revision A0) with 262144K
bytes of memory.
Some debug info:
SNMP::Info::_load_attr i_index : IF-MIB::ifIndex :
.1.3.6.1.2.1.2.2.1.1
SNMP::Info::_load_attr i_description : IF-MIB::ifDescr :
.1.3.6.1.2.1.2.2.1.2
SNMP::Info::_load_attr qb_fw_port : Q-BRIDGE-MIB::dot1qTpFdbPort :
.1.3.6.1.2.1.17.7.1.2.2.1.2
SNMP::Info::_load_attr orig_fw_mac : BRIDGE-MIB::dot1dTpFdbAddress :
.1.3.6.1.2.1.17.4.3.1.1
SNMP::Info::_load_attr qb_fw_port : Q-BRIDGE-MIB::dot1qTpFdbPort :
.1.3.6.1.2.1.17.7.1.2.2.1.2
SNMP::Info::_load_attr orig_fw_port : BRIDGE-MIB::dot1dTpFdbPort :
.1.3.6.1.2.1.17.4.3.1.2
SNMP::Info::_load_attr qb_fw_port : Q-BRIDGE-MIB::dot1qTpFdbPort :
.1.3.6.1.2.1.17.7.1.2.2.1.2
SNMP::Info::_load_attr dot1qVlanFdbId : Q-BRIDGE-MIB::dot1qVlanFdbId :
.1.3.6.1.2.1.17.7.1.4.2.1.3
SNMP::Info::_load_attr bp_index : BRIDGE-MIB::dot1dBasePortIfIndex :
.1.3.6.1.2.1.17.1.4.1.2
[24191] 2017-08-14 20:14:56 debug [172.16.252.70] macsuck
9c:5d:12:87:70:00 - port 226 has no bp_index mapping - skipping.
[24191] 2017-08-14 20:14:56 debug [172.16.252.70] macsuck
e0:1c:41:6d:91:c0 - port 94 has no bp_index mapping - skipping.
[24191] 2017-08-14 20:14:56 debug [172.16.252.70] macsuck
e0:1c:41:6d:92:c0 - port 269 has no bp_index mapping - skipping.
[24191] 2017-08-14 20:14:56 debug [172.16.252.70] macsuck
e0:1c:41:6d:91:00 - port 98 has no bp_index mapping - skipping.
[24191] 2017-08-14 20:14:56 debug [172.16.252.70] macsuck
e0:1c:41:6d:92:00 - port 92 has no bp_index mapping - skipping.
[24191] 2017-08-14 20:14:56 debug [172.16.252.70] macsuck
10:f3:11:87:86:99 - port Port-channel31 has neighbor 172.16.252.75 -
skipping.
[24191] 2017-08-14 20:14:56 debug [172.16.252.70] macsuck
4c:4e:35:97:ef:b8 - port Port-channel19 has neighbor 172.16.252.100 -
skipping.
[24191] 2017-08-14 20:14:56 debug [172.16.252.70] macsuck
e0:1c:41:6d:91:80 - port 96 has no bp_index mapping - skipping.
[24191] 2017-08-14 20:14:56 debug [172.16.252.70] macsuck
4c:4e:35:c0:41:b1 - port Port-channel31 has neighbor 172.16.252.75 -
skipping.
[24191] 2017-08-14 20:14:56 debug [172.16.252.70] macsuck
4c:4e:35:97:f0:78 - port Port-channel19 has neighbor 172.16.252.100 -
skipping.
SNMP::Info::_load_attr i_type : IF-MIB::ifType : .1.3.6.1.2.1.2.2.1.3
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Netdisco mailing list
netdisco-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/netdisco-users
--- End Message ---
--- Begin Message ---
Hi Mark
On 2017-08-14 19:17, Mark Boolootian wrote:
Deleting and discovering always produced the same result.
However, setting reverse_sysname to false and deleting and
discovering fixed the issue. Does that offer any hints about
what might be causing this?
No immediate thoughts. When Netdisco selects the reverse IP of the
sysName, it makes an SNMP test connection - so something is responding!
Anything running on the Arista which would proxy ARP?
Anyway, my advice: leave reverse_sysname disabled. In my opinion it's a
hack which is prone to human error, and you can use DNS instead. If
Netdisco picks the wrong management IP for a device, either use LLDP
config to alter what is advertised, or use device_identity in Netdisco
to steer it to the correct IP alias.
regards,
oliver.
--- End Message ---
--- Begin Message ---
Here's an example of the device_identity config for our Arista:
device_identity:
'vendor:arista': 'port:(?i)management.*'
which means... "when the device vendor is Arista, use the lowest IP on a
port named management*".
Another example ("pick the lowest interface IP with property which looks
like...."):
device_identity:
'vendor:fortinet': 'port:(?i)mgmt.*'
'vendor:brocade': 'dns:.*-mgmt.example.com'
'vendor:cisco': '172.20.20.0/24' # CPEs
HTH,
regards,
oliver.
On 2017-08-16 21:40, Oliver Gorwits wrote:
Hi Mark
On 2017-08-14 19:17, Mark Boolootian wrote:
Deleting and discovering always produced the same result.
However, setting reverse_sysname to false and deleting and
discovering fixed the issue. Does that offer any hints about
what might be causing this?
No immediate thoughts. When Netdisco selects the reverse IP of the
sysName, it makes an SNMP test connection - so something is
responding! Anything running on the Arista which would proxy ARP?
Anyway, my advice: leave reverse_sysname disabled. In my opinion it's
a hack which is prone to human error, and you can use DNS instead. If
Netdisco picks the wrong management IP for a device, either use LLDP
config to alter what is advertised, or use device_identity in Netdisco
to steer it to the correct IP alias.
regards,
oliver.
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Netdisco mailing list
netdisco-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/netdisco-users
--- End Message ---
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Netdisco mailing list - Digest Mode
netdisco-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/netdisco-users
