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. Re: Duplicate Cisco Nexus Serial Numbers (Chip Pleasants)
----------------------------------------------------------------------
Message: 1
Date: Wed, 14 Oct 2015 15:45:59 -0400
From: Chip Pleasants <[email protected]>
Subject: Re: [Netdot-users] Duplicate Cisco Nexus Serial Numbers
To: "[email protected]" <[email protected]>
Message-ID:
<cajq5atqv0zgxmuwf7xpgwr2veafr7_2cxywc8ceymgdohcx...@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
Hi all,
I've only received one reply from my message about our change in the
device.pm. Is device.pm not Netdot source? I've included the change below
for everyone. I can post it in another place if someone directs me
where. I'm kind of surprised no one has seen this before. Let me know if
anyone has questions.
[NETDOT_SERVER]# diff Device.pm Device_backup.pm
3027,3029d3026
< # Print asset id's for serial and base mac easier debugging
< $logger->debug("$host: ASSET SN $asset_sn");
< $logger->debug("$host: ASSET BASE MAC $asset_phy");
5697,5703c5694
< # Added to declare device sysdescription
< my $sysdesc = delete $info->{sysdescription};
<
< # Added to not allow NX-OS devices to use base mac, incase VPC
peer-switch is configured
< # Since this feature causes the same base MAC to be used for every
VPC device with the same
< # Domain ID.
< if ( $address && ($address = PhysAddr->validate($address)) &&
$sysdesc !~ /NX-OS/ ) {
---
> if ( $address && ($address = PhysAddr->validate($address))) {
[NETDOT_SERVERl]#
Thanks,
Chip
On Mon, Oct 12, 2015 at 11:49 AM, Chip Pleasants <[email protected]>
wrote:
> Hi All,
>
> Just wanted to provide an update. We patched the device.pm, which I
> believe is part of Netdot source. We added in a check to see if the device
> was NX-OS and it if is, use the first interface mac on the device (the mgmt
> interface) as the base_mac within NetDot rather than the Bridge ID as the
> base_mac. Since the mgmt-int should be unique, this appears to resolve the
> issue. I'm not sure what the correct protocol for code
> updates/changes/suggestions to the source, so please comment on how I
> should handle this particular instance. Idealy I'd think everyone would
> want a fix for tis particular issue but maybe not.
>
> -Chip
>
>
>
> On Fri, Oct 9, 2015 at 9:21 AM, Chip Pleasants <[email protected]>
> wrote:
>
>> 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/20151014/4c508009/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 3
*******************************************
