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: errorlog Invalid size for IPv6 address (Jeroen van Ingen)
   2. Re: Duplicate mac entries on every vlan (Jeroen van Ingen)
   3. Re: Report for Cisco Catalyst 3K Advisory (Natxo Asenjo)
   4. Re: Duplicate mac entries on every vlan
      (SOPORTE ADMINISTRACION DE REDES Y COMUNICACIONES)
   5. Serial number shows as 0x10 (Zachary McGibbon)
--- Begin Message ---
Hi Norbert,

Thanks for the debug output. Looks like the Windows server has an implementation error in IPV6-MIB, it seems to return an octet specifying the address size/length even though it shouldn't.

I guess it's easier to implement a workaround in SNMP::Info than it is to file a bug report with Microsoft ;-). I don't have a Windows server with SNMP enabled to test against; can you try a patched version of SNMP::Info to see if that solves your issue?

Patched version is now available as a separate branch, https://sourceforge.net/p/snmp-info/code/ci/IPv6-workaround/tree/. I also attached the diff as a patch.

Please let me know if this solves the error; if so, I'll merge the patch for the next release.


Regards,

Jeroen van Ingen
ICT Service Centre
University of Twente, P.O.Box 217, 7500 AE Enschede, The Netherlands


On 02/10/2016 10:15 AM, Elitzer, Norbert wrote:
Hi,

- What make & model device are you seeing this on?
        arpnip at Windows 2012 R2 ESX Virtual Machine
- What software version is it running?
        Netdisco 2.033005 on Redhat7
- What version of SNMP::Info do you have on the server?
        SNMP::Info - Version 3.31

the error happens when I start arpnic job

~/bin/netdisco-do arpnip -DD -II -d 192.168.xxx.yyy

See log in the attachment



-----Original Message-----
From: Jeroen van Ingen [mailto:[email protected]]
Sent: Montag, 08. Februar 2016 10:09
To: [email protected]
Subject: Re: [Netdisco] errorlog Invalid size for IPv6 address

Hi,

Could be a bug in SNMP::Info or a bug in the SNMP agent on one of your
devices.

- What make & model device are you seeing this on?
- What software version is it running?
- What version of SNMP::Info do you have on the server?


Regards,

Jeroen van Ingen
ICT Service Centre
University of Twente, P.O.Box 217, 7500 AE Enschede, The Netherlands



