Send Netdot-users mailing list submissions to
        [email protected]

To subscribe or unsubscribe via the World Wide Web, visit
        https://osl.uoregon.edu/mailman/listinfo/netdot-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 Netdot-users digest..."


Today's Topics:

   1. Duplicate Cisco Nexus Serial Numbers (Chip Pleasants)


----------------------------------------------------------------------

Message: 1
Date: Fri, 9 Oct 2015 09:21:19 -0400
From: Chip Pleasants <[email protected]>
Subject: [Netdot-users] Duplicate Cisco Nexus Serial Numbers
To: "[email protected]" <[email protected]>
Message-ID:
        <cajq5atrpn5ku0+p2vu1jm+kbgldowrmy3jtotreg5t50w9y...@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"

Hi All,

We are seeing duplicate serial numbers on Nexus VPC peers.  A pair of Nexus
with the same VPC domain have the same serial numbers.  I found a bug with
SNMP::Info 3.05 or prior, however updating to the latest 3.28 still doesn't
seem to fix the issue. Looks like it was fixed in 3.07. Anyone else seen
this before? How can I tell that I'm using the correct SNMP::Info module?
Anyway to actively view the polling? Does Netdot use NetDisco database
structure? Below is the thread I found, which discusses exactly what we are
seeing. Let me know if you have any questions and thank you for assisting
me.

http://sourceforge.net/p/snmp-info/mailman/snmp-info-users/thread/[email protected]/



Thanks,
Chip
-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
http://osl.uoregon.edu/pipermail/netdot-users/attachments/20151009/8c4de560/attachment-0001.html
 

------------------------------

_______________________________________________
Netdot-users mailing list
[email protected]
https://osl.uoregon.edu/mailman/listinfo/netdot-users


End of Netdot-users Digest, Vol 82, Issue 1
*******************************************

Reply via email to