Implementation Report for Remote Operations MIB modules
"Randy Presuhn" <[email protected]> Tue, 5 Oct 2004 13:31:15 -0700
| Newsgroups | gmane.ietf.disman |
|---|---|
| Message-ID | <000b01c4ab1a$430de520$7f1afea9@oemcomputer> |
Hi Bert -
In preparation for advancing the disman Remote Operations MIB
modules to Draft Standard, here are implementation reports for the
DISMAN-PING-MIB, the DISMAN-TRACROUTE-MIB, and the
DISMAN-NSLOOKUP-MIB. There were at least two independent
implementations of each of these. There was at least
one freely-available implementation ("B") for all
three MIB modules.
Implementation | Submitted By | Submitter's |
Report | | Address |
---------------+-----------------+----------------------------+
B | J. Chen | [email protected] |
R | Govind Haridass | [email protected] |
J | Daniel Chuang | [email protected] |
E | John Scano | [email protected] |
Note that "E" and "J" were done by different groups at
Juniper, and were reported separately.
Report | Implementation Source
-------+-------------------------------------------------------
B | Beijing University of Posts and Telecommunications
| Network Information Center
E | Juniper (E-Series routers)
J | Juniper
R | SNMP Research
Module: DISMAN-PING-MIB
Groups | Implementation |
Implemented | B | J | R |
-----------------------+----+-----+-----+
pingGroup | y | y | y |
pingNotificationsGroup | y | y | y |
pingTimeStampGroup | y | y | y |
There were reports on three independent implementations, and all
supported all three object groups in this MIB module. Additional
details on the individual objects implemented:
OBJECT-TYPE | Implementation |
access supported | B | J | R |
-------------------------------+----+-----+-----+
pingMaxConcurrentRequests | - | rw | rw |
pingCtlStorageType | rw | rw | rw |
pingCtlType | rw | rw | rw |
pingCtlByPassRouteTable | rw | rw | rw |
pingCtlSourceAddressType | rw | rw | rw |
unknown | n | y | n |
ipv4 | n | y | y |
ipv6 | n | n | n |
pingCtlSourceAddress | rw | rw | rw |
pingCtlIfIndex | rw | rw | rw |
pingCtlDSField | rw | rw | rw |
pingResultsIpTargetAddressType | ro | ro | ro |
unknown | y | y | n |
ipv4 | y | y | y |
ipv6 | y | n | n |
pingResultsIpTargetAddress | ro | ro | ro |
0 | y | y | |
4 | y | y | |
16 | y | n | |
Module: DISMAN-TRACEROUTE-MIB
There were reports on three independent implementations of
the DISMAN-TRACROUTE-MIB, and all three supported all four
groups.
Groups | Implementation |
Implemented | B | J | R |
-----------------------------+----+-----+-----+
traceRouteGroup | y | Y | Y |
traceRouteTimeStampGroup | y | Y | Y |
traceRouteNotificationsGroup | y | Y | Y |
traceRouteHopsTableGroup | y | Y | Y |
Additional details on support of specific OBJECT-TYPES:
OBJECT-TYPE | Implementation |
access supported | B | J | R |
--------------------------------+----+-----+-----+
traceRouteMaxConcurrentRequests | - | rw | rw |
traceRouteCtlByPassRouteTable | rw | rw | rw |
traceRouteCtlSourceAddressType | rw | rw | rw |
traceRouteCtlSourceAddress | rw | rw | rw |
traceRouteCtlIfIndex | rw | rw | rw |
traceRouteCtlMiscOptions | rw | rw | ro |
traceRouteCtlStorageType | rw | rw | rw |
traceRouteCtlDSField | rw | rw | rw |
traceRouteCtlType | rw | rw | rw |
traceRouteResultsIpTgtAddrType | | | |
unknown | y | y | n |
ipv4 | y | y | y |
ipv6 | y | n | n |
traceRouteResultsIpTgtAddr | | | |
0 | y | y | |
4 | y | y | |
16 | y | n | |
traceRouteProbeHistoryHAddrType | | | |
unknown | y | y | n |
ipv4 | y | y | y |
ipv6 | y | n | n |
traceRouteProbeHistoryHAddr | | | |
0 | y | y | |
4 | y | y | |
16 | y | n | |
traceRouteHopsIpTgtAddressType | | | |
unknown | y | y | n |
ipv4 | y | y | n |
ipv6 | y | n | n |
traceRouteHopsIpTgtAddress | | | |
0 | y | y | |
4 | y | y | |
16 | y | n | |
Module: DISMAN-NSLOOKUP-MIB
There were two reports of implementations of the
DISMAN-NSLOOKUP-MIB module. Both implemented the
mandatory object group for lookupCompliance, which
is a superset of the lookupMinimumComplaince.
Groups | Implementation |
Implemented | B | E |
-----------------------------+----------------+
lookupGroup | y | y |
Additional details on support of specific OBJECT-TYPES:
OBJECT-TYPE | Implementation |
access supported | B | E |
--------------------------------+---------+------+
lookupMaxConcurrentRequests | n (?) | y |
lookupPurgeTime | n (?) | y |
lookupCtlTargetAddressType | | |
ipv4 | y | y |
ipv6 | y | y |
dns | y | y |
lookupCtlTargetAddress | | |
ipv4 | y | y |
ipv6 | y | y |
dns | y | y |
lookupResultsAddressType | | |
ipv4 | y | y |
ipv6 | y | y |
dns | y | y |
lookupResultsAddress | | |
ipv4 | y | y |
ipv6 | y | y |
dns | y | y |