BIND 10 #1544: Resolve the design issues about names in MIB of stats-snmp
BIND 10 Development
do-not-reply at isc.org
Thu Jan 5 11:04:50 UTC 2012
#1544: Resolve the design issues about names in MIB of stats-snmp
-------------------------------------+-------------------------------------
Reporter: naokikambe | Owner:
Type: task | Status: new
Priority: major | Milestone: New
Component: statistics | Tasks
Sensitive: 0 | Keywords:
Sub-Project: DNS | Defect Severity: N/A
Estimated Difficulty: 0 | Feature Depending on Ticket: SNMP
Total Hours: 0 | stats
| Add Hours to Ticket: 0
| Internal?: 0
-------------------------------------+-------------------------------------
As result of #930 we found at least two possible issues about names in MIB
of stats-snmp in the current design as described in the prototype
implement in the experiment branch(kambe-SNMP-stats) and in the document
StatsModule#StatsSnmp(#1448).
* The MIB of stats-snmp is statically generated when the BIND 10 is made.
And if we change the daemons to run, for example, when we disable the Auth
daemon and enable the Resolver daemon, there may be an inconsistency
between such static MIB and the statistics list which is dynamically
answered by the Stats daemon.
* There might be name duplication in MIB. For example, if one name
authQueriestcp is defined in MIB as two different OIDs
.1.3.6.1.4.1.2021.255.0.0 and .1.3.6.1.4.1.2021.255.0.2.0.2, we can
access to the object firstly matched in MIB by authQueriestcp but we
cannot access secondly matched one by same way.
Improve current data mapping between specfile and MIB to resolve these
design issues, and then revise the document StatsModule#StatsSnmp.
--
Ticket URL: <http://bind10.isc.org/ticket/1544>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development
More information about the bind10-tickets
mailing list