Send Netdot-devel mailing list submissions to
[email protected]
To subscribe or unsubscribe via the World Wide Web, visit
https://osl.uoregon.edu/mailman/listinfo/netdot-devel
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-devel digest..."
Today's Topics:
1. [Netdot - Bug #200] Product name too specific
([email protected])
----------------------------------------------------------------------
Message: 1
Date: Thu, 6 Jun 2013 06:46:38 -0700
From: [email protected]
Subject: [Netdot-devel] [Netdot - Bug #200] Product name too specific
To: [email protected], [email protected],
[email protected]
Message-ID: <[email protected]>
Content-Type: text/plain; charset=utf-8
Issue #200 has been updated by Chris Wilson.
Does the sysName entry help?
<pre>
SNMPv2-MIB::sysDescr.0 = STRING: "PROCURVE J9029A - PA.03.01"
SNMPv2-MIB::sysName.0 = STRING: "PROCURVE J9029A"
</pre>
----------------------------------------
Bug #200: Product name too specific
https://osl.uoregon.edu/redmine/issues/200#change-3085
Author: stephenf -
Status: Closed
Priority: Normal
Assignee: Carlos Vicente
Category:
Target version: 0.8
Resolution: fixed
We have a few devices that were discovered where netdot created a new product
to associate the device with. The problem is that the product name is too
specific. For example:
2620 chassis, Hw Serial#: 443681889, Hw Revision: 0x102
There are a couple other examples. The hardware serial number of a specific
device isn't appropriate for a product name.
--
You have received this notification because you have either subscribed to it,
or are involved in it.
To change your notification preferences, please click here:
http://osl.uoregon.edu/redmine/my/account
------------------------------
_______________________________________________
Netdot-devel mailing list
[email protected]
https://osl.uoregon.edu/mailman/listinfo/netdot-devel
End of Netdot-devel Digest, Vol 75, Issue 5
*******************************************