On 02/05/2016 11:12 AM, Elitzer, Norbert wrote:
Hello,
I just update to the new version 2.033005 and checked my log files.
MY 'old' error shows up again...
I this a known error or to I have just a fault at my IPv6 infrastruture?
[6989] 2016-02-05 08:37:32  warn App::Netdisco 2.033005 backend
Use of uninitialized value $args{"mac"} in pattern match (m//) at
/home/netdisco/perl5/lib/perl5/NetAddr/MAC.pm line 269, <__ANONIO__>
line 36.
Use of uninitialized value $node in sprintf at
/home/netdisco/perl5/lib/perl5/App/Netdisco/Util/Node.pm line 75,
<__ANONIO__> line 36.
Invalid size for IPv6 address: expected 16 bytes, got 17
(1.16.255.2.0.0.0.0.0.0.0.0.0.0.0.0.0.22 = )
Invalid size for IPv6 address: expected 16 bytes, got 17
(14.16.255.2.0.0.0.0.0.0.0.0.0.0.0.0.0.22 = 33:33:00:00:00:16)
Invalid size for IPv6 address: expected 16 bytes, got 17
(14.16.255.2.0.0.0.0.0.0.0.0.0.0.0.0.0.1 = 33:33:00:00:00:01)
Invalid size for IPv6 address: expected 16 bytes, got 17
(14.16.255.2.0.0.0.0.0.0.0.0.0.0.0.0.0.2 = 33:33:00:00:00:02)
Invalid size for IPv6 address: expected 16 bytes, got 17
(14.16.255.2.0.0.0.0.0.0.0.0.0.0.0.1.0.3 = 33:33:00:01:00:03)
Invalid size for IPv6 address: expected 16 bytes, got 17
(1.16.255.2.0.0.0.0.0.0.0.0.0.0.0.1.0.2 = )
Invalid size for IPv6 address: expected 16 bytes, got 17
(14.16.255.2.0.0.0.0.0.0.0.0.0.0.0.1.0.2 = 33:33:00:01:00:02)
Invalid size for IPv6 address: expected 16 bytes, got 17
(14.16.255.2.0.0.0.0.0.0.0.0.0.1.255.163.83.136 = 33:33:ff:xx:xx:xx)
My previous  workaround to suppress this error was to change the IPv6.pm
~/perl5/lib/perl5/SNMP/Info/IPv6.pm
#my $v6_packed = pack("C*", split(/\./, $v6addr));
my $v6_packed = pack("C16", split(/\./, $v6addr));
Thanks,
Norbert




diff --git a/Info/IPv6.pm b/Info/IPv6.pm
index bab9301..5ec0e0d 100644
--- a/Info/IPv6.pm
+++ b/Info/IPv6.pm
@@ -72,10 +72,10 @@ $VERSION = '3.31';
     'ip_pfx_origin'     => 'ipAddressPrefixOrigin',         # IP-MIB
     'c_pfx_origin'      => 'cIpAddressPfxOrigin',           # CISCO-IETF-IP-MIB 
 
-    'ip_addr6_pfx'      => 'ipAddressPrefix',              # IP-MIB 
+    'ip_addr6_pfx'      => 'ipAddressPrefix',               # IP-MIB 
     'c_addr6_pfx'       => 'cIpAddressPrefix',              # CISCO-IETF-IP-MIB 
 
-    'ip_addr6_index'    => 'ipAddressIfIndex',              # IP-MIBw
+    'ip_addr6_index'    => 'ipAddressIfIndex',              # IP-MIB
     'c_addr6_index'     => 'cIpAddressIfIndex',             # CISCO-IETF-IP-MIB 
 
     'ip_addr6_type'     => 'ipAddressType',                 # IP-MIB
@@ -142,6 +142,12 @@ sub ipv6_n2p_addr {
                     # so what we've collected in that variable is actually the first byte of the address.
                     $v6_packed = pack('C', $addrsize) . $v6_packed;
                 }
+                if (length($v6_packed) == 17) {
+                    # Workaround for IPV6-MIB on Windows 2012: if the address is one byte too long, the SNMP agent probably has an incorrect
+                    # implementation where a length field precedes the actual IPv6 address.
+                    # In that case, the first character should be chr(16), ie 0x10; strip it if that's the case.
+                    $v6_packed =~ s/^\x10//;
+                }
                 if (length($v6_packed) == 16) {
                     $v6addr = join(':', map { sprintf("%04x", $_) } unpack("n*", $v6_packed) );
                     $return->{$row} = $v6addr;

--- End Message ---
--- Begin Message ---
Hi,

If I remember correctly, the HP 2524 was the last ProCurve switch that actually didn't have a VLAN aware forwarding table. While it supports VLANs, a MAC can only be learned on a single port and isn't linked to the VLAN config on the port.

We don't have any 2524's in our network anymore so I can't verify the SNMP output, but I think the switch will simply return each MAC it knows in all VLANs.

TBH I don't think it's worth the time to fix this in Netdisco.


Regards,

Jeroen van Ingen
ICT Service Centre
University of Twente, P.O.Box 217, 7500 AE Enschede, The Netherlands


On 02/04/2016 11:55 AM, SOPORTE ADMINISTRACION DE REDES Y COMUNICACIONES wrote:
Hi there,

I'm facing some strange behaviour in some of our pretty old procurve
gear (2524 with version F.05.75 circa 2010). This does not happen in
other newer procurve switches.

Netdisco shows an actual mac address on a port belonging to every vlan
in that switch, instead of just showing the mac once in the proper vlan.

00:1e:90:XX:XX:XX (on vlan 1)
00:1e:90:XX:XX:XX (on vlan 50)
00:1e:90:XX:XX:XX (on vlan 10)
00:1e:90:XX:XX:XX (on vlan 62)
00:1e:90:XX:XX:XX (on vlan 63)
...and so on

Its weird because it also shows IP and netbios info in EVERY vlan.
However it shows both actual native and tagged vlans in the left colums
(please refer to the attached picture)

¿Anyone else facing issue? ¿Any parameter in the web gui to show just
one line?

Thank you,
Ramon




--- End Message ---
--- Begin Message ---
Hi Zachary,

On Mon, Feb 29, 2016 at 9:52 PM, Zachary McGibbon <
[email protected]> wrote:

> Here is the added field notice 63744 which adds some 2K switches
>
> http://www.cisco.com/c/en/us/support/docs/field-notices/637/fn63744.html
>
>   - tag: cisco_fn_63744_63745
>     label: 'Cisco Field Notice 63744 and 63745'
>     columns:
>       - {name: 'Name'}
>       - {ip: 'IP'}
>       - {pos: 'Switch Number'}
>       - {model: 'Model'}
>       - {serial: 'Serial'}
>       - {hw_ver: 'HW Ver'}
>       - {fw_ver: 'Firmware'}
>       - {last_discover: 'Last Discover'}
> <https://lists.sourceforge.net/lists/listinfo/netdisco-users>
>

[knip]

This is awesome! Thanks for sharing.

--
regards,
natxo

--- End Message ---
--- Begin Message ---
Hello Jeroen,

It makes sense, they're pretty old and I just wanted to check if anyone has 
faced this issue.

No worries, thanks for such an awesome tool!

Best regards,
Ramón

----- Mensaje original -----
De: "Jeroen van Ingen" <[email protected]>
Para: "SOPORTE ADMINISTRACION DE REDES Y COMUNICACIONES" <[email protected]>, 
[email protected]
Enviados: Martes, 1 de Marzo 2016 9:11:59
Asunto: Re: [Netdisco] Duplicate mac entries on every vlan

Hi,

If I remember correctly, the HP 2524 was the last ProCurve switch that
actually didn't have a VLAN aware forwarding table. While it supports
VLANs, a MAC can only be learned on a single port and isn't linked to
the VLAN config on the port.

We don't have any 2524's in our network anymore so I can't verify the
SNMP output, but I think the switch will simply return each MAC it knows
in all VLANs.

TBH I don't think it's worth the time to fix this in Netdisco.


Regards,

Jeroen van Ingen
ICT Service Centre
University of Twente, P.O.Box 217, 7500 AE Enschede, The Netherlands


On 02/04/2016 11:55 AM, SOPORTE ADMINISTRACION DE REDES Y COMUNICACIONES
wrote:
> Hi there,
>
> I'm facing some strange behaviour in some of our pretty old procurve
> gear (2524 with version F.05.75 circa 2010). This does not happen in
> other newer procurve switches.
>
> Netdisco shows an actual mac address on a port belonging to every vlan
> in that switch, instead of just showing the mac once in the proper vlan.
>
> 00:1e:90:XX:XX:XX (on vlan 1)
> 00:1e:90:XX:XX:XX (on vlan 50)
> 00:1e:90:XX:XX:XX (on vlan 10)
> 00:1e:90:XX:XX:XX (on vlan 62)
> 00:1e:90:XX:XX:XX (on vlan 63)
> ...and so on
>
> Its weird because it also shows IP and netbios info in EVERY vlan.
> However it shows both actual native and tagged vlans in the left colums
> (please refer to the attached picture)
>
> ¿Anyone else facing issue? ¿Any parameter in the web gui to show just
> one line?
>
> Thank you,
> Ramon




--- End Message ---
--- Begin Message ---
I've noticed that a lot of my Cisco switches show up in the inventory with
a serial number of 0x10, however if I re-run a discover on the device it is
corrected.  Then, when the cron runs the next day it goes back to 0x10

I've looked in the tables and see that this 0x10 is stored in the 'device'
table in the 'serial' column.

However, in the device_module table the serial for the same switch is
correct.

Anyone else have this problem?

- Zachary

--- End Message ---
------------------------------------------------------------------------------
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140
_______________________________________________
Netdisco mailing list - Digest Mode
[email protected]
https://lists.sourceforge.net/lists/listinfo/netdisco-users

Reply via email to