Re: Remops Implementation Survey

Juergen Quittek <[email protected]>
Newsgroups gmane.ietf.disman
Message-ID <2147483647.1087526395@[192.168.1.8]>
Many thanks to all who submitted Remote Operations MIBs
implementation reports.

I know that also Juniper has an implementation.
Does anyone on the list have contacts to Juniper
and can ask there for an implementation report?

Below please find the form for the report.

Thanks,

    Juergen
-- 
Juergen Quittek        [email protected]        Tel: +49 6221 90511-15
NEC Europe Ltd.,       Network Laboratories        Fax: +49 6221 90511-55
Kurfuersten-Anlage 36, 69115 Heidelberg, Germany   http://www.ccrle.nec.de


--On 05.04.2004 12:25 Uhr -0700 Randy Presuhn wrote:

> Hi -
>
> Here is the Implementation Survey for RFC 2925, the Remote Operations MIBs.
> Please send responses to [email protected] , or, if you would like your implementation
> to remain anonymous for the implementation report, to the WG chair at
> [email protected].
>

=================================================

Implementation Survey for RFC 2925,
Definitions of Managed Objects for Remote Ping,
Traceroute, and Lookup Operations


Module: DISMAN-PING-MIB
Implementation Source:
Management Application / Agent:


GROUPs:
pingGroup (y/n): _
pingNotificationsGroup (y/n): _
pingTimeStampGroup (y/n): _

OBJECTs:
pingMaxConcurrentRequests (rw/ro): __
pingCtlStorageType (rw/ro): __
pingCtlType (rw/ro): __
pingCtlByPassRouteTable (rw/ro): __
pingCtlSourceAddressType (rw/ro): __
            unknown (y/n): _
            ipv4 (y/n): _
            ipv6 (y/n): _

pingCtlSourceAddress (rw/ro): __
pingCtlIfIndex (rw/ro): __
pingCtlDSField (rw/ro): __
pingResultsIpTargetAddressType:
            unknown (y/n): _
            ipv4 (y/n): _
            ipv6: _
pingResultsIpTargetAddress:
     0 (y/n): _
     4 (y/n): _
     16 (y/n): _


Module: DISMAN-TRACEROUTE-MIB
Implementation Source:
Management Application / Agent:

GROUPs:
traceRouteGroup (y/n): _
traceRouteTimeStampGroup (y/n): _
traceRouteNotificationsGroup (y/n): _
traceRouteHopsTableGroup (y/n):

OBJECTs:
traceRouteMaxConcurrentRequests (rw/ro): __
traceRouteCtlByPassRouteTable (rw/ro): __
traceRouteCtlSourceAddressType rw/ro): __
traceRouteCtlSourceAddress (rw/ro): __
traceRouteCtlIfIndex (rw/ro): __
traceRouteCtlMiscOptions (rw/ro): __
traceRouteCtlStorageType (rw/ro): __
traceRouteCtlDSField (rw/ro): __
traceRouteCtlType (rw/ro): __
traceRouteResultsIpTgtAddrType
        unknown (y/n): _
        ipv4 (y/n): _
        ipv6 (y/n): _
traceRouteResultsIpTgtAddr
        0 (y/n): _
        4 (y/n): _
        16 (y/n): _
traceRouteProbeHistoryHAddrType
        unknown (y/n): _
        ipv4 (y/n): _
        ipv6 (y/n): _
traceRouteProbeHistoryHAddr
        0 (y/n): _
        4 (y/n): _
        16 (y/n): _
traceRouteHopsIpTgtAddressType
        unknown (y/n): _
        ipv4 (y/n): _
        ipv6 (y/n): _
traceRouteHopsIpTgtAddress
        0 (y/n): _
        4 (y/n): _
        16 (y/n): _


Module: DISMAN-NSLOOKUP-MIB
Implementation Source:
Management Application / Agent:

GROUPs
lookupGroup (y/n): _

OBJECTs:
lookupMaxConcurrentRequests (rw/ro): __
lookupPurgeTime (rw/ro): __


Deployment / Operational Experience:


Comments:
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.